Hmm, maybe you forgot to perform a factory reset after updating?
1 Like
No, i did The factory reset.
The watch rings with signal but the screen does not wake up. This is with simcard installed, 4g.
Yes. I Will try a new factory reset and see in problem persist.
Factory reset fixed it. It is not really fast, takes about one second to wake after first signal. Could be faster.
The one second doesnt bother me . There are lots of odd jobs i can be doing while i wait for the second to pass 
2 Likes
It takes a little longer than the original firmware because the watch never slept deeply before. This has been changed to greatly improve battery life. One second is ok for me.
2 Likes
Yes, the âwake screen for notificationsâ option is enabled. Today the same thing happened again without doing anything, just pressing the power button or double tap without apparently turning on the screen. But in the dark, I checked that the black color of the screen when off is different from the black when the top button is pressed, itâs like something more gray or blurred, that is, the screen works but without backlight.The first time happened without software installed, one hour after upgrading to FAW 1.2. It never happened before with FAW v1.1.
Install ringtone with a 1 to 2 second delay. Then you always have a picture when the Smartwatch rings. 
4 Likes
I noticed that if I close all recent apps, the phoneapp closes too. So recieving a call takes 4-5 sekonds to wake screen. But if I dont close recent apps (including phone-app); the watch wakes up after one second when incoming call.
The delay is 4 seconds in LEM14 with FAW1.2. In FAW v1.1 there was no delay, 0 seconds. If we add these 4 seconds to the time it naturally takes to react, look at the screen, touch to answer, it can take 7 or 8 seconds. I know people so impatient that they sure donât wait that long 
. But the most serious problem, in my opinion is when the screen doesnât light up when you try to use the watch, whatever you do, so you have to hardware shut down - 10 seconds with the power button pressed. Maybe a system log can bring some âlight in the darkâ? 
In my case the delay is 4 seconds always, no matter weather I close or not recents apps. Just tested.
I would send the photo to after-sales@kospet.com and ask them if they can replace it.
In my opinion that yellow tint is not normal and you can clearly demonstrate it with this picture.
You have obviously factory reset after updating to confirm the problem?
Sorry if you have already answered the questionâŚ
I was wondering if you could disable double tap to wake and any lift to wake or wake up screen for notification?
One at a time and reboot each time.
Trying to understand if there is a bug in the touch panel driver.
Or factory reset and do not change any display settings and check if the problem still persists?
No apps⌠Nothing.
Just to see where the problem is.
Cheers
Yes, factory reset is mandatory because otherwise the power button does not activate the long press, as other guys and myself have already checked.
About the test you propose, thatâs exactly what I started to do this morning: I disabled âlift to wakeâ, and left âdouble tap to wakeâ enabled. âwake up screen for notificationâ was not in the plans for this test, but I include it as you suggested. I do one disable at a time and in each phase I will test with everything I can for 4 or 5 hours. Then, if there are no definite conclusions, I will do the factory reset as you suggest, without changing any screen options or software installation. Thanks for the suggestions to try to find the cause of this problem.
This might help to track down the problem.
Seems like the same behaviour as on my smartphone, first the vibration appears and a second later the screen gets enabled.
2 Likes
@Pablo11 The first test I did was with the following options: âtap to wake: enabledâ; âlift to wakeâ: disabled ; âwake up screen for notificationâ: enabled. After receiving a call, at the end the screen turned off and no longer turned on with the double tap nor with the button. In that state I connected the watch to the computer via USB and fortunately I was able to blindly tap on âacceptâ to start the bugreport. I PM the link to the file.
I understand, but in that case the watch would not respond to the touch on the screen, and in my case I can hear the clicks when I interact with the screen. I can also receive calls, listen to music via bluetooth, etc. The problem is that the backlight does not come on, everything else works. You can see how the deep black color when off changes to an almost gray black, and goes back to black when I press the power button.
In the crashlog folder I donât have any files from today, only from August 10, and the problem just happened half an hour ago. Does that mean itâs not a problem with the launcher?
The black display indicates a problem with the launcher that has crashed and canât be properly restarted.
Those crashes happen because some apps are behaving more differently than anticipated, very often the problem is just a missing null pointer check.
1 Like