I'm using:
Mac OS High Sierra 10.13.4
Android Studio 3.1.1
Nexus 5X emulator with API level 27
On its top, the emulator is not clickable or draggable, I just cannot drop down the notification bar or click the back button in app. This is not happening at the bottom of the emulator...anyone experiencing the same issue? I don't know if this could be useful, but I'm using a double monitor (macbook + led panel).
EDIT: I think there's a problem with smaller devices. same problem with Pixel 2 (NOT XL).
Works fine with Pixel 2 XL.
EDIT 2: Pixel 2 works fine on API level 25 (Nougat).
I thought that experienced exactly this issue with the Pixel 4 API 31 emulator running in AndroidStudio 2021.1.1 on Ubuntu today; however, it turned out to be user expectations of older APIs combined with a barely-readable notification icon in the bar.
I wanted to open the device settings; my own devices are older Android 9 and to do this, I just tap the notification bar, it expands, and I click on the gear icon which immediately appears in the notification bar area once the pane expands to show quick settings.
The API 31 UI acts differently - first of all, I thought there was a permanent settings gear already in the notification bar. I thought that was odd, but, okay, I'll click it to open... turns out that this is not the case: it's an actual notification icon that looks like a settings gear from the Google Setup program trying to complete the initial setup on the phone (this was a new emulator). Tapping it did nothing, of course, but was frustrating because I thought it was a setting gear. Strike one, and had me googling for "Emulator top bar not responsive" leading me here.
Secondly, clicking to "tap" on the notification bar in API 31 doesn't immediately expand it like it does on my API 28-based Note 8: I had to "click and swipe" down (awkward with the mouse) to open notifications. And in API 31, even this is not sufficient to see the actual phone settings gear either! You have to swipe down one more time to further expand the notification pane and finally you can see the gear to open settings.
These two things combined to make me believe that the emulator was non-responsive when clicking the notification bar at the top.
I hope this helps someone else realize what might be happening - took me more time to write this up than the actual "problem" cost me, but I was so annoyed at this "broken" emulator which wasn't opening the settings for me that I had to write it up!
Related
I was just testing my app on Pixel3 XL emulator and noticed that the app bar is covered by the bezel. I thought the flutter framework handles this for app bar own its own.
Is there a way to fix this? I also looked at SafeArea but that probably would make me to manage the app bar on all the pages of BottomNavigationBar.
This is an issue with the emulator, not Flutter. If you open Chrome on the emulator you will see that it's also covered by the notch. You can also drag from the notch and the notification's pane will be dragged down, even thought it shouldn't be possible.
You can fix this though. Open the Android settings, go to to the About phone section and tap on the Build Number 7 times, to enable developer mode. Once that's done, in Settings, go to the System section, open Advanced and go to Developer options. Tap the Display cutout option and select Tall cutout. This will adjust the OS to account for the notch.
I've just update my Android Studio together with the Android Emulator to the newest version. After I click "run" in my project and selected my emulator, it boots up like normal. However, when the app pops up, I can hear some strange noise produced. I've made sure that I didn't set the app to play any sound. Link to the strange noise
Android Emulator: Galaxy Nexus API 27
Android Studio Version: 3.0.1
Turn off Touch Sounds on the Android device/emulator.
You can find it under Settings -> Sound & notification -> Other sounds -> Touch sounds
That sound was actually the notification sound of the emulator. Since my app is in landscape mode, it needed me to configure the keyboard in landscape mode. So the notification came out.
On Android 10/11/12 emulators, this odd "sparkle" sound happens when rotating the device to landscape or portrait. Here's how to turn it off:
Launch your Android 10 or 11 emulator (API 29 or 30)
Drag and pull down the notification bar at the top (screenshot A)
You should see a "Configure physical keyboard" notification from the status bar. Drag it to the right slowly and by a small amount, to reveal the settings cog icon ️️⚙️ (screenshot B)
Press the Settings cog icon ⚙️ to reveal the expanded options (screenshot C)
Click on "Silent - No sound or vibration", then click "Apply/Done"
Optional: If a "Configure physical keyboard" notification still appears, swipe it to the right, to remove it.
Another way - Android 10/11
On the Home screen, swipe up to reveal all the apps
Settings ➔ Apps & Notifications ➔ Notifications ➔ Android System ➔ Physical Keyboard (and/or Virtual Keyboard) ➔ Switch it off or click it and set it to Silent.
Another way - Android 12 (API 31)
On the Home screen, swipe up to reveal all the apps
Settings ➔ Notifications ➔ App Settings ➔ Click the '3 dots' menu at the top ➔ Show System (to reveal system apps in the list) ➔ Android System ➔ Physical Keyboard (and/or Virtual Keyboard) ➔ Switch it off or click it and set it to Silent.
Now there are no more annoying noises when changing the emulator's orientation.
Try using emulators, like genymotion or bluestacks. They are pretty good. On the other side, in my experience, Android Studio emulators are very slow and buggy.
It can be due to multiple reasons:
One of the reason is
If you turn your laptop Bluetooth ON. If that is the case, turn Bluetooth off and restart the emulator.
I made android emulator for Nexus 10 using latest ADT(21) and SDK tools.
I know that in Android JellyBean 4.2 there's a new feature called DayDream. I want to access it in my Nexus10 Emulator I have. but don't know how.
i am not getting option Daydream inside Settings -> Display.
How can i enable and use it Inside Emulator?
Here's what i need to do:
1st Step: Launch the Settings app, scroll to the bottom, and tap About Phone.
2nd Step: In the middle of the screen is the listing for Android Version. Tap this item until you see a jelly bean appear on your screen. You can then tap and hold the giant jelly bean until your device vibrates. You should then see interactive beans floating all over your screen. And yes, you can fling them. Go ahead, try it.
3rd Step : After doing, this the BeanFlinger Daydream will be unlocked. You can find the Daydream option by going to Settings > Display > Daydream.
Hope it Will Help to all of the Users Facing this Same kind of Problem.
I too had the same problem, what I did was, previously, I had an emulator with 4.2.1 version. I changed it to 4.3, now its working for me.
As the title says, my menu items no longer have their icons in the Android emulator. I am developing with API 16 and recently downloaded an update that became available for the SDK and the ARM image. Even after removing and reinstalling the whole Android SDK, the issue persists. I know that it isn't my own code because I reverted to a known version and it also has the same issue. The same version runs on an actual device as expected. I also previously ran the app on the emulator using API 7 and the icons appear just fine. Does anyone know if this is a known issue with the recent update?
Screenshot:
Previously, the menu items all appeared in a row at the bottom with icons above the text.
As the title says, my menu items no longer have their icons in the Android emulator.
This is the way the overflow appears on Android 4.0+, for devices and emulators with an off-screen MENU button.
Even after removing and reinstalling the whole Android SDK, the issue persists.
It will persist on the tens of millions of Android 4.x devices as well, or at least those that have a MENU button. Devices sans MENU button will have a similar-looking drop-down menu, emanating from the ... affordance on the right side of their action bar.
The same version runs on an actual device as expected.
That actual device is not running Android 4.x, presumably.
Does anyone know if this is a known issue with the recent update?
If by "recent update" you mean the nearly-year-old release of Android 4.0, then yes.
I have application which uses Sherlock ActionBar package.
The application uses platform-specific behavior for menu (so it's 3-dot icon in ActionBar on ICS and classic menu under HW button on pre-ICS)
I had recieved report from one user with HTC One X. It appears, that One X shows some "compatibility" bar with menu button on the bottom of screen, and there is also same button in ActionBar (where it's supposed to be).
I was not able to emulate this in AVD, and I have multiple reports that this issue is not present on Galaxy Nexus or Galaxy S (they show only the icon in ActionBar).
I have no idea where to look to resolve this or how to debug it, so any help or workaround will be appreciated.
Application is built against API14, with targetSdk="11"
You have a typo:
The android:targetSdkVersion in the manifest should be the solution - it's recommended by Google to always set it to the maximum available (currently it's 19).
Some websites do show that HTC shows the huge button on old apps, but not on new ones, as shown here, so if you think it's weird/ugly, simply set the target SDK. Also make sure it's updated in the project.properties file .