Assigned
Status Update
No update yet.
Comments
rk...@google.com
Correction: I meant mysid/toro, not yakju, in the subject line. But this affects yakju, as well.
st...@gmail.com
I want this.
rk...@google.com
I wan't this too! And I want't all Android 4.1+ devices to have it, not only the Nexus.
rk...@google.com
I would love to see BT4 support. Seems to be the only other option to ANT+ when it comes to fitness sensors.
st...@gmail.com
Why is this considered an enhancement? The fact that Android doesn't support the latest standards and is behind iOS will run developers to iOS. Unfortunately my company cannot wait for Google to include this "enhancement" in their OS and with great sadness we are moving to iOS.
BLE is not a nice to have, it's the next big thing in short range networking.
BLE is not a nice to have, it's the next big thing in short range networking.
rk...@google.com
@tomer...
I don't think it fair to say "Android doesn't support the latest standards." The fact that both ICS and Jelly Bean fully support BT4.0, which includes BLE, is well-documented. Other ICS devices like the One X and the Galaxy SIII support BLE. It is just the Nexus that is crippled in this regard, with a compatible stack but no driver support.
I don't think it fair to say "Android doesn't support the latest standards." The fact that both ICS and Jelly Bean fully support BT4.0, which includes BLE, is well-documented. Other ICS devices like the One X and the Galaxy SIII support BLE. It is just the Nexus that is crippled in this regard, with a compatible stack but no driver support.
st...@gmail.com
@jdavidmo...
So what you say is that it's up to the phone manufacturer to supply a driver? And this is why the S3 and Motorola RAZR has this support?
How come it's so har to supply a driver for this? There aren't that many different BT chipsets around...
So what you say is that it's up to the phone manufacturer to supply a driver? And this is why the S3 and Motorola RAZR has this support?
How come it's so har to supply a driver for this? There aren't that many different BT chipsets around...
ko...@google.com
Well, I said driver, but I don't know if that's the case. I don't know who is responsible for it in this instance. It could be Google, Samsung, or Broadcom for all I know; my point is that the chip and ICS/JB support BT 4.0, so the Nexus should have it. It is not that Android doesn't support BT4 or BLE; it is just this phone for some reason.
According to iFixIt, the Nexus contains a "Samsung SWB-B42 BT 4.0 Dual Band Wlan FM Tx/Rx. Chipworks says the module is actually manufactured by Murata, and houses a Broadcom BCM4330 die inside."
http://www.ifixit.com/Teardown/Samsung-Galaxy-Nexus-Teardown/7182/2#s30574
If it is the BCM4330, it supports BLE:http://www.murata-ws.com/wi-fi.htm
According to iFixIt, the Nexus contains a "Samsung SWB-B42 BT 4.0 Dual Band Wlan FM Tx/Rx. Chipworks says the module is actually manufactured by Murata, and houses a Broadcom BCM4330 die inside."
If it is the BCM4330, it supports BLE:
wb...@gmail.com
Sorry, but I disagree with the statement that Android supports BLE. There's no API for GATT, no way to receive advertisement data, no way to control the device's role, basically no support for any of the new features introduced with BLE. That's why Motorola and Broadcom came up with their own (very limited) BLE stacks for Android. There may be some support down under at the BlueZ level but if there's no framework support and no API it cannot reasonably be considered as supported.
rk...@google.com
[Comment deleted]
Description
STEPS TO REPRODUCE:
1.
2.
3.
ATTACH SCREENSHOTS/RECORDINGS OF THE ISSUE
ATTACH LOG FILES (Select Help > Show Log in Files, or Show Log in Finder on a Mac)
------------------
IMPORTANT: Please read
all required information.
------------------
Studio Build:
Version of Gradle Plugin:
Version of Gradle:
Version of Java:
OS:
********************************************
The Android Emulator is crashing immediately when trying to run with OpenGL (-gpu host) or Vulkan (-gpu vulkan) on my Intel UHD Graphics 620 GPU.
Previously, Vulkan worked fine, but after a recent Intel GPU driver update or Windows update, Vulkan is no longer detected properly. OpenGL also fails, and the emulator terminates unexpectedly.
Even with Hyper-V and WHPX fully disabled, the emulator continues to crash. Logs indicate warnings about Vulkan incompatibility, OpenGL rendering failure, and snapshot corruption.
-/ System Information:
OS: Windows 10 Pro (Version 10.0.19045.5440)
Processor: Intel Core i5-8350U (VT-x Enabled)
GPU: Intel UHD Graphics 620
GPU Driver Version: 31.0.101.2130
Vulkan API Version: 1.3.215 (Verified with VulkanCapsViewer)
Android Emulator Version: 35.3.11.0
AVD Device: Pixel 7 Pro (API 35, x86_64)
HAXM Status: Installed & Running
Steps to Reproduce the Issue:
1 - Open Android Emulator (latest version).
2 - Create an AVD with API 35 (Pixel 7 Pro, x86_64).
3 - Run the emulator using OpenGL: emulator -avd Pixel_7_Pro_API_35 -gpu host
* Emulator crashes immediately.
4 - Run the emulator using Vulkan: emulator -avd Pixel_7_Pro_API_35 -gpu vulkan
* emulator -avd Pixel_7_Pro_API_35 -gpu vulkan
5 - Check logs – Vulkan is no longer supported despite previously working.
6 - Check Windows Event Viewer – Logs show qemu-system-x86_64.exe crashed due to ntdll.dll error.
-/ Expected Behavior:
The emulator should run without crashing using OpenGL (-gpu host) or Vulkan (-gpu vulkan).
-/ Actual Behavior:
The emulator fails to start and crashes immediately.
Vulkan is not detected properly, even though VulkanCapsViewer confirms it should work.
OpenGL rendering (-gpu host) crashes.
AVD snapshot is corrupt and cannot load.
Emulator logs show:
""""
WARNING | Your GPU 'Intel UHD Graphics 620' has driver version 1.3.215, and cannot support Vulkan properly.
ERROR | Failed to find ColorBuffer:0
WARNING | Failed to load snapshot 'default_boot'
""""
Event Viewer logs show a crash in ntdll.dll :
""""
Faulting application: qemu-system-x86_64.exe
Faulting module: ntdll.dll
Exception code: 0xc0000374
""""
-/ Emulator Logs & Crash Details:
* Vulkan Not Working:
"""
WARNING | Your GPU 'Intel(R) UHD Graphics 620' has driver version 1.3.215, and cannot support Vulkan properly. Please try updating your GPU Drivers.
""""
* OpenGL Rendering Issue:
INFO | OpenGL Renderer=[Android Emulator OpenGL ES Translator (Intel(R) UHD Graphics 620)]
INFO | OpenGL Version=[OpenGL ES 3.0 (4.5.0 - Build 31.0.101.2130)]
ERROR | Failed to find ColorBuffer:0
* AVD Snapshot Corruption:
WARNING | Failed to load snapshot 'default_boot'
USER_WARNING | The saved emulator state could not be loaded, performing a cold boot.
* Crash Detected & Saved in Logs:
INFO | Storing crashdata in: C:\Users\Pc\AppData\Local\Temp\\AndroidEmulator\emu-crash-35.3.11.db
-/ What I Have Tried So Far (No Fixes Worked):
1- Disabled Hyper-V & WHPX (bcdedit /set hypervisorlaunchtype off).
2- Updated Intel UHD 620 GPU Drivers (Latest version 31.0.101.2130).
3- Reinstalled Vulkan Runtime (From LunarG Vulkan SDK).
4- Tried Lower API Levels (API 30, API 28, API 27) – All failed the same way.
5- Tried Software Rendering (-gpu swiftshader_indirect) – Works, but is too slow.
6- Deleted & Recreated AVDs – No change.
7- Wiped AVD Data & Disabled Snapshots – No improvement.
8- Tried Running Older Emulator Versions – Issue persists.
Attachments:
1- Full Emulator Log (emulator_log.txt)
2- Event Viewer Crash Report (qemu-system-x86_64.exe failed due to ntdll.dll)
3- VulkanCapsViewer Report (Shows Vulkan 1.3.215 is detected but emulator doesn’t use it)
4- android studio , message issue screenshot