Database Users

Can't pick up the phone! Anyone else?

Well, thats it, I actually can't pick up my phone when I get a call. I can push the green pick up button as many times as I want, but it wont respond, and I end up having to call people back. Anyone else with this issue? (phone info in sig)

I am only going to take a guess and say that you have a lot of programs that run in the background.
Maybe try not using auto rotate.

I agree with Neobbs although when I first read the subject, I thought maybe you needed to work out more....

Same problem here. I can have the phone in my hands looking at it straight up when the phone rings and the phone goes black for about 5 seconds (or about 2 rings) and then the caller id comes up and I start hitting the call/talk button to answer. It goes to VM eventually and me hitting the green button ends up bringing up the recent call list. Auto rotate is disabled, but I do have weatherbug, open home, caller lookup and IM running in the background. Oh... and I have the transistions/animations enabled. That's all i can think of. I'll try removing the caller lookup app to see if it eliminates the problem.

hi,im running rc33 stock rom on bronze tmo g1 in singapore..it happened many a times,even on a cold boot up..wonder what is the actual problem here,mine is not rooted at all..

screamsoflust said:
hi,im running rc33 stock rom ....wonder what is the actual problem here,mine is not rooted at all..
Click to expand...
Click to collapse
why in the world would you do that? (j/k)

bhang said:
why in the world would you do that? (j/k)
Click to expand...
Click to collapse
huh?what do you mean?

screamsoflust said:
huh?what do you mean?
Click to expand...
Click to collapse
he means.. why would you not root your G1???
I think it's a good, fair and valid question.

Do you have installed a customer ring tone ? if yes, choose original ring tone and try again.

I had the same problem when I started using my phone. I dunno what changed but the prob. has disappeared or I got used to hold the pickup button down for a bit longer automatically. I got the feeling that this helped the issue.
My phone is RC33 not rooted... and to answer you question: I've tried but I'm still fighting with my XP to accept the USB driver.

Guess again!
neoobs said:
I am only going to take a guess and say that you have a lot of programs that run in the background.
Maybe try not using auto rotate.
Click to expand...
Click to collapse
mine does the same randomly. Straight after a factory reset.
nothing installed, and my G1 is not rooted (yet).

has anyone found a solution for this problem?
Using RC33 with weatherbug running in the background, but it occurs with it installed and without it installed
I swear, the G1 must be the worst phone ive ever used
can't wait for the touch pro 2 now...
google can't release polished software if their lives depended on it.. selling a beta phone is just bs

n3rdftw said:
has anyone found a solution for this problem?
Using RC33 with weatherbug running in the background, but it occurs with it installed and without it installed
I swear, the G1 must be the worst phone ive ever used
can't wait for the touch pro 2 now...
google can't release polished software if their lives depended on it.. selling a beta phone is just bs
Click to expand...
Click to collapse
Yep, must be terrible if about 4 or 5 people have this problem out of the thousands who have bought it....
I've never had any of these problems, but im guessing they're (probably) firmware related.

Meltus said:
Yep, must be terrible if about 4 or 5 people have this problem out of the thousands who have bought it....
I've never had any of these problems, but im guessing they're (probably) firmware related.
Click to expand...
Click to collapse
most probably just call back and arent bothered to find out how to fix it on xda
anyways, when you say firmware related, what did you mean?
I installed JF 1.42, and before that, his earlier versions, and way before that my phone started out with RC18, which I then rooted. Would it be linked to that? I've wiped my phone like a dozen times, but the problem is reoccurring perhaps once or twice a day, out of about 30 phone calls a day
additionally, although this may be linked to t-mobiles ****ty service, have you guys noticed a large increase in dropped calls?
I use my phone in both austin tx and houston, and in both locations, about every 10 calls is dropped, I dont know if its just the horrible service they have, or when I move from a location with 3g to edge.
With the new radio, the dropped calls have reduced in number, but still occur randomly
Also, one more thing, and a little off topic, but this has been bothering me,
Is there anyone to get a SMS application that allows me to type using a numpad or something similar on the screen? or at least, have spell correct, cause chompsms' keyboard is way too small to use one handed and still have legible messages, unlike the iphone where the errors would be auto corrected

n3rdftw said:
most probably just call back and arent bothered to find out how to fix it on xda
anyways, when you say firmware related, what did you mean?
I installed JF 1.42, and before that, his earlier versions, and way before that my phone started out with RC18, which I then rooted. Would it be linked to that? I've wiped my phone like a dozen times, but the problem is reoccurring perhaps once or twice a day, out of about 30 phone calls a day
additionally, although this may be linked to t-mobiles ****ty service, have you guys noticed a large increase in dropped calls?
I use my phone in both austin tx and houston, and in both locations, about every 10 calls is dropped, I dont know if its just the horrible service they have, or when I move from a location with 3g to edge.
With the new radio, the dropped calls have reduced in number, but still occur randomly
Also, one more thing, and a little off topic, but this has been bothering me,
Is there anyone to get a SMS application that allows me to type using a numpad or something similar on the screen? or at least, have spell correct, cause chompsms' keyboard is way too small to use one handed and still have legible messages, unlike the iphone where the errors would be auto corrected
Click to expand...
Click to collapse
I'm in austin, tx too and I also get the black screen of death almost every time I get an incomming call so maybe it is a location based thing? My g1 is rooted and I have over 70 apps installed and I'm not about to uninstall them 1 by 1 to see which one could be causing it. In the past, rings extended was said to be the one causing the problem but I don't have that installed.
Also, there have been enough requests for t9 and auto correct with chomp, I'm sure it will be in the upcomming updates

Im running Haykuro now and haven't had a single incident so far. Also, I have 73 (yes, seventy-three) MB of free system memory as I moved pretty much EVERYTHING to the SD card. In return, my phone is unable to boot without my SD card... which is a bit strange.

My phone keeps randomly shutting off. Ideas?

Earlier, my G2 shut off on me about 5 times. -_-
First, I had it sitting in the car ,tried to take a pic but the stupid voice recognition menu kept coming up so I gave up and set it down in the console. When I got home, the phone felt warm and was.. off.
Then, I turned it on.. stuffed it in my pocket. A moment later, I pulled it out and YET AGAIN when I pushed the button I was greeted by a quick vibe and the HTC screen -_-
Then a few minutes later I ran a speed test (checking HSPA+ out in Vegas).. put it down on the table.. come back.. PHONE IS *(@#% DEAD AGAIN.
I HATE YOU! *glares at phone*
It's killing me because it either happens several times in a row, or doesn't happen for days! I've tried replacing the sim card, replacing the SD card.. moving the battery... no dice.
Maybe it's my SIM card? Would that cause it? My last phone did that -_- And I'm silly to have not yet changed the SIM lol
Good thing I have a spare sitting in my bag.

What battery are you using? Aftermarket? Is so, did you remove the sticker around the battery? If you did then make sure you place a piece of tape on the battery to avoid making contact with the metal sd card holder. The metal on metal causes it to shut down.
Sent from my HTC Vision using XDA App

Interesting. I've also been having random shutdowns (not reboots, which I've seen mentioned elsewhere, due to a hardware fault) --
HTC Desire Z, using default battery, but I'll try isolating it anyway with a slip of paper or something.

OP you on a custom rom with overclock? maybe your clocking your phone too high or low?
Also if the phone for whatever reason gets too hot or cold it will turn itself off.

Please see this forum: Phone powers down and won't turn back on w/o pulling the battery
I strongly believe that this may be an issue with the GPS and/or Google Maps. Once I have the GPS off, this has not occurred. Can anyone else try this?
I have the Bell Desire Z NAM with stock HTC Sense 2.2 ROM.
It seems to be quite prevalent, see the bottom of this review: T-Mobile G2 is speedy sequel to original Android

I think you may be onto something with that GPS note, but my phone doesnt' need the battery pulled to restart.
Also, it's running the stock firmware, stock battery (just exchanged battery and got a new SIM card yesterday, and it shut off again today.. so those aren't the problem)... so any issues I'm having are 100% stock related...
This time it shut off after using Maps so....

i read somewhere (trying to find the source) that some G2's were experiencing random restarts / shutdowns due to low signal strength. Not sure how valid this is but you might want to look into this as well.

fablife said:
i read somewhere (trying to find the source) that some G2's were experiencing random restarts / shutdowns due to low signal strength. Not sure how valid this is but you might want to look into this as well.
Click to expand...
Click to collapse
This was true before we received the first OTA update. Since then though the problem has been fixed.

I think it was definitely the GPS, that said I just got done with a really long phone call about this and have a replacement on the way.. but that was way too much effort AND I have to pay shipping (it's not much, but seriously.) I'm not happy that T-Mobile was THAT big a pain in the butt about getting the phone replaced with a new one in the 30 day return period.
Going by the pointers one of my close friends on sprint (that used to be on AT&T) gave me, I'd say this could've been worse with another provider.. but it shouldn't have been. The reception isn't the best so the customer service should make up for that, and it sorta does.. but it sorta doesn't.
Oh well.

I have been experiencing almost the same thing for the past week or so. I have tried a few things such as lowering clock speeds, changing roms, and not using maps or GPS. Nothing has stopped the shutdowns. I cant seem to find a pattern in the things the phone is doing when it shuts off because it rarely does it when i have the screen on, also it never does it if music is playing or if i am watching a video. I will say that it seems to happen alot when i am in spots i know are dead spots for phone signal. I flash roms a fair amount so it is hard to say this has started after flashing a rom, but I will say it never did this before I flashed my first sensui 3.0 rom.
I am thinking its one of two things, something with the radio and/or its firmware or something with the sdcard because at least one senseui 3.0 rom said something about sdcard formatting.
I hope all this helps the smart people come up with idea on what wrong with our phones.

djrajir said:
I have been experiencing almost the same thing for the past week or so. I have tried a few things such as lowering clock speeds, changing roms, and not using maps or GPS. Nothing has stopped the shutdowns. I cant seem to find a pattern in the things the phone is doing when it shuts off because it rarely does it when i have the screen on, also it never does it if music is playing or if i am watching a video. I will say that it seems to happen alot when i am in spots i know are dead spots for phone signal. I flash roms a fair amount so it is hard to say this has started after flashing a rom, but I will say it never did this before I flashed my first sensui 3.0 rom.
I am thinking its one of two things, something with the radio and/or its firmware or something with the sdcard because at least one senseui 3.0 rom said something about sdcard formatting.
I hope all this helps the smart people come up with idea on what wrong with our phones.
Click to expand...
Click to collapse
My Desire Z had the same problem and I returned it to HTC Service for repair. They said they change some cables? and a new battery. It has been nearly 3 days and I haven't experienced a single shutdown but there was one time it restarted by itself.

Yeah my only problem with that is, I am close to my upgrade date. How much did it cost. I may still do it so I can give this phone to my kid brother.
Sent from my Htcclay's SuperCM7 G2 using Tapatalk

Just to update, I found that I can make it do it some times when playing with opening the hinge.
Sent from my Htcclay's SuperCM7 G2 using Tapatalk

Possible cause/fix found
I posted this in another thread here regarding the same problem but it appears it may have been overlooked so I'll post the info again in hopes of helping you and others having this problem.
A possible cause/fix has been found as posted on the T-mobile forums:
http://forums.t-mobile.com/t5/T-Mobile-G2/G2-Turning-off-by-itself/td-p/513575/page/4
There is a conductive metal strip along the back of the battery that looks like it may be shorting out. Check out the link for detailed fix with pics. I take no credit for this, just posting it since I'm experiencing this problem too.

Talked to tmobile CS today and was trying to get a replacement because my phone would randomly reboot and shut off. All he told me was go and pick up a new sim card. If that didn't help then they would be willing to give me a warranty replacement.
Sent from my T-Mobile G2 using XDA App

carquote said:
I posted this in another thread here regarding the same problem but it appears it may have been overlooked so I'll post the info again in hopes of helping you and others having this problem.
A possible cause/fix has been found as posted on the T-mobile forums:
http://forums.t-mobile.com/t5/T-Mobi.../513575/page/4
There is a conductive metal strip along the back of the battery that looks like it may be shorting out. Check out the link for detailed fix with pics. I take no credit for this, just posting it since I'm experiencing this problem too.
Click to expand...
Click to collapse
Clicking your link all I got was an empty T-Mobile page with the message "Page not found" and some some java script error message when closing the window.
Is this possible fix something else than lining the back of the battery with a strip of paper?

whpsnp said:
Clicking your link all I got was an empty T-Mobile page with the message "Page not found" and some some java script error message when closing the window.
Click to expand...
Click to collapse
Sorry about that, I fixed the link and it should be working now.

Cool, thanks!
Sent from my HTC Vision using XDA App

I'm pretty sure mine is not caused by the metal strip since my battery's all proofed. I didn't have anything wrong with it until about half a month ago, and it always happened after using GPS and left it on. If I turn it off after navigation or any other app that requires GPS the phone won't go into SOD.
I switched back to CM7 RC2 around that time and starting to get the GPS no fix problem, and it could't be fixed by the dd=/dev/.... script. So I switched into Nightly 88 or something that at least I was able to get a fix but the not-so-random freezing started.
This morning I flashed the new 7.1.0 RC1 and the phone would just turn itself off (it used to just freeze and become hot), and I got really tired of it... My old G1 was much more reliable than this.
I tried the dd=/dev script again, so far after 5 min the phone is still on with GPS on....

@carcuote
Thank you! I haven't had this issue for months now. But the solution is so easy to do that I will try our anyways.
I had this issue the first month our so when I got the new phone, but went away permanently after the second month. Maybe the contacts in the battery got a little rusted? Don't know but the solution is simple enough to try...
Sent from my T-Mobile G2

New Nexus 6P User, problems out of the gate

So like the title says, I'm a new Nexus 6P user, and I had problems out of the gate.
I bought the device 2nd hand from a guy off craigslist, after my S6 edge started over heating after I had the screen replaced (don't buy Samsung "edge" phones, I know your careful, but on the off chance you drop it, your in a world of trouble).
I tested the phone, before I bought it, it appeared pretty much brand new, everything worked. When I got home, and hard reset it again for good measure all hell broke lose.
After a hard reset the phone wanted to update to build 19 something. After the update and a reboot, the phone app kept crashing before I could finish the setup process. The only thing I could do is factory reset it again. This appeared to clear up that problem. I did the near by device thing, and restored it from what Google could find out about my S6 edge. I wish it was more of a restore like what you can do in the iOS world, but it's better then what we had before so it's cool. I noticed that Chrome would crash everytime you tried to use it only in less I uninstalled the update. After I got the phone to the point where I wanted it, I thought I was free in the clear. When I started trying to use music apps, they all crash. Apple Music, Spotify, Soundcloud. Then I noticed YouTube also crashed the same way. When I tried to make a phone call, the phone app would crash too... So the phone was useless. I downloaded the SDK and the most current build which I think was 20 something. I followed a guide on here and formatted the phone reinstalling everything around build 20. The only thing this fixed was the phone issue.
I could now make phone calls without it crashing, but I was in the same boat with some applications working, and the same ones that didn't work not working. I flashed this phone 5, or 6 times, with the last time me formatting the userdata. I read that it wasn't a good idea because it could lock me to only 32GB ( I had a 64GB version), but after I did the flashing along with the usedata format, I still had 64GB of useable space, however I still had the same issue with the same types of applications crashing. I tried older builds, same issue (also the older builds all had the problem with the phone app crashing to the point that the phone wasn't usable).
I ended up sending the phone to the manufacturer, which appears to be in the same metroplex I live in. Hopefully they can find a hardware problem under warenty and fix it. I'm making this post to see if anyone else ran into similar issues, and if anyone knows if this is a hardware build issue, that was hopefully resolved.
I'm sorry to be so long winded...

Is the phone rooted and running a custom ROM?

Pappy35 said:
Is the phone rooted and running a custom ROM?
Click to expand...
Click to collapse
Everything appeared to be stock, I don't know if it was rooted before, but when I was finished with it it was stock, I even locked the boot loader again (it was locked before I started flashing it)

vmiyoshi said:
Everything appeared to be stock, I don't know if it was rooted before, but when I was finished with it it was stock, I even locked the boot loader again (it was locked before I started flashing it)
Click to expand...
Click to collapse
How much did you pay for it?
Sent from my LG-H830 using Tapatalk

RidinNerdy said:
How much did you pay for it?
Sent from my LG-H830 using Tapatalk
Click to expand...
Click to collapse
I paid 4 for it...

Note 4 freezes and restarts issue! Ultimate thread

Hello everyone,
I've had my note 4 over two years now and out of nowhere problems started happening after second MM update, model SM-N910F was freezing and restarting and sometimes was not able to boot normally and got mmc read fail.
I'm reading a lot about this problem in other forums and here, so hope someone could help about this issue.
No Success:
I tried anything from removing sd card, removing sim card, changing the battery, resetting the device, cleaning the cache, flashing the room through odin, flashing the rom with pit file and doing a re partition (Didn't tried Nand erase).
Success:
The only way that I was able to fix the freeze issue was by installing app called Wake Lock and enabling PARTIAL_WAKE_LOCK.
But using Wake Lock has its disadvantages. First of all you need to run the app all times which its not practical and second it wipes your battery because it keeps device and processor awake.
Please join this thread anyone who has similar issues with the aim to fix or bring the phone to an usable state again.

I also purchased my GN4 about 2 years ago and just recently got this error. This is really fishy. Wouldn't be surprised if it was Samsung trying to screw over all the root users and get us to upgrade to newer models.

The Sponge said:
I also purchased my GN4 about 2 years ago and just recently got this error. This is really fishy. Wouldn't be surprised if it was Samsung trying to screw over all the root users and get us to upgrade to newer models.
Click to expand...
Click to collapse
Did you tried Wake Lock if it works? Which model of GN4 do you have ?

shpeendi said:
Did you tried Wake Lock if it works? Which model of GN4 do you have ?
Click to expand...
Click to collapse
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:

The Sponge said:
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
Click to expand...
Click to collapse
I really don't think it's an hardware issue but even if so, why this started to happen immediately after the update and why it only happens when the device goes to sleep or when we power on the device.
I also noticed the change on bootloader fonts and interface after the update. I'm suspecting that the problem is there.
Does any one has any thoughts about this?

It's a hardware issue. It's a bad nand issue in fact. You can find Reddit posts a mile long about it.
Anyways it will slowly get worse over time. Had to replace the main-board in my SM-N910W myself.

ciscostud said:
It's a hardware issue. It's a bad nand issue in fact. You can find Reddit posts a mile long about it.
Anyways it will slowly get worse over time. Had to replace the main-board in my SM-N910W myself.
Click to expand...
Click to collapse
Is there any reason at all why it is happening I mean for the nand issue. I don't like the answer that is motherboard fault and we should replace it, which probably means replacing the phone. Is there anyone who can see deeper into the motherboard to find the issue. I also insist that this started to happen immediately after the second MM update.
I still have an IPhone 3G from 2008 and never changed anything on it. Isn't that ironic ?

shpeendi said:
Is there any reason at all why it is happening I mean for the nand issue. I don't like the answer that is motherboard fault and we should replace it, which probably means replacing the phone. Is there anyone who can see deeper into the motherboard to find the issue. I also insist that this started to happen immediately after the second MM update.
I still have an IPhone 3G from 2008 and never changed anything on it. Isn't that ironic ?
Click to expand...
Click to collapse
It was a Bad batch of nand chip that started to go bad after a year or two. Note 4s started to drop like flies before April.
I think your in the 1st stage of Loss and Grief. 1st stage is denial.

If thats so than Samsung should repair our phones under warranty and not tell us we have to pay for the repair coz we installed custom roms.

The Sponge said:
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
Click to expand...
Click to collapse
same issue here, exactly as described above...
any way to push Samsung to admit bad batch and fix it for us with no charge?

golden_m said:
same issue here, exactly as described above...
any way to push Samsung to admit bad batch and fix it for us with no charge?
Click to expand...
Click to collapse
I've already swaped a few main-boards. Ive even put a international exynos n910c main-board in a broken canadian snapdragon note 4 and its works perfect.
If anyone needs help just pm me.

ciscostud said:
I've already swaped a few main-boards. Ive even put a international exynos n910c main-board in a broken canadian snapdragon note 4 and its works perfect.
If anyone needs help just pm me.
Click to expand...
Click to collapse
I would be more interested in understanding how come so many Note 4 devices started acting up around same time mark...

This is definitely a hardware problem with the motherboard. Mine started giving the same symptoms 2 weeks after the 6.01 upgrade. Wakelock made it stable but after Samsung replaced the motherboard it is so much faster and no issues at all. I wonder if this is a faulty NAND issue whether the 6.01 upgrade and the way it manages memory could have triggered it. Certainly strange but it need Samsung to fix it.

I am also having same problem.
I was using custom rom and it was working fine without any lag or freeze suddenly one day my Note fall from bed to ground and since then it is not working properly i thought its the ROM so i reverted back to stock MM rom flashed via odin.
Reset everything erased everything but the problem remains same.
At present i am on stock with hardly any apps just FB and whatsapp.
But my device is so slow and keep lagging and sometimes it becomes very hot and restart itself.
I dont know what to do now. i m on 910 G snapdragon.

anasrizvi said:
I am also having same problem.
I was using custom rom and it was working fine without any lag or freeze suddenly one day my Note fall from bed to ground and since then it is not working properly i thought its the ROM so i reverted back to stock MM rom flashed via odin.
Reset everything erased everything but the problem remains same.
At present i am on stock with hardly any apps just FB and whatsapp.
But my device is so slow and keep lagging and sometimes it becomes very hot and restart itself.
I dont know what to do now. i m on 910 G snapdragon.
Click to expand...
Click to collapse
Sorry to hear that, as for now jut install wake lock and enable partial_wake_lock so you can use your device until it fails completely

Mmm. I was thinking to root my phone (4month old still under warranty ) i think i changed my mind after reading this ?. Thank you guy's for the warning
Sent from my SM-N910G using Tapatalk

Same issues, I downloaded the wake lock and so far so good.

I have the same issue also guys and it started a week after updating to Marshmallow.
Phone worked perfectly fine for 2 years prior to this. So I highly doubt its a hardware issue and more likely a software/firmware problem.
Phone seems to have issues whenever the screen is asleep (hence why the wake lock app seems to help with this problem although not a proper solution)
I'm hoping Samsumg can release a patch fix for this as I truly love my Note 4 and would like to keep it for some time yet.

have anybody tried going back to Lollipop?

golden_m said:
have anybody tried going back to Lollipop?
Click to expand...
Click to collapse
I was thinking about that! but I saw on other threads people downgrading with no success.

SM-T500 Apps / Games flashing black when running

Hi all,
Just like to check as i am at a loss on what to do. I got my Samsung Galaxy Tab A7 10.4" SM-T500 last month. Generally it was ok except that samsung browser will hang when the tablet goes into deep sleep and it will take mins for it to 'catch up' meaning i cannot turn off the tablet or launch applications during that time. Youtube app sometimes will sometimes randomly close.
However in early dec, after a samsung software update, games and some apps started flashing black for 5 seconds and perhaps about 2 seconds of the app /game screen shown. It has not gone into sleep or anything as if the game / app appears on the screen you can still click on items and all. Restarting the tablet or factory reset did not help. Youtube app will still randomly close.
Already sent in to samsung service centre and they tell me they have reflashed the latest firmware.. however above problems remain. I asked customer support and they told me that at this point to wait for a new samsung update or app update which may solve the following issue. but thats going to take a while before an update comes from their tablet
Wonder is there anything i can do ?
Thank you.

lcaveyl said:
Hi all,
Just like to check as i am at a loss on what to do. I got my Samsung Galaxy Tab A7 10.4" SM-T500 last month. Generally it was ok except that samsung browser will hang when the tablet goes into deep sleep and it will take mins for it to 'catch up' meaning i cannot turn off the tablet or launch applications during that time. Youtube app sometimes will sometimes randomly close.
However in early dec, after a samsung software update, games and some apps started flashing black for 5 seconds and perhaps about 2 seconds of the app /game screen shown. It has not gone into sleep or anything as if the game / app appears on the screen you can still click on items and all. Restarting the tablet or factory reset did not help. Youtube app will still randomly close.
Already sent in to samsung service centre and they tell me they have reflashed the latest firmware.. however above problems remain. I asked customer support and they told me that at this point to wait for a new samsung update or app update which may solve the following issue. but thats going to take a while before an update comes from their tablet
Wonder is there anything i can do ?
Thank you.
Click to expand...
Click to collapse
This is happening to me since the latest update as well.
I wouldn't stress about too much. Updates have been coming pretty regular so just wait for an update. They've updated the tablet about 3 times since I bought it so I feel they'll have this fixed soon.
Nothing I've done fixed it so I'm just waiting for an update.

lcaveyl said:
Hi all,
Just like to check as i am at a loss on what to do. I got my Samsung Galaxy Tab A7 10.4" SM-T500 last month. Generally it was ok except that samsung browser will hang when the tablet goes into deep sleep and it will take mins for it to 'catch up' meaning i cannot turn off the tablet or launch applications during that time. Youtube app sometimes will sometimes randomly close.
However in early dec, after a samsung software update, games and some apps started flashing black for 5 seconds and perhaps about 2 seconds of the app /game screen shown. It has not gone into sleep or anything as if the game / app appears on the screen you can still click on items and all. Restarting the tablet or factory reset did not help. Youtube app will still randomly close.
Already sent in to samsung service centre and they tell me they have reflashed the latest firmware.. however above problems remain. I asked customer support and they told me that at this point to wait for a new samsung update or app update which may solve the following issue. but thats going to take a while before an update comes from their tablet
Wonder is there anything i can do ?
Thank you.
Click to expand...
Click to collapse
Do you have auto rotate on? It seems turning it off stopped the black screen for me. Give it a try until it's fixed with an update.

Thanks Halftebyte.
Tested to turn off the auto rotate but didnt help. There is a new Samsung update but seems it didnt do anything to help. i will try the factory reset later again

lcaveyl said:
Thanks Halftebyte.
Tested to turn off the auto rotate but didnt help. There is a new Samsung update but seems it didnt do anything to help. i will try the factory reset later again
Click to expand...
Click to collapse
Yes, I thought that solved it but you're right, turning off auto rotate didn't actually help.
I haven't gotten any new updates since version T500XXU2ATK3.
What version are you on?
I'm pretty confident a factory reset won't solve this problem. I'm happy I'm not the only one experiencing this. Hopefully an update will fix it soon.

My version is now T500XXS2ATL1, security patch level is 1 December 2020
You are right, the factory reset didnt do anything at all. It made it worst!! even at the home screen it will just keep flashing. I gave up and went back to the service centre and told them to do something as i could not work on it. They changed the motherboard and it seems ok for now. Stil testing it but problem seems to have gone away.
Suggest if yours is under warranty to do the same too!

lcaveyl said:
My version is now T500XXS2ATL1, security patch level is 1 December 2020
You are right, the factory reset didnt do anything at all. It made it worst!! even at the home screen it will just keep flashing. I gave up and went back to the service centre and told them to do something as i could not work on it. They changed the motherboard and it seems ok for now. Stil testing it but problem seems to have gone away.
Suggest if yours is under warranty to do the same too!
Click to expand...
Click to collapse
Oh wow. I hope mine isn't a hardware issue.

lcaveyl said:
My version is now T500XXS2ATL1, security patch level is 1 December 2020
You are right, the factory reset didnt do anything at all. It made it worst!! even at the home screen it will just keep flashing. I gave up and went back to the service centre and told them to do something as i could not work on it. They changed the motherboard and it seems ok for now. Stil testing it but problem seems to have gone away.
Suggest if yours is under warranty to do the same too!
Click to expand...
Click to collapse
Any update on your experience?
Just wanted to update that I solved this problem for myself by downgrading to firmware version T500XXU2ATJ6 which had a November 2020 build/release date (with Sept 2020 security patch unfortunately). I'm happy now though. Confirmed fully working after using for over a week.

Hmm after the hardware change, the tablet works as it should. I am still on the T500XXS2ATL1 firmware.

Interesting. Someone else on the Samsung forums had a similar issue and firmware downgrade solved his issue.

When a firmware newer than ATL1 comes out I'll try it.
Also, doubt this tablet will get Android 11 before May/June.

hmm wondering if there is anything different in our tablets (mobo chips /memory / etc) which made it behave so drastically with this firmeware update. And with a hardware change it seems to work better? hmmm wondering wondering.
I still have one small issue where every now and then unlocking the screen you may not be able to access any icons, i will need to lock the screen again and drag on camera/browser before i am able to use the tablet. This happened out of the box as well but didnt think much of it then.

lcaveyl said:
hmm wondering if there is anything different in our tablets (mobo chips /memory / etc) which made it behave so drastically with this firmeware update. And with a hardware change it seems to work better? hmmm wondering wondering.
I still have one small issue where every now and then unlocking the screen you may not be able to access any icons, i will need to lock the screen again and drag on camera/browser before i am able to use the tablet. This happened out of the box as well but didnt think much of it then.
Click to expand...
Click to collapse
That's exactly what I'm wondering. Some minor component difference on the mobo having compatibility issues with the different firmwares.
Kinda sounds like a touchscreen issue you're having. Hopefully it won't get unbearably bad for you.