Related
So the other day the app Widgetsoid releases a "Completely rewritten" update for their sweet app. I was obviously excited to play with this and set about recreating all of my toggles. One toggle I have is to toggle the camera flash on/off which is very handy to have a widget for on the homescreen. Another one I use toggles the screen always on/off which is handy when reading long articles. So I was using the screen always on toggle as a reading light (as the camera LED can be overly bright) when, after some time, my phone locked up. Following my natural instinct I pulled the battery and powered it back on. When it came back on I noticed that the screen always on toggle was still in the "on" position though I believe (honestly can't remember for sure) that the screen was timing out as if it were off. Anyways I put this out of my mind and decided to use the flashlight toggle as the screen hadn't been quite as bright as I wanted. However, upon toggling the flashlight to "on" The toggle froze in mid activation. I could see that I had clicked it but the animation never finished and the flashlight never turned on. I gave it several minutes to sort itself out and when it didn't I did another battery pull thinking that would clear it up. Well it didn't. Upon the phone restarting I was greeted by "Tango has stopped responding". Then when I tried the flashlight toggle again I got "Gallery has stopped responding" which flashed up and disappeared too quickly for me to click on it. I tried opening the camera to no avail. "Gallery has stopped responding". So one bug led to another to another to another as bugs so often do. No biggie, I was planning on doing a factory reset soon anyways so I backed up my data and went ahead with that. Unfortunately, when I finished the setup and went back to the camera app it gave me the same error. (please note that I did not restore anything after the reset.) So I did another just for sanity's sake but no change. I went into the bootloader and into recovery, cleared the cache and then did another factory reset. Nada. I downloaded a flashlight app to see if it could tell me anything new, which it sort of did. "Cannot connect to camera", it said when I turned it on. In my search on this forum for a similar issue I came across a post to a different issue talking about how when an app uses the camera it might not have let go when it was finished which causes problems for other apps. This makes enough sense except that I figured the reset would have resolved that issue. Unless, of course, the problem lies in the hardware which I am desperately hoping someone will tell me is foolish.
I'm not really sure what to try next in my troubleshooting short of unlocking the bootloader and flashing either the stock back over it or another ROM. I would prefer to try other possible solutions before this. Correct me if I'm wrong but shouldn't the factory reset restore the system and stock apps to their default state? Almost literally bit for bit? If that is the case then that means the issue isn't with the system or the camera app and must fall to the camera hardware itself? I feel it is worth noting that on about the third factory reset, during the initial setup (quite literally on the first screen) a popup popped saying "Talk has stopped responding". Why the Talk app would stop responding due to some issue with the camera seems out of place. Though as I said and we all know, bugs have a way of spreading to the places you least expect.
Anyways any help, suggestions or questions would be greatly appreciated. This really has me stumped.
I guess the question it boils down to (besides the three I've already asked) is how can I do a full wipe/reset that will actually reset everything? Or is it that the camera is really hung and if so any possible fixes for that? Anyone see any bright red flags waving violently in the storm?
Thanks in advance for any help you can provide
patrioticparadox
I am running 4.1.1 on a Verizon Galaxy Nexus build JRO03O
patrioticparadox said:
So the other day the app Widgetsoid releases a "Completely rewritten" update for their sweet app. I was obviously excited to play with this and set about recreating all of my toggles. One toggle I have is to toggle the camera flash on/off which is very handy to have a widget for on the homescreen. Another one I use toggles the screen always on/off which is handy when reading long articles. So I was using the screen always on toggle as a reading light (as the camera LED can be overly bright) when, after some time, my phone locked up. Following my natural instinct I pulled the battery and powered it back on. When it came back on I noticed that the screen always on toggle was still in the "on" position though I believe (honestly can't remember for sure) that the screen was timing out as if it were off. Anyways I put this out of my mind and decided to use the flashlight toggle as the screen hadn't been quite as bright as I wanted. However, upon toggling the flashlight to "on" The toggle froze in mid activation. I could see that I had clicked it but the animation never finished and the flashlight never turned on. I gave it several minutes to sort itself out and when it didn't I did another battery pull thinking that would clear it up. Well it didn't. Upon the phone restarting I was greeted by "Tango has stopped responding". Then when I tried the flashlight toggle again I got "Gallery has stopped responding" which flashed up and disappeared too quickly for me to click on it. I tried opening the camera to no avail. "Gallery has stopped responding". So one bug led to another to another to another as bugs so often do. No biggie, I was planning on doing a factory reset soon anyways so I backed up my data and went ahead with that. Unfortunately, when I finished the setup and went back to the camera app it gave me the same error. (please note that I did not restore anything after the reset.) So I did another just for sanity's sake but no change. I went into the bootloader and into recovery, cleared the cache and then did another factory reset. Nada. I downloaded a flashlight app to see if it could tell me anything new, which it sort of did. "Cannot connect to camera", it said when I turned it on. In my search on this forum for a similar issue I came across a post to a different issue talking about how when an app uses the camera it might not have let go when it was finished which causes problems for other apps. This makes enough sense except that I figured the reset would have resolved that issue. Unless, of course, the problem lies in the hardware which I am desperately hoping someone will tell me is foolish.
I'm not really sure what to try next in my troubleshooting short of unlocking the bootloader and flashing either the stock back over it or another ROM. I would prefer to try other possible solutions before this. Correct me if I'm wrong but shouldn't the factory reset restore the system and stock apps to their default state? Almost literally bit for bit? If that is the case then that means the issue isn't with the system or the camera app and must fall to the camera hardware itself? I feel it is worth noting that on about the third factory reset, during the initial setup (quite literally on the first screen) a popup popped saying "Talk has stopped responding". Why the Talk app would stop responding due to some issue with the camera seems out of place. Though as I said and we all know, bugs have a way of spreading to the places you least expect.
Anyways any help, suggestions or questions would be greatly appreciated. This really has me stumped.
I guess the question it boils down to (besides the three I've already asked) is how can I do a full wipe/reset that will actually reset everything? Or is it that the camera is really hung and if so any possible fixes for that? Anyone see any bright red flags waving violently in the storm?
Thanks in advance for any help you can provide
patrioticparadox
I am running 4.1.1 on a Verizon Galaxy Nexus build JRO03O
Click to expand...
Click to collapse
I would honestly try to flash another ROM. its hard to tell what is exactly causing this prob but I highly highly highly doubt its hardware. Make sure you wipe data and dalvik a couple times and go to mounts and storage and wipe system too. Do those a couple times, I always do just to be sure it works. Then after that try to flash another ROM stock or custom doesnt matter. This will help a lot.
Just a recommendation, I use and LOVE Codename Android Rom. Very very fast and stable with a lot of features.
Anyways, post back when you wipe everything out and flash a new ROM on there and let me know the outcome.
nothing yet...
myboyblake said:
I would honestly try to flash another ROM. its hard to tell what is exactly causing this prob but I highly highly highly doubt its hardware.
Click to expand...
Click to collapse
Just finished flashing the 4.1.1 back and still the same issue (did all of the data wiping). I'll try a custom ROM now though I doubt its going to make any difference.
What in the world has got a hold of my camera?
No dice
"Unfortunately Talk has stopped responding" on the first screen. "Gallery has stopped responding" when trying to open Camera app.
So despite several wipes and two distinct ROM flashes (used PARANOIDANDROID the second time) my device is still acting up.
Please help me out people. What is causing this error that is lasting across ROM flashes? What can I try to resolve this issue?
Rewiped everything and reflashed PARANOIDANDROID (2.23) just to be sure and still the camera doesn't work
seems like perhaps the registers ended up in an odd state.. know this is for a different phone, but you might give it a shot..
http://www.droidforums.net/forum/dr...amera-app-stoped-working-wont-initialize.html
---------- Post added at 05:03 PM ---------- Previous post was at 04:46 PM ----------
Looks like OMAPFlash can do a full reset on all the camera registers from looking at:
./Targets/Definitions/definitions_omap4.txt
in the OMAPFlash zipfile..
It might be worth a shot..
Slide opultl
No dice... I assume you were referring to clearing the cache and data. I had tried this before but gave it another shot anyways. In case you meant the screenshot part, I did that too and the screenshot captures fine but still the camera does not function. Also holding down the volume down and power keys never shuts the phone off I assume that is device specific (though several seconds after the screenshot captured the screen did flash off then on very quickly). I have tried disabling Gallery and rebooting in the hopes that would free up the hardware. Failed.
I am uber stuck on this.
Why is this persisting across flashes and what can I try to resolve it?
edit: just noticed that the bottom of your post was more info and not a signature. I'll look into that. Ran out of "thanks" for today but I'll get you yours
Since it won't delete....
As an update: I have tried contacting both Verizon and Samsung about the issue. Both recommend returning the device under warranty (as was expected). This would be fine except that I LEARN NOTHING! If the Samsung techies have a protocol/enumeration/anything to discover and resolve the issue then so can I (potentially), which means the general public should have this knowledge too, right? WHAT IS MY NEXT STEP?
(still have not yet OMAP_Flash'ed as I haven't found SOLID documentation on this yet.) (Google searching led me somewhere but left me confused. Please post documentation or the correct link if you have it and thank you) I am open to trying anything. Understand that my bottom line is giving Asurion $50 USD. "I LOST my phone, send me a [new] one". Phone gets replaced and I get to trash the old one. Sweet for everyone right? Wrong.
I don't give two runny, stinky butt creams about the phone itself. Which is not entirely, or honestly, even close to true. I'd hate to see a Nexus that can be saved be completely obliterated. If its totally bricked (which its very hard to do to a Nexus) then go for it. Smash that ***** up! But if, like mine, its recoverable then you owe it to the developer to try to save it. This Galaxy Nexus SCH-I515 reminds me of my SCH-a950. I loved that phone and literally (because of a now EX girlfriend) BEAT THE LIVING SNOT OUT OF IT. I literally threw it at my front porch as hard as I could from a good 30 yards away and yet it survived. Not only did it survive, it thrived. Never failing me (even until I finally upgraded) despite the "wear and F'ing tear" I had inflicted upon it.
I have actually dropped my Nexus several times. I have a massively cracked screen that I would love to show you all, yet the screen still functions as if there were no crack. I can click on the "options" toggle that is in the bottom right corner of many apps as if there were not a MASSIVE chunk of screen missing there. The phone is quite amazing. And before anyone says "oh you dropped it, that could have to do with the errors in the camera", NO. The camera worked just fine until what I described above. Samsung has done quite a magnificent job with this device (and all of their hardware, {I own a 26" computer monitor that kicks ass too}) making it resilient to adversity.
Now please, help me out....
I am hesitant to try the OMAP_flash as I haven't found decent documentation. PLEASE PLEASE post a link.
As I said I can always "lose" the phone and get a new one through insurance. So I'm not worried about screwing the phone, I just want to LEARN about the issue at hand.
What do YOU think is causing this issue?
If someone could post a link to the relevant info about the OMAP_flash then I will be happy to go forward with it.
Aside from all this I am shocked at the relative dismissal of this thread. I am seeking information from experienced members who have expertise on this device and while many are available I have gotten no replies as of yet. (this is not to discount those who have replied as I am very grateful for those suggestions as well) Please take two minutes and give me your thoughts. I don't believe this issue is similar to any other posts here and if you do believe it, kindly point me in that direction.
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
Here's a link, sorry I didn't post soon - I don't check back here often..
patrioticparadox said:
(still have not yet OMAP_Flash'ed as I haven't found SOLID documentation on this yet.) (Google searching led me somewhere but left me confused. Please post documentation or the correct link if you have it and thank you) I am open to trying anything. Understand that my bottom line is giving Asurion $50 USD. "I LOST my phone, send me a [new] one". Phone gets replaced and I get to trash the old one. Sweet for everyone right? Wrong.
I don't give two runny, stinky butt creams about the phone itself. Which is not entirely, or honestly, even close to true. I'd hate to see a Nexus that can be saved be completely obliterated. If its totally bricked (which its very hard to do to a Nexus) then go for it. Smash that ***** up! But if, like mine, its recoverable then you owe it to the developer to try to save it. This Galaxy Nexus SCH-I515 reminds me of my SCH-a950. I loved that phone and literally (because of a now EX girlfriend) BEAT THE LIVING SNOT OUT OF IT. I literally threw it at my front porch as hard as I could from a good 30 yards away and yet it survived. Not only did it survive, it thrived. Never failing me (even until I finally upgraded) despite the "wear and F'ing tear" I had inflicted upon it.
I have actually dropped my Nexus several times. I have a massively cracked screen that I would love to show you all, yet the screen still functions as if there were no crack. I can click on the "options" toggle that is in the bottom right corner of many apps as if there were not a MASSIVE chunk of screen missing there. The phone is quite amazing. And before anyone says "oh you dropped it, that could have to do with the errors in the camera", NO. The camera worked just fine until what I described above. Samsung has done quite a magnificent job with this device (and all of their hardware, {I own a 26" computer monitor that kicks ass too}) making it resilient to adversity.
Now please, help me out....
I am hesitant to try the OMAP_flash as I haven't found decent documentation. PLEASE PLEASE post a link.
As I said I can always "lose" the phone and get a new one through insurance. So I'm not worried about screwing the phone, I just want to LEARN about the issue at hand.
What do YOU think is causing this issue?
If someone could post a link to the relevant info about the OMAP_flash then I will be happy to go forward with it.
Aside from all this I am shocked at the relative dismissal of this thread. I am seeking information from experienced members who have expertise on this device and while many are available I have gotten no replies as of yet. (this is not to discount those who have replied as I am very grateful for those suggestions as well) Please take two minutes and give me your thoughts. I don't believe this issue is similar to any other posts here and if you do believe it, kindly point me in that direction.
Click to expand...
Click to collapse
Jesus, will people stop talking about insurance fraud........
It's these kind of people that people in your country have to suffer higher insurance premiums, and the very same group of fraudsters are complaining about high insurance premiums..
Regarding OMAP flash:
1) Remove battery
2) Open device manager
3) Plug your phone to your PC/laptop
4) Right click on OMAP4460, go to properties
5) Drivers tab
6) Update drivers, direct to the OMAP flash folder
7) Run the .bat
8) Reflash a ROM just in case.
I don't think it going to do a reg reset for the camera by default..
This is from: Targets/Definitions/definitions_omap4.txt
CONTROL_CORE_PAD_CAM_GLOBALRESET 0x4A1000C0
It is pulled in and used by:
Targets/Configurations/configuration_omap4460_tuna_8g.txt
CONTROL_CORE_PAD_CAM_GLOBALRESET needs to set for the correct location -- I have not done any digging, so I don't know what the location is..
Just Found this -- https://github.com/omapconf/omapconf/wiki
omapconf can be used to read/write/modify any register from within Android..
Mach3.2 said:
Jesus, will people stop talking about insurance fraud........
It's these kind of people that people in your country have to suffer higher insurance premiums, and the very same group of fraudsters are complaining about high insurance premiums..
Regarding OMAP flash:
1) Remove battery
2) Open device manager
3) Plug your phone to your PC/laptop
4) Right click on OMAP4460, go to properties
5) Drivers tab
6) Update drivers, direct to the OMAP flash folder
7) Run the .bat
8) Reflash a ROM just in case.
Click to expand...
Click to collapse
Insurance fraud? Um get a life! That's not why their premiums are high you ass! They do it to make more money you jack knob. My company charges $65/yr with a $25 deductible with up to 5 claims a year! That's so much better than asurion. And they give you a piece of **** replacement. Is all about money not the customer...now please me nice. Great ideas come from working together not from being an asshat!
My wife's moto360 has recently stopped working. She woke up today and was greeted with a white screen that said "Unfortunately, Android Wear has stopped." Clicking Ok brings you to the watch face which hangs for a few seconds and then returns to this screen. During this period you cannot navigate the watch at all.
I have tried the following to resolve the issue but none of them have solved it.
1) Rebooted the watch by holding the button for 30 seconds.
2) Rebooting the phone.
3) Turning off bluetooth on the phone.
4) Uninstalling android wear.
5) Unpairing the watch and the phone.
Right now it looks like the watch is basically a brick. Has anyone else seen this? Is there a way to factory reset the watch without having to go through the menus on the watch (i.e. from a phone app for example).
I ended up fixing this. Basically I had to repeatedly mash the button on the side while trying to scroll the screen and dismissing the error prompt. Eventually I was able to get to the settings screen which then allowed me to select the reset (which factory resets the device).
Rekna said:
I ended up fixing this. Basically I had to repeatedly mash the button on the side while trying to scroll the screen and dismissing the error prompt. Eventually I was able to get to the settings screen which then allowed me to select the reset (which factory resets the device).
Click to expand...
Click to collapse
Clearing cache of Android wear app on phone helped. Restarted watch as a safe side measure. Everything fine now.
I have exactly the same problem now. But I can't solve it with you metod. Any clue of how can I fix this? Thank you!!!
Mine just started doing this as well. Tried just about everything I have seen on the internet so far to fix it and nothing has worked.
+1. Woke up and found the screen as OP described. I have tried everything except factory resetting the watch. I can't get into the menu long enough to do it. As soon as I hit the OK button the "Android Wear has stopped" screen pops back up within about 1 second. The GUI doesn't respond well enough for me to get to the factory reset.
update: Finally managed to get to the factory reset. The watch rebooted, but did not factory reset.
I gave up and am RMAing it.
for me it worked after lots of resets... but had to start all over again then.... dont know why this happened
Sent from my Nexus 9 using XDA Free mobile app
mrorange2108 said:
for me it worked after lots of resets... but had to start all over again then.... dont know why this happened
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I just bought my Moto 360 all excited to get my Android Fanboyism to the next level.
The first thing I did was try to update my Android Wear version.
And This is when I start getting the error..
It keeps saying google play services crashed.
google apps crashed..
Someone help..
I know it's a pain, but I ended up RMAing mine. I took my aftermarket band off and just sent it back in the original box with nothing else. They very quickly shipped me a refurb (which appeared to be new). It came in a brand new box with full accessories (charging cable/stand and band). A few days of inconvenience but well worth it. Got the new watch, updated to the latest and it's been running smooth.
i just got this message today!! i cannot interact with the GUI no matter what i tried.. i tried all possible steps except factory reset cause i can't get to it...
IM kinda SOL cause i bought this in the US when it launched and I am in Canada... : < sigh... this totally BLOWS
I tried several times to get to the reset... No luck, Motorola agreed to replace it for free.
Same here ... No luck in accessing settings for factory reset ... going to send it to RMA
Sent from my 1+1 using Tapatalk
impala454 said:
I know it's a pain, but I ended up RMAing mine. I took my aftermarket band off and just sent it back in the original box with nothing else. They very quickly shipped me a refurb (which appeared to be new). It came in a brand new box with full accessories (charging cable/stand and band). A few days of inconvenience but well worth it. Got the new watch, updated to the latest and it's been running smooth.
Click to expand...
Click to collapse
Just wanted to say thanks, because I've been experiencing a similar issue, and I just filled out the RMA for mine. It's been freezing and overheating so bad I have to take it off for awhile. I can live a few days without it.
I think you need to contact with the service center as soon as possible.
I had this same thing and the only solution was to RMA. Goty new 360 in less than a week.
So I got my new 360 in the mail, brand new in retail packaging, and even came with an additional charger. (YIPEE one for work!!) However it's started doing the same thing!! "Unfortunately Android wear has stopped wait, close" No matter how many times I hit close it reappears. I have to hard reset it every time. I took it off the charger 2.5 hours ago at 100% and its down to 52% already because of this. (Once again thankfully I have the extra charger now). I don't understand the issue. My boyfriend's 360 has the same software version and does not have any problem whatsoever. He's also able to change the colors while on the dock and neither of mine would do it (the old or the new). I have tried every color in the settings on my phone and it stays blue. I am beyond frustrated here. IDK what is going on!! Oh we both have Nexus 6 phones too, so I don't think it has to do with that.
I think I'm going to try flashing a different ROM to my phone, and factory resetting. Maybe **sigh** maybe that'll work...
rachelm920 said:
So I got my new 360 in the mail, brand new in retail packaging, and even came with an additional charger. (YIPEE one for work!!) However it's started doing the same thing!! "Unfortunately Android wear has stopped wait, close" No matter how many times I hit close it reappears. I have to hard reset it every time. I took it off the charger 2.5 hours ago at 100% and its down to 52% already because of this. (Once again thankfully I have the extra charger now). I don't understand the issue. My boyfriend's 360 has the same software version and does not have any problem whatsoever. He's also able to change the colors while on the dock and neither of mine would do it (the old or the new). I have tried every color in the settings on my phone and it stays blue. I am beyond frustrated here. IDK what is going on!! Oh we both have Nexus 6 phones too, so I don't think it has to do with that.
I think I'm going to try flashing a different ROM to my phone, and factory resetting. Maybe **sigh** maybe that'll work...
Click to expand...
Click to collapse
I'm running into the same thing. I just received my replacement last week and have received the error twice. I'm going to reset the watch tonight and see how things work out.
Sent from my LG-VS985 using XDA Free mobile app
OState said:
I'm running into the same thing. I just received my replacement last week and have received the error twice. I'm going to reset the watch tonight and see how things work out.
Sent from my LG-VS985 using XDA Free mobile app
Click to expand...
Click to collapse
So I'm pretty sure I narrowed my issue down to watchmaker. I asked my BF if he still uses the watchmaker watch faces and he said no. So I took it off, and started using the regular MOTO watch face. I have not had any errors in 2 weeks. I'm about to install a new ROM on my phone again today, so I may re-install it to see if the issues resurface. If they do I will be contacting the developer, as I have the paid version of the app.
rachelm920 said:
So I'm pretty sure I narrowed my issue down to watchmaker. I asked my BF if he still uses the watchmaker watch faces and he said no. So I took it off, and started using the regular MOTO watch face. I have not had any errors in 2 weeks. I'm about to install a new ROM on my phone again today, so I may re-install it to see if the issues resurface. If they do I will be contacting the developer, as I have the paid version of the app.
Click to expand...
Click to collapse
That very well could be the issue, I use watchmaker for all of my faces. I uninstalled it today. Hopefully I have the same result as you. Thanks!
Some background info.
I bought my pixel XL from the Google store and I believe it came with the 63L build out of the box. I have since made it a point to completely wipe and fastboot flash the latest image Everytime an update is release, right now I am on the 26U build. The only thing I have done to my phone (and these bugs happen before and after) is bootloader unlock and root.
The bugs.
Every once in a while, my volume controls will quit working. I notice it happen more if I cast to my Chromecast and play a song or video (seperate) on my device. I'll hit the volume button and literally nothing will happen. To fix this I usually have to turn the display off, wait a few seconds, wake it back up, then the controls work fine again. I do not believe it is a hardware issue because i can fix it Everytime it happens.
The second bug, probably the most annoying, is that my nav bar will become completely unresponsive occasionally while in landscape orientation. Say I'm watching a video on YouTube in full screen, if I swipe to pull out my nav bar and hit the home/recent/back button, nothing will happen. I will see the animation however no vibration (feedback) or a action occurs.
This happens in games, YouTube, web browsers, doesn't matter as long as my phone is in landscape mode. Also note that when this happens, my device refuses to rotate back to portrait. This leaves my only solution (same as the volume bug) to turn off the display, wait a few seconds, and then I back on. Sometimes, however, this don't even work, and I'll have to jump straight to settings from my lockscreen to force the phone to portrait where the functionality of the nav bar returns.
I've contacted google, they run me through the typical steps "delete cache, have you tried a reset, update to the latest software", but nothing fixes it. They have told me repetitively it's not a common problem and it's not a problem that's worth rma'ing over.
I've been discovering my pixel has many small issues that no one else has. Such as the horrible transfer speed explain in my earlier thread, these bugs above, refusing to charge when the device is off, etc.
Has anyone had similar problems?
@noidea24,
I've had none of those issues. In fact, my Pixel XL has been flawless.
Not good. I guess I'm going to try and force a RMA.
noidea24 said:
I've contacted google, they run me through the typical steps "delete cache, have you tried a reset, update to the latest software", but nothing fixes it. They have told me repetitively it's not a common problem and it's not a problem that's worth rma'ing over.
Click to expand...
Click to collapse
Sorry to nit, but when I read the statement above I can't help but wonder if you actually did a factory reset. Reason I say that is you stated "have you tried a reset" and you didn't explicitly state that you did.
I kind of doubt the responsiveness stuff you're referring to is hardware related, it's probably software.
Whether or not a rogue app is affecting your device or a root app is impossible to determine without doing a factory reset and carefully adding one app/change at a time until the problem comes back. It's a PITA but that's what I'd do first to rule out hardware, and I'd simply run email and messaging apps unrooted for at least 24 hours to rule out hardware issues before I start loading up my favorite apps.
muzzy996 said:
Sorry to nit, but when I read the statement above I can't help but wonder if you actually did a factory reset. Reason I say that is you stated "have you tried a reset" and you didn't explicitly state that you did.
I kind of doubt the responsiveness stuff you're referring to is hardware related, it's probably software.
Whether or not a rogue app is affecting your device or a root app is impossible to determine without doing a factory reset and carefully adding one app/change at a time until the problem comes back. It's a PITA but that's what I'd do first to rule out hardware, and I'd simply run email and messaging apps unrooted for at least 24 hours to rule out hardware issues before I start loading up my favorite apps.
Click to expand...
Click to collapse
A factory reset is far from a pain in the ass, and yes, i have done it many times. the only things that makes it suck is when i have to transfer files back to my device because (as mentioned) i have terrible transfer speed from pc to device.
i have literally done everything i can to make this devices worth the price, and things are only getting worse. Since the post (later that night) i factory flashed once again, and re locked the bootloader. No root, No extra apps, hell, the only apps i had on my phone to begin with were facebook messenger, and that pixel car racer, i dont use anything else. ive had an even worse bug come in where my phone completely freezes when opening google camera and swiping to the video section. ill have to hold power until it force resets.
ive been with xda since my Motorola droid, Ive built roms for the community for my lg g2 and my nexus 6. hell, i even built kernels for my 5x (not public), so im a little past your average user complaining about some things that dont work due to user error. these are legitimate device flaws and malfunctions, and i was simply asking if anyone else has experienced them. and since it seems no one has, i have deemed my device faulty. now i have to come up with $600 for a service hold to get it replaced.
My experience with Googles first official flag ship has been pathetic, and im hoping that this replacement device i get (eventually) will persuade me not to go back to my 6p.
Well if that's the case then yeah I hope a replacement device will solve your issues. Sounds like it will.
Didn't mean to rile you up, just looking for clarity.
Good luck!
This is more of a "what the hell happened" post, more than it is a question or answer.
So i seen this happening to the normal pixels, but havent seen a report for the XL. I was at work when i decided to take the latest update during lunch. after eating i glimpse at my phone to see "update failed", i thought this was odd because as i mentioned earlier, only the smaller variants were receiving this problem. I paid it no attention and just thought to myself "ill factory flash the image later". Break time was over and it was time for me to get to work, i threw my (wired) headset in and played some music to find that my volume at max was only playing at about a quarter of what it usually does (weird). didnt have time to mess with it so i dealt with the abnormally low volume. it wasnt until i got off i went to play a video on facebook, i realized i didnt have media volume!!
After playing around for a second, i found out my pixel had lost ALL OUTPUT as far as noise was concerned. no ringtones, notifications, media, calls, nothing. THought it could have been a rogue app hogging something, so i uninstalled almost everything. I tried restarting, i tried clearing cache, nothing worked. i was messing around with source and compiled a rom for the pixel the other day and said "why not try flashing it". flashed it, still no volume. at this point i grabbed the latest image and allowed it to wipe and flash everything. i now have my volume back. anyone know what could have went wrong?
My wife's small Pixel lost all sound after an ota. It was a verizon phone with bootloader unlocked and rooted, so I was surprised it even took the update on its own. I tried flashing older images, the beta, safe mode, and everything I could think of. Google exchanged it (which was a win because they sent her a google store pixel, not another verizon one)
noidea24 said:
This is more of a "what the hell happened" post, more than it is a question or answer.
So i seen this happening to the normal pixels, but havent seen a report for the XL. I was at work when i decided to take the latest update during lunch. after eating i glimpse at my phone to see "update failed", i thought this was odd because as i mentioned earlier, only the smaller variants were receiving this problem. I paid it no attention and just thought to myself "ill factory flash the image later". Break time was over and it was time for me to get to work, i threw my (wired) headset in and played some music to find that my volume at max was only playing at about a quarter of what it usually does (weird). didnt have time to mess with it so i dealt with the abnormally low volume. it wasnt until i got off i went to play a video on facebook, i realized i didnt have media volume!!
After playing around for a second, i found out my pixel had lost ALL OUTPUT as far as noise was concerned. no ringtones, notifications, media, calls, nothing. THought it could have been a rogue app hogging something, so i uninstalled almost everything. I tried restarting, i tried clearing cache, nothing worked. i was messing around with source and compiled a rom for the pixel the other day and said "why not try flashing it". flashed it, still no volume. at this point i grabbed the latest image and allowed it to wipe and flash everything. i now have my volume back. anyone know what could have went wrong?
Click to expand...
Click to collapse
At least you are knowledgeable enough that you were able to flash the factory image and get your phone working again. Since the Pixel is being marketed to a more mainstream crowd a lot of people likely would have had to RMA the phone. Pixel support will never tell you to unlock the bootloader and flash the factory image. As for what went wrong, something was clearly corrupted when the OTA failed so it must have partially installed before things went wrong. I've had problems like that when flashing custom Roms and the only remedy I've ever found was wiping everything and doing a clean install.
Updated successfully to July security patch yesterday (OTA), no issues... it's smooth
Sent from my Pixel XL using Tapatalk
Just bumping up this thread once more because it happened again. Took august update, rebooted, no media sound.
Calls work, ringtones, all bt and wired sounds work, but no main speaker media sound.
Cleared cache and dalvik, uninstalled any app that wasn't factory, done everything besides a factory reset.
Can't really do the factory reset right now, as I'm not at home, and I'm not comfortable being in a situation where my PC isn't accessible (in case it ****s up).
Any ideas?
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.