I found this easy little mod while poking around on the internet today. What it does is makes absolutely certain that launcherpro stays in memory (apparently there can be a problem with this even if you have the checkbox checked). Now by no means was LauncherPro slow to begin with, it is already the fastest launcher, IMO, available. But since performing this mod ive not had a single instance with any lag what so ever with launcherpro, whether is be coming out of apps or waking from a screen off/phone sleep mode.
No this wont fix the FC on reboot issue...
So open Terminal Emulator on your phone.
Type (or copy and paste) the following, hitting ENTER between each line:
su
echo ro.HOME_APP_ADJ=1 > /data/local.prop
reboot
If for whatever reason you experience some adverse affects with this you can simple go into any File Manager with root access and delete the /data/local.prop file you created and reboot your phone. I personally have not experience any negative effects as of yet (several hours using this mod).
EDIT: This mod should work with whatever launcher you have on your phone. I've only tested it with LauncherPro however. But the idea is that it locks the launcher in memory, any launcher.
EDIT: also, if you would like to make the file manually to store on your sd card so you can copy/paste it after a factory reset you just need to use a file manager to create a file and name it local.prop
Then you will need to open it with a text editor and type the following and save: ro.HOME_APP_ADJ=1
From there it just gets pasted to the /data partition to make it active (not the data folder on the SD card btw).
EDIT (05/26/2011): Ok uploaded a working .zip that can be flashed from clockwork recovery.
EDIT (05/26/2011): Also added a flashable .zip that will remove the mod from your phone for whatever reason. Just flash from clockwork recovery.
Will try this tonight!
HTC Liberty
CM7 nighlty 39
Smartass Kernal 6-7
Will this get rid of that sluggishness when unlocking phone? I want smooth like fr008
HTC Liberty
CM7 nightly 39
Smartass Kernal 6-7
andrew.cambridge said:
Will this get rid of that sluggishness when unlocking phone? I want smooth like fr008
HTC Liberty
CM7 nightly 39
Smartass Kernal 6-7
Click to expand...
Click to collapse
Im getting no lag what so ever when waking/unlocking the phone. LauncherPro no longer has to do any redraws so unlocking is super smooth.
EDIT: On a side note, this should work with any launcher. What it does is keep the current launcher in memory at all times, so it should work regardless of launcher. So anyone using another launcher such as adw or Go who wants to test this and share their results it would be appreciated.
Just confirmed no lag when swiping to unlock screen
HTC Liberty
CM7 nightly 39
Smartass Kernal 6-7
Wow! This actually worked. It wasn't faster as much as smoother (which I thought impossible with Launcher Pro lol!) Well thanks!
HTC Aria
CM7 <<Just so you know it works with CM7
LauncherPro v0.8.5 = WIN. So smooth its rediculous!
Is this something that needs to be done each time I flash a new nightly?
lsusparky621 said:
Is this something that needs to be done each time I flash a new nightly?
Click to expand...
Click to collapse
no. The only time you'll need to re-do it is if you do a factory reset. It persists through normal cache/dalvik wipe/rom flash.
On a side note, you after you create the local.prop file using the method in the first post you can make a copy of it to save to your sd card so that you can just paste it to /data for those times where you want to do a factory reset.
EDIT: updated first posts with directions to create the file manually.
WOW, my Aria is flying....
And, I can confirm that this patch works just fine with the stock ADW launcher on CM7.
I hate to think of all the hours I spent playing with different governors trying to eliminate "lag". This little patch blows them all away, even with the phone set back to stock, non-OC'd speeds.
Thanks...
Seems to have helped GO Launcher Ex in the smoothness department, nice find.
will this work on other phones?
boxcar8028 said:
will this work on other phones?
Click to expand...
Click to collapse
Yes. This hack was originally intended for the old MotoDroid because of its slow redraw issues. Should work with any android phone.
Sent from my cm7 Aria.
CallMeAria said:
Yes. This hack was originally intended for the old MotoDroid because of its slow redraw issues. Should work with any android phone.
Sent from my cm7 Aria.
Click to expand...
Click to collapse
Thanks, Im going to flash this onto my aria and my nook color.
boxcar8028 said:
Thanks, Im going to flash this onto my aria and my nook color.
Click to expand...
Click to collapse
Let me know how it works out on your nook.
Sent from my cm7 Aria.
CallMeAria said:
Let me know how it works out on your nook.
Sent from my cm7 Aria.
Click to expand...
Click to collapse
All went well on my aria. the zip flash with no problem. love this little hack. ADW is so smooth on my aria now, loving it. thxs. cm7 n77
But on my nook it was not so good. cm7 n69 The flash was aborted by CWR the error message was "Amend scripting is go longer supported. please switch to edify scripting" Im no dev but I thinks this error is because CWR on the nook is 3.0.x and does not support the older script. so I try to do this through terminal of the nook with no luck, Im a noobe with the terminal and Im sure i just enter the code wrong.
I was typing:
echo ENTER
ro.HOME_APP_ADJ=1 ENTER and then I'll get "denied"
------------------edited--------
I see it now, I see all 3 lines of code. last night all I saw was the main line "echo ro.HOME_APP_ADJ=1 > /data/local.prop" and totally miss the other 2 lines "su" and "reboot"
I think the right way is:
su ENTER
echo ro.HOME_APP_ADJ=1 > /data/local.prop ENTER
reboot ENTER
---------------------------
I'll try again tonight. Thanks, love this hack
boxcar8028 said:
All went well on my aria. the zip flash with no problem. love this little hack. ADW is so smooth on my aria now, loving it. thxs. cm7 n77
But on my nook it was not so good. cm7 n69 The flash was aborted by CWR the error message was "Amend scripting is go longer supported. please switch to edify scripting" Im no dev but I thinks this error is because CWR on the nook is 3.0.x and does not support the older script. so I try to do this through terminal of the nook with no luck, Im a noobe with the terminal and Im sure i just enter the code wrong.
I was typing:
echo ENTER
ro.HOME_APP_ADJ=1 ENTER and then I'll get "denied"
------------------edited--------
I see it now, I see all 3 lines of code. last night all I saw was the main line "echo ro.HOME_APP_ADJ=1 > /data/local.prop" and totally miss the other 2 lines "su" and "reboot"
I think the right way is:
su ENTER
echo ro.HOME_APP_ADJ=1 > /data/local.prop ENTER
reboot ENTER
---------------------------
I'll try again tonight. Thanks, love this hack
Click to expand...
Click to collapse
Yea that zip I posted is not compatible with cwm 3.x +.
And your very last edit is correct.
"echo ro.HOME_APP_ADJ=1 > /data/local.prop" is all one line.
Sent from my cm7 Aria.
CallMeAria said:
Yea that zip I posted is not compatible with cwm 3.x +.
And your very last edit is correct.
"echo ro.HOME_APP_ADJ=1 > /data/local.prop" is all one line.
Sent from my cm7 Aria.
Click to expand...
Click to collapse
Got this to work through the terminal with my nook and its working nicely. The nook screen respond was never that bad but this little mod just makes it also smoother. I just don't understand why the launcher makers don't add this as a default setting. Thanks, this is awesome.
I was just wondering if anyone knows if this little mod is similar to cyanogenmod's performance setting of "lock home in memory". is it basically the same thing? and is it safe to use both.
it is safe to use both.
this just insures that that setting wont be overridden.
Related
I did this exact procedure and everything is working fine with my phone. No issues at all. I AM NOT RESPONSIBLE FOR ANYTHING YOU CHOOSE TO DO WITH YOUR PHONE.
**Make sure adb and java are both installed on your system
1. Download and install xUltimate
2. Run Main.exe
3. Choose option 1 and wait
4. Choose option 2 and wait
5. Choose option 6 and wait
6. Choose option 3 and wait
7. Choose option 4 and wait
8. Once everything has been deodexed and the script did not come up all red with a major error then you are good. You will know the error if you see it. If you get that major error then DO NOT PROCEED.
9. Copy done_app and done_frame to your internal sdcard.
10.
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
You might get an error with the 2nd mount, and if you do just ignore and type reboot. You're device will take longer to boot the first time but after that it will be quicker. And all around will be quicker.
There is no point in doing this to your phone right now. There is no recovery or sbf for this phone at the moment.
I would advise people NOT to do this to your phone. There is no real benefit to this on a stock rom while on the phone. Your phone might actually be slower and use more memory.
You should probably post a link back to the original thread instructions as well.
Had no errors except when trying to cp so I rebooted and now stuck @ motorola logo
Rebooted into recovery and tried resetting phone with no luck. Since there is no SBF file available yet I'm assuming the phones toast until it's available? I've had the phone for past 14 days so I doubt exchanging it is going to be easy
hax0red said:
Rebooted into recovery and tried resetting phone with no luck. Since there is no SBF file available yet I'm assuming the phones toast until it's available? I've had the phone for past 14 days so I doubt exchanging it is going to be easy
Click to expand...
Click to collapse
This is exactly why I said NOT to do this.
nitroglycerine33 said:
This is exactly why I said NOT to do this.
Click to expand...
Click to collapse
Ahh but you had not posted yet when I had the page loaded reading the instructions
This phone just isn't for me, it's too locked down and slow to develop so I'm moving to a Droid Charge. Will send this back for reflash and put on ebay when it returns.
Maybe OP should also put in that there is no SBF available just to add the extra layer then the "Im not responsible bla, bla, bla,....." I love seeing any bit of development for this phone =) but we should make it bold that there is no way to fix any mistakes that occur right now. =)
hax0red said:
Rebooted into recovery and tried resetting phone with no luck. Since there is no SBF file available yet I'm assuming the phones toast until it's available? I've had the phone for past 14 days so I doubt exchanging it is going to be easy
Click to expand...
Click to collapse
If you made a backup you can go into recovery and push the backed up apks and odex back.
Sent from my DROID X2 using XDA Premium App
Interesting.. what app are you using to actually do a decent back up?
I didn't think there was one out that worked.
Thanks.
rook75 said:
Interesting.. what app are you using to actually do a decent back up?
I didn't think there was one out that worked.
Thanks.
Click to expand...
Click to collapse
Indeed, I'm curious also.
Option 6 backups your odex apks and framework
Sent from my DROID X2 using XDA Premium App
I did exactly like you said and only had trouble with the cp command so I rebooted from there rather then doing the remove (rm). I'll try pushing the files back. Can you explain further the command to push them back?
hax0red said:
I did exactly like you said and only had trouble with the cp command so I rebooted from there rather then doing the remove (rm). I'll try pushing the files back. Can you explain further the command to push them back?
Click to expand...
Click to collapse
I am mobile right now and will be home in about 30 and I will add information to the first post when I get home
Sent from my DROID X2 using XDA Premium App
nitroglycerine33 said:
There is no point in doing this to your phone right now. There is no recovery or sbf for this phone at the moment.
I would advise people NOT to do this to your phone. There is no real benefit to this on a stock rom while on the phone. Your phone might actually be slower and use more memory.
You should probably post a link back to the original thread instructions as well.
Click to expand...
Click to collapse
Yaaa I agree with this statement... until the sbf is leaked and bootloader is cracked.. I wouldn't recommend this, there's really no need unless you don't care if you don't have a phone.
Me? I need the darned thing.
Thanks for the info though.
nitroglycerine33 said:
I would advise people NOT to do this to your phone. There is no real benefit to this on a stock rom while on the phone. Your phone might actually be slower and use more memory.
Click to expand...
Click to collapse
Quadrant just pulled 2645
Sent from my DROID X2 using XDA Premium App
taylorhome11 said:
Quadrant just pulled 2645
Sent from my DROID X2 using XDA Premium App
Click to expand...
Click to collapse
I'm guessing thats an improvement for you but mine has hit 2700+ almost everytime since I got it. I've gotten a peak of either 3050 or 3150 after killing all tasks and running quadrant back to back a few times. Would be nice to have a vanilla android 2.3 running on it to really see what the hardware is worth but it seems to be a long way off for the x2.
If this backup works I'm getting a Xoom to play with instead of my phone. Never had any trouble with my HD2 like this even before nandroid was available but there was plenty of development for that phone.
Stock rooted: 2666
I just don't think the benefits outweigh the possible issues that can arise from deodexing at this time.
Taylor: I'm glad you posted this though... how did you find this out? This is awesome for the community once we (as a community) are able to develop on this phone.
Thank you.
hax0red said:
I'm guessing thats an improvement for you but mine has hit 2700+ almost everytime since I got it. I've gotten a peak of either 3050 or 3150 after killing all tasks and running quadrant back to back a few times. Would be nice to have a vanilla android 2.3 running on it to really see what the hardware is worth but it seems to be a long way off for the x2.
If this backup works I'm getting a Xoom to play with instead of my phone. Never had any trouble with my HD2 like this even before nandroid was available but there was plenty of development for that phone.
Click to expand...
Click to collapse
Yeah before this I ran it and got 2100. That was running my phone normal with adw, widgets galore, and everything else. Just opened ATK and killed all then ran again. That was one test before and then just now. Not over and over again.
hax0red said:
I did exactly like you said and only had trouble with the cp command so I rebooted from there rather then doing the remove (rm). I'll try pushing the files back. Can you explain further the command to push them back?
Click to expand...
Click to collapse
are you able to do adb devices while it is in bootloop?
rook75 said:
Stock rooted: 2666
I just don't think the benefits outweigh the possible issues that can arise from deodexing at this time.
Taylor: I'm glad you posted this though... how did you find this out? This is awesome for the community once we (as a community) are able to develop on this phone.
Thank you.
Click to expand...
Click to collapse
He probably took the instructions from here: http://forum.xda-developers.com/showthread.php?t=765270&highlight=manually+deodex
http://forum.xda-developers.com/showthread.php?t=991276&highlight=http://forum.xda-developers.com/+V6+SuperCharger!
http://forum.xda-developers.com/showthread.php?t=991276&highlight=[Script]+V6+SuperCharger!+HTK+%26amp%3B+BulletProof+Launchers!
I know quite a few roms that use this script.. That run awesome!!
I was hoping that more roms here would make use of it.
OmegaRED^ said:
http://forum.xda-developers.com/showthread.php?t=991276&highlight=http://forum.xda-developers.com/+V6+SuperCharger!
http://forum.xda-developers.com/showthread.php?t=991276&highlight=[Script]+V6+SuperCharger!+HTK+%26amp%3B+BulletProof+Launchers!
I know quite a few roms that use this script.. That run awesome!!
I was hoping that more roms here would make use of it.
Click to expand...
Click to collapse
I do use this script, and I can say that it is a success!
1.0.2 Using the MiniCM6 Nobodyatall!
One of the best roms in Big X10 xda land "Wolfbreaks" uses this.
I hope the roms here start using it... It rapes!
I must say.. this is works very well on my mini with MiniCM 2.0.5 GingerBread
Before: Active launcher and Zeam launcher is redraw everytime I finish to play NFS Shift or even after I open Application manager
After: No redraw (Active Launcher and Zeam) when finished playing Angry Birds, NFS Shift and other RAM eater games
Great ..
So I tried this script, and now my launcher is hard to kill / supercharged
but then after reboot it still says my launcher is hard to kill, but also that my prior minfrees don't match my current minfrees.
it then shows my curent minfrees as the default minfrees and the prior as what i selected. is that supposed to happen?
I mean exactly as the screenshot moedjs posted
like isn't it supposed to set current minfrees to what i selected, and not to default?
moedjs said:
I must say.. this is works very well on my mini with MiniCM 2.0.5 GingerBread
Before: Active launcher and Zeam launcher is redraw everytime I finish to play NFS Shift or even after I open Application manager
After: No redraw (Active Launcher and Zeam) when finished playing Angry Birds, NFS Shift and other RAM eater games
Great ..
Click to expand...
Click to collapse
Exactly.. makes multi tasking rock.. keeps the memory free, locks in the home app.
It works badass!
I did not understand the installation
ops , I did find a help, sorry
hey guys, does this works in SE android firmware 2.1?
Another question, in a tutorial it says :
P.S. When Installing Programs, MAKE SURE Script Manager are installed on PHONE and NOT in the MicroSD Card!
I have app2sd installed already , how can I do this? thanks
can someone who tried this give his values and his results?
sounds like a great tool
thnx in advance
I have the same problem as Carpe-Dimi above regarding new minfrees not sticking after reboot, although the Launcher is "Hard to kill".
I used option 6 in the script set up.
I followed help file advice to have Script Manager run /system/etc/init.d/99SuperCharger "at boot" and "as root" but problem persists.
Otherwise seems to work fine at keeping launcher in memory. I don't see any boost in Quadrant Score... or any other noticeable improvements to be honest.
MiniCM 7 is pretty good as it is
Any advice on settings or getting minfrees to stick?
Anyone know if it works on mini pro?
That number 1-17 is best for my phone?
alanllew said:
I have the same problem as Carpe-Dimi above regarding new minfrees not sticking after reboot, although the Launcher is "Hard to kill".
I used option 6 in the script set up.
I followed help file advice to have Script Manager run /system/etc/init.d/99SuperCharger "at boot" and "as root" but problem persists.
Otherwise seems to work fine at keeping launcher in memory. I don't see any boost in Quadrant Score... or any other noticeable improvements to be honest.
MiniCM 7 is pretty good as it is
Any advice on settings or getting minfrees to stick?
Click to expand...
Click to collapse
there are config files in the ramdisk.tar (can't remember name atm, but they are init.rc files) that have lines regarding the setting of ram optimizations.
however. these are definatley meant to do the same as the script, but the values in them don't correspond to the ones the script readsout, so I'm thinking another script runs on top of that which overrides those values again.
that's just a theory tho, since I can't edit the ramdisk file as I dunno how to set the permissions back when unpacking and repacking ramdisk.tar but I'll get back when I find out.
as for the launcher being bulletproof, that definately makes the home button respond a lot faster ^^
Carpe-Dimi said:
there are config files in the ramdisk.tar (can't remember name atm, but they are init.rc files) that have lines regarding the setting of ram optimizations.
however. these are definatley meant to do the same as the script, but the values in them don't correspond to the ones the script readsout, so I'm thinking another script runs on top of that which overrides those values again.
that's just a theory tho, since I can't edit the ramdisk file as I dunno how to set the permissions back when unpacking and repacking ramdisk.tar but I'll get back when I find out.
as for the launcher being bulletproof, that definately makes the home button respond a lot faster ^^
Click to expand...
Click to collapse
Somewhere in the original post it says that in some Custom Roms the minfrees won't stay after reboot so you HAVE TO select 'run at boot' for it to stay.
edit: From original post:
Note: For some reason, the minfree levels do not stick on some Custom ROMs. I don't know why this is. Maybe a bug in GingerBread?
........ You can check /res/user.log to see if it ran...
........ If this happens to you, use Script Manager to load /system/etc/init.d/99SuperCharger "on boot" and "run as root"
And I also have a question(just like the one 2 above)
What is the best one to choose (1-17)?
ThankYou
I tried:
'........ If this happens to you, use Script Manager to load /system/etc/init.d/99SuperCharger "on boot" and "run as root"'
and still could not get values to stick
Has anyone else tried this and had more luck?
how do you install this.. i could not understand
Carpe-Dimi said:
there are config files in the ramdisk.tar (can't remember name atm, but they are init.rc files) that have lines regarding the setting of ram optimizations.
however. these are definatley meant to do the same as the script, but the values in them don't correspond to the ones the script readsout, so I'm thinking another script runs on top of that which overrides those values again.
Click to expand...
Click to collapse
u r correct...the memory free settings are modified by some file not located in ram disk...i have examined the init.rc files and ramdisk settings are quiet different form the one that is set in the roms during runtime
now only if v knew what that file was!!!
The values are not equal with me, but I noticed a big improvement!
I am using the following values in the original 6,8,16,20,22,60 MiniCM6 Froyo!
It must have some kind of file it impossible values are equal, but it works it works!
I have done for mine and is awesome...
DareDan said:
I have done for mine and is awesome...
Click to expand...
Click to collapse
which values did you use?
please delete this post sorry
UPDATED 12/23
---------------------------
1) Added automatic fixing of devicemanager.apk sql databases to prevent OTA root (thanks for the SQL tweak suggestions, Indirect)
2) Added otaban.sh script for those who are already rooted and just want to tweak the sql databases (you will need to put your device back in USB debug mode)
3) Added getroot.sh to just dump the nook back in to rooted/adb mode
INSTRUCTIONS
(Please follow these to the letter; over 500 people have downloaded this script and very few have reported issues)
On the NOOK
Disconnect from USB
Factory restore & initial setup
Browse to this:
http://goo.gl/vTNpJ
Click on notifications center, wait for the file to finish downloading.
Press on downloaded go_launcher_ex_v2.66.apk file
Select Complete action using package installer
It should say "install blocked"
Press settings
Tick unknown sources (press ok)
Pick Development
Tick USB debugging (press ok)
Tick the other USB debugging further down
Untick Automount
Back/Back
Connect the Nook to the MAC. On the nook you should see "USB debugging connected" in notifications center
On the MAC
Download the nooktablet-mac-root-0.6.zip file from http://goo.gl/qyYDB
Open Terminal, and change in to the directory where the zip file was downloaded. Unzip and cd in to the directory created. EG:
Code:
[B]cd ~/Downloads
unzip nooktablet-mac-root-0.6.zip
cd nooktablet-mac-root-0.6[/B]
Start the rooting script:
Code:
[B]./go.sh[/B]
Sometimes adb doesn't wake up immediately. Just try go.sh again if it says it can't find your Nook and you are sure it's in debug mode and plugged in properly. Also don't connect via a USB Hub.
When the script is finished, it should say "Done. Unplug from USB now"
The Nook will reboot.
You are now rooted and the following is auto-installed for you
1) Go Launcher Ex (Rooted App Launch/Desktop)
2) Market Place (The Android "App Store")
3) Button Savior (adds tiny button on right of screen for nagivation home/back etc)
4) Home Catcher (makes 2 clicks of the Nook N bring up the new Launcher)
5) Nook Color App Menu (allows you to install sideloaded apps to the Nook home screen/Library)
6) Dolphin HD Browser (Replacement web browser)
In addition, some tweaks have been made to prevent OTA updates from working, preserving your root state.
trying this now..
thanks a lot! i spent 2 hours last night trying to get the other method working and it gave me the headache of the gods.
edit: that mediafire link is crawling for me (dl is at like .2kb/s) can anyone mirror it for others who may have similar issues?
Worked beautifully! Where can I send a donation to?
beatlesfan01 said:
Worked beautifully! Where can I send a donation to?
Click to expand...
Click to collapse
Tempting and appreciated as that is, there is no neeed. Good luck,
Sent from my BNTV250 using Tapatalk
i can confirm this works guys
yes.. someone please start a thread and aggregate donations for some roms on this bad boy.
t-r-i-c-k said:
Tempting and appreciated as that is, there is no neeed. Good luck,
Sent from my BNTV250 using Tapatalk
Click to expand...
Click to collapse
You are a good man. Thanks again for all of your help and great work. You're an invaluable asset to this community.
Sent from my BNTV250 using Tapatalk
Thanks for the tutorial. It works extremely well!
This worked great, thanks!
I had one minor glitch. I was doing this on an old MBP running Leopard and for whatever reason it wouldn't create the ~/.android directory when I ran the script.
I created the directory manually and re-ran the script and it worked perfectly! Thanks again!
jdubr said:
This worked great, thanks!
I had one minor glitch. I was doing this on an old MBP running Leopard and for whatever reason it wouldn't create the ~/.android directory when I ran the script.
I created the directory manually and re-ran the script and it worked perfectly! Thanks again!
Click to expand...
Click to collapse
Ah, I just looked at the script, I realized now I missed out the mkdir -p ~/.android in it, hence your issue. I will likely fix that and update the script/zip file when I get a minute.
I'm currently considering whether to make the script install busybox at the moment. I don't really need it myself, but I see other people might.
Part of the problem is that if I develop the script any further I ought to test it before releasing it... but I really don't want to keep re-rooting my nook. I want to actually use the damn thing!!
t-r-i-c-k said:
Part of the problem is that if I develop the script any further I ought to test it before releasing it... but I really don't want to keep re-rooting my nook. I want to actually use the damn thing!!
Click to expand...
Click to collapse
I totally get that. I had just gotten done side-loading tons of stuff and getting my launcher screens setup the way I wanted and then I saw your script and thought about it for a day before breaking down and wiping my NT and starting over.
It was worth it! Thanks again!
I'm confused... rooting on PC using other method didn't work for me and now I'm stumped on Mac as well.
This part stumped me:
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Can someone explain the steps in greater detail? I tried runing the adb fiel via terminal, it goes through the script but does nothing on installing files to the device.
Thanks.
Minor problems encountered
I followed the directions and it mostly worked. First, had the problem with the missing:
[ ! -d ~/.android ] && mkdir ~/.android
Then I wasn't sure about the step where it says to click on the golauncher icon in the notifier. I clicked on the LauncherPro.apk entry and choose the package installer. That seemed to work but I'm not sure that's what you meant.
Then found out I should have unplugged the USB cable before rebooting otherwise the launcher chooser is covered by some wrning message. (I can't remember the exact wording now.)
Installed Button Savior. Not sure what that does. I can't figure out where it's suppose to be on the screen.
And worst of all, LauncherPro keeps crashing on me, dumping me back into native Nook mode. That requires a reboot.
But despite all that, I'm happy and will now probably keep my NT.
Big thanks!!
Mike
lanceot said:
I'm confused... rooting on PC using other method didn't work for me and now I'm stumped on Mac as well.
This part stumped me:
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Can someone explain the steps in greater detail?
Click to expand...
Click to collapse
Sent from my BNTV250 using Tapatalk
lanceot said:
I'm confused... rooting on PC using other method didn't work for me and now I'm stumped on Mac as well.
This part stumped me:
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Can someone explain the steps in greater detail? I tried runing the adb fiel via terminal, it goes through the script but does nothing on installing files to the device.
Thanks.
Click to expand...
Click to collapse
Literally type
unzip nooktkablet-mac-root-0.4.zip
cd nooktablet-mac-root-0.4
mkdir -p ~/.android
./go.sh
Sent from my BNTV250 using Tapatalk
kisstek said:
Then I wasn't sure about the step where it says to click on the golauncher icon in the notifier. I clicked on the LauncherPro.apk entry and choose the package installer. That seemed to work but I'm not sure that's what you meant.
Then found out I should have unplugged the USB cable before rebooting otherwise the launcher chooser is covered by some wrning message. (I can't remember the exact wording now.)
Installed Button Savior. Not sure what that does. I can't figure out where it's suppose to be on the screen.
And worst of all, LauncherPro keeps crashing on me, dumping me back into native Nook mode. That requires a reboot.
But despite all that, I'm happy and will now probably keep my NT.
Big thanks!!
Mike
Click to expand...
Click to collapse
Launcher: that's what I meant.
Unplug: if you dont before you reboot it probably wants to media sync
Button savior: installs a tiny button on the right of the screen. Gets you back/home
LAUNCHER: certain things crash for me. Cant change dock shortcuts for example
I'm sure this will all get smoother in time. Pretty good already though.
Sent from my BNTV250 using Tapatalk
Thanks. I found the little tiny button savior icon while trying out an ssh client. It shows up well on a black background.
And that does make it real easy to get back and forth between Android and Nook. Thanks again for making this easy and the button savior recommendation.
I may have to break down and try the Amazon store now.
t-r-i-c-k said:
Connect the Nook to the MAC. On the nook you should see "USB debugging enabled" in notifications center
On the MAC
Download the nooktablet-mac-root-0.4.zip file
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Sometimes adb doesn't wake up immediately. Just try go.sh again if it says it can't find your Nook and you are sure it's in debug mode and plugged in properly.
On the NOOK
Click on Notification center again, and press on the Golancher Icon again. Install the Goauncher
Reboot
After reboot, slide to unlock and it should ask "complete action using..". Pick LauncherPRO
Open Marketplace which should be on the launcher screen
Sign in with your google credentials, attach the device to your account
Install button savior from the Marketplace.
Browse to amazon.com/app-email
Click notifications and watch for Amazon appstore apk download
Click and install.
You should now be live with Android Market & Amazon Market.
Click to expand...
Click to collapse
Hey! Noob here. Thanks so much for this! Just have a few questions...is this a permanent fix? I currently have the amazon appstore, but not android, so is this going to be set up the same way (i.e. have to click search and then go launcher to find the apps)?
When I connect to my mac, the usb debugging prompt will come up right away (like the screen for file xfer normally does)?
After unzipping, are those instructions to enter into the mac's terminal command prompt? Sorry, that's where u lost me! Is "cd" short for something? Thanks again for your help. Just want to make sure I do this right the first time. I think swype is the first thing I will install. Hating this keyboard!!!
First, I want to openly thank t-r-i-c-k for this. Even with little to no knowledge of this kind of stuff, after futzing with terminal for a while I got it to work in two tries. Finally, freedom from another lock-in service/device. But I am having a little glitch that I don't understand.
It's intermittent, but now and then I'm getting a crash on the launcher. It happens when trying to adjust settings/preferences. No big deal as it comes right back, and maybe its the app itself. Anyone else facing this?
t-r-i-c-k said:
LAUNCHER: certain things crash for me. Cant change dock shortcuts for example
I'm sure this will all get smoother in time. Pretty good already though.
Click to expand...
Click to collapse
I installed the ADW Launcher because LauncherPro wouldn't let me change the dock shortcuts. ADW is letting me modify just about everything--dock shortcuts, icons, etc., without issue.
I get an occasional crash but not as many as before.
jdubr said:
I installed the ADW Launcher because LauncherPro wouldn't let me change the dock shortcuts. ADW is letting me modify just about everything--dock shortcuts, icons, etc., without issue.
I get an occasional crash but not as many as before.
Click to expand...
Click to collapse
ADW seemed slow to me. I just switched to Launcher Ex anf thsts is working nicely. No crashes yes.
Sent from my BNTV250 using Tapatalk
I'm wanting to see what the V6 Scripts will do for CM7 but I cannot for the life of me get them to stick upon reboot.
I have them setup via Script Manger to run as root. I've gone in, did option 6 (0,4,10,12,14,15) and option 20.
Upon reboot, the settings in /sys/module/lowmemorykiller/parameters/adj are set back to the default CM7 settings
I've tried setting the properties in both local.prop and build.prop, but nothing seems to stick.
I've tried integrating the settings of the init.rc into the ROM and not doing that.
None of these options seems to make the low memory killer settings I set in V6 stick and it ALWAYS reverts back to the stock CM7 settings.
I know I can just rerun the script after it's done booting, but I never had to do this with other ROMs as it would integrate fine in /etc/init.d and run.
I see in the /etc/init.d a S99SuperCharger script with the correct permissions set. I can run it via sh and it sets the properties correctly.
It just seems that CM7 is overwriting the low memory settings somewhere and I don't know where. I don't see it occurring in any of the supplied scripts from CM7 in the /etc/init.d and I don't see it in the build.prop file.
Any ideas? I know I could just tell Script Manager to run the script on boot, but that's usually not recommended except as a last resort.
I guess the real reason I would like to get this working the way it normally does (via the init.d scripts) is just to understand what CM7 is really doing.
Thanks!
Perhaps CM7 has some sort of memory management of it's own that sets things back to the defaults on boot????????
I know, not much of an answer but it's the best I can come up with.
robocuff said:
Perhaps CM7 has some sort of memory management of it's own that sets things back to the defaults on boot????????
I know, not much of an answer but it's the best I can come up with.
Click to expand...
Click to collapse
That's what I figured is happening. I just have to determine where it's happening at.
I see that the V6 scripts are running, but something is setting it AFTER the init.d process is done.
I also checked the /data/SuperChargerRan log file and this is what I saw:
02-16-2012 09:20:53: Applied Settings from /system/etc/init.d/S99SuperCharger!
02-16-2012 09:20:54: DIDN'T Apply Settings from /data/99SuperCharger.sh!
Not sure why the second one isn't working.
Looking at the /sys/module/lowmemorykiller/parameters/adj file, it's back to the original settings that CM7 has: 0,1,2,4,7,15
iBolski said:
I'm wanting to see what the V6 Scripts will do for CM7 but I cannot for the life of me get them to stick upon reboot.
I have them setup via Script Manger to run as root. I've gone in, did option 6 (0,4,10,12,14,15) and option 20.
Upon reboot, the settings in /sys/module/lowmemorykiller/parameters/adj are set back to the default CM7 settings
I've tried setting the properties in both local.prop and build.prop, but nothing seems to stick.
I've tried integrating the settings of the init.rc into the ROM and not doing that.
None of these options seems to make the low memory killer settings I set in V6 stick and it ALWAYS reverts back to the stock CM7 settings.
I know I can just rerun the script after it's done booting, but I never had to do this with other ROMs as it would integrate fine in /etc/init.d and run.
I see in the /etc/init.d a S99SuperCharger script with the correct permissions set. I can run it via sh and it sets the properties correctly.
It just seems that CM7 is overwriting the low memory settings somewhere and I don't know where. I don't see it occurring in any of the supplied scripts from CM7 in the /etc/init.d and I don't see it in the build.prop file.
Any ideas? I know I could just tell Script Manager to run the script on boot, but that's usually not recommended except as a last resort.
I guess the real reason I would like to get this working the way it normally does (via the init.d scripts) is just to understand what CM7 is really doing.
Thanks!
Click to expand...
Click to collapse
Hehehehe... Me thinks you should search the forums a little bit. When I was testing cm7 for DZK, I tried EVERYTHING I used on previous ROMs, to include V6_SuperCharger. V6_SuperCharger DOES NOT WORK with CM7! The BIGGEST reason is the mapping for the memory slots are different with CM7, so fudging with them tends to cause massive issues and slowdowns. The reason it does not stick is most likely (speculation here) due to CM7 settings things back to it's optimized default settings.
Keep in mind that CM7 is an "optimized" AOSP based ROM... That means NO BLOATWARE! I am running with roughly 315 apps, most of which I use on a WEEKLY basis. Some, only monthly.
There are a few issues that I have noticed, root/su issues, sometimes system crashes on boot, sometime bluetooth crashes on boot, sometimes the dialer crashes... But with non-root apps, this thing SCREAMS!
Also, CM7 incorporates it's own memory management system that works better than the Moto Blur based ROMs. Just my two cents.
Ciao!
Moonshadow, thanks for the explanation. I did do a search and for some reason, your post didn't come up. Now that I search, I find it. I'll attribute it to an ID-10T or PEBKAC error.
iBolski said:
I'll attribute it to an ID-10T or PEBKAC error.
Click to expand...
Click to collapse
Are you REALLY sure about that??? It could be that Google just hiccuped during that nanosecond that your search on XDA was running... And didn't affect anyone elses searches...
You can be like Apple and blame/sue everyone else... (Just joking!)
Ciao!
Besides cm 7 does not need any script runs good as it is.
I know there are a couple posts out there on how to fix this, but this is one of the most legitimate ways to fix the multitasking issue we have all come to know and hate on Android devices running Sense. If you don't want to install a whole new ROM, such as MEANROM, you don't have to! This is a small guide to using the V6 SuperCharger script by Zeppelinrox. I know the amount of steps seems like a lot, but it's really not that many. Most of the steps will be followed by just reading what you see on the screen and accepting the recommended option!
Zeppelinrox said:
What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind
NO LAUNCHER REDRAWS, faster than ever, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
Also, because of the rearrangement, it works the same on all roms!
The problem with using minfree tweakers like AMM or AKMO is that it doesn't work the same on all roms.
Secondary apps may be in slot 3 on some roms but in slot 5 in others!
That's why you hear people comment "I tried AKMO but it didn't do anything..."
Most likely it didn't do anything because the apps weren't sitting where they were expected to be.
So fasten your seat belts and enjoy the ride!
Click to expand...
Click to collapse
So, everything you need to know or want to know can be found at Zep's original thread here. There is a lot of information, and because he is so technical, I think that sometimes his instructions can be hard to read for some, so I thought I would put together a VERY SIMPLE GUIDE to give you guys a hand. You can find the best instructions from him under Installing/Using.
http://forum.xda-developers.com/showthread.php?t=991276
On to the instructions...
How To Use Supercharger
Please only proceed if you are rooted and have busybox
Download script manager from the market: https://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=en
Download zep's latest V6 Script (V6_SuperCharger_for_Android-Update9_RC11_Test_6.sh.pdf): http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
remove the .pdf extension (should now end in .sh) and place on your phone /sdcard (you can use rom tool box or estrongs to rename the file)
At this point, I highly recommend you make a nandroid through TWRP or CWM. The script has a built-in undo feature, which works well, but I still think we all know this is best.
Open up Script manager on your phone. Make sure to check 'Browse as Root' Option
Navigate to the location wher you placed the V6 .sh script
Click the Skull/Crossbones to run as root. This should turn green. NOTE: DON'T USE THE BOOT OPTION
Hit Run
At this point, get ready for an onslaught of text. Don't be afraid and try your best to read even though much of it may not make sense!
You may be asked about your launcher. Answer the question correctly for your setup.
Any time you are asked to press Enter, go ahead and proceed. This is the last time I will tell you to hit Enter for most occasions.
Pick your scrolling speed. I recommend slow or normal the first time you do this, so you can keep up.
On the kernel panic screen, I recommend choosing the Rock(H)ard Option, so hit H and then enter
Accept the Misc and 3G tweaks by hitting Y
Feel free to keep or disable the annoying animation (the scrolling V6 at the beginning of the script)
Hit Y(es) for SuperMinFree Calculator settings. This is an automatic calculation. You can change this later when you get more confident. Many will choose the 1000HP option for our phone (based on available memory)
It will now backup your build.prop and some other system files.
ICS and newer Android services store a lot of the memory tweaks in services.jar. This script will now take you through an ICS patcher. Accept the Automatic Transmission. This will upload services.jar, and download the patched one.
It will eventually tell you that it needs to wipe your caches and restart. You will definitely want to do this. You will need to wait 4-5 minutes while it rebuilds your Dalvik Cache
Almost done! After your phone boots up and stabilizes, go back into Script Manager. Navigate to /data/99Supercharger script. Check the SU (skull/crossbones) and check the boot option.
Zepelinrox said:
- Stock ROMs - It also creates /data/99SuperCharger.sh which you can load up on boot (run as root) with Script Manager. The OOM groupings work as well since it happens on boot in local.prop or build.prop (18 entries added)
Click to expand...
Click to collapse
Reboot your phone and now your phone will run the supercharger script on startup. If you ever want to verify that your script is working, or if you want to mess with any of the extra options (including removal), run the original V6 shell script you downloaded as root, just like we did at the beginning. This will tell you if you are 100% optimized and give you a whole menu of options to play with!
I can actually open multiple apps now and go back to the first one without it having to reload. Waze is the best example. If I ever switched out and then back, it always had to reload...not anymore! Again, this all seems like a lot, but it's really pretty easy once you give it a shot!
Let me know if anything is unclear so that I can adjust this OP to help others.
Make sure to give Zep a 5 Star Rating in his OP and also give him thanks, he is the man!
Reserved just in case.
ok i need to correct you on one of your steps...DO NOT SELECT THE BOOT OPTION FOR THE SCRIPT. IT COULD CAUSE YOUR PHONE TO BOOT LOOP. only select run as root. it even tells you that on the guide that zeppelinx put in his thread.
edit: sorry for caps but i wanted to point this out before someone made this mistake
bog3nator said:
ok i need to correct you on one of your steps...DO NOT SELECT THE BOOT OPTION FOR THE SCRIPT. IT COULD CAUSE YOUR PHONE TO BOOT LOOP. only select run as root. it even tells you that on the guide that zeppelinx put in his thread.
edit: sorry for caps but i wanted to point this out before someone made this mistake
Click to expand...
Click to collapse
You have to run /data/99Supercharger as root and give it boot option or it won't be applied at boot. But you are right, if you are worried, you could just run it as root the first few times. I personally always set this one to boot as well. If you had to, you could always adb in recovery, and remove /data/Supercharger if you are having problems.
*EDIT
This is mostly a concern for ROMS/Kernels that utilize /etc/init.d but I will add this caveat to the OP
adma84 said:
You have to run /data/99Supercharger as root and give it boot option or it won't be applied at boot. But you are right, if you are worried, you could just run it as root the first few times. I personally always set this one to boot as well. If you had to, you could always adb in recovery, and remove /data/Supercharger if you are having problems.
*EDIT
This is mostly a concern for ROMS/Kernels that utilize /etc/init.d but I will add this caveat to the OP
Click to expand...
Click to collapse
if the rom uses init.d then the script will install a service to the init folder and it will auto load when then phone is restarted, no need to try and force it to run. also if it is a stock rom (with the script manager program) you can set the 99supercharger to run after boot as a task.
bog3nator said:
if the rom uses init.d then the script will install a service to the init folder and it will auto load when then phone is restarted, no need to try and force it to run. also if it is a stock rom (with the script manager program) you can set the 99supercharger to run after boot as a task.
Click to expand...
Click to collapse
What you are saying is exactly the point I made in the OP. Is this unclear? You should only ever run 99Supercharger on boot, not the original V6Supercharge Script. And yes, this is geared mostly towards stock users, who do not have init.d support and therefore need SManager to run the boot script for them.
adma84 said:
What you are saying is exactly the point I made in the OP. Is this unclear? You should only ever run 99Supercharger on boot, not the original V6Supercharge Script. And yes, this is geared mostly towards stock users, who do not have init.d support and therefore need SManager to run the boot script for them.
Click to expand...
Click to collapse
i understand what you are saying but the boot symbol next to the run ass root symbol in the script should not be checked. if you need it to run at boot the script manager program can do that for you, by setting up a scheduler when you reboot. after boot it will run the script but not during
p.s. let me re-read what you put so i am just not looking stupid lol. i think i need a nap
edit: yea if you need it to run at boot do it through the script manager program and set it up to schedule it to load the script after your phone is already booted to avoid any potential boot loops (but dont check the boot logo at the top left hang corner of the actual script itself
bog3nator said:
i understand what you are saying but the boot symbol next to the run ass root symbol in the script should not be checked. if you need it to run at boot the script manager program can do that for you, by setting up a scheduler when you reboot. after boot it will run the script but not during
p.s. let me re-read what you put so i am just not looking stupid lol. i think i need a nap
edit: yea if you need it to run at boot do it through the script manager program and set it up to schedule it to load the script after your phone is already booted to avoid any potential boot loops (but dont check the boot logo at the top left hang corner of the actual script itself
Click to expand...
Click to collapse
Can you post the steps to describe how you personally do boot scripts with SManager?
After Android starts up, it will send a boot intent to all apps registered to receive such an intent. This is where SManager is allowed to execute any scripts you have marked with the boot option. This happens much later than a traditional /etc/init.d start script, but is no less effective. Please let me know how you mark scripts as bootable and I can add that recommendation as well. Thanks.
adma84 said:
Can you post the steps to describe how you personally do boot scripts with SManager?
After Android starts up, it will send a boot intent to all apps registered to receive such an intent. This is where SManager is allowed to execute any scripts you have marked with the boot option. This happens much later than a traditional /etc/init.d start script, but is no less effective. Please let me know how you mark scripts as bootable and I can add that recommendation as well. Thanks.
Click to expand...
Click to collapse
1. open script manager
2. click menu
3. click more
4. click advanced options
5. click scheduler
6. click add new task
7. click select file
8. navigate to 99supercarger file the script created and click on it
9.you can from there click on boot (inside the file you just clicked on)
10. click save
it will boot the script after the phone is done booting, to prevent the possibility of boot looping. you can also create an event to do an engine flush however often you want (i do one at midnight everyday)
This gets executed at the same time during system boot as the method I mentioned. Both are valid. Thanks for the feedback!
Sent from my Nexus 7 using xda app-developers app
adma84 said:
This gets executed at the same time during system boot as the method I mentioned. Both are valid. Thanks for the feedback!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i thought you were saying click the boot thing during install ....i am sorry haha i got really tired all of a sudden and stuff wass getting jumbled together...
v6 works awesome though i have been using it for about 1 year now on this phone and my old evo
Also, for anyone that gives this a shot, please post back with your results!
Not to be "that guy" buuuut the effects of v6 at least from my experience with this phone (again fresh frombcustoms preorder release) the day i got it i was rooted and installed v6 because ive used it on all my prior evos since i found it probably right around when zep released lol...anyways on this phone its a strictly placebo effect and actually created more lag and launcher reloads...i was running the 1000hp option and tried the i believe 750hp whatever the one down from 1000 is anyways both of them gave me same results and once i removed the script all was good in the hood as they say lol...but if its working for yall then maybe zep fixed some ish for this problem and i didnt know about it...well this epic runon sentence is finished sorry for the length and useless points
Sent from the depths of hell
yea i also used it on my og evo and i just put it on last night again on this one, tried the 750 option and 1000 option. today at school my memory got so low it locked my phone, that never happened with mean rom and the tweaks he puts in. undoing the supercharge now.
Sorry everyone.
Sent from my Nexus 7 using xda app-developers app
adma84 said:
Sorry everyone.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
no thanks man for helping out, i just think this phone doesnt do well with it, and that may be because of how HTC changed the multitasking settings themselves. it may conflict with v6
Theres something up with it because its def just this phone because nothing solves it at all
Sent from the depths of hell
wileout said:
Theres something up with it because its def just this phone because nothing solves it at all
Sent from the depths of hell
Click to expand...
Click to collapse
I wonder if it's hard coded into sense somewhere
Sent from my EVO using xda app-developers app
bog3nator said:
I wonder if it's hard coded into sense somewhere
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Im thinking its sonething stupid like a character in the code is supposed to be one way and its mirrored the other way lol
Sent from the depths of hell
It's definitely helps with multitasking. I can keep apps open in the background much easier. Problem is that it chokes out the available ram for running apps, so it can make it feel sluggish. I think it's overtweaking the mem settings.