Related
Hi guys, just bought S4 I9500 5 days ago and yesterday i just noticed 1-2 second delay / lag when waking up sceen with power / home button
I know this has ben issue since S1 because i have Galaxy Gio and Galaxy Ace. Both have this issue after updating in GB. no wake up lag in Froyo. and i know this also happen in lot of Samsung Phone (S2, S3, Epic, Note 1,2). But the difference is those phone already do that from the start, but in my first 3 day i think don't have the issue (or i don't know, maybe i just too amazed by Full HD 441ppi screen and not noticed it until yesterday)
what i want to ask is that do u have this issue on ur S4 too?
because when i googled "Galaxy S4 wake up lag" the result is direct me to S2,S3 forum /article, even Epic 4G. but nothing about S4. I just afraid that this problem is specific to my device / i have a fault device
I already tried:
-. turning off all S-Voice setting and even disabled the S- voice
-. remove SD Card (because some people on S2 thread say that the device need time to mount SD card everytime screen on)
-. wipe dalvik from recovery
none of them works
i know the problem is caused by SOC that go to deep sleep to save battery because:
-. if i turn off and instantly turn on again, the lag didn't happen (because the processor still wake. ussualy take 3 second to go to deep sleep)
-. playing music / downloading someting /do anything that run in background. the lag didn't happen too (because processor awake to do all the task)
-. use app like wakelock and softlocker that make processor always run even screen is off. but this drain battery very fast because the processor is forced to awkae 24/7
please tell me do ur S4 have this issue? because 2 point below make me afraid
1. i feel i didn't have the problem for the first 3 days (but it can be that i just did not notice it yet)
2. i find bunch google result about this problem on another Samsung device, but none mention S4
thx b4
no one have this problem?
riderzecter said:
no one have this problem?
Click to expand...
Click to collapse
As you mentioned starting Android GB, the deep sleep was introduced, hence the lag when waking up the device, this was put there to save battery.
riderzecter said:
no one have this problem?
Click to expand...
Click to collapse
Have you tried opening S-Voice, hitting the menu button and turning off the 'activate S Voice with double tap of home button' option?
riderzecter said:
Hi guys, just bought S4 I9500 5 days ago and yesterday i just noticed 1-2 second delay / lag when waking up sceen with power / home button
I know this has ben issue since S1 because i have Galaxy Gio and Galaxy Ace. Both have this issue after updating in GB. no wake up lag in Froyo. and i know this also happen in lot of Samsung Phone (S2, S3, Epic, Note 1,2). But the difference is those phone already do that from the start, but in my first 3 day i think don't have the issue (or i don't know, maybe i just too amazed by Full HD 441ppi screen and not noticed it until yesterday)
what i want to ask is that do u have this issue on ur S4 too?
because when i googled "Galaxy S4 wake up lag" the result is direct me to S2,S3 forum /article, even Epic 4G. but nothing about S4. I just afraid that this problem is specific to my device / i have a fault device
I already tried:
-. turning off all S-Voice setting and even disabled the S- voice
-. remove SD Card (because some people on S2 thread say that the device need time to mount SD card everytime screen on)
-. wipe dalvik from recovery
none of them works
i know the problem is caused by SOC that go to deep sleep to save battery because:
-. if i turn off and instantly turn on again, the lag didn't happen (because the processor still wake. ussualy take 3 second to go to deep sleep)
-. playing music / downloading someting /do anything that run in background. the lag didn't happen too (because processor awake to do all the task)
-. use app like wakelock and softlocker that make processor always run even screen is off. but this drain battery very fast because the processor is forced to awkae 24/7
please tell me do ur S4 have this issue? because 2 point below make me afraid
1. i feel i didn't have the problem for the first 3 days (but it can be that i just did not notice it yet)
2. i find bunch google result about this problem on another Samsung device, but none mention S4
thx b4
Click to expand...
Click to collapse
AFAIK, that's just an issue with the wakeup time of the exynos processor. I had this exact issue on my s3 ( with the exynos processor) and it bugged the life outta me. Since buying the snapdragon 600 version of the s4 the lag is nonexistent.
So it's not exactly a problem. But is certainly annoying.
Sent from my GT-I9505 using Tapatalk 2
leoni1980 said:
Have you tried opening S-Voice, hitting the menu button and turning off the 'activate S Voice with double tap of home button' option?
Click to expand...
Click to collapse
yes. this only fix home button lag
pardoned said:
AFAIK, that's just an issue with the wakeup time of the exynos processor. I had this exact issue on my s3 ( with the exynos processor) and it bugged the life outta me. Since buying the snapdragon 600 version of the s4 the lag is nonexistent.
So it's not exactly a problem. But is certainly annoying.
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
yes, i heard about that too. from the start i also want to buy i9505 but my country only get i9500
what surprise me is that few days ago i have a family meeting and when i played with my cousin's S3 (exynos, stock 4.1.2, no root) there is no wake up delay. the screen wake up instantly. even my finger is still on power button when the screen wake up.
i know a lot of people have this issue in 4.0.4 S3. so this means that the wke up delay can be fixed by firmware update? (like 4.0.4 to 4.1.2 in S3). i dont know about my cousin's S3 pre-4.1.2 because she just bought it recently this year and already have 4.1.2 out of the box
anyway thx for the replies
galaxy s4 2 second delay wake up
i have also thid problem and its killing me plz help me:crying:
I have a version of the i9505 Android 4.2 and the problem did not occur, but after the upgrade to 4.3 the problem occurs: (
Also looking for solutions ...
Hi,
Anyone been keeping an eye on hotplugging on the n9005 ?
Mine is still unrooted, so I'm talking 100% vanilla Samsung configuration...
I use Android Tuner's online core notifications to keep an eye on this, there are other apps that can to this as well.
At some point, after a few hours of uptime, sometimes only after quite a many (20h+), I just notice that it will never drop below 2 or 4, never had it lock on 3 minimum, so can't comment on that scenario.
Once this happens, it's impossible to get back to single core even on very low load.
Also when leaving the device doing nothing, freq. drops to 300MHz and still 4 cores remain online.
There is obviously an impact on battery drain as well.
Only way to get back to normal is to reboot...
JP.
I've noticed the opposite issue, two cores just going offline forever until I reboot the device.
So that would point to obvious hotplugging issues, except if you ran into thermal throttling, maybe.
Were you running some heavy stuff when this happened ?
JP.
i tested it out of curiosity using the widget in system monitor app.
i have exactly the same issue as SentinelBorg above. the two cores go offline and never come back online until the next restart.
very wierd.
Well for the very least we can conclude hotplugging is flawed in the current firmware ...
As soon as we get a proper recovery (nandroid restore that don't bootloop) I'll start working on an improved kernel, this is just not acceptable for a top notch 700€ pricetagged device
JP.
Send from my Note 3 (n9005)
Latest case ...
Send from my Note 3 (n9005)
Again ...
Send from my Note 3 (n9005)
You're on full stock. Doesn't that mean you have no options regarding CPU government?
nakedtime said:
You're on full stock. Doesn't that mean you have no options regarding CPU government?
Click to expand...
Click to collapse
Correct, so I cannot do anything about this misbehaving, except reboot.
I want to know whether this is something others observe as well.
The thing is, if you're not looking at it, you won't know it's happening, cause who really keeps an eye on online cores all the time ? I do as I do kernel coding and as such also work on governors, which make me look at stuff like that.
If this happens of yours, you'll just have a hotter Note 3 with less lasting battery without knowing why, or worse without knowing battery easily could last longer if that was fixed.
This clearly is a bug in the current firmware, since as you correctly stated, being full stock unrooted, I can't be influencing this in any other way than applying load to the CPU which is clearly not the case as you can see in the screenshots... and it just happens randomly.
Once I start on a Note 3 kernel that will be in the top list of things to take care of.
JP.
Sent from my SlimBean 4.3 build 1.8 / Yank555.lu CM10.2 kernel v1.6g-beta4 (Linux 3.0.99) powered Galaxy S3 i9300
I would have gone with the N9000 if I knew how to develop a kernel. BIG.little sounds like so much fun to dev on.
PS
Have you found any Info about the thermal throttling? I'd love to be able to manipulate the temps for less heat when over clocking.
I was actually not going to get any more Samsung device because of crappy open source support they (in fact don't) give
I ended up going for the note 3 because of the specs and exactly because it was the Qualcom and not the Exynos version and a one time offer I could not refuse, but I will go nowhere Samsung's own super secret Exynos CPUs ever again unless they change their policies, which I doubt.
I just do hope I won't regret my move...
JP.
Sent from my SlimBean 4.3 build 1.8 / Yank555.lu CM10.2 kernel v1.6g-beta4 (Linux 3.0.99) powered Galaxy S3 i9300
exactly the same here, after a reboot everything is back to normal
Sent from my SM-N9005 using Tapatalk 2
Happened again after ~10h uptime while watching a live video stream...
Cores went to a steady 4 online, load was unchanged over a longer period (~45 mins of video stream over WiFi).
This makes little sense, hotplugging is flawed.
JP.
PS: Still stock unrooted.
Send from my Note 3 (n9005)
This is still happening for me, reboot solves it. Running 4.4.2 and thought this should be solved by now.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Stock kitkat XXUENB3, unrooted. I have a similar problem when all of the sudden all cores are stuck online with core 1 and 2 stuck at 1958 mhz and core 0 and 3 scaling normally just not going offline. A reboot fixes the issue untill it happens again randomly. This is my last Android device and I had gs2,gnex,n4 and now n9005.
I've rooted and when the issue happens, disabling mp decision and enabling it again fixes the issue so this means that hotplug doesn't play well. Maybe a custom kernel will fix this issue.
ciprianruse88 said:
I've rooted and when the issue happens, disabling mp decision and enabling it again fixes the issue so this means that hotplug doesn't play well. Maybe a custom kernel will fix this issue.
Click to expand...
Click to collapse
Yes, long time I've open this thread
Indeed, on TW I used to do just that, "pkill -9 mpdecision", which killed the daemon and it respawned and all was back to usual.
I've since then moved to CM11, and this never happened again ever since, so I expect this to be a TW related issue, since mpdecision had the same MD5 signature in CM11 as on my stock 4.3 TW ROM.
And it looks like if the problem still persists on KK TW...
But it's certainly not a kernel related issue, as I've use my own kernel on JB TW, where this happened as well, once I went CM11, I ported my kernel to CM, and as I mentioned, never happened ever since.
Might be TW messing with DVFS (for benchmark cheating and maybe other things...).
Maybe worth trying to use Wanam's Xposed Module and disable ROM DVFS.
JP.
2 cores always online and the other 2 always offline= Dual Core
Ok guys I have experienced the bug with 2 cores being always offline which basically makes your Note 3 a dual core phone many times in the past untill I found what caused this! Even firing up Antutu the cores are still 2 and not 4 online! So yeah at first a reboot was an easy and effective sollution but that was not enough so I devoted 2 days trying to find out what caused this. Guess what? The problem was inside one of Samsung apps, specifically the bloody S-Finder app! I can reproduce the bug 100% whenever I want so I am very sure about it! Also I have tested this on 2 other Note 3s (n9005) and I noticed the same bug , with 4.3 and unfortunately now on 4.4.2!
Steps to reproduce it:1) Fire up S-finder 2) Search any app and launch it or even without launching just only by typing on the search bar the phone enters into dual core mode(!) after few seconds 3)Now this is the critical step, remember now the phone is already having only 2 cores enabled so if you press the home button then you are stuck with the buggy dual core mode!!! So this is how you end up with only 2 out of 4 cores working!
The sollution is of course to reboot the phone but another more faster and specific sollution is to close the S-Finder with only this (correct) way: while you are on the S-finder app close it by simply pressing the back button untill it exits completely and you are out to the menu. Incase you are not in the S-finder app then you must check if the program is shown in the recently used apps(longs pressing the home button) then tap on it to open it and then close it by hitting the back button." Don't close/kill it from the task manager or from the recently used apps, only close it when you are inside of the app and hitting the back button!"
Synopsis All in all, the culprit at least on my case is the S-finder app in which when it is used it somehow forces the phone to get into dual core mode and it stays like this because you forget to properly close it after the search is done. The sollution is simply closing the S-Finder gently/properly by using the back button from the inside of the app and not with any other way.
I don't know if this is truly a bug of Samsung or just a sneaky way to increase/improve the battery life at the expense of performance but I surely know that many people have this issue without even realising it!
I said too many things so that I can give a detailed review on this bug, I hope I have expressed it clearly and not to confuse you!
I think it is a very serious issue and it should be fixed as well as inform people about it!
SAVVAS. said:
Ok guys I have experienced the bug with 2 cores being always offline which basically makes your Note 3 a dual core phone many times in the past untill I found what caused this! Even firing up Antutu the cores are still 2 and not 4 online! So yeah at first a reboot was an easy and effective sollution but that was not enough so I devoted 2 days trying to find out what caused this. Guess what? The problem was inside one of Samsung apps, specifically the bloody S-Finder app! I can reproduce the bug 100% whenever I want so I am very sure about it! Also I have tested this on 2 other Note 3s (n9005) and I noticed the same bug , with 4.3 and unfortunately now on 4.4.2!
Steps to reproduce it:1) Fire up S-finder 2) Search any app and launch it or even without launching just only by typing on the search bar the phone enters into dual core mode(!) after few seconds 3)Now this is the critical step, remember now the phone is already having only 2 cores enabled so if you press the home button then you are stuck with the buggy dual core mode!!! So this is how you end up with only 2 out of 4 cores working!
The sollution is of course to reboot the phone but another more faster and specific sollution is to close the S-Finder with only this (correct) way: while you are on the S-finder app close it by simply pressing the back button untill it exits completely and you are out to the menu. Incase you are not in the S-finder app then you must check if the program is shown in the recently used apps(longs pressing the home button) then tap on it to open it and then close it by hitting the back button." Don't close/kill it from the task manager or from the recently used apps, only close it when you are inside of the app and hitting the back button!"
Synopsis All in all, the culprit at least on my case is the S-finder app in which when it is used it somehow forces the phone to get into dual core mode and it stays like this because you forget to properly close it after the search is done. The sollution is simply closing the S-Finder gently/properly by using the back button from the inside of the app and not with any other way.
I don't know if this is truly a bug of Samsung or just a sneaky way to increase/improve the battery life at the expense of performance but I surely know that many people have this issue without even realising it!
I said too many things so that I can give a detailed review on this bug, I hope I have expressed it clearly and not to confuse you!
I think it is a very serious issue and it should be fixed as well as inform people about it!
Click to expand...
Click to collapse
Yes. I've did the exact same thing and cpu was dual core but after I've reset mp decision I couldn't reproduce it anymore. Good catch!
Yank555 said:
I use Android Tuner's online core notifications to keep an eye on this, there are other apps that can to this as well.
Click to expand...
Click to collapse
How did you enable the online core notifications in Android Tuner?
To turn the screen on my Galaxy Note 4 sm-N910G on & off, i press the power button each 24 hour day............... 0 times.
I never touch the darn thing. The phone turns on when i pick it up off the table. It turns on automatically when i take it out of my pocket. It turns on by itself when i flip the wallet case open. It also turns the screen off when i put it in my pocket or flip the case closed or i put it on the table. How?
Get the app "Gravity Screen". BEST APP EVER. It uses the proximity sensor and gyroscopes to sense when the phone's out of the pocket to wake it from sleep. Do u guys use something similar? What cool things do u got going with ur smartphone?
LightspeeDLee said:
Get the app "Gravity Screen". BEST APP EVER. It uses the proximity sensor and gyroscopes to sense when the phone's out of the pocket to wake it from sleep
Click to expand...
Click to collapse
I mostly use the Home button to switch on. Been meaning to try this app out - must give it a go. Are you on Lollipop? Have you found this app has much impact on battery life?
Kinsman-UK said:
I mostly use the Home button to switch on. Been meaning to try this app out - must give it a go. Are you on Lollipop? Have you found this app has much impact on battery life?
Click to expand...
Click to collapse
...or use the spen!
Almost every time also to end a call : )
rarely when i use my wallet/flip case.
the official Samsung one makes use of a sensor to detect if it's open or not.
if it's closed the phone goes into standby and can't wake at all, and if it's flipped open it will automatically wake up.
Tried the app, couldn't get it to work consistently. Either the screen would come on when I didn't want it on, wasting battery, or it wouldn't go off when it was supposed to go off, wasting more battery. Tried all the different settings I could think of. Also the app seemed incredibly laggy at times, at one point becoming totally unresponsive - actually the only app I've ever experienced that with on my Note 4, oddly enough. Uninstalled.
Kinsman-UK said:
I mostly use the Home button to switch on. Been meaning to try this app out - must give it a go. Are you on Lollipop? Have you found this app has much impact on battery life?
Click to expand...
Click to collapse
It worked beautifully on my rooted stock kitkat ROM. I flashed 5.0.1 lollipop last month and decided not to root as i would lose OTA & thought Gravity Screen wont work good without root, but its working for me. No lags or unwanted on/off screen's. Tho if i were to choose, i think it woked better on kitkat.
It hardly has an impact on battery life for me. I get a full days battery everyday, & im a pretty heavy user. Leave the settings on default.
Samsung's got the inbuilt air wake gesture in settings, but i noticed it doesnt wake the phone often enough when u wave in front of the proximity sensor, it's a hit n miss thing. To me, this app works 100% of the time on kitkat rooted. Now on lollipop, about 95%. I love it.
If Gravity Screen isn't working right for anyone, there is another great App that's free & very similar. called: "Wake On Gesture" (playstore). Try that one. I got the paid one of Gravity Screen tho i think it doesn't matter the free version or full version. Wake On Gesture is all free. Plenty other similar apps out there, & i tried many of them. Most are ur basic ones, turn off when proximity is covered, turn on when it's not. These 2 apps have got the most settings that we can configure to our liking, i think the Dev's put in alot of work to their apps. Goodluck
Does anybody know of a method or app to add always on display? I tried an app from the app store and it worked well but killed my battery. Probably because it disabled doze and kept the phone awake... Anybody have any input on this?
That function doesn't work exactly perfectly on the Axon but I am using ACdisplay with some success. The always on thing isn't going to be exactly what you'd see on a Motorola device though. If you want the wave to wake feature as good as it gets, try ambient display through xposed but it's still iffy and ACdisplay has much better notification layouts imo.
This is one of the things that really bugged me about this phone at first, especially with the tiny, barely visible LED notification light. Not good synergy.
Always on Amoled Beta
https://play.google.com/store/apps/details?id=com.tomer.alwayson
howdid said:
Always on Amoled Beta
https://play.google.com/store/apps/details?id=com.tomer.alwayson
Click to expand...
Click to collapse
I tried that one actually. I liked the idea but the power consumption was pretty crazy. Had to uninstall. Maybe others will have better luck.
What you need is a way to allow the CPU to go into deep sleep without turning the display off. I believe this is hardware dependant, though.
All recent moto phone have their own low-power CPUs specifically for ambient display and voice commands without requiring the CPU to wake.
Oneplus devices support gestures while the device is in deep sleep, but this is a hardware feature built into the panel, which is why these gestures are not customizable.
The problem with both of these is that they're hardware-specific, so unless ZTE has made provisions for always on displays, active display, off screen gestures, etc, theres going to be a pretty significant hit to battery when using apps that do these things.
xxBrun0xx said:
What you need is a way to allow the CPU to go into deep sleep without turning the display off. I believe this is hardware dependant, though.
All recent moto phone have their own low-power CPUs specifically for ambient display and voice commands without requiring the CPU to wake.
Oneplus devices support gestures while the device is in deep sleep, but this is a hardware feature built into the panel, which is why these gestures are not customizable.
The problem with both of these is that they're hardware-specific, so unless ZTE has made provisions for always on displays, active display, off screen gestures, etc, theres going to be a pretty significant hit to battery when using apps that do these things.
Click to expand...
Click to collapse
You can read on Qualcomms homepage about the 820 that it supports always on low power mode ....it is something the CPU can do ....look at Samsung's s7s they have the same CPU
howdid said:
You can read on Qualcomms homepage about the 820 that it supports always on low power mode ....it is something the CPU can do ....look at Samsung's s7s they have the same CPU
Click to expand...
Click to collapse
Sweet. I doubt the always on app uses whatever process the s7/g5 use to do this, is this something kernel related?
Thanks for the input everybody. If the Snapdragon 820 can support low power use like some of you suggested we may see this feature in cyanogenmod? (hopefully ZTE actually helps...) otherwise custom roms built on ZTE's base maybe. Although I doubt ZTE will add the feature to the rom in future updates.
xgerryx said:
That function doesn't work exactly perfectly on the Axon but I am using ACdisplay with some success. The always on thing isn't going to be exactly what you'd see on a Motorola device though. If you want the wave to wake feature as good as it gets, try ambient display through xposed but it's still iffy and ACdisplay has much better notification layouts imo.
This is one of the things that really bugged me about this phone at first, especially with the tiny, barely visible LED notification light. Not good synergy.
Click to expand...
Click to collapse
I've seen this app before. Might try it out.
Yes, glance plus
https://play.google.com/store/apps/details?id=com.thsoft.glance
It's awesome, plus your phone thinks it's on the lock screen. So you can shake whenever glance is active to turn on your flashlight.
Double tap to wake works WAY better.
Is also compatible with fingerprint unlock.
I use this on my Axon, haven't noticed any battery drain
MrWilsonxD said:
Yes, glance plus
https://play.google.com/store/apps/details?id=com.thsoft.glance
It's awesome, plus your phone thinks it's on the lock screen. So you can shake whenever glance is active to turn on your flashlight.
Double tap to wake works WAY better.
Is also compatible with fingerprint unlock.
I use this on my Axon, haven't noticed any battery drain
Click to expand...
Click to collapse
I can't figure out how to get the fingerprint working!
When it's on, you can't unlock with fingerprint, you have to wait until the screen is fully black
amus76 said:
I can't figure out how to get the fingerprint working!
When it's on, you can't unlock with fingerprint, you have to wait until the screen is fully black
Click to expand...
Click to collapse
Have you enabled these settings?
MrWilsonxD said:
Have you enabled these settings?
Click to expand...
Click to collapse
Yes and I havec to double tap ton open, the fingerprint is not working when glance is on screen
amus76 said:
Yes and I havec to double tap ton open, the fingerprint is not working when glance is on screen
Click to expand...
Click to collapse
That's strange! I haven't had that issue.. It just immediately unlocks for me.
I would try uninstalling, rebooting, reinstalling? + maybe another reboot? (I'm no tech expert.. But I'll reboot a phone till magic happens lol)
MrWilsonxD said:
That's strange! I haven't had that issue.. It just immediately unlocks for me.
I would try uninstalling, rebooting, reinstalling? + maybe another reboot? (I'm no tech expert.. But I'll reboot a phone till magic happens lol)
Click to expand...
Click to collapse
Still got the problem
amus76 said:
Still got the problem
Click to expand...
Click to collapse
Have you activated it as a device administrator?
MrWilsonxD said:
Have you activated it as a device administrator?
Click to expand...
Click to collapse
Yes, all autorisation
Maybe i'm expecting too much from this app, i want to unlock with the fingerprint directly when you get a notification instead of double tap and I don't think any app at the moment manage to do it
Thanks for the help
amus76 said:
Yes, all autorisation
Maybe i'm expecting too much from this app, i want to unlock with the fingerprint directly when you get a notification instead of double tap and I don't think any app at the moment manage to do it
Thanks for the help
Click to expand...
Click to collapse
That's strange.. As I'm able to do exactly that.. Sorry man.
I am using this app. The clock goes away after showing for a few seconds. It seems to happen intermittently.
MrWilsonxD said:
That's strange! I haven't had that issue.. It just immediately unlocks for me.
I would try uninstalling, rebooting, reinstalling? + maybe another reboot? (I'm no tech expert.. But I'll reboot a phone till magic happens lol)
Click to expand...
Click to collapse
My fingerprint was working. Now its doing the same as yours. Its not working not double tap unlocks phone now.
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.