Hi guys.
I got an issue of screen time out timer.
Sometimes it works but mostly not.
Display isn't turning off at all.
Sometimes it's turning off like normal (set at 1min) but sometimes not turning off at all.
It's all happening with any notifications (not specific one).
Can't find the reason it's happening,
Even made a clean flash and nothing changed
Need advice.
Thanks.
Related
Since Sprint is going to try and screw me big time if I get a new phone, I've decided to see what new life I could put into my old Touch Diamond (DIA500). I installed XDAndroid FRX05, and it seems to be working really well, with a few exceptions. One of the first things I tried was to enable Bluetooth. What happens is that it enables, but about 4 seconds after being enabled, it says it's shutting down, then it starts back up, and shuts down. It keeps doing this forever, until I turn it off. Now that I tried Wifi, it does the exact same thing. I've rebooted a few times, and took the battery out once, but still nothing. I've since installed a battery-saving program, but this happened on a fresh install.
The next issue is with the backlight. If I try and change the brightness, it changes for a second, then goes back to the brightness it was. It does this whether I turn the brightness up or down. It's not set to auto.
The third issue is the GPS. It works, but seems to take a long time to get a lock. Under WM, I'd have some kind of location within seconds, even inside. I'm guessing it was using the phone network to speed things up. Under android, it takes a few minutes sometimes, and it's worse inside.
I also had a nightmare calibrating the screen. It's still a little off, but it works. Does anyone know a screen calibration program that would work?
Any ideas?
Thanks!
To solve the brightness problem. Boot WinMo and turn off auto brightness there. That will solve that problem.
Thanks for share you knowledge here DA01
Hi again. I'm having a very weird issue, and I thought it was related to my camera problem [now partially solved] because this started happening after the camera incident. The screen will suddenly and randomly turn off, or switch to the highest brightness. To fix it, I have to lock the screen, then unlock it.
I searched and this thread showed up. It's exactly my problem, but I can't do what he did, since I'm not in Brazil. I'm running Kang's CM7.
Is the latest fix important? I haven't installed it because I'd have to wipe everything [again] and I'll need a whole weekend to get my stuff together once more, but if this is key to fix the screen, I'll do it.
I have the same problem, I havent found a solution. Have you found a solution?
Same for me
Same problem for me... the screen suddenly set to highest brightness (only sometimes) and after a few seconds, the screen turn off itself. Sometimes turn on itself in 10-20 seconds but already times, I need lock it (with power butom) and unlock again.
I was testing with a bounch of ROMs (CM7, GB, ICS, etc), but problem always is present. I was cleaned the usb port pins (see that solution from other post) and nothing happen.
...sorry for my english
You can try to reflash the stock rom from www.samfirmware.com based on your region..
I have a strange problem, well a few. If I lock my phone (C6903) using the physical button I can't unlock it again. I try for about 5-10 minutes sometimes and it just wont work. If I hold it down I can feel it vibrate as if it's bringing up the power menu but the screen just stays black. Eventually it will randomly wake up then I can play around as normal. If I leave it to lock itself I can unlock every time, fist time no worries. This is what pointed me to it being a SW problem rather than a hardware problem.
I also noticed that when I do have the screen turning off in the dark, I can see that the screen is still lit up! Just it is black, not completely asleep. It's really quite bright when I have it next to the bed. Also when I am outside I can't see the screen at all really, even with the brightness turned right up.
It's really strange all these happened about the same time. I figured maybe it was a ROM problem and a fresh install of stock ROM would help. Tried it and at first most of these problems went, just the fact I still couldn't really see the screen in the sun. I tried another ROM and at first was just the same but then these problems started again.
Has anyone had any or all of these problems or got any ideas what it could be? I am left thinking now that the problem is more likely hardware related as the problems are so sporadic and happen whatever I have installed.
Any help / suggestions would be appreciated but I have the feeling I will have to just admit the phone is dogged
You say that most of the problems desapararecen to install a new ROM, it is likely that installing something extra to be the cause, I was introduced me something similar with Expoxed Notifications Module.
Try a clean installation without installing test applications to determine if the problem recurs.
Thanks, yes I guess I will try that, bit of a pain having to reinstall apps after every install and restoring messages etc so I might just put up for now.
I also have realised that the screen not turning on and the screen staying on but black happen at different times. i.e. I can now randomly turn the screen on and off no problem (don't think I have installed or deleted any apps or changed anything), but the screen stays awake when off. When I was last not able to turn the screen back on after turning off the screen actually went to sleep. Very strange
Using the ROM][GT-I9305][Marshmallow][6.0][Cyanogenmod 13.0][UNOFFICIAL] with pleasure
No problems, battery uses more when there is no wifi around, but I guess that is normal?
The only problem I had was that the screen did not rotate, after boot it worked for a while, then stopped.
The fix for that, well, it works for me is to change a setting:
In the Developer options turn on the Multi-windows mode, you will get a message that it may cause some problems, but I did not notice that.
But it fixes the screen rotation, it works perfect now!
(My first posting on XDA)
I've searched far and wide and can't find a solution for this issue.
Here is what happens: for no reason that I can see (no new notifications), my screen turns on its own. My phone is just there on the table when this happens and I haven't touched it.
This happens whether the phone is plugged in or not. It happens in the middle of the night and wakes me up.
Things I came tried:
- turn on do not disturb and remove all exceptions.
- disable always on display.
- disabled all lock screen notifications.
- disabled a notifications.
Other things I've tried:
Lift to wake and all other things that could wake the screen.
Did a factory data reset and re setup my phone from scratch.
Nothing works. Can anyone please help me?
Thanks in advance.
I had the very same problem until a few days ago when this behaviour suddenly stopped. What changed? I had shutdown my Pebble watch and connected a Wear OS watch to my phone.
I don't know what the Pebble did, but it looks like it woke up my phone at random intervals.
Maybe it a bluetooth device you've connected?
I'm expeciencing sometimes this behaviour when listening to the music on bike with phone in pocked on back. I disabled all "smart" funcions like smart lock, pocket detecting, wearing detection etc and it stopped.
I think it is caused by new type of proximity sensor used in whole S10 line (so I think it is hw related). I read somewhere than it detects skin proximity even thru several layers of cloting.
It is behaving strange even during phone calls - when put phone down from my ear, it tooks several seconds until screen lights on.
it's one of the things that bothers me a lot about otherwise great phone.
facing same issue
I always loved Samsung galaxy s10. I bought it from my friend who used it for 10 months. I am facing the same issue first I thought it is because he used it for 10 months and some bug appeared but now I came to know its not just me. if anyone knows how to fix it then please post a reply. I really need to fix this
I haven't noticed that on my S10. It sounds like something is triggering it, but what. Do all of you use Bixby because I don't.