I've been absent for some times from WearOS development. Now I am back and I have one annoying issue with the latest emulator - it goes automatically in Ambient Mode after few seconds. Not just my app, but the OS itself.
I Checked into the settings, tried clicking on the top of the window, but no luck - is there a settings for this or I should file a bug?
Set the emulator to be charging.
Make sure Settings - Developer options - Stay awake when charging is enabled.(default)
PS: Click Settings - System - About - Build number quickly to enable Developer options.
Related
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.
A lot of older posts about AVD manager and its Android emulators suggest that device screen can be set to full screen by using Alt+Enter. In my case - it does not work. Neither does F11 or other shortcut key do the trick. To sum up what I want to know is, does the AVD manager emulators even support such thing? If yes, how, if not - are there any workarounds for it. The target device is a touchscreen monitor, so running in full screen is most important. Bonus question - is it possible display the toolbar with control icons (for controlling rotation, volume, hardware keys etc.) separately from main window in case the device screen is in fullscreen mode?
This is the Samsung Digital Heath ProgrammingGuide_SHealthService.pdf link
http://developer.samsung.com/html/techdoc/ProgrammingGuide_SHealthService.pdf
According to this guide document
3.3.1. S Health’s Developer Mode
Enable to active developer mode,
But in the S Health 5.4.1 version
I can't find how to active developer mode.
Is anyone know how to active?
Follow the below steps:
Open S-Health App
Go to Settings (Menu)
In bottom of the screen you will find: About S-Health, Tap on it
Now About S-Health Screen will open, and then tap 10 times on the version continuously.
Now you will see Developer mode on the version line (where you tap 10 times).
How can I test ambient mode in Android Wear emulator?
I need to see how does my app render on different watches while in ambient mode.
Seems ambient mode is different on Moto 360 and Sony Smartwatch 3.
To test Ambient Mode in an emulator, you need to do the following:
In the Emulator, Go to settings and Turn ON "Always-on Screen: ON".
While emulator window is active Press "F7" (F7 emulates the power button) then press the power button to turn on ambient mode.
Hope this helps.
On recent Wear emulators you can just press the power button in the associated control panel. The power button within the emulator frame acts as a press on the main button, eg opening the list of apps.
Not your main question but hopefully this helps you in regards to the differences you're seeing between the Moto 360 and SmartWatch 3 ambient modes:
I believe what you're referring to is ambient mode versus low-bit ambient mode. Google covers some of it in their developer documentation but it doesn't seem to be mentioned anywhere else. I did a huge write-up for the community based on my own research since I was frustrated with the lack of info (it's mostly written from a consumer perspective though):
http://www.reddit.com/r/AndroidWear/comments/2qb3ia/clarifying_ambient_modes_everything_you_could/
The latest Wear emulator lets you click in the top of the emulator window to toggle between full power and ambient modes (the shaded section in the screenshot).
I am running a VirtualBox with android-x86 (as a replacement for the ultra-slow AVD emulator).
Its a Linux VirtualBox running android 4.0, on a Windows 7 Host.
The machine boots up and everything works fine, but if i leave the machine idle for less than 5 min, i can't perform any action - all the menus,buttons,etc are unresponsive although the android clock is changing, and i can go to command (alt + F1) and back to gui (alt + F7).
Has anyone came across this phenomenon or has an idea what goes wrong here?
I was able to get back to the screen by clicking ACPI shutdown menu(HOST + H)
It is pretty simple. Just hold ESC + MENU (A key between right-alt and right-ctrl) and the machine will wake up.
I had this problem today and couldn't solve with any keys provided by the documents.
Android will resume if you try to close the VirtualBox window, and when asked, select to send shutdown signal instead of forced shutdown.
Try disabling the sleep time to never. You can find it under settings.
Here are something users need to know
You can only use ESC, Menu, left, right, up and down keys to wake up the system.
To wake up the system ,you have to hold the keys mentioned above for at least 1 second.
You can push menu key when keyguard screen showing up to unlock screen.
You can use mouse to turn the wheel on the keyguard screen to unlock screen.
Source : http://old.android-x86.org/documents/how-to-wake-up-machine
open the "dev tools" app / developer options / stay awake.