I have enabled jump to camera with double power button click. Ever since the may update the camera launches randomly when I try and shut my phone off.
Anyone else seeing this? Fix?
I've been noticing the same behavior. Happens intermittently with no real reason. No noticeable physical difference with the power button either. Still clicks just fine. Definitely seems like a software bug of sorts.
Itachisasuke said:
I've been noticing the same behavior. Happens intermittently with no real reason. No noticeable physical difference with the power button either. Still clicks just fine. Definitely seems like a software bug of sorts.
Click to expand...
Click to collapse
Google RMAed my phone for it (new one comes tomorrow) so I'll let you know if it persists across a hardware swap.
madscribblerz said:
Google RMAed my phone for it (new one comes tomorrow) so I'll let you know if it persists across a hardware swap.
Click to expand...
Click to collapse
Thanks for the reply. Good to know.
Two friends that also have this issue after the May update so I'm hoping that it's software but it's good to know we can get a replacement if it's not.
Any updates on the new device are appreciated.
Itachisasuke said:
Thanks for the reply. Good to know.
Two friends that also have this issue after the May update so I'm hoping that it's software but it's good to know we can get a replacement if it's not.
Any updates on the new device are appreciated.
Click to expand...
Click to collapse
So far no issues on new hardware, but was intermittent and unpredictable so not entirely certain issue has resolved. Given multiple reports its unlikely hardware.
I did do something slightly differently on this phone though. On my old I went from OPM2 to OPM4 with the June release. This time I stayed with OPM2. Only manually wrote June update, rest was OTA.
Will provide updates as time passes or if I see it again.
Itachisasuke said:
Thanks for the reply. Good to know.
Two friends that also have this issue after the May update so I'm hoping that it's software but it's good to know we can get a replacement if it's not.
Any updates on the new device are appreciated.
Click to expand...
Click to collapse
Promised update - since switching to the rma unit I've not seen this issue in any form. It could have been moving over to a clean userdata but otherwise the software and firmware were identical between my old and new phone.
Edit (1 Aug 2018): After one day of the factory reset, the problem started happening again but a lot less frequently than it was before the factory reset. After two days, the problem is back just as bad as it was before I did the reset. I'm certain this is a software problem because of this but it makes no sense to me.
----------------------
I had the same problem with my Pixel 2 XL and had an experience I wanted to share.
I did a factory reset on my phone and restored all of my apps and data from backup except for my device settings. The problem remained for just a few minutes after my phone booted after factory resetting it, but after that, I've never had the problem since.
I'm not too sure if this is a permanent fix yet, but it seems a factory reset solved the issue for me. Fingers crossed it lasts.
exactly the same issue. But i think this is definitely a hardware problem, due to a design defect or quality control. so replace with new machine would not fix this entirely.
hope this could be fixed on pixel 3
The same issue have been happening with my phone , was hoping someone had a solution. It had never been an issue until recently
I had this issue, Google just did an RMA without much question. Just had to check in Safe Mode. I suspect a slight quality issue with the button mechanism registering double clicks despite it only feeling like one click.
pemz82 said:
I had this issue, Google just did an RMA without much question. Just had to check in Safe Mode. I suspect a slight quality issue with the button mechanism registering double clicks despite it only feeling like one click.
Click to expand...
Click to collapse
Started a chat today with them, I got it through the Google Store and they are going to RMA my device as well. This is my second Google phone that had issues after a year. As much as I like the google phone . I can't say I trust it's QC . Nexus 6p was a useless brick after the power issue and bootloop and now this with the Pixel 2
I've also just started having this problem. I'm going to try a full wipe when Android 10 gets released on the 3rd. If that doesn't work, guess I'll be RMAing my 3rd phone.
Related
A white line appeared down the middle of the screen last night. Its going back...
Bummer, I hate it when a new toy gets taken away so quickly like that...
Still, sadly there will always be problems with any hardware to a certain extent
and its worthy of mention that this is the only report I have heard so far so hopefully it is an isolated event
Gutted for you mate!
Hope they will pay... Most of the time when it's about the screen, you have to pay yourself:S
sorry to hear that really! hopefully you took out insurance but it will be covered by manufacturer warranty i am sure. hopefully it will just need a new ribbon and not a new screen. by what you described it may only be the ribbon. no issues with mine yet touch wood!
Chris Proud said:
A white line appeared down the middle of the screen last night. Its going back...
Click to expand...
Click to collapse
My unit screen is so unresponsive, Only got it today tried a few tweaks and factory reset makes no difference. Crashing and hanging for long periods also. No 3rd party software installed, No sync done. My unit is going back today just packaged it up.
The phone is so slick though best HTC handset to date.
xxnoelziexx said:
My unit screen is so unresponsive, Only got it today tried a few tweaks and factory reset makes no difference. Crashing and hanging for long periods also. No 3rd party software installed, No sync done. My unit is going back today just packaged it up.
The phone is so slick though best HTC handset to date.
Click to expand...
Click to collapse
have you done a hard reset? i would recommend it just to avoid you making a hasty decision! can't believe that as mine is spot on!
shingers5 said:
have you done a hard reset? i would recommend it just to avoid you making a hasty decision! can't believe that as mine is spot on!
Click to expand...
Click to collapse
Hard reset makes no difference with this unit. Back to my Nokia E75 for a few days till I get a replacement or I may just grab a different phone. Just tested a friends Touch Pro 2 and his is fine so it is the unit. It is a very nice phone fastest wm phone out. I just wish they would sort the Touch Flow out as it is still laggy in spots. Sure next firmware will sort it out.
Mine did similar right after the intial sync. I did a battey pull and its been working good ever since. My "s" key doesnt register unless pressed hard. Also noticed no weather in calender and when using the keyboard to type it doesnt auto capitalize but it does with the virtual keyboard
xxnoelziexx said:
Hard reset makes no difference with this unit. Back to my Nokia E75 for a few days till I get a replacement or I may just grab a different phone. Just tested a friends Touch Pro 2 and his is fine so it is the unit. It is a very nice phone fastest wm phone out. I just wish they would sort the Touch Flow out as it is still laggy in spots. Sure next firmware will sort it out.
Click to expand...
Click to collapse
no issues wid touchflo and no lags at all! i have tweaked mine and added a few enhancements and no problem. shame if you changed phones as some real good times to come on here with this phone
Bummer, hopefully the manufacturer warranty will fix or replace it ASAP!
I'm sure they will... unless it's visible, physical damage
Hey does anyone know or tried hdtweak? Maybe it will work on our TP2
Wow..guess I"m lucky.. I experience none of these flaws at all on my device
michaelra said:
Wow..guess I"m lucky.. I experience none of these flaws at all on my device
Click to expand...
Click to collapse
I hope most people wont experience any problems
Just an update my new unit will be delivered tomorrow. Had super serivce so far from handtech just hope my new unit will be fine (I am sure it will be) Fingers crossed.
I can't wait to play around with the unit again. Only sent it back yesterday it was tested and they confirmed it was faulty.
Yesterday my Galaxy S6 Edge got pretty hot and started acting strange. My back button started to act like it was the recents button where it would open my multi-tasking list. I set it in front of a fan and when it cooled down it started working right. Updated to 5.1.1 this morning (T-mobile) and then about an hour ago the phone got hot again and started the same behavior as described above. Is this some kind of manufacturer's defect or a software problem? Has it happened to anyone else?
If you got the update through ota it can be assumed your stock non root, but you may have a chuck load of apps.
You may have an app conflict causing the overheating issue.
Try disabling or un installing the downloaded apps to see if the condition stops.
If this isn't the case then the phone may be buggy and a replacement may be in order.
Pp.
Yeah sorry, I'm stock not rooted. I'm in the process of clearing out useless apps. I'll probably factory reset too since there's nothing too important that i'll lose. I'm wondering if using ccleaner may have caused the issue.
EDIT: Factory reset.. no luck. My capacitive back button is still acting like the capacitive recents button.
Any luck with your button issue?
Pp.
PanchoPlanet said:
Any luck with your button issue?
Pp.
Click to expand...
Click to collapse
Nope, tried to odin the tmobile 5.1.1 file found Here and that did not work. Contacted customer support and they said that my phone had the wrong baseband version (G925TUVU2COF6 ) and the tmobile release version was (G925TUVU1AOF6). Got transferred to tech support who shipped me out a replacement unit. I'm actually in the process of charging up the new phone and getting everything swapped over.
Side question: Is there any way to tell if the unit tmobile sent me is brand new or a refurb? I'm not really worried about it since the phones are so new anyways.
Your phone could be new if it was in a Samsung box, if it came with a generic plane box it may be a returned unit and there should be a sticker indicating refurbished .
A refurb could be hard to spot, and the only sure way to tell would be by DNA testing.
Lol.
Good luck with your fresh phone and don't mess it up, at present no root, no recovery, so chill and enjoy stock / no-root for a little while.
Stay away from ccleaner, I use Zoner anti virus never had any issues.
Pp.
i had the same exact problem, i made a soft reset but notthing worked. Also i tryed to verify if the back button was hardware broken and i thik this is the case. As i can tell those capacitives touch may measure the resistivity with one analog input. This means that if the resistence is chaning for any reason the back button will be read as the folder button. This is so annoyng for a phone of this cost. I really am upset about that. Do you managed to have your phone back?
Hi all,
Just got news of the marshmallow being available to my LG G4 (H815). I was aware of the update having been rolled out to Poland and Korea before so I thought it was a safe bet.
I plugged in my phone, started the LG Bridge software which prompted me with the update. I went on and downloaded it, which happened without any issues.
However, when the process was over and my phone restarted, it went through the usual "app optimization" window and after that started boot-looping. I have the initial audio cue from LG playing every few minutes, with the same "app optimization" for 12 apps (when the first time it was around 90).
I initially left it for a while (5-10min) before i started losing patience. I removed the battery but that didn't change anything.
I initiated the Recovery mode, but it prompted me with a "factory reset" question, which I didn't feel like doing before having tried anything else.
My phone is not rooted and was running Android 5.1, the LG variant. I never fiddled with this phone.
Has anyone else experienced issues updating? Do you have any suggestions on what I can do to recover my data? Because for me, that's mostly what I'm concerned of.
Thanks!
Edit: In addition, I'm facing a new problem... while boot-looping, my phone is actually draining more energy from the battery than my charger can provide (yet, it's a 1,8A @ 5V).
It's now down to 10%, which I've been able to verify by removing the battery thus shutting down the phone, putting the battery back inside, and plugging the phone in while being off. However, this automatically turns on the phone, so it briefly displays the battery charging animation before booting... My phone was at 100% during the Marshmallow update.
Which S/N (serial number on your box) do you have? 505 and 506 are known for this issues..
appileh said:
Which S/N (serial number on your box) do you have? 505 and 506 are known for this issues..
Click to expand...
Click to collapse
Wow, wasn't aware of that... it turns out it's a 505...
Wh!teSh4dow said:
Wow, wasn't aware of that... it turns out it's a 505...
Click to expand...
Click to collapse
yes it can be a issue of the 505.. Not to scare you or anybody else (there are people here that are crying and closing threads because i talk things like this.) But 505 is a known issue that some of the motherboards have defects. I hope you can fix it for yourself or call the cheap manufacturer LG..
appileh said:
yes it can be a issue of the 505.. Not to scare you or anybody else (there are people here that are crying and closing threads because i talk things like this.) But 505 is a known issue that some of the motherboards have defects. I hope you can fix it for yourself or call the cheap manufacturer LG..
Click to expand...
Click to collapse
Are you aware of this being a reason for replacement units to be issued? I didn't buy it through LG directly but through amazon, so I'll get in touch with them, but just wanted to know if you've had any experience or know of anything regarding this. And thanks for letting me know.
Wh!teSh4dow said:
Are you aware of this being a reason for replacement units to be issued? I didn't buy it through LG directly but through amazon, so I'll get in touch with them, but just wanted to know if you've had any experience or know of anything regarding this. And thanks for letting me know.
Click to expand...
Click to collapse
Np chief. They will fix your phone, just say it is in a bootloop after LG's official update. Call Amazon or LG itself to fixe this problem. (you mentioned you didnt root anything etc so you are good to go boss).
appileh said:
Np chief. They will fix your phone, just say it is in a bootloop after LG's official update. Call Amazon or LG itself to fixe this problem. (you mentioned you didnt root anything etc so you are good to go boss).
Click to expand...
Click to collapse
I figured, they would just try to restore my device and send it back to me, so I tried it and it worked. I'm still disapointed for two reasons:
- I still lost valuable data which I can't retrieve any more
- I'm still stuck with my device which could very well be prone to other issues in the future (any future update ?)
There are issues with this phone because i had 3 Rma's because of motherboard and dead pixels. My wife has also dead pixel and has version 506. Just use your phone, Marshmallow update is out so maybe they changed something in the system to stabilize the motherboard.
Verstuurd vanaf mijn LG-D855 met Tapatalk
Has anybody noticed an intermittently unresponsive touch screen after the latest OTA? I haven't had any problems since they fixed the original problem way back when.
It goes completely unresponsive and I have to reboot several times to get it to work until it stops again. I'm assuming this is a hardware issue on my end since I haven't heard anybody else talking about it but I just wanted to make sure.
I think I will try a different kernel and/or ROM to see what that does.
Hi,
I have the same issue here, it started a few days ago for me. Up till today I just had to reboot but now it seems completely blocked... I will try again later but this is becoming really annoying
.
I had the same happen to me about 2 months ago. Happened around an OTA.
In the process of trying to replace it. Tried flashing recent factor images but no luck
I've had exactly the same issue as described. Hardware buttons work fine, but no response to touch. Started intermittently and got progressively worse until there is no touch response at all.
The first time this happened, I contacted google support, and they arranged a replacement. That was in June.
The replacement device has now developed the same fault, which progressed in the same way as the first device.
Just got off of the phone with Google support, and my second replacement is now on it's way.
Fingers crossed for 3rd time lucky.
Same thing...
This has started to happen to me -_- replacement is on its way. Doesn't seem like the problem is being fixed more or less just addressed...
DG android fanboy said:
This has started to happen to me -_- replacement is on its way. Doesn't seem like the problem is being fixed more or less just addressed...
Click to expand...
Click to collapse
Sadly they don't think the Pixel c is important enough but least the RMA is straight forward.
Sent from my Pixel C using Tapatalk
Hertshammer said:
I've had exactly the same issue as described. Hardware buttons work fine, but no response to touch. Started intermittently and got progressively worse until there is no touch response at all.
The first time this happened, I contacted google support, and they arranged a replacement....
Click to expand...
Click to collapse
Ditto here. Just received "refurbished" (was actually new--factory wrap, unopened) replacement unit two days ago. Had my initial Pixel C about 10 months with zero issues. Then, a couple weeks ago, touch responsive became spotty, typically cured by putting tablet to sleep and waking. Progressively got worse until no touch response whatsoever. Physical buttons worked fine. Factory reset, tried flashing prior OS versions, etc. Nothing worked. Stock / unrooted.
But, Google customer service was very cool about the replacement.
How were everyone able to contact Google Support? I have the same problems with the touch screen, but am not able to find a way to contact Google about it. I had bought mine straight from Google Store.
DukyY said:
How were everyone able to contact Google Support? I have the same problems with the touch screen, but am not able to find a way to contact Google about it. I had bought mine straight from Google Store.
Click to expand...
Click to collapse
Top right hand corner, "contact Google" > https://support.google.com/store/troubleshooter/3070579?hl=en
I had the same problem after an OTA Security update yesterday. Booting into recovery and erasing cache fixed it for some time, then problem reappeared. Can be fixed by repeating the procedure. Seems a software problem to me.
Same problem. I can't even get it unlocked now as nothing registers.
Sent from my ZTE A2017U using XDA-Developers Legacy app
I guess this is just a hardware issue because it happened to me twice and both times Google provided me with a new tablet. The only advice I can give you is to contact the support because in my opinion nothing can be done at our individual level...
Will they still replace out of warranty? Purchased Dec 21, 15. Tablet had been flawless until yesterday.
Sent from my ZTE A2017U using XDA-Developers Legacy app
Hmmm I highly doubt it, but you can give it a try. Did you try to factory reset yet, just in case?
Yes, initiallyit was slightly working as of Wednesday and I factory reset. No change, but it registers no touches now so I can't even unlock it.
Google is getting me a replacement so I thank them greatly for that.
Sent from my ZTE A2017U using XDA-Developers Legacy app
yeah, google did the right thing by shipping a replacement, bill3508. i just hope whatever hit your device is isolated.
2 issues I've come across lately with my Pixel C tablet:
1. Touchscreen unresponsive
The tablet has lost touchscreen responsiveness. When I touch the screen, nothing happens. Buttons pressing ok - it works.
I have connected the device to the PC by Vysor app. Using a mouse from PC I can manage. I tried diagnostics in programming options (I've turned on show touches on touchscreen and localization of the pointer) but no touches detected however mouse moves yes.
Rebooting didn't help - many trials. Safe mode neither.
I haven't done a full recovery to factory settings yet. I am afraid of loosing USB debugging mode. Looking foreward to finding software resolution before warranty replacement.
2. Power button doesn't light up the screen - possibly backlight fault (software?)
After few trials with power button the screen shows up. Sometimes I try reboot but the problem returns. It is randomly, sometimes after one pressing power buton, sometimes lastlky after few trials withe few rebooting.
When I put the tablet on light (a lamp or sunshine throug window) I can see the view of the screen darkly. So there is the view but without brightness.
Android 7.1.2, N2G47D
I have the same problem now.. However I've noticed the following: When the device is in the case which covers the screen and has a magnet, the problem will persist. If removed from the case and left for a day outside, the problem is gone (so far at least). I will return the device for a replacement and hope google can replicate the issue. Anyone else using a case with a magnet?
Yes I have the same problem and also a magnet case. But for me the problem is not gone, after removed from the case and left for a day outside .
Now I get a replacement from google.
Should I now no longer use a case with magnet? Is the case the reason for a broken pixel c?
The phone speakers make a crackling popping noise periodically... i cant figure out what exactly triggers it and i dont think its necesarily just at high volume. The one way i know how to reproduce this every time is to run antutu benchmark and try to turn the volume all the way down and all the way up while the first video benchmark (i think its called maroon) is running. the speakers will crackle through several of the adjustements.
Anyone else experiencing this? Do you think this is a software issue or a factory defect? I could listen to music for a halfhour straight and not have an issue as long as im not doing anything else with the device which makes me think its more of a software issue when volume is being adjusted or other operation where the volume is being toggled (i.e it has also happened while receiving a notification where the first milliseconds of the notification alert will play and then it will "crackle-out")
I did a complete factory reset and booted total stock and still had the issue so its not root or any modification related.
Hey, i have the same problem! Did you contact the support?
CBlues said:
Hey, i have the same problem! Did you contact the support?
Click to expand...
Click to collapse
I contacted support and the tech said they didn't get any other reports of this happening and said it might be a hardware issue but then they forwarded me to Verizon to get a replacement phone... then Verizon told me it's not a hardware problem it's a software problem so I can't get a replacement. I am convinced that it is a software problem because of the symptoms of otherwise normally working speakers but at the same time I am very surprised that there aren't tons of other people bringing this up. I am also not sure where to report this bug to google
diabl0w said:
The phone speakers make a crackling popping noise periodically... i cant figure out what exactly triggers it and i dont think its necesarily just at high volume. The one way i know how to reproduce this every time is to run antutu benchmark and try to turn the volume all the way down and all the way up while the first video benchmark (i think its called maroon) is running. the speakers will crackle through several of the adjustements.
Anyone else experiencing this? Do you think this is a software issue or a factory defect? I could listen to music for a halfhour straight and not have an issue as long as im not doing anything else with the device which makes me think its more of a software issue when volume is being adjusted or other operation where the volume is being toggled (i.e it has also happened while receiving a notification where the first milliseconds of the notification alert will play and then it will "crackle-out")
I did a complete factory reset and booted total stock and still had the issue so its not root or any modification related.
Click to expand...
Click to collapse
Actually I have heard of this... Its in the forums somewhere...
Tell VZW to STFU and send you a new one. :angel:
I've been experiencing a similar issue. Pixel XL 128GB.
I notice sporadic stuttering in the video and audio whenever playing videos, either through YouTube or Chrome. I don't really notice it anywhere else, which leads me to believe it's a software issue. Potentially a bug in the video decoders. I haven't contacted Google support yet.
I had the same exact problem with my Verizon one, it happened twice in a week of owning it, it bothered me so I ended up returning it, back to my s7e!
---------- Post added at 04:37 PM ---------- Previous post was at 04:35 PM ----------
When it first started happening to me I couldn't find any others talking about the issue so I thought I was alone lol
My 32gb XL has been doing it too. I generally use bluetooth headphones, so it's not a big deal, but it is certainly something I've noticed when trying to use the in-phone speaker.
diabl0w said:
I contacted support and the tech said they didn't get any other reports of this happening and said it might be a hardware issue but then they forwarded me to Verizon to get a replacement phone... then Verizon told me it's not a hardware problem it's a software problem so I can't get a replacement. I am convinced that it is a software problem because of the symptoms of otherwise normally working speakers but at the same time I am very surprised that there aren't tons of other people bringing this up. I am also not sure where to report this bug to google
Click to expand...
Click to collapse
Obviously they are lying! See my post from 11/11/2016!http://forum.xda-developers.com/showpost.php?p=69576560&postcount=109
Scott said:
Actually I have heard of this... Its in the forums somewhere...
Tell VZW to STFU and send you a new one. :angel:
Click to expand...
Click to collapse
That would be me:silly:
Scott said:
Actually I have heard of this... Its in the forums somewhere...
Tell VZW to STFU and send you a new one. :angel:
Click to expand...
Click to collapse
ringochan said:
Obviously they are lying! See my post from 11/11/2016!http://forum.xda-developers.com/showpost.php?p=69576560&postcount=109
:
Click to expand...
Click to collapse
Thanks guys, so I contacted Verizon and they had the nerve to tell me that they would replace it but only with a "like new" device. What a joke. So basically they told me well **** you and that sucks that we sent you a broken phone so here's somebody else's old broken one. such a slap to the face.
I didn't have the time to sit an argue so I will have to either call back another time or go to a store
I'm contacting support about this now. I only notice it when I'm using my Daydream View headset though. But does anyone know if it's safe to perform a factory data reset if I'm rooted with custom kernel?
Sent from my Pixel XL using Tapatalk
I have the same issue. Here is where I posted about it.
http://forum.xda-developers.com/pixel-xl/help/pixel-xl-speaker-issue-t3483952/page3
I contacted Google. They want me to send my phone back and after they got it they will send me a replacement...
Being on Verizon I am also afraid that I'll get shipped a phone with a locked bootloader, I am still trying to figure out how I wanna handle this
Same here. Sending back for a new one.
diabl0w said:
Being on Verizon I am also afraid that I'll get shipped a phone with a locked bootloader, I am still trying to figure out how I wanna handle this
Click to expand...
Click to collapse
You can send you phone back to the Google store if you speak to the right person. But you will have to send it then they will send you another. But beware they are already sending used phones as replacements just as Verizon is. Many have returned their device for many different reasons. This is a nice phone and we all like Google but this phone has the worst customer service I've ever seen displayed versus a nexus. Google will actually argue with you to assure you there's nothing wrong with your phone even though you have it in your hand and know there's something wrong. And in all honesty every phone should be recalled because of the lens flare if the camera. That's a major issue noteworthy if a recall. Google doesn't want scar of their first all Google phone to tarnish their image and branding. I spoke to Google cs and the rep was totally real and honest starting that the camera has caused many phones to be replaced knowing all of them have the same camera issue. He said they've replaced do many phones that it had caused a delay of others getting their phones. Google actually has phones that are new put aside for replacing defective phones and they've used all of their stock as replacements. Hence the reason after two months they are already sending out used replacements.
I think I am going to take it to a Verizon store tomorrow because the process of showing them the issue will be a lot easier and maybe they have older phones in stock that don't have locked bootloader