yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] nikodr:
A 3.4 kernel would offsr many good things. Gnex is powerful but lacks 3.4. Many devices with less power outperform gnex because of 3.4 kernel they have.

Memory share would offer maybe 150 of ram
[Samsung Galaxy Nexus] christianpeso:
Which devices with less power have the 3.4 kernel? Curious.
[Samsung Galaxy Nexus] bamtan2:
Presumably all the smart watches have 3.4 or newer ;) I think Tizen uses newer.

I suspect some smart home devices, network routers, and streaming video boxes have newer kernels too.
[Samsung Galaxy Nexus] siealex:
Usually 3.10, it's the standard kernel for all modern devices.
[Samsung Galaxy Nexus] nikodr:
I think 3.4 was the kernel that was for kitkat and lollipop.

We really need this, share ram would bring back the memory reserved for ducatti. Better optimization for battery etc.bad news that texas instruments withdrew from market regarding our chipset
[Samsung Galaxy Nexus] zieruchan:
bro, I agree with you,

I don't know anyone,

as my daily driver and the only phone I have, I m always running out off memorry specially on lolipop and marshmallow.

it's different from anyone said, "free ram is waste ram",

when I'm running out off memory, android kill apps, : Whatsapp, Music, tunetalk IN THE FOREGROUND.
[Samsung Galaxy Nexus] christianpeso:
If you really use your phone, I recommend going back to a 4.3 ROM. Yeah, its 2+ years old, but it runs A LOT better than any Kit Kat or Lollipop ROM. I use my phone a lot from social media, web browsing, texting and a few calls. Multitasking on 5.0 was horrendous even with the most optimizations and 4.4 was not that much better. I came from a Note 3 and that broke so I had to go back to this device and coming back to it, that is when you realize the age and slowness of this device. You dont always have to have the latest OS just because their is one available.
[Samsung Galaxy Nexus] siealex:
Roll back to the stock kernel, all custom LP kernels have incorrect OOM behavior.
[Samsung Galaxy Nexus] JackSlaterIV:
Can you please tell me more about this?
[Samsung Galaxy Nexus] bsmitty83:
Please explain this as well . because it's simply not true . my lmk/oom does what it's supposed to do . Show me how its incorrect and I'll fix it .........
[Samsung Galaxy Nexus] siealex:
I tried LuckyK 2.5 and Full Auto r21 (or r23, i don't remember), both had problems with prioritizing tasks. Full Auto did it slightly better (but sometimes did not kill anything and caused freezes or soft reboots), LuckyK simply grouped ALL processes as Visible and killed them in a random order. The stock ZMOD kernel did it much better, but it has too high MPU voltages and does not support zRAM.
[Samsung Galaxy Nexus] nikodr:
Can i install a virtual device from android emulator and inject custom kernels?Can i eg create a galaxy nexus maguro and load somehow custom kernel?would love to start changing and learning to do stuff but would not risk under a real device.

If so how can i open the files and inject the kernel?
[Samsung Galaxy Nexus] l.capriotti:
Does the kernel support for Tap2Wake?
[Samsung Galaxy Nexus] hemantv:
Yes it does and works quite well. Though sometimes it doesn't detect touch, just sometimes.
[Samsung Galaxy Nexus] bsmitty83:
As far as I know the Android emulator that is part of the SDK is a generic ARM platform . there is no such way to emulate a specific device. If so , a developer would/could build for phones they don't even have.

If you want to mess around with a galaxy nexus as far as for development purposes , do it ! Don't be scared , the device is (imho) one of the hardest devices to hard brick . it may be difficult to restore , but there are numerous different ways to try to restore . if you backup all your important files , including your efs partition you should have nothing to worry about .
[Samsung Galaxy Nexus] nikodr:
Thank you. I was just wondering for the kernel because the one included is OMG 2.6 era. Would love to test for 3.0.x or 3.4. Thats why i asked i am trying to create a new avd that would boot with your kernel.
[Samsung Galaxy Nexus] siealex:
Why 2.6? All our kernels are 3.0.73 to 3.0.101.
[Samsung Galaxy Nexus] bsmitty83:
I think he's referring to the kernel that runs the emulator being 2.6 , he's trying to use a 3.0 kernel instead .
[Samsung Galaxy Nexus] nikodr:
Exactly that the kernels of emulator are too old. I think i found a way to start it with another kernel. Will see if it boots correctly.
[Samsung Galaxy Nexus] l.capriotti:
I need directions on how to enable it then, I used "kernel adiutor" to enable "Tap2Wake" but it still does not work.
[Samsung Galaxy Nexus] hemantv:
You just have to enable it from any kernel control app. I used TricksterMOD. And make sure you disable the time delay for tap2wake as it doesn't seem to work.
[Samsung Galaxy Nexus] l.capriotti:
there must be something else as I did the same but still I cant wake the device by tapping. Thanks anyway.
[Samsung Galaxy Nexus] osm0sis:
Flash my Synapse injector addon from 2 pages back over R25, then install Synapse from the Play Store. T2W is in the Misc tab and works great, including the timeout. Read the control's description so you understand how to use the timeout correctly.
[Samsung Galaxy Nexus] l.capriotti:
I must be doing something really wrong as my phone does not want to wake up with knocks even with that...

I'm running Full_Auto_R25v2_Ak2 with ZMoD-20150906-maguro.

Never mind, thanks anyway
[Samsung Galaxy Nexus] bamtan2:
I find tap-to-wake works better now. But it's still inconsistent, so for regular use I've left it turned off.

Is R25 stable for everyone? I've had some hard crashes and hot lockups where the CPU tries to cook itself. Not sure it's the kernel though.
[Samsung Galaxy Nexus] handofdark:
i have to agree with you. im not expert in these matters but i do get better multi tasking on stock kernel. lucky kernel was very good at old versions but it seems the more features are added to these kernels the slower they get
[Samsung Galaxy Nexus] christianpeso:
[MENTION=4608636]bsmitty83[/MENTION]

Decided to hop back into Lollipop land after a couple months of using 4.3.

Anyway, I used to use your kernel and it was the only one that ran at 1.6ghz without freezing. I also see that [MENTION=2633638]Ziyan[/MENTION] has modded the BFQ scheduler to allow some improvement to our devices. [MENTION=3265822]Musical[/MENTION]_Chairs has implemented it into his Toro ROM kernel. Is it possible for you to implement the modded version of the BFQ scheduler into your kernel? Would love to try a combo of 1.6ghz and that BFQ scheduler.
[Samsung Galaxy Nexus] siealex:
Can you take a video of opening some apps, e. g. browser, Gmail and Youtube and switching between them? On my phone opening the stock browser or Gmail takes 30 to 60 seconds with this kernel and 5 to 10 seconds with stock one.
[Samsung Galaxy Nexus] ASHURiCAN:
Go for stock then, what do you want else? Stock is delivering the best usability.
[Samsung Galaxy Nexus] siealex:
I can't understand why some people have no lags on EXACTLY the same ROM and kernel. Often they also have 20 to 100 times faster random write speeds.

PS, ASHURiCAN, can you install Androbench (find it on Google Play) and run all tests (or only linear write and random write) on default settings? I get 30..35 IOPS on random write and other people get 400..800 IOPS.
[Samsung Galaxy Nexus] bsmitty83:
https://youtu.be/0nJLeqDdc7U

i took that off a restored backup .

Obviously it will help alot if you overclock this kernel .

For me , I have great multitasking. I'm very happy how the device runs at such an old age now.

PS mute the video , unless you like commercials on a TV in the background lol
[Samsung Galaxy Nexus] siealex:
It's very strange... these actions on my phone will take at least 10 minutes. Can you post all your Trickster settings?

PS, do you have Xposed on your phone?
[Samsung Galaxy Nexus] nikodr:
I overclock phone to 1.65. Max screen off 550 min screen on 350.

Sioplus and Westwood. Gpu 512 on demand. Fsync on.

Minfree from top to bottom

50 70 116 130 165 370

Zram on. Core ipa and mpu from 830 i lower to 810.

Vaux3_6030 3100 and vmmc 1800. These are settings of nephelim . Along with greenify installed. I never ever have lag.
[Samsung Galaxy Nexus] siealex:
I'll try these ones tomorrow.

Do you clear dalvik cache after changing kernels?
[Samsung Galaxy Nexus] nikodr:
Yes i always do. I clear cache and dalvik cache. Just to be safe.
[Samsung Galaxy Nexus] osm0sis:
Haha actually that ribs/chicken commercial is amazing and hilarious in the background. :laugh:
[Samsung Galaxy Nexus] nachiket_xda:
Are you human? :confused: ........... but but I thought you're a Simpson :D
[Samsung Galaxy Nexus] ASHURiCAN:
I have worse results than yours :( Latest CM12.1 original kernel, Xposed with 6 modules, and 87 user apps.

Seriously? I don't want to rely on this benchmark! I really don't like it and will delete it forever! [emoji13]
[Samsung Galaxy Nexus] siealex:
They are almost the same as mine. I tried a different benchmark and it showed almost the same speeds. Do you have lags?

PS, remove Xposed (or reflash your ROM without it) and try again. I think it's Xposed related.
[Samsung Galaxy Nexus] ASHURiCAN:
I go up 15000 on Antutu and that's what makes me feel good [emoji16]
[Samsung Galaxy Nexus] Punkiderma:
After a long time trying to understand that, I think that the problem is all in the apps you're using.

I installed Osmonitor like someone said in another topic, and checked for all the process running. Then, I removed everything I could (some dashclock extensions and things like that) in order to reduce ram usage.

Since I have a battery without NFC antenna, I even removed the NFC apk from the system folder in order to prevent it from running and save like 40 mb more of ram.

Finally, after a long time using evolvesms, I switched back to default Sms app.

My phone always worked by phases: sometimes very fast, sometimes impossibly slow. After this fine tuning work, it is ALWAYS fast, and it would be even more if I could use f2fs (damned whatsapp deleting my messages if I use this instead of ext4).

All of this, on Kit Kat, wich I personally think is the last good version for this phone, at least without 3.4 kernel. I think would be wonderful to have ddk 1.9 on Kit Kat, it would be the perfect android for the gnex IMHO.
[Samsung Galaxy Nexus] siealex:
But why the stock ZMOD kernel is always much faster?
[Samsung Galaxy Nexus] Fatsodonkey:
BSmitty could you please consider making DirtyV SR kernel for zzpianomans cm12.1?

That would be awesome. I tried it the old kernel for lolz and damn it was pretty snappy. LMK settings in synapse were missing though. :D

Please just one version. I have always used DirtyV´s SR version and it has been awesome.
[Samsung Galaxy Nexus] bsmitty83:
I've actually thought about it a few times . i will try to update it when I get some time .

I really would like to make an anykernel2 package with all the necessary libs and other things needed to use the new ddk . that way it would be good for all 4.4 Roms regardless of what graphic driver version it was compiled with. Not sure if I could do it , but I still might give it a shot.
[Samsung Galaxy Nexus] Fatsodonkey:
Thanks for the quick answer. :) U r Auwesome.
[Samsung Galaxy Nexus] :
That's too low.

I manage to get more than 20,000 in Antutu using this kernel with tweaked Nephilim settings.
[Samsung Galaxy Nexus] Punkiderma:
So this would bring the new ddk to every rom or would just make possible to use your new kernel also with roms that have the old ddk? :)
[Samsung Galaxy Nexus] h4xx0rr:
I never got 20k, which rom are you using?
[Samsung Galaxy Nexus] :
I'm using Chroma ROM.

I haven't really tested other Lollipop ROMs (except for SlimLP which was very laggy) so can't really compare with them. The ROM seems very fast though so I don't plan to change it. This phone is my daily driver and I need it stable.

What's important is that the 20500 score is only possible with FSYNC turned off. It will be 19000 with FSYNC on. I use slightly modified Nephilim settings except for the governor which I set to zeneractive.
[Samsung Galaxy Nexus] l.capriotti:
how much free memory you have on average?
[Samsung Galaxy Nexus] siealex:
bsmitty83

Are the default Core and IVA voltages on this kernel exactly the same as on stock? On 4.4 ROMs my phone starts lagging very much if I decrease any of them by 20 mV or more. Can this be the cause of lags on FA?
[Samsung Galaxy Nexus] nikodr:
I always decrease them by 20 on all roms. Its ok
[Samsung Galaxy Nexus] :
It's difficult to tell as with this kernel all apps show 0.0 bytes memory use. I don't really check memory usage too much as long as the ROM performs fine.

What I indeed have observed is that minfree settings are very kernel dependent. I tried to use Nephilim settings with LuckyK kernel which resulted in constant killing and restarting different processes. On the other hand, no such problem occurs with this kernel.

You need to experiment yourself. I personally do not like CM and prefer to use lighter AOSP based ROMs, especially on older devices.
[Samsung Galaxy Nexus] siealex:
It's a critical bug that prevents this kernel from killing processes correctly.
[Samsung Galaxy Nexus] bsmitty83:
Iva voltages are stock , core volts are dropped based on Fransisco Franco's volts .

Stock core voltages are :

For opp_50 = 962

For opp_100 = 1127

For opp_100_ov = 1250
[Samsung Galaxy Nexus] siealex:
I'll try them tomorrow, thanks.
[Samsung Galaxy Nexus] siealex:
Trying R25 with these voltages and Neph's OOM settings...
[Samsung Galaxy Nexus] bsmitty83:
So your mad cause the calendar app got killed ? Because that's the only app I see that was . if your concerned with the strange ram reporting, toggling zram seems to fix it . but I haven't found a reason why the apps report 0 ram used , I'm going to try to figure that out.

But I don't think it has anything to do with lmk or apps being killed . apps are killed correctly in lowmem situations . show me your proof that it isn't ....once again .......because I've checked and checked .

Bottom line is that this is my kernel . for my own use . I'll fix whatever problem I deem to be a problem and I have absolutely no commitment to you or anyone for fix it dates . you don't like it download the source and compile it yourself . maybe you'll learn a thing or two instead of coming off as tirelessly ungrateful and a whiner .
[Samsung Galaxy Nexus] siealex:
I run Foreca Weather, it runs MinMinGuard service and both apps are immediately killed, but the launcher continues running. This is certainly incorrect and never happens on the stock kernel.

PS, can I increase ZRAM size to 100 M?

---------- Post added at 04:04 AM ---------- Previous post was at 03:56 AM ----------

Even if the kernel always reports negative free RAM value?
[Samsung Galaxy Nexus] siealex:
Today my phone started lagging again. Booting system takes up to 15 minutes. I'm back on stock kernel without any lags...
[Samsung Galaxy Nexus] akhi24nick:
Hey I suppose its well established in XDA that if XYZ Rom/Kernel doesnt go well with your device or it doesn't have a feature that you want and ABC Rom/Kernel has it, you can go ahead and use ABC instead of posting non productive comments. (This one included)

There are only few developers for the GNexus please dont shoo them away.
[Samsung Galaxy Nexus] nikodr:
Fenix46 mentioned something on his kernel thread regarding shared dma buffer and total 845 mbytes of free ram. If that is the case then we won't need a 3.4 kernel for more ram.exciting things are coming i think for kernel develioment :))
[Samsung Galaxy Nexus] massoudsh:
hi [MENTION=4608636]bsmitty83[/MENTION], have you any plan for update this kernel for android6?!!
[Samsung Galaxy Nexus] siealex:
Our phone cannot run Android 6. Period.
[Samsung Galaxy Nexus] pvkiniyan95:
[MENTION=4608636]bsmitty83[/MENTION] its a bit off topic...i was a galaxy nexus user until it fried, now i own a Lenovo K3 note for which they released a 5.0.2 kernel source code. Could u please point me to a tutorial where i can make it boot with 5.1 like u guys are booting 5.1.1 with old source code.
[Samsung Galaxy Nexus] hemantv:
As Lenovo K3 Note is a MediaTek device, I'd suggest you to check out this thread. Devices based on MediaTek chipset are not quite development friendly. They don't have enough or proper sources to get a completely working rom.
[Samsung Galaxy Nexus] pvkiniyan95:
i m just entering into the kerenel developing area so I just wanted to know how could i possibly create a kernel that could boot with 5.1 with older sourced...forget that i even mentioned K3 note...i just wanted to get the basic picture how kernel developiong works...i previously compiled kernel in linux but that is nothing coz pkgbuild takes care of everything and i use xconfig to edit the kernel...:D

So what should i do to boot a 5.1 with older source code...what should i look for and where?
[Samsung Galaxy Nexus] eternal70:
I think you should also learn about the language too. Yeah, C or java. I myself start developing kernel only by cherry picking commits from other devs [emoji14]

In my thoughts it's quite hard to make old kernel source to work with newer android version. I remember back in early gnex kitkat days when some devs are dealing with screen glitches. Without updated source and libs i guess it will be hard except you really know how to debug and fix things.

Correct me if i'm wrong, someone [emoji5]
[Samsung Galaxy Nexus] pvkiniyan95:
i compiled from the source without any change and being arm64 i only got Image, Image.gz and image.gz-dtb but no zImage to pack it...if somebody know can u clarify what should be used as zImage and to top it of the initrd.img provided with the boot.img of the original android that came is not in gzip or lz...

I know these are offtopic but bear with me as this is the only thread i know that has wise people who can put up with off topics.
[Samsung Galaxy Nexus] ghost010:
Running 6.0 just fine.. With 23mb free ram.
[Samsung Galaxy Nexus] hemantv:
Was it supposed to be a positive comment?! How is 23 MB free ram enough to run any rom fine? My device running 5.1 still lags even after having ~150 MB free ram.
[Samsung Galaxy Nexus] siealex:
Where do you check free RAM, in Trickster (or any similar app) or in system settings?
[Samsung Galaxy Nexus] ghost010:
Because you don't need free ram to run any thing. Free ram is unused ram, you don't use it. The rest of the ram is in use and running the system. Maybe run proper ROM? I'm now running 5.1.1 with 178 mb free ram, no lag. And not using this kernel.

Your statement that our device can't run 6.0 is just false.

---------- Post added at 03:32 PM ---------- Previous post was at 03:31 PM ----------

Just the in system settings. And I do double check it.
[Samsung Galaxy Nexus] hemantv:
Yea, it might be enough for rom but how many apps will you be able to run simultaneously? And I never denied that our device will be able to run 6.0, the thing is will it be able to run it efficiently? I guess the answer is no. I'd be really happy if we could. :)
[Samsung Galaxy Nexus] ghost010:
You kinda did. But that's beside the point. Going gapp less or choosing the smallest gapp package helps allot. The play service alone almost takes 100 to 200 mb ram. I also wonder what exactly happens to our 1GB ram. Biggest cut I got out of it is 760mb with this kernel.

I'm now running slim gappless and I'll see how it go's. Though even with gapp I have the same amount of free ram on 5.1.1. But system ram usage gets bigger with gap compared to gappless. Have not tryd the cm version yet and the last stable ROM I had was 4.3 paranoid
[Samsung Galaxy Nexus] siealex:
Sometimes even 240..280 M, especially when using Google Maps or similar apps.
[Samsung Galaxy Nexus] bsmitty83:
Op updated with M1 ,

I updated R25 with a few arm patches , but functionally it should be about the same as R25 .

Additionally I removed zram being enabled in the bootscript . if you wish to use it , which I do , you have to set it manually via an app or terminal .

Running saosp at the moment . runs about as well as lp but that's for yourself to determine.

Happy new year to all .
[Samsung Galaxy Nexus] siealex:
100% load at 1520 MHz and 96*F???
[Samsung Galaxy Nexus] bsmitty83:
And ?? Why are you worried about MY load ? Do you want my load ??

Is the battery supposed to be hot ? I don't understand your questions as usual......
[Samsung Galaxy Nexus] nikodr:
Btsmitty83 thank you.i have been using your kernel r22 for more i can remember. Question would it work sometime in the future with shared ram rhat fenix46 introduced in his kernel?

For Android 6.0 we need all ram we can have
[Samsung Galaxy Nexus] siealex:
Is it battery or CPU temperature?
[Samsung Galaxy Nexus] bsmitty83:
Battery , what you saw was a brief second in the snapshot since its a real-time update widget . The CPU load never stays at 99 percent for long , and if it is for longer than say a few min , it will heat up of course.
[Samsung Galaxy Nexus] bamtan2:
Brilliant :) I'm glad to hear android 6.0.1 is working well for you :) As usual, the community at large is working hard to mature AOSP 6... and we may take it for granted, but we shouldn't!
[Samsung Galaxy Nexus] rohitchouhan07:
thanks smitty I was waiting for it ....
[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