Radio 1.18 Feedback

[nvatvani]

I have been seeing a lot of fragments in various threads that Radio 1.18 is "bad". I did not know if this was true or not so I tried it myself by upgrading to Laurentius' WM6PROBUSINESS update 3 http://forum.xda-developers.com/showthread.php?t=325466

My first test was the Bluetooth, and the official result (as far as I have been doing things) is that I manage to lock-up the entire OS 100% of the time out of 5 tries using the following procedure:
1. Pair your Headset with the Universal
2. Enable "Headset" and "Wireless Stereo" profiles
3. Play any music that is at least 1 minute long

Result = OS Freeze

To make the OS lockup immediately on queue, swap Steps 2 and 3 above. To be much more specific it is the "Wireless Stereo" profile that triggers the lock-up.

This has been my test so far and I am not going to bother with any further testing since I intend to downgrade to 1.17 immediately. But if you have other issues with Radio 1.18, I guess it would be helpful to all if you list a step-by-step procedure to break Radio 1.18.

[sl9]

I've been using 1.18 since the day it was "released", but unlike you I don't use WM6, in fact I'm still using the original WM5 ROM that came with my MDA PRO, which is at least 2 years old now. If it ain't broke, don't try to fix it! :)

No problems with this radio version at all. Some people have said 1.18 "drains the battery faster", but I have not noticed any significant difference after months of testing, although I do use a 3200mAH extended battery which lasts for 1+ week on a single charge ;)

So how do you know this bluetooth crash is a radio bug and not an OS ROM bug - have you tried an earlier radio like 1.17 or 1.15 and tried to reproduce the bug then?

[cktlcmd]

I've been using 1.18 since the day it was "released", but unlike you I don't use WM6, in fact I'm still using the original WM5 ROM that came with my MDA PRO, which is at least 2 years old now. If it ain't broke, don't try to fix it! :)

No problems with this radio version at all. Some people have said 1.18 "drains the battery faster", but I have not noticed any significant difference after months of testing, although I do use a 3200mAH extended battery which lasts for 1+ week on a single charge ;)

So how do you know this bluetooth crash is a radio bug and not an OS ROM bug - have you tried an earlier radio like 1.17 or 1.15 and tried to reproduce the bug then?

Same here, no problems. :) I am using WM5 Kamal's Version.

---

[beast0898]

I have been seeing a lot of fragments in various threads that Radio 1.18 is "bad". I did not know if this was true or not so I tried it myself by upgrading to Laurentius' WM6PROBUSINESS update 3 http://forum.xda-developers.com/showthread.php?t=325466

My first test was the Bluetooth, and the official result (as far as I have been doing things) is that I manage to lock-up the entire OS 100% of the time out of 5 tries using the following procedure:
1. Pair your Headset with the Universal
2. Enable "Headset" and "Wireless Stereo" profiles
3. Play any music that is at least 1 minute long

Result = OS Freeze

To make the OS lockup immediately on queue, swap Steps 2 and 3 above. To be much more specific it is the "Wireless Stereo" profile that triggers the lock-up.

This has been my test so far and I am not going to bother with any further testing since I intend to downgrade to 1.17 immediately. But if you have other issues with Radio 1.18, I guess it would be helpful to all if you list a step-by-step procedure to break Radio 1.18.


Hi,

I have had no issues at all with 1.18 since before I released it.

To provide proper test results could you post back the results of the same procedure with 1.17.

Since I work with leo on the Roms we release, I can tell you now that A2DP is the issue you are reporting and not the radio stack, even with 1.17 I am 90% sure you device will appear to lock up. Actually it doesnt lockup it simply drops comms with the headset, if you press a button on the headset it will continue (though not for long) this is an issue with the BT Stack and A2DP implementation in the Rom.

Please post back your results with 1.17.


Thanks,

Cheers,


Beasty

[topgunarindam]

Hi,
Its working fine for me.

using laurentius26's WM6 rom.

though battery drain is perhaps bit more (nothing major), but then that can be attributed perhaps to WM6 OS as well.

cheers
AB

[nvatvani]

Hi,

I have had no issues at all with 1.18 since before I released it.

To provide proper test results could you post back the results of the same procedure with 1.17.

Since I work with leo on the Roms we release, I can tell you now that A2DP is the issue you are reporting and not the radio stack, even with 1.17 I am 90% sure you device will appear to lock up. Actually it doesnt lockup it simply drops comms with the headset, if you press a button on the headset it will continue (though not for long) this is an issue with the BT Stack and A2DP implementation in the Rom.

Please post back your results with 1.17.


Thanks,

Cheers,


Beasty

Am currently flashing down to Radio 1.17. The reason why I say it locks up is because the Universal is totally unresponsive to any Input - not even the backlight toggle, and the clock shows the same time.

Will keep you posted on the performance of 1.17.

------------------------------------------------
Edit:

You are correct, 1.17 performed exactly the same way as 1.18, and that it isn't actually a lock-up. It just looks like a lock-up but upon pressing the MFB on the Headset that triggers Voice Command, the device starts to tick again.

[suraj.tomer]

Using 1.18 since last month on wm6, facing no problem at all :)

[mamaich]

My first test was the Bluetooth, and the official result (as far as I have been doing things) is that I manage to lock-up the entire OS 100% of the time out of 5 tries using the following procedure:
1. Pair your Headset with the Universal
2. Enable "Headset" and "Wireless Stereo" profiles
3. Play any music that is at least 1 minute long

Result = OS Freeze

I don't see here any radio problems.

[topgunarindam]

battery drain might be due to WM6.....
and hanging/freeze also due to some ROM/WM6 issues.....

try a diff wm5 rom with 1.18 radio