Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is this still relevant? #22

Open
Atemu opened this issue Oct 26, 2024 · 7 comments
Open

Is this still relevant? #22

Atemu opened this issue Oct 26, 2024 · 7 comments

Comments

@Atemu
Copy link

Atemu commented Oct 26, 2024

Hi, I'm wondering whether GsfProxy is still necessary in modern Android because it hasn't seen a release in years.

The docs aren't entirely clear on this and generally appear quite outdated.

@david79111
Copy link

Well, it says gsfproxy is legacy support proxy library so I guess its for older android versions or apps that use old code that needs this

@Atemu
Copy link
Author

Atemu commented Oct 31, 2024

I'd like some confirmation on exactly that.

@david79111
Copy link

So, dev said this:
"It is used only by old apps, so it is still useful but not in all cases."

microg/GmsCore#2623 (comment)

@Atemu
Copy link
Author

Atemu commented Nov 14, 2024

@Sapiosenses is not a µG dev, though they appear to be knowledgeable.

Edit: You were talking about microg/GmsCore#2623 (comment).

@Sapiosenses
Copy link

Sapiosenses commented Nov 14, 2024

So, dev said this: "It is used only by old apps, so it is still useful but not in all cases."

microg/GmsCore#2623 (comment)

Ask yourself:

That service was shutdown by Google almost 10 years ago. That means that no app today that continues to use that old push messaging API will work on any stock Android device.

Furthermore, since that is a GMS service, it will not work on any plain vanilla AOSP-based ROM which was last updated in the last 10+ years, because that functionality would have been removed from AOSP by that time already. (Google moved it to proprietary GMS/Gapps frameworks, like many other things over the years)

Literally the only way ANY app can still use that service, is on a custom ROM running microG. (Which just picks up the communication attempts and forwards them to the current push messaging service)

So then one has to ask themselves, how many apps are there still out there, written in the last ~10 years, that have specifically coded themselves to only have full functionality on a microG device for push messages?

Apps like that were probably written within the first 4 years of Android's existence, if that.

How many of those do you think people are still using??

I'd guess the number is infinitesimally small.

In short: the impact of that being entirely missing will probably go unnoticed by 99.5% of users.

If @ale5000-git thinks it would be easy to update it for A15 that's cool. But I'd be shocked if anyone actually noticed the change outside of the error message that Google added for apps targeting those old APIs on A13-A15 devices.

@ale5000-git
Copy link
Member

I don't think this app does have any problem with Android 15, if you install with adb I think you can bypass the sdk limit.

Beside supporting old apps it is also useful to fake Google since it make sure there is an app called com.google.android.gsf installed.
Although it isn't usually checked apps may choose to detect this.

@ale5000-git
Copy link
Member

To see an app that use it, look here: #17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants