Problem with Android 10 and Magisk - Xiaomi Poco F1 Questions & Answers

I'm experiencing problems with apps and UI freezing when I install magisk on Android 10.
There is no problem whatsoever if I don't install Magisk.
Everything works for a minute after boot, but if I open something after that, it just freezes.
I've had this problem with ArrowOS, so I changed to crDroid. The 8/10 build of it was working perfectly but updating to 21/10 has a problem.
I've attached the log where I try opening Whatsapp but it gets stuck on the splash screen. The log says "notResponding = true".

Related

Sound not working or repeat reboot in a strange way (HDX8.9)

the device was alright at fire OS 3.x.x. when i upgraded the system to 4.x.x, the frequent reboot occurred (like every 3~5 min). then i flashed in CM to see if it's the problem with OS, the reboot is still there, but strangely, if i left the device for a while (a few hours), the sound stopped working, but the reboot is gone. so it's sound or reboot for me now:crying:. Any one know what's this about? THANKS!

Android heavy lagging/freezing/desktopscreen moving left<->right [HELP]

Hello guys,
So, i have rooted my Device (BQ M5) 1 Month ago and installed Xposed on it. Everything was fine until yesterday, where i was underway and streaming via Chrome a video. I didn't close Chrome and simply locked my phone. Several minutes later, when I tried to unlock my phone, i directly noticed heavy lag (response 2seconds - 2min - locks device). I thought a reboot might solve this issue, but i was wrong. I started to uninstall several previously installed apps and tweaks (where the newest App/Tweak was 8 days "young".
After a reboot, still heavy lagging. I opened TWRP and Cleared Dalvik and Cache, did a reboot in System, Recovery and Bootloader. I even flashed the device with a complete fresh OS. The problem still remains. After several re-flashings, some cache clear, factory resets and SuperSu unrootement i somehow managed to get it to work again. So I started from 0 again, and installed all previous apps, and root apps. Everything was fine for several hours (connected to Wi-Fi), so i was installing Xposed again, with 2 apps/tweaks: Flat Style bar, youtube adaway. Everything was still allright untill i left the house. I unlocked my device 50min later (for the first time when i left my house) and boom, the lagging was back. (Don't have internet outside my house).
As soon as i came back, i retried everything to remove the lag, however I did now several things in addition for over 3h and the lagging sill remains. I down and upgraded the OS, formatted the data, did every clear in TWRP and Bootloaded that i could find. I reset it via Settings and flashing. I installed SuperSu and de-installed it.
I don't know what else i could do, to solve this issue. The lag remains when using TWRP, Bootloader, using the Device, or when the Booting animation of android appears (slow animation or with a "fps of 0,05").
Please help me!
Device: BQ M5
Had Android 5.1.1. on it and Installed xposed sdk22 arm, and installed SuperSu via TWRP.
All files were downloaded from official posts here on xda, or from the brands website.
p.s. Even the littlest information which could help, please share!
p.p.s Here's a video that shows whats going wrong. After the reboot the booting animation continues like this around 1-3min. and then at the unlock screen, the "lag" still remains. What i noticed too, is that the charging animation in the top right is running flawlessly, however opening apps and all the rest is really slow!
youtube(dot)com/watch?v=Htuhj8UzWs4

Touchscreen freeze and soft bootloop with Magisk v18.1

Direct questions at the bottom...
I didn't see anything about 18.1 causing issues (still see some about 17 causing bootloops) so I figured I'd start here before reporting a bug with Magisk.
After hitting the Google Pay update (but before finding that thread) I figured it was time to move from Magisk v17.1 to v18.1. Unfortunately patching 20d with the new Magisk Manager v7/v18.1 didn't work. I flashed the patched 20d boot image (adb/fastboot - no TWRP for me) and the phone booted up just fine and I swiped to see that my launcher was working and then the touchscreen stopped responding. The power button continued to function (would bring up off/restart/airplane mode menu). After a few moments the phone 'rebooted' in that the LG logo came up and then I was presented with my start screen again. The phone didn't fully reboot as it didn't go through secure startup, but I did have to enter my passcode to unlock and again my launcher worked for a few seconds before the touchscreen freezing. Between this and a few hard restarts (pressing and holding power and voldown) I was able to start and get into Magisk Manager which prompted me 'Your phone needs some additional setup - do you want to download magisksetup now to finish setup?'* It was only one time as every other time I could not get Magisk Manager to start fast enough to prompt me such that I could accept the 'extra setup' before the touchscreen froze. I later did the whole song and dance after dirtyflashing 20g, rebooting after Android did it's 'upgrading' thing and flashing the patched 20g boot - same touchscreen freezing after a few seconds. (NB: if you need fastboot, press and hold voldown same as if you wanted download mode for LGUP with volup). I had ADB setup & my computer trusted throughout all this and adb would disconnect when the phone did its 'reboot' thing so even grabbing logs is tough.
I ended up writing a custom json file and pointing the update channel in Magisk Manager v6.1.0 (185) at it to get v17.3 (17302) installed which doesn't exhibit the behavior. Stock is fine, but I'm not missing out on root.
*: Only time I've seen this message in person or in other various threads.
1. Has anyone seen the touchscreen becoming completely unresponsive with or without soft bootloops using Magisk or similar? Maybe it's because of RCTD (never experienced it on LG and Sony's RIC I think just rebooted)?
2. Any idea on how to gather logs in this case so I could make a bug report?
I'm starting here as I don't want to blame this on Magisk alone just yet as long as I can't seem to gather logs and I haven't seen this weird half bootloop reported on other phones.
Hi, had the same problem with the touchscreen and Magisk 18.1, all was totally slow, apps needed seconds to respond and so on.
Bootloops never.
My solution: gone back to Magisk 18 and all problems are gone. So it seems, there is a Problem withe Magisk 18.1 and our phone. I have the European H930.
Regards
mkpcxxl
mkpcxxl said:
Hi, had the same problem with the touchscreen and Magisk 18.1, all was totally slow, apps needed seconds to respond and so on.
Bootloops never.
My solution: gone back to Magisk 18 and all problems are gone. So it seems, there is a Problem withe Magisk 18.1 and our phone. I have the European H930.
Regards
mkpcxxl
Click to expand...
Click to collapse
Owh, I thought that it was the gcam. I have been flashing the roms 21w for multiple times and still have the freeze sometimes. A force restart is needed everytime...

[Solved] Custom Roms getting stuck after language selection screen

I am facing strange problem on my Redmi Note 4. Custom Roms are getting stuck after language selection screen on first boot. I had been using Resurrection Remix (Official) – Pie Rom on this phone earlier. Due to some reasons, I had to flash the stock MIUI rom. Thereafter, I flashed the latest TWRP 3.3.1 in fastboot mode and installed the latest build of Resurrection Remix (Official) – Pie (7 July 2019) via TWRP. The Rom installed successfully without facing any encryption problem because I had formatted my data partition prior to flashing Rom.
After flashing Rom, the System boots and Set Up Wizard initiates with the screen giving me option to select language. After I select language and press next…the phone goes to next screen ‘Just a Sec…’ and thereafter remains there forever. The screen blinks after some time and goes blank, then it comes back to ‘Just a Sec…’. It simply doesn’t let me go beyond that.
I tried two more builds of Resurrection Remix – Pie, but again the same story.
I tried to flash Pixel Experience (Official) – Pie, but the same story.
I believe, Set Up Wizard is stuck with some thing and doesn’t let me through. The Resurrection Remix (Official) – Pie (20 January 2019) build came to my rescue as this rom doesn’t initiate Set Up Wizard at first boot and simply goes to desktop. Thereafter, Set Up can be completed any time and doesn’t create any problem.
As 20 January 2019 build works fine, I tried to dirty flash the latest build over it with the hope that Set Up Wizard won’t come up. The dirty flash goes without error and phone boots to system. But this time, phone gets stuck while trying to get to desktop screen and message keeps showing forever on the screen ‘Phone is Starting’. I can see the desktop image in the background. The screen goes blank in between and then message keeps showing again. It simply doesn’t let me pass through. In this scenario, I can access the pulldown and go to settings. I did check, phone wasn’t encrypted because I had not used any pin, fingerprint etc. on the working rom prior to dirty flash of latest build.
Can anyone help me as I simply cannot install any Custom Rom due to this problem. I have been left with only two options, either to stick with 20 January 2019 build of Resurrection Remix, which doesn’t initiate Set Up Wizard at first boot or to bloatware loaded MIUI stock rom.
What I tried :
1. Tried to rename the SetupWizard.apk file to SetupWizard.apk.bak in TWRP to evade first time Set Up Wizard but in this case, screen doesn’t show any thing and goes blank at the time just before going to desktop. It didn’t work.
2. I tried TWRP backup of another Redmi Note 4 having latest build and restored backup of four partitions of that phone (vendor, boot, system and data) on my trouble creating phone. The system booted but it also got stuck at ‘Phone is Starting’ Screen while showing me desktop in the background. I could enter the settings through quick pulldown in this scenario.
Please help me resolve this problem.
I have obtained catlog files through adb while my phone was booting after dirty flashing latest RR build (August 2019). Please note that I can't go beyond Just a Second screen, in case I go for clean flash after data format. Therefore, I flashed RR January build first, which works without any problem. Then settled my phone and thereafter updated it with latest RR (August 2019) build by dirty flashing. Phone accepted my pin on startup screen and then went ahead with showing 'Phone is Starting'. The phone never passed through that screen.
I have obtained two files, one with Error option and other is complete log. Please help me understand the problem, so that I may update my phone with latest RR build, else I may remain stuck with January build only.
https://drive.google.com/open?id=1zVXYxdQ5epImYTOiXSs1tIFB8uTwNV2p (Complete Log File)
https://drive.google.com/open?id=1YYXbdq7csCwskCtgtn2uWYG4rXWng4em (Log File with Error Tag only)
I kept trying Rom after Rom and finally, the AOSiP Official Rom is working great on my phone. Every thing went smooth with this Rom.
Moderator, please close this thread.
Thread closed at Op's Request.
Thanks
SacredDeviL666.

Screen off after initial boot - Redmi 5 plus - on Custom Rom

I flashed a Redmi 5 plus with lineage 17 successfully then i rooted it. I wanted to install Revolut and other banking apps but they don't work with root so tried to unroot but was not possible as it got corrupted so reflashed it back to stock rom android 8.1 and worked fine.
I tried again to flash Lineage 17, 16 and also Paranoid Android but each time I boot put the screen turns off. The boot seems to start up but the screen is off.
I reflashed it back to stock rom and it gave me an error on startup saying "Find Device Storage Corrupted, Your Device is Unsafe Now" and keeps rebooting.
Any clues?
berex said:
I flashed a Redmi 5 plus with lineage 17 successfully then i rooted it. I wanted to install Revolut and other banking apps but they don't work with root so tried to unroot but was not possible as it got corrupted so reflashed it back to stock rom android 8.1 and worked fine.
I tried again to flash Lineage 17, 16 and also Paranoid Android but each time I boot put the screen turns off. The boot seems to start up but the screen is off.
I reflashed it back to stock rom and it gave me an error on startup saying "Find Device Storage Corrupted, Your Device is Unsafe Now" and keeps rebooting.
Any clues?
Click to expand...
Click to collapse
Have the same problem with my 5 plus, just keeps rebooting, also when the charger is not plugged it just shutdown before booting to bootanimation. Do you already solve yours? Can you help me?

Categories

Resources