Database Info

Nexus 5 keeps crashing/rebooting

Hey guys,
I just picked up my Nexus 5 and I noticed especially on cameras my camera stops responding and I can't even click "OK" or "Cancel" it's just frozen and i have to reboot it. THis happened to me 10 times in the last hour now... any ideas?

did you do anything to the phone?
root anything.
everything is stock?

Mine does the same thing. It was doing this from day one and now it keeps doing it after I rooted..
Not sure what the issue is, but I probably have to restart my phone about once every three days.
Oh btw, I use face unlock so its really annoying when the camera stops working

I would suggest using this
http://forum.xda-developers.com/showthread.php?t=2513937
or this toolkit: http://forum.xda-developers.com/showthread.php?t=2517778
restore to stock completely, break the root and see what happens.
edit: this one as well I think it will be easiest and then try again. http://forum.xda-developers.com/showthread.php?t=2525026
need more information if you are loading a custom rom/ kernel etc. I know you probably are not but we cannot assume anything.

My Nexus 5 does this even after a full refresh mainly when not touching it. I updated to 4.4.1 and still no luck. Did you resolve yours?

ssconceptz said:
My Nexus 5 does this even after a full refresh mainly when not touching it. I updated to 4.4.1 and still no luck. Did you resolve yours?
Click to expand...
Click to collapse
My Nexus 5 is constantly rebooting itself every 5 seconds. There's no time to try any recovery option while it is turning on because it turns off immediately. Do you have any possible solution for this issue as well?
THANKS!

[Q] Problem with my N5 when it heats up.

Hi,
Not sure if this is the right forum thread, but recently having lots of problem with my N5.
i have a 32GB N5, when I use LTE & Location on the road, it heats up, the screen starts flickering and eventually, gets to a point when I don't see anything, I have to wait for it to cool down, turn off from recovery by guessing and after 15-20-30 mins, it will be back to Normal. Is this an issue with N5 or is it just with mine.
I bought it from Craigslist, so I do not have any warranty info. not sure if I can get it replaced.
I have used many many different ROMs on my N5, it was unlocked & I rooted it. Currently I am running stock rooted with Faux kernel with Gravitybox for customizations.
Any help would be appreciated.
TIA,
Dhaval.

From the way it is described it is way more than just software especially with screen flickering clearly this isn't an issue with every nexus 5 or Google would have addressed it immediately.. I would restore back to complete stock and see if it still does it. Too bad you bought it from some guy off craigslist, he probably knew about the problem and just didn't RMA it.
There is a Q&A forum.

Do you get some weird colored lines sort of like TV static also? Randomly, my phone does this every so often and I'm somewhat worried about it.
It only occurs in apps, on the home screen it doesn't occur.
Sent from my Nexus 5 using xda app-developers app

datallboy said:
Do you get some weird colored lines sort of like TV static also? Randomly, my phone does this every so often and I'm somewhat worried about it.
It only occurs in apps, on the home screen it doesn't occur.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
A stock Nexus 5 should be pretty well protected from over heating. I would recommending restoring the factory firmware to see if it fixes the problem. If it is still over heating then it probably needs a visit to service.

justmpm said:
A stock Nexus 5 should be pretty well protected from over heating. I would recommending restoring the factory firmware to see if it fixes the problem. If it is still over heating then it probably needs a visit to service.
Click to expand...
Click to collapse
ElementalX kernel might be making it funny. I'll go back to stock kernel first and see.
Sent from my Nexus 5 using xda app-developers app

OP
if i were you, i would download the Google N5 Image from their servers and wipe your device clean
before knowing is for sure its hardware related, i would rule out all signs of software issues first

[Q] Cyanogenmod 11-M9 crashy as hell on Hammerhead?

Is anyone else running Cyanogenmod 11 M-releases on their Nexus 5?
I just got mine a week or two ago, and the first thing I did was unlock it and flash it to CyanogenMod 11. (M8 at the time)
I'm using the device encryption, because I'm a paranoid bastard (And I love the fact this phone is actually usable while encrypted, unlike my Nexus S), and I find it very crashy. Several times per day, seemingly totally random, often while entering into the keyboard, though sometimes while it's just in my pocket. I've been able to determine no rhyme or reason.
No error messages, no apps crashing, no force closes, just several times a day it'll just freeze and reboot. Data loss is a common occurrence. I've lost my WhatsApp! database several times now, and a few others as well.
Is this just me, or is CyanogenMod 11 this crappy for other people too? I can't find a way to prove to myself that this is a hardware problem, the Android Stability Test app just keeps going and going. I've been watching adb logcat during a crash, and nothing interesting is output. Any suggestions on how to troubleshoot this?

starslab said:
Is anyone else running Cyanogenmod 11 M-releases on their Nexus 5?
I just got mine a week or two ago, and the first thing I did was unlock it and flash it to CyanogenMod 11. (M8 at the time)
I'm using the device encryption, because I'm a paranoid bastard (And I love the fact this phone is actually usable while encrypted, unlike my Nexus S), and I find it very crashy. Several times per day, seemingly totally random, often while entering into the keyboard, though sometimes while it's just in my pocket. I've been able to determine no rhyme or reason.
No error messages, no apps crashing, no force closes, just several times a day it'll just freeze and reboot. Data loss is a common occurrence. I've lost my WhatsApp! database several times now, and a few others as well.
Is this just me, or is CyanogenMod 11 this crappy for other people too? I can't find a way to prove to myself that this is a hardware problem, the Android Stability Test app just keeps going and going. I've been watching adb logcat during a crash, and nothing interesting is output. Any suggestions on how to troubleshoot this?
Click to expand...
Click to collapse
Try without encryption. It's hardly useful and only causes issues on Android.

Lethargy said:
Try without encryption. It's hardly useful and only causes issues on Android.
Click to expand...
Click to collapse
We'll have to disagree about the usefulness of encryption, (I like that if my phone is powered off, my data is PRIVATE until and unless my passphrase is entered) but I'll wipe the phone this eve, TRIM it, and get setup on it again without encryption.

starslab said:
We'll have to disagree about the usefulness of encryption, (I like that if my phone is powered off, my data is PRIVATE until and unless my passphrase is entered) but I'll wipe the phone this eve, TRIM it, and get setup on it again without encryption.
Click to expand...
Click to collapse
Maybe it's useful if you have something important on your device, but really, if you do, it shouldn't be kept on your phone anyways.
On Android, encryption is nothing but trouble, maybe it doesn't cause issues right away, but eventually it'll cause many. If you really wanted to keep things secured then I don't see why you would unlock the bootloader, flash a custom recovery and install a custom ROM.

Lethargy said:
Maybe it's useful if you have something important on your device, but really, if you do, it shouldn't be kept on your phone anyways.
On Android, encryption is nothing but trouble, maybe it doesn't cause issues right away, but eventually it'll cause many. If you really wanted to keep things secured then I don't see why you would unlock the bootloader, flash a custom recovery and install a custom ROM.
Click to expand...
Click to collapse
CyanogenMod has Privacy Guard, which is another feature I'm using, mostly with the aforementioned WhatsApp!, which has a list of permissions longer than my arm. I don't like it, but I need it for work.
I'll grant that the custom Recovery and ROM may slightly weaken the encryption (specifically an attacker could alter the ROM from Recovery), but even so having the encryption makes the phone a million times more resistant to data theft and tampering than not having it. It's worth noting that tweaking the ROM is the _worst_ an attacker could do. If I suspected such a thing had happened I could re-unlock the bootloader (which would wipe my data), and re-flash a known good Recovery and ROM. I'd lose my data, but even if the attacker had dumped the partition they still wouldn't have my key, and my data would still be private.

And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?

starslab said:
And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?
Click to expand...
Click to collapse
its more then likely the encryption. Disable it, re-flash and see what happens

No encryption. Wiped and trimmed the phone yesterday, now 4 crashes.

Try another ROM, see if it crashes. If it still does, flash factory images and see if it still does.
If so, RMA.

Nothing but trouble for me since upgrading to m9. I have been using the various M builds since March with no problems. M8 was fine. No device encryption for me. I tried turning it on and instead got stuck redoing the whole phone.
Now I get frequent crashing. I switched to the most recent nightly yesterday. Apps stopped crashing. However the os itself still crashes. Several times the screen wouldn't turn on after removing it from my pocket. The light was blinking so it definitely didn't just turn off. It also has stayed black after a few (but not all) phone calls. I've had to hard reset every time to recover.
Thinking about reverting to m8 backup. Willing to give it a few more nightie and see if it works out.

Where did you get it? I'm using the stable M9 snapshot off the CM site for hammerhead and it works pretty good.
Sent from my Nexus 5 using XDA Free mobile app

MrObvious said:
Where did you get it? I'm using the stable M9 snapshot off the CM site for hammerhead and it works pretty good.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Got it from the OTA update. Unfortunately I'm not experienced enough to know how to debug it or use proper logs. It could be that its an app I'm using combined with the most recent update...

Im using M9 snapshot too and i have not had 1 problem its been excellent

No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.

C0dy said:
No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.
Click to expand...
Click to collapse
+1. I installed another kernel (Chaos) for that reason and it's way faster.
OP: Maybe a bad flash? I would download M8 latest stable snapshot, and do OTA upgrade to M9. That's how I got mine.

C0dy said:
No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.
Click to expand...
Click to collapse
Thanks for the suggestion. I actually have been using elemental and forgot to install it after the OTA. Will put that on now and see if it helps.

starslab said:
And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?
Click to expand...
Click to collapse
cyanogenmod is not what it used to be. it ALWAYS has one type of issue or another.

simms22 said:
cyanogenmod is not what it used to be. it ALWAYS has one type of issue or another.
Click to expand...
Click to collapse
Yeah it'll never be like the GB days. There's either audio problems, crashes, or other random problems. It's sad because people are expecting it to be like it was in old days. CM is not for stability, you can quote me on that.
Sent from Tapatalk on Nexus 5

last four hours have been fine since adding elemental. Hopefully works in the long run. 8/18 nightly.
Yeah it'll never be like the GB days. There's either audio problems, crashes, or other random problems. It's sad because people are expecting it to be like it was in old days. CM is not for stability, you can quote me on that.
Click to expand...
Click to collapse
What roms do you think are more stable than CM at this time?

trobbs said:
What roms do you think are more stable than CM at this time?
Click to expand...
Click to collapse
Just about any

oneplus one touch screen problem?

touch screen sensitivity is so low, sometime it gets stuck when typing or just miss a few keys and very very annoying. is there a way to fix this ATM ? i'm not sure its software problem or my phone is defected. i flashed like 5 6 roms already but the problem still there, change to another keyboard and samething . any help ?

Software. Have to wait for an official fix
Sent from my A0001 using Tapatalk

sjhotwings said:
touch screen sensitivity is so low, sometime it gets stuck when typing or just miss a few keys and very very annoying. is there a way to fix this ATM ? i'm not sure its software problem or my phone is defected. i flashed like 5 6 roms already but the problem still there, change to another keyboard and samething . any help ?
Click to expand...
Click to collapse
I feel your pain. My situation is absolutely the same. I beleive it could have started after I used the chinese car charger and power bank on vacation. Did you use something like that?

sjhotwings said:
touch screen sensitivity is so low, sometime it gets stuck when typing or just miss a few keys and very very annoying. is there a way to fix this ATM ? i'm not sure its software problem or my phone is defected. i flashed like 5 6 roms already but the problem still there, change to another keyboard and samething . any help ?
Click to expand...
Click to collapse
The problem is in the touchscreen firmware and the fix have to be released from synaptics and not frome Oneplus.
The fact is that it may take a few or a long time based on the issue and it may be enven never be fixed, who knows.
As now i am really disappointed. They should have never release da device knowing of such a major bug.

ky3bmu4 said:
I feel your pain. My situation is absolutely the same. I beleive it could have started after I used the chinese car charger and power bank on vacation. Did you use something like that?
Click to expand...
Click to collapse
No, nothing related to the charger tho haha. the problem started as soon as i turn on the phone for the first time and it went crazy like that since then. i flashed almost every rom on here still no good. i flashed fusionjack slimsaber rom earlier and it really improved alot . you might want to check that rom out.i'm gonna stick w/ slimsaber for a while now i guess

sjhotwings said:
No, nothing related to the charger tho haha. the problem started as soon as i turn on the phone for the first time and it went crazy like that since then. i flashed almost every rom on here still no good. i flashed fusionjack slimsaber rom earlier and it really improved alot . you might want to check that rom out.i'm gonna stick w/ slimsaber for a while now i guess
Click to expand...
Click to collapse
Thx for the advice. For me the issue seems to be solved randomly when I restored the 33R in Twrp. However some other problems remain: like not getting back to the mobile Internet after leaving the wifi area or loseing the network at all ( curable by switching on and off the airplane mode or rebooting respectively).
My phone is cursed really xD

ky3bmu4 said:
Thx for the advice. For me the issue seems to be solved randomly when I restored the 33R in Twrp. However some other problems remain: like not getting back to the mobile Internet after leaving the wifi area or loseing the network at all ( curable by switching on and off the airplane mode or rebooting respectively).
My phone is cursed really xD
Click to expand...
Click to collapse
try slimsaber , it worked very good for me . and hope it work for you too

sjhotwings said:
try slimsaber , it worked very good for me . and hope it work for you too
Click to expand...
Click to collapse
I'm not sure if this is the same issue, but when you run a touch screen test, does it work with more than one touch? IE is multitouch working? I had an issue the other day and I resolved it by turning off the phone, attaching it to the charger and then turning it back on (read it on the oneplus forum). It is a known issue and they are working on bringing us the fix.
Hope this is helpful.

I have this issue too, although it's been mitigated somewhat by the most recent software patches they pushed in 30O and 33R. I'm on a CM nightly at the moment and it's certainly usable. I made the issue a lot better by disabling haptic feedback in the SwiftKey settings - it almost feels like that extra effort to run the vibrating motor causes the screen to respond badly or something.

Is it doing this?
http://youtu.be/XsGPsDP4V0U
If so this is what mine is doing and it's soooo annoying trying to type.

http://www.androidheadlines.com/201...ti-touch-issues-oneplus-one-fix-incoming.html

Some-not me, have been able to mitigate the problem by running a code through terminal emulator.
This has been brought up in CM bug log as Bacon 55.
You don't have to be rooted to do this.
Type: su (if you're rooted)
Type: cat /sys/class/input/input0/baseline_test
Press enter.
Note that you will need to do this every time you reboot your phone.
Credits to a member on jira cm. Forgot to name! Hope it works for you

I've tried everything and everything failed.
Let's hope synaptics pushes out a fix soon. I can't stand this issue. Basically two different touches near each other are recognized as a swype -_-'

i did a test using multitouch test app. i use 1 finger touch on the phone and got a red dot, finger #2 gave me a blue dot . as soon as my 2 fingers get close together 1 of the dot disappear, also test w/ 4 5 fingers same result .thats why if you text really fast , you get alot of missing words and sometime it lag and get stuck.

I think that until this gets fixed the phone will be not ready to be sold,too...
Sent from my Oneplus One

Here is a fix I have tried and it has helped me a lotttt.
https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com

DuckMcQUack said:
I think that until this gets fixed the phone will be not ready to be sold,too...
Sent from my Oneplus One
Click to expand...
Click to collapse
Is this phone worth purchasing since customer service is not readily available. I'm not sure if I want to spend my money and not be able to get quality customer service. What are your thoughts?

alhadee12 said:
Is this phone worth purchasing since customer service is not readily available. I'm not sure if I want to spend my money and not be able to get quality customer service. What are your thoughts?
Click to expand...
Click to collapse
As long as the touchscreen issue is not fixed the phone has to be considered to be bugged and faulty. I would not spend my money on a defective phone at a very few weeks from N6 release that will be a superior terminal by far.
Even if it gets fixed it will be not worthy the same as N& is near to come anyways.
I wish i didn't buy mine.

DuckMcQUack said:
As long as the touchscreen issue is not fixed the phone has to be considered to be bugged and faulty. I would not spend my money on a defective phone at a very few weeks from N6 release that will be a superior terminal by far.
Even if it gets fixed it will be not worthy the same as N& is near to come anyways.
I wish i didn't buy mine.
Click to expand...
Click to collapse
Thanks, I started becoming more concerned because users have been paying long wait times for service and possibly having to ship back to China at the customers cost. That's a bad deal.

alhadee12 said:
Thanks, I started becoming more concerned because users have been paying long wait times for service and possibly having to ship back to China at the customers cost. That's a bad deal.
Click to expand...
Click to collapse
Definitely. I would stay away from this thing.
And by the way who knows if the ghost touches/swypes problem is not even a software issue just as the multitouch not working when placing the phone on a non-conductive surface...

Question Experiencing random restarts?

Is it only me or something common? (P7P)

I haven't had any, and my wife hasn't said anything about this happening with hers, either. We've had ours for two weeks today. I'm rooted, hers is with the bootloader still locked.

Have not had a random restart since I got the phone.

Alright, possibly one of the root modules is causing some problems. thanks for the info.

Rooted, no restarts.

I have been experiencing them regularly... Usually right after i try and make a call ...
This is the first time i ever saw something like this.... Does not inspire confidence!

p_shad0w said:
I have been experiencing them regularly... Usually right after i try and make a call ...
This is the first time i ever saw something like this.... Does not inspire confidence!
Click to expand...
Click to collapse
Factory reset and use the phone with little to nothing installed and see if it still happens. If it does try a sim from another provider. If you still get them you have a faulty handset so RMA it.

I haven't experienced it with the Pixel 7 Pro but it happened sometimes with the 6 Pro.

Got one restarts just after freeze for 30 second twice. Rooted kirasakura kernel and despair both happen once

Hasn't happened once in the two weeks I've had it.

Well this is absolutely rediculous.. HORRIBLE support... Google Support wanted me to run the phone in SAFE MODE for a "a few days" to make sure it wasn'ty a third poarty app causing the reboots.. and if it still happens i will have to run around trying to find a service center to "look at the phone" eff that... Take itr back and i will go back to OnePlus or Samsung..... HORRIBLE first experience with a Pixel ... ABHORRENT

I still have one Day on my 14 day return window so i am returning the sucker and getting my money back.. I am not paying 1500$ CAD for a phone that randomly reboots when i try to initiate a call...

I had 1 random reboot during a VOIP call. Didn't notice it till my headphones told me they were disconnected, lol.
This was full stock, unlocked and rooted the day after.

p_shad0w said:
Well this is absolutely rediculous.. HORRIBLE support... Google Support wanted me to run the phone in SAFE MODE for a "a few days" to make sure it wasn'ty a third poarty app causing the reboots.. and if it still happens i will have to run around trying to find a service center to "look at the phone" eff that... Take itr back and i will go back to OnePlus or Samsung..... HORRIBLE first experience with a Pixel ... ABHORRENT
Click to expand...
Click to collapse
How is that horrible support? 90% of the time it is user error. As a few post above mentioned. Wipe phone and try it with minimal apps installed. They want you to run it in Safe Mode for a reason, if still happens send it in or find a service center. I wouldn't call that horrible support.

schmeggy929 said:
How is that horrible support? 90% of the time it is user error. As a few post above mentioned. Wipe phone and try it with minimal apps installed. They want you to run it in Safe Mode for a reason, if still happens send it in or find a service center. I wouldn't call that horrible support.
Click to expand...
Click to collapse
It is.... I have been running the exact same apps on the OnePlus 9 pro and the OnePlus 8 pro before that and there was no issues whatsover.... why would there be on the Pixel ? It is horrible support yes... I asked for an RMA

p_shad0w said:
It is.... I have been running the exact same apps on the OnePlus 9 pro and the OnePlus 8 pro before that and there was no issues whatsover.... why would there be on the Pixel ? It is horrible support yes... I asked for an RMA
Click to expand...
Click to collapse
Bare in mind this is probably thye first phone i have owned since my nokia days back in the early 2000's that is -NOT- rooted , bootloader unlocked or anything of the sort !(Yet)

I have my P7P now since the 13th of October and I had no random reboot during this time. Everything is running smooth and stable. My phone is not rooted.

I've only noticed phone crashes when using Android auto. When I try using apps that change the font and display size, that's when I run into reboots. My phone is rooted with multiple magisk modules

rester555 said:
I've only noticed phone crashes when using Android auto. When I try using apps that change the font and display size, that's when I run into reboots. My phone is rooted with multiple magisk modules
Click to expand...
Click to collapse
Just a data point: I haven't had any phone crashes when using Android Auto on the Pixel 7 Pro.

More specifically, whenever I change the screen to large screen on an app like Paramount Plus, or some other video viewing app. This is when I get the phone reset