Jump to content

Google Pixel C (google-smaug): Difference between revisions

From postmarketOS Wiki
m source -> syntaxhighlight
Jja2000 (talk | contribs)
m Update status
Line 27: Line 27:
| status_battery =  
| status_battery =  
| status_3d = Y
| status_3d = Y
| status_audio =  
| status_audio = N
| status_bluetooth = Y
| status_bluetooth = Y
| status_camera =  
| status_camera = N
| status_gps = -
| status_gps = -
| status_mobiledata = -
| status_mobiledata = -
Line 38: Line 38:
| status_nfc = -
| status_nfc = -
| status_usba = -
| status_usba = -
| status_hdmidp =  
| status_hdmidp = N
| status_keyboard = -
| status_keyboard = Y
| status_touchpad = -
| status_touchpad = -
| status_irtx = -
| status_irtx = -
| status_rxtx = -
| status_rxtx = -
| status_ethernet = -
| status_ethernet = -
| status_accel =  
| status_accel = N
| status_magnet =  
| status_magnet = -
| status_light =  
| status_light = N
| status_proximity =  
| status_proximity = N
| status_hall =  
| status_hall = Y
| status_barometer =  
| status_barometer = -
| status_powersensor =  
| status_powersensor = Y
| status_fossbootloader = P
| status_fossbootloader = P
| booting = yes
| booting = yes
Line 162: Line 162:
|-
|-
| Volume/Power/Home keys || GPIO || Yes || Working in kernel
| Volume/Power/Home keys || GPIO || Yes || Working in kernel
|-
| Keyboard Detection || GPIO || Yes || Working in kernel, needs script to automatically connect to BT device
|-
|-
| cros-ec:‎<br />- Accelerometer‎<br />- Ambient Light Sensor<br />- Lightbar<br />- USB Connector (alerts tegra-xusb/-xudc when modeswitching) || <br />- Bosch BMI160<br />- Silicon Labs Si114x<br />- Included in platform driver<br />- cros-ec-typec<br /> || Yes, but see notes || cros-ec-i2c (the platformdriver) broke for the Pixel C somewhere inbetween 4.14 and 4.19, needs bisection with UART, none of the mentioned components work
| cros-ec:‎<br />- Accelerometer‎<br />- Ambient Light Sensor<br />- Lightbar<br />- USB Connector (alerts tegra-xusb/-xudc when modeswitching) || <br />- Bosch BMI160<br />- Silicon Labs Si114x<br />- Included in platform driver<br />- cros-ec-typec<br /> || Yes, but see notes || cros-ec-i2c (the platformdriver) broke for the Pixel C somewhere inbetween 4.14 and 4.19, needs bisection with UART, none of the mentioned components work

Revision as of 08:38, 19 September 2024

Google Pixel C
CHANGE_ME
CHANGE_ME
Manufacturer Google
Name Pixel C
Codename google-smaug
Released 2015
Type tablet
Hardware
Chipset Nvidia Tegra X1
CPU Quad-core 1.9 GHz Cortex-A57
GPU Maxwell
Display 2560x1800 IPS LCD
Storage 32/64 GB
Memory 3 GB
Architecture aarch64
Software
Original software Android
Original version 8.1.0
FOSS bootloader partial
postmarketOS
Category testing
Pre-built images no
Mainline yes
Features
Flashing
Works
USB Networking
Broken
Internal storage
No data
SD card
No data
Battery
No data
Screen
Works
Touchscreen
Works
Keyboard
Works
Multimedia
3D Acceleration
Works
Audio
Broken
Camera
Broken
Camera Flash
No data
Connectivity
WiFi
Works
Bluetooth
Works
Miscellaneous
FDE
No data
USB OTG
Partial
HDMI/DP
Broken
Sensors
Accelerometer
Broken
Ambient Light
Broken
Proximity
Broken
Hall Effect
Works
Haptics
No data
Power Sensor
Works


Contributors

Users owning this device

  • Jja2000 (Notes: Currently trying to get this in a presentable state, have two of these (32GB/64GB))
  • Joshaspinall (Notes: Currently running Lineage Android)
  • Russanandres (Notes: ResurrectionRemix 9)


How to enter flash mode

fastboot

When turned off press and hold the power button and volume down until the bootloader menu displays. Using the volume button select "Switch to fastboot mode" and press the power button.

APX

There seems to be no key combination for entering APX mode. Use these commands instead:

$ pmbootstrap initfs hook_add apx
$ pmbootstrap flasher flash_kernel

This will cause device entering APX on boot

Installation

Installation keeping Android partition table (easy way)

$ pmbootstrap init
$ pmbootstrap install --no-cgpt

Then in fastboot mode:

$ pmbootstrap flasher flash_kernel
$ pmbootstrap flasher flash_rootfs

Installation with repartition and booting from USB (recommended way)

Enable booting from USB

On PC:

$ wget https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_15183.78.0_trogdor_recovery_stable-channel_mp-v7.bin.zip
$ unzip chromeos_15183.78.0_trogdor_recovery_stable-channel_mp-v7.bin.zip
$ sudo losetup -Pf chromeos_15183.78.0_trogdor_recovery_stable-channel_mp-v7.bin
$ sudo cp $(findfs LABEL=ROOT-A) recovery.img
$ adb push recovery.img /sdcard/recovery.img

On device in adb shell:

$ su # assuming you have root
# cd /sdcard
# mkdir rootdir
# losetup /dev/block/loop0 recovery.img # this may throw an error, but still pass. check blkid command, make sure there is /dev/block/loop0 in the output
# mount -o ro -t ext4 /dev/block/loop0 rootdir
# cd rootdir
# mount -t sysfs /sys sys
# mount -t proc /proc proc
# mount -o bind /dev dev
# mount -t tmpfs -o size=100M tmpfs tmp # for flashrom to avoid read-only fs
# mount -t tmpfs -o size=100M tmpfs run # for crossystem to avoid read-only fs
# mkdir run/lock # crossystem will create /run/lock/crossystem.lock there
# chroot . /bin/bash
# export PATH="$PATH:/usr/sbin:/bin"
# ln -s /dev/mtd/mtd0 /dev/mtd0 # this is needed for crossystem to work with downstream SPI flash driver
# crossystem dev_boot_usb=1 dev_boot_signed_only=0 # this command enables booting from USB

Everything else is the same to Chrome OS devices except that we don't have prebuilt images yet.

Installation to USB storage

Use these commands:

$ pmbootstrap init # select google-smaug
$ pmbootstrap install --sdcard /dev/sdX # replace /dev/sdX with your storage

You can boot from USB with pressing Ctrl + U in bootloader.

Installation to eMMC

Warning WARNING: This part is not tested. Make a backup before attempting this.

Boot pmOS from USB, connect to WiFi and install pmOS on eMMC:

$ sudo apk add pmbootstrap
$ pmbootstrap init # select google-smaug
$ pmbootstrap install --sdcard /dev/mmcblkX # replace X with correct eMMC block device

Mainline Kernel Status

Table of components in the device