Related
I made a video, here is the link:
http://youtu.be/_4KC8wnc_zE?t=23s
It won't rotate correctly, I already tried several apps for setting the wallpaper, but no one worked
This seriously looks sh**
Is it only my device that has this problem?
Greetings
What do you mean it fails? It looks exactly just as it should. I have audio off, so if you said something crucial there, can you repeat it here.
I don't see anything worrying apart from a slight lag, but this may be your camera.
Edit: Sorry, after looking at it for the second time and in the full-screen mode now, I can see what you mean - there's a black bar that gets updated later. It certainly shouldn't be this way. I had similar issues with pdf rendering in the power-saving mode. What settings are you on?
d14b0ll0s said:
What do you mean it fails? It looks exactly just as it should. I have audio off, so if you said something crucial there, can you repeat it here.
I don't see anything worrying apart from a slight lag, but this may be your camera.
Click to expand...
Click to collapse
I dont have mine yet, but compared to my wife's ipad2, with whats in the video, it seems there is a lot of lag?
Shouldnt that thing turn almost a second after you have turned it?
It can take like 2 or 3. It seems slower than iPad, but also have in mind that iPad uses the animation that lasts about a second itself. Anyway, should be faster, I agree, although I think it's only a little worse on this video than what I normally experience, so if there's a speed issue, it's not rotation issue, but a general one. Try different power modes and be sure to update to .26 firmware.
Edit: Sorry, after looking at it for the second time and in the full-screen mode now, I can see what you mean - there's a black bar that gets updated later. It certainly shouldn't be this way. I had similar issues with pdf rendering in the power-saving mode. What settings are you on?
The thing about wallpaper misguided me a bit though.
lardo5150 said:
I dont have mine yet, but compared to my wife's ipad2, with whats in the video, it seems there is a lot of lag?
Shouldnt that thing turn almost a second after you have turned it?
Click to expand...
Click to collapse
No, that is not "real" lag, it has been included to make sure you really want to turn it to landscape for example (as far as I know).
On my galaxy nexus with 4.1 the lag seems to have gone, seems to me like they disabled it there.
So just wait for 4.1 if you don't like the "lag".
But thats not the point. d14b0ll0s, you correctly recognized the black bar, and the picture itself seems to zoom in and out sometimes, aligning itself to the left, to the right and then in the center.
But I don't know what to do, is that definitely not the case on your device? Am I really the only one?
In that case I have to hardreset it
Not only do hard reset, but - what's more important - try re-flashing firmware (you can actually start with it). If the problem remains, return the device. I'm definitely not getting anything like that.
Use Titanium Backup or MyBackup if you have something you don't want to lose and copy the files to your PC.
Problem solved
You'd never guess what caused the problem:
_Wallpaper Wizardrii_
Deleted that and it's gone
paysen said:
Problem solved
You'd never guess what caused the problem:
_Wallpaper Wizardrii_
Deleted that and it's gone
Click to expand...
Click to collapse
Geeze, of all things
Nice job man.
Glad it's solved, but you should've mentioned you're using apps changing your desktop / wallpaper behaviour in any way.
BTW, I knew there was a reason not to like this app in the first place
lardo5150 said:
Geeze, of all things
Nice job man.
Click to expand...
Click to collapse
Luckily I haven't done a hard reset before recognizing the sh***y impact of the app
d14b0ll0s said:
Glad it's solved, but you should've mentioned you're using apps changing your desktop / wallpaper behaviour in any way.
BTW, I knew there was a reason not to like this app in the first place
Click to expand...
Click to collapse
I really should have mentioned this, but forgot it. And it's on the 2nd site of my app-launcher, just started it one time ;D
so prior to being on venom 4.2, i was on venom 3.xx. i had no problems prior.
i flash 4.2, and had no problems related to the camera not working. i had other problems though, after reflashing 4.2 those problems went away, but now a new problem came up.
after a restart, i can use the camera maybe once, or take one photo. after that, the screen through the camera will be frozen on screen. i can still take pictures, but it will only be off what is on the screen. after closing the camera, or force closing it,upon trying to open the camera app again, it barely loads, then force closes automatically and i get an "unable to start camera" bubble on screen. i can see only the grid outline of the camera, off center and such very briefly ontop of my wallpaper.
i can do a reset on my phone, and resume taking pictures, sometimes i am fine to continue, other times its the same problem. this is a very common recurring problem for me.
looking at my apps, i see 2 cameras installed, one is the new 5.0, and the other is the old 4.xx camera. i have frozen the 4.xx camera before through titanium, and it doesnt fix it. should i uninstall the 4.xx camera altogether?
subsequent reflashing of this rom doesnt fix this issue. and i dont know what else to do rather than reflashing the rom from a blank slate. previous reflashings have been on top of the current rom.
i would rather not have to start new as this phone has crappy amoint of space, and i cannot back up all my apps and settings.
i dont know if it is kernel related. prior to 4.2 i was using elemental x, after 4.2 i switched to beastmode since i wasnt soff.
is there perhaps a way i can manually start the camera through root browser?
If you've got both versions of camera in your app drawer I'm guessing you dirty flashed the ROM, which has most likely caused your problems. Clean flash the ROM and see if it fixes your issue. This is why I'm totally against dirty flashing anything.
I don't understand how you don't have space to back up your apps, I have a backup of every app I've ever used and still have tons of space left over. The fact that you mention backing up settings troubles me, restoring system settings after flashing a new ROM will more than likely cause problems for you.
When you're flashing a ROM don't do it the lazy way, do it the right way, perform a full wipe (cache/dalvik cache/factory reset/system) and start clean. It only takes a few minutes to setup your ROM from scratch. Restore your apps but don't restore any system data.
Sent from my Evita
thanks for the reply.
as suggested, I did a complete reset. wiped the caches, factory reset, and system reset.
installed from scratch. But i am still having the camera issue?
now its just not loading at all. black screen, then close. no error message. and no unable to start message.
could it perhaps be a hardware issue at this point?
without restoring anything, under apps, I still see two instances of the camera app. one at 5.1, and one at 4.2.2. can anyone confirm this is normal?
the only thing out of the ordinary, within the past few months, my phone has been getting crazy hot at times. specifically right below the lens of the rear camera. I was getting this heat from charging, or even certain apps. Definitely attribute that to the age of the phone. as apps that ran smooth when the phone was new, no longer are so.
I dont know if the heat can cause hardware damage?
also, not sure how relevant this is in the context of my situation. but apps that use the camera do not work either when the camera is needed, such as snapchat and instagram.
Since the clean flash did you at least end up with only the more recent version of the camera in your app drawer? You could be looking at some kind of hardware malfunction, or even a problem with the ImageSense proprietary chip that is utilised to operate the camera. The fact that the camera works sometimes would suggest that all is not lost. Have you tried flashing an aosp ROM to see if anything changes? I'd suggest trying that, and if that doesn't work you should try running an RUU to see if a completely stock setup will help.
The phone heating up near the camera lens isn't abnormal for this device. The amount that it heats up can change significantly depending on the ROM/kernel that you're running. You should definitely try not to use CPU intensive apps while the device is charging.
Sent from my Evita
timmaaa said:
Since the clean flash did you at least end up with only the more recent version of the camera in your app drawer? You could be looking at some kind of hardware malfunction, or even a problem with the ImageSense proprietary chip that is utilised to operate the camera. The fact that the camera works sometimes would suggest that all is not lost. Have you tried flashing an aosp ROM to see if anything changes? I'd suggest trying that, and if that doesn't work you should try running an RUU to see if a completely stock setup will help.
The phone heating up near the camera lens isn't abnormal for this device. The amount that it heats up can change significantly depending on the ROM/kernel that you're running. You should definitely try not to use CPU intensive apps while the device is charging.
Sent from my Evita
Click to expand...
Click to collapse
no, the clean flash still left both cameras in my "manage apps", i have never seen two camera icons in my app drawer.
as of right now, i cannot get the camera to run in any way. even with a reboot. The only reason I really did the clean reflash, was because the camera wasnt working at all today. I did a bit more digging around, and it seems like this is a fairly common problem for the one x. there seems to be quite a few people, even on stock roms, that cannot seem to remedy this. and a few have chalked it up to a hardware problem, some have been confirmed, and others not so much.
I really dislike flashing this phone. ive encountered so many hiccups and scares(mainly a few soft bricks here and there). I really prefer the "if its not broken, it doesnt need fixing approach" here, granted my camera is shot.
one of the reflashes today was giving me wifi errors with wifi not even turning on. I really want to avoid potentially more problems, unless a fix is deemed more definite. Thank you for all your help timmaaa!
im just in need of a new phone now. so many problems, and so many things the phone can no longer do effectively. random reboots, overheating, battery life, even the charging rate. this phone has become crap. Ive always hated the lack of expandable memory. I really dont know why I didnt choose a different phone over this at the time.
i really like the htc one, but i feel like many of the nuisances in the one X will follow over.
chinaman_chong said:
no, the clean flash still left both cameras in my "manage apps", i have never seen two camera icons in my app drawer.
as of right now, i cannot get the camera to run in any way. even with a reboot. The only reason I really did the clean reflash, was because the camera wasnt working at all today. I did a bit more digging around, and it seems like this is a fairly common problem for the one x. there seems to be quite a few people, even on stock roms, that cannot seem to remedy this. and a few have chalked it up to a hardware problem, some have been confirmed, and others not so much.
I really dislike flashing this phone. ive encountered so many hiccups and scares(mainly a few soft bricks here and there). I really prefer the "if its not broken, it doesnt need fixing approach" here, granted my camera is shot.
one of the reflashes today was giving me wifi errors with wifi not even turning on. I really want to avoid potentially more problems, unless a fix is deemed more definite. Thank you for all your help timmaaa!
im just in need of a new phone now. so many problems, and so many things the phone can no longer do effectively. random reboots, overheating, battery life, even the charging rate. this phone has become crap. Ive always hated the lack of expandable memory. I really dont know why I didnt choose a different phone over this at the time.
i really like the htc one, but i feel like many of the nuisances in the one X will follow over.
Click to expand...
Click to collapse
There's nothing wrong with this phone. Given the right amount of knowledge and care the thing doesn't skip a beat. Even though there is no such thing as a soft brick (a phone is either bricked or it isn't), whatever it is that people experience in those so called "soft brick" instances is caused by user error 99% of the time. I've seen it time and time again.
Any phone available on the market can experience any amount of issues if it isn't handled correctly. You got unlucky and your camera is most likely shot, but any other problem you've encountered comes with the territory of flashing unofficial firmware and software, it isn't anything wrong with the device itself. These are possibilities you need to be comfortable with if you're going to modify your device.
Yea, I assumed there were gonna be risks when I rooted my phone. Dont know if any of the issues I had were related to rooting or not.
The soft brick scare I had was due to a flash that went wrong for no apparent reason.
another update on my phone. I noticed my front facing camera has no issues whatsoever. unluckily for me, I cannot even access my camera, to toggle to the front facing camera to even attempt to check it out. Instagram also does not allow me to switch either, it just gives me an error saying it cannot connect to a camera, then closes. snapchat's rear facing camera is just a black screen for me, but it doesnt force close, so I am able to toggle to the front camera, and it works just fine.
is there a setting or something I can modify, for now, so the front facing camera is the default?
my brother's one x recently went out this year too. I am gonna try to salvage his camera, and see if it will fix my problem.
I have not taken apart this phone yet, is the camera soldered or held in with connectors?
Have you tried an RUU yet like I previously suggested?
Sent from my Evita
chinaman_chong said:
I really dislike flashing this phone. ive encountered so many hiccups and scares(mainly a few soft bricks here and there). I really prefer the "if its not broken, it doesnt need fixing approach" here, granted my camera is shot.
one of the reflashes today was giving me wifi errors with wifi not even turning on. I really want to avoid potentially more problems, unless a fix is deemed more definite.
Click to expand...
Click to collapse
If a couple hiccups and scares are too much for your, then it might be that modding phones is not for you. These types of things happen time to time to even those experienced with flashing ROMs. Occasional setbacks and troubleshooting is just part of the game. If that is too much for you, than don't play.
As timmaaa already mentioned, failure to boot is not the phone's fault; and its almost always a matter of user error and not following the procedures properly.
chinaman_chong said:
im just in need of a new phone now. so many problems, and so many things the phone can no longer do effectively. random reboots, overheating, battery life, even the charging rate. this phone has become crap. Ive always hated the lack of expandable memory. I really dont know why I didnt choose a different phone over this at the time.
i really like the htc one, but i feel like many of the nuisances in the one X will follow over.
Click to expand...
Click to collapse
Random software errors like random rebooting, overheating, etc. are often easily remedied with the proper steps. They are likely not issue with the phone itself, but rather a result of improper steps while flashing the ROMs. I've flashed many ROMs on this device, and have never suffered any such issues that I couldn't solve easily.
As for your other complaints about the phone (lack of expandable memory, why you didn't choose another phone), I don't know why you even posted them, as they are not constructive. Those still on this forum are mostly here because we love the phone and remain loyal to it. Your comments aren't going to help your issue, and will only annoy fans of the device. Better to keep such comments to yourself.
If you hate the phone so much, go buy another one and be done with it. But crying about it isn't going to solve anything.
I would suggest you follow timmaaa's advice, and flash the appropriate RUU to "start over". S-off is highly recommended before RUU, as running certain RUUs with S-on and SuperCID will brick the phone.
I have the same device and the same problem.
It doesn't depends of firmware or kernel or camera app..
I thought it's hardware problem but it is not. Because i was changing the camera module and it doesn't helps((
Don't know what to do with this issue(
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Same issue
You_got_owned123 said:
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Click to expand...
Click to collapse
Im having a similar problem. I cant type a single sentence without errors. It doesnt register the touch as well few times. Using a device is so sluggish.. hate it. Tried many roms with clean wipe but without any success. Would be nice if anyone could help with the above issues.
I have similar issues and I don't think it's a software issue - I have never flashed a ROM. I think it's hardware problem, probable the earthing suggested in this post:
http://forum.xda-developers.com/oneplus-one/general/fixing-ghost-touch-grounding-issue-hint-t2951000
There is an app that re-calibrates the touchscreen every time you turn it on, but it doesn't completely solve the problem for me and also prevents unlocking until it has completed, which is annoying. The fact that a re-calibration is needed to even achieve a little stability is consistent with an earthing problem.
If mine gets any worse, and I think it will, I'm going to investigate a warranty claim, but that sounds like a few weeks with no phone, which I can't tolerate.
hi, i'm experiencing the same problems. you can test this when registering 2 touches on the same Y axis (try with anyone of touch test apps).
I think that this is popping out to a lot of people in this moment because of the hot days kicking in. in fact, if your phone is cold (try to put in a fridge for 5 minutes) it will work perfectly, but when it will become hot again in your hands the touch will start to freak out again
What sucks is my phone was perfectly fine a few days ago and we've only had an increase of about 5 deg F over the week.
Occasionally the capacitive buttons don't register either.
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
My bro has the same problem, some days after flasing CM12S the screen doesn't feel as responsive anymore.
The screen isn't able to handle multiple touches anymore what makes typing really annoying, scrolling through settings also goes really slow.
Tried flashing latest 12.1 nightly but I don't think any ROM will be able to fix it.
No idea what caused it and if there is a way to fix it.
ZuLa said:
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
Click to expand...
Click to collapse
This is exactly what happened to me and it seems like it happened to a good number of people around the same time. Either 1)It's a huge coincidence 2)OnePlus rigged our phones to go haywire around this time or 3)Something in one of the nightlys got messed up for a few people however like you said, flashing new roms for kernels doesn't help anymore which makes me want to do a complete wipe - Internal data included.
Same issue
I was sure it's the heat some time back but then this touchscreen fixer app in the Themes and Apps section is actually helping. That makes me wonder if its the firmware, coz the problem only kicked off after the CM12.1 update. A few of my classmates purchased the OPO at the same time as I did and they dont have this issue (they didnt go to CM12.1).
Any tips on what firmware/ROM to revert to?
Edit: I also flashed the Oxygen OS firmware.
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
patp said:
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
Click to expand...
Click to collapse
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
TL;DR - Don't jump to conclusions that fast, weather changes aren't a strong correlation.
hyshion said:
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
Click to expand...
Click to collapse
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
goldengargoyle said:
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
Click to expand...
Click to collapse
Well I guess it's good that it's not hardware damage.
Has anyone tried going back to android 4.x to see if it helps- if it really is software?
Surprised there hasn't been more people experiencing this issue given the number of people going to android 5.x
I have the same frustrating issue
Same here, works fine in recovery. Also had this issue arise after the first bout of touch issues: https://www.youtube.com/watch?v=yoFYcFawTI4&feature=youtu.be
(clearing cache seems to alleviate that particular problem)
I think it's a software issue. I mean possibly there is hardware problems too but mine started appearing only after I installed the 5.1 update... also some things for me feel like a software issue for example when scrolling instagram back up to the top. as soon as it gets to the top it bounces back down again.. seems like software problem to me.
This is definitely a hardware issue. My phone was working perfectly. Until I went on a 5 days trip and used it for navigation, and went very hot. Up until then I was on the same CM12 rom for weeks without a problem. Since then, I've flashed many roms and the problem persists. It's definitely a hardware problem. For me it occurs whenever the phone runs a little bit hot. Practically all the time when I'm on 3G. When the phone has been in my pocket with 3G on, it's almost impossible to unlock it when I try to use it.
I contacted Oneplus a week ago and I still try to get them to RMA the phone. They've sent me all sorts of crap emails, I wiped the phone and now they ask me to shoot a video to showcase the problem. This company has the worst customer service you can find. As much as I like the pricing, I won't be bothered again with their devices. I only hope they'll RMA it otherwise I'll open it myself and try to fix the grounding issue. There is a detailed how to which also explains what's the problem.
I always had it but it was so minim that maybe couple of times a day weren't that big problem!
Just yesterday and today the issue is now intolerable! I removed the screen protector and used the stock lollipop keyboard (bcz swiftkey is kinda slower the issue was there more).
It's still very annoying and I can't type easily! I had to remove flow/swype feature to minimize it further!
Seriously considering buying another phone although I wanted to keep it for a year at least! But the hate is growing on me...
HAha exact same problem here happening since 3days.
I was on Euphoria 29/3 build. I flashed ak kernel, after reboot i couldn't type properly anymore. I was like damn, maybe its bad kernel setting or so. Didn't help.
Cleanflashed 3 roms since then, didn't solve anything. All tho touch works fine in twrp for me. So im really clueless. Swiping does seem to work better for some unknown reason to me!
The ghost swipes while typing is driving me crazy. Thinking of going back to 5.0.2 to see if that helps. Do I need to flash an old firmware to go back to a previous Android version
Hey everyone! My Nexus 5 is experiencing random reboots and does so regardless of which rom I have installed. I started by pulling logcats and didn't find anything interesting (not an expert though), so I moved on to pulling the last_kmsg and saving it to a txt file. It says the reason for the last reboot was "kernel panic," but I assume there is more to it. There has to be a message in there explaining what caused it, but to be honest, I'm not really knowledgeable enough to pull it out of what looks like 50% gibberish to me.
http://pastebin.com/315jSBZt
I would be more than happy to provide needed logs or run tests, just let me know what you need. If someone can give me a good answer that is corroborated by someone else in the community, I'll make a $5 donation to the EFF in your honor.
Possible power button issue?
audit13 said:
Possible power button issue?
Click to expand...
Click to collapse
Unlikely. Power button feels good and this phone hasn't really even been used very much. If it's a hardware issue, I think we'll find a clue in the logs. Kernels shouldn't just panic of their own accord, right?
I looked at the log you posted and I do see a kernel panic on the last line.
Does this happen with a stock ROM too?
audit13 said:
I looked at the log you posted and I do see a kernel panic on the last line.
Does this happen with a stock ROM too?
Click to expand...
Click to collapse
Yes, I've experienced this problem on the stock ROM, Cataclysm, and Chroma (what I'm using now).
Some observations that might help:
- Sometimes it reboots more frequently than others. I've had it reboot several times within 10 min. I've also say in front of my computer with logcat running, purposefully trying to make it crash, and for 30min. it didn't do anything. (I got it to eventually, but didn't find anything useful)
- I recently reflashed everything to stock including the bootloader and recovery to see if it would help. I also updated the radio to see if that would do anything.
- It boots up fairly quickly. There are no real performance issues while using the phone
- Before it crashes, it freezes for a few seconds with whatever is on the screen. You can't use any of the buttons or do anything.
- It does not require screen-on or user interaction to prompt a reboot. I've had it reboot while sleeping before and I can hear it vibrate when it hits the "google" screen.
Is there any way to identify the cause of a kernel panic? I assume that the kernel logs what it does or what it's trying to do somewhere. I'd love to be able to pull some intel out of the logs to figure out exactly what's causing it. Any other logs I should be pulling?
Sorry, this is way beyond my analytical skills. You've gone a lot further than I would.
Could the reboots be an indication that the on-board memory is starting to fail? I'm not sure.
audit13 said:
Sorry, this is way beyond my analytical skills. You've gone a lot further than I would.
Could the reboots be an indication that the on-board memory is starting to fail? I'm not sure.
Click to expand...
Click to collapse
Good call. That was one of my possible guesses too. I keep looking for evidence of that in the logs, it's gotta leave a trace somewhere! The phone is "certified refurbished" one that I bought off Amazon fairly cheap ($160-180ish). I think I'm just going to flash it back to stock and return it. Not sure what I want to get as a replacement. I might be able to beat my old Moto G (original) back into submission and use it for a while. It had some problems too, and it was worse when it comes to specs, but it was a really well thought out put together device. Never noticed the little things mattered so much until I bought my Nexus 5. I love it, don't get me wrong, but the positioning of the speaker, the slow-focusing camera, and a few other things keep it from hitting 100% for me. It's odd that two phones from the same manufacturer could be so different feeling when it comes to polish. Maybe I should buy a Moto X just so I can experience them all!
I used to have a Moto g as well. It as a great phone until I damaged the sim reader.
Although Google used to own Motorola, the nexus was made by LG which probably explains the different approaches to building a phone.
I'm okay with my lg which is a frankenphone that I clobbered together using spare parts I salvaged from cheap used nexus 5 phones I bought over a period of a few weeks.
Hi, I have a p7p. I've got the animations turned off. I'm NOT using the smooth display. When I do use the smooth display this issue seems to go away. Perhaps it's because my eye doesn't perceive the flash at the higher frequency. The flash most often seems to occur when I'm typing on the Gboard. It's like a glitch ⅓ of the way do the screen and is just a line that flashes across the entire width of the screen. Is there some way to test this? I see mention of "display checker" apps on this forum sometimes.
I am wondering if I have to RMA the phone. The flash is just a line and is for a split second, but I don't like it having paid $1000 for this phone. I don't want it to get worse after the phone is out of warranty. That's what really bugs me. If I let this go and it grows into a screen failure or something I'll be kicking myself in the butt if it fails after the warranty is expired. What even is the warranty on these phones?! I have the 512GB storage version from Google
The standard warranty is 1 year; this may be dependent on your locale.
I have yet to understand why people tend to take to the Internet to complain about problems with a device that they can get fixed for free. Not flaming anyone here, but if you're worried about the longevity of your device and whether a problem may get worse in the future, why wouldn't you just take advantage of the warranty you have?
V0latyle said:
The standard warranty is 1 year; this may be dependent on your locale.
I have yet to understand why people tend to take to the Internet to complain about problems with a device that they can get fixed for free. Not flaming anyone here, but if you're worried about the longevity of your device and whether a problem may get worse in the future, why wouldn't you just take advantage of the warranty you have?
Click to expand...
Click to collapse
Not complaining. Asking if anyone else has it. Sometimes these things are known hardware issues and if it was i have no problem starting a RMA. I was just seeing if anyone else experienced this.
Schroeder09 said:
Not complaining. Asking if anyone else has it. Sometimes these things are known hardware issues and if it was i have no problem starting a RMA. I was just seeing if anyone else experienced this.
Click to expand...
Click to collapse
It most likely is a hardware issue. If it's not happening in a specific app, and you don't have any of the display debug options enabled in Developer Options, it's probably a GPU issue.
Thanks for the help.
try disabling animation, in case it's glitching
what i notice is this phone has that animation during app switching, and other thing, which on some ocassion, doesnt really suit my taste for visual stuff, bit awkward for the eye.
otonieru said:
try disabling animation, in case it's glitching
what i notice is this phone has that animation during app switching, and other thing, which on some ocassion, doesnt really suit my taste for visual stuff, bit awkward for the eye.
Click to expand...
Click to collapse
I have animations off. I thought you hat might be part of the issue too and is why I mentioned it. With animations off a large app icon (for whatever is being switched from) momentarily pops up on the screen.
Schroeder09 said:
I have animations off. I thought you hat might be part of the issue too and is why I mentioned it. With animations off a large app icon (for whatever is being switched from) momentarily pops up on the screen.
Click to expand...
Click to collapse
in my case, it was first app in app drawer (the app doesnt need to be running for it to happen) that will pop up during animation. I think this might be launcher bugs as well.
i stop seeing it after switching to nova btw
Should Google be repairing or replacing for this? I was hoping they'd just swap me a new phone. I don't want em tearing this apart and giving it back to me. What have they been doing for everyone else?
Dude you may have a lemon. In all my years on XDA, I have never seen someone start this many threads for a single phone.
schmeggy929 said:
Dude you may have a lemon. In all my years on XDA, I have never seen someone start this many threads for a single phone.
Click to expand...
Click to collapse
One thread? I've started one thread for suspected hardware issue.