Database Users

Contacts not syncing via bluetooth to car now on 7.1.1

Just updated to 7.1.1 from 7.0 where all was well with the car (BMW 530 - E60), but now I have no contacts viewable from the car.
I've tried deleting the phone and repairing but still the problem persists, I can't see any contacts anymore on 7.1.1
Anybody have any idea how to fix?
Thanks in advance
Paul

my bluetooth isn't working with my 2011 GMC now that I've flashed 7.1.1 It connects for a second or two, then disconnects. This was an issue on the Pixel, but now its fixed on 7.1.1 not sure why 6P got screwed up

Google makes me mad
Bluetooth connects no problems in 7.0 to my 2011 Chev Cruze. Update to 7.1.1, drops every second. Flash factory image of 7.1.1 in hope that it might have been an OTA issue, and no luck. Flash 7.0 factory image, and bluetooth works and stays connected with my car. But after downgrading I lost the ability to restore all my apps and data, just had the Gapps. There wasn't an option to restore the info from my 6P previous to factory imaging it.. So now I have to manually search the apps out and reinstall them.
I just don't understand how Google keeps screwing this up. I'm grateful to have a Nexus and I can rescue myself, but it would be a piss off if I was not aware of how to get myself back to a place when the phone actually WORKED. It's just nonsense.

TREMER said:
Bluetooth connects no problems in 7.0 to my 2011 Chev Cruze. Update to 7.1.1, drops every second. Flash factory image of 7.1.1 in hope that it might have been an OTA issue, and no luck. Flash 7.0 factory image, and bluetooth works and stays connected with my car. But after downgrading I lost the ability to restore all my apps and data, just had the Gapps. There wasn't an option to restore the info from my 6P previous to factory imaging it.. So now I have to manually search the apps out and reinstall them.
I just don't understand how Google keeps screwing this up. I'm grateful to have a Nexus and I can rescue myself, but it would be a piss off if I was not aware of how to get myself back to a place when the phone actually WORKED. It's just nonsense.
Click to expand...
Click to collapse
If possible, can you post the 7.0 factory image? Thank you in advance
Sent from my SM-G928T using Tapatalk

2012 GMC Sierra. No Bluetooth issues at all with MM or Nougat 7.0. Side-loaded 7.1.1 OTA this morning, now my Bluetooth connection drops/connects repeatedly (every 2-3 seconds). Have deleted the BT device from phone & repaired, wiped cache, & rebooted with no success. Stock/no root here.

skydog1970 said:
2012 GMC Sierra. No Bluetooth issues at all with MM or Nougat 7.0. Side-loaded 7.1.1 OTA this morning, now my Bluetooth connection drops/connects repeatedly (every 2-3 seconds). Have deleted the BT device from phone & repaired, wiped cache, & rebooted with no success. Stock/no root here.
Click to expand...
Click to collapse
I have been having the same issue, but apparently no one in the threads of the roms I have flashed do not appear to be having that issue
Sent from my SM-G928T using Tapatalk

[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work

Bluetooth not working with 7.1.1 aosp stable x - Jiayu s3a

Hello,
First of all, sorry for my bad english, i'm french and not very good
Thanks for reading me and the help you give me on xda (even if i never post, i always find my solution on the forums )
I'm actually on CM13 6.0.1 20160810 beta, working quite good since then, but my system is going completely drunk, my sim is not working any more (only my sim), wifi problems etc.
Factory reset is a solution but i have to setup again all my apps, so I want to update to 7.1.1 and then setup all my apps on a new rom without the bugs i used to.
I create this thread because i tried to install MAD Team aosp 7.1.1, stable 7 and also stable 8 and succeeded, but bluetooth is not working...
The problem i have is when i install this rom, bluetooth is written as "Disabled", and when i turn it on, it stays greyed 10 seconds and returns to OFF.
I tried many things :
-install starting from CM13 with factory reset
-install starting from CM13 without factory reset
-install starting from CM13 with format data
-install official 5.1 after factory reset + format data, then install 7.1.1
-factory reset after installing 7.1.1 with all methods over
I'm out of ideas, not finding useful things on the web, even on XDA threads :crying:
It's not hardware problem, my BT works perfectly on CM13 actually, and when I reinstall CM13 after a 7.1.1 fail (with or without restoring my data), it works again...
If you have any idea, i'm desperate :fingers-crossed:
Thanks for your help

I had the same problem the first time I enabled Bluetooth, but rebooted the phone (just one time) worked. Now Bluetooth works perfectly.

Thanks for your quick answer, I tried it this morning but no result.. :crying:

Bluetooth pairing lost after every reboot

Hello,
Am I the only one with this problem? Bluetooth loses all paired devices after every reboot...
- no problem pairing with any BT device
- after every reboot some or all previously paired devices are completely gone/missing from the list of paired devices.
- after wiping Dalvik/Cache in TWRP, they all show up again and can be paired without going through pairing (until next normal reboot).
- some device on the paired list may be lost permanently even after wiping Dalvik/Cache IF some new BT devices have been added or deleted. In this case a new pairing procedure is needed, as if the device(s) was never paired before.
It seems some devices are more "sensitive" than others. For example a BT mouse may still be on the paired list after reboot while the car BT (Toyota Venza) will always, invariably disappear from the list. In the car, as it tries to connect, the phone will keep asking for randomly generated pairing codes, which the car will not recognize until the phone gets added/paired again. On the other hand, the phone never disappears from the list of paired phones in the car's BT menu.
Just a thought: it's definitely a phone issue rather than a BT device issue (any). Whether connected or not, within or out of range, the phone will always loose the list of paired devices after a reboot.
Phone: SM-G950F (AQH3)
CSC: XEU (UK & Ireland) / Used in Canada on Virgin Mobile
Rooted with Magisk
Thanks!

Same Problems
Hello, I got the same problems. After seeing that this post is a little older, did you found a solution to this?
Need to try the dalvic/cache solutions next reboot.

Some (unknown) system modifications are the culprit! You need to reinstall the firmware (fresh install) using Odin (all sections, not just AP) and most importantly, during the installation of TWRP make sure you do NOT ALLOW SYSTEM MODIFICATIONS (do not use the slider)..

Just started having this very issue recently. Rooted Snapdragon S8+
Used to ok fine remembering all BT devices after a reboot. Just last week, started to notice I would have to start over pairing all my devices after a reboot. Ex: Car Sync, Gear S3 Frontier, Various Earbuds.
I don't have Twrp recovery due to the locked bootloader. I suspect it could be an app, however, no idea where to begin.... Any advice?

Unlikely for an app to do that, unless the app changed your system. Although I'm not sure what really causes it, I know that "some" system modifications do that. At some point I created shortcuts of some hidden settings, using Activities, which caused that to happen again. I didn't have to go through the hassle of reinstalling everything fresh through Odin since I've had a recent TWRP backup and I've restored both, the System and Data. I've lost many hours trying to figure out what exactly causes it but I didn't get any further than figuring out that: (1) some system modifications cause this to happen and (2) reflashing firmware through Odin without allowing any other system modifications during the process, is the ONLY WAY to get back the normal BT behavior.

Any fix for this
I have started getting this on my rooted S9+
Started to get annoying now.
I have stock rom, custom Kernal and magisk.
What resolved yours in the end?

It seems to be an Xposed issue: https://github.com/rovo89/Xposed/issues/294

Despite the apparency, I don't think this is caused by the XPosed framework. As I've detailed above, the problem may occur even before installing XPosed. Even with XPosed installed, everything may be running just fine indefinitely, until certain system modifications seem to be triggering this problem. Although I pointed out before that this would most certainly happen if, during the TWRP installation, system modifications are allowed (by sliding the bar), I'm almost sure that TWRP in itself is NOT the culprit. The same may be said about XPosed. While both may seem to potentially be triggering the issue, I don't think they really are the cause. My feeling is that the real cause is Samsung's native system (possibly one specific application). I've noticed, for example, that when the problem occurs, while Android loses the list of previously BT paired devices either partially or completely, Samsung's Connect still sees them all - as if nothing happened. How is that possible? It's just assumptions at this point but one thing is certain - after freezing Samsung Connect (Smart Things), I've never had the issue again.
As for permanently resolving this once it happens, there seems to be ONLY two ways:
1. Start fresh by re-flashing the stock ROM through ODIN and if TWRP is also installed, system modifications should not be allowed at this time, or.
2. If you already had TWRP installed and had a nandroid backup (System and Data) done before the problem occurred, (1) wiping system and data and then (2) restoring their respective previous versions, definitely solves the problem, without having to go through ODIN everything fresh.
I hope this helps, and I also hope that someone could eventually identify the root cause and address this once and for all. I definitely wouldn't hold my breath counting on Samsung's help!

Note 10 + sm-n975f
Rooted with Magisk
Definitely not an exposed issue because I am not using exposed, never had exposed on this device.
Same problem with 2 different phones of the same model. One was a international dual sim and the other international single sim.
2 other problems,
Sometimes incoming call notification sound can be heard but no incoming call shows up on the screen (ie. Answer /decline. No missed call notification either, only a new voicemail notification, but if they do not leave a message then you would not know who called. lol
Other issue is Sammy is putting music apps to sleep randomly even though I used an app to set screen time out to never.
Never had any of these problems on any other rooted device always used note phones. Ready to get an Exynos note 8, got the 10 because thought it was cool and I was using the note 8 previously with SamFAIL. Too many glitches though.
Man Sammy is failing big time as usual. Never had this foolishness on any other note always been using rooted notes. (exceptffor note 9) Every Sammy support agent acts like they never heard of this before. I see a bunch of note 9 users on shameful Sammy's forums having this exact Bluetooth problem, shame on Sammy's lies and ignorance!
Update :
Found this Magisk fix, This file name is
nfsinjector-956.zip
Flashed with Magisk module manager.
Update : still not working

From experience, I can confirm that a failsafe way to ALWAYS get back all previously stored BT paired devices is to wipe your Dalvik/cache in TWRP.
I'm still on a Samsung S8, rooted with Magisk + TWRP and XPosed. Once in a while I get this BT issue and the above suggested solution always worked for me. Let me know if it works for you.
As for the rest of the problems, I'm really disappointed to hear that. I was planning on buying myself a Note 10 but that makes me rethink it - it pretty much was THE REASON I held back for so long.
I always suspected this had nothing to do with the XPosed framework but every one on Earth, including the devs, swear by it. Well, you just confirmed it.

Xposed had this issue on s8 we had found a fix somewhere. It may not be present on newer versions. Modifying the libs or something. I studied into it. It's even in the github for xposed. So for me it was most definitely xposed

Thanks for the wipe cash fix, I would like to try it, but not sure if I can since I don't have twrp, can twrp be installed on a Exynos note 10?
Is Its possible that the xposed fix is actually fixing a Samsung failure and not an xposed problem to begin with in the place?
all those people on the note 9 shameful Sammy fourms I assume are unrooted users!

Xposed had always had issues on Samsung's. Until s7 or 8 it was modded by Rovo. The s8 didn't need rovos xposed.

Android Auto: Something Went Wrong (Google Play Services)

I recently acquired a Nexus 6P.
TWRP is properly installed as the Recovery - twrp-3.2.3-0-angler
First thing I did with the device was flash the latest Android 8.1 Oreo version to it - angler-ota-opm7.181205.001-abb36a2f
I then installed Lineage OS 15.1, Open G Apps 8.1 (nano), and SU
From there I've done nothing but struggle with bugs and quirks. The device has been re-imaged several different times, with different variations of the above setup, and one of the main things I need to get working (Android Auto) keeps failing. Does anyone have any idea why Android Auto keeps pulling up the error "Google Play Services doesn't seem to be working right now"
All of the suggestions I've found online have failed. Screenshots have been provided for the version info and error. I've already cleared the data caches and tried to re-install and re-flash the device.

I got pissed and went back to JUST the stock OTA for testing/verification. With the stock rom there are no issues. Seems like Lineage OS 15.1 on the Nexus 6P has some bugs to work out. A fully functional stock phone is better then being frustrated.
If anyone can confirm I'm not crazy or explain what I missed while troubleshooting that would be awesome.

GTF696 said:
I got pissed and went back to JUST the stock OTA for testing/verification. With the stock rom there are no issues. Seems like Lineage OS 15.1 on the Nexus 6P has some bugs to work out. A fully functional stock phone is better then being frustrated.
If anyone can confirm I'm not crazy or explain what I missed while troubleshooting that would be awesome.
Click to expand...
Click to collapse
Try magisk as root method insted of su...
Other than that, cant think any other solution

GTF696 said:
I recently acquired a Nexus 6P.
TWRP is properly installed as the Recovery - twrp-3.2.3-0-angler
First thing I did with the device was flash the latest Android 8.1 Oreo version to it - angler-ota-opm7.181205.001-abb36a2f
I then installed Lineage OS 15.1, Open G Apps 8.1 (nano), and SU
From there I've done nothing but struggle with bugs and quirks. The device has been re-imaged several different times, with different variations of the above setup, and one of the main things I need to get working (Android Auto) keeps failing. Does anyone have any idea why Android Auto keeps pulling up the error "Google Play Services doesn't seem to be working right now"
All of the suggestions I've found online have failed. Screenshots have been provided for the version info and error. I've already cleared the data caches and tried to re-install and re-flash the device.
Click to expand...
Click to collapse
I got error when installed lineageos15.0 on twrp 3.2.3 , suddenly automatic restart. Can you help me dude ?

Redmi K20 Audio Completely Broken

One day my phone suddenly started crashing upon opening any app and it restart on its own. Then I tried to flash my default ROM (MIUI10 on Android 9) using Mi flash tool from my PC (Note: My phone was on MIUI 12 on Android 10 when it happened).
Now My Phone works normally except its Audio doesn't work (Eg : Apps like Youtube, Music player doesn't work). Later I updated my phone using system updater now It went back to the first case (Restarting abnormally).
After this I gave my phone to an Authorized Service Centre but they couldn't fix it and told me to replace its motherboard (which I feel like its unnecessary). I was told that they tried to install the default ROM.
Later I brought it back and rooted it and installed PixelExperience on Android 11. Now it went back to the second case (Only Audio not working).
I also went through another forum where I saw that Installing Audio Compatibility Patch, Viper4Android, Audio Modification Library (Using Magisk Manager) would solve the issue, but it didn't work either. Upon opening Viper4Android app and checking its status It shows a lot of errors (Which are attached to this thread).
Please Help Me Guys.................

I see you are from India. Recently there was a bug in official MIUI for India, so check if it was resolved. A lot of people were complaining and they removed update

Gopalakrishnan V said:
One day my phone suddenly started crashing upon opening any app and it restart on its own. Then I tried to flash my default ROM (MIUI10 on Android 9) using Mi flash tool from my PC (Note: My phone was on MIUI 12 on Android 10 when it happened).
Now My Phone works normally except its Audio doesn't work (Eg : Apps like Youtube, Music player doesn't work). Later I updated my phone using system updater now It went back to the first case (Restarting abnormally).
After this I gave my phone to an Authorized Service Centre but they couldn't fix it and told me to replace its motherboard (which I feel like its unnecessary). I was told that they tried to install the default ROM.
Later I brought it back and rooted it and installed PixelExperience on Android 11. Now it went back to the second case (Only Audio not working).
I also went through another forum where I saw that Installing Audio Compatibility Patch, Viper4Android, Audio Modification Library (Using Magisk Manager) would solve the issue, but it didn't work either. Upon opening Viper4Android app and checking its status It shows a lot of errors (Which are attached to this thread).
Please Help Me Guys.................
Click to expand...
Click to collapse
How can i contact you?

May I know for what??

About k20 broken audio. Leave it. Can you tell me what have you done after this problem?

Bought a new phone Redmi Note 10 pro

Gopalakrishnan V said:
One day my phone suddenly started crashing upon opening any app and it restart on its own. Then I tried to flash my default ROM (MIUI10 on Android 9) using Mi flash tool from my PC (Note: My phone was on MIUI 12 on Android 10 when it happened).
Now My Phone works normally except its Audio doesn't work (Eg : Apps like Youtube, Music player doesn't work). Later I updated my phone using system updater now It went back to the first case (Restarting abnormally).
After this I gave my phone to an Authorized Service Centre but they couldn't fix it and told me to replace its motherboard (which I feel like its unnecessary). I was told that they tried to install the default ROM.
Later I brought it back and rooted it and installed PixelExperience on Android 11. Now it went back to the second case (Only Audio not working).
I also went through another forum where I saw that Installing Audio Compatibility Patch, Viper4Android, Audio Modification Library (Using Magisk Manager) would solve the issue, but it didn't work either. Upon opening Viper4Android app and checking its status It shows a lot of errors (Which are attached to this thread).
Please Help Me Guys.................
Click to expand...
Click to collapse
i have the same issue, have u tried downgrade to rom based pie android?

Yup, as mentioned in the article

Gopalakrishnan V said:
Yup, as mentioned in the article
Click to expand...
Click to collapse
omg right , i'm pretty sure it's software issues. i hope someone found out how to solve it

The same issue was encountered with me also. I am in great distress right now. Tried more than 30+ ROMs (including recover, fast boot, custom, and stock), but nothing helps.
IF you find anything please update here.. THat’ll be a great help indeed!!
Here’s my thread: https://forum.xda-developers.com/t/...dphone-and-many-features-not-working.4309769/

Hello guys I have found this issue solution
1st off all you have to flast device and use oldest rom and after that you have to keep update until android 11 and miui 12.1.4 and after that you have to find and audio ic specialist if you are not getting audio then it is audio ic problem i have solved every problem but not able to find and audio ic specialist. And now I am using phone without audio .