HELP THREAD : IMILAB KW66 Smart Watch- Screen Flikering - General Questions and Answers

Hi, I am using the KW66 smartwatch for 6 months. A few days back, the screen of my watch starts flickering on white color. I have tried resetting the device but nothing happened. can somebody guide me? I have also written a complaint on Gloryfit App but no reply so far!

IMO screen flickering doesn't come out of the blue.
Screen flickering issue is associated with software malfunctions usually get resolved by performing some workarounds. But your chance of obtaining quick and ultimate solution is higher if you could pinpoint the root cause. And this is what you should do first. To help you isolate the problem, try to think of what has happened before the onset of the problem. For example, did your watch's screen start to flicker after making some changes to the display settings or options other than the brightness level? Or did it begin to occur after installing a new app, contents, or Android update? Prior actions are usually the trigger so that is what you need to find out first. Among the possible triggers for you to consider would include but not limited to rogue apps, corrupted files like photos and videos, broken segments or files in the SD card, and software bugs. Once you’ve successfully dealt with the culprit, you’ll finally find the remedy.

I am attaching snapshot of problem for your kind perusal

Can you upload a video of the screen flickering here or else can you send it to below mentioned mail plzz??
[email protected]

Im having the same issue. Can i get solutions for this??

I have the same problem. Firmware: V003129
The light is very low. It is not very bright at 100% brightness.
It also features vertical lines as "shadows"
I would appreciate if someone can help me.

juan_speed said:
I have the same problem. Firmware: V003129
The light is very low. It is not very bright at 100% brightness.
It also features vertical lines as "shadows"
I would appreciate if someone can help me.
Click to expand...
Click to collapse
I am unable to upgrade the firmware on Gloryfit app. It says newest version detected and doesnt give any option to upgrade. updated the app from playstore but still no firmware upgrade fr the watch through gloryfit app.. any workaround ??

Related

[FIX] Burn INs/Dead Pixels/Other Display Glitches FIX

Hello everyone,
I saw multiple threads already opened for the burn in issue (which I also have from time to time) and I wanted to share my solution with you. It is a simple video, which is changing the three main colors (RGB) very fast. Played for 5-10 minutes on a loop will erease any glitches on your screen (softkeys burned into the screen which is the most commen problem).
Here is the link in youtube:
http://www.youtube.com/watch?v=liMySLZkF5o
Here is the mp4 file to upload directly on your device:
STUCK PIXELS or BURN INS RGB VIDEO FIX
http://www.megaupload.com/?d=878ZGHF0
To the Moderators: I searched over the forum for a solution and did not find it, I hope I am not overlaping with another old thread, just wanted to help.
Regards.
Hi
I don't mean to thread-crap
but....
after having discussed this issue with HTC themselves they have said its a hardware based issue
whilst its true running a slide show/video full screen displaying solid blocks of colour are likely to erase screen burn-in, the issue will still persist, the underlying cause is a faulty screen panel which must be replaced
Could you upload it somewhere? I could use it, i have a stuck pixel. It's blue on a black background, it should fix it.
I once fixed a big bright spot on a LCD TV with one of these RGB movies.
Hi duke_stix, I agree with you that it could be a faulty display panel, but however I didn't find anyone had it replaced due to that issue. And I know it is a temporary solution, but at least there is a solution
AndyJ91, download link available, hope it helps.

[Completed] Auto Brightness Issue on Sony M4 Aqua Experia

Hello XDA Dev, I am new here and don't know where else to go for advice.
I recently aquired a Sony M4 Experia Aqua (E2303 I believe) and the brightness is stuck on full brightness all of the time. I have tested to see if the auto brightness hardware sensor was still working and the values change whenever I cover it or remove my hand, so it looks like a software issue. I did a factory reset, reinstalled the OS using the software 'Xperia companion' and I still have the same issue - full brightness. I have however, managed to obtain an application that dims the screen brightness, it's called 'Night Mode'. It's sorted it out, so the phone doesn't burn my retinas every time I look at it in the morning, but I can't let go of trying to fix this. I have looked everywhere online, many people say they have the same problem, but they never seem to come up wth or find a solution. I really liked the adaptive brightness on my other M4 Aqua, I got this one as a replacement. I have a Samsung phone with a decent Android set up on it, so I wondered if I could transfer the OS from that phone to this one?
Disjunctive said:
Hello XDA Dev, I am new here and don't know where else to go for advice.
I recently aquired a Sony (E2303 I believe) and the brightness is stuck on full brightness all of the time. I have tested to see if the auto brightness hardware sensor was still working and the values change whenever I cover it or remove my hand, so it looks like a software issue. I did a factory reset, reinstalled the OS using the software 'Xperia companion' and I still have the same issue - full brightness. I have however, managed to obtain an application that dims the screen brightness, it's called 'Night Mode'. It's sorted it out, so the phone doesn't burn my retinas every time I look at it in the morning, but I can't let go of trying to fix this. I have looked everywhere online, many people say they have the same problem, but they never seem to come up wth or find a solution. I really liked the adaptive brightness on my other M4 Aqua, I got this one as a replacement. I have a Samsung phone with a decent Android set up on it, so I wondered if I could transfer the OS from that phone to this one?
Click to expand...
Click to collapse
Greetings and welcome to assit. Unfortunately I don't think there is a way to transfer the os but you could install a custom rom from here
http://forum.xda-developers.com/m4-aqua/development
and see if that fixes the issue. Also there is an app called lux on xda/playstore that may help
Good Luck
Sawdoctor
sawdoctor said:
Greetings and welcome to assit. Unfortunately I don't think there is a way to transfer the os but you could install a custom rom from here
http://forum.xda-developers.com/m4-aqua/development
and see if that fixes the issue. Also there is an app called lux on xda/playstore that may help
Good Luck
Sawdoctor
Click to expand...
Click to collapse
Thanks for getting back to me. I will check out the link.

[HELP] Partially Blank Screen but otherwise active device OR Sleep of Death

Hello everybody,
I've got a problem with a Oneplus One.
First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. So I'm quite used to replace the display on this device.
Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.
Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).
I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.
A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!
An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.
As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.
Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.
I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.
I also tried to install different original factory images.
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip
and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.
I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.
I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.
I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.
Unfortunately I've got no luck.
Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.
So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.
I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?
thanks!
p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.
I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...
Maybe there is a problem with permissions or the flash memory?
p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
pesche80 said:
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
pesche80 said:
Hello everybody,
I've got a problem with a Oneplus One.
First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. So I'm quite used to replace the display on this device.
Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.
Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).
I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.
A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!
An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.
As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.
Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.
I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.
I also tried to install different original factory images.
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip
and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.
I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.
I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.
I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.
Unfortunately I've got no luck.
Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.
So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.
I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?
thanks!
p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.
I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...
Maybe there is a problem with permissions or the flash memory?
p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX
Click to expand...
Click to collapse
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Click to expand...
Click to collapse
Thanks!
I'm going to consider a new display... but not a new gf
pesche80 said:
Thanks!
I'm going to consider a new display... but not a new gf
Click to expand...
Click to collapse
Don't forget to invite me to your wedding.

S7 Strange Screen Flickering

So I bought my used S7 recently, the device seems to be totally clean not even a scratch on the frame, looks like brand new and even the software status is OFFICIAL not even the Knox is tripped.
I found a thread on XDA about using an updated version of TouchWiz Home of the S8 for the S7 by installing the APK.
it worked like a charm until I started to change my wallpapers and notice something strange.
im using an application to change the wallpapers auto every 5 minutes, the problem is whenever the wallpaper i use has some bright colors like bright purple or bright red and i press the app button to access the app drawer those colors (ONLY) flicker , they flicker just before the screen get blurred and take u to the app drawer, and also when u go back to the main screen from the app drawer also right after the blur disappear.
i got scared so i uninstalled that Touchwiz Update and came back to stock, to notice that the problem is still there, but its not as noticeable as the s8 TW
i wanted to know if the screen is dying or this is something normal, and also wanted to know if its a software related problem or hardware one, and finally if someone is having the same issue ( i can share a wallpaper if anyone is willing to try wit it )
NB: the screen flicker ONLY ON THE BRIGHT COLOR before the blur effect happens and After it.
Thank you all in advance & i apologize for my English
I made this video If you focus on the second time especially ( when going to the home screen from the app drawer ) you can see clearly the red rose flicker. Sometimes the flickering is harder depending on how bright is the color.
https://i.imgur.com/cuO7BBU.png
This can only be a software problem, because its also visible in the Video. Your screen is not damaged, and it will not be damaged. This issue is not a problem, maybe only a bit annoying.
profi_fahrer said:
This can only be a software problem, because its also visible in the Video. Your screen is not damaged, and it will not be damaged. This issue is not a problem, maybe only a bit annoying.
Click to expand...
Click to collapse
It is so annoying for me cuz i had an old S5 plus that ended up with the screen flickering so whenever i see it flickering i got a heart attack.
Is there anyway to fix it i tried factory reset but nothing changed..
Thank you anyway for replying
I think thats a Problem with the Launcher. I've tried it on my Phone, and it is also flickering. You can try to speed up the Animation-Speed in the Developer-Settings. Maybe then you wont see the flickering.
You can see it here, that it is also on my phone: https://photos.app.goo.gl/nYKM5ss9EKe3L0M43
profi_fahrer said:
I think thats a Problem with the Launcher. I've tried it on my Phone, and it is also flickering. You can try to speed up the Animation-Speed in the Developer-Settings. Maybe then you wont see the flickering.
You can see it here, that it is also on my phone: https://photos.app.goo.gl/nYKM5ss9EKe3L0M43
Click to expand...
Click to collapse
Thank you very much !!!! You have no idea how much its relieving to know that this problem is not only present in my device.
For now ill just stay away from bright wallpapers until hopefully Samsung will make fix for this issue.
Thank you again !
EDIT : after i came to the pc and i saw the GIF u made i noticed that we dont have the same flickering , maybe the quality of the GIF wasnt high enough but for me it didnt seem to be te same, so i will ask you one last time when you tried that wallpaper did it show the SAME result as my video for u ?
thank you in advance

Question Screen dimming in the sun

Hello everyone,
anyone experienced the main screen dimming to a very low brightness level " in the sun " and no difference happens if i switched off adaptive brightness and got it to the max. I am not sure if that is related to the phone heating, but in general sometimes it dims very quick without even having the phone that heated.
OR maybe the phone gets heated very fast with simple use in the sun light.. any experiences related to that issue ??
Thank you great people.
Can't confirm your observation ... . But there is an option to dimm the screen in the settings of the energy or battery saving mode.
m.
It's a false positive from the light sensor. Some phones add a special setting to increase the brightness when it's overly bright to offset it, but I haven't come across one for this phone. It's a little impressive that so few phones actually address it after it's been a known issue so long.
I thought this issue was fixed already... what sw version are you on? share the device' model number as well please.
Additionally, submit error report to Samsung Members after reproducing the issue, you should be able to get guidance on how to get the fix...
meduza said:
Can't confirm your observation ... . But there is an option to dimm the screen in the settings of the energy or battery saving mode.
m.
Click to expand...
Click to collapse
no that is not the case, it happens even when not enabling the power saving mode.
twistedumbrella said:
It's a false positive from the light sensor. Some phones add a special setting to increase the brightness when it's overly bright to offset it, but I haven't come across one for this phone. It's a little impressive that so few phones actually address it after it's been a known issue so long.
Click to expand...
Click to collapse
so do you mean there is a solution or it is just a bug with the sensor ?
TheNewGuy92 said:
I thought this issue was fixed already... what sw version are you on? share the device' model number as well please.
Additionally, submit error report to Samsung Members after reproducing the issue, you should be able to get guidance on how to get the fix...
Click to expand...
Click to collapse
can you tell me how to submit this error report ? is it through the samsung members application ??
also the model number is SM-F711B
software version is android 11.. one ui 3.1.1 ..
k.a.h said:
so do you mean there is a solution or it is just a bug with the sensor ?
Click to expand...
Click to collapse
It's a bug that should have been fixed already.
twistedumbrella said:
It's a bug that should have been fixed already.
Click to expand...
Click to collapse
Sadly its not fixed at my side !
k.a.h said:
can you tell me how to submit this error report ? is it through the samsung members application ??
also the model number is SM-F711B
software version is android 11.. one ui 3.1.1 ..
Click to expand...
Click to collapse
If you don't have Samsung Members app installed then go to Galaxy or Play store and download it. In the app, click the Blue circle with+ icon. Then select Error Report.
Provide as much detail about the issue as you can and if possible include any screenshots or screen recording (make sure it's 1 issue per ticket).
Sorry for the late Reply... hope this helps and any future issues, submit a ticket as your first step so Samsung can start working on the issue while you look for work arounds or fixes
It might be a bug related to overheating. Had that happen to mine. The phone becomes too hot and dims the screen, turns off multi-window.

Categories

Resources