Min and target SDK

[ghost]

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.

[ale5000-git]

Everything is opinable, I use microG in KitKat perfectly.
And with not to much effort it can also be compiled for SDK 14.

Those that don't follow consumism may want to be able to use old devices even without security.
microG is perfect for old devices.

[ghost]

Of course, but this is definitely a bad Opinion for sure...14 is ridiculous...Better but it should be 21/26 or like that...

Security is not consumism for making at least the bare minimum effort for their Security...You could buy a Pixel and use it 7 Years with Updates, please never label something like that again. Your choice is not wise, because you should prioritize Security, rather than no Security Devices...MicroG should be perfect for Security and Privacy...Your just helping them with their bad Habits with keeping old Phones but imagine if every App would be Android 14/15...They would must to change their Habits. And also MicroG is totally not private...It sends Data to Google still...

[ale5000-git]

You suppose only phones used as "phone" can use microG.

There are many old Android emulators for PC that works perfectly with microG, in addition one can use old phones without SIM to play music or using some old apps.

microG make the phone faster compared to GPS, so even excluding security it is better.

[ghost]

Yea, that might be true and I appreciate your work but these were just my wishes and my view from a user perspective.

[JonnyTech]

@Jeffrey2307 if you want to have a higher api version then you are free to fork and build your own. The code is all open and available. But please to not force your opinion which will hinder many of us with older devices. The current code works with many devices, old and new. Unless you have a specific functionality issue which needs addressing...?

[ghost]

@JonnyTech If I would be a developer than I had already forked it and would not ask here. I never forced anyone, please don't claim something which is not true. Your accusing randomly...Who should I hinder, when I myself use MicroG and I only told my Opinion and my Wish. I think everyone should be able to express theirself and if they are not happy with something. It's not about functionality...I mentioned about MicroG being not private and my Wish about SDK...Please calm down...Understand what I ask and my Words, before being in panic...

[JonnyTech]

@Jeffrey2307 "force" was obviously too strong a word. There was no "panic" in my post. Just a bit annoyed when you state that we should buy new devices and "must" change our ways. Carry on, I'm out. Peace and calm.

[ghost]

But why are you feeling offended, if you feel like you not need to buy a new Phone or need to change your way? People feel triggered by everything now a days, that's crazy...Me too.

[grenadin]

For me
"Devices...MicroG should be perfect for Security and Privacy" I agree with this statement.

But this statement doesn't agree. People had their own taste.
"...Your just helping them with their bad Habits with keeping old Phones but imagine if every App would be Android 14/15...They would must to change their Habits. And also MicroG is totally not private...It sends Data to Google still..."

I had a choice for use old phone. MicroG not spoil me for bad habit. If every app update to 14/15 why I had to update app. sometime I could sent old phone to my family.

Bad habits do not put people at risk in every case. It is the responsibility of the individual to protect themselves from risk. If you see a car about to hit you and you do not take steps to protect yourself, it is your fault. Therefore, choosing to use an old mobile phone is the responsibility of each person to find a way to protect themselves as well.

So a smart choice, if this community has a poll asking what the minimum and tarket sdk should be and let’s develop it together.

[ghost]

But this statement doesn't agree. People had their own taste. "...Your just helping them with their bad Habits with keeping old Phones but imagine if every App would be Android 14/15...They would must to change their Habits. And also MicroG is totally not private...It sends Data to Google still..."

That's true but not every taste is good for sure. Security should not be a taken easy like that, but never mind.

I had a choice for use old phone. MicroG not spoil me for bad habit. If every app update to 14/15 why I had to update app. sometime I could sent old phone to my family.

Everyone has that choice, but that does not mean, that it is the best recommendable choice...That's your opinion but I see it different. Not update App...Update the Phone, I said. Yes, you could do that and buy a new Phone afterwards for example.

Bad habits do not put people at risk in every case. It is the responsibility of the individual to protect themselves from risk. If you see a car about to hit you and you do not take steps to protect yourself, it is your fault. Therefore, choosing to use an old mobile phone is the responsibility of each person to find a way to protect themselves as well.

I totally don't agree with that...Most bad Habits are not bringing People to a good ending...That's why it is called a bad Habits, because it is not good. Of course, but you let it seem not bad at all...Of course and you decided to say that if you let a car hit you, that this would be a choice which would be okay...That's ridiculous...With an old Phone you can never protect yourself really...It is like a old car which is broken but your driving it, without thinking that you could die of that...

So a smart choice, if this community has a poll asking what the minimum and tarket sdk should be and let’s develop it together.

I agree on this nice Idea!

[BurhanBudak]

Kind of topic but would removing 32-bit support bump up the SDK version? I think users complain about the issue of apps recognizing Companion as a older version, if so, Companion needs to do better at spoofing.

[ale5000-git]

As general suggestion: there is no need to argue, everyone can have their say while always remaining polite.

My opinion is that a user is always right (right a salesman would say) :-)
For me a user should be able to choose to do what it want and know their risks; so forcing to update Android isn't like a good thing.
Think if the goverment would force you to buy a new home because yours is not safe enough; certainly in a perfect world it would works but in today's world it would end up with people sleeping on the streets.

PS: Galaxy S2 have a working "32-bit only" Android 13.

[ale5000-git]

I think users complain about the issue of apps recognizing Companion as a older version, if so, Companion needs to do better at spoofing.

This is completely unrelated to min SDK or bitness.

[ale5000-git]

Target SDK can be increased without reduce devices support but it wasn't already done because it require code changes otherwise microG will break or have issues.

[ghost]

Target SDK can be increased without reduce devices support but it wasn't already done because it require code changes otherwise microG will break or have issues.

And will that happen, that the Target SDK will be maken higher?

[ghost]

At least make the Target SDK from MicroG Companion, MicroG Services and MicroG Services Framework Proxy to 35 and everyone would be happy. That would be a solution for everyone. Because it is on 29 or 23 for the Proxy which is to low for Target SDK...MicroG should support Android 15 (Target SDK 35) too! Otherwise it would make Problems...Like for example I get a warning that this App is to low and for older Android Version. Making the Target SDK to 35 would fix this Problem and warning for me.

[mar-v-in]

Changing the target SDK version also does other things than just getting rid of that one-time warning. Very likely, if you were to just change the target SDK to 35, something will break and you will be less happy than if you just see that warning once. Eventually, we will do this upgrade, but it takes time and intensive testing to do so.

[ghost]

Changing the target SDK version also does other things than just getting rid of that one-time warning. Very likely, if you were to just change the target SDK to 35, something will break and you will be less happy than if you just see that warning once. Eventually, we will do this upgrade, but it takes time and intensive testing to do so.

I understand that totally and thank you. I hope that this will come true. I can understand that too.

[ale5000-git]

@PrivacyAndSecurity
Target SDK isn't just to declare that the app run on any particular version but change the behaviour of the app.

For example (just an example, not a real thing):
App target API 30 a function works without require a permission
App target API 31 a function no longer works without a granted permission

Now if in that app you bump the target SDK without fix the code to handle the new permission then the app will no longer works corrently (at least the part that require it).

[ghost]

@PrivacyAndSecurity Target SDK isn't just to declare that the app run on any particular version but change the behaviour of the app.

For example (just an example, not a real thing): App target API 30 a function works without require a permission App target API 31 a function no longer works without a granted permission

Now if in that app you bump the target SDK without fix the code to handle the new permission then the app will no longer works corrently (at least the part that require it).

I understand the points. It makes sense, of course.

[BurhanBudak]

PS: Galaxy S2 have a working "32-bit only" Android 13.

Cool and nice, but 15 minutes of SoT isnt that useful, also no volte( I still own a i9100 but it collects dust).

But the issue from users can't be FOMO of a higher SDK, it must be other factors like apps not recognizing Companion.

[ale5000-git]

But the issue from users can't be FOMO of a higher SDK, it must be other factors like apps not recognizing Companion.

It is unrelated, other apps cannot detect that, they only detect it to be old because some features are missing.
For example some apps may try to bind to com.google.android.play.core.integrityservice.BIND_INTEGRITY_SERVICE and since it isn't supported claim that it is old; this specific case will be fixed when #2599 is merged.