Android application: taSageTV

[planetc]

Yay! Looking really impressive, tweaks to the ui have really bought it on. No problem syncing it now.

[pjwerdna]

Unfortuantely even with the latest version I'm still aving sync issues.

(log files from server and andriod attached)

Im getting unterminated object errors so I suspect it never finishes updating the database. Certainly it always starts updating as soon as I start it.

Oh! and the "thread exiting with uncaught exception (group=0x40144760)" at the end of the android log is me pressing back after looking at the detail of a recording. Might be related to the previous errors though.

[Fonceur]

Originally Posted by pjwerdna

Unfortuantely even with the latest version I'm still aving sync issues.

Well, I can sync my simulator and cheap tablet just fine with data from your home. What seems to happen is that your tablet piles up packets, then throws away the overflow and wonders why it doesn't have full messages to parse... ;

[Fonceur]

Originally Posted by pjwerdna

Unfortuantely even with the latest version I'm still aving sync issues.

Try those versions:

2k buffer: http://dl.dropbox.com/u/408295/TaSag...2/TASageTV.apk
8k buffer: http://dl.dropbox.com/u/408295/TaSag...b/TASageTV.apk


I tried to limit the buffer, see if that does anything and send me the log.

[pjwerdna]

Originally Posted by Fonceur

What seems to happen is that your tablet piles up packets, then throws away the overflow and wonders why it doesn't have full messages to parse... ;

Yeah that doesnt really suprise me.

I was on Andriod 3.0.1, but "upgraded" to 3.1 a few days ago. It was supposed to be faster and more stable. This is not entirely true! Wifi disconnects and transfers very slowly, cant transfer files using bluetooth anymore. Flash video stutters more than it used to as well. So Buffering problems arent a big supprise.

Might see if I can downgrade to 3.0.1 again.

[pjwerdna]

Originally Posted by Fonceur

Try those versions:

2k buffer: http://dl.dropbox.com/u/408295/TaSag...2/TASageTV.apk
8k buffer: http://dl.dropbox.com/u/408295/TaSag...b/TASageTV.apk

I tried to limit the buffer, see if that does anything and send me the log.

The 2K one sort of worked. Well it does work, but keeping the tablet awake is a problem as the sync takes so long!

The 8K one seems to sync very well.

I think you might want to add a bit of code to keep the tablet awake until the database has synced though. With the 8K buffer it looks to be taking just over a minute to sync and I dont have much TV etc on this server. The default timeout for the tablet is a course exactly 1 minute!

[Fonceur]

Originally Posted by pjwerdna

I think you might want to add a bit of code to keep the tablet awake until the database has synced though.

Which is why it's recommended to disable the sleep mode for long sync... As I've said before, the problem with me disabling it in the app is that there might not be a clear signal as to when to re-enable it...

[Fonceur]

Version 1.92

- Set the TCP socket's incoming buffer to 8k.
- More database tweaks.
- Switched off a lot of the logging.


I'm not sure that I can do much better than this as far as adding data to the database...

[planetc]

I just realised that the remote doesn't fit on the tab screen, and is no longer scrollable. Don't know when it changed as I haven't used it for some time.
Also something strange going on with the refresh on the TV screen, it seems to recount every time I return to the screen, but doesn't finish the update each time, leaving me with missing recordings and favourites etc.

[Fonceur]

Originally Posted by planetc

I just realised that the remote doesn't fit on the tab screen, and is no longer scrollable. Don't know when it changed as I haven't used it for some time.

Hmm, sounds like your device is considered a large screen or such... What is its resolution and size?

Also something strange going on with the refresh on the TV screen, it seems to recount every time I return to the screen, but doesn't finish the update each time, leaving me with missing recordings and favourites etc.

It means you lost connection and it had to reconnect, get all the lists again and such... If you wait for the resync to happen, you will be fine...

[Fonceur]

Version 1.93

- Replaced the images on the Keyboard page.
- Merged the Status and Keyboard page.

[planetc]

Originally Posted by Fonceur

Hmm, sounds like your device is considered a large screen or such... What is its resolution and size?

1024x600 7" screen

Originally Posted by Fonceur

It means you lost connection and it had to reconnect, get all the lists again and such... If you wait for the resync to happen, you will be fine...

...it counts everything up ok first visit to the screen in any session, but seems to clear itself and recount, but only partially or very very slowly, when going back from any visit to the individual screens within the tv section. Exiting the app and restarting allows the count to complete.

OK, so now noted that I have started to lose the connection and I get a cross in the top left corner, so what is happening makes sense, gonna roll back and see what I have.

[Fonceur]

Originally Posted by planetc

1024x600 7" screen

Hmm, it fits on my 800x600, strange that it wouldn't fit on bigger... Any chance you can post a screenshot? Might be the combination of large screen and high resolution...

OK, so now noted that I have started to lose the connection and I get a cross in the top left corner, so what is happening makes sense, gonna roll back and see what I have.

Right, I get the feeling that I'm killing the connection when switching screens, which should only happen when the application itself is closed...

[pjwerdna]

Tried to delete a recording and got a force close, it did delete the recording though.

Logs from both ends attached.

The android log also seems to have lots of database errors in it but I didnt notice any effect in the GUI.

[Fonceur]

Originally Posted by pjwerdna

Tried to delete a recording and got a force close, it did delete the recording though.

Haven't tried to do that in a bit, so something might be broken.

The android log also seems to have lots of database errors in it but I didnt notice any effect in the GUI.

The Schedule error I already noticed and I think I fixed them. The others were the same buffer issue.

[planetc]

Screenshots requested, it's never fitted properly, but I could scroll with the early versions.

[Fonceur]

Originally Posted by planetc

Screenshots requested, it's never fitted properly, but I could scroll with the early versions.

Hmm, maybe it's because I'm not allowing the xlarge screen mode, so you're getting some odd compatibility mode...

[planetc]

Been playing, the recount of the content on the 'TV' screen doesn't happen when on 3g, only on wifi. First opening of the screen is fine every time, it is only when I go back after visiting the next level of menus.

[Fonceur]

Version 1.94

- No longer disconnect when the main activity is killed.
- Try to automatically reconnect from more than just the main activity.
- Fix: Was not coming back cleanly from deleting a file.


I guess my main activity has gotten fatter, and people are running more background tasks, making it more likely for it getting killed. Unfortunately getting killed was also taking down the TCP service, not a good idea... So now you should experience less connection drop and as a bonus more automatic reconnections should be happening.

[planetc]

Just when I thought it was all sorted AND looking really good, the last update broke something, I have no albums populating, songs are there, just not the albums. Also noted get FCs on opening the app intermittently, always seems to open ok second attempt though.