Hi,
I just bought a N1, it works great so far, the only problem it has is when I wake it up by using the power button. Sometimes it doesn't work but most of the time it works.
I thought it was the power button but I installed cyanogenmod, I set up the trackball to wake up the device and it also happens that way.
Are anybody having the same problem?
Same problem. I think is a problem with Cyanogenmod, when having stock firmware never happened tu me.
Sent from my Nexus One using XDA App
There's a six second lag between going to sleep and waking up. Maybe this is what you're seeing?
...although I have heard other complaints about this with CM.
Sent from my Nexus One using XDA App
perrera said:
Same problem. I think is a problem with Cyanogenmod, when having stock firmware never happened tu me.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I used the stock firmware only two days and I didn't noticed it, but I am not sure and I don't want to flash it back, I like Cyanogenmod. Maybe I will try 2.3 if it comes out soon.
danger-rat said:
There's a six second lag between going to sleep and waking up. Maybe this is what you're seeing?
...although I have heard other complaints about this with CM.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I thought it was Widget Locker. With Widget Lockers it fails often I think because the six second lag.
Related
I was wondering if anyone else has ever experienced this issue. I am currently running the latest cyan 7 nightly but i do recall it happening 2 other times on cyan 7 RC4 and RC1. I am not at all saying it only happens on cyan, i am just showing when and how it happened. All 3 times it happened my battery was below 10% and i restarted my phone to have the issue occur. It seems as if every button on the screen would choose the exact mirrored opposite of itself on the screen. If i would press the phone icon on adw the default on the other side wich happens to be internet browser would launch. If i pulled down on the notification bar the app drawer would open and so on and so on. the only thing that was regular was when i would press an option in the main menu such as wifi or location, basically anything that didnt have an option next to it that it could switch to. after a few minutes i restarted the phone again to have the issue go away as fast as it started. It was not only in adw for those wondering it was anything that had an option next to it, such as pressing favorites in the browser and it would launch whatever is opp of it, settings i think im not positive at the moment. Oh well i just figured i would share some of my story with all of u in case it somehow starts a topic or even some how helps somebody out in any way. thanks, veritas
Sent from my HTC Vision using XDA Premium App
something told me i was going to be the only one with this crazy issue lol.
Sent from my HTC Vision using XDA Premium App
i know what you mean. I had that happen too. It didn't happen anymore after I flashed to another ROM. I'm on CM7 RC4
veritasaequita said:
something told me i was going to be the only one with this crazy issue lol.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I work for a cell phone repair company and we recently had a G2 come in with heavy water damage. after doing the water damage treatment the phone powered on, everything working fine.
I powered it off to put my SIM into it to test the call functionality and when it powered back up the entire touchscreen was backwards, even the softkeys at the bottom.
we replaced the digitizer and that fixed the issue, so maybe T-Mobile or HTC will warranty it if its a bad digi
Hey, do any of you guys get wake up lag? If i don't wake up my phone for about 3 minutes, and I try and wake it up, it takes a good 3-4 seconds to turn on the screen. is this normal? I am running gingerblur, launcher pro, and a fingerprint sensor, so I don't know if that is what is slowing it down.
yeah its normal i have it too. i returned my atrix for the same reason got the new one right out of the box with the same issue
thanks for the quick reply!! hopefully this will be fixed in a future update...
yep. it got used to it already.
Nope. I have no wakeup lag. I would say that mine takes a fraction of 1 second after I press the power button for the screen to be ready to be unlocked.
are you running everything stock motoblur? and do u have fingerprint setup?
Search button anyone? This topic has been done to death....
3-5 secs lag is too much. I tested this (in 1.86) with//without fingerprint lock, with/without launcher pro, with/without GB 3.5 and although fingerprint and LP seem to add a small lag, no combination that I tested had anything close to 3 secs of lag. The few times I've seen that kind of lag in the couple of months I've owned the phone were far and few between.
Yes, 3 seconds or so is normal, sometimes out doesn't turn on. Tomorrow I'm exchanging for an Infuse.
Sent from my MB860 using XDA App
Don't really have 3 secs, I'd say about 1 or max 2. Go louncher ex removed motoblur widgets, everything else stock and live wallpaper.
Sent from my MB860 using XDA App
cheetah2k said:
Search button anyone? This topic has been done to death....
Click to expand...
Click to collapse
Seriously. I mean when you start a topic it shows similar topics, right? Not that hard.
Lurk moar, people.
Sent from my MB860 using XDA App
Turn off fingerprint sensor and problem solved
I have this problem as well, very annoying. It has happened ever since i first booted it. But its weird, even though the screen is off, its is still responsive and i can feel the screen vibrate when i drag where the unlock bar would be across the screen.
If you are using set cpu in sleep below 500mhz you maybe will get a delay/lag
.......................................................
Sent from my loved atrix ;D
No lag.
Only when it boots up the first time but that's expected when all my crap is loading up.
I don't use the finger scanner or password or anything just turn on the volume button and its fast no lag.
Haplodroid said:
Yes, 3 seconds or so is normal, sometimes out doesn't turn on. Tomorrow I'm exchanging for an Infuse.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Ha. I just did that. Im getting mine shipped today, they didn't tell me to return the Atrix tho. Shall I keep it?
Sent from my MB860 using XDA Premium App
I have tried kj4, kka and sheep rom. All have the annoying long wait after pressing power button intil the screen is lit up. Also tried different CPU governors without result. What is the problem here? And can it be solved?
Is it just me, or do others experience this as a prob?
Sent from my GT-N7000 using Tapatalk
I've got the same rom, but I don't see the problem you described.... try to reinstall the rom.
ps: you should post this under the thread of your rom, without creating a new one
You may have a defective device.
Sent from my GT-N7000 using xda premium
mine is like 2seconds after the bootanimations and stops at samsung logo..fast enough for me
I have the same problem with my note. I just got mine yesterday. No clue as to what's causing it. I updated my firmware to the latest but left the old kernel so i could keep root access. Had the same problem with both the new and the old firmware.
Sent from my GT-N7000 using XDA App
resistant said:
mine is like 2seconds after the bootanimations and stops at samsung logo..fast enough for me
Click to expand...
Click to collapse
I dont mean at starup, i mean when turning screen on.
Delux9364 said:
ps: you should post this under the thread of your rom, without creating a new one
Click to expand...
Click to collapse
The prob is on all roms.
Delux9364 said:
I've got the same rom, but I don't see the problem you described.... try to reinstall the rom.
Click to expand...
Click to collapse
U have 3 roms on your device????
Sent from my GT-N7000 using Tapatalk
Just to clarify the issue here:
When the phone is on but screen has been off for a while, the time between pushing pwr button and until the screen lights up is about 1 second, it may not sound much but it just enough to make one press the button once again. Not what i am used to on my previous androids from HTC.
Sent from my GT-N7000 using Tapatalk
Same here. KJ4, stock KKA and sheep KKA. It is annoying indeed...
Probably a user experience thing, you guys who claim to NOT have the issue:
Can you lock the screen and wait for like 10 mins and then on the screen again and time the delay from button press to screen light-up?
Sent from my GT-N7000 using Tapatalk
pjm77 said:
Same here. KJ4, stock KKA and sheep KKA. It is annoying indeed...
Click to expand...
Click to collapse
Where do you come frome? I mean are u used to Samsung devices or something else?
I am judging this by my 2 previous HTC's whith all kinds of different Roms where I have never seen this.
My thought is that it is on all notes but some people does not see it as a problem but you and me do.
nemoshotyany said:
I have the same problem with my note. I just got mine yesterday. No clue as to what's causing it. I updated my firmware to the latest but left the old kernel so i could keep root access. Had the same problem with both the new and the old firmware.
Same questions 4 u.
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
Sent from my GT-N7000 using Tapatalk
Sent from my GT-N7000 using Tapatalk
I am having the same issue. Takes 1-2 seconds until the device is fully powered up from standby...
I think I figured out the issue. I disabled weather on the lock screen and now my phone comes straight on. Maybe everyone with the issue can try that and see if it works for them?
Confirmed, getting rid of the weather on the lock screen gets rid of the lag
I'm having the same prob. I'll try removing the weather app and see if that helps.
Great no I cant remember how to remove it. help
Sent from my GT-N7000 using xda premium
getmouse said:
I'm having the same prob. I'll try removing the weather app and see if that helps.
Great no I cant remember how to remove it. help
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Settings, Display, Screen Display, and uncheck weather.
Nope still does it, 2sec delay.
snyggsomfan said:
I have tried kj4, kka and sheep rom. All have the annoying long wait after pressing power button intil the screen is lit up. Also tried different CPU governors without result. What is the problem here? And can it be solved?
Is it just me, or do others experience this as a prob?
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
nope mine is snap on... did u try turning off display animations? if not try it
This was there even on the s2..
yea, mines also has the same 1-2 sec delay. no weather on lock screen. found it odd, cause i've only had HTC phones so far, and never saw this.
Samsung don't use early_resume in the kernel, that Seems To be more qualcomm Related code.
It's that Code that gives you instant screen resume on the HTC devices et al.
I found this a niggle on the note as well, but have got Used to it,especially compared to amount of work it would take to fix it.
This has been happening since I remember getting the device. About 3/5 times when I bring my device out of standby and I go to enter my pattern the touch is off. I have "show touches" enabled in developer options to verify this.
When I put my finger on the top left dot of the 3X3 pattern, which is around the middle-left of the screen, it is detecting that I'm touching the device all the way in the top left corner. If I drag my finger around the screen, the touch is offset. If I remove my finger from the screen and place it back on the screen, then it is properly detected.
I didn't run on stock for very long, maybe an hour or two, before I rooted and flashed AOKP. Right now I'm on WhiteHawkx's unnoficial AOKP nightly and Franco's Kernel (r122).
My plan is to flash back to stock and see if it still happens then. But currently I have a really busy week ahead and don't have time so looking for insight.
Anyone else experience something like this?
No one? So I guess I should call Google for a warranty exchange?
Sent from my Nexus 4 using xda premium
fone_fanatic said:
No one? So I guess I should call Google for a warranty exchange?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I would do that if I were you.
Sent from my Nexus 4 using xda app-developers app
Try recalibrating the touch screen, I think there's an option in settings.
Sent from my HTC One X using xda app-developers app
It's franco's kernel, I have it too.
.coomb. said:
It's franco's kernel, I have it too.
Click to expand...
Click to collapse
I posted in that thread a while ago about this issue and no one confirmed. Thanks for your reply. I'm going to go back to stock this weekend and run it for a couple days to verify.
Sent from my Nexus 4 using xda premium
fone_fanatic said:
I posted in that thread a while ago about this issue and no one confirmed. Thanks for your reply. I'm going to go back to stock this weekend and run it for a couple days to verify.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Let me know your results. If it persists, I might have to send mine back.
I'm on stock ROM. I have this issue too, when I power on and drag to unlock, I get a delayed mismatched response. I have to power off then back on again.
It started this recently, so might be app related.
Sent from my Nexus 4 using xda app-developers app
Vyker said:
I'm on stock ROM. I have this issue too, when I power on and drag to unlock, I get a delayed mismatched response. I have to power off then back on again.
It started this recently, so might be app related.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What kernel are you running?
Vyker said:
I'm on stock ROM. I have this issue too, when I power on and drag to unlock, I get a delayed mismatched response. I have to power off then back on again.
It started this recently, so might be app related.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Turn on " show touches" in developer options to help verify if you the save thing happening.
I don't have to reboot mine but I have to lift finger of screen and put back on to get it to properly detect where the touch should be.
Sent from my Nexus 4 using xda premium
So just as a follow up I reverted to stock for 5 days and didn't see this issue. Flashed back to AOKP and Franco kernel and now it's happening randomly when I go to hang up a call. I tap on the red hang up bar and it detects the touch in the top left corner.
I called Google play support but since I didn't buy my device from them they directed me to lg.
I'm starting to think it's my screen protector.
Sent from my Nexus 4 using xda premium
lol, I had insensitivity issues on the bottom of the screen way back, I use a displayed pin pad on lockscreen so I just tap a certain spot to unlock, I sometimes wonder why the digitizer register incorrectly.
flashing a different kernel helped, I'm using motleys.
Have had this problem since launch, im on stock rooted, maybe its a certain app?
If anyone wants to compare their apps with me to find a similar problem, shoot me a pm
Randomly it seems, when I tap on the touchscreen on my new N7 2013, nothing happens, and I have to repeat the process several times before my touches are registered.
Does anyone else have this problem?
Macmee said:
Randomly it seems, when I tap on the touchscreen on my new N7 2013, nothing happens, and I have to repeat the process several times before my touches are registered.
Does anyone else have this problem?
Click to expand...
Click to collapse
See my thread titled " Another touch issue, with reproducible steps".
Go into developer options and enable "Show touches" and "Pointer location"
If you see your touches registering but the app isn't responding, it is probably a problem with the app. If you see random stuff on the screen, probably a problem with the digitizer or digitizer in combination with the driver/software in this release.
Ive experienced this a few times and it seems to be a software /hardware interface issue with particular custom rom builds ive installed. I know the touchscreen hardware itself was fine when I forced reboot into recovery and the touchscreen worked as normal in custom recovery.
Sent from my Nexus 7 using Tapatalk 2
Is everyone experiencing this or is it only certain units. Mine does it even when holding and firmly pressing. Gonna take it back and try another if its not all.
Sent from my SPH-L720 using xda premium
dcaplinger76 said:
Is everyone experiencing this or is it only certain units. Mine does it even when holding and firmly pressing. Gonna take it back and try another if its not all.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Are you running yours stock
Sent from my Nexus 7 using Tapatalk 2
I am and I'm experiencing same problem I have 32gb stock and installed all updates... Actually did not have problem till update 4.3
Sent 4rm my Paranoid Nexus 4.3 LTE...
kayone73 said:
Are you running yours stock
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yeah totally stock.. this was happening last night and actually today it hasn't happened in the 20 minutes I messed around while working. Gonna hang onto it for now unless it creeps back up
Sent from my SPH-L720 using xda premium
dcaplinger76 said:
Is everyone experiencing this or is it only certain units. Mine does it even when holding and firmly pressing. Gonna take it back and try another if its not all.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
I wouldn't. If you had a Verizon Galaxy Nexus when it came out, you'll remember that it had the same issue with certain points on the screen (lower right hand corner) when using multi-touch applications. The entire screen would either stop seeing input or start going erratic and creating faulty inputs that weren't happening. It isn't a hardware issue, proven by some users experiencing it and some not. The only time I've experienced it is in the Netflix application while trying to choose a show to watch. I re-boot the application and viola, no more issue. Some in this thread even are stating that they only see the problem sometimes after getting the 4.3 update.
In short, it's software and not hardware.
Same issue when not touching with both hands somehow (like if the tablet is flat on a table).
Sent from my Nexus 7 using xda app-developers app
Haven't had a problem with mine. I just got it today, and it's worked like a charm. I bought mine from Gamestop if that helps any.