Hi.
Today I encounter a strange problem that I don't how to solve, I've used the LED flash as Torch for aprox 20 mins, and it stopped working.
In camera app the flash is working fine as "flash" only and not as torch. I've tried to reboot/reset the whole system/factory and even tried to hard reset, without any change. Is the LED defective? or what's wrong. I've also tried to download a random torch app from playstore, and it couldn't turn on the LED.
Any advice is appreciated.
Related
It wastes lots of battery. I think i might have damaged the light sensor but i've tried turning it off but it doesnt change anything.
Anybody know?
Even if the light sensor is damaged, your backlight will go off after your device idles for some. Check your settings
thanks for the prompt reply.
ive checked all my power managment settings and they're all on the lowest time settings..
i dont understand why it would do this.
Are you using any softwares that manages the backlight timeout? Such as Tweak2k2, etc
it seems to be working fine now after i restarted my phone.
i wasnt using any software.
thanks for your help.
ducamie said:
it seems to be working fine now after i restarted my phone.
i wasnt using any software.
thanks for your help.
Click to expand...
Click to collapse
my phone did this before. but yea just a simple reset fixed it
Maybe you installed maniac's AutoKeyLock, I had the same behavior a couple of time...
It seems like after some time, it overrides by mistake the power mgt values.
Hi!
I have the same problem. Wm6 The back light turn to the dim mode and that"s all. It does switch off the screen. If I connect to the AC power It does the same. When I lock the keypad, every thing seems to be all right. It switches the screen off. Any idea. I restarted the phone, but nothing changed, i didn't install any Autokeylock program.
Hi, this problem exist occasionally after you install some apps (i.e. AutoKeylock). You can fix it easy - enter registry and open key "HKEY_CURRENT_USER\ControlPanel\Power" then modify value in key "Display".
Thanks, it is working.
I am having a really weird issue with these. So, sometimes all is working fine and then suddenly (after a reboot or even after unlocking the screen) the capacitive lights stop working (or don't go off at all if I unlock again) and the auto brightness does not work. I restart, take battery out, power on and nothing happens. Tried different ROMS (ARHD, DarkSense, stock one), different kernels (Sebastian, Faux, Sultan's) and the same happens. Everything is working fine and then suddenly it just doesn't. Even today I wiped everything on my phone, flashed ARHD with faux's kernel that it includes and all was awesome. Installed my apps, my games, restored the save games with titanium and was good. Rebooted, took battery out, power on again and all was fine. Did some benchmark, all good. Then I did a nandroid just in case it fails again. After that, I played a bit on the phone and copied some albums to sdcard I was impressed how it was lasting so long without everything to break again. Then I rebooted and everything started again. I rebooted and after the screen went off (not completely, I could see some light on it still) the capacitive lights stayed on for like 15s or so. After they went off, I took battery off and powered on the phone and guess what? Capacitive lights don't work neither does auto brightness. Formatted sdcard, fixed permissions, rebooted and nothing once again.
I shall say that capacitive lights work all the time while in recovery mode.
I am running out of options to try and to see what is wrong here. Here goes some options:
1- Battery. My battery does not last long at all. It's really weak and if it lasts like 8h with normal/low using is too much. I plan in buying a Anker battery to improve this.
2- Software. Is this possible? Because I tried with 3 different ROM's, 3 different kernels and all happens. Unlikely.
3- Hardware. Light sensor broken + capacitive lights or some connection? Really unlikely, imo. If it was like that they would be always off and not power on when on recovery mode. Plus, sometimes after I fix permissions/format sdcard all works good.
4- Sdcard. Perhaps it's faulty? I have 2 more but can't try them now, just on friday.
5- USB cable? No idea...
6- ???????
7- You name it.
PS: While writing this post I rebooted into recovery, formated sdcard and fixed sdcard filesystem with the phone just on battery. Ater that, took battery off, power on and nothing. Then, I took battery off, rebooted into recovery, connect the phone to the power socket to charge, formated sdcard, fixed card filesystem, fixed permissions, took battery off, reboot and...gues what. It is working. All is working good. This is a ****ed up issue, I guess and I think all points to battery, for some reason. Any help here? Thank you!
EDIT: Just copied some music albums again to sdcard and after that switched off the phone. Took battery off, powered on and everything stopped working again. This while on battery. Power phone off again, connected to the power socket and turned it on again. Does not work. Disconnected the cable, rebooted into recovery and formated sdcard. Rebooted and...it works. What the hell? Next: copied an album to phone. Disconnected it properly in Windows and waited on phone for sdcard to be mounted. Reboot while on battery...and it works.
Any clue?
bumpy bump
Hey guys,
I have a really strange display issue with my Galaxy R.
I'm on CM10.1 nightly and already tried different nightlies with factory reset and wipe data/cache.
If the phone is not used for a while (sometimes even after 30 minutes), meaning it is on and screen is off, the display won't turn on anymore.
So I press the power button and the capacitive buttons light up, but the screen stays completely black.
Today I noticed that I can even use the touch screen and I could hear all sounds, I even managed to open the dialer and start typing blindly and it would make the dial sounds.
But whatever I try, the screen won't turn on.
Also, it seems when I'm connected to a charger and/or connected to wifi, this problem doesn't seem to occur.
Then I have no choice but to remove the battery, but then often I can't even start the phone.
Sometimes it takes some minutes, sometimes a really long time until I can start it again.
Usually the battery isn't drained, this only happened once.
This occurs after I dropped the phone twice, so it might be related to that.
(Though before I've also dropped it and this never happened.)
Any ideas?
flash stock ics and see if problem persists.
once i flashed a custom rom and faced this issue, reverted to stock and now my device is running with zero issues.
Nikhil said:
flash stock ics and see if problem persists.
once i flashed a custom rom and faced this issue, reverted to stock and now my device is running with zero issues.
Click to expand...
Click to collapse
I tried to find the stock rom online, but all links seem to be down.
Do you know where I can get it?
wasabah said:
I tried to find the stock rom online, but all links seem to be down.
Do you know where I can get it?
Click to expand...
Click to collapse
You need to register and then download from here.
Thanks for that, I installed newest stock rom.
Could boot fine, set up the phone, put it to the side.
One hour later I checked it - same problem again.
Capacitive buttons flaring up, screen not.
Thanks for that, I installed newest stock rom.
Could boot fine, set up the phone, put it to the side.
One hour later I checked it - same problem again.
Capacitive buttons flaring up, screen not.
Then you should visit SSC. They can only repair your device.
I am using a One Plus One and recently flashed Cyanogen 12.1.
Something very interesting is happening:
One morning my phone's screen wasn't displaying anything yet the phone was obviously working. I know this because the hard-button lights were on and I could feel the vibration when I held down the volume button to put it into vibrate mode. I even pressed the buttons to take a screenshot and when I looked in my gallery later, it was there.
So the phone was functioning in every way except for the display.
To fix it, I tried rebooting. It didn't work. So then I went into TWRP and wiped the dalvik cache. When the phone rebooted, the screen turned on and everything worked as normal.
So the next morning, the same thing happened. It happened at the same time of the day, right after I woke up. It had been charging all night. I woke up to the alarm on my phone and the screen was on so that I could turn the alarm off. Then I turned the screen off. The next time I tried to turn the phone on, same thing... screen not on... dalvik cache... yadeeyadayada...
So I thought maybe it was charging my phone all night that caused it. So the next night, I didn't charge my phone overnight, and in the morning, the same result.
So then it occurred to me that it might be my alarm app (I use 'Morning Routine'), but even when I didn't use the app, the same thing still happened.
I read up online and followed so advice (turning off proximity sensor, disabling the "prevent accidental wakeup function"). The advice did not work.
I am at a loss and can only figure that my phone's screen not turning on is caused by having it off for quite a while (6-8 hours). And the only solution for it is wiping the dalvik cache. This is really annoying to do every morning considering wiping the dalvik cache results in all of my apps needing to be "optimized for android."
Any help would be great. Thanks!
XDA Visitor said:
I am using a One Plus One and recently flashed Cyanogen 12.1.
Something very interesting is happening:
One morning my phone's screen wasn't displaying anything yet the phone was obviously working. I know this because the hard-button lights were on and I could feel the vibration when I held down the volume button to put it into vibrate mode. I even pressed the buttons to take a screenshot and when I looked in my gallery later, it was there.
So the phone was functioning in every way except for the display.
To fix it, I tried rebooting. It didn't work. So then I went into TWRP and wiped the dalvik cache. When the phone rebooted, the screen turned on and everything worked as normal.
So the next morning, the same thing happened. It happened at the same time of the day, right after I woke up. It had been charging all night. I woke up to the alarm on my phone and the screen was on so that I could turn the alarm off. Then I turned the screen off. The next time I tried to turn the phone on, same thing... screen not on... dalvik cache... yadeeyadayada...
So I thought maybe it was charging my phone all night that caused it. So the next night, I didn't charge my phone overnight, and in the morning, the same result.
So then it occurred to me that it might be my alarm app (I use 'Morning Routine'), but even when I didn't use the app, the same thing still happened.
I read up online and followed so advice (turning off proximity sensor, disabling the "prevent accidental wakeup function"). The advice did not work.
I am at a loss and can only figure that my phone's screen not turning on is caused by having it off for quite a while (6-8 hours). And the only solution for it is wiping the dalvik cache. This is really annoying to do every morning considering wiping the dalvik cache results in all of my apps needing to be "optimized for android."
Any help would be great. Thanks!
Click to expand...
Click to collapse
Hello, and welcome to XDA!
Dalvik cache trick throws a wrench into things, but I used to have a similar issue with an older device - the screen wouldn't come one, but the hard button backlight would - pulling the battery and rebooting relieved the problem for that fit. I ended up scaling down the max processor speed (as it was being overclocked on the current custom ROM) back to the stock value. The problem went away at the point. But that was for my device, and because yours requires a dalvik cache wipe, it is probably a different cause.
At any rate, please go ahead and create an XDA account. Then, venture over to post in the [Q&A] Help thread. Ask away! (Noob friendly) thread, (or at least) in the > OnePlus One > ONE Q&A, Help & Troubleshooting forum. Your device experts can be found there.
Hope this helps, and good luck!
Hey, something's wrong with my phone.
When I turn off the phone, the display does not show anything, the touchscreen and buttons work, everything except the display. Black screen.
And when I reboot the phone many times, about 20-30 times, the display magically turns on and everything works fine. I wanted to know the problem in the display itself or all because of the battery. If the phone fully broken, then how after many reboots it turns on?
ps: The display does not turn off when I restarting the phone without turning it off
Iskak said:
Hey, something's wrong with my phone.
When I turn off the phone, the display does not show anything, the touchscreen and buttons work, everything except the display. Black screen.
And when I reboot the phone many times, about 20-30 times, the display magically turns on and everything works fine. I wanted to know the problem in the display itself or all because of the battery. If the phone fully broken, then how after many reboots it turns on?
ps: The display does not turn off when I restarting the phone without turning it off
Click to expand...
Click to collapse
you might have LED strip problem. not sure btw that I ever heard this problem before.