Related
Enable Custom Boot Sounds
First make sure you are running a cyanogenmod based rom, i have only tested on CM7, but i believe the capability exists in CM6 as well.
Flash from recovery:
http://www.mediafire.com/?4cr7aa4lg51y8pc
BUSYBOX REQUIRED - if you dont have a proper busybox install (like cm7) this can sometimes fail. if you experience issues, mount system rw before running the script.
Zip contains the default "DROID" sound, to replace with your own see below.
Instructions:
1) Flash from recovery over current rom
2) reboot phone
Once you have flashed this you will also have some new commands in terminal or adb:
enablebootsound - enables boot sound if enable from recovery was unsuccesful
bootsoundtoggle - turns bootsound on or off
newbootsound - copies /sdcard/android_audio.mp3 as new boot sound
newbootanim - copies /sdcard/bootanimation.zip as new bootanimation.
Feel free to post your custom sounds in this thread. i'll try and keep the first post updated.
Once again - to set custom sound or animation place them on root of sdcard named appropriately i.e. 'bootanimation.zip' and 'android_audio.mp3'
Enjoy.
bootsound enable script by mrdaviso modified by me for compatibility and to eliminate double runs, from a tutorial posted by spiicytuna
Very cool idea and a very nice implementation. I had a media force close as soon as the phone finished turning on, but then again I was using a 5mb mp3. Also as soon as I did "newbootsound", the selected song started playing. Other then that everything works exactly as you described . Ill post some logs up tomorrow. Thanks!
Nice work. I always thought this had to be done by fixing the links in /system/bin/bootanimation
Sent from my HTC Vision using XDA Premium App
I'm always changing my animations and will now be changing bootsounds....so I hope you don't mind, I made a small change to /system/bin/bootsound
Its now
#!/system/bin/sh
bprop=/system/build.prop
play=$(cat $bprop | egrep -c -i -o ro.config.play.bootsound=1)
if [ "$play" = "1" ]; then
stagefright -a -o /system/media/*.ogg
stagefright -a -o /system/media/*.mp3
fi
exit 0
Sent from my HTC Vision using XDA Premium App
Doesn't work on PyroMod.
----------------------------------------
Never mind. A wipe and a few reflashes later and I got it working right.
In CM7 RC2, remember to type "su" before typing enablebootsound...
It works! great add-on to cm7, u tha man!
EdWRX said:
In CM7 RC2, remember to type "su" before typing enablebootsound...
It works! great add-on to cm7, u tha man!
Click to expand...
Click to collapse
In Terminal Emulator period you need to type su (to gain root access) before typing any of the commands.
I'm running CM 6.1.1 and it worked great..only thing is the boot audio cuts out about 5 seconds before my animation ends (and it's not the audio clip..it's 30seconds long)..is there any way to increase the length of this?
In case you wanna add to the OP, this is from enablebootsound.
#I just made this into a script this was from a post on XDA by spiicytuna
#http://forum.xda-developers.com/showpost.php?p=8274824&postcount=2
#Please give the credit to him not me.
Sent from my HTC Vision using XDA Premium App
only thing is the boot audio cuts out about 5 seconds before my animation ends (and it's not the audio clip..it's 30seconds long)..is there any way to increase the length of this?[/QUOTE]
I have the same problem. Any suggestions? I might have to wipe, but I don't want to unless I have to xD
Sent from my HTC Vision using XDA Premium App
this sounds so awesome, but im a super noob when it comes to other things that isnt just flashing something and bam its there.......
Simer03 said:
this sounds so awesome, but im a super noob when it comes to other things that isnt just flashing something and bam its there.......
Click to expand...
Click to collapse
EDIT no terminal required now
Already have the perfect start sound. Android Hell wave from Portal. Other good ones would be "Hello friend" and "Amusing Fact" from Portal.
when i run enablebootsound after su and reboot...it loop....
but i get into recovery and press fix permissions ..it sound DRIOD...
well done!
I was able to get this working on my evo shift cm7 nightly rom, great work!
update:
http://www.mediafire.com/download.php?dxjcc9cyhzyalz3
if you have already flashed and used the previous version, this one is of no use to you.
The only modification is after flashing when you are rebooting you will see your splash screen for a few seconds, then your device will reboot and continue like normal. ONE REBOOT is normal. after this reboot the boot sound will automatically play. so for you self proclaimed super noobs, all you do is flash and reboot. once again after flashing your device will boot to splash screen for a few seconds then reboot and greet you with your animation and the default android sound.
see OP for changing the sound.
If you can, why not build an app that lets you change your sound? Something similar to Root Tools by Rummler. You can swap boot-animations easily with that app, granted you can only change from the ones he has. There are 24 of them.
sounds like a good idea. I would use an App to do this. Shouldn't be too hard, as right now I use gscripts to do most of my changing/testing.
This will never be released as an app by me. Script only. a few commands in terminal should be easy enough, and it isn't a customization suite, it's just to enable the boot sound, the ability to change was an after thought and is a simple few lines.
mejorguille said:
Very cool idea and a very nice implementation. I had a media force close as soon as the phone finished turning on, but then again I was using a 5mb mp3. Also as soon as I did "newbootsound", the selected song started playing. Other then that everything works exactly as you described . Ill post some logs up tomorrow. Thanks!
Click to expand...
Click to collapse
I know how to get the clip to play all the way through. I got it on mine. Not sure if there are any side effects, but perhaps you would like to test it out? If so, please send me your clip.
@ amazinglarry311
Do you think this will cause any side effects? I dont know much, but I like to tinker and learn
If you remove the line that tells it to stop playing the boot audio
this
Code:
on property:dev.bootcomplete=1
stop bootsound
from
/etc/init.local.rc
so it now looks like this
Code:
# CyanogenMod Extras
# Compcache - handle at boot
service compcache /system/bin/handle_compcache
user root
group root
oneshot
###Bootsound - Safe to Delete: Start ###
service bootsound /system/bin/bootsound
user media
group audio
disabled
oneshot
on property:init.svc.bootanim=running # to correct timin
start bootsound
### Bootsound - Safe to Delete: End ###
As long as the audio clip doesn't exceed boot time, than you should be good.
If the clip is longer, it will continue to play, until its finished...which no one probably wants.
If anyone wants to give it a shot, just backup your file, and edit it... or use the attached file. Its not zipped, just remove the .zip from the filename.
Thanks.
Introduction
Here's a repackage and repost of my modified Random Boot Animation script. This was originally conceived by Nighthound many moons ago and was long abandoned. I picked it up and modified it for my Kang-o-rama ROM and the Optimus 2x.
And here it is for you Galaxy Nexus pleasure!
What it Does
There are various apps out there that can achieve the same result but this is a simple script that uses a random number generator to swap in a random boot animation each time you boot. The script runs one just before the animation and never again until you boot the next time.
You can have any number of animations that will randomise and you can also set a flag to have just one run without needing to delete the others.
How it Works
The script executes on startup, generates a random number, assigns this number to a boot animation stored in /data/local/bootanimations/, copies that animation to /data/local/bootanimation.zip and let's Android take over from there. Android will automatically prefer /data/local/bootanimation.zip to the one stored by your ROM in /system/media/.
You just put any valid boot animation in /data/local/bootanimations/ - calling it what you wish - and the script will do the rest. You should not try and call all of your boot animations "bootanimation.zip" - you need to give them a unique name.
Installation
Upon installing the script will automatically back up any custom animation you have in /data/local/ to /data/local/bootanimations/CustomAnimBackup.zip and this animation will be among those randomly selected.
Download one of the files below
Flash from recovery
Reboot and enjoy
Hit 'Thanks' below
System Requirements
This script will run on any custom Galaxy Nexus ROM with init.d support (which is most).
Notice
Some boot animations are distributed within another zip archive. You need to extract the bootanimation.zip file from that archive and rename it before you put it in the bootanimations directory.
Downloads
Update 08 July 2014
The script, in install.zip format has been attached to this post.
Single Animation Flag
If you want to view a single animation only you can do so without moving or changing any of the other files.
Simply Create a file called "bootanimation.use" in /data/local/bootanimations/. In this file place a single line with the filename of the boot animation you want to use. For example:
Code:
CustomAnimBackup.zip
When you want to revert to random animations again delete "bootanimation.use" from the directory.
Oh this is very cool! Will test it out shortly. Thanks.
I rather enjoy bootanimations. Thank you for this lovely script!
This script will run on any custom Galaxy Nexus ROM with init.d support (which is most).
Click to expand...
Click to collapse
Does this mean it doesn't work on rooted stock?
zombieflanders said:
Does this mean it doesn't work on rooted stock?
Click to expand...
Click to collapse
Correct. You need a custom kernel at minimum and a /system/etc/init.d/ directory.
djmcnz said:
Correct. You need a custom kernel at minimum and a /system/etc/init.d/ directory.
Click to expand...
Click to collapse
I'm on bigxie build 8 and Franco kernel - and this didn't work for me
I flashed the zip with animations and nothing seem to have happened
dhruvraj said:
I'm on bigxie build 8 and Franco kernel - and this didn't work for me
I flashed the zip with animations and nothing seem to have happened
Click to expand...
Click to collapse
That's odd. It does log what's happening at boot, know how to get a logcat?
djmcnz said:
That's odd. It does log what's happening at boot, know how to get a logcat?
Click to expand...
Click to collapse
Don't but would love to know. Some app? Script? Or cmd on terminal emulator?
Sent from my Galaxy Nexus using XDA App
dhruvraj said:
Don't but would love to know. Some app? Script? Or cmd on terminal emulator?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Via adb, it's quite easy:
adb logcat > log.txt
Will save the log to log.txt
Turn phone off, plug in, type command, start phone, wait till boot completes, ctrl+c to stop logging. Attach file here.
Remember to boot a few time first, just to make sure you're not getting random animations.
Thanks a lot mate!
Its attached
Also attached, are the screenshots (available at http://forum.xda-developers.com/showthread.php?t=1446531) that I am having a seperate problem with, not sure if you would know but just checking with you.
My screen is all screwed up when it boots, if I stop the launcher and restart it seems to be okay though. Any pointers to what it could be because (if it is glaringly visible in the log file) ?
dhruvraj said:
Thanks a lot mate!
Its attached
Also attached, are the screenshots (available at http://forum.xda-developers.com/showthread.php?t=1446531) that I am having a seperate problem with, not sure if you would know but just checking with you.
My screen is all screwed up when it boots, if I stop the launcher and restart it seems to be okay though. Any pointers to what it could be because (if it is glaringly visible in the log file) ?
Click to expand...
Click to collapse
Okay, it doesn't look like your ROM executes init.d scripts... which is required.
Is it this ROM: http://forum.xda-developers.com/showthread.php?t=1372376
If so that one's a little too close to stock... if you want to run a stock ROM that has init.d support I suggest a free MCR (MoDaCo) ROM.
Can't help with the crazy display sorry...
Very interested in this, but have a scrub question... so all I do is download then flash through cwm and I 'm all set?
Sent from my LTE GNex
Lizard King said:
Very interested in this, but have a scrub question... so all I do is download then flash through cwm and I 'm all set?
Sent from my LTE GNex
Click to expand...
Click to collapse
Correct as long as you're running a custom rom with init.d support.
If not, it will do no damage, it just won't work.
Just flashed... works flawlessly... awesome mod
Sent from my LTE GNex
I'm ok AOKP Milestone2 with franco kernal #12. works great! genius!
gaetawoo said:
I'm ok AOKP Milestone2 with franco kernal #12. works great! genius!
Click to expand...
Click to collapse
I'm on the same ROM and kernal and having difficulty with the script. Did you just copy the animation file to just /data/local/bootanimations or to /system/media as well?
- I ran the script
- Copied the few bootanimations I downloaded to /data/local/bootanimations
- Rebooted
- Black screen
raniosman said:
I'm on the same ROM and kernal and having difficulty with the script. Did you just copy the animation file to just /data/local/bootanimations or to /system/media as well?
- I ran the script
- Copied the few bootanimations I downloaded to /data/local/bootanimations
- Rebooted
- Black screen
Click to expand...
Click to collapse
When you say you "ran" the script, do you mean you flashed it in CWM? Hope so.
Other than that your steps are correct... nothing needs to go in /system/
The script logs to logcat... if you can get a boot logcat I can tell you if it's initiating.
djmcnz said:
When you say you "ran" the script, do you mean you flashed it in CWM? Hope so.
Other than that your steps are correct... nothing needs to go in /system/
The script logs to logcat... if you can get a boot logcat I can tell you if it's initiating.
Click to expand...
Click to collapse
Yea, I meant ran it on CWM. Phone is rooted and has the CWM recovery. Using AOKP Milestone2 custom rom with the franco kernal #12
But all I get is a blank black screen after the 'Google' word until the phone reaches the lock screen. None of the bootanimations are loading.
Trying it with the bootanimations:
ITCrowd, DoctorWho, and TheRoosevelt-Sharp-ICS
raniosman said:
Yea, I meant ran it on CWM. Phone is rooted and has the CWM recovery. Using AOKP Milestone2 custom rom with the franco kernal #12
But all I get is a blank black screen after the 'Google' word until the phone reaches the lock screen. None of the bootanimations are loading.
Trying it with the bootanimations:
ITCrowd, DoctorWho, and TheRoosevelt-Sharp-ICS
Click to expand...
Click to collapse
Okay, I'll need a log really to see what's happening... perhaps it's permissions on the /data/local/bootanimations directory.
if you can do this:
Code:
adb logcat > boot.log
From phone off all the way to home screen and attach it here I can look at it for you.
raniosman said:
Yea, I meant ran it on CWM. Phone is rooted and has the CWM recovery. Using AOKP Milestone2 custom rom with the franco kernal #12
But all I get is a blank black screen after the 'Google' word until the phone reaches the lock screen. None of the bootanimations are loading.
Trying it with the bootanimations:
ITCrowd, DoctorWho, and TheRoosevelt-Sharp-ICS
Click to expand...
Click to collapse
See my comment above as well but I have a question... did you create the /data/local/bootanimation directory yourself?
If so, delete it (copy the contents elsewhere temporarily) and reboot the phone. If the directory is re-created the script is firing. Then copy the files back in a reboot... that will fix any problems with the permissions that exist.
If the dir is not re-created automatically I'll need the log.
Hi all,
I own no credits to this mod/script, it's all put together by zeppelinrox, Thanks go out to him for this! Orginal thread can be found here.
http://forum.xda-developers.com/showthread.php?t=991276
This is the first post of this kind I have ever made, so it might not be that good, or any help at all, but for those who want to try this script for the first time, I shall try my very best to explain how to do so.
I had been running ROMS for my Nexus with the V6 SuperCharger built in, and decided to see if it'll run well on our humble little Tabs. And indeed it does, it could be a placebo of course, but I seem to notice a good difference.
First, there are a few requirements in order to use this script :-
You NEED to be Rooted, in order to do this (if you aren't already) you could try the excellent Quick and Easy Root Script by the genius Crossix http://forum.xda-developers.com/showthread.php?t=1472521
Download and Install Script Manager from the Market
https://market.android.com/details?id=os.tools.scriptmanager
You also need to have BusyBox installed for the script to be run, I suggest installing the Script attached to the above V6 SuperCharger thread (even if you already have BusyBox installed to avoid errors). Simply scroll to the bottom of the thread and download the file named "busybox_v1.19.3_installer_script_wraithdu.zip"
To install this version of BusyBox navigate to where you saved the ZIP file, if on the Tab it should have downloaded to "/mnt/sdcard/Download", extract it using your file manager, I use ES File Explorer. Then open Script Manager and navigate to the extracted folder, find the script that should be called "busybox_v1.19.3_installer_wraithdu.sh", open this and select the "su" icon, make sure it is selected as a script and not executable.
To Run the Script:-
Scroll to the bottom of the SuperCharger thread and Download the file named " V6_SuperCharger_for_Android-update8.sh.txt" Navigate to where this file is downloaded, if on the Tab it should have downloaded to "/mnt/sdcard/Download", rename it using your favourite file manager, usually via a long-press to "V6_SuperCharger_for_Android-update8.sh"
Then open Script Manager and navigate to the script, open it using script manager, again taking care to run it as "su" as a script not an executable. The script should Run and prompt you for an option numbered 1-17. I chose Option 2, which is Aggressive Level 2 and noticed a good improvement, you can of course opt for the balanced options of 3 or 4. To input a number touch the screen and the on screen keyboard should pop up, hit a number and enter it.
The Script Should run and then prompt you for another option, don't choose another one just yet.
If you are running the excellent build.prop by Crossix, Icewyng et al, it is recommended to disable the device keeping Launcher in memory for the script to run properly. To do this, open Root Explorer, navigate to the build.prop, in "/system", and open it in the text editor. Scroll to the part of the prop file that begins "store launcher in memory" and change the below string to "ro.HOME_APP_ADJ=0"
In order for this to be a persistent change to how RAM is managed on our Tabs, a script has to be set up to be run at boot. To do this, in Script Manager, navigate to "/data" and open the script named "99SuperCharger.sh", and check the boxes of "su" along with "boot" to run it at boot.
After you have followed these steps reboot your Tab and you *should* see a snappier Tab
Please be aware that this is the very first HOW TO I have ever written, and it will probably be inaccurate and crap. So, please, feel free to correct my errors and I will try to help running the script.
Yours,
Toyface
Awesome scripts. Im going to give it a try here in a bit and see if there is a difference in performance.
Could someone confirm if this really works?
I just did this and have notices an improvement but do follow instructions carefully
Sent from my A500 using xda premium
I can't download the update 8 sh.txt file it just opens it in my browser
I used taptalk to download it it worked great and is still working its magic
Sent from my A500 using xda premium
Super huge improvement. Thank you!
rando152 said:
I can't download the update 8 sh.txt file it just opens it in my browser
Click to expand...
Click to collapse
Which browser are you using? If chrome on the PC, try a right click and save as a txt file and rename it as a file ending .sh
Sent from my A500
Thanks for all the cool info. Using info I found in sin threads Skype seems to stay running for hours now instead of just 15 Minutes.
Sent from my modified A100 using Tapatalk and SlideIT keyboard.
so far so good.
Just had time to get this installed. So far it seems to be a bit snappier. Wish i had thought to benchmark first. Grrrr....
I think this should be in the dev section, I might ask to have it promoted... Good Work!
Frankly the whole you cant modify his script deal is a HUGE turn off. I understand him wanting credit for his hard work, BUT wth. I'll stick to safer things.
EDIT: Forget what I said I completely miss understood what he says in his post. He says
"Personal Use: You may tweak the V6 installation script (leaving credits intact) to your own personal liking as long as it is NOT redistributed in any way."
His autostart script script looks very handy. I was considering trying Gscript already here is a new reason hehe.
NoSudo said:
Frankly the whole you cant modify his script deal is a HUGE turn off. I understand him wanting credit for his hard work, BUT wth. I'll stick to safer things.
EDIT: Forget what I said I completely miss understood what he says in his post. He says
"Personal Use: You may tweak the V6 installation script (leaving credits intact) to your own personal liking as long as it is NOT redistributed in any way."
His autostart script script looks very handy. I was considering trying Gscript already here is a new reason hehe.
Click to expand...
Click to collapse
I can see why he doesn't want redistributables floating around, even with the open source (something I feel very strongly about) nature of the forum.
All I wanted to do was spread the word, maybe help along the way, if I've done this then I'm happy
Sent from my Nexus S using xda premium
NoSudo said:
His autostart script script looks very handy. I was considering trying Gscript already here is a new reason hehe.
Click to expand...
Click to collapse
You can also auto start scripts without having to use script manager or any other scripting program by calling them from within install-recovery.sh (see my sdswap mod).
For example if you had a script /data/app/supercharger.sh
in install_recovery.sh you'd add a line sh /data/app/supercharger.sh
crossix said:
You can also auto start scripts without having to use script manager or any other scripting program by calling them from within install-recovery.sh (see my sdswap mod).
For example if you had a script /data/app/supercharger.sh
in install_recovery.sh you'd add a line sh /data/app/supercharger.sh
Click to expand...
Click to collapse
Cool. I have re-written another version of my hulu script in .sh and set it up to be able to run in a normal verbose mode, or to accept "silent" as a command line argument to redirect output to a lhulu.log file instead to better allow for the option of running at startup like a cron entry or what ever our allowed methods are on android.(like the one you just referenced, thanks) I'm planning on playing with it a little to figure out the best and easiest method. Then repost the updated version that can be a semi permanent fix.
NoSudo said:
Cool. I have re-written another version of my hulu script in .sh and set it up to be able to run in a normal verbose mode, or to accept "silent" as a command line argument to redirect output to a lhulu.log file instead to better allow for the option of running at startup like a cron entry or what ever our allowed methods are on android.(like the one you just referenced, thanks) I'm planning on playing with it a little to figure out the best and easiest method. Then repost the updated version that can be a semi permanent fix.
Click to expand...
Click to collapse
install-recovery.sh won't work for the hulu lib, sometime after that script is loaded all the apks libs get extracted for whatever reason. Unless you put a wait in there for the prop sys.boot_complete or something like that. Might also need to use busybox run-parts for a seperate init.d script, not sure if the wait would actually stop the rest of the boot process.
It should be fine, install_recovery is called really late in the boot process you're right about putting the waits in, if you look at my swapscript you'll see the amount of time I used to get it to work (and it does not pause the other processes).
Sent from my MB860 using XDA App
crossix said:
It should be fine, install_recovery is called really late in the boot process you're right about putting the waits in, if you look at my swapscript you'll see the amount of time I used to get it to work (and it does not pause the other processes).
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
It's not as late as I previously thought myself. dmesg won't work at that point and getting a logcat from there you'll see it's the start of the system log just when vold starts up. Which is why you need a few sleeps in your script. Using it was my second attempt at 2nd-init, which wasn't possible until after my first bootloop, the boot animation starts later but also before the libs are replaced.
For hulu I've just been running a gscript after a reboot because of this, at least until I find a different solution.
Anyway install-recovery is the perfect spot for any kind of kernel tweaks and also SuperCharger.
@toyface sorry for being off topic
Sorry a little confused with the last part how do I navigate to /data in script manager?
Edit.. never mind. ma bad noob moment, couldn't for the life of me figure out how to get out of the mnt part of the directory.
Sent from my A100 using Tapatalk
Guys I looked around and didnt find anything regarding our phones and this script so I decided to post it here. If I missed it and there is a thread about it, forgive me.
Recently the developer updated his script so it can run on ICS too. Is anyone running the script?? Would it be useful for our phones?
http://forum.xda-developers.com/showthread.php?p=16635544#post16635544
atsavlis said:
Recently the developer updated his script so it can run on ICS too. Is anyone running the script?? Would it be useful for our phones?
Click to expand...
Click to collapse
Nope.
and
Probably not much use at all. Zeppelinrox originally created it for phones with low amounts of memory (originated on the milestone which has 256mb and would constantly kill the launcher etc), I'm not sure if anythings changed now in the script, but we have heaps of memory, and I just don't see the point.
That's weird... this device has the most supercharged services.jar downloads...
http://android.mimic.ca/
Hmmmm, interesting... Hopefully someone who has an idea can shine some light for us. There must be a reason the script developer created a section specifically for ICS??
atsavlis said:
Hmmmm, interesting... Hopefully someone who has an idea can shine some light for us. There must be a reason the script developer created a section specifically for ICS??
Click to expand...
Click to collapse
Shhhh! He's behind you ........
I think this could potentially be a problem with DroidTheory's SHO script in this AXIOM XBREAD.
I don't know but I guess zeppelin can find out for us? :O
It did wonders for my Samsung Captivate.
I'm currently running it on the latest AOKP build, but it was one of the first things I installed. So I don't really have a feel for what the Nexus is like without it.
TwinkyOfHope said:
It did wonders for my Samsung Captivate.
I'm currently running it on the latest AOKP build, but it was one of the first things I installed. So I don't really have a feel for what the Nexus is like without it.
Click to expand...
Click to collapse
What options are you using?
TwinkyOfHope said:
It did wonders for my Samsung Captivate.
I'm currently running it on the latest AOKP build, but it was one of the first things I installed. So I don't really have a feel for what the Nexus is like without it.
Click to expand...
Click to collapse
Could you give us a quick rundown of what you did?? Specifically did you do that whole process about ODEX/DEODEX roms??
Make sure you have terminal emulator before replacing your services.Jar!
First use root browser to copy your services.Jar to your sdcard it is in the /system/framework folder.
Then go to http://android.mimic.ca and upload your services.Jar file.
Afterwards, I downloaded the modified services.Jar because the flashable cwm option didn't work for me.
I copied the modified services.Jar to /system then changed its permissions to the same permissions of the other .jar files in the /system/framework folder.
Then move the services.Jar with changed permissions to the /system/framework folder.
Once you have done that, open up terminal emulator.
Type this out, and press enter when said:
Su enter
Cd /system/framework enter
Chown 0.0 services.Jar enter
Chmod 644 services.Jar enter
Then reboot!
Start Up script manager.
Browse to the supercharger v6 pdf and click on it. Press su to run the script with superuser permissions.
The script will load and is mostly self explanatory. It will take you through the options when you first run it. I put the text scrolling on fast and disable the animation and integrate when it asks.
When you get back to the main menu, I usually use option 10. It calculates what minfree values to use based on the ram of the phone.
After all this, reboot once more and run the script again to see if you are 100% supercharged!
EDIT: if you run into bootloops by moving your services.Jar incorrectly, then just reflash your rom without wiping.
Sent from my Galaxy Nexus using XDA
Option 10 asks us to input our own Ram value, is this correct?? If so, what did you set it to?
atsavlis said:
Option 10 asks us to input our own Ram value, is this correct?? If so, what did you set it to?
Click to expand...
Click to collapse
Option 10 shouldn't ask you to input anything else. It should use the minfree calculator and set itself. Are you using update9 RC7? If it still isn't working for you, then try option 8 which should be the 768 settings
Sent from my Galaxy Nexus using XDA
i followed everything but when i run the first line of code i get
sh: cd/system/framework: not found
not sure if its because of the binary
You're missing a space.
zeppelinrox said:
You're missing a space.
Click to expand...
Click to collapse
thanks i just noticed that. funny thing is when i was on liquids rom they had a cwm zip file to flash for that rom and was able to bypass the cd /system/framework, enter, chown 0.0 services.jar, enter, chmod 644 services.jar, enter stuff. i am not sure if the stuff carried over but it let me run it on aokp31 release without it and it runs smoothly. phone is exactly the way i want it super snappy
Any use of the script on stock jelly bean?
Sent from my Galaxy Nexus
Here is a very simple script that turns off the key lights..
I find them very annoying at night, and an unnecessary waste of battery.
Extract the file from the zip, place in init.d and set permissions.
Might be useful for the Rom devs as an option in aroma installers?
If this isn't the place then please delete this thread someone of mod variety.
#THESE ARE NOT TO BE FLASHED IN RECOVERY
http://db.tt/E0UUuuAs
backfromthestorm said:
Here is a very simple script that turns off the key lights..
I find them very annoying at night, and an unnecessary waste of battery.
Place in init.d and set permissions.
Might be useful for the Rom devs as an option in aroma installers?
If this isn't the place then please delete this thread someone of mod variety.
Thanks.
http://db.tt/k0yjWc6c
Click to expand...
Click to collapse
nice can you also make one for button lights always on
Wow Thanks
i wish if there is an app for that,, So we can switch on/off easy
Isn't working for me..
Tried this both permissions:
x x x
x x x
x x x
and
x x x
x o o
x o o
Also did a full reboot after each permission change
XXX
XOX
XOX
Turn off fastboot?
Also try executing in root explorer.
manually executing helps. But after a reboot they are back on..until I execute the script again..
been looking for something like this for weeks but unfortunately it doesn't work for me, used root explorer set permissions as you wrote and disabled fastboot
edit
sorry my fault i did a quick reboot instead of a full reboot.. now working perfect many thanks matey and welcome to the one x
boshot said:
manually executing helps. But after a reboot they are back on..until I execute the script again..
Click to expand...
Click to collapse
Disable fastboot in power settings.
If no, then hold power for twenty seconds.
I did...but they always went on again.. Don't know why..
Oke the off Works
But the on does not work
When the phone boots up they are on
But when i turn off screen then the light are off and stay off
Sent from my HTC One X using xda premium
not work for me, and yes fastboot is off in powersettings!
ISC V6.1
peterfeter said:
not work for me, and yes fastboot is off in powersettings!
ISC V6.1
Click to expand...
Click to collapse
full reboot?
peterfeter said:
not work for me, and yes fastboot is off in powersettings!
ISC V6.1
Click to expand...
Click to collapse
Nice to see I'm not alone with that problem.
It's doing quite well if I manually execute it from Root explorer, but after a reboot it's not execute automatic by the script..
fastboot off and al lot of full reboots were done.. I really don't know what the problem is..
Solution: I'll never reboot by phone anymore
boshot said:
Nice to see I'm not alone with that problem.
It's doing quite well if I manually execute it from Root explorer, but after a reboot it's not execute automatic by the script..
fastboot off and al lot of full reboots were done.. I really don't know what the problem is..
Solution: I'll never reboot by phone anymore
Click to expand...
Click to collapse
Which ROM are you using? I have noticed that not all ROMs support all init.d scripts for some reason due to ramdisk issues. I haven't bothered investigating exactly why.
EDIT: @OP FYI The backlights off script that you have posted is identical to the backlights back on script. I am assuming that the back on script should read:
Code:
echo KB - set Key Backlight [B][COLOR="DarkRed"]1[/COLOR][/B]
echo "[B][COLOR="DarkRed"]1[/COLOR][/B]" > /sys/class/leds/button-backlight/brightness
I'm using Touch X-treme ( Sig )
Also tried it on villain rom with a friends HOX, same behavior.
I saw the sig but most people don't update them.
You can test to see if you have an underlying problem with (some) init.d scripts running correctly by unzipping this script and placing it in your system/etc/init.d folder and setting the permissions to match the others that you have in there.
Then do a full reboot and view the contents of the file:
/sys/devices/virtual/bdi/179:0/read_ahead_kb
It should read '4096'. If it doesn't, you have a problem with (some) init.d scripts.
All the script does is to increase the size of the SD card readahead cache to 4096 rather than whatever is is set to run at.
Once you have tested, simply delete the init.d script and reboot again to restore your original value.
Thanks.
Will test it later the day...
Send via Tapatalk 2
@ nobnut
Sorry had wrong link up for auto.
No apology necessary. I was just letting you know before people started getting confused
EDIT: The scripts work really well. Thank you.
I don't use them as init.d scripts. I execute them from shortcuts using Tasker, that way I can have manual control over the button lights from the homescreen
Bloomin' marvellous
Thanks again.
@nobnut Cool, btw the first few lines of the auto script don't do anything, the last line just sets it back to rw instead of ro, so the phone can have control back.