32

I have created an Emulator using android 7.1.1 (API 25) CPU X86. When I start the emulator its showing pixel launcher keeps stopping issue. I have checked with CPU x86_64 also but same issue.

Here is the screenshot:

enter image description here

Here is my details config:

enter image description here

0xAliHn
  • 18,390
  • 23
  • 91
  • 111

7 Answers7

15

Selecting emulated performance --> graphics:Software-GLES 2.0 option in AVD setting.Solves my problem.

enter image description here

Pravin Londhe
  • 865
  • 7
  • 14
  • 3
    but now the emulator runs slower – CodeToLife Jun 09 '17 at 18:14
  • @CodeToLife what is your machine configuration? if you are using windows platform install HAXM and if you are using ubuntu install KVM. – Pravin Londhe Jun 12 '17 at 04:47
  • yes , installed. and the machine is uptodate seems, with 1150 socket MB, gt630, but with hardware option in that red framed dropdown it runs much faster than with usb device. – CodeToLife Jun 12 '17 at 18:12
11

EDIT

It seems like the issue is solved in Android Studio 2.2.3. If for some reason you still see this problem, the solution below works.

Original answer

I found a reasonable solution for now. The problem is mainly in the launcher, not the emulator itself. So installing a different launcher can fix the issue. I installed the GO launcher from here: http://www.appsapk.com/go-launcher-ex/

Just drag and drop the apk on the emulator and install it, then tell the OS to use it as default.

I am not sure if this specific apk is a legal copy of the apk, but anyway it solves the issue for me and there are many launchers out there

good luck.

amitfr
  • 1,033
  • 1
  • 9
  • 29
  • I can agree, surprisingly it started to work like a charm! – Bálint Pap Jan 13 '17 at 23:05
  • 3
    I would suggest one without internet permission – CodeToLife Jun 09 '17 at 18:20
  • I can't see that Android studio 2.3.3 solved the issue? I have a Mac mini 2012 With Intel HD Graphics 4000 (running Win10 (and OSX)) and then I have a component built PC Intel motherboard with Intel HD Graphics 3000, same thing. I still have this issue with everything but the stock Nexus play store units. The TV and Wear units works with the SW graphics acceleration fix below. The other Phone and Tablet units are unusable slow including both x86 and ARM. Looks like the units need update (because in previous versions of AS they worked so fine). Intel has no update Win10 driver, not an issue. – Jan Bergström Sep 07 '17 at 01:29
  • Interesting is that the stock Nexus play store units looks to learn, do not go into this indefinite loop of errors?? So they are usable after clicking away the errors. Also interesting is that I blank installed AS 2.3.3 on my Intel board PC and there are fuzz, but I upgraded my Mac Mini from AS 2.2.3 and the the emulator units from 2.2.3 works fine?? However I get the same "Your GPU driver information"-message asking to look for new Graphics board Win10 drivers. MS latest is from 2015 and and Intel's is elder. In short no new drivers, and that is no path, MS will not do anything about it? – Jan Bergström Sep 07 '17 at 02:20
  • Also interesting is that the old HAXM-issue where Win Hyper-V (must be disabled) is getting back, due to Win10 upgrades that puts it back. The AS people have been very keen on getting a smooth switch off, but it don't look to work from the AS, Hyper-V is still on. But it is off doing it manually but in Win10 culture the control panel, programs and functions Windows functions setting is easiest way of switching it off. True old fuzz and hazzel coming back on you. So a reminder always helps. – Jan Bergström Sep 07 '17 at 02:30
  • 5/2018 and this problem wasn't solved. C'mon Google! – Pedro Paulo Amorim May 01 '18 at 11:25
10

clearing launcher app data may help

adb shell pm clear com.google.android.apps.nexuslauncher
lil
  • 101
  • 3
  • This only works partially for me. The launcher no longer crashes by itself, but it does crash every time the app is launched. Uninstalling and reinstalling the app does not help. – PointedEars Feb 13 '18 at 01:52
  • @PointedEars - that is expected, since you haven't fixed the underlying problem, which is that your app crashes the emulator. – ToolmakerSteve Jun 05 '18 at 21:03
6

I was able to fix this by turning off "App suggestions" in the Pixel Launcher Settings. You can open the settings panel with this command:

adb shell am start com.google.android.apps.nexuslauncher/.SettingsActivity
weiyin
  • 6,819
  • 4
  • 47
  • 58
  • this command only works untill I updatd system image. Comming here again as it resolved the problem last time :). Also the only you should add to the answer above: " On the emulator in opened settings window of that launcher disable all check boxes". – CodeToLife Mar 01 '18 at 14:07
0

Some good suggestions above but I found out that it was crashing for me because the HAXM RAM specified was more than the AVD RAM.

I started getting the pixel launcher crash after I updated to the latest emulator version (26.1.2) and to the latest HAXM version (6.0.6). By default the HAXM RAM was set to 2GB and the RAM allocated to my virtual device was 1536MB. After I updated the HAXM RAM to 1GB I stopped getting the pixel launcher crashes.

To update the HAXM RAM you will need to run the HAXM installer again. Refer to this link HAXM configuration in android studio

Randeep
  • 403
  • 1
  • 4
  • 11
  • I could not find the HAXM installer in my GNU+Linux Android SDK. But this might be a general “out of resources” issue: It started occurring for me when I only allocated one of my CPU cores to the emulator under “Show Advanced Settings” (since I wanted one idle for distributed computing), but left “Multi-Core CPU” checked. Switching the setting back to the default 2 cores made the problem disappear. Emulating a Pixel phone with Android Oreo, SDK 27 with Google API). – PointedEars Feb 13 '18 at 02:28
  • The RAM values in answer seem backwards. Should be HAXM RAM >= virtual device RAM, right? Otherwise, you won't be running in high-speed mode. [So if you really do mean the numbers you say here, then you were having a problem running virtualized mode, and your "fix" worked by forcing emulator to run in the slower, but more reliable, emulated mode. Lessening your HAXM memory below AVD RAM was an indirect way to force that.] – ToolmakerSteve Jun 05 '18 at 20:57
0

it worked for me to simply clean the project

Tobe
  • 508
  • 5
  • 14
0

After one day of troubleshooting this issue, I just deleted the emulator and created another one with a different name. Now it working but still very slow. maybe I have to upgrade my laptop.

Tarek Salah
  • 170
  • 3
  • 16
  • An alternative to deleting an emulator is to launch emulator manager and use it to "Start" the desired emulator. On "Start" screen, check "wipe user data". That gets you back to a clean state. – ToolmakerSteve Jun 05 '18 at 21:01