Related
I got the Pixel 1, and it was working fine and great on 7.0, then 8.0 came along and i did the update, now its complete garbage. The phone will periodically shut off and turn back on, the bluetooth is almost not usable.
I drive a Ram, so it utilzes the Uconnect system, it worked flawlessly on 7.0, but now when its connected and i play spotify thru the Uconnect, it does not display song name or artist, it just says pixel, i never had this issue before. And to add insult to injury, this morning when i made a call to my wife thru my Uconnect system, it didn't even connect to my bluetooth, it was ringing thru my phone, I even checked to make sure the BT was on, it says it was and it was connected.
so does anyone know if there is a fix for this? or am i SOL? I really like the phone otherwise, these issues only came up after i updated to 8.0, can i downgrade it back to 7?
truwrxtacy said:
I got the Pixel 1, and it was working fine and great on 7.0, then 8.0 came along and i did the update, now its complete garbage. The phone will periodically shut off and turn back on, the bluetooth is almost not usable.
I drive a Ram, so it utilzes the Uconnect system, it worked flawlessly on 7.0, but now when its connected and i play spotify thru the Uconnect, it does not display song name or artist, it just says pixel, i never had this issue before. And to add insult to injury, this morning when i made a call to my wife thru my Uconnect system, it didn't even connect to my bluetooth, it was ringing thru my phone, I even checked to make sure the BT was on, it says it was and it was connected.
so does anyone know if there is a fix for this? or am i SOL? I really like the phone otherwise, these issues only came up after i updated to 8.0, can i downgrade it back to 7?
Click to expand...
Click to collapse
Bluetooth is an intermittent issue with Pixel and Oreo. Google is aware and apparently added a fix in most recent update (November).
Fortunately, I have had no issue with Bluetooth and Oreo on my Pixel.
Concerning downgrade, you can always flash any factory image.
does it not have a rollback protection? From my understanding, i would need to OEM unlock it first before i can roll it back, mine is on 8.0 from verizon and apprantly the oem unlock is protected so i cannot turn it on
truwrxtacy said:
does it not have a rollback protection? From my understanding, i would need to OEM unlock it first before i can roll it back, mine is on 8.0 from verizon and apprantly the oem unlock is protected so i cannot turn it on
Click to expand...
Click to collapse
Wasn't aware you had Verizon's version. You may want to check with Google Forums concerning the Bluetooth issue. Best wishes!
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
Phone Motorola One Vision (unlocked but NOT rooted)
Recently got updated (in UK) to Android 11 ~ 24th August 2021
Received a Security Update (dated 1 August) on 1st September 2021
Problem: Bluetooth will not stay connected - phone 'sees' whatever I try to connect to, it might 'connect' but then disconnects - depending on device it may take a few attempts before giving up
Firstly before anyone says 'search for it' - I have.
I've seen many posts about Android 11 & it's 'broken' bluetooth & the many so-called temporary fixes - but nothing works for me
(Clear Cache/Data, Reset Networks, Delete/Upair & reconnect etc) - Only thing I've not done is a full Phone factory reset
When the phone got updated to Android 11 everything went smoothly, except I had to go through all my Apps & (re)give the necessary permission to SD card etc. This also meant my Car Infosystem (SYNC 3 on a 2018 Ford C-max) didn't recognise my phone - so I deleted it & reconnected it & afaik for the week I was on Android 11 the phone stayed connected without any problems.
My Bluetooth Earbuds (cheap pair off of Amazon) still worked without any sound drop-off & My Amazefit Bip watch also stayed connected (apart from the occasional 'hiccup' when the App I use gets an update)
I then received a 'Security Update' a week later & now I've noticed Bluetooth is NFG (No F-ing Good).
When I try to pair up, the device(s) are seen (whether the car, earbuds or another phone) - I get the usual 'Check Pin matches the same as...' messages & I confirm.... then the phone disconnects/reconnects/disconnects until it finally gives up
In the case of the Car connection I get additional messages such as 'Allow Access to messages - An Untrusted Bluetooth device Ford C-Max, wants to access your messages' & I also get 'Bluetooth has stopped' pop-ups
In the case of Pairing up Phones - it just connects & disconnects, sometime when trying to reconnect - it doesn't even try to connect
The ONLY things that seems to stay connected is my Amazefit Bip watch - & ironically this is the only thing that DOESN'T show up as a 'Previously connected device' under Bluetooth
To try & figure this out I've tried all the usual tricks mentioned on Google Searches (as mentioned above), as well as trying different AVRCP & MAP options under the Phones 'Developer options' (even the 'Enable Gabeldorsche' option that apprently is suppose to stabilise connections)
- Nothing I've tried lets me stay connected more than a few seconds.
As I mentioned earlier I googled a lot & I see that Android 11 has had Bluetooth connection problems for a long time (posts I've seen go back to Feb 2012) & it's not just on one particular phone manufacturer - all the solutions given are basically all the same thing repeated, which I've tried (apart from the full manufacturer reset)
But as mentioned - these are 'old posts' (a few months old) & my questions are.....
Is there a permanent 'fix' for Android 11 Bluetooth connection problem ?
Do I/Will I have to wait until a proper fix is sent ? (afaik all this has happened due to the last 'Security Update' I received)
Is there a way to 'roll-back' to the previous Security Update (remember my Phone isn't rooted) - just to prove it's the update that caused the problem ?
or am I totally 'up-the-creek-without-a-paddle' do to a muck up by Google/Android developers ?
Cannon_Foddr said:
Phone Motorola One Vision (unlocked but NOT rooted)
Recently got updated (in UK) to Android 11 ~ 24th August 2021
Received a Security Update (dated 1 August) on 1st September 2021
Problem: Bluetooth will not stay connected - phone 'sees' whatever I try to connect to, it might 'connect' but then disconnects - depending on device it may take a few attempts before giving up
Firstly before anyone says 'search for it' - I have.
I've seen many posts about Android 11 & it's 'broken' bluetooth & the many so-called temporary fixes - but nothing works for me
(Clear Cache/Data, Reset Networks, Delete/Upair & reconnect etc) - Only thing I've not done is a full Phone factory reset
When the phone got updated to Android 11 everything went smoothly, except I had to go through all my Apps & (re)give the necessary permission to SD card etc. This also meant my Car Infosystem (SYNC 3 on a 2018 Ford C-max) didn't recognise my phone - so I deleted it & reconnected it & afaik for the week I was on Android 11 the phone stayed connected without any problems.
My Bluetooth Earbuds (cheap pair off of Amazon) still worked without any sound drop-off & My Amazefit Bip watch also stayed connected (apart from the occasional 'hiccup' when the App I use gets an update)
I then received a 'Security Update' a week later & now I've noticed Bluetooth is NFG (No F-ing Good).
When I try to pair up, the device(s) are seen (whether the car, earbuds or another phone) - I get the usual 'Check Pin matches the same as...' messages & I confirm.... then the phone disconnects/reconnects/disconnects until it finally gives up
In the case of the Car connection I get additional messages such as 'Allow Access to messages - An Untrusted Bluetooth device Ford C-Max, wants to access your messages' & I also get 'Bluetooth has stopped' pop-ups
In the case of Pairing up Phones - it just connects & disconnects, sometime when trying to reconnect - it doesn't even try to connect
The ONLY things that seems to stay connected is my Amazefit Bip watch - & ironically this is the only thing that DOESN'T show up as a 'Previously connected device' under Bluetooth
To try & figure this out I've tried all the usual tricks mentioned on Google Searches (as mentioned above), as well as trying different AVRCP & MAP options under the Phones 'Developer options' (even the 'Enable Gabeldorsche' option that apprently is suppose to stabilise connections)
- Nothing I've tried lets me stay connected more than a few seconds.
As I mentioned earlier I googled a lot & I see that Android 11 has had Bluetooth connection problems for a long time (posts I've seen go back to Feb 2012) & it's not just on one particular phone manufacturer - all the solutions given are basically all the same thing repeated, which I've tried (apart from the full manufacturer reset)
But as mentioned - these are 'old posts' (a few months old) & my questions are.....
Is there a permanent 'fix' for Android 11 Bluetooth connection problem ?
Do I/Will I have to wait until a proper fix is sent ? (afaik all this has happened due to the last 'Security Update' I received)
Is there a way to 'roll-back' to the previous Security Update (remember my Phone isn't rooted) - just to prove it's the update that caused the problem ?
or am I totally 'up-the-creek-without-a-paddle' do to a muck up by Google/Android developers ?
Click to expand...
Click to collapse
Im having exactly the same problem. Looks like it's the security update. May have to wait a month to get a fix I hope.
Sorry, I have the same problem with my One Vision XT1970-3 after upgrading on android 11
Did you give Magisk Bluetooth Library Patcher a try?
Same problem on UK Moto One Vision XT1970 following update to Android 11 and subsequent security update on same dates as above..
Ford Galaxy 2018 Sync 3 keeps disconnecting and reconnecting before giving up. Same Bluetooth "check pin..." message appears.
Everything worked flawlessly under Android 10. This is definitely an Android 11 issue.
It would be great to see some positive response from Google / Android / Motorola.
dc
dc305 said:
Same problem on UK Moto One Vision XT1970 following update to Android 11 and subsequent security update on same dates as above..
Ford Galaxy 2018 Sync 3 keeps disconnecting and reconnecting before giving up. Same Bluetooth "check pin..." message appears.
Everything worked flawlessly under Android 10. This is definitely an Android 11 issue.
It would be great to see some positive response from Google / Android / Motorola.
dc
Click to expand...
Click to collapse
Not a lot unfortunately.
I posted this problem on the Lenovo/Motorola Community Support forums (3rd October) & it seems not just you & I have had this problem (& not just on Ford Sync 3 either) - it does seem to point more towards the September Security Update though
Some posters have gone & brought new phones because of this problem, & (IMHO) a couple have even been a bit brash in their comments about how poor the support is. (What DID people do before phones could connect to cars by Bluetooth??? - I remember if someone called while I was driving, I just waited until I could pull over & phone back lol)
I admit I would've liked Motorola to release a sort of mid-month 'rollback' security update or something.. maybe even allowed people with problem to download & side install (somehow) the pre-1st August update just so that they could use their phones like they did before (I think you can with a rooted phone, but mine is unrooted).
let's hope they figure it out for the October Security Update
Cannon_Foddr said:
Not a lot unfortunately.
I posted this problem on the Lenovo/Motorola Community Support forums (3rd October) & it seems not just you & I have had this problem (& not just on Ford Sync 3 either) - it does seem to point more towards the September Security Update though
Some posters have gone & brought new phones because of this problem, & (IMHO) a couple have even been a bit brash in their comments about how poor the support is. (What DID people do before phones could connect to cars by Bluetooth??? - I remember if someone called while I was driving, I just waited until I could pull over & phone back lol)
I admit I would've liked Motorola to release a sort of mid-month 'rollback' security update or something.. maybe even allowed people with problem to download & side install (somehow) the pre-1st August update just so that they could use their phones like they did before (I think you can with a rooted phone, but mine is unrooted).
let's hope they figure it out for the October Security Update
Click to expand...
Click to collapse
PJ
Cannon_Foddr said:
Not a lot unfortunately.
I posted this problem on the Lenovo/Motorola Community Support forums (3rd October) & it seems not just you & I have had this problem (& not just on Ford Sync 3 either) - it does seem to point more towards the September Security Update though
Some posters have gone & brought new phones because of this problem, & (IMHO) a couple have even been a bit brash in their comments about how poor the support is. (What DID people do before phones could connect to cars by Bluetooth??? - I remember if someone called while I was driving, I just waited until I could pull over & phone back lol)
I admit I would've liked Motorola to release a sort of mid-month 'rollback' security update or something.. maybe even allowed people with problem to download & side install (somehow) the pre-1st August update just so that they could use their phones like they did before (I think you can with a rooted phone, but mine is unrooted).
let's hope they figure it out for the October Security Update
Click to expand...
Click to collapse
Thanks for the reply. Buying a new phone is a bit extreme. I've found that simply using a cable gives all the functionality needed with the added advantage of charging en route. Need to delete Bluetooth pairing for a quiet life.
I'll wait and watch for news of a workaround or solution.
Thanks again
Anyone else having issues with the latest update? I'm constantly getting error messages that NFC isn't supported anyone, my podcast app and media player doesn't work when I connect my Bluetooth headphones. It seems like this latest update wasn't well tested.
For me Google Pay not working, root signs detected
Bogeyof said:
For me Google Pay not working, root signs detected
Click to expand...
Click to collapse
I get that message too but contactless payments work.
I also get that message (Google Pay) in my non-rooted OP8. I think they've broken something. I haven't tried using it.
Alan
Has anyone found a cure for this? I can't use my card or add new ones.
The latest update seems to have cured everything I was worried about.
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