Related
This will NOT work in CM5.0b4 as JIT has been disabled entirely
It seems like a lot of people are constantly pulling/editing/pushing build.conf in order to turn JIT on and off, so I threw together a short script to toggle it on and off.
It's nothing elaborate, but it gets the job done. This is meant to work with the build.prop that comes stock with cyanogenmod 5.0b2 but will most likely work with other build.props that have JIT.
Steps to run the script:
1) Download jit.txt, rename it jit.sh
2) If you downloaded from your computer, run "adb push jit.sh /sdcard" or mount your device and copy to your sdcard.
3) In terminal on Nexus One:
$ su
# sh /sdcard/jit.sh
JIT toggled ON
JIT enabled upon reboot
#
You can also set it up in GScript or GScript Lite so you can add an icon on your homescreen to toggle JIT more easily:
1) From command line: mv /sdcard/jit.sh /sdcard/gscript/jit.sh
2) Open GScript
3) Go to Menu->Add Script
4) Go to "Load file"
5) Select jit.sh
Then to make an icon on your homescreen:
1) Long press homescreen
2) Select Shortcuts
3) Select GScript(Lite)
4) Select jit
You must reboot for the changes to take effect after running the script. If you prefer, simply put "reboot" (without quotes) on it's own line at the end of the script and it will reboot automatically. Only do this after you have confirmed that the script works for you.
If you are using Windows, make sure you use the attached jit.txt rather than copying the code from this post. Copying/pasting the code will not work because of Windows CR/LF line breaks.
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
if grep -q fast /system/build.prop ; then
sed -i s/=int:fast/=int:jit/ /system/build.prop
echo "JIT toggled ON"
echo "JIT enabled upon reboot"
else
sed -i s/=int:jit/=int:fast/ /system/build.prop
echo "JIT toggled OFF"
echo "JIT disabled upon reboot"
fi
exit
mhaedo said:
It seems like a lot of people are constantly pulling/editing/pushing build.conf in order to turn JIT on and off, so I threw together a short script to toggle it on and off.
It's nothing elaborate, but it gets the job done. This is meant to work with the build.prop that comes stock with cyanogenmod 5.0b2.
Simply push the script to your phone (sdcard, or wherever you please) and run it. For example, put the quoted text into a file called jit.sh, push it to the root of your sdcard, and run "sh /sdcard/jit.sh" from a terminal. You can also set it up in GScript or GScript Lite so you can add an icon on your homescreen to toggle JIT more easily.
You must reboot for the changes to take effect.
Click to expand...
Click to collapse
Nice - been looking for just this, thanks. As a bit of a n00b, any idea why this doesn't seem to run in GScript Lite? I get the SU request OK, but then nothing - don't see the echo'd text at all, nowt. Running CM5b2 .29 kernel.
Ive installed pauls modaco patch wil this turn jlt off? its annoying me
Thanks for this script !
I just pull, nano, and push it back.
I don't think It's 100% stable.
push/pull? Shoot, I just use vi on build.prop from betterterminal. Don't have to mess with adb at all
Since you need to reboot anyway, couldn't we just put "reboot" in place of "exit"? I'm assuming that's not part of the script to save, since you have "fi" at the end of it. Personally, what I did is save 2 versions of build.prop to my sdcard and then built gscripts to swap 'em out. lol A little more crude, but just as effective.
when i try to run the jit.sh file in terminal i get:
failed: no such file or directoryk3 on /system : not found
sdcard/jit.sh : 13: syntax error: end of file unexpected (expecting 'then")
am i completely retarded?
trisl said:
Nice - been looking for just this, thanks. As a bit of a n00b, any idea why this doesn't seem to run in GScript Lite? I get the SU request OK, but then nothing - don't see the echo'd text at all, nowt. Running CM5b2 .29 kernel.
Click to expand...
Click to collapse
Yeah, I had the same problem. Remove the su request from superuser.apk. Then, run any script that requires root. Click remember, and allow. It will not work at this point. Back out to the homescreen with the back button, then go back into GScript Lite and run it again. It should work this time.
Guitarfreak26 said:
Ive installed pauls modaco patch wil this turn jlt off? its annoying me
Click to expand...
Click to collapse
Not sure. I would assume so, never seen the build.prop that's used but I don't see why it would be any different.
Mi|enko said:
Since you need to reboot anyway, couldn't we just put "reboot" in place of "exit"? I'm assuming that's not part of the script to save, since you have "fi" at the end of it. Personally, what I did is save 2 versions of build.prop to my sdcard and then built gscripts to swap 'em out. lol A little more crude, but just as effective.
Click to expand...
Click to collapse
That would be more efficient, but I just enjoy clicking my icon a few times and toggling it on and off Don't ask me why.
[email protected] said:
push/pull? Shoot, I just use vi on build.prop from betterterminal. Don't have to mess with adb at all
Click to expand...
Click to collapse
How would I do that? I have betterterminal emulator pro..
Four Fourty Four said:
How would I do that? I have betterterminal emulator pro..
Click to expand...
Click to collapse
$ su
# vi /system/build.prop
Proceed to edit (man vi, google vi). Bit of a pain in the ass though if you switch back and forth frequently.
mhaedo said:
$ su
# vi /system/build.prop
Proceed to edit (man vi, google vi). Bit of a pain in the ass though if you switch back and forth frequently.
Click to expand...
Click to collapse
Don't forget, you need to remount /system as rw also. it is a tiny bit of a pain, but I don't see much of a reason to switch back and forth all the time. Thus far I have yet to have any problems with JIT.
[email protected] said:
Don't forget, you need to remount /system as rw also. it is a tiny bit of a pain, but I don't see much of a reason to switch back and forth all the time. Thus far I have yet to have any problems with JIT.
Click to expand...
Click to collapse
The only time I consistently have problems with JIT is when tethering. Otherwise, I have yet to have any issues. I tether frequently, hence the script.
BTW, thanks for Apps2SD(2) and OpenOverclocker. They were very helpful to me at one point.
blakestimac said:
when i try to run the jit.sh file in terminal i get:
failed: no such file or directoryk3 on /system : not found
sdcard/jit.sh : 13: syntax error: end of file unexpected (expecting 'then")
am i completely retarded?
Click to expand...
Click to collapse
+1
I'm getting this message also.
blakestimac said:
when i try to run the jit.sh file in terminal i get:
failed: no such file or directoryk3 on /system : not found
sdcard/jit.sh : 13: syntax error: end of file unexpected (expecting 'then")
am i completely retarded?
Click to expand...
Click to collapse
Hm, strange. I can't duplicate this error. The steps I take are as follows:
1) Cut/paste the quoted code in the original post and save it in a document called jit.sh
2) On computer, adb push jit.sh /sdcard
3) In terminal on Nexus One:
$ cd sdcard
$ su
# sh jit.sh
JIT toggled ON
JIT enabled upon reboot
#
I'm sorry I can't be more help, but I'm not sure why you'd see that error.
mhaedo said:
Hm, strange. I can't duplicate this error. The steps I take are as follows:
1) Cut/paste the quoted code in the original post and save it in a document called jit.sh
2) On computer, adb push jit.sh /sdcard
3) In terminal on Nexus One:
$ cd sdcard
$ su
# sh jit.sh
JIT toggled ON
JIT enabled upon reboot
#
I'm sorry I can't be more help, but I'm not sure why you'd see that error.
Click to expand...
Click to collapse
Ok, I didn't do the whole adb push thing, I just copied it to my SDcard root from windows. Is that the problem?
BoostedSR20 said:
Ok, I didn't do the whole adb push thing, I just copied it to my SDcard root from windows. Is that the problem?
Click to expand...
Click to collapse
Ah, it's the line breaks. Windows uses a pair of CR and LF characters to terminate lines. Unix based system use an LF character only.
You can get a utility to convert the line breaks to unix style line breaks. I'm sure it will come in handy. I'll also upload the jit.sh with proper line breaks to the original post.
BoostedSR20 said:
Ok, I didn't do the whole adb push thing, I just copied it to my SDcard root from windows. Is that the problem?
Click to expand...
Click to collapse
Just tried pushing it to the sdcard, that went thru ok.
Still cant get it to run, same error. I've tried your command in the OP, and the what you wrote out a couple posts up. Same error on each one.
mhaedo said:
Ah, it's the line breaks. Windows uses a pair of CR and LF characters to terminate lines. Unix based system use an LF character only.
You can get a utility to convert the line breaks to unix style line breaks. I'm sure it will come in handy. I'll also upload the jit.sh with proper line breaks to the original post.
Click to expand...
Click to collapse
Ahhh, so it had to do with me making the file in the Windows Notepad. Got it..
As mentioned here and here:
adding "echo ro.HOME_APP_ADJ=1" to /data/local.prop fixes the launcher redraw lag.
Documentation:
http://code.google.com/p/sipdroid/wiki/FAQ
Due to limited memory home screen often takes several seconds to load. Luckily these phones allow root access. Issue the command "echo ro.HOME_APP_ADJ=1 >/data/local.prop" and reboot, to lock home screen in memory.
Click to expand...
Click to collapse
update:
it does seem to made a difference
Here are the commands: (batch file to do this here,post#5)
Code:
adb remount
adb pull /system/build.prop .
edit build.prop with a decent text editor and add these two lines a the end
#fix for screen redraw lag
ro.HOME_APP_ADJ=1
Click to expand...
Click to collapse
Code:
adb push build.prop /system/
adb reboot
you could try
Code:
adb shell stop
adb shell setprop ro.HOME_APP_ADJ=1
adb shell start
if it works you just have to add ro.HOME_APP_ADJ=1 to build.prop.
g4rb4g3 said:
you could try
Code:
adb shell stop
adb shell setprop ro.HOME_APP_ADJ=1
adb shell start
if it works you just have to add ro.HOME_APP_ADJ=1 to build.prop.
Click to expand...
Click to collapse
tried:
Code:
adb shell stop
adb shell setprop ro.HOME_APP_ADJ 1
adb shell start
My phone hot rebooted after the last command.
After it rebooted I ran
Code:
C:\Users\meeee>adb shell getprop ro.HOME_APP_ADJ
4
Since its 4. I guess it did not stick.
Also tried setting it and immediately reading it, did not stick.
Code:
C:\Users\meeee>adb shell setprop ro.HOME_APP_ADJ 1
C:\Users\meeee>adb shell getprop ro.HOME_APP_ADJ
4
The setting stuck after putting it in build.prop, time to check if it made any difference...
Code:
C:\Users\meeee\Desktop>adb shell getprop ro.HOME_APP_ADJ
1
Don't reboot, try the commands and watch out if your problem got fixed. If it works like that you can add the line to build.prop.
g4rb4g3 said:
Don't reboot, try the commands and watch out if your problem got fixed. If it works like that you can add the line to build.prop.
Click to expand...
Click to collapse
It did it on its own.
seems to be working, updated op with the commands.
britoso said:
seems to be working, updated op with the commands.
Click to expand...
Click to collapse
Added this cmd to build.prop but see no changes... what lags you talking about btw?
For me my home screens were sluggish. There was a delay when I tried to switch desktops.
I made a little bat.file, which adds those 2 lines to your build.prop.
- put "Launcher_lag_fix.bat" in ..Android/tools/
- doubleklick
- and wait till reboot.
rori~ said:
I made a little bat.file, which adds those 2 lines to your build.prop.
- put "Launcher_lag_fix.bat" in ..Android/tools/
- doubleklick
- and wait till reboot.
Click to expand...
Click to collapse
thanks rori.
No one has posted yet what the command actually does. All it does is tell Android to try to keep the launcher in memory.
Shouldn't affect anything like the scrolling or any response while actually using the launcher, but will fix some lag for when going back home from any other app, as it doesn't have to re-launch the launcher if it was kicked out of memory.
Various options like this exist in some launchers, and I think Cyanogenmod has this option in the settings too. They are not all the same as this command though, so this may work better for some people while the other ways to do it may work better for others.
Clarkster said:
No one has posted yet what the command actually does. All it does is tell Android to try to keep the launcher in memory.
Click to expand...
Click to collapse
As per this it locks the 'screen' in memory. (maybe they mean the screen buffer)
Due to limited memory home screen often takes several seconds to load. Luckily these phones allow root access. Issue the command "echo ro.HOME_APP_ADJ=1 >/data/local.prop" and reboot, to lock home screen in memory.
Click to expand...
Click to collapse
Makes sense as I always have had launcher locked in memory before this and was still having my home screen redraw very slowly when I switched to it.
A good find
Btw just for info there were issues in apps from pre release system dump of arc
However if u r using apps from the retail dump 'they don't lag'
Sent from my U20i using XDA App
rori~ said:
I made a little bat.file, which adds those 2 lines to your build.prop.
- put "Launcher_lag_fix.bat" in ..Android/tools/
- doubleklick
- and wait till reboot.
Click to expand...
Click to collapse
can you specify where is the android/tools mentioned, can it be found in all android phones?
Btw, I have seen ">>" and ">" then "space" /data/local.prop in other websites, while in the sipdroid article, it is exactly
"echo ro.HOME_APP_ADJ=1 >/data/local.prop".
otivaeey said:
can you specify where is the android/tools mentioned, can it be found in all android phones?
Btw, I have seen ">>" and ">" then "space" /data/local.prop in other websites, while in the sipdroid article, it is exactly
"echo ro.HOME_APP_ADJ=1 >/data/local.prop".
Click to expand...
Click to collapse
adb comes with the sdk, for my windows machine its at
C:\android-sdk-windows\platform-tools
in unix ">" sends text to a file (deletes whatever was there) and ">>" appends at the end of a file. If you're not familiar its easiest to just add the one line manually at the end of build.prop.
Hey y'all, wondering if anybody can help me with this:
I'm at work and don't have access to ADB. Can I use Root Explorer to copy the file to the sdcard, mount the card on a PC, edit it, and then use Root Explorer to copy it back again? Or will that cause issues with permissions or something?
EDIT: Well it's intellectual now, I nandroided back to my previous ROM due to some other issues. I'd still like to know though.
Ya the root explorer thing should work but just to be safe I would nandroid first cause worst case scenario your phone freezes you pull battery boot into recovery restore nandroid. But seriously I don't think it will be a problem.
Just out of curiosity I wanted to see if I could do this without a computer at all and turns out all you really need to do is download estrong (or any other root explorer), turn root explorer option on, mount /system and go and edit build.prop through the the built in note editor in estrong. So that might be an alternate solution for you kippswanson.
This is my first mod
Tell me how you like it and don't forget to thank if you like it
**REQUIRES ROOT** I am not responsible for any damage done to your device.
Never tried it in 2.1 or DI18, probably would work but not positive. If anyone tries it tell us how it works
-------------------------------
(You will need SDK & ADB)
Instructions:
1. Download the twframework-res.apk
2. Move the twframework-res.apk to the tools folder in the SDK (Usually in C:/Program Files/Android/sdk...or something in that range) [Where ever your SDK is]
*If adb is in platform tools, cut and paste the 3 adb files into tools*
3. In the tools folder, make sure no files are selected and hold shift and right click, then select open command window here.
4. Enter the following 6 commands in this order (ignore # signs or $ signs):
*Your device should ask to allow something SU permissions be sure to accept*
adb push twframework-res.apk sdcard/twframework-res.apk
adb shell
su
remount rw
cat sdcard/twframework-res.apk > system/framework/twframework-res.apk
reboot
Congratulations!!! Your phone should reboot and everything will look as it did in screenshot
I like the look. Might want to put it in a flashable .zip to get more users.
I been away from stock for so long I don't see what exactly the mod is
Sent From Da Hood.
mysteryemotionz said:
I been away from stock for so long I don't see what exactly the mod is
Sent From Da Hood.
Click to expand...
Click to collapse
I hear that lol. Hes got 3 mods in that pic, the short cut buttons on press, status bar background, and the bottom of the status bar
Sent from my SPH-D700 using Tapatalk
Sweet, its short and to the point, but if you click here you can customize it a little more. Some of the wording is similar to this OP as well.
I would love this on my phone but I'm still to new to flashing and roms and tweaking. It would go great with my current layout and color theme
What, I dont get any credit? Kidding. I wanna be in the credits though, I helped. >.> <.<
This guide will show you how to install the V6 SuperCharger script on the Ideapad K1. This script was created by zeppelinrox. I am in no way responsible for any part of this script. This guide is just how I chose to install and configure the script on my K1. Please feel free to experiment with different options, this was meant as a basic setup.
This will work on
Ideapad K1 Honeycomb Rooted 120109 R2 (Must have the R2 update)
http://forum.xda-developers.com/showthread.php?t=1564002
-or-
Ideapad K1 CM9 port
http://forum.xda-developers.com/showthread.php?t=1528775
Before starting please read the entire first post here:
http://forum.xda-developers.com/showthread.php?t=991276
If you like the script make sure you hit "Thanks" on that thread
Keypresses will be in BLUE
Honeycomb specific instructions will be in RED
CM9 specific instructions will be in GREEN
Download the latest version of the V6 SuperCharger script here:
http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
If using CM9, download the modified services.jar file and flash via recovery before starting the guide:
http://goo.im/devs/khanning/k1/modded_services-jar_K1_CM9_ALPHA-1.6.zip
1.
If using adb
Code:
adb remount
adb push V6_SuperCharger_for_Android-Update9_RC8.2.sh /system/xbin
adb shell
If using a terminal emulator
Code:
su
mount -o rw,remount /system
mv /sdcard/Download/V6_SuperCharger_for_Android-Update9_RC8.2.sh /system/xbin
2.
Code:
chmod 755 /system/xbin/V6*
3.
Code:
/system/xbin/V6*
--
Is Home is Locked in Memory?
If it is, Enter Y for Yes, any key for No...
Just say "No" if you don't know: [ENTER]
--
Press the Enter Key... and Come Get Some!! [ENTER]
--
Scrolling Speed Options...
==========================
1 (fast), 2 (normal), 3 (slow)
Please select scrolling speed (1 - 3): I chose 2 here, but you can select any [2] [ENTER]
--
Do you want to use Build.prop...
...or create /data/local.prop?
Enter (B)uild.prop or any key for local.prop: [ENTER]
--
Run Fix Emissions on boot?
Enter N for No, any key for Yes: [ENTER]
--
Press The Enter Key... [ENTER]
--
Integrate? Enter Y for Yes, any key for No: [y] [ENTER]
--
Enter Y for Yes, any key for No: You decide, this is the V6 SuperCharger animation when you run the script
--
...Press the Return or Any Key: [ENTER]
--
Apply SuperMinFree Calculator Settings?
Enter Y for Yes, any key for No: [y] [ENTER]
--
Press The Enter Key... [ENTER]
--
================================================
...SuperClean & ReStart!
================================================
Press The Enter Key... [ENTER]
--
Do you want to SuperClean & ReStart now?
Enter Y for Yes, any key for No: If your using Honeycomb you MUST follow the step below before saying yes here. [y] [ENTER]
FOR HONEYCOMB
if using adb
Open another terminal window and run
Code:
adb shell rm -r /data/firstboot
if using a terminal emulator
Open another terminal tab by tapping the "+" in the top right corner and run
Code:
su
rm -r /data/firstboot
Now go back to the first terminal window and press [y] [ENTER] to run SuperClean and reboot
Click to expand...
Click to collapse
Thats it!! The V6 SuperCharger script should now be enabled.
To check that it's running:
The script sleeps for 90 seconds before it starts the service so make sure the system has been fully loaded for at least 90 seconds.
1.
Code:
adb shell
or
open a terminal emulator then
Code:
su
2.
Code:
/system/xbin/V6*
--
Is Home is Locked in Memory?
If it is, Enter Y for Yes, any key for No...
Just say "No" if you don't know: [ENTER]
--
Press the Enter Key... and Come Get Some!! [ENTER]
Click to expand...
Click to collapse
3. Now make sure you see:
================================================
SuperCharger Level: 100% SuperCharged!
================================================
If so, your all set. If not, smack your face against the keyboard and come join me in freenode IRC room #ideapad-k1
Thanks to zeppelinrox for creating the V6 SuperCharger script. Please be sure to hit "Thanks" at this thread if you like his work.
Can you notice a difference? It was debatable if it helped on the Nook Color, how's it look on the K1 with much better hardware.
Thanks a lot....I just ****ed up my K1 with this **** a second time.
I did stick 100% to your directions....all went fine till the reboot...and then I get thousands of force closes....cant do anything.
I did it the original way in the v6 topic.
I did it your way.
Edit:
Damn I forgot this:
FOR HONEYCOMB
if using adb
Open another terminal window and run
Code:
adb shell rm -r /data/firstboot
if using a terminal emulator
Open another terminal tab by tapping the "+" in the top right corner and run
Code:
su
rm -r /data/firstboot
Now go back to the first terminal window and press [y] [ENTER] to run SuperClean and reboot
---------- Post added at 11:21 PM ---------- Previous post was at 10:41 PM ----------
Update:
thanks it runs....the last part was the problem....will test over the weekend.
Does this really work? That original thread reads (and looks) like an infomercial, LOL. Does your Google Play Store still work properly afterwards?
I installed RAM Manager Pro on mine and was using it for a little while, but then I started noticing that I couldn't update any of my apps through the Play Store. They would constantly say "Downloading..." and nothing would happen. They never got to a KB download counter. When I uninstalled RAM Manager Pro, app updates started working again for me.
ssl123 said:
Does this really work? That original thread reads (and looks) like an infomercial, LOL. Does your Google Play Store still work properly afterwards?
I installed RAM Manager Pro on mine and was using it for a little while, but then I started noticing that I couldn't update any of my apps through the Play Store. They would constantly say "Downloading..." and nothing would happen. They never got to a KB download counter. When I uninstalled RAM Manager Pro, app updates started working again for me.
Click to expand...
Click to collapse
Yes, it works fine. I just installed 1 app and updated a bunch
send by K1
It works. I also just updated some apps and installed a new game from play store (yes I did force the update). Firefox runs faster. Everything "feels" more fluid.
sent from my Ideapad K1 with Tapatalk v2
Twist79 said:
Firefox runs faster. Everything "feels" more fluid.
Click to expand...
Click to collapse
Thanks for the info and thank you Khanning for everything you've done to make the K1 a better device!
Makes a great differance even with rooted HC rom which is already very stable and fast.... Thanks KHanning
Hi, I have searched hi and low to try and find info on this weird bug. I have flashed my note with Odin with LPY and LQ2 and every time the setup wizard is missing and there is no lock screen when I press the power button. Now I have cleaned the device and wiped it, installed different kernels and nothing fixes it. Anyone else had this problem and knows how to fix it?
Sent from my GT-N7000 using Tapatalk 2
Same here with LQ2.
Thank god I am not the only one. I have tried everything to fix it. Any luck?
Can anyone shed light on this. I have flashed back to GB which restores the Setup Wizard and Lockscreen button but then when I flash any official ICS rom there is no setup wizard again. Just starts right to the homescreen which mean you can't restore google apps etc.
Lockscreen fix :
You need root and terminal emulator and this code
Get lockscreen back
su
echo -n ON > /efs/imei/keystr
sync
To bad I didnt invent this myself source http://forum.xda-developers.com/showthread.php?p=25953317 go thank this guy
Sent from my GT-N7000 using Tapatalk 2
Thank you I will try this
Sent from my GT-N7000 using Tapatalk 2
i've try to do with terminal emulator but still got something wrong when i create the command..
type "su" pass with grant by SuperSu
type "echo -n ON > /efs/imei/keystr" it appear cannot create the command got i/o bla bla bla
type "sync" and nothing happen and still missing my lock screen...many custom rom i've been try all got the same issue...please help...:crying:
reehan80 said:
i've try to do with terminal emulator but still got something wrong when i create the command..
type "su" pass with grant by SuperSu
type "echo -n ON > /efs/imei/keystr" it appear cannot create the command got i/o bla bla bla
type "sync" and nothing happen and still missing my lock screen...many custom rom i've been try all got the same issue...please help...:crying:
Click to expand...
Click to collapse
- type into the command:
su
echo -n ON > /efs/imei/keystr
sync
Go to home, force close your terminal app, shut your screen off, and when your turn it back on your lock screen should be there.
Type only su <--- (Without commas)
Follow the above procedure and it will work for sure. All Credits goes to the original author