<?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>Setting MTU size through nRF connect mobile app not working properly with Samsung mobile</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/108007/setting-mtu-size-through-nrf-connect-mobile-app-not-working-properly-with-samsung-mobile</link><description>Hi, 
 I am working on a project with nRF52832 chipset(custom board). 
 When I am trying to set MTU size to 247 bytes with nRF connect mobile app, I am getting max_rx_octets &amp;amp; max_rx_octets size as 251 bytes in BLE_GAP_EVT_DATA_LENGTH_UPDATE event. 
 This</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 02 Feb 2024 05:40:26 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/108007/setting-mtu-size-through-nrf-connect-mobile-app-not-working-properly-with-samsung-mobile" /><item><title>RE: Setting MTU size through nRF connect mobile app not working properly with Samsung mobile</title><link>https://devzone.nordicsemi.com/thread/467285?ContentTypeID=1</link><pubDate>Fri, 02 Feb 2024 05:40:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a8eb72b1-f884-470a-a4d7-d39938f61073</guid><dc:creator>Torsten Robitzki</dc:creator><description>&lt;p&gt;The Bluetooth standard allows to have MTU sizes as low as 23, so 247 is already quite high. You can simply not rely on benign able to set the MTU size to higher values as 23. In practice, most phones implement GATT MTUs much higher than that, but you can not really rely on it.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>