Develop Bugs

[MOD] Enable custom Boot Sounds in CyanogenMod 07/15/2011

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.

[SCRIPT] Random Boot Animations

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.

V6 SuperCharger Script

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

How to change bootanimation runnig stock.

Hi, I am currently using stock JB with a couple of mods/extras i managed to link in via the kitchen. But frustratingly so I cannot change the boot image and are hoping with appreciation someone in here can direct me. So far I have tried everything I am capable of. That is from within the kitchen enabling the function which is suppose to allow you to change your boot animation. Although it gives you the tick and creates a different directory for your boot animation this still doesn't work. I have tried replacing hTC_boot_one.zip file but does not work. Whenever i do replace or alter that file the boot starts as normal with white htc and then goes to black with android with a back light rolling from side to side, like kit in night rider. I also have tried flashing Mattmans-Boot-Animation which uses aroma installer. Still didnt work and as far as I know it just added the file in system/customize/resource/. There appears to be a command file preventing any changes internally in stock. Really appreciate and hope someone can help. Thanks in advance......happy new years.....:good:

Did you root the rom ?
You need root acces to write in the system directory's ......

You need SU

Mr Hofs said:
Did you root the rom ?
You need root acces to write in the system directory's ......
Click to expand...
Click to collapse
Yeah rooted with su access to system files.....cheers!
basically is just stock jb base.....

veroby said:
Hi, I am currently using stock JB with a couple of mods/extras i managed to link in via the kitchen. But frustratingly so I cannot change the boot image and are hoping with appreciation someone in here can direct me. So far I have tried everything I am capable of. That is from within the kitchen enabling the function which is suppose to allow you to change your boot animation. Although it gives you the tick and creates a different directory for your boot animation this still doesn't work. I have tried replacing hTC_boot_one.zip file but does not work. Whenever i do replace or alter that file the boot starts as normal with white htc and then goes to black with android with a back light rolling from side to side, like kit in night rider. I also have tried flashing Mattmans-Boot-Animation which uses aroma installer. Still didnt work and as far as I know it just added the file in system/customize/resource/. There appears to be a command file preventing any changes internally in stock. Really appreciate and hope someone can help. Thanks in advance......happy new years.....:good:
Click to expand...
Click to collapse
Dude. I think you need root your rom to get custom boot (-:
There're a lot ready-to-go tools for booting animation
Good luck !

allv.newbie said:
Dude. I think you need root your rom to get custom boot (-:
There're a lot ready-to-go tools for booting animation
Good luck !
Click to expand...
Click to collapse
its rooooooooooteeeeeeeed thx..

veroby said:
its rooooooooooteeeeeeeed thx..
Click to expand...
Click to collapse
lol
https://play.google.com/store/apps/details?id=com.simproductions.bachanger&hl=it I think it can works

fez vrasta said:
lol
https://play.google.com/store/apps/details?id=com.simproductions.bachanger&hl=it I think it can works
Click to expand...
Click to collapse
hey thx, but it did not work. I cant even find where it has placed the file. If it managed to. Man im p-i-s-s-e-d. not your fault its just on my tits. cheers....

allv.newbie said:
Dude. I think you need root your rom to get custom boot (-:
There're a lot ready-to-go tools for booting animation
Good luck !
Click to expand...
Click to collapse
Its rooooooooooooooooooteeeeeeeeeeeeeeeeeeeeed cheers....
Its my own custom rom but this little simple thing i cannot get around. I can only semis that within stock base there's a system file preventing any change...

Have you mounted system as rw? In root explorer you just press the button, not sure on other apps, and have you set the right permissions? rw-r--r-- to match everything else in system/customize/resource.
maXimus One X

evo1rs said:
Have you mounted system as rw? In root explorer you just press the button, not sure on other apps, and have you set the right permissions? rw-r--r-- to match everything else in system/customize/resource.
maXimus One X
Click to expand...
Click to collapse
Thanks for your help. Not sure what you mean by mount the system as rw. The permissions - yes always changed permissions when trying to replace the hTC_bootup_one.zip file. Cheers...

veroby said:
Thanks for your help. Not sure what you mean by mount the system as rw. The permissions - yes always changed permissions when trying to replace the hTC_bootup_one.zip file. Cheers...
Click to expand...
Click to collapse
If system is mounted as ro (read only) you can't change anything in the folder, this is the default setting I think and it needs to be mounted as rw to allow changes.
You could try to rename something in the system directory and if it doesn't actually change then you need to change it, or check if the filesize of the boot animation you replace changes.
Like I said, rootexplorer app changes it with a tap of the button, not sure what else to use
maXimus One X

evo1rs said:
If system is mounted as ro (read only) you can't change anything in the folder, this is the default setting I think and it needs to be mounted as rw to allow changes.
You could try to rename something in the system directory and if it doesn't actually change then you need to change it, or check if the filesize of the boot animation you replace changes.
Like I said, rootexplorer app changes it with a tap of the button, not sure what else to use
maXimus One X
Click to expand...
Click to collapse
Thanks again. No problem renaming any file within system so I guess it is mounted as rw. As to file size, i have tried different file sizes and identical file sizes to the hTC_boot_one.zip file. I have even tried using the same Zip file and just replacing with different images. Making sure to end up with the same values. Nothing seems to work.

Strange, I had rooted stock Rom and it worked fine, maybe you have the wrong format of files or haven't zipped as store only, no compression. I assume it is a sense one x Rom?
Maybe try this one I made for the Rom I use
http://forum.xda-developers.com/showthread.php?p=31136343#post31136343
maXimus One X

evo1rs said:
Strange, I had rooted stock Rom and it worked fine, maybe you have the wrong format of files or haven't zipped as store only, no compression. I assume it is a sense one x Rom?
Maybe try this one I made for the Rom I use
http://forum.xda-developers.com/showthread.php?p=31136343#post31136343
maXimus One X
Click to expand...
Click to collapse
Lol - hadnt planned on having maximus on my own custom rom but will give it a try tomorrow. Let you know...cheers again...:good:

Yeah, just to test formats and setup of course!
maXimus One X

Official HTC Flashlight APK for custom ROM [WORKING]

I have tried many of stock HTC Flashlight APKs on my WFS+CM9+MIUIv4, but none of them worked. Then I digged the error log using logcat and fixed the issue. It was simply due to permissions. Change the permissions of the file /sys/class/leds/flashlight/brightness to 666, if the flashlight works fine, then you may need to create a /etc/init.d script to set permission each time device boots.
Create a file in /etc/init.d with following line
chmod 666 /sys/class/leds/flashlight/brightness
Click to expand...
Click to collapse
ENJOY!!! HIT THANKS AND LET HELP OTHERS!!!

painkalshafeer said:
I have tried many of stock HTC Flashlight APKs on my WFS+CM9+MIUIv4, but none of them worked. Then I digged the error log using logcat and fixed the issue. It was simply due to permissions. Change the permissions of the file /sys/class/leds/flashlight/brightness to 666, if the flashlight works fine, then you may need to create a /etc/init.d script to set permission each time device boots.
Create a file in /etc/init.d with following line
ENJOY!!! HIT THANKS AND LET HELP OTHERS!!!
Click to expand...
Click to collapse
A really good find...... Good for people who still want some sense stuff in custom roms
I personally never used the HTC application, but will try this sometime

ill try nextime.. busy for work right now, anyway tnx!

I would like to ask something, a little offtopic, but I'm sorry. Could the same be applied for Link2SD? In the custom rom that I use (gb_2.3.7) every time I reboot it doesn't show the apps and I have to recreate mount scripts and "quick reboot". So if I write something relevant on the android emulator to give permission would it be solved..?
Again, sorry for the offtopic.

polfrank said:
I would like to ask something, a little offtopic, but I'm sorry. Could the same be applied for Link2SD? In the custom rom that I use (gb_2.3.7) every time I reboot it doesn't show the apps and I have to recreate mount scripts and "quick reboot". So if I write something relevant on the android emulator to give permission would it be solved..?
Again, sorry for the offtopic.
Click to expand...
Click to collapse
Any script put in /etc/init.d will be executed at boot time.
Still stick with GB??? even JB 4.2 is arrived for our WFS :good: