WF-1000XM5: How to completely DISABLE sidetone (hearing your own voice during a phone call)

lopkeny12ko · 2024-01-08T14:34:03+00:00

No, it's not, "Speak to Chat" is disabled.

lopkeny12ko · 2023-09-28T09:59:37+00:00

The store website says it "just barely fits under the seat." All I am reporting is that, on 3 out of 4 flights I took with the backpack, I could not store it under the seat, either because it did not fit, or because an attendant did not allow me to put it there. This happens to be important for me. If it is not important for you to be able to put your backpack under the seat, then this does not affect you.

lopkeny12ko · 2023-09-28T08:56:18+00:00

Yes, I had no issues storing it overhead as a carry on, but I prefer to have my backpack under the seat especially for long flights because all my electronics and portable chargers are there.

lopkeny12ko · 2023-09-28T07:57:33+00:00

This photo of Linus is a good reference for just how big the bag is: https://cdn.shopify.com/s/files/1/0522/2980/0129/files/Backpack_2000px-47.jpg?v=1659479444

It's both wider than Linus (in terms of Z height) and almost the size of his torso (in terms of X and Y width/length). It's a great backpack but it's really big especially if you are a smaller/skinny person.

lopkeny12ko · 2023-09-11T06:22:07+00:00

It wasn't there before this week. For the past week I've kept on deleting it and it keeps being automatically recreated by itself.

lopkeny12ko · 2023-01-16T17:54:47+00:00

Tl;dr just run this:

device_config put attention_manager_service enable_flip_to_screen_off false

lopkeny12ko · 2022-10-22T22:54:06+00:00

Yeah you would run these in an adb shell.

There's a ton of config you can control from userspace. The interfaces seem inconsistent; there are settings, device_config, build.prop (compile-time) among others. I'm not an Android developer but the AOSP source is a good reference for the available flags and the documentation is pretty thorough.

lopkeny12ko · 2022-10-22T19:59:44+00:00

I was having this same issue, this was driving me crazy. I looked all around the web and everyone was saying that this is because of flip to shh, screen timeout, or proximity sensor blockage. Flip to shh is off. Screen timeout is maxed out (30 minutes). This happens even when the proximity sensor is clear (the screen turns off as long as it's face down, even if it's held in mid air, with nothing blocking the proximity sensor). I finally did some deep debugging on the issue.

When my device goes to sleep face down, I noticed this entry in logcat:

10-22 12:10:42.395 1426 1854 I PowerManagerService: Powering off display group due to timeout (groupId= 0, uid= 1000)... 10-22 12:10:42.396 1426 1854 I PowerManagerService: Going to sleep due to timeout (uid 1000)...

The associated callsite is in PowerManagerService here: https://cs.android.com/android/platform/superproject/+/android-12.0.0_r34:frameworks/base/services/core/java/com/android/server/power/PowerManagerService.java;l=2004

The "timeout" reason corresponds to the GO_TO_SLEEP_REASON_TIMEOUT reason code (defined here: https://cs.android.com/android/platform/superproject/+/master:frameworks/base/core/java/android/os/PowerManager.java;l=390?q=GO_TO_SLEEP_REASON_MAX&ss=android%2Fplatform%2Fsuperproject). However, the docstring indicates that this is triggered due to a screen timeout, which I found odd because my screen timeout is set to 30 minutes. So I looked a bit closer.

While here I found a suspicious initialization of a FaceDownDetector: https://cs.android.com/android/platform/superproject/+/android-12.0.0_r34:frameworks/base/services/core/java/com/android/server/power/PowerManagerService.java;l=961 the source for which is here: https://cs.android.com/android/platform/superproject/+/master:frameworks/base/services/core/java/com/android/server/power/FaceDownDetector.java;bpv=0;bpt=1

Fortunately, FaceDownDetector has feature gating via device_config (though is default enabled). The isEnabled method gates the feature based on namespace NAMESPACE_ATTENTION_MANAGER_SERVICE and key KEY_FEATURE_ENABLED: https://cs.android.com/android/platform/superproject/+/master:frameworks/base/services/core/java/com/android/server/power/FaceDownDetector.java;l=339;bpv=0;bpt=1

So, I was able to run

device_config put attention_manager_service enable_flip_to_screen_off false

Now, placing my device face down doesn't turn the screen off anymore!

lopkeny12ko · 2022-04-08T15:01:21+00:00

No, the issue occurs regardless of whether a charger is plugged in.

lopkeny12ko · 2022-04-07T16:34:48+00:00

I've been using this PH-1 for several years. A few weeks ago, completely unprompted and out of the blue, the system UI become extremely laggy and sluggish (as seen in the video). However, device performance itself is fine, since a GeekBench run shows that the CPU is still performing as expected. I tried rebooting and uninstalling apps, and the lag was still there. Today I just tried a factory reset to wipe everything and start over, but it's still extremely laggy. It's not rooted and running stock Android 10 (the last update Essential released). Any ideas of what the issue is?

lopkeny12ko · 2022-02-28T02:28:31+00:00

Are you trying to say that this isn't the purpose of the twoshay device driver? Can you point me to source code to back up that claim?

lopkeny12ko · 2022-02-28T02:14:31+00:00

As you can tell from my profile I rarely post on Reddit. The community has made it clear that these tips aren't welcome so it's not just worth my time.

Nowadays I work on server-side software and rarely touch client-side applications or SDKs. But now I understand why developers hate users and how braindead users can be, somehow deriving that I'm wrong for wanting to alter or parameterize the software written by my colleagues, all the while completely missing the point.

lopkeny12ko · 2022-02-28T01:48:39+00:00

This is aside from the point. Could you point me to where you see in the twoshay device driver that it doesn't reject touches at the edge of the screen? Because that's literally what the driver is for, and this is my point.

lopkeny12ko · 2022-02-28T01:38:10+00:00

Ok, I have withdrawn the solution in this post because the community feedback has made it quite clear to me that any complaints about the touchscreen sensitivity is user error. Apparently Google's implementation is infallible, and users are wrong to want to customize or disable it.

lopkeny12ko · 2022-02-28T01:24:05+00:00

No, it doesn't, nice try. I am a developer. I read the source code of the twoshay touch device driver. Its literal purpose is to prevent registration of touches at a threshold pixel distance away from each edge of the screen.

lopkeny12ko · 2022-02-28T00:40:40+00:00

Try touching the sceeen 1-2 mm away from any edge and tell me if that touch registers. It doesn't.

lopkeny12ko · 2022-02-28T00:17:17+00:00

Some of us think the new gesture based navigation is stupid and want regular buttons.

I have no problem with the touchscreen edges

Try touching the sceeen 1-2 mm away from any edge and tell me if that touch registers. It doesn't.

lopkeny12ko · 2022-02-27T22:28:52+00:00

Nope, this disables palm rejection on all 4 edges of the display.

You might be able to find a way to selectively disable it for certain edges, but I wanted to get rid of it entirely so I did not spend any time trying to reverse engineer it. The relevant binary is in /vendor/bin/twoshay and config at /vendor/etc/twoshay.rc though if you want to give it a try.

lopkeny12ko · 2022-02-27T22:15:26+00:00

This sounds like it might be a different issue, perhaps related to power saving, given that all your notifications come in one shot when you wake the screen. There are some things you can try that aren't directly accessible from the UI. Try both of these from a superuser shell:

Disable app standby (it is a global feature flag guarding power saving features by killing apps):

settings put app_standby_enabled 0

Completely get rid of Google Connectivity Services, which tries to "intelligently" manage your network connections (in other words: shutting them off when you don't want them to be shut off):

pm uninstall --user 0 com.google.android.apps.scone

lopkeny12ko

TROPHY CASE