Odd occurence. Whichever ROM I use on my t800 bar stock alterations like ironman, I end up with terrible Bluetooth audio dropping up to a dozen times song making it unusable. Sadly I hate Samsung's stock ROM which even cleaned up is still painful to use. Any ideas how I can resolve this or is this a cyanogen related issue that will affect all cm based ROMs?
Any way I can debug it?
Thanks
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....
Has anyone figured out the issues with bluetooth on MIUI for E4GT?
In Summary:
Loss of established connection
Can't pair devices
Drops and reconnects
I see the issues spread all over the dev thread, but there is no apparent resolution. It seems that the issue is intermittent (some people experience it, some do not). Some experience certain symptoms and others are experiencing multiple symptoms. I flashed back to Calkulin's ROM after using MIUI for a couple of days because having no bluetooth is a show stopper for me. Otherwise the ROM is fantastic. Calkulin's is always my default. Smooth, stable, and fast.
Of course, all this might be moot for me once ICS comes out.
So I've had a VZW Nexus for about 5 months, flashed all kinds of custom ICS stuff on it, never had problems.
When Jelly Bean ROMs come out I flash one built from AOSP, works great, after a while an updated version of the ROM hits Goo.IM, I dirty flash+GApps, and suddenly after a few days my phone seems to be stuck in headset mode, not allowing me to use the mic or make calls without using speakerphone mode.
Do full system wipe, factory reset of radios/system/bootloader back to IMM76K, the issue is still there at first boot, hmm, must not be a software issue then.
I Google, this seems like a known hardware issue with the headphone jack, get a replacement from Verizon, it works fine, no problem.
Until I flash an AOSP JB ROM on this working phone, then, just like before, after dirty flashing a JB AOSP ROM upgrade, a day or so later I get the exact same issue, and again full wipes/factory resets don't fix it.
Verizon sends me a new one. This time, I'm staying on IMM76K.
This seems fishy to me, the odds of getting this kind of hardware failure on two different phones after the same sequence of events and there being no relation is astronomically high.
Again, not running any OC's or anything weird. Never dropped the phone. Don't use it in humid environments. Don't even use actual headsets. Used the first phone for months with no issues. Tried SIM/battery pulls. The AOSP JB ROM in question is used by many without this issue, though I have found what seems to be a few more instances of this that have happened after JB upgrades via Google.
Any explanations? Is there a weird bug in AOSP that's frying stuff? Doesn't seem likely or even possible, but then why?
Hello,
First I apologize for opening a new thread instead of posting in the CM11 thread, but till now I don't have write privileges there.
I recently unlocked and permrooted my Desire HD then installed Mustaavalkosta's CM11, but as a newbie, I have some issues I require assistance with. To note that I did an extensive reading before I did any rooting and installing a new rom.
1- I find myself not hearing anything during calls. It's sort of like my internal speaker got muted somehow after installing CM11. I tried multiple apps to no avail. I read somewhere that if u fail to flash the boot.img in the rom u might get this issue, but thing is I did flash the boot.img after I installed the rom and the recovery and wiped the cache. I can hear the calls with the external speaker turned on and with the headphone, so I think it's not a hardware issue but a software one. Any fix to this?
2- After each restart, the UI somehow resets itself. I mean many of the settings and widgets I use either get reset or vanish like the sleep option in seetings for example (I put the screen to turn off after a 1 min and it resets to 15 sec after each reboot which is annoying as hell). Also, many apps like Dolphin and GoSMSPro shortcuts vanish from the home screen after each reboot, while whatsapp for example doesn't. I'm not able to figure why some app shortcuts vanish while others don't.
3- I tried to use ART instead of dalvik, but yet again after each reboot, dalvik is back. So effectively, I can't benefit from ART.
4- other minor bugs which I will not mention for now till I solve the 3 main ones.
If someone can provide some assistance (mainly for the first issue which is the major one), I will be very grateful. It's becoming increasingly annoying and embarrassing to turn the speaker on every time I receive a call, bc most of the times I am in a room with other individuals or in a meeting, and I am forced to have them hear the conversations bc not always I can excuse myself.
No one has any input on this?
After wiping data, dalvik cache, android secure, etc... and reinstalling the stock rooted 2.3.5 Rom, I still had the same internal speaker issue on calls. The heaphone icon was on even though there were no headphones plugged. I installed 2 widgets (togggleheadset 2 and headphone fix) and the issue was fixed. To note I had this problem back on my unrooted stock Desire HD before I rooted it and upgraded to CM11 BR3 thinking the new rom will fix this problem.
So after I made the calls work on Gingerbread stock rooted rom, I did a clean wipe once more and installed CM11 BR4. The problem reemerged. And the 2 widgets couldn't be redownloaded bc they are not compatible with kitkat. The other issues mentioned in the OP disappeared, only the incall volume issue remained.
I need to mention that many Desire HD owners have had this problem on their Froyo and Gingerbread stock builds, and usually the 2 widgets I mentioned above helped fix the issue. On 4.4.2, it seems some android users have complained of in-speaker audio volume being very low, so maybe this worsens the issue I had instead of fixing it.
I'm leaning to think that it's mostly a software/code issue, otherwise why would the widgets fix the problem on an earlier version if it's hardware related? hence, there could be a workaround for it on Kitkat if someone knowledgeable cares to look at it. Maybe the code turns off the internal speaker or lowers the volume so much it becomes unhearable. The headphone and external speaker are just fine, I can hear the other person in the call without any problem. It's when I rely on the internal speaker that I hear nothing.
Hope someone can offer some assistance here.
Hellol
So I have an old S4 and have a problem that I imagine is due to my girlfriend dropping the phone but would like to hear if anyone has an idea of what is going on.
So basically the phone screen wakes every 5-30s (seems to be a random time interval I have used a stopwatch to make sure it wasnt predictable) I originally assumed it was a kernel problem so I switched kernels, then switched roms, then went back to 100% stock and this behaviour happens on every single rom and every single configuration Touchwiz / aosp / CM / Google Edition everything I have tried.
What is strange is something I noticed that is a work around which is that if I play music in the background it never wakes. So basically what I am doing now is having music playing 24/7 and the volume down all the way so I cannot hear it. This is a pretty acceptable work-around but I was wondering if one of you clever folks would maybe have some idea what is going on and why playing music fixes it.
Damage: Screen is cracked in the top left corner where the sensors are, this why I am just assuming is phyically damaged something that.
Current OS: CM 12.1 Nightly.
Tried stock battery + aftermarket battery just in case it was that.
Any insight would be greatly appreciated! Thanks.