My audio randomly drops out and requires a reboot to clear. All audio is silenced. For example, pressing the volume buttons do not beep. It happens randomly, but most often after a reboot.
Tonight I was able to reproduce the problem fairly consistently so I was able to get a logcat (attached) of the issue. I was using Rockplayer v1.5.5 with hardware decoding. I don't think Rockplayer is the issue because the problem has happened with other programs, like Angry Birds.
I am not an expert but I see lines like "[FONT="]W/AudioTrack( 927): obtainBuffer timed out (is the CPU pegged?) 0x21a528 user=00033b2a," [/FONT]when the issue occurs. When everything is working normally, these entries are not there. I trimmed the log file to meet the size limitations. I have the whole file if needed. Please help!!![FONT="]
[/FONT]
Moved to general
I will try and post a logcat the next time mine does it.
I'm having the same problem. I can hear sound whenever i startup the tablet, but after a while (sometimes it can be less than 1 min sometimes after 5 hours) the sound stops and i only get static noise or no sound at all. Whenever that happens, in the android log appears the following lines repeatedly (with a frequency of 1 sec):
W/AudioTrack( ####): obtainBuffer timed out (is the CPU pegged?) 0x##### user=00######, server=00######
I've tried changing ROMs without success in solving this problem, now i'm using TNTL v4.4.0.
The bug triggers while i'm using sound (games/watching videos on youtube/playng music on winamp/ pressing the battery button on the status bar, triggering that "click" noise).
When this bug is triggered, i get FC from some apps that use sound (Youtube / Winamp / some games)...
Rebooting the tablet fixes the problem untill it triggers again
i've been using adb logcat several times with this problem and the only correlation between the logs is the line described above, i've tried searching on google, but the results i get are for cellphones or pre 2.2 devices... in one of them, they interpret it as a kernel problem (http://forum.xda-developers.com/showthread.php?p=6280968)...
Any help is appreciated.
Same thing here on one of the woot tablets running Vegan 5.1. 1. Usually happens after coming back from sleep. I asked for a replacement and the new tablet will be here tomorrow.
I really hope this is a hardware problem and not caused by a rom or app. Still interested in finding out what causes this, so I won't have this happen again with my new tab. Did anyone have this issue with the stock rom? Are these all recently bought tablets? I didn't spend enough time with stock to encounter sound problems.
I've been toying around with my tablet to see what is causing the problem, so i started by Flashing all over to stock to find out if at some point the sound problem stops... well... here are my results untill now:
Started at TNTL 4.4.0, Many apps installed and the sound problem appears constantly and is triggered easily. Before starting I backed up everything using Titanium Backup xD.
Part 1: Format + NVFlash to "belkit 1105" + Factory Reset: Problem Still Arround, took me about 3 reboots and 7 minutes to reproduce it by playing a song and randomly click on the battery/wifi/notification buttons with the sound of those buttons turned on.
Part 2: Updated to "stock 3588" (couldn't do it through OTA because it sayed that my tablet was up to date... so I downloaded the update from the NVFlash guide and installed using this guide from the internal SD. It didn't work, it took me about 5 minutes to reproduce the error, no rebooting .
Part 3: Settings > Security > Factory Reset: ... still haven't been able to reproduce the error, i've rebooted it about 7 times and listened music for 3 hours, eventually clicking on the notification/battery/wifi buttons and it seems to work fine... at least this is a checkpoint for me
It would be great if someone with the same problem could confirm that this works, i'm going to leave my tablet playing music during the night just to be sure :9.
Oh, JIC I bought my tablet on 27 Feb from J&R Electronics Inc through Amazon.
I'm having the same problem with mine in fact I have the tablet sitting next to me and the thing just went all static and freaked the cat out and woke my wife up not exactly cool when your in bed! I may have to look into exchanging or return it! I would hate to be at work or somewhere else and have it freak out like that! It's annoying!
I'm having the same problem, I lost all sound once I upgraded to Vegan Tab Ginger. Downgrading, or any changes doesn't do anything
I have a similar issue. I installed Cyanogenmod 7.0.3 and my sound mysteriously goes away. I can easily repeat it by putting the table to sleep and then waking it up. Sometimes, you can hear some static before it goes out.
I discussed this with Gojimi long time ago, but, I dont remember, I think the issue got lost with time. Still happens though
Related
hello.
i have a 32 gb hp touchpad overclocked.
when i turn it on i have sound working good.
but after very quicly, it have no more sound at all (even when i push the sound + or soung - button, i see the sound logo going up and down but no sound)
and if i turn it off and on the sound come back.
do you know what can be the problem ?
Thank you
Happens to me ALL THE TIME. I just chalk it up to WebOS being completely unfinished. But then again it could be some of the patches I have installed, since I spent all of about 3 minutes without them.
Me too, I read that Making a call in skype will bring sound back.
Apparently it helps to disable system sound, keyboard and vibrate.
Happened to me twice more today. So annoying.
Happens to mine pretty much daily. I don't see a whole lot of *****ing in general about it though, mostly here and Precentral, which leads me to believe it's mostly "modified" touchpads with this problem. I'm thinking it's a patch or kernal problem.
It's most likely a problem with a kernel or patch. I have 3 16GB's, two stock, one modded, and none of them exhibit this behavior. Since all of you have modded yours, I suggest removing patches/kernels and see if the problem persists.
parisien99 said:
hello.
i have a 32 gb hp touchpad overclocked.
when i turn it on i have sound working good.
but after very quicly, it have no more sound at all (even when i push the sound + or soung - button, i see the sound logo going up and down but no sound)
and if i turn it off and on the sound come back.
do you know what can be the problem ?
Thank you
Click to expand...
Click to collapse
te)
Install the Preware Linux App > Increase TouchPad Volume ( Lite)............
See if it makes a difference
I haven't figured out what causes it for me, but a simple solution to fix it without having to restart is to run a couple commands in xterm..
stop pulseaudio
start pulseaudio
Sound goes off (ANNOYING)
Why does the sound go off all of a sudden, I hate it, I can't even hear youtube videos, it requires a restart
Sent from my SCH-I510 using XDA App
Finally , I had to disable the email audible notification (left the vibrate only). Now it has been OK for more than 1 week, before it will lose sound in a few hours.
Hope HP get's this resolved.
Thanks
trialdoer said:
I haven't figured out what causes it for me, but a simple solution to fix it without having to restart is to run a couple commands in xterm..
stop pulseaudio
start pulseaudio
Click to expand...
Click to collapse
If you install the "Advanced Reset Options" patch, you can use it to restore your sound...
Just hold the power switch until the buttons show up, then tap "Cancel".
Hi,
Advanced Reset option does not fix the issue for me (unless I select Reset).
Sound fails even if the only App I have opened since a full reboot is the email App.
Maybe one of the installed Logging patches is causing the sound to drop out? Maybe we should enable logging to see if the logs give any indication around what is causing the sound issue?
this issue was happening to me everything my touchpad would go idle for longer than an hour (super annoying) however I gave all the suggestions here a try and finally had luck with robrob777's suggestion! Turning my email notification sounds to vibrate has seemed to fix my issue hasn't happened in 2 days. Just wanted to say thanks robrob777!
gburt said:
Advanced Reset option does not fix the issue for me (unless I select Reset).
Sound fails even if the only App I have opened since a full reboot is the email App.
Click to expand...
Click to collapse
There's an article over on precentral about fixing the problem, though it really isn't a fix, but rather a way of getting your sound back without a reboot. See it at:
www
precentral.net
/
fix-your-touchpad-s-lost-audio
Sorry about the format of the link, but forum rules for newbies prvented me from posting it properly. Since it obviously isn't spam, I am hoping I won't be in trouble for it.
It's complicated, and you might find a reboot easier, but perhaps some developer who's into patches will spot it and come up with a more permanent fix, either to fix the problem itself, or at the very least, to have the stop/start fix applied when the volume control button reaches max and is pressed again once or twice.
Update: It just became a little easier to apply the start/stop "fix". XServer, Xterm, and Xecutah just became available on webos-internals (.org). Just use Preware, select Applications, All, and the new stuff will show at the top of the page. Just download Xecutah and the other two packages will download with it if you allow it.
Update 2: Even easier...
After installing the X stuff, start Xecutah and create a shell script in the default directory you land in with Xecutah. I just used cat and typed it in.
cat >fixaudio
Here's what I put in it...
#!/bin/sh
stop pulseaudio
start pulseaudio
Then, fix up permissions...
chmod 070 fixaudio
(It's been a while since I used Unix/Linx, but I'm sure someone will correct my permissions choice if it's not right).
Then, when your sound goes away, start Xecutah and type fixaudio.
Even better... Use Preware to find an app called PulseAudio Restarter. Works well.
Okay, I would have liked to post this in development but apparently I dont have enough posts. What is th deal with the phone dropping out on CM10 when the screen goes black from the sensor, then coming back when the call is dropped by the other person. Does anyone have a fix for this, the CM10 thread gets so diluted with different issues you'd think people would start making other topics regarding issues rather than discussing them throughout a 30 page thread.
Are you talking about the screen shutting off and not being able to use the dialer or any onscreen buttons?
tallyforeman said:
Are you talking about the screen shutting off and not being able to use the dialer or any onscreen buttons?
Click to expand...
Click to collapse
Yeah but it also drops the phone call when that happens.
Thanks really strange. Try getting a fresh download with the gapps and flash it again.
It's a good thing you didn't post this in the development because it would have been moved here. You can always PM me with questions and I try my best to respond to everyone in a timely manner.
Anyhoo. I'm not quite sure as to why this isn't working yet. I've called my family, friends, girlfriend, whomever a few times already and haven't ran into the problem yet. With this being said, no one is giving any real details on what leads up to the problem or how to really reproduce it. The best I've received so far is "I make a call, the screen goes off and won't go back on." What I need is someone to get me the logs of this happening. As weird as this may seem it's the only way I can help anyone with it. Apparently from what I hear the phone is still "working" but with the screen just not turning back on. If this is the case, anyone should be able to plug their phone into their computer and get me a logcat of what is going on (this doesn't require any screen interaction if the phone is setup properly). If you have any questions on how to get one, search the forums. It's been posted in just about every development forum for every phone including ours.
My phone did that last night. People in the CM10 thread have been blaming it on the bluesleep fix but who knows. I had that flashed at the time too. When it happened, I was on a call and the call dropped a few minutes into the conversation, the screen stayed black and didnt come back on. I had to pull the battery and restart. I called the person back and it happened again. Long story short, due to my own error, one thing led to another and I ended up SBF'ing. Since last night, I made one call and it didnt happen. I need to make more calls to see if it persists. The problem is, I dont call people very much. lol
Just want to add that I was having this issue also. I only noticed it after I installed the bluesleep fix... I SBF'd and installed clean with no bsfix and have not had this issue since... Maybe it has nothing to do with bluesleep but thats some really strange timing if it doesnt.
If it happens to me again I'll get a log for you DZK but seeing as I don't plan on flashing the bluesleep fix back I don't think it will happen.
Well I sent a message to you DZK cause i'd really rather avoid SBF if I could. But if I have to I will because most people are linking it to the bluesleepfix which I did indeed install. In any case, the phone just hangs when the screen shuts off until the other person hangs up the phone then the call is ended and the screen comes back, but until then voice is dropped the call is droped and the screen remains off as that person tries to talk to me but isnt disconnected until they end the call.
[Tutorial] How To Logcat
Logcat or it never happened.
download adb
place it in folder I use
Code:
c:/root
open command prompt
Code:
cd/
Code:
cd c:root
Code:
adb logcat *:E > oh_nos_it_crashed.txt
should work
oh_nos_it_crashed.txt will be in root folder can name it
Code:
adb logcat *:E > dropped_call.txt
if you want
I'm having similar issues. The phone locks up on a call and can't be unlocked. I just have to pull the battery. The call continues for me, so at least I can finish the call, but to hang up - pull the battery.
I currently have the CM10 ROM, gapps v5, and bluesleep fix applied.
So, how does one get rid of the bluesleep fix? Can I delete is somehow using a root browser, adb, or... ? If not, can I just reflash the ROM and gapps files (without the bluesleep fix) without a factory reset, etc.? Or am I in for a complete refresh of the phone and reflash of the ROM and gapps?
TIA
no way to remove bluesleep that i remember
just restore nandroid of rom other than cm10, then reflash cm10
This started happening to me tonight.
I haven't installed the Bluesheep fix... unless that's the MX2 wifi patch.. if that's the case then I have that too.
My current workaround is using headphones, which disables the proximity sensor.. I also put my phone to stay cycle a little longer.
I just flashed my phone with CM10a3 Wednesday and ran into this issue with the first call I tried to make. I'm still new to rooting and flashing ROMs (my first time lol) so I don't have too much useful information, I will try and gather some logs next time it happens. Unfortunately it is not something that seems to happen every call. My current work around is to use bluetooth or speaker phone as the issue does not happen then.
I'm using
CyanogenMod 10-20130113-Daytona Alpha 3
gapps-jb-20121011-signed
I'm also running into issues with the mount locations and losing settings upon restart, however I still need to do more research on those items first.
I was able to get some logs around the phone call issue. However, it appears the behavior has changed for me now. When the screen goes to sleep, the call audio cuts out, and then about 10-15 seconds later I get notified that the call was dropped. I do now however have control of my screen during this whole time.
Unfortunately by speakerphone workaround does not work for this new behavior, so I have to carry around a wired or bluetooth headset in order to take calls.
Since the behavior is no longer identical to the original poster, I'll post my log in a new thread once I clean up some of the noise in the log.
licwid said:
I was able to get some logs around the phone call issue. However, it appears the behavior has changed for me now. When the screen goes to sleep, the call audio cuts out, and then about 10-15 seconds later I get notified that the call was dropped. I do now however have control of my screen during this whole time.
Unfortunately by speakerphone workaround does not work for this new behavior, so I have to carry around a wired or bluetooth headset in order to take calls.
Since the behavior is no longer identical to the original poster, I'll post my log in a new thread once I clean up some of the noise in the log.
Click to expand...
Click to collapse
lol carrying headphones around? that sounds a bit overkill.
I rooted my phone a month or two ago using odin and TWRP recovery, and I also flashed a new rom (Resurrection Remix 6.0.1). I have since had constant issues with my bluetooth headphones, which are the only bluetooth device i use with this phone. I have searched online and looked at many forums but I couldn't find very much information to help me. My issue is that there are random times where the audio from my headphones gets very choppy and unintelligible, kind of like static. It only occurs for a few seconds though, then everything resumes perfectly fine. Another big issue I have is that when I wake the screen, the same audio choppyness will occur and it will usually stay like that on the lockscreen, and when I unlock my phone, it goes away after a bit. My phone will also randomly show the message "Bluetooth messenger has stopped working" sometimes, usually after my phone is unlocked after a while of not using it. I have turned off my phone's doze function, cleared the cache many times, and factory reset it to no avail. Hope you guys can help.
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.