So I took a gamble on a cheap smartwatch (Yeah I know, you get what you pay for) which comes with full Android 5.1.
I've noticed two things that really make it hard to use. First of all, there is no notification panel. The built in launcher has a really whacky way to open and dismiss notifications but there's no way of accessing notifications once you changed the launcher since it's not a notification app that I could perhaps launch using a gesture.
The second weird thing is that google fit does not have the permission set to use the phone sensor. I can find apps that remove permissions for apps on a rooted phone, but not add one. Is there a way?
I've rooted the watch and have access to Magisk Manager. I can't get the phone into fastboot even with adb - this somewhat limits me on tinkering more.
Anyone have an advice or suggestions?
Sideburnt said:
The second weird thing is that google fit does not have the permission set to use the phone sensor. I can find apps that remove permissions for apps on a rooted phone, but not add one. Is there a way?
Click to expand...
Click to collapse
You only can grant/revoke permissions that are defined by app's developer in app's AndroidManifest.xml. You can try to add extra permissions of your choice to that file.
Example:
Code:
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
jwoegerbauer said:
You only can grant/revoke permissions that are defined by app's developer in app's AndroidManifest.xml. You can try to add extra permissions of your choice to that file.
Example:
Code:
<uses-permission android:name="android.permission.INTERNET" />
Click to expand...
Click to collapse
That's the strange thing, on my phone the app has BODY_SENSORS permission granted, on the watch it doesn't.
I'm not sure if that's a restriction of the OS implementation or Android 5.1.
Through ADB if I try and run
"adb shell pm grant com.google.android.apps.fitness android.permission.BODY_SENSORS".
I get the error "Operation not allowed: java.lang.SecurityException: Package com.google.android.apps.fitness has not requested permission android.permission.BODY_SENSORS".
So I can't seem to add it if it was never included in initial installation of the apk through google play. I can only enable USB debugging through developer options and have no access to turn off Disable permission monitoring.
Related
Hi all,
I've started development on an application for Android that allows you to assign a keyboard to an application. Personally, I've found a need for it due to constantly going between the terminal, text messaging, browsing, etc. Who has time to manually switch?!
Anyway, it's for root only and I thought I'd introduce it here since noobs would never have a need for this app.
Caveats:
Start On Boot isn't functional yet
Keyboards occasionally force close (still tracking this down)
Needs to be put into /system/app
If you have adb set up, you can do adb push KeySwap.apk /system/app. Otherwise, you'll need to use a file manager like Root Explorer (make sure to mount the directory as R/W)
Enjoy and feedback is appreciated.
Matt
I love the idea for this app. But it keeps force closing after I start the service and navigate back to the home screen (or to another app). My phone is a Nexus One running CM 7.1.0 RC1. I mighty be able to get you some log files later. Also, I noticed that Superuse does not prompt me to give KeySwap root permissions.
CSorry to hear it's giving you problems. I'll try to work on the app this weekend and see what might be responsible for your trouble. If you get a chance, please post a log.
Thanks,
Matt
Ok, I've updated the architecture of the app a bit and it should provide much better log info.
Please make sure you have the app in /system/app and that the file permissions are all set to enabled. Also, I don't believe you'll get the Superuser prompt for apps in /system/app.
I've attached the updated apk to this post.
Any updates?
This sounds super useful but unstable. I might even root my phone just for this functionality. Have there been any updates to this since 2011-07? Is there a development workspace for it, on github for example?
mattanonymous said:
Ok, I've updated the architecture of the app a bit and it should provide much better log info.
Please make sure you have the app in /system/app and that the file permissions are all set to enabled. Also, I don't believe you'll get the Superuser prompt for apps in /system/app.
I've attached the updated apk to this post.
Click to expand...
Click to collapse
This is a great idea. Any chance you could open-source the app?
I'm no pro, so forgive anything stupid I may say in advance. I recently learned that any android application has permission to see any application installed on your device. I'm a bit of a privacy nut, and I have concerns with this for a plethora of reasons. I was hoping to learn of a method that would allow me to somehow prevent apps from being able to see what's installed, or at minimum, mask the actual application names so the data an app gets is useless for any purposes they may have for it.
Is there any way to achieve such a thing?
I'm no pro either, but what I do is I use two apps to accomplish this. The first is MyAppSharer (no root required). The second is Advanced Permission Manager (again, no root required). Both can be found on the play store.
First I use MyAppSharer to create an .apk of the app I want to isolate. Place it In the download folder (or any folder of your choosing). Next I install the .apk with Advanced Permission Manager. While installing simply uncheck the 'view other apps permission' or whatever it's called and that might work.
The only concern I have is that apps usually check to see if they have access to all their permissions before startup, and if one is missing it might either not allow you to launch the app or or will crash. Or it'll work perfectly fine and all's well
Good luck
I think you need to hide apps and permission manager. For me, I used to use Greenify, the ForceStop as permission manager, which are available on xposed module repository, but they both require root.
For hiding apps, maybe the "PrivateMe" can help you, it also can hide photos, install apps in hidden mode.
Dresden_ said:
I'm no pro, so forgive anything stupid I may say in advance. I recently learned that any android application has permission to see any application installed on your device. I'm a bit of a privacy nut, and I have concerns with this for a plethora of reasons. I was hoping to learn of a method that would allow me to somehow prevent apps from being able to see what's installed, or at minimum, mask the actual application names so the data an app gets is useless for any purposes they may have for it.
Is there any way to achieve such a thing?
Click to expand...
Click to collapse
The sudo hide xposed module is exactly what you want to figure out
You will get first list of apps where you have to select ''which app to hide"
Then you will get second list of apps where you can select "from which apps to hide that app"
If you want any help regarding xposed,reply me back
Please push the thanks button if it helped
Enjoy:victory::victory:
Regards milkyway3
I've tried to complete this mission a few times, each ending in disaster...until now.
Summary:
The parental control applications too are restrictive. Amazon made some slight changes to the Android code which gave these applications full, and in my opinion unnecessary control of the tablets and the security options. Disabling or uninstalling them can and will eventually cause you to reflash stock firmware. That's because they are labeled as "device/profile owner applications". Located in /data/system is 'device_owner.xml'. That file configures the apps as device/profile owners and doing anything to stop them results in a disaster, often unfixable without reflashing stock. The idea was to trick FireOS by switching device owner applications right from under it's nose. It's not easy but it is possible.
This will be along guide. one or two of these steps may not even be necessary but I am going to present them as I did them and was successful. Beyond that you are free to remove steps and try the process at your will. However any deviation from the guide can result in damage to your device. Even this guide may result in damage to your device, because not everyone's results will be the same. From here on out you are on your own and I am not responsible for any damage done to your devices. This will take some time, if you do not have it it is recommended you do not continue until you do. It will not be possible to pause for extended periods through this guide. This WILL REQUIRE a factory reset. You must be rooted or have an unlocked tablet to complete the guide. You must also have the Google play store and related services installed as system applications in priv-app folder. For this it's recommended to flash a pico Gapps package in TWRP.
THIS OPERATION WAS PERFORMED ON A DEVICE THAT WAS DEODEXED ON 5.6.1.0 WITH A 5.3.6.0 (LATEST FIREOS) BOOT IMAGE. This will not likely work on a stock ROM that has not been deodexed.
Instructions:
1. You need to download an application that uninstalls system applications. Any one of them will do so long as it works. You will absolutely need to download an application that does this. Also download a root file explorer.
2. Uninstall the application called 'Managed provisioning.' then open a shell using a terminal emulator or ADB. Then type the commands below.
Code:
adb shell
su
settings put global device_provisioned 0
3. Go to settings > security > device administrator and make sure Google pay is a device administrator. This is very important and you must not miss this step.
4. Using a root explorer, go to /data/system and copy device_owner.xml to your internal storage. If using your PC please use Notepad++, though it's recommended you complete the following tasks on your device.
4b. Go to system/etc/permissions/ and open handheld_core_hardware.xml in a text editor. Find the line that says: <!-- feature name="android.software.managed_users" --> and replace that line with the one below, save the file and reboot:
Code:
<feature name="android.software.managed_users" />
5. Then go to your internal storage and open the file device_owner.xml in a text editor. Replace the lines of text with the text below, making sure the format is NOT changed from the original and save the file:
Code:
<profile-owner package="com.google.android.gms" name="Google Play services" userId="0" component="com.google.android.gms/com.google.android.gms.mdm.receivers.MdmDeviceAdminReceiver" />
6. NOTE: this step CANNOT be done in TWRP. Again Using a root explorer, copy and paste device_owner.xml to /data/system, overwriting the current one (remember to back up the original). Set permissions to rw (0600) and reboot. If there are no errors or popups and your home and recents button still work after rebooting, continue to the next step.
7. Reboot to recovery and clear/wipe cache and dalvik and reboot system. When booted, if no pop errors from anything, open the uninstaller app you downloaded and uninstall Parental Controls and Parental monitoring. Again reboot to recovery and wipe cache and dalvik and reboot system.
8. Again if no errors, reboot to recovery again and this time do a factory reset. This step is very important and cannot be missed. It is absolutely required that the data be wiped on the device or the device and system will recognize it is no longer owner of said device and it will start shutting you out of security and other options on the device.
9. When rebooted, Open the shell in terminal emulator again or ADB and type the following command below. A reboot should not be necessary when done:
Code:
su
settings put global device_provisioned 1
10. Download an activity launcher (I use activity manager and yes you need to pay a slight fee to use the root part of the launcher, but it's worth it.) Scroll settings and search for 'generic lockscreen set' and long press it to open it with root access. All of your lock screen options should be open and available to you even after removing the parental applications. If they are congratulations you have now remove parental applications and the restrictions that came with them from your device. Go back to /data/system and you will also notice that the device_owner.xml is gone. Killing 2 birds with one stone. If any lockscreen options are blocked then you have failed to properly remove the parental applications and the policies that go along with them.
NOTE: You may need to deactivate 'smart lock' and trusted gms as that may interfere with some lock screen options.
I'll let you guys decide, but I think the device is vastly improved in terms of performance and in Internet connectability after removing these applications.
Edit: forgot a step. Can't believe I did that.
Sent from my Amazon KFSUWI using XDA Labs
I must have goofed. I did a factory reset and now my tablet is back to stock. lol
Edit: I take that back. I tap on parental controls and nothing happens lol
Edit2: Yep It's running good. You were right too. It seems like it runs a lot smoother without amazon's parental controls.
Shadow Death said:
I must have goofed. I did a factory reset and now my tablet is back to stock. lol
Edit: I take that back. I tap on parental controls and nothing happens lol
Edit2: Yep It's running good. You were right too. It seems like it runs a lot smoother without amazon's parental controls.
Click to expand...
Click to collapse
Cuz I'm pretty sure without the support of manage profiles, the parental applications actually cut down on a Wi-Fi speed. I don't think it's cutting short the connection, rather the metrics and scripts associated with other apps and configs, cause it to constantly disconnect and reconnect. also fireOS doesn't like when you have more than one network saved at a time, in the same area. You can also delete etc/wifiloglevels.sh if you are on the deodexed rom. Can also set the value of the line in build prop for wifi rssi levels to ""
Shadow Death said:
I must have goofed. I did a factory reset and now my tablet is back to stock. lol
Edit: I take that back. I tap on parental controls and nothing happens lol
Edit2: Yep It's running good. You were right too. It seems like it runs a lot smoother without amazon's parental controls.
Click to expand...
Click to collapse
Add: you Dan probably reinstall the managed provisioning app. It might let you create a work profile I am not sure. I am going to experiment with that more tomorrow.
I'd like to add that I am on the same battery cycle as the other day when I started this process at 65%. I haven't been as aggressive in my use as much as normal this weekend but I haven't had to put it on the charger all well and usually I have to do that a few times a week if I really use it.
I forgot to mention that step 4 and possibly 5 seem jumbled.
Shadow Death said:
I forgot to mention that step 4 and possibly 5 seem jumbled.
Click to expand...
Click to collapse
Are you using the app?
DragonFire1024 said:
Are you using the app?
Click to expand...
Click to collapse
I'm not sure what app you mean. What I meant was this part:
Using a root explorer, go to /data/system and copy device_owner.xml to your internal storage and open it in a text editor. If using your PC please use Notepad++, though it's recommended you complete the following tasks on your device. Open system/etc/permissions/handheld_core_hardware.xml in a text editor.
Click to expand...
Click to collapse
Shadow Death said:
I'm not sure what app you mean. What I meant was this part:
Click to expand...
Click to collapse
I'll fix it tomorrow. Thanks.
DragonFire1024 said:
I'll fix it tomorrow. Thanks.
Click to expand...
Click to collapse
I figured out what you meant but I thought I would point it out just in case others can't.
Shadow Death said:
I figured out what you meant but I thought I would point it out just in case others can't.
Click to expand...
Click to collapse
Worded it a bit better and broke it apart somewhat. I definitely saw where one would get lost right there. Good eyes!
Hi Dragon Fire,
Is it now working ok? I have the HD8 (7th generation) and would like to eliminate the restrictions of the parental control.
masterted said:
Hi Dragon Fire,
Is it now working ok? I have the HD8 (7th generation) and would like to eliminate the restrictions of the parental control.
Click to expand...
Click to collapse
Every thing is working so far as I can see. There is a slight delay with some apps that require a lock screen be activated for them to work. I use a WiFi app my provider provides and it requires a screen lock. It failed to recognize it at first. Clearing the providers app cache and restarting it worked.
Sent from my Droid RAZR M using XDA Labs
Hi guys, I got a couple questions about this process...
Could someone who did it already check to see if it is possible to change the language of the tablet? On my own tablet, I get a message about parental controls being required, however my own tablet was rooted and debloated a different way last year. In my case, I don't care about changing the language, and I'm totally satisfied with the results I got.
I ask because I'd like to do this "stock Android look & feel" process for a friend (they do not even have an Amazon account, nor want one), but they need to be able to switch language between English and Spanish on a regular basis, and I don't want to mess up their tablet with mods that would prevent this.
Thanks for any insights you guys might have on this... really appreciate the hard work and vast knowledge represented here on XDA.
Kids Dashboard free app and free cloud (Basically you are making dashboard kiosk like small mdm).
PLAY STORE LINK : https://play.google.com/store/apps/details?id=com.tabnova.aidashboard
Cloud Login: https://cloud.kidsdashboard.com
Main site : http://www.kidsdashboard.com/
Complet free app enjoy dont waste money
I was iPhone user but years ago I switched to Android. Since then I've been using "Assistive Touch" apps on all my android devices. Unfortunately now on latest android devices especially with Go editions all those "Assistive Touch" apps stopped working due to the missing overlay "Draw over other apps" permission
For example I've Sunshine T1 Cloud tablet (with 8" display 2GB RAM 16GB storage, and Android 11) in my hand and I've tried almost every Assistive Touch, Easy Touch, Floating Menu app available in Play Store without success.
There is though an Accessibility Shortcut Menu in stock Settings that is when enabled shows a little doll icon in lower right corner of display. It is a static icon that can't be moved anywhere on screen and thus so unconvenient. It also interferes with the Keyboard Switch Icon that appears at the same placement
I am immensely in need of Assistive Touch app. Is there any solution or alternate available ?
Any solution....
Adb command for the app requesting it like
pm grant com.android.phone android.permission.SYSTEM_ALERT_WINDOW
Did this help you. Android Go disables Displaying Over Other App. The command I posted is the only way to grant any app this permission. So to grant YouTube this permission is
adb shell pm grant com.google.android.youtube android.permission.SYSTEM_ALERT_WINDOW
From a local shell
sh -c pm grant com.google.android.youtube android.permission.SYSTEM_ALERT_WINDOW
Or
pm grant com.google.android.youtube android.permission.SYSTEM_ALERT_WINDOW
If those fail you may need to use another device to set the permissions. You don't need root however some terminal emulators don't have sufficient permission
You can always download Bugjaeger app and in dev settings enable wireless adb and pair your app. This requires split screen. As soon as you move away from the pop up with the pairing code. The code becomes invalid and a new code and ip is required.
Obviously if you have root this not be a issue. I hope this helps.
Here if you need the help
The output will be nothing on most devices when the command is successful. Check the permissions screen to verify it has been marked as yes.
** I have the - Sunshine T1 Cloud tablet **
Ithe bootloader is unlockable and this device is Treble - enabled ** I have not been able to get a GSI installed on it without go Gapps. So unfortunately the tablet will remain a go device. So the command is still the only real way to approve the permissions. So I can verify it works without room but you need to be connected with a different device through adb either. Wired or wifi-adb as non of the terminals I tried worked. It does work in terminal if you have an active device connected to adb from the emulator. So I believe you just need adb active with a device accessing it..
JovialQuestion said:
Did this help you. Android Go disables Displaying Over Other App. The command I posted is the only way to grant any app this permission. So to grant YouTube this permission is
adb shell pm grant com.google.android.youtube android.permission.SYSTEM_ALERT_WINDOW
From a local shell
sh -c pm grant com.google.android.youtube android.permission.SYSTEM_ALERT_WINDOW
Or
pm grant com.google.android.youtube android.permission.SYSTEM_ALERT_WINDOW
If those fail you may need to use another device to set the permissions. You don't need root however some terminal emulators don't have sufficient permission
You can always download Bugjaeger app and in dev settings enable wireless adb and pair your app. This requires split screen. As soon as you move away from the pop up with the pairing code. The code becomes invalid and a new code and ip is required.
Obviously if you have root this not be a issue. I hope this helps.
Here if you need the help
The output will be nothing on most devices when the command is successful. Check the permissions screen to verify it has been marked as yes.
** I have the - Sunshine T1 Cloud tablet **
Ithe bootloader is unlockable and this device is Treble - enabled ** I have not been able to get a GSI installed on it without go Gapps. So unfortunately the tablet will remain a go device. So the command is still the only real way to approve the permissions. So I can verify it works without room but you need to be connected with a different device through adb either. Wired or wifi-adb as non of the terminals I tried worked. It does work in terminal if you have an active device connected to adb from the emulator. So I believe you just need adb active with a device accessing it..
Click to expand...
Click to collapse
Thank you very much...!!!
What you suggested worked like a charm
I'm sorry I couldn't reply in a timely manner
In fact I would've thrown away this device if I had not your precious suggestion
Although its touch is not that smooth but after installation of Assistive Touch, it is now easy on hands.
Thanks once again.
Glad to hear it. Any app that requires that permission on Android 11-12 (Go). You can use the same command just changing the apps name in the command. It will lag a little bit on applications that use a lot of the devices resources. So I wouldn't grant the permission to data consuming apps or ones that run large processes in the background. I'm glad this worked for you.
Great...!!!
Thank you very much
Hey folks.
Pixel 4a, with LOS 20, rooted.
I cant find a way to prevent applications to autostart on phone boot up.
Tried several applications (AppsopsX, Permissions manager X and 1 more).
They simply do not list the "startup" permission at all.
I can see the permission as being given to the app (in this case, Slack), in Permissions > Slack > All Permissions.
But those listed there are just informative, you cant change them.
Then i tried the CLI methods - "pm revoke com.Slack android.permission.RECEIVE_BOOT_COMPLETED" .... and it fails with
Code:
Exception occured while executing 'revoke':
java.lang.SecurityException: Permission android.permission.RECEIVE_BOOT_COMPLETED requested by com.Slack is not a changeable permission type.
Any ideas?
It worked for Skype, but not for Slack.