, I’ve got some skins too which work strange, could you pls take a look when you have some free minutes? Pls find attached. Omega shows an empty screen without hands, ant in the other skin they’re running in CCW direction. Thanks!
P40 : yes bad clockskin syntax again !! Added a check, should be ok for next release
P154 : normal behavior i’ve implemented the bug of direction to act like the normal skin engine… so you should correct the skin and add direction=2 on the last second item…
Many thanks! Ok, I see, I should learn a little bite about the XML watch format Well, the bigger second hand is now rotating CW, but the smaller one still CCW and the “battery hand” is “mirrored”. I hope, I will get 'em as well. And I’m looking forward regarding the new version - every version is getting better and better
regarding direction=2, ricktop : is it a bug / a feature or kinda workaround? I mean, I’ve tried to understand the XML format of clock skins and I’ve found this post on XDA: forum.xda-developers.com/smartwatch/other-smartwatches/clockskin-extracted-1-d5-firmware-t3295297/page4 They write that the default direction should be CW, direction=2 would be CCW. Am I on the wrong way? And what’s about the “mirroring” of the hands, for example the battery hand in P154?
I've explained this some post ago...
What you describe is the "normal" way of understanding the feature and the way i had implemented it first..
But the bug is that each direction=2 change the direction and each direction=1 does not.
So the first direction=2 makes it CCW the second CW, the third CCW ... This per rotate value for sure.
: is it a bug / a feature or kinda workaround? I mean, I’ve tried to understand the XML format of clock skins and I’ve found this post on XDA: forum.xda-developers.com/smartwatch/other-smartwatches/clockskin-extracted-1-d5-firmware-t3295297/page4 They write that the default direction should be CW, direction=2 would be CCW. Am I on the wrong way? And what’s about the “mirroring” of the hands, for example the battery hand in P154?
I’ve explained this some post ago…
What you describe is the “normal” way of understanding the feature and the way i had implemented it first…
But the bug is that each direction=2 change the direction and each direction=1 does not.
So the first direction=2 makes it CCW the second CW, the third CCW … This per rotate value for sure.
Oh yeah! “Reimplementing the bug” - now I understand what you meant!
Got it, thx! What’s about “mirroring”? Dou you know perhaps how to fix?
UPD. Got it too And I could reproduce the bug you mentioned above. The clockskin bug in P154 was not the missing direction at the second hand, but the false direction at small hand above. After I have adjusted it the follwing directions were changed automatically.
I do have sim card and I have no problems after restart with changing faces (note however that I don’t have pin enabled)
I’m not using the watch (Lemfo Les1) with SIM. After restarting, the selected face loads up, but if I want to change it, I have to select and restart again; everytime I change the clock face.
Update: I followed steps to uninstall in linked video and so far it’s working. I will check more tomorrow. It’s late in the night here in California.
Update 04/27/17 - I powered off the watch before going to bed last night, and turned it back on this morning, to discover that the issue with changing (swapping) faces is back again. Like I said yesterday, I followed every step in the video link pointed above in this thread, to uninstall the old installation. It did work fine for the rest of the afternoon and evening yesterday. But I am bak to square one. Anybody else experiencing the same?
Apr 27, 2017 6:37:00 GMT 1oscarhmeza said: I'm not using the watch (Lemfo Les1) with SIM. After restarting, the selected face loads up, but if I want to change it, I have to select and restart again; everytime I change the clock face.
Update: I followed steps to uninstall in linked video and so far it’s working. I will check more tomorrow. It’s late in the night here in California.
Update 04/27/17 - I powered off the watch before going to bed last night, and turned it back on this morning, to discover that the issue with changing (swapping) faces is back again. Like I said yesterday, I followed every step in the video link pointed above in this thread, to uninstall the old installation. It did work fine for the rest of the afternoon and evening yesterday. But I am bak to square one. Anybody else experiencing the same?
Yes, as explained in one of my previous posts, I also have the same issue.
When I shut down my watch in the evening and reboot in the morning, I cannot change watchfaces anymore although that worked perfectly before. Also the battery, weather and temperature tags are not updated anymore. I also have the impression the battery drain is must bigger then (15% drop in 1 hour).
When I click the ‘Uninstall me’ option of the launcher and then click on the WatchClockSkin shortcut in the apps list (to restart the launcher), I get a black screen instead of showing the watchface.
I also tried the ‘Reboot’ option, but that solves the issue only partially: the battery, weather and temperature tags are updated but still cannot change the watchfaces.
The only option to solve the issue completely is by uninstalling the launcher and reinstalling it again.
So something seems to go wrong in the launcher when rebooting after a complete shutdown of the watch …
I have a Domino DM368 watch with launcher v2.1.4.
Ricktop, is there something we can test for you to better understand and fix this issue ?
I do have blitz but never encounter battery drain to much when phone is on idle mode, when it comes to bugs yes but not what you mention, on my end its seems it just some minor adjustments, perhaps we neef to considrr the plafort is that adroid 5 upward or kitkatt. Try only two or 3 faces
No clue what happened overnight. Yesterday and after reinstalling the launcher my troubles when changing faces had gotten away, but now I am having the same issue again; I must reboot the phone for the face to change to the new selected one.
I have seen this reported by someone else. Is there a permanent fix? Lemfo Les 1.
same problem with LF16. Noticed some error log generating in my watch - see the attachment
I’ve root on smartwatch and tried RootUninstaller for this task. Also tried manually copy file com.ClockSkinCoCo.apk in folder /system/priv-app. Right 644 root:root
Yesterday I run out of battery and when I boot it today I had same problems (unable to change skins, temp, battery etc stuck, notifications not shown etc). Restart didn’t help.
I follwed this video www.dropbox.com/s/8lv3pz75lzotyjd/2017-04-24%2019.09.59.mp4?dl=0 posted by yawa with two additions:
reboot after wiping data & uninstalling launcher
please pay attention to 1:59 at this video. yawa clicked on open but I clicked on OK instead. After that you will be returned to stock launcher. Now push the button and you should be asked to choose launcher and there will be “always” option. Allow permissions it asks.
After that all the things just work (skin changing, indicators, notifications etc).
ricktop can all this have something to do with permanently stored prefs of launcher? (like corrupted db or other file) Some bad behaving code run on initial run? (or bad skin wreaking havoc… Before my watch died on me II was modyfing .watch files and some bad or unsupported xml could have broken internal things). It looks like when launcher breaks it will stay broken until (very) clean reinstall
How do you make your launcher permanent. Mine keeps switching back to the factory launcher when i push the button. I have to restart your launcher and hit the button again. I have LF16. Using 2.14.
I thought there was some way to toggle between them. I selected both during install.
clicked on open but I clicked on OK instead. After that you will be returned to stock launcher. Now push the button and you should be asked to choose launcher and there will be “always” option. Allow permissions it asks.
After that all the things just work (skin changing, indicators, notifications etc).
ricktop can all this have something to do with permanently stored prefs of launcher? (like corrupted db or other file) Some bad behaving code run on initial run? (or bad skin wreaking havoc… Before my watch died on me II was modyfing .watch files and some bad or unsupported xml could have broken internal things). It looks like when launcher breaks it will stay broken until (very) clean reinstall
N.
So now - after a clean install - everthing is working fine on your watch, right ?
What happens if you - in that state - shut down (so not reboot, but complete shutdown) your watch and then start it up again ?
On my watch (Domino DM368) I get back in the erroneous state (so unable to change skins, temp, battery etc stuck, notifications not shown etc).
Can you please try ?