Min and target SDK
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
Hey,
i saw that Microg Services (com.google.android.gms) has target SDK 29 and minimum SDK 19 I wanted to ask if you could make Target SDK to 35 for Android 15 and Minimum SDK to 21/23/26/28/29/31? (Higher is always better)
And I saw that Microg Services Framework Proxy (com.google.android.gsf) has even lower SDK. Target SDK is 23 and Minimum SDK is 10. Can you make Target SDK to 35 for Android 15 and Minimum SDK to 21/23/26/28/29/31? (Higher is always better)
And I don't know about the Minimum and Target SDK of MicroG Companion (com.android.vending) but if it is like that too, then I hope you make it higher too!
A higher Minimum SDK version implies that your app supports fewer Android versions, minimizing compatibility issues. Because higher SDK means also Versions which are supported better. It makes the work easier. because Android 12 (SDK 31) is the last version that receives security patches. Further more, the less minSdk, the more internal compatibility layers, techniques etc. For example, lower SDK versions require v1/v2 signing, have somewhat different optimization levels, etc.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the Android build configuration for com.google.android.gms, com.google.android.gsf, and the MicroG Companion app to find their current minimum and target SDK values. Confirm which SDK levels are supported for each component, update the configuration consistently, and build or test the affected apps to verify the requested Android 15 target and chosen minimum SDK.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- build-system, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100