Database Develop

{UTIL}( Vibrant )Enable Adb Push / Pull

We had are First Sleepless Night with the New baby Boy.... Between Trying Figure out what was Wrong & taking turns with the Wife Holding Aries, I tried Pushing File's & forgot adb push didn't work...
Now this Script originally is what I made for the Behold 2, but the Basic still works For the SGV..
Just mod the script if your using the userinit.sh
Using this script you can place the userinit.sh any place you would Like...
I hope ever gets Good use out of this & Please Enjoy!
~Eugene
Download > adbpushGS1.zip
Installing*
Reboot to recovery, run the update.zip to run ClockworkMod Recovery, then installed the ZIP..

eugene373 said:
We had are First Sleepless Night with the New baby Boy.... Between Trying Figure out what was Wrong & taking turns with the Wife Holding Aries.
Click to expand...
Click to collapse
Glad mine is now past that stage! lol
Thanks for the script.

Anyone test this with the init script + this?
Sorry for double doubting again ) But i just want confirmation.
Also, Some of us are still having force close and other issues with the init sript. Just FYI.

rhcp0112345 said:
Anyone test this with the init script + this?
Sorry for double doubting again ) But i just want confirmation.
Also, Some of us are still having force close and other issues with the init sript. Just FYI.
Click to expand...
Click to collapse
FYI, I don't have nor Run the inituser.sh, so FC IDK... doubting People Gets Old ( Mainly when you state it )..
I will never Release Something that Don't work &/or would brick a Device!
Script Does work, I'm leaving up to the User to add back in support for userinit.sh though.
~Eugene

Word. so ill wait till someone tests this with the userinit
I think it has something to do with davik cache. I have to figure out a way to clear all cache without wiping. I dont want to go through all that non-sense.
Great work though. *Hats off*

Thank's Eugene for all your hard work,your the sh**

Hey eugene you think your battery hack will work on the vibrant?
sent using my xda app

this won't work with the userinit because it replaces the same file as the userinit. Now it could easily be modified to do both.....

anomalous3 said:
this won't work with the userinit because it replaces the same file as the userinit. Now it could easily be modified to do both.....
Click to expand...
Click to collapse
That's what I said
Just mod the script if your using the userinit.sh
Click to expand...
Click to collapse

eugene373 said:
That's what I said
Click to expand...
Click to collapse
This is what happens when I don't read the whole thread

anomalous3 said:
This is what happens when I don't read the whole thread
Click to expand...
Click to collapse
np
Honestly you could just add the script from userinit.sh inside of the script, or the other way around & should still work fine.

Question, I would like to do as you said. Just add to the userinit
Is the problem just having the system/data mounted? It seems thats all your script does. If so, I can just use a widget to unmount/mount as i go. and not bother to have my system/data mounted all the time Please let me know.
Thanks!

Nicely done! I appreciate the work, I was hoping someone figured out a way to do adb push.. xda to the rescue again

hi, somewhat n00bie-ish (sorry) but what could
..deamon started.. "remount failed: no such file in directory"
in command prompt after i enter "adb remount" mean??

fit333 said:
hi, somewhat n00bie-ish (sorry) but what could
..deamon started.. "remount failed: no such file in directory"
in command prompt after i enter "adb remount" mean??
Click to expand...
Click to collapse
Am having the exact same problem, with a Samsung spica (i5700) though. Any ideas?

adb remount is not needed with my script.. system / rootfs is already mount via the script.

shameless bump
so I can find this easier... I wish our Moderator would get on his job...
thanks for your work eugene..

[TOOL] Auto-Deodexer/ROM builder 2.5.6.2 - UPDATED 02/04/2011

this script is based on the work to Danesham90 and others see link
http://forum.xda-developers.com/showthread.php?t=598026
===============================================================================
Tested on the Samsung Vibrant, Script may need modification for other phones
===============================================================================
===============================================================================
Directions:
===============================================================================
the easy way:
1. turn on USB debugging
2. plug phone in to computer
3. run the script and follow the screen pormpts
the script will download everything needed to make a
signed deodexed clockwork flashable update.zip while also
adding root and the modified 3e recovery in the proccess.
===============================================================================
the hard way:
http://forum.xda-developers.com/showpost.php?p=10986893&postcount=28
================================================== =============================
Code:
/* This program is free software. It comes without any warranty, to
* the extent permitted by applicable law. You can redistribute it
* and/or modify it under the terms of the Do What The **** You Want
* To Public License, Version 2, as published by Sam Hocevar. See
* http://sam.zoy.org/wtfpl/COPYING for more details. */
UPDATED 02/03/2010
bug fix to signupdate.jar
clockwork script tweeks
UPDATED 02/02/2011
added upload to ROM to SDCard
added reboot recovery
added test sign all apk's in ROM - see README for details
added pull "/data/app/" and install "/data/app"
UPDATED 02/01/2011
added adb on by default toggle
added data wipe toggle
updated smali/baksmali to 1.2.6
UPDATED 01/31/2011
updated adb
fix similar filename deletion when using delete.txt
added barebones_delete.txt deletes everything that
does not cause phone to crash
UPDATED 01/29/2011
add "symlink dumpstate SYSTEM:bin/dumpmesg" to update-script.
add "symlink debuggerd SYSTEM:bin/csview" to update-script.
completed secondary method to make ROM from extracted Odin files.
see this post for instructions
http://forum.xda-developers.com/showpost.php?p=10986893&postcount=28
UPDATED 01/28/2011
added auto delete apk's (bloat removal), edit bin/example_delete.txt and rename to delete.txt
added auto add apk's (pre-install or update apk's) add apk's to bin/apks directory
UPDATED 01/23/2011
fix path error when space in user name
UPDATED 01/22/2011
updated TempRoot.exe to not trigger anti-virus
updated Superuser.apk

This is fantastic! Thank you for always making things a little less troublesome.

Oooops, last minute change broke something, fixed and re-uploaded.

untermensch said:
Oooops, last minute change broke something, fixed and re-uploaded.
Click to expand...
Click to collapse
Thanks for the heads up. I was just testing this on KA5 for funsies. It looked like it went ok but there was a prob with temp root at the beginning and it looked like a few java errors at the end. I'll re-download and give it another go.
Edit: Ah, looks like it's working now. Temp root worked and it downloaded the modem and kernel.
Edit2: So it looked as though everything worked fine, but when I went to install it I got
E:Can't symlink /system/bin/cat
E:Failure at line15:
symlink toolbox SYSTEM:bin/cat
Installation aborted.

Whitehawkx said:
Thanks for the heads up. I was just testing this on KA5 for funsies. It looked like it went ok but there was a prob with temp root at the beginning and it looked like a few java errors at the end. I'll re-download and give it another go.
Edit: Ah, looks like it's working now. Temp root worked and it downloaded the modem and kernel.
Click to expand...
Click to collapse
I just tested on my laptop and got a java out of memory error
while signing the rom so I increased the heap size which seems
to have fixed it.

untermensch said:
I just tested on my laptop and got a java out of memory error
while signing the rom so I increased the heap size which seems
to have fixed it.
Click to expand...
Click to collapse
Yea I got the same thing as well. Thanks again, will give it another go.
Update: The process was more in-depth when deodexing. Signing went through np and when I flashed through clockwork it worked (goodbye splash screen!). There must be some issue with KA5 though. It got through to the Galaxy S screen and then started vibrating and then blackscreen. T_T

Thank god for this.. (Deodexer)
Thanks untermensch, your the best

Really really appreciate this. Thanks a bunch!

Most useful tool EVAR!
I T W O R K E D~!
My final attempt last night did not shoot out the "signed_ROM.zip" at the end. I ran it again this morning on KA5 and when it finished I had the signed_ROM.zip in the folder. Put that on my internal, flashed through clockwork and viola! Doedexed KA5 with root and modded 3e recovery. I can't thank you enough Untermensch for putting this together for everyone.
"Give a man fish feed him for a day. Provide him with tools to fish and feed him for a lifetime." (Yea I tweaked it but you get the idea!)

I noticed one thing. During the deodexing process I got [null] on one file in the core.odex. After it had all finished up I looked in the framework folder and core.odex was still there. So am I correct in assuming that it did not doedex properly? Other than that everything else looks golden.

Oh this is sick. i was looking for this all day the otherday when i was trying to deodex ka5! you rock and rule. i cant wait to explore the possiblities!

Whitehawkx said:
I noticed one thing. During the deodexing process I got [null] on one file in the core.odex. After it had all finished up I looked in the framework folder and core.odex was still there. So am I correct in assuming that it did not doedex properly? Other than that everything else looks golden.
Click to expand...
Click to collapse
I deleted the core.odex file and rebooted just to see what would happen and it soft bricked and is stuck at the Vibrant screen. So it seems the only issue lies in deodexing the core.jar at this point.

can i use this to port a rom? forgive me if that is a noob question. just wanted to know if i had the right idea...

Whitehawkx said:
I noticed one thing. During the deodexing process I got [null] on one file in the core.odex. After it had all finished up I looked in the framework folder and core.odex was still there. So am I correct in assuming that it did not doedex properly? Other than that everything else looks golden.
Click to expand...
Click to collapse
yep that was an baksmali error, likely you could run the script again and it
would baksmali OK.
this script is a real system stress test, any way I increased the java maxmem
setting for framework files to 1024m added error logging and the script will
now stop if there is an error. hopefully to prevent a broken ROM from being
released.

Whitehawkx said:
I deleted the core.odex file and rebooted just to see what would happen and it soft bricked and is stuck at the Vibrant screen. So it seems the only issue lies in deodexing the core.jar at this point.
Click to expand...
Click to collapse
can you reproduce this error? I have seen it once but cant reproduce it

untermensch said:
yep that was an baksmali error, likely you could run the script again and it
would baksmali OK.
this script is a real system stress test, any way I increased the java maxmem
setting for framework files to 1024m added error logging and the script will
now stop if there is an error. hopefully to prevent a broken ROM from being
released.
Click to expand...
Click to collapse
untermensch said:
can you reproduce this error? I have seen it once but cant reproduce it
Click to expand...
Click to collapse
Pretty sure the core.odex [null] error I got happened every time I ran the program. I ran it once after the 1:25am update and it happened. That is also the time it did not produce the signed_ROM.zip. I ran it again this morning after I saw the OP had been updated and it did produce the signed_ROM.zip but I still got the [null] error on core.odex. I'm going to Odin KA5 and do it again right now. I will let you know how it works out.
On a side note. I flashed the one I recieved this morning with everything being deodexed except the core.jar and it ran great until I deleted the odex file. Anywho, will test now. Also, not sure if this matters but I am running 32-bit Windows 7.
Update1: Initial news is good. Core.jar was deodexed properly with no errors. Will let you know how the entire process fairs once its completed.

Worked perfectly. I got no errors and everything deodexed properly. Flashed it on my phone and it's running just fine. You are awesome.

Thanks for retesting, glad it worked, there are thousands of files being generated
an lots of java processes being spawned so there are bound to be an occasional
error. I have added an automatic retry when there is an error to the next version
should be posted some time tomorrow.

I'm about 3/4 the way through testing this out - it seems to be working just fine with the exception that every command is appended with "ATTRIB" is not recognized as...
Hopefully it will work anyway.
One thing I noticed that might speed the script up in the beginning would be a root check, I have already rooted this rom but it still needed to run rageagainstthecage.

I've been looking for something like this forever now, thanks so much! Can't wait to play with it.
Sent from my SGH-T959 using Tapatalk

[Q] how to enable init.d support

I'm using the the stock 2.3.4 from Spice website and this is by far the best considering wifi important.
My question is, can we enable init.d support or we need a special kernel for that?
I tried a tut. from zeppelin but failed miserably...
Any idea guys???

whyzee,
I followed this http://forum.xda-developers.com/showthread.php?t=1017291 and was able to use init.d without any issues.

cowsgo said:
whyzee,
I followed this http://forum.xda-developers.com/showthread.php?t=1017291 and was able to use init.d without any issues.
Click to expand...
Click to collapse
Thanks for the link but that was the one I tried without success .... Should try again when I have some real time...

whyzee
did you get an error when you ran the script? If you didn't then get root explorer from the market and see if you have the folder. It should be in the \system\etc folder. When I ran it I had no issues and followed the instructions that were on the page. Dumb question, did you reboot your phone once you ran this? If you got a error then you could try pm Zep and see if he has ideas that might help.

cowsgo said:
whyzee
did you get an error when you ran the script? If you didn't then get root explorer from the market and see if you have the folder. It should be in the \system\etc folder. When I ran it I had no issues and followed the instructions that were on the page. Dumb question, did you reboot your phone once you ran this? If you got a error then you could try pm Zep and see if he has ideas that might help.
Click to expand...
Click to collapse
The script you are executing is not meant for our device. Its trying to mount system partition as mtd type, while we need emmc partition type. Also, our device does not have moto-boot-mode file which this script is trying to replace.
So my suggestions are :
If you are using MIUI or CM, then they already support init.d scripts. (I guess)
Or
If you are using stock or andro - id then just copy following code in post boot.sh (something like that) found in /system/etc/, at the end of file.
Code:
for BOOT in "/system/etc/init.d/"*; do
.$BOOT
done
P.S. Note that you have enabled executable permission for all of your scripts placed in /system/etc/init.d
Sent from my CSL-MI410 using XDA App

Thanks for the replies guys, I've jumped to MIUI 1.10 now and as Napstar said it natively supports init.t...

whyzee said:
Thanks for the replies guys, I've jumped to MIUI 1.10 now and as Napstar said it natively supports init.t...
Click to expand...
Click to collapse
hi
correct me if im wrong. To my knowledge u need init.d to use apps2sd so u can put ur apps on ur SD and now since our phone has around 1GB phone storage which i feel is more than enough to install all the apps u need I dont see a reason why we need the init.d

haree said:
hi
correct me if im wrong. To my knowledge u need init.d to use apps2sd so u can put ur apps on ur SD and now since our phone has around 1GB phone storage which i feel is more than enough to install all the apps u need I dont see a reason why we need the init.d
Click to expand...
Click to collapse
init.d is a folder on /system/etc folder which runs whatever scripts you put in it during boot.....

[TOOL] The O2x Nullifier 2.2 - Single & Dual Passes!!! SU660

Hello my fellow Android crack flashers! So Volk and I have wrote(him) and tested(me) his g2x nullifier for our phones. Well it works flawlessly! Which his thread is here. So with our learning adventures he has helped me port it to the O2x. So here is the run down. This was originally created as the g2xscrubber was insufficient enough for our flashberry addiction, and on top of that if wouldn't wipe our /cache either. And yes this is the same thing from the p990 dev thread but I just wanted to post in the official su660 thread since its avail for me to do so...
So the domino effect has begun. This is a simple script that will wipe your internal partitions cleaner then a whistle and get it dam near like new status, perfectly ready for a ROM. Like as if you just purchased it and didnt have any data on it nor a ROM and needed to be flashed. And yes it came all tricked out like that with CWM and all.. haha
So here it is...
The O2x Nullifier
This uses a special command in combination with a special file to overwrite the internal partitions with 0's, hence "Null" for 0 and "-ifier" for the fact that it does something. It also formats the partitions afterward, including /cache too! Enjoy!
Some brief need to knows:
1. This is a little lengthy process so please bear with it. The longest wipe is on /data which will take about 7 minutes. Obviously, make sure you have plenty of battery life before running it. I've ran this Nullifier like 20 times in the last two days of first testing and on average its about 1204 seconds or about 19.8 minutes, on average. The Single pass zip is only half of the time of course. Or you can just watch the progress bar. After 20 times of nullifing and log pulling in 2 days, im pretty dang sure the bar is accurate. So enjoy!
2. ONCE THE NULLIFICATION PROCESS HAS BEEN COMPLETED DO NOT, I REPEAT, DO NOT TURN OFF OR LET YOUR PHONE DIE BEFORE FLASHING A ROM OR RESTORING... or you will brick your phone.
3. I will provide help, support, etc. for this, but as always flash at your own risk and I am not responsible if you turn your phone into your next non-aerodynamic frisby.
Enjoy!
Also I have now decided to copy the log to sdcard at completion (thanks to DARKSIDE for the idea). But from now on the log created in /tmp while in cwm is now copied to sdcard as O2x-Nullified-recovery.log. So it will still be deleted from RAM but never lost any more!!!!! muhahahahahahah... love it!
Thanks go to Волк aka Volk for letting me test and learn from his G2x Nullifier script. And also to owain94 for helping me make sure that this thing will run ok on the O2x, since I dont actually have the O2x..

Also if is doesn't work, please we need logs. You need to use a file explorer or put the external sdcard into your pc and grab and upload or pm me the log from your sdcard the file will be named 'O2x-Nullified-recovery.log'

Hi!
I have su660, i would like to know the difference bettween nullifier single n dual? Or which one works with su660?
Im new to this.
Thanks a lot!
Sent from my LG-SU660 using XDA

magbobote69 said:
Hi!
I have su660, i would like to know the difference bettween nullifier single n dual? Or which one works with su660?
Im new to this.
Thanks a lot!
Sent from my LG-SU660 using XDA
Click to expand...
Click to collapse
haha nice avatar pic! but the difference is based on ocd levels. lol Basically we originally did the Nullifier to have two passes in the nullification process just to make sure that all data has been zero'd out before formatting. However with the time it takes to complete such a process it seemed a bit much and end users didnt like it much. So we made the single and dual passes. Basically the single pass only does one nullification pass before formatting and moving to the next partition.

getting an error on CWM saying "build.prop s660..."something and its not doing its thing...sorry was not able to get the exact message...will try later if have time

chupi_24 said:
getting an error on CWM saying "build.prop s660..."something and its not doing its thing...sorry was not able to get the exact message...will try later if have time
Click to expand...
Click to collapse
sorry didnt see this till now.. it was my moms bday yesterday so I wasnt paying attention... however please get the log from /cache/recovery/last_log... Im not going to guess at what the error could be. I gotta have actual info to give you a better resolution.

[MOD][ICS+GB] lagfree & dalvik fix (automatic installer released!)

This is an automatic installer for the lagfree script and the dalvik fix build.prop changes.
It does detect if you're using ICS or GB and does set it up accordingly.
Explanation and credits are in post 2. Manual instructions on how to apply this without the installer are at post 3. Have fun!
Most easiest way to check if the tweak script works is to open terminal before installation and type:
Code:
cat /proc/sys/vm/*
After flashing the zip do the same thing again and check if the numbers have changed (which they should have done).
pastime1971 said:
tony and i have worked out a flashable zip of init.d script + build.prop mod
there are two types of installations. choose one you like.
* system installation *
buttery-system.zip : edits /system/build.prop & installs /system/etc/init.d/99tune
to revert it, simply re-flash ROM.
you have to flash this every time you flash a ROM.
* user installation *
buttery-local.zip : edits /data/local.prop & installs /data/local/userinit.d/99tune
buttery-local-remove.zip : reverts /data/local.prop & removes /data/local/userinit.d/99tune
this changes /data/ and therefore, the effect is permanent unless you change it manually, which is the reason for buttery-local-remove.zip
# do a nandroid backup always.
# it probes if ROM is GB or ICS and apply mod accordingly. (only tested on ICS. please test it and feedback on GB.)
# to check if it is working, do the following in terminal
Code:
getprop | grep dalvik
getprop cm.buttery.active
cat /proc/sys/vm/*
!!! this script is based on vork kernel installer. the credit goes to vork team (benee and kiljacken)
Click to expand...
Click to collapse
Please give pastime1971 a "Thanks" at the following post: original post by pastime1971

Credits to whom they belong:
This idea has been ported over from the G2x forum (link, by flak0).
Thanks goes to flak0 and batoo.
The original thread of the tune.sh script (by batoo) can be found here.
and of course to pastime1971 who did the most work for this great installer. Thank you so much!
What does it do?
atb1183 said:
dexopt flags:
m=y -> use mapping, optimize the dalvik code
u=n -> NOT a uniprocessor, optimize for multicores
v=n -> do Not verify , breaks some old app compatibility but dalvik get a bit more speed (tonyp: doesn't work in Android 2.3!)
o=v -> im not sure, i think this sets optimization level to the highest. but again, not sure. alternate is o=a.
might wanna look into the /proc/sys/vm/dirty_ratio tweaks, cant remember exactly and im quite surprise many roms dont have these tweaks in the init.d scripts
it specifies how much cache/junk data to keep in memory. if the ratio is high, after a while, so much crap is kept that it waste your ram and slow the phone down.
Click to expand...
Click to collapse

Manual instructions:
Read this properly! This guide requires some knowledge of editing system files and running scripts.
It wouldn't harm to do nandroid backup! I didn't do one and everything worked fine - but it's on your own risk! You have been warned!
(if your phone won't boot anymore wiping /system and reflashing your ROM should restore everything without you loosing any data).
First we need to edit some dalvik dexopt flags in the build.prop (you can do that with the build.prop app from the market):
backup your build.prop
edit your build.prop
ICS: change dalvik.vm.dexopt-flags=.... to dalvik.vm.dexopt-flags=m=y,v=n,o=v,u=n
GB: change dalvik.vm.dexopt-flags=.... to dalvik.vm.dexopt-flags=m=y,o=v,u=n
right below add: dalvik.vm.execution-mode=int:jit
ICS only: change windowsmgr.max_events_per_sec=... to windowsmgr.max_events_per_sec=300
comment out dalvik.vm.heapgrowthlimit if it exists by placing a # in front (or delete the whole line).
save
Now Reboot to Recovery and Wipe Dalvik + reboot
Now you need to download and extract the attached tune.sh script and place it into /sdcard
Either run the script with Terminal Emulator or with the Script Manager app (don't forget to use root)
For the first method: Open the "Terminal Emulator" app and type:
Code:
su
cd /sdcard/
sh tune.sh
You're done. But you need to run the script after every reboot - or just place it under /system/etc/init.d/, rename it to "90tune" and set the permission to "rwxr-xr-x", then it will run automatically at each reboot.
Have fun!

@tonyp....
well just that I am a bit busy at office and saw ur thread fortunately....I would wait for people to give their comments, experience on GB (as I use DJ 1.5 beta from Carburano )and also the CWM flashable file so I dont need to do all that hardwork and reserve that for the office
Thanks once again mate

As soon as I'm able I will try and test this on GB and ICS. Maybe in the evening.
Thanks for bringing this to our attention Tony
Sent from my LG-P990 using XDA

tonyp said:
I'm "porting" over some information from the G2x forum (link) which should possibly help against the well known decreasing speed of the phone after some uptime.
At the G2x forum they're pretty excited and talking from buttery smoothness.
Thanks goes to flag0 and batoo.
The original thread of the attached script (by batoo) can be found here.
Read this properly! This guide requires some knowledge of editing system files and running scripts for now.
Edit: Good news, I linkes an app to edit the build.prop and included instructions how to run the script. Now it's pretty straightforward and you should be done in 10-15minutes.
It would be possible to create a flashable zip which does these steps for you, but creating a script which edits values in the build.prop isn't that easy and takes some time. If it works well it will get incorporated by the ROM devs anyway - owain already said at the G2x forum that he will include it in a later build.
It wouldn't harm to do nandroid backup! I didn't do one and everything worked fine - but it's on your own risk! You have been warned!
(if your phone won't boot anymore wiping /system and reflashing your ROM should restore everything without you loosing any data).
First we need to edit some dalvik dexopt flags in the build.prop (you can do that with the build.prop app from the market):
backup your build.prop
edit your build.prop
change dalvik.vm.dexopt-flags=.... to dalvik.vm.dexopt-flags=m=y,v=n,o=v,u=n
right below add: dalvik.vm.execution-mode=int:jit
change windowsmgr.max_events_per_sec=... to windowsmgr.max_events_per_sec=300
comment out dalvik.vm.heapgrowthlimit by placing a # in front (or delete the whole line).
save
Now Reboot to Recovery and Wipe Dalvik + reboot
Now you need to download and extract the attached tune.sh script and place it into /sdcard
Either run the script with Terminal Emulator or with the Script Manager app (don't forget to use root)
For the first method: Open the "Terminal Emulator" app and type:
Code:
su
cd /sdcard/
sh tune.sh
You're done. But you need to run the script after every reboot - or just place it under /system/etc/init.d/, then it will run automatically at each reboot.
Have fun! Works like a charm for me!
I only tested it with CM9 (owain build #77).
If you want to test that out in GB (either Stock or CM7) you probably shouldn't touch "windowsmgr.max_events_per_sec" (don't do step 5 above!).
Please give some feedback!
Click to expand...
Click to collapse
Thanks bro its flak0 though lol
Sent from my LG-P999 using xda premium

Crashing my Cm7 ROM
Goodmorning,
Ive just tried the tweak, but it just crashed my Phone. After updating the Build.prop the phone, just wouldnt start up anymore.
Restored backup.. and up and running again!
Im running Temasek CM7.
Just so you know!
Regards!
WyCkson

wyckson said:
Goodmorning,
Ive just tried the tweak, but it just crashed my Phone. After updating the Build.prop the phone, just wouldnt start up anymore.
Restored backup.. and up and running again!
Im running Temasek CM7.
Just so you know!
Regards!
WyCkson
Click to expand...
Click to collapse
I'm pretty sure this is cm9 ics only as it says ics in the title.
Sent from my Optimus 2X using XDA

Shadowchaz said:
I'm pretty sure this is cm9 ics only as it says ics in the title.
Sent from my Optimus 2X using XDA
Click to expand...
Click to collapse
OP states: 'If you want to test that out in GB (either Stock or CM7) you probably shouldn't touch "windowsmgr.max_events_per_sec" (don't do step 5 above!).'

Ximo F. Verde said:
OP states: 'If you want to test that out in GB (either Stock or CM7) you probably shouldn't touch "windowsmgr.max_events_per_sec" (don't do step 5 above!).'
Click to expand...
Click to collapse
You are right, missed that line! Thanks for clarifying.

flak0 said:
Thanks bro its flak0 though lol
Click to expand...
Click to collapse
lol sorry for that

I tried it with owain 78, I placed the script in init.d after editing build.prop and before rebooting, and it works perfect for now, no lag at all. Thanks tonyp,
Enviado desde mi LG-P990 usando Tapatalk 2

Tried on XXmrHyde's unnoficial 8 - works likec harm - that's great!

sergiob8 said:
I tried it with owain 78, I placed the script in init.d after editing build.prop and before rebooting, and it works perfect for now, no lag at all. Thanks tonyp,
Click to expand...
Click to collapse
Make sure to set the permission to rwxr-xr-x
Code:
chmod 0755 /system/etc/init.d/tune.sh

DAMN! Went back to CM7 because of this lag.
CM9 was unusable for me because I needed my phone to run properly at work.
I'm some kind of forced to flash
Don`t feel a need to do anything like that for CM7
Runs like a charm for the last few days.

I created a flashable zip to install the tune.sh script into init.d: http://d-h.st/NFq
You still need to manually edit the build.prop. I probably won't create an installer for that because this will probably get incorporated into the ROMs anyway.

tonyp said:
I created a flashable zip to install the tune.sh script into init.d: http://d-h.st/NFq
You still need to manually edit the build.prop. I probably won't create an installer for that because this will probably get incorporated into the ROMs anyway.
Click to expand...
Click to collapse
i was forced to get back to CM7 like others cause of this lag... will try this script later but
thanks a lot man, good to see people like you helping comunity.

it works for me, system is very fast
BUT google play store force closes instantly -.-

Player9446 said:
it works for me, system is very fast
BUT google play store force closes instantly -.-
Click to expand...
Click to collapse
After manual method, my play store still works flawless
Sent from LG 2X using Tapatalk 2 Elite

Player9446 said:
it works for me, system is very fast
BUT google play store force closes instantly -.-
Click to expand...
Click to collapse
Clear market data. Are you using cwm touch?
Sent from my LG-P990 using XDA