I just got a new 2015 VW Golf and a new Moto G. Before the Moto G, I had a OnePlus One and it was having this problem as well. It's actually the reason I ended up with a new Moto G, because after two weeks or so of troubleshooting I couldn't figure out what was causing the problem. Immediately upon pairing the Moto G it's been having skipping/stuttering issues with Spotify and Youtube.
My first thought was that it obviously must be an issue with the car, but it isn't, as I've tried many different phones with the car (extensively) and they all work just fine, with the exception of the Moto G (2015) and the OnePlus One. I'm at wits end after having spent so much time on this issue.
Seems to be a compatibility issue between certain phones(or software) and this car(or multiple cars), but that some work just fine. The phones seem to work fine with other bluetooth devices, but just not this one.
On the OnePlus One here are some of the things I tried (there were a lot so I can't possible remember them all):
1. Repaired bluetooth
2. turned off wifi.
3. turned off bluetooth contact sharing
4. restarted device
5. hard reset
6. wiped data and cache in recovery mode
7. reinstalled spotify/wiped app date and cache.
8. toggled nu/awesome player in developer options
9. rooted/unlocked bootloader and flashed many different roms, some with CM12 base and some with out. I had heard Oxygen OS had less problems, but still didn't fix the issue.
10. Tried the ro.bluetooth.request.master=true fix in build.prop
11. av.offload.enabled=true to false
Is anyone else having this issue? There are a lot of vague threads out there about other phones and streaming issues via bluetooth, but I'm not sure what applies to this phone or what doesn't.
Some basic troubleshooting done on the Moto G
1. Repaired bluetooth
2. turned off wifi.
3. turned off bluetooth contact sharing
4. restarted device
5. hard reset
6. wiped data and cache in recovery mode
7. reinstalled spotify/wiped app date and cache.
8. toggled nu/awesome player in developer options
Any help would be great. Might just return the device if I can't get it working.
yeah, I have the same issue. Data and cache wiping in recovery mode sorted out for a couple of months but now I am getting the stuttering again. I use Bluetooth for all my listening and I hate this bug.
I have the same problem on my Moto G. Seems like some CPU/RAM issue since I've notice it got worse when I try to use any other program with spotify. But it's good to know that other ROMs don't work. I was about to test that.
Related
any insight would be appreciated. My AT&T note three has for some reason stopped Being able to detect any Bluetooth devices. It was working one second then it suddenly stoped. All devices that were previously connected no longer display in the list. I know it is not a hardware issue because this has happened before. Doing a complete reset to factory settings solved it. Don't want to completely redo phone again. Any thoughts?
Stock everything beaides nova launcher if that helps
(EDIT) Solution: I remember a long time ago when I went from stock to CM11 I lost all GPS capability. It was determined this is just a random occurance and all you need to do is flash back to stock, get a lock, then reflash CM11 until the lock sticks. With this previous tactic, I applied the same principle to the bluetooth issue since it was apparent I had a unique situation and most did not have issues. Steps taken to fix the bluetooth issue:
Step 1: Backup everything to external SD
Step 2: RUU back to GPE 4.4.2 (found VZW variant on XDA)
Step 3: OTA Update to 4.4.4 because the build needs to be higher than 4.4.2's build
Step 4: Ran bluetooth through car for a little bit and also ensured I had a GPS lock
Step 5: Reflash CM Recovery
Step 6: Wiped /system, /data (sdcard), /cache, and /dalvik
Step 7: Flashed CM12. Restored via Titanium Backup and on 3rd day without bluetooth dropping out yet (fingers still crossed)
Obviously I did not provide much detail on the steps because there are numerous tutorials already. However, if someone would like more explicit instructions just ask.
----------------------------
Greetings. A few weeks ago I made the jump from CM11 to CM12. I first did a dirty flash and a had a few problems so I ultimately did a clean flash. I transferred everything to my external and wiped everything else (system, data, dalvik, cache) then reinstalled CM12. Both on CM11 and CM12 I noticed that my bluetooth, when connected to my car streaming audio, would randomly disconnect. The phone would still think it was connected, but my headunit would lose the connection. This never happened on CM11, leading me to believe the headunit is not the culprit. I've erased the bluetooth cache, wiped cache in recovery, and deleted and repaired numerous times.
Android 5.0.2
CM version 12-20150320-NIGHTLY-m8 (has been happening since I first switched in the beginning of March)
Kernel: 3.4.0-g1ac088b
What I've observed:
- I cannot force the disconnect through any specific action
- It almost exclusively (cannot say for 100%) happens when the screen is off
- It does not happen every time the screen is off
- I've tried in both performance and balance mode -- no difference
- I've never had this problem before going to CM12
- When the connection is working, everything works as expected (no volume issues, can control through headunit, etc)
- If I disable then reenable bluetooth the devices will reconnect and work until the random disconnect occurs again
- When connected as phone only, it does not disconnect. It is only the audio profile (A2DP I believe)
Has anyone else observed this as well? Furthermore, does anyone have a solution? I've scoured the interwebs and I found a few issues but all related to the One Plus One -- and those solutions did not work for me.
Any help is greatly appreciated. I did a CATLOG and noticed numerous bluetooth issues, but I do not have the log on me at the moment. I can recapture it and post it if it helps.
Thanks.
Bill
I'm currently on the latest CM12.1 Sultan-Mod. Last week I got a new car which supports Android Auto (Volkwsagen Columbus Headunit), at the beginning I got a connection a few times, but all the time with frequent connection losses ("Error: USB Device" shown on Headunit), the longest period it worked was about 1 hour. Today on my phone I got the message "Communication Error 7", now it's not possible to get a stable connection at all.
I've tried removing the car from the auto app and removing the auto app but without success. Has anybody been able to get a working connection between a CM12.1 device and a car?
Missing features after resetting mobile
Hi,
I am using OPO with CM 12.1. Yesterday i have reset my mobile and few apps and features (Screen Pinning,Screenshot,Menu button ) are missing after resetting my mobile. Please let e know the solution.
I've tried different CM13 Nightlies and CM12.1 without success now. Seems like Android Auto won't work with the OPO at the moment.
For future notice, I was having this same problem all of a sudden on my Nexus 6P, found how to fix it.
Uninstall updates for Google Play Services, it's a buggy install that is doing it. Found a few other forums talking about it, did it myself, and even after it re-updated, everything is working fine. I had to plug it in and unplug it several times, and it finally gave me all of the prompts again to start like new.
Recently on my Note 10+ (SM-N975U1) running stock Pie and Dec 1 2019 update, I have been experience 2 issues.
Notifications for some apps are delayed
App updates hang on Google Play Store
For the app updates, they stall with "Download Pending" or the download stalls with <100% complete.
Resolution steps that have NOT worked
Clearing cache and data for Google Play Store
Rebooting phone
Rebooting into Safe Mode
Changing from Wifi to Cell Network Data and vice versa
Stop/starting app updates
Current Workaround
Closing/swiping the Google Play Store and opening it again. It will eventually complete downloading after multiple attempts and install/update an app - you will have to repeat this continuously for every app you want to install or update.
Is there anyway to debug this without doing a complete reset?
This is a problem I've had on many phones over the last few years. It took me a while to figure it out but it's bluetooth related. More specifically, I had the "Dynamic Lock" option enabled on my Windows 10 work laptop (which basically just locks my pc when my phone gets far enough away). I disabled this and now all my notifications come immediately and play store updates work as they should. I realize that you may not have that enabled and if that is the case then turn off your bluetooth for a while and see what happens. It worked for me and several others on the samsung community forum.
mtweisenbarger777 said:
This is a problem I've had on many phones over the last few years. It took me a while to figure it out but it's bluetooth related. More specifically, I had the "Dynamic Lock" option enabled on my Windows 10 work laptop (which basically just locks my pc when my phone gets far enough away). I disabled this and now all my notifications come immediately and play store updates work as they should. I realize that you may not have that enabled and if that is the case then turn off your bluetooth for a while and see what happens. It worked for me and several others on the samsung community forum.
Click to expand...
Click to collapse
Thank you! I turned off Bluetooth but nothing happened but after I rebooted with Bluetooth off everything started to work again. Is there a permanent fix for this? I am assuming turning back on Bluetooth will cause this to happen again? The strange thing this never happened to my Note 8.
selector said:
Thank you! I turned off Bluetooth but nothing happened but after I rebooted with Bluetooth off everything started to work again. Is there a permanent fix for this? I am assuming turning back on Bluetooth will cause this to happen again? The strange thing this never happened to my Note 8.
Click to expand...
Click to collapse
I have no idea why this happens. What I do know I have had this issue on LG phones, Pixels, and Motorola's. It isn't a Samsung thing. I think it's an Android Bluetooth issue.
This is an old thread - but in case someone else finds it, I came across someone's suspicions in another thread that their Plantronics headset was causing some kind of problem with their Bluetooth. I began unplugging my Savi headset when not in use and it seems to help... YMMV.
This has been going on since Pie; made me upgrade from my Note 8 to Note 10 and it came right back. Infuriating.
You may also want to try to rub a lucky stone and do some chanting as well, because it's about as effective as hoping for a fix after all this time.
So I've recently "upgraded" my car from a Opel Zafira 2009 to a 2015 Volkswagen Golf 7 Variant(stationwagon).
In the VW there's an infotainment system, not a NAVI but still classified as MIB 1 I've figured out.
I've done a ton of searching and it seems to still be an issue with certain cars infotainment systems, I have no issues what so ever connecting my Lenovo tablet to the car and playing Spotify through that. But since there's no phone feature it's kind of not what I'm after.
I've contemplated just getting a used *insert random other brand here* and just use that until the issue is solved, but since I've done quite a bit of reading on this I see that this has been an issue since late Android 10 versions of Oxygen OS and still persists on 11...
Has anyone here found a workaround for this? Is the issue still ongoing if I use a custom rom and most important, is there a stock camera to flash on custom roms?
Needless to say, it's annoying as heck and yes I've actually done every bit of troubleshooting there is. I even reset the infotainment, removed power from it and put it back... The whole shabang so to say...
It's a bug with OnePlus and no matter what settings I use in "developer alternatives" it still keeps randomly disconnecting, sometimes after a few seconds and sometimes it's a minute and a half.
Things I've tried:
- Removed the pairing on both devices
- Removed fuses related to infotainment on car, waited 2 min and tried again
- Unplugged the infotainment from the glove compartment, waited 2 min and connected it again
- Deleted data/cache on the bluetooth app within android
- Tested another device(Lenovo tab) that worked fine.
- Hard reboot of the infotainment(10 sec power button hold)
- Rebooted the phone(obviously)
- Reset system settings on the infotainment
- Asked a VW dealer, they had no idea and wanted me to bring in the car
- Searched numerous VW forums for any updates(has to be done by a dealership I've figured and since it's working with another unit not relevant).
- Every bluetooth setting combination related to bluetooth in developer settings.
- Probably alot more, but it's been a few days now.
Note to self, the Lenovo tab is actually running android 8, so I might have to get a Android 11 device to test with as well.
This is the only community I trust when it comes to custom roms and that kind of stuff tbh, so if anyone has experienced anything similar or found a workaround, feel free to post...
Thanks in advance for any reply. If you experience this as well feel free to says so, maybe it can all be submitted to OnePlus(not that I think they would care) or something...
I've attached a video displaying the issue as well.