yashsingh1/xdaforums huggingface dataset:
[Nexus S General] ekerazha:
The current Android version for Nexus S (4.1.1) is too much bugged to be the last release. I expect a 4.1.2 or a 4.2 version. Or a Lumia 920.
[Nexus S General] apatal:
I'd still like to think that my Nexus S will get the KLP update. After all, 4.2 is not that big an update from 4.1. If however, for some reason Google chooses to drop support for the crespo for that, I won't really blame them as the Crespo has definitely seen better days, and as a veteran for the Android cause, no one can say it hasn't been utilized to its fullest. :)

Posted using xda mobile app
[Nexus S General] Mark2dp:
In my opinion Jelly Bean is, with high probability, the last update we will receive.

Anyway I don't think Google will announce another Android version since the 4.1 was release only 3 months ago!
[Nexus S General] Articudos:
Well,

This is just rumor:p

http://www.androidpolice.com/2012/1...w-phone-and-a-new-nexus-tablet-both-motorola/
[Nexus S General] oldblue910:
Someone's trolling Android Police's server logs. JOO92 is an invalid build number. Build numbers don't go higher than 90. JOO92 would be JOP02. Notice in the Android Police article, they show both JOO92 AND JOP02. Hmmm...sounds like someone realized the build number wasn't right, updated it, and hit the site again. This is total troll material.

Another piece of circumstantial evidence (though it may mean nothing)..."O" is a heretofore unseen branch identifier. We know "R" (like JRO03C, GRJ22, etc) is the release branch. We've also seen T (GTJ61), F (JFN53N), W (HWI69, GWK74), C (ICL53F), M (IML74K), and maybe a few others, but I don't think "O" is one that has been used before. Again, doesn't necessarily mean Google doesn't use it for something, but whatever.

The only point here is that the troll gave himself up with JOO92. Fail. BS.
[Nexus S General] giaomnitel1:
I do not think it is "too much bugged", but there is still something not working properly...

As you said, it would not be so much good if JB 4.1.1 is the latest build for our Nexus S...
[Nexus S General] styckx:
After just getting a Nexus 7 I'm even more convincing the Nexus S will never see 4.2.. Jellybean is absolutely amazing on high end hardware... Ermagerd! Love my Nexus S but I just had a reality check. :laugh:
[Nexus S General] oldblue910:
Yeah, Jelly Bean runs amazingly well on the Galaxy Nexus and the Nexus 7. It turned the Xoom into a brand new tablet. The Nexus S, not so much. You can tell the hardware has a hard time with it.
[Nexus S General] simonb255:
Realized the same and sold my nexus s and got a gnex
[Nexus S General] albundy2010:
Can we at least wait until the next update is announced before saying we want it? Or a least shown in some way or another.
[Nexus S General] FirePoncho86:
I think the ns will get 4.2, maybe a 'light' version, but I think we will get it. But if they release something like 5.0, there's no way
[Nexus S General] hlxanthus:
Most of the rumors I have heard are saying that 4.2 will still be jellybean. Try googling "project roadrunner"
[Nexus S General] giaomnitel1:
If the 4.2 is still Jelly Bean, we can still hope we will get it ...
[Nexus S General] hp420:
guys, the n1 just lost support with jb, and afaik, the devs even still managed to hack the crap out of it to make it load....I think it'll be a cold day in hell before devs give up on ns since it's still under 2 years old.
[Nexus S General] oldblue910:
Incorrect. The Nexus One lost support with Ice Cream Sandwich. The N1's last official OTA from Google was Gingerbread, 2.3.6/GRK39F.
[Nexus S General] Talal916:
I think the Nexus S is done, but I'm happy with the two major updates we got (ICS & JB). We've gotta be thankful that the Nexus S/4G got more support over it's lifetime than most manufacturers do with their whole line of phones. :good:
[Galaxy S Plus I9001 Android Development] hiej:
ADDONS - FIXES - UPDATES

APP PACKS

1.TW3 Launcher Final <--- click to download

Bugless, fast and clean, graphically not up to date...​

2.TW4 Launcher Final <--- click to download

Lookings better UI in comparison to TW3 launcher​

3.TW4.5 Launcher Final <--- click to download

Lookings like TW4, but full customizable, it can perform 5 links on doc menu, shows active apps, temable...

Hint:The dock of TW4.5 launcher should be configured at first boot, put the icons you want (phone, contacts, messages etc...) dragging icons you want from the app drawer to the dock.​

Note: applying this addons, you must reconfigure your home screen links and widgests after first restart

KERNELS

1.Stock tweaked KQI Kernel <--- click to download

This is the Stok kernel of Ginger Revenge ROM, supports custom boot animation, init.d scripts.

It works very fine with good performances level and good battery​

2.Feacore Kernel sOCL <--- click to download

This is the Feacore kernel with overclok capability up to 1800 MHz.

It features more governors and schedulers than stock KQI kernel.

I've done a mod so that it's default clock is 1400 MHz instead of 1800, you can set higher or lower frequencies using cpu control apps.​

3.BroodKernel 1.3 sOCL <--- click to download

This is the BroodKernel 1.3 with overclok capability up to 1800 MHz.

It features more governors and schedulers than stock KQI kernel, Virtual RAM (SWAP) possible, No JPEG compression (HQ photo's)

I've done a mod so that it's default clock is 1400 MHz instead of 1800, you can set higher or lower frequencies using cpu control apps.​

4.SkyHigh Kernel 1.4d <--- click to download

This is the SkyHigh Kernel with overclok capability up to 1800 MHz.

It features more governors and schedulers than stock KQI kernel, Virtual RAM (SWAP) possible, HQ photo's, it contains by default a lot of tweaks like V6 Supercharger, Tunderbolt, Zipalign, Battery and SD Card Improvement etc.

For this reason no tweak scripts ar loaded on init.d folder, because apply tweaks twice can produce strange behaviours, so be careful to load additional (and in some cases unuseful) tweak packs with this kernel!

The main advantage using this kernel is UNDERVOLT capabilities, that permits to improve battery life maintaining a good performances level.

See 3rd post a guide and suggestions to apply good voltage values.​

REMOVED APPS PACKAGE

1.Removed Google & Samsung Apps <--- click to download

Removed apps: like Talk, Adilko, animated wallpapers, Samsung apps, etc... (Install package from recovery)​
[Galaxy S Plus I9001 Android Development] hiej:
SkyHigh Kernel Voltage tweaks

A good way to improve battery life is to apply some undervolt to CPU.

On stock kernels is not possible to change the voltage, to do this kind of operation is necessary to use modded kernels like SkyHigh or Vitality.

Personally I prefer SkyHigh because there's no issues with SD cards (but if you like you can follow this suggestions also for Vitality).

To set voltages you need to use apps like, IncrediControl, SetCPU, AnTuTu CPU Master, etc... search them on play store

Looking on the following graphic, you can see that SkyHigh kernel does by default (red line) a little undervolt on high clocks compared to stok kernel (black dotted line),

on low clocks the SkyHigh kernel voltage is equal to stock kernel.

My Idea is to try to use more lower voltage values, and based on my esperience using Castagna's Kernel on ICS roms I've seen tha my device works very fine with Extreme UV version.

So I've applied the Castagna's EX-UV voltages values to SkyHigh with absolutely no failures. (See green line).

As you know no all devices are identical, some are more low voltage friendly, some with too low voltages does not boot or not works properly.

So maybe instead to use EX-UV voltages you may try Castagna's standard UV values (blue line) that on high clocks is equal to standard SkyHigh.

Or maybe using intermediate values between SkyHigh defaults and Castagna UV / EX-UV.

Hint: after setting voltages vaules prior to stick them @ boot, do a normal usage of your phone for some hours, play games, run benchmarks to do some kind of stressing, verify that the phone is able to wake-up from deepsleep etc... If in normal usage yor are facing to some problems try use less agressive undervolt values, find right UV values is not easy but I think that playing with values between red and green lines of previous graph can be a good starting point.

Hint2: If you're not a gamer and your primary goal is battery saving, limit the clock to 1.4 GHz if you're using SkyHigh kernel.

__________

Credits to:

- Castagna

- Smeroni68
[Galaxy S Plus I9001 Android Development] texten:
good luck :)
[Galaxy S Plus I9001 Android Development] YMYA:
Thanks for your effort :)

Some screenshots would be good..
[Galaxy S Plus I9001 Android Development] tomixdev:
looks pretty cool, good work ;)
[Galaxy S Plus I9001 Android Development] raptor92:
Good work. Working smooth and battery friendly!

Could you add OTA update next version??
[Galaxy S Plus I9001 Android Development] mizuki_kai:
No alert for camera, music etc means can use during the alert time?coz i kind of like this part if it can function during those time.
[Galaxy S Plus I9001 Android Development] major_stitch:
This looks nice, I'll surely try it :)
[Galaxy S Plus I9001 Android Development] Hipo the caos:
Dowload link is disabled now. can anyone upload to another service, please?
[Galaxy S Plus I9001 Android Development] hiej:
another location is in upload, it will be available in about 1 hour.
[Galaxy S Plus I9001 Android Development] DeuxEx:
Hello! I want to test your ROM, but you have a problem with download link:

This account's public links are generating too much traffic and have been temporarily disabled!

My advice: use a torrent link!
[Galaxy S Plus I9001 Android Development] alexpowermetal:
Thats torrent mirror.

Google Drive Mirror
[Galaxy S Plus I9001 Android Development] DeuxEx:
Thank you! I will test this ROM for 24 hours, before drawing my conclusions. What do you use for kernel? The stock kernel or an improved one? It have Overclocking?
[Galaxy S Plus I9001 Android Development] hiej:
Thanks very much Alex ;)

I did not think there were so many downlads ...

Now there's 3 links + 1 torrent on 1st page, hi hope is enough

I hope also that my work lives up to your expectations...

Any criticism, suggestion is welcome
[Galaxy S Plus I9001 Android Development] hiej:
Hi,

on 2nd post the first patch :crying:

it fixes poor image quality using gallery app when zooming pictures.
[Galaxy S Plus I9001 Android Development] nikczemnik:
Nice to see that ginger roms are still alive:) I'm trying your rom now and seems to be very nice piece of gingerbread;). Thx

Wysłane z mojego GT-I9001 za pomocą Tapatalk
[Galaxy S Plus I9001 Android Development] hiej:
I've used stock KQI kernel... the only *improvement* is init.d support.

If you want, you can use custom kernels, I suggest witality or Feacore with OC, and why not also Broodkernel 1.3 that support OC also.

____

In any case it seem's (at least to me but maybe I'm wrong) to that stock KQI kernel is a bit better thant stock KQI, specially for how it concern battery consumption.

In fact I'm waiting comments about battery drain from who decided to test my rom.
[Galaxy S Plus I9001 Android Development] m0e_03:
"stock KQI kernel is a bit better thant stock KQI"..

.. dafuq i just read?? @_@
[Galaxy S Plus I9001 Android Development] hiej:
ops... I mean KQI is better than KQE
[Galaxy S Plus I9001 Android Development] DeuxEx:
Thank you for this update! This launcher is the best!
[Galaxy S Plus I9001 Android Development] sanefirst:
Hi hiej,

I think that something is not working with SD card tweaks (or maybe init.d scripts in general).

When I go to sys/devices/virtual/bdi I can see that all values are still 128, not 512 as in the script.

Moreover, I don't have 179:28 or 179:33, but I have 179:32.

Could you check why it's not working, please?

So far the ROM is very good. I'll test it against heavy games like Dungeon Hunter 3D and report.

Do you advice flashing feakernel?
[Galaxy S Plus I9001 Android Development] hiej:
I'll check, maybe there's a conflict between two or more tweaks scripts.

(to be honest... most of tweaks creating only placebo effect...)

about the use of feacore... imho if you dont need OC it is unuseful.

for me stock kernel works fine.
[Galaxy S Plus I9001 Android Development] sanefirst:
maybe the /sys is mounted as read only before applying tweaks...
[Galaxy S Plus I9001 Android Development] Smantanasiceapa:
hiej I want to flash these audio beats to see how is hears. What file(s) do I have to remove before flashing?
[Galaxy S Plus I9001 Android Development] hiej:
these audio beats are already included in the rom ;)
[Galaxy S Plus I9001 Android Development] sanefirst:
hiej, did you solve the sd card problem?
[Galaxy S Plus I9001 Android Development] hiej:
there's SD card problems ?

in what conditions?
[Galaxy S Plus I9001 Android Development] sanefirst:
Sorry, I meant sd card tweaks. The problem is they are not applied.
[Galaxy S Plus I9001 Android Development] hiej:
ah ok

I dont had time to check sorry
[Galaxy S Plus I9001 Android Development] EternalFame:
i have wifi drops and static ip doesnt fix it ):
[Galaxy S Plus I9001 Android Development] outerh3aven:
Send a pm to op. Please check it. Object: autobrightness

sent from my cardboard box using THE AWESOME ProjectStock 4.0.4
[Galaxy S Plus I9001 Android Development] q123456:
Hi, great rom but have one problem- no frills cpu is not working for me. Can't save changes as app hangs and i must kill. Chainfire hangs also. I have 1.8ghz oc kernel. Pls give any idea what should i do to get things working. Thx

Wysyłane z mojego GT-I9001 za pomocą Tapatalk 2
[Galaxy S Plus I9001 Android Development] hiej:
did you wiped cache and fixed permissions after flashing new kernel?

what kernel are you using ?
[Galaxy S Plus I9001 Android Development] q123456:
yes, i did wipe cache + dalvik and I fixed permissions.

regarding to kernel, i'm using FeaCore phoenix with OC
[Galaxy S Plus I9001 Android Development] hiej:
ok I've found the problem: there's some problems to get root if usb debugging is disabled.

so the solution for the moment is to enable usb debug under develpment settings.

I will fix this on some days (no have time now sorry).

thanks for report. ;)
[Galaxy S Plus I9001 Android Development] q123456:
Ok, i've enabled debugging and now is working. Thank you :)

Now for me it is what i call complete rom :)
[Galaxy S Plus I9001 Android Development] sanefirst:
What about sd card tweaks?

Did someone find a solution to the problem?
[Galaxy S Plus I9001 Android Development] hiej:
About SD Card, I'm looking on script but I dont understand why is not applied.

Init.d support works fine because after boot the test file init.d_log_test.txt is created on /data/local/tmp folder

I have also checked on Gigabread+ rom (is from here I've taken the script) and the behaviour is the same...

so maybe or there's something wrong in the script or there's something that we have not understood...

here follows the script, so please to someone to suggest what's wrong, thank you :)

#!/system/bin/sh

#SD CARD SPEED

READ_AHEAD_KB="512"

if [ -e /sys/devices/virtual/bdi/0:18/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/0:18/read_ahead_kb
fi

if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/179:0/read_ahead_kb
fi

if [ -e /sys/devices/virtual/bdi/179:28/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/179:28/read_ahead_kb
fi

if [ -e /sys/devices/virtual/bdi/179:33/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/179:33/read_ahead_kb
fi

if [ -e /sys/devices/virtual/bdi/7:0/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:0/read_ahead_kb
fi

if [ -e /sys/devices/virtual/bdi/7:1/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:1/read_ahead_kb
fi

if [ -e /sys/devices/virtual/bdi/7:2/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:2/read_ahead_kb
fi

if [ -e /sys/devices/virtual/bdi/7:3/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:3/read_ahead_kb
fi

if [ -e /sys/devices/virtual/bdi/7:4/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:4/read_ahead_kb
fi

if [ -e /sys/devices/virtual/bdi/7:5/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:5/read_ahead_kb
fi

if [ -e /sys/devices/virtual/bdi/7:6/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:6/read_ahead_kb
fi

if [ -e /sys/devices/virtual/bdi/7:7/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:7/read_ahead_kb
fi

if [ -e /sys/devices/virtual/bdi/default/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/default/read_ahead_kb
fi
[Galaxy S Plus I9001 Android Development] sanefirst:
I managed to get it working...

I created a separate file: 98sdfix and I put above code in that (in the same time I removed the code from 00revengetweaks).

After reboot the buffer is 512.

I am now wondering if other scripts work well... Is there any possibility to check that?

---------- Post added at 10:37 AM ---------- Previous post was at 09:41 AM ----------

I performed some test and I'm sure that 00revengetweaks are not applied, while other scripts are.

I put a

touch /data/local/tmp/test_[COLOR="Red"]xx[/COLOR].txt
echo "WORKS" > /data/local/tmp/test_[COLOR="Red"]xx[/COLOR].txt

in the end of every script and it created txt files for 01 (kernel tweaks), 06 (supercharger) and my 98 (sdfix).

The file for 00 (GR tweaks) is not created...
[Galaxy S Plus I9001 Android Development] Loca Toni:
arabic language ????????????
[Galaxy S Plus I9001 Android Development] hiej:
thank you very much sanefirst, this evening I'll check your suggestion to fix it.

I have to check also why there's root problems if usb debugging is turned off...

-----

@ Luca Toni

arabic support is enabled but is missing keyboard and input language it's right?

I'll try to add missing things on next release.
[Galaxy S Plus I9001 Android Development] athankar75:
Questions

I have this Rom 1 day, so far seems stable and fast. I dont know why i have almost 5700 score in antutu but only 1650 in quadrant.Small complains no options for smartass and sio in kernel and for my taste the ugliest battery bar ever!
[Galaxy S Plus I9001 Android Development] sanefirst:
SIO and smartass are not supported by Samsung Kernel...
[Galaxy S Plus I9001 Android Development] hiej:
you mean the battery simbol or battery drain?

in 1st case I agree with you, I'm thinking to change it.
[Galaxy S Plus I9001 Android Development] athankar75:
I mean the symbol only, drain seems ok but i will find out after few days.
[Galaxy S Plus I9001 Android Development] hiej:
Hi,

I've done same things as you, but for me is not working...

the

/data/local/tmp/test_98.txt is createt and contains "WORKS" but buffer still = to 512

I'm going crazy... :(
[Galaxy S Plus I9001 Android Development] sanefirst:
But buffer should be 512. If it is 512 now, then it works.
[Galaxy S Plus I9001 Android Development] hiej:
sorry, i was wrong... is still to 128

...i'm thinking to discontinue this rom and leave this kind of stuff to pro people :(

...on 1st post the link to previous release, less bugged (0.96) than final

____________________________________________

A question: it is normal that is not possible to have superuser permission if usb debuggin is turned off?

I'm triyng various Gb roms and on all if USB debugging is off is not possible to have root pemission...

if that it's normal final version is not bugged about root permission...
[Galaxy S Plus I9001 Android Development] sanefirst:
Hey man, don't give up! This ROM is very good and it's the only KQI rom, cause Blazr is ****ty. Just need some polishing.

Permissions for the 98sdfix set to 777?
[Galaxy S Plus I9001 Android Development] DeuxEx:
Don't give it up, man! I don't know why you think that 1.0 version is full of bugs. I use it from day one when you relese it and I think that you made a hell of a job. Good work, more stable than 0.9.6! I have fate on you that you will make things better in your next relese. If you need a beta tester, just contact me. And I think that are some guys on this thread that can and will give a hand If you need a testing area.
[Galaxy S Plus I9001 Android Development] sanefirst:
This is my file, which 100% works. Permissions: set to all (777)

#!/system/bin/sh

#SD CARD SPEED

READ_AHEAD_KB="512"

if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/179:0/read_ahead_kb
fi;

if [ -e /sys/devices/virtual/bdi/179:32/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/179:32/read_ahead_kb
fi;

if [ -e /sys/devices/virtual/bdi/7:0/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:0/read_ahead_kb
fi;

if [ -e /sys/devices/virtual/bdi/7:1/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:1/read_ahead_kb
fi;

if [ -e /sys/devices/virtual/bdi/7:2/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:2/read_ahead_kb
fi;

if [ -e /sys/devices/virtual/bdi/7:3/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:3/read_ahead_kb
fi;

if [ -e /sys/devices/virtual/bdi/7:4/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:4/read_ahead_kb
fi;

if [ -e /sys/devices/virtual/bdi/7:5/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:5/read_ahead_kb
fi;

if [ -e /sys/devices/virtual/bdi/7:6/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:6/read_ahead_kb
fi;

if [ -e /sys/devices/virtual/bdi/7:7/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/7:7/read_ahead_kb
fi;

if [ -e /sys/devices/virtual/bdi/default/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/default/read_ahead_kb
fi;

touch /data/local/tmp/inittest3.txt
echo "Works OK_99" > /data/local/tmp/inittest3.txt

As you can see, I added ";" after each "fi" and I changed directories to match my device.
[Galaxy S Plus I9001 Android Development] hiej:
thankyou very much sanefirts! now it works.

but imho there's no noticeable improvement in performace using 512...

a better improvement is done using 1024 but there's some issues on management of system files: example is not possible to save changes also if gained root access after modifications to a file on init.d folder...

that happens also with 512 sometimes...

maybe the right thing to do is to set high values only for sd and external sd, and leave value = 128 for the other locations...

that have sense ???
[Galaxy S Plus I9001 Android Development] sanefirst:
Yes, I think you're right...

For me, 2048 gives best results, so now my script looks like that:

#!/system/bin/sh

#SD CARD SPEED

READ_AHEAD_KB="2048"

if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/179:0/read_ahead_kb
fi;

if [ -e /sys/devices/virtual/bdi/179:32/read_ahead_kb ]; then
echo $READ_AHEAD_KB > /sys/devices/virtual/bdi/179:32/read_ahead_kb
fi;

What about other tweaks??? Do yuo have an idea why they are not applied?
[Galaxy S Plus I9001 Android Development] DeuxEx:
@hiej: Don`t worry, mate, I have all my fate in you!

Sent from my Speed3Duo 1,5 GHZ Dual-Core
[Galaxy S Plus I9001 Android Development] athankar75:
Keep it up!!!

3d day with final version and i think is the most stable rom i have ever use. Plz don't stop improving this rom i'm one of many users who prefer stability, battery friendly, lag free and full functionality, which in my oppinion only Gb provide.
[Galaxy S Plus I9001 Android Development] hiej:
I'm testing version 1.12. if all seems ok I will release it friday 21

....

with maya permission :p
[Galaxy S Plus I9001 Android Development] sanefirst:
We're waiting! :)

Did yuo resolve the 00revengetweaks problem?

I'm curious why it's not applied.

PS. In sdcardtweak 179:0 is for everyone, but the second one :179:16 or 179:32) depends on the capacity of the card, so I think the script should also cover those possibilities (possible combinations can be found in /sys/dev/block I think).

PS2. Could you set the deafult i/o scheduler to noop? I believe it is better in terms of performance.