Database Users

[TIP] GPS Issues Workaround

Obviously Samsung has no idea how to write proper drivers for Android phones running the QSC6085. I found a workaround that fixes any issues with GPS.
It's completely simple, turn off WiFi and 4G when you're trying to get a lock.
Proof 1: I stood outside in broad daylight with clear skies connected to my home's WiFi network. Using GPS Test, my phone discovered 12 satellites and made 0 connections for 3 minutes. I closed the app, disabled WiFi (used 3G) and I got a lock of 4 satellites within 15 seconds and 6 - 8 after another 15 seconds.
Proof 2: I left my house and went straight from WiFi to 4G. I got in the car and turned on Google Navigation. I set it to my destination and waited for a lock. After a minute I turned off 4G and got a lock within 15 seconds.
THIS PHONE HAS NO MAJOR GPS ISSUES. Obviously these are simple bugs and I have no doubt in my mind that Samsung is aware of these and will fix them in the next update.
Other GPS bugs I've noticed:
No matter how many satellites I have locked on, my accuracy has never gone below 30 meters.
SNR numbers are really low. According to a leaked ROM for the Vibrant, this can be fixed.

K.. I checked your tips..
3g only[Inside Apt] -- floats between 7 and 8 sat and usually 6-7 locks
Wify Only[Inside Apt] -- Solid 9 satalites and 7-8 locks
4G[no wifi] : stopped with 4 sat and 4 locks but I noticed that my 4g likes to sleep

Yes, it seems that when using WiFi, that updated ephemeris data is not being transmitted, however, it's not bulletproof - after a day or so, it'll try to lock, the 3G connection will go dormant, and it'll just sit there...

I have three epics and have been working with *#1472365# settings and testing for about a week.
I am concerned you maybe getting a false positive on repair of the main problem until you confirm, with no resets and further changes to *#1472365# (which reset the cache) that 24 hours later and in a diffident position you do lock most sats Epic sees.
There are a dozen things you can do to flush out the xtra data cache, just none that I have found that persist and to it regularly (ideally with a couple hours at most for ephmeris, and a day o r two for alamanc). Most proper aGPS implementation will also give the device a minute on warm/hot start, and if is seeing and not locking, grab new assistance data from the best source (first choice network, second birds)
I do think sammy is teid itself up in knots with drivers because of the many different agps environments Galaxy S is sold in. It goes way beyond GSM v CDMA, but also even bigger considerations, like agps data source adn methods, and even whether the device is in a unlimited data carier environment (like our epics) or not.
have you done any testing with the xtra settings themselves? seems to me that is where the rubber hits the road?.

aero1 said:
have you done any testing with the xtra settings themselves? seems to me that is where the rubber hits the road?.
Click to expand...
Click to collapse
The only change I've made with my phone's *#1472365# settings is setting it to Cold Start to save battery. I know in testing builds of the Moment aGPS addresses were set to internal testing ones that didn't work.

No problem with GPS here. I use Navigation and CoPilot and both pick me in seconds. Navigated from the mechanics workshop today just to test it out and worked like a charm. Guess some have it and some don't.

yes me too, and further, with speedtest app, the only way i can get it to lock on a server that is near me is to have wifi on when I start the app, then it locks on my server, otherwise, it has me 1500 miles away as closest server.

LordLugard said:
No problem with GPS here. I use Navigation and CoPilot and both pick me in seconds. Navigated from the mechanics workshop today just to test it out and worked like a charm. Guess some have it and some don't.
Click to expand...
Click to collapse
No, we all have the same bug and Sprint Device team is trying to get samsung on it.
You just haven't been in a condition where it occurs, whcih is turning on GPS in a different location say 8 hours later absent flushing the cache.
The Epic doesn't properly check the cache for staleness, so everyone who uses GPS will come up on this problem eventually. It is a bug Samsugn has had before.
arashed31 said:
The only change I've made with my phone's *#1472365# settings is setting it to Cold Start to save battery. I know in testing builds of the Moment aGPS addresses were set to internal testing ones that didn't work.
Click to expand...
Click to collapse
the reason why I am asking is Epic has in that debug menu are setting to set time for attempts as well as flushing the cache manually. It would be interesting if we could get that going.
the reason I say so is cold start is a good workaround but it will murder GPS TTFF (time to first fix) in non network conditions. It will make it worse than standalone. Literally every time you start it will be a cold start and you will have to wait for almanac, which is 5 to 15 minutes if outside of network coverage. That is what I am seeing with cold workaround. I am still playings with forcing warm
Are you seeing that? with cold stat set, enable airplane mode, restart Epic, restart GPS and see what happens.

arashed31 said:
I found a workaround that fixes any issues with GPS.
It's completely simple, turn off WiFi and 4G when you're trying to get a lock.
Click to expand...
Click to collapse
This method did not save me today, when after letting my Epic's GPS go unused for > 24 hours I tried to get a lock with WiFi and 4G disabled. Multiple satellites were visible, but only two were used. Gave up and rebooted. After which, almost immediately, I got 8 out of 9.

boomerbubba said:
This method did not save me today, when after letting my Epic's GPS go unused for > 24 hours I tried to get a lock with WiFi and 4G disabled. Multiple satellites were visible, but only two were used. Gave up and rebooted. After which, almost immediately, I got 8 out of 9.
Click to expand...
Click to collapse
Yes I think the OP got hit with what hit us in all testing. That is why i am doing careful controlled tests. Since the main issue has to do with failure to consistently and properly remove expired and invalid assistance data cache lots of things may be removing that cache, for example any changes to that cause a reset.
Right now the only consistent way to remove it without user intervention is to go into the debug and set as cold start. The problem with that is it introduces a new problem affecting standalone TTFF, ie once you get outside of data range you will do worse TTFF than dedicated handlheld GPS units that keep almanac in ephemeris.
This problem is akin to some condition where the phone will freeze and not make calls if you don't use it in 24 hours but most people didn't realize there was a time consideration. 90% of the people would be saying there is no bug or that they have a fix.
to test any fix you have to:
get a gps location.
not use GPS for 12 hours or move location significantly.
do not reset or action that inadvertently fushes cache.
test again.
In every case and attempted workaroudn with this test but cold start hack I cannot get a gps fix on any of our three epics.

@aero1,
The complication in my last case is that I was in Cold Start mode. Maybe I just didn't give it enough time.
Sent from my SPH-D700 using XDA App

boomerbubba said:
@aero1,
The complication in my last case is that I was in Cold Start mode. Maybe I just didn't give it enough time.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Cold start set in *#, data connection on, clear sky and no fix within 30 seconds? Please say it isn't so.

aero1 said:
Cold start set in *#, data connection on, clear sky and no fix within 30 seconds? Please say it isn't so.
Click to expand...
Click to collapse
That's the setting alright. I think at first I had 4G enabled when I started GPS Test. But the first thing I did was disable it, thus defaulting to 3G, with GPS Test still running.
But it's possible I didn't give it enough time to lock. I was in my car and perhaps too impatient. I may have given up and rebooted after less time than that.
Since then I have left Cold Start set, and have not experienced a no-lock error condition again. But I have rebooted a couple of times for other reasons. When I started my commute home this afternoon and started GPS Test, it was slow to lock but it came around to a full lock in a minute or so.

I've been using the GPS quite a bit this past week. I've had no problems getting a fix except for onces. It was due to the typical bug (find satellites but not connect). I went into the GpsTest shortcut and set it to Hot Start then back to Cold Start. Immediately the GPS started working again.
Switching back and forth clears the GPS cache and fixes this issue. To me, that's the only problem this phone has. As far as I know, this can be an INCREDIBLY EASY fix if anyone can go into the source and put in a way to periodically clear the cache.

time keeps changing

My tab(unrooted) has an issue where the time keeps going back by an hour. All of my time setting are OK. Any one else have this issue or know a possible fix

You probably don't have your timezone set right. Set it and you should be golden.

I've ckecked and double checked my time zone. It is correct
Sent from my Nexus S using XDA App

Does the hour change or the minutes?

I had time issues with both my Tabs, despite setting the correct time zone on startup. No amount of fiddling seemed to correct it.
Then I installed a program called ClockSync from the Market. Its a free app. It can automatically fix the time setting if you're rooted (and keep you in sync), or guide you how to do it manually if you're not rooted. Once I used this program to get my settings correct, I've been right as rain since.

Sorry, I just started a new thread, I don't know if our issues are the same -
http://forum.xda-developers.com/showthread.php?t=1140873
Mine shows an hour different in certain things. The clock doesn't change by an hour, some things appear to use GMT and some BST...

Incorrect Clock/Time After Hibernation

Hi,
I checked the web on this issue and have found it being reported on other sites but I can't seem to find the resolution, if there is one....
I received my Nexus 4 last Friday. Been digging it ever since. I came from the SG2 Skyrocket on att. I realized how much I miss the pure Android experience on a phone without the carrier's bloatware and manufacturer software.
however during the Super Bowl, my buddies and I discovered a weird bug on the phone. Upon waking up from a "long" hibernation, my time/clock is off by 20-30 minutes. Once I reboot the phone, the time is corrected. However, it's kinda weird waking up in the morning, my bedside clocks displays the correct time but when i wake up my phone, the time/clock is incorrect.
Has anyone experienced this? Does anyone know the resolution??
Much thanks..........

It happened to me once or twice before on my N4 stock/rooted. What is your setup under Settings>Date and Time ? Sometimes when you have Automatic date & time and Automatic time zone enabled and you are out of mobile network service, the time doesn't get updated until your phone mobile connection is restored. In my opinion, this behavior smells like a bug. Post a screen shot of that settings page if you could....

Hash_Map said:
It happened to me once or twice before on my N4 stock/rooted. What is your setup under Settings>Date and Time ? Sometimes when you have Automatic date & time and Automatic time zone enabled and you are out of mobile network service, the time doesn't get updated until your phone mobile connection is restored. In my opinion, this behavior smells like a bug. Post a screen shot of that settings page if you could....
Click to expand...
Click to collapse
Hi Hash,
Thanks for the feedback. I went into the settings, as you directed, and see that both Automatic date & time (use network provided time) and Automatic time zone (use network provided time zone ) are both checked.
I will try and take a picture tomorrow morning for, again, it was weird looking at my cell phone which says 5:35am when my bedside clock showed 6:00am.
Schwacker

My Issue with Pictures
All,
To document what is happening to my phone, I am attaching pictures to this post. The early morning picture post, I had my Wifi turned on. After the pictures were taken, I turned off WiFi an let it go int hibernation until I woke up at 6am. As you'll see in the second picture, my time/clock was way off.
I am using Beautiful Widgets for the clock but can't see that causing my issues.
Any thoughts? Hate to return the phone for I'm really loving it but don't want the phone if I can't depend on the time!
Thanks!

Schwacker said:
All,
To document what is happening to my phone, I am attaching pictures to this post. The early morning picture post, I had my Wifi turned on. After the pictures were taken, I turned off WiFi an let it go int hibernation until I woke up at 6am. As you'll see in the second picture, my time/clock was way off.
I am using Beautiful Widgets for the clock but can't see that causing my issues.
Any thoughts? Hate to return the phone for I'm really loving it but don't want the phone if I can't depend on the time!
Thanks!
Click to expand...
Click to collapse
Have you tried the stock clock to see if Beautiful widgets is the issue. Try that first. Next thing I would try is to leave WiFi on during sleep and see if the issue is fixed. I would expect to have some lag after a wakeup for the clock to update but no more than 15 seconds. Good luck.

grubbster said:
Have you tried the stock clock to see if Beautiful widgets is the issue. Try that first. Next thing I would try is to leave WiFi on during sleep and see if the issue is fixed. I would expect to have some lag after a wakeup for the clock to update but no more than 15 seconds. Good luck.
Click to expand...
Click to collapse
Thanks Grubbster -- I have to admit and I'm somewhat embarrassed in doing so, I couldn't figure out how to use the stock clock on my home screen and when I couldn't figure it, I thought "hey, I purchased Beautiful Widgets...I'll just add that clock to my screen....".
FYI -- I have always left my wifi on during the night and into hibernation. Last night I had the brain child thinking maybe it's the Wifi that is causing my delays for when I first noticed the time issue on Sunday, it was while I had my Wifi on....so I thought I'd turn it off to see if the time would be correct......freaking weird....

Schwacker said:
Thanks Grubbster -- I have to admit and I'm somewhat embarrassed in doing so, I couldn't figure out how to use the stock clock on my home screen and when I couldn't figure it, I thought "hey, I purchased Beautiful Widgets...I'll just add that clock to my screen....".
FYI -- I have always left my wifi on during the night and into hibernation. Last night I had the brain child thinking maybe it's the Wifi that is causing my delays for when I first noticed the time issue on Sunday, it was while I had my Wifi on....so I thought I'd turn it off to see if the time would be correct......freaking weird....
Click to expand...
Click to collapse
The stock clock is a widget. Just go into your widgets, long press the clock, and drag it to your home screen. Also, does the clock in the status bar show the correct time when waking up?
Check your beautiful widget app settings to see if there is anything related to updating system settings. Maybe a frequency (10 min, 15 min, etc.) that needs to be changed.

grubbster said:
The stock clock is a widget. Just go into your widgets, long press the clock, and drag it to your home screen. Also, does the clock in the status bar show the correct time when waking up?
Check your beautiful widget app settings to see if there is anything related to updating system settings. Maybe a frequency (10 min, 15 min, etc.) that needs to be changed.
Click to expand...
Click to collapse
Ok. Thanks -- duh -- there it is. I'll try this for a day to see if this will resolve the issue.

This has happened to me once, on Faux's kernel. It was my first time ever undervolting my device, and I undervolted by -100 mV (fast binned chip). It did it twice, and both during deep sleep. But the time corrected itself once I go into Settings > Date & Time and unchecking-and-rechecking the Auto Time setting.

Do you use a task killer?

Michealtbh said:
Do you use a task killer?
Click to expand...
Click to collapse
No. No task killer....though I have to admit....I was discussing my issue with a fellow phone geek. He believes my 2 options are: if it's an internal hardware issue, I'll need to get a new phone if it loses connection to the antenna which connects to my att network for the time/clock. Or if it's a software issue, then maybe a flash can resolve it.
I'm also going to contact Google later today and see what my return options are if, by tomorrow, I'm still experiencing this..
Thanks...

[Q] wrong date time every morning

Hello
I have my G2 for 3 days now, and I keep having the same weird problem every morning when I turn it on: the clock "looses" one day, and either advances or loses a few minutes.
Yesterday I checked as the hour went past 00h and the date changed to day 19, thursday ('I'm on GMT 00). The phone and computer had the same time.
I left my phone off during the night, and today when I turned it on I found it at 10.00 o'clock (8 minutes in advance of my computer). It also switched back to the 18th, wednesday. The weather/time app still detects it was last updated on the 19th.
I have automatic date-time-timezone switched off. If I turn it on, it will sync with the Internet and correct the hour, but that does not fix the problem.
Any ideas on what's happening? Any suggestions?
I'm on Android 4.2.2
Kernel 3.4.0
Software D80210b-EUR-XX

Yesterday (after midnight) I switched the phone off for more than 10 minutes, switched back on: all ok
Restarted the phone: was ok - up till 3 am the date/time was correct.
Turn it off, woke up this morning, turned it on: 5 minutes delayed, date went back to the 19th.

It seems what is happening is not really a lost of time. Today as I turned the phone on, it was showing 10:24, 20th (yesterday). This was over half an hour ahead of correct time. This happened after I had the phone off for 3 hours, so it's not a delay that increases as proportional to the time the phone is off. It must have something to do with some date/time on the settings, that override actual date/time.
I think this is like a "return to last settings", in this case, I believe this was the date/time set when I turned the phone on yesterday morning.
I already went by all apps I think could be related, but I can find no relevant option to prevent this.

That is indeed strange, maybe someone else around here can help you with that.
I don't think many people turn their phones off during the night.

Hi i think this is the same for all g2, my phone does the same thing once you turn it off the device is literally off. I am sure if you check the battery time it will show only from the time you rebooted it and not from last full charge. At the beginning i reported this issue but didn't get any reply but with further investigation i reached to the conclusion it wasn't an issue with device.
Any way regarding date time issue, you can simply make sure its automatically synchronized with network that way no matter whether its on or off it will be correct.
Sent from my LG-D802 using xda app-developers app

its probably cmos battery if phone has one, try warrantee

Thank you for your input
I've done a few more tests. I've flashed a different firmware, but it still does the same. This originally came with 10B-SEA, and I flashed it to 10B-EUR (UK open). Now it's back to SEA.
I've contacted LG about this, and they told me it's under analysis.
The phone will not loose date and time if it's powered off for one hour. After two hours it will happen and it will go back to the last time the phone was powered on and the clock was set.
I've been keeping it synced with the network time, and that way it works fine, but that's not a permanent fix. Yesterday I unchecked the automatic time, left it powered off for two hours, and it went back to monday.
I've read this post http://forum.xda-developers.com/showthread.php?t=2580974, and it seems to be related.

Same problem with date and time
I do have the same problem. My phone model is D802 (international variant). But as far as I remember, this issue did not start from the day one. I purchased the phone some 2 months back. It was fine on the JB. It remained fine even after the KitKat update. But one day, my phone did show some weird problems. Serious lag coupled with overheating and battery drain. I did a factory reset because the phone was hardly usable at that point. After the reset, lag + overheat and battery issue was gone, but I remember that after that incident, it started this weird date/time sync issue. There is something which I wish to highlight by the attached screenshot. There is always a broken curve of battery usage whenever the date/time reverts which happens whenever you keep the phone switched off for a few hours. I am not a technical person, but this might be related to the battery.

Anyone have any luck with this? The main problem that this is causing is that when emails, texts, messages come in whilst the clock is incorrect (before it updates), these items get put out of sync with when they did actually arrive.
I contacted LG and they said...
If you have both options ticked, I would advise you to try and perform a hard factory reset. Before doing the reset, please ensure that you back up all of your files as all data will be lost during the reset. The details of the reset are as follows:
Turn the phone off
Press and hold the power key and the volume down key together
Release the power key only when the LG logo appears and immediately press and hold it again
Release both keys when the hard factory screen shows up
Select yes (use the power key to select yes)
Select yes again
This will then take you through the set up of the phone, and the issue should be resolved. I hope this helps you.​
I haven't yet tried this, as from what I've read elsewhere, this wont fix it, plus it is a bit of a hassle to copy everything off and then reset, then et everything back on the way it was and all apps, etc.

Hi,
I've the same problem.
Can you tell me if Hard factory reset or LG support had resolved this issue?
I'm currently using ClockSync app that sync time every 3h and at boot.
The clock seems not to be very accurate : 1.139s of local offset in 2h...
I've tested the Clock_offset_fix. I'll update this post when I'll be sure that this solution is ok for me or not...

pbenoit said:
Hi,
I've the same problem.
Can you tell me if Hard factory reset or LG support had resolved this issue?
I'm currently using ClockSync app that sync time every 3h and at boot.
The clock seems not to be very accurate : 1.139s of local offset in 2h...
I've tested the Clock_offset_fix. I'll update this post when I'll be sure that this solution is ok for me or not...
Click to expand...
Click to collapse
This is not an issue per say. It's just that the device is built this way..... So as far as I know there is no fix to this. Except you can have accurate date and time if you have a sim card in the device and auto date&tme option is ticked in settings. You see the device doesn't have a pc like cmos rom to store basic info like date and time. So when u turn off the device that info isn't maintained and becomes corrupted after some time but it is corrected when synchronized with the cell network provider at boot.

Hi, I have the same problem. is there any way to solve this problem? I have stock lolipop.

გიორგი said:
Hi, I have the same problem. is there any way to solve this problem? I have stock lolipop.
Click to expand...
Click to collapse
Same problem for me, date and time are wrong for some seconds after boot.
Than it switch correctly to the current date and time.
Make sure you have setting > date and time > automatic sync for all options...
On my phone it start wrong than it correct itself if internet is enabled.
The problem ia when mobile data is OFF. :'(

4Freedom said:
Same problem for me, date and time are wrong for some seconds after boot.
Than it switch correctly to the current date and time.
Make sure you have setting > date and time > automatic sync for all options...
On my phone it start wrong than it correct itself if internet is enabled.
The problem ia when mobile data is OFF. :'(
Click to expand...
Click to collapse
Yes, I have automatic sync on, but the problem is when I can't access internet. What if I install Cyanogenmod?

გიორგი said:
Yes, I have automatic sync on, but the problem is when I can't access internet. What if I install Cyanogenmod?
Click to expand...
Click to collapse
I am on Temasek now, same problem.
I'll try Cyanogen CM13 M1 this night or tomorrow.
Hoping

Time resting to 2010, affects internet not working

Hi, I have the small 8 inch screen Amazon fire tablet (2 years old, now out of warranty)
A few months ago i noticed that the tablet was resetting the time back to the original factory setting of January the 1st, 2010 sometimes, This affects synching with the wi-fi internet, so webpages do not display. as its says clock time is not correct.
When this happens I have to go to device options, then date and time setting and reset my time zone, and then shutdown tablet and switch it back on to synch with wi-fi. The tablet then works fine with the internet for a few days then it loses the correct time and date.
neither puting settings on select time zone or automatic time zone sorts the problem, as after a few days its back to 2010 (original factory setting).
This problem happens, no matter if tablet battery is needing recharging or has plenty of power, or if wi-fi is on or off, it just seems it lasts a few days at the correct date and time, then it reverts to 2010.
Any solution to this. I know I can keep adjusting date and time by above method, and then reboot the tablet back up, but wondering if there is a reason why the tablet is reseting date and time, and is there a solution?

colin2x2 said:
Hi, I have the small 8 inch screen Amazon fire tablet (2 years old, now out of warranty)
A few months ago i noticed that the tablet was resetting the time back to the original factory setting of January the 1st, 2010 sometimes, This affects synching with the wi-fi internet, so webpages do not display. as its says clock time is not correct.
When this happens I have to go to device options, then date and time setting and reset my time zone, and then shutdown tablet and switch it back on to synch with wi-fi. The tablet then works fine with the internet for a few days then it loses the correct time and date.
neither puting settings on select time zone or automatic time zone sorts the problem, as after a few days its back to 2010 (original factory setting).
This problem happens, no matter if tablet battery is needing recharging or has plenty of power, or if wi-fi is on or off, it just seems it lasts a few days at the correct date and time, then it reverts to 2010.
Any solution to this. I know I can keep adjusting date and time by above method, and then reboot the tablet back up, but wondering if there is a reason why the tablet is reseting date and time, and is there a solution?
Click to expand...
Click to collapse
Almost certainly a hardware or battery fault. Given age of device I suspect the latter is experiencing a spontaneous voltage drop which resets the clock. Not much you can do about that short of replacing the battery.

Thanks, how long should the rechargable battery last in it, as two years seems very short.

colin2x2 said:
Thanks, how long should the rechargable battery last in it, as two years seems very short.
Click to expand...
Click to collapse
Lots of variables; 2 years is not out of the question depending on how it was used and stored. Battery quality/consistency isn't the best on these value oriented Fire devices.

OK thanks, I will just suffer the problem for a few more months by keep resetting time and date when needed, and I will buy the bigger screen Amazon Fire tablet latter this year.