<?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>Eddystone + iBeacon UUID advertising issue</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/85608/eddystone-ibeacon-uuid-advertising-issue</link><description>Hello everybody, 
 
 My project is based ble_app_eddystone example and nRF5_SDK_17.2.0 SOC is nRF52832. 
 Beacon advertise Eddystone UID +Eddystone TLM +Eddystone URL, works ok. 
 I understood that The Eddystone Project uses a timer to modify/update ad</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 09 Mar 2022 16:08:01 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/85608/eddystone-ibeacon-uuid-advertising-issue" /><item><title>RE: Eddystone + iBeacon UUID advertising issue</title><link>https://devzone.nordicsemi.com/thread/357259?ContentTypeID=1</link><pubDate>Wed, 09 Mar 2022 16:08:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9c510c87-e557-423f-bb52-63c8fbe74c30</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;That depends on what you want to use it for. I suggest you refer to the official statement google made: &lt;a href="https://android-developers.googleblog.com/2018/10/discontinuing-support-for-android.html"&gt;Discontinuing support for Android Nearby Notifications&lt;/a&gt;&amp;nbsp;to see to what degree it is relevant for you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Eddystone + iBeacon UUID advertising issue</title><link>https://devzone.nordicsemi.com/thread/357232?ContentTypeID=1</link><pubDate>Wed, 09 Mar 2022 15:06:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f0743bf8-17d0-4d0c-a1f6-96a7de77a7fe</guid><dc:creator>rh.amine</dc:creator><description>&lt;p&gt;I did not completely understand!!!&lt;br /&gt;that means we won&amp;#39;t be able to use it, or else it will be of no use to us.?&lt;/p&gt;
&lt;p&gt;can you explain me in detail please??&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Eddystone + iBeacon UUID advertising issue</title><link>https://devzone.nordicsemi.com/thread/357179?ContentTypeID=1</link><pubDate>Wed, 09 Mar 2022 13:31:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fbc926dc-7653-4c69-a287-dba324dfda49</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I do not have any ready made project that combine this, but there are some old threads about it, for instance &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/43305/trying-to-setup-a-alternating-eddystone-and-ibeacon-advertising-using-the-nrf52-dk-using-timeslot-api/170967#170967"&gt;this one&lt;/a&gt;. The Eddystone example is quite complex though, so this may be a bit of work.&lt;/p&gt;
&lt;p&gt;By the way, may I ask for what you are using Eddystone, seen as &lt;a href="https://en.wikipedia.org/wiki/Eddystone_(Google)#Discontinued_date"&gt;Google has discontinued it&lt;/a&gt;?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>