Related
I've noticed this problem from the day I got my phone (10/10/13). I'll experience a full second or more of lag when trying to wake the phone by hitting the home button or the power button.
It's pretty bad, so much so that I sometimes think I may have missed the button and go for it again.
Is this common? I've searched online and I haven't found anything about the Note 3 but I see stuff about it happening on the previous Note.
One thing u can try that made speed things up slightly is to go into developers options and turn off or change the transition animation scale, Window animation scale and Duration animation scale. It won't brake anything and it just may help a little. The default setting for each is a 1 so I'd either change em all to a 0.5 or turn em to off. And hell, if u don't think it helps you can always change em back. Worth a shot at least.
Sent from my SM-N900V using Tapatalk
Ibkevin said:
One thing u can try that made speed things up slightly is to go into developers options and turn off or change the transition animation scale, Window animation scale and Duration animation scale. It won't brake anything and it just may help a little. The default setting for each is a 1 so I'd either change em all to a 0.5 or turn em to off. And hell, if u don't think it helps you can always change em back. Worth a shot at least.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Nice tip. In all my years of Android tweaking, I've never come across that one. I don't need fancy screen on/off animations. I prefer quicker response time. Thanks.
This phone is fast enough to where you should be able to do screen on animation with no lag. I'd try wiping cache before disabling anything
Sent from my SM-N900V using xda app-developers app
noticed too
sintricate said:
I've noticed this problem from the day I got my phone (10/10/13). I'll experience a full second or more of lag when trying to wake the phone by hitting the home button or the power button.
It's pretty bad, so much so that I sometimes think I may have missed the button and go for it again.
Is this common? I've searched online and I haven't found anything about the Note 3 but I see stuff about it happening on the previous Note.
Click to expand...
Click to collapse
I have noticed this too... bugs the hell out of me. i tried putting animations to .5 cause i think it makes the phone look like crap when set to 0, helped a little bit but it is still there.
I noticed this last night. I was missing the swipe to unlock because it was taking so long. Seems ok now, though.
I found a slightly faster response with the three animation options set to 0.
I think its a touchwiz thing my s4 did it stock and it went away with Hyperdrive rom but it came back when I was on cynanogen mod. I feel like my I wore out my power button lol it is a little loose.
Sent from my SCH-I545 using xda app-developers app
Its a Samsung thing with the processor. The Note 2 was the same way. The easiest way explained to me awhile back....once your screen goes off...and all stuff running finishes up...you essentially enter Deep Sleep. It's a battery saving feature...if you will.
Manually turn off your screen, then like..2 seconds later, turn it back on. Should be virtually instant. Now do the same thing but wait 2 minutes....lag.
It is 'kind of' annoying, but I'll deal with it for the sake of battery life.
Now that we have root, you can always try to adjust governors and kernel settings to help it, but until we're able to use other kernels, it's gonna pretty much always be there, the lag, that is.
Hope that helps explain a bit.
The only way around it on the Note 2 was to force a wake lock, basically it never enters deep sleep. You may be able to use an app to do it as well, such as: https://play.google.com/store/apps/details?id=eu.thedarken.wl
MikeyXDA was an advocate of the method and explained it really well on his MeanBean ROM for the Verizon Note 2. You just take a slight hit to battery, but at least there's no wake lag.
Here's the thread: http://forum.xda-developers.com/showthread.php?p=543135
Sent from my SCH-I605 using XDA Premium 4 mobile app
I have absolutely no wake lag on mine at all. I was expecting it like my Note 2 but I hit the button now and it's just on instantly.
Wake lag with sd card
sintricate said:
I've noticed this problem from the day I got my phone (10/10/13). I'll experience a full second or more of lag when trying to wake the phone by hitting the home button or the power button.
It's pretty bad, so much so that I sometimes think I may have missed the button and go for it again.
Is this common? I've searched online and I haven't found anything about the Note 3 but I see stuff about it happening on the previous Note.
Click to expand...
Click to collapse
I'm having a problem with wake lag bad sometimes - several seconds. Mine seems to be connected to the sd card. I have a 32 gb card I used in my note 2 with no problem, it's and sdhc i think. I cleaned it down to 8g of stuff on it and put it in. It kept causing note 3 to dis mount the card each time I turned it on; had a little message at the top left. Much of the time the card would stay dismounted. When I finished a call the screen would not come back on for a long time, couldn't end the call. Took the sd card out, problem resolved. Backed up the sd card, put it in the N3 and formatted. Got better results although still doing it some. I'm wondering if I'm going to have to get a new sd card or trade in for a new note 3.
Any thoughts. I would check the sd card if you still see long lags.
Try to freeze/remove S Voice if you rooted because S Voice is mapped to double tapping the home button. This helped me out a lot on the Note 2 and I removed it already on the Note 3 without comparing lag difference already
Hi guys,
I just purchased a Galaxy Note 3 a week ago. However, I'm noticing that this phone has a major problem (at least, I consider it a problem). Turning the screen on and off has a bit of a delay.
To show what I mean I made this video in which I use a Desire HD to compare it with.
You can clearly see that the Desire HD turns on and off immediately, however.. the fancy Note 3 has to wake up, make a pot of coffee, read the morning news and then decides to switch on the screen.
Is this just my phone? Do more people experience this? Why does my phone do this?
I don't have a second Note 3 and I'm waiting for somebody to test it with. So I'd like to know how other Note 3 owners experience this.
There are many other things about this phone that really disappoint me, but this is one of the things that annoy me the most.
(p.s. I already tried a factory reset, didn't chance a thing...)
Thanks you for any replies/help.
supervinnie40 said:
Hi guys,
I just purchased a Galaxy Note 3 a week ago. However, I'm noticing that this phone has a major problem (at least, I consider it a problem). Turning the screen on and off has a bit of a delay.
To show what I mean I made this video in which I use a Desire HD to compare it with.
You can clearly see that the Desire HD turns on and off immediately, however.. the fancy Note 3 has to wake up, make a pot of coffee, read the morning news and then decides to switch on the screen.
Is this just my phone? Do more people experience this? Why does my phone do this?
I don't have a second Note 3 and I'm waiting for somebody to test it with. So I'd like to know how other Note 3 owners experience this.
There are many other things about this phone that really disappoint me, but this is one of the things that annoy me the most.
(p.s. I already tried a factory reset, didn't chance a thing...)
Thanks you for any replies/help.
Click to expand...
Click to collapse
I think that something is wrong with your phone, my wakes up almost emmediately
supervinnie40 said:
Hi guys,
I just purchased a Galaxy Note 3 a week ago. However, I'm noticing that this phone has a major problem (at least, I consider it a problem). Turning the screen on and off has a bit of a delay.
To show what I mean I made this video in which I use a Desire HD to compare it with.
You can clearly see that the Desire HD turns on and off immediately, however.. the fancy Note 3 has to wake up, make a pot of coffee, read the morning news and then decides to switch on the screen.
Is this just my phone? Do more people experience this? Why does my phone do this?
I don't have a second Note 3 and I'm waiting for somebody to test it with. So I'd like to know how other Note 3 owners experience this.
There are many other things about this phone that really disappoint me, but this is one of the things that annoy me the most.
(p.s. I already tried a factory reset, didn't chance a thing...)
Thanks you for any replies/help.
Click to expand...
Click to collapse
Something up there mate my phone is on soon as i press the button
my guess is ...
that its "some form of lag" caused by an app ??
have you got Svoice enabled ? /
or otherwise its some "app setting "( eg a launcher/camera )
that power button functions , is also assigned to and causes delay ??
Further have you check Svoice settings ?
it does sometimes cause lag as it waits for second press on "home button "
i disabled it completely /otherwise uncheck in S voice settings.
have you tried to wake phone with home button press,not power button.?( any lag ? )
i use Sview cover to open cover and note 3 wakes up straight away !(use no power button at all )
but if i press power button ,wakes up ....immediately !
same with me pressing home button,wakes up ..immediately.!
(No lag at all .)
(but above then,is my experience in tracking " cuplits/apps " responsible for various lags on my phone
The result is my phone is very, very smooth ,no lags or hiccups....
I have the N9005 ,stock, not rooted .
good luck.
Thanks for the replies guys.
I don't have any launcher apps running. I like to keep things smooth and optimized, so I turn off everything I don't need. No Air Gesture, No Svoice etc.
I've been playing with this the last week, and haven't really been able to find anything.
However, I just wanted to delete some stuff and reset some settings and removed my SD card to be safe. Since I removed the card, it seems the screen reacts a bit faster....
But does that make any sense? Could there be anything that could cause this lag/delay that has to do with the SD card?
My current card is a 16gb class 2. But I can't find any info on why the phone would slow down when a slow SD card is used.... Just doesn't make much sense.
In the meantime I continue testing and trying. Others have said that there might be something wrong with my phone, but when I compare stuff with other Note 3 tests, then it all seems ok. Installing an app takes the same time, opening a heavy app too, starting up is just as fast and even after a full factory reset everything seems to be fine.
Mine has a bit of a delay too...I was wondering if it was only me. With mine it's pretty erratic though - sometimes it takes a full second or so to activate the screen, while other times it comes on almost instantly.
I did notice on many occasions using the home button to wake is quicker, plus it's generally easier to get to one handed.
p.s. do you have the Verizon variant?
Good to read that somebody else noticed this to.
In the mean time I have been testing some more. After disabling almost anything that could have to do with either cpu usage or lockscreen usage, removing the SD card, removing the sim card, deleting many apps and using a very low res image, the phone becomes almost as quick as the Desire HD.
There is still a difference, the Note 3 is still a tiny little bit slower, but it has been improved.
However, if I need to do all this radical stuff to make a 2.3 ghz powerhouse perform the same as a 4 year old 1 ghz calculator.... then this phone is just not worth the money I spent on it.
Very, very dissapointed.
After my testing I applied all my previous settings, apps and such to a phone from my friend. Just like you said (siciliano) there is a noticable delay. An erratic delay, but still noticable. Sometimes it's really quick, other times it's really slow.
My Desire HD has never shown any delay... not even when I'm downloading 5 apps at the same time (which makes it quite slow).
This phone will go on for sale tomorrow. I'm not gonna spent 600 euro on a toy that can't perform the way it should.
p.s. No, it's not a Verizon phone. I bought the phone, without phone-plan or anything. Just the phone itself.
Hi,
I think it's very safe to assume that if you think there's a problem then there likely is. Sometimes you have to turn the question round or switch focus... scratch your head all day about 99 maybes yet you have 1 factor that swings it.
Certainly when it comes to testing leave things out like memory cards or SIMs. Sounds like you have and it's not happy. All might not be lost though. Perhaps the stock firmware didn't load well. Have you tried updating OTA or via Kies or Odin? And was the device bought from a regular vendor?
Jonty.
Sent from my SM-N9005 using XDA Premium 4 mobile app
I just checked mine - same delay. So I restarted it. Now no delay.
@jonty, I got the phone from a well known Dutch re-seller (phonehouse). Unfortunately my results and/or problems seem to be repeatable, which makes me believe that it's not just my phone.
I h aven't used any other ROMs, but I did give it a factory reset (twice in 2 weeks...) and I have swiped the cache. Both did not make a difference.
Even better, right after the reset, the delay is bigger then when I optimize the settings (which means turning pretty much anything and everything off... stripping down the phone via settings).
@Bulbous, how did it take you to get the delay back again. I've tried restarting a few times, but after +/- 5 minutes the delay was the same again.
I just don't understand why a powerhouse like this phone has so much trouble with such a simple thing....
It's like asking Einstein to tell me 1+1=? and then he has to take his calculator out....
If you experience lag like this something is wrong. Note 3 should have no lag at all. I have about 150 user apps adding to the stock apps and have never experienced any lag whatsoever.
If you do, you have fu..ed up your phone somehow..
Sent from my SM-N9005 using Tapatalk
slight delay like 0.5 sec to 1 sec is ok cos it is normal as the phone required to enter deep sleep. (google to understand it)
any more than that might be faulty software or hardware.
if i were to encounter such problem, i will first remove the sdcard and reboot..if not fixed, then format.. without sdcard inserted, reboot and try again.
if not fixed, then i would send to SC ask them check.
the reason i remove sdcard because the phone might still scanning in the background.
Hi,
Although unfortunate it might just be that the device is defective. Although it's new it can still happen.
But before you go the repair/replace route you should at least consider installing any OS updates if there are any and perform a complete wipe. Then see how it performs before installing any memory cards or other software. Perhaps also install a system info app (afterwards) and make sure the chip, cores and other spec are what they should be as fakes do exist.
Jonty.
Sent from my SM-N9005 using XDA Premium 4 mobile app
try this method maybe will help u http://forums.androidcentral.com/sa...-note-3-lags-sometimes-slow-here-how-fix.html
Something is wrong it shouldn't be that slow, comment above is useless as it's not an animation.
Flash the latest stock firmware - if that doesn't help I'm clueless to what could cause this.
Its the sd card...I used a class 2 and I had lags..changed to a new class 10 and everything was instantaneous
Teleported from my SM-N9005 from the Enterprise
dcracks said:
Its the sd card...I used a class 2 and I had lags..changed to a new class 10 and everything was instantaneous
Teleported from my SM-N9005 from the Enterprise
Click to expand...
Click to collapse
Can anyone confirm this? This could very well be the problem because I know for a fact my sd card is very old.
I'm gonna buy a new 64GB sd card soon anyway, so I'll make sure it's fast.
I had some delay when turning the screen on/off, but im pretty sure that something was corrected in one of the multiple firmware updates that i have installed because i don't have it any more.
tWoBrO said:
I had some delay when turning the screen on/off, but im pretty sure that something was corrected in one of the multiple firmware updates that i have installed because i don't have it any more.
Click to expand...
Click to collapse
Just out of curiosity, are you rooted? How did you go about updating?
Thanks!
My phone is not rooted, I'm using stock room. I was talking about official Samsung firmware updates. Running version MJ7.
It took my a while, but thanks to Wugfresh I was finally able to instal 5.1 on my N6. Curious to know what the general consensus is. I've only had it up and running for 6 hours, but has anyone noticed improvement in battery life or memory management?
Thanks.
When I get it.....
For now still waiting.
Think I will like the change in notifications where I can select WiFi hotspot with going into settings.
The battery life has always been great on 5.01
Read all 4 cores are active but I doubt I will notice.
AstroDigital said:
When I get it.....
For now still waiting.
Think I will like the change in notifications where I can select WiFi hotspot with going into settings.
The battery life has always been great on 5.01
Read all 4 cores are active but I doubt I will notice.
Click to expand...
Click to collapse
Franco's kernel has given my battery some extra life, I hope this update does the same.
I have yet to get the two bugs that were really getting on my nerves previously in 5.0 and 5.0.1
1- Random restarts. They could happen at any time, but it seemed like they would happen when I was trying to text. I'd try to keep closing my text messenger application (happened with both Google Messenger and Hangouts), but it didn't always help. I'd send a text message, put my phone down and then a few seconds later, notice the Google logo because it was restarting.
2- Sometimes when the screen powers up, all I see on my lock screen is a blank black background, the on-screen back button and the usual clock and what not at the top of the phone. Otherwise, the screen itself is black and I'm basically locked out of my phone until I restarted it. If I was lucky and I was using my Bluetooth headset, if I received a phone call, that would sometimes get the phone to snap out of it and allow me to answer the phone call and then when the call was done I'd get the normal lock screen again.
So far so good with 5.1 *knocks on wood*
I just flash it this morning and I feel like im still on 5.0.1. I only use 1 wifi connection and 1 bluetooth connection, so a drop down menu doesn't really effect my daily usage since I don't switch them. Whatever they did behind the hood to improve performance/battery will be nice, but haven't had it installed long enough yet to notice anything different really.
I would also like to know how the 4 cores being force enabled effects the experience before I make the jump.
5.1 is what Lollipop should have been from launch. It's equivalent to Windows 7 replacing Vista. It's that much better.
Sideloaded with adb on my stock att N6. Seems real quick so far. Don't notice any additional drain on battery.
So far it seems about the same as before to me. However, I am on Sprint and the new radio that prevents duplicate texts is awesome so that part of it makes it seem like a new device.
I play Hearthstone, Kingdom Rush and Clash of Clans on My nexus 6 and they all run fine so far.
I did un-encrypt like before. I cannot comment on battery life yet since it hasn't even been 24 hours for me since I updated.
So far so good. Battery life has certainly improved, it was pretty abysmal for me before. I only experienced one bug that I know of on 5.0.1 where occasionally my status bar and nav bar would disappear and the phone was in a partially locked state. Trying to slide down the notification drawer would show the lockscreen. Hopefully that's fixed.
is double tap to wake.. enable in 5.1??
I'm not on a N6 yet, but my GNex is on 5.1, and to compare (because I've only got 1Gb of RAM here, it's a good test because the margins are so small compared to having 3Gb) the 5.1 update is by far the most stable yet for my device. 5.0 was baaad, but consider how many commits corrected memory leaks and you can tell this is the one. I'm looking forward to getting my N6 with 5.1 on it.
Big dialer bug in 5.1. Anyone else getting it?
My screen immediately locks and turns off in the dialer when initiating or answering phone calls. I have no access to onscreen controls until the call is terminated. I cannot hangup, select speakerphone, go to my home screen, etc., until the call ends and Android gives me my screen back.
I'm stock rooted on a 64gb N6 on Verizon. In order to maintain my data and settings I used fastboot to individually flash the new bootloader, radio, system, and boot images.
The same thing happened to an acquaintance of mine who is not rooted and did a fresh install.
Bug reported to Google, ID 160006, if you're interested.
Sent from my Nexus 6 using XDA Free mobile app
I am noticing a huge performance improvement from 5.0.1 already. Battery life is also better. I am not having the dialer issue like some, but have seen 3 instances of people saying the same thing.
Was on stock, now on Vanillipop 1.6 with Franco Kernel r20.
Much smoother and the battery seems improved. Still testing out.
Fly135s said:
Big dialer bug in 5.1. Anyone else getting it?
My screen immediately locks and turns off in the dialer when initiating or answering phone calls. I have no access to onscreen controls until the call is terminated. I cannot hangup, select speakerphone, go to my home screen, etc., until the call ends and Android gives me my screen back.
I'm stock rooted on a 64gb N6 on Verizon. In order to maintain my data and settings I used fastboot to individually flash the new bootloader, radio, system, and boot images.
The same thing happened to an acquaintance of mine who is not rooted and did a fresh install.
Bug reported to Google, ID 160006, if you're interested.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
got a tempered glass protector on it?
Fly135s said:
Big dialer bug in 5.1. Anyone else getting it?
My screen immediately locks and turns off in the dialer when initiating or answering phone calls. I have no access to onscreen controls until the call is terminated. I cannot hangup, select speakerphone, go to my home screen, etc., until the call ends and Android gives me my screen back.
I'm stock rooted on a 64gb N6 on Verizon. In order to maintain my data and settings I used fastboot to individually flash the new bootloader, radio, system, and boot images.
The same thing happened to an acquaintance of mine who is not rooted and did a fresh install.
Bug reported to Google, ID 160006, if you're interested.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Do you use a screen protector that covers the sensor? I know there is a thread somewhere around here with a lot of people that have that issue and it's because of their screen protector in 5.1 for some reason.
jakebites said:
I would also like to know how the 4 cores being force enabled effects the experience before I make the jump.
Click to expand...
Click to collapse
Greatly, its butter all the time.
I haven't noticed a whole lot yet, some games seem to be playing a lot better, the graphical glitch I was seeing on xcom seems to have disappeared so its actually playable now
I've been experiencing an increase in fluidness (is that a word) throughout the UI as a whole, the phone moves from task to task without any stutter and the animations seem to have a bit more polish to them. Checking on the battery now, but I was never a power user to begin with. Overall it may not look like much but you can tell there are some big time enhancements coming from 5.0.1
My apologies if this is a repeat post.
It has been mentioned before that the double-tap-to-wake does not working with anything but the stock launcher. Actually technically the *wake* should work with any launcher. I just installed Apex (my regular launcher), and it is still working just fine. What does not work is the *lock*. Apex has its own double-tap gesture definition, and lock isn't one of the options. So to get around that, you can go to the Play Store and download, install and activate "Screen Off and Lock" . One option on the Apex double-tap setting is to launch any other app. You can now configure it to launch this app. Once you do that, when you double tap while in Apex, it will lock the screen. When you double tap again, it will unlock ( I do not think that has anything to do with Apex anyway ) .
Apex is my favorite launcher and I have been looking for a way to get back to it without losing the double tap. Now I can change themes, make my drawer look better and set up many other gestures. Hopefully this trick can work in any other launcher you want to use. And at the minimum , the double tap to wake should work regardless.
Double tap to wake works for me with Google Now launcher and Nova (free version). Double tap to sleep (lock) doesn't work with either. Works fine both ways with the stock Idol launcher. Looks like you may have discovered a work around.
stl1859 said:
My apologies if this is a repeat post.
It has been mentioned before that the double-tap-to-wake does not working with anything but the stock launcher. Actually technically the *wake* should work with any launcher. I just installed Apex (my regular launcher), and it is still working just fine. What does not work is the *lock*. Apex has its own double-tap gesture definition, and lock isn't one of the options. So to get around that, you can go to the Play Store and download, install and activate "Screen Off and Lock" . One option on the Apex double-tap setting is to launch any other app. You can now configure it to launch this app. Once you do that, when you double tap while in Apex, it will lock the screen. When you double tap again, it will unlock ( I do not think that has anything to do with Apex anyway ) .
Apex is my favorite launcher and I have been looking for a way to get back to it without losing the double tap. Now I can change themes, make my drawer look better and set up many other gestures. Hopefully this trick can work in any other launcher you want to use. And at the minimum , the double tap to wake should work regardless.
Click to expand...
Click to collapse
Nova Launcher has an identical gesture/setup. [ which I'm using in same way with the "Screen Off" app since the phone auto locks when the screen goes blank. ]
I have experienced the inconsistency with dt2w. I kept deactivating/activating it and it's been working adequately (~60% of the time, still sucky but much better than before). Like others have said, it works much better if the phone is sitting on a desk as opposed to attempting it while in your hand. I really hope the reliability of dt2w gets improved in the next OTA update.
Using Nova and a double tap gesture that activates a screen lock app works perfectly for me.
JJ2525 said:
I have experienced the inconsistency with dt2w. I kept deactivating/activating it and it's been working adequately (~60% of the time, still sucky but much better than before). Like others have said, it works much better if the phone is sitting on a desk as opposed to attempting it while in your hand. I really hope the reliability of dt2w gets improved in the next OTA update.
Using Nova and a double tap gesture that activates a screen lock app works perfectly for me.
Click to expand...
Click to collapse
Same here, NOVA launcher premium
My dt2w works flawlessly to turn screen off. It only works 50% of the time to get it on.
maddog497 said:
My dt2w works flawlessly to turn screen off. It only works 50% of the time to get it on.
Click to expand...
Click to collapse
Exactly the same situation here.
Borghi said:
Exactly the same situation here.
Click to expand...
Click to collapse
I'm spoiled with the G3 and the Zenfone 2. They both work flawlessly.
Hopefully this gets fixed in an update.
Sent from my LG-D852 using Tapatalk
Thank you very much dude, I'm hoping to root ASAP still haven't found a reliable way to. I wish this device had a bit more ram but pretty good so far. I hate not being rooted just because I can erase anything on the external SD and hopefully with a custom Tom the screen Issues with the phone not waking gets fixed
You don't have to be rooted to delete files on the external drive. There's a thread here that covers that. I'll post the link when I'm on the PC.
Sent from my Alcatel OneTouch Idol 3 using Tapatalk
Shodan5150 said:
You don't have to be rooted to delete files on the external drive. There's a thread here that covers that. I'll post the link when I'm on the PC.
Sent from my Alcatel OneTouch Idol 3 using Tapatalk
Click to expand...
Click to collapse
Sorry it took so long fopr me to get back here to post the link. I had PC issues and had to install Windows and then the hardware drivers for the AMD card gave me a fight. But you prolly already found the thread but the thread is below.
http://forum.xda-developers.com/idol-3/help/install-to-sd-card-root-access-t3119374
New discovery
Some of you may have already discovered this - but this is certainly new for me. What I am noticing about the double-tap-to-wake - is that it always works - BUT - what is happening is that often it is slow - and I mean really really slow sometimes. Most of us would perceive that as not working - and try it again. And double-tap, on top of double-tap just makes matters worse. What I did was - tried double-tapping once - and when the screen did not come back on, just let it be for about 10+ ( probably more than that at times ) seconds - and it eventually came back on. Even under normal circumstances, the screen wakeup is slow . It looks like sometimes it just takes forever, creating the impression that it is not working. I am not trying to suggest that we can say that this behavior qualifies as 'working' - but at least we know what exactly the problem is.
I hope Alcatel pushes a fix for this. Till that time - I will have to continue to rely on single-tap to wake ( aka the power button ) if double tap to wake does not work.
stl1859 said:
Some of you may have already discovered this - but this is certainly new for me. What I am noticing about the double-tap-to-wake - is that it always works - BUT - what is happening is that often it is slow - and I mean really really slow sometimes. Most of us would perceive that as not working - and try it again. And double-tap, on top of double-tap just makes matters worse. What I did was - tried double-tapping once - and when the screen did not come back on, just let it be for about 10+ ( probably more than that at times ) seconds - and it eventually came back on. Even under normal circumstances, the screen wakeup is slow . It looks like sometimes it just takes forever, creating the impression that it is not working. I am not trying to suggest that we can say that this behavior qualifies as 'working' - but at least we know what exactly the problem is.
I hope Alcatel pushes a fix for this. Till that time - I will have to continue to rely on single-tap to wake ( aka the power button ) if double tap to wake does not work.
Click to expand...
Click to collapse
I have tried waiting for the screen without it coming on. Putting it on the desk and trying it and leaving it there, with no response. After a reset or disabling then enabling the function would work for a brief while. After that nothing seemed to help. If I used the power button to activate the screen and then try the DTTW, it would work but as soon as the phone went idol, so did the DTTW. As much as I liked the phone for the most part, I was not prepared to go past my return date without even one update coming from Alcatel.
maddog497 said:
I have tried waiting for the screen without it coming on. Putting it on the desk and trying it and leaving it there, with no response. After a reset or disabling then enabling the function would work for a brief while. After that nothing seemed to help. If I used the power button to activate the screen and then try the DTTW, it would work but as soon as the phone went idol, so did the DTTW. As much as I liked the phone for the most part, I was not prepared to go past my return date without even one update coming from Alcatel.
Click to expand...
Click to collapse
Since the time I arrived at this theory, I have tested it again and again - and I can confirm that it is always doing it. You just have to be really really patient to see this in action. Forget what I said about 10 seconds ; sometimes you have to wait for more than a minute. It is weird - you double tap - then just stare at the phone for ages and suddenly out of nowhere the screen lights up.
If D2W is important for you , then my discovery does nothing for you - It is still broken. So you did the right thing in returning it. As far as updates go, again if that is important for you, then you did the right thing. Honestly I do not expect many ( if at all ) updates from TCL. From what I understand, they do not have the kind of software development infrastructure that Asus does . And that is evident from the extent of skinning that Asus did on top of Lollipop whereas the Idol3 was mostly a stock experience. IMHO - right now - more than updates from TCL, we need root , so that developers can do their own thing with the phone.
I have since installed a proximity sensor based wave-to-unlock app. Not only does it work very well, it also allows me to lock the screen back, from the lock-screen itself, something that is missing in the default D2W setup. The only downside is the additional power consumption by the proximity sensor. Since it is supposed to use only 3 mA , I am hoping it is not going to be too bad, but I will watch out for it. If the battery performance does not degrade too much, then I think I can kiss D2W goodbye.
I sent an email to Altatel Tech Support about a week ago and asked them if they are aware of the DTTW issues and working on a fix. I received a reply stating that they are aware and are working on an update. My guess is that they will try to combine multiple fixes into a single update. It may take a little longer and it is too bad that Alcatel is not better at communicating with its customers. It would make no sense for Alcatel to ignore all of the customer complaints here, on Amazon, and in various reviews and do nothing. They are spending cash marketing this phone and they must be smart enough to know that their sales will tank if they ignore the issues.
Hey guys, just thought I'd let you know of a solution that appears to fix the double tap to wake issue everyone is having. Like most of you, I've been annoyed that this only works like 50% of the time. I've noticed in the G4 forums of people having issues with their double tap to wake not working as well also (only 80% of the time, still much better than idol 3). One of their fixes is to download SGS Screen Booster from the Play Store. Using the Super Optimized preset, I can say that double tap to wake works 10 out of 10 times in my testing.
https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com&hl=en
japhule said:
Hey guys, just thought I'd let you know of a solution that appears to fix the double tap to wake issue everyone is having. Like most of you, I've been annoyed that this only works like 50% of the time. I've noticed in the G4 forums of people having issues with their double tap to wake not working as well also (only 80% of the time, still much better than idol 3). One of their fixes is to download SGS Screen Booster from the Play Store. Using the Super Optimized preset, I can say that double tap to wake works 10 out of 10 times in my testing.
https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com&hl=en
Click to expand...
Click to collapse
I tried this app and it seems to improve lag time when you open an app too! Great find!
OTA
An official OTA update has just been announced to fix the DTTW
Borghi said:
I tried this app and it seems to improve lag time when you open an app too! Great find!
Click to expand...
Click to collapse
Hi everyone,
Has anyone noticed a second screen lag when swiping it around while the main screen is off? I only have the quick toggles and music player on my second screen when the main screen is off. But regardless of any direction you swipe it, there is a VERY considerable lag as it navigates to the next item. For those who previously had the LG v10 and are currently using the V20, I'm pretty sure you've noticed that the swipe on the V10 was very swift. I'm asking out of curiosity if anyone else has had this issue. It's possible that due to first batches of V20s available to the public, these units are suffering from it? Idk, I just want to hear your thoughts if possible. Thank you!
I'm experiencing the same thing.
Not mine, I have also the music player active and actually is pretty snappy.
no problems here. I'm not saying there's never been a lag, but generally not a lag on my Tmo version.
Sent from my LG-H918 using Tapatalk
When Pandora is playing the 2nd screen is noticeably laggy for sure. It doesn't impact how quick I can scroll around but it doesn't look great. Doesn't really bother me since the 2nd screen is too locked down to be that useful. I just leave it on Pandora controls or date/time
Yeah I'm seeing it too. Most of the time I need to double swipe it then it would jitter to the left when playing music. When not playing anything, it still has basic lag when screen is off.
Im noticing the same lag on mine as well when the main screen is off. Maybe something to do with battery saving.
Try this
Settings/Developer Options/ Tick on "Force GPU Rendering" this should make your beast smoother/snappier!
If root available try L Speed/Entropy/fstrim apps found on Play Store! LG V20 & LG G5 are both snappy beasts and most anticipated of 2016! They are well optimised with Snapdragon 820 and is better than Samsung.
I had this lag until I did a factory reset 3 days ago. I thought maybe it was the LG Home + App update from the lg app update so I didn't update until yesterday. The second screen lag is still gone. Maybe it was during initial setup that something borks. I don't know.
Sent from my LG-H918 using Tapatalk
beast330001 said:
I had this lag until I did a factory reset 3 days ago. I thought maybe it was the LG Home + App update from the lg app update so I didn't update until yesterday. The second screen lag is still gone. Maybe it was during initial setup that something borks. I don't know.
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
Hey beast,
So you recommend a factory reset? And you SURE it should be a bit faster or the lag would leave atleast?
saqc2010 said:
Hey beast,
So you recommend a factory reset? And you SURE it should be a bit faster or the lag would leave atleast?
Click to expand...
Click to collapse
I had to do a rest because of work and the little lag I had is gone.
Sent from my LG-H918 using Tapatalk
Pick_A_Name said:
I had to do a rest because of work and the little lag I had is gone.
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
Thanks. So how soon did you notice the lag and how quickly did you do the reset. Other than the screen lag being gone, did you notice any other changes or flaws?
saqc2010 said:
Thanks. So how soon did you notice the lag and how quickly did you do the reset. Other than the screen lag being gone, did you notice any other changes or flaws?
Click to expand...
Click to collapse
Honestly I didn't notice the lag until this thread pointed it out. Probably because I've had Samsung devices for so long that lag is just part of life. Since factory resetting it, I've noticed it just runs better in general and not just the second screen lag.
Sent from my LG-H918 using Tapatalk
saqc2010 said:
Hey beast,
So you recommend a factory reset? And you SURE it should be a bit faster or the lag would leave atleast?
Click to expand...
Click to collapse
The second screen lag hasn't returned for me after the factory reset. It swipes left or right very quickly.
I do get a random lag from several hours/days uptime on the regular screen though. A restart fixes that lag for me.
Sent from my LG-H918 using Tapatalk
My screen was lagging so I reset all the defaults that go with the second screen and it now runs smoothly so long as my battery percentage is above 25%.
Almost 3 weeks and I've experienced no lag at all on second screen, always fast and fluid however it's been set up.
@Olivia1234
I'm curious why you think battery % would make any difference. Have you actually confirmed it does?
And welcome to XDA.
Same here. I am having lag on stock and now running mega rom on my 918. I have to swipe a couple of times and then it will skip the toggles I want ? maybe it's meant to be laggy so toggles aren't pressed by accident? Or so it's not swiping back and forth in your pocket??...either way it's very annoying
Nah mate, you not read my post above yours?
It should behave the same as main screen, be dumb to purposely make it behave like yours is.
Only time I have lag so to speak is when the phone has been sleeping for awhile in my pocket. When I take it out and wait for the 2nd screen to turn on and I try swiping sometimes it'll take a 2nd swipe or so. Almost seems like doze or deep sleep and it's not kicking it up fast enough to respond in time. So far has happened to stock, WETA and MegaRom.
Very annoying how long it takes for the phone to wake up when it's been in pocket. It won't even register the power button press to turn it on or the double tap to wake until the 2nd screen has turned back on
KUSOsan said:
Only time I have lag so to speak is when the phone has been sleeping for awhile in my pocket. When I take it out and wait for the 2nd screen to turn on and I try swiping sometimes it'll take a 2nd swipe or so. Almost seems like doze or deep sleep and it's not kicking it up fast enough to respond in time. So far has happened to stock, WETA and MegaRom.
Very annoying how long it takes for the phone to wake up when it's been in pocket. It won't even register the power button press to turn it on or the double tap to wake until the 2nd screen has turned back on
Click to expand...
Click to collapse
I've experienced that exact same thing. Sometimes I try to unlock it to fast and it just locks again no big deal for me though. I just ran across an issue running MegaRom.
Not sure if it has anything to do with the room though anyway the quick tools on the second screen are gone. If you scroll from the signature to the quick tools menu it's just black if you tap where the icons should be they work it's just like they are invisible or black I'm thinking it might have something to do with Nova launcher but I'm not sure I've played with the settings in Nova for about a day and it hasn't changed.