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
Related
Hello,after replacing the display (by myself) , I' m not able to adjust the brightness of my display. It's stuck on the lowest level. Things I've tried;
- Called with HTC
- Performed hard reset
- Set the brightness to "auto"
- To adjust it with a brightness widget on my homescreen
- Replaced it with another display
- And of course digging through XDA
Specs;
- Desire Z 2.3.3,sense 2.1,unrooted
When I try to adjust it to the max.level it does not give an error. It just stays on the lowest level.
Is there anyone with the same problem or better,has a solution?
Many thanks in advance!
Can't adjust brightness either...kinda sucks
I am also having this issue and would appreciate any insight.
Did you guys do the work yourselves?
Yes,together with a video on "repair universe" I changed the display by myself (twice). Still having the same problem.
Anyone
Brightness stuck on highest setting
I also have this same problem. I just replaced the lcd display myself yesterday on my G2 with the help of the repair universe video. My display brightness is stuck on the highest level. When I try to adjust the brightness, only the buttons on the bottom of my screen (home, menu, back, search) change brightness but not the display.
I'm currently running ILWT CM7 297.
I'm going to try re-flashing my radio and then wiping and flashing a new ROM.
If anyone knows how to fix this please help!
I suspect it is hardware related such as the ribbon cable or screen is missing a lead for the dimming function. Can't tell from here though sorry.
killj0y said:
I suspect it is hardware related such as the ribbon cable or screen is missing a lead for the dimming function. Can't tell from here though sorry.
Click to expand...
Click to collapse
I tend to second this opinion from killj0y.
Have you tried making sure the ribbon cables are tight and secure? Sounds like the ribbon cable from the screen may be loose.
beefynick said:
I tend to second this opinion from killj0y.
Have you tried making sure the ribbon cables are tight and secure? Sounds like the ribbon cable from the screen may be loose.
Click to expand...
Click to collapse
Also is it the original ribbon?
Any updates
Has anyone figured out the answer to this? I just replaced the LCD from RepairsUniverse.com as well and the same thing. The brightness is low and won't change at all. Everything was fine before and RepairsUniverse.com says it's the motherboard. If the motherboard was fine before and all of us are having pretty much the same problem and some (or all?) of us got the replacement from RepairsUniverse.com, does anyone else smell a rat?
I know nothing of this company but depending on you screen problem, I wouldn't assume your mb is perfectly fine.
Sent from my HTC Desire Z using Tapatalk
Mine too
Has anyone fixed this problem? I have the exact symptoms, this is the second one I've tried, could it be because the lcd isnt oem? Please help
Hi. Are there any updates to this proble. I recently had the screen replaced on my Desire S and now it is stuck on the lowest brightness settings. Change any of the brightness controls does nothing. I took it back to the shop and they tried another screen, but still have the same problem. The motherboard was also replaced and the problem was there, but reversed...!? The screen was then stuck on full brightness...
Back to the original motherboard and the brightness is back stuck on lowest brightness setting....
Unrooted, Stock ROM
I installed cm9 after using cm7 and cant get the four buttons on the phone to light up. They are accessible but not illuminated. has anyone else encountered this problem.
Also I was wondering if the Cm7 uses more battery than cm9
You have to use auto brightness.
cm9 illumination
If you mean display auto brightness ok but when I'm outside I can't see the screen...guess ibhave to toggle back and forth. I had switched back to cm7. In your opinion is 9 worth changing to. It seems like in 7 everything is working pretty well.
Thank you for the reply
pmpic said:
I installed cm9 after using cm7 and cant get the four buttons on the phone to light up. They are accessible but not illuminated. has anyone else encountered this problem.
Also I was wondering if the Cm7 uses more battery than cm9
Click to expand...
Click to collapse
Toggling auto brightness on and off solves it. Just tinker with it..
Sent from my Incredible 2 using xda premium
cm9 illumination
Thank you....I appreciate it
Menu keys...
Ive been using the dinc2 since last July and I got used to the buttons to the point that I noticed they didn't light up, but until I saw this post, I never considered it a "problem". Since I knew where they were and didn't need to see them to use them. If they ever do "fix" this issue I hope they allow for a settings option to keep them turned off. I actually enjoy them off, in my mind its just one more security feature. I know when my wife tries to use my phone she needs to see them, and since recently rooting to CM9 I don't want her bricking my phone. Because of the unlit buttons she has stopped using my phone (she uses some cheap AT&T phone, refuses to switch to Verizon). Just throwing my opinion in the mix. Thanks for the post as well I wasn't sure it was intentional or not.
atomwes said:
Ive been using the dinc2 since last July and I got used to the buttons to the point that I noticed they didn't light up, but until I saw this post, I never considered it a "problem". Since I knew where they were and didn't need to see them to use them. If they ever do "fix" this issue I hope they allow for a settings option to keep them turned off. I actually enjoy them off, in my mind its just one more security feature. I know when my wife tries to use my phone she needs to see them, and since recently rooting to CM9 I don't want her bricking my phone. Because of the unlit buttons she has stopped using my phone (she uses some cheap AT&T phone, refuses to switch to Verizon). Just throwing my opinion in the mix. Thanks for the post as well I wasn't sure it was intentional or not.
Click to expand...
Click to collapse
I believe in the advanced brightness settings under CMSettings you can do just that. Whenever I run a CM rom, I always go to the brightness settings under edit Other Levels and set all the softkey values on the far right column to 255 so they're always the same brightness and look nice. I like the sheen they have, but I can only see it when they're close to full brightness.
If you did the opposite, set all the values to 0 and then click Save and Apply Values at the top of that screen, they should, theoretically, never turn on.
Thank you ....as I am new to a rooted phone and this forum I didn't know those adjustments were available...learn something new everyday ......
Does cm9 drain the battery alot quicker or is it unnoticeable
pmpic said:
Thank you ....as I am new to a rooted phone and this forum I didn't know those adjustments were available...learn something new everyday ......
Does cm9 drain the battery alot quicker or is it unnoticeable
Click to expand...
Click to collapse
Unfortunately, I can't answer that question for you, as my phone doesn't like our ICS builds. Until we get a leaked official kernel and some source, I'm SOL.
RegnierD said:
I believe in the advanced brightness settings under CMSettings you can do just that. Whenever I run a CM rom, I always go to the brightness settings under edit Other Levels and set all the softkey values on the far right column to 255 so they're always the same brightness and look nice. I like the sheen they have, but I can only see it when they're close to full brightness.
If you did the opposite, set all the values to 0 and then click Save and Apply Values at the top of that screen, they should, theoretically, never turn on.
Click to expand...
Click to collapse
Where exactly are these settings? Running CM7 with the same problem as the OP and can't find it anywhere. Edit: found the settings and putting them all at 255 didn't do anything. Any other ideas?
Hey all,
I experienced something a few mintues ago. I installed a new rom, Blissdroid. I 'discovered' that the backlight of the touch input (under the screen) was reacting dynamicly to sunlight. It went off in full sun. I couldn't find a setting to let it lighten up all the time.
I went back to Virtuous Unity, 2.35. It seems like the same thing is happening. I don't know if it's just normal (and I never discovered it before) or is there a setting I have to change (because I can't find one)?
Someone who can help me?
Thanks!
Settings>Display>Brightness and turn off automatic brightness and set it to a value manually see if that works for you.
dstylazz said:
Settings>Display>Brightness and turn off automatic brightness and set it to a value manually see if that works for you.
Click to expand...
Click to collapse
I tried that, didn't work.
For you it is always lighten up, even if you are outsise/inside where it is really bright? When I go outside, full sun, those 4 touch inputs will stop shine. It seems there is something wrong with my DHD? Or Am I mistaken? Someone who can confirm it is always lighten up?
Nahsen said:
I tried that, didn't work.
For you it is always lighten up, even if you are outsise/inside where it is really bright? When I go outside, full sun, those 4 touch inputs will stop shine. It seems there is something wrong with my DHD? Or Am I mistaken? Someone who can confirm it is always lighten up?
Click to expand...
Click to collapse
When inside those buttons will be on. When you go outside they will turn off. They don't have a setting to turn that off
Sent from my Desire HD using XDA
trh1341 said:
When inside those buttons will be on. When you go outside they will turn off. They don't have a setting to turn that off
Sent from my Desire HD using XDA
Click to expand...
Click to collapse
Oh, so it is just a normal feature of DHD? Weird that I just discovered that yesterday
rcmix 4.0 and roms that use rctweaks have settings for this. alternatively you can set it to your exact preference if you edit framework-res according to this:
http://forum.xda-developers.com/showthread.php?t=1034743&highlight=systemui+apk
the link is manly aimed at tweaking your autobrightness, but it has info on butons too
Thank you. I only feared a problem, caused by changing ROM, as I never saw that before. I Thought those inputs were always lighten up, in every dark/bright situation.
depends on rom authors preference i suppose
if you are using sense 3.5 runnymede port, you can also flash tweaks as addon. some very nice features in there
Thank you all. I'm not great in flashing ROMs, certainly nog all those tweaks. I tried Virtuous Affinity and Blissdroid, but in both I heard a pop sound after playing music, sound, ringtone,... It seemed like I was not alone.
So I went back to Virtuous Unity 2.35, which doesn't give me any problem, except for a random bootloop from time to time (for example after playing Angry birds and once just after sending a message) what I can fix by replacing the battery. This happens 1 time in 3 months or so.
I just don't want to brick my phone, so I don't experiment much. Maybe one day, when I've got a new phone, I can use my DHD to experiment more.
Hi Guys!~
Hope all is well !!
... recently I came across my rooted android 11 Pixel 3XL got a screen flashes with bright home screen background during the screen turning off and entering ambient display mode.
I try my best to find a solution but haven't found one yet.
I have tried to reflash to stock, also doesn't fix the problems.
... the only solution I found at this moment is to get android 12 beta which the transition animation from turning off the screen to the wake up of ambient display is totally different and I still prefer to stay with rooted android 11.
Your browser is not able to display this video.
Sounds like a hardware failure, display or mobo.
blackhawk said:
Sounds like a hardware failure, display or mobo.
Click to expand...
Click to collapse
It only happens when the screen turning off from home screen or app.
Trying to shoot a vid to show the issue now.
haritvii said:
It only happens when the screen turning off from home screen or app.
Trying to shoot a vid to show the issue now.
Click to expand...
Click to collapse
If you tried multiple roms especially the stock* one unless it's something you loaded after the flash, it's got to be hardware related. It's possible the non stock rom blew out some hardware too.
Try setting brightness to manual.
A rework around may be the only viable solution.
You ever wonder what happens when one or two of the billions of semiconductor junctions/resistors/caps fails in the chipset or display? You might be looking at an example
It could be a loose connection, or a faulty ribbon cable/connector, a subassembly maybe even battery (if so there be more symptoms).
*unless a known issue in this device.
blackhawk said:
Sounds like a hardware failure, display or mobo.
Click to expand...
Click to collapse
blackhawk said:
If you tried multiple roms especially the stock* one unless it's something you loaded after the flash, it's got to be hardware related. It's possible the non stock rom blew out some hardware too.
Try setting brightness to manual.
A rework around may be the only viable solution.
You ever wonder what happens when one or two of the billions of semiconductor junctions/resistors/caps fails in the chipset or display? You might be looking at an example
It could be a loose connection, or a faulty ribbon cable/connector, a subassembly maybe even battery (if so there be more symptoms).
*unless a known issue in this device.
Click to expand...
Click to collapse
Thank you so much, now I got a great reason to get a new Pixel 6 then
haritvii said:
Thank you so much, now I got a great reason to get a new Pixel 6 then
Click to expand...
Click to collapse
I could be wrong... and even if it is hardware that doesn't mean a work around doesn't exist to make it usable.
Play with it, Androids wuv attention
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.