Download Frodo compatible test version here

Download Frodo compatible test version here - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: Supplementary Tools for Kodi (https://forum.kodi.tv/forumdisplay.php?fid=116)
+---- Forum: Kodi Remote for Android Official Forum (https://forum.kodi.tv/forumdisplay.php?fid=129)
+---- Thread: Download Frodo compatible test version here (/showthread.php?tid=147741)

Pages: 1 2 3 4 5

RE: Download Frodo compatible test version here - RogerS - 2012-12-26

(2012-12-23, 16:58)dhead Wrote: It seems that the remote is crashing (partially, if that make sense) and generating a crash log when I try to browse audio folders in file mode (only on the second level)

Unfortunately I can confirm this. I'm using a Google Nexus 7 together with Openelec V2.95.6 beta which is based on Frodo RC 2.

I how stability of the "Official" remote will quickly be improved because I find the alternative (Yatse), due to it's cluttered and somewhat strange UI design, too user unfriendly.

RE: Download Frodo compatible test version here - Millencolin007 - 2012-12-26

If you don't like Yatse, there is also Music Pump XBMC Remote which works well with XBMC frodo

RE: Download Frodo compatible test version here - ZULan87 - 2013-01-07

Hi,

I have noticed a couple of issues, will there be an updated version released soon?
I guess that the issues I have are already posted somewhere as a defect and you are already aware of this.

Best regards

RE: Download Frodo compatible test version here - tthomas48 - 2013-01-07

Freezy was talking about going with tombriden's fork with Frodo support. Not sure where in the process that is...

RE: Download Frodo compatible test version here - Nat! - 2013-01-08

Hi

I downloaded xbmc for the first time in my life, choosing the latest release candidate frodo for OS X. Then I tried to control it on my phone with the android remote, which i downloaded from this thread (v0.10.6-alpha_tombriden).

Unfortunately it's not working so great. I can browse stuff (music) on the file level, but I can't get the albums list. (See error log below). There is nothing interesting to be seen in the server log. I sent the request, gleaning it from the server log with curl

Quote:curl -q -H "Accept: application/json" -H "Content-type: application/json" -X POST -d '{"jsonrpc": "2.0", "id": 1, "method": "AudioLibrary.GetAlbums", "params"
: {"properties": ["title", "description", "albumlabel", "artist", "genre", "year", "thumbnail", "fanart", "rating", "playcount"],
"limits": {"end": 20}, "sort": {"method": "random"}}}' 192.168.2.1:8080/jsonrpc

to xbmc manually, took the result and checked it with jsonlint, which surprisingly said "valid json" (even when removing the limits). The strings look like they are properly UTF-8 encoded.

Regards
Nat!

Server

Quote:20:08:11 T:2899700264 NOTICE: Starting XBMC (12.0-RC3 Git:20130102-7a6cb7f), Platform: Darwin OSX (12.2.0 x86_64, Version 10.8.2 (Build 12C60)). Built on Jan 3 2013

Client

Quote:01-08 21:40:15.432 W/System.err( 1977): org.codehaus.jackson.JsonParseException: Invalid UTF-8 middle byte 0x25
01-08 21:40:15.432 W/System.err( 1977): at [Source: libcore.net.http.FixedLengthInputStream@2be34b68; line: 1, column: 1181]
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.JsonParser._constructError(JsonParser.java:943)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.impl.JsonParserBase._reportError(JsonParserBase.java:632)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.impl.Utf8StreamParser._reportInvalidOther(Utf8StreamParser.java:1673)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.impl.Utf8StreamParser._reportInvalidOther(Utf8StreamParser.java:1680)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.impl.Utf8StreamParser._decodeUtf8_2(Utf8StreamParser.java:1469)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.impl.Utf8StreamParser._finishString(Utf8StreamParser.java:960)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.impl.JsonParserBase.getText(JsonParserBase.java:364)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.map.deser.BaseNodeDeserializer.deserializeAny(JsonNodeDeserializer.java:216)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.map.deser.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:185)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.map.deser.BaseNodeDeserializer.deserializeAny(JsonNodeDeserializer.java:210)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.map.deser.BaseNodeDeserializer.deserializeArray(JsonNodeDeserializer.java:199)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.map.deser.BaseNodeDeserializer.deserializeAny(JsonNodeDeserializer.java:213)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.map.deser.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:185)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.map.deser.BaseNodeDeserializer.deserializeAny(JsonNodeDeserializer.java:210)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.map.deser.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:185)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.map.deser.BaseNodeDeserializer.deserializeAny(JsonNodeDeserializer.java:210)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.map.deser.JsonNodeDeserializer.deserialize(JsonNodeDeserializer.java:52)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.map.deser.JsonNodeDeserializer.deserialize(JsonNodeDeserializer.java:13)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.map.ObjectMapper._readValue(ObjectMapper.java:1568)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:711)
01-08 21:40:15.432 W/System.err( 1977): at org.codehaus.jackson.JsonParser.readValueAs(JsonParser.java:879)
01-08 21:40:15.432 W/System.err( 1977): at org.xbmc.jsonrpc.Connection.query(Connection.java:288)
01-08 21:40:15.432 W/System.err( 1977): at org.xbmc.jsonrpc.Connection.getJson(Connection.java:318)
01-08 21:40:15.432 W/System.err( 1977): at org.xbmc.jsonrpc.client.MusicClient.getAlbums(MusicClient.java:345)
01-08 21:40:15.432 W/System.err( 1977): at org.xbmc.jsonrpc.client.MusicClient.getAlbums(MusicClient.java:337)
01-08 21:40:15.432 W/System.err( 1977): at org.xbmc.android.remote.business.MusicManager$2.doRun(MusicManager.java:74)
01-08 21:40:15.432 W/System.err( 1977): at org.xbmc.android.remote.business.Command.run(Command.java:40)
01-08 21:40:15.432 W/System.err( 1977): at android.os.Handler.handleCallback(Handler.java:605)
01-08 21:40:15.432 W/System.err( 1977): at android.os.Handler.dispatchMessage(Handler.java:92)
01-08 21:40:15.432 W/System.err( 1977): at android.os.Looper.loop(Looper.java:137)
01-08 21:40:15.432 W/System.err( 1977): at org.xbmc.android.remote.business.ManagerThread.run(ManagerThread.java:78)
01-08 21:40:15.442 W/System.err( 1977): java.lang.Exception: Weird JSON response, could not parse error.
01-08 21:40:15.442 W/System.err( 1977): at org.xbmc.jsonrpc.Connection.getJson(Connection.java:322)
01-08 21:40:15.442 W/System.err( 1977): at org.xbmc.jsonrpc.client.MusicClient.getAlbums(MusicClient.java:345)
01-08 21:40:15.442 W/System.err( 1977): at org.xbmc.jsonrpc.client.MusicClient.getAlbums(MusicClient.java:337)
01-08 21:40:15.442 W/System.err( 1977): at org.xbmc.android.remote.business.MusicManager$2.doRun(MusicManager.java:74)
01-08 21:40:15.442 W/System.err( 1977): at org.xbmc.android.remote.business.Command.run(Command.java:40)
01-08 21:40:15.442 W/System.err( 1977): at android.os.Handler.handleCallback(Handler.java:605)
01-08 21:40:15.442 W/System.err( 1977): at android.os.Handler.dispatchMessage(Handler.java:92)
01-08 21:40:15.442 W/System.err( 1977): at android.os.Looper.loop(Looper.java:137)
01-08 21:40:15.442 W/System.err( 1977): at org.xbmc.android.remote.business.ManagerThread.run(ManagerThread.java:78)

RE: Download Frodo compatible test version here - ZULan87 - 2013-01-08

I rolled back to Eden today and also the old android app which is at Google Play.
There was too much trouble for me using the app like crashes, hangs, no response on button push, delays etc.
I did however not try XBMC a lot but it seemed to be working fine with IR remote, but the android app needs some more work to it.

Perhaps you should switch to Eden which is much more stable and you could enjoy your time with XBMC.
I will wait for a stable release or really close to it before next upgrade attempt.

I discovered XBMC in December and falled for it instantly.
Thanks XBMC-team for the work you put into this!

RE: Download Frodo compatible test version here - S0lstice9 - 2013-01-10

Working fine on Aiki Xtreamer Frodo RC3..

RE: Download Frodo compatible test version here - jblance - 2013-01-10

(2013-01-08, 23:18)Nat! Wrote: Client

Quote:01-08 21:40:15.432 W/System.err( 1977): org.codehaus.jackson.JsonParseException: Invalid UTF-8 middle byte 0x25

It looks like the UTF-8 parsing has some 'interesting' exclusions - i.e. the above looks to me like a % symbol in the data - which the parser considers an invalid character

(I think, lot of bitwise operations in the parse code...)

Is there a reason that the % character is invalid?

It looks to me like ((d & 0xC0) != 0x080) will limit the valid range of d to 128-191?

My 'hack' is below (in android-xbmcremote/lib-src/org/codehaus/jackson/impl/Utf8StreamParser.java)
Is also in function _decodeUtf8_3fast

Code:
private final int _decodeUtf8_2(int c)

        throws IOException, JsonParseException

    {

        if (_inputPtr >= _inputEnd) {

            loadMoreGuaranteed();

        }

        int d = (int) _inputBuffer[_inputPtr++];

        //% character is OK - but will fail ((d & 0xC0) != 0x080)?

        if (d == 37) {

            return d & 0xFF;

        } //

        if ((d & 0xC0) != 0x080) {

            _reportInvalidOther(d & 0xFF, _inputPtr);

        }

        return ((c & 0x1F) << 6) | (d & 0x3F);

    }

RE: Download Frodo compatible test version here - jblance - 2013-01-11

OK - I've read up on the UTF8 encoding a bit

It does seem like the reply contains incorrectly code data, for example I am getting the above error with data like:
11000011 00100101, however the first 2 bits of the second byte should be 10

Similar problems happen with some 3 byte encodings

So I guess this means it is a problem at the XBMC end?

RE: Download Frodo compatible test version here - Tolriq - 2013-01-11

Yes it is Smile

If on Xbmc Frodo RCx you can just force a rescrape, if on Eden you need to find the wrong NFO or MP3 tag that causes the problem Sad

RE: Download Frodo compatible test version here - jblance - 2013-01-11

(2013-01-11, 07:54)Tolriq Wrote: Yes it is

If on Xbmc Frodo RCx you can just force a rescrape, if on Eden you need to find the wrong NFO or MP3 tag that causes the problem

But shouldn't the encoding be correct even if there is 'bad' data in the information?
If not, wouldn't it be better to ignore anything incorrectly encoded?

RE: Download Frodo compatible test version here - Tolriq - 2013-01-11

As said this have been corrected on Xbmc for Frodo after my reports, they refused to add sanity checks on JSON side and on conversion from Eden.

So the only path left is to rescrape for users during the update to Frodo.

RE: Download Frodo compatible test version here - Nat! - 2013-01-11

For what it's worth. I had the same problem with Yatse now. BUT if I change to Windows for the server with the same NAS holding the identical files, I don't have the problem anymore.

RE: Download Frodo compatible test version here - Futhark - 2013-01-11

I just created an account to thank you for continuing the effort on this app! I banged my head for days trying to get the official one working on my new HTPC build. Found this one, installed it, worked instantly. YOU ROCK!

RE: Download Frodo compatible test version here - Nat! - 2013-01-11

(2013-01-11, 07:50)jblance Wrote: OK - I've read up on the UTF8 encoding a bit

It does seem like the reply contains incorrectly code data, for example I am getting the above error with data like:
11000011 00100101, however the first 2 bits of the second byte should be 10

Similar problems happen with some 3 byte encodings

So I guess this means it is a problem at the XBMC end?

I think the fetching code should be lenient with respect to encoding exceptions. If a tag is malformed in an album list, it shouldn't really abort the whole operation. After all a tag is just a tag.