two years blog post (2019-06-23)
Add structure, write introduction, add more quotes to start page (having only one quote talking about 1 year of pmOS is a bit thin at this point in time).
Closes #105 (closed)
I've recycled two images from the old start page in the introduction section. As always, feedback welcome, let me know if I forgot something in the headlines.
Preview as rendered by gitlab (lots of unsupported markup in there): https://gitlab.postmarketos.org/postmarketos/postmarketos.org/blob/2y-post/content/blog/2019-06-23-two-years.md
Latest screenshot: Screenshot_2019-06-23_postmarketOS_Two_years_of_postmarketOS
Merge request reports
Activity
added blog post label
added 17 commits
-
8f41e0cd...f42fd8e1 - 15 commits from branch
master - 28cf7870 - WIP: two years blog post
- c0144b43 - Start writing about UI changes/some restructuring
By Oliver Smith on 2019-06-04T18:32:54
-
8f41e0cd...f42fd8e1 - 15 commits from branch
I am currently working on mainlining my sm-a300fu (Samsung Galaxy A3 2015). lambdadroid is working on sm-a500fu, which is similar. There are some other similar samsung phones with msm8916, which should be easy to start mainlining thanks to easily accessible UART and almost ootb usb. My very wip mainline fork (rebased on linaro's qcom integration, but should work on mainline; will test again once the feature I thought I needed lands in mainline, should be 5.3 iirc) is at https://gitlab.com/Mis012/sm-a300fu-mainlining_wip ;
It should be just dts and the panel driver, but don't count on my memory ;)
Working features:
SMP - CPU cores power management depends on PSCI on aarch64, which is implemented in (signed) trustzone and only on the dragonboard 410c of all msm8916 devices wifi: (needs firmware that smells like OEM signed trustlet)
serial port: (multiplexed on microusb port in standard Samsung fashion. Is actually so.called blsp, so could in theory be used as spi/i2c/gpio instead)
gpio keys: volume up and home button
power/reset keys: power-on button and volume down (connected to pm8916 reset for hard reset without battery removal - that one would require unglueing the display)
hall sensor: actually a reed switch connected to a gpio. used as lid switch sdhci: emmc works flawlessly; microsd not tested
nfc: driver in mainline, should work - but can't test (neard doesn't compile, and not sure if it supports android beam as that's all that I have regarding nfc)
usb: works; only device mode tested sm5502 MUIC: driver in mainline, not sure if otg host mode detection is wired up to usb drivers
rt5033 charging ic: regulators and battery gauge supported in mainline, other functions not; phone seems to be charging in any case, unsure about safety functions like trickle charge
display: works with basic custom panel driver; GPU acceleration working on mesa 18.x, should work in latest 19.1 git tree with adreno a3xx regressions fixed; simple-framebuffer driver works, but is useless because freedreno doesn't support handover (yet)
Not working zinitix bt532(541?) touchscreen - working on writing the driver atm "back" and "multitask" touchkeys - are not really needed, and are implemented using an 8051 based MCU with flash memory (not many rewrite cycles though) and no signature verification, which means they may serve as a fun liberation chalange and are not worth porting otherwise.
bluetooth - throws some error in dmesg
modem - not tested, no plans to test because the firmware is probably not trustworthy
bmc150 accelerometer/magnetometer - bma150 is in mainline, no idea if it's similar
gps - not tested, no idea if driver is in mainline (chip is qcom's as is wifi/bt) sound - works on dragonboard, not sure how much that helps audio jack insertion/button press detection - will look into when sound works proximity sensor - similar one is in mainline; has a gpio-connected ir led - would be cool if it worked with lirc :P
cameras - no idea how that will workBy Mis012 on 2019-06-07T20:05:27
Edited by Administratoradded 1 commit
- fcd88c31 - Add lots of content for the UIs, some restructuring
By Oliver Smith on 2019-06-08T01:55:01
-
@Mis012: thanks! let's fit some of that into the mainlining section of the post.
Four hours more put into it, here's the next version. I've uploaded a screenshot (see initial post at the top).
The UI sections are slowly heading towards completion. plamo and shelli still consist of bullet points, and 150x150 images for the bottom parts of coreapps and phosh sections are missing. I have added two videos, and a shorter thumbnail video for each of them.
@unrznbl: would you like to write out the Shelli section? (EDIT: done)
@PureTryOut: would you like to write out the PlaMo section?
That would help out a lot, as you can see writing these posts takes lot of time. It should be easier now, that bullet points and the layout are already there. The README.md explains how to run the blog locally, in case you want to do that (only needed for previewing, not for writing text obviously).
If anybody else wants to write out a section, or add missing images (e.g. thumbnails for CoreApps, take them from the wiki page), be my guest, I highly appreciate it.
@rahmanshaber: I've also written a section about CoreApps. What do you think about it, anything to correct there?
@danct12: FYI I'm not planning to add a screenshot next to the Sway section; we already have much UI stuff there, and it is not much of a mobile UI, so I doubt that there would be much benefit in it.
Reviewing is appreciated as well :)
By Oliver Smith on 2019-06-21T03:47:14
Edited by Administrator -
@ollieparanoid just reviewed the very nice shelli section, looks great! And thanks!!! Been too busy this month to contribute much. :)
By Craig Comstock on 2019-06-21T03:47:14
-
@danct12: FYI I'm not planning to add a screenshot next to the Sway section; we already have much UI stuff there, and it is not much of a mobile UI, so I doubt that there would be much benefit in it.
It's fine, I don't need to see sway on a phone without a keyboard.
By Danct12 on 2019-06-08T02:14:12
-
@GrantM11235 I would be glad to see my work here ;)
I can take some photos if you want.
Just to say, device support is still WIP - I have some things uncommited, like 5GHz WiFi fixed, working charging, etc. I'll finish my work soon and send the changes.
By Sergey Larin on 2019-06-10T15:44:39
Edited by Ghost User
-
@ollieparanoid thanks a lot.
i will put some light on our little project. soon we will release the v2.6 with fix for the theme. Now CoreApps will use system theme.
can you also mention the group(including me in the group) that are working on the CoreApps project.
By rahmanshaber on 2019-06-08T14:27:45
Edited by Administrator -
I have started with the mainlining section now. Added an intro, and wrote about samsung-maguro. I've simplified it a bit by not mentioning the sleeps that were used in initial debugging, but also mentioned that it was simplified. (and I think it makes sense not to go into more detail there, it is already quite long.)
@drebrez: what do you think?
For the other mainlining devices, I plan to only write a few sentences for each device; we can't make each of them that long obviously. But drebrez' efforts are the best documented ones I think, so it makes sense to dive a bit deeper in there.
Regarding the date, I've moved it by one week, new target is 2019-06-22.
By Oliver Smith on 2019-06-11T20:16:16
Edited by Ghost User -
@ollieparanoid I think you summed up very well, thank you very much
By Daniele Debernardi on 2019-06-11T20:16:16