Related
Hello good people
I've had my I9000 for a couple of weeks now, and recently flashed it to JP3
At the version screen it says exactly:
PDA: I9000XXJP3
Phone: I9000XXJF5
CSC: Unknown
Build info: 2010, 07
The issue is that my phone follows a time on it's own. A couple minutes ago I set the time to 01:40. It's now 02:10, but my phone shows 02:05. After a few hours I suddenly find it 30+ minutes behind...
Here's the kicker though, I flashed it to JP3 to improve performance, but the damn clock is lagging. So I've voided the warranty, and my top of the line 1ghz smartphone can't even keep show me the right time.
Please.... help, I'm begging...
Go settings --> Date and Time. If automatic is ticked then untick it and set the time manually.
It's unticked, and I've manually set the time
Highfall said:
It's unticked, and I've manually set the time
Click to expand...
Click to collapse
Does it do the same thing if it's receiving it's time update off the internet?
psychoace said:
Does it do the same thing if it's receiving it's time update off the internet?
Click to expand...
Click to collapse
Yes, I've tried that too. When I set it to "automatic" and connect to the internet, the time doesn't correct itself, or even change. I've tried giving it some time, but it doesn't sync. Same issue, same lag. Even if it did fix, it would just be temporarily. I'd like to have it show time accurately even when it doesn't have access to the internet.
flash a new firmware, you can always go back to your old firmware anyway if you have to return it.
(i assume it was working fine before flashing)
Kilack said:
flash a new firmware, you can always go back to your old firmware anyway if you have to return it.
(i assume it was working fine before flashing)
Click to expand...
Click to collapse
I'll try flashing to JP2, jp3 has given me nothing but trouble.
Do I just follow the same procedure or is there another way of downgrading to a previous firmware?
Most of the previous firmwares can be gotten from Samsung-Firmwares website.
JG5 was a good stable version.
JM2 is the next best thing.
Sheesh, just flash back (JM2 or JG5)...
You flashed some ultra beta/alpha firmware and now complain the phone isn't working properly? Not really honest.
From what ive been reading this is an issue with JP3, it really bugs me why such issues still exist these days, my Nokia 5800 also had an alarm bug.. its not really the same issue but a related one.
EarlZ said:
From what ive been reading this is an issue with JP3, it really bugs me why such issues still exist these days, my Nokia 5800 also had an alarm bug.. its not really the same issue but a related one.
Click to expand...
Click to collapse
It is a beta (if that, perhaps even alpha) release. Quit whining about it, you haven't voided your warranty because there is no evidence of you ever doing something to it. If you flash an older firmware to it there is no history of different firmwares that have been installed.
BTW, I'm on jp3 and have no such issue with automatic time adjustment.
I'm on the stock firmware and have the same issue. The other problem with this is that the alarm not always going off! So I have to use the alarm in my iPhone!!! How ridiculous is that?!
Sent from my GT-I9000 using XDA App
The android 2.2 firmwares do definitely lose track of time. Probably a broken network time implementation (time for phones come from your carrier's atomic clock) that doesn't sync properly or something.
Android 2.1 firmwares don't have this problem.
exstarosta said:
I'm on the stock firmware and have the same issue. The other problem with this is that the alarm not always going off! So I have to use the alarm in my iPhone!!! How ridiculous is that?!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
During the time in question, if you ever used a task killer, make sure you the alarm clock on the ignore list.
I initially had a problem, I think only once but maybe twice, where the alarm didn't go off. As far as I could tell, I think I used a task killer and killed the alarm clock, so since then I've had it on the ignore list and haven't had any issues. If you think this might be the issue, give it a week long test using dual alarm clocks.
exstarosta said:
I'm on the stock firmware and have the same issue. The other problem with this is that the alarm not always going off! So I have to use the alarm in my iPhone!!! How ridiculous is that?!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Are you using a custom lockscreen? I found that the ICE lockscreen caused that issue for me. But otherwise, I've been using JG5/Modaco for a long time now, am using the standard lockscreen, and been using the alarm twice a day for 3 days now, and it's always gone off..
And I don't use task killers, but alovell83 is probably correct
dekeijzer said:
you haven't voided your warranty because there is no evidence of you ever doing something to it. If you flash an older firmware to it there is no history of different firmwares that have been installed.
Click to expand...
Click to collapse
That, and generally, they don't care (unless you burnt out your CPU doing stupid stuff like overclocking, but most CPU's have thermal controls these days to help prevent that). But be aware, that if it is strictly a software issue, regardless of whether they care or not, you will possibly be charged (because no fault found), which is what happens with Apple.
That being said, just in case, I would suggest flashing back to the original firmware if there is an issue anyway, because there is subtle differences between many of the firmwares (and it's difficult to differentiate between beta and final ones)
alovell83 said:
During the time in question, if you ever used a task killer, make sure you the alarm clock on the ignore list.
I initially had a problem, I think only once but maybe twice, where the alarm didn't go off. As far as I could tell, I think I used a task killer and killed the alarm clock, so since then I've had it on the ignore list and haven't had any issues. If you think this might be the issue, give it a week long test using dual alarm clocks.
Click to expand...
Click to collapse
I do have a task killer and I have the clock/alarm on ignore list. But it didn't help at all. In the evening I restarted the phone and didn't use the task killer and in the morning the alarm didn't go off.
andrewluecke said:
Are you using a custom lockscreen? I found that the ICE lockscreen caused that issue for me. But otherwise, I've been using JG5/Modaco for a long time now, am using the standard lockscreen, and been using the alarm twice a day for 3 days now, and it's always gone off..
And I don't use task killers, but alovell83 is probably correct
Click to expand...
Click to collapse
No, I don't have a custom lock screen, just the stock one.
I am really starting to think about this phone as piece of junk. The Froyo update propably will fix some issues, but it will definetaly bring a lot of new ones....
exstarosta said:
I do have a task killer and I have the clock/alarm on ignore list. But it didn't help at all. In the evening I restarted the phone and didn't use the task killer and in the morning the alarm didn't go off.
No, I don't have a custom lock screen, just the stock one.
I am really starting to think about this phone as piece of junk. The Froyo update propably will fix some issues, but it will definetaly bring a lot of new ones....
Click to expand...
Click to collapse
Perhaps it's best if you post a list of apps you jhave installed (maybe using Appbrain).
I've been using my alarm to remind me to take the medicine for my ear-infection, and it's been fine, and perfectly reliable.
dekeijzer said:
It is a beta (if that, perhaps even alpha) release. Quit whining about it, you haven't voided your warranty because there is no evidence of you ever doing something to it. If you flash an older firmware to it there is no history of different firmwares that have been installed.
BTW, I'm on jp3 and have no such issue with automatic time adjustment.
Click to expand...
Click to collapse
Just to let you know, i dont have an SGS yet. ETA for those handsets in my country is still late august to late september or even first week october
Excuse me but this, as already have been said, is a known issue with JP3 firmware and there is a fix for that. If you read through the forum you'll find the answer.
The "solution" is to root your phone and then install clock sync, to sync every few hours...
Hey guys,
So as an attendee to IO, I got a 10.1 tab; only problem is it was using the European time zone and for whatever reason used my google account settings which told it to automatically pull down the time from the servers (which would then report an incorrect time due to the incorrect time zone). I guess there's some kind of bug in the settings for the tab as it's missing the option to turn off automatic time, so I was left with a tab that had the incorrect time and could not be set.
So I wrote an android app that manually over-rides the automatic time setting, and it worked like a charm. If anyone else out there is having this issue, I have an apk file on hand that you can use to unlock your tab's time. Just make a post here and I'll try and get back to you asap.
I'd love to get that .apk. Thanks for your work!
Thanks for the fix. I bet most of us here still don't have the device yet, to benefit from your work. But we would appreciate if you could post your impressions about the device
i would love to get my hands on that I was frustrated at this unfortunate bug :-/ luckily during the conference it was the right time but now I need east coast time.
Apparently you can wipe to fix it but would rather not
I had this problem as well.
It is a bug in the pre-release software supposedly. You can download timezone changer from the market to fix.
https://market.android.com/details?id=com.futurek.android.tzc&feature=search_result
Mine worked well until I attached the tab to Exchange. At that point it switched to GMT and locked me out of the setting. The Time Zone Corrector seemed to fix the problem.
I hope that 3.1 update comes as soon as they indicated it would... I don't know if I'm optimistic about it though.
Ah OK there you go. Interesting bug though, it didn't happen to a friend who got a tab as well, so some of you might be fine.
Could use apk, if its still available. Thanks
Well I need to make 8 posts to post a link... so you're going to have to make this link for yourselves:
http : // appliedanalog . com / downloads / SetTime . apk
All this program does is disable automatic time zones and clocks on your device.
http://appliedanalog.com/downloads/SetTime.apk
FTFY
Edit: Awesome, thank you so much for the unlock of automatic time zone. worked perfectly.
kentoe said:
http://appliedanalog.com/downloads/SetTime.apk
FTFY
Edit: Awesome, thank you so much for the unlock of automatic time zone. worked perfectly.
Click to expand...
Click to collapse
Worked great for unlocking but I notice the time zone still resets every time you reboot. Is this the same for everyone?
I think there is an easier way, with a non-apk to do it. When I was going through the settings, i ran across an area to set locale. Since I didn't have to change the locale (PDT), I didn't go into the settings. If I can find it again, I'll post where it is.
N/M. The locale setting I saw in the samsung apps, you can reset the locale on it, but it doesn't do anything.
thepro8 said:
Worked great for unlocking but I notice the time zone still resets every time you reboot. Is this the same for everyone?
Click to expand...
Click to collapse
This didn't happen to me on reboot :-/
thepro8 said:
Worked great for unlocking but I notice the time zone still resets every time you reboot. Is this the same for everyone?
Click to expand...
Click to collapse
If it is resetting (I've not tried this on mine) it'll be because it is pulling the time down from online. I ended up doing a factory restore today to fix the time zone.
On a separate issue I was having a partial success using XJNB to sync files with my Mac (see my 'first impressions' blog post post at surfsoftconsulting.com) but since the factory restore this has stopped working completely.
Other issues I have noticed:
Samsung browser is still very buggy compared to the vanilla Android browser. It crashes less than the one on the Galaxy Tab 7" but frequently fails to redraw large areas of the page when scrolling.
Using the camera forces bluetooth to be turned off.
Plugging the Galaxy Tab into a computer for sync forces bluetooth to be turned off.
Can't mount the (virtual) SD card as a drive on the computer you plug the tablet in to - you can only use the (buggy) MTP implementation called 'Kies'.
On the plus side:
Stock keyboard (not the default Samsung one) is good, I can almost touch-type.
I watched about 4.5 hours of DivX video and played about 3 hours of music during my 10 hour flight back to the UK and the battery was still 35% full on landing.
Thanks for the fix! I thought I was going crazy!!
kentoe said:
http://appliedanalog.com/downloads/SetTime.apk
FTFY
Edit: Awesome, thank you so much for the unlock of automatic time zone. worked perfectly.
Click to expand...
Click to collapse
Same. Thanks a ton.
Hi guys and girls,
Been using WP7 about a week now and one niggling little issue is doing my head in. Sorry if it has been mentioned before or is covered under some other issue, I did try a search and got nothing relating to it.
My issue; the clock on the phone keeps jumping to random times.
I am using YukiXDA latest build and could find nothing relating to this isue there either.
Would like to know if others have had this problem and what have they tried to remedy it?
Is it a ROM issue or is it a hardware issue?
Okay, An update
This is happening when I reboot the device.
Is there something in settings that I am missing, or is there a registry setting I can change?
do you have your "date & time" settings set automatically?
Yes
bleui said:
do you have your "date & time" settings set automatically?
Click to expand...
Click to collapse
Yes time setting is automatic, even tried setting it in the registry.
It got that bad yesterday my phone reset itself to Jan 1980.
It sounds like the battery *may* be ****ed up, I have no idea about the htc hd2 (I've only had mine for a couple of months), but on my old phone(s), some of them have had that "time resetting" too, and the people at the tech support said the battery needed to be replaced.
Sorry for hijacking your thread:
I have a similar error with my phone (yukixda v4):
If I send myself a text message at say... 01:35... it's sent 01:35, but the one i recieve has the timestamp at 01:34... this is both with and without automatic time settings..
any ideas?
h0ng said:
It sounds like the battery *may* be ****ed up, I have no idea about the htc hd2 (I've only had mine for a couple of months), but on my old phone(s), some of them have had that "time resetting" too, and the people at the tech support said the battery needed to be replaced.
Sorry for hijacking your thread:
I have a similar error with my phone (yukixda v4):
If I send myself a text message at say... 01:35... it's sent 01:35, but the one i recieve has the timestamp at 01:34... this is both with and without automatic time settings..
any ideas?
Click to expand...
Click to collapse
Truth is no matter what is causing this... TWO big issues for me when choosing a phone software set up.
The phone knows what freakin time and date itis
The phone nor the software on should destroy batteries
but thanks guys it really was fun to play with.
Don't use automatic, mine does the same if I set to automatic.
I thought it was something with Giffgaff as I would set automatic and the time would be right but later on during the day it would be some crazy time and date.
Set to manual and your clock will be fine
dunno about any of that but, i do know that if i boot in to MAGLDR is gets buggered up, doesnt matter if the time is manually set or auto set, it always buggers up, dont boot to it and all is good
, at least for me anyway
I'm having the same issues. Time and sometimes dates getting screwed up. Only started happening to me about a couple of weeks ago now. But it's frustrating at the least. I've switched mine to manual setting at the moment. Gonna see how it goes over the next week.
One thing though, it isn't happening to my wife's HD2. She is using the older version of WP7, I'm currently on Yuki's more recent NODO version...
as per my post above yours if you use magldr or even the bootloader it gets messed up, so dual booting droid may be a reason, or using bootloader / magldr to charge, other than that i dont have this issue
Not got dual-boot on my phone, neither do U boot to magldr to charge... But it's happening to my phone every few days so far. Today it was out by 28mins. I want to see if having it on manual time/date does any better...
i also have a problem with my hd2,
9 times out of 10 when i reboot the phone the time and date will be wrong with no pattern i can spot (started to do this out of the blue- no updates or new roms).
im currently running with a cooked win mo image and android on the sd card.
battery still has a respectable life although seems to run out quicker than it once did so i may purchase a new one. (the old one is just over 12 months old)
also my phone has started to freeze on pin request after receiving a text so im gonna try a new image too
if anyone else has seen problems like these and solved them drop a noobie a helping hand pleeeeaaasseeee....
It's not HD2 related
The same issue happens to me (phone jump approximately 36 hours foward randomly)
The phone was a LG Optimus 7 on official rom but never managed to fix this issue (automatic date or not)
ForgetfulGuru said:
Hi guys and girls,
Been using WP7 about a week now and one niggling little issue is doing my head in. Sorry if it has been mentioned before or is covered under some other issue, I did try a search and got nothing relating to it.
My issue; the clock on the phone keeps jumping to random times.
I am using YukiXDA latest build and could find nothing relating to this isue there either.
Would like to know if others have had this problem and what have they tried to remedy it?
Is it a ROM issue or is it a hardware issue?
Click to expand...
Click to collapse
I have the same issue! It happened some months after flashing xboxmods v. 1.11 Rom. It can't be a battery problem because I use 3 different batterys ^^
i use alarm clock extreme and for whatever reason the alarm did not go off. it went off later then when i woke up on my own and starting poking with my phone.
i suspected doze, but its not supposed to doze when plugged in so.....???
anyone else have these issues?
i did not have this problem on my 6 with M.
k.electron said:
i use alarm clock extreme and for whatever reason the alarm did not go off. it went off later then when i woke up on my own and starting poking with my phone.
i suspected doze, but its not supposed to doze when plugged in so.....???
anyone else have these issues?
i did not have this problem on my 6 with M.
Click to expand...
Click to collapse
I use Alarm Clock Xtreme and I'm not having any issues.
no issue with 3p alarm. I use alarm clock plus.
Yes, I am having a similar problem on my Nexus 6P with Alarm Clock Extreme Free. This app worked fine on my Nexus 7 2013.
Omg.. Yes same problem here. I got my nexus this pass Monday and was late for twice because my alarm didn't go off until I picked up the phone or woke it up...
Alarm clock extreme paid app..
Same kind of problem here. Ended up creating an alarm in the stock clock app. After that, both alarms went off. I've left it like this cause I already was late for work 3 days last week.
Sent from my Nexus 6P using Tapatalk
Seems like an app issue. Have you guys reached out to the developer?
badboy47 said:
Seems like an app issue. Have you guys reached out to the developer?
Click to expand...
Click to collapse
i have sent them a bug, got the canned response.
this is a real annoyance because i need a math problem to wake up.
k.electron said:
...this is a real annoyance because i need a math problem to wake up.
Click to expand...
Click to collapse
I hear ya! However, I've switched back to the alarm in the stock Android Clock app, which works fine, and I'm now using an old-school clock radio as a backup. This double-pronged strategy seems to work fine for me for the time being, until the developers of Alarm Clock Xtreme address the problem with using their app on the Nexus 6P.
I just got a new S7 edge 935f. I rooted it with magisk after installing twrp. I have tried a few Nougat stock roms and in all of them, my alarm clock fails to go off first thing in the morning. It will come on when I push the home button and for the rest of the day all alarms work fine. It is only the first morning alarm that fails.
I wonder if this is due to something wrong with the kernel, and if installing a custom kernel may fix this. Or is the a lib file that may be corrupt.
Anyone else experience this kind of problem? I read in a few articles and forums that it is linked possibly to a SOD (sleep of death) bug. Hoping some information can come from anyone else who knows of this.
Thanks in advance.
So a custom rom and kernel failed to fix this. In the kernel settings with mtweaks I even allowed all wake locks. Mos puzzling and even slightly frustrating...
bobfrantic said:
So a custom rom and kernel failed to fix this. In the kernel settings with mtweaks I even allowed all wake locks. Mos puzzling and even slightly frustrating...
Click to expand...
Click to collapse
Hey have you tried using a third party alarm clock so you can test if it's an isolated case or with all of them ?
jaimep01 said:
Hey have you tried using a third party alarm clock so you can test if it's an isolated case or with all of them ?
Click to expand...
Click to collapse
yes I have and all have same issue. For the first alarm I have to manually wake up the phone, all others work through the day.
Surely I am not the only one to have this trouble....
bobfrantic said:
Surely I am not the only one to have this trouble....
Click to expand...
Click to collapse
Check the battery saver app in maintanance it miht have picked up the clock app which I soubt but it is a good idea to check it.
jaimep01 said:
Check the battery saver app in maintanance it miht have picked up the clock app which I soubt but it is a good idea to check it.
Click to expand...
Click to collapse
Yes, I checked all those things... I wonder about MM 6.0.1 if the issue would remain or not. I found an app "SOD Killer" that I will test. It results in some battery being used to keep it from going into deep sleep. Have googled this and there are a lot of others with the situation but not a lot of fixes around.
bobfrantic said:
Yes, I checked all those things... I wonder about MM 6.0.1 if the issue would remain or not. I found an app "SOD Killer" that I will test. It results in some battery being used to keep it from going into deep sleep. Have googled this and there are a lot of others with the situation but not a lot of fixes around.
Click to expand...
Click to collapse
I feel my alarms fail as well from time to time, but i think the culprit is, in advance features the easy mute function have you tried turning it off ?
It might have a bug or something with the sensor.
jaimep01 said:
I feel my alarms fail as well from time to time, but i think the culprit is, in advance features the easy mute function have you tried turning it off ?
It might have a bug or something with the sensor.
Click to expand...
Click to collapse
No I haven't tried that. I have mine working now. It woke me up this morning. What did it is the app "SOD Killer" which is on google play. It increases battery useage a little but until I find out which file is keeping phone asleep, it's a small price imho.
do not "freeze" or "doze" or use any similar apps to "kill" clock app in background.
which means, clock app needs to run to have alarm working.
yaibakt said:
do not "freeze" or "doze" or use any similar apps to "kill" clock app in background.
which means, clock app needs to run to have alarm working.
Click to expand...
Click to collapse
I don't kill or freeze anything. Only thing I have to make alarm work is the SOD Killer app that keeps phone from going into deep sleep.
So a funny thing happened on the way back to Marshmallow 6.0.1 as I had just finished getting through setup and was about to start doing things on my phone, I got a notification that there was a firmware update downloading. It was taking me back to 7.0 and it upgraded my phone to the first version of Nougat for Luxembourg. Then a few minutes later another system update was downloading and I installed it and my phone now had the latest Nougat for Luxembourg. So first thing I checked was the alarm. I set one for 4 hours later, and it worked. I also tested an overnight alarm and it also worked. So now I have working alarms. Still going to downgrade back to 6.0.1 though, just feels better than Nougat to me.