Related
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.
I have purchased second hand galaxy S2 I9100.
I am experience LCD problem from the start. First w botton on horizontal arrangment not working.
I tried *#0*# test code for LCD and found one column from top to bottom not working.
Now LCD is behaving strange after i remove the screen protector. It goes to automatic selection in the middle of screen after some time of use e.g it automatically got selecting every thing which is on middle left of screen
I talked to some of my friends and they think it is a software issue.
I have tried flashing it with different ROMs using ODIN but no improvement results
It also go to downloading mode by only selecting volume down during power on.
Please help as I am not getting anything for solution
If that's happening with every rom you've tried (I presume you've gone back to stock firmware to test as well ?), then that's a hardware problem.
Home key Download mode
Yes I have also tried stock firmware of my model.
I have one more question. My Samsung galaxy S2 goes to download mode by pressing power and volume down button only e.g without pressing home key button. My home key button function properly at the android home.
I that also some issue with the hardware?
Try flashing the XWKL1 fw.. It pretty much fixed mine
Sent from my GT-I9100 using xda premium
MistahBungle said:
If that's happening with every rom you've tried (I presume you've gone back to stock firmware to test as well ?), then that's a hardware problem.
Click to expand...
Click to collapse
Yes I have also tried stock firmware of my model.
I have one more question. My Samsung galaxy S2 goes to download mode by pressing power and volume down button only e.g without pressing home key button. My home key button function properly at the android home.
I that also some issue with the hardware?
If its still under warranty get the screen replaced. I did.
I.lost a whole collumn and wasn't too stressed about it but before long another collumn went. I expect more would have followed so better to get it replaced at their cost not ours.
----------------------
GTI9100
Hydra H2O 1.2.1
fluxi xx.01_rc5
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
Hi all..
I have a problem with my DNA. Sometimes, like maybe once every few weeks or so, the touch screen will not respond correctly.
Here's what happens:
1. I turn on the display while the phone is already running. (meaning, I'm not booting up when it happens)
2. I try to slide the unlock widget up but it doesn't respond.
3. I hold the power button, and it says to continue holding it for 3... 2... 1.. seconds. However, at 1 seconds, it never does anything. I've held it for 2 or 3 minutes at times, and no reboot.
4. I swipe randomly around the screen and notice that some of my quick launch icons or the unlock slider bump up momentarily, but not enough to unlock the phone.
5. I continue swiping randomly, with a random number of fingers, and eventually the stars align and the phone is unlocked.
6. Once the phone is unlocked, tons of random touch presses occur. Random apps will open, messaging, etc. Sometimes, it opens the phone app and randomly presses things. It does this at a very, very rapid rate. I usually panic and turn off the display so it stops.
7. I manage to unlock it and hold the power button until the "Reboot/Shutdown/Airplane Mode" window appears and STAYS on the screen long enough for me to tell it to reboot.
8. After it reboots, the problems are gone and the touch screen returns to its proper functionality.
Has anyone had this problem before or know why it's happening? Or what can contribute to it?
Insertcoin rom or any kernel?
It's kernel issue. I have same problem. Flash another kernel fix it
Sent from my HTC Droid DNA using Tapatalk
Huongnv said:
Insertcoin rom or any kernel?
It's kernel issue. I have same problem. Flash another kernel fix it
Sent from my HTC Droid DNA using Tapatalk
Click to expand...
Click to collapse
Forgot to give some info:
I'm on default Rom, not rooted, nothing special.
To fix this problem, should I go ahead and root and install a new Kernal?
Garmy said:
Forgot to give some info:
I'm on default Rom, not rooted, nothing special.
To fix this problem, should I go ahead and root and install a new Kernal?
Click to expand...
Click to collapse
Flash a clean rom
U can use stock img with latest 4.4.2 sense 5.5 official or viper 4.4.2 sense 6
Sent from my HTC Droid DNA using Tapatalk
My screen started doing this, for me it is hardware failure. When you enable "show touches" from developer options, does it show 3-7 ghost touches? Mine is doing this (shattered screen and that is the only side effect, ha)
Sent from my HTC6435LVW using xda app-developers app
So i was just forced to install Lollipop by Sprint. I was having a minor S-Pen issues and Sprints "FIX" was to update me to Android 5.0 Lollipop. Well now I have 500000000 other issue with my phone. Most i can live with, but there are 2 in particular that at driving me absolutely bonkers and I cant fix. I was hoping someone around here would have an idea how to fix it without me having to root, and go back to the previous OS. (The Sprint Root seems a little intimidating and I cant afford to brink my phone even for 20 minutes).
The main issues I am having are regarding the lock screen. I cant get the lock screen to stay open more then 3 or 4 seconds and if I botch my pattern or don't swipe fast enough, the screen will turn itself off. Then I have to turn the screen back on and try and unlock it again. Sometimes the screen even turns off in the middle of trying to unlock it. It is EXTREMELY annoying having to try and unlock my phone 4 or 5 times just to get to the notification screen ...... As for the Notification screen, once i finally am able to get my phone unlocked, then when i try and swipe my notification bar the phone will sometimes turn the screen off as well, then I have to go BACK to trying to unlock the phone and try and do everything faster then 2 jack rabbits banging in order to just get to my notifications. Its become a major problem in that sometimes I just cant get the sequence and speed right for 10 or 15 tries.
Anyone else having these issues or have a fix???
jcohenlv said:
So i was just forced to install Lollipop by Sprint. I was having a minor S-Pen issues and Sprints "FIX" was to update me to Android 5.0 Lollipop. Well now I have 500000000 other issue with my phone. Most i can live with, but there are 2 in particular that at driving me absolutely bonkers and I cant fix. I was hoping someone around here would have an idea how to fix it without me having to root, and go back to the previous OS. (The Sprint Root seems a little intimidating and I cant afford to brink my phone even for 20 minutes).
The main issues I am having are regarding the lock screen. I cant get the lock screen to stay open more then 3 or 4 seconds and if I botch my pattern or don't swipe fast enough, the screen will turn itself off. Then I have to turn the screen back on and try and unlock it again. Sometimes the screen even turns off in the middle of trying to unlock it. It is EXTREMELY annoying having to try and unlock my phone 4 or 5 times just to get to the notification screen ...... As for the Notification screen, once i finally am able to get my phone unlocked, then when i try and swipe my notification bar the phone will sometimes turn the screen off as well, then I have to go BACK to trying to unlock the phone and try and do everything faster then 2 jack rabbits banging in order to just get to my notifications. Its become a major problem in that sometimes I just cant get the sequence and speed right for 10 or 15 tries.
Anyone else having these issues or have a fix???
Click to expand...
Click to collapse
I can't say I had any problems like this. I was running Stock rooted OC5 for a while and had really no problems with it. I didn't have any pattern or pin unlock though, so maybe it would have been different? I would have stayed stock but my Flashaholic took hold and made to start trying out other ROMs.
As for rooting, I have found it very easy to root this phone. I haven't had a problem either using auto-root or flashing superSU.
Factory reset is easy.
w7excursion said:
Factory reset is easy.
Click to expand...
Click to collapse
before a factory reset, you might try doing a wipe of the cache partition.
turn your phone off
press and hold, Volume up + home key + power until you see the blue booting to recovery mode message
wait for recovery mode to display (the menu will show after the green robot)
use the volume rocker to move down to wipe cache partition and press the power button to select it.
now select the yes line and press power
now reboot your phone and see if that helps with the lock screen behavior
good luck
jdelano said:
before a factory reset, you might try doing a wipe of the cache partition.
turn your phone off
press and hold, Volume up + home key + power until you see the blue booting to recovery mode message
wait for recovery mode to display (the menu will show after the green robot)
use the volume rocker to move down to wipe cache partition and press the power button to select it.
now select the yes line and press power
now reboot your phone and see if that helps with the lock screen behavior
good luck
Click to expand...
Click to collapse
This seemed to work so far. Ill keep you posted as I use it more today. Thank you so much
jcohenlv said:
This seemed to work so far. Ill keep you posted as I use it more today. Thank you so much
Click to expand...
Click to collapse
Glad to hear that, I hope it stays that way
You should read more before trying to root