Status Update
Comments
am...@google.com <am...@google.com>
ya...@google.com <ya...@google.com>
bo...@google.com <bo...@google.com> #2
Hi, sorry for the trouble. I am working on improving our radio HAL. Unfortunately, it will take a while because it is very large. Please do not send non-ASCII characters in SMS.
ws...@gmail.com <ws...@gmail.com> #3
I've tried with ÄÇÖÜà èéìòùäñöü and all of them are correctly sending only one SMS and not two concatenated.
bo...@google.com <bo...@google.com> #4
I've tried with ÄÇÖÜà èéìòùäñöü and all of them are correctly sending only one SMS and not two concatenated.
I see, maybe we missed that one Unicode somewhere then. Could be easier to fix then. I will take a look this week. Thank you for pointing this.
ws...@gmail.com <ws...@gmail.com> #5
Sending a character outside that set, like á, message it's correctly split into 2 parts, first one of 70 chars as expected.
bo...@google.com <bo...@google.com> #7
ws...@gmail.com <ws...@gmail.com> #9
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Emulator 35.4.6 Canary
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
bo...@google.com <bo...@google.com> #10
that is why it was trying (unsuccessfully) to read $HOME/.android/./config.ini
ws...@gmail.com <ws...@gmail.com> #11
ANDROID_HOME is set to the same thing as ANDROID_SDK_ROOT. Doesn't help.
bo...@google.com <bo...@google.com> #12
could you remove the path.rel=. and try again?
ws...@gmail.com <ws...@gmail.com> #13
Yes, that worked. Thanks! Any idea why this changed? This is still a bug, right?
bo...@google.com <bo...@google.com> #14
explanation:
emulator 31.2 takes absolute path first, and 31.3 take relative path first.
it turned out relative path code path ignores the ANDROID_AVD_HOME (both 31.2 and 31.3 ignore), and that only
works for default ANDROID_HOME setup (/home/user/.android)
will fix this
sorry for the inconvenience and thanks for reporting the bug to us.
ws...@gmail.com <ws...@gmail.com> #15
That makes sense. Thank you!
ws...@gmail.com <ws...@gmail.com> #17
Yes, this artifact works fine. Any idea when this could be released?
de...@google.com <de...@google.com> #19
to...@gmail.com <to...@gmail.com> #20
tonyvg2013@gmail.com
Tony if you want to contact me for some questions or related topic it would be great.
I have been a whitness for the activity of my friends and others over 35 individual cases of the same MO.
Description
We're running the
emulator
CLI, using the latestAPI 30 AOSP ATD x86
image, on an x86_64 host, like this:/android-emulator-sdk/emulator/emulator -avd emulator-avd -no-boot-anim -read-only -verbose -no-window -sysdir ./system/x86 -system ./system/x86/system.img -ramdisk ./system/x86/ramdisk.img -qemu -enable-kvm
On emulator 31.2.10:
and the emulator starts successfully.
On emulator 31.3.10:
Eventually failing with this:
(Note: we pass the
-sysdir
arg explicitly, since our system images are not stored in the SDK directory.)Found AVD target architecture: arm, thus trying to run qemu-system-aarch64-headless, seems likely to be the root cause?