Im running a T989, rooted, with the Blu|Ray ROM from M&S. Whenever I power off the phone from the menu, the touch lights stay lit until I do a battery pull.
Does anybody have a solution or answer as to why they do this?
Never heard of that problem, u try doing a search in the ROM thread? Might be an easy fix or something
Edit: Did a search in the ROM thread, possibly try a different kernel if this is the same problem you are experiencing .. you might also check the kernel thread that the ROM uses .. check your touch light duration setting as well?
http://forum.xda-developers.com/showpost.php?p=23895098&postcount=2899
Sound weird. If you haven't seen anyone else with this problem I would recommend you install the rom again.
Hope I helped you out!
Its an issue with faux's new 10m kernel version. I also have an issue with the kernel and my hardware lights acting weird. Flash another kernel and all should be well.
Sent from my SGH-T989
Related
Hi,
I flashed E2's WM6.5 rom which is based on AT&T's stock rom. Everything is fine except that sometimes, after I turn off the screen (by using the power button on the top), I can't turn it on anymore unless I unplug the battery. Is there any way to solve this problem?
Thanks
I had this problem with EnergyROM I believe. I couldn't figure it out. I'm currently using RRE and it doesn't have the problem. No clue what causes it and whenever I posted I was completely ignored.
can you please tell me the version of your rom or give me the link to the rom you are using now?
By the way, if I want to use the rom you are using now, do I need to do anything else for the keyboard? (I heard that I have to do something with the key mapping)
Thank you very much
This one
http://forum.xda-developers.com/showthread.php?t=576957
This is pre-setup for AT&T so you should be good to go.
Hi. I am experiencing an annoying issue.
The problem exists in both CoreDroid and CM7 with battery drain fix kernel, but I am not sure if that's a software problem.
Every time I boot up the phone, my g-sensor works very well, but, when I turn off the screen and turn back on, the sensor died. Just "halted", the values just being constant.
It seems the accelometer failed to "wake up" after turning off the screen.
Anyone knows why?
Thanks in advance.
Sent via psychic transmittion.
I've had g-sensor problems on all kernels based on the latest HTC kernel source.
Can't say for sure but I think it's something to do with the BMA150 rotation driver.
Going to back to a kernel based on old HTC source and all problems are gone.
Yep, I flashed another kernel and the problem is solved. DEV should have a look on the sensor driver. The kernel with problem seems failed to turn the sensor on again.
Sent via psychic transmittion.
What kernel did you try instead?
I think the devs know about the bug, but not every user is affected by it so I'm not sure if it's a priority to fix it.
I flashed "[CM7]Performance Enhanced...."kernel by hrkfdn.
Then the problem is gone. The stock kernel from CM7 is fine too.
Sent via psychic transmittion.
I apologize if there is any easy fix for this or if there's already a thread, but I just recently started having this issue for about a week. Sometimes, when I turn on the screen it will quickly light up to the lock screen, but then turn blank right after; before I even get a chance to unlock the phone. The capacative buttons will completely stay light up and when I press them they vibrate so I assume the screen is still active.
Is this a common issue and is there an easy fix? I'm running the latest CM7 nightly build 258. I don't think that's the issue though because I just upgraded it today and before I hadn't upgraded the Nighly Build ROM in a couple weeks. I upgraded it today just to see if there was something wrong with that build.
Has anyone else experienced this?
Restore your previous ROM save
graymonkey44 said:
I apologize if there is any easy fix for this or if there's already a thread, but I just recently started having this issue for about a week. Sometimes, when I turn on the screen it will quickly light up to the lock screen, but then turn blank right after; before I even get a chance to unlock the phone. The capacative buttons will completely stay light up and when I press them they vibrate so I assume the screen is still active.
Is this a common issue and is there an easy fix? I'm running the latest CM7 nightly build 258. I don't think that's the issue though because I just upgraded it today and before I hadn't upgraded the Nighly Build ROM in a couple weeks. I upgraded it today just to see if there was something wrong with that build.
Has anyone else experienced this?
Click to expand...
Click to collapse
Are you using a custom kernel. If so are you under / overclocking or over / undervolting?
Nope. I'm running whatever kernel comes with the ROM and no undervolting or overclocking either.
Anyone....?
Have you done a restore?
I would try wiping dalvik-cache and the cache partition. If that dosent work i would wipe everything and do a fresh install of a different rom to determine weather it is rom related or hardware related.
Can anybody help me. For whatever reason when my phone is charging randomly when i pull it off the charger the screen wont come on. The backlight comes on. the hardware keys light up. but no ones home. i have to do a battery pull to fix it. It has happened thru blackout, codefire, and jellytime so I dont know that it is a rom issue. But im not overclocked. Im havent changed the governor, just running straight up jellytime 29 right now. Please anyhelp would be appreciated. this happens more often than not.
hotrod60 said:
Can anybody help me. For whatever reason when my phone is charging randomly when i pull it off the charger the screen wont come on. The backlight comes on. the hardware keys light up. but no ones home. i have to do a battery pull to fix it. It has happened thru blackout, codefire, and jellytime so I dont know that it is a rom issue. But im not overclocked. Im havent changed the governor, just running straight up jellytime 29 right now. Please anyhelp would be appreciated. this happens more often than not.
Click to expand...
Click to collapse
That sounds more like a hardware issue than a software issue. Have you tried another battery? Also, please don't crosspost: http://forum.xda-developers.com/showthread.php?p=35663637.
bananagranola said:
That sounds more like a hardware issue than a software issue. Have you tried another battery? Also, please don't crosspost: http://forum.xda-developers.com/showthread.php?p=35663637.
Click to expand...
Click to collapse
Why not? Im running a dhd rom on an inspire 4g. I got great helpful answers from both posts. Maybe I missed one of the rules. Or maybe were just making them up as we go.
http://forum.xda-developers.com/announcement.php?a=81:
5. Post a message only once.
Oh well. I tried to help and you were rude. Good luck to you.
Does anyone else have problems with their screen just randomly turning off? I will be using the phone with my finger on the screen and the screen will go off. When this happens the phone doesn't lock, I can hit the volume button to turn it back on. I haven't been able to narrow the behavior down to an app. I have done a full wipe of system data and cache and only flashed a rom with gapps and it will still happen before I even restore anything other than Google login.
My phone hasn't been dropped or suffered any damage other than a small scratch on the screen. The buttons don't stick and seem to function perfectly. Never spilled anything on the phone either.
Anyone have any ideas about how to diagnose or someone that may have had the same issue?
Sent from my Galaxy Nexus
Happened to me when running a xylon ROM a week or so ago. I did a full wipe, sdcard and all, went back to stock then flashed a different ROM.
Which roms did it happen to you on?
Scent from my bud
I'm worried that it is possibly a hardware issue because it seems to happen on any rom that I flash. I just bought a mako yesterday and am looking to sell this phone soon and really hope their is nothing wrong with this phone. It might also be kernel related also because the dual boot kernels don't seem to be very stable yet.
Sent from my Galaxy Nexus
Don't seem to be encountering the issue on latest cm stable rom with latest lean kernel 6.4. Not sure what was causing the problem before, but it seems to have resolved.
Sent from my Galaxy Nexus
eqjunkie829 said:
Don't seem to be encountering the issue on latest cm stable rom with latest lean kernel 6.4. Not sure what was causing the problem before, but it seems to have resolved.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
It was probably the kernel!
I also use LK but when I used AK I had that issue and it was just me, other people didn't have it
The phone should be fine