I have 2 android phones, a Nexus 4, and a HTC Desire HD
On the Desire HD, qt4 is working and qt5 is not working. if i start qt5, i only get a black screen
I have to say, i have a custom rom on the Desire HD
On the Nexus 4, qt4 is working, but qt5 is not completly working. in qt5 none of my media gets displayed, or qt5 crashed when i press the media button. and i have some rotating issues with qt5
If i play media while the qt5 orbiter is running on my phone, qt5 crashes, and i cannot start it again until media playback has finished
I've tried several times to reinstall the skins, and running the script from langstonball.com
I love the smokey skin on my nexus!!!
For me, the media browsing is terrible on my nexus, because for every episode of a TV show i get a hit in the first screen, with just the title of the show, if i click that, it seems i get a randomly generated number, if i click that, i get into a season folder for that tv show.
I would like to see the Viewed/Unviewed options added, is this a possibility?
This would already help a lot.
imho the performance could be better, perhaps it is an option to throttle the data based on the processing speed of the device?
I found a strange feature, that if you use the back button in media browsing, it jump back to (for me) a random location
If i need to somehow make logging, or screenshots, tell me how i can make them, and i will)))
Keep up the good work!
Qt5 is going back to the barn. it seems to only work on selected devices, and this kinda annoys me
The media grid should see some evolution to being more useful in the next week.
*The numbers you see when selecting by program are the attribute numbers of the season's. I need to translate that to the actual db value.
Back button is something i should have fixed. trying to decide what it should be used for. I did many experiments on loading and its a matter of how fast the android device is. Im still researching this area but right now it runs on a loop. I throttle that loop so the gui doesnt freeze because even though the processing is happening in another thread, depending on the processor it can still slow the gui down.
Its something thats been tricky since day one since we have a more free flowing implementation as opposed to the more static legacy one.
ill see about the viewed /unviewed