this post was submitted on 19 May 2026
22 points (95.8% liked)

Android

34224 readers
62 users here now

DROID DOES

Welcome to the Android community on Lemmy. Here you can participate in amazing discussions and events relating to all things Android.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules


1. All posts must be relevant to Android devices/operating system.


2. Posts cannot be illegal or NSFW material.


3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.


4. Non-whitelisted bots will be banned.


5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.


6. Memes are not allowed to be posts, but are allowed in the comments.


7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.


8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.


Community Resources:


founded 3 years ago
MODERATORS
 

Hey, so I have a bunch of items that won't install, saying they're not compatible with my device. Thing is, they were all installed prior to my doing a reset. I just needed to get a fresh clean start after lots of testing stuff cluttered things.

OK so here are things to note: I'm using a Moto g stylus 5g 2023 (XT2315-1) genenv. Android 13. I have TWRP setup as my recovery, and I'm rooted with Magisk which is up to date.

I did not make any upgrades or downgrades of Android, I simple reset. Most things are working fine, but just some APKs won't install.

It is possible that I had previously had an LSposed (Xposed variant) module installed which dealt with this; all it is, is an arbitrary minAPI designation but in no way actually has a compatibility problem. But try as I might, I don't remember specifically installing a module to resolve this. Rather, I suspect perhaps it was dealt with inadvertently by something I happened to install. ¿maybe?

If anyone knows the solution to this, I'd be much-preesh.

you are viewing a single comment's thread
view the rest of the comments
[–] db2@lemmy.world 5 points 1 month ago (2 children)
[–] AndrewZabar@lemmy.world 5 points 1 month ago* (last edited 1 month ago)

I will certainly give it a try, thank you! Actually I'm a bit under the weather and not thinking too clearly because I didn't even think to try installing via ADB with I assume has command line arguments to skip the SDK level. Actually I do have an advanced installer app, which I haven't yet thoroughly explored; maybe it, too, can handle this.

[–] AndrewZabar@lemmy.world 2 points 1 month ago

Also, the thing is, I have installed this on a dozen phones of differing Android versions and different phone models etc. with no problem. I think I have got it on some devices running Android 6 even.