<?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>change advertised devicename</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/16602/change-advertised-devicename</link><description>Hi, 
 In SDK11 I was able to update advertised device name without restart, just handled write on the characteristic and update advertising data (through a second call to ble_advertising_init). sd_ble_gap_device_name_set seems to be called automatically</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 23 Sep 2016 11:59:51 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/16602/change-advertised-devicename" /><item><title>RE: change advertised devicename</title><link>https://devzone.nordicsemi.com/thread/63516?ContentTypeID=1</link><pubDate>Fri, 23 Sep 2016 11:59:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bd6aba25-53f7-4e31-9c08-4c67c5e641e7</guid><dc:creator>S&amp;#233;bastien Le Ray</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;First, this code does not use SD3 device_name_t struct, so the question about ignored write_perm (and device name value) by the new device name setting code is still valid.&lt;/p&gt;
&lt;p&gt;Secondly I found out that ble_advertising_init to reset device name works //only// if you&amp;#39;re currently advertising while S132v2 (&lt;strong&gt;same code&lt;/strong&gt;) worked fine, no matter if you were currently advertising, connected or not&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: change advertised devicename</title><link>https://devzone.nordicsemi.com/thread/63515?ContentTypeID=1</link><pubDate>Fri, 23 Sep 2016 11:45:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:af8903b0-a569-42af-a3e9-341419e16b23</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;I think you have done some kind of mistake in your code. I did a quick test by modifying the Heart Rate Application in SDK 12 (see attached modified &lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/48655.main.c"&gt;main.c&lt;/a&gt;). If you build and flash it, you will see that it advertises as &amp;quot;Nordic_HRM&amp;quot; initially. After a long button 2 push, it will advertise as &amp;quot;New&amp;quot;.&lt;/p&gt;
&lt;p&gt;Essentially the steps are the same as with earlier SoftDevice and SDK versions:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Call &lt;code&gt;sd_ble_gap_device_name_set()&lt;/code&gt; with the new device name&lt;/li&gt;
&lt;li&gt;Call &lt;code&gt;ble_advdata_set()&lt;/code&gt;. (Using the advertising module you typically don&amp;#39;t do this directly, but indirectly by a call to &lt;code&gt;ble_advertising_start()&lt;/code&gt; or (as I did in the attached example) &lt;code&gt;ble_advertising_restart_without_whitelist()&lt;/code&gt;.)&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>