Jump to content

User:MasanoriOgino: Difference between revisions

From postmarketOS Wiki
Devices: I have an EV3 by the way
 
(46 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Userbox container|
{{Userbox container|
   {{User main device|Generic x64 UEFI device}}
   {{User main device|Google Pixel 8 (google-shiba)}}
   {{User mainline attempts}}
   {{User mainline attempts}}
   {{User Matrix|@omasanori:matrix.org}}
   {{User Matrix|@omasanori:matrix.org}}
Line 7: Line 7:
}}
}}


I am Masanori Ogino, a computing cluster sysadmin in Japan. I am interested in computing, physics and linguistics. I have a personal website: [https://www.brackets-salad.com/ Brackets Salad]. I usually choose ''omasanori'' as my username. I am in favor of [https://gitlab.com/groups/postmarketOS/-/milestones/25 Immutable postmarketOS].
I am Masanori Ogino, a computing cluster sysadmin in Japan. I am interested in computing, physics and linguistics. I usually choose ''omasanori'' as my username. I have a personal website: [https://www.brackets-salad.com/ Brackets Salad]. I am the founder of [https://github.com/FUJIMI-IM FUJIMI], a Japanese input method community. I am in favor of [https://gitlab.com/groups/postmarketOS/-/milestones/25 Immutable postmarketOS].


== Current Targets ==
== Current Targets ==


=== Japanese language support of mobile Linux ecosystems ===
=== Improving Japanese language support and NLS in general ===
* {{issue|2069|pmaports}}: See {{MR|5540|pmaports}}
* Improve Maliit (on-screen keyboard used by KDE Plasma) Japanese plugin: [https://github.com/maliit/keyboard/issues/231 maliit#231] and [https://github.com/maliit/keyboard/issues/232 maliit#232]
* Package Noto variable fonts: See {{albug|16329}}
* Package Noto variable fonts: {{albug|16329}}
* Investigate Plasma Mobile on-screen keyboard bugs
* Package IBM Plex fonts


=== Porting and Mainlining ===
=== Porting and Mainlining ===
* Mainline [[LG Fx0 (lg-madai)]]: WIP [https://github.com/omasanori/linux/tree/lg-madai lg-madai] branch
* Mainline [[LG Fx0 (lg-madai)]]: WIP [https://github.com/omasanori/linux/tree/lg-madai lg-madai] branch
* Port postmarketOS to [[KING JIM POMERA DM200 (kingjim-onyx2)]]: Pending as I broke my DM200
* Port postmarketOS to [[Raspberry Pi Compute Module 4 (raspberry-picm4)]]
* Port postmarketOS to [[Google Pixel 6 (google-oriole)]]: Pending as I currently use my Pixel 6 as an Android phone
* Port postmarketOS to [[Google Pixel 6 (google-oriole)]]: Pending as I currently use my Pixel 6 as an Android phone
=== Maintaining pmOS Wiki ===
* Zero deprecated source tags on postmarketOS Wiki: See Category:Pages_using_deprecated_source_tags
* Write a wiki article on customizing fonts
* Survey on-screen keyboards and update [[Input methods]]


== Are We PinePhone Yet? ==
== Are We PinePhone Yet? ==
In the summer of 2024, I read [https://konradybcio.pl/pinephone-code/ PinePhone Is The Perfect Reason to Fix Bad Code] and I was impressed by the article.
In the summer of 2024, I read [https://konradybcio.pl/pinephone-code/ PinePhone Is The Perfect Reason to Fix Bad Code] and I was impressed by the article.


At the same time, I bought an used [[Apple iPhone 5s (apple-iphone5s)|iPhone 5s]] (2013) running iOS 12.5.7 (2023). The UI worked smoothly as if it is a recently released device. iPhone 5s has 2x 1 GHz 64-bit Arm CPU cores and 1 GB of RAM, while PinePhone has 4x 1 GHz 64-bit Arm CPU cores and 2 GB or 3 GB of RAM.
At the same time, I bought an used [[Apple iPhone 5s (apple-iphone5s)|iPhone 5s]] (2013) running iOS 12.5.7 (2023). The UI worked smoothly as if it was a recently released device. iPhone 5s has 2x 1 GHz 64-bit Arm CPU cores and 1 GB of RAM, while PinePhone has 4x 1 GHz 64-bit Arm CPU cores and 2 GB or 3 GB of RAM.


Apple did it. Ten years of iPhone 5s! Can we make [[PINE64 PinePhone (pine64-pinephone)|PinePhone]] (2020) in 2030 viable?
Apple did it. Ten years of iPhone 5s! Can we make [[PINE64 PinePhone (pine64-pinephone)|PinePhone]] (2020) in 2030 viable?
Line 31: Line 36:


== Random Ideas ==
== Random Ideas ==
* Zero deprecated source tags on postmarketOS Wiki: See Category:Pages_using_deprecated_source_tags
* Revise [[Kernel_configuration/Adjusting_one_kernel]] and [[Installing_packages_on_a_running_phone]] to make them consistent
* Use Alpine Linux or postmarketOS on my dev laptop PC
* Use Alpine Linux or postmarketOS on my dev laptop PC
* Font-related
* Try [https://codeberg.org/a13xp0p0v/kernel-hardening-checker kernel-hardening-checker] and evaluate performance penalty on some devices
** IBM Plex
** fontconfig setting overhaul
* Security-related
** Try [https://codeberg.org/a13xp0p0v/kernel-hardening-checker kernel-hardening-checker] and evaluate performance penalty on some devices
** LSM. Which ones?
* Port postmarketOS to BeagleBone Black
* Port postmarketOS to BeagleBone Black
** Using omapdrm as the current PVRSGX DRM driver is out-of-tree and will not be supported by postmarketOS. See {{issue|1316|pmaports}}
** Using omapdrm as the current PVRSGX DRM driver is out-of-tree and will not be supported by postmarketOS. See {{issue|1316|pmaports}}
Line 53: Line 51:
{{Owns device|Fujitsu_F-08E_(fujitsu-f08e)}}
{{Owns device|Fujitsu_F-08E_(fujitsu-f08e)}}
{{Owns device|Google_Nexus_5_(lg-hammerhead)}}
{{Owns device|Google_Nexus_5_(lg-hammerhead)}}
{{Owns device|Google_Pixel_3_(google-blueline)}}
{{Owns device|Google_Pixel_3_(google-blueline)|UFS 128 GB Micron}}
{{Owns device|Google_Pixel_3a_(google-sargo)}}
{{Owns device|Google_Pixel_3a_(google-sargo)|eMMC 64 GB SKHynix}}
{{Owns device|Google_Pixel_6_/_6_Pro_(google-oriole_/_google-raven)|oriole 128 GB}}
{{Owns device|Google_Pixel_6_/_6_Pro_(google-raviole)|oriole, UFS 128 GB SKHynix}}
{{Owns device|https://wiki.postmarketos.org/wiki/Google_Pixel_8_/_8_Pro_(google-shiba_/_google-husky)}}
{{Owns device|Google_Pixel_8_/_8_Pro_(google-shusky)|shiba, UFS 128 GB Samsung}}
{{Owns device|Lego_Mindstorms_EV3_(lego-ev3)}}
{{Owns device|LG_Fx0_(lg-madai)|2x}}
{{Owns device|LG_Fx0_(lg-madai)|2x}}
{{Owns device|PINE64_PinePhone_(pine64-pinephone)|1.2a}}
{{Owns device|PINE64_PinePhone_(pine64-pinephone)|1.2a}}
Line 62: Line 61:
{{Owns device|Raspberry_Pi_3_(raspberry-pi3)}}
{{Owns device|Raspberry_Pi_3_(raspberry-pi3)}}
{{Owns device|Raspberry_Pi_4_(raspberry-pi4)}}
{{Owns device|Raspberry_Pi_4_(raspberry-pi4)}}
{{Owns device|Raspberry_Pi_Compute_Module_4_(raspberry-picm4)|1x CM4001000 Rev.5, 1x CM4108032 Rev.5}}
{{Owns device|Raspberry_Pi_Compute_Module_4_IO_Board_(raspberry-picm4ioboard)}}
{{Owns device|Toshiba_Excite_7c_(toshiba-at7b)|3x}}
{{Owns device|Toshiba_Excite_7c_(toshiba-at7b)|3x}}
</div>
</div>

Latest revision as of 07:19, 1 October 2024

📱 This user's main device is a Google Pixel 8 (google-shiba).
🐧 This user is currently trying to mainline a device.
Element logo This user has a Matrix account.
SourceHut logo This user has a SourceHut profile.

I am Masanori Ogino, a computing cluster sysadmin in Japan. I am interested in computing, physics and linguistics. I usually choose omasanori as my username. I have a personal website: Brackets Salad. I am the founder of FUJIMI, a Japanese input method community. I am in favor of Immutable postmarketOS.

Current Targets

Improving Japanese language support and NLS in general

  • Improve Maliit (on-screen keyboard used by KDE Plasma) Japanese plugin: maliit#231 and maliit#232
  • Package Noto variable fonts: alpine#16329
  • Package IBM Plex fonts

Porting and Mainlining

Maintaining pmOS Wiki

  • Zero deprecated source tags on postmarketOS Wiki: See Category:Pages_using_deprecated_source_tags
  • Write a wiki article on customizing fonts
  • Survey on-screen keyboards and update Input methods

Are We PinePhone Yet?

In the summer of 2024, I read PinePhone Is The Perfect Reason to Fix Bad Code and I was impressed by the article.

At the same time, I bought an used iPhone 5s (2013) running iOS 12.5.7 (2023). The UI worked smoothly as if it was a recently released device. iPhone 5s has 2x 1 GHz 64-bit Arm CPU cores and 1 GB of RAM, while PinePhone has 4x 1 GHz 64-bit Arm CPU cores and 2 GB or 3 GB of RAM.

Apple did it. Ten years of iPhone 5s! Can we make PinePhone (2020) in 2030 viable?

In short, Are We PinePhone Yet? is my personal project making ten years of PinePhone great. The naming was borrowed from existing Are We ... Yet? websites.

Random Ideas

  • Use Alpine Linux or postmarketOS on my dev laptop PC
  • Try kernel-hardening-checker and evaluate performance penalty on some devices
  • Port postmarketOS to BeagleBone Black
    • Using omapdrm as the current PVRSGX DRM driver is out-of-tree and will not be supported by postmarketOS. See pmaports#1316
    • As a playground of PowerVR SGX in the future
  • RISC-V stuff (DeepComputing's DC-ROMA series looks good imho)
  • Try https://github.com/P1sec/QCSuper and related software stack on a Qualcomm device

Devices

Device Notes
Apple iPhone 5s (apple-iphone5s) 32 GB
Fujitsu F-08E (fujitsu-f08e)
Google Nexus 5 (lg-hammerhead)
Google Pixel 3a (google-sargo) eMMC 64 GB SKHynix
Google Pixel 3 (google-blueline) UFS 128 GB Micron
Google Pixel 6 / 6 Pro (google-raviole) oriole, UFS 128 GB SKHynix
Google Pixel 8 / 8 Pro (google-shusky) shiba, UFS 128 GB Samsung
Lego Mindstorms EV3 (lego-ev3)
LG Fx0 (lg-madai) 2x
PINE64 PinePhone (pine64-pinephone) 1.2a
Purism Librem5 (purism-librem5) Evergreen
Raspberry Pi 3 (raspberry-pi3)
Raspberry Pi 4 (raspberry-pi4)
Raspberry Pi Compute Module 4 (raspberry-picm4) 1x CM4001000 Rev.5, 1x CM4108032 Rev.5
Raspberry Pi Compute Module 4 IO Board (raspberry-picm4ioboard)
Toshiba Excite 7c (toshiba-at7b) 3x