yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] musical_chairs:
This is gonna make me sound stupid, but what LMK settings changed? I've been sticking with Ziyan's stock CM-12.1 settings for that, and I wasn't aware that there were any changes. Unless the lowram build.prop tweaks are messing with that? Here is the patch that added them:

https://github.com/CyanogenMod/andr...mmit/baaeb5e9e5760842ba520b3fd4a89dd25eade1ba
[Samsung Galaxy Nexus] SynbiosVyse:
Everything, actually.

Your 2015-08-02 build and as far back as I've been recording this has had the following (more aggressive) settings:

12288,15360,18432,21504,24576,30720

Foreground Applications 48MB

Visible Applications 60MB

Secondary Server 72MB

Hidden Applications 84MB

Content Providers 96MB

Empty Applications 120MB

Your 2015-08-17 build has these settings:

3072,5119,8191,10240,12288,14335

Foreground Applications 12MB

Visible Applications 19MB

Secondary Server 31MB

Hidden Applications 40MB

Content Providers 48MB

Empty Applications 55MB

It's totally possible that ro.config.low_ram=true line is what changed this, but from documentation it is not really clear to me. It seems as though that line should be used for devices < 512 MB RAM and for Android 4.4.

For anyone who wants to check this stuff too :

adb shell cat /sys/module/lowmemorykiller/parameters/minfree

to get these values in pages (1 page = 4 KB).

Or use Kernel Adiutor to get the actual MB values.

Hope it helps!
[Samsung Galaxy Nexus] musical_chairs:
Well that's definitely what is happening. Edit build.prop, change ro.config.low_ram=true to false, reboot, and the LMK values go back to the way they were. I'll agree that those lower LMK values are less than ideal. Thanks very much for the info regarding this.
[Samsung Galaxy Nexus] christianpeso:
So is it better for our device to go into build.prop and change that flag for low RAM to false?

Also, has anyone successfully installed Xposed on this? Tried using the latest one, which is version 71 for 5.1.1 devices and I get stuck on the CM logo boot animation.

http://xdaforums.com/xposed/super-alpha-posted-permission-xposed-t3072979
[Samsung Galaxy Nexus] quickdraw86:
I edited the build. prop as you've suggested, and the lag in the dialer is completely gone after a reboot.
[Samsung Galaxy Nexus] kb8no:
Editing build.prop fixed it for me too!
[Samsung Galaxy Nexus] Jimmy_Z:
nice work, only issue I've met so far is some times it makes a short cracking sound.
[Samsung Galaxy Nexus] funkypc:
I had no luck on toroplus. I got stuck on the CM logo as well

Aparently [MENTION=1048318]zzpianoman[/MENTION] has it working on his Rom (but that is not available for toroplus, which is my biggest problem)
[MENTION=4531957]musical_chairs[/MENTION] do you know what it would take to make this Rom compatible with Xposed?
[Samsung Galaxy Nexus] musical_chairs:
Sorry, no, I don't. I'll keep my eyes open though in case I stumble across anything related to that.
[Samsung Galaxy Nexus] SynbiosVyse:
It was mentioned elsewhere in this thread but it's a bug with Touch sounds. Go to Sounds, Other sounds, and turn off Touch sounds. That should get rid of most, if not all, of the clicks. Hopefully you don't like or need touch sounds.
[Samsung Galaxy Nexus] zzpianoman:
Try building without DEX_PREOPT.
[Samsung Galaxy Nexus] musical_chairs:
OK, so there's that, the low_ram flags, and the fact that Ziyan flipped the switch to set SELinux to enforcing. Just when I thought Lollipop was getting stable and wasn't going to be needing much attention. LOL.

DEX_PREOPT is an easy one, so hopefully those of you who like XPosed can use it in future builds. I think I got the lowmemorykiller stuff figured out, by setting the values using the process from CM-12.0, the low_ram flag leaves those values untouched. And SELinux Enforcing breaks the radio entirely on toro, though I think I got that figured out now too. Just gotta flash my new build and see if it all works...

Edit: SELinux seems to be getting along with our sim card reading app now. I'm going to do a clean build and will upload it as soon as I can.
[Samsung Galaxy Nexus] musical_chairs:
Here's the SELinux policy stuff to get the radio working on toro with SELinux set to enforcing, if anybody cares:

(Edit: this is a git commit to the tuna device tree)

diff --git a/BoardConfig.mk b/BoardConfig.mk
index 7fa2c03..b4a4959 100755
--- a/BoardConfig.mk
+++ b/BoardConfig.mk
@@ -123,7 +123,8 @@ BOARD_SEPOLICY_UNION += \
init.te \
mediaserver.te \
pvrsrvinit.te \
- rild.te
+ rild.te \
+ platform_app.te

# Recovery
RECOVERY_FSTAB_VERSION := 2
diff --git a/sepolicy/platform_app.te b/sepolicy/platform_app.te
new file mode 100644
index 0000000..f939793
--- /dev/null
+++ b/sepolicy/platform_app.te
@@ -0,0 +1,2 @@
+# platform_app
+allow platform_app rild:unix_stream_socket connectto;
diff --git a/sepolicy/rild.te b/sepolicy/rild.te
index 975a054..dce18d2 100644
--- a/sepolicy/rild.te
+++ b/sepolicy/rild.te
@@ -4,3 +4,5 @@ allow rild system_data_file:dir create_dir_perms;
allow rild system_data_file:file create_file_perms;
allow rild self:process execmem;
allow rild block_device:dir search;
+allow rild proc_net:file write;
+allow rild sysfs:file write;

I came up with those by using the process described here:

http://selinuxproject.org/page/NB_SEforAndroid_1#Logging_and_Auditing

If anybody sees any glaring errors in this, please let me know. I don't fully understand what I did here, but it seems to be working.
[Samsung Galaxy Nexus] musical_chairs:
OK, the new build is up. Lots of changes, so I recommend making a good backup in case something doesn't work.

Changes:

- DEX_PREOPT has been disabled. This will make the first boot take a bit longer. It also makes the ROM smaller, and XPosed might work now. I have not tested XPosed.

- SELinux is now set to enforcing. This is a kernel build change, and I would really like to leave the kernel sources untouched (GPL compliance and all, and me without a github account). If anything doesn't work that used to on previous builds, please attach /data/misc/audit/audit.log to your bug report.

- low_ram flags have been left enabled in this build, but the lowmemorykiller minfree values are now set to their original cm12.1 values. Hopefully this will give us the best of both worlds. Any unusual system thrashing (aka horrible lag when receiving a phone call), or any excessive app killing or homescreen redraws, please report.

Happy flashing!
[Samsung Galaxy Nexus] christianpeso:
I can confirm xposed works on this latest version. Thanks!

Also, does anyone use Snapchat? I am getting artifacts on the videos with some of them. I did switch kernels for Bsmittys latest.
[Samsung Galaxy Nexus] bamtan2:
IMO these settings are too aggressive and if lowram flag is used, the lmk settings should be re-tweaked to make more sense for how much free RAM Galaxy Nexus has under 5.1, and how much memory modern apps need. IMO the average memory needed by an app is maybe 50MB, and several apps need 150MB, so clearing 10MB, 20MB, 30MB free... is pointless, because still more will need to be cleared when the next app runs.
[Samsung Galaxy Nexus] isobsr:
Thanks. I experienced major slowdown when switching apps and especially when I had large apps (HERE maps) in the background. Killing recent apps would fix it.

I changed minfree from the default

3072,5119,8191,10240,12288,14335

to

8192,12288,16384,24576,28672,32768

and the problem is gone. Not super smooth, but much better. Maybe I'll try your larger values later.

I tried adding it to the /data/local/userinit.sh script, but the writes get blocked by SELinux. So, I need to use adb root shell to change the value after every boot.
[Samsung Galaxy Nexus] SynbiosVyse:
Try Kernel Adiutor. It's free from FDroid store (and I think it's in Play Store as well). I actually use that to set the LMK settings, it will re-apply them on boot automatically. Not to mention, it's a really awesome tool anyways for modifying other things.
[Samsung Galaxy Nexus] quickdraw86:
Yep, 3c toolbox works great too.
[Samsung Galaxy Nexus] PythonNut:
How did you get Xposed working? I still get the following error:

Xposed is not (yet) compatible with Android SDK version 22 or your processor architecture (armeai-v7a)

CANNOT LINK EXECUTABLE DEPENDENCIES: library "libdvm.so" not found.
[Samsung Galaxy Nexus] quickdraw86:
You got that error because you tried to install either the SDK 21 (android 5.0) or legacy (android kitkat) version of xposed... If you read the error, obviously you need a version of xposed made for SDK 22... And because of the hardware of this device, you need the arm version, as opposed to the arm64 and x86 versions...

Read all of the OP in this thread:

http://xdaforums.com/showthread.php?t=3030118

Read the OP of this thread too, and download only the latest beta .apk, which is at the top of the download list in the thread...

http://xdaforums.com/showthread.php?t=3034811

Visit this thread too, read the entire OP, and download the unofficial SDK 22 arm version of the framework .zip...

http://xdaforums.com/showthread.php?t=3072979

Reboot to recovery, make a nandroid backup, flash the framework .zip, reboot system, install the beta .apk. Profit.
[Samsung Galaxy Nexus] traco1:
I flashed this rom last night & I am quite impressed with it . It is smooth & so far everything seems to work. It was one of the easiest roms to flash everything just fell into place with no problems.

Question : I can't get lock screen wallpaper to work. If I could can I use my own wallpaper? How?
[Samsung Galaxy Nexus] quickdraw86:
Great question... Most developers have been recommending:

https://play.google.com/store/apps/details?id=com.miniprepumen.cm12.changelockscreencm12

Works great.
[Samsung Galaxy Nexus] traco1:
Thanks took a minute to figure out how it worked but I got it.
[Samsung Galaxy Nexus] traco1:
Battery Life

What I've seen with this rom ,the battery life goes real well with the screen off. Lasts for ever.but when I play a bit with the phone the battery drops real fast. Things that make you go .... huh?
[Samsung Galaxy Nexus] traco1:
Now that I played with it I see the video camera got some bugs . Play back processing & far right side of screen has kinda a pinkish stripe. I still like the way everything works though . Battery life seems great so far.
[Samsung Galaxy Nexus] quickdraw86:
The stripe on video playback is known, and has been an issue on some builds more so than others...

http://xdaforums.com/showthread.php?p=61229680

http://xdaforums.com/showthread.php?p=60595388

http://xdaforums.com/showthread.php?p=60347862

Kind of a fact of life since TI driver updates ended at 4.2.2... And these builds use ddk1.9... zzpianoman's builds differ in that his use ddk1.8, which seems to minimize video issues to a greater degree, as some older builds of this ROM have done as well.
[Samsung Galaxy Nexus] musical_chairs:
New build up. Includes a very cool under-the-hood change: MWisBest has reverse-engineered libsec-ril_lte.so for toro, fixing a long-standing bug. This eliminates the need for many of the hacks / workarounds needed in kitkat and newer ROMs. Awesome work there from one of the best, MWisBest. :)
[Samsung Galaxy Nexus] quickdraw86:
Glad to see you integrate that so soon, and happy to be on enforcing mode with data too, made a couple scripts to toggle enforcing/permissive for my other devices, but couldn't figure out why data was null after I switched to enforcing until you posted that commit when you posted about the previous update, Thanks.
[Samsung Galaxy Nexus] traco1:
I just installed new build. Looking forward to see how this runs.

Thanks
[Samsung Galaxy Nexus] quickdraw86:
Hmm... On earlier builds, my phone would occasionally idle while trying to connect to data after screen off and back on... Haven't noticed that behavior yet on this latest version. Also, toast messages now seem to display the app icon for the associated application/process, similar to the burnt toast xposed module... Great update.
[Samsung Galaxy Nexus] traco1:
I have a question about boot animation. I want to use the L boot but I get the cm guy. As much as he is cute & all I like the L. a bit better.

I loaded down another theme ----- same thing. Before the latest flash the loaded theme I allowed me to chose the one I wanted. Whats up?
[Samsung Galaxy Nexus] musical_chairs:
IDK - I have the M-style boot animation on mine, I set it to that a few builds ago. I seem to get tired of the CM boot animation about this time every year. :) I'm using the M style free theme from the play store.
[Samsung Galaxy Nexus] traco1:
Themes

Thanks for the Email I will try M . Another dumb question can I use the cm 11 themes also?
[Samsung Galaxy Nexus] musical_chairs:
If my memory serves me correctly, the theme engine changed during the CM11 cycle. For a while themes were referred to as using the 'old' theme engine or the 'new' theme engine. Anything for the 'new' theme engine should work with this ROM; stuff for the 'old' theme engine won't.
[Samsung Galaxy Nexus] kb8no:
What exactly should I notice as being different or improved with this RIL improvement?
[Samsung Galaxy Nexus] quickdraw86:
It'd be best to take a look at MWisbest's post about it over in his thread,

http://xdaforums.com/showthread.php?p=62542349

In practical use, I notice that my phone no longer seems to idle when reconnecting to data after screen off and back on. Also, if I'm driving and leave a strong 4G coverage area, the handoff to 3G, or reconnection to 4G, is much more fluid than before, night and day.
[Samsung Galaxy Nexus] musical_chairs:
Since my phone is activated on prepaid and I keep data off most of the time, I haven't noticed the improvements [MENTION=4471805]quickdraw86[/MENTION] has seen. About the only user-facing change I know of, if you can call it that, is in the 'Phone Testing' menu. Dial *#*#INFO#*#*, select 'Phone Testing', and scroll down to 'Preferred Network Type'. With the fix, it will now correctly show 'LTE/CDMA auto (PRL)' instead of 'GSM/CDMA auto (PRL)' like it had been before. Not a big change for users but a huge help for guys like me. It eliminated (I believe) the need for three patches to two different Android source trees.
[Samsung Galaxy Nexus] quickdraw86:
Yeah, mW said that the latency in deciding between those bands caused a bit of a handoff and connection stall, that fix appears to have worked great.
[Samsung Galaxy Nexus] traco1:
My calendar will not sync with the computer.( I use Google )
[Samsung Galaxy Nexus] svonavja:
Only issue I have found so far is that when starting fresh the tap and go feature seems to be missing.
[Samsung Galaxy Nexus] musical_chairs:
Either install Google Calendar from the Play Store, or use a Gapps package or extension that includes Google Calendar Sync.
[Samsung Galaxy Nexus] traco1:
Calendar sync

I tried a couple of calendars . Did a reboots & data wipes. No Go. Checked settings all good there. I hate to load down a bandaid . But I guess I'll habe to see.

When I was using PA rom or any other everything was good . this is a first time problem .
[Samsung Galaxy Nexus] musical_chairs:
It's not a band-aid; Google Calendar Sync won't work if it's not installed. When you were using other ROMs, were you using minimal gapps packages? Most minimal gapps packages do not include Calendar Sync, but they are preferred with Lollipop due to the small /system partition on our aging phones. You'll either need a gapps package that includes Google Calendar Sync, or a gapps add-on package that installs it, or, you can install Google Calendar from the Play Store.
[Samsung Galaxy Nexus] traco1:
I checked & calendar sync is in the installed apps. I tried the google calendar. I have google apps package.
[Samsung Galaxy Nexus] odmejia:
Haven't used this device in a while but CM is looking nice and smooth like butter! :good:
[Samsung Galaxy Nexus] FMXP:
Been fiddling around with my GNex and this ROM seems to give the "Application Not Installed" error when trying to install some apps, anyone know how to fix this?
[Samsung Galaxy Nexus] lovemachine35:
First off. Downloaded lastest version, did factory reset, flashed rom and pico gapps recommended from first post. Works AWESOME!

Only problem is no mobile data. Only get 1XRTT.

I came from 4.4.4 OmniRom and previous version of radios. Changed to newest radios. Reinstalled your ROM. Still no mobile data. Any recommendations welcome.
[Samsung Galaxy Nexus] quickdraw86:
You may need to go through the activation process again since switching radios... See this post...

http://xdaforums.com/showthread.php?p=62427797

Also, you may just be in need of a new SIM card.

It's also entirely possible that you had a bad download or install of the 4.2.2 radios, or incorrect radios for toro. Toro and most other VZW smartphones utilize two radios, one for CDMA, and one for LTE. If your LTE radio did not install correctly, and you're in an area with poor CDMA reception, that would explain it.

Your baseband in "about phone" should match mine if you're using the 4.2.2 toro radios...

Just some ideas.
[Samsung Galaxy Nexus] Kf_Umbra:
Data Issues

I'm having some bizarre issues with the data connection... It works sometimes, but it drops occasionally. Recently, it dropped and never came back, even after a reboot. Does anyone else have this problem?

edit: well, the signal came back (an hour later) by itself.
[Samsung Galaxy Nexus] PythonNut:
Does this ROM work with F2FS on /system? It seems to reset the partition to EXT4 when it's flashed (although I don't see any message in TWRP indicating that this was done).
[Samsung Galaxy Nexus] quickdraw86:
According to [MENTION=5516338]Musicalchairs[/MENTION] back on page 7 of this thread, this rom doesn't support F2FS. I know that zzpianoman's rom supports F2FS, but only for /data and /cache...
[Samsung Galaxy Nexus] christianpeso:
I have honestly not seen a ROM yet that works with F2FS on System. If my mind serves me correctly, I remember reading a couple years ago that for some reason it did not make sense for System to be F2FS for one reason or another.
[Samsung Galaxy Nexus] PythonNut:
It definitely supports F2FS on /data and /cache. I'm running it that way right now.
[Samsung Galaxy Nexus] quickdraw86:
It doesn't make sense for /system because that partition is rarely written as compared to /data and /cache.

---------- Post added at 07:13 PM ---------- Previous post was at 07:12 PM ----------

Hmm... I don't use F2FS, but MC said it wasn't supported on page 7. Maybe he was mistaken, or it's been added since.
[Samsung Galaxy Nexus] musical_chairs:
It's been added since. Since I'm using Ziyan's kernel and basing off of his device tree (formerly on his own github, more recently coming straight from CyanogenMod), when he added f2fs support, I got it too. :)

Just flashing the zip's I upload will blow away whatever formatting you have on system, since the rom is packaged as a filesystem image rather than a zipped file directory tree like it was on kitkat and earlier. I'm probably using all the wrong words to describe it here... I think I could package it differently and get it to where it would work with /system as f2fs, but since (as I understand it) the gains with f2fs are in writing, and you almost never write to /system, it's not worth the pain of slower flash times (flashing the ROM is much quicker the way it is packaged now) and decreased system partition space.
[Samsung Galaxy Nexus] PythonNut:
Yes, I did some more research, and it honestly doesn't look like there's any benefit to having F2FS on /system. :silly: sorry for the bother.
[Samsung Galaxy Nexus] Kf_Umbra:
This build is blazing fast, but I can't get 4G to work at all.

I did find something in settings, under "About Phone:" it lists the baseband version as "unknown." The IMEI information is fine, though.

I clean-flashed the build (with gapps) and I didn't install any apps from the play store.

This ROM is great, but I really need data to work, and I can't fix it by myself.
[Samsung Galaxy Nexus] musical_chairs:
That's not good. Data works just fine here, but of course I dirty-flashed like always. I do remember seeing similar behavior though a while back. As I recall, I started poking around, trying to figure out what was wrong, and it just started working and has worked fine since. I may have flipped the network mode settings back and forth (4G/3G), and/or toggled airplane mode a few times, don't really remember. Anybody else have any ideas and/or problems with this?
[Samsung Galaxy Nexus] Kf_Umbra:
I tried toggling airplane mode and messed with the APNs to no avail. I went back to stock, and data works fine there. I know it's not a problem with the radios, so something must be wrong with how the ROM handles data connections. I would poke around in the system files, but I have no idea where to start. Does anyone know anything else about this issue?
[Samsung Galaxy Nexus] musical_chairs:
It's the APNs again. If you flash the old APN fix from zzpianoman, it should get things working. I'll bake the proper APNs into the ROM and get another build up in a few days.

http://xdaforums.com/showpost.php?p=57890624&postcount=17

It was my mistake. I put my source code on github recently, and somehow in the process my local source code lost the commit that makes toro copy its own prebuilt APNs instead of using the APNs from CyanogenMod. For some reason our toro's don't like CM's APNs.
[Samsung Galaxy Nexus] musical_chairs:
I did push a newer build earlier this week but had not had a chance to post about it. The APN thing is fixed (again), and it is still using the BFQ scheduler. It is snappy, but it is also crashy - I've been getting black screen hangs and hard reboots every few days. If you're having issues with that, use one of the many kernel tweaking tools on the market and set the scheduler to something else.
[Samsung Galaxy Nexus] traco1:
Are all the bugs worked out of this Rom . I was having calendar sync & tile disappearing.

Anyone?
[Samsung Galaxy Nexus] traco1:
Do you get the calendar to sync?

Any one?

I would definitely use this as my daily if all works well.

Doing a Great Job!!
[Samsung Galaxy Nexus] musical_chairs:
Yes, calendar sync works fine here, I use the calendar many times a day. I've gotten the best results with the Google Calendar app installed. I don't actually use the Google Calendar app itself, I much prefer the Business Calendar paid app, mainly for its month widget. I've also gotten sync to work several times by installing a gapps add-on for calendar sync, but that seems to quit working after a while, I needed to flash an updated calendar sync add-on every so often. I'm not sure why it's not working for you.
[Samsung Galaxy Nexus] kb8no:
I dirty flashed 10/18 build and it is working way better on my hardware than anything I have used in a very long time. Certainly the best Lollypop. Probably better than any kitkat. In particular the laggyness disappeared. I don't know what you did but it is like a normal ROM. Was it the 10 extra RAM? Maybe it's a fluke. Had only one reboot on day 1 of 3. It's multitasking like a banshee, FB and all.
[Samsung Galaxy Nexus] kb8no:
After a few more days I find it reboots at least daily. Otherwise it is great.
[Samsung Galaxy Nexus] musical_chairs:
Unfortunately, the speed increase and the reboots are related, it seems. You can use a kernel settings app (Kernel Aduitor is my current favorite) and set the IO scheduler to deadline or CFQ, that should make the reboots go away.
[Samsung Galaxy Nexus] barry99705:
Anybody getting pops and squeeles when talking on the phone? I've been getting it randomly for the last few weeks. Flashed 20151018 a couple days ago, but still get it. Came from stock.