Related
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
Hi there,
Now I've come across a few threads that mention reboot issues. However mine seem to be almost unique.
The biggest thread I came across was more along the lines of overheating.
Everything on my phone functions normally. GPRS / 3G, WiFi, Bluetooth (I think, never use it!).
First issue: GPS takes FOREVER to lock. A good ten minutes, at least. Whether I sit and wait for it to lock or just start driving. Makes no difference.
GPS eventually locks. A good 20 minutes (give or take a few minutes) in, and bang. Reboot.
My first thought was the radio. I was running the very latest one (in the radio thread). I downgraded. I tried 4 older radio's. Each previous one improving the stability. However all except the latest only keep the GPS working for around 20 minutes after locking.
This morning I flashed the oldest radio (first post of the radio thread, oldest one there).
Results in my testing on the way home are quite different. After 20ish minutes I didn't get a boot loop. NDrive went crazy, and stopped navigating. I restarted the app and the GPS refused to lock.
I had installed CatLog some time ago. In my early experimenting, I ran the logging while driving. It seemed to have prevented a reboot but instead created circumstances like above where the GPS stopped working mid-navigating.
I'm running Pays DHD Rom. When navigating its running on battery alone. Temps don't go above 35 degrees Celcius. My phone is rooted, s-off'd as well.
Does anyone have any suggestions?
Short of un-rooting, finding a stock like 2.2 ROM and turning S-on and sending it back to the shop I bought it from, I don't know what to do
Thanks.
In my personal experience all GPS receivers loose sensitivity over time. Some go off faster other stay fine for a few years. If it takes that long for your GPS receiver to lock it is most likely caused by lost sensitivity and no ROM will fix this. The very last thing you can try is to download one of the GPS manager apps and perform a full wipe of the GPS data followed by GPS cold start. It should lock within 2 minutes. Otherwise install a stock ROM and apply for warranty repair.
Sent from my HTC Desire using XDA App
Agreed. Definitely not the rom. I installed cm7 and damn its a great rom but the problem persists.
I downloaded one of those GPS apps. When soft resetting it rebooted my phone sad days.
Sent from my HTC Desire using XDA App
So I've pretty much given up.
Tomorrow its going back to where I've gotten it from.
After downloading the stock RUU (first Eclair and then Froyo. Lets just say Eclair didn't like my phone at all) and getting it on the phone, I'm finished.
The moment I turn on GPS... instant reboot!
If you ever have troubles like this, don't waste your time, just take it back!
check out here
Hi,
First post, feels like I'm a little late to the party. I have a gio which initially had gingerbread 2.3.3. The phone is unlocked, and rooted, and has the clock work mod recovery patch on it. I have tried a couple of different versions of gingerbread, and am now running ice cream sandwich: kernel 2.6.35-7-galaxyics, CyanogenMod version build 9-20120610-UNOFFICIAL-gio, build number IMM76L.
Firmware-wise, it's mostly good, but I'm having a couple of weird issues:
1. The screen goes black on me periodically, and won't come back without pushing the on/off button. This is happening every 30 to 60 seconds of use.
2. The wifi crashes, a lot. With the older gingerbread I would get the word "error" under wifi in settings, and couldn't turn it back on. I would enter *#*#526#*#* to bring it back, but every 5 minutes seems a little excessive.
With the newer ICS, I've noticed I can play on a wifi link all day long without issue, but as soon as I set the phone down for a couple of minutes, wifi stops working. If I go into settings, wifi is on, but there's no connection. If I turn wifi off and back on, it comes back to life.
I guess, I'm wondering if these indicate more of a hardware issue than a software issue. It's hard to ask for support from my carrier, given I'm using an unlocked phone bought from a 3rd party, and have no contract.
zapstrap said:
With the newer ICS, I've noticed I can play on a wifi link all day long without issue, but as soon as I set the phone down for a couple of minutes, wifi stops working. If I go into settings, wifi is on, but there's no connection. If I turn wifi off and back on, it's comes back to life
Click to expand...
Click to collapse
I got that problem to sometime ,
And welcome !
send from my galaxy gio with paranoidAndroid Rom
Errors that you describe has a lot of people
The team is now working on ICS AOSP so be patient wait a little meringue as soon
And yet you propose to install something else that any CM
In total there is this quite a bit
update
A couple of things I've noticed:
1. The resetting wifi problem does not happen when the phone is plugged into USB.
2. The screen turning off happens frequently, but about 1/2 of the time, the screen will turn off for 1-2 seconds, then come back on at full brightness; the rest of the time, it will not come back on at all, but still responds to being tapped. The only way to get it back is to push the on/off button on the side twice, but then the screen is locked, and has to be swiped to unlock.
I have picked up a second phone, a 5660M running stock gingerbread 2.3.4, unlocked and rooted; not experiencing either of the two above issues (and the camera preview works). If I could take the 5660 back to stock at this point, I would prefer that, as the phone is not usable with these problems. Is there a stock rom available for this phone somewhere?
update part II
Hmm, after the phone showed up with 2.3.3 claiming to be a gt-s5660, and was sold as such, I finally put 1 & 1 together. I checked under the battery, it's a gt-s5660m. That explains probably all of the problems I've been having. Pity there's no ICS build for the M version of the phone.
You can use cm9 ics on your M model, it only changes your device id to gt-s5660, just dont flash roms with ODIN except roms for the M model.
Flashing from recovery wont install a baseband, with ODIN it mostly does, so the only roms you cant flash are old roms that still need odin like gioprio.
Flashable .zips are fine, all of them
Sent from my GT-S5660 using xda premium
The wifi problem might be hardware, m8
I don't know, as my gio has some strange problems as well and I've had ICS, Adrenaline ROMs, everything, and the problems still persist. At least they're not really bad to handle in everyday use but still, they're annoying.
Go to wifi settings - advanced - sleep policy- never
Sent from my GT-S5660 using xda premium
update part III
Since going back to GINGERBREAD.MUGKG3 / 2.3.4 for the GT-S5660M, the wifi crashing and screen blanking behaviours have completely stopped. After two days of running, wifi has not shut-off unexpectedly even once, and the screen does not blank any more at all.
The gps works now; it was not before. It used to sit for up to an hour under a clear open sky, day or night, and never acquire a single satellite. Now it picks them up within 30-60 seconds, though a full lock does take a couple of minutes.
The phone previously always indicated it was roaming, and would frequently refuse to send texts or make calls. I would get full bars for signal strength, but no connectivity.
I even got hold of the fm radio app, which was not included with the M version of the 5660, and manually installed it (phone must be rooted, and file system must be mounted read/write). It works too; a nice bonus.
The camera works, but is a bit flaky, requiring an occasional restart to get it going.
Probably the biggest headache, after flashing back to the 5660M version, was that the phone locked itself again, and wouldn't work on my network. I dumped bml5 page and searched out the unlock code. I had some trouble with this. The search string to get close to the code is supposed to be a sequence of twenty 0x00 bytes, one 0x05 byte, and fourteen 0xff bytes. The 0xff bytes weren't there, and it took a while for me to clue in that if I searched on the twenty 0x00, and single 0x05 byte sequence, I could still pull it out. I got it, and wrote it down in case this happens again.
sms issue
Still ticking along with the GT-S5660M; mostly it's all working nicely. I have one question though: I recently ran out of memory for storing SMS messages. It looks like the texting app in the phone wants to put everything on the SIM card rather than on the SD card, but there's no option for moving the default storage location for messages. Is there a simple way to do this? The phone is unlocked & rooted, but does not have the ext2 file system on it.
What's the IC? I checked under the battery to confirm mine is a Canada model, and it is.
But my IC is GT-S5660L
Model: GT-S5660M
IC: GT-S5660L
buremily You
Peteragent5 said:
What's the IC? I checked under the battery to confirm mine is a Canada model, and it is.
But my IC is GT-S5660L
Model: GT-S5660M
IC: GT-S5660L
Click to expand...
Click to collapse
Same, GTS5660L ... why do you ask?
Hey all,
For a while now ive noticed my phone tends to reboot itself randomly(r800a), usually when waking up, ie, using the slider on the lockscreen after its been asleep.
Outside the house i would be lucky to get an uptime of 5+h, however i have been home sick this week and the phone has been connected to wifi the entire time and ive noticed... no reboots.
I get these reboots on CM9, AOKP, and modded stock roms, whilst hunting for the cause in the last couple of months I have steadily dialed back the use of oc/root and modded firmware altogether, i am currently running bone stock .42 for the r800a and have been for a couple of weeks hoping i could pin down the cause.
Does anyone have any idea what steps I could take to fix this issue, it seems to be related to external data use, a straight firmware flash has not fixed it, is there any more advanced methods i could use to potentially fix the problem?
I've been with this problem since phone was new, I'm in Mexico City in Telcel network, sent my phone several times for the same problem and Sony has never replaced the device, they say it's fine, I 've also noticed the problem is when accessing the carrier' s network, I'm testing gin2jellybean and problems seem to stop, at least for a while.
Hmm, thanks for the reply, at least im not alone with the issue, its been bugging me for a while, I might just keep trying different roms and if im lucky one will fix it, considering prying it open to check the antenna connections as remote as that possibility would probably be.
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