Related
So, this started happening out of random I believe (Specifically after flashing the faster 3g mod), and I'm not quite sure what happened. I doubt the 'faster 3g mod' caused it, but it happens on stock roms, backups previous to the 3g mod, etc...
Basically, what happens is when I open my slider, the screen gets distorted sometimes, and there are blue and yellow blotches all over the place that flicker. It doesn't happen when I'm in portrait mode, and I've even tried editing voodoo settings to see if it was just voodoo causing this, but it wasn't. Sometimes, if I take off auto brightness, it stops temporarily. But do you guys think it's a problem with the phone itself? If so, what would I need to replace?
I think it is the hardware. I would make sure that everything in the phone is plugged it well and not loose.
Sent from my SPH-D700 using Tapatalk
Ahhh, I figured. Is there a guide anywhere on how to safely take this apart?
xLoveHateLegend said:
Ahhh, I figured. Is there a guide anywhere on how to safely take this apart?
Click to expand...
Click to collapse
Have you tried odining back to a stock rom? I have no idea if this would help but its worth a try.... if that fails.... its def gonna be your hardware
sent via my Samsung EPIC 4G running cm9 : alpha 3 : samurai tanto
xLoveHateLegend said:
Ahhh, I figured. Is there a guide anywhere on how to safely take this apart?
Click to expand...
Click to collapse
There is a video to disassemble it somewhere. Google turns it up.
Edit: here's one: http://www.youtube.com/watch?v=IeO89VGAPuU
@realtic, yes I have. I figured it was the hardware... guess I'm gonna have to tear this thing apart now :/
@kenny, thank you for the link
What exactly do you guys is loose/needs replacement?
Sent from the one and only Legendary Samurai ;]
Hi,
I've noticed an issue recently with my SGS3 (I747M). The flicker that I am referring to is not the more common hardware overlays issue, but rather only occurs, or is noticeable, on a white background. What happens is the screen will flicker colors; it's not that the entire screen will display one color and change to another and another rapidly, but rather it seems random pixels on the screen will flicker in waves...almost a 'shimmering' effect. So far, it seems to happen not immediately after reboot, but later on as I use my device. I was hoping this was a software issue, but so far it seems to be more likely a hardware issue.
From googling, I have found that this issue is not limited to myself (http://www.howardforums.com/showthread.php/1772504-Samsung-Galaxy-S3-Praise-and-Problems), that being said, I couldn't find anyone else here on XDA that has this issue. Have any of you experienced it? and if so, what did you do? return under warranty perhaps?
Thanks in advance.
mk_ln said:
Hi,
I've noticed an issue recently with my SGS3 (I747M). The flicker that I am referring to is not the more common hardware overlays issue, but rather only occurs, or is noticeable, on a white background. What happens is the screen will flicker colors; it's not that the entire screen will display one color and change to another and another rapidly, but rather it seems random pixels on the screen will flicker in waves...almost a 'shimmering' effect. So far, it seems to happen not immediately after reboot, but later on as I use my device. I was hoping this was a software issue, but so far it seems to be more likely a hardware issue.
From googling, I have found that this issue is not limited to myself (http://www.howardforums.com/showthread.php/1772504-Samsung-Galaxy-S3-Praise-and-Problems), that being said, I couldn't find anyone else here on XDA that has this issue. Have any of you experienced it? and if so, what did you do? return under warranty perhaps?
Thanks in advance.
Click to expand...
Click to collapse
It might be a digitizer problem, digitizers are hard to replace but, I think zedomax has a way to change it.
Just go on galaxys3root.com-- this might help http://galaxys3root.com/galaxy-s3-root/how-to-replace-broken-lcd-screen-on-galaxy-s3/
thanks for the reply, but would a malfunctioning digitizer actually cause the screen to shimmer as it does? I would think it might be a digitizer problem if the screen wasn't recognizing my inputs properly, but I think this is a different issue which, to me, seems to be not related to the digitizer.
thanks though!
any other possible ideas/solutions?
I have had that issue. It would do the same thing and then lock up because I would try and hit the home button. The. It would do a full reboot. Weirdest thing I have ever had happen to a phone. I tried different than roms and stock and didn't do a dang thing. Returned it to att.
Sent from my SGH-I747 using xda app-developers app
I suppose if it actually does get to that point where it renders the phone as unusable as in your case, I'll probably do the same...though since it's outside the 14 days I have with my provider (Rogers), I think I might have to go through with a warranty replacement through Samsung.
Thanks for the reply
update:
It seems it was either the ROM or Kernel that caused the issue (last few versions of task's AOKP). After flashing a different ROM (bacon version of Roger's JB), the issue seems to be resolved *knock on wood*.
Just now replaced my ribbon cable as i faced some problem with my old one.
But after replacing it i was not able to adjust the screen brightness, by adjusting the screen brightness only my softkey light brightness is adjusted not my screen brightness.
So whats the solution for my problem? really confused
some one help me on this please!!! My battery drains cause of this full brightness
ramprabhu19 said:
Just now replaced my ribbon cable as i faced some problem with my old one.
But after replacing it i was not able to adjust the screen brightness, by adjusting the screen brightness only my softkey light brightness is adjusted not my screen brightness.
So whats the solution for my problem? really confused
Click to expand...
Click to collapse
Are you sure it's a hardware issue (OK sound stupid but it's easiest to check if it's a software issue)? Try a couple of different ROMs, from the latest CM10.1 test builds all the way to rock hard stable CM7 and stock ROMs. It's interesting that soft key light is being changed though; did you mix up some wires or something? Also, not to insult your intelligence but you have turned off autobrightness, haven't you?
HTCDreamOn said:
Are you sure it's a hardware issue (OK sound stupid but it's easiest to check if it's a software issue)? Try a couple of different ROMs, from the latest CM10.1 test builds all the way to rock hard stable CM7 and stock ROMs. It's interesting that soft key light is being changed though; did you mix up some wires or something? Also, not to insult your intelligence but you have turned off autobrightness, haven't you?
Click to expand...
Click to collapse
Sorry i forgot to mention those things... i already tried many roms, still the problem persist. and i dont think that i mixed up the wires cause it doesnt have much wire connections in the ribbon cable and they are just plug in type so we cant make wrong in the connections.
Even tried external apps to control the brightness... still the soft key ligh is adjusted not the screen brightness
http://forum.xda-developers.com/showthread.php?t=2268259
demkantor said:
http://forum.xda-developers.com/showthread.php?t=2268259
Click to expand...
Click to collapse
in that thread you mentioned about increasing the brightness... what about the lowering the level?
i tried those codes...but nothing happened
I'm doubting it is software then, you have tried different ROMs and manually changing brightness so I will assume you need to replace your LCD. Being I have never seen this issue before this is just my best guess and what makes sense to me. It is doubtful that the flex is causing this issue and the screen itself is to blame
Sent from my Nexus 7 using xda premium
demkantor said:
I'm doubting it is software then, you have tried different ROMs and manually changing brightness so I will assume you need to replace your LCD. Being I have never seen this issue before this is just my best guess and what makes sense to me. It is doubtful that the flex is causing this issue and the screen itself is to blame
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
i dont think that the lcd is defective...i think my new ribbon cable is not supporting this,...but i dont know how and why?? (might be its because made in china?)
can i change the brightness level thru build. prop editor?
its very possible but it really doesnt make sense how the cable wont support it, do you have your old to test against?
and i doubt build.prop will change a thing as we have already attempted manually changing it and it appears to be hardware
demkantor said:
its very possible but it really doesnt make sense how the cable wont support it, do you have your old to test against?
and i doubt build.prop will change a thing as we have already attempted manually changing it and it appears to be hardware
Click to expand...
Click to collapse
yes am having the old one, but its fault is about the display..so cant use that any more... i tried to figure out the brightness option in build prop, but i cant find that option...can u help me on this?
truthfully i dont know of anything in build.prop that would be changed to change brightness level, ill dig around in a bit but nothing off the top of my head.
but again if using adb to change brightness or any other manual method wont change then there is a hardware fault somewhere as this happens across all roms.
i guess i never asked, is the screen the same brightness in recovery and bootloader?
if so you will need either a new lcd or flex cable
but in general even if we use low brightness in phone, while getting into recovery or bootmenu it will be in normal brightnes..i think so,....so i dont find any difference in brightness level at recovery page..but do we have options to change brightness level in recovery mode?
That would be coded into your recovery and bootloader respectively, I couldn't say how esay that would be to change, probably near impossible in hboot and still hard in recovery. Don't know the brigtness value in them but I assume high
I guess there is an off chance a sensor is malfunctioning, download z device test from market and test them, but this shouldn't be a symptom of a bad sensor.
Really you need to find out what hardware to change
Sent from my RubiX NonSense using xda app-developers app
I don't use my camera flash much, so I'm not sure when this started, but all photos taken with the flash have an orange cast or tint to them. In the flash preview before the actual picture, it looks fine, but once the final flash/photo is taken, they're orange. I tried several other camera apps, and they all behave the same way. The only way I could get a proper picture with the flash was to install camera zoom fx, and put the flash in torch mode, then, pictures turned out looking ok.
I was thinking it might be a hardware issue, but the pre-flash is ok, and the flash light is ok. Looking at the flash when the picture is taken, both LEDs light up.
Has any one else seen this issue?
I have an Unlocked US HTC 10 with the stock software (1.96.617.20), and HTC Camera (8.10.779478).
A bit more testing, it seems to only happen when it's fairly dark. And looking at the room when the flash fires, it's very obvious to the naked eye the flash is actually orange, so I don't think it's a camera white balance issue. When there is some additional ambient light, the flash pictures seem to come out ok, the flash itself does not have the orange tint to it.
Do you have a case on the phone? If so, try it without the case.
Had the same issue and like Rolo42 said above, I took off the Ice View case and tried it with flash in an almost pitch black room. No orange tint this time.
Sent from my HTC 10 using XDA-Developers mobile app
This is with no case.
Sent from my HTC 10 using Tapatalk
So, I've played around with this a bit more. I think the issue is when it uses a not full powered flash, that it gets the orange tint. In a completely dark room, the flash is fine. The initial focus flash is fine. It's just the flash with some ambient light that is the issue. For what it's worth, I only see this issue when I have the flash forced on. If it's on auto, and it selects to not use the flash, and I then set it to force the flash is usually when I see this. I've tried on both MM and now Nougat, with the same results. I was kinda hoping the upgrade to Nougat would fix this.
So I was looking through my past pictures looking for a specific one, and I noticed that this orange flash issue has existed since I got the phone. I don't think noticed since I usually only took flash pictures for things like the state of the plumbing under the sink before I tried to fix something. I hadn't taken many flash pictures, and when I did, it wasn't something where I much cared what it looked like, other than that I could make out what was going on.
As a result, I've done a chat with HTC, and when through all troubleshooting steps sans a factory reset. I doubt the factory reset will help it, but if it doesn't, the HTC rep said the next step was replacement under the Uh-Oh protection.
Orange tint
Did you fix your problem?
w69 said:
Did you fix your problem?
Click to expand...
Click to collapse
Yes and no. I ended up getting a replacement 10 about a year ago. The new phone didn't have the same problem. So I have a phone that works, but I didn't actually fix the phone that had the issue.
Sent from my HTC 10 using Tapatalk
Any time the screen turns off and I turn it back on, I have to wait 30 seconds to a minute before the touch screen is responsive at all. I've tried using my fingerprint or removing all screen security and that doesn't seem to make a difference. Has anyone else run into a similar issue? Any idea on how to fix it?
zebinadams said:
Any time the screen turns off and I turn it back on, I have to wait 30 seconds to a minute before the touch screen is responsive at all. I've tried using my fingerprint or removing all screen security and that doesn't seem to make a difference. Has anyone else run into a similar issue? Any idea on how to fix it?
Click to expand...
Click to collapse
What android version are you running? Do you have many apps installed? Have you tried restoring back to factory defaults?
I believe it started after upgrading to 9 manually a few weeks ago. But I've tried a few different ROMs with the same situation. I have not rolled back to 8 to test that yet. It happens right out of the gate without installing any additional apps as well. I've done multiple full wipes, including unlocking the bootloader that for sure wiped everything with no change to the situation.
zebinadams said:
I believe it started after upgrading to 9 manually a few weeks ago. But I've tried a few different ROMs with the same situation. I have not rolled back to 8 to test that yet. It happens right out of the gate without installing any additional apps as well. I've done multiple full wipes, including unlocking the bootloader that for sure wiped everything with no change to the situation.
Click to expand...
Click to collapse
Fastboot upgrade? If not, i'd download 9 stock RETAIL and just flash it all with fastboot
Ok, I'll try that when I get a chance. we'll see if it works.
marcost22 said:
Fastboot upgrade? If not, i'd download 9 stock RETAIL and just flash it all with fastboot
Click to expand...
Click to collapse
I just re-flashed via fastboot 9 stock RETAIL found here. Looks like I'm still having the same issue as before with the touch screen not being responsive after turning the screen back on. Even if it's only been off for half a second, it will still not be responsive for a minute
Any further ideas? Or is there a better location to get the RETAIL image for XT1710-01?
zebinadams said:
I just re-flashed via fastboot 9 stock RETAIL found here. Looks like I'm still having the same issue as before with the touch screen not being responsive after turning the screen back on. Even if it's only been off for half a second, it will still not be responsive for a minute
Any further ideas? Or is there a better location to get the RETAIL image for XT1710-01?
Click to expand...
Click to collapse
This is gonna sound weird, but have you changed your screen at all?
marcost22 said:
This is gonna sound weird, but have you changed your screen at all?
Click to expand...
Click to collapse
Actually, yes. Just after getting the phone, it was dropped and the screen had to be replaced. The fingerprint sensor has been loose ever since then too. But this was never an issue until flashing a new ROM
zebinadams said:
Actually, yes. Just after getting the phone, it was dropped and the screen had to be replaced. The fingerprint sensor has been loose ever since then too. But this was never an issue until flashing a new ROM
Click to expand...
Click to collapse
did you have someone else replace your screen? If so, and it might sound weird, they might have installed an LCD screen instead of OLED; and then modified the stock rom for that. You might not know, but OLED and LCD have very different power profiles, so when turning LCD on you can just blast it, meanwhile oled you need to slowly bring the power up. This is what might be causing your issues
marcost22 said:
did you have someone else replace your screen? If so, and it might sound weird, they might have installed an LCD screen instead of OLED; and then modified the stock rom for that. You might not know, but OLED and LCD have very different power profiles, so when turning LCD on you can just blast it, meanwhile oled you need to slowly bring the power up. This is what might be causing your issues
Click to expand...
Click to collapse
Yeah, I had someone else install the screen for me. How would I go about checking if its LCD vs OLED? And do you know what would need to be modified in order to fix it if it is LCD?
zebinadams said:
Yeah, I had someone else install the screen for me. How would I go about checking if its LCD vs OLED? And do you know what would need to be modified in order to fix it if it is LCD?
Click to expand...
Click to collapse
You would need to remove the screen. Otherwise you can use something like AOD and check if the whole display lights up vs only the clock or whatever. On an LCD screen the whole display will light up a tiny bit vs complete black on OLED.
You would need to modifiy the dtb's and kernel, but it's something i would be able to do for you
marcost22 said:
You would need to remove the screen. Otherwise you can use something like AOD and check if the whole display lights up vs only the clock or whatever. On an LCD screen the whole display will light up a tiny bit vs complete black on OLED.
You would need to modifiy the dtb's and kernel, but it's something i would be able to do for you
Click to expand...
Click to collapse
It looks to me like OLED to me with only the clock lighting up. I could still take the screen off at some point to verify if needed.
Thanks for all of your help by the way
zebinadams said:
It looks to me like OLED to me with only the clock lighting up. I could still take the screen off at some point to verify if needed.
Thanks for all of your help by the way
Click to expand...
Click to collapse
I don't know if it's the reflection, but is there some bleed around the clock? Like is the dark areas lighter compared to the rest of the screen?
marcost22 said:
I don't know if it's the reflection, but is there some bleed around the clock? Like is the dark areas lighter compared to the rest of the screen?
Click to expand...
Click to collapse
I think it's just the reflection? Here's a shot of my Nexus 6p right beside it and I think they look basically the same.
The phone is used almost exclusively for kids videos so it's not the end of the world if I never get it fixed, but at the same time, it would alleviate some frustration when I'm helping my daughter turn a show on.
zebinadams said:
I think it's just the reflection? Here's a shot of my Nexus 6p right beside it and I think they look basically the same.
View attachment 5544389
The phone is used almost exclusively for kids videos so it's not the end of the world if I never get it fixed, but at the same time, it would alleviate some frustration when I'm helping my daughter turn a show on.
Click to expand...
Click to collapse
Yeah, to me it still looks significantly brighter around the clock
marcost22 said:
Yeah, to me it still looks significantly brighter around the clock
Click to expand...
Click to collapse
Ok, I'm willing to try modifying the ROM if that'll get rid of the stupid touch screen delay. How difficult is it? I know you said you would be willing to do it for me, but if it's not something that will persist through an update (I had been running AICP) and it's something that I could learn to do, all the better. If that's not realistic, that's fine as well.
zebinadams said:
Ok, I'm willing to try modifying the ROM if that'll get rid of the stupid touch screen delay. How difficult is it? I know you said you would be willing to do it for me, but if it's not something that will persist through an update (I had been running AICP) and it's something that I could learn to do, all the better. If that's not realistic, that's fine as well.
Click to expand...
Click to collapse
[REFERENCE] How to compile an Android kernel
Introduction Hello everyone, I will be going over how to compile a kernel from beginning to end! Prerequisites: A Linux environment (preferably 64-bit) Knowledge of how to navigate the command line Common sense A learning spirit, there will be...
forum.xda-developers.com
Is a great guide, you'd need to follow the clang guide tho, as our kernel IS clang-compiled, and i recommend repacking the boot.img
You'd need to change this line
kernel_motorola_msm8953/msm8953-albus.dtsi at 7befedacd91b84ed737b691671c088c89e394f66 ยท AICP/kernel_motorola_msm8953
Contribute to AICP/kernel_motorola_msm8953 development by creating an account on GitHub.
github.com
In your source to be
qpnp,qpnp-labibb-mode = "lcd";
If i'm right, after doing that and flashing it the issue will be fixed. Otherwise when you try to turn on the display it will cause a kernel panic
You would need to reflash this boot.img after every update, and redownload sources everytime i do something to kernel.