forge/pmaports
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
pmaports/device/device-motorola-titan/APKBUILD

34 lines
1.3 KiB
Text
Raw Normal View History

APKBUILD + deviceinfo (work in progress) - Removed ACTIVATE_DOWNLOAD_MODE.txt and ACTIVATE_RECOVERY.txt From lineage-14.1-20170602-nightly-titan-signed.zip $ unpackbootimg -i boot.img Android magic found at: 0 BOARD_KERNEL_CMDLINE androidboot.bootdevice=msm_sdcc.1 androidboot.hardware=qcom vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags buildvariant=userdebug BOARD_KERNEL_BASE 00008000 BOARD_RAMDISK_OFFSET 01000000 BOARD_SECOND_OFFSET 00f00000 BOARD_TAGS_OFFSET 00000100 BOARD_PAGE_SIZE 2048 BOARD_SECOND_SIZE 0 BOARD_DT_SIZE 1763328
2017-06-04 11:42:38 +00:00
pkgname=device-motorola-titan
Porting to Moto G 2014 "titan" - Use samsung-i9100 as template
2017-06-04 11:37:14 +00:00
pkgver=1
Implement sparse system images (fix #299) (#303) * Packaged libsparse libsparse from the Android project provides multiple tools like img2simg and simg2img. These are used to split a large image for the system partition into separate smaller chunks with sparse headers This is required for several devices (at least bullhead, fp2 and titan) because it fixes the "Invalid sparse file format at header magi" error https://github.com/postmarketOS/pmbootstrap/issues/299 * Added new variable deviceinfo_flash_sparse (fixes #299) Right after the system image is generated, pmbootstrap checks this variable. In case it is true, run img2simg on it * motorola-titan: enable deviceinfo_flash_sparse * libsparse: use source from github: anestisb/android-simg2img It is not that easy to use the upstream archive because everytime you download it, the files have the current date as creation date and that makes the file have a different checksum every download https://github.com/postmarketOS/pmbootstrap/pull/303#issuecomment-319017197
2017-08-02 16:21:50 +00:00
pkgrel=10
APKBUILD + deviceinfo (work in progress) - Removed ACTIVATE_DOWNLOAD_MODE.txt and ACTIVATE_RECOVERY.txt From lineage-14.1-20170602-nightly-titan-signed.zip $ unpackbootimg -i boot.img Android magic found at: 0 BOARD_KERNEL_CMDLINE androidboot.bootdevice=msm_sdcc.1 androidboot.hardware=qcom vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags buildvariant=userdebug BOARD_KERNEL_BASE 00008000 BOARD_RAMDISK_OFFSET 01000000 BOARD_SECOND_OFFSET 00f00000 BOARD_TAGS_OFFSET 00000100 BOARD_PAGE_SIZE 2048 BOARD_SECOND_SIZE 0 BOARD_DT_SIZE 1763328
2017-06-04 11:42:38 +00:00
pkgdesc="Motorola Moto G 2014"
Porting to Moto G 2014 "titan" - Use samsung-i9100 as template
2017-06-04 11:37:14 +00:00
url="https://github.com/postmarketOS"
arch="noarch"
license="MIT"
deviceinfo_generate_bootimg
2017-06-25 22:36:11 +00:00
depends="linux-motorola-titan mkbootimg"
Porting to Moto G 2014 "titan" - Use samsung-i9100 as template
2017-06-04 11:37:14 +00:00
makedepends=""
install=""
subpackages=""
udev rule to use touchscreen + calibration
2017-06-25 22:07:27 +00:00
source="deviceinfo 90-android-touch-dev.rules initfs-hook.sh profile.sh"
Porting to Moto G 2014 "titan" - Use samsung-i9100 as template
2017-06-04 11:37:14 +00:00
options="!check"
build() {
return 0
}
package() {
install -D -m644 "$srcdir/deviceinfo" \
"$pkgdir/etc/deviceinfo"
udev rule to use touchscreen + calibration
2017-06-25 22:07:27 +00:00
install -D -m644 "$srcdir"/90-android-touch-dev.rules \
"$pkgdir"/etc/udev/rules.d/90-android-touch-dev.rules
Added profile.sh and initfs-hook hacks Weston works! (and has red screen bug) Note: I have to manually ssh and sh /etc/postmarketos-mkinitfs/hooks/00-device-motorola-titan.sh
2017-06-26 21:46:37 +00:00
install -D -m644 "$srcdir"/initfs-hook.sh \
"$pkgdir"/etc/postmarketos-mkinitfs/hooks/00-${pkgname}.sh
install -D -m644 "$srcdir"/profile.sh \
"$pkgdir"/etc/profile.d/00-$pkgname.sh
Porting to Moto G 2014 "titan" - Use samsung-i9100 as template
2017-06-04 11:37:14 +00:00
}
Implement sparse system images (fix #299) (#303) * Packaged libsparse libsparse from the Android project provides multiple tools like img2simg and simg2img. These are used to split a large image for the system partition into separate smaller chunks with sparse headers This is required for several devices (at least bullhead, fp2 and titan) because it fixes the "Invalid sparse file format at header magi" error https://github.com/postmarketOS/pmbootstrap/issues/299 * Added new variable deviceinfo_flash_sparse (fixes #299) Right after the system image is generated, pmbootstrap checks this variable. In case it is true, run img2simg on it * motorola-titan: enable deviceinfo_flash_sparse * libsparse: use source from github: anestisb/android-simg2img It is not that easy to use the upstream archive because everytime you download it, the files have the current date as creation date and that makes the file have a different checksum every download https://github.com/postmarketOS/pmbootstrap/pull/303#issuecomment-319017197
2017-08-02 16:21:50 +00:00
sha512sums="09abd5f4681d9479650cfa64fcbc58528827017757539c3faf142ca92e8537691f9fb88f5d84ece086af7f23be2ac03e196f49ae708a832f1331f40cc96bab29 deviceinfo
Changes done after code review
2017-06-28 17:27:34 +00:00
f37e6324abf0b0fc8a3d360d6d11bb0648090a438a55ca7f04a9d494719e687ce445ae107ace642edf293afb6ca82615bcb5d0ddb6c46c1a7f8ee3c213b7c5c4 90-android-touch-dev.rules
Added profile.sh and initfs-hook hacks Weston works! (and has red screen bug) Note: I have to manually ssh and sh /etc/postmarketos-mkinitfs/hooks/00-device-motorola-titan.sh
2017-06-26 21:46:37 +00:00
8590967fa10388a890fdfafdb1070b9ab22dc89e06a3a8834806c772191e3b67de7b914b0d68e5ddf581cee715cb90f3f24abcb8762c415ff328c6da23e55d52 initfs-hook.sh
Handle generating weston.ini in post-install script (#201) This PR automatically creates the weston.ini in the postmarketos-base post-install script based on options set in the deviceinfo file for a particular device. This replaces #191. If weston.ini exists, then no modifications are made. (Optional) options supported in this PR for deviceinfo are: deviceinfo_weston_core_modules - defaults to NONE if none specified deviceinfo_weston_core_backend - defaults to 'fbdev-backend.so' if none specified deviceinfo_weston_keymap_rules - keymap rule, found under /usr/share/X11/xkb/rules/ deviceinfo_weston_keymap_model - keymap model
2017-07-21 19:46:40 +00:00
2f7cdf558a6bff56fd343d29a1ca6c27e75715bedfad661700dfcfb01acd1bdfcfecdfccf619f1e56c1e6331be146f8882a14d3a2cd33830e9d00bb6118971a3 profile.sh"
Reference in a new issue Copy permalink