Phillip Berndt

I've ran into a similar issue on a new notebook recently. What helped me was to create this `predetect` script: if [ -n "$AUTORANDR_BATCH_PID" ]; then autorandr -l off xrandr...

I frankly have no idea, sorry. It's to tackle driver flakyness, and pretty much was a random attempt 🤷‍♂️

If the monitor models are somewhat standardized, then you can easily share configurations between machines. If user homes are network backed, then things should just work for users: A machine...

One other thought: It should be somewhat straightforward to hack autorandr to generate the profile name from the EDIDs, and to rather than managing configurations itself just maintain a symlink...

Yes, that's what I thought, too. See the [`single-pass` branch](https://github.com/phillipberndt/autorandr/commit/c982fc5ab0c3df9db99ca404b4afc29a4a061b7e). Does that work as expected?

Yes, that's why autorandr doesn't do everything in one pass either. It even uses 3 passes in some cases (e.g., some drivers run into issues when it comes to `--transform`...

It does, see autorandr.py line 1097. Meaning something must be off with the detection here. What happens if you run `DISPLAY= autorandr.py --batch` manually as root?

autorandr doesn't have such a feature. Maybe you can make it work with a generic setup (EEID `*`, or even a pattern encoding the resolution you want if you can...

Hey, thanks for reporting this and sorry for the late reply. To apply the profile you'll need the `-c` option. Did you skip that on purpose above, or is that...

Hey, thanks, and also thanks for sharing your tool, that's an awesome extension! (Which we should link to from the readme.) I agree that this should be improved, and with...