Android application: taSageTV

[wit713]

Originally Posted by Fonceur

You don't, that was my bad...


I'd suggest opening the Mirage beta app and trying to stream a known .m3u8... Maybe try from the web browser too...


Version 2.17

- Fix: The Stream button visibility was linked to the Server instead of Client state.

Thanks Fonceur. That worked.

I will try playing with the Mirage. I really did not look at it that closely.

[twollman]

Originally Posted by cjalphonso

The status screen reports the correct info of what is playing after doing as you requested. Almost seems as if it is reading properly but not sending commands properly.

I am experiencing the same problem on my Motorola xoom tablet running honeycomb 3.2.

Fonceur,

Do I enable logging in tcpserver? Where is the file saved and what would it look like?

As you can tell I am clueless. But I am willing to try.

[Fonceur]

Originally Posted by twollman

Do I enable logging in tcpserver? Where is the file saved and what would it look like?

From the wiki:

2) Set Debug to true in the plugin interface and in the 
Detailed settings/Advanced.

If things are working well, feel free to keep it as false. However, if you 
are asked for the sage log, then set this to true, restart sage to 
reproduce the problem, and send the logfile. The file will have the 
name "sagetv_0.txt" and it will be located in the SageTV\SageTV folder.

You should also install an Android log collector app (like aLogCat) and post the result.

[twollman]

Originally Posted by Fonceur

Which makes no sense... So I'll need access to the logs to figure out where the issue is...

I have a log file created by alogcat. Post an email address and I will send it. I tried to attach it but it wouldn't let me browse files on my tablet.

Edit:

I copied the file to my laptop. File attached

The SageTV log is too big to upload. I can make it smaller or send it to you.

[Fonceur]

Originally Posted by twollman

The SageTV log is too big to upload. I can make it smaller or send it to you.

If you zip it, it should fit.

EDIT: OK, I see the problem: "android.os.NetworkOnMainThreadException", I need to make my network call differently...

[Fonceur]

Version 2.18

- Fix: On Android 3.x network operations are forbidden on the main thread.


Since people could potentially perform long network operations on the main thread, Google's solution is to prevent them all regardless, nice...

[twollman]

Success! The remote works again.

I get a consistent force close if I try to bring up the program guide.

Edit:

Rebooting the tablet seems to have cured it.

Thanks again for being so responsive.

[Fonceur]

Version 2.19

- Fix: On android 3.x, the Program guide had some database issues...


I do plan on targeting Android 3.2, but implementing the Fragment and ActionBar to work on Android 1.6 to 3.2, on phone/tablet is a bit tricky on such a big app... I am currently getting the hang of it on smaller projects.

[rdefino]

Quick question. I've been poking around in the thread.

Is this app worth the $29.

Especially since it seems like sagetv will no longer be develop any more...maybe.

Thanks for any Thoughts

[Fonceur]

Originally Posted by rdefino

Is this app worth the $29.

First of all, the Android version is 30% cheaper than the iOS version, as Apple/Google aren't taking a cut...

Especially since it seems like sagetv will no longer be develop any more...maybe.

Well, the development of the consumer version of BeyondTV basically stopped 2-3 years ago, but people still use it just fine...

[Fonceur]

As you might have noticed, I have put a free version on The Market which only includes the Remote control part... Being a smaller/simpler application, it does make it easier to test the Android 3.x stuff and such. As part of it I redid the layout, so on an Android phone it should match the iPhone/iPod Touch more closely. While I did modify the tablet layout too, it's not meant to match the iPad one...

Since the various screen size/density is a pain on Android, I would need some people to test the following build: (deleted)

On an Android phone in portrait mode, the top part can be swiped left/right and basically give access to 3 screens, instead of the 2 crammed one in the current TaSageTV version. I haven't modified the landscape version, but might before it gets put on The Market...

On a tablet, it should make a slightly better use of the screen than the current TaSageTV version.

So if you could post the Android device (and resolution if known), and if everything is fine or if there are issues. For example, previously some users did not get access to all the buttons, which is mostly what I'm trying to avoid... Those changes will make it into TaSageTV soon, so better test this now to avoid having it broken later...

EDIT: OK, got enough testing done...

[pjwerdna]

Just tried taSageTVRemote...

Screen shots attached for an ASUS Transformer (10.1 inch, 1280 x 720 screen)

Works fine and looks ok.

Button and screen size are about the same as the full version. i.e. would be easier to use if it was slightly bigger. Not necessarily fullscreen as the buttons would be a bit far apart I think, maybe 10% or 20%.

[Fonceur]

Originally Posted by pjwerdna

Screen shots attached for an ASUS Transformer (10.1 inch, 1280 x 720 screen)

Thanks, that's exactly the kind of thing I was looking for! I was also seeing that in the emulator, but wasn't sure if it was already using the double sized images or not.

Button and screen size are about the same as the full version. i.e. would be easier to use if it was slightly bigger.

Actually, once I start using fragments, the full version will most likely have other things like playback Status or such in that empty space...

[Fonceur]

Version 2.20

- Now targeting Android OS 3.2.
- Now using the Action Bar.
- No longer compiling against JAVA 1.5 (!?!).


It shouldn't make much difference on Android phones or pre-3.x tablets. On 3.x tablets, now you get access to the "over flow" menu... It might be worth it retrying the streaming on 3.x tablets, to see if it helps any...

[Fonceur]

Version 2.21

- Now using the same Remote control fragments as TaSageTVRemote.
- Moved the Remote control's Text entry field.
- Fix: Was not actively killing the services in all cases.


That last fix is the reason why the application might have been crashing the first launch after an update... Of course it will only fix future installations, this one might still crash on the initial launch...

[Fonceur]

Version 2.22

- Now using a "Dashboard" for the navigation.
- Moved the Recordings to Media center...
- Hide the unimplemented Searches...

[pjwerdna]

HI

Just tried 2.22...

Kind of like the new look.

However I cant connect anymore. THis is partly because I reconfigured the client and extender settings on the server and got it wrong and partly because tasagetv is just not showing server settings anymore to match what I think I put on the server.

See attached

[Fonceur]

Originally Posted by pjwerdna

tasagetv is just not showing server settings anymore to match what I think I put on the server.

Actually, the settings are white on white, if you look carefully, you can see your host as 192.168.2.4...

[Fonceur]

Version 2.23

- Fix: On some devices, text fields could be white on white.

[Fonceur]

Version 2.24

- Added the item's count to the "Dashboard".