Using Android-x86 along with Square as a POS system
222 views
Skip to first unread message
PingMetal
Jun 1, 2019, 4:16:06 PM6/1/19
to Android-x86
This idea could be interesting and many could benefit from it. I don't know if you know the Square payment system, but it's not compatible with PCs, only Android phones, iPads and iPhones, so I thought of installing Android-x86 to make a POS system using a computer. The installation of the Square app from the Play Store worked and bluetooth seems to work fine. It detects my Square card reader (device) when I open the Square app and it tries to pair with it. The only problem is the app doesn't allow me to use the reader on Android x86 as it detects the Android system is on developer mode (for whatever reason, probably security ones). Is there a way to fix that? The system doesn't seem on developer mode, but there's probably something that makes it seem like it is. Is there a command line to change that? I would love to be able to use my PC for transactions!
Thank you!
Chih-Wei Huang
Jun 2, 2019, 4:31:29 AM6/2/19
to Android-x86
PingMetal <samuel.c...@gmail.com> 於 2019年6月2日 週日 上午4:16寫道：
If app needs a user build image, you may need
to build it yourself.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
>
> This idea could be interesting and many could benefit from it. I don't know if you know the Square payment system, but it's not compatible with PCs, only Android phones, iPads and iPhones, so I thought of installing Android-x86 to make a POS system using a computer. The installation of the Square app from the Play Store worked and bluetooth seems to work fine. It detects my Square card reader (device) when I open the Square app and it tries to pair with it. The only problem is the app doesn't allow me to use the reader on Android x86 as it detects the Android system is on developer mode (for whatever reason, probably security ones). Is there a way to fix that? The system doesn't seem on developer mode, but there's probably something that makes it seem like it is. Is there a command line to change that? I would love to be able to use my PC for transactions!
The image we released is a userdebug build.
> This idea could be interesting and many could benefit from it. I don't know if you know the Square payment system, but it's not compatible with PCs, only Android phones, iPads and iPhones, so I thought of installing Android-x86 to make a POS system using a computer. The installation of the Square app from the Play Store worked and bluetooth seems to work fine. It detects my Square card reader (device) when I open the Square app and it tries to pair with it. The only problem is the app doesn't allow me to use the reader on Android x86 as it detects the Android system is on developer mode (for whatever reason, probably security ones). Is there a way to fix that? The system doesn't seem on developer mode, but there's probably something that makes it seem like it is. Is there a command line to change that? I would love to be able to use my PC for transactions!
If app needs a user build image, you may need
to build it yourself.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
DDS Central
Jun 2, 2019, 7:13:15 AM6/2/19
to Android-x86
You will need to make your own signed release build.
Some apps, especially those used for sensitive things like banking and personal identification will refuse to run on anything other than a release build. And make sure you remove root as well.
On Sat, Jun 1, 2019, 23:16 PingMetal <samuel.c...@gmail.com> wrote:
This idea could be interesting and many could benefit from it. I don't know if you know the Square payment system, but it's not compatible with PCs, only Android phones, iPads and iPhones, so I thought of installing Android-x86 to make a POS system using a computer. The installation of the Square app from the Play Store worked and bluetooth seems to work fine. It detects my Square card reader (device) when I open the Square app and it tries to pair with it. The only problem is the app doesn't allow me to use the reader on Android x86 as it detects the Android system is on developer mode (for whatever reason, probably security ones). Is there a way to fix that? The system doesn't seem on developer mode, but there's probably something that makes it seem like it is. Is there a command line to change that? I would love to be able to use my PC for transactions!Thank you!
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/61526ac3-0401-449d-96da-1ae090145754%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
PingMetal
Jun 3, 2019, 1:28:30 PM6/3/19
to Android-x86
I see. I guess getting it signed is quite something, isn't it?
On Sunday, 2 June 2019 07:13:15 UTC-4, DDS Central wrote:
You will need to make your own signed release build.Some apps, especially those used for sensitive things like banking and personal identification will refuse to run on anything other than a release build. And make sure you remove root as well.
On Sat, Jun 1, 2019, 23:16 PingMetal <samuel.c...@gmail.com> wrote:
--This idea could be interesting and many could benefit from it. I don't know if you know the Square payment system, but it's not compatible with PCs, only Android phones, iPads and iPhones, so I thought of installing Android-x86 to make a POS system using a computer. The installation of the Square app from the Play Store worked and bluetooth seems to work fine. It detects my Square card reader (device) when I open the Square app and it tries to pair with it. The only problem is the app doesn't allow me to use the reader on Android x86 as it detects the Android system is on developer mode (for whatever reason, probably security ones). Is there a way to fix that? The system doesn't seem on developer mode, but there's probably something that makes it seem like it is. Is there a command line to change that? I would love to be able to use my PC for transactions!Thank you!
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to andro...@googlegroups.com.
Mauro Rossi
Jun 4, 2019, 4:19:03 AM6/4/19
to Android-x86
On Sunday, June 2, 2019 at 1:13:15 PM UTC+2, DDS Central wrote:
You will need to make your own signed release build.Some apps, especially those used for sensitive things like banking and personal identification will refuse to run on anything other than a release build. And make sure you remove root as well.
Does signing of release builds just requires private keys to be generated and used to build image?
Or does it involve require to pass Android CTS certification to received release keys?
Thanks
On Sat, Jun 1, 2019, 23:16 PingMetal <samuel.c...@gmail.com> wrote:
--This idea could be interesting and many could benefit from it. I don't know if you know the Square payment system, but it's not compatible with PCs, only Android phones, iPads and iPhones, so I thought of installing Android-x86 to make a POS system using a computer. The installation of the Square app from the Play Store worked and bluetooth seems to work fine. It detects my Square card reader (device) when I open the Square app and it tries to pair with it. The only problem is the app doesn't allow me to use the reader on Android x86 as it detects the Android system is on developer mode (for whatever reason, probably security ones). Is there a way to fix that? The system doesn't seem on developer mode, but there's probably something that makes it seem like it is. Is there a command line to change that? I would love to be able to use my PC for transactions!Thank you!
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to andro...@googlegroups.com.
Mauro Rossi
Jun 4, 2019, 4:40:24 AM6/4/19
to Android-x86
On Tuesday, June 4, 2019 at 10:19:03 AM UTC+2, Mauro Rossi wrote:
On Sunday, June 2, 2019 at 1:13:15 PM UTC+2, DDS Central wrote:You will need to make your own signed release build.Some apps, especially those used for sensitive things like banking and personal identification will refuse to run on anything other than a release build. And make sure you remove root as well.Does signing of release builds just requires private keys to be generated and used to build image?Or does it involve require to pass Android CTS certification to received release keys?
Grammar rephrase, sorry, I meant if passing Android CTS certification officially is mandatory to be able to use release keys?
Mauro
Povilas Staniulis
Jun 4, 2019, 2:45:27 PM6/4/19
to andro...@googlegroups.com
Not sure, but that article does not mention any certifications. So I do
think you can roll your own release-keys.
It's just that some apps do use the build tag as a way to detect custom
ROMs and rooted devices. And most custom ROMs do use test-keys.
> <https://groups.google.com/group/android-x86>.
> <mailto:android-x86...@googlegroups.com>.
> <https://groups.google.com/d/msgid/android-x86/f3c9fecd-ed29-46bb-8f3a-6cbfc6ad2999%40googlegroups.com?utm_medium=email&utm_source=footer>.
think you can roll your own release-keys.
It's just that some apps do use the build tag as a way to detect custom
ROMs and rooted devices. And most custom ROMs do use test-keys.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-x86/61526ac3-0401-449d-96da-1ae090145754%40googlegroups.com
> <https://groups.google.com/d/msgid/android-x86/61526ac3-0401-449d-96da-1ae090145754%40googlegroups.com?utm_medium=email&utm_source=footer>.
> https://groups.google.com/d/msgid/android-x86/61526ac3-0401-449d-96da-1ae090145754%40googlegroups.com
> For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android-x86" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to android-x86...@googlegroups.com
> --
> You received this message because you are subscribed to the Google
> Groups "Android-x86" group.
> To unsubscribe from this group and stop receiving emails from it, send
> <mailto:android-x86...@googlegroups.com>.
> To post to this group, send email to andro...@googlegroups.com
> <mailto:andro...@googlegroups.com>.
> Visit this group at https://groups.google.com/group/android-x86.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-x86/f3c9fecd-ed29-46bb-8f3a-6cbfc6ad2999%40googlegroups.com
> To view this discussion on the web visit
> <https://groups.google.com/d/msgid/android-x86/f3c9fecd-ed29-46bb-8f3a-6cbfc6ad2999%40googlegroups.com?utm_medium=email&utm_source=footer>.
Chih-Wei Huang
Jun 4, 2019, 11:30:27 PM6/4/19
to Android-x86
Mauro Rossi <issor...@gmail.com> 於 2019年6月4日 週二 下午4:40寫道：
in any possible way.
Actually the sequence is, make a user build image
and sign it with release keys.
Run CTS (and other Google required tests) on the image
and generated reports.
Send the image and reports to Google contact window
for approval. Once it's approved, the image could be shipped.
Or if it's rejected, fixed the issues and re-run the cycle.
That's what we usually did when I worked in
Android BSP team before.
> On Tuesday, June 4, 2019 at 10:19:03 AM UTC+2, Mauro Rossi wrote:
>>
>> Does signing of release builds just requires private keys to be generated and used to build image?
>> https://source.android.com/devices/tech/ota/sign_builds
>>
>> Or does it involve require to pass Android CTS certification to received release keys?
>
> Grammar rephrase, sorry, I meant if passing Android CTS certification officially is mandatory to be able to use release keys?
No. A release keys are just keys generated
>>
>> Does signing of release builds just requires private keys to be generated and used to build image?
>> https://source.android.com/devices/tech/ota/sign_builds
>>
>> Or does it involve require to pass Android CTS certification to received release keys?
>
> Grammar rephrase, sorry, I meant if passing Android CTS certification officially is mandatory to be able to use release keys?
in any possible way.
Actually the sequence is, make a user build image
and sign it with release keys.
Run CTS (and other Google required tests) on the image
and generated reports.
Send the image and reports to Google contact window
for approval. Once it's approved, the image could be shipped.
Or if it's rejected, fixed the issues and re-run the cycle.
That's what we usually did when I worked in
Android BSP team before.
Reply all
Reply to author
Forward
0 new messages