Commit graph

13 commits

Author SHA1 Message Date
Nikita Travkin
fe54a7be49
device/msm8916*: Generate extlinux.conf (MR 4826)
Now as boot-deploy allows us to generate both boot.img and extlinux.conf
at the same time, enable generating the config for all msm8916 since it
will be used in the future lk2nd release. boot.img is still kept to keep
compatibility with current lk2nd releases and to allow system recovery
with fastboot when required.

[ci:skip-build] already built successfully in CI
[ci:ignore-count]
2024-02-15 11:34:55 -08:00
Pablo Correa Gómez
cf69326222
device/*: rebuild all devices (MR 4551)
[ci:ignore-count]
2024-01-22 19:32:30 +01:00
Pablo Correa Gómez
ea93a6d07f
device/*: rebuild all devices to relocate deviceinfo (MR 4283)
[ci:ignore-count]
[ci:skip-build]: already built successfully in CI
2023-09-25 09:21:03 +02:00
Raymond Hackley
a2d1c2e97e
samsung-{a2015,e2015}: add rt5033 modules to initfs (MR 4402)
Add rt5033 modules to initfs for the following devices, to unlock FDE with
USB OTG keyboards:

- Samsung Galaxy A3/A5/A7
- Samsung Galaxy E7
- Samsung Galaxy Grand Max
2023-09-19 04:19:39 +00:00
Pablo Correa Gómez
4914067590
device/*: transform deviceinfo_modules_initfs into a file (MR 4169)
The file is automatically packed by devicepkg-dev utils

Relates #1836
2023-08-04 08:27:44 +02:00
Raymond Hackley
6f074ad61d
samsung-*: Add USB ID (MR 3469)
Some devices have 04e8:6860 as their USB ID. Add it to deviceinfo.

[ci:ignore-count]
[ci:skip-build]: already built successfully in CI
2022-09-28 09:10:57 +02:00
Minecrell
6c628d66ed
samsung-{a3,a5}: also apply ModemManager "facility lock" workaround (MR 3021)
It seems like at least samsung-a5 needs the same "facility lock"
workaround as samsung-serranove, otherwise ModemManager can not detect
the SIM card correctly. Move it to a subpackage of soc-qcom-msm8916
and apply it to samsung-a3 as well just to be sure.

So far this issue seems limited to Samsung devices, at least bq-paella
is not affected (tested with the same SIM card), so it does not seem
right to apply it unconditionally to all devices.

[ci:skip-build] Already built successfuly on CI in MR
2022-03-27 16:34:39 +02:00
Raymond Hackley
9833cc8a64
samsung-{a3,a5,a7,klte,serranove}: move tm2-touchkey rules to pmos-base (MR 2926)
Fixes: #1422
2022-03-03 19:21:20 +03:00
Oliver Smith
eb21ed5472
device/*/device-*: rebuild for new splash screens (MR 2222)
[ci:ignore-count]
2022-01-22 13:40:33 +01:00
Jakob Hauser
c655f5cc9c
samsung-a3|a5|klte|serranove: remap left touch key (MR 2718)
Remapping the left key of tm2-touchkey to KEY_MENU.

The KEY_APPSELECT, which is set by the device tree, is not available in
the postmarketOS UIs. In X11 UIs this is due to keycode limitation to
8 bit. In Wayland UIs the keycodes don't have this limitation but xkb
keycodes higher 255 are not processed correctly by several software
packages. It still makes sense to keep KEY_APPSELECT in the device tree
because this is the correct mapping intended by the manufacturers when
running the kernel on Android.
2021-12-05 21:34:10 +01:00
Minecrell
dd935c0d58
community/<msm8916>: use _pmb_select="..." instead of kernel variants (MR 2632) 2021-11-21 19:10:58 +01:00
Minecrell
eff90a2071
<msm8916+secure boot-venus>: use separate firmware packages (MR 2619)
Rule D: Devices with secure boot and venus present in the firmware
        partition need:

  1. GPU firmware (firmware-qcom-adreno-a300)
  2. msm-firmware-loader (for wcnss, modem, venus)
  4. device-specific -wcnss-nv firmware

[ci:ignore-count]
[ci:skip-build] already built successfully in CI
2021-10-23 14:41:30 -07:00
Nikita Travkin
a1688878a2
samsung-a5*: squash to a5, use msm-firmware-loader (MR 2431)
Right now we have multiple variants of A5 that are only different in
secure-boot keys and as such different firmware blobs.
Use msm-firmware-loader to support all A5 variants with a single device
port. Because of that, drop lte suffix as there are 3g variants as well.
2021-09-27 15:23:50 +03:00
Renamed from device/community/device-samsung-a5ulte/APKBUILD (Browse further)