I woke up to see my watch saying it was synching. 30 minutes later it went back to the normal screen.
Two hours later synching again, 30 minutes or so later back to the normal screen...
Two hours later... rinse and repeat.
Now it's doing it again! Any idea what is going on? I have not seen any notice of an update, and when the sync is done and I check the system version, it's not on 6.x.
Thanks!
Related
I was using tweetdeck like any other moment I would & left my phone on a table. When I took it again in a couple of a minutes the screen wouldn't turn on. I can go through menus I think, take pictures & such. It doesn't even light up when someone's calling me. I tried to update/repair it but I can't select connect on a screen when I want to connect it with a PC. I can charge it, it responds to a PC, but the screen seems dead.
I updated it yesterday to a new version of 1.6 because I'm still waiting on 2.1 so that build of software could be bad because this has never happened to me before.
From what I see, all I can do is to wait for the battery to drain out.
Does somebody know what the hell happened?
Have you tried rebooting your device (use menu bytton and power button together for 5-10 seconds)?
Yep, that did it. I didn't have time to reply lately. Sometimes it also took 7-10 seconds to get out of standby. I updated to 2.1 so I hope that won't happen again, everything is much faster.
I'm in the middle of SBF flashing my phone, and it's been going for at least an hour and a half and it's been stuck on "creating image file" and says "executed: 0%"
How long is this supposed to take roughly? Should I just leave my computer running into the night to finish this?
EDIT: Alright, it's starting to move past 0%. Currently at 19%. I guess it just takes a while to get going.
It took me maybe 20 minutes total.
It took me roughly 2 hours, but it did get finished (thankfully).
TheJuxe said:
It took me roughly 2 hours, but it did get finished (thankfully).
Click to expand...
Click to collapse
Wow. I have never had it take anything close to that long. Maybe 10 minutes or so. I've done it numerous times.
Guys, need your help. I've had this phone since launch day and am way beyond my 30-day return/exchange policy. Completely stock w/ 3 downloaded programs (bank apps) and all updates applied. Here are my problems:
1. Random rebooting or dead phone. This doesn't happen often, but I think I've narrowed it down to the GPS navigation. Sometimes after using the GPS I've witnessed the phone continually reboot every 15 minutes or so. Just laying on the table and it'll spontaneously reboot. The only way to stop it is to pull the battery. Earlier today I used the GPS for a quick trip, ended the program, then turned the phone off. About 1hr later, I tried turning the phone back on... but couldn't power on or anything. The only fix was to pull the battery.
2. The damn GPS program takes SEVERAL MINUTES to lock on. I have to pull the car over or just wait until it locks on. I thought one of the updates was supposed to fix this. WTF?
I've tried factory reset w/ no apps installed. Even took it to the Sprint store but the rep said he couldn't do anything for me since I'm beyond 30 days besides resetting the phone.
I'm really frustrated since I upgraded my plan and renewed for 2 more YEARS.... Any suggestions?
Check out the thread on battery tips. I also posted a thread about how my phone would randomly reboot or shutdown. The problem was the battery was not making full contact all the time, so I put a piece of rubber band on one side of the battery to make a more snug fit and haven't had a random reboot since.
Hi,
Just wondering what steps I should take next and if this has happened to anyone else.
My phone constantly reboots or gets stuck at the boot logo and requires a battery pull the past few days, only between 3pm and 8pm. The rest of the night and the rest of the day the phone is perfectly fine.
It started Monday 10/3. I took the phone out of my pocket as I walked to my car 5pm after work and noticed a reboot...but thought nothing of it. At dinner time I put the phone in the table and noticed a reboot...but since the phone worked still...I ignored it.
Tuesday, starting at 4pm...my phone rebooted many times..or was stuck at the boot logo...making the phone unusable. I ate dinner with the phone off...and it was fine after dinner.
I decided to swap to a spare battery. Both genuine Lg batteries...direct from Lg. Wednesday...the phone was on my desk...and around 415pm the phone rebooted without me touching it ...just sitting in my desk. Unusable again until 8pm...no matter how many times I pulled the battery.
I was charging my phone from 1pm - 4pm everyday...so I thought it might have something to do with the battery being full.
Today, Thursday...same thing as Wednesday, except at 3 pm it started rebooting and getting stuck. Lasted until 8pm. This time I didn't charge my phone in the afternoon.
Any ideas? My phone was rooted 6 months ago...but I never installed any Roms or anything...just rooted it and kept it stock.
ButterPhone said:
Hi,
Just wondering what steps I should take next and if this has happened to anyone else.
My phone constantly reboots or gets stuck at the boot logo and requires a battery pull the past few days, only between 3pm and 8pm. The rest of the night and the rest of the day the phone is perfectly fine.
It started Monday 10/3. I took the phone out of my pocket as I walked to my car 5pm after work and noticed a reboot...but thought nothing of it. At dinner time I put the phone in the table and noticed a reboot...but since the phone worked still...I ignored it.
Tuesday, starting at 4pm...my phone rebooted many times..or was stuck at the boot logo...making the phone unusable. I ate dinner with the phone off...and it was fine after dinner.
I decided to swap to a spare battery. Both genuine Lg batteries...direct from Lg. Wednesday...the phone was on my desk...and around 415pm the phone rebooted without me touching it ...just sitting in my desk. Unusable again until 8pm...no matter how many times I pulled the battery.
I was charging my phone from 1pm - 4pm everyday...so I thought it might have something to do with the battery being full.
Today, Thursday...same thing as Wednesday, except at 3 pm it started rebooting and getting stuck. Lasted until 8pm. This time I didn't charge my phone in the afternoon.
Any ideas? My phone was rooted 6 months ago...but I never installed any Roms or anything...just rooted it and kept it stock.
Click to expand...
Click to collapse
You say it is only happening at very specific times? Try setting system clock to the time when it usually happens to see if it is some sort of software issue. If you can trigger by changing clock, then reflashing stock rom should fix it. If not it may be a underlying hardware problem.
I feel like it may be a charging issue. Ive had it reboot when charging in the car now...or shortly after it charges...so not just a time issue. The odd thing is it happens to both my batteries.
I got a new phone yesterday anyways. Apparently yesterday was the last day best buy let's you do a 2 year contract upgrade on the everything data 1500 plan. I think the only way to get contract pricing is through sprint.com now. So I'm glad I got in on the best buy deal.
This is the 2nd time, in 6 days I am facing this problem. I am on "SoLdieR9312s G96XBRGA ROM" (7.2 at the moment). From the 1st day I am on this ROM. With no reason, the phone is freezing, with no response. After few minutes, can turn it off, but I need to wait few minutes more to power it on again (Previous time, it took about 10 minutes to power on.). I tried to plug in it to adapter, but it looks like the phone was completely dead (no charging at all)! After that "death", in about 10 minutes, the phone has returned to its "normal state". After update from 7.1 to 7.2 and 1 hour on this newest update, the phone is "dead" again. This time, it can't reboot to system and can't go to twrp either. Only I can go to "Download Mode", but this time my laptop can't recognize the phone!
What am I supposed to do? Any help?
Is this problem with mainboard or something is wrong with the system?