Seems I have another question, Does anyone else have this problem! My Screen never turns all the way off, its lite up from the bottom left corner, it happened when I was adjusting the setting for screen brightness & POW! LIGHT LEAKAGE I THINK IT'S CALLED
what room are you on?? i had that happen on synergy i just wiped dalvik and cache then reflashed the ROM it worked out.
I'm on Viper 1.21 and no matter what ROM I flash or what's wiped it won't stop! It's so screwed
Sent from my PG86100 using XDA App
Related
I am running BAMF Sense 3.0 RC3 (Imo's leanKernel running at Extreme with MR2), and I use WidgetLocker. Quite often, I will go to unlock my touch screen and my touching capabilities are not working - I can slide my slider, or do anything. I can hold down the power button to come up with the shutdown/restart options, but I cannot touch them to make it work. Sometimes if I wait a while it works again, or if I get another message/e-mail, but one time I had to pull the battery! I am not sure if this is a known issue or if maybe this is something with WidgetLocker, but does anyone know what I can do to fix this or have any suggestions? Any help would be appreciated! Thanks!
Bump - anyone else have this problem? Is it WidgetLocker, and maybe I need to make it no longer use RootHelper or something? When this happens (it currently is), only the power button works - all others do no effect, although they make a vibrate noise when pressed as if there are. After 10 minutes it will work again...)
Just a thought... Bump your min cpu setting to 368 and see if that helps.
Sent from my ADR6400L using XDA Premium App
Thanks, I did not think of that - I will change from Extreme to Normal (since Extreme undervolts it) and I will give that a try. Any other suggestions in case that does not work?
That's all I know man. I bet its a setting issue on the kernel.
Sent from my ADR6400L using XDA Premium App
You could always try switching to dream kernel 2.3.0 or 2.3.2, which are updated versions of the sense 3.0 stock kernel from das bamf. But I'm guessing that your min cpu setting is too low, especially if its undervolted. I have lag setting it to 245/368 with screen off, but its just laggy.
I tried changing settings on Imo's kernel, still no avail. His kernel gives me great battery life so I am trying to not switch to a different one; I was looking in Das BAMF toolkit and originally I had Sense Lock Screen off, which is when the lock screen froze, and when I turned it back on, I still had the lock screen froze but now sometimes the Sense one came into view, frozen. And by frozen, I mean the touch screen doesn't work - I can wake on with the volume keys and power button, but none of the bottom buttons work too. I am baffled... What could cause this?
Aup808 said:
I tried changing settings on Imo's kernel, still no avail. His kernel gives me great battery life so I am trying to not switch to a different one; I was looking in Das BAMF toolkit and originally I had Sense Lock Screen off, which is when the lock screen froze, and when I turned it back on, I still had the lock screen froze but now sometimes the Sense one came into view, frozen. And by frozen, I mean the touch screen doesn't work - I can wake on with the volume keys and power button, but none of the bottom buttons work too. I am baffled... What could cause this?
Click to expand...
Click to collapse
No idea, but the easiest solution is likely to wipe and flash again. For other lockscreen issues this has been the most successful solution.
Sent from my ADR6400L using XDA Premium App
Yeah, I was thinking about this... Considering I have Bamf 3.0 RC3, might just wipe and get RC4. I will let you guys know how I make out! Thanks for the suggestions!
Off topic question though... How do I edit the Swype dictionary?
Sent from my ADR6400L using XDA App
Aup808 said:
Yeah, I was thinking about this... Considering I have Bamf 3.0 RC3, might just wipe and get RC4. I will let you guys know how I make out! Thanks for the suggestions!
Off topic question though... How do I edit the Swype dictionary?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Don't forget to check out the preview of the rc5. It can be found on teambamf dot net. It is like rc4 but is very nice, especially with the new radio.
Sent from my ADR6400L using XDA Premium App
And as for swype, I think in options, by hitting that button on bottom right or through settings, there's a way to reset or tell it to not remember, but no way to edit I don't believe. There's a way to get it to ignore some words but its been so long I've forgotten.
Sent from my ADR6400L using XDA Premium App
I just recently did a nandroid restore of CM7 Beta coming from MIUI 4.0 Beta. I wiped the big 3 and then did the restore. No hiccups with the restore and everything is back to the way it was, but the screen timeout. I changed the settings for the screen to turn off after 15 seconds, but the screen stays on and never shuts off.
What can I do to make it look at the settings and abide by them?
eddieb1983 said:
I just recently did a nandroid restore of CM7 Beta coming from MIUI 4.0 Beta. I wiped the big 3 and then did the restore. No hiccups with the restore and everything is back to the way it was, but the screen timeout. I changed the settings for the screen to turn off after 15 seconds, but the screen stays on and never shuts off.
What can I do to make it look at the settings and abide by them?
Click to expand...
Click to collapse
Edit: While installing CM7 or MIUI, we flash then WIPE Data, Cache & Dalvik
Was your NANDroid before you played around adjusting things? If so, in Cyanogen settings you can adjust turn off and time out.
After countless SBF's I have come to realize that it only takes under 30 minutes to SBF back to 2.3.4, activate, ROOT, install BSR then Flash any ROM.... We are always better off with a clean slate... always.
Good luck, hope this helped :-D
Yes it was before I played with the settings. I think I'm just gonna have to SBC and start over. Ugh!!
Sent from my MB870 using XDA App
It won't hurt
Dee Ex Two - See Em Seven
Try entering recovery the patched one for CM7 and try wiping cache and dalvik cache first....
Dee Ex Two - See Em Seven
Pixelation said:
Try entering recovery the patched one for CM7 and try wiping cache and dalvik cache first....
Dee Ex Two - See Em Seven
Click to expand...
Click to collapse
Ok. I'll try that in the morning.
Sent from my MB870 using XDA App
I just sbf'd back to 2.3.4 and rooted and everything. Now I'm back on CM7 comfortably.
Sent from my MB870 using XDA App
Moon shadow posted the fix for screen timeout and security screen.
http://forum.xda-developers.com/showthread.php?t=1451904
My sbf always take like 30 minutes on the first step. Any easy to speed this up?
Sent from my MB870 using xda premium
I'm running the CM9 beta 0.2.0 by jokersax11 ([Ics] cm9 beta with camera CDMA/GSM/UMTS/HSDPA/WCDMA/roaming 2/22/12) and my capacitive touch buttons at the bottom of the screen*(Menu, Home, Back and Search) are not lighting up at all! I can't figure it out at all and I really need these buttons to light up, due to my recent switch from the LG Optimus S, and before that I had an AT&T HTC Inspire 4g (which have the home and menu buttons reversed). I use my phone alot at night and I desperately need to get this fixed! Is there something in the CM9 settings I'm overlooking? Or is there an app or mod that I could use to get control of them and get them working again? PLEASE HELP! I WOULD REALLY APPRECIATE ANY ADVICE OR ANY INFO ON HOW TO GET THESE BUTTONS TO LIGHT UP AGAIN! This is really frustrating!
Click the link below for the answer ...
http://forum.xda-developers.com/showthread.php?t=1526546
EDIT - Well that was fun. If you haven't figured it out, the link above goes to the other thread you started, with the same title, and the same body, in the same forum .... You should not create duplicate threads. For future reference best practice is create 1 thread and wait a minimum of 24 hours between bumps.
With that out of the way my actual advice is as follows, i dont believe the capacitive buttons are an issue with jokers CM build although i dont personally use it. This would indicate the answer lies in a) something you did b) something you didnt do c) something you installed
1. You can eliminate a and b without losing any info by going into your custom recovery and wiping cache and dalvik cache then doing a dirty flash on the rom (dirty flash = don't wipe data/factory). In this case there would be no reason to reflash gapps.
2. If that doesn't work, do a full wipe (data factory/system/dalvik) and reflash the ROM, then gapps. Be slow to in stall your apps and test the capicitive buttons frequently to ensure you haven't done anything to break them
Set the phone's brightness to Automatic.. Fixed..
People are so over dramatic sometimes lol.
Sent from my MB855 using Tapatalk
Thanks, that pointed me in the right direction. My auto brightness isn't working. I'm gonna do a "dirty flash" and see if that helps. Oh and btw,the second post was an accident and you can't delete your own thread.So, sorry about that.
eszumlas1985 said:
Thanks, that pointed me in the right direction. My auto brightness isn't working. I'm gonna do a "dirty flash" and see if that helps. Oh and btw,the second post was an accident and you can't delete your own thread.So, sorry about that.
Click to expand...
Click to collapse
Please come back and update the thread on if it works or not. Others may experience the same issue in the future and this thread could assist them.
Cheers!
i just now notices mine dont light up but o well my thumb pretty much know ware to push
Well, it's fixed. Don't know what the heck was going on but reflashed my CM9 & Google apps and voila my automatic brightness switch in settings started working again. No more problems and capacitive buttons work fine. Strange but at least it's fixed
Sent from my MB855 using xda premium
And sorry to anyone that needed a fix to this. I was involved in the tornado that hit Branson, Missouri and was unable to keep phone charged due to the power outage that lasted over a week, and had bigger things to worry about at the time, like getting shelter and food. But everything is ok now and hope this thread helps anyone that has this problem. Check to see if your automtic brightness switch is working under settings (mine wasn't working) So if it isn't working just reboot into recovery, wipe dalvik cache & /cache, and reflash your rom and gapps, then check in your settings to see if your automatic brightness is now working. If so your problem should be fixed and your capcitive buttons should now light up. It worked for me, hopefully it will work for you.
Sent from my MB855 using xda premium
eszumlas1985 said:
Check to see if your automtic brightness switch is working under settings (mine wasn't working) So if it isn't working just reboot into recovery, wipe dalvik cache & /cache, and reflash your rom and gapps, then check in your settings to see if your automatic brightness is now working. If so your problem should be fixed and your capcitive buttons should now light up. It worked for me, hopefully it will work for you.
Click to expand...
Click to collapse
Thanks man i just had to set the screen brightness to automatic and reboot once. It worked like a charm
I have a strange problem.
E.g. I installed carbon rom. Set it up. Rebooted an lost vibrations. Checked settings an "vibrate on touch" is selected. Haptic is enabled. All seem to be set up for vibrations but phone is not vibrating.
It happens only with AOSP roms. Stock roms are ok.
I also had this problem with slim bean but then clearing cache and dalvig was helping for a while.
I tried different kernels but still not vibrating.
Even in recovery it is not vibrating on touch.
Any one experienced something like this before and knows the fix?
If it's not vibrating in recovery when it normally does, it can't be a rom problem. Maybe its hardware and coincidence? Give the phone a tap o. The side. Perhaps the motor got stuck
Sent from my GT-I9300 using Tapatalk 2
Ok. So I've installed stock rom and vibration is back. Just flashed carbon again and after reboot vibration again is gone....
Where actually is it "stored"? Is it in rom itself or kernel?
And does it matter what I had before flashing AOSP (stock 4.1.2 or leaked 4.2.2)?
Sent from my GT-I9300 using xda premium
Hey,
Updated from 4.2 to 4.3 hoping it was a glitch with 4.2 but my screen brightness flickers up and down what appears to be about 5 levels consistently (very fast, resembles a flickering) whenever the display is on. The brightness control also doesn't work, it has no effect on the brightness levels, you can slide it from one side to the other with no actual change.
This has an ill affect of draining the battery about 1% a minute when the display is on.
Anyone have a similar problem or know how to fix this?
I have the auto brightness unchecked and when enabled there is no change either.
xclaw said:
Hey,
Updated from 4.2 to 4.3 hoping it was a glitch with 4.2 but my screen brightness flickers up and down what appears to be about 5 levels consistently (very fast, resembles a flickering) whenever the display is on. The brightness control also doesn't work, it has no effect on the brightness levels, you can slide it from one side to the other with no actual change.
This has an ill affect of draining the battery about 1% a minute when the display is on.
Anyone have a similar problem or know how to fix this?
I have the auto brightness unchecked and when enabled there is no change either.
Click to expand...
Click to collapse
When you flashed to 4.3 did you do a wipe? Have you tried a reset at any time? If you just updated without wipe it would have retained any previous settings or conflicts that may cause this.
Sent from my C6833 using XDA Premium 4 mobile app
I'll do a quick backup and then try a wipe to see if that clears it up. Thanks for the suggestion.
maybe you has to sent to service central but before just update again ,hope will fine
Did all the wipes and no go, called up Bell and have her going in for a RMA check. Can't wait to see what they say.
xclaw said:
Did all the wipes and no go, called up Bell and have her going in for a RMA check. Can't wait to see what they say.
Click to expand...
Click to collapse
Are you sure you flashed the device correctly and followed the procedures in LordManhattan's guide or [NUT]/blueether's posts?