yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Nabbolo:
I came to the conclusion that my problems are more related to the famous eMMC brick bug that to the ROM iself.

I didn't know about that bug, and some people say that with 4.4+ Android it shouldn't even be a thing, but I keep to have the same symptoms.

Also, it seems that my chip was produced in March 2012, so it shouldn't be affected, but I heard that switching to f2fs partitions should completely solve the problem in every case.

So my question is: did someone notice a huge improvement in performance switching to f2fs because of fixing this bug? If not, what is the main reson for switching to that?

And last and more important question: what is the procedure to switch from a stock filesystem to f2fs partitions on Galaxy Nexus? I have already downloaded the Zyan modded TWRP, but I don't know if I have to convert the ROM file to make it work with f2fs, and also I don't know in which order I should flash the recovery, the ROM and perform the partition conversion. Is there a noob-proof guide? Thanks
[Samsung Galaxy Nexus] klbrn:
I switched from cm11 to cm12 today, and decided that since I was already going through the wiping trouble I might as well switch to f2fs partitions. Steps I followed:

Installed the twrp-2.8.6.0-maguro-f2fs.img that you can find on the downloads section (I did it using the bootloader + fastboot method)

Using TWRP, on the wipe->advanced wipe section, I converted both the "data" and "cache" partitions to f2fs, one by one. After converting the "data" partition it showed an error message about "mount -o bind /data/media/0 /sdcard" failing. In my case, this was because the "/data/media/0" folder did not exist. I'm not sure whether this is necessary or not, but I connected through "adb shell", created the directory with "mkdir /data/media/0" and bind-mounted it using "mount -o bind /data/media/0 /sdcard" at this point.

Then I simply wiped the "system" partition (you should not switch this to f2fs) and the dalvik cache

Finally, I installed CM12.1 using the standard procedure (I used cm-12.1-20150805-UNOFFICIAL-LOWRAM-maguro.zip and tk_gapps-modular-pico-5.1.1-20150816-signed.zip). No conversions nor anything needed for that.

The phone has been working properly for a few hours now. General GUI performance is awesome, app performance is slightly worse than before but totally usable, and I haven't found any bugs yet. We'll see about battery life, but I'm pretty happy for now.
[Samsung Galaxy Nexus] hanschke:
will we get a new build soon? maybe with xposed support please :)
[Samsung Galaxy Nexus] CyberTech28:
Idea

Maybe a idea to post the kernel for people who have flashed a different and is not working for them.

No way to get back without flash the build again
[Samsung Galaxy Nexus] Childe89:
You can get original kernel from ROM zip :) Open it with some archiver (WinRar for example) and take the "boot.img" file.

Then flash it through TWRP recovery (wipe cache and dalvik before), don´t forget to switch to img files in Install menu to be able to select it.

And it will probably ask if you want to flash boot or recovery, so select boot option.

I´m not sure though if the kernel will work properly, tweaks and fixes from the different kernels might be still active sometimes...
[Samsung Galaxy Nexus] BlackSoldierB:
My lockscreen background stays black.

How do i fix that?

PS: Great ROM, performance is like new :D

Edit: I will try "klbrn" steps.

Edit 2: These steps did the trick, I probably restored data of an old system application with Titanium Backup.
[Samsung Galaxy Nexus] Nabbolo:
Thank you so much for your contribution!
[Samsung Galaxy Nexus] vannix_a:
I've read in some post back that in the ZMoD the purple line on the edge of the screen while recorded was fixed. Can anyone confirm? I know it's a small bug but for me it's pretty annoying... :(

Now I returned to the 07/28 build because I wasn't able to disable the low ram mode, also with the lowram flag set to "false", so how can I disable this guys?

Anyway good job Ziyan! :good:
[Samsung Galaxy Nexus] n76:
I am running the June 17th build of ZMoD and just did a test video. I had thought it was fixed too (I recall reading about an error on the stride setting that as fixed). But I am still seeing a blue/purple line/band on the right side of the video when played back on both the phone and on my laptop.
[Samsung Galaxy Nexus] musical_chairs:
Stride setting was fixed, big green lines went away. Then, focus mode / snapshots during videos was fixed, and the little purple line appeared. So that fix was a trade-off.
[Samsung Galaxy Nexus] Childe89:
Can someone please type the default MinFree settings from latest LOWRAM build?

I´ve been experimenting with custom settings, and forgot to save stock values :o
[Samsung Galaxy Nexus] musical_chairs:
A user here posted the minfree settings before and after the low_ram flags were added:

http://xdaforums.com/showpost.php?p=62397112&postcount=200
[Samsung Galaxy Nexus] BlackSoldierB:
Does anyone know where i can find the "Do not disturb" settings for the Heads-up notifications?

In CM 11 i could select an app where it didn't show them (for example a video player).
[Samsung Galaxy Nexus] bamtan2:
Thanks for digging that link up. I replied to say that I think those lmk minfree settings are too small for Galaxy Nexus under 5.1. Most modern apps will need 50MB free or more, so clearing less than that is pointless IMO. And Galaxy Nexus under 5.1 has limited RAM, but not so limited as a 512MB device. I feel like those tiny minfree settings were made for tiny android 2.3 apps ;)
[Samsung Galaxy Nexus] playitlouder:
Well the new values cause black screens in the play store and lags all over the place.

Problem is changing them messes with the animations, the notification bar malfunctions and all the transparency is gone.

Can someone tell me how they changed their values without messing everything up?
[Samsung Galaxy Nexus] Lex_Michdeandroid:
Awesome post! Exactly how everyone should post their experiences! Keep them coming!
[Samsung Galaxy Nexus] KarlusHTC:
I've finally installed CM-12 on my Maguro (cm-12.1-20150805-UNOFFICIAL-LOWRAM-maguro.zip). Done a clean install + gapps minimal, its working fine, but I noticed that the RAM now only shows 750mb, this is very strange, this device has 1gb RAM.

Does anybody have this problem, is there a fix for it?

Thanks in advance for the grate job done with this release.
[Samsung Galaxy Nexus] nikodr:
We don't have a 3.4 kernel so part of ram is reserved for playback of videos. The ducati codecs i think reserve 200 of ram. Indeed it has 1 gig but we never had that much. Back in the old days we only had 693 of free ram. Newer kernels have slightly more like 750 or 760
[Samsung Galaxy Nexus] KarlusHTC:
Thanks [MENTION=2744041]nikodr[/MENTION]
[Samsung Galaxy Nexus] silentz0r_:
I know that there's a poll about this, but since I haven't tried the lowram settings myself what do you guys have to say about it? I'd like to hear both sides (why people votes for Yes / No).

Apart from a manual restart every 3-4 days, I'm perfectly happy with the phone as it is running now (it can just get super bugged sometimes, mainly if browsing some super heavy website with the default browser).
[Samsung Galaxy Nexus] Vara83:
delete this reply

delete this post , i solved :)
[Samsung Galaxy Nexus] jasonsniper:
is it possible that every gaaps i try to install end with an aborted process? then i reboot my phone and i get all the error messages that gaaps has stopped. Is there another way to install the google play store?

thanks
[Samsung Galaxy Nexus] KarlusHTC:
The way I solved that was to make a clean install, format cache and data install cm and minimal gapps.
[Samsung Galaxy Nexus] jasonsniper:
i did that.

I entered in recovery mode

wipe data/factory reset

wipe cache partition

install zip from card

can you copy a link of minimal gaaps that works for you?

thanks
[Samsung Galaxy Nexus] KarlusHTC:
Hi [MENTION=4617159]jasonsniper[/MENTION],

Before installation i've made the following steps:

Wipe data/factory reset

in advanced - wipe dalvik cache

in mount Storage - format /cache

in mount Storage - format /data and /data/media (/sdcard)

then

I've used this rom http://xdaforums.com/devdb/project/dl/?id=13856 with this gapps https://www.androidfilehost.com/?fid=95916177934550851 as found on this topic http://xdaforums.com/android/software/gapps-google-apps-minimal-edition-t2943330 .

dont know if it is the best way to do it, but it solved my problem.

---------- Post added at 03:05 PM ---------- Previous post was at 02:55 PM ----------

After 2 day of normal use of the Lowram rom, what i can report is that it works fine, a few minor issues of lag opening some apps (hangouts, gmail) but can't expect more from a 2011 hardware. thanks for the great work done with this image [MENTION=2633638]Ziyan[/MENTION] and all the other that have been helping in this development.
[Samsung Galaxy Nexus] ivzn:
"Encrypt phone" issue possible fix?

Hello, [MENTION=2633638]Ziyan[/MENTION].

First of all, thank you for your great work.

However, as you can see according to some feedback in this thread, encryption still is not working.

I've had the same issue. But here a starting point to fix it - jira NIGHTLIES-1746 , review c/107830

I'm software engineer, not a cryptographer, and it took dozen change-build-wipe-flash-test cycles

to "bisect" the issue between cm-12.1/system/vold and aosp/system/vold,

but I hope that this information and provided tiny patch as well will be useful to help for fixing the issue

within the next few commits right into cm-12.1 branch.

Needless to say that encryption of personal data is a very essential part of a good user experience,

especially for a mobile device which can be suddenly lost or stolen.
[Samsung Galaxy Nexus] ASHURiCAN:
Hi, is there a patch to this outside CM?

Thx.
[Samsung Galaxy Nexus] hgmichna:
Tap & go does not work

I just tried to wipe everything, then flash these:

cm-12.1-20150805-UNOFFICIAL-LOWRAM-maguro.zip

tk_gapps-modular-pico-5.1.1-20150816-signed.zip

During the first start I did the Tap & go procedure to restore the Galaxy Nexus to the same state as that of my other phone, a OnePlus One running Android 5.0.2/Cyanogen 12S, but it went very quickly and did not restore any apps. Bluetooth was started on both phones, but only for a couple of seconds.

Apparently only my Google account was transferred and probably some system settings, but not my CyanogenMod account, no apps and thus none of their settings.

The procedure progressed to the next point where I could choose from my known and backed-up devices. So I chose the same phone I first tried with Tap & go, and ran into the next problem, which is related to the on-screen buttons.

After selecting the device, I got a list of apps to restore where I could check or uncheck each app. However, the DONE button at the bottom was unclickable, possibly because of the overlaid on-screen button row at the bottom. The rightmost button overlaid the DONE button on the app selection input dialog. It did not do anything, but apparently it prevented me from hitting the DONE button. My only choice was to back out of the app selection dialog and accept to restore all apps.

It is sad that Tap & go does not work, and I have the feeling that both defects are not very easy to fix. In addition, testing is somewhat time-consuming.

I'm not sure how I would classify these defects, but I would say that they are at least moderately severe. I also don't know whether either of them is caused by a bug in the ROM or merely by some incompatibility between the two phones or something else. The real question is how many users are affected. Am I the rare and unlucky guy and everything works well for most others or does everybody have these defects? Has anybody else here seen them as well?

Of course one more or less acceptable way out would be to state that Tap & go does not work and that restore from a Google-backed-up phone works only without being able to select apps, so it's either all or nothing. If people are being warned, I would consider that acceptable.
[Samsung Galaxy Nexus] romut:
Hi,

I've updated my wife's GN with the 20150805 ROM (not LowRam), and I see it has been removed from the download list, why? I've not followed all the lastest developments of this thread, so I guess I've missed something ; especially because my wife feels extremely difficult to catch the 3G network with that ROM release.

Thanks.
[Samsung Galaxy Nexus] moe61:
Slow response in lowram

Hi there,

since the lowram update I have response problems with my phone.

If I got a call and the phone was in standby mode it takes up to 30 seconds until it turns the screen on and i can accept the call. The response time was already slow without lowram patch but now i miss most of the calls. Furthermore it is not realy useabel after wake up for a few minutes.

If it is freshly boot or woken up for at least 2 minutes it works blazing fast.

Has anybody a idea to solve this?

thx

moe
[Samsung Galaxy Nexus] hgmichna:
Preferred network type cannot be set. No SMS reception.

Just noticed: I cannot set the preferred network type to 2G. When I do, it always jumps back to 3G.

And I do not receive SMS. For the test I was roaming, but this has always worked before I installed CM 12.1.

Has anybody else seen either of these failures?
[Samsung Galaxy Nexus] anthony216:
stable

when will it be stable
[Samsung Galaxy Nexus] hgmichna:
Stable

On October 13th, 10:30 am.
[Samsung Galaxy Nexus] ASHURiCAN:
Red October? [emoji14]
[Samsung Galaxy Nexus] [.::MDT::.]:
Same here, I keep missing calls.

Tried to uninstall a lot of apps but still missing calls.

It does not seem to be a RAM problem (or is maybe due to low ram update?), but maybe a dialer problem?

I have to try what happens if I delete all the calls logs...
[Samsung Galaxy Nexus] NCguy:
Is that a Friday?
[Samsung Galaxy Nexus] hgmichna:
Stable

The day when it's stable? Sure.

Hm, that would be Friday, 2017-10-13.
[Samsung Galaxy Nexus] borizz27:
After trying lowram for about 2 weeks, I went back to 0728 without lowram. Lowram made my phone very laggy (sometimes it would just hang for 10 seconds). All that is gone with the normal build, it's snappy again.
[Samsung Galaxy Nexus] moe61:
I don't think it's about the call logs because the whole phone is slow after wake up.
[Samsung Galaxy Nexus] nikodr:
Flash r22 auto kernel. Apply Nephilim settongs and phone Ali be fast. That's what i have for the past months. R22 phone is like new. No lags.
[Samsung Galaxy Nexus] [.::MDT::.]:
I agree.

Nevertheless, after deleting the 500 calls log, the dialer now gained a few seconds in responsiveness... still very slow though...
[Samsung Galaxy Nexus] Ziyan:
New build up with tweaked lmk values for the lowram flags, which should remove the slowdowns some of you are noticing - report back how it works :)

I noticed that too - did you try to press the power button to wake up the screen earlier? Seems like some sort of Android bug, as most of the times, if I press the power button, I can instantly accept the call.
[Samsung Galaxy Nexus] hanschke:
does xposed work?
[Samsung Galaxy Nexus] [.::MDT::.]:
Thanks for the new build [MENTION=2633638]Ziyan[/MENTION]!

Flashed it over the previous one (i.e. directly flashed the latest zip) and now it takes "only" two rings before the phone wakes up and I can see the call and answer it.

So a bit better now imho.
[Samsung Galaxy Nexus] mgBd:
Hi [MENTION=2633638]Ziyan[/MENTION], Is that 31/08 build is based on the 12.1 snapshot of this monday ?

Anyway, thank you for your hard work ! :)
[Samsung Galaxy Nexus] loryevolution:
Google camera app crash on settings with 31/08 build.
[Samsung Galaxy Nexus] nWaf3t:
Stock camera crashed also yesterday with 31/08 build
[Samsung Galaxy Nexus] chakme:
Hi!! First of all, thanks so much [MENTION=2633638]Ziyan[/MENTION] for the great job!!

I've flashed last version cm-12.1-20150831-UNOFFICIAL-maguro and for me it's working very smooth. But in one day of use, i've got two unexpected reboots. Last reboot, it happened some minutes ago and the phone was only connected to PC, by USB, just charging. I was not using it and suddenly it rebooted by it's own.

I'll attach a catlog, saved just after it booted. As I'm not a developer I don't know what to look for and I don't know if in this file, there is something important. As it was two unexpected reboot, in only one day, hope it can help anyway.

Thanks again for the great job you guys are doing!!
[Samsung Galaxy Nexus] musafercom:
Thanks for the great job

just as a feedback my device stock on a boot loop after flashing the latest build as it did with the low ram.

So i went again back to the 28th july build and happy with it.

Best regards
[Samsung Galaxy Nexus] Childe89:
Works great for me, flashed over 20150805, no problems with stock camera or restarts, everything stable.
[Samsung Galaxy Nexus] moe61:
If I try to use the power button the ring gots mute and the screen is still black. But on a second push on the power button the screen turns on and I can answer the call. The whole process is still laggy though. But I mostly can answer the call except for waiting to turn the screen on by itself.

I'll try the new build and will report back.
[Samsung Galaxy Nexus] hgmichna:
Testing the 2015-08-31 build

Flashed it, without flashing Google apps as recommended, and everything works fine. Tried the CyanogenMod camera and the Google Camera and could not find any fault with these.

Tested and found working properly: compass, GPS, K-9 (email), Hangouts.

Not tested yet: calling, being called, SMS.

One peculiarity is that while booting it displays a starting apps dialog. Is that normal?

Thanks for the good work! I hope that this CM 12.1 will soon become an official CyanogenMod OTA update. There are still many Galaxy Nexus phones around, and they are very beautiful phones, still eminently useful in spite of a slight slowness and not too much RAM.
[Samsung Galaxy Nexus] nikodr:
Ιf you want to make most of your nexus default settings on kernel are too slow.Better flash btsmitty r22 kernel and apply the nephelim settings as well as overclock the gpu and cpu.With a cpu on 1.65 ghz and gpu to 507 mhz and with nephelim settings i can almost feel like there is no lag at all and that i have a decent phone running android 5.1.With the default settings of roms most of the times phone lagged like hell.Not anymore though ;)
[Samsung Galaxy Nexus] djkk16:
doesnt your nexus heatsup when you overclock your gpu and cpu ? i am on stock settings and on some apps i face that my nexus heatsup alot
[Samsung Galaxy Nexus] hgmichna:
Beta testing

Let us first test this ROM as it comes from the developer, without introducing additional variations, particularly not overclocking.

Testing a modified version is meaningless, because you cannot tell whether a defect is caused by the original version or by your modification.
[Samsung Galaxy Nexus] nikodr:
I undervolt it also,part of those settings is to lower some settings.If you do it right you have some better performance with not much overheat.

For internet usage with the aosp browser or some apps is ok,most heatup occurs when i am on 3g ,and i try to avoid it if possible,with wifi internet usage,there is not much.

Still i think phone is much more usable than if i had it on stock settings.
[Samsung Galaxy Nexus] opticyclic:
Several people are saying that the camera is fine but I haven't seen an announcement that the purple lines are fixed.
[Samsung Galaxy Nexus] djkk16:
mate the only settings for bsmitty kernel by nephilim are for version 5 are you using that ?
[Samsung Galaxy Nexus] sergialess:
AFAIK, Neph's settings are outdated.
[Samsung Galaxy Nexus] nikodr:
No they are not and not from version 5 for sure.

He updated them.If you want them i can post them again.My phone is usable and fast and i have not lag,or have to wait 2-3 seconds to answer a call.I can browse the web very fast with aosp browser or chrome.I dont mind a little extra heat.And as i said it's a matter of priorities.I dont want to waste time with lag.

So nephelim settings even on stock are recommended.

I advice to setup the rom to work ok with not crashes,or fc stuff.Then apply them.You won't regret it
[Samsung Galaxy Nexus] djkk16:
Would be great if you can post them or msg me the settings
[Samsung Galaxy Nexus] sergialess:
[MENTION=5362533]djkk16[/MENTION], here it goes:

http://xdaforums.com/showpost.php?p=58205913&postcount=317
[Samsung Galaxy Nexus] Syakir Imran:
You use the latest build or? ??? and can you provide me the nephilim setting (new one ) the r22 kernel got some changes and not the same as old nephilim setting .... Thankyou
[Samsung Galaxy Nexus] Syakir Imran:
Can anyone share some SS nephilim setting on r22 in Trickster
[Samsung Galaxy Nexus] AMKhatri:
Pretty smooth for a 2011 phone...

Facing a problem with the notification drawer though..

I'm not able to view all the notifications...

Dev, What do I need to provide to help you have a look at this?
[Samsung Galaxy Nexus] hgmichna:
[SOLVED] No SMS Reception

Have tested SMS now. Receiving does not work.

Correction: SMS works fine. There was a misconfiguration due to Helium, which made itself the SMS app to restore SMS, but failed to set it back. Sorry for the confusion.
[Samsung Galaxy Nexus] poo706:
So I built LiquidSmooth yesterday, no errors during building, but it still won't boot past the google logo. Smitty's new L kernel didn't change anything either. Here's the dmesg I pulled while it was stuck at the google logo: http://pastebin.com/m3dYjeP4 . Would someone mind taking a look? I'm no good at reading logs.

[poo]
[Samsung Galaxy Nexus] Ziyan:
First, I'd recommend to pull logs using it's own kernel. Anyways, it seems like your PVR module doesn't want to load (line 1085), which is usually a problem when you change kernels, but keep the old PVR module, as they're somewhat connected to each other (if you change major stuff in the kernel, you need to rebuild the PVR module for it).

I was busy building my UART cable (thanks to the donations, I was able to buy the parts needed for it), which should help debugging stuff like non-booting kernels using GCC 4.8 (fixing this properly), and offmode charging ;)

[Thermal] OK to boot
Initialize runtime thermal monitoring ...done!

-- OMAP 00004460 (version 04460e11) PPA release 1.6.1 Hash 30639809--
Device type: HS, DEBUG OFF
CPFROM HAL API support integrated
THERMAL support integrated: Run Time + Boot time
HDCP support integrated
-- PROD PPA RC3.2.3 --
Reset reason = 000379a2
PRM_RSTST = 00000002
PPA freed 2992 bytes

Texas Instruments X-Loader 1.41 (Apr 24 2013 - 17:28:52)
Starting OS Bootloader from MMC/SD1 ...
[ __omap_twl6030_init_vbat_cfg :49] SA_PHOENIX_START_CONDITION = 0x2
[ __omap_twl6030_init_vbat_cfg :54] SA_PH_CFG_VBATLOWV = 0x80
[ __omap_twl6030_init_vbat_cfg :63] SA_PH_CFG_VBATLOWV = 0x80
[ __omap_twl6030_init_vbat_cfg :86] SA_BBSPOR_CFG = 0x78
[ __omap_twl6030_init_vbat_cfg :93] PHOENIX_LAST_TURNOFF_STS = 0x1
j▒ : 79, nMaxSOC : 99, nMinSOC : 59
[ omap_power_get_reset_source :47] PRM_RSTST : 0x2
wipe_all_ram : all ram wiping is done
* FB base addr = 0xbea70000!
lock PLL Done
* PANEL_S6E8AA0_ID_READ : 0xa2, 0x8e, 0x9e.
message.command =
message.status =
message.recovery =
<hit enter twice to activate fiq debugger>
[Samsung Galaxy Nexus] poo706:
I'm having a hell of a time trying to get a dmesg with the stock kernel! ADB sees me as unauthorized and won't let me pull a log. It did that to me too when I tried to get a dmesg the first time around. Pretty sure I restored KK, booted, authorized ADB, rebooted to recovery, wiped everything, installed LP & smitty, booted and got my log. Trying to do just the ROM, I can't get it to see me as authorized no matter what I do! Is there some trick here?

[poo]

---------- Post added at 06:19 PM ---------- Previous post was at 05:42 PM ----------

Ok, finally got it. http://pastebin.com/wkKSjkGz

[poo]