I can hardly find any informatie on how to install Greenify on a multi(ple) user setup.
In my case, Android 4.4 and 5.0, non-rooted tablets.
Does Greenify work on al users (present on tablet) when installed on main-account or do I have to install it on all present user-accounts?
bemoo said:
I can hardly find any informatie on how to install Greenify on a multi(ple) user setup.
In my case, Android 4.4 and 5.0, non-rooted tablets.
Does Greenify work on al users (present on tablet) when installed on main-account or do I have to install it on all present user-accounts?
Click to expand...
Click to collapse
In a non-rooted configuration I suspect Greenify will need to be installed and configured on each sub-account. That might present headaches/issues with some operations like auto hibernate and screen off.
Not a common usage scenero; you will likely need to learn/adapt on-the-fly.
Related
I now have a second Thor, and it's on 3.0.5. What kind of things can I do to this?
fdigl said:
I now have a second Thor, and it's on 3.0.5. What kind of things can I do to this?
Click to expand...
Click to collapse
Some suggestions:
-root and block OTA with HDX toolkit (link)
-install TWRP
-update bootloader to 3.2.3 (link)
-ROMS: Nexus 2.0.5 or CM11
-optional: unlock bootloader (thread)
-ROMS: as above plus CM12
Unlocking the bootloader is the most involved but opens additional options and (more importantly) offers a more robust recovery capability should things go wrong.
Most important thing you can do now is 1) stay off WiFi until OTA is effectively blocked; and 2) read, read and read some more. You've likely seen numerous 'brick' posts. Most were the result of rushed actions and/or incomplete research. Do your homework and ask questions along the way. Good luck.
Davey126 said:
Some suggestions:
-root and block OTA with HDX toolkit (link)
-install TWRP
-update bootloader to 3.2.3 (link)
-ROMS: Nexus 2.0.5 or CM11
-optional: unlock bootloader (thread)
-ROMS: as above plus CM12
Unlocking the bootloader is the most involved but opens additional options and (more importantly) offers a more robust recovery capability should things go wrong.
Most important thing you can do now is 1) stay off WiFi until OTA is effectively blocked; and 2) read, read and read some more. You've likely seen numerous 'brick' posts. Most were the result of rushed actions and/or incomplete research. Do your homework and ask questions along the way. Good luck.
Click to expand...
Click to collapse
Thanks! In Xposed Installer, the framework section is just blank white. No buttons or dropdowns, just white. Everything else in the app appears normal. I can't install the framework for HDXposed.
fdigl said:
Thanks! In Xposed Installer, the framework section is just blank white. No buttons or dropdowns, just white. Everything else in the app appears normal. I can't install the framework for HDXposed.
Click to expand...
Click to collapse
HDXposed is not on the list. There is no need for this module as it has long been depreciated and of questionable value given more current alternatives. Strongly suggest not installing stuff or traveling your own path. Also recommend uninstalling Xposed framework and any other 'system' level hacks/utilities until your devices is otherwise upgraded and stable. Just asking for trouble ...
While I have the pulpit don't mess with build.prop or any system file other than OTAcerts (even that can be avoided). If you are following a guide that indicates one/both should be modified you're in the wrong place. Post a question; someone will help you get back on track.
Davey126 said:
HDXposed is not on the list. There is no need for this module as it has long been depreciated and of questionable value given more current alternatives. Strongly suggest not installing stuff or traveling your own path. Also recommend uninstalling Xposed framework and any other 'system' level hacks/utilities until your devices is otherwise upgraded and stable. Just asking for trouble ...
While I have the pulpit don't mess with build.prop or any system file other than OTAcerts (even that can be avoided). If you are following a guide that indicates one/both should be modified you're in the wrong place. Post a question; someone will help you get back on track.
Click to expand...
Click to collapse
Oh, thanks for the info!
Anyways, I have Android Market working but Play Store just crashes while opening. I have the same version of Play Store running on the older Thor, but not this one. It just stops working, but behind the dialogue I can see another one under it, likely the Play Store agreement, but it closes when I close the stopped working dialogue. This makes Play Store unusable.
fdigl said:
Oh, thanks for the info!
Anyways, I have Android Market working but Play Store just crashes while opening. I have the same version of Play Store running on the older Thor, but not this one. It just stops working, but behind the dialogue I can see another one under it, likely the Play Store agreement, but it closes when I close the stopped working dialogue. This makes Play Store unusable.
Click to expand...
Click to collapse
Play Store works great on the three roms previously mentioned while various issues keep cropping up using it with Fire OS. I suggest you flash TWRP, the 3.2.3 bootloader update and Nexus 2.05. Each is relatively low risk (given your favorable starting point; many would love to have that device!) if you follow directions. In the end I think you will be much happier with the overall experience. Perhaps someone else can help if you want to continue with Fire OS 3.x and sideload gapps.
Davey126 said:
Play Store works great on the three roms previously mentioned while various issues keep cropping up using it with Fire OS. I suggest you flash TWRP, the 3.2.3 bootloader update and Nexus 2.05. Each is relatively low risk (given your favorable starting point; many would love to have that device!) if you follow directions. In the end I think you will be much happier with the overall experience. Perhaps someone else can help if you want to continue with Fire OS 3.x and sideload gapps.
Click to expand...
Click to collapse
I have Safestrap 3.72 on there, does that count as TWRP? Despite this, I'd prefer to keep Fire OS on here.
To get gapps working on fire is, look at the version of google play services. Some people have no problems. I am running 7.0.99 I think.
fdigl said:
I have Safestrap 3.72 on there, does that count as TWRP? Despite this, I'd prefer to keep Fire OS on here.
Click to expand...
Click to collapse
Nope. TWRP in Safestrap does not operate in 'native' mode. If you prefer Fire OS then your options are limited:
- create another slot in Safestrap and install Nexus 1.0.5 (note different version number) which offers full Play Store support. Make sure you preserve your existing copy of Fire OS in the base slot; bad things happen if it gets trashed. You can then toggle between Fire OS and Nexus although the two roms can not share applications (they operate independently)
- continue wrestling Play Store (and other Google components) on Fire OS 3.x.
- permit your device to upgrade to the version 4.x of Fire OS which is a modest improvement over 3.x. You will be faced with the same headaches getting Google Components to play nice with Fire OS but you will likely receive better community support. Please note this is a one way trip. Once you go beyond 3.2.6 you can not make the modifications required to run most non-Amazon roms like CM11/12.
Davey126 said:
Nope. TWRP in Safestrap does not operate in 'native' mode. If you prefer Fire OS then your options are limited:
- create another slot in Safestrap and install Nexus 1.0.5 (note different version number) which offers full Play Store support. Make sure you preserve your existing copy of Fire OS in the base slot; bad things happen if it gets trashed. You can then toggle between Fire OS and Nexus although the two roms can not share applications (they operate independently)
- continue wrestling Play Store (and other Google components) on Fire OS 3.x.
- permit your device to upgrade to the version 4.x of Fire OS which is a modest improvement over 3.x. You will be faced with the same headaches getting Google Components to play nice with Fire OS but you will likely receive better community support. Please note this is a one way trip. Once you go beyond 3.2.6 you can not make the modifications required to run most non-Amazon roms like CM11/12.
Click to expand...
Click to collapse
It seems that I got Play Store 4.6.17 to work, but I'm unable to download anything (will spam ANRs). In HDXposed, did the content provider fix have to do with any of this? I have it on the older Thor, but not on the new one. If it does, what would be the alternative way of applying that fix?
EDIT: Any version of Play Store is working, just unable to download/install from the store.
lekofraggle said:
To get gapps working on fire is, look at the version of google play services. Some people have no problems. I am running 7.0.99 I think.
Click to expand...
Click to collapse
I know how to get GApps working, it's just Play Store that's acting up.
fdigl said:
I know how to get GApps working, it's just Play Store that's acting up.
Click to expand...
Click to collapse
I meant play store. That is the problem most people are having. Take a look at the two threads in the general section.
Sent from my KFTHWI using Tapatalk
fdigl said:
Thanks! In Xposed Installer, the framework section is just blank white. No buttons or dropdowns, just white. Everything else in the app appears normal. I can't install the framework for HDXposed.
Click to expand...
Click to collapse
What version of Xposed Installer are you using?
Davey126 said:
HDXposed is not on the list. There is no need for this module as it has long been depreciated and of questionable value given more current alternatives. Strongly suggest not installing stuff or traveling your own path. Also recommend uninstalling Xposed framework and any other 'system' level hacks/utilities until your devices is otherwise upgraded and stable. Just asking for trouble ...
While I have the pulpit don't mess with build.prop or any system file other than OTAcerts (even that can be avoided). If you are following a guide that indicates one/both should be modified you're in the wrong place. Post a question; someone will help you get back on track.
Click to expand...
Click to collapse
EncryptedCurse said:
What version of Xposed Installer are you using?
Click to expand...
Click to collapse
I tried the latest, and v32 - the one that worked on my Thor on 3.2.5. The tablet in question is on 3.0.5, but installed TWRP and the 3.2.3 boot loader zip was flashed.
For what ever reason ever since I went from 4.4.4 to 5.1.1 (TW) on my Note 4 i have not been able to cut wake lock paths. To be more clear I did not upgrade to 5.1.1 it was a clean flash.The option is no longer there, it no longer even displays the path when an app automatically awakens from hibernation. I'm running the latest beta version of greenify with the donation/zoomed features enabled. Can anyone help?
XBlackChaosX said:
For what ever reason ever since I went from 4.4.4 to 5.1.1 (TW) on my Note 4 i have not been able to cut wake lock paths. To be more clear I did not upgrade to 5.1.1 it was a clean flash.The option is no longer there, it no longer even displays the path when an app automatically awakens from hibernation. I'm running the latest beta version of greenify with the donation/zoomed features enabled. Can anyone help?
Click to expand...
Click to collapse
It works for me even on M.
Is Greenify enabled in Device Administrators?
Are you rooted? If not, have you enabled Greenify in Accessibility?
Are you using Supersu latest version?
tnsmani said:
It works for me even on M.
Is Greenify enabled in Device Administrators?
Are you rooted? If not, have you enabled Greenify in Accessibility?
Are you using Supersu latest version?
Click to expand...
Click to collapse
Yes to all 3. This is so weird. I would like to cut a few paths but I can't even see any wake paths let alone cut any.
I'm having the same Problem. For example i start Instagram, Facebook starts, too, but i can't cut off the wakeup pathes. I'm on Resurrection Remix (CM12.1 - Android 5.1.1) Rom on Galaxy S3 GT-i9300 with Xposed.
I flashed this Rom clean today. Before it was working fine! Greenify Version is 2.6.2 (i don't understand the function of 2.7...)
Any idea?
Some ROM may disable the logcat module of Android by default, please check your ROM configuration tool (if any) to enable logcat.
Any idea where i could find it?
Ok, got it: I had to activate "Android Logging" in Boeffla Config App!
Why DEGOOGLE ?​Degoogling is removing Google apps (gapps) from an android device; in order to gain more performance, privacy and battery life.
The script works on all android devices with gapps installed and removes ONLY irrelevant gapps.
Degoogle script for both Linux and Windows can be downloaded below respectively.
NB: This is an Android Debug Bridge (adb) script that only removes Google apps that are never used and stay idle in our phone; running in the background and taking unnecessary space.
BUGS: Phone works perfectly fine after this. No issues, like nothing changed except for better battery life, more storage space and a bit of performance.
Oops that's not a bug XD
PREREQUISITES:
'USB Debugging' ENABLED
'adb' INSTALLED - https://dl.google.com/android/repository/platform-tools-latest-linux.ziphttps://dl.google.com/android/repository/platform-tools-latest-windows.zip - Recommended
And of course, in a PC
Edit: list - https://spaceb.in/UylgPfrU
You can manually install both root and non-root users.
Side note: Since you stumbled across the thread I highly recommend you to get this open-source tool called "universal debloater". This tool is really nice with a minimal user interface, it recently gained a GUI work profile, it's like a super app manager, can read all debloated files and restore with ease and it also recommends which one to debloat. AND yes root is not required.. win-win​
LINK IS DOWN...!!!
Can you post a list of what Gapps are purged?
TheThunderspy said:
LINK IS DOWN...!!!
Click to expand...
Click to collapse
I deleted the file on my Google drive after moving to custom ROM
But I updated OP just in case.
CarbonGTR said:
Can you post a list of what Gapps are purged?
Click to expand...
Click to collapse
I can't remember some but I have updated OP
Original Google Pixel here with the latest Pixel-Dust-CAF Android 10 ROM. I wanted to debloat my phone with Magisk and Terminal Debloater module to make a Wi-Fi only device. Telephony, SMS, and mobile data would never be used on this phone. It worked, but I broke 2 feature I wanted to keep:
1. Default WiFi Printing. Restoring Print-related Apps did not resolve the issue, but maybe Default Printing depends on other System Apps that need restoration. Restoring the following Apps did not bring back default printing:
BuiltInPrintService^=/system/app/BuiltInPrintService
PrintSpooler^=/system/app/PrintSpooler
PrintRecommendationService^=/system/app/PrintRecommendationService
Click to expand...
Click to collapse
2. Certificate installation, even though Certificate Installer App was not removed. I was able to install AdGuard HTTPS certificate before debloating, but after debloating Certificate Installer App simply closes and does not install anything.
Here's my full debloat list and I hope someone can tell me which Apps I shouldn't have removed due to their vital importance to Android OS and printing services:
VzwOmaTrigger^=/system/priv-app/VzwOmaTrigger
Telecom^=/system/priv-app/Telecom
ManagedProvisioning^=/system/priv-app/ManagedProvisioning
CNEService^=/system/priv-app/CNEService
Tag^=/system/priv-app/Tag
MusicFX^=/system/priv-app/MusicFX
AwakeWallpaper^=/system/priv-app/AwakeWallpaper
TelephonyProvider^=/system/priv-app/TelephonyProvider
Mms^=/system/priv-app/Mms
SharedStorageBackup^=/system/priv-app/SharedStorageBackup
MmsService^=/system/priv-app/MmsService
ONS^=/system/priv-app/ONS
TeleService^=/system/priv-app/TeleService
OemDmTrigger^=/system/priv-app/OemDmTrigger
OPScreenRecorder^=/system/priv-app/OPScreenRecorder
OmniRecord^=/system/priv-app/OmniRecord
CallLogBackup^=/system/priv-app/CallLogBackup
CellBroadcastReceiver^=/system/priv-app/CellBroadcastReceiver
KeyChain^=/system/app/KeyChain
WAPPushManager^=/system/app/WAPPushManager
CarrierDefaultApp^=/system/app/CarrierDefaultApp
BluetoothMidiService^=/system/app/BluetoothMidiService
PrintSpooler^=/system/app/PrintSpooler
PrintRecommendationService^=/system/app/PrintRecommendationService
BookmarkProvider^=/system/app/BookmarkProvider
OsuLogin^=/system/app/OsuLogin
PacProcessor^=/system/app/PacProcessor
Stk^=/system/app/Stk
Traceur^=/system/app/Traceur
SimAppDialog^=/system/app/SimAppDialog
PixelDustWallpapers^=/system/app/PixelDustWallpapers
ims^=/system/app/ims
LiveWallpapersPicker^=/system/app/LiveWallpapersPicker
BasicDreams^=/system/app/BasicDreams
CtsShimPrebuilt^=/system/app/CtsShimPrebuilt
BuiltInPrintService^=/system/app/BuiltInPrintService
CompanionDeviceManager^=/system/app/CompanionDeviceManager
WallpaperBackup^=/system/app/WallpaperBackup
HideCutout^=/system/app/HideCutout
PlatformCaptivePortalLogin^=/system/app/PlatformCaptivePortalLogin
SprintDM^=/system/product/priv-app/SprintDM
GCS^=/system/product/priv-app/GCS
DCMO^=/system/product/priv-app/DCMO
SettingsIntelligence^=/system/product/priv-app/SettingsIntelligence
PixelLiveWallpaperPrebuilt^=/system/product/priv-app/PixelLiveWallpaperPrebuilt
WallpaperCropper^=/system/product/priv-app/WallpaperCropper
HotwordEnrollmentXGoogleWCD9335^=/system/product/priv-app/HotwordEnrollmentXGoogleWCD9335
CarrierSettings^=/system/product/priv-app/CarrierSettings
PixelSetupWizard^=/system/product/priv-app/PixelSetupWizard
CarrierSetup^=/system/product/priv-app/CarrierSetup
DiagMon^=/system/product/priv-app/DiagMon
ConnMetrics^=/system/product/priv-app/ConnMetrics
HotwordEnrollmentOKGoogleWCD9335^=/system/product/priv-app/HotwordEnrollmentOKGoogleWCD9335
GoogleOneTimeInitializer^=/system/product/priv-app/GoogleOneTimeInitializer
MatchmakerPrebuiltPixel4^=/system/product/priv-app/MatchmakerPrebuiltPixel4
AndroidMigratePrebuilt^=/system/product/priv-app/AndroidMigratePrebuilt
ConfigUpdater^=/system/product/priv-app/ConfigUpdater
TurboPrebuilt^=/system/product/priv-app/TurboPrebuilt
OBDM_Permissions^=/system/product/priv-app/OBDM_Permissions
ConnMO^=/system/product/priv-app/ConnMO
CarrierServices^=/system/product/priv-app/CarrierServices
EmergencyInfo^=/system/product/priv-app/EmergencyInfo
obdm_stub^=/system/product/priv-app/obdm_stub
SprintHM^=/system/product/priv-app/SprintHM
WellbeingPrebuilt^=/system/product/priv-app/WellbeingPrebuilt
GooglePartnerSetup^=/system/product/priv-app/GooglePartnerSetup
DMService^=/system/product/priv-app/DMService
StorageManager^=/system/product/priv-app/StorageManager
WfcActivation^=/system/product/priv-app/WfcActivation
CarrierConfig^=/system/product/priv-app/CarrierConfig
MyVerizonServices^=/system/product/priv-app/MyVerizonServices
Velvet^=/system/product/priv-app/Velvet
PrebuiltBugle^=/system/product/app/PrebuiltBugle
PrebuiltDeskClockGoogle^=/system/product/app/PrebuiltDeskClockGoogle
Chrome^=/system/product/app/Chrome
TrichromeLibrary^=/system/product/app/TrichromeLibrary
PixelDustThemeStub^=/system/product/app/PixelDustThemeStub
Music^=/system/product/app/Music
VZWAPNLib^=/system/product/app/VZWAPNLib
WallpapersBReel2019^=/system/product/app/WallpapersBReel2019
MarkupGoogle^=/system/product/app/MarkupGoogle
PhotoTable^=/system/product/app/PhotoTable
fastdormancy^=/system/vendor/app/fastdormancy
vzw_msdc_api^=/system/vendor/app/vzw_msdc_api
RCSBootstraputil^=/system/vendor/app/RCSBootstraputil
imssettings^=/system/vendor/app/imssettings
datastatusnotification^=/system/vendor/app/datastatusnotification
colorservice^=/system/vendor/app/colorservice
embms^=/system/vendor/app/embms
radioconfig^=/system/vendor/app/radioconfig
SecureExtAuthService^=/system/vendor/app/SecureExtAuthService
shutdownlistener^=/system/vendor/app/shutdownlistener
QAS_DVC_MSP^=/system/vendor/app/QAS_DVC_MSP
QtiTelephonyService^=/system/vendor/app/QtiTelephonyService
Click to expand...
Click to collapse
It would be nice if I could find definitive explanations for each of the Apps I removed.
@DirtyAngelicaSecured
I'ld use LOGCAT, the command-line tool that dumps all system messages.
FYI:
How to make use of LOGCAT is explained here.
Hello,
I recently installed GrapheneOS on my Pixel 6 and I want to use XPrivacyLua on it. But when I install and activate LSPosed (1.8.3) and reboot then it says there's no LSPosed installed. But in Magisk it is loaded together with Shamiko. Shamiko works fine, but I wasn't able to use LSPosed yet. Does anybody know how LSPosed can be used successfully on GrapheneOS?
Thank you,
Oebbler
Oebbler1 said:
Hello,
I recently installed GrapheneOS on my Pixel 6 and I want to use XPrivacyLua on it. But when I install and activate LSPosed (1.8.3) and reboot then it says there's no LSPosed installed. But in Magisk it is loaded together with Shamiko. Shamiko works fine, but I wasn't able to use LSPosed yet. Does anybody know how LSPosed can be used successfully on GrapheneOS?
Thank you,
Oebbler
Click to expand...
Click to collapse
you lose more for the little gain you get by using xprivacylua. also graphene os isn't meant to be used with root since you defeat the main goal of the os itself: security. it hardens several aspects of android to make it more secure, and that's why things like lsposed won't work.
hellcat50 said:
...graphene os isn't meant to be used with root since you defeat the main goal of the os itself: security.
Click to expand...
Click to collapse
That's a redundant and absurd thing to say. First of all, grapheneos objection to root is realistically tied to support burden and public impression rather than anything practical. Second, root doesn't threaten security if used responsibly. Third, root is HELPFUL for security when used competently.
Now for the other thing... lsposed... avoid like the plague.
Thank you for your answers!
The thing is that I cannot avoid LSPosed for XPrivacyLua on Android 12. I really want to use it in order to avoid tracking by getting IDs and other data from my device. So my question still remains on how to make LSPosed runnable.
I tried to install it with Riru. Riru was telling me that LSPosed is loaded, but the LSPosed app told me it cannot find LSPosed. It seems the same as with LSPosed on Zygisk. Is there any way to get LSPosed (or maybe EdXposed) working?
Oebbler1 said:
Thank you for your answers!
The thing is that I cannot avoid LSPosed for XPrivacyLua on Android 12. I really want to use it in order to avoid tracking by getting IDs and other data from my device. So my question still remains on how to make LSPosed runnable.
I tried to install it with Riru. Riru was telling me that LSPosed is loaded, but the LSPosed app told me it cannot find LSPosed. It seems the same as with LSPosed on Zygisk. Is there any way to get LSPosed (or maybe EdXposed) working?
Click to expand...
Click to collapse
Please read this about ID's: https://grapheneos.org/faq#hardware-identifiers
Thank you! This sounds good, but leaves something out which I also want to do:
I want to allow access to particular contacts for some apps only. And maybe in the future it should be possible to hook some other methods (with XPrivacyLua Pro) that apps use for things I don't want them to do. So I think I cannot avoid LSPosed, EdXposed or something like that. How can this be achieved?
Oebbler1 said:
Thank you! This sounds good, but leaves something out which I also want to do:
I want to allow access to particular contacts for some apps only. And maybe in the future it should be possible to hook some other methods (with XPrivacyLua Pro) that apps use for things I don't want them to do. So I think I cannot avoid LSPosed, EdXposed or something like that. How can this be achieved?
Click to expand...
Click to collapse
Contacts permission does not need any additional hacks to be denied.
hellcat50 said:
you lose more for the little gain you get by using xprivacylua. also graphene os isn't meant to be used with root since you defeat the main goal of the os itself: security. it hardens several aspects of android to make it more secure, and that's why things like lsposed won't work.
Click to expand...
Click to collapse
Unless you're running GrapheneOS via yellow state boot loader (and you checking the finger print each boot), I can't take claims of "root is insecure" quite seriously.
I don't want to deny contacts permission at all, but I want to allow only certain contacts to be seen by some apps. So I want e. g. Telegram or Signal to only see the contacts I am using in these apps. These aren't the same so Telegram's and Signal's access to the contacts list need to be hooked in order to provide individual faked/manipulated lists to these apps.
And maybe in the future some apps do a call to e. g. some app-internal ID which is used for tracking, so I want to hook that later on.
To me it doesn't matter if there are other hacks available to do these things. I'd just like to do that with XPrivacyLua Pro. So how can I get this working on GrapheneOS?
ezdiy said:
Unless you're running GrapheneOS via yellow state boot loader (and you checking the finger print each boot), I can't take claims of "root is insecure" quite seriously.
Click to expand...
Click to collapse
Yeah right rooting makes your device more secure haha. https://madaidans-insecurities.github.io/android.html#rooting
Oebbler1 said:
I don't want to deny contacts permission at all, but I want to allow only certain contacts to be seen by some apps. So I want e. g. Telegram or Signal to only see the contacts I am using in these apps. These aren't the same so Telegram's and Signal's access to the contacts list need to be hooked in order to provide individual faked/manipulated lists to these apps.
And maybe in the future some apps do a call to e. g. some app-internal ID which is used for tracking, so I want to hook that later on.
To me it doesn't matter if there are other hacks available to do these things. I'd just like to do that with XPrivacyLua Pro. So how can I get this working on GrapheneOS?
Click to expand...
Click to collapse
I don't think lsposed will ever work on graphene os. for that you will have to switch the os
hellcat50 said:
Yeah right rooting makes your device more secure haha. https://madaidans-insecurities.github.io/android.html#rooting
Click to expand...
Click to collapse
Applications don't just have access to root if you make it available to yourself. Again, its about the USER being competent and not just granting root permission willy nilly like a total retard. Nice try, but NOPE.
A project to keep an eye on...
GitHub - chriswoope/resign-android-image: Resign Android OS (esp. GrapheneOS) images with your signing keys and add ADB root and other modifications
Resign Android OS (esp. GrapheneOS) images with your signing keys and add ADB root and other modifications - GitHub - chriswoope/resign-android-image: Resign Android OS (esp. GrapheneOS) images wit...
github.com