Skip to content
This repository has been archived by the owner on Jun 20, 2023. It is now read-only.

App not Working on Huawei Devices #490

Closed
xpcone opened this issue Jun 16, 2020 · 29 comments
Closed

App not Working on Huawei Devices #490

xpcone opened this issue Jun 16, 2020 · 29 comments
Labels
bug Something isn't working wontfix This will not be worked on

Comments

@xpcone
Copy link

xpcone commented Jun 16, 2020

Despite #474 / #484 there is also to be noticed, that the App is not useable on devices with HMS.

All newer Huawei devices are banned from Goolge/PlayStore due to a presidential order. Without an apk or a upload to the Huawei store, there'll be approx. 1M Users not able to use this app.

@mat-l
Copy link

mat-l commented Jun 16, 2020

Same problem for me, although I have installed Google Play Services besides Huawei Mobile Service: #478 (comment)

@Nokius
Copy link

Nokius commented Jun 16, 2020

@Huawei implimented an own framework called HMS Core Contact Shield. This could be may implemented for users with Google Serivce baned Huawei devices.

@henning-schild
Copy link

In fact the app should be available as .apk in https://github.com/corona-warn-app/cwa-app-android/releases
That version should later be extended to update itself without the need for a store or google.

It could also be added to other stores like i.e. https://f-droid.org/. That is where true FOSS goes ... not "don't be evil"

@textvrbrln
Copy link

+1
Otherwise people will download your standalone APK from sources like https://apkpure.com/de/corona-warn-app/de.rki.coronawarnapp/download?from=details and you probably don't want that.

@henning-schild
Copy link

@SebastianWolf-SAP
Copy link
Member

The respective information, especially the issue corona-warn-app/cwa-documentation#5 has already been posted. We are closing this issue now...

Mit freundlichen Grüßen/Best regards,
SW
Corona Warn-App Open Source Team

@mat-l
Copy link

mat-l commented Jun 16, 2020

@SebastianWolf-SAP will there be an implementation of HMS services in your app? Currently it means all phones of Huawei are not supported at all. By closing this issue, all Huawei, Honor, and so on will be left out to participate in the app pogamme and therefore in taking care of our health.

@Nokius
Copy link

Nokius commented Jun 16, 2020

@mat-l As @SebastianWolf-SAP linked the decision is to use the API from Google and Apple.
As there is a stupid trade war between the OS creature country and the handset makers one. You are for now in pity as well as all other non iOS/Google Service Android users.
Welcome to the walled garden called monopoly!

@carlos22
Copy link

@Nokius yes and we the tax-payers of Germany payed about 20 Million Euros to SAP (and apparently Telekom) for this solution. So one could expect a solution that does not limit users for the stupid wars other countries and companies fight. But we are obligated to clap our hands that this stuff is open source.

@mat-l
Copy link

mat-l commented Jun 16, 2020

@SebastianWolf-SAP @Nokius yeah its the trade war, I commented as well over here: https://github.com/corona-warn-app/cwa-app-android/issues/510#issuecomment-644693694
In my opinion there must be support for HSM as well!

@corneliusroemer
Copy link

@SebastianWolf-SAP Stop closing issues with unrelated references.
A link to the documentation is not sufficient. Please update your FAQs and general public facing documents to mention which phones are not supported rather than deeplinking complicated documentation.

This issue was about Huawei, not F-Droid. In your link I can't find a Huawei mention.

@s-martin
Copy link

@Nokius yes and we the tax-payers of Germany payed about 20 Million Euros to SAP (and apparently Telekom) for this solution. So one could expect a solution that does not limit users for the stupid wars other countries and companies fight. But we are obligated to clap our hands that this stuff is open source.

Ok, how would you expect that SAP or German government would resolve the ongoing trade conflict between USA and China (Google and Huawei, respectively) for a tiny Corona warn app?

@mat-l
Copy link

mat-l commented Jun 16, 2020

@s-martin they can't stop it, but they should provide an solution that fits all, that means also to implement HMS Core services, which I wrote here: https://github.com/corona-warn-app/cwa-app-android/issues/510#issuecomment-644693694

@s-martin
Copy link

The Exposure Notification API is provided by Google via Play Services, so there's no workaround at this point.

@Nokius
Copy link

Nokius commented Jun 16, 2020

@carlos22 I agree with you it's tax payers money used here.
Personally I'm very happy to see that public money has turn into public code.
But 20 Million are not covering corner cases.
Like:

  • non smartphone users with feature phones
  • gray market devices with no Google Services
  • alternative OS/ROM's
  • Android devices with no Google Services
  • ...

As we both found out it's open source so you or anyone else can modify the code and open a PR. What about you @Huawei wanna get you users under the corona-warn-app umbrella?

@corneliusroemer
Copy link

corneliusroemer commented Jun 16, 2020

Huawei has a market share of 16% in Germany - that is quite significant. It's more than half of Apple's. So it can be considered worth it's own app - if the changes required aren't huge. Marginal costs per marginal benefit could be lower than for Apple with only 30% market share.
https://gs.statcounter.com/vendor-market-share/mobile/germany
@Nokius Good point mentioning @Huawei It's probably far too late though. But worth considering for the 16%.

@Nokius
Copy link

Nokius commented Jun 16, 2020

@corneliusroemer is it now 16% or 17%. Anyway I don't thinks all of them are without Google Service. If so it's still a user choose and not the fool of the app developer(s).

@corneliusroemer
Copy link

@Nokius Not sure how many devices are affected. But Huawei has significant market share. Same can be said about Apple, why doesn't everyone use Android. Sure Huawei doesn't offer the API, so that's Huawei's fault. Not sure if there's a workaround possible.

@jlnprssnr
Copy link

Huawei will offer an API as @Nokius mentioned above.

@henning-schild
Copy link

Did anyone bother telling google about the problem and maybe ask them to make that code available?
That would allow for a truly free implementation, which would suddenly also cover huawei devices and not just lineageOS and friends. Who knows, they might be willing to help out.

@carlos22
Copy link

carlos22 commented Jun 16, 2020

The Exposure Notification API is provided by Google via Play Services, so there's no workaround at this point.

Yes but that is the essential part. Which I would have expected to be implemented by this app. But software development today means you pay a lot of money for people making nice UIs and really using FAANG frameworks. Thats like giving up.

Some volunteers try to implement it: https://github.com/theScrabi/CoraLibre-android-sdk

@carlos22
Copy link

Did anyone bother telling google about the problem and maybe ask them to make that code available?
That would allow for a truly free implementation, which would suddenly also cover huawei devices and not just lineageOS and friends. Who knows, they might be willing to help out.

They sure will not. Google Play Services are essential to what keeps them having full control over Android. Very clever people at Google found this loophole to make sure everybody still likes Android because it is open source but still are able to make contracts with OEMs and ship code to every smartphone. They will never give you anything that is inside of Play Services.g that is inside of Play Services.

@corneliusroemer
Copy link

@SebastianWolf-SAP I think you should reopen this issue here - it's unrelated to F-Droid. It asks specifically for compatibility with a Huawei API that is TBA.

There should be special regards for Huawei while the issue is not resolve - if ever. Doesn't harm to have one issue that acts as a reminder that Huawei support is know to be limited.

@Nokius
Copy link

Nokius commented Jun 16, 2020

@corneliusroemer As I linked earlier today, currently the implementation is only for Apple and Android ( Google Service API). Here again the link to the developer mentioning it.

If you like to see support for an minority group of users, create fork, read the Huawei documentation, code, create a PR -> provide profit for the group of users. Looks like you are effected and you have the ability to solve it it's open source and you can make it happen.

@SebastianWolf-SAP SebastianWolf-SAP added the wontfix This will not be worked on label Jun 16, 2020
@Nokius
Copy link

Nokius commented Jun 16, 2020

@henning-schild come on google is aware of this 'issue' and they do it (from my point of view) on purposes. Google will never give up on users data as they are an ad company. So the google services are imported for them.

@SebastianWolf-SAP
Copy link
Member

Dear @corneliusroemer,

we have stated repeatedly, also in our FAQ and also in the official communication that only iOS and Android devices running Google Play Services are supported and we are not aware of additional plans. Moreover, there is currently no sign that the German Federal Government and/or the Robert Koch Institute will contract us to implement the app on other platforms.

We cannot state more clearly than what we've already done. And to be even more precise: We're the wrong contacts for such questions. Requests to implement the app on other platforms need to be ordered by the government or implemented by the community as @Nokius said.

So either somebody starts doing the work here (and announce that accordingly such as the folks in #75 for a free implementation of Google Play) or we will keep this issue closed with the label 'wontfix'.

Thank you for your understanding!

Mit freundlichen Grüßen/Best regards,
SW
Corona Warn-App Open Source Team

@henning-schild
Copy link

I personally also believe that google is aware and they are locking things down on purpose. But that does not rule out talking to them! Until somebody does that we are just working on assumptions here.

And with "somebody" i am thinking of SAP and Telekom with the COVID health mission, they might have some leverage. They should at least ask instead of refusing/ignoring true FOSS ... maybe based on the same assumptions that others already mentioned here.

To be honest i could not care less about the app ... i just see the leverage as a potential to open up android. That would be a good tax invest with or without the virus

@Nokius
Copy link

Nokius commented Jun 18, 2020

@henning-schild For sure the Federal Republic of Germany in person as RKI can try to contact Google so they may will debundle the Proximity Tracing API from the Google Services. BUT how Android will get the API then? To add it directly to the AOSP base or the deviates OEM/Manufacture create will take month/years or never happens as this will not push out Updates anytime soon.
Also the User who not install this OS Updates are may bigger then User who avoid Application Updates which in fact Google services are.

From my point of view Europe should wake up now and start an European driven mobile OS. So we [Europe / Federal Republic of Germany] could find solutions and not try to bargain with 'ruler'.

@henning-schild
Copy link

henning-schild commented Jun 19, 2020

@Nokius i would not say "Europe" because there is no reason to limit the scope of a liberation, maybe the pressure and funding could initially come from there.

The media seemed to focus more on availability on older devices, which just boils down to the same problem. Even if things will take a lot of time and this app will not get its fast solutions ... getting google to open up and loose control would be a step in the right direction. Maybe for the next pandemic or simply the next federal effort to release FOSS apps, which will hopefully happen after this one.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

10 participants