So, I have custom firmware that I flashed to my ROM over 2 months ago, if that matters.
Recently, when I was trying to send a message (as usual), it lost service, then reset the time/date to 4PM, November 29, 1999.
Please help, this is so confusing, even as a coder
Weird but I have seen posts on like xda that said 1969 when I flashed ROMs on my rezound. Maybe the data portion isn't talking to the section that updates to the current date and time. I have seen on my bolt flashing a new ROM it will show the wrong date and time until everything updates.
Sent from my Nexus 7 using Tapatalk HD
Related
Hi, I've scoured the forums here looking to see if anyone else had this problem. I found an old thread started back in May, but I am concerned with firmware 2.13.651.1 (the latest OTA). Since installing this update my phone now restarts 3-4 times per day, usually while idle sitting untouched on my desk. I hear a "buzz", look over and my phone is on the HTC startup screen. No rhyme or reason, just a completely random restart.
A little history, I had this problem OOB with version 1.13.651.1, it went away with OTA #1 - 1.22.651.3 (which had it's own problems, including lockup/overheating 3-4 times a day) and it returned with OTA #2 - 2.13.651.1. I am HTC Unlocked and have SuperSU/BusyBox installed, however I doubt those are my issue. Obviously I am running stock ROMs.
I've tested by doing a complete factory reset and letting the phone sit there idle on the startup wizard. Within hours it had restarted itself despite being untouched. I don't see a huge number of folks complaining about this issue here, so it must be hardware, yes? Do you think I got a bum unit?
I had this happen once today.. this is my second day on the new kernel.do not know if it was a fluke or related to your issue
Sent from my EVO using xda app-developers app
That is definitely not normal. You may want to relock and take it into Sprint. I have never experienced a reboot and I've had my phone since launch week. Or try a custom roms like MeanRom and see if you have better luck. You're already upgraded to the new base so you can just download and flash it.
Sent from my A500 using Tapatalk
Yep. I'm on EVO LTE #5. Strange part 2 and 4 did not have reboots. 1,3 and 5 do. Drives me nuts and sprint techs are clueless. With the lastest update it gives you a log of exactly why it had the errors. Yesterday I brought the log to the sprint repair and he said it was meant for HTC, not them.
I'm otherwords, he had no clue on how to read the log.
I'm hoping they fix this crap soon..they will not replace the phone anymore yet they can't fix it. I hate Sprint
Edit. Mine is stock, have not had one working good, long enough to root
Sent from my EVO using Tapatalk 2
Well, I took it into Sprint and yes they were clueless. Best they could offer me was to flash me back one version to the one the had blank notifications and overheated. I declined and went to HTC. They immediately issued an RMA. While I am not excited to get a refurb unit, I certainly am fed up with the constant reboots. Good thing I kept my old EVO 3D just in case.
FYI, I sent it back to HTC unlocked (but not S-OFF). I like to live dangerously.
My stock, never-rooted GT-I9300 (4.1.2, I9300BWELK1, JZO54K.I9300XXEMC2) is plagued by boot loop problems. It first started about 3 months ago, where the blue charge LED would suddenly come on and the phone would not wake from sleep. I pulled the battery, then when it was turned on it showed the initial S III logo, then the O2 logo followed by the glowing Samsung logo. Then repeated from the O2 logo endlessly. I pulled the battery again, then the next morning restarted it without the SIM or SD card in, and it had done a partial factory reset - i.e. lots of phone contacts were there with the texts, but all the settings had reverted to default. Later that day while on charge the same thing happened again, and I sent it away to O2 for repair.
When it returned, the same thing happened 6 weeks later although this time it was on when it froze and went straight to the O2/blue LED stage. Another repair (I'm fairly sure these 'repairs' were just factory resets...), and 6 weeks later exactly the same. Back to the O2 shop for another repair.
This time they replaced the 'main board' and when it came back it had a different Wi-Fi MAC address. This time only 6 days elapsed before the same fault arose again, and finally I was eligible for a replacement handset. This lasted 2 days before a boot loop condition occurred again! This time, being sure it couldn't be a hardware fault I tried my own /data and /cache wipe, which worked. I skipped all but the must-have apps, and I thought this was going to be stable but once more this past weekend the boot loop happened again (I've got my restoration procedure down to about 15 minutes thanks to the practice!)
I don't know what could be causing this and I'm fed up with resetting my phone. Are all S IIIs this unstable? I've never had a phone that required a factory reset within 18 months! When it is in the boot loop, I can access recovery and download modes, but safe-mode start-up has no effect.
The last remaining candidates I can think of are a problem with my SIM card, or a defect with my SD card... or an app. Can anyone suggest the best way to troubleshoot this? I'd really really rather not have to skip importing my settings as I have among other things many SSIDs I don't easily have access to re-create.
What ROM are you on? 4.1.2?
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
What ROM are you on? 4.1.2?
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Yes, 4.1.2. I don't recall this behaviour before I got the OTA update from 4.1.1 though
kernalk said:
Yes, 4.1.2. I don't recall this behaviour before I got the OTA update from 4.1.1 though
Click to expand...
Click to collapse
No, not all S3 owners experience this, a factory reset solves most of these issues however, if it doesn't, a trip to the Samsung service center will help.
I'd say it's probably a dodgy app, or some kind of unstable firmware update for your region/carrier, since hardware replacements didn't help with it.
Skander1998 said:
No, not all S3 owners experience this, a factory reset solves most of these issues however, if it doesn't, a trip to the Samsung service center will help.
I'd say it's probably a dodgy app, or some kind of unstable firmware update for your region/carrier, since hardware replacements didn't help with it.
Click to expand...
Click to collapse
Hmm. Thanks for the reply. I'm not sure I know anyone else with and S III on O2-UK but it seems to be news to O2, so I assumed it must be fairly rare.
I'm not sure about dodgy apps; testing them one app at a time isn't really feasible as it can take up to 6 or 7 weeks to fail judging by past performance. Are there any logs or similar that I can pull out somehow in the event of a boot loop? I've seen about logcats but I am not sure if this would be of use
Sent from my GT-I9300 using xda app-developers app
kernalk said:
Hmm. Thanks for the reply. I'm not sure I know anyone else with and S III on O2-UK but it seems to be news to O2, so I assumed it must be fairly rare.
I'm not sure about dodgy apps; testing them one app at a time isn't really feasible as it can take up to 6 or 7 weeks to fail judging by past performance. Are there any logs or similar that I can pull out somehow in the event of a boot loop? I've seen about logcats but I am not sure if this would be of use
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Everything to carries is "news".
I can't help with logs and whatnot, so I'll leave that to someone else.
You can always flash and downgrade to the older firmware that didn't give you a problem, if the problem persists, it is indeed an app.
Even when rooted, informative logs are nigh on impossible to get
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Even when rooted, informative logs are nigh on impossible to get
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
That doesn't fill me with confidence!
Thanks again for the replies. I'm not wild about downgrading. I liked the improvements! Is it possible to downgrade in a carrier supported way? Retaining warranty compliant has been rather useful in the past few months!
Sent from my GT-I9300 using xda app-developers app
You can flash any official via odin.
Sent from my GT-I9300 using Tapatalk 4
Well late Friday night it did it again. Not sure when exactly as I was asleep. Woke up in the middle of the night and went to check the time, Looked at my phone to find the blue LED on when it should have been red for charging or green for fully charged, and it was very hot - wouldn't turn on either. Pulled the battery but it kust went into the loop. I was away from home so I couldn't do any troubleshooting and had no choice but to wipe.
This time I didn't restore settings and the only apps I installed were SMS Backup & Restore and Puzzle Alarm (I know this isn't the culprit as I only started using it this week!). Gone are all my precious wifi SSIDs but otherwise I'm not sure I've noticed the difference.
So I'm now not connected to my work wifi, nor have I set up my work email or Lync - two of the things I use my phone for must after Facebook which I've also not reinstalled. Facebook mobile web is really hard to use by comparison.
By chance I popped into the O2 shop later that day and had the fortune to bump into a Samsung rep who had never heard of this and agreed that I was unfortunate to have these problems (how touching!) and suggested I speak directly to Samsung support rather than O2 which I will do this week. I will also contact O2 about a replacement SIM and look into replacing the SD too.
This is really silly. I'm not keen on downgrading the software because the first thing either Samsung or O2 will do is upgrade it again. Frankly at this point I'm fed up with the whole thing but I've got a year left on the contract and even a pretty much new handset like mine won't fetch enough.
I was just playing with my phone and thought I'd check for an update to phone software. Surprisingly, the message that usually pops (saying your OS is up to date) isn't showing up and instead, it just keeps searching. Is something brewing???
Don't know if anything is "brewing" but mine is doing the same as yours...Verizon V980 @ 7:55 AM CST.
What version are you using? Sprint got an update a week or two ago now
Sent from my LG-LS980 using xda app-developers app
I had to reset my phone a month ago and I'm still on VS98010B. Haven't seen a reason to update Is it strange I haven't gotten the update nag?
Hi all,
After Oreo update my Samsung Galaxy tab s3 wifi stock version looses date and time every time I turn off.
I sent feedback to Samsung Italy and they say that Knox is blocking date update.
They told me to bring it to assistance..
Obviously I formatted it so many times..
I just want to ask to community if I am the only one with this problem.
As a workaround I take data and time from internet.. but it's quite frustrating.
DJ Palmis said:
Hi all,
After Oreo update my Samsung Galaxy tab s3 wifi stock version looses date and time every time I turn off.
I sent feedback to Samsung Italy and they say that Knox is blocking date update.
They told me to bring it to assistance..
Obviously I formatted it so many times..
I just want to ask to community if I am the only one with this problem.
As a workaround I take data and time from internet.. but it's quite frustrating.
Click to expand...
Click to collapse
You are not the only one! This hapens to me every time I turn off or restart the tablet; even when I set date and time manually. Every time I restart or turn off, the same date and time is shown: october 29 2018(!?) 06:34am. With Nougat , I had no issue.
Kurimoulius said:
. Every time I restart or turn off, the same date and time is shown: october 29 2018(!?) 06:34am. With Nougat , I had no issue.
Click to expand...
Click to collapse
Last time I wrote the default starting date was 15th August.
After that date it started to store data!
Everything was OK.. Till some weeks ago: I received a security update so... Now the new default date is... 24th December!
So: now I have to wait till.. Christmas!
I can't believe nobody complains about this really bad thing!
I just restarted my Tab S3 no issues with the date. It is correct. What is the last update you received? My security patch level is April 1, 2018 and it says that is the latest for me.
My security patch is 1st August 2018.
Version is T820XXU2BRG3 but i think is something related to Italian version..
Fixed with latest firmware..
Inviato dal mio SM-T820 utilizzando Tapatalk
As I'm rooted, I have to manually check for updates via xperifirm. There was an upsated released: version 64.1.A.0.913.
Anybody updated and tested? Apparently camera apps have been updated! Any new features?
I wont get time to update yet, just thought I'd ask.
Thanks
Unless I'm mistaken, this update allows you to switch from android 12 to android 13
Huh we have android 13 for months now ...so i would say no .
Its for sure a security patch.
Chinese 72 got it 2 weeks ago , european 54 got it a week ago and US has to wait for another two weeks , i wish it would be all at the same time .
Hello,
The only feature I expericence since the upgraded is the "phone too hot warning" issue. I use the phone since late november without any trouble.
For the latest week, the phone displayed the orange warning sign and closed the camera app maybe 10 times. It couldn't even go through a 10 minutes google meet call...
It may not be related to the latest release, and I may be the only one having this issue...
viper. said:
Huh we have android 13 for months now ...so i would say no .
Its for sure a security patch.
Chinese 72 got it 2 weeks ago , european 54 got it a week ago and US has to wait for another two weeks , i wish it would be all at the same time .
Click to expand...
Click to collapse
Yeah, you're right about security patch. Thought perhaps something has trickled down from the new phone releases, like improved camera apps as they have changed their version numbers. Thanks
arthurham said:
Hello,
The only feature I expericence since the upgraded is the "phone too hot warning" issue. I use the phone since late november without any trouble.
For the latest week, the phone displayed the orange warning sign and closed the camera app maybe 10 times. It couldn't even go through a 10 minutes google meet call...
It may not be related to the latest release, and I may be the only one having this issue...
Click to expand...
Click to collapse
Ouch, sorry to hear that. I will update in a few days and see if I have the same issue. Though tbh, I havent had as many issues as some have, perhaps because of root and cleaning up some bloat and adding in adblockers etc.
You should do a full all apps cache wipe and see if that helps.
arthurham said:
Hello,
The only feature I expericence since the upgraded is the "phone too hot warning" issue. I use the phone since late november without any trouble.
For the latest week, the phone displayed the orange warning sign and closed the camera app maybe 10 times. It couldn't even go through a 10 minutes google meet call...
It may not be related to the latest release, and I may be the only one having this issue...
Click to expand...
Click to collapse
I had overheating problems with meet and 5g i was outside but on older different firmware.
You also have to understand now its summer time (probably in your country too) so you cant really compare november temperatures with current ones unless you did that in room with AC on.
I'm on the latest US version so still waiting for our update for this cycle. But since my last update, the phone has been very warm to the touch during normal use and I've seen the heat warning many times while using camera. I have never seen it before. Battery life is crap now too and used to be fantastic. Maybe you guys lucked out last month and the US version got whatever it was to cause the heating issues first? My last update was around 300mb so it was bigger that usual I think.
.913 QR reader from statusbar dont work. only black screen.
hasztagL said:
.913 QR reader from statusbar dont work. only black screen.
Click to expand...
Click to collapse
I had that sometimes on .891 ,couldnt get it to work no matter what but it goes away eventually with restarts .
Edit: i just got the .913 and qr reader works fine. Been using my phone before that for 2 hrs and no overheating ,after installing 913 and checking camera apps for 1 minute my top part of the screen got extremly hot but didnt show any overheating warnings.nothing changed so far in camera related apps (no portrait mode)