yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Ziyan:
New build up.

Notable changes:

- Enabled 512 MHz GPU frequency, using the same voltage as for 384 MHz. Until CM12 gets support for performance profiles again, 512 will be the default (use trickster mod to change it till them). Report back if it has any stability, heat or battery life effect.

- Android 5.0.2

Fixes:

- Carrier text on the lockscreen is now aligned properly

- annoying screen off animation glitch is now gone

Enjoy ;) personally, I like where CM12 is headed - materialized apps (sms, browser, file manager, audio player, gallery), nice new features.... About the sms issue with RIL, I feel like this will only get fixed once we switch to the open source libril - I gave it a quick try some days ago, despite it showed 'No sim card', I could receive calls and SMS messages, so with enough time and knowledge (I'd need a bit more from both), we could get that open-sourced and fixed as well. About the charging mode, I'm on it - by adding the 'critical' flag to the service, it will at least reboot into recovery after multiple crashes, instead of having to do a battery pull.

If anyone wants to experiment: please change the interactive governor's hispeed_freq (this is the freq the CPU will switch to first when it notices increased load) from 700 to 900 MHz. 700 MHz is defined in our PowerHAL, I'm wondering if setting it to 900 MHz would improve responsiveness noticeably. The effect on the battery life shouldn't be too big...
[Samsung Galaxy Nexus] tiagofernandex:
Noob question:

I have the previous build, to update its just flash the new build?
[Samsung Galaxy Nexus] TheMan0790:
Yes, that will work.
[Samsung Galaxy Nexus] revanmj:
I like it for as long as they don't add new Theme Engine back. CM11 started lagging a lot for me after they did this, so I'm afraid the same will happen to CM12 :/

EDIT: Is there any chance this will help us too? http://review.cyanogenmod.org/#/c/82584/
[Samsung Galaxy Nexus] blackout23:
I'm on the zRAM, BFQ, LZ4 Build and it is running great! Thanks for all the work Ziyan! I moved back to Paranoid Android 4.4.4 for a while, because the memory problems made the device unusable.

Now I'm waiting for an Android 6.0 Build with the same treatment. For me Android 6 doesn't bring that much new to the table, but I want the security fixes.
[Samsung Galaxy Nexus] Childe89:
I noticed new build up on CM downloads - https://download.cyanogenmod.org/?device=maguro&type=

CMX log still not added Maguro changelogs, would be useful :) - http://www.cmxlog.com/12.1
[Samsung Galaxy Nexus] kongha:
a big congrats guys for hitting nightly! ive followed, tried to contribute and im so astonished what you have done for this "old" device :)

edit: mentioned in swedens largest android forum http://www.swedroid.se/gamla-godingen-galaxy-nexus-far-lollipop-genom-cyanogenmod/
[Samsung Galaxy Nexus] callmewind:
Wow! this ROM gives me excuses to keep my phone alive even more time, [MENTION=2633638]Ziyan[/MENTION] you're the boss :D

For the record, two small bugs I've found:

-When removing the phone from the pogo dock, it reboots and SIM card doesn't get detected until I manually restart again. 100% reproducible. Also built-in speaker is muted when docked. I suppose the sound is routed trough the dock, but I don't have speakers connected to it.

-Settings app crashes when tapping in NFC 'Touch and pay' setting (network settings->more)
[Samsung Galaxy Nexus] MonstaDriva:
Unified ?

Seems like I remembered reading somewhere a while back that this might become a unified build for 3 variants , Maguro , Toro and Toroplus . Just asking if it is and if not are there any plans for it to become so ? ty
[Samsung Galaxy Nexus] erOzeOz:
Hi Ziyan and others,

Thank you so much for your hard work on CM 12.1 for our Galaxy Nexus!

I would like to know if you are still supervising the development of the builds on CM website?

Could you please give us some information about those builds as there is no changelogs available...

Does the latest (20160119) have lowram flag? Will you continue working on the speed improvements with zram?

Thanks for keeping us posted :)

Sam
[Samsung Galaxy Nexus] cloud_strife84:
Where did you find zRAM, BFQ, LZ4 Build?
[Samsung Galaxy Nexus] Childe89:
In download section in this thread :)

Lowram flags are removed in official builds, but it´s working really good now

btw. official logs are updated, including our freshly supported Maguro :good:

http://www.cmxlog.com/12.1/maguro/ - you can find changelog here :)
[Samsung Galaxy Nexus] cloud_strife84:
So official 19 nightly build is good to use?
[Samsung Galaxy Nexus] Childe89:
Yes, everything OK, same as previous unofficial builds but improved :)

Except two problems with the Camera (universal Lollipop problem on Maguro) - 1. purple line in recorded videos 2. crashes when taking snaps during video recording (or switching between taking photos and recording videos few times)

If you use Camera only for photos, works flawlessly :)
[Samsung Galaxy Nexus] musical_chairs:
I don't think there are any plans to make the CyanogenMod builds unified, at least not in the near future.
[Samsung Galaxy Nexus] :
This is not a universal Lollipop problem. It's related to the new graphics drivers.

The Lollipop and Marshmallow ROMs by zzpianoman which use the old drivers do not have any issues with camera / video.
[Samsung Galaxy Nexus] Nukedathlonman:
Wow, just made the switch OTA from CM11, very nice work - haven't seen my phone run this smoothly in months. But, somehow when the upgrade occurred I lost root access...
[Samsung Galaxy Nexus] redcrash:
Congratulations Ziyan & team for hitting the CM nightly builds!

For those interested in changelogs, you can search them here:

http://www.cmxlog.com/12.1/maguro/
[Samsung Galaxy Nexus] cloud_strife84:
What is the difference among old and new graphic driver?
[Samsung Galaxy Nexus] musical_chairs:
You didn't lose root access, it's just not on by default in L: http://www.androidexplained.com/cyanogenmod-enable-root/
[Samsung Galaxy Nexus] LeoHart:
Has anyone noticed the missing "immersive Mode" ?

I don't no why, but no app get in it. The navigation bar is always displayed.

Overall very good job!
[Samsung Galaxy Nexus] vortex-5:
I've had a few programs enter immersive mode without much issue. Pocket is one of them that I observed immersive mode.
[Samsung Galaxy Nexus] Nukedathlonman:
Okay, sorry - thought it was a problem with the install and was going to manualy root it tonight... Not now. :) Thx.
[Samsung Galaxy Nexus] leto78:
My father's Nexus got updated from CM11 to CM12.1 with OTA and but now the Play store doesn't work.

I guess the Gapps need to be installed separately.

Can anyone provide a really easy step-by-step for someone that is not tech savvy to follow?
[Samsung Galaxy Nexus] 0s1ride:
Oh, I see it was disabled on purpose.

The flag does more than just disabling atlas by default, though.

For example, it enables the isLowRamDevice() API, that apps can choose to use.

I agree that zRAM helps a lot, but for me chrome is only usable with the lowram flag; it's just much faster, since it disables tab caching, that is very memory hungry.

Some other google apps that use it are the camera and the google app, but they only disable photoshpere and "ok google" from any screen, as far as I know.

Also, memory tests that [MENTION=2838735]aosp[/MENTION] posted show that on devices with less than ~600MB U01 score (max usable memory for an app after boot up) should use it.

For the record: the 1 GB RAM Moto G uses it.

If anyone wants to enable the flags again, it can be done by adding those lines in build.prop:

ro.config.low_ram=true
persist.sys.force_highendgfx=true
dalvik.vm.jit.codecachesize=0
ro.config.max_starting_bg=8
ro.sys.fw.bg_apps_limit=16
[Samsung Galaxy Nexus] girkev:
Yes, its the gapps.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] skyleth:
Maybe this should be added to the next nightly

Enviado desde mi GT-I9300 mediante Tapatalk
[Samsung Galaxy Nexus] bamtan2:
In my experience, lowram mode is not necessary. So I think [MENTION=2633638]Ziyan[/MENTION] made the right decision leaving it out. But I ALSO think it is a good tweak for users to manually make! I think these two are the most important ones:

ro.config.low_ram=true

persist.sys.force_highendgfx=true

That said, I don't know how to easily add that tweak myself. I don't see ro.config.low_ram in Kernel Adiutor, and it doesn't stick when I add it manually using the Kernel Adiutor build.prop editor. Maybe I'm doing it wrong.

[MENTION=2633638]Ziyan[/MENTION], what would happen if ro.config.low_ram = false was added to build.prop? Would that make it easier for people to tweak it to = on?

---------- Post added at 01:05 AM ---------- Previous post was at 12:30 AM ----------

I think:

Download 5.1 nano from here: http://opengapps.org/

Turn phone off.

I think volume up + power simultaneously boots into recovery mode. Most people use TWRP for recovery.

Browse to the sdcard downloads folder and flash the gapps zip.

Alternatively, the way I do things sometimes:

Enable developer mode in android (tap build number in settings: https://wiki.cyanogenmod.org/w/Doc:_developer_options )

Enable CM root mode in developer settings

Enable advanced reboot in developer settings

Now you can reboot to recovery from inside android, just by holding down the power button, or by using an app like Flashify to flash the gapps zip automatically in conjunction with TWRP recovery. ( https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en )
[Samsung Galaxy Nexus] Childe89:
You can just add them to build.prop if they are not present :) Then save, restart to recovery, wipe cache and dalvik, and you are lowram :)
[Samsung Galaxy Nexus] mateusm:
Just wanted to congratulate everyone's efforts devoted on the official nightly builds posted on cyanogenmod.org. It's amazing how far everyone's knowledge and experience has taken our maguro. I'm happy and can't wait to update, what is still my daily driver.
[Samsung Galaxy Nexus] momojuro:
For some lazy guys, it would make it easier yes ! :laugh:

Adding ro.config.low_ram=false to build.prop file will have the same effect as removing the one set to true (ro.config.low_ram =true). :)

By the way, did someone tried to change ART's compiler filter flags ? Setting them to the ones that I'm suggesting below helped me a lot to reduce some rare freezes and also to make the compilation process faster on my OMAP4 tablet :

dalvik.vm.dex2oat-filter=verify-none
dalvik.vm.image-dex2oat-filter=balanced

Note that you must wipe dalvik-cache after that you added those lines, or changed your original ones.

Best regards.
[Samsung Galaxy Nexus] cloud_strife84:
How is battery life? It seems it consumes a lot of battery... Maybe my battery is faulty

Inviato dal mio LG-D855 utilizzando Tapatalk
[Samsung Galaxy Nexus] bamtan2:
replacing your old battery with a GOOD new one will make a BIG difference. unfortunately I had to buy 5+ batteries before finding a GOOD one with high capacity. and unfortunately the one I bought is gone from here: http://xdaforums.com/showpost.php?p=61555946&postcount=141

I recommend EVERYONE get a new good battery... but unfortunately I have none to recommend anymore ;( there may be a good one out there to find. but a lot of batteries are scams with 900mah instead of 1900mah ;(
[Samsung Galaxy Nexus] :
Last year I bought two 2000 mAh extended batteries directly from Samsung. They cost around 20$ each.
[Samsung Galaxy Nexus] casaprocida:
After 6 month I used the stock 4.3 firmware i install this. Battery is awesome, it gain 20% each day same use.

Search for the Anker nattery on Amazon. I use this brand on different devices and I have always a good feedback from them.
[Samsung Galaxy Nexus] hgmichna:
I also use one with good success.

Certainly better than the "original Samsung" batteries you get for $10. They are all cheap chinese fakes. Some fail after half a year.
[Samsung Galaxy Nexus] blackbird5308:
Hey man, i followed your answers since you started mentioning those sources, did you finally reach your TI contact? Is there some hope left? :)
[Samsung Galaxy Nexus] blystad:
Well, it's challenging. We've tried using a couple of our TI contacts, but they've had some challenges helping us. They want to help us, but are unsure on the correct process, since the OMAP team is laid off. I believe normally this would be available for download on TI CDDS, after a request has been made, but that way doesn't work anymore :(

So we're trying the normal way now: a post on TI E2E where we request access to the source code. The support personell there has directed the request to the correct parties, and we're awaiting further information.
[Samsung Galaxy Nexus] cloud_strife84:
It would be great! This means it's possible to make appropriate driver and blue line during videos will disappear right?

Inviato dal mio LG-D855 utilizzando Tapatalk
[Samsung Galaxy Nexus] pepexzz:
3.4 KERNEL maybe... nice
[Samsung Galaxy Nexus] blystad:
There will be various improvements. The blue/green line...I'm not sure. See, we don't have that issue on our device..Might be that the Ducati firmware on Galaxy Nexus screws up something..I don't know. We use a newer version of the ducati firmware.

On another note, [MENTION=2633638]Ziyan[/MENTION] - Since I know you're not too happy about Marshmallow and memory usage, check out this - https://android-review.googlesource.com/#/c/195062/ . Might save some space. AOSP is actively trying to get rid of dlmalloc from what I can see.
[Samsung Galaxy Nexus] cloud_strife84:
New firmware? Where did you find it? Maybe ziyan can use it.

Sorry but I don't understand the rest of conversation as I'm not an android developer...

Inviato dal mio LG-D855 utilizzando Tapatalk
[Samsung Galaxy Nexus] blystad:
I work at a company that manufactures a OMAP4 based smartphone. I.e. it uses the same CPU as what's on the Galaxy Nexus :)

https://www.pixavi.com/product/mobile-devices/intrinsically-safe-smartphone/

Ziyan probably couldn't use it, since we use a different camera module, and we have a 3.4 based kernel where a new Ducati driver was added. The ducati file on Galaxy Nexus is called ducati-m3.bin while on our device it's ducati-m3-core0.xem (since that's the new format). If there are major differences I don't know. The only thing I've learned so far is that TI code is a real mess...
[Samsung Galaxy Nexus] cloud_strife84:
That's great!!! Why don't you contact ziyan to cooperate? There is another thread which wants to create a 3.4 kernel. Maybe with your help they can obtain a working kernel

Inviato dal mio LG-D855 utilizzando Tapatalk
[Samsung Galaxy Nexus] blystad:
If only it was that easy :) While we have the same processor (OMAP4460); the same power management ASIC and the same audio chip...everything else (screen, sensors, cameras, RAM, 3G modem, eMMC, etc.) is different. We're closer to the TI Blaze development platform then we are to the Galaxy Nexus.

EDIT: As for the kernel, Ziyan is free to request our kernel under the GPL license, but I doubt it would do much good...Most of our changes are for things specific to our device (e.g. additional drivers, or small bug fixes). We base that on the TI 3.4 kernel, available here: http://www.omappedia.org/wiki/4AJ.2.5P2_OMAP4_Jelly_Bean_Release_Notes which is also what Ziyan and others has used for their 3.4 kernel.
[Samsung Galaxy Nexus] cloud_strife84:
I see... Anyway you can try...

Inviato dal mio LG-D855 utilizzando Tapatalk
[Samsung Galaxy Nexus] blackbird5308:
Nice to know! I'm no developer too, but i understand what the implications of such a transition are :) Well, unless [MENTION=2633638]Ziyan[/MENTION] wants to rebase the entire kernel to 3.4 and try to use all the new Ducati binaries! But as i can see, almost every maguro is being put in a drawer now, i think it's just time to move on :)

On the other hand, how is your product working? I guess you're contacting TI and everything to get it up to 6.0, right? I would love to see how it does perform compared to a maguro by now :)
[Samsung Galaxy Nexus] blystad:
We're currently working on transitioning from 4.2.2 -> 5.1.1 in one huge jump (with smooth over the air updates, so our customers can upgrade their phones out in the field). We're probably going to skip 6.0, but we might jump to Android N (6.1 / 7.0). The main constraint is RAM, of which we're working on increasing to 2GB on new devices we produce.

We havn't asked TI for anything actually, until now (the graphics card driver sources), since we have had the source code for everything we needed until then. We have a small team consisting of excellent engineers, and some with TI background, so we manage.

The main challenge has been passing the Android Compatibility Test Suite (CTS), a necessity for getting official access to Google Play Services - followed by performance. For CTS the main painpoints has been camera and video encoding/decoding...There has been a huge change in how buffers work in 4.4 and newer, and that has created some issues for us, but we have an expert in Video encoders/decoders that is working on those issues. For the camera, it has been adopting our and TIs camera changes to the new Camera 2 HAL. But we have also have a Camera expert that knows his way around Ducati :) so that helps.

For performance we've been monitoring what happens on XDA, CyanogenMod and various other ROMs, and tried to apply these. Lately we've also been surveying the Android Gerrit. It's important for us to have a stable product, so we can't apply all the performance improvements which one might find here on XDA, which has the possible sideeffect of making the device unstable.

We're looking to officially release Lollipop for our customers in the next few months (we need to fix ~100 CTS errors in Camera and Video codecs, then do internal and external testing and certification). I've said this a few times, and I'll say it again: It probably wouldn't have happened if not for the great work done by multiple people here in the XDA and the Galaxy nexus community :) That's also why I hope we can get the graphics card drivers. Even though we can't share the source, we can share the binary blobs and maybe bring some new life in the Galaxy Nexus, and fix some of its quirks.
[Samsung Galaxy Nexus] zingzangripper:
very nice work here. glad that the community is still working around maguro! noticed that the incoming calls don't turn on the screen right away. (3-4 sec delay)

do you have any tweaks or tricks for better performance? is there a more suitable kernel for this rom?
[Samsung Galaxy Nexus] hgmichna:
Perhaps this cannot easily be improved on the Galaxy Nexus. This ROM uses zRAM to extend the scarce RAM on this device. Obviously this does not make RAM operations faster. It is a price to pay for keeping this phone in operation with the ever-growing Android and the seemingly even faster growing Google apps.

In my view it is a very good compromise.
[Samsung Galaxy Nexus] zingzangripper:
i mean, the more apps you install the slower the phone gets. it will get smoother if you unistall apps like facebook and facebook messenger for example.

back in a kitkat rom i user trimmer app with good results. any worth using it with cm 12.1?
[Samsung Galaxy Nexus] hgmichna:
In theory, no, because at least the newer Android versions trim their internal memory automatically.
[Samsung Galaxy Nexus] tmxda:
After flashing cm-12.1-20160125-NIGHTLY-maguro.zip, I'm getting constant notifications about Trebuchet crashing. If I select submit crash report it says:

.... [CRASH] com.android.launcher3 threw java.lang.IllegalArgumentException ...

I can't launch any apps due to this error. What can I try to fix it?
[Samsung Galaxy Nexus] hgmichna:
Trebuchet crashes

My first try would be:

Take screenshots of all your desktops, copy them to a computer or print them.

Delete the data of Trebuchet.

Reboot the phone.

Rebuild all your desktops manually, guided by the screenshots.

Does anybody have a better idea?
[Samsung Galaxy Nexus] tmxda:
I did these steps below and it worked a lot better now. I previously didn't do the factory reset and format system.
[Samsung Galaxy Nexus] Steamwave:
I flashed the latest nightly on my dad's Nexus.

Everything seems to work fine except MMS.

He can't send/recieve it.

Tried messing around in settings but can't find any way to fix this.

Any ideas?
[Samsung Galaxy Nexus] playitlouder:
Check your APN Settings.

---------- Post added at 10:04 PM ---------- Previous post was at 10:02 PM ----------

Thats a 5.1 issue.

Also experienced that on my Nexus 5 with stock AOSP.

It's behaving differently on 6.0. There the screen never turns on, if the other party has hung up. You have to actively toggle the power button twice.
[Samsung Galaxy Nexus] Steamwave:
Everything seems to be okay in APN just same settings as on Orange website.

Still not working.
[Samsung Galaxy Nexus] playitlouder:
Try again with the wifi turned off and mobile data on.

If it still wouldn't work, grab the Andy Log App and post a logcat.
[Samsung Galaxy Nexus] Steamwave:
Here it is:

pasted.co/444daa64

(it's too long for pastebin and too large for attachments so I had to use this website)
[Samsung Galaxy Nexus] Valberu:
You can try this, it finally worked for me with Orange too, after hours of useless workarounds :

copy the MMSC field of the mms APN

delete the mms APN

go to the data APN,

paste the MMSC field,

in type add ",mms" at the end

(for example my type field is now default,supl,mms)

You can delete all other APNs..

I hope this will work :)
[Samsung Galaxy Nexus] Steamwave:
Thank you very very much!

It works.
[Samsung Galaxy Nexus] tenchi-man:
lowram flags pros/cons?

Can anyone explain the pros & cons for using the lowram flags in CM12.1 ?

Does CM11 have such flags?

Thanks
[Samsung Galaxy Nexus] zingzangripper:
no new nightlies?

anyone tried any themes? which do you recommend?
[Samsung Galaxy Nexus] cloud_strife84:
There are not free good themes it seems...

Inviato dal mio LG-D855 utilizzando Tapatalk
[Samsung Galaxy Nexus] bamtan2:
Some apps check the flag, but most probably don't, and basically none have documentation that tells you either way. Chrome will keep fewer tabs open, for example.

Android tweaks some things, but the biggest is the graphics, and people disable that change by manually forcing the graphics up to high whenever lowram is on. The remaining changes are so insignificant that ziyan couldn't tell the difference and didn't care to leave lowram on anymore.

It's a fine tweak for anyone who wants to do it. But it's not a big deal or a clear win.
[Samsung Galaxy Nexus] Ziyan:
I like Ash :)

There was a problem on CM's end making all the cm12.1 nightly builds fail in the last couple days, but it's now fixed, a new maguro nightly should be up today with zcache disabled, I think it performs a tad bit better ;)
[Samsung Galaxy Nexus] djkk16:
Which builds should one download for performance and stability? Like should i download and flash the unofficial builds with zram and stuff or the official nightly builds ?
[Samsung Galaxy Nexus] Ziyan:
Stick to the latest official nightly builds, they have all those - I'm going to remove the builds from the downloads section here soon :)
[Samsung Galaxy Nexus] cloud_strife84:
Ash theme is great!! It's battery saver thanks to amoled!

Thanks for your job ziyan! Is it possible to add native f2fs support?

Inviato dal mio LG-D855 utilizzando Tapatalk
[Samsung Galaxy Nexus] rsaka:
What theme is that?
[Samsung Galaxy Nexus] cloud_strife84:
Ash theme

Inviato dal mio LG-D855 utilizzando Tapatalk
[Samsung Galaxy Nexus] Ziyan:
It's already present :)
[Samsung Galaxy Nexus] cloud_strife84:
Is there a wiki to follow to enable it?

Inviato dal mio LG-D855 utilizzando Tapatalk
[Samsung Galaxy Nexus] Atento:
You just need a recovery that supports it. The rom itself already supports it a long time ago.
[Samsung Galaxy Nexus] cloud_strife84:
Does Latest official twrp support it? Please explain me steps to do it. Do I have to format partitions?

Inviato dal mio LG-D855 utilizzando Tapatalk
[Samsung Galaxy Nexus] playitlouder:
PitchBlack FTW!