Cannot connect to NextPVR from Samsung S21 Ultra

[DSperber]

Oops. Sorry. Forgot to activate "verbose logging".

I will rerun the test and produce new ZIP of logs. Give me a few minutes.

[DSperber]

Oops. Sorry. Forgot to activate "verbose logging".

I will rerun the test and produce new ZIP of logs. Give me a few minutes.

Ok. Sorry for the confusion.

Here is the new ZIP of logs with "verbose logging" active. I repeated the same tests, first manually logging into 192.168.1.26:8866 with the proper password (which worked), and the second attempting to connect with the NextPVR client app (which still failed).

[sub]

I'd really been hoping to see an S21 connect attempt, because I can get a bit more info on what went wrong with an app login, but unfortunately I can't see any sign of it attempting a login.

[mvallevand]

We see a sign the discovery is working though so I would think that a manual entry isn't even necessary.

Code:

2021-12-27 15:29:32.242    [DEBUG][10]    Received broadcast from 192.168.1.18:35298 : DISCOVER_REQUEST
2021-12-27 15:29:32.242    [DEBUG][10]     (fe80::a97a:6f51:6720:d3a3%14, 192.168.1.18)
2021-12-27 15:29:32.252    [DEBUG][10]     (fe80::dd05:a7f:a5cc:33d8%51, 192.168.1.18)
2021-12-27 15:29:32.252    [DEBUG][10]     (192.168.1.26, 192.168.1.18)
2021-12-27 15:29:32.252    [DEBUG][10]     (192.168.200.2, 192.168.1.18)
2021-12-27 15:29:32.252    [DEBUG][10]    address: 192.168.1.26

The second entry responding on the second NIC from the wrong subnet could be an issue.

It looks like browser access from the S21 is still failing.

Martin

[DSperber]

We see a sign the discovery is working though so I would think that a manual entry isn't even necessary.

Code:

2021-12-27 15:29:32.242    [DEBUG][10]    Received broadcast from 192.168.1.18:35298 : DISCOVER_REQUEST
2021-12-27 15:29:32.242    [DEBUG][10]     (fe80::a97a:6f51:6720:d3a3%14, 192.168.1.18)
2021-12-27 15:29:32.252    [DEBUG][10]     (fe80::dd05:a7f:a5cc:33d8%51, 192.168.1.18)
2021-12-27 15:29:32.252    [DEBUG][10]     (192.168.1.26, 192.168.1.18)
2021-12-27 15:29:32.252    [DEBUG][10]     (192.168.200.2, 192.168.1.18)
2021-12-27 15:29:32.252    [DEBUG][10]    address: 192.168.1.26

The second entry responding on the second NIC from the wrong subnet could be an issue.

It looks like browser access from the S21 is still failing.

Martin

No, although I wonder if that second IP address is part of the problem.

I have a Ceton 6-tuner TV card in that PC. It has a "gateway" IP address (192.168.200.1) that supports its web browser UI. And then its six tuners are each uniquely addressed through a separate common IP address (192.168.200.2) and unique port number.  For example 192.168.200.2:8000 is tuner 1, 192.168.200.2:8001 is tuner 2, etc.

So this 192.168.200.* is a wholly independent and separate local network from 192.168.1.* which is my real Netgear-based LAN. They are unrelated, but both are present for sure. The Ceton driver for the card is what supports access to the gateway and six tuners for purposes of supporting use by Windows Media Center.

If that second-to-last line in your log snippet quoted above is significant, with the first entry being 192.168.200.2 and the second item being 192.168.1.18, therein might be the source of confusion. These are 100% unrelated, and 192.168.200.* should be completely ignored by whatever NextPVR is doing. But unfortunately it actually does show up in Network and Sharing -> Adapters.

[sub]

It looks like browser access from the S21 is still failing.

Yep, I'm pretty certain this is just a case of username/password being wrong, leading to incorrect MD5 hash:

Code:

2021-12-27 15:28:30.622    [ERROR][20]    Web login failed (192.168.1.18)
2021-12-27 15:28:30.622    [VERBOSE][20]    Server: d0edaaa8f26c5640e305ac495d6a9eaa
2021-12-27 15:28:30.622    [VERBOSE][20]    Client: 96ed38ecd99776ab364e97c48886aa7e

[DSperber]

adblink works tethered by USB, and you could always copy the apk to your phone via USB or even with the browser and install that way. 

Martin

Ok. Connected the phone to the PC via USB cable. Then I launched ADBLINK2. Now it actually did go through some preliminary contact with the S21, presenting the ALLOW/DENY popup on the phone screen. I replied ALLOW but ADBLINK2 was involved in an "unauthorized" situation, and asked me to "refresh ADB" or check HELP for unauthorized devices", etc. Even though I had pushed ALLOW on the phone I still needed to work through this.



One of the suggestions in HELP was to toggle the USB Debugging switch within Developer Options on the phone. I did that, and then tried "refresh ADB" again on ADBLINK2. Still not quite past the problems.



Redid things one more time, and now finally ADBLINK2 was happy with the connection to the phone. And in fact the phone showed up automatically, by itself, in "connected devices". So it was going through this USB connection, not IP wireless (as I unsuccessfully had tried earlier). Then I pushed "install APK", navigated to where the NextPVR UI APK was located, and things now looked like this just before I OK'd the install:








I then pushed YES and in a couple of seconds the app was successfully installed on the phone. Sure, I know I'm probably not going to keep it or use it on the phone, but we're just trying to investigate if/how it does or does not successfully connect with NextPVR Server. This is simply to provide more data and clues, in trying to figure out why the regular NextPVR Android app (from sub) does NOT connect.



So remember, the phone is currently USB-connected to the PC. And now I launch the NextPVR UI app. It launches, connects properly to NextPVR Server, and even presents the TV Guide perfectly when I tap on the top item in the Menu. Yes, not everything after that worked, for example as was predicted it is hard to tap onto a TV Guide cell to play that channel, and actually make it work. But eventually I was able to succeed a few times. I didn't actually get the TV picture/sound to display and play but I did have the surrounding information indicating that I'd selected that channel. And I was able to use the BACK button to go back to the TV Guide presentation.



However again, I didn't really care about or have expectations of it actually working. I only wanted to produce a verbose LOG piece that would show how connection worked or didn't. And as things happened, it DID CONNECT JUST FINE.



So, here is the log snippet right after I pushed the "verbose" button on ABOUT. I then launched NextPVR UI from the phone, and within a few seconds it connected successfully and presented the main Menu screen. I then tapped on TV Guide, and that presented properly as well. I then went BACK, and then EXIT. Pretty sure that's all I did (i.e. I didn't try to play any channel during this test shot).

I'm attaching a ZIP of the verbose log snippet, that hopefully clearly shows how it connected to NextPVR Server (again with the phone still USB-connected to the PC).



I don't know there would be anything different if the phone is no longer USB-connected but instead tried to connect through WiFi (as I was trying to do with the regular Android NextPVR client app from sub. I will give that a try.



Also, I don't know what might happen if the phone is USB-connected and I try launching the regular Android NextPVR app. I will also give that a try.



But for new, the newest piece of information for this topic is that NextPVR UI actually does launch properly on the S21, does connect to the NextPVR Server (unclear if that connection is via IP or USB), and does successfully present the Menu as well as the TV Guide. And I am able to EXIT.



Hopefully this provides some useful new clues regarding the original actual problem, which is that NextPVR client app doesn't succeed in connecting... perhaps confused by the 192.168.200.* second network on my machine.

[DSperber]

Some kind of problem with the previous post.

Here is that ZIP snippet of the log file.

[DSperber]

Ok. I have now disconnected the USB cable between phone and PC. So it's back purely WiFi connected to the network.

And then I once again launched NextPVR UI, to see if/how it connects successfully or not to NExtPVR Server on the PC... but purely via WiFi. So this is the same configuration as for the regular Android NextPVR app attempting to connect... but failing.

And I can report that NextPVR UI CONNECTS SUCCESSFULLY VIA WIFI!! There obviously must be some difference in the connection methods between uidroid and the official NextPVR Android client app from sub, which fails.

So, here is the failing log snippet re-attempting (still unsuccessfully) from sub's NextPVR Android client app:

Code:

2021-12-28 00:09:22.622    [DEBUG][28]    method=system.verbose
2021-12-28 00:09:22.622    [DEBUG][28]    parameters:
2021-12-28 00:09:22.622    [DEBUG][28]       method: system.verbose
2021-12-28 00:09:22.622    [DEBUG][28]       format: json
2021-12-28 00:09:22.632    [DEBUG][28]       sid: 9d579444-3609-4436-a01b-3b30ca9238c6
2021-12-28 00:09:22.632    [DEBUG][28]       client_ip: 127.0.0.1
2021-12-28 00:09:22.632    [DEBUG][28]       user_agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:95.0) Gecko/20100101 Firefox/95.0
2021-12-28 00:09:22.632    [DEBUG][28]       host_callback: ...
2021-12-28 00:09:22.632    [INFO][28]    Verbose logging now enabled
2021-12-28 00:09:22.632    [DEBUG][28]    {"stat":"ok"}

2021-12-28 00:09:22.902    [VERBOSE][8]    STATUS: pending 0, recording 0
2021-12-28 00:09:32.356    [DEBUG][10]    Received broadcast from 192.168.1.10:40185 : DISCOVER_REQUEST
2021-12-28 00:09:32.356    [DEBUG][10]     (fe80::a97a:6f51:6720:d3a3%14, 192.168.1.10)
2021-12-28 00:09:32.356    [DEBUG][10]     (fe80::dd05:a7f:a5cc:33d8%51, 192.168.1.10)
2021-12-28 00:09:32.356    [DEBUG][10]     (192.168.1.26, 192.168.1.10)
2021-12-28 00:09:32.356    [DEBUG][10]     (192.168.200.2, 192.168.1.10)
2021-12-28 00:09:32.356    [DEBUG][10]    address: 192.168.1.26
2021-12-28 00:09:32.356    [DEBUG][10]    Waiting for broadcast
2021-12-28 00:10:16.070    [DEBUG][1]    CaptureSource.LoadAll()
2021-12-28 00:10:16.085    [DEBUG][1]    No C:\Users\Public\NPVR-Data\scripts\PreShutdown.bat
2021-12-28 00:10:16.085    [INFO][1]    Flushing logs
2021-12-28 00:10:16.085    [DEBUG][2]    Unloading...
2021-12-28 00:10:16.085    [INFO][2]    Flushing logs

I just noticed that the IP address of the S21 has changed to now be 192.168.1.10 instead of its earlier 192.168.1.18 as it was earlier. But that shouldn't matter. I just happen not to have any "address reservation" for the phone's MAC address so it's just getting DHCP-assigned an IP address from the router. But it's identical to what NextPVR UI is working with, so again this should be irrelevant.

And in contrast, attached is a ZIP of the log snippet from NextPVR UI and its successful WiFi connection via WiFi from the identical 192.168.1.10 IP address. I then went from Menu to TV Guide, and BACK to terminate (sorry, I forgot to gracefully EXIT). So forget about the bottom of the snippet. Just look at the top, where connection seems to be 100% perfect and successful from the same S21 phone.

So there is clearly something fundamentally different and significant between the connection methods used by uidroid vs. sub's Android app. One works, and the other fails.

[mvallevand]

Great I expect sub's Android client is not extracting the port and other information from discovery properly.

Some notes for your reference

- uidroid will work via network, tethered or not.
- I forgot that tap and mouse click to play are only in my pre-release, you would need to use a Watch button or Live TV from the main menu
- I think adblink offers a keypad for controlling the device.
- swipe left is the same as DPAD back.
- there is no worry about graceful exit in uidroid and the Roku. They are designed so you can hit Home and restart a new session where you left off if you relaunch. However this session will not work if DHCP changes your IP.
- the full zipped log NextPVR creates is way better than a snippet.

Martin