Fixed
Status Update
No update yet.
Comments
rk...@google.com
rk...@google.com
I'm also seeing this issue, specifically under low-memory conditions and only on a Nexus 5x running Nougat. I was trying to launch a camera intent from a fragment. I've attached my log as well.
ga...@gmail.com
I'm seeing this crash too, specifically on build NBD90W of Android on the nexus 5x (october security patches). We're not using a camera intent, but we're using the camera API directly.
rk...@google.com
Oh, good point -- I, too, am running build NBD90W with the October 5 security patches.
ga...@gmail.com
Same here and my app uses Google Maps and a few images. It only crashes upon exit. My device is also Nexus 5X w/ build number NBD90W.
rk...@google.com
I am on NBD90W as well.
ga...@gmail.com
I was the reporter for the question on Stackoverflow -- I'm definitely glad other people are having this issue. Hopefully it can be resolved!
rk...@google.com
Can you provide the below requested information to better understand the issue:
Steps to reproduce
What steps do others need to take in order to reproduce the issue themselves?
Please attach sample project to reproduce the issue.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Expected output
What do you expect to occur?
Current output
What do you see instead?
Android bug report:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
Steps to reproduce
What steps do others need to take in order to reproduce the issue themselves?
Please attach sample project to reproduce the issue.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Expected output
What do you expect to occur?
Current output
What do you see instead?
Android bug report:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
rk...@google.com
an...@google.com
Seeing the same crash here, I am using Android 7 and Nexus 5x.
an...@gmail.com
I can't come up with a good example project and unfortunately, I cannot share my project publicly as a result of my company's NDA. But, here's the bug report from our app:
https://drive.google.com/file/d/0Bzu4wPnZXr0FaTFFejM2STFkVTA/view?usp=sharing
I shared the file with android-bugreport@google.com as well but it looks like the email failed to deliver.
In any case, I have a fragment in my application. When an activity uses the fragment (via supportFragmentManager), things work fine. But when another activity has the fragment contained in a TabAdapter, I get a crash around 80% of the time. I experience the crash whenever I background this fragment. It should be noted that the app uses very similar amounts of memory in both of these cases (~30Mb)
The issue certainly seems to be memory-related. When I background the fragment, I get the standard TRIM_MEMORY_UI_HIDDEN from onTrimMemory. But just a few seconds later, I get a TRIM_MEMORY_COMPLETE and the app is killed (see my previous log).
I shared the file with android-bugreport@google.com as well but it looks like the email failed to deliver.
In any case, I have a fragment in my application. When an activity uses the fragment (via supportFragmentManager), things work fine. But when another activity has the fragment contained in a TabAdapter, I get a crash around 80% of the time. I experience the crash whenever I background this fragment. It should be noted that the app uses very similar amounts of memory in both of these cases (~30Mb)
The issue certainly seems to be memory-related. When I background the fragment, I get the standard TRIM_MEMORY_UI_HIDDEN from onTrimMemory. But just a few seconds later, I get a TRIM_MEMORY_COMPLETE and the app is killed (see my previous log).
le...@gmail.com
[Comment deleted]
Description
This is the correct behaviour in case characters of UCS-2 Encoding are used, but not for standard characters included into GSM 03.38
Ñ character is included into GSM 03.38 GSM 7-bit default alphabet:
In fact with a real phone only one SMS with 97 characters is received.
Code is pretty easy, see attached screenshots, with $ everything is ok, while with Ñ smsMessages array is made of 2 items
For privacy and security reasons I cannot attach more than this and full log files, but I think it may be enough because it's quite simple to reproduce.
Tested with emulator API 31 and API 35, both have the issue.
Studio Build: Build #AI-242.23726.103.2422.12816248, built on December 18, 2024
Version of Gradle: 8.9
Version of Java: 11
OS: Windows 11 Professional