Develop Bugs

Need help ASAP.

I installed the kingx bfs kernel #5 and after rebooting my phone, the phone would come on and start loading the widgets and all that good stuff. After about a minute, my phone would reboot and do the same thing. well after about 4 reboots, I pulled the battery and went to bed, thinking I would just download a new kernel in the morning and things would be better. Now when I try and start my phone up into recovery, it vibrates 3 times and nothing happens. The screen doesn't come up; nothing. It will still boot the phone up and load the widgets and then reboot itself again, but I can't get into bootloader or recovery.
I am running the leaked version of froyo that came out a while back.
any ideas?
*EDIT* ok somehow I managed to get into recover... idk how but I did. wish me luck.

You put your phone into some type of Debug mode. I'm assuming you have S-Off enabled? You are fine, you just need to unplug and remove the battery for a while when that happens.

happened to me when i put the CPU clock too high.
If you can get to recovery just flash another kernel or do a nandroid backup. Should be fine.
I've noticed setCPU locks up at higher frequencies w/ KK's #5. Not sure what you are running at, but i don't go much over 1GHz.

knock 3 times....
Speculation, if it makes you feel any better:
I seem to recall in the UnREVOked notes during rooting - that when one pushes the volume button up while pressing the power button, it triggers a harmless diagnostics run on the Qualcomm processor, yielding 3 buzzes - suspect that may have been the 3 buzzes.
Agree w/ other guidance posted to get you up and running again.
FWIW, just because a kernel is capable of going 119 and we can keep it 'to the floor' the whole time by overclocking in SetCPU - it doesn't mean the device will do it, nor that it won't nag you for pushing it so hard.
Some will work reliably/consistently @ that rate.. Some will not.

thanks guys. Setcpu was automatically setting the kernel to 1.13, and I believe that's what was happening as well. I had just enough time to get the setcpu up to see it and then it would restart.

[Q] Phone randomly booting (Android Revolution)

Heya.
I am running Android Revolution 2.0.16, Kernel 2.6.32.29_BUZZ1.3.3_OCUV with radio Radio_12.35d.60.140fU_26.06.03.24_M2.
I've been running this for ~1.5 weeks and I think this started about 1 week ago, not sure. Sometimes randomly (sometimes when I'm playing and sometimes when the phone has been idle for few hours) the phone boots. I see the white background with the green HTC logo and after a while it asks for my Pin number. Sometimes this happens once/day and sometimes it happens three times in a row. With stock it never did this.
What could be the cause?
How could I fix this?
I'm interested in Android Revolution 2.1 but can't find it after the 3.0 and 4.0 came along. I'm not ready for unofficial Gingerbread yet and 3.0 is using 1.84 for Orange and I'm not completly sure if I should use it with my unbranded Finland located phone.
Thanks for your time!

Hi. This has nothing to do with the ROM you are running it is a physical problem with the phone and is quite a common fault on the Desire HD.
It is a problem with the placement of the SIM card underneath the cover. I just stuck a bit of selotape across the SIM card to keep it in place and mine has been fine since. Other than that flash back to default and send it back under the warranty.

I don't think it's about loose Sim card. I tried to move the sim card while the phone was on the finally removed the sim card. The phone didn't boot but I got a message that said that phone can't locate sim card and I must either restart or shut off the phone.
This isn't what I mean with the restarting. It just restarts, boots, without any error message. Like I would have pressed the power button and selected restart.

Its because of the kernel, like mine your cpu seems to be sensitive to undervolt, try leedroids kernel
Sent from my Desire HD using Tapatalk

So although all DHD have the same type of CPU, each specific CPU reacts differently to UC/OV? Strange, how widespread is this? Personally I've had no problems.

Had the same random boots with revolution 3.0 and 3.1, reverted back to stock 1.72 with the same(BUZZ) kernel and same setcpu settings as I used with revolution, and reboots are gone for me

Heya. Thanks for the replies. I was thinking going back to stock too but decided to try Revolution 3.2 and it seems to work. Atleast one day without boots, but we'll see how it's in the long run.

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] Galaxy Nexus Reboot/Screen of Death Issues

Hello, everyone, this is my first post here, and after doing much research on my problem, I haven't had much insight into solving my problem permanently. tl;dr version is at the last paragraph.
First off, I installed AOKP on my phone for the first time a couple months ago and I had no problems for two months for reboots or anything like that, and I believe my phone was overclocked to 1520 mhz on the SmartReflex voltage settings. I did not undervolt whatsoever. In this phase, whenever I would turn it on, I would get to the boot animation, then the animation would hang, and the screen would rise to the highest brightness, flicker, and reboot, or shut down.
Then, in my troubleshooting, being the idiot I was, I accidentally unplugged it while I was flashing back to stock using ODIN. I got the "Android triangle computer" A.K.A. the "Soft Brick" signal. If I booted it normally, into my recovery, ODIN mode, whatever, I would get the same signal.
So, I left my phone alone for a couple weeks, accepting failure. Two weeks ago, I rebooted again into Odin mode, and I saw that Odin on my PC still recognized it, so I connected it and reflashed the stock ICS rom. I re-rooted and installed AOKP, all was fine for two/three days.
After that, the reboots started to happen again, and after a week of constant rebooting, and restoring latest backups,I set the CPU back to normal with no overclocking. I also undervolted but left "Set On Boot" unchecked for everything, This seemed to work fine for normal use, but I still had the phone on "InteractiveX" as the governor. So, when I would go to sleep, I would wake up and the phone would not be on. I would have to battery pull, reboot, etc. I thought this had something to do with one of the cores being turned off when the screen is, so I changed the governor to "Interactive" and the phone would charge now the same.
Now, the problem is, yesterday, I was fiddling with some benchmarks and I OC'd to 1520 for fun, and the phone screen froze, rose to the highest brightness, and shut down. I didn't have it "set to boot" so I thought everything should be fine, so I rebooted and the same thing happened at the boot animation which happened to me when I OC'd. I restored a Nandroid Backup I had before I set it to 1520, and still, no dice.
I reflashed my recovery then, because sometimes it would just freeze at the Google logo and not boot into recovery at all. Then, I restored my Nandroid again, and it booted into Android. After a few minutes, it crashed with the same "High Brightness, Screen Flicker". I restored again, and this time, I rushed into the "Performance Tab" and set my undervolt settings. The phone worked smoothly until I turned the screen off, and then I got the "Screen of Death". Basically, the screen stayed black, but the notification light was still on, and there was no response. So I pulled my battery and tried to reboot, but at the boot animation, the Nexus logo goes into "High Brightness, Screen Flicker". So, I took the battery out, and the phone is just sitting here now for fifteen or so minutes while I typed this out.
My question is, has anyone been having these same issues with their GNex. Because at this moment, I'm thinking I caused a hardware defect for running on 1520 for so long previously and I fried some inner components. Any help?
Edit: I put the battery back in and still the same thing. Going to charge overnight and let it sit, but if anyone has any help, please come forward.

Bump

First off, don't bump threads which aren't even a day old.
Secondly, if your device behaves like that when you UV/OC, have you thought about not pushing it so far?? Why don't you stick to stock for a while to check for hardware failure or if it's just you?
Edit: if it comes back, install stock through fastboot. Leave Odin. Don't OC.
Sent from my Nexus

Sorry
bk201doesntexist said:
First off, don't bump threads which aren't even a day old.
Secondly, if your device behaves like that when you UV/OC, have you thought about not pushing it so far?? Why don't you stick to stock for a while to check for hardware failure or if it's just you?
Edit: if it comes back, install stock through fastboot. Leave Odin. Don't OC.
Sent from my Nexus
Click to expand...
Click to collapse
First post here, didn't know much about rules. Thanks for the response. My Nexus did come back, just about 5 minutes ago. I'm going to stay on AOKP for a day and if I don't encounter any problems, I'll stay on it. If I do, I'll revert back to stock.

So yeah, **** this
bk201doesntexist said:
First off, don't bump threads which aren't even a day old.
Secondly, if your device behaves like that when you UV/OC, have you thought about not pushing it so far?? Why don't you stick to stock for a while to check for hardware failure or if it's just you?
Edit: if it comes back, install stock through fastboot. Leave Odin. Don't OC.
Sent from my Nexus
Click to expand...
Click to collapse
It was working fine until I got 3 or 4 Sleeps of Death a day until today. It just stopped working, and I restored my backup multiple times, but it would just hang at boot or bootloop. So I'm like **** this, so I flashed the stock image for 4.2.2 through Fastboot, and it still didn't boot, even after complete data wipe through the stock recovery. So, I thought it must be 4.2.2 that is doing this, so I installed the 4.1.1 and still the same result.
I'm so done with this thing, it's a hardware issue, total crap of a phone. If it is actually meant to be tinkered with and to be a "developer's phone" this crap wouldn't happen.

Random power offs

This has been happening for about 2 months now and has progressively started happening more frequently.
I've narrowed it down to a set of apps that are running when it happens.
Apps in use:
Screen On ( to keep the screen on while driving)
Waze (If you don't know what this app is stop reading now)
Play Music (Streaming through the Pioneer head unit)
It doesn't happen all the time but when it does the screen freezes for about 5 seconds then goes black and music stops the instant the screen freezes. Once the screen is black I try holding down the power button. Sometimes it'll power back on but most times I have to do a battery pull.
I've tried multiple ROM's and it still does it.
I've formatted my internal and external SD.
The last thing I still need to do is ODIN back to stock and then re-root.
Its taken me two weeks to get a logcat when the phone locks up. I'm not sure how much is needed so I'll attach the 2 hour logcat
Get Logcat here.
If someone can help me out and check out the logcat it would be extremely helpful. I can't ODIN back to stock yet because I'm on call all week and need a semi functioning phone till Friday.

I'm on stock unrooted NF4 and getting this sometimes. It happens when I am charging overnight. The next day, phone is off and I have to do a battery pull to turn it on. Luckily on those days I've gotten up before the alarm time. ?

p_synthesis said:
I'm on stock unrooted NF4 and getting this sometimes. It happens when I am charging overnight. The next day, phone is off and I have to do a battery pull to turn it on. Luckily on those days I've gotten up before the alarm time. ?
Click to expand...
Click to collapse
I had similar experience when using my phone as gps device in a long distance drive. Maybe because it got hotter?

Yesterday I was at the hospital with my son (he just had his tonsils removed). We were watching a movie Netflix and my phone locked up and rebooted 4 times within a 30 minute span. I finally had time afterwards to Odin back to stock and updated to NF4 then CFautoroot, TWRP latest and flashed Hyperdrive. I had hoped all was good but when i was cleaning out my car (streaming to the BT stereo) it locked up 10 minutes into my playlist.
Should I take it back to T-Mobile? Is there something else that I can do to troubleshoot?

Are you guys using any cpu apps?

Not that I'm aware of. I am using the compulsive kernel that is bundled with the latest hyperdrive.

Kernel issues, try other kernels.:good:

If you have a custom kernel, don't use setcpu in addition with the specific cpu governor app for that kernel. Also, don't set you minimum at 300 or lower. It's been documented to cause random reboots.

Not using setcpu. Was using the Hyperdrive tweaks to control frequencies.
I tried the latest compulsion kernel and within an hour it restarted twice. Tried the latest leanKernel and still rebooted. I guess I could go to stock, but I hate that music via bluetooth skips constantly on stock kernel.
The reboots are happening now at complete random, sometimes I'm using the phone other times I have the phone sitting on my desk and I'll look down and its at the Galaxy splash screen with the seandroid is not enforcing at the top.
I'm kinda lost at what it might be...I don't think its the ROM, and I'd really like to stick with hyperdrive just because for what I want in a ROM its all there.

wonderbread24 said:
Not using setcpu. Was using the Hyperdrive tweaks to control frequencies.
I tried the latest compulsion kernel and within an hour it restarted twice. Tried the latest leanKernel and still rebooted. I guess I could go to stock, but I hate that music via bluetooth skips constantly on stock kernel.
The reboots are happening now at complete random, sometimes I'm using the phone other times I have the phone sitting on my desk and I'll look down and its at the Galaxy splash screen with the seandroid is not enforcing at the top.
I'm kinda lost at what it might be...I don't think its the ROM, and I'd really like to stick with hyperdrive just because for what I want in a ROM its all there.
Click to expand...
Click to collapse
if u want to try something, when u ODIN flash the firmware, after it boots up, I ODIN flash TWRP then use my Stock Odex not rooted roms,then if u want root just flash SU from chainfire and install busybox,from the playstore, keep a copy on the sdcard and install.. and LEAVE the STOCK KERNEL, I use stock kernels and have no issues this way,
make a copy of my rom, remove the files u don't want from system/app and system/priv-app then flash that rom and SU right after that install busybox, and test that way. if u want I also have on the 3rd page a tethering rom, I have all the version, http://forum.xda-developers.com/showthread.php?p=51812491#post51812491
try it out, If u have problems, try not restore any data if u use titanium backup..