<?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>Android DFU failure when device not found through scanning</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/85129/android-dfu-failure-when-device-not-found-through-scanning</link><description>I&amp;#39;m using Android DFU library 1.11.1 and occasionally I see &amp;quot;E/DfuBaseService: Connection state change error: 133 newState: 0&amp;quot; errors. It appears they happen when the initial scan for devices (after performing buttonless DFU entry) does not find the device</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 25 Feb 2022 14:41:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/85129/android-dfu-failure-when-device-not-found-through-scanning" /><item><title>RE: Android DFU failure when device not found through scanning</title><link>https://devzone.nordicsemi.com/thread/355073?ContentTypeID=1</link><pubDate>Fri, 25 Feb 2022 14:41:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e87431c7-64fc-4eeb-9d6f-eee65051a3ef</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Try to do the same with &lt;a href="https://github.com/NordicSemiconductor/Android-DFU-Library/releases/tag/1.12.1-beta01"&gt;1.12.1-beta01&lt;/a&gt; and see if it works then.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Sigurd Hellesvik&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>