This annoying problem popped out of nowhere I can think of.
Originally running AOKP #37. Since then I've tried all version of AOKP back to M5, wiping, formatting /system, CM9, faux123 16m, 17m, 18 b3. Each ROM the same problem.
I can connect to a media device once, either the car of speakers then a reboot is needed to [play] media again. The phone does show it being connected to the car but it's phone only.
If music is playing, through the phones speaker, and a call is placed the music plays [with] the call.
I've restored to AOKP b34 which seems to work, and totally wiped the phone to factory 4.02 which also seemed to work. Wiped flashed b37 back and was fine for a day.
I'm lost. It's annoying having to reboot at every 7-Eleven, gas station or Starbucks.
rinse and repeat? try a different rom? different kernel?
I rinsed and repeated constantly over the last week.
It's with all the ROMS I tried except for returning to stock, I think, I didn't keep it more than half a day and with AOKP b34 restored.
Oh, I had the "hybrid" radios, I've since installed 4.0.2 radios, 4.0.4 radios and am back to 4.02 thanks to returning to factory.
This is a VZ Galaxy Nexus.
I think I found my issue finally. I think a few more tests will confirm it's the MIUI permissions mod.
I've found the Bluetooth on the GN a bit buggy too. Though i manage to live with it.
When connecting to bluetooth devices i usually get the device to do the connection. If that doesnt work i just toggle Airplane mode on and off, and then it's working again.
If I manually turn off bluetooth it will end up hanging when turning on again.
After i switched to CM9 I think bluetooth overall is working a little better (might be placebo effect though).
The problem is definitely the MIUI permission mod.
Reinstalled it today and the issue returned immediately.
The stock Bluetooth system actually worked pretty good. from Nexus WAS controllable from the car stereo to an extent.
Related
Hi, I was wondering if anybody has come up with a fix for AOSP roms for Bluetooth yet. Sense roms connect to my bluetooth stereo perfectly, but none of the AOSP roms (Cyanogen, ect.) can connect consistently.
The very odd issue is that yesterday I thought I came up with a solution, so I flashed CM7 on and tested. It worked. However I couldn't connect to the market because I forgot to install the gapps addon, so I did, and didn't think twice until last night when going to work, and bluetooth wouldn't work again. It seemed like the gapps addon broke bluetooth, but it could have been some unknown external factor. I can test this later today to see if the gapps addon does in fact kill it somehow.
Can anybody shine light on the bluetooth issues and maybe enlighten me as to a fix if there is one?
Not one response? That's disappointing. I was doing some testing with CM7 today and I could not reproduce the bluetooth breakage that I have experienced every other time. I was trying to isolate what was causing the issue by lashing the rom, then booting, testing, then flashing the RIL, booting, testing, then flashing the gapps package, booting, testing, then re-installing all apps one at a time from titanium backup (the same as I did before) and nothing broke it. Over a full day now and bluetooth is rock solid.
This poses a problem because I don't know WHY it is working. The only variable I actually changed is booting after each thing I flashed. This still will not change issues with any other AOSP roms even if the solution is to flash each separately, because the rest come with gapps installed, and they are broken both before and after a RIL flash.
Also to further convolute things, I started the day testing LeeDroid. Bluetooth would not connect. This is a rom that should have connected just fine.
Hi mrcandyman,
I too have noticed that a lot of AOSP roms have (imho) severe BT problems, mainly with connection to earpieces in my case (voice dialling). I have tried AOSP roms on both my desire and sgs2 and had the same problems on both. Flashing back to rooted stock roms has always cured my problems with BT. I am not a dev or programmer so have no idea what or where the problem lies only that stock roms I've tried don't have BT problems and AOSP do.
feeling your pain,
Night....
I have the Verizon Galaxy Nexus, running the 6/12/12 nightly for CM9, and everything was running great until this afternoon. I haven't dropped my phone, gotten it wet or anything like that.
Now whenever I receive a call or make one, I can't hear the other person and they can't hear me. It was working at around 11 this morning when I got a call, but not after around 5, and I hadn't done anything with it.
I tried flashing to a different ROM to see if that would fix it, so I flashed to the latest MIUI, wiped data/cache, and when I rebooted it, I noticed a headset icon in the notification bar. Curious, I plugged in my headphones, and I could hear youtube (which I also tested earlier and I couldn't hear). When I unplugged them, the headset icon remained, and I remained unable to hear anything.
I don't know why, but I restored my backup of CM9, tried everything again, and it didn't work. So I tried plugging in my headset again, and the music app that I use recognized that I plugged them in and started playing music, it stopped when I unplugged them, but I still couldn't hear anything through my normal speaker.
I looked around the forum and found temporary solutions that involve installing an app that forces the phone to use the speaker, however I am hoping to find a more permanent solution.
I'm about to reflash back to stock 4.0.2 and see if that helps, I'll post back if it does.
EDIT: Nope, didn't work. Please help.
EDIT2: Just relocked my bootloader to send it in ...and it started to work .-.
I'm going to reflash CM9 and hope that everything works out.
Do you guys think I should still have it replaced?
Had a similar experience
Headset being detected even when not connected seems to be a common bug on Gnex, have seen several posts and I myself had to go through this. It usually gets fixed by itself in a day or two.. but till then use the "toggleheadset2" from the play store, which would allow you to manually say when the headphone is connected or not.
--Vj
PhreeqQitsikk said:
I have the Verizon Galaxy Nexus, running the 6/12/12 nightly for CM9, and everything was running great until this afternoon. I haven't dropped my phone, gotten it wet or anything like that.
Now whenever I receive a call or make one, I can't hear the other person and they can't hear me. It was working at around 11 this morning when I got a call, but not after around 5, and I hadn't done anything with it.
I tried flashing to a different ROM to see if that would fix it, so I flashed to the latest MIUI, wiped data/cache, and when I rebooted it, I noticed a headset icon in the notification bar. Curious, I plugged in my headphones, and I could hear youtube (which I also tested earlier and I couldn't hear). When I unplugged them, the headset icon remained, and I remained unable to hear anything.
I don't know why, but I restored my backup of CM9, tried everything again, and it didn't work. So I tried plugging in my headset again, and the music app that I use recognized that I plugged them in and started playing music, it stopped when I unplugged them, but I still couldn't hear anything through my normal speaker.
I looked around the forum and found temporary solutions that involve installing an app that forces the phone to use the speaker, however I am hoping to find a more permanent solution.
I'm about to reflash back to stock 4.0.2 and see if that helps, I'll post back if it does.
EDIT: Nope, didn't work. Please help.
EDIT2: Just relocked my bootloader to send it in ...and it started to work .-.
I'm going to reflash CM9 and hope that everything works out.
Do you guys think I should still have it replaced?
Click to expand...
Click to collapse
---------- Post added at 10:27 AM ---------- Previous post was at 10:17 AM ----------
Only permanent solution is to change the socket. Its the switch inside which usually gets jammed.
Same exact problem
I am having this same exact problem. Its fine on stock, once I flash CM10 calls say connected and the time starts ticking but I can't hear a thing and no one on the other end can hear me.
Sometimes when I do connect, the person will hear me for a couple seconds and then it'll drop then connect again then drop...over and over again.
Google now doesn't pick up any voice searches either.
HELP, this is a relatively new issue. (2-3 months old) I've had the nexus since January and had it rooted and rom'd shortly after. Only recently has this issue cropped up.
toggleheadset2 seems to work but it sucks that I even have to use it. Any devs out there have suggestions/input? I've looked all over for a resolution.
Please don't make me go back to stock....Please!
Just bought a nexus from Verizon, on my second device now. First device was exchanged after 1 day, battery ran out in 6 hours, never held signal for more than 2 min. Second device is a refurb, phone worked great and had ZERO issues until updating to 4.0.4. Came with 4.0.2 on it, put off the update for several days to see if it worked ok. Everything ran smooth and fast, great battery life and signal. Immediately after the update, phone now hangs and freeze when unlocking, switching home screens, open app menu etc. Phone also seems to randomly think a headset is plugged in and will not make any sounds except ring, and in a call, neither ear speaker or mic work. Speakerphone works, and if a headset is plugged in, sounds works normally through headset. Found this app:Wired Headset Routing Fix which sometimes fixes mic issue. Sounds and mic work normally after a reboot, but will then randomly stop. Found several pages of threads all over about the mic issue, but with no fixes.
Tried flashing Bugless Beast rom to adress some of these issues, all problems remain. Mic/sound issue seems tom be related to something with the software that controls the headphone jack. Should I continue trying different roms? Try a different kernel? Possible to complete reset phone back to stock 4.0.2? It worked FANTASTICALLY before the update, how could I get it back to the way it was when I unboxed it? My 14 day warranty runs out on the 22nd, so I could exchange the phone again, but my Verizon store has been hounding me to switch to another device.
Any help would be greatly appreciated!
After your first device they gave you a refurb? Only After a day? That's strange.
Sent from my Galaxy Nexus using xda app-developers app
They initially gave me a brand new one, case was cracked completely through when they opened the box to activate it. The only other phone they had on hand was a refurb.
Hey folks,
I'm completely stumped. Here's my problem:
For several months now, my Note 2 (N7100) has been making random low beep sounds while I'm listening to music. Very seldom, not reproducable, but always recurring. It only happens when my headphone jack is connected (headphone, line out audio in my car, etc.), and it sounds pretty much like an old MS-DOS PC speaker beep, only very low. The beep is only audible in the right speaker/earpiece.
My current setup:
Android 4.4.2 XAFND3 stock firmware
MJ5 bootloader
AGNi pureStock kernel 4.3.1
Neutron Music Player
Things I tried so far:
Tried different sound drivers (Boeffla and Wolfson sound)
Tried different ROMs (Android Revolution HD, Dr Ketan Custom ROM, Deodexed Stock ROM)
Tried different kernel (Nadja kernel)
Tried different players (stock and Poweramp), but to no avail. In Poweramp, instead of a single low, extremely loud beep, I get a constant, earpiercing, insanely loud screeching noise that almost made me fall from my bike the first time it happened.
Replaced the headphone jack (was having issues anyway and needed to be replaced) with a new one.
Factory resetted my phone
Flashed a stock ROM (the one I'm using right now) via Odin, even re-partitioned the phone with the appropriate .pit file (which didn't erase all data, though, unlike the three-part fw I used on my old SGS1).
Now, using a stock kernel with no improved audio driver is out of the question for me, as it isn't loud enough, especially when I listen to my vinyl rips. Also, I doubt it's related to one of these drivers, because they worked without any issues for almost two years. Of course, a little browsing helps. I've increased max volume of the stock kernel to 63 through system/etc/default_gain.conf. Still, that's not a perfect workaround, because I'm losing all the other nice improvements, like increased clarity, stereo widening (eases the pain of listening to overcompressed audio files), etc; and I'll have to wait and see if this even helps at all. Back to listening...
Could this be a firmware issue that's rooted a bit deeper in my phone? I was having some troubles in the past with a completely broken OS (bricked phone). Should I go looking for a three part firmware and/or another bootloader to set the phone back to absolute zero? Anyone any ideas? Because I have none left.
Ah well, maybe it's really just a firmware bug - I've been using XXUFND3 (Vietman) for several months now, and come to think of it, the problems started roughly around that time. Plus, I was having troubles with SODs, so I've backed up everything, then formatted my whole phone (cache, dalvik cache, system, data, internal storage), applied a mega wipe script, then flashed a XXUFNI2 (Germany) ROM I picked up from sammobile and also re-partitioned the phone. Funny thing is that my wallpaper was still stored and applied to the touchwiz homescreen afterwards.
If this doesn't help, I'll probably have to accept its some kind of hardware issue...
Solved it. Flashing the latest AOSB ROM (v1.3.7, KK 4.4.4) did the trick. I guess there was something messed up deep inside my phone's OS. So no more Touchwiz for me, I'm perfectly happy with CM11 now.
Xelasarg said:
Solved it. Flashing the latest AOSB ROM (v1.3.7, KK 4.4.4) did the trick. I guess there was something messed up deep inside my phone's OS. So no more Touchwiz for me, I'm perfectly happy with CM11 now.
Click to expand...
Click to collapse
probably nfc problem. try to off nfc if u still using tw.
fonblets said:
probably nfc problem. try to off nfc if u still using tw.
Click to expand...
Click to collapse
Thanks for the reply!
In fact I am back to TW by now with no issues. I suspect that AGNi kernel had somehow screwed up my phone, and the bug even persisted after a factory reset. I did some full wipes, format /system, format /data, battery pull, everything all over again, before I flashed the CM11 ROM, and kept the stock CM kernel, so this might have done the trick.
So when I switched to TW again, I also used a clean stock ROM, followed by the latest Dr. Ketan 4.4.2 ROM (v14), keeping the (stock?) kernel provided that came with it. I have had no problems ever since. :good:
Plus, I don't miss AGNi at all, because it was also breaking SWKOTOR support on my Note 2, causing horrible frame drops. This issue is now gone, too.
Hi all,
I was wondering if anyone else was experiencing this, and/or had any solutions - as it's slowly driving me mad.
I do love my M8, but it's getting old and slow running Sense 6/7, and I much prefer the 'pureness' of GPe/CM12.
My phone is SuperCID'd and fully unlocked, and currently flashed the latest RUU for GPe (full firmware) then Candy5 ROM v2.5.5 flashed (based on CM12).
I've tried various Sense firmwares, and other hacked/full GPe firmwares... Bluetooth seems the same on all - works fine on Sense, but not as reliable on non-Sense.
The biggest issue I have is that I have a LG G Watch R and it will disconnect after a few hours, sometimes days, and won't reconnect unless I turn off and on Bluetooth on the phone. Even then it's temporary - I find Wiping Data on com.share.bluetooth makes it stable again for a few more hours/days.
And no, it's not the watch, as if I'm in the car at the same time - that will disconnect and not reconnect either. It's definitely the phone...
Now I generally keep Bluetooth and WiFi on at all times. I only use WiFi at home.
I have noticed it seems to become unreliable if WiFi is on, but hasn't been connected to anything for a while. It's almost like it's "scanning" buffer is full and it's affecting both WiFi and BT (as it's the same chip).
If I keep WiFi off, and only on at Home where it stays connected - my Bluetooth seems really reliable and I don't have an issue.
This isn't a fix, though. As I don't want to have to rely on Llama to switch my WiFi on and off based on my location. Surely a potential battery drain versus just keeping it on at all times.
I've tried a Tasker task to wipe com.share.bluetooth every couple of hours, but it didn't fix it. Would still die beforehand.
I've tried various GPe ROMs, and CM12 ROMs - all as Clean Flashes and not restoring Bluetooth data in Titanium Backup (I only restore user aps + data).
Just wondered if anyone had any ideas!!
Thanks for reading.
I'm having the exact same issue.
Gpe and sense work fine, but cm12,1 just won't stay connected to my car or watch. Very frustrating.
I really want to run cm as my daily driver, but it's totally incapable of keeping Bluetooth up.
Is anyone running cm 12.1 and has working Bluetooth? If so, can you let us know which radio firmware you're using?
I took a stab in the dark and applied firmware 4.16.401.10. So far my watch's connection has been solid. Still haven't tested the car, but will test today. Hopefully it'll be stable - if it is then I'll finally be able to use CM as my daily driver!
Full commute without Bluetooth disconnecting from my car, and I've had a solid connection to my watch for over 24 hrs! WOOOOOOOT!!!!
4.16.401.10 is the trick. Anyone having Bluetooth issues on CM12.1 should go download and apply the firmware. (must be s-off, obvs.)
Firmware is here (courtesy of Mike1986 of ARHD fame)
Ah great news - thanks.
I'll give it a go later!
Should know within 15 mins after if the bug is fixed!
Thanks again.
Update - looks like that's the fix!
Strange it doesn't seem to be mentioned anywhere else but at least it's now here for anyone else.
Thanks for the tip!