<?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>Galaxy Tab A8 fails to connect properly, while Galaxy Phone S10 works fine</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/115242/galaxy-tab-a8-fails-to-connect-properly-while-galaxy-phone-s10-works-fine</link><description>Galaxy Tab A8 connects, but then disconnects after a burst of approx 600 &amp;quot;Central_0x2a208f55 Peripheral_0x2a208f55 ATT 37 Sent Read By Group Type Request, Primary Service, Handles: 0x0001..0xffff&amp;quot; 
 Galaxy S10 works fine 
 Bot are running the same mobile</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 14 Oct 2024 07:31:07 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/115242/galaxy-tab-a8-fails-to-connect-properly-while-galaxy-phone-s10-works-fine" /><item><title>RE: Galaxy Tab A8 fails to connect properly, while Galaxy Phone S10 works fine</title><link>https://devzone.nordicsemi.com/thread/506017?ContentTypeID=1</link><pubDate>Mon, 14 Oct 2024 07:31:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d2c5c2d4-efe3-45fa-9156-7d990c139304</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;After a quick chat with one of our Android developers there is nothing we can do in the Android BLE library to ignore this auto PHY updates, as the Android stack will adhere to these if 2MBPS is supported.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Galaxy Tab A8 fails to connect properly, while Galaxy Phone S10 works fine</title><link>https://devzone.nordicsemi.com/thread/505360?ContentTypeID=1</link><pubDate>Tue, 08 Oct 2024 13:02:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:319bb44e-f017-4342-a208-afc8a2bc7f65</guid><dc:creator>tellg</dc:creator><description>&lt;p&gt;That doesn&amp;#39;t work, as the peripheral sets it back to 2MBPS, due to&amp;nbsp;&lt;span&gt;CONFIG_BT_AUTO_PHY_UPDATE as default, &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;which is &amp;#39;y&amp;#39;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Sniffer log attached&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/try_2D00_1mbit_2D00_phy_2D00_from_2D00_nrfconnect.pcapng"&gt;devzone.nordicsemi.com/.../try_2D00_1mbit_2D00_phy_2D00_from_2D00_nrfconnect.pcapng&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Galaxy Tab A8 fails to connect properly, while Galaxy Phone S10 works fine</title><link>https://devzone.nordicsemi.com/thread/505349?ContentTypeID=1</link><pubDate>Tue, 08 Oct 2024 12:42:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a020978d-2bec-4952-aa86-b6c1cfab770b</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Ah, of course. Sorry about that. The preferred PHY is indeed only a suggestion and will be negotiated upon a connection. AFAIK there is no way to hard set the used PHY to automatically set o 1MBPS, but you can change the PHY manually after connecting to the device by going to the connection settings and changing it from there.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Galaxy Tab A8 fails to connect properly, while Galaxy Phone S10 works fine</title><link>https://devzone.nordicsemi.com/thread/505126?ContentTypeID=1</link><pubDate>Mon, 07 Oct 2024 09:07:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d22ff1ad-3ebf-48f0-ba9f-69eeac396715</guid><dc:creator>tellg</dc:creator><description>&lt;p&gt;That does not help, as we anyhow end up in 2MBPS as soon as connection is done&lt;/p&gt;
&lt;p&gt;I also tried this macro, but still end up in 2MBPS&amp;nbsp;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/SetPreferredPhy_5F00_1M.xml"&gt;devzone.nordicsemi.com/.../SetPreferredPhy_5F00_1M.xml&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;nRFConnect log:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/3051.Log_5F00_2024_2D00_10_2D00_07_5F00_11_5F00_14_5F00_25.txt"&gt;devzone.nordicsemi.com/.../3051.Log_5F00_2024_2D00_10_2D00_07_5F00_11_5F00_14_5F00_25.txt&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Seems like setPreferredPhy is just a recommendation, and depends on local and remote controllers behaviour&lt;/p&gt;
&lt;p&gt;&lt;a href="https://developer.android.com/reference/android/bluetooth/BluetoothGatt#setPreferredPhy(int,%20int,%20int)"&gt;https://developer.android.com/reference/android/bluetooth/BluetoothGatt#setPreferredPhy(int,%20int,%20int)&lt;/a&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Galaxy Tab A8 fails to connect properly, while Galaxy Phone S10 works fine</title><link>https://devzone.nordicsemi.com/thread/505125?ContentTypeID=1</link><pubDate>Mon, 07 Oct 2024 09:02:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0f803169-c4c9-4dd3-bd64-f8d036af9000</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;At least in the nRF Connect for Android app you can set the supported PHYs in the settings of the app (Settings -&amp;gt; Scanner -&amp;gt; Physical layer) to 1MBPS if you&amp;#39;d like.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Galaxy Tab A8 fails to connect properly, while Galaxy Phone S10 works fine</title><link>https://devzone.nordicsemi.com/thread/504993?ContentTypeID=1</link><pubDate>Fri, 04 Oct 2024 12:07:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ba85127e-c186-45eb-9c96-7f610d50bace</guid><dc:creator>tellg</dc:creator><description>&lt;p&gt;We have seen that it helps setting&amp;nbsp; CONFIG_BT_AUTO_PHY_UPDATE=n on the peripheral, and setting client side mcumgr initial mtu setting to 23&lt;/p&gt;
&lt;p&gt;ref&amp;nbsp;&lt;a href="https://github.com/search?q=repo%3ANordicSemiconductor%2FAndroid-nRF-Connect-Device-Manager%20initialmtu&amp;amp;type=code"&gt;https://github.com/search?q=repo%3ANordicSemiconductor%2FAndroid-nRF-Connect-Device-Manager%20initialmtu&amp;amp;type=code&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Downside is that devices already out in the field have&amp;nbsp;&lt;span&gt;CONFIG_BT_AUTO_PHY_UPDATE as default, which is &amp;#39;y&amp;#39;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Is it possible from mcumgr android library to force using 1 Mbit phy when the device is SM-X200 (Galaxy tab A8)?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;If so, then maybe also do this in the other libraries for SM-X200 (&lt;a id="" href="https://github.com/NordicSemiconductor/Android-BLE-Library"&gt;https://github.com/NordicSemiconductor/Android-BLE-Library&lt;/a&gt;&amp;nbsp;and&amp;nbsp;&lt;a id="" href="https://github.com/NordicSemiconductor/Android-DFU-Library"&gt;https://github.com/NordicSemiconductor/Android-DFU-Library&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Galaxy Tab A8 fails to connect properly, while Galaxy Phone S10 works fine</title><link>https://devzone.nordicsemi.com/thread/504982?ContentTypeID=1</link><pubDate>Fri, 04 Oct 2024 11:40:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:402a6055-03c3-4a2f-b247-13950b74b6df</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;In 2022, we found an issue in the Samsung A8 series Bluetooth capabilities, where it apparently tries to send packets with longer payloads than what has been negotiated, which caused these issues to occur. It has been reported to Samsung, but I do not have a status beyond that I&amp;#39;m afraid. There is nothing to be done from the nRF side of the application to remedy this I&amp;#39;m afraid.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Galaxy Tab A8 fails to connect properly, while Galaxy Phone S10 works fine</title><link>https://devzone.nordicsemi.com/thread/504938?ContentTypeID=1</link><pubDate>Fri, 04 Oct 2024 07:48:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7fcb9da9-fb37-4b48-b53e-8197967777bf</guid><dc:creator>tellg</dc:creator><description>&lt;p&gt;&lt;span&gt;Another capture from the A8, this time using the nRFConnect Device Manager app to try to perform a OTA DFU.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Firmware is this time the smp_svr example running on nRF52840dk , ncs 2.6.1&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/samsungA8_5F00_nrfConnect_5F00_Device_5F00_Manager_5F00_smp_5F00_svr_5F00_example_5F00_nRF52840dk.pcapng"&gt;devzone.nordicsemi.com/.../samsungA8_5F00_nrfConnect_5F00_Device_5F00_Manager_5F00_smp_5F00_svr_5F00_example_5F00_nRF52840dk.pcapng&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Also on this capture we see a burst of &amp;quot;Central_0x0b3c1c55 Peripheral_0x0b3c1c55 ATT 37 Sent Read By Group Type Request, Primary Service, Handles: 0x0001..0xffff&amp;quot;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Details of Galaxy Tab 8:&amp;nbsp;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/Screenshot_5F00_20241004_5F00_100121_5F00_nRF-Connect.jpg" /&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Galaxy Tab A8 fails to connect properly, while Galaxy Phone S10 works fine</title><link>https://devzone.nordicsemi.com/thread/504931?ContentTypeID=1</link><pubDate>Fri, 04 Oct 2024 07:13:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:49e200fe-320c-4abb-a346-d8e42153f6b8</guid><dc:creator>tellg</dc:creator><description>&lt;p&gt;Another capture from the A8, this time using the nRFConnect Device Manager app to try to perform a OTA DFU&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/samsungA8_5F00_nrfConnect_5F00_Device_5F00_Manager.pcapng"&gt;devzone.nordicsemi.com/.../samsungA8_5F00_nrfConnect_5F00_Device_5F00_Manager.pcapng&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Galaxy Tab A8 fails to connect properly, while Galaxy Phone S10 works fine</title><link>https://devzone.nordicsemi.com/thread/504929?ContentTypeID=1</link><pubDate>Fri, 04 Oct 2024 07:03:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:89fbeed2-b9d1-439a-a97c-1d8dc752835a</guid><dc:creator>bearsh</dc:creator><description>&lt;p&gt;As it also affects me, I did also capture the communication&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/nordic_2D00_sdk_2D00_2.6.1_5F00_samsung_2D00_SM_2D00_X200.pcapng.gz"&gt;devzone.nordicsemi.com/.../nordic_2D00_sdk_2D00_2.6.1_5F00_samsung_2D00_SM_2D00_X200.pcapng.gz&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>