**Happy New Year Everyone,

2025, 2015 is already 10 years ago...**

If you guys bought a laptop with a locked domain (enterprise/organization/company laptop), Windows setup locks your laptop by asking for the company email, try these method for Windows 10 to UNLOCK and SKIP the OOBE/Windows Setup :

1. At first fresh boot of Windows setup, press CTRL+Shift+F3 (to enter audit mode)
2. Open regedit
3. Go to HKEY_LOCAL_MACHINE/SYSTEM/Setup
4. Remove the value of CmdLine
5. Set value of OOBEInProgress, SetupPhase, SetupType to 0
6. Go to HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/Policies/System
7. Set value of EnableCursorSuppresion to 0
8. Open command prompt
9. type net user /add user
10. type net localgroup /add administrators user
11. Restart, you will direct enter Windows home screen, check for drivers update and etc.

Enjoy your hijacked-stolen company laptop.

Anyway, you can get latest stable CI builds HERE

GPU Undervolt, Konabess

*So i've found out something that probably not everyone already know about. As for now, GPU undervolt done by looking at this 2 aspects; no artifacts, no freezing. Those 2 things were the concern of going to the most lowest voltage possible to run.

Running on the lowest voltage with no artifacts or freezing might be a good thing. But there's something we are not aware whole this time. Microstutters.
Running too low voltage might cause device to have microstutters due to sudden spike of GPU power demand.

Let's take example of it :
- 150mhz @1 microvolt
- 205mhz @1 microvolt
- 330mhz @1 microvolt

This might sounds good since it run with no issues with the lowest voltage, but it cause microstutters. Don't run anything lower than RETENTION (@16), since it also might fasten the GPU aging.

So, i made a simple formula to have "safe" undervolt.@lowest_threshold + @16 example:
683mhz @225, it will be 683mhz @241

Lowest threshold means the safest microvolts to run without having issues like artifacts or freezing, and then added by 16.*

Kernel Naming Scheme Installation
Starting from R9 version

DO NOT INSTALL WITH SIDELOAD, KERNEL NAME WON'T BE DETECTED

\-KSU or \-ksu (This will detect kernel installer to use KernelSU). Use \-NOKSU or \-noksu if you're not using KernelSU. Leaving this unset will automatically select no KernelSU

\-EFFCPU or \-effcpu (This will select efficient cpufreq DTB image to be installed). Leaving this unset will install normal DTB image.

\-MIUI or \-miui (This will install specific DTBO image for MIUI/HyperOS). Use \-AOSP or \-aosp to use normal DTBO image. Leaving this unset will automatically install normal DTBO image.

Example :

[xxx\-AOSP\-KSU].zip
(Normal DTBO with KernelSU)

[xxx\-AOSP\-NOKSU].zip
(Normal DTBO without KernelSU

[xxx\-MIUI\-KSU\-EFFCPU].zip
(MIUI DTBO with KSU and EffCPU)

Okay, so this is my new discovery regarding Battery Health.

Recently i got issues where my phone suddenly death during overnight charging or when battery is going to full during the charge. The culprit came from bad battery and it causes voltage fluctuate, thus causing panic/blackscreen. Any battery health percentage either it's from FKM, Settings, Battery Monitoring, or whatever it is... It's not going to be fucking accurate.

The only way to predict and determine your battery health is by looking at the battery voltage nominal. If it's drops too much during heavy load, or phone dies when battery is low (10% or so), or the voltage is going over 4.45v when charging... Throw and buy new original battery ASAP, it might kill your PMIC.

Like in this example where the battery voltage shows 4.45v at 93%, which is not normal at all because 4.45v is the maximum tolerated voltage and full voltage must be around 4.35v. And then it goes up to 4.6v when plugged in, which is dangerous.

Regarding to this, i have released Alioth & Apollo Stable Beta Build.
Any feedback will be appreciated.