Develop Bugs

Notifications is bugged as hell.

Hi,
Why is it that in the new android on the stock rom for the P2 the sound notification is bugged. I just tripped bad because this is the 10th time at least that when I NEED to be accessible that the phone simply keeps silent while it is IN NOT SILENT mode. And when I put the phone in silent mode that messages come through and my phone makes sound (when I am in a meeting).
It is frustrating like ...Mod Edit: profanity removed... hell.
What is a stable custom rom, I am flashing today got enough of this stock rom. I don't care about warranty anymore if there still is any at all.
Seriously but the software on the Lenovo Z1 was at least more stable.
Unbelieveble that they are able to mess up basically the BASIC functionality of the phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hey. Little FAQ for you:
Which Custom Rom Android Version is stable enough?
- Nougat (nearly everything), then Oreo.
Custom Roms i can recommend:
- ViperOS by BabluS. : NOUGAT
- Nearly all Roms by Subham (Cardinal AOSP; Android Open Source Illusion Project) : OREO
- AOSP Extended : OREO + NOUGAT
- Firehound : OREO
Things to note:
- There are Camera bugs when changing to Custom Roms: Taking photos is normal, but video recording is buggy. Fail Safe app for video recording: Footej.
- Most Custom Roms already have it fixed, so you can use it as a daily driver all the way.
- In-App Video recording doesn't work , e.g.: in Whatsapp or Telegram; to get it working you have to edit the build.prop file. If you need help regarding that, Pm me.
- To get Fingerprint Gestures on Oreo you have to encrypt your phone. On Nougat, encryption isn't always neccessary, like on ViperOs.
I personally am on ViperOS Nougat.
Pros: Stable Connectivity; Bugless as i can tell, counting out video recording; build in- Black amoled mode- use the built-in theming engine.
Cons: Older Android Version, but that's totally unimportant. One-key doesn't work, on any kinda rom. Maybe in the future it will be useable again.

[Shared] [ROM][Onclite]LineageOS 17.1-20210203-microG[UNOFFICIAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The full Android experience without Google Apps.
I am not developer in sence that I has developed this room. After throughfull testing around 20 rooms 9, 10 and 11, I found this room as most stable and working right out of box. As for now, Android 9 is outdated and 11th is full of bags and lacks stability. Out of Android 10 releases, Lineage OS is most polished and stable one, near to stock AOSP experience. Bunch of Gcams works with this room out of box, also Filmic pro, ANX and others. So far, only 60 fps video recording is abcent, which is not big matter. Via Magisk modules, I managed to achieve 24 bit high resourses audio play back with this room, without losing stability, which is more then enough for me. Also Dolby Atomos and Viper work flavlessly.
Since my device has only 2 gb ram, and also becouse I don't like Google look behind my sholder on everything I do, I decided to go for MicroG as Gaps replacement. Afrer trying set up Microg via Magisk module and otherwise, and experiencing numerous problems, I finally found a room which has them implemented by default: room Features
Since this room is not on xda Redmi7 forum, I decided to share its link with others, who have similar problems, like me. All credit goes to the original developers and modifiers. Download link: Download
Note: Tested on Orange Fox recovery 11.03 and Magisk 20.4.
Installation: Back up your data, such as files and downloads form inbuilt memory card. After moving to this room from Mooke 10, I have at last to format my data, since directory structure got coorupted after flashing LOS 17 (all files on inbuilt sd card were lost as sequence). From Orange Fox recovery wipe caches, system, vendor and data. Then perform formating of data. Flash the room. Flash Magisk 20.4 if you want root access. Default LOS kernel is pretty OK, but it doesn't have fast charge. I personally use SiLonT-Kernel V11.0.11 | 29/12/2020 (later build gives system error). Do not flash oficial Lineage OS updates over this room, since both has differnt signatures.
Thanks to moderator of this thread for correcting some aspects of my post.

OnePlus 7T Nethunter installation help

Hello Guys,
I was trying to install Nethunter On my OnePlus 7T Europe with Android 10
10.0.9-EUROPE-OnePlus7TOxygen_14.E.11_OTA_011_all_2003271950_b7c5bfe612-FASTBOOT.zip​ using following instruction:
Installing NetHunter On the OnePlus 7 | Kali Linux Documentation
From a reset to running NetHunter in 4 steps: Flash latest Android 10 with the unbrick tool Flash TWRP and Magisk Disable force encryption of data partition Install NetHunter Disable OnePlus update service 1. Flash latest stock (OOS) Android 10 1.01. Download and unzip...
www.kali.org
But I had used:
Twrp:
Download TWRP for hotdog
Download TWRP Open Recovery for hotdog
eu.dl.twrp.me
Magisk:
Release Magisk v23.0 · topjohnwu/Magisk
This release is focused on fixing regressions and bugs. Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 only supports Android 5.0 and higher. Bug Fixes [App]...
github.com
I am unable to install with error from screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Error Failed to mount /system_ext also appears on Magisk and decrypt tool installation.

I saw that a lot of people have seen this, but no one has commented, so I'll just throw you a few guesses. 1. Possibly a bad download of either Kali or your Recovery. 2. However, you said it happens with Magisk too, so I'm thinking it also might be the wrong recovery, are you sure that you have the right recovery.img for your model number? And if so, is it a reliable recovery.img? I know that there is guacamole, guacamoleb, hotdog and hotdogb and there were a handful of unstable TWRP builds due to the force encryption. More information about your device and resources would help, what's your model number, what version of platform tools are you on?
P.s. I'm also assuming that the photo of the log isn't of an instance where you were flashing it through Magisk as a module because you said it happens with Magisk too.
P.s.2 I know you said your phone is the Europe variant, but I'd assume not to many people memorize every model number for devices that they don't own, I'd say that's why we have codenames like guacamole, lol.

Realme x2 Fingerprint enrollment is not working anymore after RUI downgrade

Realme X2​
Hi, I have a problem with my Realme X2 RMX1993
When realme UI 2 was released I was already rooted with magisk and had the TWRP recovery installed. In order to update from RUI 1 to RUI 2 I un-rooted the phone and reverted back to stock recovery, updated the system (everything went fine and worked fine) then flashed back the TWRP recovery, and the phone has begun to boot directly to the fastboot mode even if I wanted it to boot either normally or in the recovery mode.
After messing around I managed to flash the stock recovery from which I flashed a down-grade package to go from RUI 2 to RUI 1. After that, I got the previous version of stock recovery and flashed the latest RUI 1 version and finally, the system booted up.
Everything is working nice now apart from the fingerprint enrollment which keeps flashing and vibrating without making appear the icon on the sensor.
Here is a short I recorded:
I followed step by step the instructions in these videos:
- (in the first seconds here it is how the fingerprint enrollment page flashes after the phone reset)
-
I even tried to flash the stock ozip package and tried to install other ROMs but the fingerprint enrollment still doesn’t work.
When I unlocked the bootloader the first time and flashed TWRP and magisk the fingerprint was still working fine and now it doesn't.
I even downloaded the ofp package and tried to flash it through the Realme Flash Tool but the program gives me an error message saying “Cannot find central directory”.
Can you help me, please?
Do you have any suggestions?
Thank You

Same issue on Realme Q5 pro (rmx3372 => global rom rmx3371)
i did everything nothing worked

Same issue on my realme x2 pro (RMX1931). Downgrading from android 13 custom rom to official version (android 11) led to this awful result. Any clues/solutions?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Development [ROM][13][AOSP][Unoffical] Miku UI (11-May-2023)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Miku UI is an AOSP-based Project for Mikufans!​
Miku UI Version:TDA_0.15.1
Android Version:13
Linux Kernel Version: v4.19.259
Maintainer:MZRME
Status: Unofficial
SELinux Status: Enforcing
Features:
MIUI Camera Inline
KernelSU inline
More Features on the way....
Known Issues:
Come and tell me.
ScreenShots:
Requirements
MIUI 14 firmware for Redmi K40S/POCO F4
Poco F4 Global V14.0.1.0 or newer
Download Link:
Vanilla Version Click here
Gapps Version Click Here
Recovery Click Here​CREDITS:​
AOSP
LineageOS
exTHmUI
Weeb Project
Dirty Unicorns
Device Tree: https://github.com/madmax7896/android_device_xiaomi_munch
Kernel Source: https://github.com/UtsavBalar1231/kernel_xiaomi_sm8250

Really interesting ROM, just some details which isn't your fault. Some UI things don't fit properly on some languagues like Brazilian Portuguese for example. Also no option for changing the screen refresh rate (?)
Overall it feels nice, runs smoothly and hope you develop more updates. (Thanks a lot for the kernelsu, brazilian banking apps are really a pain in the ass if you are rooted)

Another issue that I face is that some apps don't detect root using the kernelsu, althought it shows that it is installed just fine. Adaway, swift backup and other apps don't work at all

joaovti said:
我面临的另一个问题是有些应用程序没有使用 kernelsu 检测到 root，尽管它表明它安装得很好。Adaway、swift backup 和其他应用程序根本不起作用
Click to expand...
Click to collapse
you can use the magisk the mean time,but however the kernelsu will lose its ability with its module

joaovti said:
非常有趣的 ROM，只是一些细节，这不是你的错。某些 UI 内容不适合某些语言，例如巴西葡萄牙语。也没有更改屏幕刷新率的选项（？）
总体感觉不错，运行流畅，希望大家开发更多的更新。（非常感谢 kernelsu，如果你已经扎根，巴西的银行应用程序真的很痛苦）
Click to expand...
Click to collapse
i am poor in languages other than Chinese so that i cannot make a translation.For the way changing screen refresh rate，it depends on the rom source code,i cannot do somethings else.If you want more functions,make a issue in the repo of the miku-ui？

For flashing: Flash via TWRP then format data?
And what's the use of the boot.img? At what point does it needs to be flashed?

binary**# said:
For flashing: Flash via TWRP then format data?
And what's the use of the boot.img? At what point does it needs to be flashed?
Click to expand...
Click to collapse
it seems like can flash by all rec.Boot.img is the rec