[Q] porting Lynx - Android Software Development

Has anybody tried this? having Lynx accessible via adb shell would be - imo - very handy. For example, my work terminal has no internet access, but I can install the USB driver for my Galaxy S and access the shell that way.
Of course, since I'm not allowed to play with my phone while working, it would be very nifty to open up a cmd window and just type "adb shell lynx" and have at it if I need to.
Has anybody tried this? I'm no coder by any stretch of the imagination, otherwise I'd be having a go at it now..

Related

ADB / Linux / G1

Ok, do I am changing all of my work over to Ubuntu and have the 1.5 SDK installed and working now. What I don't have is a device connection when I type "ADB Devices" in my terminal window, or when I bring up DDMS. IS there a trick to getting Ubuntu to recognize the G1 as an ADB device? Help is appreciated.
chicojd said:
Ok, do I am changing all of my work over to Ubuntu and have the 1.5 SDK installed and working now. What I don't have is a device connection when I type "ADB Devices" in my terminal window, or when I bring up DDMS. IS there a trick to getting Ubuntu to recognize the G1 as an ADB device? Help is appreciated.
Click to expand...
Click to collapse
Do a search for an Ubuntu SDK guide, there's a really good one floating around. You need to create a couple of text files to get it to register the USB device, the guide tells you how to do that.
Search for ubuntu udev android. You should be able to find it that way...

adb shell in windows has weird characters, echos everything back

I have been using adb in linux for a while with no issues. When I use the shell, I can use android's native vi editor to edit files, etc, without having to pull and push.
I was reading about the fix for tmo my account 2.x for the phone model, and since I'm at work on a windows xp machine, I downloaded the sdk, installed drivers, etc, and tried this out.
When I get into the adb shell using cmd, each command is echoed back before returning data. Also, when I enter vi, it's just totally messed up. It still works, but I'm afraid to actually use it since I can't actually see what I'm doing.
Is there a way around this?
gsgleason said:
I have been using adb in linux for a while with no issues. When I use the shell, I can use android's native vi editor to edit files, etc, without having to pull and push.
I was reading about the fix for tmo my account 2.x for the phone model, and since I'm at work on a windows xp machine, I downloaded the sdk, installed drivers, etc, and tried this out.
When I get into the adb shell using cmd, each command is echoed back before returning data. Also, when I enter vi, it's just totally messed up. It still works, but I'm afraid to actually use it since I can't actually see what I'm doing.
Is there a way around this?
Click to expand...
Click to collapse
i tried importing bash's vi to adb but didn work

After unlock/recovery/root, cannot use adb commands in Terminal Emulator

Hi all,
After unlocking/recovery/rooting via Heisenberg's guide, I then tried to connect to my Amazon FireTV via Terminal Emulator, but when I try any adb command from it, it says:
/system/bin/sh: adb: not found
What am I missing or forgetting to do? Thanks.
adb is computer -> phone connection. Adb cannot be used in terminal emulator.
zephiK said:
adb is computer -> phone connection. Adb cannot be used in terminal emulator.
Click to expand...
Click to collapse
I've been using the same ADB commands in Terminal Emulator on my Android phones for years...
Anyone?
Anyone? Would really like to be able to connect to all my Android devices...
Can anyone help me with this? I can't find anything online and surprised no one else is asking about the issue...
Same issue was posted here on reddit FYI: https://www.reddit.com/r/AndroidQue.../adb_tool_no_longer_available_on_marshmallow/
How can we connect to other Android devices via Android 6.0 devices if this no longer works?

Anyone had luck with ADB on ChromeOS?

I'm not able to see my PH-1 in ADB on my new Chromebook, and I'm hoping there's a fix available.
I'm in Dev mode, open a terminal, get into shell, type "ADB devices," and the list of devices is blank. No unknown devices, nothing.
I can see it in ADB on the Windows laptop I'm trying to replace, just not on the Chromebook, in Chrome OS, or by using Crouton.
Anyone overcome a similar issue?

Install APK from PC, without ADB

I have developed apps for Android and Wear OS watches – mainly for personal use. It's no problem for me to use ADB to Install to a watch.
But, I would like to install the APK on a friend's watch, who is not a developer or very technical. It Would be nice to be able to do this without a lot of rigmarole. I can enable Developers Options on his watch, but installing ADB to his PC is asking a lot. It would be nice to have a PC app, hopefully that is portable and can reside on a flash drive, that will simply interface with the install protocol to install an APK on the watch.
Does something like this exist?
Barry.
A little more searching and I found this, Flakie's ADB GUI:
Direct download:
https://flakie.co.uk/downloads/FlakieADBGUI.zip
There is a GUI for the common ADB commands and an integration with scrcpy (as in version 1)
It now has an experimental option to use ADB and ADB Shell commands by typing/pasting them in.
I have not actually tested it, but it seems to be exactly what I was looking for.
I downloaded ADB and put the "platform tools" folder on my Flash drive. I also put Flakie's on the flash drive along with the APK I intend to eventually install.
Theoretically this should give me a portable install for the APK (fingers crossed). I am hoping to connect to my friends watch via Wi-Fi and use Flakie's to install the APK.
As an alternative, there is also ADB AppControl. It is well known, and the developer has it quite improved.
ADB AppControl
Official website of the ADB AppControl application. Free Download. Latest release. The ultimate applications manager and debloat tool for Android devices.
adbappcontrol.com

Categories

Resources