Database Info

[Q] Any workaround for Bluetooth MAP wakelock?

Hi!
I received my new Nexus 5 last week. Great device!
Unfortunately, I have a small problem when connecting my N5 to my car's nav (BMW 3series 2012 model, new NBT sat nav) system.
Battery drains quickly, because the Bluetooth connection prevents a deep sleep.
In particular, I get a StartingObexMAPTransaction wakelock.
I made some screenshots to illustrate the problem (Screenshots are in German, sorry. But I hope you get the idea).
Is there anything I can configure on my Nexus 5 to circumvent the wake lock?
I will inform BMW of the problem, but I really doubt there will be a fix anytime soon.
What i also observed is, that the nav system cannot display e-mails from my N5, although the MAP profile seems active. Just text messages are displayed. This worked with my previous phone (Galaxy S2 I9100, SlimBean ROM with 4.3.1).
Has anyone an idea?
Thanks for your time!

DasWerschaf said:
Hi!
I received my new Nexus 5 last week. Great device!
Unfortunately, I have a small problem when connecting my N5 to my car's nav (BMW 3series 2012 model, new NBT sat nav) system.
Battery drains quickly, because the Bluetooth connection prevents a deep sleep.
In particular, I get a StartingObexMAPTransaction wakelock.
I made some screenshots to illustrate the problem (Screenshots are in German, sorry. But I hope you get the idea).
Is there anything I can configure on my Nexus 5 to circumvent the wake lock?
I will inform BMW of the problem, but I really doubt there will be a fix anytime soon.
What i also observed is, that the nav system cannot display e-mails from my N5, although the MAP profile seems active. Just text messages are displayed. This worked with my previous phone (Galaxy S2 I9100, SlimBean ROM with 4.3.1).
Has anyone an idea?
Thanks for your time!
Click to expand...
Click to collapse
I've had this exact issue with my 2012 Prius since I got my N5. It has persisted through all OTA updates and roms like CM/Omni. I am using stock right now. I've done factory resets periodically whenever I switch roms and the problem is always there. I haven't tried 4.4.3 yet. Just like OP my phone stays awake the entire time I am driving and BBS shows StartingObexMAPTransaction for that exact amount of time.
My workaround is to pair the phone and deny it access to text messages when it asks. I give it contacts and call history but deny the SMS popup and the problem goes away. The downside is you lose SMS access on your headunit.
I don't know why reports of this are not more prevalent. I suspect it only crops up on certain cars/headunits.

[Q] Bluetooth handsfree problem

I have a Sony bluetooth head unit in my car which supports handfree and audio streaming profiles. I can play my music through the head unit just fine via bluetooth. I can also make and receive calls without problem when I am listening to the radio (ie when I am not listening to my own music). However, when I am playing my own tunes and I either make or receive a call, the head unit indicates I am on a call, it mutes the music but I just get silence through the speakers.
I used to have a Galaxy S Advance and it all worked just fine without too much configuration on the phone or head unit; basically just pair them up, make sure the right boxes are ticked in the bluetooth options and thats it.
Any idea what the problem could be? I've tried an upgrade to 4.2.2 but it didn't help...

Hi,
I have a similar problem. I can pair my s2 plus with cm11 from this thread to my car kit (Parrot MKi 9200). Playing music via phone on the car speakers works fine but when I place a call the receiving phone just gets loud static (and my voice very very silent).
I wanted to ask the developer of the cm11 I am using if he sees a way to exchange the bluetooth module (or what androis equivalent is) to the one of e.g. Android 4.1.2 because I know that one works perfectly. I am posting here because I havent reached 10 posts yet.
Of course I am open to other workarounds and ideas.
Thanks,
Kiesel

Bluetooth
Same issue here,
everything (music etc.) is okay, but the phone connection.
I'm connecting to my Ford Sync.
I can connect, but then the quality of the voice is very very bad, I can hardly understand anything...
I thing there's a configuration file in the etc/ folder, maybe that need some upgrade?!?
Hope someone can help, because I really like to keep CM11 on my phone...
Dan

This is a known problem wich has been asked 100 times before
Sent from my GT-I9105P using xda app-developers app

safariking said:
This is a known problem wich has been asked 100 times before
Sent from my GT-I9105P using xda app-developers app
Click to expand...
Click to collapse
How is this message supposed to be of any help? Of course we know that. We have seen a lot of threads. I have read the whole bug report including all the comments on googlegroups, I have browsed dozens of websites and googled my ass of. What I didnt find was an explanation (at this point I dont expect to find a fast solution anymore). After reading the googlegroups bug call I thought it was a problem with the bluetooth stack that apparently is being redeveloped by google. But here cooldevelopment said it isnt a google problem.
I fully understand that it must be annoying for you to see this question a million times but please understand, that it is also annoying (and unsatisfactory) to not know whats going on.

DeKiesel said:
How is this message supposed to be of any help? Of course we know that. We have seen a lot of threads. I have read the whole bug report including all the comments on googlegroups, I have browsed dozens of websites and googled my ass of. What I didnt find was an explanation (at this point I dont expect to find a fast solution anymore). After reading the googlegroups bug call I thought it was a problem with the bluetooth stack that apparently is being redeveloped by google. But here cooldevelopment said it isnt a google problem.
I fully understand that it must be annoying for you to see this question a million times but please understand, that it is also annoying (and unsatisfactory) to not know whats going on.
Click to expand...
Click to collapse
I know what you mean but i think the best method now is to wait until cooldev find a solution to this

As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?

kidmanis said:
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
Click to expand...
Click to collapse
Hmm, interesting. I will try this out as well. Might probably be a week though, I am leaving for holidays tonight and cant risk making my phone unusable. Maybe somebody else is willing to give it a try?

kidmanis said:
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
Click to expand...
Click to collapse
Thanks now i know where to search the problem.

Hi,
here is a logcat of a bluetooth connection during a call on stock rom/stock kernel.
What I did:
-start logcat
-start bluetooth
-chose a contact
-call contact-
-talk for a minute
-hang up
-stop logcat
I then wanted to flash the mosh kernel and do the same again but the last time I checked there wasnt this huge plethora of different kernels to choose from. Very impressive work!
Could you tell me which one you would like me to flash and I would then redo everything?

Hi,
I tried installing mosh kernel 1.8 and 1.85 (for stock, init.d enabled) on sazy rom but it didnt boot. It stayed at the very first screen you get when you turn the phone on. I then installed your cm11 build8, connected via bluetooth to my car and had someone call me.
Attached is the logcat.
Do I need the samsung stock rom for mosh kernel? I thought sazy rom was a stock rom?

Connection Problems After Update

Since the update, my SW2 seems to be incapable of playing nicely with any other Bluetooth-enabled devices. If I am in an area where it is just my phone (LG G2 running KK) and the watch, everything works just fine. But if my phone connects to something else via BT, for example my car stereo or BT headphones), the watch will immediately disconnect and the only way to reestablish a connection is to power cycle the watch.
I'm trying to determine if this is a problem with the firmware update or simply a matter of a problem between phone's BT firmware and the watch. Anyone else have the same issue?

I don't face this problem. I've used 2 BT headphones models without any issue.
Sent from my SM-N9005 using Tapatalk

Before the update I had zero connection problems. After the update my SW2 constantly disconnects and sometimes reconnects, other times I have reconnect by going through smart connect and un-pairing/re-pairing to power cycle the watch. I have tried disabling apps and even removing all apps and resetting all to no avail. This is extremely frustrating because my fancy new expensive piece of tech is 99% useless . Also I have ZERO bluetooth devices on in the area besides the SW2.
Any help would be greatly appreciated. Is there a way to flash and/or format the SW2? I tried SUS(sony update service) which USED to have the SW2 in it with a repair option but they have since removed the SW2 in the latest version 2.14.6.2014170858.

help
Pirate_Freder said:
Before the update I had zero connection problems. After the update my SW2 constantly disconnects and sometimes reconnects, other times I have reconnect by going through smart connect and un-pairing/re-pairing to power cycle the watch. I have tried disabling apps and even removing all apps and resetting all to no avail. This is extremely frustrating because my fancy new expensive piece of tech is 99% useless . Also I have ZERO bluetooth devices on in the area besides the SW2.
Any help would be greatly appreciated. Is there a way to flash and/or format the SW2? I tried SUS(sony update service) which USED to have the SW2 in it with a repair option but they have since removed the SW2 in the latest version 2.14.6.2014170858.
Click to expand...
Click to collapse
helo
I have the same problem with my new sw2 firm: 1.0.B.4.154 and my sgs4 standard ROM .If You find some solutions for this problem please wright how make this.

Question: does any of you guys use the 'watchwidgets' app?
I had disconnection problems too only while using the clock widgets from this app.
As soon as I removed it all went back to normal.
I'd strongly suggest a connectivity test without the use of any 3rd party screen candy, at least for a day, maybe it'll help you find the culprit.
Sent from my Xperia V using Tapatalk

vrl13 said:
Question: does any of you guys use the 'watchwidgets' app?
I had disconnection problems too only while using the clock widgets from this app.
As soon as I removed it all went back to normal.
I'd strongly suggest a connectivity test without the use of any 3rd party screen candy, at least for a day, maybe it'll help you find the culprit.
Sent from my Xperia V using Tapatalk
Click to expand...
Click to collapse
I think the problem is on te watch because i try for four different phone with only 1 aplication for smw2 is smart watch connection
i think about loading Rom for watch but i don't now how.

It sounds like a watch problem indeed... can't you go to Sony with it? If you're still under warranty maybe they'll change it...
As for a watch ROM...there isn't any, as far as I am aware.
Sent from my Xperia V using Tapatalk

Same issues here. Mix of roms. With some roms all seams fine for a while. It always ends up with disconnects. I'm trying to find a reason. Mix of software and hardware. Coudl you post the HW version of your SW?

I have the same problem after update ... GT I8530
I have the same problem after update ... GT I8530

[Oreo] Bluetooth Audio settings in Developer options don't stick.

So I've recently updated to the current oreo Beta on my MHA-L29 and I'm facing issues with the Bluetooth audio codec selection. Regardless of what device I connect, Android always switches to the lowest possible settings aka 44. 1kHz streaming and 16bit sample after stopping/starting audio (its enough for a song to end and a new one to start to reset those) now visually the settings don't actually change at all as long as a Bluetooth device is connected, so even if I change to 96kHz the option displays 44.1kHz, however the change in sound quality is definitely noticeable since 44.1kHz has atrocious artifacts on any higher note.
Now my question would be if this is beta related, a general oreo bug or If anyone actually has an idea on how to fix this issue.
Build number: 8.0.0.361(C432)

Bumping this since I still haven't found a fix and maybe someone else has the same issue.

Having the same issue on a Mate 10 Pro, seems to be an Android 8 related problem.

Same issue here.. but bluetooth does work well

Having the same issue, do you think they will fix it?

Updated to .363 today and unfortunately the issue still persists, i am actually starting to get worried now that it will take quite a while for this to be fixxed, if it is adressed at all.

I'm having this issue as well and this is absolutely atrocious.
Ever since I upgraded to android 8 my bluetooth audio sounds like crap. There is very noticable overall hissing and lots of cracking (most noticeably on drums in music).
I also tried digging in the developer options but nothing will stick, this is the first and last time I ever bought a Huawei product.

Arthurvben said:
I'm having this issue as well and this is absolutely atrocious.
Ever since I upgraded to android 8 my bluetooth audio sounds like crap. There is very noticable overall hissing and lots of cracking (most noticeably on drums in music).
I also tried digging in the developer options but nothing will stick, this is the first and last time I ever bought a Huawei product.
Click to expand...
Click to collapse
Im pretty sure Huawei is not to blame for this, since i've seen reports from other phones aswell having the same problem, i believe its an Oreo problem in general that adds ontop of the other bluetooth connectivity issues.

Ran into the same issue myself. Unacceptable audio quality reduction since Oreo update a few days ago. Rolling back to Nougat for now. Based on what I could find, seems to be just as much Google's fault. I really don't like what they did with the notifications either. The app running in the back round is just plain annoying since you can't turn it off.

Syndirail said:
So I've recently updated to the current oreo Beta on my MHA-L29 and I'm facing issues with the Bluetooth audio codec selection. Regardless of what device I connect, Android always switches to the lowest possible settings aka 44. 1kHz streaming and 16bit sample after stopping/starting audio (its enough for a song to end and a new one to start to reset those) now visually the settings don't actually change at all as long as a Bluetooth device is connected, so even if I change to 96kHz the option displays 44.1kHz, however the change in sound quality is definitely noticeable since 44.1kHz has atrocious artifacts on any higher note.
Now my question would be if this is beta related, a general oreo bug or If anyone actually has an idea on how to fix this issue.
Build number: 8.0.0.361(C432)
Click to expand...
Click to collapse
Is your Bluetooth turned off while you changing the setting. I think bluetooth need to be turned off if you want setting to stick. I tried my phone and it is keeping the setting

zhouqishi110ok said:
Is your Bluetooth turned off while you changing the setting. I think bluetooth need to be turned off if you want setting to stick. I tried my phone and it is keeping the setting
Click to expand...
Click to collapse
Yeah it does...until you turn bluetooth on again.. Ive tried absolutely everything unfortunately.

Syndirail said:
Im pretty sure Huawei is not to blame for this, since i've seen reports from other phones aswell having the same problem, i believe its an Oreo problem in general that adds ontop of the other bluetooth connectivity issues.
Click to expand...
Click to collapse
I couldnt care less about who's to blame, its unacceptable Huawei pushed this update through with such a major bug in it. If they couldnt fix developer settings not sticking, the least they could've done is make people aware of this issue when they offered the update. I use my phone for music A LOT and if I had known this in advance I would have never updated in the first place. Now im stuck with this crappy audio quality on a phone I paid 655 euros for.
Welp, that's what you get for not waiting around for bug reports I guess....
Does anyone here know if there is a safe way to downgrade back to Nougat without voiding your warranty? I know how to root etc. but I dont feel like totally breaking open my phone again, I got out of that world a while back because I wanted to avoid this crucial stuff not working the way it should stuff. If there is no other way Ill void my warranty but I'm seeing lots of different guides on here and none of them seem that professionally made so I'm kinda on the fence

Arthurvben said:
I couldnt care less about who's to blame, its unacceptable Huawei pushed this update through with such a major bug in it. If they couldnt fix developer settings not sticking, the least they could've done is make people aware of this issue when they offered the update. I use my phone for music A LOT and if I had known this in advance I would have never updated in the first place. Now im stuck with this crappy audio quality on a phone I paid 655 euros for.
Welp, that's what you get for not waiting around for bug reports I guess....
Does anyone here know if there is a safe way to downgrade back to Nougat without voiding your warranty? I know how to root etc. but I dont feel like totally breaking open my phone again, I got out of that world a while back because I wanted to avoid this crucial stuff not working the way it should stuff. If there is no other way Ill void my warranty but I'm seeing lots of different guides on here and none of them seem that professionally made so I'm kinda on the fence
Click to expand...
Click to collapse
Fair enough point. You can downgrade safely via the Huawei pc application, just choose update and it should give you the option to downgrade. It will however most likely factory reset your phone so I'd advise you create a backup first.

Syndirail said:
Fair enough point. You can downgrade safely via the Huawei pc application, just choose update and it should give you the option to downgrade. It will however most likely factory reset your phone so I'd advise you create a backup first.
Click to expand...
Click to collapse
I downloaded the HiSuite app and there is no downgrade option anywhere.
Edit: Windows 10 antivirus says the downloaded .exe from the official Huawei website is a virus, anyone else have this?

Hello. I've been playing around with the Bluetooth settings and I've found out that while playing Spotify through BT, if I change the kHz to 48 or higher the sound is actually getting better! Although the setting isn't sticking or showing, I'm getting way better sound choosing 48 kHz or better after I press play. Maybe just my phone, but try it out if you're experiencing bad quality BT sound!

Thanks. Will try the 48k sound mode out

I was having this problem with my P20 Pro and Sony WH1000XM2s. Turns out you can get the aptx HD codec and 24bits setting to stick if you select 'Priority on Sound Quality' within Sony's Headphones app. Sample rate is still stuck on 44.1khz however.
Edit: Just turned off bluetooth and set sample rate to 96khz, turned bt back on and it's sticking!

Bluetooth loses devices after sleep

Any help with this issue would be very appreciated! I've had this from the very beginning where after the device goes to sleep, then wakes again the bluetooth devices disappear from the paired list, plus it won't find anything when you search. After you hard reboot it works perfectly again until you next put it to sleep. This means the OBDII won't connect in Torque, phone won't connect etc until you reboot every time you get in the car which is major pain.
- I've tried replacing the bluetooth module with a USB and physically removing the onboard one.
- Replacing MTCManager with a version that doesn't kill any services/apps during sleep
- Using the whitelist from Graser Dasaita's tool
- Tried multiple ROM's
Unfortunately I'm at the end of my Android knowledge so not sure what to try next. Seems like its some kind of service that gets killed? Weirdly it will sometimes for no apparent reason randomly reconnect when I'm driving along.
Please help!
Running PX5, Maylask Android 6.0.1 (ROM version 7.2)

I've since discovered the system service "bluetoothservice" gets killed which is probably causing my issue. How do you automatically start a service on wake? Any suggestions?

I had white listed "bluetooth com.microntek.bluetooth" but I also needed to white list bluetoothservice android.microntek.mtcservice still doesn't work though.

Removed

bjt2 said:
Removed
Click to expand...
Click to collapse
Hi !
What do you mean by removed?
I have a similar issue.