This repository was archived by the owner on Mar 6, 2026. It is now read-only.
Improve README.md#1
Open
GfEW wants to merge 7 commits into
Open
Conversation
… clearing data Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
In some custom ROMs (e.g., Huawei), the AOSP-default string names are not used which causes the app to crash as it attempts to get the value of those strings. Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
…er IDs Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
…of RuntimeException Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
If the size of the text being copied exceeds 1 MB, it is stored in a temporary file and the file URI is copied instead of the text itself. During pasting, the supplied text/URI or any other type of data is coerced to text value. This required some nasty workarounds for Sora Editor which does not inherently support such copy and pasting. Signed-off-by: Muntashir Al-Islam <muntashirakon@riseup.net>
According to MuntashirAkon/AppManager#1603 (comment) , making sure not to "use ADB on both builds at the same time" doesn't suffice, testers rather need to explicitly disable the use of ADB in one build, even if going to be uninstalled, _before_ enabling it in the other. That's relevant info, it may save testers hours of pointless troubles. Also added a sentence that helps to decide which build to use if unsure.
3 tasks
dff0497 to
934c7e7
Compare
cac57c0 to
f083cbe
Compare
1f2d08f to
7219e19
Compare
f831df7 to
19cf8ae
Compare
47d609c to
f16d401
Compare
e92ea36 to
144fc3a
Compare
e4c8863 to
6270c19
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently,
README.mdwarns that ADB users "may not use ADB on both builds at the same time". However in my experience, as well as confirmed by MuntashirAkon/AppManager#1603 (comment), that doesn't suffice.Testers rather need to explicitly disable the use of ADB in one build before enabling it in the other, even if the former is to be uninstalled. That's relevant information, it may save testers hours of pointless troubles.
Also added a sentence that helps to decide which build to use if unsure.