AOSP auto-dimming issue. - Droid Incredible Q&A, Help & Troubleshooting

I've tried both new releases of Evervolv and WeDoDroid Gingerbread roms and find that my screen will not respond to auto-dim when unit is turned off then on (not reboot).
I've had this happen with a few other AOSP roms but not Sense roms.
Currently, I'm using Ruby 2.0 and do not have this issue so I am wondering if this is a build issue.
So here are my questions;
Is this a beta build issue?
Is anyone else having this issue with GB? Roms?
Sent from my ADR6300 using XDA App

I don't know about auto dimming, but I have mine set at a specific level and every so often mine will come out of lock with the screen on full brightness. I think this may be a driver issue in Gingerbread, at the moment.

Related

[Q] Most Stable Rom?

I've tried almost every ROM on the development page but could not find any ROM that is stable (I.E. GPS not working, or Camera issues, etc.) Is there any ROM that anyone here recommends that is most stable?
Probably Villision 1.0
Coak5 said:
I've tried almost every ROM on the development page but could not find any ROM that is stable (I.E. GPS not working, or Camera issues, etc.) Is there any ROM that anyone here recommends that is most stable?
Click to expand...
Click to collapse
How about Cyanogenmod 6.1.1? Granted its Froyo but its Stable. Other then that just root the stock rom and get the junk off of it. I did those for a while. Now I'm on Cyanogen Nightly 31 having no issues. I have been lucky being able to fix the GPS issues.
The latest Virtuous is pretty stable for me! and everything works
I've never once had an issue with cyanogenmod.. just flashed rc4. Idk why everyone complains about gps, my works flawlessly.. id say cm6 would be the most stable thou as someone already said. But it is froyo.
Sent from my HTC Vision using XDA App
shady503403 said:
I've never once had an issue with cyanogenmod.. just flashed rc4. Idk why everyone complains about gps, my works flawlessly.. id say cm6 would be the most stable thou as someone already said. But it is froyo.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
So you're saying your phone isn't experiencing the Gmail margin issue that's been present post CM7-RC2?
http://forum.xda-developers.com/showthread.php?t=1001996
I think miui is the most stable, to be honest. Those folks in china know their stuff. Haven't had a single damn thing force close on me with that rom. No joke. Battery life is just magical too.
Sent from my HTC Vision using XDA Premium App
Go for the ROM with the most replies.
Any ROM will have bugs. The older and more popular it is, the more likely, the bugs will have been worked out. Go for older, stable roms instead of newer, unstable ones.
shady503403 said:
I've never once had an issue with cyanogenmod.. just flashed rc4. Idk why everyone complains about gps, my works flawlessly.
Click to expand...
Click to collapse
Seems to me the GPS issue on CM7 may be location dependent, since some have the issue, others don't, and flashing various different radios seems to solve the issue for many. Since I travel a lot for work, it gives me less than 100% confidence that the GPS will work when I really need it to.
There is also the persistent video camera landscape/portrait playback bug (but I haven't tried the latest nightlies or RC4). Plus, the camera button is laggy on CM7. So I'm onto Virtuous, but ADW EX as launcher (Sense is sloooow). Virtuous is built off the stock Desire Z ROM, so its very stable. Off the top of my head, the only common bug I know of is wake issues depending on kernel and clocking, but those are easily solved by SetCPU profiles, or using the Standard Virtuous kernel. I haven't tried a great many ROMs, but Virtuous is working well for me so far.
Gingerbread ROMs are all ports from other phones, since a native GB "official" ROM has not been released for the Vision yet. Until that happens, the Froyo builds are going to be less buggy than the GB ones.

[Q]Brightness stuck at 100%

Hello all thanks for the help in advance!!
So recently I've been using MikFroyo Rom but decided to try out some gingerbread roms and over the last 3 days I've tried out about 6 but just today I've tried out Calkulin's EViO 3v1.0 beta 2 with the enable all buttons and his splash screen zips... After that I can't get my screen to dim at all auto brightness or custom moving it to the lowest settings doesn't do anything I've tried flashing into roms I know dim and adjust correctly but its stuck to 100% on ... I haven't tried a froyo Rom yet I might try that now but has anyone ran into this being stuck on 100% brightness on all roms? How might I fix this my battery is deing lol
Thanks again
Sent from my PC36100 using XDA App
Flash a different kernel. That will usually solve the brightness big associated with gingersense roms.
posting & replying via the XDA Premium app.
Somebody correct me if I'm wrong, but....
Calkulin and other Gingerbread Sense ROMs based off of the latest Gingerbread leak for the Evo have several bugs. (stock kernel issue)
One of them would be the brightness issue, staying at 100% for certain screens (Nova screens, if I remember correctly....)
You can try to flash one of Netarchy's kernels, which fixes the screen brightness issue but borks the camera I think. So, pick your poison
tropicalbrit said:
Calkulin and other Gingerbread Sense ROMs based off of the latest Gingerbread leak for the Evo have several bugs. (stock kernel issue)
One of them would be the brightness issue, staying at 100% for certain screens (Nova screens, if I remember correctly....)
You can try to flash one of Netarchy's kernels, which fixes the screen brightness issue but borks the camera I think. So, pick your poison
Click to expand...
Click to collapse
You are correct switching Kernels will bork camera you get white screen but can still take pictures

screen wake up

whenever using aosp roms such as gingerbread decks or cm7 i will ocassionally get a black screen when trying to wake phone up/unlock. is there a fix for this or an aosp rom that doesnt do this that is similar? ive tried salvage mod and cant remember if it did it or not. it lags when turning on the screen.
i noticed tremendous wake lock issues with the latest RC of CM7. So bad that i couldn't use it. Is that the ROM you're currently using?
If so, have you tried switching to one of the more recent nightlies and checked the results.
i'm currently running the latest version of MIUI, which is based off of AOSP. I have had no wakelock issues with it at all.
im on decks 1.2.1 sorry for not mentioning it. it just happens with most aosp. yea ive tried miui and dont recall ever having that issue. might give it a shot this friday or something for the new release, thanks for the reply.

[ROM] JellyTime forgets input choice

I apologise in advance if this is in the wrong spot. I'm not able to post in the relevant topics in the Dev section.
I've tried both the AOKP and AOSP version of randomblame's JellyTime (as well as different beta versions of each) and on each version whenever I reboot Swiftkey 3 gets disabled.
This never happened when I was running IceColdSandwich, so I'm pretty sure it's a ROM issue. Is anyone else experiencing this/know of a fix?
Yes, happens to me too. It's a ROM issue. It'll be fixed in the next few betas, not to worry. Meanwhile, if that's holding you back from using JellyBean, you can try the unofficial CM10/AOKP nightlies. As of now, they're more complete than JellyTime and everything works. JellyTime will get there soon too, randomblame is busy with real life stuff now.
Edit: Problem occurring with latest CM10 nightly too (28/08).
Sent from my Desire HD using xda premium

[Q] Camera Flash bug in Custom ROMs

I have tried several ROMs and they all seem to have an issue with the camera. What happens is when you try to take a picture with the flash on, the phone will crash. At first I thought it was just an issue with the ROM itself until I tested it on others, and the same problem occured (Android 4.4.4 ROMs used with cyanogenmod, paranoid android, liquidsmooth, carbon). Am I doing something wrong? or is this something that was an issue already known?
Were you using the preinstalled aosp camera or Google camera?
Sent from my SGH-T989
I only saw that issue when battery was below 30 percent somewhere. Not above that though.
How old is your ROM? I seem to remember there were some camera issues with CM nightlies earlier this year.
I did and experimenting and found that open camera does not have this problem. It was featured on the xda portal a few days ago so it should be easy to find.
jrc2
Sent from my T-Mobile S2 using Tapatalk.

Categories

Resources