yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] diablo46:
So i installed this ROM today and i'm really happy with performance/features but my battery life is terrible; In wifi only mode it dropped form 48% to 45% in about half and hour while i did my settings but after that i popped up the cellular service/data and it went from 45% to 28% in about 7min, even in standby with data disabled is still pretty bad (28% to 22% in 40 min). Before that on 4.3 i was losing 1-2% overnight and usually did 3.5h of screen on;

CM-12.1-20150429, GCC 4.7 Kernel, gapps-5.1.x minimal edition, default settings, only app installed is fb messenger, network signal was very high all the time;

Any idea on what i should check? I've search this thread for battery related issues and found nothing, so i apologies if this has been talked about;
[Samsung Galaxy Nexus] Akosijasper:
im facing bugs with music due to audio Fx Fc.
[Samsung Galaxy Nexus] ItsMe57:
Battery Life

Battery life could be better.

No flashing red led, when lower 15%
[Samsung Galaxy Nexus] sharathnair_2190:
Frequent FC errors, system reboots when on charging...F@cing lot of problems... super l@ggy .. i dont knw wt went wrong in here... :( c@n ny1 help ..??
[Samsung Galaxy Nexus] nikodr:
Wipe Cache/Data,

Format System

Wipe Dalvik Cache

Clean install with correct gapps and all problems go away :)
[Samsung Galaxy Nexus] sharathnair_2190:
Hey thnks der... i tried evrything buddy.. now wht is system formt...?? if i delete my internl strge, how will i b able to flash the ROM..?? thnks in anticipation of ur cooperation..cheers
[Samsung Galaxy Nexus] ItsMe57:
Find ADB HowTo here in the forum

or

Copy the files with MTP-mount after formatting .
[Samsung Galaxy Nexus] AYAMY:
I have flashed cm-12-20150322-UNOFFICIAL-maguro and now I'm stuck with the boot animation (flying circles) and I'm waiting for half an hour (FIRST BOOT).

it's normal ?

- switch off , wipe , reflash , it's ok now !!!
[Samsung Galaxy Nexus] joshyzacariya:
That's good; and don't forget to flash the update1.
[Samsung Galaxy Nexus] joshyzacariya:
[MENTION=1048318]zzpianoman[/MENTION], how can I uninstall and reinstall gapps? I removed some boltware and in trouble now. :confused:

Thanks,
[Samsung Galaxy Nexus] JackSlaterIV:
zzpianoman, many thanks for having found a workaround for the green lines affecting video recordings.

I've just tested the last build and it's working nicely.
[Samsung Galaxy Nexus] zzpianoman:
Just reflash the ROM and gapps.
[Samsung Galaxy Nexus] sharathnair_2190:
Gosh..!!! thats what i did... i am no noob.. but anyways,, Thank you ... :p
[Samsung Galaxy Nexus] bjr1108:
I cant update the binary in supersu :(

How to fix this?
[Samsung Galaxy Nexus] zzpianoman:
NEW BUILD - 05/15/2015:

cm-12.1-20150515-UNOFFICIAL-maguro.zip

CHANGELOG:

Latest CM-12.1 updates (synced 5/13/2015)

New OOM values, less aggressive better for multitasking

Added ktoonservative governor to kernel*

Video snapshots fixed in stock and Google camera**

1080p video recording should be smooth

NOTES:

*ktoonservative governor has hotplugging disabled by default, because it does NOT work well on our devices and may will lead to random crashes and reboots. You are free to enable it, but please do so with this in mind.

**Although video snapshots are now working correctly in the stock and Google cameras, they may still crash randomly from time to time which will require a system reboot before the camera becomes usable again. I'm working on a fix for this, but in the mean time you may want to stick with the Legacy Camera for video recording. If you stick to only taking still photos with the stock/Google cameras, you should not experience any crashes.

Also, the green lines have been completely fixed and are no longer present in recorded videos of ANY resolution. This was fixed in the last update, but this is the first complete build where that fix is now fully integrated.

The new OOM values are actually based off of CyanogenMod's new OOM values for 32-bit devices with the foreground apps level being reduced to 15 (to prevent foreground apps from being killed when you are using them) and the empty apps level increased to 195 (to compensate and to ensure that there is enough free RAM in the system).

NOTE: The kernel in this build was compiled with GCC 4.7 so there is no need to flash the kernel fix update from the previous build.
[Samsung Galaxy Nexus] Tolazace:
[MENTION=1048318]zzpianoman[/MENTION] Zip is broken :/ When I open on PC i see MD5 error, on phone Rom don't copy system partition... I tried download from all mirrors... previous build works great.
[Samsung Galaxy Nexus] andusci:
Failed operation to flash new release

I flashed the new realease [05/15/2015] with no problems, but when I try to flash the gapps the operations abort it.

During the rebooting of the system, after few seconds it re-appears the recovery screen. :confused:

Luckily that I did a backup before these operations.. :)
[Samsung Galaxy Nexus] Tolazace:
Format system before flash and check this partition after flash(File menager in TWRP) - it's empty like before flash. Install look fine but zip is broken.
[Samsung Galaxy Nexus] zzpianoman:
My apologies...

I will re-upload ASAP.
[Samsung Galaxy Nexus] zzpianoman:
Okay, post has been updated with new zip.

Hope this works!!
[Samsung Galaxy Nexus] andusci:
I'll try it!! ;)
[Samsung Galaxy Nexus] Tolazace:
Works :D Great and Smooth rom ;)
[Samsung Galaxy Nexus] zzpianoman:
Thanks!
[Samsung Galaxy Nexus] andusci:
Everything okay for me.

Thank you!!! :)
[Samsung Galaxy Nexus] rambhanushali20:
Is Snapchat video recording working with this..?
[Samsung Galaxy Nexus] zzpianoman:
Yes.
[Samsung Galaxy Nexus] wenqing huang:
the best rom i've ever used.

the best rom i've ever used.

yes. this is true.

thank zzpianoman.
[Samsung Galaxy Nexus] coleburns:
anyone managed to download the file? i keep getting an error
[Samsung Galaxy Nexus] Akosijasper:
[MENTION=2613974]zzp[/MENTION]ainoman is the music player fix? coz when i use the music player and go to other apps while playing the music, the music stops :( can you check it?
[Samsung Galaxy Nexus] joshyzacariya:
Is it a bit laggy comparing to previous builds? :confused: I feel so.
[Samsung Galaxy Nexus] zzpianoman:
Yes...it is because of the new minfree values.

If you want, you can use an app like 3C Toolbox to adjust the OOM values to some more aggressive numbers......

These are the approx minfree values from the previous build:

315 - empty

228

157

130

32

12 - foreground

It's always a work in progress with these - still trying to find the optimal values for multitasking/performance but adjusting them back to those values should eliminate the lag.
[Samsung Galaxy Nexus] aleale228:
Does anyone have the following problem with this rom - at certain point, I still can't figure out when and what causes it (but it happens at least once in every couple of days)- the phone soft reboots by itself. For example- it happened few minutes ago as it was staying on the table in front of me (e.g. without me doing anything, I just saw the boot animation, but much shorter than the normal boot ).

And after this reboot - I no longer have mobile network data - no 3G, HSDPA, GPRS .. And I need to reboot the phone once again to have the data back on. Yesterday I wiped the phone and installed the rom once again hoping to somehow fix this, but - no luck.

Thanks
[Samsung Galaxy Nexus] harjifangki:
Yep. Happens to me too.

I used FML and this ROM, and it keeps happening on both ROM.

It's extremely annoying, but I know this is still in alpha state, so I guess it's fine.

Hope it'll be fixed soon. :good:
[Samsung Galaxy Nexus] saprer:
ive got this too
[Samsung Galaxy Nexus] joshyzacariya:
Works fine on these values; please keep in next builds... thanks.
[Samsung Galaxy Nexus] joshyzacariya:
I experienced reboots during phone calls. Any idea?
[Samsung Galaxy Nexus] seriousia:
Sorry for asking but in not able to find this

How to limit recent app list limit from build.prop
[Samsung Galaxy Nexus] zzpianoman:
ro.config.max_recents=10

you can change this to any number you like, from 0 to 99.
[Samsung Galaxy Nexus] 93fuelslut:
I can't change "kill all" to "empty" just like the other member had said on how he set his values.

Sent from your moms phone
[Samsung Galaxy Nexus] zzpianoman:
UPDATE

Sorry I haven't been around much lately, but I've been working hard at trying to iron out the last few bugs in the CameraHAL. Almost there!!

I do think it's probably time for a new build, so I'll be syncing up with CyanogenMod and will hopefully have something together in the coming days.

If I encounter any significant problems after syncing, I might consider releasing an incremental update with new hardcoded minfree values and the Camera fixes, so stay tuned!
[Samsung Galaxy Nexus] quickdraw86:
Empty is merely the name of the application group at the top of the list in 3c's OOM menu. "Kill all" would be the result of choosing an extreme value for a given app group, or an option for an individual app group, but isn't the name of any specific group of apps as it appears in the sytem, if that makes sense. Actually, the reason zzpianoman recommended 3c in post #605 is because the way it lists the app groups directly corresponds, top-to-bottom to the way he listed values in the post linked in #605 (he likely uses 3c himself, and likely used that app to configure or check OOM values on his own device). See my screen for the values as he listed them. Using the sliders in 3c, it's difficult to set the exact values as listed, but plus or minus a few in either direction for any given app group will make very little difference in actual usage...

View attachment 3330431

As zzpianoman stated in the post above this one, and alluded to in other posts, more appropriate OOM values will be default in future builds, and this type of tweaking/configuration won't be absolutely necessary in future builds.
[Samsung Galaxy Nexus] zzpianoman:
Yeah, those &#^$ sliders!!

But that is correct. They don't have to be exact. I've had the best luck focusing in on the two endpoint values - empty apps and foreground apps, and then tweaking the middle values until you find a good balance. You're going to want to set foreground apps pretty low, because ideally, they should never get killed - and empty apps should be higher, I feel, than the default values chosen by CyanogenMod for 32-bit devices. The truth of the matter is we simply can't set minfrees as lenient as they were on KitKat or else the device lags to an unusable state - especially if you use big apps like Chrome, or Facebook. I feel it is better to sacrifice a "bit" of multitasking for faster, more fluid performance - and with ART, applications start much faster than they did on KitKat with dalvik, so you're already going to be making up some time there. The only apps you'd have problems with are ones that aren't optimized properly for some reason, or are using too many background resources - i.e. Pandora.
[Samsung Galaxy Nexus] quickdraw86:
Lol. Exactly. Lollipop is friendlier in general to modern devices, with 2-3 gb of ram, and more aggressive OOMs are necessary to run L on our older hardware, but a happy medium can be found with a bit of experimentation. 5-14 runs well with the values you posted earlier, have been running that build daily with those OOMs for the past few days.
[Samsung Galaxy Nexus] xcvzq:
My Google Play Services keeps crashing. Is this happening for anyone else? I'm using the GAPPS recommended in the post but the crash only happens after Play Services updates to the latest version.
[Samsung Galaxy Nexus] quickdraw86:
I had the same issue briefly. Go into apps from the system settings menu, scroll to the all tab, chose play services, wipe play services data and reboot. That solved my issue anyway.
[Samsung Galaxy Nexus] xcvzq:
I tried that before and it didn't work. I just wiped /system and installed a newer GAPPS from the CM wiki and it seems fine so far.
[Samsung Galaxy Nexus] zzpianoman:
I can confirm that this seems to fix the issue. It only began appearing after the latest Google Play Services update, but changing your gapps package to the CM version seems to fix it.
[Samsung Galaxy Nexus] mgBd:
Hi [MENTION=1048318]zzpianoman[/MENTION] !

Coming back for my MMS issue, and it's still here, no matter if i try to use another SMS/MMS app... Any idea since last time ?

Also good news, your last build is working so well, no more reboot or other FC (maybe also since i replaced FB app by FB Lite...), so keep going that way, you rock ;)
[Samsung Galaxy Nexus] zzpianoman:
NEW BUILD - 05/27/2015:

cm-12.1-20150527-UNOFFICIAL-maguro.zip

CHANGELOG:

Latest CM-12.1 updates (synced 5/25/2015)

Sync QS tile

Previous OOM values

Camera is 99% working*

Added support for UnifiedNlp**

Secure adb is enabled by default

NOTES:

*Stock/Google cameras are now a suitable functional replacement for the LegacyCamera app, although I will continue to include the LegacyCamera for anyone who prefers using it over the stock camera. There *may* be an occasional crash requiring a reboot - but this happens mostly when recording 1080p video with the rear camera. Video recording for MMS is now 100% fixed and camcorder should work in all 3rd party apps (SnapChat, Instagram, etc).

**UnifiedNlp is an open-source network location provider that works alongside Google Play Services, and allows you to maintain a local database of wifi/cell towers for use with high-accuracy location. I have added support in this ROM so that the Xposed module is not needed to make this work.
[Samsung Galaxy Nexus] mgBd:
HALLELUJAH !! After posting this, i made some other research about my carrier APNs and guess what ? I found the solution with this french thread.

It's poorly written (huh...) but i just added "default,suppl,mms" instead of default "default,suppl" in my "Orange World" APN type (in french, "type d'APN") ! But this APN is about Orange France mobile data, not about MMS, so i don't really know why it's working... and i want to understand ;)
[Samsung Galaxy Nexus] joshyzacariya:
Clean or dirty flash?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] zzpianoman:
Hi,

I've actually been focusing most of my time on getting the camera to work, but I should have some time now to go back and revisit your MMS issue. I have a feeling it is due to incorrect APN settings, so it will be just a matter of finding the correct settings and applying them. I'll look some more into that French app to see if I can find anything!

EDIT:

From apns-conf.xml:

<apn carrier="Orange Internet" mcc="208" mnc="01" apn="orange.fr" user="orange" password="orange" authtype="0" type="dun" />
<apn carrier="Orange World" mcc="208" mnc="01" apn="orange" user="orange" password="orange" authtype="2" type="default,supl" />
<apn carrier="Orange MMS" mcc="208" mnc="01" apn="orange.acte" user="orange" password="orange" mmsc="http://mms.orange.fr/" mmsproxy="192.168.10.200" mmsport="8080" authtype="2" type="mms" />
<apn carrier="Orange Entreprise" mcc="208" mnc="01" apn="orange-mib" proxy="172.16.2.8" port="8000" user="orange" password="orange" authtype="2" type="default" />
<apn carrier="Orange GPRS ISP" mcc="208" mnc="02" apn="orange.fr" type="default,supl" />

Try adding the settings for Orange MMS to Orange World in the APN editor on the device, and add "mms" to the "type=" field so it reads: "type=default,supl,mms". If that doesn't work, resolving the mmsc (http://mms.orange.fr/) to its IP address and use that in place of the http link.
[Samsung Galaxy Nexus] xcvzq:
It seems to have come back after some time. I once got a message that said Google Play Services is not supported on this device.
[Samsung Galaxy Nexus] chelhydra:
Can I upgrade from Ziyan's CM12.1 (21/052015) to this without swipe etc?
[Samsung Galaxy Nexus] draganmk:
Same here, clean install latest ROM 27.05.2015. Have tried with latest CM gapps, pico package from TK gapps and Gapps-5.1.x-20150404-minimal-edition-signed. Latest one has worked well before with only calendar not synchronizing. I have been trying all day to make this work without success. I have constant play services error.
[Samsung Galaxy Nexus] zzpianoman:
UPDATE - 05/28/2015:

cm-12.1-20150527_UNOFFICIAL-zzpianoman_update1.zip

CHANGELOG:

Fix Google Play Services FC on High Accuracy Location

NOTES:

Flash this in recovery on top of the latest build (5/27/2015).
[Samsung Galaxy Nexus] chelhydra:
ThIs is possibly the best lolipop release, everything is working great. Thanks
[Samsung Galaxy Nexus] ItsMe57:
lag lag

The last update was very laggy.

Redrawing of the UI tooks very long.

I deinstalled the facebook app, reboot, wiped cache and dalvik.

All fine!

THX again for this nice LP.

ItsMe57
[Samsung Galaxy Nexus] joshyzacariya:
In battery saver mode, the phone works very fast. Can you please tell us what are the modules disabled and what is running in battery mode? Thanks,
[Samsung Galaxy Nexus] phaleg:
How is the situation installing the update 1?

Will next build have this update integrated?

thanks for keeping the best android of ever still alive ^^
[Samsung Galaxy Nexus] zzpianoman:
Anyone having problems with excessive battery drain, download Disable Service, select "Google Play Services" under System apps, toggle FULL service name by tapping the FULL/SHORT button at the top, search for "location" and disable all but the following services:

com.google.android.location.internal.GoogleLocationManagerService

com.google.android.location.internal.server.Google LocationService

com.google.android.location.internal.PendingIntent CallbackService

So you should have disabled 19 services with the keyword "location".
[Samsung Galaxy Nexus] jose daniel:
i m having some trobles whith wifi and data ; wifi dont conect some times and data aswell. a reboot use to solve the problem.

is any one having seme problem?

i am working with the special kernel for old Nexus
[Samsung Galaxy Nexus] phaleg:
gapps type

Arm, arm64 or x86 for gapps?

Do custom gapps (like slim or nano) work as well?

thanks
[Samsung Galaxy Nexus] Joearrow:
I use PICO gapps without any problem
[Samsung Galaxy Nexus] phaleg:
Could you give me a link please?

And you said no problem at all...
[Samsung Galaxy Nexus] Joearrow:
http://xdaforums.com/paranoid-android/general/5-1-x-5-0-x-4-4-x-pa-gapps-mirror-t3069879

:good:
[Samsung Galaxy Nexus] Njkntr2:
Hi, whether it is possible to flash your kernel on another ROM 5.1.1 ?

if yes, as it to make that?
[Samsung Galaxy Nexus] zzpianoman:
All other Lollipop ROMs for the Galaxy Nexus use DDK 1.9, so this kernel is not compatible with those. If you flash this kernel with another ROM the device will not boot.
[Samsung Galaxy Nexus] chelhydra:
Did that and now i'm getting very impressive battery life. What's the catch ?
[Samsung Galaxy Nexus] phaleg:
Any issue after doing that?
[Samsung Galaxy Nexus] chelhydra:
No problems, everything runs great!
[Samsung Galaxy Nexus] phaleg:
I have just done a clean install on my wife's maguro with sad results...

I wiped both caches, data and system

Installed rom, update1, gapps nano and superuser from recovery

then reboot and patiently wait

At first boot phone was struggling and repeating the process in which you insert login details many times... plus it was laggy on easy operation like typing.

If it matters, I am using Italian language and my recovery wipes in ext4f2fs (I may be wrrong on that, but it is what I understand from recovery lines)

my gapps were PA nano... [MENTION=4239728]chelhydra[/MENTION] #chelhydra said they were ok

Now I am back to slimkat r2 from this forum, I had a backup
[Samsung Galaxy Nexus] chelhydra:
I followed the steps in the first post of this thread (with gapps) and have no problems
[Samsung Galaxy Nexus] 93fuelslut:
Can anyone post videos on Instagram?

Sent from your moms phone
[Samsung Galaxy Nexus] zzpianoman:
NEW BUILD - 06/04/2015:

cm-12.1-20150604-UNOFFICIAL-maguro.zip

CHANGELOG:

Latest CM-12.1 updates (synced 6/3/2015)

(experimental) Battery Emergency Reserve*

Volume keys can wake/boot phone from offline charger mode

NOTES:

*Enable extra battery capacity by lowering critical shut-down voltage. Please use this with caution, as discharging your phone's Li-ion battery beyond specified limits will have an adverse effect on the overall lifespan of the cells. This should be used in emergencies only, when there is no available power source and you would like to buy some extra time before the phone shuts itself down. I have successfully managed to gain an extra 3 hours of standby time using this feature although your results may vary.

HOW IT WORKS:

Once the battery has reached 15% capacity, you can enable the emergency reserve feature by issuing the following command from a terminal prompt (or modifying the file with Root Explorer):

"echo 1 > /sys/battery_reserve/enabled"

Shortly after the feature is enabled, you will see the battery capacity jump by several percentage points to a higher, adjusted value. The emergency reserve feature will remain enabled until the device is rebooted, or until a charger is connected. Although it is possible to enable the feature at any point during the charge cycle, it will not have any effect on the battery percent scale until after it has reached 15% and will be reset any time the phone is plugged into a charging source.

I must reiterate, that this should only be used as an emergency backup and repeated use of this feature will degrade the battery over time. You will have best results if used in tandem with other power saving measures, such as lowering CPU frequency, screen brightness, managing radio usage, etc and keeping the phone in standby mode as much as possible. Either way, the phone will shut down gracefully once capacity reaches 0% so there should be no risk of data loss or corruption. The battery percentage may fluctuate unpredictably under situations of high CPU load when the device is using more power, so the less stress you place on the device, the longer the battery will last.
[Samsung Galaxy Nexus] phaleg:
Hello!

Do you have any idea why I got that problem post #304 ?
[Samsung Galaxy Nexus] zzpianoman:
Hi,

Are you referring to the problem here? If so, try letting the device sit for a while after the initial boot has completed (maybe 10 minutes or so). The dexopt procedure can be very taxing on the system, drawing quite a high cpu load for an extended period of time so it is best to just let it cool down for a minute before entering the setup procedure. This ROM is deodexed - meaning all of the cache building for system apps happens during that initial boot, compared to other ROMs which have performed all necessary optimizations during compile time resulting in a much quicker initial boot.

I chose to build this way in order to make it easier for me to modify framework files between builds which allows me to troubleshoot issues much faster and cuts down on the size of incremental updates. It also makes for a considerably smaller /system partition which awards you more flexibility in terms of gapps packages. The downside to all of this is that those initial boot times will be much longer and slightly more taxing on the system's resources so the device might be a bit slower to respond initially since all of those resources had been devoted to building and optimizing the cache. If you are experiencing problems during the setup procedure, just turn off the screen for a few minutes to let everything "settle" and try again.
[Samsung Galaxy Nexus] phaleg:
Hi zzpianoman and thanks for your answer...

I have read of being deodexed and I was cool with it and its longer first boot time...

The main problem, was that I was not able to do the usual first login properly, it was hard to type and after putting your gmail address and password as usual, you get a couple of screen forward and then it starts again from login, saying you can't put your address because you already did.

If you quit the procedure, then no apps of your is reinstalling as usual...

It was not a problem of waiting a bit, could it be related to being probabily in F2fs if my understanding from the recovery is correct?

(latest TWRP)
[Samsung Galaxy Nexus] zzpianoman:
F2FS should work just fine. Which gapps package are you using?
[Samsung Galaxy Nexus] phaleg:
I was using PA gapps nano...