Android application: taSageTV

[twieder]

Originally Posted by Fonceur

Yes, since I had not read the icon design recommendation before...


Interesting, so someone can simply use the outside address of your.sagetv.domain and if he is within his LAN that will never go out, right?

Exactly. Works great for me.

[Brent]

How is the streaming testing going with this app so far? Anyone have it working successfully yet?

[Fuzzy]

I've had intermittent success with it.. though it's got a lot of the same flaws the web interface does (my HDTV R5000 recordings don't ever start in vlc, and there is no seeking capabilities).

[Fuzzy]

Originally Posted by Fonceur

I was looking at the 1.0 icon design and they were saying 25x25, but for 2.0 they mention 48x48 for the high resolution screen, so that's probably not helping.

http://developer.android.com/intl/de...on_design.html

I don't really plan on creating the low/medium/high resolution icons that they suggest, but if someone else wants to...

Here's what I whipped up... gave it a bit stronger outline, and a slight drop shadow (seems to follow the guidelines, as well as most other notification icons I've see. Also, boosted the contrast up a bit to make it not quite so washed out. There isn't the FULL 2 pixel safe zone on them, but I think I read in the guidelines that the major WEIGHT of the image should be within the zones. All that extends beyond this is some low alpha anti-aliasing, so it should work out (won't really tell until you wrap them into a version to test.. :-)

[Brent]

Guys, I posted a little writeup about the taSageTV app on GeekTonic. Let me know if I missed anything important or misstated anything.

Thanks to Brewston for the extra images I used in the post!

[brewston]

Originally Posted by twieder

If you have a DD-WRT compatible router, just add your Sage boxes to your "Additional DnsMASQ Options" : address=/your.sagetv.domain/192.168.###.###

I suspect this implements the 'loopback' functionality I read about. Doesn't look like router will support DD-WRT - might be time for a new one

[twieder]

Originally Posted by brewston

I suspect this implements the 'loopback' functionality I read about. Doesn't look like router will support DD-WRT - might be time for a new one

Not really a 'loopback'. Your router is your DNS server, getting and redirecting queries to your providers DNS server. You are simply telling DNSMasq to return a hard-coded internal IP for all requests to resolve that name. It is working like a HOSTS file, but for all the devices serviced by the router (and that have the router's IP setup as their DNS server)

[Fonceur]

Originally Posted by Brent

How is the streaming testing going with this app so far? Anyone have it working successfully yet?

Like Fuzzy said, someone else had partial success with it. But that is also why the point 2 in this thread might be useful...

Originally Posted by Fuzzy

Here's what I whipped up...

Those look great! I'll definitely replace the existing one.

Originally Posted by Brent

Let me know if I missed anything important or misstated anything.

That looks good, the only thing is that Tallus is not "my company" as such, I would say more that it's my American distributor and main beta tester...

[Fonceur]

After creating the folders for icons of various resolutions, I realized that this feature is only available on the Android OS version 1.6 and more... Currently, I was targeting the Android OS 1.5 for the greatest possible compatibility, so if people could post the version on their device as well as its resolution, I could see if I need to stick to 1.5 or can target 1.6...

[Zippster]

I havent had time to try your app yet, but am following this thread closely.

Have a Moto Droid running Android 2.1 with stock rez which I believe is 480 x 854


Nice work.

[Fuzzy]

Originally Posted by Fonceur

After creating the folders for icons of various resolutions, I realized that this feature is only available on the Android OS version 1.6 and more... Currently, I was targeting the Android OS 1.5 for the greatest possible compatibility, so if people could post the version on their device as well as its resolution, I could see if I need to stick to 1.5 or can target 1.6...

I'm not positively sure, but I think all devices on market have had upgrades to at least 1.6 available... The few who DON'T have official upgrades, probably never will.. meaning they are already considered end of life. (like the HTC Hero)... That said, the HTC Hero DOES have a community generated 2.1 ROM available...

[Fonceur]

Originally Posted by Fuzzy

I'm not positively sure, but I think all devices on market have had upgrades to at least 1.6 available...

Well, I know that in Canada some phones are stuck on 1.5, and can't be upgraded without rooting them.

Until more people reply, I will stick with 1.5 and just use the 48x48 version of the icons you posted.

[brewston]

Motorola finally released 2.1 for my phone yesterday and taSage still works fine

[CyRex]

Originally Posted by Fuzzy

I'm not positively sure, but I think all devices on market have had upgrades to at least 1.6 available... The few who DON'T have official upgrades, probably never will.. meaning they are already considered end of life. (like the HTC Hero)... That said, the HTC Hero DOES have a community generated 2.1 ROM available...

There has been talk of an update for the HTC Hero to 2.0 (or 2.1?) which should be coming anytime now, although the expected release date keeps getting pushed back. So, I wouldn't say it's considered end of life just yet...

-Dan

[Fuzzy]

Originally Posted by CyRex

There has been talk of an update for the HTC Hero to 2.0 (or 2.1?) which should be coming anytime now, although the expected release date keeps getting pushed back. So, I wouldn't say it's considered end of life just yet...

-Dan

My point was more to the fact that if someone DOES have a phone with 1.5 on it, and if that phone is going to stay at 1.5, there'd be a high chance of that phone being replaced soon... meaning coding for 1.5 is not necessarily a priority.

[amg]

I have a HTC Droid Eris on 1.5, which will hopefully get upgraded soon.

[lewispm]

I followed the wiki installation instructions, but the tcpserver does not start.

nmap shows neilm's webserver running, but not yours.

The log doesn't generate, so I can't post that.

[Fonceur]

Originally Posted by lewispm

I followed the wiki installation instructions, but the tcpserver does not start.

Did you make sure to stop Sage and it's service before changing the sage.properties file? You can double check the full instructions for the SageTCPServer part at:

http://talluscorp.com/mediawiki/inde...=SageTCPServer

or maybe zip and attach your sage.properties file.

[lewispm]

Originally Posted by Fonceur

Did you make sure to stop Sage and it's service before changing the sage.properties file? You can double check the full instructions for the SageTCPServer part at:

http://talluscorp.com/mediawiki/inde...=SageTCPServer

or maybe zip and attach your sage.properties file.

I did stop the service. I disabled the service on the second attempt, but neither seemed to have an effect.

The install defaulted to C:\program files\SageTV\ and the wiki instructions said to install to x\SageTV\SageTV, so I changed it to install there, but when I checked the JARs directory, the installed files weren't there. I reinstalled to C:\program files\SageTV\ per the default, and the installed files were not there either. So I installed to a new directory on my desktop, and copied the files into their locations in the SageTV\SageTV directory.

[Fonceur]

Originally Posted by lewispm

I did stop the service. I disabled the service on the second attempt, but neither seemed to have an effect.

And if you edit sage.properties, you do see the appropriate lines:

debug_logging=TRUE 
load_at_startup_runnable_classes=sagetcpserver.StartServers
sageTCPServer/clients=local.9250,<client2MACID>.<port2>
sageTCPServer/debugOn=true

So I installed to a new directory on my desktop, and copied the files into their locations in the SageTV\SageTV directory.

So the end result is:

c:\Program Files\SageTV\SageTV\JARs\gkusnkick.sagetv.jar
c:\Program Files\SageTV\SageTV\JARs\SageTCPServer.jar