First and foremost I am not the developer of this App! I just discovered it and thought those of you missing Greenify might find this useful.
[What's Brevent]
There are a lot of apps which claim to prevent apps from running. However, most of them requires ROOT, or do a system modification via Xposed or patching or unlocked bootloader.
Brevent can app-standby or force-stop apps, prevent apps from running in long time. It doesn't require ROOT, nor modify system. Furthermore, it may doesn't work well on ROOT or modified system. There is an experimental feature to start Brevent Server without adb, please read guide - permissions.
Brevent supports Android 5.0 to Android O DP3, requires "USB debugging" in "developer options". I mainly used it on Google Pixel with Android 7.1.2.
[Simple Guide]
0. (Device) open Brevent, read "Guide"
1. (Device) open Brevent, navigate to "Developer Options", turn on "USB debugging"
2. (PC) Download ADB: https://developer.android.com/studio/releases/platform-tools.html
(If you live in China, you can download it here too: https://developer.android.google.cn/studio/releases/platform-tools.html)
3. (PC) Uncompress, navigate to "platform-tools" directory in Command Line, refer to "Guide - ADB"
4. (PC and Device) connect device and PC with usb cable, type "adb devices" in PC Command Line, and confirm the authorized dialog on Devices if needed
5. (PC) type "adb -d shell sh /data/data/me.piebridge.brevent/brevent.sh" in PC Command Line
[FeedBack]
For any issues, please open an issue at github with logs: https://github.com/brevent/Brevent/issues
1. crash log (in PC's command line): adb -d logcat -d -b crash
2. brevent server log (in PC's command line): adb -d logcat -d -b main -s BreventServer BreventLoader
2.1. enable debug for Brevent Server, type in PC's command line: adb -d shell setprop log.tag.BreventServer DEBUG, then get brevent server log
2.2. disable debug for BreventServer, type in PC's command line: adb -d shell setprop log.tag.BreventServer "" (Note for the back slash)
https://play.google.com/store/apps/details?id=me.piebridge.brevent&hl=en
according to the info, you have to regrant permissions thru ADB every darn reboot or it's useless.
Alternative To Greenify, Native Feature
ggrant3876 said:
First and foremost I am not the developer of this App! I just discovered it and thought those of you missing Greenify might find this useful.
[What's Brevent]
There are a lot of apps which claim to prevent apps from running. However, most of them requires ROOT, or do a system modification via Xposed or patching or unlocked bootloader.
Brevent can app-standby or force-stop apps, prevent apps from running in long time. It doesn't require ROOT, nor modify system. Furthermore, it may doesn't work well on ROOT or modified system. There is an experimental feature to start Brevent Server without adb, please read guide - permissions.
Brevent supports Android 5.0 to Android O DP3, requires "USB debugging" in "developer options". I mainly used it on Google Pixel with Android 7.1.2.
[Simple Guide]
0. (Device) open Brevent, read "Guide"
1. (Device) open Brevent, navigate to "Developer Options", turn on "USB debugging"
2. (PC) Download ADB: https://developer.android.com/studio/releases/platform-tools.html
(If you live in China, you can download it here too: https://developer.android.google.cn/studio/releases/platform-tools.html)
3. (PC) Uncompress, navigate to "platform-tools" directory in Command Line, refer to "Guide - ADB"
4. (PC and Device) connect device and PC with usb cable, type "adb devices" in PC Command Line, and confirm the authorized dialog on Devices if needed
5. (PC) type "adb -d shell sh /data/data/me.piebridge.brevent/brevent.sh" in PC Command Line
[FeedBack]
For any issues, please open an issue at github with logs: https://github.com/brevent/Brevent/issues
1. crash log (in PC's command line): adb -d logcat -d -b crash
2. brevent server log (in PC's command line): adb -d logcat -d -b main -s BreventServer BreventLoader
2.1. enable debug for Brevent Server, type in PC's command line: adb -d shell setprop log.tag.BreventServer DEBUG, then get brevent server log
2.2. disable debug for BreventServer, type in PC's command line: adb -d shell setprop log.tag.BreventServer "" (Note for the back slash)
https://play.google.com/store/apps/details?id=me.piebridge.brevent&hl=en
Click to expand...
Click to collapse
One of the reasons I rate this phone so highly is that there are plenty of 'native' features present that make rooting less necessary.
My phone is a UK Sky Mobile Exynos model, and under 'Maintenance', 'Battery' there is an option to put 'non running' apps to sleep, just like 'Greenify'. I don't know if this is true for other regions or carrier's. Maybe other people can check this to see if it's so for their region and carrier.
kxdaorbit said:
One of the reasons I rate this phone so highly is that there are plenty of 'native' features present that make rooting less necessary.
My phone is a UK Sky Mobile Exynos model, and under 'Maintenance', 'Battery' there is an option to put 'non running' apps to sleep, just like 'Greenify'. I don't know if this is true for other regions or carrier's. Maybe other people can check this to see if it's so for their region and carrier.
Click to expand...
Click to collapse
I agree with you on the phone but there are two features that I miss with root.
1. Titanium Backup - they ability to back up your apps and data. I know there is Samsung Cloud but I'm not a big fan of cloud based services.
2. TWRP - the ability to back up your whole phone and restore it if needed.
ggrant3876 said:
I agree with you on the phone but there are two features that I miss with root.
1. Titanium Backup - they ability to back up your apps and data. I know there is Samsung Cloud but I'm not a big fan of cloud based services.
2. TWRP - the ability to back up your whole phone and restore it if needed.
Click to expand...
Click to collapse
I get your apprehension about cloud based services, but this is 2017, you'll have to bite the bullet sooner rather than later.
Also don't forget, if you have really super sensitive or personal data that you can't trust to cloud based services, we have 'Smart Switch'. Enables you to make as close to a 'nandroid' backup as is possible, and to store it locally. You can then restore single elements or the whole phone. Thank you Samsung.
kxdaorbit said:
I get your apprehension about cloud based services, but this is 2017, you'll have to bite the bullet sooner rather than later.
Also don't forget, if you have really super sensitive or personal data that you can't trust to cloud based services, we have 'Smart Switch'. Enables you to make as close to a 'nandroid' backup as is possible, and to store it locally. You can then restore single elements or the whole phone. Thank you Samsung.
Click to expand...
Click to collapse
Yes I read a thread yesterday that said you can use Smart Switch and back it up to your sdcard. It's getting better, I started with the T-Mobile G-1 and the only way to root and even do screenshots was with adb. I learned adb and it has served me well on android, even on the S8+ to get rid of the battery icon I had to run a few commands to get SystenTuner UI to work.
Why don't you just use Samsung built in always sleeping option for apps? Works great
Compusmurf said:
according to the info, you have to regrant permissions thru ADB every darn reboot or it's useless.
Click to expand...
Click to collapse
If you have rooted, it's not problem.
And if you don't have rooted, no other alternative third-party apps can app-standby other apps or force-stop apps quickly.
I am rooted, but the app doesnt seem to see that I am rooted.
MrPhilo said:
Why don't you just use Samsung built in always sleeping option for apps? Works great
Click to expand...
Click to collapse
I agree, s8 already have functions to put your apps to sleep immediately without waiting 3 days.
{
"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"
}
Sent from my SM-G955F using Tapatalk
BratPAQ said:
I agree, s8 already have functions to put your apps to sleep immediately without waiting 3 days.
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
how do you get here ?
crayonyes said:
how do you get here ?
Click to expand...
Click to collapse
Settings - Device Maintenance - Battery
Then at the very bottom is "always sleeping apps"
Sent from my SM-G955F using Tapatalk
BratPAQ said:
Settings - Device Maintenance - Battery
Then at the very bottom is "always sleeping apps"
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
got it, Thanks
Where is the experimental feature to start server without adb?
mrQQ said:
Where is the experimental feature to start server without adb?
Click to expand...
Click to collapse
suku_patel_22 said:
I am rooted, but the app doesnt seem to see that I am rooted.
Click to expand...
Click to collapse
]
Compusmurf said:
according to the info, you have to regrant permissions thru ADB every darn reboot or it's useless.
Click to expand...
Click to collapse
If you have Root
Just press "back" about 6 times
And then a new menu appears
There you press on "ROOT"....
Related
DISCLAIMER:
I'm not responsible for damage to your phone or watch.
You are using this app at your own responsibility
WearToolbox was just an idea to make life easier.
With WearToolbox you can connect from your phone to your watch through adb, with this it's possible to send commands or sideload apps etc. (see features).
For now design doesn't matter for me, functionality does. Design will be better when app is in a further stage.
When enough people have tested it and provided me feedback, it will be released in the Play Store for easier updating.
The app is in DEVELOPMENT and TEST stage and can have BUGS.
Tested on LG Watch R with Android Wear 5.1.1 and LG G2 5.0.2
Have fun with it and let me know if it works or not!
FEATURES
- Automatic installation of necessary binaries (adb -> /system/bin/)
- Automatic connection
- Reboot (system, recovery, bootloader)
- Sideload apps (/sdcard/WearToolbox/sideload/)
- Uninstall apps
- Push files to /sdcard/
- Send adb commands (adb command)
- Send shell commands (adb shell command)
- ADB and shell command history
- Script parser for own created scripts
TODO:
- Make a nicer UI
IDEAS:
- Pull files
- ADB filebrowser
REQUIREMENTS
- Enabled debug and bluetooth debug on android watch, developer options (youtube)
- Enabled debug on phone, developer options
- Enabled debug in Android Wear app, under settings
- Rooted phone
FAQ:
Q: How to use root with shell:
A:
Code:
"su -c '[COMMAND]'"
Snippets:
Code:
"su -c 'echo 85 > /sys/class/timed_output/vibrator/amp'"
Code:
"su -c 'echo 120 > /sys/class/timed_output/vibrator/driving_ms'"
Code:
wm density 200
Q: How to sideload apps:
A: Place apk in the folder /sdcard/WearToolbox/sideload/, restart WearToolbox, choose right apk, click sideload, wait a long time
Q: How to use scripts:
A: Make for example a dummy.txt file in /sdcard/WearToolbox/scripts/ with shell commands in it. Each command on a newline. Save it, restart WearToolbox, test it.
Example (vibrate.txt):
Code:
cat /sys/class/timed_output/vibrator/amp
cat /sys/class/timed_output/vibrator/driving_ms
"su -c 'echo 85 > /sys/class/timed_output/vibrator/amp'"
"su -c 'echo 120 > /sys/class/timed_output/vibrator/driving_ms'"
cat /sys/class/timed_output/vibrator/amp
cat /sys/class/timed_output/vibrator/driving_ms
DOWNLOAD
https://play.google.com/apps/testing/com.diechel.xda.weartoolbox
I might go ahead and try this. Having something like this would be very very useful. (fyi, I believe you initial change log date has the wrong month. Unless it is June 31st already)
Rennat said:
I might go ahead and try this. Having something like this would be very very useful. (fyi, I believe you initial change log date has the wrong month. Unless it is June 31st already)
Click to expand...
Click to collapse
Haha yes youre right about the changelog Will change.
Let me know if it works and what you think about it.
What features would you like etc etc.
stuck on "Checking Connection" for me Sammy 5.1.1 S6 Edge (arm64) and LGWR 5.1.1
EDIT - seems to download binaries every time I open the app, still won't connect - perhaps something to do with arm64 architechture ???
EDIT2 - in Android Wear Manager bluetooth debugging ON, it says HOST disconnected, TARGET connected
kashortiexda said:
stuck on "Checking Connection" for me Sammy 5.1.1 S6 Edge (arm64) and LGWR 5.1.1
EDIT - seems to download binaries every time I open the app, still won't connect - perhaps something to do with arm64 architechture ???
EDIT2 - in Android Wear Manager bluetooth debugging ON, it says HOST disconnected, TARGET connected
Click to expand...
Click to collapse
- Can you check if the files 'adb' and 'fastboot' are present in /system/bin/
- What is there permission? should be 755
- Are the files 'adb' and 'fastboot' on your root of your /sdcard/
- Can you type 'adb' and 'fastboot' in terminal and post output
- Can you type 'mount -o remount, rw /system' in terminal and post output
For me HOST and TARGET are connected in Android Wear App
@Diechel , I have adb but not fastboot in /system/bin
Okay copied adb and fastbook to /system/bin and 755'd them.
{
"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"
}
kashortiexda said:
Okay copied adb and fastbook to /system/bin and 755'd them.View attachment 3343013
Click to expand...
Click to collapse
i see something weird
Code:
localhost:4444:4444
should be
Code:
localhost:4444
Will look if i can find something.
Also wondering why copying didnt work, was searching all over the internet how to correctly remount /system
My output is as follows, see attachment. Of course a newer version but nothing changed to adb init
@Diechel am I supposed to have my watch or phone plugged into my PC by USB when doing all this / running weartoolbox ?
kashortiexda said:
@Diechel am I supposed to have my watch or phone plugged into my PC by USB when doing all this / running weartoolbox ?
Click to expand...
Click to collapse
No just bluetooth connected to each other.
And all the 3 debugging option on as stated in the OP
Edit:
Build 21 online
Yip got all that but no adb devices and the localhost:4444:4444 is clearly wrong
Would a logcat help
kashortiexda said:
Yip got all that but no adb devices and the localhost:4444:4444 is clearly wrong
Would a logcat help
Click to expand...
Click to collapse
I dont know if logcat helps, what you can try is manually connect with terminal on your phone.
Code:
su
adb kill-server
setprop service.adb.tcp.port 5555
stop adbd
start adbd
adb forward tcp:4444 localabstract:/adb-hub
adb connect localhost:4444
adb devices
Each line need to be filled in, not all together.
And try build 21
Did the manual Terminal stuff and it FIXED the 4444 problem, installed v21 and.....[emoji1]
kashortiexda said:
Did the manual Terminal stuff and it FIXED the 4444 problem, installed v21 and.....[emoji1]
View attachment 3343080
Click to expand...
Click to collapse
TADAAAAAA
GOOD!
Let me know if you have ideas to implement. First i go for functionality then change the user interface a bit
@Diechel
EDIT: I tried sideloading es file explorer apk ... worked !!! [emoji1]
kashortiexda said:
@Diechel I tried sideloading es file explorer apk ...it says done but nothing on watch.
Have you successfully sideloaded any apks ?
Click to expand...
Click to collapse
Yes i had, will try again.
It takes some time for the watch to install, will try now and report back!
Edit:
From what i see now is that the message done comes too fast.
Bluetooth is slow and is still transferring after the done message, can see that in my top bar.
Seems not working indeed, will check thanks
EDIT:
It got installed after a while
Good that it is working! Will see how i can report in log
I got it installed too, yes the done is misleading .... GREAT app btw, well done [emoji106] [emoji106]
kashortiexda said:
I got it installed too, yes the done is misleading .... GREAT app btw, well done [emoji106] [emoji106]
Click to expand...
Click to collapse
Haha thank you, now there is a message that you need to wait untill it arrives on your watch, bluetooth is slow
@Diechel are you planning on adding the trickier "adb remove sideloaded app" but I think it may not be possible. .
kashortiexda said:
@Diechel are you planning on adding the trickier "adb remove sideloaded app" but I think it may not be possible. .
Click to expand...
Click to collapse
Can try at least, I think it's possible. Maybe a lot of work
I was looking at a toshiba chromebook 2 but was wondering if you can root a phone on it as i wanted to root my G4.
Sent from my LG-H811 using XDA Free mobile app
Technically yes but you will have to root the Chromebook first to gain access to the Linux command line to install the adb software as root
mrme73 said:
Technically yes but you will have to root the Chromebook first to gain access to the Linux command line to install the adb software as root
Click to expand...
Click to collapse
Is it an easy process? Ive been rooting since 2011 so i can't imagine rooting a chrome book would be too hard?
Sent from my LG-H811 using XDA Free mobile app
I don't think it's that hard but I've only tried it when testing it for a netbook. You will have to search that model as it varies. Usually called developer mode and dual booting with another Linux distribution.
Yes. You just need to enable developer mode, install Arch Linux, disable software verification settings, and obtain adb/fastboot via command prompt (although the versions may or may not be outdated).
kibmikey1 said:
Yes. You just need to enable developer mode, install Arch Linux, disable software verification settings, and obtain adb/fastboot via command prompt (although the versions may or may not be outdated).
Click to expand...
Click to collapse
Hi, I'm trying to flash Marshmallow on my Nexus 7 using my Dell Chromebook. I'm almost there but my N7 says I have to update my ADB to 1.0.32. Unfortunately Ubuntu hasn't updated their repositories so any idea how I can update ADB on my chromebook?
thanks
Sent from my D6503 using Tapatalk
mrme73 said:
Technically yes but you will have to root the Chromebook first to gain access to the Linux command line to install the adb software as root
Click to expand...
Click to collapse
if i do this will it "root" my phone so I can get apps that require root?
Also, I have a galaxy j3 eclipse, will this work on my phone
rickyiswhite said:
I was looking at a toshiba chromebook 2 but was wondering if you can root a phone on it as i wanted to root my G4.
Sent from my LG-H811 using XDA Free mobile app
Click to expand...
Click to collapse
Yes you can root a phone on a chromebook just put it in developer mode and use your crosh shell to run adb and fastboot.
There is a lack of information and a bit of misinformation here. You don't "root" your chromebook and you don't have to install Arch Linux. So here is the breakdown. If you want to root your phone you can do so by using ADB. To do this you have to do a few things:
1. Enable Developer mode on your chromebook (this requires a powerwash which will delete data and reset your chromebook)
2. Open Crosh by pressing Ctrl + Alt + T
3. Type "shell" and press enter.
4. Update ADB and move the binaries to their appropriate location by typing:
Code:
curl -s https://raw.githubusercontent.com/nathanchance/chromeos-adb-fastboot/master/install.sh | bash
5. Make sure ADB is working by typing "adb --version" and pressing enter. This will tell you the version of ADB that is installed, which the current version is 1.0.40 Typing "adb --version" will also tell you where ADB has been installed to. This should say: /usr/local/bin
6. Enable Developer Mode on your phone and enable USB Debugging within the Developer settings.
7. Test that you can communicate with your phone by typing "adb devices" with your phone connected to your chromebook. If your device shows up make sure that you can send data to your phone by typing "adb reboot recovery". This should reboot your device into recovery.
8. If you were able to successfully reboot your phone into recovery using ADB then you have everything you need to root your phone using your chromebook. Just look up how to root your phone using ADB and you will be good to go. This is the method I used to unlock my Bootloader, install a Custom Recovery and the method I used to root my OnePlus 6T with Magisk.
phone not connecting
What do i do if phone does not connect?
how do i put the TWRP.img file into the same folder where the fastboot and adb files are? or how do i type the command to flash it to my oneplus 7 pro in my crosh shell window.
I am able to unlock my boot-loader via adb and and fastboot but cant find away to access the Chromebooks file system to flash twrp and and custom roms. help!!! Im attempting to convert the Moto G7 to a more secure linux rom.
lonnie89 said:
I am able to unlock my boot-loader via adb and and fastboot but cant find away to access the Chromebooks file system to flash twrp and and custom roms. help!!! Im attempting to convert the Moto G7 to a more secure linux rom.
Click to expand...
Click to collapse
On my pixelbook with the beta Linux installed copy the downloadet twrp.img file to the linux folder that's located in the files app. Should then show up in your home Linux directory.
How do I get access to that file system in croots and flash it to the phone.
How do I get access to the file and move to the phone in croots what are the commands. It's my my downloads folder.
garretts228 said:
There is a lack of information and a bit of misinformation here. You don't "root" your chromebook and you don't have to install Arch Linux. So here is the breakdown. If you want to root your phone you can do so by using ADB. To do this you have to do a few things:
1. Enable Developer mode on your chromebook (this requires a powerwash which will delete data and reset your chromebook)
2. Open Crosh by pressing Ctrl + Alt + T
3. Type "shell" and press enter.
4. Update ADB and move the binaries to their appropriate location by typing:
Code:
curl -s https://raw.githubusercontent.com/nathanchance/chromeos-adb-fastboot/master/install.sh | bash
5. Make sure ADB is working by typing "adb --version" and pressing enter. This will tell you the version of ADB that is installed, which the current version is 1.0.40 Typing "adb --version" will also tell you where ADB has been installed to. This should say: /usr/local/bin
6. Enable Developer Mode on your phone and enable USB Debugging within the Developer settings.
7. Test that you can communicate with your phone by typing "adb devices" with your phone connected to your chromebook. If your device shows up make sure that you can send data to your phone by typing "adb reboot recovery". This should reboot your device into recovery.
8. If you were able to successfully reboot your phone into recovery using ADB then you have everything you need to root your phone using your chromebook. Just look up how to root your phone using ADB and you will be good to go. This is the method I used to unlock my Bootloader, install a Custom Recovery and the method I used to root my OnePlus 6T with Magisk.
Click to expand...
Click to collapse
Hi. Thanks for a working method. I have tried each step and Crosh gave me error:
bash: /usr/local/bin/adb: cannot execute binary file: Exec format error
One question - do i have to be on "developer channel" in Chromebook?
Coz then i will have to reinstall Chromebook.
Best Regards
Nick
{
"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"
}
Finally yes - i need to be in Developer mode for ADB.
Full article is here - how to and what is what.
How to Use ADB and Fastboot on a Chromebook
For a long time, Chromebook users who also need access to the Android Debug Utility (ADB) and Fastboot for Android devices were left with one option: Crouton. Now, however, both ADB and Fastboot are included in Chrome OS. Here’s how to access them.
www.howtogeek.com
eurovive said:
Finally yes - i need to be in Developer mode for ADB.
Full article is here - how to and what is what.
How to Use ADB and Fastboot on a Chromebook
For a long time, Chromebook users who also need access to the Android Debug Utility (ADB) and Fastboot for Android devices were left with one option: Crouton. Now, however, both ADB and Fastboot are included in Chrome OS. Here’s how to access them.
www.howtogeek.com
Click to expand...
Click to collapse
Sorry I didn't leave that detail behind for you, but yes that method does indeed require dev mode. However there are other methods that don't require it now using Linux. I have not done them so I am only forwarding this information:
https://www.reddit.com/r/chromeos/comments/dtwfpm
Thats a nice suggestion too. As someone says Chromebook should be Intel-ready to run Android apps, thats why i was thinking whats wrong. I have Arm based Tegra K1 with saying some how limited support of updates, therefore having support for Crostini feature. Will try later.
Hello,
I have a daughter and she's using the Galaxy S2, with LineageOS 16 (Android 9) as her phone. I want to block app installation from unknown sources completely, since this is a security threat and she can install anything. I've scavenged Google for about 2 hours and can't find a way to block app installation, even with root.
Uninstalling the PackageInstaller isn't a way, that puts the phone in a bootloop (since PackageInstaller is also used for managing permissions from Android 6)
Disabling unknown sources in the settings isn't enough, since when you open an APK file, it opens a dialog which links you to the settings option
I don't want to lock the entire settings with an AppLock since she needs to access Wi-Fi and other settings
Is there any way to do this?
Blocking certain file types or downloading them would be enough, but I can't find a way to do that either.
Thanks.
You can use the Play Store's parental controls to restrict or block app installation on the Android device.
Using your child's device, open the Play Store app and tap the menu in the top left corner. Choose Settings and then Parental controls, and turn on the controls. Choose a PIN your kids won't know and tap the kind of content – in this case, apps and games – you want to restrict. Essentially, you've set a password for Google Play free downloads.
Aside from basic downloading, you also want to restrict paid apps and in-app purchases. Apps specifically targeted at kids 12 and under already block unauthorized purchases, but to make it universal, you need to go back to the main Parental Controls menu and choose Require authentication for purchases. Set it to All purchases, which means your PIN must be entered for any purchase.
No, that's not what I want. She doesn't have Play Store on the device, just the browser, through which she can download .apk files to install apps.
TramSK said:
No, that's not what I want. She doesn't have Play Store on the device, just the browser, through which she can download .apk files to install apps.
Click to expand...
Click to collapse
If device is rooted another option is to freeze both the Android's "Package Installer" app ( com.android.packageinstaller ) and "Package Manager" - what is an Android service: "Packet Manager" service gets invoked by "Package Installer" app.
jwoegerbauer said:
If device is rooted another option is to freeze both the Android's "Package Installer" app ( com.android.packageinstaller ) and "Package Manager" - what is an Android service: "Packet Manager" service gets invoked by "Package Installer" app.
Click to expand...
Click to collapse
How would I do that? Wouldn't it cause a bootloop like when I removed it completely?
TramSK said:
How would I do that? Wouldn't it cause a bootloop like when I removed it completely?
Click to expand...
Click to collapse
A1: By means of ADB
Code:
adb shell pm disable com.android.packageinstaller
A2: Don't know it.
jwoegerbauer said:
A1: By means of ADB
Code:
adb shell pm disable com.android.packageinstaller
A2: Don't know it.
Click to expand...
Click to collapse
Nope, that's unfortunately not possible. ADB doesn't allow that:
Code:
java.lang.SecurityException: Shell cannot change component state for com.android.packageinstaller/null to 2
TramSK said:
Nope, that's unfortunately not possible. ADB doesn't allow that:
Code:
java.lang.SecurityException: Shell cannot change component state for com.android.packageinstaller/null to 2
Click to expand...
Click to collapse
The ADB command - as an example above shown by me - should work, if the Android device is rooted means run in superuser-mode ( aka ROOT ). Sorry I forgot to mention it: Didn't know you aren't familiar with this.
jwoegerbauer said:
The ADB command - as an example above shown by me - should work, if the Android device is rooted means run in superuser-mode ( aka ROOT ). Sorry I forgot to mention it: Didn't know you aren't familiar with this.
Click to expand...
Click to collapse
Ah right, I didn't know I had to run adb in root mode. Let me try. :good:
That puts the phone in a bootloop, similarly to when I removed it completely. That's not the way unfortunately.
Wait, perhaps I could disable a specific activity of PackageInstaller? Would that work? I can't find any info on that online, just that you can also disable an activity by doing
Code:
adb shell pm disable <package>/.<activity>
TramSK said:
Wait, perhaps I could disable a specific activity of PackageInstaller? Would that work? I can't find any info on that online, just that you can also disable an activity by doing
Code:
adb shell pm disable <package>/.<activity>
Click to expand...
Click to collapse
I think you've to revoke app's permission "INSTALL_PACKAGES"
{
"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"
}
Code:
adb shell pm revoke com.android.packageinstaller android.permission.INSTALL_PACKAGES
FYI: Haven't tried it.
jwoegerbauer said:
I think you've to revoke app's permission "INSTALL_PACKAGES"
Code:
adb shell pm revoke com.android.packageinstaller android.permission.INSTALL_PACKAGES
FYI: Haven't tried it.
Click to expand...
Click to collapse
Nope:
Code:
java.lang.SecurityException: Permission android.permission.INSTALL_PACKAGES is not a changeable permission type
And yes, I'm in SU mode.
Bump
Is there really no way to do this in Android? Such a shame, I thought this was achievable.
Any solutions found? It is like I went through all those commands in exact same order and then I found this post.....
Working?:
adb shell pm disable com.android.packageinstaller/.PackageInstallerActivity
If the name ever changes, I think we can always use the following to obtain the new component name?
adb shell dumpsys activity activities | grep mResumedActivity
No effect:
adb shell appops set com.android.packageinstaller RUN_IN_BACKGROUND deny
Bootloop:
adb shell cmd package hide com.android.packageinstaller
SmartestKen said:
Working?:
adb shell pm disable com.android.packageinstaller/.PackageInstallerActivity
If the name ever changes, I think we can always use the following to obtain the new component name?
adb shell dumpsys activity activities | grep mResumedActivity
No effect:
adb shell appops set com.android.packageinstaller RUN_IN_BACKGROUND deny
Bootloop:
adb shell cmd package hide com.android.packageinstaller
Click to expand...
Click to collapse
And what is with one of this steps?
3 Ways to Block Kids From Installing Apps On Their Android Phone | Boomerang - Best Parental and Screen Time Controls for Android mobile devices
I don’t know about your kids, but mine just love to browse the Google Play Store for new apps to download and install. It drives me crazy. They have plenty of apps and games on their devices, and …
useboomerang.com
Tab A7 stock rootless setup
model used: Tab A7 Lite SM-T220
Just a quick article for this nicely sized 8.7" tablet. It's a baby tablet, not wasting time with rooting We want:
* debloating
* better battery
* better privacy
* call recording
* disk encryption
* tweaks
RootingNo rooting. No logins, not even Google login, that's the plan. FDroid, Aurora, Vanced manager to deploy all you need. No contacts, no SMS, no location, nothing to protect.
ModulesMagisk-
XPosed-
Apps* AdGuard -> supreme adblocker and firewall. Set VPN approach (rootless friendly, assuming device will stay at home), turn on HTTPS and turn off internet for all apps. Then enable few (browser, youtube, aurora) specifically.
* YouTube Vanced -> YouTube without ads and sponsor blocks.. install in non root mode, and remove the existing originals
* (optional) MiXplorer -> best file manager, replaces spyware ES File explorer you had before
* F-Droid -> open source apps
* Aurora -> all apps
DebloatingWhat the script does:
* choose 8 categories of app removal, in the beginning of the file
for each say 0=skip 1=remove 2=revert back
* use more switch to disable some questionable/helpful stuff
* disable up to 70 apps with possibility to revert back
I usually cook these files carefully, here i just removed non existing packages, added existing vendor packages. Vendor garbage gets uninstalled straight away, majority of packages is disabled in non-root mode (per user) so it can be reenabled later. You can edit the file.
unzip the file to some folder
adb shell as it's plugged to PC and authorized (and usb debugging in developer otions on)
go to the folder with script
cp TabA7_cleanup.sh /data/local/tmp
chmod +x /data/local/tmp/TabA7_cleanup.sh
/data/local/tmp/TabA7_cleanup.sh;
Tested ok on August Android 11 EU firmware. It produced no errors (=packages relevant), but there could be regional differences, producing exceptions in your case. See other comments below if the instructions are unclear.
Download: (file attached)
BatteryBattery saving:
turn off location
turn off permissions and app usage for usual snitches
in Adguard turn off WIFI/mobile for each app (will be the default), then reenable few - advantage: no ads in games, no stupid accidental payments. Also set WIFI/mobile off when screen off -> tablet won't do anything, just keep idle for days hopefully
don't even enable GMS, this device can be a good throwawy tablet with no login to ANY service, without encryption, just pure gamepad.... likely no password/PIN to unlock. It's with slow CPU but games work nicely. It's not even slower than S4 flagship tablet honestly.
hi, thanks for the guide, very insightful with me transitioning from iOS.
My only question is the script, I’ve downloaded ABD and can shell into my device. However I’m having issues when copying the script, it keeps coming up saying invalid path, I’ve looked everywhere for a tutorial but with me having limited knowledge I’m at a dead end
any help greatly appreciated
Herb291 said:
hi, thanks for the guide, very insightful with me transitioning from iOS.
My only question is the script, I’ve downloaded ABD and can shell into my device. However I’m having issues when copying the script, it keeps coming up saying invalid path, I’ve looked everywhere for a tutorial but with me having limited knowledge I’m at a dead end
any help greatly appreciated
Click to expand...
Click to collapse
i just flashed the new firmware and did it again, no problem. First i copied the script from Windows to somewhere on Android (/storage/emulated/0 or similar "noexec" quasi-sd card location), and then moved it to a location from where it can be executed. The location should work and is generally recommended. You can find another one /data/local, /tmp or whatever is there. Or use adb push <PC_file> <target_directory>. Or post the screenshot. This should be a trivial issue and can't stop you.
{
"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"
}
getting this error
raxahasan0077 said:
View attachment 5456865getting this error
Click to expand...
Click to collapse
Place the script on the tablet in an easy to remember location.
Open Powershell:
“adb shell” or “./abd shell” (whichever works)
“Cp /storage/emulated/0/FILELOCATION/TabA7_cleanup.sh /data/local/tmp”
then follow the rest of the instructions
now getting this error
raxahasan0077 said:
now getting this errorView attachment 5456963
Click to expand...
Click to collapse
Is your USB debugging turned on in the dev settings, did you hit authorise on your device when you first plugged it in?
you can check if you’re device is authorised with “adb devices”
edit: not sure if it matters but try a lowercase cp
Herb291 said:
Is your USB debugging turned on in the dev settings, did you hit authorise on your device when you first plugged it in?
you can check if you’re device is authorised with “adb devices”
edit: not sure if it matters but try a lowercase cp
Click to expand...
Click to collapse
yeah lowercase cp works
Working with LADB ( no computer needed)
https://www.xda-developers.com/debloat-your-phone-run-adb-shell-commands-no-root-no-pc/
Download: https://disk.yandex.com/d/H02YifGGtrErbw
////////////Run an .sh file to install ///////////
cd /sdcard
cp cleanup.sh /data/local/tmp
cd /data/local/tmp
ls -l
chmod +x /data/local/tmp/cleanup.sh
ls -l
./cleanup.sh
/////////
Download: https://disk.yandex.com/d/NcQMhFp73OpwXw
( and run .sh script with LADB)
Tips howto install LADB:
important! Always use "Open in split screen view” for pairing devices. (only first connection, next time don't need)
View attachment 5457089
@tom.android have you removed all theese 41 apps and the tablet functions ok, without any problems ? Is there any real benefit in performance and especially in lagging ?
Reply: @nikoum
Just removed (switch off) my unused app, sorry not help for good performance but no trouble.
Note: LADB
https://forum.xda-developers.com/attachments/ladb_v1-7_test-zip.5457295/
How dose this work without rooting? When I try to run the script from ADB i get Can't execute: permission denied?
I run "cmd", then "adb shell" and then "pm uninstall --user 0 <package name>". Make sure in developer options to check USB debugging to on and when connecting device with usb cable, authorize the conneftion, when asked by the phone.
doggydog2 said:
Tab A7 stock rootless setup
model used: Tab A7 Lite SM-T220
Just a quick article for this nicely sized 8.7" tablet. It's a baby tablet, not wasting time with rooting We want:
* debloating
* better battery
* better privacy
* call recording
* disk encryption
* tweaks
RootingNo rooting. No logins, not even Google login, that's the plan. FDroid, Aurora, Vanced manager to deploy all you need. No contacts, no SMS, no location, nothing to protect.
ModulesMagisk-
XPosed-
Apps* AdGuard -> supreme adblocker and firewall. Set VPN approach (rootless friendly, assuming device will stay at home), turn on HTTPS and turn off internet for all apps. Then enable few (browser, youtube, aurora) specifically.
* YouTube Vanced -> YouTube without ads and sponsor blocks.. install in non root mode, and remove the existing originals
* (optional) MiXplorer -> best file manager, replaces spyware ES File explorer you had before
* F-Droid -> open source apps
* Aurora -> all apps
DebloatingWhat the script does:
* choose 8 categories of app removal, in the beginning of the file
for each say 0=skip 1=remove 2=revert back
* use more switch to disable some questionable/helpful stuff
* disable up to 70 apps with possibility to revert back
I usually cook these files carefully, here i just removed non existing packages, added existing vendor packages. Vendor garbage gets uninstalled straight away, majority of packages is disabled in non-root mode (per user) so it can be reenabled later. You can edit the file.
unzip the file to some folder
adb shell as it's plugged to PC and authorized
go to the folder with script
cp TabA7_cleanup.sh /data/local/tmp
chmod +x /data/local/tmp/TabA7_cleanup.sh
/data/local/tmp/TabA7_cleanup.sh;
Tested ok on August Android 11 EU firmware. It produced no errors (=packages relevant), but there could be regional differences.
Download: (file attached)
BatteryBattery saving:
turn off location
turn off permissions and app usage for usual snitches
in Adguard turn off WIFI/mobile for each app (will be the default), then reenable few - advantage: no ads in games, no stupid accidental payments. Also set WIFI/mobile off when screen off -> tablet won't do anything, just keep idle for days hopefully
don't even enable GMS, this device can be a good throwawy tablet with no login to ANY service, without encryption, just pure gamepad.... likely no password/PIN to unlock. It's with slow CPU but games work nicely. It's not even slower than S4 flagship tablet honestly.
Click to expand...
Click to collapse
How do I get the script file to.run from ADB? I get permission denied
TheDroidKid said:
How do I get the script file to.run from ADB? I get permission denied
Click to expand...
Click to collapse
that's literally discussed above incl all common mistakes, if you think it's unique, please post a screenshot.
Your right got it working. Didn't releaize it was a big deal not to have it in /tmp
I keep trying to do the cp step but it keeps saying no such file or directory.
I checked my tablet with MiX and there's no local folder on data... What am I doing wrong here?
Is better privacy only possible with rooting? I want to disable the radio entirely and remove all of the Google apps.
Elzbach said:
Is better privacy only possible with rooting? I want to disable the radio entirely and remove all of the Google apps.
Click to expand...
Click to collapse
i disabled google, and using Aurora without root. With no logins, no PIM data, no location tracking, there's almost no data to steal. But if I was using it as a mobile phone, with logins, contacts etc, i'd have to root.
doggydog2 said:
i disabled google, and using Aurora without root. With no logins, no PIM data, no location tracking, there's almost no data to steal. But if I was using it as a mobile phone, with logins, contacts etc, i'd have to root.
Click to expand...
Click to collapse
I'm not using it as a phone and there is still no data to steal, but I still want to get rid of those things. I want to completely remove the tracking apps regardless of how little there is to track because they are bloat. I want to completely disable the radio, the microphone, gps, and blu tooth. I don't even want wireless internet connections to remain.
How to use?
1. Enable ADB Debugging from Fire TV settings
2. In this app, add the adb commands that you want to execute on every boot
3. Set whether you want to display a Toast message on completion of command execution
4. Test the script if you want by pressing "Test Script" button.
5. Apply the configs by pressing the apply button.
Support the work by purchasing it from here
Note: when you run this app for the first time, you should press the test script button, so that app can acquire adb permission. If you don't do this, then the adb permission prompt would appear when you boot the stick for the first time, after installing and opening this app.
That's all
Also note that, the commands you'll write here should be without "adb shell" prefix.
For example,
you have to write
echo "Hello World"
and not
adb shell echo "Hello World"
{
"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"
}
(or multiple commands separated by semi-colon ' ; ' )
Awesome thanks!
Is it possible to combine commands with ; or add a delay?
Spamm00r said:
Awesome thanks!
Is it possible to combine commands with ; or add a delay?
Click to expand...
Click to collapse
Yes you can add multiple commands with ; and add a delay using sleep command.
Example,
sleep 3; echo "I'm here after 3 seconds";
Shaikh Amaan FM said:
Yes you can add multiple commands with ; and add a delay using sleep command.
Example,
sleep 3; echo "I'm here after 3 seconds";
Click to expand...
Click to collapse
Perfect!
Did you test wether you can use this app to issue "adb tcpip 5555" command at bot so that the adb wifi tasker function can do the rest? Thatway we would have adb shell on a non rooted device all the time.
Spamm00r said:
Perfect!
Click to expand...
Click to collapse
let me know if you are able to get your work done
Spamm00r said:
Perfect!
Did you test wether you can use this app to issue "adb tcpip 5555" command at bot so that the adb wifi tasker function can do the rest? Thatway we would have adb shell on a non rooted device all the time.
Click to expand...
Click to collapse
The issue with Tasker is something else as far as I can see. May be because Tasker have subscription checking thing in it and it needs Google Libraries which are not available in fire os.
So I finally was able to test this. The app does work ok.
I'd like to be able to execute these scripts not only at boot. For example like when you press test script, I'd like to be able to run the app anytime I want the script to execute.
Can you please also add an setting that allows the scripts to be executed by just opening the app, so that you are not limited to run these scripts only at boot or when you manually press " test script". So we could use these scripts anytime we run this app for example via Tasker.
Why does the shell execution work with this app but not with taskers adb shell?
Spamm00r said:
So I finally was able to test this. The app does work ok.
I'd like to be able to execute these scripts not only at boot. For example like when you press test script, I'd like to be able to run the app anytime I want the script to execute.
Can you please also add an setting that allows the scripts to be executed by just opening the app, so that you are not limited to run these scripts only at boot or when you manually press " test script". So we could use these scripts anytime we run this app for example via Tasker.
Why does the shell execution work with this app but not with taskers adb shell?
Click to expand...
Click to collapse
Are you able to use Tasker in the stick?
I tried in my device and it won't even show a simple Toast and possible reason as I said is that Tasker have subscription checking thing in it and that requires Play services which are missing in Fire OS. So unless you have direct purchased version of Tasker or unless you install Play services in it, I don't see any good way of running Tasker in it.
Shaikh Amaan FM said:
Are you able to use Tasker in the stick?
I tried in my device and it won't even show a simple Toast and possible reason as I said is that Tasker have subscription checking thing in it and that requires Play services which are missing in Fire OS. So unless you have direct purchased version of Tasker or unless you install Play services in it, I don't see any good way of running Tasker in it.
Click to expand...
Click to collapse
Yes I have Tasker running on FireTV 4K without play service. You can download an apk with 7 day trial directly from the tasker website and it works without playstore. If it has issues with subscription or trial expired, it will tell so and refuse to execute some advanced features.
I can run intents and stuff with tasker just fine, but as Fire TV has no Accessibility service installed, you can not use most of the nice features and plugins of Tasker. Issuing shell commands for example does not work. so I can not issue any keyinput with tasker. That's why I have to rely on your app.
With your app however I was able to completely avoid tasker for now.
I used Tasker to run an intent that opens a youtube link. Now I run this intent from your app. Also i can now issue keyinput with your app. With Tasker that was not possible due to missing accessibility service, which Tasker relies on.
How is your app able to issue keyinput via shell, while tasker can not due to mssing accessibility services? Maybe you can make your app more advanced and allow it to be used as a proxy for issuing shell keyinput on devices without accessibility service. This is the one single reason why I wish i had root on this device. Just to have accessibility service back, which Amazon removed in the recent firmware versions.
I use input to press home key, which makes Fire TV switch the HDMI input of the TV to itself. Now Whenever I start the tv, Fire TV automatically switches input to itself and starts playing youtube.
What I now also want is to be able to use your app also after boot, as I need to switch input and issue keyinput after boot while running several times. Thats why I asked you to add an option to runn it also after boot.
Because if I press "test script" keyinput also works with your app. But not with Tasker.
Will it work, if I open your app with intent "android.intent.action.MAIN"? Will it execute the shell script like when at boot? if yes, then I will try to run this intent from Tasker.
Also It would be good if it was possible to have multiple scripts that you can execute so that you are not stuck with one single script. For example allow to save script a, b, c etc, and then have an intent to be ebale to run a specific script a, b or c. etc..
Your script is very helpful and solves a big problems that amazon has introduced by cutting accesisbility service. Without your app, fire tv would be so useless for me. Thanks for releasing it.
Spamm00r said:
What I now also want is to be able to use your app also after boot, as I need to switch input and issue keyinput after boot while running several times. Thats why I asked you to add an option to runn it also after boot.
Because if I press "test script" keyinput also works with your app. But not with Tasker.
Click to expand...
Click to collapse
Yes this can be done, but i'm busy in something else, so it might take a while
Spamm00r said:
Also It would be good if it was possible to have multiple scripts that you can execute so that you are not stuck with one single script.
Click to expand...
Click to collapse
For having multiple scripts, currently I think you can do it by creating different bash files containing scripts and store them somewhere in Fire Device's storage and then execute them (but probably you'll face problem in giving execute permission to those bash files), this process can be made easier but as I said would take time.
Shaikh Amaan FM said:
Yes this can be done, but i'm busy in something else, so it might take a while
For having multiple scripts, currently I think you can do it by creating different bash files containing scripts and store them somewhere in Fire Device's storage and then execute them (but probably you'll face problem in giving execute permission to those bash files), this process can be made easier but as I said would take time.
Click to expand...
Click to collapse
OK no problem. Take your time.
I don't think that you can execute scripts without root. How does your app execute these scripts without root permissions?
Also sometimes the script is not executed, not at boot and not when I press "test script". I think maybe adb is being blocked by some other app? I have to look into why this happens.
Spamm00r said:
OK no problem. Take your time.
I don't think that you can execute scripts without root. How does your app execute these scripts without root permissions?
Also sometimes the script is not executed, not at boot and not when I press "test script". I think maybe adb is being blocked by some other app? I have to look into why this happens.
Click to expand...
Click to collapse
Which fire device do you have and what's the Fire OS version in it. App doesn't works in Fire OS 5, in Fire OS 6, you have to make sure that no other device/service is connected to ADB, In Fire OS 7, I didn't saw any issue
Shaikh Amaan FM said:
Which fire device do you have and what's the Fire OS version in it. App doesn't works in Fire OS 5, in Fire OS 6, you have to make sure that no other device/service is connected to ADB, In Fire OS 7, I didn't saw any issue
Click to expand...
Click to collapse
I have Fire TV Stick 4k and OS is 6. I figured out why it sometimes doe snot work. it is because ADB is occupied by another app. If I disable and enable adb debugging and thatway break any exisiting connections, it works fine. I just have to make sure that no other app blocks adb, as apparently only 1 app can be connected to adb at a time.
That might be another point of improvement, to make sure that adb is not left occupied.
Spamm00r said:
I have Fire TV Stick 4k and OS is 6. I figured out why it sometimes doe snot work. it is because ADB is occupied by another app. If I disable and enable adb debugging and thatway break any exisiting connections, it works fine. I just have to make sure that no other app blocks adb, as apparently only 1 app can be connected to adb at a time.
That might be another point of improvement, to make sure that adb is not left occupied.
Click to expand...
Click to collapse
In fire os 7, there's no such issue. But yeah in fire os 6 I have tested, only one service or device can connect to adb at a time, and I don't think there's anything I can do about it
Shaikh Amaan FM said:
In fire os 7, there's no such issue. But yeah in fire os 6 I have tested, only one service or device can connect to adb at a time, and I don't think there's anything I can do about it
Click to expand...
Click to collapse
My exact Fire OS is: Fire OS 6.2.8.1
WHich Fire TV Stick has OS 7?
Being able to connect multiple clients to adb is a big step forward. Right now I have to manually toggle adb access to allow other tools to connect to adb. This is a big problem.
Spamm00r said:
My exact Fire OS is: Fire OS 6.2.8.1
WHich Fire TV Stick has OS 7?
Being able to connect multiple clients to adb is a big step forward. Right now I have to manually toggle adb access to allow other tools to connect to adb. This is a big problem.
Click to expand...
Click to collapse
I have Fire Stick 3rd gen.
New devices including Fire Stick Lite are running Fire OS 7.x and I can connect multiple different devices/services to adb at the same time without any issue.
Curious that the Lite has newer Fire OS Version than man other devices. In this case it would be desirable to update, but until then how can make sure that your app or any other app disconnects form adb and gives it free to use for other applications.
Right now I have to manually go to developer settings and toggle ADB off and on to make it available to other apps. Otherwise, adb will be occupied by the last app that used it.
Is it possible to automate this? Adding "disconnect" to the shell command didn't help.
Spamm00r said:
Curious that the Lite has newer Fire OS Version than man other devices. In this case it would be desirable to update, but until then how can make sure that your app or any other app disconnects form adb and gives it free to use for other applications.
Right now I have to manually go to developer settings and toggle ADB off and on to make it available to other apps. Otherwise, adb will be occupied by the last app that used it.
Is it possible to automate this? Adding "disconnect" to the shell command didn't help.
Click to expand...
Click to collapse
Look for force stopping the application through adb commands.
I have managed to make the app start also after boot via Taskers app action. But the script is only executed after manually pressing the "test Script" button.
What exact intent action is executed by pressing the "Test Script" button? From the xml file I can only see "com.asfmapps.firetv_adbonboot.MainActivity".
I have also tried to send android.intent.action.BOOT_COMPLETED to your app to make it think it just started up but that also does not make your app to execute the script automatically.
What intent is your app listening for to execute the script? And ho do I issue it via shell or tasker?
Hi,
I'm trying to echo to sys/class/display/mode so I can change the resolution on boot.
When I test the script it shows 'permission denied'. It's an android box so it won't work?