Android application: taSageTV

[valnar]

Originally Posted by Fonceur

- Setup SageTCPServer as a SageTV v7.0 plugin.

I have a Motorola Droid running 2.1 and will be reformatting my Sage Server to run 7.0 when it is released. As far as I'm concerned, you can drop all backwards compatibility.

[Fonceur]

Originally Posted by valnar

I have a Motorola Droid running 2.1 and will be reformatting my Sage Server to run 7.0 when it is released. As far as I'm concerned, you can drop all backwards compatibility.

Hehe, I wouldn't go that far, as I know those cheap Chinese Android tablets (i.e. < $150) are typically using Android OS 1.6, as are a bunch of phone providers.

EDIT: Of course I just read that the Archos 7 tablet is stuck at 1.5, and that's what I was hoping to get for development...

[Fonceur]

I also forgot to put the video streaming on the "to do" list.

My understanding is that the built in player on the Android platform does not support progressive streams (i.e. the "on the fly" encoding that we need). It seems that the Media Player from BluMediaLab (and apps from others) might be using a work around. So if someone could try it by starting the stream (rtsp), hitting "back" on the black window in taSageTV, and opening the stream (rtsp://MachineIP:8000/stream.sdp) in their player... If that works, I could probably find a way to launch the app myself, or try to get the same work around going. A simple search for "media player stream" comes up with many results, but that's the only one confirmed to have a work around...

[PosterBoy]

Hi.

I am in the process of evaluating tasage. Does it specifically require the original version of the web server or is it compatible with the jetty version that is out now for 7.0 I tried it out a bit last night and could not get it to connect to my server. Does the username have to be something specific? The jetty web site lets you set the username and password, but the tasage app only makes you specify a password.

FYI, I am on a mytouch running 1.6. TMobile swears they will update it to 2.1 any day now, but no cookies (or eclairs as the case may be) yet for me.

Oh one comment on the TASage purchase page here:
http://www.shop.talluscorp.com/produ...&categoryId=12

I was initially turned of by this page because the first thing I saw when quickly hunting for the cost was a price of $79.99. On my second visit a few weeks later I figured out that the cost was actually only $9.99. Yes I realize it was me being stupid and not reading what was right in front of me but shoppers tend to look quickly like that. I am not sure how many people have the same issue, but to me it would make sense to clarify that.

Thanks

Kent

[Fonceur]

Originally Posted by PosterBoy

Does it specifically require the original version of the web server or is it compatible with the jetty version

Actually, it doesn't use either, it's using SageTCPServer... You certainly didn't get that idea from the wiki...

Oh one comment on the TASage purchase page here:

I agree and passed along that comment.

[PosterBoy]

lol looks like I need to pay more attention to what I am reading. I will go through the wiki tonight

Thanks

Kent

[PosterBoy]

Originally Posted by PosterBoy

lol looks like I need to pay more attention to what I am reading. I will go through the wiki tonight

Thanks

Kent

Edit: Ahha. I know where I got the misplace idea it used nielms web server. On the first page of this thread you said it was based on that, and I guess I took more from that than I should have

Kent

[spike5884]

Originally Posted by Fonceur

Hehe, I wouldn't go that far, as I know those cheap Chinese Android tablets (i.e. < $150) are typically using Android OS 1.6, as are a bunch of phone providers.

EDIT: Of course I just read that the Archos 7 tablet is stuck at 1.5, and that's what I was hoping to get for development...

I don't get what is up with all these tablets running old versions of Android. I would think that people would be jumping all over them if they had a more current version. Running an old version, is the main reason I have not pulled out the wallet and bought a few of them.

[Fonceur]

Originally Posted by spike5884

I don't get what is up with all these tablets running old versions of Android.

Same reason most Android phones in Canada are at 1.5, they use customized firmware and pretty much stick with what was available at the start of their development cycle... Then there's the fact that underpowered devices might struggle with Android 2.1+...

[weedydeed]

Originally Posted by Fonceur

I also forgot to put the video streaming on the "to do" list.

My understanding is that the built in player on the Android platform does not support progressive streams (i.e. the "on the fly" encoding that we need). It seems that the Media Player from BluMediaLab (and apps from others) might be using a work around. So if someone could try it by starting the stream (rtsp), hitting "back" on the black window in taSageTV, and opening the stream (rtsp://MachineIP:8000/stream.sdp) in their player... If that works, I could probably find a way to launch the app myself, or try to get the same work around going. A simple search for "media player stream" comes up with many results, but that's the only one confirmed to have a work around...

Hi Fonceur,
Glad to see that the video streaming option is still on your radar. I noticed that the Android 2.2 update includes support for progressive stream playback. Not that it helps now but maybe in the future it may increase your chances of success.

I noticed on the taSageTV support wiki you removed the sections about the vlc streaming entries for the sage.properties file. Are they still required?

[Fonceur]

Originally Posted by weedydeed

I noticed that the Android 2.2 update includes support for progressive stream playback.

Nice, I guess I might need to target multiple versions, which would be a bit of a pain, but...

I noticed on the taSageTV support wiki you removed the sections about the vlc streaming entries for the sage.properties file. Are they still required?

It's not removed, it has always been on the SageTCPServer wiki page...

[Fonceur]

Make sure to update sageTCPServer.jar and taSageTV at the same time, as they both break backward compatibilities... I have essentially cut the middleman in the "sageTCPServer --> memory --> database" and "database --> memory --> display" processes, which should save some of the precious/limited memory... I haven't touched the Music or TV Guide parts yet.

Version 0.84

- Fix: the database file did not have an extension.
- Changed the database structure.
- Reduced the memory usage by getting rid of some buffers.
- Some of the ListView's now use a customized SimpleCursorAdapter.
- Exposed more of the available information.


Known issue

- Accessing the Favorites/Recordings/Schedule while it is connecting and wiping those tables is bad...
- Some weird issue about not liking having the database opened while using it to display the listview items or getting detailed information about a selected item..

[Fonceur]

Version 0.86

- The list of Favorites, Photos, Recordings, Schedule and Videos have gained some sorting and filtering.

Known issue

- The "Albums by genre" is broken...

- Accessing the Favorites/Recordings/Schedule while it is connecting and wiping those tables is bad...

- Some weird issue about not liking having the database opened while using it to display the listview items or getting detailed information about a selected item..

[Fonceur]

Version 0.87

- The list of Recordings, Schedule and Videos can now be filtered by actor.

[Fonceur]

Version .88

- The list of Photos, Recordings and Videos can now be filtered by folder.


While this is not the "file browser" view I had in mind for some of the lists, I think the current implementation should do just fine. Now I just need to do the same for the Music...

[Fonceur]

Version 0.89

- The Music section now mostly use the improved code.

[Fonceur]

Version .90

- Fix: crashed on empty list.
- Added a "Do you really want to quit?" prompt.

[Fonceur]

Version 0.91

- Fix: Big Upcoming recordings list could fill the 8k buffer.
- Fix: Genre was not defined in the Songs table.
- Fix: Some characters like " or % would mess up the filtering. (most likely others still can...)

Known issue

- Accessing the Favorites/Recordings/Schedule while it is connecting and wiping those tables is bad...
- Some weird issue about not liking having the database opened while using it to display the listview items or getting detailed information about a selected item..
- Synchronizing a list while browsing it, might have issues due to the filtering...

[Fonceur]

Version 0.92

- List of less than 100 items (up from 50) can be viewed unfiltered (*) .
- Non alphabetical titles are no longer bunched up under the # filter...

[Fonceur]

Version 0.93

- Fix: the memory leaks related to the database should be fixed...