Android 4.4.3 support

[cimst]

I fear we have to live with the old radio, it's quite complicated to find a solution for this problem. Since it works with the old radio something must have changed inside the radio software. But how to find out? In the meantime I'm at least able to load this into IDA, but it's a 45 MB binary for an unknown CPU (at least for me)
The IDA database has more than 500 MB and IDA is slow as a snail and it seems it crashes frequently. Doesn't look good...

That is a bad announcement, if it is the final decision. So anyone who doesn't want to combine different parts from different builds will not be able to use it anymore?

[admin]

I did not yet give up
But currently I'm still clueless what I can do to fix it

[delicats]

Hi,

Unfortunately I uptated to 4.4.3 before seeing the warning.

So today I downgraded the radio as recommended. It works but now the phone drains heavily the battery... 40% battery after 7 hours with cell standby of 57% although I've been in the car for 3 hours.

Anybody with the same problem?

Cheers
Dirk

[Brian]

Hi Dirk,

I'm 8 hours on battery with 81% left with this particular setup...

What radio did you flash?

Brian

[delicats]

Hi Brian,

I took the

D820 KOT49E (4.4.1)
M8974A-1.0.25.0.23
AAAAANAZQ1025019
by QUALCOMM Incorporated Nov 19 2013

from

http://downloads.codefi.re/autoprime/LG/Nexus_5/Modems

I rebooted a couple of times, but it did not help. Interestingly the cell standby used power also during the time when I've been in the car and the phone radio was turned off (via rSAP). Looking at the curve in 'history details' shows that in the first 5 hours it consumed most (2/3) with medium signal strength (using LTE) and then with no signal (rSAP) and after a good signal (3G) another third.

Tomorrow I'll try if LTE does make the difference. But before I did not observe a very significant differnce while ideling...

Anyhow, all this does not help reg. the main problem. I googled a bit today at lunchtime and found that just in the AOSP part there were more than 7000 changes between 4.4.2 and 4.4.3. In addition all the undocumented chnages in the binaries...

Is there any further info on the error available? Even though the old radio fixes the issue, does the RIL of 4.4.3 not need to reflect the changes of there radio, if there is one regarding interface towards the RIL?

cheers

dirk

[bernstein]

In the beginnin 4.4.3 (4.4.2-radio) would drain my battery, too.
Overnight loss was 10-15%, with g-now turned off.
It has improved day by day, tonight: 5% loss, even with g-now turned on!

In the changelog are "several Bluetooth enhancements for stability" mentioned, i suppose those are our troublemaker!?

@ admin: If you need testers: please let us/me know.

[Mandulli]

I can confirm the problem. with the old baseband rasp works perfectly with the new not.

[delicats]

I agree, the power consumption of the phone seems to decrease...as if it is learning something.

But I found another side effect of 4.4.3 (in combination with the 4.4.1/2 radio at least):

My car phone does not recognize the nexus rsap all times. Out of may be ten tomes it happens 4 times. If it try manually to find it as rsap phone the car can not find it. Then either turning BT or rasap off and on again, followed by a manual search for the phone helps (Mercedes sap v4).

Cheers
Dirk

[cimst]

I did not yet give up
But currently I'm still clueless what I can do to fix it

There were only 20 commits for bluetooth, does the following link help?
https://android.googlesource.com/platfo ... /bluedroid

[bernstein]

These are the commits for android.
But as admin wrote, android 4.4.3 itself seems not to be the problem, the nexus 4 with 4.4.3. works as good as with 4.4.2. And the n5 on 4.4.3 with the old radio works, too.

The problem lies within the radio software that came bundled with 4.4.3 on the N5. And that is not open-source.