<?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>feedback: BLE_GAP_DEVNAME_MAX_LEN is too short</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/5171/feedback-ble_gap_devname_max_len-is-too-short</link><description>The core specification v4.0 vol 3 part C section 3.2.2.3 &amp;quot;Bluetooth Device Name -- Representation&amp;quot; states that the device name can be up to 248 bytes. I&amp;#39;ve confirmed that sd_ble_gap_device_name_set rejects long device names, consistent with BLE_GAP_DEVNAME_MAX_LEN</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 28 Jan 2015 12:41:02 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/5171/feedback-ble_gap_devname_max_len-is-too-short" /><item><title>RE: feedback: BLE_GAP_DEVNAME_MAX_LEN is too short</title><link>https://devzone.nordicsemi.com/thread/18114?ContentTypeID=1</link><pubDate>Wed, 28 Jan 2015 12:41:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:db404631-ce89-4741-8d4e-505e4efa7bb3</guid><dc:creator>pabigot</dc:creator><description>&lt;p&gt;While the line I cited does say &amp;quot;can be up to 248 bytes&amp;quot;, Vol 1 Part E section 1.6 states that &amp;quot;can&amp;quot; is informative, not normative, and may be read as &amp;quot;is able to&amp;quot;.  Volume 2 Part C section 4.3.5 repeats the 248 byte maximum but does not use normative language nor suggest a minimum that must be supported.&lt;/p&gt;
&lt;p&gt;I expect the answer can be found somewhere in the 2771 pages of Core V4.2, and hoped somebody would know where, just to satisfy curiosity.  It&amp;#39;s not that important, though.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: feedback: BLE_GAP_DEVNAME_MAX_LEN is too short</title><link>https://devzone.nordicsemi.com/thread/18113?ContentTypeID=1</link><pubDate>Wed, 28 Jan 2015 10:38:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:867c4f83-bb59-4297-a31b-e1de7f2b751e</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;Thank you for the feedback.&lt;/p&gt;
&lt;p&gt;Yes, the Bluetooth spec allows it. It says &amp;quot;The Bluetooth device name &lt;em&gt;can&lt;/em&gt; be up to 248 bytes&amp;quot;.&lt;/p&gt;
&lt;p&gt;Earlier it was 20 bytes, but we have increased it 31 bytes.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>