I am currently on PA 3.68 and since quite some time I am having some problems with my lockscreen:
1. Many times the power button is not responsive... I doubt it might be a hardware problem since this started only a few days ago
2. Many times the lockscreen doesn't even show up, the screen which I was on previously shows up and this is problematic for me as I use a patter to unlock...
Please help !!
If you didn't, try a clean flash. I'm running 3.68 and have none of those issues.
Sent from my Nexus 4 using Tapatalk 4 Beta
YoMaMa7467 said:
If you didn't, try a clean flash. I'm running 3.68 and have none of those issues.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I did try the XenonHD ROM... Still same issues :/
If its following you across Roms I'm not really sure what it could be. Try bumping up your locked/sleeping/low CPU speed.
Sent from my Nexus 4 using Tapatalk 4 Beta
I think I have a similar problem. I had to press the Power button very hard to respond.This is happening from last few weeks. I use swipe2wake and swipe2lock. So not a huge issue. But it still worries me. I am using DU rom. Not sure if it is a button issue or ROM.
Related
Hi,
I've googled about this problem for a long time but haven't found anyone with the same problem as me.
When i leave my Nexus 10 unused for a some hours it don't lit the screen when i open the case or when pressing the power button.
The notification light often blinks because of a email or instant message recived so i know it's still on.
Anyone knows what couse this?
I've experienced this both with 4.2.2 and 4.3.
Sent from my Nexus 10 using xda app-developers app
Is it a stock ROM or custom? I've had the same problem on a few customs ROMs
Sent from my Razr HD using Tapatalk 4 Beta
motodroidfreak said:
Is it a stock ROM or custom? I've had the same problem on a few customs ROMs
Click to expand...
Click to collapse
It's full stock ROM, no root or anything.
Sounds a lot like the SoD, or Sleep of Death. If you search that you will find tons of info.
I have been suffering bad SoD since upgrading to 4.3
Like 2 - 3 times daily.
Sent from my Nexus 10 using XDA Premium HD app
riqjuan said:
I have been suffering bad SoD since upgrading to 4.3
Like 2 - 3 times daily.
Click to expand...
Click to collapse
Same here. I've had two SoDs and one reboot after sitting idle for 8 hours in the past day.
Basically, my N7's screen is frequently unresponsive. I was trying to start something in my launcher, and tried pressing it at least 6 times, but nothing happened. Then I tried swiping between launcher pages, and that worked just fine the first time.
This just started happening on an almost constant basis within the last 30-60 minutes, and I was wondering if anyone else has experienced this, or heard of anyone else experiencing it. I'm running the latest Minimus with Jassy's latest kernel (I just flashed them this morning, but it was probably 4-5 hours ago at least), with the DPI set to 290 (I just raised it from 280 to see if that would help anything). I also cleared the cache and dalvik.
Any ideas?
My girlfriends tablet has done that too, then it just randomly goes back to just fine
Sent from my Nexus 7 using Tapatalk 4 Beta
Why don't you try stock and see if you have an issue. This would allow you to rule things out at least.
Sent from my Nexus 7 using xda app-developers app
Same issue here...both stock and CleanROM
me as well. And this is my second tablet after returning the first one for dead pixels
My tablet is stock rooted and I have just experienced this. I had to reboot in order to fix it. Hopefully this doesn't happen again.
Sent from my Nexus 7 using xda premium
lyall29 said:
My tablet is stock rooted and I have just experienced this. I had to reboot in order to fix it. Hopefully this doesn't happen again.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Same here this has happened to me on stock, but a reboot fixed it.
I've only experienced this using Chrome. it got so bad that I'm using the molasses-in-the-winter-going-up-hill Firefox browser just to be able to web surf.
Same here stock, and clean ROM.. Haven't noticed anything on kanged cm nor pa yet. Can't get otg to work worth a crap either I bought chainfires app to help with otg worked with stock based ROMs but not cm based ROMs .. I'm pissed I bought the 16 GB model..
Sent from my Nexus 7 using Tapatalk 4
dincdoes.me said:
Same here stock, and clean ROM.. Haven't noticed anything on kanged cm nor pa yet. Can't get otg to work worth a crap either I bought chainfires app to help with otg worked with stock based ROMs but not cm based ROMs .. I'm pissed I bought the 16 GB model..
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
It happened to me as well (complete stock). Mostly (if not all) instances were with Chrome. I don't remember it happening again since I switched to Chrome beta. (Fingers crossed).
I just took mine back to Best Buy and exchanged it for the 32gb model. The guy at the store asked if anything was wrong with the tablet and I told him that it would freeze up and I would have to reboot in order to fix it. He told me that all tablets and phones freeze like that and that I should reboot the device at least once a day to prevent the freezing of the screen. I thanked him and told him that I would do that. These salesmen must think that everyone is as dumb as they are.
I hope my new tablet doesn't have the same problem, because if it does I might give up on the new nexus 7.
Sent from my Nexus 7 using xda premium
Hi guys,
I recently bought a Google Nexus 4. Great device! But now I have a problem with the touch screen I guess.
I have some ghost touches on the screen. They are always on the same places.
To be more specific, on the same X-as of the screen. 3 to 5 touches in horizontal direction, swiping and touching the screen.
It's not always there, that's what's bothering me.. what is gods name could it be...
I'll add a screenshot of the touches when I get a chance to...
I have this problem for about a week now. And I was wondering if someone knows the solution to this.
ROM: Cyanogenmod 10.1.2
Cheers,
Alexander
When did this happen?
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
When did this happen?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
It happens every now and then. It started a week and a half ago or two weeks ago. Not exactly sure.
Alexandersch said:
It happens every now and then. It started a week and a half ago or two weeks ago. Not exactly sure.
Click to expand...
Click to collapse
This is start on the stock or custom rom?
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
This is start on the stock or custom rom?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
I have installed the custom rom the moment I got this device. It didn't happen before.. So I doubt it is a software problem. I'd rather think of it as a hardware problem, don't you think?
No-one?
If it started on custom Rom then flash back to stock to see if it still happens. If not then there you go.
If still happens even on stock then RMA the device.
Sent from my Nexus 4 using xda premium
mariosraptor said:
If it started on custom Rom then flash back to stock to see if it still happens. If not then there you go.
If still happens even on stock then RMA the device.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I flashed another ROM CM10.2 UNOFFICIAL. Did a clean install.
Untill now it is reacting normal.. Let's wait and see.
I am thinking, could it be of some backup settings it is recovering from my google account?
Because it has no Gapps installed yet. Downloading at the moment.
Thanks in advance
As suggested, try stock.
Sent from my Nexus 4 using Tapatalk 4
naenee said:
As suggested, try stock.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Ok, The CM10.2 did not work. I disabled auto backup and recovery of Google settings and stuff and flashed the Stock ROM 4.2.2.
Also there was an official update to 4.3. And surprisingly enough, the device is responding normal again. Still though, i think it was very strange that the problem was also in the recovery...
Hi
I notice that my new nexus 4 has a annoying bug.
While I use it its randomly simulate a touch on the side of the screen and not release it untill I turn off and on the screen.
Its happen many times for me.
I tried to use different ROMs and kernels and the problem remains.
Is it common bug? how can I resolve it?
Thanks!
someone?
This hasn't happened to me seems to be a strange bug.
Sent from my Nexus 4 using Tapatalk
It happend on my N4,i think when it has low battery;running PA,didnt noticed on stock because didnt use it that much,few daya
Sent from my Nexus 4 using Tapatalk 2
im running PA too, but it happen to me on every rom.
is it happen to you with high frequency?
This does happen to me, although very rarely. I have came the conclusion that it only happens when I have the TouchControls modules enabled with ParanoidAndroid rom.
Hi all.
I've been looking at different threads and a few people talk about it but not seen any fixes.
When I receive a call I get a 3-4 second delay before the screen wakes up meaning I don't know who is call or able to answer the call.
I'm running PA4 with r201 FK
If any one knows a fix please share.
Sent from my Nexus 4 using Tapatalk
Even we are facing similar issue on Note 2. Tried few things but issue still persists.
Seemingly got something to do with some service.
So it's not device related then?
Sent from my Nexus 4 using Tapatalk
Was just using my phone and tookna call, even when screen was on it still took a long time to show who was calling!?!
Sent from my Nexus 4 using Tapatalk
Seems to be getting worse! I have to wait for about 5 seconds now, or maybe it already did.
Does no one have a fix?
Thinking about reverting to stock to see if that fix's it then maybe flash each thing one at a time and see when it breaks.
Sent from my Nexus 4 using Tapatalk
If you're playing around with kernel's and under clocking the CPU this can affect how quickly the phone wakes up. But my phone has a delay of a few seconds before I am am aware of a call coming in. Maybe it will be fixed in a future update.
Phone : Nexus 4 /Rom : cataclysm / Kernel : Stock.
I've only installed them the same as others but they don't seem to suffer the same problems.
Any one have any fixes?
Sent from my Nexus 4 using Tapatalk
foxguard said:
I've only installed them the same as others but they don't seem to suffer the same problems.
Any one have any fixes?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
same problem to me !!! i9100g cm11 last update!!!i hope they fix it!!
yohan7 said:
same problem to me !!! i9100g cm11 last update!!!i hope they fix it!!
Click to expand...
Click to collapse
Installed stock and all is fine, have unrooted my phone and now starting fresh to see if helps.... fingers crossed!
foxguard said:
Installed stock and all is fine, have unrooted my phone and now starting fresh to see if helps.... fingers crossed!
Click to expand...
Click to collapse
Aaaaaand what happend? Did you resolved problem? I have problem too on cataclysm and hells b43 kernel.
Deni_NS said:
Aaaaaand what happend? Did you resolved problem? I have problem too on cataclysm and hells b43 kernel.
Click to expand...
Click to collapse
I remember having this issue with franco r201 I think, but it went away when I updated the kernel/changed kernels
lopezk38 said:
I remember having this issue with franco r201 I think, but it went away when I updated the kernel/changed kernels
Click to expand...
Click to collapse
And now your kernel is?
Deni_NS said:
And now your kernel is?
Click to expand...
Click to collapse
It went away for me with franco r203 but I had to restore a nandroid running franco kernel + r200 and I haven't checked for the bug since
lopezk38 said:
It went away for me with franco r203 but I had to restore a nandroid running franco kernel + r200 and I haven't checked for the bug since
Click to expand...
Click to collapse
I'll try then r203. Thanks
I installed a different ROM with stock kernsl and had same prob.
Did a complete wipe and unroofed the phone, took back to stock and all was ok.
Rerooted the phone, installed PA, all fine. Installed r203 and still all good
Sent from my Nexus 4 using Tapatalk
foxguard said:
Hi all.
I've been looking at different threads and a few people talk about it but not seen any fixes.
When I receive a call I get a 3-4 second delay before the screen wakes up meaning I don't know who is call or able to answer the call.
I'm running PA4 with r201 FK
If any one knows a fix please share.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
If you have DU Battery Saver or any similar app which puts your device on low CPU usage upon locking, then uninstall it. It worked perfectly in my case.