Black Screen - Android 9?

[TheKenR]

Hi Martin,

I decided to try out your Android UI client on an older Android 9 4k MBOX. Installation went fine but when I launch it all I get is a black screen. Here is the logcat from when I launched it.

https://thekenr.com/temp/uidroid.log

Do you see anything odd there? Is Android 9 supported?

This looks a little odd to me. I'm not sure what it's "discovering" but it doesn't seem to find anything.

Code:

08-05 12:21:18.227  7900  7900 D uidroid-discovery: discovery start
08-05 12:21:18.228  7900  7900 D uidroid-discovery: about to wait to receive
08-05 12:21:23.234  7900  7900 D uidroid-discovery: discovery end

Thanks
K

[mvallevand]

I see the same thing that you are, discovery isn't working. Is your NextPVR server on 192.168.2.xx?

It works on the on MiBox if that is what you are using but the remote is a simple DPAD.

Martin

[TheKenR]

I see the same thing that you are, discovery isn't working.  Is your NextPVR server on 192.168.2.xx?

It works on the on MiBox if that is what you are using but the remote is a simple DPAD.

Martin

Yes, NextPVR is running on 192.168.2.200. I checked my firewall and I don't see anything being blocked. I'm not sure how discovery works. Is there a specific port it uses?

K

[mvallevand]

UDP 16891

When you have the black screen can you long press the DPAD centre and get settings?

Martin

[TheKenR]

UDP 16891
When you have the black screen can you long press the DPAD centre and get settings?
Martin

Yes, holding the DPAD worked - once. From there it allowed me to manually setup the server IPort and PIN. Once I did that it worked perfectly!

Then I decided to do more testing so I deleted app data. Now I can't get the settings screen to come back up. Even after uninstalling and re-installing holding the centre button does not bring up the settings.

Regarding the discovery function, I think it's on my server side. The server side has port 16891 open (by NextPVR-Server service) and the Android app is able to make contact. Here's a tcpdump of the data packets being being transferred between the Android app and NextPVR server when I open the app and get the black screen. It looks like the Android app is making contact OK but the NextPVR server process is not responding. It's using the broadcast IP address but I suspect the broadcast IP is somehow mapped to my VPN network rather than my LAN. One clue is the NextPVR server logs have nothing so it seems NextPVR is not receiving the broadcast. I'll work on this angle. 

Code:

ken@ubuntu:~$ netstat -an | grep 16891
udp        0      0 0.0.0.0:16891          0.0.0.0:*

ken@ubuntu:~$ sudo tcpdump -vA src 192.168.2.24 or dst 192.168.2.24
tcpdump: listening on enp4s0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
14:49:11.917482 IP (tos 0x0, ttl 64, id 43275, offset 0, flags [DF], proto UDP (17), length 50)
    192.168.2.24.38833 > 255.255.255.255.16891: UDP, length 22
E..2..@.@.............A.....NextPVR, where you at?

Thanks
K

[mvallevand]

I can't explain why it doesn't work now. You would need to wait until the black screen and hold it down. I have so many servers I don't test the no server scenario much.

Martin

[TheKenR]

I can't explain why it doesn't work now.  You would need to wait until the black screen and hold it down.  I have so many servers I don't test the no server scenario much.

Martin

Yeah, I don't understand that either. I'll poke around a little more. 

Can you tell me where the server IP address is stored once I enter it (or it's discovered)? Assuming it's not a binary file I could just manually edit the file.

On your next update it might be a good idea to open the settings screen by default if the discovery function does not succeed. For some reason on my network it's not being routed to the server even though the devices are on the same network. A quick test using netcat results in the broadcast IP NOT reaching NextPVR (although it shows succeeded) but when I use the direct IP it works like a charm even from the Android box. So something is a little wonky with my 255.255.255.255 broadcast IP. Likely something with my VPN or router.

ken@ubuntu:/etc/network$ sudo nc -b -vz -u 255.255.255.255 16891
Connection to 255.255.255.255 16891 port [udp/*] succeeded! <-- nope!

ken@ubuntu:/etc/network$ sudo nc -b -vz -u 192.168.2.200 16891
Connection to 192.168.2.200 16891 port [udp/*] succeeded! <-- Yup, NextPVR sees the connection, see below.

Code:

2023-08-05 17:46:51.428    [INFO][182]    Flushing logs
2023-08-05 17:54:40.148    [DEBUG][14]    Received broadcast from 192.168.2.200:41347 : X
2023-08-05 17:54:40.148    [DEBUG][14]     (127.0.1.1, 192.168.2.200)
2023-08-05 17:54:40.148    [DEBUG][14]     (192.168.2.200, 192.168.2.200)
2023-08-05 17:54:40.148    [DEBUG][14]     (100.64.100.6, 192.168.2.200)
2023-08-05 17:54:40.148    [DEBUG][14]    address: 192.168.2.200
2023-08-05 17:54:40.148    [DEBUG][14]    Waiting for broadcast
2023-08-05 17:54:40.148    [DEBUG][14]    Received broadcast from 192.168.2.200:41347 : X
2023-08-05 17:54:40.148    [DEBUG][14]     (127.0.1.1, 192.168.2.200)
2023-08-05 17:54:40.148    [DEBUG][14]     (192.168.2.200, 192.168.2.200)
2023-08-05 17:54:40.148    [DEBUG][14]     (100.64.100.6, 192.168.2.200)
2023-08-05 17:54:40.148    [DEBUG][14]    address: 192.168.2.200
2023-08-05 17:54:40.148    [DEBUG][14]    Waiting for broadcast
2023-08-05 17:54:41.148    [DEBUG][14]    Received broadcast from 192.168.2.200:41347 : X
2023-08-05 17:54:41.148    [DEBUG][14]     (127.0.1.1, 192.168.2.200)
2023-08-05 17:54:41.148    [DEBUG][14]     (192.168.2.200, 192.168.2.200)
2023-08-05 17:54:41.148    [DEBUG][14]     (100.64.100.6, 192.168.2.200)
2023-08-05 17:54:41.148    [DEBUG][14]    address: 192.168.2.200
2023-08-05 17:54:41.148    [DEBUG][14]    Waiting for broadcast
2023-08-05 17:54:42.148    [DEBUG][14]    Received broadcast from 192.168.2.200:41347 : X
2023-08-05 17:54:42.148    [DEBUG][14]     (127.0.1.1, 192.168.2.200)
2023-08-05 17:54:42.148    [DEBUG][14]     (192.168.2.200, 192.168.2.200)
2023-08-05 17:54:42.148    [DEBUG][14]     (100.64.100.6, 192.168.2.200)
2023-08-05 17:54:42.148    [DEBUG][14]    address: 192.168.2.200
2023-08-05 17:54:42.148    [DEBUG][14]    Waiting for broadcast
2023-08-05 17:54:43.148    [DEBUG][14]    Received broadcast from 192.168.2.200:41347 : X
2023-08-05 17:54:43.149    [DEBUG][14]     (127.0.1.1, 192.168.2.200)
2023-08-05 17:54:43.149    [DEBUG][14]     (192.168.2.200, 192.168.2.200)
2023-08-05 17:54:43.149    [DEBUG][14]     (100.64.100.6, 192.168.2.200)
2023-08-05 17:54:43.149    [DEBUG][14]    address: 192.168.2.200
2023-08-05 17:54:43.149    [DEBUG][14]    Waiting for broadcast

[mvallevand]

The settings screen is supposed to open if no servers are found, that is what I need to check. Edit I checked on my Mibox and not opening the settings is an Android 9 issue.

If it doesn't connect there won't be a settings file to edit even if you could access the Android file system.

If you disable your VPN and allow uidroid to connect the setting should be saved and you could enable your VPN again.

Do things work on your end if this was just a sub broadcast sudo nc -b -vz -u 192.168.2.255 16891

Martin