18-08-2019 12:14 AM
Hey,
I've noticed a problem with my A70 regarding trying to dim the screen when locking manually or expecting it to lock after screen timeout.
Basically, my phone won't sleep, at least not whilst charging. I spent a good while playing around with settings on my phone, such as timeout and lock screen settings. I also powered off the device but no luck.
After trying to figure out the problem further I discovered that the notification tray is being constantly updated every few seconds swapping between "Android system USB connector connected" and "Android system USB connector disconnected". So presumably this is what is keeping the phone awake as it thinks it is being constantly connected and disconnected from source USB source. I cleaned out the USB port but it was pretty clean to begin with. I'm not getting any notifications regarding any moisture detection.
The A70 charges just fine (though sometimes there is a slight delay to it recognising being plugged in) and it seems that the USB tethering interface is working well as I can use the remote debugging feature in Google Chrome (for web development purposes) just fine. As far as I can tell, there are no actual issues with the USB port - it functions as I would expect.
The A70 was last updated on the 14th August to "Security Patch level: 1 July 2019" and looking over the log of updates I see that "The charger/USB port's moisture detection algorithm has been improved" - so someone somewhere has been looking at this feature and I doubt it coincidence that my device has just developed a fault, given that I've not had it anywhere near moisture or excessive dirt.. and the port still actually works!
I've also tried Safe Mode but the issue persists. Also, if I power the device off, then plug it into the wall, power it on, the notification issue stops... until I unplug it/switch off the wall socket - then it comes back again.
Anyone else having similar problems?
15-09-2019 09:27 AM
Thanks wamoz, did it have corrosion? Did they say it's under warranty?
15-09-2019 09:30 AM
16-09-2019 07:43 AM
Hello,
I also have the same problem from 13.09.2019.
Is there any other solution avaiable other than replacing the sub boards?
Thank you.
16-09-2019 08:25 AM
My mobile is on its way to the lab so I hope I will soon know what's going on with it.
Maybe a factory reset solves the issue, if you want, you can try and share your findings.
Make sure to give it a day or two after resetting to make sure it's not there anymore.
18-09-2019 05:01 PM
Related to car chargers. Since I stopped using my car charger issue has stopped.
It has taking a few day of using factory charger but it has solved my issue for the moment.
DO NOT USE 1.0amp or 2.1amp charger.
Go to samsung spend the money for a proper charger and protect the phone rather then damage it and say its Samsung's fault.
Although I do think that Samsung should put a press release or at least a post about this. So far it's the community doing all the work. I had faith in you guys cause of my s3 I had for almost 10 years. I still use to this day lol.
Dont let me down samsung come on
Now did I have this issue prior to the update, no definitely not. So I do think the update has confused some software program but since I stopped with the car charger it stopped prompting these messages and my screen stays off 95% of the time. Other 5% is the light sensor when it pulls out my pocket or lighting changes.
18-09-2019 05:04 PM
20-09-2019 09:59 AM
22-09-2019 05:29 AM
Hi guys,
Just started having the same problem (22nd september) no clue what to do. Has anyone tried a factory reset? Not ideal but if it fixes the issue then I'd be willing
22-09-2019 07:03 AM
Mine was in the lab, they said there was a bit of corrosion so they replaced the USB port and now it's ok. Because it was on a small part it will be fixed under warranty.
I ask how come and they said it can be moisture, it can be the charging head that connects to the phone, etc etc... I have a mobile phone for more than 20 years now and never had nor heard about this issue.
I wonder if something is bad with the phone design that caused this issue but without Samsung checking this, all we have is this discussion.
24-09-2019 09:21 AM