Whenever I type fast the screen registers touches that I don't do or small swipes. I originally thy thought it was my fault but now I'm noticing it more often.
Does anyone else have this issue? Maybe its a kernel issue or hardware? Using PA with Franco kernel
Sent from my One using XDA Premium 4 mobile app
Here you can see when I'm taping each side alternatively it registers another touch further in the middle, doesn't always happen but enough to be annoying.
OK its pretty hard to see, try yourself using screen touch test
Sent from my One using XDA Premium 4 mobile app
shure2 said:
Whenever I type fast the screen registers touches that I don't do or small swipes. I originally thy thought it was my fault but now I'm noticing it more often.
Does anyone else have this issue? Maybe its a kernel issue or hardware? Using PA with Franco kernel
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I thought I was the only one with this issue. I was gonna reap my fingers off. Wow.
Anyways, I heard CM is issuing a fix coz it has to do with the kernel.
So let's hope there's a fix.
Sent from my One using Tapatalk
i've noticed this as well - can't wait for a fix i hate having to type slow -.-
omg this is one of the BIGGEST issues i'm having with the phone
when i type fast it sometimes registers a swipe left or down which will either delete the last word (Swiftkey) or make the keyboard disappear
its SOOO annoying...
i really hope this is a software issue that can be addressed
i'm coming from the Nexus 5 which was super solid and accurate for typing
i even tried disabling all screen gestures as per the other OPO threads but there isnt any difference
Same here, but for me some times the app i am typing on gets minimized. Does this happen to anyone else?
Sent from my One using XDA Free mobile app
vamshi88 said:
Same here, but for me some times the app i am typing on gets minimized. Does this happen to anyone else?
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Personally I've never had that but I was only using cm11s for 1 day before I moved to Paranoid android. Maybe that's a ROM issue? I've heard of someone else having the same issue as you though
Sent from my One using XDA Premium 4 mobile app
I installed SwiftKey keyboard and see if it helped that issue. Sorry to inform, not by much if at all. Coming from a nexus 5 too and I thought I just wasn't adjusted to the screen size but it is happening regularly enough to make me suspicious.
this issue is becoming a showstopper for me
its like...70% accuracy or less
either it will have a phantom swipe to left or down for me, which will either delete the last word or make my keyboard disappear
i didnt have any of these issues with my N5. I have my N5 right beside me too and i type the exact same speed and its 100% accurate
something is totally off with the OPO touchscreen and i REALLY hope its a software related issue..
farangutan said:
I installed SwiftKey keyboard and see if it helped that issue. Sorry to inform, not by much if at all. Coming from a nexus 5 too and I thought I just wasn't adjusted to the screen size but it is happening regularly enough to make me suspicious.
Click to expand...
Click to collapse
SwiftKey only helps the issue because it is better than Google keyboard at correcting errors when you type. The screen still had the same issue.
Surely hope this is a kernel driver issue that can be fixed. It has been noted by many people and apparently they are working on it or it has been at least acknowledged. I would be surprised if they we would let these phones go out faulty like this without knowing there was a resolution that could be reached....
Got my OPO in the mail on its way. Yet another thing to be concerned about.
Also currently running a nexus 5.
Sent from my Nexus 5 using XDA Free mobile app
I thought it was my own personal error this whole time. Hope it can be fixed with a software update!
Guys, please help us all out and vote on this issue in JIRA to make it as visible as possible to the CM devs. Create a JIRA account, and then on the right, Vote for the issue and then watch it as well. Also, if you can, comment on it too.
https://jira.cyanogenmod.org/browse/BACON-55
There are a LOT of people complaining about this issue, and many of us are nervously waiting to find out if it's a hardware or software issue. I'm personally hoping it's a kernel fix that needs to be done on CM's side, or it's something that can be fixed with a firmware update from JDI.
BTW - for more visibility , I found this official JIRA ticket for the issue:
https://jira.cyanogenmod.org/browse/BACON-55
I hope it gets more exposure. I'm surprised more people haven't complained about this because it's awful.
It's really the only major issue for me though, everything about the phone has been pretty great
*EDIT
oh lol, looks like someone beat me to it haha
I am actually relieved to see other people experiencing this. I use Swiftkey almost exclusively, installed it first thing, and I thought they must have done something, because I have had to focus on slowing down how quickly I type. I am bummed to know it's my phone but relieved to know it's not just me.
cas8180 said:
Got my OPO in the mail on its way. Yet another thing to be concerned about.
Also currently running a nexus 5.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It's being fixed in an update, it's a bug in the Kernel that is going to be fixed.
oscarandjo said:
It's being fixed in an update, it's a bug in the Kernel that is going to be fixed.
Click to expand...
Click to collapse
curious, where did you read this?
oscarandjo said:
It's being fixed in an update, it's a bug in the Kernel that is going to be fixed.
Click to expand...
Click to collapse
In CM11S, or just a future nightly CM11?
Bakedbread said:
curious, where did you read this?
Click to expand...
Click to collapse
Cyanogenmod JIRA.
oscarandjo said:
Cyanogenmod JIRA.
Click to expand...
Click to collapse
No one said its a kernel issue on JIRA. I was the one who posted the issue first on XDA and someone replied to me and took the initiative to put it on JIRA. I've been following this from day 1, and the CM devs said they're looking into it. Never said if it will be fixed or not. We can only hope.
Also please notice the CM devs may have accidentally merged two issues into BACON-55. Please only talk on BACON-55 if your issue is related to fast typing and the multitouch issues.
Related
Hello all.
Hope you guys can help me figure out a little problem I've been having with my nexus.
Its basically quite simple. I've had this problem with both the infin1ty and oxygen roms.
Basically my phone randomly jumps back to the pin entry screen. Its not a total reboot, it Just goes to the pin entry and its like I just restarted the phone again.
Its happened mostly when the phone has been asleep but also one time when I was using it to browse the web. It just jumped to the pin screen asking for my sim card pin code. Its never a full on total reboot.
I don't know what could be causing the problem. The only connection between the two different roms I'm using is the fact that I use the same netarchy kernel, with set cpu and proton voltage app.
I figure if I didn't have my sim card pin enabled then the phone would just connect to the network automatically and I would be none the wiser but due to security I always have my pin enabled. So its quite annoying that when I go to wake my phone to use for something I see the pin screen waiting for me and no signal. I hope some of you guys can help me figure out what's causing the issue.
Thanks in advance
Sent from my Nexus S using XDA App
did it happen when you were on the stock rom?
Anyone???? :-(
Well it didn't happen on stock but I haven't been on stock since January. Long time ago. And its a recent issue
Sent from my Nexus S using XDA App
voyager_s said:
Anyone???? :-(
Well it didn't happen on stock but I haven't been on stock since January. Long time ago. And its a recent issue
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
did you have a sim card pin enabled while on stock?
same issue here, some solution ?
nekoss said:
same issue here, some solution ?
Click to expand...
Click to collapse
Hey, what do you know ...I'm not the only one. That's comforting at least.
I just switched to a new rom about a week ago now and same issues...it seems whatever this thing is, it runs real deep. Very annoying now.
Sent from my Nexus S using XDA App
Having the same issue - it happens irregardless of which custom rom I use. Doesn't happen often, though, like once a week and usually when I'm not using the phone. Have no clue why...
^^^it must be that we are just a small unlucky minority or else others would probably have found a solution by now.
Sent from my Nexus S using XDA App
nekoss said:
same issue here, some solution ?
Click to expand...
Click to collapse
getting a new sim card will solve this issue. worked for me
vabeachfc3s said:
getting a new sim card will solve this issue. worked for me
Click to expand...
Click to collapse
Really? Interesting...might try that and see. Thanks for the tip
Sent from my Nexus S using XDA App
As a general note you should always clear any and all sim card locks before putting them into any smartphones. They almost all use different protocols to communicate with the sim card and without clearing the pin before insertion can cause corruption and that's how these errors arise.
Sent from my Nexus S using xda premium
This phone is not my daily driver, and I'll do as much as I can, but I also have a day job
I would appreciate all discussion stay to this thread, and I'd love it if there were some community self-help.
State of the Union (for the Blaze 4G) (2012-11-05)
Current state of the ROM. This likely applies to any of the ROMs using the kernel sources coming from CyanogenMod for this device.
The device mostly works as it should. There are some problems currently people are having with this phone, and I will detail those here:
1) First and foremost, the Screen of Death. This is a problem that isn't only occuring to us. Just a couple of days ago I asked what the status was and the answer is that they have no idea. Some think it's specific to our platform (msm8660, which we share with a number of other phones), except that I've experienced it on other platforms, like my S3. Some think it's related to the display, except that not all the devices on this platform use the same display. Because of the randomness and lack of verbosity in the bug, they don't have a way of getting any useful data on it. dmesg and logcats are pointless. They are working hard trying to find it, but keep in mind that it isn't just us.
2) Saving pictures somewhere other than local storage. Yes, you should be able to save to your SD card. I think this is coming sooner rather than later. The following patch popped up over the weekend and adds in the functionality: http://review.cyanogenmod.com/25848. The Q&A responses to it look good. I suspect it'll go through a revision or two once they work out the bugs and then it'll get incorporated.
3) Saving app data somewhere other than the local storage. While I'm looking into it and talking to officials, I'm fairly confident that this behavior won't change in the official CM builds. Some of the other CM derived roms may allow this, and you should probably look there to solve this problem. The sad thing fact that our devices shipped with 1.2 GB of internal storage. I don't know why Samsung hates us so much, but they do. And therefore, the default behavior for CM is bad for those of us that want to game. Some users have reported success using an app called Directory Bind. I haven't used it and can't vouch for it, however it looks like it'd let you point specific directories from your internal storage to a space on your external storage. This is definitely safer than the mount swapping ideas that have been going around.
4) BLN isn't 100% unbuggy. Yes, BLN is buggy. BLN is the Button Lights Notifications. As of 11/10 we are on the official CM cypress-touchkey driver. However it seems there's still a bug there. Occasionally if you unlock during a notification, the lights won't come on. Sorry, that's just the way it is.
5) Camera Flash won't disable. This is unfortunate. Apparently if you tell the camera to disable flash, it simply won't do it. It's towards the bottom of my list, but it is definitely there.
The most important thing to keep in mind is that CyanogenMod version 10 is a moving target. Lots of stuff is happening, and until it's labeled as "stable" (and probably even for some time after that), we will continue to experience bugs.
Thank you
Reserved for future posts...
Won't boot. I'll try again...
Edit: Okay second boot worked.
Sent from my LG-P999 using xda premium
Boots fine for me been using it all morning so far so good.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Bulletblitz27 said:
Won't boot. I'll try again...
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Make sure to check the MD5 sum of your download(s). Make sure you wipe dalvik, and do a factory/data reset from CWM. It might also help to format /system.
I used this ZIP in my last install and it has worked fin for me so far... I've actually found it to be fairly stable...
2vivid said:
Boots fine for me been using it all morning so far so good.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
How has the data seemed? The "regular" stuff seemed to work great for me, but since I don't use this phone on a regular basis I don't know how to judge the 3/4g performance.
Also, I'd love to hear about maps performance (GPS, compass, etc).
I know I'm opening a can of worms by asking about this stuff (everyone will be hyperaware of things that never bothered them before), but it's useful to know as feedback.
Data seems normal to me. GPS and compass seem to be working fine for me also.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Do the nav bar buttons take much off of the screen?
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
KrimsonChin said:
Do the nav bar buttons take much off of the screen?
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
I almost think they look better. But I believe the screen just squishes up a little bit.. check out the attached.
So the regular touch buttons will not work anymore, mines doesn't, how do I fix tht
Sent from my SAMSUNG-SGH-T769 using xda premium
badboy68 said:
So the regular touch buttons will not work anymore, mines doesn't, how do I fix tht
Sent from my SAMSUNG-SGH-T769 using xda premium
Click to expand...
Click to collapse
I'm working on it. It wasn't a choice I made, it was a mistake I made and am trying to find it...
Not to be mean, I was jus wondering, this by far though, is hell a damn awesome
Sent from my SAMSUNG-SGH-T769 using xda premium
Surprisingly this is actually more stable than CM9 lol. The camera is smoother and has more options and the Google account synching is easier. The transitions are fast and cool too.
While I'm not a fan of the navigation bar due to the smaller screen, I do love the easy access to the multitasking. It makes switching apps easier. Is this something that you could possibly port without the navigation bar when you fix the buttons? Like give an option in the settings to replace the search button for the multitasking action? I can access the searching from the top widget. Just throwing ideas out lol.
Also the UI sounds are not working, along with the keyboard sounds. I also get this message once in a while about the "CM updater stopped working" it's not a big deal. I haven't used the data much, so I'll report in a little while. Worked fine during the little moment I used it.
Update:
UI sounds are working. Never mind. Let's see if it's consistent or not lol.
Sent from my LG-P999 using xda premium
badboy68 said:
Not to be mean, I was jus wondering, this by far though, is hell a damn awesome
Sent from my SAMSUNG-SGH-T769 using xda premium
Click to expand...
Click to collapse
Oh, don't sweat it, first rom I've ever actually posted so this is a learning process for me... been working on this for ages, all I needed was the kernel source.
Please tell me you asked Google Now to "do a barrel roll"
Bulletblitz27 said:
Surprisingly this is actually more stable than CM9 lol. The camera is smoother and has more options and the Google account synching is easier. The transitions are fast and cool too.
While I'm not a fan of the navigation bar due to the smaller screen, I do love the easy access to the multitasking. It makes switching apps easier. Is this something that you could possibly port without the navigation bar when you fix the buttons? Like give an option in the settings to replace the search button for the multitasking action? I can access the searching from the top widget. Just throwing ideas out lol.
Also the UI sounds are not working, along with the keyboard sounds. I also get this message once in a while about the "CM updater stopped working" it's not a big deal. I haven't used the data much, so I'll report in a little while. Worked fine during the little moment I used it.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Glad to hear it's working out stable for you!
I'm not a Java/Android developer per se... I'm a bit of a self-taught hacker and the majority of my work for this was really about the kernel and forward porting the changes from 3.0.8 samsung sources to the 3.0.43 that CM uses. Adding things to the settings seems a bit daunting to me, but I'll look into it. Always wanted a reason to actually start developing for android
I can tell you that on my SGS3 (and I imagine on other phones as well), the home button, when as a long press, brings up the multitasking menu. This would probably be the immediate answer to your situation for this phone.
I could also possibly just offer up a flashable zip to remap the key and that would be much easier for me.
My long term goal really is to get this into github (and into the CM nightly cycle) and get my kernel changes into the cm kernel for msm8660 so I don't have to maintain the patches myself.
Bulletblitz27 said:
Update:
UI sounds are working. Never mind. Let's see if it's consistent or not lol.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I meant to mention that they start working after the first time you adjust the volume. This seems to be a general CM10 bug as I've had it (and seen people complain about it) on the SGS3.
dr4stic said:
I meant to mention that they start working after the first time you adjust the volume. This seems to be a general CM10 bug as I've had it (and seen people complain about it) on the SGS3.
Click to expand...
Click to collapse
Thanks! I noticed it worked after I adjust it And that flahable zip for the action replacement on the search button would be AWESOME if you can pull it off, but let's focus on polishing what we have lol.
Sent from my LG-P999 using xda premium
Just flashed, its SO smooth. Can't wait for future updates. And I'm kind of liking the navbars lol
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Surprisingly smooth. No force closes. No major unlisted bugs that I've seen.
Incredible
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Is there any way I can change the location of camera photos to my SD card? Can't seem to find it
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Hello! Sorry if my English is not great, it's not my first language.
I have a Prestigio 3400 Duo and I have two issues with my touchscreen, the multitouch function in particular. My phone is freshly factory reset, done while trying to solve this problem, and
The first problem is pretty apparent, when I'm holding two fingers on the screen in a horizontal line it registers only one point at the center of the two I'm actually pressing (that's what a multitouch test app sees, at least). This happens exclusively in an horizontal line.
The second problem I have is when I'm holding two fingers on the screen and I let one go, the other one - the one that's still holding - is not getting registered for an instant before appearing again. So when, say, I'm playing a game on the phone and my character walks and I press a button at the same time, the character stops for a second. Really annoying stuff.
Is there any solution for either of these? I saw some fix for other phones but they're exclusively for those, not mine.
gyrozeppeli said:
Hello! Sorry if my English is not great, it's not my first language.
I have a Prestigio 3400 Duo and I have two issues with my touchscreen, the multitouch function in particular. My phone is freshly factory reset, done while trying to solve this problem, and
The first problem is pretty apparent, when I'm holding two fingers on the screen in a horizontal line it registers only one point at the center of the two I'm actually pressing (that's what a multitouch test app sees, at least). This happens exclusively in an horizontal line.
The second problem I have is when I'm holding two fingers on the screen and I let one go, the other one - the one that's still holding - is not getting registered for an instant before appearing again. So when, say, I'm playing a game on the phone and my character walks and I press a button at the same time, the character stops for a second. Really annoying stuff.
Is there any solution for either of these? I saw some fix for other phones but they're exclusively for those, not mine.
Click to expand...
Click to collapse
Maybe it's a hardware problem.
What did you do before it happened?
Sent from my A706 using XDA Premium 4 mobile app
Ragkhuza said:
Maybe it's a hardware problem.
What did you do before it happened?
Sent from my A706 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I don't know if it was something that I've done that caused this, I don't play many games so I've noticed it only recently. I can tell you that for a while the phone was rooted - now it isn't - but I've never installed CFWs or stuff like that.
gyrozeppeli said:
Well I don't know if it was something that I've done that caused this, I don't play many games so I've noticed it only recently. I can tell you that for a while the phone was rooted - now it isn't - but I've never installed CFWs or stuff like that.
Click to expand...
Click to collapse
What do you mean by recently the phone was root - now it isn't. Can you explain specifically.
Sent from my A706 using XDA Premium 4 mobile app
Try intalling custom rom or reinstalling stock
Sent from my GT-I9300 using XDA Free mobile app
Ragkhuza said:
What do you mean by recently the phone was root - now it isn't. Can you explain specifically.
Sent from my A706 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I took off the root thing because I wanted to play a game that doesn't accept rooted phones.
tchen100 said:
Try intalling custom rom or reinstalling stock
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
Can you direct me to a good custom rom or how to reinstall stock? I'm not good at these things, I don't know much about it.
gyrozeppeli said:
I took off the root thing because I wanted to play a game that doesn't accept rooted phones.
Can you direct me to a good custom rom or how to reinstall stock? I'm not good at these things, I don't know much about it.
Click to expand...
Click to collapse
Take a look at this thread --> http://forum.xda-developers.com/showthread.php?t=2578187
Ragkhuza said:
Take a look at this thread --> http://forum.xda-developers.com/showthread.php?t=2578187
Click to expand...
Click to collapse
Thank you, but there's no stock rom or a tutorial there, so...
I'm bumping the thread, hoping that someone that knows how to fix the problem can see this.
I'd like to at least solve the second problem, because the first one is barely noticeable to me. I basically can't play any game with the second issue because it's really annoying. I read that sometimes these kinds of problems are when you have an app that is used to block the touchscreen of the phone, but I've never used any of those so I don't know.
Is it me or is typing on this device a pain?
Its like I have to type at the devices pace, as in, it cant keep up and letters get skipped or swipe activates.
I havent experienced this on any other device. Any help?
Im using the stock google keyboard.
What keyboard app are you using? I'm using SwiftKey and am not experiencing any problems with double hand typing, although flowing thru SwiftKey can have a lot of errors or sometimes I accidently have my hand on the enter button.
zephiK said:
What keyboard app are you using? I'm using SwiftKey and am not experiencing any problems with double hand typing, although flowing thru SwiftKey can have a lot of errors or sometimes I accidently have my hand on the enter button.
Click to expand...
Click to collapse
Im using the stock google keyboard. Its my favorite keyboard (at least on all the other devices lol)
Which phone did you come from? I have similar issues, but that's from switching from an iPhone! Try changing to ART I have found it a bit smoother.
xkawsx said:
Which phone did you come from? I have similar issues, but that's from switching from an iPhone! Try changing to ART I have found it a bit smoother.
Click to expand...
Click to collapse
Coming from HTC M8 and from Note 3
Try art and then if that doesn't work. Try another keyboard app like SwiftKey, it's free now. So you don't lose anything by trying either
Sent from my One using Tapatalk
zephiK said:
Try art and then if that doesn't work. Try another keyboard app like SwiftKey, it's free now. So you don't lose anything by trying either
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Art helped a little bit but still bad, swiftkey feels better.
Thanks though
Its just you lol
Try using your fingers to type
I have also problems, in portrait mode and with the standard keyboard I can' t type a "b" . Its always the letter nearby... I use now smart t9 keyboard to avoid this problem. I already reseted the device,unchecked the gestures and contacted the support,but still the same !
Im afraid thats it hardware related ?
Juan
Sent from my LG-V500 using XDA Free mobile app
I have the same problems. Try using a touchscreen test app and it'll be even more clear of the inaccuracies. I'm not sure if this is a hardware or kernel issue
Sent from my One using XDA Premium 4 mobile app
This isn't just you. There are plenty of people having this problem. Please, create a JIRA account here and "Vote" on the issue by using the links on the right (and also comment if you can). The higher the exposure, the more seriously they'll take this problem.
https://jira.cyanogenmod.org/browse/BACON-55
As I said in the other thread, we're all very nervously waiting to find out if this is a hardware issue or a software one. I literally cannot reliably type on this thing unless I slow right the heck down and type like a snail.
Hi everybody,
I've Nexus 5 with original rom Android Lollipop 5.01
I've a strange problem and I'd like to know if it is a software or hardware problem.
Sometimes, and only with Facebook app, in a part of the screen appear few pixels and they disappeared when I close the app or I move between tab.
Enclosed an example, I reproduce it in photoshop.
Any idea?
Thank you very much.
Ciao!
Its probably a damaged flex cable. Cheap to replace.
Lethargy said:
Its probably a damaged flex cable. Cheap to replace.
Click to expand...
Click to collapse
Tky for reply. This appears only on Facebook app, and sometimes.
If cable is damage I think always I had this problem.
And if the problem is the app? It's possible?
RoksVempire said:
Tky for reply. This appears only on Facebook app, and sometimes.
If cable is damage I think always I had this problem.
And if the problem is the app? It's possible?
Click to expand...
Click to collapse
Not really sure if it only happens in Facebook then.
I'd say ignore it a bit for now, but if it happens more and in other apps then replace it.
Lethargy said:
Not really sure if it only happens in Facebook then.
I'd say ignore it a bit for now, but if it happens more and in other apps then replace it.
Click to expand...
Click to collapse
Ok tky very much.
Latest question, is there a way to test this problem? For example by a benchmark app or other?
RoksVempire said:
Ok tky very much.
Latest question, is there a way to test this problem? For example by a benchmark app or other?
Click to expand...
Click to collapse
Don't think so, no. Unless you know which exact colors in which exact pixels are causing the issue, which is pretty impossible.
Lethargy said:
Don't think so, no. Unless you know which exact colors in which exact pixels are causing the issue, which is pretty impossible.
Click to expand...
Click to collapse
Tky so much for help
This is a bug in Lollipop and has nothing to do with a hardware defect. I get this in several other apps as well. A fix from Google is already on the way and will be released with a next update of Android.
Sent from my Nexus 5 using XDA Free mobile app
ChrKu said:
This is a bug in Lollipop and has nothing to do with a hardware defect. I get this in several other apps as well. A fix from Google is already on the way and will be released with a next update of Android.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Oh that's great!
Where did u find this news?
It's marked in the Android issue tracker, but I don't know the exact thread anymore.
Sent from my Nexus 5 using XDA Free mobile app
ChrKu said:
It's marked in the Android issue tracker, but I don't know the exact thread anymore.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, but what's the name of this problem? It's difficult to describe it...
Just google "Lollipop graphics glitch" or something like that und you will find many people with this problem
Sent from my Nexus 5 using XDA Free mobile app
Tky very much ?
This problem is described here:
https://code.google.com/p/android/issues/detail?id=80203
RoksVempire said:
Hi everybody,
I've Nexus 5 with original rom Android Lollipop 5.01
I've a strange problem and I'd like to know if it is a software or hardware problem.
Sometimes, and only with Facebook app, in a part of the screen appear few pixels and they disappeared when I close the app or I move between tab.
Enclosed an example, I reproduce it in photoshop.
Any idea?
Thank you very much.
Ciao!
Click to expand...
Click to collapse
have you tried force stoping and then clear cache then data or uninstalling it
poptarticus456 said:
have you tried force stoping and then clear cache then data or uninstalling it
Click to expand...
Click to collapse
Oh yes but the problem is a bug in Lollipop, check previous post.