Android application: taSageTV

[planetc]

I have just run through getting a v7 setup running, gonna take some getting used to but that is another story. Once I have tested with phoenix I'll feedback but family have just returned home so my window has closed for the time being

[Fonceur]

Regarding the thumbnails, double checking on my SageTV server, I see that I have the Phoenix API installed, but not the Phoenix Fanart as such, maybe the later doesn't have a dependency on the first... I also have the sagex-api and sagex-services. I assume that the rest are just dependencies from those.

As far as providing images for pre-7 versions, my hands are kinda tied up, as I'm not responsible for those plugins... I could have included the image serving in SageTCPServer, but first I would have needed to rewrite the TCP handling in it, and decided not to reinvent the wheel for now.

[planetc]

Originally Posted by Fonceur

Regarding the thumbnails, double checking on my SageTV server, I see that I have the Phoenix API installed, but not the Phoenix Fanart as such, maybe the later doesn't have a dependency on the first... I also have the sagex-api and sagex-services. I assume that the rest are just dependencies from those.

Just been through to make sure I have all those plugins and fanart is being utilised on the clients in the house although I still have no images in TaSage, which seems strange.

Originally Posted by Fonceur

As far as providing images for pre-7 versions, my hands are kinda tied up, as I'm not responsible for those plugins... I could have included the image serving in SageTCPServer, but first I would have needed to rewrite the TCP handling in it, and decided not to reinvent the wheel for now.

The thread is running within the pre-7 customisation area of the forum, and the reading I did suggested it was written for pre-7 and considered compatible with v7 rather than the other way around. It's not the end of the world, I can live without images. Your software does what I wanted it to do, it just would have been nice to have it fully functional.

[Fonceur]

Originally Posted by planetc

The thread is running within the pre-7 customisation area of the forum, and the reading I did suggested it was written for pre-7 and considered compatible with v7 rather than the other way around.

Which it was until about 3 weeks ago, when I started to add new features not available in the pre-SageTV 7 plugins... It is still fully compatible with older versions of SageTV, though new features might not work.

[planetc]

Originally Posted by Fonceur

Which it was until about 3 weeks ago, when I started to add new features not available in the pre-SageTV 7 plugins... It is still fully compatible with older versions of SageTV, though new features might not work.

fair enough

[Fonceur]

Version 1.47

- Use the wifi network state instead of screen_on as trigger to reconnect.
- Fix: was not properly refreshing the connection state on wake.
- Fix: TV guide could crash when it had old data but no connection.

[baudfather]

Just curious if anyone's been able to get streaming working on a Galaxy S (i9000)? The remote works fine, VLC starts streaming, then the Galaxy media player says it can't play the file. So close!

[planetc]

Originally Posted by baudfather

Just curious if anyone's been able to get streaming working on a Galaxy S (i9000)? The remote works fine, VLC starts streaming, then the Galaxy media player says it can't play the file. So close!

The tab does the same thing the first time you hit stream, if I wait a few seconds then hit it again it plays fine. It is just because the stream is still firing up on the server and isn't available yet.

[planetc]

I got the images working! A little poking and digging required but it goes like this.....the default install of TaSage on the handset had the Sage Remote API on port 8080, I had no reason to change it and went with default options throughout so assumed it would be correct. When I realised the default install of Jetty was on port 8000, I changed it to match it to the Jetty server and presto!

[Fonceur]

Originally Posted by planetc

I got the images working!

Good!

When I realised the default install of Jetty was on port 8000, I changed it to match it to the Jetty server and presto!

I think the default port conflicted with either the VLC streaming port or the BTV web server.

[wit713]

I also got the images to work by connecting through my WiFi connection for the server. When I user my 3G connection, they do not show but I probably have the port blocked. Is 8000 the default port used to fetch the images? I am assuming you use different port than 9250 which is for the server.

I think I found the answer to my own question. I was looking at the server setting and I just saw you added another setting called "Sage Remote API" on port 8080. I am assuming this is what is being used to pull all the images. This port is blocked when I am on 3G so I believe this why no images.

[Fonceur]

Originally Posted by wit713

Is 8000 the default port used to fetch the images? I am assuming you use different port than 9250 which is for the server.

Right, the images are fetched through jetty/sagex/phoenix on port 8000 or so, while SageTCPServer uses a different set of ports.

[planetc]

Having looked, I have the web interface on 8080. This was the default setting as installed for on the phone to fetch the images. It worked but was really slow loading data until I opened port 8080 so I am guessing data was loading from the API elements of the web interface but it wasn't set up for images.
The jetty install defaulted to 8000 so I changed the setting on the phone to match it, obviously opening a port to match. Hope that makes sense.

[batwater]

Originally Posted by Fonceur

Right, the images are fetched through jetty/sagex/phoenix on port 8000 or so, while SageTCPServer uses a different set of ports.

Is Jetty installed separately? Also do the images load on demand or during a sync? Still not getting images after adjusting port to 8000 on client.

Thanks

[Fonceur]

Version 1.48

- Added a configurable delay before launching the streaming application.
- The Sagex port setting has been replaced by the Jetty web server port (8000).


If you had Jetty on a port different than 8000, you will need to set it back on the Settings screen.

On the Galaxy tab and such, you might need to increase the delay, if you are getting a message that the video can't be played. This basically would be the case if the SageTV Server is slow in starting the stream from VLC and that the media player is not waiting long enough.

[Fonceur]

Originally Posted by batwater

Is Jetty installed separately?

It's a dependency of the other required components like Sagex.

Also do the images load on demand or during a sync?

They are on demand and cached.

Still not getting images after adjusting port to 8000 on client.

Make sure that you have updated versions of Sagex-services and Phoenix API. Also make sure that you are not using port 8000 for the VLC streaming (i.e. rtsp.8000 in sage.properties).

[Fonceur]

Originally Posted by planetc

When I realised the default install of Jetty was on port 8000, I changed it to match it to the Jetty server and presto!

Is the default really 8000? I am confused, I am seeing 8080 as the default in the Mobile streaming thread... Or maybe it got changed between version, and since you had an old installation you had it at 8000...

[wit713]

Originally Posted by Fonceur

Is the default really 8000? I am confused, I am seeing 8080 as the default in the Mobile streaming thread... Or maybe it got changed between version, and since you had an old installation you had it at 8000...

Fonceur, I just updated and the images were not showing again. I then changed the port back to 8080 and it worked. I installed phoenix and jetty about a month ago and have not tweaked any settings for it so I would think 8080 is the default.

[Fonceur]

Originally Posted by wit713

I installed phoenix and jetty about a month ago and have not tweaked any settings for it so I would think 8080 is the default.

That's what I thought too, but planetc got me wondering.

[sic0048]

v48 won't open. It immediately force closes. I haven't had that problem with any other version.

I can send a log, but I've misplaced your email address.

EDIT - a reboot seems to have fixed my problem.

PS - the streaming delay seems to have fixed my streaming issue! This is awesome! Previously I was only able to stream over WAN, now I can stream over the 3g connection too!