Lineage Power Driver Download



Supported devices:

Lineage Power Driver download
  • Lineage Compact Power Line Power Entry Modules

    Prefix: ‘lineage-pem’

    Addresses scanned: -

    Documentation:

Does this ROM have all the bugs and instability older Lineage ROMs had, or it works as a daily driver? Apart from the fixable echo problem, do calls work well? I am considering switching ROMs to instal ThundeRStorms Kernel if I can't solve this issue from userspace. As a bonus I get EAS. Download Lineage OS 14.1 for LG G3. Get even more performance if you’re trying to squeeze every drop of power from the device. To be used as a daily driver. Power off the device, and boot it into download mode: With the device powered off, hold Volume Down + Home + Power. Now, click the button that the on screen instructions correlate to “Continue”, and insert the USB cable into the device. For Windows user only: install the necessary drivers. Download LineageOS 16.0 ROM ZIP for your device from above; Next, download the latest Gapps package, corresponding to your device’s architecture. Connect your device to PC via USB cable. Transfer both the ZIP files (ROM and GApps) to your device’s internal storage. Power off your device. LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project.

Author: Guenter Roeck <linux@roeck-us.net>

Description¶

This driver supports various Lineage Compact Power Line DC/DC and AC/DCconverters such as CP1800, CP2000AC, CP2000DC, CP2100DC, and others.

Lineage CPL power entry modules are nominally PMBus compliant. However, moststandard PMBus commands are not supported. Specifically, all hardware monitoringand status reporting commands are non-standard. For this reason, a standardPMBus driver can not be used.

Lineage Power Driver Download

Usage Notes¶

Lineage power driver download windows 7

This driver does not probe for Lineage CPL devices, since there is no registerwhich can be safely used to identify the chip. You will have to instantiatethe devices explicitly.

Example: the following will load the driver for a Lineage PEM at address 0x40on I2C bus #1:

All Lineage CPL power entry modules have a built-in I2C bus master selector(PCA9541). To ensure device access, this driver should only be used as clientdriver to the pca9541 I2C master selector driver.

Sysfs entries¶

All Lineage CPL devices report output voltage and device temperature as well asalarms for output voltage, temperature, input voltage, input current, input power,and fan status.

Input voltage, input current, input power, and fan speed measurement is onlysupported on newer devices. The driver detects if those attributes are supported,and only creates respective sysfs entries if they are.

in1_inputOutput voltage (mV)
in1_min_alarmOutput undervoltage alarm
in1_max_alarmOutput overvoltage alarm
in1_critOutput voltage critical alarm
in2_inputInput voltage (mV, optional)
in2_alarmInput voltage alarm
curr1_inputInput current (mA, optional)
curr1_alarmInput overcurrent alarm
power1_inputInput power (uW, optional)
power1_alarmInput power alarm
fan1_inputFan 1 speed (rpm, optional)
fan2_inputFan 2 speed (rpm, optional)
fan3_inputFan 3 speed (rpm, optional)
temp1_input
temp1_max
temp1_crit
temp1_alarm
temp1_crit_alarm
temp1_fault

Here’s my build of LineageOS 17.1 for Raspberry Pi 3 Model B and Model B+. It is unofficial and unsupported by the LineageOS team. It’s for advanced users only.

Important! This image includes parts that are licensed under non-commercial license (Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International). You may use this build freely in personal/educational/etc use. Commercial use is not allowed with this build!

Do not mirror my builds! Please post a link to this page instead.

lineage-17.1-20201108-UNOFFICIAL-KonstaKANG-rpi3.zip
https://www.androidfilehost.com/?fid=10763459528675579938
md5:2f0d503a5bbea5a4e15fbec22d767aff

Working:

  • Audio (HDMI, 3.5mm jack, USB microphones, bluetooth speakers/headsets, etc)
  • Audio DAC (using PCM512x DACs e.g. Hifiberry DAC+)
  • Bluetooth
  • Camera (using official Pi camera modules & UVC USB webcams)
  • GPIO
  • GPS (using external USB modules e.g. U-Blox 7)
  • Ethernet
  • Hardware accelerated graphics (VC4)
  • HDMI display
  • I2C
  • IR remotes (using external GPIO IR modules e.g. TSOP4838)
  • RTC (using external GPIO I2C modules e.g. DS3231)
  • Serial console (using external GPIO serial console adapters e.g. PL2303)
  • SPI
  • Touchscreen/multi-touch (USB touchscreens, Waveshare SPI touchscreens, official 7” touchscreen using SwiftShader software renderer)
  • USB (mouse, keyboard, storage, etc)
  • Wifi
  • Wifi tethering

Not working:

  • Hardware video decoding & encoding (software decoding & encoding works)

Issues:

  • SELinux is in permissive mode
  • and more…

Sources:

Thanks:

  • Peter Yoon and everyone who has contributed to android-rpi
  • brobwind for graphics and bluetooth fixes
  • Eric Anholt for VC4 graphics driver
  • Google for Android Things platform
  • Android-x86 project
  • LineageOS team & everyone who has contributed to LineageOS 17.1

How to install:

  1. Follow the official Raspberry Pi instructions for writing the image to the SD card (Linux, Mac, Windows).

FAQ:

Q: How to enable developer options?
A: Settings -> About tablet -> Click ‘Build number’ several times. You need to ‘drag’ the settings menu to reach the ‘About tablet’ section that is last on the list.

Q: How to enable root access?
A: You can enable root access under Settings -> System -> Developer options -> Root access. LineageOS no longer has built-in root management for applications. You should keep this option disabled at all times when you are not using an app that explicitly requires root access.

Q: How to enable local terminal application?
A: Settings -> System -> Developer options -> Local terminal

Q: How to enable advanced reboot options?
A: Settings -> System -> Developer options -> Advanced restart

Q: How to find several Raspberry Pi specific settings options?
A: Settings -> System -> Advanced settings

Q: My display is not working. I can only see the rainbow screen but no Android boot animation. What should I do?
A: This build only supports HDMI displays that report supported resolutions using EDID. See this page under ‘Which values are valid for my monitor?’ to see how to check in Raspberry Pi OS which resolutions your display supports. 1280x720 resolution is used by default with this build. You can try changing value in /boot/resolution.txt to use a different resolution that your display supports. Removing /boot/resolution.txt will try to use the preferred resolution for your display.

Q: Settings -> Storage shows total system size of 7 GB. There’s unallocated space on my sdcard. What should I do?
A: This is a 7 GB image, remaining space on your sdcard will remain unallocated. Easiest way to extend /data partition is to simply flash my resize zip in TWRP.

Alternative option is to use e.g. GParted and extend /data partition (/dev/block/mmcblk0p4) to cover the unallocated space. Resizing the partition manually will break support for encrypting /data. Format /data in TWRP recovery (Wipe -> Format data) after resizing to leave required space for crypto footer.

Q: I have official 7” LCD display and touchscreen. What should I do?
A: Official 7” touchscreen is only supported using SwiftShader software renderer. See below how to switch between different graphics drivers. You will also need to change display size under Settings -> Display -> Display size (or change ro.sf.lcd_density to 120 in /vendor/build.prop) to adapt to the smaller resolution.

Q: I need to use SwiftShader software renderer to use the official 7” display or I want to boot without any display connected. What should I do?
A: Warning, SwiftShader is a software renderer and using it affects graphics performance. You can switch between MESA and SwiftShader graphics drivers using a settings option found in Settings -> System -> Advanced settings -> Graphics drivers.

Also the previous method of executing following commands in ‘adb shell’/serial console/terminal still works:

Q: Raspberry Pi doesn’t have a power button. How to power off/reboot device?
A: Following keyboard keys work as Android buttons: F1 = Home, F2 = Back, F3 = Multi-tasking, F4 = Menu, F5 = Power, F11 = Volume down, and F12 = Volume up. You can also use one of many third party reboot applications.

Q: How to create a DIY hardware power button?
A: You can send power button events by connecting GPIO21 to ground.

You can enable the feature by using a settings option found in Settings -> System -> Advanced settings -> Power button.

Also the previous method of executing following commands in ‘adb shell’/serial console/terminal still works:

You can also use the DIY power button to boot the device to TWRP recovery. Press and hold the button while powering on the device until you see the TWRP screen.

Q: How to enable audio through 3.5mm jack?
A: You can enable the feature by using a settings option found in Settings -> System -> Advanced settings -> Audio device.

Also the previous method of executing following commands in ‘adb shell’/serial console/terminal still works:

Q: How to use IR remote?
A: You can enable the feature by using a settings option found in Settings -> System -> Advanced settings -> Infrared remote.

You can place a keymap for your remote as /boot/rc_keymap to be automatically loaded on boot (see available keymaps for reference).

Q: How to use RTC?
A: You can enable the feature by using a settings option found in Settings -> System -> Advanced settings -> Real time clock.

System time is automatically read and set from the RTC on boot once you’ve enabled the feature. You need to write the system time you want to use to the RTC:

Q: How to boot from USB device?
A: Warning, this is still an experimental feature. Especially TWRP seems to have some issues with USB boot.

  1. Follow the official instructions on how to enable USB boot on Pi 3 B (this step is not needed on Pi 3 B+)
  2. Write image to your USB device as above
  3. Mount the USB device on your computer and make following changes to /boot/config.txt under ‘Boot device’ section:
  4. Plug in the USB device to your Raspberry Pi, remove any sdcard, and boot

Lineage Power Driver Download Free

Q: How to boot to TWRP recovery?
A: You can boot to TWRP by selecting recovery option in Android power menu after enabling advanced restart options.

Also the previous method of executing following commands in ‘adb shell’/serial console/terminal still works:

If mouse cursor doesn’t appear, try replugging your mouse.

Lineage Power Driver Download

Q: How to boot out of TWRP recovery?
A: You can boot out of recovery by simply selecting reboot to system option in TWRP.

Lineage Power Driver Download

Q: How to update from previous LineageOS 17.1 build without losing data?
A:

  1. Boot to TWRP recovery with the build you want to keep the data (see FAQ)
  2. Plug in an external USB storage device and select ‘Backup’
  3. Use ‘Select Storage’ to choose the USB device and ‘Swipe to backup’ (it’s only necessary to backup the data partition so you can uncheck other partitions to speed up the process)
  4. Write new LineageOS 17.1 image to the sdcard following installation instructions
  5. Boot to TWRP recovery with the new build (see FAQ)
  6. Select ‘Restore’ and find the backup you created from the USB device (‘Select Storage’)
  7. Make sure you only have data selected as partitions to restore (uncheck other partitions if available) and select ‘Swipe to Restore’
  8. (Flash Google apps package/other add-ons you had previously installed)
  9. Boot out of recovery (see FAQ)

Q: How to install Google apps?
A: Warning, installing gapps slows things down especially on low-end devices with limited amount of RAM such as this one. I would strongly recommend against installing Google Apps on this device. Raspberry Pi 3 doesn’t have enough memory to provide decent user experience with Google Apps.

  1. Download open_gapps-arm-10.0-pico-xxxxxxxx.zip and save it to your device’s internal storage or use an external USB drive
  2. Boot to TWRP recovery (see FAQ)
  3. Install open_gapps-arm-10.0-pico-xxxxxxxx.zip from your selected storage
  4. Wipe->Factory reset!
  5. Boot out of recovery (see FAQ)

Merged commits not mentioned in the changelog.

8.11. changelog:

  • initial device settings for various Raspberry Pi specific options (Settings -> System -> Advanced settings)
    • audio device option (HDMI/3.5mm jack/audio DAC)
    • display options (graphics drivers, display resolution, display rotation)
    • options for IR remote, hardware keys, and RTC
  • simplify booting to/out of TWRP recovery (see FAQ)
  • improve support for booting from USB devices (see FAQ, thanks to maxwen)
  • improve support for RTC & IR remotes (see FAQ)
  • add more options for rotating touch input on Waveshare SPI (ADS7846) touchscreens (thanks to mikenon)
  • allow switching display off with power button
  • map right mouse button to back key
  • update to TWRP 3.4.0-1
  • update to Mesa 20.2.2 and latest upstream version of drm_hwcomposer
  • update to Linux 4.19.155 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
  • Android security patch level: 5 November 2020 (merged)

Lineage Power Driver Download Windows 10

13.8. changelog:

  • bring back forced landscape orientation for portrait apps
  • bring back support for running scripts from /system/etc/init.d/
  • read resolution from /boot/resolution.txt
  • fix issue with drm video playback
  • initial support for SSH server
  • update Mesa to 20.1.5
  • update to Linux 4.19.139 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
  • Android security patch level: 5 August 2020 (merged)

27.7. changelog:

  • initial LineageOS 17.1 build
  • hardware accelerated graphics
    • VC4 using Mesa 20.1.4 with drm_hwcomposer & minigbm gralloc
    • 1280x720 resolution
  • update TWRP to 3.4.0-0
  • update to Linux 4.19.134 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
  • Android security patch level: 5 July 2020 (merged)

Previous builds: