Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Nexus 5 crashes and drains all battery #35
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vanitasvitae
Sep 28, 2015
Oops I accidently hit the send button.
I took a look at the battery monitor and there was a big gap from ~2am (75%) untill this morning when I plugged the device into a charger (0%).
How can I see crashlogs or something else from such a crash?
vanitasvitae
commented
Sep 28, 2015
|
Oops I accidently hit the send button. I took a look at the battery monitor and there was a big gap from ~2am (75%) untill this morning when I plugged the device into a charger (0%). How can I see crashlogs or something else from such a crash? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment|
Did you have a lockscreen password set before encrypting? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vanitasvitae
Sep 28, 2015
Yes I did. Then I encrypted, then changed to pin, noticed, that also the encryption password is now a pin and finaly changed the encryption password back to a password.
vanitasvitae
commented
Sep 28, 2015
|
Yes I did. Then I encrypted, then changed to pin, noticed, that also the encryption password is now a pin and finaly changed the encryption password back to a password. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Sep 28, 2015
Contributor
Crash logs for applications would be in /data/tombstones or /data/anr. Logcat output isn't persistent by default so I doubt there are any useful logs around.
I'm not really sure why you think it crashed though. I don't have anything to go from here. It's possible that the battery monitoring is very inaccurate (not because of CopperheadOS though).
|
Crash logs for applications would be in I'm not really sure why you think it crashed though. I don't have anything to go from here. It's possible that the battery monitoring is very inaccurate (not because of CopperheadOS though). |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vanitasvitae
Sep 28, 2015
I cant find any logs for the specific period of time in these directories.
I dont think, the battery monitoring is THAT inaccurate. Will see, if it happens another time, maybe I can deliver more information then.
I cant imagine, that the battery drained from nothing. This morning I recharged my phone to 100% and now it's still at 76%.
vanitasvitae
commented
Sep 28, 2015
|
I cant find any logs for the specific period of time in these directories. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vanitasvitae
Sep 29, 2015
One question (I dont want to open a new issue for that): Is tge "bug" where Android shouts out the names of all known wifi networks fixed in cyanogen/copperheadOS? I used to have Wifi Privacy Police installed on my devices and I wonder, if copperhead could implement this feature/include the app by default.
https://f-droid.org/repository/browse/?fdfilter=wifi&fdid=be.uhasselt.privacypolice&fdpage=2
vanitasvitae
commented
Sep 29, 2015
|
One question (I dont want to open a new issue for that): Is tge "bug" where Android shouts out the names of all known wifi networks fixed in cyanogen/copperheadOS? I used to have Wifi Privacy Police installed on my devices and I wonder, if copperhead could implement this feature/include the app by default. https://f-droid.org/repository/browse/?fdfilter=wifi&fdid=be.uhasselt.privacypolice&fdpage=2 |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Sep 29, 2015
Contributor
It's something that needs to be done by the OS itself, not an app. It's not possible to use apps for stuff like this because Android will happily kill app-level services at any time.
|
It's something that needs to be done by the OS itself, not an app. It's not possible to use apps for stuff like this because Android will happily kill app-level services at any time. |
thestinger
changed the title from
Necus 5 crashes and drains all battery
to
Nexus 5 crashes and drains all battery
Sep 29, 2015
thestinger
added
the
unconfirmed
label
Sep 29, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
polyzen
Sep 29, 2015
That would be a great addition. A quick look at the reviews shows there are
issues with wifi login webpages. Worth a separate issue!
On Tue, Sep 29, 2015 at 1:14 PM, Daniel Micay notifications@github.com
wrote:
It's something that needs to be done by the OS itself, not an app. It's
not possible to use apps for stuff like this because Android will happily
kill app-level services at any time.—
Reply to this email directly or view it on GitHub
copperhead#35 (comment).
polyzen
commented
Sep 29, 2015
|
That would be a great addition. A quick look at the reviews shows there are On Tue, Sep 29, 2015 at 1:14 PM, Daniel Micay notifications@github.com
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vanitasvitae
Sep 30, 2015
My phone froze crashed again this night. When I pushed the power button a few minutes ago, the screen went on and showed the time 0:27 and 98% battery. But then it doesnt respond to any more button clicks or gestures. I restarted it by long pressing the power button and now it works again (53% battery).
I would really love to gibe you more advanced logs. Is there some kind of app that does more advanced and persistent logging?
vanitasvitae
commented
Sep 30, 2015
|
My phone froze crashed again this night. When I pushed the power button a few minutes ago, the screen went on and showed the time 0:27 and 98% battery. But then it doesnt respond to any more button clicks or gestures. I restarted it by long pressing the power button and now it works again (53% battery). I would really love to gibe you more advanced logs. Is there some kind of app that does more advanced and persistent logging? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vanitasvitae
Sep 30, 2015
I searched Cyanogens Issue tracker and found theese two issues that may be my problem:
https://jira.cyanogenmod.org/browse/CYAN-5867?jql=text%20~%20%22hammerhead%20freeze%22
vanitasvitae
commented
Sep 30, 2015
|
I searched Cyanogens Issue tracker and found theese two issues that may be my problem: https://jira.cyanogenmod.org/browse/CYAN-5867?jql=text%20~%20%22hammerhead%20freeze%22 |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Sep 30, 2015
Contributor
The useful logs can be obtained with running adb logcat if you hook it up to a computer and enable adb in the developer settings. It may not work after the problem occurs though...
|
The useful logs can be obtained with running |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vanitasvitae
Oct 1, 2015
The CyanogenMod Issue post suggests trying another kernel. Is that also possible for copperhead or are there vital changes in copperheads kernel?
vanitasvitae
commented
Oct 1, 2015
|
The CyanogenMod Issue post suggests trying another kernel. Is that also possible for copperhead or are there vital changes in copperheads kernel? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment|
Using another kernel would mean not having PaX. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vanitasvitae
Oct 2, 2015
Thats a shame. Is nobody else having this problem? My phone is dead every morning. Only exception is when I plugged it to a charger over night, but I dont like that.
vanitasvitae
commented
Oct 2, 2015
|
Thats a shame. Is nobody else having this problem? My phone is dead every morning. Only exception is when I plugged it to a charger over night, but I dont like that. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
polyzen
Oct 2, 2015
I am not. The other night, my battery was ~30 when I went to bed, and 23
when I woke up. More drain than I'd like, but..
On Fri, Oct 2, 2015 at 7:53 AM, vanitasvitae notifications@github.com
wrote:
Thats a shame. Is nobody else having this problem? My phone is dead every
morning. Only exception is when I plugged it to a charger over night, but I
dont like that.—
Reply to this email directly or view it on GitHub
copperhead#35 (comment).
polyzen
commented
Oct 2, 2015
|
I am not. The other night, my battery was ~30 when I went to bed, and 23 On Fri, Oct 2, 2015 at 7:53 AM, vanitasvitae notifications@github.com
|
thestinger
added
the
Type: bug
label
Oct 5, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vanitasvitae
Oct 5, 2015
I realized, that the crash doesn't appear, when I have an Alarm set on the next morning. That's strange. Maybe it has to do with wake ups of the phone?
vanitasvitae
commented
Oct 5, 2015
|
I realized, that the crash doesn't appear, when I have an Alarm set on the next morning. That's strange. Maybe it has to do with wake ups of the phone? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment|
Is this still happening on the latest builds? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vanitasvitae
Oct 13, 2015
I had a series of frequent crashes (even with alarm set) on build cm-12.1-20151009-UNOFFICIAL recently.
Currently downloading build cm-12.1-20151013-UNOFFICIAL. Is that the build you mean?
vanitasvitae
commented
Oct 13, 2015
|
I had a series of frequent crashes (even with alarm set) on build cm-12.1-20151009-UNOFFICIAL recently. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 13, 2015
Contributor
Yeah, that one. I wouldn't expect many changes since 20151013 though. By crashes, what exactly do you mean? Are you interacting with the device when it happens?
Also, do you have gapps installed?
|
Yeah, that one. I wouldn't expect many changes since 20151013 though. By crashes, what exactly do you mean? Are you interacting with the device when it happens? Also, do you have gapps installed? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vanitasvitae
Oct 13, 2015
Well I think the device itself is still working...
It happens only when I have my phone laying around. Never happened when I had it in my hand or pocket.
When it crashed and I try to turn the screen on, nothing happens (sometimes it vibrates once when I tap the volume rocker before pushing the power button. So maybe just the UI froze?
Only thing I can do is to reboot the phone by long clicking the power button. Most times I recognize a huge battery drain and when I take a look at the battery monitoring there is just white space for the time the phone was "crashed".
I installed OpenGApps arm-5.1 pico package.
vanitasvitae
commented
Oct 13, 2015
|
Well I think the device itself is still working... I installed OpenGApps arm-5.1 pico package. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vanitasvitae
Oct 13, 2015
Updated successful. The crashes mostly happen at night, so maybe I can give you feedback tomorrow. One idea I have: Can the crash occur due to temperature changes? At night I lay my phone on the window ledge with the window half opened (~12-15°Celsius). That's just a thought.
vanitasvitae
commented
Oct 13, 2015
|
Updated successful. The crashes mostly happen at night, so maybe I can give you feedback tomorrow. One idea I have: Can the crash occur due to temperature changes? At night I lay my phone on the window ledge with the window half opened (~12-15°Celsius). That's just a thought. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 13, 2015
Contributor
I don't know about that. If this is happening regularly, you could try vanilla CyanogenMod for a while to figure out if it's actually related to CopperheadOS.
|
I don't know about that. If this is happening regularly, you could try vanilla CyanogenMod for a while to figure out if it's actually related to CopperheadOS. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vanitasvitae
Oct 13, 2015
Thats a good Idea. Is it possible to dualboot with MultiROM-Managger and disk-encryption turned on? I tried that a few months ago with ubuntu-phone, but it didn't work.
vanitasvitae
commented
Oct 13, 2015
|
Thats a good Idea. Is it possible to dualboot with MultiROM-Managger and disk-encryption turned on? I tried that a few months ago with ubuntu-phone, but it didn't work. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 13, 2015
Contributor
Not sure. If it works with CyanogenMod, it would work with CopperheadOS too.
|
Not sure. If it works with CyanogenMod, it would work with CopperheadOS too. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vanitasvitae
Oct 13, 2015
MutliROM needs a kernel that supports kexec-hardboot. Can I use another kernel temporarily?
vanitasvitae
commented
Oct 13, 2015
|
MutliROM needs a kernel that supports kexec-hardboot. Can I use another kernel temporarily? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 13, 2015
Contributor
Using another kernel would mean not having PaX and MAC randomization. PaX could be the source of whatever error you're encountering, so you'd need to make sure that wasn't it. It wouldn't make much sense to use a setup like that in the long-term since PaX is a big part of CopperheadOS.
|
Using another kernel would mean not having PaX and MAC randomization. PaX could be the source of whatever error you're encountering, so you'd need to make sure that wasn't it. It wouldn't make much sense to use a setup like that in the long-term since PaX is a big part of CopperheadOS. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vanitasvitae
Oct 13, 2015
Well, I think if the error occurs after the update and I have enough time, I will flash CM to see, whether it is CopperheadOS related or not. I'm hoping for the best though :)
vanitasvitae
commented
Oct 13, 2015
|
Well, I think if the error occurs after the update and I have enough time, I will flash CM to see, whether it is CopperheadOS related or not. I'm hoping for the best though :) |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
polyzen
Oct 14, 2015
I take it it's a bad idea to enable kexec-hardboot for chos?
On Tue, Oct 13, 2015 at 3:49 PM, vanitasvitae notifications@github.com
wrote:
Well, I think if the error occurs after the update and I have enough time,
I will flash CM to see, whether it is CopperheadOS related or not. I'm
hoping for the best though :)—
Reply to this email directly or view it on GitHub
copperhead#35 (comment).
polyzen
commented
Oct 14, 2015
|
I take it it's a bad idea to enable kexec-hardboot for chos? On Tue, Oct 13, 2015 at 3:49 PM, vanitasvitae notifications@github.com
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 14, 2015
Contributor
I don't intend to deviate from CyanogenMod when it comes to features that aren't related to privacy / security, especially when it comes to adding new features (i.e. new attack surface).
|
I don't intend to deviate from CyanogenMod when it comes to features that aren't related to privacy / security, especially when it comes to adding new features (i.e. new attack surface). |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 14, 2015
Contributor
So if you want something like that you should get CyanogenMod to do it.
|
So if you want something like that you should get CyanogenMod to do it. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vanitasvitae
Oct 14, 2015
Bug is not fixed, phone was dead again. Am I the only one with this problem/the only one with an encrypted Nexus 5?
vanitasvitae
commented
Oct 14, 2015
|
Bug is not fixed, phone was dead again. Am I the only one with this problem/the only one with an encrypted Nexus 5? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 14, 2015
Contributor
Well, I'm not running into it and I use a Nexus 5 with CopperheadOS as my phone. I haven't heard of anyone else with the issue and there are other people using it too. I'm less sure about the stability on the S4.
|
Well, I'm not running into it and I use a Nexus 5 with CopperheadOS as my phone. I haven't heard of anyone else with the issue and there are other people using it too. I'm less sure about the stability on the S4. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 14, 2015
Contributor
I would need logs and other information to be able to approach the problem at all. Right now I don't have anything to go by.
|
I would need logs and other information to be able to approach the problem at all. Right now I don't have anything to go by. |
thestinger
added
the
upstream
label
Oct 14, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 14, 2015
Contributor
There are some people on #cyanogenmod on freenode with similar issues BTW.
|
There are some people on #cyanogenmod on freenode with similar issues BTW. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
Heimdal300
Oct 14, 2015
I can copy that. I use CM 12.1 on Nexus 5, with device encryption, different passwords and my phone goes off every 5 min if its on battery, although its well charged.
Heimdal300
commented
Oct 14, 2015
|
I can copy that. I use CM 12.1 on Nexus 5, with device encryption, different passwords and my phone goes off every 5 min if its on battery, although its well charged. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
bowlofeggs
Oct 14, 2015
I have just reported this issue upstream: https://jira.cyanogenmod.org/browse/CYAN-7060
bowlofeggs
commented
Oct 14, 2015
|
I have just reported this issue upstream: https://jira.cyanogenmod.org/browse/CYAN-7060 |
thestinger
removed
the
unconfirmed
label
Oct 14, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 14, 2015
Contributor
(and I do use encryption on my Nexus 5, and have a matching radio version to the one in that bug report, so those things alone aren't the cause)
|
(and I do use encryption on my Nexus 5, and have a matching radio version to the one in that bug report, so those things alone aren't the cause) |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Oct 14, 2015
Contributor
So there are actually 2 models of the Nexus 5: D820 (North America) and D821. I'm curious if this only happens on one of them. It has it printed on the back of the phone in a barely legible font right underneath the LG logo.
|
So there are actually 2 models of the Nexus 5: D820 (North America) and D821. I'm curious if this only happens on one of them. It has it printed on the back of the phone in a barely legible font right underneath the LG logo. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment|
I have a D820. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
bowlofeggs
commented
Oct 14, 2015
|
I checked the back and I also have the D820. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment|
Ah, so that's not it either. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
Heimdal300
commented
Oct 14, 2015
|
Just to complete: I have D821. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vanitasvitae
commented
Oct 14, 2015
|
Im also using a D821. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
polyzen
Oct 14, 2015
D820 here. No crashes. Looking forward to Marshmellow and the battery life improvement
polyzen
commented
Oct 14, 2015
|
D820 here. No crashes. Looking forward to Marshmellow and the battery life improvement |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
Heimdal300
Oct 15, 2015
Must be a problem with the CM-Kernel. Yesterday I flashed ElementalX-N5-4.09-Kernel (http://elementalx.org/devices/nexus-5/) on my phone and this solved the problem. Perhaps a temporary solution for people with the same problem on Copperhead.
Heimdal300
commented
Oct 15, 2015
|
Must be a problem with the CM-Kernel. Yesterday I flashed ElementalX-N5-4.09-Kernel (http://elementalx.org/devices/nexus-5/) on my phone and this solved the problem. Perhaps a temporary solution for people with the same problem on Copperhead. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
polyzen
Oct 15, 2015
@Heimdal300:
thestinger commented 2 days ago
Using another kernel would mean not having PaX and MAC randomization. PaX could be the source of whatever error you're encountering, so you'd need to make sure that wasn't it. It wouldn't make much sense to use a setup like that in the long-term since PaX is a big part of CopperheadOS.
Just in case you had not noticed..
polyzen
commented
Oct 15, 2015
|
@Heimdal300:
Just in case you had not noticed.. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
polyzen
Oct 20, 2015
Apparently we can use MultiRom. Thanks to razorloves from #cyanogenmod for sharing this.
http://forum.xda-developers.com/google-nexus-5/orig-development/mod-multirom-v24-t2571011
Comes with a nice big warning saying, "It is dangerous."
polyzen
commented
Oct 20, 2015
|
Apparently we can use MultiRom. Thanks to razorloves from #cyanogenmod for sharing this. http://forum.xda-developers.com/google-nexus-5/orig-development/mod-multirom-v24-t2571011 |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vanitasvitae
Nov 30, 2015
Since there were no crashes for me for a very ling time, I would consider this Issue as closed.
vanitasvitae
commented
Nov 30, 2015
|
Since there were no crashes for me for a very ling time, I would consider this Issue as closed. |
vanitasvitae commentedSep 28, 2015
Hi
I lately installed Copperhead on my Nexus 5 and encrypted the OS.
This night my phone must have been crashed or something but the next morning it was dead (I had aeound 75% battery before)