So I have seen the 6.0 and the CM permission system before.
Both have a toggle that allows setting permissions for preinstalled system apps aswell.
Is that possible in OxygenOS too?
(The whole reason for me to get a phone with a permission system was to be able to restrain all that Google Play stuff...)
NotieB said:
So I have seen the 6.0 and the CM permission system before.
Both have a toggle that allows setting permissions for preinstalled system apps aswell.
Is that possible in OxygenOS too?
(The whole reason for me to get a phone with a permission system was to be able to restrain all that Google Play stuff...)
Click to expand...
Click to collapse
CM's privacy guard can do exactly that, even with system apps. OOS's permissions can only limit non-system apps, so you'd need to remove all the Google Play apps as system apps and re-install as user apps (or convert them to user apps with Titanium Backup). However, this would need root. Not sure if you wanted a non-root option, but I can't think of any that would not require root.
MrKhozam said:
However, this would need root. Not sure if you wanted a non-root option, but I can't think of any that would not require root.
Click to expand...
Click to collapse
I was indeed wondering about a non root option, i.e. if there is a toggle i just missed.
So I guess I'll wait for the 6.0 update as the native android permission system works for system apps aswell, and they'd be stupid to replace it.
Related
Hello. I have the non root app. I see that if i want to check the option "greenifying system apps" i have to purchase the donation package.
The question is: do i need also root ? Thanks
No, you do not need root. That is the beauty of the app now. But the hibernated system apps may wake up sometimes. With root, once hibernated, they stay that way.
gxg10 said:
Hello. I have the non root app. I see that if i want to check the option "greenifying system apps" i have to purchase the donation package.
The question is: do i need also root ? Thanks
Click to expand...
Click to collapse
After I tried to understand the text under the "Greenifying system apps" I found out that, no, you would not require root. However, the process might not be smooth as if you installed Xposed and use boost mode. But still, you can hibernate system apps.
I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
njaustin123 said:
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
Click to expand...
Click to collapse
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
dimm0k said:
I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
Click to expand...
Click to collapse
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
Whenever you do a clean fresh flash Rom at the setup most rooms let you restore all your previous apps from google, no need to go to the play store it does it automatic. If you made a backup just restore the data.
Sent from my LG-H901 using XDA-Developers mobile app
dimm0k said:
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
Click to expand...
Click to collapse
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
I have witnessed this, mainly with Google apps. after restoring the app with data the app would randomly crash... removing the app and installing it from Google fixes it, but I have not experienced this with non-Google apps. I'll keep this in mind the next go around when restoring my stuff.
njaustin123 said:
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
Click to expand...
Click to collapse
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
after doing some research and from my understanding, the bad news is that it looks like it's up to devs to add the feature of writing to the external SD via the Storage Access Framework (SAF). unfortunately it doesn't look like an easy task, as the developer of Tasker mentioned that he won't be implementing this since the number of external SD users are far and few =( and would revisit it if that number changes.
the good news for those of us smart and brave enough to root our devices, this is solvable via editing packages.xml and adding in one line for each app you want to "fix". this is documented here
justice26 said:
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
works fine for me here... are you using stock ROM?
dimm0k said:
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
Click to expand...
Click to collapse
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
njaustin123 said:
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
Click to expand...
Click to collapse
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
dimm0k said:
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
Click to expand...
Click to collapse
OK, so here is it: I was able to mount /system as rw with the terminal emulator in ROM toolbox and then create a dummy file named su. Rebooted the phone, both the apps still fail. I will write to the developers. For the time being, I am OK turning data on/off manually along with using MyProfiles for other things. And for the One Power Guard, I believe freezing many of the T-Mobile and LG junk using Titanium and having SetCPU with a little bit under-clocking have already made the battery better. So I can wait. Am also evaluating Craig's Root Battery App instead of OPG. Thank you anyways.
After I root a phone, I would like to be able to uninstall/remove some stock apps (for example, stock Messaging app) and add some new apps (for example, 3d-party Messaging app).
Do I need Titanium app to achieve that? Or is there something more lightweight?
After I complete the setup, I want to disable/ restrict any further software changes. Pretty much the same as Window OS "Admin" VS "Standard User"
So I guess I would need some app manager capable of permission managing.
Any advice on my project? Will my phone be as stable as the original stock after such modding?
The phones: Moto E2 and Moto G2 and G3, Android 5.01 or 6.01
Well, Backing Up the Stock Content before doing any Modding to your Phone is a Good Practice and Extremely Recommended in Case of any worst case scenarios and you can achieve the same by Titanium Back or any Other app Readily available on Play Store.
After Back up, Yes, you can Uninstall PreInstalled apps or any other bloatware that you may don't want in your phone. And Install 3rd Party apps in place of stock Ones.
Talking about Permissions, until/unless you give Root Access to that App, it won't be able to Make any changes in the System. So, you also have to keep a check on giving Root permissions to apps.
Your Phone Will remain stable When you know what actually you are doing with it and what measures could be taken to revert it.
abhinavp649 said:
Talking about Permissions, until/unless you give Root Access to that App, it won't be able to Make a.
Click to expand...
Click to collapse
Once the phone is rooted, will I be able to block/restrict both: uninstalling apps (which are already installed) and installing new apps? The phone will be used by my kids, so I want to prevent them from making any phone changes.
rybshik said:
Once the phone is rooted, will I be able to block/restrict both: uninstalling apps (which are already installed) and installing new apps? The phone will be used by my kids, so I want to prevent them from making any phone changes.
Click to expand...
Click to collapse
You can't restrict to install and uninstall apps. As abhinavp649 said the application makes modifications to the system if you give root permission to them. If you are using SuperSU superuser app then you can set pin to grant root permission to the app from the settings of supersu
rybshik said:
Once the phone is rooted, will I be able to block/restrict both: uninstalling apps (which are already installed) and installing new apps? The phone will be used by my kids, so I want to prevent them from making any phone changes.
Click to expand...
Click to collapse
To Prevent app from uninstalling the best way is to hide it From Home screen Or Make that as System.
And Revoke SU permissions from those apps which can uninstall system apps or any similar one.
Hit thanks if Helped :laugh:
abhinavp649 said:
to hide it From Home screen Or Make that as System.:
Click to expand...
Click to collapse
How can I do that?
Additionally, can I, for example, turn on Location (GPS) and prevent the phone user from turning it OFF? thanks!
rybshik said:
How can I do that?
Additionally, can I, for example, turn on Location (GPS) and prevent the phone user from turning it OFF? thanks!
Click to expand...
Click to collapse
Installing an App as system is a easy and you can find tools easily on play store. Just search 'make app system' or something else similar.
Using GPS to prevent Turn off? I think you are expecting too too much out of a device.
However, you can disable Power Off from options you get by holding lock button.
To do this You Have to Install Xposed Framework in your Device.
Xposed Framework allows you to do Amazing modding to your Android device. You can just do everything with the device(Exceptions are always present)
rybshik said:
How can I do that?
Additionally, can I, for example, turn on Location (GPS) and prevent the phone user from turning it OFF? thanks!
Click to expand...
Click to collapse
If you are thinking of turning on GPS for the sake of tracking your kids, then make sure you tell them you are doing so. Have known a few people that got into legal trouble for not doing so.
In the end if the kids are smart enough there will be nothing you can really do as they can just reset the device and everything you did is gone.
zelendel said:
nothing you can really do as they can just reset the device
Click to expand...
Click to collapse
So, can I prevent that by disabling/removing or password-protecting the option of "Factory Reset" on a rooted Android 6.0?
rybshik said:
So, can I prevent that by disabling/removing or password-protecting the option of "Factory Reset" on a rooted Android 6.0?
Click to expand...
Click to collapse
No. You can not restrict or disable factory data reset option by any ways even you are rooted. Some brands like Samsung gives FRP (factory reset protection) to their device. Devices without FRP easily factory data reset by entering in recovery mode or in settings.
For a project I need to install an app in a custom rom as a system app to prevent being uninstalled. The problem comes with Android 6, where some system apps can be disabled. For example, Google apps like Youtube or Gmail can be disabled, but other apps like Calendar, Messages or Clock can't be disabled.
Now I'm placing my apk inside /system/priv-app but my app can be disabled. ¿Any idea how to prevent that?
Thanks in advance!
With custom roms there is no way to prevent it. All it takes is root and a root browser or an adb command.
zelendel said:
With custom roms there is no way to prevent it. All it takes is root and a root browser or an adb command.
Click to expand...
Click to collapse
Thanks for the quick response. Well, I assume that using root or adb apps can be unninstalled.
The only thing I want is to prevent a "normal user" to uninstall the app throught the Android UI.
With the app now on /system/app/my.apk I've achieved to prevent Android from uninstalling the app, but it can be disabled (Android 6.0). So my question is how can I prevent also from disable the app?
dlaballosn said:
Thanks for the quick response. Well, I assume that using root or adb apps can be unninstalled.
The only thing I want is to prevent a "normal user" to uninstall the app throught the Android UI.
With the app now on /system/app/my.apk I've achieved to prevent Android from uninstalling the app, but it can be disabled (Android 6.0). So my question is how can I prevent also from disable the app?
Click to expand...
Click to collapse
As far I know there is no way to prevent it. If there is it will be a bool settings. I would look at an app that doesn't allow disabling it. But I think you might need a Google signature for that.
Search stack overflow and you might find something.
So I've narrowed this down to being an issue with install unknown app permissions. In my list I only have a select few apps and none of the apps request permission when they try to install. Furthermore if I click show system applications nothing more shows.
Anyone else run into this?
Thanks
Dave
TT_Vert said:
So I've narrowed this down to being an issue with install unknown app permissions. In my list I only have a select few apps and none of the apps request permission when they try to install. Furthermore if I click show system applications nothing more shows.
Anyone else run into this?
Thanks
Dave
Click to expand...
Click to collapse
Not sure but if the apks that you are trying to install require writing to the Android\data, Android\media or Android\obb directories then you have a problem on Android 11. I've tried apks that need to write data here and they won't install. Android 11 has made these directories read only :-( except for official Google playstore apps. Android 10 allowed writing to them from any app.
Gordster said:
Not sure but if the apks that you are trying to install require writing to the Android\data, Android\media or Android\obb directories then you have a problem on Android 11. I've tried apks that need to write data here and they won't install. Android 11 has made these directories read only :-( except for official Google playstore apps. Android 10 allowed writing to them from any app.
Click to expand...
Click to collapse
Scoped storage is an iPhone nightmare come true. Not needed and a system burden.
Big sister Gookill thinks you're too stupid to keep your phone secure.
Pie was the last good Android OS... Android has been in a high G flat spin since then and is descending faster with each new version.
Gordster said:
Not sure but if the apks that you are trying to install require writing to the Android\data, Android\media or Android\obb directories then you have a problem on Android 11. I've tried apks that need to write data here and they won't install. Android 11 has made these directories read only :-( except for official Google playstore apps. Android 10 allowed writing to them from any app.
Click to expand...
Click to collapse
No idea the destination path but they install just fine in an app which ALREADY is listed in install unknown apps. Anything that isn't never requests permission and it never added to this area to be able to modify the permission. It may have been the app i was trying to use (older version of ES file explorer) was too old to request the correct permission.
TT_Vert said:
No idea the destination path but they install just fine in an app which ALREADY is listed in install unknown apps. Anything that isn't never requests permission and it never added to this area to be able to modify the permission. It may have been the app i was trying to use (older version of ES file explorer) was too old to request the correct permission.
Click to expand...
Click to collapse
Many older pre-scoped storage era apps won't load on 11. Updated ones should.
Even with Android 10 there's a lose of functionality; for instance Karma Firewall loses its useful logging feature and trusted overlay apps are gutted.
blackhawk said:
Many older pre-scoped storage era apps won't load on 11. Updated ones should.
Even with Android 10 there's a lose of functionality; for instance Karma Firewall loses its useful logging feature and trusted overlay apps are gutted.
Click to expand...
Click to collapse
Yeah I put a newer version of ES file explorer on and it did request the permissions. My fault, sorry to bother you all.
Dave