Sometimes, after a reboot, the opening and closing of the Clear View Cover isn't recognized by the S9.
When asked in the past Samsung suggested a factory reset, but that didn't help.
It is NOT a problem of the hardware, the hall-sensor works correctly ( tested with sensor test *#0*# ).
Some affected users have found the following workaround : press start button with cover being open, 5 sec after begin of startup close cover, keep closed while booting, some secs after sim-unlock-prompt the closed cover is recognized, from then on it works until to the next boot .
There are several topics, chats, etc for this issue - I would kindly ask Samsung to involve technical staff, do a proper root cause analysis and solve the problem.
Solved! Go to Solution.
@CarlH @Anonymous User : Due to some other problems with the hardware ( the bixby key didn't work so I couldn't boot into maintenance mode, wipe the cache partition and see if that solves the problem ) I sent my S9 back to the vendor. So in a way my problem is solved.
Well, the vendor gave me new S9 ... and that works. As there also were some other issues with the other device, I've come to the conclusion that this might have been a hardware defect after all. That's not a perfect explanation, as the hardware test showed no problems with the hall sensor, but I havn't got a better one.
Ok, after the December Security Patch it happened again on my new S9. I wiped the cache partition and hope that this workaround will help. The question then would be : why isn't the cache partition wiped automatically after updates ?
This here is another thread regarding the same issue :
There are several other workarounds :
- remove S9 from case and reassemble
- wipe cache partition
- replace cover
- boot while charging
Sometimes they work, sometimes not. And after the next update the same issue again.
My best guess is that this is an initialization problem during the boot process.
@CarlH : ( sorry to grab your attention and assault you with this request, but I don't know whom and how else to ask ) could you perhaps obtain information about the status this issue has ? Does Samsung know about this, do they regard it as a problem, are they working to solve it etc.