<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Bluetooth Android API Changes and Permissions causing port lockout and battery drain in Z Series</title>
    <link>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548957#M107880</link>
    <description>&lt;P&gt;I've included some examples of how the database for com.android.bluetooth can become corrupted.&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Any users reading this; this is not a Sony fault, but an Android fault, so blame Google.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;I don't know who to contact on the Google end of things, but the whole Bluetooth section for Android is a mess.&lt;/P&gt;&lt;P&gt;Because of how they decided to interface bluetooth on our devices, we don't have a proper management for the "App" and what we have available to us, isn't good enough to rectify the problem.&lt;/P&gt;&lt;P&gt;You won't be able to get Bluetooth working unless you override the security and clear the faults yourself, which no general domestic market user should be expected to have knowledge, or even have to.&lt;/P&gt;&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot_20170605-205012.png" style="width: 400px;"&gt;&lt;IMG src="https://community.sony.co.uk/legacyfs/online/37962i69B15048FF2E0A7E/image-size/medium?v=1.0&amp;amp;px=400" title="Screenshot_20170605-205012.png" alt="Screenshot_20170605-205012.png" /&gt;&lt;/SPAN&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot_20170605-205022.png" style="width: 400px;"&gt;&lt;IMG src="https://community.sony.co.uk/legacyfs/online/37961i9E0A08EC15F35C10/image-size/medium?v=1.0&amp;amp;px=400" title="Screenshot_20170605-205022.png" alt="Screenshot_20170605-205022.png" /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;The last data table for Bluetooth keeps track of the sequence - sqlite_sequence&lt;/P&gt;&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot_20170605-210938.png" style="width: 225px;"&gt;&lt;IMG src="https://community.sony.co.uk/legacyfs/online/37965i62521B80CFACD91D/image-size/medium?v=1.0&amp;amp;px=400" title="Screenshot_20170605-210938.png" alt="Screenshot_20170605-210938.png" /&gt;&lt;/SPAN&gt;&amp;nbsp; If the sequence doesn't match the final seuquence of what is in the main data table - this is where problems start happenening. I rectified mine to reflect the last working record, and deleted records 34,35,36.&lt;/P&gt;&lt;P&gt;Because the Android Bluetooth app has those operations in it's queue; 34,35,36, it tries to resolve them.&lt;/P&gt;&lt;P&gt;But, because it has no idea what to do, it just throws errors. The next time it loads up, it says... oh I have jobs, let's do them.. 34,35,36.... wait... **bleep** is this... oh crap... .....&lt;/P&gt;&lt;P&gt;There's no way for any 3rd party app to fix this, because com.android.bluetooth is a System app.&lt;/P&gt;&lt;P&gt;I could probably hack the build environment and push out a quick fix, but that is not an ideal option... because only Root Access users will be able to install the app, but I don't really see anything where Google has any decent changes to how Bluetooth works in their source server.&lt;/P&gt;&lt;P&gt;&lt;A href="http://android.googlesource.com/platform/system/bt/" target="_blank" rel="nofollow noopener noreferrer"&gt;http://android.googlesource.com/platform/system/bt/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://android.googlesource.com/platform/packages/apps/Bluetooth/" target="_blank" rel="nofollow noopener noreferrer"&gt;http://android.googlesource.com/platform/packages/apps/Bluetooth/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I don't even know which patches will be applied to the final firmware release for the Z5 family.&lt;/P&gt;&lt;P&gt;But I know that nothing has been done about the total lack of user administration for bluetooth, and that's just not good enough.&lt;/P&gt;&lt;P&gt;Any advice from the Sony team would be appreciated.&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jun 2017 11:48:15 GMT</pubDate>
    <dc:creator>NeoBeum</dc:creator>
    <dc:date>2017-06-05T11:48:15Z</dc:date>
    <item>
      <title>Temp Fix Bluetooth Connectivity  (File TX, Tether, Stream): Vulnerability found CVE-2017-0781 -0785</title>
      <link>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548950#M107873</link>
      <description>&lt;P&gt;&lt;FONT size="6"&gt;&lt;STRONG&gt;&lt;FONT color="#FF0000"&gt;UPDATED: 12OCT2017&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;&lt;FONT size="4"&gt;I'm sure google will change things again if they haven't already. But if the latest patch 32.4.A.1.54 did not include the Bluetooth Security Patches - there will be another change to the BT API no doubt.&lt;/FONT&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;&lt;FONT size="4"&gt;There's a security Vulnerability to do with Bluetooth discovered in Sept. It's probably the junk I ran in to ... anyhoo... I'm busy compiling the new changes for 32.4.A.1.54&amp;nbsp; on the Z5C for a rebuild of the TWRP Recovery.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;&lt;FONT size="4"&gt;Adios.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;&lt;FONT size="4"&gt;&lt;FONT color="#FF0000"&gt;CVE-2017-0781&lt;/FONT&gt; to&lt;FONT color="#FF0000"&gt; 0785&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;&lt;FONT size="4"&gt;edit wow... i been out of action for a while... just looking at the last date there...&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;DIV class="lia-spoiler-container"&gt;&lt;A class="lia-spoiler-link" href="#" rel="nofollow noopener noreferrer"&gt;Spoiler&lt;/A&gt;&lt;NOSCRIPT&gt; (Highlight to read)&lt;/NOSCRIPT&gt;&lt;DIV class="lia-spoiler-border"&gt;&lt;DIV class="lia-spoiler-content"&gt;trolling microsoft by shrinking windows 10 pro, home and education on to 1 dvd and down to 3.9GB and posting screenshots on the MSDN forums hurrrrrr hueheu&lt;BR /&gt;&lt;DIV class="lia-spoiler-container"&gt;&lt;A class="lia-spoiler-link" href="#" rel="nofollow noopener noreferrer"&gt;Spoiler&lt;/A&gt;&lt;NOSCRIPT&gt; (Highlight to read)&lt;/NOSCRIPT&gt;&lt;DIV class="lia-spoiler-border"&gt;&lt;DIV class="lia-spoiler-content"&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="lelele.PNG" style="width: 400px;"&gt;&lt;IMG src="https://community.sony.co.uk/legacyfs/online/41593i8C0360FCCB5081B4/image-size/medium?v=1.0&amp;amp;px=400" title="lelele.PNG" alt="lelele.PNG" /&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;NOSCRIPT&gt;&lt;DIV class="lia-spoiler-noscript-container"&gt;&lt;DIV class="lia-spoiler-noscript-content"&gt;trolling microsoft by shrinking windows 10 pro, home and education on to 1 dvd and down to 3.9GB and posting screenshots on the MSDN forums hurrrrrr hueheu&lt;/DIV&gt;&lt;/DIV&gt;&lt;/NOSCRIPT&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&lt;FONT size="6"&gt;&lt;STRONG&gt;&lt;FONT color="#FF0000"&gt;UPDATED: 20JULY2017&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;DIV class="lia-spoiler-container"&gt;&lt;A class="lia-spoiler-link" href="#" rel="nofollow noopener noreferrer"&gt;Spoiler&lt;/A&gt;&lt;NOSCRIPT&gt; (Highlight to read)&lt;/NOSCRIPT&gt;&lt;DIV class="lia-spoiler-border"&gt;&lt;DIV class="lia-spoiler-content"&gt;&lt;P&gt;one of my devices stored the correct names, the other didn't&lt;BR /&gt;the (W)hite device had never been paired to the pc before, while my main Black device had been previously&lt;/P&gt;&lt;P&gt;&lt;A href="http://i.imgur.com/xiVkZvu.jpg" target="_blank" rel="nofollow noopener noreferrer"&gt;http://i.imgur.com/xiVkZvu.jpg&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://i.imgur.com/xiVkZvum.jpg" target="_blank" rel="nofollow noopener noreferrer"&gt;http://i.imgur.com/xiVkZvum.jpg&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;A href="http://i.imgur.com/avyWCNFm.jpg" target="_blank" rel="nofollow noopener noreferrer"&gt;http://i.imgur.com/avyWCNFm.jpg&lt;/A&gt; &lt;A href="http://i.imgur.com/QnPkCmZm.jpg" target="_blank" rel="nofollow noopener noreferrer"&gt;http://i.imgur.com/QnPkCmZm.jpg&lt;/A&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;NOSCRIPT&gt;&lt;DIV class="lia-spoiler-noscript-container"&gt;&lt;DIV class="lia-spoiler-noscript-content"&gt;one of my devices stored the correct names, the other didn'tthe (W)hite device had never been paired to the pc before, while my main Black device had been previouslyhttp://i.imgur.com/xiVkZvu.jpghttp://i.imgur.com/xiVkZvum.jpghttp://i.imgur.com/avyWCNFm.jpg http://i.imgur.com/QnPkCmZm.jpg&lt;/DIV&gt;&lt;/DIV&gt;&lt;/NOSCRIPT&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&lt;FONT color="#3366FF"&gt;Standard Users having Bluetooth Problems:&lt;/FONT&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Remove All Paired Devices: Done via Bluetooth Settings Menu Page.&lt;/LI&gt;&lt;LI&gt;Clear Android Bluetooth Data: Done via Apps Menu in Main Settings:&lt;BR /&gt;- Settings &amp;gt;&amp;gt; Apps &amp;gt;&amp;gt; Vertical Triple Dot Menu and "Show System"&lt;BR /&gt;- Find "Bluetooth Share" and select "Storage"&lt;BR /&gt;- "Clear Data" and "Clear Cache"&lt;/LI&gt;&lt;LI&gt;Turn Off Bluetooth.&lt;/LI&gt;&lt;LI&gt;Reboot Device with Cache Clear: Done by pressing "Power Button" and "Volume Up" until Device display turns off and device vibrates once.&lt;/LI&gt;&lt;LI&gt;Turn on device.&lt;/LI&gt;&lt;LI&gt;Reset Bluetooth Notifications: Done by accessing Bluetooth Share in Apps Menu&lt;BR /&gt;- Settings &amp;gt;&amp;gt; Apps &amp;gt;&amp;gt; Vertical Triple Dot Menu and "Show System"&lt;BR /&gt;- Go to "Notifications"&lt;BR /&gt;- Toggle all settings again, by turning it off and then back to the setting desired&lt;BR /&gt;- Ensure "On the lock screen remains as "Show all notification content" &amp;amp; "Interupts in Priority Only" is left on for next test.&lt;/LI&gt;&lt;LI&gt;Before pairing new devices, launch the Bluetooth App Menu, and turn on Bluetooth.&lt;/LI&gt;&lt;LI&gt;Wait in the Bluetooth Menu Page, and select the Vertical Triple Dot Menu and select "Show Received Files"&lt;BR /&gt;- &lt;FONT color="#FF0000"&gt;If the "Show Received Files" page does not appear immediately, do not attempt to load other applications. If you are using a 3rd party "Home" launcher app, temporarily go back to the Sony Default Home App.&lt;BR /&gt;&lt;/FONT&gt;- At the "Show Received Files" - if there are any files here, clear all by long press and clear.&lt;BR /&gt;&lt;BR /&gt;&lt;U&gt;&lt;FONT size="5" color="#FF0000"&gt;IF THERE WAS A DELAY FOR "SHOW RECEIVED FILES", WAIT UNTIL THERE IS NO DELAY WHEN LAUNCHING OR REPEAT STEP 1 TO 8&lt;BR /&gt;&lt;BR /&gt;DO NOT REPEATEDLY SELECT "SHOW RECEIVED FILES" AS THIS WILL CAUSE A BACKLOG OF PAGES TO APPEAR&lt;BR /&gt;&lt;BR /&gt;ONLY ONCE SELECT ONCE, AND WAIT OR REPEAT STEP 1 TO 8&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot_20170612-140801.png" style="width: 225px;"&gt;&lt;IMG src="https://community.sony.co.uk/legacyfs/online/38143i30C53A8767B7E27E/image-size/medium?v=1.0&amp;amp;px=400" title="Screenshot_20170612-140801.png" alt="Screenshot_20170612-140801.png" /&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/FONT&gt;&lt;/U&gt;&lt;/LI&gt;&lt;LI&gt;Pair a computer or another device capable of file transfer.&lt;BR /&gt;- Ensure pairing code matches &amp;amp; that both devices display a successful pairing.&lt;/LI&gt;&lt;LI&gt;Use Android Storage to access files: Done via Settings Menu &amp;gt;&amp;gt; Storage&lt;BR /&gt;Select a file for transfer with your problem device set to receive the file:&lt;BR /&gt;- Use Bluetooth Share via the "Share" Icon from the Storage app.&lt;BR /&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot_20170612-140627.png" style="width: 225px;"&gt;&lt;IMG src="https://community.sony.co.uk/legacyfs/online/38137i70C1594471713326/image-size/medium?v=1.0&amp;amp;px=400" title="Screenshot_20170612-140627.png" alt="Screenshot_20170612-140627.png" /&gt;&lt;/SPAN&gt;&amp;nbsp; &lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot_20170612-135552.png" style="width: 225px;"&gt;&lt;IMG src="https://community.sony.co.uk/legacyfs/online/38136iA57E8A10C1D6393B/image-size/medium?v=1.0&amp;amp;px=400" title="Screenshot_20170612-135552.png" alt="Screenshot_20170612-135552.png" /&gt;&lt;/SPAN&gt; &amp;nbsp;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot_20170612-141127.png" style="width: 225px;"&gt;&lt;IMG src="https://community.sony.co.uk/legacyfs/online/38142iD348C41FB592F326/image-size/medium?v=1.0&amp;amp;px=400" title="Screenshot_20170612-141127.png" alt="Screenshot_20170612-141127.png" /&gt;&lt;/SPAN&gt;&lt;BR /&gt;- Test using a capture taken by the device, but make sure the image file extension is LOWER CASE: &amp;lt;filename&amp;gt;.jpg &amp;lt;filename&amp;gt;.jpeg&amp;nbsp;&amp;lt;filename&amp;gt;.png&lt;BR /&gt;- Test using a text file: ensure that extension is not &amp;lt;filename&amp;gt;.TXT but lower case.&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="5" color="#FF0000"&gt;A POPUP DIALOG SHOULD APPEAR TO ACCEPT ANY FILE TRANSFER.&lt;BR /&gt;IF IT DOES NOT: REPEAT STEP 8&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;Test transfer with Sending files from the problem device.&lt;BR /&gt;If a file transfer encounters a problem, select the notification from the Notification bar, and repeat the process for "Outbound transfer" menu page - (Step 8 Received File Page)&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot_20170612-140941.png" style="width: 225px;"&gt;&lt;IMG src="https://community.sony.co.uk/legacyfs/online/38141i6B061DABE0C496BC/image-size/medium?v=1.0&amp;amp;px=400" title="Screenshot_20170612-140941.png" alt="Screenshot_20170612-140941.png" /&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Before Proceeding with Other Bluetooth Connectivity: Ensure that "Outbound Transfer" and "Bluetooth Received" pages are clear.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot_20170612-140924.png" style="width: 225px;"&gt;&lt;IMG src="https://community.sony.co.uk/legacyfs/online/38139i1211D4BE81B08DD4/image-size/medium?v=1.0&amp;amp;px=400" title="Screenshot_20170612-140924.png" alt="Screenshot_20170612-140924.png" /&gt;&lt;/SPAN&gt;&amp;nbsp; &lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot_20170612-140807.png" style="width: 225px;"&gt;&lt;IMG src="https://community.sony.co.uk/legacyfs/online/38140i8E9AF90B17BC2E17/image-size/medium?v=1.0&amp;amp;px=400" title="Screenshot_20170612-140807.png" alt="Screenshot_20170612-140807.png" /&gt;&lt;/SPAN&gt;&amp;nbsp; &lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot_20170612aaa-140924.jpg" style="width: 225px;"&gt;&lt;IMG src="https://community.sony.co.uk/legacyfs/online/38144i5F0E5A500250B106/image-size/medium?v=1.0&amp;amp;px=400" title="Screenshot_20170612aaa-140924.jpg" alt="Screenshot_20170612aaa-140924.jpg" /&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;FONT color="#FF0000"&gt;ACCESSING THESE PAGES SHOULD BE ALMOST INSTANTANEOUS, IF THERE IS A DELAY, THEN REPEAT THE CACHE CLEAR OR WAIT UNTIL THERE IS NO DELAY&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;Pair audio device.&lt;BR /&gt;- Test pairing with music stream.&lt;/LI&gt;&lt;/OL&gt;&lt;UL&gt;&lt;LI&gt;&amp;nbsp; OPTIONAL:&lt;BR /&gt;Test with Bluetooth Tether&lt;BR /&gt;Test with Mirror Link, Miracast, or other Bluetooth services (3rd Party Apps)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;FONT color="#339966"&gt;Root Users Having Bluetooth Problems:&lt;/FONT&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Clear Dalvik and ART Cache. Reboot using Power + Volume Up. Clear Cache in Recovery.&lt;/LI&gt;&lt;LI&gt;Repeat Process Above&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;____________&lt;/P&gt;&lt;P&gt;09 June 2017&lt;/P&gt;&lt;P&gt;Found the cause for some of the problems.&lt;/P&gt;&lt;P&gt;Shared Pref in User_De is missing pretty much all the configurations it needs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;____________&lt;/P&gt;&lt;P&gt;05 June 17&lt;/P&gt;&lt;P&gt;Included btopps database corruption examples - view last post&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.sony.co.uk/t5/Xperia-Z5-Z5-Compact-Z5-Premium/Bluetooth-Android-API-Changes-and-Permissions-causing-port/m-p/1228964#M36564" target="_blank"&gt;/t5/Xperia-Z5-Z5-Compact-Z5-Premium/Bluetooth-Android-API-Changes-and-Permissions-causing-port/m-p/1228964#M36564&lt;/A&gt;&lt;/P&gt;&lt;P&gt;=========================================================&lt;/P&gt;&lt;P&gt;ORIGINAL POST&lt;/P&gt;&lt;P&gt;=========================================================&lt;/P&gt;&lt;P&gt;I've been doing some trawling through my log, as I've finally been able to recreate the Nougat issues on my phone that everyone else seems to have that I didn't.&lt;BR /&gt;&lt;BR /&gt;From what I read ( could have misunderstood) the bluetooth and wireless api have had changes from Google to do with security. The result of this means that older hardware does not send the device sufficient parameters for a handshake or data transfer.&lt;BR /&gt;&lt;BR /&gt;Older written apps will cause the system to check for things that it won't find because of permissions, so it loops causing battery drain.&lt;BR /&gt;&lt;BR /&gt;I blame Google for a large part of this&lt;/P&gt;</description>
      <pubDate>Mon, 27 Mar 2017 03:01:37 GMT</pubDate>
      <guid>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548950#M107873</guid>
      <dc:creator>NeoBeum</dc:creator>
      <dc:date>2017-03-27T03:01:37Z</dc:date>
    </item>
    <item>
      <title>Re: Bluetooth Android API Changes and Permissions causing port lockout and battery drain</title>
      <link>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548951#M107874</link>
      <description>&lt;P&gt;I have the same problem since the android update 7.&lt;BR /&gt;The battery no longer holds. In the settings the bluetooth consumes 55% of the battery, before updating about 5%.&lt;BR /&gt;I did not change anything in my use.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Mar 2017 14:12:21 GMT</pubDate>
      <guid>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548951#M107874</guid>
      <dc:creator>serac01</dc:creator>
      <dc:date>2017-03-28T14:12:21Z</dc:date>
    </item>
    <item>
      <title>Re: Bluetooth Android API Changes and Permissions causing port lockout and battery drain</title>
      <link>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548952#M107875</link>
      <description>&lt;P&gt;EDIT: &lt;STRIKE&gt;I think the 32.3.A.2.33 update may have fixed the Bluetooth issues... I'm going to flash back to 32.3.A.0.376 and just check, I might extract the APK and check that way too&lt;/STRIKE&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2017 21:15:29 GMT</pubDate>
      <guid>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548952#M107875</guid>
      <dc:creator>NeoBeum</dc:creator>
      <dc:date>2017-03-30T21:15:29Z</dc:date>
    </item>
    <item>
      <title>Re: Bluetooth Android API Changes and Permissions causing port lockout and battery drain</title>
      <link>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548953#M107876</link>
      <description>&lt;P&gt;Nope.... who's stupid idea was it to lock out Bluetooth app File Receive Folder? Sony or Google?&lt;BR /&gt;&lt;BR /&gt;There's not even an easy way to access Outbound and Inbound transfers... zzzzzzzzzzzzzzzzzzzzzzzzzzzz&lt;BR /&gt;&lt;BR /&gt;You only need one bad connection and it starts a chain reaction where RFCOMM starts being stupid.&lt;BR /&gt;&lt;BR /&gt;com.android.bluetooth means a Google Problem right? Not Sony? or both?&lt;/P&gt;&lt;P&gt;To fix things, everyday users need access to:&amp;nbsp; rootfs:&amp;nbsp; /data/user_de/com.android.bluetooth&lt;/P&gt;&lt;P&gt;Which they won't have... because they don't have sufficient privileges.&lt;/P&gt;&lt;P&gt;Cache clearing every error isn't really going to be super effective because it's slow.... and restart is needed.&lt;/P&gt;</description>
      <pubDate>Sat, 01 Apr 2017 17:32:10 GMT</pubDate>
      <guid>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548953#M107876</guid>
      <dc:creator>NeoBeum</dc:creator>
      <dc:date>2017-04-01T17:32:10Z</dc:date>
    </item>
    <item>
      <title>Re: Bluetooth Android API Changes and Permissions causing port lockout and battery drain</title>
      <link>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548954#M107877</link>
      <description>&lt;P&gt;The deeper I get in to the Android Repo and start looking at language I understand, the more I dislike Android... Google still haven't released a fix because it will break security for other subsystems.&lt;/P&gt;</description>
      <pubDate>Tue, 30 May 2017 22:48:57 GMT</pubDate>
      <guid>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548954#M107877</guid>
      <dc:creator>NeoBeum</dc:creator>
      <dc:date>2017-05-30T22:48:57Z</dc:date>
    </item>
    <item>
      <title>Re: Bluetooth Android API Changes and Permissions causing port lockout and battery drain</title>
      <link>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548955#M107878</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;I think I found the reason why some bluetooth activity is failing,&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;&amp;nbsp;&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;Bluetooth share is missing&lt;/STRIKE&gt;&lt;/P&gt;&lt;PRE&gt;&lt;STRIKE&gt;&lt;SPAN class="tag"&gt;&amp;lt;uses-permission&lt;/SPAN&gt; &lt;SPAN class="atn"&gt;android:name&lt;/SPAN&gt;&lt;SPAN class="pun"&gt;=&lt;/SPAN&gt;&lt;SPAN class="atv"&gt;"android.permission.BLUETOOTH_ADMIN"&lt;/SPAN&gt; &lt;SPAN class="tag"&gt;/&amp;gt;&lt;/SPAN&gt;&lt;SPAN class="pln"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/STRIKE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;STRIKE&gt;&amp;nbsp;&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;&amp;nbsp;But, I think there are some other issues regarding Bluetooth LE - because of the package upgrade from Lollipop to Marshmallow to Nougat.&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;It has BLUETOOTH_PRIVILEGED, but I can't see it using or calling any functions from it, and I think Bluetooth share tries to access everything directly, which needs Admin.&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;&amp;nbsp;&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;I'm going to post something at the Xperia Github to discuss&lt;/P&gt;&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot_20170602-143542.png" style="width: 225px;"&gt;&lt;IMG src="https://community.sony.co.uk/legacyfs/online/37906i3F4F1DD4E037D1F2/image-size/medium?v=1.0&amp;amp;px=400" title="Screenshot_20170602-143542.png" alt="Screenshot_20170602-143542.png" /&gt;&lt;/SPAN&gt;&amp;nbsp; &lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot_20170602-143550.png" style="width: 225px;"&gt;&lt;IMG src="https://community.sony.co.uk/legacyfs/online/37907iA3508EAA630A0857/image-size/medium?v=1.0&amp;amp;px=400" title="Screenshot_20170602-143550.png" alt="Screenshot_20170602-143550.png" /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Nope, this isn't it, I just found where the permissions are hiding.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Jun 2017 04:50:50 GMT</pubDate>
      <guid>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548955#M107878</guid>
      <dc:creator>NeoBeum</dc:creator>
      <dc:date>2017-06-02T04:50:50Z</dc:date>
    </item>
    <item>
      <title>Re: Bluetooth Android API Changes and Permissions causing port lockout and battery drain</title>
      <link>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548956#M107879</link>
      <description>&lt;P&gt;&lt;STRIKE&gt;I've figured it out - for File Transfer - the Android Bluettoth App doesn't have sufficient permissions to write to the device.&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;I'm assuming that these permissions where somehow lost during firmware updates.&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;I'm able to reproduce the bug, and either force a fail, or a successful transfer.&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;&amp;nbsp;&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;The other apps will have a similar issue regarding Bluetooth connectivity.&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;&amp;nbsp;&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;&lt;STRIKE&gt;Now that I know what is causing it - I can start looking at where abouts in the code I should be looking.&lt;/STRIKE&gt;&lt;/P&gt;&lt;P&gt;It's more than likely due to a database corruption with during upgrades with Nougat and Marshmallow using Android Runtime, and with Lollipop optimised dexopt&lt;BR /&gt;&lt;FONT color="#FF0000" face="comic sans ms,sans-serif" size="7"&gt;(See first post for temporary solutions)&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jun 2017 14:23:55 GMT</pubDate>
      <guid>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548956#M107879</guid>
      <dc:creator>NeoBeum</dc:creator>
      <dc:date>2017-06-03T14:23:55Z</dc:date>
    </item>
    <item>
      <title>Re: Bluetooth Android API Changes and Permissions causing port lockout and battery drain</title>
      <link>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548957#M107880</link>
      <description>&lt;P&gt;I've included some examples of how the database for com.android.bluetooth can become corrupted.&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Any users reading this; this is not a Sony fault, but an Android fault, so blame Google.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;I don't know who to contact on the Google end of things, but the whole Bluetooth section for Android is a mess.&lt;/P&gt;&lt;P&gt;Because of how they decided to interface bluetooth on our devices, we don't have a proper management for the "App" and what we have available to us, isn't good enough to rectify the problem.&lt;/P&gt;&lt;P&gt;You won't be able to get Bluetooth working unless you override the security and clear the faults yourself, which no general domestic market user should be expected to have knowledge, or even have to.&lt;/P&gt;&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot_20170605-205012.png" style="width: 400px;"&gt;&lt;IMG src="https://community.sony.co.uk/legacyfs/online/37962i69B15048FF2E0A7E/image-size/medium?v=1.0&amp;amp;px=400" title="Screenshot_20170605-205012.png" alt="Screenshot_20170605-205012.png" /&gt;&lt;/SPAN&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot_20170605-205022.png" style="width: 400px;"&gt;&lt;IMG src="https://community.sony.co.uk/legacyfs/online/37961i9E0A08EC15F35C10/image-size/medium?v=1.0&amp;amp;px=400" title="Screenshot_20170605-205022.png" alt="Screenshot_20170605-205022.png" /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;The last data table for Bluetooth keeps track of the sequence - sqlite_sequence&lt;/P&gt;&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot_20170605-210938.png" style="width: 225px;"&gt;&lt;IMG src="https://community.sony.co.uk/legacyfs/online/37965i62521B80CFACD91D/image-size/medium?v=1.0&amp;amp;px=400" title="Screenshot_20170605-210938.png" alt="Screenshot_20170605-210938.png" /&gt;&lt;/SPAN&gt;&amp;nbsp; If the sequence doesn't match the final seuquence of what is in the main data table - this is where problems start happenening. I rectified mine to reflect the last working record, and deleted records 34,35,36.&lt;/P&gt;&lt;P&gt;Because the Android Bluetooth app has those operations in it's queue; 34,35,36, it tries to resolve them.&lt;/P&gt;&lt;P&gt;But, because it has no idea what to do, it just throws errors. The next time it loads up, it says... oh I have jobs, let's do them.. 34,35,36.... wait... **bleep** is this... oh crap... .....&lt;/P&gt;&lt;P&gt;There's no way for any 3rd party app to fix this, because com.android.bluetooth is a System app.&lt;/P&gt;&lt;P&gt;I could probably hack the build environment and push out a quick fix, but that is not an ideal option... because only Root Access users will be able to install the app, but I don't really see anything where Google has any decent changes to how Bluetooth works in their source server.&lt;/P&gt;&lt;P&gt;&lt;A href="http://android.googlesource.com/platform/system/bt/" target="_blank" rel="nofollow noopener noreferrer"&gt;http://android.googlesource.com/platform/system/bt/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://android.googlesource.com/platform/packages/apps/Bluetooth/" target="_blank" rel="nofollow noopener noreferrer"&gt;http://android.googlesource.com/platform/packages/apps/Bluetooth/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I don't even know which patches will be applied to the final firmware release for the Z5 family.&lt;/P&gt;&lt;P&gt;But I know that nothing has been done about the total lack of user administration for bluetooth, and that's just not good enough.&lt;/P&gt;&lt;P&gt;Any advice from the Sony team would be appreciated.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jun 2017 11:48:15 GMT</pubDate>
      <guid>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548957#M107880</guid>
      <dc:creator>NeoBeum</dc:creator>
      <dc:date>2017-06-05T11:48:15Z</dc:date>
    </item>
    <item>
      <title>Re: Bluetooth Android API Changes and Permissions causing port lockout and battery drain</title>
      <link>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548958#M107881</link>
      <description>&lt;P&gt;after submitting my video, i think i should have &lt;A title="post wrongly, correcting" href="https://community.sony.co.uk/t5/Xperia-XZ/Bluetooth-sharing-continously-stops-working-after-Nougat-7-0-OTA/m-p/1229285#M8405" target="_blank"&gt;posted it here instead&lt;/A&gt; to be more accurate anyway.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jun 2017 15:41:42 GMT</pubDate>
      <guid>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548958#M107881</guid>
      <dc:creator>JAI0073</dc:creator>
      <dc:date>2017-06-06T15:41:42Z</dc:date>
    </item>
    <item>
      <title>Re: Bluetooth Android API Changes and Permissions causing port lockout and battery drain</title>
      <link>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548959#M107882</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;A href="https://community.sony.co.uk/t5/user/viewprofilepage/user-id/150545"&gt;@JAI0073&lt;/A&gt; wrote:&lt;BR /&gt;&lt;P&gt;after submitting my video, i think i should have &lt;A title="post wrongly, correcting" href="https://community.sony.co.uk/t5/Xperia-XZ/Bluetooth-sharing-continously-stops-working-after-Nougat-7-0-OTA/m-p/1229285#M8405" target="_blank"&gt;posted it here instead&lt;/A&gt; to be more accurate anyway.&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;yes, currently, there is a very big lag between when bluetooth turns on, and icon display, and when services are actually functional.&lt;/P&gt;&lt;P&gt;you can soft test "show received files".&lt;/P&gt;&lt;P&gt;when that no longer lags in displaying the page fragment for downloaded files, then bluetooth is ready to be used.&lt;/P&gt;&lt;P&gt;NB:____________&lt;/P&gt;&lt;P&gt;I've factory reset my device and I'm currently diagnosing a working bluetooth framework so I can run a comparison when I force a corruption&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jun 2017 03:20:35 GMT</pubDate>
      <guid>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548959#M107882</guid>
      <dc:creator>NeoBeum</dc:creator>
      <dc:date>2017-06-09T03:20:35Z</dc:date>
    </item>
    <item>
      <title>Re: Bluetooth Android API Changes and Permissions causing port lockout and battery drain</title>
      <link>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548960#M107883</link>
      <description>&lt;P&gt;Bumpity Bump.&lt;/P&gt;&lt;P&gt;Found the cause for the problems. /data/user_de/0/com.android.bluetooth/shared_pref&lt;/P&gt;&lt;P&gt;is missing bluetooth profile configurations.&lt;/P&gt;&lt;P&gt;Now all I need to do is find where in the framework the code is and submit a patch to Sony or Google&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jun 2017 09:34:30 GMT</pubDate>
      <guid>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548960#M107883</guid>
      <dc:creator>NeoBeum</dc:creator>
      <dc:date>2017-06-09T09:34:30Z</dc:date>
    </item>
    <item>
      <title>Re: Bluetooth Android API Changes and Permissions causing port lockout and battery drain</title>
      <link>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548961#M107884</link>
      <description>&lt;P&gt;Bump to add temporary solution for Non-Root and Root Users&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jun 2017 03:48:40 GMT</pubDate>
      <guid>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548961#M107884</guid>
      <dc:creator>NeoBeum</dc:creator>
      <dc:date>2017-06-12T03:48:40Z</dc:date>
    </item>
    <item>
      <title>Re: Bluetooth Android API Changes and Permissions causing port lockout and battery drain</title>
      <link>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548962#M107885</link>
      <description>&lt;P&gt;There is a workaround, but you have to be sure not to turn off your bluetooth on your phone...or you will have to do the procedure again.&lt;/P&gt;&lt;P&gt;First, open smart connect app on your phone. you will find the bluetooth accessory in the list.&lt;/P&gt;&lt;P&gt;keep pressing on it, then remove.&lt;/P&gt;&lt;P&gt;Second, clear all your apps in memory (I use fast reboot app) then close all apps.&lt;/P&gt;&lt;P&gt;Third, open smart connect one more time, press on the plus to add accessory..this will open bluetooth settings...pair your device.&lt;/P&gt;&lt;P&gt;The accessory will work now....hopefully....until you turn off bluetooth....it will be corrupted...again. It works for me..(I use wireless headset pro mw1 and RM-X7bt car accessory).&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jul 2017 15:33:23 GMT</pubDate>
      <guid>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548962#M107885</guid>
      <dc:creator>Jimmy_121</dc:creator>
      <dc:date>2017-07-18T15:33:23Z</dc:date>
    </item>
    <item>
      <title>Re: Bluetooth Android API Changes and Permissions causing port lockout and battery drain</title>
      <link>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548963#M107886</link>
      <description>&lt;P&gt;this one's not really related but..&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;in Microsoft we trust&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://i.imgur.com/mMuBPZk.jpg" target="_self" rel="nofollow noopener noreferrer"&gt;http://i.imgur.com/mMuBPZk.jpg&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.sony.com.mk/0678cc50119719dd856fbab9040904a0d2d4763e/687474703a2f2f692e696d6775722e636f6d2f6d4d7542505a6b6d2e6a7067" border="0" /&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://i.imgur.com/gumtZVM.jpg" target="_self" rel="nofollow noopener noreferrer"&gt;http://i.imgur.com/gumtZVM.jpg&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.sony.com.mk/edc4c4813bac94ba24d32a67bd22232192cd7333/687474703a2f2f692e696d6775722e636f6d2f67756d745a564d6d2e6a7067" border="0" /&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://i.imgur.com/afwUuxB.jpg" target="_self" rel="nofollow noopener noreferrer"&gt;http://i.imgur.com/afwUuxB.jpg&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.sony.com.mk/976a5be2f5ce19bafa3b7777208b34e853e9dd8d/687474703a2f2f692e696d6775722e636f6d2f616677557578426d2e6a7067" border="0" /&gt;&lt;/P&gt;&lt;P&gt;...and asus... because laptop isnt made for Server 2016...&lt;/P&gt;&lt;P&gt;but at least bluetooth is working..... pfff&lt;/P&gt;&lt;P&gt;now there's another vendor to add to confusion... yay windows&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jul 2017 07:02:24 GMT</pubDate>
      <guid>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548963#M107886</guid>
      <dc:creator>NeoBeum</dc:creator>
      <dc:date>2017-07-19T07:02:24Z</dc:date>
    </item>
    <item>
      <title>Re: Bluetooth Android API Changes and Permissions causing port lockout and battery drain</title>
      <link>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548964#M107887</link>
      <description>&lt;P&gt;heres something interesting ...&lt;/P&gt;&lt;P&gt;one of my devices stored the correct names, the other didn't&lt;BR /&gt;the (W)hite device had never been paired to the pc before, while my main Black device had been previously&lt;/P&gt;&lt;P&gt;&lt;A href="http://i.imgur.com/xiVkZvu.jpg" target="_blank" rel="nofollow noopener noreferrer"&gt;http://i.imgur.com/xiVkZvu.jpg&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://i.imgur.com/xiVkZvum.jpg" target="_blank" rel="nofollow noopener noreferrer"&gt;http://i.imgur.com/xiVkZvum.jpg&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;A href="http://i.imgur.com/avyWCNFm.jpg" target="_blank" rel="nofollow noopener noreferrer"&gt;http://i.imgur.com/avyWCNFm.jpg&lt;/A&gt; &lt;A href="http://i.imgur.com/QnPkCmZm.jpg" target="_blank" rel="nofollow noopener noreferrer"&gt;http://i.imgur.com/QnPkCmZm.jpg&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 20 Jul 2017 01:49:46 GMT</pubDate>
      <guid>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548964#M107887</guid>
      <dc:creator>NeoBeum</dc:creator>
      <dc:date>2017-07-20T01:49:46Z</dc:date>
    </item>
    <item>
      <title>Re: Bluetooth Android API Changes and Permissions causing port lockout and battery drain</title>
      <link>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548965#M107888</link>
      <description>&lt;P&gt;&lt;FONT size="6"&gt;&lt;STRONG&gt;&lt;FONT color="#FF0000"&gt;UPDATED: 12OCT2017&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;&lt;FONT size="4"&gt;I'm sure google will change things again if they haven't already. But if the latest patch 32.4.A.1.54 did not include the Bluetooth Security Patches - there will be another change to the BT API no doubt.&lt;/FONT&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;&lt;FONT size="4"&gt;There's a security Vulnerability to do with Bluetooth discovered in Sept. It's probably the junk I ran in to ... anyhoo... I'm busy compiling the new changes for 32.4.A.1.54&amp;nbsp; on the Z5C for a rebuild of the TWRP Recovery.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;&lt;FONT size="4"&gt;Adios.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;&lt;FONT size="4"&gt;&lt;FONT color="#FF0000"&gt;CVE-2017-0781&lt;/FONT&gt; to&lt;FONT color="#FF0000"&gt; 0785&lt;/FONT&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 12 Oct 2017 13:01:14 GMT</pubDate>
      <guid>https://community.sony.com.mk/t5/z-series/temp-fix-bluetooth-connectivity-file-tx-tether-stream/m-p/3548965#M107888</guid>
      <dc:creator>NeoBeum</dc:creator>
      <dc:date>2017-10-12T13:01:14Z</dc:date>
    </item>
  </channel>
</rss>

