yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
Shouldn't be sysctl or the power.tuna.so HAL since those are disabled now, so it must be some app conflict you guys have got going on.

I have no problems here on ShinyROM and using franco.Kernel updater to change my max.

P.S. Testing out the updated ramdisk with some newer SGS3 init binaries I pulled from [MENTION=4196889]DerTeufel1980[/MENTION]'s Github:

https://github.com/DerTeufel/androi...2/tree/new_dualboot/ramdisks/i9300-combo/roms

Hopefully one of these makes Smitty's initlogo work. :D
[Samsung Galaxy Nexus] DevVorteX:
I'm on shiny rom also. Only seems to reset on a reboot, trickster is setting everything else on boot. I don't have anything in init.d. It's not a big deal, just an oddity. I only started noticing around the 2/14 kernel...(I think)
[Samsung Galaxy Nexus] Atento:
Updated from 02142014 to 02172014 DirtV and I lost almost 1000 points on Antutu with the same settings (neph one). Is there any reason for this?
[Samsung Galaxy Nexus] Nephilim:
? If anything I gained at least 100 to 300 points.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] BestBrd:
I'm facing sod's and freezes with the two lasts dirty v...and when i do the battery pull i have to set again anything on trickster!!!:mad::mad::mad::banghead::banghead::banghead:

P.s.: i sue neph's settings
[Samsung Galaxy Nexus] Atento:
Rebooted I run Antutu again. Same result. Going back to the older version.
[Samsung Galaxy Nexus] GilGameshn1:
You did something wrong ... I have no problem so far . please clean dalvik/cache .

Sent From My GNex
[Samsung Galaxy Nexus] BestBrd:
Already done(i always clean dalvick/cache)..
[Samsung Galaxy Nexus] büscher:
Use init.d scripts so you dont have to use trickster. and don't undervolt - freezes and sod's mostly happen because of undervolting.
[Samsung Galaxy Nexus] Punkiderma:
Are you on Slim Kat like me? I'm reading something about this problem on Slim Rom thread

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] DevVorteX:
Nope, shiny. Just checked again, no reboot, and high frequency is back to default 12000? Odd indeed
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION] Hmm so none of the newer SGS3 init binaries (Sammy, Omni or CM11) showed a bootlogo. Not even the old one from ak's ramdisk worked (well.. it booted - no logo - but broke other things). Are you sure it's added correctly?
[Samsung Galaxy Nexus] inmanster:
I have to turn on Frequency Lock in Trickster Mod to get it to stick. It reverts to stock when either going into or coming out of deep sleep. I run Shiny 90% of the time but I had this happen on omniMetal and Liquid Smooth last week. I thought it may be app related so I deleting F.KU and Performance Control without any change. I may delete Trickster and see if it sticks using F.KU.

---

On a side note, I love this thread. I read a lot and have learned a lot. Great bunch of guys here. Thanks Smitty for your work and bringing this all together and for everyone helping out.
[Samsung Galaxy Nexus] bsmitty83:
afaik . i got the same results ,,,,,,,,
[Samsung Galaxy Nexus] osm0sis:
Weird. Maybe the man himself [MENTION=3685904]ak[/MENTION] can help. :)

[MENTION=4608636]bsmitty83[/MENTION] Here's your spiffy new updated ramdisk:

http://v.ht/osmod -- http://d-h.st/users/osm0sis/osmod/

:D

It backs up media_profiles.xml if on SmittyV or DirtyV-SR, restores the backup if on DirtyV, and pushes an init.d script for if someone changes kernels away from any of the above to restore it -- Edit: oooh I should make the init.d script delete itself. That'd be classy. BRB. Upload pulled until then.

Edit 2: And we're back! :cowboy:
[Samsung Galaxy Nexus] dbt816:
I had to roll back to the 2/15 version to keep things stable. Had a lockup trying to navigate to a customer site (battery pull while driving through rush hour traffic...heh), a reboot while on the phone with my boss, and numerous freezes (that recovered) throughout the day.
[Samsung Galaxy Nexus] bsmitty83:
Awesome , I just added a 3rd build time option . before it was bigmem or superram now its those 2 plus regular ram .
[Samsung Galaxy Nexus] osm0sis:
Cool. Should still work I imagine. The logic is: As long as it's not DirtyV-SR or SmittyV the dvbootscript.sh restores the original, and the init.d script does the same if it's not DirtyV* or SmittyV at all. Pretty slick if I do say so myself. :D
[Samsung Galaxy Nexus] robbnsade:
Been running great on the past few smittys and dirtys but when I flashed 2-17 R it stayed on Google logo for over ten minutes...restored backup for now. Prob bad download but I'm going to try again once I get home. BTW... No settings set up for boot and wiped dalvik and cache after flash. Just fyi

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] milojoseph:
Im always the one giving good support for this kernel, but this new build dirty v RSR.... big SOD had to battery pulll... This time i didnt care too much on the overheat but this one too it to the next level.. and random reboot. Going back to metal 1
[Samsung Galaxy Nexus] heXacode:
You're not alone. Getting real fed up with the snowplowers pushing snow into my parking spot every time and having to shovel it away 2 or 3 times each snow storm. BTW I'm in central PA.
[Samsung Galaxy Nexus] Nephilim:
I'm not understanding all these reboot and SOD posts about the latest DirtyV. I undervolt quite alot in my settings and haven't had a single hiccup on this or yesterdays SmittyVMetal2.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
I was getting them the first time I installed smittymetal , but haven't seen a lockup or sod since . in fact I've been running smartreflex off and thermal throttle off as well , no problems . but I understand that some phones can't handle it . maybe its cause I'm on toro ? Idk
[Samsung Galaxy Nexus] milojoseph:
Lml team Maguro
[Samsung Galaxy Nexus] LibertyMonger:
I had a few freezes and reboots with Neph's settings so I just lower GPU OC and raised my voltages 15 and it stopped. I have also had instances where I press an app or dialer and it stalls before opening. Not really lag, just won't open and i have to press it again. But I know going in this is all one big experiment and there might be risks so I keep a backup phone if I need it. I see some seem like they were inconvenienced by running this kernel lol. Did you tell your boss it wasn't your phone "it's this damn kernel" Lmao. Sorry just kidding lol.
[Samsung Galaxy Nexus] milojoseph:
Of course we are beta testers of a stable rom.... We risk our phone and report back to help the community of noobs (me) to fix their issue... When i press the dialer it freezes for like 10 sec and the resume...

---------- Post added at 09:49 PM ---------- Previous post was at 09:48 PM ----------

You took the words right out my mouth lml i didnt see... Maybe i should raise my voltage as well. But i think my phone had enough flashing for today.
[Samsung Galaxy Nexus] pattyboi:):
we get it man,you had it the worst,quit showing off -_- xD
[Samsung Galaxy Nexus] pattyboi:):
i believe you bro,especially from what ive seen on tv (which i doubt even comes near describing what it was like)
[Samsung Galaxy Nexus] dbt816:
Maybe I should try 2/17 again and revert my voltages back to default...
[Samsung Galaxy Nexus] pattyboi:):
Not to sound weird,but that would be really cool to see man:highfive:
[Samsung Galaxy Nexus] pattyboi:):
Lol,nice turtle man ;D & you met Mike Tyson...lucky bastard..lol ..we are so OT right now
[Samsung Galaxy Nexus] pattyboi:):
Both are of those are true lol. This kernel is quite amazing.
[Samsung Galaxy Nexus] dbt816:
bonus:

Here is a young MBQ meeting Mike Tyson at a Circle K in Scottsdale, Arizona several, several years ago!

You're lucky he didn't bite your ear off ;) lol
[Samsung Galaxy Nexus] DevVorteX:
Agree on the kernel running great. If I could figure out what's reverting my max frequency I'd be super happy. For now I'm using tricksters frequency lock feature. But I swear it's causing battery drain. 12000 fur max isn't even bad, so o may just deal with it.
[Samsung Galaxy Nexus] DevVorteX:
Lol, I know, I'm on shiny, so it's practically aosp. So nothing else should be messing with it. Maybe I'll re flash just for the heck of it.
[Samsung Galaxy Nexus] klobkelosh:
I'm having the same problem on cm11. Max freq reverts to 1200. No cm performance settings used.
[Samsung Galaxy Nexus] robbnsade:
Flashed again and it booted fine... Not sure what happened but flying again. Haven't had any reboots or anything due to undervolting or any issues with sod's except for when I've tried to let trickster set anything on boot. I turned everything off long ago and just set it up myself. Only been using this phone for a few weeks (rezound charging port issue) and have see this device is very picky on which kernels you can use. So far this kernel has been butter :D

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] aosp:
DirtyV is that fast causing some phones to freak out and boot loop a few times before catching up ;)

Dirty&Fast Yes!
[Samsung Galaxy Nexus] osm0sis:
I'm running Shiny too and I don't have this problem.. I use f.Ku to set the max to 1350 on boot and it works perfectly. Must be something else going on with your setup.. :confused:
[Samsung Galaxy Nexus] RoadToNever:
Not sure what's changed but the latest DirtyV-R doesn't make my phone heat up as much pervious versions.:good:
[Samsung Galaxy Nexus] milojoseph:
Me and galaxy are always the odd balls.... we will try again......
[Samsung Galaxy Nexus] osm0sis:
Try my updated DirtyV-SR 2.17.14 ramdisk version and see if it helps?

http://v.ht/osmod :D
[Samsung Galaxy Nexus] milojoseph:
Ok for free??? Lml will report back....
[Samsung Galaxy Nexus] garyngkt:
I don't seem to be running well with RSR 15/2 or 17/2 on CM11, phone froze a few times. I'm now back on 10/2 and no issues :crying:
[Samsung Galaxy Nexus] milojoseph:
Try osmosis version that he just shared it works perfectly fine for me.... ;)
[Samsung Galaxy Nexus] DevVorteX:
In case this so sparks an idea from someone.

Whenever I turn my phone off (screen), then back on again, my scaling max frequency is reset to default.

I'm losing my mind here. Lol
[Samsung Galaxy Nexus] osm0sis:
That sounds like what happens when the power.tuna.so HAL is running.

Do you see it in /system/lib/hw/ ? It's supposed to be backed up and then deleted by dvbootscript.sh, and this same script has worked fine on franco.Kernel for ages, and also seems to be working fine for most people here. :confused:
[Samsung Galaxy Nexus] DevVorteX:
Yup, it's there alright.

What does that mean? Should I delete it?
[Samsung Galaxy Nexus] osm0sis:
"There" as in power.tuna.so OR power.tuna.so.dvbak ?

I just verified mine gets copied to the .dvbak and then the .so gets deleted. In other words, it's still all working correctly here. :confused:
[Samsung Galaxy Nexus] DevVorteX:
Power.tuna.so is in there, without the .dvbak extension.

I'm on dirty v - r 2/17, so....I'll rename that file to end with .dvbak?

I just want to confirm so I know who to blame :)

---------- Post added at 01:05 AM ---------- Previous post was at 01:03 AM ----------

I also just recently started using twrp over cwr like 4 days ago. Could that affect it?
[Samsung Galaxy Nexus] osm0sis:
That's f*cked. Leave the file alone and try the one I posted on the last page, then check the file again please.

Shouldn't make a difference. Everything that happens occurs in the ramdisk script.
[Samsung Galaxy Nexus] DevVorteX:
Downloading, but fyi I'm not happy, I don't want SR version. But idol so what you tell me...

---------- Post added at 01:12 AM ---------- Previous post was at 01:08 AM ----------

Just installed yours, and that file is renamed. So.. latest dirty v is borked?
[Samsung Galaxy Nexus] osm0sis:
We're trouble shooting, brother. I'm not forcing you to marry it. :p

Look in /sbin/bb/ while you're at it and see if busybox is there. Something you have installed messing with the ramdisk busybox is literally the only reason the script could fail.
[Samsung Galaxy Nexus] mrcooter:
I've created 9 different lockrings in 4 different styles from stuff I've found here with the various DirtyV logos. With many ROMs having custom image settings now for this i just thought I'd share these for anyone that would like to use them. Just trying to contribute what little I can and show some love to this great kernel! Feedback is welcome. Hope no one minds me posting them here. I'll remove this if need be. Keep up the great work. Kernel running great for me! Here's the link...

https://www.dropbox.com/sh/jbh5in69m0yktrm/jyBmFUC9ER
[Samsung Galaxy Nexus] osm0sis:
Ahh crap. Yup! That sucks! That's the only other way things could not work - the disabling script wasn't there to begin with! :p

I guess [MENTION=4608636]bsmitty83[/MENTION] didn't use the same ramdisk for all of them by mistake? Good news is my new ramdisk is meant for all of them, so it should be fixed for the next release. :)
[Samsung Galaxy Nexus] DevVorteX:
Lol, busybox is there. Like I said, your version is working perfect, it's the latest dirty v that's not. The bigmem version. Maybe sr is fine, but bigmem has an issue?
[Samsung Galaxy Nexus] milojoseph:
Ot...nbut every time I flash and im done to rebot. I get a "fix xbin root might be lost" I fix it and root is fixed... when I dont root is still there. Someone told me to reinstall busybox...cna someone help
[Samsung Galaxy Nexus] DevVorteX:
Phew, at least it's probably not something I did. Thanks for hanging around and helping me figure this out. I guess i should say you're welcome that I helped you, since I didn't do too much thinking on this one.
[Samsung Galaxy Nexus] osm0sis:
Yeah just a mistake where bigmem has the wrong ramdisk. See my reply above and thanks for helping weed that issue out! :)

That's CWM being retarded and not realizing that su permissions get reset on boot starting with JB4.3+ due to SELinux. You can press whatever you want and things will still be fine. Basically just ignore it. Check the "Known Issues" in my CWM thread OP. ;)
[Samsung Galaxy Nexus] büscher:
After a short night I have to share my experiences with 2/17 RSR:

I'm on a maguro and as you may know I don't undervolt. I also had a freeze before going to bed, was using my phone normally with whatsapp and gentle alarm.

My settings differ a little bit from Nephilims, I use sioplus 1280 and 1.5GHz.

Also the last two builds are battery eater on my phone compared to previous versions.

And last thing I noticed is (yes blame me for benching with antutu :sly:) database I/O is very weak ond latest build. The rest performs like it used to on previous builds.

However, still amazing :thumbup::thumbup:
[Samsung Galaxy Nexus] osm0sis:
The "battery eating" is maybe the wrong default freq being set for input boost - it would make it jump to 1200 instead. Should be fixed in the next build with my patch Smitty committed yesterday.

Database IO - Use the DirtyV-SR 2.17 from the OP, but delete the bundled init.d scripts from /system/etc/init.d/ after flashing, reboot and test again to see if it fixes it?
[Samsung Galaxy Nexus] büscher:
I just realized that I stayed on SmittyV_Metal2.

Sorry for that. I deleted all of the scripts except the mountscript. And I set boostfreq to 700, so it schould jump to 920 schouldn't it?

I'll see how my phone performs without this bootscript and won't bother you until next release ;)

Btw: who the f*** is maintaining this crappy xda developers app?? Damn this thing is buggy. Any alternatives?
[Samsung Galaxy Nexus] Charmacas:
Tapatalk for sure! ?

Your newest modification works fine [MENTION=1143630]osmosis[/MENTION]. The power_tuna.so is backed up as intended. Now the frequency sticks and we are able to modify target loads. Any downsides or disabling it?

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] oman0123:
Are you guys using any apps other than Trickster? It never fully restores my settings and i paid for the full version. Oh well. I got my money's worth.

Any recommendations are appreciated :thumbup:

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] garyngkt:
OK will test thanks
[Samsung Galaxy Nexus] josera06:
where i can download it?

thx!
[Samsung Galaxy Nexus] mrgnex:
[MENTION=5083140]mcooter[/MENTION]

Thanks for sharing. I was gonna test them out but link is down. Any mirror?
[Samsung Galaxy Nexus] adoboyo:
Hey guys, what's the default TCP, rab and scheduler annnddd gpu oc on 2/17 dv-rsr?

I'm on vanir and i forgot to disable the vanir.cfg before I flashed.
[Samsung Galaxy Nexus] Punkiderma:
everything smooth, now frequences stick and power.tuna.so is renamed with the backup extension ;)

thanks!
[Samsung Galaxy Nexus] qtoo941:
[MENTION=4544860]osm0sis[/MENTION] - thank you, man. Very good work with new ramdisk version. Even target_loads are saving in trickster.

Can I ask a question: I decided to set my max freq to 920 MHz. And in governor control of interactive i got hispeed_freq at 920,000 and input_boost_freq at 920,000. I was using this values when my max freq was 1200 MHz. Should I decrease both values to 700,000?

And question to [MENTION=4608636]bsmitty83[/MENTION]: Is it possible to add InteractiveX governor to your SuperRam kernel ? :D
[Samsung Galaxy Nexus] bsmitty83:
Its strange since I used the same ramdisk , only for dirtyV I left out the mediaprofiles.XML . that's it
[Samsung Galaxy Nexus] 47th_Ronin:
[MENTION=4608636]bsmitty83[/MENTION]

faux just released v36 of faux kernel and he has two new items, the first is intelli-active governor that hot plugs and second us something called intelli-plug?

Trickster says it's an in kernel replacement for MPDecision....

Testing it out now and seems very smooth.

Thought you and he guys might like to check it out.
[Samsung Galaxy Nexus] Grarak:
Mpdecision only exist on krait devices
[Samsung Galaxy Nexus] ak:
intelliplug = hotplug cpu

intelliactive = governor (like interactive)
[Samsung Galaxy Nexus] garyngkt:
So far [MENTION=4544860]osm0sis[/MENTION] 17/2 mod version is running fine with my CM11
[Samsung Galaxy Nexus] büscher:
I'm on osm0sis mod too. Running smooth but is also a battery eater somehow... 5.6%/h for the last 3 hours with 20 minutes screen on and wifi off...

And what I noticed: After a reboot I'm sometimes not able to power off my screen immediately (happened on previous builds too). I can press my power button but nothing happens, however long press brings up the boot-menu. This is really a small thing, just wanted to mention it.
[Samsung Galaxy Nexus] pvkiniyan95:
Guys sorry for this question...

Does dirtyV 17.2 has all those patches of smittymetal2...
[Samsung Galaxy Nexus] aaron13:
Dirty V 17/2

Hello people,

I flawlessly flashed Dirty V 17/2 on CM11-18febr. Changed nothing, max.cpu is at 1200mhz.

Everything works fine, however in the logcat were some errors.

Cq. : "failed to find cpu subsys"

Does someone knows what this means?

The benchmark compared to Dirty V15/2 is almost the same(100 points less in Antutu).
[Samsung Galaxy Nexus] qtoo941:
Damn, new osm0sis version of 2/17 is eating battery like hell.
[Samsung Galaxy Nexus] infectedorganism:
Could someone post the default minfree settings?

Thanks in advance.
[Samsung Galaxy Nexus] qtoo941:
For sure there must be something wrong in 2/17 osmod version... Battery temp went up to 51°C and cpu temp went up to 73°C. My phone has never been so hot and my battery life is just... No comment.
[Samsung Galaxy Nexus] pattyboi:):
yes it does.
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4443334]Grarak[/MENTION]

Check out the newest goodies for the tuna from [MENTION=2765426]styr[/MENTION] & [MENTION=3332811]faux123[/MENTION]

https://github.com/jimsth/vanir_tuna/commits/jim_mr2

https://github.com/jimsth/vanir_tuna/commits/jim_mr2_exp

https://github.com/faux123/tuna/commits/kk_exp
[Samsung Galaxy Nexus] pianistaPL:
It would be really nice to see Inteliactive in Dirty_V :)
[Samsung Galaxy Nexus] pattyboi:):
man you always find the best sh*t..android detective aosp!:cowboy:
[Samsung Galaxy Nexus] bsmitty83:
Dmsg 's help.........
[Samsung Galaxy Nexus] aamadorj:
Bad battery life on my device after installing bsmitty latest DirtyV-RSR made me explore the possible causes. I found nothing clearly wrong with BetterBatteryStats so I began to explore different roads.

Some tests later, I found out CPU frequencies were having a weird behavior: even right after reinstalling this kernel (that is with stock values) the min CPU freq for screen on was ignored and it was going down all the way to 180 MHz (according to the info section of Trickster MOD). The same weird behavior happened when I load my personal profile within Trickster MOD, but it fixed after I manually selected every CPU frequency setting and pressed "apply". I suspected other kernel settings could be having the same issue, so I manually entered my own values for minfree and interactive governor. Battery life went back to normal after all this.

Curious about the osmosis comment about the issues with the ramdisk package, today I tried his build and it seems the CPU frequencies weird behavior is still there. Again, I manually entered my own kernel values using Trickster MOD and so far it seems battery life is completely normal.

Just my experience.

Note: I decided to try as hard as possible to keep using DirtyV-RSR 02.17.14 because it has the best performance so far. Thanks for all your good work, [MENTION=4608636]bsmitty83[/MENTION] and team.
[Samsung Galaxy Nexus] büscher:
I hope this helps, I'm a beginner in interpreting such logs...

https://www.dropbox.com/s/do0c5ysrg2vdkl9/dmesg.txt

Edit: Reverted back to Dirty_V 4 SR and the battery drain is still here.

So as dirtyv did not have a ramdisk back then and, as far as my knowledge goes the ramdisk persists if no new was flashed, i think this is a ramdisk issue..

I'm on osm0sis latest build btw.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Grarak:
I already have almost all those commits. Commits which I don't have are useless for me.
[Samsung Galaxy Nexus] milojoseph:
finally a dmesg....i couldnt get one. Im using [MENTION=4544860]osm0sis[/MENTION] build using neph setting...... i undervolted and battery life is doing well. But that heat man keeps my hands very warm during the winter lml.
[Samsung Galaxy Nexus] qtoo941:
The most time i was using DirtyV-SR-V5 until DirtyV-SR-2.10.14 was released. With this builds my phone was very stable, cool and with good battery life. But in newer releases with and without ramdisks my phone was really hot and the battery drain was bigger. Yeah, there was some performance with new kernels but just slight difference.

[MENTION=4608636]bsmitty83[/MENTION]: Smitty, I would like to download some kernels (V4.1 / V5 / 2.10.14) but your DevHost is not working. Would you give me another link please??
[Samsung Galaxy Nexus] giorgis91:
Strange poor battery also with smitty

Send trough time and space with a Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
None. Smitty switched to Franco's kernel-side touch boost instead.

Yeah you're not going to want that at your max.

Normal. That keeps your device from rebooting due to CAB. Screen is always the battery killer, what do you normally get?

Unless you can show some process keeping your device awake it doesn't really make any sense. Same ramdisk tweaks for ages on franco.Kernel (and Fancy) with no issues. Only difference is the governor permission fixer and a little script loop like that doesn't affect anything as I showed back in the day with my 950io script. Exact same kind of sleep loop.

Y'all are crazy. ;)