Development [ROM][OFFICIAL][sake][12L] StatiXOS v5.1

[Androbots]

And there we go.

Jan builds are here!

Device changelog:
- Rebase device-specific sources for official Android 12 source drop: we now run the latest stock blobs and kernel.
- Silence a whole lot of DEBUG driver spam and stop use of TRACE_PRINTK.
- Use UDFPS instead of Lineage's FOD implementation with a slight caveat and, in my opinion, a big quirk: High brightness mode doesn't exactly work. So, you have to make sure the screen brightness is set to more than 40% at least to use UDFPS properly. However, since HBM doesn't work, there is absolutely zero flicker.
- This build has SELinux enforced. Expect OEM-like signed -user builds once we roll out OFFICIALs.

Note: You must be on 31.1004.0404.81 to flash and use this.

Source changelog:
- Our new color scheme (notice the quick settings)
- Tons of under the hood optimization
- Use our new GMS
- Bring back system wide icon packs! (Remember them in ThemePicker on Android 11?)
- Implement a ton of Pixel specific stuff as modular overrides to AOSP

Download: https://downloads.statixos.com/12-SNOWCONE/sake/fastbootimages/statix_sake-SNOWCONE-20220123.zip

Enjoy!

 

[NisseGurra]

Thanks , will try.
Signature spoofing included for microG users?

 

[Androbots]

Thanks , will try.
Signature spoofing included for microG users?

Unfortunately, we only ship GMS builds so no microG. Although, if I get enough requests, i am fine building a GMS-free build

 

[NisseGurra]

Yes, after using microg roms its difficult moving back to google bloat. Thanks anyway !

 

[Adaoh]

Yes, after using microg roms its difficult moving back to google bloat. Thanks anyway !

Same here, the difference in battery life alone is enough to make me want to stay on MicroG (And thats without talking about no google telemetry which is the main reason I use MicroG)

 

[Adaoh]

@Androbots Should the old install instructions still be used? I tried the flash script with the new rom .zip file, but it bootlooped and I had to reset. Should it be installed like many other roms with TWRP?

 

[Androbots]

@Androbots Should the old install instructions still be used? I tried the flash script with the new rom .zip file, but it bootlooped and I had to reset. Should it be installed like many other roms with TWRP?

Ah yeah, my bad. I would suggest you to use fastboot update <zip location> to flash the ROM while being in fastbootd. Will update the instructions now.

 

[Sozos]

Hello, I get the following error when I try to flash from fastbootd:
--------------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' FAILED

Device product is 'ASUS_I006D'.
Update requires 'sake'.

fastboot: error: requirements not met!
--------------------------------------------------

As far as I know, 'ASUS_I006D' and 'sake' should refer to the same device. Can you please help?

 

[Dong_9894]

Hello, I get the following error when I try to flash from fastbootd:
--------------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' FAILED

Device product is 'ASUS_I006D'.
Update requires 'sake'.

fastboot: error: requirements not met!
--------------------------------------------------

As far as I know, 'ASUS_I006D' and 'sake' should refer to the same device. Can you please help?

me too , i end up installing by script 1st , error then boot to fastbootd , install again using fastboot update , success

 

[Adaoh]

Hello, I get the following error when I try to flash from fastbootd:
--------------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' FAILED

Device product is 'ASUS_I006D'.
Update requires 'sake'.

fastboot: error: requirements not met!
--------------------------------------------------

As far as I know, 'ASUS_I006D' and 'sake' should refer to the same device. Can you please help?

Having the same issue, it says that it needs sake, but it gets lahaina. I saw a .txt file with board=sake inside it. Maybe changing that value will help, but I am too scared of writing things to bad partitions so I won't do it (Even though what is most likely going to happen is the flash will also fail because other things depend on that board=sake and just wont be found).

 

[argonautone]

I'm having trouble booting the current recovery for sake. I've tried LOS microG, and everything works fine. But I can't seem to get the recovery to sideload the latest .zip. Any suggestions?

P.S. if there was a microG version of this ROM, I'd be more inclined to use as a daily driver.

 

[Androbots]

Hello, I get the following error when I try to flash from fastbootd:
--------------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' FAILED

Device product is 'ASUS_I006D'.
Update requires 'sake'.

fastboot: error: requirements not met!
--------------------------------------------------

As far as I know, 'ASUS_I006D' and 'sake' should refer to the same device. Can you please help?

me too , i end up installing by script 1st , error then boot to fastbootd , install again using fastboot update , success

Having the same issue, it says that it needs sake, but it gets lahaina. I saw a .txt file with board=sake inside it. Maybe changing that value will help, but I am too scared of writing things to bad partitions so I won't do it (Even though what is most likely going to happen is the flash will also fail because other things depend on that board=sake and just wont be found).

Hmm. Try this: flash this while you are in the bootloader (the one with START in green) https://downloads.statixos.com/12-SNOWCONE/sake/bootimages/boot-sake-SNOWCONE-20211101.img to the boot partition. From there, `fastboot reboot fastboot` and run the `fastboot update` command as usual. You should be all set. I did not see this coming, so will update instructions to flash one of the StatiX boot images beforehand.

 

[Adaoh]

Ok, so if my understanding is good, what we should do:

1. Flash the latest firmware from Asus
2. plug-in the phone open a terminal/cmd, type

   adb reboot bootloader

   or shut down and press volume up + power
3. Type

   fastboot flash boot boot-sake-blablabla...

   (The file in the last comment)
4. Type

   fastboot reboot fastboot

5. Type

   fastboot update {rom file}.zip

Is this right?

EDIT: With this method, I actually got farther, but I got a bunch of other errors...

 

[thatguy222]

Those errors saying the archive does not contain certain files is fine. Let it finish, reboot. It will boot into LOS recovery saying there is not OS (or something). Format datsla (your only option). It will now reboot into Statix.

 

[thatguy222]

Loving the rom, @Androbots. Few things I noticed after installing:
- When finally get into Android each time you reboot you get an error messaging say something about an internal error. You can just press OK to get by it.
- Double tap to wake doesn't seem to work.
- Lift to wake doesn't seem to work.
- Greyscale feature doesn't work in Bedtime Mode
- Can we get eSIM functionality added?

Thanks!

 

[Androbots]

Ok, so if my understanding is good, what we should do:

1. Flash the latest firmware from Asus
2. plug-in the phone open a terminal/cmd, type

   adb reboot bootloader

   or shut down and press

   volume up

   +

   power

3. Type

   fastboot flash boot boot-sake-blablabla...

   (The file in the last comment)
4. Type

   fastboot reboot fastboot

5. Type

   fastboot update {rom file}.zip

Is this right?

EDIT: With this method, I actually got farther, but I got a bunch of other errors...

Those red arrows pointing to archive doesn’t contain xyz is harmless. Your steps seem to be fine so I’m slightly confused why you’re getting those errors at the end. Are you using the latest platform tools? I also see vendor_dlkm missing in there so that might point to you not having the latest platform tools. Can you check?

 

[Androbots]

Loving the rom, @Androbots. Few things I noticed after installing:
- When finally get into Android each time you reboot you get an error messaging say something about an internal error. You can just press OK to get by it.
- Double tap to wake doesn't seem to work.
- Lift to wake doesn't seem to work.
- Greyscale feature doesn't work in Bedtime Mode
- Can we get eSIM functionality added?

Thanks!

Thanks for trying StatiX out!

- I’ll look into it today hopefully
- ^^^
- Seems like Night light, extra dim and bedtime mode don’t work for some reason. Will look into it
- I don’t think sake supports eSIM? At least my variant has two physical SIM slots.

 

[thatguy222]

Thanks for trying StatiX out!

- I’ll look into it today hopefully
- ^^^
- Seems like Night light, extra dim and bedtime mode don’t work for some reason. Will look into it
- I don’t think sake supports eSIM? At least my variant has two physical SIM slots.

Thanks! You're right, mine (US variant) also has two SIMs. A Google search does not help clarify. Perhaps someone on stock firmware can check.
Also, I was wrong about lift to wake; it does work. I think it turned it self off a couple times, though. Not sure how that would be possible.

 

[Adaoh]

Those red arrows pointing to archive doesn’t contain xyz is harmless. Your steps seem to be fine so I’m slightly confused why you’re getting those errors at the end. Are you using the latest platform tools? I also see vendor_dlkm missing in there so that might point to you not having the latest platform tools. Can you check?

It should be up to date. I am on the latest version of platform tools, as I updated everything the day before via apt (I am using PopOS, which is based on Ubuntu). I can retry on Fedora

 

[thatguy222]

When I try to set up the fingerprint reader, it just keeps saying Clean the Reader.