OK, so my trusty (made in 2016) Pixel has been faultless for 10 months.
Along with the microphone problem (after installing the 8.1 5 July 2018 Security Update) and the fix (enrolling and installing Android 9 P beta) I now have a new issue where my NFC is "disabled".
I have successfully added a bank account card to the Google Pay app but when I go to use it at a store it just does nothing. I installed the 'Phone Information' app which tells me my NFC chip is there but "disabled".
Is the NFC issue a deliberate PPP5.180610.010 thing or what?
Yours,
Frustrated of Maidstone, Kent, UK.
Related
Hello everyone, i currently own a Chinese version MHA-AL00 Mate 9, and my Android Pay wasnt working. Im on build B153.
I fixed this issue by going into my Settings->More->Near Field Communication (NFC)->NFC SECURITY CHIP->Card 1:AT&T
It was set to "Built-in security chip" and that was the problem i was having. And as for AT&T, just replace it with your carrier. Hope this helps!
Also i made an unboxing video and highlighted some other issues here
youtube.com/watch?v=Q6mJKITexDM
No it wasn't the problem. Mine set at "built-in security chip". Works just fine. I think it was Google changed something on their end. After updating to B153, Android pay didn't work initially but after a couple days I tried again it started working without me changing anything
Not sure if this is a Android issue or a Pixel 2 issue. I have an up-to-date Pixel 2 (Android 9 with Feb 5 2019 security patch). Last November when I tried to use the Mobile Passport app it crashed when doing a 'new reciept' (entry) after set-up and then crashed every time I tried to restart it on unlock. Did the this month when I reinstalled it to use it coming back from Costa Rica (app says it was updated in Jan 2019).
Here's the weird thing. It works on my Moto X4 (also Android 9, but with January 2019 security patch). Problem is that my Moto is my "Costa Rica" phone (no US carrier service).
I tried taking off the apps on my Pixel that aren't on my Moto (but since the Pixel has some necessary apps that are not on the Moto I can't make them identical.
Did u update ur phone to the latest security patch (Feb 5)
Hello all,
First of all:
My Mi 10 Lite used to work properly on an Audi Head Unit and a china Android HU with an AA box.
With the china HU the phone ran with MIUI 12.1 und 12.5 I guess? I did got an update to MIUI 12.5.1 this week.
I have the Skoda since 02. july, so Android Auto worked with all MIUI Versions till then on the china Radio in my old car.
Now I have a big problem, that after pressing the microphone button on screen, my voice is detected, and the assistant will do what I am saying. For example "Play BAND XY an Spotify" or "Route to Mainstreet my City". I can also say "Write a whatsapp to abc". After that command it says something like "OK, chatting with abc. What do you want to say?". AND now my voice won't be recognized anymore.
What have I tried till now:
- updated firmware of Skoda Headunit to newest Version (1433)
- three different cables (china noname, Anker, original Xiaomi cable)
- another Android Phone (Samsung A40) --> DID work well
Just as I am writing now, I have not tried yet to swipe the cache of the app.
In the screenshots, you cann see the permissions of the Android Auto app.
What have I missed? What can I do?
For me it is an important feature to dictate messages, as my family or girlfriend sometimes have simple questions per whatsapp, which can be shortly answered. Calling would be a very much longer time, and my drive home is about an hour.
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
I cant get NFC to work properly. My phone is able to read cards and tags in NFC mode but it doesnt emit anything. E.g. google pay is not working.
I have ArrowOS 11 with latest MIUI firmware.
I tried with my wifes NFC phone and my Poco can register signal from her phone but not the other way around.
Im thinking firmware issues or something with ArrowOS?
Any ideas?
I've got a similar issue, I can't get NFC payments to work. Also using Arrow OS 11 (latest release) with the newest miui firmware. Tried to root my phone with Magisk 24 to see if this works but until now without any success. Any help would be great.
I was able to get mine to work yesterday using an apple 12 as reciever.
The signal is insanely weak, i literally had to use a precise angle at a certain spot on the iphone to get a registration.
There is no way to get a card terminal to register anything this NFC emits. Seems it has to be closer than a few millimeters apart to get any registration.
Which is strange because i can scan tags/cards that are a few cm away without issue..
Im thinking this is a hardware issue
ndb055 said:
I've got a similar issue, I can't get NFC payments to work. Also using Arrow OS 11 (latest release) with the newest miui firmware. Tried to root my phone with Magisk 24 to see if this works but until now without any success. Any help would be great.
Click to expand...
Click to collapse
Install Magisk 23, hide the Magisk app (it will get a different icon and a different package name), hide Magisk from Google Play, Google Pay and your banking apps, install GPay SQLite Fix v2.6 from here:
Releases ยท stylemessiah/GPay-SQLite-Fix
A magisk module that ONCE allowed Google Pay to work on rooted phones - stylemessiah/GPay-SQLite-Fix
github.com