So every time I try to take a screen shot(power/volume down), about 20 seconds later I get a notification that a bug report has been taken. When I try to send the bug report, it has no "to" in the recipient address. No clue what this is. Anyone else get this?
HyperM3 said:
So every time I try to take a screen shot(power/volume down), about 20 seconds later I get a notification that a bug report has been taken. When I try to send the bug report, it has no "to" in the recipient address. No clue what this is. Anyone else get this?
Click to expand...
Click to collapse
Yes, I do too. It's pretty annoying. Not sure why there is no "to" email present either.
Same issue here. Pixel XL 128 from Rogers in Canada. It's a minor annoyance. I just swipe the notification away now. I'm more annoyed by how tricky it is to take the screenshot in the first place.
Actually, since I posted this thread I haven't really gotten the bug oddly enough.
HyperM3 said:
So every time I try to take a screen shot(power/volume down), about 20 seconds later I get a notification that a bug report has been taken. When I try to send the bug report, it has no "to" in the recipient address. No clue what this is. Anyone else get this?
Click to expand...
Click to collapse
Same issues here, too.
Anyone has idea?
G-pixel said:
Same issues here, too.
Anyone has idea?
Click to expand...
Click to collapse
I notice if I hold both buttons down longer it doesn't happen.
When I was pressing the buttons quickly I would get the bug report notice, but after holding the buttons longer it wouldn't happen. That's what I have noticed.
I have to say since 7.1.1 I havent had this issue anymore and I take a lot of screen shots. For myself, I can consider this case closed.
I still constantly have issues with screenshots. Running 7.1.1 NMF26U on Verizon. It's very frustrating.
HyperM3 said:
So every time I try to take a screen shot(power/volume down), about 20 seconds later I get a notification that a bug report has been taken. When I try to send the bug report, it has no "to" in the recipient address. No clue what this is. Anyone else get this?
Click to expand...
Click to collapse
It's a feature not a bug. It's quite obvious what it's for and who said recipient would be.
Sent from my Pixel XL using Tapatalk
superchilpil said:
It's a feature not a bug. It's quite obvious what it's for and who said recipient would be.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yeah, like I mentioned though, it hasnt happened since the last 7.1.1 update for me.
I get the Bug report every time I take a ss. Running 7.1.1 NMF26U on Verizon as well.
Pixel XL screenshot
I'm running Android O Developer Preview 4 and I too still get this as well as no address to send the bug report too?
Try, for those who may still have the problem, power + vol up.
I don't know what it'll do, as in my mate 10 pro that takes a recording while in my 6t it takes a screenshot WITHOUT the bug report. (I have the exact same annoyance in my 6t with power + vol down, while the Huawei takes a screenshot, just as it should)
I have this problem now with every screenshot. It started when I I updated to android 10 on my Note 10+ how do I stop it?
noah_k_08 said:
I have this problem now with every screenshot. It started when I I updated to android 10 on my Note 10+ how do I stop it?
Click to expand...
Click to collapse
This is the Pixel XL thread, not Note 10+
My apologies. Was a little distracted when I posted and did not see.
Related
Hey everyone, I've been having a little bug that I noticed after I received the 4.0.4 update. I don't know what I exactly do to cause this but my nexus takes random screenshots whenever I press my power button to unlock my phone. I have the pattern lock that I use and when I hit power it randomly vibrates and when I go check my gallery it shows that I just took a screenshot. At times, when my battery is low it seems to randomly vibrate again and take a screen shot and gives me the prompt screen for which app I'd like to use to complete the action... No, I don't press the volume down key when this happens and no I don't have any screenshot apps. I'm stock, non rooted... Anyone else have this issue?
Stuck volume key?
adrynalyne said:
Stuck volume key?
Click to expand...
Click to collapse
I'm having doubts that it would be that...sometimes it does it even when I don't touch the power off key..
I have this same problem. I decided to find out what was going on when it asks what app to use, so I selected google drive. It uploaded the screenshot and a bug report to google drive. The bug report is a 3mb text file. I can't upload it here.
Same here with 4.0.4 IMM76I rooted,bootloader unlocked
Sent from my Galaxy Nexus using XDA
Do any of you guys run a rom that gives the ability to use the volume rocker to take screenshots? Have you tried reflashing your roms since you updated?
Sent from my Galaxy Nexus using Tapatalk 2
xterrain15 said:
I have this same problem. I decided to find out what was going on when it asks what app to use, so I selected google drive. It uploaded the screenshot and a bug report to google drive. The bug report is a 3mb text file. I can't upload it here.
Click to expand...
Click to collapse
Upload it somewhere and update your post with the link.
sent from my i9250
Posting the bug report
docs.google.com/open?id=0BxAJdhmCAyirSDU2UEU5dTRyQzg
There it is.
I am about to try flashing the 4.0.4 update again, as I just downloaded the zip of it.
Screenshots are Volume Down + Power. Bug Reports with screenshots are Both Volume Keys + Power. Do you have a case on? I've seen many people having these issues that were due to a tight fitting case.
Case
I do have a case on, but I know that's not the issue, as the power button is not covered, and this often occurs without me being anywhere near the power button. It can happen in the middle of typing out a text message. A prompt appears asking what application I'd like to complete this action with, and if I check the gallery later, there will be a new screenshot of my messaging app.
Slightly tangential - but is there any ROM or setting that will allow you to use a softkey to take screenshots? Or do I need to just search out an app that'll do so?
I find it really awkward (at least with my case on) to take screenshots and wouldn't mind the ability to do it with a softkey instead.
ceribaen said:
Slightly tangential - but is there any ROM or setting that will allow you to use a softkey to take screenshots? Or do I need to just search out an app that'll do so?
I find it really awkward (at least with my case on) to take screenshots and wouldn't mind the ability to do it with a softkey instead.
Click to expand...
Click to collapse
AOKP allows you to set up any functions/icons to softkeys
Sent from my Galaxy Nexus using xda premium
nirco68 said:
Same here with 4.0.4 IMM76I rooted,bootloader unlocked
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I have the exact same problem! No clue what's causing this. I'm on AOKP M5 on rooted Galaxy Nexus. I can't find any setting to disable bug report creation, nor can I find anything about bug reports in the settings at all. I really hope someone can figure out what's causing these spontaneous bug reports (plus screenshots) to be generated.
Same issue
I just received my 4.0.4 update on Galaxy Nexus, and I am having the same issue. It randomly takes a snapshot of the lock screen and generates a bug report. Have they added some new hardkey combination that is too easy to trigger? I do have a case on, but I have always had it on, way before the update.
This is a manual bug report triggered by pressing both volume keys and the power button at the same time. It will vibrate once when you do it and then it takes a good minute or two for it to compile the report. The phone will then vibrate 3 times quickly when the report is ready, but only if the phone is awake and unlocked. So, for example, if you hit the power button to check the time and happen to press all three buttons or your TPU case (just an example) is holding down your volume buttons, then it will trigger then. You won't actually see the results until the next time you unlock the device. They are addressed to your default email address unless your ROM developer adds an email to them. Obviously being stock this would not be the case.
If you want to get rid of this feature, go to /system/bin and rename bugmailer.sh to bugmailer.sh.bak or delete it. Then reboot and no more bugmailer.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
chandradithya said:
This is a manual bug report triggered by pressing both volume keys and the power button at the same time. It will vibrate once when you do it and then it takes a good minute or two for it to compile the report. The phone will then vibrate 3 times quickly when the report is ready, but only if the phone is awake and unlocked. So, for example, if you hit the power button to check the time and happen to press all three buttons or your TPU case (just an example) is holding down your volume buttons, then it will trigger then. You won't actually see the results until the next time you unlock the device. They are addressed to your default email address unless your ROM developer adds an email to them. Obviously being stock this would not be the case.
If you want to get rid of this feature, go to /system/bin and rename bugmailer.sh to bugmailer.sh.bak or delete it. Then reboot and no more bugmailer.
Click to expand...
Click to collapse
While I appreciate the fact that you are helping out, please do not take my responses from another forum and paste them here verbatim as your own.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
Also of note for those having the issue on the 4.0.4 update, disabling USB debugging should now also disable the bugmailer.
Sent from my brain using human to phone transport technology.
ABQNM said:
While I appreciate the fact that you are helping out, please do not take my responses from another forum and paste them here verbatim as your own.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
Also of note for those having the issue on the 4.0.4 update, disabling USB debugging should now also disable the bugmailer.
Sent from my brain using human to phone transport technology.
Click to expand...
Click to collapse
No offence to you. Seriously.
was annoyed with this issue, google searched it , opened a lot of tabs, found many posts never had answers,
I agree it was copy paste, sorry for not mentioning the source.
I edited them and linked it to your post on rootzwiki,
I was in a hurry then and rushed up and pasted on the threads where there was no proper answers.
I have the same problem
Hello guys.
I have the same problem. I have the Android 4.2 original from Google. I have the issue from Android 4.1 and I don't know what is the problem.
Drakonworld said:
Hello guys.
I have the same problem. I have the Android 4.2 original from Google. I have the issue from Android 4.1 and I don't know what is the problem.
Click to expand...
Click to collapse
See my full explanation here http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123 (last post on the page). Simple answer, something is pressing all three buttons at once, be it a case or whatever. Either disable usb debugging to turn it off or see my link for instructions to disable just the bugmailer.
Sent from my brain using human to phone transport technology.
Can anyone check if your camera recording got darker after 2.22 firmware update or arhd 10.2 in low light situations..... Picture quality is still great but when I try to record in low light it sucks so bad..... It doesn't adjust to it.....
Anyone
Same problem. Annoying!
helispot said:
Same problem. Annoying!
Click to expand...
Click to collapse
You have the same issue as someone who posted over a year ago, on software/firmware (2.22) that is two generations old at this point?
I can't say for sure if the problem started during the some update, but for a while now, I've been experiencing the same issues as the OP. Seemed to start roughly around the same time as the OP, too.
helispot said:
I can't say for sure if the problem started during the some update, but for a while now, I've been experiencing the same issues as the OP. Seemed to start roughly around the same time as the OP, too.
Click to expand...
Click to collapse
The camera app has been updated several times since the time of the OP. Don't know if it will help your issue or not, but at least a start to see if your camera app is up to date. Current version is 7.30.581119
That's the exact version that I have.
The newest problem, just started maybe a couple of months ago, is that I'll open up the camera app, the shot looks beautiful on the screen, I hit the "video record" button to start, and the camera "stops down" to an unrecognizable dark image before recording. Annoying!
Ok, so three times now, I get an indicator in my notification bar that there is a bug report. I press it and it opens gmail, and has 2 attachments. But it wants to send the email to my self. To whom should these bug reports be sent to?
[email protected]
Just to bump this back up. I'm still getting bug reports generate. Not certain which app is the problem yet. But when I select share, the email puts my email in the send to. Has anyone else received bug reports?
Yeah, I've been getting them occasionally (but steadily) too.
Me too, daily bug reports being generated with no way of submitting them to anyone?
I ended up doing a factory reset a couple of weeks ago, and I haven't gotten a single bug report since. so, I don't know if the out of box experience had a bug, or something I had installed.
Me too. FWIW, the culprit was HD Widgets. Switched to Beautiful Widgets and bug reports stopped.
Sent from my HTC 10 using XDA-Developers mobile app
I don't have HD widgets and I'm still getting bug reports almost daily which is annoying, no idea what is generating them and I really don't want to have to factory reset and lose all my game data
again
Do you use some apps control the screen lock?
Same issue here, factory reset didn't resolve.
Maybe one of the trusted devs here would be willing to look over the logs and pinpoint the culprit.
ufkal said:
Ok, so three times now, I get an indicator in my notification bar that there is a bug report. I press it and it opens gmail, and has 2 attachments. But it wants to send the email to my self. To whom should these bug reports be sent to?
Click to expand...
Click to collapse
Hey can you test this for me? Turn screen off and press volume up+down and release. Did it do a weird vibration? Then a few seconds/minutes later generate a bug report?
Sent from my HTC 10 using XDA Labs
I can tell you now that pressing both vol up and vol down at the same time is indeed what causes it. HTC has built that into their phones to generate bug reports. It's been that way since the M8 and maybe longer. I agree, it is annoying.
The next release of Viper 10 ROM that will come out this weekend (probably) has removed that function. You'll still get the haptic feedback when the buttons are pressed together, but the bug report won't be generated.
xunholyx said:
I can tell you now that pressing both vol up and vol down at the same time is indeed what causes it. HTC has built that into their phones to generate bug reports. It's been that way since the M8 and maybe longer. I agree, it is annoying.
The next release of Viper 10 ROM that will come out this weekend (probably) has removed that function. You'll still get the haptic feedback when the buttons are pressed together, but the bug report won't be generated.
Click to expand...
Click to collapse
I had the m8 for a very long time and never noticed this. Lol glad I found the culprit though!
Sent from my HTC 10 using XDA Labs
Maybe it's just the screen protector, I know I've read some stuff about the screen protector and people rooting and flashing something, but I swear this thing doesn't respond to my touch. I'm on Android p DP 2 and just factory reset it to see if it helps with some app bugs. Just swiped up 7 times before it went up so I could type my pin in, this has been an issue with this particular device.
kickenwing13 said:
Maybe it's just the screen protector, I know I've read some stuff about the screen protector and people rooting and flashing something, but I swear this thing doesn't respond to my touch. I'm on Android p DP 2 and just factory reset it to see if it helps with some app bugs. Just swiped up 7 times before it went up so I could type my pin in, this has been an issue with this particular device.
Click to expand...
Click to collapse
I have noticed this sometimes as well on DP2. I have a fingerprint setup but my phone is usually lying on my desk so i swipe up and enter the pattern. Sometimes it just refuses to swipe up and stay there.. its sort of bounces back down. I have to pick up the phone and use the fingerprint scanner.
They lock screen swipe issue was fixed for me recently on a security update but on dp2 sometimes it's worst then it ever was before the fix.
Just tap the lock, no need to swipe
Ah never noticed that. If you have the fingerprint enabled, tap the fingerprint icon.
akellar said:
Just tap the lock, no need to swipe
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
akellar said:
Just tap the lock, no need to swipe
Click to expand...
Click to collapse
And this is why you're a senior member, that's pretty helpful. Now swiping away notifications would be wonderful
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
skimminstones said:
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
Click to expand...
Click to collapse
Are they not allowed to test and provide feedback? Why does it bother you?
Anyways, to be fair, I've been experiencing this issue off and on ever since I purchased the phone. And no, I'm not running beta firmware.
Why does it bother you if I comment?
If you're running a version of Android that hasn't been officially released yet then there is always going to be issues. That's pretty obvious frankly.
The lockscreen swiping is definitely an issue with the Pixel 2 XL. I always had this issue on Oreo but on P DP2 it's gone. It's interesting how it's the opposite for others in this thread.
Even on Oreo, it's hit or miss.
Swiping away notifications almost always takes at least 2-3 tries.
Super annoying for a phone this expensive.
E30Nova said:
Even on Oreo, it's hit or miss.
Swiping away notifications almost always takes at least 2-3 tries.
Super annoying for a phone this expensive.
Click to expand...
Click to collapse
Oreo Lock Screen Fix (Substratum) from Arol Wright fixed it for me.
skimminstones said:
Why does it bother you if I comment?
If you're running a version of Android that hasn't been officially released yet then there is always going to be issues. That's pretty obvious frankly.
Click to expand...
Click to collapse
You seem very passionate about this issue so let me clarify... It's been an issue the entire life of this phone ON ANY AND ALL SOFTWARE.
skimminstones said:
amazes me that people run essentially a beta version of the software and complain when things arent working correctly.
Click to expand...
Click to collapse
To be fair....even before I jumped on dp2....I had these same lockscreen issues on Oreo. It's just worse on dp2.
kickenwing13 said:
You seem very passionate about this issue so let me clarify... It's been an issue the entire life of this phone ON ANY AND ALL SOFTWARE.
Click to expand...
Click to collapse
Nope, No issues on mine
Yeah the swipe up issue definitely does happen once in a while for me but it's not often or consistent. Now that I know the tap the fingerprint/lock does the same thing, I just do that.
Sent from my Pixel 2 XL using Tapatalk
No issues here. If i'm looking for perfection ill go purchase one of those $25,000 phones and even then you'll find something wrong.
after each lock when i turn the screen on with double tap or power button screen is unresponsive for good 3 seconds. This started happening after the latest camera fix update. When if i use aod and use the fingerprint through the aod this doesnt happen. tried reboot and factory reset with fresh install (no backups) tried safe mode. Same thing happens.
S20 plus exynos.
Yup happening to me too (s20+ exynos). For me the time of unresponsiveness is around 1-2 seconds. Happened after the latest update.
Yes, have been facing the same issue since "ATCH" update.
Yeah has been driving me nuts. Same problem.
I'm surprised this isn't gaining more traction? Can't be the only few experiencing this!?
Glad to see it's not only my device. Waiting for fix.
I have similar situation
I'ne noticed the same after the last update.
Chris_c81 said:
Yeah has been driving me nuts. Same problem.
Click to expand...
Click to collapse
Seriously when it happens(which it does like 90% of the time i wake the screen) i feel like i'm using a cheap 100$ phone and not a 1000$+ flagship.
Chris_c81 said:
I'm surprised this isn't gaining more traction? Can't be the only few experiencing this!?
Click to expand...
Click to collapse
This. I'm afraid if it goes unnoticed by samsung we may have to face this issue for longer.
BTW any user here with Snapdragon that has this issue. Or is this exynos only ?
anfederin said:
I have similar situation
Click to expand...
Click to collapse
Mine is Exynos
sjandroiddeveloper said:
Seriously when it happens(which it does like 90% of the time i wake the screen) i feel like i'm using a cheap 100$ phone and not a 1000$+ flagship.
This. I'm afraid if it goes unnoticed by samsung we may have to face this issue for longer.
BTW any user here with Snapdragon that has this issue. Or is this exynos only ?
Click to expand...
Click to collapse
Is there any channel to communicate this bug to Samsung? Anyone know?
Chris_c81 said:
Is there any channel to communicate this bug to Samsung? Anyone know?
Click to expand...
Click to collapse
There is an app called samsung member where you can send error reports. I have already done it, its currently under review. I suggest everyone affected to do it.
sjandroiddeveloper said:
There is an app called samsung member where you can send error reports. I have already done it, its currently under review. I suggest everyone affected to do it.
Click to expand...
Click to collapse
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
turn off the battery optimized for apps: com.samsung.android.biometric.
Go to Settings>Apps>Select "Special Access" from three dot menu>Optimise Battery Usage>select All from drop down menu>Search for "com.samsung.android.biometric"> Turn it off and Restart.
Click to expand...
Click to collapse
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
Did accordingly as above.
For a moment it felt like the issue is resolved!
But after checking several times I can confirm the issue still exists.
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
Unlock is now super faster. Issue is completely gone. Thanks [emoji4]
Sent from my SM-G986B using Tapatalk
verynuclear said:
Unlock is now super faster. Issue is completely gone. Thanks [emoji4]
Click to expand...
Click to collapse
While using the sidekey and turning off and on the screen and checking consecutively, the unresponsiveness persists in mine.
Virgo_Guy said:
While using the sidekey and turning off and on the screen and checking consecutively, the unresponsiveness persists in mine.
Click to expand...
Click to collapse
Have you restarted the phone? It didn't work until I restart mine.
Sent from my SM-G986B using Tapatalk
verynuclear said:
Have you restarted the phone? It didn't work until I restart mine.
Click to expand...
Click to collapse
Ofcourse I did. In fact restarted one more time since it didn't resolve after the first restart, post disabling the optimization.
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
I did this already and while it feels like fingerprint is faster, unfortunately this is a screen issue. You see if the screen is off and i put the finger in the correct spot it always scans my finger without any lag. The issue is occurs when -
a) I have unlocked the phone using above way, then the screen becomes unresponsive right after unlocking.
b) The screen is off and i either press the power button or double tap to wake, then the screen will be unresponsive and its during this time the fingerprint scanner doesn't scan (because the scanner doesn't know it needs to scan since the touch is unresponsive)
so TL;DR its not a FP scanner issue.
I am quiet sure Samsung is already addressing this issue for next update.