Anyone else having problem's waking up the screen when receiving phone calls? Or default ringtones continuously ringing without pausing? I love the rom,but this can be quite frustrating. On the other hand,cyanogenmod has been flawless for me.
Sent from my CyanogenMod powered G2.
Yea i had that problem too. Someone said to try the pershoot kernel. I havnt had that problem happen again yet. Been running it for about 4 hours
Sent from my HTC Vision using XDA App
i switch back and forth to different roms but have noticed lately that on my Evo and running Synergy that under Facebook Events none of the birthdays are showing up, can someone tell me how to get this going again as its been on there before, do i need to swithc Rom's or anything like that?
thank you
Bump, anyone?
Same problem here :-(
I think the Facebook app itself is the problem. No need to switch ROMS in my opinion
Sent from my PC36100 using XDA App
I just saw an update about an hour ago. that exact issue is on the changelog.
Udate it i had the same problem till i udated it just a hour ago
Sent from my PC36100 using XDA App
So first off the app search function sucks...
Has anyone had a problem where the screen suddenly becomes unresponsive to touch? I can turn the screen on and off just fine with the power button but can't actually unlock it since it doesn't recognize my finger touching the screen. Only way to fix it was to do a battery pull.
I'm also on Eagles Blood with the latest Franco kernel.
I've never experienced this problem. I've run Codename Android, Redemption Rom, and currently on AOKP. I've used Leankernel, Defiant kernel and am currently using Faux123's kernel. As far as the app search function I can't concur because I've never used it.
Sent from my Galaxy Nexus
gravis86 said:
So first off the app search function sucks...
Has anyone had a problem where the screen suddenly becomes unresponsive to touch? I can turn the screen on and off just fine with the power button but can't actually unlock it since it doesn't recognize my finger touching the screen. Only way to fix it was to do a battery pull.
I'm also on Eagles Blood with the latest Franco kernel.
Click to expand...
Click to collapse
To answer your question: No.
Was the phone plugged in when it was unresponsive?
Sent from my Galaxy Nexus using XDA App
i have the same experience, once in a while,
if you have patience, if you wait like 5-10 mins later, it will be responsive again.
I had the unresponsive screen when I turned the screen on to unlock but I couldn't draw my unlock pattern. Closed and opened the screen using power button twice and it was working again. I've also noticed that sometimes the screen doesn't register touches soon after turning it on. Have to always redraw my pattern because first bit is missed off.
Sent from my Galaxy Nexus using xda premium
qwerp_ said:
i have the same experience, once in a while,
if you have patience, if you wait like 5-10 mins later, it will be responsive again.
Click to expand...
Click to collapse
Same here. Very annoying. Is there a fix yet?
I had this problem once since having the phone in November. I did do a battery pull but its good to know you can wait 5-10 minutes.
Also stock phone 4.0.2 ota so its happening on unrooted phones as well.
Sent from my Galaxy Nexus using XDA App
qwerp_ said:
i have the same experience, once in a while,
if you have patience, if you wait like 5-10 mins later, it will be responsive again.
Click to expand...
Click to collapse
There is said to be a multi touch issue with the galaxy Nexus, I have experienced it myself. There is not a fix that I know of for the issue yet.
Sent from my GNex running gummy v0.7.0
Hydera5 said:
There is said to be a multi touch issue with the galaxy Nexus, I have experienced it myself. There is not a fix that I know of for the issue yet.
Sent from my GNex running gummy v0.7.0
Click to expand...
Click to collapse
This thread is not about the issue.
Sent from my Galaxy Nexus using XDA App
I'm currently on Slim, but the same problem occurs in AOKP and CM9. I've tried the stock kernel and the Franco milestones.
When I have the screen time out set at 1 minute, the screen doesn't turn off at all - even after 20 minutes. If I set the time out at 30 seconds it turns off like it should.
Anyone else with this problem?
Sent from my Galaxy Nexus using xda app-developers app
I have been running aokp build 5 for a about a day now and I only have one problem with it. Whenever I turn my screen on the brightness also gets turned up very high for about a second then goes back to the normal setting It should be at. This happens most of the time but not always and I can't figure out what is causing it. Does anyone have a fix for this? Thanks!
Sent from my SGH-T989 using xda premium