I updated via that menu just last night. It worked and I didn't have any issues. So looks like it's just you
Maybe because of your "old" currently installed build.CM11 is dead, we all moved onto CM12. Unless you ask a dev to build an update or build one yourself, i'm afraid there's a good chance you are s.o.l.. I'm not saying this to be mean, just giving you the facts and being honest.
Thanks much, not sure how that could be considered mean tho, so no worries there. I assumed it was related to work on CM12. But other devices are still getting CM11 updates so development doesn't appear to be completely dead/frozen quite yet.... but I see no need to bug a developer yet for our phone until it's all done ready for M13, if other phones get that and ours doesn't I'll ask how to ask a dev to build that.
you'd be surprised, we have a handful of ppl who can be very sensitive to how members come off. I know I can come off the wrong way at times, and some other senior members can agree with me on that. The reason some devices are still getting CM11 updates is b/c either the device's unofficial CM12 builds don't meet CM's requirements to be officially supported devices at the CM12 level, a CM12 build has yet to build, the build has yet to be submitted for review, or lack of ROM stability (kernel or ROM related).
This is the most noobish comment i have ever heard. Battery doesn't run all day? See what app is eating your battery. G+ giving you errors? Uninstall it and have it roll back to the version in the gapps you flashed. Easiest to blame it on CM? Go back to stock then. Oh i'm sorry, you don't have 4.4.4 on stock. So stop complaining, take steps to improve your battery, or start developing or replacing your device. Its like blaming the weatherman b/c it rains. Smh, what a wonderful and ridiculous post you made. Yes, you do deserve to be ripped into for the comments you made
The wakelocks related to the updated (via play store) google apps and services should be fixed for CM11 by:Thanks, that made me smile. Especially the weatherman bit, can't quite see that connection. At least if you said something like blaming the guy who changed your brakes for an engine failure or something would make more sense, but quite not as funny
Honestly tho, is it that hard (for the person who knows what they're doing already) to put out a newer version? I mean they used to do it every day, it must be fairly automated.
I like the idea of rolling back g+ tho, I'll try that now. And yeah, apparently my battery problem is google play services, it's used 37% in the last few hours since this morning when I took the phone off the charger, along with android OS taking 25%. Screen is down at 3% cuz I hadn't even looked at my phone today until this very moment, and that's usually the thing that's highest any other time I'd looked at it with previous versions.
But I still think it's easier to blame CM since that's what I changed that started this, and I did try to read the changelog to see if this particular issue was mentioned and fixed in later version, but didn't find anything, would be easier (for me, obviously) to just try something newer before I spend time trying to figure something out that may already be solved.
Thanks much. I did look into this a bit more and yeah seems it's a problem caused by google when they released an update to google services, that affected both CM11 & CM12 and most (all?) other custom roms, plus one model of phone that shipped natively with CM. I read about workarounds with xposed & wakelock blockers, but I'm a pretty basic user and avoid installing anything on my phone unless I really need it and rarely use my phone for anything besides the occasional text message or phone call, the only reason I even have g+ on there is for location sharing so my wife can easily see where I am and I only created the g+ account specifically for that purpose and dont use it for anything else. There's probably a way for me to revert the google services update if I looked into it; proably because it's a service, the phone won't let me remove updates thru the menus like I can with regular apps. But I'm lazy and concerned the more I mess with things the more problems I could cause, so prefer to not mess with things. So I'll just be patient, but will watch this thread incase you or whoever posts an unofficial or official or any update those two fixes. I also saw cyanogenmod forums administrator post on March 30th that M13 is still planned as the final CM11, but no estimate as to when. I guess they'll work on finishing that up after the first milestone release for jellybean.
Would be very grateful if you did this... but understand having busy life.
CM11 with f2fs is the update you can use until he has a chance to release an update of his own. Search one of your device's sections, its in there
Thanks. I did find it and install it, although took me a lot of time to figure that process out, as instructions weren't clear and in fact if followed exactly will not work right, plus required figuring out how to use and install a new recovery, which required android sdk install on pc, driver download from samsung, etc, things I hadn't done since the initial install and certainly didn't remember how to do off the top of my head, and was using a different computer so nothing left from back when I did it the very first time. Those were the reasons I was hoping for official (or unofficial built the same way), but yep, I'm good now, and am familiar with the manual install process and also how to restore it back to an official nightly (which I had to do a couple times after attempting to install that unofficial).
Hi, is it this one?
