Related
Hey all, after searching here and on google play without finding anything I dediced to ask you guys!
I can't find an app that activates my Flash LED which is next to the camera of my Ace, or, being more precise, I've used Tiny Flashlight and it works but it has TOO MANY USELESS permissions!
I installed many apps which have only flash permission or have no permission, but they just don't work, it says that flash is ON but actually it's OFF.
So any of you who sometimes uses smartphone as a Torch could suggest me a good working app? The security aspect of Android is very understimated and it seems that no one cares about permissions.
(I already posted this thread in the Ace section but it seems that no one knows the answer, so that topic could be closed in order to not creating duplicates).
Hi
I use TeslaLED - works great.
Only permissions are 'Control LED' and 'Prevent phone from sleeping'.
Besides that, it has a customizeable widget, and are nice and simple (which i like of this type of app )
Don't know why but it doesn't work for me. Tried all settings possible.
In 'Settings -> Advanced -> LED Method' there is a few options if it doesn't work by standard. Have you tried the different options? Mine worked on 'Auto' (default).
MichaelOrnsholt said:
In 'Settings -> Advanced -> LED Method' there is a few options if it doesn't work by standard. Have you tried the different options? Mine worked on 'Auto' (default).
Click to expand...
Click to collapse
Of course, I tried all of them, sometimes it force closes and sometimes nothing happens..
Hmm then i don't know how to fix it.
Don't know that Ace, and thus don't know if there should be any specific issues with that phone...
Sent from my HTC Desire using XDA
Try the "torch" application. I think it's listed as "Nexus Torch" in google play, it might work for your phone. It has permission requirements other than just accessing the camera light.
MichaelOrnsholt said:
Hi
I use TeslaLED - works great.
Only permissions are 'Control LED' and 'Prevent phone from sleeping'.
Besides that, it has a customizeable widget, and are nice and simple (which i like of this type of app )
Click to expand...
Click to collapse
Not any more ... now it has the spyware $hit permission built into it called:
Camera:
take pictures and videos
TheArt. said:
Hey all, after searching here and on google play without finding anything I dediced to ask you guys!
I can't find an app that activates my Flash LED which is next to the camera of my Ace, or, being more precise, I've used Tiny Flashlight and it works but it has TOO MANY USELESS permissions!
I installed many apps which have only flash permission or have no permission, but they just don't work, it says that flash is ON but actually it's OFF.
So any of you who sometimes uses smartphone as a Torch could suggest me a good working app? The security aspect of Android is very understimated and it seems that no one cares about permissions.
(I already posted this thread in the Ace section but it seems that no one knows the answer, so that topic could be closed in order to not creating duplicates).
Click to expand...
Click to collapse
You can download permission remover app from play store developed by steelworks and remove unwanted permissions from your favourite flashlight app.
Ashwinrg said:
You can download permission remover app from play store developed by steelworks and remove unwanted permissions from your favourite flashlight app.
Click to expand...
Click to collapse
Are you sure any permissions app other than Xprivacy does the job ???
App Ops eXtended is a launcher for the 4.3 AND 4.4 App Ops activity, as well as an installer for a more advanced version of App Ops with added features:
- search for apps
- filter out disabled apps
- sorting alphabetically
- batch grant/revoke OPs (permissions)
- ability to automatically deny permissions chosen by you on new app installs
- optional persistent notification to show revoked permissions for the current foreground app
App Ops X is a recompiled version of Android 4.3's App Ops which we've made available to Kit Kat now too.
We're going to improve on it and add new features, so please, if there's anything you'd like to see just let us know! Also if you have any problems with it, please send us a description along with your ROM. Thanks!
Link: http://play.google.com/store/apps/details?id=com.colortiger.appopsinstaller
Can you add the option to take away ability from apps to connect to the internet, or to write to the USB storage, or to read the phone status and identity? That's what I would call extended app ops
sordna said:
Can you add the option to take away ability from apps to connect to the internet, or to write to the USB storage, or to read the phone status and identity? That's what I would call extended app ops
Click to expand...
Click to collapse
Don't these apps work by listing ALL the permissions that an individual app can access ? So if it can't access the internet or GPS or or or it won't give the option to denied ?
drawde40599 said:
Don't these apps work by listing ALL the permissions that an individual app can access ? So if it can't access the internet or GPS or or or it won't give the option to denied ?
Click to expand...
Click to collapse
App Ops lists some, not all permissions. Look at chrome, it doesn't say that it has any network permissions, neither write storage, but if you look at them in Settings->apps you can see it does.
sordna said:
App Ops lists some, not all permissions. Look at chrome, it doesn't say that it has any network permissions, neither write storage, but if you look at them in Settings->apps you can see it does.
Click to expand...
Click to collapse
Gotcha I never really looked at apps like chrome , I really only use it for games and shady apps downloaded from the internet . I agree finding a way to show all permissions would be great
Many thanks!! I was waiting for kit Kat version.
Sent from my Nexus 4 using Tapatalk
Yep, working on the INTERNET permission right now. App Ops eXtended uses the same AppOpsManager as the native app, which doesn't support it, so it's a bit more work, but we're getting there!
Looks nice !
If I may, once App Ops X is installed, the button still says Install App Ops X Maybe you could change it to "Launch App Ops X"
That's done, along with a few other features:
- notification that shows revoked permissions to the current foreground app
- batch grant/revoke a permission to all apps that requested it at once
- rules - automatically disallow permissions of your choosing to newly installed apps (like READ CONTACTS)
Don't see wake lock option in X version
First thanks for make this great app available on Kitkat platform.
I'm not sure if the following bug might be related to my phone only:
When trying the Native AppOps, all works fine and I see the "wake lock" option.
However when I try the AppOps X, I'm unable to see the option for "wake lock". I had granted superuser access to the app and phone is rooted. I'm on Kitkat (Build from CM 11). Phone is a Samsung S2 I9100.
If nobody is having this issue, then I would guess it's something with my OS or phone.
zrgiu said:
That's done, along with a few other features:
- notification that shows revoked permissions to the current foreground app
- batch grant/revoke a permission to all apps that requested it at once
- rules - automatically disallow permissions of your choosing to newly installed apps (like READ CONTACTS)
Click to expand...
Click to collapse
This is cool! Can you also present the apps sorted by name ? The standard app ops show the apps in random order, so it's hard to find a specific app you are looking for, if it falls under a section with a lot of apps.
keepasa said:
When trying the Native AppOps, all works fine and I see the "wake lock" option.
However when I try the AppOps X, I'm unable to see the option for "wake lock".
Click to expand...
Click to collapse
Thanks for that! It is actually a bug on our side which we'll try to get fixed by the next version! Feel free to suggest any improvements if you have an ideas too!
sordna said:
This is cool! Can you also present the apps sorted by name ? The standard app ops show the apps in random order, so it's hard to find a specific app you are looking for, if it falls under a section with a lot of apps.
Click to expand...
Click to collapse
They are actually sorted so that the app which most recently used that OP is shown first. We'll try to add a sort option by the next version too though!
Does it affect OTA Updates?
THX
Bernd
bgrimm said:
Does it affect OTA Updates?
Click to expand...
Click to collapse
It shouldn't affect them in any way.
Is there a way to stop notifications?
killall said:
Is there a way to stop notifications?
Click to expand...
Click to collapse
In App Ops X on the upper right side there's a "settings" button, and there on the unlocked version the first option is for turning off the notification. If you haven't unlocked (purchased) though and you see notifications from App Ops X then that's a bug which we'll try to fix ASAP.
Yeh I have upgraded, but still get notifications, even if unchecked in settings
killall said:
Yeh I have upgraded, but still get notifications, even if unchecked in settings
Click to expand...
Click to collapse
found it, thanks! fixing now!
My main concern is the device ID. is there anyway to stop apps from gaining access to that? Seems like a good app so far. Nice job
Greatness83 said:
My main concern is the device ID. is there anyway to stop apps from gaining access to that? Seems like a good app so far. Nice job
Click to expand...
Click to collapse
Thanks!
There isn't any way through the AppOpsManager as of yet. Even so, the device ID now isn't as unique as it used to be, since it's software generated as opposed to hardware. I'm still looking into it to confirm that it's so, but the most of the internet tells that it is.
Few hours ago @explainAndroid posted article on xda main page onto how to use android's hidden RUN_IN_BACKGROUND permission to restrict app's background behavior. I made an app for that.
Here's link to original article: https://www.xda-developers.com/freeze-app-background-processes-without-root-android-nougat/
Here's link to app's github: https://github.com/MrBIMC/RunInBackgroundPermissionSetter
Here's link to reddit thread about app: https://www.reddit.com/r/Android/co...en_run_in_background/?st=j570s1rf&sh=675cc4d6
Here's link to xda labs: https://labs.xda-developers.com/store/app/com.pavelsikun.runinbackgroundpermissionsetter
Omg it created multiple threads. Sorry. Trying to remove duplicates now.
Submit this to XDA Labs as well! Don't worry about a crappy icon or whatever. I've made apps in Tasker and have posted them to Labs hehe. As long as people find it useful feel free to submit!
@MrBIMC
Thanks for the app!!
Is possible add hours of the days of week when selected apps run or doent run in background?
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
Nice app!
Will charging disable this?
Can u make the app work without rooting, just using adb, where the permission through adb for this app is granted once and then it can be used to limit background permission of other apps
excellent mate.
we should post a tutorial... not everyone will understand the potential ramifications of disabling everything
I will try to test this out! Though, I kinda like the old icon compared to the new one, it seems like it's not properly cropped. Additionally, could you add an option to show system and user apps only? Maybe a toggle to ignore apps all at once or vice versa too?
No chance for Marshmallow?
Does this have the same functionality as in lineage os ROMs app ops where you can disable background processes?
As someone is undoubtedly going to ask it, I'll ask it for them. How does this differentiate to apps like greenify @MrBIMC? Do they both limit background processes? Anyways, the all looks very interesting, thanks!
This looks great!
Do the settings stick after reboot?
arjuntsgowda said:
Can u make the app work without rooting, just using adb, where the permission through adb for this app is granted once and then it can be used to limit background permission of other apps
Click to expand...
Click to collapse
No.
From the Github page:
Anyway, this app is for those who don't want to mess with adb shell and input commands manually and prefer to just click on app name to enable/disable it from running in the background. Sadly, android apps are not allowed to implicitly edit permissions of other apps, so this application requires root to overcome it.
Click to expand...
Click to collapse
Al Gore said:
No chance for Marshmallow?
Click to expand...
Click to collapse
No.
From the Github page:
Anyway, this app is for those, who don't want to mess with adb shell and input commands manually and prefer to just click on app name to enable/disable it from running in the background. Sadly, android apps are not allowed to implicitely edit permissions of other apps, so this application requires root to overcome it.
Click to expand...
Click to collapse
jordirpz said:
@MrBIMC
Thanks for the app!!
Is possible add hours of the days of week when selected apps run or doent run in background?
Click to expand...
Click to collapse
This would be really cool. Best way to implement that I think would be to add Tasker plugin functionality to the app to allow Tasker flows to toggle the permission, which would have the benefit of being able to change it for any reason (such as low battery).
DEVILOPS 007 said:
As someone is undoubtedly going to ask it, I'll ask it for them. How does this differentiate to apps like greenify @MrBIMC? Do they both limit background processes? Anyways, the all looks very interesting, thanks!
Click to expand...
Click to collapse
If I understand both correctly... Greenify forces apps to hibernate when you turn your screen off (or manually tell it to), but the app can still wake itself back up for a variety of reasons, such as receiving push notifications, location updates, or any other unnecessary reason like Facebook, lol. This app overrides a hidden permission in Android 7+ that tells the system to not allow the app to run in the background, which means it will not be able to wake itself up.
hassan_1000 said:
Does this have the same functionality as in lineage os ROMs app ops where you can disable background processes?
Click to expand...
Click to collapse
according to the reddit comments its the same. but maybe the Developer can confirm this
xdauser7 said:
according to the reddit comments its the same. but maybe the Developer can confirm this
Click to expand...
Click to collapse
Am Developer. Can confirm, toggle "limit background activity" in LOS14 is the same as this app. At least that's what reddit tells me as I haven't checked myself.
Wow. Looks promising. I was too lazy to run ADB manually xD
So lets see if I can screw something up with disabling almost everything
MishaalRahman said:
Submit this to XDA Labs as well! Don't worry about a crappy icon or whatever. I've made apps in Tasker and have posted them to Labs hehe. As long as people find it useful feel free to submit!
Click to expand...
Click to collapse
Ditto
neonixxx said:
This would be really cool. Best way to implement that I think would be to add Tasker plugin functionality to the app to allow Tasker flows to toggle the permission, which would have the benefit of being able to change it for any reason (such as low battery).
If I understand both correctly... Greenify forces apps to hibernate when you turn your screen off (or manually tell it to), but the app can still wake itself back up for a variety of reasons, such as receiving push notifications, location updates, or any other unnecessary reason like Facebook, lol. This app overrides a hidden permission in Android 7+ that tells the system to not allow the app to run in the background, which means it will not be able to wake itself up.
Click to expand...
Click to collapse
thanks, makes sense about Greenify... do you or anyone know the difference between this and Brevent?
dimm0k said:
thanks, makes sense about Greenify... do you or anyone know the difference between this and Brevent?
Click to expand...
Click to collapse
I actually tried Brevent for the first time a few weeks ago. According to the app itself, aside from not requiring root, it's supposed to monitor when you hit the back button or remove an app from recents, and then actually kill the app process when you do, despite if the app has some background process that it intended to keep running. Basically lets you manually control when an app is killed in a quick and intuitive way, but for me personally, it didn't seem to work as expected for some reason; background processes seemed to keep running after.
Also Brevent, being a non-root solution requires you to connect the device to a PC and run some ADB commands to give it permission every time you reboot. It has an experimental root mode that doesn't require this.
Hey guys,
I've done a bit of an oops when I removed some of the bloatware via adb on my F2 Pro and now the native Gallery and Notes apps don't seem to work. I'm getting random pop up notifications of Notes/Gallery not working and some apps don't work properly without the functionality.
I've tried to see if I can reinstall them but no success yet
Not sure if the debug logs are helping but here are the ones for the Gallery app:
Code:
java.lang.ExceptionInInitializerError
at com.miui.gallery.preference.PreferenceHelper.getPreferences(PreferenceHelper.java:25)
at com.miui.gallery.preference.PreferenceHelper.getInt(PreferenceHelper.java:41)
at com.miui.gallery.preference.GalleryPreferences$DataBase.getViewVersion(GalleryPreferences.java:1190)
at com.miui.gallery.provider.GalleryDBHelper.createViewIfNeeded(GalleryDBHelper.java:2066)
at com.miui.gallery.provider.GalleryDBHelper.onCreate(GalleryDBHelper.java:1066)
at org.sqlite.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:308)
at org.sqlite.database.sqlite.SQLiteOpenHelper.getReadableDatabase(SQLiteOpenHelper.java:228)
at com.miui.gallery.provider.cache.MediaManager$InitializeTask.run(MediaManager.java:796)
at java.lang.Thread.run(Thread.java:919)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.SharedPreferences android.content.Context.getSharedPreferences(java.lang.String, int)' on a null object reference
at com.miui.gallery.preference.PreferenceHelper.<init>(PreferenceHelper.java:15)
at com.miui.gallery.preference.PreferenceHelper.<init>(PreferenceHelper.java:11)
at com.miui.gallery.preference.PreferenceHelper$SingletonHolder.<clinit>(PreferenceHelper.java:18)
... 9 more
Some help would be much appreciated!
Use simple gallery and simple notes from F-Droid, way better.
MajorBoobage said:
Use simple gallery and simple notes from F-Droid, way better.
Click to expand...
Click to collapse
For some reason, I am unable to change the default Gallery option so a new Gallery app doesn't help
It won't let me set Gallery default to anything
This happened to me in the past when I removed the Xiaomi Service Framework including the Xiaomi Cloud.
Same Problem. Please Help Xiaomi Cloud + Framework Reinstalled still Gallery app doesn't open
You need mi.cloud.sdk
AsusZenFone3Deluxe said:
You need mi.cloud.sdk
Click to expand...
Click to collapse
Thank you That indeed solved the issue of Gallery and Notes!! Who would've thought those two need the cloud sdk package
It still doesn't let me change the default Gallery though so there's that
Hey everyone. I found this APK dump for the pixel watch one reddit. I got the pixel UI APK and it installs fine. When I set it as the default home app though it just crashes. I'm hoping if I provide the apk one of you more experienced users can perhaps mod this APK to work with our watches.
Link?
File?
APK Name?
Memo to me...
Google Pixel Subforum seems here:
Google Pixel Watch
forum.xda-developers.com
Link to APks I saw first time in this Thread...
Official List of Sideloaded Apps and Workarounds For Wear OS (Tested on Galaxy Watch)
SIDELOAD LIBRARY COMPATIBLE WITH WEAR OS 3 TESTED ON GALAXY WATCHES All Smart Watches Can Probably Benefit From This Guide Special thanks to everyone who has contributed to testing and providing feedback on various apps and versions. Thanks to...
forum.xda-developers.com
Best Regards
adfree said:
Link?
File?
APK Name?
Click to expand...
Click to collapse
Reddit Link for Pixel Watch APK
com.google.android.wearable.sysui.apk
Is file name for apk
After some Google Search...
No idea if different Version(s)...
Wear OS System UI - Apps on Google Play
Access to the next generation of Wear OS smartwatch user experiences.
play.google.com
Edit 1.
Attempt from dump... "backup"...
Code:
D:\Android\ADB>adb install com.google.android.wearable.sysui.apk
Performing Streamed Install
Success
Edit 2.
I see only 2 ugly Icons... both nothing open...
Is this what you mean with crashes?
Short tested on GVI3...
Best Regards
adfree said:
After some Google Search...
No idea if different Version(s)...
Wear OS System UI - Apps on Google Play
Access to the next generation of Wear OS smartwatch user experiences.
play.google.com
Edit 1.
Attempt from dump... "backup"...
Code:
D:\Android\ADB>adb install com.google.android.wearable.sysui.apk
Performing Streamed Install
Success
Click to expand...
Click to collapse
I found a link on APKPure it's the same version number as the dump from the pixel watch. Will probably have to be modded since it's crashing when trying to make default home app.
...when trying to make default home app.
Click to expand...
Click to collapse
How?
Btw... If I search for text string:
Code:
com.google.android.wearable.sysui
Inside old EVA8...
Then 2 GW4 files found:
Code:
d:\GW4_****\superTest_EVA8\result1_imj\extracted\system\system\framework\framework-res.apk
d:\GW4_****\superTest_EVA8\result1_imj\extracted\system\system\priv-app\ClockworkWcs\ClockworkWcs.apk
Best Regards
adfree said:
How?
Click to expand...
Click to collapse
In watch setting click app then default
adfree said:
Btw... If I search for text string:
Code:
com.google.android.wearable.sysui
Inside old EVA8...
Then 2 GW4 files found:
Code:
d:\GW4_****\superTest_EVA8\result1_imj\extracted\system\system\framework\framework-res.apk
d:\GW4_****\superTest_EVA8\result1_imj\extracted\system\system\priv-app\ClockworkWcs\ClockworkWcs.apk
Click to expand...
Click to collapse
Okay there's also APK from the dump that matches clockwork maybe that is needed
Sorry, I will check this ... then sleep or other stupid tests:
Phone by Google - Apps on Google Play
Reliable phone calls with spam protection, caller ID and more helpful features
play.google.com
Code:
D:\Android\ADB>adb install com.google.android.dialer.apk
Performing Streamed Install
Success
adfree said:
Sorry, I will check this ... then sleep or other stupid tests:
Phone by Google - Apps on Google Play
Reliable phone calls with spam protection, caller ID and more helpful features
play.google.com
Code:
D:\Android\ADB>adb install com.google.android.dialer.apk
Performing Streamed Install
Success
Click to expand...
Click to collapse
The Google dialer is already available in the watch play store
This is first time I found working Dialer for GW4...
Only Phone go or something similar... I was able before...
How to fire Secret Codes?
I can not * #
?
adfree said:
This is first time I found working Dialer for GW4...
Only Phone go or something similar... I was able before...
How to fire Secret Codes?
I can not * #
?
Click to expand...
Click to collapse
It could be your region does not have it available for gw4 in play store. However I'm in US an I was able to install it from there.
Also you can scroll down when you are in the dialer to see *#
I hope someone can port it too.
Yo, I'm the dude who dumped the Pixel Watch APKs on reddit. I've also tried tinkering around with getting the Home APP running on my GW4, but I'm not having any luck so far. I believe both com.google.android.wearable.sysui.apk and com.google.android.wearable.app.apk from the dump are responsible for the Home-Screen Experience. However as you said, if selected as the Home app on the GW4, the Sysui app just keeps crashing over and over.
Here's some notable things I found in the logcat during those crashes:
Code:
WindowManager: Permission Denial: addWindowTokenWithOptions from pid=2394, uid=10145 requires android.permission.STATUS_BAR_SERVICE
WindowManager: Permission Denial: addWindowToken() from pid=2394, uid=10145 requires android.permission.MANAGE_APP_TOKENS
ActivityManager: Permission Denial: Accessing service com.google.android.wearable.app/com.google.android.clockwork.wcs.service.notification.NotificationService from pid=2394, uid=10145 requires com.google.android.wearable.permission.BIND_WEAR_CORE_PRIVILEGED_SERVICE
ServiceConnection: Failed to bind connection 'NotificationClient#com.google.android.wearable.app#com.google.android.wearable.app.BIND_NOTIFICATION_SERVICE', no permission or service not found.
ServiceConnection: java.lang.SecurityException: Not allowed to bind to service Intent { act=com.google.android.wearable.app.BIND_NOTIFICATION_SERVICE pkg=com.google.android.wearable.app }
AndroidRuntime: FATAL EXCEPTION: WcsSdkWorkerThread
AndroidRuntime: Process: com.google.android.wearable.sysui, PID: 2394
AndroidRuntime: java.lang.SecurityException: Not allowed to bind to service Intent { act=com.google.android.wearable.app.BIND_NOTIFICATION_SERVICE pkg=com.google.android.wearable.app }
I've tried my best to grant the missing permissions using pm grant but that didn't change anything so far... Kind of at my wits end here.
By manually granting all the grantable permissions that the apks request, I was able to get it so far as to say 'Getting started...' before crashing over and over, but no luck in getting to the actual Pixel Watch home screen on my GW4
Quad_Plex said:
Yo, I'm the dude who dumped the Pixel Watch APKs on reddit. I've also tried tinkering around with getting the Home APP running on my GW4, but I'm not having any luck so far. I believe both com.google.android.wearable.sysui.apk and com.google.android.wearable.app.apk from the dump are responsible for the Home-Screen Experience. However as you said, if selected as the Home app on the GW4, the Sysui app just keeps crashing over and over.
Here's some notable things I found in the logcat during those crashes:
Code:
WindowManager: Permission Denial: addWindowTokenWithOptions from pid=2394, uid=10145 requires android.permission.STATUS_BAR_SERVICE
WindowManager: Permission Denial: addWindowToken() from pid=2394, uid=10145 requires android.permission.MANAGE_APP_TOKENS
ActivityManager: Permission Denial: Accessing service com.google.android.wearable.app/com.google.android.clockwork.wcs.service.notification.NotificationService from pid=2394, uid=10145 requires com.google.android.wearable.permission.BIND_WEAR_CORE_PRIVILEGED_SERVICE
ServiceConnection: Failed to bind connection 'NotificationClient#com.google.android.wearable.app#com.google.android.wearable.app.BIND_NOTIFICATION_SERVICE', no permission or service not found.
ServiceConnection: java.lang.SecurityException: Not allowed to bind to service Intent { act=com.google.android.wearable.app.BIND_NOTIFICATION_SERVICE pkg=com.google.android.wearable.app }
AndroidRuntime: FATAL EXCEPTION: WcsSdkWorkerThread
AndroidRuntime: Process: com.google.android.wearable.sysui, PID: 2394
AndroidRuntime: java.lang.SecurityException: Not allowed to bind to service Intent { act=com.google.android.wearable.app.BIND_NOTIFICATION_SERVICE pkg=com.google.android.wearable.app }
I've tried my best to grant the missing permissions using pm grant but that didn't change anything so far... Kind of at my wits end here.
By manually granting all the permissions that the apks request, I was able to get it so far as to say 'Getting started...' before crashing over and over, but no luck in getting to the actual Pixel Watch home screen on my GW4
Click to expand...
Click to collapse
Theory here is we most likely can't provide these permissions through ADB because they're system permissions provided by default on the Pixel Watch but don't exist on the GW4 (For all we know), which is why we're getting this error when we try to give them.
Code:
C:\Users\Test\Desktop\platform-tools>adb shell "pm grant com.google.android.wearable.app com.google.android.wearable.permission.BIND_WEAR_CORE_PRIVILEGED_SERVICE"
Exception occurred while executing 'grant':
java.lang.IllegalArgumentException: Unknown permission: BIND_WEAR_CORE_PRIVILEGED_SERVICE
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermissionInternal(PermissionManagerService.java:1470)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:1429)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:2287)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:249)
at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
at android.os.ShellCommand.exec(ShellCommand.java:44)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:22522)
at android.os.Binder.shellCommand(Binder.java:929)
at android.os.Binder.onTransact(Binder.java:813)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4730)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4523)
at android.os.Binder.execTransactInternal(Binder.java:1159)
at android.os.Binder.execTransact(Binder.java:1123)
The only possibility would be someone tries to give these permissions with a rooted watch.
Maybe, you can try
Cartesian8445 said:
Theory here is we most likely can't provide these permissions through ADB because they're system permissions provided by default on the Pixel Watch but don't exist on the GW4 (For all we know), which is why we're getting this error when we try to give them.
Code:
C:\Users\Test\Desktop\platform-tools>adb shell "pm grant com.google.android.wearable.app com.google.android.wearable.permission.BIND_WEAR_CORE_PRIVILEGED_SERVICE"
Exception occurred while executing 'grant':
java.lang.IllegalArgumentException: Unknown permission: BIND_WEAR_CORE_PRIVILEGED_SERVICE
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermissionInternal(PermissionManagerService.java:1470)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:1429)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:2287)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:249)
at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)
at android.os.ShellCommand.exec(ShellCommand.java:44)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:22522)
at android.os.Binder.shellCommand(Binder.java:929)
at android.os.Binder.onTransact(Binder.java:813)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4730)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4523)
at android.os.Binder.execTransactInternal(Binder.java:1159)
at android.os.Binder.execTransact(Binder.java:1123)
The only possibility would be someone tries to give these permissions with a rooted watch.
Click to expand...
Click to collapse
Maybe it can be done by editing the app itself, I don't know...
Apparently the WearOS System UI is available on Google Play now?... Not sure if this is the same version as found on the Pixel Watch, however it's marked as 'incompatible' with the GW4
Wear OS System UI - Apps on Google Play
Access to the next generation of Wear OS smartwatch user experiences.
play.google.com
Quad_Plex said:
Apparently the WearOS System UI is available on Google Play now?... Not sure if this is the same version as found on the Pixel Watch, however it's marked as 'incompatible' with the GW4
Wear OS System UI - Apps on Google Play
Access to the next generation of Wear OS smartwatch user experiences.
play.google.com
Click to expand...
Click to collapse
Same .apk name, "com.google.android.wearable.sysui", probably posted on the play store so they can update it easier
Cartesian8445 said:
Same .apk name, "com.google.android.wearable.sysui", probably posted on the play store so they can update it easier
Click to expand...
Click to collapse
It's the same package, yea, but I'm not sure if it's the exact same version as the one I dumped before.
Quad_Plex said:
It's the same package, yea, but I'm not sure if it's the exact same version as the one I dumped before.
Click to expand...
Click to collapse
Yes, I was able to past the link for the play store version in APK pure and found that it is the same version on the dump.