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

Chromebook Pixel 2013 audio and touchpad issues #212

Open
arnoldthebat opened this issue Nov 12, 2018 · 2 comments

Comments

@arnoldthebat
Copy link
Owner

commented Nov 12, 2018

https://www.chromium.org/a/chromium.org/dev/chromium-os/developer-information-for-chrome-os-devices/chromebook-pixel

I’ve partially solved audio problem by unmutting headphones channel in the alsa-mixer though headphones sound is extremely loud. But the main problem is touchpad. I’ve tried to use atmel’s mxt-app utility to export/import touchpad settings but unfortunately it doesn’t help.

What’s interesting, running original chrome os image lsmod | grep atmel doesn’t show atmel’s driver but
cat /proc/bus/input/devices shows
I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name=”Atmel maXTouch Touchpad”
P: Phys=i2c-1-004b/input0
S: Sysfs=/devices/pci0000:00/0000:00:02.0/i2c-1/1-004b/input/input8
U: Uniq=
H: Handlers=event8 cpufreq_interactive
B: PROP=5
B: EV=b
B: KEY=e520 10000 0 0 0 0
B: ABS=671800001000003

@arnoldthebat arnoldthebat changed the title Chromebook audio and touchpad issues Chromebook Pixel 2013 audio and touchpad issues Nov 12, 2018

@arnoldthebat

This comment has been minimized.

Copy link
Owner Author

commented Nov 12, 2018

Keyboard backlight needs fixing as well

Hi Arnold, I just installed this on my Chromebook Pixel (2013), and everything works great except I can no longer adjust the keyboard backlight using Alt+ brightness keys. I found some articles saying you can do this manually by changing the values in /sys/class/leds/chromeos::kbd_backlight/brightness, but I don’t have this file. Maybe the device for the keyboard LED isn’t loaded in this build?

@andyleadbetter

This comment has been minimized.

Copy link

commented Jul 1, 2019

I worked out that saving the cfg files for both the touchscreen and touchpad allowed them to generate events, but the builds for pixel don't know what to do with them. It seems that both both the atmel tp and ts cfg files must be pushed to the hardware, after which the devices at least generate events.

If we are able to build the image with libinput, and the cfg files, then the driver should auto load them and all work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.