Cannot connect to NextPVR from Samsung S21 Ultra

[DSperber]

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.

Just following up on this.

Now that it's been proven that NextPVR UI can absolutely be run on the S21 and also can connect perfectly to NextPVR Server running on the PC, with associated verbose log provided above, isn't this sufficient to give you the clues you've been looking for to know what is different in your own Android NextPVR client app that is preventing connection from happening on the S21?

Here is that portion of the "successful" log from uidroid:

Code:

2021-12-27 23:54:07.787    [DEBUG][47]    Got request [127.0.0.1]: /services/service (system.verbose)
2021-12-27 23:54:07.787    [DEBUG][47]    method=system.verbose
2021-12-27 23:54:07.787    [DEBUG][47]    parameters:
2021-12-27 23:54:07.787    [DEBUG][47]       method: system.verbose
2021-12-27 23:54:07.787    [DEBUG][47]       format: json
2021-12-27 23:54:07.787    [DEBUG][47]       sid: 9d579444-3609-4436-a01b-3b30ca9238c6
2021-12-27 23:54:07.787    [DEBUG][47]       client_ip: 127.0.0.1
2021-12-27 23:54:07.787    [DEBUG][47]       user_agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:95.0) Gecko/20100101 Firefox/95.0
2021-12-27 23:54:07.787    [DEBUG][47]       host_callback: ...
2021-12-27 23:54:07.797    [INFO][47]    Verbose logging now enabled
2021-12-27 23:54:07.797    [DEBUG][47]    {"stat":"ok"}

2021-12-27 23:54:07.807    [VERBOSE][8]    STATUS: pending 0, recording 0
2021-12-27 23:54:24.303    [DEBUG][10]    Received broadcast from 192.168.1.10:41963 : Android UI Client
2021-12-27 23:54:24.303    [DEBUG][10]     (fe80::a97a:6f51:6720:d3a3%14, 192.168.1.10)
2021-12-27 23:54:24.303    [DEBUG][10]     (fe80::dd05:a7f:a5cc:33d8%51, 192.168.1.10)
2021-12-27 23:54:24.303    [DEBUG][10]     (192.168.1.26, 192.168.1.10)
2021-12-27 23:54:24.303    [DEBUG][10]     (192.168.200.2, 192.168.1.10)
2021-12-27 23:54:24.303    [DEBUG][10]    address: 192.168.1.26
2021-12-27 23:54:24.303    [DEBUG][10]    Waiting for broadcast
2021-12-27 23:54:29.388    [DEBUG][43]    Got request [192.168.1.10]: /service (session.initiate)
2021-12-27 23:54:29.388    [DEBUG][43]    method=session.initiate
2021-12-27 23:54:29.388    [DEBUG][43]    parameters:
2021-12-27 23:54:29.388    [DEBUG][43]       method: session.initiate
2021-12-27 23:54:29.388    [DEBUG][43]       ver: 1.0
2021-12-27 23:54:29.404    [DEBUG][43]       device: uidroid
2021-12-27 23:54:29.404    [DEBUG][43]       client: c78076715f5e8f33
2021-12-27 23:54:29.404    [DEBUG][43]       format: json
2021-12-27 23:54:29.404    [DEBUG][43]       client_ip: 192.168.1.10
2021-12-27 23:54:29.404    [DEBUG][43]       user_agent: Dalvik/2.1.0 (Linux; U; Android 12; SM-G998U Build/SP1A.210812.016)
2021-12-27 23:54:29.404    [DEBUG][43]       host_callback: ...
2021-12-27 23:54:29.404    [DEBUG][43]       sid: default
2021-12-27 23:54:29.404    [INFO][43]    InitiateSession (device=uidroid)
2021-12-27 23:54:29.404    [DEBUG][43]    SetSessionObject(b2775c016f9845f594647d76480679db, 'child', NON-null)
2021-12-27 23:54:29.404    [DEBUG][43]    Device: uidroid
2021-12-27 23:54:29.404    [DEBUG][43]    SetSessionObject(b2775c016f9845f594647d76480679db, 'child', NON-null)
2021-12-27 23:54:29.404    [DEBUG][43]    {"sid":"b2775c016f9845f594647d76480679db","salt":"2f63d6f3-931e-4a9b-ace5-c297552536f6"}

2021-12-27 23:54:29.482    [DEBUG][43]    Got request [192.168.1.10]: /service (session.login)
2021-12-27 23:54:29.482    [DEBUG][43]    method=session.login
2021-12-27 23:54:29.482    [DEBUG][43]    parameters:
2021-12-27 23:54:29.482    [DEBUG][43]       method: session.login
2021-12-27 23:54:29.482    [DEBUG][43]       md5: 31f18f99a1224c275584821eb6140c2f
2021-12-27 23:54:29.482    [DEBUG][43]       client: c78076715f5e8f33
2021-12-27 23:54:29.482    [DEBUG][43]       format: json
2021-12-27 23:54:29.482    [DEBUG][43]       sid: b2775c016f9845f594647d76480679db
2021-12-27 23:54:29.482    [DEBUG][43]       client_ip: 192.168.1.10
2021-12-27 23:54:29.482    [DEBUG][43]       user_agent: Dalvik/2.1.0 (Linux; U; Android 12; SM-G998U Build/SP1A.210812.016)
2021-12-27 23:54:29.482    [DEBUG][43]       host_callback: ...
2021-12-27 23:54:29.482    [INFO][43]    LoginSession(sid = b2775c016f9845f594647d76480679db)
2021-12-27 23:54:29.513    [DEBUG][43]    [gmWFGYFLh/33ZUJUzOl9yvmRQoYvDM9cid23ccXY/g8oa0bUc9gO/Ja7lsd6XeMiyTCM328YG5VZUOITQWdL9cPxMEjn0g/eqliGltv2BATmCxKGEdk4UMg9z6gNEmWxGZM9+pr8YjsPW+x0fxzWSxMEiDy9OCJRSvb6Iap8W0+zOVqGdtOfgc0zo54xF7zIgHXWdEZXk8mp7UVA/hmQES7K6PKtj9UcmmdmWfLhGQcBupt9WzpcwVS/csL3DAZkVpNEcKTfJ0nDSOAyvKRuuA//O3DOdi6amRFAxYt8Oqpl6L+Nrn947uaziE8R59wk1XOYyaDxJtk7CyosUkQ1HKUBAcYTrT/8mTPyWylRu3Kx7K3on4DEtRH5qCnKBWMkAfJlq2MR0rIqu4aqa85YyXpqHg2WkQVDWRmspFtpLQTvr8h19X76KWdcL/2ObcbfD51uxvCV5aNGzsbjLe3erw==]
2021-12-27 23:54:29.513    [DEBUG][43]    [JxG+B9BzaT2pTyBbAgpYHDefjt0E2PeYRqcw0Gl/e1VX7PS0A6ml7O9O/Yz3Tzj6YzHbiF8/hsoh7wn+sj/MJVzbe3RQBVI70qOQ9+vCM0EFRtXjr9yx7+snJIMHe8RfYMejJuwt7gVOXOJls3xdgjpvcOTg/1G/NWKB5Ax1QJt6GOrk7fjVbhbvb7zYLHgjMG7FNm1Py19CfajPE4H2SIAi3f9t5pPFlmO1NzIKLmDMrYLgh1QSa6T52Y1ka2Biv+9O6xikX8MuU+7WYkhbiirqbU5G+j5HV/uoG92buohJoIoblMB0AXu/om5drA+SaRV33r378JivkFVN6kRx9onFd5cwCHyFOth6n/BWwbziOJMHdYHQzDVbDIOqrM5p7ytEDUM8IU8DRBfMvrODxfuNN9XOvKNbNl6l7/Io+3E=]
2021-12-27 23:54:29.513    [DEBUG][43]    [fY6ZyNJHuTVVaeTO9xgUXXeAVLK/LI7N6hjUJxvVqNCLtuiylHcNrl/4SInJHn7WlUh8qwlz8AX15QLR1aYqF9eBxSWJdoS3jbfXcJdNzHgwJmOjk0yRYwQSujFCFCebCjBjQ//LL0pNowV7inMALGk5G63trycZCOTWGgQDdr4Qn6HA1bcZ9eYHVmEPCfgmydFpNL+iLDzW/DGkX5YbV/0DGdtzuw/sAbebpNdOdX2OBwb3PMUlSc0XVX8nycvg9MYZSH1yVpXeSOF2LKIskrlUf3qh3VKkWN9ym0ItjjcK40aWuIKTXQMyTINH7vbj5dQGni4LoUh/kvAPNOzDPdpuBxGA8HAiVpYdcexUnn9aTaXBmeNWPR8VaRAvUfRTdm38TvN1VTfDJf3cBJHDfnxcmWxzxNRI776feiesrjY=]
2021-12-27 23:54:29.513    [DEBUG][43]    {
"stat": "ok","sid": "b2775c016f9845f594647d76480679db","allow_settings":false,"allow_watch":true,"allow_schedule":true,"allow_delete":tru

And in contrast, here is the failing log from NextPVR client which seems to just hang up at "waiting for broadcast":

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

The key difference is that uidroid also shows "waiting for broadcast", but actually gets a response:

Code:

2021-12-27 23:54:24.303    [DEBUG][10]    Waiting for broadcast
2021-12-27 23:54:29.388    [DEBUG][43]    Got request [192.168.1.10]: /service (session.initiate)
2021-12-27 23:54:29.388    [DEBUG][43]    method=session.initiate

[sub]

No, it's not clear to me why the session request never comes from your phone.

[DSperber]

No, it's not clear to me why the session request never comes from your phone.

How about adding some special diagnostic debug code for the client app that can put out somehow/somewhere the data that might help reveal the solution to this mystery? You can build a custom APK for this test, I will install it on my S21, and provide you with its output. I'm more than willing to be the laboratory.

And again, the "giant clue" is that uidroid seems to have the required technique correctly built into its own design. The exact same S21 behaves exactly as expected as far as uidroid being able to connect successfully to the very same NextPVR server, whereas your NextPVR must have something significant that is different to be unsuccessful doing the exact same thing with the exact same NextPVR server.

Can you two compare notes on this common logic, to identify the difference?

[sub]

Did you try manually adding the server?

[DSperber]

Did you try manually adding the server?

Sure. Numerous times I've pushed the "add server" button and then entered 192.168.1.26:8866 in the first field, and my PIN in the second field and then OK.

Doesn't do anything other than present "connecting" for a short time, which disappears. And no connection. I can than again tap on the IP address (192.168.1.26) which is onscreen, the "connecting" appears, and then disappears. Still no connection.

Just gave it one more try, without activating verbose logging first, just to see at a high level what's occurring. Once again the "contact attempt" arrives (DISCOVER_REQUEST) from 192.168.1.18:50361 (I'm back at my original location, connecting WiFi through a different access point), which then leads to a "waiting for broadcast" that is never satisfied.

Code:

2021-12-29 05:01:21.571    [DEBUG][10]    Received broadcast from 192.168.1.18:50361 : DISCOVER_REQUEST
2021-12-29 05:01:21.571    [DEBUG][10]     (fe80::a97a:6f51:6720:d3a3%14, 192.168.1.18)
2021-12-29 05:01:21.587    [DEBUG][10]     (fe80::dd05:a7f:a5cc:33d8%51, 192.168.1.18)
2021-12-29 05:01:21.587    [DEBUG][10]     (192.168.1.26, 192.168.1.18)
2021-12-29 05:01:21.587    [DEBUG][10]     (192.168.200.2, 192.168.1.18)
2021-12-29 05:01:21.587    [DEBUG][10]    address: 192.168.1.26
2021-12-29 05:01:21.587    [DEBUG][10]    Waiting for broadcast
2021-12-29 05:07:29.213    [DEBUG][1]    CaptureSource.LoadAll()
2021-12-29 05:07:29.213    [DEBUG][1]    No C:\Users\Public\NPVR-Data\scripts\PreShutdown.bat
2021-12-29 05:07:29.213    [INFO][1]    Flushing logs
2021-12-29 05:07:29.213    [DEBUG][2]    Unloading...
2021-12-29 05:07:29.213    [INFO][2]    Flushing logs

Is this the server asking the phone for something, and never receiving it back? Is there some special port number involved? Again, I just keep thinking about BitDefender Firewall and a possible port number exception rule although I know it's virtually guaranteed unnecessary.

Remember that uidroid presumably does exactly the same thing, and it gets past that "waiting for broadcast" without a problem, and presents the opening Main Menu of the user interface.

Although it may not be of any real help, I'll attach one more log ZIP again. This is a "verbose logging" from just this minute, after restarting NextPVR Service and then demonstrating the successful uidroid connection again, and then stopping the NextPVR Service so that I can ZIP the log. It may not be your app, but again it might reveal something uidroid did that your own NextPVR app did not.


Note this isn't a log snippet, but rather a complete ZIP. So it shows the startup process for NextPVR Server on the Win7 PC. This might be informative, although whatever it's doing obviously is not a problem using uidroid. You'll see Hauppauge tuners (WinTV) mentioned in there as well, as I do also have a Hauppauge Quad-HD OTA/ATSC 4-tuner card in there for use by Windows Media Center (along with the Ceton 6-tuner card for Spectrum cable, which are not noticed by NextPVR).

Again, seems to exonerate NextPVR Server, BitDefender Firewall, and all things on the PC. Seems to be localized to the NextPVR app running on the S21, and whether it "sees" the "waiting from broadcast" or not and/or why it is not responding as expected.

Is there no special "debug version" of the client app you have on your development shelf, that you used when originally debugging and which might be helpful if installed onto my own S21?

[mvallevand]

The discovery process should be totally separate from the manual connection. Since discovery is working initially I would recommended clearing the Android memory for the NextPVR app and ignore manual connections for now.

Martin

[sub]

Delete the app, and reinstall it. When just start the app (no manually adding servers), are you seeing the correct ip address and port for your server displayed?

[DSperber]

Delete the app, and reinstall it. When just start the app (no manually adding servers), are you seeing the correct ip address and port for your server displayed?

Uninstalled. Went to Google Play Store, searched, found it, pushed INSTALL. When finished I pushed OPEN. The above appeared. Obviously it found the server running at 192.168.1.26.  However there is NO PORT NUMBER SHOWN.

Then nothing more. Here is the very tail end of the log, showing this very connection attempt. Interestingly I note that the "from" port number shown in the "received broadcast from" line is a different port number than before. Is this randomly assigned each connection? Or once chosen at install? Is it relevant?

Code:

2021-12-29 08:38:33.776    [DEBUG][10]    Received broadcast from 192.168.1.18:33119 : DISCOVER_REQUEST
2021-12-29 08:38:33.776    [DEBUG][10]     (fe80::a97a:6f51:6720:d3a3%14, 192.168.1.18)
2021-12-29 08:38:33.776    [DEBUG][10]     (fe80::dd05:a7f:a5cc:33d8%51, 192.168.1.18)
2021-12-29 08:38:33.776    [DEBUG][10]     (192.168.1.26, 192.168.1.18)
2021-12-29 08:38:33.776    [DEBUG][10]     (192.168.200.2, 192.168.1.18)
2021-12-29 08:38:33.776    [DEBUG][10]    address: 192.168.1.26
2021-12-29 08:38:33.776    [DEBUG][10]    Waiting for broadcast
2021-12-29 08:47:02.613    [DEBUG][1]    CaptureSource.LoadAll()
2021-12-29 08:47:02.613    [DEBUG][1]    No C:\Users\Public\NPVR-Data\scripts\PreShutdown.bat
2021-12-29 08:47:02.613    [INFO][1]    Flushing logs
2021-12-29 08:47:02.623    [DEBUG][2]    Unloading...
2021-12-29 08:47:02.623    [INFO][2]    Flushing logs

[mvallevand]

Does it work if you change the PIN to 0000?

Martin

[DSperber]

Does it work if you change the PIN to 0000?

Martin

But that's not the correct PIN value, which was changed along with the password when installing NextPVR DVR and also checking the "remote access" option.

Also, there's no way to actually change either IP or port or PIN without pushing the "add server" button. Again, what is shown does not include the port number but only the IP. I was asked to try connecting without changing anything first, right after reinstall.