yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bsmitty83:
Since I've never included a ramdisk , what would be the best base for compatibility ? Im just curious because I thought a lot of ROMs use custom ramdisks that need to be there . If I can make one that works for everything I'd love to simply to remedy all these issues . I have bad luck with ramdisk inclusions .

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pattyboi:):
dont most roms use cm's ramdisk?
[Samsung Galaxy Nexus] michierusama:
Wich kernels don't have ram modification?
[Samsung Galaxy Nexus] pkgnex:
The OP says Illinois is available! ?

... and I know it was there back in the "v5 / v6" days (I haven't been running Dirty-V since the new numbering and re-basing effort started).

I tested all of the ones listed in the OP, and Illinois and Westwood were far and away the best - everything else was a distant 3rd. Illinois seems to generally be faster for me, but when I test, there are days when Westwood is faster. It often works out that Illinois is faster over 3g/4g and Westwood is faster over wifi, but sometimes that inverts, and they are always so close that I don't think one is really significantly better than the other - at least statistically. Cubic, Reno, Veno, etc. were always much, much, slower whenever I tested them.
[Samsung Galaxy Nexus] Sik-1:
I figured they all do at different levels tho, read young padawan
[Samsung Galaxy Nexus] metalspring:
You'll want to use cms ramdisk, they tend to need things other roms don't, but the extra additions they need usually don't effect other roms

Just make sure to keep a tab on cm gerrit to keep it up to date (they love adding things that break any custom ramdisks)
[Samsung Galaxy Nexus] osm0sis:
Agreed. I use CM's then use the latest AOSP charger binary since I hate CM's green percentage overlay in the powered-off charging.

Also, I've put a SmittyV AnyKernel with ramdisk mods together this afternoon, I just need to test it out. :)
[Samsung Galaxy Nexus] lokety:
Brilliant! Finally we are able to use Touch Control to swipe unlock and enjoy Dirty_V kernel.
[Samsung Galaxy Nexus] gohamstergo:
Am I missing something, or is it normal that SmartReflex Control doesn't work on SmittyV?
[Samsung Galaxy Nexus] pattyboi:):
nope. its completely normal (:
[Samsung Galaxy Nexus] gohamstergo:
wtf. I turn it on and its shuts itself back off. And I've already reflashed my ROM and kernel, no change....not sure what else to do. Also, "Dynamic FSYNC" is now only named "FSYNC" hmmm
[Samsung Galaxy Nexus] Nephilim:
SmittyV is Smittys personal test kernel, certain things such as SmartReflex are disabled. Basically SmittyV comes out and if everything is good he releases updated DirtyV and DirtyV SR with all the normal functions. (Hopefully cubic this time)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] gohamstergo:
ohhh ok good. thought i broke something. thanks
[Samsung Galaxy Nexus] Nephilim:
Hey smitty, would you mind including Illinois TCP Congestion in your next DirtyV? Since osm0sis spoke of it I'm now curious.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Check the op and see ;)

I forgot to set fsync off at boot I think , sorry bout that

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gohamstergo:
Nice. Hate to ask, but does DirtyV 2/10 have or not have "touchie touchie?" :P
[Samsung Galaxy Nexus] bsmitty83:
No touchwake

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Op updated 2/10 DirtyV and "-SR

-zram

-3.4 WiFi drivers . native tether still broke till [MENTION=1143630]osmosis[/MENTION] hooks me up with a ramdisk I can tinker with ;)

Hope all works , fsync is on at boot cause I forgot to set it again . oops .

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] DevVorteX:
Is it just me, or the last two builds with DirtyV, not SR, have the interactive governor settings kinda jacked up.

In trickster, I'm seeing go_highspeed_load = 50, and target_loads = 75.

I thought that was a no-no.
[Samsung Galaxy Nexus] pkgnex:
Yep, those are jacked up and should be changed. You're a pretty smart fella, DevVorteX!

BTW, I'm not saying the kernel is built with those values as default (maybe your trickster data is borked or something), but you don't want t_l higher than g_h_l in the interactive settings.

I appreciate your efforts on Shiny, BTW.
[Samsung Galaxy Nexus] milojoseph:
I can never keep up with this kernel...... Jeez thanks..... also thanks.....
[Samsung Galaxy Nexus] AndreiLux:
The point of it is that you have total control over the elements of the interface instead of some random app developer (Trickster for example).
[Samsung Galaxy Nexus] DevVorteX:
Just cleared trickster data/cache, rebooted. Values are the same. Odd.

just trying, like everyone else here, to keep this device chugging along as long as possible. If my data tweaks for shiny helped you, liquids got them, and the last omnimetal before the "official" does too if you want to check those out. Great things still happening for this dated phone. Especially the amazing development of this here kernel

I just wish the thread could slow down a bit, I sometimes have to skip pages to try and keep up! :eek:
[Samsung Galaxy Nexus] Nephilim:
2/10 is running amazing. Trying out Illinois TCP instead of Cubic and do far so good. :)

New wifi drivers are working great as well!

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] juju2011:
Know how you feel why am glad I own 3 phones have taptalk signed in on all of them and keep one on each floor of the house so i can keep up with this thread!!!! Boo yeah Smitty did it again:beer::thumbup:
[Samsung Galaxy Nexus] pkgnex:
-

Nah, I love Shiny. Something about that stock experience just makes me the happiest! I'm one of those many souls who have ridden the toro train from Bugless Beast to Mmuzzy to Shiny.

While your work on Shiny didn't really pertain to me (never had data drops), I know how hard you worked to help out the community, and my hat's off to you.

Fwiw, if you want a good set of interactive tunables, you should check out the work done by the Franco kernel Dev team. In the mean time, just set g_h_l to 95 and t_l to 85. :)
[Samsung Galaxy Nexus] aosp:
Update is running smoother recently some users asked [MENTION=4443334]Grarak[/MENTION] about adding low memory killer elements I was looking into sysctl elements but not sure if these can be added I been having trouble resetting zram do you have any plans to start a thread on xda for this awesome app would love to see import export profile support thanks again for creating Synapse ;)

https://github.com/Grarak/grakernel-tuna/blob/grakernel/drivers/staging/android/lowmemorykiller.c

https://github.com/Grarak/grakernel-tuna/blob/grakernel/kernel/sysctl.c

https://github.com/RomSwitchers/Rom...ter/boot.img-ramdisk/res/synapse/actions/zram
[Samsung Galaxy Nexus] cujo6801:
First try dirtyV 2/10 SR.

Westwood/hyper/sioPlus

230 low/ 1500 high

sent from the DOG pound

---------- Post added at 09:02 PM ---------- Previous post was at 09:00 PM ----------

OK ok

I'm bored....

So sue me

sent from the DOG pound
[Samsung Galaxy Nexus] fracama87:
Everytime smoother!

You're the boss [MENTION=4608636]bsmitty83[/MENTION] :)

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] osm0sis:
Haha I was still working on an AnyKernel ramdisk mod solution for all your governor woes, but everything seems to be working just fine with SmittyV 2.10 and f.Ku as a tweak app.

Hold up, I'll make a DirtyV-SR + ramdisk using the same stuff and you can go from there (not sure how the tethering fix works). :good:

Ahhhhhh I get it now. The app is a blank slate for each kernel dev. That's downright brilliant! Thank you for coming up with such a cool idea, sir! :D

---------- Post added at 01:59 AM ---------- Previous post was at 01:10 AM ----------

Alright [MENTION=4608636]bsmitty83[/MENTION], here are both proofs of concept:

http://d-h.st/users/osm0sis/DirtyV/

:D

Tested and working in the latest CWM & TWRP. The ramdisk one is CM's latest ramdisk + AOSP's latest charger binary. I changed the permissions for interactive and ondemand in init.rc and init.cm.rc from 0660 to 0664. Also got Smitty started on a ramdisk bootscript in /sbin/dvbootscript.sh to match the commits he's got in there for boype's timer_slack and boype's kernel-side oom_adj patches meant to complement my lmkwhitelist script. Threw in native kernel-side init.d support, native SuperSU support, and my version of boype's systemui/launcher renice script while I was at it. ;)

The AnyKernel script is like what I did with f.K before, and smarter than Koush's old AnyKernel, it will modify your current ramdisk with pretty much all the same tweaks as in the boot.img if it doesn't have them already, call it "AnyKernel 1.5".

In the next several weeks I'm going to attempt to streamline that idea into methods like:

# replace_line <file> <line search string> <original line> <replacement line>
replace_line init.rc "cpuctl cpu,timer_slack" "mount cgroup none /dev/cpuctl cpu" "mount cgroup none /dev/cpuctl cpu,timer_slack"

That'll be "AnyKernel 2.0" and then I'll be happy to have that idea out of my head and finished so I can sleep better. :p
[Samsung Galaxy Nexus] piterdemon:
What that doing ? I read few pages back but i still dont understand what is diffrent :)

Wytapatano z Galaxy Nexus CM11
[Samsung Galaxy Nexus] memaro_maro:
tq.. actually love this timer slack patched
[Samsung Galaxy Nexus] osm0sis:
Someone already PM'd me reporting a hung boot on the latest LiquidSmooth with the DirtyV-SR-ramdisk... Can anyone confirm or deny?

Goodbye AnyKernel woes; say hello to ramdisk woes. ;) :p
[Samsung Galaxy Nexus] Hetalk:
You got to up the screen off frequency to around 525 or 700. Try both, and keep whatever works well for you. :good:
[Samsung Galaxy Nexus] Blackcrx:
Wow. That's pretty high. Any reason behind this lag?

How will this min CPU affect the battery drain?
[Samsung Galaxy Nexus] Hetalk:
I guess, you'll have to try it out and find out. :good:

This build is just released, so it's too early for me to call on actual battery usage.

Edit: I dont think they're too high. I mean you just beef it up about 1-2 levels. 325 to 525.
[Samsung Galaxy Nexus] bsmitty83:
This is still one thing i haven't seen out of all the kernels I've made , even ones I don't post . I'm not sure what's delaying the screen from coming on but mine snaps on immediately. Even with screen off min set low .

I honestly get zero lag outta SR3 in any way , no sods for sure , I just don't know I don't use xposed or gbox , or any other things . wish I had an answer , its gotta be an interaction with the ROM /kernel . maybe lockscrren setting factor in , I really don't know . for me its simply flying
[Samsung Galaxy Nexus] Nephilim:
He means you have to up the max screen-off cpu frequency, all that does is allow things that need to run when the screen is off to get a little more cpu power, things like waking the screen, music playback etc. It shouldn't affect your battery in the least. Also, you could try using Hyper governor, that worked for me. Although I am using other custom test settings as well and one of them is max screen-off 525mhz. ;)
[Samsung Galaxy Nexus] Blackcrx:
So I've tried 180-230-350-525-700-920. Still lags on wake up. Haha.
[Samsung Galaxy Nexus] pattyboi:):
for me,changing from interactive to any other gov is what gets rid of the screen lag,havent touched any other setting and my screen comes to life right as the button is pressed.
[Samsung Galaxy Nexus] Nephilim:
I've been having good luck with Hyper, don't know for sure about battery since Smitty's been pushing out updates like a boss but from what I can tell, both performance and battery are pretty damn good. (using my test kernel settings).
[Samsung Galaxy Nexus] pattyboi:):
i completely agree,i get better battery on this than with any other kernel yet.
[Samsung Galaxy Nexus] Nephilim:
Yep, I've noticed excellent screen-on time, especially since I'm on Toro. Idle drain in deep sleep is pretty rad too.
[Samsung Galaxy Nexus] pattyboi:):
toro's need all the love when it comes to battery,mines been getting me through school and the rest of my day even with 4g on with the SR versions,all tho that didnt happen today cause there was enough snow to kill school lol.
[Samsung Galaxy Nexus] Nephilim:
Yea, all the great developers for the Gnex be it Rom or Kernel are what is really helping me out. I can't afford a Nexus 5 quite yet so it's great to have so much productivity still living in this forum. I hope that my G+ Community keeps everyone I talk to here together after we have moved on to new devices. The Gnex forums are among the most chill I've ever been a part of on XDA.
[Samsung Galaxy Nexus] Culex316:
Awesome kernel! Does anyone know which touch control module works with this kernel? I've tried stock and CM11 but they both freeze up. I know boype's kernel somehow worked with the CM11 kernel... Otherwise great work!! I really appreciate you keeping my Gnex alive.
[Samsung Galaxy Nexus] pattyboi:):
i joined XDA specifically because of my Gnex and the community behind it,i bought my gnex as a replacement for my dx2 and started looking into roms/kernels and was just touched by how nice people were and how much people really do help eachother on the forums,i cant afford a high end phone and the dev community is what has kept me going until i can,i couldnt thank the community and devs enough even if i had millions of dollars to give them.
[Samsung Galaxy Nexus] irland2bite:
This score (with ur latest SR2) almost kill myself. You, Mr. Brian Smith, are really made my day (not in a gay way) :). Thanks for your hard work. Awesome !
[Samsung Galaxy Nexus] juju2011:
Everything works great my phone just doesn't go into deep sleep :(

---------- Post added at 08:39 PM ---------- Previous post was at 08:33 PM ----------

Oh nvm it back now
[Samsung Galaxy Nexus] Blackcrx:
Patty: you're right. Changed to hyper, dyninteractive and both are fine. So problem lies with interactive governor.

Smitty: running slim 2.4, but as mentioned the problem was with interactive. Awesome kernel man. Thanks a lot.
[Samsung Galaxy Nexus] Nephilim:
You guys think that my SOD issues and unresponsive screen freezes may be due to a low battery and hot device? I've ran my battery down to practically nothing trying to tweak things and get everything smoothly and I thought my SOD's may be due to Vanir. So I just tried LiquidSmooth with DirtyV-SR-v3 on about 22% battery and a pretty hot device, I got sod's right away, then after booting I got complete unresponsive screen freezes while the device was still awake. I literally watched the screen fade and then turn off via crt animation but touching it did absolutely nothing, it was completely unresponsive.
[Samsung Galaxy Nexus] bsmitty83:
Not sure but if you get another sod and your by your computer , pull a dmsg ,or kmsg , I can't remember off hand which . but I'll revert some interactive commits for stability . im keeping them in my personal git branch though , they work great on my phone for whatever reason
[Samsung Galaxy Nexus] Nephilim:
I got an SOD with Mpokang too. It looks like my device was possibly overheating and that coupled with the low battery most likely caused my issue. Letting my phone relax for a few and then I'm going to do a clean install of the 1/20 Vanir with DirtyV v3.
[Samsung Galaxy Nexus] milojoseph:
Ok...... someone told me to not set stylc on boot. I did and my phone is too hot to the touch. I cleared rom flash new rom still hot that it reboot. Im using nephilim setting can someone help please.
[Samsung Galaxy Nexus] memaro_maro:
dirty v SR wt ramdisk ~ work fine for me. slimkat
[Samsung Galaxy Nexus] milojoseph:
?????? Im using the latest version with nephilim settings. But my phone is toooooo hot
[Samsung Galaxy Nexus] Charmacas:
Yeah it booted up just fine on SlimKat but the values still not stick. For example "target load" or "Max freq".

I did not wipe cache and Dalvik. I did not see the necessity. There isn't one, is it?

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] memaro_maro:
try re- flash your rom boot.img (kernel), after boot, flash that dirty v once more.

or try the osmosis ramdisk version of dirty v:

[/COLOR]Alright [MENTION=4608636]bsmitty83[/MENTION], here are both proofs of concept:

http://d-h.st/users/osm0sis/DirtyV/
[Samsung Galaxy Nexus] milojoseph:
I tried the boot.img with clean install. Disabled systlc. And osmosis as well. :(
[Samsung Galaxy Nexus] osm0sis:
No need to wipe anything for a kernel. target_loads sticks perfectly well here on the ramdisk version, and to clarify, that's the only one on which you should expect it to.

If that's what you're using then there must be some app limitations going on here because it works just fine in f.Ku.

Edit: There is something weird with the color multipliers though.. The permissions look fine but even as root I can't write to the file. Does Smitty have them hardcoded or something?
[Samsung Galaxy Nexus] memaro_maro:
after run this script in terminal. it will sticked

su

# Governor

echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo 15000 > /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay

echo 0 > /sys/devices/system/cpu/cpufreq/interactive/boost

echo 80000 > /sys/devices/system/cpu/cpufreq/interactive/boostpulse_duration

echo 95 > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load

echo 729600 > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq

echo 45000 > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time

echo 85 > /sys/devices/system/cpu/cpufreq/interactive/target_loads

echo 15000 > /sys/devices/system/cpu/cpufreq/interactive/timer_rate

echo 80000 > /sys/devices/system/cpu/cpufreq/interactive/timer_slack

# edit the script follow your own setting
[Samsung Galaxy Nexus] citizeninsane89:
Slimkat RC3 working fine
[Samsung Galaxy Nexus] demlv:
I read recently that some kernels don't play nice with the fstrim function built into the newer versions of Android. So is there a way to tell whether/when the trim function is happening? A log of some sort, perhaps?
[Samsung Galaxy Nexus] neetee:
Touch Wake option seems to be removed on DirtyV 2.10 ???
[Samsung Galaxy Nexus] büscher:
yes, but now you can use Touch Control. You can't have both...
[Samsung Galaxy Nexus] qtoo941:
View attachment 2572670 should i change anything in my interactive values ?
[Samsung Galaxy Nexus] pianistaPL:
Attach image again.
[Samsung Galaxy Nexus] scarcry:
Kernel: [MENTION=4544860]osm0sis[/MENTION] modified DirtyV-SR 2/10 with ZRAM

Kernel settings by [MENTION=2853378]Nephilim[/MENTION] applied using trickstermod donation version.

ROM: unofficial 01/25 LiquidSmooth for maguro by [MENTION=2267583]nasty007[/MENTION]

After taking a nandroid I finally flashed latest CWM touch 6.0.4.7 official, flashed your new kernel and rebooted.

After successful reboot I cleared data + cache for TricksterMod and rebooted again.

After reboot I reapplied all of [MENTION=2853378]Nephilim[/MENTION]'s settings except for the UV saving his settings as a new profile (nephilim) and ticked Kernel Settings on boot and enabled ZRAM and rebooted once more.

After reboot, all settings stuck except for target_loads (profile unnamed was showing in TricksterMod instead of nephilim).

All this has only been 30 minutes ago but phone feels very snappy so far.

HTH
[Samsung Galaxy Nexus] metalspring:
Do the latest dirtyv versions have anything the smittyv version doesn't?
[Samsung Galaxy Nexus] qtoo941:
Does somebody have problem with wi-fi? I cannot connect to my wi-fi. My net signal is 100% full and when i try to connect my signal to phone is dropping to lowest level and cannot connect. Flashed kernel via cleaning just cache and dalvik over my old 2/8 kernel.
[Samsung Galaxy Nexus] memaro_maro:
maybe your baseband (radio.img) not updated. or maybe your rom or driver issues... wifi just fine with dirty v.
[Samsung Galaxy Nexus] GilGameshn1:
Dear [MENTION=4608636]bsmitty83[/MENTION] thanks for your hard work . I have a very good experience with fiops/1024/hyper . also the WiFi working great . buttery GNex around . thanks to you and other contributors .

Sent From My Nexus Prime
[Samsung Galaxy Nexus] milojoseph:
I guess no one can help me with my over heating problem
[Samsung Galaxy Nexus] GilGameshn1:
If no app worked in background could be some ROM complications . clean install ROM/gapps . then flash kernel . you can see what app keep awake device in Settings/Battery . could be help .

Sent From My Nexus Prime
[Samsung Galaxy Nexus] LibertyMonger:
I lost Wi-fi as well
[Samsung Galaxy Nexus] metalspring:
What type of password authentication do you have on your wifi or is it open, etc?

[MENTION=1533050]bsmitty[/MENTION], do the new wifi drivers you use also need this commit too?

https://github.com/anarkia1976/AK-tuna/commit/0f91ce3ebaf3f7325e3d7e91a9494df6fa61ef0d

Just wondering if that might help with some losing wifi
[Samsung Galaxy Nexus] memaro_maro:
just restore your nandroid backup, if dont have any solutions ????

* just 5 minutes process~ no need to seek any solutions
[Samsung Galaxy Nexus] pkgnex:
Aren't the 3.4 wifi drivers the ones that don't work with WEP?

I never heard of a commit that successfully fixed that.
[Samsung Galaxy Nexus] DevVorteX:
Ha ha, quoting myself always seems funny to me.

Turns out it was trickster trickery. I flashed a different kernel just to test, and the interactive settings where exactly the same jacked up setting I'd seen with DirtyV lately. So I'm trying to figure that out since my phones performance has gone down since I noticed.
[Samsung Galaxy Nexus] juju2011:
Lol and with it my settings don't stick between kernel updates even tho set at boot is on but no big saved settings just apply profiles at boot now when they don't stick. Using the anykernel osmo made will try sr with ram disk when I get out of bed can I just flash it like normal or do I have to dirtyflash it with ROM because of ramdisk??
[Samsung Galaxy Nexus] brymaster5000:
Any chance there is an init.d file telling you one thing and another telling you another...sometimes I find multiples never get deleted when flashing different kernels. Should be in system/etc/init.d

Ps: [MENTION=4608636]bsmitty83[/MENTION] looks like you guys have a good fun forum. The HTC one is a bit crazy and definitely some drama...not like the inc2 days...but it seems you have that here!
[Samsung Galaxy Nexus] juju2011:
Did u mess with Iva voltages ? Mine over heated like crazy when I fiddled with them and don't use fast charge if you plugged into wall that also made my phone over heat.. But mbq is right need to give more info and try a get a log with your phone running hot
[Samsung Galaxy Nexus] metalspring:
Not to be off topic but [MENTION=4244313]MBQ_[/MENTION] have you ever checked out viper 4android app? Just curious what an actual musician thinks about it lol

Also about to flash my custom compiled dirtyv-sr (mostly just slimmed down), hopefully no WiFi issues, but if there are then I'll report back with a dmesg or logcat
[Samsung Galaxy Nexus] jhonnyx:
My best guess is:

1- do a backup of the phone

2- flash stock firmware (4.3 if possible)

3- flash a recovery (CWM, TWRP, etc)

4- flash some stock rom (PA, CM, etc)

5- configure it and when you finish go to step 6

6- Nandroid backup: DO IT

7- flash smitty's kernel. if phone overheats, restore backup
[Samsung Galaxy Nexus] pmbabu:
Actually, WEP is dropped in 3.4. So, no fix is needed AFAIK. People, just switch to WPA2 as long as the router is in your control ;)
[Samsung Galaxy Nexus] qtoo941:
[MENTION=4608636]bsmitty83[/MENTION] must change this drivers in my honest opinion... no chance to connect to WEP :X
[Samsung Galaxy Nexus] Hetalk:
WEP is a flawed authentication system and has been deprecated. See link

Anyone really serious about security, must change from wep to wpa2. JMHO
[Samsung Galaxy Nexus] chongns:
Yeap, or do a zip for it to revert the driver, like ak kernel previously.

Sent from my Galaxy Nexus