Related
Hey guys I recently bought my moto 360 and love it! The only problem I'm currently experiencing is that the watch face no longer wakes when I turn my wrist to look at the watch. This is extremely annoying because I want to be able to have more functionality with just one hand. Other than that the watch works perfectly. I've even been getting 16 hrs+ battery life on average. I tried looking through the settings to see if there was an option to change the wake settings but there are none. I don't see any other forums or anyone else posting about this issue so if you've had this issue please let me know what you did to fix this. ThankS!!
That started happening to me after the most recent update. Battery life improved by a few hours but then the wrist turn stopped being reliable
matrix0886 said:
That started happening to me after the most recent update. Battery life improved by a few hours but then the wrist turn stopped being reliable
Click to expand...
Click to collapse
Since battery life is a bit more reliable, have you tried going with Ambient Mode again? While it admittedly doesn't last as long on as off, it does result in much more 'reactive' wrist turns to tell the time more quickly and repeatedly.
mine's a bit odd. Wakes fine normally, but when I mute notifications, it doesn't wake the screen unless I really move my wrist in an obvious way.
I actually got it to work now. The problem was going on when I had the keislertech stainless steel band on it. I switch the band with the leather one and the watch started waking every time I turned my wrist. I'm guessing the steel band was interfering with the accelerometers considering they use electromagnets.
Im still having this problem. And im only using the leather band. Any fix? Yesterday was working fine when i was driving to work then i noticed at work when i twisted my wrist nothing happened.
Try more of a 'flick' with your wrist than a 'turn' with your wrist.
I too am having this issue. I just did a complete factory reset on the device, still no luck. I was worried my gryoscope may be busted, but it seems to be working at least by using a testing app I found, though I am not sure how reliable that is.
No matter how hard I flick my wrist, the screen won't come on. What's more, putting it in Ambient mode will show the black and white screen for 1 second, then the screen turns off, as if the device was face down.
Quite honestly, I think it may be a busted Gryoscope, which would suck, so I'm going to test a few more things and see.
---------- Post added at 11:55 AM ---------- Previous post was at 11:13 AM ----------
Factory Reset with no apps installed didn't help. Called Motorola, they are shipping me a new device.
Can't think of it being anything other than a busted Gyro that always points down.
Question for the OP, at any time did you use the latest Nexus QI charger to charge your device? Doubt that has anything to do with it, but want to know just in case.
Well, the Gyro in my watch is working again, but I'm still going to follow through with the replacement, since I don't want to risk it happening again. Nothing was done to fix it, it just randomly started working Saturday night. The sensor test I mentioned earlier is showing full functionality now.
Candidly, you're probably smart to do so. Tech being what it is, often times you get a device with bugged hardware. Let us know how the replacement works out for you.
humulos said:
Well, the Gyro in my watch is working again, but I'm still going to follow through with the replacement, since I don't want to risk it happening again. Nothing was done to fix it, it just randomly started working Saturday night. The sensor test I mentioned earlier is showing full functionality now.
Click to expand...
Click to collapse
Same problem here... Seems to have a link with aftermarket QI charger. The first time I've put it on the charger pad the screen flipped upside down. Since then, no waking up from wrist movement and even on the original charger it's showing upside down.
I don't know what to do !!!
This is my second watch i had a crack on the first one taking it out of the box I don't want to wait another week to get a replacement !
glabbe0299 said:
Same problem here... Seems to have a link with aftermarket QI charger. The first time I've put it on the charger pad the screen flipped upside down. Since then, no waking up from wrist movement and even on the original charger it's showing upside down.
I don't know what to do !!!
This is my second watch i had a crack on the first one taking it out of the box I don't want to wait another week to get a replacement !
Click to expand...
Click to collapse
Came back to normal without any reasons... oh well....
my moto 360 also doesn't wake anymore, but also not when i tap it
if i tap and hold, i feel the vibration that shows up to change the watch face and when i click the side button you see this menu before it goes back to the clock
Wow, this just started happening to me too! I was hoping to find the solution in this thread, so I hope this isn't a sign of universal hardware failure!
Started happening to me too just yesterday.
Bummer
Been a few days for me. . . not responsive on wrist turn or tap.
davegravy said:
Started happening to me too just yesterday.
Click to expand...
Click to collapse
skeralum said:
Been a few days for me. . . not responsive on wrist turn or tap.
Click to expand...
Click to collapse
Got mine working again. If you haven't already tried, open android wear app on your phone, then toggle the setting "tilt to wake screen" a few times (make sure it ends up ON however). Also, on your watch, make sure theatre mode is off.
I was having the same problem. It was theater mode. Somehow it was turned on,I turned it off and now the wake function works again.
Mine stopped working too a few days ago. I toggled 'tilt to wake screen' in the wear app and it started working again.
davegravy said:
Got mine working again. If you haven't already tried, open android wear app on your phone, then toggle the setting "tilt to wake screen" a few times (make sure it ends up ON however). Also, on your watch, make sure theatre mode is off.
Click to expand...
Click to collapse
Thanks! Toggling the "tilt to wake" setting worked for me too!
Ok I have noticed my Note 4 can take the LONGEST time to focus. I mean over a minute sometimes. The only settings I have on is HDR and have video set to record in full HD. Is this normal for the Note 4? Just curious as I am coming up on 30 days and if its got a camera issue I can exchange it at ATT.
Normal !
Lots of people having that issue, me included. I just choose to live with it.
One thing to make it focus properly is pointing it up and tap the screen, then it would focus normal (macro or not).
Hopefully it would be fixed in Lolipop.
Attempted to fix
Hello, I recently got the Note 4 myself about a month ago too. Since I purchased it from Best Buy, I thought I had 30 days to exchange it once I noticed and endured the camera issue. I waited too long. However if you go to the Samsung Repair Center and tell them your issue with your camera they will fix it. However, when they attempted to fix it, they ended up frying my motherboard and I had to wait 3-4 days while they received a new motherboard. Afterward though, everything works perfectly and its instantly focusing. The frying motherboard is probably independent of the camera so its a gamble if you want to risk it, make sure you back up all your data and go as soon as early as possible since all the Samsung Repair Centers get busy fast.
Google: "Samsung Repair Center Locations" and pick, I cannot post links as I just made an account to post this.
This is NOT normal. It should focus right away. The Note 4 is one of the first phones to have moving parts in the lens, and Optical Image Stabilizer (OIS). Apparently there is a problem with it sticking due to many factors, I'm guessing most of it is from shipping since there is no padding in the boxes. Once you load your camera app and it doesnt focus, try slapping the side of the phone, if it focuses then, return it. I had 2 replaced due to this issue. If you can return within your return period, do it. Everyone else can just do a warranty replacement.
I am having the same issue, but am able to correct it relatively quickly by rotating to potrait or landscape depending. Not quick enough for those "moments" necessitating instant response time though.
bluetoothless said:
I am having the same issue, but am able to correct it relatively quickly by rotating to potrait or landscape depending. Not quick enough for those "moments" necessitating instant response time though.
Click to expand...
Click to collapse
Thanks for the info. For the moment, this works.
bluetoothless said:
I am having the same issue, but am able to correct it relatively quickly by rotating to potrait or landscape depending. Not quick enough for those "moments" necessitating instant response time though.
Click to expand...
Click to collapse
That does seem to help me also, at least its faster. Thanks for the tip!!
jpinks said:
Ok I have noticed my Note 4 can take the LONGEST time to focus. I mean over a minute sometimes. The only settings I have on is HDR and have video set to record in full HD. Is this normal for the Note 4? Just curious as I am coming up on 30 days and if its got a camera issue I can exchange it at ATT.
Click to expand...
Click to collapse
I am using two phones - one personal (Note 4) and the new BlackBerry Passport for work. I do notice that Note 4 is pretty slow with focusing. The darker it gets the longer it takes to focus. I think it is pretty normal. Just the software is like that.
Happens when you're in auto night mode. To disable just set your ISO
Sent from my SAMSUNG-SM-N910A
greekunit690 said:
Happens when you're in auto night mode. To disable just set your ISO
Sent from my SAMSUNG-SM-N910A
Click to expand...
Click to collapse
Nice thanks for the info. I couldn't understand why my note 2 took night pics so much faster. Now that I set the iso to 100 it works fast. What iso are you setting your to?
Sent from my SAMSUNG-SM-N910A using xda premium
borijess said:
Nice thanks for the info. I couldn't understand why my note 2 took night pics so much faster. Now that I set the iso to 100 it works fast. What iso are you setting your to?
Sent from my SAMSUNG-SM-N910A using xda premium
Click to expand...
Click to collapse
Depends on the lighting. If it's dark I set it a bit higher (600 to 800)... Bright out I set it to 100 or 200. I also really like camera fv-5. Try it out if you want an amazing picture experience
Sent from my SAMSUNG-SM-N910A
Thanks for all the tips!! I will be trying them!!
When I first got my Tmobile note 4, camera focused really fast, in a split of a second. Then one day, it suddenly slowed down to several seconds being unable to focus at all every time it started, sometimes up to 10 seconds. I had to tap it, shake it, or rotate it, then it starts to focus.
Today, I tried to reboot into safe mode to see if there's any downloaded app that might be the culprit, and no improvement at all. I started to disable pre-loaded apps, turning off GPS didn't help. But when I disabled/turned off S Health, the camera focused almost immediately just like new. Camera on and off, tested repeatedly, it worked very quick and smoothly. Afterwards, I turned on S Health again, seems the camera keeps working normally. Under low light, I do have to tap the focus ring one or two times to make it focus properly.
My testing results are when S Health is completely disabled, the camera focuses super fast. When S Health is turned on again, it slows slightly by maybe half to one second. I vaguely remember the focusing issue happened sometime after I turned on S Health. I suspect it'll slow down again after S Health has been running for a couple weeks. I'll keep an eye on it.
Maybe S Health keeps holding on some sensors until camera app asks for them, which may take a few seconds. S Health does slow down steadily when more and more data are accumulated. But at this point, I can't say for sure that S Health is the real problem. YMMV.
hz-zh said:
My testing results are when S Health is completely disabled, the camera focuses super fast. When S Health is turned on again, it slows slightly by maybe half to one second. I vaguely remember the focusing issue happened sometime after I turned on S Health. I suspect it'll slow down again after S Health has been running for a couple weeks. I'll keep an eye on it.
Maybe S Health keeps holding on some sensors until camera app asks for them, which may take a few seconds. S Health does slow down steadily when more and more data are accumulated. But at this point, I can't say for sure that S Health is the real problem. YMMV.
Click to expand...
Click to collapse
It helps.
Thanks
I think I should write a follow-up on this issue.
My previous method of turning off/on S Health worked only temporarily, unfortunately. After a few days, auto focus problem came back again. Basically the symptom is like this: leave the phone sitting on desk for a while, say 10+ minutes to half an hour, the camera app has focus issue that needs 10-20 seconds to start auto-focus, like something suddenly wakes up. When camera app is opened/closed several times in a row non-stop, there's no auto-focus problem.
Also tried the method of modifying /system/build.prop file, didn't work.
Eventually what worked for me is this: my phone has wallet cover, so I tried the method someone suggested, slapping the top back part of the phone against my palm. It took me three tries, once a day slapping 10-20 times. I thought it'll never work in the first two days, but still tried the method. The 3rd day, it suddenly worked. Now the phone auto-focuses properly.
However, there's one issue, initially the phone takes picture just like +1ev is set when the setting is actually at zero, and range of view showing on screen is like shrinking by about 5% on both sides. To take normal pictures, had to manually set to -1ev. What I did next is doing the opposite, slapping the top glass/screen part of the phone against my palm. It took several rounds of back & forth slapping, loosing fast auto-focus then getting it back, etc. Now it looks like it's only at +0.5ev, which is acceptable, photos are slightly brighter than normal. Most probably picture size is also back to original.
So my feeling is maybe there is a hardware defect with Note 4's camera module. Right now, I'm ok with it. But the final solution is probably buying a new camera module and replace it. If you're handy enough, that's not a bad idea. There're youtube videos showing how to replace, but I'd prefer not peeling off the screen from main board. Comments on videos showed how-to not taking off screen when replacing camera.
I have same issue with camera. Since getting the phone it's been so slow.
I finally just found that tapping the screen pretty hard right about where the camera is located jolts it enough to focus quickly.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
I've had the same issue with the camera, it was pretty fast when I first got the phone and it slowed down over time.
Recently I accidentally dropped the phone as it slipped from my hand and the issue seemed to have gone away for good (knock on wood).
My brand new Note 4 (back in November, I think?) couldn't focus close up (& keep it), was slow to gain focus at all, and made me despise the camera. Had to use the warranty service to replace it (didn't get it at a corporate store --got it at an authorized retailer-- and the one I got worked a thousand times better. You have a hardware defect. I found people in the T-Mobile forums I think back then having similar problems. Nobody ever found a "fix" outside replacing the camera or the phone.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
keithfrombm said:
My brand new Note 4 (back in November, I think?) couldn't focus close up (& keep it), was slow to gain focus at all, and made me despise the camera. Had to use the warranty service to replace it (didn't get it at a corporate store --got it at an authorized retailer-- and the one I got worked a thousand times better. You have a hardware defect. I found people in the T-Mobile forums I think back then having similar problems. Nobody ever found a "fix" outside replacing the camera or the phone.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
Click to expand...
Click to collapse
I had same problem with my note edge, I replace camera module and for last 3 days so fare so good. I think this is hardware problem since I had to shake or tap phone to get my focus to work.
Sent from my SAMSUNG-SM-N915A using XDA Premium HD app
keithfrombm said:
Nobody ever found a "fix" outside replacing the camera or the phone.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
Click to expand...
Click to collapse
You're right, the HW is defective. Eventually I bought a new rear camera, and replaced by myself. Easy fix. Worked like a charm, focused in a split second again.
Every once in a while I can't swipe down the notifications bar and the top 10% ish of the screen doesn't respond to touches.
Also, I seem to get quite a few false touches
I think i may have issue but not too sure will keep a eye out
Sent from my LG-H811 using XDA Free mobile app
misteroh said:
Every once in a while I can't swipe down the notifications bar and the top 10% ish of the screen doesn't respond to touches.
Also, I seem to get quite a few false touches
Click to expand...
Click to collapse
I have an issue that is 100% reproducible on my G4.
1. I set in Dev option for the animations to be .5x
2. Swipe between home screens left, right left, then press any of the shortcuts in the persistent are of the screen (phone, camera etc).
3. Now try to do the same thing but press any app shortcut or even the recents button. it works fine. I think this is a software issue.
I freaking starting to hate LG UI.
No issues on my G4, however...
I had the same exact issues on the G2 where the digitizer and the screen had to be replaced time and time again, and it'd just break again. Seems like the heat makes it so touches don't register.
I posted the other day about an issue mainly in Pinball Arcade, where taps occasionally weren't registering a flipper activation. This problem seemed to extend into the OS itself, as I have had some hiccups while typing or navigating. I just wiped everything and am trying again...we'll see. But I want this figured out by early next week so I can take advantage of the 14-day period.
Seems to happen when the top part of the phone is really hot
I'm having issues with the touch screen just not registering taps randomly. i can be in chrome scrolling and just have it stop scrolling then decided to start up again and i have to press an app icon multiple times to get it to register. ive only had the phone for 5 hours now. very pissed.
going to go return it now. was going to get the nexus 6 and i should have in the first place.
Some taps not registering here too...sucks, but i don't see any other phone I like out there.
same here I'm having bad touch screen issue, will be returning just paid $635 for this
.. I just started having this issue after the recent tmo update.. Wtf
Don't seem to be having any touchscreen issues. Mine is only heat related. Getting new phone delivered today. Hopefully that will fix it.
rsbenedict said:
Don't seem to be having any touchscreen issues. Mine is only heat related. Getting new phone delivered today. Hopefully that will fix it.
Click to expand...
Click to collapse
It's normal to heat up the first few days while it downloads and installs all your data.
I've had my phone two weeks. It heats up to over 107F while listening to Tune-in Radio. Yesterday at the T-Mobile store it went from 81-107F after 5 minutes of talking on the phone and about 5 minutes of Tune-In Radio. The hottest I've noticed is 117F. This is under normal operation and NEVER happened with any other smart phone I've had (I've had smart phones since 2005). It will be in my pocket and I have to take it out because it's so hot. I don't play intensive games or do anything really intensive on it. The most intensive thing I do is watch youtube videos or periscope. I use this phone exactly as I used my G3 two weeks ago. Nothing has changed and no new apps.
rsbenedict said:
I've had my phone two weeks. It heats up to over 107F while listening to Tune-in Radio. Yesterday at the T-Mobile store it went from 81-107F after 5 minutes of talking on the phone and about 5 minutes of Tune-In Radio. The hottest I've noticed is 117F. This is under normal operation and NEVER happened with any other smart phone I've had (I've had smart phones since 2005). It will be in my pocket and I have to take it out because it's so hot. I don't play intensive games or do anything really intensive on it. The most intensive thing I do is watch youtube videos or periscope. I use this phone exactly as I used my G3 two weeks ago. Nothing has changed and no new apps.
Click to expand...
Click to collapse
Yeah, that's probably not normal if it's been two weeks. Mine was only warm the first two days, but it quickly resolved once everything's properly set up.
What's funny, is she went down a list of why my phone might be hot: did you leave it in the sun? are you playing intensive games? a case can cause the phone to get hot. using your screen at high brightness can cause the phone to overheat. LOL
I told her that when play store updates 2 apps, it gets hot. She said she could fix that and promptly went to my settings and turned off auto-update. REALLY?
Valkyrie743 said:
I'm having issues with the touch screen just not registering taps randomly. i can be in chrome scrolling and just have it stop scrolling then decided to start up again and i have to press an app icon multiple times to get it to register. ive only had the phone for 5 hours now. very pissed.
going to go return it now. was going to get the nexus 6 and i should have in the first place.
Click to expand...
Click to collapse
I bought phone last week and experiencing the same exact thing. Also when texting. Very mad too as I was going to get Nexus 6 too. Well within 14 days so returning tomorrow
---------- Post added at 07:55 AM ---------- Previous post was at 07:51 AM ----------
rsbenedict said:
I've had my phone two weeks. It heats up to over 107F while listening to Tune-in Radio. Yesterday at the T-Mobile store it went from 81-107F after 5 minutes of talking on the phone and about 5 minutes of Tune-In Radio. The hottest I've noticed is 117F. This is under normal operation and NEVER happened with any other smart phone I've had (I've had smart phones since 2005). It will be in my pocket and I have to take it out because it's so hot. I don't play intensive games or do anything really intensive on it. The most intensive thing I do is watch youtube videos or periscope. I use this phone exactly as I used my G3 two weeks ago. Nothing has changed and no new apps.
Click to expand...
Click to collapse
Mines got pretty hot too when updating apps the first day of use, hottest I've ever felt a phone. I've been working at T-Mobile since 2009 and I always thought customers would exaggerate about a hot phone.
Different kind of touch issue
When i place my mobile on bed or any soft surface, the touch does not respond. Am unable to pull down the notification bar. Tried multi touch app and it does not recognize the touches itself. Someone help me out pls.
misteroh said:
Every once in a while I can't swipe down the notifications bar and the top 10% ish of the screen doesn't respond to touches.
Also, I seem to get quite a few false touches
Click to expand...
Click to collapse
Mine is perfect except if it's plugged in and charging. It's much less responsive then, and needs a much firmer touch.
Sent from my VS986 using Tapatalk
brainwash1 said:
Mine is perfect except if it's plugged in and charging. It's much less responsive then, and needs a much firmer touch.
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
I just noticed this last night as well. I had it plugged in and it started to slow down a bit (Thermal throttling) and touches were less responsive.
At this moment it's working great. I really hope this isn't a heat/hardware thing
rsbenedict said:
I've had my phone two weeks. It heats up to over 107F while listening to Tune-in Radio. Yesterday at the T-Mobile store it went from 81-107F after 5 minutes of talking on the phone and about 5 minutes of Tune-In Radio. The hottest I've noticed is 117F. This is under normal operation and NEVER happened with any other smart phone I've had (I've had smart phones since 2005). It will be in my pocket and I have to take it out because it's so hot. I don't play intensive games or do anything really intensive on it. The most intensive thing I do is watch youtube videos or periscope. I use this phone exactly as I used my G3 two weeks ago. Nothing has changed and no new apps.
Click to expand...
Click to collapse
If you don't mind me asking, what are you using to monitor the temp?
After using my Pixel daily for 6 months (got the first batch, pre December 25th) and having next to no issues with it (wifi strength sucks, even with Xceed kernel, but it's better than it was), half of my screen decided it wanted to go goofy. I was using it two days ago and everything was working fine, I used it yesterday morning for a few minutes and then plugged it into the Google charger that came with it and let it sit on my couch for a few hours while it was charging. I got on the bus, and pressed the power button to wake the screen and nothing happened. Thinking I had it turned off I held the power button for a few second, and still nothing. So I held it for 30 seconds and when it brought up the bootloader warning the right side of the screen was glitching, same thing happened on the Google logo, boot animation, and continued into Android. I powered it off, hoping it would go away but it didn't. The slight glitch then turned into static "snow" which will then change sporadically based on what I'm doing on the tablet. That area of the screen still works perfectly because touch input works, and when I take a screenshot and view that area of the screen it shows up just as it should. It seems like there is an overlay on the right side of the screen that won't go away. Since it happens from the moment you turn it on makes me think it's a hardware issue but the fact that the screen itself still works perfectly makes me think it's a software issue. I haven't flashed the stock ROM back on it yet or locked it backup yet since I don't have a type c to type a adapter with me, it's still under warranty but I wanted to see if you guys could help me fix it before I sent it back.
TL; DR
This just started happening to me today, exactly as you described.
Interesting. I just RMA'd mine, should be receiving it within the next few days.
I'm returning mine too. I've determined that it's hardware because when I applied pressure around the edges of the screen I felt something slightly pop into place and then the problem was temporarily corrected. If I apply slight pressure to parts of the screen it happens again.
At this point I've flashed back to stock and I'm in an eternal recovery bootloop that I can't fix because acquiring USB drivers that work is incomprehensively difficult.
Just had mine go as well :crying:
Oh wow, that sucks. At least I'm not the only one though. I just got my new one a few days ago and all is well so far, hopefully this one won't screw up. RMA process was very smooth.
As for the USB drivers I usually have to install them manually by using the "select driver from a list"
Sent from my Pixel C using Tapatalk
Same issue on my first one
Here's my post from the mapping problems to serial # thread.
Google RMA process was fine once I was finally able to get a chat window with them.
Be sure to post to the problem mapping thread to help others!!
Add me to the list. Just went through the RMA process and am now waiting for the replacement to come. I can deal with the wifi issue and the random reboots, but having half of your screen corrupted is unacceptable. I don't even know how this is possible unless some genius at the pixel C team decided that it's cheaper to source half a screen and glue them together.
It's kinda crazy that I couldn't find this happen anywhere then all of the sudden it's happening to you guys! I'm extremely confused how it happened and what actually went wrong with it.
brando56894 said:
It's kinda crazy that I couldn't find this happen anywhere then all of the sudden it's happening to you guys! I'm extremely confused how it happened and what actually went wrong with it.
Click to expand...
Click to collapse
Most likely some latently defective silicon from Nvidia.
Sent from my Pixel C using Tapatalk
pkelly517 said:
Most likely some latently defective silicon from Nvidia.
Click to expand...
Click to collapse
I don't believe so, I think it has more to do with the screen, since it would occasionally correct itself, and even when half the screen was screwed up, screenshots would come out perfectly. It's almost like there's something stuck over the right half of the screen.
brando56894 said:
I don't believe so, I think it has more to do with the screen, since it would occasionally correct itself, and even when half the screen was screwed up, screenshots would come out perfectly. It's almost like there's something stuck over the right half of the screen.
Click to expand...
Click to collapse
Of course screenshots would come out perfectly. It's just a memory dump of the video RAM. This is a problem with getting that memory to the display. I think the display driver is part of the SoC. I could be wrong. Maybe it's a cable.
But it seems like a bit in the display driver is never getting enabled.
Sent from my Nexus 5X using Tapatalk
I'm fairly certain that it's a physical issue with the screen or the connection to the screen. When I had this issue I saw a visible change when I applied some light pressure around the edges of the screen. At one point it almost felt like something popped into place and the problem went away (then resumed.) Also, if I applied some pressure on the lagging side of the screen I would see some odd behavior as if the connection was fluctuating. I didn't squeeze hard, but it didn't take much.
I have had TWO Pixel Cs do this now. The first got the dreaded half screen of death after 5 months back in May, and the replacement that Google sent me has just started doing it today after just 3 months. The second device was from a much later batch than the first.
My experience so far makes me think that all Pixel Cs might have this hardware defect - it's just a matter of time before it happens. That's kinda gutting if it's true as for me this is the best tablet out there, and I can't see anything else coming close to replacing it.
About to contact Google for RMA again I guess. Third time lucky maybe...?
Wow really? That's no good!
Pixel C Screen Issues
Add me to the list, as of this morning. 8 months old.
SpaceGooner said:
I have had TWO Pixel Cs do this now. The first got the dreaded half screen of death after 5 months back in May, and the replacement that Google sent me has just started doing it today after just 3 months. The second device was from a much later batch than the first.
My experience so far makes me think that all Pixel Cs might have this hardware defect - it's just a matter of time before it happens. That's kinda gutting if it's true as for me this is the best tablet out there, and I can't see anything else coming close to replacing it.
About to contact Google for RMA again I guess. Third time lucky maybe...?
Click to expand...
Click to collapse
what's the serial# of your replacement?
lude219 said:
what's the serial# of your replacement?
Click to expand...
Click to collapse
My second Pixel C's s/n is 61250***** This one has developed the screen problem on the right of the screen
The earlier one I had was 5A230***** This one had the problem on the left side of the screen
I assumed the second one was from a later production batch than the first, but must admit I don't really know that.
SpaceGooner said:
My second Pixel C's s/n is 61250***** This one has developed the screen problem on the right of the screen
The earlier one I had was 5A230***** This one had the problem on the left side of the screen
I assumed the second one was from a later production batch than the first, but must admit I don't really know that.
Click to expand...
Click to collapse
According to this http://forum.xda-developers.com/pixel-c/general/mapping-problems-to-serial-t3274660 there still seem to be some issue with the #61250 batch so I'd try for a 3rd time to see if you get a 6202000 one (what i have now). It's stupidly frustrating but the Pixel C is too good to give up now.
lude219 said:
According to this http://forum.xda-developers.com/pixel-c/general/mapping-problems-to-serial-t3274660 there still seem to be some issue with the #61250 batch so I'd try for a 3rd time to see if you get a 6202000 one (what i have now). It's stupidly frustrating but the Pixel C is too good to give up now.
Click to expand...
Click to collapse
Thanks for the info. Not sure I'll be able to determine what s/n Google sends me next time, but here's hoping I get a good one and that I've just been unlucky so far. I won't be able to RMA until I get home from vacation later in the week anyway. If they send me another Pixel C that develops the half screen problem down the line, I will surely have to get a refund and maybe go for a top end Chromebook (with Google Play of course) next time.
I bought my G5+ in August of 2017, so ~19 months ago... And up until a couple weeks ago, it has been working flawlessly. Lately it will just stop letting me into the device, meaning I can't unblank the screen with the power button or fingerprint sensor. It isn't locked up, things still work and I get notifications, but the screen won't come on. Press and hold the power button and it reboots and usually sticks at the Moto logo and goes nowhere until I reboot and clear the cache partition in recovery, sometimes having to repeat this a time or two before it boots and seems to act normally for several days then we repeat the process. I haven't added any new apps I can think of in the last 30 or so days. This did not start after a system update either.
Think it's on it's last legs, or is it just time to factory reset and start clean again?
How are other's devices holding up, and if it has died what were the symptoms before it did?
acejavelin said:
I bought my G5+ in August of 2017, so ~19 months ago... And up until a couple weeks ago, it has been working flawlessly. Lately it will just stop letting me into the device, meaning I can't unblank the screen with the power button or fingerprint sensor. It isn't locked up, things still work and I get notifications, but the screen won't come on. Press and hold the power button and it reboots and usually sticks at the Moto logo and goes nowhere until I reboot and clear the cache partition in recovery, sometimes having to repeat this a time or two before it boots and seems to act normally for several days then we repeat the process. I haven't added any new apps I can think of in the last 30 or so days. This did not start after a system update either.
Think it's on it's last legs, or is it just time to factory reset and start clean again?
How are other's devices holding up, and if it has died what were the symptoms before it did?
Click to expand...
Click to collapse
Never heard of issues like that. My device is a little older and still working as it should, I use the fingerprint sensor to unlock it and also for one button navigation with hidden nav bar.
As your problem is not only related to the sensor but also to the power button I would think it's not a hardware issue and if you haven't installed anything like a third party lockscreen you're maybe right that it's time to do a factory reset or, if this won't help even reflash the firmware using fastboot or Lenovo Motorola Smart Assistant.
Wolfcity said:
Never heard of issues like that. My device is a little older and still working as it should, I use the fingerprint sensor to unlock it and also for one button navigation with hidden nav bar.
As your problem is not only related to the sensor but also to the power button I would think it's not a hardware issue and if you haven't installed anything like a third party lockscreen you're maybe right that it's time to do a factory reset or, if this won't help even reflash the firmware using fastboot or Lenovo Motorola Smart Assistant.
Click to expand...
Click to collapse
Thanks... Honestly, kind of what I expected... Guess this weekend I will make sure everything is backed up and factory reset. Probably time anyway, was thinking about it and I don't recall every doing one since I got it, not on this phone, so it's well past due.
Thanks for the input.
acejavelin said:
Thanks... Honestly, kind of what I expected... Guess this weekend I will make sure everything is backed up and factory reset. Probably time anyway, was thinking about it and I don't recall every doing one since I got it, not on this phone, so it's well past due.
Thanks for the input.
Click to expand...
Click to collapse
Mine's still holding since Sept 2017. A new replacement is $180 from Amazon.
I never considered this as a "forever" phone; my goal was to get about 2 years out of the G5+ and see where it stood in terms of security.
I paid almost double for my N5, and got about 2X the life out of it. Even at 19 months, it's still an excellent value.
androcraze said:
Mine's still holding since Sept 2017. A new replacement is $180 from Amazon.
I never considered this as a "forever" phone; my goal was to get about 2 years out of the G5+ and see where it stood in terms of security.
I paid almost double for my N5, and got about 2X the life out of it. Even at 19 months, it's still an excellent value.
Click to expand...
Click to collapse
Well, there won't be another Moto in this house... Not after getting a couple Nokia's. When this one's finally gives up, I will likely replace it with a Nokia.
After 20 months it's still running like new. Battery life is still around 5-6 hours sot, standby time is still about the same as it always has been. No problems or issues with any sensors or buttons. And I haven't noticed any signs of it slowing down or lagging. Basically, it's still running like it was when I bought it. Great phone and excellent value for money.
As a side note, my father-in-law is using my old Moto G3 that I replaced with this G5 plus. Battery life is starting to fade, but aside from that, the old G3 is still functioning perfectly.
Sent from my Moto G (5) Plus using Tapatalk
Only issue with mine (bought Nov 2017) is it is a little warped for some reason. I do carry it in my front pocket but there is never any stress on it. It doesn't affect anything but is annoying that it can rock a little when on a flat surface. I love it other than it doesn't support Band 71.
My first one I dropped broken screen second one I bought tempered glass screen protectors and they have saved my phone more than 10 times well worth a couple bucks a piece online and it's been a great phone