Develop Bugs

Random reboot?

So, I've had the premium for almost 3 weeks now. On the second day it crashed whilst I was listening to music +browsing in chrome. Thr screen turned inky and then turned off. Since then I haven't had anything similar happen, but I have had 1 or 2 reboots. Are these signs something could be wrong with my phone? I have like a week to get a replacement. It's rev 2, other than this I have no complaints.

Try to remove cach in recovery mode, maybe that will fix your problem. If not let me know

This has been happening to me as well and actually results in boot loops. Since I have Liveboot, I can see the dmesg output. It says "Failed to start system services. Invalid abi: ABI" or something like that. I'm RomAur so maybe that has something to do with it?

It has happened to me 3 times this week. Also RomAur 1.1. It seems to happen when i am heavy multitasking, definitely related to chrome I think.

I'm completely stock... I use chrome as my main browser. The last time it happened it froze on wake whilst it was charging... The first time I was listening to music and doing something else which I can't recall. The phone has 3gb of ram so I don't really clear my recent apps as often as I did on my S4. It happens once a week on average for me. Cache wipe didn't do anything.

You could've easily gotten a faulty device. A but load of hardware issues can do that and I would advice you to do a factory reset, update to the latest F/W (flash it if not available in ur region), see if it happens again and if it does - get a replacement
Gd luck

If you're totally stock this might not help but I narrowed my problem down to xposed being unstable as crap on mine at least. Hasn't happened since I went back to stock fw (using. 200 generic FR). But I tried to install xposed and I got the three light reboot immediately.

TheImmutable said:
If you're totally stock this might not help but I narrowed my problem down to xposed being unstable as crap on mine at least. Hasn't happened since I went back to stock fw (using. 200 generic FR). But I tried to install xposed and I got the three light reboot immediately.
Click to expand...
Click to collapse
exactly like that on my z5 . when i flash the xposed uninstaller , it doesnt randomly reboot, but when i flash xposed , it does.i was thinking of flashing .200 ftf and then flashing xposed from the beggining (before i install any apps ) to see if it helps , but you said you did it??

Upgraded to Oreo yesterday, rebooting randomly...

As the title says, phone has randomly rebooted
... twice in the last few minutes, both times I had picture in picture going while sending a text...has anyone else experienced this? Also, the boot time is amazingly fast at least!
Chris

cswee1932 said:
As the title says, phone has randomly rebooted
... twice in the last few minutes, both times I had picture in picture going while sending a text...has anyone else experienced this? Also, the boot time is amazingly fast at least!
Chris
Click to expand...
Click to collapse
Did you do a wipe when you flashed or just update? If you just did an update, I would try to reinstall and let it wipe the device.

Yup. I'm experiencing this as well. Happened to me twice yesterday. Maybe try a factory reset?
Sent from my Pixel XL using Tapatalk

Having the same issue did a complete factory install with the stock image.
Then rooted not sure if that is causing my issues but, is anyone else stock not rooted having random reboots?

I've had 3 reboots since jumping on Oreo. Did my update the clean way through a factory reset and flashing a factory image. Stock, unrooted.

humdrum2009 said:
Having the same issue did a complete factory install with the stock image.
Then rooted not sure if that is causing my issues but, is anyone else stock not rooted having random reboots?
Click to expand...
Click to collapse
Stock, updated via ota... Having 5 to 6 reboots per hour. Google is sending a replacement phone.

Maybe you have to do a factory reset.

Reason why i havent upgraded. Still on a rock solid nougat until google fix all this problems. Maybe 8.1 or so. Seem like reboot is a common problem with the pixel,. All thread about orea theres someone talking about his reboot problem in many different sites.

jerryhou85 said:
Maybe you have to do a factory reset.
Click to expand...
Click to collapse
Did that too. It is even rebooting in safe mode after a factory reset Hence the return...

sandibhatt said:
Did that too. It is even rebooting in safe mode after a factory reset Hence the return...
Click to expand...
Click to collapse
That sounds much like a hardware failure... :crying:

I had random reboots too coming from DP4 to FInal. No more random reboots since I flashed the factory images

Is 8.0 the version that is the start of the new OS updating system? I wonder if the partitioning is getting all screwed up? I think I'll stay on 7.1.2 for a bit longer till this gets ironed out.
Sent from my Pixel XL using Tapatalk

Stock, bootloader unlocked, Oreo by OTA, and 1 random reboot and 1 random power off
Sent from my sailfish using XDA Labs

Not gonna upgrade to Oreo.
Is there such a way?

nabbed said:
Not gonna upgrade to Oreo.
Is there such a way?
Click to expand...
Click to collapse
Just don't download the OTA till they send out a patch. That's what I'm doing.
Sent from my Pixel XL using Tapatalk

when i first updated to oreo and rooted it, i ran into the rebooting issues some of you are experiencing. i think the root of my issue was busybox. i did a clean install of oreo again the other day and rooted, but didnt put busybox on the phone. phone ran fine for a day, so i tried giving busybox another go. the reboot issues came back. hope this helps

Mine only reboots randomly if I have YouTube picture in picture enabled once I disabled it I haven't had any reboots maybe try to disable that

Just did the update a couple hours ago and so far so good. Picture in picture works too. Stock, GPE on VZW, no root or anything.
Sent from my Pixel XL using Tapatalk

Guys, anyone still getting random on persistent reboots on Oreo with Pixel (XL)? I'm doing my second factory reset atm and monitoring these two threads on buganiser - 1, 2. Basically people started getting reboots after upgrading to Oreo and one notable common thing is: 'Sense Key : Hardware Error [current]' which Google reps assigned to the threads read as hardware issue (probably with Toshiba's memory chips being prone to overflow/overload (?)). They haven't answered my question why is it only happening on Oreo though. I REALLY don't want to go through the warranty process again only to get a device with the same problem as I still believe it can be fixed in 8.1. Is there anyone who had similar issues that got fixed with the 8.1 Beta? Cheers!

I'm experiencing the random reboots too.
Oct. 8.0, Magisk, Root
I almost missed an alarm due to this, so I think I may go back to Nougat. Not only does it reboot, but it gets stuck in the boot screen. If I hold Power and reboot, it comes up though.

Touch screen on 5T randomly stops responding

I've been having this issue where the touchscreen on my OP 5T will be working just fine but the next second just turn unresponsive to any touch, and no amount of rebooting fixes it.
So far, I've tried using the unbricking tool and restored it to OOS 5.1.3, wiped everything off the phone and tried the latest OOS 9.0.1, and even some custom ROMs like Pixel Experience, both the official Oreo version and some unofficial Pie versions.
I even tried installing custom kernels like the blu-spark kernel and the π kernel.
But here's the thing, all of these work right after making the change but the touchscreen stops working a day later. I'm still on the fence if this is a hardware or a software issue, because (do please correct me if I am wrong) a hardware issue would be if it was totally unresponsive and not work fine after installing a new ROM/kernel, which is not the case here, leading me to assume it has to be something in the software related?

gasburger said:
I've been having this issue where the touchscreen on my OP 5T will be working just fine but the next second just turn unresponsive to any touch, and no amount of rebooting fixes it.
So far, I've tried using the unbricking tool and restored it to OOS 5.1.3, wiped everything off the phone and tried the latest OOS 9.0.1, and even some custom ROMs like Pixel Experience, both the official Oreo version and some unofficial Pie versions.
I even tried installing custom kernels like the blu-spark kernel and the π kernel.
But here's the thing, all of these work right after making the change but the touchscreen stops working a day later. I'm still on the fence if this is a hardware or a software issue, because (do please correct me if I am wrong) a hardware issue would be if it was totally unresponsive and not work fine after installing a new ROM/kernel, which is not the case here, leading me to assume it has to be something in the software related?
Click to expand...
Click to collapse
Same problem. Did you solve this problem?

Has anyone found a permanent solution to this? Or at least a reason? My op 5t also stops responding randomly to the touch. This is really bad.

I also have this problem as well. It seems that many users have this issue. OnePlus should take a close look at it

I have been having this issue for more than 6 months. The problem came after one update during android Oreo if not mistaken (Which update i can't remember)
For my phone, the screen will be unresponsive during the below occasions:
1. After rebooting the phone, touchscreen is unresponsive for up to a minute
2. When browsing pictures in gallery
3. When taking picture using portrait mode
4. When google play is updating apps
5. When google photo is backing up photos.
I am also doubting if is a hardware or software issue, because it only happened in some occasion previously for my case. Tried wipe and install stable/open beta a few times, same thing.
After the latest open beta update, it got even worst, other than the above occasions, the screen start to stop working randomly (be it watching a youtube video or using chrome), its getting annoying as i need to restart my phone a few times a day.
I saw alot of people having this issue, but has yet to raise concern of OnePlus.

I've recently had the same problem, I was still running Lineage 15.1 and had not updated my firmware in months because the official builds switched to 16, then suddenly 2 weeks ago the touch screen stops responding while I was actually using it. Reboots didn't help, clearing cache and flashing lineage didn't help. In the end I somehow got it to work again by flashing the last open beta - but even then it didn't work right after flashing it, I had to leave it over night then it mysteriously started responding again in the morning.
I've just had it happen again and I have tried removing the screen protector and completely discharging the battery as some people on the oneplus forum have reported this helps, but it did not work for me. I really can't be bothered going through the whole process of re-flashing open beta then flashing back to lineage and installing all my apps an restoring my data again, but the only other option at this point is to try take it apart to check the screen is still connected to the motherboard properly....

solution
I also faced this problem, then i tried to degrade it to android oreo, and somehow i never faced touch issue, i think this is a bug in android pie,

karyy said:
I also faced this problem, then i tried to degrade it to android oreo, and somehow i never faced touch issue, i think this is a bug in android pie,
Click to expand...
Click to collapse
I'm not sure about that, the first time I had the issue appear I was still running oreo, as I mentioned, I hadn't updated anything in months due to the lineage nightlies switching to Pie.... That said, certainly seems like most people who have reported it mentioned upgrading to Pie

Facing same issue..
I have a similar issue too..
It started several months ago, when the screen used to randomly stop working, a quick hard reboot usually solved the issue.
But about a month ago, the screen stopped responding altogether and any amount of reboot did not work. So too the device to Oneplus service, there they flashed it to 9.0.7, and the screen started working again, and continued working for a few more hours, until it stopped responding again.
Tried flashing several times using the unbricking tool, but all efforts in vain.
Finally after a month or so, I bought a new phone, and today I just wanted to see if anything has changed on OP5T, and to my surprise, the touch screen started working again.
So this time I enabled USB Debugging, permanently enabled OTG, so that even if the screen stops working, I can use an external keyboard/mouse.
But OP5T is no longer my primary device, and hence I have moved on to a different manufacturer, as I saw absolutely no point in buying another Oneplus and god knows what will happen a year down the line...

Has anyone found a solution to this? I am facing the same problem with my oneplus 5T.

chandle-stick said:
Has anyone found a solution to this? I am facing the same problem with my oneplus 5T.
Click to expand...
Click to collapse
I had the problem. Had to send it back to OnePlus. They replaced the cpu under warrenty. Call 0neplus.

i have this problem on LineageOS 16, in stock is good

k-ninja said:
I'm not sure about that, the first time I had the issue appear I was still running oreo, as I mentioned, I hadn't updated anything in months due to the lineage nightlies switching to Pie.... That said, certainly seems like most people who have reported it mentioned upgrading to Pie
Click to expand...
Click to collapse
I was just searching this issue online. I'm currently facing it as well.
Rebooting the phone makes it go away. I face this issue while charging the phone via official dash charger.
I'm running stock Oxygen OS 5.1.7 running Oreo 8.1.0. I faced this issue 6-8 months ago as well. I cleared 7gb free space in my phone then it started working fine then. My device is 64GB variant. I never updated to Android Pie.
This is a major problem in OnePlus 5 and 5t. I've seen many posts on both XDA and official oneplus forums but found no guaranteed solution so far. I was thinking of flashing custom kernel but then saw here that people are still facing this issue in custom ROMs.

I thought I had solved the problem by installing the RenderZenith kernel, which someone on the oneplus forums recommended in the thread there dealing with this issue... but it has resurfaced after a couple of months without issue. Rebooting does not fix the issue for me, I have to flash a stock firmware, and sometimes reboot a few times, before the touchscreen starts working again. I tried installing CarbonROM instead of Lineage to see if that made a difference but it lasted about a day before the problem reoccurred. I am now going to try a Q-based ROM (probably Carbon) to see if that makes any difference, but I am not hopeful. I have even had the issue occur once while I was still running stock 9.0.9 and had not yet got to reflashing a custom ROM, had to do a full wipe and reinstall the stock ROM again to get it working.
I'm about ready to throw this phone in the bin and buy something new - only problem is I don't know what. Certainly not going to waste money on another oneplus after this debacle but there aren't many other options that are good for custom ROMs. Too bad OOS is such insecure trash and Oneplus as a company cant be trusted, otherwise I might at least see how I go running stock for a while.

k-ninja said:
I thought I had solved the problem by installing the RenderZenith kernel, which someone on the oneplus forums recommended in the thread there dealing with this issue... but it has resurfaced after a couple of months without issue. Rebooting does not fix the issue for me, I have to flash a stock firmware, and sometimes reboot a few times, before the touchscreen starts working again. I tried installing CarbonROM instead of Lineage to see if that made a difference but it lasted about a day before the problem reoccurred. I am now going to try a Q-based ROM (probably Carbon) to see if that makes any difference, but I am not hopeful. I have even had the issue occur once while I was still running stock 9.0.9 and had not yet got to reflashing a custom ROM, had to do a full wipe and reinstall the stock ROM again to get it working.
I'm about ready to throw this phone in the bin and buy something new - only problem is I don't know what. Certainly not going to waste money on another oneplus after this debacle but there aren't many other options that are good for custom ROMs. Too bad OOS is such insecure trash and Oneplus as a company cant be trusted, otherwise I might at least see how I go running stock for a while.
Click to expand...
Click to collapse
Have you tried Affinity kernel? Saw a post here. But it is for OnePlus 5
https://forum.xda-developers.com/showpost.php?p=79256461&postcount=95

archz2 said:
Have you tried Affinity kernel? Saw a post here. But it is for OnePlus 5
https://forum.xda-developers.com/showpost.php?p=79256461&postcount=95
Click to expand...
Click to collapse
No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....

k-ninja said:
No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....
Click to expand...
Click to collapse
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
---------- Post added at 08:23 PM ---------- Previous post was at 07:57 PM ----------
k-ninja said:
No I haven't.... but I am losing faith by the minute here.... screen now stops responding even in TWRP or on a fresh install of the stock OS..... I'd say it's hardware related but seems weird that reverting to stock fixes it... sort of....
Click to expand...
Click to collapse
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk

archz2 said:
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
---------- Post added at 08:23 PM ---------- Previous post was at 07:57 PM ----------
Okay. So you're currently running stock ROM version 9.0.9?
Another query, did this problem occur on your phone in stock Oxygen OS v5.1.7 with Oreo 8.1. 0?
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
I'm not running OOS now, but I have had the issue occur while I was. I am just re-flashing OOS to get the touchscreen to work again, but actually I can't even get the setup wizard to work once the phone boots (hangs on the "just a sec" screen), so I am usually flashing another custom ROM once the screen works again. I managed to get to about 6 hours of normal usage last night before the screen stopped responding again - after fighting with the phone all day and most times not getting much past installing magisk modules.
I am starting to think the problem is related to either Magisk, or the riru kernel hooking modules necessary for Xprivacylua (which is mandatory to install IMO) - I had been using the YAHFA module mostly but yesterday I tried Sandhook to see if it made any difference - that was when I managed to get to 6 hours instead of 30 minutes, but it was also when I went back to Magisk 19.3 instead of installing 20.2. Now that I think back, I am wondering if it was upgrading Magisk from 19.x to 20.x that made the issue resurface after a couple of months without it.... Can't remember for certain, but it seems like the most plausible explanation. I tried flashing Magisk uninstaller this time when the screen stopped, but it didn't help - only reflashing back to stock works (sometimes it even takes a few goes). Whatever the problem is, it seems like it is tripping some hardware related switch which only gets reset when installing stock FW.
the other thought I had was that perhaps the hooking framework is getting in the way - like it intercepts the screen touches before they are processed, but it bugs out for some reason and they never get passed on to the OS. I don't know enough about how it works honestly, or any idea how to go about debugging such a weird problem, so no way to look into it.
Anyway, to answer you other question - I never had the problem with OOS 5.1.7, I have never run stock OOS on my phone, but the first time I had the problem was with Lineage 15.1 Oreo 8.1.0. I can't remember if at that time I was running stock xposed or edxposed.
I'm close to my wits end here. IF the problem turns out to be magisk related, it's pretty much new phone time - I doubt even if I logged a bug report it will get looked at any time soon much less resovled, and I simply refuse to run an android phone without xprivacylua.

k-ninja said:
Anyway, to answer you other question - I never had the problem with OOS 5.1.7, I have never run stock OOS on my phone, but the first time I had the problem was with Lineage 15.1 Oreo 8.1.0. I can't remember if at that time I was running stock xposed or edxposed.
Click to expand...
Click to collapse
Edexposed is for Pie ROMS as there's been no development for Pie from official developer for xposed. Chances are you were running xposed only on Oreo 8.1.0.
Today I flashed Franco Kernel on my phone, been running smooth so far. I used to get non-responsiveness while dash charging specifically. Let's see how it goes. Will keep you updated.

Bugger it... I managed to get to 4 days or so after flashing back to LOS 16.1 / Magisk 19.3 / Edxposed YAFHA / Franco kernel, but it has just crapped out on me again.
This time I has tried a slowly-slowly approach, at first running just the stock OS and apps for a few hours, then gradually started installing magisk, riru, edexposed, then finally xprivacylua - Didn't have any problems up to there. Then I installed pico gapps, and used the Play store to do a fresh install of Mobius Final Fantasy instead of restoring from Titanium backup (this game is actually the only real reason I need gapps at all :-/). Mobius is a PITA because its like a 5Gb download, so it takes a long time to reinstall rather than restore from TB. Anyway it seemed like it was working ok for a few days after the fresh install but I just picked up the phone as couldn't unlock it. I have noticed that often the problem does occur while I am playing the game and I have wondered if there is something about it which makes it more likely to trigger, but it can't be the only thing as it happens even during the setup wizard sometimes.... bloody infuriating.
Anyway... not sure what to do now. Really CBF going through the back-to-stock dance again. Meh.

Question Freezes and crashes with custom ROMs

Hey,
I have some minor and major lag issues (freezes and crashes), sometimes I even have to force restart the phone.
It happens with most of the customs ROMs that I have tried (HavocOS, ShapeshiftOS, Pixel Extended, etc.) but not every ROM (the only ones where it doesn't occur are ArrowOS and xiaomi.eu I think)
Even after flashing multiple times (mi flash + Clean flash), it happens with multiple apps, so I don't think it's apps related (maybe magisk or TWRP), and not ROM too.
Is anyone facing those issues, or is there any solution or thing that I can do to solve this problem.
Also, I'm having issues collecting logs because it is happening randomly and when it happens the log app I use crashes, but it is always the same issue (ANR Input dispatching timed out (...))
I have one set of logs where I got freeze (5-10 seconds) multiples times, I will attach the file.
I can provide anything to help solve this annoying problem.
Thanks in advance

faced that problem too with app Greenify (xiaomi.eu rom + Twrp Alpha +Magisk 23)

Still a pain to have to deal with that, is anyone here ready to help ?

CRNO said:
faced that problem too with app Greenify (xiaomi.eu rom + Twrp Alpha +Magisk 23)
Click to expand...
Click to collapse
Don't use it. That and Hyperion were on my stock Note 10+ that got boot looped twice, back to back, grrrrrr. Removed both on the 3rd load and still running that load over a year latter.
When you're seeing that kind of behavior you're just one reboot away from a boot loop

Havoc os was the only ROM with freeze's after the phone went in sleep mode, apps like YouTube freezing then. But on the other roms I didn't had that and i tested everyone on havoc I have installed the ROM 2 times with different firmwares but always a freezing of apps after deep sleep

r3sp said:
Havoc os was the only ROM with freeze's after the phone went in sleep mode, apps like YouTube freezing then. But on the other roms I didn't had that and i tested everyone on havoc I have installed the ROM 2 times with different firmwares but always a freezing of apps after deep sleep
Click to expand...
Click to collapse
Too bad I have to install others ROMs, I much prefer Havoc. But weird that it also appears with other ROMs

I have been having similar issues. I'm from the US and it happens often when I am using mobile data.

Shmi117 said:
I have been having similar issues. I'm from the US and it happens often when I am using mobile data.
Click to expand...
Click to collapse
+1 same here
All pixel based custom roms crash while I'm on mobile data. I think it's a modem issue.

NonoBow85 said:
Too bad I have to install others ROMs, I much prefer Havoc. But weird that it also appears with other ROMs
Click to expand...
Click to collapse
I have been using havoc latest build for close to 2 weeks. I didnt encounter any freeze though

aravreddy2231 said:
+1 same here
All pixel based custom roms crash while I'm on mobile data. I think it's a modem issue.
Click to expand...
Click to collapse
Same here in BC. I have found it seems to happen with LTE with ArrowOS (I haven't tried any other custom ROMs). I haven't had the problem occur at all on H+.

If you are rooted, check /sys/fs/pstore/console-ramoops, or dump logcat/bugreport if you aren't rooted, and search for "crash". On my device, it says that my modem crashes which causes every CPU core to stop and reboot.

Shmi117 said:
If you are rooted, check /sys/fs/pstore/console-ramoops, or dump logcat/bugreport if you aren't rooted, and search for "crash". On my device, it says that my modem crashes which causes every CPU core to stop and reboot.
Click to expand...
Click to collapse
I will try that later, thanks

I got that if it can helps

After some research, I think the problem is caused by @manuelbianco tree for alioth, that is widely used and correspond to which ROMs I have problem with.
Still doing some research on how to solve this because it removes ROMs that would like to use.
If anyone knows anything, I would like to hear it.

NonoBow85 said:
After some research, I think the problem is caused by @manuelbianco tree for alioth, that is widely used and correspond to which ROMs I have problem with.
Still doing some research on how to solve this because it removes ROMs that would like to use.
If anyone knows anything, I would like to hear it.
Click to expand...
Click to collapse
yes. That tree has some instabilities. Unfortunately most alioth developers are using that tree. You can try hentaios and arrowos. They are not using that tree

kmykoh said:
yes. That tree has some instabilities. Unfortunately most alioth developers are using that tree. You can try hentaios and arrowos. They are not using that tree
Click to expand...
Click to collapse
Yes I know, but I in my opinion there are not the best, hope it will be fixed soon enough.

i think i finally found a solution, if you have magisk installed, i reccomend uninstalling it and giving up root, because i did it and the freezing stopped, maybe trying an older model or just giving up magisk overall will stop the freezing, but i did remove magisk and the freezing stopped, completely. also, remove any custom kernels to prevent more freezes and other shenanigans from happening, cheers.

I am facing the same issue for a long time now. Others with same device(Poco X3) didn't have any problem, it's just me and it sucks!!!

himanshu1081 said:
I am facing the same issue for a long time now. Others with same device(Poco X3) didn't have any problem, it's just me and it sucks!!!
Click to expand...
Click to collapse
This section is for Poco F3.

Question Soft Reboots After Every Reboot [SOLVED]

EDIT: Apparently this was a result of using the wrong setting for enabling hotspot in PropsConfig. Because all that stuff was set during bootup, deleting apps wouldn't change the situation. Setting worked fine on my Pixel XL, but not here. Changed the setting and all is well.
--------------------------
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.

Might be quicker and easier to back up your required files and just factory reset.

Texan1 said:
Might be quicker and easier to back up your required files and just factory reset.
Click to expand...
Click to collapse
*sigh* I kinda made this post to avoid that step.

somethingsomethingroot said:
*sigh* I kinda made this post to avoid that step.
Click to expand...
Click to collapse
I know, it's just that it sounds like you've already disabled some things that could be causing it, which hasn't helped. If it was me, with something like constant reboots, I'd want to start fresh just to make sure they are eliminated for good

somethingsomethingroot said:
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Click to expand...
Click to collapse
I've seen reports of "random" (=not intentional) reboots after
+ booting up the phone
+ using the FP scanner
+ making videos or shooting photo
+ doing a firmware update (I've seen both reports of ppl that "officially" OTAed & used manual flashing)
+ doing nothing
+ doing something
Some were able to fix their issues by factory resetting, some needed replacement devices. Some reported that even after a factory reset, the issue still persisted, but they were able to fix it by NOT using a backup via cable, some reported that even the Google Drive backup "corrupted" their phone (fix after setting up everything by hand from scratch). Some even reported their issues to get fixed via a software update.
So it seems to be connected to hardware (= replacement device) and/or software simultaneously (=fix via reset).
Strange this is since there are also numerous reports of Samsung owners that upgraded to A12 about random reboots. So it might even be something Android 12 related, or it's just Samsung also implementing similar bugs without it being A12 related (unlikely, since the reports seem to be centered around people using the new A12 update).
I also had the random reboot problem (~ 6 times a day, when doing nothing, it just rebooted when the phone layed on the table in idle). I wasn't able to fix it via a reset, so I got a replacement device.
I also have the "random" reboot problem on my Pixel 3 since upgrading to Android 12 (never had any issues all the years I've been using that phone), so that issue is clearly caused by A12, but I haven't troubleshot it/ tried to solve it, since I don't actively use the phone currently.
Aside from trying a factory reset and minding the backup issue (especially backups that you got from phones that did NOT have Android 12), there is not much more that you can do (ofc you could also use the Pixel repair/android flash tool to do a "clean" install of Android on your phone). Next step would be to contact Google.