Hi,
I've set up an emulator using genymotion and am playing a game on it. What I need to do right now is:
Loop begin
2. Simulate a touch/tap at a particular location on the game.
3. sleep for 10 seconds
Loop end
I used to simulate the touch using xdotool in lunux. However, I think tasker should be able to handle this better. I'm a noob when it comes to tasker. I chanced upon a tutorial where in this guy explains how a touch can be simulated buy I'm stuck. It doesn't work. Here is what I've done so far:
1.Tasker > New task > "Test"
2.Run shell
Command:
while [ 1 ]; do
input tap 545 240
sleep 15
done
3. Run tasker.
4. Open the game.
Aaaaand.....nothing happen.
Please assist.
TIA.
Have you ran the task? You say run Tasker, but you still have to run the task or specify an event/condition when to run it.
polobunny said:
Have you ran the task? You say run Tasker, but you still have to run the task or specify an event/condition when to run it.
Click to expand...
Click to collapse
Um.. I pressed the play button, then switched to the game to see if it works every 10 seconds. But didn't work
blueren said:
Um.. I pressed the play button, then switched to the game to see if it works every 10 seconds. But didn't work
Click to expand...
Click to collapse
You ticked Use Root in Run shell?
polobunny said:
You ticked Use Root in Run shell?
Click to expand...
Click to collapse
Edit - Oh no.. I had forgotten to set a profile. Now that it's done, I'm able to get the basic tap command working. But when i put it in the while loop, it fails.
Yes- root enabled. Basic command works, loop doesnt.
blueren said:
Edit - Oh no.. I had forgotten to set a profile. Now that it's done, I'm able to get the basic tap command working. But when i put it in the while loop, it fails.
Yes- root enabled. Basic command works, loop doesnt.
Click to expand...
Click to collapse
That will help you ;D
http://tasker.dinglisch.net/userguide/en/flowcontrol.html
polobunny said:
That will help you ;D
http://tasker.dinglisch.net/userguide/en/flowcontrol.html
Click to expand...
Click to collapse
I had done a silly mistake -__- how stupid of me. Things work now! Thanks for you help.
<<Thread can be closed>>
Thread closed - OP request.
Related
i hope it doesnt force itself on the phone..
cookzitall said:
i hope it doesnt force itself on the phone..
Click to expand...
Click to collapse
Just don't let it force itself on the phone
If you want to disable OTA updates, you can remount your system folder, and delete /system/app/Updater.apk and /system/app/Updater.odex
I've done that on my own phone with no negative effects (so far). I'm fairly sure that should disable any OTA updates from being installed.
Once it does come out, I plan on downloading it (onto my computer), and giving it a good going over. I'll yank out anything that looks like it will disable my root access, and then resign it with the test keys and load it onto the phone using a modified recovery tool.
JesusFreke said:
Just don't let it force itself on the phone
If you want to disable OTA updates, you can remount your system folder, and delete /system/app/Updater.apk and /system/app/Updater.odex
I've done that on my own phone with no negative effects (so far). I'm fairly sure that should disable any OTA updates from being installed.
Once it does come out, I plan on downloading it (onto my computer), and giving it a good going over. I'll yank out anything that looks like it will disable my root access, and then resign it with the test keys and load it onto the phone using a modified recovery tool.
Click to expand...
Click to collapse
Ditto my good man.
We don't have to reject it per se any OTA "official" update. We just have to modify it and load it. It will have benefits to update, just not completly to Google's standards
can some one please help..
in the "how to get root" thread i asked a question..can some one help me out...thank u
JesusFreke said:
Once it does come out, I plan on downloading it (onto my computer), and giving it a good going over. I'll yank out anything that looks like it will disable my root access, and then resign it with the test keys and load it onto the phone using a modified recovery tool.
Click to expand...
Click to collapse
Details? I was under the impression the retail bootloader wouldn't accept any keys except tmob/google's.
With root though its no biggie to just install the update manually.
well who ever does accept this update please make not of the url it's calling so those of us that aren't can manually grab it. assuming this will still be an option
cookzitall said:
i hope it doesnt force itself on the phone..
Click to expand...
Click to collapse
It sounds like the current state of affairs is not safe. Everything typed on the phone is also submitted to a root shell. It is just a matter of time before I inadvertently type something that damages the filesystem.
wolfgangrupprecht said:
It sounds like the current state of affairs is not safe. Everything typed on the phone is also submitted to a root shell. It is just a matter of time before I inadvertently type something that damages the filesystem.
Click to expand...
Click to collapse
So start each reboot by typing "kill 26"
Disconn3ct said:
So start each reboot by typing "kill 26"
Click to expand...
Click to collapse
That won't help, as it's respawned by init when it dies. Maybe kill -STOP 26 would work, but I haven't verified that.
jimparis said:
That won't help, as it's respawned by init when it dies. Maybe kill -STOP 26 would work, but I haven't verified that.
Click to expand...
Click to collapse
Nope
Tried kill -STOP from adb shell, then "<cr>sleep 90<cr>" and ps showed 'sleep' running. (Sure, I could use 'reboot' but thats just a pita.)
has anyone thought to type "exit" and see if that terminal closes?
Darkrift said:
has anyone thought to type "exit" and see if that terminal closes?
Click to expand...
Click to collapse
it does but a new one is automatically spawned, so..
there are a new terminal emulator in the market that close with exit and you can do the same .
Disconn3ct said:
it does but a new one is automatically spawned, so..
Click to expand...
Click to collapse
satru said:
there are a new terminal emulator in the market that close with exit and you can do the same .
Click to expand...
Click to collapse
we are talking about the "invisible" ghost terminal that is open on the G1 by default, not one you install and run.
Can somebody explain to me why you woudnt want to update to rc30?
donutman said:
Can somebody explain to me why you woudnt want to update to rc30?
Click to expand...
Click to collapse
rc30 prevents root access. if you don't know why you want root, you prolly don't
JesusFreke said:
Just don't let it force itself on the phone
If you want to disable OTA updates, you can remount your system folder, and delete /system/app/Updater.apk and /system/app/Updater.odex
I've done that on my own phone with no negative effects (so far). I'm fairly sure that should disable any OTA updates from being installed.
Once it does come out, I plan on downloading it (onto my computer), and giving it a good going over. I'll yank out anything that looks like it will disable my root access, and then resign it with the test keys and load it onto the phone using a modified recovery tool.
Click to expand...
Click to collapse
You are awesome. Thanks and God bless you!
bennekl said:
You are awesome. Thanks and God bless you!
Click to expand...
Click to collapse
Wondering if Google guys are cursed him already
i keep getting a pop up saying that there i an update ready for the hone or something like that. is that the new update trying to come in. i just keep canceling it
The Great NY said:
i keep getting a pop up saying that there i an update ready for the hone or something like that. is that the new update trying to come in. i just keep canceling it
Click to expand...
Click to collapse
Hack it now or never, it will eventually apply the patch anyway.
Since I've gotten my Sidekick, I've noticed on most ROMs a horrible tendency to not register key-presses on the physical keyboard. There was one ROM early on that didn't do this (or very little) and one of the versions of RAGE was very good. I'm running GOV3.2 Bulky right now and it's not horrible, but it's noticeable. Does anyone have an idea of what might cause this? Thanks.
ged92781 said:
Since I've gotten my Sidekick, I've noticed on most ROMs a horrible tendency to not register key-presses on the physical keyboard. There was one ROM early on that didn't do this (or very little) and one of the versions of RAGE was very good. I'm running GOV3.2 Bulky right now and it's not horrible, but it's noticeable. Does anyone have an idea of what might cause this? Thanks.
Click to expand...
Click to collapse
I thought my keyboard was going bad or i just did not press the key all the way, now im on stock and i have not had that issue, hope someone finds the rom
ultraprimeomega said:
I thought my keyboard was going bad or i just did not press the key all the way, now im on stock and i have not had that issue, hope someone finds the rom
Click to expand...
Click to collapse
I wonder what the issue is that's causing it to show up on custom ROMs. Though, I've had it on the stock ROMs as well.
Have you tried this version of the kernel? Along with the removal of the keystroke logger, it also contains a patch that allows you to lower the keystroke timer delays... If you are experiencing dropped keystrokes, this could help, as the patch was designed for tht very issue.
http://forum.xda-developers.com/showthread.php?t=1663622
yogi2010 said:
Have you tried this version of the kernel? Along with the removal of the keystroke logger, it also contains a patch that allows you to lower the keystroke timer delays... If you are experiencing dropped keystrokes, this could help, as the patch was designed for tht very issue.
http://forum.xda-developers.com/showthread.php?t=1663622
Click to expand...
Click to collapse
Thank you!!!!!!!! I went ahead and dug into that thread. I do have that kernel already on my phone. I looked at the thread linked in that thread that gives a patch to adjust the timer delay and column delay in the kernel. HOWEVER, I'm not knowledgeable enough to apply that patch to my phone as it's given. Elsewhere in that thread, someone gave the commands to edit the settings manually through a terminal which I did through Android Commander on my PC and it worked wonders! Being the suspicious type, I guessed that the settings might not keep after a reboot. Unfortunately, that is the case and I had to reapply the settings after my phone finished restarting. So, I'll have to play with this a bit more to get it to keep, but thank you for showing me this!
You're welcome! That patch was made just for this issue. And yeah, it doesn't stick after a reboot, so we could either compile the kernel with chosen settings added in, or make a simple init.d script. I never did either one lol, was too lazy to try editing and building the kernel from source, and was on the stock ROM so I thought maybe it had no init.d support. You could probably create a file with those same commands used in Terminal, and throw it in your init.d folder to change the settings at boot.
yogi2010 said:
You're welcome! That patch was made just for this issue. And yeah, it doesn't stick after a reboot, so we could either compile the kernel with chosen settings added in, or make a simple init.d script. I never did either one lol, was too lazy to try editing and building the kernel from source, and was on the stock ROM so I thought maybe it had no init.d support. You could probably create a file with those same commands used in Terminal, and throw it in your init.d folder to change the settings at boot.
Click to expand...
Click to collapse
I set my column delay to 30 and my timer delay to 1 and it now feels like I'm typing on a Sidekick again! I wouldn't know how to correctly compile the kernel myself with these settings changed. So, are there any devs out there willing to make a zip that can be flashed in CWM so these settings will become permanent?
ged92781 said:
I set my column delay to 30 and my timer delay to 1 and it now feels like I'm typing on a Sidekick again! I wouldn't know how to correctly compile the kernel myself with these settings changed. So, are there any devs out there willing to make a zip that can be flashed in CWM so these settings will become permanent?
Click to expand...
Click to collapse
+1
I've noticed this problem and thought it was just me :$
I've had this happen as well as my screen thinking I was pressing it in one location when I wasn't even touching the phone. :s Had me at my wits end.
Sent from my SGH-T839 using xda premium
To those interested in the commands I used to fix the keyboard, see below. If you reboot your phone, these settings will go away and you will need to input these commands again. For a permanent fix, someone will need to add them to a kernel that can be flashed. To use these commands, your phone must be rooted. I've successfully used Android Commander to enter these commands from my PC while my phone is connected via USB.
The current timer delay may be read with:
cat /sys/devices/platform/s3c-keypad/timer_delay
The default is 5 if I remember correctly.
A new timer delay may be set with:
echo 1 > /sys/devices/platform/s3c-keypad/timer_delay
The default 300 µs column delay value may be read with:
cat /sys/devices/platform/s3c-keypad/column_delay
A new delay may be set with:
echo 30 > /sys/devices/platform/s3c-keypad/column_delay
In either command, you may experiment with different values by changing the 1 or the 30 in either command to what you want. I believe the lowest is 1 and the max is 256 for the timer delay. If you damage your phone running these commands, that's on you. I'm just telling you what I did and feel worked for me. YMMV. Also, if you don't want to connect your rooted phone to your PC and want to use Terminal Emulator from the Play store, that will work too. You need to enter 'su' prior to running the above commands and grant the terminal super user permissions for the commands to take.
ged92781 said:
I set my column delay to 30 and my timer delay to 1 and it now feels like I'm typing on a Sidekick again! I wouldn't know how to correctly compile the kernel myself with these settings changed. So, are there any devs out there willing to make a zip that can be flashed in CWM so these settings will become permanent?
Click to expand...
Click to collapse
I'll work on it for the next releases of the Bi-Winning roms and also try to attach flashable zips.
RicAndroid said:
I'll work on it for the next releases of the Bi-Winning roms and also try to attach flashable zips.
Click to expand...
Click to collapse
Thank you!
ged92781 said:
Thank you!
Click to expand...
Click to collapse
You are very welcome! All done, BTW. Posting my updates now.
Permanent Fix(Manual way)
Taking the timer_delay and column_delay tricks shown above...I was able to make an init.d script(pretty easy, tbh) but don't feel it merits an update.zip since it's so easy. What I did was:
1. go to /etc/init.d
2. find the last script(In GOV3.3 it's 18complete) and rename it - adding one to the sequence(In my case I renamed it to 19complete)
3. make a new file name 18keyboardfix(The number depends on your rom, really...like if you renamed the above file to some thing like 33complete, you'd call this 32keyboardfix. Easy? right?)
4. Open the file you just created and put:
Code:
!#/system/bin/sh
echo 1 > /sys/devices/platform/s3c-keypad/timer_delay
echo 30 > /sys/devices/platform/s3c-keypad/column_delay
5. Set the permissions to rwxr-xr-x or whatever the numeric equivalent is. (0755, iirc)
6. Reboot
7. (Optional) Recheck the values with the following commands:
Code:
cat /sys/devices/platform/s3c-keypad/timer_delay
Code:
cat /sys/devices/platform/s3c-keypad/column_delay
I take no credit for this fix. Really, it was all ged92781 for providing the commands. All I did was find a way to make it permanent(Well, it's just reset when the devices is turned off and the init.d scripts set it back to you desired values, but that's debatable on whether it's permanent or not...either way...it works and is a simple fix)
SammaelAkuma said:
Taking the timer_delay and column_delay tricks shown above...I was able to make an init.d script(pretty easy, tbh) but don't feel it merits an update.zip since it's so easy. What I did was:
1. go to /etc/init.d
2. find the last script(In GOV3.3 it's 18complete) and rename it - adding one to the sequence(In my case I renamed it to 19complete)
3. make a new file name 18keyboardfix(The number depends on your rom, really...like if you renamed the above file to some thing like 33complete, you'd call this 32keyboardfix. Easy? right?)
4. Open the file you just created and put:
Code:
!#/system/bin/sh
echo 1 > /sys/devices/platform/s3c-keypad/timer_delay
echo 30 > /sys/devices/platform/s3c-keypad/column_delay
5. Set the permissions to rwxr-xr-x or whatever the numeric equivalent is. (0755, iirc)
6. Reboot
7. (Optional) Recheck the values with the following commands:
Code:
cat /sys/devices/platform/s3c-keypad/timer_delay
Code:
cat /sys/devices/platform/s3c-keypad/column_delay
I take no credit for this fix. Really, it was all ged92781 for providing the commands. All I did was find a way to make it permanent(Well, it's just reset when the devices is turned off and the init.d scripts set it back to you desired values, but that's debatable on whether it's permanent or not...either way...it works and is a simple fix)
Click to expand...
Click to collapse
Uh, oh....I used echo "number" /proc/sys/devices/platform/s3c-keypad in my script. Will I have to change it?
RicAndroid said:
Uh, oh....I used echo "number" /proc/sys/devices/platform/s3c-keypad in my script. Will I have to change it?
Click to expand...
Click to collapse
Idk, honestly. Try and see if your script works first, if not, then use the one I made using the commands ged92781 provided. Now...to find a way to fix the spaztic touch screen...that'll be tricky.
SammaelAkuma said:
Idk, honestly. Try and see if your script works first, if not, then use the one I made using the commands ged92781 provided. Now...to find a way to fix the spaztic touch screen...that'll be tricky.
Click to expand...
Click to collapse
I'm using your commands, dude. I'm very into details....so thanks!
RicAndroid said:
I'm using your commands, dude. I'm very into details....so thanks!
Click to expand...
Click to collapse
Lol. No problem. And good luck with the custom rom cooking.
How can I disable soft keys backlight without power saving? Is no longer in the settings of the Galaxy s6.
I don't believe theres a setting for it, I've looked and looked, I like to set it to 6 seconds but its nowhere to be found.
Yeah I think you need to root and install a custom Rom or xposed (if that's possible yet)
Please refer to my earlier post at http://forum.xda-developers.com/showpost.php?p=60009456&postcount=12 and/or use the search function.
The ATT version has this setting under Display. It's weird that the other versions don't have that setting.
How can I run adb for this fix? Can some one help me to run adb..
The post above has instructions on how to to that
I just ran terminal emulator from my phone and entered "settings put system button_key_light 0" and they are disable for good.
Capacitive Lights Off
Two ways ,
1. The observe the power saving mode turns it off by default.
2. This message is from the user/developer @Averix in one of the S6 thread,
"That thread covers the ADB method. I wrote an app that doesn't require root to set the values to whatever you want from .5 - 10 seconds on, off/on all the time."
Galaxy Button Lights
Hope this helps
nappent said:
I just ran terminal emulator from my phone and entered "settings put system button_key_light 0" and they are disable for good.
Click to expand...
Click to collapse
Are you rooted? Doesn't work for me.
knitler said:
Are you rooted? Doesn't work for me.
Click to expand...
Click to collapse
Does the app not work on your device?
knitler said:
Are you rooted? Doesn't work for me.
Click to expand...
Click to collapse
Use the app in the post above yours, I'm not rooted and it worked fine for me
Sent from my Verizon S6,
formerly abdel12345
Hey guys, just got my Pixel today. I was wondering if there is a mod that turns the earpiece into a loud speaker like the mod for the XL? Thanks.
I am using this:
https://forum.xda-developers.com/pixel-xl/themes/mod-enabling-dual-speaker-audio-playback-t3492257
However, do note that the earpiece speaker is too soft and negligible to work together for Stereo. My goal is to get the speaker to be louder and it does that.
It's all explained in the thread
MasK said:
I am using this:
https://forum.xda-developers.com/pixel-xl/themes/mod-enabling-dual-speaker-audio-playback-t3492257
However, do note that the earpiece speaker is too soft and negligible to work together for Stereo. My goal is to get the speaker to be louder and it does that.
It's all explained in the thread
Click to expand...
Click to collapse
Does this work for the non-XL pixel? The reason I ask is because I thought that was only for the XL. I'll give it a try tomorrow though.
evolzar510 said:
Does this work for the non-XL pixel? The reason I ask is because I thought that was only for the XL. I'll give it a try tomorrow though.
Click to expand...
Click to collapse
Yes it does.
I followed the steps and set to force maximum gain all the time. Then froze the app as I didn't wan't the notification showing up. The setting just stays.
MasK said:
Yes it does.
I followed the steps and set to force maximum gain all the time. Then froze the app as I didn't wan't the notification showing up. The setting just stays.
Click to expand...
Click to collapse
Cool! Thanks.
MasK said:
Yes it does.
I followed the steps and set to force maximum gain all the time. Then froze the app as I didn't wan't the notification showing up. The setting just stays.
Click to expand...
Click to collapse
I just tried to do the mod and it hasn't worked for me. When I try to use the adb commands, it always says no such file or directory. I even tried the older method of dowloading the mixer_paths file but I can't change permissions for that. How did you manage to do it?
evolzar510 said:
I just tried to do the mod and it hasn't worked for me. When I try to use the adb commands, it always says no such file or directory. I even tried the older method of dowloading the mixer_paths file but I can't change permissions for that. How did you manage to do it?
Click to expand...
Click to collapse
Well, there are 3 steps.
For first step, I simply copied the gz file into the /data/local/tmp folder using root explorer. I found this method easier than ADB.
For 2nd/3rd step, you need to execute the commands in root shell. (type su, enter) to grant root access before doing the 2 commands.
MasK said:
Well, there are 3 steps.
For first step, I simply copied the gz file into the /data/local/tmp folder using root explorer. I found this method easier than ADB.
For 2nd/3rd step, you need to execute the commands in root shell. (type su, enter) to grant root access before doing the 2 commands.
Click to expand...
Click to collapse
When I try to type in the commands, it says "can't gzopen chdloc_hardware_audio_mods_pixel__no_ull.tar.gz........."
I've tried typing the adb commands on my computer and on my phone through Material Terminal app.
evolzar510 said:
When I try to type in the commands, it says "can't gzopen chdloc_hardware_audio_mods_pixel__no_ull.tar.gz........."
I've tried typing the adb commands on my computer and on my phone through Material Terminal app.
Click to expand...
Click to collapse
Hmm.. you got root access in your terminal right?
Try posting on the thread itself.. You may get better help there Sorry
MasK said:
Hmm.. you got root access in your terminal right?
Try posting on the thread itself.. You may get better help there Sorry
Click to expand...
Click to collapse
Yep, I finally managed to do it. And it is true what they say, the earpiece volume is a lot quieter than the bottom speaker but at least it's something, lol.
MasK said:
Yes it does.
I followed the steps and set to force maximum gain all the time. Then froze the app as I didn't wan't the notification showing up. The setting just stays.
Click to expand...
Click to collapse
Can you show me where you edited this setting, I built a magisk module for this mod and it is in the xl forum. People are asking about it being louder
Hi! is there a way to do a rebbot on Head Unit Android 9 (PX6) ?
I know only the method pushing the small pinhole on the radio.
Maybe there is another way via interface in the settings?
thanks
I'd like to know too... without root (root is easy).
At the moment I use a terminal app and type 'reboot' but I'd like an easier method.
djmcnz said:
I'd like to know too... without root (root is easy).
At the moment I use a terminal app and type 'reboot' but I'd like an easier method.
Click to expand...
Click to collapse
Which app are you using? My Dasaita PX6 is not rooted. Can you give me a link? TIA
See wiki in my sig.
marchnz said:
See wiki in my sig.
Click to expand...
Click to collapse
I can't find the terminal app in your wiki....sorry. I don't want to root my Dasaita, just be able by terminal to do reboot, so i need to know which terminal app he used.
Just enter hctreboot in password for factory settings.
Ati_gangster said:
Just enter hctreboot in password for factory settings.
Click to expand...
Click to collapse
I will try! Thanks
[/COLOR]
MarcoZ76 said:
I can't find the terminal app in your wiki....sorry. I don't want to root my Dasaita, just be able by terminal to do reboot, so i need to know which terminal app he used.
Click to expand...
Click to collapse
Slow down; not suggesting a terminal app at all, read the wiki - factory password codes for various utility commands, you might pick up a few other things than might then enable helping others, rather than a quick answer to get what you want and exit.