I am ussing pa 8/4 and franco r111.. I don't use touch control or something like that. However i always have this bug : when i put n4 in my jean's pocket, and then i have a call or a message, i take it out and touch the screen but it doesn't work..after press the power and press again, it work normally...
Can anyone meet this bug...help me plz...thanks a lot !
Had this problem for a while with the same setup. But was using Touch Control. Un installed that and every worked fine. I think it's touch control or some of it's remains. Try doing a complete reset and see if the problem persists.
Sent from my Nexus 4 using Tapatalk 2
ak700 said:
Had this problem for a while with the same setup. But was using Touch Control. Un installed that and every worked fine. I think it's touch control or some of it's remains. Try doing a complete reset and see if the problem persists.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
thank..but i don't use touch control. What rom and kernel are u using ?. And the version also
ga_ran said:
thank..but i don't use touch control. What rom and kernel are u using ?. And the version also
Click to expand...
Click to collapse
Do you undervolt heavily?
gee2012 said:
Do you undervolt heavily?
Click to expand...
Click to collapse
i use franco r134, uv -100mv, my chip is fast. i think it's ok. I also try not uv but it still happens
ga_ran said:
i use franco r134, uv -100mv, my chip is fast. i think it's ok. I also try not uv but it still happens
Click to expand...
Click to collapse
Try a data/factory reset, save files first off course and restore apps with TB. That may fix the issue. I UV -100mV too and have no issues so far.
gee2012 said:
Try a data/factory reset, save files first off course and restore apps with TB. That may fix the issue. I UV -100mV too and have no issues so far.
Click to expand...
Click to collapse
yah, i will give it a try..hope is ok
Unfortunately, it still happens (
Are you sure about touch control....this happened to me only when I had touch control installed...
htnawsaj said:
Are you sure about touch control....this happened to me only when I had touch control installed...
Click to expand...
Click to collapse
no. i have never install this software...
Are you using tight jeans? I'm serious... I had this issue once after my phone was in my pocket using really tight jeans... It took a about 40 seconds until my screen began to work again. After that I stopped putting my phone on tight places, and never had the issue again.
Sent from my Nexus 4 using xda premium
Related
I have been using syndicate rom and if I leave my phone on standby after a while it doesn't come back on. It also did this on latest bonsai. I have to do a battery pull to get it back. Any suggestions would be appreciated. Oh I always wipe 3x and flash then wipe again 3x and flash.
Sent from my second head?
jarnail24 said:
I have been using syndicate rom and if I leave my phone on standby after a while it doesn't come back on. It also did this on latest bonsai. I have to do a battery pull to get it back. Any suggestions would be appreciated. Oh I always wipe 3x and flash then wipe again 3x and flash.
Sent from my second head?
Click to expand...
Click to collapse
Try using setcpu to set your minimum to 200 that should help.
Sent from my Samsung-SPH-D700 using XDA App
deano0714 said:
Try using setcpu to set your minimum to 200 that should help.
Sent from my Samsung-SPH-D700 using XDA App
Click to expand...
Click to collapse
Disable all setCPU screenoff profiles if you have any also. That may help.
I'm getting the samething.. and its starting to piss me off.. I have to pull my battery out like 6 to 7 times a day.. I read somewhere on here that it was related to EB13.. but im not sure.. but it didnt start happening on my epic till I ugraded to EB13 Twilight... I'm gonna try and downgrade later on after I get off work..
this also use to happen to me when I started putting diffrent roms on my Touch Pro 2 back in the day..
Same here but it started with eb13 bonsai.
Sent from my second head.
Anybody have any idea on fixing this?
Sent from my Second head
jarnail24 said:
Anybody have any idea on fixing this?
Sent from my Second head
Click to expand...
Click to collapse
Try fixing the permissions using rom manager, if that doesn't work...wipe and reflash the rom...sometimes the apps u install on the phone is wat causes it.
A friend of mine got a nexus s and his automatic display brightness doesn´t seem to work until today. His device is not rooted or has a custom rom, so I can´t test, if it´s an software bug or not.
His firmware is android 4.0 since more than 3 months.
Is there a possibility to check this issue? With an other app or something? Sending back his device is an option, he want to choose as his last possibility.
Impact7 said:
A friend of mine got a nexus s and his automatic display brightness doesn´t seem to work until today. His device is not rooted or has a custom rom, so I can´t test, if it´s an software bug or not.
His firmware is android 4.0 since more than 3 months.
Is there a possibility to check this issue? With an other app or something? Sending back his device is an option, he want to choose as his last possibility.
Click to expand...
Click to collapse
Automatic brightness on ics sucks, it doesn't work properly
Sent from my ARCHOS 80G9 using XDA Premium HD app
DarkhShadow said:
Automatic brightness on ics sucks, it doesn't work properly
Sent from my ARCHOS 80G9 using XDA Premium HD app
Click to expand...
Click to collapse
He used it until more than 3 months without any problems. That´s why I don´t get why it shouldn´t work anymore.
Impact7 said:
He used it until more than 3 months without any problems. That´s why I don´t get why it shouldn´t work anymore.
Click to expand...
Click to collapse
Idk about that, but it never works properly for me full stop
Sent from my ARCHOS 80G9 using XDA Premium HD app
My stoped work too, after using this rom.. Tomorrow I will flash another one to see, if my sensor work...
Sent from my Nexus S using Tapatalk 2 Beta-4
keb00 said:
My stoped work too, after using this rom.. Tomorrow I will flash another one to see, if my sensor work...
Sent from my Nexus S using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
I´m waiting for your anwser^^
Should be a software bug. Ask him if he would do a factory reset.
Sent from my Nexus S using Tapatalk
You can always try Sensors applcation to check if light sensor is working properly:
URL: play.google.com/store/apps/details?id=com.miian.android.sensors
shockem said:
Should be a software bug. Ask him if he would do a factory reset.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
He did a factory reset and now it seems to work again. But he also mentioned that the display is a bit darker than before. But even though it is, he must live with it
Impact7 said:
He did a factory reset and now it seems to work again. But he also mentioned that the display is a bit darker than before. But even though it is, he must live with it
Click to expand...
Click to collapse
Lowest value is lower in ICS then it was in GB. IMHO crap, but it can be changed in framework-res.apk.
Impact7 said:
I´m waiting for your anwser^^
Click to expand...
Click to collapse
I re-flashed and work again... A some bug....
Set up as followed: latest version of slim bean ROM, and latest faux kernel.
I just set this up a few hours ago, apps and all and then the phone reboot and all my settings, passwords,etc had been reset. Its like the phone did a partial factory reset and honestly I am stumped . It so happen to do this right after I deleted set CPU...any input would be helpful.
Sent from my Nexus 4 using Tapatalk 2
Erazo1986 said:
Set up as followed: latest version of slim bean ROM, and latest faux kernel.
I just set this up a few hours ago, apps and all and then the phone reboot and all my settings, passwords,etc had been reset. Its like the phone did a partial factory reset and honestly I am stumped . It so happen to do this right after I deleted set CPU...any input would be helpful.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Well first of all, I believe this should be in the Q&A Section.
Second thing: I have had this happen to me too. I was running _Motley's kernel and I had the same thing happen. I believe that this was caused by me UV'ing too much. If you're OC'ed, I'd lower it. If you're UV'ed, I'd raise the voltages too. It may have just been one of the little quirks of Android and may be impossible to reproduce.
Best of luck,
Connor Baker
Connor Baker said:
Well first of all, I believe this should be in the Q&A Section.
Second thing: I have had this happen to me too. I was running _Motley's kernel and I had the same thing happen. I believe that this was caused by me UV'ing too much. If you're OC'ed, I'd lower it. If you're UV'ed, I'd raise the voltages too. It may have just been one of the little quirks of Android and may be impossible to reproduce.
Best of luck,
Connor Baker
Click to expand...
Click to collapse
Thank you and I will remember that for next time.
Sent from my Nexus 4 using Tapatalk 2
Make sure fsync isn't ticked off. Sounds like it could be that..
Vangelis13 said:
Make sure fsync isn't ticked off. Sounds like it could be that..
Click to expand...
Click to collapse
Fsync? Where's that option?
Sent from my Nexus 4 using Tapatalk 2
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.
I've been facing ghost touches for few days now, and I their to fix it with changes ROMS and kernels, but non of that helped no matter which ROM I've tried.
So I thought to myself why not change the voltages? I've increased the voltages by +75 now, and from that moment I have not faced any ghost touches, I don't know if it's just luck or a real solution. So I would like to know of you his try that, will it help you too? Try it and tell me.
Thanks
Sent from my A0001 using XDA Free mobile app
marwan91 said:
I've been facing ghost touches for few days now, and I their to fix it with changes ROMS and kernels, but non of that helped no matter which ROM I've tried.
So I thought to myself why not change the voltages? I've increased the voltages by +75 now, and from that moment I have not faced any ghost touches, I don't know if it's just luck or a real solution. So I would like to know of you his try that, will it help you too? Try it and tell me.
Thanks
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Can you provide a bit more info on what you changed and where?
gsmyth said:
Can you provide a bit more info on what you changed and where?
Click to expand...
Click to collapse
If you have custom kernel, like AK, Franco, boeffela.. Etc you can change mpu voltages using application such as Trickstermod, synapse( AK specific).
Sent from my A0001 using XDA Free mobile app
my ghost touch was fixed after flashing Temasek's 5.1 . Back in 5.0.2 it was miserable and I can't type without registering random alphabet or swipes.
marwan91 said:
If you have custom kernel, like AK, Franco, boeffela.. Etc you can change mpu voltages using application such as Trickstermod, synapse( AK specific).
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Have you noticed any impact on battery?
I had some touch issues previously, not as bad as some on here but they mostly seem to have gone away after updating to CM12S.
I still didn't test the battery, because I applied this setting just 5 hours ago. But is supposed to effect battery life for bad. But I don't care if this keeps me away from touch issues.
Sent from my A0001 using XDA Free mobile app
I have -85mv undervolted and I don't have any ghost touches....but overvolting could help who knows...
phoenixita said:
I have -85mv undervolted and I don't have any ghost touches....but overvolting could help who knows...
Click to expand...
Click to collapse
You had them before undervolting?
Sent from my A0001 using XDA Free mobile app
IMHO.....this ghost touch problem is absolutely relative....like some never face it, others get it solved with makeshift fixes while others face it all the time.
Yes, it's so annoying, I noticed when the phone is charged, the issue is gone, but when using it until the battery is 50% the issue is back. So I think it might be something related to the CPU and screen temperature, when it's hot, it's works good, when it's cold it starts to stutter.
Sent from my A0001 using XDA Free mobile app
marwan91 said:
Yes, it's so annoying, I noticed when the phone is charged, the issue is gone, but when using it until the battery is 50% the issue is back. So I think it might be something related to the CPU and screen temperature, when it's hot, it's works good, when it's cold it starts to stutter.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
give this a shot
http://forum.xda-developers.com/showthread.php?t=3079029
ViditM14 said:
give this a shot
http://forum.xda-developers.com/showthread.php?t=3079029
Click to expand...
Click to collapse
thanks mate i will for sure..
Reidwan said:
my ghost touch was fixed after flashing Temasek's 5.1 . Back in 5.0.2 it was miserable and I can't type without registering random alphabet or swipes.
Click to expand...
Click to collapse
Out of interest, did you do a full wipe before installing?
At this stage I'm willing to do anything!
emailrob said:
Out of interest, did you do a full wipe before installing?
At this stage I'm willing to do anything!
Click to expand...
Click to collapse
of course, clean wipe as usual. I know its a headache but at least its working for me.
Reidwan said:
of course, clean wipe as usual. I know its a headache but at least its working for me.
Click to expand...
Click to collapse
Thanks. I did a full wipe etc. and have put it on. I THINK OK so far. The real test seems to be putting swiftkey back on. I'll report back.