After getting perma root and installing Bacon bits 0.3, when I want to turn my phone off completely it instead just boots back up into the recovery. Does anyone else have this problem or have any ideas how to resolve it?
Sent from my T-Mobile G2 using XDA App
I have no idea, but noticed it too...
Sent from my T-Mobile G2 using XDA App
I am apparently having this problem as well now. I never noticed it before and even after a battery pull my phone seems to boot back into recovery. Any help with this problem would be greatly appreciated. Thanks in advance!
One thing to note is that you need to make sure that you don't have it plugged in and charging. It's known to boot on its own when you do that. I'm not sure if that is a bugged feature or not, but I also have Bacon Bits installed and can shut down fine.
Although, my phone stays on all the time.
Sent from my T-Mobile G2 using XDA App
Ok just tried to turn off my phone with it unplugged and it did not turn on to recovery. So kind of a boo bug for now but I am sure that it will get worked out.
Heh... I'm guessing you all have Clockwork Recovery installed? That's the problem. At least, when I switched to the test keys recovery, it wouldn't constantly start back up with any power regardless of how I shut down.
hmm..i have baconbits installed and dont have this problem. ill look into it
Hi
I have a rooted stock ROM/Theme MT4G which I noticed last week that it stopped going to sleep. If I set the timeout to 15 seconds (or anything) then right after the timeout is reached the screen sleeps and then within a second immediately comes back on (to the lock screen). It keeps doing that no matter what settings I try. This of course kills the battery life with my screen being nearly 100% of use.
I thought it was related to an app update so I removed nearly everything I could to no avail. Thinking that it was something related to the ROM I decided to try a different ROM. I installed CM7RC2 and low and behold the same problem persisted. I had to disable trackball wake for this problem to go away. I then tried several other ROMs and the problem still remained. I've attempted the various Royal* ROMs and the same problem persisted. Any Sense based ROM was problematic since I had no way of disabling Trackball Wake so I'm now running CM7 (nighties).
The other snag I'm having is that I too have the problematic power button but in my case I have to REALLY press hard to operate the power button which of course is annoying.
Anyone have any suggestions or experience with this sort of problem?
Thanks.
Did you check out the Cyanogen mod 7 in settings ?
I did. That's what I'm running now.what exactly are you suggesting? Thanks.
Sent from my HTC Glacier using XDA App
I have the same exact issue, ive been trying to get some devs to add the disable trackpad wake option in sense roms but so far nothing so right now i use either royalginger or royalmiui im on miui but i really miss sense :/
I had the same thing. I booted into recovery and wiped data and cache and flashed again and everything worked.
Sent from my glacier using XDA Premium App
Nicgraner said:
I had the same thing. I booted into recovery and wiped data and cache and flashed again and everything worked.
Sent from my glacier using XDA Premium App
Click to expand...
Click to collapse
Yeah ive tried that be4 with no luck
Nicgraner said:
I had the same thing. I booted into recovery and wiped data and cache and flashed again and everything worked.
Sent from my glacier using XDA Premium App
Click to expand...
Click to collapse
I must have done that a bunch of times already but nothing worked except CM7 because I can disable the trackpad wake function. I wish Sense based ROMs allows for disabling the trackpad...that would be greatly appreciated. An even more helpful feature is the ability to remap the buttons.
Is it possible your trackpad is defective? DO you notice other odd behavior that could be related to it?
If your using google voice its the application doing that you can fix this on cm 7 by moving the application to the Sd card.
Sent from my HTC Glacier using XDA Premium App
I believe this is a real hardware issue... It seemed that the optical sensor in the trackpad is broken and it's always sending signal to the kernel telling that it detected activity but in reality nothing was going on, so the kernel can never go into power saving mode.
Sense UI is a CLOSED SOURCE software, there's nothing you can do to patch it.
Since ALL MT4G are still under the 1 year Manufacturer's warranty, you should call T-Mobile/HTC to get it fixed or just get a replacement....
Ok I found a solution for us mt4g owners with the messed up trackpads, you are gonna have to flash virtuous unity rom v. 2.39 and then apply this patch:
http://dl.dropbox.com/u/28766802/Virtuous/trackpad_disabled.zip
This patch was made by one of the developers of the rom chrisch1974 specially for this issue, so good luck =D
Same problem, but found work-around
My phone (MT4G) has the same issue but I know why it happened. I got caught in the rain and although I had the phone in my pocket, it got wet. Everything works except that. I left in a bag of rice overnight to no avail.
Anyway, when I press the power button to send it to sleep mode, it just comes back to the lock screen. If I let it time out, it goes out but comes right back to the lock screen. Sounds familiar?
What works for me is holding the home button (the one with the sensor) and, while still holding the home button, pressing the power button once. It is then that I let go of the home button.
Works, but sometimes I have to repeat this charade a couple of times before it sticks. Usually have to repeat it when I don't fully press the home button.
Anyway, hopefully this will help someone that is stuck with this phone and is unable to get a replacement.
My phone froze so i did what i normally do and thats pull the battery, replace and reboot. While the phone was booting up i held down the vol key trying to not wake my girlfriend up since its quite early in the morning. Once booted back up i saw the words "safe mode" in the bottom left hand corner. Now i understand what safe mode is for the PC and have used this function many times before but i'm really not sure why and what use it would give to our HD2. Could someone shed some light on what this might be good for on a mobile phone?
I also noticed that all my downloaded apps are missing while in safe mode but after a normal reboot the safe mode disappeared and my apps restored to normal. For reference there is a picture below of what I'm talking about. I'm using the latest version of CoreDroid if anyone cares to know. I took the screenshot using DroidExplorer since i did not have any access to my downloaded apps and even after i downloaded a new screenshot app from the market it would not see it in the list or the gallery. Only after a reboot could i see and use my downloaded apps again.
On a side note while using DroidExplorer the hue of my wallpaper seemed really off. Does anyone know of a fix for this?
So I take it no one else has held down the volume button during boot? Every time it goes into safe mode. I would really like to know what use this would be on a cell phone so if anyone has any clue, please let me know.
My volume buttons got stuck once and it happened to me too, if I understood what I read correctly it is a tool to allow you to start up the phone if an app has caused it to become unresponsive. I am assuming that it is more for people developing apps to be able to start up and remove their mistakes.
Sent from my NexusHD2 using XDA
This was kind of what i gathered because when you run in safe mode all user apps disappear. Well i though it would be useful if I ever made a mistake and installed something that messed my phone up but your explanation of being designed for developers makes perfect sense. Thanks!!
Hey XDA,
I received my 16GB Nexus 7 from Google 4 days ago. I immediately updated to 4.2.1, rooted, and then flashed franco.Kernel. I was running the latest update to franco's kernel, and had left the settings untouched from the defaults with interactive governor. Yesterday I flashed the latest nightly for Cyanogenmod.
I was using the Facebook app when my tablet ran out of battery (I intentionally let it die), and after it powered itself off, I plugged it in with the charger provided to me by Asus/Google. Because I am new to this tablet, I wasn't aware that plugging the charger in meant that the device would power on. Anyways, it did power on, and I had no plans to turn it off now that it had turned itself off. I went to turn the wi-fi off so that it would charge with less power drain, but just before I turned the wi-fi off, the device began to power down again (The charger is still plugged in, and it didn't become unhooked at any time). I begin to walk away to do other things while it turns off again, but I stop when I hear a weird grinding noise. It's hard to explain, other than it sounded like a kettle getting progressively louder and then shutting itself off when it reaches its desired temperature, only it sounded like gears and not a kettle.
A little worried, I wait a bit and then I turn it on. I'm relieved when I see the Google logo appear, and then the Cyanogenmod logo appear. After a long boot, I'm greeted by a black screen with what tiny white flashing dots randomly appearing. I turn the device off, and restart it. Same thing, only now it seems like there may be more flashing white dots than the last boot. I unplugged the device from the wall, and force shut it off (power + volume keys).
I've never heard of this happening before, which is why I'm hoping someone can give me some advice. Obvious things for me to do would be to flash stock 4.2.1 onto my Nexus 7. The reason I haven't done this is that I'm worried that my device may now be dangerous (battery melt, processor malfunction). Does XDA have any recommendations before I phone Google? I'd like to avoid Google because I've voided my warranty with them by rooting and flashing a custom kernel, so any other help is MUCH appreciated.
Thank you so much for reading my essay, and for taking the time to help,
Robert
Do your very best to revert it back to stock os and kernel and re lock the bootloader. Yes it is possible. Look for the nexus 7 toolkit. Then send it to google/asus. Best I can think of dude.
Sent from my MB612 using xda app-developers app
I have heard people with similar issues start device in bootloader and leave it there to charge to prevent the on/off loop and after a few hours when charged boot normally.
Hope this helps
Sent from my SGH-I927 using xda app-developers app
The screen with white dots has turned into what appears to be a screen with no signal like you see on tv's.
This is even happening while I'm in recovery mode, it'll just randomly happen.
What's going on?
Can you get it into fastboot? Does it still respond to adb?
Sent from my MB612 using xda app-developers app
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
Here you go dude. It'll help. http://forum.xda-developers.com/showthread.php?t=1809195
BlackFire27 said:
Can you get it into fastboot? Does it still respond to adb?
Sent from my MB612 using xda app-developers app
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
Here you go dude. It'll help. http://forum.xda-developers.com/showthread.php?t=1809195
Click to expand...
Click to collapse
Thanks, that's actually what I'm using =) The issue I'm having is getting it into recovery mode. I am always able to do it prior to this incident, at least after two tries anyways. Now every time the Google logo displays and I hit the down volume, it just begins to boot into Android ignoring the fact I hit the volume down.
Robert
Trewyy said:
Thanks, that's actually what I'm using =) The issue I'm having is getting it into recovery mode. I am always able to do it prior to this incident, at least after two tries anyways. Now every time the Google logo displays and I hit the down volume, it just begins to boot into Android ignoring the fact I hit the volume down.
Robert
Click to expand...
Click to collapse
Make sure the device is off. Hold the volume up, down, and power for 2 or 3 seconds. Then let go of the power button while holding the volumes. That'll bring you to the bootloader. From there you can also get into recovery mode. By selecting with the power and volume keys.
BlackFire27 said:
Make sure the device is off. Hold the volume up, down, and power for 2 or 3 seconds. Then let go of the power button while holding the volumes. That'll bring you to the bootloader. From there you can also get into recovery mode. By selecting with the power and volume keys.
Click to expand...
Click to collapse
I'm going to leave it charging for a while and see if that will give me enough time to do what I need. I'll report back here either within an hour, or sometime tomorrow around this time.
Thanks for the help so far!
Robert
Trewyy said:
I'm going to leave it charging for a while and see if that will give me enough time to do what I need. I'll report back here either within an hour, or sometime tomorrow around this time.
Thanks for the help so far!
Robert
Click to expand...
Click to collapse
Anytime man! PM me if you have anything else man.
It's 4 days old. Send it back as defective.
turn it off, let it charge for long time, after tha download toolkit and revert it back to stock.
You should be good to go.
I'd bring it back, as it is possible to cause an injury to you. Better to be safe than sorry.
Its new so just bring it back (or send) and get a new one.
Sent from my Nexus 7 using xda premium
Try to relock it and flash the stock rom.
After that, phone up Google and explain what happened AND ask for a compensation. This could have harmed you, and Google/ASUS IS responsible for it. Unless, of course you have messed something up while rooting or flashing the custom rom.
Anyway, you should be able to get a compensation, maybe a 32GB version.
This is not something that should happen to a 4 days old device.
did you void the warranty by flashing? i don't actually know.
granted, this sounds like a hardware malfunction (again, i don't know, could be a kernel), but, modder beware. this is a risk we take.
I'd put it back in the box and return it if possible. Save some time. If they are jerks about it then proceed:
If you can flash anything to it through recovery, download the updated Galaxy Nexus (Samsung) JB Bootloader and flash it.
I have a Galaxy Nexus and a Nexus 7. I killed my first N7 by getting confused and flashing it to my N7. It won't even power on afterwards. That should screw up your partitions enough where it won't be recoverable without a full format/reflash.
I had this issue when my battery died. I took off the back cover and unplugged the battery and plugged it back in. Put it back together and charged it up for a few hours. All has been well since, I'm pretty sure its a common issue with N7's when the battery gets low.
Had a similar issue once after letting it discharge to 0 and plugging it in and trying to boot right away. Mind you I didn't have the noise, just the snow effect. My solution was to turn it off and let it charge for a few minutes while off. After that it worked fine.
Sent from my Galaxy Nexus using xda app-developers app
Do your best to revert it back to factory and call them up about that possible firecracker before something else can happen
keep us informed about what happens too if thats ok
Stock - and the same problem...
Hi, my N7 is two months old and worked perfectly. It's clear stock - never rooted, modded etc. Today I suddenly can't run it - it boots, battery level is 24% (on bootscreen), and after few seconds shows 1% and starts to snow - sometimes with sound. I haven't installed anything new for few weeks, so I'm sure it's not a virus, trojan etc. WTF?
PS. Sorry for my English...
djexacto said:
Had a similar issue once after letting it discharge to 0 and plugging it in and trying to boot right away. Mind you I didn't have the noise, just the snow effect. My solution was to turn it off and let it charge for a few minutes while off. After that it worked fine.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I confirm that. I had this issue already a lot of times. When the battery is completley discharged it seems that the display or the graphics hardware is not able to start as expected. I just left it powered of (or in that charging screen) for some time (>1h) without using it. Then it started normal.
But also for me, no noise, just the screen like on an old TV without signal.
Hi
I have just had an issue with the screen turned off and not turning back on forcing me to reboot by holding down the power for 10 seconds. It was after a call and went off as it is meant to as i had the phone to my ear. When i had finished i went to end the call and no display. The phone was still functioning as the notification led was flashing when i double tapped.
Just wondered if anyone else has experienced similar?
Cheers
I had that exact problem with this phone when i first got it... it kinda went away after a while it seemed.. i haven't had that issue sense..
Try factory reset
Sent from my IM-A850K using Tapatalk 2
I think it's a core android problem, because I had it on my Note 2.
Thanks guys
I did a hard reset last night and havent been able to make it happen again after numerous calls today at work. I think perhaps it was a one off bug.
That was one of the first things i did..
Sent from my VS980 4G using xda app-developers app