[Q] No Battery Backed Real Time Clock? - Verizon Samsung Galaxy S III

So I know that there's been talk about recovery not being able to get the correct date and time, but if you put your phone into airplane mode, turn off the phone and turn it back on, (and leave airplane mode on) you'll see the phone default to April 18, 1970, which indicates that the clock has reset.
At least that's what happens in CM10.0.0 and all previous CM builds I've tried. If I recall correctly this was also an issue on the Stock builds.
This is of course a huge pain in the ass, since any time the battery dies and you plug it in, the device boots up, has a date of 1970-April-19 for a good 15 seconds before picking up time from the network. Which means that alarms think they've been missed and go off, and any titanium backups that are scheduled go off as well.
(And this also happens every time you turn off your phone on a flight, for the same reasons.)
So I'm assuming that whether there is a clock or not...it just doesn't work.
Can we at least have a way to put the UTC system time at shut down into a file on /data or /sdcard that's read at startup? Such that if system time < time in file, use the time in the file.
I know this is ass backwards, but in the case there isn't actually a persistent RTC/hwclock on the device, we need some way to get an approximation of the time when the network or ntp isn't available.

Related

[Q] Auto time update

Do you have to manually update the time and date if the battery runs out? My time and date has been reset.
I have had the same thing happen to me several times. If the battery completely runs out, you have to manually reset the time I think.
I've never let my battery run completely down, but there are several apps in the market that will keep your clock synced via NTP.
I have mine setup to sync whenever it sees wifi after a reboot and that seems to work well.
thanks - I wasn't sure if ntp was built into the kernel but my clock didn't update so I guess an app is the way to go.

[Q] Is there a possibility (an app?) to make it impossible to shut down phone in cer

I would like to know if there is a possibility (maybe an app) to make it impossible for me to shut down / turn off my Android phone (in certain periods of the day). I want to not be able to turn off my phone.
(The reason behing it: In the morning every time the alarm goes off, instead of solving the math problem to turn it off, I turn off my phone and continue sleeping )
steffenlindau said:
I would like to know if there is a possibility (maybe an app) to make it impossible for me to shut down / turn off my Android phone (in certain periods of the day). I want to not be able to turn off my phone.
(The reason behing it: In the morning every time the alarm goes off, instead of solving the math problem to turn it off, I turn off my phone and continue sleeping )
Click to expand...
Click to collapse
Wow. I thought I was a heavy sleeper, often hitting the snooze multiple times without actually waking up.
I can't imagine that there is a way to do this, without some sort of custom ROM that prevents shutting the phone off.
I'd suggest:
Putting the phone across the room so you have to get up to turn it off.
Getting an alarm clock and doing the same thing.
Getting one of the really annoying alarm clocks available at ThinkGeek.com that require you to find a part or do a puzzle to shut the alarm off.

Nite Mode doesn't automatically stop at sunrise

I have Nite Mode enabled & use the default on/off criterion of Sunset & Sunrise.
For the past two mornings, unlike previously, I have turned on my fone (abt 8:30am) to be surprised that apparently the Nite Mode S/W doesn't know how to tell time. Yesterday I just clicked the "Turn off" button in the notif bar. Today it happened again; & I left it to see what would happen. Nite Mode remained 'on' until about 10:15 or so - when it turned off, apparently spontaneously. I did reboot on both days to no avail.
Bootloader is still locked, so fone is not rooted.
Could it be that I locked the phone w/a Pattern to get to use the Fingerprint Feature? understand that a number of things won't take place if the fone is off & locked; still it shouldn't take > 2hrs for the Nite Mode S/W to 'see' the right time... It seems to go into Nite Mode very nicely on it's own when sunset time comes around…
Anyone else have this prob? Any ideas what may have caused it? Sprint Tech Experts had no immediate answer, & are looking into it. Got the phone June 27… TIA, oldwolf
oldwolf613 said:
I have Nite Mode enabled & use the default on/off criterion of Sunset & Sunrise.
For the past two mornings, unlike previously, I have turned on my fone (abt 8:30am) to be surprised that apparently the Nite Mode S/W doesn't know how to tell time. Yesterday I just clicked the "Turn off" button in the notif bar. Today it happened again; & I left it to see what would happen. Nite Mode remained 'on' until about 10:15 or so - when it turned off, apparently spontaneously. I did reboot on both days to no avail.
Bootloader is still locked, so fone is not rooted.
Could it be that I locked the phone w/a Pattern to get to use the Fingerprint Feature? understand that a number of things won't take place if the fone is off & locked; still it shouldn't take > 2hrs for the Nite Mode S/W to 'see' the right time... It seems to go into Nite Mode very nicely on it's own when sunset time comes around…
Anyone else have this prob? Any ideas what may have caused it? Sprint Tech Experts had no immediate answer, & are looking into it. Got the phone June 27… TIA, oldwolf
Click to expand...
Click to collapse
Check your time zones or something....is your time set automatically or manually? What what time zone are you in the first place (no to get too personal...)?
@AarSyl, it doesn't matter, I haven't changed timezones I've been in ever since I activated the fone… 6/27… & it happened only the last two days; since I locked my phone w/Pattern to beable to use Fingerprint feature… I have get auto time from network provided time, & auto time zone fm network provioed time. I haven't left my home boro…
oldwolf613 said:
@AarSyl, it doesn't matter, I haven't changed timezones I've been in ever since I activated the fone… 6/27… & it happened only the last two days; since I locked my phone w/Pattern to beable to use Fingerprint feature… I have get auto time from network provided time, & auto time zone fm network provioed time. I haven't left my home boro…
Click to expand...
Click to collapse
I have one on Verizon activated last Saturday. Im not 100% sure but I think it worked as expected for a day or two but then... The "sunset and sunrise" are two time zones (hours) off. Which coincidentally is the time zone of the area code of my phone number. The OOTB text message app, and some other texting apps, also show text sent time stamps in the time zone of my number, even when I send a text from the time zone I live in. Everything else on the phone seems to know the correct time zone as the phone is set to get it from the network. Including the text time received stamp. Its odd.
@anon2017, left phone off Fri aftnoon to Sat nite (a brief respite) & well pst sunset turned it back on, & it read Sunset time just fine & booted into nite mode - now to see if it properly reads sunrise Sun morn… I recently took the June security patch for my Sprint U11; so maybe that'll fix my orig issue… or I might just turn off Auto Get Time Zone fm Network, or turn off nite mode & leave auto brightness adjustments… Keep me posted pls on your results… BTW, I fell asleep this past Thu. w/out turning off fone & it switched off nite mode as expected.
So maybe h/w default behavior affects this- many things don'tork when fone is locked &I'm using Kaspersky Full which affects lock insofar as I no longer get "Your phone is encrypted- which makes me happy- bc a nasty thief could purposely go past30 bad passwords & cause my fone to be Factory Reset. Talk abt loss…
Well, it seems that taking the June security update has solved, @ least for this morning's boot-up, my prob w/nite mode staying on in the morning (nothing else has been changed).
Earlier this a.m., at the beginning of the boot process, my wallpaper seemed a bit dark immediately on startup; which wasn't making me feel like the problem was solved- however, upon completing the boot process, there was no moon icon in my notification bar & the wallpaper picture was as bright as usual!
Let's see if this will be consistent.
*Update* 7/11/17 8:11:14 seems the boot time may have something to do w/whether or not Nite Mode is turned off on bootup. I turned on fone around 6something & Nite Mode was still on… used notif par settings to turn it off & rebooted & it was now off… ?
Two days in a row- Nite mode goes off on its own…
Third day no luck; beginning to think it depends on when I boot fone…
Awesome

Help: Device won't finish booting?

So, like every other thing out there, stuff fails. I woke up this morning and checked my phone to check the time. Nothing unusual. I go to get changed and I come back to my phone and it just shows the Verizon boot logo. I thought "Ok, it must have just crashed somehow and it'll reboot!" And so I waited...and waited....and waited. It seems to be half-booted, but stuck somewhere along the way. The screen is dimmed (indicating the auto-brightness feature is working) and it has the orange hue over the white text (indicating the night-light mode is still on). I had medium Power Saver mode on to keep the battery overnight, and the CPU cap was enabled. I've noticed that some apps don't like to start with that setting enabled, so I'm inclined to believe that the 70% CPU cap is somehow messing up the system and keeping it from fully rebooting. I'm currently waiting for the battery to die since I can't remove my battery in the Note 5. I've checked the device temperature by hand every now and then, and it doesn't feel warm so the CPU isn't cycling up like it should. I don't have access to my computer until I finish moving and unpacking my new house, so I can't use ADB to try and do anything. What should I do?
BluSpectre said:
So, like every other thing out there, stuff fails. I woke up this morning and checked my phone to check the time. Nothing unusual. I go to get changed and I come back to my phone and it just shows the Verizon boot logo. I thought "Ok, it must have just crashed somehow and it'll reboot!" And so I waited...and waited....and waited. It seems to be half-booted, but stuck somewhere along the way. The screen is dimmed (indicating the auto-brightness feature is working) and it has the orange hue over the white text (indicating the night-light mode is still on). I had medium Power Saver mode on to keep the battery overnight, and the CPU cap was enabled. I've noticed that some apps don't like to start with that setting enabled, so I'm inclined to believe that the 70% CPU cap is somehow messing up the system and keeping it from fully rebooting. I'm currently waiting for the battery to die since I can't remove my battery in the Note 5. I've checked the device temperature by hand every now and then, and it doesn't feel warm so the CPU isn't cycling up like it should. I don't have access to my computer until I finish moving and unpacking my new house, so I can't use ADB to try and do anything. What should I do?
Click to expand...
Click to collapse
Ok, so I fixed my own problem. I tried a variety of small post-boot tricks like trying to force the device into a different boot mode (ex: Power+minus=safe boot, power+home+VolDown= Download Mode) and forcing it into Download mode worked. It overrode the issue and I was able to tell it to reboot again. This time it rebooted normally. This was really weird. I've never had this happen before on any other device I've ever owned. I hope this might help someone in the future.

Phone(s) still hot when turned off. Also, wicked power draw.

G'day,
I've had some odd issues with two consecutive Xiaomi phones, and I'm hoping someone here can shed some light on it for me.
With both my Mi Note 2, and now my current Mi Mix 3, after less than a year of owning each one (respectively), out of nowhere, the battery life drops through the floor, the phone gets really hot, and most oddly, I got wicked battery drop while the phone is off (e.g. I turned the phone completely off at 77%, and about an hour later, I turn the phone back on and it's at 43%).
On both phones, I've tried a factory reset, but it didn't work. It was, for all intents and purposes, fecked. At the moment, I'm waiting for the 15 day countdown for my Mi Mix 3 bootloader to be unlocked so I can try flashing the EU MiUI ROM and see if that helps, but that's still a hell of a long time to wait with a phone that idles at 50+° C and has a battery life of about 3 hours with minimal SoT.
I've installed BetterBatteryStats (using ADB to provide permissions), CPU-Z, CPU Monitor and Ampere to see if I could get some more information. I found a few things:
1. Somehow, with mobile data and WiFi enabled, the system was drawing SO MUCH power (reported by Ampere) that it literally wouldn't charge while plugged into a 2A wall port. It was drawing like 1300mA when it wasn't plugged in, and when it was, it was STILL drawing about 130mA, meaning no matter what, while the phone was on, I was losing battery.
2. BBS reported the biggest battery killer was under the 'Alarms' tab, caused by Android, which were "Intent: *job.delay*" and "Intent: *job.deadline*". I have literally no idea what these are, what's causing them, or how to stop it triggering.
3. I've done a full factory reset. The first hint that something was wrong was when I noticed that the phone wasn't charging when it was plugged in and turned on. I did the full factory reset, didn't help.
I'm currently running Global MiUI 11.0.4.0, Android 9.
Does anyone have any ideas? I haven't manually updated anything, I'm not particularly rough with the phone, but for two phones in a row, this has come straight out of nowhere. It's a shame, because the Mi Mix 3 has spoiled me with it's 100% screen real estate (no hole-punch, no teardrop for front camera), but I think my next phone is gonna go with something else.
Cheers.
Update: I've taken a squizz at the Google Battery Historian and basically, I have no feckin' idea.
The best I can get out of it is "Yep, something in the labyrinthine generic 'Android' system is causing it, but good luck narrowing it down or stopping it."
That being said, I've found that this Partial Wakelock is triggered fairly often (1-6 times per minute, give or take): IntentOp:.common.broadcast.BackgroundBroadcastReceiverSupport$GmsReceiverIntentOperation
I have no idea what the hell it is or does, and the only information I can find about it is from developers asking questions where it just happens to be part of their codebase, or a breakdown of how the WakeBlock app works.
It's getting woken up about every minute or so (usually more than once a minute). However, the wakelocks appear to be part of the core Google/Android systems that can't be individually disabled.
I'm still feckin' confused.
Overloke said:
Update: I've taken a squizz at the Google Battery Historian and basically, I have no feckin' idea.
The best I can get out of it is "Yep, something in the labyrinthine generic 'Android' system is causing it, but good luck narrowing it down or stopping it."
That being said, I've found that this Partial Wakelock is triggered fairly often (1-6 times per minute, give or take): IntentOp:.common.broadcast.BackgroundBroadcastReceiverSupport$GmsReceiverIntentOperation
I have no idea what the hell it is or does, and the only information I can find about it is from developers asking questions where it just happens to be part of their codebase, or a breakdown of how the WakeBlock app works.
It's getting woken up about every minute or so (usually more than once a minute). However, the wakelocks appear to be part of the core Google/Android systems that can't be individually disabled.
I'm still feckin' confused.
Click to expand...
Click to collapse
I think it's an issue with your network operator
XDRdaniel said:
I think it's an issue with your network operator
Click to expand...
Click to collapse
Any ideas as to how I'd further troubleshoot? I've gone into *#*#4636#*#* and changed the sort of signal it looks for, but it doesn't appear to have fixed anything.
In case anyone is interested, I've attached on of my Bugreports (from running adb bugreport), which can be viewed through Google Battery Historian.
I'm not saying there's a cash prize for anyone who can tell me what is happening and why, but I'm also not saying that there isn't.
So, I think we have our culprit (maybe).
I have attached several screenshots from a Battery Historian I took after having my phone on all day. The total phone on time was about 4-5 hours with, no joke, maybe 10 seconds of screen on time. Let's go through this absolute bullshittery together, shall we?
Battery - Full Time: The full length of time captured by the Battery Historian/bugreport command. It's in Zulu Time (GMT+0) and I'm in Australia (GMT+10), so the line starts going up at 5PM last night, which is more or less when I plugged it in to charge. You can see, while 'off', it took 16 hours to charge to 100%, and this was from a 'cold boot' (phone is completely dead), so it didn't have any information about what had been running, etc.
Battery - Discharge: The five or so hours time in which the entire battery discharged, starting from when I woke up in the morning and got ready for work. In the Screen row, you can see the small, three-to-four second windows throughout the day that I turned the phone on to check the battery. For almost the entirety of the time, the screen was off. You can see where the line next to Phone State goes from black to navy blue. This indicates that the phone has been put into Airplane Mode - you can see this is also where everything relating to network connectivity or mobile strength completely disappears. You can also see that App Processor Wakeup completely dies here - that means that actual installed apps (including GOOGLE_SERVICES and Xiaomi's preinstalled Facebook app stop sending commands to wake the CPU.
Battery - Cause: At least once a minute, usually more, two things fire that keep the CPU running - Abort:Wakeup IRQ detected during suspend: 999 msoc-delta and Abort:Wakeup IRQ detected during suspend: 663 qpnp_rtc_alarm. I have no feckin' idea what either of those are, and Googling results in either developer guides or threads that lead nowhere. If anyone knows what they are, for the love of God let me know.
Battery - Foreground Processes: While the phone was off, with every app closed, in Airplane Mode, we can see that there are still four apps that are somehow in the foreground: com.miui.mishare.connectivity (odd, since there's no connection), com.miui.securitycenter (which I tried disabling through ADB last night, and it stopped my phone from booting. Oops), com.miui.notification, and com.android.providers.contacts (which disappeared shortly after entering Airplane Mode).
Battery - Video: You can see here, for the ENTIRETY of the time that the phone was turned on, this odd Video row was enabled. There is no other information about it - what causes it, where it's coming from, what 'Video' means, anything.
Battery - 7 Second Slice: This is just a close-up of a seven-second period of time, wherein the above 999 msoc-delta and 663 qpnp_rtc_alarm kept the CPU running six times within 7 seconds. Not a lot on its own, perhaps, but over the course of hours, it clearly causes issues.
I've also attached the latest bugreport where I took these screenshots from if anyone wants to try and make sense of it.
--
This looks to me like an hardware issue more than anything, what is the idle state of the cpu?
Overloke said:
So, I think we have our culprit (maybe).
I have attached several screenshots from a Battery Historian I took after having my phone on all day. The total phone on time was about 4-5 hours with, no joke, maybe 10 seconds of screen on time. Let's go through this absolute bullshittery together, shall we?
Battery - Full Time: The full length of time captured by the Battery Historian/bugreport command. It's in Zulu Time (GMT+0) and I'm in Australia (GMT+10), so the line starts going up at 5PM last night, which is more or less when I plugged it in to charge. You can see, while 'off', it took 16 hours to charge to 100%, and this was from a 'cold boot' (phone is completely dead), so it didn't have any information about what had been running, etc.
Battery - Discharge: The five or so hours time in which the entire battery discharged, starting from when I woke up in the morning and got ready for work. In the Screen row, you can see the small, three-to-four second windows throughout the day that I turned the phone on to check the battery. For almost the entirety of the time, the screen was off. You can see where the line next to Phone State goes from black to navy blue. This indicates that the phone has been put into Airplane Mode - you can see this is also where everything relating to network connectivity or mobile strength completely disappears. You can also see that App Processor Wakeup completely dies here - that means that actual installed apps (including GOOGLE_SERVICES and Xiaomi's preinstalled Facebook app stop sending commands to wake the CPU.
Battery - Cause: At least once a minute, usually more, two things fire that keep the CPU running - Abort:Wakeup IRQ detected during suspend: 999 msoc-delta and Abort:Wakeup IRQ detected during suspend: 663 qpnp_rtc_alarm. I have no feckin' idea what either of those are, and Googling results in either developer guides or threads that lead nowhere. If anyone knows what they are, for the love of God let me know.
Battery - Foreground Processes: While the phone was off, with every app closed, in Airplane Mode, we can see that there are still four apps that are somehow in the foreground: com.miui.mishare.connectivity (odd, since there's no connection), com.miui.securitycenter (which I tried disabling through ADB last night, and it stopped my phone from booting. Oops), com.miui.notification, and com.android.providers.contacts (which disappeared shortly after entering Airplane Mode).
Battery - Video: You can see here, for the ENTIRETY of the time that the phone was turned on, this odd Video row was enabled. There is no other information about it - what causes it, where it's coming from, what 'Video' means, anything.
Battery - 7 Second Slice: This is just a close-up of a seven-second period of time, wherein the above 999 msoc-delta and 663 qpnp_rtc_alarm kept the CPU running six times within 7 seconds. Not a lot on its own, perhaps, but over the course of hours, it clearly causes issues.
I've also attached the latest bugreport where I took these screenshots from if anyone wants to try and make sense of it.
Click to expand...
Click to collapse
Same problem. Any solution?

Categories

Resources