<?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>Where is the connected state changed in the UART nrf toolbox?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/18867/where-is-the-connected-state-changed-in-the-uart-nrf-toolbox</link><description>Hello, in the NRF Toolbox UART application for iPhone if you navigate the the UART button screen and connect to the nrf52 eveything is fine. You can exit the app (whitch goes to the background) and come back while the connection stays up. On the UART</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 11 Jan 2017 17:03:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/18867/where-is-the-connected-state-changed-in-the-uart-nrf-toolbox" /><item><title>RE: Where is the connected state changed in the UART nrf toolbox?</title><link>https://devzone.nordicsemi.com/thread/72882?ContentTypeID=1</link><pubDate>Wed, 11 Jan 2017 17:03:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f4200620-14ce-4896-95bf-bd7654ea2eb1</guid><dc:creator>Claude</dc:creator><description>&lt;p&gt;ye, I will continue searching to find where the GUI is destroyed to save the connection state and re-instate it when you come back. If you leave the app (the app going to the background) and come back the connection is preserved so it should not be too difficult.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Where is the connected state changed in the UART nrf toolbox?</title><link>https://devzone.nordicsemi.com/thread/72881?ContentTypeID=1</link><pubDate>Tue, 10 Jan 2017 15:37:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f4e10c1c-77a5-4a19-89dc-7e0c34ab62ba</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Claude,&lt;/p&gt;
&lt;p&gt;It&amp;#39;s a bug with the code. We suspecting it has something wrong with the memory that when the GUI is destroyed the peripheral is also go away with it. Meaning the UART app has no clue it was connected to the peripheral, and when you try to click scan, it won&amp;#39;t be the list because it&amp;#39;s already connected and doesn&amp;#39;t advertise.&lt;/p&gt;
&lt;p&gt;The &amp;quot;Back&amp;quot; button is handled by the OS, it makes it a little bit more difficult to figure out what is wrong. You can try to create your own app based on our UART code without the Back button.&lt;/p&gt;
&lt;p&gt;We will try to fix the issue and release an update as soon as possible.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>