Assigned
Status Update
Comments
cm...@google.com <cm...@google.com>
rk...@google.com <rk...@google.com> #2
Correction: I meant mysid/toro, not yakju, in the subject line. But this affects yakju, as well.
va...@gmail.com <va...@gmail.com> #3
I want this.
rk...@google.com <rk...@google.com> #4
I wan't this too! And I want't all Android 4.1+ devices to have it, not only the Nexus.
va...@gmail.com <va...@gmail.com> #5 Restricted
Restricted
rk...@google.com <rk...@google.com>
va...@gmail.com <va...@gmail.com> #7
I would love to see BT4 support. Seems to be the only other option to ANT+ when it comes to fitness sensors.
rk...@google.com <rk...@google.com> #8
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.
va...@gmail.com <va...@gmail.com> #9
@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.
rk...@google.com <rk...@google.com> #10
@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...
Description
Android Studio Meerkat | 2024.3.1 Beta 1
Build #AI-243.22562.218.2431.12926017, built on January 16, 2025
Runtime version: 21.0.5+-12771278-b631.28 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.lwawt.macosx.LWCToolkit
macOS 15.2
Kotlin plugin: K2 mode
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 8192M
Cores: 10
Metal Rendering is ON
Registry:
debugger.new.tool.window.layout=true
ide.mac.native.pipette=true
ide.experimental.ui=true
ide.hide.toolbox.promo=true
ide.mac.stage.manager.support=true
idea.ignore.disabled.plugins=true
i18n.locale=
terminal.new.ui=true
jdk.updater=false
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 35.4.7-12936821
Hypervisor Version: HVF 15.2.0
Android SDK Tools: 26.1.1
Host Operating System: macOS 15.2
CPU Manufacturer: Apple CPU
Virtualization is supported
Bare metal
64-bit CPU
RAM: 32768 MB
GPU:
Build Fingerprint: google/sdk_gphone64_arm64/emu64a:14/UE1A.230829.036.A4/12096271:user/dev-keys
AVD Details: Name: Pixel_8_Pro
CPU/ABI: arm64
Path: /Users/nek/.android/avd/Pixel_8_Pro.avd
Target: google_apis_playstore [Google Play] (API level 34)
Skin: pixel_8_pro
SD Card: 512M
AvdId: Pixel_8_Pro
PlayStore.enabled: true
avd.ini.displayname: Pixel 8 Pro
avd.ini.encoding: UTF-8
disk.dataPartition.size: 6442450944
fastboot.chosenSnapshotFile:
fastboot.forceChosenSnapshotBoot: no
fastboot.forceColdBoot: no
fastboot.forceFastBoot: yes
hw.accelerometer: yes
hw.arc: false
hw.audioInput: yes
hw.battery: yes
hw.camera.back: virtualscene
hw.camera.front: webcam0
hw.cpu.ncore: 4
hw.dPad: no
hw.device.hash2: MD5:285089d225c2d59e55162831e66d8f93
hw.device.manufacturer: Google
hw.gps: yes
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.gyroscope: yes
hw.initialOrientation: portrait
hw.keyboard: yes
hw.lcd.density: 480
hw.lcd.height: 2992
hw.lcd.width: 1344
hw.mainKeys: no
hw.ramSize: 2048
hw.sdCard: yes
hw.sensors.light: yes
hw.sensors.magnetic_field: yes
hw.sensors.orientation: yes
hw.sensors.pressure: yes
hw.sensors.proximity: yes
hw.trackBall: no
image.sysdir.1: system-images/android-34/google_apis_playstore/arm64-v8a/
runtime.network.latency: none
runtime.network.speed: full
showDeviceFrame: yes
skin.dynamic: yes
tag.display: Google Play
tag.displaynames: Google Play
tag.ids: google_apis_playstore
vm.heapSize: 256
Steps to Reproduce Bug: Just start the emulator and open an app. The emulator crashes every 30 seconds, on every single page open, and especially when hiding and showing system bars or controlling insets.