-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add screenshots #54
base: main
Are you sure you want to change the base?
Add screenshots #54
Conversation
Yes, that is under discussion between me and R0S. |
Also, what is the benefit of adding IzzyOnDroid instead of F-Droid? @theimpulson |
IzzyOnDroid is the largest 3rd party F-Droid repo (currently 1120apps) from a former F-Droid contributor. Lots of apps are served there because mostly app devs struggle to make fully FOSS or devs asked to keep there, F-Droid build failures similar cases... Making apps publish to larger audience through IzzyOnDroid motivates devs to go fully FOSS & publish on official F-Droid repo :) Some clients have this repo enabled by default, e.g. Neo Store, Droid-ify, IzzyOnDroid client by Sunil. After successful F-Droid inclusion, we can request to remove from IzzyOnDroid or keep it there if you want to. It's not an issue.
It's not rather than F-Droid the app can co-exist in both the repositories. Besides that if I understand correctly Aurora Store devs are interested in using Dhizuku service as new installer option, why publishing on IzzyOnDroid or any platform would affect their choice? Both are not related at all 🤷🏿♂️ |
Thanks @shuvashish76! Also worth mentioning are the additional checks performed at IzzyOnDroid, which in several cases already prevented F-Droid.org publication running into issues ("early warnings" and such, also things not covered by F-Droid's scans but, when "accidentally found/reported", might lead to releases being removed there). Thanks also for mentioning the clients having IzzyOnDroid enabled by default! Their teams and ours are communicating with each other quite well for best experience and to improve things – for app developers as well as for those using F-Droid-style repos (and of course also for those running such repos). |
|
||
<b>Enable service</b> | ||
This app is similar to Shizuku (ADB) and Magisk (Root) but instead, it shares device owner permissions with other apps. An example use would be having a new Installer in the Aurora Store for allowing devices such as those sold in Japan (and those where normal package installation is blocked) to install apps from third-party app stores. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks oddly similar to my comment on RFP on F-Droid. Please don't use my comment here especially mentioning Aurora Store. Both projects are unrelated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please don't use my comment here especially mentioning Aurora Store. Both projects are unrelated.
IzzyRepo copied your comment & I just used same description here because I don't have any knowledge about how it really works or how different to Shizuku...
Ok I'll remove it, @s1204IT @iamr0s any better suggestions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, first of all, Shizuku and Dhizuku are completely different things. Please focus on each one individually.
Shizuku is for sharing internal shell services, while Dhizuku has no such functionality and is for sharing device owner permissions.
A Device Owner has higher privileges than a Device Admin and can only have one per device.
And you'll need Dhizuku to use the Device Owner across multiple apps.
To explore the features and benefits of Device Owner, try TestDPC.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please don't use my comment here especially mentioning Aurora Store. Both projects are unrelated.
That was my bad then. I've integrated that with the app description to make it a bit clearer what the app is intended for, which was hard to figure by "outsiders" not involved with developing the app or having deep knowledge on the topic otherwise.
Once a "proper" description has been merged to the fastlane structures here, please give me a ping so I enable that on my end and also manually trigger an update for it to be reflected in the IzzyOnDroid repo. Thanks a lot!
As I replied on the Aurora Store issue, I prefer Google Play or F-Droid. |
No description provided.