Hello!
Is there any possibility to set up the priority for a bluetooth A2DP connection?
I have connected my desire to a Parrot MK6100 - making phone calls and syncing the phonebook makes no problems, but listening to musik leads into unpredictable "gaps" (like gaps within musik streaming with slow connection) - the musik stops and goes on 1-2 seconds later -- that is horrible when listening to musik!
My current ROM is "ICS 4.0.4 BCM RC3.1U0" - what can I do? I had the same problems with other ROMs also! (so it is NOT a special Problem with ICS!). I think the only ROM I didn't had these Problems was the original Stock-Rom!
What can I do?
The most strange thing is: With a new ROM, the first (and most times also the second) connect to the Parrot is perfekt! Listening to musik without gaps - like it shoud be! And then - all following connects do have these problems...
Switching off WLAN doesn't help... (all independant of the player!)
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Similar problems
Hi,
have you find any solution. I've similar problems with Galaxy SII (ICS 4.0.3) and MK6100. I'm not using it to play music, just podcasts using BeyondPod, but issue is probably same.
Martin
Hi Martin,
I am not really sure whether I have found the solution or not... But the last two days it worked without any gaps!
I tried to not move the dalvik cache to the sd-card - so I kept it within the phone memory... Probably this was the trick?!
But this might be only a solution for a couple of days, like all my previous solutions... When I clean dalvik and format all partitions (except fat32) - and so have a new, clean installation, everything works most times for at least two days...
I will update this "solution" in a couple of days - maybe you want to try it nevertheless?!
Mario
Hi Mario,
my only new observation is that if the connection is initiated from the phone, it seems stable. Eg. when I disable BT on the phone, re-enable it and then click to connect to the HF.
Martin
Hi Martin,
I haven't tested that yet - I have switched off Bluetooth and activated it again on the phone, but then the "automatic connection" to the Parrot was faster than me. But then, normally, it wasn't better than before.
To be honest: I really hope that keeping the dalvik cache on the phone-memory did the trick for me...
No Solution
Hi, keeping dalvik cache on the phone-memory seems not to be the solution!
Today - after about 5 connects without problems - I got gaps again! More or less every Minute there is a gap which makes listening to mp3 really horrible.
After that, I rebooted my phone and connected again: Still gaps within the first 5 Minutes (about 6 breaks) and after that no gap for about 6 Minutes (until I switched of the car)
Can anyone tell me: What changes after ~50hours usage?
Update
The last two days... I haven't changed anything within the configurations...
There are still gaps - at least two within 15 minutes listening. (Used it three times for 15 minutes each time)
Are there any possibilities to give higher priority to the bluetooth connection? (I am only able to increase it for Poweramp - maybe that could help?
I tried to listen over bluetooth again. I have gabs every few seconds. Two gabs in 15 minutes would be fine for me
I'll probable give up, sice I have 3.5mm jack too, so I'll start to use cable
Martin
Related
I'm having the same problem for a week now...
I was on the street with my BA making calls and all went ok. I use it for my work, so I do lots of calls a day. Suddenly, I realized, when I call, that the other can not hear me, nor can I hear them! The counter is running, the screen says "Connected". I haven't done anything to change the configuration, nor it have dropped it from my pocket.
I'¡m getting crazy. I don't know what I've done wrong.
Things tried unsuccessfully:
-Lots of device resets..... Between tryes and Updates.
- Reinstalled WM5 using a different ROM. Now I have TM 1.3. [http://forum.xda-developers.com/viewtopic.php?t=42632]
- Upgraded Radio to 1.15 (previously, I had 1.13)
- Used a Bluetooth headset. It worked, I could hear the sound from the phone, at least. Only thru the bluetooth headphone. Still, I could not hear any phone-sound from the loudspeaker when I turned off the headphone and the bluetooth headset were disabled, even with the Bluetooth signal ON, as suggested on other post. Each try with a new call.
- "Installed" the Unidirectional patch (copied the AudioGW.dll file over the old one successfully, reset, etc..)
- Turned off the device and leave it off for a while. Take off the SIM card, touch it (cosmic vibrations ) Sometimes, before, the SIM card went a little nuts if I resetted the device too much -maybe :?- or if I got the battery off...
Sorry if this has been posted before, but, at this point, when I've been tried almost (I think) everything, i couldn't find anything relevant using search.
Please, any help will be greatly appreciated!!! Maybe I can use at least a link to another thread..
Thanks
come on, people, a little bit of help here Still making calls with my old Nokia
Out of interest... do you have any wisbar apps installed?
No wisbar apps installed. Thanks
I'm having the same problem. Most of the time this occurs the first time I use it in the morning. The other side can hear me, but I can't hear them. I softreset and it works again.
Yes, I've checked and there's lots of posts about this problem. It differs from mine in the sense that the other CAN hear you. In my case, nor I or the other part can hear us....
As you can read, I've done lots of soft-resets, now I have also 3 hard-resets with everything "at 0" (clear Registry Hive and format Storage). But the problem remains. The only thing I see I can do now is downgrade to wm2003 and see.......
Thanks for your answer.
mutho said:
I'm having the same problem. Most of the time this occurs the first time I use it in the morning. The other side can hear me, but I can't hear them. I softreset and it works again.
Click to expand...
Click to collapse
I've moved to the "BA upgrade, etc" forum. Please, help me from there!! Still looking for an answer
http://forum.xda-developers.com/viewtopic.php?t=44440
there is an issue with BT and this behaviour. Either you need to always have BT activated or once you have deactivated BT you need to reboot your device. I have the same problem myself.
Regards,
Fredrik
I have a problem that more people seem to have, according to the search. I couldn’t find the “audio” tab in my Bluetooth-settings, so that didn’t help me.
The problem is as follows. After 1 day the sound on my compact III mutes, including vibration. Sometimes it's after 12 hours, sometimes after 2 days, there's no distinct pattern to be recognized. Also, it doesn't seem to matter if you use the phone or not, since it sometimes is alright at night and the sound is muted the next morning. This is for all sound-events (warnings, incoming call notifications, messages, mp3 etc), however, you can make a call without any problems and hear what the other person is saying. Once you’ve hard-reset the device everything is back to normal.
It does get annoying however, since I regularly miss calls due to this bug.
I had the same problem on my Vario in the past. So I’m guessing it’s somewhere in the software I use, but apart from Total Commander and TomTom6 I haven’t installed any third-party apps.
Yup i've been having a slight problem with the sound. I thought it was like the endless knackered M500's that orange used to send me which had speaker failure after about 10minuites! (Swear they kept sending me the same 2 faulty phones - I had 5 in 5 days once!) But a play in the bluetooth seems to get it working again.
The other annoying thing is that if you leave the power management at the default settings then occasionally the screen blanks without being able to get the backlight on again - so now I have to manually turn of the screen. Stil aint much of a problem - ive had a normal days use, 2 hours of radio play, bluetooth and wi-fi on all day and still have 35% battery - wehay!
Hopefully there'll be a patch soon to sort out he glitches.
I forgot to mention I had the exact same problem on my mda Vario also. I always thought it was a problem with that specific piece, but apparantly not.
Could it be the vibrate.cab that I'm using to produce vibrations when you use the phonepad? Or should I really do some further research in the bluetooth-department?
Same problem here.
Phone becomes completely silent after 9 hours in standby mode.
I need to reset it to get back sound
Does someone know what is going on here ?
Please advise. Thank you.
I seem to experience no problems the past couple of days (fingers crossed). I used the 'speed up your WM5' tweak where you set the Glyphcache to 32768. After I reduced it to 16something the problems seem to have disappeared.
I noticed that this problem happens when for example email is automatically checked during night. If email comes in (and is not read immediately) the phone will start notifying in background.
Notifications are kept and only a program like "check notifications" will delete them manually. But still if you delete them, the phone then needs a reset
to work properly again.
This is not a memory issue, it has to do with the notifications.
I do not know how to solve it.
Hey all,
So I'm posting this thread regarding a couple pretty weird glitches and bugs occurring on my G3, 3 specific ones.
The first: (Probably the least serious but still REALLY annoying) At EXACTLY 12:00AM every night no matter what timezone I set the phone to (I'm in AU on the AEST GMT+10 timezone but it does this at the same time on any timezone) the phone will switch it's WiFi off automatically without warning, reason or explanation. It just goes off and then I have to manually turn it back on. Sure I could use an app such as Tasker or AutomateIt to turn it back on but I don't see why this is occurring in the first place?
The second issue (Most recent): Lately after updating to the V20E firmware for my D855 I've noticed that a graphical glitch (Specifically related to the colour Blue) occurs when there are fast moving elements on my phone's screen (Such as when I move a chat head around on my phone from Messenger, or when I'm scrolling Facebook or my App Drawer fast, there's just a blue box around whatever object/s appear to be moving on my phone's screen. I've not dropped the phone at all, and it has only been present since updating from the V20D ROM. Not sure what could be causing it.
The third and by far the MOST ANNOYING of the issues I'm having, is that for no apparent reason, whenever I am listening to Music with the stock Music player, and I lock the screen (The screen goes off) about 5 seconds later weird stuff starts to happen..
The song will pause, play or even stop completely, seemingly on its own. The "phone" will change songs, artists and sometimes complete albums and playlists completely by itself, with me doing nothing but staring at the lock screen (It keeps doing it until I re-enter the Music app, then when I lock the phone the whole cycle just repeats itself.)
I've done some looking around and careful observations on the phone itself, and it seems that before the weird stuff starts happening to my music, the phone opens Voice Mate by itself, and then if I'm not present, it apparently closes it and then that's when the stuff happens. I've tried everything I can on a non-rooted phone to stop this. I've tried re-installing the Music app, Uninstalling all updates to the Voice Mate and it's packages to the factory version, force-stopping Voice Mate, everything and no matter what I do the phone still opens Voice Mate and the weird stuff starts happening (It's like it's taking commands from Voice Mate to do something but I'm not even doing anything ) It's been doing this since I got my phone when it came with Android KitKat 4.4 (I was on the D10M ROM until I moved to the D20D Android L ROM) and I moved ROMs doing a completely fresh start ( I factory wiped the phone and then upgraded via a CSE flash and put all my stuff back on it manually) and I would've thought a completely fresh start would have fixed it but apparently not... Either it's a bug that's been present for a while, or it's something deeper than the ROM.
So yeah some pretty weird issues, if someone knows what could be causing them, please let me know, especially if you know a way to solve them.
Cheers guys.
I'm having a very similar problem with regards to #1 but it's doing it with Bluetooth for me!
At midnight on the dot, it will disconnect my connected Bluetooth devices. It doesn't shut Bluetooth off, it just drops the connection. I posted about it here: http://forum.xda-developers.com/verizon-lg-g3/help/bluetooth-disconnects-midnight-t2973187
Your phone sound possessed! Call 1-800-Exorcism now.
You right, weird/unusual.
after a loooot of search on the internet and after reading all the older posts here i am desperate and i am opening here a thread. Thats my last hope that someone found a solution to this issue.
So 6 months ago i bought a nexus 7 2013 wifi for a car project. i wanted to use it as multimedia and navigation system. After i modified my car (see pic. / contact me in case of interesst or advices)
https://postimg.org/image/exyp7da37/
everything was nice i was happy with the result. The problem starts when i wanted to use the navigation...
The device cant find a satelite, searching for gps signal is the only message i see. 9/10 the gps cant find satelite. One or two times it found the signal after one hour or more..
My thoughts:
1. The case is causing this issues... the tablet charges wireless and is kept in place with magnets so i can remove it in a second.
I am trying with the "naked" tablet outside with directly sky view... no change.
2. The backcover is modified with 2 small metal plates in order to get magnetizied with the magnets installed in the car dush.
i tried an other backcover.. no change.
3. I tought it is a software issue.... i was using Cyanogenmod 13 with elemental X... installed the original software / Android 6. Without any other installations only GPS Status... still no signal.. I installed android 5.0.1 ... still no signal.
4. i used various of settings changes and apps ( GPS FIX, GPS Doctor, GPS Status) ... the gps android settings are the the most accurate level. Still no change..
created the data/gps/ folder with the permissions rwxrwxr-x. Still no change.
After all that and after reading that there are many people out there with the same problem i thought thats a hardware issue.
5. Thats why i bought an other one (used)... before buying it i made sure that the tablet will find a satelite in GPS Status... i went to the sellers house.. and it did (with wifi off). I went back home i tried again and it did... i was so happy.. i wiped my storage flashed CM13 with ElementalX again ... i opened the Nav App (Sygic)... Everything worked like a charm... i was so happy i finally have gps in my car. I visited a friend stayed there 5 hours went back home... Navi still works.
I took the tablet in my home and wanted to make a restart for some reason... After restarting , tablets gps was dead again... and still looking for a solution..
i am 100% it is a software issue. in case there is someone out there with a solution i would really appreciate it.
I'm kinda on the same boat.
My trusty Nexus 7 2013, that has been through a lot of display changes due to my clumsiness. Few days ago it decided to kick the GPS boat for reasons.
It used to work just fine, without any software tricks or anything. Used to work beautifully without wi-fi (even though I tethered from my phone, many times I travelled to places without connection) with a 8-10m precision.
Now it's spotty, taking from 2 to 280 seconds for the first fix, and precision floats between 10 and 150m (which is unbearable).
Using GPS Status & Toolbox, I can see the A-GPS does it part guiding the tablet on where are the sattelites at (I see around 22 sattelites), however the tablet has a real hard time connecting to them, most of the time staying at a solid 0 connections. My phone (Moto G5 Plus) connects within' seconds to the sattelites with pinpoint precision.
When the tablets manages to fix, it only connects to a couple (5 or 8 out of 22) sattelites, thus not so precise.
I am guessing the heat might have damaged something, but I'm not also 100% sure it ain't a software issue. I flashed the sole GPS fix, but it didn't help at all. I tried every software trick on the book, but nothing. I flashed several ROMs but it didn't make even a dent.
It seemingly gets better if I keep it connected for a good while. I tried letting it overnight with the GPS connected, and it worked fine the day after at any time (between 5 and 20m precision). However it was dead again the next day.
I couldn't find anything regarding a GPS antenna for this device, it's almost like it doesn't have one... I fiddled with the Wi-Fi antenna, which has 3 pins (one I guess is for bluetooth?), but it didn't help with GPS. Bluetooth (I use an OBD2 scanner that sends too many data per second, and I still can play music through bluetooth just fine) and Wi-Fi (Speeds and latency are optimal) are great.
I can't help but think this device doesn't have a GPS antenna, and whatever it uses for an antenna has failed or is now faulty.
Have you ever managed fixing yours?
Hi guys,
I'm having a weird problem that I am unable to resolve. It drives me crazy since I have a very long drive daily and rely on bluetooth audio.
When playing music over bluetooth, there will be stuttering after 20-30mins of playback. The stutter will occur sporadically every x seconds. Sometimes it goes away sometimes it doesn't.
A quick fix I found is disabling/enabling bluetooth, which resets everything and gives another ~20-30 mins without stuttering.
Since I use the phone as a work device, I bought another one so that I could run some tests. Both phones are unlocked.
I tried Pi Experience (Pi) and Lineage 15.1 (Oreo). Both were ran without any apps other than the built-in ones and Play Music.
A few troubleshooting steps I did:
- Since this is occurring on 2+ devices, I strongly doubt it's a hardware issue
- My previous LG V20 (Android 6-7) and friends Iphone have zero issues (so the car isn't the problem)
- This stutter occurs on any BT device the phone connects to
- Disabling/enabling bluetooth resets the issue
- Pi and oreo are affected
- Disabling BT/Wifi scanning in location does not resolve the issue.
- Stopping every service related to BT besides a2dp while the problem occurs does not resolve the issue.
- Restarting Play Music or stopping Play store does not resolve the issue.
- Disabling battery Manager on Pi does not resolve the problem
What I think the problem could be:
- Memory leak in the A2dp service? (I have no idea how to check for that)
- Power saving features that are applied to the BT service after being active for so long (since resetting the service works)?
I'm running out of ideas. Does anyone have any suggestions/tips/story on what the culprit could be and how to fix it?
I can provide a logcat of when the problem occurs if that can be of help
Thanks
Phil
Bumping this up in case someone can chime in!
I have tried all the firmwares as they become available and still face this issue! I know for a fact I am not alone with this problem since I have 2 Redmi Note 5 pros with this problem, and had the exact same issue with a Samsung Galaxy S9+ (snapdragon) that was returned!
If someone can answer these questions, that would be greatly appreciated:
- Do the Firmwares available contain the actual android drivers for bluetooth? Or it's the literal firmware for the SOC (the driver would then be a different file inside the /system partition)?
- When you disable/enable bluetooth, what happens in android? Is the driver unloaded/loaded? or maybe disabled/enabled? Since this step resets the the problem, i'd be interested to know!
Thanks
Maybe Doze-related, but I use audio over Bluetooth for like 2hs almost every single day in my main device (Is not whyred) without problems, so I'm not sure about that.
1- No, the Bluetooth blobs are located in /vendor partition.
1- The operation of bluetooth is complex, many things happen when it's switched on/off, but simplifying: some processes and services are started/stopped.
Anyways, the best way to find the problem is taking logs and send it to the rom developer.
onliner said:
Maybe Doze-related, but I use audio over Bluetooth for like 2hs almost every single day in my main device (Is not whyred) without problems, so I'm not sure about that.
1- No, the Bluetooth blobs are located in /vendor partition.
1- The operation of bluetooth is complex, many things happen when it's switched on/off, but simplifying: some processes and services are started/stopped.
Anyways, the best way to find the problem is taking logs and send it to the rom developer.
Click to expand...
Click to collapse
Thanks for the reply.
This occurs on every rom that is loaded on the devices. I have a strong feeling it's related to the drivers.
I tried looking at the logcat while it glitches, and no errors seem to be shown. I will attach one within the next few days.