Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
terragady said:
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
Click to expand...
Click to collapse
Honestly, there's not enough information to understand exactly why it's happening. You need to get a logcat in the time before the reboot; unfortunately, logcats get erased during a reboot so it might be a little tricky getting it if the reboot is seemingly random. Someone had posted this as a possible way of getting the log:
"Retrieving the logs is tricky, since the log cache gets erased on reboot. If the phone reboots even while sitting on a charger, try running adb logcat continuously (you will need Android SDK and USB drivers installed and configured on your PC.) When the phone reboots, look at the last several pages in the command prompt window for any errors or abnormalities."
Click to expand...
Click to collapse
Otherwise, it's hard for anyone to help. I'm not much help in actually figuring out the issue, but I know if you can get the log, someone else probably can help.
For more information on logcats: Logcat Tutorial
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
terragady said:
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
Click to expand...
Click to collapse
Check in advanced to see if schedule off is on
Nope it's off
Happened to me to on 4.0.2. Rebooted twice a day.
Solution to me was Qualcomm flash back to stock 3.5.1 and uodate from internal to 3.5.4. OTA 4.0.2.
The theard "how to unbrick".
Not one reboot until now in days.
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
terragady said:
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
Click to expand...
Click to collapse
It's possible. Not necessarily the reason, but it might be. Either uninstall the app or freeze it using Titanium. Greenify might also work, but that allows the app to start itself up and potentially continue the issue. See if that stops the crashes for a couple of days.
The problem is that it doesn't happen often and only when I quit the game and lock the phone immediately after that. I am not sure if that's a reason though, just guessing because it happens after this last time. I will uninstall this game anyway, it's just time eater
Related
hey guys, I don't know what's going on with my S7 but yesterday was working fine and out of nowhere everything started to FC! From twitter to "Google Services Framwork", Gmail, browser, tweetdeck, calendar, voice, I can't pretty much use it anymore, I haven't done any new app installations so i don't know what's wrong! is it just me, or anyone else having this problem??
Any help will be much appreciated!
Thanks
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
djdanska said:
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
Click to expand...
Click to collapse
ha! i remember I already did that. After the Update we had, and I exchanged mine for a new one I decided to stay with no root (i don't know why! lol) so I guess I'll reset everything and go back to root I figured at the end I was gonna do that, but I was trying to see if it was just me or there was a fix
thanks man!
ok, so since yesterday I've been trying to factory reset the DS, and when it boots back on, everything stays the same!
I'm a little confused now, if I take a picture and I turn the tablet off, when I turn it back on, the picture disappears. Same thing happens if I move widgets, delete or create new ones on the screen, they go back to as the configuration was on friday night! GV not working, and the last message that shows there, same thing, shows the last one on friday. I don't know what can I do.... should I call dell??
duck tape and dynomite
stupid thing started crashing yesterday FC this and FC that ....cant restore it as i no longer have write access to the internal sd card
1) tried nv flash
2) tried restoring from clockwork
3) tried pushing files through adb
4) tried fastboot ....
if i didnt just dump money into this thing id blow it up ......
any help would be appreciated.......any tips to fix it or kill it completely so i can get another one
actually deleted all of the files on internal sd card and uninstalled every program on the device looked completly stock ....rebooted it and it went back to how it was yesterday ......theres gotta be a reason why other are having the same problem that started on the same day .....maybe dell pushed an OTA update and screwed us ......just a thought cause mine was fine till i went 4g yesterday so my sis could post facebook pics ....not sure but hope we can figure this out
Samething happened to me
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
jz83 said:
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
Click to expand...
Click to collapse
I'm running stock, and I discovered the hard way that you can't let the S7 battery run all the way down. The S7 will not power itself down in time. I had the same issue, and the only way around it was to do a complete factory reset, using the menu button from the main screen. I think the reset is in the "About" section, but I don't have my S7 with me now.
Being used to WM6, which powers the device down at 5%, I was not expecting the device to do this, but there it is.
dell streak 7
im not sure if I am the only one with this issue you but becareful with the streak 7 mine well both of mine wont charge properly and the newest one wont charge at all. i have to send it back to dell for them to fix it. Im not sure what cause this but my only advie is to never use a different charger for it only dell chargers. Im guessing that it messes up the battery callibration and then it gets really hot when charging
Hey guys,
I could need a bit of help! It's now the third time I'm having this problem, don't ask me why. I've got the feeling that I read the whole forum here, but didn't find anything similiar.
The 1st time I didn't change anything (ok, rooted it, but nothing else)
The 2nd time I overclocked it slightly (~850-900 MHz)
Now I'm using MIUI.
But back to the problem:
I'm unable to use the keyboard, every time I'm sliding open the keyboard (even when it's turned off), it "crashes". The screen stops working or it freezes, the only way to turn it off is taking out the battery.
However, the bigger problem comes now: I'm barely able to restart it. It tries booting, but is restarting all the time or the screen is just turning on (in some angles you see that it is turned on but it's black). After many retries, it starts working, sometimes the bootloop is running 15min or i have to manually restart it 10 times or more. The strange thing is that the keyboard works fine, nevertheless I have to choose between using it opened (taking it with me becomes difficult ) or closed...
...the main problem now is flashing a new Rom, I'm currently trying it through the android sdk and adb, but using the power-button + x is easier
I don't think that I can solve the problem, I sent the device two times back (warranty till may 2012), but maybe someone here knows a bit more. My guess is that one of the sensors is broken, or some parts of the display that should manage the sliding process...
Anyway, thanks for your attention!
Web
If you already have Rom Manager, just click Reboot into Recovery..
inches0 said:
If you already have Rom Manager, just click Reboot into Recovery..
Click to expand...
Click to collapse
Tried to use one a time ago, but it wasn't working right....
However, now I'm not even able to boot it, the screen just flashes and turns off itself before trying to restart a few moments later....guess I lost my Milestone
Sbf back to stock?
taptaptouch said:
Sbf back to stock?
Click to expand...
Click to collapse
the computer isn't finding it anymore...I'll back up the data and try use my warranty... I hope that they don't complain about MIUI...
But I'm still not getting the point, why my mobile had these issues three times, although they "repaired" it twice...and nobody else is having the same problem
Heya all,
So my Galaxy Mini started rebooting itself today.. Anybody knows what to do? I can't give much details only that I thought the problem could be the custom rom (CM7, New Experience). I flashed it back to stock, but it's still doing the same thing, sometimes it'll hold out for 30 minutes but sometimes it restarts and I can't even open Whatsapp before it reboots again.
All I can tell the on/off button for locking isn't always working as fast as it should. Could this button be stuck or something like that?
Also warranty is gone, got water damage from like 1.5 year ago.. Maybe that could still have something to do with it.
Thanks in advance,
Sanderth.
Update: I was just viewing a WhatsApp message and it rebooted itself again, please does somebody have any advice on how to fix this?
Bump: Please does anybody know what the problem could be? Today at school I wasn't even able to send a message via WhatsApp
Edit: I'm pretty sure it always happens a few seconds after I pressed the on/off button to lock. I just tried to lock it, got the prompt where you can enable airplane mode and turn the phone off and I clicked the back arrow, after ~5 secs it rebooted, could something be stuck behind this button or could my ROM be bugged?
Edit2: Well I disassembled my phone, probably something was stuck behind my button and fell out or something else was wrong with it.. But the most important thing is: It works like it should again, locking is going smooth now and it really feels as if my phone was better than before XD
Next time I'll open it first before opening a topic on xda, but well.. Hopefully somebody who will ever have the same problem will find this thread and fix it the same way I did
:thumbup:
Sent from my GT-I9300 using xda premium
Well to be honest, it'll stick to randomly rebooting itself once in a while, less than it was before disassembling and putting it back together again though (From 5 times in one hour to max. 3 on a day). But trying this could never mess something up (as long as you know what you are doing.) At least it's possible to use my phone normally again.
For the people that don't know how to disassemble, use this: http://www.formymobile.co.uk/s5570disassembly.php
Disassemble until you've got the battery compartment of, then just assemble again.
I've got this little problem, if I reboot using Autoreboot (from the play store) or via the extended power button menu the phone reboots as normal initially but then hangs at the 3 network logo splash screen, where it hangs for around 30 minutes before finally turning on properly. Turning the handset on and off normally works perfectly however.
Is this a problem I've caused?
I'm running 290 Fw, UB, Doomlords kernel.
Look like some incompatibility to use the Autoreboot, he maybe doing something wrong. It's nothing wrong what you did, is just the app. I will suggest to use different application and see if the issues persist or even do not use Autoreboot because to me the phone should not be rebooted every day at all.
eclyptos said:
Look like some incompatibility to use the Autoreboot, he maybe doing something wrong. It's nothing wrong what you did, is just the app. I will suggest to use different application and see if the issues persist or even do not use Autoreboot because to me the phone should not be rebooted every day at all.
Click to expand...
Click to collapse
Thanks for the reply, I'll try using a different app, I have to reboot everyday unfortunately. If I don't the phone goes mental, starts freezing and jumping around, apps force close and it doesn't respond to touch or physical buttons. Rebooted once a night and it runs perfectly and I can't fault it.
I'll see what happens with another app though.
So, I was clean flashing Titan Prime back into my XT1064 after testing CM12.
Everything went well, same apps, same configurations as always, no major changes.
I was about to reboot the phone when it did it by itself.
The boot screen (you know, the white one that burns your eyes) showed up, then it went away, and then oh surprise!, it came back again.
So the phone was in this bootloop within the boot screen.
I tried to enter to the Bootloader and the key presses (Power + Volume Down) did not work.
Every time I would try that, the phone screen would stay off for as long those keys were pressed down, and then, Bootloop.
After many tries I was about to let the phone stay in the bootloop until I find a solution here on XDA.
But I tried one more time, and lo and behold, it went into the Bootloader.
From there everything went as normal.
Now, the question is, could I have bad sectors?, could the Bootloader be corrupted?, could I have a ghost trapped?.
Thank you for answers and/or ideas.
And if any of you happens to be in my same situation, do not give up, let it be, try many times, and it finally will work (hopefully)
Strange. There wouldn't be bad sectors in internal memory. If it was me and I had your phone I'd try a complete wipe again. Of course that would be scary because you don't have a clue as to why it happened the first time. I wonder if it's your power button going screwy or maybe sticking.
That's the worst kind of problem, you do everything right and it still screws up then mysteriously fixes itself.
Did you maybe do any special changes/settings or similar things?
As Teil864 al ready says, you could reflash your rom and hope it'll never happen again.
Tel864 said:
Strange. There wouldn't be bad sectors in internal memory. If it was me and I had your phone I'd try a complete wipe again. Of course that would be scary because you don't have a clue as to why it happened the first time. I wonder if it's your power button going screwy or maybe sticking.
That's the worst kind of problem, you do everything right and it still screws up then mysteriously fixes itself.
Click to expand...
Click to collapse
You do everything right, the phone gets screwed, it gets fixed, and the problem is something no one else has had so you have no freaking idea of why or what it was.
It is not my power button, the only times I use it is when I turn the screen on, and it would not be the reason because it made a difference when it was pressed.
I will try some fastboot commands to scan sectors, but I need to remember how they worked. The last time I used them it was when I had a Galaxy Note 1.
Lars124 said:
Did you maybe do any special changes/settings or similar things?
As Teil864 al ready says, you could reflash your rom and hope it'll never happen again.
Click to expand...
Click to collapse
As noted on the first post, I did not do anything out of the ordinary. Same apps, same configuration as always.
The good thing is that I now can say I have every app that I need, with the configurations that I need, so I almost never need to change.
Let's hope it will not happen again.