So I've tried to overclock my nook with both 1.1ghz, 1ghz, 950 and 900 quickie. I only got 1.1 and 900 to work. But after both I swear I have to basically pound my finger into the screen for it to recognize it. not just a light touch like when I'm not OC'd. Is this something I'm doing, the kernel I'm using or what? Thanks
Hit the power button to put it in sleep mode and then wake it back up. Magically it's responsive again. I read elsewhere on here it seems to be a problem with just about any custom kernel. It only seems to occur when you first boot up.
Thankyou thank you thaaaank you.
Related
Tried searching first, sorry if already reported. I'm running the Modaco Froyo ROM, with pershoot's .34 kernel.
After about 1/2hour or so of playing any touchscreen intensive games (ie... Robo Defense and Super KO Boxing 2) the touch sensor goes completely out-of-sync. Anything from touching the screen causing a haptic feedback (as if pressing one of the softkeys) or pressing on one spot of the screen and it registers in a completely different region.
I've never had this issue pre-froyo (as has been reported by folks using 2.1).
Anyone else getting similar issues?
I've been getting this issue since 2.1, and had it for the brief period of using 2.2. Don't think it's been fixed yet. Annoying, but you can always just toggle the screen with the power button to get it back to normal.
gstar_raw said:
...but you can always just toggle the screen with the power button to get it back to normal.
Click to expand...
Click to collapse
Thanks for the workaround tip, heck of a lot better than having to reboot.
as the title says i was reading when the menu started showing and hiding again and again i tought was some book issues but when i got to the homescreen it began to run apps i had on it, i have no idea of the cause of this problem
I've had this same problem. I believe it's just the software and not a deficient screen. If you look over on the nookdevs website, there's a page about recalibrating the screen. I've tried it a couple of times and it's definitely improved it. Every now and then something wacky happens, but I guess that's to be expected when you let B&N develop for Android.
I had this happen myself once, and it was pretty annoying... If I didn't have adb available I don't think I could have fixed it until I did. I wasn't able to tap the screen myself, it was taping all over the place.
I did manage after a few minutes to get multitouch paint installed and it was drawing weird dots, lines, angles, etc...
I now have the recalibrate command in gscript but not sure I could run it while it's acting up. Luckily it's only happened once, and it happened while plugged in but never seen it happen again.
Happens a lot on my NC, and I think every time its because my kids touch it with dirty fingers (sweets, chocolate etc), smearing small amounts of dirt on the screen.
The screen goes nuts within few seconds, thinks its being clicked etc...
Wiping/cleaning the screen helps to resore normal behavior, btw - while the screen is moist it does not work for me at all...
Ordered screen protectors, lets see if it makes a differencel
My screen randomly goes nuts as well. It seems like a sudden, rather than a gradual thing. The screen sometimes gets pretty dirty, but cleaning it didn't seem to make much difference. Odd thing is, what DID make a difference was taking it out of the aftermarket case. I have no idea why this would work, but it does. One thing this case does is that it pushes the power and volume buttons in, as it uses four elastic straps at the corners. Maybe holding these buttons a certain way recalibrates the screen, and if you're touching it at the time, it freaks out?
I've noticed my screen only bugs out when I have it plugged into the charger.
As long as its unplugged, its fine. As soon as i pop in the cord, the screen goes haywire.
Only the wall charger though, not when its plugged into the USB on the computer.
My screen was doing that until I got a screen protector.
Sent from my LogicPD Zoom2 using XDA App
Also, if you lock and unlock the NC it should stop acting funny.
I noticed that too. Mine hasn't gone REALLY nuts since I took it out of it's case, but sometimes when playing angry birds, it freaks out to the point where I can't play. Hitting the power button, and then hitting it again, and unlocking makes it normal. Wouldn't that indicate it's software instead of hardware? Maybe there's more than one problem?
RChadwick said:
I noticed that too. Mine hasn't gone REALLY nuts since I took it out of it's case, but sometimes when playing angry birds, it freaks out to the point where I can't play. Hitting the power button, and then hitting it again, and unlocking makes it normal. Wouldn't that indicate it's software instead of hardware? Maybe there's more than one problem?
Click to expand...
Click to collapse
Mine does the same thing every now and again. And like you, locking the screen and waking it back up fixes it every time. It's definitely software related.
Do your cases have a latch? With a magnet? Because I'm starting to think that may have something to do with it.
My case has a latch, but the magnet is not against the nook when I'm using it..
HotShotAzn said:
Do your cases have a latch? With a magnet? Because I'm starting to think that may have something to do with it.
Click to expand...
Click to collapse
Heh, I've considered that.. Also considered the mystery sensor to the left of the Nook button too.. Nook is afraid of the dark.
Seriously though, with the CPU guvna' set to ondemand and wifi turned OFF before I power it off I haven't seen it reboot yet. It rebooted once yesterday and I know it had wifi left on as I had just been using it and didn't turn it off before it went to sleep.
So totally making up numbers here....
Default CPU governor + wifi on = 30% chance it's gonna reboot when it goes to sleep..
ondemand governor + wifi on = 20% chance it's gonna reboot
ondemand govenor + wifi off = <10% chance it's gonna reboot (not gonna even say 0 here.. heh)
RChadwick said:
My case has a latch, but the magnet is not against the nook when I'm using it..
Click to expand...
Click to collapse
I tested this theory. When the Nook is in the case, I get crazy screen taps when i try to type something. Out of the case, its perfectly fine.
When I just rest the Nook on the open case (not inside the straps/holders), it will also get crazy screen taps.
One thing to note is I also did not have any problems before updating to 1.0.1. Not saying the update is the cause of the problem but its one of the variables.
Hi everyone,
some days ago, I've got a new display into my phone. It is working fine and everything is running good except two things:
- The phone app does hang during an outgoing call. I cannot hang up the call, because there is a black screen, or the phone does not accept input either. When the screen keeps black, I can go back to the home screen pressing the middle button. But in the "system tray" there is no phone symbol. The behavior is changing from call to call. Sometimes the process crashes.
- When the phone is not used for some seconds or minutes it takes up to ten seconds to see someting after pressing the middle button. An interesting aspect is that when the mp3 player is running, there is no delay. Whenn I press the middle button the screen comes back immedialtely.
I have the Firmware 2.2.1 running and executed a hardware reset two times.
Has someone an idea what I can do to bring the phone app to work properly and to decrease the delay when I want to get the from out of the "sleeping mode".
Please excuse my bad english, I hope you got me right
What do you mean by a new Display...I assume you mean a new ROM or kernel and not actually replacing the screen.
Are you using any sort of app that controls or underclocks the CPU such as SetCPU? I used that app for a while to underclock the CPU while the screen was off and it caused the sort of hanging when answering calls that you described.
Also if this is a new kernel confirm that is is not underclocking or using UV to lower the voltage.
Thank you for your reply.
I replaced the display for hardware damage reason. No new kernel or something like that.
I've done 2 hardware resets. So I just have some standard apps on my phone.
Is there some app wich dispays the voltage and frequency of the cpu?
Ok guys, the problem is "solved".
I thought, that I would have to live with my delay und phone problems forever
But this weekend, my phone decided to workl properly as before. There is no delay when bringing back the screen from sleep and no process hanging up anymore. I did not invest more energy to solve that problem.
I dont know what happened internally, but I am extremly happy now
Hi All,
I've just rooted my phone (my first root) and installed Nameless ROM v7.2 Build 5 with the 806Mhz image. Right after that everything seemed to be fine. But later on the wake up function for pressing the power button stopped working.
The symptoms: Phone goes to sleep mode for pressing the power button (screen goes blank), but when I press the power button again nothing happens, the screen remains blank. If I press it twice in fast succession, the lock screen appears for a fraction of a second then again it goes blank. The only way I can get to the lock screen is if I start charging it, then I remove the USB cable, and press the power button. (but it only works right after that) Pressing the power button also works the very first time after automatic timeout.
I'd appreciate any ideas on how this could be fixed as besides that Nameless and the OC image seems to be rather awsome.
Hi, Well there could be many reasons why your phone won't wake, to rule out one does the power button defiantly work?
If it does it could be that your cpu goes too low in clock speed to sustain waking the phone, I think you should try to get an app called setcpu which is found on xda for free and higher the lowest clock speed like so:
806mhz-806mhz
806mhz-4xxmhz
806mhz-xxmhz
then 806mhz and the lowest one
Doing this will let you figure out if it is infct the cpu causing this, post back with your results.
Good luck.
russell664 said:
Hi, Well there could be many reasons why your phone won't wake, to rule out one does the power button defiantly work?
If it does it could be that your cpu goes too low in clock speed to sustain waking the phone, I think you should try to get an app called setcpu which is found on xda for free and higher the lowest clock speed like so:
806mhz-806mhz
806mhz-4xxmhz
806mhz-xxmhz
then 806mhz and the lowest one
Doing this will let you figure out if it is infct the cpu causing this, post back with your results.
Good luck.
Click to expand...
Click to collapse
I've tried setcpu with the four settings listed above and the scaling parameter set to default (ondemand). The problem persists.
To answer your question: the power button definitely works, I can lock the screen with it, initiate shutdown/reboot, it only doesn't function properly when I try to wake up the phone with it. I've also noticed one thing: the 'charging via USB'-'unplug'-'press power' unlock method only works if I don't wait too much after unplugging.
I've tried insalling a different locker (Holo locker) and I wasn't even able to unlock the phone anymore.
Can the htc locker itself be corrupted? Can it be somehow reinstalled?
FYI: I have Autokiller installed but it's currently set to system defaults. Also my battery isn't calibrated yet (I'm not sure if that's relevant). And I have Llama installed and running in the background.
Can it be related to the System off and lock app? It is installed but it doesn't have root access.
Thanks in advance for your help!
This might not be related , but could you tell me what display brightness level you are currently using? If you are not using auto brightness try using that option and retry locking and unlocking the device.
Might be also due to the screenoff app.Try uninstalling it.
nikhil16242 said:
This might not be related , but could you tell me what display brightness level you are currently using? If you are not using auto brightness try using that option and retry locking and unlocking the device.
Might be also due to the screenoff app.Try uninstalling it.
Click to expand...
Click to collapse
Thanks for that nikhil, you've just saved my phone . The issue seems to be solved now. I've also tried with all the brightness settings you can set up with the Power widget - all of them works fine. But if I tweak brightness in the Notification bar - Quick settings, the problem appears again. I guess I'll avoid that slider in the future.
Thanks again!
Novbert said:
Thanks for that nikhil, you've just saved my phone . The issue seems to be solved now. I've also tried with all the brightness settings you can set up with the Power widget - all of them works fine. But if I tweak brightness in the Notification bar - Quick settings, the problem appears again. I guess I'll avoid that slider in the future.
Thanks again!
Click to expand...
Click to collapse
I had a similar problem when i was on stock rom and after a lot of searching found out that it was related to the brightness level we set (Dont know why this problem arises though)
So...Happy to help
The problem is linked to the brightness level
As pointed out by a member 2, this issue is related to the brightness level we set on this phone. I used to have the same problem when i changed the brightness level to the minimum but eversince i increased the brightness just a fraction the problem seems to have dissappeared.
I still dont why it happens
Just a question...
Did anyone having this problem commit a "dirty" flash or any other ROM flashing that didn't involve a full wipe? This may explain this conundrum.
Last night, I decided to check out some of the new roms out for the droid 4 so I downloaded the avatar rom and tried it out. It worked fine except when I would lock my phone and put it into sleep mode, it wouldn't always wake up the screen when pressing the power button. The lights for the hard keys lit up, but not the screen. Then sometimes the screen would light up, but the touch screen wouldn't be active so I couldn't swipe to unlock. It usually takes between 5-10 tries until it finally works. I had the same problem with the AOKP rom as well.
I thought it might be the performance controls keeping the CPU too low when the screen was off and therefore having trouble waking it up so I set the minimum to 600 but that didn't help. Any ideas?
Also, slightly unrelated question but is there a way to turn off the transition animations for 4.2.2? I can't seem to find it :/
nuhusky4 said:
Last night, I decided to check out some of the new roms out for the droid 4 so I downloaded the avatar rom and tried it out. It worked fine except when I would lock my phone and put it into sleep mode, it wouldn't always wake up the screen when pressing the power button. The lights for the hard keys lit up, but not the screen. Then sometimes the screen would light up, but the touch screen wouldn't be active so I couldn't swipe to unlock. It usually takes between 5-10 tries until it finally works. I had the same problem with the AOKP rom as well.
I thought it might be the performance controls keeping the CPU too low when the screen was off and therefore having trouble waking it up so I set the minimum to 600 but that didn't help. Any ideas?
Also, slightly unrelated question but is there a way to turn off the transition animations for 4.2.2? I can't seem to find it :/
Click to expand...
Click to collapse
I have had similar issues with the 4.2.2 ROMs although not as often as you. It would happen to me maybe once a week. I would just hard reboot the phone when it happened. Not sure if it's an issue with the kexec kernel or what.
As for the transition animations I would assume they would be in the launcher settings somewhere.