Related
I have a couple of "issues" with the phone. Not sure if its software related or hardware related. Maybe you guys can check on yours too see if it happens. This is all on stock ATT rom
It seems the One has "dynamic contrast" enabled by default. When scrolling on webpages, for example, if I come to an area with a dark advertisement, the brightness adjusts very slightly most of the time. Thats all well and good but the annoying thing is that it does it in steps causing quick blinks of the backlight. Its most pronounced at medium brightness. The same "blinking" happen when autobrightness wants to set the brightness to a very low level . It does it in very discrete steps and it takes a long time for the brightness to settle to its minimum.
If i set my brightness to 50% (most prevalent when the slider is under the "t" in brightness) I get a VERY subtle, but constant pulsating of the backlight. Again, Its a very subtle but my eyes pick it up regardless and its distracting as hell. I wouldn't mind it if autobrightness didn't hit this brightness level, but it does sometimes indoors. The effect is best seen on a mixed white and color screen, like a homescreen with a white widget and most websites. If the brightness goes a bit above or below this level, the pulsing goes away . Anyone else seeing this? maybe it happens at a different brightnesses on different screens.
Thanks
I noticed this when watching a video today. Maybe it only happens if you have autobrightness on?
Sent from my HTC One
It happens with autobrightness off for me. I actually tested it a bit more. I happens on a variety of backlight settings depending on what's on the screen.
At approx. 33% brightness (im using an app called screen adjuster to set the system brightness to a specific value), the screen does heavy pulsating on an all white image. For example, if I go to "about:blank" in the web browser. I can be seen on a desktop screen with a white widget or the settings menu.
Same thing at 40. Worst is 33% though. I have a feeling its dynamic contrast going haywire at certain brightnesses. If you turn the screen off then on, it doesnt do it for a second or 2, but then it will start. I haven't been able to find a demo unit anywhere around me to test this out. So if someone can check this on their device, I would appreciate it. Please use Screen Adjuster to get a definitive reading on the brightness. (Use the slider in "system brightness" to set it to a specific brightbess) and go to "about:blank" in the default browser
hi..
i had the widget set on the third setting, the fourth being the brightest. i had the same problem with my first phone and thought at the time it may have been a backlight problem? or power flow problem? i sent that phone back and the next phone did the same? after posting on here.. i removed the widget and manually adjusted the brightness. i like the screen quite bright, manual adjustment cleared the problem for me. i gotta say yep the flicker was more visible on screens with alot of white, google, facebook, texts? and way way annoying! i can only suggest you try the same as i did? perhaps it is just a quirk with the htc? or maybe the os? you never know, when the update to keylime or whatever it is called comes out the flicker may go totally?
JUST had this on facebook? hope it helps?
HTC One
HTC One : Update Available (1.29.401.12)
HTC is currently deploying an update for the new One
Version: 1.29.401.12 - Size: 229.04 MB
It includes :
- System Optimization
... - Updating Service Location
- HTC Zoe: Optimizing sound quality
- Camera: Optimizing Parameters
- Beats Audio: Sound enhancement
- other fixes
coming soon...
shep98 said:
hi..
i had the widget set on the third setting, the fourth being the brightest. i had the same problem with my first phone and thought at the time it may have been a backlight problem? or power flow problem? i sent that phone back and the next phone did the same? after posting on here.. i removed the widget and manually adjusted the brightness. i like the screen quite bright, manual adjustment cleared the problem for me. i gotta say yep the flicker was more visible on screens with alot of white, google, facebook, texts? and way way annoying! i can only suggest you try the same as i did? perhaps it is just a quirk with the htc? or maybe the os? you never know, when the update to keylime or whatever it is called comes out the flicker may go totally?
JUST had this on facebook? hope it helps?
HTC One
HTC One : Update Available (1.29.401.12)
HTC is currently deploying an update for the new One
Version: 1.29.401.12 - Size: 229.04 MB
It includes :
- System Optimization
... - Updating Service Location
- HTC Zoe: Optimizing sound quality
- Camera: Optimizing Parameters
- Beats Audio: Sound enhancement
- other fixes
coming soon...
Click to expand...
Click to collapse
Thanks for the response. I ended up looking at 4 more devices at 2 different stores and they all had the flicker. The sales associates even saw it. I got tired of doing exchanges and I ended up reversing my upgrade. Im going to wait and see what happens with this issue. Hopefully it gets sorted out with a firmware update, because otherwise its an awesome phone. Its a shame that the $100 trade-in offer is going to end by then and I wont be getting a free medialink device, but atleast i'd be able to get it in black, which is what I originally wanted.
Ive noticed this too and its really annoying me. Ive tried multiple roms including the new asop carbon rom and its even on that.
Mr Sliff said:
Ive noticed this too and its really annoying me. Ive tried multiple roms including the new asop carbon rom and its even on that.
Click to expand...
Click to collapse
In addition to the phones I exchanged, every display model that I've come across has had it. I'm was a bit surprised at first that not many people have come across this. I'm starting to think that maybe the One has a PWM backlighting, which some folks are sensitive to and some don't even notice. I'm in the former category and I think you are too. It a shame really that this problem exist. Besides that, I couldn't find any other faults with the phone. It was perfect in every other aspect
I've run Into the same exact behavior using the HTC droid DNA with both sense 4+ and sense 5 ROMs. I smell tomfoolery afoot.
Screen Flicker
I'm glad I'm not the only one that has noticed this. It doesn't stay that way very long for me, but it is quite annoying. Seems to happen when there's a white or light-colored background the most. So I guess there's nothing specifically wrong with my phone and we'll either have to live with it or wait until someone figures out how to fix it?
I guess most people don't notice this.m it's extremely irrational going between this and my tablet and having the black.ighting flashing in my face when I scroll through webpages.
For the past week or so my phone has had flickering multicolored lines flash across the homescreen(s)/lockscreen when I turn the display back on. Sometimes it will also happen if I'm sitting on the homescreen with the display already on.
Here is my Rom history as the problem began:
Was on supernexus (Android 4.2.2 I believe) - issue was not present
Flashed Unofficial Slim build 6 (wiped cache/dalvik/factory reset before install)- started having the issue
Flashed Unofficial Slim build 6.2 (wiped cache/dalvik)- issue still present
Flashed AOCP 5.7 yesterday (wiped cache/dalvik/factory reset and formatted internal SD)- thought issue was gone, but it started happening again today.
I tried taking screenshots but the issue disappears as soon as I press the volume+power button to take the screenshot. This only seems to happen when I'm on the homescreen/lockscreen, I dont think it has happened while in any other apps.
I'm wondering if this might be an issue with the specific version of the Nova launcher, as I believe that is the common denominator between these Roms (isn't AOCPs launcher based on CM's nova?). I just installed go launcher and the problem seems to be gone (for now).
Has anyone else seen something like this? I apologize if this has been discussed somewhere, I spent several hours searching Google and XDA before posting. I can post a picture later when I have access to another camera phone.
Same issue here
I have the same issue at the lock screen. Prevalent on all JB roms I have tried, carbon, revolt & slim bean.
I'm currently using Carbon nightly. I have not seen a fix for this yet. I have heard it might be an issue with the processor waking up from sleep.
After installing Go Launcher Ex opening it a couple times and then going back to using the Aspire launcher that came with AOCP, I haven't had this issue again all afternoon. Didn't have it at all yesterday though, so it might come back.
I played around with all the brightness settings but it didn't seem to do anything. Do you happen to have any pictures of the effect you are getting? I'll try and post a picture of mine tonight if it happens again. Thanks!
About 3 hours ago, I changed some GPU & lock screen settings and the issue has not reappeared.
I will post back either later tonight or tomorrow morning with some info.
I haven't taken any photos of the problem yet. By the way, do you usually experience the issue on lock screen coming from a screen off state?
ditto on this. I have Cyanogenmod 10.1 installed and I get these lines intermittently.
Try turning off CRT animations and disable hw overlays.
Sent from my SAMSUNG-SGH-I717 using xda premium
disabling hardware overlays always fixes it for me
same issue
Have the same issue going on had freezing and resolved that now I'm stuck on these lines multiple diff ROMs I am running cm10 I see people saying he overlays can someone provide a little more info on what that is and where to find it? Attaching screen shots of these multi color lines we speak of
Nvm can do it with the browser will edit this later and add them with a pc
nimixes said:
I am running cm10 I see people saying he overlays can someone provide a little more info on what that is and where to find it?
Click to expand...
Click to collapse
Go to settings, developer options scroll half way down and you will find it. You will have to disable it every time you reboot or you can use two paid apps from the market. These apps are tasker and secure setting they are both worth every cent.
Sent from my SAMSUNG-SGH-I717 using xda premium
Do you have any backlight handling apps? I used lux all the time and it stopped after I disabled it.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4 Beta
Just enabled "Disabled HW overlay" and "Force GPU rendering". Like some of the users suggested, I found about the possible solution from this video:
http://www.youtube.com/watch?v=yhhPPke_Nbw
(go to 1:40)
I usually get the flickering with the lock screen (I use WidgetLocker Lockscreen). I was having some flickering this morning and checking both of those options seemed to immediately cut out the flickering.
I ran across it(the flickering lines) on one of the 4.2.2 roms, can't remember exactly which one but what I ended up having to do was disable one of the tweak apps it came with and install Trickster Mod only. Worked for me, no more flickering or rebooting, not sure what the cause may have been but have had no other issues after that for I believe it was 2 weeks
Please elaborate
Demmonnixx said:
I ran across it(the flickering lines) on one of the 4.2.2 roms, can't remember exactly which one but what I ended up having to do was disable one of the tweak apps it came with and install Trickster Mod only. Worked for me, no more flickering or rebooting, not sure what the cause may have been but have had no other issues after that for I believe it was 2 weeks
Click to expand...
Click to collapse
By chance can you give some more details about this Trickster Mod like where to find it and what it is supposed to do?
A link to a thread would be great
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
nimixes said:
By chance can you give some more details about this Trickster Mod like where to find it and what it is supposed to do?
A link to a thread would be great
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2301558&page=22
Scroll down to my post there. If you still need help, just let me know.
Trickster mod I believe is mainly for Rom's that have Kernels that can be OC'd or Under Clocked. Kind of the same as Android Tweaker or SetCPU but is a little smoother for me IMO.
Go into your connection settings. Turn on your wifi, right after you switch it on, pull down your notifications bar and keep going up and down with it while the wifi turns on. Does your notification bar get all laggy and stuttery while the wifi turns on?
Sent from my SCH-I545 using xda app-developers app
Chadly said:
Go into your connection settings. Turn on your wifi, right after you switch it on, pull down your notifications bar and keep going up and down with it while the wifi turns on. Does your notification bar get all laggy and stuttery while the wifi turns on?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
yeah. wifi turning on/off and switching to mobile network lags the entire phone down.
kinda does it on every android phone, but it's 10x worse on the gs4 because of touchwiz lol
Yes...but this is one of those things that is super specific to a certain scenario. I never noticed it before.
Sent from my SCH-I545 using xda premium
jayochs said:
yeah. wifi turning on/off and switching to mobile network lags the entire phone down.
kinda does it on every android phone, but it's 10x worse on the gs4 because of touchwiz lol
Click to expand...
Click to collapse
Glad I'm not the only one lol. Hey I saw you talking in some thread about gs4 head issues. Mine gets got too but the hottest I've seen it was 41c battery and i was on it and charging it at the same time. Thats really the only time it gets close to 40, is when I'm charging it and using it. Most of the time it seems to be 30-36c when I'm using it. Is this ok?
Sent from my SCH-I545 using xda app-developers app
It's weird cuz the wifi thing doesn't lag my note 2 at all. I think the new version of android is messed up. Hopefully we get some updates soon. If i had a defected device wouldn't it show up in the benchmarks? I ran every benchmark and get higher scores than any other phone so I know the hardware is good.
Sent from my SCH-I545 using xda app-developers app
Chadly said:
Go into your connection settings. Turn on your wifi, right after you switch it on, pull down your notifications bar and keep going up and down with it while the wifi turns on. Does your notification bar get all laggy and stuttery while the wifi turns on?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
No, this doesn't lag my S4 at all. However, I set "Disable hardware overlays" to always use GPU for screen composing (in developer options). With this option set I haven't noticed a single stutter.
Before this workaround, I used to notice microstutters here and there (it would stutter doing window animation opening up facebook notifications for example).
Word of caution: supposedly this can cause problems for some apps. The only app that has problems is quadrant
I tried that setting but it didn't seem to change anything. All I want to change about the phone is the occasional home button lag I'm experiencing. Sometimes when I hit the home button it takes half a second to respond but when I clear all my recent apps the home button response is instant. Any ideas?
Sent from my Verizon Galaxy S4
elucid said:
No, this doesn't lag my S4 at all. However, I set "Disable hardware overlays" to always use GPU for screen composing (in developer options). With this option set I haven't noticed a single stutter.
Before this workaround, I used to notice microstutters here and there (it would stutter doing window animation opening up facebook notifications for example).
Word of caution: supposedly this can cause problems for some apps. The only app that has problems is quadrant
Click to expand...
Click to collapse
ive tried that before and haven't noticed anything..and i noticed it resets on reboot too. does yours?
elucid said:
No, this doesn't lag my S4 at all. However, I set "Disable hardware overlays" to always use GPU for screen composing (in developer options). With this option set I haven't noticed a single stutter.
Before this workaround, I used to notice microstutters here and there (it would stutter doing window animation opening up facebook notifications for example).
Word of caution: supposedly this can cause problems for some apps. The only app that has problems is quadrant
Click to expand...
Click to collapse
Thank you for this.. I never really had the need to disable hardware overlays, but my snapchat app lags hardcore when going from my snap list to the camera. This has fixed that. Is there any disadvantage to disabling hardware overlays?
Sent from my SCH-I545 using xda app-developers app
There's a lot of lag on this phone, but still a lot to love!
Sent from my SCH-I545 using xda premium
Please read forum rules before posting
Questions and help issues go in Q&A and Help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I've seen a few threads/comments here about the flickering/adjusting of the backlight level at lower (less than 50%) brightness levels even though auto-brightness was off. As was suspected, it's just due to a content adaptive backlight module. It can be shut off by just running the CABLPreferences activity of the com.qualcomm.cabl app. It also looks like there is a "quality" setting in there to play with that just varies the aggressiveness of the effect.
If you don't know how to launch an activity, you can do the following:
Via ADB:
Code:
adb shell "am start -a android.intent.action.MAIN -n com.qualcomm.cabl/com.qualcomm.cabl.CABLPreferences"
Via Terminal on your phone:
Code:
am start -a android.intent.action.MAIN -n com.qualcomm.cabl/com.qualcomm.cabl.CABLPreferences
I haven't done any more checking, but I'm guessing this is just a flag that could be set in sys/devices/blah... by init.d script on boot as well.
If you prefer a gui, there are plenty of launchers out there that can select an activity to start. I actually had it set up as a long-press pie on LMT while I was playing with it.
It seems (on my phone, at least), that the app wasn't as good at turning it back on, but you can just clear the app data/cache on "Content Adaptive Backlight Settings" in application manager, reboot, and you'll be back to stock behavior.
Sorry I didn't post this sooner. I've been too busy playing with the G2!
this doesn't work.
I've tried this weeks ago. simply telling the app to turn it off does nothing, as it's still on no matter what. deleting the app produces the same exact effect.
in the build prop, the line pointing to cabl is set to false. therefore it's really not even reading what the app is saying it seems.
I believe it's a kernel issue that can only be solved once we get a custom one.
again, this isn't a fix and doesn't turn it off at all sadly.
Sent from my VS980 4G using Tapatalk 4
https://www.youtube.com/watch?v=slwkFhpiYbs&feature=youtube_gdata_player this video was made when it was set unchecked and set to off.
Sent from my VS980 4G using Tapatalk 4
I read your post about this a couple of weeks ago and saw that you mentioned deleting the app, but did you try running it, unchecking the box and rebooting? Deleting it won't do anything, as the app is set to run on boot and (as far as I can tell) set whatever selection you have chosen. I did and this seems to have worked for me I checked by scrolling through a spot on settings that had normally triggered it. I'll play with it more later to see if I either got lucky when I tested it or it is still happening. I agree that this is working on a kernel level.
Is this issue on all carrier versions?
I use auto-brightness and the annoyance I have is that it doesn't change brightness right away when entering different lighting environments. It either takes time or doesn't change at all until I uncheck/check the auto-brightness setting.
xdabbeb said:
I read your post about this a couple of weeks ago and saw that you mentioned deleting the app, but did you try running it, unchecking the box and rebooting? Deleting it won't do anything, as the app is set to run on boot and (as far as I can tell) set whatever selection you have chosen. I did and this seems to have worked for me I checked by scrolling through a spot on settings that had normally triggered it. I'll play with it more later to see if I either got lucky when I tested it or it is still happening. I agree that this is working on a kernel level.
Click to expand...
Click to collapse
yeah, if the app is deleted, then it can't run unless defaulted to on without the app. . so i tried deleting it, and then i also tried un checking the box, and it still does it. no matter what, there must be a setting somewhere else to actually turn it off. did you see that line in the build prop? it's set to false... weird right?
Sent from my VS980 4G using Tapatalk 4
jayochs said:
yeah, if the app is deleted, then it can't run unless defaulted to on without the app. . so i tried deleting it, and then i also tried un checking the box, and it still does it. no matter what, there must be a setting somewhere else to actually turn it off. did you see that line in the build prop? it's set to false... weird right?
Sent from my VS980 4G using Tapatalk 4
Click to expand...
Click to collapse
Yep, I did...and I remembered I had set it to true before I even began messing with the CABL App. I was thinking that could be the difference between what you and I had tried, but I just did a bit more testing to see if it was happening still and unfortunately I think I may have seen it. I'll play with it a bit more later to be sure. I also did a quick look in the usual places for this to be turned on/off in /sys/class/ and couldn't find anything. I suppose it's possible LG built the kernel for this device without the ability to turn it off. If so...that'll be unfortunate.
xdabbeb said:
Yep, I did...and I remembered I had set it to true before I even began messing with the CABL App. I was thinking that could be the difference between what you and I had tried, but I just did a bit more testing to see if it was happening still and unfortunately I think I may have seen it. I'll play with it a bit more later to be sure. I also did a quick look in the usual places for this to be turned on/off in /sys/class/ and couldn't find anything. I suppose it's possible LG built the kernel for this device without the ability to turn it off. If so...that'll be unfortunate.
Click to expand...
Click to collapse
I believe the original Nexus 7 had this feature in the kernel too. However, in custom kernels you could use Trickster mod to toggle the feature off. I think the kernel devs had to expose the setting though, so maybe we'll get this taken care of if we can get a custom kernel.
Here are some build props for Qualcom devices that control the CABL
Code:
ro.qualcomm.cabl=1
hw.cabl.level=Auto
persist.qcom.cabl.video_only=1
By adding / editing these lines in the build.prop you should be able to adjust as noted in the lines.
And yes, it is in the kernel.
Dont know why LG has an app for it?
Scott, I sent you a message on hangouts but in my build prop, i don't show a 1 for the cabl setting.. i show false... as if it's already turned off in the build prop. I changed it to true once and it didn't do anything. those two top settings seem to be what's in the app.. you can check a box to turn it on and off (the first line) and then you can set the degree to which it handles the cabl (second line.) I've messed with both in the app and it did absolutely nothing... does the kernel need to be changed as well?
Sent from my VS980 4G using Tapatalk 4
xdabbeb said:
I've seen a few threads/comments here about the flickering/adjusting of the backlight level at lower (less than 50%) brightness levels even though auto-brightness was off. As was suspected, it's just due to a content adaptive backlight module. It can be shut off by just running the CABLPreferences activity of the com.qualcomm.cabl app. It also looks like there is a "quality" setting in there to play with that just varies the aggressiveness of the effect.
Click to expand...
Click to collapse
I'm not sure you really want to "fix" this feature.
LCD screens (like the one in the LG G2) have inherent low contrast ratio (just 1500:1, in comparison to infinity, with AMOLEDs). In order to compensate, LCD screens use a feature called "dynamic contrast", in which the backlight dims when the screen shows darker content, in order for the perceived black levels to appear darker (and not grey). I'm not sure you want to disable this feature, because the outcome will be grey blacks.
we do want to bc it causes horrible screen flicker issues. you can be sitting on a pic and it doesn't know what to do so it flickers badly
Sent from my VS980 4G using Tapatalk 4
Noam23 said:
I'm not sure you really want to "fix" this feature.
LCD screens (like the one in the LG G2) have inherent low contrast ratio (just 1500:1, in comparison to infinity, with AMOLEDs). In order to compensate, LCD screens use a feature called "dynamic contrast", in which the backlight dims when the screen shows darker content, in order for the perceived black levels to appear darker (and not grey). I'm not sure you want to disable this feature, because the outcome will be grey blacks.
Click to expand...
Click to collapse
I did not know about the contrast ratio on these screens. Makes sense what you are saying.
However like Jay said it does not react smoothly or at appropriate times.
Some will need to edit the kernel code to fix this.
Noam23 said:
I'm not sure you really want to "fix" this feature.
LCD screens (like the one in the LG G2) have inherent low contrast ratio (just 1500:1, in comparison to infinity, with AMOLEDs). In order to compensate, LCD screens use a feature called "dynamic contrast", in which the backlight dims when the screen shows darker content, in order for the perceived black levels to appear darker (and not grey). I'm not sure you want to disable this feature, because the outcome will be grey blacks.
Click to expand...
Click to collapse
Yep. What @jayochs and @scrosler said. What you wrote does make sense, and I had noticed that it behaves the opposite of the CAB implementation on AMOLED screens (where it dims on lighter colored content)...so that gives even more credence to what you're saying, but the implementation is a little buggy. It transitions abruptly and causes the "flickering" that many have reported. I certainly wouldn't mind having it enabled if the transitions were slower/less frequent, but it's kind of annoying as it is. I never was able to find a way to disable it in the stock kernel anyway, so hopefully it can be fixed one way or another now that the source is available. Still the best phone I've owned!
So any success with any method here or elsewhere?
I'm currently using Xposed to try and figure out what is going on here (I have several updateBrightness() events hooked, and am logging stack traces from them). It happened again less than an hour ago, so I need to go through that stack trace and see if I can figure out whether or not the actual brightness update can be blocked.
This has nothing to do with CABL, incidentally. I have CABL turned off, and I've seen the flicker-flicker-flicker-brightness drop issue with nothing more than a web page open. I usually keep my brightness around 68%-69%, too.
antinorm said:
I'm currently using Xposed to try and figure out what is going on here (I have several updateBrightness() events hooked, and am logging stack traces from them). It happened again less than an hour ago, so I need to go through that stack trace and see if I can figure out whether or not the actual brightness update can be blocked.
This has nothing to do with CABL, incidentally. I have CABL turned off, and I've seen the flicker-flicker-flicker-brightness drop issue with nothing more than a web page open. I usually keep my brightness around 68%-69%, too.
Click to expand...
Click to collapse
i'm thinking it's CABL, but it's kernel level, NOT software level, which is why disabling it does absolutely nothing.
I've been using Lux Auto Brightness to fix the issue.
Cheers!
Rayan said:
I've been using Lux Auto Brightness to fix the issue.
Cheers!
Click to expand...
Click to collapse
it's not an issue with auto brightness, that's a completely different problem.
this is the content adaptive backlight problem.
so no solution was ever found for this (besides a new kernel)? my phone doesn't flicker but on the brightness below 50% i can notice it's trying to readjust itself slightly once in awhile (with xda app or play store for example).
Encountered this issue as well. So, the cause of this has something to do with the software and not the hardware? Don't want to send my phone back just to receive yet another problematic set.. I set my screen brightness to 38 which it flickers on certain photos and apps. Bumped it up to about 45 and it seems to have stopped.
I've had my Z2 for a day, and before I bought it I read a review that measured phone reaction time between when the screen was clicked and when the phone started to react and it was DOG SLOW. Now I'm definitely experiencing the same. I mean there is noticeable lag when clicking something (like the Home button for example) and when the phone actually starts to take action. Is this normal? Is this just due to Sony's Android Customization?
Really?!! My experience is exactly opposite. I think the phone's touchscreen is too sensitive.
So I usually type wrong... ( Maybe it's my personal problem)
carbonmeteor said:
Really?!! My experience is exactly opposite. I think the phone's touchscreen is too sensitive.
So I usually type wrong... ( Maybe it's my personal problem)
Click to expand...
Click to collapse
Yeah the problem isn't sensitivity, it's responsiveness. The screen sensitivity is fine, it's just that the time it take between when I click the Home button and the point at which the Z2 actually STARTS to close my current app and bring me to the home screen seems WAY too long to me. Not sure if the review I read and my experience is normal or is the reviewer and I both have phones with issues.
I see... I misunderstood your words~~
Did u upgrade the firmware ? OR the problem had existed from the beginning?
Coz it's seldom that a new phone has such...lag
My phone did update when I started it for the first time, but I don't know how it was before the update since it was brand new.
SwarlosEstavez said:
My phone did update when I started it for the first time, but I don't know how it was before the update since it was brand new.
Click to expand...
Click to collapse
For myself, I usually do a factory reset after a OS version update~ otherwise waiting for the next update released by official .
I always do a factory reset on system updates. Prevents a lot of weird things...
Sent from my SGP312 using XDA Premium 4 mobile app
SwarlosEstavez said:
Yeah the problem isn't sensitivity, it's responsiveness. The screen sensitivity is fine, it's just that the time it take between when I click the Home button and the point at which the Z2 actually STARTS to close my current app and bring me to the home screen seems WAY too long to me. Not sure if the review I read and my experience is normal or is the reviewer and I both have phones with issues.
Click to expand...
Click to collapse
Maybe its the default animation of the default launcher. Personally I don't seem to have this problem, when I press the home button it goes straight to the homescreen, there is no delay but I don't use the default launcher.
Go into developer options and turn animations off, maybe this might help you
Settings>About phone>Build number, keep clicking it until you unlock developer mode
SwarlosEstavez said:
I've had my Z2 for a day, and before I bought it I read a review that measured phone reaction time between when the screen was clicked and when the phone started to react and it was DOG SLOW. Now I'm definitely experiencing the same. I mean there is noticeable lag when clicking something (like the Home button for example) and when the phone actually starts to take action. Is this normal? Is this just due to Sony's Android Customization?
Click to expand...
Click to collapse
Nope. My Z2 responds very quickly. It may be a problem with your device.
Same goes, although i curently have a very defective unit, everything is very rapid
I agree with @nreuge this could be a fault with your device
Sent from my D6503 using XDA Premium 4 mobile app
My z2 sometimes lags too, not much, but I can feel it,
How about a backup and a hard reset then? It helps to that most at-times.
Definitely more sluggish than the HTC One M8 and iPhone 5s. It isn't as bad as the Galaxy S5 though.
Sent from my iPhone using Tapatalk
Its far from sluggish, and the speed at which home button reacts to your press isnt really a deciding factor in phones performance..
Thanks for the responses everyone. I did a factory reset and it did help a bit. I guess the phone just isn't as fast and responsive as others on the market. It's a far cry from the Nexus 5 and the HTC M8, but I'm sure that over time I'll either get used to it or flash a custom rom on it.
The Z2 isnt as slugish as people have mentioned
I can play almost all games around -40-60fps
If you cant acheieve this and have no lag at all lag through home or navigating apps, your unit is probably defective
Sent from my D6503 using XDA Premium 4 mobile app
feis said:
Its far from sluggish, and the speed at which home button reacts to your press isnt really a deciding factor in phones performance..
Click to expand...
Click to collapse
You're right it's not, but a Snapdragon 801 shouldn't hesitate to go to the home screen when you press home.
Envious_Data said:
The Z2 isnt as slugish as people have mentioned
I can play almost all games around -40-60fps
If you cant acheieve this and have lag through home or navigating apps, your unit is defective
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This has nothing to do with gaming performance. I can play all games without any stutter, but as soon as the home button is hit or the recent apps button is hit, it will hesitate before opening or going to the homescreen. It's not "defective", something is just making the phone sluggish.
OP, I removed the small apps launcher from the recent apps panel and it seems to be a bit faster, though still not instant.
Ya, it is not about playing games, it is these little things, like home key, camera app, setting manual, recent app key.....
the z2 is a bit slow and lags compares to other flagships. It is not too bad, but the lags are there. It doesn't happen all the time.
If you are coming from dual core phones you will not notice it, however if you are coming from M8 or S5, you will notice it.
Hopefully the next update will fix this.
No phone is perfect, overall I am very happy with the z2, except the audio......:crying: I will get used to it.
If you need to speed up the phones response try altering the 'Drawing modes' for Window animation, transition animation and animator duration scales.
To do this you first need to activate Developer mode.
Go to Settings/About phone and at the very bottom of the list tap on Build number eight times.
This will bring up a small warning informing you Developer mode is now active.
Next, go back to Settings and you will notice in between Printing and About phone you now have 'Developer options' available.
Tap on Developer options and scroll down to the 'Drawing' section.
Where it says:-
Window animation scale
Transition animation scale
Animator duration scale
Change these three settings from 1x to .5x
You should now notice your phone is much snappier and responsive.
Beards said:
If you need to speed up the phones response try altering the 'Drawing modes' for Window animation, transition animation and animator duration scales.
To do this you first need to activate Developer mode.
Go to Settings/About phone and at the very bottom of the list tap on Build number eight times.
This will bring up a small warning informing you Developer mode is now active.
Next, go back to Settings and you will notice in between Printing and About phone you now have 'Developer options' available.
Tap on Developer options and scroll down to the 'Drawing' section.
Where it says:-
Window animation scale
Transition animation scale
Animator duration scale
Change these three settings from 1x to .5x
You should now notice your phone is much snappier and responsive.
Click to expand...
Click to collapse
That does make a difference, thanks!