Cannot connect to NextPVR from Samsung S21 Ultra

[mvallevand]

I understand but I wanted to know if it worked with default.

Martin

[DSperber]

Again, I note that the most recent connection attempt (after pushing the Add Server button and manually entering 192.168.1.26:8866 and the correct PIN number) once again shows another different port number in the RECEIVED BROADCAST FROM log line. Is this appropriate and correct? Is it ever-changing for security? Is it relevant to the permanent "waiting from broadcast" state back at the server?

Code:

2021-12-29 09:22:01.973 [DEBUG][10] Received broadcast from 192.168.1.18:53661 : DISCOVER_REQUEST 2021-12-29 09:22:01.983 [DEBUG][10] (fe80::a97a:6f51:6720:d3a3%14, 192.168.1.18) 2021-12-29 09:22:01.983 [DEBUG][10] (fe80::dd05:a7f:a5cc:33d8%51, 192.168.1.18) 2021-12-29 09:22:01.983 [DEBUG][10] (192.168.1.26, 192.168.1.18) 2021-12-29 09:22:01.983 [DEBUG][10] (192.168.200.2, 192.168.1.18) 2021-12-29 09:22:01.983 [DEBUG][10] address: 192.168.1.26 2021-12-29 09:22:01.983 [DEBUG][10] Waiting for broadcast

[sub]

Again, I note that the most recent connection attempt (after pushing the Add Server button and manually entering 192.168.1.26:8866 and the correct PIN number) once again shows another different port number in the RECEIVED BROADCAST FROM log line. Is this appropriate and correct?

That's normal. It's just whatever port number Android has allocated on the client side. It'll be different each time.

[sub]

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.

I just double checked this - it's normal to not have the port number shown.

[sub]

If you could get ADBLINK2 to connect to your phone, we could use it to collect some logs, which has probably got some error message or something...

[DSperber]

If you could get ADBLINK2 to connect to your phone, we could use it to collect some logs, which has probably got some error message or something...

I will do that in a minute. Through USB cable I presume.

But first one more question. Presumably the initial presentation of IP-only corresponds also to a default port of 8866. And also presumably there is a default PIN of 0000. But if I have set NextPVR Server with the "remote access" option checked, and was obligated to change password and PIN as well, how can the phone's default PIN of 0000 work... assuming PIN is still required for this phone-to-server connection method?

Now if I push the ADD SERVER button, and now manually enter the complete 192.168.1.26:8866 and also the new PIN and OK, when I get back to the main screen it still shows the one-and-only original 192.168.1.26. So did that one original entry get UPDATED with the replacement values from my "add server" dialog? Turns out that was the same IP:port but a new PIN?

If PIN is needed then the initial post-install connection attempt is guaranteed to not be successful if I've checked "remote access" and changed the PIN on the server. So it seems at the very least I shouldn't expect a successful connection right after install, with a changed PIN. Right?

Anyway, I will get the phone connected via USB cable and ADBLINK2 right now. Be back in a minute.

[DSperber]

Ok. Phone is "'connected" to ADBLINK2 through USB cable. Device is "authorized" successfully.

I'm at your command. What would you like me to do?

[DSperber]

Incidentally, if you would like to remotely connect to my PC and control ADBLINK2 yourself, I support both UltraViewer and Team Viewer remote connections right now. If you have some other preferred method we could discuss.

Otherwise I'll just patiently follow your instructions here.

[sub]

But first one more question. Presumably the initial presentation of IP-only corresponds also to a default port of 8866. And also presumably there is a default PIN of 0000. But if I have set NextPVR Server with the "remote access" option checked, and was obligated to change password and PIN as well, how can the phone's default PIN of 0000 work... assuming PIN is still required for this phone-to-server connection method?

It should still work fine with whatever pin number you've set on the server. The local network discovery includes a hash of the pin, which can be used for automatically logging in.

Now if I push the ADD SERVER button, and now manually enter the complete 192.168.1.26:8866 and also the new PIN and OK, when I get back to the main screen it still shows the one-and-only original 192.168.1.26. So did that one original entry get UPDATED with the replacement values from my "add server" dialog? Turns out that was the same IP:port but a new PIN?

Yes, it'll replace the current one in the list. FYI, if you port is the default 8866, then you don't need to enter it in the 'Add Server' popup. ie, just enter 192.168.1.26 and whatever the pin is.

We've never seen the session.initiate request in your logs though, so it's not related to the pin being wrong. ie, it's never connected to server to check that.

[sub]

Ok. Phone is "'connected" to ADBLINK2 through USB cable. Device is "authorized" successfully.

I'm at your command. What would you like me to do?

From memory there is a 'logcat' option in the menus?