Skip to first unread message

Garry Deakin

unread,
Jan 1, 2016, 7:06:03 PM1/1/16
to Android-x86
Hi

I have installed android 6 onto my old Asus EEEPC that previously had Android 5 on, I continually get an error message when trying to set up that states Unfortunately, Google Play services has stopped.

I installed fine onto another laptop though using the same media.

Any ideas on this ?

Thanks

Gaz

Michał Ostrowski

unread,
Jan 3, 2016, 1:06:00 PM1/3/16
to Android-x86
Hi,
after you finish setup, you should get asked to grant all permissions to Google Play Services. After that the message should not appear.

Regards
Michał

Joshua Burton

unread,
Jan 3, 2016, 6:19:22 PM1/3/16
to Android-x86
Hmm,I'm having the same issue on my Dell Optiplex 755 but i'm not sure whats causing this error to always pop up... I try to bypass the "Checking Info" without connecting to Wifi and after i'm out of the setup screen when I try to open an app lets say "Google Play Store" or the default browser that came with it comes up with both "Unfortunately, Google Play services has stopped." and Unfortunately, Browser has stopped. It happens with almost all the apps pre-installed.

Derek Yu

unread,
Jan 3, 2016, 11:37:32 PM1/3/16
to Android-x86
I didn't get asked to grant permission to anything. Just in the middle of checking, Google Play Services stop and it rewind back to ask Wifi connection again.

Garry Deakin

unread,
Jan 4, 2016, 4:33:52 PM1/4/16
to Android-x86
I tried all these things too, skipping the wifi and going back.

I also tried to run from the installation CD instead of installing - same problem.

Worked ok on a different laptop though so maybe its a hardware issue ?

Chih-Wei Huang

unread,
Jan 4, 2016, 9:55:07 PM1/4/16
to Android-x86
2016-01-05 5:33 GMT+08:00 Garry Deakin <garry...@gmail.com>:
> I tried all these things too, skipping the wifi and going back.
>
> I also tried to run from the installation CD instead of installing - same
> problem.
>
> Worked ok on a different laptop though so maybe its a hardware issue ?

Yes, a known issue for devices without a supported GPU.

The bad news is OpenGL ES 2 seems a mandatory requirement
of the marshmallow prebuilt webview.apk which is used by
Google Play Service and many other apps.
That means you are almost unablt to use android 6.0
if your GPU is not supported.

Except trying to support more GPUs as we can,
I don't see other solution yet.

Jeff McJunkin

unread,
Jan 4, 2016, 9:58:25 PM1/4/16
to Android-x86
Derek --

I saw the same issue, but I was able to get past it by disconnecting from the network before skipping the wifi connections again.

Hope that helps!
- Jeff

Diazz72

unread,
Jan 4, 2016, 9:58:25 PM1/4/16
to Android-x86
OffTopic: What Asus EEEPC are u using?

Garry Deakin

unread,
Jan 5, 2016, 11:29:06 AM1/5/16
to Android-x86
I think its the 1005HA SeaShell - just trying to breathe life back into an older piece of kit that I dont want to dispose off its still useable :-)

Garry Deakin

unread,
Jan 5, 2016, 11:30:05 AM1/5/16
to Android-x86
Is there anyway to tell what GPU is in my netbook ?

Antony Stone

unread,
Jan 5, 2016, 11:57:07 AM1/5/16
to andro...@googlegroups.com
On Tuesday 05 January 2016 at 17:30:05, Garry Deakin wrote:

> Is there anyway to tell what GPU is in my netbook ?

Best bet is to boot from some Linux LiveCD (on a USB stick, probably) and use
the command "lspci".


Antony.

--
"640 kilobytes (of RAM) should be enough for anybody."

- Bill Gates

Please reply to the list;
please *don't* CC me.

Garry Deakin

unread,
Jan 5, 2016, 2:45:02 PM1/5/16
to Android-x86
is there a list of supported GPU ?

I am going to run GPU-Z and see what is in the machine !


On Tuesday, January 5, 2016 at 2:55:07 AM UTC, Chih-Wei Huang wrote:

Garry Deakin

unread,
Jan 5, 2016, 4:40:33 PM1/5/16
to Android-x86
OK according to GPU-Z the GPU is i945GME rev 3.  Is this GPU supported ?  If not, is there any plans to support it ?

Thanks

Gaz

Chih-Wei Huang

unread,
Jan 5, 2016, 9:02:29 PM1/5/16
to Android-x86
2016-01-06 5:40 GMT+08:00 Garry Deakin <garry...@gmail.com>:
> OK according to GPU-Z the GPU is i945GME rev 3. Is this GPU supported ? If
> not, is there any plans to support it ?

This one should be supported.

Please provide logcat for further analyzing.


--
Chih-Wei
Android-x86 project
http://www.android-x86.org

Jeff McJunkin

unread,
Jan 5, 2016, 10:13:50 PM1/5/16
to Android-x86
Hmm, apparently Android 4.0 and above requires OpenGL ES 2.0[1][2]. 

Is it not actually enforced by most applications until Marshmallow, or is there some software rendering support for OpenGL ES 2.0 in the earlier Android-x86 releases?

In other words, is there hope for Marshmallow Android-x86 in VMware / VirtualBox / Hyper-V?

[1] http://source.android.com/devices/graphics/index.html

Diazz72

unread,
Jan 5, 2016, 10:13:50 PM1/5/16
to Android-x86
Well you can add GTX 770 on not supported ( its boot, but acceleration is not working and its freez machine, you cant even change wallpaper LOL ).

Garry Deakin

unread,
Jan 6, 2016, 3:03:38 AM1/6/16
to Android-x86
Hi

Im happy to provide any support logs to try and resolve it, Android isnt that familiar to me yet though, can you give me some step by step instructions and I will happily post them when completed.

Thanks

Gaz

Chih-Wei Huang

unread,
Jan 6, 2016, 3:43:35 AM1/6/16
to Android-x86
2016-01-06 3:59 GMT+08:00 Jeff McJunkin <boredo...@gmail.com>:
> Hmm, apparently Android 4.0 and above requires OpenGL ES 2.0[1][2].
>
> Is it not actually enforced by most applications until Marshmallow, or is
> there some software rendering support for OpenGL ES 2.0 in the earlier
> Android-x86 releases?

The software renderer only support ES 1.x, not 2.0.
Not all apps requires ES 2.0, so we are still able to run
these apps on a software rendering only device.
But the webview.apk of marshmalow now enforces ES 2.0.
So any app (including Google Play Service) using it will just crash.

> In other words, is there hope for Marshmallow Android-x86 in VMware /
> VirtualBox / Hyper-V?

That depends what "hope" you meant.

In short term, we may need to find a way to workaround
the GLES2 requirement of webview.apk.
I'm not sure if it's possible now.

In long term, we still hope to enable GLES 2 support for VMs.
But that needs more experts to join.
Currently the Mesa porting for VMware does work but buggy.
Just need some experts to fix the remaining bugs
to make it usable.

marco milanese

unread,
Jan 6, 2016, 7:23:01 AM1/6/16
to Android-x86
Hi,

Logcat: https://gist.github.com/Mm7/12a684dfd323657eef93

device: eee pc 100he

Chih-Wei Huang

unread,
Jan 6, 2016, 7:34:12 AM1/6/16
to Android-x86
2016-01-06 17:39 GMT+08:00 marco milanese <marcomi...@gmail.com>:
> Hi,
>
> Logcat: https://gist.github.com/Mm7/12a684dfd323657eef93
>
> device: eee pc 100he

Thanks.
GLES libs loaded and work, fine.
However, the gms crashed in GpuThread.
No idea what's wrong yet.

--------- beginning of crash
01-06 10:12:41.860 3477 3868 F libc : Fatal signal 11 (SIGSEGV),
code 1, fault addr 0x0 in tid 3868 (GpuThread)
01-06 10:12:41.986 1443 1443 F DEBUG : *** *** *** *** *** *** ***
*** *** *** *** *** *** *** *** ***
01-06 10:12:41.986 1443 1443 F DEBUG : Build fingerprint:
'Android-x86/android_x86/x86:6.0/MDB08M/cwhuang11262219:userdebug/test-keys'
01-06 10:12:41.986 1443 1443 F DEBUG : Revision: '0'
01-06 10:12:41.986 1443 1443 F DEBUG : ABI: 'x86'
01-06 10:12:41.987 1443 1443 F DEBUG : pid: 3477, tid: 3868, name:
GpuThread >>> com.google.android.gms.ui <<<
01-06 10:12:41.987 1443 1443 F DEBUG : signal 11 (SIGSEGV), code 1
(SEGV_MAPERR), fault addr 0x0
01-06 10:12:42.129 1443 1443 F DEBUG : eax a48bfe40 ebx
a48a5ab8 ecx a47f8988 edx 98bff8d0
01-06 10:12:42.129 1443 1443 F DEBUG : esi 915abd10 edi a48bfdd8
01-06 10:12:42.129 1443 1443 F DEBUG : xcs 00000073 xds
0000007b xes 0000007b xfs 0000010f xss 0000007b
01-06 10:12:42.129 1443 1443 F DEBUG : eip 00000000 ebp
9477f4fc esp 9477f45c flags 00010286
01-06 10:12:42.129 1443 1443 F DEBUG :
01-06 10:12:42.129 1443 1443 F DEBUG : backtrace:
01-06 10:12:42.129 1443 1443 F DEBUG : #00 pc 00000000 <unknown>
01-06 10:12:42.130 1443 1443 F DEBUG : #01 pc 80000019 <unknown>
01-06 10:12:42.130 1443 1443 F DEBUG : #02 pc 2024548a <unknown>
01-06 10:12:42.919 1443 1443 F DEBUG :
01-06 10:12:42.919 1443 1443 F DEBUG : Tombstone written to:
/data/tombstones/tombstone_00
01-06 10:12:42.919 1443 1443 E DEBUG : AM write failed: Broken pipe
01-06 10:12:42.920 1780 1797 I BootReceiver: Copying
/data/tombstones/tombstone_00 to DropBox (SYSTEM_TOMBSTONE)
01-06 10:12:42.924 3477 3477 I Choreographer: Skipped 56 frames!
The application may be doing too much work on its main thread.
01-06 10:12:42.985 1780 1944 I WindowState: WIN DEATH:
Window{1bd83b2 u0
com.google.android.gms/com.google.android.gms.auth.uiflows.minutemaid.MinuteMaidActivity}
01-06 10:12:42.999 1780 2614 D GraphicsStats: Buffer count: 4
01-06 10:12:43.003 1440 1440 W SurfaceFlinger: couldn't log to
binary event log: overflow.
01-06 10:12:43.008 1449 1449 I Zygote : Process 3477 exited due to
signal (11)
01-06 10:12:43.011 1780 1988 I ActivityManager: Process
com.google.android.gms.ui (pid 3477) has died

池程

unread,
Jan 7, 2016, 8:31:28 PM1/7/16
to Android-x86
you should grant all permissions for Google Play Services, then it wont go wrong.

Garry Deakin於 2016年1月2日星期六 UTC+11上午11時06分03秒寫道:

Garry Deakin

unread,
Jan 8, 2016, 5:00:21 AM1/8/16
to Android-x86
OK - how do I do this then ?

Thanks

Gaz

Tim Kowalsky

unread,
Jan 8, 2016, 11:21:49 PM1/8/16
to Android-x86
I've been trying to add gapps, to Android-x86 Marshmallow, and ran into the same sorts of errors.

I found the following links, that refer to a problem with AOSP sourced ROMs, and permissions, needed, for gapps.  These may or may not help.

Discussion of the issue...

Possible patch?
Message has been deleted

spin877

unread,
Jan 11, 2016, 10:13:54 AM1/11/16
to Android-x86

I recompiled with the patch DefaultPermissionGrantPolicy.java now the situation is much improved.
Thank you for the tip.
P.S
I forgot. I came to put on android_x86 6.0.1 Supersu
BETA-SuperSU-v2.65-20151226141550.zip

just rename su.pie in su

Gökhan Çokşen

unread,
Jan 11, 2016, 10:11:32 PM1/11/16
to Android-x86
Yes, i experienced the same issue. But interestingly, it doesn't happen every time. Your chance is %50.
When i got the error, i tried to go back to first screen (Language selection). I selected the English. In 2nd trying i didn't get that error. I could use the Youtube, Google Play, Browser and other internet relating apps.
I don't know if it is work for everyone, but worked for me.

Garry Deakin

unread,
Jan 13, 2016, 8:35:02 AM1/13/16
to Android-x86
How do I edit the file ?

Can we put step by step instructions on there as I am not too familiar with Android, and apologies if the steps are already there and I have just missed them :-

Thanks

Gaz

Michael De Rubertis

unread,
Jan 26, 2016, 8:42:49 PM1/26/16
to Android-x86
Thank you this worked!
Reply all
Reply to author
Forward
0 new messages