yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bsmitty83:
Op updated with M2

changelog

312d553 UPSTREAM: mm/zsmalloc: allocate exactly size of struct zs_pool

86136f0 UPSTREAM: zram: free meta table in zram_meta_free

a991324 UPSTREAM: zsmalloc: move pages_allocated to zs_pool

60f1291 BACKPORT: zram: change parameter from vaild_io_request()

aa7b79c UPSTREAM: zsmalloc: merge size_class to reduce fragmentation

46451b1 UPSTREAM: zram: avoid NULL pointer access in concurrent situation

d094c9a UPSTREAM: zsmalloc: simplify init_zspage free obj linking

7bd45fb UPSTREAM: mm/zsmalloc.c: correct comment for fullness group computation

c7ff5d5 UPSTREAM: zram: use notify_free to account all free notifications

0bf6cce UPSTREAM: zram: report maximum used memory

1c94cd3 UPSTREAM: zram: zram memory size limitation

f8021f2 UPSTREAM: zsmalloc: change return value unit of zs_get_total_size_bytes

b3edb96 UPSTREAM: zsmalloc: move pages_allocated to zs_pool

df3c567 BACKPORT: mm/zpool: use prefixed module loading

ad3510a UPSTREAM: zram: fix incorrect stat with failed_reads

489d37c BACKPORT: mm/zpool: zbud/zsmalloc implement zpool

c45f473 BACKPORT: mm/zpool: implement common zpool api to zbud/zsmalloc

4e537c0 UPSTREAM: zram: correct offset usage in zram_bio_discard

e64edd4 zram: support REQ_DISCARD

9b1fc76 UPSTREAM: include/linux/poison.h: fix LIST_POISON{1,2} offset

a65bc40 ANDROID: android: base-cfg: disable CONFIG_SYSVIPC Android SELinux policies block SysV IPC. New kernels should not be built with it.

b896dc2 ANDROID: exec_domains: Disable request_module() call for personalities

73de670 BACKPORT: pagemap: do not leak physical addresses to non-privileged userspace

1510308 SELinux: use deletion-safe iterator to free list

cdcb5e2 selinux: enable genfscon labeling for sysfs and pstore files

39cd731 selinux: enable per-file labeling for debugfs files.

8be6798 selinux: convert avtab hash table to flex_array

d6c94ba selinux: fix broken peer recv check

589a14a tuners: Add help text to MEDIA_TUNER

44dca7d kernel/hz.bc: ignore.

38c53d8 kernel: Replace timeconst.pl with a bc script

04e4b87 Disable block device entropy gathering

1329c67 scripts: tune XZ for ARM

-added zpool to zsmalloc or zbud

-added memory limiting and usage reporting to zram

( Set memory limit: Optional

Set memory limit by writing the value to sysfs node 'mem_limit'.

The value can be either in bytes or you can use mem suffixes.

In addition, you could change the value in runtime.

Examples:

# limit /dev/zram0 with 50MB memory

echo $((50*1024*1024)) > /sys/block/zram0/mem_limit

# Using mem suffixes

echo 256K > /sys/block/zram0/mem_limit

echo 512M > /sys/block/zram0/mem_limit

echo 1G > /sys/block/zram0/mem_limit

# To disable memory limit

echo 0 > /sys/block/zram0/mem_limit )

# To read max used memory

cat /sys/block/zram0/mem_used_max

# To reset max used memory

echo 0 >/sys/block/zram0/mem_used_max

-zram now supports discard so in theory should free up ram when not in use by zram

-added some other upstream commits to zram and zsmalloc from Android Linux 3.10 kernel
[Samsung Galaxy Nexus] bsmitty83:
Op updated -- M3

Changelog

cdc168 tcp_cubic: better follow cubic curve after idle period Jana Iyengar found an interesting issue on CUBIC :

65dba56 tty: fix memleak in alloc_pid There is memleak in alloc_pid:

ba87322 vfs: fix data corruption when blocksize < pagesize for mmaped data

60bcf1a ext4: backport mm portion of: fix data integrity sync in ordered mode

1d2f879 procfs: use N_MEMORY instead N_HIGH_MEMORY

dde73dd mm, mempolicy: fix printing stack contents in numa_maps

852f75d proc/smaps: show amount of nonlinear ptes in vma

f698b76 proc/smaps: carefully handle migration entries

6105171 proc: report file/anon bit in /proc/pid/pagemap

82bf777 mm: fix NULL ptr deref when walking hugepages

c7db081 proc/pid/pagemap: correctly report non-present ptes and holes between vmas

eebcbc5 revert "proc: clear_refs: do not clear reserved pages"

d07bf49 pagemap: remove remaining unneeded spin_lock()

4d984b8 mm: thp: fix up pmd_trans_unstable() locations

a1b5172 procfs: mark thread stack correctly in proc/<pid>/maps

2420c4b pagemap: introduce data structure for pagemap entry

a270e92 thp: optimize away unnecessary page table locking

21e58de pagemap: avoid splitting thp when reading /proc/pid/pagemap

abe9ee3 mm: distinguish between mlocked and pinned pages

BTW : the M kernels should also work on lp , I have not tried myself , but there is no reason it would not

that is all .....
[Samsung Galaxy Nexus] massoudsh:
I test it on lp and work fine, thanks so much man!![emoji7]
[Samsung Galaxy Nexus] thagringo:
Hi [MENTION=4608636]bsmitty83[/MENTION],

I used your kernels a lot in the past but nowadays I have 2 problems :

1- apparently only synapse can be used for simple tasks like setting CPU low freq to 200. All other apps i tried won't work. Not your fault probably, I know.

2- phone deadlocks if screen is turned off and can only be restarted with a battery pull. Tried to get accurate logs but they look useless to me. Do you want me to send them to you ?

This happens with stock settings.

Other than that all works fine for me afaict and yes the kernel is fine for LP

Would you be able to include bfq io sched in one of the next releases ?

TIA !

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] bamtan2:
Very interesting new features!!! "mem_limit" will help configure ZRAM properly and safely, and reading "mem_used_max" will help us monitor how it is being used. I will need to test this kernel when my testing of [MENTION=2633638]Ziyan[/MENTION]'s latest kernel is complete.
[Samsung Galaxy Nexus] siealex:
Don't you set max screen off frequency less than min screen on?
[Samsung Galaxy Nexus] thagringo:
i know, thats what im using right now :)

nope.

TIA !
[Samsung Galaxy Nexus] bsmitty83:
Op updated --M4

changelog

9a8b204 android: drivers: workaround debugfs race in binder

7486af3 vfs: umount_tree() might be called on subtree that had never made it

4ae129c Revert "vfs: umount_tree() might be called on subtree that had never made it"

6aa676b lowmemorykiller: trace kill events. Allows for capturing lmk kill events and their rationale.

2062a69 wakeup: Add last wake up source logging for suspend abort reason. There is a possibility that a wakeup source event is received after the device prepares to suspend which might cause the suspend to abort.

4a4d621 PM / Sleep: Add wakeup_source_activate and wakeup_source_deactivate tracepoints

7ecdf0b PM / Sleep: Change wakeup source statistics to follow Android

d6ba99a PM / Sleep: Use wait queue to signal "no wakeup events in progress"

9b1189a PM / Sleep: Add more wakeup source initialization routines

e7c7914 PM / Sleep: Make __pm_stay_awake() delete wakeup source timers

2aa0d57 PM / Sleep: Fix race conditions related to wakeup source timer function

7f7d301 PM / Sleep: Fix possible infinite loop during wakeup source destruction

6bb0130 PM / Sleep: Initialize wakeup source locks in wakeup_source_add()

2e10f14 arm: mm: support ARCH_MMAP_RND_BITS.

829e955 mm: mmap: Add new /proc tunable for mmap_base ASLR.

749e4a1 net: fix iterating over hashtable in tcp_nuke_addr()

- enabled tracing and dynamic printk ( for me )

- updated AnyKernel2 to [MENTION=4544860]osm0sis[/MENTION] latest
[Samsung Galaxy Nexus] :
@bsmitty83

Do the M versions of the kernel have any advantages over R25v2 when used in Lollipop 5.1.x ? Would you suggest to use them or rather stick to R25v2? For now on I do not plan to upgrade to Marshmallow.
[Samsung Galaxy Nexus] bsmitty83:
Well , yes in short . lol

It's going to be newer as far as the kernel patches I apply , I'm always trying to update anything relevant , mm, fs , etc . so if you don't use the latest you might miss out on certain tunables I've added etc. But if you use a version and like it , by no means do you have to update . it's all in what you want to do and how much time you have lol .

Basically I changed to the M version for the first kernel I booted on Android 6 , but there were no necessary changes needed internally for the new OS version ( on our device only this applied I'm sure ). I am running marshmallow so I named it as such , but it still works for lollipop and that's cool too lol .

tl;dr yes , and the M kernels work for both Lp/Mm
[Samsung Galaxy Nexus] :
I flashed the M4 today but was unable to set anything in Synapse ("No UCI support detected" - same message as here). After wiping Dalvik cache it worked once but then stopped working again after next reboot. Is it a kernel problem or something wrong in Synapse? I didn't check Trickster MOD because I want to manipulate ZRAM settings and Trickster cannot do it.

At the moment I'm back on R25v2.
[Samsung Galaxy Nexus] osm0sis:
Flash my Synapse addon zip, then clear data on Synapse and reboot.
[Samsung Galaxy Nexus] bsmitty83:
umm , totally possible one of my commits are the cause , I myself have been noticing adb not being recognized , except for once untill I reboot , on my phone . I just chalked it up to Marshmallow ......

Try [MENTION=4544860]osm0sis[/MENTION] suggestion , and I'll look into a solution from my end .
[Samsung Galaxy Nexus] girkev:
500 MB zram. Real fast and up to now quite stabile and snappy. 1536 Mhz Marshmellow!!!

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] siealex:
500 M ZRAM??? How much real RAM does it take?
[Samsung Galaxy Nexus] bsmitty83:
500mb is kind of high lol . I use ~120 max
[Samsung Galaxy Nexus] girkev:
[/IMG]

Just crazy.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] bamtan2:
Try ZramCC :) https://play.google.com/store/apps/details?id=com.javilonas.zramcc.app
[Samsung Galaxy Nexus] siealex:
The builtin settings app shows all memory usage except the current app as System. WTF?
[Samsung Galaxy Nexus] girkev:
Yes indeed it was after s short while a tremendous annoying experiment.

But: zyans latest cm build runs with 250 MB zram by preset. Somehow it obvious that the bigger the better works...[emoji649] [emoji649]

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] siealex:
Did anyone try this kernel on ZMOD 5.1.1? On my phone it starts lagging terribly 10..15 hours after boot. Exactly like any older version.
[Samsung Galaxy Nexus] fivefour:
250MB of ZRAM is how much the Moto E (2nd gen) defaults to, with swappiness of 100 no less. It seems to work great but I bump the swappiness down to 85.

---------- Post added at 12:49 PM ---------- Previous post was at 12:35 PM ----------

This is a lollipop on gnex issue, all kernels do it eventually on my device. It's why I went back to the last CM nightly that was released, phone is so much smoother on kitkat.. Battery life sucks though.

I get around 10 hours of screen time on this Moto E, my Nexus will go dead in 24 hours in Airplane mode with WiFi running and the screen off the whole time (only the play store installed, no Google now). It has a relatively new OEM extended battery, I'm not sure what the problem is. I used to get around 5 hours of SOT over 4G with the stock battery, something hardware related is killing the battery now. At least it seems to be hardware as battery stats doesn't show anything abnormal.

I love my Nexus but when a $40 device has over 4x the performance and over 4x the battery life it's time to semi-retire the old girl.
[Samsung Galaxy Nexus] siealex:
LuckyK rarely does it (once a week, not more), the builtin ZMOD kernel does not slow down at all. I think this problem happens only with AnyKernel 2 kernels, very old FA builds did not lag too.
[Samsung Galaxy Nexus] osm0sis:
AK2 has nothing to do with it. Packing a ramdisk as root on a Linux box is the same as packing a ramdisk as root in recovery. If there's a common denominator that's the wrong one.
[Samsung Galaxy Nexus] siealex:
Is this bug present on Marshmallow?
[Samsung Galaxy Nexus] :
I also went back to KitKat (LS 3.2 ROM). No matter what kernel you use, Lollipop just "feels" much heavier than KK. It's not only the lack of RAM but also the CPU seems to struggle just to run the OS. For me it's especially the LP dialer which takes forever to open and initiate / answer phone calls which is extremely annoying as I have to make quick calls often. Overclocking to 1.52 GHz and disabling all animations helps a little bit but the situation is still much worse than in KK and previous versions of Android :(

No real difference in battery life here between LP and KK (3-4 h SoT using a few months old Samsung 2000 mAh extended battery). You may either have a hardware problem or the CM nightly may be just buggy.
[Samsung Galaxy Nexus] bamtan2:
I agree the dialer loads slowly. But once in memory it is fast. I suggest managing your multitasking such that your most important applications stay open and ready. ZRAM makes multitasking a bit slower, but it also allows MORE apps to multitask with. So if the phone app didn't stay open for you, ZRAM might allow it to stay. Or, if you only ran 2 apps, then an absence of ZRAM might make the already-running phone app swap faster.

In my experience of testing the latest work done for Galaxy Nexus, I can keep a few (~4?) important apps in memory on 5.1.1, and they work well. But I'm careful to not install unnecessary apps stealing background memory.
[Samsung Galaxy Nexus] :
Once in memory it opens quickly but making and receiving calls is still laggy, especially when compared to the KitKat dialer which is almost instant. The dialer app itself seems too bloated for older devices such as GNex :/

Enabling / increasing ZRAM and taking care of background apps of course helps (and I always do it) but it's just too much hassle to kill the apps manually, especially considering the fact that in Kitkat everything works smoothly without all of that (as long as your minfree values are set correctly), and you can use ZRAM there too.

I really tried to use Lollipop hard but the whole experience is just annoying due to the overall slowness of the OS. It may be acceptable for a backup phone but not for a device used as a daily driver.
[Samsung Galaxy Nexus] osm0sis:
Chrome still chokes the life out of KitKat where it didn't used to before because it's continued to grow. There are memory problems with GApps on all OS versions on older devices now. :(
[Samsung Galaxy Nexus] fivefour:
Indeed, memory consumption has gotten out of hand. It's reached and even surpassed in some cases desktop levels.
[Samsung Galaxy Nexus] :
Fortunately in case of Chrome you can just use another browser (not like with the dialer). Recently I've switched to Naked Browser completely. Even though it's just a wrapper for the built-in WebView, its UI is extremely lightweight and the overall performance is better than any other browser I've used on this phone. It also has several unique features such as text wrap and force zoom working at the same time.

As for the Google Apps, even the Google SMS Messenger app is slow despite having very limited functionality. I only flash the pico version of GApps just to have Play Services / Store and account sync up and running, and use alternatives for everything else.
[Samsung Galaxy Nexus] nikodr:
There are solutions. I use aosp browser it works perfectly for me. For sms i use textra. And everything is fast. Also dont forget to use modified kernel settings. I use nephelim settings for kernel.
[Samsung Galaxy Nexus] siealex:
I also use AOSP browser.
[Samsung Galaxy Nexus] GilGameshn1:
Hey almighty [MENTION=4544860]osm0sis[/MENTION] ... just want to say hello to you . Also I clearly see the true meaning of this great comment : brands do not want 5 year old device to be used no matter what . [emoji14] [emoji14] [emoji14]
[Samsung Galaxy Nexus] henrywhtin:
which rom is best for this kernel?
[Samsung Galaxy Nexus] Ashtrix:
Hello guys,

Sorry for a lil OT & not to hijack the thread....

I was busy lately and I was using ZF2 as primary and could'nt get a N6 good piece from amazon (3 devices I tried all of em had some or the other issue) and sticking to ZF2 for now, and I learned that the updated ddk v1.9 made to our GNEX I still have my GNEX with me, needs a new battery though the old one cycles are 90% over & I was running KK4.4 slim final but I want to upgrade the ROM now.

Could any one guide me to a stable 5.1.1 or 6.0.x if working properly, drop me a PM If there's any precious information to know and please let me know which TWRP should I use, are these LP or MM have any F2Fs support ?

Thanks in advance and I apologize for this post.. Miss my gnex with a good ROM last time I had the best exp was with that Trinity and then Mpokang and then boype later bsmitty and the progress was being made to bring updated DDK v1.9 that google failed, then I forgot my device....I regret that now as a purist. I learnt No nexus = No Android enthusiasm at all, feels empty and dull :crying:

Hoping for a helping hand, to pull me up.

Thanks again guys and MWisbest, Ziyan, bsmitty, boype and the people in this forum you are amazing thank you for everything :cowboy: .

Edit : Flashed a cm 12.1 nightly with nano OGApps with F2Fs on cache and dalvik cache EXT4 on system and yay It booted !!
[Samsung Galaxy Nexus] :
There is a problem with this kernel and Marshmallow / Xposed / Greenify. I cannot provide any logs since I had no time for further testing and I am back to KitKat now but it is easy to reproduce. Just open Greenify 2.8/2.9beta in Marshmallow and click on "+" for a list of apps. The result is instant reboot.
[Samsung Galaxy Nexus] ramosroger:
I'm no genius, but "greenify beta". It could possibly be an issue with greenify not being fully ready for marshmallow, but idk man I'm just some random guy.
[Samsung Galaxy Nexus] :
Unfortunately it happens in the stable version (2.8.1) too :( and only with this kernel.
[Samsung Galaxy Nexus] :
Another problem is that Trickster MOD doesn't work (crashes on launch).

These issues are not present in Lollipop 5.1.1 where both Greenify and Trickster work with the M4 version of the kernel.
[Samsung Galaxy Nexus] girkev:
The kernel turns the phone into a hot thing and sucks the akku very suddenly and fast.

Maguro, CM 12. How to get it more comfortably?

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] E66666666:
Same issue as [MENTION=5038522]tomasz86[/MENTION], kernel causes Trickster Mod to crash on launch and causes Kernel Adiutor to crash when selecting CPU settings. I'm on Marshmallow 6.0.1.
[Samsung Galaxy Nexus] massoudsh:
Hi [MENTION=4608636]bsmitty83[/MENTION];

Have you any plan for develop new kernel based on recently zyan kernel with about 876mb available ram?!!
[Samsung Galaxy Nexus] bsmitty83:
None at the moment
[Samsung Galaxy Nexus] EirikrHinnRauthi:
Do any recent download links happen to exist? 😊
[Samsung Galaxy Nexus] davinaizer:
Sorry man, bootloop again. :(

no PVRs
[Samsung Galaxy Nexus] bsmitty83:
Ha , OK well I'm prepared to sit here all night till we get a working cm kernel , I'll have a new build in a few
[Samsung Galaxy Nexus] bsmitty83:
heres another test kernel ,

hopefully it will boot and have sound , I believe its just a matter of a few different config options

let me know what happens
[Samsung Galaxy Nexus] davinaizer:
Unfortunately, it boots but no sound.

And the phone became very laggy. Maybe because of too much flashing after flashing?

Anyway... wiped cache and nothing...

Should we try a Factory reset?

Does a logcat helps?

EDIT: Does this mean something?

[ 01-10 22:33:16.373 154: 154 W/AudioPolicyManager ]
getOutput() could not find output for stream 3, samplingRate 0,format 0, channels 3, flags 0

[ 01-10 22:33:16.379 542: 542 E/MediaPlayer ]
error (-19, 0)
[Samsung Galaxy Nexus] cujo6801:
Smitty get out of the kitchen so you can concentrate.. :D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] bsmitty83:
Sorry this is all my fault , some how my commits related to audio didn't get included in my cm branch of my kernel source . I fixed it and will have the working kernel out shortly. Sorry man , thanks for hanging in there .
[Samsung Galaxy Nexus] davinaizer:
No need to be sorry.. Im here to help. Its the least I can do.

I should be sorry for taking your precious time in the kitchen...

People say you have good things in there.
[Samsung Galaxy Nexus] bsmitty83:
Ok as promised , Heres a kernel for CyanogenMod 12 , should work with audio now as well lol ( like anybody needs audio )

Link added to Downloads Tab

sorry again for the delay ........
[Samsung Galaxy Nexus] davinaizer:
And the winner is..........

Full_Auto_R4.5_CM-Ak.zip

Now i can watch youtube videos, make calls, listen to music, eat popcorn watching netflix... hell yeah!

Man.... I really appreciate your effort to solve this....

Edit: And you thought i didn't delete the PVR*/GPU file...
[Samsung Galaxy Nexus] bsmitty83:
no problems , now i can get back in the kitchen :p
[Samsung Galaxy Nexus] davinaizer:
LOL... go there then... you deserve it...

And take some rest...

Edit: I 'll keep testing, in case something unusual happens I'll let you know.
[Samsung Galaxy Nexus] bsmitty83:
I totally have that coffee maker ......
[Samsung Galaxy Nexus] davinaizer:
LOL... Totally...

You should get the rest of the accessories of that kitchen too... especially the one in red..
[Samsung Galaxy Nexus] Syakir Imran:
Gonna try for awhile will report later ... FML
[Samsung Galaxy Nexus] cujo6801:
Smitty has a lot of accessories in the kitchen... :D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Syakir Imran:
[MENTION=4608636]bsmitty83[/MENTION] What the best setting?? Just flashed the new kernel (FML)

Default

Governor:Adaptive

Scheduler:Sioplus
[Samsung Galaxy Nexus] Rushead:
Man, I'm in the wrong kitchen.

I wear thongs when I cook, too.
[Samsung Galaxy Nexus] rajputrajat:
Hi [MENTION=1533050]bsmitty[/MENTION],

Version 4 for fml is working great.

Thanks a lot for working so hard.

Edit:

It's running definitely running way smoother than R1. [MENTION=1533050]bsmitty[/MENTION], please say it is not placebo. :p

Same configuration as before for me.

- sioplus, RAB 512

- ondemandplus

- freq 200, 1350, 700, 200

- core iva mpu 800, 800, 800

- all other mpu voltages -75

- VAUX3_6030 2500

- VMMC 1300

Thanks to [MENTION=2853378]Nephilim[/MENTION]
[Samsung Galaxy Nexus] Rushead:
Here's my kitchen shot. Not on Cujo's level by far, but I'm sure some fetishists here will dig it.
[Samsung Galaxy Nexus] MeHR@N:
Thank you man, R4.5 works perfect.:victory::victory: I have a problem at all versions of this awsome kernel on cm12.

When the phone boots up and after that lock screen apears, if I don't unlock the screen

and screen turns off then after some seconds it will be reboot. :confused:
[ONE Q&A, Help & Troubleshooting] asp2010:
Hi,

I'm experiencing quite big idle battery drain, but not always. Sometimes by battery lasts for 3-4 days with minimal usage, but some days it goes down by up to 4% per hour with no usage. I'm sure it's not a rogue app keeping my phone awake and I've done the Google Play Services "fix" in App Ops. I'm running stable crDroid KitKat with stock kernel, and a lot of people don't seem to be having issues.

I've attached some screenshots from Wakelock Detector. It looks to me there is an insane number of wakeups for some reason. Has anyone had anything like this and managed to fix it?

Thanks.
[ONE Q&A, Help & Troubleshooting] abhi08638:
Connectivity service is probably your culprit. It's a very bad battery draining wakelock that happens when you lose network signal and It keeps your phone awake until it finds another signal. Your best option would be to try out a different modem

sent from my amazingly awesome OnePlus One with Stereo Mod

Don't forget to hit thanks!
[ONE Q&A, Help & Troubleshooting] asp2010:
Thanks for the reply.

I think you're right. I was looking at the stats today and I saw a lot of wake-ups by 'RILJ' under phone, which also suggest my issue might be modem-related. I've attached a screenshot for reference.

On a side note, it seems a bit weird how WLD shows a lot of wake-ups by SwiftKey with 'AudioMix'. I've never fully trusted that these apps show accurate stats, especially when it comes to system processes.

But anyway, I'll give a newer modem a try when I have the time and report back.

Thanks again :good: