This seems to be an elusive topic. I’ve seen threads of people who can’t enable it, people who can’t disable it, people who can’t even find the settings, …
My situation:
Fairphone 5
With Fairphone OS, Android 14, “Tap on wake” (double tapping anywhere on the black screen to wake up the phone) was working more or less reliable. I used it daily as my phone’s buttons are often not reachable in its bike mount.
Now with /e/OS 2.8 (Community) the setting is still there, it is turned on, but it doesn’t work at all.
AoD, Always on Display (aka “Always show time and info”, available on /e/OS but not on FairphoneOS) does not seem to impact the behaviour whether it’s turned on or off.
Battery saver on or off also makes no difference.
I’m quite missing this functionality. I would submit a bug report on GitLab, but it doesn’t let me register (probably because my e-mail address uses the newer top-level domain .gent).
Anyone in a similar situation who did manage to get this to work?
So, as an update: I don’t know what changed, I’m not aware of any updates since, but out of nowhere this started working. With and without AoD, I can now smoothly wake up my phone by double tapping the screen. Nice.
(I did install Google TTS to get Duolingo working again, but that can’t be related, can it?)
I would like that, too. Had it on my Blackberry for years. But I would never like to have an always on display because of energy consumption.
I use another method because of that, based on the proximity sensor. In the FP3 the proximity sensor is somewhere near the top edge. So when I move my hand near this edge the screen is activated. This is done by an app called WaveUp (F-Droid). Not always good (for instance in a pocket), that’s why you can switch it off, but works well in the very most cases and reduces the use of the hardware button a lot.
Just as unexpectedly as tap to wake started working for me, it stopped again.
No update or change in settings that I am aware of. I just rebooted after swapping out an SD card and “tap on wake” wasn’t working anymore. Very strange.
Im confused becasue this is a feature I would find really useful (I constantly used it on my previous device) and on my Fairphone 5 which I got preinstalled with e/os I dont even have a setting to wake the phone on tap. Where is the setting for you?
Note: you need hardware support for this. Not every device is able to provide this feature. The very most devices switch the screen off when the device is locked. It does then not react anymore on any taps or swipes.
It seems from this thread on the fairphone forums that the FP5 has the hardware support for it given that on their OS there is the option to enable/disable it, but I still cant find anything in the settings.
From my experience this is NOT a hardware issue. As I clearly wrote here higher up, tap-on-wake used to work on my FP5 when I was running the original FairphoneOS, and for a few weeks is has been working perfectly fine with /e/OS (Community version).
The tap-on-wake setting is there (Settings > Display > Tap to wake), it is on, it just is not working. And, as said, it started working for me out of the blue after a phone reboot and just like that, on a next reboot, it stopped working again. No settings were changed that I am aware of.
I’d be curious to hear from any FP5-user running /e/OS if they got tap-to-wake working at some point. I’d love to have this feature back, as my phone is in a protective bike mount most of the time, with no access to the side buttons.
It seems so. Perhaps someone who is in a better position to can weight in on whether this will be pushed to the official FP5 build, or if it is an Android 14 feature, or what is actually going on? Or is there a process to getting those answers elsewhere from this forum?
In any case, thanks for shedding some light on this.
It sounds like a13 (official) and a14 (community) difference,
one additional one is ‘Battery Information’ where you are able to see the actual max. capacity of it (but it was a bit arbitrary for me).
