Related
Does anyone know what this is, Or why it happens. my phone would crash and this screen would pop up. I did alot on my phone before it started to happen. I think it has something to do with GPS, but the only other people I have seen on the net to have this problem have different stories.
One says its after he rooted
Another person on the T-mobile forums reported it but didn't give a suspected reason.
Mine did it after three things happened I used the supl.google.com gps fix, and my battery showed an overheat warning when charging turned off. And My girl tried to send 15 pics she took to herself and cousin one through E-mail and the other through mms. The email and text messages to my girl gave me error messages that and a way to solve the problem (which didn't work) The only thing that worked was deleted her thread and the email.
I have since restored factory setting to see if it fixes the problems. I'll keep everyone updated.
If anyone has any ideas or has had this happen chime in maybe we can find out whats going on.
Factory Data reset was useless, it was a waste of time. It appears to be related to the GPS. After thinking about it, the radio probably burned out when i was trying to use gps while charging it in the car yesterday, it had to be 94 degrees outside probably hotter on the dash. The phone actually reset to the battery indicator and flashed a battery heat warning. Gps didn't last last long after that. It was the next morning when I started to get the error.
Called rep, and he gave me an exchange right away, no questions, will be getting another phone sat. or monday.
I realize this is a little old, but I just wanted to say that I just had the same problem today while I was using a navigation tool (Waze). I thought it might be related to the app, but maybe it is the GPS as op said.
I do realize this thread is months old but, likewise, I just had the same thing happen to me.
I wasn't using GPS though, I was simply trying to tether through usb.
Next thing I know the "kernel panic, upload mode" screen came up rendering my phone useless
I pulled the battery restarted, and did the same thing yet this time the screen didn't come up allowing me to tether and search the issue.
From the google search results I came across a thread where a guy said it had something to do with task managers/killers. He said since he unistalled the version he was using "advanced task manager" he never had the problem again.
which led him to believe it came from the wrong proccesses being killed or stopped by it which caused the kernel to crash.
Likewise...I too was using a task killer--Auto killer. So I uninstalled it as well, and now use the system default task manager to kill unwanted apps manually.
So far so good...Idk if this is the solution, but to any future readers that run across this and are having the same problem, I suggest you rid of any task killing apps that may be running. Manually kill apps on your own, and let android handle the rest.
I'm not saying dont use them at all but...unless you are an advanced enough user to understand how they work a little more, your best benefit is to leave it be.
Here are some tips that helped me fix this issue:
1. As someone said earlier, uninstall task killers. It's better to install an app that changes the os default task killer. I use autokiller and I use the preset optimum. This way the os can manage the processes and it will stay stable.
2. If you have setcpu, make sure to go to menu, autodetect device, and then set the minimum to 200.
3. If you flash a rom, if it's possible use a clockwork recovery image instead of using Odin.
After these steps, it never happened to me again.
crazy25000 said:
Here are some tips that helped me fix this issue:
1. As someone said earlier, uninstall task killers. It's better to install an app that changes the os default task killer. I use autokiller and I use the preset optimum. This way the os can manage the processes and it will stay stable.
2. If you have setcpu, make sure to go to menu, autodetect device, and then set the minimum to 200.
3. If you flash a rom, if it's possible use a clockwork recovery image instead of using Odin.
After these steps, it never happened to me again.
Click to expand...
Click to collapse
I was using Autokiller too....I uninstalled it and everything seems fine, Idk, may had nothing to do with it...because I've used Autokiller for quite a while, way back on my G1 and never had that problem, oh well...appreciate your input.
I had several "kernel panic" warnings on my handset which I replaced. If I remember it was after using Google maps right after an update and it was hot as a ***** and could smell components melting. As far as autokiller the experience I had was that say I was online Google reader decided to check XDA for instance,go back to Steel would have closed the App out.this happened using visual task swithcher and the default last used programs panel. So I don't use it for that reason.
if your phone is Loki, use Odin, you'll be Thor.
Thread moved to Q&A.
I think this is related to some applications. This is happening to me also, I am on Stock 2.2 Rooted. First I noticed this one when I was online on Nimbuzz and my yahoo account was logged in through nimbuzz, and when I started Yahoo messenger with the same login ID I got "USER FAULT NOT KERNEL PANIC". It happened with same scenario again & again. So I dont use both together.
Again I noticed when I kept my phone on charging through USB connected to a PC, sometimes my fon went in the same Panic mode without doing anthing.
Somebody needs to find out why this is happening. some application or process is causing this problem which needs to be find out.
Vibrant Crash Response
I have the same problem! It's happened about 20 times to my phone. It crashes, gets hot as ****, and gives me the 'user fault kernel panic upload mode' screen.
I think I've narrowed it down a little though.
Things I've noticed:
1.. It only happens when the phone is charging, never on battery.
2.. It only happens after the screen is turned off, never while I'm using it (anywhere from 5 min to hours after the screen has been off).
I'm guessing its some kind of background process that uses a lot of processing power and overheats the phone..
Hope this helps. Be sure to post up if you find a solution.. I don't want to burn it up!
Just for confirmation sake are we all seeing the same Kernel Fault error? are you seeing the same codes?
RST_STAT 0X4
PMIC_IRQ1 0x0
PMIC_IRQ2 0x0
PMIC_IRQ3 0x0
PMIC_IRQ4 0x0
PMIC_STATUS1 0x0
PMIC_STATUS2 0x0
Also i have tried three different Kernels so i am pretty sure this is going to be a hardware issue.
I may be wrong though, in my case it could be a task killer.
Need help! What can we do?
My cousin had the same problem but, It did happenned on battery power, he did not activated the GPS or Google Map.
The phone is practically bricked. It does not boot to android. We tried everything and came up with no results. Even we get the battery off and waited like a minute or so, plug it back and try to turn it on and it just got us to the same screen with the message saying something about kernel panic upload mode and a bunch of red numbers at the upper left corner. He does not installed any task killer either.
I think he was trying to install a .zip file from the SD Card in clockwork recovery mode. Now we can't even get to recovery mode!
What can we do?
hardware problem
I have been running on I997UCKI4 rom. Now a days the phone suddenly keeps getting into "user fault kernel panic upload mode" and phone would not even go into 3e recovery mode.
I have to take out the battery and put it back again. It keeps heating up until I do that.
Please help.
My original vibrant had this error...
turns out was bad hardware, replaced phone and havent had the problem since.[lots of other problems but not this one]
good luck
i have some issue too
anyone can resolve it?
i get this when i reload new ROM for my galaxy tab..
always shown "KERNEL PANIC RELOAD MDOE"
please help
Same problem
Mine too. What should I do?
I was flashing to stock firmware. Then this error appeared. and i couldn't restore because it doesn't even boot.
PLease help asap. It was my birthday gift.
its nothing to do with GPS.
Jnt
My samsung infuse 4g keeps turning itself off. If I take the battery out then put it back, the phone starts working eventually shuts down again.and gives message user fault not kernal panic upload mode And phone going heat also. Plz tell solution
do anyone find any solution please?
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
GTMoraes said:
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
Click to expand...
Click to collapse
Try flashing another ROM for S3 and doing a full wipe.
TenKoX said:
Try flashing another ROM for S3 and doing a full wipe.
Click to expand...
Click to collapse
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
GTMoraes said:
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
Click to expand...
Click to collapse
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
TenKoX said:
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
Click to expand...
Click to collapse
Thanks for the reply.
I started doing this the first time, but it still crashes it. And as I was wasting too much time with this, the backup option came as a option to not have to click to download over 200 apps one by one. Also, it once happened during a long holiday, and I was in a friend's ranch with no decent internet connection for downloading. All my apps were gone and I was stuck with a default phone for five days.
The backup is exactly the point where I finish downloading all the apps and they're installed. There are no cracked programs or adapted (e.g. Nexus camera). Every single app is obtainable from Play Store, so it's pretty fresh
Funny (actually sad) thing is that it's a system-wide error that a wipe solves it. If I don't wipe data and reinstall the same ROM (which under normal condition is no big deal), it doesn't get past from boot screen.
The worst is it happens instantly. It's working now, but then it crashes. Bam, gone. Few hours ago I was texting my gf and I left the phone for a while, waiting for her answer. After some time I knew something was off, picked up the phone and it was pretty warm (first signal), with the LED blinking some Facebook notification. Tried to wake up but it is in coma. I force a restart and it hotboot loops like I described on first post
It -only- happens when screen is locked. I disabled the screen lock for now to see if it's a workaround, but I'm not holding my breath
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
WildfireDEV said:
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
Click to expand...
Click to collapse
That's pretty much discarded. Wiping data instantly solves it. It did indeed run for 5 days with no external app without a single problem.
But also it ran over one week with external apps without a problem. I've executed some memory integrity tests and they all reported a-OK.
I'm kinda ruling out the "rogue-app" issue. I thought that recovering "data" from NAND backup was the /sdcard/android/data. But it's deeper than that. Now I don't even have a lead.
Phone already crashed today, without Vine and lockscreen, so that's not the problem. I really need to get some logs out of him. Just need to know how. Only if it could write a realtime log, so I could pull through ADB.
My last resort will be a fresh-fresh android installation, default S3 i9300 ROM, with only essential apps. Already have it triggered for the next crash.
If it goes rogue even this way, I'm running triangleaway and returning it (will be a profit too, the silver border is stripping).
This time around, I'm trying running it without a external sdcard (several files were being corrupted in it, don't know if it's due to force restart by removing battery, or some real issue on the card)
It's a problem within the Facebook social app or Youtube.
I've managed to run the phone flawlessly for weeks without signing in on Facebook, suspecting it might be it.
Today I logged in on Youtube app accidentally, and had to login on Facebook app to retrieve some info. Three hours later, phone went mad again.
I don't know which app caused it, but I think there's some relation to Facebook due to a greater ~involvement~ (couldn't find a proper word.. forgot it) with Android.
I've changed ROMs, launchers, system versions.. but not Kernel. I'll try another kernel and report on Boeffla main thread to see if there's some known bug
I don't know what may have caused this, but, here's what happens for both phones. They both boot up fine. Then after a minute or two, I can't access the status bar, but the phone still functions. Eventually, the Xperia launcher crashes, then it says System UI crashes. Then I can't do anything, then the phone eventually reboots. This happened on my Z3C a week ago, and now it just happened to my daily driver, the Z5C. It takes a little longer for things to happen on the Z5C, as in, I have Twilight installed on both, and Twilight doesn't even boot up oin the Z3C, but it still boots on the Z5C before everything crashes. What the heck is going on with my phone?
RCizzle65 said:
I don't know what may have caused this, but, here's what happens for both phones. They both boot up fine. Then after a minute or two, I can't access the status bar, but the phone still functions. Eventually, the Xperia launcher crashes, then it says System UI crashes. Then I can't do anything, then the phone eventually reboots. This happened on my Z3C a week ago, and now it just happened to my daily driver, the Z5C. It takes a little longer for things to happen on the Z5C, as in, I have Twilight installed on both, and Twilight doesn't even boot up oin the Z3C, but it still boots on the Z5C before everything crashes. What the heck is going on with my phone?
Click to expand...
Click to collapse
I had a similiar issue with both phones. I
Do you have xposed enabled? I found disabling xposed fixed constant reboot issue
rp3 said:
I had a similiar issue with both phones. I
Do you have xposed enabled? I found disabling xposed fixed constant reboot issue
Click to expand...
Click to collapse
No I don't have Xposed enabled on either phone. I ended up just factory resetting my Z5C since it's my default phone, but, hoping I figure out how it happens so I can stop it in the future
Hi,
sorry for posting here without being a developer myself. It seems like nobody on the other boards knows enough about android to be able to help me with this particular problem - which is the most strangest problem with electronic devices I have experienced so far:
The tends to "loose" sensors after a while. This mostly happens when in sleep mode, but can also happen during charging, sometimes after half a day, sometimes after a few seconds. The following sensors are affected: Accelerometer (including auto rotation), light, magnetic field, orientation and GPS. The sound and battery sensors keep going.
Now, while this is very annoying, it is not really strange. The strange part is the following: Two times I thought to have found the problem and get it back working normally, only to learn better 2 days later:
1) when I uninstalled the Dolphin browser - which never really worked on this device - the problem disappeared for more than a day and I thought it solved. Alas, it returned about two days later. So, Dolphin may have been a cause, but something new jumped into its place after 2 days.
2) at some point, I decided to uninstall Smart Launcher 3, which I had installed right at the start. E voilà: problem gone, the sensors worked perfectly without a single glitch for 2 days. So Smart Launcher must have been the culprit, right? -> wrong! Two days later the problem reappeared, worse than ever! All it takes now is putting the tablet to sleep for ~ 1 minute and the sensors are gone. If I want to use the sensors, I have to either prevent the sleep mode or restart the tablet whenever I want to use it.
So far, I haven't found another solution to make it work for 2 days (or even longer than a couple of minutes). But anyway, it doesn't make any sense. Why would uninstalling an app make the problem disappear, but only for 2 days? Then the same story again, when uninstalling another app?
Any kind of hint or suggestion is greatly appreciated, I am desperate and have no more ideas what else to try. All pleasure in the device is gone, it's just frustrating.
Thank you a 7'200 times (seconds in 2 hours)!
- spitfire
It just got more weird. I figured out, that enabling the power save mode caused the tablet to work somewhat normally, meaning sensors would still work after sleeping most of the time.
But guess what: 3 days later even that workaround doesn't work anymore. Restarting the tablet brings the sensors back, but switching the screen off (sleep mode) for 5 seconds is enough to disrupt them, always. This doesn't make any sense at all. Why does the device always find a way to counteract my workarounds after 2-3 days? Is the thing alive and doing it on purpose? It starts to drive me really mad :crying:
Please, does anybody have an idea? I am looking for
ways to restart the sensors without having to reboot the tablet. There must be some service to kill and restart, right?
ways to identify the cause of the problem. There must be some kind of event log where the sensor crash and what happened before is recorded.
I am sure somebody must know about those things, at least in this forum. Otherwise I don't know what to do, I run out of workarounds, the evil device wins this battle and will soon target the world - welcome Skynet.
Thanks very much for any kind of help
Pesche
edit: I noticed that when the problem occurs, it takes the tablet longer to wake up than the few times when everything is fine. This indicates that there is something going wrong with the wake up process. It must be possible to see in some kind of log what exactly happens, but my sparse knowledge of android isn't deep enough. I already tried OS monitor to access the catlog and I do see some warnings (pink W), but they don't tell me much. E.g.: OpenGLRenderer: Failed to choose config with EGL_SWAP_BEHAVIOR_PRESERVED, retrying without. Or: Syste: ClassLoader referenced unknown path: /mnt/expand/.../com.eolwral.osmonitor... (which rather sounds like a problem of OS monitor itself than a problem of the system).
i installed termux... ran top... i see a /system/vendor/bin/sensorhubd
i assume thats the process not "waking up"
is there a way to monitor that? or to tell it to restart? so we dont have to reboot everytime.............
isak.sr said:
i installed termux... ran top... i see a /system/vendor/bin/sensorhubd
i assume thats the process not "waking up"
is there a way to monitor that? or to tell it to restart? so we dont have to reboot everytime.............
Click to expand...
Click to collapse
I think i found whats killing it: google play services... disable body sensors permission in settings-->apps-->google play services-->permissions--> body sensors
also uninstall mcafee.
Wazzup.
Over at the Pixel 6 Pro fair, we have quite the number of people having problems with random reboots. We are trying to narrow it in - Android12? Pixel 6? Software? Hardware?
So - anyone here with the same set of problems? Or does the Pixel 6 not have that kind of issue?
For reference: https://forum.xda-developers.com/t/random-reboots.4353231/
I have gotten several random reboots as well. 256gb seafoam pixel 6. In particular, I was using "Frep" automation app (unrooted, used pc to start server) to do repetitive image searches in a game. Also the phone was sitting on a wireless charger while doing this. I noticed my phone felt pretty warm, wonder if it could be overheating?
Could be a naughty 3rd party app. Have you tried safe mode?
I posted this here:
P6 Bluetooth Problems
My p6 will see most some of my Bluetooth devices (laptop, tablet, TV, earbuds) . It pairs with the earbuds, but everything else it will try and pair, usually does not. If and when hen it does pair, that pairing is dropped dropped within 5 secs...
forum.xda-developers.com
My random reboots (or crashes that forced me to reboot) almost entirely stem from the wifi+bluetooth implementation. I found a sure-fire way to crash it during setup. Without word vomiting here, connecting the P6 with and to other devices has proved more difficult than any previous Pixel (for me).
mruno said:
Could be a naughty 3rd party app. Have you tried safe mode?
Click to expand...
Click to collapse
Not yet. It's also hard to "force" it (the reboots, I am not able to replicate it manually). Yesterday it just randomly happened whilst the phone laid idle next to me, thrice at the morning, about one time through late afternoon, then one time evening. I just notice the screen lighting up, then the Google logo comes, meaning the phone restarted.
I'm also pretty sure that Bluetooth/Wifi settings differed when the reboots happened, ergo at some times bluetooth was on, then when it rebooted, bluetooth was off. At no time when the reboots happened had I a bluetooth device connected. WiFi was online though, all the time.
What all the reboots have in commong though (at least the ones where I am concerned), is that the phone is just laying next to me, or somewhere, being in idle - doing as far as I know, nothing. It never happened when I used the phone or put it under load, so my P6 never "crapped" out under me. That's why I am not that concerned about this as of now, but it's certainly a nuisance to unlock the phone every time with my darn pin.
(Concerning 3rd party app) - I'd say that's unlikely. I copied my files over from my Pixel 4 XL and have not yet added one singular other app to my P6 Pro, so it should have gone naughty before my transfer over.
Hi! I experienced a big crash on the pixel 6. When I was configuring telegram, the app crashed and then the screen got black. After a minute it rebooted to the Google logo with a loading bar underneath. It was blocked in that state, but I could reboot it with volume up + power button.
I was pretty scared as the usual button down + power button didn't do anything lol
12 (SD1A.210817.036) on my pixel 6, occurred randomly when opening camera app. Happend 7-10 times.
dirtyissa62 said:
12 (SD1A.210817.036) on my pixel 6, occurred randomly when opening camera app. Happend 7-10 times.
Click to expand...
Click to collapse
Odd. I never had a problem whilst using the phone, my phone only rebooted when laying idle (even though today I had no reboots at all, alas I didn't use the phone much, maybe 2h SoT without any heavy lifting).
Something in android 12 is bugging around, maybe we have to open support tickets.
dirtyissa62 said:
Something in android 12 is bugging around, maybe we have to open support tickets.
Click to expand...
Click to collapse
I just talked for a while with a Google rep and he said that they are not aware of any reboot problems, no people over at Google Forums have reported such a thing. "We do not monitor Reddit or XDA" - so he said he opened a support ticket to the responsible team and they would look into it, he also asked that I / we report/feedback this under -> Settings -> Tips & Support -> Feedback.
We also talked about a lens flare problem, that at least the Pixel 6 Pro has. If you shot some photos where the sun is directly shining into the camera, you might want to re-check them. Most of mine have either some sort of big circular green dot in them, or a big beam of light like in a phone with a very bad HDR processing. It seems to be some sort of software glitch, he also reported that.
So hopefully those things can get fixed.
This was the follow-up email:
Thank you for contacting Google support.
This email is regarding the chat conversation we had earlier today, I'm sorry we weren't able to complete it. Hence I wanted to follow up via email to ensure all your queries have been answered.
Please re-launch the camera app and check if the issue is fixed.
Please be assured our developer team is working on this to fix it as soon as possible. We would really appreciate your kind understanding as we work on this to fix it for you.
If there is anything apart from this that needs clarification, please feel free to reply back to this email. I'll be more than happy to assist you.
Thanks!
Nova
The Google Support Team
I'm having similar restarts while phone is sitting on a table doing nothing. Tried a factory reset and was fine until overnight on charge and it happened again.
Also have had a few times where wifi has stopped working for some reason. Not sure if related.
Not had any reboots but quiet a few app crashes in especially FB will be scrolling away and bang just closes also Amazon app ,
Well that was interesting.. When it rebooted that time, it gave me an error screen saying it could not load and may be corrupt. I had two options, try again and factory reset. Try again got me back running, but I'm wondering do I got as defective device now.. or if it's software related.
So after a lot of messing around, I think I have narrowed down what may be causing my reboots. It only seems to happen when I am using "Frep" to play macros on a game while charging my phone.. the phone gets pretty hot, and reboots when I tap the screen or try to swipe home or recent apps. Maybe its overheating, or maybe its "Frep" playing naughty.. but Frep did work perfectly fine on my old $200 used Nord N10 5g. Will update if it reboots while not doing this.
no reboots or crashes so far, not doing any gaming - but using phone for email, surfing, whatsapp etc and also a work profile for MS outlook and teams.
I have/had similar issues with my Pixel 6 (128GB - europe unlocked).
I was transferring old data via cable from my old (Xiaomi Mi A1) to the Pixel 6. This resulted in sluggish performance, crashes every 15 minutes. The crashes would randomly occur and behave mostly like this:
Try to unlock phone with fingerprint sensor
Fingerprint sensor lights up, nothing happens, no haptic response
Swiping up to the PIN entry. Enter PIN and hit enter. Nothing happens. Now freeze.
Screen turns black and it takes phone to reboot on average ~7minutes
Factory Reset; Installed apps manually (standard messaging apps, no games etc), better performance, problem persists
Factory reset; boot into safemode. It now took way longer to provoke the issue. But it still happened.
After this I contacted the customer service and they will provide me with a replacement. But now after a night of idle, the phone was working for 3-4 hours without any issue at all with most of my apps installed. It just now went into a random reboot (could only notice because it asked for PIN because of the reboot). But not the 8 minute blank black screen type of reboot.
I am really unsure what is the issue at hand here. But have to say that experience is less than ideal.
Mine just happened last night, not charging or running anything 3rd party apps (all from App Store). I tried to use the camera after eating dinner and noticed that double clicking power button doesn't open the camera anymore. After unlocking the phone it appears that the phone has restarted.
Is anyone running Private DNS on their system like Adguard DNS or NextDNS? I did some searching and people reported some private DNS were causing Android to crash. It was suppose to be fixed in previous Android versions but it could be back again.
I haven't noticed any random reboots (and the lock screen will require a pin to be entered after reboot and says this on the screen, so you should know the phone rebooted). I've had the P6 since the official release date. In fact, I haven't restarted the phone in days.
I run a wide variety of apps. Some from the Play store and some sideloaded. I think that any reboot issues are probably app related. Remember that A12 is very new and the are surely still some compatibility issues that app developers haven't found/fixed yet.