Fixed
Status Update
Comments
uc...@google.com <uc...@google.com> #2
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.
hu...@google.com <hu...@google.com>
bo...@gmail.com <bo...@gmail.com> #3
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.
bo...@gmail.com <bo...@gmail.com> #4
Oh, good point -- I, too, am running build NBD90W with the October 5 security patches.
wd...@google.com <wd...@google.com>
bo...@gmail.com <bo...@gmail.com> #5
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.
wd...@google.com <wd...@google.com> #6
I am on NBD90W as well.
bo...@gmail.com <bo...@gmail.com> #7
I was the reporter for the question on Stackoverflow -- I'm definitely glad other people are having this issue. Hopefully it can be resolved!
bo...@gmail.com <bo...@gmail.com> #8
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.
ap...@google.com <ap...@google.com> #9
Seeing the same crash here, I am using Android 7 and Nexus 5x.
bo...@gmail.com <bo...@gmail.com> #10
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).
li...@gmail.com <li...@gmail.com> #11
[Comment deleted]
ap...@google.com <ap...@google.com> #12
You can download our app from the Play Store (Gogobot City and Travel Guide, link below) and put it on your Nexus 5x with the latest updates. Run our app. Tap into some of the restaurants, destinations, etc... and generally exercise the app (but please don't put up any fake ratings, just browse - this is our live production app). Then exit out of the app by pressing the back button. You will get a message that says "Gogobot has stopped - x Close app" after a few seconds.
https://play.google.com/store/apps/details?id=com.gogobot.gogodroid
wd...@google.com <wd...@google.com> #13
It sounds like the issue is in the Nexus 5X's NBD90W Security update (firmware)- given that apps only started having this issue after the update was pushed.
Is this the right place to report a bug in that firmware or does Google use a different tracker for firmware (of so can you move it). The team that wrote that firmware update needs to look at these reports (probably with some urgency) as they seem widespread.
Is this the right place to report a bug in that firmware or does Google use a different tracker for firmware (of so can you move it). The team that wrote that firmware update needs to look at these reports (probably with some urgency) as they seem widespread.
[Deleted User] <[Deleted User]> #14
I'm having the same issue on app that I'm developing. In my view which extends TextureView and I have mediaPlayer inside which plays video. I lost couple of days trying to figure out what is a problem. Even in onPause in fragment I've nulled the view, and I still get this error. :-/ Nexus 5x, Nouget.
[Deleted User] <[Deleted User]> #15
We have passed this defect on to the development team and will update this issue with more information as it becomes available.
Description
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 26.0.0-3833124
Android SDK Tools: 26.0.1
Host Operating System: OSX 10.12.4 (16E195)
Steps to Reproduce Bug:
1. Use the Emulator with an Apple Magic Mouse (this one:
2. This mouse is very sensitive, so, inevitably, your finger will move by a few µm, which in turn will send some scrollwheel events to the emulator
3. For some reason, these events are interpreted as *clicks*
So basically when using this mouse, you end up involuntarily clicking all the time on your UI, which is very annoying/frustrating.
Expected Behavior:
Honestly the "wheel" should probably be completely disabled? IMHO.
But if not, it should work correctly.
Observed Behavior:
Anger and frustration :)