yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] pikachu01:
Weird. This is the exact results that I've obtained, which is Linux LMK can be set successfully while Dalvik LMK doesn't budge.

I'm not sure how snapx installed his in JW5. snapx, are you sure you're on JW5? Can you post a screenshot of your About Phone?
[Android Software/Hacking General [Developers Only]] geokilla:
Even if they're different in terms of values? Because I know you tweak your own values on some of the stuff in ThunderBolt, which might conflict with the values in the kernel and/or ROM.

Btw, what Bolt Script should we run now? I'm gonna assume the OP is still valid?
[Android Software/Hacking General [Developers Only]] pikachu01:
How different in terms of values?

It depends on how you see it. If you want, you can experiment with ThunderBolt! values and see if it works better for you?

You should run the zipalign, the remount (based on your phone) on boot and sqlite_optimize once in a while.
[Android Software/Hacking General [Developers Only]] carbonassassin:
Hey There, I was Wondering if you would give me permission to include this script in my Tweak app for the Galaxy Note (Carbon Tweaks) ? :) All Credits would be given
[Android Software/Hacking General [Developers Only]] :
pikachu01, why don't include a /efs optimizing script? Just to deny write permissions to the nv_data.bin. This will fix maybe a lot of problems of imei lost. Just like this: "chmod 500 /efs/nv_data.bin". Just running as root on a script in the bolt_scripts folder. I think it could be very useful for a lot of people, my imei isn't taking a 10+ minutes break anymore.
[Android Software/Hacking General [Developers Only]] zeppelinrox:
New V6 SuperCharger values.

You're probably using an Update 9 RC9 test?

Old V6 SuperCharger values.

You're probably using Update 8 which is almost a year old :p

Newest version is sticky :D
[Android Software/Hacking General [Developers Only]] pikachu01:
Even if it's old or new, the point was that the Dalvik LMK didn't get set even with Supercharger. Do you know why that is the case?
[Android Software/Hacking General [Developers Only]] zeppelinrox:
The output from snapx is fine.

Everything sticks, no?

The line at the end is weird tho: [ro.CONTENT_PROVIDER_MEM]: [14]

That didn't come from supercharger - since it won't apply content_provider settings for anything above froyo.
[Android Software/Hacking General [Developers Only]] pikachu01:
I mean the output from ZaneZam. I'm doubting that snapx is using XWJW5, as Dalvik LMK cannot be set on XWJW1 and above.
[Android Software/Hacking General [Developers Only]] zeppelinrox:
snapx already stated he's on the JW5 but I guess you think that's wrong.

And honestly, I have no clue as to what these things are :D

I assume they're gingerbread roms.

Even tho they do both have that weird [ro.CONTENT_PROVIDER_MEM]: [14] entry.

What do the build.props on these roms look like?
[Android Software/Hacking General [Developers Only]] pikachu01:
Yeah, XWJW5 is a gingerbread ROM. Starting from XWJW1 to XWJW4,XWJW5, the Dalvik LMK cannot be set by conventional means.

You can disregard the CONTENT_PROVIDER_MEM. It's a typo bug in init.rc present in all gingerbread ROMs.

The build.prop is just like any other. No setting of LMKs in there though.
[Android Software/Hacking General [Developers Only]] zeppelinrox:
So it won't load the ADJs from build.prop?

I guess that would mean that values are loaded from init.rc before loading build.prop values.

Is the activity manager java source basically the same as most gingerbread roms?
[Android Software/Hacking General [Developers Only]] geokilla:
Are the two scripts being run correctly? I don't think they are...
[Android Software/Hacking General [Developers Only]] pikachu01:
Yes they are :)
[Android Software/Hacking General [Developers Only]] pikachu01:
I've tried the init.rc method and it doesn't work as well. :/ I haven't taken a look at the activity manager source yet, hence I can't comment.

Hey carbonassasin, I would be glad if you can integrate it onto your Tweak app. Just wanted to confirm that this would be not for profit right? If it does, I'd prefer to be told upfront.

Thanks!

I'm not so sure about this. Messing with the EFS (especially on different phones could have dire consequences. I can make a script for that if someone requests it, though I wouldn't want to distribute it to everyone unless it is compatible with all phones.
[Android Software/Hacking General [Developers Only]] snapx:
Hello, I use the version V6_SuperCharger_for_Android-Update9_RC8.2 and these are the screenshots:
[Android Software/Hacking General [Developers Only]] carbonassassin:
Its a free app currently on xda only :)

Sent from my GT-N700 running CM9 and Carbon Tweaks
[Android Software/Hacking General [Developers Only]] pikachu01:
I see that the baseband is XXJW4 and it's a different XWJW5 version (the other one I had was from Slovakia). I'll flash your XWJW5 and see if LMK can be applied there or not.

Ok. Then it's fine with me :)

Let me know if this changes.
[Android Software/Hacking General [Developers Only]] snapx:
I download the version Hungary of the page samfirmware
[Android Software/Hacking General [Developers Only]] pikachu01:
Got it. Will be applying that ROM and testing it out. ZaneZam, if you're seeing this, can you do the same test and see if it works on your side? :)

Thanks!
[Android Software/Hacking General [Developers Only]] spambayes:
Hi Pika,

I'm running XWJW1 with the latest V6 Test16 using build.prop method. Here're my values:

$ getprop | grep ADJ

[ro.FOREGROUND_APP_ADJ]: [0]

[ro.VISIBLE_APP_ADJ]: [3]

[ro.PERCEPTIBLE_APP_ADJ]: [2]

[ro.HEAVY_WEIGHT_APP_ADJ]: [4]

[ro.SECONDARY_SERVER_ADJ]: [6]

[ro.BACKUP_APP_ADJ]: [7]

[ro.HOME_APP_ADJ]: [1]

[ro.HIDDEN_APP_MIN_ADJ]: [9]

[ro.EMPTY_APP_ADJ]: [15]

$ getprop | grep MEM

[ro.FOREGROUND_APP_MEM]: [2048]

[ro.VISIBLE_APP_MEM]: [3584]

[ro.PERCEPTIBLE_APP_MEM]: [1024]

[ro.HEAVY_WEIGHT_APP_MEM]: [14080]

[ro.SECONDARY_SERVER_MEM]: [14080]

[ro.BACKUP_APP_MEM]: [17920]

[ro.HOME_APP_MEM]: [1024]

[ro.HIDDEN_APP_MEM]: [17920]

[ro.EMPTY_APP_MEM]: [25600]

[ro.CONTENT_PROVIDER_MEM]: [14]

$cat /sys/module/lowmemorykiller/parameters/minfree

2048,3584,14080,17920,21760,25600

$ cat /sys/module/lowmemorykiller/parameters/adj

0,3,6,10,12,15

Hope that helps. :)
[Android Software/Hacking General [Developers Only]] ZaneZam:
SURPRISE!

Quick report: just tried V6 test16 too and now it seems

also to work on XWJW6!! (using also build.prop)

values are now:

getprop | grep ADJ

[ro.FOREGROUND_APP_ADJ]: [0]

[ro.VISIBLE_APP_ADJ]: [3]

[ro.PERCEPTIBLE_APP_ADJ]: [2]

[ro.HEAVY_WEIGHT_APP_ADJ]: [4]

[ro.SECONDARY_SERVER_ADJ]: [6]

[ro.BACKUP_APP_ADJ]: [7]

[ro.HOME_APP_ADJ]: [1]

[ro.HIDDEN_APP_MIN_ADJ]: [9]

[ro.EMPTY_APP_ADJ]: [15]

getprop | grep MEM

[ro.FOREGROUND_APP_MEM]: [2048]

[ro.VISIBLE_APP_MEM]: [3072]

[ro.PERCEPTIBLE_APP_MEM]: [1024]

[ro.HEAVY_WEIGHT_APP_MEM]: [10496]

[ro.SECONDARY_SERVER_MEM]: [10496]

[ro.BACKUP_APP_MEM]: [12288]

[ro.HOME_APP_MEM]: [1024]

[ro.HIDDEN_APP_MEM]: [12288]

[ro.EMPTY_APP_MEM]: [16128]

[ro.CONTENT_PROVIDER_MEM]: [14]

cat /sys/module/lowmemorykiller/parameters/minfree

2048,3072,10496,12288,14336,16128

cat /sys/module/lowmemorykiller/parameters/adj

0,3,6,10,12,15

@zeppelinrox

you know your script(s) very well, hmm!? :rolleyes: Jup exactly you got me, i accidentally used the old version update 8! :)
[Android Software/Hacking General [Developers Only]] pikachu01:
I tried zep's update 16 on my XWJW5 (Slovakia) and it didn't work. At this point I'm thinking that it's either a kernel issue or a ROM issue.

What kernel are you using when successfully installing the LMK values?
[Android Software/Hacking General [Developers Only]] ZaneZam:
That was semaphore 2.7.4sbf. I will try midnight mngb-0.5.5 as well and let you know! ;)
[Android Software/Hacking General [Developers Only]] spambayes:
Semaphore all the way. 2.5.0bm at the moment.
[Android Software/Hacking General [Developers Only]] pikachu01:
I'll flash XWJW6 and see if it works. Though I'm waiting for Boeffla (sp?) Mod to arrive for it ;) looking at you Zane :P
[Android Software/Hacking General [Developers Only]] ZaneZam:
Will see what i can do pika. :)

I really can't stand that stock bat icons any more so maybe @weekend(?) ;)

But you know that time problem, right?

btw. after "sorting out" a "little" problem with midnight kernel version mngb-0.5.5 i was able to test supercharger now and it works with this kernel too (with build.prop method). So we have now semaphore and midnight where properties get sticky by using build.prop method on at least JW6 for now. ;)

UnLedded multitasking(512) values from supercharger RC9_Test16 after reboot:

getprop | grep ADJ

[ro.FOREGROUND_APP_ADJ]: [0]

[ro.VISIBLE_APP_ADJ]: [3]

[ro.PERCEPTIBLE_APP_ADJ]: [2]

[ro.HEAVY_WEIGHT_APP_ADJ]: [4]

[ro.SECONDARY_SERVER_ADJ]: [6]

[ro.BACKUP_APP_ADJ]: [7]

[ro.HOME_APP_ADJ]: [1]

[ro.HIDDEN_APP_MIN_ADJ]: [9]

[ro.EMPTY_APP_ADJ]: [15]

getprop | grep MEM

[ro.FOREGROUND_APP_MEM]: [2048]

[ro.VISIBLE_APP_MEM]: [3584]

[ro.PERCEPTIBLE_APP_MEM]: [1024]

[ro.HEAVY_WEIGHT_APP_MEM]: [10240]

[ro.SECONDARY_SERVER_MEM]: [10240]

[ro.BACKUP_APP_MEM]: [12800]

[ro.HOME_APP_MEM]: [1024]

[ro.HIDDEN_APP_MEM]: [12800]

[ro.EMPTY_APP_MEM]: [19200]

[ro.CONTENT_PROVIDER_MEM]: [14]

cat /sys/module/lowmemorykiller/parameters/minfree

2560,4096,6144,10240,11264,12288

cat /sys/module/lowmemorykiller/parameters/adj

0,1,2,7,14,15

@zeppelinrox if you read this: before you complain, yes minfrees don't match! :). These are the tweaked values from init.rc of midnight kernel. Your script was so kind and presented me a solution for this problem and now i have 100% charge, thx! :) But the important point is the properties get sticky with your build.prop method!

Hope you can bring up your lmk addon again pika and i hope your relation to your GF doesn't suffer because of taking away her phone to test this GB stuff, hehe... or did you get another one? (i mean phone! *g*)

good night.. at least for me :)
[Android Software/Hacking General [Developers Only]] pikachu01:
Oh wait. It works with the build.prop method? Does it with with local.prop?
[Android Software/Hacking General [Developers Only]] iamjerry123:
How do I know if this updated?

By the way, I don't have to remove the previous script I had to upgrade it right? I can just overwrite it?
[Android Software/Hacking General [Developers Only]] pikachu01:
If the script works, it'll automatically overwrite the files. It is smart enough to know that it copied it (except if you don't have the disk space for it).

You don't need to remove the previous script.

If you really want to know whether its updated, you'll have to compare the zip files and the files it copied.
[Android Software/Hacking General [Developers Only]] ZaneZam:
Nope, it only worked with build.prop
[Android Software/Hacking General [Developers Only]] spambayes:
Just finished a wipe and re-flashed JW1 and reinstalled V6 again, this time with local.prop. Here:

getprop | grep ADJ

[ro.FOREGROUND_APP_ADJ]: [0]

[ro.VISIBLE_APP_ADJ]: [3]

[ro.PERCEPTIBLE_APP_ADJ]: [2]

[ro.HEAVY_WEIGHT_APP_ADJ]: [4]

[ro.SECONDARY_SERVER_ADJ]: [6]

[ro.BACKUP_APP_ADJ]: [7]

[ro.HOME_APP_ADJ]: [1]

[ro.HIDDEN_APP_MIN_ADJ]: [9]

[ro.EMPTY_APP_ADJ]: [15]

getprop | grep MEM

[ro.FOREGROUND_APP_MEM]: [2048]

[ro.VISIBLE_APP_MEM]: [3072]

[ro.PERCEPTIBLE_APP_MEM]: [1024]

[ro.HEAVY_WEIGHT_APP_MEM]: [9728]

[ro.SECONDARY_SERVER_MEM]: [9728]

[ro.BACKUP_APP_MEM]: [11520]

[ro.HOME_APP_MEM]: [1024]

[ro.HIDDEN_APP_MEM]: [11520]

[ro.EMPTY_APP_MEM]: [15104]

[ro.CONTENT_PROVIDER_MEM]: [14]

cat /sys/module/lowmemorykiller/parameters/minfree

2048,3072,9728,11520,13312,15104

cat /sys/module/lowmemorykiller/parameters/adj

0,3,6,10,12,15

Just for your comparison. :)
[Android Software/Hacking General [Developers Only]] pikachu01:
So local.prop does work in JW1, but doesn't work for JW4/JW5/JW6?
[Android Software/Hacking General [Developers Only]] ZaneZam:
Seems so, jep!

Just tried again with no luck on JW6.
[Android Software/Hacking General [Developers Only]] spambayes:
Hmm. I thought JW1-JW6 are all Value Pack and exhibit the same behaviour.:confused:
[Android Software/Hacking General [Developers Only]] Steven6489:
Hi all,

I'm newbie to this script..there is a question I wanted to know..

I did the following steps provided in 1st page, but what does it mean? what happen when I set it as Root and Boot?

Open up Script Manager and launch /etc/bolt_scripts/remount[device] (e.g. remounti9000) as Root (The skull icon) and as Boot (The wheel icon).

Open up Script Manager and launch /etc/bolt_scripts/sqlite_optimize as Root (The skull icon).

Open up Script Manager and launch /etc/bolt_scripts/s70darky_zipalign as Root (The skull icon).

Open up Script Manager and launch /etc/bolt_scripts/CFS/S98CFS as Root (The skull icon) and as Boot (The wheel icon)..

If I want to run specific script when system boot, I need to move the script to init.d? Example : TCP_Buffers script..
[Android Software/Hacking General [Developers Only]] pikachu01:
It seems that it's not. I'll revamp the whole LMK to use build.prop instead. This would also mean that it'll be hard to remove it later on with just a CWM updater_script. I'll need to think more about this.

You can use Script Manager for that, no need to move/copy etc. That's how easy it is. Setting it as root and boot is the equivalent of moving it to init.d.

Only way why some scripts require Script Manager is that init.d doesn't allow it to be booted at a later stage. We use Script Manager so that some values are only applied later in the boot stages.
[Android Software/Hacking General [Developers Only]] Steven6489:
Thanks for your reply..

So what is the difference between Set as Root and Boot? When I need to set Root and when I need to set Boot? Depends on script?
[Android Software/Hacking General [Developers Only]] pikachu01:
It depends on the script. Set as Root means give root permission (all scripts need this). Set on Boot means run it at boot. It's pretty clear cut right? Judging from the names itself :/
[Android Software/Hacking General [Developers Only]] Steven6489:
Ok..so in the future, if I want to disable some scripts, I can go to Script Manager there to remove the Root and Boot right?

Sorry pikachu01 if I'm asking noob questions as I really have no idea about scripting.. :(
[Android Software/Hacking General [Developers Only]] pikachu01:
Yes, that's right :)
[Android Software/Hacking General [Developers Only]] Steven6489:
Cool..you are fast in response..

Do your bolt_siyah Script support the latest Siyah v3.3.1?
[Android Software/Hacking General [Developers Only]] pikachu01:
You have to edit the bolt_siyah script to get what you want it to do. For now, most of everything can be done in ExTweaks, so I myself don't use it as well.
[Android Software/Hacking General [Developers Only]] Steven6489:
Ok..understand..so basically, I just flash the ThunderBolt-CWM v2.7.6.zip and set Root/Boot by following your installation instruction will be sufficient for the newbie like me right?
[Android Software/Hacking General [Developers Only]] pikachu01:
Yup. What ROM you're using? You probably can flash the screenstate_scaling addon as well.
[Android Software/Hacking General [Developers Only]] spambayes:
This is major good news! Thanks! :D
[Android Software/Hacking General [Developers Only]] Steven6489:
I'm using Foxhoud Sniper Wolf with Siyah 3.3.1..
[Android Software/Hacking General [Developers Only]] pikachu01:
That's an AOSP ROM, hence you can only use the main CWM.
[Android Software/Hacking General [Developers Only]] Steven6489:
Thanks for your script..so far its running good..
[Android Software/Hacking General [Developers Only]] carlos67:
Please forgive my ignorance :o

i9100 running Wanam 11.9 with Siyah 3.2.7.2 (performance profile in exTweaks using Ondemand with SIO). Everything else default Siyah.

I'm thinking of installing this and running the following as root and boot....

1. Main script (obviously - but do I need to comment any part of it out though??)

Additional scripts....

2. S70darky_zipalign

3. Drop

4. sqlite_optimise

5. S98bolt_siyah

6. remounti9100

Is there anything else I could/should run or anything in my list you think I should not use? Only have S98Mass_storage in init.d at the moment.

Any guidance gratefully received. Btw, only issue I have at the moment is slight lag of maybe 2 secs when unlocking to homescreen, but this only happens after a period of deep sleep (doesn't happen if unlocking after only a few moments of screen off)

Thanks :)
[Android Software/Hacking General [Developers Only]] pikachu01:
No need to comment out anything :)

The sqlite_optimize will slow down boot if enabled at boot.

The S98bolt_siyah doesn't have anything set unless you edit it. :) The drop script are ran ondemand when you feel that you need more free memory.

You should try screenstate_scaling to see if it makes your battery life better.

Also, can you described the lockscreen lag? Is it once you unlocked, you feel lags? Or the moment of pressing power and the screen comes on, you lag?
[Android Software/Hacking General [Developers Only]] pikachu01:
Also, I've tried using build.prop for i9000 and SGSII. Both of them stick correctly. :)

It means I was wrong in my initial research about Dalvik LMK not applying using local.prop. It works using build.prop.

There's a catch though. You'll need to restart twice (when the init.d script runs for the first time).

Also, I prefer for the edited build.prop to be restored manually. I can't be sure if the restore pack would do something bad if used on certain configurations.
[Android Software/Hacking General [Developers Only]] carlos67:
Thanks for your reply Pikachu, and great work, thanks :)

Will not run sqlite_optimise on every boot - maybe manually run once a week perhaps (same as zipalign).

Is there any reason not to run drop script on every reboot? What harm can it do?

I want to try screenstate scaling - my main priority is a smooth ui, rather than getting the very last drop from my battery as I have the sammy 2000mAh battery anyway which lasts 2-3 days with my light usage.

I will probably not use S98bolt_siyah, and instead continue with Performance profile setting in exTweaks. Although I'm not too sure what this setting changes:confused:

Bearing in mind my prefernce for smooth lag free ui over battery, would you suggest sticking with Ondemand scheduler with SIO(stock Siyah values), or, would you recommend changing to Pegasusq governor and if so, with which scheduler and settings?

The lag I have is not when pressing home button to wake the phone (I understand there will always be a 0.65 sec lag due to hardware limitations) but when swiping to unlock to the homescreen(from widgetlocker). Its only an issue after the device has entered deep sleep. Once I'm at the homescreen the phone is silky smooth and stable. Didn't have this 2 sec lag issue with widgetlocker on GB.

Sorry for the long post and thanks for your help and any suggestions. :)

Please keep up the excellent work.

Edit: Can I use notepad++ instead of Vim to edit screenstate script?
[Android Software/Hacking General [Developers Only]] iEmDan:
You think you can make this work with the Sidekick 4G?
[Android Software/Hacking General [Developers Only]] pikachu01:
I'm not sure. I don't have the device so you'll need to test it out. Be sure to have a nandroid backup beforehand :)
[Android Software/Hacking General [Developers Only]] :
What is the CFS script? Didn't understand what is... What's the pros and cons of executing?
[Android Software/Hacking General [Developers Only]] pikachu01:
1. No harm can be done by running it at every boot, though its primary purpose is to be a one-shot memory freeing script.

2. Screenstate_scaling won't jeopardize the performance when the screen is on. Only when the screen is off.

3. Performance setting will change the GPU stay count, the hotplug frequency (which is not used when selecting pegasusq) and some pegasusq settings (which is not used if you're using screenstate_scaling/ThunderBolt! main CWM)

CFS script tweaks the scheduler based on having a lower granularity, and lower latency as well. In most cases it should improve performance while keeping latency to a lower level (while still maintaining) throughput.
[Android Software/Hacking General [Developers Only]] spambayes:
This is good news! Manual restoration is fine as long as we have the instructions. :D

Sent from my GT-I9000
[Android Software/Hacking General [Developers Only]] xXCorleoneXx:
I can use thunderbolt and V6 Supercharger in a rom?

I am using 5.1.2 ICS VK Rom.
[Android Software/Hacking General [Developers Only]] liewkingyan:
Reserved

Sent from my GT-N7000
[Android Software/Hacking General [Developers Only]] liewkingyan:
sorry im new to thunderbolt.

If i flash the thunderbolt zip do i still have to flash the addons?

what are the add ons for?
[Android Software/Hacking General [Developers Only]] pikachu01:
I'll upload it now with the instructions to remove. :)

You can use it together. Though you can't use the LMK addon with V6 Supecharger. Either use the LMK addon or the V6 Supercharger.

The addons are optional. You can look at the addons' description in the 2nd post.
[Android Software/Hacking General [Developers Only]] pikachu01:
News

Updated the LMK to use build.prop instead of local.prop. It now works for ICS I9100 as well as JW4/JW5/JW6 I9000. Also updated restore pack and LMK addon with automounter.

Changelog:

13/6/2012(LMK 2.0.0 and restore packs 1.2.0)

- Updated LMK to use build.prop method. Older build.prop will be backed up in /system/build.prop.thunderbolt.

- To apply the LMK changes, you'll need to restart twice. Once to modify the build.prop, another to load the modified build.prop

- To restore the build.prop, just copy over build.prop.thunderbolt to build.prop

- Updated restore packs with automounter by iXNyNe.
[Android Software/Hacking General [Developers Only]] spambayes:
Thank you!! Btw, I'm assuming this also works for JW1 too?

Which restore pack should I use for JW1?
[Android Software/Hacking General [Developers Only]] pikachu01:
The stock i9000 restore. Yes this should work with JW1.
[Android Software/Hacking General [Developers Only]] spambayes:
Just confirmed this. Yes, LMK now works fine on JW1. Thanks again. :)
[Android Software/Hacking General [Developers Only]] snapx:
thank you very much for your work pikachu :), now if that works. I've spent at the JW6 and also works very well.
[Android Software/Hacking General [Developers Only]] :
Can you explain what LMK I need to choose? 40, 50, 60 or 80? Don't know how each one runs... And instructions, I don't know much about this...
[Android Software/Hacking General [Developers Only]] ZaneZam:
Just tested and indeed (actually as expected *g*) it's working again here on JW6! Very nice, thank u pika! Now we can enjoy the FULL flash of thunderbolt again! :)

btw. boeffla is on the way... ;)

c ya
[Android Software/Hacking General [Developers Only]] :
btw, there's some errors while executing the S98system_tweak. Here's parts of the logcat

I/run-parts( 1704): sysctl: error: 'net.ipv4.tcp_syncookies' is an unknown key

I/run-parts( 1704): net.ipv4.ip_dynaddr = 0

I/run-parts( 1704): kernel.sem = 500 512000 100 2048

I/run-parts( 1704): kernel.shmmax = 268435456

I/run-parts( 1704): kernel.msgmni = 1024

I/run-parts( 1704): /system/etc/init.d/S98system_tweak[490]: cannot create /sys/kernel/debug/sched_features: No such file or directory

I/run-parts( 1704): /system/etc/init.d/S98system_tweak[491]: cannot create /sys/kernel/debug/sched_features: No such file or directory

I/run-parts( 1704): /system/etc/init.d/S98system_tweak[492]: cannot create /sys/kernel/debug/sched_features: No such file or directory
[Android Software/Hacking General [Developers Only]] borjaag:
Does it works on JW6?

Enviado desde mi GT-I9000 usando Tapatalk 2
[Android Software/Hacking General [Developers Only]] snapx:
Yes, it works very well in JW6, I have that rom.