Develop Bugs

[APP] ADB enhanced Putty (replacement for "adb shell" command)

We all know that running "adb shell" from the command line is pretty crap, and when using a latter busybox version which has coloring support it's ultimately crap. One workaround was usually to start a telnet server on the phone, and use putty to connect to that telnet server. Actually there is a more easier way to do that which also works for non rooted phones.
Actually the Android Debug Bridge has a terminal connection feature (roughly speaking), which will be enabled after you connect to the adb server in "0006shell:" mode. You can actually use the putty to connect to this interface always, by setting the following things:
- Turn off line discipline in settings
- Use RAW mode to connect to localhost:5037
- Enter "0012host:transport-usb" (without quotes)
- Enter "0006shell:" (without quotes)
Now you've got a full fledged connection to your device. The main drawback is that it's tedious to repeat the above all the time, so I've made some modifications to the putty binary that adds a new type of connection, called "Adb"
To use the enhanced putty (via USB):
- Select Adb from the connection type list
- Enter "transport-usb" in the host (or any other connection string, check the adb socket interface documentation if you need something else than connecting via usb)
- Enter 5037 as port, if it's not already set there.
- Connect and enjoy (you might also save this connection, so next time you only have to double-click on the settings)
To use this via wireless adb:
- Connect to wireless adb using a command shell: "adb connect IPORT" (substitute ip and port for the real values)
- Enter "transport-any" in the host
- Enter 5037 as port if it's not already set there
- Connect and enjoy
To use this via the android emulator:
- Enter "transport-local" in the host. Everything else is the same
If you have multiple devices (for example multiple devices connected to usb and/or wileressly)
- Enter "transport:serial-number" in the host, where you substitute "serial-number" with the serial of the device you get by using "adb devices". Everything else is the same.
DL and source: http://github.com/sztupy/adbputty/downloads

Thanks
Great job
Love to use putty.
If this do what your say it's good buy adb shell!!

i am using putty for a long time, and i just tried urs, it looks great but i failed to connect coz i'm connecting to 2 devices....
so how can i add the -s param to specify which phone i'm gonna connect?
thx
EDIT: wow!!! i removed one of my devices and connected to it now!! ctrl-U now works!!!! THANK YOU!!!
EDIT2: quick question. if i use a normal putty, where to type in 0012transport-usb and 0006shell: ? i typed them in the term but it closed after 0006shell

Thanks. It works, but any idea how to get the up and down arrow keys to work on Putty? They work on the windows adb shell.

ykk_five said:
i am using putty for a long time, and i just tried urs, it looks great but i failed to connect coz i'm connecting to 2 devices....
so how can i add the -s param to specify which phone i'm gonna connect?
thx
EDIT: wow!!! i removed one of my devices and connected to it now!! ctrl-U now works!!!! THANK YOU!!!
EDIT2: quick question. if i use a normal putty, where to type in 0012transport-usb and 0006shell: ? i typed them in the term but it closed after 0006shell
Click to expand...
Click to collapse
The complete specification is here: http://android.git.kernel.org/?p=pl...T;hb=f41986bbc79055a4feed7266cac5c1b540296daf
This is what you can use:
- transport-any (either usb or local emulator)
- transport-usb (the only usb device)
- transport-local (the only emulator)
- transport:SERIALNUMBER (the concrete device with the appropriate serial number)
so in your case you have to use the latter.
For the second question, you need to ensure that all of the things are present:
- You are using RAW mode (connecting to localhost:5037)
- Line discipline is on "Force OFF" (in the terminal settings dialog)
- You make some pause between writing the two commands
- You don't press enter/backspace or any other key while entering the commands (the easiest way is to write the commands in eg. notepad, copy them, and paste them into putty by pressing ****+RIGHT MOUSE BUTTON)

hardcore said:
Thanks. It works, but any idea how to get the up and down arrow keys to work on Putty? They work on the windows adb shell.
Click to expand...
Click to collapse
The up and down arrow keys were actually handled by cmd.exe, which is non existent in putty. Instead it's now the responsibility of the shell to do the hard work. The included sh in the phone's sotfware (toolbox sh) is mostly useless here, but if you have busybox installed, you might want to run "busybox sh" after connecting (some rooted phones have busybox's sh as default, on them it should work out of the box).
Busybox's sh can not only handle the up and down arrows, but other things like tab completion works too.

sztupy said:
The up and down arrow keys were actually handled by cmd.exe, which is non existent in putty. Instead it's now the responsibility of the shell to do the hard work. The included sh in the phone's sotfware (toolbox sh) is mostly useless here, but if you have busybox installed, you might want to run "busybox sh" after connecting (some rooted phones have busybox's sh as default, on them it should work out of the box).
Busybox's sh can not only handle the up and down arrows, but other things like tab completion works too.
Click to expand...
Click to collapse
Use the ash.
edit:
Btw, thank you for this adb-putty.

sztupy said:
The complete specification is here: http://android.git.kernel.org/?p=pl...T;hb=f41986bbc79055a4feed7266cac5c1b540296daf
This is what you can use:
- transport-any (either usb or local emulator)
- transport-usb (the only usb device)
- transport-local (the only emulator)
- transport:SERIALNUMBER (the concrete device with the appropriate serial number)
so in your case you have to use the latter.
For the second question, you need to ensure that all of the things are present:
- You are using RAW mode (connecting to localhost:5037)
- Line discipline is on "Force OFF" (in the terminal settings dialog)
- You make some pause between writing the two commands
- You don't press enter/backspace or any other key while entering the commands (the easiest way is to write the commands in eg. notepad, copy them, and paste them into putty by pressing ****+RIGHT MOUSE BUTTON)
Click to expand...
Click to collapse
thx for u reply, but all i got in the log:
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2010.10.09 13:10:54 =~=~=~=~=~=~=~=~=~=~=~=
0012transport-usb
0006shell:
FAIL0012device offline (x)
with adb turned on and working

sztupy said:
The up and down arrow keys were actually handled by cmd.exe, which is non existent in putty. Instead it's now the responsibility of the shell to do the hard work. The included sh in the phone's sotfware (toolbox sh) is mostly useless here, but if you have busybox installed, you might want to run "busybox sh" after connecting (some rooted phones have busybox's sh as default, on them it should work out of the box).
Busybox's sh can not only handle the up and down arrows, but other things like tab completion works too.
Click to expand...
Click to collapse
Yes and it will be great if busybox can handle history like linux

ADB over wireless ?
Hi, thanks for your great work
I'm using ADB Wireless
The first step is to connect first with
Code:
adb.exe connect 192.168.6.14:5555
And then the standard procedure
Is it possible for you to include these two phases directly inside Putty ?
So we just have to enter the IP address of the phone and here we go
PS : to disconnect, we have to do
Code:
adb.exe disconnect 192.168.6.14:5555
but that's not an obligation

seems to be a windows/putty problem because adb shell works wonderful on ubuntu with the default shell ...
btw. you can also easily get a sshd (dropbear) running. then you can ssh onto the device over wifi ... i can provide the binary+explanation if anybody is interested.

I'm very interested in that !
Sent from my GT-I9000 using XDA App

virus found

mathieumeuh said:
I'm very interested in that !
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
here is the explanation how to set it up (cyanogenmod wiki):
http://wiki.cyanogenmod.com/index.php?title=Howto:_Connect_to_Device_with_SSH
basically you have to create the keys on your pc and copy them onto the device. then you can connect via key-auth. if you want dropbear to autostart @boot you could add it to playlogos1 ...
and here are the binary's you need (including the missing dropbear-keygen) and a bash binary:
http://www.multiupload.com/B0L9FDQHPB
bash is optional of course but it's very nice to have tab-completion and the other improvements bash offers over sh. to replace sh with bash do the following:
Code:
cp bash /system/bin/
chmod 0755 /system/bin/bash
mv /system/bin/sh /system/bin/sh_OLD
ln -s /system/bin/bash /system/bin/sh
the chmod is really important. i forgot it once and then was unable to get shell access even over adb. was a pain in the ass to fix it again

jodue said:
seems to be a windows/putty problem because adb shell works wonderful on ubuntu with the default shell ...
btw. you can also easily get a sshd (dropbear) running. then you can ssh onto the device over wifi ... i can provide the binary+explanation if anybody is interested.
Click to expand...
Click to collapse
You seem to miss the point of this development. First, your method is mentioned as one of the possible workarounds in the first post. Second you need to have some kind of telnet/ssh server running on the phone, which you don't need, if using adb.
Meanwhile you don't even need a rooted phone or busybox or anything to get this thing working.
The main problem with adb shell under windows, that it uses the standard cmd.exe to run, and uses the standard cmd.exe's "readline" support, which only supports the up and down keys for history (and even that it only supports that within one session).
Putty is mainly the only good (xterm compatible) terminal emulator for windows (msys's or cygwin's rxvt is good too, but "adb shell" was programmed in a way that makes it kinda useless under rxvt too). There are two ways to fix this. One is to make adb.exe more comptible with rxvt, the other is to skip adb.exe entirelly and communicate with the adb server without it. This project utilises the latter.

But what is the advantage compared to "normal" ABD

But what is the advantage compared to "normal" ADB ?
Thank you!

DirkStorck said:
But what is the advantage compared to "normal" ABD
Click to expand...
Click to collapse
It has a real xterm compatible terminal emulator. Is you use busybox >= 1.17.1 you've got coloring, tab completion, resize events, keyboard events (applicatios like vi is working), etc.

This is the reason I recommend a faulty device: without the problems with the SGS the developments would go much slower Thank you for this putty, i have it connecting to the bash. Color coding and keys work perfectly.

Thanks for this Sztupy!
I hated using windows cmd.exe to access a linux shell

A100 with ICS and Ad-hoc: The right wpa_supplicant

After an hour or so of searching for the right file, I want to share with A100 owners how to enable ad-hoc support for their ICS-running tablets. All the work was done by other users on this forum, but I just want to compile the right links and method here.
1) Root your device. Follow the instructions on http://forum.xda-developers.com/showthread.php?t=1531646 and you should be set.
2) Remount /system as rw. In a root terminal,
Code:
$ su
# mount -o remount,rw /dev/block/mmcblk0p3 /system
For the next few steps, I recommend using a file manager.
3) Navigate to /system/bin and backup your original wpa_supplicant file.
4) Copy the wpa_supplicant from http://forum.xda-developers.com/showpost.php?p=25356357&postcount=136 to /system/bin.
5) Change the permissions of your new wpa_supplicant file to match the old one. It should be -rwxr-xr-x.
And you're done! Ad-hoc networks are now prefixed with a (*) symbol. Tether your tablet to your phone and free your ICS from hotspots!

It's does not work on my phone.
My phone is Galaxy note ICS.

bunkhun said:
It's does not work on my phone.
My phone is Galaxy note ICS.
Click to expand...
Click to collapse
The right wpa_supplicant varies by device, which is why it took so much trial-and-error for me to find the right one. This one I can confirm to work on Acer A100 running ICS. You'll have to look for a wpa_supplicant that works on the Galaxy Note. Look around on the forums and experiment with wpa_supplicants and you might get lucky (just don't forget to backup your existing one)
Sent from my A100 using XDA

I guess I'm not sure what this ad-hoc really does. I can tether my phone's 3G network as a hotspot. My A100 running Flexreaper ROM can connect to it and browse the internet just fine without modifying the wpa_supplicant. Maybe civato already included the modified wpa_supplicant in the ROM?

That's probably right; the Flexreaper ROM probably has an ad-hoc compatible wpa_supplicant. I'm pretty sure Cyanogenmod has, too. Ad-hoc allows a wireless device to connect to another peer-to-peer style (i.e., without a router). Cell phones that broadcast hotspots are ad-hoc networks. For some reason the stock Android OS does not allow connecting to ad-hoc networks, so a modified wpa_supplicant must be used.
Sent from my A100 using XDA

I copied the file over. I used root explorer for everything. I will check it momentarily.
---------- Post added at 12:58 PM ---------- Previous post was at 12:53 PM ----------
Are you tethering using Bluetooth or are you using a cable? If you are using a cable, what kind of cable. I have looked for a micro usb to micro usb cable but cannot find one. Please advise.
---------- Post added at 01:33 PM ---------- Previous post was at 12:58 PM ----------
Okay, it's working perfectly over Bluetooth. My speed to New Orleans was 1.9mbps down and .9 mbps up. Not bad at all on 3g, Bluetooth. I am very pleased. Now if I could SMS my son. He does not care for google chat or google plus, but he has unlimited texting. I don't because I don't text much.
Thanks for compiling this for us.

Thanks!
Thank you! That was really quick and painless! I now can connect my A100 to my Nokia E72 using Joikuspot!!
Initially, I followed the instructions but I could not mount RW even after successful rooting - not sure why. If you have the same problem, you can try the following:
1. Turn off your Wifi before proceeding
2. Save the modified wpa_supplicant provided in the given link to your PC - e.g. the desktop (you'll need to unzip it)
3. Connect your A100 to the PC via the USB cable.
4. Copy the wpa_supplicant file to anywhere in your A100 (temporarily) using your PC's usual file manager.
5. Use a good file explorer on your A100 (I used Root Explorer - very powerful! But must purchase from Googleplay - $5 Singapore dollars only) to get into the file directories of your A100 and find the modified wpa_supplicant file. Long touch the file until the menu appears and choose 'cut' from the menu.
6. Use Root Explorer to set "mount R/W" which is a convenient button near the top left of the screen
7. Now navigate to the /system/bin folder and find the original wpa_supplicant file - long touch it until the menu appears. Rename it to something like 'wpa_supplicant_original' or whatever you like.
8. Paste the new wpa_supplicant file
9. Exit and go back to settings to turn on the Wifi
10. You should be able to see a (*) next to E72-Joikuspot_XXXXXXX (assuming your phone is on and Joikuspot is on). Now just connect the usual way and now you have adhoc access!

CombatCube said:
And you're done! Ad-hoc networks are now prefixed with a (*) symbol. Tether your tablet to your phone and free your ICS from hotspots!
Click to expand...
Click to collapse
I have the Archos Arnova 7 G3. All AdHoc Networks are prefixed with (*) but I cannot connect. Does anyone have a wpa_supplicant that will work with the Archos Arnova 7 G3?

childoftheworld said:
I have the Archos Arnova 7 G3. All AdHoc Networks are prefixed with (*) but I cannot connect. Does anyone have a wpa_supplicant that will work with the Archos Arnova 7 G3?
Click to expand...
Click to collapse
Way wrong forum for that device, but, post yours up, and see what we can come up with, never know.

pio_masaki said:
Way wrong forum for that device, but, post yours up, and see what we can come up with, never know.
Click to expand...
Click to collapse
Which forum should I be posting this in?

childoftheworld said:
Which forum should I be posting this in?
Click to expand...
Click to collapse
Either your device specific forum, if there is one, or if not there's a forum for devices without their own forum. Some things are universal to a point and others aren't, so if something here doesn't work it'll likely need something based on your device or one with similar hardware.
Tapatalked from my Galaxy S II.

How to disable carrier-check for native WiFi Tether (no root)

*EDIT* This appears to only be working for people with NON-unlimited data plans. I apologize for the inconvenience...
Saw this over in the AT&T subforum, originally posted by @ExTREmE99 , just reposting here.
This will disable the carrier check on your Verizon G4 and allow you to use the native WiFi tether - no root needed!
1. Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
2. Enable USB debugging under Settings -> Developer options
3. Connect the device with a USB cable to a computer with the Android SDK platform tools installed
4. Start an adb shell: adb shell
5. In the adb shell, run these commands one by one:
settings put global tether_dun_required 0
settings put system tether_entitlement_check_state 0
reboot
When your phone comes back up you will have a fully functional native WiFi tether

i must be doing something wrong because i still get the "you need a subscription" popup

Worked for me, thanks! Needed this a few days ago and couldn't use it n was like "F***, wish I had root" hahaha. Oh and also shouldn't this be posted in General?

jrc27 said:
i must be doing something wrong because i still get the "you need a subscription" popup
Click to expand...
Click to collapse
Same here, did I do this right?
Code:
$ adb shell
[email protected]:/ $ settings put global tether_dun_required 0
[email protected]:/ $ settings put system tether_entitlement_check_state 0
[email protected]:/ $ reboot

Congobongo said:
Same here, did I do this right?
Code:
$ adb shell
[email protected]:/ $ settings put global tether_dun_required 0
[email protected]:/ $ settings put system tether_entitlement_check_state 0
[email protected]:/ $ reboot
Click to expand...
Click to collapse
when do you see the subscription message?
try typing:
adb devices
you should see a string of characters listing your device. if it shows no device, then you need to double check that you have your device drivers installed

Tomyk89 said:
when do you see the subscription message?
try typing:
adb devices
you should see a string of characters listing your device. if it shows no device, then you need to double check that you have your device drivers installed
Click to expand...
Click to collapse
I see it after i reboot and try using the hotspot app

jrc27 said:
I see it after i reboot and try using the hotspot app
Click to expand...
Click to collapse
don't use the hotspot app - in fact, disable that one.
You want to use the built in functionality to tether (not technically an app)
Go to settings, More (under wireless networks), then "Mobile Hotspot". You can setup your SSID and password in there. Also, you can create a shortcut in your notification bar by scrolling over to the right side, clicking edit, then checking the box next to "Mobile Hotspot"
Hope that helps.

Tomyk89 said:
don't use the hotspot app - in fact, disable that one.
You want to use the built in functionality to tether (not technically an app)
Go to settings, More (under wireless networks), then "Mobile Hotspot". You can setup your SSID and password in there. Also, you can create a shortcut in your notification bar by scrolling over to the right side, clicking edit, then checking the box next to "Mobile Hotspot"
Hope that helps.
Click to expand...
Click to collapse
I can't even find the damn app to disable it.
I tried as you suggested, going in through the settings and i still get the verizon C*ckblock...

jrc27 said:
I can't even find the damn app to disable it.
I tried as you suggested, going in through the settings and i still get the verizon C*ckblock...
Click to expand...
Click to collapse
Could you try disabling the verizon hotspot app? Mine was disabled way before I discovered this so I may need to add this step to the instructions. you may want to go through the steps one more time after that to ensure everything is set correctly. Don't forget to restart either. It works great on mine so it should for yours as well - unless you took the update a week ago?
Let me know - Thanks!

Tomyk89 said:
Could you try disabling the verizon hotspot app? Mine was disabled way before I discovered this so I may need to add this step to the instructions. you may want to go through the steps one more time after that to ensure everything is set correctly. Don't forget to restart either. It works great on mine so it should for yours as well - unless you took the update a week ago?
Let me know - Thanks!
Click to expand...
Click to collapse
I've been very careful not to take the update. Is the hot spot app have a weird name or something? I can't seem to find it in the app manager or using rom toolbox

jrc27 said:
I've been very careful not to take the update. Is the hot spot app have a weird name or something? I can't seem to find it in the app manager or using rom toolbox
Click to expand...
Click to collapse
hmmm i think I'm confused. My Hotspot app is apparently still in my app drawer. When i click on it it just takes me to the native hotspot functionality.
Honestly I'd attempt to run those commands again. It would help if you took a screen shot of the command prompt window after running all of the commands. After each command it should pause for a second or two then jump to the next line with no errors or responses.
Is your USB debugging on? Also, are you in MTP or PTP USB mode when plugged into your PC?

jrc27 said:
i must be doing something wrong because i still get the "you need a subscription" popup
Click to expand...
Click to collapse
Should it be? I assumed stuff like this went under the Help section since it was helping people. Maybe I'm wrong. If a MOD would like to correct me and maybe move the thread, feel free.

Tomyk89 said:
hmmm i think I'm confused. My Hotspot app is apparently still in my app drawer. When i click on it it just takes me to the native hotspot functionality.
Honestly I'd attempt to run those commands again. It would help if you took a screen shot of the command prompt window after running all of the commands. After each command it should pause for a second or two then jump to the next line with no errors or responses.
Is your USB debugging on? Also, are you in MTP or PTP USB mode when plugged into your PC?
Click to expand...
Click to collapse
Heading to bed...I'll give it another go in the morning
Thanks again for the help, i appreciate it!

jrc27 said:
Heading to bed...I'll give it another go in the morning
Thanks again for the help, i appreciate it!
Click to expand...
Click to collapse
no problem dude. try some of my suggestions tomorrow and get back to me. feel free to PM and we can post the final solution up here as to not fill the the thread up with troubleshooting.

No Go...
Tried multiple times and could not get it to work. adb looked successful but after reboot I still get a subscription check.

joebrady119 said:
Tried multiple times and could not get it to work. adb looked successful but after reboot I still get a subscription check.
Click to expand...
Click to collapse
have you taken the latest OTA update?

Tomyk89 said:
have you taken the latest OTA update?
Click to expand...
Click to collapse
Have not taken any OTA.

This unfortunately doesn't seem to work for me either
I had to put my device in PTP mode in order for ADB to show the device, after the device was confirmed with adb devices, I issued the commands this is the output
Code:
C:\Users\NOTIMPORTANT\AppData\Local\Android\sdk>adb devices
List of devices attached
VS986931(changed the last four for security) device
C:\Users\NOTIMPORTANT\AppData\Local\Android\sdk>adb shell
[email protected]:/ $ settings put global tether_dun_required 0
settings put global tether_dun_required 0
[email protected]:/ $ settings put system tether_entitlement_check_state 0
settings put system tether_entitlement_check_state 0
[email protected]:/ $
When I attempt to enable hotspot I am greeted with the "Use of this service requires a subscription..."
FoxFi seems to work, I just HATE having to change my lock screen in order to use the damn thing!
I'm willing to run further tests and commands if you would like, please just let me know.
I have NOT taken any over the air update. I used the Debloater tool and blocked/hid the app.

Tomyk89 said:
when do you see the subscription message?
try typing:
adb devices
you should see a string of characters listing your device. if it shows no device, then you need to double check that you have your device drivers installed
Click to expand...
Click to collapse
Here's a screenshot of my terminal window:
I'm using the native tethering just like everybody else (Settings, More, flick the tethering switch to On and receive the service check). Haven't taken the OTA and have the service disabled via debloater tool. I appreciate the help!

At this point I'm not sure why some are reporting that this works while others aren't. I added a message on the original post warning that this isn't a for sure thing. I'll be sure to update if/when I find a fix or what is going wrong, but for now I think I have enough info to look into this. thanks for your help everyone and I hope that I can find a fix for this. Worst case - we have to wait until we have root to enable this.
-tom

IP / REST API for controlling Fire TV?

There does not seem to be an official documented API to send commands to the Fire TV via IP. The interface obviously exists and is used by the Fire TV Remote app. Does anybody know how to control the Fire TV via IP?

attunezero said:
There does not seem to be an official documented API to send commands to the Fire TV via IP. The interface obviously exists and is used by the Fire TV Remote app. Does anybody know how to control the Fire TV via IP?
Click to expand...
Click to collapse
I need the same thing so I can control it via Tasker. Unfortunately, communication is encrypted and far from simple (I sniffed the traffic with IP captcher)

djsvetljo said:
I need the same thing so I can control it via Tasker. Unfortunately, communication is encrypted and far from simple (I sniffed the traffic with IP captcher)
Click to expand...
Click to collapse
Well you could try decompiling the android apk and see if you can figure out what it's doing.

rbox said:
Well you could try decompiling the android apk and see if you can figure out what it's doing.
Click to expand...
Click to collapse
Unfortunately, my programming skills end with block diagrams, Tasker at most.
---------- Post added at 04:46 PM ---------- Previous post was at 04:42 PM ----------
BTW, do you know someone that knows SMALI? I need another app that needs a very simple change - doubling the output of one function. I was able to de-compile and find the function in .java but i can't compile it back to class/.smali (a friend of my helped me on this a bit).

Hi,
I am also interested in ip control for the Fire TV. So are there any news on this topic?
Thanks,
Wolfgang

If anyone is still interested it can be controlled by sending keyevents via adb. adb debugging must be enabled on the firetv and adb must be connected then you can send commands like so:
adb shell input keyevent KEYCODE_MEDIA_PLAY_PAUSE
A list of keycodes can be found here: developer dot amazon dot com/docs/fire-tv/remote-input.html#input-event-reference
I believe you can also find commands to start apps and things too.

despian said:
If anyone is still interested it can be controlled by sending keyevents via adb. adb debugging must be enabled on the firetv and adb must be connected then you can send commands like so:
adb shell input keyevent KEYCODE_MEDIA_PLAY_PAUSE
A list of keycodes can be found here: developer dot amazon dot com/docs/fire-tv/remote-input.html#input-event-reference
I believe you can also find commands to start apps and things too.
Click to expand...
Click to collapse
Can you connect to ADB via network (wifi) ?

https://forum.xda-developers.com/fire-tv/themes-apps/windows-app-simple-adb-remote-t2898206

TimmyP said:
https://forum.xda-developers.com/fire-tv/themes-apps/windows-app-simple-adb-remote-t2898206
Click to expand...
Click to collapse
It looks like it will be hard to implement via Tasker (which is what I needed in first place). Controlling mine with Harmony and Tasker Plugin for Harmony

djsvetljo said:
Can you connect to ADB via network (wifi) ?
Click to expand...
Click to collapse
Of course.
Code:
adb connect IP_of_your_FireTV
https://forum.xda-developers.com/fi...adb-remote-t2898206/post55882391#post55882391

djsvetljo said:
Can you connect to ADB via network (wifi) ?
Click to expand...
Click to collapse
Yes, that was my point. Sorry, thought that was implied.
I wrote this shell script to make sending the commands a bit easier. I use it in OpenHAB to control my FireTV via my home automation system Maybe somebody else might find it useful.
Code:
#!/bin/bash
# script to execute a comand on a fire tv via adb
# $1 : ip or hostname and connection port of firetv e.g. Snug-FireTV:5555
# $2 : command to execute
# array of available commands
declare -A COMMANDS=(
["UP"]="19"
["DOWN"]="20"
["LEFT"]="21"
["RIGHT"]="22"
["ENTER"]="66"
["BACK"]="4"
["HOME"]="3"
["MENU"]="KEYCODE_MENU"
["PLAYPAUSE"]="85"
["PREVIOUS"]="88"
["NEXT"]="87"
["WAKE"]="KEYCODE_POWER"
)
if [[ ! -z $1 && ${COMMANDS[$2]+_} ]]; then
# check for existing connection and create new if none found
CON=$(adb devices | grep $1 -c -i)
if [ $CON -eq 0 ]; then
adb connect $1
fi
# execute command
adb -s "$1" shell input keyevent "${COMMANDS[$2]}"
fi

8.0 Shield Experience, goodbye custom home launcher

I'm almost sick to my stomach. I have used HALauncher since I bought the Nexus Player, and now after updating from 7.23 to 8.0, that's it, no more. No more option for custom home launcher in settings. I'm really pissed right now. Not sure if I'm the only one left using something other than the Android TV launcher, but yeah, don't update

No, you're not the only one... I just updated today and same thing, can't manage to work with other launchers as default

It’s easy to set custom home launcher in 8.0. Here is quick guide.
1. Install your prefered custom home launcher (Mine is airlauncher pro)
2. Connect USB cable. Enable ADB. If you don’t know how to enable adb read root guide.
3. Your command for custom home launcher is “adb shell pm disable-user --user 0 com.google.android.tvlauncher”
It will disable default launcher. And thus load other available launcher as default.
Edited: In 8.0 there is adb networking option, so USB cable is not exactly needed. Just use adb connect (ip) instead.

It is a known bug with the update and they are supposedly working on a fix.
https://forums.geforce.com/default/...-experience-upgrade-8-0/post/6125532/#6125532
oldpoem said:
Edited: In 8.0 there is adb networking option, so USB cable is not exactly needed. Just use adb connect (ip) instead.
Click to expand...
Click to collapse
Not entirely true You will have to connect it to USB to make the unit listen on tcp port before you can connect via IP.

oldpoem said:
It’s easy to set custom home launcher in 8.0. Here is quick guide.
1. Install your prefered custom home launcher (Mine is airlauncher pro)
2. Connect USB cable. Enable ADB. If you don’t know how to enable adb read root guide.
3. Your command for custom home launcher is “adb shell pm disable-user —user 0 com.google.android.tvlauncher”
It will disable default launcher. And thus load other available launcher as default.
Edited: In 8.0 there is adb networking option, so USB cable is not exactly needed. Just use adb connect (ip) instead.
Click to expand...
Click to collapse
Not working

alex22280 said:
Not working
Click to expand...
Click to collapse
It’s working fine here. 8.0 with alauncher pro. Please capture error output of adb command.
OK found an error typo in guide that might lead to not working case. Ipad keyboard made wrong autocorrect. combine - - into nonworking —
This is correct command
adb shell pm disable-user --user 0 com.google.android.tvlauncher
This is reference howto
https://www.xda-developers.com/disable-system-app-bloatware-android/
The package we would want to disable is tvlauncher.
---------- Post added at 04:40 PM ---------- Previous post was at 04:34 PM ----------
jeffshead said:
It is a known bug with the update and they are supposedly working on a fix.
https://forums.geforce.com/default/...-experience-upgrade-8-0/post/6125532/#6125532
Not entirely true You will have to connect it to USB to make the unit listen on tcp port before you can connect via IP.
Click to expand...
Click to collapse
There is no easy way to set custom home launcher. That’s what they would fix. But adb is workaround to disable default launcher and other registered home launcher would get called instead.
I didn’t try adb networking anyway. Just pointed out that it probably not needed usb cable.

macmandarrell1 said:
I tried this method yesterday and removed the launcher but it didn't give me the option to choose a different one at all, I had to download the launcher again to fix it
Click to expand...
Click to collapse
OK mine was set alauncher pro as home launcher before upgrade so maybe the defaults was kept and don’t need to registered again.
If it is that case you might need to add more adb command (not tested though)
adb shell cmd package set-home-activity "package/activity"
where package/activity is different from each launcher.
My alauncher pro is
ca.dstudio.atvlauncher.pro/ca.dstudio.atvlauncher.screens.launcher.LauncherActivity

https://forum.xda-developers.com/shield-tv/themes-apps/alternate-launcher-root-marshmallow-t3359076
I have a whole Guide thread on changing the launcher there's many responses from a lot of people perhaps you can find what you are looking for here. The Oreo commands are the same for Pie.

DBCAB said:
https://forum.xda-developers.com/shield-tv/themes-apps/alternate-launcher-root-marshmallow-t3359076
I have a whole Guide thread on changing the launcher there's many responses from a lot of people perhaps you can find what you are looking for here. The Oreo commands should be the same for Pie.
Click to expand...
Click to collapse
The guide which use pm uninstall is something I recommended to avoid because to restored you need to factory reset. It is prefer to just disable and you can enable back anytime you want.

oldpoem said:
This is correct command
adb shell pm disable-user --user 0 com.google.android.tvlauncher
Click to expand...
Click to collapse
Worked for me on Pie.
Thanks!

oldpoem said:
It’s working fine here. 8.0 with alauncher pro. Please capture error output of adb command.
OK found an error typo in guide that might lead to not working case. Ipad keyboard made wrong autocorrect. combine - - into nonworking —
This is correct command
adb shell pm disable-user --user 0 com.google.android.tvlauncher
This is reference howto
https://www.xda-developers.com/disable-system-app-bloatware-android/
The package we would want to disable is tvlauncher.
---------- Post added at 04:40 PM ---------- Previous post was at 04:34 PM ----------
There is no easy way to set custom home launcher. That’s what they would fix. But adb is workaround to disable default launcher and other registered home launcher would get called instead.
I didn’t try adb networking anyway. Just pointed out that it probably not needed usb cable.
Click to expand...
Click to collapse
Thank you for this, I was able to get my launcher back

Good to know this old method still works. Will give it a shot

oldpoem said:
The guide which use pm uninstall is something I recommended to avoid because to restored you need to factory reset. It is prefer to just disable and you can enable back anytime you want.
Click to expand...
Click to collapse
I agree that disable will work and you can disable or uninstall its your choice, as long as you have a functional launcher before doing so. If its a bug we could just use launcher of choice and switch to it when using until NVIDIA fixes the issue.

DBCAB said:
I agree that disable will work and you can disable or uninstall its your choice, as long as you have a functional launcher before doing so. I was wondering though is there not an option under apps on the Shield to simply disable the launcher without using ADB commands ? Has anyone tried to do so ? Quite a few system apps do allow me to disable them right from the settings on the Shield. Also if its a bug we could just use launcher of choice and switch to it when using until NVIDIA fixes the issue. I will add that link to the guide and update it. Ty @oldpoem
Click to expand...
Click to collapse
FYI the command works fine for Nougat and Oreo as well.

oldpoem said:
FYI the command works fine for Nougat and Oreo as well.
Click to expand...
Click to collapse
Yes I know, the thread I was referring to has the Marshmallow, Nougat, Oreo and Pie info as well. I linked it because it has specifics to the different versions of the shield 2015, 2017, 2019 and what cable you need etc. to help people connect if they need the info.

Need to bump up this thread because 8.0.1 hotfix onward Nvidia remove custom launcher option again. They cited google andtoid tv policy prevent them now since google want to force their ads ridden home launcher on android tv.
ADB method still works though.

oldpoem said:
Need to bump up this thread because 8.0.1 hotfix onward Nvidia remove custom launcher option again. They cited google andtoid tv policy prevent them now since google want to force their ads ridden home launcher on android tv.
ADB method still works though.
Click to expand...
Click to collapse
Has anyone figured out how to flash in fastboot on sif?
Oddly enough there's no oem unlock in dev settings but it is already allowed.. so all you have to do is reboot to bootloader then use the power button to unlock the BL... but so far I haven't found a way to flash lol.. been trying fastboot over ethernet using udp/TCP but it's new to me and having a hard time.
Also, not too worried but while oem unlock is on AI upscaling is not allowed lol.. should be easy fix with magisk though.