OOS camera keep crashing/freezing - OnePlus 6 Questions & Answers

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.

Related

Does anyone meet the random restart problem?

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:

Black Screen One plus camera

Hi
On latest updates and updated the one plus camera from the below
https://www.apkmirror.com/apk/onepl.../oneplus-camera-3-10-19-android-apk-download/
Phone rooted and using xxxNolimits and Smurf kernel
However when I open it all I get is a black screen??
Anyway of fixing this
Okay removed updates but on version 3.8.114
What's the latest version that works with 7 Pro?
I get the same issue with the new updated camera app 4.0.251.
Phone is not rooted and on factory software.
Earlier when it was on 3.10.19 it was working fine.
Uninstalling updates now.
After uninstalling the update 4.0.251 and reinstalling 3.10.19 now it's working fine.
funkyirishman said:
Hi
On latest updates and updated the one plus camera from the below
https://www.apkmirror.com/apk/onepl.../oneplus-camera-3-10-19-android-apk-download/
Phone rooted and using xxxNolimits and Smurf kernel
However when I open it all I get is a black screen??
Anyway of fixing this
Okay removed updates but on version 3.8.114
What's the latest version that works with 7 Pro?
Click to expand...
Click to collapse
I am facing same issue with my OnePlus 6 any solution sir
red rocket said:
I get the same issue with the new updated camera app 4.0.251.
Phone is not rooted and on factory software.
Earlier when it was on 3.10.19 it was working fine.
Uninstalling updates now.
After uninstalling the update 4.0.251 and reinstalling 3.10.19 now it's working fine.
Click to expand...
Click to collapse
Sometime your method working for 30-40 min then the issue remains same camera show black screen...
I have OnePlus 6
Since past 2 months I am facing this issue. Whenever I open camera. It goes completely black. I am so frustrated with it as my daily usage is from camera....any permanent solution
I updated it via Oxygen Updater app, from Android 9 to 10 and then Android 11.1.1.1. The camera was working completely fine on Android 9/10 but 3-4 days after updating to Android 11.1.1.1., it started crashing. On 6-7th day it completely stopped working on stock Camera app.
Now when I click the Camera app, it opens the Camera with black screen and closes within two seconds. That's it, no response at all. It does not switches to front camera at all. If I select any other Camera Mode (Video/Portrait) on back cam it closes without any response.
I need your help Any solution

New StatiXOS OFFICIAL 4.2 build for Essential PH-1

StatiXOS
Download StatiXOS for free. StatiXOS is a homebrew distribution of Android. StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal and clean, while providing quality of life improvements and up to date security patches. This page is to provide downloads for...
sourceforge.net
4.2 has been release
"Introduce our OTA Updater!"
For those with the Chrome issue of freezing I have a fix that another user in another ROM thread accidentally found!
If you download
PH1-OTA-PQ1A.190105.090.zip
and then reboot into recovery (TWRP, be sure to disable pin on phone before hand and backup everything) then flash the above (I wiped everything first but DON'T wipe internal storage) then I did a second wipe of everything but internal storage and then I flashed 4.2 of StatiXOS and then I flashed TWRP, then I rebooted phone and set it up from new and restored everything from Cloud backup and I can confirm that I no longer have the Chrome freezing issue.
You can thank seungbaekm over in the Evolution-X 5.4 thread for this fix as he is the one that accidentally flashed the older PH-1 factory image and discovered Chrome then worked again! This should fix the issue for all the new Android 11 ROM 's out there for us folks that have the Chrome browser locking issues.
I did not even test the new 4.2 ROM on its own to see if it happens to fix the Chrome issue but I doubt that it does since it is not mentioned in the release notes. Also I have no idea if any of the other original factory images will also fix the issue, I only downloaded the one they he said he accidentally flashed and used it.
Hope this helps everyone with this issue as I know how frustrating it has been. Sure, there is the Bromite/Brave/Firefox work around, and I have been using and enjoying Bromite since 4.1 but I like having things working the way they are supposed to work.
Thanks you very much
I will test
Following this great insight about the fix of the Chromium issue, I only flashed mata PQ1A.190105.090 NOVENDOR firmware from this old thread, without wiping anything of my current StatiXOS 4.2 installation, and after booting Brave is working perfectly.
So, it seems the issue was caused not by the ROM system or vendor, but the mata QQ1A.200105.007 firmware.
As a consequence of flashing this old no system nor vendor firmware, my device baseband was downgraded, but mobile data seems to be working just fine. I guess it's possible to test newer firmware available at the referenced thread, like PQ1A.190105.112, QP1A.190711.107 or QP1A.190711.148, to identify the latest firmware free of the Chromium issue.
More good news: now Netflix is working fine, also.
UPDATE: I tried all the these firmwares and Netflix worked fine only with the Pie ones. So, PQ1A.190105.112 is the more recent mata firmware that I can use on my PH-1 with StatiXOS 4.2 in order to keep Chromium browsers and Netflix working.
aamadorj said:
Following this great insight about the fix of the Chromium issue, I only flashed mata PQ1A.190105.090 NOVENDOR firmware from this old thread, without wiping anything of my current StatiXOS 4.2 installation, and after booting Brave is working perfectly.
So, it seems the issue was caused not by the ROM system or vendor, but the mata QQ1A.200105.007 firmware.
As a consequence of flashing this old no system nor vendor firmware, my device baseband was downgraded, but mobile data seems to be working just fine. I guess it's possible to test newer firmware available at the referenced thread, like PQ1A.190105.112, QP1A.190711.107 or QP1A.190711.148, to identify the latest firmware free of the Chromium issue.
More good news: now Netflix is working fine, also.
UPDATE: I tried all the these firmwares and Netflix worked fine only with the Pie ones. So, PQ1A.190105.112 is the more recent mata firmware that I can use on my PH-1 with StatiXOS 4.2 in order to keep Chromium browsers and Netflix working.
Click to expand...
Click to collapse
This is some great news, thank you and SirDigitalKnight for the research! I haven't tried this fix yet, but I'm planning to when I flash this week if I do run into the chrome freeze problem. You mentioned this downgrades the device baseband version. I'm not too familiar with that, you did say it's working fine so far, but do you think that could cause issues in the future?
Just a question, does StatiXOS have slim recents included?
Mous3kteer said:
This is some great news, thank you and SirDigitalKnight for the research! I haven't tried this fix yet, but I'm planning to when I flash this week if I do run into the chrome freeze problem. You mentioned this downgrades the device baseband version. I'm not too familiar with that, you did say it's working fine so far, but do you think that could cause issues in the future?
Click to expand...
Click to collapse
I have no idea if using a.Pie firmware could have side effects in the future. So far, I haven't seen any.
Using the StatiXOS Telegram support group, I shared the information about the different firmwares to the devs, so I think they'll tell us if something can go wrong in the future.
Is anyone else having issues with sending a text message with this rom?
vineetbhatia said:
Is anyone else having issues with sending a text message with this rom?
Click to expand...
Click to collapse
If you have VoLTE on, turn it off
vineetbhatia said:
Is anyone else having issues with sending a text message with this rom?
Click to expand...
Click to collapse
If you have VoLTE on, turn it off
Double Post
Just reporting that I did a clean install - "Fastboot -w" on the latest working firmware (JAN20 FW, FEB20 Vendor iirc) and I'm very impressed.
Plus replaced the screen, battery, and buttons cable and now the phone is "essentially" new. Parts are actually quite cheap.
Chrome is working without issues.
360 Camera is working without issues
Haven't tried sending SMS with VoLTE On yet.
Amazing that we still a maintainer.
chanh2018 said:
If you have VoLTE on, turn it off
Click to expand...
Click to collapse
Yup, that worked. Thanks mate..
The March 10th update they pushed out through the OTA updater worked perfectly. It is nice to see we still have good support on this great phone.
SirDigitalKnight said:
For those with the Chrome issue of freezing I have a fix that another user in another ROM thread accidentally found!
Click to expand...
Click to collapse
Thank you for this! And also thanks to @aamadorj for the further investigation!
It's too much of a hassle for me to do this fix right now, and I admit I have adapted to using Bromite and Firefox, but I'll definitely keep this in mind for some other time when I feel more like it... BTW, I did check, and Chrome stil freezes on the latest 4.2 update, no surprise here.
This ROM has been working great for me, very stable, no issues, and the updates are a breeze, especially with the latest OTA updater.
kt-Froggy said:
Thank you for this! And also thanks to @aamadorj for the further investigation!
It's too much of a hassle for me to do this fix right now, and I admit I have adapted to using Bromite and Firefox, but I'll definitely keep this in mind for some other time when I feel more like it... BTW, I did check, and Chrome stil freezes on the latest 4.2 update, no surprise here.
This ROM has been working great for me, very stable, no issues, and the updates are a breeze, especially with the latest OTA updater.
Click to expand...
Click to collapse
You should be able to flash the older Pie firmware without wiping from what I have read but I have not tried that yet. I might try it with the very latest firmware of Pie, PQ1A.190105.112 and see if it screws anything up without wiping the phone. Anyway I always to a backup of the phone to the cloud and also of Whatsapp before I start messing around just in case I have to wipe and so far all my restores have worked perfectly, but yes it is a pain to have to setup wifi's and add back in BT devices and setup security and any double authentication apps you use. Getting used to it now though.
SirDigitalKnight said:
You should be able to flash the older Pie firmware without wiping from what I have read but I have not tried that yet. I might try it with the very latest firmware of Pie, PQ1A.190105.112 and see if it screws anything up without wiping the phone. Anyway I always to a backup of the phone to the cloud and also of Whatsapp before I start messing around just in case I have to wipe and so far all my restores have worked perfectly, but yes it is a pain to have to setup wifi's and add back in BT devices and setup security and any double authentication apps you use. Getting used to it now though.
Click to expand...
Click to collapse
Flashing the contents of the attached files using fastboot should make your device to use last firmware for Android Pie, without losing your current ROM installation.
aamadorj said:
Flashing the contents of the attached files using fastboot should make your device to use last firmware for Android Pie, without losing your current ROM installation.
Click to expand...
Click to collapse
OK, here is my update... Noting your comment in the other post about the downgraded baseband, I decided to exclude the modem from flashing. Flashed everything else from PQ1A.190105.112-NOVENDOR via fastboot, rebooted, and... Chrome froze again. Ugh... :\ OK. I went back to fastboot and flashed the modem - this time after the reboot the problem was fixed.
So, I'd say it's safe to conclude that the modem (baseband) is the actual component that was screwing up the Chromium-based browsers. Go figure...
This ROM is great on the PH-1. At the moment I can't get the LED to blink when notifications arrive. The setting is toggled on.
I've installed magisk, nanodroid and microg (not tried that sort of thing before!). Could that have anything to do with it?
chrisrg said:
This ROM is great on the PH-1. At the moment I can't get the LED to blink when notifications arrive. The setting is toggled on.
I've installed magisk, nanodroid and microg (not tried that sort of thing before!). Could that have anything to do with it?
Click to expand...
Click to collapse
Even with stock rom LED is not blink if you're using stock messages, try Textra and see if it works for you.

Cannot update OOS

Hi everyone, this is my first post here on XDA but i'm a very looong passionate of this forum.
Recently my loved one plus 7 pro has experience some weird mic issues so I changed the motherboard and this resolved every problem.
But now I'm experience some really strange software issues, I'm able to flash the stock OOS but I can't upgrade OOS, I always get a "signature verification failed" or when I'm able to pass the verification (by downloading many times the update) the update fails, only once I was able to update. The firmware, flashed with msmdownloadtool, works fine. The problem is that often many app crash and the ui reboots randomly. I've also tried to install pixelexperience ROM but it's the same with the apps, the continue to crash, I always clean flash everything.
Do you have any idea why app continues to crash?

[S10e, Lineage 20.0] Bootlooping after a few hours of usage

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

Categories

Resources