Cannot connect to NextPVR from Samsung S21 Ultra

[mvallevand]

I total agree with sub on that, (although you can hook up a remote and even HDMI out) my point was to primarily test connectivity. An added bonus on the Samsung is you can hear true AC-4 output.

Martin

[DSperber]

Just wanted to remind everyone that my PC is running BitDefender, which includes its Firewall support.

I did have to add some Rules for BitDefender Firewall, which I believe was part of the HDHR Server install (I think so, but can't recall if it was for NextPVR instead). Anyway it is to "allow" TCP access on port 8089, and UDP access on port 5353. And all relevant programs are named as allowed (e.g. NextPVR.exe, NextPVRServer.exe, along with all of the set of HDHomeRun*.exe programs).

I've even tried temporarily just turning BitDefender Firewall OFF entirely, and it's made no difference.   Even if NextPVR needed another port number "rule" that should not be relevant if I disable Firewall completely. So I don't think this is the issue.

So honestly at this point I think it must be something else.

[DSperber]

And under developer options you have also have USB debugging turned on, this is needed even for TCP connections.

Martin

Sure. It's on as well.

[mvallevand]

In at least one of your posts discovery on working so that should have connected regardless of the setting you have

2021-12-27 08:31:41.979 [DEBUG][10] Received broadcast from 192.168.1.18:50936 : DISCOVER_REQUEST

That is one reason I wanted to test uidroid.

Make sure your firewall is allow outbound.

Martin

[DSperber]

I total agree with sub on that, (although you can hook up a remote and even HDMI out) my point was to primarily test connectivity.  An added bonus on the Samsung is you can hear true AC-4 output.

Martin

Exactly. I agree as well. I really hadn't intended to use uidroid on the phone. As you mention, it was just to see if it, too, was unable to connect or not to the server, as another data point in the hunt for why primary NextPVR couldn't connect.

Nevertheless, it still is now another question as to why ADBLINK2 cannot connect to the phone.  What if I really did want to side-load something to it.

I know. Off-topic. I will take this up on the ADBLINK forum which is where this new discussion really belongs.

[DSperber]

In at least one of your posts discovery on working so that should have connected regardless of the setting you have

2021-12-27 08:31:41.979    [DEBUG][10]    Received broadcast from 192.168.1.18:50936 : DISCOVER_REQUEST

That is one reason I wanted to test uidroid. 

Make sure your firewall is allow outbound.

Martin

BitDefender Firewall port number rules are for ALL PROGRAMS, and BOTH DIRECTIONS.

I don't have any rule for 50936 (if that's what NextPVR client app uses), but regardless it fails even if I totally disable Firewall.

I think the diagnostic avenue of simply trying to connect and log in through a browser and 192.168.1.26:8866, and getting that to work, that's the most promising route to getting to the bottom of what the problem really is.

[mvallevand]

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

[DSperber]

From that, it just looks like you're using the wrong username/password. Maybe check if you phone is doing something with auto capitalizing or something.

Wait a minute. I just assumed that the "login" dialog presented when I browsed to 192.168.1.26.8866 from my phone expected a username of "admin" and a password of "password". Is that NOT the case?

Furthermore, when the NextPVR client app (not uidroid, but YOUR NextPVR Android client app from the Play Store) is launched there is no username or password to enter. There is only a server IP:port number and PIN. That's exactly what I previously entered (but which fails to connect), and what I've repeatedly RE-ENTERED (using the "add server" button and entering the proper numeric values yet again). And that is failing, which is the origin of this thread's discussion.

I don't think it's a keyboard entry problem.

In your server debug code is that a way to output whatever the text strings received are? Something you're expecting or looking for is not matching. So what is that mis-match? Would be helpful if what is getting received were displayed, so that any extraneous or incorrect characters or puncuation or whatever could be clearly seen.

[sub]

From that, it just looks like you're using the wrong username/password. Maybe check if you phone is doing something with auto capitalizing or something.

Wait a minute. I just assumed that the "login" dialog presented when I browsed to 192.168.1.26.8866 from my phone expected a username of "admin" and a password of "password". Is that NOT the case?

Yes, the default would be admin/password unless you've changed it.

In that case, it clearly looked like you hadn't supplied the same username/password as it was expecting.

Furthermore, when the NextPVR client app (not uidroid, but YOUR NextPVR Android client app from the Play Store) is launched there is no username or password to enter. There is only a server IP:port number and PIN. That's exactly what I previously entered (but which fails to connect), and what I've repeatedly RE-ENTERED (using the "add server" button and entering the proper numeric values yet again). And that is failing, which is the origin of this thread's discussion.

If the server is discovered on the local network, then no login information is required. If you manually enter a server, then you supply ip:port and pin.

Try restarting NextPVR, then try connecting again from the NextPVR app on your phone, then zip and attach your logs (not a small snippet this time).

In your server debug code is that a way to output whatever the text strings received are? Something you're expecting or looking for is not matching. So what is that mis-match? Would be helpful if what is getting received were displayed, so that any extraneous or incorrect characters or puncuation or whatever could be clearly seen.

It doesn't actually pass the text strings to the server, so it's unable to log them. It just passed a hashed copy. (your web login showed different hashes, meaning it was not the same login details as stored in the server)

[DSperber]

From that, it just looks like you're using the wrong username/password. Maybe check if you phone is doing something with auto capitalizing or something.

Wait a minute. I just assumed that the "login" dialog presented when I browsed to 192.168.1.26.8866 from my phone expected a username of "admin" and a password of "password". Is that NOT the case?

Yes, the default would be admin/password unless you've changed it.

In that case, it clearly looked like you hadn't supplied the same username/password as it was expecting.

Furthermore, when the NextPVR client app (not uidroid, but YOUR NextPVR Android client app from the Play Store) is launched there is no username or password to enter. There is only a server IP:port number and PIN. That's exactly what I previously entered (but which fails to connect), and what I've repeatedly RE-ENTERED (using the "add server" button and entering the proper numeric values yet again). And that is failing, which is the origin of this thread's discussion.

If the server is discovered on the local network, then no login information is required. If you manually enter a server, then you supply ip:port and pin.

Try restarting NextPVR, then try connecting again from the NextPVR app on your phone, then zip and attach your logs (not a small snippet this time).

Ok. I'm an idiot. I completely forgot that I HAD changed the password as well, in addition to changing the PIN.

In fact I DID change both password and PIN from their defaults in order to support "remote connection". While this was primarily to support local network connection from my LAN streaming devices, I believe (though have not tested it) connection to my NextPVR server from outside on the web from a Windows laptop or from my S21 phone (which hasn't yet succeeded in even locally connecting).

Mea culpa.  This was explained with installation text, and my brain had forgotten it. But I had, in fact, both done this as well as made notes in my records along with the two new values.

And now sure enough, when I attempt the manual login to 192.168.26:8866 and specify the CORRECT password, sure enough "something" happens indicating success at the server end.

I have also now repeated my NextPVR app attempt (which of course still is failing).

I have now put all of the logs into a ZIP file, attached here.

EDIT: I've deleted the ZIP file from this post, as it was mistakenly done without first turning on verbose logging. Please see my later post on the next page of the thread, this time with a proper ZIP done with verbose logging. Sorry for the inconvenience.

EDIT #2: well, looks like the forum software doesn't actually DELETE the attachment, even though I clicked on the "X" and confirmed that I wanted the attachment deleted, and then applied the update to this thread. My updated text (like right here) appears, but the attached incorrect ZIP file remains. So just ignore it and use the larger "correct" one (reflecting verbose logging) in my later post.