IssueTracker

I am also facing the same problem. Please look into it.

Work around:

Set input type other than "InputType.TYPE_NULL"
<EditTextn>.setTextIsSelectable(true);

The above method is available API-14 onwards.

The above work around hides the soft keypad and also cursor will be visible.

[Comment deleted]

I got the same problem after I called .setInputType(InputType.TYPE_NULL), the cursor disappeared.

Use this workaround:

<EditText>.setOnTouchListener(new View.OnTouchListener(){
                @Override
                public boolean onTouch(View v, android.view.MotionEvent event) {

                      int inType = <EditText>.getInputType(); // backup the input type
                      <EditText>.setInputType(InputType.TYPE_NULL); // disable soft input
                      <EditText>.onTouchEvent(event); // call native handler
                      <EditText>.setInputType(inType); // restore input type
                      return true; // consume touch even
                }
            });

Cursor is visible, but don't have ability to move it by touching on <EditTex> in Android 4.0+. Is any solutions?

I have finally found a (for me) working solution to this.  

First part (in onCreate):
mText.setInputType(InputType.TYPE_NULL);
if (android.os.Build.VERSION.SDK_INT >= 11 /*android.os.Build.VERSION_CODES.HONEYCOMB*/) {
        // this fakes the TextView (which actually handles cursor drawing)
        // into drawing the cursor even though you've disabled soft input
        // with TYPE_NULL
        mText.setRawInputType(InputType.TYPE_CLASS_TEXT);
}


In addition, android:textIsSelectable needs to be set to true (or set in onCreate) and the EditText must not be focused on initialization.  If your EditText is the first focusable View (which it was in my case), you can work around this by putting this just above it:
<LinearLayout
  android:layout_width="0px"
  android:layout_height="0px"
  android:focusable="true"
  android:focusableInTouchMode="true" >
    <requestFocus />
</LinearLayout>

You can see the results of this in the Grapher application, free and available in Google Play.

[Comment deleted]

the above solution worked for me as well,,,, I was struggling with this problem for hours....

[Comment deleted]

It worked not for all models. For example, doesn't work on CUBE U9GT2, android 4.0.3.

It really helps a lot. Thanks.

See this for an untested workaround based on #2, above, and please report your results if you try it.

http://stackoverflow.com/questions/12366867/edittext-missing-cursor/19811046#19811046

[Comment deleted]

#14 e...@google.com:

How is this obsolete when the bug still exist? As of Android version 6.0, setting InputType.Null still disable the text cursor. And the work around above introduce it's own issues like the Android OS forcing a suggestion box on the screen!!!

I still have this issue in several Android Versions e.g. 5.1.1 and 6.0!

Google, please solve issues reported to you instead of waiting several years and then setting it to "osolete"!
Thanks!

I am also facing this issue. But "editText.setTextIsSelectable(true);" works for me. Thanks..

I'm facing the same issue, but both "editText.setTextIsSelectable(true);" and "mText.setRawInputType(InputType.TYPE_CLASS_TEXT); " don't work form me; still trying to find a solution.

I am starting to hate the emulator take a look free sample on a brand new Mac book Pro 15" Quad Core i7

Same this updated to Mac OS 10.7 kernel panics twice a day..Please resolve..

Do all persons that experience Lion panics have Time Machine enabled? I saw some thread speaking about kernel panics and Time Machine and I just disabled it. I'm not sure about this but I haven't experienced more panics.

I don't have Time Machine enabled and i get the kernel panic.

Time machine disabled, still getting kernel panics :(
can't finish my thesis project like this :(((((

so what happened with this subject I still getting this issue and it's sucks last time i had my MAC wouldn't turn on...

Also happening when using version 2.2 as emulator. Time machine disabled here as well. Extremely annoying, and should be given priority.

I think this is the same case http://code.google.com/p/android/issues/detail?id=15025 right? why this haven't being solved? Hopefully it won't give that problem on ICS

I increased the heap space used by Eclipse, and haven't experienced this problem since.

In eclipse.ini I used the following values:
--launcher.XXMaxPermSize256m
-Xms256m
-Xmx1024m

Could anyone else try this, and see if it works?

Thanks, Hans Petter. I've increased the memory limits and restarted the emulator several times, both on my desktop iMac and my MBA. No kernel panics so far, and it was happening reliably (in a manner of speaking...cough) before.

I'm using Titanium Studio which uses a customized version of Aptana/Eclipse. In case other Ti users run across this, the relevant file is hidden inside the application bundle. Right/control click on TitaniumStudio.app and choose Show Package Contents, then go to Contents/Mac OS. The file you want is TitaniumStudio.ini. launcher.XXMaxPermSize was already set to 256m and -Xmx was already 1024m, but -Xms was only 40m. I bumped up -Xms40m to 256m as Hans Petter suggested, and increased -Xmx to 1536m just for luck. :-)

This doesn't appear to be a Android or even Eclipse bug per se -- others are reporting similar problems with NetBeans. See: http://www.mailinglistarchive.com/html/java-dev@lists.apple.com/2011-08/msg00018.html

Has anyone on this thread filed a bug report with Apple?

I'm glad there's a workaround -- I've been installing test builds on my physical device, but that doesn't give good debugging output and of course you don't have the ability to check different screen sizes, etc.

I reported it now:
https://bugreport.apple.com/cgi-bin/WebObjects/RadarWeb.woa/41/wo/aSoi6G405Y4Nye2XwHLPs0/11.66

Please fill in any additional info that you might have.

No that did not work for me still getting kernel panic... this is really anoying

Apple is tracking this issue under rdar://10260008 (finally confirmed after a few rounds of "Please know that our engineers have not been able to reproduce the Panics"). Since Radar is a closed bug system, only Apple can advise on its status or any potential workarounds.

jose(?): Strange. I haven't experienced any panics since I changed the values, and experienced 1-2 a day before.

Should be irrelevant what settings you have in Eclipse.
If you want to see the crash, just create a Job in Jenkins to start the emulator in some way. I just wanted to set up the beginning of our CI system, and seen this happen way too often. APK creation and deployment on the emulator, then some Robotium tests too. The latter will help you trigger the bug very easily...

I've only been testing for a day or so but, since I upgraded my Lion to the latest update, I haven't had any kernal panics from the emulator.  Good luck devs!

You have just been lucky so far, or haven't used your emu much.
No more updates here and I had 5 panics the last 24 hours.

Agree with @Peter, the crash reduce but still are happening!

#MeToo

OSX 10.7.2

I get this crash regularly with the 2.1 and 2.3.3 Emulators.

Crash details attached.

@Hans Petter

I'm running with the increased Eclipse mem.

there is no permanent fix yet?

Some of my students told me that if you made ​​a clean installation of the Lion, the problem does not happen. However do not want to risk. Someone who had the problem, did this type of installation?

I have this same issue, what can I say is that, for me, emulator-arm needs to be running without interaction to reproduce this error

Same issue for me, occasionally crashes my MBP when the emulator is booting.

Same for myself, MBP, Lion 10.7.1, Eclipse Indigo, android 2.3.3 Emulator on an
i7 4GB memory.
HAppened three times in the last 24 hours

Same issue for me.
Environment:
- OS X Lion (Mac Mini 5 i5 2GB).
- Eclipse Indigo.
- Android Emulator 2.3.3 and 4.0 too.
Usually freeze when emulator is starting.

stack trace:
panic(cpu 3 caller 0xffffff80002c207e): "kernel_trap(0xffffff8009400710) with 32-bit state"@/SourceCache/xnu/xnu-1699.24.8/osfmk/i386/trap.c:586
Backtrace (CPU 3), Frame : Return Address
0xffffff80094004c0 : 0xffffff8000220702
0xffffff8009400540 : 0xffffff80002c207e
0xffffff80094006e0 : 0xffffff80002d7a1d
0xffffff8009400700 : 0x105b28506

Still experiencing crashes.  I'm on 10.7.2 with the 4.0.3 emulator on a 2010 MacBook Pro and using IntelliJ IDEA 11 CE.

I read before that this issue was added to Apple's internal tracking system, but I wasn't able to view it when I tried following the instructions to access it.   Has there been any progress?

Also I re-read this thread and saw a suggestion to try using -no-audio.   I haven't done this before and will try to use that switch going forward.

Definitely the emulator causes kernel panic on Mac OS X. I use Mac OS X 10.7.2 on a MacBook Air late 2011 and I experienced kernel panics 4 or more times a day work, all of them sending report to Apple.

I decided then to buy a device for debugging because the kernel panics would cause some data corruption in my system.

Definitely it's an urgent matter to solve.

MacOS not ready for prime time - going back to Win7.
Same problems 2.3.3

Same problem for me, just bought and crashed twice in the first day after installed Eclipse and Android SDK. I'm just trying the suggestion In eclipse.ini:
--launcher.XXMaxPermSize256m
-Xms256m
-Xmx1024m

I'll let you know,
Marco

[Comment deleted]

This is happening at least daily to me as well on a Mac Mini running up to date Lion. We aren't using eclipse, just emulator to do testing of builds of our android app.

Mac OS X Lion + Eclipse 3.7.1 INDIGO + Android Virtual Device 2.2 FROYO = OS CRASHES !!!!

EVEN UNASSIGNED??? WE HAVE TO WORK TO PROVIDE ANDROID MORE APPS AND YOU DON'T ASSIGN THE ISSUE TO A PERSON? DO WE HAVE TO THINK THAT IT'S BETTER APPLE ???????????

my problem is probably gone - I'm using the same Lion 10.7.2, but started using a brand new eclipse 3.7.1 installation... the android SDK is still the same, both 2.3 and 4.0 emulators didn't crash for more than a week.
weird.

The suggestion in comments 51, etc. also worked for me. More specifically: if there is no eclipse.ini in Eclipse.app/Contents, add one, and add

--launcher.XXMaxPermSize256m
-Xms256m
-Xmx1024m


I haven't had a crash since this happened.

Marco's suggestion was missing vmargs before passing actual JVM paramters:
--launcher.XXMaxPermSize256m
-vmargs
-Xms256m
-Xmx1024m
That solved the problem for me.

Is this a duplicate of http://code.google.com/p/android/issues/detail?id=15025 ?

I repeat my comment from that other bug:

How can eclipse.ini have any impact on this when I see the crash even if I start emulator-arm from the command line, no Eclipse involved?

Has anybody seen the crash with OS X 10.7.3 btw? (Personally I switched my Android work to my Linux laptop partly because of this crashing problem...)

I haven't seen a crash in ~3 months, with moderate amount of android development.
using 10.7.3, the Xms settings from above. Also, I've done a new installation of eclipse 3.7.1

It seems 10.7.3 fixed the kernel panic this crash caused, but now the emulator just crashes with an EXC_BAD_ACCESS very frequently. Attached is the crash report for one of these crashes. This happens to me multiple times a day.

@alex pretzlav; Can you try uninstalling SIMBL to see if that improves emulator stability. The SIMBL bug at http://code.google.com/p/simbl/issues/detail?id=51 makes me a bit wary

If that doesn't improve things can you then try uninstalling Menu Extra Enabler because their site doesn't indicate they support Lion.

I've just installed the Lion 10.7.3 and after a few hours the problem did not occur. I'll test little more tomorrow. I'll notify you if the problem happens again :)

I've been using the latest version of the emulator on Lion and it didn't crash anymore.

What hasn't been fixed is still broken.
I will use the emulator again only if I see this issue in the changelog as fixed.

I don't feel like having an OS crash again, Eclipse is so unable to handle that (settings gone etc.). Until then, only real devices.

@peter.v...: But note that the actual *bug* of course was in Mac OS X; no matter what a user-level process (like the emulator) does, the kernel should obviously not crash. So sure, it would be nice if the emulator people had found out what caused the crash and added a workaround, but even better if the Apple people noticed the kernel crash reports and fixed that. So you should actually try to check the Mac OS X kernel changelogs. Good luck.

That's all true, but long story short, I think Google should take care about this and post a bug report for apple. I don't have an iDev account, but I am sure they do :)

After five days using the emulators (2.1, 2.2, 2.3 and 4.0.3) and devices (Galaxy S and Asus Transformer) in my Android classes, I didn't have kernel panic anymore. I think the problem was fixed in the latest OS X version (10.7.3).

I no longer experience these issues on 10.7.3
leaving the thread now.

Experienced crash running Android 2.3.3 emulator on Mac OS 10.7.4.

> adb version
Android Debug Bridge version 1.0.29

> emulator-arm -version
Android emulator version 18.0 (build_id MASTER-306762)
Copyright (C) 2006-2011 The Android Open Source Project and many others.
This program is a derivative of the QEMU CPU emulator (www.qemu.org).

  This software is licensed under the terms of the GNU General Public
  License version 2, as published by the Free Software Foundation, and
  may be copied, distributed, and modified under those terms.

  This program is distributed in the hope that it will be useful,
  but WITHOUT ANY WARRANTY; without even the implied warranty of
  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  GNU General Public License for more details.

Just had a kernel panic after five minutes of using the emulator. 10.7.4, problem is still present.

Didn't have a problem on 10.7.3. Updated to Mac OS 10.7.4 and now I'm getting regular kernel panics :(

I can only agree. Minimum 2-4 times a day I get a kernel panic due to the started AVDs.

The problem was fixed in 10.7.3 and now it's back in 10.7.4... this is costing me enormously. Half of my time goes to dealing with crashes

And how is your report to apple that their latest update has caused a regression going?

[Comment deleted]

Panic occurring on 2 MACS using 3.2 emulator
Mac Mini and MacBook Pro - both running 10.7.4
Eclipse Indigo - Service Release 2 Build id: 20120216-1857
Android SDK Tools - r17
Android Platform Tools - r11
Android ADT - r18

Your SDK tools and ADT are out of date. Try upgrading.

[Comment deleted]

See this post, it seems working for me :

http://www.ctrlplusz.com/2011/10/getting-rid-of-kernel-panics-when-running-the-android-emulator-under-os-x-lion/

About the raising eclipse memory fix, this is not true. I never used eclipse and had that issue.
According to the linked article and my experiences, I guess this kernel panic only occurs in race conditions, when CPU is highly loaded.
Which can happen with any other task than eclipse, or even simulator itself that sometimes goes nuts at 100% CPU. And that likely will happen more easily on a older computer, with less CPU/RAM...

Confirming this is still happening under ADT 20 and SDK Tools r20. This needs to be looked at ASAP.

Here's a bit of my report:

panic(cpu 0 caller 0xffffff80002c412e): "kernel_trap(0xffffff800bac16d0) with 32-bit state"@/SourceCache/xnu/xnu-1699.26.8/osfmk/i386/trap.c:587
Backtrace (CPU 0), Frame : Return Address
0xffffff800bac1470 : 0xffffff8000220792
0xffffff800bac14f0 : 0xffffff80002c412e
0xffffff800bac16a0 : 0xffffff80002da0cd
0xffffff800bac16c0 : 0x0

BSD process name corresponding to current thread: emulator-arm

Mac OS version:
11E53

Kernel version:
Darwin Kernel Version 11.4.0: Mon Apr  9 19:32:15 PDT 2012; root:xnu-1699.26.8~1/RELEASE_X86_64
Kernel UUID: A8ED611D-FB0F-3729-8392-E7A32C5E7D74
System model name: iMac11,3 (Mac-F2238BAE)

[Comment deleted]

This actually first appeared for me under Android 4.1 when it auto-chose WSVGA switching to the default WVGA800 fixed it for me.

Nevermind, it happened again :( Both times seemed to be when browsing in Google Chrome...

I'm using Eclipse 4.2 Juno btw.

If you experience this problem, you should file a bug report with Apple. Go to http://bugreport.apple.com/. The more bug reports about this Apple receives, the more likely they are to look into it.

Attach the panic log in your bug report. The panic logs can be found in /Library/Logs/DiagnosticReports/

seriously sucks - 4-5 panics a day for otherwise 1-re-boot-a-week-iMac :(

Does anyone know if this issue persists with Mountain Lion too?

This just happened to me.. ugh such a pain. Is it safe to say that I should develop on a VM now?

Has anyone experienced this on Mountain Lion ? I'm considering upgrading just to get rid of this issue.

An other Panic Report to help fix the issue

The question is, has anyone reproduced this crash on Moutain Lion ?

I've been using the Android emulator on Mountain Lion for several weeks now and have not experienced a kernel panic (I got them regularly on Lion). I have gotten a few emulator segfaults, but nothing that has taken my machine down. I suspect Mountain Lion did indeed fix whatever underlying bug the emulator was hitting.

I just had this issue running Mountain Lion. It's happening every time I try to start up an emulator.

Keeps crashing on OSX 10.8

Hi Everyone,

When I have upgraded my RAM from 2GB to 5GB its this issue is not happening.

Ravi Pulluri.

I have a 2010 21 inch iMac running Mountain Lion.  I have a second monitor.  I find that the emulator crashes when I try to restart an AVD that was closed while on the second monitor.  I foind that I could prevent the crash by using the Terminal to go to /Users/<my user name>/.android/avd/<name of avd>.avd and editing the file emulator-user.ini. The first line of this file contains the x position of the AVD window when the AVD was closed.  If this value is negative (i.e. on my second monitor), then the emulator crashes.  If I edit the value to 100, then the emulator does not crash.

Just my three pence worth...

I can confirm the fix in comment #99. A negative value in emulator-user.ini makes the emulator crash. Editing the value to a positive value fixes the crash.

same here, working dual screen on a 13-inch, medio 2010 OS X 10.8.2 (12C60)
#99 fixes it, when I drag the emulator to the second screen the emulater gets a blue transparant layer.

Hello!
Although the problem seems to be solved for emulator (see HAXM hotfix 1.0.4), however it persists for ADB.

Here is my configuration:
MacBookPro, MacOS 10.6.8, 2.3 GHz Intel Core i5,
Eclipse Indigo, Android Development Tools rev. 21, HAXM 1.0.4.

Steps to reproduce the kernel panic:
1) Launch emulator for Android 4.1.2 device, Intel Atom x86 (doesn't matter how - from command line or eclipse). It launches without problems, runs, etc...
2) Call "./adb devices" or any other adb command from command line
3) BUM! Kernel Panic!
I believe it's HAXM issue, because the same steps, but with ARM CPU doesn't produce kernel panic.

Please, fix it asap :)
Thanks in advance

Hi, we have reproduced the kernel panic with the adb tools currently. We will look into the issue. Thanks for the reporting.

Thanks
Xiaohui

Currently, you can try to use command line to start emulator with 32bit binary like this if you don't care you are not using a 64bit emulator binary:
#./tools/emulator-x86 -avd "your avd name"

In that way, you can still use adb tool before we have a solution.

Thanks
Xiaohui

Could it be that the issue is gone with the latest Android SDKs?

I have been using SDK V 21 with HAXM rev 2 on Lion 10.7.2 without issues for a few weeks, running an emulator with Android 4.0.3.

"adb devices" also works.

I just checked, now SDK 22 and HAXM rev 3 are available, have not tried that yet.

This bug is pretty old, and most people have switched to more recent of OS X.

Do people still experience this problem with the latest SDK Tools release? I'm going to close this bug since Lion hasn't been supported by Apple for a long time now.

On the other hand, if you have issues with 10.8 or 10.9, please open a new bug with more details.

And we are all switching to  Android Studio + Genymotion ;)

Forget Eclipse.

@sori...: And how exactly is Eclipse related to this bug at all?

Just read the thread...

Some extracts :

1- "I increased the heap space used by Eclipse, and haven't experienced this problem since.

In eclipse.ini I used the following values:
--launcher.XXMaxPermSize256m
-Xms256m
-Xmx1024m"

2-"The suggestion in comments 51, etc. also worked for me. More specifically: if there is no eclipse.ini in Eclipse.app/Contents, add one, and add

--launcher.XXMaxPermSize256m
-Xms256m
-Xmx1024m


I haven't had a crash since this happened."

Sure, but just because a lot of other people believe in placebo effects doesn't mean they are right. I have seen this bug (back when I ran ther Android emulator on OS X) with no Eclipse at all. I repeat, with no Eclipse at all. The initial comment here, i.e. the original bug report, also doesn't mention Eclipse at all. Only in comment #30 does somebody start mentioning Eclipse, and it's all downhill in comment quality after that. Sigh.

Ok, sorry.

Androids emulator can create Kernel Panics.
All the same, I haven't encountered this yet since switched to Genymotion's emulators.

http://www.genymotion.com/

Regards.

And here we are five years later with the same issues still happening...

OS X 10.11.4 (15E65)
Android Studio 2.1.2

I got this kernel panic with Android Studio 2.2.2 and OS X 10.11.6.
It occurs when android studio is starting ADB and looking for connected devices or emulators.
Also, it occurs if i run any ADB from terminal, like "adb devices".

I can confirm this happens throughout all versions of OSX >= 10.12 up to 10.12.6 on the latest mbpr 2016, sporadically when starting the emulator.

android-studio-2.3.3
android-emulator-26.1.2
intel-x86-emulator-accelerator-6.1.1

2019 and the same problem still.

I get this still in Android Developer Studio. Trying to connect Webcam0 to Back, phone is asking permission to use camera, add permission, get macos authorization popup, alllow. Everything freezes for a while(mouse, keyboard) and then macos crashes with some green light and reboots. Crashreport says:
panic(cpu 3 caller 0xfffffe0022be8f10): AMX exception from kernel, state=0xfffffe881d1679a0, esr=0xfe000003 @sleh.c:2438
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 23G93
Kernel version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6000
Fileset Kernelcache UUID: 998DB52EFE380DD975913B122F3AFE97
Kernel UUID: 6E79A99E-A9B0-3865-94D2-2BDD4F1504CB
Boot session UUID: 6F3E5985-6BB1-4C6F-BA5B-35E488094E3A
iBoot version: iBoot-10151.140.19
secure boot?: YES
roots installed: 0
Paniclog version: 14
KernelCache slide: 0x000000001a4fc000
KernelCache base:  0xfffffe0021500000
Kernel slide:      0x000000001a504000
Kernel text base:  0xfffffe0021508000
Kernel text exec slide: 0x000000001ba3c000
Kernel text exec base:  0xfffffe0022a40000
mach_absolute_time: 0x1a07eced9
Epoch Time:        sec       usec
  Boot    : 0x66fea74a 0x0002fbe4
  Sleep   : 0x00000000 0x00000000
  Wake    : 0x00000000 0x00000000
  Calendar: 0x66fea866 0x00043c3a