yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Fatsodonkey:
Splash loop on cm11 0809 nightly. With dirtyV it works.
[Samsung Galaxy Nexus] namtombout:
Ensuring the second core kicks back in after it goes offline. With stock voltages I got lock ups, had to pull battery. I'm assuming it's the hotplug driver because I've been tuning hotplug governors and get similar lock ups when certain tunables are varied

Or could it be because I'm on 4.2 cm 10.1.3?
[Samsung Galaxy Nexus] pattyboi:):
Could be voltages too they are extremely undervolted by default,I'll take a look into that tho,thanks for clearing that up :)
[Samsung Galaxy Nexus] eternal70:
[MENTION=5380162]pattyboi:)[/MENTION] have seen you playing with the kernel on github these days [emoji1] seems a big update [emoji5]
[Samsung Galaxy Nexus] pattyboi:):
yes sir ;) theres been alot of updates for f2fs,some for wifi,took in some updates from ziaynns omapzoom kernel for powerdomain controller,updated the backend for dynamic page writebacks,updated ksm due to smittys work,updated sioplus from boype repo,then some misc updates/patches from omapzoom/linux upstream/bopye :) im gonna add in a couple governors then throw the build up either today or tomorrow :)
[Samsung Galaxy Nexus] eternal70:
Looking forward to that. Had been testing the new release of other kernel but, this kernel + interactive modification from nephilim give me the best performance and battery. Yeah the hotplug is soo much stable [emoji2]
[Samsung Galaxy Nexus] mrgnex:
Wait, stable and hotplug in one sentence? You had my curiosity but now you have my attention. I'll try this after the next update :)
[Samsung Galaxy Nexus] eternal70:
Just try this man. Yes everything has changed. :D
[Samsung Galaxy Nexus] freshgiammi:
Intelli-plug from faux used to be really unstable. Hotplug governor was really slow to use, at least for me. InteractiveX from imoseyon was great but yet not much battery saving. Will Tisdale's ARM Generic Hotplug is a whole new world. gg for that pattyboi ;)
[Samsung Galaxy Nexus] pattyboi:):
alright guys,new build is up :P

-updated powerdomain controller from the omapzoom kernel

-updated ksm to upstream as of yesterday

-updated f2fs to upstream as of yesterday

-brought in some misc updated to the 3.10 wifi drivers

-updated sioplus to boypes source

-updated workqueue slightly

-updated and switched to lzo kernel compression

-added a soc thermal throttle switch from franco

-added a couple other misc updates to various kernel parts

oh and i updated to christopher83's latest cortex a9 toolchain :)

enjoy!

i didnt add any governors in for this release,i mostly focused on updating some things,next release ill add 2 or 3,but you guys gotta let me know which ones you want,just post your fav govs and ill pick a couple to add :)
[Samsung Galaxy Nexus] eternal70:
Wake up in the morning and see a kernel update :good:

First time the kernel gives me a bit more smoother. For governor , i like intelliactive and maybe gallimaufryX [emoji2]
[Samsung Galaxy Nexus] pattyboi:):
i dunno how well the hotplug driver will work with hotplugging govs (even if we set the driver to keep 2 cores on) ill look into it tho :)
[Samsung Galaxy Nexus] eternal70:
What governor is hotplug based ? Intelliactive is interactive based and gallimaufry is ondemand based as i know. Correct me if i'm wrong [emoji28]
[Samsung Galaxy Nexus] pattyboi:):
gallimaufryx has hotplugging as does intelliactive,intelliacive hotplugs when the rq_stats report load is low enough to not be tramitizing to performance if we hotplug,gallimaufryx kinda does a load based one too,but far more primitive and its more prone to lock ups,the regular gallimaufry sounds like a good thing to try tho
[Samsung Galaxy Nexus] eternal70:
Thanks for the correction. Junior highschool works makes me crazy so i can't build my own test kernel again [emoji17]
[Samsung Galaxy Nexus] pattyboi:):
your a junior? awesome!im a freshman :P
[Samsung Galaxy Nexus] mrgnex:
I flashed NukedTrinity4 last night but I got a Google logo bootloop. I'm on Vanir f2fs (the nightly from 13-7-2014 or 7-13-2014 for 'muricans ;)) and I had Fancy kernel r55 installed. Is there anything I can grab to help?

EDIT: Where is the boot.img? I only see mkbootimg. Is there a way I can convert something to a boot.img?
[Samsung Galaxy Nexus] eternal70:
Have you tried clean flash (wipe only system, dalvik, and cache) ? I have many FC when dirty flash. Im on DU
[Samsung Galaxy Nexus] pattyboi:):
this is a anykernel kernel (no ramdisk,just kernel itself) the kernel is zimage,try fastbooting it please,i wanna nail this down,i know it boots cause im running it now lol
[Samsung Galaxy Nexus] musical_chairs:
My thought was the same as Pattyboi's above, this flashes using anykernel so you need to dirty-flash your ROM before flashing the kernel if you're on another custom kernel. BTW, this kernel is working great so far on the latest Omni nightly.

[MENTION=5380162]pattyboi:)[/MENTION] I'm using your kernel at the moment because you say in the OP that you've got stuff from Ziyan's OMAP kernel tree. I had been running my own builds of his stable branch, and having issues with camera (OMX becomes unwriteable after about 24 hours uptime, not sure yet what is triggering that). I was suspicious of the RAM timing tweaks, which was one of the few patches I had added. Since your kernel includes those too, I thought I'd run NukedTrinity and see if I can re-create my issue here. So far, I like your kernel. :highfive:
[Samsung Galaxy Nexus] pattyboi:):
omx stops writing because of the remoteproc changes if i remember correctly,i think there was something else he said cause omx to be unstable,all tho i cant quite remember what it was,all tho i know its not the ram timings,they wont tie into that :P & thank you i appreciate that alot:)
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] was having this issue when using a 4.8 toolchain but it boots fine with 4.9.1 which one you using?
[Samsung Galaxy Nexus] pattyboi:):
Christopher83's latest arm cortex 19 toolchain from a couple days ago
[Samsung Galaxy Nexus] mrgnex:
I tried flashing the zImage via fastboot but it didn't work..

I need an f2fs kernel for flashing a rom. So I need to flash a custom kernel anyway..

Any way I can fix this? I am quite a noob with f2fs..
[Samsung Galaxy Nexus] pattyboi:):
ill keep looking into this :good:
[Samsung Galaxy Nexus] Punkiderma:
Flash the ROM with default kernel, then flash this. Only then reboot to system.

You can flash a ROM with a kernel that is not f2fs enabled, only thing important is to change it with a compatible one before leaving recovery, or you'll be stuck at boot logo [emoji6]
[Samsung Galaxy Nexus] redj12:
Can't boot on slimkat last version. Any idea ?
[Samsung Galaxy Nexus] musical_chairs:
Well, camera is working fine after 48 hours uptime, so the bug I was looking for isn't in this kernel. But what happened to MTP and adb? They both seem to be broken (toroplus on OmniROM, recent nightly). Flashed back to Omni and they work again.
[Samsung Galaxy Nexus] mrgnex:
Depends, which version (date and f2fs or ext4) are you running? And which kernel before this one?
[Samsung Galaxy Nexus] pattyboi:):
Adb and mtp work fine for me..and I'm on FML...probably something wrong with omni init files
[Samsung Galaxy Nexus] redj12:
SlimKat 7.6 (ext4) and my kernel is the stock one. Maybe is should reflash the ROM before the kernel flash ?
[Samsung Galaxy Nexus] mrgnex:
Yeah this is anykernel so that is recommended ;)
[Samsung Galaxy Nexus] Jagoflax:
I'll give a try, thank you!
[Samsung Galaxy Nexus] pianistaPL:
I converted Omni to f2fs using poo tool and i used DirtyV kernel for this. I freshly installed the ROM (with DirtyV kernel) then i installed NukedTrinity and unfortunately i have still Google logo bootloop.
[Samsung Galaxy Nexus] Jagoflax:
Google logo bootloop after a fresh clean installation of official PA (ext4) :'(
[Samsung Galaxy Nexus] aliesz:
I don't know who could try this kernel?! everybody with different roms say about bootloop and logo stopping.
[Samsung Galaxy Nexus] mrgnex:
I had that problem too with vanir f2fs. The suggestion that was given me is to flash the ROM (it is any kernel so it uses the ramdisk of what is flashed before), I figured that out but you need to edit the ROM yourself. You can't use the f2fs converter because that uses a custom kernel.. Then flash the edited ROM and flash this kernel. At least that's what I think..
[Samsung Galaxy Nexus] pattyboi:):
-_-

i tried it. works pretty f**king good for me.
[Samsung Galaxy Nexus] aliesz:
What is your ROM and previous kernel?
[Samsung Galaxy Nexus] pattyboi:):
i only use my kernel and im running fml.
[Samsung Galaxy Nexus] an430:
Hi, is it fit for PA rom?
[Samsung Galaxy Nexus] jhonnyx:
Hi, seems not for the moment. You can do a nandroid backup always and try, then report ;)
[Samsung Galaxy Nexus] aliesz:
What the fml rom has?! Most of ROM's don't work with this kernel.
[Samsung Galaxy Nexus] eternal70:
PA and DirtyUnicorns are working with this. I have tested it myself
[Samsung Galaxy Nexus] aliesz:
See previous posts such as 109,110, it doesn't work with PA, omni,slim, stock 4.3,..
[Samsung Galaxy Nexus] eternal70:
You didn't believe me ? I have tried it yesterday. Should i try it again ?
[Samsung Galaxy Nexus] redj12:
I am on DU and the phone won't boot. Some days ago I was on Slim and the problem was the same. Even with a clean installation.

So, maybe it's OK for you and other 3-4 people but for major part of us the phone won't boot. The dev should take a look or it's already done and he can't find any solution.

I will wait and flash the next release for sure. Maybe this boot issue will be solved.
[Samsung Galaxy Nexus] eternal70:
As you see it works on PA and DU. Ask me what rom you want me to try and this night i will try that. Maybe you should wipe system partition too before flashing
[Samsung Galaxy Nexus] redj12:
Huuum weird. The only thing to do is wait the next release.

Ps: what is your theme on the first screen ? Thx
[Samsung Galaxy Nexus] eternal70:
Yeah im also waiting for the new release. Seems many changes for RAM management on it [emoji2]

Oh and the theme is Android L from Nucleoid
[Samsung Galaxy Nexus] pattyboi:):
Deleted due to my incompetence ;)
[Samsung Galaxy Nexus] redj12:
I am sorry but it wasn't nasty at all bro, believe me. This is your personal kernel and you share it for all of us so our duty is to report all of problems. It was just a "suggestion". Nothing rude amigo.

I am on tiny but thx for suggestion.
[Samsung Galaxy Nexus] pattyboi:):
My bad dude,its bee one of " those " weeks,I interpreted that the wrong way,honest you have my sincere apologies, and to anyone else I kinda pulled that d*ck move on,I am looking and I am working,I promise.
[Samsung Galaxy Nexus] eternal70:
So you are continuing this kernel ?? Ah i almost throw my maguro when you say that this kernel development has stopped
[Samsung Galaxy Nexus] pattyboi:):
I'm gonna continue :p just kinda had one of those weeks and took things the woing way
[Samsung Galaxy Nexus] eternal70:
Yeah, i'll always wait for it. I'm also still searching for the best rom that's perfect and stable for me. Take your time dude !
[Samsung Galaxy Nexus] eternal70:
[MENTION=5380162]pattyboi:)[/MENTION] found some funny bugs. Or maybe this is not bug ? When enable fast charge, the computer detected the device. But when fast charge turned off, no MTP notification on phone. Anyone who has problem with computer connection can try to enable fast charge
[Samsung Galaxy Nexus] pianistaPL:
[MENTION=5380162]pattyboi:)[/MENTION] Bro, are you using FML converted to f2fs or standard ext4?

Ah, i forgot that FML is f2fs&ext4! I hope that this time your kernel will work on my phone :)

---------- Post added at 09:35 PM ---------- Previous post was at 08:49 PM ----------

I don't know why but it's still not booting...

CLEAN install - i installed latest FML test build, Banks Gapps, then wipe dalvik&cache (i don't think it's necessary by clean install but i always do that) and then i installed NukedTrinity4. I don't know what's wrong, DirtyV or Fancy boot fine.
[Samsung Galaxy Nexus] eternal70:
Have you wipe system partition ?
[Samsung Galaxy Nexus] eternal70:
[MENTION=5380162]pattyboi:)[/MENTION] what the hell is moto quick wake up ?? [emoji1] seems the new update are going crazy !
[Samsung Galaxy Nexus] pianistaPL:
Yes, as i said - clean installation.
[Samsung Galaxy Nexus] eternal70:
Are you using f2fs ? if yes then i cannot do anything. Just wait for the dev
[Samsung Galaxy Nexus] redj12:
Clean install of Carbon, won't boot. Ext4 format.
[Samsung Galaxy Nexus] eternal70:
Seems there is issues on your phone. I'm on carbon now. You can't pass the google logo ?

---------- Post added at 06:39 PM ---------- Previous post was at 06:34 PM ----------

Anyone who can't get it booting, maybe can try to wipe all the phone. My friend's galaxy s2 got the same problem on almost all roms available. But then when i wipe all the phone, it works. Remember to move your important data to another storage
[Samsung Galaxy Nexus] pattyboi:):
yikes o.o

ok:

1:fast charge works,its just the new version with the working storage capability as well as faster charging

2:this rom bug is the most confusing sh*t ive ever seen

3: quick wake up is a driver from moto that allows the kernel to sorta "half-wake" out of suspend state to do a task,then fall back to suspend if the task can be handled in half suspend (basically a low power wake driver which handles tasks then puts the phone back to sleep)
[Samsung Galaxy Nexus] jhonnyx:
hmmm.... to all users that won't get a boot, are you on maguro, toro or toroplus?

I'm on maguro. what about you? I can't get it to boot, maybe it's a device specific :(

Someday we'll get it booting :)
[Samsung Galaxy Nexus] pianistaPL:
Maguro here
[Samsung Galaxy Nexus] Jagoflax:
Maguro too
[Samsung Galaxy Nexus] jhonnyx:
annnnnnnnnnnd, does not boot, right?

Can anyone from Toro/Toroplus can confirm wether it boots or not?

(we know patty's does boot, he's on toro if my memory's ok, feel free to correct me, bro)
[Samsung Galaxy Nexus] pattyboi:):
yes sir,toro and a toroplus actually
[Samsung Galaxy Nexus] jhonnyx:
Seems the ghost haunting me for no data over toro/toroplus is haunting you for boot :(

HolyCrapBatman!
[Samsung Galaxy Nexus] redj12:
Maguro here sir :)
[Samsung Galaxy Nexus] eternal70:
Seems so many changes on your github these days, but you didn't release any update. Maybe planning on something ? [MENTION=5380162]pattyboi:)[/MENTION]
[Samsung Galaxy Nexus] pattyboi:):
im still trying to fix fricking omni,it boots,but its not stable,im still teasting random sh*t tho,i may release a build today for anyone that can boot
[Samsung Galaxy Nexus] braddock84:
Nuked 3 and 4 boots on my toro but the screen has a bright red tint. I'm running vanir
[Samsung Galaxy Nexus] pattyboi:):
first: i know its been forever and i apologize,life got a lil wonky for awhile for me :P

seconded: im not promising this boots for everyone,i know it boots omni,vanir and fml for sure.

third: i just want everyone to know this kernel is very very " hacky" xD as in i kind chop sh*t up and throw it in and hope it works than try to fix all the issues that come from it (if any)

okay,on to what most of you want to hear (if anyone is still interested XD): new sh*t-

Dynamic LMK values. (screen on/screen off set dynamically)

Added the new ION allocation system from daniels repo (ported in from omapzoom)

Added the bug fix for bluetooth from Deehraj CRV to fix the chip always technically on consuming power

Fixed the IVA (image video accelerator) sticking at the highest enabled frequency until state changes (e.g. using the camera would allow it to finally ramp down,until then it would be stick at full speed consuming power)

Added a errata smitty found to fix some OWSR power leakage

Added boypes fix for DTIM skipping to the 3.10 wifi drivers (originally wasnt there,duh)

Completely disabled Duty Cycle Correction as our chip (4460) ((according to OmapZoom)) has a Hardware problem and should be used period

Updated the Omap DPLL controller code to our exact frequencies so it knows exactly how to set things

Updated sioplus from pkgnex

Removed arm CPU topology as it was broken in the first place

Switched back to the original fsync control

updated the twl6040 SOUND driver from dans repo/omapzoom

modified auto_hotplug to work better on a dual core device

updated f2fs from mainstream

pulled in some slight i2c bus updates from mainstream

added zram

basically,this update will have much better performance,and better battery life. enjoy.
[Samsung Galaxy Nexus] eternal70:
Hmm at last. May i suggest you something ? While waiting i also make custom build of your kernel for every update you push to github. You can use SaberMod 4.9 toolchain because it give me more speed. And also please add your "rage" governor. It's CRAZY !

Just my suggestion [emoji6]

Thanks for the update though. Will test now !
[Samsung Galaxy Nexus] pattyboi:):
I'll check into a sabormod toolchain :) that's actually something I've wanted to try :3 & I'll look into rage,it needs work right now,but I think I can set something up soon :) thanks for the suggestions bro!
[Samsung Galaxy Nexus] eternal70:
Okay, have checked the kernel. Only one bug so far that has been present since the first version. The MTP is often not detected. The rest is all good !
[Samsung Galaxy Nexus] rajputrajat:
[MENTION=3990075]Pattyboi[/MENTION], really admire your passion and effort.

I am really thrilled after going through the change-log.

You make us feel that there are still endless possibilities with this device.

but my bad luck - could not pass google logo screen this time.. :-/

Thanks a lot.

EDIT:

ROM - Liquid smooth unofficial 30/09
[Samsung Galaxy Nexus] eternal70:
What rom did you used ? Already clean install ?
[Samsung Galaxy Nexus] rajputrajat:
Ohh, forgot to mention that.. I'm on 30/09 "liquid smooth unofficial"..

no, did not try clean-install - due to ART cache building takes time and phone gets pretty hot and I fear for mobo of phone...
[Samsung Galaxy Nexus] eternal70:
Hold on, im trying it now with liquidsmooth
[Samsung Galaxy Nexus] eternal70:
Ok, have been checked. Latest liquidsmooth unofficial took a very long time to boot. The charging led is on, but still showing the bootanimation. I will recheck it later
[Samsung Galaxy Nexus] pianistaPL:
And what ROM are YOU using with new version? :)
[Samsung Galaxy Nexus] eternal70:
latest crdroid
[Samsung Galaxy Nexus] handofdark:
sadly none of the versions boot up on my omni rom. stuck on google screen
[Samsung Galaxy Nexus] Punkiderma:
For me (latest liquidsmooth unofficial, system ext4, data and cache f2fs) it boots, but then I get submerged by apps' force close messages :(
[Samsung Galaxy Nexus] eternal70:
It's because anykernel. You nedd to dirty flash your rom before flashing the kernel. Then the FC's will be gone [emoji6]
[Samsung Galaxy Nexus] pattyboi:):
guys im very very very sorry for anyone im causing a problem i really feel bad because i have literally no idea what is going on,like i said ive had it boot fine on omni (used for 2 days straight),worked fine on vanir,works fine on fml (my daily driver)

but ill keep looking,it might very well be something the rest of the guys pointed out forever ago,ill check.

[MENTION=5127221]eternal70[/MENTION] bro i just wanted to say thanks you have been a massive help in the thread and i really really appreciate it,

as he said guys try dirty flashing than flashing the kernel,if it dosent work my apologies,im literally down to 1 or 2 ideas other than that i really dot have any clue whats going on
[Samsung Galaxy Nexus] pattyboi:):
hi guys :)

progress update:

big thing first,im sure everyone heard about how [MENTION=3390093]MWisBest[/MENTION] did some great work fixing camera/HW decoding & encoding with the new gpu drivers,im picking up those new drivers as i type :)

2: i enable Smartreflex for the gpu were it will really save a decent amount of power :) (especially with the ddk 1.9 update) ((& i added the sysfs entries from dtrail and imoseyon for modding the highs and lows of sr))

3: i did switch to sabermod toolchain from clk3ner and it runs pretty damn smooth

ok now the little things:

1: i added ASRAM back :)

2: i updated hotplug to work a little better for our chip ;)

ill have a update when i get all the ddk sh*t setup :P
[Samsung Galaxy Nexus] pattyboi:):
got a new build up :)

didnt switch to the OZ kernel yet so no ddk 1.9 :/ i couldnt get a build to boot with it yet,ill keep working tho

did a lil work on lmk,so it should perform better and handle multitasking better

changed the workqueueu for auto_hotplug,it should be smoother now

switched to a uber-sabermod toolchain,if anyone has a computer with enough horse power to build me a cortex-a9 optimized sabermod 4.9 toolchain id seriously be so thankful cause this toolchain is baller even without being set directly for our cpu

adjusted some voltage parameters for the regulators and pmic,should be safer for everyone

im hoping the adjusted voltages let more people boot the kernel,if it dosent im out of ideas :/

either way,enjoy!

oh,and i got rid of that SR hack i did for the gpu,it was sending the logs crazy,ill take another look into it later,for now all sr is disabled
[Samsung Galaxy Nexus] eternal70:
Wow ! Thanks for the new build. I want to help you but this week i'm having an exam.

Why 4.9 ? For me 4.10 sabermod increase the smoothness a bit more than 4.9
[Samsung Galaxy Nexus] pattyboi:):
4.10 was giving me section mismatches,i dont know what that means but i know its a warning ++ official GCC 4.10 hasnt even been released yet,all 4.10 toolchains are sorta hacky combos of linaro and saber and standard gcc source,they may build and be smooth,but im gonna wait a little before fully switching to it,just so it can ironed out a lil more ;)
[Samsung Galaxy Nexus] eternal70:
Okay guys here's my personal build. Compiled with Sabermod 4.9 plus some difference from the official build :

1. Added gallimaufry gov

2. Disabled SELinux and android logger

https://docs.google.com/file/d/0B7SqITe__f5KZHlBLUVzUjlQbU0/edit?usp=docslist_api

Enjoy !
[Samsung Galaxy Nexus] aliesz:
Thanks pattyboy,but I think the version of GCC is not so important that compatibility on different roms is.
[Samsung Galaxy Nexus] pattyboi:):
I have been trying and trying and trying to fix compatibility. I'm literally out of ideas,each "fix" I thought of hasn't fixed anything. I have literally 2 ideas left,if anyone has any ideas please let me know.
[Samsung Galaxy Nexus] eternal70:
Yeah i'm confused too. All the rom i tried is working. Why others not ?

---------- Post added at 06:17 PM ---------- Previous post was at 06:07 PM ----------

By the way, [MENTION=5380162]pattyboi:)[/MENTION] your last update make the kernel very stable. No freezes. But wake up seems to take a bit more time. And also, still my most hated bugs, the mtp is often not working
[Samsung Galaxy Nexus] mrgnex:
[MENTION=5380162]pattyboi:)[/MENTION] I have a computer with horsepower. How much do I need? I stille have linux :) Pm me if I can help ;)
[Samsung Galaxy Nexus] pattyboi:):
should be able to fix mtp today,my bad :/ & the wake up i can fix too,i think :3

btw has anyone tried booting the no selinux build?
[Samsung Galaxy Nexus] pattyboi:):
probably quad core with atleast 10 gigs of ram,i dunno how much you got running but building a toolchain is very very taxing :/
[Samsung Galaxy Nexus] eternal70:
My personal build always without SELinux. Oh yes and i already fixed the wake up issues. I set the max screen off too low
[Samsung Galaxy Nexus] pattyboi:):
no no,i know it boots,i meant if anyone who couldnt boot at all tried the non-selinux version to see if then they could boot
[Samsung Galaxy Nexus] mrgnex:
I have a 6 core @4.7 GHz and 8 gigs of ram. I am willing to help ;)
[Samsung Galaxy Nexus] pattyboi:):
dammnnn,thats ALOT of horsies :P if your willing,ill look for the instructions for building a toolchain and pm you soon ;) gonna be in physical therapy for a lil,we will talk soon ;)