yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] uconnpat:
I know I'm missing something but don't know what....

I've tried to flash the newest kernel as well as all three of the 8.30 versions and every time the device doesn't get past the Google (unlocked) screen.

What am I missing? I'm on aokp 4.2.2? Do I need to do the ak installer?
[Samsung Galaxy Nexus] pvkiniyan95:
sry buddy i dont use a gnex anymore so lost track of the features, i dont think active display was implemented at that time

btw here is the link check it urself :good:

http://www.emccann.net/nuclearmistake/VanirAOSPRelease/maguro/
[Samsung Galaxy Nexus] uconnpat:
would anyone be willing to walk me through installing this on my gnex with aokp 4.2.2 on it? Please and thanks
[Samsung Galaxy Nexus] bsmitty83:
should be as simple as downloading whichever version you want to use , and flashing it via recovery

the old version links are a zip file containing all of the old version zips , so you have to un-zip that to access all the old versions , but other than that , should be a straightfoward install.

what specifically were you having trouble with ? I'm more than willing to help , just need a little more on what you need help with is all
[Samsung Galaxy Nexus] uconnpat:
I downloaded all 3 versions of the 8.30 build and tried to flash with twrp and all three got me to the Google screen (the process of flashing didn't have any problems) and then wouldn't go any further... I waited about 5-10 minutes and then did a battery pull and then flashed the golden kernel to restore the phone back to the original
[Samsung Galaxy Nexus] uconnpat:
I'm gonna give it a whirl with cwm because twrp is not getting me anywhere
[Samsung Galaxy Nexus] bsmitty83:
I doubt the recovery is the issue ,but you can certainly try .

The kernel is 4.4 based , but it should be compatible with 4.2 and 4.3 Roms . if you still can't get past the google lock screen , try fastbooting just the zimage from the .zip .

If you still can't get anything to work , I'll flash a 4.2 ROM on my gnex tomorrow and see what's up . what ROM are you running BTW?
[Samsung Galaxy Nexus] uconnpat:
that may be the problem.... When I open your newest kernel zip I see a zimage file but when I open the older kernel zip and then the 8.30 file all I see is a boot.img file
[Samsung Galaxy Nexus] uconnpat:
I'm running aokp 4.2.2
[Samsung Galaxy Nexus] bsmitty83:
installed on the first try for me , just a factory reset , rom install, gapps install , then the kernel

I would install a 4.3 rom , 4.2 is pretty old . theres really no reason to stay on it
[Samsung Galaxy Nexus] uconnpat:
thanks so much for trying to help... i can't get it to work on 4.2 and I don't want to go to 4.3 because of the data to wifi handoff problems that are on any rom after 4.2 that I've tested and I've tested a lot
[Samsung Galaxy Nexus] xxSAKISxx:
after really long long time i decide to test the final version of Dirty V kernel. So far is awesome but its normal that in trickster i don't see the option to choose how many cores will work? (i don't remember the exact option)
[Samsung Galaxy Nexus] bsmitty83:
If your talking about multicore power saving , I removed it as it does not really do much good , so yes its normal . if your going to run the final version, I recommend disabling zram , it will cause a reboot after some time . other than the occasional reboot , the kernel ran great IMHO
[Samsung Galaxy Nexus] emanuele1986:
which folder i can convert to f2fs with this kernel?
[Samsung Galaxy Nexus] nickdc986:
SmittyV = NormalRAM, my personal build options

DirtyV-SR = SuperRAM

DirtyV = Bigmem

which one is the best with jb 4.3 stock?
[Samsung Galaxy Nexus] bsmitty83:
So apparently the website that I used for hosting all the kernels and recoveries for dirtyV expired yesterday , and since the site was not owned by me , just a gracious user let me use the site to host , I never got a warning that it was expiring soon . I didn't have them saved anywhere else , so I pretty much lost all of the old versions .

I'll clone my source on github and recompile some builds eventually . but if anyone ever downloaded the 3 zips that I had posted that contained all of the old versions and still has them , please drop me a link so I can download them myself and re-add them to the op
[Samsung Galaxy Nexus] SirOch:
Hi,

[MENTION=4608636]bsmitty83[/MENTION]

I have the 3 zips.

I send you a mp soon with the links :)

Envoyé de mon Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
thank you very much , I'll make sure to archive them properly this time :o
[Samsung Galaxy Nexus] SirOch:
No problems.

You have an mp :)

Envoyé de mon Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
and you have my gratitude :)

I'll try to update this thread soon with new links for everything as soon as my wife and two kids let me lol
[Samsung Galaxy Nexus] Rushead:
"So you're saying there's a chance!" (not holding breath) [emoji6]
[Samsung Galaxy Nexus] bruor:
If you can post a link or even share the builds via google drive I'd appreciate it greatly.
[Samsung Galaxy Nexus] wavedashdoc:
I'm also i need of the f2s TWRP toro recovery. I flashed a maguro one (2.7.0.0) from somewhere else by mistake, took me awhile just to get back to 2.8.6.0 TWRP toro :/ but since it doesn't support f2s it says I have 0mb of space lol.

does anyone have links to these?
[Samsung Galaxy Nexus] bsmitty83:
Check the zmod thread , I believe there is a current f2fs compatible twrp linked .
[Samsung Galaxy Nexus] wavedashdoc:
I searched, nothing there [MENTION=4608636]bsmitty83[/MENTION] I've searched for the last hour now, I might just reflash the mugaro one and format back to EXT4.
[Samsung Galaxy Nexus] bsmitty83:
Check the downloads section from a web browser , you can use the maguro version if your on toro , it will work fine
[Samsung Galaxy Nexus] wavedashdoc:
Edit: found working one fml-twrp-2.7.1.0-20140705-toro.img from FML ROM OP

When I try to flash a toro ROM (CM-12.1 unofficial with F2s) with the maguro twrp it says "this file is for a toro device. You're device is a maguro. Since I wiped my device clean when switching to f2s I don't have any files on there, and I haven't been able to push anything successfully while using this mugaro twrp version. I need a toro f2s recovery.
[Samsung Galaxy Nexus] bsmitty83:
Yea I forgot to say you just have to open the ROM zip and delete the build check from the top of the updater script , but a toro twrp will work no worries lol .
[Samsung Galaxy Nexus] quickdraw86:
Zzpianoman just posted TWRP 2.8.4.0 in his toro ROM thread, it works with F2FS

http://xdaforums.com/showthread.php?p=60663541
[Samsung Galaxy Nexus] 3anagJIo:
link to the dirty V SR died, put more please.....

thanks
[Samsung Galaxy Nexus] kerpert:
I have error also with smittyV
[Samsung Galaxy Nexus] ALBIEL:
http://xdaforums.com/devdb/project/?id=6110#downloads here:)
[Samsung Galaxy Nexus] l2azoredge:
Hi,

i started using this kernel a week back, im using it on stock 4.3 and using kernel auditor to choose the settings.

My issue is with wifi not staying on during sleep( ive tried "always on" from wifi advanced settings and uncheck minimise battery usage when on wifi. is it something with governer(im using hotplug)? this is troubling me a lot as all the messages are missed. same with data connection, it almost gives me a dead speed whereas im using a same company sim on a moto e and it works fine. data connection goes off in sleep.
[Samsung Galaxy Nexus] ashclepdia:
I'm not CERTAIN on this, but I recall before, "Back in the day", the Gnex didnt always behave great with hotplug governors. I haven't been staying on TOP of development lately so I'm sure it could've been an issue ironed out at some point. I just remember I had always avoided hotplug governors, they had always caused my gnex to have issues of some type. it is possible that it is totally unrelated to that, but that would be an easy thing to try changing at first, just in case.
[Samsung Galaxy Nexus] Nephilim:
Hotplug is not recommended for Gnex at all, leads to freezing, soft reboots and bootloops.
[Samsung Galaxy Nexus] CoDe LaZaRuS:
Which one/version is rock stable. I'm handing my Gnex to my mom and have moved onto the G4 ?
[Samsung Galaxy Nexus] bsmitty83:
Franco kernel or fancy kernel if your handing the device off to mom . don't think she wants to be messing with dirtyV [emoji6] . really I wouldn't consider any of my kernels rock stable . I'd flash a stock kernel or another developers kernel that isn't so experimental
[Samsung Galaxy Nexus] CoDe LaZaRuS:
I'm using vanir and just flashed fancy kernel on top lets see how well they work together ?

Btw which rom + kernel combo do you reccomend also I wanted to see what the big deal about the art enhancements in vanir was about but kitkat xposed dosent support art ?

Any reccomendations captain xD
[Samsung Galaxy Nexus] traco1:
I noticed this kernel is listed as "tuna " build. Can I flash with my verizon Gnex "toro" I515?

Thanks
[Samsung Galaxy Nexus] Nephilim:
Tuna is the codename for all variants of the Galaxy Nexus so this kernel can be flashed on all Galaxy Nexus versions.
[Samsung Galaxy Nexus] traco1:
Kernel

Never mind I did some more research and answered my own question.
[Samsung Galaxy Nexus] mdki1996:
Maybe nooby question: is it possible to update ddk driver from 1.8 to 1.9 in kernel?
[Samsung Galaxy Nexus] bsmitty83:
Yes but without the new user space libs the updated driver in kernel won't work . it may be possible to replace all the necessary libs with anykernel2 , I might try if I get some time .
[Samsung Galaxy Nexus] Pee_kee:
What is difference between SR-Ak2 and Ak2. Am on maguro, which one should i choose.?
[Samsung Galaxy Nexus] David 617:
Wow, talk about a Zombie thread...
[Samsung Galaxy Nexus] Pee_kee:
Pardon me. :(
[Samsung Galaxy Nexus] bamtan2:
Nothing wrong with posting :) Old software is still good software! In fact, I wish we had recorded what the best 4.2/4.3/4.4 builds of ROMs and kernels were, and then stickied them at the top of the forum. That way you wouldn't need to go searching.

I used to run AOKP 4.2 and it was great! :) And I run CM 12.1 now and it works great too. A lot of people are running CM 13 and say it's good. That's all I can help you with. =)
[Samsung Galaxy Nexus] rahimali:
To quote [MENTION=4278473]Hetalk[/MENTION] from the second post on the first page,
[Samsung Galaxy Nexus] PicoDeGiao:
Interactive does seem to work better now. Thank you!
[Samsung Galaxy Nexus] KJW979:
I know only been running short time with v4 but this one so far seems to be the best put out so far. Everything opening and closing quickly. Give it more time to settle in and see how it goes. Thanks for keeping up and improving your kernels. Much appreciated.
[Samsung Galaxy Nexus] fracama87:
New default voltage are good too! No need to uv them I've tried old default values and new with smartreflex on and are used the same voltage :)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Nephilim:
v4 SR is simply incredible. Smoothest so far, working absolutely amazing with my settings!

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] fracama87:
Did you maybe has also applied uv settings of Nephilim?

Some time ago it's happened to me few times I had a value of vmmc too low! In some cases could be a cause ;)

Thanks smitty for your great works, v4 is amazing ;)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] chainrulez:
Great work smitty. Using your kernel from the very first day when you posted at Vanir thread. New v4 is so much smooth plus zero lag. Thanks for your great work dude ... :highfive:
[Samsung Galaxy Nexus] sagara.sandaru:
Im gonna flash Dirty_V3 SR version. Im currently on Dirty_V Linaro version. Should I do a complete wipe bfore flash it? And does video apps like Skype works on SR version?
[Samsung Galaxy Nexus] bpark32:
Link? Please n thanks!

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] garyngkt:
So far so good with SR V3 on CM11
[Samsung Galaxy Nexus] cujo6801:
Guys, anyone using the unofficial 1/20 or the official 1/25 build of Liquid flash this zip in order to fix issues with ART causing SOD's, It is a revert of CM Bionic back to 1/17, something in the updated Bionic (libc.so) caused these problems with ART and this is the temporary solution for those that would like to use ART successfully for now.

Credit to klobkelosh for finding this fix.

http://d-h.st/SQO

sent from the DOG pound
[Samsung Galaxy Nexus] oubeichen:
I cherry-picked some commits from mpokang kernel to reclaim some more ram of dirtyv.

https://github.com/oubeichen/DirtyV_tuna/commit/be88534edbf6fa7a67eb5070b5b716272b6c6625

https://github.com/oubeichen/DirtyV_tuna/commit/588ee3b6007e6107878b67d5b1821eec61a19d40

https://github.com/oubeichen/DirtyV_tuna/commit/6300221a8c1c2c42e3a452a37e17769b2221625b

Seems no issues.

But I dont have much acknowledge of kernel and I was wondering if they could have any side effect.
[Samsung Galaxy Nexus] metalspring:
thats why bsmitty has the dirtyv-sr branch, its the super ram branch with more free ram ;)
[Samsung Galaxy Nexus] killersloth:
Definitely my new goto kernel.
[Samsung Galaxy Nexus] garyngkt:
Fuah v4 is out already, flashing time :victory:
[Samsung Galaxy Nexus] Vekhez:
I know that this may be a Moto G thing, but the Moto G has the same amount of RAM as us, but it has 882MB of RAM available, is there anything that we can do to make it this high, or lolnope.
[Samsung Galaxy Nexus] sagara.sandaru:
This is my MPU voltages if anyone interested.. DirtyV4 Linaro. :cool:
[Samsung Galaxy Nexus] Charmacas:
Definitely a good question. But I am not able to answer that.

By the way we should start to mess around more with the Minfree settings. Look into my Trickster settings. There you can see my actual setting which I found somewhere in the forum here. And my phone actually flies with this. And I did not upgrade to DirtyV-SR4 yet and underclocked to 1036. ;)

Oh my last edit in my settings got lost... One moment... Done

And here's the link to the original author: http://xdaforums.com/showthread.php?p=49889812

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] Culex316:
Not (easily) possible with the Galaxy Nexus. Mpokang himself said in his thread that the only way to get close to 900MB of free RAM is to leave out media playback and camera support entirely (this phone uses some system RAM for media playback , GPU and camera/recording, this is why 1080p video is broken for super RAM kernels, that extra free RAM was originally allocated for 1080p video recording /buffering )
[Samsung Galaxy Nexus] oubeichen:
dirtyv-sr dont have those commits either
[Samsung Galaxy Nexus] Charmacas:
Smitty could you please configure your kernel in the standard configuration that FSYNC is always activated? I would appreciate that.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] Nephilim:
Dude, this has already been mentioned twice! Turn dynamic fsync off and fsync will be completely on.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
Gotta say, DirtyV-SR V4 and my latest omnimetal build is absolutely amazing, the fastest my phone has felt in a long time :)
[Samsung Galaxy Nexus] Charmacas:
Duty Dude, I know that. But I can explain it also in detail:

Please turn Dynamic FSYNC off and FSYNC on by default. ?

So safety first would be nice.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] ashclepdia:
i wish i knew how to build a kernel...i was always interested in just seeing how the device runs even if i cannot use my camera at all.

only thing i might want is music playback. but i'd still be interested in just at least TRYING out a "no playback/no recording" kinda kernel.

i cant be the only one interested in just SEEING a 900mb userspace ram. hahahaha

i need to quit procrastinating and look into this whole kernel building thing. always wanted to hardcode in my settings too for my own builds :D

EDIT:

not trying to start a war here, but am i the only one who just isnt a fan of dynamic fsync? i dont really have a "good" explanation as to why, but i have some kinda hatred towards it. this is NOT a complaint lol(i rarely even mess with fsync settings no matter what it is as default only because i've never really noticed any difference when i tested it before.)
[Samsung Galaxy Nexus] xxSAKISxx:
i remember when I flash mpokang big mem kernel it remove 1080p from camera settings. dirtyv sr dont do that?

"If you want to live you must die first"

" Powered from my 4.4.2 KitKat Galaxy Nexus "
[Samsung Galaxy Nexus] drmxmyt:
thats true but you should manually do it every time that you rebooted. on trickster, if you uc'd(or a bad governor/bad frequencies) and your trickster sets it on boot, it set it dynamic fsyinc off and your uc/other settings on the same time after a reboot and if you have a bad setting, data loss is happens even before you set your dynamicfysinc off. i think dynamic fysinc should be off by default too. (i hope i could tell my thoughts, english is not my native lang.)
[Samsung Galaxy Nexus] ashclepdia:
dirtyV bigmem 1080p works.

superram 1080p DOESNT work.

says it right next to the kernel download links in OP(and in second post FAQ)

;D
[Samsung Galaxy Nexus] BestBrd:
Sorry but,ATM,what are the main differences between dirty and smitty v4?
[Samsung Galaxy Nexus] ashclepdia:
isnt it just mainly the same thing except it is smitty personal build, has less gov/schedulers/etc.. that he doesnt use?

thats what post 2 says anyways.
[Samsung Galaxy Nexus] scarcry:
I concur :) I've always loved my gnex but it has never felt this good!

I'm also impressed with the battery life I'm getting.

considering the fact I'm still on the original 1750 mAh battery when I bought my maguro in 2012 I find that truly impressive.

Thanks so much [MENTION=4608636]bsmitty83[/MENTION] for the kernel, [MENTION=2853378]Nephilim[/MENTION] for your tweaked settings and all others for the valuable input.

Tapatalked from my maguro running vanirAOSP nightlies
[Samsung Galaxy Nexus] büscher:
But I benchmark my phone to see what it is capable of and 1.6GHz seems to be the highest stable frequency for my phone.

It's a great score imho, also with 1.5GHz (my daily setting) I'm getting around 14'000 points
[Samsung Galaxy Nexus] bsmitty83:
No , just don't choose 1080 even thought it still a choice
[Samsung Galaxy Nexus] bsmitty83:
Commit 1and 3 make the kernel not boot and number 2 is in my kernel.
[Samsung Galaxy Nexus] Shambola:
Just for info: no more wake up issue with Interactive using V4 and Neph's settings (min 180)

\m/
[Samsung Galaxy Nexus] scarcry:
Another confirmation here. Hasn't failed waking up on me once :)

Tapatalked from my maguro running vanirAOSP nightlies
[Samsung Galaxy Nexus] boki2911:
Can you share these settings with Us :laugh:

14000 impressive
[Samsung Galaxy Nexus] büscher:
Sure, my daily driver settings (with 13976 points) are:

TCP: Westwood

Minfree (credits [MENTION=3777325]wavedashdoc[/MENTION])

Foreground App: 10

Visible App: 20

Secondary Server: 100

Hidden app: 120

Content Provider: 95

Empty App: 195

RABS: 1280

Scheduler: sioplus (on my phone sioplus is almost twice as fast as noop)

Min: 525

Max: 1500

Max Screen Off: 700 (because of Poweramp)

Min Screen On: 525 (because I can't change it to any lower, it jumps back)

Governor: Interactive (it was on performance as I ran antutu)

CAB: off

FFC: off

MPS: off

HPS: off

HVB: 2

DFSYNC: off

GPU: 512

Nothing undervolted for now

I'm also on ART (ROM: CM-REMIX)

For better battery results:

I uninstalled a lot of unnecessary system apps and use greenify

I installed wifi-matic that disables data on wifi and disables wifi if I'm not at a location with a known wifi.

With all these settings I get a antiutu score around 14000 idle drain 1.2 - 1.4%/h and a normal use-drain from about 3.5%/h
[Samsung Galaxy Nexus] Nemed:
SR4 is blazing fast, thanks dude!

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] boki2911:
[MENTION=3317173]büscher[/MENTION] What kernel version you are using
[Samsung Galaxy Nexus] xxSAKISxx:
sry guys i flash the v4 sr (i think) hehe. is thst the one becuse i think is the same in description with v3 sr

"If you want to live you must die first"

" Powered from my 4.4.2 KitKat Galaxy Nexus "
[Samsung Galaxy Nexus] oubeichen:
I dont have any problem with the first and the second commit in V2 source.

The third hasnt been tested yet because i messed up config files.Maybe just disable the swap is the same.
[Samsung Galaxy Nexus] büscher:
the above result was with SR V4
[Samsung Galaxy Nexus] bsmitty83:
Hotplug governor also works now on v4
[Samsung Galaxy Nexus] eternal70:
Hey man, is the conservative governor have early suspend ?
[Samsung Galaxy Nexus] migadeath:
Thank you very much man! I'll test it ASAP.

What do you thing about adding more freq. steps under 1200MHz for e.g. every 150MHz? Bad idea? THX anyway!
[Samsung Galaxy Nexus] bluerez79:
No reboots with it?:thumbup:
[Samsung Galaxy Nexus] bluerez79:
^^ great news. Thanks
[Samsung Galaxy Nexus] Hetalk:
Linaro SRv4 : No more screen unlock delay on interactive. Awesome job [MENTION=346208]smitty[/MENTION]83:good:

Edit: I'm almost at the end of my battery cycle with sr3 and sr4 with interactive. Will be testing a hotplug gov next.
[Samsung Galaxy Nexus] migadeath:
Seems OK for me. No probs last 10 mins form boot. Keep on testing...
[Samsung Galaxy Nexus] b4u2:
V4 rocks! No problems here with Neph settings.
[Samsung Galaxy Nexus] bluerez79:
Same here. Not quite as snappy as interactive but I like the idea of it so am going to keep trying as well
[Samsung Galaxy Nexus] büscher:
Not for me, I still have to press the power button twice sometimes and have a slight lag of around one second (but very rarely)
[Samsung Galaxy Nexus] migadeath:
On SGS2 is every governor hot-plugging second core in low usage scenarios but this may bu due different HW implementation. Nevermind I'll do some testing to see if it is worth or not in battery terms.

---------- Post added at 03:12 PM ---------- Previous post was at 02:55 PM ----------

If I set min. on screen frq. 350MHz the second core is not hot-plugging and stays on 350 on idle, can you confirm it too? THX!
[Samsung Galaxy Nexus] bluerez79:
I set min to 230 MHz with sakuactive and according to trickster core 2 does go off line
[Samsung Galaxy Nexus] migadeath:
Yes it works with 230, but not with 350 for me with hotplug governor. For you?
[Samsung Galaxy Nexus] Nephilim:
I requested dynamic fsync for a reason, because I dont want fsync fully on, if you do then you can turn dynamic fsync off, I prefer dynamic fsync as an option over fsync because it is safer no matter which way its set since at the very least its always on when the screens off. Now if you are requesting dynamic fsync be set to off by default, I believe it already is. I just turn it on myself.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Hetalk:
Lol. You guys are going in circles.:laugh:
[MENTION=2288033]Charmacas[/MENTION] wants [MENTION=4608636]bsmitty83[/MENTION] to take the safe approach of turning off "dynamic fsync" as a kernel default. So, that fsync may stay on, as a safety feature. Whoever wants dynamic fsync (like me) for better performance can turn it on using trickster.
[Samsung Galaxy Nexus] piterdemon:
I see Im only one with suspend on interactive on v4

Wytapatano z Galaxy Nexus CM 11
[Samsung Galaxy Nexus] Charmacas:
I repeat because it seems that I am not saying it the right way: I want one of the following:

Dynamic FSYNC turned off by default OR

FSYNC turned on by default

I hope you understand this now. ;)
[Samsung Galaxy Nexus] migadeath:
+1 ...yesterday I've to restore my nandiod backup due crash ( my fault - device behint its linit :) and following bootloop with dynamic fsync ON. When would all my settings pilled out than I'll enable dynamic fsync.
[Samsung Galaxy Nexus] bluerez79:
it works on 350 for me with hotplug. min and min screen on have to be at 350 for me. if i put to 230min and 350 min screen on then core two won't go off line but both at 350 core 2 will go off line.
[Samsung Galaxy Nexus] migadeath:
Thanx! Same for me! I was not sure that I've messed something again in settings. ;)

Is this desired behavior?