Official HTC Flashlight APK for custom ROM [WORKING] - HTC Wildfire S

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:

Related

[Q] SU not working

I am just about to release my new barebones build with a lot of new features but one thing is killing me. I cannot get superuser to work anymore with the latest build and the latest kernel. Rogue tools won't overclock without SU working and that just totall kills the speed of my build =(. The build is based off scoot's release 5 and I am using the latest kernel with and without the module update SU is unaffected. Everything else works though.
What have you changed from the build i sent you that might effect it? Does it work for you with the original build? Things to check are the sysinit.rc, make sure it calls userinit.sh on startup, and also check your userinit.sh in the /bin directory and make sure the su fix is still present in the file Otherwise, try opening the super user app and downloading the latest su binary file, if it fails to install then you most likely have partition permission issues.
I did edit userinit to enable the odex script. I am gonna check that now.
Ok I am pretty sure that was it. how do I add this line to userinit to have it be proper then? /system/bin/odex.sh
aceoyame said:
Ok I am pretty sure that was it. how do I add this line to userinit to have it be proper then? /system/bin/odex.sh
Click to expand...
Click to collapse
You'd need to put it in sysinit.rc like this :
service odex /system/bin/odex.sh
So put that line right at the end then? Or is there a special format it has to go in. Sorry, I have just never had to edit this particular file before lol.
aceoyame said:
So put that line right at the end then? Or is there a special format it has to go in. Sorry, I have just never had to edit this particular file before lol.
Click to expand...
Click to collapse
At the end is fine, you will see some similar lines in there, you may want to add some options such as :
console
user root
oneshot
I don't know what the structure of the odex script is so i don't know which options you will need to get it to run properly but these are the most likely, just experiment and see
I've always put it at the end, after the su fix just as "/system/bin/odex.sh" and nothing else. What does service do? will it run it continuously or just with different permissions?
I would say its more likely that something's gone wrong while you edited userinit.sh, and now it can't be executed.
did you edit it in windows? you may have /n/r line endings now instead of /n
if you did it in linux it may be a permissions problem
fixed! I used the userinit from my old barebones. Something changed in the update. The two looked totally different.

[GUIDE] Getting some old features back in Virtuous Sense ROMS

GUIDE: Getting some old features back
INTRO: For those who dislike some of the changes/features made to roms as they are developed and are asking how to get them back, here is a how to. It is usually a simple matter of pushing the old files from previous builds into your current rom. Keep in mind that the devs are building a rom as they see fit. As with any rom that you don't build yourself, there will always be things you want to change.
-If there is a bug, post it in the thread.
-If there is a change that you personally want, then do it yourself. Don't expect the dev, and everyone else who uses the rom, to accommodate your specific needs/wants. You may not have noticed, but you aren't the only one using the rom!
NOTE: This guide and code are meant for the virtuous sense rom, but the concept is universal. For example, if you are using some rom and the new version is posted with, say the amazon mp3 apk removed, and you want it back, refrain from cluttering up the dev's thread with a request to have it back. This is both selfish and a waste of posting space. If you are to the point of installing custom roms, you should first be able to type basic adb/terminal emulator commands to copy/delete files. In this case you would extract the amazon mp3 apk from an old .zip and push/install it into your current one. Now wasn't that easier than waiting and hoping that someone will do it for you?
NOW TO THE GUIDE:
Auto brightness mod - To revert from the auto brightness 'mod', which is far too sensitive, to the original, simply pull the services.jar and framework-res.apk from a rom before the patch, and push them to your framework folder. I've attached them to the second post for ease.
Reboot into recovery
Code:
adb shell mount /system
adb shell rm /system/framework/services.jar
adb shell rm /system/framework/framework-res.apk
adb push [directory of saved file]\services.jar /system/framework
adb push [directory of saved file]\framework-res.apk /system/framework
Reboot
-------------------
Keyboard mapping - The www/com key has been changed to a tab, which is good, as it was non-functional before. However the user keys have been changed too. I've modified a file which keeps the www/com key as TAB but also keeps the user keys as user assignable keys. Also attached to second post.
Reboot into recovery
Code:
adb shell mount /system
adb shell rm /system/usr/keylayout/vision-keypad.kl
adb push [directory of saved file]\vision-keypad.kl /system/usr/keylayout
Reboot
-------------------
Rosie auto-rotate - If you want to keep it so that rosie will only be in portrait mode with the keyboard closed, but dont want to turn off auto-rotate throughout all apps, just push the old rosie. Also attached to second post.
Reboot into recovery
Code:
adb shell mount /system
adb shell rm /system/app/com.htc.launcher.apk
adb push [directory of saved file]\com.htc.launcher.apk /system/app
Reboot
Attachments:
You need to rename "services.jar.zip" back to "services.jar" and "vision-keypad.kl.zip" back to "vision-keypad.kl". This is because the forum wont let you upload .kl and .jar extensions as attachments.
Thanks so much for this. I'll definitely be pushing the auto-brightness mod back, and I may do the keyboard, too (might let others do that one first, or see if rmk40/eViL release an update with that first).
Thanks for this!
Sent from my HTC Vision using Tapatalk
Couldn't make the quick key to work.. maybe I might be doing it wrong but I couldn't make it work.. ill keep trying
sent from t-mobile g2 using HTC sense
android602 said:
Couldn't make the quick key to work.. maybe I might be doing it wrong but I couldn't make it work.. ill keep trying
sent from t-mobile g2 using HTC sense
Click to expand...
Click to collapse
What version of virtuous are you running? Did you rename it and remove the .zip from the end?
I'm using that exact file w/ no issues
calendar/lockscreen
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
felixk87 said:
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
Click to expand...
Click to collapse
Lockscreen - no.
Calendar - maybe, haven't tried. However I did find these 2 threads by typing in the words "htc calendar" in the search box (which means you didn't search very hard )
http://forum.xda-developers.com/showthread.php?t=795222
http://forum.xda-developers.com/showthread.php?t=723761]
They may help you.
Good idea with this thread. It's impossible for us to please everyone and this is absolutely the most constructive way to deal with everyone's personal preferences. There is one key consideration for everyone. If we make other changes to the frameworks which you DO want, pushing files from this thread which have not been updated with said features will eliminate those changes as well. Point is, the concept here is good but it needs to be maintained.
Also, the intention with Virtuous is to provide options. The ROM isn't finalized so ROM Manager isn't populated with all the variants it will eventually have. Case in point, we had to re-base on the new Egypt RUU and are in the process of re-applying all our changes. If we had a variety of options, we would have to redo all of those as well. Once we're in a more "final" state, you'll start to see a lot more choices officially supported with the ROM.
The keyboard mod you have here will probably just become part of Virtuous 0.8.0, by the way. I had not realized our replacement eliminated the quick key customizations (oversight).
Chances are I'm not doing it right, as I'm only about 2% oriented in using ADB, but after following the code, pushing the files, etc, the phone boots up with perpetual errors and crashes. (Phone cannot be launched, etc.)
The process in which I did it was:
Wipe the G2, install v0.7.0, update to 0.7.4, remain in recovery and use adb and followed the code you provided above. (Everything says it works, in terms of mounting, pushing, etc.)
I've also tried it where I reboot after updating, let the phone launch fully, then go back to recovery to push the mod files. Same errors occur.
The only two mods I was interested in were the auto-brightness one and the orientation one.
Any idea what I did wrong?
felixk87 said:
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
Click to expand...
Click to collapse
You could possibly try pushing the lockscreen apk from SuperVillainZ.
NANDROID 1ST THOUGH!!!!!
Sent from my HTC Vision using XDA App
fox-orian said:
Chances are I'm not doing it right, as I'm only about 2% oriented in using ADB, but after following the code, pushing the files, etc, the phone boots up with perpetual errors and crashes. (Phone cannot be launched, etc.)
The process in which I did it was:
Wipe the G2, install v0.7.0, update to 0.7.4, remain in recovery and use adb and followed the code you provided above. (Everything says it works, in terms of mounting, pushing, etc.)
I've also tried it where I reboot after updating, let the phone launch fully, then go back to recovery to push the mod files. Same errors occur.
The only two mods I was interested in were the auto-brightness one and the orientation one.
Any idea what I did wrong?
Click to expand...
Click to collapse
Well from what you are saying, it sounds like the methods are correct. Did you make sure to remove the ".zip" from the end of the services.jar.zip file?
Can this be modified to restore ".com/www" to G2's?
the1wingedangel said:
Well from what you are saying, it sounds like the methods are correct. Did you make sure to remove the ".zip" from the end of the services.jar.zip file?
Click to expand...
Click to collapse
Yup, and I have "always show extension" enabled in folder options, so I definitely got rid of the .zip.
Maybe I'll fiddle with it a little more, see if I missed something.
All right, here's the error I get after removing the files for the brightness mod, and pushing the ones you attached in:
"The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly."
Basically the launcher is completely inaccessible, the phone remains perpetually in the settings screen because I suppose it's the only thing that it can load without the launcher. It also can't get a signal except for wi-fi, "Mobile Networks" in the settings remains unchecked, and it can't be turned on. Hahaha pretty severe for a rather simple mod.
Here's a full step-by-step of exactly what I did:
Wipe User Data, Wipe Cache
Install virtuous v0.7.0, then v0.7.4 from zip
Remain in Recovery
Open command prompt Change directory to ADB (c:\AndroidSDK\tools)
Entered the following codes one at a time:
- adb shell mount /system (mounts)
- adb shell rm /system/framework/services.jar (file removed)
- adb shell rm /system/framework/framework-res.apk (file removed)
- adb push C:\services.jar /system/framework (success 0.250s)
- adb push C:\framework-res.apk /system/framework (success 1.80s)
(I just have the files on C temporarily for the ease of it.)
Reboot
Then the errors hit once I unlock the screen.
Heheh, I can't really think of any other way to approach it. Hmmmm.
Any idea what I'd need to put back for video codecs? I'm running CM 6.1 but it doesn't run streaming videos from the NHL Gamecenter unlike the stock rom. I'm assuming its a codec issue and was wondering what I'd want to replace.
fox-orian said:
All right, here's the error I get after removing the files for the brightness mod, and pushing the ones you attached in:
"The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly."
Basically the launcher is completely inaccessible, the phone remains perpetually in the settings screen because I suppose it's the only thing that it can load without the launcher. It also can't get a signal except for wi-fi, "Mobile Networks" in the settings remains unchecked, and it can't be turned on. Hahaha pretty severe for a rather simple mod.
Here's a full step-by-step of exactly what I did:
Wipe User Data, Wipe Cache
Install virtuous v0.7.0, then v0.7.4 from zip
Remain in Recovery
Open command prompt Change directory to ADB (c:\AndroidSDK\tools)
Entered the following codes one at a time:
- adb shell mount /system (mounts)
- adb shell rm /system/framework/services.jar (file removed)
- adb shell rm /system/framework/framework-res.apk (file removed)
- adb push C:\services.jar /system/framework (success 0.250s)
- adb push C:\framework-res.apk /system/framework (success 1.80s)
(I just have the files on C temporarily for the ease of it.)
Reboot
Then the errors hit once I unlock the screen.
Heheh, I can't really think of any other way to approach it. Hmmmm.
Click to expand...
Click to collapse
Weird, I have no idea why that won't work for you. Anyway, there is another way around it. Just open up your patch.zip (from 0.7.0 to 0.7.4), go to the framework folder, and remove the services.jar and framework-res.apk from it. Then go about the wipe/install of both zips like normal. That way the patch zip will no longer replace those two files. Anything that you don't want changed in a patch zip can just removed from it.
Snap Jackel Pop said:
Any idea what I'd need to put back for video codecs? I'm running CM 6.1 but it doesn't run streaming videos from the NHL Gamecenter unlike the stock rom. I'm assuming its a codec issue and was wondering what I'd want to replace.
Click to expand...
Click to collapse
Sorry cant help on that one, I haven't run a CM rom since like 1 or 2.0 haha. You may try to see if others are having that problem, or if it is a known issue with the 6.1 and streaming videos. Is it only that site? Maybe a flash player version problem?
rmk40 said:
Good idea with this thread. It's impossible for us to please everyone and this is absolutely the most constructive way to deal with everyone's personal preferences. There is one key consideration for everyone. If we make other changes to the frameworks which you DO want, pushing files from this thread which have not been updated with said features will eliminate those changes as well. Point is, the concept here is good but it needs to be maintained.
Also, the intention with Virtuous is to provide options. The ROM isn't finalized so ROM Manager isn't populated with all the variants it will eventually have. Case in point, we had to re-base on the new Egypt RUU and are in the process of re-applying all our changes. If we had a variety of options, we would have to redo all of those as well. Once we're in a more "final" state, you'll start to see a lot more choices officially supported with the ROM.
The keyboard mod you have here will probably just become part of Virtuous 0.8.0, by the way. I had not realized our replacement eliminated the quick key customizations (oversight).
Click to expand...
Click to collapse
Yea, I assumed it would be out-dated soon anyway, as changes are made to your roms. I'll adjust it to keep up if the need is there though. It was just a couple of the more simple alterations that I made, and after seeing so many people cluttering up your thread with posts about them, I decided to post this.
Mostly, though, I just wanted to remind people that many simple issues/personal needs (like an app being removed from a rom, or a small change to one or two apps) can be solved with a little bit of thought and some adb knowledge - both of which should be present if you are working with a rooted phone in the first place!
the1wingedangel said:
many simple issues/personal needs can be solved with a little bit of thought and some adb knowledge - both of which should be present if you are working with a rooted phone in the first place!
Click to expand...
Click to collapse
I really cant emphasise this enough!
Sent from my sweet G2
Do you know if there is anyone to return the power down message. I remember before there being and option to restart the phone, hibernate, power off, or reboot into recovery. I liked having that. Is there anyway to return this feature?
Sent from my sweet G2
felixk87 said:
Is it possible to replace the sense lockscreen/calendar with the vanilla versions? I have tried searching but can't find find any instructions for how to do this
Click to expand...
Click to collapse
ddotpatel said:
You could possibly try pushing the lockscreen apk from SuperVillainZ.
NANDROID 1ST THOUGH!!!!!
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
by chance, did anyone try this? if not, I will try it in a few...

[HOW TO][MOD] V6 SuperCharger Script

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

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

[mod] script - disable key backlight

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.

Categories

Resources