Related
NOTE: Root is required
When an application fails to install - even side loads - an error message is logged.
First thing to check is the logcat -> it will point to a secure file issue.
for error -18 it is
smdl2tmp1.asec
this file, and all other *.asec files are in the /mnt/secure/ directory.
If this file cannot be removed by the installing application a failure message results.
to manually remove this file you need a terminal application
android terminal emulator works just fine.
{
"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"
}
Step 1.
launch the terminal application of choice
Step 2.
SU
Step 3.
At the # command prompt type
cd /mnt/secure/asec/
Step 4.
type
ls
This will locate the file causing the issue.
Step 5.
type
rm smdl2tmp1.asec
Step 6.
close the terminal application
Step 7.
enjoy the fruits of your labor by installing the application that initially failed.
Thanks, manikin13!
Do you know any other error codes?
joe75 said:
Thanks, manikin13!
Do you know any other error codes?
Click to expand...
Click to collapse
I believe this fix works on most install error codes.
Interesting. Been getting the Error code 18 when attempting to install VitalPlayer. (Vegan Beta1) Folowed your steps to the letter (miss DOS at times) but that folder appears empty. Actually there is no asec folder on either sdcard or sdcard2. Did I miss something? thanks
skeeterpro said:
Interesting. Been getting the Error code 18 when attempting to install VitalPlayer. (Vegan Beta1) Folowed your steps to the letter (miss DOS at times) but that folder appears empty. Actually there is no asec folder on either sdcard or sdcard2. Did I miss something? thanks
Click to expand...
Click to collapse
Are you using a terminal app on the tablet?
this folder does not show up without using a terminal app on the tablet.
once in the terminal app
cd to /mnt/secure/ to see the files. There is no asec folder. The file extension is asec as in *.asec
You bet. Android terminal emulator from the market. At /mnt (via FileManager) there are folders named secure and asec. Both are empty. Notice that when I cd to even mnt/secure I get same message "not found" Verrrrrrrry interesting!
skeeterpro said:
You bet. Android terminal emulator from the market. At /mnt (via FileManager) there are folders named secure and asec. Both are empty. Notice that when I cd to even mnt/secure I get same message "not found" Verrrrrrrry interesting!
Click to expand...
Click to collapse
I saw the samething that nothing shows up in any file manager. only in the terminal ls do the files show up.
you should definitely get a not found for mnt/secure as the actual path is
/mnt/secure/asec/
the initial / is the root of the OS. (linux or unix)
so you are looking for a dir under root called mnt -> /mnt
so if you are having difficulty finding the full path break it down into each step, and do a ls to find the next step
ie
cd /
ls
cd mnt
ls
cd secure
ls
cd asec
ls
etc
hope that helps
Permission denied in Terminal
How do I get terminal permissions?
JackedNY said:
How do I get terminal permissions?
Click to expand...
Click to collapse
Typically typing su at the $ prompt should bring up the superuser prompt (allow / deny) as seen on screen 3. If not you should be able to go into the superuser app, and specifically add terminal.
once you allow the su request the prompt should change to the
# symbol
That did it. Only difference this time was I added the ls step you suggested (ls same as dir in DOS?) Got to where I needed to be and deleted the *.asec. Thanks.
skeeterpro said:
That did it. Only difference this time was I added the ls step you suggested (ls same as dir in DOS?) Got to where I needed to be and deleted the *.asec. Thanks.
Click to expand...
Click to collapse
Exactly
Dos = Dir
Linux, Unix, OsX, Android = ls (small letters)
Awesome little tut
Was having the same issue - but not receiving an error when attempting to install - walked straight through - had to stop in the dir and see the filename to rm but worked like a champ - thanks!
Thanks for this great walk through. I followed it and was able to correct the problem I was having with some installs. I knew intellectually that Android was similar to Linux, but I did not realize how close it is. It is good to see that my Linux knowledge, I know enough to get me into and sometimes out of trouble (Linux Abuser) , can be applied somewhere else.
Thanks again!
linesma said:
Thanks for this great walk through. I followed it and was able to correct the problem I was having with some installs. I knew intellectually that Android was similar to Linux, but I did not realize how close it is. It is good to see that my Linux knowledge, I know enough to get me into and sometimes out of trouble (Linux Abuser) , can be applied somewhere else.
Thanks again!
Click to expand...
Click to collapse
Android is actually very close to OsX in the respect that it is gui first, with the BSD base doing the heavy lifting.
Android is linux in the background with a gui first to allow the ordinary user some familiarity. The reason linux on the phone is not popular and linux on the desktop is not mainstream is because the command line gets equal or higher billing.
Google was smart with Android (basically a linux port with java framework) by promoting it as a gui just like iOS even though to truely see all the potential you need to get to the command line.
As we don't have root yet on the M preview, here is quick tutorial how to enable Muiltiwindow and change density.
You will need TWRP and Total Commander with adb plugin.
1. Boot the TWRP
2. Go to Mount and check the system checkbox
3. Plug the device to PC
4. In Total Commander go to network/adb/your device/system and find build.prop
{
"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"
}
5. Copy the file to some safe place for backup
6. Open the file in editor (F4)
7. Change the line
Code:
ro.build.type=user
with
Code:
ro.build.type=userdebug
8. You can also change the density in the line
Code:
ro.sf.lcd_density=480
I prefer 420.
9. Save the file and copy it back (if you change it on PC).
10. Done
Just FYI, there is a much more simple way to change the DPI without root. You just need a single ADB command.
With the phone powered on, just open up a window in terminal (OSX) or command prompt (Windows) like you would to perform fastboot or ADB commands, and type the following:
adb shell wm density DPI && adb reboot
Just replace "DPI" with the desired DPI. So if you want a 420 DPI, this will be your command:
adb shell wm density 420 && adb reboot
Then just hit enter, the phone will reboot, and voila! enjoy your new DPI.
how to flash twrp on M !!
bicho19 said:
how to flash twrp on M !!
Click to expand...
Click to collapse
fastboot flash recovery
rivera618 said:
fastboot flash recovery
Click to expand...
Click to collapse
i know, but can you provide me with the img file that work with Android M
bicho19 said:
i know, but can you provide me with the img file that work with Android M
Click to expand...
Click to collapse
It is the same as for Lollipop
Man, I can confirm that this tutorial works perfectly, thank you!
Have you understood how to use multiwindows?
In my case, I can't understand which is the second app he shows on the screen. I can chose one from recent menù, but the second seems to be chosen randomly!
Maybe I'm just tired
Will it cause missing applications from PlayStore as it did every time I changed DPI?
To check, try to download 'Tinder'. Or go to the Store webpage from a computer and try to find an App that it's incompatible with your Nexus 5 (And it shouldn't)
bregan90 said:
Will it cause missing applications from PlayStore as it did every time I changed DPI?
To check, try to download 'Tinder'. Or go to the Store webpage from a computer and try to find an App that it's incompatible with your Nexus 5 (And it shouldn't)
Click to expand...
Click to collapse
Tinder installs/opens fine with DPI set to 420 (just tested it). I used the adb commands to change DPI, worked perfectly.
Own a mac, cant seem to get adb to work properly.
swirly05 said:
Own a mac, cant seem to get adb to work properly.
Click to expand...
Click to collapse
./abd "commands go here"
Don't forget the ./
ape96 said:
Man, I can confirm that this tutorial works perfectly, thank you!
Have you understood how to use multiwindows?
In my case, I can't understand which is the second app he shows on the screen. I can chose one from recent menù, but the second seems to be chosen randomly!
Maybe I'm just tired
Click to expand...
Click to collapse
From the resent menu you can set the top and bottom windows.
When u then in some time launch one of them, it is still will be on top or bottom, but another one will be the last used, but it will not be scrollable some or them, or not always. Still a little buggy, . As the new "half frame" app will be on top.
But if you run both apps from resents that you made top and bottom, then they will both scroll.
The new photo app shows some display bugs with density set to 420
neFAST said:
The new photo app shows some display bugs with density set to 420
Click to expand...
Click to collapse
Dunno. Seem to be working fine for me...
What are those bugs? Try to change to 400 or smth else.
playahate said:
From the resent menu you can set the top and bottom windows.
When u then in some time launch one of them, it is still will be on top or bottom, but another one will be the last used, but it will not be scrollable some or them, or not always. Still a little buggy, . As the new "half frame" app will be on top.
But if you run both apps from resents that you made top and bottom, then they will both scroll.
Click to expand...
Click to collapse
I start to understand! It's a big buggy, but it seems that it will improve a lot
It's a useful function, though
ape96 said:
I start to understand! It's a big buggy, but it seems that it will improve a lot
It's a useful function, though
Click to expand...
Click to collapse
Yap. I like it too.
Added the pic to 1st post. Watching YouTube and browsing the same time...
I changed DPI to 420 but there is no option to enable multiwindow?
how do I fix?
swirly05 said:
Own a mac, cant seem to get adb to work properly.
Click to expand...
Click to collapse
You might need to install the latest ABD and Fastboot, compatible with M Preview: https://github.com/simmac/minimal_adb_fastboot/tree/preview
razor17 said:
I changed DPI to 420 but there is no option to enable multiwindow?
how do I fix?
Click to expand...
Click to collapse
I flashed a zip file posted by another user to enable multi window. Then did the adb command from this thread and its all working here.
Edit: here's the post I got the zip from. Flashed it and enabled multi window. Then I adb command DPI to 420. Working for me. Hope this helps
http://forum.xda-developers.com/showthread.php?p=61061093
height soft key
sn0warmy said:
Just FYI, there is a much more simple way to change the DPI without root. You just need a single ADB command.
With the phone powered on, just open up a window in terminal (OSX) or command prompt (Windows) like you would to perform fastboot or ADB commands, and type the following:
adb shell wm density DPI && adb reboot
Just replace "DPI" with the desired DPI. So if you want a 420 DPI, this will be your command:
adb shell wm density 420 && adb reboot
Then just hit enter, the phone will reboot, and voila! enjoy your new DPI.
Click to expand...
Click to collapse
it's a way to change height navigation bar / soft key ?
EDIT 09/23/16
I finally found a permanent solution to how to change fire launcher on the Amazon Fire without root. It works on any version (FireOS 5.3.1) on any tablet variant (7, HD 8, HD 10 etc...).
You can read the detailed tutorial at http://forum.xda-developers.com/ama...-remove-default-launcher-amazon-fire-t3288310 but basically you run one command, must be done after reboot currently via adb shell:
Noval Launcher on Amazon Fire no-root:
Code:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.teslacoilsw.launcher/.NovaLauncher; done &
That's it. Once you paste that into your adb shell you're done; you now have a default launcher programmatically set via ADB.
Optionally, you can install the modded firelauncher.apk so you can finally delete it without root .
(this is optional, you wont have any launcher after doing this! backup your old APK!!)
Code:
adb install -r -d com.amazon.firelauncher.apk
... as you can now see this will -r reinstall and -d downgrade the launcher, causing it to crash and never open.
Thanks for your support guys, I love android!
EDIT:
I have updated with a new method that is much better, the only negative to this new method is when you hit the home button, for a brief moment you see the firelauncher. Performance, speed, and bugs are perfect.
Just paste this code in adb shell, I'm working on setting up nohup to work with it, when you close adb it will stop working.. Going to bed for now though.
Code:
#!/bin/bash
am monitor | while read -r line; do
if [[ $line == *"firelauncher"* ]]
then
am start [B]com.newlauncher.launcher[/B]
fi
done
I'm new to the whole Android scene, and recently I had acquired an Amazon Fire HD 8. The only complaint about this tablet is the lack of Google Play and the horrible firelauncher. There is currently no root options available for the Fire HD modles 8 & 10, so I have spent the time to develop a temporary workaround.
Please take a quick look at the developmental thread I previously created so we can collaborate to make a more efficient version of this:
http://forum.xda-developers.com/hd8...zon-fire-hd-8-10-remove-firelauncher-t3286646
Disclaimer:
If you plan on installing new applications/packages while this script is running you may have a hard time. Installing packages may take 2-10 minutes, or maybe not at all!
If you experience any problems you can undo everything by running the undo script attatched (unix), or by typing "adb shell ps | grep /system/bin/sh", you will see anywhere from 2-10 processes listed. For each type "adb shell kill -9 <pid>", pid would be the process ID, should be the first number you see on each line.
There is a small chance when you press the home button that it will load the regular firelauncher, do not fret, try again and it will go to whichever launcher you previously selected.
Performance may be slightly altered, if it becomes too bad to use try adjusting the script and change the interval at which it loops (set to 20 by default).
This is an alpha experiment, and I am a noob with Android so please bare with me
This is a noobish approach to disabling the firelauncher (com.amazon.firelauncher.apk), please do not judge it, this is also my first time releasing something for Android.
If you are using a unix operating system (like Linux or Mac), I have compiled a script that does the work for you! Windows users will have to wait and do it manually since I am unfamilar with batch (would someone like to help with this?)
Automatic Tool (easy, linux, mac only)
Step One:
Download the two script attachments:
remove_default_launcher.sh - disables amazon's firelauncher
re-endable_firelauncher(undo).sh - reverts the process, if you have any issues
Step Two:
Run the following commands to make the scripts executable:
Code:
chmod +x remove_default_launcher.sh
chmod +x re-endable_firelauncher(undo).sh
Run the tool to remove amazon's nasty launcher!
Code:
./remove_default_launcher.sh
Step Three:
The script should automatically do everything, when it's done, check your Fire. Keep pressing the home button and switching between applications until you get the "Change default launcher" dialogue, make sure you have an alternative launcher installed beforehand or else you won't have a launcher! When it's all working how it should be go to step four!
Step Four:
Simply exit out of your terminal window, do not type anything, just exit ADB. The script will continue running!
This is what a successful window looks like, whenever you have confirmed it is working, close out of the ADB window and end that process.
{
"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"
}
Manually (harder, windows)
Step One:
Open up a new ADB shell window and type
Code:
adb shell
Step Two:
Once you are in the shell window, simply copy and paste this line of code and press return. It is just a simple bash script that loops the command "install -r -d "/system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk"" which will reinstall the firelauncher repeatedly, which temporary uninstalls it.
Code:
#!/system/bin/sh
nohup
while :
do
kill $!
sleep 1 & pm install -r -d "/system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk" & sleep 20; kill $!
kill $!
done &
exit
#press enter now
After pressing enter, you can watch it go to work, or you can close out of the adb window and unplug your device, it will continue to run until you kill the shell processes or reboot the device. Make sure you have an alternative launcher already installed so it can easily be set as default. EDIT: Reboot may not reset it, which is cool but could be annoying. To turn off this wonderful feature open up adb shell and use "ls | grep shell" and kill using "kill <pid>" all releated processes to /bin/shell or whatever. It may take up to a minute to reset.
If you have any issues at all please comment and I will send you a private message with detailed instructions catered to your specific issue!
If you are a dev, take a look at my unix auto-install script, it may help you figure it out yourself as well. I need someone who understands batch to help me write a windows version .
I literally spent about 45 minutes working on this noobish approach, so if you find bugs or want to modify the script, simply post in the comments your version and why you think it is more efficient. If you want to help make a dedicated and more efficient approach to this, check out the development thread here (there are alternative methods here too):
http://forum.xda-developers.com/hd8...zon-fire-hd-8-10-remove-firelauncher-t3286646
This appears to be a very stable system actually, I recommend everyone does this to the Fire HD tablets!
I hope this helps someone, if this helps you please give me a thanks so I know it
Confused as to why you'd post this here after using the correct forum section for the HD8 and 10 already.
Pond-life said:
Confused as to why you'd post this here after using the correct forum section for the HD8 and 10 already.
Click to expand...
Click to collapse
I was not sure whether it was the correct forum actually, it is stable enough to use for all versions of Fire now, so I posted for users who do not want to root their device, but hate the launcher. If you think it is in the wrong place I will remove it promptly. I actually did post this in the wrong spot.. It is in development instead... At least there will not be any flaming here
I have also noticed 6x more downloads in 1/5 of the time this thread has been posted compared to the other.
I have updated with a new method that is much better, the only negative to this new method is when you hit the home button, for a brief moment you see the firelauncher. Performance, speed, and bugs are perfect.
Just paste this code in adb shell, I'm working on setting up nohup to work with it, when you close adb it will stop working.. Going to bed for now though.
Code:
#!/bin/bash
am monitor | while read -r line; do
if [[ $line == *"firelauncher"* ]]
then
am start [B]com.newlauncher.launcher[/B]
fi
done
Good job on this!
glitch3yf0x said:
Good job on this!
Click to expand...
Click to collapse
No problem, hopefully I will find some more time to work on this in the future .
I am glad you like it.
nyln said:
If you are using a unix operating system (like Linux or Mac), I have compiled a script that does the work for you! Windows users will have to wait and do it manually since I am unfamilar with batch (would someone like to help with this?)
Click to expand...
Click to collapse
If you're still in need, I'd be happy to help port it to windows!
as for me,on windows, worked simply:
adb shell
pm hide com.amazon.firelauncher
to enable the fire launcher again,
adb shell
pm unhide com.amazon.firelauncher
This is one of the best thread for Fire OS world! Can't wait for you to perfect this.
P.S: Plz, someone here port it to Windows.
Does it work on Fire 5.3.1 ?
Please message me if you want me to keep working on this. After the root I stopped.
working great. And how to restore in the laucher back?
I am in Win10
update: After reboot, it turns back to original FireOS launcher. Is there a way to make it auto applied?
ttcontributor said:
update: After reboot, it turns back to original FireOS launcher. Is there a way to make it auto applied?
Click to expand...
Click to collapse
I will do some work on it. I am not an android developer, so maybe i will write a python application.
nyln said:
I will do some work on it. I am not an android developer, so maybe i will write a python application.
Click to expand...
Click to collapse
It's great to hear you still have your hands on this
nerakkaren said:
as for me,on windows, worked simply:
adb shell
pm hide com.amazon.firelauncher
to enable the fire launcher again,
adb shell
pm unhide com.amazon.firelauncher
Click to expand...
Click to collapse
If I am not mistaken, this will only bennefit those who have a rooted device. Fire 7 and HD 8 got updated via OTA removing my root. I am now working on a better way right now .
Please PM or Thank me if you're interested in this, it'll come out faster if I know people are waiting
I finally found a permanent solution to how to change fire launcher on the Amazon Fire without root. It works on any version (FireOS 5.3.1) on any tablet variant (7, HD 8, HD 10 etc...).
You can read the detailed tutorial at http://forum.xda-developers.com/ama...-remove-default-launcher-amazon-fire-t3288310 but basically you run one command, must be done after reboot currently via adb shell:
Noval Launcher on Amazon Fire no-root:
Code:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.teslacoilsw.launcher/.NovaLauncher; done &
That's it. Once you paste that into your adb shell you're done; you now have a default launcher programmatically set via ADB.
Optionally, you can install the modded firelauncher.apk so you can finally delete it without root .
Thanks for your support guys, I love android!
Here is a teaser of my application:
[email protected]:/ $ adb install -r -d com.amazon.firelauncher.apk
/system/bin/sh: adb: not found
im getting this error, so i still c the default launcher for a couple of seconds before it goes to nova launcher
ahac85 said:
[email protected]:/ $ adb install -r -d com.amazon.firelauncher.apk
/system/bin/sh: adb: not found
im getting this error, so i still c the default launcher for a couple of seconds before it goes to nova launcher
Click to expand...
Click to collapse
You are already inside adb shell, type exit then type it again silly
Hello guys.
I stumbled across a reddit thread providing some run shell commands to replace secure settings. The fixes on Android 6.0 allowed me to install and grand the root permissions but never actually worked as intended. Secure settings still returns errors when used.
Long story short I built on the list adding ones I used before from my list.
Here is about 30 most common run shell commands. I will update list if i come across some new ones. Also appreciate your input if you happen to use some good ones.
You can access it all here:
http://www.notenoughtech.com/tasker/tasker-run-shell-commands/
Happy tasking. :good:
Boy, where do I start? The list would be endless. Anyway, here are some, not all, that I use.
Root commands
Open power menu: sendevent /dev/input/event0 1 116 108 && sendevent /dev/input/event0 0 0 0
Restart SystemUI: pkill -l TERM -f com.android.systemui
Safe reboot: svc power reboot
Safe reboot to recovery: svc power reboot recovery
Get list of all system/global/secure settings along with their values; using system settings as example: settings list system
Read system/global/secure setting to a variable; using secure setting accessibility_enabled as example: settings get secure accessibility_enabled
Change system/global/secure setting; using secure setting accessibility_enabled as example: settings put secure accessibility_enabled 0
Make /system rewritable: mount -o remount,rw /system
Make /system read-only: mount -o remount,ro /system
Change file permissions, using /system/etc/hosts as example; numbers are 7 for rwx, 6 for rw, 4 for r; first number is for root (system user), second is for group, third is for all users: chmod 644 /system/etc/hosts
Tap at x,y pixels on screen, using 540,1500 as example: input tap 540 1500
Swipe from x1,y1 to x2,y2, using 540,1500 to 540,300 (swipe up) as example: input swipe 540 1500 540 300
Read/change another app's database; can't give examples as this would need a full tutorial: sqlite3 /path/to/.db_file "sqlite3 commands";
non-root command
Open any app from a variable %package_name containing com.paclage.name; this one is javascript, not shell script [note that you don't want to put % before variable in javascript]: loadApp(package_name, '', false);
Extract %file zip file to /sdcard: unzip %file /sdcard/
Move a file: mv /original/path /new/path
Copy a file: cp /original/path /new/path
Read a file to a variable: cat /path/to/file
Write %var to a file: echo %var > /path/to/file
Delete a file: rm /path/to/file
Delete a folder and all its contents: rm -r /path/to/folder
Check whether a process is doing something or not; set the output to a variable, set a wait for some time, and then get the output again, if output has changed then the process is doing something: ps | grep com.package.name
Sukarn said:
Boy, where do I start? The list would be endless. Anyway, here are some, not all, that I use.
Click to expand...
Click to collapse
Thanks I'm updating the page as I type this! - I completely forgot about file operations if I'm honest. Good to have others to contribute!
quintaar said:
Thanks I'm updating the page as I type this! - I completely forgot about file operations if I'm honest. Good to have others to contribute!
Click to expand...
Click to collapse
You need to proofread that page. There are lots of errors in there that will stump newbs
Sukarn said:
You need to proofread that page. There are lots of errors in there that will stump newbs
Click to expand...
Click to collapse
That's what I'm doing now , trying to put them, in some logical order as well, to make it easy to find, and use. I do appreciate the time taken to type this.
Is input keyevent correct for emulating the power button in a shell command? The # on the website didn't work. I found the generic.kl file in my /system/usr folders and the key # for power listed there did now work with that shell command, either. Even with run as root checked.
{
"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"
}
LeftyGR said:
Is input keyevent correct for emulating the power button in a shell command? The # on the website didn't work. I found the generic.kl file in my /system/usr folders and the key # for power listed there did now work with that shell command, either. Even with run as root checked.
Click to expand...
Click to collapse
I believe hardware keys would be device specific, ego could have different codes.
quintaar said:
I believe hardware keys would be device specific, ego could have different codes.
Click to expand...
Click to collapse
I guess my real question is that the correct shell command as it is written? Because with my specific device key code did not do anything.
Are you trying to do this when the phone display is on or off? this only works when screen is on. input keyevent 26 works fine on my device
quintaar said:
Are you trying to do this when the phone display is on or off? this only works when screen is on. input keyevent 26 works fine on my device
Click to expand...
Click to collapse
On... Guess it does not like me.
LeftyGR said:
On... Guess it does not like me.
Click to expand...
Click to collapse
Do you get any error? My most common mistake is spelling the run shell with upper case, as my keyboard automatically corrects it. And if I forget to change it, it returns an error
quintaar said:
Do you get any error? My most common mistake is spelling the run shell with upper case, as my keyboard automatically corrects it. And if I forget to change it, it returns an error
Click to expand...
Click to collapse
Yes. Appears to be a timeout error.
Background Data On/Off? Thanks in advance
Sent from my hlte using XDA-Developers mobile app
LeftyGR said:
Yes. Appears to be a timeout error.
Click to expand...
Click to collapse
I stumbled on this:
http://forum.xda-developers.com/showthread.php?t=2063741
Perhaps will help you more as well
shaharofir said:
Background Data On/Off? Thanks in advance
Sent from my hlte using XDA-Developers mobile app
Click to expand...
Click to collapse
I've not come across the setting, but try to use:
settings list system
settings list global
settings list secureand see what your device will give you in options lists.
I totally forgot about another shell command that I have set up in Tasker: md5sum /path/to/file
I use it to verify the integrity of downloads in an OTA app I made for a custom ROM using only Tasker.
---------- Post added at 10:52 AM ---------- Previous post was at 10:43 AM ----------
quintaar said:
Are you trying to do this when the phone display is on or off? this only works when screen is on. input keyevent 26 works fine on my device
Click to expand...
Click to collapse
On my phone (OnePlus One), "input keyevent 26" just turns the screen off, while 116 does nothing.
LeftyGR said:
I guess my real question is that the correct shell command as it is written? Because with my specific device key code did not do anything.
Click to expand...
Click to collapse
Did you try the command I posted at the top of my post here? It's the second post in this thread.
quintaar said:
I've not come across the setting, but try to use:
settings list system
settings list global
settings list secure
and see what your device will give you in options lists.
Click to expand...
Click to collapse
Thanks. Will give it a try.
Sukarn said:
I totally forgot about another shell command that I have set up in Tasker: md5sum /path/to/file
.
Click to expand...
Click to collapse
I have added this one as well Thanks
shaharofir said:
Thanks. Will give it a try.
Click to expand...
Click to collapse
Looked, nothing there. Any suggestions?
Sent from my hlte using XDA-Developers mobile app
shaharofir said:
Looked, nothing there. Any suggestions?
Sent from my hlte using XDA-Developers mobile app
Click to expand...
Click to collapse
Perhaps maybe more luck with intents? I'm working on the similar list for it
Sent from my Nexus 6P using Tapatalk
Hey there XDA! I'm here to show off a new Android app I've published that I think a certain audience may find useful.
Ever heard of ADB? If not, you likely won't need this app. But for those of you who have used or encountered ADB in the past, you know that you usually need a PC to shell into your phone. While yes, apps such as Termux exist, they don't have elevated privileges as ADB does.
Behold, LADB! A truly local ADB shell server. That means no root, no computer, and no hassle.
Here's how it works. LADB bundles an ADB server within the app libraries and extracts it upon runtime (W^X compliant). Normally, this server cannot connect to itself because it requires an active USB connection to be visible. However, Android's Wireless ADB Debugging feature allows the server and the client to speak to each other through localhost. LADB initializes the ADB server and asks to connect to localhost, solving this limitation.
So, what can you do with it? Well, anything that ordinarily uses "adb shell <command>" can now be done locally. That means granting apps special privileges for things like SystemUI Tuner, many logcat apps, and generally anything else that needs elevated privileges. That's not all though. You can disable system apps using pm disable-user com.android.whatever, you can enable and disable system overlays with cmd overlay, you can get a logcat with logcat -d | tail -n 20, and the possibilities go on.
Here's the link to the app. It is paid, and it's actually my first paid app in a very long time. If you just need to use the ADB server for a minute, you can buy the app, use it for a few minutes, and then refund it through the store (don't tell Google).
https://play.google.com/store/apps/details?id=com.draco.ladb
Note, this app is also open source! I'm a huge fan of FOSS so I went ahead and published the app on GitHub so that anyone can compile the app for themselves for free. Any purchases through the Google Play store can be considered as donations <3.
https://github.com/tytydraco/ladb
I'm always available for support if you encounter any issues either by direct message, by telegram (@tytydraco), or by email [email protected]. I'll also be answering questions in the comments of this post. Enjoy!
Reserved for any updates or questions
Hi! I bought this app few minutes ago. I haven't tied yet. Can I use this app on 2 phones with the same google account or I have to pay twice?
badmania98 said:
Hi! I bought this app few minutes ago. I haven't tied yet. Can I use this app on 2 phones with the same google account or I have to pay twice?
Click to expand...
Click to collapse
You only need to pay once for it to be in your library
” While we tested this and found it working on essentially every modern Android phone sold in the US in the last four years, not every device is guaranteed to have the Wireless Debugging feature. It's part of AOSP, Android's open source code base, but OEMs sometimes remove functionality from their skinned versions of Android. If your phone doesn't have this option, sadly, LADB won't work for you. ”
Unfortunately my Mate 30 Pro has not this option.
LE: I managed to work.
Anybody tried to use appops https://play.google.com/store/apps/details?id=rikka.appops using ladb?
Is there a way to automate some task, for example after reboot?
Unfortunately my galaxy note 10+ has no wireless adb so i can't try but i hope it will come with android 11...
Yes, well...
alessandro_xda said:
Anybody tried to use appops https://play.google.com/store/apps/details?id=rikka.appops using ladb?
Is there a way to automate some task, for example after reboot?
Unfortunately my galaxy note 10+ has no wireless adb so i can't try but i hope it will come with android 11...
Click to expand...
Click to collapse
I quote myself...
I've a galaxy note 10+ (exynos) on android 10 and in the developer options there is no wireless debugging toggle, nevertheless ladb works!
Now a question: is it possible to execute "adb backup' or 'adb restore' in some way?
alessandro_xda said:
I quote myself...
I've a galaxy note 10+ (exynos) on android 10 and in the developer options there is no wireless debugging toggle, nevertheless ladb works!
Now a question: is it possible to execute "adb backup' or 'adb restore' in some way?
Click to expand...
Click to collapse
This functionality is on it's way
alessandro_xda said:
I quote myself...
I've a galaxy note 10+ (exynos) on android 10 and in the developer options there is no wireless debugging toggle, nevertheless ladb works!
Now a question: is it possible to execute "adb backup' or 'adb restore' in some way?
Click to expand...
Click to collapse
What do you mean by work? can you prompt an adb command?
I've the same device and it doesn't work (NO wireless ADB in devOpts) just waiting
{
"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"
}
when I press reset it gives me this message
And FC's.
Using v1.1.2 under Android 10 with rootfs.
Thanks
rypz79 said:
What do you mean by work? can you prompt an adb command?
I've the same device and it doesn't work (NO wireless ADB in devOpts) just waiting
View attachment 5170637
when I press reset it gives me this message
View attachment 5170639
And FC's.
Using v1.1.2 under Android 10 with rootfs.
Thanks
Click to expand...
Click to collapse
I've just typed ls
alessandro_xda said:
I've just typed lsView attachment 5170783
Click to expand...
Click to collapse
I've no idea why it's not working on my SM-N975F (N10+)
Say what ROM are you using? what kernel? do you have root access (magisk)?
TnXaLoT
rypz79 said:
I've no idea why it's not working on my SM-N975F (N10+)
Say what ROM are you using? what kernel? do you have root access (magisk)?
TnXaLoT
Click to expand...
Click to collapse
I'm on stock rom (unrooted)
I think you only need to start the wireless connection using the cable connected to a pc and then the wireless adb will survive until next reboot
No wireless abd option on A50
I have ladb up and running but I am having trouble getting basic advanced commands to function.
When I enter:
adb shell pwd
It returns:
system/bin/sh: <stdin>[24]: adb: inaccessible or not found
It returns this for every adb command I have tried.
what happens if I disable the system keyboard (Gboard) on my oppo? I'm using SwiftKey and it "fights" with gboard autocorrection...
Tuvor said:
I have ladb up and running but I am having trouble getting basic advanced commands to function.
When I enter:
adb shell pwd
It returns:
system/bin/sh: <stdin>[24]: adb: inaccessible or not found
It returns this for every adb command I have tried.
Click to expand...
Click to collapse
It isn't really a bug. On pc you would always type something like adb {acction} {parameters}. Adb - is the program which is going to be executed so in windows it will be adb.exe (it contains server for adb interface). Action - specifies what adb server should do, so things like devices - list adb devices, shell - open android shell. The last one contains parameters for action, so if you used shell as action it takes shell command as parameter. In this situation, when we use local shell we need to skip adb shell part because we don't have a whole adb server like adb.exe on windows with a lot more options, because we are always using just this adb shell functionality.
pawloland said:
It isn't really a bug. On pc you would always type something like adb {acction} {parameters}. Adb - is the program which is going to be executed so in windows it will be adb.exe (it contains server for adb interface). Action - specifies what adb server should do, so things like devices - list adb devices, shell - open android shell. The last one contains parameters for action, so if you used shell as action it takes shell command as parameter. In this situation, when we use local shell we need to skip adb shell part because we don't have a whole adb server like adb.exe on windows with a lot more options, because we are always using just this adb shell functionality.
Click to expand...
Click to collapse
could you please explain this like I was completely stupid?
I am trying to get running the SystemUITuner. When I enter the path with cd / /storage/emulated/0/Download/platform ecc LADB doesnt show anything. I think that should be ok. But when I then enter ./adb shell pm grant com.zacharee1.systemuituner android.permission.WRITE_SECURE_SETTINGS it tells me "permission dinied".
What am I doing wrong?
mathias.ngr said:
could you please explain this like I was completely stupid?
I am trying to get running the SystemUITuner. When I enter the path with cd / /storage/emulated/0/Download/platform ecc LADB doesnt show anything. I think that should be ok. But when I then enter ./adb shell pm grant com.zacharee1.systemuituner android.permission.WRITE_SECURE_SETTINGS it tells me "permission dinied".
What am I doing wrong?
Click to expand...
Click to collapse
You don't need to type " adb shell"....just type pm grant com.zacharee1.systemuituner android.permission.WRITE_SECURE_SETTINGS
See if that works
Ryano89 said:
You don't need to type " adb shell"....just type pm grant com.zacharee1.systemuituner android.permission.WRITE_SECURE_SETTINGS
See if that works
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That worked. Thanks a lot and have a nice sunday!