Related
Hey Everyone,
I was just wondering that if we have a build to which we have BOTH RamHack kernels and the non-ramhack kernel, would there be a way to write a quick app or script to switch between them.
I guess we could store both kernels on the /sdcard and use a .sh script to flash_image between them, and reboot. I dont believe we can "hot-swap" between kernels, but if anyone knows a method, please respond here
If anyone can think of a better or more efficient method of doing this, I believe the whole community would benefit. Lets see if we can get something like this going....
zimphishmonger said:
Hey Everyone,
I was just wondering that if we have a build to which we have BOTH RamHack kernels and the non-ramhack kernel, would there be a way to write a quick app or script to switch between them.
I guess we could store both kernels on the /sdcard and use a .sh script to flash_image between them, and reboot. I dont believe we can "hot-swap" between kernels, but if anyone knows a method, please respond here
If anyone can think of a better or more efficient method of doing this, I believe the whole community would benefit. Lets see if we can get something like this going....
Click to expand...
Click to collapse
is it really that hard to boot into recovery and flash an update.zip?
I guess this is what you're looking for:
http://wootroot.com/blog/?page_id=1463
Ive seen it implemented on one other rom on xda, but can't remember which one ..
I am trying to make it easier and more efficient to switch between them. The uneek switch seems exactly what im looking for
I put together a version of uneeks script that can be flashed over SuperD or FastTest3.1.
ISSUE THOUGH, I cant get it to flash correctly, as I get the "update-script not found" error, even though I signed it and created the appropriate META-INF directories.
Here is the file, if anyone thinks they can fix it
Uneek Script (needs to be fixed\signed) : http://www.4shared.com/file/257220832/8b6c2940/uneek.html
Alpha release
Here is a very alpha release of a working port of uneek's RamHack/NonRamHack Toggle script ported to SuperD 1.10.2 by myself.
http://www.4shared.com/file/257253893/a61182a2/Uneek_Script.html
Instructions
extract zip file to /sdcard/uneek
Launch terminal
type 'su'
type 'sh /sdcard/uneek/install-uneek.sh' -should see no errors/messages
execute 'uneek' from /system/bin
Chose Ram option or JIT (not tested) options, all others prob dont work as I didnt modify them
reboot (you must do so to see effects take place, the kernel doesn't "hot-swap" :-( )
WiFi still works, CC & Swap work.
Issues
Switch breaks boot screen - not sure why as its stored in framework-res.apk, but still a bug
Leave me feedback\ improvements\whatever......
You still have to boot into recovery so you might as well flash a zip containing a rhack or noram-hack kernel.
I did some scripts based off Kings,
get gscript from the market ( donate if you like it )
and drop script into the gscript folder
with a little uname query you could have just one script, which switches based on the current running kernel
Edit: , actually if your kernel needs different kernel modules, then you will have to build in a copy ( which I suspect is where king got his rwsystem bit from , he copied from a script which updates the kernel modules )
Firerat said:
...<snip>...
my faster, much safer script
Code:
#!/system/bin/sh
if [ -e /data/kernels/full3d.img ];
then
if [ "`md5sum /data/kernels/full3d.img|cut -d " " -f1`" != "061284119d4ce46cbe0b585e0a8b2d0b" ];
then
echo "/data/kernels/full3d.img isn't the version I was expecting"
echo "I'm not going to flash it, as it may have become corupt"
exit 1
else
flash_image boot /data/kernels/full3d.img
echo "full3d Kernel Flashed..."
echo "Rebooting now"
sleep 1
shutdown -r now
fi
else
echo "Sorry, /data/kernels/full3d.img"
echo "seems to be missing....."
exit 1
fi
and yeah, I could never spell corrupt , is it one or two 'r's?
PS , the md5sums in the scripts are for the power off fix boot.img's I did for you guys
if you are wanting to switch to different boot.imgs then update the md5sum its checking for ( or remove the check )
Click to expand...
Click to collapse
If you have an engineering SPL installed, there isn't any need for the recovery partition, so might as well install your second kernel to the recovery partition. Boot normal = normal, boot recovery = ramhack.
lbcoder said:
If you have an engineering SPL installed, there isn't any need for the recovery partition, so might as well install your second kernel to the recovery partition. Boot normal = normal, boot recovery = ramhack.
Click to expand...
Click to collapse
and then have a script switch wlan.ko if incompatible
might as well switch with script and keep recovery for the odd times when you just want to quickly flash some zips from a list and not at your pc.
yeap, I've downloaded and flashed a rom while 'out and about' before.
Firerat said:
and then have a script switch wlan.ko if incompatible
might as well switch with script and keep recovery for the odd times when you just want to quickly flash some zips from a list and not at your pc.
yeap, I've downloaded and flashed a rom while 'out and about' before.
Click to expand...
Click to collapse
If the only difference is ramhack on one but not the other, then the wlan module will be fine -- there is NO REASON to be switching modules around with your kernel unless you use a kernel that is binary incompatible -- which means DIFFERENT VERSION.
lbcoder said:
If the only difference is ramhack on one but not the other, then the wlan module will be fine -- there is NO REASON to be switching modules around with your kernel unless you use a kernel that is binary incompatible -- which means DIFFERENT VERSION.
Click to expand...
Click to collapse
yeap, true but why not keep options open?
What if they decide they want to switch between binary incompatible kernels?
They would need to switch kernel modules anyway.
so get a script that works, and is simple to 'generate'.
I know you are trying to keep it simple, but you are actually needlessly setting up restrictions, which would then require a script to get around.
So why not use a script from the start, keeping the added convenience of a recovery image?
Firerat said:
yeap, true but why not keep options open?
What if they decide they want to switch between binary incompatible kernels?
They would need to switch kernel modules anyway.
so get a script that works, and is simple to 'generate'.
I know you are trying to keep it simple, but you are actually needlessly setting up restrictions, which would then require a script to get around.
So why not use a script from the start, keeping the added convenience of a recovery image?
Click to expand...
Click to collapse
If the only objective is to be able to easily toggle between ramhack and noramhack, then the recovery solution is (1) more reliable, (2) doesn't require reflashing NAND, (3) just easier to activate. With the reflashing approach, you have to either go into recovery and flash something, or pause-and-wait-and-autoreboot.
lbcoder said:
If the only objective is to be able to easily toggle between ramhack and noramhack, then the recovery solution is (1) more reliable, (2) doesn't require reflashing NAND, (3) just easier to activate. With the reflashing approach, you have to either go into recovery and flash something, or pause-and-wait-and-autoreboot.
Click to expand...
Click to collapse
did you ever read anything?
the script is as easy as a couple of taps, maybe home button, swipe tap tap.
( the key app here is gscript )
the flash is over very quickly, it checks md5sum first, it reboots.
you have to reboot with the recovery method anyway
recovery method restricts to binary compatible kernels, or require a script to switch kernel modules.
It is a no brainer imo, keep it flexible and keep the convenience of a true recovery.img
ok, so nand only gets what, on average 10,000 writes, is it really going to reduce its life in practice?
I like your idea, it will work but it just isn't as flexible as a script.
It is however more suited to an mt3g, offering duel ROM
I'm thinking mtdblock3 for one ROM, block4 for the other
errm, data , yeah might need to section that up somehow
any reason why a loopback can't sit on yaffs?
oh, and the ramdisk will need tweaking, obviously.
Sorry back on topic
Guys,
Either will work, if you do have incompatible kernels, and are having problems with scripts just let me know, I can probably make a script to generate a script for you.
1) Booting into recovery to change out your kernel image is totally unnecessary. You can do it via CLI with the flash_image command -- most every modded ROM already includes it.
2) Removing the recovery image just to put up a second install also seems somewhat overkill for devices as heavily limited on storage as most Android phones -- especially the G1.
3) I don't know about loopback on yaffs2 -- but I don't see any reason why it couldn't work.
4) It really seems to me that what we need is some kernel hacker who's familiar with hotswapping patched files -- a la ksplice ( http://www.ksplice.com/ ) -- to hack together a genuine, non-rebooting, RAMhack switch.
5) In all seriousness; what makes gscript superior to ASE ( http://code.google.com/p/android-scripting )?
IConrad01 said:
5) In all seriousness; what makes gscript superior to ASE ( http://code.google.com/android-scripting )?
Click to expand...
Click to collapse
Nothing, apart from its easy, it works and I haven't looked at ase yet
btw , you missed a p/ in that link
http://code.google.com/p/android-scripting/
btw , you missed a p/ in that link
http://code.google.com/p/android-scripting/
Click to expand...
Click to collapse
>_<
Pesky perniciously persistently phantasmagoric P!!!
I just keep on seeing people referring to gScript when ASE is a vastly more robust offering. It can run its scripts as daemons, run in background, run in terminal, it offers the same desktop shortcut option -- and more importantly, it can run Python, Perl, JRuby, Lua, BeanShell, JavaScript, Tcl, and shell scripts. (It loads the interpreters onto your /sdcard.) I've asked this question more than once before and I've never gotten an answer. It really seems like people just aren't aware of ASE -- which is kinda sad, considering the fact that ASE is still seeing continuing development whereas development ended on gScript sometime at the end of last year.
IConrad01 said:
>_<
Pesky perniciously persistently phantasmagoric P!!!
I just keep on seeing people referring to gScript when ASE is a vastly more robust offering. It can run its scripts as daemons, run in background, run in terminal, it offers the same desktop shortcut option -- and more importantly, it can run Python, Perl, JRuby, Lua, BeanShell, JavaScript, Tcl, and shell scripts. (It loads the interpreters onto your /sdcard.)
Click to expand...
Click to collapse
no, I am very interested in it,
I have been meaning to have a proper look at it for sometime
, I think I first saw it on @google
gscript is just handy,
unzip this, gscript from market,add, load, tick su, save , tap
But I promise , I will look at ASE
Firerat said:
and then have a script switch wlan.ko if incompatible
might as well switch with script and keep recovery for the odd times when you just want to quickly flash some zips from a list and not at your pc.
yeap, I've downloaded and flashed a rom while 'out and about' before.
Click to expand...
Click to collapse
Glad this is getting your attention....My script was pretty dirty anyways.
Anyway you can package it up in signed-zip format for easy access and modification of boot.imgs. Im having some issues with the update-script portion during the signing process tos keeping me from getting mine to be "flashable"
zimphishmonger said:
Glad this is getting your attention....My script was pretty dirty anyways.
Anyway you can package it up in signed-zip format for easy access and modification of boot.imgs. Im having some issues with the update-script portion during the signing process tos keeping me from getting mine to be "flashable"
Click to expand...
Click to collapse
still having update-script issues?
if you post it, I'll be happy to take a look for you
Oh, I've started a kernel switch script
I'll do some testing when its done and post it here for you
This is going to be the thread for everyone to post in when they are testing the app, regardless of device. Please only post in this thread if you are a tester to minimize on clutter.
Ok guys, I have a test version of the app ready and I need some testers! This app was put together by Smurph82 (Ben), me (Derek), and another friend of mine (Will) with Ben doing the majority of the coding. If Smurph82 asks you anything, ANSWER HIM! He is the guy who will get this fixed! Please bear with us as we get the bugs worked out and get this to be the best voltage control app out there!
Some things don't work and I need help figuring out what else isn't working. I'm looking for 2-3 testers for devices I don't officially support right now. (check the list in my sig of officially supported devices and make sure you're applying to beta test for a device not listed there) All testers will get the paid version of the app when done, assuming you provide me with feedback of this app. Here are a few rules...
0.) You must be on a HAVS/SVS kernel (exceptions Nexus S/NS4G with mathkid or Netarchy kernel). If you don't know what this means, please do not send me a request to beta test. You must also be on a ROM that supports init.d (99% of ROMs)
1.) If you are selected to be a tester, you WILL NOT send this app to anyone else and you will use it only on your personal devices.
2.) If you are not selected to be a tester, please don't blow up my PMs or thread complaining about it.
3.) You will provide me with some feedback about the app, what works and what doesn't, what should be implemented and/or taken out. I don't think this is an unreasonable request.
4.) To be an official beta tester, your submissions will BY PM ONLY. This information needs to be sent to me or I will ignore your PM. I don't have time to respond and ask for the information that I need. Please don't post in this thread for wanting to test, this thread is for the testers to post their results and collaborate with one another. Please include this with your beta testing submission:
Device:
ROM:
Kernel:
Please also keep replying with our whole conversation so I can reference it.
5.) I may be going to bed soon so if you get nothing from me tonight, I will hit you up tomorrow.
Thanks guys, I look forward to working with all of my beta testers!!
Known Issues:
[*]Landscape in 2nd tab doesn't scroll
Some voltages presets need to be implemented
Links are too small
[*]Netarchy kernel detection shows UNKNOWN
Shouldn't show init.d button if one doesn't exist
[*]App looks in the wrong place for SVS kernel voltages
Cannot save init.d file
Alright, I've run into one problem right off the bat but I think it will be easy to solve.
It says:
"File at /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs was not found
My frequency tables are at:
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
I know it will work, I've been using the vipermod terminal script to change my voltages, it just can't find my frequency tables it seems.
EDIT: i messed up the file path for my tables (left out the /cp0) fixed now.
I am also getting the same issue of:
File at /system/etc/init.d/74havsvoltages was not found.
DEVICE: HTC EVO 4G
KERNEL: TIAMAT 3.3.7
Im getting file at /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels)havs was not found
Also I cant adjust voltages up or down as I keep getting a pop up saying "This is not a HAVS kernel"
MIUI 1.8.12 DEXT
HTC DESIRE
SVS stock kernel [email protected] 2.6.37
Dont like the contacts font colour either imho difficult to read
File at /system/etc/init.d/74havsvoltages was not found.
DEVICE: NEXUS ONE
KERNEL: IR 2.6.38.8_AVS-CM7_CFS_20110813_1517
Already off to a fantastic start lol
OK, so issues with SVS detection. On the main page, does it detect that you are running an SVS kernel? It should say "This is an SVS kernel" right?
Do you already have an init.d file there from the viperMOD script when you try to read it? If so, can you back it up, delete it, and try to generate a new voltage file from the app?
Thanks guys!
yes it detects that I have an SVS kernel. Tried deleting the 99voltages file in my init.d and still no dice.
-viperboy- said:
Already off to a fantastic start lol
OK, so issues with SVS detection. On the main page, does it detect that you are running an SVS kernel? It should say "This is an SVS kernel" right?
Do you already have an init.d file there from the viperMOD script when you try to read it? If so, can you back it up, delete it, and try to generate a new voltage file from the app?
Thanks guys!
Click to expand...
Click to collapse
device : nexus s
rom : oxygen 2.2.1
kernel : tried both matr1x 5.5 and netarchy 1.4.0
i am having the same issue. the main page does not detect SVS kernel. it says this is a UNKNOWN kernel. (and i thought netarchy and matr1x are the only kernel compatible to this.
gotta go to sleep now, i will check again tomorrow ..
ok viperboy, first off thanks! i have several initial observations. the app assumes you have the voltage script installed in order to work. i think this should be the opposite. if not detected on app install the app should install one for the user, otherwise you would still need to use the vipermod te script in order to use the app by saving changes on default settings to create the init.d script. second, at a hi density view of 200, the lettering in your about section is a bit too small and your links are barely viewable. this needs to be adjusted. and finally, if you make a voltage selection too low for your phone to handle and need to do a battery pull because your phone locks up, i LOVE how it automatically resets itself to kernel defaults negating the need for having to flash a reset zip, bravo!! however, it changes your customized cpu settings as well. in my case it changed my cpu levels from 128/499 smartass to 245/998 interactive.
evo 4g/decks 1.3b2/sz 2.2.1 cfs
Thanks bud
ropodope
499mhz is the new 998mhz.
Jake33108 said:
yes it detects that I have an SVS kernel. Tried deleting the 99voltages file in my init.d and still no dice.
Click to expand...
Click to collapse
Please explain a little bit further. It sees its an SVS kernel, then what happens? Can't create the voltages?
saryu said:
device : nexus s
rom : oxygen 2.2.1
kernel : tried both matr1x 5.5 and netarchy 1.4.0
i am having the same issue. the main page does not detect SVS kernel. it says this is a UNKNOWN kernel. (and i thought netarchy and matr1x are the only kernel compatible to this.
gotta go to sleep now, i will check again tomorrow ..
Click to expand...
Click to collapse
OK, no Netarchy/mathkid kernels show up as unknown. Thanks for the info.
ropodope said:
ok viperboy, first off thanks! i have several initial observations. the app assumes you have the voltage script installed in order to work. i think this should be the opposite. if not detected on app install the app should install one for the user, otherwise you would still need to use the vipermod te script in order to use the app by saving changes on default settings to create the init.d script. second, at a hi density view of 200, the lettering in your about section is a bit too small and your links are barely viewable. this needs to be adjusted. and finally, if you make a voltage selection too low for your phone to handle and need to do a battery pull because your phone locks up, i LOVE how it automatically resets itself to kernel defaults negating the need for having to flash a reset zip, bravo!! however, it changes your customized cpu settings as well. in my case it changed my cpu levels from 128/499 smartass to 245/998 interactive.
evo 4g/decks 1.3b2/sz 2.2.1 cfs
Thanks bud
ropodope
499mhz is the new 998mhz.
Click to expand...
Click to collapse
Well, it shouldn't install one for the user, it should just error. We don't want to set a bad voltage that is too low for your phone or anything!
The links are an easy fix, thanks for the input.
And as far as setting too low of a voltage, that's because it doesn't write the init.d file yet. You could still end up with the same problem as the script if you set a voltage too low and saved it. And it shouldn't have changed anything like that at all. Could you explain how it changed your CPU settings??
Quick update, it reads my init.d 74havsvoltages file that the script made now. But it still won't let me lower or raise anything.
When I hit the "Adjust Voltages" tab it says "A havs or svs file cannot be found. Are you sure your kernel supports this?"
I believe this is because its looking for my files under:
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
and
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_svs
when my voltages are really at:
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
Just out of curiosity does this require root privileges maybe? Because I never got a SU request for it.
Jake33108 said:
Quick update, it reads my init.d 74havsvoltages file that the script made now. But it still won't let me lower or raise anything.
When I hit the "Adjust Voltages" tab it says "A havs or svs file cannot be found. Are you sure your kernel supports this?"
I believe this is because its looking for my files under:
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
and
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_svs
when my voltages are really at:
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
Click to expand...
Click to collapse
Ok, small oversight on that. Thanks much!
naf007 said:
Im getting file at /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels)havs was not found
Also I cant adjust voltages up or down as I keep getting a pop up saying "This is not a HAVS kernel"
MIUI 1.8.12 DEXT
HTC DESIRE
SVS stock kernel [email protected] 2.6.37
Dont like the contacts font colour either imho difficult to read
Click to expand...
Click to collapse
If the app does not detect the HAVS file correctly it will not allow you to update as it would be have not files.
I know that viperBoy requested your specs for being a beta tester
but please provide me with your phone, ROM, and Kernel in your post so I can
better understand your problem. This was built on an Evo 4g, CM7, Tiamat 4.0.*. Thanks.
/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs is the path that I knew development on my platform. I am working on this.
Already off to a fantastic start lol
OK, so issues with SVS detection. On the main page, does it detect that you are running an SVS kernel? It should say "This is an SVS kernel" right?
Do you already have an init.d file there from the viperMOD script when you try to read it? If so, can you back it up, delete it, and try to generate a new voltage file from the app?
Click to expand...
Click to collapse
It does detect that its a SVS on the main page
I deleted my file that I created with the script and tried to generate a new one but no change
HTC DESIRE
MIUI 1.8.12 DEXT XPART
Stock Kernel SVS [email protected] 2.6.37
I don't have an example of the /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
can someone please post me one thanks. Sorry the svs had not been implentment due to the fact that I only have one phone.
I'm restoring a backup right now, I'll post mine in just a second.
sure. i set the voltages too low on purpose in order to cause my phone to lock so that i would have to do a battery pull because i was curious to see if my kernel voltage defaults would be restored on reboot....and they were. i think that is great. i then reset them using the app to where i knew my phone would handle them. after doing so i took a look at my custom cpu settings which i have set to retain on reboot. when i did they were completely changed from 128/499 smartass to 245/998 (stock settings) along with the governor being changed to interactive. i just thought that was weird.
also the tapatalk app is not allowing me to reply to this thread. it keeps saying "failed to connect to forum. please check with the forum administrator if this problem persists". i have to reply from my laptop.
ropodope
499mhz is the new 998mhz.
Here's my file. All of my build info is in my sig.
Jake33108 said:
Here's my file. All of my build info is in my sig.
Click to expand...
Click to collapse
Thanks I will be working on this.
Updates
10/1/2011 - Added 00remounti9001 to remount the major partitions to noatime and disabled barriers for as well as delayed journaling to every 60 seconds (as opposed to 5) to /data, /persist, /cache. Added Acid Tweaks - Removed Useless Stuff i9001.zip to remove journaling from /cache and /system (It's safe). Also added JournalingOn.zip to revert back the two partitions to being journaled.
For the 00remount script, here's the how to:
0. Wait till Android finishes loading everything.
1. Install Script Manager from Market
2. Point script manager to the script you placed in the sdcard.
3. Run as root.
4. Do this at every boot, as mount points are reset to its default as set by the type of your lagfix. Voodoo (from what I am using will set barriers for /data and atime for every mount point except /system, /data, /cache, /dbdata which puts a slight risk at your disk for using atime.
5. You can add a widget to your home screen for the script so that you can
activate it easily.
The other two are CWM zips. You should know how to flash CWM zips right?
Introduction
I've made a Definite Guide on Android thread for i9000 that focuses on a few optimizations/scripts I've picked up over the months I've spent on XDA. I truly enjoyed sharing my knowledge with the i9000 community and since the tips/guide/scripts can also be applied here (save some exceptions that I would list down below),I would like to share this with the Captivate community too.
Exceptions
Take note that the guide is primarily for i9000 units. There are a few differences I can note here that you should be aware of:
1. The guide points out some kernels/ROMs that are for i9000. Hence the phones you are using may have different ROMs/kernels that may or may not correlate with the one in the guide.
2. The guide also mentions some apps/tweaks that are particularly alien to your unit and you may have never encountered it in your use of your phone or in XDA. Please ignore them for now, I'll make an effort to make the guide compatible in the future (with feedback from you guys of course )
3. Journaling scripts that are attached like the JournalingOn.zip and Acid Tweaks - Removed Useless Stuff and 00remount may not work well with your unit or it may completely brick it. I don't know this, but if you can post your mount partition configuration, I am willing to make the scripts work for you. You only have to type "mount" on your Terminal Emulator and provide the output to me, and I'll provide the rest. Zach's script however, have high compatibility towards a lot of phones, and thus can be used for your unit. Take note that there is a slight risk that it won't work well. If it doesn't, please post your problems here, and I'll try to fix it. Hence, it's best that you make a nandroid backup before attempting to use any tweaks here.
3. I've compiled a guide on a few notable tweaks in XDA here: LINK. If you would like me to evaluate scripts/tweaks/anything that you do not understand due to their terms being alien to you, I'll be glad to explain it here
Guide
You can refer to the guide here:
LINK
Hi pikachu!
I've made a screenshot of the terminal output after entering the mount command. Hope it provides you the needed informations!?
reneph said:
Hi pikachu!
I've made a screenshot of the terminal output after entering the mount command. Hope it provides you the needed informations!?
Click to expand...
Click to collapse
Thank you
I'll get to work on the scripts. Give me an hour or two
pikachu01 said:
Thank you
I'll get to work on the scripts. Give me an hour or two
Click to expand...
Click to collapse
Updated the scripts. Please read my guide before flashing any of those zips/scripts to know about its risks.
I am not responsible for any damages/bootloops if you did not read the guide before flashing those scripts/zips.
UPDATE 10/1/2011 - Added 00remounti9001 to remount the major partitions to noatime and disabled barriers for as well as delayed journaling to every 60 seconds (as opposed to 5) to /data, /persist, /cache. Added Acid Tweaks - Removed Useless Stuff i9001.zip to remove journaling from /cache and /system (It's safe). Also added JournalingOn.zip to revert back the two partitions to being journaled.
For the 00remount script, here's the how to:
0. Wait till Android finishes loading everything.
1. Install Script Manager from Market
2. Point script manager to the script you placed in the sdcard.
3. Run as root.
4. Do this at every boot, as mount points are reset to its default as set by the type of your lagfix. Voodoo (from what I am using will set barriers for /data and atime for every mount point except /system, /data, /cache, /dbdata which puts a slight risk at your disk for using atime.
5. You can add a widget to your home screen for the script so that you can
activate it easily.
First of all, thanks for the work.
I have tried to execute the remount-script using the script manager as root as you mentioned, but something fails. When running the script it outputs "mount: No such file or directory, mount: Invalid argument" and then the predefined echos of the script.
I had to remove following lines of code to get an output without the mount-errors:
mount -o noatime,remount,rw /mnt/.lfs /mnt/.lfs;
mount -o noatime,remount,rw /sys/kernel/debug /sys/kernel/debug;
Click to expand...
Click to collapse
more scripts and tweaks!
http://forum.xda-developers.com/showthread.php?t=1227269
reneph said:
First of all, thanks for the work.
I have tried to execute the remount-script using the script manager as root as you mentioned, but something fails. When running the script it outputs "mount: No such file or directory, mount: Invalid argument" and then the predefined echos of the script.
I had to remove following lines of code to get an output without the mount-errors:
Click to expand...
Click to collapse
Thanks for the heads up. I forgot to remove those lines actually. I reupload the script with those two lines remoevd.
sakindia123 said:
more scripts and tweaks!
http://forum.xda-developers.com/showthread.php?t=1227269
Click to expand...
Click to collapse
Thanks for the link. Yes, I've read this one before. My guide would explain more about what some of the tweaks do, and the script incorporates more than the link that you provided. You can edit the script and take a look if you want
is this working?
larry200ro said:
is this working?
Click to expand...
Click to collapse
Which tweak are you specifically asking about?
They should work provided you read the guide to know what those tweaks are
can i use this in my rom?thanks
sakindia123 said:
can i use this in my rom?thanks
Click to expand...
Click to collapse
Why not?
Let me know how good it is working for you. Remember to read the guide, as the scripts might not work well with other scripts (if your ROM also implements other scripts)
pikachu01 said:
Which tweak are you specifically asking about?
They should work provided you read the guide to know what those tweaks are
Click to expand...
Click to collapse
Honestly, I am at work now, I tried to read some things really quickly from your guide but I think that this is to technical for me. In a few words can you please describe what are they doing? I own a i9001 with Kernel 2.6.35.7-perf [email protected] #1 and build number gingerbread.xxkg1 android 2.3.3.
Sorry if my english is not to good, I am at work , have no time to concentrate, I am Romanian
larry200ro said:
Honestly, I am at work now, I tried to read some things really quickly from your guide but I think that this is to technical for me. In a few words can you please describe what are they doing? I own a i9001 with Kernel 2.6.35.7-perf [email protected] #1 and build number gingerbread.xxkg1 android 2.3.3.
Sorry if my english is not to good, I am at work , have no time to concentrate, I am Romanian
Click to expand...
Click to collapse
Umm, if you only want to use the scripts, you could scroll down to Zach's scripts and 00remount (Hint: They are in quoted text form). They are pretty short and simple to read. All the others in the guide would reinforce the things that are explained in there. If you don't understand something in the guide, post it here, and I'll offer up a simpler more laymen explanation of it
And you'll need a custom kernel with init.d support if you want to use the scripts.
pikachu01 said:
Umm, if you only want to use the scripts, you could scroll down to Zach's scripts and 00remount (Hint: They are in quoted text form). They are pretty short and simple to read. All the others in the guide would reinforce the things that are explained in there. If you don't understand something in the guide, post it here, and I'll offer up a simpler more laymen explanation of it
And you'll need a custom kernel with init.d support if you want to use the scripts.
Click to expand...
Click to collapse
Sorry but you lost me in the bold section. Where do I get a custom kernel with init.d support? I am searching for a month now for a custom kernel/custom rom/custom anything for my phone but found nothing than the successfull rooting guide in this forum.
Am I so stupid?
pikachu01 said:
And you'll need a custom kernel with init.d support if you want to use the scripts.
Click to expand...
Click to collapse
But not for the remount-script!?
Anyways, is there an existing custom kernel for the phone at all?
larry200ro said:
Sorry but you lost me in the bold section. Where do I get a custom kernel with init.d support? I am searching for a month now for a custom kernel/custom rom/custom anything for my phone but found nothing than the successfull rooting guide in this forum.
Am I so stupid?
Click to expand...
Click to collapse
Ahh, it appears that i9001 doesn't have a custom kernel If supercurio or chainfire is free, they could patch the initramfs with theirs and publish it here. I'm not an expert in initramfs and I don't have this phone
reneph said:
But not for the remount-script!?
Anyways, is there an existing custom kernel for the phone at all?
Click to expand...
Click to collapse
The remount script will always work, yes with Script Manager. No, I can see that i9001 doesn't have a custom kernel for it. Too bad
Actually, even without init.d support, you could use Script Manager to launch the scripts at boot. The only thing is that the screenstate_scaling would need the Script Manager to be on all the time, which will drain more battery than save it.
pikachu01 said:
Actually, even without init.d support, you could use Script Manager to launch the scripts at boot. The only thing is that the screenstate_scaling would need the Script Manager to be on all the time, which will drain more battery than save it.
Click to expand...
Click to collapse
So, you are saying that it's better not to use any scripts until a custom Kernel will appear?
larry200ro said:
So, you are saying that it's better not to use any scripts until a custom Kernel will appear?
Click to expand...
Click to collapse
You can use the scripts with Script Manager. A custom kernel only makes it easier to apply the scripts.
pikachu01 said:
You can use the scripts with Script Manager. A custom kernel only makes it easier to apply the scripts.
Click to expand...
Click to collapse
Ok, This I understood very well but, as you said before, this will need Script manager to be running all the time which will result in more battery spent.
Isn't the purpose of all tweaks/scripts to improve performance without lose of battery life and the phone to run the applications that you need and freeze/uninstall those you never use?(I've uninstalled the applications that I don't need with Titanium Backup and I have improved my battery life significantly).
Thanks very much pikachu for all the scripts and for the good work but I think this is not worth it because 1. galaxy s plus i9001 has a good 1.4Ghz processor and runs almost anything perfect. 2. You can safely improve the battery time with a simple software available on the market for free without risking with scripts.
Many thanks again, if you need any information from my phone for development purposes just let me know. I am willing to help
i want to create a rom for i9001..i have already started a thread for this.
and init.d will be one of the first things i would do!
all ur scripts will load automatically at startup!
Hi there
I got droidwall running on the SGY.
Please first read the whole post. I add changes at the end of it.
Here's what I did:
1. follow this great tut from irfanbagus. Thanks a lot irfanbagus!
2. After running "make bcm21553_totoro_05_defconfig", set this in .config:
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_NETFILTER_XT_MATCH_OWNER=y
and continue irfanbagus's steps
3. Install the new boot.img, e.g. via mai77's method as shown here
4. Profit! (as in: use droidwall )
Notes:
Alternatively the changes in .config could be set in cm21553_totoro_05_defconfig or via make menuconfig
If you don't have your boot.img as a normal file, run this in adb, then pull the file:
dd if=/dev/block/bml7 of=/data/local/boot.img
I was surprised that there was no such modified kernel till now. Maybe this is because the TARGET_REJECT option is essential but only XT_MATCH_OWNER is largely discussed when dealing with droidwall.
See attachment (mikstev_SGY_Kernel_netfilter_for_droidwall_boot.img.zip) for a boot.img with only these modifications.
Please test and report. I only tested blacklist/whitelist mode with Google Play blocked/allowed on Wifi connection, but it worked.
Edit 1: I've added the necessary (and probably some more) modules so that droidwall's logging works. Use the second attached file instead the first one.
Here are the changes I made, compared to normal .config:
CONFIG_NETFILTER_NETLINK=y
CONFIG_NETFILTER_NETLINK_LOG=y
CONFIG_NETFILTER_XT_MATCH_OWNER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_LOG=y
CONFIG_IP_NF_TARGET_ULOG=y
I guess the first two aren't necessary but I didn't bother to check every single module if it's the correct one which droidwall needs for logging. However this shouldn't matter anyway. See mikstev_SGY_Kernel_netfilter_for_droidwall_with_log_boot.img.zip
Edit 2: Due to request I've added init.d support to the latest release. Thanks irfanbagus! See mikstev_SGY_Kernel_droidwall_initd_boot.img.zip
Edit 2.5: Seems only the following modules are required but that only as a side note:
CONFIG_NETFILTER_XT_MATCH_OWNER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_LOG=y
Edit 3: New method for adding init.d support to a (newest) boot.img, with kernel modules for droidwall (+logging) and init.d scripts to load these modules. Please read the readme, if you have questions, post here. Special thanks to irfanbagus See mikstev_add_initd_to_boot.img__kernel_modules_initd_scripts_for_droidwall.zip
Edit 4: Thanks to an idea by irfanbagus and another tutorial to include init.d support by kurotsugi, here's another release. Adding init.d support is now easier with kurotsugi's method plus there's a update.zip (modules_droidwall_signed.zip) which does the other steps for you (copying the modules, init.d scripts and applying the correct permissions for these files). NOTE: this update.zip is yet untested. If you test it please report. See mikstev_add_initd_to_boot.img__kernel_modules_initd_scripts_for_droidwall_v2.zip
Edit 5: The update.zip from edit 4 seems to work. If you're using a kernel with init.d support you only need to install the update.zip and it should work fine.
good job. i know droidwall depend on other kernel features beside CONFIG_NETFILTER_XT_MATCH_OWNER. since i don't have plan to use droidwall, i don't bother to find it.
Profit indeed! It works! Good job, mikstev! I was able to block dolphin HD on my phone just to test if it works and it did, much to my delight!
And to irfanbagus as well for that wonderful guide on how to compile a kernel.
Great job, guys!
Now let's hope that all the other kernel developers include this small bit of configuration in their builts
finally! ive been waiting for this for ages. thank you very muchhhh!
Sent from my GT-S5360 using xda premium
Logging doesn't work yet. I'll try the solution from highlandsun: http://forum.xda-developers.com/showpost.php?p=11110889&postcount=357 tonight and upload new kernel if successful.
No need for so much hassel
Just use "lbe privacy guard" (free in store) it has much more features than droidwall and it doesnt require any special kind of kernel.
Y u no press "thanks"!?
Sent from my GT-S5360 using XDA
Ok, logging works now, I'll upload the new kernel. See first post.
devilrulz4ever said:
No need for so much hassel
Just use "lbe privacy guard" (free in store) it has much more features than droidwall and it doesnt require any special kind of kernel.
Y u no press "thanks"!?
Sent from my GT-S5360 using XDA
Click to expand...
Click to collapse
It seems that there're at least some people who see this differently. Here're some of my reasons, why I prefer droidwall over LBE Privacy Guard:
- it's a good and easy to use firewall. Not more, nor less. That's what I want.
- no "hassel" (to use your words) with resticting internet access of "trusted" apps
- I did not find a way in LBE to block LBE from using internet. In the iptables rules created by Droidwall I can clearly see that droidwall is not allowed = blocked
@mikstev: I'm just curious...is it based on sgy's newest kernel?
I think so, the source code is the one mentioned in irfanbagus' post (update2) which I linked above.
nice...I can integrate dualboot and data-2sd mod into this kernel easily. thx
i got other option to make droidwall work.
on init.rc i added this line:
service netfilter /system/bin/iptables
disabled
oneshot
this also work with avast firewall..
gear12 said:
i got other option to make droidwall work.
on init.rc i added this line:
service netfilter /system/bin/iptables
disabled
oneshot
this also work with avast firewall..
Click to expand...
Click to collapse
Can anyone confirm this? I can't see how this could replace the missing kernel modules.
mikstev said:
Can anyone confirm this? I can't see how this could replace the missing kernel modules.
Click to expand...
Click to collapse
nope. iptables only a user space application that depend on kernel features. and you can't call iptables without command/params.
the firewall works great, also, I can see the logs but after disconnecting from the internet and a few minutes the log is empty again, is this normal or a bug?
off topic:
and can I make a request? can you make the your boot.img support init.d as well? please...
Adam_Blade said:
the firewall works great, also, I can see the logs but after disconnecting from the internet and a few minutes the log is empty again, is this normal or a bug?
Click to expand...
Click to collapse
Yep, I noticed this too. The droidwall source seems ok at first glance and I don't think it's related to the netfilter modules etc. My guess would be that it's dmesg's fault, maybe the log is truncated or something but this is just speculation. I'll investigate in this in a few days. Maybe someone else knows why this happens?
Adam_Blade said:
and can I make a request? can you make the your boot.img support init.d as well? please...
Click to expand...
Click to collapse
Sorry, I currently don't have the necessary skills, so if you're looking for a quick solution you might better ask someone else for help. (Especially since there're already kernels with this feature and including the modifications for netfilter/droidwall should be trivial). However as I wanted to build up my knowledge regarding android/kernel development anyway, I'll try to add this feature one time, but that surely would take >1 week.
Regarding dmesg: the buffer size is set by CONFIG_LOG_BUF_SHIFT=19 which means 2^19 Bytes = 512KiB. I'll check later if this relatively huge size is really used up.
@mikstev: make init.d support kernel is easy. we only have to add a few script inside init.rc file. we can do it easily by using dsixda's kitchen or put the script manually. you can see my modified init.rc here http://www.mediafire.com/?cc1kg8s7cx27onb
I believe the script that have to be added is
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
Just to get sure: the init.rc which needs to be modified is the one in the initial ramdisk and not in the kernel (zImage), right?
I wrote this guide for originally in elk759's JB CM10 thread, but with some modifications it works with every ROM and every phone.
I thought other guides were too hard to understand so I concluded all neccessary information and nothing more.
This guide is for Windows, because it uses a Windows tool to make the process MUCH easier. This only affects the modding of services.jar, so look at the original Supercharger thread for instructions withot the Windows tool.
Here are the benefits of using SUPERCHARGER, I cn approve that it works, it's faster, more apps can run and no launcher redraws!
___________________________________________________________________________
Sources:
http://forum.xda-developers.com/showpost.php?p=12058585&postcount=1
http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
zeppelinrox said:
What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind
NO LAUNCHER REDRAWS, faster than ever, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
Also, because of the rearrangement, it works the same on all roms!
The problem with using minfree tweakers like AMM or AKMO is that it doesn't work the same on all roms.
Secondary apps may be in slot 3 on some roms but in slot 5 in others!
That's why you hear people comment "I tried AKMO but it didn't do anything..."
Most likely it didn't do anything because the apps weren't sitting where they were expected to be.
So fasten your seat belts and enjoy the ride!
Click to expand...
Click to collapse
zeppelinrox said:
And -=Maximum Overdrive=- was born!
Upside: You can run up to 70 apps if you have enough RAM.
Downside: NONE
Click to expand...
Click to collapse
zeppelinrox said:
The Kick Ass Kernelizer
What Does The Kick Ass Kernelizer Do?
Memory Management++
MFK Calculator Info - explanation for vm.min_free_kbytes
LinuxInsight - The /proc filesystem documentation (Fantastic!)
XDA [REF] Startup script speed tweaks OP by hardcore
XDA Speed up your system with the noop scheduler
TCP Speed & Security
Security and Hardening the TCP/IP stack to SYN attacks
Click to expand...
Click to collapse
zeppelinrox said:
The 3G TurboCharger
In case of connection issues, see the notes in the 3G TurboCharger section at the top of /system/build.prop!
Homework/Background Info... see the folllowing links for resources used.
XDA Thread 1
XDA Thread 2
XDA Thread 3
Wi-Fi AfterBurner.
XDA Thread (Faster WIFI - N Standard Enabling)
The 3g build.prop tweaks aren't really anything new... but I did put a new spin on it! ;^]
You can find various individual configurations but as far as I know, my script is the only one that lets the user choose from more than one configuration.
Click to expand...
Click to collapse
___________________________________________________________________________
IF YOU HAVE ANY PROBLEMS, LOOK FIRST AT THE Q&A BELOW!
1. Prerequisites:
SuperCharger_Starter_Kit_xxx.zip (contins busybox, sqlite and zipalign)
[*]V6_SuperCharger_for_Android-Update9_RC11_xxx.sh.pdf
Script Manager for starting scripts (on first run enable root browse AND run every script with su rights, the skull and bones symbol)
ES File Explorer (with root rights in settings->root management)
optionally: Terminal Emulator
Recommended for everyone and REQUIRED for 4.0+ Roms:
pepcisko's Windows tool for patching services.jar
Place the V6_Supercharger script and the Supercharger_Starter_Kit.zip content to "/sdcard/V6"
Place the Windows tool somewhere on your Hard Drive
Install the required apps
2. Installation of Starter Kit:
Start SManager and confirm root rights when browsing
go to sdcard/V6/1_SuperCharger_Starter_Kit and click on StartMeUp.sh
select the SU button (skull + bones) and RUN it as script and follow the instructions (install at least busybox for being safe that everything works)
3. Patching services.jar
Background information (could be very useful):
Patching the services.jar gives you the multitasking mod. Apps shouldn't restart all the time, they will stay in RAM as long as they can.
Patching the services.jar is REQUIRED for Android 4.x.x, but you don't have to use multitasking mod.
For the other Android versions it isn't required, you only need this if you want to have multitasking mod, too.
If you have Sense 4.0+ and want multitasking mod, you have to follow this, more complex tutorial.
But you can also use this method, but your visible app limit stay at 8 Apps, instead of 50!
extract the Windows tool and launch it
You can choose between online mode (phone drivers needed) or offline mode, I'll explain offline mode:
make sure you have root rights in ES Explorer and that you mount system as R/W (read/writable)
copy the services.jar from /system/framework to your SD, and connect your phone to PC
move the services.jar to the framework folder of the Windows tool directory
in the windows tool specify your Android version + if the rom is odexed/deodexed
now press "enter" -> "y" for supercharge -> "enter" for die die-hard launcher -> "enter" -> "y" for multitasking -> "enter" -> "y" to delete temporary files
You have patched the services.jar, now you have two options (both files are in "dist" directory):
Place the update-signed.zip on sdcard and install it via recovery
OR
Place the modded services.jar (and if odexed rom the services.odex too) to /system/framework and overwrite. Then you have to set owner and permissions:
In Terminal Emulator
su
(confirm SuperUser Request)
busybox mount -o remount,rw /system
cd /system/framework
chown 0.0 services.jar
chmod 644 services.jar
Now go into recovery (or stay there after flashing update-signed.zip) and wipe cache & dalvik cache.
On your next reboot apps should be optimized.
4. Supercharger Installation
Remember: I can't promise, that the guide is always up to date. So it could happen that after an update of the script, the option numbers are different. Look at the text on the right side of the option
start the /sdcard/V6/V6_SuperCharger... script with SManager with SU rights
follow the instructions of driver options: You will be asked for Scroll Speed but also various tweaks which can improve the performance
The script calculates the preferred FreeMem size, you can use them or set your own prefered size:
After you have declined to use the calculated option you are in Driver's Console, you can choose between 33 options.
The Options 2 to 9 set the MinFree size, for the different Ram Size of the devices.
For the Desire I recommend option 6 which is called "balanced". You can try a lower or a higher option, too.
Lower values are better for Multitasking, higher values are better for the speed on the visible app.
go back to driver options and type 21 for Nitro Lag Nullifier, confirm with N (could be unstable, you don't have to use this)
After you are finished press option 17 for Engine Flush and after that option 32 for SuperClean& Restart
After the restart you should open SManager again and navigate to /system/etc/init.d, click on S99SuperCharger and enable SU + Run on Boot.
Press Save. This should avoid issues if you want to launch Supercharger Script again (for me it worked without doing that)
Widgets for easy and fast freemem change:
For compairing settings, you can make widgets, settings will be changed instantly:
- you have to select the option you want to use as a widget (e.g. option 5 of supercharger) one time in V6_Supercharger script
Your selected options will appear as a small script in sdcard/V6_Supercharger/PowerShift_Scripts
- long press on home screen, click on Widgets and select SManager
- choose the script you want to use (e.g. 512HP_UnLedded...)
Q&A Supercharger
Q: Supercharger says "sorry, your rom wipes service entries on boot". Is it an issue?
A: No you can ignore it. You'll stay supercharged. (thx to abelle_abelle for the hint)
Q: Supercharger says that I'm only 75%/50% supercharged. What is the reason?
A: Propably the services.jar hasen't been patched right. Check if the services.jar is replaced and if the owner and the permissions are right. Try it out with offline mode in the Windows tool.
Q: Do I have to patch the services.jar again after rom update?
A: If you flash the rom you have to replace the original services.jar again. I don't know if you can use the previous patched services.jar.
Q: Do I have to run the whole script again after a rom update?
A: You have to run the Supercharger script again, but it has stored the last settings and can restore them. Then you have to Wipe Cache & Dalvik, reboot and set /system/etc/init.d/S99SuperCharger to run with SU rights + at boot.
Q: Did my settings stick?
A: If Supercharger says "100% supercharged" everything should be fine. If you think there is something wrong, because of a particular message paste the log text in pastebin.com and give me the link in your post.
Q: Do I have to install the Supercharger StarterKit?
A: No, you cann try it without this first if you want. BUT some busybox versions doesn't work with Supercharger (everything below 1.16.2 and even some versions above 1.16.2.
The StarterKit installs a recommended version.
Q: My phone is getting slower from time to time.
A: This can happen if you don't reboot often (1 or 2 days). The cache is growing and there is less and less RAM.
If you don't want to reboot all the time you can make the EngineFlush in V6_SuperCharger (option 17) and a script will be created (!FastEngineFlush.sh). You can make a widget for it after you set it as favorite or launch it normally in Script Manager.
A more detailed guide about making widgets is written above.
Q: Everythings (apps and launcher) stucks after NitroLagNullifier/V6 Supercharger installation. What can I do?
A: The user abelle_abelle had this issue. He had to hard reset his device (hard reset wipes your partitions -> deletes your data) and had to reinstall the rom.
Q: Are there any possibilites to make my rom even faster?
A: Yes, with KickAssKernelizer (KAK):
http://forum.xda-developers.com/showpost.php?p=32508611&postcount=35
Maybe I will write a bit more detailed guide for this. You can see what it does at the benefits of Supercharger at the top of my first post.----------------------------------------------------------------------------------------------------------------------------------------------------------
It took me long to test and to write please give a Thanks if I helped you
Also thank the creator of the scripts (check links)
Reserved for possible addition and Q&A
Have been using this for some time, and I can confirm it works.
Sent from my toaster.
I'm stuck in the CM logo screen after installing service.jar (online mode) and wiped davlink and cache.
aledex said:
I'm stuck in the CM logo screen after installing service.jar (online mode) and wiped davlink and cache.
Click to expand...
Click to collapse
Which Rom you are using?
Androidmarketuser said:
Which Rom you are using?
Click to expand...
Click to collapse
I'm sorry, I thought I edited the post. I'm using Elk's CM10 for Desire.
After trying several times to wait after having wiped cache and davlink (and fixed permissions) I re-flashed the rom and tried to apply the superchager script.
Problem 1: not enough spaces on the system (I'm using INT2EXT)
Problem 2: supercharger only at 50%
Problem 3: Apex launcher not recognized
Should I try to re-do everything, maybe this time with the offline method? But how to avoid the system space problem?
aledex said:
I'm sorry, I thought I edited the post. I'm using Elk's CM10 for Desire.
After trying several times to wait after having wiped cache and davlink (and fixed permissions) I re-flashed the rom and tried to apply the superchager script.
Problem 1: not enough spaces on the system (I'm using INT2EXT)
Problem 2: supercharger only at 50%
Problem 3: Apex launcher not recognized
Should I try to re-do everything, maybe this time with the offline method? But how to avoid the system space problem?
Click to expand...
Click to collapse
First off, I used it for CM10 too but without int2ext.
The reason for 50% is propably the unpatched service.jar(at beginning I had this issue too)
First, I would try to use the offline mode, the utility propably hasn't patched anything so try if it's working by manual way.
Just put the service.jar on PC, patch it and replace it. Then start the Supercharger V
script gain and it should be 100%.
otherwise do that:
On your SD Card there should be a Supercharger.html with a "log" or sth like that, please send it to me.
Additionally check if there is a "V6 Supercharger" folder on your SD, created by the script.
And check the output of the Windows tool! Be sure you have phone drivers on your PC and your phone is connected without SD Card Read if you use online.
-------------------------------------------
The space on system shouldn't be a problem, you have to use at least 250mb system (so stock hboot), int2ext only mounts /data on ext, so as I understood it is used for fatsys hboots which have 450mb system and NO space for data...
Why do you think that the space is a problem? Where did you notice it?
The APEX problem can be discussed after getting the rest work...
Please give feedback whether it worked or not
Androidmarketuser said:
First off, I used it for CM10 too but without int2ext.
The reason for 50% is propably the unpatched service.jar(at beginning I had this issue too)
First, I would try to use the offline mode, the utility propably hasn't patched anything so try if it's working by manual way.
Just put the service.jar on PC, patch it and replace it. Then start the Supercharger V
script gain and it should be 100%.
otherwise do that:
On your SD Card there should be a Supercharger.html with a "log" or sth like that, please send it to me.
Additionally check if there is a "V6 Supercharger" folder on your SD, created by the script.
And check the output of the Windows tool! Be sure you have phone drivers on your PC and your phone is connected without SD Card Read if you use online.
-------------------------------------------
The space on system shouldn't be a problem, you have to use at least 250mb system (so stock hboot), int2ext only mounts /data on ext, so as I understood it is used for fatsys hboots which have 450mb system and NO space for data...
Why do you think that the space is a problem? Where did you notice it?
The APEX problem can be discussed after getting the rest work...
Please give feedback whether it worked or not
Click to expand...
Click to collapse
Here's my problem:
1 - Installation of starter kit:
http://i50.tinypic.com/dqp5qf.png
2 - Patch of services.jar went ok with offline mode, but when I try to change permissions
http://i45.tinypic.com/34drlog.png
(this problem is obviously related to point 1)
Supercharger.html in attachments
aledex said:
Here's my problem:
1 - Installation of starter kit:
http://i50.tinypic.com/dqp5qf.png
2 - Patch of services.jar went ok with offline mode, but when I try to change permissions
http://i45.tinypic.com/34drlog.png
(this problem is obviously related to point 1)
Supercharger.html in attachments
Click to expand...
Click to collapse
Do you have stock hboot?
Try to delete some unnecessary preinstalled apps with file explorer.
(I search for some which you could delete...)
Edit: in system/app/ you can delete at least Calenar.apk, ES File Explorer.apk and Email.apk (after backup I think you can delete Gallery2.apk too, don't know how this affects on camera)
This should free at least 4mb and should be enough.
The file was just a help file and not a log, sorry for the mistake, thought it would create a og, but you have showed me the eroor with the pics...
Hey mate can you make a youtube video showing the steps. I understand better with visuals, and thanks for sharing.
Sent from my HTC Desire using xda app-developers app
Androidmarketuser said:
Do you have stock hboot?
Try to delete some unnecessary preinstalled apps with file explorer.
Click to expand...
Click to collapse
Yes I have stok hboot, and this is the first time I try to install V6 on a JB rom.
Concerning the lack of space I've done like you said, thank you!... BUT when I try to install binay 3.1 (which should fix the segmentation faults) it points out that it's only for ICS and aborts the installation. So I fixed the permission manually.
Now I'm going to check the rest and see what happens.
Fixed permission, flashed update-signed.zip, wiped davlink and cache, rebooted and... well, after HTC logo the screen turned off and only the hardkeys were illuminated
I'm going to flash the rom again and start from the beginning for the third time.
aledex said:
Yes I have stok hboot, and this is the first time I try to install V6 on a JB rom.
Concerning the lack of space I've done like you said, thank you!... BUT when I try to install binay 3.1 (which should fix the segmentation faults) it points out that it's only for ICS and aborts the installation. So I fixed the permission manually.
Now I'm going to check the rest and see what happens.
Fixed permission, flashed update-signed.zip, wiped davlink and cache, rebooted and... well, after HTC logo the screen turned off and only the hardkeys were illuminated
I'm going to flash the rom again and start from the beginning for the third time.
Click to expand...
Click to collapse
I saw that you are going to install Paranoid anyway, I have flashed CM10 recently so I have to redo my Supercharger and I will explain it in detail for you.
I will edit this post but give you a overview first.
I recommend to flash Gapps first and then enable a2sd.
Try installing Supercharger without the use of Starter Kit, Busybox, SQlite and SU binaries (v3.2) are preinstalled (if you want to check for update anyway check it in SuperUser app)
StarterKit is designed to give everyone the TESTED busybox version, to avoid problems, but try it without the installation of StarterKit, just if it doesn't work because of busybox get the one of StarterKit (I will try it with preinstalled version, not the one of StarterKit)
So here are my steps, I'll try:
1. patch services.jar with offline mode, then put the output service.jar with ES File Explorer in /system/framework
2. With terminal emulator I will set the permissions and the owner
3. I will launch the Superuser script.
You can try this while I am using this method, too, but in any case I will report if it works or not
Edit: I decided to make a video, for this I will use StarterKit too, to show everything.
chico1620 said:
Hey mate can you make a youtube video showing the steps. I understand better with visuals, and thanks for sharing.
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
I'll have to see, I have only a camera of the year 2005 or a old samsung phone of the year 2008/2009
I don't know if the quality would be good enough + I would do it only for 4.0+ ROM
Androidmarketuser said:
I'll have to see, I have only a camera of the year 2005 or a old samsung phone of the year 2008/2009
I don't know if the quality would be good enough + I would do it only for 4.0+ ROM
Click to expand...
Click to collapse
Does not matter my problem is the terminal coding i dont want to mess it up and change something crucial.
Sent from my HTC Desire using xda app-developers app
chico1620 said:
Does not matter my problem is the terminal coding i dont want to mess it up and change something crucial.
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
I'm currently making a video but I don't know if I can upload it today, but tomorrow you'll have it in any case
Quality is good I noticed.
Androidmarketuser said:
I'm currently making a video but I don't know if I can upload it today, but tomorrow you'll have it in any case
Quality is good I noticed.
Click to expand...
Click to collapse
Omg ty mate, i will be looking forward to it. Im also trying to follow your guide and see how things go, jopefully i succeed
Sent from my HTC Desire using xda app-developers app
Androidmarketuser said:
I saw that you are going to install Paranoid anyway, I have flashed CM10 recently so I have to redo my Supercharger and I will explain it in detail for you.
I will edit this post but give you a overview first.
I recommend to flash Gapps first and then enable a2sd.
Try installing Supercharger without the use of Starter Kit, Busybox, SQlite and SU binaries (v3.2) are preinstalled (if you want to check for update anyway check it in SuperUser app)
StarterKit is designed to give everyone the TESTED busybox version, to avoid problems, but try it without the installation of StarterKit, just if it doesn't work because of busybox get the one of StarterKit (I will try it with preinstalled version, not the one of StarterKit)
So here are my steps, I'll try:
1. patch services.jar with offline mode, then put the output service.jar with ES File Explorer in /system/framework
2. With terminal emulator I will set the permissions and the owner
3. I will launch the Superuser script.
You can try this while I am using this method, too, but in any case I will report if it works or not
Click to expand...
Click to collapse
Thank you, you are very patient and nice!
Yes I'm indeed trying Paranoid, because it solves the big problem I had with Elk's CM10 (wifi not working with wifi networks with PEAP), although it is slower and I intend to revert back as soon as the problem is fixed.
I will try your method, hoping that the hateful fragmentation fault problem doesn't occur anymore. :fingers-crossed:
aledex said:
Thank you, you are very patient and nice!
Yes I'm indeed trying Paranoid, because it solves the big problem I had with Elk's CM10 (wifi not working with wifi networks with PEAP), although it is slower and I intend to revert back as soon as the problem is fixed.
I will try your method, hoping that the hateful fragmentation fault problem doesn't occur anymore. :fingers-crossed:
Click to expand...
Click to collapse
Thanks for you thanks
I don't know if it is rally the segmentation (or whatever it's called) because it only occurs in ICS, if you want to install the su binary of the StarterKit it says NO because you don't need this (I think so)
I will upload a video tomorrow and I hope it solves your problem, for me everything's working fine
Does reinstalling the rom gets rid of the script? Because I'm currently using mildwild 5.0 and when I installed the supercharger script the rom got slightly slower, so I was wondering if reinstalling the rom gets rid of the script. Maybe I picked the wrong choices when installing the script I'm gonna wait for you to make a video so I can correctly do it.
Sent from my HTC Desire using xda app-developers app
chico1620 said:
Does reinstalling the rom gets rid of the script? Because I'm currently using mildwild 5.0 and when I installed the supercharger script the rom got slightly slower, so I was wondering if reinstalling the rom gets rid of the script. Maybe I picked the wrong choices when installing the script I'm gonna wait for you to make a video so I can correctly do it.
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Reinstalling the rom deletes supercharger, because system is wiped (i think so)
The Video will show how you install the script, there aren't man decisions which you can choose incorrectly.
The speed is especially affeced by multitasking mod (keeps apps in memory, a bit less RAM for games) and freemem options which you choose in supercharger script, I recommend Option 6 for balanced settings.
AS I said the video only shows the basic things (and only for 4.0+)...
Edit: Video wont have many anotations, will be under time pressure
Sent from my HTC Desire using xda app-developers app