<?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>Simulating beacon with smartphone</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/75055/simulating-beacon-with-smartphone</link><description>We are currently working on a project where we use a NRF52832 in a beacon to act as a keyfob for another device. We are concerned that if we lose the key we cannot use the device since we are not able to then connect a new beacon to the device. Is there</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 12 May 2021 12:31:08 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/75055/simulating-beacon-with-smartphone" /><item><title>RE: Simulating beacon with smartphone</title><link>https://devzone.nordicsemi.com/thread/309501?ContentTypeID=1</link><pubDate>Wed, 12 May 2021 12:31:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6df37b76-338b-4d0c-bfb1-3a1c9a2db2b3</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Jacob,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Our nRF Connect app on Android/iOS can clone a beacon and broadcasting that same data using the phone (It&amp;#39;s the clone button when you click on an advertiser)&amp;nbsp;&lt;/p&gt;
&lt;p&gt;However, the main challenge here is if the beacon keep broadcasting the same data or it&amp;#39;s the dynamic data that the beacon transmit. If it&amp;#39;s the dynamic data that change over time, the phone&amp;nbsp;won&amp;#39;t be able to generate that dynamic data because it doesn&amp;#39;t have the algorithm. You would need to implement the algorithm in your own app to generate such data.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Simulating beacon with smartphone</title><link>https://devzone.nordicsemi.com/thread/309482?ContentTypeID=1</link><pubDate>Wed, 12 May 2021 11:54:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e6f1603b-7f6b-4ad7-a68b-12f129b33402</guid><dc:creator>swanav</dc:creator><description>&lt;p&gt;Hey Jacob,&lt;/p&gt;
&lt;p&gt;The experts at Nordic might be able to guide you with a better solution, but thought I&amp;#39;d drop my 2 cents.&lt;/p&gt;
&lt;p&gt;I would suggest using the iBeacon format for your beacon, since the iOS natively supports generating beacons in this format.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://developer.apple.com/documentation/corelocation/turning_an_ios_device_into_an_ibeacon_device"&gt;https://developer.apple.com/documentation/corelocation/turning_an_ios_device_into_an_ibeacon_device&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The licensing and easy application of this format should allow you to realize this use-case, since iBeacons can be broadcasted by an iOS, Android as well as any native BLE device (nRF52832) in your instance.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;If you do not need to support iOS devices, you can also look into the Eddystone beacon format, which is Google&amp;#39;s format (but more flexible in terms of payload).&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/google/eddystone"&gt;https://github.com/google/eddystone&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Also, if your usecase is just about BLE Beacons you might want to look into the nRF52805, since it should be able to serve you abundantly.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>