I have 3.4 but it does the same thing on my Prime 2
1 Like
I havenât tried android 10 yet, but if it works the same way like on the 7.1 watches you should press only âalltidâ and not the name of the launcher when it shows for the second time
But I also show the picture from settings, where is is also set as start app, so it should never ask at all !? I will try only to press always next time.
Iâm not sure ul can run on Android 10, you may wait until I can test it on an Android 10 watch. I can try to publish a beta version, but not testedâŚ
3 Likes
Well, it runs quite good 
Only it seems more difficult to find correct settings, to keep it from being killed now and then.
One detail that puzzles me: on Android 7 we needed to protect 2 apps, watch Clockskin and a settings app, but I canât find the settings app in the list of apps to spare from battery optimizationâŚ
I may have solved the kill issue: I found the old style background cleaner and in there were both the watch Clockskin and the settings app.
1 Like
The âOptimizationâ app. I have that disabled entirely but it doesnât help me.
It actually seems to have helped me.
Edit: mostly⌠I do still see the âselect launcherâ dialogue 5-10 times pr day, but the frequency has drastically decreased since removal from the background cleaner.
Here is a beta version without being tested on Android 10 watch :
5 Likes
Thanks! This fixes at least one thing - one widget that wouldnât initialize properly now does. Crashes may be reduced but arenât eliminated. I tried uninstalling/reinstalling, changing every setting I can think of one at a time, but I havenât been able to discern a pattern to the crashes yet.
Thanks 
I have installed the beta and will provide feedback.
Edit:
- Very seldom the blue status / buttons are drawn a bit later than switching to the page.
- The color of the notification backgrounds sometimes makes it impossible to read the text from the notification. There are some nice backgrounds, so also very nice. Is it possible to replace the backgrounds ?
- The notifications seems to use only the 450 or 400 pixels or something, i.e. they sit a bit to the left and donât use the right side of the display.
1 Like
Do you have a change log for this? Just curious.
Iâve worked on some deprecated methods for gsm setting. Also some clockskin and watchmaker bugs. Small rework on app launcher, but this should not be visible.
2 Likes
@Eric_Crochemore Did you notice my feedback and questions above ?
Thank you.
So, I am using your beta version ClockSkinCoco-3.4.1.apk on a Kospet Prime SE running Android version 7.1.1 Build number KOSPET_PRIME_SE_v1.6B_20200922.
The SIM bar graph is not working correctly now. When first booted, it displays all the bars. After some use, it displays no bars and when pressing on the bar graph shows SIM:true Service:0 Network:13 dBm:-120 asu:0. However, when viewing SIM Status in the Settings menu, Signal Strength displays as -110 dBm 29 ASU Service state: In service Cellular network state: Connected.
You corrected this issue previously with the latest release on Playstore. Thank you Eric. I LOVE UNIVERSAL LAUNCHER!
One other question⌠Why did you name the APK with âcocoâ on the end LOL!
LOL I had to Google âdeprecatedâ.
1 Like
Its very simple . For many a year Eric has only eaten one type of cereal for breakfast . He loves the stuff
3 Likes
Yes I did. Iâm not sure that this specific to the beta version. I will see what I can do. Thanks
3 Likes
Thanks for the feedback. I will check this part again.
About coco, it comes from the framework used : cocos2dx.
3 Likes
beta 3.4.1 updated (same link). New arraytype 61, 63, 65, 66 and 101 should work with this version.
Also maybe GSM signal level ?
2 Likes