So I rooted over the weekend and tried several roms but noticed a problem that drives me nuts. After the downgrade my weather works with the clock\weather widget but after rooting the weather cant find my location. It doesnt seem to matter what rom I load the weather widget does not work. I tired beatiful widgets and it only works if I manually enter my location none will automatically detect my location. I did multiple wipes of data and delvic with no help. I even ran the sprint 2.2 ruu and it didn't work. The only way to get it back was run the ruu and then downgrade back to 2.1 and it works then 2.2 ota upgrade and it works but not when I root. I searched and tried all the ideas to no avail. Is anyone else having this problem? By the way the 2 roms I was wanting to use were CM6 and Fresh just want it to automatically find my location for weather.
So am I to assume that nobody has had this issue or has any ideas?
DROID76 said:
So am I to assume that nobody has had this issue or has any ideas?
Click to expand...
Click to collapse
I turned GPS off, enable the use wireless networks in location settings. Then turned GPS back on.............and now mine works.
What setting did you turn the gps off and back on in.
I tried that and I still have the Current location issue.
I just turned on wifi, I got my correct city showing again.
I think it's an issue with 3g that I posted another thread about.
So now my issue with 3g is that I can't get google to sync contacts, calander, email well, google talk times out, market can't pull open pages and now my current location city name.
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
Does anyone else have a network issue with news and weather ?
I'm running Bugless Beast JB with Trinity Kernel.
It won't refresh and says there's a network issue.
The Google says this could be a server side issue, but just wanted to see if anyone else has the same issue ?
Had the same issue since last night.
UK.
Regards.
i'm having the same issue, i think/hope it's just a temporary server problem
here is another thread about it
http://forum.xda-developers.com/showthread.php?t=1786370
Same issue here in France, ever since this morning...
Not just me then... wouldn't be the first time it went down for several hours. Time to find a replacement, I think.
Yeah,same here.And I deleted and reinstalled widget,looked trough different settings and so on...
My logcat says:
07-21 19:51:35.822 2657 2657 W Genie : Cache file not found: java.io.FileNotFoundException: /data/data/com.google.android.apps.genie.geniewidget/files/genie_iconcache (No such file or directory)
Not sure if it is related, but I deleted all app caches recently
Why is it always the good apps that quit working? Why can't the BlockBuster bloatware app quit working?
Sent from my unrooted DroidX using Tapatalk
Seems to have been fixed, news and weather displaying and refreshing properly now.
same problem here with LG-P500 - always get network error...
sometimes it work if i enable "use wireless networks" for getting location but most of the time it doesn´t work.
searching manually for a location never works!
it stopped working since google introduced this:
http://phandroid.com/2012/07/17/goo...visualizations-for-tablets-to-search-results/
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