Google Pixel (google-pixel)
Manufacturer | |
---|---|
Name | Pixel |
Codename | sailfish, marlin |
Released | 2016 |
Hardware | |
Chipset | Qualcomm MSM8996 Snapdragon 821 |
CPU | Quad-core (2x2.15 GHz Kryo & 2x1.6 GHz Kryo) |
GPU | Adreno 530 |
Display | 5.0 inch AMOLED capacitive multi-touch screen, 1280x1920 |
Storage | 32/128GB |
Memory | 4GB Dual Channel LPDDR4 |
Software | |
Original software | Android 7.1 (Nougat) |
postmarketOS | |
Category | testing |
Pre-built images | no |
Mainline | no |
Flashing |
No data |
---|---|
USB Networking |
No data |
Internal storage |
No data |
SD card |
No data |
Battery |
No data |
Screen |
No data |
Touchscreen |
No data |
Multimedia | |
3D Acceleration |
No data |
Audio |
No data |
Camera |
No data |
Camera Flash |
No data |
Connectivity | |
WiFi |
No data |
Bluetooth |
No data |
GPS |
No data |
NFC |
No data |
Modem | |
Calls |
No data |
SMS |
No data |
Mobile data |
No data |
Miscellaneous | |
FDE |
No data |
USB OTG |
No data |
HDMI/DP |
No data |
Sensors | |
Accelerometer |
No data |
Magnetometer |
No data |
Ambient Light |
No data |
Proximity |
No data |
Hall Effect |
No data |
Haptics |
No data |
Barometer |
No data |
Contributors
Maintainer(s)
Note on device codenames and compatibility
The sailfish variant of the Google Pixel shares the same kernel builds as the Pixel XL (marlin). Therefore, anything here referencing sailfish should also be relevant to marlin.
What works
TLDR;
- Nothing
Installation using normal measures does not successfully boot. This is likely due to the fact that the Google Pixel's fastboot has two boot slots (A and B). What this effectively means is that fastboot allows you to dual boot. That's nice and all, but it's annoying. What we will likely have to do is flash via TWRP. Needs more investigation.
What does not work
Watch this space.
How to enter flash mode
It is required that the device is cell carrier unlocked before attempting to perform an OEM unlock using fastboot.
Installation
Coming soon
Serial Debugging
Sounds like this is possible, given kernel has serial debugging enabled.
http://www.viruss.eu/malware/practical-android-debugging-via-kgdb/
To Do List
Doing
- [ojbr] - Investigate serial debugging. Obtained a USB FTDI device, just need to hack together a 3.5mm TRRS cable
Backlog
- Re-enable LZMA kernel image compression, add via makedepends
- Test device flashing using fastboot
- Investigate Kernel upgrade path to 4.X where MSM8996 has better support in mainline