<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Advertisement in BL5 isn&amp;#39;t visible</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/111403/advertisement-in-bl5-isn-t-visible</link><description>Hello, 
 I&amp;#39;m trying to test and document my device (nrf52840 pcb) BLE5 abilities . so far i tested connection and dfu using my nrf connect mobile app. 
 Now its time to test advertisement. i tested it using BLE_GAP_ADV_TYPE_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 24 May 2024 07:40:46 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/111403/advertisement-in-bl5-isn-t-visible" /><item><title>RE: Advertisement in BL5 isn't visible</title><link>https://devzone.nordicsemi.com/thread/485733?ContentTypeID=1</link><pubDate>Fri, 24 May 2024 07:40:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b716ed7f-4ea6-4672-9ac0-7b0c9ab43d25</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi Raz&lt;/p&gt;
&lt;p&gt;Advertising extensions, coded phy and 2M support were all added in Bluetooth 5, so the difference between 5.2 and 5.3 should not make a difference. The problem is that the phones probably use different wireless chipsets with different feature sets and different low level drivers.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The Bluetooth specification includes a lot of optional features which doesn&amp;#39;t necessarily need to be implemented, and which of these optional features are included varies between vendors.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Advertisement in BL5 isn't visible</title><link>https://devzone.nordicsemi.com/thread/485633?ContentTypeID=1</link><pubDate>Thu, 23 May 2024 12:31:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:93c5e520-88bb-414f-8904-b247de77aa5e</guid><dc:creator>Raz_k</dc:creator><description>&lt;p&gt;Hey,&amp;nbsp;&lt;span&gt;Torbj&amp;oslash;rn&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;I just looked again on the &lt;span&gt;B&lt;/span&gt;&lt;span&gt;luetooth&amp;nbsp;&lt;/span&gt;specification of both phones.&lt;/p&gt;
&lt;p&gt;Samsung Galaxy S24 has B&lt;span&gt;luetooth&amp;nbsp;5.3, while Google Pixel has Bluetooth&amp;nbsp;5.2.&amp;nbsp;&lt;br /&gt;I did some research between the key differences but i didn&amp;#39;t notice any thing that can explain the reason that the device wasn&amp;#39;t shown in the app.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;It would be great to understand this phenomenon, but for no i have my solution.&amp;nbsp;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thanks!!&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Advertisement in BL5 isn't visible</title><link>https://devzone.nordicsemi.com/thread/485606?ContentTypeID=1</link><pubDate>Thu, 23 May 2024 11:06:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:218f661b-d0c8-4121-a73f-7ed152ed2b7a</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi Raz&lt;/p&gt;
&lt;p&gt;I discussed this with one of the Android developers, and apparently the coded support in different phones is very fragmented. Even if they claim to support coded phy they don&amp;#39;t necessarily support all the different features needed.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For more information please refer to the information shared in &lt;a href="https://github.com/NordicSemiconductor/Android-BLE-Library/issues/166"&gt;this github issue&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Samsung phones generally seem to offer the best performance and feature set for BLE on the Android side.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Torbjørn&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Advertisement in BL5 isn't visible</title><link>https://devzone.nordicsemi.com/thread/485452?ContentTypeID=1</link><pubDate>Wed, 22 May 2024 14:04:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4d7973b7-f61c-448b-b14d-bba6365929a2</guid><dc:creator>Raz_k</dc:creator><description>&lt;p&gt;Thanks&amp;nbsp;&lt;span&gt;Torbj&amp;oslash;rn,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I&amp;#39;m using google pixel 6a, and i was able to connect and dfu using&amp;nbsp;2M PHY and&amp;nbsp;CODED PHY and nrf Connect app for mobile, as such:&lt;br /&gt;connect-&amp;gt;Set preferred PHY-&amp;gt;and then you can see in the device log there is an update to the chosen PHY.&lt;br /&gt;&lt;/span&gt;That&amp;#39;s why i assume that my phone can support it.&amp;nbsp;&lt;br /&gt;However i am not able to see the advertising device.&lt;/p&gt;
&lt;p&gt;But i tried again with Samsung galaxy S24 with the app and it was able to see the advertising device.&lt;br /&gt;I wonder if it is&amp;nbsp;due to different phones specifications or some thing is defined differently in the&amp;nbsp;&lt;span&gt;nrf Connect app for mobile.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Advertisement in BL5 isn't visible</title><link>https://devzone.nordicsemi.com/thread/485429?ContentTypeID=1</link><pubDate>Wed, 22 May 2024 13:05:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:525beef8-4ef1-4884-bd21-4fe536cc4c6c</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi Raz&lt;/p&gt;
[quote user=""]So i tried using&amp;nbsp;BLE_GAP_ADV_TYPE_EXTENDED_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED, here i am not getting an error, but i also cant see the advertisement in my nrf mobile app (yes, my mobile device is suitable for &lt;span&gt;2M PHY and&amp;nbsp;CODED PHY)&lt;/span&gt;.[/quote]
&lt;p&gt;Which phone do you have, and which app are you using to scan for the advertisements?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In some apps it might be necessary to enable extended advertising and/or coded phy explicitly before starting the scan.&amp;nbsp;&lt;/p&gt;
[quote user=""]Pluse i didnt really understand the diffrance between&amp;nbsp;BLE_GAP_ADV_TYPE_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED&amp;nbsp; vs&amp;nbsp;BLE_GAP_ADV_TYPE_EXTENDED_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED[/quote]
&lt;p&gt;The extended advertising specification was added in Bluetooth 5, and includes a larger advertising payload that have more capabilities than the &amp;#39;legacy&amp;#39; advertising specification in Bluetooth 4. Extended advertising is necessary in order to do things like advertising on secondary channels, advertising on other PHY&amp;#39;s (legacy advertising supports 1M only), advertise packets larger than 37 bytes, and do things like chained or periodic advertisements.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;For a more detailed description you can refer to the following blog:&lt;br /&gt;&lt;a href="https://novelbits.io/bluetooth-5-advertisements/"&gt;https://novelbits.io/bluetooth-5-advertisements/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>