Jump to content

Google Nexus 4 (lg-mako)

From postmarketOS Wiki
Note Currently the device is booting into a black screen, see pmaports#209. Help with resolving this is welcome. Please remove this note when the issue has been fixed.
Google (LG) Nexus 4
LG Nexus 4 running Weston
LG Nexus 4 running Weston
Manufacturer Google (LG)
Name Nexus 4
Codename lg-mako
Released 2012
Type handset
Hardware
Chipset Qualcomm Snapdragon S4 Pro (APQ8064)
CPU Quad-core 1.5 GHz Krait
GPU Adreno 320
Display 768x1280 IPS
Storage 8/16 GB
Memory 2 GB
Architecture armv7
Software
Original software Android
Original version 4.2
Extended version 5.1.1 (Linux 3.4)
postmarketOS
Category testing
Pre-built images no
Mainline partial
Unixbench Whet/Dhry score 1233.4
Features
Flashing
Works
USB Networking
Works
Internal storage
No data
SD card
No data
Battery
Works
Screen
Broken
Touchscreen
Works
Multimedia
3D Acceleration
No data
Audio
No data
Camera
No data
Camera Flash
No data
Connectivity
WiFi
Works
Bluetooth
No data
GPS
No data
NFC
No data
Modem
Calls
No data
SMS
No data
Mobile data
No data
Miscellaneous
FDE
Works
USB OTG
Works
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

Users owning this device


Installation

Note FDE (full disk encryption) seems to be broken for lg-mako currently, see pmaports#209
Note No backend is available for user interface weston - it will boot to black/blank screen, see Weston troubleshooting.
$ pmbootstrap init
$ pmbootstrap install
$ # (enter fastboot, see below)
$ pmbootstrap flasher flash_rootfs
$ pmbootstrap flasher boot

To flash the kernel, you can choose pmbootstrap flasher flash kernel (but charging and power off doesn't work as expected anymore, see below).

Attempting to flash an arbitrarily large rootfs (here xfce4 ui, >1GB), will fail:

$ fastboot flash userdata lg-mako.img
Sending 'userdata' (1129472 KB)                    FAILED (remote: 'data too large')
fastboot: error: Command failed

Note that this is not related to the destination partition size. The getvar option to fastboot does not list a max-download-size variable. Unfortunately the fastboot -S flag is not useful since the image is not sparse. An untested tedious workaround may be to just flash a smaller ui image and manually apk del/add.

Entering "Fastboot mode"

Hold Volume Down + Power, let go of Power once the device display does something (e.g. turns from battery icon to black screen).

Reverting to factory

Reflashing a factory image after a pmOS install may hang. For the final factory image (LMY48T), the display will show a looping animation of rotating / flying colored dots on a black background (but be patient, wait at least 10 minutes to confirm hang). Follow the instructions at Reverting to stock (manta). The first time setup screen should follow the rotating dots (perhaps 8 minutes). During the flash the back of the device may warm noticeably.

Charging and power off (after flashing the postmarketOS kernel)

Note You don't have to flash the kernel! pmbootstrap flasher boot is also working!

You can flash the postmarketOS kernel, but instead of charging the battery, it will boot straight into postmarketOS (or the on screen keyboard to type in the password). Right now, the best way to charge it from that situation is to boot the recovery TWRP.

You can properly turn the device off by unplugging the usb cable, then booting into fastboot, then choosing power off.

Wifi

We need to package the wcnss.* files for wifi. A version from 2015 can be found here.

Hardware status (downstream kernel)

Output from hwtest

hwtest output:

CPU tuning

CPU tuning:

Charging

Charging:

Sensors

For reference, sensor information from sensorsandbox (f-droid) on mako 16GB; note that in addition to hardware-based sensors, it presumably includes software-based / derived sensors.

sensor details (sensorssandbox)

Mainline

Note See The Mainline Kernel for a general introduction to mainlining.

Current tree can be found here Qualcomm_Snapdragon_600_(APQ8064)#Mainlining

theohussey's mainlining progress was here. Read on for generic instructions of what would need to be done.

That most peripherals of the mako should work with mainline as well, once they are enabled in the DTS file. In fact, @vetzki reported in #1079 that the mako boots when using exactly the same DTS as the one from flo (this is not recommended, as misconfiguring your device like that may damage it). SSH appears to be working for a short time before getting kicked out, the display does not work.

A good way forward would be using a minimal version of the flo DTS, where everything but USB is deleted, and fixing USB / trying to get the display working with the DSI Panel Porting Guide. The downstream DTSI files that need to be ported to the upstream kernel are probably located here, and I guess the exact panel name appears when running dmesg after a successful boot (I did not verify this). Please expand this when you're working on it, and report your progress in #postmarketOS. Check out the Mainline Guide.

Partition Layout

Partition layout:

Community Info

postmarketOS users that own the device


Maintainers

  • Ivan Belokobylskiy

Contributors

  • ollieparanoid
  • PabloCastellano and robb4 on IRC: Workaround for red screen bug (#54)

See also