Is your feature request related to a problem? Please describe.
Using the nRF Connect application on Android (version 4.29.1) today, I noticed that it does not recognize some of the newer (last 2-3 years) advertising data types when scanning, specifically 0x30 Broadcast_Name from Assigned Numbers (https://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/Assigned_Numbers/out/en/Assigned_Numbers.pdf section 2.3).
Describe the solution you'd like
Add missing AD data types from assigned numbers
Describe alternatives you've considered
Consider adding support for user-defined AD types for handle such cases in the future, similar to how users can add GATT service UUIDs
Additional context
N/A
Is your feature request related to a problem? Please describe.
Using the nRF Connect application on Android (version 4.29.1) today, I noticed that it does not recognize some of the newer (last 2-3 years) advertising data types when scanning, specifically 0x30 Broadcast_Name from Assigned Numbers (https://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/Assigned_Numbers/out/en/Assigned_Numbers.pdf section 2.3).
Describe the solution you'd like
Add missing AD data types from assigned numbers
Describe alternatives you've considered
Consider adding support for user-defined AD types for handle such cases in the future, similar to how users can add GATT service UUIDs
Additional context
N/A