Develop Bugs

Phone continues to lock up

Alright so ive used the search and couldnt find anything. I have a rooted s2 running eagles blood v1.1 and last night i flashed over lite'ing theme and now my phone screen will shut off and wont allow me to turn it back on, i have to hold the power button and it restarts. Ive reflashed eagleblood even recovered back to stock with just root and it continues to do it.
Any help would be much appriciated :/
Sent from my SGH-T989 using XDA App

Probably best to post this in the rom developer's thread. Any number of things can cause this behavior.

I would but my post count is low and i am unable to post there, so for now i am seeking help here.
ive tried un-rooting the phone, flashing the stock rom and no root, but have the same issue.

Did you wipe the caches in recovery?

treo...not! said:
Did you wipe the caches in recovery?
Click to expand...
Click to collapse
sure did, every time i reflashed/flashed i wiped everything

still contines, ive wiped everything, unrooted with factory resets, tried stock rom, eagles blood rom, reflashed multiple times.
screen shuts off and will not turn back on, have to hold power button and phone reboots.

IProbablyDidit said:
still contines, ive wiped everything, unrooted with factory resets, tried stock rom, eagles blood rom, reflashed multiple times.
screen shuts off and will not turn back on, have to hold power button and phone reboots.
Click to expand...
Click to collapse
Are you using SetCPU? I had this problem from a screen off profile where I could get calls or have my alarm go off yet not able to wake the screen unless I manually powered it off and on.
Sent from my EagleBlood-infused SGSII or my GTab 10.1 now "In Paris"

bhowanidin said:
Are you using SetCPU? I had this problem from a screen off profile where I could get calls or have my alarm go off yet not able to wake the screen unless I manually powered it off and on.
Sent from my EagleBlood-infused SGSII or my GTab 10.1 now "In Paris"
Click to expand...
Click to collapse
setcpu ? youll have to bare with me a little bit as i dont know probably all i should

odin back to stock with zedomax file! that usually fixes all probs
GRAB THIS STUFF :http://forum.xda-developers.com/showthread.php?t=1323878
Enjoy and also make sure u have the proper samsung drivers

movieaddict said:
odin back to stock with zedomax file! that usually fixes all probs
GRAB THIS STUFF :http://forum.xda-developers.com/showthread.php?t=1323878
Enjoy and also make sure u have the proper samsung drivers
Click to expand...
Click to collapse
i have tried this already, does not work :/

I'm having the same problem on rooted stock rom. It's getting more and more frequent. The phone just refuses to come back on after going to sleep. If I plug in the power/usb cable, it actually makes the connected noise as if it's actually awake but the screen stays off.
I've uninstalled all cpu and memory tweaking apps and am still experiencing the issue.

KaneHusky said:
I'm having the same problem on rooted stock rom. It's getting more and more frequent. The phone just refuses to come back on after going to sleep. If I plug in the power/usb cable, it actually makes the connected noise as if it's actually awake but the screen stays off.
I've uninstalled all cpu and memory tweaking apps and am still experiencing the issue.
Click to expand...
Click to collapse
ive tried everything, flashed over and over, un rooted, different roms etc nothing has worked so i just used zedomax's stock rom to restore the phone ( problem still continues) called tmobile and will have my replacement within a day or so, nothing else i can do i suppose.
though my problem did seem to start right when i flashed lite'ing theme for eaglesblood (not saying that caused it )

IProbablyDidit said:
ive tried everything, flashed over and over, un rooted, different roms etc nothing has worked so i just used zedomax's stock rom to restore the phone ( problem still continues) called tmobile and will have my replacement within a day or so, nothing else i can do i suppose.
though my problem did seem to start right when i flashed lite'ing theme for eaglesblood (not saying that caused it )
Click to expand...
Click to collapse
i had the same problem with the phone when i got it , i think its gotta be something with the phone.if mine continues then im sending it back also

tigerz0202 said:
i had the same problem with the phone when i got it , i think its gotta be something with the phone.if mine continues then im sending it back also
Click to expand...
Click to collapse
im starting to think it is a phone issue myself, going to find out Tuesday when my new one arrives though i am hoping it was an error on my part because this phone has the chance to be fantastic.

I was having random shutdowns with my 1st phone, the thing is I never did have stock long enough (rooted after 45min of gettjng) to see if it was the phone or root/rom(s).
My second phone is working great without any random shutdowns, but I'm still stock(running on second day of testing).
Gonna root and flash tomorrow and hope everything remains the same if not back it goes before my remorse period ends.
I really think it's phone related rather then a rom because I've never had this problem with previous phones.
So I would suggest on exchanging it.
Sent from my SGH-T989 using xda premium

htc2364 said:
I was having random shutdowns with my 1st phone, the thing is I never did have stock long enough (rooted after 45min of gettjng) to see if it was the phone or root/rom(s).
My second phone is working great without any random shutdowns, but I'm still stock(running on second day of testing).
Gonna root and flash tomorrow and hope everything remains the same if not back it goes before my remorse period ends.
I really think it's phone related rather then a rom because I've never had this problem with previous phones.
So I would suggest on exchanging it.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
i do appreciate the feed back, and from everyone who did give it. after lots of research and back and fourth between stock and custom roms i definitely wanted it to be the rom so it was fixable but im about 96% sure its the actual phone its self.

Phone goes into random boot loops and vibrates? Any help

Okay so ive been running jmt v8 for about a week on my phone and everything was running great. Then yesterday morning my phone became very slow and unusable. Then i started getting the error message acore system has stopped working and the phone would randomly restart and then it would start vibrating then stop then vibrate again and so on. So i insalled a new rom and i stopped getting the core system has stopped error but i am still getting the random reboots. And the screen also wakes up by itself. Please any help or suggestions would be greatly appreciated.
Sent from my cm_tenderloin using Tapatalk 2

I just had this fixed. There's something wrong with the power sensor, especially if it tries to boot the second you put the battery in without touching the power button.
Unfortunately you've been rooted now and because of the issues, you can't flash stock and reset the root count. So you can't sent to your carrier.
Fortunately, http://www.mobiletechvideos.com fixes EXACTLY this for $35 minus shipping it to them. I got my phone back today and it's just the way it was ROM wise and all my files are there and the issue is fixed.
This is a pretty common T989 issue.

Justananomaly said:
I just had this fixed. There's something wrong with the power sensor, especially if it tries to boot the second you put the battery in without touching the power button.
Unfortunately you've been rooted now and because of the issues, you can't flash stock and reset the root count. So you can't sent to your carrier.
Fortunately, http://www.mobiletechvideos.com fixes EXACTLY this for $35 minus shipping it to them. I got my phone back today and it's just the way it was ROM wise and all my files are there and the issue is fixed.
This is a pretty common T989 issue.
Click to expand...
Click to collapse
That's exactly my problem but are you sure this company is reliable?
Sent from my cm_tenderloin using Tapatalk 2

And can you also give me the link to the exact thing you ordered because i couldn't find it on their site, thanks !
Sent from my cm_tenderloin using Tapatalk 2

http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-t-mobile-power-button-repair/
And yes, I was sceptical too. Josh, the owner, is reachable by email and answers pretty quickly and did an amazing job repairing my phone.

You Can Boot into Recovery? Darkside Wipes, Flash another Rom, Dalvik Cache wipe,Format System,Fix Permissions.

Dennisalex said:
You Can Boot into Recovery? Darkside Wipes, Flash another Rom, Dalvik Cache wipe,Format System,Fix Permissions.
Click to expand...
Click to collapse
I can boot into recovery but its tricky because I have to press the buttons perfect or it'll just reboot. I believe the problem is with the power button and ill probably get it replaced.
Sent from my cm_tenderloin using Tapatalk 2

I have same problem last month, send the rooted phone to Samsung. After 15 days .I get back my phone for free.
I hope this can help you.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

For anyone with key issues and need to get into recovery or download mode there are adb commands that do this. We get too comfortable with apps and forget about the manual way of achieving a lot of the same tasks that apps provide for us.
From a command prompt:
adb reboot recovery
adb reboot download

playya said:
For anyone with key issues and need to get into recovery or download mode there are adb commands that do this. We get too comfortable with apps and forget about the manual way of achieving a lot of the same tasks that apps provide for us.
From a command prompt:
adb reboot recovery
adb reboot download
Click to expand...
Click to collapse
Thanks I will be trying this out.
Sent from my cm_tenderloin using Tapatalk 2

hey guys. after the ics update my phone started to lock up and its not rooted. now all of a sudden when i put the battery in it it vibrates once then starts to load and gets about half way and stops. then it turns off and just vibrates a few seconds and vibrates but the screen never shows anything. tryed using just a usb with the battery out and it skips the load screen and automatically starts vibrate looping. the power button seems stuck but i dont think i can fix it any ideas?

Hey everyone! I have a similar (but not quite the same) problem. Every now and then my phone "tells" me to restart it for maximum performance. Every time I restart or just turn on my phone it goes through the boot cycle, including a message that says "android is upgrading" (I got the ICS upgrade from Kies prior to rooting my phone). Then, all of a sudden, the phone doesn't work, and it starts the boot cycle all over again. This happens several times in a row, which for me is a safety issue because I'm not able to call Big Jon (my husband) to get me from the train late at night. Any fixes for that? Thanks.

sparkie6point0 said:
Hey everyone! I have a similar (but not quite the same) problem. Every now and then my phone "tells" me to restart it for maximum performance. Every time I restart or just turn on my phone it goes through the boot cycle, including a message that says "android is upgrading" (I got the ICS upgrade from Kies prior to rooting my phone). Then, all of a sudden, the phone doesn't work, and it starts the boot cycle all over again. This happens several times in a row, which for me is a safety issue because I'm not able to call Big Jon (my husband) to get me from the train late at night. Any fixes for that? Thanks.
Click to expand...
Click to collapse
You may have to run fix permissions in recovery are you rooted
Sent from my SGH-T989 using Tapatalk 2

Warranty exchange it. Known problem
Sent from my SGH-T989 using xda app-developers app

Same problem
And the vest part is that i can't replace it cause i live in India
Sent from my SGH-T989 using xda app-developers app

Damn! Just found this thread...sounds like what my phone started doing today!!
I was clicking around on gmail, then back to home screen, the camera FLASHED all by itself without me doing anything, then started the boot loop thing. Clicking the power button only made it worse. Finally was able to get into recovery via TWRP...but that was weird too. I did a factory reset/wipe and was going to reinstall The Sith ROM that I was running, but it just rebooted and loaded up The Sith anyway and it should have been cleared. I then tried to restore back to Beastmade ROM, restore was very quick and said successful but it booted back to Sith.
Now the power button is hyper sensitive! All I have to do is brush the power button and it will light up the screen. Touch it too long and it will bring up the boot menu. I'm afraid to actually CLICK the button as it might go haywire again.
WTF is going on!? This all seems really odd that it's going down with some of these new ROMs being released. I wasn't even touching the power button when all this started. The weird clicks and flashes didn't sound good when it was all going on.
Has anyone tried flashing back to and OLD rom to see if it will fix it?

change settings to interactive/deadline

[Q] Sleep of Death

I've read XDA for some time now but I'm not sure I've posted all that much since I can't post to the dev forms. Anyway, I just acquired a Kindle Fire and decided to put a ROM on it:
http://forum.xda-developers.com/showthread.php?t=1591850&page=213
I tried one from August and it worked well but the charge indicator didn't react to plugging it in so I found the 12/02 one and it was better but then I ran into the Sleep of Death problem. I decided to try a different one so now I'm back to 11/27-1605. I did a full wipe and used it all day with no issues. I left it for a few hours tonight, came home to it being dead. I did more searching and found something about CPU settings and the like so I've change that but I was wondering if there was a specific thread that I wasn't able to find directed at the Kindle Fire CM10 builds and this issue.
Any pointers for a KF noob?
thanks peterb

It sounds like the battery is dead. Try plugging it in, booting into recovery, and trying mounting the fire onto you computer as a flash drive. Then you can move a ROM like Jandycane over to it and flash it. Make sure you do a system wipe first.
Also, it might be a good idea to charge the kindle to 100% before copying over the ROM and trying to flash it.

jji7skyline said:
It sounds like the battery is dead. Try plugging it in, booting into recovery, and trying mounting the fire onto you computer as a flash drive. Then you can move a ROM like Jandycane over to it and flash it. Make sure you do a system wipe first.
Also, it might be a good idea to charge the kindle to 100% before copying over the ROM and trying to flash it.
Click to expand...
Click to collapse
It's not the battery because I can hold the button for about 10-15 seconds, release and then power it back up. Based on what I've read, it's the sleep of death issue. More reading lead me to mess with the CPU governor (setting it to performance) which seems to have helped out the snappiness of the device which is cool but it still got the sleep of death. More reading led me to SoftLocker Free. So far that seems to have taken car of things but will know more with time. I was hoping to find some feedback from folks who've run into this on the Fire and been able to fix it. I'll report back if this latest addition does indeed take care of it.
You mention the Jandycane ROM, is there a place to go to see the various ROMs are available? So far I like the ROM I've got as it's pretty standard Jellybean which makes it a lot like the N7's that my two kids have which is cool. I'd be interested in seeing what the other ROM's have to offer but so far my preference has always been for as vanilla a ROM or image as I can find.
thanks peterb

The sleep of death thing seems to be in the 4.1 kernel that Hashcode has been working on. He is the one that is working on getting us on CM 10. I believe Jandycane and SGT7 are both based on his CM10. That is why the sleep of death occurs on these roms. Once Hashcode gets more time, I'm sure he'll try to fix it. But until then... it is usually just a minor annoyance, at least for me. It is random, but does not usually occur all the time.
You could also try some of the CM 9 based roms, I believe there is also a MIUI rom based on CM9.
I am on the CM10 11/16 build. And it is usable most of the time. There are still a few quirks here and there.
Hope this helps.

With the softlocker free app installed the fire slept all night and woke up this morning as soon as the power button was pressed. So that seems to be the solution for me for now. If hash code gets it fixed that would be great but if this keeps working it's fine with me. BTW, thanks hashcode . The fire is great with this ROM.
Peterb

Q: Is my device defective?

Ok here's the deal, I have my device about 3 months and never had a problem. Since last week my phone kept turning off when I'm on the home screen, restarts when screen is off. So I was advice to try and hard reset my device which I did bunch of times and problems still continues. I did not install any apps when I hard reset it and I don't know what to do????

tsanchez31 said:
Ok here's the deal, I have my device about 3 months and never had a problem. Since last week my phone kept turning off when I'm on the home screen, restarts when screen is off. So I was advice to try and hard reset my device which I did bunch of times and problems still continues. I did not install any apps when I hard reset it and I don't know what to do????
Click to expand...
Click to collapse
Random restarting can happen with custom ROMs. It's happened to me with CM a while back. With you being on a custom ROM, that may be what is causing your issue.
Only way to really determine the cause is to view your logcat, which is tricky because it is cleared on a reboot. This app: aLogcat (free) might be useful. You can set it to save your logcats to your sdcard in intervals, that way it is persistant through a reboot.
You can monitor that and see what exactly is causing your issue.
You can also flash back to stock and see if the issue persists.

If you are running stock rom then your main board might be going bad. Someone sent me an article the other day about this happening to people. Apparently Samsung fixes it for free.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Galaxy S3 bricked... sometimes??

So, lately my phone has been acting kinda weird.. Basically, it'll shut off on it's own, no matter what my battery level or if I'm on the charger, its pretty random. When I go to turn it on, it shows me the samsung logo and shuts off after about 3 seconds of the galaxy s3 logo. It does the same in download mode and recovery. The phone will stay off and do that for an hour or more, and then itll turn on and be all dandy again for hours or at least another day. I'm going to take off all my pictures on the sdcard and odin back to stock as soon as possible for warranty, but does this sound like a hardware failure or software? I read about the s3 sudden death syndrome, but this one isnt permanent. Any ideas?

I agree with your assessments.

I'd wonder about overheating or a bad battery.
Sent from my SGH-T999 using xda app-developers app

what's your setup as of right now?

Beware if it shuts down when your flashing back to stock in the middle of the process it may never turn back on.
Sent From My Galaxy S3 Boricua 100%

It might be the kernel that came with the ROM you installed. I used to have problem with ktoon kernel.

I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure

mejorguille said:
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
Click to expand...
Click to collapse
If you have an app that controls kernel voltage that is still set up for set on boot and the voltage is too low when it boots or is granted root it'll kill it in this manner. Otherwise your phone is [email protected]#
Sent from my SGH-T999 infected with AnthraX using Tapatalk 2

I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.

I used the phone for work, not play, no overclocking was done neither was any undervolting. I ran stock kernel settings.
Aerowinder said:
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
Click to expand...
Click to collapse
I remember a time when XDA had helpful answers and users weren't reduced to insults. I've been around a couple years, hacked more phones than I can count and flashed hundreds of roms in my days, back when everything was still done in adb and terminal emulator. It's no wonder a lot of decent user has started moving over to rootzwiki