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

Happy Chick APK on Ouya Not Showing Up

So like the Google Play Store, if you install Happy Chick on the stock Ouya Rom it won't show up in the Apps or Software menu. Anyone know a work around, possibly be able to just rename it within the apk to get around it?

The same for me. Any solution?

Hi, don't know if anyone will read this, but here it is:
I suppose installing a custom ROM would also do the trick, but if you want to keep the Ouya ROM (keep in mind that this is not a pretty solution, and that it requires a PC running on the same network as the Ouya):
- Download the ADB tools and install them on your desktop PC
- Activate network ADB on the Ouya (development menu)
- On your PC, go to the ADB folder and type "adb shell am start -n com.xiaoji.emulator/.Entry"
If this does not work, try "adb connect <IP>" with the IP shown on your TV, and then the shell command.
You can create a .BAT file to launch it, which is a cheap hack but works.

Google Assistant

I have discovered a way to disable and replace Alexa with the Google Assistant through what you could call a 'privilege escalation.' I don't know anything about the Fire Phone so I don't know if you can hook it up to a PC and run ADB commands to it. Can you even download Google apps (sorry if this sounds stupid)?
Anyways, I need some testers to see how widespread this is. In android there is a permission set called WRITE_SECURE_SETTINGS. Basically you can create an app with that said permission in it's manifest. Doing so allows the app to be escalated to a 'root user' in order to edit, remove and or manipulate a set of settings Android called Settings.Secure. In this set of settings are three tiers: System, Secure and Global. The app, or anyone with access to ADB, can run a command to add, remove or change the values of some of these settings.
An app currently exists and is available on the Play Store, that edits these settings; Settings Database Editor. I need you to do the following steps for me please and thank you:
1. Download, install the app, but don't edit anything yet.
2. Hook the device up to your PC and open an ADB window.
3. Type and hit enter when done:
Code:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
4. Go back to the Settings Database Editor app and tap on the Secure tab.
4. Locate the following three lines, if they exist:
Code:
"alexa_enabled"
"assistant"
"voice_interaction_service"
"voice_recognition_service"
5. Go back to the ADB window. Type each of the commands below, hitting enter after each one. You won't see any reply or messages if the commands are successful:
Code:
adb shell settings put secure assistant com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
adb shell settings put secure voice_interaction_service com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
adb shell settings put secure voice_recognition_service com.google.android.googlequicksearchbox/com.google.android.voicesearch.serviceapi.GoogleRecognitionService
adb shell settings put secure alexa_enabled 0
If the last command doesn't work, go to the Settings Database Editor app and tap on secure tab. Locate the alexa_enabled setting and tap it. change the 1 to a 0 and save the setting.
6. Open the Google App and go to settings > voice > Configure 'Ok Google" or your Assistant.
The more who confirm this, the better

How can I disable double tap of home button who activates the "voice input", who is no longer avaible as Amazon decided... THANKS THEM

DragonFire1024 said:
I have discovered a way to disable and replace Alexa with the Google Assistant through what you could call a 'privilege escalation.' I don't know anything about the Fire Phone so I don't know if you can hook it up to a PC and run ADB commands to it. Can you even download Google apps (sorry if this sounds stupid)?
The more who confirm this, the better
Click to expand...
Click to collapse
Hi DragonFire1024,
Thanks for this very interesting post I was just wondering by to see if anyone had unlocked the bootloader :laugh:
Problem with the fire phone is probably 98% of users here use one of @ggow custom ROM's LineageOS 11 or the AOSP based SlimKat and Nexus Rom. Those running the Stock ROM are likely not interested in development hence why no reply's.
To be honest I never even gave the Fire OS a chance before rooting and switching to the Nexus ROM. I am not sure our fire OS has Alexa :silly: or at least as we know it today yes you heard correct a Premium Amazon Device and they see fit not push it out to Amazon device owners. In fact they just went one better and removed the voice service altogether. https://forum.xda-developers.com/fire-phone/general/amazon-voice-services-fire-phone-t3681235 Pretty amazoning :laugh
I was kinda hoping it was to make way for Alexa and a Massive OS Update but I guess thats just wishful thinking. :laugh:

Pocket Mode

Dear Community,
Greetings,
I have been using the mate 20 x for a while now, and very happy with it, what is missing from the phone (and the mate 20 pro too) is the pocket mode in the settings of the dialer app. I had this option on my old Huawei P9.
When having the phone in my pocket, and a phone call starts ringing, the ringtone volume starts increasing, and this doesn't look good when I'm at work or in a meeting.
Is there any ADB command to bring the option to the settings (I used the ADB commands on P9 to show the Font Styles which was missing from the phone).
Regards,

Pocket mode gone
Hi I have the same problem,
latest with EMUI 9.0.0 the pocket mode setting cannot be found via dialer > three dot menu anymore.
Regardless of volume settings (except for vibrate only) the ring tone volume keeps increasing to embarrassing loudness levels when the phone is in my briefcase.
Is there any change to disable the pocket mode "feature" when you cannot access it anymore?
Regards,
MaeSiuS

Finally, a solution to missing pocket mode option
Hello,
I have finally solved it, I tried it and it works perfectly.
Here are the steps:
1- Install settings database editor by 4A from Google Play store
2- Allow developer options in your phone's settings
3- Allow USB debugging
4- Install platform tools ADB on your PC
5- Connect your phone to PC
6- Make sure your phone is recognized by ADB, type command: adb devices
7- if the ADB console list your device number, type the command:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
8- On your phone, open the application Setedit
9- Go to the Secure Table from the top right menu
10- Find the line "Hide_Pocket_Mode", select the value, change it from 1 to 0.
11- Restart your phone, and you'll find the option in the dialer options, More settings.
Hope I helped, it took me time and some research, but it was worth it. lots of embarrassment caused by high ringtone in the office.

Hash_droid said:
Hello,
I have finally solved it, I tried it and it works perfectly.
Here are the steps:
1- Install settings database editor by 4A from Google Play store
2- Allow developer options in your phone's settings
3- Allow USB debugging
4- Install platform tools ADB on your PC
5- Connect your phone to PC
6- Make sure your phone is recognized by ADB, type command: adb devices
7- if the ADB console list your device number, type the command:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
8- On your phone, open the application Setedit
9- Go to the Secure Table from the top right menu
10- Find the line "Hide_Pocket_Mode", select the value, change it from 1 to 0.
11- Restart your phone, and you'll find the option in the dialer options, More settings.
Hope I helped, it took me time and some research, but it was worth it. lots of embarrassment caused by high ringtone in the office.
Click to expand...
Click to collapse
Does this solution works on a Huawei P30 too?
There is the same problem.

flummi19200p said:
Does this solution works on a Huawei P30 too?
There is the same problem.
Click to expand...
Click to collapse
Most probably, yes.
download the setedit application, and make sure you have the secure table, and there is a line "hide_pocket_mode".
Let me know if it works.

Hash_droid said:
Most probably, yes.
download the setedit application, and make sure you have the secure table, and there is a line "hide_pocket_mode".
Let me know if it works.
Click to expand...
Click to collapse
Is the procedure with adb Shell, conecting to PC and the adb console on a PC not necessary?

flummi19200p said:
Is the procedure with adb Shell, conecting to PC and the adb console on a PC not necessary?
Click to expand...
Click to collapse
It is necessary since it will grant permission to the setedit app to modify the secure table, without ADB, setedit won't work.

Hash_droid said:
Hello,
I have finally solved it, I tried it and it works perfectly.
Here are the steps:
1- Install settings database editor by 4A from Google Play store
2- Allow developer options in your phone's settings
3- Allow USB debugging
4- Install platform tools ADB on your PC
5- Connect your phone to PC
6- Make sure your phone is recognized by ADB, type command: adb devices
7- if the ADB console list your device number, type the command:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
8- On your phone, open the application Setedit
9- Go to the Secure Table from the top right menu
10- Find the line "Hide_Pocket_Mode", select the value, change it from 1 to 0.
11- Restart your phone, and you'll find the option in the dialer options, More settings.
Hope I helped, it took me time and some research, but it was worth it. lots of embarrassment caused by high ringtone in the office.
Click to expand...
Click to collapse
Oh man, this is so great! I have a P8 Lite from work which has pocket mode visible, but I also just bought a P Smart 2019 which doesn't have it visible. Or should I say HAD, because thanks to Hash_Droid I now have Pocket mode visible and disabled. I can't begin to tell you how you made my day. Thanks a lot!

Hash_droid said:
Hello,
I have finally solved it, I tried it and it works perfectly.
Here are the steps:
1- Install settings database editor by 4A from Google Play store
2- Allow developer options in your phone's settings
3- Allow USB debugging
4- Install platform tools ADB on your PC
5- Connect your phone to PC
6- Make sure your phone is recognized by ADB, type command: adb devices
7- if the ADB console list your device number, type the command:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
8- On your phone, open the application Setedit
9- Go to the Secure Table from the top right menu
10- Find the line "Hide_Pocket_Mode", select the value, change it from 1 to 0.
11- Restart your phone, and you'll find the option in the dialer options, More settings.
Hope I helped, it took me time and some research, but it was worth it. lots of embarrassment caused by high ringtone in the office.
Click to expand...
Click to collapse
Thank's a lot for this. It works perfectly on P30 Pro :good: :highfive:
It's hard to understand and unlogic why manufacturers like Huawei hide options like Pocket mode in their software. Most users, even the simpliest, surely are interested to customize ring tone options.

Thank you very much Hash_droid, works on P20 pro. :highfive:

Hash_droid, works perfectly on a Mate 10 Pro (I had the same issue) . Thanks a lot.

Thanks, confirming also for Mate 9, EMUI 9.1, not rooted (BL locked).
Btw, I've also enabled virtual HD sound - not sure if the call quality is better

This works on Mate 20 pro. But, if your ADB doesnt recognise your phone, install Huaweis HiSuite. Only so ADB listed my phone.
However, person at Huawei who decided that removing option to disable pocket mode should ne fired. Also, who ever designed the diler app. Huawei, just copy Samsungs dialer, or at least use google phone app. My galaxy S6 had 10x better dialer then my Mate 20 pro now has. At least I have google phone now.

Hash_droid said:
Hello,
I have finally solved it, I tried it and it works perfectly.
Here are the steps:
1- Install settings database editor by 4A from Google Play store
2- Allow developer options in your phone's settings
3- Allow USB debugging
4- Install platform tools ADB on your PC
5- Connect your phone to PC
6- Make sure your phone is recognized by ADB, type command: adb devices
7- if the ADB console list your device number, type the command:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
8- On your phone, open the application Setedit
9- Go to the Secure Table from the top right menu
10- Find the line "Hide_Pocket_Mode", select the value, change it from 1 to 0.
11- Restart your phone, and you'll find the option in the dialer options, More settings.
Hope I helped, it took me time and some research, but it was worth it. lots of embarrassment caused by high ringtone in the office.
Click to expand...
Click to collapse
Thanks! This guide worked also for Huawei P40 Pro (emui 10.1.0.154) :good:

How to improve the performance of Firestick?

How to improve the performance of Firestick?
Please write any tips you know.

Kodimaster said:
How to improve the performance of Firestick?
Please write any tips you know.
Click to expand...
Click to collapse
To improve the performance on Fire TV Stick:
Disable UI animations using ADB:
1. Enable USB debugging in developer options
2. Connect ADB over Wi-Fi
Code:
adb connect <Fire TV's IP address>
3. Run ADB shell
Code:
adb shell
4. Disable any UI animations
Code:
settings put global animator_duration_scale 0.0
settings put global transition_animation_scale 0.0
settings put global window_animation_scale 0.0
Done.
Disable any following dangerous settings:
-> Location based services
-> Interest based ads (advertising ID)
-> Collect App usages
-> Device usage data
Disable System sounds in settings
ADVANCED PERFORMANCE IMPROVEMENT:
Magisk Add-ons for Fire TV Stick 4K. Including with Google services installition, Amazon services removal (debloating to improve performance), Leanback Launcher, and more.
https://forum.xda-developers.com/fi...iretv-4k-stick-add-ons-magisk-module-t3979117

Kodimaster said:
How to improve the performance of Firestick?
Please write any tips you know.
Click to expand...
Click to collapse
When you use it too much. its best clear the cache memory. its very good thing for best performance of the amazon firestick

I tweeked the props and set the CPU to performance based off this thread...
https://forum.xda-developers.com/fire-tv/general/fire-tv-stick-4k-tweaks-root-keyboard-t4064269

Get a 4k or even better an ATV device. No matter how much you "tweak" performance you will not have ram to switch between 2-3 apps without them reinitialize. Even the 4k really cant do 3, but it can do 2 pretty well.

adb returning this error on executing the shell command
adb.exe: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

hiteshp said:
adb returning this error on executing the shell command
adb.exe: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Click to expand...
Click to collapse
It sounds like you are making a connection to your FireTV from a new device (your computer). When you do this, an authorization prompt should appear on the FireTV, press ok to give your computer authorization to access your FireTV.
If the authorization prompt is not appearing on your FireTV make sure you have ADB debugging turned on in the FireTV settings menu

Try the following steps to speed up your firestick:-
Restart/Reboot Your FireStick
Remove Unwanted Apps
Clear Cache of Apps
Keep Your FireStick Up to Date
Disable Automatic App Updates
Turn Off Collect App Usage Data
Factory Reset