Plasma Mobile Documentation Website issueshttps://invent.kde.org/documentation/docs-plasma-mobile-org/-/issues2020-12-10T16:03:20Zhttps://invent.kde.org/documentation/docs-plasma-mobile-org/-/issues/14Missing rootfs_stamp and other issues with the pm-flash and rootstock-touch-i...2020-12-10T16:03:20ZJames RichardsonMissing rootfs_stamp and other issues with the pm-flash and rootstock-touch-install scripts (Documentation Opportunity)I'm attempting install on a Nexus 5X (bullhead) and when running the pm-flash utility, the script checks for the latest rootfs version by curl-ing the URL: "https://images.plasma-mobile.org/rootfs_stamp" (Line 55)
This step fails becaus...I'm attempting install on a Nexus 5X (bullhead) and when running the pm-flash utility, the script checks for the latest rootfs version by curl-ing the URL: "https://images.plasma-mobile.org/rootfs_stamp" (Line 55)
This step fails because that rootfs_stamp file does not exist in that web folder.
![curl_error](/uploads/a3961f669aac3f85bf421ff74feb9ea5/curl_error.png)
![rootfs_stamp_url](/uploads/e7f81cd4d367a632a5900ee657e4d456/rootfs_stamp_url.png)
I am able to update the script, bypassing the version check and plugging in the latest version manually into the ROOTFS_VERSION variable assignment to get past this hurdle.
![ROOTFS_VERSION](/uploads/e99d686af9fd0a2e70cead4db7385b9f/ROOTFS_VERSION.png)
The next hurdle I hit is when it is done downloading the rootfs, system, recovery, and boot, and it reboots to TWRP recovery. I'm not sure if this is happening because I already had TWRP installed or if your recovery.img is TWRP, but when it boots, the /cache and /data partitions are already mounted. So the mount commands in the rootstock-touch-install script (lines 41-49) fail with a device or resource busy.
![mount_error](/uploads/e64d754b873a898372d0c2e2df070e03/mount_error.png)
If I modify the pm-flash script further by replacing the "wait_for_device" function call at line 93 with a "read -p" pause to give myself a chance to go into TRWP and unmount those two partitions, then when I let the script continue, it gets through those mounting commands and the script continues through to my next hurdle.
For my last hurdle, the fetch-demo.sh script called in the rootstock-touch-install script (lines 159-165) always runs. There does not seem to be any IF statement to let us specify if we want demo content or not. And the fetch fails because of a 404 error.
![demo_fetch_error](/uploads/1efb99f57ca4a7f35be40835eaf09c8f/demo_fetch_error.png)
If I comment out that section of the rootstock-touch-install script to prevent it from downloading the demo data, the pm-flash script completes all steps without any errors. Unfortunately, my bullhead device fails to boot. It is just stuck at the Google boot-logo screen. I can reboot it into recovery but that is it.
Then I found this thread: https://forum.kde.org/viewtopic.php?f=297&t=150546 that pointed me to the flash_vendor script included in the pm-flashtool folder. I ran that script, then re-ran my modified pm-flash script and all is good!https://invent.kde.org/documentation/docs-plasma-mobile-org/-/issues/13Consider moving development documentation to develop.kde.org2020-09-14T06:24:27ZBhushan ShahConsider moving development documentation to develop.kde.orgCC: @carlschwan @jbbgameich @nicolasfella
Thoughts?CC: @carlschwan @jbbgameich @nicolasfella
Thoughts?https://invent.kde.org/documentation/docs-plasma-mobile-org/-/issues/12Add instructions on how to install Plasma Mobile on PinePhone2020-03-08T21:09:47Zcah fofpaiAdd instructions on how to install Plasma Mobile on PinePhoneNot only KDE Neon provides Plasma Mobile on the PinePhone, but also PostmarketOS and Manajro. Links can be found at https://wiki.pine64.org/index.php/PinePhone#Operating_Systems .Not only KDE Neon provides Plasma Mobile on the PinePhone, but also PostmarketOS and Manajro. Links can be found at https://wiki.pine64.org/index.php/PinePhone#Operating_Systems .https://invent.kde.org/documentation/docs-plasma-mobile-org/-/issues/11Should the documentation be translated?2019-09-12T09:00:29ZJonah BrĂ¼chertShould the documentation be translated?We can easily generate gettext catalogs using `make gettext`. This could probably somehow be given to the translation team and the result could be directly be used by sphinx to build localized documentation using `make -e SPHINXOPTS="-D ...We can easily generate gettext catalogs using `make gettext`. This could probably somehow be given to the translation team and the result could be directly be used by sphinx to build localized documentation using `make -e SPHINXOPTS="-D language='ja'" html`.https://invent.kde.org/documentation/docs-plasma-mobile-org/-/issues/10Be more descriptive about the QEMU user static2019-02-12T12:56:25ZBhushan ShahBe more descriptive about the QEMU user staticCurrently documentation just tells to install qemu-user-static and binfmt support packages, but doesn't explain rationale and/or how to do that.
See also #9Currently documentation just tells to install qemu-user-static and binfmt support packages, but doesn't explain rationale and/or how to do that.
See also #9https://invent.kde.org/documentation/docs-plasma-mobile-org/-/issues/9Add a troubleshooting guide for qemu-user-static2019-02-12T12:56:25ZBhushan ShahAdd a troubleshooting guide for qemu-user-staticIn theory, qemu-user-static works just out of box, but for some distribution it needs manual tinkering, document this in application development under troubleshooting page.In theory, qemu-user-static works just out of box, but for some distribution it needs manual tinkering, document this in application development under troubleshooting page.https://invent.kde.org/documentation/docs-plasma-mobile-org/-/issues/8Document the infrastructure2019-02-05T18:26:47ZSimon SchmeisserDocument the infrastructureAdd explanation about
neon based: https://build.plasma-mobile.org/ https://github.com/bhush9/rootfs-builder/tree/pm-bionic
debian-pm: ...Add explanation about
neon based: https://build.plasma-mobile.org/ https://github.com/bhush9/rootfs-builder/tree/pm-bionic
debian-pm: ...https://invent.kde.org/documentation/docs-plasma-mobile-org/-/issues/7Mention about Gitlab CI for flatpak builds2019-01-05T12:44:58ZBhushan ShahMention about Gitlab CI for flatpak buildsCurrent docs mention the `flatpak-kde-applications` repository, currently we don't offer ARM builds in Gitlab CI but probably it will be soon,
Link to https://invent.kde.org/sysadmin/ci-tooling/wikis/Gitlab-CI#flatpak and modify instru...Current docs mention the `flatpak-kde-applications` repository, currently we don't offer ARM builds in Gitlab CI but probably it will be soon,
Link to https://invent.kde.org/sysadmin/ci-tooling/wikis/Gitlab-CI#flatpak and modify instructions.https://invent.kde.org/documentation/docs-plasma-mobile-org/-/issues/6Flashing KDE Neon mobile page links to community wiki page.2020-09-10T09:48:14ZBhushan ShahFlashing KDE Neon mobile page links to community wiki page.https://docs.plasma-mobile.org/FlashingNeon.html
links to,
https://community.kde.org/Raspberry_Pi
Should RPi page be moved to website?https://docs.plasma-mobile.org/FlashingNeon.html
links to,
https://community.kde.org/Raspberry_Pi
Should RPi page be moved to website?https://invent.kde.org/documentation/docs-plasma-mobile-org/-/issues/5Flashing neon page have duplicated content2020-09-10T09:47:19ZBhushan ShahFlashing neon page have duplicated contenthttps://docs.plasma-mobile.org/FlashingNeon.html
https://www.plasma-mobile.org/neon-arch-reference-rootfs/
Remove docs.plasma-mobile.org page?https://docs.plasma-mobile.org/FlashingNeon.html
https://www.plasma-mobile.org/neon-arch-reference-rootfs/
Remove docs.plasma-mobile.org page?https://invent.kde.org/documentation/docs-plasma-mobile-org/-/issues/4Placeholder contributing page2020-09-10T09:51:16ZBhushan ShahPlaceholder contributing pagehttps://docs.plasma-mobile.org/Contributing.html
Doesn't really have much info,
https://www.plasma-mobile.org/contributing/ is more complete, perhaps remove docs.plasma-mobile.org page?https://docs.plasma-mobile.org/Contributing.html
Doesn't really have much info,
https://www.plasma-mobile.org/contributing/ is more complete, perhaps remove docs.plasma-mobile.org page?https://invent.kde.org/documentation/docs-plasma-mobile-org/-/issues/3Move FAQ to plasma-mobile.org2019-11-11T07:31:11ZBhushan ShahMove FAQ to plasma-mobile.orgIn general current FAQ we have is more suitable for the plasma-mobile.org repo, move it to websites/plasma-mobile-org> repository which uses jekyll.
We might keep FAQ page for development related queries.In general current FAQ we have is more suitable for the plasma-mobile.org repo, move it to websites/plasma-mobile-org> repository which uses jekyll.
We might keep FAQ page for development related queries.https://invent.kde.org/documentation/docs-plasma-mobile-org/-/issues/2Empty Plasma Mobile Tester guide page2020-09-10T09:41:57ZBhushan ShahEmpty Plasma Mobile Tester guide pagehttps://docs.plasma-mobile.org/TesterGuide.html
add content, or remove page. Looks largely related to the https://docs.plasma-mobile.org/DevGuide.html
Maybe makes sense to rename DevGuide to TesterGuide and remove empty page?https://docs.plasma-mobile.org/TesterGuide.html
add content, or remove page. Looks largely related to the https://docs.plasma-mobile.org/DevGuide.html
Maybe makes sense to rename DevGuide to TesterGuide and remove empty page?https://invent.kde.org/documentation/docs-plasma-mobile-org/-/issues/1Add section on using Plasma Mobile on postmarketOS using QEMU2018-12-28T14:35:17ZBhushan ShahAdd section on using Plasma Mobile on postmarketOS using QEMUCurrently we have postmarketOS mentioned only in Devices section and not emulated environment.
https://docs.plasma-mobile.org/DevGuide.html#using-postmarketos
Either make postmarketOS instructions generic, or add another section under ...Currently we have postmarketOS mentioned only in Devices section and not emulated environment.
https://docs.plasma-mobile.org/DevGuide.html#using-postmarketos
Either make postmarketOS instructions generic, or add another section under emulated environment.