- Добавление Google Apps в эмулятор Android (Intel x86 Atom System Image)
- Google Play services has stopped #56
- Comments
- jazzl0ver commented Aug 29, 2019
- 4SiB commented Sep 16, 2019
- jazzl0ver commented Sep 17, 2019 •
- 4SiB commented Sep 17, 2019
- jazzl0ver commented Sep 17, 2019
- 4SiB commented Sep 18, 2019
- jazzl0ver commented Sep 18, 2019
- BananaLumps commented Sep 18, 2019
- 4SiB commented Sep 18, 2019 •
- jazzl0ver commented Sep 18, 2019
- 4SiB commented Sep 18, 2019
- jazzl0ver commented Sep 18, 2019
- 4SiB commented Sep 18, 2019
- BananaLumps commented Sep 18, 2019 •
- 4SiB commented Sep 18, 2019
- BananaLumps commented Sep 18, 2019
- jazzl0ver commented Sep 19, 2019
- 4SiB commented Sep 19, 2019 •
- jazzl0ver commented Sep 19, 2019
- 4SiB commented Sep 19, 2019 •
- jazzl0ver commented Sep 19, 2019
- 4SiB commented Sep 19, 2019 •
- Android x86 google play services
Добавление Google Apps в эмулятор Android (Intel x86 Atom System Image)
Все разработчики под Android знают, насколько медленно работает эмулятор. В июне прошлого года Intel представила Android, который работает в режиме x86 (без эмуляции ARM). И конечно, скорость эмулятора стала потрясающая. Но в системных образах этих эмуляторов отсутствуют Google Apps (Maps, GMail, Calendar, Google Play, аккаунт Google, . ).
В этой статье мы добавим приложения от Google.
Необходимо установить Intel Hardware Accelerated Execution Manager.
Скачиваем Google Apps (версия CM 10.1)
Также, через Android SDK необходимо скачать Intel x86 Atom System Image для Android 4.2.2 (API 17).
Создаём эмулятор:
Запускаем эмулятор из консоли с увеличенным системным разделом:
Заходим в папку, где архив с Google Apps, и запускаем скрипт (скрипт на bash):
Далее перезапускаем эмулятор в обычном режиме. Теперь у нас система с полным комплектом Google Apps!
Если будет появляться сообщение, что сбой в клавиатуре, то можно установить любую другую.
Полученный образ можно сохранить и использовать при создании новых эмуляторов на Android 4.2 (просто копировать его в папку avd соответствующего эмулятора). По этому же принципу можно сделать и под другие версии.
Успехов в разработке!
Update:
Как подсказывает Cancel можно не заморачиваться с yaffs2. Пока работает эмулятор, файл с образом системного раздела можно скопировать из /tmp/android-…
Источник
Google Play services has stopped #56
Comments
jazzl0ver commented Aug 29, 2019
Hi. Just installed the android-x86-8.1-r2.iso into VirtualBox and got this error while trying to sign in:
Is that an expected behavior? (Network is working well)
The text was updated successfully, but these errors were encountered:
4SiB commented Sep 16, 2019
Poweroff. Poweron and wait, wait, wait until he update itself. This is only way. I wait
5h and works!. When the fist upgrade are done then the «Play Store» works perfect.
jazzl0ver commented Sep 17, 2019 •
Thanks for your reply! It’s just installed several updates (including Google Play services), but still doesn’t want to work. I gonna wait for another several hours (just in case) but I don’t see any disk/net activity anymore.
What I found is that Google states Google apps won’t work on non-certified devices. Obviously, my VM is not certified 🙂
Can you please check and tell me what version and certification status you see in Google Play settings and confirm that you’re able to sign in?
4SiB commented Sep 17, 2019
In my scenario I create a PIN before creating VPN. After reboot I see that before my logon the store start update himself. Before logon of any user. Maybe this way is faster.
But, Play Store after his first update himself start working properly giving me access to any app, my account and works normal.
jazzl0ver commented Sep 17, 2019
I’m sorry, I didn’t get that. What PIN and VPN did you create and where?
PS Just checked (after 6 hours) — Google Play still doesn’t allow to log me in. Any chances you could check the Play Store settings for the version and certified status I asked about previously?
4SiB commented Sep 18, 2019
@jazzl0ver Settings > Security & Location > Screen lock > PIN
or Settings > Search: Unlock selection
After enter PIN and reboot I always see some automatic updates and I think before user is logon this store works better for himself
jazzl0ver commented Sep 18, 2019
I’ve set up PIN, stopped the VM and started it back. Made sure everything is up to date. But still can’t sign into Google Play services 🙁
BananaLumps commented Sep 18, 2019
I too am having this same issue
4SiB commented Sep 18, 2019 •
Hmm, I reinstall again to check this and try reproduce your problem.
I install Android x86 at VM without internet. Play Store is v10.5.10
Create a PIN:1234 with all notification at lock page.
Connect the wifi: VirtWifi and reboot from HardDrive and wait until Play Store is updated to any newer version, 5m max. Some times I login and run PlayStore and just do reboot and still wait for update or any new information from OS, 5min max.
By the way of waiting I create a new gmail test account — tree time.
BTW, Swipe up to unlook is possible by pressing on your physical keayboard the «right mouse menu key».
At ones of reboot I see new notification about
«To finish your VirtualBox installation».
I logon and start a wizzart, skiping all settings, imports etc.
On Desktop I see that Google Play has «dot» who is information about new updated.
Clicking to Play Store I see that Google Play is start automatic update
After it finish press a «. «>Updates and update «Google» engine or «Update All»
I poweroff and create a snapshot «Installed Updated». From this time I can connect to my Google
test and final account’s and they works properly — Google Chrome updates me a Bookmark and this is ok.
I hope any of this information help you in some point. General way is update all first and at the end start do settings/imports etc.
jazzl0ver commented Sep 18, 2019
I’ve reinstalled it following your instructions and still getting the error. Can we compare the setup?
I’m using VB 5.2.22. android.vbox is
4SiB commented Sep 18, 2019
- Why you upload me a virtual machine configuration when you haven’t problem with installation but with software inside a vm ? Play Store is work or not it’s not problem of Virtual Machine itself.
- Please google and discover a pastbin.com to share a «multi-line» stuff instead creating very long posts.
- I have v6.x and my file can be differ structure, I not understand why this file can help you.
My Config: https://pastebin.com/y5hME9Vc
Please use a text-compare.com to compare both version. This is a good tip.
I think that Android x86 must have finish this «Complete the VirtualBox configuration» wizzard as finished to PlayStore check the updates.
jazzl0ver commented Sep 18, 2019
1 — in general you’re right. but sometimes wrong mem or other settings might affect the inner guest
2 — i indeed had to use pastebin. apologies.
3 — thanks for your config. i made several tweaks but that didn’t help.
i don’t really know what to do else. @BananaLumps, have you had a chance to test 4SiB’s suggestions?
4SiB commented Sep 18, 2019
Maybe you must upgrade the VirtualBox to 6.x because he have got a other «virtual hardware» who is certification by Google Play Store.
When you have a Play Store >v10 and you have because you show this:
and I think this is a key to «Sign IN».
BananaLumps commented Sep 18, 2019 •
Haven’t managed to fix it yet but after a bit of testing it seems it may be a network issue. I tried a few proxy’s which did keep the app from crashing but i could not sign in. I’m going to try a VPN now and hopefully that will work. I don’t think the VM host has much to do with it apart from networking seems off. I’m running it in proxmox.
UPDATE 40 Minutes later:
Unable to get any VPNs to connect which leads me more into the network issue theory. Will keep going at it and update with any success.
4SiB commented Sep 18, 2019
In my case at VirtualBox v6.x with Android x86 v8.1 I have this one in Play Store > Settings > About section:
Then I have got not certified device but I have connected to @gmail.com account and I can search and install any software.
If @jazzl0ver you want to check this remotly then we can check this via TeamViewer — contact to me I publish at my github page.
BananaLumps commented Sep 18, 2019
@4SiB I know this is a big ask so i hope you have fiber =D Any chance you could upload a working vhd for me?
jazzl0ver commented Sep 19, 2019
@4SiB, thanks for your readiness to check things over teamviewer. Just to avoid wasting your time — I’m connecting to @BananaLumps ask — would you please export and share your VM? If that won’t help — we’ll try teamviewer option.
4SiB commented Sep 19, 2019 •
No problem. I am network administrator . I works only in remote access (from home) without fiber(FTTH).
After restore snapshot to «Installed» I receive this wizzard by pressing «finish setup» and the PlayStore start update by himself the same time.
I Finish this wizzard.
Disable the PIN to none.
Update all components in Play Store without «Sign in».
Do some reboots and check if any new notification but it’s clear and ready updated OS.
Forget wifi ssid: VirtWifi.
Power off vm.
Disable in VB network and audio.
VB not have possibility to do other export’s.
You must find way to import «Open Virtualization Format 2.0» into your Virtualization host (HyperVisor) like Proxmox, Hyper-V, KVM, ESX etc.
I can do a backup by external software like CloneZilla etc. but I think you should can import this OVF.
I import it and check. All works properly and my Google account works with SIGN IN button.
You must enable your audio and network device.
jazzl0ver commented Sep 19, 2019
I’ve sent a request from alex. gmail.com — please permit.
4SiB commented Sep 19, 2019 •
Sorry, I change the permission now. anyone can download this file. Please check again.
Edit: check again from other place and works. I hope this OVF2.0 is possible to import for you.
jazzl0ver commented Sep 19, 2019
Thanks, @4SiB ! Your VM does work! I’ve compared the settings and set up hardware of my VM in the same way — still no luck. Would you like me to export my VM into ovf and share with you? That’s probably easier than teamviewer stuff.
One more question — did you install on MBR or GPT?
4SiB commented Sep 19, 2019 •
Would you like me to export my VM into ovf and share with you?
ok. You should not ask but create it and share.
That’s probably easier than teamviewer stuff.
My experience give me thinking that TeamViewer is better.
- write at few communicators described in my github profile (contact repo), even with audio.
- Do snapshots and try differ stuff.
- I know a WireShark as network person. We can check this as a network problem or not.
- I can create a own vpn via EMEA\PL\RO\GB.. with QoS/Firewall/Google_AS limitation to check the stuff via vpn from Android x86.
- @BananaLumps try with proxy but VPN is better and if this will be solution then we know that is a your country&internet&google restriction.
- final solution we can publish here and mark them as Solution without creating many, many necessery post like this one.
- we not loose time
did you install on MBR or GPT?
I don’t know. I install it using automatic installation:
We must check this.
In your terminology it’s a «MBR». GParted give this info MS-DOS:
because MBR is not type of partition but place where is inserted MS-DOS or GPT structure.
For me I have problems with installation that Android x86 and few google times resolve them.
This OS is so slow by not using VirtualBox guest addon then I use it only to read Manga from Chrome/Bookmark and I thinking about other Emulator of Android to use more optimal OS.
But why you cannot sign in into account on updated Play Store — this is strange.
Источник
Android x86 google play services
Android OS на x86
В этой теме обсуждаются вопросы общие для всех Андроидов на платформе x86, конкретно проект портирования Android-х86, а также его братья, не имеющие отдельных тем обсуждения на нашем форуме.
Android в виртуальную машину | Сайт и Форум проекта Android-х86 | Android от Intel
Вопросы, касающиеся только проектов Phoenix OS , Remix OS x86 и Bliss-x86 , обсуждаются в своих темах.
За работоспособность ваших устройств ответственность несёте исключительно Вы. Задавая вопрос, постарайтесь указать следующую информацию .
- Hardware List — список совместимого оборудования
- Графическое ускорение нормально работает на видеоадаптерах от AMD и Intel (кроме GMA 500, GMA 600, GMA 3600, GMA 3650, т.к. они основаны на PowerVR).
Графика nVidia поддерживается начиная с Android-x86 4.4-R3; новое поколение начинает поддерживаться после выхода следующего. - Ситуация с поддержкой планшетов, Критическое замечание о звуке.
- Чипы, которые реализуют одновременно и WiFi, и Bluetooth работают хуже, чем отдельные.
- Если Вы не нашли в шапке или в листе совместимости версию для вашего компьютера/ноутбука (модификации железа), то следует попробовать разные версии и опытным путём подобрать оптимальную.
- Загрузочную флешку или диск необходимо записать с помощью Rufus, UNetbootin, LiLi, или WinImage. UltraISO использовать не рекомендуется потому, что созданные им флешки мало где грузятся.
Раздел под Android рекомендуется форматировать в ext3 или ext4 (для версии 5.0 Lollipop и новее) чтобы иметь >4ГБ места под свои нужды и избежать проблем с SuperSU и другим софтом. Форматирование раздела лучше произвести до установки Android сторонним ПО (Acronis, GParted, др.): родной установщик не всегда справляется с этой задачей.
title Android-x86 5.1-rc1
kernel /android-5.1-rc1/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 SRC=/android-5.1-rc1
initrd /android-5.1-rc1/initrd.img
title Android-x86 5.1-rc1 (Debug mode)
kernel /android-5.1-rc1/kernel root=/dev/ram0 androidboot.hardware=android_x86 DEBUG=2 SRC=/android-5.1-rc1
initrd /android-5.1-rc1/initrd.img
title Android-x86 5.1-rc1 (Debug nomodeset)
kernel /android-5.1-rc1/kernel nomodeset root=/dev/ram0 androidboot.hardware=android_x86 DEBUG=2 SRC=/android-5.1-rc1
initrd /android-5.1-rc1/initrd.img
title Windows
rootnoverify (hd0,1)
chainloader +1
Тут default указывает номер пункта, котоый будет выбран автоматически после истечения timeout секунд. root и rootnoverify указывают с какого диска, и с какого его раздела загружать выбраную операционную систему. Как и в случае с default, нумерация начинается с нуля. Параметры загрузки прописываются в конец строки, которая начинается со слова kernel. Такими параметрами можно повлиять на многие аспекты работы Андроида с железом. К примеру настроить работу с внешним монитором.
GRUB 2 — следующая версия GRUB. Разработчики писали GRUB 2 «с нуля», чтобы добиться переносимости и модульности.
Используется в образах Android-x86 для компьютеров с новым UEFI-BIOS.
Может хранить свои настроки в файле grub.cfg либо menu.lst. Обычно этот файл лежит на отдельном системном разделе EFI (ESP). Типичное содержимое:
set timeout=60
set gfxmode=1024×768
terminal_output gfxterm
Источник