Hello friends! I really hate the vibrator function (yes, I love a quiet phone) and I will be very happy if someone know a way to totally disable the vibrator (well, let me explain, I don't want to open the phone and disconnect it...)
Each app can be configured individualy to vibrate or not (I know) and sound options lets you configure the vibration when the phone rings, but is very annoying to do it for each application, even when you have a lot of apps (it's my case)
I was googling for a module, a build.prop line, delete a file... no sucess...
Do you guys know a way to totally disable vibration?
Regards and merry Xmas
Havent tried myself, but you could delete the vibrator module so the kernel doesnt load it.
The module is located on /lib/modules/vibrator.ko
You should make a backup else where (just in case) and try to power the phone with it deleted to see if it all loads correctly and the vibrator should be disabled.
AzureusPT said:
Havent tried myself, but you could delete the vibrator module so the kernel doesnt load it.
The module is located on /lib/modules/vibrator.ko
You should make a backup else where (just in case) and try to power the phone with it deleted to see if it all loads correctly and the vibrator should be disabled.
Click to expand...
Click to collapse
Thanks for your reply, but unfortunatelly this doesn't work, I tried it and the module recreates itself when phone is restarted. I also tried to unload it with a init.d script, using the command rmmod -f vibrator, but no sucess...
Checking the init.rc file I have the following line:
Code:
#ko files for vibrator
insmod /lib/modules/vibrator.ko
Have you tried commenting that line?
The init.rc file is located on the root / of the phone.
AzureusPT said:
Checking the init.rc file I have the following line:
Code:
#ko files for vibrator
insmod /lib/modules/vibrator.ko
Have you tried commenting that line?
The init.rc file is located on the root / of the phone.
Click to expand...
Click to collapse
I tried it, but init.rc also recreates itself on every boot... I'm using SpeedMod K2-18 kernel, anyway to parse kernel parameters to disable vibrator module? Now, disable vibrator is a question of honor...
dani_mola said:
I tried it, but init.rc also recreates itself on every boot... I'm using SpeedMod K2-18 kernel, anyway to parse kernel parameters to disable vibrator module? Now, disable vibrator is a question of honor...
Click to expand...
Click to collapse
Use the leaked ICS builds as they do not have proper kernel support for the vibrator
Related
Here is a small script that toggle force usb charging option from pershoot kernel :
Code:
#!/system/bin/sh
export STATE=`cat /sys/class/power_supply/battery/force_usb_charging`
if [ $STATE == 0 ]
then echo 1 > /sys/class/power_supply/battery/force_usb_charging
echo "Enable USB Charging"
else echo 0 > /sys/class/power_supply/battery/force_usb_charging
echo "Disable USB Charging"
fi
It needs root permission and a suitable kernel such as pershoot's.
PS: first step in the XDA community
It will be nice if you could explain how to use this script (one of the several ways).
Sorry to forgot the documentation part, here it is :
It can be used with any terminal apps with root access, just copy the content into a file (toggle_usb.sh for instance) and launch it in root terminal with :
Code:
sh toggle_usb.sh
A more user friendly way is to use Script Manager with SMWidget to add it on your homescreen. I use it this way so I could disable charging when the tab is plugged only for a file transfert.
Will this work on other devices? Like say the acer a100 or acer a500. Considering getting one of those but don't like that neither will charge usb.
If this only works for galaxy tab, how come? Just curious why force usb works on galaxy tab and not other devices.
It might work on other devices if the charging chipp support it and if the kernel has driver for. For the Galaxy Tab,The stock kernel and many others shipped with custom rom don't allow usb charging.
If supported by your hardware the script should work, it only use standard script and kernel related configuration.
EDIT:
The Acer a100 et a500 have a dedicated charger wich deliver 12V which is far more than a USB port can deliver (5V), I seriously doubt they put a dc-dc converter to connect the usbport to the charging chip.
Envoyé depuis mon GT-P7500 avec Tapatalk
Widget Apps
Hello,
I've tried to make it more user friendly, so I created a small widget apps using my previous script. It's my first real apps for Android, it still has some flaws.
Known Issues :
when adding the widget the file is at unknown state, need to hit the refresh button
Design is perfectible especially icons...
I would like to thanks the authors of the android-widget-development-tutorials availlable on google code.
not on tab 3
ebolalex said:
Here is a small script that toggle force usb charging option from pershoot kernel :
Code:
#!/system/bin/sh
export STATE=`cat /sys/class/power_supply/battery/force_usb_charging`
if [ $STATE == 0 ]
then echo 1 > /sys/class/power_supply/battery/force_usb_charging
echo "Enable USB Charging"
else echo 0 > /sys/class/power_supply/battery/force_usb_charging
echo "Disable USB Charging"
fi
It needs root permission and a suitable kernel such as pershoot's.
PS: first step in the
Well so far as I can see the folder called battery here apears as a file that is un openable to root explorer, the terminal will go in but there is no editing allowance as the files are locked, command chmod return a bad mode eror, since force_usb_charging does not exist I thought np ill creat on... long story short I made a file by that name in storage then used cp to copy that file to the destination mentioned (after chmod the sys class power_supply to write for all, ) battery would not as I mention take such command. All in all I still have not created the file force_usb_charging with a 1 as cat. So question........ how can I create the file in the directory. I am rooted, all my work in terminal has been su, I see the # show me as rooted, and I can alter the permissions. (Ps sorry dude with svsfsswitch.apk did absolutly nothing as the file did not exist, nor did the script above) is the smt 210r that different from othet machines? Lol retorical q, sorry . Tyvm for the help in advance. With time ill learn this linux /android stuff out.... summery how to creat a file in the sys/class/power_supply/battery called force_usb_charging containing the number 1.....
Click to expand...
Click to collapse
grummbunger said:
ebolalex said:
Here is a small script that toggle force usb charging option from pershoot kernel :
Code:
#!/system/bin/sh
export STATE=`cat /sys/class/power_supply/battery/force_usb_charging`
if [ $STATE == 0 ]
then echo 1 > /sys/class/power_supply/battery/force_usb_charging
echo "Enable USB Charging"
else echo 0 > /sys/class/power_supply/battery/force_usb_charging
echo "Disable USB Charging"
fi
It needs root permission and a suitable kernel such as pershoot's.
PS: first step in the
Well so far as I can see the folder called battery here apears as a file that is un openable to root explorer, the terminal will go in but there is no editing allowance as the files are locked, command chmod return a bad mode eror, since force_usb_charging does not exist I thought np ill creat on... long story short I made a file by that name in storage then used cp to copy that file to the destination mentioned (after chmod the sys class power_supply to write for all, ) battery would not as I mention take such command. All in all I still have not created the file force_usb_charging with a 1 as cat. So question........ how can I create the file in the directory. I am rooted, all my work in terminal has been su, I see the # show me as rooted, and I can alter the permissions. (Ps sorry dude with svsfsswitch.apk did absolutly nothing as the file did not exist, nor did the script above) is the smt 210r that different from othet machines? Lol retorical q, sorry . Tyvm for the help in advance. With time ill learn this linux /android stuff out.... summery how to creat a file in the sys/class/power_supply/battery called force_usb_charging containing the number 1.....
Click to expand...
Click to collapse
Hi grummbunger,
The /sys folder is a special filesystem handled by the linux kernel itself (by the means of its drivers), it provide information and control on peripheral. So If you do not have a specific fil in your /sys you could not create it. My Script was intended to work with Pershoot kernel, if you do not use it, the driver may not be loaded or might use a different file.
I would asked you which ROM and Kernel you are using to test it, but unfortunately i don't have access to a galaxy tab anymore...
Could you post me the list of file availlable in your battery folder ?
Welcome in the community, I hope you'll find the way to hack into your device to suit your needs
Click to expand...
Click to collapse
samsung usb charge enabling
ebolalex said:
grummbunger said:
Hi grummbunger,
The /sys folder is a special filesystem handled by the linux kernel itself (by the means of its drivers), it provide information and control on peripheral. So If you do not have a specific fil in your /sys you could not create it. My Script was intended to work with Pershoot kernel, if you do not use it, the driver may not be loaded or might use a different file.
I would asked you which ROM and Kernel you are using to test it, but unfortunately i don't have access to a galaxy tab anymore...
Could you post me the list of file availlable in your battery folder ?
Welcome in the community, I hope you'll find the way to hack into your device to suit your needs
Click to expand...
Click to collapse
android version 4.1.2 (could not find a pershoot rom to run on a 7 inch samsung tab3, and before flashing at all i wanna make sure that the setting can't be applied without flashing as that is really a last resort.) but i am totally ok with flashing if it is nessesary. i have rockettab ready to go, but have no idea if that would help at all with this situation.
kernel 3.4.5-1304745-user
found that the link "battery" goes to sys/devices/platform/sec-battery/power_supply/battery there are many files there that report status of power and such i found, some of the files names are like:
batt_charging_source batt_lp_charging Charge_now charge_type soip_activated soip_level status talk_gsm wc_enable wc_status. etc...
tyvm for your interest in helping my problem!
Click to expand...
Click to collapse
grummbunger said:
ebolalex said:
android version 4.1.2 (could not find a pershoot rom to run on a 7 inch samsung tab3, and before flashing at all i wanna make sure that the setting can't be applied without flashing as that is really a last resort.) but i am totally ok with flashing if it is nessesary. i have rockettab ready to go, but have no idea if that would help at all with this situation.
kernel 3.4.5-1304745-user
found that the link "battery" goes to sys/devices/platform/sec-battery/power_supply/battery there are many files there that report status of power and such i found, some of the files names are like:
batt_charging_source batt_lp_charging Charge_now charge_type soip_activated soip_level status talk_gsm wc_enable wc_status. etc...
tyvm for your interest in helping my problem!
Click to expand...
Click to collapse
In fact the kernel you need to install must support charging from any sources. It should be specified in the kernel feature list. Stock kernel won't let you do this or it would work out of the box.
Be aware that your Usb port must provide enough power to charge your device.
You're welcome.
Click to expand...
Click to collapse
ebolalex said:
grummbunger said:
In fact the kernel you need to install must support charging from any sources. It should be specified in the kernel feature list. Stock kernel won't let you do this or it would work out of the box.
Be aware that your Usb port must provide enough power to charge your device.
You're welcome.
Click to expand...
Click to collapse
Well it is a dell usb with power share at 1.2 a a wall charger is 2, the battery is 4000ma, I digress though I have in fact found the battery lasts for well over the time I need so I am all good. Thanks again for the responce!
Click to expand...
Click to collapse
If your kernel supports init.d scripts you can save script to /system/etc/init.d and it will be automatically launched on device boot. You have to delete extension from script name and prefix is number from 00 to 99
Hi,
Any way to get this working on kitkat rom (carbon kk)?
Phone is photon q, in the original sprint rom burried under hidden menu's the is a app to do it, so it must be possible in some way....any ideas?
Thanks!
I put the following script in my /system/etc/init.d/ folder
Code:
#!/system/bin/sh
iptables -P OUTPUT DROP
On my Samsung GalaxyS - CM10 - Semaphore Kernel, it is applied at boot time as it should.
On my Galaxy Tab 2 7 CM9 (CM Kernel) on the other hand, it is not getting applied.
WHY ?
I've already checked: The scripts in the init.d-folder indeed do get executed.
And there wasn't also anything useful in the logcat either (nor did I find evidence that something flushed/overwrote iptables).
My next guess would be that the netfilter/iptables isn't loaded yet while init.d is still being processed.
Is there a way to load iptables manually upfront?
Thanks for your thoughts.
init.d iptables drop
The same problem. Sony Xperia stock, rooted.
I've made "iptables drop" script for init.d to prevent data leak BEFORE firewall loads.
It works. But sometimes script doesn't affect iptables, or something overwrites it.
Don't know what to do :/
Hi
I would like to reopen the topic.
I have written an init service which is executed by the init.rc script. This service set a new iptables configuration. I have checked all the outputs and it seems to work, but a later service overwrites my settings.
Does anyone know which service this and if it also has been executed by the init.rc script or later?
Otherwise I have to write a wrapper over iptables which only accepts my commands.
Regards,
cloooned
It seems like lucky random.
Your init script can be executed before or after tool-that-overwrites. The only way is to make delays and re-execute.
Anyway, phone wont be protected for some small period during boot.
Hello. I have a question about rules in afwall. I want to lock qq and wechat. It works very well. However, I used this app on mobile phones of a company. I need to uninstall afwall again. Is it possible to copy the created rules into init.d in order to keep them running without the app? Where can I find the file with the rules?
thanks...
micky1067 said:
Hello. I have a question about rules in afwall. I want to lock qq and wechat. It works very well. However, I used this app on mobile phones of a company. I need to uninstall afwall again. Is it possible to copy the created rules into init.d in order to keep them running without the app? Where can I find the file with the rules?
thanks...
Click to expand...
Click to collapse
This should be in the AFWALL+ thread however it can export the rules and with that you can turn it into a script and load it at boot. To lock qq and webchat you need to know the GUID and block that but be warned that turning on or off network interfaces deletes IPTables
I have been looking for this for days and i still cannot find the answer...
I would like to disable the MobiCore security daemon in the S3 4.3 stock kernel as on stock 4.3 the logcat is full of errors trying to initialize etc etc...
apparently commenting out the lines with "mobicore...etc etc" does the trick? im not sure what to do?
also is there a better method to disable it? init.d or something?
ive attacted the log if anyone wants to check it out!
Ricky Divjakovski said:
I have been looking for this for days and i still cannot find the answer...
I would like to disable the MobiCore security daemon in the S3 4.3 stock kernel as on stock 4.3 the logcat is full of errors trying to initialize etc etc...
apparently commenting out the lines with "mobicore...etc etc" does the trick? im not sure what to do?
also is there a better method to disable it? init.d or something?
ive attacted the log if anyone wants to check it out!
Click to expand...
Click to collapse
Have you had any luck?
zappacor said:
Have you had any luck?
Click to expand...
Click to collapse
i gave up due to my S3 being destroys but im pretty sure if you modify the init.RC of a kernel and remove the "mobicore*.." sections it should disable it but with that being said im not sure if any bugs will appear.
Ok, thanks mate!
I tried to disable it from init.rc, but it seems there was just some driver for accessing some resources. McClient is still running and producing alot of activiti, along with complaining about driver is not started.
The mcRegistry dir is tied into the fingerprint reader. That mobicore seems to use it, loading those .bin files.
service mobicore /system/bin/mcDriverDaemon -r /system/app/FFFFFFFF000000000000000000000001.drbin -r /system/app/mcRegistry/ffffffffd0000000000000000000000a.tlbin -r /system/app/mcRegistry/ffffffffd00000000000000000000016.tlbin
Hello,
Problem:
My Meizu MX3 (runs Flyme os 3 based on android 4.2.2) has preset "Camera" in the DIRECTORY_DCIM environment variable. Most of the camera apps respect this setting and they are saving photos in the Camera instead of the DCIM. This causes problems with automatic syncing, because photos are obviously expected to be in the DCIM.
Partial solutions:
I tried symlinking the two dirs, but as far as i know it is not possible in the FUSE used since the 4.2.2.
mount -o bind led to the duplicity in the gallery app and i don't consider it too "clean" solution.
I ended up with modifying source of Focal open source camera not to read DIRECTORY_DCIM env var, but rather just to save the picture into the DCIM directly.
Is there a way to change this variable on boot? I don't want to use any 3rd party apps for simple things like this. Editing init.rc led to nothing, because it is always replaced by the default one from the ramdisk.
Thanks in advance.
Have you tried making an init.d script to export the value you want? I haven't looked at the source code so I don't know if that'll make a difference, but that's the only thing I can think of, short of modifying the API call using e.g. Xposed (somewhat similar to what this mod does.)
You may want to link the SO question you also created, in case you get a working answer there, so anyone stumbling on this page will find the way to that.
The init.d dir was not on my phone, so i tried creating it. Scripts from there do not get run on the startup, which brings me back to the problem with editing init.rc.
I will probbly just keep using modified camera until they release Ubuntu mobile for mx3 - which according to rumors could be soon
Thank you for your time
Sent from my M353 using XDA Premium 4 mobile app
Check if in your init.rc there is something like
Code:
service flash_recovery /system/etc/install-recovery.sh
Then you can edit/create that script and enable running init.d scripts with:
Code:
busybox run-parts /system/etc/init.d
search on this forum for more info
Sent from my ZP980 using Tapatalk
Thank you, your guide worked and my scripts in init.d now get executed
Sadly, exporting the variable in script residing in init.d does nothing (the script itself gets executed, i tried echoing "test" in file). There must be something, which keeps reseting the DIRECTORY_DCIM to its original value, or else i'm out of ideas
Or am i assuming incorrectly, that Java code
Code:
Environment.DIRECTORY_DCIM
should read env variable settable by
Code:
export DIRECTORY_DCIM="DCIM"
?
Actually now that you say that I checked my init.rc and I don't have that. Plus if I try
Code:
echo DIRECTORY_DCIM
I have nothing, so at least for me it's not set there.
Sent from my ZP980 using Tapatalk
For me echoing the varible also returns nothing, but reading it by Java returns "Camera".
Since it was my only clue, i hoped it could be reset by exporting DIRECTORY_DCIM (since android docs states that
android.os.Environment provides acces to environment vars) I guess i was wrong.
Is there any other kind of emvironment variables, i am not aware of?
Sent from my M353 using Tapatalk
I checked that variable is hardcoded in the android.os.Environment class.
I can think of three methods to test to change that but I didn't test any:
Use exposed framework to change the call that gets DIRECTORY_DCIM, if that's possible it's probably the best choice.
Edit and compile again android.os.Environment (I have no idea how to do that or if it's even possible)
Make a script that monitors your X folder to move pictures to DCIM folder
I can help you with the last one
The xposed is great idea, but unfortunately it doesn't work. It says "unknown option -- c" which as far as i know has something to do with bad (probably outdated?) version of SU. Meizu's firmware is probably more customized android than i previously thought.
Now i'm using the solution you also advised - i am automatically moving media from Camera to DCIM - i was hoping for more clean solution, but i guess this is as close as i'll ever get (don't get me wrong, it works as it is supposed to. I'm just a perfectionist )
Thank's for your time.
np I'm a perfectionist too and it's always cool to learn how things work and can be hacked
Sent from my ZP980 using Tapatalk
Hey guys, gals, I recently downloaded the Viper v3.0.1 Android 4.4 Sense 5 rom, viperhttp://forum.xda-developers.com/showthread.php?t=2629211. With the Sense kernel edited by zarbov, says sweep2wake is enabled but doesnt work. Attempted to activate using Kconrol and Kernel tuner. Can anyone educate me on what is missing or give any advice. All would be appreciated!!
You need to set the start button and end button files
Sent from my HTC6435LVW using XDA Premium HD app
hey Torrented, attempted this with kernel tuner...no go. Recommended method of setting this?
.torrented said:
You need to set the start button and end button files
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
fastguy82 said:
hey Torrented, attempted this with kernel tuner...no go. Recommended method of setting this?
Click to expand...
Click to collapse
AHH! Figured it out after playing with permissions thanks
fastguy82 said:
AHH! Figured it out after playing with permissions thanks
Click to expand...
Click to collapse
Hey fastguy82 can u post your fix and does it stick after reboot? thanks
mopartonyg said:
Hey fastguy82 can u post your fix and does it stick after reboot? thanks
Click to expand...
Click to collapse
Navigate to /sys/android_touch/
Look for the sweep2wake files and edit them, I found that after you enter what you want press enter to add a second blank like to the file and then save and exit
I use root explorer and this is what I needed to do.
.torrented said:
Navigate to /sys/android_touch/
Look for the sweep2wake files and edit them, I found that after you enter what you want press enter to add a second blank like to the file and then save and exit
I use root explorer and this is what I needed to do.
Click to expand...
Click to collapse
thanks torrent still cany get settings to stick. u mean a space right after the entry?
mopartonyg said:
thanks torrent still cany get settings to stick. u mean a space right after the entry?
Click to expand...
Click to collapse
Well I somehow made it work last night, but after rebooting today. Not working again. So without "holding my hand",jk. What do I change exactly? Iam using Root Browser, I am going to permissions and editing them, correct? I have also tried using Kernel tuner to edit but this does nothing useful. All input once again is appreciated.d
fastguy82 said:
Well I somehow made it work last night, but after rebooting today. Not working again. So without "holding my hand",jk. What do I change exactly? Iam using Root Browser, I am going to permissions and editing them, correct? I have also tried using Kernel tuner to edit but this does nothing useful. All input once again is appreciated.d
Click to expand...
Click to collapse
not sure what to tell u, I have tried all different ways and still no luck
Settings do not seem to stick upon reboot, not sure why.
mopartonyg said:
thanks torrent still cany get settings to stick. u mean a space right after the entry?
Click to expand...
Click to collapse
Inside the sweep2wake file
Code:
1
<----Needs an extra blank line
Startbutton file
Code:
BACK
Endbutton file
Code:
MENU
fastguy82 said:
Well I somehow made it work last night, but after rebooting today. Not working again. So without "holding my hand",jk. What do I change exactly? Iam using Root Browser, I am going to permissions and editing them, correct? I have also tried using Kernel tuner to edit but this does nothing useful. All input once again is appreciated.d
Click to expand...
Click to collapse
No don't mess with perms, there in no need to just change the values inside the file (I recommend removing kernel tuner or just disable its SU access)
.torrented said:
Settings do not seem to stick upon reboot, not sure why.
Inside the sweep2wake file
Code:
1
<----Needs an extra blank line
Startbutton file
Code:
BACK
Endbutton file
Code:
MENU
No don't mess with perms, there in no need to just change the values inside the file (I recommend removing kernel tuner or just disable its SU access)
Click to expand...
Click to collapse
Make a init.d script to setup buttons
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Zarboz said:
Make a init.d script to setup buttons
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ill make some scripts later tonight when I get home from work.
.torrented said:
Settings do not seem to stick upon reboot, not sure why.
Inside the sweep2wake file
Code:
1
<----Needs an extra blank line
Startbutton file
Code:
BACK
Endbutton file
Code:
MENU
No don't mess with perms, there in no need to just change the values inside the file (I recommend removing kernel tuner or just disable its SU access)
Click to expand...
Click to collapse
I can them to work until reboot, hopefully Z will figure it out. Thanks
.torrented said:
Ill make some scripts later tonight when I get home from work.
Click to expand...
Click to collapse
you can also use cmdline.. i THINK i enabled that
you would set in cmdline
s2w_start=%value s2w_end=%value s2w=%value
and insert your values for %value
mopartonyg said:
I can them to work until reboot, hopefully Z will figure it out. Thanks
Click to expand...
Click to collapse
Considering the config files are spawned by the kernel and are rewritten upon boot ... that is why it wont stick
you can just add some edit lines to any init.d script in /system/etc/init.d/
just add
echo "WHATEVERKEY" > /sys/android_touch/sweep2wake_startbutton
echo "WHATEVERKEY" > /sys/android_touch/sweep2wake_endbutton
echo "WHATEVERSETTING" > /sys/android_touch/sweep2wake
Zarboz said:
Considering the config files are spawned by the kernel and are rewritten upon boot ... that is why it wont stick
you can just add some edit lines to any init.d script in /system/etc/init.d/
just add
echo "WHATEVERKEY" > /sys/android_touch/sweep2wake_startbutton
echo "WHATEVERKEY" > /sys/android_touch/sweep2wake_endbutton
echo "WHATEVERSETTING" > /sys/android_touch/sweep2wake
Click to expand...
Click to collapse
Yeah I know, I've done scripting for chris' kernel a while ago.
.torrented said:
Yeah I know, I've done scripting for chris' kernel a while ago.
Click to expand...
Click to collapse
since you compile source enable CMDLINE functions in defconfig
then you can use the s2w_start= s2w_end= s2w= in cmdline
Fixed the issue
Edit* Found the problem why S2W doesn't work, DT2W needs to also be enabled, I will look at the code and see if I can fide where its causing the issue.
If anybody wants this, all you will need to do is add two files to the sdcard called
torrented-s2w-start
torrented-s2w-end
inside these files add the button of choice using all caps like
1 of these: BACK MENU HOME
also this will enable S2W by default if it is not.
then flash the kernel attached, and then you should be good to go!
to debug this, there will be a file called torrented.log on the sdcard after my script executes
@Zarboz When I enabled cmdline in defconfig I got build errors in the /arch/arm/mach-msm/build-in.o
I didn't look into in a lot, but I can check it out later.
Also my 99torrented script will only execute if you are on my kernel, if you flash back to z's kernel this will no longer work! <---- the way @crpalmer's scripts work (you can only use them on his kernel)
source: https://www.github.com/torrented/Monarudo_GPU_M7
scripts:
"99torrented"
Code:
#!/system/bin/sh
(
if grep torrented /proc/version > /dev/null
then
echo "** torrented's Sweep2Wake configuration:"
for script in /system/etc/torrented/*
do
$script
done
else
echo "!! torrented's Sweep2Wake configuration not running, this isn't my kernel !!"
fi
)2>&1 | tee /sdcard/torrented.log
"sweep2wake.sh"
Code:
#!/system/bin/sh
F=/sdcard/torrented-s2w-
S2W=/sys/android_touch/sweep2wake_
echo "Enabling Sweep2Wake"
echo 1 > /sys/android_touch/sweep2wake
for which in start end
do
Fwhich=$F"$which"
if [ -r $Fwhich ]
then
s2w=`cat $Fwhich`
echo $s2w > "$S2W$which""button"
echo "Setings $S2W$which""button to $s2w"
else
echo "Leaving $S2W$which""button alone"
fi
done
This is what the log should output on success
Code:
Enabling Sweep2Wake
Setings /sys/android_touch/sweep2wake_startbutton to BACK
Setings /sys/android_touch/sweep2wake_endbutton to MENU
hi torrent, in an attempt to get this to work on my device , I flashed your kernel, and did the above steps. I kept getting an internet crash, so I reflashed your kernel, and rebooted. device soon froze and is now stuck looping on the DNA screen. Hardware keys to get into recovery are not working. i have been trying for over a half hour now. i am on viper 3.0, twrp .6 beta. phone is not recognized in adb. will pulling battery get me a reboot? or is that dangerous? any input would be appreciated. thanks
---------- Post added at 05:09 AM ---------- Previous post was at 05:06 AM ----------
.torrented said:
Fixed the issue
Edit* Found the problem why S2W doesn't work, DT2W needs to also be enabled, I will look at the code and see if I can fide where its causing the issue.
If anybody wants this, all you will need to do is add two files to the sdcard called
torrented-s2w-start
torrented-s2w-end
inside these files add the button of choice using all caps like
1 of these: BACK MENU HOME
also this will enable S2W by default if it is not.
then flash the kernel attached, and then you should be good to go!
to debug this, there will be a file called torrented.log on the sdcard after my script executes
@Zarboz When I enabled cmdline in defconfig I got build errors in the /arch/arm/mach-msm/build-in.o
I didn't look into in a lot, but I can check it out later.
Also my 99torrented script will only execute if you are on my kernel, if you flash back to z's kernel this will no longer work! <---- the way @crpalmer's scripts work (you can only use them on his kernel)
source: https://www.github.com/torrented/Monarudo_GPU_M7
scripts:
"99torrented"
Code:
#!/system/bin/sh
(
if grep torrented /proc/version > /dev/null
then
echo "** torrented's Sweep2Wake configuration:"
for script in /system/etc/torrented/*
do
$script
done
else
echo "!! torrented's Sweep2Wake configuration not running, this isn't my kernel !!"
fi
)2>&1 | tee /sdcard/torrented.log
"sweep2wake.sh"
Code:
#!/system/bin/sh
F=/sdcard/torrented-s2w-
S2W=/sys/android_touch/sweep2wake_
echo "Enabling Sweep2Wake"
echo 1 > /sys/android_touch/sweep2wake
for which in start end
do
Fwhich=$F"$which"
if [ -r $Fwhich ]
then
s2w=`cat $Fwhich`
echo $s2w > "$S2W$which""button"
echo "Setings $S2W$which""button to $s2w"
else
echo "Leaving $S2W$which""button alone"
fi
done
This is what the log should output on success
Code:
Enabling Sweep2Wake
Setings /sys/android_touch/sweep2wake_startbutton to BACK
Setings /sys/android_touch/sweep2wake_endbutton to MENU
Click to expand...
Click to collapse
hi torrent, in an attempt to get this to work on my device , I flashed your kernel, and did the above steps. I kept getting an internet crash, so I reflashed your kernel, and rebooted. device soon froze and is now stuck looping on the DNA screen. Hardware keys to get into recovery are not working. i have been trying for over a half hour now. i am on viper 3.0, twrp .6 beta. phone is not recognized in adb. will pulling battery get me a reboot? or is that dangerous? any input would be appreciated. thanks
findinghomer said:
hi torrent, in an attempt to get this to work on my device , I flashed your kernel, and did the above steps. I kept getting an internet crash, so I reflashed your kernel, and rebooted. device soon froze and is now stuck looping on the DNA screen. Hardware keys to get into recovery are not working. i have been trying for over a half hour now. i am on viper 3.0, twrp .6 beta. phone is not recognized in adb. will pulling battery get me a reboot? or is that dangerous? any input would be appreciated. thanks
---------- Post added at 05:09 AM ---------- Previous post was at 05:06 AM ----------
hi torrent, in an attempt to get this to work on my device , I flashed your kernel, and did the above steps. I kept getting an internet crash, so I reflashed your kernel, and rebooted. device soon froze and is now stuck looping on the DNA screen. Hardware keys to get into recovery are not working. i have been trying for over a half hour now. i am on viper 3.0, twrp .6 beta. phone is not recognized in adb. will pulling battery get me a reboot? or is that dangerous? any input would be appreciated. thanks
Click to expand...
Click to collapse
So holding down the power button and vol down button isnt working? <- this usually 99% will work if not
try this
plug in the device to the pc and run
Code:
adb wait-for-device reboot recovery
either restore the stock viper boot.img or grab this kernel http://www.androidfilehost.com/?fid=23329332407576625
I personally don't recommend opening the device to disconnect the battery, unless you really know what you are doing because the internals are very sensitive.