[UPDATE]
BusyBox 1.19.2
Bash 4.2
Midnight Commander 4.8
TMUX 1.5 - That's right, full terminal multiplexer..
Vim 7.3
Terminal IDE ASCII Soft keyboard first round bug fixes complete.
It's the addition of TMUX and MC that really excites..
--------------------------
Well,
As the only people I know who might even be interested in this, I would like to announce the release of Terminal IDE v1.0.
A complete Java / Android Development Environment that runs on the device itself, with a nice telnetd / sshd feature.
For Android. Of course... Eat this you IPhone Hounds..
Woo HOO!!
The application is available on Android Market.
https://market.android.com/details?id=com.spartacusrex.spartacuside
As what I can only describe as 'dark days' finally draw to an end, I am very pleased with this first draft.
PLEASE give it a go, log in over telnet for a smoother ride, and let me know how it goes..
DO THE TUTORIAL! Does it work ?!
I have released the whole project GPLv2! Yeah, Who Knew!?
http://code.google.com/p/terminal-ide/
BOOOOOM!
Spartacus
a link to the app in the market would be usefull.
Interesting. Was just wondering about coding on my tablet.
Pretty freakin sweet
Thanks for putting this out!
Awesome
The full keyboard alone makes it worth downloading, but the IDE as well - wow!
this is best bro.
I randomly found this last night while looking for a decent mobile IDE for my tablet. I was looking for a simple text editor with syntax highlighting and you've taken that extra step to include other tools for ssh, telnet and compilers. Much appreciated.
One question, how do you start the ssh server? sshd doesn't seem to do it. I would like to scp files to my device from my desktop in order to work on my commute.
Thanks
The sshd app is actually called Dropbear.
You also have Dropbearkey.
You use Dropbearkey to generate the sshd certificates you need.
I really need to add a tutorial on setting the sshd keys up
For now Google has a couple of articles on it.
For file transfers you also have busybox FTP but I admit not terribley secure..
Allthough SSH is provided, and I wonder whether an SSH pipe can be created..?
And lastly you can just copy the files over to your sdcard via USB..
Will look into it & add tutorials asap.
Ok. So I now have SSHD working..
But there is a slight issue.. basically when you log in you have to start bash manually.. unless you have the file /etc/shell with the correct shell to use.. Which requires a rooted phone.
Since Terminal IDE is for non-ROOT users, I will have to recompile the code to allow a shell to be specified on the command line.. Soon..
FOR NOW - This is how to connect to the phone via SSH (There are other ways using public keys but this is one way)
So - Once in Terminal IDE
2) You need to create a couple of server ssh keys
Start in $HOME
Code:
cd ~
Create folder
Code:
mkdir .ssh
Give it some secure permissions
Code:
chmod 700 .ssh
Get in there
Code:
cd .ssh
Now create the keys
Code:
dropbearkey -t dss -f dropbear_dss_host_key
dropbearkey -t rsa -f dropbear_rsa_host_key
ok - That's almost it. Just need to start dropbear with the correct parameters now. [Probably want to keep this in a script]
Back HOME
Code:
cd ~
You need to know the UID of your app, which is different per phone - use 'id'
Code:
id
That will tell you your user ID / Group ID. Let's say its 10058.
Now to start DropBear
Code:
dropbear -A -N username -U 10058 -G 10058 -C password -d ~/.ssh/dropbear_dss_host_key -r ~/.ssh/dropbear_rsa_host_key -F -E -p 8090 -P PidFile
This will start it running in the foreground with password set to 'password' on port 8090.
Then you can connect, like telnet, and simply use 'password' for the password.
Now for the issue. It will start a simple shell session in / with no ENVIRONMENT variables or anything..
I'll fix it permanently in a future release, but for now it can be fixed with these 2 commands.
cd into your home dir - Check this is correct on your device
Code:
cd /data/data/com.spartacusrex.spartacuside/files
And start bash with an init file Terminal IDE auto-magically creates..
Code:
./system/bin/bash --init-file ./.init
Everything should now be setup as usual.
Good luck..
Very awesome and thank you sir. Works like a charm.
One thing to clarify for those "braving" this (not that it's all that insane to try)... the '-N' is setting the username (in the case of the example, setting it to 'username').
Also, it gives a permission denied for scp, I'm assuming since it doesn't init/run the shell. Should be fine since FTP is included. Haven't tried this option yet. Not too worried about security at the moment, since I'll only run it on a private network.
May I make a (maybe) small feature request? Is it possible to include a "keep screen awake" option in the options menu? I have my Xoom config'd to turn off the wifi when the screen is off for power saving (can go ~4 days on 1 charge), so it will kill my connections if I let this happen. I know not everyone has this config set, but it'd be a nice option.
NOW, if I wasn't lazy, I could probably add this myself and build since I've dl'd the source. But, lazy and working on a few projects already.
Again, much thanks.
And as if by magic..
Funnily enough I was having the exact same issue last night while using wget to transfer a big file to my device..
NEW VERSION UPLOADED v1.13
Now has 3 non-exclusive lock types available in the options :
- CPU Lock
- SCREEN Lock
- WIFI Lock
Set them as you wish...
Saw that this morning when I was on the bus (Thursday morning here in Hong Kong). Very awesome and much appreciated.
As well, thanks for open-sourcing it. +1 for you sir!
Very cool stuff
Thanks for creating this.
Great app! However I can't compile .java files. I always get an error that it can't unzip a file in /android.policy.jar. Any idea?
Sent from my GT-I9100 using XDA App
Do you think its possible to also support compiling C sources directly in your phone
I've been searching for this ever since I got an android.
THANK YOU.
Says that it's incompatible with my OG Droid. Any idea why?
shpen said:
Says that it's incompatible with my OG Droid. Any idea why?
Click to expand...
Click to collapse
Most likely seems to be due to the ROM you are using and/or the market version
can u post the build.prop here?
/system/build.prop
also, try going back to market 2.x, 3.x market(s) do loads of checks
Does anybody know why I can't compile java files? I always get the following error:
Error reading /system/framework/android_policy.jar cannot read zip file.
Any ideas? Could anyone upload there android_policy.jar because that might cause the error.
Sent from my GT-I9100 using XDA App
Hi Schindler33.
Can I ask, have you followed the tutorials, say the first helloworld example TO THE LETTER?
Does the helloworld example work?
The parameters have to be correct, and as always exact, and the BOOTCLASSPATH variable must be set.
If so, is it a custom ROM?
Does that policy jar file exist and is it readable by non root users?
As much info as possible good..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Background:
It all started with me often finding myself sending small files to my device, and quickly got sick of the constant enabling/disabling of USBMS on my old phone, which is quite slow with re-mounting the SD card(ZTE Blade).
I also quickly got sick of not being able to quickly transfer files from my PC to my tablets internal storage.
There are a few graphical interfaces for adb out there, but none was really what I wanted...
So I decided to attempt to code something myself, and here we are!
Info:
A graphical UI for "adb push" to quickly transfer files from your PC to any location on your Android device.
.... Thats what I planned when i started, and what the first 2 versions did...
Now it hosts a powerful File Explorer thats capable of doing everyday tasks such as copy, paste, rename, create folders, delete files and folders, as well as transfering files on its own.
Features:
The main application is capable of sending and receiving files, and installing APKs.
It also serves as the connection-manager as can connect to devices using either your USB Sync cable, or by using WLAN (req. an app on your device to enable wireless adb).
Finally, it hosts a few other functions such as reboot to recovery, reboot to bootloader and a plain reboot.
The Filebrowser is very similar to any other filebrowser you use everyday on your PC.
It can copy/cut and paste files and folders within the device, rename file and folders, create new folders, delete files and folders.
Highlights would be:
Browse the content of your device like you browse your PC's harddrives
Drag and drop files between your PC and your Android device
Move, copy, delete and rename files and folders
Limitations:
The main program does not detect case sensitive, which can end up with funny results if you push a file to "/removable/" instead of "/Removable/" for example.
ADB is only capable of sending 1 file at a time, but is capable of sending whole directories incl. subdirs.
In a future update, I will add the ability to send multiple files.
Getting started:
Everything should be self explanatory. Most of the buttons have tooltips that tells you what they do.
Basically you make sure USB Debugging is turned ON on your device, plug it into your PC and start Quick ADB Pusher.
If you are connecting using a USB Cable, the application should find it automatically.
If you're connecting through wifi, you will need to type the IP address in the dedicated field. Port only needs to be provided if you are using any other port than the standard 5555. The IP address will be saved, and you can select it from the drop-down list the next time you start the application.
Requirements:
An Android device.
Windows
.NET 3.5
USB Debugging turned ON.
Additional Recommendations:
Root
Busybox
Vulnerable Kernel or Custom ROM
Q&A
Q: My device is rooted, but the program says it cant get root access
A: You are probably on stock rom or kernel. Most shipped roms have root-access from adb blocked.
To check this: Open default.prop located in the root of your device ("/"). If ro.secure is set to 1, thats your issue. Note: Default.prop gets overwritten everytime you restart the device, so changing this file will do nothing.
Theres is an app available that can fix/bypass this: http://forum.xda-developers.com/showthread.php?t=1687590
Q: The cache didnt delete itself when I closed the app!
A: You have two choices here: Either delete the cache/ folder located in the same location as the adb pusher exe, or you can just open and close the program.
If the cache still wont delete itself, report it as a bug.
Q: I cant connect to my device over wifi!
A: Make sure you have an app on your device that enables wireless ADB and that its turned ON. I personally use adbWireless found on the Play Store.
Double-check you are attempting to connect to the correct IP and port.
Q: Whats the "Information" window good for?
A: Its actually a left-over debug window, but can provide you with useful information should a transfer fail. If nothing else, you can use it if and when you report a bug.
Note that the Info window only shows what the main program is doing. ADB Explorer works independently, and will not report anything to the Info window.
Q: Why do I have to click a button to switch between push, pull and install?
A: The program need to knows which adb command to run (adb push or adb pull), and having a button for it was the easiest way for me .
The install option is there because you might not always want to install an .apk, but rather store it on your SD card or something. I know I do.
Q: Why cant I send a whole folder to my device from the main program?
A: Old implementation, use the built-in ADB Explorer instead, which allows you to send whole folders.
Q: Whats the point in the main program, when the Explorer can do everything but better?
A: At the moment it still controls the actual transfers as well as the connections to your device(s).
The main program is, however, more or less untouched since v0.3, while the Explorer is constantly being updated. Therefore, the Explorer hosts more and better features.
I am concidering removing the main form, as its rather obsolete by now.
Q: I Have a question!
A: Feel free to ask in this thread, and I'll answer your question as best I can.
Q: Can I donate?
A: No, I dont feel this program is worth "paying for" and it wouldnt feel right to receive money for it in any form.
Hit 'thanks' and vote the thread 5stars instead
Q: I Found a bug, how do I report it?
A: Report it to me on this forum, either in the thread or through PM, and I'll make sure to look into it.
Just make sure to provide as much info you can.
And remember: I cant fix anything if I dont know about it! So dont hesitate reporting bugs.
Changelog:
v0.5 current version
First of all... v0.4.1 had 6570 views on the attachement alone. Not bad... :victory:
Added an awesome splashscreen! As those who have used this program before should know - the program takes a while to load. The splashscreen is visible during this load, so you know the program is actually starting.
The wifi-field has been redesigned. It now saves your IP adresses so you dont have to retype them every time.
Added an "X" button next to the wifi-field. This button clears the wifi-cache and removes all entries in the list.
Added my name with a link to this thread, Ive seen my program hosted at a few sites with no credit whatsoever. I dont mind anyone hosting it elsewhere, in fact Im happy it gets spread, but PLEASE at least give me credit for it.
Slight redesign
Added tooltips to both the main application and the Filebrowser
Filebrowser:
Renamed "ADB Filebrowser" to "ADB Explorer". It can do so much more than just view the files on the device, so this name is more fitting. I should think of a new name for the entire application as well... "Quick ADB Pusher" isnt even half the truth anymore
Added cache feature! Everytime you enter a directory youve already been in, the cache kicks in rather than asking the device for the content. Each device has its own cache (note: a wifi-connected device will have its own cache based on the IP, so if you connect to the same device using cable or another IP, the cache needs to be rebuilt).
The cache will update as follows:
When entering a new directory not currently present in the cache.
When you hit the refresh button.
When you rename a file/folder.
When you create a new folder.
When you paste a file/folder from the clipboard.
When you delete a file/folder.
When you transfer a file/folder to the device.
The cache will NOT update when you send a file from the device to your PC
The cache will get deleted upon application exit.
You can now cancel the contentlisting and go back by hitting "../", Backspace shortcut-key or the Back button. Added because some directories takes ages to load on various devices, and its not so fun rolling your thumbs when all you want to do is go back to the previous dir
Added "drag-drop" to the filebrowser - you can now dragdrop files and folders directly to the browser to send it(or install, if .apk) to your device. The cache will refresh upon completion. You can also drop files and folders FROM the browser to your PC!*
* this might not sound so special, but it was a ***** to implement. Dragging stuff to the browser - ~50 lines of code. Dragging stuff FROM the browser - a little over 200 lines of code... C# sure has its limitations...
Added "Grab" to the right-click menu. This will send the selected file/folder from your device to your PC.
In short, the filebrowser can do what the main application can, so you dont have to close the browser to send/recieve a file/folder. A loading thingy will appear over the browser while a filetransfer is in progress.
Added "Properties" to the right-click menu. This shows some info such as the size of the file, and even the total size of a folder (incl. sub dirs). If you select a folder with a lot of content/folders, it might take a while to calculate the size. Other things it show is where its mounted and what permissions the file/folder has. NOTE: Requires Busybox, and root for files and folders only accessible by root (duh!)
Added 3 warnings upon opening the browser: One to inform you if your device isnt rooted, one to warn you busybox is missing and one to warn you if your device is rooted, but ADB was unable to acquire it. None of these warnings will show if adb acquires root and busybox is present.
Added a textarea showing the used space on the device, based on the mounted partition (such as /data, /sdcard, etc). So dont be scared if the number jumps around while youre browsing - it just means youve entered a different partition. Click to switch between used and free space. Requires Busybox
The browser now remembers your last location and will not start from "/" everytime you open it. Memory is lost upon main program exit and when you select a different device.
Added "View file" (prev. unfunctional "Open" menu item) to the right-click menu. This allows you to view smaller files (up to 10MB) without permanentally save them on your PC. I have blocked larger files because the time it takes to transfer those files isnt worth it for just "a quick look". My devices transfers a 10MB files between 2 and 5 seconds(depending on device) - which I think is ok, so I set the limit there.
Tweaked and tuned to make the browser act somewhat normal for devices without root/busybox. Devices without root/busybox will miss out on quite a lot though And before anyone asks - No, I do not plan on making this program able to root your devices. There are plenty of tools for that already.
Fixed the shortcutkeys that only worked when they wanted to. In addition, several more shortcuts have been added.
List of currently supported shortcuts:
ctrl+x: Cut file/folder
ctrl+c: Copy file/folder
ctrl+v: Paste file/folder
ctrl+s: Grab the selected file/folder
shift+delete: Delete the seleceted file/folder
shift+n: Create a new folder
F1: View file
F2: Rename file/folder
You can also use the arrowkeys to navigate, similar as in explorer. cut/copy/paste only works within the ADB Explorer.
Added Forward and Back buttons. Works the same way ordinary back/forward buttons do. Also changed icon for Refresh
Added a Toolbar, containing more buttons such as "view file", "download", "upload", "delete"...
Added 2 eastereggs , one is easy to find. The other is well hidden, and actually serves a purpose Well actually, the latter isnt really an easteregg, but it should be hard enough for you mortals to find
Known issues:
You friends might rage and throw their IPhones at you when they see this
------
HTC Sync REALLY doesnt like ADB, so close that crap before starting this app, or better yet - uninstall it!
It seems HTC Sync is trying to start its own adb server, and is very persistant in doing so.
This results in Quick ADB Pusher and HTC Sync having a fight for their life on who is going to start the server.
------
If you install an .apk, then try to send something else, the program will try to install that as well. This is because I was retarded and forgot to add one check.
Solution: Close the filebrowser, untick "install apk". Will be fixed in the next version, I promise! :angel:
Version History:
v0.4.1 - 6570 views on the attachement alone. Not bad...
Fixed filebrowser not working on some devices, I hope. Please test this for me as the browser has always worked fine for me on all my devices.
Changed apk install method to use AndroidLib's method. It now tells you if the installation was successful or not.
... Some minor things I cant remember.
Note, the "Open" option in the filebrowser is just a placeholder for now, its not a bug that it doesnt work, it isnt ment to work.
v0.4
Fixed bug where files and folders containing "_(" threw a syntax error.
Added file browser for device (see Seperate notes).
Added wireless ADB support.
Added Pull-file mode.
Re-designed the UI.
Moved the info-view to 3rd tab. Im moving away from it more and more.
A lot of the text and button-text will now change depending on your current choices. Ex. the Send-button now switches between Send, Pull and Install.
A truckload of code rewriting and optimizations.
Added an additional check for Root remounting, which should fix rare cases where remounting fails (If your device cant be remounted as root, please report it along with your device, rom etc)
Added "Install APK" You can now install APKs directly through the program.
Added reboot options in the Advanced tab
Added device info in the Advanced tab (The temp seems to be reported in C * 10, so I report it as C / 10, let me know if it doesnt look right for your device, and dont forget to tell me what device/rom you're using)
Filebrowser Features:
Browse and select files.
Context menu (right-click menu).
Copy or move(cut) files/folders within the device.
rename files/folders on the device.
delete files/folders on the device. Warning: Deleting the wrong files might brick your device! Double-check that you really want to delete the file before doing so!
create new folders on the device.
icons for certain formats (more to be added).
progressbar for directory loading progress.
'clipboard' icon to remind you what you currently have selected for copy/cut.
Notes:
The filebrowser is in its early stage. I have bugtested it as much as I can and it works flawless with my 3 devices.
The speed of listing directoiess/files greatly differs with device. My TF101 lists the contents about twice as fast as my ZTE Blade, theres not all that much I can do about it, as I dont have the time right now.
When pasting a file in a location where a file with the same name already exists, the program will currently simply overwrite the file. I havnt had time to add a check for it yet (ETA: Next version).
---To be added:
Direct interacting/editing of files, such as text files etc.
cache-feature, to reduce the frequency of grabbing the dir. contents from the device (which will help speed up changing paths).
A "file exists" check when pasting, allowing you to chose to overwrite or rename the old file.
v0.3
Fixed program freeze when no device was connected.
Added device selection, so it should work with multiple devices connected. please test this for me
Rewrote most of the program to make use of AndroidLib.dll
Removed the console(debug) tab, as it served little to no use now
Added an 'Advanced' tab for future use
Cleaned up a lot of garbage code
Fixed system not mounting as R/W
Other minor changes and fixes
v0.2
First public release
v0.1
very first version I wrote, which was buggy and often froze and god knows all...
Trust me, it was terrible. It worked and did what it set out to do but... It was terrible...
The latest Version has been tested and bugfixed on the following devices:
ZTE Blade with Swedish Spring 5, connected through USB Cable
ASUS Transformer TF101 with Team EOS Nightly build 28, connected through WIFI
HTC One S with stock 4.0.3, no root, no busybox. USB Cable
HTC One S with stock 4.0.4, root, no busybox. USB Cable
HTC One S with stock 4.0.4, root, busybox. USB Cable.
-------------------
Suggestions for improvements, feedback etc are more than welcome
Thanks to:
regaw_leinad - for writing the very handy AndroidLib found here
Dont forget to hit 'thanks' if you like my application. Every thanks I get brings a smile to my face
Download:
If the attachment doesnt work, try this mirror (select version and hit ctrl+s, or file -> download)
i think making a batch file was easier
Hey, cool app. There does however seem to be a problem with XDA's attachment feature, and it only downloads about 1k of the zip, then says complete. Also, if you plan on extending this a little more, check out my .NET Android Library named... well AndroidLib. It will help you out a bunch with the coding of the features you want to add.
regaw_leinad said:
Hey, cool app. There does however seem to be a problem with XDA's attachment feature, and it only downloads about 1k of the zip, then says complete. Also, if you plan on extending this a little more, check out my .NET Android Library named... well AndroidLib. It will help you out a bunch with the coding of the features you want to add.
Click to expand...
Click to collapse
Thanks for the heads up.
I placed it on google docs, hopefully it works better
Linky
If it doesnt, perhaps you could give me a tip as to where to upload it. I used to have my own server so never really used any other file-sharing method
regaw_leinad said:
Also, if you plan on extending this a little more, check out my .NET Android Library named... well AndroidLib. It will help you out a bunch with the coding of the features you want to add.
Click to expand...
Click to collapse
O nice, Ill definitely check that out Thanks.
Goatshocker said:
Thanks for the heads up.
I placed it on google docs, hopefully it works better
Linky
If it doesnt, perhaps you could give me a tip as to where to upload it. I used to have my own server so never really used any other file-sharing method
O nice, Ill definitely check that out Thanks.
Click to expand...
Click to collapse
Yup, the new link works great! Unfortunately, when I don't already have an adb server running and hit the 'Check ADB Status' button, the form freezes and the process needs to be killed to close the program. Works fine when adb.exe is already running though.
---------- Post added at 12:26 AM ---------- Previous post was at 12:17 AM ----------
Killing adb.exe while it's frozen fixes the issue I pointed out, probably means there is an error in your
Code:
Process
code
EDIT:
Stalls on process.WaitForExit() when debugging
regaw_leinad said:
Yup, the new link works great! Unfortunately, when I don't already have an adb server running and hit the 'Check ADB Status' button, the form freezes and the process needs to be killed to close the program. Works fine when adb.exe is already running though.
---------- Post added at 12:26 AM ---------- Previous post was at 12:17 AM ----------
Killing adb.exe while it's frozen fixes the issue I pointed out, probably means there is an error in your
Code:
Process
code
EDIT:
Stalls on process.WaitForExit() when debugging
Click to expand...
Click to collapse
Thanks for the report,it seems to happen when theres no device connected. Silly me have only even tried the app with a device connected hehe.
I'll try to fix it later today
Goatshocker said:
Thanks for the report,it seems to happen when theres no device connected. Silly me have only even tried the app with a device connected hehe.
I'll try to fix it later today
Click to expand...
Click to collapse
ah, you're calling
Code:
adb get-state
that gets the state of the device connected.
My .NET Android library handles everything adb wise, it even uses it's own adb binary, so the user doesn't have to have the sdk for it to work. let me know if you're going to reference it with your app, and I'll put your project in AndroidLib's post of "Projects using AndroidLib"
regaw_leinad said:
ah, you're calling
Code:
adb get-state
that gets the state of the device connected.
My .NET Android library handles everything adb wise, it even uses it's own adb binary, so the user doesn't have to have the sdk for it to work. let me know if you're going to reference it with your app, and I'll put your project in AndroidLib's post of "Projects using AndroidLib"
Click to expand...
Click to collapse
Yep, I assumed that would work since it works fine if you do it directly in cmd. But guess not adb start-server didnt work either...
I think I'll leave the bug for now and start looking into your lib instead.
Really nice app
Do you plan to develop a Linux version ?
Great idea, thanks =)
How does it achieve rw access, since device-dependent?
For example, on some devices, in ADB shell, you use
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
But, in some, you use mtdblock3 instead of mtdblock0.
Since there's no setting on which mtdblock to use, how does the program know which one is correct?
Theonewithideas said:
How does it achieve rw access, since device-dependent?
For example, on some devices, in ADB shell, you use
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
But, in some, you use mtdblock3 instead of mtdblock0.
Since there's no setting on which mtdblock to use, how does the program know which one is correct?
Click to expand...
Click to collapse
adb remount does all the job as you are ultimately using adb..
the command which you specified is used to mount on device shell which you enter by adb shell
madman_amit said:
adb remount does all the job as you are ultimately using adb..
the command which you specified is used to mount on device shell which you enter by adb shell
Click to expand...
Click to collapse
Oh, so that's what it does! lol
Thanks.
Actually, when trying it out, it says, after starting daemon "remount failed, action not permitted"
Nevermind, will check the program, it seems easier...
Looks cool! I shall give this a try later and see how it does with my HTC Rezound.
Thank you for your work!
Wow, responses
Thanks for the feedback guys.
Unfortunely Ive kinda killed my sync cable for my TF (tried to convert it to a usb host adapter^^), and currently dont have any other android device to play with.
So development has kinda stalled right now. Ive got rid of the freeze-when-no-device-connected, but developed another issue instead. Not anything major, but very annoying. The app freezes while it checks for a device >_>, its only for a few seconds, but annoying nevertheless.
As for linux version... Im afraid thats way above my coding skills, and I dont have a linux PC to test on anymore (I killed the laptop which was running linux when I tried to build a touchscreen on it. Yes! I break a lot of things)
Awesome, just what I needed!
Could you please add an option to connect the phone using network?, with the "adb connect" command, I can use a bat file before starting the app but because I have several devices connected to the network the phone´s ip change in time, and having it built in the app would be great
Awesome work, just tried it out now and it's pretty awesome.
I think an adb connect option would be awesome, for those who have adb wireless app on there phone then it'll be really easy to transfer files and it'll be pretty sweet.
Anyway keep up the good work
Hey, just an fyi,
Code:
adb remount
will NOT work if the device connected does not have the option ro.secure=0 in the default.prop of the ramdisk. You shouldn't assume it does, because not all "ROM" developers know how to change it. My library does check for this, but in case you don't want to use it, be sure you can mount the filesystem /system as rw that way, or using the mount binary on the phone directly.
regaw_leinad said:
Hey, just an fyi,
Code:
adb remount
will NOT work if the device connected does not have the option ro.secure=0 in the default.prop of the ramdisk. You shouldn't assume it does, because not all "ROM" developers know how to change it. My library does check for this, but in case you don't want to use it, be sure you can mount the filesystem /system as rw that way, or using the mount binary on the phone directly.
Click to expand...
Click to collapse
Hey thanks for the info. I had no idea about that, remount have always worked on all my devices on all roms Ive tried.
I'll keep that in mind when Ive fixed my sync cable
Could you give an example of a device/rom combo remount does not work on?
Goatshocker said:
Hey thanks for the info. I had no idea about that, remount have always worked on all my devices on all roms Ive tried.
I'll keep that in mind when Ive fixed my sync cable
Could you give an example of a device/rom combo remount does not work on?
Click to expand...
Click to collapse
I can't think of a specific example, but if the developer does compile a boot.img with ro.secure=1, adb remount will not work but lots of 'devs' these days just grab the boot.img from people who actually know what they're doing, so you should be ok, just in rare cases, this will not work.
[Toolkit][Windows&Linux(Wine)] Already Setup Adb/Fastboot Environment and Installer
First, I take donations.
Second, see the 2nd post about Windows XP compatibilty.(XP requires that the tool be used on a usb drive or a partition that does not contain the current running operating system)
(For the other OSs it works fine on the drive with the running OS) (For Linux see the last post)
Third, XP users that don't have a removable drive available can use the XP-ONLY version on the local drive.
Fourth, read EVERYTHING here on the first and last post.
Fifth, adbClient is a download, unzip, connect to phone package that requires nearly no setup at all allowing you to use the android debugging bridge.
If you want to install adb and fastboot use the "instadb" command.(If you get an access denied error, you must have the administrator password and check your typing)
ANSWERS TO YOUR PROBLEMS:
If you want to update but continue to keep automagically using your work folder: you must copy the Work folder into the folder above the updated bin folder.
Like so: extract the new package. copy the old work folder into the new extracted folder. your work folder should sit right beside the launchadbclient script and the updated bin folder.
This tool can be moved anywhere alongside the work folder
HOW TO USE:
To launch the script extract the zip and run LaunchadbClient by double clicking on it.
Type "xt" without quotes to see a menu for commands.
Check out some package management by typing apk.
To install adb and fastboot to the system without fiddling with environment variables use the instadb command.
DRIVERS:
Visit this link first to enable usb debugging:
To utilize the Google usb driver extract its zip and right click the android_winusb.inf file and hit the install option.
If Google's drivers dont work or you have no drivers or adb doesn't mention any connected devices at the top of the window then you need to visit your manufacturers website for your phone's driver.
Here is the pdanet all purpose adb driver that is pretty much fail proof. if you have any issues with it uninstall it and try another one from below.
If all three of those driver suggestions are not applicable then read the "OTHER DRIVERS" category:
OTHER DRIVERS: The Universal Naked Driver is a good one. Or you can follow this exceptional tutorial for all purpose adb driver installation (I am not responsible for any issues with the tutorial, I just found it.)
I recommend Adb Konnect from the play store if drivers are a problem.
Sometimes your usb cable is keeping you from using adb, so try changing cables.(this actually just happened to me with my samsung usb cable and i ended up using my nexus 7 one instead)
DESCRIBE THE TOOL:
This tool is here to make my life(and your life) with adb easier.
It's the windows command line on steroids.
It is made for being put on a flash drive and being used on different computers.
Especially if you are using someone else's computer but want to keep an environment with your tools and files in it where you could just load it up from a flash drive.
It uses shortcuts for tools including and can autoroot etcetera among other features. This tool is free to use and distribute\modify with my name attached. It contains a presetup adb and fastboot environemnt and has extra binaries\scripts for working with the windows command line and android easier.
Overall it makes interfacing with android over adb much more interesting.
GETTING THE TOOL AND INFO:
1.9.5-XP_ONLY is for the Windows XP desktop only.
Version 3.2.9 is the latest stable release, Use this version please. Thanks for your interest.
If you want to take a snapshot of the latest development go here.
ANNOUNCEMENTS: I now have a donate button if you want to see more development.
I don't support 2.2 or 1.9.5 anymore. Only 3.x.
KNOWN ISSUES: tar might not work.
apklist won't auto exit because of the more pipe. just use control-c for now to unfreeze it
Some of the scripted adb commands stall.
EXTRA INFO:
The only thing that I own in the zip is the scripts. The copyright notice and license for android sdk and included files is included as Notice.txt and Noticeforadb.txt in the LicenseForAdbEtc.zip
With this tool their is no need to install adb or fastboot on your computer just run the script.
If you get an antivirus warning its because of the Zergrush, Psneuter, Framaroot, and ExynosAbuse root exploits.(And the Hstart binary sometimes)
I am not malicious anyway.(You can read my code easily)
You can copy the folder wherever you want. (I made sure it works)
Just don't have anything named bin in the same directory as the launch script.
EXTRA EXTRA INFO:
This tool is meant to be an extension to the command prompt and will pass anything that it doesn't understand over to the command interpreter.
It works in Wine. Extra launching needed. (See last post)
This is a tool for beginners and advanced users however beginners need to learn adb's commands before using this tool.
It will root 2.x and up(Support added for newer android versions). I suggest installing Supersu also.
Tool works on all windows versions: Wndows XP and above.
You are no longer encouraged to use the XP only zips for Windows XP.
For XP: If you use the tool on the local drive it throws errors however if you use it on a usb drive then it works fine
If you need to use it on a local drive then you can use the old win xp only version.
Windows 8 and 8.1 run the tool perfect.
Use the exit command to exit the tool.(It auto kills the adb server)
Links to third party tools used or included:
Recommended download: ApkMultiTool. Another recommended download: Mediatek flashtool
Framaroot
Exynosabuse
strace
Android Sdk
Stahlworks Binaries : Open source
Win32 Busybox Binary(pclouds) REPLACED WITH Tigress busybox
Freac Not in Slim builds.
Stericson Busybox Android Binary
Sqlite3 android
Supersu
Hstart for use with startup sound
This info applies to testing, finals, and anything else.
FUTURE CHANGES:
Code:
add start settings app and browser app command using am start
add intent disabler (Disable an app's MAIN so that it can be hidden from drawer and be unstartable "locked" )
add the ability to make img of a specified size and store it in /data and even loop mount it to sdcard
add the ability to live image the system and data partitions.
remember to make the user specify the filesystem for sdcard image
I need to backport all bug fixes and improvements to 1.9.5_XP-ONLY
use vbscripts to automate key sends (control-c) Not done due to batch sucking.
add su -c sh to start up root shell on device for use with things like strace. Not done due to batch sucking.
add if blank adb devices say you must connect with either cnt or plugging your device in. (But still show the output)
add variable for work folder
Migrate all custom data text files(hist,clr) to config folder in Work\ but keep defaults in regular bin folder.
add adbkiller script to the desktop by question on first startup.(Store info text file in userbin) (User variable then desktop)
clean output on adbp and adbps plus
change all du -smc to du -sm for single push/pull
add ability to do several pushes and pulls with du -smc in one operation
add parameters to adbp and adbps
add if not defined to destination and source file in adb and adbps to allow for hitting enter to quit in the middle of setting up a push or pull
cleanup and organize xt
include some sort of nano for windows binary for command line editing
include a compact notepad++
Remove extra binaries such as zip and unzip to point to busybox linkers (Skim through code to change "zip" to "busybox zip" or "sfk zip")
Pass all inputted commands to a script that can parse arguments before they are sent to they're respesctive scripts or binaries. (Mostly to catch /? and run it without call)
Remember to update adbClient Launcher to point to new folder.
Add first time greeting, explaining commonplace commands and the various folders using java.
add batch snake from [URL="http://www.dostips.com/forum/viewtopic.php?t=4741&mobile=on"]here[/URL] [URL="http://www.dostips.com/forum/viewtopic.php?t=4741&mobile=on"]and here[/URL] for fun
learn some design tips from batch snake.
add adb closer background script for when someone closes adbclient with the windows close button.
add ability to root adbps and adbp or just enable insecure adb debugging
setpass not using admin privileges, add call capability to use instadb privilege elevation code as an elevation module for the rest of my code)
search for commands
CHANGELOG:
This changlog is deprecated for the commits page on my github: https://github.com/lgrootnoob/adbClient_EnvironmentandTool/commits/master
Code:
With 1.3.1 adb/fastboot has been updated from platform-tools to rev. 19(Previously rev. 18.0.1)
Split 1.3.1 into xp only and vista up packages
Add a work command that will send you back to the work folder no matter where you are.
See third post.
Removed a couple of the zips in the post to make the download list easier.
Made license a separate download.
Add unroot function.
Implement extracter with a windows tar exe for extracting images from a tgz.
Make adb/fastboot installer for system. (%WINDIR%\system32) (To install the binaries just type instadb and follow the prompts)
(Installing adb and fastboot to the system makes adb or fastboot dependent applications operate without the need to setup complicated environment variables.)
(Before you would have had to make the environment variable point to the folder conanaining the binaries then you would have to check to make sure its setup properly. this will eliminate that issue)
Add the launch script into the package and update instructions. (JUST added launcher to make starting it easier.)
Issues with my implementations of certain processes inside the script.
Fixed updater typo.
Added sfk binary from stahlworks.(VERY useful tool [URL="http://stahlworks.com/products.html"]http://stahlworks.com/products.html[/URL])
Added zip and unzip binary from stahlworks
Added latest usb driver from google.
Add the launch script into the package and update instructions.
add win32 busybox and remove gnuwin32 tar command.
Apk install from file. And apk uninstall and apk installed lister. pm argument sender. apk command for menu
Version change in updater code. but server on mandatory downtime for a week.
Fixed problem with missing dlls in system32 install for adb and fastboot
^Fixed bugfix in 1.8 Whackamole:)
use nul to detect dirs
everything that is passed to cmd is called.(In 1.8.2+)
Added ls links to busybox and can use params like ls -l
Made links to busybox with batch files and parameters.
Added md5sum binary.
Make attempt at auto pushd popd implementation. To use this feature just cd to wherever then type back to go back.
New XP local drive version. (Remember that XP can run any version from a removable drive or drive that isnt the partition with the running OS on it.)
FIXED - Output cleanup and implementation of code rendering inner shortcuts unuseful)
add extra bin for user binaries in Work\userbin
added addpath command to append the current folder to the temporary path
Fix another bugfix.
testing version released so the version number on my server will not be updated until I have personally evaluated these builds for a couple of days.
implement pushd popd into my code
add windows tools from knife into adbclient.
made repo command.
added bin2hex binary
added deveject binary
move %clrsnd% %clrval% above the doneloop subroutine so busybox's ls command can properly highlight file names.
only use %clrsnd% %clrval% when needed (pretty much the same as I have done with adb devices and fastboot devices)
added zipalign binary
update updating system to live (ON)
add repo style p2p apt-get system called Gridlock(Thought of the name myself) (not p2p yet :( )
moved extended menu out of code and into a file to help clean up stuff.
add bash link for busybox
fixed up repo script address(dynamic)
added mkfloppy
fixed bug in apk installer code.
removed cmdmenusel and trashed the idea of using it for the preffered java dependency setup.
fixed small bug
changed exit for future dynamic handling of shutdown disk operations.
cat command takes over the beginning of the next echo so it has an echo. in its code.
Deprecated every addpath script and moving to modular addpath userspace script.
Also fixed varname bug in addpath script that made it worthless
Commented my info in.
fixed unrooting issue.
piped apklist to more.
Comment code/subroutines etc. and use whitespace to make it easier to read.(Half done, it needs more work)
everything below is for unreleased 2.3 version.
Strace helper
added goo.im opener
added audio converter freac (Freac has source code available freely on their webpage)
Remove just a couple lines from the inital output to make it fit the command prompt screen.
strace installer (chmod 777 adb push and su -c sh) for work with strace.
add data /T to top of script
added frontend for deveject binary because it is too complicated
make cnt a command that will take params so you can type cnt 192.168.1.81
^if no params are given it will ask for ip address
added send command to strace in testing
merged strace bug fixes into testing
fixed another path bug in testing
code now becoming very modular with me using scripted functions as commands in other scripts.
lgctnp always out to work dir now
fixed 'regression' in hist (Accidental reference to deprecated function broke it) (ALSO: fixed in clr)
project no subroutine/if statements: instead of using if statements on the users input on the main loop I will use batch files in my path that have the name of the user's command.
^This eliminates "" crashing.
add hash check for transmitted file. (Needs md5sum binary for android.) (Make it a question)
add busybox installer
add quick fixes menu for things like accidentally deleted launcher, etc.
fixed issue with busybox android binary got deleted.
added: 'mode con:cols=100 lines=50' for big console
fixed up lgctnp and dmsgnp code
add dmesg
quick patch for scroll height (It will be tweaked more in the future.)
[B]3.1.5 will be a temporary bug fix and binary addition in preparation for.......[/B]
make cd freac* point to full path instead
add startup Splash screen for christmas holiday
added Framaroot to rooter
added exynosabuse to rooter
adbsl is accidentally pointing to old doneloop subroutine and needs to be pointed to EOF
move from old pclouds busybox binary to [URL="http://intgat.tigress.co.uk/rmy/busybox/index.html"]tigress win32 busybox[/URL]
update android sdk dependent stuff (platform tools have been updated to 19.0.1)
update su and supersu
change call adbclient to call start adbclient so the intital launcher is exitable
java detector added
[B]3.2 Released![/B]
fix old subroutine pointers in devej
add startup sound
[B]3.2.1 Released![/B]
added screenshots to OP
patch instadb with set "installmaybe="
add size check for pulling/pulled or pushing/pushed files on adbp and adbps like the md5sum checker.'
update busybox/adb/fastboot/freac/anything else/check and update apk versions.
add question to adbp and adbps for redoing the push/pull operation if the user notices the hashes don't match
[B]3.2.4 Slim Released![/B]
change release naming scheme from final to only use final name for final release in 3.2.x, 3.3.x etc.
fix adbp to do you to "Redo pull operation?" instead of "Redo push operation?"
cleanup root.bat output organizing exploits by android version.
change subroutine pointer in ex from doneloop to :EOF
[B]3.2.5 Slim_ Maintenance Released![/B]
Google's usb driver updated to revision 9.
link every busybox applet
store busybox whoami value in variable and then put it into $~: set /p command
pointed launcher directly to bin folder name
updated binary and application dependencies
[I]Made some progress in porting a new xp desktop version: the path names need to have quotes around them.[/I]
[B]3.2.6 Slim Released![/B]
[I]INFO: adbClient is somewhat usable in Wine.[/I]
Framaroot and sfk updated.
Tigress busybox updated.
Fixed qfx mounting issue.
android busybox binary updated
updated supersu apk and su, [B]NOTE:[/B] It is ton of work to support 4.3 rooting but I will do it soon in 3.2.8 I will have to bundle cydiaimpactor somehow.
[B]3.2.7 Slim Released![/B]
2.2 removed(cached locally, so it will be unavailable. leaving the remnants of 1.9.5 even though xp is not supported by microsoft anymore)
[B]3.2.8 Released![/B]
GITHUB REPO: [url]https://github.com/lgrootnoob/adbClient_EnvironmentandTool[/url]
updated to usb driver v10
[B]3.2.9 Released![/B]
Bump:
Bump, any dev can use this tool to have their rom users debug the roms that they make easily if they like.
I have done enough testing to know that this works in Wine on Linux pretty good now.
However, special launch instructions are needed.
cd to the adbclient bin folder(Currently bin-3.2.6-Slim) and use the command:
Code:
WINEDEBUG=-all wine cmd /c adbclient.bat
- all on one line.
Adbclient should be started and you can connect to your phone wirelessly with cnt *.*.*.* (Insert ip address to the left).
Happy Linuxing.
EDIT: Bash port coming soon to a Linux computer near you.
Latest use of this tool as a library/environment for making a rooting package for phones.
http://forum.xda-developers.com/showthread.php?t=2738977
The changelog here will now go unmaintained in deprecation for a github repo: https://github.com/lgrootnoob/adbClient_EnvironmentandTool
3.2.9 released.
Lgrootnoob said:
I have done enough testing to know that this works in Wine on Linux pretty good now.
However, special launch instructions are needed.
cd to the adbclient bin folder(Currently bin-3.2.6-Slim) and use the command:
Code:
WINEDEBUG=-all wine cmd /c adbclient.bat
- all on one line.
Adbclient should be started and you can connect to your phone wirelessly with cnt *.*.*.* (Insert ip address to the left).
Happy Linuxing.
EDIT: Bash port coming soon to a Linux computer near you.
Click to expand...
Click to collapse
I don't like bash. :/
pcwizzy37 said:
I don't like bash. :/
Click to expand...
Click to collapse
bash is necessary for using some build systems to compile android source code. If the OP wishes to donate his time and efforts , I'm sure that an easy installer will be useful to someone. I believe that this tool deserves more response than it has received.
Sent from my LGL15G using Tapatalk
ibub said:
bash is necessary for using some build systems to compile android source code. If the OP wishes to donate his time and efforts , I'm sure that an easy installer will be useful to someone. I believe that this tool deserves more response than it has received.
Sent from my LGL15G using Tapatalk
Click to expand...
Click to collapse
I have no idea why I said that back then. I have been dailying Linux for years now and BASH is what I primarily use, also it's wierd because at that time was when I was migrating to Linux.
It has been a long time since I last posted some of my AppleScripts (posted them on reddit way back when...) - so I decided its time for an update, since I changed them quite a bit since I first wrote them.
So what is this?
--
In the .zip file below are small applescripts I use on a daily basis to control my FireTV (/Sticks) and Kodi from my Macbook.
You can look at the source of every single one of those scripts using the AppleScript-Editor that comes with every Mac. I encourage you to look at how they work, and modify them, or write your own eventually.
I use two additional programs from github (aafm and xbev) that are currently included in the .zip file - so its easier for you to use them, without sourcing them first -
the respective project sites are:
https://github.com/sole/aafm
and
https://github.com/bobo1on1/xbev
please visit the sites to say thank you for the work their devs did, or contribute to the projects.
(If you wan't me to take them out of the .zip package, drop me a PN, or post it here in the thread and I will take them out immediately and replace them with readmes on how to source the programs instead.)
--
To use the scripts you have to have adb installed on the Mac.
http://forum.xda-developers.com/android/general/adb-fastboot-binaries-os-x-inclusive-t2941205
It doesn't hurt if you are familiar with adb already. And at least have used the adb connect, adb disconnect and adb devices commands before.
Also of course on the Fire TV ADB has to be enabled. (Developer settings.)
To use aafm and xbev you have to have
python
https://www.python.org/downloads/mac-osx/
and
pygtk
http://python.6.x6.nabble.com/Testing-PyGTK-installer-for-Mac-OS-X-td1948270.html or google it
installed, because both programs depend on it.
--
Getting started with the scripts.
In the .zip file, there is a folder named FireRemote which contains the scripts and the Applescript apps. That folder HAS to be copied to the documents folder in MacOS. The scripts have to be started from there. They are written in a way that depends on it.
All the .sh files in the main folder (not the sub folders, the main folder is the one called FireRemote) have to be made executable (chmod 755) or the scripts will not work. The .sh files generally are helper scripts, meant to be executed by the main script, once you run that.
The reason why this is needed is, that I pull the Fire TV's IP address from the terminal history - and this only works if I use shell scripts that are executable.
--
How do you use them?
there is one prerequisite, and that is that you typed in
adb connect IP.ADD.RE.SS
into the macs Terminal recently. IP.ADD.RE.SS of course being the actual IP address of your FireTV (/Stick). If you are typing it in just now, make sure to disconnect from your FIre TV with
adb disconnect
afterwards - or the adb "channel" won't be open for the scripts to connect. Also - it might not hurt to toggle the FireTVs adb toggle (in Settings) off and on. If you have still issues with the scripts connecting.
--
Scripts and what they do.
aafmtrigger
connects to the FireTV and starts aafm - a GUI adb filebrowser, that allows you to browse the FireTVs file system and transfer files from and to the Mac.
If you start the app again (for example using the cmd+space spotlight shortcut), it closes aafm and the adb connection.
acopy
copies the content of your clipboard to a textfile, names it zwischenablage.m3u, copies it to /sdcard/ on the FireTV and tells Kodi to play it. This is meant to be used with any direct video links you get from the web.
To get direct videolinks (and copy them into your clipboard) you could use the chrome or firefox extension "Video DownloadHelper" - if you need a video to test it on, use a kickstarter.com video - but it works with pretty much everything else as well.
Also - if you look into the corresponding .sh script - I also made it work with youtube links (default link format, not shortlinks) - which requires a slightly different syntax in the .m3u file. Point being - if you want to use it with links that require the urlResolver in Kodi - you might have to tweak the formating of the links - and the youtube example should show you how thats possible.
capmyfire
pulls a screencapture from the FireTV and puts it on the Desktop. Renames the filename, so you can take multiple screencaptures in a row.
FRtrigger
starts xbev and connects it to Kodi. If you have Kodi set up to be able to be controlled from external devices. Look up how thats supposed to be done, on the xbev project site.
xbev is a programm that allows you to use your Macs keyboard to control Kodi (play, pause, navigation, text entry... the whole nine yards)
If you start FRtrigger again, it closes the program.
kolog
copies Kodis log file onto your desktop.
firefire, firekodi, and firereboot
Are just simple apps that start Firestarter, Kodi, or reboot the FireTV;
pandorapeek
is an app to control the pandora app from your Mac.
(homeadb
ATTENTION! Use with caution.
(I am modifying the .bash_history file here - now while thats a file thats common to all Linux and macOS systems - and shouldn't have changed in structure across different version releases, I havent tested it with all macOS versions, and I havent tested it with Sierra yet. Also it is important that you follow the instructions below regarding the empty line thats needed - so there is a small amount of risk that you might have to clear the .bash_history - if it shouldn't work.
You can find information on how to do that here:
http://askubuntu.com/questions/191999/how-to-clear-bash-history-completely )
homeadb is meant to be integrated as part of the macs "Login Items", and is a script that will write the "adb connect IP.ADD.RE.SS" line into your terminal history file every time you boot up your Mac. To use it, first you have to change the IP address in the firetv_ip file in the FireRemote folder, to resemble the IP address of your FireTV. Please make sure, that after the IP address there always is an empty line in the file. This is IMPORTANT.
If you run the script manually - nothing will happen until the next reboot of your mac, because there is only a short window at boot where the terminal history file is writable and hasn't already been pulled into ram. Thats why the homeadb script is meant to be integrated as a "Login Item".
The other reason is, that eventually you might loose the adb connect IP.ADD.RE.SS line from your terminal history, as it only stores a limited number of recent entries. Having this script "repopulate" the line on every boot up usually is enough for it to stay there.
Why do I use the terminal history, and not a hardcoded IP address for the scripts?
Using the terminal history makes it very easy to switch between FireTVs (/Sticks), and use the scripts with another one. You just enter adb connect IP.ADD.RE.SS into the terminal (which is something you usually do anyways -) and all the scripts are set up and ready to go.)
(usrbin
ATTENTION! Use with caution.
(in this case, because /usr/bin/ is a directory where other important files are situated - so basically, don't go haywire and delete them by accident - apart from that, there is no risk)
In the folder usrbin are two files that you could copy to /usr/bin/ on your mac (dont forget to make them executable with chmod 755). The files are called adb.sh and telnet.sh and basically do the same "history loockup" my scripts to.
adb.sh will look up the last adb connect command you entered into the terminal and enter it again -
telnet.sh will look up the last telnet connect command you entered into the terminal and enter it again -
both are meant to be used as shortcuts. Once you moved them to /usr/bin/ and have made them executable - you can just type in adb.sh or telnet.sh in the terminal (in any directory), to establish a adb or telnet connection to the last device you were conncted to. Both are only meant to be used from the terminal. If you dont use the terminal that often, don't bother with them).
(miscellaneous folder
in the miscellaneous folder you find a few scripts that probably will not work "out of the box" for you, and are meant for you to be played with, if you are interested what else is possible with a little Applescript codeing.
The webkey apps start/kill webkey (a remote desktop app for android - to be able to remote control Fire TVs from a laptop - but they are coded pretty specific to my needs. F.e. after starting the app they go to the third desktop on my mac, where a chrome window is always open, open a new tab, enter the iport for the webkey server, enter username and password, press enter --- and so forth... So not necessarily something thats instantly usable by everyone - but you can make it work... )
The kill webkey app is there to kill webkey after using it, so it doesnt draw cpu cycles in Kodi, while watching videos.
The adbwebkey app uses webkey to toggle the FireTVs adb toggle. As webkey doesnt use adb to pipe into the FireTV you can use it to reset the adb toggle. But this one is dependent on having the adb wifi app installed (you find the app name in the script), and being placed on a certain position in the firestarter grid, to be launched -- so again, not something you can use, without at least some modification.
There also are two Kodi configuration examples in there I use, that you could look at, and another script thats just pure overkill... )
Oh - and of course install the Play to Kodi addon for Chrome - if you haven't done so already - it opens up a few more usecases *https://chrome.google.com/webstore/detail/play-to-kodi/fncjhcjfnnooidlkijollckpakkebden
Thats it, have fun parsing all this information and using the scripts, if you are a Mac user.
The "ATTENTION! Use with caution." warnings in the text might have been a bit harsh...
I have left them in to indicate, that you should pay close attention with those steps, but I've now explained why, and what the (actually small) risks are.
I had the average user in mind, when writing those warnings - but reading the tutorial again, the amount of steps needed to make all of this work, might have scared them off sufficiently...
Don't get scared by the warnings - Is what I am saying. Get scared by the complexity and my unwillingness to provide eazy step by step tutorials.
I'm not updating the script bundle just for this, but if you add this line -
Code:
pbpaste | sed 's,https://,http://,g'| pbcopy
to the acopyh.sh script (I leave it to you to figure out where exactly ),
every https videolink you send to Kodi gets redirected to http instead. This sometimes is important, as - the FIre TV still has issues supporting some https standards (and afair Kodi relies on the system to handle that stuff) - and sometimes will not play videos, just because they require a https connection.
So if you notice that direct videolinks tend to "not work" with Kodi, when they want to establish the connection over https - this is an easy to implement workaround.
reading pillow
nice post
---------- Post added at 01:38 PM ---------- Previous post was at 01:19 PM ----------
sdfgksdjui sgashgaui gkhasg
---------- Post added at 01:48 PM ---------- Previous post was at 01:38 PM ----------
fjkaskjfh alfjasdkga asfhsgjuk
---------- Post added at 02:36 PM ---------- Previous post was at 01:48 PM ----------
hfjashf sdfgughasdu afjhasj asfashj
o yesss
sfasfu asu r4854klhfa 8ryt8ri
---------- Post added at 04:05 PM ---------- Previous post was at 04:00 PM ----------
nice post
yar kya krtty o
---------- Post added at 04:09 PM ---------- Previous post was at 04:05 PM ----------
hi
i want to ask you
you r awesome
hello
nice post
klklhk jkjkjk
---------- Post added at 01:02 PM ---------- Previous post was at 12:54 PM ----------
jhjhk djhgh kukh
---------- Post added at 01:06 PM ---------- Previous post was at 01:02 PM ----------
ghsgd adsda sdsdgh