There are some kernels that let you do this, but I'm using glitch which doesn't and I don't want to change.
I can set the vibration intensity by going to /sys/class/timed_output/vibrator/duty and changing the value to about 25000
Only problem is that this is set back to device default after reboot. Is there a way to manually set it permanently?
Cheers
Pete
Sent from my GT-I9000 using xda app-developers app
If you wanted you could make an init.d file to execute on each boot. Use a file manager and create a file called 99VibeIntensity and enter the code below. Paste it in /system/etc/init.d. Then change the permissions to -r-
Try this code here;
#!/system/bin/sh
#Changing Vibration Intensity...
echo 25000 > /sys/class/timed_output/vibrator/duty
Sent from my GT-I9000 using xda app-developers app
AlwaysDroid said:
If you wanted you could make an init.d file to execute on each boot. Use a file manager and create a file called 99VibeIntensity and enter the code below. Paste it in /system/etc/init.d. Then change the permissions to -r-
Try this code here;
#!/system/bin/sh
#Changing Vibration Intensity...
echo 25000 > /sys/class/timed_output/vibrator/duty
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Thanks very much for the reply!
My script says exactly this:
Code:
#!/system/bin/sh
#Changing Vibration Intensity...
echo 25000 > /sys/class/timed_output/vibrator/duty
is that right? doesn't seem to work, but i am pretty noobish. The system has created a file called 99VibeIntensity.bak, if that is telling at all.
Cheers
peterpandemic said:
Thanks very much for the reply!
My script says exactly this:
Code:
#!/system/bin/sh
#Changing Vibration Intensity...
echo 25000 > /sys/class/timed_output/vibrator/duty
is that right? doesn't seem to work, but i am pretty noobish. The system has created a file called 99VibeIntensity.bak, if that is telling at all.
Cheers
Click to expand...
Click to collapse
No worries man we all are at one point. Also it doesnt HAVE to be called 99VibeIntensity. the number at the beginning just tells the system in which order to execute the scripts. so make sure there isnt another one with 99 as the prefix. Just to be sure, call the script "S99VibeIntesity. Also make sure the file has no extension like .txt etc.
EDIT: Im sorry i told you the wrong permissions. After placing the file try this from terminal emulator.
chmod 644 /system/etc/init.d/NameOfOurScriptHere or use file manager to set permissions to -rw-r--r--
then do a reboot and see if the value in the file has changed.
AlwaysDroid said:
No worries man we all are at one point. Also it doesnt HAVE to be called 99VibeIntensity. the number at the beginning just tells the system in which order to execute the scripts. so make sure there isnt another one with 99 as the prefix. Just to be sure, call the script "S99VibeIntesity. Also make sure the file has no extension like .txt etc.
EDIT: Im sorry i told you the wrong permissions. After placing the file try this from terminal emulator.
chmod 644 /system/etc/init.d/NameOfOurScriptHere or use file manager to set permissions to -rw-r--r--
then do a reboot and see if the value in the file has changed.
Click to expand...
Click to collapse
i just cant seem to get it! i found some more info here: http://forum.xda-developers.com/showthread.php?t=1626756
whatever i do doesn't seem to work. i tried setting the permissions to rx-rx-rx because the other scripts in init.d have those permissions. i tried changing the script a little to match the attachment in that other thread, but no dice. im still googling hard - cheers for tips so far
Try full permissions. My script in init.d to activate swap at boot has full permissions. Also remove the space from in between /system/bin/sh line and between our next line #changing vibe intensity.
Sent from my GT-I9000 using xda premium
tried a few format changes and full permissions. got this now in filename "99VibeIntensity"
Code:
#!/system/bin/sh#VIBRATIONINTENSITY#echo "25000" > /sys/class/timed_output/vibrator/duty
all permissions set. maybe i should stop punching above my weight and just use devil or midnight!
peterpandemic said:
tried a few format changes and full permissions. got this now in filename "99VibeIntensity"
Code:
#!/system/bin/sh#VIBRATIONINTENSITY#echo "25000" > /sys/class/timed_output/vibrator/duty
all permissions set. maybe i should stop punching above my weight and just use devil or midnight!
Click to expand...
Click to collapse
You should use devil, it is amazing. The options are endless. So many options for performance. I get exactly a day worth of battery life keeping 3g on only when I need it. Also I am going to make you a new script that I want you to try out for me. Will upload in a bit.
Sent from my GT-I9000 using xda premium
Sounds good! :beer:
Sent from my GT-I9000 using xda app-developers app
Uploading to dropbow now... be available in a few min
Edit: here is the link http://db.tt/ADr1qScP
Reboot a few times and then go to the file and see if it is changing. What is the stock value BTW?
Also I am on devil kernel and have vibration at max. Goes up to like 43000 just FYI!
Sent from my GT-I9000 using xda premium
default is 40140. i tried your script and no good. im probably missing something massive here... bawlz to it, im thinking of trying jellybean anyway! is it this rom you're using? http://forum.xda-developers.com/showthread.php?t=1778526 might take the plunge!
Yes I do use that, with devil kernel. I have vibration on Max and it works well. Its very smooth, not very many random reboots, temple run okays smooth to. Good ROM :]
Sent from my GT-I9000 using xda premium
I'm not really from this forum but someone linked here from mine, anyway in case your writing your script on windows use notepad++ because the regular one doesn't work well.
second try this script:
Code:
#!/system/bin/sh
sleep 60
echo 25000 > /sys/class/timed_output/vibrator/duty
Permission should be set rwxr-xr-x
You might want to name it S1XXXX to make sure it runs amongst the first scripts to eliminate any endless loop scripts that may be running and blocking the initiation of later scripts.
Make sure your kernel supports init.d scripts.
The script will run approx 1-2 minutes after boot to make sure any other startup script that changes the value did it's stuff already.
If all else fails you could use this script without script manager and set run as su and on boot.
which romis best for jelly beans for captivate....plz post the link
kishke said:
I'm not really from this forum but someone linked here from mine, anyway in case your writing your script on windows use notepad++ because the regular one doesn't work well.
second try this script:
Code:
#!/system/bin/sh
sleep 60
echo 25000 > /sys/class/timed_output/vibrator/duty
Permission should be set rwxr-xr-x
You might want to name it S1XXXX to make sure it runs amongst the first scripts to eliminate any endless loop scripts that may be running and blocking the initiation of later scripts.
Make sure your kernel supports init.d scripts.
The script will run approx 1-2 minutes after boot to make sure any other startup script that changes the value did it's stuff already.
If all else fails you could use this script without script manager and set run as su and on boot.
Click to expand...
Click to collapse
Very good point, i never thought of the loop scripts. Good call my friend! So maybe he should try to make it execute first.
OK, I got it to work.
I used Root Explorer and used the same permissions as the files that where inside the folder.
Here is what you have to use:
User: Root
Group: Shell
Permissions: rwxr-xr-x
First off apologies if it's not OK to bump and old thread and then go off topic a bit.
I was just wondering if anyone knew if its possible to increase the vibration intensity of the S2 (I9100)? I tried to see if i could just do the same as in this thread (im a total noob) but when trying to navigate to the correct directory there appears to be no 'duty' folder and so i couldn't find the correct thing to alter.
I have tried asking in the S2 forums about vibrator intensity but the most help i got was a link to this thread.
Thanks
Goooober said:
First off apologies if it's not OK to bump and old thread and then go off topic a bit.
I was just wondering if anyone knew if its possible to increase the vibration intensity of the S2 (I9100)? I tried to see if i could just do the same as in this thread (im a total noob) but when trying to navigate to the correct directory there appears to be no 'duty' folder and so i couldn't find the correct thing to alter.
I have tried asking in the S2 forums about vibrator intensity but the most help i got was a link to this thread.
Thanks
Click to expand...
Click to collapse
I apologise for bumping either.
I've almost solved the problem by using STweaks app with DorimanX Kernel (I have old 7.4.2 with very old ROM on Android 4.1.2)
I set Vibration Force to 100%. Look at the attachment.
Related
is it possible to change the resolution of htc legend..........i tried lcd density but no use ...i am using azure cyanogen mod 6.....
i tried to edit the build pro..but no use
some one help me.......
Change Your Screen Resolution on HTC Evo 4g
I have successfully done this now. Remember that we don't have root in the same way that the EVO 4G does.
So:
Using any file manager that can read the / partition of your phone find and copy "/system/build.prop" onto your SD card.
Now copy the file to your desktop, and take a backup of that file too.
Open notepad and make sure word wrap is on, then open build.prop in notepad
Edit the required value (I chose 120), save and copy the file to your ADB/tools directory
Reboot your phone into clockworkMOD recovery, and connect your phone to the PC. Also go into the partitions menu of ClockworkMOD and click "mount system"
Open up ADB, and run "adb devices" to make sure the phone is connected and everything is working
Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
Then reboot your phone.
Let me know if this helps
Also, for other readers:
Make sure you read the post that is linked to in the above post, otherwise my instructions might not make sense... I might edit it later when I have time
@TheGrammarFreak
What is the resoultion of your screen now?
qzem said:
@TheGrammarFreak
What is the resoultion of your screen now?
Click to expand...
Click to collapse
I dunno how I'd work it out, sorry.
Ah...
I think I've found the first of many flaws with this, and it was mentioned in the EVO 4G post. Some apps ignore this and use the old resolution, and thus don't fill the screen (see attachment)
As you can the the status bar goes a lot wider than the app. The status bar is the full width of the screen.
Other problems arise too, a reinstall of the app doesn't help, and some apps just end up completely screwed...
qzem said:
@TheGrammarFreak
What is the resoultion of your screen now?
Click to expand...
Click to collapse
The resolution is the same - HVGA (pixels are hardware). You only change the dpi value which means that more things will fit to your screen but it will appear coarser than before.
grandioso said:
The resolution is the same - HVGA (pixels are hardware). You only change the dpi value which means that more things will fit to your screen but it will appear coarser than before.
Click to expand...
Click to collapse
Cool, thanks grandioso
On a slightly different note I've found that changing the value to 130, and using the 5 icon rows feature of launcher pro, is quite nice.
grandioso said:
The resolution is the same - HVGA (pixels are hardware). You only change the dpi value which means that more things will fit to your screen but it will appear coarser than before.
Click to expand...
Click to collapse
Thanks for clearing that .
There are some problems, but if you want to try it out, you can flash the update.zip I've just made.
160lcd.zip takes you back to default and 120lcd.zip makes your screen resolution higher.
@Briix
Can you make update for 130, like TheGrammarFreak suggested
I'd make one but I'm currently struggling to sign my .zip
EDIT:
Done it, just testing then I'll upload. I also notice that ROM Manager is one of the apps that ends up being screwed by this mod...
EDIT 2:
Wow, lots of edits. Anyhoo, 130lcd right here:
really nice
TheGrammarFreak said:
I have successfully done this now. Remember that we don't have root in the same way that the EVO 4G does.
So:
Using any file manager that can read the / partition of your phone find and copy "/system/build.prop" onto your SD card.
Now copy the file to your desktop, and take a backup of that file too.
Open notepad and make sure word wrap is on, then open build.prop in notepad
Edit the required value (I chose 120), save and copy the file to your ADB/tools directory
Reboot your phone into clockworkMOD recovery, and connect your phone to the PC. Also go into the partitions menu of ClockworkMOD and click "mount system"
Open up ADB, and run "adb devices" to make sure the phone is connected and everything is working
Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
Then reboot your phone.
Let me know if this helps
Also, for other readers:
Make sure you read the post that is linked to in the above post, otherwise my instructions might not make sense... I might edit it later when I have time
Click to expand...
Click to collapse
thanks man its working...........
Has anyone tried GrammarFreak's zip ?
Are there any problems with it ? Is it worth the effort ?
Do I have to wipe for this to work ?
Explicitly my zip? Or any of the zip's in this thread?
No wipe is needed.
Also, this method is inherently flawed. Some apps just don't use the edited resolution. Unless a way can be found to force these apps to scale up then there will always be ugly moments.
One of the things that I've found to not work is the HTC-IME mod. So is it worth it? That for you to decide... Lol
Sent from my Legend using XDA App
I mean yours or Briix' - are there any others ?
I don't want to edit the file manually if I don't have to
grandioso said:
Has anyone tried GrammarFreak's zip ?
Are there any problems with it ? Is it worth the effort ?
Do I have to wipe for this to work ?
Click to expand...
Click to collapse
Yup.. Tried.. working like a charm..
-------------------------------------------------------------------
Could you make a 140 and a 110 .. Just to try and see the result!?
I'll gladly test them both..
whitetigerdk said:
Yup.. Tried.. working like a charm..
-------------------------------------------------------------------
Could you make a 140 and a 110 .. Just to try and see the result!?
I'll gladly test them both..
Click to expand...
Click to collapse
I'd love to, but I can't at the moment, I'm at school and didn't bring my laptop. Unless someone beats me to it I'll make one in about an hour and a half; when I'm home.
I did try 140 myself but I didn't think it was worth it. I use 5 icon rows in launcher pro and the widgets started overlapping again. Like they did in the default resolution.
Sent from my Legend using XDA App
I'll wait..
Would be great though if WF & Clock Widget (The Sense look Clock) would adapt to new screen and fill it out..
Totally sweet indeed..
Yeah, if I knew more about android I'd look into forcing apps to scale up. I'm not sure if it's even possible, but hey.
Sent from my Legend using XDA App
requires Root (Superuser/Busybox), and a kernel that supports "init.d" scripts (script files that are stored in /system/etc/init.d/).
The script also has a partner called V6 supercharger they go pretty well together heres a link to the V6 supercharger by zeppelinrox
this script is so easy to use but users might have problems using it so here is a easy install for you all to use i have converted it to run on non samsung phones by renaming the file and removing processes connected to the stock samsung apps
Have Clockwork recovery installed
Download the update.zip from the bottom of the post
Reboot into recovery and install the update.zip
Now for the really easy part
Using Root Explorer navigate to ect/init.d and select mount RW now scroll down to the "97loopy_smoothness_tweak" file and open it in the text editor within root explorer and you will see the 3 main sections to the script they are called
At the start of the script you will see this
Code:
USER_LAUNCHER=""
you need to add the launcher you currently use so that it gets locked in
Resident system apps
Other system apps
Other apps
in the 3 sections you will see lines one code that look the same which are
Code:
if [ $PROCESS_1 -eq "0" ]; then PNAME="com.android.phone"; NICELEVEL=-20; if [ `pidof $PNAME` ]; then renice $NICELEVEL `pidof $PNAME`; PROCESS_1=1; P_CHECK=`expr $P_CHECK + 1`; fi; fi;
All you do to add a app you want to keep in memory for as long as possible is to edit the script and change these values for e.g the stock dialer to go contacts
Code:
PNAME="com.android.phone";
to
Code:
PNAME="com.japps.contactpro";
that will keep Go Contacts EX locked in the background so everytime you wish to use the GC EX dialer you wont have to wait for it redrawing before using it.
To find the process names goto the data/data folder and all the folders you see in there are the process names used by the apps e.g. the com.android.vending folder is the process name for the vending.apk aka market app.
Just to let users no this script will not auto start the apps on reboot and once you first select the app you have added to the script after reboot you will have to wait for the app to redraw the app again into the memory slot once it has done that the app will remain in a cache type(hidden) form until you run the app again then it will return to ram in the foreground.
lpy of XDA said:
What this script hopes to achieve:
- Entering your PIN with minimal/no delay/lag
- Minimising delay with lock screen pattern/unlock (not the time it takes to wakeup, but the touchscreen response lag)
- Having smoother notifications on the status bar, and smoother pulldown menu response
- Minimising Launcher lag while Media Scanner is running (can scroll through screens without heavy pauses)
- Minimising lag when scrolling through the market while icons are still loading
- Installing/Uninstalling apps while continuing other tasks
- Minimising/eliminating intermittent lag spikes in gaming
- No delay in being able to answer phone calls
... you get the idea
Click to expand...
Click to collapse
Thanks goes to the creator lpy @XDA
tweak source:
http://forum.xda-developers.com/showthread.php?t=1137554
Download:
http://www.mediafire.com/?g4fte3m87t3ukui
Install via CWM as update.zip ???
Have you tested this? I'm doing backup right now, and I might, but I'm looking at the script, and it says it's for Galaxy S. There's also a part on one of the first lines where you have to specify your launcher. Also, I don't think the scripts it our init.d even begin with "S_..", but rather with a two digit number, e.g. "06swapon".
EDIT: I edited the file to point to my launcher "com.fede.launcher", and touched nothing else. Named it "18smooth" or something of the sort, and put it in /system/etc/inid.d. The system failed to boot(never got past the second "LG" screen. Maybe it's the rom I'm using, but this is not working so far. I hope your promised tutorial is of use.
nutterbg said:
Have you tested this? I'm doing backup right now, and I might, but I'm looking at the script, and it says it's for Galaxy S. There's also a part on one of the first lines where you have to specify your launcher. Also, I don't think the scripts it our init.d even begin with "S_..", but rather with a two digit number, e.g. "06swapon".
EDIT: I edited the file to point to my launcher "com.fede.launcher", and touched nothing else. Named it "18smooth" or something of the sort, and put it in /system/etc/inid.d. The system failed to boot(never got past the second "LG" screen. Maybe it's the rom I'm using, but this is not working so far. I hope your promised tutorial is of use.
Click to expand...
Click to collapse
yes i have tested it and it works i will be uploading a modded one for the update.zip but if you install it just rename it to 97smoothnees, it asks for the launcher you currently are using e.g. adw launcher but if you have any worries wait until tomorrow for the tut
I think this is helping with battery management because my battery seems to be going down slower
Sent from my GT540 using XDA Premium App
Let's hope I'm wrong. Looking forward to that tutorial.
Downloaded it, and flash'd it in cwm on my girlfriends gt540. In her opinion, it makes a noticeable difference.
Sent from my Nexus S using XDA Premium App
Oki, so I install this script and I must say that it's working. ;-)
Tut added hopefully you can all understand it
Hmm, I don't know why but I don't have "97loopy_smoothness_tweak" in folder.
pRo_lama said:
Hmm, I don't know why but I don't have "97loopy_smoothness_tweak" in folder.
Click to expand...
Click to collapse
let me have a quick check to see whats going on
eoghan2t7 said:
Have Clockwork recovery installed
Download the update.zip from the bottom of the post
Reboot into recovery and install the update.zip
Click to expand...
Click to collapse
I did this and when i'm trying to do next i can't find the file in etc/init.d folder
pRo_lama said:
I did this and when i'm trying to do next i can't find the file in etc/init.d folder
Click to expand...
Click to collapse
i just tried the update.zip again there and it installed fine for me what clockwork version are you using?
but you can extract the zip file and manually add the file to the init.d folder and give it these perrmissions
xxx
xxx
xxx
I have 4.0.1.4.
When I apply script, reboot phone then on screen with PIN I don't have any delay.
pRo_lama said:
I have 4.0.1.4.
When I apply script, reboot phone then on screen with PIN I don't have any delay.
Click to expand...
Click to collapse
try adding it manually to see what happens.
So I must manualy add the file into system and then continue with tutorial ???
yes you coy the script to the ect/init.d folder then continue with the tut
ok, i'm going to try it ;-)
Can't download please mirror on another hoster.
Sent from my GT540 using XDA Premium App
Should this method not eat battery rather than conserving it? As apps run in background correct me if m wrong....
Sent from my GT540 using XDA App
This is an automatic installer for the lagfree script and the dalvik fix build.prop changes.
It does detect if you're using ICS or GB and does set it up accordingly.
Explanation and credits are in post 2. Manual instructions on how to apply this without the installer are at post 3. Have fun!
Most easiest way to check if the tweak script works is to open terminal before installation and type:
Code:
cat /proc/sys/vm/*
After flashing the zip do the same thing again and check if the numbers have changed (which they should have done).
pastime1971 said:
tony and i have worked out a flashable zip of init.d script + build.prop mod
there are two types of installations. choose one you like.
* system installation *
buttery-system.zip : edits /system/build.prop & installs /system/etc/init.d/99tune
to revert it, simply re-flash ROM.
you have to flash this every time you flash a ROM.
* user installation *
buttery-local.zip : edits /data/local.prop & installs /data/local/userinit.d/99tune
buttery-local-remove.zip : reverts /data/local.prop & removes /data/local/userinit.d/99tune
this changes /data/ and therefore, the effect is permanent unless you change it manually, which is the reason for buttery-local-remove.zip
# do a nandroid backup always.
# it probes if ROM is GB or ICS and apply mod accordingly. (only tested on ICS. please test it and feedback on GB.)
# to check if it is working, do the following in terminal
Code:
getprop | grep dalvik
getprop cm.buttery.active
cat /proc/sys/vm/*
!!! this script is based on vork kernel installer. the credit goes to vork team (benee and kiljacken)
Click to expand...
Click to collapse
Please give pastime1971 a "Thanks" at the following post: original post by pastime1971
Credits to whom they belong:
This idea has been ported over from the G2x forum (link, by flak0).
Thanks goes to flak0 and batoo.
The original thread of the tune.sh script (by batoo) can be found here.
and of course to pastime1971 who did the most work for this great installer. Thank you so much!
What does it do?
atb1183 said:
dexopt flags:
m=y -> use mapping, optimize the dalvik code
u=n -> NOT a uniprocessor, optimize for multicores
v=n -> do Not verify , breaks some old app compatibility but dalvik get a bit more speed (tonyp: doesn't work in Android 2.3!)
o=v -> im not sure, i think this sets optimization level to the highest. but again, not sure. alternate is o=a.
might wanna look into the /proc/sys/vm/dirty_ratio tweaks, cant remember exactly and im quite surprise many roms dont have these tweaks in the init.d scripts
it specifies how much cache/junk data to keep in memory. if the ratio is high, after a while, so much crap is kept that it waste your ram and slow the phone down.
Click to expand...
Click to collapse
Manual instructions:
Read this properly! This guide requires some knowledge of editing system files and running scripts.
It wouldn't harm to do nandroid backup! I didn't do one and everything worked fine - but it's on your own risk! You have been warned!
(if your phone won't boot anymore wiping /system and reflashing your ROM should restore everything without you loosing any data).
First we need to edit some dalvik dexopt flags in the build.prop (you can do that with the build.prop app from the market):
backup your build.prop
edit your build.prop
ICS: change dalvik.vm.dexopt-flags=.... to dalvik.vm.dexopt-flags=m=y,v=n,o=v,u=n
GB: change dalvik.vm.dexopt-flags=.... to dalvik.vm.dexopt-flags=m=y,o=v,u=n
right below add: dalvik.vm.execution-mode=int:jit
ICS only: change windowsmgr.max_events_per_sec=... to windowsmgr.max_events_per_sec=300
comment out dalvik.vm.heapgrowthlimit if it exists by placing a # in front (or delete the whole line).
save
Now Reboot to Recovery and Wipe Dalvik + reboot
Now you need to download and extract the attached tune.sh script and place it into /sdcard
Either run the script with Terminal Emulator or with the Script Manager app (don't forget to use root)
For the first method: Open the "Terminal Emulator" app and type:
Code:
su
cd /sdcard/
sh tune.sh
You're done. But you need to run the script after every reboot - or just place it under /system/etc/init.d/, rename it to "90tune" and set the permission to "rwxr-xr-x", then it will run automatically at each reboot.
Have fun!
@tonyp....
well just that I am a bit busy at office and saw ur thread fortunately....I would wait for people to give their comments, experience on GB (as I use DJ 1.5 beta from Carburano )and also the CWM flashable file so I dont need to do all that hardwork and reserve that for the office
Thanks once again mate
As soon as I'm able I will try and test this on GB and ICS. Maybe in the evening.
Thanks for bringing this to our attention Tony
Sent from my LG-P990 using XDA
tonyp said:
I'm "porting" over some information from the G2x forum (link) which should possibly help against the well known decreasing speed of the phone after some uptime.
At the G2x forum they're pretty excited and talking from buttery smoothness.
Thanks goes to flag0 and batoo.
The original thread of the attached script (by batoo) can be found here.
Read this properly! This guide requires some knowledge of editing system files and running scripts for now.
Edit: Good news, I linkes an app to edit the build.prop and included instructions how to run the script. Now it's pretty straightforward and you should be done in 10-15minutes.
It would be possible to create a flashable zip which does these steps for you, but creating a script which edits values in the build.prop isn't that easy and takes some time. If it works well it will get incorporated by the ROM devs anyway - owain already said at the G2x forum that he will include it in a later build.
It wouldn't harm to do nandroid backup! I didn't do one and everything worked fine - but it's on your own risk! You have been warned!
(if your phone won't boot anymore wiping /system and reflashing your ROM should restore everything without you loosing any data).
First we need to edit some dalvik dexopt flags in the build.prop (you can do that with the build.prop app from the market):
backup your build.prop
edit your build.prop
change dalvik.vm.dexopt-flags=.... to dalvik.vm.dexopt-flags=m=y,v=n,o=v,u=n
right below add: dalvik.vm.execution-mode=int:jit
change windowsmgr.max_events_per_sec=... to windowsmgr.max_events_per_sec=300
comment out dalvik.vm.heapgrowthlimit by placing a # in front (or delete the whole line).
save
Now Reboot to Recovery and Wipe Dalvik + reboot
Now you need to download and extract the attached tune.sh script and place it into /sdcard
Either run the script with Terminal Emulator or with the Script Manager app (don't forget to use root)
For the first method: Open the "Terminal Emulator" app and type:
Code:
su
cd /sdcard/
sh tune.sh
You're done. But you need to run the script after every reboot - or just place it under /system/etc/init.d/, then it will run automatically at each reboot.
Have fun! Works like a charm for me!
I only tested it with CM9 (owain build #77).
If you want to test that out in GB (either Stock or CM7) you probably shouldn't touch "windowsmgr.max_events_per_sec" (don't do step 5 above!).
Please give some feedback!
Click to expand...
Click to collapse
Thanks bro its flak0 though lol
Sent from my LG-P999 using xda premium
Crashing my Cm7 ROM
Goodmorning,
Ive just tried the tweak, but it just crashed my Phone. After updating the Build.prop the phone, just wouldnt start up anymore.
Restored backup.. and up and running again!
Im running Temasek CM7.
Just so you know!
Regards!
WyCkson
wyckson said:
Goodmorning,
Ive just tried the tweak, but it just crashed my Phone. After updating the Build.prop the phone, just wouldnt start up anymore.
Restored backup.. and up and running again!
Im running Temasek CM7.
Just so you know!
Regards!
WyCkson
Click to expand...
Click to collapse
I'm pretty sure this is cm9 ics only as it says ics in the title.
Sent from my Optimus 2X using XDA
Shadowchaz said:
I'm pretty sure this is cm9 ics only as it says ics in the title.
Sent from my Optimus 2X using XDA
Click to expand...
Click to collapse
OP states: 'If you want to test that out in GB (either Stock or CM7) you probably shouldn't touch "windowsmgr.max_events_per_sec" (don't do step 5 above!).'
Ximo F. Verde said:
OP states: 'If you want to test that out in GB (either Stock or CM7) you probably shouldn't touch "windowsmgr.max_events_per_sec" (don't do step 5 above!).'
Click to expand...
Click to collapse
You are right, missed that line! Thanks for clarifying.
flak0 said:
Thanks bro its flak0 though lol
Click to expand...
Click to collapse
lol sorry for that
I tried it with owain 78, I placed the script in init.d after editing build.prop and before rebooting, and it works perfect for now, no lag at all. Thanks tonyp,
Enviado desde mi LG-P990 usando Tapatalk 2
Tried on XXmrHyde's unnoficial 8 - works likec harm - that's great!
sergiob8 said:
I tried it with owain 78, I placed the script in init.d after editing build.prop and before rebooting, and it works perfect for now, no lag at all. Thanks tonyp,
Click to expand...
Click to collapse
Make sure to set the permission to rwxr-xr-x
Code:
chmod 0755 /system/etc/init.d/tune.sh
DAMN! Went back to CM7 because of this lag.
CM9 was unusable for me because I needed my phone to run properly at work.
I'm some kind of forced to flash
Don`t feel a need to do anything like that for CM7
Runs like a charm for the last few days.
I created a flashable zip to install the tune.sh script into init.d: http://d-h.st/NFq
You still need to manually edit the build.prop. I probably won't create an installer for that because this will probably get incorporated into the ROMs anyway.
tonyp said:
I created a flashable zip to install the tune.sh script into init.d: http://d-h.st/NFq
You still need to manually edit the build.prop. I probably won't create an installer for that because this will probably get incorporated into the ROMs anyway.
Click to expand...
Click to collapse
i was forced to get back to CM7 like others cause of this lag... will try this script later but
thanks a lot man, good to see people like you helping comunity.
it works for me, system is very fast
BUT google play store force closes instantly -.-
Player9446 said:
it works for me, system is very fast
BUT google play store force closes instantly -.-
Click to expand...
Click to collapse
After manual method, my play store still works flawless
Sent from LG 2X using Tapatalk 2 Elite
Player9446 said:
it works for me, system is very fast
BUT google play store force closes instantly -.-
Click to expand...
Click to collapse
Clear market data. Are you using cwm touch?
Sent from my LG-P990 using XDA
Hi,
is there a way so i can set the behavior of the Backlight from Back and Home Button myself or just turn it on all the time?
Im an TrickDroid Rom.
Thanks for your help :good:
Make a file and name it "99backlight" (no extension), and paste the following into it:
Code:
#!/system/bin/sh
echo "1" > /sys/class/leds/button-backlight/brightness;
chmod 444 /sys/class/leds/button-backlight/brightness;
Then save that file and copy it to /system/etc/init.d
Sorry for being a noob, but presumably this requires root?
I installed ES file explorer but couldn't see the system folder to paste it in.
RostokMcSpoons said:
Sorry for being a noob, but presumably this requires root?
I installed ES file explorer but couldn't see the system folder to paste it in.
Click to expand...
Click to collapse
I don't think i'd need it on all the time but perhaps make it a little less sensitive with light. It seems to go off very easily even in a dark room with a TV on is enough to make the Back and Home buttons backlight go off.
I also find this feature annoying. OK normally guess where they are but as you only need them lit when the main screen is on surely extra battery drain must be negligible.
So please HTC either option to have permanently on (with screen on) or ability to adjust sensitivity to personal preference.
Incidentally is there an official HTC blog to log such minor requests (not complaints)?
RostokMcSpoons said:
Sorry for being a noob, but presumably this requires root?
I installed ES file explorer but couldn't see the system folder to paste it in.
Click to expand...
Click to collapse
Yes, this does require root, sorry
Also for anyone trying to use that mod, you have to reboot after adding that file for the OS to read it
CNexus said:
Make a file and name it "99backlight" (no extension), and paste the following into it:
Code:
#!/system/bin/sh
echo "1" > /sys/class/leds/button-backlight/brightness;
chmod 444 /sys/class/leds/button-backlight/brightness;
Then save that file and copy it to /system/etc/init.d
Click to expand...
Click to collapse
just tried it and it doesn´t work.
i also rebootet after saving the file.
any advises?
MrShibby said:
just tried it and it doesn´t work.
i also rebootet after saving the file.
any advises?
Click to expand...
Click to collapse
i just noticed the file is gone after rebooting...
i also tried to change the permission but that didn´t help
MrShibby said:
i just noticed the file is gone after rebooting...
i also tried to change the permission but that didn´t help
Click to expand...
Click to collapse
Sorry but I had installed 2.4 now I am on 3.5 and the file stays but the light settings are still not changed
MrShibby said:
Sorry but I had installed 2.4 now I am on 3.5 and the file stays but the light settings are still not changed
Click to expand...
Click to collapse
Try changing the "1" to "255"
Shows how people are different. The lights not timing out is one of the things I hate about HTC devices. I wish I could permanently turn them off.
Sent from my LG-E970 using Tapatalk 2
americasteam said:
Shows how people are different. The lights not timing out is one of the things I hate about HTC devices. I wish I could permanently turn them off.
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
Make a file called 99noLEDs in /system/etc/init.d and put the following into it:
Code:
#!/system/bin/sh
echo "0" > /sys/class/leds/button-backlight/brightness;
chmod 444 /sys/class/leds/button-backlight/brightness;
This one definitely works. I use it on my phone. The other one was just kinda testing because 0 is to disable and 1 is to enable...
https://play.google.com/store/apps/details?id=com.deskangel.adjbrightness&hl=en
adding these to my init.d didn't work for me
However I have found an app that does the job:
https://play.google.com/store/apps/details?id=com.deskangel.adjbrightness&hl=en
jagnet said:
adding these to my init.d didn't work for me
However I have found an app that does the job:
https://play.google.com/store/apps/details?id=com.deskangel.adjbrightness&hl=en
Click to expand...
Click to collapse
Ok, the only I know works for sure is the disable one 2 posts above.
CNexus said:
Try changing the "1" to "255"
Click to expand...
Click to collapse
Now the lights will come on earlier but not permanently.... We are almost there
MrShibby said:
Now the lights will come on earlier but not permanently.... We are almost there
Click to expand...
Click to collapse
does anybody know a solution?
To make Xposed's AppSettings' DPI function work, I reverted this change: https://github.com/LiquidSmooth/and...92#diff-82378faf2a467d2f28e834dddd59207eR1363
Updated 01/04/2015 Build with overclock http://web.mit.edu/ispatel/www/builds/lsoc/LS-KK-v3.2-2015-01-04-vs980_yes_properoc.zip
First... Awesome. How did I beat Lawlrus.
Mightycaptain said:
First... Awesome. How did I beat Lawlrus.
Click to expand...
Click to collapse
I blame work on that one.
Glad to see a build of liquid again op, thank you. I'll DL at work and see about flashing.
Sent from my Vs980 running Aicp 5.0 4.4.4_r2
Edit nevermind, brain fart.
Its 4.4.4, can't read, sorry
@ishyesh
Maybe I'm missing it, but is there a toggle for knock on? Doesn't seem to be working and I don't see the option.
Sent from my LG-VS980
Lawlrus said:
@ishyesh
Maybe I'm missing it, but is there a toggle for knock on? Doesn't seem to be working and I don't see the option.
Sent from my LG-VS980
Click to expand...
Click to collapse
The knock code value is probably set to "0" instead of "1" in the kernel. ishyesh will most likely have to change the value in the kernel before compiling.
You can use a script to activate it in the mean time (assuming there is no option anywhere in the settings to turn it on or off).
EDIT: Try this (see if it fixes it): http://www.mediafire.com/download/icnb1bu56nq4jb9/Turn_Knockon-On_G2.zip
@bouchigo
Thanks, but it didn't work. I for the life of me cannot find the option to enable knock on if there is one. I'll just wait for op to respond I guess.
Edit: so it did work. But you need to make sure use proximity sensor to have it turn on.
I did mess with this option before flashing your zip, and it didn't work. So your zip definitely fixed it.
Thanks again bro.
Sent from my LG-VS980
Lawlrus said:
@bouchigo
Thanks, but it didn't work. I for the life of me cannot find the option to enable knock on if there is one. I'll just wait for op to respond I guess.
Edit: so it did work. But you need to make sure use proximity sensor to have it turn on.
I did mess with this option before flashing your zip, and it didn't work. So your zip definitely fixed it.
Thanks again bro.
Sent from my LG-VS980
Click to expand...
Click to collapse
To enable knock-on,
use Tasker or some sort of automation software to execute this whenever the system boots:
"echo 1 > /sys/devices/virtual/input/lge_touch/touch_gesture"
Also, I uploaded a camcorder fix in the OP. Flash like any other.
To change DPI for the overall system, use an application like "texdroider dpi". I haven't tested the built in DPI changer.
ishyesh said:
To enable knock-on,
use Tasker or some sort of automation software to execute this whenever the system boots:
"echo 1 > /sys/devices/virtual/input/lge_touch/touch_gesture"
Also, I uploaded a camcorder fix in the OP. Flash like any other.
To change DPI for the overall system, use an application like "texdroider dpi". I haven't tested the built in DPI changer.
Click to expand...
Click to collapse
I just changed the build prop using root browser. Thanks.
Also flashing that zip persists through reboots. No need to set a tasker if you flash that.
Sent from my LG-VS980
Btw, I'm not sure how Linux literate you guys are, but if you're curious and want to learn, try and unzip the KnockOnZip that bouchigo posted. Inside, you'll find a file within the path system/etc/init.d . Upon flashing, the script within that path is copied to your phone's /system/etc/init.d. On your phone, you can place whatever you want inside this directory so that it gets called whenever Android starts (read up on the naming of the script, that's critical). So in the zip, the 98knock-on-On script executes the same command I said you could tell Tasker to do.
Go crazy with that if you wish. And remember, make sure you check every zip that you flash.
ishyesh said:
Btw, I'm not sure how Linux literate you guys are, but if you're curious and want to learn, try and unzip the KnockOnZip that bouchigo posted. Inside, you'll find a file within the path system/etc/init.d . Upon flashing, the script within that path is copied to your phone's /system/etc/init.d. On your phone, you can place whatever you want inside this directory so that it gets called whenever Android starts (read up on the naming of the script, that's critical). So in the zip, the 98knock-on-On script executes the same command I said you could tell Tasker to do.
Go crazy with that if you wish. And remember, make sure you check every zip that you flash.
Click to expand...
Click to collapse
You probably already know this, but if you go into devices folder, and into the vs980 folder (I can't remember the folder structure, I haven't looked at source in a while), anyway, look for init.g2.rc and change the following before compiling:
From: chown system system /sys/devices/virtual/input/lge_touch/touch_gesture
To: write /sys/devices/virtual/input/lge_touch/touch_gesture 1
That should fix it so no scripts or tasker actions are required.
bouchigo said:
The knock code value is probably set to "0" instead of "1" in the kernel. ishyesh will most likely have to change the value in the kernel before compiling.
You can use a script to activate it in the mean time (assuming there is no option anywhere in the settings to turn it on or off).
EDIT: Try this (see if it fixes it): http://www.mediafire.com/download/icnb1bu56nq4jb9/Turn_Knockon-On_G2.zip
Click to expand...
Click to collapse
This zip worked great for me: VS98025A. Thanks
bouchigo said:
You probably already know this, but if you go into devices folder, and into the vs980 folder (I can' remember the folder structure, I haven't looked at source in a while), anyway, look for init.g2.rc and change the following before compiling:
From: chown system system /sys/devices/virtual/input/lge_touch/touch_gesture
To: write /sys/devices/virtual/input/lge_touch/touch_gesture 1
That should fix it so no scripts or tasker actions are required.
Click to expand...
Click to collapse
I did not know that! I'll be sure to incorporate that in my next iteration. Thank you!
http://forum.xda-developers.com/showthread.php?p=54906959#post54906959
Lawlrus said:
@ishyesh
Maybe I'm missing it, but is there a toggle for knock on? Doesn't seem to be working and I don't see the option.
Sent from my LG-VS980
Click to expand...
Click to collapse
could this also work? Worked for me on other ROMs. Liquid was one of my favorite GNEX roms.
mrdunn said:
http://forum.xda-developers.com/showthread.php?p=54906959#post54906959
could this also work? Worked for me on other ROMs. Liquid was one of my favorite GNEX roms.
Click to expand...
Click to collapse
No. I've never updated to knock code. So it didn't have anything to do with my touch firmware. Knock on needs manually turned on.
Sent from my Vs980 running CloudyFlex 2.6
Great work
Sent from my VS980 4G using Tapatalk
The best ROM!!!
The smoothness and fluidity of the UI is amazing.
Use one plus bionic optimized binaries and flash seeder using interactive governor and deadline as scheduler. Then, you have the best user experience on an Android device.
@luv2increase
Check yo pms
Sent from my Vs980
Anybody having issues with youtube playback on this Rom? I went back to stock for now as this Rom wasn't playing a lot of the youtube videos I was trying to watch.
What's the exact youtube error message?