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.
Related
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.
I just recently updated to JB via Odin, restored apps with Titanium Backup, and didn't restore any system settings from TBU (thinking it might conflict with the new rom).
I used the hydbrid leaked Rom from one of the other threads in this forum
Everything has been great so far... better battery life, smoother, nice notification tweaks...except my Bluetooth.
Out of the 3 BT devices that previously 'worked', one of them doesn't work any more.
I am under the impression that 4.0.4 had some BT problems where it couldn't auto-connect to some 2.0 BT devices.
Not ideal, but now it's worse.
The non working device I have, is a Blackberry Music Gateway that I've been using for my 3.5mm Aux input into my car stereo.
Prior to JB on 4.0.4, I could pair easily, but had to manually connect each time.
Now, with JB i can pair the device, but it WON'T manually OR auto connect.
I've tried clearing the pairing in the phone, clearing the Blackberry Music Gateway, but no success.
I've looked for system processes/apps to clear data/cache, but nothing jumps out at me for clearing a BT (I only see 'Bluetooth share' and 'BluetoothTest' in my Application manager, which doesn't seem like they'd be involved)
Is there a process somewhere I could stop/start/clear that could clear BT data that might have been left over or is conflicting from my previous system rom? (reason I ask is that it seems to be variable as to what system settings stuck or cleared on many peeps JB upgrade)
Have other seen any problems with BT after the JB upgrade?
Anyone found any fixes?
(I've seen some other BT problem threads that deal with other devices over the past year or so, but nothing pertaining to JB and the GS3)
I have the same Blackberry Music Gateway. I also have the problem of it not autoconnecting (same thing happened on ICS) but it still works correctly when I manually connect.
You checked "Yes this is a question"
Guess where it goes?
Thread moved to Q&A
FNM
Lol
Sent from my SPH-L710 using xda premium
jeesh, who was the noob that posted the original question in the wrong thread? What a doofus.
(whoopsie, learning my way around...makes sense...*slaps own wrist)
edit: can't post links, too much noob.
go to google code, search for -- Issue 38563: Upgrade to 4.1.2 broke tethering --
My tethering appears to have gone to crap since 4.1.2
There are quite a few variables so I'm not sure where the problem is, on top of that the issue is not 100% consistent.
It appears that when I am not tethered I get a decent ping on my phone (150ms, 95%)
Shortly after initiating a tether my connection goes straight to hell (300-3000ms 50%)
My laptop is often even worse than my phone.
This is usually with a full 5 bars of 'H'.
I'm gathering the ping stats from my phone with terminal emulator.
I'm using a MacBook Air.
I will try to reproduce the issue with my nexus 7 when I have some spare time.
Anyone else experiencing something similiar?
luck02 said:
edit: can't post links, too much noob.
go to google code, search for -- Issue 38563: Upgrade to 4.1.2 broke tethering --
My tethering appears to have gone to crap since 4.1.2
There are quite a few variables so I'm not sure where the problem is, on top of that the issue is not 100% consistent.
It appears that when I am not tethered I get a decent ping on my phone (150ms, 95%)
Shortly after initiating a tether my connection goes straight to hell (300-3000ms 50%)
My laptop is often even worse than my phone.
This is usually with a full 5 bars of 'H'.
I'm gathering the ping stats from my phone with terminal emulator.
I'm using a MacBook Air.
I will try to reproduce the issue with my nexus 7 when I have some spare time.
Anyone else experiencing something similiar?
Click to expand...
Click to collapse
http://code.google.com/p/android/issues/detail?id=38563
I, like many others have had this problem since 4.1.2, rolled back to 4.1.1 and WiFi tethering worked again. Back to 4.1.2, stopped working again. Installed 4.2 on Gnex yesterday hoping for fix but still no good.
As 4.1.2 is "old hat" now I have started new issue at Google for 4.2 here
code.google.com/p/android/issues/detail?id=39618
Please anybody with same problem go there and add to report.
DO NOT turn it into a *****ing thread like so many here on xda.!!! The item to which luck02 referred for 4.1.2 at code.google.com is just full of twats ranting about their phone suppliers charges for data and crap like that.
code.google.com is to report faults and bugs and by everybody contributing pertinent information maybe Google will look for a fix. Trolling and whinging does nothing but obscure the facts...... please respect this. Just tell them model number, build and describe fault - thanks
Well there is definitely some ranting and twats involved but to my mind that's just part and parcel of being on the internet. Ignore and contribute as you can. Has anyone tried the CM build on the GNEX? Also, has anyone confirmed / denied whether third party wifi tether applications resolve the issue (requires root)?
Actually even more importantly, has anyone isolated where the breakage is actually occurring? I'm assuming it's something in the drivers / networking layer that is screwing up the routing between incoming data and the wifi layer...
I will probably downgrade if nothing else works.
So I got frustrated and rooted / installed clockwork recovery.
Moved to CM 10 and still have the same issue. I'm thinking it's actually a carrier issue for me at this point.
My carrier term expires in January and I'll probably go to a different carrier then.
Will follow up with more information as I have it, I may roll back to an older version of CM to confirm the problem is still occurring.
luck02 said:
So I got frustrated and rooted / installed clockwork recovery.
Moved to CM 10 and still have the same issue. I'm thinking it's actually a carrier issue for me at this point.
My carrier term expires in January and I'll probably go to a different carrier then.
Will follow up with more information as I have it, I may roll back to an older version of CM to confirm the problem is still occurring.
Click to expand...
Click to collapse
Definitely not carrier for me, proved by numerous attempts and firmware this weekend. Gnex running 4.1.1 everything works perfectly. Let phone do ota to 4.1.2, broke WiFi tethering and Bluetooth to vehicle completely. Reinstalled 4.1.1 thro Odin and re-partitioned at same time so completely clean install, WiFi tethering and Bluetooth worked perfectly. Continued on complete wipe track by then installing 4.1.2 thro Odin with re-partition (thus removing possibility that incremental upgrade to 4.1.2 was to blame) still no WiFi tethering or Bluetooth.
Did same for 4.2 using Odin still didn't work. Returned to 4.1.1 using Odin, everything worked.
Even made my own Odin package using radio from 4.1.1 (even tho supposedly same as 4.1.2) system and other files from 4.2 - same result, nothing worked.
To eliminate doubt used same sim card in two HTC phones running 4.0.4, both showed correct working and tethering and Bluetooth. Conclusion, not carrier/ supplier related, but surely random hardware/ firmware incompatibility on some examples of Gnex for unfortunate souls such as us
Tried two WiFi tethering apps with exact same result... shows tether as working, greyed out WiFi icon on tab and no go on laptop or desktop....I have spent hours on this to no avail
Have you tried any network diagnostics while not tethered?
I may be getting carrier and 4.1.2 issues. I was running some ping tests while not tethered yesterday. Full 5 bars of 'H+' running CM10 and I was getting horrible signal. More than 50% dropped packets and long ping times.
I'll roll back to an older CM sometime soon and see if there's a difference over the next couple of days.
Thank you,
stinky73 said:
Definitely not carrier for me, proved by numerous attempts and firmware this weekend. Gnex running 4.1.1 everything works perfectly. Let phone do ota to 4.1.2, broke WiFi tethering and Bluetooth to vehicle completely. Reinstalled 4.1.1 thro Odin and re-partitioned at same time so completely clean install, WiFi tethering and Bluetooth worked perfectly. Continued on complete wipe track by then installing 4.1.2 thro Odin with re-partition (thus removing possibility that incremental upgrade to 4.1.2 was to blame) still no WiFi tethering or Bluetooth.
Did same for 4.2 using Odin still didn't work. Returned to 4.1.1 using Odin, everything worked.
To eliminate doubt used same sim card in two HTC phones running 4.0.4, both showed correct working and tethering and Bluetooth. Conclusion, not carrier/ supplier related, but surely random hardware/ firmware incompatibility on some examples of Gnex for unfortunate souls such as us
Click to expand...
Click to collapse
I'm Noob, I got problem same error on 4.2 and 4.2.1, this issue over half a month.
I have google some website, found have several people like us have this issue and still no idea to fix it...
Mostly couldn't connect to laptop or Mac Book. For me is PlayStation Vita (firmware 2.0 Wifi only)
My PS Vita could deal with my galaxy Nexus on 4.1.2 , but 4.2 is could reach Internet correctly.
I have tried several Wi-Fi Device to connect my Galaxy Nexus,
My PC , My PS3, My PSP, My Uncle Galaxy Nexus 4.1.1 (Samsung image) are working fine.
Only my PS Vita couldn't...
But base on others, have same issue on other device, so I did think this issue may cause by 4.2.
Base on this issue, I have try "wifi-tether" , whatever this download on Google play! or "3.3 pre-2" on their website.
I have it running on Factory 4.2 , 4.2.1 Rooted + Super user, this couldn't work correctly.
Running on KALO 2.0 ROM, this have error on "Clamping MMS"....
No Luck for me.
My GNexus is only one device at the moment, which could let my PS Vita online... I have some PS Vita game need running online.
This force me stay on 4.1.2 and try disable System update notification next minute, for several weeks or month until the solution come...
Or... Anyone could build a patch which could let 4.2 using 4.1.2 Wi-Fi tethering engine?
Hello! I know this is a common thread, but i'm desperate!
My GPS is not locking at all, i left the phone for 10 to 20 minutes and i got nothing...
I'm using the CM10.1 MoDaCo ROM, but i tried so many ROMS, fixed configuration files, walkthroughs, etc, but none of them seem to work.
I'll list all the methods that i try so far.
1) Flash a fixed configuration file
2) Change the ROM: i tried with the stock 4.2.2, CM10, CM10.1 Nightlies, CM10.1 Experimental, MoDaCo CM10.1
3) Flash different radios. I live in Chile, so i tried UGLL1 and UGKL1
4) Clear data of Google Services Framework, restart, etc
5) Used FasterGPS to set my location in the right area
6) Used GPS Status to improve AGPS
7) Change the build.prop file
I tried every method and the combination of them, but nothing has worked for me so far....
The GPS is very important for me because i use it to track my rides with Strava, and since the GPS is not working, i cannot start the application...
I really need help...
I use a Galaxy Nexus Maguro without Wallet and live in Chile. I cannot tell exactly when the GPS started to fail, but at least in the stock 4.1.2 it was working perfect, so i guess it started failing when i updated to CM10 and then to CM10.1.....
Ok try this if you haven't.
In settings turn off all location. Reboot
Make sure location reporting is still off.
Clear data on Maps force stop maps
Reboot
Clear data on maps and force stop again
Enable location
Get gps lock with maps or easy gps.
Might not work but I have had your same problem and this fixed it .... good luck
G-Nexus Sent
Hi!
Thanks for your answer, but unfortunately i've already tried this method with no succeed. I tried again but it didn't work...
Thanks anyway, i'm going to try to roll back to stock 4.1 (because the GPS was working with that version)
and if it really works i'm going to upgrade to 4.2 to see if i can find the error...
If someone else can give me a solution i'll appreciate it!
Sent from my Galaxy Nexus using Tapatalk 2
duqueso said:
Hi!
Thanks for your answer, but unfortunately i've already tried this method with no succeed. I tried again but it didn't work...
Thanks anyway, i'm going to try to roll back to stock 4.1 (because the GPS was working with that version)
and if it really works i'm going to upgrade to 4.2 to see if i can find the error...
If someone else can give me a solution i'll appreciate it!
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Flash stock, just to make sure it isn't hardware related.
pr0xyw0rm said:
Flash stock, just to make sure it isn't hardware related.
Click to expand...
Click to collapse
I already tried, but with Android 4.2.2 and it didn't work.
Before i flashed the 4.2.2 i was using stock 4.1 without problems, so i believe, and hope, that this is a software issue in the 4.2.2 update...
I'm going to try it now and i let you know.
Sent from my Galaxy Nexus using Tapatalk 2
My GPS got worse after upgrading to 4.2.2. Lock takes much longer and finds less satellites
- wore out your welcome
More info
Well, i returned to Stock Android 4.1.2 using Fastboot, but the GPS didn't work either... So i updated via OTA to 4.2.2 and the GPS didn't worked again...
But i noticed that the Nexus S belonging to my sister, wich uses CyanogenMod 10, is not working either!
So i have a doubt now: Is it possible that CyanogenMod could have ruined our GPSs? If i erased everything via fastboot, is it possible that some remains of CyanogenMod could still be breaking my GPS? Or are our GPSs, strangely, broken at the same time?!
Please Help!!!
GPS
duqueso said:
Well, i returned to Stock Android 4.1.2 using Fastboot, but the GPS didn't work either... So i updated via OTA to 4.2.2 and the GPS didn't worked again...
But i noticed that the Nexus S belonging to my sister, wich uses CyanogenMod 10, is not working either!
So i have a doubt now: Is it possible that CyanogenMod could have ruined our GPSs? If i erased everything via fastboot, is it possible that some remains of CyanogenMod could still be breaking my GPS? Or are our GPSs, strangely, broken at the same time?!
Please Help!!!
Click to expand...
Click to collapse
Did you try changing the file referenced in this discussion? It worked fine for me.
http://forum.xda-developers.com/showthread.php?t=1722983&page=2
If you've flashed the Google factory image, you have an active sim card with data connection, and gps does not work, then you have a hardware problem.
klobkelosh said:
If you've flashed the Google factory image, you have an active sim card with data connection, and gps does not work, then you have a hardware problem.
Click to expand...
Click to collapse
And is there a way to fix it?
duqueso said:
And is there a way to fix it?
Click to expand...
Click to collapse
Out of my realm of expertise, but I imagine the sirf chipset is not user serviceable. Your best bet would be Samsung factory service. I'm sorry.
Well, after giving up on trying to solve my GPS problem, it fixed itself.... i know that sounds weird, but the only thing that i did was update the CM10.1 to the latest RC2 and the problem was fixed, at least partially. Now it can find some satellites and it takes like 100 seconds.
The Gnex GPS isn't the best one, so it behaves a little weird some times, but at least is fixed now...
I really don't know what could be the problem, because i tried with almost any Rom, officials and no-officials...
Finally, the CM10.1 RC2 fixed my problem, hope this could help someone else.
Enable wifi & mobile network location in settings
Should be some code in 4.2.2 that prevents you from getting AGPS data if you disable the said option.
Enable wifi & mobile network location in settings
Should be some code in 4.2.2 that prevents you from getting AGPS data if you disable the said option.
Click to expand...
Click to collapse
The problem is fixed now, but i tried everything, from rolling back to 4.1 official to 4.2.2 official, CM9, CM10, CM10.1, AOKP, etc. So i really don't know what could be the problem. I also tried the solution that you told me, but that didn't work either.
Right now, with CM10.1 RC2 my GPS is working great and i'm able to use Strava again.
I've been having the same issue. I'm running a Stock Verizon Galaxy Nexus, on my third one now. I have tried everything from apps, to resets, to disconnecting the gps, and nothing seems to work. It just seems to take forever to get a GPS lock, sometimes I just have to reset it. Not sure the issue, and I can't seem to find anyone with answers either. IDK if anyone found anything??
wpeen001 said:
I've been having the same issue. I'm running a Stock Verizon Galaxy Nexus, on my third one now. I have tried everything from apps, to resets, to disconnecting the gps, and nothing seems to work. It just seems to take forever to get a GPS lock, sometimes I just have to reset it. Not sure the issue, and I can't seem to find anyone with answers either. IDK if anyone found anything??
Click to expand...
Click to collapse
Cold start gps can take up to 20 minutes outdoors with a clear view of the sky if you don't have current agps data. Thereafter, you should have quick starts for a day or two.
Is your data working properly? Do you have sync settings turned off?
klobkelosh said:
Cold start gps can take up to 20 minutes outdoors with a clear view of the sky if you don't have current agps data. Thereafter, you should have quick starts for a day or two.
Is your data working properly? Do you have sync settings turned off?
Click to expand...
Click to collapse
My data is working just fine, I actually have great 4g where I'm at, and all my sync is turned on. I've never had GPS problems with any of my other phones. I had an EVO 3D, and it worked great, cold starts would take seconds to find GPS.
wpeen001 said:
My data is working just fine, I actually have great 4g where I'm at, and all my sync is turned on. I've never had GPS problems with any of my other phones. I had an EVO 3D, and it worked great, cold starts would take seconds to find GPS.
Click to expand...
Click to collapse
And you have certified that all the gps settings/permissions are turned on? Even in the Google settings app?
Since you are stock, it might be helpful for diagnosis to preform a factory reset.
Edit - I see on another thread that you have already performed a factory reset. Next step would be to flash the factory image and see if that helps.
klobkelosh said:
And you have certified that all the gps settings/permissions are turned on? Even in the Google settings app?
Since you are stock, it might be helpful for diagnosis to preform a factory reset.
Edit - I see on another thread that you have already performed a factory reset. Next step would be to flash the factory image and see if that helps.
Click to expand...
Click to collapse
Thanks, I'll have to look up and see how to do that without root and boot loader unlocked, this is my third Galaxy Nexus from Verizon, they keep replacing it and I keep having the same issue
And yes all setting have been turned on, kind of driving me nuts
I'm sorry for you. it must be very frustrating.
As far as flashing an official factory image, I think you can do it unlocked if you have adb set up. Or use a toolkit, unlock, flash factory, relock (or not, why not keep it unlocked?)
Hello, im on cm 12.1 and recently i have no call audio, calling works fine on facebook and the like, but not when im calling someone from my contacts , ive tried factory reset, flashing different rom , back to stock and nothing works ,can someone help me???
dpwguenther said:
Hello, im on cm 12.1 and recently i have no call audio, calling works fine on facebook and the like, but not when im calling someone from my contacts , ive tried factory reset, flashing different rom , back to stock and nothing works ,can someone help me???
Click to expand...
Click to collapse
Need more info....download samsung phone info and post a screenshot of the firmware tab. If your bootlader and baseband dont match, theres your problem. If they do, try reflashing stock (twice) then doing a tactory reset from the stock recovery right after. If after that the issue is still present....probably something else.....mabey hardware related. Good luckl
Do you use bluetooth? I had a very similar problem and figured out that the only time I had call audio was when I was using a bluetooth headset or the bluetooth in my car. I don't know what sets it off but I've done some searching on this problem and it appears to be common among GSM GS4 owners, and even doing stuff like a complete reset doesn't fix it.
The one fix that I did find, that helped some people, was to go into Google Now and disable "Okay Google" detection from any screen. Several people found that that worked. But I didn't have that feature enabled anyway so it didn't apply.
I don't know if the same problem occurs with CDMA GS4s; my wife has a Sprint GS4 and doesn't have the problem but that doesn't mean it doesn't exist. I think it was just AT&T and T-Mobile GS4 owners who reported this.
lordodin912 said:
Need more info....download samsung phone info and post a screenshot of the firmware tab. If your bootlader and baseband dont match, theres your problem. If they do, try reflashing stock (twice) then doing a tactory reset from the stock recovery right after. If after that the issue is still present....probably something else.....mabey hardware related. Good luckl
Click to expand...
Click to collapse
My bootloader is nb4 and baseband is foh3, but it's been that way for a while now, and this problem is only recently, also I've tried that and it didn't work
Sent from my SGH-M919 using XDA Free mobile app
Mama Luigi said:
Do you use bluetooth? I had a very similar problem and figured out that the only time I had call audio was when I was using a bluetooth headset or the bluetooth in my car. I don't know what sets it off but I've done some searching on this problem and it appears to be common among GSM GS4 owners, and even doing stuff like a complete reset doesn't fix it.
The one fix that I did find, that helped some people, was to go into Google Now and disable "Okay Google" detection from any screen. Several people found that that worked. But I didn't have that feature enabled anyway so it didn't apply.
I don't know if the same problem occurs with CDMA GS4s; my wife has a Sprint GS4 and doesn't have the problem but that doesn't mean it doesn't exist. I think it was just AT&T and T-Mobile GS4 owners who reported this.
Click to expand...
Click to collapse
I don't have Bluetooth, I've tried it with a wired headset and even that didn't work, but what's so puzzling about this is that my calling works fine with Facebook messenger calling feature, hangouts and things like that
Sent from my SGH-M919 using XDA Free mobile app
Edit:
Nevermind. It worked twice then I tried calling a different phone and it broke again. I will keep searching and update.
Original:
I have had this issue intermittently for the past year. It was fixed for about 6 months then two weeks ago started occurring again. Today I flashed a new Rom (PacMan) and the M919UVUFOK3_M919TMBFOK3_TMB firmware. That did not fix it. I was connecting to a 5Ghz WiFi so on a whim I forgot that network and made a call without WiFi enabled. Call worked!
So I connected to my 2.4Ghz WiFi and it is working again. I would try turning off WiFi and see if your calls go through if so it could be 5Ghz or the router...maybe a forget network / reconnect to network will fix it consistently.
Hope this helps you and if anything new comes up I will let you know.
So an update. I finally just gave up on it. My wife had an old phone I remembered (from 2 - 3 years ago) that was ran over and the digitizer broke. I just took her guts and put it in my phone and now it magically works. Hopefully it stays that way.
Should have done this years ago as my phone would no longer charge with the USB Cable nor was my SD Card accessible. Now it is all functioning right again.
dpwguenther said:
My bootloader is nb4 and baseband is foh3, but it's been that way for a while now, and this problem is only recently, also I've tried that and it didn't work
Sent from my SGH-M919 using XDA Free mobile app
Click to expand...
Click to collapse
So after flashing stock NB4 twice.....and factory resetting after from stock recovery, your still not getting call audio?.....doesnt make sense....try again and make sure the bootloader and baseband match.....and dont reboot into download from the OS.
For anyone having issues with no call audio through cell service but for some reason it works through data calls through whats app or facebook messenger, etc ,i have been having the same problem for awhile now. I believe i have traced it to be a hardware issue with the middle frame, when looking at the phone with the battery cover open on the top right over by where there are two markings R1 and L1. There is a module there labeled J-AT TMGA 7-3. When i was having issues i noticed that if i put slight pressure on that module my audio would fade back in on the call but if i put too much pressure it goes away again. If it is a hardware connectivity issue it would explain why slunked was able to get his phone working again by changing the guts in the unit. Im currently waiting for a middle frame and a blue cable for the antenna to confirm if this is indeed the issue.