|
SageTV Clients Development This forum is for discussions relating to SageTV Open Source Clients Development. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
Android Miniclient - problem with screen image
I have 2 SageTV servers - both version 9.1.7 - one in Windows 7x64 and the other in a VirtualBox Linux guest (Linux Mint 18). Both are using Java 1.8.0_151.
From my android Oneplus 2 phone on my own network, the miniclient connects fine and the image is great on the Linux side. On the Windows side, however, the opening screen image splits into 4 sections - each one a copy - divided vertically. (e.g., the SageTV menu on the left repeats 3 more times). Once within on the menu options, it's ok. A similar mess happens when I try to connect using LocatorID - username/password repeated 4 times and the screen image a jumble of overlays making it impossible to login. I'm attaching 3 images - the good Linux, the bad Windows and the bad placehifter login. Has anyone any idea how I can begin to try to fix this? |
#2
|
||||
|
||||
Is the Windows VM considered to be on the same network as well, or, do you need a placeshifter user to connect to it. I honestly can't figure out a reason why it would be doing what you are showing.
__________________
Batch Metadata Tools (User Guides) - SageTV App (Android) - SageTV Plex Channel - My Other Android Apps - sagex-api wrappers - Google+ - Phoenix Renamer Downloads SageTV V9 | Android MiniClient |
#3
|
|||
|
|||
Are all the UI/skin options for the clients set the same on both servers? How about trying to copy the contents of one properties file (on the good server) to the correct properties file for the client on the Windows system?
__________________
Bruno Twisted Melon Inc. While you're clicking, check out my Mini Theater custom build. |
#4
|
|||
|
|||
Thanks for the idea - I had tried that with no luck. But your suggestion made me think of trying different user interfaces and I finally had luck with Diamond instead of standard. I get the opening screen with no repeats - a great improvement! so thanks!
I had managed earlier to get in with LocatorID through the messy login screen - I could see the word LOGIN so tried pressing that and it asks for username and then password so I got in. Interestingly, since I started the Diamond UI, I no longer get the placeshifter login screen???? The other puzzle is that I seem to be always connecting to the Windows version using the Linux LocatorID but I just don't know enough about networking and routers to get that straightened out. At least now I can use this so massive progress. Thanks again for your suggestion, |
#5
|
|||
|
|||
Quote:
|
#6
|
|||
|
|||
I have been trying all the configurations I've read about for the past few days. The internet IP address you mention - is that the same as the one I use to access the router? If so, I had forwarded port 31099 a couple of days ago to the specific address of my Linux server (as shown in an app - Fing - that I have on my phone). But it still goes to the windows version. Is that because Linux is in a vBox within Windows?
I have a vpn service and I've tried with that off (changing a set DNS servier within IPv4 properties to an automatic DNS server address). Neither way seems to make much difference. I don't know if this is at all relevant but within the config of both servers, I am unable to automatically configure the placeshifter location - always get the messages that no UPnP device found Iit is on in my router). Within windows it tells me to manually forward 31099 to the address I'd forwarded it to already. Within Linux it says to forward it to IP 0.0.0.0. Probably none of this will help diagnosing my problems but I thought I'd write all the things that just don't make sense. |
#7
|
|||
|
|||
Quote:
The "Internet" (external) IP is the one seen by the outside world. Use a browser on the server machine and Google for "what is my IP". That is the one the locator service needs to use and/or you need to use to connect. I suspect both the Windows host and the Linux VM will report the same external IP. You likely need to setup port forwarding in Vbox as well to pass the Host traffic on to the Linux VM. Read here. |
#8
|
|||
|
|||
Many, many thanks to Stuckless (for his help with my current problem), wnjj (for his help and patience in explaining networks and IP etc to me) and to TwistedMelon for his suggestion. I am now able to access my Linux server using the LocatorID. The windows image is still messed up but I don't need it now that I have the Linux version - the problem had been my lack of knowledge of networking, routers and port forwarding.
Love the miniclient! thanks again |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Android MiniClient 1.2.9 | stuckless | SageTV Clients Development | 53 | 04-16-2018 07:30 AM |
New problem showing up only on Android Miniclient | sacrament055 | SageTV Clients Development | 9 | 03-01-2017 12:31 PM |
Android MiniClient On Screen Guide question | crarbo1 | SageTV Clients Development | 7 | 02-13-2017 11:13 AM |
Android Miniclient Screen Orientation | snorth87 | SageTV Clients Development | 3 | 08-02-2016 08:57 AM |
[Android MiniClient] Need a better start screen | stuckless | SageTV Clients Development | 16 | 01-29-2016 01:55 PM |