Androbots said:

It has been fixed, please get the latest update. Thank you!

Have you encountered the issue I described in my posts above? I've tried several times at this point, but haven't made any progress. I'd like to try this ROM, but the fastboot issue won't let me.

Androbots said:

New update out!

Changelog:
- Update blobs and firmware to 33.0210.0210.269
- Merged March Pixel Feature Drop into source
- New wallpapers!
- Major improvements to performance and battery life
- Merge MGLRU and android11-5.4_2023-03 ASB to kernel
- Removed Pixel Launcher (Reason: https://review.statixos.com/c/android_device_asus_sake/+/10348)

Download: https://downloads.statixos.com/13-TIRAMISU/sake/statix_sake-20230318-13-v6.2-TIRAMISU.zip

Note: Unfortunately, due to the massive rebase you must clean flash this update.

Click to expand...

Removing the Pixel Launcher and replacing it with Quickstep is a benefit, I'd say. You can use Shortcut Manager to theme your icons and you don't have to worry about the pesky Search and At A Glance widgets and you still get those great transition effects. It's no Nova but it'll do.

CRS10114 said:

I'm having trouble with step 4 for flashing the fastbootimage. I get my phone to reboot to fastboot, then command prompt hangs on <waiting for any device>. If I reboot to the bootloader from fastboot, then I get this error:

fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.


I have tried to do this several times, but no dice. I made sure I have the most recent versions of adb and fastboot, so I'm unsure what else I can do.

Also, would typing, "fastboot update [fastbootimage.zip]" be equivalent to typing "fastboot update" and dragging the ROM zip?

Any help is appreciated.

Click to expand...

try to boot to bootloader instead of fastboot

Androbots said:

It has been fixed, please get the latest update. Thank you!

I clean flashed the latest build from stock ASUS A13 and auto-brightness doesn't work for me either. I tried toggling it in QS and in the main Settings page to no effect.

The stock ROM reported that it was latest so it shouldn't be an issue, but I didn't flash the latest firmware separately when I flashed StatiXOS. If I get time today over lunch I'll try flashing firmware but I doubt it will change anything.

randman2011 said:

I clean flashed the latest build from stock ASUS A13 and auto-brightness doesn't work for me either. I tried toggling it in QS and in the main Settings page to no effect.

The stock ROM reported that it was latest so it shouldn't be an issue, but I didn't flash the latest firmware separately when I flashed StatiXOS. If I get time today over lunch I'll try flashing firmware but I doubt it will change anything.
View attachment 5868561

Flash the latest one. 19-03-2023 build

damarwardoyo said:

Flash the latest one. 19-03-2023 build

Is this different from 18-03-2023? I'm used to the build name and build reported version being off by a day so I didn't think anything of it.

I didn't take the originally quoted post as an announcement of a new build, but I will go ahead and download the 19-03-2023 build.

EDIT: the reported version did indeed update to 19-03-2023 so this is a different build, but I'm not in an environment where I can test auto dimming at the moment.

damarwardoyo said:

try to boot to bootloader instead of fastboot

Apologies, I should have noted that I start in bootloader as per the flashing instructions, then go to fastboot. I then tried to go back to the bootloader and received the error.

Trying to flash from bootloader also produces an error.

CRS10114 said:

Apologies, I should have noted that I start in bootloader as per the flashing instructions, then go to fastboot. I then tried to go back to the bootloader and received the error.

Trying to flash from bootloader also produces an error.

What error? Make sure you're flashing the boot and vendor_boot images, then boot into the modified fastbootd.

thatguy222 said:

What error? Make sure you're flashing the boot and vendor_boot images, then boot into the modified fastbootd.

fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

I'm assuming I've been following the instructions in the wrong order. I have been trying to flash the fastbootimage, but it sounds to me like I should be following the instructions for flashing the OTA package first instead.

CRS10114 said:

fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

I'm assuming I've been following the instructions in the wrong order. I have been trying to flash the fastbootimage, but it sounds to me like I should be following the instructions for flashing the OTA package first instead.

I was getting that error after trying to switch slots and then I couldn't boot. I had to flash the factory ROM to unbrick it.

But if you're trying to flash the fastboot version of this ROM (because maybe you're coming from stock), you need to flash the boot and vendor_boot images available here. Then you boot into fastbootd and you can flash the rom according to the directions in the OP.

thatguy222 said:

I was getting that error after trying to switch slots and then I couldn't boot. I had to flash the factory ROM to unbrick it.

But if you're trying to flash the fastboot version of this ROM (because maybe you're coming from stock), you need to flash the boot and vendor_boot images available here. Then you boot into fastbootd and you can flash the rom according to the directions in the OP.

Yes, I am currently on factory ROM WW-33.0210.0210.269.

Thank you for clarifying! I'll give it a try later today.

thatguy222 said:

I was getting that error after trying to switch slots and then I couldn't boot. I had to flash the factory ROM to unbrick it.

But if you're trying to flash the fastboot version of this ROM (because maybe you're coming from stock), you need to flash the boot and vendor_boot images available here. Then you boot into fastbootd and you can flash the rom according to the directions in the OP.

I went to bootloader and tried flashing boot.img, but got this error:

fastboot: error: cannot determine image filename for 'boot.img'

Command prompt is operating in the folder where the images are located, so I'm unsure what I'm doing wrong.

CRS10114 said:

I went to bootloader and tried flashing boot.img, but got this error:

fastboot: error: cannot determine image filename for 'boot.img'

Command prompt is operating in the folder where the images are located, so I'm unsure what I'm doing wrong.

You're running "fastboot flash boot boot.img" while in bootloader mode?

thatguy222 said:

Y

You're running "fastboot flash boot boot.img" while in bootloader mode?

I was not, but just figured it out. Everything is up and running. If it isn't obvious, I don't mess around with custom ROMs all too often. LineageOS is the only one I've used so far.

Anyway, thanks again for the assistance.

CRS10114 said:

@Androbots potential couple of bugs:

The camera seems to not want to work. I'll open the camera app (or any app that uses it, like Snapchat or QR scanner), and the screen will just be black.

Also, bluetooth is not working at all. I have tried connecting to several devices, but the bluetooth app keeps crashing or turns on and off constantly while connecting.

Thank you for reporting them. I can confirm the bluetooth bug but I cannot reproduce the camera bug. Attach a logcat for that.

Androbots said:

Thank you for reporting them. I can confirm the bluetooth bug but I cannot reproduce the camera bug. Attach a logcat for that.

I think there's something up with my camera. I flashed the stock ROM again because I needed bluetooth, but the camera issue still persists.

The weirdest part about it is that the camera will work as expected for a bit, then the focus shift to practically right in front of the phone. Once it's doing that, then the camera software freezes. After closing and reopening the app, I am met with a black screen. The camera usage indicator shows up at the top right, but the app's UI isn't there. Snapchat and my QR code scanner app still have their respective UIs, but the view will be a black screen as well. Leaving the camera alone for a bit seems to fix it temporarily, only to go back to the black screen.

Might be a good idea to create a separate post about this in case anyone else has had this problem.

In any event, thank you for the OS. From what I saw, it's really slick.

CRS10114 said:

I think there's something up with my camera. I flashed the stock ROM again because I needed bluetooth, but the camera issue still persists.

The weirdest part about it is that the camera will work as expected for a bit, then the focus shift to practically right in front of the phone. Once it's doing that, then the camera software freezes. After closing and reopening the app, I am met with a black screen. The camera usage indicator shows up at the top right, but the app's UI isn't there. Snapchat and my QR code scanner app still have their respective UIs, but the view will be a black screen as well. Leaving the camera alone for a bit seems to fix it temporarily, only to go back to the black screen.

Might be a good idea to create a separate post about this in case anyone else has had this problem.

In any event, thank you for the OS. From what I saw, it's really slick.

Click to expand...

You can still always install the build before the March one. Bluetooth will work on that one.