If your GPS isn't working with your new ROM, then try this method. It has worked for me for every ROM I've used with a problem connecting to GPS. I've seen the problem posted in several ROM threads, and instead of posting it in each one and having it get lost in the hundreds of pages of posts, I figured I'd start a new one which might be searched for a little more easily.
- Open 'Settings' and go to 'Applications'. Choose 'Manage Applications'.
- Choose 'Running Apps'
- Find the 'Maps' app and open it. Click 'Force Stop' and choose 'Clear Data'.
- Go back to your app drawer and open 'Maps'. It will have you check off the disclaimers. Close it after you have done this.
- Open your 'Navigation' app and check off the disclaimers there. It should connect after that.
Like I said, this has worked for every ROM I've tried with a problem connecting to GPS. I don't know why it works, but it does.
tags: gps not working, gps won't connect, gps issue, broken GPS
Didn't solve my GPS issue...which is that it doesn't toggle on what so ever.
Each new nightly I flash, I have to push an old gps.vision.so in order to get my gps to toggle on and off again.
Thanks anyway.
edit: No app on the market will make my GPS work...That is the type of GPS problem that I and some others are having.
try install the gpxfix or gps status from the market.. work well for me..
Same here...this didnt help.
Also installing GPS status did not help either.
As discussed in the nightlies thread, Cyanogen presumeably updated a crucial library responsible, among other, for GPS functionality which requires the/a new radio.
This also could explain why some users while having identical devices to other users do have GPS while others dont. They simply did upgrade the radio already earlier while the ones which are stuck with a bon-working GPS didnt and are still on the original radio, an "old" one in regards to the prerequisites of the "new" library added to the build.
Makes sense?
schaggo said:
As discussed in the nightlies thread, Cyanogen presumeably updated a crucial library responsible, among other, for GPS functionality which requires the/a new radio.
This also could explain why some users while having identical devices to other users do have GPS while others dont. They simply did upgrade the radio already earlier while the ones which are stuck with a bon-working GPS didnt and are still on the original radio, an "old" one in regards to the prerequisites of the "new" library added to the build.
Makes sense?
Click to expand...
Click to collapse
Yep...this is 100% correct.
And for what its worth, I went a head and flashed the new radio again just too see if in fact it does fix the GPS and yes it does.
Back to the T-Mobile US OTA radio and the gps.vision.so from Nightly #4 or earlier.
not 100% correct, i have the new radio and still have the gps problem... i've seen at least one other person with the same.
But i'm using a Bell Desire Z, maybe thats why
evilive27 said:
not 100% correct, i have the new radio and still have the gps problem... i've seen at least one other person with the same.
But i'm using a Bell Desire Z, maybe thats why
Click to expand...
Click to collapse
Did you happen to use the app 'GPS Status' to check your gps after you upgraded? If not, what was the first gps application that you opened after you upgraded to CM7, if you can remember?
Scratch that....just reflashed the radio and nightly 13. Gps works a charm now! Thanks
Sent from my HTC Vision using XDA App
Im on the stock ROM and have a problem. I think the GPS on these phones are messed up big time. Here is my problem.
stock rom with ota update and ota update radio= no GPS AT ALL it will just stick there blinking tryin to get a fixed signal but it wont! Happens in alll my GPS app not just maps.
So I downgraded my radio to the pre-ota one and GPS gets a fix but takes a minute or so.. after that I can leave the app and come back and itll refix itself within 5 seconds (what it should be normally).. So even downgraded I still have slight issues with gps.. plus for some reason if I loose signal for more than 5 mins on this radio it wont ever get a signal unless I reboot.
Im going to try your method but dont think itll work since my problem is not Maps specific.
EDIT: this seems to have worked, even on my the ota radio. I just dont understand why Maps would break GPS for all apps. Funny things is when something like this usually happens I clear app data but didnt do it here because it was all my GPS apps.
I'm glad it has worked for a couple people anyway. I don't know what the problem is that causes this, but it has worked on the ROMs I've flashed, so I figured it might be a good step to take before updating radios and things like that. Just in case the solution is as simple as just stopping Maps and clearing the data... If you have done more modification to your phone beyond just flashing ROMs, then this may not work for you since the problem may be bad radios or other issues. If you are just a ROM flasher without tweaking too much else, then this may solve your problemo.
evilive27 said:
not 100% correct, i have the new radio and still have the gps problem... i've seen at least one other person with the same.
But i'm using a Bell Desire Z, maybe thats why
Click to expand...
Click to collapse
And I have the old radio, and never had a gps issue. Maybe not all the batches in the factory has the same chip, ic whatever?
Sent from my HTC Vision using Tapatalk
I used to not have GPS issues either - european Desire Z btw - having said that, CM7 #14 breaks with that uuhm... tradtion. It's the first build giving me no GPS unless a new-ish (the 26.04 and 26.06 works) radio is flashed.
So wat is the new radio, I recently flashed a different radio but I'm not sure if its the latest radio out. Thx
Sent from my HTC Vision using XDA App
New to this, can some on explain how to find an old radio and flash it? I am using CM9 build 78.. my GPS hasnt worked for any rom ive used since rooting..
dannynyc said:
New to this, can some on explain how to find an old radio and flash it? I am using CM9 build 78.. my GPS hasnt worked for any rom ive used since rooting..
Click to expand...
Click to collapse
Follow the instructions in this thread. Flash the updater and then the efs wipe tool through recovery.
http://forum.xda-developers.com/showthread.php?t=1632482
Related
Sometimes my internet will not connect unless I quick reboot and even then there is no guarantee it will and other times it connects fine. I don't think its a signal issue, it just seems to be quite tempremental. Is this a common issue or is just one of those things. I'm using a HD version of Froyo and wondered if there was an app or widget to force the internet on and off. Any help would be great. Thanks.
Sent from the future
I personally have found that with custom roms some arn't "made" properly and so things like this happen. Happened to me plenty of times. I guess you can update you radio to 5.14.05.17 if you haven't.
GoogleJelly said:
I personally have found that with custom roms some arn't "made" properly and so things like this happen. Happened to me plenty of times. I guess you can update you radio to 5.14.05.17 if you haven't.
Click to expand...
Click to collapse
Cool, I will check that out thanks.
Sent from the future
Similar issue with VillainROM 0.9
I have a similar issue after I used WiFi.
After reboot the Mobile Data Connection works properly. But if I activated WiFi in the meantime, it will not switch back to MobileData after stopping WiFi.
The only method to get Mobile Data working again is to reboot or switch to flight mode and back.
As well the Mobile Data's ToggleButton in the status bar and the option in the settings sometimes show the exact opposite.
Anyone to confirm this issue?
im would update the kernel and the radio, newest kernel should be no problem but im would not install the newest radio because a couple of people had some problems with the newest version.
Thanks to all for helpful replies, will have a bash with a different radio and rui.
Sent from the future
I'm kinda at the end of my rope trying to find a non-stock ROM that doesn't break GPS. I've tried several so far. I can't use any CM7 ROM or anything based off CM7, as GPS is useless. Recently I tried MIUI Bulletproof and loved it, but sure enough, GPS would lose signal during GPS Navigation. The only ROMs that consistently have fully functional GPS for me are the rooted Gingerbread official release and some variations like G-Lite.
There's nothing wrong with these ROMs, but I'd like to run something that has the insane speed and increased functionality that the awesome devs here and elsewhere create. It just get frustrating finding a cool new ROM, loving all the features, then finding that, as always, GPS constantly drops connection or fails to lock at all. I've done all the tricks like efs_wipe and even a proposed workaround bug fix in the General section, but no joy as of yet. So I'm back to vanilla 2.3.4. Nothing exciting, but GPS is flawless. Anyone have any tips of ROMs I may have not tried where I can get best of both worlds? Figured it won't hurt to ask.
Interesting. I'm running CM 7 and my GPS has been working fine. Assuming you did a full wipe between installs and all that recommended stuff?
Yup, I always do a Superwipe+ that does a good scrub as well as wipes the efs partitions. Plus I manually wipe the Dalvic cache. From what I've gathered, random G2 users just cannot avoid GPS problems running anything that isn't stock. CM7 and MIUI give me major GPS woes, whereas stock ROMs give me no issues whatsoever. I've been trying to get to the bottom of this since January and not much luck.
Are you sure u got no hardware problems with ur phone/gps?
My gps is working very good @cm7!
I got the same issue you said with me hd2... gps got lost, never found gps, phone freezes @navigation...
The end of the story was that my hd2 has to be repaired by HTC.
Sent from my HTC Vision using XDA Premium App
I feel like you're not going to get anywhere with this, since you've obviously tried ROMs that work fine for others. I had problems with GPS on CM7 before, but a efs wipe (and performing Superwipe+ thereafter) fixed any and all issues. The only thing I can think of is to try CM7 nightlies off of CWM (a few user reviews under each) instead of the release. I'm on nightly 204, and everything from GPS, to performance, to battery life is flawless. There's always the option of getting the G2 replaced and trying again.
Good luck!
hlx187 said:
Are you sure u got no hardware problems with ur phone/gps?
My gps is working very good @cm7!
I got the same issue you said with me hd2... gps got lost, never found gps, phone freezes @navigation...
The end of the story was that my hd2 has to be repaired by HTC.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Well, he did say he has flawless GPS on stock 2.3.4, so we can safely rule out actual issues with hardware.
EfemaN said:
I feel like you're not going to get anywhere with this, since you've obviously tried ROMs that work fine for others. I had problems with GPS on CM7 before, but a efs wipe (and performing Superwipe+ thereafter) fixed any and all issues. The only thing I can think of is to try CM7 nightlies off of CWM (a few user reviews under each) instead of the release. I'm on nightly 204, and everything from GPS, to performance, to battery life is flawless. There's always the option of getting the G2 replaced and trying again.
Good luck!
Well, he did say he has flawless GPS on stock 2.3.4, so we can safely rule out actual issues with hardware.
Click to expand...
Click to collapse
Exactly. Since GPS works perfectly with stock ROMs, I have to rule out hardware problems. If it was a problem across the board, I'd already have a replacement in hand. The only thing I have not tried yet is RIL matching. Can anyone link me to it? I know the dev who had it up on these boards left XDA and took all his stuff with him. Not sure what it involves or if it may potentially help, but maybe worth a shot. I've tried flashing a few different radios and am now on the "official" radio that came with latest OTA update.
killswitch11 said:
Exactly. Since GPS works perfectly with stock ROMs, I have to rule out hardware problems. If it was a problem across the board, I'd already have a replacement in hand. The only thing I have not tried yet is RIL matching. Can anyone link me to it? I know the dev who had it up on these boards left XDA and took all his stuff with him. Not sure what it involves or if it may potentially help, but maybe worth a shot. I've tried flashing a few different radios and am now on the "official" radio that came with latest OTA update.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1028405
Doing the efs wipe should fix gps problems
Post on ril matching http://forum.xda-developers.com/showthread.php?t=902752 another idea is the change the gps.config file to the US server
http://forum.xda-developers.com/showthread.php?t=732030
Also if using superwipe+ there is a new version with support for 4ext partitions
http://dl.dropbox.com/u/10752587/SuperWipeG2+ext4.zip
bombadier said:
http://forum.xda-developers.com/showthread.php?t=1028405
Doing the efs wipe should fix gps problems
Post on ril matching http://forum.xda-developers.com/showthread.php?t=902752 another idea is the change the gps.config file to the US server
http://forum.xda-developers.com/showthread.php?t=732030
Also if using superwipe+ there is a new version with support for 4ext partitions
http://dl.dropbox.com/u/10752587/SuperWipeG2+ext4.zip
Click to expand...
Click to collapse
Thanks for the links. I've tried efs wipe several times. Done it manually via terminal emulator and flashed the zip/superwipe+. I'll look into the RIL matching. The GPS config options appear to be specific to Verizon and the Samsung Captivate, so not sure if that one is an option for me. Thanks again for linking me to all this.
killswitch11 said:
The GPS config options appear to be specific to Verizon and the Samsung .
Click to expand...
Click to collapse
Changing the GPS server should work for any ROM,Im using unity and in the uk so not carrier specific just a matter of opening a file and changing the server values,
Luckily I've never had any serious problems with my GPS so I'm running out of ideas,there is also an app called GPS status is useful but if wiping the efs data is not helping then not sure if the app will help,best of luck finding a solution
You should check out the latest "unofficial" ILWT CM7 212b by tsubus. He includes an option to use stock HTC GPS drivers. I updated my radio to. 30, and flashed 212b (which includes the efs data wipe) and my GPS works flawlessly now. Highly recommend it. Link is in my signature.
All features are now part of/options in version 213, and all subsequent releases. Seriously, it's worth a shot...
Sent from my HTC Vision using XDA App
Hi,
My GPS stopped working.
After much research and several tests, changing radio\RIL, stock rom.... could not get the GPS working.
Some time ago, after a long time just picking up one satellite, now does not get any.
Is there any tool or application to test the hardware?
Thanks.
rom do you use?
I noticed this with CM7.1.
The stock rom I tested was the latest 2.3.5 OTA.
Try this: http://forum.xda-developers.com/showthread.php?p=17081413
Hi,
I tried this with the stock rom and did not work.
I tried with CM7.1 and still not show any satellite.
Sugestions?
Just for the record:
Radio - 27.14.04.28_M
Have the same issue
I like Cyanogen 7.1, but it seems that the gps doesn't work on DHD. Too bad, because it is a really good rom. I have radio 26.10.04.03_M. The same thing as described by others happen:
I turn on the gps, it start searching, and then it stops and the icon disappears even that the gps is still showed as being turned on
My case is different.
Worked for me several months without problems, and fast.
But stop working.
Someone?
I've tried modifying hardware (antenna), changing to stock rom, tried some different radios, editing gps.conf....
I do not know what else to do.
Anyone know some software to test the GPS hardware?
Have you tried changing the NTP servers?
Changing the NTP servers is part of the link spikey001 posted.
Have you tried flashing agps? I haven't got a thread to point you too but there is one in the DHD ROM section. There are about 6 different gps things you can flash, hopefully one of them will work.
jonhyxda said:
My case is different.
Worked for me several months without problems, and fast.
But stop working.
Click to expand...
Click to collapse
You mention that your GPS used to work. Have you recently dropped your phone? It's possible that the GPS antenna contacts might not actually be making contact anymore (either through trauma or just plain old age)? If none of the SW fixes get your GPS working then perhaps you might actually have to do a HW mod?
See this thread for a HW fix: http://forum.xda-developers.com/showthread.php?t=1318892
Don't worry, it's not as scary as it looks!
Hi,
sounds like what mine did.
Tried software and even made the fysical contact better for the gps-module itself.
No luck.
The solution for me was to buy a new gps-module on ebay for 5-10 us$.
Worked like a charm.
Good luck!!
Thanks for all the help.
RED_
I've tried the agps reset/download and no luck.
mrlooneytoon
The phone did not fall, just stopped working.
I've tried the HW fix but did not work, still no satellites.
tvetkalle
I can not find the gps-module on Ebay, can you help me?
same issue after upgrading to...
same thing happened to me after upgrading to ICS rom and since am not using it that much, just ignored it and wait for the devs to fix it...now waiting for the wifi fix of blackout ICS
Hello there,
As the registration video pointed out to me that i'm a noob i have noob question.
Im running Android Revolution HD 6.3.3 By mike1986
with these radio thingies.
12.65.60.29U_26.14.04.28_M
But my gps isn't getting a fix. What is wrong with my phone settings?
Hope to hear from you.
Greetings
Youri
Hello.. Maybe try flashing the AGPS patch from this thread.
Here's the direct link... flash that through recovery and see if it works
And if you are having crappy GPS accuracy once you lock, your best bet is just to find some way to get a solid connection from the GPS antenna to the motherboard.
Question is if you've had problems with gps fix since flashing Mike's rom or has it happened after a while.
Next question is what navi software do you use.
I tried two navi programs: Google's and beta version of Automapa (although beta is closed for now)
GPS always gets fix after couple of seconds. With Automapa it is also very accurate. Google is worse than Automapa but still quite good.
Both programs were running on ARHD 6.3.1
Anyway I'd try reflashing with full wipe again. Or maybe try newer (or older) version of ARHD?
Regards
Rafal
There are several possibilities:
1) environmental - try again outside, in plenty of open space. Try with & without your case, if you're using one.
2) config: download FasterFix from the market and choose your preferred server (there is a preconfigured list, but you can also type your own in: Spain is es.pool.ntp.org France is fr.ntp.pool.org etc) also check out GPS Test, also from the market, and you will see exactly how many satellites are in view etc.
3) hardware - bad connection. If you can't get a result from 1 or 2, well maybe there is a bad connection (the GPS antenna is around the flash). This is unlikely, I'd say.
A reboot may help to clear the cache - as suggested above, a superwipe is the way to clean before flashing a new ROM. You can also clear caches from Recovery.
First do some testing before install any patches.
Go out under clear sky and after activate gps sattelites from settings, download and run from market the Gps Test apk.
Write us the results here.How many satellites and after how much time did you get.
I`maar also noob without same issue. Same rom and same radio.
Before flashing, gps worked flawless, after flashing no more fix.
Even the quality of the signal for calling is nota wat it was.
Tried 3 navigation apps, open area,... nothing works.
I really Need the gps, so i`m thinking of unrooting if there isn't aan sollution.
Or could this be solved by flashing an stock rom ? Any tips or hints are welcome
Thanks in advance!
Personally i reccommend this http://forum.xda-developers.com/showthread.php?t=1318892
it seems a bit risky,but it shouldnt be a problem opening the flash case. Im not into soldering, and im afraid of burn motherboard,so i just pulled up the golden springs a bit,cleaned with alchool, an voilà! fix in < 10 seconds with < 20 meters precision.
hope it helps.
It seems to me that if gps worked stock, the hardware is ok
Yeah try the Rom in my signature its awsome :thumbup:
Sent from my HTC Desire HD A9191 using xda premium
I had problem with my GPS too. It's doesent a rom or radio problem. In other thread it's show how to hardware hack the GPS under flash cover of our dhd. I won't hardware hack so gently push down the flash cover. Go out and GPS status and gmaps fix in less then 10 sec.
Inviato dal mio Desire HD con Tapatalk 2
i'm noob with rooting phones, but not with pc's or other electric equipment.
If i say gps worked FLAWLESS on my stock DHD, how can my antenna suddenly be defected after flashing a rom?
I even went to open field with NOTHING in a 500m radius
it has to be something software....
i'll try to flash other rom like someone suggested...
already thanks for the replies!
check if GPS is broken?
Djteaser said:
...
Im running Android Revolution HD 6.3.3 By mike1986
with these radio thingies.
12.65.60.29U_26.14.04.28_M
But my gps isn't getting a fix. What is wrong with my phone settings?
...
Click to expand...
Click to collapse
I have the same problem! My GPS is running but it cannot find any sattelite!
Is ther any method to check the GPS if there is a hardware problem or a software problem?
Maybe there is a logging like "logcat" for GPS which i can check?
I'd recommend trying the app Faster Fix. You select your region, and it sets the correct GPS configuration data. If that's the issue, that app will solve it.
Also worth trying the app AGPS Inject, which downloads GPS assist data when opening gps apps like gmaps.
Also recently removed the letters "supl" from the APN type in the data access point settings. Resulted in a faster fix.
Sent from my HTC Desire HD using xda app-developers app
Thank you Swell6 for your tips, but nothing helped!
I think it's an hardwareproblem.
Does someone know where in the phone the GPS Module is sitting?
With the dhd there's a known hardware issue with the GPS antenna, which is part of the black plastic led cover. Over time it can lose contact with the main board, and sometimes just pressing it in can fix it. If it needs more, there's loads of posts on what can be done. Worth a try!
Sent from my HTC Desire HD using xda app-developers app
Since I've updated to Android 4.3 on my Galaxy Nexus (Maguro), I've noticed an issue with the WiFi. Sometimes, when entering the range of a known WiFi network, my device doesn't automatically connect, as if it doesn't know I'm in range or hasn't scanned for the WiFi networks nearby. This issue has been reported on the official Google Bugs tracker here. -->
https://code.google.com/p/android/issues/detail?id=58230
If you have this issue, please visit this link and star/report it so that Google will know. For now, I've found a few ways to resolve the problem, and wanted to share them.
Solution 1: When I go into Settings < Wi-Fi to view the WiFi networks, I notice that at first it shows the network I'm trying to connect to as "Not in range," but then it immediately connects to it.
Solution 2: I also found that turning WiFi off completely, and then back on again allows my device to see the network and connect.
Both solution 1 and 2 are manual fixes. While both are easy to do, they require you to actually take action to reconnect to your network. This can cause you to miss notifications, etc. if you aren't aware of what's going on. I didn't like that too much, so I made a simple Tasker profile to help.
Solution 3: This requires a little bit of knowledge about Tasker, but I'll try to explain it well enough that anyone can get the profile setup and working.
First we will create a Task called "Wifi fix." This task will have 2 simple actions.
Disconnect Wifi
Reconnect Wifi
Now we need to create a profile to trigger the task. I'll name it "Wifi Fix Profile."
This is going to have 3 context triggers that all have to be met before it will execute our Wifi fix task, all are state contexts.
First we will use Wifi State Connected, with the Invert Checkbox checked
Then, Variable value "%WIFI" matches "on". Both "%WIFI" and "on" are case sensitive, so be careful.
Lastly, Display State "ON". This one is optional. I added it because I don't want wifi constantly disconnecting/reconnecting while my phone is asleep if I'm not near a network. So instead, the profile can only trigger while I'm actually using the phone.
After that, all you need to do is go into Profile Settings (by long pressing the profile name) and set a cooldown. I use 5 minutes, you can use anything (or nothing) you want.
Basically, what this profile does is when your wifi is on but not connected to a network, then it forces a scan for wireless networks by disconnecting, then reconnecting wifi. Simple, and it works.
Theory:
Now that we have a workaround, back to the problem. Based on the solutions listed, namely solution number 1, I believe that the problem lies with how often/ when WiFi networks are scanned for. This could be due to the new WiFi Setting Google added in 4.3, "Scanning always available". It has been reported that disabling this does not fix the issue, but I haven't tried it myself. I also tried changing the wifi scan interval in build.prop, but that didn't seem to make a difference.
Hope this helps some of you!
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Sent from my Nexus 7 using xda app-developers app
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
geckocavemen said:
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Click to expand...
Click to collapse
Yes, I do have the issue on both custom and the stock factory image. I am also currently on Slim Bean Beta 1 (it's my favorite), but I also had the issue on Cataclysm.
NCguy said:
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
Click to expand...
Click to collapse
I would test this for you, but I don't have a bluetooth device to connect to. Sorry, maybe someone else can test this?
http://forum.xda-developers.com/showthread.php?t=2380403
Sendt fra min Nexus 7 med Tapatalk2
What I really wanto to know if this issue is posted in the official google bugs tracker
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
stevensoaj said:
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Expose your case here:
https://code.google.com/p/android/issues/list
Then come here and recruite some people to star your posted issue, the more stars the more atention Google puts on the issue. If you do it, add 1 star from me for sure.
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Big ZD said:
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
FlickFlack said:
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
Click to expand...
Click to collapse
I stand corrected. My apologies for not reading more thoroughly.
Sent from my Galaxy Nexus using xda app-developers app
FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
I promised to give feedback for testing the tasker profile. After 3 days I am sure that the tasker profile described in OP is working fine.
For me it is a good workaround. But I am still hoping that google will fix the problem, because for normal users this must be a real annoying bug.
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
memnoc said:
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
Click to expand...
Click to collapse
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
stevensoaj said:
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Scratch that. A little more testing and I'm back to the initial, disconnect then reconnect wifi net. What do you guys think?
stevensoaj said:
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
Click to expand...
Click to collapse
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
memnoc said:
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
Click to expand...
Click to collapse
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
stevensoaj said:
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
Click to expand...
Click to collapse
yes, you was, my friend; radio has everything to do with gsm/umts, wifi/bluetooth connections...it is exactly what a radio module does in the phone, to be precise, radio.img is that piece of software that virtually connect the radio chipset hardware with the basic software..the RIL (radio interface layer) instead, is what connect the software previously mentioned with the actual OS (the rom), but I read somewhere it is not so important in aosp roms, while it very important in other OS, propietary ones, like HTC (that has a specific RIL different from the asop one)...
You probably know it as "baseband", which is how google used to define it..in samsung environment is a.k.a as "modem" , whatever you call it, we are talking about the same thing, I keep calling it "radio" because of the old froyo times we learned to call this way, since changing the baseband it's just changing the radio.img..now, be very careful, flashing this kind of stuff may brick your device IF something goes wrong in the flashing process..however, I flashed tons of radios, and I've never experienced any hard brick..here on maguro we have the opportunity to fash it from recovery which is what I suggest you to do, so you'll avoid any issue whatsoever, and remeber, it may not be related to your problem but, as I stated before, radio module controls all the wireless signals, included network/provider frequencies, their range, and their geo-location, as well as bluetooth, and anything communicate wirelessly into your phone, it's worth to give it a shot in my opinion..here some extra info for you:
RIL info
http://www.netmite.com/android/mydroid/development/pdk/docs/telephony.html
radio module info
http://android.stackexchange.com/questions/70/what-is-radio-firmware
http://forum.xda-developers.com/showthread.php?t=1462360
http://forum.xda-developers.com/showthread.php?t=1930844