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)

[RAM Script] Tweaking Juwe11's RAM script for O2X, good for all ROM support init.d

======
Preface
======
The script is actually Base on Juwe11's RAM script
which you can found here... http://forum.xda-developers.com/showthread.php?t=1111145
==========
Main Content
==========
The adj value of his script is a bit too tight for Our O2X...
so the Launcher is killed quite often if many apps opened in the background.
Here's the adj value changes I made, originally, Juwe11's values are..
"0,1,2,4,6,15" and I change it to, "0,1,2,7,8,9"
the forth value is for HIDDEN_APP_MIN_ADJ, which including the Launcher (I'm using LauncherPro) belongs to this category when you open some foreground application.
the default android value for this is also 7, and I find the OOM value for Launcher is 6 usually... so Juwe11's "4" will lead to our Launcher being Killed, keep it at 7, never tried to have mine killed yet.
The last 2 vaule just make sure the last category EMPTY_APP_ADJ is kill earlier than the previous..
About the minfree vaule...
I change it to "1536,3072,4096,7680,8960,10240" which actually the same values of "Moderate preset" of autokiller
which is enough to ensure most RAM being use before killing for faster task switching...
=====
Credit
=====
!! Credit goes to Juwe11 for his mighty RAM script~ !!
Backup your RAMscript and remove it to somewhere before install this...
install via CWM, it will put the script into your /etc/inti.d/ that's it, boot and try

i just installed it,
i will let u know what are the results,
u are correct, the original script kills the launcher and apps specially XDA

will try this configuration on auto killer memory seems good m8 to set it to moderate

shpapy said:
i just installed it,
i will let u know what are the results,
u are correct, the original script kills the launcher and apps specially XDA
Click to expand...
Click to collapse
I'm not sure if other Launcher would have a different OOM value~
I have Autokiller memory optimizer which I paid before...so I can view OOM value easily..
But with this Script... I guess really no task killer needed for our 2X already.

antec123 said:
will try this configuration on auto killer memory seems good m8 to set it to moderate
Click to expand...
Click to collapse
so, just edit the minfree value according to the values inside AutoKiller if you find some other setting suits you more
but about the adj value... I guess that part is already good enough
now I find my phone already got around 60-90 free RAM at any time...
Multiple games running at the background while web browsing...
and the Browser usually got a higher OOM, which tends to kill earlier than Games..
it is reasonable.. as the WEB you can load again with the same URL..
while the game got killed, you lost the state... android is doing it's work nicely I guess.

best memory managment script i have tryed is v6supercharger http://forum.xda-developers.com/showthread.php?t=991276
I think its the best of the best.

orlox said:
best memory managment script i have tryed is v6supercharger http://forum.xda-developers.com/showthread.php?t=991276
I think its the best of the best.
Click to expand...
Click to collapse
I tried both V6 and Juwe11's before...
and I manage to be patient enough to follow step by steps...
for installing so many things... and it just put a script in init.d at the end...
And I found it do not contain adj value in it, so I come back to Juwe11's
but anyway, this is your choice...

thanks for that script
just a quick question
would this script also work on a sgs2, running oxygen aosp stock rom?

pa.pn2 said:
thanks for that script
just a quick question
would this script also work on a sgs2, running oxygen aosp stock rom?
Click to expand...
Click to collapse
same as Original Juwe11's version.
it was suppose to work on any ROM which support init.d
but the values may need some tweaking accordingly.

squide said:
I'm not sure if other Launcher would have a different OOM value~
I have Autokiller memory optimizer which I paid before...so I can view OOM value easily..
But with this Script... I guess really no task killer needed for our 2X already.
Click to expand...
Click to collapse
Sorry to let you down. But the results are the same......
Sent from my LG-P990 using XDA App

squide said:
I tried both V6 and Juwe11's before...
and I manage to be patient enough to follow step by steps...
for installing so many things... and it just put a script in init.d at the end...
And I found it do not contain adj value in it, so I come back to Juwe11's
but anyway, this is your choice...
Click to expand...
Click to collapse
adj values are in /data/SuperChargerAdj while minfree values are in /data/SuperChargerMinfree.
it's just a script in init.d at the end, you only need to follow it step by step...

squide said:
so, just edit the minfree value according to the values inside AutoKiller if you find some other setting suits you more
but about the adj value... I guess that part is already good enough
now I find my phone already got around 60-90 free RAM at any time...
Multiple games running at the background while web browsing...
and the Browser usually got a higher OOM, which tends to kill earlier than Games..
it is reasonable.. as the WEB you can load again with the same URL..
while the game got killed, you lost the state... android is doing it's work nicely I guess.
Click to expand...
Click to collapse
i set the preset to moderate and get about 126-128mb on free ram pretty impressive and the stock browser don't get close so quickly nice! i use v10e ESA and neoblaze kernel

Works on CM7?

_Vegas said:
Works on CM7?
Click to expand...
Click to collapse
it should work on all ROM supporting init.d
in case you don't like it, go to /etc/init.d to remove the script and reboot.
it wont modify your file system..
it just override some system value on boot.
if you removes the script.. your phone would back to the state before you install this.
so, just try see if u like, if not, delete it, reboot, that's it.

Works really nicely on CM7 nightly.
Sent from my Optimus 2X

Bit of a Dumb question but my phone still has the Stock rom and doesn't have the init.d Folder
if I created /system/etc/init.d and copied the script into that would this work?

waynefox said:
Bit of a Dumb question but my phone still has the Stock rom and doesn't have the init.d Folder
if I created /system/etc/init.d and copied the script into that would this work?
Click to expand...
Click to collapse
Sorry, no. You need a custom rom of some sort to get init.d support.

TrymHansen said:
Sorry, no. You need a custom rom of some sort to get init.d support.
Click to expand...
Click to collapse
You need a Custom Kernel supporting init.d to be more accurate.
and NeoBlaze is a good one to try with.
if you really need to keep your stock ROM..
First of all you still need to root your phone
Install ROM manager from market
flash the Clockworkmod via ROM manager
install NeoBlaze Kernel, then you're ready.
if warranty is your concern, take a look to the Nvflash thread..
O2X is ALMOST unbrickable, almost.

squide said:
You need a Custom Kernel supporting init.d to be more accurate.
and NeoBlaze is a good one to try with.
if you really need to keep your stock ROM..
First of all you still need to root your phone
Install ROM manager from market
flash the Clockworkmod via ROM manager
install NeoBlaze Kernel, then you're ready.
Click to expand...
Click to collapse
I'm pretty sure that won't work. You need ROM-support as well. (A Ramdisk script which starts the init.d. thing to be even more accurate.) Feel free to prove me wrong.

TrymHansen said:
I'm pretty sure that won't work. You need ROM-support as well. (A Ramdisk script which starts the init.d. thing to be even more accurate.) Feel free to prove me wrong.
Click to expand...
Click to collapse
Ramdisk is a part of the kernel, so if you bung a kernel that supports init.d on (any) rom it'll run what's in there assuming it's eXecutable.
You can do it on the stock rom even, as long as you have a init.d kernel (and create the entries in ../etc/init.d/).
Although I can't "prove" this to you at the moment...

[ROM][KANG³][CM9][UNOFFICIAL] Linaro Optimized Droid Incredible CM9 ROM

Because the CyanogenMod developers decided not to switch to the Linaro toolchain, I decided that I would do it myself. This ROM is very similar to invisiblek's nightlies, but has a few more patches from the CyanogenMod queue applied and other changes made to enable building with GCC 4.7 and -O3. I will try to put up a new build at least once every few days if there is much being merged into the CM9 tree.
The main benefit of using the Linaro optimized ROM is that the UI is faster and snappier. Some applications (especially heavy ones like Google Play) are noticeably less laggy. Also, you get higher benchmark scores. (Yay!)
My kernel is included as the stock kernel in this ROM.
As always, if you are in any doubt whatsoever, you should do a Nandroid backup before flashing this ROM.
Changelog:
8/15/2012
No changes from me; just updates from the CM repo
8/12/2012
Revert the patch increasing the number of cached app pages, as this used more memory and made the launcher homescreens lag
8/10/2012
No changes from me; just updates from the CM repo
8/7/2012
Remove the ext4 sdcard patch because it was causing multiple regressions in handling the sdcard, even though it was still fat32
8/6/2012
Apply patch (http://review.cyanogenmod.com/#/c/20061/) to remove videos intended only for the tuna device
Attempt to workaround the lag issues by making the browser kill itself when the last tab is closed
8/3/2012
Apply patch (http://review.cyanogenmod.com/#/c/20654/) to enable HTTPS Google searches in the stock browser for better privacy
Apply patch (http://review.cyanogenmod.com/#/c/19807/) to allow mounting ext4 sdcards
7/31/2012
Update to the Linaro 2012.7 toolchain
Compile the kernel with "-O3 -fno-tree-vectorization"
7/22/2012
Add TCP MSS iptables filter to the kernel as it seems to be used during tethering
Add the Linaro string processing optimizations to the ROM
7/21/2012
Include my "Lite" kernel with the ROM
Update to a new, unreleased-as-of-yet version of my kernel with more optimizations
7/16/2012
Disable WebGL again. It was causing hardlocks on a number of enabled sites
Apply patch (http://review.cyanogenmod.com/#/c/18490/) to allow for the downloading of "unsafe" attachment files in Email
7/10/2012
Apply patch (http://review.cyanogenmod.com/#/c/18319/) to speed up some app starts
Apply patch (http://review.cyanogenmod.com/#/c/17552/) to add more NEON optimizations to pixelflinger
Enable WebGL
7/8/2012
Apply Evan McClain's libskia update (fixes the blacked-out JPEG issue)
Fix some media players like MX Player (an instruction was missing because it was optimized out by O3)
Apply more optimization flags
6/27/2012
Initial release
Apply CM9 patches to fix compile failures with GCC 4.7 and enable O3 optimizations
Switch to libjpeg-turbo
Disable scrolling cache (increases scrolling smoothness for non-hardware-accelerated listviews)
Issues (specific to the Linaro optimized version):
Turning off Bluetooth causes the Phone app to crash. It restarts immediately, so there are no long-term effects.
Bluetooth file transfer (OPP) does not work. The Linaro team experiences this bug too and is currently looking for a solution. I will update as soon as a solution is found.
You can download the source I use to compile this ROM by following these instructions: https://github.com/invisiblek/android_device_htc_inc/blob/ics/README.md
Compiling Instructions:
These compiling instructions are for Linux. They should work on any distro, but I am using the latest release of (K)ubuntu.
Follow all of the instructions from the source link above except for the last one. This will download the source tree and get you set up to build.
Assuming you are already in the root directory of your source tree ("~/cm9" if you followed the above instructions), run the following commands in the terminal. Some of the git pulls will display a text editor screen. When you get this, just press Ctrl-O, Enter, and finally Ctrl-X.
Code:
cd external/skia
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_skia refs/changes/85/14585/1
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_skia refs/changes/86/14586/1
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_skia refs/changes/87/14587/1
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_skia refs/changes/88/14588/1
git commit -a
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_skia refs/changes/89/14589/1
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_skia refs/changes/10/15810/1
cd ../webkit
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_webkit refs/changes/90/14590/1
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_webkit refs/changes/91/14591/1
cd ../../frameworks/base
git pull http://review.cyanogenmod.com/CyanogenMod/android_frameworks_base refs/changes/92/14592/1
git pull http://review.cyanogenmod.com/CyanogenMod/android_frameworks_base refs/changes/80/17380/2
cd ../../external/freetype
git pull http://review.cyanogenmod.com/CyanogenMod/android_external_freetype refs/changes/54/12654/2
cd ../../build
git pull http://review.cyanogenmod.com/CyanogenMod/android_build refs/changes/58/17358/4
Follow the instructions here to replace your libjpeg with libjpeg-turbo.
Open the file ~/cm9/frameworks/base/core/java/android/widget/AbsListView.java in your favorite text editor. Go to line 753 and change it to read "setScrollingCacheEnabled(false);".
Open the file ~/cm9/bionic/libc/arch-arm/bionic/libgcc_compat.c in your favorite text editor. Go to line 114 and insert two new lines reading "XX(__aeabi_llsl) \" and "XX(__aeabi_llsr) \" below it.
Open the file ~/cm9/build/core/config.mk in your favorite text editor. Go to line 91 and change it to read "COMMON_GLOBAL_CFLAGS:= -DANDROID -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith -Wno-error=strict-aliasing -Wno-error=enum-compare". Go to line 312 and change it to read "TARGET_GLOBAL_CFLAGS += $(COMMON_GLOBAL_CFLAGS) -march=armv7-a -mcpu=cortex-a8 -mtune=cortex-a8". Go to line 315 and change it to read "TARGET_GLOBAL_CPPFLAGS += $(COMMON_GLOBAL_CPPFLAGS) -march=armv7-a -mcpu=cortex-a8 -mtune=cortex-a8".
Open the file ~/cm9/build/core/combo/TARGET_linux-arm.mk in your favorite text editor. Go to line 47 and change it to read "prebuilt/$(HOST_PREBUILT_TAG)/toolchain/linaro-4.7.1/bin/arm-linux-androideabi-". Go to line 149 and change it to read "TARGET_GLOBAL_CPPFLAGS += -fvisibility-inlines-hidden".
Download this file and unzip it to ~/cm9/prebuilt/linux-x86/toolchain/linaro-4.7.1
You are finally ready to build! Open a terminal to the ~/cm9 directory, then run ". build/envsetup.sh" and "brunch inc". This will take a long time.

Great, going to try this out. Maybe the keyboard works better, I've shut down pop up and prediction.
Still lags horribly.
Edit: Is gapps included or do I need to flash them?
Edit: Wow.. Maybe some won't notice it, but I've seen an increase of speed and snapiness. Keyboard lag seems to have stopped somewhat.. its still there but its along better.
Sent from my ADR6300 using Tapatalk 2

withbloodskies said:
Great, going to try this out. Maybe the keyboard works better, I've shut down pop up and prediction.
Still lags horribly.
Edit: Is gapps included or do I need to flash them?
Edit: Wow.. Maybe some won't notice it, but I've seen an increase of speed and snapiness. Keyboard lag seems to have stopped somewhat.. its still there but its along better.
Sent from my ADR6300 using Tapatalk 2
Click to expand...
Click to collapse
You still need to flash Gapps. It would be illegal for me to include them.
The best workaround I have found for keyboard lag is to disable spellchecking. You still get autocorrect like in GB; it just doesn't put a red squiggly under misspelled words.

Good work, I'll have to try it out. Any chance you putting this up on goo.im and/or ROM Manager, to expedite the update process?

Very nice work,Thanks for your contribution .

PonsAsinorem said:
Good work, I'll have to try it out. Any chance you putting this up on goo.im and/or ROM Manager, to expedite the update process?
Click to expand...
Click to collapse
I will look at putting it on goo.im.

One last suggestion (for now) before I'm off to flash it: thought of changing the ROM and zip name just slightly so it's not confused with invisiblek? Maybe throw a linaro in there somewhere or something? Right now, they have the same names (and dates, too, shortly) with just the compile times and machines being different. Now off to flash.

PonsAsinorem said:
One last suggestion (for now) before I'm off to flash it: thought of changing the ROM and zip name just slightly so it's not confused with invisiblek? Maybe throw a linaro in there somewhere or something? Right now, they have the same names (and dates, too, shortly) with just the compile times and machines being different. Now off to flash.
Click to expand...
Click to collapse
I'm not quite sure how to do that. Can you tell me?

mamarley said:
I'm not quite sure how to do that. Can you tell me?
Click to expand...
Click to collapse
You'll have to do some tweaking to the bottom of this file. Hard to explain on the phone. As part of my compile script I wrote for my kangs, it sed/replaced the necessary lines with pons (I'd use linaro for yours). Experiment with it till it looks how you want it to. Any questions, let me know.
https://github.com/CyanogenMod/android_vendor_cm

mamarley said:
You still need to flash Gapps. It would be illegal for me to include them.
The best workaround I have found for keyboard lag is to disable spellchecking. You still get autocorrect like in GB; it just doesn't put a red squiggly under misspelled words.
Click to expand...
Click to collapse
I wanted to point out that I got keyboard lag on ICS even on my gnex. There's not much that can be done. I never did try disabling spell checker. Liquid 1.5 helped with its linaro optimizations but what helped more to me was the interactive governor I was using had input boost which boosts frequency upon using the touchscreen to minimize lag rather than wait for it to ramp up. The other part nay have been the go_high setting of 50% load. I'm not using all the technical terms but to high-speed frequency is user configurable and its the speed it will jump to at a specified load. It may exist in our current interactive governor.
I do know that there is no keyboard lag in jelly bean that I can tell.
Sent from my Galaxy Nexus using Tapatalk 2

tiny4579 said:
I do know that there is no keyboard lag in jelly bean that I can tell.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Its all that butter
Anyway I used DPI and it works but it makes alot of apps force close. I was on 175, the same thing happens on Evervolv's Roms too.
Sent from my ADR6300 using Tapatalk 2

Can i flash this over invisiblek's Cm9 nightlies?
Or do i have to do a full wipe?
I have all my apps and everything just the way i want it.. I really dont wanna wipe.

Gorilla* said:
Can i flash this over invisiblek's Cm9 nightlies?
Or do i have to do a full wipe?
I have all my apps and everything just the way i want it.. I really dont wanna wipe.
Click to expand...
Click to collapse
You can flash over.
I have been flashing over since the CM7 days and have never had any problems. I even flashed the CM9 ROM right on top of the CM7 ROM and only had to clear the data for 2 apps to get everything working again.

Marley, Im booting up now, I flashed it, flashed your Lite Kernel, and USB fast charge zip.
Heres to hoping for some sexy Linaro Goodness!
Ill report back to how this runs.

Gorilla* said:
Marley, Im booting up now, I flashed it, flashed your Lite Kernel, and USB fast charge zip.
Heres to hoping for some sexy Linaro Goodness!
Ill report back to how this runs.
Click to expand...
Click to collapse
Same here. Just booted up. This is legit. Snappier than the CM9 nightlies so far. I didn't flash the USB zip- what will that give me?

statusqu0 said:
Same here. Just booted up. This is legit. Snappier than the CM9 nightlies so far. I didn't flash the USB zip- what will that give me?
Click to expand...
Click to collapse
That enables USB Fast Charge. It will make your phone charge much faster when it is plugged into a PC or some third-party wall/car chargers.

mamarley said:
That enables USB Fast Charge. It will make your phone charge much faster when it is plugged into a PC or some third-party wall/car chargers.
Click to expand...
Click to collapse
Forgive my noob-ness, but will that damage the battery in any way?

statusqu0 said:
Forgive my noob-ness, but will that damage the battery in any way?
Click to expand...
Click to collapse
No, it just makes it charge in the same way it would if you plugged it into the stock wall charger.

seems good so far. a couple slow-downs at first but seem to have gone away.

Yea, seems snappier than the other cm9 rom..
Im just hoping i dont get phantom touchscreen issues.. like the screen typing for me,.

[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.

Speed Tweaks for Blur ROMS

This will only modify what needs to be tweak in the build.prop.
It will not modify anybody else's build.prop work.
This means it can be used after you install a custom ROM and
keep any changes your dev has made to their own build.prop.
I have screen shots of my 3 Mps DSL Line and my LTE.
If it gives any indication about how much more performance gain there is
WiFi gives me up to 2.9 Mbps normally.
LTE gives me close to 30 Mbps normally.
Revision 2:
little less aggressive on the phone itself
little bit better WiFi and LTE speeds
cleaned up TONS of code and named everything!
Also the 2nd version will save a backup so you
can restore your old build.prop if you do not like
the changes that were made from from the tweaks.
AND it should keep the original build.prop.
Mind you, the undoer will only work with version 2.
you can also make a swap file (paging file like windows)
command will be
# busybox mkswap /dev/block/zram0
# chmod 077 /dev/block/zram0
# reboot

how did you install an ULV kernel on your droid 4?

dewhashish said:
how did you install an ULV kernel on your droid 4?
Click to expand...
Click to collapse
through an inti.d script

Won't install
I can't get these to install, using safestrap 3.0. Any ideas what I am doing wrong?

zeroktal said:
I can't get these to install, using safestrap 3.0. Any ideas what I am doing wrong?
Click to expand...
Click to collapse
it has only been tested on SS211.
I believe there are differences in the way it reads
and mounts the partitions...
what does the error say?

Not to sound stupid, but will this work on Eclipse 1.3.4 for D4?
Sent from my DROID4 using xda app-developers app

panamakevin said:
Not to sound stupid, but will this work on Eclipse 1.3.4 for D4?
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
the way It is set it up -should- in theory work with any ROM made for the D4.

Can we get this written for ss305?

jkieffer46 said:
Can we get this written for ss305?
Click to expand...
Click to collapse
yes give me a little while to install and reconfigure for ss3

jkieffer46 said:
Can we get this written for ss305?
Click to expand...
Click to collapse
I have tried and failed miserably! I am no means a "true" programmer BUT
I have a work around for the people with SS3. Although it does involve a
terminal emulator which is free and the Google Play Store link is BAM!
I will make a flashable fix in the morning with instructions on how to do it.
I will also have a screenshot of what to type as well. The script will still do
the same thing as the flashable BUT in the terminal (manual way)

Just ran the .sh
I just modified and ran the SH from the command line. Only had to remove one > per file. Thanks, my speed increase isn't amazing, but its solid. You are Awesome.

Is there a way to flash this in ss305 yet or what

No, I'm sorry, haven't time to work on it. right now the work around is through a shell and reboot
Sent from my DROID4 using xda premium

Ok ill wait. I dont know how to do anything other than flash zips

Does it have any tweaks for GSM/HSDPA? The 3G is really poor on Droid 4.