Develop Bugs

[Q] HTC Desire Z Freeze During Standby Mode

Hi,
I just got a new HTC Desire Z Bell Branded (A7275) for my AT&T service. I "debrand" it using the debrand guide. I just noticed twice yesterday that when I put it in standby mode, I try to press the power button to turn off standby mode so I can get the screen to slide down to unlock the screen for usage. Well, it did not....no matter what I do...I cannot get the screen to get unlock. The screen is black as if it isn't on. I hold the power button, still nothing. Only way is for me to pull the battery out, put it back in and power it up. Is this common? What is the problem that causes this? Any help would be nice. Thank you in advance.

have you oc your phone at all? have you flashed a kernel? custom rom? and what guide did you use?

I used this guide to debrand my phone.
have you oc your phone at all?
Not a single bit, everything is bone stock regarding CPU.
have you flashed a kernel? custom rom?
I only flashed the one from the guide.
[ROM] RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e _26.03.02.26_M
what guide did you use?
http://forum.xda-developers.com/showthread.php?t=835777
Thanks for the fast reply and help, bahmanxda.

Tbh I am not sure what is the problem I got nothing ,the only thing that I can think of is if you are already rooted and s/off do a full wipe and flash the Rom again or try different roms if u like sense try virtuous 9.0 its really good.
Sent from my HTC Vision using XDA App

There are some others with this issue. Unfortunately, the cause has not been found, or whether it is hardware or software related:
http://forum.xda-developers.com/showthread.php?t=857584&highlight=pulling+battery
I've had this crop up myself a few times. I can say this:
Several times my Desire Z has powered off and could only be powered on after pulling the battery and re-installing. It did this twice within the first few days I owned it. Then it didn't happen anymore.
Maybe a week later I tried the Godspeed kernal (1 GHz) and SetCPU. No issues for about 2 weeks.
Then I tried CPU Tuner based on claims made by some users here that it is easier on battery life. Used a screen-off profile to underclock. The phone had the power off problem, 3 times in 2 days. Every time when the screen was off. But the random poweroffs did not start immediately after installing CPU Tuner, maybe 2 days later.
I uninstalled CPU Tuner to see if it would help (and it didn't seem to be improving battery life). Went back to Set CPU (have messed around with and without screen-off profiles). Its been more than 2 weeks, and no random power-offs.
None of this is conclusive, of course. Maybe the problem in my case was CPU Tuner, or a combination of the kernal and CPU Tuner. Maybe the things I've described are complete coincidence, and its some other factor altogether. But just thought I'd throw my experiences out there. Some claim Google Maps is the problem, but I have not found this to be the case. Or possibly some issue with the battery contacts, or the battery itself. Who knows?

Same thing happens to my Bell Desire Z. Every now and then it just decides to freeze and Only solution seems to be to take out the battery and then put it back.
Very frustrating.

Thanks for the reply, everyone. Strange it has not happen for the past 2 days now. I've read the other thread and still no exact detail on the cause of this. This is not good...especially it is my first Android phone and first HTC (bought it due to their reputation of quality made phones).

It happened twice within the first week of using the phone. Decided NOT to return the phone to observe it for a full month. During that month it happened every 3-4 days, always happens when the phone is not charging, and at the hour mark. Decided enough is enough and returned for a warranty claim 2 days ago.
During the one month, I rooted the phone after 2 weeks and flashed a custom ROM, but the problem did not go away.
There're people who aren't affected by this problem though.

I've the exact same problem here. CM 6.1.1 will just randomly black screen on standby. No response to charge when plugged in. The only way to reset is to pull the battery.
I don't think it happened on stock firmware. I'm now highly debating switching ROMs. It's getting annoying to remove the back cover every time I need to do a hard reset.

I think there is a thread in regards to CM and overclocking causing a screen on issue. But I think in those cases, the phone has power (LED and front buttons light up), just the screen can't power on. But adjusting any overclocking/underclocking profiles is worth a try.
Do you have SetCPU or CPU Tuner setup, and any profiles under those, such as underclock when the screen is off? I tried CPU Tuner for a few days, due to claims by XDA users of better battery life than SetCPU. I got 3 instances in 3 days of the phone not being able to power on (had to pull battery). I un-installed CPU Tuner, switched back to SetCPU, and haven't had the power on issue crop back up for almost a month now.
Given, I had the power on issue 2 times before using CPU Tuner, so it can't be the sole culprit. My only theory is that some combination of switching the kernel and SetCPU has solved the issue. Or it has nothing to do with those at all, just a coincidence, and is something else completely. Who knows.

It happened to me many time already. I still use stock htc desire rom and never rooted..

I've had it happen about 6 times, always requiring a battery pull. Totally stock other than being unlocked, not-rooted. But it hasn't happened for the last 3 weeks or ever since I stopped using juicedefender. Coincidence?

Desire Z freezes
Hi,
I also have some random freezes of my Stock Desire Z, I didn't do a thing on software or hardware side.
I run Android 2.2.1 Build 1.72.405.2 CL296256, provider KPN (Rabo Mobiel)
I got rid of the hangs after the upgrade from 2.2.0 then after several weeks it came back, only solvable by removing the battery.
I tried to figure out what's wrong and I think I have several clues:
- mostly some time after using Google Maps
- mostly when Wifi was on (it might be that the Wifi has limited connection and it screws up the data)
- after the reset I allways have updates from Market available
I can't remeber the Memory widget I ran, which I felt was having a good influence on the hangs.
I'm not happy with this behavioure, but cannot determine if it is hardware or software, it's not helping much that the phone just stalls , a reboot is irritating but less then a complete hangup when you don't know how long it has been in that status.
P.S. I don't run juicedefender
Cheers, Edward

I have STOCK G2 ROM.
S-off, CID, unlock via http://forum.xda-developers.com/showthread.php?t=855764
NO Cputuner or SetCpu (well I uninstalled them before these problems cropped up)
Used G2 for about a month and a bit no problems. Installed launcher pro then started to experience this problem. Coincidence? Not sure. Uninstalled and it did not help. Uninstalled several more apps that I recently loaded (skype, minimalistic text, Gtab Simi clock...) didn't help.
Wiped phone, nandroid backup to original ROM, restored using TB. Worked for a few days then just started happening again.
I also was using 2 chinese batteries I bought from eBay. Not sure if this has anything to do with it either.
// Just reflashed, HTC stock battery. Froze up within an hour. Too bad I bought this off of ebay, no warranty
// Factory Reset, restored apps and data with TB, still freezing

Hi all
I'm new to this forum (sorry, a newbie about to make a whole load of gaffs, no doubt), but I am at least fairly tech-savvy. I've had HTCs for years, right from the days of the 2000 vintage Compaq Ipaq!!
My wife & I bought two Desire Zs at Christmas, and it was therefore 50:50 which box was opened by whom. It appears I picked the dud, as I'm suffering from the issue described by all you guys, and in the other thread:
http://forum.xda-developers.com/showthread.php?t=857584
For the sake of adding more evidence to this otherwise confusing issue, I thought I'd join the forum:
So:
1) The device is not modded in any way. Standard ROM from HTC, being used on the UK T-mobile network. Currently at Android 2.2.1, Kernel 2.6.32.21-g540976a, Build 1.72.405.2 CL296256 "release-keys". This was installed on Christmas day, over the air.
2) There has been no playing with processor speeds or memory management.
3) The first crash of this nature was either on Christmas Day or Boxing day (ie the day-after-christmas-in-England); can't quite remember now, but certainly after the ROM update.
4) I have had this occur irregularly, but in increasing frequency, since that date. I think I'm probably into double figures by now, but I've only started to log them recently.
5) I was starting to think that there was some correllation with GPS applications. The phone would die after using Google Earth, for example, but not immediately. It may be after two or three standby's that it would fail to respond on the fourth, for example.
6) I had a very bad day a few weekends ago where the phone died four times in a single day. I had been using geotagging-photos (in the standard HTC camera app)... plus location-based services such as Yell and Google maps.
7) I tried keeping GPS disabled, and to be fair, there was no evidence of it crashing at that point. But I use GPS too much to make this plausible for a long time.
8) I wondered if it was due to the motion of keeping my phone in my pocket, but it died over night on the bed-side table on Monday-Tuesday, where my last usage had been the Friend-Stream widget/app. GPS was on...
During all of this, my wife's phone has not shown any of these symptoms. Whilst she uses Google Maps, Google Navigator & HTC Navigator a bit, she generally keeps the GPS turned off except for specific odd occasions. Hers has not crashed in this manner...
About to contact HTC to see what their response is...

This has occurred for me regardless of app usage.
It can occur right after a fresh reboot after being fully charged.
// Wow, I was in the middle of sending a txt and it just shut off on me...
I really wish I had a warranty on this

Hey there.
I can clearly pinpoint the problem with my desire z to the GPS. In the first view weeks I used it regularly and my phone froze, but only when the gps sensor was not active anymore (and the phone had gone to standby once or more). It didn't matter which app I used. For a while now I haven't been using GPS and my phone runs smooth as hell.
@lost800: I suppose your problem has a different kind of nature.
I already contacted HTC (very good support) and they told me to send it in to repair. I need my phone for work at the moment and I haven't found time to do this.
Due to the very small amount of ppl having that problem, I suppose it's an hardware error.
Greetz
Edit: Just out of curiosity, is there any meaning to the kernel version? Or has every mobile phone the same one?

Hello all, here is my input on this problem
My DZ has started freezing while I'm doing stuff:
* playing cards
* writting an email or a text
* using xda app
* ...
I never have GPS on. The frequency has greatly accelerated in the past 2 weeks but the weirder thing is that the last 3 times I remove sdcard and then put it back in to get the phone to boot, but it does not boot... it hangs on HTC logo for a long time (I've left it there for up to 15 minutes to see...) I eventually just remove the battery and from the phone and wait before trying to put it back in and boot...
Wait times required have varried from 5 minutes to several days.
I have observed this behavior on Stock 1.34.405, Virtuous 0.9, Virtuous 1.0.0 and back on stock 1.34.405 Today. I've wiped, flashed stock RUU nothing has helped. This puppy is going back for repair/exchange (it is 3 months old).

dwardo said:
Hello all, here is my input on this problem
My DZ has started freezing while I'm doing stuff:
* playing cards
* writting an email or a text
* using xda app
* ...
I never have GPS on. The frequency has greatly accelerated in the past 2 weeks but the weirder thing is that the last 3 times I remove sdcard and then put it back in to get the phone to boot, but it does not boot... it hangs on HTC logo for a long time (I've left it there for up to 15 minutes to see...) I eventually just remove the battery and from the phone and wait before trying to put it back in and boot...
Wait times required have varried from 5 minutes to several days.
I have observed this behavior on Stock 1.34.405, Virtuous 0.9, Virtuous 1.0.0 and back on stock 1.34.405 Today. I've wiped, flashed stock RUU nothing has helped. This puppy is going back for repair/exchange (it is 3 months old).
Click to expand...
Click to collapse
I called HTC support to see about getting the phone replaced. After explaining to the guy that it was freezing and then not rebooting when I pulled the battery out, the first thing he said was: "Did you install apps from the market ?"
Given that I replied by the affirmative he wanted me to test rebooting in safe mode and seeing if the freezes still occured before moving on to a replacement. He claimed that some market apps are not "properly coded and can mess up the phone"
I asked for and got the instructions how to reboot into "safe mode" (hit keyboard S key at HTC logo and stay on it while it boots)
In "safe mode" you can still install apps but they won't appear in the app drawer so you won't be able to start them (you can start them if they are on your home pages though ). No backgroud apps will run though (bbc, task killer ...)
Well I ran in safemode for 6 days and used the phone as I always do (work email, leisure email, web, video, camera, games, GPS, bluetooth etc...) and the darned thing ran perfectly. No freeze during those 6 days (the last few times it took less than 2 days to get a freeze).
I therefore decided it was time to test it again in "normal mode". Before rebooting I removed my task killer as for me this was "THE APP" that "safe mode" was really blocking from running on my phone...
Well It has been 2 days now and still no freeze. If it stays that way for another week I think I will have a rather good idea of who was the culprit...
Will keep you all updated and keep my fingers crossed.

Hi guys
An update:
HTC over the web-support were very helpful. Immediately they suggested that the device needed to be taken in for repair. In subsequent stages of the dialogue, they stated that the mainboard would be replaced.
A couple of weeks ago, I cleared down my device, packaged it up and waved goodbye to it (sniff...). HTC took it and...
!!DID NOTHING!!
It came back on Monday with an *old* ROM installed (1.35... If I remember correctly), and a statement saying 'no fault found'.
I've built the phone back up to where it used to be, including installing the over-the-air update to 1.72.405.2 (I need this as there's an activesync exchange bug in the old ROM) and within 24 hours, the device was unresponsive again
I have just written back to HTC to find out what the next steps are. I'd be interested to see if they suggest some debugging actions, like the safe-mode option, for example.
I've also asked them directly if their engineers have any clue what is causing this? Fundamentally, I don't see how any app should have the power to kill the device, however badly written it might be. That suggests insufficient controls/barriers in the OS.
Throughout this period, my wife's phone has continued to operate perfectly, even with some extra GPS playing to try to force a failure. So, we are now looking for any differences that could help to pin this down further. One difference is that she has never enabled the HTCSENSE.COM account on her phone, whereas I had. Perhaps there's some problem with the Phone Location functionality (in addition to the fact that I have to be in a yacht off the West coast of Africa for it to accurately show the phone's location). To test this, I've removed my HTCSENSE.COM account this morning.
Dwardo: I think your issue is slightly different, but the safe-mode info is useful.
Thanks
Andy

Nexus 5X reboot problems

If you're having reboot problems please post here - if there are problem apps or bad devices out there it would be good to know!
Got a new Nexus 5X yesterday for my partner. Plugged it in and charged all day (oh what patience). 10pm started setup and added account to it. Phone immediately did an update which succeeded. Then it started to install the saved apps from the Google account, about 50 in all. After all the apps were installed I handed it over to her to play and log into all those apps with logins. Tedious.
Within about 30 minutes she tried to take a photo and it rebooted. Then a bit later she was using it and it rebooted again. Before going to be it rebooted a few more times. Then again this morning. There wasn't one particular app or other that was in use when these crashes happened. During the day she saw a message about "Google needs to restart". Also the camera often comes up with an all black screen and can't be used.
I called Google tech support and they wanted to do a factory reset and maybe a cache partition wipe. They would also like to investigate if a rogue app is causing the crashes by using it without any apps installed. Because reinstalling apps is so tedious I decided to have her do a cache partition reset I'm awaiting news. I'm hoping we don't have to do the other... I can't imagine how a bad app could be causing such repeated crashes (well I can, but it just shouldn't happen). That's lame...
It would really help if it was easy to get a crash log and find out the cause - unfortunately unless you're rooted this doesn't seem to be easy, and may well be impossible.

I've been having a lot of similar-sounding issues with my 5X. It's never rebooted while I was using it, but once or twice a day I'll pull it out of my pocket and it will be off, awaiting the unlock pattern to boot up.
The camera has been atrocious as well. I've seen the black screen you describe, tons of rotation lag, hanging, etc. Not just in Camera, but in other apps using the camera (such as when attaching a photo to a Hangout). Hoping this is something software-related and not a hardware problem.

I've had mine spontaneously reboot twice so far, both times I've pulled it out of my pocket and it required the PIN to unlock, then it booted up. I'm a bit concerned, as I have no idea when this happened, and, since it's encrypted a reboot essentially puts me offline until I notice it.

I just now had mine reboot during active use for the first time. I was long-pressing a wifi network in order to forget it (which is another 5x problem I keep having—wifi turns itself off or connects to the wrong networks).

My 5x was working fine and the crashing started happening yesterday...
they only app that i recently installed before the crashes started was firefox... are you guys using firefox by any chance???

Mine is still working fine, I do not have Firefox.

Same problem for me when using Firefox. The phone seems to crash and reboot when loading news websites containing photos and videos.
Not seen the issue when not using Firefox.

I've had my nexus 5x since mid/late November 2015. I've had the problem described below happen prior to today, and more than once.
Today, I cant turn my phone off - it seems to be in the middle of a reboot... the four coloured circles (google logo?) with colours going round and round. I powered it off cos it had started going slow... thought a reboot might fix the problem... but now its not starting and I cant even turn it off or do anything with it.. I've tried pressing the power button, I've tried holding the power button down, and I've tried different combinations... nothing seems to make a difference... (has been in that state of un-useablity for at least 30 mins now)
Anyone else also having wi-fi issues where facebook has an error and "cant connect" ?

I had the same thing happen and returned the phone, it's the only solution I found. I factory reset multiple times, called up Google and they told me to safe boot. Right.. I was completely stock and it rebooted multiple times / day and I know what I'm doing too, for the most part anyway. Got a replacement device and it has not once rebooted no matter what I do. Camera, Chrome random apps caused a reboot, it's not that. It's a defective device and you need to get it replaced period.

I have the same thing and can't sent it back to google because I live outside the US.
I believe it is a manufacture defect as I tried everything with no success really annoying.
Stuck with a brick...
Sent from my Nexus 5X using Tapatalk

I used my phone completely stock for weeks and had zero issues, whereas I have a friend who ordered and received the phone at the exact same time (likely same mfg batch) and had issues. Difference between us two is that I'm a minimalist and only have about 50 apps installed, and he has a ton that he rarely uses and restores them every time.
I know it seems ridiculous, but having an android phone gives you more customization and your apps more power of the phone, so it's completely feasible for ONE rogue app to destroy performance and/or battery.
You guys might all want to try uninstalling apps one by one and figuring out which apps are killing performance. In particular, check out the running services (developer options -> running services) and see which apps are constantly running, since those are more likely to be the ones causing issues.
For example, I've used firefox (for adblocked browsing) for weeks recently, and can definitely say it's a pretty slow app, so if you're having issues on it, you may want to just use chrome or lightning browser.

I just ordered a replacement as well. Mine would reboot about 1 to 2 times a week right after the fingerprint unlock. Annoying as hell today because I was in the middle of a conf call.
Sent from my Nexus 5X using Tapatalk

#brickgate

Hi everyone, I had some strange behavior with my note 7 last night, it locked up for abou 10-15 seconds and then rebooted itself and got stuck in a bootloop, it looped through the first boot screen for around 10-15 cycles and eventually managed to boot up, I kept having random reboots and bootlooping for the next hour or so, I suspected it could be the stock browser as it seemed to be what I had open when most of the reboots occurred so I disabled it with EZ disabler, I haven't had any trouble since last night and I have re enabled the stock browser a day still don't seem to have any problems yet. I googled it and found that apparently a lot of people with the exynos variant are having similar issues, I read somewhere that it was the July date coded models that had the issue but mine is an August coded model, does anyone know anything about this?
Edit, its possible that downloading or updating apps might have something to do with it.

Mine does this and has been doing it since day 3 of my 10 days of having it.
What I'm gathered, any form of lag that corresponds with the vibration motor causes the reboot - so if you touch the back button one too many times or hitting the menu button; heck, sometimes it even just reboots when I'm scrolling in anything and there's some lag (both Chrome and stock browser as well as Whatsapp/Playstore).
I talked to my Telco and they said they'd replace as it's a clear defect but there's no stock unfortunately for an instant swap. I'm about to switch to the international XSA firmware (Currently on OPS Optus firmware) to see if that does anything since the XSA had a recent update relating to performance issues. If it is a defect it won't do anything and the best bet is to go into store and send it off while they order a new one.
Mine's begun to do it more frequently now. Sucks that this is the experience of a first time Note user :'(

Frequent freezing occurences per day

Nexus 5X 32GB - stock Android 7.1.2
Fact 1: The device presented the usual bootloop issue a couple months ago. I sent it to LG support for repair, where they replaced the entire PCB. For about a week after the repair the device behaved normally, then the freezing issue started.
Fact 2: After some factory resets and experimentation with installing/uninstalling apps I suspected might cause the issue, I unlocked the bootloader, flashed the latest stock Android 7.1.2 image (wiped user data/cache etc.), relocked the bootloader and kept using it normally.
Fact 3: A few days later from the flashing, the freezing issue came back.
Behavior: What happens is that the device randomly freezes when interacting with it (be it texting on a messaging app, scrolling through Chrome, expanding the notification bar etc.). When this happens, most of the times the device will stay frozen for a couple of minutes and then take me back to the lockscreen where I need to enter my PIN again to unlock it. Sometimes it will just reboot. And less frequently, it will give me an error message that "Google App has crashed". All of the times, when the device remains frozen, the back of the phone will get hot (but not extremely hot).
As you understand, I haven't yet managed to find the root cause of this issue, whether software or hardware induced. Nevertheless, the phone is rendered unusable that way and I want to investigate my options.
Any ideas? Your help is much appreciated.

I would see if your are still covered under the warranty and get it replaced with a unit that doesn't have the hardware issue.
Sent from my Nexus 5X using Tapatalk

I'm noticing similar behaviors on mine too. I have the latest Android 6 room installed instead of 7.
It started happening about 2 weeks ago. Was there an update on Google apps or the core platform recently that could be affecting the ROMs?

I have exactly the same problem! Except I haven't flashed anything. Mine has been stock all the time. So I don't think it is because of flashing.
They also replaced my phone's motherboard after bootloop. And now I have this random freezing at least once a day. Also I haven't been rooted or unlocked bootloader.
Mine is still under warranty.
Does anyone have an update?

I also saw this start happening on a stock 5x with no bootloop issues and no replacement hardware, roughly mid-May. Usually multiple freezes per day. Have not observed freezing for the last 5 days or so, though -- operating like normal again.

Just an update: Lately the issue happens a lot less frequently, but it's still there.
I suspect it has nothing to do with the ubiquitous bootloop issue (as mine has been repaired before the freezing issue appears, while @biff-torkington experiences freezes without having the bootloop issue).
Still no idea what can be done to remedy this situation.

No freezing at all in my 16 month old bullhead currently on stock rooted 7.1.2 with phasma kernel, no previous bootloops or hardware repair. I have never updated ota however and have run a custom ROM the majority of the time since I've had it, no idea if that would make a difference or not

The answer is simple:
2GB Ram + badly written ram hungry apps like messenger.
Best solution is to get another phone.Oh well...

Question Random reboots

Well, I had the 6 Pro for about 36 hours. It kept rebooting randomly, even after a factory reset, so it's going back for an exchange.
Has anyone else had this issue?

skyman631 said:
Well, I had the 6 Pro for about 36 hours. It kept rebooting randomly, even after a factory reset, so it's going back for an exchange.
Has anyone else had this issue?
Click to expand...
Click to collapse
No definately not, here the worst I have experienced is some app crashes, they probably aint android 12 ready, and some pretty big lag moments

I don't have any issues. Do you have the November update yet?

For some strange reason, I noticed exactly this aswell (one time, this morning). I was working out and my phone laid on the table, when I saw it lit up because it restarted for no reason.
I guess it's a software bug.
And no, there was no automatic system update - I checked, I'm still running the old version.

copong said:
I don't have any issues. Do you have the November update yet?
Click to expand...
Click to collapse
Is there a bugfix list of any sort about the most recent sytsem update?
I tried to find one, but as of now I have been unsuccessful.

No, nothing at all either. Mine also installed silently at some point. I recall a notification asked for a reboot yesterday morning.

No, not had one random reboot since I got it on Tuesday.

Nothing here either. Good luck!

copong said:
I don't have any issues. Do you have the November update yet?
Click to expand...
Click to collapse
I had the November update and all apps had been updated as well. It would freeze and then reboot.
I did a factory reset and did not restore any of my apps, just ran it with the factory apps, and it still did it. Since no one else is having the issue, I'm feeling confident it was a bad unit. I had the 128 gb version.
It's back to the pixel 5 for another week or so. I had to exchange that after I got it too because of a bad proximity sensor. Either I just have really bad luck or Google needs to tweak their quality control department.

Weird unexplainable OS crashes like that are usually due to faulty hardware, potentially RAM

If you're having issues, do yourself a favor and keep an itemized list (on your device, word doc on pc, somewhere) and notate the following for each occurrence:
-date / time
-the fault (self reboot, major lag, over heated, fast battery discharge, etc.)
-what you had to do to clear it (rebooted, closed app, powered off/on, etc.)
When talking with Google about a replacement, having THIS information ready to read off will make it extremely hard from them to give you any grief about you needing a warranty replacement.
An itemized list of faults is MUCH better evidence that you need a replacement than "well, it rebooted a few times last month"

copong said:
Weird unexplainable OS crashes like that are usually due to faulty hardware, potentially RAM
Click to expand...
Click to collapse
I am inclined to agree here, but my years of working with Windows and Android incl. rooting and using custom roms and kernels want to disagree here. There can be half a gazillion software based reasons for an OS crash, especially with a buggy release like Android 12. Not sure if you participated the beta, but it reminded me of Windows 11. There was a buggy beta build with about 100 bugs, they fixed 20, called it a day and released it. Now we new P6 owners can play beta testers Volume 2 for Google.
One very important thing here is also: Did you guys set up your phone "clean" or did you copy over your old phone by cable or did you use backup?
Any of these things can cause issues.
I, for example, used a cable to transfer all file and apps from my P4 XL to my P6 Pro. It's possible that this is the rootcause for some issues, or maybe it's not. Maybe there are even problems that occur only if you transfer your files from specific phone models to this one, you never know.

Morgrain said:
I am inclined to agree here, but my years of working with Windows and Android incl. rooting and using custom roms and kernels want to disagree here. There can be half a gazillion software based reasons for an OS crash, especially with a buggy release like Android 12. Not sure if you participated the beta, but it reminded me of Windows 11. There was a buggy beta build with about 100 bugs, they fixed 20, called it a day and released it. Now we new P6 owners can play beta testers Volume 2 for Google.
Click to expand...
Click to collapse
Sure, but the OP stated the crashes are happening right after a factory reset, and anecdotal evidence on this thread suggests it's not widespread. It does point to some sort of hardware problem.

I'm having exactly the same issue!
I got the phone today and booted it up for the first time. I selected my language and as soon as I pressed get started it froze, then got stuck in a bootloop. I fixed that by factory resetting from within recovery.
Once I'd gotten through the setup it crashed again when I clicked on the apps button in the optional setup. Because of this I factory reset and set the phone up for a third time.
Third time I got through setup with know issues but the phone freezes/reboots roughly once every two hours. I've been searching all day to see if anyone else has mentioned this issue.
I guess this phone is going in for replacement. Does anyone happen to know how long that takes/ if I'm going to be without a device for long?

They told me 3-5 business days to get a replacement. I expect mine early next week.

skyman631 said:
They told me 3-5 business days to get a replacement. I expect mine early next week.
Click to expand...
Click to collapse
Do you have to send the old device back first?

skyman631 said:
Well, I had the 6 Pro for about 36 hours. It kept rebooting randomly, even after a factory reset, so it's going back for an exchange.
Has anyone else had this issue?
Click to expand...
Click to collapse
I just had 3 random reboots today. Phone just laid on the side of my table on my laptop, doing nothing. It was in the span of probably ~10 minutes each reboot. A strange observation I made - now that I removed my phone from the back of my laptop and laid it directly on the table, no more reboots. Maybe it's a coincidence, maybe it has something to do with the magnets of my Laptop (has quite a lot inside). Not sure what to make of this. It kinda feels like a software buggy-thing, but it's odd that it sometimes just comees and goes. It also only appears to be in absolute idle. I had my phone working yesterday for about 12 hours, incl. using it constantly with navigation, and it never faltered for once. That's why I'd say it's a software thingy, if it had something to do with hardware, it would reboot/fail when under load. But it doesn't.
Had 4 total reboots as of now (had the phone since 27.10).
First reboot was yesterday (28.10) morning when working out, phone laid idle around, booted up.
And now again 3 reboots, morning, laid around, did nothing.

So I've had probably a dozen in two days. I take my phone out of my pocket and attempt a fingerprint unlock only to be told that my PIN is required after a restart. At first I wasn't sure if it was actually rebooting until last night. It prompted me for my pin and upon entering it, the screen locked up for about 20 seconds and it rebooted.
This morning I woke up and was yet again greeted with the "PIN required after restart" and less than 20 minutes later it was the same thing. Only once hav I witnessed the "G" boot animation, but everytime I see my UI loading. So I'm not sure if it's always a full reboot or some times it's just the UI crashing. Everything on my device is stock.

cloudraker said:
So I've had probably a dozen in two days. I take my phone out of my pocket and attempt a fingerprint unlock only to be told that my PIN is required after a restart. At first I wasn't sure if it was actually rebooting until last night. It prompted me for my pin and upon entering it, the screen locked up for about 20 seconds and it rebooted.
This morning I woke up and was yet again greeted with the "PIN required after restart" and less than 20 minutes later it was the same thing. Only once hav I witnessed the "G" boot animation, but everytime I see my UI loading. So I'm not sure if it's always a full reboot or some times it's just the UI crashing. Everything on my device is stock.
Click to expand...
Click to collapse
Did you transfer your old phone over with a cable, or backup, or did you start "fresh"?
Maybe we can narrow it down if it's software or hardware problem.

Morgrain said:
Did you transfer your old phone over with a cable, or backup, or did you start "fresh"?
Maybe we can narrow it down if it's software or hardware problem.
Click to expand...
Click to collapse
I did a partial transfer. I was coming from an iphone 12 so I transferred photos and contacts only. And I transferred via cable.