• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Firmware update WLAN and BT for Nougat

Search This thread

GreyLeshy

Senior Member
Feb 1, 2017
489
634
Saint-Petersburg and Olonets
Firmware update WLAN / BT

FW for 32.3.A.0.372/376/378 and 32.3.A.2.33

WLAN: 7.45.59.15 (This firmware WLAN installed in 32.4.A.0.160)
BT: cfg121-0121 (BT 4.2)
Download: androidfilehost.com

--------------------------------------------------
FW for 32.3.A.0.372/376/378, 32.3.A.2.33, 32.4.A.0.160

WLAN: 7.45.59.16 (This firmware WLAN installed in 32.4.A.1.54)
BT: cfg121-0121 (BT 4.2)
Download: androidfilehost.com

WLAN: 7.45.59.17
BT: cfg121-0121 (BT 4.2)
Download: androidfilehost.com

WLAN: 7.45.59.18
BT: cfg121-0121 (BT 4.2)
Download: androidfilehost.com

To install use TWRP 3.1.1.
About changes to don't ask, don't know.​
 
Last edited:

NeoBeum

Senior Member
Feb 25, 2017
223
81
BT is still having issues I think. I've gotten side tracked with my device tree, and been looking at the broadcom c++,
I think googles framework and bt app need fixing
 

NeoBeum

Senior Member
Feb 25, 2017
223
81
Firmware update WLAN / BT
for FW 32.4.A.0.160

WLAN: 7.45.59.16 (Sony will add this driver in the next firmware.)
BT: cfg121-0121 (BT 4.2)

it's got some changes to how the Qualcomm stack, RFCOMM, talk to the Broadcom stuff for SDIO..

I asked about some other stuff on GitHub, but no one's replied yet.

at the moment I can see some conflicts with 'bt.name=Android', the dynamic naming to 'Xperia {Device Model}', and the name users can change in the bluetooth settings
 

GreyLeshy

Senior Member
Feb 1, 2017
489
634
Saint-Petersburg and Olonets
at the moment I can see some conflicts with 'bt.name=Android', the dynamic naming to 'Xperia {Device Model}', and the name users can change in the bluetooth settings

You have this conflict on stock FW cfg121-0121 BT 4.1?

The difference between the drivers is minimal and the main part is not affected.
BCM4345C0 Sony Kitakami R21 UART 37.4 MHz BT 4.1 cfg121-0121
BCM4345C0 Sony Loire UART 37.4 MHz BT 4.2 cfg121-0121
 

NeoBeum

Senior Member
Feb 25, 2017
223
81
its not really firmware related - but software - so the problem exists for almost every release - because either one of them wants to supercede or be in charge...
this is what i was trying to find out... who has final control.. there's 4 vendors involved... qcom, broadcom, sony, google... 5 if you include the user

i was just going through the kitakami bluetooth stuff - you'll probably see my post in github if you have a look


edit: the firmware itself looks solid (apart from the bit where i mentioned the dynamic naming - because there's the override/or not override with build.prop) - it's the google framework added on top of it - that is leading to my suspicions
just go have a look at the system/bt at googlesource - and you might see what i'm having doubts about
 
Last edited:

GreyLeshy

Senior Member
Feb 1, 2017
489
634
Saint-Petersburg and Olonets
its not really firmware related - but software - so the problem exists for almost every release - because either one of them wants to supercede or be in charge...
this is what i was trying to find out... who has final control.. there's 4 vendors involved... qcom, broadcom, sony, google... 5 if you include the user

i was just going through the kitakami bluetooth stuff - you'll probably see my post in github if you have a look

edit: the firmware itself looks solid (apart from the bit where i mentioned the dynamic naming - because there's the override/or not override with build.prop) - it's the google framework added on top of it - that is leading to my suspicions
just go have a look at the system/bt at googlesource - and you might see what i'm having doubts about

Post read, I will say a few words about the boot:
- kernel and ramdisk (initialization scripts)
- system/build.prop (medium priority)
- other scripts with higher priority, programs and drivers

In general, it is tedious, but the problem is most likely in the stack between broadcom and google.
To search for the culprit will have to study the source code...
 

Cerhio

Senior Member
Feb 25, 2013
206
29
Hey, quick question:

Should I stick with the firmware that came with my Rom or should I update to the latest version even if it's a different android version? I'm using Marshmallow and wonder if the Nougat update would do anything.
 

GreyLeshy

Senior Member
Feb 1, 2017
489
634
Saint-Petersburg and Olonets

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    Firmware update WLAN / BT

    FW for 32.3.A.0.372/376/378 and 32.3.A.2.33

    WLAN: 7.45.59.15 (This firmware WLAN installed in 32.4.A.0.160)
    BT: cfg121-0121 (BT 4.2)
    Download: androidfilehost.com

    --------------------------------------------------
    FW for 32.3.A.0.372/376/378, 32.3.A.2.33, 32.4.A.0.160

    WLAN: 7.45.59.16 (This firmware WLAN installed in 32.4.A.1.54)
    BT: cfg121-0121 (BT 4.2)
    Download: androidfilehost.com

    WLAN: 7.45.59.17
    BT: cfg121-0121 (BT 4.2)
    Download: androidfilehost.com

    WLAN: 7.45.59.18
    BT: cfg121-0121 (BT 4.2)
    Download: androidfilehost.com

    To install use TWRP 3.1.1.
    About changes to don't ask, don't know.​
    3
    Firmware update WLAN / BT for Nougat

    WLAN: 7.45.59.18 (r718509)
    BT: cfg121-0121 (BT 4.2)
    2
    Firmware update WLAN / BT for Nougat

    WLAN: 7.45.59.17
    BT: cfg121-0121 (BT 4.2)
    1
    Firmware update WLAN and BT for Nougat 7.1.1

    Firmware update WLAN / BT
    for FW 32.4.A.0.160

    WLAN: 7.45.59.16
    BT: cfg121-0121 (BT 4.2)

    Download: androidfilehost.com
    1
    Are these files newer than the ones on stock 32.4.A.1.54?

    Ah, they came from the Xperia X? That's a yes then, brilliant. I put the firmware folder in /data/adb/magisk_simple and I think it worked (but I don't know how to confirm that the new firmware was loaded!)

    Yes, newer. See description.

    View the wlan version: sys/module/wlan/parameters/info_string.
    pZ7YyNw.png