In latest build of CM11 I'm having SOd's very regulary..
I mean, I boot the phone, let him with screen locked for about 2, or 3 minutes and it never wakes up. Have to remove battery. It's been a day, I reflashed everything, clean sd card, clean flashed, only whatsapp installed, and no luck. Every ****ing 3 minutes this happens
Attached log.
Thanks!
EDIT: THE PROBLEM ONLY GOES AWAY IF I LET MY PHONE CHARGING. Then, no SOD's. Could be a voltage problem?
try flashing previous stable build and see if still there is a problem.
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.
Just putting this out there for anyone who may be having the same issue as a possible fix for them.
The wifes sgs3 would not go into deep sleep mode. as a result the battery was under constant drain.
her phone is set up pretty much like mine is and i wasn't having the issue and I couldn't seem to figure it out.
i did a clean flash but still the same problem. (wiped everything, even data)
I've been looking at BBS and wake lock detector for days but nothing was coming to mind, everything looked as it should.
i started removing apps, till there was nothing. still. same issue. tried different kernels. etc. still same issue.
I was about to move on to another rom (beans 18) to see if that would help. and i decided just for giggles to reflash the modem.
and what do you know upon reboot the phone started going into deep sleep mode.
I think i was running MF1 Modem and Bootchain with Mb1 TZ on her phone. but can't say for sure.
i downloaded the latest (d2vzw_VRBMF1_firmware) and flashed it. couldn't believe that is what the issue was.
anyways, if someone runs into the same issue. try flashing the latest modems or perhaps a previous and see if that helps.
My neighbor's 5113 is having some strange issues I hope I can get some insight on. I've worked with a lot of Samsung phones and am very familiar with flashing, Odin, etc but have not worked with a tablet before.
First, it has 4.2.2 on it. I tried the stock software update function and it says it's up to date. Is that true? Is 4.2.2 the latest official for this device?
Second, It's having lock up issues (see below) so I thought I would "Clear Cache" in stock recovery. It starts going through the process and then errors out. It just flashes ERROR and then goes back to the stock recovery screen. I've never seen that before. Any ideas?
Lastly and most importantly, it locks up regularly. It will lock up with the screen on (although it seems to take longer to lock up with the screen on with some motion.) When the screen goes off it will lock up quickly, normally within 5 minutes and it even locks up when charging up. The charging animation stops and you have to hold the power button for 10 seconds to get it to come back to life. It's very strange. It even seems to freeze when it's off. It won't just start by pushing the power button for a couple of seconds, you have to hold it for 10 seconds until the charging animation pops up and then push the power button for a couple of seconds.
I haven't reset to factory specs because she has a ton of info on the thing and I'm afraid if it errors out clearing cache, what might it do if I try a factory reset?
Thoughts?
Thanks for the help.
UPDATE: I did a factory reset via stock recovery and it did delete all the data. It still will not let me clear cache though. It still locks up whenever the screen goes dark. It will lock up in just a couple of minutes.
Very frustrating.
I would try flashing the stock firmware and see if that clears up the locking problem, after a day or so I would flash CM11 with gapps and take it from there.
After running stock rooted before flashing CM11 do a nandroid b/u just in case it acts up. CM11 IS SUPER stable, have run it on my P5113 for several years starting with cm10.
CM12 is still buggy don't trust it.
Pp.
PanchoPlanet said:
I would try flashing the stock firmware and see if that clears up the locking problem,
Click to expand...
Click to collapse
Thank you very much PanchoPlanet. I factory reset and reloaded stock firmware several times but it would still lock up as soon as it went to sleep. And I still could not wipe cache. Very strange. I went so far as to not set up any accounts and make sure it didn't download any software updates to make sure it wasn't some update that was causing issues.
It would still lock up even when it was off and just supposed to be charging the battery! So I really think it's memory is trashed.
But I would be more than open to listen to any other ideas.
Thanks.
Maybe there could be other issues that you are not aware of, like the tab having been dropped or liquid damage or even voodoo, who knows.
Sometimes people don't disclose all the details.
Pp.
PanchoPlanet said:
Maybe there could be other issues that you are not aware of, like the tab having been dropped or liquid damage or even voodoo, who knows.
Sometimes people don't disclose all the details.
Pp.
Click to expand...
Click to collapse
It looks to be in perfect shape. But in any event, if something like that happened then it's toast anyway.
Yeah, especially the voodoo. Lol.
Pp.
Hi,
i have oneplus device.
in the last few weeks, about once a day my phone is stuck (black screen, can't do nothing) (the Bluetooth for example is still connect, and the notification light blinking).
This enforce me to make reboot by long press on power button.
after this reboot i get the optimizing apps screen, which take about 20-30 minutes because i have a lot of apps (about 200).
this means once a day in a random time i don't have my phone for 30 minutes.
during driving so i don't have my gps and during important calls .
I really don't know what to do about it.
some more relevant info:
i had slimkat rom before (build 9.0) - the phone did random reboots but without the optimizing problems. (Those reboots which make me miss my alarm in the morning was the reason i moved to CM)
i did full wipe and install cm12.1 nightly from May 12 (made apps+data backup with Titanium and restore with Titanium).
i did dirty flash to nightly May 18 and again to May 26.
Im totally loss with this issue, i can't going on with this dead time every day, but i have no idea.
i feel like the stuck/reboot issue is maybe an specific app which make the phone crash,
and the optimizing issue on reboots is CM issue.
but i really don't have any idea about what to do.
is there some logs i can look at?
Thx a lot.
Gilad
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.