yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] 7175:
Changelog looks good, nice job finding and fixing the busybox issue quickly!

If anybody's having trouble coming from AK kernel and maybe other kernels, this might be helpful, even if you've flashed ak kernels before on your current rom:

(coming from any kernel!!) Manually clear the cache for trickster and pgm and make sure you have "set on boot" unchecked in each app's gui.

- Delete "95iosettings", "98fq_codel", "98frandom", "zram" in /system/etc/init.d/ (backup if you want to) -- This clears out custom init.d tweaks and scripts from AK. I added zram and frandom using ak kernel, and I had to delete them to flash to another kernel.

- Run "su", "sh /data/ak/recovery_wpa_hostapd.sh" in terminal emulator OR flash ak_wifi_restore(spelling).zip (from AK thread) and make sure that "system" is mounted in TWRP or CWM -- This restores original wifi.

-Flash stock JDQ-39 kernel, wipe dalvik and cache, then flash new kernel and reboot.

Hope this helps. ;)

edit: I added some specifics on init.d files left by ak kernel. Thanks Blackcrx for pointing out there are definitely some important init.d files that are not created by kernels, so only clean out what's left behind by old kernels. Too lazy to make a new post so this backwards quote will have to do.
[Samsung Galaxy Nexus] Blackcrx:
A easier method which also works would be to dirty flash your ROM, GApps and kernel of choice. With this method you do not need to delete init.d folder contents, revert wifi or flash stock kernel

Also deleting the init.d folder is not always a good thing without reflashing the ROM since a lot of ROMs come preloaded with their own init.d files
[Samsung Galaxy Nexus] lesclark:
r23 is much much better.

smooth and fast ... :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Riekr:
R23 battery drain overnight was about 16% in 7 hours but i was very low on battery so tonight i will recheck.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Syfer_Fever:
i want to report R22 first before i move on to R23 and here's my experience:

-boot animation seems very slow (yes indeed, this because cpu clocled at lowest freq <192 mhz> instead <1228 Mhz> which is normal on every kernel (i checked it in TricksterMOD i saw on cpu stats 192 Mhz 98% time in state)

-problem with trickster mod? i don't think so, becuase my trickster mod setting was normal (Mmuzzy ROM)

-phone lag like hell after boot (i think this because cpu clocked again at lowest freq (192 Mhz)

-and finally i open trickster, set my personal option and settings and hit "apply" and then BOOM! my phone back to normal, everything seems to be very smooth and fast. but i don't know if i reboot my phone again, maybe i have to repeat my step above

and the conclussion is, THANKS! boype for your amazing kernel. i think i'm gonna stay a while with R22, and later i will test R23 (wanna read peoples feedback first) :D
[Samsung Galaxy Nexus] Riekr:
r23 is meant to fix all those issues :)

go ahead without worries with r23 ;)
[Samsung Galaxy Nexus] momomok:
Life is short, why wait? Just flash

(of coz r23 is awesome, I notice zero issue so far :D
[Samsung Galaxy Nexus] angourakis:
boype, let me ask something regarding the GPU:

I can see in TricksterMOD, the default value is 307Mhz with possibility to overclock and select which governor I want to use. I generally don`t play on my phone so 307Mhz and ondemand is just fine. But if I do something heavier (graphic intense), will the frequency ramp up accordingly to the demand or I have to select manually the other high steps?

Regards,

angourakis
[Samsung Galaxy Nexus] mangusZen:
Since someone asked this are my incomplete results with r23 and slimbean.

You can do a roughly math, Im near to 4 screen hours at this rate..

Greenified and inverted slimbean( no games or music, sync off, just phone usage and web in many ways)

Great work thanks!

sent from Vega gnex
[Samsung Galaxy Nexus] boype:
I don't know if you can. All I know is this: Recently, this line was added to the ramdisk's default.prop:

ro.adb.secure=1

Ever since this was added, I cannot get an adb connection anymore. That's why I decided to disable it. Also, the above mentioned line has NOT been in the CM ramdisk for a long time before it was added recently. So my guess is that it is safe to disable it.

Actually I set the default to 384 MHz, but this usually gets overruled by CM based ROMs.

To answer your question: If you do something graphic intense, the GPU will only be scaled up to 307 MHz, unless you set it to something higher.
[Samsung Galaxy Nexus] Blackcrx:
All default kernel settings I assume?
[Samsung Galaxy Nexus] mangusZen:
Yes and standard battery :D

sent from Vega gnex
[Samsung Galaxy Nexus] mohaimed:
Facing lags with r23. Using it with pa rom. Kernel settings all on stock
[Samsung Galaxy Nexus] Riekr:
Secure adb keeps a sha fingerprint of the connected authorized pc and has been introduced in 4.2.2 i think (even stock).

To authorize a pc you should use adb latest android sdk (21.1 if i'm not wrong) and when the device is first time connected a popup should appear asking if you want to authorize that connection. Once authorized the popup is never shown again.

This is about preventing access via usb debug to devices protected by pin since you have to unlock the device to authorize the connection.

If you were not able to connect the problem may simply be that android sdk needs to be updated.
[Samsung Galaxy Nexus] boype:
r24

Hi all,

it has only been two days since r23 was released, but I made a fairly good improvement, so I decided to put up r24 already. Here is the rather short change log:

elevated systemui process priority (smoother UI)

trim filesystem on first boot after wiping cache and dalvik-cache (first boot takes a little longer due to this, but it pays off)

re-enabled ro.adb.secure (all it needs is the updated adb version from the Android SDK)

The 'good improvement' I'm talking about is the elevated systemui process priority. The systemui process is responsible for the transition effects, among other things. That said, it makes sense to give this process as much CPU priority as possible to smooth-out the UI. I cannot understand why this is not a standard setting in Android in the first place - from what I have heard, Apple prioritizes the UI too.

And also, I want to give my thanks to Riekr for explaining the adb secure thingy to me. Nice to know there are people on this thread who I can learn from :good:

[EDIT] I can tell from the download statistics that r23 has been the most popular version of this kernel yet. That is if you look only at the first two days of downloads, as r23 was only up for two days, Thanks to all downloaders!

Best regards
[Samsung Galaxy Nexus] agritux:
r24 is up :D
[Samsung Galaxy Nexus] chiwou:
thanks for this kernel, good battery and very good performance

keep it up :D
[Samsung Galaxy Nexus] momomok:
A new build! Perfect cure for my flash-withdrawal syndromes :D

Beamed from my Nexus Prime
[Samsung Galaxy Nexus] thebogy:
ok, just flashed r24 from r21 let's settle it down. i hope there would be better in performance and battery life :D

great work boype !! :thumbup:
[Samsung Galaxy Nexus] Gafanhotz:
Geesh, first boot took nearly 20 minutes!

I hope the R24 have a batter battery than R23, it was draining a lot here.
[Samsung Galaxy Nexus] Syfer_Fever:
seriously? 20 minutes?
[Samsung Galaxy Nexus] lippol94:
I didn't even wait so long! After 10 minutes of booting process I rebooted and switched kernel.

Something went wrong again :/

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bimasakti85:
Mine got about 5 minutes for the first boot. I think the UI much more snappy than before. Good job boype...
[Samsung Galaxy Nexus] gwindlord:
About 5 minutes indeed, but this is ok :) Thanks boype!
[Samsung Galaxy Nexus] Riekr:
First boot time depends on the status of internal storage since starting from r24 a full fstrim is done on first boot only after flash to optimize performance

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] thebogy:
my first boot only took 5 minutes, and everything works great, flawlessly smooth :D
[Samsung Galaxy Nexus] omid900:
Here it boot for sure in less then 5 minutes, actually I think it take less time to boot then r23!!

The phone feels like a brand new one, it is really great to have this performance.

Thank you boype :thumbup::thumbup:
[Samsung Galaxy Nexus] Riekr:
Has anyone tried hyper governor?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] momomok:
Seriously, it is stated in the changelog that the first boot is gonna be longer than you may have expected...

Beamed from my Nexus Prime
[Samsung Galaxy Nexus] lippol94:
I know. I can read. But it was really taking too much.

As a matter of fact, I flashed back to stock and then wiped cache and dalvik. After flashing r24, it took just 2 minutes to boot + optimizing process. So yeah ;) it's fine now.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] boype:
~20 minutes for the first boot?! Wow :eek: I just added an easily visible note to the OP that it can take some minutes. Even though it takes long, it is worth the wait.
[Samsung Galaxy Nexus] thegtfusion:
Edit: check pm boype;)

Sent from my Nexus Prime
[Samsung Galaxy Nexus] lippol94:
+1!

That would be great in order to smooth things up a little bit when using interactive.

That's definitely a sweet spot for highspeed_freq :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] logi43:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #3) (JAN-27-2013)

I'm using this kernel since its launch, with rel, 1 suffered a SOD phone off and freezing interacticex settings / rw with rel 2, screen freezing and had to remove the battery in both cases, configuration pegasusq / noop, now rel, 3 seems that all is well. On this night only consumed 1% in 8h 35min. Default settings.

I like how this kernel is very smooth, no lag, PGM use application that we all know that sometimes produces screen freeze, also with other kernels, thanks for your work I will continue using this kernel

Edit: Sorry to say I just had a new screen with rel freezing, 3 had to remove the battery.
[Samsung Galaxy Nexus] Doomhamma:
Just for the info, the screen stays on for quite a bit of time - since I almost in 90 % cases when I'm at home ( and read - I was ;) ) my phone is on the speaker and I constantly do something on it - while making a phone call ... But nevertheless, thx for the info ;)
[Samsung Galaxy Nexus] Vladivid:
If you share a governer "X" with PGM you can have freeze or SOD problems. Here the response to a similar problem from other thread - http://xdaforums.com/showpost.php?p=37277278&postcount=9071
[Samsung Galaxy Nexus] boype:
I am currently trying to track down and solve the freeze problems. Apparently, they only occur with hotplug governors, so if you get any - try something else than pegasusq or interactivex.
[Samsung Galaxy Nexus] bigbear6708:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #3) (JAN-27-2013)

In on epicness.. phone woke me up this morning :D
[Samsung Galaxy Nexus] macmeier:
AW: [KERNEL][4.2.x] Fancy Kernel (Rel. #3) (JAN-27-2013)

This Kernel is running great so far. I just had one sod while using Spotify with screen off on.

I changed the governor to interactive and don't experience any sod.

Battery life is great when the device is idle.

Keep up the good work and thanks a lot!
[Samsung Galaxy Nexus] Sveke:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #3) (JAN-27-2013)

What the F did this mean? Haha
[Samsung Galaxy Nexus] huskerkate:
Great work!!

i've been using this since first release, and it just keeps getting better! i haven't had the epic batt life like others have posted, but it has been much better than just about every other kernel i've tried (running XenonHD rom on toro). and even without 16 hours of batt, this thing is still smooth, fast, and stable - no freezes, no lag, no SOD, and it's fast and smooth.

keep it up!!! :highfive:
[Samsung Galaxy Nexus] bigbear6708:
HAHA,

My bad, Good Sir. I rely on my phone to wake me up very early in the morning. There seems to be a plague of Sleep of Death (now referred to as "SOD" thoroughout) happening to 4.2.1 ROMs. This SOD has been generally been appearing after sitting on a charger, overnight; in my usage at least. Needing my phone to wake me up, and overnight SOD happening are NOT a good combination for me. My phone, acting as my alarm clock, woke me up this morning, inferring that a SOD did in fact not happen. Enter, epicness!
[Samsung Galaxy Nexus] Sveke:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #3) (JAN-27-2013)

Haha, I knew what you meant. I was just laughing at the language.

I hear you though, on time for work is epic.

Sent from my Nexus 7
[Samsung Galaxy Nexus] lancec50:
New to the Galaxy Nexus world of ROM's. Glad to have the option to flash kernels again. Have a quick question can I use this kernel with Official AOKP MR2 build 1/27/13. I have Lean Kernel but everyone is talking how epic this kernel is running and would love to try it out. I know some of the kernels I used when I had Nexus S some wouldn't cross over very nice if they where built for CM. Thanks for help guys. I am loving my phone again. Nexus FTW
[Samsung Galaxy Nexus] justme1988:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #3) (JAN-27-2013)

Really great battery keep up the awesome work!

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] Sveke:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #3) (JAN-27-2013)

Should be good as long as its 4.2.1 ROM. Haven't tried AOKP yet.
[Samsung Galaxy Nexus] larkhillv:
No SOD or reboots or freezes for me yet. Running latest release on latest Xylon. The only possible issue I've encountered so far is GPS lock on. Usually I can get a lock on indoors at my house. Just tested and it didn't work. I'll test outside and moving tomorrow to be sure. Other than that, good job on this kernel. Very snappy and responsive with good battery life. Ended the day with around 14 hours discharge and 30% left with light to moderate use, including some LTE connectivity. Last I checked, I had a little over an hour screen time. Probably around 70 mins with screen around 30-35% brightness.
[Samsung Galaxy Nexus] mrasquinho:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #3) (JAN-27-2013)

Perfect battery time with Release #3

However,sometimes the phone freezes! It happened to me in a call and ending an app. I had to pull off the battery..

---------- Post added at 01:54 PM ---------- Previous post was at 01:53 PM ----------

I forgot to say that I'm using default settings
[Samsung Galaxy Nexus] gwindlord:
Yeah, the default governor is pegasusq with hotplugging, which seems to be the most frequent freezes reason. If you would have a slowdown, the culprit could be kernel, but for freeze it is not always true.
[Samsung Galaxy Nexus] mrasquinho:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #3) (JAN-27-2013)

Yeah, but I've been using for months Franco Kernel and even cm10.1 default kernel and the freezes never happened.

However, I'm keeping Fancy kernel. Greatest battery life ever!
[Samsung Galaxy Nexus] nziria:
set to interactive governor and no freezes at all.tested on lean kernel. i have to test this kernel :)
[Samsung Galaxy Nexus] Hawkw1nd:
+1
[Samsung Galaxy Nexus] larkhillv:
I was able to get a GPS lockon outside, so I guess I was just getting poor signal from inside my house. So, the kernel seems to work fine. I haven't been getting extraordinary battery life today. Switched from pegasusq to interactive now after reading some comments. Hopefully tomorrow I get at least slightly better battery life. Today, I have been getting about 1.25-1.5 minuts of screen time for every 1% of battery, so pretty average. Doesn't seem like I have any rogue apps, so I guess it's just how the kernel is on my phone.
[Samsung Galaxy Nexus] DariosF:
Let's try it...Thx dev ;)
[Samsung Galaxy Nexus] mangusZen:
Second boot is very very fast, very happy with performance for now. :thumbup:

sent from Vega gnex
[Samsung Galaxy Nexus] bunnahabhain:
This Kernel looks very interesting..

How stable is it? Is it in experimental stage like AK Kernel or is it stable like Francos - or in between?

Good choice anyway to compile from CM sources cuz these days nobody knows how AOSP kernels cope with Cyanogenmod... Good to have a fully compatible kernel for CM!

Freundliche Grüße nach Flensburg der Herr - schöne Stadt ;)
[Samsung Galaxy Nexus] lippol94:
Stable.

For example he reverted a commit once just because the kernel was no longer compatible with PGM.

Other devs don't care and say to go and complain to pgm dev.

Fancy dev reverted it and bam, compatibility restored ;)

So yeah. It's 100% stable.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ericsdeadinside:
Hyper governor seems to try to keep frequency on the lower end. But this phone just hemorrhages battery life when not idling in general. So who knows.
[Samsung Galaxy Nexus] madhavs:
Love this new version but just having one small problem it's about wifi Does anyone experience wifi dropouts with r24 all default settings

Reverted back to r21 for the time being
[Samsung Galaxy Nexus] Invicta:
Fully, 100% compatible with cm10.1????
[Samsung Galaxy Nexus] agritux:
yes
[Samsung Galaxy Nexus] mixtapes08:
More than 100 coz it's built in cm sources. :) :thumbup:

-3StarsAndaSun
[Samsung Galaxy Nexus] Invicta:
Love this:thumbup:
[Samsung Galaxy Nexus] bunnahabhain:
Wow!

I am impressed with this as well... Long Time Ak and Franco User - but this one rocks! Really!
[Samsung Galaxy Nexus] 123egg:
Just done my first boot with r24, boot + optimize apps takes under 5 mins. After that everything is good. Thx for the update!
[Samsung Galaxy Nexus] odavans:
+1 and working extremely fast and stable. Hyper gov. super-duper fast :)
[Samsung Galaxy Nexus] Invicta:
just flash the zip file, no cache and dalvik cache wiping as standard?
[Samsung Galaxy Nexus] n2rjt:
Using 23, fuss doesn't work for me. I'll update manually.

Edit: fuss worked from terminal emulator, just not from SMWidget. 15 minute first boot. Sheet ecstasy. Thank you!
[Samsung Galaxy Nexus] lippol94:
I'm astonished.

Nothing more to say. Ui is smooth like butter, no more lag in systemui transitions. Kept everything as stock but rab = 256 (which is still set to 512kb by default. I thought you changed it to 256kb :)) and colors.

I'll report more feedback in a few days. :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jjhrrsn:
I. Love. This. Kernel.
[Samsung Galaxy Nexus] boype:
I recommend wipes, but they are not a necessity.

readahead is 256, I'm sure it is. Must be some leftover script / app that sets it to 512.

I'm really happy about the positive feedback here. :victory:
[Samsung Galaxy Nexus] Invicta:
First try, impressions are very good

Rom is CM10.1

settings are all stock except for

RAB=512

Scheduler=row

MAX=1.42GHZ

max screen off is 729000

Multicore P.S.=0
[Samsung Galaxy Nexus] lippol94:
My mistake. I forgot about init.d script by osm0sis in order to optimize i/o scheduler.

I wish you all the best boype!

You did an amazing work. :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mixtapes08:
Anyone having lags adjusting brightness via status bar slider.? Ive noticed it with franco kernel too...

-3StarsAndaSun
[Samsung Galaxy Nexus] mangusZen:
Keep this kernel tight, you're gonna miss it someday :p:p:p:p

sent from Vega gnex
[Samsung Galaxy Nexus] jesssiii:
What do you mean?
[Samsung Galaxy Nexus] mangusZen:
That is so good, when you'll change it maybe you'll wish to have it back :p:p:p

sent from Vega gnex
[Samsung Galaxy Nexus] zoomy942:
Any thoughts on sio vs deadline?
[Samsung Galaxy Nexus] TheMysteriousOne:
Found deadline much smoother with these tweaks:

http://xdaforums.com/showthread.php?p=41263013
[Samsung Galaxy Nexus] lippol94:
That's a rom thing. Nothing related to kernel side.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] zoomy942:
And without tweaks?
[Samsung Galaxy Nexus] thegtfusion:
sio for sure.
[Samsung Galaxy Nexus] mixtapes08:
I know what I'm doing dude.. It's definitely a kernel thing..

-3StarsAndaSun
[Samsung Galaxy Nexus] zoomy942:
I'm running it now on cm rc2. Will update later. I'm very interested in the system ui change.

Running 384/1400 speed.
[Samsung Galaxy Nexus] ciprianruse88:
Well dude...no lag here adjusting brightness via status bar slider on purity 5.4.1 :)
[Samsung Galaxy Nexus] wai10691:
Thanks for making me falling in love with my phone once again.
[Samsung Galaxy Nexus] lippol94:
Probably you don't! I'm sorry man but that's a rom thing. In fact, CM code for adjusting brightness has always been a bit laggy, while aokp one is absolutely responsive.

This has nothing to do with kernel.

Thanks ;)

I know. I said the same yesterday! :) Boype congratulations! SystemUI thing is an incredible idea. :good:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] boype:
Thank you, thank you :)

One question for everyone: is the smoothness keeping up for you, even after 1 day of system-on-time?
[Samsung Galaxy Nexus] ciprianruse88:
22h here and yes...it's still smooth :thumbup:
[Samsung Galaxy Nexus] boype:
Good stuff :)

I was asking because I was getting lags with my May 4th CM10.1 Nightly, but those lags only occurred on homescreen.

I read up on the issue in the cm10.1 thread and I'm relieved it was a CM memory leak which now has been fixed. So nothing that the kernel screwed up.
[Samsung Galaxy Nexus] HessNL:
Nice kernel but I have a qeustion about it what is hyper governor? And the best way to save battery :) I have it now on ondemandplus and sheduler in noop
[Samsung Galaxy Nexus] sergini:
You have made it boype! Awesome job you did with 24.
[Samsung Galaxy Nexus] gwindlord:
Surprisingly it still is, though didn't on previous builds :) Thank you!
[Samsung Galaxy Nexus] boype:
From some thread in XDA:

While the English in this explanation almost looks like a machine-translation, the paragraph does not really contain much information IMO. All I know about Hyper is that it is ondemand-based and has suspend/wake code to provide different CPU scaling behavior when the screen is off.

I could look at the source code of hyper to give a more detailed overview, but I'm simply too lazy to do that (I'm rather slow reading others' code).

Without having really looked at hyper, I'd say ondemandplus is superior, also in terms of energy savings. But my mind is not really un-biased, since I'm the author of ondemandplus :eek:

It was one of my major concerns, and then I found out why smoothness wasn't staying :) Also, the backported 3.4 lowmemorykiller does an awesome job in freeing RAM, while still keeping most apps in memory.
[Samsung Galaxy Nexus] Bl4ck3urn:
Hyper:

The Hyper (formerly known as kenobi) is an aggressive smart and smooth, optimized for SGS2 getweakt and, based on the Ondemand, which was getweakt of Arighi and was equipped with several features of Ondemandx suspend imoseyon. (Added by sysfs, the settings suspend_freq and suspend Imoseyon's code) is the behavior of the hyper Ondemand if he is in action, very similar. He also has the Arighi's fast_start deep_sleep and detection features. In addition, the maximum frequency is in suspend mode 500Mhz.

Source: http://xdaforums.com/showthread.php?t=1663809

Cheers
[Samsung Galaxy Nexus] differentstyles:
Afters some months with Ak I've switched to your kernel yesterday. After one day I must say your kernel seems to be in love with my gnex:thumbup::thumbup::thumbup:
[Samsung Galaxy Nexus] omid900:
Using r24 since yesterday morning and it stills the same...... Very fast!!

Only thing I just need to confirm is the battery level, but seams still be good :):)

Thank you boype :thumbup:
[Samsung Galaxy Nexus] RevengeFNF:
This is the kernel of the moment.