Development Paranoid Android Topaz Beta 4 - Redmi Note 10

[WalinAhmed]

I've been using the rom for a couple of weeks and am absolutely loving it.
But there are few adjustments to make that would really amp up the experience. It goes:

1. Reducing the status bar padding below the notch a little bit (just like in stock MIUI).
2. Having the option to toggle Fullscreen mode in Gesture settings, like hiding the gesture bar entirely and the drop-down icon while typing in Gboard.
3. Turning the display off by double tapping the status bar from any app.
4. Replacing the Google Camera Go with Aperture from LOS.

 

[carlos974]

Then it's your screen issue

My screen is touchscreen: fts-ts

 

[cyberknight777]

My screen is touchscreen: fts-ts

I just saw this commit
focaltech_touch: Rebrand to CONFIG_FOCALTECH_*

here:

Commits · sileshn/android_kernel_xiaomi_sunny

Contribute to sileshn/android_kernel_xiaomi_sunny development by creating an account on GitHub.

github.com

That is merely a fork of my kernel and that commit does nothing functionally. Your issue is specific to your replaced panel.

 

[carlos974]

That is merely a fork of my kernel and that commit does nothing functionally. Your issue is specific to your replaced panel.

Okay thank you very much.
I ordered an original amoled screen.

 

[Spaceboy60]

Can you just do a batch file with all the fastboot commands?

 

[Aribala Duraipandian]

Android auto not working, with error message as 'Your phone is not responding'.

Any help is appreciated.

 

[troolie]

I've been running the rom for about a month and so far, I like it a lot. It's a bit barebone but I have yet to run into any issue.
This thread looks pretty dead though, is the rom development still ongoing?

 

[cyberknight777]

Can you just do a batch file with all the fastboot commands?

You can copy paste the commands in a batch file anyways.

 

[cyberknight777]

Android auto not working, with error message as 'Your phone is not responding'.

Any help is appreciated.

I recall android auto working fine here, reprod and get logs.

 

[cyberknight777]

I've been running the rom for about a month and so far, I like it a lot. It's a bit barebone but I have yet to run into any issue.
This thread looks pretty dead though, is the rom development still ongoing?

Yes it's very much alive. June update was skipped due to some internal conflicts. The conflicts has therefore been resolved and currently we are waiting for a release build to be ready so we can test it and release it ASAP.

 

[troolie]

Yes it's very much alive. June update was skipped due to some internal conflicts. The conflicts has therefore been resolved and currently we are waiting for a release build to be ready so we can test it and release it ASAP.

Awesome. Thanks a lot mate.

 

[troolie]

For those unaware, beta2 is available via OTA or on the official website https://paranoidandroid.co/sunny
Changelog:

Fix IR, Fix Dual Sim Selection, Update blobs from LA.UM.9.1.r1-12900-SMxxx0.0, Merge LA.UM.9.1.r1-12900-SMxxx0.0 in kernel, Update F2FS from f2fs-stable.

 

[troolie]

Should the slide down menu (where you can toggle internet, gps, bt, restart the phone and all that) really be accessible from the lock screen on a locked device? I'm not sure it's a bug but I couldn't find any option to change that behaviour and that's just unsafe.

 

[cyberknight777]

Should the slide down menu (where you can toggle internet, gps, bt, restart the phone and all that) really be accessible from the lock screen on a locked device? I'm not sure it's a bug but I couldn't find any option to change that behaviour and that's just unsafe.

That stuff is custom afaik. @herna what's your take on this?

 

[troolie]

Looking at a stock android 13 GSI, it seems you're right. That's an actual design choice. I have no idea what weird thought process led to that glaring security flaw though.

I noticed the default device name for BT is set to Asus something. It can be renamed in the UI but it should be an easy enough fix.
BTW, android auto works fine here.

 

[rahimali]

Hi, I'm kind of new to this particular device but here's how far I've gotten:
Unlocked bootloader (the official way)
Flashed official TWRP
Formatted/wiped and flashed Topaz beta 3.
All good except TWRP seems to have been replaced with stock recovery and I'm unable to revert to TWRP through fastboot. How do I get it back?
Also, is there any harm if I flash the forced encryption disabler? Which one is recommended? I was thinking NEO. Am I on the right track?

Thanks!

 

[carlos974]

Hi, I'm kind of new to this particular device but here's how far I've gotten:
Unlocked bootloader (the official way)
Flashed official TWRP
Formatted/wiped and flashed Topaz beta 3.
All good except TWRP seems to have been replaced with stock recovery and I'm unable to revert to TWRP through fastboot. How do I get it back?
Also, is there any harm if I flash the forced encryption disabler? Which one is recommended? I was thinking NEO. Am I on the right track?

Thanks!

See instructions --> OP
don't use twrp!

 

[rahimali]

See instructions --> OP
don't use twrp!

So how do I flash something (like Magisk or any other mod) post ROM install without TWRP or OrangeFox?

 

[carlos974]

So how do I flash something (like Magisk or any other mod) post ROM install without TWRP or OrangeFox?

--> OP
Instructions (Recovery package)

 

[rahimali]

So anyone unable to flash anything after installing the ROM, at least here's how to get magisk onboard:
extract boot.img from ROM zip and copy to downloads (or whatever else) folder on the device
install the magisk app
when you run it the first time, it will ask you to provide image to flash, point it in the direction of above-mentioned boot.img
magisk will patch the boot.img and put a patched/renamed boot.img in the same location which you now have to copy to your PC as magisk_patched_boot.img
do an adb reboot bootloader
with the device in fastboot mode, do a fastboot flash boot magisk_patched_boot.img
fastboot reboot and prosper
hope this helps