Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Android now forces apps to include proprietary code for push notifications

reddit.com

Post reply on HN
Print view View original

51–60 of 284 posts

Re: Android now forces apps to include proprietary code for push notifications

#51

Post by Ajedi32 »

So to summarize, to save battery all notifications on Android (since two versions ago) have to go through a single notification service (rather than each app having the option of continuously running in the background and maintaining a connection with its own notification service). Recently Google killed their GCM notifications service in favor of Firebase Cloud Messaging, which (unlike GCM) unfortunately doesn't have an open source library available for it at the moment.

Does that sound right so far?

Anyway, the Telegram-FOSS team claims that this doesn't _actually_ save battery:

> Despite Google's misleading warnings, there is no difference in battery usage between v4.6 in "true background" and v4.9+ with notification.

But this seems rather unlikely to me. Are they saying that an application running continuously in the background uses the same amount of battery as an application that's not running at all? Or am I just misreading that statement?

Re: Android now forces apps to include proprietary code for push notifications

#53

Post by runeks »

Ajedi32 wrote: post #51

So to summarize, to save battery all notifications on Android (since two versions ago) have to go through a single notification service (rather than each app having the option of continuously running in the background and maintaining a connection with its own notification service). Recently Google killed their GCM notifications service in favor of Firebase Cloud Messaging, which (unlike GCM) unfortunately doesn't hav…

> Are they saying that an application running continuously in the background uses the same amount of battery as an application that's not running at all?

A single application running in the background probably uses only a small amount of extra power compared to the notification service alone.

However, a couple dozen applications -- all running in the background in order to enable notifications -- probably consume a lot more power than a single service.

Re: Android now forces apps to include proprietary code for push notifications

#54

Post by jimmaswell »

krn wrote: post #11
geofft wrote: post #2

You can still write free software that uses it and produces a not-entirely-free artifact when compiled, though, right? (Is there a distribution restriction on the artifact, or is it impermissible to link it with GPL apps, or something?) I'm curious if the free software apps are compelled not to link it to preserve the free software status of their code, or just voluntarily refusing on principle (which is laudable, to…

Ubuntu gets around any possible GPL violations by offering to download and install proprietary drivers (ex., Nvidia) and codecs during installation process. Could something similar work for Android apps?

GPL seems like it gets in the way more than it helps.

Re: Android now forces apps to include proprietary code for push notifications

#55

Post by [deleted] »

pzmarzly wrote: post #22
jmkni wrote: post #6

I'd love to know just how different/bare bones AOSP (Android Open Source Project) is to regular Android. As an experiment, I'd love to compile it, put it on a spare phone and use it as my daily driver for a week.

I was using clean LineageOS for over 2 years, recently switching to LineageOS+microG. I'm using APKPure and F-Droid for apps, Chrome for browsing (as in Firefox, last time I checked, one tap separates you from losing all open tabs). Some apps refuse to work or break (e.g. Bitwarden does not sync), some have degraded functionality (e.g. WhatsApp sometimes does not ring when someone is calling you), many are just spamm…

[deleted]

Re: Android now forces apps to include proprietary code for push notifications

#56

Post by curt15 »

Ajedi32 wrote: post #51

So to summarize, to save battery all notifications on Android (since two versions ago) have to go through a single notification service (rather than each app having the option of continuously running in the background and maintaining a connection with its own notification service). Recently Google killed their GCM notifications service in favor of Firebase Cloud Messaging, which (unlike GCM) unfortunately doesn't hav…

> So to summarize, to save battery all notifications on Android (since two versions ago) have to go through a single notification service

And presumably the user has no way to install alternate notification services?

Re: Android now forces apps to include proprietary code for push notifications

#57

Post by pfortuny »

kartan wrote: post #26

> Problem: The Firebase Android client library is proprietary, meaning FOSS apps can not use it. Apps that do not comply are reported to the user as "using too much battery". This is a standard on the industry. From 1999: https://www.theregister.co.uk/1999/11/05/how_ms_played_the_i... It doesn't matter how much money Google is going to have to pay in the future as a fine for this practice. The amount of money that th…

So, if I understand correctly, the GPL prevents you from using a non-free library in your code? (Asking honestly: I have tried to find this elsewhere but the FSF page on the GPL is rather ... convoluted).

If that is so, then this is obviously a killer and quite seemingly arbitrary requirement. Your MS example is quite good.

Re: Android now forces apps to include proprietary code for push notifications

#58

Post by neves »

Ajedi32 wrote: post #51

So to summarize, to save battery all notifications on Android (since two versions ago) have to go through a single notification service (rather than each app having the option of continuously running in the background and maintaining a connection with its own notification service). Recently Google killed their GCM notifications service in favor of Firebase Cloud Messaging, which (unlike GCM) unfortunately doesn't hav…

I think they said they aren't using any more battery than they were using before.

Sure they could implement their software using less battery, but these Google warnings could apply to anything. This app could perform better. This app could be smaller. This app could have less bugs.

The only thing that they can't say is: "This app could be more secure."

Re: Android now forces apps to include proprietary code for push notifications

#59

Post by extropy »

squarefoot wrote: post #44
TeMPOraL wrote: post #19

Earlier quoted context omitted.

I think they already do. Isn't it what Play Services is really all about?

They never did. Releasing the source contributed creating the developers ecosystem we have today. What Google fears more than the Armageddon would be someone making a truly FOSS operating system capable of running on Android devices, and they prevent that by keeping device drivers and firmware tightly locked.

IMO Android is working towards having a compatibility layer so that drivers can be freely shared across distros.

Look up Project Treble.

Re: Android now forces apps to include proprietary code for push notifications

#60

Post by throwayEngineer »

deogeo wrote: post #18

Perhaps it is time to treat Google as the enemy, because that is how it is treating us.

Google puts 1 restriction, they are the enemy.

Apple has created priopritary connectors, closed off systems, paid barriers to entry, and banning apps from their store.

Where is Apple and Microsoft on the scale from Friend to Enemy?

Post reply on HN