Cannot connect to NextPVR from Samsung S21 Ultra

[DSperber]

WAIT A MINUTE!!!  While I was waiting for your ADBLINK2 instructions, I retried the NextPVR client connection. And, magically, after "connecting..." suddenly it was apparently successful finally and the UI appeared!!

I will look at the log in a moment, to see what happened. But with the phone connected via USB cable to one PC on my network, it was apparently able to successfully connect to a second PC on my network where NextPVR Server runs.

[sub]

FYI, it's not great timing to be trying to experiment with the Android app - I put out a new release a couple of days ago, which broke the layout of a few screens. I've got a new build to push out later today to fix this issue.

[DSperber]

Here's the log snippet. Note that with the phone "wired-connected via USB cable" to a PC which is wired on the LAN, the access via the same 192.168.1.18 IP address now responds to the "waiting for broadcast", and all proceeds properly... same as uidroid does even using just plain WiFi connection to the network.

For some reason, it appears NextPVR on the phone is not successful when the phone is connected to the network through WiFi. But if USB-connected (indirectly, via a connected PC) whatever security software is blocking the original connection attempt is now bypassed. And yet, this didn't impact uidroid!

I wonder if it's got something to do with the "Digital Secure" (from Verizon) running on my phone that "protects me" from "insecure WiFi networks", establishes VPN alternate if for example I'm using public WiFi like at the airport, etc.? But again, why wasn't this a factor with uidroid?

Anyway, here is that connection snippet from NextPVR and its SUCCESSFUL connection.

Code:

2021-12-29 09:49:06.184    [DEBUG][10]    Received broadcast from 192.168.1.18:58175 : DISCOVER_REQUEST
2021-12-29 09:49:06.184    [DEBUG][10]     (fe80::a97a:6f51:6720:d3a3%14, 192.168.1.18)
2021-12-29 09:49:06.184    [DEBUG][10]     (fe80::dd05:a7f:a5cc:33d8%51, 192.168.1.18)
2021-12-29 09:49:06.184    [DEBUG][10]     (192.168.1.26, 192.168.1.18)
2021-12-29 09:49:06.184    [DEBUG][10]     (192.168.200.2, 192.168.1.18)
2021-12-29 09:49:06.184    [DEBUG][10]    address: 192.168.1.26
2021-12-29 09:49:06.199    [DEBUG][10]    Waiting for broadcast
2021-12-29 09:49:16.870    [DEBUG][30]    Got request [192.168.1.18]: /services/service (session.initiate)
2021-12-29 09:49:16.885    [DEBUG][30]    method=session.initiate
2021-12-29 09:49:16.885    [DEBUG][30]    parameters:
2021-12-29 09:49:16.885    [DEBUG][30]       method: session.initiate
2021-12-29 09:49:16.885    [DEBUG][30]       ver: 1.0
2021-12-29 09:49:16.885    [DEBUG][30]       device: android
2021-12-29 09:49:16.885    [DEBUG][30]       client_ip: 192.168.1.18
2021-12-29 09:49:16.885    [DEBUG][30]       user_agent: Dalvik/2.1.0 (Linux; U; Android 12; SM-G998U Build/SP1A.210812.016)
2021-12-29 09:49:16.885    [DEBUG][30]       host_callback: ...
2021-12-29 09:49:16.885    [DEBUG][30]       sid: default
2021-12-29 09:49:16.885    [INFO][30]    InitiateSession (device=android)
2021-12-29 09:49:16.885    [DEBUG][30]    SetSessionObject(a59cbb86146a4323b00d241b11d890a9, 'child', NON-null)
2021-12-29 09:49:16.885    [DEBUG][30]    Device: android
2021-12-29 09:49:16.885    [DEBUG][30]    SetSessionObject(a59cbb86146a4323b00d241b11d890a9, 'child', NON-null)
2021-12-29 09:49:16.885    [DEBUG][30]    <?xml version="1.0" encoding="utf-8" ?>
<rsp stat="ok">
  <sid>a59cbb86146a4323b00d241b11d890a9</sid>
  <salt>413b04cd-b8e1-4dce-aac3-9c67bb043828</salt>
</rsp>

2021-12-29 09:49:16.994    [DEBUG][30]    Got request [192.168.1.18]: /services/service (session.login)
2021-12-29 09:49:16.994    [DEBUG][30]    method=session.login
2021-12-29 09:49:16.994    [DEBUG][30]    parameters:
2021-12-29 09:49:16.994    [DEBUG][30]       method: session.login
2021-12-29 09:49:16.994    [DEBUG][30]       sid: a59cbb86146a4323b00d241b11d890a9
2021-12-29 09:49:16.994    [DEBUG][30]       md5: add60f324c01b44a52a1e29479e397fc
2021-12-29 09:49:16.994    [DEBUG][30]       client_ip: 192.168.1.18
2021-12-29 09:49:16.994    [DEBUG][30]       user_agent: Dalvik/2.1.0 (Linux; U; Android 12; SM-G998U Build/SP1A.210812.016)
2021-12-29 09:49:16.994    [DEBUG][30]       host_callback: ...
2021-12-29 09:49:16.994    [INFO][30]    LoginSession(sid = a59cbb86146a4323b00d241b11d890a9)
2021-12-29 09:49:17.026    [DEBUG][30]    [IX21JOnrl51fl5ye/GWAkTtbrkKr5hdSSqG1m68UZwD0rjkYP+ixVhR3EojbAJCQ1Rs/HpyhZIpPPrWDm5lVWUutJ+VFykrYnH0rZGNUyDuAKeKpGIwA8DUX9r5B3MOzVHV5U8vBnm193sE/xoRjiwmB3wLB9cAnRwGi0hQ/MZ6tdoueCgBMonKF+eyp3YAnzq9cNfJn/Cit/wzKLdFsVpD4NLGxRznkffXNegNWjgrc+ZCAENZXotdC7kU5ozPniSDNsNA4LxRL+XS1IVyfzedXkGOpXIngYtAs2itMC4kKxTsnZc3Czisc+eOgeyWwSZuNTc0jS5BD8kHRwp0JzgU56IdjsYYmu78mfyISJzqIsJpFz0R1JaAI8A3o3AxxYFzz/zN8D4tQv2U32OyhpKvlO4uf8QDDLOr5bmrxqp6dPCZCrfsSQsgG0EoM5prSpEk46ckDpGVVCSXz89ql3Q==]
2021-12-29 09:49:17.026    [DEBUG][30]    [FX33EnK5eRRsryU/j+b1Ni8rLzv0+oOt9UtZthk60HmltZfvCPS36HMakHbjqOc5K8/VsrfHZWbwV5Ajxsu5Ix66ytAsq2XTr+tI2HgYbkYYkaZ4gyDwnWitAAkkgHsRiv39sK5iNrt1WZyFVwC1HcUsvDNIuJG8Vvub6buqzivUnPH4ebxhnMY1k1XJaG4+iCMhSyo9d1OyxGPKEY6YvMCrAXwpJPuzTm6y14z1ZSGuHVYoUNVqIYPe5D9feyRSlFzSIlw3x/IIrOV/eRS8CJjKJFnWeV1mhaQgA6s2T2HIulxY1spgKq+nfoYdcovh1OUx/vq3Gs0w3/ZPlgR6Q9/uVV/g2y4zpY+iJcTYdZplc+JNn9KEd1lmhEa9Uq905NcbrI0CM9gwW1c6QV0xETtWaJR0ZkWhqrII19pjysg=]
2021-12-29 09:49:17.026    [DEBUG][30]    [RNxZFfUBp547Xnh3A1uxl6Ye3NcpAg0Qsx39NQ6CmqrdiiKE9PPqZkouda62LBuWJc2kVZMNwqE04DymsVeOwwq72h15xNnQFxRBTJ+JR1tXLR01Wa1xeG6jIDMtMWNHWXQ2lk74KhcRdZYPCny+8CyGkeaIpGuQbdKx4bZ5oh14GGk8MqpgvB2uDHUHvB9TkwqeeaN8DhEaJMhSWRFEGEmL8WjgxvKlE8y/9NxrVhRbkAKCBcbWbHAeVICwsQa/krurQMg0BEf/Hmw+XKX1mEoykYydFK6yUh2PtgrDQLI8XOi3fv3QTIyhE1tQEZQXuNMe8PBSDJSsec/X7L5tbvwY+HbwS4hsORazpLeZdLvsWVR8X1Px5f76Q8anmt+2PfKH8yD+Oznro1/oxylKtUGsAqNGmGXWuxcJUOMtPpQ=]
2021-12-29 09:49:17.041    [DEBUG][30]    <?xml version="1.0" encoding="utf-8" ?>
<rsp stat="ok">
  <sid>a59cbb86146a4323b00d241b11d890a9</sid>
  <allow_settings>false</allow_settings>
  <allow_watch>true</allow_watch>
  <allow_schedule>true</allow_schedule>
  <allow_delete>true</allow_delete>
</rsp>

2021-12-29 09:49:17.228    [DEBUG][27]    Got request [192.168.1.18]: /services/service (channel.list)
2021-12-29 09:49:17.228    [DEBUG][27]    method=channel.list
2021-12-29 09:49:17.228    [DEBUG][27]    parameters:
2021-12-29 09:49:17.228    [DEBUG][27]       method: channel.list
2021-12-29 09:49:17.228    [DEBUG][27]       group_id: All Channels
2021-12-29 09:49:17.228    [DEBUG][27]       format: json
2021-12-29 09:49:17.228    [DEBUG][27]       sid: a59cbb86146a4323b00d241b11d890a9
2021-12-29 09:49:17.228    [DEBUG][27]       client_ip: 192.168.1.18
2021-12-29 09:49:17.228    [DEBUG][27]       user_agent: Dalvik/2.1.0 (Linux; U; Android 12; SM-G998U Build/SP1A.210812.016)
2021-12-29 09:49:17.228    [DEBUG][27]       host_callback: ...
2021-12-29 09:49:17.244    [DEBUG][27]    GetChannelList@1
2021-12-29 09:49:17.275    [DEBUG][27]    GetChannelList@exit
2021-12-29 09:49:17.275    [DEBUG][27]    {
"channels": [

[sub]

I wonder if it's got something to do with the "Digital Secure" (from Verizon) running on my phone that "protects me" from "insecure WiFi networks", establishes VPN alternate if for example I'm using public WiFi like at the airport, etc.? But again, why wasn't this a factor with uidroid?

It wouldn't surprise me. It sounds like the type of thing that could get in the way.

[DSperber]

I wonder if it's got something to do with the "Digital Secure" (from Verizon) running on my phone that "protects me" from "insecure WiFi networks", establishes VPN alternate if for example I'm using public WiFi like at the airport, etc.? But again, why wasn't this a factor with uidroid?

It wouldn't surprise me. It sounds like the type of thing that could get in the way.

Sure enough, just pulled the USB cable and tried NextPVR, and once again connection failure.

Reconnected through USB cable to PC, and once again SUCCESS!

I will pursue this "Digital Secure" (essentially a firewall for the phone) configuration, and see if there are "exceptions" that can be authorized.

Also, I will reconfirm that my home WiFi network is correctly configured and recognized as a private and secure network, which is probably what's fundamentally at the hear of the problem.

Guess we don't need to use ADBLINK2!

Finally... some real progress. (except for the enigma of why uidroid's connection method seems to work around this whole issue, and is successful even in the current WiFi mode)

I've gotta go somewhere right now, but I'll be back later (hopefully with some good answers)

[sub]

except for the enigma of why uidroid's connection method seems to work around this whole issue, and is successful even in the current WiFi mode

It's probably just down to the way uidroid was installed manually rather than from play store. It probably ends up with different entitlements/permissions when installed this way.

[mvallevand]

I did have to use this in the discovery thread.

Code:

.
            StrictMode.ThreadPolicy policy = new StrictMode.ThreadPolicy.Builder().permitAll().build();
            StrictMode.setThreadPolicy(policy);

Martin

[DSperber]

I did have to use this in the discovery thread.

Code:

.
            StrictMode.ThreadPolicy policy = new StrictMode.ThreadPolicy.Builder().permitAll().build();
            StrictMode.setThreadPolicy(policy);

Martin

I've researched that "Digital Secure" app on my phone, that provides device and WiFi security. It was paid for as part of add-on insurance I opted into when I bought the phone, to provide loss/accident/theft/damage protection. It also included as part of the deal some other phone services I had already been paying separately for (so that I could cancel those separate items).

Turns out my home Wifi network did originally show up as "unprotected", but I only had to "enable" the WiFi security option for the currently in-use WiFi and it became "protected". But this is unrelated to the NextPVR connection problem when not USB connected, as my experimenting has shown. It only enables or disables VPN WiFi. so when "enabled" the NextPVR app cannot even see my home network, and thus doesn't even present 192.168.1.26. Thus through this VPN technique the phone is isolated from possiblity of intrusion. As soon as I "disable" the "Secure WiFi" feature, instantly 192.168.1.26 pop onto the screen. But then there is still no actual connection.

I believe only if the WiFi network was "blocked" (as opposed to "protected" vs. "unprotected") might this second concept possibly been relevant to the current discussion. But my home WiFI network is NOT BLOCKED. It was only "unprotected" or "protected", with NextPVR still not connecting for either.

So this brings us to the coding you've done in your "discovery" logic. Sub, do you have something similar in your own NextPVR? Could this be the secret sauce? Worth trying perhaps, as long as you've got a product update coming out in a few days to fix the screen issues you said had been recently broken by a previous update?

Works with uidroid, which connects without needing the USB cable connection trick. Can it hurt/harm? I'd certainly be willing to beta test it, if you want. Just put it in a special APK.

[mvallevand]

That's only one part of the sauce. You've already showed us that the manual connection fails so that means there is another different problem.

Martin