Related
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
bsander said:
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
Click to expand...
Click to collapse
Are you doing Apps to SD? It could be your card.
Did you move any caches?
Do you have any nandroid backups? (just fastboot flash if so)
Did you recently try to update to anything and fail?
Try to use the update.zip again. If that doesn't work then start over from scrap.
bsander said:
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
Click to expand...
Click to collapse
Wipe worked for me. It was sticking on the Android flash screen, but worked after the wipe.
Yeah, a wipe fixes it. Later today I stumbled upon a thread which suggested the problem is the "Contact Owner" app that doesn't play nice. Can anyone confirm that?
In answer to binary: yeah I do apps on SD but I've been doing that since ADP1.1, so I doubt the card is the problem. Didn't move any caches. Yeah I have a nandroid backup, and all the updates I did went smoothly. I had the whole system working for about 2 days until this happened (probably, because this was the first time I rebooted since installing Contact Owner, though I can't really remember that 100%)
bsander said:
Yeah, a wipe fixes it. Later today I stumbled upon a thread which suggested the problem is the "Contact Owner" app that doesn't play nice. Can anyone confirm that?
Click to expand...
Click to collapse
Contact Owner caused my phone to go into a reboot loop, but that was on the 5.02H build. I haven't had the guts to try it on JF1.5 or 1.5Hr3. If you look through the market comments for Contact Owner you'll see quite a few complaints of the same issue.
Hi there,
And sorry for reviving this old thread. I am the developer of Contact Owner an I kinda need your help in debugging this issue. I got a small number of messages from users of custom builds a while ago (about a month or two) but thought it was an issue with those builds.
Now it came back to bite me in the ass, as it seems the HTC builds in various countries (Canada, Sweden, South Africa) have the same issue: the phone goes into a reboot loop. I've tried (and failed) to install a custom build on my dev phone (almost bricked it) so I'm going to ask nicely if someone is willing to debug the issue for me. Please, please, please!
All that's needed is to install and run Contact Owner and if the device goes into a reboot loop, simply attach it to USB, run 'adb logcat' and then post the output. To recover from the reboot loop, simply start in 'safe mode' (hold Menu down while booting) and then uninstall Contact Owner.
I suspect the problem lies in SQLite, because I've seen similar complaints from Klaxon users and that app also sets the alarm message (which then ends up in a SQLite db, I guess). The Alarm Clock app that comes with Android also does that but I imagine it's because the message set by Alarm Clock is always short and has no newlines. I also don't think the issue is in Dalvik code, because the device should not crash if managed code causes an error.
TIA,
Paranoid Android.
Hi there,
I'm having a problem with my smartphone and i felt like this is the #1 place to ask for guidance on android issues over the interwebz.
I have a low-budget Samsung Galaxy Y GT-S5360.
It's running what it came with, Android 2.3.6 / Gingerbread.XXLK3.
30 minutes after having it, i foolishly decided i need more internal memory and rooted the device, in order to remove the useless apps on it.
It was a total slaughter. I think i even pwnd Samsung Apps app.
Anyway, device worked well for months after the bloody carnage, but recently backfired right into my face with random shutdowns.
I have no proper idea on the reasoning of these shutdowns but i've collected some data on the subject, here they are;
- It randomly shuts down almost every day. Just 3-5 times a day if it's on a good mood. Over 10-12 if it feels down.
- Device never shuts down while being charged or connected through USB.
- Device usually shuts down after i used power button to lock the screen.
- It's not being locked on black screen, it definitelly shuts down, not properly tho. (no small time vibrating)
- I feel like front sensors (which turns off the screen during calls) might be causing this, because lately it's shutting down whilst calls on my face. I even managed to shut it down by wiping the mentioned sensors with my thumb.
- Sometimes it can be shut down by brute force. I mean putting it down to table a little bit harder than average.
- My SDCard is problematic, it gets unmounted and says its damaged but i tend to ignore it and just reply with "sssh everything is gonna be alright" (format and reuse)
- I have only a handful of apps which contains bank & password apps etc. Nothing serious going on with my services.
PLEASE HELP ME OUT IF YOU RECOGNIZE THE SEMPTOMS.
What should i do? A custom rom? New battery?
Thanks in advance.
Bonus information;
I've never seen it shutdown with my own eyes.
It usually happens when its' screen is blacked out, when i put it in my pocket or table.
Or when i try to make a call and put it against my head.
So whatever is happening, it happens while the screen is blacked out.
It neves turned off while listening to music either.
straud said:
Bonus information;
I've never seen it shutdown with my own eyes.
It usually happens when its' screen is blacked out, when i put it in my pocket or table.
Or when i try to make a call and put it against my head.
So whatever is happening, it happens while the screen is blacked out.
It neves turned off while listening to music either.
Click to expand...
Click to collapse
might be you should go to recovery mode and do a data factory rest and also might need to clear the cache partition.
try it..
prafull07 said:
might be you should go to recovery mode and do a data factory rest and also might need to clear the cache partition.
try it..
Click to expand...
Click to collapse
Ah yes, i did that. Sorry that i forgot to mentioned it.
I've factory reseted it and while i was there i got curious and did the cache-clearing too.
But the problem persists.
straud said:
Ah yes, i did that. Sorry that i forgot to mentioned it.
I've factory reseted it and while i was there i got curious and did the cache-clearing too.
But the problem persists.
Click to expand...
Click to collapse
I think you should try flashing your stock rom with the help of Odin.
I've got an Idol 3 that has been randomly shutting down. No warning, no specific activity happening... it just shuts off.
I checked to see if there are any pending updates, no dice... it is up to date.
I was thinking to start deleting installed apps to see if it might be related to something that is running. If no help there, perhaps a factory restore.
Has anyone seen anything like this? Any suggestions?
If a factory reset doesn't solve it, it is probably defective and hopefully you can return it for a different one. If a factory reset fixes it. Only add your apps back one at a time to see if it was a particular app that was causing the issue. Let us know if there is an app that isn't playing well with the idol.
Factory reset is a really good way to pin it down to either software or hardware. Run it with just the stock apps for a day to see if it's solid.
Also, if you have a micro SD card in there, pop it out. If there's any issues with the card, or if that specific one just doesn't happen to get along with the phone..it can cause odd things to happen.
What were the results? My device is doing that too...
xycarp said:
I've got an Idol 3 that has been randomly shutting down. No warning, no specific activity happening... it just shuts off.
I checked to see if there are any pending updates, no dice... it is up to date.
I was thinking to start deleting installed apps to see if it might be related to something that is running. If no help there, perhaps a factory restore.
Has anyone seen anything like this? Any suggestions?
Click to expand...
Click to collapse
Check the temperature of your device as soon after a shutdown as possible.....turn off location reporting in location settings to cut down on gps use which I'm told can cause excessive heat if you find the temp is high (over 100F)
The phone was cold to the touch the last time it restarted which was a few minutes ago. Also I was running the system update and the phone got pretty hot and did not shutdown or restart.
Now that I think of it It wasn't having this restart problem till I ran the update... Maybe it got too hot and broke something...
It did get stuck on updating one of the app packages for a lot longer then the rest. Maybe the update didn't install properly?
I've been having the same problem since the most recent software update. It normally happens when I change the volume in my Opera browser.
Did a factory reset and it didn't fix the problem... Alcatel said to contact returns to get a new phone
I love the phone! I just wish this process hadn't came up. I hope they ship the new one fast, Alcatel has been communicating very fast.
I have the same problem. Only for about two times a week. Has somebody a solution?
Hi everyone, few days ago i got some problems with my phone.
When i am doing smth, for example chatting in whatsapp(it can be any app, even the menu) , the screen may freeze from 5 to 20 sec. After it, the device may become locked or not. Also, after it, device may reboot. Or just shutdown.
I already tried :
1 wipes (full via phone menu and recovery)
2 formatting flash via custom recovery
3 flashing 5.1 via odin
4 emergency restore via Smart Switch
But the problem is still here.
Is this a hardware problem, or should i try smth else?
Thanx for advice
I'm starting to wonder about hardware issues myself.
I'm getting the feeling that Samsung wound the processor too tight on these phones.
Once I get rooted again,I'm planning a proc' downclock to 2.3/2.4 Ghz.
I'm not totally sure,but if these proc's control the RAM directly,that might help with stabilty issues.
Just to confirm; you did a factory restore and also flashed the stock 5.1.1 for your model and region with Odin 3.10.7?
Sent from my SM-N915G using Tapatalk
yes, exactly. Not sure with odin version, but everything was fine.
Yesterday also tried River rom with Mickey Kernel. First few hours phone worked normally, but was a little bit slow (it is normal for this kernel). But then the problem returned, i got some (2 or 3 ) reboots and lots of freezes.
weird. I started gettig these issues a couple of weeks ago too. Did as you did, Odin, Smart Switch, TWRP. Nothing. On RiverRom it seems to be more stable than on the official Rom. Which is crazy. Searched through all the logs, only idea i got left is keeping in under android logcat on my computer until it crashes.
Also phone won't restart if I want to do that. Not from menu, not from TWRP. It will just not do it. It shuts down and no matter how much I press the power button.... nothing. Hve to take out the battery, wait 30 seconds, plug it back in, and it will start.
Any advices on what logs should be looking at would be much appreciated.
kalin12351 said:
weird. I started gettig these issues a couple of weeks ago too. Did as you did, Odin, Smart Switch, TWRP. Nothing. On RiverRom it seems to be more stable than on the official Rom. Which is crazy. Searched through all the logs, only idea i got left is keeping in under android logcat on my computer until it crashes.
Also phone won't restart if I want to do that. Not from menu, not from TWRP. It will just not do it. It shuts down and no matter how much I press the power button.... nothing. Hve to take out the battery, wait 30 seconds, plug it back in, and it will start.
Any advices on what logs should be looking at would be much appreciated.
Click to expand...
Click to collapse
I just tried to restart my, it booted normally.
Maybe its overheating or smth like this? It will be difficult to demonstrate this problem in service centre
honestly i don't think it's overheating. For me the behavior is a bit weirder, as said, as the phone won't restart, unless removing the battery and waiting for a minute or two before plugging it back in. Every. Single. Time. Not even rebooting from recovery.
I use now riverrom with the emotion kernel (they launched this year a new version of the kernel) and it seems to be better. Weirdly enough, the system gets slower when i turn on GPS (although i have next to nothing appls installed), and the apps that say they stopped responding are the boring ones. System UI, Google Play, etc. Also downloading the kernel auditor from the guys at emotion and enabling logcat seems to help too.
An error i seem to get constantly now is google play services error.
Bluetooth also seems to be an issue, i also have a android watch and it gets kinda weird behavior.
Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
marf3 said:
Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
Click to expand...
Click to collapse
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
pradctgign said:
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
Click to expand...
Click to collapse
I noticed problems with my ear speaker as well. And i cant make phone calls. The phone doent respond anymore when i try to.
Same problem after android 8.0 update
If you have installed the latest Google phone/dialer app, that is likely the problem, was for me.
Find the app in settings and uninstall,it will roll back to a previous version and hopefully fix your issues.
Sent from my Pixel using Tapatalk
My pixel does the same thing, ever since I updated to 8.0, have you tried doing a factory reset? I haven't done it yet, I have been uninstalling apps for the last couple of days, when it is in safe mode it works good, but when it's not, it freezes and restarts. I'm going to try uninstalling the latest version on google dialer to see if it helps.
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
droid4lif3 said:
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
Click to expand...
Click to collapse
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
wrong place sry
Had this on my pixel xl. I was on the 8.1 beta.
factory reset, rolled back to 8.0
8.1 ota official
haven't had a reboot in over a week now
Murrzeak said:
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
Click to expand...
Click to collapse
Yea, the issue is back, has been for about 2 weeks. This phone is really starting to be a pain in the ass, I can't believe that it happens so often. Did you do a warranty fix?
That's a pity. Yes, I did. Got the device roughly two and a half weeks ago. Flashed 8.0 and then sideloaded 8.1 right away. Knock on wood, all good. But there's still a report every other day in Buganiser of a phone even on 8.1 doing this.
Got mine at release. November 16. Google won't replace it either. I have a one pixel brick
I have the same problem. However, it is not frequent enough on Android P beta. But as soon as I go back to the stable build, it starts to do the same thing. Did you guys have any luck resolving this or should I send it back to the vendor I bought it from. They won't replace the device in Pakistan but may be will fix it in some manner.