Apr 11, 2017 10:56:56 GMT 1yawa said: Very strange. I was sure, that all my three skins were ok under 1.x and 2.0.x. Well, the only thing I can do is to take another 3-4 skins and play with them. Will do that and report.
UPD. Nope, I deleted these three skins and uploaded three new skins. Restart. I could change the skin only one or two times, after that I've got the same problem - I change the skin, but no reaction, it remains the same. Well, I didn't reinstall the launcher, but I suppose, it's not the point. To be sure: here the three new skins I've tested.
i just downloaded the tagheuer-formula1.rar (495.31 KB). uncompressed it and transfered it over to the watch. black/blank. looked at the file and there .img* hidden? removed the . from infront of the filenames and edited the xml to correspond with the new name. transfered the new files over and its showing up now. poked it a few times, restarted the watch seems to be working fine.
Thx for your test, cinitek32, but it doesn't seem to be the cause of the problem. I've just tested the same - I have renamed all .img*.* in img*.* and adjusted the respective names in the xml. the same result: I can change the skin once or twice, that's it. And furthermore there were no .img*.* filenames in my previouos "collection" (breitling/tissot).
From the looks of it itās not the skin itself but rather some āoverloadā of cocos library.
Iāve got .trace file from todays morning and another one like an hour ago. They are identical and both point to:
java.lang.IllegalArgumentException: Receiver not registered: com.ricktop.ClockSkinCoco.QuickSettingsSystemConfigFragment$2@229ef682
I just guess that above refers to fragment that displays flight mode, bluetooth, wifi etc switches (same thing was in one of yours .trace yawa ) but it all looks like launcher got signal/forced to exit and fails to do so cleanly (this is just pure assumption based on logic only)
More or less about the time I got that last one .trace file my KW88 asked me what I want to use as default launcher. Iām not sure but few minutes before I might turn on data transfer (or wifi)
Iāve not been here these days and iāve been injuredā¦ but i have reproduced the situation. Seems to be happening on the released version and not on my test version. That would mean that the released cocos library is not the same as the debug libraryā¦ I will try to confirm and give a new version soon. Thanks for your patience.
ricktop great news and I think we all do understand and respect that you do that excellent work in your spare time
Seems like bad karma finally got me too Iām tryingt o recover my watch from weird bootloopā¦ Oh wellā¦ Fingers crossed
Debug version might contain f.ex. some assertions that like keep things in order and thatās why your test version works ok. Iāve seen that way often that Iād ever wanted
Good luck and thx for all your work
N.
Hi guys, just bought a LEM5 and I am a nooby. The question iāve got is will this launcher be fine with my watch as the screen size is the same as K88 so i donāt think there will be an issue but still wanted to be sure before i downloaded it.
Using a clean install of 2.1 on my I3, Iāve experienced a few oddities:
The watchface seems to lock up and during that time the battery drains quickly. I turn off the display and turn it back on and then the watchface seems to come back to life. Iāve restarted my watch now to see if this continues.
I put on a new watchface www.watchawear.com/watches/watch-faces/download/2-watch-faces/8814-radar.html and it seems to work well, except only the foreground color changes, ie. the radar sweep and inner indicators. The numbers on the dial and the outer ring remain greeen. Not sure if this is an issue with the watchface itself or due to the way that the clockskin works with it. Can anybody else see if it exhibits the same behavior? Unfortunately I never tried it with previous versions so Iām unsure if it ever worked properly.
Apr 12, 2017 16:05:02 GMT 1f00bar12 said: 2. I put on a new watchface www.watchawear.com/watches/watch-faces/download/2-watch-faces/8814-radar.html and it seems to work well, except only the foreground color changes, ie. the radar sweep and inner indicators. The numbers on the dial and the outer ring remain greeen. Not sure if this is an issue with the watchface itself or due to the way that the clockskin works with it. Can anybody else see if it exhibits the same behavior? Unfortunately I never tried it with previous versions so I'm unsure if it ever worked properly.
Same here.
After looking at watch.xml file I think that this might be proper behavior (parts that are responsible for changing color have display=ānā attribute which, according to watchmaker wiki, shoud not display this element). I might be wrong of course (those xml files arenāt all that readable and I donāt know that much about all the attributes).
Even without those colorchanges itās pretty neat watchface tho
nameless, it is same for me. Wrist gesture works normal even when launcher is not activated as administrator. Also when itās not administrator I can manipulate launcher easier, and if you remember about my problems with changing skins after restart, now i need to force stop launcher, and activate it again and after that changing skins works normal, and I think that widgets are back to their place.
So let me explain step by step, maybe we will find sollution for my problems and bugs this way. Note: I use 2.0.10 version.
I clean install launcher, and .watch and clockskins works without problem. There are no problems with changing skins. I put widgets also.
The watch goes off after battery discharge (or I deliberately reboot watch), and when itās up again I canāt change skins, and widgets are not on their place.
I go to Settings -> Uninstall Application and then Force Stop WatchClockSkin. Then I press power button, watch ask me which launcher I want to use, I chose WatchClockSkin, and after that everything is ok. I can change skins, and widgets are on their place again.
P.s. I have one more problem. When battery goes to 20% watch turns off. Like itās not good calibrated.
Apr 12, 2017 21:21:19 GMT 1scytalemk said: So let me explain step by step, maybe we will find sollution for my problems and bugs this way. Note: I use 2.0.10 version.
1. I clean install launcher, and .watch and clockskins works without problem. There are no problems with changing skins. I put widgets also.
2. The watch goes off after battery discharge (or I deliberately reboot watch), and when it's up again I can't change skins, and widgets are not on their place.
3. I go to Settings -> Uninstall Application and then Force Stop WatchClockSkin. Then I press power button, watch ask me which launcher I want to use, I chose WatchClockSkin, and after that everything is ok. I can change skins, and widgets are on their place again.
P.s. I have one more problem. When battery goes to 20% watch turns off. Like itās not good calibrated.
The same for me including the battery issue ā it seems that the battery status is not updating correctly, both in 2.0.10 and 2.1
Regarding 1-3: Itās the same behavior I have already described. But Iām not sure that the restart / reinstall is āhealingā the app. It seems that the launcher is either losing its permissions while running or itās running into another ātroubleā with register/unregister of some events or smth like that - see posts above. But there is a hope now, because Eric has found out smth regadring the frameworl version, as I undeerstood. So letās wait for him, I guess he will bring a new version soon
Iād suggest you to install 2.1 version. Probably wonāt solve all bugs but maybe some of them Donāt know if you seen it but Eric was able to recreate some (if not all) of those problems and narrow them down to non-debug version of cocos library (apparently debug version is doing just fine. He is still investigating it.
Also itās probably easier for Eric when bugreports regard current version (he doesnāt need to backtrack in source code version too much).
About battery I think it tries to enter power saving mode which is not supported by Ericās launcher. It displays bright white screen instead and that can drain battery pretty fast
and I think we all do understand and respect that you do that excellent work in your spare time 
Iām tryingt o recover my watch from weird bootloopā¦ Oh wellā¦ Fingers crossed