yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] AbhishekS:
I too PMed him some weeks back. Didn't get any reply! :/
[Samsung Galaxy Nexus] cmoG530:
I mean, what happened though? He just went MIA, with no trace?
[Samsung Galaxy Nexus] Nephilim:
He was last active at the end of Dec. I suggest you guys head over to DirtyV thread. I mentioned ramspeed optimizations to AK and sh*t is getting interesting. We have metalspring over there helping out too. That thread is bumpin'!!

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] tryo0004:
Watching the back and forth on this kernel and dirtyv... Wondering if your opinions are based at all on your use of the kernels with the most recent AOKP KK nightlies. If any of you are running those builds, I'd love to hear of your success stories and settings (or if you just use defaults or nephlim's general recommendations). Normally I would just flash and mess around like crazy but I've become overly superstitious. AOKP 1-20 is running so stable and smooth off baked in kernel that I'm scared to even trust twrp to perfectly replicate my current run state. Still, I'm a flashaholic and can't help but want better battery life, which I've managed to get with mpokang 1080p on other roms.
[Samsung Galaxy Nexus] AbhishekS:
This may sound surprising but I've gone back to 4.3.2 Jellybean. The devs are doing a great job but unfortunately none of the KitKat ROM or kernel come closer to the smoothness of Jellybean.

I have sort of given up on KitKat. I'm beginning to believe that until we get 3.4 kernel for the Galaxy Nexus, getting KitKat for the device to work as good as Jellybean is nearly impossible.
[Samsung Galaxy Nexus] Kaemo:
For what it's worth, I've seen an increase of posts in the 3.4 kernel thread.

I can't do anything code-related, unfortunately, but I would be happy to donate and assist in any way I can.
[Samsung Galaxy Nexus] Blackcrx:
No offense to any developers. But I would suggest slim 2.4 and dirty sr5 test build. My phone feels like a nexus 4 right now.
[Samsung Galaxy Nexus] Az Biker:
I will certainly vouch for Slim 2.4... It has always been a top notch Rom and has the feel of a professional rom. Well thought out, super stable, and just about the right amount of options to really make it your own. It really is a top contender for the Gnex...

Even though I've moved on to the GN3, I keep my Gnex current with Slim... and honestly, except for the physical size of the two, the Gnex still looks as nice and doesn't feel like a dinosaur compared to my tweaked GN3. And THAT is a hard thing to accomplish!

As far as the kernel: If AK is on team Dirty V, you won't be disappointed. He is a WIZARD with kernels!
[Samsung Galaxy Nexus] AbhishekS:
Have tried that combo too, was good but nowhere close to the smoothness of 4.3.2. No offence to the devs.
[Samsung Galaxy Nexus] Nephilim:
I gather you dont use ART then. LiquidSmooth 3.0 paired with Mpokang SuperRam or DirtyV kernel on ART are far more smooth than anything that has ever came out of 4.3.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] lileoja:
I can install this kernel with night version of AOKP

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] ahmadairfan:
You should try OmniMetal paired with Mpokang, too. It had been the most lagfree and stable combo I've ever had on this phone since I bought it on 2012 lol.

Though I'm now on DirtyV for some testing purposes, this awesome kernel is making its progress.

Of course, why you can't? :)
[Samsung Galaxy Nexus] AbhishekS:
OmniMetal plus Mpokang was one combo which I tested for the longest time. As I said, it was nice but nowhere compared to the brilliance of 4.3 Jellybean. :)
[Samsung Galaxy Nexus] tryo0004:
Thanks for that. When I read the posts following mine I kind of got the feeling people may not have even flashed the newest AOKP builds.
[Samsung Galaxy Nexus] akash3656:
Once that JB ROM you're using starts leaking RAM, we may see you back here again haha. KitKat still leaks RAM but not at the insanely high rate as 4.3, maybe 4.3.2 leaks RAM at a smaller pace but I'm not betting on that. I'm on OMNI the 23rd Jan build and there's some lag when pressing the nav buttons no doubt, and certain ROMs which are hyped to be smooth, but a lot just lag as bad if not more. Its just bad luck with the case of drivers.

Not to be rude to the people working on 3.4 on tuna (in fact if they manage to get it done, big huge congrats to devs and FU to Google), but I doubt anything is gonna fix the weird issues on KitKat 4.4 for our device. What we need first are newer GPU drivers which seem impossible as those can't be built easily (need a new camera/hardware acceleration binary, known as ducati on OMAP and this was not released by Google for tuna I think, normally you have to extract it from stock ROMs). And if those new GPU drivers still don't fix up certain issues, we may have those for a long time until a proper workaround is found.

A 3.4 kernel if built with the old GPU drivers I don't think we will magically get a huge boost of performance. A lot of devs have tried back porting lots of >3.0 kernel commits back down to our kernel, but not every commit boosts performance all that greatly. And if they do help out, moving to 3.4 has a smaller boost then. And there's no telling a new GPU driver would increase performance more than a couple of percent or just solve bugs (frankly more important).

Honestly this whole entire 3.4 kernel sounds as if its going to revive the GNex but to me it's all buzzwords so far. Plus I hope none of your GNex starts having corrupt nand blocks which cause your phone to spontaneously reboot and tale forever to start. Normally going to recovery and running e2fsck on /data solves it temporarily.

/sorry much rant and OT

---------- Post added at 08:06 PM ---------- Previous post was at 08:04 PM ----------

ART doesn't work for everyone and it uses a good 200-400 extra MB to create the ART cache. And back when I tried ART I felt the ROM faster to load apps at start, but after long uptime, the phone gets bogged down lot faster than when using dalvik. I know that's weird, but maybe that's why it's still experimental.
[Samsung Galaxy Nexus] ahmadairfan:
Have you ever tried ART?

I mean, I was a big fan of 4.3 Jellybean too. I was staying on PSX for a long time like from v3 until v8.2. Am still a flashaholic though, so I tried many KK ROMs and then stopped by cMetal back then. That was really smooth at that time. And then OmniMetal comes.

You should look into how it scroll, how it handle things. Try to make a comparison.

RAM usage on both ROM. 4.3 ROM is still laggy for me on the scrolling side. PSX (paired with mpokang, too) I think had been the fastest ROM outta there on JB, opening/switching apps would be the fastest and stable as hell. But it still had it lags whatsoever when scrolling. (Whatsapp, example)

Not on OmniMetal scrolling hasn't been so smooth lol. Opening/switching apps are hell fast comparable with PSX on 4.3 (in ART). RAM usage is more efficient because of the ART. And the last is, it is still under development. It will always get better ;)

Sorry for OT, just an opinion though lol :)

This, I believe is not a placebo. Phone gets less snappy after some period of usage.
[Samsung Galaxy Nexus] ruben46_:
Thanks for this amazing work
[Samsung Galaxy Nexus] Atento:
Wifi tethering doesn't work. This is an awesome kernel, but basic things simply don't work. OTG, tethering...
[Samsung Galaxy Nexus] AbhishekS:
Wifi tethering is fine. Never tried OTG.
[Samsung Galaxy Nexus] antypas:
Your problem.

WiFi tethering works perfectly here just tried it. CM11 1/8
[Samsung Galaxy Nexus] wintel_mac:
Great kernel, using it with SlimKat 4.4.2 Weekly Beta 2.4 and it does a great job. Thanks!
[Samsung Galaxy Nexus] antypas:
Are the mobile data arrows working for you guys or only the WiFi ones?
[Samsung Galaxy Nexus] wavedashdoc:
Hi Hey guys I've been doing some major testing and tweaking with this Kernel and the new DirtyV Kernel.

This post is primarily for the VZW variant but may also yield good results on the GSM variant as well. These, I believe are the best tunables and settings for the kernel. Also this is for the SuperRam version. And I have tested this on the 1/25/14 build of CM 11

TCP: Westwood

RABS: 512 or 768

Scheduler: noop (was with cfq, recently switched to noop because of its benefit on flash based storage devices.)

Min: 384

Max: 14208 (1536 for better benchmarks if your device can handle it, varies)

Max Screen Off: 5376

Min Screen On: 384

Governor: Interactive with Franco kernel settings

Above high speed delay: 15000

Boost: 0

Boostpulse duration: 500000

Go high speed load: 95

High speed freq: 10368 (minimal battery loss)

Io is busy: 1

Min sample time: 4500

Target Loads: 85

Timer rate: 15000

Timer slack: 80000

WiFi HP: off

CAB: off

FFC: off

Multicore power saving 0

High performance sound: off (not needed on CM)

Headphone volume boost: 0 (not needed on CM)

Battery life extender: 98

Dynamic Fsync: off (not worth the risk of messing up your data partition with errors from crashing)

Temperature Limit: 75

GPU OC: 512

Zram: off

Smart Reflex: off (Franco and team did extensive testing and found SR not to be worth while since its not optimized well)

Core Voltages: Franco r394 set voltages

V1: 1120

V2: 1150

V3: 1050

V4: 950

IVA Voltages: Franco 394

V1: 1275

V2: 1150

V3: 1050

V4: 990

MPU Voltages: my custom current voltages (new timings)

1536: 1320 -> 1290

1420: 1300 -> 1270

1344: 1270 -> 1215

1228: 1200 -> 1140

1036: 1070

729: 970

537: 900

384: 840

192: 800 ( just to look right but not used)

Regulator Voltages: Neph and tweaked

Vaux3_6030: 2500 (for the VZW Nexus) 2700 or 2900 (GSM)

VUSIM: 2100

VMMC: 1700

Color settings: calibrated for auto brightness

Contrast: 0

Gamma: 0

Gamma Offset:

Red: 0

Green: -3 ( those on CM 11)

Blue: 0

Color Multiplayer:

Red: 184

Green: 197

Blue: 200

Colors are not over saturated and may not look as vivid. More natural looking colors and whites look white. No purpling affect either.

Thanks to Neph of course for giving me a base to start with and to everyone who continues to work on this great phone!

Edit: further testing setting the voltage regulators to low seemed to overwork the device. Back to stock besides Vaux_6030.

Small edits to Mpu voltage too.

Managed to get highest antu rating at 1420mhz

**undervolted higher values for even better performance**
[Samsung Galaxy Nexus] lileoja:
i wear it and passes 1080p version if I restart or turn on my phone and left a long time without touching it reboots itself, but if restart or turn on, and then unlocking continuing well, someone else happens to him that someone might try thanks

I take the last night of AOKP
[Samsung Galaxy Nexus] Pjodor:
I'm trying other kernels but always coming back to this one it seems.

Skickat från min Galaxy Nexus via Tapatalk
[Samsung Galaxy Nexus] Culex316:
To add to what you said about undervolting the regulator voltages, do not set the VUSIM voltage below 1600. I set it yesterday at 1000 to see what would happen and the screen shut off and the phone went dead. I had to do a battery pull lol
[Samsung Galaxy Nexus] wavedashdoc:
So far with the lower mpu voltages I got one freeze and reboot. So I adjusted a few things

Mpu:

1536: 1300

1420: 1290

1344: 1225

1228: 1140

Color settings (changed for more brightness and less green with lower Vaux_6030.

Red: 194

Green: 207

Blue: 217

Also I have found that the slight OC to 1334 is the best option for consistent deep sleep and consistent frame rate. I will test 1420 more with slightly lower voltages but with 1344 my device rarely goes above 50° for the CPU and that in turn prevents the throttling that begins to show slowness.

Also noop really does seem the best. I was on CFQ with osmosis timed tunables for so long but noop just runs the device so much cooler. :)

Let me know what you guys think!
[Samsung Galaxy Nexus] Tubra:
I think I am having this problem. Sometimes it'll reboot randomly and then just not start at all, I have to flash a nandroid backup to get it running. Same issue on multiple ROMs/Kernels. Not sure how to go about running e2fsck, can that be done through something like Wugs Toolkit? :rolleyes:
[Samsung Galaxy Nexus] wavedashdoc:
More Fine tuning:

To really figure out the best voltages I did some extensive "real use scenarios" Including;

Playing google music

Running the Gps

Running the Gps while listening to music

Running the Gps while listening to music and multi tasking between taptalk, chrome, trickster mod and hangouts

With these new settings I'm 92 percent sure that these are almost perfect for any VZW nexus device, but of course would love feed back

I also did some research into minfree control. So with the voltages basically done I'll dig deeper into this area.

Min Free:

Content Provide: 94

Empty App: 138

Max: 14208 (now safe with no SOD or heat issues)

MPU:

1536: 1300

1420: 1270

1344: 1220

1228: 1170

1036: 1070

729: 970

537: 910

384: 840

192: 820 -> for those who want to run 192. I prefer not to due to bigger spike in ramp up.

The only true final test to be done would be to test all of these scenarios on 4g. I am on wifi at my house. (which may make a difference)

Feedback please
[Samsung Galaxy Nexus] akash3656:
Are you running dyanmic fsync on or fsync off? If you are, your first step is to turn off dynamic fsync or turn on fsync on your kernel. Or just use stock kernel, Trinity, Franco as all this come with Fsync on and you would be constantly rebooting.

If you suspect you have this issue, it is quite hard to "fix" as the bad blocks don't normally show up. But I'll tell you.

Pre-requisites: TWRP 2.6.3.2, working adb/fastboot installed on your computer.

When the device crashes and reboots, pull the battery while its at "Google" screen, put the battery back in, press Vol Up+Vol Down + Power, to go fastboot mode. Then from there, press Vol Up/Down to choose recovery and hit power.

Once in TWRP, hit the Mount button and uncheck/unmount /data and /cache.

Then plug in your phone to your computer. Now open up cmd/terminal and type this "adb shell" then

"e2fsck -c -c -f -D -v -k /dev/block/mmcblk0p12" and hit enter. If you have bad blocks it will ask you to fix them, press "Y" and fix them. Then try rebooting back to Android.

Remember, this isn't a permanent fix, if your phone hits more bad blocks, its gonna reboot again and you have to run these steps again. And once your NAND goes totally kaput, these steps probably won't help anymore. I had to basically play trial and error to fix (all?) of the bad block on my phone by slowly filling up my internal space by downloading all those "free to play" games which are huge. Think Asphalt 8.
[Samsung Galaxy Nexus] marcocsh:
Guys sorry for noob question.

I need to change to the below in the default.prop

ro.secure=1

ro.debuggable=0

persist.service.adb.enable=0

I unpack the boot.img in the kernel zip file and found nothing in the ramdisk folder.

How can I edit the default.prop?
[Samsung Galaxy Nexus] Firewalker1980:
I've returned to Mpokang kernel on AOSPA beta 4 to test your settings and so far they seem fine. Antutu benchmark score is 13285. Can't say anything about battery life though atm. Settings seem stable.

Although on another Rom (CMRemix), I've had approx 138600 score on Mpokang using Nephilim's settings. But the score never seems to the same twice, so that doesn't necessarily mean anything. :)

- using Galaxy Nexus GSM version -
[Samsung Galaxy Nexus] wavedashdoc:
I'm going to have a new full post on more up to date tunables I have come up with 8) going to test them while I'm away from home and at work today.

As far as battery is concerned there is no question of deep sleep, it works no matter what with the correct Vaux_6030 and etc.

Also a side note. I have been getting THE BEST results because I did a clean install of CM11, no extra flashing of mods or using exposed framework. Keeping the device as clean as possible seems to yield with good results.
[Samsung Galaxy Nexus] nickdc986:
Don't know why, but touch control doesn't work on this kernel, any tips?
[Samsung Galaxy Nexus] vfmmeo:
Ony SuperRam variation works with touch control.
[Samsung Galaxy Nexus] wavedashdoc:
Hey guys, got some real world performance results for my newest settings. Pretty good results on 4g with really great deep sleep! Going to look into tweaking the lower clocks so more for better on screen time if possible.

Note: wifi was left on but not actually connected too all day.

Full Settings:

Minfree:

(all of others are default)

Hidden app: 74

Content Provider: 92

Empty App: 142

TCP: Westwood

RABS: 512

Scheduler: noop (add_random 0)

Min: 384

Max: 14208 (1536 for better benchmarks if your device can handle it, varies)

Max Screen Off: 5376

Min Screen On: 384

Governor: Interactive with Franco kernel settings (Thanks to [MENTION=1143630]osmosis[/MENTION]

Above high speed delay: 15000

Boost: 0

Boostpulse duration: 500000

Go high speed load: 95

High speed freq: 10368 (minimal battery loss)

Io is busy: 1

Min sample time: 4500

Target Loads: 85

Timer rate: 15000

Timer slack: 80000

WiFi HP: off

CAB: off

FFC: off

Multicore power saving 0

High performance sound: off (not needed on CM)

Headphone volume boost: 0 (not needed on CM)

Battery life extender: 98

Dynamic Fsync: off

Temperature Limit: 77

GPU OC: 512

Zram: off

Smart Reflex: off (Franco and team did extensive testing and found SR not to be worth while since its not optimized well)

Core Voltages: Franco r394 set voltages

V1: 1120

V2: 1150

V3: 1050

V4: 950

IVA Voltages: Franco 394

V1: 1275

V2: 1150

V3: 1050

V4: 990

MPU Voltages: my custom current voltages (new timings)

1536: 1300

1420: 1240

1344: 1220

1228: 1170

1036: 1070

729: 970

537: 910

384: 840

192: 820 ( just to look right but not used)

Regulator Voltages: Neph and tweaked

Vaux3_6030: 2500 (for the VZW Nexus) 2700 or 2900 (GSM)

VUSIM: 2100

VMMC: 1700

Color settings: calibrated for auto brightness

Contrast: 0

Gamma: 0

Gamma Offset:

Red: 0

Green: -3 ( those on CM 11)

Blue: 0

Color Multiplier:

Red: 194

Green: 207

Blue: 217

---------- Post added at 11:57 PM ---------- Previous post was at 11:54 PM ----------
[Samsung Galaxy Nexus] wavedashdoc:
So I know I only just made my last post a few hours ago but...

I'm about to SUPER CHARGE your galaxy nexus. You may not need to upgrade for even longer.

Ok so I did about 3 hours of research into how minfree works, Turns out minfree really hasn't been tweaked or adjust on a lot of kernels and roms for the GN since 4.0! D: So this, this is what is going to make the biggest impact to your phone. An instant difference in quality. Best part is you don't have to sacrifice anything. you will get;

Better battery life (because the CPU and GPU don't have to work as hard

THE FASTEST multitasking experience yet on your device.

UP TO 6-7 active non redraw apps running simultaneously (GPS, Google Music, Taptalk, Hangouts, etc)

More responsive keyboard popup with 0 lag

Device never goes above 53 degrees (On wifi)

Instant deep sleep

Full Settings:

Minfree:

Foreground App: 10

Visible App: 20

Secondary Server: 100

Hidden app: 120

Content Provider: 95 (lower so hangouts, facebook, twitter, etc can still get background data)

Empty App: 195 (higher to reduce rouge apps from staying in the background based off infrequent use)

TCP: Westwood

RABS: 512

Scheduler: noop (add_random 0)

Min: 384

Max: 14208

Max Screen Off: 5376

Min Screen On: 384

Governor: Interactive with Franco kernel settings (Thanks to [MENTION=4544860]osm0sis[/MENTION]

Above high speed delay: 15000

Boost: 0

Boostpulse duration: 500000

Go high speed load: 95

High speed freq: 10368 (minimal battery loss)

Io is busy: 1

Min sample time: 4500

Target Loads: 85

Timer rate: 15000

Timer slack: 80000

WiFi HP: off

CAB: off

FFC: off

Multicore power saving 0

High performance sound: off (not needed on CM)

Headphone volume boost: 0 (not needed on CM)

Battery life extender: 98

Dynamic Fsync: off

Temperature Limit: 77

GPU OC: 512

Zram: off

Smart Reflex: off (Franco and team did extensive testing and found SR not to be worth while since its not optimized well)

Core Voltages: Franco r394 set voltages (no need to touch these ever)

V1: 1120

V2: 1150

V3: 1050

V4: 950

IVA Voltages: Franco 394 (Now even more fine tuned)

V1: 1275

V2: 1135

V3: 1035

V4: 975

MPU Voltages: Fine tuned low undervolting. Should not see any SOD or freezes (raise each by 15 if so)

1536: 1290

1420: 1265

1344: 1225

1228: 1155

1036: 1045

729: 955

537: 900

384: 825

192: 815 ( just to look right but not used)

Regulator Voltages: Neph and tweaked

Vaux3_6030: 2500 (for the VZW Nexus) 2700 or 2900 (GSM)

VUSIM: 2100

VMMC: 1700

Color settings: calibrated for auto brightness

Contrast: 0

Gamma: 0

Gamma Offset:

Red: 0

Green: -3 ( those on CM 11)

Blue: 0

Color Multiplier:

Red: 194

Green: 207

Blue: 217

Feed back [MENTION=4544860]osm0sis[/MENTION] [MENTION=2853378]Nephilim[/MENTION] [MENTION=4608636]bsmitty83[/MENTION] I would like your freed back especially. If it wasn't for you guys I would have never learned as much as I have.
[Samsung Galaxy Nexus] cmoG530:
Could you do one for Dirty_V???
[Samsung Galaxy Nexus] ahmadairfan:
Apologize, this is the right username [MENTION=4544860]osm0sis[/MENTION] [MENTION=2853378]Nephilim[/MENTION] :)

Gonna try it all after back to mpokang except for the voltages, many thanks! :thumbup:
[Samsung Galaxy Nexus] osm0sis:
I'm going to bring in Paul, he was by far the LMK master in Franco's Dev Team. :)

[MENTION=4793042]pkgnex[/MENTION] What's your take on the lmk minfree here?
[Samsung Galaxy Nexus] wavedashdoc:
Whoops didn't realize I didn't have the correct usernames lol. Was up pretty late last night.

---------- Post added at 03:45 PM ---------- Previous post was at 03:15 PM ----------

I will. Once the Kernel matures more. It's still much to early to really benefit from a fine tunning. No offense to bsmitty83.

This kernel has many benefits such as the 50% ram speed boost; closer to stock clocks; working interactive governor.
[Samsung Galaxy Nexus] osm0sis:
Problem here is mpok is breaking GPL by not releasing the source for v10 so you can't hold the 50% RAM speed boost against any other kernel; it's not by choice.
[Samsung Galaxy Nexus] wavedashdoc:
Yes I know, I've been keeping up with the DirtyV development as well as the 3.4 kernel development.

Odd that he won't respond.

So [MENTION=4544860]osm0sis[/MENTION] have you tried my minfree settings yet? I have been running them all day so far.