Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Samsung Chromebook Plus changing resolution? #3144

Closed
serfma opened this issue Mar 10, 2017 · 9 comments
Closed

Samsung Chromebook Plus changing resolution? #3144

serfma opened this issue Mar 10, 2017 · 9 comments
Labels

Comments

@serfma
Copy link

serfma commented Mar 10, 2017

name: xenial
encrypted: yes, unlocked
crouton: version 1-20170309181220~master:a72a0cb5
release: xenial
architecture: arm64
xmethod: xorg
targets: gnome,touch,extension,keyboard
host: version 9000.91.0 (Official Build) stable-channel kevin 
kernel: Linux localhost 4.4.21-06459-ge91c124 #1 SMP PREEMPT Wed Feb 22 23:26:03 PST 2017 aarch64 aarch64 aarch64 GNU/Linux
freon: yes

Please describe your issue:

Using setres doesn't properly change resolution (as I've read it does no sanity checking) and I'm stuck at an unusable 2400x1600 resolution.

@Burgal
Copy link

Burgal commented Mar 11, 2017

I wouldn't call it unusable but it is a bit uncomfortable. :)

I found a somewhat bad hack that gets us to the correct resolution but kills responsiveness.

xrandr --output eDP-1 --scale .75x.75 --fb 1800x1200 --panning 1800x1200

@Burgal
Copy link

Burgal commented Mar 11, 2017

WARNING: DO NOT RUN SETRES- IT CAN DAMAGE YOUR SCREEN ON THE SAMSUNG CHROMEBOOK PLUS

I wish I knew this. I have constant flickering on the bottom left side of my screen with the image of my linux desktop regardless of if I'm in the chroot or not. Pretty sure it's burn in so I'm leaving my screen on a blank white webpage to hopefully fix it.

I think there should be a way to get the resolution issue fixed though. Anyone have an idea why the scaling causes such lag?

@serfma
Copy link
Author

serfma commented Mar 11, 2017

Is it still occurring even after a device reboot?

@Burgal
Copy link

Burgal commented Mar 11, 2017

It did stay after device reboot, yes. I played one of those pixel fixing videos https://www.youtube.com/watch?v=GQBz4khU_ck and kept my screen on white for an hour each. Using setres to make my display1800x1200 probably shortened the life of my screen a bit but now it looks like it's back to normal.

Be careful with xrandr, the same thing happened with some of the settings I tried besides:
xrandr --output eDP-1 --scale .75x.75 --fb 1800x1200 --panning 1800x1200

@serfma
Copy link
Author

serfma commented Mar 12, 2017

Hmmm. Yeah I tried to reduce scale to 0.5 but of course there's performance issues with that. Starting to believe that there's not really a swell solution.

@drinkcat
Copy link
Collaborator

If you use xiwi there is a HiDPI option in the popup menu that should do what you want.

@drinkcat
Copy link
Collaborator

@Burgal: I didn't see any flickering issue on my kevin (R58-9227.0.0), running the xrandr command above (but, yes, frame rate seems to drop considerably).

@serfma
Copy link
Author

serfma commented May 17, 2017

I'd like to update this as I've finally gotten back around to messing with my CB+. The only thing that I've found to work is using XFCE with the default hidpi theme while increasing icon sizes and font sizes. Has anyone thus far found a better solution?

@aleifuu
Copy link

aleifuu commented Dec 5, 2017

I'm using CB Pro with lxde and jessie as a backend

Have no success at adjusting resolution either using setres, xandr, or any other method outlines here yet

Probably going to stop trying since your warning if potential "dead" screen on this baby's sibling ...

not unusable, just uncomfortable

What works so far is that you hook your CB to external monitor, then the resolution will just fit nicely

I think CB's unusual 3:2 is just unusual to adjust

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants