thanks you all for your help 
You are welcome.
2 Likes
Ok, I just read through all 362 posts in this thread so I think Iâve got the answer to my question above. Still a couple other thoughts:
Somewhere in my memory banks I seem to recall a problem using anything after Magisk 18.1 on Kospet? False memory or is there something to that?
Is it possible to downgrade updates to v1.5 or v1.6 if you find changes you donât like?
Yep but magisk is working fine on all the updates as far as I know?
1 Like
Flashing worked fine. Just a note for some here on flashing I always set the watch on the charging dock (after it is off and USB cable not yet connected to PC) the click âdownloadâ or start in the flashtool, then attach the USB cable to my PC and it starts the flash right away. Learned that from other MTK devices as the most sure way to get a flash started.
Thanks! Just getting ready to fire up SP flash tool. Iâm planning to first try âdownloadâ of just the TWRP image and Magisk patched boot image to my 1.5b current build.
That all went well. Rooted with Magisk and with TWRP installed. I installed J.Rummyâs ROM Toolbox which has a ârebootâ function that will let you reboot into recovery - TWRP in this case. Itâs also great for freezing apps and a lot of other uses. Without ROM Toolbox I donât think there is a way to reboot to TWRP unless you have a PC (or there may be a couple other root Apps that will allow that also).
Can anyone say if the v2.1b update takes care of the rotation problem with clockfaces? Iâm not sure I actually understand clearly what that problem involves if anyone can elaborate. Until I got the Prime the only Android watches I had previously were square face.
You can just use magisk manager to reboot to recovery.
Can also use the Magisk busybox module.
Basically no need to install anything else unless you want to actually write to the system partition.
I prefer to use system less modules myself.
Glad you had no problems
2 Likes
Hi pablo11, I thought I saw a checkbox about recovery mode when I was installing Magisk but I didnât check it or any of the other 2 boxes I saw. Other than that I donât see any options in Magisk manager to reboot to recovery now. Is that a module add on to reboot into recovery or did I miss something? Thanks again for all your help and posts in the Prime thread!
Thanks again! Thatâs the one thing I didnât touch 
Looking back through some older versions Iâve got on phones I see that option has been there quite a while and I donât recall if I ever knew about it. Might be an age related thing ⌠
1 Like
I did a simple test of the battery level display error.
https://drive.google.com/open?id=1WtdGYJgmox63mpmb6MydRcdTLD4LYA5F
WFD does not fix this error.
You can see the error in the pictures.
GOOD DISPLAY (all stock launchers. These are made from OPTIMUS PRO 4.0.) This is how PRIME 2.0 worked.
BAD DISPLAY (Someone wanted to do good. Centered display alignment. Canât be used for graphic display with variable position.)
These are the UL display positions We are already used to this
(If possible, it would be good to standardize the positions)
1 Like
Has anyone tested the new 2.1 update yet? Comments, improvements, or issues?
Hello, no OTA 2.1 for my after flash to 2.0b. but 2.0b is pretty good no heating when i use BT and no freeze for app circle/square
1 Like
Please just wait a little longer for the OTA with the Google apps fix.
Cheers
2 Likes
Did the 2.1 OTA and my battery is draining very fast and 10-12 hours then the battery is emty. Heartrate and pedometer dosenât work.
Please perform a factory reset. This will solve your problems.
1 Like
Did factory reset but still dosenât work. I also did 2.0 OTA mabey i must do reinstallation from computer?
Maybe heartrate and stepcounter is disabled in the settings?
If not, I would flash it manualy.
1 Like
Check BT and location as well.
In the newer firmware these are on after update by default.
It is to help people pair with their phone etc.
Just turn them off.