Hi all,
i have the Kaiser for a week, and was thinking the batterry autonomy isn't especially amazing..
Then doing some research, i've found out that that despite the backlight setting set to be turned off after 30 sec, it was NOT turned off.
Switching setting to 1 min doesn't help either.
Setting it to 10 sec DOES work, the backlight turns off after 10 secs, BUT turns back ON after various seconds (sometimes +/- 11 secs, sometimes after 21 seconds...), then 10 secs later again off, etc etc... (cycle forever).
I did removed from the today screen both SPB Mobile shell and HTC Home (today screen = blank). But the problem is still there...
so the questions :
1) Does anybody experience that (it took me a full week of use to note this... can you try it on your Kaiser ?)
2) Any idea/solution to fix this ?
Best Regards,
Mike.
Just letting you know, that mine works as it should.
I dont have that bug .... but another bug:
After soft-reset, the battery backlight will be set to 10 seconds.
No clue yet why that happen.
When having issues like that try a hard reset and do not use a back up just set everything back up by hand. I found that most apps still are not ready for WM6 just yet since it really is a new OS even though we have had it for what seems like a very long time now.
Hi
Then doing some research, i've found out that that despite the backlight setting set to be turned off after 30 sec, it was NOT turned off.
Switching setting to 1 min doesn't help either.
Click to expand...
Click to collapse
When you set the back light to turn off, it doesn't actually turn off, instead it drops to minimum brightness. If you are in darkish room and so have the backlight set to minimum anyway, it looks like it isn't going off.
This is by design for Windows Mobile 6 devices, the Toshiba G900 was exactly the same. I can only guess it is because the screens are not trans-reflective, so they dim to the lowest level so you can still make out what is on the display and can tell it is still on, rather than in standby. This makes the behaviour seem similar to those moving from trans-reflective displays as while the backlight could go out completely, you could still make out what was on the display.
Regards
Phil
[UPDATED]
Fixed in 4.2.2 update
THIS ONLY SEEMS TO DO IT IN LANDSCAPE MODE!?!?! WTF!?!?!?
This may seem minor to most of you but I use this to time my daughters physio exercises.
Can someone please try this out? Set screen/display timeout to 1 minute. Go to standard clock app. Swipe sideways to countdown timer. Set timer to 00:05:00. Start timer. Leave the phone for around 2 1/2 minutes (so display times out and phone locks). Unlock phone.
How many of you now have 12 hours left to go!?!?
Or is it just my phone randomly adding 12 hours to the countdown when the screen is off? :silly:
Mine did not, but I'm not sure if we have our locks set to the same action. I set my phone to require a pin after 15 minutes of the screen being off, how do you have yours set so I can mimic your settings?
No screen lock, sleep 1 minute.
Updated
Only seems to do it in LANDSCAPE mode!?!?
I can't manage to reproduce the bug on my end, but then again, I'm on a Sprint model.
Hi,
Since upgrading to Tizen a couple of weeks ago, I've had a couple of occassions where the screen has stayed on and not dimmed or turned off.
I only notice it because I get the low battery warning and think it shouldn't be dead so quickly. I then watch it for a bit and notice that it doens't dim or turn off. Changing the screen timeout from 10s to something else and then back doesn't make any difference.
A reboot lets the screen timeout work as normal again.
I probably looked at the watch a few times whilst it was stuck on and just thought that it had been triggered by the movement sensor.
Anyone else have this problem?
Didn't have this problem under Android (had the watch since November last year)
This morning my AT&T Galaxy S6 drained 15% battery in 1 hour with wifi and data turned off and hardly any screen on time.
Not normal behaviour for this phone. I powered it off and then turned it on and now is stuck at the white At&t screen and keeps repeating a vibrating pattern. The pattern is like this. 1 short vibration -pause -1 long vibration -pause -3 short vibrations. And the blue light on the phone's top dims down and up slowly.
I got into Android Recovery and wiped cache but it gets stuck on the same screen.
Phone has stock Android. Last update was 2 months ago from At&t.
I don't want to factory reset so I don't delete all the pictures on it.
Can I use Android Recovery and ADB to download the pictures to the computer?
Cheers!
Any one knows what the vibrating pattern means?
Does anyone else have an issue with the screen going black randomly? When I attempt to unlock my Mate 20 Pro from lock screen I have been getting a black screen. Nothing works. I can hear clicking while I am touching the screen but nothing happens. No particular app running or starting just when I unlock the screen using fingerprint. First time it happened was a few weeks ago and I didn't think much of it. Then it started to happen more frequently a few times per week (5-6). Now it seems to be getting worse 10-15 times per week. I am at a loss to explain why this would happen. I just keep on hitting the screen randomly, pressing the on/off toggle several times. Eventually after about 3-5 minutes the phone screen re-appears.