Use Cases
In the event where a source causes a 'boot loop' type cycle when starting the app, a button to disable the offending source to continue would be beneficial.
Proposal
My idea is a 5th button on the bottom that either just disables the source, or lets you go to your sources tab to disable the offending sources. Currently, an app that throws an error of some sort that causes the app error screen on startup, the only options are: submit, share, restart, and close (and check for update). Checking for update is useful if the app error is an updatable fix situation; but if its net nanny induced, none of the options really help.
References
I havent seen any other issues similar to this yet
Version 381
Google pixel 7 pro
Graphene os
Use Cases
In the event where a source causes a 'boot loop' type cycle when starting the app, a button to disable the offending source to continue would be beneficial.
Proposal
My idea is a 5th button on the bottom that either just disables the source, or lets you go to your sources tab to disable the offending sources. Currently, an app that throws an error of some sort that causes the app error screen on startup, the only options are: submit, share, restart, and close (and check for update). Checking for update is useful if the app error is an updatable fix situation; but if its net nanny induced, none of the options really help.
References
I havent seen any other issues similar to this yet
Version 381
Google pixel 7 pro
Graphene os