You will lose these.
There is no way of upgrading the system image without having to re-install TWRP and Magisk boot and Exposed.
It would be the same if you upgrade any firmware. You also cannot take an OTA unless you go back to stock first.
These are basic rules for rooting devices.
2 Likes
it should present no significant problems sir 
1 Like
Yep.
It’s pretty straight forward to reinstall these things. I do it almost every day 
2 Likes
Ok thank you. It’s been a while since I had to root my last phone… So I think there’s some rust in my memory that needs to be cleaned! Cheers
1 Like
sad to report overheating and battery drain at 10% an hour when idle with 3.0
rolling back to 2.6.
thank you and have a good day
2 Likes
Hmm - I don’t have this experience at all.
Which is a worry…
So the switching between normal and performance mode made no difference at all ?
I’m surprised that you didn’t give it a chance to go through at least one power cycle as part of your testing.
So let’s be clearer - if you want to test this firmware properly - you will need to use it for a couple of days and at least through one discharge and recharge cycle to get any results at all.
You will also need to use the Firmware Upgrade option in SP Tools or perform a factory reset after flashing. I do both - just to be sure.
This is extremely important !!
There is not much point in the company giving us firmware to test if we only use it for a couple of hours.
However - thanks to any of you who do 
!!
Please remember - this is a voluntary testing option.
If you are happy with your watch right now then don’t worry about testing this.
It is absolutely your choice to try it or not.
Cheers
4 Likes
didn’t test the performance mode as I’m mainly interested in preserving the charge, and not interested at all in increasing performance.
I did a factory reset after the flash and I charged the watch up just to get an idea on how battery life is before I start flashing TWRP , Magisk, xposed and such.
unfortunately it showed to be less than ideal ; I noticed that the watch is kind of warm just laying on my desk doing nothing and the battery was draining fast, so I assumed the watch would behave just like it did running 2.7.
as I was more than happy with 2.6 (especially paired with amplify and gms doze) I rolled back to it immediately, the heat/drain problems just disappeared and performance went back to excellent.
I might give another shot to 3.0 though
cheers
2 Likes
Thanks very much.
This explains your situation.
I appreciate your reply.
Cheers.
1 Like
When the watch is turned on, the watch consumes about 1-2% of the energy per hour (Watch Droid). I use an alarm clock (for vibration only). If the alarm starts to vibrate and I end it, the power consumption has risen to 10% per hour since then. Only a restart will help. It does this in all firmware listed here
that is a specific detail to notice, but glad we are now all informed.
That’s interesting.
I use the alarm as well but I haven’t noticed this behavior.
Thanks for the heads up and I will test it.
Cheers.
I guess you suffer from ledswakelock bug.
Good morning @pablo11, Yesterday I decided to give v3.0 beta a try.
Unfortunately the performance option doesn’t help with the overheating issue: almost anytime I download content (music, web surfing, etc…) for more than (let’s say) a couple of minutes (not a couple of hours), I got the overheating issue as on the previous versions (tested personally v1.6, v2.5, v2.7).
As said above, the issue seem related to data exchange from the internet and is becoming very frustrating.
Hope this feeback helps to have a better product in the future. However count me in if you need a beta tester!
Cheers, and thank you for your job!
Thanks very much for your feedback.
Have you tested v2.6?
If everyone agrees that 2.6 is best for the heat problem - I will see if we can merge v3 with v2.6.
The bottom line is that v3.0 is v2.7 with menu changes.
So it seems like v2.6 is probably the best option, right?
1 Like
Good morning @pablo11, as I said I have not tested 2.6 personally, so I can’t say whether it’s good or not. I’ve read good things about it though.
Maybe merging 3 with 2.6 is a good option.
Let me know and I will help testing.
Now I’m tweaking v3 with some build.prop hacks and cpu control to underclock. I will keep you informed if is useful for you.
Cheers
1 Like
Ok cool.
I have thoroughly tested cpu underclock and it is a waste of time unfortunately.
I strongly recommend that you test 2.6 because I need as many positive reports as possible.
Tweaking the .prop files can come after.
Right now we need a stable base to work with. 
1 Like
Ok thanks for the advice. I will test v2.6 as soon as possible. Nevertheless, having good results with SetCPU ( free XDA version) and underclocking to 845MHz of maximum frequency.
Cheers
Thanks mate.
I appreciate that it may seem to have good results with SetCPU but after a lot of testing I can tell you that my experience shows that it is either not really settling the frequency as it seems to - or it just makes no difference to battery life.
I say this because after some sustained testing - battery life remains the same.
However, I would be very happy if you could prove me wrong
I will tell. Hope I will not get the overheating issue further on
Maybe take a look at this. Heating is constant 100% cpu usage. You need to find out which process is doing that and then why it is doing that. Of course a task for the manufacturer!
But you can try to put your finger on it too.
You need adb access to the watch. Then use the linux ‘top’ command and let it run for a while. top will show the processes that use the most cpu.
Limit the nr of processes it shows with: top -m 5
At least now you know which process it causing the heat.