Database Develop

Powertop

Tried searching but didn't see anything already posted....
Cyanogen posted on twitter:
powertop for android binary: http://bit.ly/VfOUN .. it needs a kernel with timer debugging enabled (this is in the CM kernels)
Its a tar file that you download. I tried deploying the files but I get an error:
Error opening terminal: unknown
Here is how I deployed the files......
Code:
# pwd
pwd
/system/etc/terminfo
# ls -l l
ls -l l
-rw-r--r-- 1 0 0 1672 Jul 3 00:47 linux
# ls -l u
ls -l u
lrwxrwxrwx 1 0 0 10 Jul 3 00:49 unknown -> ../l/linux
# ls -l /system/bin/powertop
ls -l /system/bin/powertop
-rwxrwxrwx 1 0 0 286648 Jul 3 00:42 /system/bin/powertop
#

I get the same problem.
My guess is cyan is going to include it with 3.6.1 so we can just wait for that to be released.

ive tried various things too. cyanogen, must use some voodoo to get it to work. chmod 777 the 3 files changing PATH, TERM and terminfo, no avail

From cyan on twitter:
if you can't get powertop to work, try "export TERMINFO=/system/etc/terminfo" first
Tried it, still no luck though.

Screen shot of the problem

GOT IT!
Code:
# su
su
# export TERMINFO=/etc/terminfo
export TERMINFO=/etc/terminfo
# export TERM=linux
export TERM=linux
# powertop

Attached some screenshots...
It suggested "increase the VM dirty writeback time to 15 seconds"...
I think that was part of the sysctl.conf tweak thread. I haven't redone those tweaks since I wiped and put cyan's new ROM on my phone. Interesting.
I wish my dos prompt would work with ANSI control codes so I could run it through ADB...

BTW, the tweaks it suggests are for X86, not Android. Most can be ignored, especially the ones about kernel options.
I included it with 3.6.1 too.

So what exactly does this do?

Breen said:
So what exactly does this do?
Click to expand...
Click to collapse
How did you find this website if you've never used a search engine before?

I didn't find anything specific to android.
Just like a "check what consumes most power"-app.

lmfwtw said:
Does accepting powertop suggestions reduce the speed of the phone?
It is currently suggesting
Increase the VM dirty writeback time from 5.000 to 15 seconds with
echo 1500 > /proc/sys/vm/...
Another one it suggest is
Enable the CONFIG_NO_HZ
Enable CONFIG_USB_SUSPEND
Enable CONFIG_HPET_TIMER
in kernel conf option
Click to expand...
Click to collapse
ubernicholi said:
only VM dirty writeback works
the others are for x86 architecture, which the g1 is not. ignore the recommendations of this app.
Click to expand...
Click to collapse
A few questions:
I've been running my phone with Open Overclocker at min 528 Mhz / max 528 Mhz. Would it save battery life to put the minimum lower? (I've found that the lowest you can go is "001 / 528" (leading zeros are necessary).)
How do you implement the VM dirty writeback? lmfwtw says "echo 1500 > /proc/sys/vm/...". But what is the "..."?
What is gp_timer? It always seems to be the #1 cause of wakeups by FAR. Next is futest_wait, and sometimes m2m_i2c. Can they be shutdown/decreased?
Is there anything else we can write to the kernel to save power? I found this, http://ubuntuforums.org/showthread.php?t=729644 but I have no idea if any of that is applicable / will brick my phone.

I didn't find anything specific to android.
Just like a "check what consumes most power"-app.
Click to expand...
Click to collapse
Yeah thats what I found too.
Dont pay any attention to that dude, he likes to play pretend moderator at times and ***** at people for useless posts when in fact his posts are just as useless and adding to the garbage that clutter up threads.
I found this: "Powertop is a Linux command line tool that monitors your laptop (or desktop) and offers suggestions on how to make your hardware consume less power."

I have some other questions as well, but I'll wait. Does anyone know the ones in my last post?

I've been running my phone with Open Overclocker at min 528 Mhz / max 528 Mhz. Would it save battery life to put the minimum lower? (I've found that the lowest you can go is "001 / 528" (leading zeros are necessary).)
Click to expand...
Click to collapse
Found in another thread...
Do NOT use 128/528. It hurts battery life and the processor. The jump between 528 and the idle frequency is big enough to require extra circuits to be switched on. That does two things... slows down the gain of the processor speed and hurts battery life more than simply running permanently on 528.
Click to expand...
Click to collapse
I assume going 001 / 528 would be even worse. Hope that helped.

Senorkabob said:
Found in another thread...
I assume going 001 / 528 would be even worse. Hope that helped.
Click to expand...
Click to collapse
Thanks. Actually, last night after I put it on 001/528, I started having freezes almost immediately. For example, each time the screen rotated when I took the keyboard out, it froze. And when enabling an Alarm, the toast message caused a freeze. And they were 100% full freezes, ie had to take the battery out. After about 5 full freezes, I decided to go back to 528/528 and everything went back to normal. I guess I'll stay on 528/528 hah

[OVERCLOCK]XT860/XT862 Overclock

Had a few minutes today to play around and wrote a few quick programs in native code to overclock the OMAP4430 to run at 1.1GHz or 1.2GHz instead of the stock 1GHz. You need to force the CPU to run at it's highest clock rate at all times if you want to verify that it works but this is not required if you take my word for it. Long story short, it is possible to change the maximum clock speed by directly manipulating the registers responsible for the clocking of the OMAP4430 but doing so in this manner doesn't alter the frequency tables that the kernel looks to, so as a result the phone thinks it is still capping out at 1000MHz. I'm working on this, don't worry.
This requires root privileges. To set the max clockspeed to 1.1GHz, run "1100" from the adb shell or terminal. Make sure the permissions are set to 755, ie: "chmod 755 1100" in the terminal in the directory you have placed the executable. (I just placed them both in /data/local/)
To reset it back to 1GHz, run "1000", same permissions as before.
To try out 1.2GHz, use "1200". 1.3GHz, use "1300".
It doesn't survive a reboot, so it won't do much damage. That being said, I take no responsibility whatsoever for any damage done to your phone, this is extremely experimental. I also take no credit for this, yang.felix was the one who figured out how to do this first:
http://forum.xda-developers.com/showthread.php?p=17669227#post17669227
Now, the real fun part is making this persist a reboot, and notify the kernel about the changes so that overclocking/underclocking can be easily performed with SetCPU or other apps.
**** EDIT ****
I removed the 1400 and 1500 binaries because in layman's terms... I screwed up. I don't have much time to work on this tonight but I'll try and put something better up; in the meantime, I removed the binaries because they are useless. I'm suspicious that the 1300 binary is destined to fail as well but apparently some of you out there are able to execute it without an immediate reboot so maybe it is a voltage problem. I'll keep you all posted.
**** N00B INSTRUCTIONS ****
Here's how I do it. If you don't already have them, I suggest downloading the following from the Market: "SetCPU", "Root Explorer" and "Better Terminal Emulator". I bought them; the $5 or so was well spent as these three apps are probably ones that I use the most. If you don't want to pay, you can find SetCPU here on xda-developers if you search for it; Root Explorer you'll have to pony up the $1.99 or whatever it is, Better Terminal Emulator you can do without if you look for "Terminal Emulator" in the Market.
Connect your phone via USB to your PC, select from the drop-down in your status bar "USB Storage" or whatever it says, and browse to your phone on your PC. Unzip the attachment from the first post to the root of your sdcard, ie: don't unzip it into any folders after browsing to your phone on your PC, just put them in the root of the drive. You can put them in whatever folder you like but if you want to keep it simple, don't bother putting them in a random folder unless you know what you're doing.
First, open up SetCPU and slide the sliders for Maximum and Minimum all the way to 1000. You can leave everything else alone, after sliding the bars just exit the app. This step is important so don't skip it.
Open Root Explorer. Navigate to "/system/xbin". Press the button at the top that says "Mount RW". This will allow you to save the binaries in this folder as it is normally mounted as read-only.
Now, open Better Terminal Emulator (or whichever terminal program you like, or even use adb if you are so inclined... although if you know how to use adb the following probably goes without saying) and assuming you followed my instructions earlier and saved the files "1000", "1100" and "1200" to the root of your sdcard, type the following commands in, pushing Enter/Return after each one:
Code:
su
(Click on Allow)
cd /sdcard
cp 1000 /system/xbin/
cp 1100 /system/xbin/
cp 1200 /system/xbin/
cd /system/xbin
chmod 755 1000
chmod 755 1100
chmod 755 1200
Now you can run the binaries from anywhere in your terminal without the requirement of being in the folder you've saved them because /system/xbin is typically included in your $PATH variable. Simply put, your phone always looks in this folder for any executable file you try to run if it doesn't find it in the current working directory.
In order to run "1000", simply type:
Code:
1000
And push Enter. You can do this from anywhere on your phone. You should see a message that says your phone has been reset to 1GHz.
To run "1100", you guessed it:
Code:
1100
Rinse and repeat.

Thank you. Works great, love it. I like the confirmation, noticing a solid performance increase and my phone doesn't seem to be heating up any more than normal after a few hours use.

Thanks! Will this work with the XT862 too?

I don't see why not; both the XT860 and XT862 have the same OMAP4430 chipset so the memory addresses tweaked in order to increase the maximum clock frequency ought to be identical.
Sent from my XT860 using xda premium

Never mind my problem was that I accidentally set the permissions to 775 not 755.

AcidRoot said:
Just tested on the XT862, it froze the device and required a reboot.
Click to expand...
Click to collapse
Just tested on my XT862. works fine, no reboot. make sure you have setcpu set to performance mode, and in the terminal (move to directory where the files are located) and run chmod 755 1100
---------- Post added at 03:35 PM ---------- Previous post was at 03:32 PM ----------
To the OP, what ROM are you running? I'm running Liberty, at 1100mhz, and I'm getting 35 MFLOPs single thread, 25 multi thread..

Keeps saying aborted
Sent from my DROID3 using XDA App

what do i put in adb to make this work. this is good news have been waiting to see this oc thanks.

oostah said:
what do i put in adb to make this work. this is good news have been waiting to see this oc thanks.
Click to expand...
Click to collapse
Read the whole first post, 2nd or 3rd paragraph answers your question 100%

ChaoticWeaponry said:
Just tested on my XT862. works fine, no reboot. make sure you have setcpu set to performance mode, and in the terminal (move to directory where the files are located) and run chmod 755 1100
---------- Post added at 03:35 PM ---------- Previous post was at 03:32 PM ----------
To the OP, what ROM are you running? I'm running Liberty, at 1100mhz, and I'm getting 35 MFLOPs single thread, 25 multi thread..
Click to expand...
Click to collapse
That's about what mine gets without the overclock sometimes higher/lower. 36 multi and 43 single just now, was as low as 8 yesterday with an average of 30. On liberty also.
Edit: haven't tried it yet

Slow down
I am noticing a consistent slow down when I perform the overclock. I did several tests and dropped the lowest and highest values and took the average. My single-thread (st) and multi-thread (mt) results for stock 1000 are 41st/49mt and for the overclock 1100 they are 38st/45mt. I am running stock ota gingerbread. Any ideas?

Not sure what I was thinking when I mentioned my Linpack results earlier; I'm getting nowhere near 75 MFlops. Before setting the max clock frequency to 1100MHz I consistently get a rate of about 27 MFlops, increasing to about 33 MFlops afterwards. Could have sworn I remembered it being higher but I must have been mistaken.
The Linpack results are highly subjective to quite a few other factors though and isn't very indicative of much but since it's a rather quick benchmark it is pretty easy to see that there is a significant increase in performance that isn't attributed to random error.
It shouldn't be too much more work to be able to alter the clock speed in a way where SetCPU or other clock-related applications can see and manipulate the hardware but I haven't had much free time at all lately and was pretty happy I was able to get this working.
It would be really nice to not have to rely on forcing the OMAP4430 to run full out with the "performance" governor but this was really just a proof of concept for me.
Sent from my XT860 using xda premium

we should be able to go to 1.2 with no problems on all of our phones. the RAZR is 1.2 with the same processor we have in the D3.

Rick#2 said:
Not sure what I was thinking when I mentioned my Linpack results earlier; I'm getting nowhere near 75 MFlops. Before setting the max clock frequency to 1100MHz I consistently get a rate of about 27 MFlops, increasing to about 33 MFlops afterwards. Could have sworn I remembered it being higher but I must have been mistaken.
The Linpack results are highly subjective to quite a few other factors though and isn't very indicative of much
Click to expand...
Click to collapse
Increase from 1000 to 1100 = 10%, 27 to 33 >= 10%. Better than can be expected imo.
Stock bell I'm getting ~43 single, ~67(saw a few 70+) multi at 1ghz
at 1.1ghz I'm getting ~48 single , ~78 multi, solid improvement averaged over 10 runs.

I'm running CM7.1, and when I try running 1100, it says "can't open /dev/mem/"

diceroll123 said:
I'm running CM7.1, and when I try running 1100, it says "can't open /dev/mem/"
Click to expand...
Click to collapse
Are you trying to run it as root? "su" first

did you run chmod 755 1100? I would like to see the phone go to 1.2, as idroidnow said it is the same processor. Its amazing that the razr and d3 have such similar specs, and the razr bumped out 5501 on my benchmark, and stock d3 only grabbed 3500

Willis111 said:
Are you trying to run it as root? "su" first
Click to expand...
Click to collapse
Teehee, woopsie.
All it does after that is ask for SU permission, and nothing is output afterward. That's...normal, yes? ಠ_ಠ

diceroll123 said:
Teehee, woopsie.
All it does after that is ask for SU permission, and nothing is output afterward. That's...normal, yes? ಠ_ಠ
Click to expand...
Click to collapse
Yes, when you type "su" into a command prompt(gives you root) it might make the prompt look a little different but there's no confirmation that it worked, there would be if it didn't though. Once you're root it should work no problems, without root it will throw up errors about anything that it tries to change and perhaps some things that it just tries to read even.

Willis111 said:
Yes, when you type "su" into a command prompt(gives you root) it might make the prompt look a little different but there's no confirmation that it worked, there would be if it didn't though. Once you're root it should work no problems, without root it will throw up errors about anything that it tries to change and perhaps some things that it just tries to read even.
Click to expand...
Click to collapse
Wonderful! I haven't been using my phone much today, but I'm sure I'll notice a slight difference. Thanks!

[MOD] [New Version]CPU Editor Modified for ATRICS or ICSROMs

As promised earlier that I would share my work and yes I stand by that promise. The modified CPU editor script.
CREDITS​smokin1337 The original creator of the script​upnndwn4par For his support
todobarato For suggesting optimization which was really useful​
ONLY FOR ATRIX 4G Running ICSROM or ATRICS
The usual warnings. Do not blame me for bricked phones. This is still under testing phase and I need testers.
Please donot PM me with the results, Post them here in this forum
New Version
Added an optimization suggested by todobarato (thanks!!) Works fine. The only problem still is the sticky bit issue. Still Working on it
Download the New Version Here.
Instructions
1. Flash in CWM
2. Reboot
3. The script should start working on its own (Doesn't Work for now)
Open terminal > "auto-cpu" (Without quotes)
And also please let me know if the CPU frequencies are reverting at boot or not?
Changes Made
1. The original script by smokin1337 is kept intact , so advanced users can still use the script as usual.
2. The modifications automatically shutdown one of the cores when its not required.
So please go ahead test it and let me know results.
Anyone is welcome to help and provide suggestion or even modify this and contribute.

deathscream said:
As promised earlier that I would share my work and yes I stand by that promise. The modified CPU editor script.
CREDITS​smokin1337 The original creator of the script​upnndwn4par For his support​
ONLY FOR ATRIX 4G Running ICSROM or ATRICS
The usual warnings. Do not blame me for bricked phones. This is still under testing phase and I need testers coz I just lost my phone to my girlfriend for a week
Please donot PM me with the results, Post them here in this forum
Download the attachment.
Instructions
1. Flash in CWM
2. Reboot
3. The script should start working on its own (Couldn't test it , Sorry guys)
And also please let me know if the CPU frequencies are reverting at boot or not?
Changes Made
1. The original script by smokin1337 is kept intact , so advanced users can still use the script as usual.
2. The modifications automatically shutdown one of the cores when its not required.
So please go ahead test it and let me know results.
Anyone is welcome to help and provide suggestion or even modify this and contribute.
Click to expand...
Click to collapse
Thanks for your job
I try it..to take off one cpu I have do it manually..on reboot the cpu starts both

andrea_marcello said:
Thanks for your job
I try it..to take off one cpu I have do it manually..on reboot the cpu starts both
Click to expand...
Click to collapse
Yes I got those same results from others. Can you try using SManager and select the script /system/xbin/auto-cpu and let me know of the results.
Thanks!

what is this for?
and how do i know if it is working or not?

mindstorms54 said:
what is this for?
and how do i know if it is working or not?
Click to expand...
Click to collapse
It allows CPU mods without using an app (which of course uses battery).
You can change min/max frequencies on each core individually. You can even take one of the cores offline completely. Running on one core is not noticeably different from two for routine use. I hardly see a difference. I can't give any hard number for the increase in battery life since I have only been using it for less than two days. But battery life is definitely better.
There is some more info here:
http://forum.xda-developers.com/showpost.php?p=34427620&postcount=785
*********************************
deathscream,
I just tried it. The script is not running automatically as far as I can tell. I am not seeing the second core shutting down.
Thanks, and keep up the good work.

I'll look into it. I just got my phone back. Now I can test it without any problems.
Sent from my MB860 using xda premium

Hello,
I am following this and I think you are complicating it to much.
I have test this script and the original and it never disable the 2nd core.
If you will disable it is very easy with the following command as su: echo 0 > /sys/devices/system/cpu/cpu1/online
The only issue is that it comes online very fast again and you have to execute the command again... I have found the script that disable the 2nd core but only when the screen off, this isn't our problem, by CPU-spy it show deep-sleep is working.
I have changed the script to disable the 2nd core when the CPU frequency is under 350Mhz, this check every X second (I use 35seconds, this can be changed) , now the second core is offline when it detects low CPU frequency and stay offline, if you need it again I have observed after switch off and on again the screen it comes back online or by open set-CPU(I have it on widget to check CPU temp) if you have. If you use one very CPU intensive app comes only by itself too.
I put the script on /system/etc change the correct permission, run with SDmanager.
The script is:
--------------------------------------------------------
#!/system/bin/sh
#
#
while [ 1 ]
do
CPU0=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq`;
if [ $CPU0 -lt "350000" ]; then && echo 0 > /sys/devices/system/cpu/cpu1/online;
fi;
sleep 35
done
-------------------------------------------------------------
I hope this help, I am using it on CM7 and work better that I have expected.
Sent from my MB860 using xda app-developers app

Thanks a lot. Will try it out.
Sent from my MB860 using xda premium

It' dont work for me automatically after reboot.
I use the terminal to put the values by myself
It's a great tool.
Thanks for the work
Regards

You have a lot of features about OC on Atrix (scripts) here
http://forum.xda-developers.com/showthread.php?p=23715720
And here
http://forum.frandroid.com/topic/93255-autoucuv-forcage-cpu-et-oc-uv-gpu/
And here
http://forum.frandroid.com/index.php?/topic/105205-[APP]-✖-AtrixTweaks-(19/08/12)#entry1701606

it works but not automatically. i noticed a little battery increase. from 12hrs i got about 15 hrs uptime running latest icsrom.

fabianowerner said:
it works but not automatically. i noticed a little battery increase. from 12hrs i got about 15 hrs uptime running latest icsrom.
Click to expand...
Click to collapse
Yes. I tried it . The script doesn't run automatically. The sticky bit setting is driving me nuts. haven't slept the whole night. adding this to userinit also doesn't work , so I guess the only way would be try upacking the booimage, ramdisk and adding to the init.rc . I'll try running that there. That should probably work. But can't say for sure.

relax dude... even with the 2nd core disabled, the battery life had increased just a little almost insignificant hours. im pretty sure that we will have this serious issue solved only if someone can put hands on another ics kernel or this leaked kernel source.

fabianowerner said:
relax dude... even with the 2nd core disabled, the battery life had increased just a little almost insignificant hours. im pretty sure that we will have this serious issue solved only if someone can put hands on another ics kernel or this leaked kernel source.
Click to expand...
Click to collapse
Yeah. Hope for the best . Released a new version. It's not automated but its even better working. The cores are managed better than the original one.

deathscream said:
Yeah. Hope for the best . Released a new version. It's not automated but its even better working. The cores are managed better than the original one.
Click to expand...
Click to collapse
I just released a new version of ICSROM with init.d support.
It might help with your automation.

upndwn4par said:
I just released a new version of ICSROM with init.d support.
It might help with your automation.
Click to expand...
Click to collapse
Perfect. I'll check it. At work now. Thanks!

deathscream said:
Perfect. I'll check it. At work now. Thanks!
Click to expand...
Click to collapse
Thank you for your support!
I'm testing the new version on AOKP (not suggested, I know ) and it seems that doesn't switch well the cores status.....I'm able to set a maximum cpu1 settings but not it doesn't really applies it.
Within my tests I can see that the 2nd core is not so much important....I can play Riptide GP and Shine Runner (heavy games??? ) plus others apps with only 1 core without any noticeable lags...so
I'd like to ask you if you can make a unique profile and cut off other settings:
cpu0 @ 1ghz max, variable
cpu1 @ 456mhz max, variable (enabled only if cpu0 is @ 1ghz more than 5/10 seconds)
screen-off: cpu0 456mhz max, cpu1 disabled.

Thanks a lot for the suggestion. I'll definitely try adding those.
Sent from my MB860 using xda premium

If disabling a core is not fetching significant battery increase in leaked rom(s) then efforts to streamline sampling would we worthless as primary issue of battery drain would not get solved.
This came as a surprise as the second core was suspected to be the mAh drainer. Maybe it could be the GPU that runs at max..

After a long amount of observation, I found out that shutting down a core isn't reducing the battery drain. There is something more to it. Thanks to upndwn4par to release icsrom 1.4.5 so that I could test my scripts... I'm still working on the battery drain issue and will let you guys know the progress soon.
Sent from my MB860 using xda premium

[Script][Mod] Increase vibrator strength

Hi all ,
I found something interesting, at least for me... I think that the vibrator strength is not very strong for the on screen actions like mainly the navbar buttons (even if the vibrator amp is set to 100 and even if the 4.4.1/2 update increased a little the thing).
You need a rooted device with init.d support, if you have not init.d support you can use this app: Universal init.d (tested and it works). Init.d script is made to have the new values will applied on boot.
So to change the value in live with a file explorer (for testing before find the right value to put in the init.d script), go to:
Code:
/sys/class/timed_output/vibrator/driving_ms
And change the value for driving_ms to something like 35/40 (stock is 20) and the vibrator strength is increased (don't forget to save)... Adjust the value to your taste. But I don't think that a higher value than 60 will be a good idea (but it's up to you).
Also (in the same path) the warmup_ms seems to to do almost the same thing but I found that the vibrator strength is not the same by changing this value, It seems for me a little weird. So for now I change only the driving_ms value.
You can use an init.d script to keep the value at boot:
Code:
#!/system/bin/sh
#increase the vibrator strength
#stock value is 20
echo 40 > /sys/class/timed_output/vibrator/driving_ms
Just in case, in attachment the init.d script (remove the .zip extension before putting the script in /system/etc/init.d). Set the correct permissions like this, reboot:
Notes:
This will also increase the vibrator strength for incoming call/SMS-MMS, etc...
It's not the same thing as the vibrator amp...
It should work on all stock/AOSP based rom and stock/custom kernel, I don't know about CM based rom (but if you have the path mentioned above it should work).
I'm not responsible if something goes wrong with the vibrator, avoid values higher than 60 I think...
Hope this help

Hi,
I've been tested with the warmup_ms value in addition to the driving_ms, it seems it produces a more "consistent" vibrator strength, or it is only me?
So for now I ended with this:
Code:
echo 32 > /sys/class/timed_output/vibrator/driving_ms
echo 32 > /sys/class/timed_output/vibrator/warmup_ms
A 40 value as previously is a bit stronger, so for now I set it to 32 (35 is good too)...
Init.d script in attachment, don't forget to remove the .zip extension before putting the script in /system/etc/init.d.
Any feedbacks? CM users?

Doesn't this script set the same value as the apps below?
https://play.google.com/store/apps/details?id=com.dunnow.software.vibrationTuner&hl=en
https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod&hl=en

Hi,
Nope, at least for Trickster Mod (I use it) it only modifies the vibrator amp in /sys/class/timed_output/vibrator/amp... An it seems that it's the same thing for the first app, only the vibrator amp is modified.
Try with the values I modified and you'll see that it's not the same thing..., here you can have a vibrator strength stronger than with only the vibrator amp setting (and even at 100)...
Sent from my LG-D802 using xda premium

Hi,
Any feedbacks?
Some have tested on CM?
Forgot to mention that, obviously, you can change the vibrator amp too if it's not enough for you (and no need for an app):
Code:
/sys/class/timed_output/vibrator/amp
The init.d scrip will be like this (a value of 100 is an example, it's the max):
Code:
echo 100 > /sys/class/timed_output/vibrator/amp
If some wonders if this affects the battery life, I did not notice anything significant, at least for me...

Can you write a how to install this. I'm new to init.d script
Sent from my Nexus 5 using Tapatalk

killajoe said:
Can you write a how to install this. I'm new to init.d script
Click to expand...
Click to collapse
Hi,
I need more information... I thought the OP was clear, but who knows
I assume you are rooted right?
Is your current setup support init.script? For this check the OP of the kernel/rom you're using (or at least check /system/etc/, have you an init.d folder?).
If you are stock (rooted) use the app I mentioned in the op (https://play.google.com/store/apps/details?id=com.androguide.universal.init.d&hl=fr), the init.d scripts needed are in attachment in posts #1 and #2 with "how to"...
If I'm wrong explain better
Thanks

I actually like the vibration that subtle. I had several phones which had a too strong vibration alarm in my opinion. But still a good thing that you can adjust that, I might just try it out. Btw I remember my nokia 6410 was dancing into the sink full of water by the vibration alarm
Sent from my Nexus 5 using xda app-developers app

I just used my Galaxy Nexus yesterday and the vibrator in that is much better. It can handle short blips better and seems to vibrate the entire phone. Nexus 5 can't handle strings either...
Sent from my Nexus 5

Any way to rig this to make the vibration on my Moto X weaker?
Sent from my Nexus 5 using XDA Premium 4 mobile app

_MetalHead_ said:
Any way to rig this to make the vibration on my Moto X weaker?
Click to expand...
Click to collapse
Hi,
Sorry but I don't know for other devices... try to see if you have the path /sys/class/timed_output/vibrator/
If the different setting are presents (driving_ms, warmup_ms, amp) try to change the values and see...
Sent from my LG-D802 using xda premium

Is there any way to do this without root??

hbkekko said:
Is there any way to do this without root??
Click to expand...
Click to collapse
Hi,
Nope, sorry...

Is this strength or just milliseconds? Seems if I put it to 500 it vibrates for half a second at max strength.

viking37 said:
Hi,
I need more information... I thought the OP was clear, but who knows
I assume you are rooted right?
Is your current setup support init.script? For this check the OP of the kernel/rom you're using (or at least check /system/etc/, have you an init.d folder?).
If you are stock (rooted) use the app I mentioned in the op (https://play.google.com/store/apps/details?id=com.androguide.universal.init.d&hl=fr), the init.d scripts needed are in attachment in posts #1 and #2 with "how to"...
If I'm wrong explain better
Thanks
Click to expand...
Click to collapse
I am rooted, unlocked, stock. So I just run those scripts in the program listed and that's it?
Sent from my Nexus 5 using Tapatalk

killajoe said:
I am rooted, unlocked, stock. So I just run those scripts in the program listed and that's it?
Click to expand...
Click to collapse
Hi,
Yes, install the app then run it and choose to run the test (you'll have a Superuser request, accept) then reboot:
After if init.d script works you'll have an init.d folder in /system/etc (and the message like above). Put the init.d script named 01vibratorstrength in the init.d folder and set the correct permissions like in the OP.
Run the app again and activate the init.d script, set to ON like the screenshot:
Reboot again and all will be fine. You'll feel that the vibrator strength is increased (wait about 1-2 seconds after boot). You can check the values are changed by following the path /sys/class/timed_output/vibrator/**** (the vlaue you want check and you have changed).

Hi,
Another feedbacks?
killajoe, did you manage to get it working?
Thanks

CM11 Random Reboot Fix

I got fed up with CM11's constant reboots and did some digging, and discovered what was causing it. Kitkat by default uses zram, which increases CPU overhead, makes it painfully slow, and apparently on the DX, makes it unstable. I disabled it and made a swapfile in /data, a day and a half of heavy tinkering later, not one crash, and it's rather snappy for being on a 5 year old device. I even installed a ****load of Xposed modules and overclocked. Not one crash.
The fix:
Use either ES or CM File Manager to make an init.d script with the following content:
Code:
#!/system/bin/sh
swapoff /dev/block/zram0
You want this done early, so name it "07-zramoff" or something. Set proper perms and you're done. It doesn't make a big difference as far as RAM usage goes (maybe 10MB), but if you're really worried about it, make a swapfile and an init.d script to swapon at boot.
Note: If you have the Gapps installed, your DX will still be painfully slow.
As always, thanks to the devs for keeping our old DXs useful.

argentwarrior20 said:
I got fed up with CM11's constant reboots and did some digging, and discovered what was causing it. Kitkat by default uses zram, which increases CPU overhead, makes it painfully slow, and apparently on the DX, makes it unstable. I disabled it and made a swapfile in /data, a day and a half of heavy tinkering later, not one crash, and it's rather snappy for being on a 5 year old device. I even installed a ****load of Xposed modules and overclocked. Not one crash.
The fix:
Use either ES or CM File Manager to make an init.d script with the following content:
Code:
#!/system/bin/sh
swapoff /dev/block/zram0
You want this done early, so name it "07-zramoff" or something. Set proper perms and you're done. It doesn't make a big difference as far as RAM usage goes (maybe 10MB), but if you're really worried about it, make a swapfile and an init.d script to swapon at boot.
Note: If you have the Gapps installed, your DX will still be painfully slow.
As always, thanks to the devs for keeping our old DXs useful.
Click to expand...
Click to collapse
Lol my sister's phone broke so I was about to cook up an update for cm11-Kanged so she can run the droidx till she gets a better replacement, I'll try this and see how it goes, with gapps of course (my ROM includes them)

can you please give more detail?
how do you make the swap file? what directory does the script go? what are the permission?
would be nice if you can give a step by step instruction
Thanks in advance

I forget the step by step but you can just google it, ain't that hard to setup. My kang already has the groundwork for it since I have a script setup. A heads up though, swapping on android off of an SD card significantly reduces the life of your SD card and isn't really advised.