<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									airlogOne Forum - Recent Posts				            </title>
            <link>https://airlogone.com/community/</link>
            <description>airlogOne Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Sun, 22 Nov 2026 13:20:58 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>RE: Battery drain when turned off</title>
                        <link>https://airlogone.com/community/v3-17x/battery-drain-when-turned-off/#post-22</link>
                        <pubDate>Sat, 07 Nov 2026 17:50:27 +0000</pubDate>
                        <description><![CDATA[we did some research, as this was new to us.
and in fact, it can be reproduced.
its tricky, the extra deep_sleep battery drain was introduced with the use of the latest generation of the B...]]></description>
                        <content:encoded><![CDATA[<div>
<p>we did some research, as this was new to us.</p>
<p>and in fact, it can be reproduced.</p>
<p>its tricky, the extra deep_sleep battery drain was introduced with the use of the latest generation of the Bosch pressure sensors (which are the best in the market). Battery in deep sleep is drained in ca one month, coming from 4-6 months before.</p>
<p>No software update helps, needs a hardware patch</p>
<p>IMPORTANT: this is no operational problem and it does not affect the use of the device in operation, its just the quiescent current drawn in sleep mode - the time you're not using the device.</p>
<p>We will do the patch for everyone who wants it and send the device to us. We will fix it and send back free of charge.</p>
<p>And we learned our lesson ;-)</p>
</div>]]></content:encoded>
						                            <category domain="https://airlogone.com/community/"></category>                        <dc:creator>Andreas Jankowsky</dc:creator>
                        <guid isPermaLink="true">https://airlogone.com/community/v3-17x/battery-drain-when-turned-off/#post-22</guid>
                    </item>
				                    <item>
                        <title>Battery drain when turned off</title>
                        <link>https://airlogone.com/community/v3-17x/battery-drain-when-turned-off/#post-21</link>
                        <pubDate>Fri, 06 Nov 2026 11:20:11 +0000</pubDate>
                        <description><![CDATA[I have the weird situation that the battery of my airlog one mini drains even when turned off. It went from full to critically empty without touching it.]]></description>
                        <content:encoded><![CDATA[<p>I have the weird situation that the battery of my airlog one mini drains even when turned off. It went from full to critically empty without touching it.</p>]]></content:encoded>
						                            <category domain="https://airlogone.com/community/"></category>                        <dc:creator>Julius Maetzig</dc:creator>
                        <guid isPermaLink="true">https://airlogone.com/community/v3-17x/battery-drain-when-turned-off/#post-21</guid>
                    </item>
				                    <item>
                        <title>AirlogOne wrist strap.</title>
                        <link>https://airlogone.com/community/feature-requests/airlogone-wrist-strap/#post-20</link>
                        <pubDate>Wed, 07 Oct 2026 16:34:21 +0000</pubDate>
                        <description><![CDATA[Hi, Me again. &#x1f600; First of all, I am really enjoying my AirlogOne. One small issue I noticed is that the attachment on the wrist strap tends to rotate when tightened. (see Photo) I thi...]]></description>
                        <content:encoded><![CDATA[<p>Hi, Me again. &#x1f600; First of all, I am really enjoying my AirlogOne. One small issue I noticed is that the attachment on the wrist strap tends to rotate when tightened. (see Photo) I think the space between the attachments is so large that it allows the strap to rotate. I think a solution is to either minimise the distance between the attachments or to include a bar in the middle to stop the rotation. Does this make sense?  I might try to see if I can get one 3d printed. </p>
<div id="wpfa-1481" class="wpforo-attached-file"><a class="wpforo-default-attachment" href="//airlogone.com/wp-content/uploads/wpforo/default_attachments/1791390861-Airlog-strap.jpg" target="_blank" title="Airlog-strap.jpg"><i class="fas fa-paperclip"></i>&nbsp;Airlog-strap.jpg</a></div>]]></content:encoded>
						                            <category domain="https://airlogone.com/community/"></category>                        <dc:creator>Marcus Cornell</dc:creator>
                        <guid isPermaLink="true">https://airlogone.com/community/feature-requests/airlogone-wrist-strap/#post-20</guid>
                    </item>
				                    <item>
                        <title>RE: Logbook syncing problems</title>
                        <link>https://airlogone.com/community/v3-17x/logbook-syncing-problems/#post-19</link>
                        <pubDate>Sun, 04 Oct 2026 17:29:28 +0000</pubDate>
                        <description><![CDATA[Hi Andreas,
Thanks for the quick reply! In the meantime I managed to solve it myself. I&#039;m sharing what I found in case it helps you or other users.
What I checked first
I made a full back...]]></description>
                        <content:encoded><![CDATA[<p><span>Hi Andreas,</span></p>
<p><span>Thanks for the quick reply! In the meantime I managed to solve it myself. I'm sharing what I found in case it helps you or other users.</span></p>
<p><span><b>What I checked first</b><b></b></span></p>
<p><span>I made a full backup of the SD card and checked </span><span>logbook.log</span><span> and all the jump CSVs. I couldn't find a corrupted line. All entries had the same </span><span>format, and the CSVs for jumps 820/821 were complete and looked normal.</span></p>
<p><span><b>What fixed it</b><b></b></span></p>
<ol>
<li><span>Jump 820 had already been uploaded, so the sync was actually getting stuck on the next jump.</span></li>
<li>I removed all entries up to and including jump 820 from logbook.log manually (so all jumps that were already online) and kept only the header plus jumps 821–844.</li>
<li>After that the sync started at 821, ran all the way to 844 and completed.</li>
<li>The device then cleared logbook.log (header only) and moved the synced entries to a new archive file (15166.log), as it apparently always does after a successful sync.</li>
</ol>
<p><span><b>What I think caused it</b><b></b></span></p>
<p><span>I think it was the amount of data, not a corrupted line. My logbook had grown to 80 jumps (765–844) because I hadn't synced for a while. Adding </span><span>up the CSV files from jump 765 onwards, the total passes </span><span><b>16 MB</b></span><span> at jump 820, exactly where the sync stopped every time. It looks like there's a </span><span>size or time-out limit per sync?</span></p>
<p><span>Because the sync never completed, the logbook was never cleared, so every new attempt started again at 765 and hit the same limit. A loop it</span><span>could never get out of on its own. Once I reduced the logbook, the sync fit under the limit and the device cleaned up as usual.<br /><br /><br /></span></p>]]></content:encoded>
						                            <category domain="https://airlogone.com/community/"></category>                        <dc:creator>PeterMuusers</dc:creator>
                        <guid isPermaLink="true">https://airlogone.com/community/v3-17x/logbook-syncing-problems/#post-19</guid>
                    </item>
				                    <item>
                        <title>RE: Logbook syncing problems</title>
                        <link>https://airlogone.com/community/v3-17x/logbook-syncing-problems/#post-18</link>
                        <pubDate>Sun, 04 Oct 2026 17:03:20 +0000</pubDate>
                        <description><![CDATA[Hi,This sounds like a corrupted line in the logbook.log file on the SD card (the device-written logbook used for transfer).- It is best if you make a ZIP file of the microSD card from the de...]]></description>
                        <content:encoded><![CDATA[<p>Hi,<br /><br />This sounds like a corrupted line in the logbook.log file on the SD card (the device-written logbook used for transfer).<br /><br />- It is best if you make a ZIP file of the microSD card from the device and send it to us at "support@airlog-one.com".<br />- We will try to repair it and provide instructions on how to proceed.<br /><br />Thank you!</p>]]></content:encoded>
						                            <category domain="https://airlogone.com/community/"></category>                        <dc:creator>Andreas Jankowsky</dc:creator>
                        <guid isPermaLink="true">https://airlogone.com/community/v3-17x/logbook-syncing-problems/#post-18</guid>
                    </item>
				                    <item>
                        <title>Logbook syncing problems</title>
                        <link>https://airlogone.com/community/v3-17x/logbook-syncing-problems/#post-17</link>
                        <pubDate>Sun, 04 Oct 2026 16:30:14 +0000</pubDate>
                        <description><![CDATA[Hi guys,


For a while now, every time I open web mode on my device, it starts syncing from jump 765 but never completes the sync. It’s currently stuck at jump 820.
The only thing I can ...]]></description>
                        <content:encoded><![CDATA[<div>
<div>Hi guys,</div>
</div>
<div>
<p>For a while now, every time I open web mode on my device, it starts syncing from jump 765 but never completes the sync. It’s currently stuck at jump 820.</p>
<p>The only thing I can do at that point is restart the device. However, when I reconnect, syncing starts again from jump 765, and it never reaches the end of my jump list.</p>
<p>Is there a way to resolve this? I wouldn’t mind resetting my logbook both on the device and online if that would help.</p>
<p>Kind regards,<br />SN: B344-77078</p>
</div>]]></content:encoded>
						                            <category domain="https://airlogone.com/community/"></category>                        <dc:creator>PeterMuusers</dc:creator>
                        <guid isPermaLink="true">https://airlogone.com/community/v3-17x/logbook-syncing-problems/#post-17</guid>
                    </item>
				                    <item>
                        <title>RE: GPS - direction of dropzone</title>
                        <link>https://airlogone.com/community/v3-17x/gps-direction-of-dropzone/#post-11</link>
                        <pubDate>Sun, 26 Jul 2026 12:53:20 +0000</pubDate>
                        <description><![CDATA[@ajanky To tell the truth, I found this problem during the flight in an airplane.]]></description>
                        <content:encoded><![CDATA[@ajanky To tell the truth, I found this problem during the flight in an airplane.]]></content:encoded>
						                            <category domain="https://airlogone.com/community/"></category>                        <dc:creator>Ucio</dc:creator>
                        <guid isPermaLink="true">https://airlogone.com/community/v3-17x/gps-direction-of-dropzone/#post-11</guid>
                    </item>
				                    <item>
                        <title>RE: GPS - direction of dropzone</title>
                        <link>https://airlogone.com/community/v3-17x/gps-direction-of-dropzone/#post-10</link>
                        <pubDate>Sun, 26 Jul 2026 12:47:17 +0000</pubDate>
                        <description><![CDATA[OK, we made a code review for three versions, specifically from 2024, 2025, and 2026 (=V3.17x), and found no relevant code changes, as I suggested.However, what we changed with the V3.17 is ...]]></description>
                        <content:encoded><![CDATA[<p>OK, we made a code review for three versions, specifically from 2024, 2025, and 2026 (=V3.17x), and found no relevant code changes, as I suggested.<br /><br />However, what we changed with the V3.17 is increasing the GPS acceleration limit to 2G because we sometimes noticed a short period of GPS dropouts exactly during canopy openings. This change can matter in the problem you have seen because GPS-heading filtering inside the GPS receiver is reduced for high-speed acceleration, notably in low-speed situations.<br /><br />So we will add extra filtering for low-speed heading values and will see if this improves the arrow. It needs some testing, and I would be happy to send you a version with our edits to see if it improves.<br /><br />Thank you for your input, we're working on this.<br /><br />Andreas</p>]]></content:encoded>
						                            <category domain="https://airlogone.com/community/"></category>                        <dc:creator>Andreas Jankowsky</dc:creator>
                        <guid isPermaLink="true">https://airlogone.com/community/v3-17x/gps-direction-of-dropzone/#post-10</guid>
                    </item>
				                    <item>
                        <title>RE: GPS - direction of dropzone</title>
                        <link>https://airlogone.com/community/v3-17x/gps-direction-of-dropzone/#post-9</link>
                        <pubDate>Sat, 25 Jul 2026 15:50:40 +0000</pubDate>
                        <description><![CDATA[@ajanky To be honest, I’m not sure what the previous version was, I think it was 3.15; but I’ve noticed a change in behavior: before, once the landing point was set, the arrow always pointed...]]></description>
                        <content:encoded><![CDATA[@ajanky To be honest, I’m not sure what the previous version was, I think it was 3.15; but I’ve noticed a change in behavior: before, once the landing point was set, the arrow always pointed to the correct spot, whereas now, after the update, it’s often incorrect (sometimes significantly so).]]></content:encoded>
						                            <category domain="https://airlogone.com/community/"></category>                        <dc:creator>Ucio</dc:creator>
                        <guid isPermaLink="true">https://airlogone.com/community/v3-17x/gps-direction-of-dropzone/#post-9</guid>
                    </item>
				                    <item>
                        <title>RE: GPS - direction of dropzone</title>
                        <link>https://airlogone.com/community/v3-17x/gps-direction-of-dropzone/#post-8</link>
                        <pubDate>Fri, 24 Jul 2026 06:02:44 +0000</pubDate>
                        <description><![CDATA[Hi, That&#039;s an interesting observation. I can&#039;t quite figure it out (yet). Which software version did you update from? As far as I recall, there haven&#039;t been any recent changes to the directi...]]></description>
                        <content:encoded><![CDATA[Hi, That's an interesting observation. I can't quite figure it out (yet). Which software version did you update from? As far as I recall, there haven't been any recent changes to the direction calculation. But I'll be happy to look into it. We'll go through the code to see if there's any indication of such behavior. <br />if you have more background information, please let us know]]></content:encoded>
						                            <category domain="https://airlogone.com/community/"></category>                        <dc:creator>Andreas Jankowsky</dc:creator>
                        <guid isPermaLink="true">https://airlogone.com/community/v3-17x/gps-direction-of-dropzone/#post-8</guid>
                    </item>
							        </channel>
        </rss>
		