EDIT (10th June 2023): Betaflight 4.4.2 is now available. See another thread HERE for details.

Betaflight maintenance release 4.4.1 was published a few hours ago. Details of the fixes since Betaflight 4.4.0 are below along with any relevant links.

• Betaflight 4.4.1 Firmware & Release Notes: https://github.com/betaflight/betaflight.../tag/4.4.1
  
• Betaflight Configurator 10.9.0: https://github.com/betaflight/betaflight...tag/10.9.0
  
• Betaflight TX LUA Scripts 1.7.0: https://github.com/betaflight/betaflight.../tag/1.7.0
  
• Blackbox Log Viewer 3.6.0: https://github.com/betaflight/blackbox-l.../tag/3.6.0
  
• Betaflight 4.4 Release Notes: https://betaflight.com/docs/release/Beta...ease-Notes
  

For information about the original Betaflight 4.4.0 release, see another thread HERE.

One important fix to note in this release is to the AA filter for the ICM426XX gyros (issue #12444) that were causing some people who were running those gyros some significant issues.

Unfortunately it doesn't look like the GPS Rescue improvements (PR #12343) were included in this maintenance release because there is no mention of it in the release notes and that PR only appears to have been merged into the master branch, so it looks like we will have to wait for Betaflight 4.5 before we get those improvements, or use a nightly build of the master branch. EDIT: The GPS Rescue improvements did actually make it into this maintenance release after all, but under a different PR (#12413) which isn't listed anywhere in the official Betaflight 4.4.1 release notes. I have therefore now added an additional entry to the list below for that under the "Improvements" heading even though it's still not listed in the official release notes on GitHub.

IMPORTANT NOTE: User's of H7 FC's that utilises an SD Card for blackbox logging should be aware that a bug in Betaflight 4.4.1 prevents the FC from logging data to the SD Card. More details are in post #11 of this thread.


What's Changed

Improvements

• Improve GPS Rescue Pitch smoothing and disarming by @blckmn in #12413 
  
• Fix unified targets that use OctoSPI. (BF4.4.x) by @hydra in #12307
  
• Increase FF smoothing max to suit elrs 1000hz link rate (#12426) by @limonspb in #12433
  

Fixes

• Fix max permissible CMS rows and up/down page arrows (#12277) by @SteveCEvans in #12284
  
• Rollup 1 by @hydra in #12306
  
• Fix SDFT batchSize rounding by @KarateBrot in #12332
  
• Latest changes from unified targets, and sdcard build fix. by @blckmn in #12415
  
• H7 Fix frozen ADC values by @klutvott123 in #12443
  
• ICM426XX AA filter (#12444) by @sugaarK in #12465
  
• Blackbox (as applied to 4.5.0) by @blckmn in #12520
  
• DShot zero between beacon commands for 4.4, from 12544 by @ctzsnooze in #12555
  
• Restore DShot Beacon control for 4.4 by @ctzsnooze in #12560
  
• Include smartport telemetry for Fport (#12314) by @klutvott123 in #12572
  
• Exclude MSP_OSD_CONFIG if USE_OSD not defined (#12513) by @klutvott123 in #12590
  
• Add separate AAF values for ICM-42605 by @sugaarK in #12616
  

Targets

• Patch for config.h files by @blckmn in #12380
  
• Adding support for building by config by @blckmn in #12376
  
• FIX CONFIG: Adding USE_ACC, USE_GYRO and USE_BARO where appropriate. by @blckmn in #12477
  
• FIX CONFIG: Adding USE_FLASH to enable where hardware supports by @blckmn in #12499
  

Full Changelog: 4.4.0...4.4.1

Very important one that is not listed in changes ... https://github.com/betaflight/betaflight/pull/12413

(06-Apr-2023, 07:29 PM)MomoBrut Wrote: Very important one that is not listed in changes ... https://github.com/betaflight/betaflight/pull/12413

This is the same as PR #12343 mentioned in the last paragraph of the first post. I was expecting this fix be part of Betaflight 4.4.1 which is why I held off installing Betaflight 4.4.0. I guess I'll just get on with it and install this version instead of waiting around for the Betaflight 4.5 release.

Well I see, I didn't notice, I didn't check the numbers only the text.

I just updated to 4.4.1 and there was a problem again. I have a non-standard FC target and I need a non-standard build, I need to add BMP280 and Vario support. Well, they changed it again when I did a custom build for 4.4, the user defines entry was BARO_BMP280 VARIO. Well, that doesn't work now, it doesn't report an error, chaos. I spent almost an hour testing, there is no documentation, the original list on github with all the #defines is no longer available, what is this again? So by trial and error I figured out that BARO BARO_BMP280 VARIO should now be specified to make a build with the correct support...again,again,again...

Yeah, I'm sure there used to be a list of all the possible defines listed HERE but they all seem to be gone now with the only option being to submit support data to the Betaflight devs and then ask on GitHub for someone to advise you what defines you need to add, or start the time consuming task of digging through the Betaflight source code to try and figure out what defines are being used.

It would be way better if there was a current up-to-date list of all possible defines listed somewhere so that people with some level of technical understanding can at least have a go at picking the defines they think might be applicable (even if by trial and error) without having to wait around for a response to a support request. I guess we can only hope for that in the future.

With cloud build can't you just add any commits you want? I think Bardwell uses that same pr in his example.
https://youtu.be/YmTq68M-NkU?t=576

(07-Apr-2023, 12:05 PM)mstc Wrote: With cloud build can't you just add any commits you want? I think Bardwell uses that same pr in his example.
https://youtu.be/YmTq68M-NkU?t=576

I've already seen JB's video on that but it still leaves a lot of unanswered questions as to how it actually works, and again there seems to be ZERO documentation about it anywhere that I can find. What if you want to include a commit into a Betaflight 4.4.x build that was destined for the Betaflight 4.5 release? Maybe there are dependencies on the commit that you also need to include, or which won't work in Betaflight 4.4.x, and who has tested that it actually works properly in different releases? Can it even be included in a different release? Unless you are a Betaflight dev or are prepared to spend the time and risks with trial-and-error builds and flights then there seems to be no real way of knowing.

(07-Apr-2023, 11:44 AM)SnowLeopardFPV Wrote: It would be way better if there was a current up-to-date list of all possible defines listed somewhere so that people with some level of technical understanding can at least have a go at picking the defines they think might be applicable (even if by trial and error) without having to wait around for a response to a support request. I guess we can only hope for that in the future.

Recently found it here : https://betaflight.com/docs/manufacturer...guidelines (scroll to bottom , chapter 4.2. And remove the 'USE_" to have your list of defines to use )

Thanks for the link listing all #defines. In any case, even here it is not written how to do it, and unfortunately they changed it from version 4.4.

It is probably the case that first (this was originally not necessary for the early 4.4 builds) during the build of the non-standard target in the custom defines, it is necessary to activate the required component at all, e.g. BARO, MAG, GYRO, FLASH, etc. and only then specify which the type of component it should be, e.g. BARO_BMP280, which is for I2C or BARO_SPI_BMP280, which is for connecting via SPI.

And above all, there is not a word about the activation of vario, nor is there a word about the fact that vario is disabled by default.

People with an H7 FC should take note that this Betaflight 4.4.1 release has fixed the issue where voltage and current readings were freezing in the telemetry and OSD data under Betaflight 4.4.0.

So while the ADC issue has been fixed in Betaflight 4.4.1 for H7 based FC's, another bug has unfortunately been introduced whereby blackbox logging on H7 FC's that use an SD Card for logging the data to no longer works in Bataflight 4.4.1. This will be fixed in Betaflight 4.4.2 but until then anyone with an H7 FC that utilises an SD Card for blackbox data has the choice of either Betaflight 4.4.0 with no current / voltage readings (due to the ADC bug), or Betaflight 4.4.1 with no blackbox logging capabilities, so not a great Betaflight release for users of those H7 FC's. It's therefore probably best for those users to just go back to Betaflight 4.3.x until such time that Betaflight 4.4.2 is published.

For reference the details can be found in GitHub issue #12647 and the fix can be found in PR #12671.

Anyone looking at this post should keep in mind that BF has since been updated to 4.4.2

https://intofpv.com/t-betaflight-4-4-2-r...-available

(22-Jun-2023, 03:40 PM)mattyfleischfpv Wrote: Anyone looking at this post should keep in mind that BF has since been updated to 4.4.2

https://intofpv.com/t-betaflight-4-4-2-r...-available

Yes, hence this thread: https://intofpv.com/t-betaflight-4-4-2-r...-available