yes,but your job is still amazing!
About the comments i forgot to mention that the comments are in chinese and not only on clock_skin.xml.
i didn't checked with english comments because the face which is not working has chinese comments and i did not check the working ones if the had english comments or not.
Thanks again for your GREAT job.
I’ve checked again and 2.0.1 is filtering comments, can you send me the link to your skin ? Thanks
I had only one suggestion.
In tops screen where are some settings shortcuts, you have only for two sound mode, silent and vibration mode.
If you enable one let say the vibration mode, I suggest if you tap again it disable and come back to full sound mode.
Hi Ricktop, thank you for your amazing work!! Your launcher makes our watches complete
I have been using the 1.1.8 version on my IQI i3 and it worked just as it was supposed to. When I switched to the new 2.0 version, I first noticed very high battery usage. Told myself that it was probably due to playing around with new watchfaces, using wifi and so on. But battery drain continued (my estimate would be that battery life was halfed). After installing the updated version of 2.0 the watch started going crazy. A watchskin (.watch format) that had worked before suddenly showed up wrong (bottom left corner ) , then the watchface started zooming in and out by itself, blinking, very much crashlike behaviour. I was still able to uninstall and went back to old 1.1.8 version. Everything normal now. I will try again tomorrow with the updated version and see if it works.
Is there anything i can contribute to further the development of this project (crashlog or some such)?
Also, could you share the watchskin that you used for the second demo? That’s exactly what I’ve been looking for!
Anyhow, thanks again for your launcher, keep up the good work!!
I have been using the 1.1.8 version on my IQI i3 and it worked just as it was supposed to. When I switched to the new 2.0 version, I first noticed very high battery usage. Told myself that it was probably due to playing around with new watchfaces, using wifi and so on. But battery drain continued (my estimate would be that battery life was halfed). After installing the updated version of 2.0 the watch started going crazy. A watchskin (.watch format) that had worked before suddenly showed up wrong (bottom left corner ) , then the watchface started zooming in and out by itself, blinking, very much crashlike behaviour. I was still able to uninstall and went back to old 1.1.8 version. Everything normal now. I will try again tomorrow with the updated version and see if it works.
Is there anything i can contribute to further the development of this project (crashlog or some such)?
Also, could you share the watchskin that you used for the second demo? That’s exactly what I’ve been looking for!
Anyhow, thanks again for your launcher, keep up the good work!!
Cheers, wokuvision
I too have the power drain issue. I have been using it for a few days and I too estimate it is half of what was before. I did not change anything other than the launcher. So my battery life is now half of what it was. Interesting since Eric said it should be better. But for me it is worse.
Eric, check this clockskin out. It really freaks out your launcher. Keeps crashing it over and over when trying to load it. Had a hard time to get it back running. It was even impossible to select another watch face skin. Try it at the link below. It is called ORANGE GLOW
not working on my lemfo lem5… the launcher is not showing fullscreen and round (it’s not centered but in the bottom right corner), but square and glitchy, even if the screen setting is fullscreen
Hi Eric, Great job with this one! I love it so much.
It gives my watch the functionality I always wanted. I still have one (severe) issue - it seems that whenever I run you launcher, I get about 50-60% less battery time. Normal operation gives me about 15-17 hours. Yesterday I got about 8 hours until the watch came into power saving mode
Any ideas?
I have been using the 1.1.8 version on my IQI i3 and it worked just as it was supposed to. When I switched to the new 2.0 version, I first noticed very high battery usage. Told myself that it was probably due to playing around with new watchfaces, using wifi and so on. But battery drain continued (my estimate would be that battery life was halfed). After installing the updated version of 2.0 the watch started going crazy. A watchskin (.watch format) that had worked before suddenly showed up wrong (bottom left corner ) , then the watchface started zooming in and out by itself, blinking, very much crashlike behaviour. I was still able to uninstall and went back to old 1.1.8 version. Everything normal now. I will try again tomorrow with the updated version and see if it works.
Is there anything i can contribute to further the development of this project (crashlog or some such)?
Also, could you share the watchskin that you used for the second demo? That’s exactly what I’ve been looking for!
Anyhow, thanks again for your launcher, keep up the good work!!
Cheers, wokuvision
Yes to help, you can share the link if the non working skin. Battery life is eaten mainly in my case by internet over bluetooth and wrist screen on. If I Don’t use that i get normal life Time.
Hi Eric , this is only an observation , I notice that during the swapping of clockskin from time to time sometimes cause some erratic clock positioning, so i need to go to default skin and delete the watchtmp and restart the wathch to work it again. doest the engine needs lots of space for temp swapping?
Mar 17, 2017 19:10:40 GMT 1pxeno1966 said: yes,but your job is still amazing!
About the comments i forgot to mention that the comments are in chinese and not only on clock_skin.xml.
i didn't checked with english comments because the face which is not working has chinese comments and i did not check the working ones if the had english comments or not.
Thanks again for your GREAT job.
I’ve checked again and 2.0.1 is filtering comments, can you send me the link to your skin ? Thanks
Hi,
I do not remember the link so i put it om my drive
Mar 18, 2017 1:24:45 GMT 1lem5gg said: not working on my lemfo lem5... the launcher is not showing fullscreen and round (it's not centered but in the bottom right corner), but square and glitchy, even if the screen setting is fullscreen
Sometimes is also to my lem5 the launcher misplaced, especially if square screen is enable.
Most of the times, if a wait for 5-10 sec, the issue solved. If not I disable square screen or restart my device.
This skin is badly formed. The XML file is wrong and my parser is not tolerant to this, so it crashes. First thing would be to correct the XML files, the tag is shown twice !
<?xml version="1.0" encoding="utf-8"?>
Mar 18, 2017 1:15:02 GMT 1buddyrm said: Eric, check this clockskin out. It really freaks out your launcher. Keeps crashing it over and over when trying to load it. Had a hard time to get it back running. It was even impossible to select another watch face skin. Try it at the link below. It is called ORANGE GLOW
This skin is also badly formed : the day_array refer to non existing files...
I've added a check so that it won't crash but the skin should be corrected.
Will publish an update soon. In general i observe that the new engine is not tolerant to badly formed XML and other non supported parameters.
The previous engine was tolerant to that, that explains that it was previously working.
2.0.3 uploaded with the same link : added some robustness with bad clockskin skins. => bad formed XML and non existing files.
Also added the ucolor tolerance with watch files, but the ucolor feature is not yet supported.
Mar 18, 2017 9:05:29 GMT 1kapuzo said: Hi Eric , this is only an observation , I notice that during the swapping of clockskin from time to time sometimes cause some erratic clock positioning, so i need to go to default skin and delete the watchtmp and restart the wathch to work it again. doest the engine needs lots of space for temp swapping?
No, nothing needed when looking in the skin gallery, only needed to unzip the chosen one.
Mar 17, 2017 10:21:41 GMT 1prostosergik said: I can confirm. After restart, I see empty slots with + mark, but widgets are disappeared. But while they were here, they were live and showed actual info. =)
After reboot, the watch ask for an autorisation for my App to create the widgets, if you say no then it probably does that.
Nope, I always say YES to this. And it worked untill next reboot. I.e. 1) add widget, 2) reboot 3) answer YES in authorization dialog, 4) reboot 5) no widget.
UPD: installed 2.0.3 - widgets appeared and works well. Will keep eye on that.
By the way, before update, step counter at clock skin stop working for me. Showed 0 always. Do I need to reset some app cache maybe?
By the way 2: When Im trying to update weather location in settings window, app get crashed unless I enter Paris,FR (default value). Im trying “Budva”, “Budva,MNE”, “Podgorica”… so on, and getting app crashed.
First of all, great job what you’ve done! I have a little problem with the newest launcher. Not a big problem, but maybe you could do something with it. Every time when I push the wake up button the watch shows the last time right before the screen lock for a second and after the hour hands jumps to the right position (doesn’t matter which face is in use). The issue only with the 2.x launchers, before with 1.1.x wasn’t. I’ve a zeblaze blitz if it’s help something.
Hi Eric, thank you for your fantastic job. As I already mentioned this, I will ask it once more to improve battery a little bit more. Can you change the screen timeout with hand gesture to switch off screen after 3 seconds? Tried a lot of apps changing timeout but the smaller I manage was 10 seconds.