Hello guys , i would like to know whether anyone else has experienced any type of graphical glitches on their 6p.
the thing is , i had a Nexust 6 (Moto) last year, and during cold temperature it would get a split screen bug few times every few hours and it was very annoying.
the only fix for it was to use a custom kernel with 'interactive' governors.
the kernel that worked best for me to get rid of that graphical glitch was Lean Kernel.
but my 6p thankfully is not getting the splitting screen graphical glitch, but instead it just looks like the picture of whatever app i am in just gets smashed into each other (sorry i dont know how to explain!).
it basically glitches for a second and is back to normal , and it happens like a couple of times per day, happened only recently after the weather here got cold.
is this a common thing with the 6p? i am now wondering whether i should try lean kernel with it ,as i am currently using flash kernel.
hm, at first i thought it was because of a profile i used on my 6p so i disabled profiles, then i thought it could be caused by the theme (cm13) so i reverted theme to stock.
but the random occasional graphic glitch was still there.
hope someone can shed some light on this for me.
Only if you could explain it a lil more maybe a screenshot or something
What kind of temperatures?
Phones usually last fine till about -15 celsius, beyond that intense screen ghostings (maybe this is what you meant?) start appearing, phone turns slow in general and battery dies very fast also causing permanent damage to the battery.
If it is the screen ghosting then that is perfectly normal and usually dissapears when it gets warm again, but I can not confirm as I have no 6P nor have had any amoled phones.
Does the glitch show up on screenshots? Or is it only visible physically?
tauio111 said:
What kind of temperatures?
Phones usually last fine till about -15 celsius, beyond that intense screen ghostings (maybe this is what you meant?) start appearing, phone turns slow in general and battery dies very fast also causing permanent damage to the battery.
If it is the screen ghosting then that is perfectly normal and usually dissapears when it gets warm again, but I can not confirm as I have no 6P nor have had any amoled phones.
Does the glitch show up on screenshots? Or is it only visible physically?
Click to expand...
Click to collapse
its only physically visible, i think it is because of the app Twitter..
when i open it up ,that graphical glitch appears for a split second, it looks like the app itself makes the screen shimmery? i dont know how to explain it, but yes i think it was twitter.
but then again, i think it is what you stated, screen ghosting.
and that stuff is normal ? if so then all is good, thanks!
@Prattham and @tauio111 sorry guys ,pretty late on providing screenshot.
i happen to have one where it took place, the graphic glitch.
it ocassionaly still does happen..
turned out it is not at all because of cold temp.
it is stupidly hot right now, haha.
and btw. it also happens more often when i go switching too fast between apps with the recents button.
and also at times when i scroll.(with scrolling happens way more rarely though).
here is the picture , look at how the picture in the youtube app (official one) mashes into each other.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
a lot of people are reporting this problem when the phone is off
http://androidforums.com/htc-evo-4g/106893-i-just-notied-my-evo-glows-dark.html
JoshHuman said:
Here is the problem on a 002 15 second exposure in complete darkness.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
The way I see ut is that the button panel has its own backlight and is meant to turn on in complete darkness, but some evo's do it when the phone is off given enough power since the panel's software run a separate lower powered chip, but I'm no engineer. It can be fixed with a firmware update, probably.
Mine did this once. I turned it back on and killed a bunch of apps with advanced task killer, and then it quit. Think it was just a fluke because it hasn't happened since.. and that was about a week ago. If it's happening constantly even after reboots, I'd assume you have installed something that is acting retarded in the background.
actually it's not a software problem... I hard reseted and kepted the phone clean and checked at night. still LED problem being lit. I took it to a store and they are willing to replace the phone
Yes this happens to me alot and i have to remove the battery and put it back in i left the phone like that for 10 minutes and i click every button but does not come back on so have to remove the battery
My wife's has been doing that and it will not stop. Ive rebooted cleaned all apps and nothing. I'm trying to return it but am waiting for bestbuy to call me when they get more phones. Any one have a solution?
Sent from my PC36100 using XDA App
I have the opposite problem. Mine never seem to turn on in complete darkness. >_<
I just noticed this for the first time last night. Haven't seen it before or since.
Sent from my PC36100 using XDA App
TheBiles said:
I have the opposite problem. Mine never seem to turn on in complete darkness. >_<
Click to expand...
Click to collapse
wish i had that problem. i really have no need for back lights on the menu. the bleed they cause is terrible when looking at dark movies.
on the droid, in froyo at least, the menu buttons dim when watching a movie or you can use LEDsHack to turn off the lights.
I posted this issue a couple days ago and got no replies. I have noticed this issue on my phone. Sometimes pressing volume up/down will cause the lights to come on too.
I wonder if this is the cause of poor battery life. It's almost as if the light sensor is still functioning when the phone is supposed to be sleeping.
I noticed this also on both mine and my girls 0002 models... You can see it during the day too if you cup your hands around the bottom of the screen just over the buttons and look under. Wasn't sure what that was all about. Looks like just another glitch to me.
Is this good enough reason to request exchange? Does this drain battery faster in any way?
apexi350z said:
Is this good enough reason to request exchange? Does this drain battery faster in any way?
Click to expand...
Click to collapse
yes it is a good reason. kills battery
delete please.. double post
I thought the whole time that the "glow in the dark" was a feature. Its something I certainly don't mind, as I have found it rather useful.
But since its not a feature... then... defect? Haha. Well, this EVO is going back to the store anyway.
I have a weird problem with my Wildfire's screen after I did an OTA upgrade to Froyo.
First, the top of the screen stopped working. The taskbar wouldn't work and I the top wasn't responding. All of a sudden, after approximately a month or so, it started working again.
It worked fine for a few weeks and then the right side of the screen has a problem. All of a sudden it started automatically hitting the spot on the screen where the letter "P" would appear on the keyboard. When I was trying to type out a message, the letter "P" would get hit on its own over and over again. When the keyboard was not open, it would still happen.
I felt it might be a virus, so I did a hard reset. This still didn't stop. So I switched off my phone and kept it in a desk for 48 hours. When I switched it on again, this problem stopped, but the right side of my phone was not responsive (approximately 4 milimeters of it).
I can see that this is clearly not a hardware problem and has something to do with the firmware/OS. I'm not too sure what to do. I've tried flashing new ROMs on to my phone, but it remains the same way.
Incidently, when I tried flashing "TheNextSense" ROM on to my phone, the phone started hitting the portion of the screen where the "P" key would appear. When I switched back to CM7, it stopped, but the right side was unresponsive.
Is this something to do with the memory? Or is this a known issue with upgrades/certain ROMs?
Any help will be appreciated. This is driving me crazy
why do you think its not a harware problem ?
for me it sounds like it is one. (temperature or short circuit problem)
IANAHRM (I Am Not An HTC Repair Man) but I think the touch screen connector has just slightly worn loose, perhaps due to temperatures. It sits on the right side of the main board (left side of the phone itself). I know the Wildfire can survive quite a motion shock so that shouldn't be it (I hope).
Nandroid backup and restore jobs heat up my phone quite a bit, did this occur on your device as well while you were installing roms? That might explain the change in behaviour.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
henkdv said:
IANAHRM (I Am Not An HTC Repair Man) but I think the touch screen connector has just slightly worn loose, perhaps due to temperatures. It sits on the right side of the main board (left side of the phone itself). I know the Wildfire can survive quite a motion shock so that shouldn't be it (I hope).
Nandroid backup and restore jobs heat up my phone quite a bit, did this occur on your device as well while you were installing roms? That might explain the change in behaviour.
Click to expand...
Click to collapse
Nope. It's never heated up till now. This happened all of a sudden, and it gets worse with upgrades. It's like, for some reason, the phone isn't able to function properly with any ROM other than the stock ROM. I'm going to try to put back eclair on it today and see whether it works. Will keep you posted.
stavro said:
why do you think its not a harware problem ?
for me it sounds like it is one. (temperature or short circuit problem)
Click to expand...
Click to collapse
Because it doesn't always occur. It kind of gets fixed on its own after a few days. It's like my phone has a ghost in it
I put back the stock Froyo ROM and now the problem is 50% better - much of the portion of the screen that was dead earlier is now responding. But the rest still isn't. Any ideas? :-(
My HD2 appears to have some big time screen problems, so i wonder if anyone has any sugestions.
Background
It never really lived in a case and the inevitable drops happened. That ended in about November when one drop too many caused the screen to crack. I replaced the digitiser and lcd screen which got it all working again happily, though beecause of the amount of fiddly stuff involved the chassis never truly fit perfectly, the screen protruded ever so slightly above the edge of the case, etc.
Fast forward to last weekend when for no apparent reason (i hadnt dropped it or anything) it started to behave erratically, not registering screen taps and then suddenly doing many things at one, making it almost impossible to send text messages and use effectively. My thought was that maybe it was losing calibration so tried aligning the screen but nothing would really happen.
Furhtermore it seemed like the bottom section of the screen had almost no responsiveness at all.
I therefore thought it might have something to do with the connections inside the machine, so i decided to take it all apart and check all the connections were sturdy. Thats when the real problems started because when i put it back together and turned it on, i had a horrible display that makes it next to useless.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I actually just fired it up to check that it was sill the case and it seems slightly worse than this picture!
So the questions. Firstly, does anyone know what might be the problem here. Is it likely to be the connection between the processor and the lcd, or soemthing more of a problem? How easy is it likely to be to sort it? A case of a completely new screen needed? Or is it likely to be something fairly simple? And would those problems with teh LCD screen be a similar cause of the calibration problems (i thought the digitiser might not be working properly, hence the original decision to take it to pieces!)
Hope someone can help. Happily my upgrade was due last friday, buit it would be nice to have a working phone for spare use etc.
Steve
It seems to me a bad LCD(100%) and probably a bad touchscreen!
As i suspected. Has anyone else with a replacement digitiser/lcd had any similar problems?
Hello, I've been best friends with my Atrix since a little over a year now. We have had many experiences together and our relationship has bloomed a lot with time. I confess I haven't completely looked after my phone, I'm a little clumsy, specially if I don't get to sleep enogh. So almost a month ago, after getting up very early, I was reading a notification when my phone fell. I tried to grab it but I pushed it even more. It went straight to a cornered tile on my bathroom. This was the result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And trust me, it's much worst in person than you can see there. Surprisingly enough the touchscreen works just as fine as it always did, even the notification area works fine (the top of the screen has been the more affected area), although I can't use the front camera anymore because there's a big scratch on top of it. Also something happened to the headphone jack because I can't use it anymore. Regardless of all this, the phone itself keeps working like a charm. I have been unemployed for a couple of months now, have a couple of bad debts so I don't have any money to fix it for the time being, so I have no choice but to use it like this.
But I have two weird errors, which has caused me to write this. The first one is related to the proximity sensor. Everytime I answer a call, the screen turns off as it should, but after the call end the screen doesn't come back on and there's no way for me to turn it, so I have to pull the battery and reset it. I tried to mark the option for the screen not to turn off when I pick a call but it keeps doing it regardless, so I suppose what I should do is to try to take the phone apart and see what's happening on the inside.
This pulling of the battery has led me to the discovery of the second error which I think it's the most interesting: 1 out of maybe 20 times that I do that, for whatever reason, a random app gets uninstalled from my phone. The first time it happened I blamed the app (growlr was the first), but then I saw it happened to Twitter, then to Google Plus, then to Script Manager. And it's not like it gets deleted completely, if I go to the app manager I can see it on the list but not with the regular name (ie: com.twitter.whatever instead of just Twitter). I'm using Neutrino but I'm not sure if I could blame the system, I think it's caused from the battery pulling in the same way turning off a computer by force can produce errors on the file system.
So has any of you come across problems like these before? Do you have any suggestions?
Please take a look at this picture. This is "pointer location" option in Developer Options. The red line is an arch I made with a single stroke, but as you see it is broken in two places. There is a part on the screen where it happens at the entire width of display. It is not constant, but happens many, many times a day. I also get screen freezes, and ghost touches which run apps, make random phone calls, etc.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Malarz said:
Please take a look at this picture. This is "pointer location" option in Developer Options. The red line is an arch I made with a single stroke, but as you see it is broken in two places. There is a part on the screen where it happens at the entire width of display. It is not constant, but happens many, many times a day. I also get screen freezes, and ghost touches which run apps, make random phone calls, etc.
Click to expand...
Click to collapse
I think this is a known symptom of degradation for the Nexus 4. Two of my friends already had this problem and nothing but a replacement screen could fix their problems. As I did research for them I came across many people who suffered from the same issues.
I have the same problem , it'a just about a month that is happening and it doesn't recognize the right part of the screen
Here I have the same problem, about 1 month ago started to have some touch parts dead, but it has been worsening, now its almost useless.
I too had the same problem. I had to change the screen. It cost about £30 from ebay for a new one. On the replacement I noticed that the version number of the screen was higher and also the manufacturing date was a few months younger than the broken original. Also the digitizer lines look different when light shines on them. Perhaps they realized that there was an issue with some of the earlier models.
Surprisingly the issue lessened for me. It is not gone completely, but for the last 5-6 days it does not happen as often as it used to, now maybe only once a day. A week ago I started using _only_ the original charger. I had read somewhere that a faulty battery or charger may be causing erratic screen. Not sure if the change of charger has anything to do with it, or if that's just a fluke.