Database Info

Screen shot problem? After tmo update

Anyone with a tmo sensation having a screen shot problem?! Like everytime I hit the home it would take a screen shot, I thought if you press home and power, then it would take the shot?.. anyone else have a problem with that?

my brother was having that problem. if it happens, try hitting the back button & see if it stops after that. apparently the phone is thinking that home is still being held down or something like that.

Same thing is happening here...super annoying. Any ideas on a fix anybody?

I just used the screenshot feature (hold power down and then tap home) for the second time tonight without any problems. Yes, I do have the T-Mobile update too.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

The problem is sometimes when we press the home button it takes a screen shot and doesn't go home unless we press back and then home again :/

Ah, I see. Reading comprehension fail. -_-"

i have that problem on revolution hd 3.0 rom, (based on the new update.)
usually just go to my lockscreen and come back to fix it, but its annoying. it happened about 5 times in the last week or so.

I was just about to post this issue. Good thing i found it.
This keeps happening to me all the time.
I keep having to delete 20 screenshot a day.
Any fixes?

Bkz Bubba said:
I was just about to post this issue. Good thing i found it.
This keeps happening to me all the time.
I keep having to delete 20 screenshot a day.
Any fixes?
Click to expand...
Click to collapse
Haven't found one yet :S

Yeah, sometimes the phone takes a screenshot for no reason. It only happened to me 2-3 times though.

Glad that I'm not the only one with this problem. Good feature but So annoying to keep taking screenshots every time you press home..

My wife is having the same problem. She applied the OTA update and it will now randomly take screenshots when she presses Home. Not sure what the setting is to disable the feature, but if anyone knows where it is that would be of great assistance. She has no need for this.
Sent from my HTC Sensation Z710e using XDA App

A buddy at work asked me about this today to, wanted to subscribe and keep this thread going. Hopefully the culprit will be found and dealt a swift fair well

Temporary Fix
I found a way to temporarily fix the screenshot problem once it suddenly starts doing it. Note, this doesn't SOLVE the problem, it's simply a work around for each time it happens:
Press the Home button and Lock button at the same time and it somehow tricks the phone back to recognizing you're not pressing both when you are only pressing the Home button.
If it doesn't work after doing it once, try doing it again a couple times and it should make it stop taking Screenshots each time you only press the Home button.
Simply just pressing the back button a bunch of times didn't do the trick for me.
Hope this helped someone? It definitely saved me the stress of restarting my phone about once an hour...

^ I have done that to.. just annoying and makes my phone feel like s**t.. hope there's a fix soon..

Ok so I found a solution to it. You can do the power+home to take a screenshot, but don't lock your phone with the power button, seems to work ok!!

808HD2 said:
Ok so I found a solution to it. You can do the power+home to take a screenshot, but don't lock your phone with the power button, seems to work ok!!
Click to expand...
Click to collapse
Dont understand, So how do we lock our phones?

808HD2 said:
Anyone with a tmo sensation having a screen shot problem?! Like everytime I hit the home it would take a screen shot, I thought if you press home and power, then it would take the shot?.. anyone else have a problem with that?
Click to expand...
Click to collapse
Having the same problem. So very annoying! Also related to the issue whereby the screen lights up again a few seconds after turning it off with the power button. Very annoying and never happened in 2.3.3.

Bkz Bubba said:
Dont understand, So how do we lock our phones?
Click to expand...
Click to collapse
You still lock your phone with the lock button, you just press Lock + Home button a couple times to get your phone to stop taking screenshots. Once you do that, you don't need to continually press them at the same time to lock your phone. It just stops your phone from taking the screenshots when you happen to only be pressing the Home button.

The only "fix" I've found is to delete the screenshot line from the build.prop and use drocap for screenshots. no biggie.

[Q] How to contact Samsung

I've wasted an hour at the Samsung website. When the chat turned out to be broken the send button didn't,t work, I tried email. After answering all the same questions, model etc, the drop down for model wouldn't work. It's a required field so again, i'm stuck. Does anyone know how to reach them?
i received a galaxy note 10.1 16 gig wi-fi only for Christmas. it was terrific until yesterday morning. I took it from my padded brief case, pressed the start button and nothing happpened. I assumed I'd left it on overnight and rrun the battery down. I just put it away until i went home to charge it. I left it on the charger for a couple of hours. When i again pressed the start buttton, still nothiing. What do i do next?

Try leaving it charging for 6+ hours. Make sure it's plugged in all the way on both ends of the usb cable.

mtcstle said:
I've wasted an hour at the Samsung website. When the chat turned out to be broken the send button didn't,t work, I tried email. After answering all the same questions, model etc, the drop down for model wouldn't work. It's a required field so again, i'm stuck. Does anyone know how to reach them?
i received a galaxy note 10.1 16 gig wi-fi only for Christmas. it was terrific until yesterday morning. I took it from my padded brief case, pressed the start button and nothing happpened. I assumed I'd left it on overnight and rrun the battery down. I just put it away until i went home to charge it. I left it on the charger for a couple of hours. When i again pressed the start buttton, still nothiing. What do i do next?
Click to expand...
Click to collapse
can you enter recovery or download mode?.. if not then you should be worried.......
Sent from my GT-N8000 using Tapatalk HD

mtcstle said:
I've wasted an hour at the Samsung website. When the chat turned out to be broken the send button didn't,t work, I tried email. After answering all the same questions, model etc, the drop down for model wouldn't work. It's a required field so again, i'm stuck. Does anyone know how to reach them?
i received a galaxy note 10.1 16 gig wi-fi only for Christmas. it was terrific until yesterday morning. I took it from my padded brief case, pressed the start button and nothing happpened. I assumed I'd left it on overnight and rrun the battery down. I just put it away until i went home to charge it. I left it on the charger for a couple of hours. When i again pressed the start buttton, still nothiing. What do i do next?
Click to expand...
Click to collapse
Call them. Very easy to reach by phone.

toenail_flicker said:
Call them. Very easy to reach by phone.
Click to expand...
Click to collapse
Does anyone know a phone number? That's one thing that's not on the website.
To answer the previous question, no it won't boot into download or Recovery.
I'll try the six hour charge, but I'm not hopeful.
Stay tuned for more on ...

mtcstle said:
Does anyone know a phone number? That's one thing that's not on the website.
To answer the previous question, no it won't boot into download or Recovery.
I'll try the six hour charge, but I'm not hopeful.
Stay tuned for more on ...
Click to expand...
Click to collapse
I found 1-800-SAMSUNG somewhere. It's seven digits I thought so, what the heck. Well a very nice woman talked me through all the trouble shooting steps I'd already tried. But, then she gave me an RMA and emailed me a shipping label. So far so good then. More to follow.

Before you write it off as dead, may I make a suggestion. Keep a finger on the touch screen while pessing the power button. This solution works for me when I've experienced the "sleep of death" after upgrading my GN 8013 to JB. Holding down the power button on mine didn't do anything. I found the solution I mentioned when I began googling in a panic. After removing one offending app, this awful sleep mode that resembles a dead device hasn't occurred again. Maybe you have an app that's triggered this. Good luck.

mke1973 said:
Before you write it off as dead, may I make a suggestion. Keep a finger on the touch screen while pessing the power button. This solution works for me when I've experienced the "sleep of death" after upgrading my GN 8013 to JB. Holding down the power button on mine didn't do anything. I found the solution I mentioned when I began googling in a panic. After removing one offending app, this awful sleep mode that resembles a dead device hasn't occurred again. Maybe you have an app that's triggered this. Good luck.
Click to expand...
Click to collapse
What was the offending app?

If all else fails, try the old fashioned way
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Riki1kenobi said:
What was the offending app?
Click to expand...
Click to collapse
It was Sipdroid. (Knock on wood) deleting it has stopped my note from going into the sleep of death. Fortunately, the voip app csipsimple is very stable on JB 4.1.2 and has no audio or registreation issues so I've still got voip on my note.

Pixel 2 while powered off gets stuck on charging splash screen - won't turn on

I previously had an issue with this which was solved by re-flashing, unfortunately this isn't helping this time.
So as far as I can tell things work properly with the following exception.
When I power off the phone and leave it in to charge I get stuck on the black and white lighting battery screen. The screen stays on indefinitely. The phone will not power on except for a soft reset which then boots the phone.
For clarity this is what the phone looks like ... it just never turns the screen off.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks.
- JasonVaritekMVP

Only other detail I have to add is that the charge screen works correctly after a flash-all. It is the process of installing twrp and then Magisk that seems to be borking the charge screen.

JasonVaritekMVP said:
I previously had an issue with this which was solved by re-flashing, unfortunately this isn't helping this time.
So as far as I can tell things work properly with the following exception.
When I power off the phone and leave it in to charge I get stuck on the black and white lighting battery screen. The screen stays on indefinitely. The phone will not power on except for a soft reset which then boots the phone.
For clarity this is what the phone looks like ... it just never turns the screen off.
Thanks.
- JasonVaritekMVP
Click to expand...
Click to collapse
Did you ever find a fix for this? My Pixel 2 XL does it as well!

MRL3GS said:
Did you ever find a fix for this? My Pixel 2 XL does it as well!
Click to expand...
Click to collapse
So this issue popped up for me when Magisk v17.0 came out and v17.1 didn't seem to fix it. Re-flashing did solve the problem but every time I tried to re-root the issue came back. Something about the latest Magisk and my flashing was causing the problem. I tried going back to earlier working versions of Magisk such as 16 and 16.5 but none of them seemed to work, whatever it was it stuck.
I finally ended up flashing the latest Pie along with the latest Magisk and that together allowed me to flash, root and solve the problem. I have not attempted to go back to Oreo.
Hope this helps.
- JasonVaritekMVP

this just happened to me. how do i fix this? I just want the thing to power up. I just got done using it. picked up phone and it was powered off.....
edit: phew. i panicked when i saw this. I just held the power button and it shut off. turned it back on and it booted up....had 2% battery. i guess it was just a low battery this time.

have the same issue too. Only happens when the phone dies after running out of juice. Hard reset reboot and boots up right back up afterwards. Also rooted with magisk 17.1

hard reset? like you lose everything? that sucks. im on 17.3 magisk.

psycho_maniac said:
hard reset? like you lose everything? that sucks. im on 17.3 magisk.
Click to expand...
Click to collapse
whoops, i meant hard reboot. Pressed and held the power button for 5+ seconds and it booted right back up.

eneka said:
whoops, i meant hard reboot. Pressed and held the power button for 5+ seconds and it booted right back up.
Click to expand...
Click to collapse
yup. thats what i did too. mine was due to low battery

Anyone figure this problem out? I've had this problem for a while now. It was doing this a few months ago then I reflashed magisk and it went away. I did a monthly update a month later and it came back and I've tried a factory reset...reflashing etc.. Nothing helps. It only happens if the phone dies or you power it off. I'm not using TWRP... It's a magisk manager direct install. Thanks!

fastracer said:
Anyone figure this problem out? I've had this problem for a while now. It was doing this a few months ago then I reflashed magisk and it went away. I did a monthly update a month later and it came back and I've tried a factory reset...reflashing etc.. Nothing helps. It only happens if the phone dies or you power it off. I'm not using TWRP... It's a magisk manager direct install. Thanks!
Click to expand...
Click to collapse
I've also had this issue since I bought the phone 2nd hand last June. I don't recall if it happen before rooting or not. The only pattern(?) I have noticed is that when I let the phone die completely, theres a chance when I plug it into the charger, it might get stuck on the screen as OP showed. However, as others noted, I think holding down the power button shuts the phone completely down again. Occasionally either I'm doing something wrong or the phone doesn't register the button presses all the time. In past I also tried holding the power button and volume down at the same time but I'm assuming the phone picked it up as me just holding the power button down or maybe that combo also works.

OnePlus 6 hard bricked. Need help.

I belive my 1+ 6 somehow got bricked. I didn't root it, I didn't unlock the boatloader, I didn't put any custom ROMs, everything was stock. I went to bed like usual, and left the phone charging. Around 1 hour later, I woke up, the screen was on
Your device is corrupt. It can't be trusted and may not work properly. Visit this link on another device: g.co/ABH
PRESS POWER KEY TO CONTINUE.
I was half asleep, I restarted the phone, everything was back to normal and I thought that was the end of it. Woke up late in the morning, confused, because my alarm didn't ring. My phone was dead, wasn't turning on, it wasn't doing anything. It was charged when I restarted it last night (75%). I tried every single combination of buttons, I couldn't get it to boot into Fast Boot, nothing was working.
In the morning, I tried using the Msm tool, but it always got stuck at 'Memory size: 119.19G' after 13 seconds.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I gave up, and tried to turn on the phone a few hours later. It turned on, and I got that message again, that your device is corrupt. Pressed the power key, and it started just fine. It restarted afterwards, and was booting to fast boot menu. No matter what I tried, it was always going to the fast boot menu.
I tried the Msm tool, and this time I got past that stage. But, this time around, it got stuck at downloading system.img to system_a (I left it there for 40 minutes), until I closed everything and tried to restart the procedure.
Now I'm back to square 1, phone won't turn on, won't vibrate and will be stuck at Memory size stage.
Please help me out, I'm really desperate...

try other rom in msmdownloadtool, i give you a link to OxygenOS 9.0.2 MSMDownloadTool v.4.058:
https://mega.nz/#!NEEEgCCJ!Wuo2tw3ehnnKhcGQEc5fMXPNZdqJO_IT5suVrCHD1UY
drivers:
https://androidfilehost.com/?fid=24052804347798730

This is what I am getting now

Do you have another usb to type-c cable for try?

Tried 3 more cables, and 2 other USB ports, same results. Will have to try it tomorrow, again, on a different machine, but I am doubtful it's going to make any difference.
Any other ideas? Thank you!

try disabling the sha256 check, perhaps you can flash it with errors but your phone boot, seems an internal damage, i never had issues with msmdownloadtool

try a different version of the program and see if a reboot works. This program saved my phone also 2 weeks ago and i thought i was hard bricked also because my phone showed there was no recovery/fastboot and bootloader and at first the program didn't work like it should and after a reboot of the pc and then starting the app and then do the correct button combination so that the led light on the phone will turn yellow i believe and then start the process.

This sounds like a hardware failure, send the phone to oneplus.

Try to contact OnePlus service, I had a very similar problem to my 5T and they solved it via remote desktop.

Press volume up for 5 seconds then plug the device into your laptop. It should be detected as COM3 and the MSM download tool should detect the device.

dragos281993 said:
Press volume up for 5 seconds then plug the device into your laptop. It should be detected as COM3 and the MSM download tool should detect the device.
Click to expand...
Click to collapse
The device, as mentioned in the initial post, is detected by the MSM tool, however, after I press start, I get hit with an error every time
I have contacted OnePlus, and they said that they no longer do remote fixes, as they used to.

For my past experience, You have to log in EDL mode instead fastboot for flashing through msntool.

DurDom said:
The device, as mentioned in the initial post, is detected by the MSM tool, however, after I press start, I get hit with an error every time
I have contacted OnePlus, and they said that they no longer do remote fixes, as they used to.
Click to expand...
Click to collapse
Sir, did you solve the problem?

Sounds like an actual hardware issue if this happened on a stock device out of the blue. Contact OnePlus and hopefully they can make it right.

SOCOM-HERO said:
Sounds like an actual hardware issue if this happened on a stock device out of the blue. Contact OnePlus and hopefully they can make it right.
Click to expand...
Click to collapse
It was a stock device. Apparently the memory went bad out of nowhere, and the motherboard had to be replaced.

Did they replace MoBo for free? I have the same issue

Did you manage to get your phone working again? My onePlus 6 died on me last week too.
It was updated to 11.1.1 a few weeks ago.
Last week while idly scrolling social media, the phone froze, turned off, and when it turned back on, it displayed Qualcomm crashdump mode.
I've been running the MsmDownloadTool, and for the past 55 minutes it's been stuck in "Downloading system.img to system_a".
Not sure how to proceed from here.

3 Short beeps at almost random time on Samsung Android

Hi All,
I'm quite desperate here, and I fear the full wipe of my phone
Context :
- I have a Galaxy Z Flip 4 that has been recently updated to Android 13 + UI5
- No NFC elements near the phone
- Bluetooth linked with my galaxy watch 5 pro
- My issue happens for 2 weeks now
Issue :
Most of the time randomly my phone is making a sound of 3 very close beeps
There is no notification after that, even in the notification history inside settings of the phone
I do not recognize a specific pattern for my issue as it is random but since a few days it is doing it at 6:55 am (happened 2 times)
I don't think it is happening when my phone is in silent mode of DND
What I did :
Remove some app, deactivating NFC, deactivation emergency alerts, removing roaming, removing data on my second sim, removing the notification reminder, reboot the phone in safe mode
Do you know why it is happening ?
Thank you all in advance

Macadam75 said:
Hi All,
I'm quite desperate here, and I fear the full wipe of my phone
Context :
- I have a Galaxy Z Flip 4 that has been recently updated to Android 13 + UI5
- No NFC elements near the phone
- Bluetooth linked with my galaxy watch 5 pro
- My issue happens for 2 weeks now
Issue :
Most of the time randomly my phone is making a sound of 3 very close beeps
There is no notification after that, even in the notification history inside settings of the phone
I do not recognize a specific pattern for my issue as it is random but since a few days it is doing it at 6:55 am (happened 2 times)
I don't think it is happening when my phone is in silent mode of DND
What I did :
Remove some app, deactivating NFC, deactivation emergency alerts, removing roaming, removing data on my second sim, removing the notification reminder
Do you know why it is happening ?
Thank you all in advance
Click to expand...
Click to collapse
@Macadam75 Try the following steps to fix your problem (boots into safe mode and then into a regular boot):
1. Power on your device (if it isn't).
2. Hold the power button.
3. Hold the power symbol for 5 seconds.
4. Click the power symbol.
5. Wait until it is booted.
6. Hold the power button.
7. Double click the power symbol to turn it off as you normally would do.
8. Hold the power button to turn it on.
Kaboom! The issue should be resolved. There was an ongoing discussion on the Samsung Members community and many people fixed it with this.

Hello, Thanks for the feedback
I did the process you shared yesterday, and it did it again today at 6:57 AM and 1-2 hour later
Can you please share the link on the Samsung Members community, so I can check if it is the exact same issue ?

Macadam75 said:
Hello, Thanks for the feedback
I did the process you shared yesterday, and it did it again today at 6:57 AM and 1-2 hour later
Can you please share the link on the Samsung Members community, so I can check if it is the exact same issue ?
Click to expand...
Click to collapse
Yes, here it is: https://www.google.com/url?sa=t&sou...EQFnoECBUQAQ&usg=AOvVaw1oNsUTxdbBTWPzvB8Xb-Um
It is for S8, but I think it could be for any device.

Thanks again
I don't think it is the same issue.
In my side, this is a triple beep with no notification in random time during the day and regularly around 7AM.
I did reboot again in safe mode twice to be sure, but I have no clue why it is happening

Also don't know. Maybe a bit more of research?

Minionguyjpro said:
@Macadam75 Try the following steps to fix your problem (boots into safe mode and then into a regular boot):
1. Power on your device (if it isn't).
2. Hold the power button.
3. Hold the power symbol for 5 seconds.
4. Click the power symbol.
5. Wait until it is booted.
6. Hold the power button.
7. Double click the power symbol to turn it off as you normally would do.
8. Hold the power button to turn it on.
Kaboom! The issue should be resolved. There was an ongoing discussion on the Samsung Members community and many people fixed it with this.
Click to expand...
Click to collapse
Hit did happen multiple time today, even the app nice catch does not get why this beep is coming fromp

Macadam75 said:
Hit did happen multiple time today, even the app nice catch does not get why this beep is coming fromp
Click to expand...
Click to collapse
You are really sure it is your phone? I almost get the feeling it is something else that is making these beeps.

Minionguyjpro said:
You are really sure it is your phone? I almost get the feeling it is something else that is making these beeps.
Click to expand...
Click to collapse
Ow yes I'm quite sure, I just had it a few seconds ago

Weird. I think you keep factory reset as last option?

Minionguyjpro said:
Weird. I think you keep factory reset as last option?
Click to expand...
Click to collapse
I think that I have no choice.

IMO they aren't random. They are purposeful….like most things on the phone.
3 short beeps mean the call was dropped or failed.

xXx yYy said:
IMO they aren't random. They are purposeful….like most things on the phone.
3 short beeps mean the call was dropped or failed.
Click to expand...
Click to collapse
In my case this is not related to a call but completely random and for sure once in the morning.

Macadam75 said:
In my case this is not related to a call but completely random and for sure once in the morning.
Click to expand...
Click to collapse
@Macadam75 WAIT A MINUTE, I got an Android 13/OneUI 5.0 update 2 days ago, and I saw there was a new app called 'Modes and Routines', and I saw that you could make an action at a certain time which runs an beep. Will show a screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
'Een piepsignaal' means a beaping sound in my language.

Thanks for keeping my feed alive
can you please do the screenshot in english as I really don't know what the menu you show is.
To end my nightmare I did a full wipe and no issue for the moment, I removed double sim as well

Macadam75 said:
Thanks for keeping my feed alive
can you please do the screenshot in english as I really don't know what the menu you show is.
To end my nightmare I did a full wipe and no issue for the moment, I removed double sim as well
Click to expand...
Click to collapse
That's nice. Here are the screenshots in English: