Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
HarryNyquist

Light Sleeper - Samsung Galaxy S10 Can't Tell When it's in a Pocket

Recommended Posts

Posted · Original PosterOP

It seems the new Galaxy S10 can't figure out whether or not it's in a pocket, judging by reports on reddit and the Samsung forums. It's hopefully a software bug and therefore fixed easily, but this continuing trend of devices or software being released untested is just unacceptable, especially when the hardware + software in question is a $1000 flagship device. Doubly so, considering not turning on in your pocket is a fairly simple thing that hundreds upon hundreds of (cheaper) phones can do without problem.

 

https://www.androidpolice.com/2019/03/15/the-galaxy-s10-cant-tell-when-its-in-your-pocket-keeps-waking-the-screen/

Quote

On most phones, the proximity sensor knows when something is pressing on the phone, be that your ear while on a call or the fabric of your pocket. The GS10 seems to only use the proximity sensor when you're on a call. So, it's easy for your leg to trigger the tap to wake feature through the fabric of your pocket. Users report their phones waste battery and activate buttons on the lock screen while in their pockets. Using the lower screen sensitivity mode doesn't seem to have any effect—the phone still wakes up. The only way to prevent this is to turn off tap to wake and ambient display, which makes the phone harder to wake up with that power button way up near the top.

https://us.community.samsung.com/t5/Galaxy-S10/Galaxy-S10-Tap-to-wake-activates-in-pocket-FIX-THIS-SAMSUNG/m-p/476809#M3226

 

 

Link to post
Share on other sites

but what if it isn't in your pocket?

 

panic mode activated


PSU Tier List//Graphics card (cooling) tier list//Build Guide Megathread//Motherboard Tier List//Linux Guide//Build logs//Before troubleshoot//Mark Solved//Off Topic//Community standards

Don't forget to quote or mention me

 

Primary PC:

Spoiler

CPU: I5-8600k  @4.5 ghz  GPU: GTX 1070 ti EVGA SC Gaming   RAM: 8+8 3360 mhz DDR4 Trident Z   MOBO: MSI Gaming Pro Carbon AC   HDD: 1 TB 7200 RPM Seagate Baracudda, 1 TB 5400 RPM Samsung ECOGREEN   SSD: Samsung 860 EVO 500 GB   Soundcard: built in   Case: Cooler Master Masterbox Lite 5 RGB   Screen: Salora 40LED1500

 

Secondary PC: Cedar mill

Spoiler

CPU: i3-2130   GPU: Intel HD graphics   RAM: 4+2 GB 1333 mhz DDR3    MOBO: HP H series   HDD: 320 GB WD Black 7200 RPM   PSU: HP 250 watt   Soundcard: built in   Case: Sunbeam Quarterback   Screen: IIyama Prolite T2240MTS, Samsung SyncMaster710N

 

Server: CookieVault

Spoiler

CPU: core2dual E8400   GPU: Intel HD graphics   RAM: 2+1+1+1 gb 1333 mhz ddr3   MOBO: HP Q series   HDD: 4x 1tb 5400 RPM Samsung Spinpoint Ecogreen   Soundcard: built in   Case: Compaq 6000 pro mt   Screen: Samsung SyncMaster710n

 

Laptop: Acer TravelMate 8573t

Spoiler

CPU: I3-2330M   GPU: Intel HD graphics   RAM: 8+2 GB 1333 mhz DDR3   MOBO: Acer   SSD: 250 gb mx500 sata   Soundcard: built in   Case: Acer TravelMate 8573t   Screen: TN 768p

 

Consoles:

Spoiler

PS4 slim glacier white 500 gb, PS4 FTP Special Edition 500 gb, Xbox, 3 DS lites, DSI XL, Gameboy Advanced Color, PS Vita v2, Wii, PS3 500 gb

 

Link to post
Share on other sites

Not OK Google.

 

 

 

 

 

(I know it's a Samsung issue, but no one uses Bixby.)


Build Logs: Cotton Candy Threads | ZEN CLARITY + | Just NCASE mITX | Noc Noc | NUC | Storage Log

 

Cotton Candy Threads - CPU AMD Threadripper 2950X | GPU EVGA FTW3 RTX 2080 Ti | MOBO Asus ROG Zenith Extreme | MEMORY 128GB (8x 16GB) Corsair Vengeance RGB 3200 | STORAGE 3x Samsung 960 Evo SSD + 4x Crucial P1 1TB + 2x Seagate Ironwolf 8TB 7.2k HDDs | PSU Corsair HX1200i w/ Cablemod Pro Extensions | COOLING Cooler Master TR4 ML360 | CASE Lian Li O11 Dynamic Black | LIGHTING 2x Corsair HD120 Fans, 4x Corsair Addressable RGB Strips, 2x Corsair Commander Pro | PCPP
 
ZEN CLARITY + - CPU AMD Ryzen 2700X | GPU Radeon VII | MOBO Crosshair VII Hero | MEMORY 32GB (4x 8GB) Corsair Vengeance RGB Pro @ 3200 | STORAGE Samsung 960 Pro SSD + 2x SanDisk Ultra II SSDs | PSU Corsair RM1000i | COOLING Corsair H150i Pro | CASE Crystal 570X | LIGHTING 6x Corsair SP120 Fans, Cablemod Addressable RGB Strip, Corsair Commander Pro | PCPP
 
Just NCASE mITX - CPU Intel Core i7 8700K @ 5.2GHz | GPU EVGA RTX 2080 Ti XC | MOBO Asus Z370-I Gaming | MEMORY 16GB (2x 8GB) G.Skill Triden-Z RGB 3000 | STORAGE Samsung 960 Evo 500GB SSD + Corsair MX500 1TB M.2 SSD | PSU Corsair SF600 | COOLING Noctua NH-U9S w/ Redux Push/Pull Fans | CASE NCase M1v5 | LIGHTING 2x Cablemod Addressable RGB Strips | PCPP
 
Noc Noc, Who's There? - CPU AMD Threadripper 1950X | GPU ASUS RTX 2080 Ti OC | MOBO ASRock X399M Taichi | MEMORY 32GB (4x 8GB) GSkill Trident-Z 3200 | STORAGE Samsung 970 Evo SSD | PSU Corsair HX1000i w/ Cablemod Pro B&W Kit | COOLING Noctua U9 TR4 w/ 2x Redux 92mm | CASE Corsair 280X White | FANS 6x Noctua 140mm Redux | PCPP
Link to post
Share on other sites

probably will be patched out soon ._.

4 minutes ago, Dogeystyle said:

Clearly the issue here is people should stop having pockets, and instead wear their phones. What a great con move by Samsung Wearables division, Apple won't see it coming

implants or smart spandex?

Link to post
Share on other sites

Yeah that seems like something that shouldnt have any problem tuning considering everything has always worked. I bet its actually related to pressure from the skin/pocket being capable of activating the ultrasonic scanner (and or directly waking up the device) instead of the proximity sensor itself being tuned poorly.

 

Sucks. Gotta fix these things.


LINK-> Kurald Galain:  The Night Eternal 

Top 5820k, 980ti SLI Build in the World*

CPU: i7-5820k // GPU: SLI MSI 980ti Gaming 6G // Cooling: Full Custom WC //  Mobo: ASUS X99 Sabertooth // Ram: 32GB Crucial Ballistic Sport // Boot SSD: Samsung 850 EVO 500GB

Mass SSD: Crucial M500 960GB  // PSU: EVGA Supernova 850G2 // Case: Fractal Design Define S Windowed // OS: Windows 10 // Mouse: Razer Naga Chroma // Keyboard: Corsair k70 Cherry MX Reds

Headset: Senn RS185 // Monitor: ASUS PG348Q // Devices: Galaxy S9+ - XPS 13 (9343 UHD+) - Samsung Note Tab 7.0 - Lenovo Y580

 

LINK-> Ainulindale: Music of the Ainur 

Prosumer DYI FreeNAS

CPU: Xeon E3-1231v3  // Cooling: Noctua L9x65 //  Mobo: AsRock E3C224D2I // Ram: 16GB Kingston ECC DDR3-1333

HDDs: 4x HGST Deskstar NAS 3TB  // PSU: EVGA 650GQ // Case: Fractal Design Node 304 // OS: FreeNAS

 

 

 

Link to post
Share on other sites

10/10 title, @rcmaehl would be proud


"Put as much effort into your question as you'd expect someone to give in an answer"- @Princess Luna

Make sure to Quote posts or tag the person with @[username] so they know you responded to them!

Purple Build Post ---  Blue Build Post --- Blue Build Post 2018 --- Project ITNOS --- P600S VS Define R6/S2

CPU i7-4790k    Motherboard Gigabyte Z97N-WIFI   RAM G.Skill Sniper DDR3 1866mhz    GPU EVGA GTX1080Ti FTW3    Case Corsair 380T   

Storage 1x Samsung EVO 250GB, WD Black 3TB, WD Black 5TB    PSU Corsair CX550M      Cooling Cryorig H7

Link to post
Share on other sites

It has happened to me a couple times, I pull my S10+ out of my pocket and it has told me I have failed to use the fingerprint scanner 5 times and should either wait or put in my passcode


Processor: i7 7700k@Stock GPU: GTX 1080 MSI Armor OC  Mobo: Asus Prime Z270-A RAM: Corsair LPX 16GB 3200 MHz CPU Cooler: be quiet! Dark Rock 3 SSD: Sandisk Ultra 2 960GB Case: Phanteks P400s PSU: Gigabyte B700H Monitor: AOC G2460PF 1080p 144Hz Mouse: Logitech G900 Keyboard: Corsair Strafe w/ MX Blues

Link to post
Share on other sites
On 3/15/2019 at 2:28 PM, TVwazhere said:

10/10 title, @rcmaehl would be proud

Glad to see people can make up for the missing witty titles while I'm busy with life


NotCPUCores Dev | Desktop Build: Ryzen 7 1800X @ 4.0GHz, AsRock Fatal1ty X370 Professional Gaming, 32GB Corsair DDR4 @ 3000MHz, RX480 8GB OC, Benq XL2730 1440p 144Hz FS


 

Link to post
Share on other sites

Weird mine doesn't do this. I even tried lol, I wonder what he doesn't have on or what I don't have. I have my always on screen off, and pocket recognition on.

Link to post
Share on other sites
5 minutes ago, floofer said:

can’t happen on an iPhone all I’m saying 

Yeah, because Apple is a 1.5-2 years behind the tech curve now a days. It will probably be happening on an iPhone in that time! 😛


Main PC: AMD Ryzen 1700 (8c/16t), MSI B350 Tomahawk, NDH 15, T-Force Delta RGB 16GB, Asus ROG STRIX RX-580, Samsung 128GB NVME, Crucial MX-300 1.05TB, 8TB WD Red/White, Seasonic S12II 620W.

School Laptop: Early 2014 Macbook Air. Intel i5-4260U, 4GB RAM, 128GB Apple PCI-E SSD, Intel HD Graphics 5000

Phone: iPhone XS Max 64GB: A12 Bionic. 4GB RAM, 6.5-inch 2,688 x 1,242 OLED, 3,174 mAh 

Wearables: Samsung Gear S3 Frontier, Sony 1000XM2

Random devices in various stages of working: Dell Inspiron 1000 (Works perfect other than battery), Late 2008 Macbook Aluminum Unibody (For Sale), Gateway Solo W2000 Laptop (For writing floppies, needs a battery), iBook G4 (For Sale.), Surface 3 (Touch screen is borked, perfect otherwise.), Lenovo G580 (For Sale)

 

Spoiler

"I looked to the sky in angst and yelled into the vast blue emptiness in hopes for an answer I would not receive. The very next day the sky fell."

 

Link to post
Share on other sites

IT'S A FEATURE! 

 

Also, how many different denim fingerprints are there? Can the gf get through if she wears my pants? 


Cor Caeruleus Reborn v6

Spoiler

CPU: Intel - Core i7-8700K

CPU Cooler: be quiet! - PURE ROCK 
Thermal Compound: Arctic Silver - 5 High-Density Polysynthetic Silver 3.5g Thermal Paste 
Motherboard: ASRock Z370 Extreme4
Memory: G.Skill TridentZ RGB 2x8GB 3200/14
Storage: Samsung - 850 EVO-Series 500GB 2.5" Solid State Drive 
Storage: Samsung - 960 EVO 500GB M.2-2280 Solid State Drive
Storage: Western Digital - Blue 2TB 3.5" 5400RPM Internal Hard Drive
Storage: Western Digital - BLACK SERIES 3TB 3.5" 7200RPM Internal Hard Drive
Video Card: EVGA - 970 SSC ACX (1080 is in RMA)
Case: Fractal Design - Define R5 w/Window (Black) ATX Mid Tower Case
Power Supply: EVGA - SuperNOVA P2 750W with CableMod blue/black Pro Series
Optical Drive: LG - WH16NS40 Blu-Ray/DVD/CD Writer 
Operating System: Microsoft - Windows 10 Pro OEM 64-bit and Linux Mint Serena
Keyboard: Logitech - G910 Orion Spectrum RGB Wired Gaming Keyboard
Mouse: Logitech - G502 Wired Optical Mouse
Headphones: Logitech - G430 7.1 Channel  Headset
Speakers: Logitech - Z506 155W 5.1ch Speakers

 

Link to post
Share on other sites

I don't really see it as a big issue. So it has a broken proximity sensor. It's not like software update can't fix it because it's clearly a software issue.

Link to post
Share on other sites
3 minutes ago, RejZoR said:

So it has a broken proximity sensor.

Why are the proximity sensor and finger print reader linked in any way?


Laptop: 2016 13" nTB MacBook Pro Core i5 | Phone: iPhone 8 Plus 64GB | Wearables: Apple Watch Sport Series 2 | CPU: R5 2600 | Mobo: ASRock B450M Pro4 | RAM: 16GB 2666 | GPU: Sapphire Nitro+ RX 580 4GB | Case: Apple PowerMac G5 | OS: Win 10 | Storage: 480GB PNY SSD & 2TB WD Green HDD | PSU: Corsair CX600M | Display: Dell UZ2215H 21.5" 1080p, ViewSonic VX2450wm-LED 23.6" 1080p, Samsung SyncMaster 940BX 19" 1024p | Cooling: Wraith Prism | Keyboard: G610 Orion Cherry MX Brown | Mouse: G303 | Audio: Audio Technica ATH-M50X & Blue Snowball
Link to post
Share on other sites

I don't think I've witnessed a single case of an iOS device improperly reading a fingerprint while inside a pocket. Just my anecdotal experience. 

 

Its probably more likely that the power button is being pressed (or activated by your thigh meat) and the pockets of peoples pants pushed up against their thigh is obviously not a fingerprint so the scan fails.

 

Also there is no reason the proximity sensor would be involved fingerprint unlocking. If the proximity sensor is involved when using the fingerprint reader on the S10........why? 

 

I think that because the power button is capacitive (duh)....there isn't really anything Samsung can do about it. If they "tune down the sensitivity", or use a Qualcomm equivalent of the motion co-processor (embedded in every A series SoC in Apple devices since the 5s) to determine that the phone is in a pocket; which would tell the system to stop accepting fingerprint input, they would still have to sacrifice unlocking speed.  

 

Shoulda just got it right the first time. 


Laptop: 2016 13" nTB MacBook Pro Core i5 | Phone: iPhone 8 Plus 64GB | Wearables: Apple Watch Sport Series 2 | CPU: R5 2600 | Mobo: ASRock B450M Pro4 | RAM: 16GB 2666 | GPU: Sapphire Nitro+ RX 580 4GB | Case: Apple PowerMac G5 | OS: Win 10 | Storage: 480GB PNY SSD & 2TB WD Green HDD | PSU: Corsair CX600M | Display: Dell UZ2215H 21.5" 1080p, ViewSonic VX2450wm-LED 23.6" 1080p, Samsung SyncMaster 940BX 19" 1024p | Cooling: Wraith Prism | Keyboard: G610 Orion Cherry MX Brown | Mouse: G303 | Audio: Audio Technica ATH-M50X & Blue Snowball
Link to post
Share on other sites
16 minutes ago, DrMacintosh said:

Why are the proximity sensor and finger print reader linked in any way?

So it doesn't trigger fingerprint false positives and locking the phone requiring you to use the PIN because it would consider them as failed attempts. Otherwise any time you'd pick it from pocket you'd have to use PIN in the end because it would trigger fingerprint reader in pocket and consume all the failed attempts without you actually failing to ID yourself with a finger.

Link to post
Share on other sites
1 minute ago, RejZoR said:

So it doesn't trigger fingerprint false positives and locking the phone requiring you to use the PIN because it would consider them as failed attempts. Otherwise any time you'd pick it from pocket you'd have to use PIN in the end because it would trigger fingerprint reader in pocket and consume all the failed attempts without you actually failing to ID yourself with a finger.

Then that’s just bad design. 

 

How would the proximity sensor relay to power button that it’s ok to accept input? When nothing is present within a few in? When there is something present at all? Obviously with something touching the proxy sensor the phone believes it’s ok. 

 

You see the problem right? Tying the proxy sensor to the finger print reader in this way can only cause false positives and negatives. It’s a terrible idea and should be removed immediately. 

 

Why cant the power button just only accept input when it’s clicked? Why does the proxy sensor have to be involved at all? 

 

 

Here is a logic test: 

If the dispay is on and phone is locked -> Activate fingerprint reader.

 

If power button is clicked and phone is locked -> Activate fingerprint reader. 

 

If proxy sensor detects an object x units away -> activate fingerprint reader

 

Now which of those doesn’t make any sense? 


Laptop: 2016 13" nTB MacBook Pro Core i5 | Phone: iPhone 8 Plus 64GB | Wearables: Apple Watch Sport Series 2 | CPU: R5 2600 | Mobo: ASRock B450M Pro4 | RAM: 16GB 2666 | GPU: Sapphire Nitro+ RX 580 4GB | Case: Apple PowerMac G5 | OS: Win 10 | Storage: 480GB PNY SSD & 2TB WD Green HDD | PSU: Corsair CX600M | Display: Dell UZ2215H 21.5" 1080p, ViewSonic VX2450wm-LED 23.6" 1080p, Samsung SyncMaster 940BX 19" 1024p | Cooling: Wraith Prism | Keyboard: G610 Orion Cherry MX Brown | Mouse: G303 | Audio: Audio Technica ATH-M50X & Blue Snowball
Link to post
Share on other sites

I just stated an example of what it could be used for. Maybe it's cheaper power wise to do phone state check with proximity sensor that might be a separate low power cluster than tripping a CPU and asking it "oy, is the screen on?"

Link to post
Share on other sites
5 minutes ago, RejZoR said:

Maybe it's cheaper power wise to do phone state check with proximity sensor that might be a separate low power cluster than tripping a CPU and asking it "oy, is the screen on?"

If I’m not mistaken Qualcomm should have some implementation similar to the Motion Co-Processor. Power draw on such a component is minuscule and gives said device immense gains in positional awareness without having to fire up the SoC and can relay the recorded info.

 

Choosing to not use it would be foolish.  


Laptop: 2016 13" nTB MacBook Pro Core i5 | Phone: iPhone 8 Plus 64GB | Wearables: Apple Watch Sport Series 2 | CPU: R5 2600 | Mobo: ASRock B450M Pro4 | RAM: 16GB 2666 | GPU: Sapphire Nitro+ RX 580 4GB | Case: Apple PowerMac G5 | OS: Win 10 | Storage: 480GB PNY SSD & 2TB WD Green HDD | PSU: Corsair CX600M | Display: Dell UZ2215H 21.5" 1080p, ViewSonic VX2450wm-LED 23.6" 1080p, Samsung SyncMaster 940BX 19" 1024p | Cooling: Wraith Prism | Keyboard: G610 Orion Cherry MX Brown | Mouse: G303 | Audio: Audio Technica ATH-M50X & Blue Snowball
Link to post
Share on other sites

Its probably something with the under screen finger print reader being too sensitive, tbh.

 

My Note 8 hasn't done this once with its back-mounted fingerprint reader (and I don't have a case, so its not like my pants just dont touch it.)

 

Im upgrading to the Nokia Pureview 9 as soon as I can afford it 🤷‍♂️


Main PC: AMD Ryzen 1700 (8c/16t), MSI B350 Tomahawk, NDH 15, T-Force Delta RGB 16GB, Asus ROG STRIX RX-580, Samsung 128GB NVME, Crucial MX-300 1.05TB, 8TB WD Red/White, Seasonic S12II 620W.

School Laptop: Early 2014 Macbook Air. Intel i5-4260U, 4GB RAM, 128GB Apple PCI-E SSD, Intel HD Graphics 5000

Phone: iPhone XS Max 64GB: A12 Bionic. 4GB RAM, 6.5-inch 2,688 x 1,242 OLED, 3,174 mAh 

Wearables: Samsung Gear S3 Frontier, Sony 1000XM2

Random devices in various stages of working: Dell Inspiron 1000 (Works perfect other than battery), Late 2008 Macbook Aluminum Unibody (For Sale), Gateway Solo W2000 Laptop (For writing floppies, needs a battery), iBook G4 (For Sale.), Surface 3 (Touch screen is borked, perfect otherwise.), Lenovo G580 (For Sale)

 

Spoiler

"I looked to the sky in angst and yelled into the vast blue emptiness in hopes for an answer I would not receive. The very next day the sky fell."

 

Link to post
Share on other sites
10 hours ago, DrMacintosh said:

Why does the proxy sensor have to be involved at all? ....

If proxy sensor detects an object x units away -> activate fingerprint reader

Because you guys are looking at it wrong and the second sentence if not even what happens. 

 

Three important things

1. Touch to wake

2. Unlock without waking

3. Thighs can trigger touches.

 

You touch the screen you can wake it and if you touch by the FP reader you can unlock it. If you put the phone in your pocket your thigh can trigger touches. This happens especially if you are sweaty. 

 

Hence why proxy should be used when in a pocket. Samsung has been doing this for years even with just preventing a screen from staying on in your pocket or purse if the button is accidentally hit. Its  a good design used to prevent phones just staying on or butt dialing. 

 

So yes, it makes perfect sense to involve the proxy. 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×