Database Users

[Q] Safe mode, trackball, partial wake, oh my!

So I've come up against the strangest problem: I recently rebooted my phone to find the words "safe mode" in the bottom left hand corner, and no access to third party apps. Eventually, examining logcat, I discovered this was being caused by the trackball, which the system thought was pressed during boot (even though it wasn't). Strangest thing is that the trackball appears to work fine both in the OS and in recovery?
I figured it was a hardware problem, and as I hardly use the trackball anyway I decided to compile a custom kernel to disable it (which worked a treat). The problem is, after all this messing about I noticed that my battery life had fallen dramatically (full to empty in ~6hrs). Going into spare parts revealed 100% awake time under "other usage", although nothing significant was listed under "partial wake usage".
I figured this was something I'd done, so I went back to a previous nandroid before I tweaked anything. No luck. Then I wiped (data, cache, dalvik, everything). Still no luck. Then I used the RUU to go back to HTC Stock (1.5). Still no luck.
I am 100% confident that it is not something I have done to cause this constant partial wake, which leads me to believe it is related to the trackball problem. Is it possible that although I've disabled the trackball it's still keeping the phone awake? I don't know enough about the system to be able to link these two issues together, so I was hoping somebody here might be able to help.
I'm already well out of warranty, so all suggestions are welcome!

http://cgi.ebay.co.uk/HTC-G3-Hero-M...UK_Mobiles_Accessories_RL&hash=item43a34cb7b4

Soo annoying, CM7 rooted G2 just died, no rhyme or reason

My T-Mobile USA G2 has been rooted running CM7 stable with no issues for a few months now. I reboot the phone a few times per week. Everything has been great for months, then all of a sudden my battery was low and the phone started to slow down. I figured it was just setCPU lowering the CPU down to the 245mhz I had it set to. Then all of a sudden it froze, I had to pull the battery, I thought that was kind of weird, but figured what the hell, why not. A good reboot can't hurt, right?
WRONG.
I put the battery back in and at the boot animation (blue arrow circling Android on a skateboard above "Cyanogen Mod 7" banner) shows up, but the arrow starts to stutter, then the screen dims -> then goes black. So I figure the time out activated, no big deal. Then I realize I can't wake hte phone up! No matter what I did, if I plugged it into my PC, the screen would come on (lock screen) but it wouldn't register any touching of the screen, therefore I couldn't unlock the phone, and it would just time out again.
I ended up having to reboot into CWM and do a Wipe Data and re-install of CM7 from my SD card for it to work!! I tried wiping dalvik cache, battery stats, etc... everything except for wiping Data, but nothing worked. I HAD to wipe my data and re-install the OS...
Anyone know why this happened? Or what could have caused it? At this point I downloaded the newer version (7.0.3) and after wiping installed that, now I have to re-download all of my apps and re-setup all of my settings (extreme pain in the @$$ and very time consuming)...
Thanks in adv.

Do a search, I thought there was some issue with low cpu speeds and waking the phone up from sleep. Basically, the cpu is undervolted and doesn't have enough juice to turn the screen back on.
Search around.. it's on here somewhere. In the meantime, increase your min cpu speed.
maybe in here?
http://forum.xda-developers.com/showthread.php?t=1043118

Thanks, I had read about that prior to setting my phone up, and that had never caused an issue for months... I don't get why it would all of a sudden cause an issue?
Also, I couldn't even get to my desktop to change the min CPU speed... no matter how long I waited, the phone wouldn't wake/wouldn't let me unlock it...
I ended up having to wipe the phone clean and re-install a fresh install... in the new install I have the min cpu higher than it was before.

Phone going crazy

I'm having some serious issues with my phone. This morning the battery was suddenly drained completely, don’t know why yet. Then after charging the phone a bit and rebooting it, it constantly goes into driving mode and starting the voice command application. The most strange thing however is that when I choose to power off the phone, it shuts down but then automatically reboots.
I know I should try factory reset, but anyone else had this problem?
(I have original firmware and the phone isn't rooted)
EDIT:
Doing a hard reset seems to have solved the problem.

Maybe your power button is broken (constantly pressed)? Did the phone get wet?

I have not heard of this. I've heard of bootloops and the phone rebooting when trying to power off but thats usually due to custom roms and people flashing over other custom roms which causes conflict. I think factory reset may be the only option. However, with the Galaxy S there used to be a way to get into safe mode. I beleive you'd hit the menu button as soon as you saw the Galaxy S boot logo. I haven't heard of a safe mode yet for SGS2 but perhaps someone can confirm if its available in this model?
If you can still get into settings of the phone when its on, I'd try going into Settings > Applications > Manage Applications and clearning data for voice commands
It almost seems as though your phone is registering home button being clicked thereby turning voice mode on and also turning it back on after a power off.

delinne said:
I'm having some serious issues with my phone. This morning the battery was suddenly drained completely, don’t know why yet. Then after charging the phone a bit and rebooting it, it constantly goes into driving mode and starting the voice command application. The most strange thing however is that when I choose to power off the phone, it shuts down but then automatically reboots.
I know I should try factory reset, but anyone else had this problem?
(I have original firmware and the phone isn't rooted)
Click to expand...
Click to collapse
Hi,
I was have exactly same problem, reset don't resolve my issue.
Solution was to replace my phone.

Thanks for the help, gonna try factory reset first. But this doesn't look like a software problem, so probably gonna need to replace it

delinne said:
Thanks for the help, gonna try factory reset first. But this doesn't look like a software problem, so probably gonna need to replace it
Click to expand...
Click to collapse
Well this is a strange problem. Is it possible a bread crumb got under your buttons? Or some case is so tight it is pressing on some buttons?

Don't have a case around it, but the power button isn't stuck I think because wouldn't the menu for shutting down the phone etc. appaer constantly? And if it's something under the buttons then it is just bad design, had the phone only a couple of weeks.

delinne said:
Don't have a case around it, but the power button isn't stuck I think because wouldn't the menu for shutting down the phone etc. appaer constantly? And if it's something under the buttons then it is just bad design, had the phone only a couple of weeks.
Click to expand...
Click to collapse
I had the same problem mate. And that was exactly what I thought, I actually started a thread on this problem about 2 weeks ago. Was really strange, people told me to take it back. But What I did was factory reset on the phone. Which still didn't completely solve my problem. So I left the battery out the phone over night. The most annoying thing was, the screen kept turning on, like something was being pressed, can't have been the middle button, because the menu would have come up, it didn't do that. And then to make matters worse the tap to speak driving mode kept coming up.
I then took out the battery and left it out over night. Put it back in, in the morning. Charged it up. Didn't do it again.
Hope that helps. Try it.

Ok thanks, I will try it. It is really a strange problem as you say. After the factory reset the problem showed up again but not as often as before. Also after upgrading to latest firmware today, according to the battery monitor android OS is using 45%, that looks really strange to me.

stuck in bootloop on stock Evo =(

I have an Evo that isn't rooted, but is stuck in a bootloop. The battery was getting low and then all the sudden after i charged it some and turned it back on it just loops the boot animation.
I have tried a few things and still can't really figure out why this came out of nowhere. I was running the official 2.3 update for a few days now and this came out of nowhere.
any idea or tips?

Jddroid9 said:
I have an Evo that isn't rooted, but is stuck in a bootloop. The battery was getting low and then all the sudden after i charged it some and turned it back on it just loops the boot animation.
I have tried a few things and still can't really figure out why this came out of nowhere. I was running the official 2.3 update for a few days now and this came out of nowhere.
any idea or tips?
Click to expand...
Click to collapse
So you're 100% stock, huh? (adjusting my thinking to stock type)...
Were you running any new apps or anything before this happened? It was literally out of the blue? I would take the battery out of it, and let it sit for a while (10-20 mins) Then put the battery back in and see if it will boot up. If not, try taking your SD card out and then try booting. If that still doesn't work, I'd suggest doing a factory wipe from your bootloader, then try booting. To do that, power the phone down completely. Hold your volume down and power buttons simultaneously until the hboot screen comes up. Navigate down to 'clear storage', and select it. This will completely wipe all of your user data from the phone. If it still won't boot up after that, I would take it to sprint. Normally I'd suggest using an RUU, but since you're on the OTA, there is no RUU for it yet, and you can't downgrade it, unfortunately. Good luck.
Again, if the phone's super hot, let it cool down with the battery out for a while.

k2buckley said:
So you're 100% stock, huh? (adjusting my thinking to stock type)...
Were you running any new apps or anything before this happened? It was literally out of the blue? I would take the battery out of it, and let it sit for a while (10-20 mins) Then put the battery back in and see if it will boot up. If not, try taking your SD card out and then try booting. If that still doesn't work, I'd suggest doing a factory wipe from your bootloader, then try booting. To do that, power the phone down completely. Hold your volume down and power buttons simultaneously until the hboot screen comes up. Navigate down to 'clear storage', and select it. This will completely wipe all of your user data from the phone. If it still won't boot up after that, I would take it to sprint. Normally I'd suggest using an RUU, but since you're on the OTA, there is no RUU for it yet, and you can't downgrade it, unfortunately. Good luck.
Again, if the phone's super hot, let it cool down with the battery out for a while.
Click to expand...
Click to collapse
That phone is stock (my gf uses it)
I myself have rooted my last few phones (Tbolt right now). yea I'm gunna let it sit for a while now, i tried the SD card thing but its a no go. I'm going to try to let it sit for a while like you said. leaving it alone can work miracles sometimes.lol
Hopefully were good because I don't think she wants to start all over in all of her games!lol
Thanks for the advice!

Jddroid9 said:
That phone is stock (my gf uses it)
I myself have rooted my last few phones (Tbolt right now). yea I'm gunna let it sit for a while now, i tried the SD card thing but its a no go. I'm going to try to let it sit for a while like you said. leaving it alone can work miracles sometimes.lol
Hopefully were good because I don't think she wants to start all over in all of her games!lol
Thanks for the advice!
Click to expand...
Click to collapse
You're welcome. I hear ya about not wanting to lose the stuff, but a reset may be the last resort if it won't boot up. It's better to get it booting and lose all her stuff, than to not have the thing even turn on! Hopefully after it sits for a while it'll fire up for ya though. If not, I'd pay sprint a visit and tell them that the OTA borked the phone!

No sound on lollipop?

Fixed problem by wiping cache from stock recovery
Anyone else flash factory image and now has no sound what soever? Completely clean factory image flash and no headphone or speaker sound. Only vibrations. Made sure everything was up all the way and tested on YouTube and play music and notification sounds. I saw one other person post they had the issue. So is it anyone who flashed factory image or everyone?
Sent from my VS980 4G

abdel12345 said:
Anyone else flash factory image and now has no sound what soever? Completely clean factory image flash and no headphone or speaker sound. Only vibrations. Made sure everything was up all the way and tested on YouTube and play music and notification sounds. I saw one other person post they had the issue. So is it anyone who flashed factory image or everyone?
Sent from my VS980 4G
Click to expand...
Click to collapse
I have sound, but the button works backwards.

I was just coming in to ask the same question - no sound at all on my N10 on 5.0 factory image. Strange. Makes it really useful as an alarm clock, eh?

Fixed it. If you have the issue reboot into stock recovery and wipe cache. Works after that.

No sound on Nexus10 after upgrading to lollipop
I have the same problem as others with no sound from nexus 10 since installing lollipop.
I don't understand how you can do, what has been posted. Please can someone tell/explain how to do it.
PLEASE

uktony said:
I have the same problem as others with no sound from nexus 10 since installing lollipop.
I don't understand how you can do, what has been posted. Please can someone tell/explain how to do it.
PLEASE
Click to expand...
Click to collapse
Power down tablet.
hold volume up and volume down and power all at same time. this will boot the boot loader.
press either volume key until you see ""recovery mode""
press power button to enter recovery
wipe cache from there
reboot tablet

Thank you
He5aid said:
Power down tablet.
hold volume up and volume down and power all at same time. this will boot the boot loader.
press either volume key until you see ""recovery mode""
press power button to enter recovery
wipe cache from there
reboot tablet
Click to expand...
Click to collapse
Thanks for that, it worked 100%

abdel12345 said:
Fixed it. If you have the issue reboot into stock recovery and wipe cache. Works after that.
Click to expand...
Click to collapse
Thank you !

Recoveery mode trouble
He5aid said:
Power down tablet.
hold volume up and volume down and power all at same time. this will boot the boot loader.
press either volume key until you see ""recovery mode""
press power button to enter recovery
wipe cache from there
reboot tablet
Click to expand...
Click to collapse
I've tried following these instructions several times so far. Each time I get to the point where I'm pressing the power button to enter recovery, the screen goes blank for about a minute, and a "No command" message is displayed, along with a picture of a dead android robot on its back. The only thing I can do at that point is to hold down the power button until it reboots normally. I never see any option to wipe cache. Suggestions?

mgaston said:
I've tried following these instructions several times so far. Each time I get to the point where I'm pressing the power button to enter recovery, the screen goes blank for about a minute, and a "No command" message is displayed, along with a picture of a dead android robot on its back. The only thing I can do at that point is to hold down the power button until it reboots normally. I never see any option to wipe cache. Suggestions?
Click to expand...
Click to collapse
Mine did exactly same. Sounds worked after boot though..

My N10 with Android 5.0.1 will always cut off audio if I power it on with a headset plugged in. I just unplug the headset then reboot and wait until the desktop is displayed before using the headset. That's never failed yet.
Sent from my Nexus 10 using XDA Premium HD app

mgaston said:
(...) Each time I get to the point where I'm pressing the power button to enter recovery, the screen goes blank for about a minute, and a "No command" message is displayed(...)
Click to expand...
Click to collapse
When You see screen with android on his back (and triangle/exclamation mark), just one more step: hold Power button and tap Volume Up once before releasing the Power. A list of items should now appear at the screen. Now, you can wipe the cache partition (~10 minutes to complete).

Nexus 10 no sound
GhromPL said:
When You see screen with android on his back (and triangle/exclamation mark), just one more step: hold Power button and tap Volume Up once before releasing the Power. A list of items should now appear at the screen. Now, you can wipe the cache partition (~10 minutes to complete).
Click to expand...
Click to collapse
I need help. I wiped out the cache partition following the above instruction but unfortunately, still no sound. The only way I have sound is via my bluetooth speakers. Any idea what I can do next?

I ran into this problem a couple days ago when booting after a recharge, with 5.0.1. No sound coming out of my Nexus 10, no matter what I did. Simply rebooting the tablet fixed it.

Just restart phone
All I had to do was turn my phone off and on. Running Nexus 4 on Lollipop.

Cause of the Sound Issue...
This is what we know based on several trial and error tests. The issue occurs when you have the tablet plugged into a charger and unplug it. Not sure why the issue is caused this way but each time it happens that was the case.
Solution...
After charging your Nexus 10 you will have to reboot the device once to get the sound back. You could go in and clear cache although its generally easier for most people to just restart the device. Have noticed best results when the tablet is on then turned off and back on again as opposed to just turning it on from a dead state.
I know this is annoying and more of a temporary solution but it will get your sound back just the same until Google pushes out an update to fix the underlying issue. It is annoying having to reboot the device each time you put it on the charger but for the time being it works.
Hope this helps.

Mofiki said:
Cause of the Sound Issue...
This is what we know based on several trial and error tests. The issue occurs when you have the tablet plugged into a charger and unplug it. Not sure why the issue is caused this way but each time it happens that was the case.
Solution...
After charging your Nexus 10 you will have to reboot the device once to get the sound back. You could go in and clear cache although its generally easier for most people to just restart the device. Have noticed best results when the tablet is on then turned off and back on again as opposed to just turning it on from a dead state.
I know this is annoying and more of a temporary solution but it will get your sound back just the same until Google pushes out an update to fix the underlying issue. It is annoying having to reboot the device each time you put it on the charger but for the time being it works.
Hope this helps.
Click to expand...
Click to collapse
For me it also kills the front mic but the back one works. The solution of restarting fixes sound and mic for me.

So its not just me. Good.

http://forum.xda-developers.com/nexus-10/help/android-5-0-sound-problem-charging-t2939672

Reboot With NO Attached Devices
Try rebooting your Nexus 10 with all connections to external devices detached and off. This means NO power supply, NO bluetooth, NO HDMI cable, NO headphones, etc.
You may need to do this a few times. This worked for me when no other remedy worked, and I tried everything.