yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] jhonnyx:
I clearly agree with you, MBQ_, no point of further discussion with you pal, but seems that the user does not know Q&A forum neither he does not fall back to the previous settings, AKA: not applying Neph's values on trickster on boot, not flashing another kernel, neither going back to a working backup, nor provides a log so we can help him, so I stick with the basic tutorial (seems that he's unable to cool down his phone) for him.

Maybe a good idea would be: "have you tried to put a cooling fan on the back of your phone?"

nay ;)
[Samsung Galaxy Nexus] swarlesbarkely:
I've noticed every so often trickster just drops the ball. I make sure the kernel settings box is checked then reboot and all is well generally
[Samsung Galaxy Nexus] juju2011:
Lol do what I do when phone over heats go stand outside for 5 mins lol the great Canadian winters cools that bizznitch supa quick lol ;)..

Or u can put kernel settings back to stock n see if phone still over heats like stated above both would work
[Samsung Galaxy Nexus] swarlesbarkely:
Anyone else still having issues with tuning smartass?
[Samsung Galaxy Nexus] osm0sis:
Edit: Somehow missed there were 3 pages between these and now before I replied haha.

Trim shows in the logcat. I wouldn't use aLogcat though because it needs a Terminal command to grant it root log privileges since the dev hasn't updated it. :good:

If you're setting it to 0 like in Neph's old settings, that's why it resets; that's not a correct value. If it still doesn't stick with something correct (about 10-20 less than go_hispeed_load), and the ramdisk didn't fix it then it's sounding like it's a Trickster problem from this point guys, to be honest.

If I followed along correctly Dirty now has Illinois TCPCAA and the 3.4 Wi-Fi drivers and Smitty hasn't yet been updated with those.

Change your router security to WPA2. The ported 3.4 Wi-Fi drivers don't support WEP security anymore. WPA2 is also much safer.
[Samsung Galaxy Nexus] scarcry:
go_hispeed_load stuck to 99 but target_loads did not stick to 85

So yeah indeed seems like a Trickster problem.

I'm going to try with f.Ku

Sent from my LiquidSmooth maguro
[Samsung Galaxy Nexus] cujo6801:
gotta have me some Rob Ford

sent from the DOG pound
[Samsung Galaxy Nexus] qtoo941:
[MENTION=4544860]osm0sis[/MENTION] actually i cannot change it to WPA2 atm :( and it shows that its not WEP but WPA (if the two things are the same - sorry) ... I would like to ask [MENTION=4608636]bsmitty83[/MENTION] to upload version of 2/10 kernel (illinois included <3) without this new wi-fi drivers. Thank you in advance guys. <3
[Samsung Galaxy Nexus] Charmacas:
I've deleted Tricksters App data and tried to apply a target load higher than 0 after that but it still does not stick.

Of course I am with DirtyV-021014 and the Ramdisk modification by Osmosis.

Any other ideas how to solve this sh**? :D

--EDIT--

70 920000:80 1200000:99

That's what Android tuner shows me on target loads. What does it mean?

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] osm0sis:
Honestly? Try something other than Trickster. f.Ku appears to work just fine. Maybe now that [MENTION=4608636]bsmitty83[/MENTION] is going to use a ramdisk he could add Synapse support and then everyone could use that as the recommended tweaking app.
[Samsung Galaxy Nexus] Charmacas:
I've edited my post above. Could you explain that Osmosis?

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] scarcry:
[MENTION=4544860]osm0sis[/MENTION] is it correct that fku doesn't have an option to set the minfrees? can't find it anywhere.

fku however has boostpulse in the interactive CPU governor menu which Trickster doesn't show so it currently has no value. any advise what value to set? I'm using boost 0 and boostpulse_duration 75000

Sent from my LiquidSmooth maguro
[Samsung Galaxy Nexus] Nephilim:
Anyone using WEP Should just turn off security on their router all together because it is completely useless. WEP is the only thing that will not work with the 3.4 drivers so there is no reason to switch back. Use WPA. These drivers are much better than the old ones.

Not trying to be rude but this was brought up over a year ago with AK kernel so people should have purchased new routers by now. They are not expensive.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
I'd just leave boostpulse alone. No minfrees, no. I always wanted him to put in RAB and NR (queue options) too but he wouldn't.
[Samsung Galaxy Nexus] Nephilim:
A couple good examples of why I stick to Trickster Mod. Well, besides the fact I bought the donate version lol.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] Hetalk:
Just wondering, can [MENTION=4608636]bsmitty83[/MENTION] make your settings a default in dirty-sr kernel? Or maybe a new smitty-neph-sr.zip :D
[Samsung Galaxy Nexus] qtoo941:
Is this WEP??
[Samsung Galaxy Nexus] osm0sis:
But on the other hand, by most accounts Trickster sounds pretty broken right now. :(

I figured out what was up with the color multipliers. Smitty left the safety limit enabled. ;)

echo 0 > /sys/class/misc/colorcontrol/safety_enabled;

Nope but WPA2 Personal is what you should be using on your router. The issue might be TKIP where AES is the preferred.
[Samsung Galaxy Nexus] scarcry:
I bought the donate versions of both lol but these settings missing in fku is a shame.

Sent from my LiquidSmooth maguro
[Samsung Galaxy Nexus] juju2011:
Lol sadly he is from my province and his last appearance on camera was a bit much he straight mangled my language but oh well he is Toronto's problem lol
[Samsung Galaxy Nexus] bsmitty83:
Oops , I'll try to remember that on next build .

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] qtoo941:
Well you said that i cannot connect if my router is set to WEP. Why i cannot connect to it when its WPA instead of WEP? ;d I am so confused right now :X
[Samsung Galaxy Nexus] David 617:
No. You have WPA.

---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------

Can you switch to WPA2? If you own the router just log into the admin console and change it.
[Samsung Galaxy Nexus] bsmitty83:
That's kind of an idea I had since Os already has his tunables , I was gonna add some scrips to handle all that . along with AK's WiFi revert script . [MENTION=3685904]ak[/MENTION] , did you complied both drivers for the script to work ? , how does that work now that the bcmdhd is build inside the kernel and not a module ?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Like I said, my best guess is that you're using TKIP instead of AES.
[Samsung Galaxy Nexus] Nemed:
Anyway i'm writing an init.d script to set [MENTION=2853378]Nephilim[/MENTION] settings at boot
[Samsung Galaxy Nexus] Swede2008:
Would Performance Control be a better option than Trickster?
[Samsung Galaxy Nexus] qtoo941:
Would you be good to me to explain me how to change it from TKIP to AES. And yes, you are right. Actually it is TKIP.
[Samsung Galaxy Nexus] metalspring:
I think it might have to be compiled as a module to be replaceable, at least then all you'd have to do is replace the 3.4 module in /system/lib/modules with the older version

If it's built into the kernel then there is nothing to replace
[Samsung Galaxy Nexus] bsmitty83:
Yea both would

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] DevVorteX:
[MENTION=3317173]büscher[/MENTION] has actually got something already. I've just used what he provided to get mine working for everything minus the voltages.

Had to set permissions on a few things to do screen_off_max_freq, and screen_on_min_freq, but other than that, his scripts are solid.
[Samsung Galaxy Nexus] tFrost:
I'm using vanir and seeing about 8 init files, and some of them defines kernel parameters, how do you control the order of which they are initialized, and should I replace them with the settings I made?
[Samsung Galaxy Nexus] dbt816:
Crap... I haven't used WiFi tethering in forever, but needed it today :silly:
[Samsung Galaxy Nexus] pkgnex:
They are run in numeric order (usually 97xxx, then 98xxx, then 99xxx, etc.).

Can't answer the 2nd question without knowing what's in the files, BUT if you make your script the last to run by numbering it correctly, it would over-write only the items that are in your script.
[Samsung Galaxy Nexus] gohamstergo:
itll be back... in time :)
[Samsung Galaxy Nexus] tFrost:
I remember they used to be like that, but it doesn't look like that here. As far as I understand the settings is set in the vanir and then on boot again with trickster, correct me if I'm wrong?

Edit: I'm looking the wrong place should look in /etc/init/ of course, but it looks like the vanir script is also doing changes to governor and stuff
[Samsung Galaxy Nexus] bsmitty83:
pretty sure you can still use a tethering app , just not native hotspot
[Samsung Galaxy Nexus] pianistaPL:
[MENTION=4608636]bsmitty83[/MENTION] It would be cool if you could past changelogs in OP ;) There is so much pages with every hour that it's very difficult to find changelog in single post ;)
[Samsung Galaxy Nexus] juju2011:
Wait mobile hotspots aren't working?

Nvm just tried it works for me hmm what's WiFi tethering then?

---------- Post added at 02:32 PM ---------- Previous post was at 02:17 PM ----------

@bsmitty83 hey dude if I want to flash the kernel with ramdisk do I have to flash the ROM with it as well or can I just flash kernel and wipes caches? And dirtyv10 is da **** mobile hotspots work fine for me tried on my ps3 and my moms phone and my note all connected and and browsed like normal :beer:
[Samsung Galaxy Nexus] gohamstergo:
Anyone else having "kswap0" be a CPU hog? As evidenced by it's name, it related to ram swapping, but I have ZRAM turned off...? So, what is kswap0 doing?
[Samsung Galaxy Nexus] dbt816:
Yeah, I know... was just funny that it happened this way! Murphy's Law...
[Samsung Galaxy Nexus] osm0sis:
It's in the wireless security settings of your router's interface. Probably at http://192.168.1.1/ though it can be different.

Haha. Yeah those are the root ramdisk / rc files, not /system/etc/init.d/ ;)

init.d scripts are run in alphanumerical order. rc files are run according to the way they get imported, starting with init.rc.

init.vanir.rc, init.slim.rc, etc., etc. are pretty much all the same as init.cm.rc; ROMs just rename it, and maybe add something minor of their own.
[Samsung Galaxy Nexus] tFrost:
On 10/2 with Nephilim's settings I'm getting around 12h with 2h screen and down to 17% - isn't that a bit below average (I have a feeling my battery have seen better days)
[Samsung Galaxy Nexus] dbt816:
When I've seen that on real Linux servers, it's a kernel bug in the memory manager. There may be some additional info on what it's doing in dmesg.
[Samsung Galaxy Nexus] mrgnex:
Yeah, Im still on v4 and now I have 11 hr up time and 1 hr screen on time and still 50% battery left.
[Samsung Galaxy Nexus] bsmitty83:
The nexus is retired .....
[Samsung Galaxy Nexus] tFrost:
Congratulations on your note 2!
[Samsung Galaxy Nexus] Hetalk:
Retired ? :eek: :confused:

In what sense? :confused:
[Samsung Galaxy Nexus] clnzx2:
Latest kernel does seem to be eating more battery than usual
[Samsung Galaxy Nexus] GilGameshn1:
Using hyper with fiops and 1024 RAB ... stock governor and Iva values and everything is OK . I can't see any difference . could be me .

Sent From My Nexus Prime
[Samsung Galaxy Nexus] Grarak:
New app? May I can help. I have nothing to do.
[Samsung Galaxy Nexus] bsmitty83:
Ive been getting pretty good numbers with the new kernel .

Its not my primary phone anymore . So I can use it just to test and for a backup
[Samsung Galaxy Nexus] TheMan0790:
I really want to post a Michael Scott in The Office/Darth Vader "Noooooooo!" pic and gif collection here...

Break me off a piece of that KitKat ROM!
[Samsung Galaxy Nexus] Hetalk:
Oh. Ok. :D
[Samsung Galaxy Nexus] Nephilim:
Screen-On time makes a big difference, are you on Toro or Maguro?

That one extra hour tFrost has sucks alot of battery, Gnex is sadly known for not having the best battery life. The difference between your two battery readings seems about right.
[Samsung Galaxy Nexus] qtoo941:
congratz for your new phone, smitty. Will we still receive any new updates on dirty v? if not (god no, please ;x) i would like to ask you for at least one last kernel - 2/10 kernel without new wi-fi drivers (like alternative kernel) please (super ram <3)
[Samsung Galaxy Nexus] GilGameshn1:
Too soon to lost hope . but so far so good experience I have with DirtyV . tnx .

Sent From My Nexus Prime
[Samsung Galaxy Nexus] bsmitty83:
I'm still gonna dev for the gnex , setting up aokp on this monster , trickster now has way too may settings , lol

No vanir for vzn note 2 either , looks like I'll be on that soon

Does WiFi tether work with the apps ?
[Samsung Galaxy Nexus] gohamstergo:
going pretty good for me in general as well. Posted this Q before, but maybe it wasn't seen. Any idea why kswap0 is maxing my CPU at times for 30+ seconds? I have zram disabled..
[Samsung Galaxy Nexus] Nemed:
So as i said i made the init.d script with [MENTION=2853378]Nephilim[/MENTION] settings:

Download

Copy to /etc/init.d foder and set permissions to -rwxr-xr-x with solid explorer or you can do it with terminal emulator, just type:

su

chmod 755 /etc/init.d/95nephsettings

1) Obviously i did NOT include in the script any voltage (MPU/smartreflex/GPU oc/ etc)

2) For some reason, in dirtyv 2.10 i'm not able to set color multiplier even though the script is correct (it's an issue mentioned before by someone...i can't remember who xD)

3) target_loads is set to "70 920000:80 1200000:99" (default value), i included the command that set the right permissions (thanks to [MENTION=4544860]osm0sis[/MENTION]) so if you want to change it type in terminal emulator:

su

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

This will set it to 85, change the value as you wish

4) I tested my script and it works, but do a nandroid backup, i'm not responsible if something goes wrong

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] dbt816:
I tried one tether app a little while ago with no success
[Samsung Galaxy Nexus] 47th_Ronin:
That's awesome!

Hmm maybe a red devils tail coming off of the letter Y in dirty?

Just wondering...
[Samsung Galaxy Nexus] milojoseph:
hmm so i change my governor to smartassv2 and it cool down... Anyone know any custom turnable for that governor?
[Samsung Galaxy Nexus] Nephilim:
Most roms have that governor locked down so you cannot modify the tunables. I have tunables ready and waiting for when smitty launches a DirtyV with ramdisk though. ;)
[Samsung Galaxy Nexus] milojoseph:
Well interactive was the cause of my phone overheating for some odd reason.....
[Samsung Galaxy Nexus] Nephilim:
That's quite odd.
[Samsung Galaxy Nexus] milojoseph:
i know.................
[Samsung Galaxy Nexus] osm0sis:
2) I posted the solution to this a couple pages back. You just need to disable the safety limit for the multipliers with a command. You can add that to the script. :good:

3) According to f.Ku it defaults to 85 along with the other Dev team interactive winners. I'm guessing ROM interference from sysctl for those that show otherwise, and if it shows 0 on my ramdisk version you've got an app problem.

Also appears to work fine in f.Ku... Trickster for the lose! ;)

Edit: Actually I take that back. There is an issue. f.Ku doesn't see any tunables for it because the directory name doesn't match the governor name. smartassV2 vs. /smartass - same goes for dyninteractive vs. /dynamic_interactive - but the tunables seem to edit just fine from a file explorer.
[Samsung Galaxy Nexus] Nephilim:
On what rom though? I think Liquidsmooth may be the culprit not Trickster Mod.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Ah perhaps you're right. I'm on Shiny. Definitely some weird sh*t going on, either way.
[Samsung Galaxy Nexus] Nephilim:
I hope once DirtyV has set ramdisk it won't be a problem anymore. Once that happens I'll create tunables for multiple Gov Controls.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Use my DirtyV with ramdisk and see how far you can get; that's likely where Smitty's going to start, since he asked. :)
[Samsung Galaxy Nexus] Nephilim:
Is it the same as SR 2/10 except with ramdisk added?

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Yes sir! As described in my post for it. :D
[Samsung Galaxy Nexus] Nephilim:
Okay, one more dumb question. I notice it says "cwm" in the kernel name. I use twrp, will that work?

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Yeah it's just a shorthand for "flashable zip" I use. Don't worry. :)
[Samsung Galaxy Nexus] Nephilim:
Cool, going to flash it right now and see what I can do. With any luck I'll be testing some new SmartAssV2 settings within the next 5-10 minutes. :D
[Samsung Galaxy Nexus] dbt816:
Booting up to [MENTION=4544860]osm0sis[/MENTION] kernel+ramdisk now... well, actually waiting on ART to cache my apps...one stinkin' bit at a time ;)
[Samsung Galaxy Nexus] Nephilim:
No go, ramdisk didn't make any difference. Still cannot change any of the tunables for SmartAssV2, I even went to check target_loads tunable on Interactive and it still reverts to 0 regardless of what you try to set it to. This can't be a TricksterMod issue because people have verified that they are able to set target_loads to 85 on Trickster with DirtyV, why is it some of us can change certain tunables but cannot change others? This is now less confusing and more so just annoying.
[Samsung Galaxy Nexus] AutomaticFailure27:
Lil off topic but wondering, since I'm sure all you fabulous people use TiBu, if any of you have it set to do an auto backup, what settings/parameters do you use? I'm trying to find something that just backs up new/modified data and newer versions of apps. Currently, I had it set to back up all data, but it seems that takes extremely long amd pointless since not all appa get updates that much. I think I might have it set right but more curious than anything as to what others use.
[Samsung Galaxy Nexus] dbt816:
My schedules:

1:00am every day: Delete backups for un-installed apps

1:05am Mon thru Sat: Redo Backups for modified data

1:20am Mon thru Sat: Backup new user apps & newer versions

1:05am Sun: Forced redo of your backups

Having the forced redo on Sunday is probably unnecessary since I only keep a max backup history of 1, but I just keep it there if I ever need to change that. The two that run Mon-Sat keep the backups current without running a full backup every day.
[Samsung Galaxy Nexus] D1BB:
I'm running vanir 2/10 with dirtyV 2/10 and I can set target loads on interactive, and have tunables for smartassV2. Hopefully you haven't already found this to be a ROM issue, I do the best I can keeping up with this thread :P
[Samsung Galaxy Nexus] fracama87:
Could synapse be a solution (with ramdisk) when it'll be supported?

MBQ can't wait for your app!

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] chainrulez:
That's a great one. Fully supported from my side :laugh: :highfive:
[Samsung Galaxy Nexus] osm0sis:
That was me setting it to 78 with f.Ku from the default 85 on DirtyV-SR-ramdisk 2.10 and it works great, even after a reboot. Checked the sysfs file directly to verify. I'm running Shiny so it's definitely clean. Soo Trickster, or ROM issue? Either sounds plausible. :confused:

Maybe we need to add the sysctl.conf disabler script to the ramdisk to try and counter any ROM interference? That's why I wrote it for Franco, he was getting pissed that the settings he chose were being overridden, but I left it out here since I wasn't sure how Smitty felt about that.

Yep Synapse is sounding more and more like a good idea. Let's take Trickster out of the equation. :highfive: :good:
[Samsung Galaxy Nexus] Nephilim:
This.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] gohamstergo:
Just figured I'd note that I'm still getting significant screen-wake delay on incoming calls. My guess would be that it has to do with the low "screen off max" speed I have set of 350. Doesn't seem to ramp up the speed fast enough when a call comes in, making it lag because of all the processing the phone suddenly has to do at such a low clock speed. Unfortunately, I barely ever get calls, so maybe someone who gets a bunch can test raising their screen-off speeds to gauge the reaction time? If that's all the problem is, maybe some sort of hook could be added to the kernel to automatically set the CPU to screen-on values as soon as a call is detected..? I wouldn't know :P

edit: So, I remembered I could use Google Voice to call my phone. Set my screen-off to 1200 just to test and I still had 5+ seconds of screen lag. Not sure what else to do then..
[Samsung Galaxy Nexus] Swede2008:
I'm getting this too on latest Vanir nightly with 525 max screen off.
[Samsung Galaxy Nexus] metalspring:
I wonder if there is a certain part of the source code overriding the script you are trying to use? Other than simple init scripts you can also set permissions and kernel settings via power_tuna.c (which ends up being power_tuna.so in system/lib/hw also known as the tuna powerhal)

To see what I mean, look here

https://github.com/CyanogenMod/android_device_samsung_tuna/blob/cm-11.0/power/power_tuna.c
[Samsung Galaxy Nexus] Charmacas:
In my case the target load value could be changed with another app because Trickster can't handle a value like "70 80:920000 95 1200000".

The other thing is that the max frequency does not stick. If I set it to something else than 1200, right after my screen was turned off for the first time it's back to that.

I looked into the power_tuna.so and there is a line which sets the CPU speed. How could I change that? Because besides some usual letters which I can read there is binary code which I cannot. I suppose that's what causing it.

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] metalspring:
That's the problem with power_tuna.c, it must be changed in source or replaced with a different version (also needing to be built from source)

Everything else can easily be changed via ramdisk editing
[Samsung Galaxy Nexus] Shambola:
I rolled back due to wi fi hotspot issue...
[Samsung Galaxy Nexus] Nemed:
Ok so, i updated the init.d script. I added minfree settings, general i/o tunables, scheduler tunables, set target_loads to 85 and fixed the color multiplier issue (thanks [MENTION=4544860]osm0sis[/MENTION] again xD). I think it's complete now :D

Download

As always copy to /etc/init.d and set permissions to -rwxr-xr-x

Type in terminal emulator:

su
chmod 755 /etc/init.d/95nephsettings

EDIT: fixed minfree settings.

EDIT2: fixed max cpu freq
[Samsung Galaxy Nexus] lordofazeroth:
On my device there is

"noop deadline sioplus cfq [row] bfq" in the file. Meaning row is selected.

Using "echo "fiops" > /sys/block/mmcblk0/queue/scheduler"

overwrites the file, right?
[Samsung Galaxy Nexus] abhishek93:
Guys i think you can help me.. I have used this kernel but battery life is not good for me.. 11hours of use with 2hrs OST... Few days back it was all good..

Right now using vanir default kernel and battery life is same as this kernel.. Don't know what is happening to my phone.. and one more thing my port is also not working properly it always shows carging (USB)..
[Samsung Galaxy Nexus] chongns:
[MENTION=4315955]Nemed[/MENTION]

i have 2 governor in /sys/devices/system/cpufreq

what have i doen wrong ?