[Q] setcpu causing screen to dim. solutions?? - myTouch 3G Slide Q&A, Help & Troubleshooting

So basically I just rooted my phone and flashed to cyanogen mod 6.1 and I'm loving it. Thanks xda for the rooting and flashing process. I decided to go into overclocking my mytouch slide and everything seems to work perfect except for the fact when I turn off my screen and turn it back on the screen is at the dimmest setting it can get. I reset the brightness back to how I want it and then turn off the screen again and turn it on, and it reverts back to the dimmest setting. I booted up without having setcpu running and the screen settings stay the same after I turn the screen on and off. has anyone found or seen this before?? And if so, is there a solution to this problem??
Thanks

I've never heard of setCPU causing that problem. You may want to trouble shoot a bit more before pinning it on that. We need to knock some things off the list of possible culprits too.
What is the brightness set to, automatic?
Custom oc kernel (dumfuq's) or what's integrated into CM?
What are your clock settings in setCPU?
What governor are you using in setCPU?
Do you have profiles set, if so, what are they?
Have you messed with the light sensor or done any custom brightness tweaks (CM settings)?
You need to answer some of those first so we can narrow it down, you may have something set up wrong. There is also the issue of the phone not coming to full brightness when you try to catch it on the screen time out (screen is off - but not locked). That's fixed by locking it and unlocking.

Related

[Q] [Idea] Overclocked and have the "wake-up and screen stays black" problem?

[Q] [Idea] Overclocked and have the "wake-up and screen stays black" problem?
I'm running CM6.1 and using Pershoot's kernel, and running at 1.5ghz, on-demand. Probably once a day, I have the issue where a call will come in, or I'll press the power button, or I'll slide out the keyboard, and the screen will stay black (though the backlight for the soft-keys does come on).
I noticed that I can appear to interact with the screen still (answer a call by swiping where the answer slider is, even though I can't see it), which indicates that it's simply the backlight not being turned on.
For others that have the same problem, the next time it happens, try pressing your camera button to open the camera application. For me, the screen comes right up as soon as the application opens (the camera application sets your backlight to high while in it). Anyone else?
I'm going to take a look at the wakeup code this afternoon, I have an idea for a _hacky_ fix that can be done.
I also wanted to confirm - do others have the same problem if not overclocked?
I've been getting that a lot too before (more than once a day for 2 weeks) until I got desperate and wipe/reflashed CM6.1.1 and I haven't seen it in the last 3 days.
I don't know anything so maybe its coincidental. My OC settings are the same as before. The only difference this time was i wipe/factory reset before flashing CM6.1.1.
instead of flashing CM6.1.1 on top of CM6.1 which was what i did 3 weeks ago.
What does your setcpu profiles look like? Set a profile for when you turn the screen off to set the cpu to 245/245. Then set a new one at xxx/806 conservative (xxx being the freq you desire)
Test it out and let me know how it works out.
PanCubano,
Others have suspected that it has to do with the CPU being at high speed the split second before you wake the device, and I agree that it's likely the problem.
Unfortunately it's quite hard to prove that the problem has gone away.

automated brightness control

Hi there, just wanna mention that i did search the forum, but didn't find an answer, just to be clear on that.
So, yesterday i got a desire, switched from a wildfire which i had for 2 months, there is a bit more power and fun to be had with a desire.
But as with the wildfire, i noticed that the auto brightness function isn't doing so well.
If i get up at night and it's all black in my room, the screen is way to bright, i have to use the power control to bring it down, but the downside is that it disables the auto brightness.
Is there anything that let's you tell auto brightness, if it's pitch black, brightness should be this low and so forth?
I've rooted and flashed with leedroid.
I'm running LeeDroid and I don't know if it's recalibrated or what, but it's definitely better than with the stock ROM.
Edit: Just saw I didn't read your post well enough and you've got LeeDroid as well, so my answer is not too helpful... sorry...
The Cyanogen ROMs have settings to adjust brightness.
This was one of the things that annoyed me about the desire.....so much that I decided to fully root this thing and do things my way lol
So I removed the stock ROM, Radio, HBOOT and Recovery and flashed some custom ROMs and now automatic brightness works JUST FINE ^^
Edit: Does leedroid come with automatic brightness settings?...hav u checked under the Display settings? becuase most of the ROMs that support automatic brightness needs to have it enabled and setup to work properly
Evil_Cid said:
This was one of the things that annoyed me about the desire.....so much that I decided to fully root this thing and do things my way lol
So I removed the stock ROM, Radio, HBOOT and Recovery and flashed some custom ROMs and now automatic brightness works JUST FINE ^^
Edit: Does leedroid come with automatic brightness settings?...hav u checked under the Display settings? becuase most of the ROMs that support automatic brightness needs to have it enabled and setup to work properly
Click to expand...
Click to collapse
Well, yes leedroid has automatic brightness, but as i mentioned, it's still too bright at night, i want to tell auto brightness that if i does not detect any light, it should turn the brightness as low as possible and so forth.
Do you turn the brightness down with power control you disable auto brightness and have to manually enable it again.
Even tho there is only one sensor, instead of having a preset value for different amount of light detected, it could be smarter.
Ex. auto brightness is on, it's dark, you go into brightness and turn it further down, phone asks you if you are turning it down because you think it's too bright, you click yes, phone learns that you want lower brightness when it's very dark, you click no, phone does nothing because you had another reason for adjusting brightness.
The next time, phone remembers that you want low brightness when it's dark, so you don't have to do it again.

CM7 Stable - Autobrightness problem

I just installed CM7 stable version yesterday, everything goes smoothly except for the autobrightness function. Whenever I turn my screen on, the first time it always very dark, although perceivable but it's like the autobrightness is broken. Yet, when I immediately turn off the screen and turn on again, it's bright like nothing happens.
minhgurluver said:
I just installed CM7 stable version yesterday, everything goes smoothly expect for the autobrightness function. Whenever I turn my screen on, the first time it always very dark, although perceivable but it's like the autobrightness is broken. Yet, when I immediately turn off the screen and turn on again, it's bright like nothing happens.
Click to expand...
Click to collapse
try turning off "screen off animation" it will fix it. it a known bug.
please refer to this thread Numerical explanation of the CM7 automatic backlight settings
Byrong does a really good job explaining what the auto brightness settings does in CM7.
By default CM7 auto brightness doesn't work very well, you need to configure it to your liking using the options described in that thread.
Use the status switch toggle the autobrightness!

Help with brightness issue - S2 t989 running4.1.2

***Update***
The culprit was Lightflow. Had to deselect all "additional leds found". Me + google = victory.
Hello all, I'm hoping someone might know how to help me diagnose an issue I'm having with my brightness settings.
If I unselect "Auto" and set to max brightness, the screen gets nice and bright. But that's not a problem.
If I press the power button to turn the screen off, then press it again to turn the screen back on, the brightness quickly dims to a less bright value. All sliders, icons, settings etc. still register as being set at max brightness.
From what I can tell, the brightness is actually switching to the dimmest setting. The opposite of maximum brightness.
Any ideas? I'm new to logcatting, so might need some specific direction on the proper parameters to log.
T989 running Rushing's Lightspeed (4.1.2 base), and latest Tiberius 3.0.101 kernel. I've made some systemui xml tweaks for status bar and expanded status bar.
Let me know what other info I can provide.
Bump ... just realized the same thing is happening even when on auto brightness. Change the setting, all is good. Press power to turn screen off. Then press power to turn screen on, and within the first second, the brightness drops. Like something loads when waking the phone.
Any ideas where to start looking?

Not able to adjust backlight after last update?

Is anyone else having this issue? No matter what I do to adjust my settings, it remains full brightness.
Go to display settings , uncheck auto brightness , now u can adjust the brightness..... If not, reboot the device.
I noticed this myself but i am rooted , using a custom kernel and xposed with some modules so i wasn't really sure what's causing the problem. Didn't have the time yet to figure it out... Is your pixel c still stock?
Still stock. I can adjust brightness with auto brightness unchecked, but the lowest setting is incredibly bright still.
I did a reboot and after that it worked again like it should... , i just checked with mine and it's still working correctly ...

Categories

Resources