-
Notifications
You must be signed in to change notification settings - Fork 11.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nothing Phone (1) OS 1.5.3 freezes and ramdumps during boot after boot.img is patched #6780
Comments
I have the same problem, on my nothing phone 1 after the latest 1.5.3 update. Unlocked bootloader, Magisk with 3 modules. I amusing this config on this phone from the beginning, without any problems, so it has something to do with the 1.5.3 update. |
Same here, restored original boot imgs, now the phone is stable again. Sadly there's no way to downgrade to 1.5.2 AFAIK. |
maybe you trigger a crash without zygisk and any modules and share the bugreport? Cannot see anything useful from the log tho. |
BTW, can you adb when the phone freezes? If so, you'd better capture bugreport during freeze. |
Just tried that. ADB still works when the whole system is frozen - I managed to start capturing a bugreport, but it stuck at 0%. ADB shell was still possible afterwards, but then the dumpstatez service seems to have crashed:
Once a magisk-patched boot img is used, any process that uses a lot of resources seems to crash almost immediately - SystemUI with it. I've triggered the freeze by using ReVanced to patch a YT apk - it froze after about 5 seconds, UI completely stuck and unusable (the above is from that time). Edit: I'll try once more, but not much hope over here. Edit 3: With zygisk and modules off, it seems to take a little longer to crash, but still no dice with the bugreport, as the service crashed at 8% (phone freeze):
Edit 4: All those freezes seem to have corrupted my partition slot A (doesn't boot anymore); B works, but I'm not inclined to continue and risk a softbrick tbh. |
Just triggered a crash without zygisk and modules but im at work, as soon as I'm home i'll try to upload an android crash report To cause a crash REBOOT THE PHONE As soon as it boots, unlock it, open discord so that it automatically reconnects I then rebooted, went to developer option to get a complete bug report. There could be sensitive data, is there a way i can send it to you privately? CrashLog.txt was produced by logcat through adb. EDIT: Producing a log while the phone crashes is impossible because it becomes irresponsive to anything. |
Same problem here. |
On my side I have the bug report from the 1st freeze, the one I've talked before, no zygisk but modules (busybox, systemless host and revanced) on: 2nd freeze, 00:14 cest 24/03, no zygisk, no modules, crashreport with adb logcat and bugreport with android Also a user on Telegram shared their logcat which they talked about it having irregularities What I've noticed is that without zygisk the system moves from using around 3.5GB of ram to 4.1 average. EDIT: does magisk change the permission of something/a process in the system? |
Since adb is accessible when problem happens, can you get me some logs by |
I have the exact same problem on 1.5.3 with hotfix, and logcat looks exactly the same, so here are my logs attached (without zygisk): The way I trigger this is just randomly open many apps, as the discord method mentioned previously didn't work well for me. Also I think this is related to memory, since memory usage during freeze is unusually high (normally it's around 4GiB used)
It is worth noting that when freezing the device sometimes showed up as offline in adb, and the only way to interact with it is to long press the power button to reboot. Hope these help. |
Even if the device is in the adb devices list, the logs created are empty. EDIT: The phone just rebooted on its own after freezing while locked |
In my case the freeze is always the whole system. Don't know why, but my apps don't crash - the whole phone freezes when it does. |
Yeah that's also my case, I suspect that the systemui got stuck because of OOM. Tried to restart the systemui from adb but it also stuck. |
Nothing I've tried for three days to get any log but now i need a working phone and to use banking apps. It's much easier to get a logcat at freeze with zygisk and the log file is filled with super critical pressure event polling check, the "suspicious" error in the screenshot a user provided in one of my previous messages. |
Two interesting situations I had were when I used Spotify and device froze but music still played via bluetooth speaker and I could change songs via remote device so both bluetooth stack and app still worked. The second situation was while using camera app - the whole system froze but live preview in camera app was working - this was the only time app was showing some kind of UI update after freeze. |
Same issue here, version 1.5.3 fresh installed with patched boot. Multiples freezes (on Camera app, etc...), hard reboot is the only way to get phone works back. EDIT : as noticed before I have the same issue with last Magisk Canary version |
There is this in changelog of 1.5.3 maybe it's the cause of the issue |
I have facing the same problem and I downgrade the OS 1.5.3 to 1.5.2 |
Did you lose all your data? |
That would make a lot of sense IMHO. Most logs posted here had some kind of OOM issues. Is anyone actively looking into this ticket? All up-to-date Nothing Phone 1's are affected. |
You have to flash 1.1.7 stock firmware via fastboot comands and then simply update to 1.5.2 with ota updates. |
Might be a memory leak. I remember seeing the ram full and logcat showing lots of processes restarting over and over until the ramdump occurs. |
I just use fastboot to flash full 1.1.7 version |
If anyone finds the reason, please open a new issue. |
Wait, how does closing this issue help here? What info do you need? We've tried to comply with the log requests as well as possible. If it's not enough, please point us in the right direction. The only thing that'll happen is that people who have the same issue (everyone on Nothing Phone 1 with current firmware who tries to root) comes and creates a new duplicate ticket. |
Yeah right |
how are you adding script? |
I created an .sh script on pc, pushed to the phone and then with termux copied it to /data/adb/post-fs-data.d Then i tried doing a magisk module which didn't set the persist.sys.mglru_enable property to false and now even with the older script resetprops does not set anything i also tried it with the verbose option but it's not outputting anything. Magisk shows it executing tho UPDATE: i tried rebooting into bootloader and then into system again, now with only the script in post-fs-data.d i again have the property set to false. |
You don't have freeze anymore with this workaround? |
Here's my Magisk module, it's working (at least for me). |
your module acts exactly as mine so for me doesn't work now all rest is for magisk "experts" to find a good way to fix this |
We are gettin off topic with this but mine stays at zero, try to check for other modules or settings in your phone. Anyway if freezes or crashes are encountered i will update this thread. If 24h passes without issue i'll also let you know |
Hi, I just wanted to mention disabling mglru seems to work on my phone, though the Magisk module doesn't (same issue as gwolf2u). It's only been a few hours without crashes, but since the longest I've went with Magisk on the latest firmware was about 5 minutes before having to force a reboot, I'd at the very least call it an improvement. |
Try this new version if it keeps changing maybe magisk is logging something about it https://github.com/LukeSkyD/NP1-MGLRU-FIX/releases/tag/V2 Remember to perform a cold boot Still no crashes for now, I've rebooted the phone one time for the module's update, seems like MGLRU is the culprit. |
Multiple devices and kernel have ported mglru but unlike np1, most of them are 5.10 kernel devices. Not sure if Nothing ported it right, or it is a real compality issue. I would suspect it is actually related to some weird cgroup issue as magiskd switched cgroup to prevent itself from being killed. |
|
Based on the current investigation, I wonder if there's something Magisk should do about it. For NP users, maybe a custom module for this is more helpful. 🤔 |
So far only two people out of around 50 reported freezes with mglru disabled The module only mitigates the problem. So Nothing's implementation of mglru is the problem. |
Multiple custom kernels with MGLRU does not have issues (mostly 5.10+ kernel). So I will suggest that Nothing did sth wrong. Actually Nothing gets patches from a Google port of MGLRU (https://android-review.googlesource.com/c/kernel/common/+/2324610/5). MGLRU is new and many fixes are not ported in this chain. |
I installed a magisk module to disable the lru feature yesterday. I'm 100% sure LukeSkyD's module is installed at this moment and I'll triple check if mglru stays disabled tonight. |
there seems to be some trigger in the system that sets the prop to true again resulting in a crash |
How about chown/chmod that 'enabled' node... |
Change-Id: I7ca338de39c64041744b818ce8647813575cc8e4
Change-Id: I0c8a77a3ef70b96c4479948fe5eafe6b95b44900
1.5.4 should have fixed this issue. |
Lru_gen/enabled is set to 1, not 3 anymore I've been using .4 for around 18h and no crashes or freezes so far, no crashes reported by the community either |
With unlocked bootloader and stock boot the phone works ok; with a patched boot img freezes and/or ramdumps during use are common.
Sometimes they happen right after boot, other times they can take a while.
This happens with and without modules installed, with or without zygisk as users have reported.
In the crashLog file i encountered a freeze, no ramdump.
Device: Nothing Phone (1)
Android version: 13
Nothing OS Version: 1.5.3 and 1.5.3 HOTFIX are affected, both EEA and Global variant of the phone, <= 1.5.2 versions work fine
Magisk version name: 25.2 but also d251c288
Magisk version code: 25205, 25210
crashLog.txt
Photo of a user reported ramdump
EDIT:
Here are some boot images:
1.5.2 stock
1.5.2 magisk
(they are both working)
1.5.3 stock
1.5.3 magisk
1.5.3.hotfix stock
1.5.3.hotfix magisk
(magisk patched boot freezes)
EDIT 2:
In my naivity i thought it was a problem with the ramdisk, so i packed a custom boot img with 1.5.2 magisk patched ramdisk and 1.5.3.hotfix boot and kernel, still crashed.
I've noticed the phone crashing a lot more with app like discord opened in background. Also discord disconnects my client easily if i multitask opening other apps.
Using the phone slowly seems to mitigate the problem, like it seems the phone boots things before it actually loaded them correctly.
Example: the phone crashes a lot faster if at boot i immediately unlock, open discord and join a voice server with a bluetooth headset, exit while still connected and open like a magazine app.
I don't get crashes only at apps' startup, even during normal use, like yt in background with some music at a certain time the music stops like the buffering but without the loading circle, the phone is still usable for 2 seconds and then freeze.
I checked the ram usage and it never goes over 3.5GB or very rarely so it doesn't seem like a memory leak is the cause.
The text was updated successfully, but these errors were encountered: