I'm rooted on Pie June update (PQ3B.190605.006) and suffering from infamous "CaptivePortalLogin keeps stopping" issue reported on Reddit ( can't post link due to policy, sorry).
As a temporary solution I use CAPTIVE_PORTAL_MODE_IGNORE in Settings.java to prevent Android from detection of captive portals.
To do that in root shell on device run:
settings put global captive_portal_mode 0
The same could be accomplished over ADB.
After updating that setting I don't get notifications until opening page in browser, which redirects me to the login page of the Wi-Fi provider.
I'm looking for ideas how to make CaptivePortalLogin to work on PQ3B.190605.006 version.
Tried to remove Magisk, reflash clean and replace CaptivePortalLogin in /system/apps with different APK provided here on XDA, sideloaded July PQ3B.190705.003 version, but nothing helped.
SOLUTION: Clean flash of July update PQ3B.190705.003 on both A/B and full factory reset.
my workaround for this is basically turning on airplane mode -> turn on wifi and connect to network -> open browser and load a random page to be redirected to the captive portal.
Did it work with the march version? Looks like even stock phones seem to have a problem with it according to reddit. It worked just fine for me on june when it wasnt rooted..
Thank you so much for workaround! It works.
For your question about March version, I don't have an answer if it worked out of the box, as I didn't try it.
It would be nice to fix CaptivePortalLogin, not sure how to attack it though.
While waiting on support to fix CaptivePortalLogin, I came up with a temporary solution, to avoid a brute force "Airplane mode" method. I decided to use CAPTIVE_PORTAL_MODE_IGNORE in Settings.java to prevent Android from detection of captive portals.
Solution:
in root shell on device run:
settings put global captive_portal_mode 0
The same could be accomplished over ADB.
After updating that setting I don't get notifications until opening page in browser, which redirects me to the login page of the Wi-Fi provider.
I hope someone can benefit from this solution until we get a real fix for CaptivePortalLogin.
I have disabled MAC address randomization in the advanced options of the WiFi network and it seems to solve the issue. Many captive portals use the MAC address to identify the device, so this would be a good explanation of the problem.
Thanks for suggestion. That option was off on my device by default and I didn't play with it. And in my case Captive Portal Login crashed on every network implementation from my corporate one to coffee shop.
R0BiN0705 said:
my workaround for this is basically turning on airplane mode -> turn on wifi and connect to network -> open browser and load a random page to be redirected to the captive portal.
Did it work with the march version? Looks like even stock phones seem to have a problem with it according to reddit. It worked just fine for me on june when it wasnt rooted..
Click to expand...
Click to collapse
This did not help
Still keep getting captiveportal crashed.
Any other suggestions?
Look at my original post or post #4 how to use CAPTIVE_PORTAL_MODE_IGNORE to disable Captive Portal login.
Wow! I am glad I am not the only one experiencing this issue!
I have the google pixel 3a with June security patch and rooted with Magisk via patched boot image.
Im wondering, is this due to Magisk or is this an actual issue with the June 2019 Factory Images/OTA?
Thanks!
djjohnnyblaze said:
Wow! I am glad I am not the only one experiencing this issue!
I have the google pixel 3a with June security patch and rooted with Magisk via patched boot image.
Im wondering, is this due to Magisk or is this an actual issue with the June 2019 Factory Images/OTA?
Thanks!
Click to expand...
Click to collapse
I speculate it's a bug in June update, because it did crash for me with or without Magisk. But on another hand I would expect more activity on this thread if it is a widespread issue.
pasha_d said:
I speculate it's a bug in June update, because it did crash for me with or without Magisk. But on another hand I would expect more activity on this thread if it is a widespread issue.
Click to expand...
Click to collapse
Looked at some threads on Reddit and it seems like even new devices are having this issue.
I don't think anyone knows what's causing it but this is a big deal. What scares me is one thread that said a replacement device works now with June security update. How could this be hardware though? Especially if it was working prior to June 2019 security update ...
The July security patch did not resolve this issue. How do we escalate this?
Issue had already been raised... No fix yet.
https://issuetracker.google.com/issues/135711621
karimski75 said:
Issue had already been raised... No fix yet.
https://issuetracker.google.com/issues/135711621
Click to expand...
Click to collapse
Not sure where they're going to fix it though, maybe in Q only. I'm looking for a fix in Pie.
Here is the post from assigned developer from Google:
vi.. @google.com <vi.. @google.com> #83 Jul 9, 2019 02:26AM
Marked as fixed.
The issue has been fixed and it will become available in a future Android release. Please keep an eye on the release notes(https://developer.android.com/preview/release-notes)
It crashes for me too. Bummer!
Stock and non-rooted.
Pasha_d posted a solution that worked for me. You need to be rooted.
https://forum.xda-developers.com/pixel-3a/help/captiveportallogin-apk-t3940042
Pasha, did you ever find a copy of the March version of the captiveportallogin.apk?
No I didn't. The only ones I found on APK mirror were from February. Nobody replied to my original request here on XDA.
I was able to turn off data. Load a web page and sign in over wifi.
pasha_d said:
No I didn't. The only ones I found on APK mirror were from February. Nobody replied to my original request here on XDA.
Click to expand...
Click to collapse
March apk
Related
I'm trying to enable fingerprint sign on in the Wells Fargo app on my rooted, magisk pixel 2 on the latest march update. I've tried a couple times to enable it and it tells me that fingerprint sign on is currently unavailable. Anybody else experiencing the same issue?
enzyne said:
I'm trying to enable fingerprint sign on in the Wells Fargo app on my rooted, magisk pixel 2 on the latest march update. I've tried a couple times to enable it and it tells me that fingerprint sign on is currently unavailable. Anybody else experiencing the same issue?
Click to expand...
Click to collapse
Working for me, but I'm stock.
I'm rooted with TWRP flashed. Other apps (like Walmart) that require fingerprint find it, but my banking app (PNC) doesn't, and doesn't work at all (restarts during a check deposit), so there's something causing a problem somewhere.
Rukbat said:
I'm rooted with TWRP flashed. Other apps (like Walmart) that require fingerprint find it, but my banking app (PNC) doesn't, and doesn't work at all (restarts during a check deposit), so there's something causing a problem somewhere.
Click to expand...
Click to collapse
Are you using Magisk? I use the PNC app and have it selected with magisk hide and fingerprint works.
1.Try depositing a check.
2. What version of the app are you running?
So just an update I was after a day able to add fingerprint sign on. I just got this account so that may be why. I dont have paper checks to deposit that often but if i ever get one i will report back.
Rukbat said:
1.Try depositing a check.
2. What version of the app are you running?
Click to expand...
Click to collapse
I'm running 4.3.1. It crashes now when the camera would open to capture a check image, but it used to work before. I hadn't used it in a while so must be something broken in an update... All the other functions except for check deposit are working.
Same version - and that's the only reason I use the app. Since I'm on the desktop all day, I do everything else on the desktop. Tech support promised that they'd have a fix out by end of March, beginning of April at the latest. Nothing yet. Oh - when it crashes, it comes up with the name and password screen when you rerun it, and won't accept the fingerprint.
A company I used to work for had a sign hanging in their cafeteria that said that it costs $1,000 to get a customer, but you can lose one with a single wrong word. I think I'm about to become one of PNC's "lost customers". The local Walmart, where I am at least once a week, has a bank branch inside (and the store is pretty much around the corner). The next time I'm there, I'm talking to them. Even if they don't have an app, I'm there all the time anyway. And PNC is 4 miles across town. It will be interesting to see if the app eventually works, but this isn't how you run a software department. (I know - I spent 45 years developing software, most of them either as lead or as head of the department. An "I can't use the program because it doesn't work" would immediately put that bug at the top of my) list - and get someone assigned to fix it.)
Anyone else having this issue, did a google search as well as a forum search.. Haven't seen this anywhere.
When I try to preview a sound in the settings for ringtones/notifications in any of the categories other than My Sounds, they just spin.
Actually the problem is well known, for example, that thread was started Dec 16 2017. Also the Issue Tracker report at Google's resources was filled Feb 23 2018 and claimed to be fixed in Dec 30 2018. Still isn't fixed - last comment about the issue was Feb 28 2019. In XDA thread there is a fix with Tasker since it appeared the problem is with connection/disconnection of a bluetooth device and Tasker's fix works with that. In my case it doesn't work (or at least sometimes doesn't work - it seems problem happens now less often, than before). Tasker is not free app, but has 14 days trial period. The comment about that fix. For now you can temporarily fix it by reboot - till the next occurrence. I'm going to open another issue, since there is no reaction in the issue thread, or you can do it yourself.
Thanks for the reply. It actually turned out to be the 1.1.1.1 app. As soon as I disabled it, the sounds loaded. I tried that on a hunch and it worked. Definitely not sure if that is the issue for all the reports I have seen posted on the app review.
Not at all how the DNS app and the Sounds app could be related.
bsdmj said:
Thanks for the reply. It actually turned out to be the 1.1.1.1 app. As soon as I disabled it, the sounds loaded. I tried that on a hunch and it worked. Definitely not sure if that is the issue for all the reports I have seen posted on the app review.
Not at all how the DNS app and the Sounds app could be related.
Click to expand...
Click to collapse
Possible, coincidence. After Feb update I caught the same problem, but was busy and didn't reboot my phone and after some time it fixed itself. So, possible, the fix works, but needs some time to act. Will keep an eye at that, especially after your discovery of seems to be unrelated app's interference. Weird...
Hi everyone,
Just see the new update in Essential release page
September 2019 Release | Q 10 - Q Release 1.5 - QP1A.190711.122
https://www.essential.com/developer/current-builds
Just arrived for me
Any improvement?
Enviado desde mi PH-1 mediante Tapatalk
Darkside1984 said:
Any improvement?
Enviado desde mi PH-1 mediante Tapatalk
Click to expand...
Click to collapse
What were broken?
chanh2018 said:
What were broken?
Click to expand...
Click to collapse
Volte for some
Also got today's update - 3.7 MB. Figured it was minor fixes they discovered. Installed - now my phone is not working. When I restarted, it froze on the splash screen. Several tries - same result. Won't boot to recovery. Will boot to Fastboot - try Recovery or Start from there, freezes on splash screen. Only choice that works is turn off. If you get the 1.5 update, you might want to wait before installing it.
HueyT said:
Volte for some
Click to expand...
Click to collapse
Well...what I see is LTE+ now show up (it was LTE only from the first release)
VoLTE toggle is always in setting (no change)
Wifi calling seem doesn't work for me
...btw, I'm using AT&T service
chanh2018 said:
What were broken?
Click to expand...
Click to collapse
I'm wondering if anyone else experienced what I did with the initial update to Android 10 with OTA update?
I've had Nova launcher beta since I've had this phone. Also rooted with Magisk using the uninstall (restore stock images, no reboot, OTA update, no reboot until installing Magisk to updated other (OTA) partition (OTA only option). What I was experiencing with Nova as default launcher was eventual slowdown which was also noticed with launching browser. Not connecting and opening but hanging up. Reboot phone; all well initially except noticing WiFi was continually reconnecting (I recently saw a post saying some routers may do this because Android 10 randomly changes the MAC address as a safety feature- I'm not aware of this? but something I read). The wifi reconnect doesn't seem to slow the phone with stock launcher as default.
Anyway, I didn't experience the slowdown with the launcher defaulted to Quick Step. Stock. But I did still see the WiFi continually reconnecting.
I just did the recent update I was alerted to today. So far, ok, not noticing the reconnecting WiFi yet. That could change but I hope not. I haven't tried Nova beta again yet. Wondering if anyone else experienced this and can give an all clear?
Memory leak? I cleared all app cache with titanium backup and rebooted. That didn't help; still eventually slowed and couldn't open browsers. I had considered a user data wipe but stopped short of trying the stock launcher. That helped; hasn't showed yet. But I'm missing the Nova shortcuts and gestures. Putting widgets on my home screen isn't so eye pleasing as having the gestures. Not the same as I'm accustomed to.
I know Nova has said Android needs an update to accommodate gestures like stock. But I haven't heard Nova is causing issues using as default launcher with Android 10 on the Essential or other phones?
Sent from my PH-1 using Tapatalk
Have to say, I haven't had any issues.
johnny8910 said:
Have to say, I haven't had any issues.
Click to expand...
Click to collapse
Same here, apart from the calendar sound selection crash (don't care, really).
samep said:
WiFi was continually reconnecting (I recently saw a post saying some routers may do this because Android 10 randomly changes the MAC address as a safety feature- I'm not aware of this? but something I read).
Click to expand...
Click to collapse
Really? WTF? What kind of a safety feature is that? What about MAC filtering on the routers (I have it set up)? I hope that's just some glitch, and not intentional... No WiFi problems for me so far.
I haven't heard Nova is causing issues using as default launcher with Android 10 on the Essential or other phones?
Click to expand...
Click to collapse
I am using Nova as default (have been for ages), and it doesn't give me any grief.
kt-Froggy said:
Same here, apart from the calendar sound selection crash (don't care, really).
Really? WTF? What kind of a safety feature is that? What about MAC filtering on the routers (I have it set up)? I hope that's just some glitch, and not intentional... No WiFi problems for me so far.
I am using Nova as default (have been for ages), and it doesn't give me any grief.
Click to expand...
Click to collapse
I use the MAC filtering on a Netgear Orbi router. Just saw the wifi reconnect again with latest Android 10 update. Flips back and forth between WiFi and cellular connection; like WiFi to cellular and back to WiFi for a while. I thought I had read about that somewhere in one of the Essential threads; effects some routers, not all. Not sure where. I was hoping to get confirmation on what I'm seeing since updating to Android 10.
I didn't do any beta Q updates. Just stock OTA updates.
Thanks for the feedback on Nova. I was using beta. You're on standard Nova release with no issues like mine?
Sent from my PH-1 using Tapatalk
rbsummers said:
Also got today's update - 3.7 MB. Figured it was minor fixes they discovered. Installed - now my phone is not working. When I restarted, it froze on the splash screen. Several tries - same result. Won't boot to recovery. Will boot to Fastboot - try Recovery or Start from there, freezes on splash screen. Only choice that works is turn off. If you get the 1.5 update, you might want to wait before installing it.
Click to expand...
Click to collapse
Try to "flash-all.bat" in fastboot or bootloader mode to reinstall latest Q v122. Full time, not OTA. Edit out "format user data" in flash-all.Bat file to keep data
samep said:
I use the MAC filtering on a Netgear Orbi router. Just saw the wifi reconnect again with latest Android 10 update. Flips back and forth between WiFi and cellular connection; like WiFi to cellular and back to WiFi for a while. I thought I had read about that somewhere in one of the Essential threads; effects some routers, not all. Not sure where. I was hoping to get confirmation on what I'm seeing since updating to Android 10.
I didn't do any beta Q updates. Just stock OTA updates.
Thanks for the feedback on Nova. I was using beta. You're on standard Nova release with no issues like mine?
Click to expand...
Click to collapse
I'm running Nova Beta but haven't had any slowness issues & like you no Q betas or tweaks, only taken stock OTA all the way to first Q release (not using mac filtering on router either). Could it be another app, someone on the Q&A thread said their phone suddenly started going very slow a few days ago, they were still on Oreo.
Only issue I've had was keypass2android crashed when filling in a password today (1st time ever, don't know why or if it's related to Android 10).
IronRoo said:
I'm running Nova Beta but haven't had any slowness issues & like you no beta or tweaks, only taken stock OTA all the way to first Q release (not using mac filtering on router either). Could it be another app, someone on the Q&A thread said their phone suddenly started going very slow a few days ago, they were still on Oreo.
Only issue I've had was keypass2android crashed when filling in a password today (1st time ever, don't know why or if it's related to Android 10).
Click to expand...
Click to collapse
I think it was another app; third party memory management. Android 10 doesn't seem to deal with cache wipe without a reboot. I used a boost app by HTC since I got this phone too but looks like I'm done with it now. Tapatalk wouldn't run; opened the boost app and saw it had recently wiped its cache.
I've seen similar behavior with Tapatalk and browsers, just manually wiping cache and app won't run without a reboot, at least initially. Just took a while to duplicate this after freezing Nova launcher was all.
I'm ready to try Nova beta again. Thanks for the confirmation on the beta app.
Edit: That was odd thawing Nova; QuickStep 10 kept reengaging as default home or momentarily until home tapped again after gesture to launch recent apps screen. I know Nova could do that animation before but doing so was bringing in Quick step to do this. Appears the Quick step launcher needs force closing after selecting Nova once thawed but a momentary freeze with titanium on the quick step launcher afterwards also did the trick. Followed by another reboot which became necessary due to slowdown almost immediately after all the above. I've never experienced this amount of oddity.
Had hopes things were here back to normal...
Edit 2: maybe time to uninstall Nova and start from scratch or even wipe user data. Nova didn't last a day for me before the slowdown returned.
Edit 3 (update): I've kept going back to Quick Step launcher for eventual slowdowns. But one common slowness I saw consistently was launching apps from recents. I sent an email to Nova development through Google Play link. Didn't get a response yet but Nova beta 6.2.2 showed as an update for me in Google Play today so I tried it. So far I can launch apps from recents without lag (just as fast). Hoping my glitches are gone this time.
Sent from my PH-1 using Tapatalk
So sometime throughout today my gpay started failing cts and I also got a notification to update my phone's firmware. Lol
I'm still on August as I haven't had a chance to update yet. I am also running Canary Magisk and Kirisakura so clearly in not taking the OTA.
I guess Google decided to push out some server side stuff. Anyway just thought I'd throw this out there for anyone else with the same to know they are not alone.
CyberpodS2 said:
So sometime throughout today my gpay started failing cts and I also got a notification to update my phone's firmware. Lol
I'm still on August as I haven't had a chance to update yet. I am also running Canary Magisk and Kirisakura so clearly in not taking the OTA.
I guess Google decided to push out some server side stuff. Anyway just thought I'd throw this out there for anyone else with the same to know they are not alone.
Click to expand...
Click to collapse
Same thing happened to me this morning with google pay.
Notification saying google pay can't be used because of uncertified software out of nowhere. Fact is, it's a cat and mouse game. We find an exploit, google patches it.
Try to check if hardware verification is enabled
If hardware verification is enabled, CTS will fail
There are currently three solutions
1.Replace ROM, some ROM hardware verification will not be enabled
2.use MagiskHide Props config Change fingerprint
3.Use the module I made to change the name of the phone to the code name, which can maintain the original fingerprint
cracky.ice said:
Try to check if hardware verification is enabled
If hardware verification is enabled, CTS will fail
There are currently three solutions
1.Replace ROM, some ROM hardware verification will not be enabled
2.use MagiskHide Props config Change fingerprint
3.Use the module I made to change the name of the phone to the code name, which can maintain the original fingerprint
Click to expand...
Click to collapse
I just use the basic module and I'm good... I just wanted to head off the rush of posts about this. Figured it would at least corral some of them into one thread.
CyberpodS2 said:
I just use the basic module and I'm good... I just wanted to head off the rush of posts about this. Figured it would at least corral some of them into one thread.
Click to expand...
Click to collapse
It is very difficult to merge threads, because everyone has different ways, and even the wrong way makes developers difficult
So I did a factory reset from 11 and upgraded to 13. Been on the fence about downgrading until I tired it on my work vans Uconnect Bluetooth and it wasn't crashing it (Was a known issue) and was like ok maybe i can live with the other stupid issues like it not auto playing Pandora when a Bluetooth device connected.
Well when I try to enable hotspot it says "to use personal host spot you need to subscribe to Personal Hotspot Services". Worked just fine on 11. I got Verizon in the US. I am Rooted and on latest security updates on stock OOS13. When I go online or use the stupid automated service it just says my device doesn't support it.
Willing to go back to 11 (Honestly feature wise it just seemed the best overall with the exception of my work van which I can live without) or use a different tethering app if out there.
drtweak said:
So I did a factory reset from 11 and upgraded to 13. Been on the fence about downgrading until I tired it on my work vans Uconnect Bluetooth and it wasn't crashing it (Was a known issue) and was like ok maybe i can live with the other stupid issues like it not auto playing Pandora when a Bluetooth device connected.
Well when I try to enable hotspot it says "to use personal host spot you need to subscribe to Personal Hotspot Services". Worked just fine on 11. I got Verizon in the US. I am Rooted and on latest security updates on stock OOS13. When I go online or use the stupid automated service it just says my device doesn't support it.
Willing to go back to 11 (Honestly feature wise it just seemed the best overall with the exception of my work van which I can live without) or use a different tethering app if out there.
Click to expand...
Click to collapse
You can try updating to the latest OOS13.1 (and check if it fixed this issue) or revert to OOS11.
Rootk1t said:
You can try updating to the latest OOS13.1 (and check if it fixed this issue) or revert to OOS11.
Click to expand...
Click to collapse
Already On 13.1 April 5 security