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?

[Q] Energy ROM Battery Question

First, I'd like to thank the DEV for the Energy ROM. I've run the last two releases and it is truly spectacular. The latest version with Hashcode's Kernel makes it a completely functional daily user (not that the SOD's in the last one made it any less amazing). I understand the battery issues associated with it, and have read through the workarounds in the DEV forum, but this issue seems to be beyond those. On any given day, I leave the house for work with a full charge and, even if I'm not able to use it during the day, I get home and am hovering around the 50% level. Not a big deal, but the last two days I've taken it a step further and did a hard power off before I left (held power for the 20s). When I got back 10 hours later and tried to power it back on, it was completely dead. First day I thought, just a fluke, maybe the power button got bumped accidentally. But two days in a row, while the KF was secured in a hard case, got me concerned. Is anyone else running into this sort of issue? This is by far the best ROM i've run on the KF, and tomorrow I won't bother to shut it down, but I'm curious as to what could be the cause. I'm running at the standard 1200/600 clock speed, but with it shut down, to my understanding I shouldn't see any significant battery loss, right? I'm definitely a noob when it comes to android, so if this is an issue easily remedied, I apologize up front. Thanks in advance for any help offered, and thanks again to all that made this ROM possible!

It's a known issue for older kernels (not sure about the latest one) that if you force the shutdown, it may sometimes turn on at random a while later - this is probably what happened, it turned on a while after you left it off, and then just ate through the battery during the day until you got back home.
If you have flashed the latest kernel, using the "normal" Shutdown option should work (not sure if the ROM would need to be updated or not) fine, so far I've never had it turn back on after using it, but I'm using Hashcode's ROM instead.
Otherwise, just reboot into TWRP and press "Reboot" - "Power Off", which will make it stay off... hopefully.

Thanks, I'll give it a try through TWRP and see what happens. FYI I'm running release #8 of the 3.0 kernel if that sheds any light on the problem
Sent from my Amazon Kindle Fire using XDA

I too had battery issues with EnergyROM... things seem stagnant there so I flashed gedeROM last night and so far so good.

psudeke said:
FYI I'm running release #8 of the 3.0 kernel if that sheds any light on the problem A
Click to expand...
Click to collapse
It'd be for the best if, at the very least, you flash kernel #10, as it allows for "normal" shutdown (ie, no need to go through TWRP or to force the shutdown by holding the power button 10-20s), though I'd recommend switching to Hashcode's ROM (better support, plus a few more ROM only features) instead, at least until everything slows down a bit.

Thanks for the advice. I'll take a look at his ROM as well. I thought about just flashing the #10 kernel, but i understand you lose some of the functionality of the kernel since the ROM isn't designed to take full advantage of it.
Sent from my Amazon Kindle Fire using XDA

[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] Phone Keeps Soft Rebooting

I'm using a T-Mobile Samsung Note 2 w/ Gummy Nightlies installed currently
Gummy: M3.0-09-02-14-NIGHTLY-t0ltetmo
The problem I'm running into happens consistently but not at predictable intervals. When the phone powers on, every so often while I'm using the phone, whether it be using the internet, browsing through Instagram or Twitter, or just scrolling through the apps my phone will perform a soft reboot.
I've tried multiple ROMs, stable releases, ROMs that aren't CM11 based, nothing seems to fix this issue.
Can anyone shed some light on what might the problem be and possibly a fix?
I'm not sure what else to include that might help anyone with diagnosing the problem, but if there is something that I forgot, I could definitely get you that information.

Have you noted this issue on TouchWiz Roms or is it happening on AOSP Roms exclusively?

Coug76 said:
Have you noted this issue on TouchWiz Roms or is it happening on AOSP Roms exclusively?
Click to expand...
Click to collapse
It hadn't happened on TouchWiz ROMs, but this just started happening about 2-3 weeks ago. I havent used a TouchWiz ROM in months. I've gone from OmniROM to LiquidSmooth to PacMan, to the most recent Gummy. From what I can remember its happened on the two latter ROMs.
It's strange because, I've called T-Mobile to have them send out a replacement battery, I figured that was the issue. I've had no issues with soft reboots while the phone was plugged into the charger, only when unplugged.
T-Mobile decided to just send me a new phone, so I reflashed to stock and im using my phone to send this message with no issues. So maybe AOSP problems?
What can I do to fix this?

Easy answer is stick with TW. That or try an older AOSP build and see if your issues go away. It may be that a specific commit messed with a setting you are running and issues start. I would do a wipe on the offending rom, avoid restoring data via titanium and see if the issues return.

Coug76 said:
Easy answer is stick with TW. That or try an older AOSP build and see if your issues go away. It may be that a specific commit messed with a setting you are running and issues start. I would do a wipe on the offending rom, avoid restoring data via titanium and see if the issues return.
Click to expand...
Click to collapse
The funniest thing just happened, it did it on the stock Firmware. My best guess would still be the battery. Good thing T-Mo sent the phone via Priority Next Day Air. I'll have it some time tomorrow

UPDATE: It now constantly just gets stuck in a boot loop when unplugged from the charger, but when plugged into the charger it has not a single issue. I've ordered a battery from Amazon, but I would still love to know what the issue might be. For example, I want to know why the battery isn't working correctly.

_lolzack said:
UPDATE: It now constantly just gets stuck in a boot loop when unplugged from the charger, but when plugged into the charger it has not a single issue. I've ordered a battery from Amazon, but I would still love to know what the issue might be. For example, I want to know why the battery isn't working correctly.
Click to expand...
Click to collapse
Did the new battery work?
I've got a similar issue ...
I was running Liquid Smooth 3.2 (4.4.4) with TWRP v2.7.0.1 and up until about a month ago, my 2 OEM batteries worked fine.
I was going to head out for the night, so I swapped to battery #2, it went into a boot-loop.
I thought it was a ROM issue, so I reflashed the ROM and still had the boot-loop, even after charging the battery to 100%
It wasn't until the next morning that I re-installed battery #1 and the phone booted fine.
Every time I swap to battery #2, the phone goes into a boot loop.
I ordered another OEM battery from Amazon and the phone goes into a boot loop as well.
The battery contacts on the back of the phone look fine.
I used the following procedure to delete the battery stats and it didn't help:
http://forum.xda-developers.com/showpost.php?p=38500258&postcount=8
I also switched to the JEDI Open Source Project (4.4.4) ROM and only battery #1 works.
I just removed battery #1 from the phone with it plugged into a charger and it remained powered up. I then installed battery #3 and it worked fine. When I rebooted the phone it went into a boot-loop again.