Universal Launcher New Generation [2.x]

stefano · April 21, 2017, 10:56pm

Mar 25, 2017 2:21:25 GMT 1 stefano said:
Great! change skin is now easier.
The above face has background/font display errors. I dont use it but for debug purpose can help.

assets.facerepo.com/app/download/link/rotated-20l-for-left-wrist-15a7cc765a7.watch

After 2.2 this face (and many others) has visualization problems due to some index or zoom factor problem.

P.S. leaf change of the watch looks very nice

gf1973 · April 21, 2017, 11:16pm

Apr 20, 2017 13:41:27 GMT 1 gf1973 said:
Apr 18, 2017 6:33:08 GMT 1 ricktop said:
I know this happens sometime, but I've not found the Root cause yet.

Hello ricktop, I don't know if it helps, but I have done a couple of tests and I have noticed that up to version 2.0.10 the skin-changing behaves OK on my Domino DM368 watch (all skins look ok). When I install version 2.1 or higher however then - when I change to another skin - the new chosen skin is graphically incomplete, missing graphics, fonts, .... And this is always the case (so not that sometimes the other skins are ok). I included in attachment 2 skins, called BigDigital.zip and LEDS.zip. Both are made with the ClockSkinMaker and I copied these ZIP files (as they are) to the 'ClockSkin' folder on my watch. For the rest, I only have your default skin on my watch (the one where background is pulsating). After I install version 2.1 (or higher) on my Domino DM368, I change from your skin to the BigDigital skin. This skin looks OK. But when I then change to the LEDS skin, then this skin is grahically incomplete/disformed (it has the second hand PNG and background PNG from the BigDigital skin, but the rest from the LEDS skin). And this is always the case.
I hope this helps you in duplicating this issue on your watch(es) …

Hello ricktop, I am not sure if you already had the chance to read my post ... Was my input helpfull ?

samsungxp1 · April 22, 2017, 3:02am

so 2.1.3 is better ?

Eric_Crochemore · April 22, 2017, 7:15am

Apr 21, 2017 23:16:24 GMT 1 gf1973 said:
Apr 20, 2017 13:41:27 GMT 1 gf1973 said:
Hello ricktop, I don't know if it helps, but I have done a couple of tests and I have noticed that up to version 2.0.10 the skin-changing behaves OK on my Domino DM368 watch (all skins look ok). When I install version 2.1 or higher however then - when I change to another skin - the new chosen skin is graphically incomplete, missing graphics, fonts, .... And this is always the case (so not that sometimes the other skins are ok). I included in attachment 2 skins, called BigDigital.zip and LEDS.zip. Both are made with the ClockSkinMaker and I copied these ZIP files (as they are) to the 'ClockSkin' folder on my watch. For the rest, I only have your default skin on my watch (the one where background is pulsating). After I install version 2.1 (or higher) on my Domino DM368, I change from your skin to the BigDigital skin. This skin looks OK. But when I then change to the LEDS skin, then this skin is grahically incomplete/disformed (it has the second hand PNG and background PNG from the BigDigital skin, but the rest from the LEDS skin). And this is always the case.
I hope this helps you in duplicating this issue on your watch(es) …

Hello ricktop, I am not sure if you already had the chance to read my post ... Was my input helpfull ?

Sadly I’ve not reproduced it using your skins, so maybe something comes from your FW also. But that’s the kind of message that could help so keep on ! Thanks

chrislynch · April 22, 2017, 12:41pm

Hello, I could use your kind help.
Can you please make clear to me whats the difference between the standalone app and the launcher?
And how I can use the watchmaker app to upload faces on my D5?
Thanks in regard

easydot · April 22, 2017, 12:48pm

Apr 22, 2017 12:41:44 GMT 1 chrislynch said:
Hello, I could use your kind help. Can you please make clear to me whats the difference between the standalone app and the launcher? And how I can use the watchmaker app to upload faces on my D5? Thanks in regard

The standalone App is what the name says, you can run it like any other App on your watch. The launcher is a replacement an everytime you go back or end up a app you came to the launcher. It is like on the phone if you press the home button your launcher will showup. The standalone app will close if you press the physical button or make the switchapp gesture.

Watchfaces can’t loaded with the Watchmaker App, you must upload them manuelly to a folder named “ClockSkin” on your watch.

Hope that could help a ittle bit

Eric_Crochemore · April 22, 2017, 2:16pm

Apr 22, 2017 12:41:44 GMT 1 chrislynch said:
Hello, I could use your kind help. Can you please make clear to me whats the difference between the standalone app and the launcher? And how I can use the watchmaker app to upload faces on my D5? Thanks in regard

Standalone is not a launcher, only a skin engine
Watchmaker is not needed, you put your skins in the ClockSkin directory directly.

jimcarter · April 22, 2017, 4:00pm

Apr 22, 2017 14:16:05 GMT 1 ricktop said:
Apr 22, 2017 12:41:44 GMT 1 chrislynch said:
Hello, I could use your kind help. Can you please make clear to me whats the difference between the standalone app and the launcher? And how I can use the watchmaker app to upload faces on my D5? Thanks in regard

Standalone is not a launcher, only a skin engine Watchmaker is not needed, you put your skins in the ClockSkin directory directly.

Apologies, but I novice in the Smartwatch arena. I installed the launcher, do i need the Watchmaker as well?

gf1973 · April 22, 2017, 9:39pm

Apr 21, 2017 15:52:31 GMT 1 ricktop said:
2.1.3 version uploaded : - correction weather update always showing - added 25 and 75% for brightness - the cocos library is in debug mode, don't know if it will change something for you...

Hello ricktop, I installed version 2.1.3, but now the weather tag/array is not updating anymore and when I get a notification, the watchface lights up, but it doesn't show the actual notification (which both work in version 2.1.2) . I use skins made with the ClockSkinMaker, copied to my watch as ZIP files. I have a Domino DM368 with android 5.1, kernel version 3.10.72 and build number DMNSB_GSM_V1.2.0_20170223 (latest version).

samsungxp1 · April 22, 2017, 11:00pm

Apr 22, 2017 21:39:19 GMT 1 gf1973 said:
Apr 21, 2017 15:52:31 GMT 1 ricktop said:
2.1.3 version uploaded : - correction weather update always showing - added 25 and 75% for brightness - the cocos library is in debug mode, don't know if it will change something for you...

Hello ricktop, I installed version 2.1.3, but now the weather tag/array is not updating anymore and when I get a notification, the watchface lights up, but it doesn't show the actual notification (which both work in version 2.1.2) . I use skins made with the ClockSkinMaker, copied to my watch as ZIP files. I have a Domino DM368 with android 5.1, kernel version 3.10.72 and build number DMNSB_GSM_V1.2.0_20170223 (latest version).

the recent task menu still there ? when i press power button only got 3 menu - power off,reboot and power save.recent task menu missing.ord have coz juz now battery saVer on

nameless · April 23, 2017, 12:17am

Apr 21, 2017 14:50:14 GMT 1 nameless said:

I now have same situation as yawa had. Can’t change clockskin, can’t switch between dim/bright. I noticed that battery, weather and step counter are stuck at the value on restart.

Reset and reinstall doesn’t help.

ricktop:

As yawa mentioned couple of times my watch did magicaly heal itself after sometime. I can change faces, switch dim/bright, notifications show up etc I noticed that it “healed” after I was asked to chose which launcher to use (that requester when you chose “just once” or “always”). After some thinking I realized something: after installing launcher (update or clean) there is window with two options: one is “ok” the other is “open” (I’m not sure how they are in english cause my watch now is in polish again). Most of the time I was clicking on “open” and this lead to erratic behavior. After installing 2.1.2 I clicked “OK” and after pressing button I was presented with requester “just once”/“always”. Clicked WatchClockSkin and “Always” and I had perfectly working launcher (until I screwed it with unspported watch). I’m certain that after updating to 2.1.3 I clicked “Open” and I had problems with everything. After sometime probably launcher got killed by OS and Android asked me to chose which launcher to use. From this point on everything is working ok. (I do hope you can make head or tails from this… )

So I’m thinking that maybe (just maybe) problems are originating from chosing “Open” just after installing/updating launcher. Proper way should be to click “OK” and then click button and chose WatchClockSkin and “Always” and all will be ok.

At some point after changing Location 1 in launcher settings I was unable to get back to watch face. I could swipe left and right to quick settings and watch status w/o problems but swiping up just did nothing. After using button to off/on watch I was presented with watch face.

Anyway now everything is working perfect

Now question regarding supported tags:

{wsr} and {wss} are supported but values reported are wrong for my location. They are updated with weather? Once a day?

N.

scytalemk · April 23, 2017, 9:22am

Apr 23, 2017 0:17:13 GMT 1 nameless said:
Apr 21, 2017 14:50:14 GMT 1 nameless said:

I now have same situation as yawa

had. Can’t change clockskin, can’t switch between dim/bright. I noticed that battery, weather and step counter are stuck at the value on restart.

Reset and reinstall doesn’t help.

ricktop :

As yawa mentioned couple of times my watch did magicaly heal itself after sometime. I can change faces, switch dim/bright, notifications show up etc I noticed that it “healed” after I was asked to chose which launcher to use (that requester when you chose “just once” or “always”). After some thinking I realized something: after installing launcher (update or clean) there is window with two options: one is “ok” the other is “open” (I’m not sure how they are in english cause my watch now is in polish again). Most of the time I was clicking on “open” and this lead to erratic behavior. After installing 2.1.2 I clicked “OK” and after pressing button I was presented with requester “just once”/“always”. Clicked WatchClockSkin and “Always” and I had perfectly working launcher (until I screwed it with unspported watch). I’m certain that after updating to 2.1.3 I clicked “Open” and I had problems with everything. After sometime probably launcher got killed by OS and Android asked me to chose which launcher to use. From this point on everything is working ok. (I do hope you can make head or tails from this… )

So I’m thinking that maybe (just maybe) problems are originating from chosing “Open” just after installing/updating launcher. Proper way should be to click “OK” and then click button and chose WatchClockSkin and “Always” and all will be ok.

At some point after changing Location 1 in launcher settings I was unable to get back to watch face. I could swipe left and right to quick settings and watch status w/o problems but swiping up just did nothing. After using button to off/on watch I was presented with watch face.

Anyway now everything is working perfect

Now question regarding supported tags:

{wsr} and {wss} are supported but values reported are wrong for my location. They are updated with weather? Once a day?

N.

Exact same problems on my watch too. The launcher just stoped, and when system ask me which launcher I want to use, my watch skin was showing -14 steps, and have problem with weather update. Also I have problems with battery drain on 2.1.2. After night it went from 90% to 11%, and after 10 seconds of using the phone it went off. I put it on the charger it shows that there is 11% left of battery. So I suppose launcher has right battery reading. I have mostly similar problems with 2.1.0 and 2.1.1 I didn’t try 2.1.3 yet, but I suppose I will have same problems. So far the most stable version for my KW88 is 2.0.10, so I using it right now.

peppe11 · April 23, 2017, 10:07am

Hello Ric, thanks you for your hard work. Y3 smartwatch has inverted gyro, so can you change the sign of horizontal gyro, to fix that? Or, i don’t know… source code? Can we have that to improve your work?

yawa · April 23, 2017, 11:47am

Apr 22, 2017 21:39:19 GMT 1 gf1973 said:
Apr 21, 2017 15:52:31 GMT 1 ricktop said:
2.1.3 version uploaded : - correction weather update always showing - added 25 and 75% for brightness - the cocos library is in debug mode, don't know if it will change something for you...

Hello ricktop, I installed version 2.1.3, but now the weather tag/array is not updating anymore and when I get a notification, the watchface lights up, but it doesn't show the actual notification (which both work in version 2.1.2) . I use skins made with the ClockSkinMaker, copied to my watch as ZIP files. I have a Domino DM368 with android 5.1, kernel version 3.10.72 and build number DMNSB_GSM_V1.2.0_20170223 (latest version).

As for me, 2.1.3. and 2.1.2 are pretty equal regarding this issue. Try simply to wait a little bit, after a while you should be able to see the last notification and so on ... see the next post from nameless. And BTW: your version is not the last one, AFAIK, but it doesn't matter. I've downloaded my "last" version here: mega.nz/#F!clIRkSpZ!X_kDwHqXDnGy11WSK1wI2w!8ppVSZRb (you should probably take the GSM, not the HEHUI version).

tomek · April 23, 2017, 12:18pm

I’ve made battery drain experiment
KW88
test was a 10 mins permanent screen on sessions, smartwatch was laying untouched on the table
here are the results :
70-64 (6%) factory launcher, wrist gesture off
62-48 (12%) launcher, wrist gesture on
48-37 (11%) launcher, wrist gesture off
35-30 (5%) factory launcher, wrist gesture off
29-24 (5%) factory launcher, wrist gesture on

leo2018 · April 23, 2017, 1:04pm

i have a strange thing about battery drain can you explain?

telephone inactif : 32%
veille gsm : 4%
ecran 4%

zsoltm · April 23, 2017, 2:25pm

Apr 21, 2017 22:03:14 GMT 1 ricktop said:
Apr 21, 2017 20:53:50 GMT 1 zsolt m said:
Hi Eric! my question : in lemfo Y3 too match battery eat the "bright screen on" function, cos company has bad giro calibration. Possible to made, one xyz axis setting in launcher for gyro? When not what your opinion to reduce the false wake up screens? thanks

For the moment i have disabled the gyro, i'm not sure how to remove false wake up, i had the same wake up with the original gyro...

Hi Eric, How do you disabled the gyro on your watch?

Second, was one issue for me, I’v build my new skin, and continue to test that.
But when made new version of same skin, than upload that to my Y3 clockskin folder, (before I’v change the skin in the watch to another)
I’m overwirte the original file, the back to skin, still display the old version.
Only way just delete the old skin, with folder, save as to another name, then upload as new, to the watch.
I’v try to delete watchtemp folder too, but same issue.
Where is the temp file, or the temp store for pictures?
Thanks

Eric_Crochemore · April 23, 2017, 4:39pm

Apr 23, 2017 14:25:04 GMT 1 zsolt m said:
Apr 21, 2017 22:03:14 GMT 1 ricktop said:
For the moment i have disabled the gyro, i'm not sure how to remove false wake up, i had the same wake up with the original gyro...

Hi Eric, How do you disabled the gyro on your watch?
Second, was one issue for me, I’v build my new skin, and continue to test that.
But when made new version of same skin, than upload that to my Y3 clockskin folder, (before I’v change the skin in the watch to another)
I’m overwirte the original file, the back to skin, still display the old version.
Only way just delete the old skin, with folder, save as to another name, then upload as new, to the watch.
I’v try to delete watchtemp folder too, but same issue.
Where is the temp file, or the temp store for pictures?
Thanks

I’ve disabled the gyro in the wake up code only.
you just need to overwrite the skin folder then reload your skin (change skin to the same one)

gf1973 · April 23, 2017, 7:57pm

Apr 22, 2017 7:15:05 GMT 1 ricktop said:
Apr 21, 2017 23:16:24 GMT 1 gf1973 said:
Hello ricktop, I am not sure if you already had the chance to read my post ... Was my input helpfull ?

Sadly I've not reproduced it using your skins, so maybe something comes from your FW also. But that's the kind of message that could help so keep on ! Thanks

Hello ricktop, I have found the reason why my skins were not showing graphically correct when switching from one skin to another. Instead of copying the skins as ZIP files in the Clockskin directory, I have copied them as seperate files (not zipped). Now when I switch to other skins, all skins are shown graphically correct again. It is still strange however that up till version 2.0.10 the launcher did not have any problems with the Zip files ... I hope this helps in investigating this bug ... I am using version 2.1.2 of the launcher currently.

Eric_Crochemore · April 23, 2017, 8:06pm

Apr 23, 2017 0:17:13 GMT 1 nameless said:
Apr 21, 2017 14:50:14 GMT 1 nameless said:

I now have same situation as yawa

had. Can’t change clockskin, can’t switch between dim/bright. I noticed that battery, weather and step counter are stuck at the value on restart.

Reset and reinstall doesn’t help.

Now question regarding supported tags:

{wsr} and {wss} are supported but values reported are wrong for my location. They are updated with weather? Once a day?

wsr and wss are not supported, only weather and temp, not wind… not yet…