Related
NEXUS 4,ANDROID 4.4 16S & 16O,Plantronics savor M1100 bluetooth headset or jabra bluetooth headset.Often disconnected during a call.Very high frequency,But 4.3 have not problem.What is the problem?
Find a temporary solution, as long as open WIFI, Bluetooth will be disconnected, closed WIFI, Bluetooth never broken! Currently only so used!
Final, to find a solution, just need to turn off WIFI 5G. Settings - WIFI - Advanced - Wi-Fi frequency band - 2.4GHz only ,ALL OK
Please don't use such a large text size, it's kinda annoying.
I will second you on the Bluetooth issue. I've noticed it with my car, where I usually spend some time on a call or two. It seems intermittent for me, usually starting after about 1 minute and then randomly disconnecting. Either the phone or the car BT will then reconnect, but it'll disconnect again within one to two minutes. Music streaming isn't affected by dropouts, but I have noticed some minor issues with it, such as stuttering.
Android 4.4 Kit Kat, Bluetooth issues
motokochan said:
Please don't use such a large text size, it's kinda annoying.
I will second you on the Bluetooth issue. I've noticed it with my car, where I usually spend some time on a call or two. It seems intermittent for me, usually starting after about 1 minute and then randomly disconnecting. Either the phone or the car BT will then reconnect, but it'll disconnect again within one to two minutes. Music streaming isn't affected by dropouts, but I have noticed some minor issues with it, such as stuttering.
Click to expand...
Click to collapse
I also have the same issue after 4.4 install. Using Nexus 4. I have contacted google, and as expected they can't help!
Sound is very crackly when making calls from my car.. :crying:
Well, let's see if we can't collectively determine what the problem is and at the least submit a good bug report to Google. The first thing I'm going to do is try to reproduce the issue with a standard bluetooth headset. If the problems happens there, I'll then run adb logcat and see if I can grab a log of any error messages.
I encourage anyone else having this problem to do the same and report back on this topic.
Also, to see if it's isolated to specific cars or something, I experience the issue with a 2011 Mazda 3. What is everyone else using?
motokochan said:
Well, let's see if we can't collectively determine what the problem is and at the least submit a good bug report to Google. The first thing I'm going to do is try to reproduce the issue with a standard bluetooth headset. If the problems happens there, I'll then run adb logcat and see if I can grab a log of any error messages.
I encourage anyone else having this problem to do the same and report back on this topic.
Also, to see if it's isolated to specific cars or something, I experience the issue with a 2011 Mazda 3. What is everyone else using?
Click to expand...
Click to collapse
My headset is Plantronics savor M1100 & Jebra BT2010,Same problem.
I am experiencing the same issue with my Alpine CDE-136BT. Running krt16s.
Sent from my Nexus 4 using Tapatalk
Also, to get some extra data, please indicate if you upgraded via official OTA, factory image, or some other method. Also, please say if you did a factory reset or if you did not.
In my case, I saw this using the old 16O factory image (no reset) and also with the 16S OTA from 66Y (4.3), no reset again.
Also worth noting if you have WiFi on and if it's pulling data at the same time...
Sent from my Nexus 4 using Tapatalk
In the car I don't get any problems with quality and/or stuttering, but the BT volume control doesn't seem to work
Also, the 'volume' sent to my car is very low, causing me to control the volume by the car (and putting it very loud)
I didn't try it with a call yet, just music, I'm going to try a call when I get the chance
Here, I'm using the factory image KRT16O, did a clean flash, and the car is a 2013 ford focus
I had the same problem on 4.4 ROMs that don't have the proper Nexus 4 libraries. I switched ROMs, and my problem is gone.
Sent from my Nexus 4 using XDA Premium 4 mobile app
kakabartz said:
but the BT volume control doesn't seem to work
Also, the 'volume' sent to my car is very low, causing me to control the volume by the car (and putting it very loud)
Click to expand...
Click to collapse
Volume seems to still be independent between the headset and the phone. When in a call, use the phone volume keys to raise the volume to near max (I usually put it two presses down from max) and use the car/headset volume to further adjust as needed. Same way with music.
trackmastersteve said:
I had the same problem on 4.4 ROMs that don't have the proper Nexus 4 libraries. I switched ROMs, and my problem is gone.
Click to expand...
Click to collapse
That would be a good option except some people will actually want to be on stock. I would hope Google has the proper libraries for the stock KRT16S factory images and OTA files.
motokochan said:
Volume seems to still be independent between the headset and the phone. When in a call, use the phone volume keys to raise the volume to near max (I usually put it two presses down from max) and use the car/headset volume to further adjust as needed. Same way with music.
Click to expand...
Click to collapse
Yes, thats how it is supposed to work, but I actually can't control the volume at the device at all
Leaving it in the max or the minimum sends the same volume to the car, and its very low
All my other android devices work properly, so its something with my nexus
motokochan said:
Also, to get some extra data, please indicate if you upgraded via official OTA, factory image, or some other method. Also, please say if you did a factory reset or if you did not.
In my case, I saw this using the old 16O factory image (no reset) and also with the 16S OTA from 66Y (4.3), no reset again.
Click to expand...
Click to collapse
16O is full factory image,all clear,two wipe,16S too.not OTA
Definitely a 4.4 bluetooth problem
motokochan said:
Also, to get some extra data, please indicate if you upgraded via official OTA, factory image, or some other method. Also, please say if you did a factory reset or if you did not.
In my case, I saw this using the old 16O factory image (no reset) and also with the 16S OTA from 66Y (4.3), no reset again.
Click to expand...
Click to collapse
I am using TMo OTA image on a Nexus 4. Was rock solid on car connection (Nissan Leaf) until 4.4. My wife's Samsung Galaxy S3 is not on 4.4 and still works great. Problem for me is exactly as described earlier, 1-2 minutes connected then intermittently cutting out so bad it is unusable as a bluetooth connection. Show stopper.
Tested today using a Morotola Elite Flip BT headset and also with my car (while hooked up and logging via adb) while in the garage. I could not reproduce the issue after over 10 minutes of talk. We'll see how it does on an actual drive tomorrow.
climber_paul said:
Problem for me is exactly as described earlier, 1-2 minutes connected then intermittently cutting out so bad it is unusable as a bluetooth connection. Show stopper.
Click to expand...
Click to collapse
Yep, that's what I was seeing. Hopefully someone will be able to get to the bottom of this. If you don't mind taking a laptop into your car, try using it while stationary and grabbing the log output from adb. If the issue occurs, there might be something in the log that can help diagnose the problem.
linkabc said:
NEXUS 4,ANDROID 4.4 16S & 16O,Plantronics savor M1100 bluetooth headset or jabra bluetooth headset.Often disconnected during a call.Very high frequency,But 4.3 have not problem.What is the problem?
Click to expand...
Click to collapse
I think I'm seeing more problems when using Bluetooth at the same time as WiFi is pulling data on it's 2.4Ghz setting (same band as Bluetooth). Can those with Bluetooth issues confirm they persist with WiFi disabled?
same intermittent bluetooth dropout
I wiped my phone before installing 4.4 factory image (16S).
I'm seeing phone bluetooth connection with car drop and reconnect about every 2 to 3 min. while in call. No problem with bluetooth media streaming.
jkang29 said:
I wiped my phone before installing 4.4 factory image (16S).
I'm seeing phone bluetooth connection with car drop and reconnect about every 2 to 3 min. while in call. No problem with bluetooth media streaming.
Click to expand...
Click to collapse
Same problem here. Never had it on 4.3. Currently solved it by using old (from 4.3) bootloader and 0.84 radio.
Took this tip from other thread on XDA.
I also disable wifi when on call (using tasker) - but this along do not solve the disconnect/connect issue. However, this will fix the
call interference in the first 5-10 sec of the call.
Can somehow bootloader and/or radio affect this issue ?
BTW, on 4.4 I finally have stable 5 GHz WiFi connection. So Google definetly fixed something in WiFi code which can now create an issue with the Bluetooth.
Nexus 4 - 4.4
I also experience the stutter when listening to bluetooth headphones, only since the update, 4.3 worked beautifully. It stutters any time I unlock the phone or lock it, very annoying. I'm using Bludio R's, although from what I've read most people are experiencing it regardless of BT type.
Edit: For anyone else experiencing the stuttering; I found a link on the google support where someone else had this issue. Someone mentioned it went away if you turn the screen lock sound off. Haven't had a chance to test as I have no BT headsets in the office, but thought I'd share.
Up for all
Hey guys,
this new android related issue where streaming music via bluetooth is a pain in the ass, as there are only two volume levels (absolutely loud and the opposite) is really annoying.
Is there any statement from google, if and when it'll be fixed or is there even a fix already?
I cannot imagine how sth like this got into a final release...
Stream every single day on a 45 minute commute via GPM and Spotify (Bluetooth to car) and never encountered this... Seems odd. I'll keep an eye out but haven't seen it yet!
Sent from my Nexus 6P using Tapatalk
Delboyd12 said:
Stream every single day on a 45 minute commute via GPM and Spotify (Bluetooth to car) and never encountered this... Seems odd. I'll keep an eye out but haven't seen it yet!
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
is a common issue with 6.0.1 and several bluetooth devices (i have a creative roar box), just search the forums here.
I'm usually ok with blue tooth streaming to my car as well as to my Polaris speaker. No issue with my Huawei watch either that I'm aware of.
(Sent via my mobile device)
I'm having a ton of bluetooth issues with this phone sad as I *love* this phone..
But I listen to podcasts daily (while biking/running./in the car) and it keeps cutting out on me.. like 2-3 times/minute.. that's using the bluetooth in-car, as well as two different bluetooth headsets
BTW phone calls are fine - this is just A2DP bluetooth stereo..
on 6.0.1 stock (rooted)
-mark
Edit - seems worse when I'm near my wifi router; although still having issues w/ wifi off..
I had some issues with bluetooth audio cutting out after the phone had been sitting for a while. I added the media apps (music, youtube) to the not optimized list under battery settings and now it works fine.
stream every day from google music app to my vw golfs system via bluetooth and never cut out once or had any issues. Im stock non rooted 6.0.1
It's a wide issue have a look here https://code.google.com/p/android/i...ry Stars&groupby=&sort=&id=189188#makechanges for the people who are having the issue make a comment and Hit the star so Google understands what's going on as they have it as a low priority
Heinous said:
I had some issues with bluetooth audio cutting out after the phone had been sitting for a while. I added the media apps (music, youtube) to the not optimized list under battery settings and now it works fine.
Click to expand...
Click to collapse
I'm going to try your suggestion here... This is infuriating as I dig the phone so far (mostly).
Grumpy Bob said:
I'm going to try your suggestion here... This is infuriating as I dig the phone so far (mostly).
Click to expand...
Click to collapse
Good luck.
Heinous said:
Good luck.
Click to expand...
Click to collapse
No joy. I did your suggestion in conjunction with a few others and I'm still getting audio hits. Did the following to no avail:
- Uninstalled an app called "gasbuddy" which has been reportedly giving users issues with BT
- Messed with a few settings in Developer Options
- Cleared Cache
Did those listed above plus your suggestion and it still doesn't work properly. The only thing that is (albeit moderately) reliable is to completely unpair, forget device, repair, and update permissions. How frustrating every time I get in the car. Additionally, I've been getting SERIOUS BT phone problems. The caller on the line cannot hear me nearly at all. It's not my car's BT unit either, as I've troubleshooted with other phones. I have to switch to handset speakerphone. I feel like I'm in the 90s again. I'm massively bummed out since I spend a lengthy portion of time in my morning/evening commutes. BT is the one thing I can't do without. What a drag.
Grumpy Bob said:
No joy.
Click to expand...
Click to collapse
Does it work with other Bluetooth devices, or do you have other phones to test in your car? Might be an issue with the car or even something google/hauwei can fix under warranty.
Heinous said:
Does it work with other Bluetooth devices, or do you have other phones to test in your car? Might be an issue with the car or even something google/hauwei can fix under warranty.
Click to expand...
Click to collapse
Thanks for the reply but yeah that's what I meant when I said - "as I've troubleshooted with other phones."...
As to your other point, this is actually my second 6p. I RMA'd one a few weeks back for the same issue - I thought the same thing.
So frustrating. Like nailing jell-o to the wall.
I found what was causing my Bluetooth issues with my Chevy Malibu. The app weather bug was messing with my phone Bluetooth and battery drain. After I deleted the app my Bluetooth works fine and my phone now sleeps with doze correctly...
Sent from my Nexus 6P using XDA Free mobile app
cables2590 said:
I found what was causing my Bluetooth issues with my Chevy Malibu. The app weather bug was messing with my phone Bluetooth and battery drain. After I deleted the app my Bluetooth works fine and my phone now sleeps with doze correctly...
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
I was having the same issue, both with BT headphones, BT speaker, and my Android Wear watch. I tried factory resets on both phone and watch, and forgetting all BT connections and re-pairing to no avail. I Factory reset my phone again, and didn't add my Amber Weather Widget back to my home screen and all was well. As soon as I added it...Bt went to hell again. Deleted the app and now I'm having no problems. Not sure why a weather app would cause BT to act up, but it sure did in my case.
Uuuh. This is ultra frustrating. Using my smartphone for business and private stuff, so it has to re reliable. Hearing music is a pain in the ass, really. Doesn´t matter if I connect it to my Bose Soundlink Mini, my Philips NFC/Bluetooth Dongle...interruptions all over the place.
BTW: I don´t have any weather widget installed, so I have absolutely no clue what to try next. Delete all paired devices is a no go, really.
PS: And it´s not only interruptions - music kind of gains speed after those interruptions.
Grumpy Bob said:
No joy. I did your suggestion in conjunction with a few others and I'm still getting audio hits. Did the following to no avail:
- Uninstalled an app called "gasbuddy" which has been reportedly giving users issues with BT
- Messed with a few settings in Developer Options
- Cleared Cache
Did those listed above plus your suggestion and it still doesn't work properly. The only thing that is (albeit moderately) reliable is to completely unpair, forget device, repair, and update permissions. How frustrating every time I get in the car. Additionally, I've been getting SERIOUS BT phone problems. The caller on the line cannot hear me nearly at all. It's not my car's BT unit either, as I've troubleshooted with other phones. I have to switch to handset speakerphone. I feel like I'm in the 90s again. I'm massively bummed out since I spend a lengthy portion of time in my morning/evening commutes. BT is the one thing I can't do without. What a drag.
Click to expand...
Click to collapse
Yep,I have the same exact issue with phone calls, the caller cannot hear me at all and I switch to speaker. This is my second phone and they both did the same thing, connects, fine for a few seconds, then gets muted or something and have to switch to speaker. My notes never did this and it's super making me mad! I'm going to call google and try to return this phone. It's BT totally broken.
I might be giving up on the phone very soon. I'm bummed. I really dig it, but BT is such a HUGE part of my life at this point that it's impossible for me to own a phone that falters in that respect. Ugh. How disappointing.
I even signed up for the new Android N beta testing, hoping that would remedy the situation. Nope.
I would like to keep the phone but I'm back to using my OnePlus One because it's a more capable phone due to it having stable custom ROMs available. Newegg won't take the Axon 7 back because I found out they have a no return policy on non contract phones. I'd rather not sell it for a loss but the phone is useless to me at the moment.
The custom ROMs I've tried are close but the no audio call bug is a show stopper. I'd like the phone portion of the phone to work properly. <--- Reported fixed with light patch v1.2 experimental
Also, the Bluetooth is not working for call management on every custom ROM I've tried except for Pure Nexus. If it works on Pure Nexus why can't it be made to work on other AOSP ROMs and LOS based ROMs? Can the Bluetooth stack (if that's even the right term) be pulled from Pure Nexus and be applied to other custom ROMs? Could a flashable ZIP be created to implement Bluetooth as described above on custom ROMs?
I'm not positive, but I think you might get in trouble, or your post deleted for trying to sell your device on here. You should be able to get about 300 out of it on swappa or ebay.
Try BadBoy rom. It's based on the zte stock rom but has some custom aspects. Runs smooth with better battery life and much better camera than any of the Lineage based roms I've tried.
ThePublisher said:
I'm not positive, but I think you might get in trouble, or your post deleted for trying to sell your device on here. You should be able to get about 300 out of it on swappa or ebay.
Try BadBoy rom. It's based on the zte stock rom but has some custom aspects. Runs smooth with better battery life and much better camera than any of the Lineage based roms I've tried.
Click to expand...
Click to collapse
Yeah you're prolly right. I'll excise the last part. I tried Bad Boyz. It's great but I can't do stock based. I've come to rely on all the tweaks in custom ROMs. I should have done more research prior to buying the phone. I need a tweaker's phone like the OnePlus 5. Thank you for your response.
I guess if you like downgrading your display, paying more, and getting jelly scrolling as a thank you then the OnePlus 5 would be for you.
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Whoooo? said:
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Click to expand...
Click to collapse
Call bug is due tu Google now app, disable OK Google hot word. It solved mine and others too.
---------- Post added at 07:22 AM ---------- Previous post was at 07:17 AM ----------
Doc Ames said:
I would like to keep the phone but I'm back to using my OnePlus One because it's a more capable phone due to it having stable custom ROMs available. Newegg won't take the Axon 7 back because I found out they have a no return policy on non contract phones. I'd rather not sell it for a loss but the phone is useless to me at the moment.
The custom ROMs I've tried are close but the no audio call bug is a show stopper. I'd like the phone portion of the phone to work properly. Also, the Bluetooth is not working for call management on every custom ROM I've tried except for Pure Nexus. If it works on Pure Nexus why can't it be made to work on other AOSP ROMs and LOS based ROMs? Can the Bluetooth stack (if that's even the right term) be pulled from Pure Nexus and be applied to other custom ROMs? Could a flashable ZIP be created to implement Bluetooth as described above on custom ROMs?
Click to expand...
Click to collapse
Call bug is due tu Google now app, disable OK Google hot word. Phone is always listening to OK Google to activate Google assistant or search that's why it disabling mic in audio calls sometime...
ArgonautPollux said:
I guess if you like downgrading your display, paying more, and getting jelly scrolling as a thank you then the OnePlus 5 would be for you.
Click to expand...
Click to collapse
Thank you. That's very helpful.
Laleka said:
Call bug is due tu Google now app, disable OK Google hot word. Phone is always listening to OK Google to activate Google assistant or search that's why it disabling mic in audio calls sometime...
Click to expand...
Click to collapse
The one time I had the call bug I'm pretty sure I had "OK Google" hotword detection turned off. Although I hardly used the phone. I'll bear it in mind if I fire up the Axon 7 again.
Doc Ames said:
The one time I had the call bug I'm pretty sure I had "OK Google" hotword detection turned off. Although I hardly used the phone. I'll bear it in mind if I fire up the Axon 7 again.
Click to expand...
Click to collapse
I had success getting rid of the call bug flashing Light Patch v1.2 - experimental.
Whoooo? said:
Hi there,
I haven't looked into it yet (had no problems with the no audio call bug at first, but now it started showing up), but I'm pretty sure the bug can be 'hidden' with some tasker script (phone app starts, speaker off/on or so)...
So if you are a tweaker, you are likely rooted anyway and this might be an option...
Click to expand...
Click to collapse
That's a really good idea to use a Tasker task. I wonder if Bluetooth will ever be fixed though. Problem is that Bluetooth connectivity issues only happen with some car head units. It seems like devs aren't looking to fix Bluetooth on custom ROMs because they don't think there's an issue.
piet8stevens said:
I had success getting rid of the call bug flashing Light Patch v1.2 - experimental.
Click to expand...
Click to collapse
I heard another member mention that light patch fixes the call bug. I thought he was mistaken because I'm pretty sure I had light patch v1.1 installed when the call bug happened to me. Sounds like v1.2 preview will fix it. I'm going to count the call bug portion of my question as solved since there are workarounds and everyone recognizes it as a problem so it will get fixed eventually.
The Bluetooth remains a showstopper though. I would gladly pay a significant sum if somebody could make a flashable zip that could fix Bluetooth for custom ROMs. It works in Pure Nexus so having BT work in AOSP ROMs is definitely possible. Hopefully for LOS ROMs too.
Also for me the showstopper/deal breaker is that the phone loses it's loud speaker volume in custom ROMs. I use it very often.
Doc Ames said:
I heard another member mention that light patch fixes the call bug. I thought he was mistaken because I'm pretty sure I had light patch v1.1 installed when the call bug happened to me. Sounds like v1.2 preview will fix it. I'm going to count the call bug portion of my question as solved since there are workarounds and everyone recognizes it as a problem so it will get fixed eventually.
The Bluetooth remains a showstopper though. I would gladly pay a significant sum if somebody could make a flashable zip that could fix Bluetooth for custom ROMs. It works in Pure Nexus so having BT work in AOSP ROMs is definitely possible. Hopefully for LOS ROMs too.
Click to expand...
Click to collapse
Can you expand a bit on what "Bluetooth is not working for call management on every custom ROM" means? I use bluetooth with my car and have no issues.
piet8stevens said:
Can you expand a bit on what "Bluetooth is not working for call management on every custom ROM" means? I use bluetooth with my car and have no issues.
Click to expand...
Click to collapse
Audio streaming with AVRCP works fine. However the head unit (Kenwood KMM-BT515HD) shows a status of "Connected (no phone)" in Android Bluetooth settings. This means that I can't use my deck to make/answer calls or use voice commands. It works as expected on stock and on Pure Nexus. Others are having this issue too. I know a couple members had issues on Nissan decks and one that I know of had a BMW deck.
Does anyone get voice echo during voice calls on custom roms?
I'm looking to buy the Axon 7 soon, but the voice echo would be a dealbreaker if it exists.
( it's currently an issue with the custom roms I've tried on my Xperia XZ - if I call anyone they complain that they can hear an echo of their voice )
Waancho said:
Also for me the showstopper/deal breaker is that the phone loses it's loud speaker volume in custom ROMs. I use it very often.
Click to expand...
Click to collapse
You need to install Dolby digital
Im on RR build from Jun 11, connect's to my hyundai veloster oem headunit tru bluetooth with 0 issues, it can download my contacts, route calls perfectly fine 0 issues what so ever, the mic bug i get it once in a blue moon, and the 720p/1080p/2k/4k 60FPS slow motion videos on youtube is the other issue, besides that its my daily driver for months now.
rafyvitto said:
Im on RR build from Jun 11, connect's to my hyundai veloster oem headunit tru bluetooth with 0 issues, it can download my contacts, route calls perfectly fine 0 issues what so ever, the mic bug i get it once in a blue moon, and the 720p/1080p/2k/4k 60FPS slow motion videos on youtube is the other issue, besides that its my daily driver for months now.
Click to expand...
Click to collapse
Whatever the issue is it only causes connection problems (i.e. "Connected (no phone)" ) with some head units. I should try connecting to my roommate's Toyota. I bet it would connect as a phone just fine. There was an issue with BT in LOS that was causing AVRCP (remote control, song info) to not work with some head units. I'm guessing the devs couldn't solve the underlying issue because the fix was to roll back the AVRCP version. It seems there are still compatibility issues with Bluetooth in LOS and AOSP ROMs (save Pure Nexus).
If I could get BT to work fully with my car I would absolutely use RR as my daily driver. Unfortunately the phone is sitting in the box right now until I lose patience and sell the phone or the BT gets fixed. Sucks because I was totally thrilled with the phone after installing and setting up AOSPExtended. Then I got into my car and noticed the issue forcing me back to the dusty, but trusty OnePlus One.
supergear said:
You need to install Dolby digital
Click to expand...
Click to collapse
Hi there,
Thanks a lot for the info (new to me) - to verify:
Are you referring to
https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342
or is there another (preferable safe/easy to install) version one would need?
Thanks again!
Stock ROM from Seicane ~4 weeks ago. The unit pairs with the cell phone for ~2 seconds and then drops the connection. If I'm quick, I can actually place a call that goes through the handset and places a call that uses the handset speaker.
I tested on a Leeco Pro3 and an Alcatel phone. This is a show stopper but the unit is installed and it was shipped direct from China so replacing it is a big deal. HELP!
Has anyone else seen this?
i have this unit, I have not had any issues with Bluetooth. I did a 6 hour road trip, listening to Bluetooth the whole time. I was connected to a Moto Z2 Force.
What is your About Device screen showing? maybe you need an update, i just updated my MCU to the latest KSP
https://forum.xda-developers.com/an...-development/mtcd-ksp-firmware-t3607398/page4
CadillacMike said:
i have this unit, I have not had any issues with Bluetooth. I did a 6 hour road trip, listening to Bluetooth the whole time. I was connected to a Moto Z2 Force.
What is your About Device screen showing? maybe you need an update, i just updated my MCU to the latest KSP
https://forum.xda-developers.com/an...-development/mtcd-ksp-firmware-t3607398/page4
Click to expand...
Click to collapse
Thanks CadillacMike. I checked and I have the same MCU as you do. So I did a factory reset (on Seicane's advice, sort of, it's little hard to guess what they were trying to say). It didn't fix anything but blew away IGO and maybe a few other things.
Then I tried a 3rd phone; my son's Moto G4 paired quickly and perfectly.
Next up:
Recover the missing pieces from the factory reset.
Update/change/whatever to get my phone to behave.
EDIT: Got it working. Burned my phone with a custom ROM: ResurrectionRemix. No idea why this worked but the hint came from some else with a similar andoid head and a LeeCo phone. Likely hopeless for the Alcatel phone but that is unimportant for me.
As small thank, maybe you would enjoy a Jeep icon for your IGO map? Put the attached files in \igo\content\car Then in settings -> map options change the 3d car to one of the selected
hey thanks, but i dont use iGo, i just use Google Maps.
I also got Seicane headlights:
https://youtu.be/N4W8oE0twsM
and here are a couple of videos about the same head unit:
https://youtu.be/5cavKcYauSk
https://youtu.be/MWVsNWZjeCQ
I updated my software and it looks cool
Image not found...
CadillacMike said:
I updated my software and it looks cool
Click to expand...
Click to collapse
What did you update to? The pictures aren't loading for me.
I like unit so much that I might leave it alone for awhile and have something to play with later when a 10" screen in the dash seems like an everyday thing.
It was the October 26th update for PX3 that was in the Dasaita thread
Pictures aren't loading for me either
CadillacMike said:
It was the October 26th update for PX3 that was in the Dasaita thread
Click to expand...
Click to collapse
I can see the pictures now. Looks great, thanks for the pictures. Did you have to reinstall all the apps and settings? Now that everything is working on mine I am trying to resist rehashing the whole thing.
Well, trying to resist anyway.
tlyonstlyons said:
I can see the pictures now. Looks great, thanks for the pictures. Did you have to reinstall all the apps and settings? Now that everything is working on mine I am trying to resist rehashing the whole thing.
Well, trying to resist anyway.
Click to expand...
Click to collapse
No, there a box you can check to wipe everything, but I didnt check it.
It kept all my stuff intact
tlyonstlyons said:
Stock ROM from Seicane ~4 weeks ago. The unit pairs with the cell phone for ~2 seconds and then drops the connection. If I'm quick, I can actually place a call that goes through the handset and places a call that uses the handset speaker.
I tested on a Leeco Pro3 and an Alcatel phone. This is a show stopper but the unit is installed and it was shipped direct from China so replacing it is a big deal. HELP!
Has anyone else seen this?
Click to expand...
Click to collapse
Whats happened on the mazdas with all chinese units
People were having issues having their cell phones even connect. It was duento the issue of having the device paired with the old radio.. which i had with my so480.
I had to reinstall the old radio, unpair all devies from it then reinstall the new radio and pair up and has worked fine ever since. Now as to why i dont know as the aftermarket radio used its own bluetooth connections as the canbus only let the radio sync up with the steering wheel functions. Hopefully you get it fixed.
Hey guys,
I installed the OpenBeta 1 on my OP5, and it seems I have bluetooth connection issues with my car. It keeps connecting, then disconnecting all the time... I tried deleting the sync, resyncing everything but still the same issue.
Anyone else? I'm using Blu spark kernel (I'll have to try it with stock kernel) and stock OOS, clean flash.
Thanks!
Same here with open and leaked betas. It may work for half an hour or just a few minutes. Pretty annoying, but it's the only issues I'm facing with the betas.
californicated said:
Same here with open and leaked betas. It may work for half an hour or just a few minutes. Pretty annoying, but it's the only issues I'm facing with the betas.
Click to expand...
Click to collapse
What kernel are you using?
matssa said:
What kernel are you using?
Click to expand...
Click to collapse
Stock
Open beta 1 here, everything stock, no problem at all with all my BT devices (car, speaker, watch...)
I haven't had any issues on Open Beta 1 either, use the BT in my car on a daily basis for at least an hour at a time.
On Open Beta 1 the sound via Bluetooth connected to speaker is very quiet compared to stable 4.5 ... also, I tried all available codecs with no difference.
Anyone else is experiencing this, too?
Same with leaked beta 3. I'm already in contact with OnePlus bughunters and sending them logs....
californicated said:
Same here with open and leaked betas. It may work for half an hour or just a few minutes. Pretty annoying, but it's the only issues I'm facing with the betas.
Click to expand...
Click to collapse
IlD4nX said:
Open beta 1 here, everything stock, no problem at all with all my BT devices (car, speaker, watch...)
Click to expand...
Click to collapse
daafisch said:
I haven't had any issues on Open Beta 1 either, use the BT in my car on a daily basis for at least an hour at a time.
Click to expand...
Click to collapse
TheCondorITA said:
Same with leaked beta 3. I'm already in contact with OnePlus bughunters and sending them logs....
Click to expand...
Click to collapse
I made some testing, and it appears that when the phone is connected without telephone and notifications, music is played correctly without any issues. However when connecting the phone and notification (through the Bluetooth settings), it stops the music and phone keeps connecting and disconnecting.
I'll have to try with the Ok Google disabled through headset.
Did you guys test with telephone and notification on through car? Strange that some have issues and others don't...
Sent from my OnePlus5 using XDA Labs
Tested and no change. Using stock dialer as well. Amyone else?
Sent from my OnePlus5 using XDA Labs
Tested without updating on Oreo, still the same issue. Anyone on Oreo?
Sent from my OnePlus5 using XDA Labs
My problem with Bluetooth on Oreo is that everytime I connect to a device it resets the media volume to like 25%. Having to turn it up to 100% every time I want to use a Bluetooth device is really ridiculous.
ArkAngel06 said:
My problem with Bluetooth on Oreo is that everytime I connect to a device it resets the media volume to like 25%. Having to turn it up to 100% every time I want to use a Bluetooth device is really ridiculous.
Click to expand...
Click to collapse
Same here, its annoying. Though, the connection itself is stable.
ArkAngel06 said:
My problem with Bluetooth on Oreo is that everytime I connect to a device it resets the media volume to like 25%. Having to turn it up to 100% every time I want to use a Bluetooth device is really ridiculous.
Click to expand...
Click to collapse
ulxerker said:
Same here, its annoying. Though, the connection itself is stable.
Click to expand...
Click to collapse
Yup me too, did you try the leaked version 3? BTW do you guys connect using phone and notifications too? To see if it bugs on your end as well.
Sent from my OnePlus5 using XDA Labs
Bluetooth issues after Beta 1 update
Hi there,
I have issues with my OP5 since I updated to Oreo Beta 1.
Randomly Bluetooth audio cuts several times during 1 or 2 minutes (sometimes more) so music is awful. Impossible to hear...
I only have this issue since I updated to the beta, so please solve this for the official release.
I use Bluetooth music play in my car (Toyota Auris 2011), with headphone (Sony MDR-ZX770BN), Speaker (Harman Kardon HK OMNI 10), and I have the same issue on all of them.
One question, is it possible to perform a rollback to stock ROM? All my attempts were unsuccessful... Invalid zip archive...
Please help!!!
hopefully these issues have been fixed in Open Beta 2: http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_openbeta_2/ ("Improvements for Bluetooth audio") ... I'm gonna check this out tonight.
ulxerker said:
hopefully these issues have been fixed in Open Beta 2: http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_openbeta_2/ ("Improvements for Bluetooth audio") ... I'm gonna check this out tonight.
Click to expand...
Click to collapse
OK thanks for your help. On my side I don't have issues with audio playback on Bluetooth in car or using Bose, however call issues with my car (and no issues with my gear S3, which is strange...).
Could you test the call in your car please? I'm on LB4 (leaked beta)
Sent from my OnePlus5 using XDA Labs
I get this too. Also, sometimes on Bluetooth, the song skips a second or two every second when playing music ..
ulxerker said:
hopefully these issues have been fixed in Open Beta 2: http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_openbeta_2/ ("Improvements for Bluetooth audio") ... I'm gonna check this out tonight.
Click to expand...
Click to collapse
on OB 2 it still resets the volume to 25% on each connect.
ulxerker said:
on OB 2 it still resets the volume to 25% on each connect.
Click to expand...
Click to collapse
Crap... And still issues when calling?
Sent from my OnePlus5 using XDA Labs