[Q] Keyboard backlight not working rom related or hw issue? - Motorola Droid 3

My droid 3's keyboard backlight doesn't work, i tried it in full darkness too but nothing. Tried turning on and off autobrightness/custom light levels/reset/wipe everything but didn't help.
I'm on cm9 nightly 3/28.
Is this something rom/setting related or hw issue maybe?

Try flashing Gummy. If the problem persists, try flashing an earlier nightly. Hash said on twitter that he didn't get around to testing 3/28.

slayer621 said:
Try flashing Gummy. If the problem persists, try flashing an earlier nightly. Hash said on twitter that he didn't get around to testing 3/28.
Click to expand...
Click to collapse
okay i'll try and report back thanks

epik1 said:
okay i'll try and report back thanks
Click to expand...
Click to collapse
Also, I'm not sure if this works, but try setting the autobrightness levels with these settings http://forum.xda-developers.com/showpost.php?p=22637417&postcount=957

slayer621 said:
Also, I'm not sure if this works, but try setting the autobrightness levels with these settings http://forum.xda-developers.com/showpost.php?p=22637417&postcount=957
Click to expand...
Click to collapse
Installed gummy but still no backlight and tryed the settings you linked too but nothin'

epik1 said:
Installed gummy but still no backlight and tryed the settings you linked too but nothin'
Click to expand...
Click to collapse
with gummy... keyboard lights currently only work with the autobrightness display setting enabled
:EDIT: ooops didn't see your post a couple up til now. guess you already tried that.

yes i tryed it and i also went back to stock .890 and still nothing it really looks like hw fault but keys work only backlight don't :/
(EDIT: keys are also starting to act strange numeric 7,8,9 are only working when i touch the back where they keys are strange)
EDIT2: keys problem fixed, checked sensors with sensor test and light sensor is stuck and showing the same value in dark/light
and also the proxi sensor is not reacting to nothing so maybe the light sensor is causing the keyboard problem and the proxi causing the screen won't turn back after call

UPDATE!
Took the phone apart cleaned everything and pushed the keyboards ribbon cable in it was a bit loose and now the backlight works perfect! Hope it helps others who are suffering backlight issues that can't be fixed in the os

Related

Its practically impossible to write on my N1 ¬¬

Hi you guys, im writting because im a bit worried, its practically impossible to write on my N1, when i press a letter 3 other are random letters are pasted, and when i try to delete the enter button is pressed...
Im using Cyanogen mod RC3, im been facing this behavior since a long time ago but, once in a while, but lately it had been happening more often, i need to reboot and it start working again, but later it happens again...
Just throwing my 2 cents (which may not be correct), but I think you display input calibration (touch calibration) is a little off or your touch sensor is behaving weirdly... can you go to Dev Tools > Pointer Location and verify the touch points...
craigacgomez said:
Just throwing my 2 cents (which may not be correct), but I think you display input calibration (touch calibration) is a little off or your touch sensor is behaving weirdly... can you go to Dev Tools > Pointer Location and verify the touch points...
Click to expand...
Click to collapse
Thnx dude, its working just fine now... ill try this the next time it happens! Thnx
donchele said:
Thnx dude, its working just fine now... ill try this the next time it happens! Thnx
Click to expand...
Click to collapse
It's a common problem for the screen the N1 is using. Every once in a while (especially when it heats up), it will lose calibration.
It's annoying, but very easy to fix - just turn off the screen with a power button and turn it back on (not the phone, just the screen).
This fixes it every time.
craigacgomez said:
Just throwing my 2 cents (which may not be correct), but I think you display input calibration (touch calibration) is a little off or your touch sensor is behaving weirdly... can you go to Dev Tools > Pointer Location and verify the touch points...
Click to expand...
Click to collapse
where is the dev settings?>
It isn't dev settings, it's dev tools, an apk in all cyanogenmod releases. Just launch it from your drawer and go to pointerlocation.
Myphone has been doing this more than normal lately...Especially after installing one of the latest rc3 nightlies, and extremely noticeable when using swype keyboard. I would hit reboot and it would work itself out. It happened to me this morning...and let me tell you there is nothing more annoying than waking up hungover to a keyboard that just wont work.

blank screen but phone ON!!!!

Has anyone had this issue?
I have tried a few different ROM's and have had this problem on all, the phone will work but sometimes when the phone is locked and asleep you cannot get the screen back.
If you ring the phone it will ring but you can't wake the phone up (the screen is off).
If I then pull the battery and reboot all is well until the next time, which is random.
I will remove all my programs to see if there is one of them causing the issue, I don't believe it is the rom as it has happened on a few of them.
Have you wiped your phone when flashing the different roms? I've had it sometimes, i think it could be a ram management issue...
Talon26 said:
Have you wiped your phone when flashing the different roms? I've had it sometimes, i think it could be a ram management issue...
Click to expand...
Click to collapse
Yeh, I always do a factory/wipe, dalvik cache wipe.
I think it might have been TW4.5, I did some research and installed TW4 Manager I then updated TW4.5 to the latest Version. So far it hasn't happened yet but i'll give it a couple more days.
Thanks.
Yh ive been reading and TW4 generally accelerates the issue (because its a ram hog? not sure i dont use it) Im currently using Golauncher with system tweaks, but was told that nemus launcher and system tweaks was a better combination... Seems to be working, ive had less force closes or issues of that type
it's the proximity sensor. needs replaced.
pch.radu said:
it's the proximity sensor. needs replaced.
Click to expand...
Click to collapse
I don't think so...
The proximity sensor is only used when your in a call. It should not have any effect when he tries to wake it from his pocket after a while...
Well i am on 2.3.5 and using golauncher and never had any problems. Still my best guess is the damn sensor. On samsung apps there is an app called sensors i think and that app tells u what is working inside the phone.
Sent from my GT-I9000 using XDA App
If I recall correctly yeah I had this issue once on JVR and once on JVS and now on JVT I got it a few hours ago
---------- Post added at 06:30 PM ---------- Previous post was at 06:29 PM ----------
pch.radu said:
Well i am on 2.3.5 and using golauncher and never had any problems. Still my best guess is the damn sensor. On samsung apps there is an app called sensors i think and that app tells u what is working inside the phone.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Sounds like a great app but seeing as the screen doesn't turn on that app might as well be useless in this case
No screen turns on, its just when it turns off it wont come back on...
I have the same issue with my SGS. Running stock version of JVT.
Wake up in the morning to phone alarm but screen is black. Pushing home button or any other button does nothing. Had this happen a few times now and only solution is to pull the battery
In order to help you we need to know what you are running currently and what you have tried to resolve the issue so far, can please make as detailed account as possible
It's seems that everybody have this same issue. I have exactly this same - phone is working - buttons are lit, but the screen is blank. I'm on 2.3.5 stock firmware.
Trying to solve this I already did wipe and even formatted the internal storage.
What's more interesting is that this same happens to my wife's Galaxy Mini (S5570) !!.
I can remember though that when my phone was on v2.2 about a year ago it was working ok.
small tip:
What you can do instead of pulling the battery out is to press the power button for about 10 seconds ( phone will turn off) release and the press it again for few seconds to start again.
You don`t need to press power again, just keep it pressed until you see the samsung bootlogo.
Mine has started to blackout too, maybe it`s related to some installed software. It worked ok still few months ago. My galaxy mini is working ok tho, has only few market apps installed.
Sent from my GT-I9000 using Tapatalk
poyda69 said:
Has anyone had this issue?
I have tried a few different ROM's and have had this problem on all, the phone will work but sometimes when the phone is locked and asleep you cannot get the screen back.
If you ring the phone it will ring but you can't wake the phone up (the screen is off).
If I then pull the battery and reboot all is well until the next time, which is random.
I will remove all my programs to see if there is one of them causing the issue, I don't believe it is the rom as it has happened on a few of them.
Click to expand...
Click to collapse
The bug is called SOD (Sleep of Death). Apparently a Gingerbread only bug (I think deep sleep was introduced in Gingerbread).
Your phone is going into deep sleep, and can't be woken agian.
I don't know if there is a fix for it, but you could try search for SOD on these forum pages.
Herman76 said:
The bug is called SOD (Sleep of Death). Apparently a Gingerbread only bug (I think deep sleep was introduced in Gingerbread).
Your phone is going into deep sleep, and can't be woken agian.
I don't know if there is a fix for it, but you could try search for SOD on these forum pages.
Click to expand...
Click to collapse
i had this issue on cm7 with neo kernel, but sometimes it responded after some time
i think its black magic made by apple and will kill our cats
As Herman76 said, this is the SOD, I used to get them quite frequently. I created a thread with a possible workaround. So far haven't got any new SODs.

HTC One - Vibration stopped working after 4.4 kitkat update

Hi,
I have an HTC One (m7) international version, and after 4.4 kitkat update, it slowly lost it's vibration and heptic feedback function until it completely stopped this weekend, even with power save mode turned off, and all the configurations properly set.
I've tried returning to my latest 4.3 jellybean nandroid backup from Dec-23, but the problem still ocurred.
After that, I've restored the 4.4 kitkat nandroid backup I've made this morning, and installed the "Vibrate Plus" app from the play store. After playing with it for a few minutes without any success, I've realized that the vibration function only works, with the phone screen facing down. As soon as I lift the phone from the table or turn it up in my hand, it stops vibrating.
If, instead of the "Pattern Vibration" function, I choose the "Simple Vibration", which keeps the phone vibrating constantly, I have a few seconds of vibration with the screen facing up, after lifting the phone from the table, until it stops working again.
---
I've found this single thread (URL = www (dot) htconeforum (dot) com /forum/htc-one-help/2341-vibrate-function-has-stopped-new-htc-one-m7.html) (can't post the URL here) where a guy has the same problem I have and had his phone replaced by HTC; but since Brazil does not have official HTC assistance, I probably am going to have it fixed myself, just as I did with my former HTC One X and it's GPS issue.
The problem is, I can't seem to find any other report from this same problem, other than this thread, and I also am having a hard time finding detailed instructions on how to open this phone for servicing, so, any help regarding any of these is really welcome.
Thank you very much, in advance.
tvidal said:
Hi,
I have an HTC One (m7) international version, and after 4.4 kitkat update, it slowly lost it's vibration and heptic feedback function until it completely stopped this weekend, even with power save mode turned off, and all the configurations properly set.
I've tried returning to my latest 4.3 jellybean nandroid backup from Dec-23, but the problem still ocurred.
After that, I've restored the 4.4 kitkat nandroid backup I've made this morning, and installed the "Vibrate Plus" app from the play store. After playing with it for a few minutes without any success, I've realized that the vibration function only works, with the phone screen facing down. As soon as I lift the phone from the table or turn it up in my hand, it stops vibrating.
If, instead of the "Pattern Vibration" function, I choose the "Simple Vibration", which keeps the phone vibrating constantly, I have a few seconds of vibration with the screen facing up, after lifting the phone from the table, until it stops working again.
---
I've found this single thread (URL = www (dot) htconeforum (dot) com /forum/htc-one-help/2341-vibrate-function-has-stopped-new-htc-one-m7.html) (can't post the URL here) where a guy has the same problem I have and had his phone replaced by HTC; but since Brazil does not have official HTC assistance, I probably am going to have it fixed myself, just as I did with my former HTC One X and it's GPS issue.
The problem is, I can't seem to find any other report from this same problem, other than this thread, and I also am having a hard time finding detailed instructions on how to open this phone for servicing, so, any help regarding any of these is really welcome.
Thank you very much, in advance.
Click to expand...
Click to collapse
Don't know why I pressed thanks button instead of quote. Ignore it..
Coming to the issue, did you the Trickster mod? You could set the vibration intensity there.. Install from Playstore.
Sent from my HTC One using xda app-developers app
Hi,
I've downloaded the trickster mod, and set up the vibration intensity to 3100 (max).
With this new setting, the problem seems to be fading away... yesterday, the vibration function failed to work only twice, and today, it has worked fine the entire day.
I cannot think of a reasonable explanation for this, I really tought it was a hardware problem, but it seems to be working a lot better now.
Thank you very much!!!
tvidal said:
Hi,
I've downloaded the trickster mod, and set up the vibration intensity to 3100 (max).
With this new setting, the problem seems to be fading away... yesterday, the vibration function failed to work only twice, and today, it has worked fine the entire day.
I cannot think of a reasonable explanation for this, I really tought it was a hardware problem, but it seems to be working a lot better now.
Thank you very much!!!
Click to expand...
Click to collapse
I guess it's still better to check with service center once, you never know it could be a hardware problem and you might get a replacement for this
Sent from my HTC One using xda app-developers app
tvidal said:
Hi,
I've downloaded the trickster mod, and set up the vibration intensity to 3100 (max).
With this new setting, the problem seems to be fading away... yesterday, the vibration function failed to work only twice, and today, it has worked fine the entire day.
I cannot think of a reasonable explanation for this, I really tought it was a hardware problem, but it seems to be working a lot better now.
Thank you very much!!!
Click to expand...
Click to collapse
Is it still working? Have the same problem here, but the trickster mod doesn't help!
kirbe1 said:
Is it still working? Have the same problem here, but the trickster mod doesn't help!
Click to expand...
Click to collapse
After the vibration issue was solved, the earpiece became mute at random times during calls so I gave up from KitKat... too much trouble, not so much attractive new features.
I'm back with ARHD 31.0, Jellybean 4.3... it's perfect.
This version works fine for me.
After all the problems I've had, I think I'll never try to update my phone again, unless there's some sort of "killer feature" in the new version.
Good luck!
HTC One Vibrate not work - List of Solutions Hardware and softwares

[Q] 10.4.1.B.0.101 bug?

Hey guys, recently i updated to the new 4.3 10.4.1.B.0.101 firmware
however, several times, the screen will not wake and i am forced to do a hard reset
has anyone else been forced to do this?
EDIT: The bug only started after i updated to the new firmware
spazzy1912 said:
Hey guys, recently i updated to the new 4.3 10.4.1.B.0.101 firmware
however, several times, the screen will not wake and i am forced to do a hard reset
has anyone else been forced to do this?
EDIT: The bug only started after i updated to the new firmware
Click to expand...
Click to collapse
I can't say that I experienced that too. But I will keep an eye on it for the next couple of days. Maybe I just didn't notice it.
spazzy1912 said:
Hey guys, recently i updated to the new 4.3 10.4.1.B.0.101 firmware
however, several times, the screen will not wake and i am forced to do a hard reset
has anyone else been forced to do this?
EDIT: The bug only started after i updated to the new firmware
Click to expand...
Click to collapse
i just updated too few days ago,but i didn't face this problem...
Cenobite_ said:
I can't say that I experienced that too. But I will keep an eye on it for the next couple of days. Maybe I just didn't notice it.
Click to expand...
Click to collapse
ah when it does happen you will definitely notice it
you hit the power button, but the screen stays black
although i can confirm the phone is on, because if i plug in the charger, the light turns orange
spazzy1912 said:
ah when it does happen you will definitely notice it
you hit the power button, but the screen stays black
although i can confirm the phone is on, because if i plug in the charger, the light turns orange
Click to expand...
Click to collapse
press and hold the power button to see if it comes back to life, sometimes I get this on a .569 custom rom and have to either hold power+volume up to reboot it to get it to work
spazzy1912 said:
Hey guys, recently i updated to the new 4.3 10.4.1.B.0.101 firmware
however, several times, the screen will not wake and i am forced to do a hard reset
has anyone else been forced to do this?
EDIT: The bug only started after i updated to the new firmware
Click to expand...
Click to collapse
do you have a custom kernel?
Richy99 said:
press and hold the power button to see if it comes back to life, sometimes I get this on a .569 custom rom and have to either hold power+volume up to reboot it to get it to work
Click to expand...
Click to collapse
Yep that's exactly what I have to do to get display working again
beniamin24 said:
do you have a custom kernel?
Click to expand...
Click to collapse
Nope, stock kernel
I don't have your problem but I did have times yesterday where it would flash me black screens for no reason, for example when trying to close open apps, it would just flicker black for a bit. Haven't had that problem today though. I do however have broken Wifi at the moment, I can no longer connect to any network or access the settings without the settings freezing.
spazzy1912 said:
Yep that's exactly what I have to do to get display working again
Nope, stock kernel
Click to expand...
Click to collapse
Reinstall the rom to factory, i mean wipe everything when you reinstall, usualy that fixes a lot
beniamin24 said:
Reinstall the rom to factory, i mean wipe everything when you reinstall, usualy that fixes a lot
Click to expand...
Click to collapse
i restored to factory and wiped cache before installing, as well as clearing /system
Bug CONFIRMED! Can happen randomly. Not only that, but after a hard reboot , gyroscope is broken
Back to. 569 for me
Sent from my C6603 using xda app-developers app
Yes it is a bug stamina mode is causing the problem.Turn off stamina mode and it will work at least it worked for me.
mayankgamer said:
Yes it is a bug stamina mode is causing the problem.Turn off stamina mode and it will work at least it worked for me.
Click to expand...
Click to collapse
never used stamina mode and never will lol
shoey63 said:
Bug CONFIRMED! Can happen randomly. Not only that, but after a hard reboot , gyroscope is broken
Back to. 569 for me
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
gyroscope means auto rotate right? o.o
hmm my auto rotate is always fine
spazzy1912 said:
gyroscope means auto rotate right? o.o
hmm my auto rotate is always fine
Click to expand...
Click to collapse
Yes, auto rotate. It breaks after the "black
screen" event. (if and when that happens)
Sent from my C6603 using xda app-developers app
If you are using any sort of covers around the phone, remove it and try
The proximity sensor has become very sensitive preventing in-pocket turning on of the device, this might be your issue
Thanks
camera lag
I have the camera lag. when I open the camera app it takes complete a second or two to open. and if you open it from lock screen it takes for ever. well at least from the lock screen it was laggy on .569 too. other than that the UI is slightly slower and laggy than .569.
tanny0543 said:
I have the camera lag. when I open the camera app it takes complete a second or two to open. and if you open it from lock screen it takes for ever. well at least from the lock screen it was laggy on .569 too. other than that the UI is slightly slower and laggy than .569.
Click to expand...
Click to collapse
Camera has always taken forever to open, since the original firmware release
spazzy1912 said:
Camera has always taken forever to open, since the original firmware release
Click to expand...
Click to collapse
Did you upate through PCC?
I have an update ready for 101 there (UK) but this has made me a bit wary with what you are experiencing.. Also got the 569 update OTA - which I already have.. & I can't seem to get rid of the stupid message from my top bar!
Xperia z latest update bug
In the last software update does not work anymore voice recording, voice search does not work and the voice dictation of text messages. He tells me (you can not reach google at the moment) but it works for calls. I tried doing a reset by update service and PC Companion, but I have not solved. Can anyone help me?

[Q] [CM11] Reboots with every notification with screen off

Hi there, guys.
I did a wide search in Google/XDA/whatever and didn't manage to find anything related to my problem, so I'm posting it here :good:
My S3 Mini (I8190N) runs flawless and quite smooth on NovaFusion/Maclaw 20140524. Using Gravity Box for enabling navbar (since the I8190N loses its capacitive buttons when changes the kernel) did the trick and fully usable...
Except for one little BIG bug: everytime I receive a notification (Whatsapp, Gmail, FB, SMS, calls, doesn't matter which app) while the screen is off, it reboots. Every. Single. Notification. Cause of this, my battery lasts just a couple of hours, since is rebooting non stop, and I lose a lot of important things (calls, alarms, SMS, you name it)
I tried some things:
- Installing today's NovaFusion release (didn't solved);
- Clean installing 20140524 again (nope) and clean installing today's release (nope again);
- Removing Xposed and Gravity Box (I thought it could be some incompatibility, but nope);
- Disabling lockscreen (to test if the problem was with lockscreen itself, but no).
Following the logic, it appears to be something related to notifications waking up the screen (the phone even vibrates a little before restarting again), but I didn't find any configuration related to this.
So please, anyone? Any advices? Any solutions? This issue is getting me heads off
Strange bug indeed and i have no idea why. The vibration on boot is always there to tell that bootloader boots. Its easier to troubleshoot a black phone that way, according to the service manual.
Sent through time and space from my s3mini/CM11
Jucarez said:
Hi there, guys.
I did a wide search in Google/XDA/whatever and didn't manage to find anything related to my problem, so I'm posting it here :good:
My S3 Mini (I8190N) runs flawless and quite smooth on NovaFusion/Maclaw 20140524. Using Gravity Box for enabling navbar (since the I8190N loses its capacitive buttons when changes the kernel) did the trick and fully usable...
Except for one little BIG bug: everytime I receive a notification (Whatsapp, Gmail, FB, SMS, calls, doesn't matter which app) while the screen is off, it reboots. Every. Single. Notification. Cause of this, my battery lasts just a couple of hours, since is rebooting non stop, and I lose a lot of important things (calls, alarms, SMS, you name it)
I tried some things:
- Installing today's NovaFusion release (didn't solved);
- Clean installing 20140524 again (nope) and clean installing today's release (nope again);
- Removing Xposed and Gravity Box (I thought it could be some incompatibility, but nope);
- Disabling lockscreen (to test if the problem was with lockscreen itself, but no).
Following the logic, it appears to be something related to notifications waking up the screen (the phone even vibrates a little before restarting again), but I didn't find any configuration related to this.
So please, anyone? Any advices? Any solutions? This issue is getting me heads off
Click to expand...
Click to collapse
Since there seem to be issues with the capacitive button lights on your device, I would assume that the problem is with BLN (Back light notification) which activate the capacitive button backlights when you receive a notification and the screen is off.
I would suggest that you check to see if BLN is enabled and disable it. There is a BLN Control App in the Play store :good:
Meticulus said:
Since there seem to be issues with the capacitive button lights on your device, I would assume that the problem is with BLN (Back light notification) which activate the capacitive button backlights when you receive a notification and the screen is off.
I would suggest that you check to see if BLN is enabled and disable it. There is a BLN Control App in the Play store :good:
Click to expand...
Click to collapse
This makes a HUGE sense! :victory:
(still weird, tho, that only the I8190N loses its capacitive buttons on new kernel, but not entering this discussion haha)
Will try this, @Meticulus. Thanks in advance
Download Disable_BLN.zip and flash in recovery. See if it works. My backlight are always off with this flashed.
https://app.box.com/s/ybzhlojc807u8srw8lep
Sent through time and space from my s3mini/CM11
i have the i8190 and have the same problems
So I'm using Carbon and Slimkat, works perfectly fine
Jucarez said:
This makes a HUGE sense! :victory:
(still weird, tho, that only the I8190N loses its capacitive buttons on new kernel, but not entering this discussion haha)
Will try this, @Meticulus. Thanks in advance
Click to expand...
Click to collapse
Did you try it ?
tys0n said:
Download Disable_BLN.zip and flash in recovery. See if it works. My backlight are always off with this flashed.
https://app.box.com/s/ybzhlojc807u8srw8lep
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
Thank you! Now it works perfectly fine Finally found the solution after few months, thank you!
Hi guys,
I tried it. It's working perfectly. Hallelujah!
Now I'm discovering the Xposed to do a lot of other things (autohide the navbar, disable the "3-dot" button on apps, etc)
Thank you very much!
down
tys0n said:
Download Disable_BLN.zip and flash in recovery. See if it works. My backlight are always off with this flashed.
https://app.box.com/s/ybzhlojc807u8srw8lep
Click to expand...
Click to collapse
LMH1998 said:
Thank you! Now it works perfectly fine Finally found the solution after few months, thank you!
Click to expand...
Click to collapse
Jucarez said:
I tried it. It's working perfectly. Hallelujah!
Click to expand...
Click to collapse
Unfortunately, the workaround "patch" is not available anymore :crying:
would it be possible to upload it again anywhere, maybe here?
or is there another possibility to fix that problem yet?

Categories

Resources