Take our customer survey to evaluate your visit.
It should only take a few minutes to answer five quick questions. Just click the Launch survey button at the end of your visit to begin.
Sony Mobile Communications
It should only take a few minutes to answer five quick questions. Just click the Launch survey button at the end of your visit to begin.
2017-03-27 05:01 AM - edited 2017-10-12 03:18 PM
2017-03-27 05:01 AM - edited 2017-10-12 03:18 PM
UPDATED: 12OCT2017
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.
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 on the Z5C for a rebuild of the TWRP Recovery.
Adios.
CVE-2017-0781 to 0785
edit wow... i been out of action for a while... just looking at the last date there...
UPDATED: 20JULY2017
one of my devices stored the correct names, the other didn't
the (W)hite device had never been paired to the pc before, while my main Black device had been previously
http://i.imgur.com/xiVkZvu.jpg
http://i.imgur.com/xiVkZvum.jpg
http://i.imgur.com/avyWCNFm.jpg http://i.imgur.com/QnPkCmZm.jpg
Standard Users having Bluetooth Problems:
Root Users Having Bluetooth Problems:
____________
09 June 2017
Found the cause for some of the problems.
Shared Pref in User_De is missing pretty much all the configurations it needs.
____________
05 June 17
Included btopps database corruption examples - view last post
=========================================================
ORIGINAL POST
=========================================================
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.
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.
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.
I blame Google for a large part of this
2017-06-03 04:23 PM - edited 2017-06-12 06:10 AM
2017-06-03 04:23 PM - edited 2017-06-12 06:10 AM
I've figured it out - for File Transfer - the Android Bluettoth App doesn't have sufficient permissions to write to the device.
I'm assuming that these permissions where somehow lost during firmware updates.
I'm able to reproduce the bug, and either force a fail, or a successful transfer.
The other apps will have a similar issue regarding Bluetooth connectivity.
Now that I know what is causing it - I can start looking at where abouts in the code I should be looking.
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
(See first post for temporary solutions)
2017-03-28 04:12 PM
2017-03-28 04:12 PM
I have the same problem since the android update 7.
The battery no longer holds. In the settings the bluetooth consumes 55% of the battery, before updating about 5%.
I did not change anything in my use.
2017-03-30 11:15 PM - edited 2017-04-01 07:30 PM
2017-03-30 11:15 PM - edited 2017-04-01 07:30 PM
EDIT: 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
2017-04-01 07:32 PM - edited 2017-04-01 08:50 PM
2017-04-01 07:32 PM - edited 2017-04-01 08:50 PM
Nope.... who's stupid idea was it to lock out Bluetooth app File Receive Folder? Sony or Google?
There's not even an easy way to access Outbound and Inbound transfers... zzzzzzzzzzzzzzzzzzzzzzzzzzzz
You only need one bad connection and it starts a chain reaction where RFCOMM starts being stupid.
com.android.bluetooth means a Google Problem right? Not Sony? or both?
To fix things, everyday users need access to: rootfs: /data/user_de/com.android.bluetooth
Which they won't have... because they don't have sufficient privileges.
Cache clearing every error isn't really going to be super effective because it's slow.... and restart is needed.
2017-05-31 12:48 AM
2017-05-31 12:48 AM
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.
2017-06-02 06:50 AM - edited 2017-06-02 07:11 AM
2017-06-02 06:50 AM - edited 2017-06-02 07:11 AM
Hello,
I think I found the reason why some bluetooth activity is failing,
Bluetooth share is missing
<uses-permission android:name="android.permission.BLUETOOTH_ADMIN" />
But, I think there are some other issues regarding Bluetooth LE - because of the package upgrade from Lollipop to Marshmallow to Nougat.
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.
I'm going to post something at the Xperia Github to discuss
Nope, this isn't it, I just found where the permissions are hiding.
2017-06-03 04:23 PM - edited 2017-06-12 06:10 AM
2017-06-03 04:23 PM - edited 2017-06-12 06:10 AM
I've figured it out - for File Transfer - the Android Bluettoth App doesn't have sufficient permissions to write to the device.
I'm assuming that these permissions where somehow lost during firmware updates.
I'm able to reproduce the bug, and either force a fail, or a successful transfer.
The other apps will have a similar issue regarding Bluetooth connectivity.
Now that I know what is causing it - I can start looking at where abouts in the code I should be looking.
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
(See first post for temporary solutions)
2017-06-05 01:48 PM - edited 2017-06-05 01:59 PM
2017-06-05 01:48 PM - edited 2017-06-05 01:59 PM
I've included some examples of how the database for com.android.bluetooth can become corrupted.
Any users reading this; this is not a Sony fault, but an Android fault, so blame Google.
I don't know who to contact on the Google end of things, but the whole Bluetooth section for Android is a mess.
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.
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.
The last data table for Bluetooth keeps track of the sequence - sqlite_sequence
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.
Because the Android Bluetooth app has those operations in it's queue; 34,35,36, it tries to resolve them.
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... .....
There's no way for any 3rd party app to fix this, because com.android.bluetooth is a System app.
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.
http://android.googlesource.com/platform/system/bt/
http://android.googlesource.com/platform/packages/apps/Bluetooth/
I don't even know which patches will be applied to the final firmware release for the Z5 family.
But I know that nothing has been done about the total lack of user administration for bluetooth, and that's just not good enough.
Any advice from the Sony team would be appreciated.
2017-06-06 05:41 PM
2017-06-06 05:41 PM
after submitting my video, i think i should have posted it here instead to be more accurate anyway.
2017-06-09 05:20 AM - edited 2017-06-09 11:18 AM
2017-06-09 05:20 AM - edited 2017-06-09 11:18 AM
@JAI0073 wrote:after submitting my video, i think i should have posted it here instead to be more accurate anyway.
hi,
yes, currently, there is a very big lag between when bluetooth turns on, and icon display, and when services are actually functional.
you can soft test "show received files".
when that no longer lags in displaying the page fragment for downloaded files, then bluetooth is ready to be used.
NB:____________
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