search

Divested-Mobile / DivestOS-Build

Everything needed to build DivestOS, a more private and more secure aftermarket mobile operating system.
https://divestos.org/index.php?page=build
Other
217 stars 31 forks source link

Oneplus 6T - No connectivitly after update to 19.1 #134

Closed ph00lt0 closed 2 years ago

ph00lt0 commented 2 years ago

After updating to 19.1 today I have lost any connectivity. Both Wi-Fi as well as 4G do not seem to be working.

SkewedZeppelin commented 2 years ago

fajita is my daily driver, I do not have such issue.

firmware is included too, so it can't be that either. Even after a reboot?

SkewedZeppelin commented 2 years ago

Can you try Settings > System > Reset options > Reset Wi-Fi, mobile & Bluetooth?

ph00lt0 commented 2 years ago

Reboot I tried couple of times, didn't seem to help. Tried reset now, didn't help either unfortunately.

SkewedZeppelin commented 2 years ago

Install the update again from Updater or adb sideload?

ph00lt0 commented 2 years ago

Just sideloaded again, no changes to the issue.

SkewedZeppelin commented 2 years ago

Can you post some logs?

Any messages being spammed repeatedly?

Also

ph00lt0 commented 2 years ago

Yeah i can what should i be looking for?

ph00lt0 commented 2 years ago

I just tried something crazy, created a new user. In that user the internet actually works.

ph00lt0 commented 2 years ago

I already reset app settings and stuff so i wonder what could it be.

SkewedZeppelin commented 2 years ago

Did you have private DNS set? or the captive portal disabled?

Perhaps adb shell settings put global captive_portal_mode 1;

eh that can't be it

ph00lt0 commented 2 years ago 
07-16 17:52:16.609  2347  2676 D TelephonyProvider: Using old permission behavior for telephony provider compat
07-16 17:52:16.617  2347  2674 D TelephonyProvider: Using old permission behavior for telephony provider compat
07-16 17:52:16.623  2347  2676 D TelephonyProvider: Using old permission behavior for telephony provider compat
07-16 17:52:16.634 11570 11570 I SubscriptionsPrefCntrlr: Active cellular network or active carrier network.
07-16 17:52:16.656  2347  2674 D TelephonyProvider: Using old permission behavior for telephony provider compat
07-16 17:52:16.662  2347  2674 D TelephonyProvider: Using old permission behavior for telephony provider compat
07-16 17:52:16.668  2347  2674 D TelephonyProvider: Using old permission behavior for telephony provider compat
07-16 17:52:16.679 11570 11570 I SubscriptionsPrefCntrlr: Active cellular network or active carrier network.

I see this back a lot so I am thinking it might have to do with it, also doesn't show up in the other user.

SkewedZeppelin commented 2 years ago

Unlikely

ph00lt0 commented 2 years ago

Did you have private DNS set? or the captive portal disabled?

~Perhaps adb shell settings put global captive_portal_mode 1;~

eh that can't be it

I actually had, but enabled it again before filing bug report. Didn't resolve the issue

ph00lt0 commented 2 years ago

Maybe this tells you something:

1; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.32 Safari/537.36]} headers={null=[HTTP/1.1 204 No Content], BFCache-Opt-In=[unload], Connection=[close], Content-Length=[0], Content-Type=[text/html; charset=UTF-8], Date=[Sat, 16 Jul 2022 16:59:17 GMT], Server=[gws], X-Android-Received-Millis=[1657990758004], X-Android-Response-Source=[NETWORK 204], X-Android-Selected-Protocol=[http/1.1], X-Android-Sent-Millis=[1657990757921], X-Frame-Options=[SAMEORIGIN], X-XSS-Protection=[0]}
07-16 17:59:18.010  2243 17346 D NetworkMonitor/106: PROBE_HTTP http://connectivitycheck.gstatic.com/generate_204 time=150ms ret=204 request={Connection=[close], User-Agent=[Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.32 Safari/537.36]} headers={null=[HTTP/1.1 204 No Content], Connection=[close], Content-Length=[0], Date=[Sat, 16 Jul 2022 16:59:17 GMT], X-Android-Received-Millis=[1657990758009], X-Android-Response-Source=[NETWORK 204], X-Android-Selected-Protocol=[http/1.1], X-Android-Sent-Millis=[1657990757932]}
07-16 17:59:18.164  2243 17345 D NetworkMonitor/106: PROBE_HTTPS https://www.google.com/generate_204 time=294ms ret=204 request={Connection=[close], User-Agent=[Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.32 Safari/537.36]} headers={null=[HTTP/1.1 204 No Content], Alt-Svc=[h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"], Connection=[close], Content-Length=[0], Date=[Sat, 16 Jul 2022 16:59:17 GMT], X-Android-Received-Millis=[1657990758162], X-Android-Response-Source=[NETWORK 204], X-Android-Selected-Protocol=[http/1.1], X-Android-Sent-Millis=[1657990758026]}
07-16 17:59:18.167  2243 17344 D NetworkMonitor/106: isCaptivePortal: isSuccessful()=true isPortal()=false RedirectUrl=null isPartialConnectivity()=false Time=5389ms
07-16 17:59:18.173   991  1689 D ConnectivityService: [106 CELLULAR] validation passed
07-16 17:59:18.174   991  1689 D ConnectivityService: NetReassign [no changes]
07-16 17:59:18.183   991  1080 I GnssNetworkConnectivityHandler: updateNetworkState, state=CLOSED, connected=true, network=106, capabilities=[ Transports: CELLULAR Capabilities: MMS&SUPL&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&VALIDATED&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED&NOT_VCN_MANAGED LinkUpBandwidth>=15000Kbps LinkDnBandwidth>=30000Kbps Specifier: <TelephonyNetworkSpecifier [mSubId = 1]> SubscriptionIds: {1}], availableNetworkCount: 1
07-16 17:59:18.190   991  1689 D ConnectivityService: Setting DNS servers for network 106 to [/194.151.228.34, /194.151.228.50]
07-16 17:59:18.191   991  1689 D DnsManager: sendDnsConfigurationForNetwork(106, [194.151.228.34, 194.151.228.50], [], 1800, 25, 8, 64, 0, 0, , [194.151.228.34, 194.151.228.50])
07-16 17:59:18.192   713 17354 W resolv  : Validating DnsTlsServer 194.151.228.34 with mark 0xf006a
07-16 17:59:18.192   713 17355 W resolv  : Validating DnsTlsServer 194.151.228.50 with mark 0xf006a
07-16 17:59:18.196   991  1689 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendStickyBroadcast:1568 com.android.server.ConnectivityService.sendStickyBroadcast:2812 com.android.server.ConnectivityService.sendGeneralBroadcast:2787 com.android.server.ConnectivityService.sendInetConditionBroadcast:2764 com.android.server.ConnectivityService.updateInetCondition:8452 
07-16 17:59:18.254   713 17354 W resolv  : SSL_connect ssl error =5, mark 0xf006a: Connection refused
07-16 17:59:18.254   713 17354 W resolv  : TLS Handshake failed
07-16 17:59:18.255   713 17354 W resolv  : query failed
07-16 17:59:18.255   713 17354 W resolv  : validateDnsTlsServer returned 0 for 194.151.228.34
07-16 17:59:18.256   713 17354 W resolv  : Validation failed
07-16 17:59:18.270   713 17355 W resolv  : SSL_connect ssl error =5, mark 0xf006a: Connection refused
07-16 17:59:18.270   713 17355 W resolv  : TLS Handshake failed
07-16 17:59:18.271   713 17355 W resolv  : query failed
07-16 17:59:18.271   713 17355 W resolv  : validateDnsTlsServer returned 0 for 194.151.228.50
07-16 17:59:18.271   713 17355 W resolv  : Validation failed
07-16 17:59:22.748   991   991 W ActivityManager: Receiver with filter android.content.IntentFilter@6e72379 already registered for pid 991, callerPackage is android
07-16 17:59:22.760   991  2050 W ActivityManager: Foreground service started from background can not have location/camera/microphone access: service org.projectmaxs.main/.MAXSModuleIntentService
SkewedZeppelin commented 2 years ago

Did you happen to go through all your apps and disable all internet access except for VPN access at one point?

ph00lt0 commented 2 years ago

Nope, didn't even know was an option, but also my vpn app itself didn't want to connect

ph00lt0 commented 2 years ago

I just did a factory reset and seems to work fine now.

SkewedZeppelin commented 2 years ago

OK :crying_cat_face: Very strange thing to happen.

ph00lt0 commented 2 years ago

DW this is just my secondary device. It probably was caused by myself tho, I really can't think of what but will be closing for now.

wyndon commented 1 year ago

I have a very similar issue after the recent update on my OP5T. Likewise, rebooting/resetting Wi-Fi settings didn't solve the problem, but I have connectivity access on a new user.

EDIT : Okay, it seems the update did something weird with apps permissions, all my apps have the "Network" permission not allowed, when it was clearly the case beforehand

Screenshot_20221024-192416_Permission controller

SkewedZeppelin commented 1 year ago

@wyndon read the news, you're on an experimental build, you must expect some quirks: https://divestos.org/index.php?page=news#XXXX-XX

20.0 rebuilds were published on October 20th. Users already on the existing 20.0 builds will have Network and Sensors permissions disabled for all user apps.

That is because those first 20.0 builds did not have those permissions, when they were added they were default disabled for user apps.

Users upgrading from 19.1 or fresh installing 20.0 will not have such issue.

wyndon commented 1 year ago

@wyndon read the news, you're on an experimental build, you must expect some quirks: https://divestos.org/index.php?page=news#XXXX-XX

20.0 rebuilds were published on October 20th. Users already on the existing 20.0 builds will have Network and Sensors permissions disabled for all user apps.

That is because those first 20.0 builds did not have those permissions, when they were added they were default disabled for user apps.

Users upgrading from 19.1 or fresh installing 20.0 will not have such issue.

Thanks for the answer.

To be fair, news aren't really highlighted on the website, and they also are under "Docs", probably why I missed this. I'll keep that in mind in the future.