Android application: taSageTV

[Fonceur]

Originally Posted by 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.

OK, I get those too...

[Fonceur]

Version 1.95

- Fix: Would crash when relaunching the app.

[Fonceur]

Version 1.96

- No longer locks the UI thread launching a sync/update/wipe.
- Fix: Syncing the list of Albums was broken.

[planetc]

Just thought I'd add a thankyou for the time you have put into this and for your prompt responses to issues. Bit by bit TaSage has become a useful addition to my system. I would never have asked for any specific feature, but you seem to have developed the app to address most of my wishes anyway. Here's to hoping the pending Gingerbread update for the tab opens up the facility to ff/rew, at which point it will move from useful into the world of essential for me.

[pjwerdna]

Hi

Just tried 1.96 and unfortunately Im still getting Force closes when I delete a TV recording. (Log attached)

It does delete the file though, so it looks the same as it was before the fix although it may be differant internally to taSageTV of course.

Is there any other diagnostic I can get for all these Force Closes on Android 3.1?

[Fonceur]

Originally Posted by pjwerdna

Just tried 1.96 and unfortunately Im still getting Force closes when I delete a TV recording. (Log attached)

I see it in the log, but there isn't much error message to go with...

It does delete the file though, so it looks the same as it was before the fix although it may be differant internally to taSageTV of course.

It is, as the other one was also crashing for me, but not this one.

Is there any other diagnostic I can get for all these Force Closes on Android 3.1?

Those logs are probably as good as it goes... As I move more commands to back processes, it should get better...

[Fonceur]

Version 1.97

- Fix: Some options did not work from the Detailed view.
- Remapped the various forward/rewind keys.
- Removed an unnecessary delay when deleting files.


The skip back 2 and skip forward 2 were not mapped, now it should be consistent with the iOS version...

[The Truth]

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.

I think my buffer is too small? is it possible to make the buffer bigger? I see my server placeshift to the droid then the video starts playing... then it will stop placeshifting for a second or 2...then start up again, this is where the video on the droid will freeze for a second... I think the buffer needs to be bigger or something has to happen so the file keeps placeshifting on the Server...

IS any of this posssible?? it is possible for the server to placeshift the whole video to a "streaming file (buffer)" without pausing or stopping due to connection? Or just for it to never stop placeshifting??? i think my problem is that my server stops placeshifting every few seconds which is causing pauses on play back.. I tried the 2k buffer tasagetv and the 8k buffer tasagetv, the 2k made the pauses closer together, but shorter. the 8k just a little further apart.

I would love to see if a 1024k buffer is possible? again I HAVE NO IDEA WHAT IM TALKING ABOUT... I would like to just see if i can get this to work better... Thanks.


WAIT!!! I think i might have something???? changing the file caching?? maybe this will help me!!!!?

[Fonceur]

Originally Posted by The Truth

I think my buffer is too small?

That was the TCP/IP buffer for the metadata, which has absolutely nothing to do with the video streaming... What you want to be looking at is either the various VLC profiles or fixed bit rates Mirage streams...

[Fonceur]

Version 1.98

- Fix: Was not updating the count when removing a Recording or Schedule.
- Fix: There were some metadata parsing issues.
- Updated the Remote control's buttons.
- Built and targeting Android OS 2.3.1.


So planetc if you could post screenshots of your Remote control page with this version... I am hoping that by enabling extra large screen in Android OS 2.3.1 that solves your issue...

For users running Android OS 2.3+, that might mean the return of the "forced close" for operations taking more than 16 ms... So if you could describe when it happens and post some Android logs please...

That was a first shot at updating the Remote control, the next will be to move the custom buttons from Status and rearrange them...

[pjwerdna]

Hi

Just tested 1.98 and Im not getting any new force closes

Like the new remote buttons, but they are getting a bit small now. Ful size images attached for info

[Fonceur]

Originally Posted by pjwerdna

Just tested 1.98 and Im not getting any new force closes

So you're only getting the old crashes or you're not getting any?

Like the new remote buttons, but they are getting a bit small now. Ful size images attached for info

Right, I'll need to make an actual extra large version. Would spacing out the buttons some more be enough or do I need to use buttons twice the size?

[pjwerdna]

Originally Posted by Fonceur

So you're only getting the old crashes or you're not getting any?

Just the same old ones unfortunately or should that be fortunately

Originally Posted by Fonceur

Right, I'll need to make an actual extra large version. Would spacing out the buttons some more be enough or do I need to use buttons twice the size?

Erm! Not sure twice the size would fit! Maybe one third bigger?
Problem is they really need to scale based on the screen resolution. My screen is 1280 horizontally, but I know some honeycomb devices are only 1024.

Some applications Ive found scale quite nicely others dont scale at all, keeping the display to a phone sized area of the screen.

[planetc]

Still chopping a chunk off? This is still on 2.2 I might add, 2.3 has not been released yet but is due soon (officially for my tab at least)

[Fonceur]

Originally Posted by pjwerdna

Just the same old ones unfortunately or should that be fortunately

Right, most likely issues with filling the lists from the database, just need to figure out how to do it properly...

Some applications Ive found scale quite nicely others dont scale at all, keeping the display to a phone sized area of the screen.

The multi-resolution support is painful with Android... At least with the iPod/iPhone you just create a 320x480 version, drop some image@2x for Retina Display and you're done. For the iPad, you get your landscape and portrait and that's it. For Android, you get 4 screen sizes and 4 dpi sizes, and have to try and make them work for various combo...

[Fonceur]

Originally Posted by planetc

Still chopping a chunk off? This is still on 2.2 I might add, 2.3 has not been released yet but is due soon

OK, I see the problem. It's using the double size images, but you need 1.5 for hdpi, the 2.0 is for xhdpi...

[pjwerdna]

FYI I get the same kind of cuts off on my android ish phone running 2.2.1. Although I seem to get a differant key layout!

Top left - direction keys
bottom left voluem, channel
top right : power, below is rewind, pause and a button I can see.

Think its the previous screen layout (copy attached from the tablet not the phone. Sorry cant to screen shots on the phone)

[Fonceur]

Version 1.99

- Fix: Was using 2x images when it should have been 1.5x...


EDIT: I have updated version 1.99 with more images, so if you have installed a version within the first 2.5 hours of the original message, you should update...

[Fonceur]

Version 2.00

- Fix: Deleted Favorites were increasing the count and not actually removed.
- Fix: The text on the Status page was never set visible...

[planetc]

Er, I still have a remote that doesn't fit the screen, doesn't look any different to the last change to me, and before you ask, I did the update a minute or so before posting this message. :-)