Related
So, even the the magical iPads homebutton is slower then the Galaxy S 2s one. Also when waking the device up! You will have to live with that. Also this is not a problem at ALL for me, I can not understand why people are always flaming about it.
Please tell me what you think. I know the video is useless, don't tell me that.
This video will fall on deaf ears for the Apple Fanboys I think... because your attachment is Flash and they probably can't view it.
This video clearly shows that Galaxy S2 isn't the only device that takes a second to wake up or return to home, which is nice and all. Still, coming from a HTC Desire, it does present an annoyance, as it's not something you expect from a device that costs that kind of money. I bet the Sensation wakes up instantly...
The thing that's even worse for me is the extra step that just shows a black screen with a clock, before the wallpaper kicks in. I know that's just because I'm using a stock ROM, but they should at least sort that out, because it really looks ugly, slow and cheap.
ThaiM said:
This video will fall on deaf ears for the Apple Fanboys I think... because your attachment is Flash and they probably can't view it.
Click to expand...
Click to collapse
I watched it on my iPad just fine.
666fff said:
I watched it on my iPad just fine.
Click to expand...
Click to collapse
You really want me to upload somewhere else than YouTube?
I know home button lags and that there is a wake-up lag on my SII, but i haven't been in a situation of life and death up till now to rely on home button to save my life. So i'm still cool with it, even though i would have liked the phone to perform faster.
apple falling down with releasing SGS2 ))
fanboys are unhappy
Well the SGS 1 home button press is nearly instant when exiting from an application. So I expected the same from SGS 2. I'll flash it with cyanogen when I get my JIG to reset the counter. I hear it doesn't have the lag.
1-2 second lag also cannot accept is crazy...
Maybe this is why apple is suing Samsung. They even copied wake up lag. Lol. Seriously its not lag its the phone waking up from a lower clock speed while in sleep. Sure they could fix it but battery drain will be worse I think. My quad core i7 also has lag when waking up.
Thanks for sharing the video. I wonder if someone could show an HTC wake up I bet there is a small lag too
Sent from my GT-I9100 using XDA App
gvoima said:
Well the SGS 1 home button press is nearly instant when exiting from an application. So I expected the same from SGS 2. I'll flash it with cyanogen when I get my JIG to reset the counter. I hear it doesn't have the lag.
Click to expand...
Click to collapse
Im using Cyanogenmod, and theres still "lag" if the device is in deep sleep.
But if you just lock the screen, and then unlocks, its instant.
As the first post, I think this is normal.
janis605 said:
You really want me to upload somewhere else than YouTube?
Click to expand...
Click to collapse
Skyfire
LOL nice video, I never really understand when people said they have "wake-up lag" coming from an iPhone 4 it's pretty much the same. Maybe 2 seconds is too much but anything under 1 second is definitely how it should be.
blue265 said:
Maybe this is why apple is suing Samsung. They even copied wake up lag. Lol. Seriously its not lag its the phone waking up from a lower clock speed while in sleep. Sure they could fix it but battery drain will be worse I think. My quad core i7 also has lag when waking up.
Thanks for sharing the video. I wonder if someone could show an HTC wake up I bet there is a small lag too
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
exactly... it takes a while waking your phone from deep sleep. u all should be happy u r having deep sleep. to prove this.... next time your charging your phone... press home button to wake the phone WOW it wakes up INSTANTLY ! haha
goodsmile said:
exactly... it takes a while waking your phone from deep sleep. u all should be happy u r having deep sleep. to prove this.... next time your charging your phone... press home button to wake the phone WOW it wakes up INSTANTLY ! haha
Click to expand...
Click to collapse
By god its TRUE!!!!!!!
I honestly dont understand what the fuss is about with the home button lag and wake up lag, such a miniscule issue thats not worth getting upset for.
Can anyone exactly explain why this is frustrating or annoying ?
EarlZ said:
I honestly dont understand what the fuss is about with the home button lag and wake up lag, such a miniscule issue thats not worth getting upset for.
Can anyone exactly explain why this is frustrating or annoying ?
Click to expand...
Click to collapse
Let's say you have 500ms delay after pressing the home button. In real life, the delay is much much longer but let's say 500ms. How many times do you press the home button in a day's use? I personally press it at least 300 times a day, actually much more times in a busy day, but let's say 300.
So 300 x 0.5 seconds: 150 seconds = 2.5 minutes of my life every single day is lost because Samsung can't code properly.
I've been using this phone for 2 months: 60 days. 2.5 minutes x 60 = 150 minutes of my life gone waiting so far. That's more than 2.5 hours in two months... Vanished.. Gone.. Just waiting for the home screen to appear, nothing else...
goodsmile said:
exactly... it takes a while waking your phone from deep sleep. u all should be happy u r having deep sleep. to prove this.... next time your charging your phone... press home button to wake the phone WOW it wakes up INSTANTLY ! haha
Click to expand...
Click to collapse
Nothing wrong with deep sleep but it doesn't have to take 1.5 seconds. Deep sleep still means that RAM is refreshed, so it is not impossible to do this much faster. Waking CPU <10ms, restoring CPU state (reloading code etc) <100ms, so where is the time spent? The delays are probably related to other hardware like GPU etc since everything must be ready. But it is not impossible to do this faster.
This is not a big problem for me, but I cannot see any reason not to demand improvement.
EDIT: I'm talking about wake-up lag of course, probably a bit off-topic here...
There is no Homebutton-lag! It has to have a delay because on the standard Samsung rom it has to "wait" for a second press because they mapped an action to double pressing the homebutton. I don't know why you people can't understand this... On CM7 there isn't this lag because there is nothing mapped on double pressing the homebutton.
Oh and wakeup lag is a whole other story...
gvoima said:
Well the SGS 1 home button press is nearly instant when exiting from an application. So I expected the same from SGS 2. I'll flash it with cyanogen when I get my JIG to reset the counter. I hear it doesn't have the lag.
Click to expand...
Click to collapse
It its so that the phone has enough time to detect a second click which its used for voice control. Find a room without the voice control installed and it won't have the exit lag.
Guys there is a new update for our beloved NOTE in india
Please go ahead and tell us as what changes you notice.
It is about 8mb and my phone is rebooting right now.
Happy updating guys
I think you are late for the party !!!
What changes do you notice?
Sent from my GT-N7000 using Tapatalk
darthvedor said:
I think you are late for the party !!!
Click to expand...
Click to collapse
I think he meant OTA .. the update was available for download earlier , but OTA came in yesterday.
I also installed it and i find its touch responsiveness to be pretty smooth compared to the old versions ...
Dr mentioned that this also has a better battery performance..
Well i found the OTA update on 2nd March itself, hence you are late for the party
The battery performance has improved drastically, No call drops as in LB1, Lag has reduced, google+ as default app .... better than any previous release. Last night my cell was on standby for 8 hours with only 1% power consumption. Hope this helps.
Coolkriss said:
I think he meant OTA .. the update was available for download earlier , but OTA came in yesterday.
I also installed it and i find its touch responsiveness to be pretty smooth compared to the old versions ...
Dr mentioned that this also has a better battery performance..
Click to expand...
Click to collapse
OTA came in a week ago :blink:
It also has Google+ and Google Messenger apps...
great battery improvement
Oneiricl said:
OTA came in a week ago :blink:
It also has Google+ and Google Messenger apps...
Click to expand...
Click to collapse
thank you so much guys let us please keep informing each other for all the additional changes that you notice.
Keyboard lag when charger connected is gone.
Low response issue in letter N and M on the keyboard is gone.
Ashoka Hindi Keybaord included.
Battery life is not that well on my end. Lets see.
improvement in wifi range
in a corner of my house where i could not connect to my wifi signal i am able to connect now.
no update found
Hi, there is a lag when i type or hit on the m or n button on the keypad. Otherwise also, when i hit near that area, the screen is unresponsive. Will an update fix that issue?
anoopajith said:
Hi, there is a lag when i type or hit on the m or n button on the keypad. Otherwise also, when i hit near that area, the screen is unresponsive. Will an update fix that issue?
Click to expand...
Click to collapse
Just read 2 posts above yours.
Did you update to the latest yet??
Sent from my GT-N7000 using XDA
i got the update its only 9mb didnt find any difference
improved wifi reception
Guys I reconfirm here that the wifi reception is definitely better.
Besides another add on that I have noticed is that when I hit the wifi toggle in the notification tray a white pop up appears momentarily telling u about the available wifi signals and u can touch and choose whichever u want to connect to. Earlier u always had to go to the wifi settings to be able to do this.
Okay, I've done some observations on the scroll lag issues and here's what I know.
- It persists on 8.1 ROMs too
- It mostly affects custom ROMs
- Switching kernels does not fix it
- Max CPU and GPU does not fix it (even OC)
Here's my suspected causes:
- Our touchscreen driver is bad
- Our touchscreen panel is bad
- Included screen protector is bad (anyone have scroll lag without it?)
Tell me if you notice this too, but when I scroll with my finger in the top right edge, I get almost 0 lag when scrolling. Is it possible its the display sensitivity that isn't stable? Do you feel this too? Maybe its other areas of the screen too.
Please share your ideas and thoughts. We really want to fix this issue as the phone would be so amazing if it didn't lag EVERYWHERE.
I think it's a combination of both : bad touchscreen and bad driver's as it seems to affect both stock, Caf and Los . I did a test with an old Samsung note 4 an iPhone 5s and a Huawei p20 Pro and it seems that there are certain "gaps" in the panel that when in usage register touches with a certain latency . This and also the sub par refresh rate. Even the old iPhone/note had better touch accuracy under heavy load.
I guess this is the price you pay for a 150 euro phone. Some corner's will be cut.
1unu1 said:
I think it's a combination of both : bad touchscreen and bad driver's as it seems to affect both stock, Caf and Los . I did a test with an old Samsung note 4 an iPhone 5s and a Huawei p20 Pro and it seems that there are certain "gaps" in the panel that when in usage register touches with a certain latency . This and also the sub par refresh rate. Even the old iPhone/note had better touch accuracy under heavy load.
I guess this is the price you pay for a 150 euro phone. Some corner's will be cut.
Click to expand...
Click to collapse
I can update the drivers from another kernel. Do you get hot spots on the A1 that you can notice (for me top right very edge)?
Honestly, I've replaced my tianma display in service centre for screen retention issue, i got ilitek ones then the display is super smooth n scrolling is smooth. it's the problem withth your display ",faulty display"
watsusername said:
Honestly, I've replaced my tianma display in service centre for screen retention issue, i got ilitek ones then the display is super smooth n scrolling is smooth. it's the problem withth your display ",faulty display"
Click to expand...
Click to collapse
I have a focaltech 5435 + ili7807. Stuttery scrolling :/
Same here even scrolling the xiaomi official forum (mobile version) lags ao bad
I have ilitek and no lag but colors are washed out and digitizer grid is completely visible
LoVeRice said:
Same here even scrolling the xiaomi official forum (mobile version) lags ao bad
Click to expand...
Click to collapse
Do you get lag when scrolling at the edge of the screen? For me its smooth on the very edges.
tytydraco said:
I can update the drivers from another kernel. Do you get hot spots on the A1 that you can notice (for me top right very edge)?
Click to expand...
Click to collapse
Sorry for late reply. Not really hot spots or you could call them hot spots but the are in a H pattern across the display. Also touch accuracy is abysmal.
Now I've installed Flyme OS the problem still persists that and the screen becoming tottaly unresponsive. But the proximity sensor bug it's gone, so altleast that is a good thing.
If they don't fix altleast some of the bugs in 8.1 I'm goona smash this crap phone into a wall
tytydraco said:
Do you get lag when scrolling at the edge of the screen? For me its smooth on the very edges.
Click to expand...
Click to collapse
Wow, yes its smooth when.scrolling in the edges.
LoVeRice said:
Wow, yes its smooth when.scrolling in the edges.
Click to expand...
Click to collapse
I think it's a bad driver or a bad digitizer. Imma try to fix it soon
You can replicate this lag 100% of the times with this "method", at least for me. Use your thumb with as much flesh touching the screen and then slowly drag your finger. You can notice the scroll lag in every direction.
Same with me, firstly, I thought it is bug of xiaomi rom, may be this will be fix with custom kernel and custom rom. But when custom rom came to mia1, try so many rom but laggy still there, really disapointed.
It is awkward that seem mia1 is the only xiaomi face with this issue. Redmi 5a - lowest price phone of Xiaomi is fine and MI5x same spec with mia1 doesn't have any complain about laggy scroll.
bravovn said:
Same with me, firstly, I thought it is bug of xiaomi rom, may be this will be fix with custom kernel and custom rom. But when custom rom came to mia1, try so many rom but laggy still there, really disapointed.
It is awkward that seem mia1 is the only xiaomi face with this issue. Redmi 5a - lowest price phone of Xiaomi is fine and MI5x same spec with mia1 doesn't have any complain about laggy scroll.
Click to expand...
Click to collapse
I discovered that if you have two fingers on the screen there's no lag. So use one finger and hold it, then start scrolling with your other thumb. 0 lag. It's gotta be a driver thing. I've been working on micro optimizing it but its gotta be something with the scanning frequency when there's only one finger. But frequency is a firmware thing and I dont think we can gen a firmware blob without a manufacturer tool. It's also possible it's a voltage thing (which I can set in the driver). I'll keep working on it but I think its definitely fixable.
Hey guys i dont know this problem, just bought one, does it easily notice?, how can i check it?
It's mostly a software issue, just flashed August nougat rom and the scroll was a little more responsive
nach0x said:
It's mostly a software issue, just flashed August nougat rom and the scroll was a little more responsive
Click to expand...
Click to collapse
Oh interesting. I'll check it out
nach0x said:
It's mostly a software issue, just flashed August nougat rom and the scroll was a little more responsive
Click to expand...
Click to collapse
i did this. no improvement whatsoever.
mr xombie said:
i did this. no improvement whatsoever.
Click to expand...
Click to collapse
Did you start having the issue when you first got the phone or after you first flashed a custom ROM? Maybe its a persist thing.
watsusername said:
Honestly, I've replaced my tianma display in service centre for screen retention issue, i got ilitek ones then the display is super smooth n scrolling is smooth. it's the problem withth your display ",faulty display"
Click to expand...
Click to collapse
It would be interesting to know what screens those experiencing problems have.
(dial *#*#6484#*#* - click version information)
I get no lag at all, I have checked and I also have a ilitek screen.
Does the finger print unlock from an off screen seen slow to anyone?
GCbard said:
Does the finger print unlock from an off screen seen slow to anyone?
Click to expand...
Click to collapse
Yes, Google introduced that 'feature' with June update to alleviate screen flashing issues
ram4ufriends said:
Yes, Google introduced that 'feature' with June update to alleviate screen flashing issues
Click to expand...
Click to collapse
Is this something you can change with your ambient display being on or off?
Created it in issue tracker still star it
https://issuetracker.google.com/issues/109710373
bill10 said:
Is this something you can change with your ambient display being on or off?
Click to expand...
Click to collapse
Yes, Ambient Display on will reduce the delay
---------- Post added at 05:50 AM ---------- Previous post was at 05:49 AM ----------
theserpent said:
Created it in issue tracker still star it
https://issuetracker.google.com/issues/109710373
Click to expand...
Click to collapse
The delay was deliberately increased to alleviate screen flickering issues... I don't think they will do anything about it
ram4ufriends said:
Yes, Ambient Display on will reduce the delay
Not true. Have always had Ambient Display on, and I am experiencing the fingerprint unlock lag.
Click to expand...
Click to collapse
Ok so if the fingerprint is slow with ambient display on then this is new. So if you update you might as well turn ambient display off as I have always done to save battery. Now that the fingerprint is slow with ambient display on or off it really doesn't matter now. You have a slow fingerprint
the fingerprint sensor is 1 sec slower with both ambient display on&off.
Very very annoying
idees said:
the fingerprint sensor is 1 sec slower with both ambient display on&off.
Very very annoying
Click to expand...
Click to collapse
You can thank google & lg for that one!
https://forum.xda-developers.com/pi...aimen-flash-kernel-1-00-t3702057/post76720456
They first introduced this in P, so I have had it for awhile. One work around is to tap the power button first, that turns on the display and then the fingerprint works faster. It feels smoother and faster. I got used to doing that pretty quickly and it seems natural now.
TonikJDK said:
They first introduced this in P, so I have had it for awhile. One work around is to tap the power button first, that turns on the display and then the fingerprint works faster. It feels smoother and faster. I got used to doing that pretty quickly and it seems natural now.
Click to expand...
Click to collapse
Agreed. However, I hate it when google takes one of the best features of our devices, makes it not as good as when we first got it, then calls it new and improved because they used a new lg panel. Oh well, that's progress.......I guess! ??
For me, even unlocking screen with power button takes longer now. Wtf...
pokosik said:
For me, even unlocking screen with power button takes longer now. Wtf...
Click to expand...
Click to collapse
Yep
https://forum.xda-developers.com/pi...low-finger-print-unlock-t3799880/post76724433
The same delay is there for me when using the fingerprint sensor or when pressing the power button. While I've read about others having a similar issue before, I never had the delay prior to the June security update. Turning on ambient display does decrease the delay, but I'm not an ambient display user.
TonikJDK said:
They first introduced this in P, so I have had it for awhile. One work around is to tap the power button first, that turns on the display and then the fingerprint works faster. It feels smoother and faster. I got used to doing that pretty quickly and it seems natural now.
Click to expand...
Click to collapse
This does work, but it's not something I'm going to do. Positioning my hand to hit them both in succession is a little awkward, and takes more time than just waiting for the delay. I'm sure I'd get faster at it over time.
Thanks for the heads up on one other workaround though.
I'm starting to miss my oneplus 5t...
bsweetness said:
This does work, but it's not something I'm going to do. Positioning my hand to hit them both in succession is a little awkward, and takes more time than just waiting for the delay. I'm sure I'd get faster at it over time.
Thanks for the heads up on one other workaround though.
Click to expand...
Click to collapse
For once being left handed is helping me. Grabbing it with my left hand my thumb is already by the power button.
it feels same to me, maybe being old helps.........
Read through the Flash Kernel thread. There has been some good discussion about it including some technical info. Yes it's intentional, and Google prolly won't do anything about changing it. Maybe down the road a dev will bake in the removal of the delay into a custom Rom and or kernel.
Turning AOD on definetly unlocks and wake the screen instantly, although previously i had it disabled.
Cheers ?
Sent from my Google Pixel 2 XL using XDA Labs
I have never had screen flickering issues before. Is there a video on what it looks like?
Does the Essential Phone have the necessary hardware to support this? If so, has anyone ported this function from another phone to the Ph-1? Thanks.
awdrifter said:
Does the Essential Phone have the necessary hardware to support this? If so, has anyone ported this function from another phone to the Ph-1? Thanks.
Click to expand...
Click to collapse
Its a kernel feature and it kills the battery
jacksummers said:
Its a kernel feature and it kills the battery
Click to expand...
Click to collapse
Does that mean it's only possible with a custom Rom?
Sent from my SM-G955F using Tapatalk
awdrifter said:
Does that mean it's only possible with a custom Rom?
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
It's possible but the screen must stay on and cant be put to sleep.
This means it drains battery.
tech_head said:
It's possible but the screen must stay on and cant be put to sleep.
This means it drains battery.
Click to expand...
Click to collapse
How does other LCD screen phone do it then? The OnePlus 1 had it, and it also had a LCD screen. I don't think it was always on.
Sent from my SM-G955F using Tapatalk
awdrifter said:
How does other LCD screen phone do it then? The OnePlus 1 had it, and it also had a LCD screen. I don't think it was always on.
Click to expand...
Click to collapse
I think it's a combination of low power states enabled for the CPU & digitizer, and a kernel level wakelock. Essential's firmware probably doesn't have that included.
garywojdan81 said:
I think it's a combination of low power states enabled for the CPU & digitizer, and a kernel level wakelock. Essential's firmware probably doesn't have that included.
Click to expand...
Click to collapse
It's actually enabled by having the screen and its touch layer on a separate power rail to allow one to be powered on without sending power to another, this allows it to use very little power and work on some phones but use a considerable amount on others (like the PH-1)
Nick80835 said:
It's actually enabled by having the screen and its touch layer on a separate power rail to allow one to be powered on without sending power to another, this allows it to use very little power and work on some phones but use a considerable amount on others (like the PH-1)
Click to expand...
Click to collapse
Ok, thanks for the info. I'm guessing the PH-1 doesn't have separate power for the screen and touch layer, thus the high power consumption if we use tap to wake.
I guess a follow up question is does anyone make a battery case for the PH-1? I guess I would be ok with the power consumption if I can get a battery case with 5500mah, that should allow the phone to last a full day even with tap to wake.
Essential have "lift to check phone" menu, maybe for replace doble tap to wake menu ?
I guess if this menu is enabled will make more battery drain.
IMHO
Sent from my PH-1 using Tapatalk
This thread is full of total BS. AoD has worked onall customm ROMs I've used on l lcd since 2012.
Who is talking about AOD? That works fine if it is included in the source.. i missed that part..
innoth said:
Essential have "lift to check phone" menu, maybe for replace doble tap to wake menu ?
I guess if this menu is enabled will make more battery drain.
IMHO
Click to expand...
Click to collapse
This is actually the ONLY way double tap to wake works...
If you wake the phone into doze mode... With lift to wake... You can then double tap the screen to wake it up...
So I hypothesize that if you were to use one of the AoD hacks... If they even work on this device... You could probably have double tap to wake
scottspa74 said:
This thread is full of total BS. AoD has worked onall customm ROMs I've used on l lcd since 2012.
Click to expand...
Click to collapse
There's a way to do things and then there's a hacked together way to do things. You can make a lot of crap work, doesn't mean it works the best way.
I specifically asked @flar2 about this. Its totally possible if enabled in the kernel, but kills battery. Thats all.
scottspa74 said:
This thread is full of total BS. AoD has worked onall customm ROMs I've used on l lcd since 2012.
Click to expand...
Click to collapse
No kidding... I get sick of idiotic apologists making up reasons for no tap to wake without real proven facts. First they come up with BS like "it uses too much power" waah waah! Then they come up with BS aboout how the hardware doesn't support it.
I don't have a PH-1 screen assembly, but just because there is one ribbon cable connecting it to the phone, doesn't mean that the screen and digitizer use the same power rail. Plenty of phones use tap to wake without any appreciable battery drain.
gyrfalcon said:
No kidding... I get sick of idiotic apologists making up reasons for no tap to wake without real proven facts. First they come up with BS like "it uses too much power" waah waah! Then they come up with BS aboout how the hardware doesn't support it.
I don't have a PH-1 screen assembly, but just because there is one ribbon cable connecting it to the phone, doesn't mean that the screen and digitizer use the same power rail. Plenty of phones use tap to wake without any appreciable battery drain.
Click to expand...
Click to collapse
Flar is one of the greats. I used to be fullofhell. I proposed the very thing .. heres what he said
jacksummers said:
Flar is one of the greats. I used to be fullofhell. I proposed the very thing .. heres what he said
Click to expand...
Click to collapse
To quote a movie...
It's not an excuse not to have the feature available. I'm a big boy, I can decide how I want to drain my battery. Don't need anyone making choices for me.
gyrfalcon said:
To quote a movie...
It's not an excuse not to have the feature available. I'm a big boy, I can decide how I want to drain my battery. Don't need anyone making choices for me.
Click to expand...
Click to collapse
Haha nice quote, great film. Then i would say go for it, i would use uber toolchain to compile a kernel with the DT2W.
gyrfalcon said:
To quote a movie...
It's not an excuse not to have the feature available. I'm a big boy, I can decide how I want to drain my battery. Don't need anyone making choices for me.
Click to expand...
Click to collapse
Well then what's keeping you from doing it? Big boy?
gyrfalcon said:
No kidding... I get sick of idiotic apologists making up reasons for no tap to wake without real proven facts. First they come up with BS like "it uses too much power" waah waah! Then they come up with BS aboout how the hardware doesn't support it.
I don't have a PH-1 screen assembly, but just because there is one ribbon cable connecting it to the phone, doesn't mean that the screen and digitizer use the same power rail. Plenty of phones use tap to wake without any appreciable battery drain.
Click to expand...
Click to collapse
I don't think the amount of cables has anything to do with the power distribution for the screen. You want DT2W? Make it happen.
Edit: also nobody said it wasn't possible, this thread wasn't full of BS until people came in spouting nonsense about how someone else supposedly said it "doesn't support it" acting as if that's the reason it hasn't been done yet on this device.