Hello, anyone know why my S3 would not be keeping time across reboots? Every time I boot the date is sometime in 1970.
I first noticed this, because the market and GMail apps wouldn't update, so perhaps others have noticed this, but their clock gets updated by the cell network and it goes away. The timestamps on all my recovery files is 1970(names are correct).
I know that in Linux there is the idea of a hardware clock and the system clock. The hardware clock is maintained across boots and the system clock is read from that, but my system lacks the programs to set it. Normally it is hwclock, which should be in busybox, but is not.
My s3 is doing the same all my recovery are 1970-xx-xx-xx
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Everyones does it that uses cwm..use twrp
Sent from my SAMSUNG-SGH-I747 using xda premium
JB calhoun said:
Everyones does it that uses cwm..use twrp
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Oh hell, thank you for the answer. I didn't even think it would be with CWM. I'm pretty sure it's a RTC issue. After my system clock is updated, my phone is okay until reboot. The hardware clock never updates, though. I even compiled busybox with hwclock specifically so I could set the hardware clock, but it fails. I wrote a program that specifically updates the RTC with ioctl( RTC_SET_TIME ) and again I get a failure and no update. So when it reboots, CWM sets the system clock to the hardware clock, which is still 1970.
I'm about to go traveling, so I don't want to mess up my phone. Does TWRP work with ROM Manager for backups and installs? Does it just skip setting the system time from the hardware clock or does it have a way to actually set the hardware clock?
This is actually most likely a kernel issue which prevents the hardware clock from being updated. I should try another kernel.
Related
I have a DINC2 through work so I have to stay stock (no S-OFF or root) and did the OTA update to 2.3 yesterday. I noticed that my alarm didn't go off this morning so I tapped the Sense clock on my home screen and nothing happened.
Has anyone else experienced this issue? If so, were you able to find a fix/work-around to set alarms?
No issues here. That said, I am not running OTA, but rather Gingersense which is basically a rooted and debloated version of the OTA.
If you didn't do a factory reset, it may be worth it.
Sent from my ADR6350
Mine is working. I took the official OTA. I hope someone acheives root through the new 2.3 I knew I would regret it... I own it!
My alarm died as well and I'm running a debloat official Rom
sent via rooted Droid Incredible 2
More info... this issue is being reported by other users in the HTC Support forums.
After updating to GB yesterday, I believe that the Alarm/Clock function HAD worked at least once. Since that time, I ran the Clock app from the All Apps screen and now the Widget no longer calls up the Clock App and the Clock app itself has disappeared from the App list.
I think the root of the problem is the missing Clock app. Do NOT want to factory reset to get this back. There must be another way.
For those having this problem, is your Clock app missing?
Is there a way to reinstall just the Clock app?
I'm on rmk debloated rom and it woke me up fine this morning just tested it again and its fine. I like to delete a lot of sense stuff and deleted a little too much so I reflashed it without wiping maybe that's why my clock is still working
Sent from my ADR6350 using Tapatalk
I do not have the clock app in my All Apps, so that may be the root of my issue also.
But I do not want to do a factory reset if at all possible either, hopefully someone will find a better solution.
dlipetz said:
More info... this issue is being reported by other users in the HTC Support forums.
After updating to GB yesterday, I believe that the Alarm/Clock function HAD worked at least once. Since that time, I ran the Clock app from the All Apps screen and now the Widget no longer calls up the Clock App and the Clock app itself has disappeared from the App list.
I think the root of the problem is the missing Clock app. Do NOT want to factory reset to get this back. There must be another way.
For those having this problem, is your Clock app missing?
Is there a way to reinstall just the Clock app?
Click to expand...
Click to collapse
Nope it's gotta be something else.
I haven't had a clock app since I got my phone. Rooted it and jumped on Gingersense. I still don't have a clock app but my alarms work fine and when i click on my clock on the weather widget it calls up the alarm clock/world clock just fine.
jrizk07 said:
Nope it's gotta be something else.
I haven't had a clock app since I got my phone. Rooted it and jumped on Gingersense. I still don't have a clock app but my alarms work fine and when i click on my clock on the weather widget it calls up the alarm clock/world clock just fine.
Click to expand...
Click to collapse
I definitely had a "Clock" app. Ran it today for the first time. It called up the same screens you see when pressing on the clock on the HTC Clock/Weather widget. Now widget is broken and app is missing.
If someone has extracted the HTC Sense 2.2 Clock App and can post the file I would be willing to try it.
I used the Simi Folder clock widget on Froyo, OTA updated last night and yes all of my alarms were reset, however the widget still functions as it did (to open clock, world, alarm, etc.)
jdemerol said:
I used the Simi Folder clock widget on Froyo, OTA updated last night and yes all of my alarms were reset, however the widget still functions as it did (to open clock, world, alarm, etc.)
Click to expand...
Click to collapse
What is a Simi Folder? I'm new to the Android...
jdemerol said:
I used the Simi Folder clock widget on Froyo, OTA updated last night and yes all of my alarms were reset, however the widget still functions as it did (to open clock, world, alarm, etc.)
Click to expand...
Click to collapse
Ok, I assume you mean the SiMi Clock Widget... We're talking about the stock standard HTC Clock/Weather widget that appears on the home screen. You used to be able to tap the clock and the clock app would launch. This app provided alarms, timers, stopwatches and more.
See this thread for more details...
http://forum.xda-developers.com/showthread.php?t=1167107
Updating this thread...
Factory reset does in fact restore the clock app. But the first battery pull kills it again.
I did the factory reset and spent the better part of the day reconfiguring my phone. only to lose it again after I pulled battery.
I called HTC and they said they are aware of the issue and patch will be forthcoming.
To those thinking about doing a hard reset, you may want to wait since the first battery pull you do will break the clock again.
What's interesting, at least to me, is that I've done a battery pull...no issues. I wonder why?
The issue has been discussed in the HTC support forums and the current suggested "fix" is performing a factory reset. However, there are reports that this only fixes the problem temporarily.
Using the RMK Gingersense ROM (based on the GB OTA), I too experienced my Clock app disappearing. However I was able to recover it without a factory reset using the steps I described here (root required).
dlipetz said:
I called HTC and they said they are aware of the issue and patch will be forthcoming.
Click to expand...
Click to collapse
Being new to Android I have a few questions. How would they apply such a minor update? OTA push? Market update?
jschmier said:
The issue has been discussed in the HTC support forums and the current suggested "fix" is performing a factory reset. However, there are reports that this only fixes the problem temporarily.
Using the RMK Gingersense ROM (based on the GB OTA), I too experienced my Clock app disappearing. However I was able to recover it without a factory reset using the steps I described here (root required).
Click to expand...
Click to collapse
Cool, glad you were able to resolve for rooted users. I am not rooted however and do not plan to do so (business user - corporate issues). Looks like I'm going to have to wait for HTC and Verizon to work this out.
sixteen2nd said:
Being new to Android I have a few questions. How would they apply such a minor update? OTA push? Market update?
Click to expand...
Click to collapse
The HTC rep told me it would be an OTA update but I really don't know if that was a guess or not.
My guess is that this hasn't even been escalated yet. If it were, Verizon would/should probably halt the GB rollout or at least caution users that the upgrade may remove the Clock app.
I just got my Incredible 2 yesterday. I was having trouble getting my fooled account to sync so I factory reset it about 7 times. My phone came with Gingerbread on it. My clock app worked for a while and now it's gone. I am pretty sure a factory reset is a temporary fix.
Sent from my ADR6350 using XDA Premium App
My gf got the IC2 after demoing my S. She loved it at first but after the recent OTA update she noticed that the clock widget is no longer available.
I know it's not really a big deal but thats the only convenient way to access the alarm clock.
Anyone know a way around this? And the clock apps on market isnt good as stock.
I also thought of somehow transferring my clock widget apk but I have no clue of how to do this
I appreciate any and all help!
Sent from my HTC Incredible S using XDA Premium App
From what I've week a factory reset
Sent from my ADR6350 using XDA Premium App
yup Factory reset is the only way to correct the issue. I've had to do it twice already within a 3 week period since the update to GB. I emailed HTC and all they could say was they know about it and they dont know when there will be a fix.
So for now Im using Beautiful Widgets and Alarm Clock Plus on my Phone
I took the gingerbread update and my clock still works fine. I did have to hunt it down though, I assumed it was an App but I found it under Widgets.
It used to be an app on Sense 1.0, I know that.
Did you check all the .apks in settings under manage applications? If its in there force stop it, clear data, cache & possibly uninstall update then uninstall before reset if not reset should do the job.. good luck
Sent from my ADR6350 using Tapatalk
This issue is being discussed here, here, and here if anyone is interested in following.
For those that don't want to read all the posts (I don't blame you) here is the jist:
- Factory reset seems to fix it for most, but the issue comes back after a few days/weeks
- Some people have had luck getting the default clock app to reappear after installing another clock app from the market
- Most have checked the clock apps settings and found it is greyed out in the list of installed apps and is listed as 0kb
- Verizon seems to be passing people along to HTC who admits they know about the issue but don't know what will fix it or when they will have a fix (outside of the recommended factory reset)
All the sudden today, the Clock Package stopped working right. Whenever I press "create alarm" it gives a force close. I've tried downloading clock package from the forums and pushing it to system/app, checking/resetting the permissions, and wiping the dalvik cache. Still will force close if I try to create alarm. World clock, stopwatch, and Timer work fine. Currently on deodexed EH17.
Find the app in Titanium and clear data.
Sent from my SPH-D700 using XDA App
Did, done. No effect.
radugb said:
Did, done. No effect.
Click to expand...
Click to collapse
Damn! And of course in settings the "clear data" button is greyed out. I have been using Extreme Alarm since the leak where the alarm no longer worked in silent mode.
Tried a hail mary and it worked. I used unyaffs to unpack my last nandroid back (from 7 days ago), took the clockpackage.apk that was in the system backup and pushed it to the system/app folder. Wiped dalvik cache, rebooted and crossed my fingers. I went into the clock app and pressed "create alarm", then my phone froze for about 30 seconds, but it went through. I was able to create and set my alarms and now we're back to status quo!
Then I wonder why it wouldn't work when you downloaded it. Unless it came from a different build and was incompatible with your data.
Sent from my SPH-D700 using XDA App
I have no idea either. I'm on the Rooted/Deodexed/Busybox EH17 with the EH17Plus kernel. I don't think either of those uses a different clock package. The only other instance that could confict is that I used the Wireless Hotspot patch. I know that it modifies the framework-res.apk so maybe it creates a conflict between the samsung framework and the clock package?
radugb said:
I have no idea either. I'm on the Rooted/Deodexed/Busybox EH17 with the EH17Plus kernel. I don't think either of those uses a different clock package. The only other instance that could confict is that I used the Wireless Hotspot patch. I know that it modifies the framework-res.apk so maybe it creates a conflict between the samsung framework and the clock package?
Click to expand...
Click to collapse
The way EH17 handles data is different for some apps. I could not use my email data. I had to set the accounts up manually. So it is quite possible there is a difference there too.
For me it was the stock email.apk in all the GB leaks that had problems with my email. I'd set up manually, and it would work for the first day or two, then it would get authentication errors with the SMTP server so I couldn't send mail. I went thru a lot of troubleshooting before I just gave up and d/l'ed the Yahoo!Mail app. Couldn't understand why it would work at first but not after a few days.
Alarm Clock FC
Have same problem
I am on 4.1.2 on HTC One X+ and have try two different ROM. In both ROM my Clock app FC after 2 or 3 sec
and If I set any alarm it will not work..?
I try other alarm app but I have to keep them open for alarm to work otherwise they don't work in background ?
I also Try Deskclock from 4.2 ... it also FC after 1 or 2 hr....but in that timer works, So if I set 8 Hr timer it works great.. and it not FC and works in Background too...
This is the og epic forum, go ask in the one x+ forums
Sent from my SPH-D700 using Tapatalk 2
Okay, this might be an old thread, but i just want to make suggestion which work in my case, just in case someone bumped into this.
Have u tried set the alarm ringtone first prior to checking the set alarm checkbox? on my case this was the problem due to my custom rom originally uses ringtone of which file's been deleted.
This worked for me! Been looking for a solution for a long time and finally found it.
http://forum.xda-developers.com/showthread.php?t=1968237
Essentially delete the 4.1 clock app and install the 4.2 clock app in the linked post. Im running 4.1.2 and had no issues with it.
I have not had this problem at all...until maybe a week or go, when it started.
I have screen flicker, sometimes quite bad. I thought I read somewhere that GPU settings may have something do do with it.
Thing is, I haven't changed any settings, or kernels. I'm no what is listed in my sig, and have been for quite a while.
Any thoughts?
You could try disabling HW overlays under developer options in the settings menu.
Disabling hw overlays won't help (much anyways). Turn off auto brightness. Just set your brightness to a usable level. I didn't notice a single flicker the day I turned off auto brightness. The only tradeoff there is you're gonna run through your battery a little more quickly in lower light levels. Wasn't worth it for me, but whatever makes you happy.
Sent from my SAMSUNG-SGH-I747 using xda premium
Neither is a go for me.
I never use auto brightness; I've tried both having Disable Hardware Overlays set and not set.
It's strange...I never had this problem until recently.
But, another thing that seems to be the case: I"m not sure it's happening in any app other than Samsung Email.
...
Just went and tried something: opened an email and scrolled in Samsung eMail, and it flashed. Did same in GMail, and it didn't. Maybe it's just something about a recent upgrade on that app. Maybe I'll post a topic on that app and see if anyone else is seeing it.
What's your ROM?
Sent from my SAMSUNG-SGH-I747 using xda premium
diablo009 said:
What's your ROM?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
It's listed in my signature. Stock/Rooted.
I do have an update: I also was having pretty severe flicker/flashing when reading in Aldiko.
Last night I did a TWRP backup; factory reset; restore Data partition. Flashing is improved quite a bit, but still there.
So again, it seems it is happening, for the most part, in just a couple apps: Samsung Email, and Aldiko.
ewingr said:
It's listed in my signature. Stock/Rooted.
I do have an update: I also was having pretty severe flicker/flashing when reading in Aldiko.
Last night I did a TWRP backup; factory reset; restore Data partition. Flashing is improved quite a bit, but still there.
So again, it seems it is happening, for the most part, in just a couple apps: Samsung Email, and Aldiko.
Click to expand...
Click to collapse
For one, I am trying to help you. For two, signatures don't show up when viewing in mobile app. Three... did you try a different kernel?
Same happens wid me.... still am on search for a solution.... at first I thought. May be a ROM has to do wid this... but am not sure...
Sent from my SGH-I747M using xda premium
diablo009 said:
For one, I am trying to help you. For two, signatures don't show up when viewing in mobile app. Three... did you try a different kernel?
Click to expand...
Click to collapse
Sorry. Didn't mean to offend. I didn't know sigs don't show up when viewing in mobile. I put the info in the sig in order to prevent people from having to ask, and to prevent from having to type it with every post. I appreciate your telling me it doesn't show up in mobile apps. I never use mobile for forums...typing is to laborious.
IN answer to three, yes, have tried different kernel, although it's been quite a while.
It's ok.
I've had this issue on AOSP ROMs. Only way out was to change ROM.
Sent from my SAMSUNG-SGH-I747 using xda premium
I get this twice every time I boot the phone. I'm running the latest firmware. Rooted via the previous pre-rooted image. Seems to happen when I freeze any system app in Titanium. Even if it's something that seems minor, like Clock. On that note, I'd recommend the stock clock over the ASUS one, even if just for the ability to dismiss future alarms.
Unrelated, but does the Xposed module 'App Settings' work for anyone? The DPI/font scale/resolution changes don't do anything for me.
I can't wait for this bootloader to get unlocked so we can get some 64-bit AOSP/stock ROM on this phone.
AOSP for Zenfone 2 needed badly !
This is a great phone but the only negative is too much bloatware.
I wish we had some AOSP 64-bit ROM for Zenfone 2.
Any idea how to build it ?
arindam.nsit said:
This is a great phone but the only negative is too much bloatware.
I wish we had some AOSP 64-bit ROM for Zenfone 2.
Any idea how to build it ?
Click to expand...
Click to collapse
64 bit kernel might be a problem to build for a given ROM
Sent from my ASUS_Z00AD
I used to have this problem after the last update. Specially after boot this message would come twice and every time i open power saver it crashes. Deleting the data solved the problem. Now i know any disabled system app will cause this. Thanks man.
+1 Clearing Dalvik and app cache fixed my issue. :good: This can also stem from disabling core Asus or Android services/apps and that is what you did.
Wakelock blockers apps can also cause this and may even cause random reboots or freezing if core wakelocks are blocked. Other wakelocks are required to receive instant calls/texts and sync emails/time/etc too.
You should never disable clock, as other xda users pointed out, removing the clock app will in addition cause issues with the power saving app.
Do you know that there is a forum search button on your right? Anyway, here is how to easily change DPI, Resolution etc without root on the fly with a single command in adb or terminal that survives reboots.
http://forum.xda-developers.com/zenfone2/general/tip-adjusting-dpi-root-t3098690
Whats not working with Asus Clock app? I use it for timing, alarms and international clocks, it works fine.
Asus rep stated in xda forums that they are working on a fully x64 Android OS. Currently, only the Kernel is x64.