PUBG starts fine but after 4-5 mins crashes and phone goes to home screen without any system message. this happens in match but even in lobby.
I reinstalled pubg and repaired it but no use.
I first found this issue when I installed EU rom as I went back to global India 11.0.4 updated to 11.0.7, and again went back to 11.0.4 problem was present in all of them.
I don't know what is causing this issue. or PUBG itself has to blame. anyone else having this issue?
Use magisk hide
If Your Phone is rooted this will happen. Hide magisk with different name. PUBG crash :laugh::laugh:
amantu said:
If Your Phone is rooted this will happen. Hide magisk with different name. PUBG crash :laugh::laugh:
Click to expand...
Click to collapse
I had pretty similar issue. all starts after using magisk. later i update new rom and everything but nothing changed. all i found out that there are some dns related module exist in magisk. do not install those.just hide pubg in magisk setting and rename magisk thats it. i am using eu rom with a custom karnel. magisk is working perfectly so as PUBG
Related
Hey Guys, can someone tell me what Magisk version works and does not result in a bootloop or has other negative effects? The last time I used Magisk I had problems with 15.x, are all issues are now fixed or are there still some remaining?
Lukke2804 said:
Hey Guys, can someone tell me what Magisk version works and does not result in a bootloop or has other negative effects? The last time I used Magisk I had problems with 15.x, are all issues are now fixed or are there still some remaining?
Click to expand...
Click to collapse
I am using v15. 3 without any problems..
Magisk hide is having some problem with fingerprint recognition.. Some times when magisk hide is on finger print wont work. Its a problem with all the magisk versions i tried . So i turned it off.
Latest version works for me, although it doesn't pass the Safety net checks. Therefore some finance programs may not work, but root and modules work fine.
I am currently on rooted OOS stable v 9.0.0 with blu_spark v51 and xXx mod. My OOS camera kept freezing/crashing and I have to force rebooted it everytime. Anyone have encountered this problem? Please advise
Try stock kernel, some reported having issues with cam + custom kernel. No idea why not all is affected.
Yes, I'm having very FREQUENT issues where the entire system freezes and locks up and I have to hard reboot. Happens very often when opening the WhatsApp camera (from the photo button in the text field on any conversation) as well as once in the actual camera app, which I've only opened a couple of times since switching over to the phone. It's infuriating really. This is the kind of bug you expect from poorly-made custom roms, not software that is supposed to be a stable, professional release.
This is on a 6T, though, but the software is very close and I've seen numerous people complaining about the same issues on both devices over on the OnePlus subreddit.
And to clarify, I'm running stock except for having Magisk root. This is a problem in stock OOS that OP needs to address.
Same issue here
9.0.2 Pie on OnePlus 6
Rooted with Magisk 17.2
Camera/phone will freeze close to every time I open it
Restart the device and it will open
Can't seem to find much about it on OnePlus forums except for people saying to reset the cache and then closing the thread off
I'm having the same issues...
Any new solutions?
ult1m4tum said:
Same issue here
9.0.2 Pie on OnePlus 6
Rooted with Magisk 17.2
Camera/phone will freeze close to every time I open it
Restart the device and it will open
Can't seem to find much about it on OnePlus forums except for people saying to reset the cache and then closing the thread off
Click to expand...
Click to collapse
rasluht said:
I'm having the same issues...
Any new solutions?
Click to expand...
Click to collapse
This solution in the 6T forum seems to have worked for me: https://forum.xda-developers.com/showpost.php?p=78138000&postcount=3
Specifically, I uninstalled the camera using magisk debloater then reinstalled the version from apkmirror... so far it all seems fine now.
Is the rom flashed in both a/b partition? Some people have solved these freezing issues by flashing on both a and b because they only flash in one partition not both which caused their cams to freeze. Uninstalling the cam and reinstalling could also help
possible fix
my gcam mod and the stock camera crashed always when i opened them, i'm also on xXx rom with custom kernel.
i have nova launcher and when i flashed xXx again, like to update and have nova launcher in xXx profile activated it causes my camera apps to crash. Disable your launcher and try your cameras. Maybe this helps someone.
I am on Oxygen OS 9.5.8.GM21AA. Recently I met the random restart problem. And it become more and more frequent. I have Magisk and EdXposed installed, but I have not update or install new modules recently.
The problem most time happened when I swipe from bottom screen to switch apps. And the whole phone become black. And several seconds later. It will automatically restart. The phone is showing "The phone is restarting" message.
I was tried to disable EdXposed modules one by one, but still not found any incompatible.
einverne said:
I am on Oxygen OS 9.5.8.GM21AA. Recently I met the random restart problem. And it become more and more frequent. I have Magisk and EdXposed installed, but I have not update or install new modules recently.
The problem most time happened when I swipe from bottom screen to switch apps. And the whole phone become black. And several seconds later. It will automatically restart. The phone is showing "The phone is restarting" message.
I was tried to disable EdXposed modules one by one, but still not found any incompatible.
Click to expand...
Click to collapse
Are you using a custom kernel? Updating to 9.5.9 might also help.
harpin14789 said:
Are you using a custom kernel? Updating to 9.5.9 might also help.
Click to expand...
Click to collapse
I am using ElementalX kernel. And i just update this kernel to 1.11, let's me check any problem than.
einverne said:
I am using ElementalX kernel. And i just update this kernel to 1.11, let's me check any problem than.
Click to expand...
Click to collapse
I also have the same issue as you.
This issue is a kernel related issue, oneplus is aware and will push an update in the near future.
As far I know, Fraken kernel is the only that seems to have fixed this issue, so I suggest you flash that, atleast till, OP pushes an update to fix this issue. I have tried all the kernel 7pro and have the issue with every single one. But hvae not the issue in over a week with fraken.
Good Luck!:good:
Has anyone else noticed that magisk has stopped working? The latest addition? There is no longer any access to hide magisk features with the latest features?
For instance for Pokemon Go to work on a custom rom you need magisk hide to hide magisk an hide from app.
I cannot even get it to open after it forces update?
Bryceicle1971 said:
Has anyone else noticed that magisk has stopped working? The latest addition? There is no longer any access to hide magisk features with the latest features?
For instance for Pokemon Go to work on a custom rom you need magisk hide to hide magisk an hide from app.
I cannot even get it to open after it forces update?
Click to expand...
Click to collapse
Happy new year. Maybe reinstall Magisk manager? For me it works perfectly, just be sure to install 21.2 magisk and you should be good to go.
Slim K said:
Happy new year. Maybe reinstall Magisk manager? For me it works perfectly, just be sure to install 21.2 magisk and you should be good to go.
Click to expand...
Click to collapse
I actually listened to another members post an have had success flashing an rooting 3 roms that I could not do either of those with. Apparently there is some kind of conflict bwteeen something in android 10 an android 11. So Ofox 12.0.6 an global firmware for surya 12.0.3.0 are the solutions.
Magish 21.0 worked every time with an android 11. Neither 21.1 or 21.2 worked for me with A11 roms. Only magisk 21 had full functionality
Bryceicle1971 said:
I actually listened to another members post an have had success flashing an rooting 3 roms that I could not do either of those with. Apparently there is some kind of conflict bwteeen something in android 10 an android 11. So Ofox 12.0.6 an global firmware for surya 12.0.3.0 are the solutions.
Magish 21.0 worked every time with an android 11. Neither 21.1 or 21.2 worked for me with A11 roms. Only magisk 21 had full functionality
Click to expand...
Click to collapse
Weird . For me it was the opposite. I had to flash global MIUI 12.0.4.0 to make anything custom work. Until I upgraded to 12.0.7.0, ever since everything works perfectly. Magisk below 21.0 never worked for me on this device.
I have a hypothesis, that all device variants (Indonesian, European, global, Russian) have different vendors and not 100% compatible, Maybe different modem configuration as well. I noticed in mine (European version) that LTE battery consumption is a lot better (by 2hrs SOT!!!) so i'm confused on what to do. Should I stay on MIUI with all it's issues or switch to a custom ROM and lose 1-2 hours of screen on time.
Slim K said:
Weird . For me it was the opposite. I had to flash global MIUI 12.0.4.0 to make anything custom work. Until I upgraded to 12.0.7.0, ever since everything works perfectly. Magisk below 21.0 never worked for me on this device.
I have a hypothesis, that all device variants (Indonesian, European, global, Russian) have different vendors and not 100% compatible, Maybe different modem configuration as well. I noticed in mine (European version) that LTE battery consumption is a lot better (by 2hrs SOT!!!) so i'm confused on what to do. Should I stay on MIUI with all it's issues or switch to a custom ROM and lose 1-2 hours of screen on time.
Click to expand...
Click to collapse
I've sorted everything out. I recommend the firmware you already use for android 11 custom roms. One rom I read other guides for an watched YouTube guides. It's EvolutionX 5.2. It has basically converted my Poco X3 NFC global into a Google pixel 5.
This rom is head an shoulders the best rom for our device. It only needs firmware 12.0.7.0. Which I also found solved all issues an to be flashed from the phones internal memory.
It's beautiful. No bugs. I only use that new twrp ending in 15 an magisk 21. Newer magisks fail to root.
But yes could be to do with different countries.
Edit: Evolution is not the highest benchmarking. An is not the fastest. Its an all round rom for daily driver use. Antutu bench's in the mid 270-280k area.
Hi,
kinda new to custom ROMs and running into my first real problems.
I installed TWRP, LineageOS 20.0, BitGApps Basic and Magisk 26.1 on my Samsung Galaxy S10e Exynos.
After setup everything works extremely well and fast. I installed Universal SafetyNet Fix, Viper4Android (programminghoch10/ViPER4AndroidRepackaged: A refined ViPER4Android installer. (github.com)) and Universal GMS Doze (gloeyisk/universal-gms-doze: Patches Google Play services app and its background processes to be able using battery optimization (github.com)). The phone still works fine and Viper4Android works too. SafetyNet also passes.
Now the problems arise. A few hours later and some reboots later, the phone won't boot anymore (maybe 20 reboots). I didn't even change any settings before the reboots. The boot animation plays and the phone is getting reset by a watchdog maybe. Also cannot use ADB during boot and the safe mode button combination doesn't work. I'm not experienced enough to understand the log files correctly. I already flashed the phone twice and the same problem occurred.
I attached some logs I could get from TWRP, but the main data partition is encrypted.
Full log files are here: logs.zip
Otherwise I'm extremely impressed with Lineage and would love to use it as my daily.
Thanks a lot for helping.
loriZyy said:
Hi,
kinda new to custom ROMs and running into my first real problems.
I installed TWRP, LineageOS 20.0, BitGApps Basic and Magisk 26.1 on my Samsung Galaxy S10e Exynos.
After setup everything works extremely well and fast. I installed Universal SafetyNet Fix, Viper4Android (programminghoch10/ViPER4AndroidRepackaged: A refined ViPER4Android installer. (github.com)) and Universal GMS Doze (gloeyisk/universal-gms-doze: Patches Google Play services app and its background processes to be able using battery optimization (github.com)). The phone still works fine and Viper4Android works too. SafetyNet also passes.
Now the problems arise. A few hours later and some reboots later, the phone won't boot anymore (maybe 20 reboots). I didn't even change any settings before the reboots. The boot animation plays and the phone is getting reset by a watchdog maybe. Also cannot use ADB during boot and the safe mode button combination doesn't work. I'm not experienced enough to understand the log files correctly. I already flashed the phone twice and the same problem occurred.
I attached some logs I could get from TWRP, but the main data partition is encrypted.
Full log files are here: logs.zip
Otherwise I'm extremely impressed with Lineage and would love to use it as my daily.
Thanks a lot for helping.
Click to expand...
Click to collapse
If it is an issue with the ROM itself, you will need to post your issue in the ROM thread where you got your ROM and see if there is something in the ROM that the developer of the ROM needs to fix in the ROM itself.
Hi, kinda new to custom ROMs and tried out Lineage and later Crdroid on my Galaxy S10e Exynos.
The OS works fine but after a few restarts the phone randomly bootloops and I can't find any way to fix it.
Currently installed is Crdroid recovery, Crdroid latest (the same problem happens with Lineage) with Android 13, MindTheGapps, Magisk 25.2
Magisk modules are Zygisk, Viper4Android and Universal SafetyNet Fix.
I attached some logs but I'm too inexperienced too read them correctly. It looks like the file
Code:
/data/misc_de/0/apexdata/com.android.permission/runtime-permissions.xml
is corrupted after a few restarts?? The bootlogo just repeats and nothing is happening. The logs say that the zygote process has crashed.
Does anyone know what to do? Thanks a lot!
Logs: log.txt
This used to happen on my Galaxy A50 on another ROM too, and since it's not an S10e problem it's probably a Magisk module