Develop Bugs

[Q] Phone wll not power on into any mode.

Hello. I am running SyndicateRom 1.1.0. I have been experiencing no problems with it. However, while attempting to watch a flash video in a website recently, the phone became unresponsive. Somehow I managed to get the power context menu up, and decided to reboot the phone this way rather than a battery pull. However, the phone is now powered off and will not power on back into the ROM, or for that matter anything; Download Mode, Recovery, will not even show the battery icon if plugged in.
I'm freaking out more than a bit. I'm well aware of how to restore my phone using odin and other tools, But if I can't even get out of a powered off state, I have no idea what to do. I'm also very confused as i was not doing anything particularly dangerous at the time with odin or flashing a ROM or anything. Any help at all would be sincerely appreciated.

Were you running Vision Kernal 1.2?
http://forum.xda-developers.com/showthread.php?t=1042552

nikon120 said:
Were you running Vision Kernal 1.2?
http://forum.xda-developers.com/showthread.php?t=1042552
Click to expand...
Click to collapse
I may have been actually. I believe I saw a post sometime last week (In the ACS main thread, in the OP first post) To try that kernel if you were having problems with crashes.... worked great -.-.

Yeah found the recommendation in the 1.1.0 Changelog where i saw it and followed it...
known bug (kernel): limited numbers of users experience freezes, IF YOU GET FREEZES, READ THIS OR TRY VISIONKERNEL

Sprint will replace it. Tell them you shut the phone off and will not come back on....that is all. Most phones were being replaced for free but there new policy is $35 worst case.
Do you BONSAI?

Noob Needs help

Hey all, I was trying to ask on the related threads in the dev section, but due to my post count, it won't let me.
I have a few questions that hopefully you guys will be able to help me with.
I have a rooted S3, still on T999UVALEM. I can't do the T-mobile OTA updates since it always fails, due to the root I'm assuming. I keep getting the annoying firmware update notifications and simply can't update.
I was considering loading a custom rom, but for some reason, CWM won't work anymore. I know how to flash with odin since it's easy, but I have no idea how to use ADB.
I tried reflashing CWM serveral times, multiple versions, including the latest, and I simply can't boot into recovery mode. I hold volume up + power + home, and I'll see the blue text at the top left, but after that it loads the Samsung Galaxy logo for a few seconds and goes blank. Eventually it will reboot if I keep holding the buttons, or if I let go, it will reboot again, but I can't get into CWM anymore. Anyone have a similar issue, or know how I can fix this?

Have you tried booting into recovery from ROM manager?

Try goomanager in the playstore and install TWRP instead and see if it works. It should if you are rooted.

ingenious247 said:
Have you tried booting into recovery from ROM manager?
Click to expand...
Click to collapse
I actually haven't. Going to try this now. I didn't even have it installed.. :silly:
edit:
Just did it that way, it works. Strange how I can't do it with the button combo...

Nexus Cable said:
I actually haven't. Going to try this now. I didn't even have it installed.. :silly:
edit:
Just did it that way, it works. Strange how I can't do it with the button combo...
Click to expand...
Click to collapse
More than likely you aren't doing the button combo right. You have to let off the power button after the phone vibrates when it switches back on, but continue to hold the home key and volume up key. Glad ROM manager worked for you, it's a great tool; I have had it on my last 4 phones haha
Sent from my rooted T-Mo SGS3.
If I've helped you, be sure to use the thanks button!

colbyrainey said:
More than likely you aren't doing the button combo right. You have to let off the power button after the phone vibrates when it switches back on, but continue to hold the home key and volume up key. Glad ROM manager worked for you, it's a great tool; I have had it on my last 4 phones haha
Sent from my rooted T-Mo SGS3.
If I've helped you, be sure to use the thanks button!
Click to expand...
Click to collapse
Not true
The correct way to do it (and yes I knew he was doing it wrong that's why I suggested ROM manager) is to hold all the buttons ONLY until you see that little blue writing appear at the top of your screen then IMMEDIATELY release all three buttons. Works every time, guaranteed.
Sent from my SGH-T999 using xda premium

And just to clarify when the above poster says all the buttons, he means Vol+, Home, and Power.

Thanks for your help guys. I got everything running the way I wanted it to. Only thing now is finding a ROM that has decent battery life.
With the old stock ICS rom, I could get 30 hours with light to moderate use. Now I'm getting 12hrs or so with Frosty, even less with M2, so I reverted back to M1/R7.

Check out Leankernel. It's supposed to be optimized to give maximum battery life.
CM10 based ROMs have pretty decent battery life for me. I get 16-19 hours of battery per day with screen on time between 3-5 hours running a 1.9Ghz overclock. Can't ask for much more. If you keep your CPU clock at 1.5Ghz on Leankernel with CM10, I don't see 24 hours of on time with several hours of screen on being a problem.

Xanatos57 said:
Check out Leankernel. It's supposed to be optimized to give maximum battery life.
CM10 based ROMs have pretty decent battery life for me. I get 16-19 hours of battery per day with screen on time between 3-5 hours running a 1.9Ghz overclock. Can't ask for much more. If you keep your CPU clock at 1.5Ghz on Leankernel with CM10, I don't see 24 hours of on time with several hours of screen on being a problem.
Click to expand...
Click to collapse
Nice. The only thing is that I like TouchWiz and would like to keep it. The Frosty ROM uses it so its a plus. Would I be able to run leankernel on this ROM?

ingenious247 said:
Not true
The correct way to do it (and yes I knew he was doing it wrong that's why I suggested ROM manager) is to hold all the buttons ONLY until you see that little blue writing appear at the top of your screen then IMMEDIATELY release all three buttons. Works every time, guaranteed.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
the problem that i am facing is, if i dont let go of the power button only, the blue writing wont show.

Unfortunately not. Leankernel was built specifically for CM10/AOSP ROMs. I'm sure there's a stock based kernel that comes undervolted which will help greatly with battery life.

[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

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

[Q] Anyone experiencing powering off and troubles switching it back on (charged)?

Hello guys,
I tried to search for a similar issues but I couldn't find anything similar so please bear with me.
My KF sometimes shuts down overnight. In the morning then I have troubles to switching it on again (clicking the power button, holding it for longer periods of time...). It usually helps for the tablet being connected to the charger, but it takes a few tries to turn it on. After I managed to turn it on again, for example yesterday, it had 80% of battery left.
I am using CM nighties and this is happening already for some time.
I am also using juice defender, I am not sure if that is relevant.
Do you have any suggestion, what could be the cause of this? Maybe a suggested alternative rom? Or some logs I can check? I think the powering on troubles bother me more than the shutting off overnight since I always think it won't come back on anymore.
Also, not sure if relevant. If I try to turn it on and it doesn't, sometimes the button flashes orange. After a few tries it turns green and powers on. Not sure if I am now not only confusing times, when it was simply out of juice.
P.S. On a different note, just curious, does anyone know how if there is a rom with working mic already?
Thanks in advance.
jkb

Yes, I sometimes have the same issue with the power button - in fact it happened to me this morning where I went from about 60% charge to 16% with a sudden power drop.
Not sure why this happens. I thought it was a bad battery so I changed it but am still getting the problem every now and then.
Sent from my Nexus 7 using xda premium

the only thing that i can think of is that during the middle of the night a soft-reboot happens and it cant boot back up into the system. this would cause it to sit there and continually try to boot up. this would use a lot of cpu and a lot of power. as for why that drains battery while being plugged in, well i cant help you on that.

Thanks for the input. I've wiped dalvik, cache and the system and installed hashcodes AOSP Jelly Bean (http://forum.xda-developers.com/showthread.php?t=2041694) and at least it survived this night without shutting down so maybe this helped. If I come across the same issue, I will update this thread with new info.
Thanks again,
jkb

Check this out:
amazon.com/gp/help/customer/forums/kindleqna/ref=cm_cd_pg_pg139?ie=UTF8&cdForum=Fx1GLDPZMNR1X53&cdPage=139&cdThread=Tx2JSJNEOWHGOIT
Sounds like a hardware issue, and Amazon has been replacing those of customers who buy new from them.
Mine has this issue too. I KNOW it has battery power, and is still on, but the screen won't turn on. Only solution is to plug in power, then hold down the power button until it shuts down hard. Then turn back on.
I'm returning mine because of it.

Thanks for the info. I am still hoping this is a software issue.Regrettably I am outside o the US and thus replacing it is nearly impossible. I will see, if the issue returns with the new rom and will update the thread if it happens again, just for your information.

jokob.sk said:
Thanks for the info. I am still hoping this is a software issue.Regrettably I am outside o the US and thus replacing it is nearly impossible. I will see, if the issue returns with the new rom and will update the thread if it happens again, just for your information.
Click to expand...
Click to collapse
Try going to the WiFi settings and selecting 'never' for keeping WiFi on during sleep. This seemed to work for me.... So far it hasn't happened again.
Sent from my Nexus 7 using xda premium

I think this is the bug I am experiencing:
Shutdown bug stalls out the shutdown. Looks like the device is off, but it's still powered draining battery. Currently requires long power button press to fully shutdown after the screen is black (about 15-20 seconds).
from the 3.4 kernel thread (http://forum.xda-developers.com/showthread.php?t=2264563). I am not sure if cm 10.1 nighties contain this kernel, but the description is pretty much spot on.I couldn't test the fix (holding the button for 15-20 seconds), since I already changed roms, but if someone experiences the issue again, he can post if this works and which rom and kernel they are using.

This happens to my Kindle Fire device as well. It just randomly shuts off and it won't come back on until I do a hard shutdown then turn it back on. I currently have AOSP Jelly Bean 4.2.2_r1 on it.

pwrdbykimchi said:
This happens to my Kindle Fire device as well. It just randomly shuts off and it won't come back on until I do a hard shutdown then turn it back on. I currently have AOSP Jelly Bean 4.2.2_r1 on it.
Click to expand...
Click to collapse
Yes, it happened again to me with the same ROM, but it happens less often. I will try the updated kernel once it is finished.

On May 27, 2013, Hashcode listed the known issues of the current kernel on his website:
Sound / MIC debugging
Deep sleep issues with “omapdss_dpi” device
SmartReflex shutdown loop fix.
Charging driver / OTG improvrments
Click to expand...
Click to collapse
Looks like they've been identified and are being resolved. :good: