yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Nephilim:
I'm already rooted with twrp installed, I enjoy stock lollipop so much I just stuck with 5.1.1, is there a factory image I can just use to update to the M preview without having to wipe everything I just set up? Haven't had a chance to checkout the N6 community on here yet.
[Samsung Galaxy Nexus] bsmitty83:
No not really , but the n6 will set all your stuff back up due to the working backup feature. All you'll lose is text messages not on hangouts
[Samsung Galaxy Nexus] nikodr:
Is it possible to reclaim more ram without kernel 3.4? Right now we have 760 mbytes on r21.is there way tp have more?
[Samsung Galaxy Nexus] bsmitty83:
798.1mb seems to be the limit as I see it . 1080 playback breaks , 720 seems OK .
[Samsung Galaxy Nexus] eternal70:
Cool! Can you release that as Bigmem version like DirtyV in KK?
[Samsung Galaxy Nexus] Nephilim:
Hey Smitty, what kernel are you using on N6? Upon recommendation, I'm using BenzoCore and it seems pretty solid.

Also, when are you going to get a kernel going for N6? (Take into the consideration that not building one isn't an option lol)
[Samsung Galaxy Nexus] bsmitty83:
Been running my own for the Dev preview , I've built some personal kernels , nothing posted here tho . I'll whip something up at some point I'm sure . elementalX has always been my backup kernel fwiw .
[Samsung Galaxy Nexus] Nephilim:
Well now that I'm in the N6 game, feel free to PM me some of your semi-stable personal builds to play around with anytime you like. Gotta get me some DirtyV/Full_Auto action on this new toy. ;)
[Samsung Galaxy Nexus] bsmitty83:
Honestly, I built that just to see how much ram you can pull from the 2d tiler . I will mess around with it some more and maybe have it as an option . fwiw it made no noticeable difference in terms of system performance when I ran it for a bit .
[Samsung Galaxy Nexus] Nephilim:
I feel like we've already had the discussion of bigmem being useless due to Android being able to properly allocate ram on its own. It would be wiser to adjust minfrees to improve performance and leave memory alone. Unused memory isn't always a good thing. Just my 2 cents.
[Samsung Galaxy Nexus] nikodr:
I have always been using your minfree settings on lollipop roms and i am more than happy. I think the more ram we have the better for the system. If i only have 120 mbytes to allocate for the browser it would not be the same as if i had 150 mbytes for the same browser? What i want to say is that if minfree settings are optimised for the bigmem version i suppose we would have less lag and more speed. Also i would really like to see the benefits of 3.4 kernel for gnex. I think it is the only think that will make the phone get more life. 3.0.x is not going to help maguro survive.
[Samsung Galaxy Nexus] Nephilim:
Trust me, coming from someone that has tweaked everything he can on the Gnex, nothing you do will fix the browser. I've tried it all. Gnex, sadly, is just slow at this point in its life cycle
[Samsung Galaxy Nexus] nikodr:
So unless a 3.4 kernel comes there is no way for better speed.

Have you used android m on n6? Is it brtter than lollipop?
[Samsung Galaxy Nexus] Nephilim:
Haven't tried out M yet, I'm loving stock lollipop 5.1.1 right now. Also, I heard the app drawer looks a bit retarded with vertical scrolling rather than horizontal.
[Samsung Galaxy Nexus] bsmitty83:
It was messed up in the 1st preview , but they fixed it for the 2nd release . I think it's dope , love the most used app bar on the top too .
[Samsung Galaxy Nexus] nikodr:
Are the kernel gurus here ready for the transition to 3.4? What is happening and the kernel in the 3.4 thread does not start after the google logo? Reason i am posting here is that this kernel is alive and most probably the first that in future could bring 3.4 to us
[Samsung Galaxy Nexus] bsmitty83:
I highly doubt I would be the one to get a working 3.4 kernel first . [MENTION=2633638]Ziyan[/MENTION] is about the only one left that has a gnex and the skill to get it to boot .

Once someone gets a working kernel out , I can definitely work on making a custom version .
[Samsung Galaxy Nexus] Nephilim:
So, off-topic since it's my N6 but I find it quite humorous, especially since I have my device underclocked and undervolted and still get this score. :silly:

​
[Samsung Galaxy Nexus] nikodr:
[MENTION=2633638]Ziyan[/MENTION] we really need your help. I saw your work on 3.4 kernel for nexus 7. Would it be possible to assist in the 3.4 kernel for maguro? All kernels including this one could really bring new life to our old phone. What is missing from the kernel and it does show nothing after the google logo? If it can work on nexus 7 then i think that it could too on our omap phone :)
[Samsung Galaxy Nexus] Syakir Imran:
Guys any new setting for this kernel?? (Trickster mod)

I still use the old one by Nephilim but the new version of kernel got some changes
[Samsung Galaxy Nexus] Nephilim:
I have been busy playing with my N6 lately but I'll fire up the Gnex and check it out sometime this week if I have the time. :)
[Samsung Galaxy Nexus] Syakir Imran:
Ok love you ??
[Samsung Galaxy Nexus] Fatsodonkey:
Does this kernel work with 5.1 roms?

Also is there a sr version of this kernel?

Can someone recommend me a good rom with theming support that works with this kernel.

Im so used to cm12.1 but i tried ziyans build with this kernel and i had no 3d. Asohalt 8 textures were black.
[Samsung Galaxy Nexus] siealex:
Does this kernel support init.d scripts?
[Samsung Galaxy Nexus] bsmitty83:
yes
[Samsung Galaxy Nexus] Nephilim:
Does this kernel support the developer porting it to Nexus 6? Cause I support that.
[Samsung Galaxy Nexus] pattyboi:):
no offense,but constantly nagging about 3.4 isnt going to push it any farther.
[Samsung Galaxy Nexus] nikodr:
Partyboi you are correxct. However on another thread ziyan said that he plans to start 3.4 kernel for maguro from bare minimal working adb and usb and fix display :)
[Samsung Galaxy Nexus] CoDe LaZaRuS:
[MENTION=4608636]bsmitty83[/MENTION] does your unofficial fml rom have Full auto kernel baked in?
[Samsung Galaxy Nexus] bsmitty83:
It does , but its an older version than current , so you might want to flash the latest afterwords .
[Samsung Galaxy Nexus] christianpeso:
Out of curiosity, anything new in the works?
[Samsung Galaxy Nexus] bsmitty83:
Yes , my gnex is still alive . I haven't really had much time to do anything though. Hopefully sometime this week or next I can update the kernel .
[Samsung Galaxy Nexus] christianpeso:
Great! Went back and was running a Liquid Smooth Kit Kat build for the last few weeks as it ran a lot better for me when compared to LP ROMS. Was using your latest Kit Kat kernel on that, I believe R61. Ran great.

Wanted to get back into the LP scene and MusicalChairs just released a new build of his CM12.1 ROM with latest DDK 1.9 driver. Flashed your latest R21 on that and combined that with some other tweaks and this phone feels great again! Thanks!

Not sure how much you can do to make this kernel better, but I am not a kernel dev so what do I know:p:p

Look forward to whatever you release!
[Samsung Galaxy Nexus] bsmitty83:
I uploaded R22 in the Devdb Downloads , a minor update

- I updated Synapse to the latest thanks to [MENTION=4544860]osm0sis[/MENTION] , included in the .zip are my personal FA_bootscript and fstab . You can replace the orignal ones with my personals , and remove personal from the filenames to boot with my personal settings

(always a WIP, currently I am using the DEFAULT script and fstab )

- Updates to LMK , zram , vmscan

Enjoy and hope it works well for you :good:
[Samsung Galaxy Nexus] bamtan2:
I've been running the May 21 2015 build of Full Auto (R19) since release and it has worked fine for me. At times I've enabled zRAM and it seemed to work fine. I've run at 1500mhz and it also seems fine. So that is my last testing milestone before I upgrade to this latest build.

I will also be upgrading to ZMOD with the security fix when it is released, which will be a major change from my months-old release. To reduce chance of confusing problems together, I will use your new kernel for at least 2 weeks from today, before changing anything else or upgrading to ZMOD. Fingers crossed ;)

Thanks for your work!
[Samsung Galaxy Nexus] BestBrd:
Hi btsmitty,i want to ask you if you can include a feature on your kernel...The opportunity to control The agc(mic automatic gain control),that makes registrations very bad! Can you look into it?is it possible?
[Samsung Galaxy Nexus] bsmitty83:
I'm not sure there is such a thing for the gnex . that sounds like a Qualcomm feature, like for example fauxsound .
[Samsung Galaxy Nexus] massoudsh:
[MENTION=4608636]bsmitty83[/MENTION]; HW decoder (with mx player pro) broken in r22, can you fix that?! Thanks you.
[Samsung Galaxy Nexus] bamtan2:
So far so good.

While at 1500mhz I noticed some system restarts, so I went down to 1300mhz. I have not tested further to isolate whether this is because of the kernel or something else.

While changing ZRAM settings around I was able to get the swap space stuck at one max value (above 250mb) and it wouldn't utilize well (like 30mb used). A few times after restarting it would just sit there booting but not finishing. Pulling the battery fixed that. I've left ZRAM at 192mb and 100% swappiness and it seems to work fine. ZRAM utilization for me right now is 91MB (40% of 192MB), with 77MB original data size and 23MB compressed size. I look at this in the app ZramCC.

I have tweaked my LMK minfree down to 50mb for foreground and 90mb for the rest except for empty apps, which is set to max. I set them the same because the OOM priorities of each process seem sufficient without further prioritizing by type, and I'm a rebel. I look at this in the app Auto Memory Manager

When combined with the ZRAM settings above, in 5.1.1 zmod rom I'm now keeping 4 regular 30MB-80MB applications open at once, plus 1 huge firefox browser instance worth 150MB+. I look at this in the app OS Monitor.

My changed settings from default, using the Synapse app are:

CPU max 1350mhz
CPU mins 350mhz
Thermal throttle 70C

hispeed freq 920000

content adaptive brightness
color levels: -10 green, +10 blue

Swappiness 100%
ZRAM disk size 192MB

LMK: 50, 90, 90, 90, 90, 250

Final note: Because [MENTION=2633638]Ziyan[/MENTION] is experimenting with lowram mode in the cm12.1 thread, I added ro.config.low_ram and persist.sys.force_highendgfx (both set to true) to my zmod rom build prop (using kernel adiutor app as editor) and everything seems to be fine. I did not add the other settings he was looking at because I didn't understand them (or think they'd help.)

Thanks for keeping the kernel up-to-date and working well! :)

Edit Update #1: Synapse doesn't seem to restore the "content adaptive brightness setting". Maybe a Synapse bug? Also, I tried LZ4 for ZRAM, and it either crashes the system or doesn't work. Good thing LZO is sufficient!
[Samsung Galaxy Nexus] BestBrd:
Agc is something included from android 2.2+...i don't know if is it possibile to disable it with some kernel tweaks(when i go home i'll link some posts) or it's something ROM related,i only know that causes audio distorcion during recordings(if you record a concert or something like that with loud volume)
[Samsung Galaxy Nexus] musical_chairs:
Or use an app like RecForge that allows you to manually control the mic gain.
[Samsung Galaxy Nexus] djkk16:
Mate does this kernel have t2w or s2w support ? Looking for a lollipop kernel with support
[Samsung Galaxy Nexus] bsmitty83:
No , I haven't gotten to add t2w , as its the only option right now. Slide to wake is still a ways off from me . I can at least add touch to wake for those who wish to use it . I was going to try to get a new version out soon anyhow , since most of roms are selinux enforcing now , I will eliminate the permissive setting on the kernel command line . so whatever the ROM has selinux set , the kernel won't change it .

I've also been messing around with backporting powersuspend and eliminating early suspend / late resume . but its not gonna be easy for me . it will be a good side project .

Maybe later tonight I can get a new kernel built .
[Samsung Galaxy Nexus] siealex:
Thermal throttle 70*? My phone starts throttling even at stock 1200 MHZ with this setting.

192 MB ZRAM and 250 LMK for empty apps? Do you have any empty processes ever?
[Samsung Galaxy Nexus] bamtan2:
It will throttle at almost any setting (maybe not 350mhz max?), so the point isn't to stop throttling. :) Raising the max speed to 1350mhz will do small bursts or work faster until it throttles (which will happen faster too, because 1350mhz is less power efficient).

I raised the throttle temperature because I believe hardware manufacturers constrain this number to make users feel comfortable. Normal people don't like the feel of hot phones. They don't expect it. However, I think the hardware can support higher temperatures. So I made a modest increase. Modest due to my lack of knowledge about how far the hardware can go.

In my experience, on 5.1.1 there is not enough memory for empty apps to stay open, even with default LMK settings. There is not even enough memory for multiple running apps to stay open.

ZRAM further burns more power because the CPU is constantly working extra to compress and decompress memory pages. In theory, with 5.1.1 this is worth it for me, because I can barely keep 3 apps open at once, so memory is my #1 constraint on usage, NOT CPU or battery life.

PS: I have had some crashes with R22, but I have not had enough time testing to know if the cause is R22, or a feature I enabled (like ZRAM), or if it was just a bad app.
[Samsung Galaxy Nexus] siealex:
How much does your phone drain its battery at rest? My GN started draining 10..15% per hour (independent of kernels, 3G on) and I can't find any causes.
[Samsung Galaxy Nexus] sergialess:
Check Wakeup Time, Screen on Time, wakelocks, partial wakelocks, alarms and processes using BetterBatteryStats app.

Probably Google Play Services will be causing a lot of wakeups.
[Samsung Galaxy Nexus] siealex:
15..20% active mode at 224 (or 250) MHz (I set this limit manually in trickster), no screen on at all. Can this drain 10% per hour? I'll try with stock ZMOD kernel.
[Samsung Galaxy Nexus] sergialess:
For me it doesn't mind at all what freq the CPU is running. You must look for apps or services keeping the device awake even with the screen off.

I use Xposed+Amplify to keep some wakelocks under control. But hey... I'm taking about KK, not LP. Hope you find the reason.
[Samsung Galaxy Nexus] siealex:
It's strange... on the stock kernel I have currently 1% in an hour... I'll try several hours more...
[Samsung Galaxy Nexus] bsmitty83:
Op updated with R23 , nothing major

- Removed selinux permissive setting from kernel command line , the ROM will set selinux now.

- updated interactive governor

- changed zswap compression from lz4 to lzo , I still need to work on lz4 . Also I changed the permissions for 2 of the 3 zswap tunables to R/O (444) , it seems the zswap code is still being worked on and for now enable/disable , and compressor choice is hardcoded at boot .

- Added Touch to Wake support

Enjoy , hope it works for all .....

Edit ,,, I forgot to add t2w , I'll add it and reupload shortly --DONE
[Samsung Galaxy Nexus] Fenvarien:
Awesome, thanks for the new kernel release! :good: :)
[Samsung Galaxy Nexus] nikodr:
- Added Touch to Wake support

could you tell us how is it used?and what about battery usage?

Thank you for your new release :)
[Samsung Galaxy Nexus] bsmitty83:
you can use trickstermod app to set it , or the parameters are under /sys/class/misc/touchwake/

for touchwake enabled

echo 1 > /sys/class/misc/touchwake/ enabled

for setting delay tlll active ( in seconds )

echo "n" > /sys/class/misc/touchwake/delay

no idea about battery , as I dont use touchwake, I imagine that it would keep the phone out of deep sleep , but running at a low (250mhz) freq instead isnt too bad of a tradeoff if your power button is shoddy
[Samsung Galaxy Nexus] novincobra:
Why everytime i use this kernel v22/23 on ZMod 6/17 always get random reboot and screen so hard to wake sometimes . I just set kernel setting cpu max 1350 min 350/550, gpu 384, audio boost +1 and mycolor calibration setting.
[Samsung Galaxy Nexus] osm0sis:
Adding this to Synapse but haven't unpacked my GN after my move yet to test. ;)

I found:

"/sys/class/misc/touchwake/delay

time to keep the touch controls awake after screen off (default 45000ms, 0 = indefinitely)"

Is this still accurate for the version you implemented? Is delay in ms like the quote, or s as you say?
[Samsung Galaxy Nexus] bsmitty83:
I'm not sure , I'll fire up the laptop in a few , got some time today. The parameter I was talking about is a delay for how long the screen is off before the touchwake becomes active . I think your looking at a different parameter . but I'll figure it out soon . got to wake up and get some vaping in lol .

Edit :

I think your right as usual [emoji41] , I believe it is set in milliseconds . if you set it from trickstermod its converted to seconds . from a terminal or such , its in milliseconds.
[Samsung Galaxy Nexus] bsmitty83:
The slow screen wake is probably from a low screen off freq . I use 1ghz for my screen off max . if your phone needs to do something while the screen is off , it should have a decent cpu freq to use , otherwise the rest of the time it will be in deep sleep anyways.

For the random reboots ......

"adb shell "

"cat/proc/last_kmsg"

And post the file here or wherever I can access it .

Without that info I really don't have a clue . at least there is a chance with the kmesg . most logcat apps or bugreport apps have the ability to pull the kmsg with the press of a button .
[Samsung Galaxy Nexus] zieruchan:
Bro, I flash your kernel because I'm interested with 'touch wake' feature, but I got too much lags when multitasking.

nothing changed from trickstermod except touchwake enabled, so I think there is something wrong with LMK on your kernel

btw nice job :good:
[Samsung Galaxy Nexus] bamtan2:
I flashed to try touchwake. It works, but unpredictably. I'm not sure how it works. Sometimes a touch wakes it up, sometimes only a swipe wakes it up. Sometimes nothing wakes it up, and then a few seconds later it wakes up. I did set the screen-off maximum CPU clock speed to 1200mhz to test. (Maybe the minimum needs to be higher too?)

I have not noticed any performance differences with this kernel version compared to the previous version.
[Samsung Galaxy Nexus] siealex:
Compare it with e. g. stock ZMOD or CM kernel (or even with LuckyK) and you will see that this kernel is considerably slower, sometimes up to 5..10 times.
[Samsung Galaxy Nexus] bamtan2:
Slower at what? I'm running programs and switching between them at what seems like normal speed to me. Does it benchmark slower in Antutu?
[Samsung Galaxy Nexus] siealex:
No, not in Antutu, but ONLY at starting programs or switching tasks. E. g., sometimes starting Camera from the lock screen takes 30 to 60 seconds, with the stock ZMOD kernel it takes 5..7 seconds.
[Samsung Galaxy Nexus] zieruchan:
are you sure running this kernel with galaxy nexus ?:confused:
[Samsung Galaxy Nexus] PythonNut:
I see this. It's caused by some sort of memory bloating. On CM, LuckyK, the "System" RAM usage is about 3-400MB. On CM, Full Auto, System RAM usage after a fresh boot is nearly 600MB, strangling multitasking.

This showed up sometime around r20~r21, if I remember correctly.
[Samsung Galaxy Nexus] PainFly23:
I don't know if anybody has brought this up before, but I wasn't able to get a cell connection at all when I flashed the latest version. I haven't been following this kernel recently so I don't know when this problem would have cropped up. Basically, I'm on Sprint and using CM right now and I get the no sim icon in the status bar with this kernel installed. Flashing the stock kernel image fixes the problem and I'm able to connect to cell service again.

It's not a big deal for me since I use my Gnex as a wifi only device (I turn off airplane mode only for things like updating the time or removing the no sim icon), but it's something you might want to look into if others are experiencing the same thing.
[Samsung Galaxy Nexus] bamtan2:
I can have 2-4 apps open at once with latest ZMOD and FullAuto. I can task switch between those apps basically instantly. So I don't find the CPU or RAM *speed* to be holding us back. If I had a lot of apps installed and hogging our limited RAM *size*, then I would definitely have a problem. :) Running the camera from lock screen takes me about 3 seconds.

I have not noticed any new change in RAM demands. For me 5.1 has always had very limited RAM because of the known kernel problem where RAM is reserved unnecessarily.

I have noticed that system crashes or soft resets have caused the "no sim card" error. Only turning the phone off and on would fix that for me. It is rare for me to get this.
[Samsung Galaxy Nexus] CoDe LaZaRuS:
Guys for those of you getting awesome usage with the kernel tell me your kernel setting :)
[Samsung Galaxy Nexus] bamtan2:
Honestly the #1 performance constraint in 5.1 is free RAM. This can be helped a LITTLE bit by kernel settings.

ZRAM uses CPU cycles to get compressed swap space. This means you get a little "RAM" and lose "some" battery life. This one is buggy and still in development, but it can work.

Minfree LMK settings can change how well the device performs, but the way the system interacts with these settings is VERY complicated "behind the scenes". How well these settings work depends on how your apps work, and how you want the phone to work. And with only ~300MB free maximum, and some apps that use 150-300MB at a time, it is possible there are times when the minfree lmk settings don't matter at all.

Limiting the maximum number of open apps can help you manually manage the system better. Google apparently endorses this in their "ro.config.low_ram" setting. Basically (and whether it is MAX_HIDDEN_APPS or ro.sys.fw.bg_apps_limit or what, I don't know), this limits what you can do with the device. It doesn't help performance, it just helps you be less disappointed with the existing performance. For example: If you KNOW your "recent apps" section can only hold 4 apps maximum, then you will not be very disappointed when you run a 5th app and one of the previous 4 is automatically closed. Because you KNEW that would happen. Right now, if a new user multitasks with 5.1 on Galaxy Nexus, they would be disappointed when so many "recent apps" need to reload every time.

My #1 tip for memory performance on 5.1 Galaxy Nexus: Limit what apps you have installed. I used OSMonitor ( https://f-droid.org/repository/browse/?fdid=com.eolwral.osmonitor and https://play.google.com/store/apps/details?id=com.eolwral.osmonitor ) and I saw many things running that I didn't know about. I uninstalled what I could. There are many greedy apps out there, running services when they shouldn't.
[Samsung Galaxy Nexus] bamtan2:
[MENTION=4608636]bsmitty83[/MENTION] I've had some time to flash back and forth, and I experience the "no SIM card" error often in ZMOD with the latest kernel. This last time, it went bad and stayed that way even after turning off and wiping cache 0_o

I also noticed the app ZramCC can't report any info about Zram with the latest kernel. Maybe the information is hidden because of this change? I can still see the swap file filling with a regular disk app. But no Zram info in Zram apps.
[Samsung Galaxy Nexus] CoDe LaZaRuS:
Actually I use no more than 1 app at a time xD

I use Amplify, Greenify, Boot manager to maximise battery life and minimise background apps.

I was actually rendering to trickster settings for the kernel. Since [MENTION=2853378]Nephilim[/MENTION] left the Gnex scene I don't know what settings to tinker with

But anyhow appreciate the quick reply :)
[Samsung Galaxy Nexus] bsmitty83:
I noticed it as well , I've been working on that. touch wake is buggy at best , not really sure what can be done for it . the data connection is selinux related , it shouldn't happen in permissive mode.
[Samsung Galaxy Nexus] siealex:
ZMOD always shows "no sim card" after a soft reboot.