The question explains it all. I am using Ubuntu 20.04 LTS. I have connected an android smartphone to pc using USB. Changed directory to internal storage using: cd /run/user/*/gvfs/*/'Internal Shared Storage' And now I wanna create a bash script. Did this: touch test.sh But it says: touch: setting times of 'test.sh': Operation not supported But if I 'ls' again, I see 'test.sh' actually got created. So whatever, I do this to edit 'test.sh' using vim: vim test.sh But got this: cannot open path of the current working directory: Permission denied Doing sudo outputs the same error. Is it possible to do what I am trying to do? Android version is 8.

I'm trying to open a text file from within a terminal window emulator -- but not so it opens in the actual terminal but more like I've just clicked on it. So my question is: What command can I use to open /mnt/sdcard/textfile.txt from a terminal window emulator from ROM Toolbox Lite within the Android GUI so that it will open with any one of my text editing applications? Will I need to run su before I can run what ever command? I'd prefer not to, but the device is rooted so I can run su. I'm using Android version 4.0.4.

When I want to install PrimeOS, I see a black page with a bash like command line instead of choices for choosing. Is it normal? If it is normal, what should I do and type in the page? In all PrimeOS install guides, there is choice for choosing not a place for typing. I make USB bootable with ventoy. My OS is LinuxMint. > Excuse me for my poor english

When I adb into a device with Cyanogenmod, I'm presented with a nice bash shell, color prompt, and bashrc. I don't see a symlink from /system/xbin/bash to /system/bin/sh. How do they set the default shell to bash instead of sh? I looked through rc files, but didn't find anything. I'd like to do the same on my Android build, which isn't Cyanogenmod. **Update** After re-installing from scratch with CM7, I'm taken to sh instead of bash. Now the question is how to set bash as default.

I try to login in my device directly vith adb shell bash -i It kind of partially works, because I'm logged with [tag:bash], but the terminal loose completion. The error I get: $ adb shell bash -i bash: cannot set terminal process group (-1): Not a typewriter bash: no job control in this shell mydevice / # Is there something possible to do it properly without errors ? I don't have su installed.

You can do adb shell pm list packages, and after reading through the list, do an adb shell pm path "com.yourpackage" to get the full path and do a simply adb pull. Fact is: I want to automate this. I thought about a really simple bash script: for apk in $(adb shell pm list packages | sed 's/package://g' | sort); do # If you just do an echo, IT WORKS # echo $apk # But here it doesn't work adb shell pm path $apk done But that simply doesn't work. It seems that "$apk" becomes *lost* or something and nothing is shown in that snippet. I don't know if it's a subshell problem, or some peculiarity when using variables that got through an adb shell. Should I create a script apks.sh just using pm list, for and such, push it to my device, run adb shell only once and execute apks.sh?

I would like to execute a script at logout with my GS7 android 9 (Resurrection Remix). I see that it is advised to use tasker. I guess it is possible to do that without installing a graphical application. I connect to the smartphone through adb and have a shell. Where can I write a file in the file system with bash or python commands that will be executed at logout ? Also, how should I manage the bash or python environment in order to have it working ? Thanks for your time.

The script is here: https://github.com/Magisk-Modules-Repo/com.piyushgarg.rclone/blob/master/binary/syncd.sh The code that I do not believe is working is this:

while true; do
    if [[ ! -e ${SYNC_PENDING} ]]; then
        ${HOME}/inotifywait "/storage/emulated/${PROFILE}/${SYNCDIR}" -e modify,create,moved_to,close_write -q >> /dev/null 2>&1 && touch ${SYNC_PENDING}
    fi

When I execute the inotifywait binary as a standalone, I get this message: > CANNOT LINK EXECUTABLE "inotifywait": library "libnotifytools.so" not found. Does this indicate that I am missing a library? How can I solve the issue?

I'm installing legacy Termux on an Android 6.0 device. I downloaded the legacy app- and the legacy packages. There is a txt file with all the symlinks that need to be created. I'm looking for a way to make all the links in one batch run. Either with bash or some other way. This is the format that the file is in

-open←./bin/xdg-open
gawk←./bin/awk
dash←./bin/sh
xzgrep←./bin/xzfgrep
xzdiff←./bin/lzdiff
xzgrep←./bin/lzgrep
xzgrep←./bin/lzegrep
xz←./bin/unxz
xzmore←./bin/lzmore
/data/data/com.termux/files/usr/bin/bzdiff←./bin/bzcmp
/data/data/com.termux/files/usr/bin/bzmore←./bin/bzless

I searched around on the net and have only found a way to make links from one folder with many files to another folder with the same names of the files. but as you can see from the sample above I need different names and also different folders. Thank You

I use Termux on my Fairphone 2 and I want to speed up working with it. What slows me down is not having an up arrow key that I can use to access the last command in my bash history. I can do !! !7 and so on, but most of the time I don't want to actually repeat the commands, I just want to do something similar. I know some keyboard shortcuts to work with my bash history but they require a ctrl key, which none of my keyboards have. I use - AnySoftKeyboard - Hacker's Keyboard - AOSP Keyboard None of them have up arrow or ctrl keys At the moment, I select and copy text by touching, but this is still slow. How can I access my previous commands more quickly?

I'm using an Odroid (rooted) device running Android 5.1.1 on a local network and I'd like to be able to control it via adb. Currently I'm running this at startup: setprop service.adb.tcp.port 5555 stop adbd start adbd This works initially, but I've noticed if works with one connection at a time. If a connection is left open, a second connection won't work. Even though adb says I'm connected, whenever I try to run any command I get an error: > adb connect 192.168.0.33 connected to 192.168.0.33:5555 > adb shell date error: device offline What's the easiest to ensure adbd is accessible, even if a connection is left open/hanging by accident ? I'm thinking about running a script that periodically restarts adbd but having a short interval will be very frustrating as I'd need to constantly reconnect. Is there a way to check if a connection is open, but hanging ? (no data has been received in a while ?) Alternatively, would it be possible to close the previous connection if a new one is made automatically ? How would one keep an odroid connectible via adb constantly (regardless of open connections ?)

# Short version: **Why is my bash script (running in the background, started via SSHD) not running every ~30 seconds when it should?** (NOTE: SSHD and the script are running as **root**!) ---------- I have a script that I start using nohup bash script.sh & so that it runs in the background. The script is supposed to check whether a specific app is connected using netstat and if not it automatically reconnects using am start and input keyevent. (This turns out to be irrelevant though). I've noticed that even though the script should check every 30 seconds (roughly of course), sometimes it takes minutes to check. I couldn't really figure out why and it seemed completely random (note that the phone's screen is off most of the time and everything is running in the background.), so I made a testscript which is what the question should focus on for simplicity: #!/bin/sh while : ; do echo "$(date +'%Y-%m-%d %H:%M:%S')" sleep 30 done That's it. Started via nohup bash script.sh & using SSHD. The script does nothing but print the current datetime and thanks to nohup writes it to a file. I left this running for a while and then wrote another script to check on the results and print the amount of seconds whenever it's above 30. Result: 134 127 115 127 88 113 116 99 110 116 54 44 70 75 62 82 94 68 429 62 81 126 144 39 467 71 62 This is from the output of a script that ran for only 4:20 hours, so quite a lot of times where execution must have been delayed, the sleep was longer than 30 seconds, or whatever is going on.... Can someone explain this? And is there a solution to this? I suspect this might have something to do with memory or power management pausing the script but really it shouldn't happen and I would like my script to run in the background and to sleep for exactly 30 seconds and not be paused or delayed. In this testrun, the highest was 467 seconds, but the highest I've seen with the main script so far was a little over **20 minutes**. This is rare, but 5-10 minutes of a delay happens a few times a day.

Android 8.1 PIXEL 2 with root access. I have seen this asked here once before but the only solution didn't help me at all. I am going to try and make this as simple as I can for the example. If I run the following command in terminal emulator or adb shell: am force-stop com.myapp.frustrated It will quit the app just fine. But when I run it in this shell script: #!/bin/sh am force-stop com.myapp.frustrated Nothing happens. It is odd to me that I can do many other commands just fine in a script, but a handful of them do not work. Any suggestions you have are much appreciated.