Hello everyone. We own two HTC One XLs, rooted and running CyanogenMod 10.2.1 for evita. About a month and a half ago, my phone randomly rebooted, and when it came back on, the battery had dropped to 25 percent. I can't remember what it was before that, but I'm inclined to say it was 32 or 33 percent. I thought the sudden loss of remaining battery was very strange, but this is the only time that's happened to me. After that it continued to operate and discharge as normal. My wife frequently lets her battery run low before she charges her phone. Well, yesterday afternoon her phone suddenly started rebooting. Sometimes it would get past the boot screen to the desktop, other times it wouldn't. My first thought was our messenger program. During the troubleshooting process, I plugged the phone in. I finally got it to stay on, and I noticed the battery was at 30 percent at the beginning of the charge. Well, today her phone did the SAME thing, but this time I noticed it was down to 25 percent before I plugged it in. I finally got it to power off and stay off, and after only a couple of minutes of charging, I turned the phone on and it has stayed on ever since with no problems, albeit it's still charging. At first I thought it was an app, but given that I've had trouble on both my phones when the battery is around 30 percent, give or take 5 percent, I'm beginning to think it could possibly be a driver-related (or whatever the android equivalent to a driver is) issue with Cyanogenmod 10.2.1 or Jellybean 4.3.1. So, my questions are:
-Are we the ONLY ones having this problem with their HTC One XL devices? A google search reveals random reboots are a common issue with these phones, often software related. I do not believe our problem is related to a specific app, but if their are apps known to cause reboot issues, please reply and let me know what apps these are.
-Is their any fix for this besides trying a fresh install of Cyanogenmod, or a different version of Cyanogenmod?
-Is anyone reading this part of the Cyanogenmod team, and if so, is this an issue being addressed in Cyanogenmod 11?
-Lastly, is their a link that I may submit a report to the Cyanogenmod regarding this issue if nobody here is part of the Cyanogenmod team?
Thanks, I look forward to your answers!
asilaydyingdl said:
Hello everyone. We own two HTC One XLs, rooted and running CyanogenMod 10.2.1 for evita. About a month and a half ago, my phone randomly rebooted, and when it came back on, the battery had dropped to 25 percent. I can't remember what it was before that, but I'm inclined to say it was 32 or 33 percent. I thought the sudden loss of remaining battery was very strange, but this is the only time that's happened to me. After that it continued to operate and discharge as normal. My wife frequently lets her battery run low before she charges her phone. Well, yesterday afternoon her phone suddenly started rebooting. Sometimes it would get past the boot screen to the desktop, other times it wouldn't. My first thought was our messenger program. During the troubleshooting process, I plugged the phone in. I finally got it to stay on, and I noticed the battery was at 30 percent at the beginning of the charge. Well, today her phone did the SAME thing, but this time I noticed it was down to 25 percent before I plugged it in. I finally got it to power off and stay off, and after only a couple of minutes of charging, I turned the phone on and it has stayed on ever since with no problems, albeit it's still charging. At first I thought it was an app, but given that I've had trouble on both my phones when the battery is around 30 percent, give or take 5 percent, I'm beginning to think it could possibly be a driver-related (or whatever the android equivalent to a driver is) issue with Cyanogenmod 10.2.1 or Jellybean 4.3.1. So, my questions are:
-Are we the ONLY ones having this problem with their HTC One XL devices? A google search reveals random reboots are a common issue with these phones, often software related. I do not believe our problem is related to a specific app, but if their are apps known to cause reboot issues, please reply and let me know what apps these are.
-Is their any fix for this besides trying a fresh install of Cyanogenmod, or a different version of Cyanogenmod?
-Is anyone reading this part of the Cyanogenmod team, and if so, is this an issue being addressed in Cyanogenmod 11?
-Lastly, is their a link that I may submit a report to the Cyanogenmod regarding this issue if nobody here is part of the Cyanogenmod team?
Thanks, I look forward to your answers!
Click to expand...
Click to collapse
The first thing you should try is running an RUU. You'll need s-off so if you haven't got that you'll need to do that first. Run the RUU, leave the phone stock for a few days, see if the problem still occurs or not.
I'd be really surprised if anyone from CM is reading through the q&a section of a legacy device, the correct way to submit a bug is through Jira. But you first need to completely rule out your phone or your firmware as the problem, and completely isolate CM as the definite cause before you even think about submitting a ticket on Jira.
Transmitted via Bacon
timmaaa said:
The first thing you should try is running an RUU. You'll need s-off so if you haven't got that you'll need to do that first. Run the RUU, leave the phone stock for a few days, see if the problem still occurs or not.
I'd be really surprised if anyone from CM is reading through the q&a section of a legacy device, the correct way to submit a bug is through Jira. But you first need to completely rule out your phone or your firmware as the problem, and completely isolate CM as the definite cause before you even think about submitting a ticket on Jira.
Transmitted via Bacon
Click to expand...
Click to collapse
Already updated my RUU to the one recommended in the tutorial in the forums here. Couldn't update to 10.2.1 without updating the RUU. I am trying a few things, like clearing data and reinstalling some apps. Figured it couldnt hurt. I guess its wait and see.
asilaydyingdl said:
Already updated my RUU to the one recommended in the tutorial in the forums here. Couldn't update to 10.2.1 without updating the RUU. I am trying a few things, like clearing data and reinstalling some apps. Figured it couldnt hurt. I guess its wait and see.
Click to expand...
Click to collapse
Ok. But the point of running the RUU I suggested is to see if the problem still occurs while running a completely stock setup. It's standard practice when troubleshooting.
Transmitted via Bacon
timmaaa said:
Ok. But the point of running the RUU I suggested is to see if the problem still occurs while running a completely stock setup. It's standard practice when troubleshooting.
Transmitted via Bacon
Click to expand...
Click to collapse
Right. I'm opting for simplest possibility first. I am awaiting to see if apps were indeed the cause before I take a more drastic step. So far the phone is performing as normal, was around 80 percent charge still at last check.I don't look for the problem to occur until I drop below 35 percent anyways.
fixed
asilaydyingdl said:
Right. I'm opting for simplest possibility first. I am awaiting to see if apps were indeed the cause before I take a more drastic step. So far the phone is performing as normal, was around 80 percent charge still at last check.I don't look for the problem to occur until I drop below 35 percent anyways.
Click to expand...
Click to collapse
Turns out it was an app. Problem appears to be solved. Apparently Chomp SMS became corrupted at some point.
Did a reinstall and cleared all data from the default Messaging app of good measure and the problem is gone.
same issues on CyanogenMod 11
i'm having similar problems except that i'm running CyanogenMod 11 and the phone restarts only when I have an incoming call.
does anyone have a solution to this?
gravity02 said:
i'm having similar problems except that i'm running CyanogenMod 11 and the phone restarts only when I have an incoming call.
does anyone have a solution to this?
Click to expand...
Click to collapse
If you are on CM 11, you are using a nightly or snapshot build as no release candidate or final version is available at this time. It's probably a bug in CM 11 and you'll just have to wait until it's fixed. You should stick with CM 10.2.1 final until 11 has a RC available.
Related
Since I flashed over to CM9 A6, I've noticed a few random issues and would like to know if anyone else has seen this happen on their phones.
First, when updating my apps, I've had my phone quick reboot (or possibly a crash?) in the middle of the update process. This has only happened twice so far and once it "rebooted", the update continued and I did not experience any adverse effects after.
Second, this morning when I checked my phone, I received a notification that I had 24 new emails. When I checked it, I found that these were all old emails that I had already read but were still in my inbox. Basically, it was as if I had just configured email on my phone for the first time.
I'm not exactly sure how to post log files and I'll be sure to do my research to find out but am just curious to see if anyone else has seen this happen with theirs since flashing. I did a clean wipe and install, S-ON, flashed the boot.img, etc. The phone is working as it should minus these few glitches that I've seen since flashing.
eparico said:
Since I flashed over to CM9 A6, I've noticed a few random issues and would like to know if anyone else has seen this happen on their phones.
First, when updating my apps, I've had my phone quick reboot (or possibly a crash?) in the middle of the update process. This has only happened twice so far and once it "rebooted", the update continued and I did not experience any adverse effects after.
Second, this morning when I checked my phone, I received a notification that I had 24 new emails. When I checked it, I found that these were all old emails that I had already read but were still in my inbox. Basically, it was as if I had just configured email on my phone for the first time.
I'm not exactly sure how to post log files and I'll be sure to do my research to find out but am just curious to see if anyone else has seen this happen with theirs since flashing. I did a clean wipe and install, S-ON, flashed the boot.img, etc. The phone is working as it should minus these few glitches that I've seen since flashing.
Click to expand...
Click to collapse
im s-on unlocked running alpha 6. im having none of the problems youve stated, maybe try wiping and re-flashing. the olny thing im experiencing is some battery drain
I only get a reboot when I turn on wifi or a wifi tether app, and that's so rare I can't get a logcat on it.
Sent from Spaceball One.
blackknightavalon said:
I only get a reboot when I turn on wifi or a wifi tether app, and that's so rare I can't get a logcat on it.
Sent from Spaceball One.
Click to expand...
Click to collapse
I had this happen the other day. The phone seemed to lockup for a moment, came back, then I flipped the WiFi toggle and black screen then splash screen. I don't know if I could reproduce it if I had to.
Hastily spouted for your befuddlement
Coug76 said:
I had this happen the other day. The phone seemed to lockup for a moment, came back, then I flipped the WiFi toggle and black screen then splash screen. I don't know if I could reproduce it if I had to.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
It only happens once in a few days for me. As I said, this makes it tricky to get a logcat.
Sent from Spaceball One.
wiswis said:
im s-on unlocked running alpha 6. im having none of the problems youve stated, maybe try wiping and re-flashing. the olny thing im experiencing is some battery drain
Click to expand...
Click to collapse
I've been keeping an eye on the developer thread about the battery drain and have noticed it myself. The issues I'm having aren't that big of a deal, I just thought I'd throw the question out there to see if anyone else has seen it happen with their phone. If they have, it could be worth reporting but if no one else has seen it, I'm not going to worry about it. Like I mentioned, everything is working as it should and I can deal with the random crash/reboot until the next alpha release.
Thanks to those who replied.
Hi,
I m very interested in install the official 10.2 CyanogenMod based in android 4.3, but is in Nightly phase, i am wondering how much time can take to reach a more stable version, and if is posible to follow the changes, issues and fixes in the daily releases.
I hope someone can give me orientation, thx in advance.
Of course you can. Head over to the thread Nardholio started in the Development section.
http://forum.xda-developers.com/showthread.php?t=2405310
The first post has links to: the official CM site and to the Apex Github. The CM site has a changelog for nightlies. On the Apex Github, they maintain a list of known issues.
It's all there.
I caution you on expectations here. Android 4.4 was just announced with a very unfortunate name. I think Jelly Bean 4.3 has about 60 days to live. It would be silly to expect 10.2 to be stable by then. After 4.4 hits Nexus devices, I bet the Apex guys will shift their focus to 4.4 and we will repeat some of this process...
NavarroCol said:
Hi,
I m very interested in install the official 10.2 CyanogenMod based in android 4.3, but is in Nightly phase, i am wondering how much time can take to reach a more stable version, and if is posible to follow the changes, issues and fixes in the daily releases.
I hope someone can give me orientation, thx in advance.
Click to expand...
Click to collapse
it will probably never happen.
android 4.4 is just around the corner, so i guess the focus will be swapped on that, as it was for 4.3 and 4.2 before
CyanogenMod will do a final "release" build when 10.2 is EOL which will be the most stable we can make it. We also have a last 10.1 build we consider mostly stable, although it is unofficial. Right now 10.2 does have some stability issues, but most of these will be worked out (there are some bugs in our firmware we will not be able to fix until/if Samsung updates the firmware)
Nardholio said:
Right now 10.2 does have some stability issues, but most of these will be worked out (there are some bugs in our firmware we will not be able to fix until/if Samsung updates the firmware)
Click to expand...
Click to collapse
I have random freezes/reboots all the time on the official nightlies -- even the ones people claim are stable. The lockscreen freezes quite often too. Are these known issues or am I just a lucky one? I am running CWM and followed the installation instructions on the Cyanogenmod wiki.
I just installed alogerec and hopefully something will show up to troubleshoot my issue.
Problem with 10.2 nightly as well
I have a problem with the 10.2 nightlies I have tried (all from this week) that I emailed Narholio as he requested.
But since I am a n00b and cannot post to development threads yet I could not post details there. I have not done extensive testing because the screen stays black even though the buttons light up when I try to unlock the phone. I can usually get it to display by pressing the lock button again to lock it, then pressing it again to unlock it right away. This also seems to happen only after the phone has been locked for greater than 20 seconds. If the screen timeout happens, or if press the lock button to lock it, the display almost always works if I unlock it again before 20 seconds is up.
I have not noticed any reboots or other problems, but have not used it extensively because of the black screen problem.
Try http://ls.infernix.net/jenkins/job/apexq-staging/ build 336
Sent from my SGH-T699 using XDA Premium 4 mobile app
I flashed build 336 last night and still have my phone lock up when trying to unlock it. This doesn't happen every time but when it does it either shows the back and menu buttons illuminated with a black screen or an unresponsive lock screen. In either case it will eventually reboot.
Sent from my SGH-T699 using xda app-developers app
Same problem
Nardholio said:
Try build 336
Sent from my SGH-T699 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I also still have the same problem with 336 you linked. I'm running it right now and posting this using it. I have had no reboots or other problems yet, but the black screen while trying to unlock it still plagues an otherwise really great experience. I love the speed and feel of it
I've seen that problem w/ the freezing while trying to unlock when the phone is OOM. If you can actually get it to unlock after that, check your apps memory usage.
Good idea
DOMF said:
I've seen that problem w/ the freezing while trying to unlock when the phone is OOM. If you can actually get it to unlock after that, check your apps memory usage.
Click to expand...
Click to collapse
Thanks for the suggestion. Checking memory is a good idea, although I really don't have any apps at all installed. Didn't even install gapps when I flashed this time.
Is there a preferred way to check for free memory? Terminal command?
computerinfo21 said:
I also still have the same problem with 336 you linked. I'm running it right now and posting this using it. I have had no reboots or other problems yet, but the black screen while trying to unlock it still plagues an otherwise really great experience. I love the speed and feel of it
Click to expand...
Click to collapse
Have you tried a clean install? Wipe system,data,cache then install I have not had wake-lock since early 10.1
computerinfo21 said:
Thanks for the suggestion. Checking memory is a good idea, although I really don't have any apps at all installed. Didn't even install gapps when I flashed this time.
Is there a preferred way to check for free memory? Terminal command?
Click to expand...
Click to collapse
Personally, I always forget to close browser tabs and OOM that way. Check in Settings -> Apps -> Running
Look at the apps you use as well.
When Android was introduced, they rolled it out with a set of guidelines called the application life cycle.
In the document, Google specified how to develop applications and what was available. One option for devs that is powerful is running a thread as a service. It was a feature that was supposed to be used sparingly... (A service is a program that runs all the time--unless the kernel panics and shuts down everything.)
Unfortunately, developers know that Google isn't going to do anything to push them to make quality software. The market is supposed to sort it out.
In many cases, this is not working. People are taking advantage of the lack of QA.
Bottom line: App devs are building software that leaves services running in the background all the time--for no good reason, whatsoever. Many of these services are just there to slurp up your data and send it to their servers so they can sell it.
Holding the back button to fix it? That rarely works. The devs have intentionally built their memory wasting crapware to restart the service if it gets shut down.
Plenty of free memory
croogrog said:
Have you tried a clean install? Wipe system,data,cache then install I have not had wake-lock since early 10.1
Click to expand...
Click to collapse
Yep, did wipe each time I tried multiple recent nightly versions which all do the same thing. The only one I've tried that works correctly is the 20130309 version.
DOMF said:
Personally, I always forget to close browser tabs and OOM that way. Check in Settings -> Apps -> Running
Click to expand...
Click to collapse
I generally keep a tab open to this Relay forum so I can watch what's happening, but not many tabs. Also happens immediately after flashing, without even running any apps, much less installing any.
orange808 said:
Look at the apps you use as well.
When Android was introduced, they rolled it out with a set of guidelines called the application life cycle.
In the document, Google specified how to develop applications and what was available. One option for devs that is powerful is running a thread as a service. It was a feature that was supposed to be used sparingly... (A service is a program that runs all the time--unless the kernel panics and shuts down everything.)
Unfortunately, developers know that Google isn't going to do anything to push them to make quality software. The market is supposed to sort it out.
In many cases, this is not working. People are taking advantage of the lack of QA.
Bottom line: App devs are building software that leaves services running in the background all the time--for no good reason, whatsoever. Many of these services are just there to slurp up your data and send it to their servers so they can sell it.
Holding the back button to fix it? That rarely works. The devs have intentionally built their memory wasting crapware to restart the service if it gets shut down.
Click to expand...
Click to collapse
I really haven't installed any. And when testing different nightlies I just flashed and it happens right away, didn't install a thing on them.
I decided to stay on a version for a while, so have had 20130920 since Friday, and I've used it long enough to know it is consistent. I have found another way to make it happen: incoming phone calls. When phone wakes that way it almost always happens as well. Today it finally showed the screen when I received a call, but 3 or 4 other calls the screen has just been black so I can't tell who's calling.
I discovered another thing since using this ROM for 6 days. Sometimes I get lines/bars/tearing on screen that won't go away until I lock and unlock the phone again.
I have some other phones that are broken, if I can fix one of them I might consider sending this one to a dev to temporarily play with since it seems to be the perfect test case for this problem. The screen is cracked (I got it used in this condition), which I would normally suspect to be the cause of the problem, however since it does not have either problem with stock ICS, stock JB, or the 20130309 CM I'm pretty sure it's related to something in CM10.2. Just new enough to Android I'm not sure how to track it down.
Thank you all for your help!
I have one of these "rev0 cpu" phones and just recently went back to the stock firmware (ugh) because of the lockscreen wakeup lockups. I have gone 3 days so far with no issues. Until this issue is troubleshot, this is an option for anybody who needs stability with one of these phones. I miss CM very much though.
Sent from my SGH-T699 using xda app-developers app
I also have a rev0 cpu phone, and I had a few lockup/reboots since I finally dove in last Monday (9/30) with Staging build 341. However, without me changing anything (still on the same build), they seem to have stopped. Last one I got was 10/2.
Edit: until just now. *facepalm*
TheMaskedMan said:
I have one of these "rev0 cpu" phones and just recently went back to the stock firmware (ugh) because of the lockscreen wakeup lockups. I have gone 3 days so far with no issues. Until this issue is troubleshot, this is an option for anybody who needs stability with one of these phones. I miss CM very much though.
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse
I got sick of stock so I tried CM again. After flashing the 10.2-20131014-NIGHTLY-apexqtmo nightly I have not had one reboot or lockup in days. YMMV
Edit: Still haven't had a lockup on wake or reboot.
TheMaskedMan said:
I have one of these "rev0 cpu" phones and just recently went back to the stock firmware (ugh) because of the lockscreen wakeup lockups. I have gone 3 days so far with no issues. Until this issue is troubleshot, this is an option for anybody who needs stability with one of these phones. I miss CM very much though.
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse
Hmm... I'll have to try again
Hmm... Sounds like I need to try again then. I tried one released after that and still had issues, but I will try to make some time later to try it. It is fantastic other than that problem.
newer nightlies
Anyone else having issues with the newer nightlies? I have been flashing one a week for a while now and I'm coming from the 14th. tried flashing the 21,22,and 23 all of them are giving me a boot loop at the samsung screen. I have dirty flashed, cleared cache and dalvik, updated recovery. none of them are working for me. Am I missing something? they don't work so i reflash the 14th and everything is good again.
tried in
CWM 6.0.3.7
CWM 6.0.3.8
CWM Touch 6.0.3.8
all with the same errors any help would be appreciated
This is a problem I've had persistently, I'm only just now getting annoyed enough to make a post about it.
When I first got my Nexus, everything was fine and dandy. Around the end of December though, I had this weird problem where Data turns itself off after about three seconds. I can turn it back on and let it turn off again and fight with it to solve the issue, and eventually it will stop and stay on. I figured I'd give the Cyanogenmod build (at the time) a try, and that fixed it, but had it's own problems (namely bluetooth being very horribad) so I swapped back to stock and sure enough, the problem returned. I don't recall if I did a nandroid restore or a fresh install and a titanium backup of my apps at first because I did try both, neither fixing the problem.
Nexus 5 16gig black on AT&T, stock ROM, only rooted. Any extra information can be posted upon request.
-[edit]-
I installed Paranoid Android, I'll update if I still have the issue.
-[edit+]-
Yes, the issue persists. New info is Paranoid Android v 4.2-BETA1. Obviously, hardware info stayed the same.
-[edit++]-
It appears it was an issue with Juice Defender. Will update if issue persists.
Sonic Offline said:
This is a problem I've had persistently, I'm only just now getting annoyed enough to make a post about it.
When I first got my Nexus, everything was fine and dandy. Around the end of December though, I had this weird problem where Data turns itself off after about three seconds. I can turn it back on and let it turn off again and fight with it to solve the issue, and eventually it will stop and stay on. I figured I'd give the Cyanogenmod build (at the time) a try, and that fixed it, but had it's own problems (namely bluetooth being very horribad) so I swapped back to stock and sure enough, the problem returned. I don't recall if I did a nandroid restore or a fresh install and a titanium backup of my apps at first because I did try both, neither fixing the problem.
Nexus 5 16gig black on AT&T, stock ROM, only rooted. Any extra information can be posted upon request.
-[edit]-
I installed Paranoid Android, I'll update if I still have the issue.
-[edit+]-
Yes, the issue persists. New info is Paranoid Android v 4.2-BETA1. Obviously, hardware info stayed the same.
Click to expand...
Click to collapse
Try another ROM that maybe AOSP source built, see if problem is persisting. If so, is data weak in your area for ATT and it sounds very possible your device has a hardware issue if other ROMs don't fix this. I'm running Carbon, no issues ATM. I can guarantee the CM issues and your issue are not present. If you try the ROM, problem persists, then device needs to be fixed for hardware I'd suggest.
RevelationOmega said:
Try another ROM that maybe AOSP source built, see if problem is persisting. If so, is data weak in your area for ATT and it sounds very possible your device has a hardware issue if other ROMs don't fix this. I'm running Carbon, no issues ATM. I can guarantee the CM issues and your issue are not present. If you try the ROM, problem persists, then device needs to be fixed for hardware I'd suggest.
Click to expand...
Click to collapse
It looks like it was an issue with Juice Defender.
Sorry I know I didn't mention that in the OP. :v
I'll post back if the issue continues now that Juice Defender is gone.
Sonic Offline said:
It looks like it was an issue with Juice Defender.
Sorry I know I didn't mention that in the OP. :v
I'll post back if the issue continues now that Juice Defender is gone.
Click to expand...
Click to collapse
Yes, saving battery by turning it off. Keep updated.
RevelationOmega said:
Yes, saving battery by turning it off. Keep updated.
Click to expand...
Click to collapse
It appears that was what it was. I have had zero issues since uninstalling it, which makes me sad. I liked Juice Defender, and have been using it on my phones for several years. :c
Good morning all,
I'm sure most of you are familiar with the "mm qcamera" bug. In a nutshell it is a service used by the camera that *sometimes* stays open on some nexus devices (and possibly any Android device) consuming large amounts of battery in the background. By large I mean 20% an hour sometimes more!
The bug was supposedly reported in android 4.4.2 and fixed in a later version of Android. (4.4.4? I'm not sure). I can confirm this still happens to my nexus 5 once in awhile.
Upon researching, it seems most threads are about the 4.4.2 software, however my Nexus is running 4.4.4 and is still experiencing the bug. It is hard to find anything to read on 4.4.4, most search results talk about older software.
My question is this: Is anyone experiencing this bug on their nexus 5 (or really any android device) running 4.4.4? Has anyone found a solution other than rebooting the device?
Here is some more information on the topic
https://code.google.com/p/android/issues/detail?id=70755
koszor said:
Good morning all,
I'm sure most of you are familiar with the "mm qcamera" bug. In a nutshell it is a service used by the camera that *sometimes* stays open on some nexus devices (and possibly any Android device) consuming large amounts of battery in the background. By large I mean 20% an hour sometimes more!
The bug was supposedly reported in android 4.4.2 and fixed in a later version of Android. (4.4.4? I'm not sure). I can confirm this still happens to my nexus 5 once in awhile.
Upon researching, it seems most threads are about the 4.4.2 software, however my Nexus is running 4.4.4 and is still experiencing the bug. It is hard to find anything to read on 4.4.4, most search results talk about older software.
My question is this: Is anyone experiencing this bug on their nexus 5 (or really any android device) running 4.4.4? Has anyone found a solution other than rebooting the device?
Here is some more information on the topic
https://code.google.com/p/android/issues/detail?id=70755
Click to expand...
Click to collapse
It only happens for some people and the reason behind it is unknown. For some it is a major issue, and for others it's never existed. Only way to get it to (maybe only temporarily) go away is to reboot. Not much you can do about it, but some have said it's better if camera apps are changed to user apps rather than leaving them as system apps.
Lethargy said:
It only happens for some people and the reason behind it is unknown. For some it is a major issue, and for others it's never existed. Only way to get it to (maybe only temporarily) go away is to reboot. Not much you can do about it, but some have said it's better if camera apps are changed to user apps rather than leaving them as system apps.
Click to expand...
Click to collapse
Interesting, do you think running a custom ROM or a different kernel will help... or hope and pray Android L fixes it?
koszor said:
Interesting, do you think running a custom ROM or a different kernel will help... or hope and pray Android L fixes it?
Click to expand...
Click to collapse
I doubt it, it might be a hardware driver issue, nobody knows what the real cause is. Personally I don't have this issue, I don't think another ROM or kernel will change anything much, although it's worth a shot if the drain applies to you.
It gives me a good reason to change ROMs.. haha. Ill give it some time and see what happens thanks for the quick reply so early in the morning!
koszor said:
It gives me a good reason to change ROMs.. haha. Ill give it some time and see what happens thanks for the quick reply so early in the morning!
Click to expand...
Click to collapse
Depends where you are in the world.. 10:46pm here in Australia. :angel:
But yeah, I have no idea if another ROM would fix the issue in any way. If it helps a little it's more likely because it's a clean flash, not because of the ROM itself, but who knows. Kernel won't affect this at all.
well, the camera daemon is normal to show up, especially when you use the camera or apps that use the camera. and its normal for it to take a larger % of battery than the camera app itself. what you havent really done is actually describe your problem. as far as i know, you dont have an issue, at least until you describe it. again, its normal for the camera daemon to appeae. now please, describe your actual problem. screenies?
---------- Post added at 11:25 AM ---------- Previous post was at 11:10 AM ----------
what's not normal is if it continues to drain battery, which i havent seen personally in a while, nor read any real complaints on it in a long time.
koszor said:
Good morning all,
I'm sure most of you are familiar with the "mm qcamera" bug. In a nutshell it is a service used by the camera that *sometimes* stays open on some nexus devices (and possibly any Android device) consuming large amounts of battery in the background. By large I mean 20% an hour sometimes more!
The bug was supposedly reported in android 4.4.2 and fixed in a later version of Android. (4.4.4? I'm not sure). I can confirm this still happens to my nexus 5 once in awhile.
Upon researching, it seems most threads are about the 4.4.2 software, however my Nexus is running 4.4.4 and is still experiencing the bug. It is hard to find anything to read on 4.4.4, most search results talk about older software.
My question is this: Is anyone experiencing this bug on their nexus 5 (or really any android device) running 4.4.4? Has anyone found a solution other than rebooting the device?
Here is some more information on the topic
https://code.google.com/p/android/issues/detail?id=70755
Click to expand...
Click to collapse
I've heard it only happens now when you leave the offending app that uses the camera (snapchat, skype, etc) running in the background. I can't confirm though as I've never had the issue even before the update.
simms22 said:
well, the camera daemon is normal to show up, especially when you use the camera or apps that use the camera. and its normal for it to take a larger % of battery than the camera app itself. what you havent really done is actually describe your problem. as far as i know, you dont have an issue, at least until you describe it. again, its normal for the camera daemon to appeae. now please, describe your actual problem. screenies?
---------- Post added at 11:25 AM ---------- Previous post was at 11:10 AM ----------
what's not normal is if it continues to drain battery, which i havent seen personally in a while, nor read any real complaints on it in a long time.
Click to expand...
Click to collapse
I can confirm I have the continual drain, unfortunately this was the other day and since then I have rebooted and charged my phone. I'm glad its only once in a while but from what I researched it should have been fixed in 4.4.4.
More info is available in the link I posted in the 1st post including screenshots and even links to XDA. The problem I have experienced a few times so far on 4.4.4 is identical to the link in OP.
bblzd said:
I've heard it only happens now when you leave the offending app that uses the camera (snapchat, skype, etc) running in the background. I can't confirm though as I've never had the issue even before the update.
Click to expand...
Click to collapse
Its gotta be snapchat, it used to lock up and soft boot my nexus 4 from a 'bug' or something like that ><
oh well, ill just have to keep an eye out for it.. I will try CM for a month or so and post my results back tho!
koszor said:
I can confirm I have the continual drain, unfortunately this was the other day and since then I have rebooted and charged my phone. I'm glad its only once in a while but from what I researched it should have been fixed in 4.4.4.
More info is available in the link I posted in the 1st post including screenshots and even links to XDA. The problem I have experienced a few times so far on 4.4.4 is identical to the link in OP.
Click to expand...
Click to collapse
do you have any apps that use the camera? and i mean any, there are many. if you used that app, and iy continued running in the background, the the camera daemon would also run in tbe background. if it is the old camera daemon issue that youre experiencing, then it would happen every time the camera is used, not occasionally. if its only once in a while, something else is causing your issue. i had the issue before, every single time i used the camera, not occasionally.
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