I am currently using CM 10 custom rom and I cant get my bluetooths to work where i can hear someone talking to me using it.
This is my 3rd set of different BT headsets and I now believe that its this phone rather than the BTs itself.
Does anyone have any suggestions other than remove the BT and re-pair it because i have done this a hundred times so far and it not done anything?
if CM 10 is not a good rom to use with this phone can someone point me in the right direction to find the best rom for this phone?
Thanks:
i don't know if you've been reading about all the major issues CM10 is current facing since we finely managed to get data fixed.. some peoples bluetooth might still be broken or bugged (i havent checked all week because ive been busy with the Q&A section)... if you want a stable rom you'll have to go through the roms and see what bugs they still have if any.. i'm pretty sure only a few rom's are "stable" without alot of issues
^ What he said.
Try installing the bluetooth fix on top of Sport's latest unofficial CM10 (currently 1-11-2013).
Sport's CM10:
http://goo.im/devs/Sportsstar89/Ruby/CM10
Bluetooth fix:
http://forum.xda-developers.com/showpost.php?p=36453480&postcount=3005
Be sure to do a full wipe (data, dalvik, cache) using 4ext recovery and have SmartFlash enabled when flashing CM10. You might know this already but just covering the bases... so:
1. Full wipe
2. Flash CM10 from zip
3. Flash BT Fix
4. Try using bluetooth
5. Post results in CM10 bugs thread
I don't know why you suspect the bluetooth not working is a hardware problem but if you want to be certain the best thing to do would be to do a full wipe, flash stock RUU and try to use your bluetooth headset. Once you could confirm that bluetooth radio is functioning you would then move forward with testing it on CM10.
Cm 10 Bluetooth Issue
rbross3030 said:
^ What he said.
Try installing the bluetooth fix on top of Sport's latest unofficial CM10 (currently 1-11-2013).
Sport's CM10:
http://goo.im/devs/Sportsstar89/Ruby/CM10
Bluetooth fix:
http://forum.xda-developers.com/showpost.php?p=36453480&postcount=3005
Be sure to do a full wipe (data, dalvik, cache) using 4ext recovery and have SmartFlash enabled when flashing CM10. You might know this already but just covering the bases... so:
1. Full wipe
2. Flash CM10 from zip
3. Flash BT Fix
4. Try using bluetooth
5. Post results in CM10 bugs thread
I don't know why you suspect the bluetooth not working is a hardware problem but if you want to be certain the best thing to do would be to do a full wipe, flash stock RUU and try to use your bluetooth headset. Once you could confirm that bluetooth radio is functioning you would then move forward with testing it on CM10.
Click to expand...
Click to collapse
Hi Thanks for replying so quickly.
If you look at the screenshot that i have attached.
Im running the latest CM 10 verision
Cant i just flash the BT fix or do i really have to redo the whole rom install all over again?
Thanks
Related
Everyone,
I have been running the latest CM10 nightlies for a couple days and love it on my EVO. However, I am having consistent issues with the navigation. I am S-OFF running the latest firmware. I have been flashing the latest CM10 nightly, although I have also tried deck's latest version as well. When flashing, I wipe everything in sight, trying both the superwipe zip and manual wiping, but everytime I install CM10 the Google navigation crashes on me and has weird screen artifacts. I have also tried using the GPS Status app to clear my GPS data to no avail. Does anyone have any other tricks to get nav to work on CM10?
Thanks!
Brian
Well, all I can say is to make sure you have a half decent kernel, and make sure you're using the right gapps. No reason it should crash on you.
actually im in the same boat. had to use waze (not bad at all), just wish it works.
Misterblc said:
Everyone,
I have been running the latest CM10 nightlies for a couple days and love it on my EVO. However, I am having consistent issues with the navigation. I am S-OFF running the latest firmware. I have been flashing the latest CM10 nightly, although I have also tried deck's latest version as well. When flashing, I wipe everything in sight, trying both the superwipe zip and manual wiping, but everytime I install CM10 the Google navigation crashes on me and has weird screen artifacts. I have also tried using the GPS Status app to clear my GPS data to no avail. Does anyone have any other tricks to get nav to work on CM10?
Thanks!
Brian
Click to expand...
Click to collapse
I have the same issue. Eventually I was going to get around to trying a different kernel.
I am running the Kernel from the CM10 build:
3.0.53-dc2c1ebb
[email protected] #1
Mon Dec 3 21:32:25 PST 2012
As for the GAPPS I just installed the latest I could find with the ROM and then downloaded the latest Maps from the market.
Any recommendations on a good kernel to try?
This is a widespread issue for unrooted, stock users. It is documented in several forums, so it does not only affect you or other rooted users.
I am running CM10 12/05 build from IRC and used my Navigation with G maps for 2 straight hours today with no problems.
I am on the kernel it comes with. Before flashing CM10 I update prl, profile and make sure I have a GPS lock on a Sense rom. Then go into TWRP and wipe cache, dalvick, factory reset, and system a couple times each, flash CM10, I'm using the Captain's Gapps from IRC and it works fine for me.
I've never wiped the GPS data stuff or anything like that either.
YMMV though I guess
Naters
Naters,
I haven't tried using the IRC build...do you have a link / instructions on how to get that (and the GAPPS). I will try loading up MeanROM, getting a sense lock, and then switching to that build.
Thanks!
Brian
NaterTots said:
I am running CM10 12/05 build from IRC and used my Navigation with G maps for 2 straight hours today with no problems.
I am on the kernel it comes with. Before flashing CM10 I update prl, profile and make sure I have a GPS lock on a Sense rom. Then go into TWRP and wipe cache, dalvick, factory reset, and system a couple times each, flash CM10, I'm using the Captain's Gapps from IRC and it works fine for me.
I've never wiped the GPS data stuff or anything like that either.
YMMV though I guess
Naters
Click to expand...
Click to collapse
This is the link to get into the IRC channels.
Once you are in the DL link for the rom and Gapps will be at the top of the page.
http://forum.xda-developers.com/showthread.php?t=1643396
Let me know how it works for you.
Naters
Tried it, some problem unfortunately...I guess this is a YMMV type thing.
BTW, is that IRC channel a good place to get support for CM10? I was hoping to talk with the developers and try to help out with kernel logs or whatever may be useful.
Brian
NaterTots said:
This is the link to get into the IRC channels.
Once you are in the DL link for the rom and Gapps will be at the top of the page.
http://forum.xda-developers.com/showthread.php?t=1643396
Let me know how it works for you.
Naters
Click to expand...
Click to collapse
Sorry it didn't work.
No clue why it works for some and not others.
Sent from my PC36100 using xda app-developers app
Working now
I was having a lot of problems with the navigation until looked in the location access menu and selected the GPS source as "Use Internal GPS." It has been running smooth since then. :fingers-crossed: Hopes this helps.
I've started getting a situation when I install a MIUI based ROM in my I9300T, and any call to or from a mobile has extremely distorted audio (sounds like an amplifier trying to run at 150%) in both directions.
The audio is fine to landlines, so it sounds like it might be CODEC based.
I've done factory resets, Dalvik, Cache, reflash, new modem, reduced volume, and everything else I can think of. Flashing back to a non-MIUI resolves the problem, and re-flashing MIUI brings it back every time.
I've found a couple of threads asking about this problem, but nobody has every given a suggested solution (other than reset, reflash, modem).
Has anyone here experienced this or found a solutions?
Cheers,
Jason
AW: [Q] Badly clipped voice audio running MIUI based roms
Had exactlythe same problem, tried different MIUI versions, different modems etc. Call audio on ALL Samsung based MIUI was terrible, it worked only well on MIUI polimorph (which is AOSP/CM based). But on this MIUI I had issues with Bluetooth...
I read somewhere that this problem may occur when you come from stock Samsung Jellybean ROM and then flash a Jeallybean MIUI. So I tried following:
1. Download a ICS Stock Samsung ROM (for example 4.0.4) - important: complete ROM with PDA, Modem & CSC)
2. Flash ICS ROM with ODIN -- warning: all your data on internal SD will be erased!
3. Boot into your ICS Stock Samsung ROM (just to check call audio, should be fine...)
4. Flash CWM
5. Restart phone into CWM and flash your MIUI
6. Wipe data/factory reset
7. Restart & boot your MIUI. In case you got stuck while booting into MIUI do another full wipe data/cache in CWM. Then booting into MIUI should work fine.
!!! Attention: ALL YOUR DATA ON INTERNAL SD ARE ERASED WITH THIS METHOD !!! Be sure to copy your data, backups etc. to external SD or to your PC/laptop !!!
This was the solution I found after 1,5 weeks trying and reading and trying etc... Hope this works for you also!
Btw: be very careful doing this - there is always a risk of bricking your phone! Read carefully all about flashing with ODIN! Good luck...
Brilliant, thanks for the lengthy response!
The main thing I was wanting was an acknowledgement that someone had experienced and been able to overcome the problem, and you've included a description of exactly how you did it too.
Thank you very much for the help, and I'll post back in here if this works for me too in case others have the same problem.
I'd love to know which part of this process actually resolves the issue. I wonder what aspect of the JB ROM is not erased or overwritten by the MIUI installer.
AW: [Q] Badly clipped voice audio running MIUI based roms
You're welcome mate!
I'm also wondering WHY this helped, but it did... I only read somewhere in the forums that all the Bluetooth and WiFi issues on CM 10.1 only happen when flashing from a JB Samsung ROM, and everything is ok when coming from an ICS ROM. So I thought it is worth the try...
And I'm really happy now that I can use my beloved MIUI (Sammy-based MIUI-India) on my SGS3
Wow, what a grind this was to implement.
OK, so I...
1. Odin installed 4.0.4 and reset
2. Flashed MIUI m0, same problem
3. Odin installed 4.0.4 again, reset
4. Made a call, no audio at all
5. Factory reset again
6. Made a call, receive audio only, no send
7. Factory reset again
8. Reflashed MIUI m0
9. Made a call, no audio
10. Flashed modem DUELL2
11. Audio works!
12. FlashedMIUI India
Finally, MIUI and working audio!
You'd think from this list that flashing the new modem would have fixed the original issue, but I'd already tried this several times with no luck.
I'm guessing there is something in the 4.0.4 roms that is set in the flash related to a hardware codec. It may be that in JB the values are modified, and once it's been changed MIUI doesn't have any means of resetting it, during installation or subsequent booting.
Now I've wasted many hours on this, but at least I can go home happy
AW: [Q] Badly clipped voice audio running MIUI based roms
Really much work, but finally you got it working! Congrats!
Yes, I know, only flashing different modems without flashing ICS before won't help with this weird MIUI audio issue... Can't remember all the modems I tried, but tried many...
Hello everyone! I have a strange issue with my Bluetooth when running the cm10.1 official nightly roms. On the initial flash when booting up Bluetooth turns on and comes up as it should. However, if after flashing i leave Bluetooth turned on and reboot the phone, Bluetooth is then permanently disabled. The only way to fix it is to reflash the rom. Is anyone else having this issue or am i the only one?
Thanks,
m0t0
Ditto. Reporting in 4.2.2 (RC1)
XT912, same symptoms.
Bluetooth not working in CM 10.1
m0t0 said:
Hello everyone! I have a strange issue with my Bluetooth when running the cm10.1 official nightly roms. On the initial flash when booting up Bluetooth turns on and comes up as it should. However, if after flashing i leave Bluetooth turned on and reboot the phone, Bluetooth is then permanently disabled. The only way to fix it is to reflash the rom. Is anyone else having this issue or am i the only one?
Thanks,
m0t0
Click to expand...
Click to collapse
I have a similar problem. I can't get the Bluetooth to turn on. I select "on" and it just goes back to off. I really don't want to have to reflash it.
jmaclean62 said:
I have a similar problem. I can't get the Bluetooth to turn on. I select "on" and it just goes back to off. I really don't want to have to reflash it.
Click to expand...
Click to collapse
wipe cache and davlik worked for me
Only wiping the davlik cache worked for me. Not sure why, or how often I will have to do this.
copart said:
Only wiping the davlik cache worked for me. Not sure why, or how often I will have to do this.
Click to expand...
Click to collapse
Same for me. Actually had this issue on 2 different ROMs (CM & PA) running JB 4.2. Wiping only the dalvik cache restored bluetooth functionality.
I'm sure people were getting pretty tired of hearing about the radio issues when people flashed cyanogenmod (ie, LTE worked, but no SMS, MMS, or voice calls, odin didn't fix, the only solution was to factory restore from WITHIN a TW ROM). After waiting a while for things to calm down, I'm ready to try to install Cyanogenmod again but I am naturally hesitant.
Has this issued resolved itself? I'm running rooted and unlocked MC3 with CWM installed. I heard somewhere that flashing the MJ9 radio BEFORE Cyanogenmod 10.2 / 11 fixed the problem?
I would really appreciate any input or personal experience here!
As far as I know, the issue has not resolved itself. I tried flashing the newest CM 11 a couple of days ago (I think it was the nightly build on the 22nd), and I still had the funky radio issues. However, I tried this, and it fixed all the radio issues with CM 11 (and any other Android 4.4 ROMS - I'm running Slim ROM at the moment)... Here is my post from another thread.
Hey all, I got it working (the data/network connection that is), with a little effort. Here is what I did in sequence...
1) Reflash the ORIGINAL VRALJB image via ODIN. I used the one found here. You want to make sure you get the one that replaces EVERYTHING, i.e., NOT the alternative restore.
2) I set up my phone and used it normally for about four hours. (This may or may not be necessary, I'm not entirely sure. I also rebooted the phone about five times during that time frame.)
3) I unlocked and rooted the phone via the method outlined here. After that was done, I installed CWM 6.0.4.3 via TWRP (which the unlocking process installs).
4) I then installed CM 11 and the respective Google apps. (I first did a backup, then a factory reset, then cache wipe, then dalvik wipe. The next thing I did was install CM 11, then Gapps.)
5) Restart the phone and success!
Click to expand...
Click to collapse
The reason why I found out that this method would work, is that I tried installing CM 11 on my dad's phone. He has had a TW ROM (Beans build to be exact) since the phone came out. And he has been running the stock VRALJB radio. With that said, I figured I would try flashing the stock ODIN files to restore my phone back to the VRALJB. (I think I was running the MJ9 prior to this) That worked, and the SlimROM has been working perfectly ever since!
[Also, if you wanted to check out SlimROM, you can find a link to it here.]
Still looking for some more feedback from users! Anyone successfully flashed CM 10.2 / CM 11 from MC3 without problems / fixed the problems?
I was using slimkat 4.4.2 and restored the official samsung rom 4.3 to try a mhl cable. The result as you may know is that I couldn't install any custom rom that wasn't based on samsung's after that.
Searching here in the forums I found some people saying that it was because of a layout change on partitions, others because of knox, or the update in bootloader...
I installed the twrp-2.7.1.0 recovery and tried to install omni rom with pa_gapps, cm11 etc and I always get an error for gapps (couldn't find build.prop or something...). Tried Omega v58 (based on sam) and it worked, then I tried slimkat 4.4.3 weekly and slim_AIO_gapps (advanced wipe, everything but extsd, format data) and it installed everything fine.
It's almost perfect but now I have only a small problem... when I plug the headset the audio is really bad and sometimes I can't hear anything ... I tried another kernel with the same result. Tried slimkat 4.4.2 stable, same.
Does it make any sense to anyone here? any sugestions on how to fix? flash something somewhere maybe :x
and what is the real problem after the 4.3 official update? if slimkat is working maybe we can make other roms work too.
Thank you in advance
Do a full wipe, all your previous issues were due to files left over from other firmware.
On the headset, go back to stock firmware after a full wipe. If still the same then it is hardware.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Do a full wipe, all your previous issues were due to files left over from other firmware.
Click to expand...
Click to collapse
I still can't install most roms even with full wipe (gapps error) after the 4.3 official update but I'm happy with slimkat. I think maybe it works because it just copies the gapps files to android without doing other checks, maybe editing the scripts we can "force" the install of other roms too. If anyone have any info, please tell me.
boomboomer said:
On the headset, go back to stock firmware after a full wipe. If still the same then it is hardware.
Click to expand...
Click to collapse
Oh, I think it was just a series of bad coincidences. Tried the stock firmware and the headset did not work. Seems like my headset broke the same day all that stuff happened, and I tried the one I use on PC but it didn't connect firmly on s3 so the sound was bad too... just tried a new phone headset and it's working fine.. thank you