My company is working on an in car device that is operating by Android Jelly Bean. I know android is open source but is there any reason fro me to believe I need Google's permission to install on such device the Google Play market?
Appreciate your responses.
Aaron
I don't think anyone has an answer to your question. You can try to read the open source details and license information on Google's open source.
Sent from my Nexus 4 using Tapatalk 2
You don't need permission to use it, just that it should comply with Google's CTS guidelines. Those are a series of hardware and software checks to determine that the device is suitable to run the Google Apps (which are closed source). I don't think there should be any problem if you use any of the Google Apps from the respective Gapps package (http://goo.im/gapps).
Sent from my Desire HD using xda premium
Google Play is NOT open source so it cannot legally be distributed with a device without Google's approval. Its not heavily enforced as I see many generic Android tablets and TV sticks shipping with Google Play, many of which probably haven't been approved.
From Android FAQ: http://source.android.com/faqs.html
If my device is compatible, does it automatically have access to Google Play and branding?
Google Play is a service operated by Google. Achieving compatibility is a prerequisite for obtaining access to the Google Play software and branding. Device manufacturers should contact Google to obtain access to Google Play.
If I am not a manufacturer, how can I get Google Play?
Google Play is only licensed to handset manufacturers shipping devices. For questions about specific cases, contact [email protected].
How can I get access to the Google apps for Android, such as Maps?
The Google apps for Android, such as YouTube, Google Maps and Navigation, Gmail, and so on are Google properties that are not part of Android, and are licensed separately. Contact [email protected] for inquiries related to those apps.
Is compatibility mandatory?
No. The Android Compatibility Program is optional. Since the Android source code is open, anyone can use it to build any kind of device. However, if a manufacturer wishes to use the Android name with their product, or wants access to Google Play, they must first demonstrate that the device is compatible.
How much does compatibility certification cost?
There is no cost to obtain Android compatibility for a device. The Compatibility Test Suite is open-source and available to anyone to use to test a device.
How long does compatibility take?
The process is automated. The Compatibility Test Suite generates a report that can be provided to Google to verify compatibility. Eventually we intend to provide self-service tools to upload these reports to a public database.
Who determines what will be part of the compatibility definition?
Since Google is responsible for the overall direction of Android as a platform and product, Google maintains the Compatibility Definition Document for each release. We draft the CDD for a new Android version in consultation with a number of OEMs, who provide input on its contents.
Click to expand...
Click to collapse
Android Pay stopped being officially supported/working on Android Wear (starting with the Oreo update) outside US/UK: https://www.androidpolice.com/2018/...ate-disables-android-pay-users-outside-us-uk/ and https://support.google.com/androidwear/thread/26579
I created small proof of concept app that streamlines launching/enabling of Android Pay so even with it disabled, it will only take up to two additional taps to pay with Android Pay:
Launch "Pay Enabler" (instead of Android Pay). If Android Pay is already enabled, Pay Enabler will just launch it directly.
Tap "Enable" (not needed since version 5, requires Accessibility service)
Tap "Open" (not needed since version 4)
Note 1: Google started geo blocking Google Pay on Wear OS H (Android Pie/9) so Pay Enabler doesn't work on newest firmwares. It still works on Oreo.
Note 2: When connected to iOS, Play Store requires standalone connectivity (WiFi or cellular data) for enabling as it doesn't use caches (unlike when paired with Android).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download
Play Store: https://play.google.com/store/apps/details?id=com.brouken.wear.payenabler
Source: https://github.com/moneytoo/PayEnabler
They added few more countries but there is still dozen more countries affected.
To use Google Pay on your watch, you need to: Be in the US, UK, Italy, Spain, Australia, Canada, Poland, Russia, or Germany.
Click to expand...
Click to collapse
https://support.google.com/pay/answer/7293863
Update 2018/11/19:
Uploaded Pay Enabler version 5 here to XDA (not on Play Store, yet). It uses Accessibility service to automate enabling of Google Pay, no more tapping "Enable". (Source is also available on Github.)
Requires manual enabling in "Settings -> Accessibility -> Pay Enabler".
Works only with English - texts "Google Pay" and "Enable". Post texts in your languages and I will include them (That shouldn't be necessary as of version 5d which supports two dozens of languages - at least for the "Enable" button).
Accessibility service is registered only for Play Store so it shouldn't cause basically any battery drain (as it doesn't poll anything)
Update 2018/11/29:
Version 5 submitted to the Play Store.
Update 2018/12/16:
Version 6 fixes detection of the enable button in some non English languages (cs, fi, hi, ko, th).
For me I have no issue yet, never got 8.0 and I do not want it.
I bought this watch for Android Pay and it has worked fine since May 2017.
Even though I hate Samsung for abandoning Android Wear, I maybe forced in time to try Samsung Pay; I know my Canadian Bank supports Samsung Pay.
Anybody have any clue why Android Pay on the Android Wear watch only works in the US, UK when other countries support it ?
AstroDigital said:
For me I have no issue yet, never got 8.0 and I do not want it.
I bought this watch for Android Pay and it has worked fine since May 2017.
Even though I hate Samsung for abandoning Android Wear, I maybe forced in time to try Samsung Pay; I know my Canadian Bank supports Samsung Pay.
Anybody have any clue why Android Pay on the Android Wear watch only works in the US, UK when other countries support it ?
Click to expand...
Click to collapse
This app is a good solution until Google finally fixes. Thank you!
Enviado desde mi SM-G930F mediante Tapatalk
No, no, thank YOU Mr Acavano.
Thanks for the fix!
moneytoo said:
Android Pay stopped being officially supported/working on Android Wear (starting with the Oreo update) outside US/UK: https://www.androidpolice.com/2018/...ate-disables-android-pay-users-outside-us-uk/ and https://support.google.com/androidwear/thread/26579
I didn't test it myself (yet, I'm still on Nougat) but based on user reports, Android Pay is only getting disabled (by Google Play services?). It is reported that payments are still working if it's manually enabled.
Based on this, I created small proof of concept app that streamlines launching/enabling of Android Pay so even with it disabled, it will only take two additional taps to pay with Android Pay:
Launch "Pay Enabler" (instead of Android Pay). If Android Pay is already enabled, Pay Enabler will just launch it directly.
Tap "Enable"
Tap "Open"
Version 1 vs Version 3
It was reported to me that Android Pay doesn't show up in Settings (list of installed apps) so since version 2 it uses Play Store for manual enabling. (I will try if I can open the app manually from background once enabled to save the second click to "Open").
Download
Play Store: https://play.google.com/store/apps/details?id=com.brouken.wear.payenabler
Source: https://github.com/moneytoo/PayEnabler
Click to expand...
Click to collapse
My friend, if you find a way to enable android pay on the wear24 i'll get a lot of money, you can sell a app to do this, there's a lot of people looking for it include me! The wear24 is very cheap on ebay, by without android pay is a little useless.
https://forum.xda-developers.com/android-wear/help/verizon-wear24-to-unlock-carrier-t3715300
Im in Australia, Google play store says my device is not compatible with this app.
Downloaded the version 1 and 3 apk, but upon installing it says there is a problem with parsing the package.
Help?
erwinsie said:
Im in Australia, Google play store says my device is not compatible with this app.
Downloaded the version 1 and 3 apk, but upon installing it says there is a problem with parsing the package.
Help?
Click to expand...
Click to collapse
The app is compatible only with Android Wear devices running Android Oreo. You must either select your watch when installing from web or search for Pay Enabler in Play Store directly on your watch. It's standalone app for Android Wear and nothing gets installed elsewhere.
moneytoo said:
The app is compatible only with Android Wear devices running Android Oreo. You must either select your watch when installing from web or search for Pay Enabler in Play Store directly on your watch. It's standalone app for Android Wear and nothing gets installed elsewhere.
Click to expand...
Click to collapse
Ah, ok. Got it. No worries it works. Than you very much from Australia.[COLOR="Silver"
Just to be clear, this will not work on nougat?
Because as mentioned before it would be great if this brought android pay to the wear24. Verizon's videos show the watch with the android pay app so its obviously a possibility.
Thanks
AstroDigital said:
For me I have no issue yet, never got 8.0 and I do not want it.
I bought this watch for Android Pay and it has worked fine since May 2017.
Even though I hate Samsung for abandoning Android Wear, I maybe forced in time to try Samsung Pay; I know my Canadian Bank supports Samsung Pay.
Anybody have any clue why Android Pay on the Android Wear watch only works in the US, UK when other countries support it ?
Click to expand...
Click to collapse
Thank you OP, it works! I wish Google would fix this or just re-enable.
And how does Samsung Pay on Gear (watch) devices work? I heard it doesn't unless you hack it hard.
transitnowapp said:
Thank you OP, it works! I wish Google would fix this or just re-enable.
And how does Samsung Pay on Gear (watch) devices work? I heard it doesn't unless you hack it hard.
Click to expand...
Click to collapse
Really do I need to spell it out ?
If I am forced to use a Gear I would need to dump "Google" Pay and use Samsung Pay.
But for now my watch has not been upgraded to Oreo works fine, I will never upgrade to Oreo as my first choice.
If I have to in time go to Oreo and have the same issue everybody outside of the UK, and US has I will do two things get annoyed at the arrogance of Google "hey we do not care if you been using Android Pay now Google Pay for months, we will stop you" then I will install the Pay Enabler.
The chances are I will never be forced to by a Gear, though new watches with NFC have not been released.
I'm using it since yesterday and it is so much helpful. Thank you so much!
They added 3 more countries but there are still 14 more countries affected.
To use Google Pay on your watch, you need to: Be in the US, UK, Spain, Australia, or Canada.
Click to expand...
Click to collapse
https://support.google.com/pay/answer/7293863?co=GENIE.Platform=Android&hl=en
Great news! Thanks
Enviado desde mi SM-G930F mediante Tapatalk
Is there any way to emulate being in the US from the watch? I get to the download page with the app, but can't download it as it "is not available in my country". Any way to bypass this?
Mart1neZ said:
Is there any way to emulate being in the US from the watch? I get to the download page with the app, but can't download it as it "is not available in my country". Any way to bypass this?
Click to expand...
Click to collapse
Had the same problem. A long time ago I had created a Google Account via US VPN. Now I added this as a second account on the watch and selected the account in the play store and it works.
I hope it still works like this.
It's not just Android Wear
Will your fix also work on "regular" Android 8.1 on a smartphone? I have the same issue with Google Pay on my Nexus 5x, as I now live in Hungary.
In my case, the "back-end" part of Google Pay continues to work, and I can make payments at contactless terminals using my installed credit or debit cards. But the "front-end" user interface part is disabled just as described here. If I need to change the payment card used for a transaction (or add or remove a card) it's a real pain in the ass to enable the app.
Ironically, the availability of contactless payment terminals in Hungary is excellent, while in the US they almost don't exist.
From the little research I've done on the internet, there are lots of people with Google Pay on smartphones facing the same issue, and so you might want to consider a version of your fix for the rest of us!
ikijibiki said:
Will your fix also work on "regular" Android 8.1 on a smartphone? I have the same issue with Google Pay on my Nexus 5x, as I now live in Hungary.
In my case, the "back-end" part of Google Pay continues to work, and I can make payments at contactless terminals using my installed credit or debit cards. But the "front-end" user interface part is disabled just as described here. If I need to change the payment card used for a transaction (or add or remove a card) it's a real pain in the ass to enable the app.
Ironically, the availability of contactless payment terminals in Hungary is excellent, while in the US they almost don't exist.
From the little research I've done on the internet, there are lots of people with Google Pay on smartphones facing the same issue, and so you might want to consider a version of your fix for the rest of us!
Click to expand...
Click to collapse
As Hungary is not a country supported by Google Pay, are you using your payment card that was issued by US bank? I'm curious to know what is Google Pay policy on using it abroad (as on vacation or expat) - I thought the bank requirement was only for setup/card linking. (I understand you're talking about frontend vs backend as all card data and emulation is done by Google Play services)
Anyway, you should be able to use the attached apk in the first post.
moneytoo said:
As Hungary is not a country supported by Google Pay, are you using your payment card that was issued by US bank? I'm curious to know what is Google Pay policy on using it abroad (as on vacation or expat) - I thought the bank requirement was only for setup/card linking. (I understand you're talking about frontend vs backend as all card data and emulation is done by Google Play services)
Anyway, you should be able to use the attached apk in the first post.
Click to expand...
Click to collapse
Yes, all my cards are from US banks. Although I now live abroad, all my banking/finance is still US-based. I've been using Android Pay and no Google Pay for about a year without any issues from either Google or my banks. My banks are fully aware of my situation and have been really great about shipping new credit and debit cards to Hungary.
There are rare occasions where the terminal has some issue with the phone emulation, but mostly using the phone is the fastest way to pay, as the fingerprint authentication to unlock the phone eliminates the need to enter any PIN. Interestingly, as all US chip cards are non-PIN and require a signature, when using the phone to pay, I also don't need to sign any slips. The two-factor authentication does all the work.
I'll download the apk and give it a try. Thanks!
---------- Post added at 08:18 PM ---------- Previous post was at 07:54 PM ----------
ikijibiki said:
I'll download the apk and give it a try. Thanks!
Click to expand...
Click to collapse
No joy. Payenabler-3.apk won't install on my phone.
ikijibiki said:
No joy. Payenabler-3.apk won't install on my phone.
Click to expand...
Click to collapse
My bad. It only works the other way (phone apps work on Wear). Please see the first post again for "-phone" version.
Hello,
I have two phones , one Cat S60 and today, reciewed my new Cat S61.
I have installed same apps that i have on my S60, but, the problem is, many modded app or other unnoficial app have problems with the new android system. On my S60, it working very well.
For exemple, i have and old version of Pocket Informant (i supposed is a "cracked" version but not sure) and a Modded version of Hogwarts Mystery. Both crash instantly when louching the app. Have black screen for few seconds and return to android desktop and have a texte say the app have crashed. If retry, same crash and android said (in french: "Harry Potter s'arrête systémathiquement") i think trad is "Always Crashing". I have no problems on the S60 is running on Android Mashmallow (if i'm correct). Other user have similar problems with custom app like me on his Android Oreo 8.1 or it's specific to the News Cat S61 and will be resolved by future update?
Thanks in advance for your answer and sorry for my bad spelling ^^'
Sounds like the applications are incompatible with the new android. Keep sending the reports to the developers and hopefully some day they release new versions for new Android. If you are rocking some "cracked" soft, then it might just be an old- non-updated version of the app. Search for these apps on google play and purchase them, if you enjoy them. That gives the developers some well deserved money and motivation to fix the issues.
Codeplayer said:
Sounds like the applications are incompatible with the new android. Keep sending the reports to the developers and hopefully some day they release new versions for new Android. If you are rocking some "cracked" soft, then it might just be an old- non-updated version of the app. Search for these apps on google play and purchase them, if you enjoy them. That gives the developers some well deserved money and motivation to fix the issues.
Click to expand...
Click to collapse
That i have maked for Pocket Informant. The reason i have a cracked version is i dont like the new interface of the calendar (and as need to pay for have all function, for gaving an old version of the app, needed to be a "cracked" because if isnt, even if you have paid the new version, the old (uncrackef) stay limited function. For harry potter (hogwards mystery) it just i whont paid anything ingame for advance in game or other. If the dev put this game on store and need to paid for have it and play "unlimited, i will pay for it, but... If you read how the game is working, it's just a scam for get maximum monney of people X). The mod make just infinite energy ingame and dont need to paid for advance in the game ^^.
So, it's not a Android "limitation" to make unable to have non official or modded apk . I will wait that get new version of my apps and see what happens.