I am using CM7 and have auto-brightness enabled, and my screen brightness is often Max when i unlock the phone, even in the dark!
I dindt have this problem in oxygen rom, I did experience a similar problem in redux.
anyone experienced this or have a fix?
I've had the same issue using Redux ROMs; I think it is a problem with Gingerbread, as I have never heard of anything like it with FroYo or Eclair ROMs. No fix so far.
in oxygen its awesome tho.....really good autobrightness.
:S
Related
Using the unlock button doesn't always make my screen show up. Yet, the lights for the four buttons at the bottom of the screen. Sometimes, the screen even comes up but it keeps flickering.
Is this a known issue?
LGS1231 said:
Using the unlock button doesn't always make my screen show up. Yet, the lights for the four buttons at the bottom of the screen. Sometimes, the screen even comes up but it keeps flickering.
Is this a known issue?
Click to expand...
Click to collapse
Please read the posts in the Gingervillain thread. Are you OCing?
Going through what I can of the 50something pages of the thread. And yes, I am overclocked.
Props for trying man, everybody appreciates that.
Um okay, that actually might be the problem... What are you OC at? Are you using the screen on/off animations? Are you using SetCPU?
Try to take your OC down a notch, one step at a time, and try switching the screen on and off each time to see how much you can OC and still have the screen functioning normally.
So flashing the CM7 Gingervillain ROM, there was already a kernal built in but I only maxed it out at 1401mhz. Yes, I am using SetCPU and I'm also using the custom profiles.
I'm pretty sure that 1401mhz is at a stable level because 1497mhz was even tested to be pretty stable.
I see that you are running the same ROM, but since you haven't mentioned having a similar issue, I assume you don't have this issue? I'm just scared that one day the screen won't be turning on at all.
I am currently not OC'd, since I personally don't feel the need to be. But as you can read in the other thread, overclocking has provided screen problems for tons of people. There is no border that says "Okay now your screen's gonna start acting freaky", it differs for almost everyone.
I tested it myself a while ago: I had no problems up to about 1,2 GHz, but when I mine to 1,4 or higher I had the same issues.
But like I said, it all depends, there are people who are OCing at 1,5 and have no complaints..
Overclock to 1.2 area and let us know what's up
Sent from my HTC Vision using XDA App
After originally sending Tillus a PM as he had a similar issue with another ROM I thought I had better post here.
I have tried Oxygen, CM7 and Redux but I get this problem with all of them. Everything runs fine for a few days and then I go to unlock my phone and the screen stays blank. The keys light up but the screen stays just blank. Tried Back-Trackball-Vol down (as suggested in post linked to in PM below) but it didn't work. I then have to take out the battery and restart.
Once it starts happening the gaps between it happening get smaller and smaller. It has happened 4 or 5 times today alone.
First time, on Oxygen, my phone eventually wouldn't turn on any more and I had to get HTC to fix it under warranty.
Then I tried Redux where it happened after a few days. Someone on here suggested I look at the CPU settings. I did and saw that Redux had a power save mode, so I tried that and it seemed to work but after a few more days the same thing happened. Although this was after a reboot so perhaps the phone didn't retain power save mode afterwards.
On Sunday I loaded CM7. Worked for about 24 hours before the blank screens started.
Running ONDEMAND governor, Min 245 Mhz, Max 998 Mhz.
Any ideas?
Here is the PM I sent to Tillus for info:
Tillus said:
d10brp said:
Tillus,
Hope you don't mind me sending you a PM. I noticed you had the same issue as me (screen not turning on from lock screen http://forum.xda-developers.com/showthread.php?p=9652281#post9652281). Did you ever find a permanent solution? I'm getting this issue with Oxygen, Redux and CM7.
Thanks
Alan
Click to expand...
Click to collapse
Hi,
uhm, I think this was a specific Auraxtsense issue which was resolved eventually. I never experienced this fault again - neither in a later auraxtsense version nor in oxygen (2.0.3) which I am using now.
Are you overclocking your cpu? Maybe you set the screen-off frequency too low? Or are you using a undervolt-kernel with very low settings, especially in low cpu frequencies?
As I said, I haven't experienced this issue for a while now.
Click to expand...
Click to collapse
Did you try keeping the power button pressed for a few seconds? I know, it sounds silly
Are you sure you don't have this problem on a 2.2 rom? I don't see you mentioning it in your post. Only that you have this issue with 2.3 roms.
What kernel do you use? Try a SVS kernel, don't use a HAVS kernels for now.
Also are you sure you tried the latest version for let's say Oxygen? From the oxygen changelog:
v2.0.3
Fixed font bug introduced in previous version
Fixed pmem exhaustion *
* The pmem exhaustion was causing the so called 'black screens'
at random intervals
Click to expand...
Click to collapse
I'm fairly new to this so I have only tried 2.3 ROMs since rooting. Obviously phone has been running official sense just fine on both 2.1 and 2.2 for about a year.
Also, apologies for this, but I don't know what the kernal is. Just followed the noob video tutorial. Is it Alpharev?
Haven't tried Oxygen since RC7 so I might try it out.
Seems to be memory related as just after I posted, something slightly different happened, I pressed the lock button and the lock screen appeared but then froze. After a couple of minutes the screen eventually locked again with a very slow jerky animation. So I have just removed a couple of apps that seem to be running all of the time, App protector pro and StumbleUpon. No crashes since then (2 hours).
Sent from my HTC Desire using XDA App
So that worked for about 2 days. Now thinking maybe it is the SD card. Ordered a new one.
Using the latest version of MIUI-XJ a2sd+ and for some reason after about a week of use, 'it' unchecks vibrate when in silent mode. Very annoying! I can change it back, but 'it' just changes it again...weird?
The only thing i can think of having changed here would be using the tiamat kernel. So i'm going to use the cyanogen kernel and see if it continues..but in the mean time, does anyone have any idea why this is happening? Its ruining my MIUI/Desire experience and having only recently upgraded from my hero to a 2nd hand desire, this is making me quite 'upset', for want of a better word.
Oh and I really don't know if this would make a difference, but sometimes when using sense roms the haptic feedback on the htc-ime turns off for a short while...could this be something wrong with the hardware?
Thanks
So, reverting to the stock cyanogen kernel didn't fix it..so its nothing to do with tiamat, has no one else experienced this?
I'm working around it by having it on a very low volume...
Sent from my HTC Desire using XDA App
Hey guys,
something I noticed about FXP117 (CM7) is that it seems to miss the auto-backlight function/button/options in the settings. Something else I noticed, when I recover from lockscreen the screen seems darker than before, I'd say darker than the minimum selected in the options.
Is there any fix for it?
I've got no auto-backlight functions/settings/buttons what so ever.
thanks in advice
I also noticed that setting the brightness via swiping over statusbar does not work =/
I cant find auto brighness setting in ICS ...what I must do?
well I think it is a known problem in CM7 for ARC.
That the reason I remove CM7, waiting for this correction
Hi everyone..
Did anyone notice that the samsung ROM and ROM based on it has a better vibration intensity and it feels better than the on in AOSP based ROM which have vibration provided by CM10.1
Anyone has any idea? Anyone know a system file that can do the trick? Anything that helps in that?
Sent from my GT-N7100
I have a related but different issue - the vibrate works fine with the screen on, but stutters and becomes incredibly weak when the phone is locked and the screen is off. Any ideas?
In my rom (yours may be different) there's settings>Advanced>Haptic>Vibration intensity - choose 100% and it's noticeably better than stock...but all intensities have the same problem when the screen is off