Maybe this is not worth a thread, but I (being a noob) haven't been able to find anything .
The problem is as follows:
* <=2.3.3 based "anything" (and I do mean anything as I have tried so many ROMs now that I have lost the count) the bluetooth would show still connected but would actually have lost connection. A reboot is required to solve the issue. Currently running Weapon 3.0 with this issue.
* CM7 and anything else >2.3.3 solves this issue (at least for the ones I have tried) but a mute with bluetooth headset connected would actually not result in a mute. Some folks had very bad experiences... I was lucky
* CM9 KANGs are showing the same issue as CM7.
Can any of the developers please look into it? I can't post in a development thread because of noob status .
When you flash ROMs you are wiping data, cache, dalvik cache, and system right? If you aren't, you're bound to run into some problems.
Yes. I wipe it until I run out of toilet paper .
Related
Hi,
my last installed rom was Android Gingerbread 2.3.6 (Darky-ROM 10.4.).
With this ROM it was possible to make very clear phone calls (with pure and expressive voice) with my galaxy i9000 smartphone via my (bluetooth-)paired handsfree car kit.
Now, I changed to ICS and tested d i f f e r e n t (!) ROMS, p.ex. [ROM ICS]Tiramisu+ I.C.E. A.G.E. V.1.7 (based on the latest CodenameAndroid-ROM), [ROM][ICS][I9000] Team ICSSGS RC4.2, [4.0.4][ROM] Dark Knight 4, [ROM][4.0.4][6-Apr] Slim ICS [3.2] - 70MB Clean, Simple & Fast, [ROM] [ICS] Android Open Kang Project - galaxysmtd, [4.0.4 IMM76D][ROM] EliteV10 Beta ...
With ALL(!) tested ROMS above I have the same PROBLEM:
I'm NOT ABLE to make clear phone calls with my galaxy i9000 smartphone via my (bluetooth-)paired handsfree car kit. If I dial, first the dialtone is very unclear with distorted voice an after, I can't make a phone call - the voice is distorted and I can't understand my call partner.
My problem is NOT a bluetooth pairing problem (bluetooth pairing without problems!).
Anybody with the same problem?
Any ideas/ solution/ fixes (because ROMS says p.ex. "Fully working bluetooth" (ICSSGS RC4.2)??
Maybe it's only a KERNEL-problem? But I tested with the above roms different kernels, too ...
Thx. a lot!
can you pls wipe data and wipe battery status from recovery mod...
as i searched found a similiar problem here...
http://forum.xda-developers.com/showthread.php?t=1593753
Bluetooth
Hi, I have come over from Darky 10.4.2 and have not experienced the bluetooth problem as badly as you describe.
I too have tried many ICS roms and have returned to Darky often as it seems the Darky rom just does it better.
My main problems have been poor GPS, some minor intermittent sound when running music via bluetooth to my car stereo, with some roms (I cannot remember which) giving poor sound for voice call with blue tooth. And of course some where just battery munchers.
I have almost settled on Slim ICS 3.2. I still have GPS & Bluetooth issues and I am trying to solve them. I am thinking of changing the modem which might have something to do with it.
If I have any success I will let you know.
Let me know if you find anything that works for you.
Finally on the gingerbread front I found gamerzrom to be fast, fund and stable, but of course not ICS. They are currently working on an ICS rom which they report is due in a couple of weeks. That is one to look out for.
Good luck.
had the problem in past, but got it solved after a full wipe, try that
Did the all wipes as well as clearing battery stats and problem remains... I'll try the other gaming rom ... maybe ...
i did the following:
- wiped cache
- wiped dalvic cache
- reseted to factory
- formated /system
... problem remains ...
did I forgot anything to "full" wipe?
So here's my issue, my Galaxy S Blaze has been switched from ROM to ROM constantly, I have seen ROMS with modified build.props, other added features, and a bunch of other tweaks, you name it! I don't know what all those tweaks mean, I have no idea if it could affect the way my phone receives the signal but it got me so frustrated that I kept switching roms until finally then I went back to stock and am no longer am switching to another ROM.
Here's a history of the ROM switching I've made in the past couple of months:
1st - MIUI
2nd- Cyanogenmod
3rd- Gummy ROM
4th- Liquidsmooth ROM
5th- Cyanogenmod
6th- Dirty Unicorns (problems with signal started occurring right about here, and onwards)
7th- Stock ROM (hmm... nope nothing fixed.)
8th- Validus (still no, I didn't like the constant force-closing of many apps)
9th- Gummy ROM (nope, what's worse is my screen kept freezing if I had atleast 2 apps open and I slid down the notification drawer)
10th- Cyanogenmod (well, maybe switching to cyanogenmod will fix it)
11th- Gummy ROM (*sigh* switching back? Nope, still didn't help my signal)
12th- Stock ROM (you would expect it to be fixed right about here, but nope)
So what's up what is the exact problem with my signal? Here's the thing: My signal works! That's a start atleast. However, if I turn on my Wi-Fi while I'm home, I can still call/text people, all of that works. But after maybe 2 hours or so, the signal bar is still there, it's telling me it has signal and it's connected, SOMETIMES it will be empty meaning I have no signal(when I really do). But in reality, I can't receive texts, nor calls, none of that. So how do I fix it? By restarting my phone sadly, that has been the only solution for me for these past 2 months. People have complained to me because I don't answer my phone anymore, well I'm sorry my phone can't receive those calls due to this messed up signal. There are 3 other T-Mobile phones in the house that have no problem! The problem here is with my Blaze phone.
So what if I turn the Wi-Fi off for the whole day and see if it's the main thing causing the issue? Well, I did this. Turns out that the signal stays on longer than when I'm on Wi-Fi but it still goes out. I have switched SIM Cards, I have tried switching my APN: from "epc.tmobile.com" to "fast.t-mobile.com" but the problem appears to happen more quickly on the "epc" one than the "fast" one. Please help me with this, this has been frustrating me a lot lately. I'm not sure if anyone has even had the same exact problem that I'm having, I've searched online but haven't seen a similar problem.
Some of you might say, wow that is a lot of ROMS you've switched to, I'm sure there were more that I missed but that's as of recent. I can install ROMS correctly, I know how to use CWM when installing a .zip and using Odin when it's a .tar(or other supported file extensions). I've factory reset, wiped the cache, the dalvik cache, all before installing a new rom. After installing each rom, I've also factory reset and wiped the cache to make sure no other problems could affect the way the rom would work. Hopefully I did the procedure right, thanks for anyone who's willing to help me!
Right now I am running:
Baseband Version:
T769UVLH5
Kernel Version:
3.0.8-perf-T769UVLH5-CL990184
[email protected] #1
SMP PREEMPT Fri Aug 17 15:12:14 KST 2012
Android Version:
4.0.4
Another Issue is that I can't even transfer files to and from my phone when connected to my computer! This is another big issue, here are some images:
http :// i.imgur.com/xx699ss.png
http :// i.imgur.com/1wRzJpX.png
Here's what happens when I turn Wi-Fi Calling on but maybe it's just a built-in function that I forgot it had and it's probably normal:
http :// i.imgur.com/cTSqRci.png
By the way, sorry for the links just copy and paste them in a browser to and remove the spaces between the http :// and i.imgur, thanks! Unfortunately, I can't post links until I reach 10 posts. If the links don't work for you, I've also provided attachments.
Many thanks!!!
That last picture does show the proper function of Wi-Fi calling however I don't know what to say about the rest of your problems.
Sent from my SAMSUNG-SGH-T769 using XDA Free mobile app
There are two things I would recommend trying...
1. Use Blackhole System Wipe
I know you've been following all the proper steps in CWM (and I would say to keep doing so), but I've added using Blackhole, in addition to the first steps, and I always get great system performance on my phone, and my parent's phones (I put them on ProvisionMod after stock was being stupid). It works well for pre installation for ANY ROM and helps prevent pesky issues. However, chances are, your issue is baseband related and this probably won't solve it... But still! You never know! It's worth a shot!
2. Reroot your phone
I know this will be annoying and pesky... but sometimes the process goes wrong from the beginning and starts giving issues later on... When I first rooted my mom's blaze, something went wrong, despite my following all the directions, and one of her partitions was completely disabled, no matter the ROM. I redid the process of rooting her phone (not from GB though... From the ICS stock) and fixed the issue instantly! I would try these two steps first and see if they do anything! Good luck!
Sent from The Doctor's Blaze
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Termuellinator said:
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Click to expand...
Click to collapse
*push* nobody got any ideas? i would post it in the appropriate thread (especially since this rom is still only nightly) as a potential bug report, but as a new user i'm not able to :/
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Termuellinator said:
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Click to expand...
Click to collapse
The WiFi bug is a known issue since early August. It affects almost every Moto device (G, G 4G, X and defy?) it's reported several times to CM-s bug tracking system, but nobody cares... You can use custom kernels. Maybe they aren't affected.
I don't know anything about the BT bug.
i found some posts about people having the same kind of wifi-issue, but it is good to know, that the devs are aware and - kind of - working on it
the BT-thingy is driving me insane though...fiddled around a bit, stopping BT-Related processes etc...this somehow did something...my phone now connects and stays connected, i can make phone calls...but the contact list is incomplete - only 3 random contacts are displayed on the car system
haven't rebooted since then, i kind of fear that rebooting will bring back the issue :/
BT still working after reboot, so it seems my "fix" is permanent...must have something to do with deleting the BT-data/cache while process was killed i would think - in case someone else also encounters this problem
still can't acces all my contacts from Car-system though :/
Most nights roms have a lot of issues and it is pretty hard to stay aware all of bugs. Why don't you try something more stable like Pac Man RC or some. Sometimes a different kernel will help sometimes it's the opposite.
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Termuellinator said:
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Click to expand...
Click to collapse
All AOSP rom uses the CM device tree and kernel as a base, so the low level kernel bugs are the same.. Also the last "stable" CM for falcon is dated back to April, so you didn't lose anything with peregrine...
Just in case anyone encounters the same Issues:
with CARBON-KK-NIGHTLY-20140922-0414-peregrine the BT-Problems seem to be resolved, connection works and the contacts are accessible from the car.
WiFi still has problems with dhcp, but as stated, devs are aware of that :good:
bad news: flashed to CARBON-KK-NIGHTLY-20141103-0939-peregrine and the BT-issue is back as in the beginning - com.andoird.bluetooth stops working - but only following the first connect -.-
interestingly going back to my pre-flash-backup didn't resolve the issue (doesn't matter if i just restore or wipe prior to that...but after flashing/restoring the first connect works perfectly)...perhaps that leads to some ideas about the cause?
was just trying to get it to work like the other time by stopping/deleting data of com.andoird.bluetooth, but didn't work this time
ok, figured it out again, this time i'll post my steps in case anyone ever encounters similar issues (and for my future reference in case i encounter them again, too )
1) unpair
2)switch off bluetooth
3) stop com.android.bluetooth in "apps"
4) delete data of com.android.bluetooth
5) reboot
6) pair
7) unpair
8) delete data of com.android.bluetooth
9) pair
10) reboot
at least these are the steps i did and it seems to be working now, again
(EDIT) Solution: I remember a long time ago when I went from stock to CM11 I lost all GPS capability. It was determined this is just a random occurance and all you need to do is flash back to stock, get a lock, then reflash CM11 until the lock sticks. With this previous tactic, I applied the same principle to the bluetooth issue since it was apparent I had a unique situation and most did not have issues. Steps taken to fix the bluetooth issue:
Step 1: Backup everything to external SD
Step 2: RUU back to GPE 4.4.2 (found VZW variant on XDA)
Step 3: OTA Update to 4.4.4 because the build needs to be higher than 4.4.2's build
Step 4: Ran bluetooth through car for a little bit and also ensured I had a GPS lock
Step 5: Reflash CM Recovery
Step 6: Wiped /system, /data (sdcard), /cache, and /dalvik
Step 7: Flashed CM12. Restored via Titanium Backup and on 3rd day without bluetooth dropping out yet (fingers still crossed)
Obviously I did not provide much detail on the steps because there are numerous tutorials already. However, if someone would like more explicit instructions just ask.
----------------------------
Greetings. A few weeks ago I made the jump from CM11 to CM12. I first did a dirty flash and a had a few problems so I ultimately did a clean flash. I transferred everything to my external and wiped everything else (system, data, dalvik, cache) then reinstalled CM12. Both on CM11 and CM12 I noticed that my bluetooth, when connected to my car streaming audio, would randomly disconnect. The phone would still think it was connected, but my headunit would lose the connection. This never happened on CM11, leading me to believe the headunit is not the culprit. I've erased the bluetooth cache, wiped cache in recovery, and deleted and repaired numerous times.
Android 5.0.2
CM version 12-20150320-NIGHTLY-m8 (has been happening since I first switched in the beginning of March)
Kernel: 3.4.0-g1ac088b
What I've observed:
- I cannot force the disconnect through any specific action
- It almost exclusively (cannot say for 100%) happens when the screen is off
- It does not happen every time the screen is off
- I've tried in both performance and balance mode -- no difference
- I've never had this problem before going to CM12
- When the connection is working, everything works as expected (no volume issues, can control through headunit, etc)
- If I disable then reenable bluetooth the devices will reconnect and work until the random disconnect occurs again
- When connected as phone only, it does not disconnect. It is only the audio profile (A2DP I believe)
Has anyone else observed this as well? Furthermore, does anyone have a solution? I've scoured the interwebs and I found a few issues but all related to the One Plus One -- and those solutions did not work for me.
Any help is greatly appreciated. I did a CATLOG and noticed numerous bluetooth issues, but I do not have the log on me at the moment. I can recapture it and post it if it helps.
Thanks.
Bill
Posting in Q+A since I didn't see anything like this amongst the Relay ROM threads...
I flashed my ROM to Validus 5.0.2 a couple of months ago, and discovered my GPS had stopped working. However, it was not like most cases of it failing that I had read (where it seemingly tries to get a fix but never does). Instead, any attempt to use the GPS in any app would crash and reboot the OS. I tried GPS Status among others in attempting to clear AGPS data, etc. with the same end result. Even GPS Status would crash while loading the GPS.
I had a suspicion that since Validus (and maybe FatToad also?) borrowed at least some functions from CM12, it also brought along a CM12 bug involving NVRAM corruption upon flashing (don't quote me lol, this is what I vaguely recall reading somewhere here). At least, CM12 ROMs on (at a minimum) D2 chipsets around the time of Validus's release in Feb. seem to also display GPS issues. Same goes for Validus builds on multiple other Samsung devices, among others, IIRC.
Not wanting to flash ROMs between stock and custom multiple times and maybe hopefully fix the problem (since I didn't see confirmation it would fix what *I* was experiencing), I bought a new phone for a daily (just in case) and tried the attached patch (believed I just used the hw patch). Much to my surprise, it worked! No bricked phone, just a functional GPS.
Unfortunately, since it was a little while since I found the patch, I don't completely recall its origin, other than it was to repair another D2 Samsung device with CM12 (may have been S2 or S3).
YMMV with the attached patches. It may fix the laggy acquisition as well, but I was not trying to repair that particular issue in my testing.
USE AT YOUR OWN RISK! Nandroid first! I take no responsibility if this patch results in data loss or sets your phone on fire.
I also make no claim to have created this. Credit goes to the mystery person somewhere in XDA who created/found this patch for an alternate device.
I am curious to see if the patch helps anyone else avert wiping their Relay to fix GPS. I hope it will help someone out.
DIRECTIONS: Place the attached zips into your sdcard, then flash from recovery. For good measure, wipe your Dalvik/cache after flashing before you reboot. You should only need to flash one of the zips for the fix to take effect. If the hwonly patch has no effect, then try hw+configs.
NOTE: Patch was tested on 5.0.2 Validus ROM. I am not sure if this works with other ROMs or Android versions. If you're willing to try it, let us know the results.