[Q] 2/22/11...bluetooth not work after installed eb13? - Epic 4G Q&A, Help & Troubleshooting

i installed eb13 froyo and rooted my phone with cwm3.0.0.5 , then flashed viper rom trinity 2.0 with the eb13 genocide 1.2 ghz..everything seems to be very good and fast, but so far i have noticed that the blue tooth is not connecting. does anyone have any answers to why bluetooth is not connecting?

so i toggled around with my settings and now my bluetooth is working allowing me to answer phone calls and talk on the phone but the only thing that my bluetooth doesnt do is allow me to give voice commands when i tap on the button on my blue tooth!!! any advice anyone?

How did you get the headset to take calls?

Bluetooth Issues - Summary of Testing Results
This is a problem that goes away if I simply go back to a DK28 based ROM (which I have no plans of doing), but appears with any flavor of the EB13 update available.
On a day when I didn't have a lot to do, I decided to do some testing to see if I could find the magic combination of EB13 loading (upgrade.apk, ODIN .tar/.pit load, Samsung SWUpgrade and the DEODEXed [stock-ish] ROMS available) to get my bluetooth working like it does on DK28. I have upgraded to EB13 stock, EB13 deodex, deodex w/EXT4 (no member ROMS yet) along with stock/Genocide/Daemon's kernels ... essentially every mix of install, ROM and Kernel available. Add to that, I also cleared data on the OPP application --- I tried to cover every base I could. That being said, I have narrowed down my list of issues with bluetooth on EB13 to:
Paired devices are not saved. I have a Jawbone ICON and I have to add it everytime my phone is rebooted.
(Only add once on DK28)
Unable to Pair and Connect on first attempt. It always takes at least 2 and most of the time 3 presses of Pair and Connect to get the Jawbone paired and connected.
(Paired and connected on first attempt on DK28)
When my Jawbone pairs up, if you watch the notification bar closely, my wifi will also do a quick off/on right after the notification shows "Paired" on the Jawbone. Before you ask - yes, I ran tests with the various radio's on and off just to see if that was the cause. Nope.
(Never saw this on DK28, but then again was not watching for it either)
Like others have said, I can voice dial using the Voice Dialer application on the phone, but I cannot voice dial by pressing and holding the voice dial activation button on the Jawbone (the start/stop/quick disconnect happens on the application).
(Press button, state name, call on DK28)
It did not matter what combination of the above I used, the result was always the above. I'll gladly assist in troubleshooting this issue, so if anyone out there knows what to look for in the logfiles, I'll gladly run a pair/connect sequence and capture the adb logcat output for review.
Thanks in advance ... None of these are showstoppers, in fact I love EB13 and also appreciate all the hard work done by the devs and contributors in these forums (plus I guess I need 10 posts now to add anything relevant to a dev thread ).
- Dan

If you use Titanium Backup and have backups from before the update, please read this:
I was having the same problem with bluetooth on EB13. Just before ODINing back to DI18, I decided to try this:
1. In Titanium Backup>Backup/Restore, find these three items backed up from a previous kernel: Bluetooth Pairings, BluetoothTest 1.0, BrcmBluetoothServices 1.0. --Touch and restore each one of these.
2. Go to Home>Menu>Settings>Wireless and Network>Bluetooth Settings (turn on bluetooth): If your device is listed as paired, unpair it. Pair it again as a new device.
This worked for me, except voice-dial through my Jawbone is force-closing (but I honestly don't know if it ever worked right anyway). At the very least, it is now pairing and connecting fine and staying connected for calls and music.
P.S.
I suppose if you don't already have a backup of these items you could ODIN back, get Titanium Backup, backup all apps and system data, then update to EB13 all over again and restore the bluetooth data.

If you flash the acs frozen rom bt voice dialing works and the rom is very fast and very smooth. The best rom I've seen yet.

I've been having problems with Bluetooth on MidnightROM 4.2. The Bluetooth is extremely flaky -- sometimes pairs, sometimes doesn't -- doesn't stayed paired.
I haven't struggled with it too much because I never used Bluetooth much, but I would like to know if there's a fix.

jbadboy2007 said:
If you flash the acs frozen rom bt voice dialing works and the rom is very fast and very smooth. The best rom I've seen yet.
Click to expand...
Click to collapse
ACS has these same issues. It is a EB issue and I find I am having the same problems.

Related

[Q] EVO 4G - Bluetooth Killing WiFi!? Anyone else having this issue?

I have one of the 1st White EVO's from Sprint and ever since It's been Rooted and running various ROMs I've had this issue where Every time I get a call and use my BT-Headset, it kills my WiFi connection. If I use my Speaker phone option the WiFi stays on and works just fine. Roms I've tried and this issue persist: AVA-Froyo, Fresh Rom, Freak-E Froyo, and currently running MIUI. All have been the latest versions. I've update my Radios with the current Radio "Combo Zip" and still have this issue. I've tried various headsets from the $9.99 Cheapo's to my $99.99 Plantronics Voyager Pro+ and still have this issue. If there is something I'm missing or anyone else has had this issue with the EVO, please help or point me in the right direction. What's the point of having a phone that's supposed to multi task with Voice and Data if the built-in features are killing each other?
*!Update!*
======
I am now running the latest [EVO NonSense v3.4] ROM and it's all good. I've made several calls and my WiFi and 4G are working as they should. Plus my Bluetooth transmission is a 100 times clearer as well. I'm no expert, but my only conclusion is that it could be the Kernels.
Does anyone know if the [2.6.32.15-gof673ed [email protected] #10] will work with the above mentioned ROMs, particularly the latest MIUI?
Thanks in advance for any help and quick replies.
I posted about this a little while back, have the same problem
On call through my voyager pro wifi is intermittent. I don't think it kills it, only makes it so slow that almost everything times out. Almost randomly it goes in and out. Same with 4g as well
Edit: Not rooted

[Q] is there a fix for bluetooth?

is there a download or fix for the bluetooth voice command....my bluetooth works but when i push the button on the bluetooth it says give command and then there is an error followed by, it disconnects. any advice on what to do or where togo to get the fix for this problem?
I've not been following the latest news on Epic, but if Sprint has released 2.2 I think you need to manually update your phone. Though from what I've read in the previous days was that Sprint did send out an update to some Epic users but the update was buggy. Therefore not everyone had their phone updated. Though assuming you're new to this forum ? And perhaps your Epic ? If your phone has 2.1 then there's no way you're going to be able to use your headset as 2.1 isn't capable of dialing out only accepting calls and manually making calls. I'm using midNIGHT custom rom and by using midNIGHT my headset does dial out. So join in on the forums and read up. I know there was a recent post http://forum.xda-developers.com/showthread.php?t=967014 That should be of great assistance to making your phone a lot better. Though most importantly I'm new here too and perhaps someone can give you better advice. But I do know that your phone out of the box won't allow you to voice dial using a headset until you're updated to Froyo and that I recommend midNIGHT rom but there are many roms to choose from as well as a lot of reading and learning which can be fun.

[Q] Bluetooth keep crashing

I am using NexusMod ICS Zero - [4-19-12] Modified for T989 - 2nd Release
I try to flash with SuperWipe, without superwipe, Darkside Superwipe, M&S Kernel clenser, with format everything, with clear everything.
Don't know what else I should try.
how come when I come back to my restore (which is easydoes ICS ROM) the bluetooth works fine (I have to re-pair in my car after restore, because I clear the bluetooth system in my car evertime I pair the new rom)?
For me bluetooth didn't work for any of the new UCLD2 ROMS.
The bluetooth worked on the earlier ICS leaks.
Here is the LogCat for the crash
LogCat Link
Thanks,
here is the logcat for the fresh install and fresh test with the car bluetooth.
Can someone tell me what direction I should look at?
just flash your stock rom/ or just radio
there is no ICS Stock Rom available for flashing.
and I did flash the LB7 radio
I tried Gingerbread stock works fine....
then install NexusMod and same issue.
UCLD2 broke bluetooth for me also (Skyrocket). Works fine on the first ICS leak though (UCLC something).
It pairs to my JVC car stereo.
But buzzes/crashes when trying to stream.
Bluetooth will turn on/off over and over.
I still not able to find any fix or way around.
Please update this thread if you find one.
Sent from my SAMSUNG-SGH-T989
Eddie
What is the version of your cmw?
I am on 5.0.2.7
Not cmw touch. Dunno maybe its working with cmw touch only.
Sent from my SAMSUNG-SGH-T989
I read it on skyrocket forum the Dev said on nexusmod thread that you have to be on cmw touch.
I update my cmw to touch and then reinstall the ROM and that didn't help either.
That's weird. Have no clue why Bluetooth is not working...
Anyways back to the first leak for now...
Sent from my SAMSUNG-SGH-T989
As I stated in the NexusMOD thread, bluetooth integration to my car is broken as well. Haven't tried v3.3 yet nor have I tried the make nandroid -restore from nandroid trick mentioned in the T989 NexusMOD thread... Am still hopeful that a new leak will come out with a different BT stack which fixes this
-greenboy- said:
I still not able to find any fix or way around.
Please update this thread if you find one.
Sent from my SAMSUNG-SGH-T989
Click to expand...
Click to collapse
I noticed "bluetooth" kept showing up on my CTS stereo like it was connecting. Under bluetooth click menu button and set visible timeout (mine was set to 2 minutes). I set mine to unlimited, since then it stopped showing up on my stereo.
wave_sailor said:
I noticed "bluetooth" kept showing up on my CTS stereo like it was connecting. Under bluetooth click menu button and set visible timeout (mine was set to 2 minutes). I set mine to unlimited, since then it stopped showing up on my stereo.
Click to expand...
Click to collapse
Thanks for the feedback.
I re-install the ROM with 3.8 update and tried your method but that still not stop crashing the BT and transferred the call to the handset and disconnect from the car BT.
I guess I have to wait for the new leak with the hope that it will not have this issue.

After AT&T JB update, Bluetooth connection keeps dropping (paired with car)

Since I upgraded my AT&T Galaxy S3 with the official Jelly Bean update last week, my bluetooth pairing with my car has not worked.
At first, I was continuing to use the existing pairing which was set up and perfectly working in ICS. Whenever I made a call from my car ('09 BMW 3-series, bluetooth phone via built in nav system), there would be a loud pitch sound when the call was answered and then connection lost.
So I unpaired, and re-paired.
But now it does not work at all. Connection keeps dropping every few seconds. I have not even managed to get the data sync (transferring of contact data from phone to car) to complete.
This is beyond me. Jelly Bean is great, but it is not worth the price of not having properly functioning bluetooth.
Any suggestions? Anyone with similar issue? Is it possible to somehow roll back to ICS?
I know this is a typical response for any issues after an upgrade, but have you tried a factory reset?
Also can you delete your phone from your cars memory(I know mine remembers all phones that have connected to it) might help.
nsmith4 said:
I know this is a typical response for any issues after an upgrade, but have you tried a factory reset?
Also can you delete your phone from your cars memory(I know mine remembers all phones that have connected to it) might help.
Click to expand...
Click to collapse
Thanks for your response.
I have not (yet) tried a factory reset, was sort of hoping to avoid the hassle of having to restore my data and apps. But I will eventually resort to it, if nothing else can fix it.
Good suggestion with regards to erasing from car memory. I am not sure if or how that can be done, but I will try and look through the settings to see if I can. (what I have done so far is just "remove" the device from the list of paired devices...
nsmith4 said:
Also can you delete your phone from your cars memory(I know mine remembers all phones that have connected to it) might help.
Click to expand...
Click to collapse
Pretty sure this is the actual cause of your problem.
HiKsFiles said:
Pretty sure this is the actual cause of your problem.
Click to expand...
Click to collapse
I went through all possible options in my car's nav system (xDrive) and I do not see any options to delete the car's memory.
So the only option as far as I know is to remove the device from the list of paired devices before pairing it again. And I tried that already...
Look through All Applications in Application Manager for BT share. Wipe data for that. Be warned this should wipe all your bt pairings.
Ok. So I resorted to restoring to factory settings.
With it clean, before restoring backup (made with Titanium), I went to my car and paired.
It worked - it synced the (very few, AT&T default) contacts, and no dropping (as far as I waited, a few minutes).
This was good news.
So I went back up and restored all app data, signed into Google account to sync all contacts etc.
Then back down in car and connected.
Problem is back It won't sync the contacts and continously drops and reconnects.
Well at least I have a reference point to go back to now and perhaps take one step at the time.
I was thinking next step is to restore to factory settings again, then ~only~ add google account to sync up contacts, then try. If that works, restore one app at a time to see if I can isolate the issue.
I will do this tomorrow.
mrhaley30705 said:
Look through All Applications in Application Manager for BT share. Wipe data for that. Be warned this should wipe all your bt pairings.
Click to expand...
Click to collapse
I just did this. I am however too tired for the day and will check first thing in the morning, if this resolved it (as I am back in the problem state) - before resetting and starting all over (ref. my above mentioned thoughts of how to do a gradual restore)...
Thanks all for your input so far - I cannot tell you how much I appreciate it. This forum rocks so far.
/Lars
Progress this morning:
First of all, I tried as suggested clearing data for Bluetooth Share. Didn't fix the problem.
I know now that if I pair the phone and connect after factory reset, with the contacts list on the phone at default/almost empty (11 pre-defined AT&T numbers), it works.
So what I did this morning:
I factory reset the phone again. Then I added my Google account to sync up contacts list from my GMail account.
I ~only~ did this. No apps installed or restored.
Paired and connected. And I have the problem.
So this seem to somehow be caused by my contacts list after it has synced up with Google.
Any suggestions?
I am thinking that if I cannot get this resolved, I want to roll back to ICS. Having no functional bluetooth pairing with my car is not an acceptable tradeoff, no matter how great JB is. Is there a way to roll back? Can I get the official ICS ROM from AT&T, if needed?
But of course - this will be my final solution; I much prefer to get this resolved. I am open to any suggestions re. my contacts/google account.
You have an old problem. There are stock roms and instructions to do it stickied on the original development forum. I suggest you download the jb version of your carrier and flash that through Odin first.
If that doesn't work, then go back to ics
Sent from my SGH-I747M using xda app-developers app
Deoxlar said:
You have an old problem. There are stock roms and instructions to do it stickied on the original development forum. I suggest you download the jb version of your carrier and flash that through Odin first.
If that doesn't work, then go back to ics
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Thanks for your feedback.
Can I ask, if you know where this problem is perhaps discussed?
I looked in the developer forum, but must admit I am confused which thread/which ROM you are referring to. Are you talking about a modified stock ROM? I would greatly appreciate a link if it is...
Today's update:
At work we have a Galaxy S3 AT&T device (identical to my own) for testing purposes.
I just upgraded it to Jelly Bean today and then added my gmail account to it, paired to my car - and the same problem.
So at least that rules out an issue with my specific hardware/phone.
I also tried using a Galaxy Nexus (Verizon version) from work. Issue did NOT happen.
I then flashed my own phone with the stock Jelly Bean ROM downloaded from here:
http://forum.xda-developers.com/showthread.php?t=1739426
Same issue happens
So my final solution (at least for now):
I flashed to the stock Ice Cream Sandwich ROM (downloaded from same place as listed above).
It works now.
Funny how one can be so happy with a downgrade, but I am
Thanks all for all your input.
I am still open to any suggestions (as I would love to be on Jelly Bean in the future), and I have an easy way to test possible solutions on my work test device...
Thanks again!
Lars
Hey, I am having Bluetooth problems as well. I have the sprint s3 stock jb. My blue tooth will not connect to my moga controller. Everything I have been reading points at it being a software issue on Samsung JB devices. Can anybody else confirm this?
Sent from my SPH-L710 using xda premium
Aren't the bluetooth "drivers" in the kernal? Perhaps using a different, or going back to a stock kernal.
I was having a similar issue with my phone not automatically connecting with my car. It would connect if I cycled BT off then on. All this on Tasks 4.1 rom & KT's kernal.
Flashed with the new 4.2 rom & kernal and it seems to be fixed.
Just curious, did the OP ever try a factory reset? I'm on Blackjelly, which is a ROM heavily based on AT&T stock JB and I have no issues with my Bluetooth whatsoever. However, I do have the KT747 kernel installed, which has its own set of bluetooth drivers.
crazililazn said:
Just curious, did the OP ever try a factory reset? I'm on Blackjelly, which is a ROM heavily based on AT&T stock JB and I have no issues with my Bluetooth whatsoever. However, I do have the KT747 kernel installed, which has its own set of bluetooth drivers.
Click to expand...
Click to collapse
I have a Verizon S3 (running stock) and the same problem is happening. I've even tried a factory reset but that doesn't seem to have helped although I'm still testing it (need to go drive for a while). My car is a 2010 Audi A4. I've spoken to both Samsung and Audi and both tell me it's not their problem. I'm hoping Samsung updates the phone with a backwards compatible BT driver or Audi upgrades their driver. I am not happy.
EDIT: I drove some more today and bluetooth only dropped once. The strange thing is that while I am driving I only see 2 bars on my dashboard screen when the phone shows 5 bars. I would "assume" that the phone is the most accurate signal meter. In any case, everything "seems" to be working better although not as well as before.
Bluetooth in car only has voice audio, no ability to control the phone
Ansextra said:
I have a Verizon S3 (running stock) and the same problem is happening. I've even tried a factory reset but that doesn't seem to have helped although I'm still testing it (need to go drive for a while). My car is a 2010 Audi A4. I've spoken to both Samsung and Audi and both tell me it's not their problem. I'm hoping Samsung updates the phone with a backwards compatible BT driver or Audi upgrades their driver. I am not happy.
EDIT: I drove some more today and bluetooth only dropped once. The strange thing is that while I am driving I only see 2 bars on my dashboard screen when the phone shows 5 bars. I would "assume" that the phone is the most accurate signal meter. In any case, everything "seems" to be working better although not as well as before.
Click to expand...
Click to collapse
Hi guys,
I have the same problem.
Details:
Phone: GALAXY S3 I747M
Carrier: Rogers
What happened?
Let me start by saying Bluetooth was flawless before moving to Jellybean (flawless means it would work consistently EVERY time on all featureS). Data and Voice between my Car (2010 Audi A4). I consider data the phonebook information back and fourth to the car, the ability for the car to control my device (make calls, end calls, switch calls) and the number of bars for reception.
I upgraded to Jellybean, then stuff wouldn't work (Bluetooth, GPS, 3G, wifi, etc.), so I tried a few roms (I would factory reset, wipe cache, wipe delvik cache, format /system EACH time I swapped ROM's). Unable to get anything to work consistently with everything. I downgraded to 4.0.4 (Using the WanamLite ICS SGH-I747 V1.3 Android 4.0.4 ROM).
Everything started working again! EXCEPT Bluetooth. It connects with no problems, but it seems like it's only the voice part, the data part (as decribed above) doesn't...I can tell by not seeing any information go back and fourth between call logs and the wrong number of bars for reception, it's like the connection is jumbled.
Unfortunately, it's inconsistent to around 50% of the time, sometimes it DOES work.
Voice/audio through phone calls work ALL the time. IF someone calls, the car recognizes it and the audio mic and through speakers work...but the car doesn't realize it's happening enough to give me options (like ending the call from the car).
This only happened once I went from Jellybean and then went back....not sure what's happened...
Appreciate your help and thanks in advance!
rohanverma said:
Hi guys,
I have the same problem.
Details:
Phone: GALAXY S3 I747M
Carrier: Rogers
What happened?
Let me start by saying Bluetooth was flawless before moving to Jellybean (flawless means it would work consistently EVERY time on all featureS). Data and Voice between my Car (2010 Audi A4). I consider data the phonebook information back and fourth to the car, the ability for the car to control my device (make calls, end calls, switch calls) and the number of bars for reception.
I upgraded to Jellybean, then stuff wouldn't work (Bluetooth, GPS, 3G, wifi, etc.), so I tried a few roms (I would factory reset, wipe cache, wipe delvik cache, format /system EACH time I swapped ROM's). Unable to get anything to work consistently with everything. I downgraded to 4.0.4 (Using the WanamLite ICS SGH-I747 V1.3 Android 4.0.4 ROM).
Everything started working again! EXCEPT Bluetooth. It connects with no problems, but it seems like it's only the voice part, the data part (as decribed above) doesn't...I can tell by not seeing any information go back and fourth between call logs and the wrong number of bars for reception, it's like the connection is jumbled.
Unfortunately, it's inconsistent to around 50% of the time, sometimes it DOES work.
Voice/audio through phone calls work ALL the time. IF someone calls, the car recognizes it and the audio mic and through speakers work...but the car doesn't realize it's happening enough to give me options (like ending the call from the car).
This only happened once I went from Jellybean and then went back....not sure what's happened...
Appreciate your help and thanks in advance!
Click to expand...
Click to collapse
It's a know JB problem. No solution right now
Ironically, I had the same exact bluetooth problem the OP describes, but it happened with my stock ICS ROM. Made trying to call someone extremely frustrating since I have a stickshift!
The problem disappeared with my upgrade to the 4.1.1 stock ROM. I have also had no issues at all with any 4.1.2 JB custom ROM.
I believe it is a generalized issue with Android, because the problem I had with ICS was not reproducible when using a different bluetooth headset. Only my own would cause the problem. As soon as I realized that the problem no longer existed in 4.1, I began using my own headset again, and have done so without a single dropped call.
BWolf56 said:
It's a know JB problem. No solution right now
Click to expand...
Click to collapse
Thanks, but just for clarification. It was working on JB perfectly. I upgraded to ICS, thats when bluetooth with my car stopped working (with a number of other things). So i downgraded BACK to JB (stock rom) and I still have the same problem.
It's almost like the data side of the connection is all jumbled up....did ICS leave something on my phone (I did a factory reset, wipe cache, wipe delvik cache, format /system when switching back).
So I feel like it wasn't a JB problem it was an ICS problem, but reverting back to JB didn't fix the problem, so I feel like ICS left something on there that the old rom didn't overwrite. Any files I should be checking to ensure that isn't the case?
Thanks a lot!
rohanverma said:
Thanks, but just for clarification. It was working on JB perfectly. I upgraded to ICS, thats when bluetooth with my car stopped working (with a number of other things). So i downgraded BACK to JB (stock rom) and I still have the same problem.
It's almost like the data side of the connection is all jumbled up....did ICS leave something on my phone (I did a factory reset, wipe cache, wipe delvik cache, format /system when switching back).
So I feel like it wasn't a JB problem it was an ICS problem, but reverting back to JB didn't fix the problem, so I feel like ICS left something on there that the old rom didn't overwrite. Any files I should be checking to ensure that isn't the case?
Thanks a lot!
Click to expand...
Click to collapse
Umm just to clarify, firmware goes like this (in order): Eclair, Froyo, GB, ICS, JB. So JB is the latest.
Here's a JB fix for BT: https://dl.dropbox.com/u/28275651/REVERT-MY-ALSA.zip
Flash it in recovery, clear cache and dalvik and hopefully it will work.

[Q] Bluetooth headset + call = no network

Hey everyone,
I am happily using the following on my N7100:
Agni Kernel 4.3.7
UNOFFICIAL CM 12 build (15.12.2015 release)
I came from using the nightly CM11 builds with the applicable Agni kernel and used that up to 3 weeks ago. I encountered an issue however which made me take the step from CM 11 to CM 12 and it is as follows:
Whenever I connect my car/headset/whatever to my phone via BT, the connection is perfectly fine. Listening to music works like a charm so nothing wrong there. However, whenever I receive or place a call and the phone is about to connect, the network completely vanishes. I get an error that I am out of the service area and it takes a good 5 minutes at least (with BT still connected) to get reconnected to my cellular network. Whenever I turn BT off, the network comes back in a few seconds.
I tried using the standard kernel to no avail. Normal calling (i.e without BT connected) works fine. It seems to be specific with BT connected and making a call or receiving one. Having BT turned on (no connection) and placing or receiving a call works perfectly fine as well. What can I try to resolve this or better yet; does anyone else have these issues? Could this be a hardware failure? What I can try or have tried thus far for troubleshooting:
Tried:
1. Dirty flash from CM 11 to CM 12 --> nope
2. Clean wipe and install to CM 12--> nope
3. ( I read this somewhere else) Turned on 'only connect to 2G networks'. I seem to be able to get a call *sometimes*, but the call drops midway or is garbled with high pitched noises
4. Turned off Data Connection completely whilst BT is connected to make a call --> nope
Can try:
1. Revert to stock ROM to exclude issues with CM ROMS (this does mean going back to 4.4.4/4.4.2 sadly )
2. Try another Lollipop ROM as opposed to the one from Ivan_Meler (Clicky)
3. ????????
I did look at the forums here and everywhere else I could think off on the net/Google but I did not find anything really close to what I am seeing. Unless my Google-fu has failed me for which you have my sincerest apologies
Cheers!
Notna_01 said:
Hey everyone,
I am happily using the following on my N7100:
Agni Kernel 4.3.7
UNOFFICIAL CM 12 build (15.12.2015 release)
I came from using the nightly CM11 builds with the applicable Agni kernel and used that up to 3 weeks ago. I encountered an issue however which made me take the step from CM 11 to CM 12 and it is as follows:
Whenever I connect my car/headset/whatever to my phone via BT, the connection is perfectly fine. Listening to music works like a charm so nothing wrong there. However, whenever I receive or place a call and the phone is about to connect, the network completely vanishes. I get an error that I am out of the service area and it takes a good 5 minutes at least (with BT still connected) to get reconnected to my cellular network. Whenever I turn BT off, the network comes back in a few seconds.
I tried using the standard kernel to no avail. Normal calling (i.e without BT connected) works fine. It seems to be specific with BT connected and making a call or receiving one. Having BT turned on (no connection) and placing or receiving a call works perfectly fine as well. What can I try to resolve this or better yet; does anyone else have these issues? Could this be a hardware failure? What I can try or have tried thus far for troubleshooting:
Tried:
1. Dirty flash from CM 11 to CM 12 --> nope
2. Clean wipe and install to CM 12--> nope
3. ( I read this somewhere else) Turned on 'only connect to 2G networks'. I seem to be able to get a call *sometimes*, but the call drops midway or is garbled with high pitched noises
4. Turned off Data Connection completely whilst BT is connected to make a call --> nope
Can try:
1. Revert to stock ROM to exclude issues with CM ROMS (this does mean going back to 4.4.4/4.4.2 sadly )
2. Try another Lollipop ROM as opposed to the one from Ivan_Meler (Clicky)
3. ????????
I did look at the forums here and everywhere else I could think off on the net/Google but I did not find anything really close to what I am seeing. Unless my Google-fu has failed me for which you have my sincerest apologies
Cheers!
Click to expand...
Click to collapse
I have the same problem sometimes. On a Bluetooth call, network signal drops and call is ended or a loud distortion and call is dropped. I had this on RR ROM cm12 and now on cyanogen mod x rom to. This is a cm12 bug as far as I know.
Its odd that this only occurs sometimes. Its not the modem that is causing it, it is a cm12 bug
JezzeB said:
I have the same problem sometimes. On a Bluetooth call, network signal drops and call is ended or a loud distortion and call is dropped. I had this on RR ROM cm12 and now on cyanogen mod x rom to. This is a cm12 bug as far as I know.
Its odd that this only occurs sometimes. Its not the modem that is causing it, it is a cm12 bug
Click to expand...
Click to collapse
I have the same problem. No matter if i connect to the car/headset bluetooth, I cannot make a call. Actually, the phone at the other end rings once and meanwhile my phone says "Cellular network not available". However, without BT I have no network error.
Still issues on handsfree loosing connection
silviuk said:
I have the same problem. No matter if i connect to the car/headset bluetooth, I cannot make a call. Actually, the phone at the other end rings once and meanwhile my phone says "Cellular network not available". However, without BT I have no network error.
Click to expand...
Click to collapse
I'm, also having this problem. I saw once a recommendation to replace radio or modem, can't remember which.
Anybody got any knowledge in this direction?
Possibly pointing in the direction of a flashable modem or radio???
Please help! I can't stand having to rely on stock or custom TW.
amunarjoh said:
I'm, also having this problem. I saw once a recommendation to replace radio or modem, can't remember which.
Anybody got any knowledge in this direction?
Possibly pointing in the direction of a flashable modem or radio???
Click to expand...
Click to collapse
I did flash the latest modem available for my region (Europe) - UFOA1, but same behavior. Something did improve when I switched from 5.0 to 5.1, though: I can, sometimes, successfully receive phone calls via bluetooth, from ringing until hanging up. But still not able to call from my phone.
Bluetooth car audio issues on CM11 and 12
I got the same issue with the dropped 3g when calling from car audio.
No connection
CM isn't reliable so I m back to touch wizz where it still works.
Tired of not getting newer android updates.
Waiting for the new nexus to arrive. Hopefully soon
No more Sammy!

Categories

Resources