I've had my XT926 rooted/unlocked since the original exploits surfaced. I'm now trying to update my CM11 nightly to the latest one, and I can't because "this package is for devices with 4.4 bootloader". Is there a way to update my bootloader to the 4.4 version without installing stock KK? Is it worth it? The CM11 nightly I'm trying to install is the one that I download through the CM updater through settings.
Sorry if this has been answered, I really did search here and the razr forums and couldn't find a specific answer for my device.
Raikalo said:
Is there a way to update my bootloader to the 4.4 version without installing stock KK?
Click to expand...
Click to collapse
Unfortunately, no. It involves flashing the latest Moto firmware for your device, followed by flashing a KK ROM (such as CM11).
Raikalo said:
Is it worth it?
Click to expand...
Click to collapse
In my opinion, absolutely not. Assuming you have an XT926, this device runs so much better on a JB bootloader, as I have regretfully found out. I'm not running CM11, rather another ROM, but all the problems that I've been battling (battery, GPS, WiFi, speakerphone issue, various system FCs) ever since I upgraded to a KK bootloader have completely changed my device for the worse. ymmv
Not_A_Dev said:
Unfortunately, no. It involves flashing the latest Moto firmware for your device, followed by flashing a KK ROM (such as CM11).
In my opinion, absolutely not. Assuming you have an XT926, this device runs so much better on a JB bootloader, as I have regretfully found out. I'm not running CM11, rather another ROM, but all the problems that I've been battling (battery, GPS, WiFi, speakerphone issue, various system FCs) ever since I upgraded to a KK bootloader have completely changed my device for the worse. ymmv
Click to expand...
Click to collapse
Fantastic, that pretty much answers that. I'll probably just sit tight on the JB bootloader then and avoid the hassle. Thanks for the help. Sorry to hear about your issues with the new bootloader :/
Battery life appears worse because it's more than likely poorly written apps. The API for KK had improvements made, and apps that were written before KK may have worked fine under JB, but were still poorly written but could get away with it. Once KK came out, the poorly written code was finally exposed for what it is: code that should be fixed.
Depending on how the apps are releasing resources, it could cause drain on the battery.
I myself have found my battery life to be the same as it was under JB.
One thing to really look at it is your battery stats to see if there is something waking up your phone while it's asleep. Go to Settings->Battery. Select the graph and then look at the lines below it (see attached jpg for an example).
In the screenshot attachment I've provided, compare the "Wake" line with the "Screen on" line. What you really want to see is that when the screen was off (no blue lines in the "Screen on" area), you should hopefully see minimal blue lines in in the "Awake" line in the same positions. If not, it means something is waking up your phone. In the screenshot above. you can see that there are definitely some times where my phone woke up while the screen was off. WiFi was on all the time as well. Of course, you'll probably still see some lines if you have syncing turned on, or other background processes. You might never be able to completely ensure there are no lines when the screen is not on, but you want to minimize them as best as possible. In the picture above, I was having my phone do other things (update apps, etc), but usually, I can get it minimized pretty well.
To better help determine what might be causing this issue, you can download an app from Playstore called "Wakelock Detector". Basically, charge your phone up completely, install Wakelock Detector and allow your phone to sit for about two hours without being charged and then run Wakelock Detector and see what it says. You might find you either have a lot of syncing going on (I've turned a lot of that off including gmail sync, photo sync, play books, play magazines, play movies/tvs, soundsearch, etc). Syncing is usually the #1 culprit for most people after setting up their Google accounts because they just go with whatever was set up. Or, you might find an app that seems to stay on a lot and will warrant more investigation, but it could definitely help in determining what the issue is.
I also am rooted (which does NOT affect battery life) and I run the Xposed framework with the Greenify module which helps. With this, you can "Greenify" apps - in otherwords, prevent them from causing a wakelock. Many games these days will just wakeup to give you notifications. In many, you can just go to the App Info for the app and uncheck the "Notifications" checkbox. Greenify is different from task killers. It doesn't "kill" the task (which can cause even MORE battery drain), but instead, prevents it from "waking up". The donate version allows you greenify system apps as well, but that could cause more issues. Usually, greenifying user installed apps is usually sufficient. So, if you have a misbehaving app, you can use Greenify to discipline it until it gets fixed (if ever). Or, remove the app and see if you can find a replacement.
Also, having GPS on all the time drains. Most of the time, you can either live with the battery saving mode or turn it off altogether until you need it.
On my Razr HD (non-Maxx), I can get about 72 hours before I'm down to under 10%. This is on stock or CM11.
One of the questions in the OP was (I'm paraphrasing) "Is upgrading an XT926's JB Bootloader to a KK Bootloader worth it". I answered "In my opinion, absolutely not", and I provided examples for my statement. It doesn't matter whether the apps that are available today are poorly written or not. Fact is, on my XT926, they seemed to run light years better on the JB bootloader than on the KK bootloader, as evidenced by the fact that I never had any problems with them under JB.
I am not disputing that other smartphone brands or models may run KK just fine with a KK bootloader. But my XT926 does not. Yes, I do run Greenify, and battery apps and whatnot on my device. The problems that I mentioned are still there. Granted, it is a MAXX variant, so when I say battery problems, I'm talking about having only 30% left in the tank, after putting the device through a grueling daily workload. But I used to get 2 to 3 days out of it without charging it, so it is a problem.
Not_A_Dev said:
One of the questions in the OP was (I'm paraphrasing) "Is upgrading an XT926's JB Bootloader to a KK Bootloader worth it". I answered "In my opinion, absolutely not", and I provided examples for my statement. It doesn't matter whether the apps that are available today are poorly written or not. Fact is, on my XT926, they seemed to run light years better on the JB bootloader than on the KK bootloader, as evidenced by the fact that I never had any problems with them under JB.
I am not disputing that other smartphone brands or models may run KK just fine with a KK bootloader. But my XT926 does not. Yes, I do run Greenify, and battery apps and whatnot on my device. The problems that I mentioned are still there. Granted, it is a MAXX variant, so when I say battery problems, I'm talking about having only 30% left in the tank, after putting the device through a grueling daily workload. But I used to get 2 to 3 days out of it without charging it, so it is a problem.
Click to expand...
Click to collapse
I understand and again, those are probably apps that need to be recompiled under the new KK API. Developers should always ensure their apps compile under the latest compiler to ensure they aren't doing something wrong. That is not a fault of KK, but of the app itself.
I myself have found the phone to work better for me under KK than JB, albeit there are issues with Wifi and such, but those are firmware issues, not issues with KK itself and Moto needs to address those issues.
In any case, whatever works for everyone, but I just wanted to give an explanation as to why people see battery issues. It's something that myself and other developers understand that most of your normal users (non-dev) probably don't know, and there isn't any reason as to why they would, unless they investigated it further and such.
I'm not trying to say the OP, nor you, are incorrect in your assessment of KK. I just wanted to give an explanation as to why some people do not have an issue, while others do. It would definitely be more of an issue if everyone complained of this issue.
I was part of the KK soak tests, and it was split 50/50 (possibly favored more towards those who found better battery life) on good/bad battery life after KK. That alone pretty much states it's poorly-written apps. Believe me when I say, writing an android app is completely different than it is with say a Windows app. In Windows, you don't have to worry about battery life, etc. Your windows program can run constantly. However, with phones, you have to take into account that at any time, your app can be stopped when it's no longer in the foreground. It's put into a suspended mode that could then result in it being completely removed/killed when resources (which are limited on phones) are very low and another process needs it.
Also, keeping resources locked drains batteries, or calling an out-dated API function in the kernel/system can also cause performance issues.
And in the end, it's always good to do a Factory Data Reset (FDR) whenever the upgrade is major, such as going from JB to KK. There were a lot of improvements and enhancements done within the Android framework that leaving stale cache/apps around can result in a lot of garbage that causes performance issues.
But, if JB is working better for you, then that's what counts in the end.
Just wanted to let people know that there are ways to get it working better under KK.
The only reason I am still on KK is because I am waiting to see what Moto's upcoming (presumably final) OTA KK update will do for the progress of this device. And I certainly hope that my ROM's devs would then bake those changes into the ROM. If I don't like what I see, I may consider using nobe1976's flashback script to go back to JB, seeing that I still have 7 months left on my contract for this device. But I'm not really holding my breath hoping that Moto's final soak software will fix the problems.
Not_A_Dev said:
The only reason I am still on KK is because I am waiting to see what Moto's upcoming (presumably final) OTA KK update will do for the progress of this device. And I certainly hope that my ROM's devs would then bake those changes into the ROM. If I don't like what I see, I may consider using nobe1976's flashback script to go back to JB, seeing that I still have 7 months left on my contract for this device. But I'm not really holding my breath hoping that Moto's final soak software will fix the problems.
Click to expand...
Click to collapse
Apparently, dhacker has fixed the WiFi issue with the 08/19 build of Gummy ROM. I'm currently flashing to that right now, so we'll see how that works.
There are still mic issues. Apparently, going to speaker phone when talking with someone turns off the mic for the next call and doesn't turn back on without you rebooting the phone.
I'm not sure how much Moto will fix as it appears to be now all firmware based (wifi, blue-tooth, 4g). Everything else seems to be fine, so I'm not sure what Moto will do.
iBolski said:
Apparently, dhacker has fixed the WiFi issue with the 08/19 build of Gummy ROM. I'm currently flashing to that right now, so we'll see how that works.
Click to expand...
Click to collapse
It's only a minor issue on my device right now. Occasionally (very seldom), WiFi drops off, and inexplicably reconnects by itself after a second or so. But WiFi does consume relatively large amounts of battery. That's a problem.
iBolski said:
There are still mic issues. Apparently, going to speaker phone when talking with someone turns off the mic for the next call and doesn't turn back on without you rebooting the phone.
Click to expand...
Click to collapse
That's a huge problem, and I'm experiencing this on my XT926 right now. Actually, I've had it where in the same call (not the next call), the party on the other end couldn't hear me after I switched from speaker to normal. Gets "solved" only by rebooting. That right there jeopardizes the whole concept of calling while driving.
But there's more: Navigation (which I depend on a lot) does not work correctly (loses GPS signal). Bluetooth works sometimes, and sometimes it doesn't (also bad for calling while driving). Random FCs of Playstore apps that I never experienced under JB.
Yeah these issues are exactly why I was afraid to jump ship and update the bootloader. Will it be possible to update CM11 any further without the new bootloader? I don't really need to, as my current nightly is recentish and stable, but I'm just curious.
Use the jbbl version http://download.cyanogenmod.org/?device=moto_msm8960_jbbl
DorianX said:
Use the jbbl version http://download.cyanogenmod.org/?device=moto_msm8960_jbbl
Click to expand...
Click to collapse
Thank you, I missed that addition to the website.
I think I know the answer, but just to verify: is it possible to downgrade the bootloader from KK to JB if I made the jump?
Related
im running stock rom with no mods yet (im usally a heavy softmodder but its not worth it yet)
and today epistle rom gripper and ninjump wanted to update so me not carrying updated them and for the rest of my day my phone has been rendered useless it wouldnt send text calls or go on the internet via wifi or 3g and it stopped getting a radio signal all together when i usally have full bars
so it turns out the new update to one of these programs nocked my whole phone unstable and i want to know how and why because as soon as i uninstalled them i was able to connect to the net instantly and i got my missed calls emails and text in as soon as they where gone so.
can someone shed some light on this?
have never heard of anything like that ;(
You might have to check with the respective developers of those apps. Maybe the apps you updated are not optimized for Gingerbread yet. I'm usually the first to criticize Gingerbread for its slew of glitches, but in this case, it sounds like the issue lies with the applications themselves; especially considering once you uninstall them, your phone is back to normal.
onthecouchagain said:
You might have to check with the respective developers of those apps. Maybe the apps you updated are not optimized for Gingerbread yet. I'm usually the first to criticize Gingerbread for its slew of glitches, but in this case, it sounds like the issue lies with the applications themselves; especially considering once you uninstall them, your phone is back to normal.
Click to expand...
Click to collapse
it wasn't a big loss to me because i wasnt really using the apps. but what should i email them saying hey im running 2.3 on nexus s and your app almost bricked my phone? i dont know how to get the logcat without rooting it.
dudekiller said:
it wasn't a big loss to me because i wasnt really using the apps. but what should i email them saying hey im running 2.3 on nexus s and your app almost bricked my phone? i dont know how to get the logcat without rooting it.
Click to expand...
Click to collapse
Yes, more or less. Just reach out to them (there should be an "Email the Developer" option in the Market place of every app to find their email) and tell them briefly but precisely the problems you're having. Mention you're running Gingerbread 2.3 (2.3.1 if you want to be specific) on a Nexus S. If they're good about replies, you should hear from them. Then see what happens from there.
After about one day of this GB update, what can we tell? Still any issues? Some people bricked their phones, so is there any idea why? Can we recap on what has been achieved this far? Are there any flashable ROMs with all good stuff?
The phone is still buggy. I have been having issue with BT and the phone locked up on a call once.
Basically, sometimes when I turn my BT headset off, it will still say it is connected on the phone. I will need to turn the BT off and then back on to get it to work correctly again.
As for the phone locking up. I was on BT and switched over to the speaker phone and the phone just died. I had to do a battery pull to get it to turn back on.
So it really just sounds like they need to work on BT more because I never had these issues on Froyo.
aowendoff said:
The phone is still buggy. I have been having issue with BT and the phone locked up on a call once.
Basically, sometimes when I turn my BT headset off, it will still say it is connected on the phone. I will need to turn the BT off and then back on to get it to work correctly again.
As for the phone locking up. I was on BT and switched over to the speaker phone and the phone just died. I had to do a battery pull to get it to turn back on.
So it really just sounds like they need to work on BT more because I never had these issues on Froyo.
Click to expand...
Click to collapse
Did you update the baseband?
I'm curious about this too! I was about to start a tread, but this one shall do.
Questions -
1. (People having reboots before update)
*Did it fix the reboot issue?
2. (People with signal problems before update)
*Did the new baseband fix this/ do you get better signal now??
3. Another problem I have is that wifi and 4G constantly battle each other to see which one gets the signal. So I have to turn wifi on and off until 2G/4G go away.
(For people that have this)
*Did this get solved?
4. * Does GPS lock faster/work better?
I've had three different phones and I've had same issues with all three and even trying different roms. A different rom might fix one issue, but not the others for me.
My main concern is the reboot and signal issues!
These are questions for people that have same or similar issues.
NOT for people with no issues before update.
So please NO "There is nothing wrong with my phone!" People.
Thanks!!
....
For those who are still having problems after the update it might be wise just to do a factory reset because froyo and gbread is very different...
* GPS locks much faster now, often instantly, and indoors.
* Switching between 2G/4G seems to be smoother; doesn't lose the connection for a few seconds like it used to
htc2364 said:
I'm curious about this too! I was about to start a tread, but this one shall do.
Questions -
1. (People having reboots before update)
*Did it fix the reboot issue?
2. (People with signal problems before update)
*Did the new baseband fix this/ do you get better signal now??
3. Another problem I have is that wifi and 4G constantly battle each other to see which one gets the signal. So I have to turn wifi on and off until 2G/4G go away.
(For people that have this)
*Did this get solved?
4. * Does GPS lock faster/work better?
I've had three different phones and I've had same issues with all three and even trying different roms. A different rom might fix one issue, but not the others for me.
My main concern is the reboot and signal issues!
These are questions for people that have same or similar issues.
NOT for people with no issues before update.
So please NO "There is nothing wrong with my phone!" People.
Thanks!!
....
Click to expand...
Click to collapse
I had reboot issues before and so far haven't had any, but to make a proper conclusion I'll have to wait, as even before the update sometimes I would make it days between reboots/shut offs and sometimes only hours.
GPS appears to be very good now, as for wifi/4g/2g I always turn off 2g and use only wcdma setting, and haven't had any issues with it, I leave my wifi and BT on at all times too even when not connected and don't have too bad battery strain.
some things I noticed, in the gallery now when I hit share I don't see the gmail option, the camera reverted back to stock, which is a shame because I loved the things the LG cam app had, but there are a lot of camera apps (I love vignette) so that's not a huge issue, if anyone has the lg app I would love it back though.
I did have some sluggishness especially this morning, I downloaded some widgets though so it might be more of what I added than the update itself.
one surprise was that I thought it was supposed to wipe all data etc. from the phone, but everything was set up the same as I had it before with launcher pro, so I was happy I didn't have to start from scratch. Also I have been getting occasional force closes with launcher pro that I didn't have before.
as far as quadrant scores go I'm getting consistant 2600+ so that is good, I had Faux's kernal and OC to 1300 w/ pimpmycpu and was getting 2800-3000 so without OC I'm more than happy with 2600. Now if only netflix will make it's way to this phone as is, and hopefully we can root soon as i really want ROM Manager, pimpmycpu and a few other root only apps to work again! Love this community, everyone is so helpful and creative, keep up the good work.
GPS locks Faster
Google Music Beta offline feature does NOT work, won't download.
Android Market did not restore my previous apps.
Touch screen is still dodgy, sometimes requiring multiple touches.
Email, specifically @Live.com mail will not display junk mail. Other folders, yes, but not junk.
More frequent messages about Cannot connect to Server
Has anyone figured out why some people have bricks trying to update? To be honest I still hesitate to do the update because I still don't know why this happens
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
mmapcpro said:
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
Click to expand...
Click to collapse
I think it's worth waiting for a rooted flashable version a day or two and to avoid any risks.
mmapcpro said:
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
Click to expand...
Click to collapse
<nods head and ducks>
mmapcpro said:
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
Click to expand...
Click to collapse
this ^^
even so, i had latest cwm running and i didnt brick **** lol people get so damn worried when the updating bar doesnt move consistently so they start fiddling with **** and boom! brick!
dmartin1976 said:
GPS appears to be very good now...
Click to expand...
Click to collapse
I wish that were true for me. As I've mentioned in other threads, I'm still getting 90-180 second TTFFs, which is about where I was with stock Froyo. I hope someone will reply to my question in the other thread about the system settings they have that give them such good results. I've fiddled with all of the ones in the hidden menu GPS Test section and haven't found a good combination (and I don't know what the factory settings are supposed to be any more); it's hard because of having to wait a few hours between tests to let the ephemeris data expire in the receiver so I won't just be getting a carryover hot fix.
dmartin1976 said:
some things I noticed, in the gallery now when I hit share I don't see the gmail option, the camera reverted back to stock, which is a shame because I loved the things the LG cam app had...
Click to expand...
Click to collapse
Hmm, that's strange; I still have Gmail in the list of options for "Share" in the gallery.
As for the camera, I think I actually like this one better. At least, it seems to do a better job of taking close-ups with the flash. With the original LG camera, close-up flash photos were always blown-out and overexposed. I took a couple of test shots in a dark room with the flash, and they look great, about as good as you can get with an LED flash, I think.
JHaste said:
this ^^
even so, i had latest cwm running and i didnt brick **** lol people get so damn worried when the updating bar doesnt move consistently so they start fiddling with **** and boom! brick!
Click to expand...
Click to collapse
If I recall, once you reach the % range....the install range, it tells you, do NOT disconnect. Some of the pictures people were showing were in the Analyze area, before the actual download and install. I think if you get past the analyze phase you can install. I don't believe you can get past it with CWR installed.
Even still, the anticipated failure rate of an update like this (Bricked), is like 8 digits to the right of the decimal point. Even with the problems MS had with the NODO update on the Samsungs, the total # of failures was like 8 World wide. (or just over half their sales. )
So the process is pretty well tested and known.
alodar1 said:
If I recall, once you reach the % range....the install range, it tells you, do NOT disconnect. Some of the pictures people were showing were in the Analyze area, before the actual download and install. I think if you get past the analyze phase you can install. I don't believe you can get past it with CWR installed.
Even still, the anticipated failure rate of an update like this (Bricked), is like 8 digits to the right of the decimal point. Even with the problems MS had with the NODO update on the Samsungs, the total # of failures was like 8 World wide. (or just over half their sales. )
So the process is pretty well tested and known.
Click to expand...
Click to collapse
I promise you that I did it with CWM installed... I literally restored my stock nandroid, booted into that and then ran the update tool... I only had one hiccup where after i got to the S/W screen (after I had already downloaded but before the update) it said that I did not have the phone connected so i unplugged and plugged back in and that didnt work... so I unplugged, pulled the battery, put it back in, plugged in and everything went smoothly
JHaste said:
I promise you that I did it with CWM installed... I literally restored my stock nandroid, booted into that and then ran the update tool... I only had one hiccup where after i got to the S/W screen (after I had already downloaded but before the update) it said that I did not have the phone connected so i unplugged and plugged back in and that didnt work... so I unplugged, pulled the battery, put it back in, plugged in and everything went smoothly
Click to expand...
Click to collapse
So it seems some folks just had bad luck
krekabl said:
So it seems some folks just had bad luck
Click to expand...
Click to collapse
or the file they downloaded was corrupt? its not like we had an md5 to match...
JHaste said:
or the file they downloaded was corrupt? its not like we had an md5 to match...
Click to expand...
Click to collapse
well everybody updated the same source didn't they?
GPS locks on a lot faster...but still loses accuracy in middle of route.
Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.
What firmware are you running?
Is it the same firmware on both phones?
What is the launcher?
Have you tried a different modem?
Are you using a battery saver like juice defender?
Are you using an ad blocker?
Are you using a specific kernel? Oc? Uv?
Need for specific info
ssa2204 said:
Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.
Click to expand...
Click to collapse
You know, for the rather lengthy post, you really have not explained any detail about your issue.. You have a generic 'I have an issue, the Infuse sucks' post and its not going to help anyone resolve your issue. I find it EXTREMELY hard to believe that you have 2 infuses having the SAME EXACT ISSUE. Yes, there will be times when you get a defective phone or it isnt working up to your standards, but to have 2 defective phones with the same defect? You need to play the lottery. Also, i suggest you send the phones back. It sounds like youve already made your mind up and have pretty much bashed the samsung infuse in that entire post. The same samsung infuse that myself, and plenty of other people live with day to day and have absolutely 0 complaints.
I will give you $20.00 a piece for them!!!!
ssa2204 said:
Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.
Click to expand...
Click to collapse
Simple . Hack it and put cm7 on it if you really need speed. Maybe its your screen protecter. Wipe the screen off. Cm9 can be sluggish, for speed go to miui on gingerbread or cm7
Id be willing to buy one of the infuses
Trust me...sounds like you got two defective units...which like Scott, I find hard to believe...but hey its possible-idk when you got hem.but if it hasn't been a year then put them back to stock with gtgs unbrick and file a warranty claim with Samsung...the infuse is a great phone and I never had the problem you described...I do have a question though...did you get them both at the same time? Cause I don't see why you would get a second if your first was having problems
Anyways...if you wanna sell one hmu...I may buy one depending on the price and if I can get the money (I think I already may have one lined up for $170 just need to get the money)
Sent from my HTC PH39100 using xda app-developers app
Never really had any problems with samsungs beside the only issue I have ever had with ALL Samsung phones .. They have the worst RF signal/strength out of any company! I miss the days of my old Nokia RF ..
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Android Law #1: Costum ROMs are ALWAYS 10x better than stock.
Wow an i cant find one issue. Always great signal never inresponsive u sure u have an infuse
Sent from my SGH-I997 using xda premium
Prometh1216 said:
Wow an i cant find one issue. Always great signal never inresponsive u sure u have an infuse
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Hehehe, what ROM u running?
Sent from my SAMSUNG-SGH-I997 using xda premium
qkster said:
What firmware are you running?
Click to expand...
Click to collapse
One is using the GB posted by jscott30 here, the other is the plain official Samsung GB via Kies. Mine is then UCLB3
qkster said:
Is it the same firmware on both phones?
Click to expand...
Click to collapse
No
qkster said:
What is the launcher?
Click to expand...
Click to collapse
Both stock
qkster said:
Have you tried a different modem?
Click to expand...
Click to collapse
No, thought never occurred to me that I should look at this as a solution.
qkster said:
Are you using a battery saver like juice defender?
Click to expand...
Click to collapse
Neither.
qkster said:
Are you using an ad blocker?
Click to expand...
Click to collapse
Nope
qkster said:
Are you using a specific kernel? Oc? Uv?
Click to expand...
Click to collapse
2.6.35.7-I997RUXK53-CL366622 for mine (GB rooted ROM) the other would be whatever came with the official Samsung GB release.
qkster said:
Need for specific info
Click to expand...
Click to collapse
Again this has been a recurring problem since purchase, and during this time I have had stock Froyo, rooted Froyo ROM, GB update, and for one now a the GB rooted ROM.
When the slow to unresponsiveness occurs there does not appear to be any specific cause. Prior to updating to the rooted GB I had used GO Taskmanager, and long before that some other app I long since forgot the name of. Point was that they had shown that neither CPU was excessive, or memory was used up. Both phones have data services disabled and are strictly Wifi only. There are no tasks or extra programs run in the background (though did install Connectbot today). I no longer use any Live wallpaper. After updating to the rooted GB I left the phone in that state (no software installed) for a week or so, and the problem still occured.
This occurs when calling or answering calls, but as previously posted occurs sometimes just opening the Applications menu as an example. So it is not a specific task or program that is slow or unresponsive. Earlier this evening I got a call, slide the bar across to answer and the screen just hung there for a few moments. This time it was at least not long enough that I missed the call. When the call was done I looked and there simply was nothing running on the phone. No apps, no web browser or mail, in fact I was not even connected to the wifi (I have data 3G/4G service disabled on the phone).
are you completely wiping before every flash youve done? have you tried a complete wipe and start from fresh?
ssa2204 said:
One is using the GB posted by jscott30 here, the other is the plain official Samsung GB via Kies. Mine is then UCLB3
No
Both stock
No, thought never occurred to me that I should look at this as a solution.
Neither.
Nope
2.6.35.7-I997RUXK53-CL366622 for mine (GB rooted ROM) the other would be whatever came with the official Samsung GB release.
Again this has been a recurring problem since purchase, and during this time I have had stock Froyo, rooted Froyo ROM, GB update, and for one now a the GB rooted ROM.
When the slow to unresponsiveness occurs there does not appear to be any specific cause. Prior to updating to the rooted GB I had used GO Taskmanager, and long before that some other app I long since forgot the name of. Point was that they had shown that neither CPU was excessive, or memory was used up. Both phones have data services disabled and are strictly Wifi only. There are no tasks or extra programs run in the background (though did install Connectbot today). I no longer use any Live wallpaper. After updating to the rooted GB I left the phone in that state (no software installed) for a week or so, and the problem still occured.
This occurs when calling or answering calls, but as previously posted occurs sometimes just opening the Applications menu as an example. So it is not a specific task or program that is slow or unresponsive. Earlier this evening I got a call, slide the bar across to answer and the screen just hung there for a few moments. This time it was at least not long enough that I missed the call. When the call was done I looked and there simply was nothing running on the phone. No apps, no web browser or mail, in fact I was not even connected to the wifi (I have data 3G/4G service disabled on the phone).
Click to expand...
Click to collapse
Task manager is NOT the best app to tell you what is running in the background.
Maps and other location apps may not be listed but will consume resourse that can be the cause of your lag.
The fact that stopping wallpaper or live wall paper off alleviate the condition may suggest that the phone is running at max capacity. Steps to reduce the load improves it. Live wp, facebook, maps, stock email and other device manager from stock att was one of the first @#$% I took out on any rom I run.
Having a large amount of apps installed can also cause this lag. The OS may only be able to handle so many.
Have a poor signal at the time of the call may also be an issue, especially if both of your phones have this issue occasionally but not consistently.
Lock screen can also be a factor. Some sleep setting may also cause the phone to wake up poorly. I get around this by turning off my lock screen. On the call settings, you can also change the answering options so that it will override others and make it easy to answer.
On any firmware - stock or modded, after you have the phone running for an extended period of time without a reboot, you may start to see some lags. This may be across all devices. You may need to reboot it occasionally or boot into recovery and wipe the cache.
These issues may or not go away once you have a device with more power or resources..ex: dual or quad core, 1gb or 2gb ram etc..my guess is when a device has more power, programmers will come up with more resourse intensive apps that may hinder the phone as well.
Lastly, pay attention to your battery meter. As the power dips below 30%, there are steps taken by the OS to conserve the battery. This may give you lags as well..possibly one of the reason why it seems random also.
If you wanted to test out the lag issue due to background apps, go to settings/account and sync. turn off background data. You will retain the (radio) phone and text but there will be no email/facebook, weather, widgets/market/amazon etc updates unless you manually update them. If this runs smoothly but lags when you turn it back on, you can start the process of narrowing down your culprit.
gl
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
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.