Database Develop

[FIX][SCRIPT] Fixed zram for franco 2.6.32.x kernels (v18,v19) plus remount speedups

If you do not know what is this about and do not have any problems, leave the scripts alone and go on with your life.
Click to expand...
Click to collapse
Attached.
1a. Fixed zram.zip for franco kernels v18/v19
Fixed by removing the 00remount script from /system/etc/init.d, since it messes up with boot on phones with DT's apps2sd (and probably other similar scripts) - a2sd fails to mount sd-ext partition, phone "hangs" on LG logo.
If you are already stuck after flashing franco's original zram.zip due to this issue, then go to recovery, mount /system there, and
Code:
> adb shell
# rm -f /system/etc/init.d/00remount
# exit
> adb reboot
Alternatively, flash remove-zram.zip and reboot. This will remove ZRAM altogether.
There is no ZRAM support on franco's 2.6.35.x (v1) kernels, flashing this there is absolutely useless
Click to expand...
Click to collapse
1b. remove-zram.zip: Removes ZRAM. Deletes the following files if they exist:
Code:
/system/bin/zramconfig
/system/etc/zram.sh
/system/etc/init.d/00remount
/system/etc/init.d/00zram
2. remount-noatime.zip
Remounts all your filesystems with noatime,nodiratime options (potential I/O speedup). Taken from the original zram.zip and renamed to 98remount so that it comes after all other stuff is done.
3. remount-noatime-nobarrier.zip
Same as above, plus remounts ext4 with barrier=0 option for users with sd-ext on ext4. (potential I/O speedup)
Q: What is zram?! I do not understand what is this about!
A: Read the red warning.
Q: How can I find whether my kernel supports ZRAM?
A: Use the shell.
Code:
# zcat /proc/config.gz | grep ZRAM | grep -v ^#
CONFIG_ZRAM=y
Q: What is noatime, nodiratime, barriers?
A: Google it!
Q: I deleted the 00remount script as advised in recovery, but still have issues with A2SD not mounting my sd-ext!
A: If you are using CM7 ROM, then delete /system/etc/init.d/05mountsd as well. (Rename to _05mountsd or whatever else that does not start with digits should do as well.)

Em a newbie.... just asking ... is this improves battery life?
>>Sent from my LG-optimus One™ using XDA Premium App® Rom -void forever with franco kernel v19

samcad said:
em a newbie.... Just asking ... Is this improves battery life?
Click to expand...
Click to collapse
no!
1234567890

samcad said:
Em a newbie.... just asking ... is this improves battery life?
>>Sent from my LG-optimus One™ using XDA Premium App® Rom -void forever with franco kernel v19
Click to expand...
Click to collapse
As the doctor already mentioned... THis script is for those who get issues with boot up of their OS..!! Read the FIRST POST...!!
If your phone is working fine then this is not for you...!!!

Good one.
Prepare for 40 thousand posts asking if this script makes coffee and cleans the house for you.

imiki2421 said:
As the doctor already mentioned... THis script is for those who get issues with boot up of their OS..!! Read the FIRST POST...!!
If your phone is working fine then this is not for you...!!!
Click to expand...
Click to collapse
I have read it... but m just knowing anyway in improving in this script
>>Sent from my LG-optimus One™ using XDA Premium App® Rom -void forever with franco kernel v19

franciscofranco said:
Prepare for 40 thousand posts asking if this script makes coffee and cleans the house for you.
Click to expand...
Click to collapse
My /dev/null is ready

And does it make coffe? )
Sent from my LG-P500 using XDA App

Fresh installed 6.5.7 then fk19 then revised zram then noatime then dt a2sd (rebooting in between ofc) and got stuck again after flashing a2sd.
Got in recovery and deleted the 2 scripts from init.d via adb then reboot. It rebooted ok and I thought yeeah we're done. I did another reboot afterwards and it stuck again.
Trying to figure out what to try next. That's a way to spend my vacations lol

See adb logcat

I'll be the first. Does it make coffee and clean the house for me?
Btw glad your hissy fit is over. Good to have you back.
Sent from my LG-P500 using XDA Premium App

Testing -> remount-noatime-nobarrier.zip
I had no problems, just testing that for noatime, no barrier

franciscofranco said:
Good one.
Prepare for 40 thousand posts asking if this script makes coffee and cleans the house for you.
Click to expand...
Click to collapse
rofl, youre kinda, funny you know that?

Lawful123 said:
Btw glad your hissy fit is over. Good to have you back.
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
totally out of topic!!!!
but I HAD to rotfl! ...hissy fit.... LOL!

Is there anyway to remove ZRAM after installing the original ZRAM?
I have been following franco kernel since v16.
Now i'm using V19.1.. and i have installed ZRAM for the first time after flashing 19.1
My phone has random reboots and i guess the sole cause is ZRAM.
Is there anyway to disable ZRAM? THANKS!
NOTE: I have tried to revert back to v19 but same issue.. random reboots.

kutysam said:
Is there anyway to remove ZRAM after installing the original ZRAM?
Click to expand...
Click to collapse
Delete the installed files. See the ZIP for which ones.
kutysam said:
Is there anyway to disable ZRAM? THANKS!
NOTE: I have tried to revert back to v19 but same issue.. random reboots.
Click to expand...
Click to collapse
Delete /system/etc/init.d/00zram
Finally, I very much doubt that zram is causing reboots for you. It is merely a swap.

dr. I´m using Juwe11 RamScript, as far as I can see theres no duplicate stuff between your last script and his so i can use both, but my question is if its better that your script runs after him, now yours run first because of the files name.

Roqu3 said:
dr. I´m using Juwe11 RamScript, as far as I can see theres no duplicate stuff between your last script and his so i can use both, but my question is if its better that your script runs after him, now yours run first because of the files name.
Click to expand...
Click to collapse
Does not matter at all in which order they run...

Added remove-zram.zip; self-explanatory.

dr.notor said:
Added remove-zram.zip; self-explanatory.
Click to expand...
Click to collapse
So it will increase quadrant score? (lol)

[DEV] Loadable Modules for Gingersense Incredible [Updated 9/18 - Support for OTA]

HTC released gingerbread via OTA but they did not support additional modules. This thread has flashable zips for both the leaked kernel and the one from the "OTA".
Added flashable modules to attachments that are flashable in recovery.
I have created a zip of some of the more useful modules for our device:
Code:
cpufreq_conservative.ko
cpufreq_smartass.ko (thanks Chad for the help here)
ext4.ko
jbd2.ko (necessary for me to load ext4)
tun.ko
perflock_disable.ko (I actually compiled this one a little different but confirmed it would load and not get the exec format error)
Update: Smartass is working now with assistance from chad in resolving those errors. Decided to not worry about interactive for now.
Further information:
If you don't use the CWM flashable zip you will need to load perflock_disable a special way as it needs to be called with a special parameter to make it work correctly. Try adding below to a script. Credit to Calkulin for the script.
Code:
if [ -e /system/lib/modules/perflock_disable.ko ]; then
insmod /system/lib/modules/perflock_disable.ko
if [ $? -eq 0 ]; then
echo "Perflock DISABLED"
else
addr=`awk '$3 == "perflock_notifier_call" { print "0x"$1; }' /proc/kallsyms`
if [ -n "$addr" ]; then
insmod /system/lib/modules/perflock_disable.ko "perflock_notifier_call_addr=$addr"
if [ $? -eq 0 ]; then
echo "Perflock DISABLED"
else
echo "ERROR!!! Perflock could NOT be DISABLED"
fi
fi
fi
fi
Credits:
Conap (for BootManager and helping me test ext4 on an SD ROM)
XDA (for teaching me so much about Android)
HTC (for the kernel source)
Chad0989 (for assistance in getting smartass CPU governor working)
Coolbho3000 (perflock_disable)
Calkulin for the module load script
anyone else who inspired me (apologize if I forgot)
I have attached a zip file to this. If you are not a dev you can still use the modules here but some basic ADB/terminal knowledge would be needed. The modules are open for testing though.
Attached zip files and CWM-flashable zip files for both OTA and leak-based ROMs.
inc_modules.zip - Just the loadable modules.
inc_modules_ota.zip - just the loadable modules - OTA-based ROMS (August leak)
inc_modules_ota_091811.zip - just the loadable modules - OTA-based ROMS (actual OTA from September)
inc_modules_CWM_flashable.zip - flashable zip that will also autoload modules at boot.
inc_modules_ota_CWM_flashable.zip - flashable zip that will also autoload modules at boot - OTA-based ROMS (August leak)
inc_modules_ota_091811_CWM_flashable.zip - flashable zip that will also autoload modules at boot - OTA-based ROMS (Actual OTA from September)

I'm glad some one took this up I had been wondering the same thing since HTC opened the dev section. I had found another site that had a more extensive write up on how to build kernels but I'm not very fluent in linux and was a little intimidated at trying. At least I now know that it can be done. Maybe we can get Chad to try and port it over?

Awesome. A ray of hope.

Good job Tiny! I know someone was just asking for a tun.ko module and now I can't remember who it was. Hopefully they see your post.

jermaine151 said:
Good job Tiny! I know someone was just asking for a tun.ko module and now I can't remember who it was. Hopefully they see your post.
Click to expand...
Click to collapse
Thanks!
I'm trying to add more existing modules but my compiler treats warnings as errors so it won't build. Chad, if you see this post, any advice here?

tiny4579 said:
Thanks!
I'm trying to add more existing modules but my compiler treats warnings as errors so it won't build. Chad, if you see this post, any advice here?
Click to expand...
Click to collapse
--prefix
Sent from my ADR6300 using XDA App

hightech316 said:
--prefix
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I actually got them to build but they won't load still. I will play around with it more.

This is awesome. I was hoping for a tun.ko module! Now, do I just grab these and drop then in system/lib/modules and they should just work? Or are there steps I need to take to make them work? (I am honestly only concerned with the tun.ko)

oh wow this is incredible great job tiny!!! and the reason you probably cant get those other governors to work is because htc released an uncomplete source

jskolm said:
This is awesome. I was hoping for a tun.ko module! Now, do I just grab these and drop then in system/lib/modules and they should just work? Or are there steps I need to take to make them work? (I am honestly only concerned with the tun.ko)
Click to expand...
Click to collapse
Just drop in the ones you want and run insmod /system/lib/modules/tun.ko for tun.ko. You will have to do it at boot each time or get the dev to write an init.d script to load it.

tiny4579 said:
Just drop in the ones you want and run insmod /system/lib/modules/tun.ko for tun.ko. You will have to do it at boot each time or get the dev to write an init.d script to load it.
Click to expand...
Click to collapse
would i need to make one for every module?

JoelZ9614 said:
would i need to make one for every module?
Click to expand...
Click to collapse
Joel,
No, just one script should work. I believe Synergy ROM already has the init.d script for some of them. See 00cpufreq_modules in /system/etc/init.d
All,
Updated OP with latest zip file. If you have downloaded previously, redownload to get the latest.

would it be likes this?
http://www.multiupload.com/J9WTSA4VWF

JoelZ9614 said:
would it be likes this?
http://www.multiupload.com/J9WTSA4VWF
Click to expand...
Click to collapse
The first line should be:
Code:
#!/system/bin/sh
and it needs to have execute permissions or it won't execute. Also make sure to save it in UNIX format. I would also add the smartass module as it is quite popular. To test type lsmod from adb or terminal after boot. Hope this helps.

tiny4579 said:
The first line should be:
Code:
#!/system/bin/sh
and it needs to have execute permissions or it won't execute. Also make sure to save it in UNIX format. I would also add the smartass module as it is quite popular. To test type lsmod from adb or terminal after boot. Hope this helps.
Click to expand...
Click to collapse
eeh im not good with init.d scripts lol

ok i think i got it would it be like this?
Code:
#!/system/bin/sh
/system/bin/insmod /system/lib/modules/tun.ko

Every shell script should contain
#!/system/bin/sh
Sent from my ADR6300 using XDA App

JoelZ9614 said:
ok i think i got it would it be like this?
Code:
#!/system/bin/sh
/system/bin/insmod /system/lib/modules/tun.ko
Click to expand...
Click to collapse
Exactly!
Then just make a line for each module.
EDIT: Though you could just write it like this:
Code:
#!/system/bin/sh
insmod /system/lib/modules/tun.ko
Though to be safe and to make sure you are running that particular insmod command you can leave it the way you have it.

ok done its in my rom RLS3 Thanks Tiny Great work

JoelZ9614 said:
ok done its in my rom RLS3 Thanks Tiny Great work
Click to expand...
Click to collapse
No prob! It's been a good project for me.

[Dev] Touchscreen driver on 80 for ICS

Hi All,
I'd need someone to test ICS touchscreen drivers for 80G9. I patched them "blindly" as I don't have a 80, it would be nice if some could test them and confirm that patches are working.
If someone is up to it, here is how to test:
Install my ics build.
unzip the attached file to a directory
boot ics.
get list of loaded modules, please report what is written there to this thread.
Code:
adb shell lsmod
push kernel module:
Code:
adb push cypress-tma340.ko /lib/modules
adb push tr16c0-i2c.ko /lib/modules
reboot:
Code:
adb shell reboot_into sde
Test touch screen and report here if it works.
Thanks!
LeTama

lsmod:
Code:
Module Size Used by Not tainted
btwilink 2696 0 - Live 0xbf027000
hso 25266 0 - Live 0xbf01a000
usbserial 24035 0 - Live 0xbf00e000
tr16c0_i2c 3860 0 - Live 0xbf008000
cypress_tma340 11232 0 - Live 0xbf000000
works great
any chance for a git repo with your work?
i also tried to compile ICS on my own but couldnt get around the crashing servicemanager.

a1Pha said:
works great
any chance for a git repo with your work?
i also tried to compile ICS on my own but couldnt get around the crashing servicemanager.
Click to expand...
Click to collapse
So it works for you? Great news! I'll update my build then...
Both modules are loaded, do you know which one is in use ?
Regarding repo, well, I'm far from having a structured build. It's currently a mix of stock firmware+ics for panda with few patches for surface flinger and wifi+binaries for 3D from TI Gingerbread
I can give you the few diffs I have if you want...

rmmod tr16c0_i2c doesnt have any effect while rmmod cypress_tma340 kills my touch functionality.
so i guess cypress_tma340 is used
yeah, diffs + config from kernel & ics would be very very great

a1Pha said:
rmmod tr16c0_i2c doesnt have any effect while rmmod cypress_tma340 kills my touch functionality.
so i guess cypress_tma340 is used
yeah, diffs + config from kernel & ics would be very very great
Click to expand...
Click to collapse
Thanks for the test. We'll see if tr16c0_i2c is used on others...
Here are my diffs, raw, with lots of traces commented not used anymore. On kernel side, it has the ram_console on top of the touchscreens changes.
Location for ram console is poor as it is, I did put it there because I was experimenting 3.0 drivers. 0x9EEE0000 is better if you want to keep it. Config is the same as archos with extended dmesg (CONFIG_LOG_BUF_SHIFT=17).
Last point, 3D driver binaries are from there:
git://git.omapzoom.org/device/ti/proprietary-open.git, refs/heads/gingerbread

need to delete this..

jpacleb85 said:
need to delete this..
Click to expand...
Click to collapse
Obsolete now...

i meant that i need to delete that post.. sorry

jpacleb85 said:
i meant that i need to delete that post.. sorry
Click to expand...
Click to collapse
Yes, understood later... No problem!

Compiling kernel modules...

Hey all. So I was looking at this cpu frequency governor for the razr:
http://forum.xda-developers.com/showthread.php?t=1367255
I was wondering how I could get this working on our devices, so, just for curiosity's sake, I copied it to the phone and ran insmod on it. It did a quick cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors and found the new governor listed, so I opened up SetCPU and set it as the governor. cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor told me, however, that I was still on mot_hotplug, so I switched to ondemand and then back to the eprj governor... still told me I'm on ondemand.
I figure that the razr's and droid 3's kernel modules are not binary-compatible, so I'm gonna need to recompile the module. How do I go about doing this?
Thanks.
-Zane Kaminski

I understand what your getting at but we can't flash kernels best you can do is port kernel modules
Sent from my XT862 using XDA

saintlikesniper said:
I understand what your getting at but we can't flash kernels best you can do is port kernel modules
Sent from my XT862 using XDA
Click to expand...
Click to collapse
Yeah... I wanna compile this module for the Droid 3.

ZaneKaminski said:
Yeah... I wanna compile this module for the Droid 3.
Click to expand...
Click to collapse
The source for the current 890 kernel is on Sourceforge.net under the Bionic's GPL software page.
Sent from my DROID3 using XDA

Would it be possible to build a kernel module to add loop device support? Would like to be able to chroot Ubuntu.
Sent from my DROID3 using Tapatalk 2

Q9Nap said:
Would it be possible to build a kernel module to add loop device support? Would like to be able to chroot Ubuntu.
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
loop devices are already supported. If your using linux installer from the market just ignore the warinngs. To manully mount a loop device.
Code:
# mount loop.img directory
If for some reason that doesn't work use losetup.
Code:
# losetup /dev/block/loop7 loop.img
# mount -t auto /dev/block/loop7 directory

eww245 said:
loop devices are already supported. If your using linux installer from the market just ignore the warinngs. To manully mount a loop device.
Code:
# mount loop.img directory
If for some reason that doesn't work use losetup.
Code:
# losetup /dev/block/loop7 loop.img
# mount -t auto /dev/block/loop7 directory
Click to expand...
Click to collapse
Still have questions about getting Linux installer working, started a thread here
http://forum.xda-developers.com/showthread.php?p=24855920
To avoid clogging up this thread any further, any help would be appreciated.
Sent from my DROID3 using Tapatalk 2

i'm in the process of setting up a build environment for kernel modules and have the 5.6.890 kernel source. couple of questions:
does anyone have links to any good info on how to build android kernel modules? google isn't being very helpful.
would it be possible to get modules built with the 5.6.890 source working with the 5.7.906 kernel?
thanks in advance

[HOWTO] Increase available RAM in ROMs based on "That kernel" and "Those libs"

[HOWTO] Increase available RAM in ROMs based on "That kernel" and "Those libs"
Most Atrix users using ROMs with "That kernel" and "Those libs" are stuck with 778MB or 784MB of available RAM (even after applying the ramfix for international Atrix users), but a few users are reporting getting around 855MB of RAM available on their phones. After a quick comparison of the /proc/cmdline on these phones (and since having more RAM can't hurt), here's a guide how to increase your available RAM on these ROMs. This guide is intended for people who have 778-784MB available on their phone when using ROMs based on "That kernel" and "Those libs" with the original ramfix. DO NOT USE ON OTHER ROMS!
WARNING: STOP NOW AND DO NOT FLASH IF YOU DON'T KNOW WHAT YOU'RE DOING!!!
PLEASE READ AND UNDERSTAND EVERYTHING BEFORE YOU DO ANYTHING!
I have personally tested this with Somebody's CM10 and AtrICS v2.
It should theoretically work with other ROMs based on "That kernel" and "Those libs", but use it at your own risk!
Now, on to the good part:
1. Get your current /proc/cmdline.
You can do this by using terminal emulator and typing:
su
cat /proc/cmdline
Click to expand...
Click to collapse
or by using a root browser and copy your /proc/cmdline to your sdcard.
A note from NFHimself:
NFHimself said:
Hi,
Please emphasize that the script needs YOUR complete /proc.cmdline in there, from a working phone adb session, not recovery adb session as the recovery has it's own possible /proc/cmdline via a different kernel, etc. You are not just editing the mem=?? stuff.
What would be best is to first create a zip that is plain jane what your /proc/cmdline is or one that uses setcmdline with a blank argument or "". That way you can reset to default in case of errors. Or you can just fastboot flash your boot partition, no need for an sbf.
Cheers!
Click to expand...
Click to collapse
2. Download attached file.
3. Edit the updater-script file in the zip.
Extract the zip and find META-INF\com\google\android\updater-script
Windows users: Edit the file using Notepad. DO NOT USE WORDPAD. WordPad changes the Unix-style CR to Windows style CR-LF, which may cause problems.
Once you open the file, find this in the file:
run_program("/tmp/setcmdline", "[email protected] [email protected] [email protected] vmalloc=256M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:d00:100:800,kpanic:2100:400:800 security=tomoyo mot_prod=1 androidboot.serialno=XXXXX00000");
Click to expand...
Click to collapse
Change the red part with your own cmdline, which you got in step 1. Take care especially on the tegrapart and androidboot.serialno parameters. DO NOT USE A TEGRAPART AND/OR SERIAL NUMBER FROM ANOTHER PHONE!
If your original cmdline that you got in step one was:
[email protected] [email protected] [email protected] vmalloc=320M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:1100:100:800,kpanic:2500:400:800 security=tomoyo mot_prod=1 androidboot.serialno=12345ABCDE
Click to expand...
Click to collapse
then you should modify the part of the updater-script mentioned above to look like this:
run_program("/tmp/setcmdline", "[email protected] [email protected] [email protected] vmalloc=256M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:1100:100:800,kpanic:2500:400:800 security=tomoyo mot_prod=1 androidboot.serialno=12345ABCDE"
Click to expand...
Click to collapse
Only the change the red part in the script with the red part in your original cmdline. DO NOT MODIFY ANYTHING ELSE!
4. Save the file, and repack the zip.
5. Flash zip.
6. You should now have 855MB of RAM available. Enjoy your extra 70+MB of RAM.
WARNING: DO NOT FLASH IF YOU DON'T KNOW WHAT YOU'RE DOING!!!
I AM NOT RESPONSIBLE FOR ANYTHING THAT GOES WRONG BECAUSE OF YOU BORKING YOUR CMDLINE!!!
Thanks to: NFHimself for creating the ramfix binary and Ilkinansr92 for his cmdline.

Thanks!!! I will givi it a try.
Edit: Working just fine....thanks again!
from the (m)ATRIX...

Thanks!
Now i have 855mb of RAM available

I have 815mb of ram available and i am using Nottachtrix Rom, i am going to try this method in 2 mins and i will give feedback..
Edit:
it gives me error which number 6 (my rom is working, no problem). i know nottachtirx is not based on that kernel but i had wanted to try it whether work or not.

ramanujan20 said:
I have 815mb of ram available and i am using Nottachtrix Rom, i am going to try this method in 2 mins and i will give feedback..
Edit:
it gives me error which number 6 (my rom is working, no problem). i know nottachtirx is not based on that kernel but i had wanted to try it whether work or not.
Click to expand...
Click to collapse
I got that error too....on JB...but that was because I was doing something wrong.
But I think this is for JB...

Cocolopes said:
I got that error too....on JB...but that was because I was doing something wrong.
But I think this is for JB...
Click to expand...
Click to collapse
are you using something related to "that rom"? (kernel, libs, rom)

jhonnyx said:
are you using something related to "that rom"? (kernel, libs, rom)
Click to expand...
Click to collapse
No...someones Cm10 here...but now is working...I just replace the update script in the zip...and work perfect
from the (m)ATRIX...

successful
oh yeah~
now i have 855mb ram now!
i found that you can copy the file /proc/cmdline to computer,and select the words you need
in this way,you can do it more simple and more safe!

Well. 855 MB RAM. I am using CM10 with that libs.
Thank a lot.

Cocolopes said:
No...someones Cm10 here...but now is working...I just replace the update script in the zip...and work perfect
from the (m)ATRIX...
Click to expand...
Click to collapse
Well, "Somebody's" CM10 IS using the kernel & libs from "That ROM", so I'd say it's very much related.

Can anybody help me i don't even have 500 mb in manage apps - running apps section
International user and using MRom
Sent from Otterbox Atrix 4G Rockz

ranjithkumar1201 said:
Can anybody help me i don't even have 500 mb in manage apps - running apps section
International user and using MRom
Sent from Otterbox Atrix 4G Rockz
Click to expand...
Click to collapse
Have you applied the ramfix? If not download this and apply it and it will fix that problem:
http://forum.xda-developers.com/attachment.php?attachmentid=710806&d=1315237274

Perfect. Thanks !

I hope the OP doesn't mind...
Here's my take on this. I took the source of the cmdline utility and improved it greatly, now it's almost a full-featured kernel cmdline editor. Then I used this new utility in the update script to dynamically edit the system cmdline.
Bottom line: this ZIP should work on all systems without any modifications.
WARNING: not fully tested, use at your own risk!
(If anything goes wrong, it should be easily revertable simply by reflashing the kernel, either from recovery or via fastboot.)
EDIT: added a couple more options, recompiled the cmdline binary and repackaged the ZIP.

ravilov said:
I hope the OP doesn't mind...
Here's my take on this. I took the source of the cmdline utility and improved it greatly, now it's almost a full-featured kernel cmdline editor. Then I used this new utility in the update script to dynamically edit the system cmdline.
Bottom line: this ZIP should work on all systems without any modifications.
WARNING: not fully tested, use at your own risk!
(If anything goes wrong, it should be easily revertable simply by reflashing the kernel, either from recovery or via fastboot.)
EDIT: added a couple more options, recompiled the cmdline binary and repackaged the ZIP.
Click to expand...
Click to collapse
Works beautifully on someone's cm10! Big thanks.
Sent from my MB860

ravilov said:
I hope the OP doesn't mind...
Here's my take on this. I took the source of the cmdline utility and improved it greatly, now it's almost a full-featured kernel cmdline editor. Then I used this new utility in the update script to dynamically edit the system cmdline.
Bottom line: this ZIP should work on all systems without any modifications.
WARNING: not fully tested, use at your own risk!
(If anything goes wrong, it should be easily revertable simply by reflashing the kernel, either from recovery or via fastboot.)
EDIT: added a couple more options, recompiled the cmdline binary and repackaged the ZIP.
Click to expand...
Click to collapse
sorry for ask but i don't get it this is a script to modify the cmdline or is an auto modify tool for the cmdline?

Maibol said:
sorry for ask but i don't get it this is a script to modify the cmdline or is an auto modify tool for the cmdline?
Click to expand...
Click to collapse
Both actually.
It includes a tool that can modify the cmdline, and a script that does modify the cmdline automatically, by utilizing the tool.

ravilov said:
Both actually.
It includes a tool that can modify the cmdline, and a script that does modify the cmdline automatically, by utilizing the tool.
Click to expand...
Click to collapse
thanks nice tool i gon give it a try

Why so some Atrixes have 815 MB RAM and some others 879 MB ?
And ravilov, does your script work on gingerbread ROMs, too?
Sent from my CM7 powered Atrix using TapaTalk \o/

the.cybot said:
And ravilov, does your script work on gingerbread ROMs, too?
Click to expand...
Click to collapse
Actually, I'm not sure. It doesn't seem to work for me. The boot image gets updated correctly but for some reason the new cmdline is not used when the kernel boots. I'm using MROM, latest release. Maybe it works different on another ROM. Maybe this whole cmdline business is specific to stock kernels only. Needs more research.