Interesting conversation with GrapheneOS. Didn’t know they essentially hate each other. I’m using e/os but just because I cannot run graphene on my device.

I’m using e/os. It’s, in my opinion, the best compromise between a normal device and the best out there like Jolla and Graphene.

This works!

Key Commands

1. List Connected Displays To see all connected outputs and their status:

kscreen-doctor -o

Example output:

Output: 1 eDP-1
        enabled
        connected
        Modes: 1:2560x1600@60.00*!

This helps identify your display names (e.g., eDP-1 or HDMI-A-1).

2. Turn Off All Displays (DPMS) To put all displays into low-power mode:

kscreen-doctor --dpms off

Uses DPMS (Display Power Management Signaling) to turn off displays safely.

3. Turn On All Displays To wake all displays:

kscreen-doctor --dpms on

4. Disable/Enable a Specific Output To control a specific display (e.g., HDMI-A-1):

kscreen-doctor output.HDMI-A-1.disable
kscreen-doctor output.HDMI-A-1.enable

Note: Avoid disabling your primary/laptop panel (e.g., eDP-1) unless you have another display connected.

5. Bonus: Adjust Brightness or Scale

kscreen-doctor output.eDP-1.brightness.50  # 0-100
kscreen-doctor output.eDP-1.scale.1.5     # Scale factor

Thank you for sharing your setup. Your solution using wlr-randr in a cron job is indeed useful for wlroots-based compositors (such as Sway, Hyprland, or labwc), where the wlr-output-management protocol is supported.

For those (like me) encountering the error ‘compositor doesn’t support wlr-output-management-unstable-v1’, this indicates that the compositor in use (e.g., KDE/KWin, GNOME/Mutter, or other non-wlroots compositors) does not support wlr-randr. In such cases, alternatives should be considered.

I will be post my findings, I can’t believe I’m the only or just one of the few looking to archive this in a laptop…

Are you sure? I believe that using ipleak.net will provide you with a detailed report of your public IP address, DNS servers, WebRTC status, and other network-related information. However, it will not show you the internal DNS server you are using within your local network.

You are right that Android’s system-wide DNS settings (e.g., those configured in Wi-Fi or mobile network settings) are not automatically applied to Termux. Termux runs in a sandboxed environment and manages its own network configuration. I will try changing Termux but keep in mind that the reason I checked Termus is because local dns resolution do not work on all my android devices, I can resolv local addresses only if I connect to my home network remotely using a vpn.

That’s quite drastic but maybe the only really effective. I still find all of this very difficult to believe. I mean, am I wrong if I say that DNS is fundamental to be sure your traffic is safe? But even more weird…I’m using e/os, is supposed to be focus on privacy and “degoogling” of our life but…it use google DNS? I’m also worried I might not understanding what is really happening here, that an app I used changed the DNS settings on my mobile.

Yes but how do you know that is using that? I mean, did you try to resolv a local address? I have test it using a Terminal (termux) - If I use did and seems to report all the time, regardless of which connection and despite setting my local DNS setting on a static configuration for the wifi. Is this the same for you? can you share some screenshot?

Why this matter? Is it posibile to use your local dns ip as private dns? I have tried and didn’t accept a local ip address

Did you ever tested it? Because in any android device I got, it always “default” to 8.8.8.8 - google’s one. I have to connect to a vpn do get local ips being resolved. I just don’t get it, is this normal?

like every other devices I supposed…but it doesn’t work in any mobile I got. the dns server stay google’s one no matter what you do.