I'm on t mobile nexus with the ota 4.0.3 update running. My install process was wipe, install 2.3.6, wipe, install the ota from one of the guides on xda, reflash recovery, flash su app. I keep getting screen tearing at the bottom of my launcher, and whenever a part of the screen is supposed to get dim (eg when a popup window comes onscreen) the fade animation acts really weird (it will kind of flash/distort). Any advice? Is this a common occurrence? Should I reflash from stock or would flashing a kernel later on solve this? I kind of don't want to have to reconfigure everything again.
Made a youtube video of the problem:
The launcher will (seemingly at random) get really choppy and start to tear at the bottom of the screen. I know it's hard to make out in the video (I couldn't get my camera to focus properly) but it is tearing. It's easiest to see between 0:05 and 0:10.
bump 10char
I can't be the only one to have noticed this. I see it on both my and my friend's nexus s's.
At least you're getting it in certain situations only. I get screen tearing in the lower left corner of the display in every app that uses hardware acceleration.
Using an I9023 running stock 4.0.3.
Ivenoticed.
Sent from my Nexus S
Related
Hi,
I upgraded my Samsung Galaxy R today to the official ICS version. The phone was on the stock ROM (Gingerbread) earlier.
I did the update using KIES and the update went without any errors. Post upgrade, my Samsung Galaxy R's screen isn't working normally when viewing things involving pure black background. For example, when I open the "Settings" and try scrolling through the list that is shown in the black background, the text leaves streaking effect (leading to multi color dots in the black areas). As a result, the text in the black background becomes scrambled. This problem also happens when the phone is powered on and the start up splash screen (samsung logo in pure black background) appears. The weird fact is that the screen looks absolutely normal when there is no "pure black" element involved in the display and all other colors looks okay.
Just to confirm, I installed the Gingerbread version again (using custom ROM) and the screen works perfectly okay even when scrolling through the various settings with pure black background. Splash screen at the start up doesn't leave any streaks/dots either.
Finally, I tried to install ICS once again in OTA mode and the display issue started happening again. Please find attached the image that shows the problem.
Could you please let me know if I am missing something.
P.S: One more interesting point to note is that the problem happens only when the screen is kept in the portrait mode. The moment I turn the phone to the landscape mode, the screen becomes perfectly clean.
Thanks,
KB.
Hi,
I have attached a couple more screenshots that illustrates the problem.
The issue gets fixed once I put the phone in landscape mode and the issue doesn't happen when displaying colors other than black.
Thanks!
ece2k2 said:
Hi,
I have attached a couple more screenshots that illustrates the problem.
The issue gets fixed once I put the phone in landscape mode and the issue doesn't happen when displaying colors other than black.
Thanks!
Click to expand...
Click to collapse
Hmmm..Its may be lag of ICS. can you give me details like, is it was happening to you in GB as well..??
Or have you flashed any other ROM for the fix..??
kataria.vikesh said:
Hmmm..Its may be lag of ICS. can you give me details like, is it was happening to you in GB as well..??
Or have you flashed any other ROM for the fix..??
Click to expand...
Click to collapse
Hi Vikesh,
I am not facing any issues with GB. The display is absolutely perfect when I tried out GB. I tried the following sequence:
1. The phone was working perfectly in GB and I decided to upgrade to the official ICS
2. Upgraded my phone to ICS using Samsung Kies. Found the display issue the minute ICS started
3. Worried about the problem, I tried flashing the stock GB ROM. This fixed the display issue
4. Tried upgrading to ICS once again - without KIES this time (using Wifi - OTA). Upgrade went without any error, but the display problem started once again after the upgrade
Currently I am using the ICS and it works fine except for the aforementioned display problem. Even the display is pretty responsive and I don't feel any lag while using the phone. Display issue gets sorted the moment I turn the phone to the landscape mode and the problem happens only with black backgrounds in the display.
I am not sure what I am supposed to do and I am thinking of moving back to GB.
Please let me know if you need any other information.
Thanks,
KB.
ece2k2 said:
Hi Vikesh,
I am not facing any issues with GB. The display is absolutely perfect when I tried out GB. I tried the following sequence:
1. The phone was working perfectly in GB and I decided to upgrade to the official ICS
2. Upgraded my phone to ICS using Samsung Kies. Found the display issue the minute ICS started
3. Worried about the problem, I tried flashing the stock GB ROM. This fixed the display issue
4. Tried upgrading to ICS once again - without KIES this time (using Wifi - OTA). Upgrade went without any error, but the display problem started once again after the upgrade
Currently I am using the ICS and it works fine except for the aforementioned display problem. Even the display is pretty responsive and I don't feel any lag while using the phone. Display issue gets sorted the moment I turn the phone to the landscape mode and the problem happens only with black backgrounds in the display.
I am not sure what I am supposed to do and I am thinking of moving back to GB.
Please let me know if you need any other information.
Thanks,
KB.
Click to expand...
Click to collapse
buddy, This kinda problem I never faced. Might b few problem while updating your device, is occurring (which is not reporting as error). So, My suggestion is can you please use ODIN V3.07 & flash it using Offiline mode. i.e. Flashing ICS using ODIN.
Procedure is here -> Click here
First 3 question & answer will let you know everything.
If still problem persist, then do visit SSC or flash latest cm10.1 & based ROM over it.
Hi everybody I am a Skyrocket user. Some days ago I flashed stock android 2.3.5 on my phone via Odin, just to check some performance and old apps. A day later I flashed back JellyBean 4.1.2 stock but I noticed this problem. When I flip my phone to landscape, it rotates quickly and smooth like it always did. But when I flip back to portrait, it stucks in landscape for some seconds before rotating. This is a problem it doesn't always do, sometimes it rotates immediately like it should. I turn auto rotation off as I don't always need it but some apps like camera and youtube still autorotate. I thought it might be a problem with calibration but it didn't help. I'm on stock JellyBean, no rooted.
(If it helps: I was rooted after flashing the firmware and removed some system apps but only AT&T apps like code scanner,mog music etc, and I later unrooted the phone. Tried factory reset also re-flashed the firmware again to see if it might help with the problem but it didn't.)
kristikoroveshi said:
Hi everybody I am a Skyrocket user. Some days ago I flashed stock android 2.3.5 on my phone via Odin, just to check some performance and old apps. A day later I flashed back JellyBean 4.1.2 stock but I noticed this problem. When I flip my phone to landscape, it rotates quickly and smooth like it always did. But when I flip back to portrait, it stucks in landscape for some seconds before rotating. This is a problem it doesn't always do, sometimes it rotates immediately like it should. I turn auto rotation off as I don't always need it but some apps like camera and youtube still autorotate. I thought it might be a problem with calibration but it didn't help. I'm on stock JellyBean, no rooted.
(If it helps: I was rooted after flashing the firmware and removed some system apps but only AT&T apps like code scanner,mog music etc, and I later unrooted the phone. Tried factory reset also re-flashed the firmware again to see if it might help with the problem but it didn't.)
Click to expand...
Click to collapse
If you tried odin back to stock, and the problem is still there on complete stock then it's probably time for a new phone unfortunately.
a few tips:
1. make sure you check the MD5 to make sure those files downloaded ok and aren't corrupt.
2. make sure you cable is good & you're using a USB port on the back of your PC
3. Ebay phones. even sold as new might not be new even though they look new. Could be just brand new replacement parts and new packaging, etc.
4. Check Vincom's troubleshooting thread! read the stickies! if you haven't, maybe something you overlooked as well.
screen rotation problem solve easily this trick working on all phones.
Use Spirit level pro software to calibrate your phone. sceen rotation problem is horizontal calibration fault, you solve screen rotation problem eaisly to use this software. Download from play store and download from attachment. Try this..
kristikoroveshi said:
Hi everybody I am a Skyrocket user. Some days ago I flashed stock android 2.3.5 on my phone via Odin, just to check some performance and old apps. A day later I flashed back JellyBean 4.1.2 stock but I noticed this problem. When I flip my phone to landscape, it rotates quickly and smooth like it always did. But when I flip back to portrait, it stucks in landscape for some seconds before rotating. This is a problem it doesn't always do, sometimes it rotates immediately like it should. I turn auto rotation off as I don't always need it but some apps like camera and youtube still autorotate. I thought it might be a problem with calibration but it didn't help. I'm on stock JellyBean, no rooted.
(If it helps: I was rooted after flashing the firmware and removed some system apps but only AT&T apps like code scanner,mog music etc, and I later unrooted the phone. Tried factory reset also re-flashed the firmware again to see if it might help with the problem but it didn't.)
Click to expand...
Click to collapse
Tripan said:
Use Spirit level pro software to calibrate your phone. sceen rotation problem is horizontal calibration fault, you solve screen rotation problem eaisly to use this software. Download from play store and download from attachment. Try this..
Click to expand...
Click to collapse
Hi kristikoroveshi is your issue solved if not pm me i faced same issue
I've been having screen/display issues (not the yellow hue and separate of the touch screen sensitivity problems). Every now and again, I get flashing, pixilated horizontal lines. I don't see any dead pixels and when it's not blipping the screen seems to display flawlessly, so I'm not sure if it's a software issue or if the hardware is failing. Also it's not isolated to one particular area, it jumps around. Anyone have this problem? Any fixes? I haven't been able to find anything on it. PLEASE HELP. Below is a video of the problem.
akaja24 said:
I've been having screen/display issues (not the yellow hue and separate of the touch screen sensitivity problems). Every now and again, I get flashing, pixilated horizontal lines. I don't see any dead pixels and when it's not blipping the screen seems to display flawlessly, so I'm not sure if it's a software issue or if the hardware is failing. Also it's not isolated to one particular area, it jumps around. Anyone have this problem? Any fixes? I haven't been able to find anything on it. PLEASE HELP. Below is a video of the problem.
Click to expand...
Click to collapse
Are you completely stock? Any custom kernel? Any rom?
Usually it's a kernel issue - tearing, but it's only present on custom kernels (never came across on the stock cm11 kernel). You might wanna try a different kernel though, if you're comfortable with that.
I have the same issue on my stock rom with stock kernel. the only thing i have changed was the developer options. i changed the screen animation time.
mupper said:
I have the same issue on my stock rom with stock kernel. the only thing i have changed was the developer options. i changed the screen animation time.
Click to expand...
Click to collapse
Was it working before those changes?
edit:
Perhaps this might help?
http://forum.xda-developers.com/oneplus-one/general/ghost-touches-flickering-graphics-t2900756
akaja24 said:
I've been having screen/display issues (not the yellow hue and separate of the touch screen sensitivity problems). Every now and again, I get flashing, pixilated horizontal lines. I don't see any dead pixels and when it's not blipping the screen seems to display flawlessly, so I'm not sure if it's a software issue or if the hardware is failing. Also it's not isolated to one particular area, it jumps around. Anyone have this problem? Any fixes? I haven't been able to find anything on it. PLEASE HELP. Below is a video of the problem.
Click to expand...
Click to collapse
I had exact same issue during recording a video yesterday night !! I am latest mahdi and latest franco...
Funny thing is it went away once i exited the camera... what rom and kernel are u using ?
I've been having the same issue too. I don't have a solution for you, though. I haven't been able to find much about it.
Same issue here, stock all the way, only been since latest update. The update didn't flash properly, it gave an error stating it couldn't be located but i went through the files and it was there and then upgraded OK
I had the same problem. Selecting "Force GPU Rendering" in developer options cured it.
i have stock everything. i'm not rooted.
a reboot fixes the problem temporarily. shoot, all the issues i've ran into with this phone thus far (like the GPS not locking on) is fixed by a reboot. i know a reboot is good to do every now-and-again regardless, but having to do it constantly to fix issues is the sign of a failing device and is very annoying; it shouldn't be something you have to do with a brand new device.
i am facing this too randomly. Am on rooted 38R with Franco kernel. Rebooting is a temp cure but it will frustrating to keep doing it.
This happened to me after getting 38R. Fortunately it hasn't been back since a hard reboot. It would show up on Youtube & when dragging down the notifications area.
I had this today on PAC ROM. When I unlock phone and lock ring animation dots flash up made lines come across screen not sure what it was or why. Just rebooted phone. Back to normal. But trying out vanir later tonight try something abit different.
Also experiencing this here.
Stock ROM, clean 38R install.
Stock kernel.
Rooted, with a few xposed modules.
Started a day or two ago. Haven't found a way to recreate it. When it does happen, a reboot remedies it, but only temporarily.
I will attempt to screenrec it the next time.
I find it interesting that I only see mentions of this starting recently.
Same problem for me since the last update. Restarting the Phone solves the problem for some times. Maybe a driver issue?
Glad to see that it is not a hardware issue.
Same here
Same here, mahdi-2.8-bacon-20141001 ROM, enabled "Force GPU rendering" in Developer options, let's see if this comes back!
I have the same problem on latest cm nightly with stock kernel. And dev options works sometimes but it resets on reboot and my phone reboots randomly all the time. I'm starting to hate this device
Sent from my A0001 using Tapatalk
I also have the same issue on Stock 38R update + franco kernel r27
It happens after the latest kernel update, before I never had this lines.
Lucky for me I don't have any reboots now but I fear that will come to pass as well.
Got the same problem with Mahdi Rom 2.8 - 20141016
Will be solved in Franco Kernel r28,he just confirmed this on his kernel thread.
Sent from my OnePlus One using XDA Free mobile app
same issue here. i have to reboot. its happened on stock and AK kernel. will try enabling force gpu rendering and see if it comes back
I flashed 5.0 onto my Nexus 5 a while back and have been loving it. But there is a MAJOR issue I have encountered.
If, from the lock screen, i swipe to open the camera (I use Google's camera app) then swipe on the charms and select video and press record... i can almost always reproduce an immediate forced reboot it makes me very sad.
I have tried wiping the system cache... i'm not sure what else to do...
any advice?
bumping... been playing around with my N5 more and more and still getting the issue.
I notice that it happens in other camera apps that can take videos as well. Not just google's official camera app.
Also, it does not have to be launched from the lock screen for it to occur. sigh.
there have been a few times where i can get it to successfully record a video... but i can't reproduce it all the time. MOST of the time it crashes my entire phone
Same here. Noticed they pushing 5.01 out... Maybe a fix. I've had every Nexus and early software is allways buggy, IMO
thanks so much for replying. just glad it's not only my phone, you know?
I think I found a workaround until google fixes it. and they better.
if you open the camera and switch it to video mode but BEFORE pressing record, if you toggle the thunderbolt (light) on and off at least once (doesn't matter if you leave it on or on afterwards), then start recording it SHOULD work without rebooting... at least it has so far.
Dont have the issue on mine, i have the ElemantalX kernel though but i dont think that makes a difference
Zulith said:
I flashed 5.0 onto my Nexus 5 a while back and have been loving it. But there is a MAJOR issue I have encountered.
If, from the lock screen, i swipe to open the camera (I use Google's camera app) then swipe on the charms and select video and press record... i can almost always reproduce an immediate forced reboot it makes me very sad.
I have tried wiping the system cache... i'm not sure what else to do...
any advice?
Click to expand...
Click to collapse
I'm certainly not suggesting the issue doesn't exist, but I cannot reproduce this on my stock 5.0 installation.
That being said, there are seemingly lots of Lollipop bugs that some people get and others simply do not... in my experience that'll probably make them a little more time-consuming to fix.
Well, a little good news... I hope?
I did a flash to 5.0.1 stock and i can't reproduce it anymore. videos record perfectly fine.
now let's give it a week or so of me dicking around with various apps and settings and see how that goes
Zulith said:
Well, a little good news... I hope?
I did a flash to 5.0.1 stock and i can't reproduce it anymore. videos record perfectly fine.
now let's give it a week or so of me dicking around with various apps and settings and see how that goes
Click to expand...
Click to collapse
That's interesting - they must have changed something about the camera then.
I wasn't having the issue you described but I did occasionally get "cannot connect to camera".. fingers crossed it's sorted :good:
After installing Lollipop, everything became unbearably slow. I've tried flashing multiple ROMs, both Lollipop and Kitkat, but everything remains so slow: the actual boot-up process and the ROM itself. Does anybody have any ideas about what can be done about this? In fastboot I see hammerhead D820(H) 32GB; HW version rev_11; Bootloader version HHZ12d, Baseband M8974A-2.0.50.2.22. Lock state is unlocked. Any suggestions will be highly appreciated!
Wipe cache and see if that helps and disable Chrome's integration into the app switcher. Also get rid of Facebook and FB Messenger.
Sent from my Nexus 5 using XDA Free mobile app
Instead of Lollypop try some LSD
Thanks. But it is that slow even before any of these apps are loaded (e.g. after I do a factory reset and flash a new rom). Is it possible that Lollipop did sthg to the hardware? If so, how could I find out? Just to give you an idea about how slow exactly it is: when I am typing 5 letters at normal speed, it takes until the fifth letter before the first letter actually displays on the screen. I should also note that when the screen goes off, I can no longer get it on again without a reboot...
I'm still trying to figure out what this might be. I first thought my problems were similar to those that others have described, but I now think they be different. Here are some of the issues I'm encountering:
when I boot up the phone (whether in kitkat or lollipop), the initial android (animation sequence is already incredibly slow
there are all sorts of strange things happening with my screen. When it goes to sleep in Android, I can not wake it up anymore. When it goes to sleep in recovery, and I push the power button, the screen goes (again after some time) from pitch dark to a slightly 'lit' dark, but it never displays anything, and I have to reboot again to get the info on the screen. Also, the screen is even slow in twrp - when I swipe to do a factory reset, for instance, there is also a noticeable lag.
I have tried with various ROMs (both stock and not); with ART and Dalvik, etc. but none of these changes seem to affect the slow screen issues
Does anybody have any ideas about what the problem might be? I should also add that we had the screen replaced a few months ago - could that have something to do with it?
sdspieg said:
I'm still trying to figure out what this might be. I first thought my problems were similar to those that others have described, but I now think they be different. Here are some of the issues I'm encountering:
when I boot up the phone (whether in kitkat or lollipop), the initial android (animation sequence is already incredibly slow
there are all sorts of strange things happening with my screen. When it goes to sleep in Android, I can not wake it up anymore. When it goes to sleep in recovery, and I push the power button, the screen goes (again after some time) from pitch dark to a slightly 'lit' dark, but it never displays anything, and I have to reboot again to get the info on the screen. Also, the screen is even slow in twrp - when I swipe to do a factory reset, for instance, there is also a noticeable lag.
I have tried with various ROMs (both stock and not); with ART and Dalvik, etc. but none of these changes seem to affect the slow screen issues
Does anybody have any ideas about what the problem might be? I should also add that we had the screen replaced a few months ago - could that have something to do with it?
Click to expand...
Click to collapse
Probably the replacement screen has been reconnected poorly. There's nothing you can do on software side, for me, it's more like a hardware problem.