yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] StardustOne:
Just installed the new build cm-12.1-20150805-UNOFFICIAL-LOWRAM-maguro.zip since I never had Android 5 on my Nexus (maguro) before.

As usual, I have problems with downloading/updating Google Play Services. Nevertheless, great work, the stagefright vulnerability is gone. My Galaxy Nexus is now the safest phone on the planet, again.

My Huawei Honor 6 is vulnerable to stagefright, as all the other phones out there, but the Galaxy Nexus is save. Great work. Thanks a lot for the ROM update.
[Samsung Galaxy Nexus] Settel22:
I also installed the new build cm-12.1-20150805-UNOFFICIAL-LOWRAM-maguro.zip and it works great.

The only thing that doenst work for me is the play store....

I flashed the gapps but the play store was not installed.

I downloaded the apk for the play store, installed it but I couldnt open it....

So if the play store works its a very awesome ROM. Now I need to go back to the older build...
[Samsung Galaxy Nexus] hgmichna:
Why LOWRAM?

LOWRAM devices typically have 512 MB RAM or thereabouts.

The Galaxy Nexus it not a LOWRAM device. It has 1 GB RAM. Why install a LOWRAM system on it?
[Samsung Galaxy Nexus] matorola:
since 100M free RAM is barely enough for 1-2 apps
[Samsung Galaxy Nexus] hgmichna:
You are saying that Android 5.1 and the current gapps are already so big that 1 GB RAM now already counts as LOWRAM. Hoho, things are growing fast!
[Samsung Galaxy Nexus] zieruchan:
Simply because our devices doesnt have exact 1GB. And in the reality all lolipop rom for our devices really hard to run more than 1 apps in the same time.
[Samsung Galaxy Nexus] pobetiger:
Hey Ziyan,

Is it too much trouble to ask for a quick update in the instructions on the xda wiki for the build instructions?

I haven't been able to get a good repo sync since sometime in May. Been using the prebuilt downloads since.

Thanks for all your work!

Thanks,

pobetiger
[Samsung Galaxy Nexus] ASHURiCAN:
Still not Xposed compatible?
[Samsung Galaxy Nexus] nikodr:
The recent kernel development gave roms with 760 available.The stock roms of google had around 693 mbytes of ram.Around 200 mbytes were tied to the hw video player.I think that's why we really need a 3.4 kernel.Better ram management and ram sharing as osmosis said around 200 mbytes would be back,so it is not 512 but rather 760.But 760 is not enough really.
[Samsung Galaxy Nexus] Paglino:
Hello, first of all thank you for your work.

Today I updated my nexus from cm-12.1-20150728-UNOFFICIAL-maguro.zip to cm-12.1-20150805-UNOFFICIAL-LOWRAM-maguro.zip, but I had a problem that prevents me from using the smartphone.

After boot always receiving these messages:

Google Play services is locked abnormally

com.google.process.gapps was interrupted.

I tried reinstalling the Gapps but a message tells me that they are not compatible.

I returned to the version cm-12.1-20150728-UNOFFICIAL-maguro.zip and everything is back to work properly.

Anything else I can do?

Hello Enzo
[Samsung Galaxy Nexus] vortex-5:
Just had a chance to give it a test run. It does overall run better.

There's still a kernel bug that causes a periodic speaker pop when the sound subsystem is shutting off. This is not present on 4.4.4 firmwares.
[Samsung Galaxy Nexus] zeroedout420:
If you look back through the thread someone figured it out. One has to compile the ROM without a certain optimization. This increases boot time substantially, but Xposed works. That dude doesn't seem to be compiling the latest builds without the optimization. If I get around to it I'll post my build. But honestly, it would be faster to figure out how to compile CM and build it yourself :)
[Samsung Galaxy Nexus] Ziyan:
Done, here you go.
[Samsung Galaxy Nexus] ASHURiCAN:
The last build he built was from 24/07. I was using it until yesterday and must say it was very stable and fluid (with Xposed and 7 modules enabled). The only problem was the time to the screen to appear when receiving a call.

I will try to build myself ^^
[Samsung Galaxy Nexus] Noeljunior:
The time to screen on when receiving a call was just a problem in my build?

It seems that most people says that this build (mine or Ziyan's) is fuild but all my three manguros are really slow.

I'm on vocation by now and I have not a good internet connection. I got a neighbourhood's internet connection and I'll update my build (GMT0) today's night.
[Samsung Galaxy Nexus] ASHURiCAN:
Thank you [MENTION=5443123]Noeljunior[/MENTION]! I'm glad to hear from you... [emoji4]

The time to screen On is just worst on your build, that's all. But I agree it's present in all builds. Anyway, it is so good to use Xposed on Galaxy Nexus and CM12.1 [emoji6]

Thx again for your work dear builders :)
[Samsung Galaxy Nexus] musafercom:
Thanks to all

i have similar problem and went back to the previous build with no problems
[Samsung Galaxy Nexus] Ziyan:
Can't help without logcat, gapps works fine for me :confused:
[Samsung Galaxy Nexus] Paglino:
How can I help you (and me :D)?

Where I can find logcat file?
[Samsung Galaxy Nexus] musafercom:
i dont know what you mean by that.

But i get a message on the screen after reboot saying there a proplem or error with gaap and can not use the devise.

I reinstall and wipe every thing still same problem .

Maybe you are using different gaaps . I am using gaaps that you put a link for it here.

Went back to the previous build without any problem and happy with and thanks for your great job and help.
[Samsung Galaxy Nexus] papei:
Have you ever tried formatting the system partition before installing your gapps? Just a thought. I was having the same problem with my Galaxy SII before I formatted the system partition.
[Samsung Galaxy Nexus] gsfores:
The new build is much more responsive for me.

i have been using it for 2 days, no problems so far.
[Samsung Galaxy Nexus] hgmichna:
Latest build: see the downloads section.

The original post says, "Latest build: see the downloads section." Unfortunately there is no link to the downloads section anywhere I looked. Where is it?

I would recommend to change the words "downloads section" into a link, so not everybody who is new to this has to ask.

Edit: Found it. It is kind of at the bottom of the top screen, between a lot of other stuff. I guess it would still be clever to make those two words a link.
[Samsung Galaxy Nexus] Ziyan:
Done

That's odd, as I use those gapps as well (the latest one from the link in the OP), and I simply dirty flashed the lowram build over the previous build, installed the gapps zip again (I always reinstall it just to be sure), and it worked fine:rolleyes:
[Samsung Galaxy Nexus] Paglino:
If I format System partition, I will lose all my data?
[Samsung Galaxy Nexus] hgmichna:
TWRP 2.8.7.0 with this CM12.1?

Has anybody used TWRP 2.8.7.0 with this CM12.1? I saw a 2.8.6.0 image in the downloads, but already have 2.8.7.0 on the Galaxy Nexus and don't want to downgrade needlessly.

TWRP 2.8.7.0 has caused problems on another phone, the Samsung Galaxy S III LTE GT-I9305, because it somehow damaged the partitions, making it impossible to run CM12.1. On that phone the resolution was to go back to TWRP 2.8.5.0, then flash the stock ROM, which repairs the partitions, then flash CM12.1.

After that experience I'm a bit wary, so I thought I should ask.

---------- Post added at 06:07 PM ---------- Previous post was at 05:52 PM ----------

No, the data are in the data partition.

But it is a good idea to do a backup, using the recovery, because that allows you to reset your phone to the complete status before you made changes.
[Samsung Galaxy Nexus] Paglino:
Thanks
[Samsung Galaxy Nexus] hanschke:
xposed work with new build :confused:
[Samsung Galaxy Nexus] hgmichna:
Thanks for the thanks.

The best way to say thanks is to click on the thumbs-up "Thanks!" button under the message you want to thank for. You can still do it. :)
[Samsung Galaxy Nexus] Paglino:
Done!

Also, now the last update works!

For future reference,

I upgraded TWRP to 2.8.7.0, formatted system partition and installed gapps-5.1-arm-2015-07-17-13-29.zip.
[Samsung Galaxy Nexus] Ziyan:
Could the others (who reported gapps related crashes using the lowram build) please try and report back if this fixes the crashes for them as well?
[Samsung Galaxy Nexus] pluk64:
I am using lowram build and gapps-5.1-arm-2015-07-17-13-29.zip.

My Play services crashed(?) today morning and started automatically after a few minutes. Then I checked its version - 7.8.99, which seems to be very recent version. So maybe they just updated and restarted ("crashed") itself.

Other lowram build experience:

Background services (apps) are never restarting, I didn't see any home screen redrawing. Great!

Maybe Chrome browser is sometimes more lagging, but overall I am more happy with lowram build.

Other experience:

I have started using f2fs for /data since 20150728 build (now I am using lowram build). Since then I feel like the phone stays much longer (almost a minute) at black screen with white Google title and white lock during booting. Is it normal?
[Samsung Galaxy Nexus] erOzeOz:
For general information, I had a great experience with this ROM since I started using it (2 months ago).

Here are some details:

I'm using it with

cache and data

on f2fs,

system

on ext4. I used the TWRP 2.8.6.0 modified by Ziyan to support f2fs to change partitions format (available in the download section) .

The GApps edition I'm using is the Google Apps Minimal Edition. I never experienced any issue with it.

I feel that the LOWRAM version brought even more fluidity to the ROM. Now it is not rare that I have 250Mo of free ram while I was generally around 140Mo before.

I usually experience lag during Google app synchronization (when I turn on the internet basically). But I know it and thus don't use my phone during those first minutes.

Great job Ziyan!

Thank you so much for keeping this phone alive in great conditions!
[Samsung Galaxy Nexus] skyleth:
For me was the same. I think it's normal, or at least, my phone was working okay after booting. No major problems except the known ones
[Samsung Galaxy Nexus] chakme:
For me, updating to TWRP 2.8.7.0 made everything go to normal!! No more issues with playservices, playstore or else!!
[Samsung Galaxy Nexus] hgmichna:
Google Apps Minimal Edition works well

I just used TWRP 2.8.7.0 to flash the LOWRAM version with the Google Apps Minimal Edition and can confirm that this combination works well.

Unfortunately the CyanogenMod ZIP file demands a data wipe, so I could not even try a dirty flash, which was my original plan. Why is that? Now I am running through the restore procedure from another phone's Google backup and will look carefully whether the app settings will be restored. That would be an acceptable alternative, although some app's settings cannot be backed up and have to be re-entered manually.

I had first tried to flash the full Nexus-like 560 MB gapps, but TWRP refused, saying that there was not enough space in the partition. I can live with that, as long as the Minimal Edition works so well.
[Samsung Galaxy Nexus] ftrack:
I had attempted 4 to 5 times to flash with 5.1 from cm11 and finaly with low ram edition i am on lollipop 5.1.1 yeah... I must say Ziyan good job, u really re-birth my galaxy nexus. Thanks

for me everything is working fine yes common issue is there but still its better.

Any idea how can i put my phone on vibrate mode which is right now not active. Voice volume is seems little lower.

One more request how can i install Xposed installed i means which zip should i use to flash.. i used this xposed-v70-sdk22-arm-by-romracer-20150808.zip and my phone is stuck on boot ? anyone can help me so please let me know.

Thanks
[Samsung Galaxy Nexus] QuantumSingularity:
After the last OTA update of Google Services the problem has disappeared.

I'm very happy! :)

A few months ago the problem appeared instantly after a Google update.

And now after the new update, the problem is solved.

Thank you all for your replies and ofcource Ziyan for the magnificent ROM.

---------- Post added at 06:54 PM ---------- Previous post was at 06:40 PM ----------

I forgot the screenshot...... :silly:

[IMG="Battery"]http://basbem.home.xs4all.nl/xda/qs-scr06.png[/IMG]
[Samsung Galaxy Nexus] giudech:
try with tk gapps they work well for me, the "biggest" package you can flash is modular nano, because system partition is oversize due to the current stage of development

http://xdaforums.com/android/software/tk-gapps-t3116347

you need to flash a custom kernel before flash xposed, because xposed at the moment needs that the kernel is set to permissive to work, whereas the "stock" kernel that comes with cm 12.1 by Ziyan is set to enforcing

http://xdaforums.com/galaxy-nexus/development/lollipop-kernel-fullauto-r1-aosp-cm-t2994371

http://xdaforums.com/galaxy-nexus/development/kernel-luckyk-t3060700

I hope to be helpful

A BIG THANKS to Ziyan each update brings nice improvements :good: :highfive:
[Samsung Galaxy Nexus] pobetiger:
Ziyan,

Thanks for updating the build instructions. This means we no longer have to add projects in the manifest to manually include source from github/Ziyan right?

BTW, the lowram build is awesome. Matches performance on my wife's Moto G in terms of usability with most apps and lag issue is almost gone. No longer seeing the launcher restart. I can actually use Chrome again.

The phone app is getting a lot more lag and sometimes I will get a black screen during the call and I can't pick up.

Also, it looks like camera app have regressed? I can no longer do panorama and lens blur. And trying to go into settings for the camera app crashes. I have not looked at logcat yet. I will post something if I find it.

Not sure if these are upstream issues from CM or not. I'll look through JIRA and report back if I find something.

Thanks,

Pobetiger

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sgspluss:
Tested lowram also in few of my builds, you'll have more free ram but also less features (e.g. in camera). If you want use all features, you haven't use the lowram version, i know its odd but it is how it is...

Gesendet von meinem Moto G 2014 LTE
[Samsung Galaxy Nexus] pluk64:
...and Google Camera crashes when I tap on settings icon. Stock Camera works well. (I also tried delete data, didn't help.)
[Samsung Galaxy Nexus] sergialess:
Is the lowram stuff applicable to other roms like, for instance ZMoD?. Thanks.
[Samsung Galaxy Nexus] mn.code:
I'am getting artifacts and soft-reboot on high GPU usage. GPU is clocked on default 384MHz and I am able to reproduce artifacts when I test 3D in antutu. When I turn off CPU smart reflex with Trickster app I can even overclock GPU to 512MHz and have no artifacts. [MENTION=2633638]Ziyan[/MENTION] do you think there is a chance it is bug or is my GPU throttling?
[Samsung Galaxy Nexus] iamio:
Hi Ziyan,

if this can help you:

- first time i have installed only lowram update ( no gapps reinstalled ) and after reboot gapps crashed (play store and maps for example ) .

- Second time i have done the same step indicated by Paglino and gapps works well (+:crash remains on clicking setting into Google Camera )

thanks
[Samsung Galaxy Nexus] goblin999:
First of all, thanks to everybody involved with this project because it's amazing!!! I've been using this ROM for several months and, although not without its problems, for a beta, it's great. I'm now testing the latest (lowram) and I'm having a problem which happened also with the previous build... Everytime I try to install Facebook, it ends with an "error 504". I've tried clearing the data and cache, I've tried removing the account, reinstalling everything... The result is always the same. Has anybody else has had this problem?
[Samsung Galaxy Nexus] Couch-pilot:
Flashed cm-12.1-20150728-UNOFFICIAL-maguro - no mobile data UNLESS there is a WIFI connection....

Flashed cm-12.1-20150727-UNOFFICIAL-maguro + cm-12.1-20150727-UNOFFICIAL-tuna_update1, have mobile data when I walk out of router range, so it works...

The cm-12.1-20150727-UNOFFICIAL-maguro mod goes back to no mobile data without WIFI AS SOON as I flash ANY gapps - I tried 4 of 5 different packages.

Have now flashed cm-12.1-20150805-UNOFFICIAL-LOWRAM-maguro.zip with gapps-5.1-arm-2015-07-17-13-29. Everything good, except STILL have the no mobile data issue...It works as long as there is WIFI available...

What have I done wrong.?? - LOL

I too have the same issue as Goblin above - cannot install Facebook....

P.S. A BIG thanks to everyone for this ROM - new life for an old phone!!!

Samsung Galaxy NEXUS Google phone - rooted - flashing to Cyanogen 12.1 Lollipop 5.1 from factory 4.3 Jellybean.
[Samsung Galaxy Nexus] sgspluss:
This should be normal with lowram...

Yes it will work, you can build lowram roms for every device since kitkat.

Gesendet von meinem Moto G 2014 LTE
[Samsung Galaxy Nexus] hgmichna:
Not everywhere though. On my Galaxy Nexus the Google Camera works fine, including its settings, though with reduced functionality. That is apparently normal with the LOWRAM flag.

I used the gapps-5.1.x-20150404-minimal-edition-signed.zip (90.35 MB).

I get these RAM figures:

System 365 MB

Apps 157 MB

Free 228 MB

It seems that LOWRAM would not be absolutely necessary. It has some advantages (more available RAM for apps) and some disadvantages (more system app swapping, reduced functionality). I wish I could change the flag in the running system. Users who typically use only a single app at a time may be better off without LOWRAM.
[Samsung Galaxy Nexus] Childe89:
You can switch lowram mode on and off easily in any rom since 4.4, by editing "build.prop" in system folder.

To switch on lowram mode open build.prop with some editor, and all the way down at the bottom add line "ro.config.low_ram=true" (without the "), save edited file, boot into recovery and wipe cache + dalvik cache. Your phone should now work as a lowram device. :) By default transparency effects are disabled, you can switch them on in developer or performance settings (depends on rom).

To turn off lowram mode, open build.prop with some editor, and all the way down at the bottom remove line "ro.config.low_ram=true" (without the "), save edited file, boot into recovery and wipe cache + dalvik cache.
[Samsung Galaxy Nexus] Ziyan:
Did you notice anything else with reduced functionality? I knew about Google Camera, but didn't find anything else so far.

That's very odd if you use the stock kernel and didn't change the kernel settings. Could you reboot and send a dmesg after it? That would show if there's a SmartReflex bug going on for you.

Btw, I use the following lowram flags:

ro.config.low_ram=true

persist.sys.force_highendgfx=true

dalvik.vm.jit.codecachesize=0

config.disable_atlas=true

ro.config.max_starting_bg=8

ro.sys.fw.bg_apps_limit=16
[Samsung Galaxy Nexus] mn.code:
I succesfully reproduced articacts folowed by reboot and this is dmesg after boot. Also, everything is stock, stock kernel and no setting changed.
[Samsung Galaxy Nexus] Da Magus:
WhatsApp problem with lowram rom

On the lowram rom WhatsApp doesn't show any new messages while on mobile data.

They only pop up after activing WiFi.

Does someone else experience this too?
[Samsung Galaxy Nexus] hgmichna:
Careful there! Editing build.prop can cause boot loops under some circumstances I don't understand yet. I have had that once.

The boot loop is not caused by build.prop having some invalid entry, but by build.prop having been changed in just any way. Under some circumstances Android appears to keep a second copy of build.prop, and if that is different from the first, it reboots. Crazy, but true to the best of my limited knowledge.

So what I recommend is do a complete backup from the recovery before you try to modify build.prop, just in case.

---------- Post added at 01:19 PM ---------- Previous post was at 01:15 PM ----------

There are a lot of devices with 1 GB RAM on the market, for example the entry-level Moto G. Has Motorola used the LOWRAM flag on that device? How about other 1 GB RAM phones?

I think this information should give us a hint, because I suppose they test this thoroughly, and Google may have better background knowledge than we have here.

Who can tell?
[Samsung Galaxy Nexus] musafercom:
hi

could you please help me with a direct download link for TWRP to 2.8.7.0 and right steps on how to install it.

thanks
[Samsung Galaxy Nexus] hgmichna:
Install the TWRP Manager app, select your device, select the desired version of TWRP and let it install. Worked for me on the Galaxy Nexus (and on an i9305).
[Samsung Galaxy Nexus] hgmichna:
low_ram - yes or no?

If I understand things correctly, the consequences are these:

low_ram = no

Full functionality in system and apps

Multiple active apps may not run. Apps running in the background get kicked out.

Some very big app may not run at all. Games come to mind.

low_ram = yes

Reduced functionality. Apps and parts of the system drop and do not offer RAM-hungry functions.

More apps can run at the same time.

Some very big apps can still run.

Given that the Galaxy Nexus is an older phone and will gradually be relegated to secondary functions, given to kids, etc., and given that some here have already complained about negative effects due to lack of RAM, as much as I would like to have full functionality everywhere, I lean towards low_ram = yes.

The current low_ram = yes version on my Galaxy Nexus runs smoothly and reasonably fast, perhaps even better than the previous version, CM 11. That may be worth a little sacrifice in app functions.

Did I miss any important argument for or against?
[Samsung Galaxy Nexus] matorola:
can we add 3rd option/select to current poll, build both versions, like normal and low_ram ? since I can't decide either as well, which version is better. thanks.
[Samsung Galaxy Nexus] Byo01:
Hi,

i have the same problem with WhatsApp.

Activation and sending Messages is just working after activating WIFI.

Another known issue:

Purple lines while recording video.

best regards.
[Samsung Galaxy Nexus] hgmichna:
This looks suspiciously like a defect in WhatsApp. The question is, do other low_ram phones have this same problem?

If this is indeed so, then the right way to fix it would be to tell the WhatsApp programmers about it.
[Samsung Galaxy Nexus] sgspluss:
Well apart of camera not really.

Just what also be visible, it turns off some visual goodies, but as i saw you added some build.prop tweaks which force them :good:

Gesendet von meinem Moto G 2014 LTE
[Samsung Galaxy Nexus] hgmichna:
Smart Lock has no "Trusted face".

I have not tested this on your low_ram=no version, but CM 11 had face unlock on this phone. Could somebody who has the low_ram=no version installed please check Smart Lock?
[Samsung Galaxy Nexus] Byo01:
Sorry for my post, i was too fast.

:o

The solution for my problem was the APN. I had mobile data with the pre-chosen APN. But it was the wrong one. After selecting the right one it worked.
[Samsung Galaxy Nexus] mkaito:
Seeing as some people refer to the maguro as "aged", it is probably regarded as the android phone equivalent of a touch screen abacus. And yet, I really like mine, despite getting slower and slower over time.

Running the latest 12.1 build posted here, does anyone else experience mildly frustrating slowness? I know that this is really subjective, but when it takes you ~30 seconds to answer a phone call, things are pretty darn slow. I've done what I could to get rid of apps I don't use, especially those running in the background. I don't keep much in the form of media on the phone either.

Anything else I can do to make the thing run a little faster? Do you guys have any tricks up your sleeves?

I'm posting this here because I figure everyone here is using the exact same ROM, so we're all on the same page.