Anyone know why my hardware button lights don't turn off? I'm not overclocking or anything
Android doesn't support controlling the keyboard/button backlights, so if they're on in WM before loading Android, they'll stay on as long as the device is in Android, and if they aren't lit up when in Android, they will not light up. The only solution is to make sure the hardware buttons are not lit up before booting into Android.
viper786 said:
Anyone know why my hardware button lights don't turn off? I'm not overclocking or anything
Click to expand...
Click to collapse
One of the solutions is to turn off auto-backlight control in WinMo. This way you don't have to worry about WinMo tripping the backlight right as you're trying to run haret.
The easiest way to do it is when you open the xdandroid app in winmo, before you hit "run android" press the top button to turn off the screen, then turn it back on, then hit "run android." Works for me all the time
-------------------------------------
Sent via the XDA Tapatalk App
my phone started doing that today, but for some reason mine stay on even on windows.
redsrt4 said:
my phone started doing that today, but for some reason mine stay on even on windows.
Click to expand...
Click to collapse
Reboot WinMo. Sometimes strange things happen! But a reboot or two usually sorts them out
snalbansed said:
Reboot WinMo. Sometimes strange things happen! But a reboot or two usually sorts them out
Click to expand...
Click to collapse
must have booted like 10 times but they still stay on dim but they are still on. im gonna try reflashing my rom see if that takes care of it.
well lights are still on after i did this:
task29
flashed rom
reflashed hard spl
any other suggestions on what i can do to fix it?
thanx in advance
If they stay on even in WinMo, there *may* be a hardware issue. Have you tried flashing back to stock?
im goin to try that today
I'm having exactly the same problem. Can you tell me if you found any solution to solve this issue?
Anyone get a solution to this? I've tried flashing back to stock and the keys still stay lit.
kaskd said:
Anyone get a solution to this? I've tried flashing back to stock and the keys still stay lit.
Click to expand...
Click to collapse
If your lights never turn off in WinMo, something is wrong with the phone's hardware I would think.
As was stated previously, if you boot Android with these lights on in WinMo they will stay on in Android. There's a patch in the works to fix this issue...
Try a new battery. I had similar issues with battery not fully charging changing the battery cleared it up. Sprint gives batteries for free.
Related
I'm using FROYO x 2011.01.28 SYSTEM.EXT2 UPDATED
It can detect wifi but can't connect to it.
And the biggest problem for me is when i turned my phone off.
It's turn to green and turn to red after somebody called with screen off.
but if I don't let the screen off,I can call without problem.
anybody please help.Thank you very much.
siamboyecc said:
I'm using FROYO x 2011.01.28 SYSTEM.EXT2 UPDATED
It can detect wifi but can't connect to it.
And the biggest problem for me is when i turned my phone off.
It's turn to green and turn to red after somebody called with screen off.
but if I don't let the screen off,I can call without problem.
anybody please help.Thank you very much.
Click to expand...
Click to collapse
Is your access point secured with WEP? WEP is a known issue. Try to switch to WPA.
About your screen off, i don't get what the problem is, be more chronologic
afrizal_chen said:
Is your access point secured with WEP? WEP is a known issue. Try to switch to WPA.
About your screen off, i don't get what the problem is, be more chronologic
Click to expand...
Click to collapse
Ok First I let my phone to sleep(screen off with green LED )and when I call in, it shows red LED with screen still off.when I turn on screen ,It's show me lock screen with nobody call me.
I try to change Force_cdma=0 or delete it and it gives me same thing.
Thank you.
Now I changed sleep mode =2 and it's working.
siamboyecc said:
Now I changed sleep mode =2 and it's working.
Click to expand...
Click to collapse
That should have no effect whatsoever on wifi.
Also, if you're running a newer kernel with the PLL2 commit, you should be setting this to =1... You'll get much better battery life, and you'll be able to OC without SoD (at least not as many as previously )
siamboyecc said:
Ok First I let my phone to sleep(screen off with green LED )and when I call in, it shows red LED with screen still off.when I turn on screen ,It's show me lock screen with nobody call me.
I try to change Force_cdma=0 or delete it and it gives me same thing.
Thank you.
Click to expand...
Click to collapse
Force_cdma= should be set to 0 or deleted as your t7373 is a Rhod100 if i'm correct.
So your problem seems to be that you don't receive phone calls when your phone is in sleep mode? Make sure you run the newest kernels. I can't remember issues like this on my rhod100..
Maybe just try a clean build, delete data.img (rename if you don't wanna lose everything, backup!). Or try a different build to pinpoint your problem.
And the last thing, as you are running a froyo x build, this question would've fitted perfectly in that thread
Good luck!
Thanks everybody.
Hi,
I have the T989 version, although i love my phone it seems that ever since ive started to use different roms my lock screen wont turn on, i cant get it to swipe, pattern, face unlock or anything. Its either screen on or off. Is this normal? Whenever i even restored my original gingerbread rom it still doesnt work.
One more thing, when you hold the power button it usually gives you an option to put it on silent or vibrate or plane mode, well when i press power and hold it it just turns off. What is really going on guy, any help would be great thanx!
turkishroyal1453 said:
Hi,
I have the T989 version, although i love my phone it seems that ever since ive started to use different roms my lock screen wont turn on, i cant get it to swipe, pattern, face unlock or anything. Its either screen on or off. Is this normal? Whenever i even restored my original gingerbread rom it still doesnt work.
One more thing, when you hold the power button it usually gives you an option to put it on silent or vibrate or plane mode, well when i press power and hold it it just turns off. What is really going on guy, any help would be great thanx!
Click to expand...
Click to collapse
You should probably ask here. Though it sounds like your missing your /efs/imei/keystr file.
thanx
ctomgee said:
You should probably ask here. Though it sounds like your missing your /efs/imei/keystr file.
Click to expand...
Click to collapse
it wont let me post on there cuz im new
turkishroyal1453 said:
it wont let me post on there cuz im new
Click to expand...
Click to collapse
"there" is the forum for the T989. You can post there. Should probably go to the Q&A forum there instead of here, which is the forum for the I9100. (which is a different model than what you have)
Better there than here, else people point you to do something specific for the I9100, which could potentially brick your phone.
have you checked your settings?
Settings> Security > Screen Lock
it may be on None
Hi!
I installed "U20_nAa-14_2.6.29.6-nAa-14" and "MiniCM7-2.2.1-mimmi" on my phone. The mobile network didn't worked, so I tried closing back the bootloader. I made it with "s1tool relock.exe", and it really closed it back. The instructions I followed while doing it, said that I shouldn't start the phone after doing the relocking and disconnecting it from the computer. Accidentally I switched it on, and now it won't turn on. Only the startup vibration and green led flash. If I connect it to the computer it keeps connecting and deconnecting, I don't know how to open up the bootloader again if it's possible at all.
Is it repairable?
Thank you for your help.
Rodage said:
Hi!
I installed "U20_nAa-14_2.6.29.6-nAa-14" and "MiniCM7-2.2.1-mimmi" on my phone. The mobile network didn't worked, so I tried closing back the bootloader. I made it with "s1tool relock.exe", and it really closed it back. The instructions I followed while doing it, said that I shouldn't start the phone after doing the relocking and disconnecting it from the computer. Accidentally I switched it on, and now it won't turn on. Only the startup vibration and green led flash. If I connect it to the computer it keeps connecting and deconnecting, I don't know how to open up the bootloader again if it's possible at all.
Is it repairable?
Thank you for your help.
Click to expand...
Click to collapse
Flash THIS with flashtool. The download is about 213 MB, although it may say differently when downloading, just wait till it's finished.
It's original Sony Ericsson Firmware and can be flashed on a device with a locked bootloader. Not sure about the version, although it says 2.1.1.A.0.6, it may be older, but i don't have a U20, so I can't check. It should be possible to upgrade it with Sony Update Service if it's an older version. Good luck.
Thank you!
It worked. Can I ask that too, is there a safest way to solve the no network problem?
Rodage said:
Thank you!
It worked. Can I ask that too, is there a safest way to solve the no network problem?
Click to expand...
Click to collapse
Depends on your simlock certificate or how your phone was unlocked from it's original network. There are two or three methods (msm_7227_semc, msm_7227_setool2, and maybe one for omnius too) , just try them and check if you get a signal before you flash any custom firmware. If you don't get a signal, relock it again and try a different method.
Flashtool used to be quite good at figuring out which method worked best, but I don't know if that still supports unlocking 2010 devices. I've got 0.9.13 and there is a BLU (Bootloader UnLock) button.. just try that
I opened it again with msm7227_semc, bacuse the others didn't worked, and installed it again. Now everything is fine, but the home button and the screen lock still not works:/ I think I'll leave it this way, and not risk one more time my network connection.
Thanks for your help.
Rodage said:
I opened it again with msm7227_semc, bacuse the others didn't worked, and installed it again. Now everything is fine, but the home button and the screen lock still not works:/ I think I'll leave it this way, and not risk one more time my network connection.
Thanks for your help.
Click to expand...
Click to collapse
If it's unlocked and the network is still there you can do whatever you want with it There's no need to lock it ever again so you can experiment with kernels and roms all you want.
What was the matter with the home-button and the screenlock? Do the other buttons work and is the screen ok when you slide out the keyboard?
SmG67 said:
If it's unlocked and the network is still there you can do whatever you want with it There's no need to lock it ever again so you can experiment with kernels and roms all you want.
What was the matter with the home-button and the screenlock? Do the other buttons work and is the screen ok when you slide out the keyboard?
Click to expand...
Click to collapse
The other buttons are all fine, and the home looks fine too, just the only way to use it is to turn on the screen with it. Which hasn't got a lock on it, when I push any button, it switches right to the home screen. Turning on lock patterns and others didn't helped. Maybe can I use external applications to substitute the functions?
Rodage said:
The other buttons are all fine, and the home looks fine too, just the only way to use it is to turn on the screen with it. Which hasn't got a lock on it, when I push any button, it switches right to the home screen. Turning on lock patterns and others didn't helped. Maybe can I use external applications to substitute the functions?
Click to expand...
Click to collapse
Hmm, sounds a bit like the ROM doesn't want to go to sleep. Maybe you could reboot into recovery, and wipe data/factory reset, wipe cache and wipe dalvik-cache (from the advanced menu). I'm sure you already did that, but it can't hurt to do it again, and see if that fixes the problem
The phone should enter deep-sleep after about 5 seconds after the screen is turned off, in which case the only way to wake up the screen are the power-button and the home-button. pressing menu or back should keep the phone asleep. If after about 10 or 20 seconds you can still wake up the screen with the back or menu buttons you might want to check if there's an app keeping the phone awake.
Done factory reset and cache wipe already multiple times. Just realized how annoying is the dysfunctional home button, so I tried MiniCM7-2.2.0, MiniCM9-3.0.5 with nAa-11,13,14 and nAa-ics-04. Unfortunatley didn't worked the home button or the screen lock with none of them. At first time, I installed the MiniCM10, but the phone was relatively slow with it and buzzed, so I switched to MiniCM7.
Screen timeout and turnoff delay both set to immediately, but even the camera button can turn on the screen no matter how many time elapses. Can the original MiniCM apps keep it awake? I installed a task killer, but no change.
Rodage said:
Done factory reset and cache wipe already multiple times. Just realized how annoying is the dysfunctional home button, so I tried MiniCM7-2.2.0, MiniCM9-3.0.5 with nAa-11,13,14 and nAa-ics-04. Unfortunatley didn't worked the home button or the screen lock with none of them. At first time, I installed the MiniCM10, but the phone was relatively slow with it and buzzed, so I switched to MiniCM7.
Screen timeout and turnoff delay both set to immediately, but even the camera button can turn on the screen no matter how many time elapses. Can the original MiniCM apps keep it awake? I installed a task killer, but no change.
Click to expand...
Click to collapse
If it happens on all ROMS, maybe it's your home-button keeping the phone alive, as in that it makes continuous contact. Wouldn't know what to do about that though. Does it happen on stock firmware too?
SmG67 said:
If it happens on all ROMS, maybe it's your home-button keeping the phone alive, as in that it makes continuous contact. Wouldn't know what to do about that though. Does it happen on stock firmware too?
Click to expand...
Click to collapse
No, when I restored it with the Sony Update Service everything worked fine on the stock 2.1, and it is still possible to turn on the screen with the home button, but it's other functions are out.
Wow, this time I didn't installed the gapps like it was written in the CM wiki (http://wiki.cyanogenmod.org/w/Install_CM_for_mimmi), both the home button and screen lock works. Why it is written in the "Install CM for mimmi" article if the gapps on the download page is for MiniCM10?
Whatever, shame on me, I should've just take it seriously, and not follow the instructions blindly.:silly:
Thanks for all of your help.:good:
Rodage said:
Wow, this time I didn't installed the gapps like it was written in the CM wiki (http://wiki.cyanogenmod.org/w/Install_CM_for_mimmi), both the home button and screen lock works. Why it is written in the "Install CM for mimmi" article if the gapps on the download page is for MiniCM10?
Whatever, shame on me, I should've just take it seriously, and not follow the instructions blindly.:silly:
Thanks for all of your help.:good:
Click to expand...
Click to collapse
If you get the ROM from the thread in x10minipro development section of this forum, there is a link to the proper gb-gapps
This morning I started having an issue with my edge.
Whenever I touch the screen, both capacitive buttons light up. Causing for irregular behaviour when using the phone. Is there a screen calibration mode or should I return it for a new phone.
Mine does the same thing. I'm pretty sure that's standard.
Agreed. Sounds like normal behavior to me.
I fail to see how this is an issue?
It's an issue in the sense that previously on galaxy models they only light up when you press them. It's a bit ridiculous and waste of battery to have them lighting up every time you interact with the phone.
And for reasons unknown, every s6 excluding the att version has had the setting to turn off the lights removed.
paddylaz said:
It's an issue in the sense that previously on galaxy models they only light up when you press them. It's a bit ridiculous and waste of battery to have them lighting up every time you interact with the phone.
Click to expand...
Click to collapse
That is not true.
The S5 cap lights also light up when you touch the screen. That is how it should work. It would ridiculous for it to NOT light up every time you interact with the phone (assuming you wanted them on at all).
It would be nice to have the option to turn them off. That doesn't make it an issue--more of a feature request.
paddylaz said:
It's an issue in the sense that previously on galaxy models they only light up when you press them. It's a bit ridiculous and waste of battery to have them lighting up every time you interact with the phone.
And for reasons unknown, every s6 excluding the att version has had the setting to turn off the lights removed.
Click to expand...
Click to collapse
They really don't use any noticable battery.
cpshoemake said:
It would be nice to have the option to turn them off. That doesn't make it an issue--more of a feature request.
Click to expand...
Click to collapse
If you enable power saving mode it turns them off FWIW.
Fix for this issue
Hi,
please check my reply in the S6 thread on the same issue: http://forum.xda-developers.com/showpost.php?p=60009456&postcount=12
Hi, I have the S6 Edge. The touch key lights are not working at all. In Settings I have the Touch Key Light duration set to "Always On". Power Saving Mode is off, but they still won't come on. The keys do blink briefly during startup, so I do know they physically work. Any ideas? Thanks
Some times my capacitive buttons stop working altogether. It happened to me twice so far. It lasts about a minute. No response no light, nothing. Anyone else?
asolo157 said:
Hi, I have the S6 Edge. The touch key lights are not working at all. In Settings I have the Touch Key Light duration set to "Always On". Power Saving Mode is off, but they still won't come on. The keys do blink briefly during startup, so I do know they physically work. Any ideas? Thanks
Click to expand...
Click to collapse
Where are you finding the "Touch Key Light" settings? I don't seem to see them.
---------- Post added at 08:28 AM ---------- Previous post was at 08:27 AM ----------
mrnovanova said:
Some times my capacitive buttons stop working altogether. It happened to me twice so far. It lasts about a minute. No response no light, nothing. Anyone else?
Click to expand...
Click to collapse
Yes, I am having the same issue. I thought it might be an app but I have removed all of them and it still happens. So annoying!! Even a reboot doesn't help.
Settings-Device-Display-Touch key light duration
Dr. Bamboozle said:
Settings-Device-Display-Touch key light duration
Click to expand...
Click to collapse
that option is NOT on the 925T
wase4711 said:
that option is NOT on the 925T
Click to expand...
Click to collapse
This is not on the SM-G925W8 version either.
Sometimes these buttons stop working all together and sometimes they both switch to become the task switcher button. The Back Key will no longer function to move you back a page! Very annoying. I am thinking the only fix might be a complete factory reset??
BTW, when this happens, something is loading in the background. Just before my buttons stop working, a get a very small vibration similar to when your device boots up. From that point forward the buttons don't work. It can last 1/2 hour or up to 2-3 hours before it clears itself up??
Update: I did a factory reset and it didn't do any good. There are literally thousands of posts on the web about this issue and no resolution. If you have this issue, I think you need to send your unit back.
I have a SAMSUNG-SM-G925A running stock AT&T Android 5.02
I dunno, received my Edge today and my capacitive buttons only light up when I click them.
I took my phone back today and Rogers very quickly gave me a replacement phone. Capacitive buttons working well on this one!!
Everything was working as expected and the two buttons (Back and running apps) stopped working, i made a factory rest and it did not help, I am suspecting the cover that have magnets in it and I removed it, shut down the phone for few minutes but it did not help, I will try extending the time it is shut down and see the results.
For those with button light issues try this app "Galaxy Button Lights". I'm not allowed to post external links here but you can find it in Google Play.
Hello,
I have a very strange problem with my Xperia Z2. After unlocking the display on the device is blank. You can see the brightness, the touch works, because when I swipe my fingers I can hear android sound but there is no picture. I must do "lock - unlock" pattern 3-4 times, sometimes even more to get the display work properly. I tried to fix it by using software repair but it didnt work, and also
factory reset. Its just so iritating, I cant even lock my phone anymore, I try to keep the display on as much as possible if someone trys to call me so I can answer it. Device is currently running on Existenz ROM but the issue started on the stock so I flashed custom rom but it didn't help. So this is probably a hardware problem and if it is, what could be broken ( is it display, GPU,whatever ) or it could be a software problem ? Any help would be appreciated.
Can you see your lockscreen?
iXaidyiu said:
Can you see your lockscreen?
Click to expand...
Click to collapse
No, no the "lock-unlock pattern" is reffered to simply pressing the unlock button on the phone. There is just blank display and light is on as I mentioned but no picture. After pressing button many times the picture finaly comes and then it's normal. It only happens when phone goes to sleep mode or after I lock it.
If your phone reboots can you see the SONY logo and the boot animation as well?
iXaidyiu said:
If your phone reboots can you see the SONY logo and the boot animation as well?
Click to expand...
Click to collapse
Nope, there is nothing. Just a sound and LED works, and blank screen. Then again, when the phone finally reboots, pressing lock-unlock button will do the trick. It seems like, when I dont touch the phone longer time, it's harder to get screen on. But when I constantly work with the phone there is no need for that amount of "lock - unlock button move".
mby RIP graph.. try flashtools..
YamyYugi said:
mby RIP graph.. try flashtools..
Click to expand...
Click to collapse
It's probably hardware, now it's just a question of repair cost and is it worth it ?
TechCODE said:
Nope, there is nothing. Just a sound and LED works, and blank screen. Then again, when the phone finally reboots, pressing lock-unlock button will do the trick. It seems like, when I dont touch the phone longer time, it's harder to get screen on. But when I constantly work with the phone there is no need for that amount of "lock - unlock button move".
Click to expand...
Click to collapse
I think this is due to a faulty LCD screen, but the digitalizer seems fine. So maybe you could consult some local repair shops and prove if my hypothesis is correct. But first of all you should try also flashing another kernel (eg elite kernel) first to see if it is a software issue rather than a hardware issue.
Sent from my Sony D6503 using XDA Labs