I just saw this. I am using your 900 mhz prebuilt, it really makes my allcall awatch gt run cooler. I love it. I am going to try this as well. Let’s see at what percentage it will cut charging.
I tried it in Allcall Awatch GT. It stopped charging at 90 %. Thank you very much!
Good question. Like 700 mhz.
“The file you are trying to download is no longer available.”
ah yes, in case anyone have problems after flashing older version kernel for testing, like nvram error like @tweakradje or in my case my watch can’t enter deep sleep after receiving SMS (weird indeed, but after flashing only both system and boot the problem persist. and that’s after using 3 different firmware) or any unwanted bugs, perhaps it’s better to flashing full fimware then flash new kernel release.
But this better done if you encounter problems, if not stick to what you are doing lol 
sorry to bother but I have a problem with the installation. Apparently everything was completed according to the instructions, but to no avail. Can you tell me how to upload it correctly?
@Patryk_Roszkowski
Check here for a quick tutorial.
@Giorgos_Tsarouchas
Yes, but i think the current 900MHz are already the sweetspot between performance, efficiency and power saving.
Reducing the frequency further will decrease performance without much gain in either energy saving or heat output.
Edit:
Updated all kernel images on the original post and added a short instruction for the flashing process.
4 Likes
I am using underclocked to 910 MHZ + charging up to 90 % Kospet Prime boot.img + Scatter file for a while. I enjoy using it. Recently I found that my front camera is showing reddish or blueish depending on the light. I switched back to regular boot.img + Scatter file, it was back to normal again. Is there a setting for this in Android?
Thank you for the quick reply. I downloaded it to the watch. Front Camera is still reddish. That is fine. I will live with it:-)
2 Likes
You’re right, something is definitely off:
I will try to find a fix for that.
Edit:
It actually looks like a bug on the original firmware, the stock boot.img has three camera sensor drivers included:
gc5025_mipi_raw gc0339_mipi_raw gc5035_mipi_raw
And for some reason it uses the GC5035 id for the GC0339 sensor:
LensMCU : LensMCU[CurrSensorDev]0x0002 [CurrSensorId]0x5035
The custom kernel defaults to the correct id (0xC8 = GC0339):
LensMCU : LensMCU[CurrSensorDev]0x0002 [CurrSensorId]0x00c8
So the GC0339 somehow has to use the GC5035 configuration (at least on the Android side) to work correctly.
4 Likes
It sounds reasonable, because one of the cameras functions correctly. It probably uses the right driver.
I tried it, it works very well. Thank you for your time. How did you fix it?
1 Like
It mimics the flawed behaviour of the original kernel now, i reverted a patch that was supposed to fix camera detection and added the GC5035 sensor driver.
2 Likes
Wow, that sounds complicated. Thank you very much again!
I noticed the same issue on my optimus pro as well.
Photo taken with the ‘correct’ driver:
Included kernel camera driver:
gc5025_mipi_raw
Logcat:
CAM_CUS_MSDK GetCameraCalData(MainSensorIdx=5025) Enter
Photo taken with the ‘wrong’ driver:
Included kernel camera driver:
sp250a_mipi_raw gc5025_mipi_raw gc2385mipi_raw
Logcat:
CAM_CUS_MSDK GetCameraCalData(MainSensorIdx=2385) Enter
1 Like
Yeah unfortunately they don’t invest much time in “cleaning up”
As you have found 