I was playing around with my tablet and testing my program, when there was a notification that said bug report captured and whether I would like to share it. I had not seen this message before so I clicked Yes, and then I clicked OK on the warning dialog box that asked me to share it only with people I trust. After that the gmail app opened up which had a screenshot of my tablet, as well as a file attached to it called bugreport<some numbers, date and time I think>.txt. I did not send the bug report as I was not sure what it was and where it would go. However my question is,
what exactly is this bug report?
Is it generated by the code that I was testing? Or is it generated by the android system itself?
Did I trigger something unknowingly when I pressed the hardware buttons (the tablet only has 3 hardware buttons, volume up/down and power)?
I have been trying but I cannot make that message appear again, and when I search for bug*.txt using my file viewer app, I cannot find the file. Where is that .txt fil that got attached to the bug report get saved on my tablet?
It's because you have turned on USB debugging in Developer Options. You can create a bug report by holding the power + both volume up and down.
Edit:
This is what the forums say:
By pressing Volume up + Volume down + power button, you will feel a
vibration after a second or so, that's when the bug reporting
initiated.
To disable:
/system/bin/bugmailer.sh must be deleted/renamed.
There should be a folder on your SD card called "bug reports".
Have a look at this thread: http://forum.xda-developers.com/showthread.php?t=2252948
And this one: http://forum.xda-developers.com/showthread.php?t=1405639
Related
The MediaPad M3 does not log anything related to the app I am developing (compared to other Android devices). I understand that the log level usually can be set on Huawei devices via a hidden menu.
I came across these instructions many times while searching for the solution: https://gist.github.com/Shallong11/8403487
However, this is a tabled and it doesn't have GSM support and a Dialer / Phone application. So I fail at step one: dial ##2846579##.
Update #1: I've tried everything listed here: https://android.stackexchange.com/questions/59259/typing-dialer-secret-codes-in-devices-other-than-phones
Nothing works. The only reaction I've gotten: startActivity call with Intent.ACTION_DIAL is handled by Contacts app. Quite strange that there's a Contacts app but no Dialer...
It's probably meaningful to add that debug logs are displayed but stack traces of app crashes are not.
Update #2: I've also tried with some of these secret codes; nothing works: http://mobilespecs.net/phone/codes/Huawei/Huawei_MediaPad_M2.html
Because there is no dialer on the tablet, open calculator in landscape mode and enter
"()()2846579()()=" and the hidden menu should appear.
Here's a video demonstration.
Also please note that you'd need to restart the device afterwards in order for the changes to be applied.
I am developing an app using the TextToSpeech class. I'm getting this pop-up on Galaxy Note 4 (Android 5.0) when calling Android's TextToSpeech.speak(...) that asks if I want to download a better quality voice file:
High quality TTS Popup on Android 5, Galaxy S4
This didn't occur on the other development device, an ASUS tablet. How can I somehow prevent this popup from appearing when I use speech to text?
Searching around hasn't revealed much from a development perspective about this popup, or how to prevent it from appearing. I have checked here but it references recording audio and seems to reference a different issue: Android speech Recognition App Without Pop Up
On this particular device I could prevent it by simply accepting the download. That is evident from this, though I have not tried it: http://androidforums.com/threads/download-high-quality-voice-file.789236/ However, when installed on a new device, by the time the speech feature is enabled, the user may not have access to the device. It is a unique case, I suppose, violating normal guidelines for UI. Once the app starts, the user cannot be expected to interact with the app. It receives messages over the internet and speaks those, and this is when the popup appears.
I'm open to solutions that enable me to check and download the referenced high quality voice file myself (in order to prevent the popup, hopefully) and only start speaking once this is handled.
mTextSpeech.speak(s2, TextToSpeech.QUEUE_FLUSH, null);
EDIT:
Is there an INTENT sent somewhere in the loop that the Samsung package is responding to? My thinking is, I could check to see if the "offending" package causing the pop-up is in the PackageManager list, and then possibly go from there. Or if the package has been somehow registered with the system, maybe I could somehow un-register it? I admit I'm reaching here, but I'm sick of seeing this pop-up!
I just learned Android from scratch and built an app with simple process using Android Studio.
The app has one process with repeating Alarm manager which will toast a message after 10 mins. That's it.
However, once I install it on a real device, after an hour or so, the device will ask to Share Bug Report. When I do share it,(via e-mail to my self), it is just a blank black screen..!
This happens with any device. I tried it on 3 devices so far. It is like:
Device before my app: Normal functioning.
Device after installing my app (after an hour or 2): A pop up comes
up with 'Share bug report'.
PS: I have not written any code to call or share bug report or any popup.
Has anyone come across this strange behavior?? Any idea on what is happening here??
EDIT 1: It is not just a blank screen but there is a word doc with lengthy set of code. It basically contains the entire lump of data of entire system. Not just my app..!
Probably your app is freezing or stops responding.
Analyze your app logs, you will find the cause.
Did you read these threads ?
What does it mean with bug report captured in android tablet?
http://android-developers.blogspot.com/2010/05/google-feedback-for-android.html
I have noticed that the LOGCAT of my HTC One is getting flooded with messages from a "DropBoxManagerService" after I upgraded my device to Android KitKat 4.4.2.
I'm seeing this message repeated over and over again:
02-28 16:37:39.089 773-1376/? D/DropBoxManagerService﹕ Found time mapping 1393414988780 -> 1393414988780
It's outputting so fast that IntelliJ Idea's LOGCAT window is complaining: "Too much output to process". It can go on for hours before it settles down, and then starts again at some (apparently) arbitrary point in time.
I have tried to reset and disable the DropBox App, but it doesn't help. I'm suspecting this "infinite loop"-like behavior to be the culprit for a heavy battery drain issue, so I'm desperately trying to find a solution for the problem.
The service name is not getting listed by task-killer Apps.
Any good ideas are happily received!
I was told by a HTC Taiwan customer support manager that this is a bug of Google Play Service for Android 4.4.2 Kitkat, and all Android phone manufacturers like Samsung, Sony, etc. also suffers from this bug. (I wonder if it is true?) Please wait for update from Google.
I found this DropBoxManagerService message flooding bug will be triggered when there are new app updates available in Google Play Store. I can't see the update notification but my phone will become hot and battery drains fast. Reboot the phone will stop this flooding temporarily and Google Play Store will show update message immediately after reboot.
By the way, "Wipe cache partitions" does not work for me.
I tried reset htc one max to factory setting. It works.
The annoyed log will disappear.
You have to wipe the device's cache partition. After that the issue is solved as I noticed so far. No DropBoxManagerService flooding and no battery drain.
Hold power button and volume down key together until device powers off and you see black screen
Release power button only while you still keep holding down volume down key
Release volume down key when you see OS menu options
Use volume up/down keys to scroll and highlight "recovery" and press power button to select
When you see the icon that looks like a phone and orange "!" mark in a triangle, press power button and volume up key together once
It will display more options
Scroll to "wipe cache partitions" and press power button to select
Once wiping cache partitions is completed, select reboot
I'm noticing a strange behaviour when i plug in any android device to my computer.
It starts showing some messages in the LogCat in Eclipse as soon as i plug it in. Same thing with my HTC and ASUS tablet.
This has never happened before and I dont remember doing anything out of ordinary when I developed my app yesterday.
Any1 has an idea how to stop this ?
Thanks in advance
You can add filters to the logcat so that you only show relevant information.
From my experience it's perfectly normal for the logcat to start displaying messages as soon as you plug in a device. At the least it means it's working! ;)
However, once you start building and running your application and picking up errors the specific filter for your application will start displaying which will only show logs pertaining to your app.
It's set by default to switch to your app once an error displays, but you can change that default by going to Preferences > Android > LogCat and changing "Show logcat view..." from "Error" to "Verbose" or whatever works. That way it will switch to showing your application's logs faster. Beyond that, you can do further specific filters.
Hope that helps XD
This can't be stopped as such as the log cat in eclipse will retrieve anything where logging is being done of some sort whether it is an app, or android itself.
You can filter it, I think at the top of the log cat window there is a text field to only show log messages that contain a certain string and If I remember correctly there are also buttons to the right to only show error messages or warning or both etc.
I had the same problem with my Nexus 5. Eclipse wouldn't recognize the device, so I messed around with the device window a bit and then the log cat started to go crazy.
After several reboots, I un-checked the USB debugging option in the phone's Developer settings and re-checked it.
Problem solved.
I think something in the Device window changed when I performed this action, but I'm not certain.