<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Sriram Ramkrishna &#8211; Purism</title>
	<atom:link href="https://puri.sm/posts/author/sriram/feed/" rel="self" type="application/rss+xml" />
	<link>https://puri.sm/</link>
	<description>High-quality laptops that protect your freedom and privacy</description>
	<lastBuildDate>Mon, 09 Nov 2020 16:41:35 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.9.16</generator>

<image>
	<url>https://puri.sm/wp-content/uploads/2020/04/cropped-purism-logo-rectangle-1-32x32.png</url>
	<title>Sriram Ramkrishna &#8211; Purism</title>
	<link>https://puri.sm/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Fragments App for the Librem 5</title>
		<link>https://puri.sm/posts/fragments-app-for-the-librem-5/</link>
		<pubDate>Wed, 27 Feb 2019 16:56:02 +0000</pubDate>
		<dc:creator><![CDATA[Sriram Ramkrishna]]></dc:creator>
				<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">https://puri.sm/?p=62582</guid>
		<description><![CDATA[<p>Fragments app, the BitTorrent client In continuing our series of applications that are ready to work with the Librem 5, we would like to announce that Fragments is now fully working! With Fragments, you get to have the ability to use BitTorrent to download large files. At Purism, we like using torrent to efficiently download [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://puri.sm/posts/fragments-app-for-the-librem-5/">Fragments App for the Librem 5</a> appeared first on <a rel="nofollow" href="https://puri.sm/">Purism</a>.</p>
]]></description>
				<content:encoded><![CDATA[<div class="business">
<div class="row grid">
<div class="column-4">
<h2 style="margin: 0;">Fragments app, the BitTorrent client</h2>
</div>
<div class="column-8">
<p>In continuing our series of applications that are ready to work with the Librem 5, we would like to announce that Fragments is now fully working! With Fragments, you get to have the ability to use BitTorrent to download large files. At Purism, we like using torrent to efficiently download PureOS or Debian operating systems, because what&#8217;s more fun than torrenting on the go?</p>
</div>
</div>
<hr />
<div class="row grid">
<div class="column-6"><img class="size-full wp-image-62583 alignnone" src="https://puri.sm/wp-content/uploads/2019/02/l5-front-torrent.png" alt="" /></div>
<div class="column-6" style="text-align: right;"><img class="size-full wp-image-62584 alignnone" src="https://puri.sm/wp-content/uploads/2019/02/l5-front-torrent-2.png" alt="" /></div>
</div>
<hr />
<div class="row grid">
<div class="column-12">
<p style="width: 75%; margin: 20px auto; text-align: center;">Got an app you&#8217;re interested in porting? Find out more at our <a href="https://developer.puri.sm/Librem5/">developer page</a>. Hang out at our Librem 5 community channel and tell us what you&#8217;re working on.</p>
<div><img style="width: 25%; margin: 20px auto; display: block;" src="https://puri.sm/wp-content/uploads/2019/01/coming-soon-2.png" /></div>
</div>
</div>
</div>
<p>The post <a rel="nofollow" href="https://puri.sm/posts/fragments-app-for-the-librem-5/">Fragments App for the Librem 5</a> appeared first on <a rel="nofollow" href="https://puri.sm/">Purism</a>.</p>
]]></content:encoded>
			</item>
		<item>
		<title>Librem 5 Hardware Update</title>
		<link>https://puri.sm/posts/librem-5-hardware-update-2/</link>
		<pubDate>Fri, 22 Feb 2019 13:33:45 +0000</pubDate>
		<dc:creator><![CDATA[Sriram Ramkrishna]]></dc:creator>
				<category><![CDATA[Customer Satisfaction]]></category>

		<guid isPermaLink="false">https://puri.sm/?p=62599</guid>
		<description><![CDATA[<p>Greetings everyone! This is a progress report on the Librem 5 development for the past two weeks. Here is all that happened. Conferences and Communities Quite a few members of the Purism team attended FOSDEM this year. Kyle Rankin gave a keynote, The Cloud is Just Another Sun that dealt with vendor lock-in in the [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://puri.sm/posts/librem-5-hardware-update-2/">Librem 5 Hardware Update</a> appeared first on <a rel="nofollow" href="https://puri.sm/">Purism</a>.</p>
]]></description>
				<content:encoded><![CDATA[<p>Greetings everyone! This is a progress report on the Librem 5 development for the past two weeks. Here is all that happened.</p>
<div class="business">
<div class="row grid">
<div class="column-4">
<strong>Conferences and Communities</strong><br />
Quite a few members of the Purism team attended FOSDEM this year. Kyle Rankin gave a keynote, <a href="https://fosdem.org/2019/schedule/event/cloud_is_another_sun/">The Cloud is Just Another Sun</a> that dealt with vendor lock-in in the cloud; the video is also available on the FOSDEM site. Meanwhile, some of the Librem 5 team organized a community Q&amp;A session under the heading of <a href="https://fosdem.org/2019/schedule/event/bof_free_software_mobile_devices/">Free Software on Mobile Devices</a>. Owners of the Librem 5 Developer Kit got their LCD displays flashed with the commands needed to work around some issues they had been experiencing.</p>
</div>
<div class="column-4">
<strong>Plasma Mobile sprint</strong><br />
Not everyone in the Librem 5 team went to FOSDEM: two team members attended the Plasma Mobile sprint in Berlin. Once there, they helped set up Librem 5 developer kits, talked about user interface design in Plasma Mobile and discussed development issues and progress. The Plasma Mobile team got something up and running real quickly on the developer kit, despite some initial glitches concerning touch input. This has led to a productive discussion on <a href="https://phabricator.kde.org/T10462">ways to support different form factors</a>, one that will hopefully lead to some nice cross-platform ways to support device convergence.</p>
</div>
<div class="column-4">
<strong>Application Development</strong><br />
Recent discussions, both in the Matrix chat rooms and on the forums, have led to two initiatives concerning the subject of phone applications: the first resulted in the compilation of the <a href="https://mglapps.frama.io/">Mobile GNU/Linux</a> apps list, a community-maintained list of applications that are meant to work on mobile devices running GNU/Linux – either because they target small screens, or because they feature adaptive user interfaces. If you can think of any app that should be on the list but ins&#8217;t, please follow the contribution guide at the end of the app list page.</p>
</div>
</div>
<div class="row grid">
<div class="column-8">
<h2> Dev Kits </h2>
<h4 style="font-size: 17px;">Probably the most significant event in last week&#8217;s news is that the LCD screens on development boards will <a href="https://source.puri.sm/Librem5/linux-emcraft/issues/5">now work</a>, if you <a href="https://developer.puri.sm/Librem5/Development_Environment/Boards/imx8.html#flashing-emmc">update the software</a> running on them. We knew that the screens worked just fine on the development kits we sent our backers, but we&#8217;re still all very happy to know that any remaining display problems could be fixed in software, not requiring the panels to be replaced. This update took longer to develop than initially hoped, as our kernel hackers had to work around a couple of tricky bugs in the hardware preventing the panel from being set up properly. Our community has already been exploring other features of the development board, so we&#8217;re now looking forward to seeing what they can do with working displays!</h4>
</div>
<div class="column-4">
<p>The second initiative led to the creation of a new Matrix room (community/librem-5-apps) for app development discussions, and it&#8217;s now listed in the <a href="https://developer.puri.sm/Librem5/Contact/Community.html#matrix-chat-rooms">online documentation</a>. It&#8217;s early days, there&#8217;s not that much being discussed at the moment but, with two other channels dedicated to different kinds of Librem 5-related conversations, it&#8217;s good to have a place for app-specific discussions.</p>
</div>
</div>
<hr />
<div class="row grid">
<div class="column-4">
<strong>Hardware</strong><br />
Much has been written about battery charging on the development board. Although the board&#8217;s controller circuit has built-in protection circuitry, we do recommend using batteries that also provide some level of overcurrent protection so that there is redundant protection in place. Batteries used with the development board must meet the specifications we&#8217;ve outlined – see the <a href="https://developer.puri.sm/Librem5/Development_Environment/Boards/imx8.html#dev-kit-package">developer documentation</a> and the printed text on the board&#8217;s battery holder. Following these guidelines is the safest; if you are unsure about whether the battery you are using meets the specifications, remove the battery when the board is not in use.</p>
<p>Still on the subject of batteries, charging now works with our 5.0 branch of the kernel; but the current status of the battery isn&#8217;t always correctly reported by the operating system. Despite this, the charging circuitry is always working, in order to make sure charging occurs properly. While the 5.0 branch brings this improvement, the 4.1x kernel has support for more of the Librem&#8217;s peripherals; so 5.0 is not quite ready for everyday use just yet.</p>
</div>
<div class="column-4">
<strong>Software</strong><br />
Developers with no access to boards can still get an experience of the current phone environment by <a href="https://developer.puri.sm/Librem5/Development_Environment/Boards/emulators.html">using an emulator</a>, thanks to Pan, one of the contributors to the developer documentation. While this gives a flavor of the phone experience, it may be lacking when it comes to prototyping with the types of peripherals that the phone will have. Fortunately, use of peripherals can be simulated to some extent, and a <a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/182">recent contribution to the documentation</a> shows just how to do that.</p>
</div>
<div class="column-4">
<strong>Low-Level</strong><br />
Ongoing work on the <a href="https://source.puri.sm/Librem5/uboot-imx/merge_requests/5">U-Boot bootloader</a>, the <a href="https://source.puri.sm/Librem5/flash-kernel/merge_requests/1">flash-kernel</a> and <a href="https://source.puri.sm/Librem5/librem5-devkit-tools/merge_requests/31">the tools</a> used to create images for the development board aims to make it easier to resize the storage space available on the board. This will help with the board&#8217;s software development, especially when testing with large Flatpak runtimes. In the kernel itself, we have tied the panel to the backlight so that the two <a href="https://source.puri.sm/Librem5/linux-emcraft/merge_requests/10">turn on and off together</a>, and we <a href="https://source.puri.sm/Librem5/linux-emcraft/merge_requests/12">switched to the mainline touchscreen driver</a> now that a <a href="https://patchwork.kernel.org/patch/10784125/">compatible driver has been identified</a>. The graphics stack has also been receiving some attention, in order to <a href="https://source.puri.sm/Librem5/linux-emcraft/merge_requests/13">make it more stable</a> – with work ongoing in <a href="https://source.puri.sm/guido.gunther/mesa/tree/gc7000-hacks" class="broken_link">a branch</a>, and changes being upstreamed at least as far as <a href="https://source.puri.sm/Librem5/mesa/tree/pureos/purple">PureOS</a>.</p>
</div>
</div>
<div class="row grid">
<div class="column-4"><strong><br />
Shell and Apps</strong><br />
We have guaranteed Phosh is now more stable on the development boards, as a result of <a href="https://source.puri.sm/Librem5/phosh/merge_requests/171">removing unused components</a> from the session. In the user interface department, the volume control now does indeed <a href="https://source.puri.sm/Librem5/phosh/merge_requests/169">control the volume</a>. Chatty, on the other hand, has been updated and improved over the last few weeks to include support for Matrix chats, using libpurple to provide this integration. The user interface now also features adaptive elements and dialogs, and includes a brand-new welcome screen.</p>
</div>
<div class="column-4"><strong><br />
Design</strong><br />
The new online account icons got merged https://gitlab.gnome.org/GNOME/gnome-online-accounts/merge_requests/17</p>
</div>
<div class="column-4"><strong><br />
Wi-Fi and Bluetooth</strong><br />
Wi-Fi was working on the developer kits, but many of the users found it to be unreliable; after a long investigation into this issue, a workaround was found and <a href="https://lists.community.puri.sm/pipermail/librem-5-dev/2019-February/000128.html">sent to the Librem 5 Development</a> mailing list. As noted in the message, it will improve some aspects of wireless networking &#8211; although there are a few remaining issues to be aware of.</p>
</div>
</div>
</div>
<p>And that&#8217;s our report! Questions? Come by our matrix channels, we&#8217;ll be happy to see you.</p>
<p>The post <a rel="nofollow" href="https://puri.sm/posts/librem-5-hardware-update-2/">Librem 5 Hardware Update</a> appeared first on <a rel="nofollow" href="https://puri.sm/">Purism</a>.</p>
]]></content:encoded>
			</item>
		<item>
		<title>Librem 5 Hardware Update</title>
		<link>https://puri.sm/posts/librem-5-hardware-update/</link>
		<pubDate>Fri, 25 Jan 2019 01:17:09 +0000</pubDate>
		<dc:creator><![CDATA[Sriram Ramkrishna]]></dc:creator>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Product Design]]></category>

		<guid isPermaLink="false">https://puri.sm/?p=62312</guid>
		<description><![CDATA[<p>The Librem 5 Developer Kit started arriving in the hands of developers, and focus was shifted towards supporting the growing number of developer requests – we want to make sure that shared advancements are truly shared across the developer community, it exciting to see the rapid progress being made. Much of the work being done [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://puri.sm/posts/librem-5-hardware-update/">Librem 5 Hardware Update</a> appeared first on <a rel="nofollow" href="https://puri.sm/">Purism</a>.</p>
]]></description>
				<content:encoded><![CDATA[<p>The Librem 5 Developer Kit started arriving in the hands of developers, and focus was shifted towards supporting the growing number of developer requests – we want to make sure that shared advancements are truly shared across the developer community, it exciting to see the rapid progress being made. Much of the work being done aims at making the kit work as well as possible for all kinds of developers. And even those working on non-critical issues at the moment are busy enjoying the discovery of all the capabilities of the dev kits.</p>
<p>We are keeping track of issues by tagging them with the <code>devkit</code> tag in GitLab – a summary of which can be found at <a href="https://source.puri.sm/groups/Librem5/-/issues?scope=all&amp;utf8=✓&amp;state=opened&amp;label_name%5B%5D=devkit">this overview</a>.</p>
<p>The release of the dev kit has increased the (already profound) interest in the Librem 5 phone, giving rise to many new questions in the forums – many of which have been answered elsewhere. If you have a question about the dev kit or the phone, the <a href="https://puri.sm/faq/">FAQ</a> is always a good place to start looking for answers; the recently-added <a href="https://puri.sm/faq/what-are-the-phone-specs/">What are the phone specs?</a> should hopefully clear up the current state of specs and understand what we are going to ship later in the year.</p>
<p>Cortex_M4:</p>
<ul>
<li><a href="https://source.puri.sm/Librem5/Cortex_M4/merge_requests/1">Fix makefile and ldscript</a></li>
</ul>
<p>chatty:</p>
<ul>
<li><a href="https://source.puri.sm/Librem5/chatty/merge_requests/34">flatpak: Use ‘disabled’ instead of ‘false’</a></li>
</ul>
<p>developer.puri.sm:</p>
<ul>
<li><a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/169">Update FAQ to reflect current devkit and phone status</a></li>
<li><a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/167">Tidy up the table within Sphinx and RTD theme limitations</a></li>
<li><a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/157">Add details about power LED status for devkit</a></li>
<li><a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/165">Add another Python dependency for the flashing script</a></li>
<li><a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/166">Use a local copy of the license button</a></li>
<li><a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/163">Fix typo, tidy up language</a></li>
<li><a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/160">Link back to the docs repository, hard-coding the URL in the theme</a></li>
<li><a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/161">Add dependencies for flashing script</a></li>
<li><a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/147">Add section on headphone connection events</a></li>
<li><a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/152">Refactor application development information</a></li>
<li><a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/153">Add a note about the boot mode</a></li>
<li><a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/162">Simplify instructions for image downloading</a></li>
<li><a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/158">Fix typo in Librem5 devkit troubleshooting documentation.</a></li>
<li><a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/156">Resolve “Patch submission should use “default branch” instead of “master””</a></li>
<li><a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/155">Add build dependency information for uuu</a></li>
</ul>
<p>haegtesse:</p>
<ul>
<li><a href="https://source.puri.sm/Librem5/haegtesse/merge_requests/8">README.md: Update instructions on running to not refer to -p</a></li>
</ul>
<p>image-builder:</p>
<ul>
<li><a href="https://source.puri.sm/Librem5/image-builder/merge_requests/82">build-image: Use non-latest kernel when it already exists</a></li>
<li><a href="https://source.puri.sm/Librem5/image-builder/merge_requests/80">build-image: Create meta.yml early</a></li>
</ul>
<p>libhandy:</p>
<ul>
<li><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/207">Release libhandy 0.0.7</a></li>
<li><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/204">combo-row: Rework selected-index property setting and notification</a></li>
<li><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/203">dialog: Close when pressing the back button</a></li>
<li><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/201">examples: Make the Dialog section look nicer</a></li>
<li><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/205">rows: Drop pointers to internals on destruction</a></li>
<li><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/195">meson: Allow to build as a static library</a></li>
<li><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/164">Adaptive dialog</a></li>
<li><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/192">combo-row: Add the selected-index property</a></li>
<li><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/190">action-row: Chain up the parent dispose method</a></li>
<li><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/193">action-row: Add the activatable-widget property</a></li>
<li><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/199">HdyComboRow: hdy<em>combo</em>row<em>get</em>model: Add missing scope annotation</a></li>
<li><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/198">HdyDialer: Don’t use class method slot for ‘delete’</a></li>
<li><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/185">Use <code>apt-get build-dep .</code> to install dependencies</a></li>
<li><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/197">tests: Init libhandy</a></li>
<li><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/194">example: Make the row with no action non-activatable</a></li>
<li><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/191">action-row: Add the Since annotation to properties</a></li>
<li><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/187">action-row: Handle show_all()</a></li>
<li><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/188">HdyComboRow: Don’t use g_autoptr for GEnumClass</a></li>
</ul>
<p>librem5-devkit-tools:</p>
<ul>https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/62</p>
<li><a href="https://source.puri.sm/Librem5/librem5-devkit-tools/merge_requests/21">Readme: Fix file name for uuu flash script.</a></li>
</ul>
<p>linux-emcraft:</p>
<ul>
<li><a href="https://source.puri.sm/Librem5/linux-emcraft/merge_requests/6">librem5-evk: Use a percent scaled brightness</a></li>
<li><a href="https://source.puri.sm/Librem5/linux-emcraft/merge_requests/4">Panel cleanups</a></li>
<li><a href="https://source.puri.sm/Librem5/linux-emcraft/merge_requests/5">ext2: Enable posix ACLs</a></li>
</ul>
<p>phosh:</p>
<ul>
<li><a href="https://source.puri.sm/Librem5/phosh/merge_requests/167">session: Remove incorrect error parameter in DBus call</a></li>
<li><a href="https://source.puri.sm/Librem5/phosh/merge_requests/166">rootston.ini: Scale rootston on DSI-1 output</a></li>
<li><a href="https://source.puri.sm/Librem5/phosh/merge_requests/164">Fix URLs and copyright holder</a></li>
<li><a href="https://source.puri.sm/Librem5/phosh/merge_requests/163">gitignore tag files</a></li>
</ul>
<p>uboot-imx:</p>
<ul>
<li style="list-style-type: none">
<ul>
<li><a href="https://source.puri.sm/Librem5/uboot-imx/merge_requests/3" class="broken_link">Use partition with bootable flag as mmcpart</a></li>
<li><a href="https://source.puri.sm/Librem5/uboot-imx/merge_requests/1">imx8m_som.h : make the kernel verbose rather than quiet</a></li>
</ul>
</li>
</ul>
<p>ModemManager:</p>
<ul>
<li style="list-style-type: none;">
<ul>
<li><a href="https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/62">base-call: Fix in-call URC regex to match handler logic</a></li>
<li><a href="https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/63">base-call: Increase incoming call timeout to ten seconds </a></li>
</ul>
</li>
</ul>
<p>The post <a rel="nofollow" href="https://puri.sm/posts/librem-5-hardware-update/">Librem 5 Hardware Update</a> appeared first on <a rel="nofollow" href="https://puri.sm/">Purism</a>.</p>
]]></content:encoded>
			</item>
		<item>
		<title>Purism Supports Software Freedom Conservancy</title>
		<link>https://puri.sm/posts/purism-supports-software-freedom-conservancy/</link>
		<pubDate>Tue, 15 Jan 2019 16:42:31 +0000</pubDate>
		<dc:creator><![CDATA[Sriram Ramkrishna]]></dc:creator>
				<category><![CDATA[Miscellaneous]]></category>
		<category><![CDATA[Promotions]]></category>

		<guid isPermaLink="false">https://puri.sm/?p=61995</guid>
		<description><![CDATA[<p>We live in a dangerous world where privacy and security are more important than ever. In order for software to be trusted, the source code must be available to verify — a simple trust and verify model. Purism is proud to release all of our source code under Free Software licenses that not only empower users [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://puri.sm/posts/purism-supports-software-freedom-conservancy/">Purism Supports Software Freedom Conservancy</a> appeared first on <a rel="nofollow" href="https://puri.sm/">Purism</a>.</p>
]]></description>
				<content:encoded><![CDATA[<p><img class="alignnone size-full wp-image-62040" src="https://puri.sm/wp-content/uploads/2019/01/purism-conservancy.png" alt="" width="1280" height="720" /></p>
<p>We live in a dangerous world where privacy and security are more important than ever. In order for software to be trusted, the source code must be available to verify — a simple trust <strong>and</strong> verify model. Purism is proud to release all of our source code under Free Software licenses that not only empower users but are vital to protect their privacy and security. We favor licenses with strong <a href="https://www.gnu.org/copyleft/copyleft.html" target="_blank" rel="nofollow noopener">copyleft</a> like the GNU General Public License version 3, and will release software under the GPLv3 or an <a href="https://www.gnu.org/licenses/license-list.html#SoftwareLicenses" target="_blank" rel="nofollow noopener">FSF-approved license</a> we inherit. Our code can be studied, verified, and shared, whether you use our Librem line of products or not.</p>
<p>Software Freedom Conservancy is a vital and important part of the Free Software ecosystem that we at Purism and billions of people worldwide rely upon. Without organizations that protect and enforce the terms expressed in software licenses, our digital rights are at risk. Conservancy continues to play a central role in legal battles to safeguard these freedoms.</p>
<p>License enforcement is only part of the story, and Conservancy assists its <a href="https://sfconservancy.org/projects/current/" target="_blank" rel="nofollow noopener">member projects</a> by handling all matters other than software development and documentation, so the developers can focus on what they do best: improving the software for the public good. Many of these member projects play a critical role in the advancement of privacy and security, such as the Reproducible Builds project and <a href="https://puri.sm/coreboot/" target="_blank" rel="nofollow noopener">coreboot</a>, one of the standout security features of Purism&#8217;s Librem laptops and upcoming smartphone.</p>
<p>Purism is delighted to contribute $1,000 USD to support Software Freedom Conservancy. <strong>Their funding drive ends today</strong> and we urge everyone who utilizes Free Software as part of their daily workflow or toolchain to donate to Conservancy and help them reach their fundraising goals.</p>
<p><a class="button-primary" href="https://sfconservancy.org/supporter/" target="_blank" rel="nofollow noopener">Donate Today!</a></p>
<p>The post <a rel="nofollow" href="https://puri.sm/posts/purism-supports-software-freedom-conservancy/">Purism Supports Software Freedom Conservancy</a> appeared first on <a rel="nofollow" href="https://puri.sm/">Purism</a>.</p>
]]></content:encoded>
			</item>
		<item>
		<title>End of Year Librem 5 Update</title>
		<link>https://puri.sm/posts/end-of-year-librem-5-update/</link>
		<pubDate>Wed, 09 Jan 2019 08:00:12 +0000</pubDate>
		<dc:creator><![CDATA[Sriram Ramkrishna]]></dc:creator>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Manufacturing Operations and Logistics]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Phones]]></category>

		<guid isPermaLink="false">https://puri.sm/?p=61879</guid>
		<description><![CDATA[<p>End of the Year Report &#8211; Librem 5 &#8211; Things are awesome Hello everyone! We have accomplished so much in the last 3 months and need to share, so prepare yourself for a dense update on the Librem 5 phone, PureOS, and software applications. As you know, we have a number of important components in [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://puri.sm/posts/end-of-year-librem-5-update/">End of Year Librem 5 Update</a> appeared first on <a rel="nofollow" href="https://puri.sm/">Purism</a>.</p>
]]></description>
				<content:encoded><![CDATA[<h1><strong>End of the Year Report &#8211; Librem 5 &#8211; Things are awesome<br />
</strong></h1>
<p>Hello everyone! We have accomplished so much in the last 3 months and need to share, so prepare yourself for a dense update on the Librem 5 phone, PureOS, and software applications.</p>
<p>As you know, we have a number of important components in the Librem 5 that we will try outline.</p>
<h2><strong>Calls</strong></h2>
<p>Let&#8217;s start off with the Calls application.  The calls application is what allows us to place phone calls and what makes the phone a<br />
phone.  In these past few months, we&#8217;ve been making this application work wonderfully.  Below is a demo of the calls application receiving a phone call.  So the basic support for the calls application is complete and we&#8217;re working making a great design.  We&#8217;ve successfully implemented important basic features like ring tones.</p>
<div style="width: 640px;" class="wp-video"><!--[if lt IE 9]><script>document.createElement('video');</script><![endif]-->
<video class="wp-video-shortcode" id="video-61879-1" width="640" height="360" preload="metadata" controls="controls"><source type="video/mp4" src="https://puri.sm/wp-content/uploads/2019/01/calls_ring.mp4?_=1" /><a href="https://puri.sm/wp-content/uploads/2019/01/calls_ring.mp4">https://puri.sm/wp-content/uploads/2019/01/calls_ring.mp4</a></video></div>
<p>If you&#8217;re interested in following the work, we&#8217;ve included the merge<br />
requests for calls below and important issues that were created:</p>
<p><em>Merge Requests</em></p>
<p><a href="https://source.puri.sm/Librem5/calls/merge_requests/5">https://source.puri.sm/Librem5/calls/merge_requests/5</a> &#8211; flatpak: enable access to dconf config<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/20">https://source.puri.sm/Librem5/calls/merge_requests/20</a> &#8211; new-call: set input hints and purpose of SearchEntry<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/25">https://source.puri.sm/Librem5/calls/merge_requests/25</a> &#8211; mm-provider: clarify warning a bit<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/23">https://source.puri.sm/Librem5/calls/merge_requests/23</a> &#8211; history-box: add empty view<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/19">https://source.puri.sm/Librem5/calls/merge_requests/19</a> &#8211; add i18n support<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/4">https://source.puri.sm/Librem5/calls/merge_requests/4</a> &#8211; add test for origin and calls<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/21">https://source.puri.sm/Librem5/calls/merge_requests/21</a> &#8211; add calls-application class<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/18">https://source.puri.sm/Librem5/calls/merge_requests/18</a> &#8211; add a call window and header bars<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/26">https://source.puri.sm/Librem5/calls/merge_requests/26</a> &#8211; display dialer on startup<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/28">https://source.puri.sm/Librem5/calls/merge_requests/28</a> &#8211; post ui change cleanups<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/18">https://source.puri.sm/Librem5/calls/merge_requests/18</a> &#8211; add call window and header bars<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/27">https://source.puri.sm/Librem5/calls/merge_requests/27</a> &#8211; flatpak support<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/29">https://source.puri.sm/Librem5/calls/merge_requests/29</a> &#8211; fixed memory leak<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/32">https://source.puri.sm/Librem5/calls/merge_requests/32</a> &#8211; pay attention to the addition and removal of a modem<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/33">https://source.puri.sm/Librem5/calls/merge_requests/33</a> &#8211; flatpak: Don&#8217;t build the libhandy Glade catalog<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/34">https://source.puri.sm/Librem5/calls/merge_requests/34</a> &#8211; cleaned up ringtone ringer<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/35">https://source.puri.sm/Librem5/calls/merge_requests/35</a> &#8211; providers in calls are now plugins<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/36">https://source.puri.sm/Librem5/calls/merge_requests/36</a> &#8211; updated calls icons<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/37">https://source.puri.sm/Librem5/calls/merge_requests/37</a> &#8211; flatpak building<br />
<a href="https://source.puri.sm/Librem5/calls/merge_requests/38">https://source.puri.sm/Librem5/calls/merge_requests/38</a> &#8211; changes to support impending call history changes</p>
<p><em>Issue Requests</em></p>
<p><a href="https://source.puri.sm/Librem5/calls/issues/18">https://source.puri.sm/Librem5/calls/issues/18</a> &#8211; memory leak in find_call_holder<br />
<a href="https://source.puri.sm/Librem5/calls/issues/19">https://source.puri.sm/Librem5/calls/issues/19</a> &#8211; memory leak in set_focus<br />
<a href="https://source.puri.sm/Librem5/calls/issues/20">https://source.puri.sm/Librem5/calls/issues/20</a> &#8211; memory leak in calls_call_window_add_call<br />
<a href="https://source.puri.sm/Librem5/calls/issues/36" class="broken_link">https://source.puri.sm/Librem5/calls/issues/36 </a>&#8211; transferred TODO list to gitlab issues<br />
<a href="https://source.puri.sm/Librem5/calls/issues/7#note_11069">https://source.puri.sm/Librem5/calls/issues/7#note_11069</a> &#8211; investigation into evolution data server/sqlite<br />
<a href="https://source.puri.sm/Librem5/calls/issues/22">https://source.puri.sm/Librem5/calls/issues/22</a> &#8211; DTMF fails with error Rejected send message</p>
<h2><strong>Hægtesse</strong></h2>
<p>Hægtesse is a daemon to transfer audio data between a modem and PulseAudio.  It currently only supports the SIMCom SIM7100 modem but may be useful for other modems.  The purpose of Hægtesse is to monitor the modem and when a call is initial to configure PulseAudio automatically for a phone call.  This is a necessary component for phone calls.</p>
<p><em>Issues</em></p>
<p><a href="https://source.puri.sm/Librem5/haegtesse/issues/1">https://source.puri.sm/Librem5/haegtesse/issues/1</a> &#8211; fills log when /dev/tty4 is not present</p>
<p><em>Merge Requests</em></p>
<p><a href="https://source.puri.sm/Librem5/haegtesse/merge_requests/3">https://source.puri.sm/Librem5/haegtesse/merge_requests/3</a> &#8211; Hægtesse listen to udev for the appearance of the audio TTY<br />
<a href="https://source.puri.sm/Librem5/haegtesse/merge_requests/4">https://source.puri.sm/Librem5/haegtesse/merge_requests/4</a> &#8211; Add full GPLv3 text<br />
<a href="https://source.puri.sm/Librem5/haegtesse/merge_requests/5">https://source.puri.sm/Librem5/haegtesse/merge_requests/5</a> &#8211; Build with gitlab-ci<br />
<a href="https://source.puri.sm/Librem5/haegtesse/merge_requests/7">https://source.puri.sm/Librem5/haegtesse/merge_requests/7</a> &#8211; fix build on PureOS</p>
<h2><strong>Libhandy</strong></h2>
<p>Libhandy is a library that extends GTK+ to be used on mobile profiles.  With libhandy, you can port any GTK3 or higher app that you have into a mobile profile.  If you have an application written in GTK3, reach out and we&#8217;d be happy to help you port it to libhandy.  To find out more about libhandy go here:<br />
https://source.puri.sm/Librem5/libhandy/wikis/home for our roadmap.</p>
<p>Here is an example of GNOME Web (epiphany) ported libhandy</p>
<div style="width: 640px;" class="wp-video"><video class="wp-video-shortcode" id="video-61879-2" width="640" height="360" preload="metadata" controls="controls"><source type="video/webm" src="https://puri.sm/wp-content/uploads/2019/01/libhandy-and-gnome-web.webm?_=2" /><a href="https://puri.sm/wp-content/uploads/2019/01/libhandy-and-gnome-web.webm">https://puri.sm/wp-content/uploads/2019/01/libhandy-and-gnome-web.webm</a></video></div>
<p>Documentation and example code.</p>
<p>Libhandy has had made significant advancements these months with several releases made.</p>
<p>Libhandy is currently being used to port many core GNOME apps to the librem5</p>
<p><em>Merge requests:</em></p>
<p><a href="https://source.puri.sm/Librem5/libhandy/merge_requests/137">https://source.puri.sm/Librem5/libhandy/merge_requests/137</a> &#8211; HdyDialer: Apply &#8216;keypad&#8217; style class<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/145">https://source.puri.sm/Librem5/libhandy/merge_requests/145</a> &#8211; Don&#8217;t invoke signal handlers on finalized HeaderGroups<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/147">https://source.puri.sm/Librem5/libhandy/merge_requests/147</a> &#8211; add i18n support<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/146">https://source.puri.sm/Librem5/libhandy/merge_requests/146</a> &#8211; doc fix<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/145">https://source.puri.sm/Librem5/libhandy/merge_requests/145</a> &#8211; HdyHeaderGroup signal disconnections<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/146">https://source.puri.sm/Librem5/libhandy/merge_requests/146</a> &#8211; few documentation fixes<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/147">https://source.puri.sm/Librem5/libhandy/merge_requests/147</a> &#8211; enabling l10n<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/148">https://source.puri.sm/Librem5/libhandy/merge_requests/148</a> &#8211; g_auto* documentation<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/150">https://source.puri.sm/Librem5/libhandy/merge_requests/150</a> &#8211; drop Jenkinsfile<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/151">https://source.puri.sm/Librem5/libhandy/merge_requests/151</a> &#8211; Syntax highlight HACKING<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/152">https://source.puri.sm/Librem5/libhandy/merge_requests/152</a> &#8211; Init public GObject types in hdy_init()<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/153">https://source.puri.sm/Librem5/libhandy/merge_requests/153</a> &#8211; fixes to MacOS Build<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/154">https://source.puri.sm/Librem5/libhandy/merge_requests/154</a> &#8211; Add measure() methods<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/155">https://source.puri.sm/Librem5/libhandy/merge_requests/155</a> &#8211; drop direct access to event fields<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/156">https://source.puri.sm/Librem5/libhandy/merge_requests/156</a> &#8211; renaming margins for GTK4 support<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/157">https://source.puri.sm/Librem5/libhandy/merge_requests/157</a> &#8211; make HdyDialer a descendant of GtkBin<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/159">https://source.puri.sm/Librem5/libhandy/merge_requests/159</a> &#8211; fix a mention of a HdyLeaflet in the docs<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/162">https://source.puri.sm/Librem5/libhandy/merge_requests/162</a> &#8211; unstability acknowledgement documentation improvements<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/165">https://source.puri.sm/Librem5/libhandy/merge_requests/165</a> &#8211; normalize and document private header guards<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/166">https://source.puri.sm/Librem5/libhandy/merge_requests/166</a> &#8211; adding hdysearchbar<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/167">https://source.puri.sm/Librem5/libhandy/merge_requests/167</a> &#8211; remove useless libhandy options from example flatpak<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/168">https://source.puri.sm/Librem5/libhandy/merge_requests/168</a> &#8211; document more coding style<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/169">https://source.puri.sm/Librem5/libhandy/merge_requests/169</a> &#8211; reproducible build of libhandy<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/172">https://source.puri.sm/Librem5/libhandy/merge_requests/172</a> &#8211; hdy_init() docs improvements<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/173">https://source.puri.sm/Librem5/libhandy/merge_requests/173</a> &#8211; add transfer none to hdy_init()<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/174">https://source.puri.sm/Librem5/libhandy/merge_requests/174</a> &#8211;  fix HdyHeaderGroup references<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/175">https://source.puri.sm/Librem5/libhandy/merge_requests/175</a> &#8211; example: put the content in a scrolled window<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/176">https://source.puri.sm/Librem5/libhandy/merge_requests/176</a> &#8211; add many row widgets<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/177">https://source.puri.sm/Librem5/libhandy/merge_requests/177</a> &#8211; leaflet: clear the children list on disposal<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/178">https://source.puri.sm/Librem5/libhandy/merge_requests/178</a> &#8211; build: set the shared object install directory<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/179">https://source.puri.sm/Librem5/libhandy/merge_requests/179</a> &#8211; update meson.build for MinGW compatibility<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/180">https://source.puri.sm/Librem5/libhandy/merge_requests/180</a> &#8211; build: dont&#8217; use -fstack-protector-strong on mingw64<br />
<a href="https://source.puri.sm/Librem5/libhandy/merge_requests/181">https://source.puri.sm/Librem5/libhandy/merge_requests/181</a> &#8211; update docs skeleton</p>
<p><em>Issues</em>:<br />
<a href="https://source.puri.sm/Librem5/libhandy/issues/57">https://source.puri.sm/Librem5/libhandy/issues/57</a> &#8211; HdyTitleBar broken with <code>.devel</code> window in org.gnome.Sdk//master<br />
<a href="https://source.puri.sm/Librem5/libhandy/issues/52">https://source.puri.sm/Librem5/libhandy/issues/52</a> &#8211; issues compiling on OSX</p>
<h2><strong>Librem5-devkit-tools</strong></h2>
<p>Librem5 devkit tools are the set of tools to enable the devkit that was recently shipped out to crowdfunding supporters.</p>
<p>&#8211; <a href="https://source.puri.sm/Librem5/librem5-devkit-tools">https://source.puri.sm/Librem5/librem5-devkit-tools</a></p>
<h2><strong>Virtboard</strong></h2>
<p>Virtboard is our virtual keyboard used on the Librem 5.  Work has been on-going in enabling the virtual keyboard mostly focusing on making this input working under wayland.  The UX experience is still on-going.  Feedback is of course encouraged.</p>
<p><em>Merge requests</em><br />
&#8211; <a href="https://source.puri.sm/Librem5/virtboard/merge_requests/20">https://source.puri.sm/Librem5/virtboard/merge_requests/20</a> Unbreak virtboard crashing when using GCCs stack protector<br />
&#8211; <a href="https://source.puri.sm/Librem5/virtboard/merge_requests/21">https://source.puri.sm/Librem5/virtboard/merge_requests/21</a> Update input-method protocol<br />
&#8211; <a href="https://source.puri.sm/Librem5/virtboard/merge_requests/22">https://source.puri.sm/Librem5/virtboard/merge_requests/22</a> make virtboard fully hidden<br />
&#8211; <a href="https://source.puri.sm/Librem5/virtboard/merge_requests/23">https://source.puri.sm/Librem5/virtboard/merge_requests/23</a> virtboard translations<br />
&#8211; <a href="https://source.puri.sm/Librem5/virtboard/merge_requests/24">https://source.puri.sm/Librem5/virtboard/merge_requests/24</a> convert to glib mainloop<br />
&#8211; <a href="https://source.puri.sm/Librem5/virtboard/merge_requests/25">https://source.puri.sm/Librem5/virtboard/merge_requests/25</a> added multiple layouts</p>
<h2><strong>Chatty</strong></h2>
<p>Chatty is our combination SMS and encrypted communication app.  Chatty currently works with SMS and with the help of libpurple we can also have E2E encrypted communication as promised before.</p>
<p>We currently can successfully send SMS between phones.  Below is a demo of the chatty doing some emoticons.  You might recall last post we showed chatty doing real SMS.  The UX experience is still on-going and continues to evolve.  Follow along in this issue &#8211;</p>
<div style="width: 640px;" class="wp-video"><video class="wp-video-shortcode" id="video-61879-3" width="640" height="360" preload="metadata" controls="controls"><source type="video/webm" src="https://puri.sm/wp-content/uploads/2019/01/chatty-emoji.webm?_=3" /><a href="https://puri.sm/wp-content/uploads/2019/01/chatty-emoji.webm">https://puri.sm/wp-content/uploads/2019/01/chatty-emoji.webm</a></video></div>
<p><img class="alignnone wp-image-61893 size-large" src="https://puri.sm/wp-content/uploads/2019/01/chatty_ui-712x1024.png" alt="" width="640" height="920" srcset="https://puri.sm/wp-content/uploads/2019/01/chatty_ui-712x1024.png 712w, https://puri.sm/wp-content/uploads/2019/01/chatty_ui-209x300.png 209w, https://puri.sm/wp-content/uploads/2019/01/chatty_ui-768x1105.png 768w, https://puri.sm/wp-content/uploads/2019/01/chatty_ui.png 1390w" sizes="(max-width: 640px) 100vw, 640px" /></p>
<figure id="attachment_61892" style="width: 298px" class="wp-caption alignnone"><img class="wp-image-61892 size-medium" src="https://puri.sm/wp-content/uploads/2019/01/chatty-ui-298x300.png" alt="Chatty's proposed Icon" width="298" height="300" srcset="https://puri.sm/wp-content/uploads/2019/01/chatty-ui-298x300.png 298w, https://puri.sm/wp-content/uploads/2019/01/chatty-ui-150x150.png 150w, https://puri.sm/wp-content/uploads/2019/01/chatty-ui.png 373w" sizes="(max-width: 298px) 100vw, 298px" /><figcaption class="wp-caption-text">Chatty&#8217;s proposed Icon</figcaption></figure>
<p>https://source.puri.sm/Librem5/chatty/issues/52 for how the UX is coming along.</p>
<p><em>M</em>erge<em> requests</em></p>
<p>&#8211; <a href="https://source.puri.sm/Librem5/chatty/merge_requests/1">https://source.puri.sm/Librem5/chatty/merge_requests/1</a> Add some basic gitlab-ci<br />
&#8211; <a href="https://source.puri.sm/Librem5/chatty/merge_requests/2">https://source.puri.sm/Librem5/chatty/merge_requests/2</a> fixing the Flatpak manifest<br />
&#8211; <a href="https://source.puri.sm/Librem5/chatty/merge_requests/3">https://source.puri.sm/Librem5/chatty/merge_requests/3 </a>porting the window to Glade<br />
&#8211; <a href="https://source.puri.sm/Librem5/chatty/merge_requests/4">https://source.puri.sm/Librem5/chatty/merge_requests/4</a> Remove arm special casing<br />
&#8211; <a href="https://source.puri.sm/Librem5/chatty/merge_requests/5">https://source.puri.sm/Librem5/chatty/merge_requests/5</a> don&#8217;t access inexistent header bar<br />
&#8211; <a href="https://source.puri.sm/Librem5/chatty/merge_requests/6">https://source.puri.sm/Librem5/chatty/merge_requests/6</a> Use glib&#8217;s logging<br />
&#8211; <a href="https://source.puri.sm/Librem5/chatty/merge_requests/7">https://source.puri.sm/Librem5/chatty/merge_requests/7</a> Don&#8217;t ignore compiler warnings<br />
&#8211; <a href="https://source.puri.sm/Librem5/chatty/merge_requests/9">https://source.puri.sm/Librem5/chatty/merge_requests/9</a> Fix build with a default set of warnings enabled<br />
&#8211; <a href="https://source.puri.sm/Librem5/chatty/merge_requests/10">https://source.puri.sm/Librem5/chatty/merge_requests/10</a> Enable and fix more compile warnings<br />
&#8211; <a href="https://source.puri.sm/Librem5/chatty/merge_requests/13">https://source.puri.sm/Librem5/chatty/merge_requests/13</a> Fix crash during message parsing<br />
&#8211; <a href="https://source.puri.sm/Librem5/chatty/merge_requests/14">https://source.puri.sm/Librem5/chatty/merge_requests/14</a> Make text in chat bubble copyable<br />
&#8211; <a href="https://source.puri.sm/Librem5/chatty/merge_requests/15">https://source.puri.sm/Librem5/chatty/merge_requests/15</a> Fix new messages not being displayed<br />
&#8211; <a href="https://source.puri.sm/Librem5/chatty/merge_requests/16">https://source.puri.sm/Librem5/chatty/merge_requests/16</a> Prepare chatty for translations<br />
&#8211; <a href="https://source.puri.sm/Librem5/chatty/merge_requests/17">https://source.puri.sm/Librem5/chatty/merge_requests/17</a> Fix time format display<br />
&#8211; <a href="https://source.puri.sm/Librem5/purple-mm-sms/merge_requests/1">https://source.puri.sm/Librem5/purple-mm-sms/merge_requests/1</a> Add Debian packaging<br />
&#8211; <a href="https://source.puri.sm/Librem5/chatty/merge_requests/21">https://source.puri.sm/Librem5/chatty/merge_requests/21</a> &#8211; add Debian packaging<br />
&#8211; <a href="https://source.puri.sm/Librem5/chatty/merge_requests/29">https://source.puri.sm/Librem5/chatty/merge_requests/29</a> &#8211; don&#8217;t use network when verifying appdata files<br />
&#8211; <a href="https://source.puri.sm/Librem5/purism-chatty/issues/5">https://source.puri.sm/Librem5/purism-chatty/issues/5</a> Suggested closing the old project<br />
&#8211; <a href="https://source.puri.sm/Librem5/chatty/issues/52">https://source.puri.sm/Librem5/chatty/issues/52 </a>&#8211; improve chatty UI</p>
<h2><strong>Design</strong></h2>
<p>Most of our design is being done in GNOME upstream except of course for the UX experience in the Librem 5 specific component.  Purism believes deeply in working in the upstream and we work closely with GNOME&#8217;s designers.  Below are a number of design mockups that were conceived for various GNOME apps to work with libhandy.</p>
<figure id="attachment_61882" style="width: 640px" class="wp-caption alignleft"><img class="wp-image-61882 size-large" src="https://puri.sm/wp-content/uploads/2019/01/adaptive-view-switcher-modes-1024x597.png" alt="" width="640" height="373" srcset="https://puri.sm/wp-content/uploads/2019/01/adaptive-view-switcher-modes-1024x597.png 1024w, https://puri.sm/wp-content/uploads/2019/01/adaptive-view-switcher-modes-300x175.png 300w, https://puri.sm/wp-content/uploads/2019/01/adaptive-view-switcher-modes-768x448.png 768w, https://puri.sm/wp-content/uploads/2019/01/adaptive-view-switcher-modes.png 1200w" sizes="(max-width: 640px) 100vw, 640px" /><figcaption class="wp-caption-text">Adaptive View Switcher Design mockups</figcaption></figure>
<p>&nbsp;</p>
<figure id="attachment_61884" style="width: 640px" class="wp-caption alignnone"><img class="wp-image-61884 size-large" src="https://puri.sm/wp-content/uploads/2019/01/todo-1012x1024.png" alt="GNOME TODO Mobile Mockup" width="640" height="648" srcset="https://puri.sm/wp-content/uploads/2019/01/todo-1012x1024.png 1012w, https://puri.sm/wp-content/uploads/2019/01/todo-296x300.png 296w, https://puri.sm/wp-content/uploads/2019/01/todo-768x777.png 768w" sizes="(max-width: 640px) 100vw, 640px" /><figcaption class="wp-caption-text">GNOME TODO mobile mockup</figcaption></figure>
<p>&nbsp;</p>
<figure id="attachment_61883" style="width: 640px" class="wp-caption alignnone"><img class="wp-image-61883 size-large" src="https://puri.sm/wp-content/uploads/2019/01/notes-1024x875.png" alt="GNOME Notes Mockup" width="640" height="547" srcset="https://puri.sm/wp-content/uploads/2019/01/notes-1024x875.png 1024w, https://puri.sm/wp-content/uploads/2019/01/notes-300x256.png 300w, https://puri.sm/wp-content/uploads/2019/01/notes-768x656.png 768w" sizes="(max-width: 640px) 100vw, 640px" /><figcaption class="wp-caption-text">GNOME Notes Mockup</figcaption></figure>
<p>&#8211; <a href="https://gitlab.gnome.org/Teams/Design/app-mockups/blob/master/todo/todo.png">https://gitlab.gnome.org/Teams/Design/app-mockups/blob/master/todo/todo.png</a> Adaptive Mockups for GNOME TODO<br />
&#8211; <a href="https://gitlab.gnome.org/Teams/Design/app-mockups/blob/master/notes/notes.png">https://gitlab.gnome.org/Teams/Design/app-mockups/blob/master/notes/notes.png</a> &#8211; Adaptive Mockups for GNOME Notes<br />
&#8211; <a href="https://gitlab.gnome.org/Teams/Design/os-mockups/blob/master/view-switcher/adaptive-view-switcher-modes.png">https://gitlab.gnome.org/Teams/Design/os-mockups/blob/master/view-switcher/adaptive-view-switcher-modes.png</a> &#8211; proposal for adaptive view switching modes (commited to implement by Adrien)<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/Initiatives/issues/2">https://gitlab.gnome.org/GNOME/Initiatives/issues/2</a> &#8211; new app icons for GNOME</p>
<p>In addition, a lot of work has gone in to designing parts of GNOME like the control center to work in a mobile context.</p>
<h2><strong>WLroots</strong></h2>
<p>WLroot is the Wayland implementation for the Librem5 and which phosh our UX shell runs on.  Mostly working on getting libinput working.  We did some investigations on using rust bindings, but turned out that it was more work with very little advantage.</p>
<p><em>Merge requests:</em><br />
&#8211; <a href="https://packages.debian.org/source/experimental/wlroots">https://packages.debian.org/source/experimental/wlroots </a>&#8211; update debian packaging<br />
&#8211; <a href="https://source.puri.sm/Librem5/wlroots/merge_requests/35">https://source.puri.sm/Librem5/wlroots/merge_requests/35 </a>&#8211; input-method and text-input support to the Librem5<br />
&#8211; <a href="https://source.puri.sm/Librem5/wlroots/merge_requests/40">https://source.puri.sm/Librem5/wlroots/merge_requests/40</a> &#8211; wlroots update</p>
<p><em>Issues:</em></p>
<p>&#8211; <a href="https://source.puri.sm/Librem5/wlroots/issues/6">https://source.puri.sm/Librem5/wlroots/issues/6</a> &#8211; rootston freezes on ssh log out<br />
&#8211; <a href="https://source.puri.sm/Librem5/wlroots/issues/18">https://source.puri.sm/Librem5/wlroots/issues/18</a> &#8211; rootston often freezes</p>
<h2><strong>Phosh</strong></h2>
<p>Phosh is the actual visual look and feel of the Librem 5.  The most significant work here is being able to detect idle and dim the screen automatically when not on battery power.  Some work on the lock shield was also done and various UX fixes and features.<br />
For more information see the merge requests before.</p>
<p><em>Merge requests</em></p>
<p>&#8211; <a href="https://source.puri.sm/Librem5/phosh/merge_requests/143">https://source.puri.sm/Librem5/phosh/merge_requests/143</a> Update translations from zanata<br />
&#8211; <a href="https://source.puri.sm/Librem5/phosh/merge_requests/153">https://source.puri.sm/Librem5/phosh/merge_requests/153 </a>&#8211; Drop hard coded weston-terminal from favorites<br />
&#8211; <a href="https://source.puri.sm/Librem5/phosh/merge_requests/154">https://source.puri.sm/Librem5/phosh/merge_requests/154</a> &#8211; Add a poweroff button to the settings menu<br />
&#8211; <a href="https://source.puri.sm/Librem5/phosh/merge_requests/158">https://source.puri.sm/Librem5/phosh/merge_requests/158</a> &#8211; use actual values for transform instead of looking at rotation property<br />
&#8211; <a href="https://source.puri.sm/Librem5/phosh/merge_requests/159">https://source.puri.sm/Librem5/phosh/merge_requests/159</a> &#8211; make sure setting buttons stay circular</p>
<p><em>Issues</em></p>
<p>&#8211; <a href="https://source.puri.sm/Librem5/phosh/issues/52">https://source.puri.sm/Librem5/phosh/issues/52</a>  &#8211; look into full screen blank support on lock</p>
<h2><strong>Upstream Work</strong></h2>
<p>Purism knows it stands on the shoulders of giants.  We would not be be successful without our upstream partners.  We make sure that our technical debt is as small as possible, preferring to work in upstream as much as a matter of course.  Below is a list of the work we have done in the various upstreams that we depend on.  This is not an exhaustive list of projects since we do other upstream work for our laptops as well.</p>
<p>We are very proud of our upstream work and being part of these upstream projects.</p>
<p>&#8211; <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910640">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910640</a> &#8211; Debian&#8217;s libgtk-4-dev Needs to depend on libvulkan-dev<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/200">https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/200</a> &#8211; Kept pushing making the WiFi panel adaptive<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/243">https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/243</a> &#8211; Moving the app menu<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/gnome-contacts/merge_requests/41">https://gitlab.gnome.org/GNOME/gnome-contacts/merge_requests/41</a> &#8211; contact deselection on creation fix<br />
&#8211;<a href="https://gitlab.gnome.org/GNOME/gnome-contacts/merge_requests/42"> https://gitlab.gnome.org/GNOME/gnome-contacts/merge_requests/42</a> &#8211; using HdyHeaderGroup<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/gnome-contacts/merge_requests/43">https://gitlab.gnome.org/GNOME/gnome-contacts/merge_requests/43 </a>&#8211; using HdyTitleBar<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/gtk/issues/1399">https://gitlab.gnome.org/GNOME/gtk/issues/1399</a> &#8211; Suggested to not show dashed border in keyboard-navigable selected elements when no keyboard is available<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/Initiatives/wikis/GNOME-apps-mobile">https://gitlab.gnome.org/GNOME/Initiatives/wikis/GNOME-apps-mobile </a>&#8211; Helped Javier set up the initiative<br />
&#8211; <a href="https://github.com/swaywm/wlroots/pull/1316">https://github.com/swaywm/wlroots/pull/1316</a> &#8211; don&#8217;t let the wlr_output handle the fullscreen view in case</p>
<p>&#8211; <a href="https://github.com/swaywm/wlroots/pull/1203">https://github.com/swaywm/wlroots/pull/1203</a> &#8211; Support input method and text input<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/gtk/merge_requests/384">https://gitlab.gnome.org/GNOME/gtk/merge_requests/384</a>  &#8211; reviewed fix for text input protocol<br />
&#8211; <a href="https://github.com/haecker-felix/Fragments/pull/41">https://github.com/haecker-felix/Fragments/pull/41</a> &#8211; fixed a text flickering<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/gitg/merge_requests/21">https://gitlab.gnome.org/GNOME/gitg/merge_requests/21</a> &#8211; GtkActionBar for the commit tool bar<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/gitg/merge_requests/22">https://gitlab.gnome.org/GNOME/gitg/merge_requests/22</a> &#8211; fixing the diff options sliding direction<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/glade/issues/339">https://gitlab.gnome.org/GNOME/glade/issues/339</a> &#8211; Suggested to not destroy existing property bindings<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/glade/issues/340">https://gitlab.gnome.org/GNOME/glade/issues/340</a> &#8211; Suggested to support property bindings<br />
&#8211; <a href="https://github.com/swaywm/wlroots/pull/1316">https://github.com/swaywm/wlroots/pull/1316</a> &#8211; Fix bug with full screen views and overlays (otherwise it will cause trouble with full screen video/pdf vs the lock screen<br />
&#8211; <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911146">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911146 &#8211; xwayland spurious crashes</a><br />
&#8211; <a href="https://github.com/swaywm/wlr-protocols/pull/27">https://github.com/swaywm/wlr-protocols/pull/27</a> &#8211; securing wayland protocols<br />
&#8211; <a href="https://gitlab.gnome.org/Community/Purism/gnome-software/tree/wip/aplazas/narrow">https://gitlab.gnome.org/Community/Purism/gnome-software/tree/wip/aplazas/narrow</a> &#8211; start of adaptive<br />
&#8211; <a href="https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/92">https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/92</a> &#8211; supplementary call operations<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/gtk/issues/1447">https://gitlab.gnome.org/GNOME/gtk/issues/1447</a> &#8211; tried to solve input method complications in gnome-shell<br />
&#8211; <a href="https://gitlab.gnome.org/Community/Purism/gnome-clocks/tree/librem5">https://gitlab.gnome.org/Community/Purism/gnome-clocks/tree/librem5</a> &#8211; librem 5 clock application<br />
&#8211; <a href="https://bytesgnomeschozo.blogspot.com/2018/11/gnome-at-capitole-du-libre-2018.html">https://bytesgnomeschozo.blogspot.com/2018/11/gnome-at-capitole-du-libre-2018.html</a> &#8211; blog post on Capitole du libre conference<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/gtk/merge_requests/425">https://gitlab.gnome.org/GNOME/gtk/merge_requests/425</a> &#8211; transient window notification fix to 3.24<br />
&#8211; <a href="https://gitlab.gnome.org/World/lollypop/merge_requests/1319">https://gitlab.gnome.org/World/lollypop/merge_requests/1319</a> &#8211; flatpak build fix for lollypop<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/epiphany/merge_requests/56">https://gitlab.gnome.org/GNOME/epiphany/merge_requests/56</a> &#8211; make title bar more adaptive<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/epiphany/merge_requests/59">https://gitlab.gnome.org/GNOME/epiphany/merge_requests/59 </a>&#8211; make search bar adaptive<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/312">https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/312</a> &#8211; 4 adaptive panels for GNOME settings<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/313">https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/313</a> &#8211; make shell more adaptive<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/200">https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/200</a> &#8211; Wifi panel adaptive<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/gnome-characters/issues/46">https://gitlab.gnome.org/GNOME/gnome-characters/issues/46</a> &#8211; icon mismatch<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/317">https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/317 </a>&#8211; implement new network connection editor design<br />
&#8211; <a href="https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/59">https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/59 </a>&#8211; policy: call method name should be SendDtmf rather than SendTone<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/libgnome-volume-control/merge_requests/3">https://gitlab.gnome.org/GNOME/libgnome-volume-control/merge_requests/3</a> &#8211; make debug less verbose<br />
&#8211; <a href="https://source.puri.sm/Librem5/wlroots/merge_requests/40">https://source.puri.sm/Librem5/wlroots/merge_requests/40</a> &#8211; WIP: Update 0.2<br />
&#8211; <a href="https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/43">https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/43 </a>&#8211; rework wwan plugin after upstream feedback</p>
<h2><strong>Documentation</strong></h2>
<p>This effort can never survive without documentation.  In that regard, welcome David Boddie to the Librem 5 team working on documentation for the Librem 5.  The whole team, while focusing on their development, are equally aware of the role of documentation and have worked diligently in making sure that people create applications for the Librem 5.  With two members working exclusively on documentation and developer experience, we hope to make writing applications for the Librem 5 as easy as it can be.  Feedback in improving our documentation would be most welcome!</p>
<p>A lot of focus was made on creating documentation on how to create Librem 5 applications with sample code.</p>
<p><em>Issues</em></p>
<p>&#8211; <a href="https://source.puri.sm/Librem5/developer.puri.sm/issues/28">https://source.puri.sm/Librem5/developer.puri.sm/issues/28</a> &#8211; Upate GNOME Builder section</p>
<p><em>Merge requests</em></p>
<p>&#8211; <a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/55">https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/55</a> &#8211; GTK+ limit the documentation to libhandy 0.0.3<br />
&#8211; <a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/60">https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/60</a> &#8211; update qemu<br />
&#8211; <a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/61">https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/61</a> &#8211; update email lists to be lists.community.puri.sm<br />
&#8211; <a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/63">https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/63</a> &#8211; add stack picture and more intro<br />
&#8211; <a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/68">https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/68</a> &#8211; GTK+: add links to the GTK+ and libhandy docs<br />
&#8211; <a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/71">https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/71</a> &#8211; GTK+: Note to adjust label&#8217;s xalign when ellipsized<br />
&#8211; <a href="https://source.puri.sm/david.boddie/python-gobject-gtk3-examples">https://source.puri.sm/david.boddie/python-gobject-gtk3-examples</a> &#8211; collection of simple PyGObject examples<br />
&#8211; <a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/84">https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/84</a> &#8211; document phosh&#8217;s supported DBus APIs<br />
&#8211; <a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/85">https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/85</a> &#8211; document some trivial phosh apis<br />
&#8211; <a href="https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/82">https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/82</a> &#8211; added small descriptions of KDE-related technologies</p>
<h2><strong>Phone hardware/Dev Kit</strong></h2>
<p>The recent shipping of the Librem 5 dev kit represents countless hours of work with an aggressive schedule.  Nicole, Eric, and Petra, along with dedicated operations staff, worked continuously for a week to package all the dev kits to be shipped out to our dev kit backers.</p>
<p>When it comes to software and hardware freedom, we not only do the talk, we do the walk.  Everything in the dev kit, is licensed under the GNU GPL v3+.  We have released the schematics for the dev kit and all source files.  We encourage you to participate and bring your talents and join us!</p>
<p>By now everyone who ordered a dev kit would have received it and are working on the hardware to get it fully enabled from the LCD panel to user-controlled LEDs.  We will be sharing more photos and videos of the dev kits in action as more and more community members advance the software around them.</p>
<p>In the meanwhile, our matrix channel has become a hot bed of activity as people prod and poke their dev kits, asking questions and following along with the devleopment of the phone.</p>
<p>As for the phone, we have confirmed the BOM (Bill of Materials) and the sourcing of parts, we are only finalizing the I.MX 8M or 8M Mini by benchmark testing. Once we have approved the design (also planned in January) we can create the necessary molds and stamps.</p>
<p>January is going to be really busy for Purism as we split time between the dev kit advancements and then pivoting to the Librem 5 phone hardware, but we welcome the excitement around what we&#8217;re doing.  We will have a retrospective post on the dev kit tomorow (2019-01-09), so stay tuned for that!</p>
<p>Short Summary of the work:<br />
&#8211; Moved to Kernel 4.18.11<br />
&#8211; Reworked device tree for dev kit<br />
&#8211; add texture support on GC7000   https://source.puri.sm/guido.gunther/mesa/tree/gc7000-bo-relocs,   https://source.puri.sm/guido.gunther/mesa/tree/gc7000-bo-relocs<br />
&#8211; PureOS now building on our build server using Laniakea build system<br />
&#8211; a mechanical issue was discovered with the M.2 module not sitting flush against the board so a taller M.2 connector was used on the final dev kit design<br />
&#8211; RedPine fixing the W_DISABLE# issue, they will use a bodge wire for our 340 dev kit units so that the HKS works as anticipated<br />
&#8211; Fixed various issues in the nwl-dsl (mipi) driver<br />
&#8211; picture of working HDMI &#8211; <a href="https://talk.puri.sm/_matrix/media/v1/download/talk.puri.sm/SSvCOnFIIdtgeXqmrMrjZkje">https://talk.puri.sm/_matrix/media/v1/download/talk.puri.sm/SSvCOnFIIdtgeXqmrMrjZkje</a><br />
&#8211; Fixup several bugs in the imx8ms mipi dsi layer<br />
<a href="https://source.puri.sm/Librem5/linux-emcraft/commit/2a10a1eaee8860f0f79b513497039ca21a5ded76">https://source.puri.sm/Librem5/linux-emcraft/commit/2a10a1eaee8860f0f79b513497039ca21a5ded76</a><br />
<a href="https://source.puri.sm/Librem5/linux-emcraft/commit/34bfd44c92bd32b4cd8c88a7943ced00c699a398">https://source.puri.sm/Librem5/linux-emcraft/commit/34bfd44c92bd32b4cd8c88a7943ced00c699a398</a><br />
<a href="https://source.puri.sm/Librem5/linux-emcraft/commit/937cb53b89c26ba3011ea05f6ae14b1134036a6c">https://source.puri.sm/Librem5/linux-emcraft/commit/937cb53b89c26ba3011ea05f6ae14b1134036a6c</a></p>
<p>&#8211; Initial (WIP) LCD panel driver<br />
<a href="https://source.puri.sm/guido.gunther/linux-imx8/commit/919a834a865824eeeeb9b98bc4932ae46a614fba">https://source.puri.sm/guido.gunther/linux-imx8/commit/919a834a865824eeeeb9b98bc4932ae46a614fba</a><br />
+ Look at haptic sensor. Driven by the kernel&#8217;s joystick force feedback<br />
interface (and therefore exposed to userspace as an input<br />
device). We&#8217;ll need write a tiny driver for that.</p>
<h2><strong>Purism in the Public</strong></h2>
<p>Purism employees are not hermits and you can find them at various conferences.  Here are some of the things our employees have done.</p>
<p>&#8211; Dorota: Gave a talk based on Rust+Wayland research, dutifully credited Purism (video incoming&#8230; at some point): <a href="http://rust.cologne/2018/10/10/at-cisco.html">http://rust.cologne/2018/10/10/at-cisco.html</a></p>
<p>&#8211; Adrien and Francois were at Capitole du Libre, running the GNOME booth there.</p>
<p><strong>FOSDEM</strong> &#8211; A number of us will be at FOSDEM doing talks and hanging out.  More information on what our plans are for FOSDEM in another post.</p>
<h2>Closing</h2>
<p>That&#8217;s all for now!  Stay tuned on these pages for new applications, the retrospective on the dev kit, and other features!  Things are rolling fast!  Thank you to our fans for making 2018 a wonderful year and looking forward to 2019!  It&#8217;s going to be awesome!  Thank you for a great year!</p>
<p>The post <a rel="nofollow" href="https://puri.sm/posts/end-of-year-librem-5-update/">End of Year Librem 5 Update</a> appeared first on <a rel="nofollow" href="https://puri.sm/">Purism</a>.</p>
]]></content:encoded>
	<enclosure url="https://puri.sm/wp-content/uploads/2019/01/calls_ring.mp4" length="4770442" type="video/mp4" />
<enclosure url="https://puri.sm/wp-content/uploads/2019/01/libhandy-and-gnome-web.webm" length="1407325" type="video/webm" />
<enclosure url="https://puri.sm/wp-content/uploads/2019/01/chatty-emoji.webm" length="775181" type="video/webm" />
		</item>
		<item>
		<title>Librem 5 dev kits are shipping!</title>
		<link>https://puri.sm/posts/2018-devkits-are-shipping/</link>
		<pubDate>Tue, 18 Dec 2018 22:09:19 +0000</pubDate>
		<dc:creator><![CDATA[Sriram Ramkrishna]]></dc:creator>
				<category><![CDATA[Manufacturing Operations and Logistics]]></category>
		<category><![CDATA[Newsletter and status updates]]></category>
		<category><![CDATA[Phones]]></category>
		<category><![CDATA[Product or service launch]]></category>

		<guid isPermaLink="false">https://puri.sm/?p=61781</guid>
		<description><![CDATA[<p>The Librem 5 dev kit&#8217;s hardware is done and shipping! We are beyond excited for our backers to receive their dev kits before year-end. Our entire PureOS Librem 5 development team will getting the same dev kits, upgrading the generic i.MX 6 boards (which most of the demos you have seen have been based on) [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://puri.sm/posts/2018-devkits-are-shipping/">Librem 5 dev kits are shipping!</a> appeared first on <a rel="nofollow" href="https://puri.sm/">Purism</a>.</p>
]]></description>
				<content:encoded><![CDATA[<p>The Librem 5 dev kit&#8217;s hardware is done and shipping! We are beyond excited for our backers to receive their dev kits before year-end. Our entire PureOS Librem 5 development team will getting the same dev kits, upgrading the generic i.MX 6 boards (which most of the demos you have seen have been based on) to the Purism i.MX 8M based dev kit.</p>
<p>We aim from this point forward to have a community assisted development environment. There is still a lot of work required to make the dev kit truly functional for Librem 5 development, so we need your assistance. The frenetic pace of development continues and it&#8217;s astonishing how much we&#8217;ve accomplished in the two months since we&#8217;ve put the hardware together. But the path is still long and arduous.</p>
<p>Our backers who are receiving the dev kits will also have access to a Matrix channel for dev kit owners. This channel will be staffed by our engineering team who will be on hand to answer questions, work with the community on merge requests, and be available for those who are using the dev kits. But by no means is this an exclusive channel and all of you are welcome to join in as well! Please join our <a href="https://im.puri.sm/#/room/#librem-5-devkit:talk.puri.sm">forum</a> that was set up for questions and answers on the dev kit.</p>
<p><img class="wp-image-61784 alignnone" src="https://puri.sm/wp-content/uploads/2018/12/devkit-image-shipping-300x204.jpeg" alt="" width="469" height="319" srcset="https://puri.sm/wp-content/uploads/2018/12/devkit-image-shipping-300x204.jpeg 300w, https://puri.sm/wp-content/uploads/2018/12/devkit-image-shipping-768x521.jpeg 768w, https://puri.sm/wp-content/uploads/2018/12/devkit-image-shipping.jpeg 1000w" sizes="(max-width: 469px) 100vw, 469px" /> <img class="wp-image-61785 alignnone" src="https://puri.sm/wp-content/uploads/2018/12/file1539881124897-300x169.jpg" alt="" width="578" height="326" srcset="https://puri.sm/wp-content/uploads/2018/12/file1539881124897-300x169.jpg 300w, https://puri.sm/wp-content/uploads/2018/12/file1539881124897-768x432.jpg 768w, https://puri.sm/wp-content/uploads/2018/12/file1539881124897-1024x576.jpg 1024w" sizes="(max-width: 578px) 100vw, 578px" /></p>
<p>With about four months to go until we ship the phones, we are going to need the community to help in the final sprint to the finish line. So we look forward to your help with testing, feature requests, and of course code!</p>
<p>2019 is going to be an amazing year with the introduction of the first privacy and security focused mobile phone and we can&#8217;t wait to get it in your hands.</p>
<p>As always, we are incredibly grateful for all of the support you&#8217;ve shown us and we&#8217;re working hard to do right by your belief in us. We hope to see some of you in our Matrix channels going forward. Till then onward and upward!</p>
<p>&nbsp;</p>
<p><strong> Update: </strong>here&#8217;s a <a href="https://source.puri.sm/groups/Librem5/-/issues?scope=all&amp;utf8=%E2%9C%93&amp;state=opened&amp;label_name[]=devkit">link</a> to our bug tracker with the main issues we&#8217;re trying to resolve with the devkit right now&#8221; at the end of the blog post</p>
<hr />
<p>P.s.: You will note that there is a promotion this holiday season. For those of you who are in the market for a phone and a laptop, check out our &#8220;Have A Secure Life&#8221; Laptop and Phone bundle read further about having a <a href="https://puri.sm/posts/2018-holiday-season-bundle-sale/">secure life.</a></p>
<p>Furthermore, the phone&#8217;s early-bird preorder pricing at $599 will end soon; after January 7th the preorder price will rise to $699 to cover our expenses for the phone. The money coming from this will be used to fund further engineering of the phone and to help people from the community to work on upstream projects.</p>
<p>The post <a rel="nofollow" href="https://puri.sm/posts/2018-devkits-are-shipping/">Librem 5 dev kits are shipping!</a> appeared first on <a rel="nofollow" href="https://puri.sm/">Purism</a>.</p>
]]></content:encoded>
			</item>
	</channel>
</rss>
