For some reason I can't shut my touchpad down. If I hold the power button down, not much happens until I release the button. Then the screen turns off. Tap it again and it's back.
Any ideas?
thats strange try a hard reset, hold the power button and the home button down for literally a minute or so or until it resets. it will reboot into moboot hopefully. you might have to do that and go back into webos to completely shut down. good luck
Thanks for the reply, I was just trying it when the battery ran out!
But I'll give it a go if the problem returns, thanks.
Ran into the same problem today. The power menu, along with various power/reboot widgets wouldn't work, but after about 20 seconds of holding home+power it worked and booted to moboot.
I had this happen to a coworker, after I had recently upgraded her to alpha3. I tried everything to repair it before deciding to start from scratch. The best thing to do is restart using the power and home buttons (hold them until reboot).
Then think about reinstalling.
Good luck!
Sent from my Touchpad using Tapatalk
I had this same issue today. I downloaded Quick Boot from the app store and it allowed me to restart. Worked great
just happened me too, it MAY have something to do with low battery, i noticed someone above had the problem with low battery. mine happens to be low too
also, i turned off lockscreen earlier, maybe that was related.
Related
I fell asleep next to my phone one night and when i woke up and tried to wake up my phone the volume menu opened up and acted like if i was pressing the volume bar repeatedly. I turned it off and on again and once it boots into Windows the same thing, if i try to press volume down it will and it will go right back up again. The Volume rocker button is fine and not stuck. I found out though if i hold up and down before windows mobile boots up it will allow me to operate as normal but once i let go It goes back to the volume going all the way up. I have flashed different roms to no avail.
Does anyone have any ideas to what could be causing this?
I just started having the same problem with a Samsung Omnia 7. It fell into some water, let's say it was a bucket, i pulled it apart and thoroughly dried it. Seemed to work perfectly for a few hours, now the volume thing.
Our HD2's hard buttons are not invincible and I learned that the hard way. After lots of use on my phone the send, home, end, and volume down buttons stopped working. I also believe my end button is stuck on because it always boots up on its own, meaning I can't shut it down and leave it off. I have to take the battery out of it.
My advice is if you can find a way to use "soft" buttons to navigate your phone do it and save yourself the hassle of breaking the hard ones for when you need them. Good luck!
HD2 Volume Stuck on UP
richardhauer said:
I just started having the same problem with a Samsung Omnia 7. It fell into some water, let's say it was a bucket, i pulled it apart and thoroughly dried it. Seemed to work perfectly for a few hours, now the volume thing.
Click to expand...
Click to collapse
I had a few drips of water it my hd2 and a couple days later, I rebooted and after it rebooted, the volume is stuck on UP. I took it apart. I has nothing to do with the button itself as I removed the button and it's still stuck. Still no solution yet.
Hi,
Did anyone find a solution for this? I had to hard reset my HD2 couple of days ago. After the reset, I installed all the apps, one after another. The phone worked fine for a day, until this afternoon when it started acting crazy. First symptom was that when you type some numbers of the "Phone" screen to look up a contact, I was not able to delete the using the back button. Other keys like up, down, left, right too didn't work in the SMS compose screen. I restarted the phone thinking that it would resolve the issue, but worse. The volume control showed up just after the boot and the "volume up" tone was constantly going off as though I was pressing the volume-up button constantly. I tried rebooting and remove the battery, SD etc, uninstalled few programs, but to no avail.
Request help from senior members...
Alright, I just bought my Dad a tab 10.1 yesturday since I found a really good deal on one. My problem is that when the tab freezes the only way to get it working is to hold the power button (about 10 seconds) from what I understand is that it should soft reset the device, but in our case it's being completely reset to factory settings. So is there another way to restart the tab? (On my Xoom it's Power and Vol Up) and is there anyone else having this issue? (pretty much, is this normal behavour?)
Now I'm not afraid to root and do all the goodness that is out there as I have done that on my Xoom and my Nexus One both of which were rooted within hours of recieving them, but since this is my Dads I would prefer not to.
The Tab is running 3.1, Kernal is 2.6.36.3 and the build is HMJ37.XXKG6 P7510XXKG6
Thanks for any insights
In order to reboot it, shut it down by holding the power button for 2 seconds until it shows the pop up menu - choose Power Off. When it is off, press the power button for 2 seconds again and it will start up.
baha that's a good one. As if I didn't try that already. The issue is that it was completely unresponsive to everything except a forced reboot. Too late regardless, it was returned yesturday.
So I used my nook tablet all day yesterday and this morning. I put it down to goto lunch.. came back and noticed my wifi was not on.. I checked settings and it showed "Wifi turning off" and it was grayed out and just stuck.
I've seen this before with other android devices so no biggie. I powered the unit off.
Now it won't turn back on. Holding the power button now for about 20 secs and nothing.
The battery is at like 80% and I even plugged it in to see if it helped but no good.
I did root it at 1.4.0 and used the Block OTA method with titanium backup but nobody else seems to have a problem.
Is there a way to boot in recovery or something ? Perhaps a trip back to B&N will be needed.
Ok.. holding vol down + power for around 8 secs got it back on. Weird
i have noticed this a few times. Not sure why but never lost anything
DssTrainer said:
Ok.. holding vol down + power for around 8 secs got it back on. Weird
Click to expand...
Click to collapse
His happened to me once and I don't know what I did to get it back on. Glad that I now know, thanks.
Sent from my rooted Nook Tablet.
DssTrainer said:
Ok.. holding vol down + power for around 8 secs got it back on. Weird
Click to expand...
Click to collapse
I had a similar problem. I couldn't get the tablet to turn on. I discovered in a Kindle Fire forum that you could get the Fire to start when stuck in the off position by holding down the power button for 20 seconds. I tried that with my Nook and it started right up.
Thank! That worked! I was having the same issue. Said Wifi was turning off and all went blank and couldn't reboot. You gave me the answer.
Cheers.
I have had the wifi "turning off" issue. Rather than turn off the nook, I used the menu that you get with a long press of the power button when you install either ROM manager or titanium backup, can't remember which. It has rebooted every time without issue.
The Wifi issue is a known problem. You can set the wifi to stay awake when on the charger and this problem wont happen. Add the power widget so that you can turn the wifi off when not connectwd to the charger. This combo fixes the wifi issue. When your Nook experiences a kernel error it will appear as if it is off but if you hold it at angle, you will notice backlight is on. Just hold nook button and power and it will turn off...then power to reboot rom.
C64assembly said:
The Wifi issue is a known problem. You can set the wifi to stay awake when on the charger and this problem wont happen. Add the power widget so that you can turn the wifi off when not connectwd to the charger. This combo fixes the wifi issue. When your Nook experiences a kernel error it will appear as if it is off but if you hold it at angle, you will notice backlight is on. Just hold nook button and power and it will turn off...then power to reboot rom.
Click to expand...
Click to collapse
Actually, it's happened to me twice while I had WiFi set to never sleep when charging.
Moved To Q&A
We now have a Q&A section. Please post all questions there
I rooted my Nook Tablet and it worked fine yesterday. Now it won't turn on and isn't recognized by my PC. I hear the windows alert when a usb device is connected but when I try to do anything via adb I always get 'error: device not found'.
I tried doing adb get-state and all I got was 'unknown'
I tried booting into recovery via holding the power button + n for various amounts of time, but nothing happened.
Does anyone have any ideas? It was working fine yesterday and I haven't changed anything on it since I used it last.
Hold the power button down for about 10 seconds. let it sit for a minute, then hold the power button for another 5 seconds or so and release. It should boot up. (assuming your battery is charged)
Know-Fear said:
Hold the power button down for about 10 seconds. let it sit for a minute, then hold the power button for another 5 seconds or so and release. It should boot up. (assuming your battery is charged)
Click to expand...
Click to collapse
I had to do a reset (power button + Home) twice so far. Each time it happened after I left the tablet to recharge overnight. It did not turn on as it normally does when you unplug the charger.
I must admit that the (power button + Home) reset does not seem to be cut & dry. The routine quoted above worked the first time. The second time, I tried it several times then finally I tried the pwr button by itself and it went on.
Mine just did this Power and vol down got it running again.
I have heard of this problem before but I can't seem to find any way to fix it.
I was in an app, the app froze but haptic feedback was still working, held down power to restart, phone vibrated but nothing on screen.
I have not had any screen problems before.
What do I do to fix or troubleshoot this?>
Thanks
r2tincan said:
I have heard of this problem before but I can't seem to find any way to fix it.
I was in an app, the app froze but haptic feedback was still working, held down power to restart, phone vibrated but nothing on screen.
I have not had any screen problems before.
What do I do to fix or troubleshoot this?>
Thanks
Click to expand...
Click to collapse
can you access recovery?
Did you try holding it down for 30+ seconds? It can sometimes take a really long press to trigger reboot.
Sent from my EVO
So I had the OTA update for 5.1.1 the other day and thought "yay, let's update." it worked fine till this evening where it crashed to a power off state and in now showing the Google logo like it's about to load up and then a turned off screen.
This repeats over and over I can't even stop this loop.
Holding the power button and it just continues to loop.
Power + ANY volume button and it will show the HBOOT or fastboot menu then before I can select anything turn to the powered off state and loop through (if I'm still holding the buttons the menu will show again shortly, or go back to the Google logo)
Any ideas for a solution?
try waiting until the battery drains all the way down then hold the volume down button and plug it in. if that doesn't work then all you can do is contact google support and they'll probably replace or fix it.
Hold the power button down for 20 seconds 3 times. It helped me once with a similar situation
So I have found a solution. Instead of deleting the thread I'll leave this here unless anyone else has this problem.
It seems that trying to enter the fastboot menu when plugged into a USB seemed to work.
It was either the fact it was in the computer, the timing I pressed the "power button + power down" combo, or it had just looped enough times and decided to actually stop interrupting me using the fastboot menu.
Either way, I cleared the cache partition using the recovery and it booted up fine.
EDIT: Thanks for the help, I had tried holding the combo for a long period of time (multiple loops of the booting). I also feared letting it drain in case it refused to startup again and I would have no chance of fixing it.
glad you figured that out! android can be mysterious sometimes. especially when it's on the nexus 9.