• 1
  • 215
  • 216
  • 217(current)
  • 218
  • 219
  • 259
Android Yatse: Full featured Kodi Remote (Widgets, Streaming, Offline media, ...)
Yatse 4.3.5 is published
  • New first run for Unlocked users with Quick Restore
  • New option choose Media Center on Send To
  • Host status in all Host lists
  • New host wizard / edit host
  • New search Youtube / Google in file mode
  • Bug fixes / Performance improvement

Do not forget to rate the application and G+1.
If you like this, please buy the Unlocker to ensure continued development.

Facebook : http://on.fb.me/13QNm5B
Twitter : http://bit.ly/XzZGaz
Google+ : http://bit.ly/1e2iS5z
Yatse is now available on Amazon App Store :

http://www.amazon.com/Yatse-the-XBMC-Kod..._1?ie=UTF8
http://www.amazon.fr/Yatse-the-XBMC-Kodi..._1?ie=UTF8
http://www.amazon.co.uk/Yatse-the-XBMC-K..._1?ie=UTF8
http://www.amazon.ca/Yatse-the-XBMC-Kodi..._1?ie=UTF8
http://www.amazon.co.jp/Yatse-the-XBMC-K..._1?ie=UTF8
http://www.amazon.com.au/Yatse-the-XBMC-..._1?ie=UTF8
http://www.amazon.com.br/Yatse-the-XBMC-..._1?ie=UTF8
http://www.amazon.de/Yatse-the-XBMC-Kodi..._1?ie=UTF8
http://www.amazon.es/Yatse-the-XBMC-Kodi..._1?ie=UTF8
http://www.amazon.it/Yatse-the-XBMC-Kodi..._1?ie=UTF8

Remember that you need to install from your Amazon country shop.
My htpc slows to a crawl during theses hits...any chance you can limit them?

Code:
00:37:28 T:940   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:28 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:28 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:29 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:29 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:29 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:29 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:31 T:940   DEBUG: webserver: request received for /jsonrpc
00:37:31 T:940   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:31 T:436   DEBUG: webserver: request received for /jsonrpc
00:37:31 T:436   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:32 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:32 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:32 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:32 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:34 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:34 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:34 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:34 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:35 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:35 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:36 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:36 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:37 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:37 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:37 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:37 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:39 T:436   DEBUG: webserver: request received for /jsonrpc
00:37:39 T:436   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:39 T:436   DEBUG: webserver: request received for /jsonrpc
00:37:39 T:436   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:40 T:436   DEBUG: webserver: request received for /jsonrpc
00:37:40 T:436   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:40 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:40 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:42 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:42 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:42 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:42 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:43 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:43 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:43 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:43 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:45 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:45 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:45 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:45 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:46 T:916   DEBUG: webserver: request received for /jsonrpc
00:37:46 T:916   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:46 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:46 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:48 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:48 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:48 T:436   DEBUG: webserver: request received for /jsonrpc
00:37:48 T:436   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:49 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:49 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:49 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:49 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:51 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:51 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:51 T:436   DEBUG: webserver: request received for /jsonrpc
00:37:51 T:436   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:53 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:53 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:53 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:53 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:54 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:54 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:54 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:54 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:56 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:56 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:56 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:56 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:57 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:57 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
00:37:57 T:380   DEBUG: webserver: request received for /jsonrpc
00:37:57 T:380   DEBUG: JSONRPC: Incoming request: [{"jsonrpc":"2.0","id":0,"method":"Player.GetActivePlayers"},{"jsonrpc":"2.0","id":1,"method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]
Image Lunatixz - Kodi / Beta repository
Image PseudoTV - Forum | Website | Youtube | Help?
Hey you again Wink

I'll need Yatse logs and real full logs, as those logs are not possible with one Yatse.

And as already explained I'd like to see real data that shows that Yatse is the root problem. 7 devices on with Yatse toward a slow rpi have only 3% impact on cpu.
And AFAIK you are on a more powerful Windows.
I have two issues with how the music library is sorted in Yatse - specifically the Album list.

The option of ignoring articles ("The") does not seem to have any effect. In the screen shot below you can see that The Beatles are sorted below Tame Impala, under T instead of B.

Additionally, the option "Sort by artist then year" seems to sort albums by reverse chronologically order (newer albums before older). This might be the intended function, but according to my intuition, sorting by year would put older albums before newer ones. This is also the way it works in XBMC (after adding the option "<albumssortbyartistanddate>true</albumssortbyartistanddate> " to advancedsettings.xml). It is a little confusing to have my albums sorted differently in Yatse and XBMC.


Image

Thanks for the great app, by the way! If you want me to report these things somewhere else (I see you have a redmine issue tracker here: http://yatse.leetzone.org/redmine/projec...get/issues), just let me know.
(2014-10-22, 08:43)Tolriq Wrote: Hey you again Wink

I'll need Yatse logs and real full logs, as those logs are not possible with one Yatse.

And as already explained I'd like to see real data that shows that Yatse is the root problem. 7 devices on with Yatse toward a slow rpi have only 3% impact on cpu.
And AFAIK you are on a more powerful Windows.

LOL, i've said this before... your work on this project is great! I've been a donor to your projects back when it was just a windows app!! So trust me when I say i'm a fan, not here to cause you drama Smile

Those logs are real, unedited.. I'm sure you have not designed Yatse to hammer the json like that... I have two androids in the household that control one instance of XBMC. Those logs are from exhaustive efforts to find out why out of the blue xbmc started slowing down again... I had this problem a year ago... with the same conclusion... Your polling is coming at too soon a rate, causing blocks of log entries like the one I submitted.

Now I know they are from your app, Because If I drop the connection between yatse and my HTPC they stop.. and XBMC runs smooth Smile

What should the interval of those queries be? I'm sure they weren't designed to hammer like it is...
Image Lunatixz - Kodi / Beta repository
Image PseudoTV - Forum | Website | Youtube | Help?
@eirki : Well yes ignore article does not work for the artist sorting in albums view, only direct listings. This is nearly impossible to achieve correctly with currents api and multiple artists per albums / songs and everything and all difference between Eden and Frodo and Gotham Sad

I hope I can find better ways when I drop Eden but nothing before.

For the Year sorting well maybe XBMC changed but this was added in this order because it was asked by users in this order (And if I remember correctly this was by an XBMC team member so I'd suppose he asked to have the same behavior Sad )

@Lunatixz : Well as I said those queries should not have any impact on XBMC since getting pure static data, there's something wrong with your XBMC if those queries does trigger such big problems.
Anyway Yatse pools often when the interface is visible but can't pool 2 times at the same times, so in those logs you had 2 Yatse opened on 2 different phones targeting the same XBMC. (This is very far from normal use) but anyway even in that case it should have near 0 impact on your XBMC.

60% of Yatse users are slow rpi ones, lot's have multiple devices and no one ever complained of a slow XBMC or impact, and as a rpi users and normal Windows too with tons of tests devices I can't generate XBMC slowdown.

I wonder what you call slow, but maybe you have too many addons that does block the HTTP threads (limited to 4) and having 2 Yatse using 2 threads they start to have problems and kills your XBMC.
Or something else.

You may want to check with http://technet.microsoft.com/en-us/sysin...96645.aspx for example what cause troubles on your XBMC and everything about threads. (You can see the thread IDs in your logs with the T:xxx if I remember correctly.
(2014-10-22, 22:28)Tolriq Wrote: @eirki : Well yes ignore article does not work for the artist sorting in albums view, only direct listings. This is nearly impossible to achieve correctly with currents api and multiple artists per albums / songs and everything and all difference between Eden and Frodo and Gotham Sad

I hope I can find better ways when I drop Eden but nothing before.

For the Year sorting well maybe XBMC changed but this was added in this order because it was asked by users in this order (And if I remember correctly this was by an XBMC team member so I'd suppose he asked to have the same behavior Sad )

@Lunatixz : Well as I said those queries should not have any impact on XBMC since getting pure static data, there's something wrong with your XBMC if those queries does trigger such big problems.
Anyway Yatse pools often when the interface is visible but can't pool 2 times at the same times, so in those logs you had 2 Yatse opened on 2 different phones targeting the same XBMC. (This is very far from normal use) but anyway even in that case it should have near 0 impact on your XBMC.

60% of Yatse users are slow rpi ones, lot's have multiple devices and no one ever complained of a slow XBMC or impact, and as a rpi users and normal Windows too with tons of tests devices I can't generate XBMC slowdown.

I wonder what you call slow, but maybe you have too many addons that does block the HTTP threads (limited to 4) and having 2 Yatse using 2 threads they start to have problems and kills your XBMC.
Or something else.

You may want to check with http://technet.microsoft.com/en-us/sysin...96645.aspx for example what cause troubles on your XBMC and everything about threads. (You can see the thread IDs in your logs with the T:xxx if I remember correctly.

Thanks for the information... but my test were done on a clean xbmc setup... to rule out any external problems...
Image Lunatixz - Kodi / Beta repository
Image PseudoTV - Forum | Website | Youtube | Help?
Well as previous time, you refuse to show me anything, and details and anything that could help.

Yatse is near 1 million users with 400k active at least per month so if they were such impact I would have some troubles Wink

So as I said I can't reproduce on 3 XBMC devices with 7 to 9 devices hammering them, so until you accept that the problem might be on your side and that you'll need to give me information and full logs with thread analysis and anything, I can't help to find the problem.
(2014-10-23, 08:15)Tolriq Wrote: Well as previous time, you refuse to show me anything, and details and anything that could help.

Yatse is near 1 million users with 400k active at least per month so if they were such impact I would have some troubles Wink

So as I said I can't reproduce on 3 XBMC devices with 7 to 9 devices hammering them, so until you accept that the problem might be on your side and that you'll need to give me information and full logs with thread analysis and anything, I can't help to find the problem.

LOL, refuse? such a strong word...

What logs do you need? can you at least tell me the time interval between those json requests? so I can figure out if the pattern i'm seeing is normal or not?

I understand your plugin is awesome and popular... not sure that makes it bug proof?
Image Lunatixz - Kodi / Beta repository
Image PseudoTV - Forum | Website | Youtube | Help?
There's no bug in the extract from xbmc logs you shows. And we are not talking about a bug, we are talking about a problem on your very specific installation.
If a simple JSON query that return static data make your HTPC slow (Still waiting that you describe slow, interface, playback some addons no more work, ...) then it would do the same on all other users or the problem is on your XBMC / machine.

By default Yatse pull every 1,5 sec when inside a screen that need up to date info.

I need as asked full logs from Yatse / XBMC + use the tools I gave you to have precise information about the http threads linked to Yatse to have information.

And any useful information to help you understand fix the problem.
I have an android, newest Yatse, openelec.
I can't seem to get Native player to work on my phone. I have mx player installed. I can use other apps to stream to my phone but not Yatse. What an I doing wrong? I just get a can't play video error.

Do I need the stream plugin anymore? I've tried with and without. I thought the latest version said I didn't need it, but I don't see the info now.
http://yatse.leetzone.org/redmine/projec...wiki/Debug for logs Smile

But first be sure to have read the point 1 of the FAQ : http://yatse.leetzone.org/redmine/projec...t/wiki/FAQ
(2014-10-22, 22:28)Tolriq Wrote: @eirki : Well yes ignore article does not work for the artist sorting in albums view, only direct listings. This is nearly impossible to achieve correctly with currents api and multiple artists per albums / songs and everything and all difference between Eden and Frodo and Gotham Sad

I hope I can find better ways when I drop Eden but nothing before.

For the Year sorting well maybe XBMC changed but this was added in this order because it was asked by users in this order (And if I remember correctly this was by an XBMC team member so I'd suppose he asked to have the same behavior Sad )

Thanks for the response! If you ever add an option to specify which direction to chronologically sort after year, I would be might grateful.
Great job again with the app! I got it working on my kindle. It'll be cool once I can get a full version to buy.

I have paid version on my androids... Is there a way to have the cached images load when not on my WiFi? If I leave home, my pics are blank. I like checking my collection sometimes, and text base isn't cutting it. I did a full cache scan, but nothing shows until I hit my WiFi again. Ideas?
  • 1
  • 215
  • 216
  • 217(current)
  • 218
  • 219
  • 259

Logout Mark Read Team Forum Stats Members Help
Yatse: Full featured Kodi Remote (Widgets, Streaming, Offline media, ...)24