Template talk:Infobox device

From postmarketOS Wiki

references for "partial"

It is possible to add references to "partial" (P) cells to a section describing the open issue. Example: PINE64_PinePhone_(pine64-pinephone) has "Partial" for the "Camera" which should reference to the "Cameras" PINE64_PinePhone_(pine64-pinephone)#Cameras section White gecko (talk) 20:16, 27 November 2020 (UTC)

Add "No secure boot"

It is absolutely impossible to understand whether the vendor has flashed the "root of trust" in the SoC or not. You can't usually find it on the Internet. But those who have ported pmos and run lk2nd or mtkclient know this. But almost no one describes this on the wiki, so I can't understand if I'm buying a good device.

Refer to working Linux

Refer to working Linux systems (e.g. Droidian, UBports) only for devies that don't have enough of supported features for daily drive (i.e. day to day use by end user).

Scenario: I'd support the development of Monal (XMPP client) even though I'd not likely to use the proprietary OS it is built for.

Rational: Monal gives the rest of our friends a way to communicate with us in a way that let us keep using XMPP and not being forced into further compromising our means of private and open communications.

I rather people to use other Linux solutions so that they would also help themselves and help us in fixing and reporting Linux bugs of programs that postmarketOS users use.

I'm using SXMO on Nexus 5 and I didn't verify the following, so consider it as a realization:

According to devices.ubuntu-touch.io it appears that hammerhead is more usable, so until hammerhead is equally or better supported, a link to UBports may be a good idea.

Original Kernel (To Do)

First seen (by myself) at https://wiki.postmarketos.org/index.php?title=Xiaomi_POCO_F1_(xiaomi-beryllium)&action=edit

Software Version

The numbers are few so we are left with too much space.

|header7 =
|label7  = <abbr title="The version the device was shipped with.">Original version</abbr>
|data7   = {{{originalversion|}}}
|header8 =
|label8  = <abbr title="The most recent supported version from the manufacturer.">Extended version</abbr>
|data8   = {{{extendedversion|}}}

Perhaps something like this:

|header7 =
|label7  = <abbr title="The version the device was shipped with.">Original version</abbr>
|data7   = {{{originalversion|}}} -> {{{extendedversion|}}}
|header8 =
|label8  = 
|data8   = {{{extendedversion|}}}

Optional software

If we want to use optionalsoftware as category, then we have to provide multiple optionalsoftware keys.

As we know, optionalsoftware is originalsoftware in some devices.

type from wat

See also category:devices


The chassis type. Currently, the following chassis types are defined: "desktop", "laptop", "convertible", "server", "tablet", "handset", "watch", and "embedded", as well as the special chassis types "vm" and "container" for virtualized systems that lack an immediate physical chassis.

Reorder features box

Mainline, Flashing, FDE, Battery, Touchscreen, Display, 3D Acceleration, Camera, Audio, Calls, SMS, Mobile data, USB Networking, USB OTG, WiFi, Bluetooth, NFC, GPS,


Split "names"

This is too long when is in table.

Yet, when using title, some names would be missing from the table.

Example: POCO M2 Pro / Redmi Note 9S / Redmi Note 9 Pro / Redmi Note 9 Pro Max / Redmi Note 10 Lite

The above example requires 4 extra names.

Please advise.

Fixing Split "names"

I think i fixed it? I made the name/title sections split into different line and each line contain one of the split name if the device has multiple split names.

Need a place to leave alternate device codename


we already have model right?


Segregate chipset brand from its model, and automate reference to category "chipset".

|label13 = Chipset
|data13   = {{#if:{{{chipset|}}}|[[:Category:{{{chipset|}}}|{{{chipset}}}]]}} 
|label14 = Model
|data14   = {{#if:{{{chipset_model|}}}|[[{{{chipset_model|}}}]]}}

Improving armhf warning banner.

See Category_talk:Armhf


I have rephrased to tell the users should not buy that device as well as making armhf warning banner appear on armv7 device that use armhf port by changing them to armhf on their page.