I have a O2 XDA IIs. I can't figure out what I did wrong. After the upgrade, no sounds comes thru speakerphone when I receive a call and call out. This happaned after I used the phone for like a half a day without soft reset. Once I soft reset the unit, it went back to normal. I tried going back to 1.02, but the problem remain.
Here is how I did the upgrade. I extract the xdaIIs_launchROM_v1.12.62_178; remove the files ms_.nbf, nk.nbf and radio_.nbf in the directory; downloaded the french 1.06.02; Put just that ROM into the directory. Start BaUpgradeUt and it indicates the old version and the new version and the upgrade went smoothly without any error.
I did the same thing to go back to 1.02. I tried install all my software from scratch without using the backup, but the problem remain.
I read thru most of the thread and saw there is a tool called xda3nbftool. Do I need to use this?
Appreciate anyone can help!!!!
That tool is only needed if you are trying to do none same carier upgrade.
Thus I would need it as to use the o2 rom on my T-mobile I would need to fix it with that tool and a fix.bat (wiki, getting started)
In your case you are doing a same carrier upgrade.
This should work out of the box (as in run the ship exe).
Most of us have done a radio only upgrade using the 1.06.02 FRA, and have not had any problems.
In your case I would reflash using the launch rom, try it out an you might have a hardware problem.
What I read that you did looks correct.
Only thing I am not sure is did you do a Hard reset after the install ?? But I am sure you did.
Your problem is not the upgrade, I had the same problem when I was using 1.02 radio rom and THAT'S WHY I upgraded to 1.06.02.. The problem seems to be random so far and there's no real fix as far as I know. Do a search, you're not alone with this problem...
I have that problem too when using 1.02, but after flashing to 1.06.02. This problem did still appear twice - I think this is the signal reception problem. You might try to notice that whether this happens always in the same area you are in.
Thanks for all the input. I did not have this problem before I tinker with the Radio ROM. So, I am thinking this may actually related to the ROM flash. I don't think it's related to reception since my provider coverage is very good. I am giving it another try and may ended up sending it in for repair. Having to soft reset every few hours is not fun.
Regards,
leochan2005 said:
I have that problem too when using 1.02, but after flashing to 1.06.02. This problem did still appear twice - I think this is the signal reception problem.
Click to expand...
Click to collapse
I also had this on 1.06.00 and 1.06.02 radio. After upgrading to 1.33 main ROM (from Siemens SX66) I have not noticed such problems. I've also noticed that you'll never have such a problem whan you have a bonded headset, even when headset is powered off.
mamaich said:
leochan2005 said:
I have that problem too when using 1.02, but after flashing to 1.06.02. This problem did still appear twice - I think this is the signal reception problem.
Click to expand...
Click to collapse
I also had this on 1.06.00 and 1.06.02 radio. After upgrading to 1.33 main ROM (from Siemens SX66) I have not noticed such problems. I've also noticed that you'll never have such a problem whan you have a bonded headset, even when headset is powered off.
Click to expand...
Click to collapse
mamaich, I think you are correct. I tried this yesterday by bonding my bluetooth headset which I did not do after the radio ROM upgrade. So far, the problem does not re-surface using the phone for more than 12 hours without soft resetting. What else does the 1.33 main ROM change?
that problem appear 4 times today. When a number get connected, time started counting, no we could not hear each other. Each time I need to soft reset.
Also, using Spite backup 3.14 to recover previous backup including mms and sms, mms cannot be received any more (I sent myself one), but sms ok.
My god! hard reset again....install everything again.
ok. some update. It happened again even I have the bonded blue tooth device. I notice however, if I go activate bluetooth and disable it, it comes back to normal without soft reset.
It seems no one can find out what is happening on the radio of XDAIIs
Related
Hi
I have the newest firmware version installed on my Qtek 9090 (BA_WWE_14000_147_11200_Ship), and I experience a problem again which I had first when I bought my Qtek but was gone after I had installed Radio version 1.08.00:
Once a day I have to reset my Qtek because I can't hear the one I am calling - usually this happens when I call my mobile phone's answer phone. The phone gets connected but I don't hear anything. After a soft reset everything is fine again.
Is this a known issue? Any solutions to it? Ok - I know I can downgrade to 1.08 again but I dont really wanna do that. And yes, I can stop calling my anser phone ....
Anyone knowing what is causing the problem?
Reagrds,
A
I had the same problem with my Qtek 9090 until I stopped use the Bluetooth feature completely. Since then, everything is fine.
tot 1.12 radio has solved the "no sound" issue.
keeping_sg said:
tot 1.12 radio has solved the "no sound" issue.
Click to expand...
Click to collapse
I cannot verify this, i have an mda3, upped it to R1.12 but i had many "no sound" problems. Now i downgraded to R1.10 and had not a single no sound issue ..yet
ThExSenatoR said:
keeping_sg said:
tot 1.12 radio has solved the "no sound" issue.
Click to expand...
Click to collapse
I cannot verify this, i have an mda3, upped it to R1.12 but i had many "no sound" problems. Now i downgraded to R1.10 and had not a single no sound issue ..yet
Click to expand...
Click to collapse
i have tried 1.06 & 1.10, all are having that issue. that's why i have upgraded to 1.12 so far so good. umm.....................strange..
keeping_sg said:
ThExSenatoR said:
keeping_sg said:
tot 1.12 radio has solved the "no sound" issue.
Click to expand...
Click to collapse
I cannot verify this, i have an mda3, upped it to R1.12 but i had many "no sound" problems. Now i downgraded to R1.10 and had not a single no sound issue ..yet
Click to expand...
Click to collapse
i have tried 1.06 & 1.10, all are having that issue. that's why i have upgraded to 1.12 so far so good. umm.....................strange..
Click to expand...
Click to collapse
For me, radio 1.12 delivered:
- worse signal reception
- higher battery consumption
- still no sound issue.
flashed twice & still having the bloody "no sound" issue. really give up. i think the next thing to change is the motherboard. sigh.........................
I had never had this issues untill I upgraded my Radio to 1.12 and then I had it 5 times in one day, went back to 1.10, no more issues
Hmm. This is a really 'odd' problem. I didn't originally have this problem with my SX66. Then, it just 'popped up' one day, and I can't seem to get rid of it.
I have tried different ROM versions (currently 1.40), and my radio version is at 1.10.
I have NEVER used radio 1.12, so I know that's not the CAUSE.
We need to compile a list of people with the problem, and see exactly what combination of ROM and Radio they have, as well as the programs they have installed.
if you read the cingular forums, there are a few folks there that say they have had it all along so I am not sure where to start...
umm....... different ppl have different problem. seems like it's a integration issue.
If you go to some HK forums, you will also find a lot of people suffering from this.
To me, I seldom use it as a phone. I only use it to receive emails and website browsing. When I go overseas and I used it as a phone with a BT handsfree (shut down GPRS connection), everything is just fine. I only encountered once with no sound problem when I take away my BT handsfree on a plane....
It's definitely a bug since a long time ago with old and new versions.....
Sad....and disappointed......
Hi all,
I upgraded my phone to the 1.12 radio along with the 1.40 CE ROM and am always resetting due to the "can't hear caller" issue and I never had this problem before.
I'm going to do a hard reset and see if that helps (clear out all the apps and use it for a day or so). If this doesn't work, I shall revert back to the 1.10 as I had no problems with that.
ROM 1.40.00
Radio 1.12.00
EXT ROM 1.13.139 (with Updated CallerID [1.20] and older version of O2 Active [3.0])
This cant hear caller issue, is it cant AT ALL hear caler or caller is so faint I cant hear him.
I ask as sometimes I get calls that are faint however when the caller rings back it fine. Not sure if its crap reseption or the device.
I got O2IIs from UK and had the same "No sound" problem. I have to SR about 5 times daily to sort it out. However, if I turn off Bluetooth (pairing with my Bluetrek G2) then everything's OK.
My ROM version is 1.31.00 WWE, Radio : 1.10.00, ExtROM: 1.31.139 WWE and BT 1.0.0 Build 3500
Had up to BT 3900 but wont help. Gonna up radio to 1.12. Will post the outcome soon.
I've only experience the problem once since the imate 1.40 upgrade.
Now, I must say that I don't use the phone THAT heavily.
I upgrade to 1.40 EX, it seems working fine, still the sound quality is not good enough...
people!
A guy called Derek has posted a possible solution to this problem here! http://forum.xda-developers.com/viewtopic.php?p=118364
It involves removing the Bluetooth for the startup because he believes that even with the bluetooth off, the unit is still trying to connect to a bluetooth headset.
I'm going to remove/unpair my Bluetooth Headset and see if that makes a difference. If anyone else can try this and post results I'm sure this would help loads of people.
Dom
Please confirm this and I will post it to wiki
@xdadom,
It's correct. As I mentioned in my post, when I "turned off" Bluetooth, everything's OK. The way I "turned off" Bluetooth is exactly the same with Derek did in his post, i.e. delete "Run_BTTrayCE" from Windows\StartUp\
However, I still need Bluetooth for my hand-free device. In my opinion, it's rather a trick, not a solution to kill "No sound" problem. Anyway, we can wait the updated BT version from supplier to sort it out.
The BA_DT_WWE_DutchRetail_14000_556_11300 has a new radio 1.13
I have converted this to a TYPE I file.
I have updated wiki with that info
http://wiki.xda-developers.com/index.php?pagename=BA_Radio_1.13_Upgrade
It has been tested (that is to say the flash works)
Have fun.
Seems like the GPRS "cannot connect" Problem has been fixed in this stack.
Cant manually reproduce the problem like i used to be able to, so time will tell, but so far so good
problems with no hearing the caller
Is the problem "no hearing the caller" solved with this radio radio 1.13? I can't solve this problem. Can anyone help me?
Re: problems with no hearing the caller
chaniko said:
Is the problem "no hearing the caller" solved with this radio radio 1.13? I can't solve this problem. Can anyone help me?
Click to expand...
Click to collapse
Only time can tell, and it's to early to say yet.
Just upgrade to 1.13 radio.
Let's see.....
MDAIII,
Good job with the instructions which makes it very easy to upgrade. Works better than 1.12 radio. Wish the bluetooth would not give the "insufficient memory" error.
Thanks.
Updated to 1.13
Update works fine.
GPRS Problem seems to be gone. (Works here by now)
SMS works fine (1.12 gave me a little problem here)
Bluetooth works fine (Fast on/off)
Nothing to mourn ATM
No negatives yet here. Haven't encountered the 'no sound' issue yet. I haven't noticed any improvements, though.
I'm glad to hear about the GPRS. Has anyone tested the WiFi feature and how long it takes to connect to activestync? I have notices that my BA, after upgradeing to the new Shipped Asia ROM, takes a really long time to connect to activestync (about 1min.) compared to older radios. Which took at the most 5 seconds to make a handshare.
Will This work on a SX66?
hakushox, it will. Follow the instructions MDAIIIUser has laid out on wiki.
when i just tried it says its not designed for my phone
Then you didn't follow the instructions properly.
You can always use maUpgrade_noID.exe
sprite backup after upgrade??
hi all,
if i upgrade my radio and after the hard reset, i restore with sprite backup, will it downgrade the radio as well?
please reply urgently! i cant resist the temptation to upgrade!
will doing a Radio update only make me have to reinstall all my programs and settings....if so, is there an easy way around this.....
Doing a radio update WILL make you have to do a hard reset. You will get errors when you try to restore your backup using sprite. You will have to re-install your applications after a radio update. Thats why i;m waiting till my questions have been answered before I upgrade since I just upgraded the ROM last week.
TheLastOne said:
You can always use maUpgrade_noID.exe
Click to expand...
Click to collapse
I tried that on the TypeI Radio, diddent work. I diddent try it on the TypeII though but it should work.
studdocs said:
if i upgrade my radio and after the hard reset, i restore with sprite backup, will it downgrade the radio as well?
Click to expand...
Click to collapse
Well I did the nasty thing and used Sprite Backup to restore, wanted to try since this was only a Radio upgrade.
Works perfectly until now.
But to really test this new Radio, one should not use any Restore functions.
Okay, so only time will tell whether this new Radio ROM will fix the known echo issues during bluetooth carkit telephone conversations...
It's been like a day now, I assume peeps who upgraded yet would have made several phonecalls by now... :twisted: hehe
So... wots the verdict?.. :?
Edit: Nevermind, f*ck the verdict. I've gone in, full throttle. I'll let you know the outcome, going for a ride right now.
Hi,
well I have tried, still Echo :-(
I use Radio 1.13 now.
I have echo when only using the MDA and
I have echo when using a Lintech Bluetooth adapter in my Nokia Cark-91.
The first can't be a Bluetooth problem, the second one is a bluetooth problem, even after stack BT-3900.
So I think it's a great device, but as a phone it realy sucks.
I think the bluetooth is the biggest problem.
Hope it can be fixed soon.
Regards,
Max
Just HAVE a bluetooth insufficient memory error.
GPRS seems okay so far.
No caller hearing problem.
Have a weird problem and wanted to see if anyone knows a fix.
I have siemens sx66 running wm2003
When using the phone through out the day the phone part of it stops making and recieving calls, even a reset wont fix the issue, after about 5 mins it will reconnect to the network and start to work fine, this happens about 5 times a day. It is not a reception issue since the phone worked fine in my house for the last year, it just started happening.
I upgraded to Helmi AKU3.2 1.3.2b windows mobile 5 and it seems to be more stable. Now when i lose the connection with the network a softreset will allow it to reconnect back to the network. One time when it disconnected i went into device information and for radio rom it said NONE, could this have something to do with the problem, is the phone deleting the radio rom or not seeing it sometimes?
Update:
To try to fix this issue I first smacked it a couple of times, this did nothing to resolve the problem, I then took the entire phone apart to see if there was anything broken, after noticing nothing I smacked the phone a couple of more times. After putting the phone back together the issue is still there.
doing a soft reset when "Radio: NONE" pops up seems to be the only solution.
btw, have you upgraded to Radio 1.15.00?
Hi all.
I'm facing the same issue.
Since I upgraded to Helmi's AKU3.2-1.3.1 I noticed, that the Radio Stack suddenly is lost. You will get no error message. Switching the BA on you will note that the Radio Icon has an "!". Soft resetting will not work. But strange enough, if putting th BA into craddle (or using an USB cable for syncing/charging) and then soft resetting will work, the radio unit is re-enabled again.
I'm now on AKU 3.2-1.3.2 and the issue still exists.
Unfortunately you cannot reproduce this behaviour. Sometimes it happens, but you can be happy and the BA is working for day's without any trouble.
Beside this: the BT stack performance is the worsest I ever met. Just noise, jitter and a very short range using my Headset (Plantronics M2500)
I will try AKU 2.6 this weekend hoping it will be more stable.
yes upgraded to radio rom 1.15 from 1.13 hoping it would fix the issue. Do you guys think the issue is hardware or software?
dr.x
You may want to downgrade from 1.15. There have been several reports in different posts that 1.15 presents several random problems. I installed it for about 2 weeks, but then my phone started making sounds like screetching metal, which led me to believe that I had a loose wire on the speaker or something like that. Then, I remembered about some people complaining about this Radio, so I decided to downgrade. Have not had that problem again. Moreover, I seemed to have weird reception problems in areas where I normally had good signal as well.
All in all, my bets are towards the Radio rather than the BA itself. So, downgrade your Radio and stop hitting your BA before I have to call "BA Services" for domestic violence :wink:
Hope this helps!
dr.x said:
yes upgraded to radio rom 1.15 from 1.13 hoping it would fix the issue. Do you guys think the issue is hardware or software?
Click to expand...
Click to collapse
Hi.
I upgraded to Radio ROM 1.15.00 long time ago und as it worked fine.
As I mentioned before, i faced the problems with disappearing Radio Unit first after I upgraded to AKU 3.2-1.3.1
So I suppose, it will have to do with this ROM Version (AKU 3.2-x.x.x)
Regards
Chuck
Just flashed my XDA IIs with both roms. Now using Helmi_BA_WM2k5_AKU3.5_v1.4.CF2 R2 . The problems I have are when taking out of the cradle the phone will soft reset its self, but not come back with the radio stack or the other numbers before wm2k5.
if I do a soft reset it all comes back fine.
Tried re flashing just the radio but didn’t help.
I think it may have something to do with the cradle, as with the other rom, and the old rom the XDA would shut down when you put it in the cradle.
there is something about this issue i think in the helmi 1.3 rom discussion...i had the same problem, but after upgrading it was ok...
Radio Signal Drop Problem
Hi xplode.
Very happy using the R4 rom,faster and having good interface to work with it...Thanks
After flashing your Rom i have started knowing this Many time Radio signal drops and call disconnects at the Same time if we try to make out going call signal strength is full but call doesnt get completed message appears on the top of the Screen as after Soft Reset Method done calling starts working.
This Problem As actually started after actual USE of the Phone 48hrs.
Required soultion for the same .
NOTE: this problem was not there with earlier R3 rom as its been tested too on my Ba .
ROM VERSION ...5.35.04 wwe
ROM DATE ...11/02/06
RADIO ....1.15.00
Protocol version..1337.45
Extrom ...xplode_2.0
nyuszi said:
there is something about this issue i think in the helmi 1.3 rom discussion...i had the same problem, but after upgrading it was ok...
Click to expand...
Click to collapse
I have tried a few roms now, and it will do it on all of them. It can be a pain because if the unit soft resets its self with me knowing the phone wont work.
anybody got any ideas?
still haveing problems with unit turning off or soft reseting when put in cradle, might it be related?
Hi all, had my Kaiser a while now and have been using a few different ROMs in this time which have all worked great! The last ROM I used was HyperDragon III. It worked fine for a few days, then started playing up massively. It intermittantly works - Some times I won't receive anything for 3-4 hours, then receive loads of texts and missed calls at once.
T-mobile checked the network, etc. and everything was fine. Re-flashed it back to the original ROM from on here (T-Mobile UK) and it's still playing up the same!
When I put my SIM in a different phone, it works perfectly.
What else can I do/try? I *think* I flashed back to the right radio too but not 100% sure. How do I check what radio/rom versions are currently on the phone?
Thanks!
Radio version can be found @ bootup R: , remeber that the recomended radio may not apply to you as there region specific, so the best bet is to look @ people sigs in your area and see what radio they are using?
Your in the UK try 1.70.19.09 on cooked ROM it's what i always use
R:1.27.15.32
G 22.51.88.13h
D 156.00.00
That's what I got on startup.
For some reason too, when I restart the phone, before it comes to that screen it shows the Hyper Dragon screen first!
I'll try a different radio and ROM then I'm worried it's not a fault with the actual phone..
never mind, advice already given
Well I've upgraded to 1.70.19.09 Radio and Anryl Ultimate Release 3.
Phone seems alright after 20 minutes, but it'll need a few days of testing.
It's not looking good so far - I've just soft-reset my phone and it set the time back to 13:32.. Which certainly isn't the time! It was doing this before when it wasn't working properly too.
This ROM seems incredibly buggy too! Opera keeps closing itself, as well as a few other programs.. randomly!
Help please! I'm frustrated.
jamiepyrite said:
Well I've upgraded to 1.70.19.09 Radio and Anryl Ultimate Release 3.
Phone seems alright after 20 minutes, but it'll need a few days of testing.
It's not looking good so far - I've just soft-reset my phone and it set the time back to 13:32.. Which certainly isn't the time! It was doing this before when it wasn't working properly too.
This ROM seems incredibly buggy too! Opera keeps closing itself, as well as a few other programs.. randomly!
Help please! I'm frustrated.
Click to expand...
Click to collapse
Some times if you don't do a hard reset right after flashing successfully, before the phone set up, things will act buggy. Make sure you do the hard reset.
jamiepyrite said:
Well I've upgraded to 1.70.19.09 Radio and Anryl Ultimate Release 3.
Phone seems alright after 20 minutes, but it'll need a few days of testing.
It's not looking good so far - I've just soft-reset my phone and it set the time back to 13:32.. Which certainly isn't the time! It was doing this before when it wasn't working properly too.
This ROM seems incredibly buggy too! Opera keeps closing itself, as well as a few other programs.. randomly!
Help please! I'm frustrated.
Click to expand...
Click to collapse
This should do the trick. I think the recent Hyperdragon Roms are WM6.1 and the radio you had listed is for WM6.0. This can cause all sorts of hangs/volume problems etc. Also check which SPL version you have - A WM6.0 SPL can also cause hangs etc if used on a WM6.1 rom.
EDIT: sorry, only read the radio bit of the fix.
Make sure you get rom/radio and SPL all matched ie WM6.0 or WM6,1. Most of the latest roms are WM6.1. If you find Anryls rom buggy, just try another one - I love the Garmin series.
Thanks for the advice How would I check which SPL I'm on?
Unfortunately I've hard reset it with Anryl and still running terribly. Lost the network this morning too so I received a text a few hours late.
I think I'm just going to go with a ROM that's as lite as possible now!
Sorted - I've upgraded to Hard SPL 3.28 and I'll flash the ROM to something lighter. Thanks guys
It appears to be working fine except I'm still having the problem of it changing the time!
Just checked the phone and it's saying 16:50.. Although half an hour ago it read the correct time. Any ideas?
I'm using Galarm 1.4 if it makes a difference. Running Athine Lite now.
Sorry everyone - Phone still isn't working properly. On the correct SPL, correct radio and correct ROM.. done a hard reset.. And it still just keeps losing network! Think my phone might be broken in some way?
I *assume* it's under warranty.. I got it under a year ago, but got it due to an insurance claim of my Hermes, they replaced it with a Kaiser.
When I phoned T-Mobile, they said although I got it from the t-mobile store, I'd need to speak to my Insurance company.
BUT I'd need to put it back to standard for Warranty purposes! I've no idea what I'd need to go back to..
thanks everyone
bump - anyone?
jamiepyrite said:
BUT I'd need to put it back to standard for Warranty purposes! I've no idea what I'd need to go back to..
thanks everyone
Click to expand...
Click to collapse
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs