Related
Good evening guys-
After updating from ICS to JellyBean, my gps cannot find or lock onto any satellites.
If I enable wifi, its accurate to 20meters.. If not, it won't lock even after 15 minutes.
Any help is greatly appreciated-
mine has been similar in PA2.00 and CM10.
It actually will lock after a long time. Sometimes up to 30 minutes.
Interested in any answers... I noticed in the gps.conf file agps appears to be off. I don't know if that is the issue.
Unfortunately searching for a fix just reveals too much information with a lot of supposed fixes, but no consensus so far as i can tell.
brian Marshall said:
mine has been similar in PA2.00 and CM10.
It actually will lock after a long time. Sometimes up to 30 minutes.
Interested in any answers... I noticed in the gps.conf file agps appears to be off. I don't know if that is the issue.
Unfortunately searching for a fix just reveals too much information with a lot of supposed fixes, but no consensus so far as i can tell.
Click to expand...
Click to collapse
Actually agps was turned off to improve lock times...some people noticed no difference with it off, others noticed huge improvements with half the lock time
You can change it to true, then wipe cache and dalvic cache in recovery and see if it makes a difference
Sent from my SGH-I997 using Tapatalk 2
mg2195 said:
Actually agps was turned off to improve lock times...some people noticed no difference with it off, others noticed huge improvements with half the lock time
You can change it to true, then wipe cache and dalvic cache in recovery and see if it makes a difference
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
is that a 'go ahead and try it, it wont work, but go ahead and try it anyway' ?
It seems like a lot of people are having problems with GPS in jellybean, and some aren't. There's so many 'this worked for me' solutions, but I'm starting to think it's coincidence.
Someone mentioned installing and running copilot once. Did that. it didn't work. Without root permissions what could it really change to improve anything?
I ran Faster Fix. It edited my gps.conf file (which it doesn't tell you that it does) It didn't help. it might have made it slightly worse.
I found a few other gps.conf files for jellybean ROMs, but haven't tried those yet.
This is how we learn and share our info, by trying. Just make a back up of anything that you want to change or replace.
GPS works perfect on my PA Jelly Beaned Infuse. First I ran GPS Test, it took a good twenty minutes if not more for it's first lock.
But now, I get a lock in a few seconds.
GPS Test, is free in the market.
Planning my escape!
GPS Test has kicked my GPS in the butt and got it working with almost every ROM I've flashed. Once you get over that first delay (downloading satellite data?) the first time you run it, it locks on fairly well afterward. At least, that's been my experience
Truckerglenn said:
This is how we learn and share our info, by trying. Just make a back up of anything that you want to change or replace.
GPS works perfect on my PA Jelly Beaned Infuse. First I ran GPS Test, it took a good twenty minutes if not more for it's first lock.
But now, I get a lock in a few seconds.
GPS Test, is free in the market.
Planning my escape!
Click to expand...
Click to collapse
I've already done that. It helped the next time I ran maps. When i left work yesterday I had maps give me turn by turn directions home. It took a couple minutes to lock, but after that it was working.
Then this morning I tried again. It wouldn't lock at all on the way in to work this morning. (only a 15 minute drive)
I also tried editing my GPS conf file this morning. I tried using ES file explorer, root explorer, and flashing. All three resulted in an empty file. ES says it was successful. Root explorer gives an error message 'there was not enough free disk space to complete the paste operation'
Flashing says it was successful, but again, it ends with an empty file. 0 bytes.
The file i used for the flash attempt is here. http://forum.xda-developers.com/showthread.php?t=1817558
With the gps.conf file I'm going to go leave the phone out in my car with gps on and see if it locks.
I understand that developers do a lot of work on this. I'm not trying to be a jerk. I just see a lot of people having the same issue and no agreement on a solution or even what the actual problem is.
brian Marshall said:
...
I understand that developers do a lot of work on this. I'm not trying to be a jerk. I just see a lot of people having the same issue and no agreement on a solution or even what the actual problem is.
Click to expand...
Click to collapse
I believe this is because there is no solution. If you want to try to help solve the problem, "adb shell" in and start tinkering.
You'll quickly find that GPS is anything but an easy thing to fix. A good SUPL provider for you may be completely different for others.
I can't find the Answer that fixed it for me,
but what I did:
Plug phone in, disable wifi, leave phone near window, and let
https://play.google.com/store/apps/...251bGwsMSwyLDYsImNvbS5hbmRyb2lkLmdwc3Rlc3QiXQ..
that app run... :45 minutes later it locked (GPS icon on Status Bar stopped blinking and showed locked, solid) with 7 satellites.
waited, rebooted the phone, and it locked in about 3 minutes.
-hope this helps.
other than that, love this ROM!
choffman said:
I believe this is because there is no solution. If you want to try to help solve the problem, "adb shell" in and start tinkering.
You'll quickly find that GPS is anything but an easy thing to fix. A good SUPL provider for you may be completely different for others.
Click to expand...
Click to collapse
Now that is an actual answer.
I suppose part of the problem for us noobs sorting through 300 page threads is all the filler with people saying "great rom omgz so awesome" even when they are posting on the first page and the ROM hasn't even been up long enough to do much more than flash it and swipe through the home screen.
All through out the CM10 and PA threads there are people saying GPS is working flawlessly... and then other people saying they have some fix. I guess people aren't supposed to post frivolous stuff in the dev threads, but they do.
Anyway, I ended up going back to GB as GPS is something I really need.
Hey guy's, i've also been having allot of issues with GPS just not being what it used to be, and it's pretty obvioius that this is an issue across the board for all JellyBean roms. I think those who mention that "GPS works flawlessly" don't quite understand the issue with AGPS (Assisted GPS), or they are not quite testing it thoroughly enough to see the problem.
To get an understanding of what AGPS is, and how it helps improve initial lock times, have a read here: http://en.wikipedia.org/wiki/Assisted_GPS
Also, to gain a better understanding of what I mean by "cold start" as you read below, and how it differs from a warm or hot start please read the following: http://m.gsmarena.com/glossary.php3?term=gps
That being said, i have been doing allot of digging in the hopes that someone out there has a solution to the problem with AGPS on the CM10 based ROMs on our phone.
To clarify the problem: AGPS does not seem to work and Initial lock times from a cold start can take several minutes, (this is not normal if AGPS is doing it's job). To clarify further, no one is saying that GPS does not work, it does in fact work, it just takes it's sweet time to lock and it seems to rely on pure GPS to download ephemeris data from the actual GPS birds for satelite lock acquisition, rather then downloading AGPS data over the network to speed things up. After the initial lock though, GPS functions as it should. After this point, if you do not use the phone again for several day's, it seems that upon first firing it up again you will experience the long delay in first lock. This is especially true if you keep GPS services turned off ussually to conserve battery. Those who report GPS is fine are probably keeping GPS services on all the time, and your GPS is probably working in the background at times and obviously will start up allot faster then it would from a cold start. (This is where i believe all the conflicting info comes from!)
The only info i have been able to find that did actually have an impact on my lock times was the thread below.
http://forum.xda-developers.com/showthread.php?t=1881655
I just started testing this out yesterday and i have seen some positive results. But i would caution those of you out there, and say that this is probably not a "fix" per se, but it did help cut down lock times in my case and at the very least it is a very inoformative thread that everyone should read.
What i have realisticly been able to achieve from a cold start is about 75 seconds to lock at the fastest. i.e. GPS services were off, i turned them all on, and now i started up GPS Status or GPS Test to get a lock. After that, as long as I haven't rebooted my phone it takes only a few seconds to lock.
How i tested, i started GPS Status, I then went to Tools --> MANAGE A-GPS STATE -> RESET (This is important to ensure you are clearing previously cached data. We want to make sure your previous cached info does not skew the effects of your changes.
I then replaced the gps.conf with the one contained in that thread, and i also made the change that was suggested in the Notes section that suggested modifying or adding a line in your build.prop file to "ro.ril.def.agps.mode = 1". This change set's your gps to use AGPS in Mobile Station Based (MSB) mode. For reference, setting it to "2" would set your AGPS to function to Mobile Station Assisted (MSA) mode. (Mode 1 - gave me more accurate initial locks at the expense of a bit longer lock times, Mode 2 gave me slightly quicker initial lock times, but was rather flaky and my position drifted quite a bit until GPS was running for quite some time.)
If your curious what is the difference between the two modes, see here: http://en.wikipedia.org/wiki/Assisted_GPS#Modes_of_operation
After making the changes to gps.conf and build.prop i rebooted my phone. When phone reboots, i then go back into GPS Status app, select settings, Tools --> MANAGE A-GPS STATE -> RESET, and then back to settings, Tools --> MANAGE A-GPS STATE -> DOWNLOAD (This should force the phone to attempt an AGPS download, if it hasn't already done so upon launching the app).
I have seen this same gps.conf being used in the newer RemICS-JB build. However based on the lack of feedback in that thread, i don't know if this is the golden fix we have all been looking for.
Even though this may not fix all your issues, i hope at the very least it helps clear up what the actual problem is, and how AGPS is supposed to work.
** Important Notes: **
- The version of the config that i was using was the Download the Google Specific No-SSL v3.1
- If you use the SSL version, then it will also require that you download the certifcate file. It's best to just stick with NO SSL as is explained in the thread.
- You should also note that i have cleaned out all the live wall papers, face unlock, and allot of other crap that i don't use to free up space in the /SYSTEM partition. I now have aproximately 21MB free in this partition. I think at least part of the problem with certain ROM's is that they have the /SYSTEM partition filled to the max with virtually no free space at all. I'm no expert on the subject, but i'm guessing that the AGPS data get's downloaded to this partition some where. Obviously if there is no space, then that would cause issues. Several others have reported shortened initial lock times after making room in the /SYSTEM partition.
- Another mistake people are making when testing AGPS and reporting false info, is having their WIFI on when testing GPS. To isolate the issue guy's you need have wifi off and you need to use a tool like GPS Status or GPS Test that shows that actual lock to satelites. You cannot properly test this and see the issue by using WIFI and turning on Google maps. Google maps will look at your reported wifi position and to you it looks like bamm.. i just got a lock in 2 seconds to withing 50 meters, wow these guy's are nut's, my GPS is awesome. Guess what.. your wifi and google maps is awesome.. not your GPS.. lol
- If anyone is familiar with running log's, it would be great if you could do a comparison of before and after. Showing the log of a completely fresh JB build, that shows that the AGPS data is not being downloaded, and then another log after all the changes above (including freeing up space in /SYSTEM) and hopefully it will show that AGPS data is now being downloaded and utilized. I myself am not familiar with logging data on the infuse, so i cannot and will not call this a fix until someone can actually show with real log's that AGPS data is now being utilized after these mods.
Thankfully, I'm one of the lucky ones who have always had a working GPS. It worked great when I was running AT&T stock Froyo, really good while I was on XDA GB roms, and fair > good after I went to PA JB. By far Scott's latest release of PA JB has been the best in this respect, but I can't help but tinker now that I've turned into a Droid zombie Strictly speaking the stock GPS configuration included on Scott's PA JB ROM worked charmingly, but I still had an issue whenever the phone went into deep sleep (say overnight without using it) the GPS lock the next morning took almost as much time coming from a sleep state as a cold boot. So, Like DaMeatMan I decided to give http://forum.xda-developers.com/showthread.php?t=1881655 a go. I chose the flashable option, and like DMM also edited the prop file. I picked the Google "no SSL" version 3.1 instead of the AT&T specific version. I figured I would give that one a try.
I'll keep everyone posted, buy my first impression (could be placebo effect) is that this configuration file and modification actually does improve over the original PA JB configuration by a small margin. Reported accuracy is better (by 10ft on average). Satellites in view and actually locking are 1-2 better than before. My main hope is that I can actually fire up Navigation in the morning and get working directions without having to fire up GPS Test first and relock all the NA satellites. I travel a lot, both for business and outdoor sports (hunting and fishing), and I have come to rely pretty heavily on GPS. I got spoiled when I got my first GPS capable phone because that meant I could leave my handheld GPS at home most of the time and that was one less thing I had to carry.
wevsspot said:
Thankfully, I'm one of the lucky ones who have always had a working GPS. It worked great when I was running AT&T stock Froyo, really good while I was on XDA GB roms, and fair > good after I went to PA JB. By far Scott's latest release of PA JB has been the best in this respect, but I can't help but tinker now that I've turned into a Droid zombie Strictly speaking the stock GPS configuration included on Scott's PA JB ROM worked charmingly, but I still had an issue whenever the phone went into deep sleep (say overnight without using it) the GPS lock the next morning took almost as much time coming from a sleep state as a cold boot. So, Like DaMeatMan I decided to give http://forum.xda-developers.com/showthread.php?t=1881655 a go. I chose the flashable option, and like DMM also edited the prop file. I picked the Google "no SSL" version 3.1 instead of the AT&T specific version. I figured I would give that one a try.
I'll keep everyone posted, buy my first impression (could be placebo effect) is that this configuration file and modification actually does improve over the original PA JB configuration by a small margin. Reported accuracy is better (by 10ft on average). Satellites in view and actually locking are 1-2 better than before. My main hope is that I can actually fire up Navigation in the morning and get working directions without having to fire up GPS Test first and relock all the NA satellites. I travel a lot, both for business and outdoor sports (hunting and fishing), and I have come to rely pretty heavily on GPS. I got spoiled when I got my first GPS capable phone because that meant I could leave my handheld GPS at home most of the time and that was one less thing I had to carry.
Click to expand...
Click to collapse
I have been have many of the same problems as others in this thread but I tried the fix in the S3 thread quoted above and it seems to have helped for right now. The first time I ran GPS Test after rebooting it did take a while (5-8min), but after that I get a lock in few seconds. I used the Google "no SSL" package also. I will do some more testing tomorrow and see if its reliable.
Hi guys,
I run PA 4.4 for like 10 days now. Since a week ago I have strange locations in my Google location history - constantly, when not moving - and rather accurate when I am outside (maybe has something to do with the wifi connection when stationary at home or at work?)...
One interesting part of it is: the first days of my new PA experience everything was fine. So probably it does not have anything to do with it. That first day I had the issue my phone crashed earlier while I was outside and I had to do a reboot. Maybe some settings were changed during that!? Or... maybe it doesn't and it's just a coincidence after some apps where updated (Google Search or so)...
I tried quite some settings to figure out what happens here - and it is not trivial - to my mind:
I did another clean install of the ROM; had the same issue again
I changed between "high accuracy" and "battery saving" mode in the location settings; no change
I went to the developer settings and unchecked "accept mock locations" (is that how the option is called in English?); no change
I have a Nexus 10 also running Android 4.4.4 and started to record my location history from that device with different settings: all are fine and accurate! When I record from both devices I can actually see my history jumping in 5-minute-mode...
Any ideas, any suggestions?
Please...
Two more findings, which make this issue even stranger:
When I move in the house - e.g. 2nd instead of ground floor - I get different locations, some 100 or 200 meters away, but both far from home.
I turned wifi off for one and a half hour - that resulted in perfect locations!! Locations were inaccurate after turning wifi on again...
What is wrong here?? So I get more inaccurate locations when connected to wifi!?
i always run straight gps and never wifi. imo its a conflict of interest.
gps is dead accurate, so the only time you could benefit from wifi is when you are in a building with no gps signal, and frankly, why would i need 100% accurate gps if im already in the building.
again imo, what is happening is, it can only reference wifi that it knows the exact location of. it has no way to tell how far from that wifi you are, so its guessing based on a limited gps signal and known wifi points.
i think its a waste of battery to be scanning wifi points all the time any ways, unless you have a constant use for it.
bweN diorD said:
i always run straight gps and never wifi. imo its a conflict of interest.
Click to expand...
Click to collapse
Thank you for the answer! And I sort of agree...
But the question is:
what did change that day when my location started to be different? I never had problems for more than two years of using the location history. Even after moving in April everything was fine with the wifi locations. I get one accurate reading like every one to three hours - so the location jumps from time time. Why is that? Is that a gps reading?
Plus: how could I change the settings? The only thing I can chose from is: "battery saving" (cell towers and wifi) or "high accuracy" (the same plus gps). I selected the second option but obviously still the Google location service does not really use it. When I turn off wifi it can only use cell towers plus gps... but obviously I want to be connected to the wifi when being at home.
I can't say why it started acting up.
If you use WiFi you are kinda stuck.
I only have GPS on and denied anything that wants to use WiFi for any reason.
I don't know where the option is found, but I remember it asking if I wanted to use WiFi to help results or something like that, I chose no.
Sent from my LG-VS980 using XDA Premium 4 mobile app
bweN diorD said:
I don't know where the option is found, but I remember it asking if I wanted to use WiFi to help results or something like that, I chose no.
Click to expand...
Click to collapse
I guess that option is the "use wifi for location detection although wifi is turned off" which can be found in the wifi advanced options. But I turned that on and off, no change.
But one more test from myself:
I let wifi on but disconnected from my home network. The result is: accurate locations! So the problem is not the wifi itself but a connected wifi!? And it is not only the home network because I had the same issue at work.
Plus: we just had a thunderstorm, that could have been the reason why cell towers and/or gps reacted differently: my location was at some new place about more than a mile away. The worst thing is: accuracy of that location point was about half a mile -- which means: my real location was not inside the accuracy cycle (that blue cycle when using location history)!!
The accuracy cycle is always very small when I get the real readings at home and always about half a mile in radius when somewhere else...
that is basically the problem with using wifi to help. there are too many variables. location needs to know the location of the wifi, but then there is a broadcast radius that decreases accuracy. there is also the question, what does it do when you are connected to a wifi it doesnt know the location of?, that could cause inaccuracy. maybe it makes an uneducated guess, who knows. there is also the issue, what if it thinks it knows the location but its actually wrong?
the list of possible scenarios could go on and on as to why it isnt reporting correctly.
the only way to truly know why it is wrong is to find out why exactly it thinks you are where you are when its wrong. there has to be some exact source of information its using to base your wrong location on. unfortunately, i doubt there is any way for the common user to get this information, let alone take corrective action so its not inaccurate in the future.
wrong locations only when wifi is connected, only on one device
OK, what do we already know?
I have the problem for some 8 to 10 days now. Never had it before, only have it on one device.
Maybe a coincidence but this behavior started on a day where my phone crashed and I had to reset.
I made a clean new re-install of the PA 4.4 and recently received the update to PA 4.42. There are no changes in the behavior.
It is only my phone (running ParanoidAndroid based on KitKat 4.4.4), my tablet (Nexus 10 running stock KitKat 4.4.4) does not have this problem (so it's no wifi relocation because of moving or such general problem).
I have the problem with more than one wifi! Have already seen these false locations when connected to the home and when connected to the work network. Problems with both networks started the same day...
Wrong locations are constantly there when my phone is connected to a wifi.
It's not always the same location, sometimes I get different readings, but it's 90% a position ~430m west of my home.
The correct locations have high accuracy (a few meters), the wrong locations have very low accuracy (~1000m or even more).
When I start Google Maps (i.e. probably when the phone uses gps) I can see my position moving towards the correct location.
When I switch off wifi or when leave wifi on but disconnect my phone from the network, then I get the correct location constantly.
Roughly every 1 to 3 hours there is one correct location within the list of false locations.
I tried virtually every combination of settings, "high accuracy" and "battery saving" for the location service, "no mock locations" in the advanced developers settings, "use wifi for location detection although wifi is switched off" in the wifi settings, ...
Is there some sort of cache that might be corrupted!?
Is there a possibility to force using gps?
What else...
Tho-D said:
OK, what do we already know?
I have the problem for some 8 to 10 days now. Never had it before, only have it on one device.
Maybe a coincidence but this behavior started on a day where my phone crashed and I had to reset.
I made a clean new re-install of the PA 4.4 and recently received the update to PA 4.42. There are no changes in the behavior.
It is only my phone (running ParanoidAndroid based on KitKat 4.4.4), my tablet (Nexus 10 running stock KitKat 4.4.4) does not have this problem (so it's no wifi relocation because of moving or such general problem).
I have the problem with more than one wifi! Have already seen these false locations when connected to the home and when connected to the work network. Problems with both networks started the same day...
Wrong locations are constantly there when my phone is connected to a wifi.
It's not always the same location, sometimes I get different readings, but it's 90% a position ~430m west of my home.
The correct locations have high accuracy (a few meters), the wrong locations have very low accuracy (~1000m or even more).
When I start Google Maps (i.e. probably when the phone uses gps) I can see my position moving towards the correct location.
When I switch off wifi or when leave wifi on but disconnect my phone from the network, then I get the correct location constantly.
Roughly every 1 to 3 hours there is one correct location within the list of false locations.
I tried virtually every combination of settings, "high accuracy" and "battery saving" for the location service, "no mock locations" in the advanced developers settings, "use wifi for location detection although wifi is switched off" in the wifi settings, ...
Is there some sort of cache that might be corrupted!?
Is there a possibility to force using gps?
What else...
Click to expand...
Click to collapse
I guess you shouldn't rule out that it is an issue caused by the ROM some how.
On my phone I can force it to use GPS only, I have the option anyways.
Under location I have device only or something like that, it says it only uses GPS when that option is selected.
Sent from my LG-VS980 using XDA Premium 4 mobile app
bweN diorD said:
I guess you shouldn't rule out that it is an issue caused by the ROM some how.
Click to expand...
Click to collapse
I thought about that, too. Means to installiert something else, CM11 vor so...
There's the option "device only".
That option does not record the location history, afaik.
Which means: Google Now does not work. So that's not an option...
Tho-D said:
There's the option "device only".
That option does not record the location history, afaik.
Which means: Google Now does not work. So that's not an option...
Click to expand...
Click to collapse
Ohh OK, I didn't know that. Thanks for the info
Sent from my LG-VS980 using XDA Premium 4 mobile app
Tho-D said:
There's the option "device only".
That option does not record the location history, afaik.
Which means: Google Now does not work. So that's not an option...
Click to expand...
Click to collapse
so i did a little test today on the way home from work, as i took a different route than normal to avoid traffic.
when i started "maps" i had to allow google location services to navigate. so im pretty sure you can use device only as long as you allowed google location for apps, as it said something about my google now functionality when i turned it off after navigating.
last week i navigated a 3 hour trip, on a different rom, with no issues. today, maps couldn't seem to start gps to find my location to start navigating. so i turned on "high accuracy", more to test than anything else, and it found my location and we were navigating home .
i knew where i wanted to go but at some points that varied from where maps wanted me to go. for a while it did good at making quick corrections to my path. about 20 minutes in, i didn't follow its directions again. well this time, it didn't recognize that i didn't turn, then advised me to make a subsequent turn onto a road that was off the road i didn't turn onto. now, the road i am on is about 1/4 mile from the road it thinks im on, the 2 roads are parallel. well it took maps over a mile, after i made another turn towards the road it thought i was on, before it realized it was wrong and made corrective instructions. after that, i made a quick stop to grab some liquid refreshment for the night and turned off navigation, as i was close to home.
this really goes to prove nothing more than "high accuracy" is not always highly accurate. i traveled across 3 states last week for 3 hours on "device only" and never once was it wrong about my exact location.
just wanted to share my experience, really doesn't help or fix your problem, but may shed some light on the possible inaccuracies across multiple devices.
bweN diorD said:
so im pretty sure you can use device only as long as you allowed google location for apps, as it said something about my google now functionality when i turned it off after navigating.
Click to expand...
Click to collapse
I tried this and yes, Maps works with the "device only" setting. But when using Now it said that location-based cards (weather, traffic, ...) only work with "high accuracy" or "battery saving". So for me this setting is useless.
I guess I'll do another clean install and try CM11 or so...
it's not ROM related
I trid to install CM11 M8 today. For some reason I wasn't able to, received these strange "Unfortunately process ... has stopped" messages all the time and was not able to complete the initial setup. The only hint I found online is to make sure CWM recovery is up to date. I use v6.0.5.0 which I assume is up to date.
So I made another clean install of PA 4.42. Then I downloaded another ROM: did a clean install of SlimKat. This went smoothly, but I have the same location problems, both times!!!!
I guess we can be sure my location problems are not related to the ROM.
One thing I saw that seems noteworthy: I had correct locations for some time and then the wrong locations started again. Maybe this has to do with the system restoring backed up settings or installing / updating all the apps!?
Any ideas?
Tho-D said:
I trid to install CM11 M8 today. For some reason I wasn't able to, received these strange "Unfortunately process ... has stopped" messages all the time and was not able to complete the initial setup. The only hint I found online is to make sure CWM recovery is up to date. I use v6.0.5.0 which I assume is up to date.
So I made another clean install of PA 4.42. Then I downloaded another ROM: did a clean install of SlimKat. This went smoothly, but I have the same location problems, both times!!!!
I guess we can be sure my location problems are not related to the ROM.
One thing I saw that seems noteworthy: I had correct locations for some time and then the wrong locations started again. Maybe this has to do with the system restoring backed up settings or installing / updating all the apps!?
Any ideas?
Click to expand...
Click to collapse
the only way to rule out the rom's is to return to stock and check it there.
its not uncommon to have similar issues across multiple rom's.
im not saying you are wrong, changing from one rom to another is just not a good way to check an issue.
bweN diorD said:
the only way to rule out the rom's is to return to stock and check it there.
its not uncommon to have similar issues across multiple rom's.
im not saying you are wrong, changing from one rom to another is just not a good way to check an issue.
Click to expand...
Click to collapse
Oh, is that the case?
Then I should install the stock Samsung ROM and check. Probably will do it in a few days since I am busy the next days.
BTW: I installed SlimKat and then PA again. After installing SlimKat I now have TWRP instead of CWM recovery and the settings of 5x5 Icons on the home screen plus smaller font size and probably a few other settings remain in PA although I did factory reset, format cache and so on...
The thing is: how can I change this back!?!? Didn't find it in the settings. It'not font size (which is set to 100%).
Tho-D said:
Oh, is that the case?
Then I should install the stock Samsung ROM and check. Probably will do it in a few days since I am busy the next days.
BTW: I installed SlimKat and then PA again. After installing SlimKat I now have TWRP instead of CWM recovery and the settings of 5x5 Icons on the home screen plus smaller font size and probably a few other settings remain in PA although I did factory reset, format cache and so on...
The thing is: how can I change this back!?!? Didn't find it in the settings. It'not font size (which is set to 100%).
Click to expand...
Click to collapse
there is another partition thats not normally wiped with a factory reset. i believe its called "data/media". the official cwm's that i have used have an option to wipe this separately, but i havent seen this option in twrp, or know if it wipes it by default. my guess would be no, but i could be wrong.
anyways, some settings and/or app data is stored in this area. you likely need to wipe this to fix the problem. that would be my best guess anyways.
bweN diorD said:
there is another partition thats not normally wiped with a factory reset. i believe its called "data/media". the official cwm's that i have used have an option to wipe this separately, but i havent seen this option in twrp, or know if it wipes it by default. my guess would be no, but i could be wrong.
anyways, some settings and/or app data is stored in this area. you likely need to wipe this to fix the problem. that would be my best guess anyways.
Click to expand...
Click to collapse
Just rebooted into recovery and was surprised its CWM again!? Anyways, good its back!
The one option I always used is "wipe data/factory reset" (plus of course "wipe cache"). Under "mounts and storage" there's an extra option "format /data". Should I try this one?
Tho-D said:
Just rebooted into recovery and was surprised its CWM again!? Anyways, good its back!
The one option I always used is "wipe data/factory reset" (plus of course "wipe cache"). Under "mounts and storage" there's an extra option "format data". Should I try this one?
Click to expand...
Click to collapse
I'm pretty sure it says data/media. I don't have cwm on right now or I would check, but I think it is under mounts and storage. It was in the same dir where you can format system and such if I remember correctly.
Its also possible someone removed that option from your version, but I don't know why they would unless your phone doesn't have that partition.
Sent from my LG-VS980 using XDA Premium 4 mobile app
From out of the box I've been having GPS issues. It won't get a lock when I use navigation. I've tried different places, different apps (waze and google maps) and different times (different days). If I restart the phone, it'll get a lock after about 10 seconds.
What would cause the GPS to not work unless the phone is restarted?
I contacted OnePlus and they all but told me to go screw myself. They suggested that I should walk around to get a GPS lock and if it persists that I should reset my phone. I reset my phone but all that did was waste two hours of my life re-installing apps and settings.
Any ideas? Anyone else with this issue? The phone is perfect besides this =(
Can't say I'm sure, as I haven't had any issues, except if I caused them. You let google apps have location access in the settings? Are you wake blocking any google location services?
+1 to what roxxorz said. If OP applied the workaround to Google Play Services and denied access to location it can cause a problem.
Also in addition to that make sure your location is set to "High Accuracy" as well as enabling WiFi.
Do note that when your phone is on High Accuracy it is draining the most battery.
I also have the same problem when I m on stock XNPH25R. Have to reboot in order to get a lock from the GPS.
http://forum.xda-developers.com/showpost.php?p=54334569&postcount=1
But after I switch to nightlies, no such GPS issue, works like a charm.
I am actually on stock 30O cm11s and I have a GPS lock in two out three seconds. Try to download GPS status app from Google play
Inviato dal mio A0001 utilizzando Tapatalk
Sorry I'm a complete noob when it comes to the advance stuff. I know nightlies are cyanogenmods quick version changes that may sometimes have small bugs, but never tried updating phone with nightlies. I've always just done the standard OTA updates on my previous phones.
GPS is always on high accurac. Surprisingly today, GPS was working like a charm. I haven't done anything that should affect this positive change.
What is wake locking?
ValmonUni said:
Sorry I'm a complete noob when it comes to the advance stuff. I know nightlies are cyanogenmods quick version changes that may sometimes have small bugs, but never tried updating phone with nightlies. I've always just done the standard OTA updates on my previous phones.
GPS is always on high accurac. Surprisingly today, GPS was working like a charm. I haven't done anything that should affect this positive change.
What is wake locking?
Click to expand...
Click to collapse
It could be just a thing. Sometimes I'll have apps [maps] that'll lock up, like if they tried to connect and I stopped it / turned off data. At that point killing / force closing the app works.
Normally I'd say if you don't know, don't worry about it, but wake lock is where an app / process keeps the phone awake and keeps the phone from sleeping properly, which leads to more battery drain. Google play services is notorious for waking the device for nonsense, so more advanced users block it. If you have no issues, I'd recommend leaving it alone.
Same problem here
ValmonUni said:
From out of the box I've been having GPS issues. It won't get a lock when I use navigation. I've tried different places, different apps (waze and google maps) and different times (different days). If I restart the phone, it'll get a lock after about 10 seconds.
Click to expand...
Click to collapse
I'm seeing the same thing. GPS was working fine for a week or so, but when I went to use Waze this morning it wouldn't get a lock. GPSTools showed satellites, but wouldn't lock either. Reboot fixed it. A few hours later, same problem. Reboot once again fixed it. This is all stock.
I don't have anything to suggest, but wanted to add to the evidence that there is a problem.
I did install a couple of apps from the app store between the last time I saw the GPS work normally and this morning, so I'll try uninstalling them to see if that helps. I killed them from the task manager, but that didn't help.
walendo said:
I'm seeing the same thing. GPS was working fine for a week or so, but when I went to use Waze this morning it wouldn't get a lock. GPSTools showed satellites, but wouldn't lock either. Reboot fixed it. A few hours later, same problem. Reboot once again fixed it. This is all stock.
I don't have anything to suggest, but wanted to add to the evidence that there is a problem.
I did install a couple of apps from the app store between the last time I saw the GPS work normally and this morning, so I'll try uninstalling them to see if that helps. I killed them from the task manager, but that didn't help.
Click to expand...
Click to collapse
Sorry to hear you're having trouble too, but glad I'm not going nuts. You're only the second person I've read that has the same issue I have. OnePlus support was of no help nor did they admit that the issue was real. I hope they'll figure this one out, cause I can't.
Please vote on this issue in CM's bugtracker: https://jira.cyanogenmod.org/browse/BACON-115
Hints
Here's some new data. As I mentioned, my GPS was working fine up until a few days ago. In those few days, I installed 2 apps: "UP", by Jawbone, and "MyFitnessPal". Both of them use the GPS for some sort of logging.
Anyway, this morning I installed "AppOps" from the App Store. It's the one by Sylvain Galand, and the package is fr.slvn.appops. It doesn't need root, apparently. I used that to disable location access from both UP and MyFitnessPal. Since then, my GPS has been working fine again.
I think there's something broken under the LocationManager implementation in this version of Cyanogen. Seems like some apps are able to break it somehow. The other thread about this subject points fingers at Dragon Dictate, too. Whatever it is, apps shouldn't be able to wedge a system service like this.
walendo said:
Here's some new data. As I mentioned, my GPS was working fine up until a few days ago. In those few days, I installed 2 apps: "UP", by Jawbone, and "MyFitnessPal". Both of them use the GPS for some sort of logging.
Anyway, this morning I installed "AppOps" from the App Store. It's the one by Sylvain Galand, and the package is fr.slvn.appops. It doesn't need root, apparently. I used that to disable location access from both UP and MyFitnessPal. Since then, my GPS has been working fine again.
I think there's something broken under the LocationManager implementation in this version of Cyanogen. Seems like some apps are able to break it somehow. The other thread about this subject points fingers at Dragon Dictate, too. Whatever it is, apps shouldn't be able to wedge a system service like this.
Click to expand...
Click to collapse
I honestly hope that they at the very least acknowledge that this issue exists. GPS Navigation is a primary use for mobile. I haven't installed anything that would break location. All I Have is Waze and Google.
OK, so I know M7 isn't the latest CM build, but it's the latest one without issues with GPS, so that's what I'm on since I use GPS a lot.
So last week I replaced my home router. This of course means reconfiguring all the wifi devices around the house, including my wifi thermostat. The unique thing about the thermostat is that to configure it, you connect a laptop/phone/tablet to the thermostat's ad-hoc wifi network, tell it which infrastructure ssid to connect to, verify a pin from the thermostat's screen (so nobody can hijack your t-stat from outside the house), and that's it.
thing is, when you use Cyanogenmod (at least on the relay) to connect to an adhoc network, it breaks wifi. what happens is you can't connect to any other wifi networks, and can't even scan to see available networks till you reboot. sometimes it doesn't work even after a reboot. strangely, the tethering/hotspot still works fine. you just can't connect the phone to a hotspot whether it's at home or work or anywhere.
i'd been having other issues and general slowness with the phone, so i decided to backup a few apps with TiBu and do a factory reset. that worked... till i tried connecting to the thermostat again, and it broke wifi completely this time.
solution? go to /data/misc/wifi/ and rename wpa_supplicant.conf to wpa_supplicant.conf.old (or whatever, as long as it's a different name) and reboot. the system will automatically create a new conf file. boom - wifi fixed.
obviously this requires root, but that's not an issue in CM. I doubt it matters, but i used ES file explorer since it's got a good root filesystem browser and mounting / or system as RW is a simple matter of a checkbox in the settings.
when i compared the newly created wpa_supplicant.conf with the one i'd renamed (.old) the only real difference i could see was the saved networks at the bottom. so you might be able to get away with simply deleting the offending network={ blah blah } section instead of completely renaming the conf file. the advantage here would be if you have a bunch of saved networks that you don't want to get rid of, it will keep those saved networks. the conf file is a plaintext file so it's easy enough to understand what you're looking at, and modify appropriately.
MODS: I apologize if this is in the wrong forum. I figured since it probably only applies to CM, I should post it in the dev forum rather than the general one. If it needs to be moved, I don't be offended.
Gibson99 said:
OK, so I know M7 isn't the latest CM build, but it's the latest one without issues with GPS, so that's what I'm on since I use GPS a lot.
So last week I replaced my home router. This of course means reconfiguring all the wifi devices around the house, including my wifi thermostat. The unique thing about the thermostat is that to configure it, you connect a laptop/phone/tablet to the thermostat's ad-hoc wifi network, tell it which infrastructure ssid to connect to, verify a pin from the thermostat's screen (so nobody can hijack your t-stat from outside the house), and that's it.
thing is, when you use Cyanogenmod (at least on the relay) to connect to an adhoc network, it breaks wifi. what happens is you can't connect to any other wifi networks, and can't even scan to see available networks till you reboot. sometimes it doesn't work even after a reboot. strangely, the tethering/hotspot still works fine. you just can't connect the phone to a hotspot whether it's at home or work or anywhere.
i'd been having other issues and general slowness with the phone, so i decided to backup a few apps with TiBu and do a factory reset. that worked... till i tried connecting to the thermostat again, and it broke wifi completely this time.
solution? go to /data/misc/wifi/ and rename wpa_supplicant.conf to wpa_supplicant.conf.old (or whatever, as long as it's a different name) and reboot. the system will automatically create a new conf file. boom - wifi fixed.
obviously this requires root, but that's not an issue in CM. I doubt it matters, but i used ES file explorer since it's got a good root filesystem browser and mounting / or system as RW is a simple matter of a checkbox in the settings.
when i compared the newly created wpa_supplicant.conf with the one i'd renamed (.old) the only real difference i could see was the saved networks at the bottom. so you might be able to get away with simply deleting the offending network={ blah blah } section instead of completely renaming the conf file. the advantage here would be if you have a bunch of saved networks that you don't want to get rid of, it will keep those saved networks. the conf file is a plaintext file so it's easy enough to understand what you're looking at, and modify appropriately.
MODS: I apologize if this is in the wrong forum. I figured since it probably only applies to CM, I should post it in the dev forum rather than the general one. If it needs to be moved, I don't be offended.
Click to expand...
Click to collapse
It does belong in q&a...but my lollipop validus has working gps
REV3NT3CH said:
It does belong in q&a...but my lollipop validus has working gps
Click to expand...
Click to collapse
As does FatToad. However, I do know that the privacy bit in the GPS can be flipped with the drivers we're using in FT. There's an old thread with a post from nard about how to fix that.
Magamo said:
As does FatToad. However, I do know that the privacy bit in the GPS can be flipped with the drivers we're using in FT. There's an old thread with a post from nard about how to fix that.
Click to expand...
Click to collapse
Do you understand more about this "privacy bit", what call in the API flips it, or can give me any other pointers about it? The poster previous to you indicates that GPS works with M7. I thought I had it working with M8, but can't really guarantee that, any more. The post from nard was quite an onerous process, including what looked like reflashing the baseband.
It seems to me that if we really understood this problem, the fix would be quite simple, and could be done by a root-access app. I've done more digging, and see that it seems to be common to many models of Samsung Galaxy phones, and some of the fixes involve doing potentially horrible things to the NVRAM. (like clearing it completely - what could possibly go wrong?)
It seems that the GPS is done in the baseband processor, along with the other radio stuff, but so far I haven't been able to find it. The transceiver chip is just a transceiver, no baseband processor. It looks like the baseband processor might be on the Snapdragon main processor chip, though they don't enumerate it well. In addition they mention a "gpsOne engine" without describing exactly what it is.
I'm still relatively ignorant about Android, a year after getting one. (not enough time) I'm better versed on hardware, but this problem seems to be in the cracks between.
Come to think of it, a simple question... Is there documentation on the communications between Android and the baseband processor?
Gibson99 said:
OK, so I know M7 isn't the latest CM build, but it's the latest one without issues with GPS, so that's what I'm on since I use GPS a lot.
Click to expand...
Click to collapse
I just took my wife's phone outside and tested it. GPS works on M8 from last summer, as does wifi. AFAIK the only thing that doesn't work on M8 is the video camera. (Stills on the camera work.)
This was an older phone than mine, purchased after mine. With mine I didn't need the radio or bootloader updates, my wife's did. I bought the phone for her, used it briefly with my PureTalkUSA SIM card to make sure it was really unlocked. Then I put CM11 on it.
phred14 said:
I just took my wife's phone outside and tested it. GPS works on M8 from last summer, as does wifi. AFAIK the only thing that doesn't work on M8 is the video camera. (Stills on the camera work.)
This was an older phone than mine, purchased after mine. With mine I didn't need the radio or bootloader updates, my wife's did. I bought the phone for her, used it briefly with my PureTalkUSA SIM card to make sure it was really unlocked. Then I put CM11 on it.
Click to expand...
Click to collapse
no idea how old mine actually is; i bought it "like new" from a tmobile reseller here in town and i actually use tmobile for service.
right now i'm on fattoad and once i stepped down my paranoia (i turned on privacy guard for everything including all system apps. hint: don't do that ) it seems good so far. nova launcher has an issue with flickering or disappearing icons, and everything is huge (i need to adjust the dpi) but so far no issues with gps or wifi (though i havent needed to connect to an adhoc network yet).
Do be careful with Privacy Guard. I didn't mention, but although Privacy Guard out of the box tends to make it so that most system apps are unable to be tuned, TeamApexQ likes the option of being able to tune everything in that regard, so we removed the safeguard. (For example, when PG was first ported to CM12, you could tune the settings of the 'Settings' app. Then at our next internal testing build, it was suddenly coming up empty, because CM made a change to exclude tuning for it. We restored full capability because we liked it. But that does mean you can more easily 'shoot yourself in the foot'.
Magamo said:
Do be careful with Privacy Guard. I didn't mention, but although Privacy Guard out of the box tends to make it so that most system apps are unable to be tuned, TeamApexQ likes the option of being able to tune everything in that regard, so we removed the safeguard. (For example, when PG was first ported to CM12, you could tune the settings of the 'Settings' app. Then at our next internal testing build, it was suddenly coming up empty, because CM made a change to exclude tuning for it. We restored full capability because we liked it. But that does mean you can more easily 'shoot yourself in the foot'.
Click to expand...
Click to collapse
I've recently begun to wonder if Privacy Guard might be partially responsible for reduced battery life. I'm under the impression that it lies to apps, providing false information when they have insufficient authority for the real information. Some of those permissions in Privacy Guard are to turn radios on and off. If an app thinks it's turned a radio on, and is trying to communicate based on faked (Really, it's going to look like a failure, at this point.) returns, it may spend more time continuing to try instead of just staying asleep. My battery life comes an goes, but I've noticed that on a "bad day" there are quite a few wakeups in the middle of nowhen, when the phone was sitting there in airplane mode with all radios off.
Of course I may be all wet on this - radio control may be one area where it can say, "You're in Airplane Mode, no program can turn the radio on."
good theory, and like you said, it depends on the app and how pg implements each block.
personally i'm having great battery life in L. i have a 5000mah battery, but usually by this point in the day i'm at about 60%. right now i'm still at 83%. i like how it projects your estimated remaining battery time. first time i looked at the battery chart, i lol'd - it was projecting 4.5 days before it died. i can probably get 2 no sweat even with regular usage, but i'd have to turn off sync and really cut back to make it 4 days.
I've had very good results with some simple rules with Privacy Guard. Generally the only thing I've turned off is the ability for Google Play Services and the Google App (Google Now) to wake up my device and to keep it awake. With those turned off, my battery life has gotten to be pretty damned nice... Though it makes Google Play Services FC once maybe every 24 hours. It restarts just fine, no harm no foul.
My battery life seems to be "bimodal". It either barely makes it 24 hours - basically needs recharging every night, or it lasts on the order of three or four days on a charge.
It seems to be somehow wifi-related, if I were guessing, and in an odd way. If wifi is largely off, but occasionally on, the battery life seems shorter. After wifi has been left off for "a while" (quantity not yet determined) it seems to go into long-battery-life mode. If I keep wifi largely on, and occasionally off (basically between known/trusted wifi places) the battery life comes out somewhere in between, consistent with wifi itself taking some power.
It's been really tough to detect any sort of pattern, but this is the best I've been able to come up with so far. I haven't done rigorous testing, or at least attempts at rigor so far have yielded inconsistent results. I've looked at what the Settings->Battery has available for power diagnostics, and one thing I noted was a lot of spurious wakeups when all radios were turned off. That's what led me to tentatively finger Privacy Guard.
I just saw the setting to show "built-in" apps on PG. I see two different entries for google.services and google.services.framework. The former has scads of wakeups - thanks for the tip. The latter has many, but a much smaller number. Did you block wakeups for both? I presume "built-in" are also "system" that others have said shouldn't be bulk-denied in PG. Are there guidelines anywhere about which are OK, which are useful, etc? (Like this case, and perhaps battery life.)
phred14 said:
My battery life seems to be "bimodal". It either barely makes it 24 hours - basically needs recharging every night, or it lasts on the order of three or four days on a charge.
It seems to be somehow wifi-related, if I were guessing, and in an odd way. If wifi is largely off, but occasionally on, the battery life seems shorter. After wifi has been left off for "a while" (quantity not yet determined) it seems to go into long-battery-life mode. If I keep wifi largely on, and occasionally off (basically between known/trusted wifi places) the battery life comes out somewhere in between, consistent with wifi itself taking some power.
It's been really tough to detect any sort of pattern, but this is the best I've been able to come up with so far. I haven't done rigorous testing, or at least attempts at rigor so far have yielded inconsistent results. I've looked at what the Settings->Battery has available for power diagnostics, and one thing I noted was a lot of spurious wakeups when all radios were turned off. That's what led me to tentatively finger Privacy Guard.
I just saw the setting to show "built-in" apps on PG. I see two different entries for google.services and google.services.framework. The former has scads of wakeups - thanks for the tip. The latter has many, but a much smaller number. Did you block wakeups for both? I presume "built-in" are also "system" that others have said shouldn't be bulk-denied in PG. Are there guidelines anywhere about which are OK, which are useful, etc? (Like this case, and perhaps battery life.)
Click to expand...
Click to collapse
It's difficult to give tips for this, because everyones' usage is different. Get 'WakeLock Detector' and keep an eye on that when your power drain seems more intense. Disable things that make sense to disable based on that.
I know this isn't really the topic, but just because you get a new router doesn't mean you have to reconfigure everything. Why couldn't you just configure the new router with the SSID and password from the old one?
slartibartfast42 said:
I know this isn't really the topic, but just because you get a new router doesn't mean you have to reconfigure everything. Why couldn't you just configure the new router with the SSID and password from the old one?
Click to expand...
Click to collapse
believe me, i tried that. it's stupidly tedious to enter a long keyphrase via the remote control on our tivos and only slightly less tedious on the roku (its remote is much more responsive). laptops and phones aren't as bad since they have keyboards. apparently the devices are smart enough to notice a different MAC behind the BSSID. which if you think about it, is actually a GOOD thing in terms of security, since it makes spoofing a little more difficult. granted, you'd also have to know the wpa key to successfully spoof, but it's a simple check to implement for security's sake, and i'm glad they did.
by the way, do you like fjords?
Magamo said:
It's difficult to give tips for this, because everyones' usage is different. Get 'WakeLock Detector' and keep an eye on that when your power drain seems more intense. Disable things that make sense to disable based on that.
Click to expand...
Click to collapse
"Wakelock Detector" has certainly been enlightening. "Google Fit", which makes sense, once you think about it. But the other aspect that was even more important, I just happened to see when one of the other forums popped up on some sort of search result or other.
You have to boot your Android device on battery. If the kernel starts up on charger, it never gets into the deepest power-saving states. When I first started using Wakelock Detector, my phone showed up as being awake something like 97% of the time. Google Fit was the biggest user, but not that big. After seeing that advice I've been careful to boot on battery, and now most of the time is spent asleep. Google Fit still uses wakes as much, but when it's not, the phone is really sleeping. My normal battery life has moved out to two or three days, sometimes into a fourth. As long as I consider Google Fit worth having around, this battery life is good enough for me - there is always a decent window to recharge.
phred14 said:
You have to boot your Android device on battery. If the kernel starts up on charger, it never gets into the deepest power-saving states.
Click to expand...
Click to collapse
So much for that theory. A day or two back, after good battery life since this post, I noticed it draining faster. Today I looked, and sure enough, it's not going into deep sleep. I tried rebooting with all four states of wifi and cell service, and nothing has gotten deep sleep back. I think I'm going to try charging tonight, booting while charging, then rebooting after disconnecting. It would be good to have an exact and repeatable set of circumstances that cause both good and bad battery life.
When I selected "Calibrate now" after few seconds show up notification: "Network unavailable"
and next time will show: "Can't get a sea level air pressure reading for your location. Enter manually?"
Data/internet connection working on News, Weather apps. This behavior is same, WiFi or bluetooth connection.
Does anybody have any idea how to fix this bug?
SM-R760
Tizen Version 4.0.0.2
R760XXU2DSA1
deffyplus said:
When I selected "Calibrate now" after few seconds show up notification: "Network unavailable"
and next time will show: "Can't get a sea level air pressure reading for your location. Enter manually?"
Data/internet connection working on News, Weather apps. This behavior is same, WiFi or bluetooth connection.
Does anybody have any idea how to fix this bug?
SM-R760
Tizen Version 4.0.0.2
R760XXU2DSA1
Click to expand...
Click to collapse
Hi,
I had the same issue. Uninstalled the Wear application from phone and installed again.
Bingo..
Hope this helps.
I'm having this issue too. Ive tried reinstalling everything and resetting the watch. Nothing seems to be fixing it. Looking at the reviews of the alt-barometer app in the Samsung store seems to suggest the issue is widespread.
Have the same issue too. I think it's a problem of the defined server in the app which doesn't respond anymore. They should update the app...
Hi, i have exactly same problem after update to tizen 4.0. Have you some solutions?
Same problem , too. Last update 14.2.2019
I have noticed today at my job that I was at 188m, and when it worked I was less than 50m.
Same thing after reinstalling "wear", maybe worst, I didn't had backup
Same problem here after Tizen 4.0.
Same problem. Also affects Hiking Activity in S-Health on the watch. (It can't detect altitude so whole activity is broken showing "0km walked", "--" instead altitude and wrong calories). Tried every combination of reseting watch (with and without backup restore), reinstalling wear app and all plugins on phone and reinstalling altimeter app on watch. Even reflashed firmware via NetOdin. Also tried disabling adblock on phone in case some url gets blocked. No difference).
I'm also starting to think this have to do with predefined altitude server altimeter is contacting being down and not responding.
I had enough fiddling with this but if someone is determined they can try downgrade back to 3.0.0.2 to see if problem persist. Or try debugging the watch to see what is actually happening behind the calibrate request. Maybe even use packet sniffer.
SM-R760
Tizen Version 4.0.0.2
R760XXU2DSA1
BTU (UK) region
It must really be a widespread problem. The same here after the update to Tizen 4.0.2. I have made several hard resets of the watch, the only thing I have not done is phone hard reset. Not going to suffer this not knowing if it helps. I was solving more problems, so I have made several hard resets of the watch. For instance, SOME of the incoming calls were not vibrating on the watch. But after the first hard reset after the update the altimeter started working the second day I think!!! I thought it was really an issue connected with unavailibility of a server somewhere. I was solving more important issues, so I have made other hard resets and since then the altimeter jut won't work...
Same problem after upgrade to Tizen 4. Tommorow i trying downgrade to Tizen 3.
SM-R770
Tizen Version 4.0.0.2
Poland
I had the same problem. After several tries is now working. All I had to do was set the location to "high precision " on my phone (note 8) and after 4-5 times the watch will update automatically. Also I went outside.
I tried today and a get altitude measurement! I turned off and on my location on phone. But... I got lucky only one time. I tried 5 minutes later, and get "network unavailable"... Strange...
Problem
I have the same problem..
agawron91 said:
I tried today and a get altitude measurement! I turned off and on my location on phone. But... I got lucky only one time. I tried 5 minutes later, and get "network unavailable"... Strange...
Click to expand...
Click to collapse
I had the same experience today. At 1 a.m. of our local time (Europe) I got one calibration but since then - nothing. It makes me believe that the problem is not in our watches or phones but on the side of a server somewhere. Were they testing something?
It seems that reinstalling the app would help. I have done it, and for now it's all good
again, network not available , one or two updates and gone again.
Another +1 here - I have just discovered that my S3 Frontier is doing exactly the same thing. Uninstalling the companion app on the phone and reinstalling it hasn't worked for me, the intermittent nature of it (based on previous posts) would suggest some back end network issue at the end of whoever provides that data.
deffyplus said:
When I selected "Calibrate now" after few seconds show up notification: "Network unavailable"
and next time will show: "Can't get a sea level air pressure reading for your location. Enter manually?"
Data/internet connection working on News, Weather apps. This behavior is same, WiFi or bluetooth connection.
Does anybody have any idea how to fix this bug?
SM-R760
Tizen Version 4.0.0.2
R760XXU2DSA1
Click to expand...
Click to collapse
As I posted before, same happened to me the first time after the update to Tizen 4
I had to turn location to high accuracy and had to go outdoors, and after 4-5 tries the altitude is calibrated and working perfectly now. One thing I noticed is that you need to set your phone location on all the time with at least "device only" option.
GOTO_GOSUB said:
Another +1 here - I have just discovered that my S3 Frontier is doing exactly the same thing. Uninstalling the companion app on the phone and reinstalling it hasn't worked for me, the intermittent nature of it (based on previous posts) would suggest some back end network issue at the end of whoever provides that data.
Click to expand...
Click to collapse
Seems that the data is provided by the android location services, not by your data/wifi; in this case you need to have the location on with "device only", seems to solved my problem, BTW I havent noticed more battery drain than using "battery save" mode.
Seems that the data is provided by the android location services, not by your data/wifi; in this case you need to have the location on with "device only", seems to solved my problem, BTW I havent noticed more battery drain than using "battery save" mode.
Click to expand...
Click to collapse
Thanks for this tip - I missed your earlier comment so repeating it here again is useful and does seem to provide a work-around. Have a "Thanks" on me.
Since this is a recent change I wonder if Samsung got their device class confused and are trying to get the watch to aquire a "true" GPS fix rather than using the phone if available, but got it wrong with the latest build so now the watch has acquired a dependency it didn't have before.
My S3 has Wi-fi (but turned off) and no carrier / network (ie mobile phone) support and that used to work perfectly well with my phone's location services set to "High Accuracy" over the Bluetooth link which should surely be enough for any non mission critical consumer device since that uses network location, Wi-fi and GPS. I can see why someone might want a high degree level of accuracy on their watch but then surely the watch should be acquiring GPS itself which is why I wonder if Samsung were trying to be smart and got their wires crossed.
I will check out the battery usage implications of restricting my location to GPS at a later date, but I am mostly indoors and a) don't use the altimeter all that much and b) won't get much of a GPS fix in the concrete and steel bunker that is my office so I am expecting it to be an absolute battery sucker.
Thanks again for the tip about changing the location services on the phone.
GOTO_GOSUB said:
Thanks for this tip - I missed your earlier comment so repeating it here again is useful and does seem to provide a work-around. Have a "Thanks" on me.
Since this is a recent change I wonder if Samsung got their device class confused and are trying to get the watch to aquire a "true" GPS fix rather than using the phone if available, but got it wrong with the latest build so now the watch has acquired a dependency it didn't have before.
My S3 has Wi-fi (but turned off) and no carrier / network (ie mobile phone) support and that used to work perfectly well with my phone's location services set to "High Accuracy" over the Bluetooth link which should surely be enough for any non mission critical consumer device since that uses network location, Wi-fi and GPS. I can see why someone might want a high degree level of accuracy on their watch but then surely the watch should be acquiring GPS itself which is why I wonder if Samsung were trying to be smart and got their wires crossed.
I will check out the battery usage implications of restricting my location to GPS at a later date, but I am mostly indoors and a) don't use the altimeter all that much and b) won't get much of a GPS fix in the concrete and steel bunker that is my office so I am expecting it to be an absolute battery sucker.
Thanks again for the tip about changing the location services on the phone.
Click to expand...
Click to collapse
My S3 is exactly the same as yours, and I dont have wifi or GPS on either, it gets the location straight from the phone, I checked it and when I go to altitude on my watch I can see that the icon of "searching location" goes on in my phone.
I am pretty sure that the GPS of the watch doesnt work by itself because I use it to run everyday (with my phone) and is tracking the metrics and altitude just well, also the location is locked and working, I run 5kms per day and I get 3 and a half days of battery and when I run with the watch alone I can get 1 and a half day (cause GPS and Spotify).
BTW, where I live/work there are no high structures or buildings miles around, maybe it means faster location.
Regards.
I found solution that help me in reddit: "Switch on "location history" in Google account. Should help"