Related
From http://www.seeo2.com/support/XdaIIs/template/ServiceMenu.vm
As it's only available for O2 Asia customers then I cannot see the files / nor get at it ...
Can anyone oblige / test ?
Cheers
Mark
Here you go
http://www.seeo2.com/user/XdaIIs/te...Action/downloadfile/19/dpr/51016/swupgrade/13
Prelimanary test are good. I'm guessing the patch is exactly the same as the one posted for the Pda2k from Imate, it is build 3500. SO far no issue with my sony hbh-660 headset and no issues yet with my TomTom Navigator USA bluetooth either. So for now, I am very pleased with the results, but I am going to give it one full day, especially with the headset before I can completely be satisifed. Adios.
imagine_einstein said:
Here you go
http://www.seeo2.com/user/XdaIIs/te...Action/downloadfile/19/dpr/51016/swupgrade/13
Click to expand...
Click to collapse
Doesn't work for me - keeps 'looping' back to the login page
Any chance you can post the file here ?
Thanks
Mark
Here you go
Extraction
Anyway to extract the files from this setup?
Good question. I know it's a setup.exe pretty much that kicks off the install process via active synch, then seems to place the temp files in Flash memory, thus requiring the soft reset. Not sure there is a way to capture the files being written to temp space, but I am sure there is someone on this forum that can do it
If you run the installation without connecting your XDA, you will find the cab file in:
C:\Program Files\Microsoft ActiveSync\Bluetooth headset upgrade patch for Xda IIs
Interesting that with the first imate posted bt patch the 3500 version which was withdrawn, one file showed build 3000 all others 3500. this O2 patch makes all file versions 3500 so is a final release and later than the imate patch.
Imate say they have a new final patch coming soon which will prob be the same as o2, since these all come from htc.
Patch seems good so far.
3500 Patch seems to be good
Downloaded the 3500 patch yesterday and installed in my i-mate PDA2k, certainly seems to have fixed the main BT headset problems (Sony Ericsson HBH-20). Thanks to those who take the time to post these things. A good Christmas present.
not so good. again scrasheesssss into the headset.
Waiting for another patch
hey this is the same old patch that was released by QTEK 3 weeks ago so whats new in it. I have checked both the patches they are both the same, not even a single file differs. But as always O2 is the last to deliver patches. It is very slow in providing updates, all other operators have provided new rom updates butO2 is still waitng dont now for what.
THE LAST TO DELIVER PATCHES????
Imate didn't release this patch for almost 4 days after O2 and before they had a 3000 build release. Tell the Tmobile MDA people, Siemens SX66 and all the CDMA versions of the phone with crippled bluetooth who have had no "official" update.
Great that Qtech first and early but O2 were second when all the rest are still waiting.
ONLY qtech has released a full upgrade rom. No others have.
Of course the patch will be the same, its not the operator like Qtech or Imate that makes these things, its HTC.
Patch Not Working in SX66
I dl'ed the patch into my SX66, and was hoping - no PRAYING - that it would help the BT issues..
My Jabra 250 sounds just the same..damnit!! (grin!)
Any other ideas, folks?
BTW, HAPPY NEW YEAR!
Well, needless to sat after further testing of the O2 xdaiis patch, I am still having issues with my Sony headset. I am connected for 4 hours and then all of the sudden the pairing just drops and I have to reconnect the headset which is very frustrating, so it sems this latest patch has some issues. NOt sure what to do now. I have already sent O2 support several e-mails with just a standard canned response, which is total BS
The Imate patch is way way better
Well I have tried the XDA IIs patch and I must say it sucks a.. The Imate patch which is a lower bluetooth stack build is way better. With the O2 patch the XDA IIs still randomly turns on. Garbage!!! Come on O2 release a new rom with media player 10 and a bluetooth fix.
Michael :idea:
No problems here...Motorola 850 works PERFECT. The official BT patch works great...must be either your headset or 3rd party software
Where...
can I get the imate patch...and is it the whole rom or just hte BT stack> Many thanks;' perhaps THAT will work in my SX66 and my son's O2
Guest, I have two XDA II's with a Motorola 820 bluetooth headset, and with all native apps installed and on the O2 bluetooth patch release it turns on randomly. It does not with the I mate patch so, the O2 release is garbage. Thats why Imate pulled they same bluetooth stack build that O2 released. There is issues with it.
Help !~
My O2IIs Bluetooth when I turn on it and go to susupend(standby mode?!) around 5 min ,then I resume the OsIIs again but the bluetooth will be turn off and on .....that have a big problems when I"m using the handset and have incoming call ! The OsIIs is going to resume ..... then the handset will be disconnect (because the BT was turn off automatically)~~But any problem when I do it in 5 min !! ......and I'm sure is not my handset connection problem!!
How can I Sovle it??
Thx ~~
First thing I'd do is ugrade to the latest ROM - you are still using the older one. If you still have problems after that it may be worth going from BT3500 to 3900.
If you don't know how to do either of the above have a little search around the forum. The new ROM is on the O2 site and there are numerous postings about the 3500 to 3900 upgrade all over this forum.
R
rakh1 said:
First thing I'd do is ugrade to the latest ROM - you are still using the older one. If you still have problems after that it may be worth going from BT3500 to 3900.
If you don't know how to do either of the above have a little search around the forum. The new ROM is on the O2 site and there are numerous postings about the 3500 to 3900 upgrade all over this forum.
R
Click to expand...
Click to collapse
Don't bother. I have 3900 on my IIs and it still does the same thing.
Thanks for rakh1 and kevinnugent reply~~
In fact ,I tried to downlaod and upgrade the newest ROM form the O2 website ! but my O2IIs is not buy in UK ! so....
In the mean time ,I"m also "cooked" (crack?!.. I don't understand what difference on "cooked" and "crack",haha~) the ROM by the "XDA3nbtool",but have the error message on installation ,that show "Radio image file checksum Error ",when I replace the original radio image,that will show the other image file checksum error.....
And I contact the O2 Custom Center in HK ,but they ask me to contact the Singapore customer service ,and said "they just have a repair service only!they haven't technical support ! "
OMG!! haha...a sick joke !! :lol: :lol:
Finally,the Singapore Custom Center still haven't the solution about this problem !... they just send the "bluetooth BT3500 update patch " for me to try (haha!!...) it can solve this problem or not !!
I have the same problem about BT disconnection
I posted an item about the same problem two days ago...
And the "official" technical support did the same to me: send me the 3500 BT Stack (and I found it in the web and installed two weeks before. Great technical support!).
In fact it's frustrating: I need a car kit that works well for my job, but impossible with Qtek. So, if I want to have a hands free car kit...I must buy another phone?.
Incredible for an expensive machine like Qtek 9090.
I have'nt tryed for the sort of multiple patchs of 3900, but I have no faith in it.
I you find a solution, please let me know.
Good luck!.
j.m.
Hey ~I have the solution now?!~and I tried it a whole day~any problem!
Firstly You must stop the "Auto Power Off" Function on the O2IIs,then go to:
http://www.pocketgear.com/software_detail.asp?id=14621
to download the "screenlock" (software) and install it ,after the installation ,you will not have the icon on the “Program file “ (haha…may be the software bug),than go to “file exploroe” ->”My Device”->”Program files”->”screenLock”->”screenlock.exe”,When you run it the first time it will be create the icon on “program file”,If you want to leave it, press the button 1 and 4 (Calendar and Message button on the IIs) simultaneously! Now !the Bluetooth will be connected every time ~
but I still hoped the O2IIs announce the newest rom update for the Asia user soon……..
By the way, when updated the BT3500 ,the “auto resume” problem will be solve or not ??because I’m updated to BT 3900 still no change…..
Thx
Cangratulations Alextly!
ScreenLock works fine, and although this is like killing flyes with a bazooka, it's the only solution that I know about it, and this convert this solution in the better one.
The only question I've got now it's about power consumption. This program Locks (turns down) the screen but, if I understood well, with the screen locked the CPU is sitill gorking "underground", so the battery life can be reduced (I must do some proves).
As far as I know, the BT3500 doesn't solve the problem (I installed and it's the same). I ignore if the 3900 it does, but I'm afraid that it will not. I have not installed because the 3900 I've fount it's some sort of different patches that and they doesn't seem to be very reliable. So I prefer to wait for official Patche. And as says "kevinnugent" seems not to work.
Let's keep the faith for official technical service (my faith it's going down for minutes).
Thanks for you're finding and congratulations. I would never find this one.
j.m.
ScrrenLock
ScreenLock it's not as fantastic as I though: it shuts down the PDA automatically when you are in no-battery mode (for exemple when you're using TOMTOM), and increase battery consumption dramatically.
j.m.
Interesting... I don't seem to have the same symptoms with my SX66 paired with my SE HBH-300 and HCB-30 (car kit). When the SX66 goes into standby, the BT seems to stay connected. If it does disconect with either handsfree, I just press the call pick-up on the handsfree and it re-establishes the BT connection within 2-3 seconds.
I'm using 3900.
Ken
SX66
In fact I think the connection must not be disconnected. And with my Qtek if you have good luck and re-establish the in some way, maybe you will hear nothing...
My car kit it's Drive Blue from Parrot.
j.m.
Just checked the o2 site and it seems this upgrade is now available, not tried it yet but will tonight
hi, which site are you downloading from?
www.my-xda.com
Any news on whether it is worth upgrading to the .171 ROM? Seems as though the radio is back to 1.00?
bobster007 said:
Just checked the o2 site and it seems this upgrade is now available, not tried it yet but will tonight
Click to expand...
Click to collapse
We are waiting for more info about the new rom!
Might be an anomoly but I tried the 171 ROM modified and my device has hard reset twice, with the original ROM the phone stopped working and needed a hard reset to sort it out, twice.
Think I'll keep to my 162 ROM. How's everyone else found it?
http://www.my-xda.com/xda2i_soft3.html
here's the direct link for 1.11.171 - just downloading and will let you know how I get on after discovering that 1.11.170 (blackberry)didn't work with radio version as supplied.
Hi!
When I have install it. It apeared the radio 1.100
So still old radio, not v1.104
phuong said:
Hi!
When I have install it. It apeared the radio 1.100
So still old radio, not v1.104
Click to expand...
Click to collapse
that is correct. Radio 1.104 is not compatible with the Blackberry system. This is the main reason that ROM 1.11.170 was removed from the o2 website as it had upgraded the Radio version from 1.100 to 1.104.
Hi! I've just bought an O2XDAIIi. I just wonder which ROM version I should use to upgrade my XDA. Could anyone give me an advice?
MrSandman said:
Hi! I've just bought an O2XDAIIi. I just wonder which ROM version I should use to upgrade my XDA. Could anyone give me an advice?
Click to expand...
Click to collapse
I'm using Blackberry and have upgraded to the latest o2 ROM - 1.11.171. If you aren't using Blackberry, try using Pugs cooked version of 1.11.169.
Is there any change to Blackberry functionality on 71 over 69?
Won't be changing if there isn't.
I belive that if your using the o2email open and not the BES version you won;t lose your Calendar options.
We use BES so no need to change then - thanks
Well ROM version 1.11.171 seems to be as stable as 1.11.169 and I don't have to use the workaround to sync Outlook Calendar.
I wonder if o2 are going to release more XDA phones that can use Blackberry - I quiet fancy the o2 Atom but it doesn't list BB which is a shame.
171 ROM is the BT reliability resolved
Symbasean,
Stating that the 171 ROM is as stable as the 169 ROM is a little bit of a two edged sword for me.
When I applied the O2 ROM last October / November it trashed my bluetooth functionality, effectively making my Jabra 250V a large black ear ring and the XDA 11i an electronic chocolate tea pot, for use in a car.
Can you sense my frustration with O2, who offered me £10 off my next bill as compensation and then didn't give it to me.
I switched to one of PUG's home cooked ROMs and this has been 80% successful, but randomly fails to deliver the sound.
His version has been a saviour, but would the 171 be an improvement for the BT stability and reliability?
Sorry for the incredibly rambling first post. :?: :roll:
I upgraded to the new software last night and have noticed one small annoyance. I used to be able to to deactivate GPRS by clicking the connectivity icon in the title bar and tapping disconnect. Now the disconnect option isn't there for GPRS. Eventually I discovered that I could turn off GPRS by holding the end call button.
Re: 171 ROM is the BT reliability resolved
dgt1963 said:
Symbasean,
Stating that the 171 ROM is as stable as the 169 ROM is a little bit of a two edged sword for me.
When I applied the O2 ROM last October / November it trashed my bluetooth functionality, effectively making my Jabra 250V a large black ear ring and the XDA 11i an electronic chocolate tea pot, for use in a car.
Can you sense my frustration with O2, who offered me £10 off my next bill as compensation and then didn't give it to me.
I switched to one of PUG's home cooked ROMs and this has been 80% successful, but randomly fails to deliver the sound.
His version has been a saviour, but would the 171 be an improvement for the BT stability and reliability?
Sorry for the incredibly rambling first post. :?: :roll:
Click to expand...
Click to collapse
two points:-
1. please spell my name correctly.
2. "Well ROM version 1.11.171 seems" - note also the word, "Seems". I make no direct comparison on stablity, only that mine has not crashed - caveat empore......
Apologies
Symbaseian
Sorry for the mistake.
I shall try the ROM and see.
I have to agree caveat emptor is an appropriate warning with this particular device.
If it worked as well as it is should, straoight out of the box, it would be excellent.
But it does have some way to go, and without the likes of these forums, it would not happen.
Dave
Re: Apologies
dgt1963 said:
Symbaseian
Sorry for the mistake.
I shall try the ROM and see.
I have to agree caveat emptor is an appropriate warning with this particular device.
If it worked as well as it is should, straoight out of the box, it would be excellent.
But it does have some way to go, and without the likes of these forums, it would not happen.
Dave
Click to expand...
Click to collapse
I totally agree. When I first got one of these I couldn't use TT3 let alone TT5 without it locking up all the time if I used anything other than my old 128mb Compaq SD card, but having listened and learned on this forum and also on pocketgpsworld I now have a stable XDAIIi with blackberry.
It's taken a long time to get to where I'm fully happy with the device (except camera performance - but I very rarely use that anyway) often involving Tomtom tech support, o2 tech support and these forums. If you feel happy using Pugs ROM version without blackberry please go ahead, but for me that's not an option.
It's just a shame that we have had to co-develope to get a product that is finally starting to show everything that it first promised.....
Occasionally I have a problem where when making or receiving calls I pick up and there is no sound. If I Soft Reset I can make the call and it works fine. It's been starting to happen more often recently, and is really bugging me. It happens both when I'm using the phone speaker, and my headset.
what rom are you using? I have noticed the same thing the last couple of days since upgrading to L26 M2D v1
ah, here it is the same thread.
I use WM 6.1 htc version
Is there no bugfix?
Have you tried flashing a new radio?
Ta
Dave
data at info:
ROM: 3.28.407.0 GER
funkempfänger (i guess it's the radio): 1.65.16.25
protocoll: 25.83.40.02H
it was updated with the new htc 6.1 version what i've heard.
or can i downgrade it to a version that is working fine? when yes, where is the file to do so..
Right now I'm using Radio 1.58.16.27, I'll try another one, which do you recommend?
I was using 1.65.29.22, switched to 1.65.24.36 (I was using this with L26 diamond V12 with no issues)
had the same issue today.
hm, looks like a big upcoming problem for everyone...
what roms does everyone have? any "recently added" apps or changes?
ill start
L26_KaiserTouch_V1_M2D
NETCF 3.5
HTC AudioManager_2_0_1819_2129
Opal stuff
virusv69 said:
what roms does everyone have? any "recently added" apps or changes?
ill start
L26_KaiserTouch_V1_M2D
NETCF 3.5
HTC AudioManager_2_0_1819_2129
Opal stuff
Click to expand...
Click to collapse
Old thread but still, I've been experiencing this issue on the Hyperdragon series of ROMs from late October. Also had this problem in the past on some of Dutty's roms. The latest Raphael version (15/11/2008) has not exhibited this problem in 4 days. Only difference I can see is a slightly newer version of MSVC (1.6.19965).
Cheers.
gatewayer said:
hm, looks like a big upcoming problem for everyone...
Click to expand...
Click to collapse
I am getting the same problem intermittently, with a soft reset as the solution.
I am running a bone stock AT$T rom,recently upgraded to 6.1. It started happening post upgrade.
An upgrade problem?
same here... im playing around with different radios, it has to be a radio issue imo
I would just love to have this issue solved. It's not new whatch here; http://forum.xda-developers.com/showthread.php?t=383539
Peregrine
1stPeregrine said:
I would just love to have this issue solved. It's not new whatch here; http://forum.xda-developers.com/showthread.php?t=383539
Peregrine
Click to expand...
Click to collapse
My phone rings and notifies just fine when Texts,emails and calls come in. It answers just fine, but there is no sound. Then when I try to call people back, there is no dial sound and the call appears to not go through, until I do a soft reset, then all is back to normal.....................for a while.......................
I'm having this issue also. The other party can hear me when I answer, but I can't hear anything after the initial incoming-call ringing. A power-cycle restores normal operation but only for a while.
ROM: 3.28.405.0 WWE, 05/02/2008
Radio: 1.71.09.01
Protocol: 25.75.40.02.eMo
I'm in same boat as everyone else here.
Sometimes my phones rings, but when I answer I have no sound and other party can't hear me. Other times, my phone doesn't ring and all audio is muted (despite volume on). Soft reset is the only thing that works for me.
I gotta say this is really pissing me off. I'm missing lots of important calls because my phone doesn't ring when it should, or if I'm lucky it rings but has no audio so I have to soft-reset and wait 5 minutes for my phone to reboot & re-establish signal all whilst my clients are trying repeatedly to call me.
I'm willing to try other radios, but no one seems to have any working suggestions.
Thought maybe it was software, since I don't remember this happening after my initial WM6.1 upgrade. Uninstalling S2U2 didn't work (happened again today). Just uninstalled Voice Command, too, but haven't tested yet. VC's been flaky since upgrading to 6.1, working sometimes, failing to announce calls other times, plus occasional VC crashes at boot claiming "out of memory" which is blatantly untrue.
Just out of curiousity, is everyone with this problem using Voice Command, or just some of us?
Think I might have to go back to WM 6.0 since 6.1 didn't solve my Bluetooth issues plus screwed up Destinator...oh well. Schap's WM6 4.31 was best ROM anyway.
Anyone having any luck with this problem?
Like I said, I was running AT$T WM6 with no issues. The I updated to WM6.1 and started having these call issues.
Last week I flashed to HD III still no joy. SJ says that he is running the same radio as me, 1.65.24.36 with no problems.
Is it " my " phone? Microsuck 6.1 ? The radio ? Has anyone solved this with a new radio flash ?
I run a business on this phone and it is getting really frustrating, I don't want to go back to 6.0 just so I can get my phone calls?
I'm not just whining, looking for sucess stories.
Hi, havent been here in a while but i thought i'd add to the list. I have recently flashed HD3 (one of the early november editions) and it was without problems until friday when i dropped my fone. Ever since then i have had the intermittent sound in call which is only fixed by a soft reset (exactly the same as denco7). I haven't changed the radio since dutty's 1st diamond rom (a while ago) as i haven't had any problems but now im thinking about it.
Current setup (from device info):
ROM version: HD_III_Jade WWE
ROM date: 09/30/08
Radio version: 1.65.24.36
Protocol version: 25.94.40.06H
Not using MSVC
Recently flashed to HD III Blackstone hoping this might work but still having the problem.
I also flashed radios 1.65.24.36 and 1.70.18.02
and now I am running 1.70.19.09....... and it is still happening. It has got to be something in WM 6.1. Cannot be a software conflict, because it was happening when I was running bone stock AT$T 6.1 upgrade with no software add ons.
Again, I would hate to think that I have to downgrade to 6.0 just to get my phone calls.
Damn WM6.1 sound!
Well, I thought I'd let everyone know that I've uninstalled all my favorite apps from my Kaiser. No MSVC, no S2U2, occasional hands-free Bluetooth, and no A2DP. In that time, I've had only 2 incidents of no sound for the last 3 weeks--much better than no sound every few days or even several times a day. Don't know that the apps have anything to do with it since denco7 had same problem on an unadulterated AT&T ROM.
The big question is why do we all have the same sound problem but most WM6.1 Kaiser users do not (if everyone did I'm sure there would be a lot more *****ing). If we could reproduce it at will, we'd at least have something to focus on. Not knowing that, I'll have to guess and say that I suspect one or more of the following:
WM6.1 and/or the 1.65+ radios required for WM6.1 introduced some sound bug (deadlock, dereferenced pointer, etc.). The more apps that interact with sound and/or the radio, the more likely the bug will be triggered. But even if this is true, why does it happen to us but not to others?
The bug exists only in a particular base ROM source used by the ROM cookers. Still, should be affecting more people.
Maybe people who customize their phones are more likely to reset and clear any conditions that lead to no sound? Doesn't seem likely, but hey...
The problem exists only in specific Kaiser versions, perhaps even in conjunction with only specific WM6.1 builds and/or radios. I think there's been 5+ different hardware versions of the Kaiser line, but I can't find where I read this or how to tell what version your Kaiser is.
Bluetooth affecting sound? Got absolutely nothing to back this up other than WM6.1 supposedly fixed a lot of Bluetooth problems and during the time of my frequent lockups, I was using A2DP to stream an audiobook to my car's Parrot MK6000. Finished the audiobook & quit traveling so much, so I rarely used Bluetooth during the last few weeks when I've had only 2 no sound incidents. BTW, I upgraded to WM6.1 specifically because of the Bluetooth fixes, hoping they fixed the 100% CPU usage after finishing a hands-free call and fixed the A2DP dropping after calls. WM6.1 didn't fix either, so what did they do? Maybe their "fixes" just introduced new problems?
Possible dead zone f'ing up the radio and consequently sound? I offer this only because when I was working in a particular dead zone I had frequent sound problems. For some reason, my phone has problems reconnecting after leaving this dead zone and I have to reboot. Occasionally it would reconnect without rebooting, but I never correlated this to no sound. However, I haven't been there in weeks, and my problems with sound decreased (although I also uninstalled apps & quit using Bluetooth as much). Went there last Friday, and while I was there I found I had no Windows sounds. Could dead zones or even just temporary signal loss be f'ing up the radio and consequently the sound?
These are all just guesses--I'm just throwing out some possibilities so we can find something in common between us. However, I gotta say that if I don't find a solution soon, I'm going to switch back to WM6. Threaded messages are nice, but they're not worth this no sound headache.
BTW, I'm using:
AT&T Tilt (purchased within a month of initial release)
ROMeOS v4.21.1 (OS v5.2.20273, AKU 1.3.3)
Radio 1.71.09.01
dear all...
i deceided a few weeks ago to change from nokia to the htc touch diamond. a friend of mine has an htc touch hd and i really liked it. the touch display was my favorit. i don't like apple products, so the iphone was never an option, also i don't like samsung products (mobile ones) because i had a samsung mobile and had a lot of troubles with it.
well... since i have the touch diamond, i also have troubles with it. in the first three days i wasn't able to phone -> the phone hangs up and if i tried to dial a number no one can hear me and i didn't hear the one i called. i gave it back to the shop for repair -> after two weeks i got it back and was told there was an software problem and it is now fixed. ok... well it was fixed, but new problems were upcoming. first of all the battery -> it's not possible to pass a day from morning to the late evening with charging the diamond only once... first i thought this is my biggest problem but then i revealed that an other bigger problem exists which actually effects my job. i'm not reachable because my mobile losts connectivity as soon as it goes to standby. when i activate it over the power button it searches for an gsm signal but it doesn't find one. it doesn't matter if i'm in my flat or if i stand with the mobile near to the radio mast. it only helps if i turn the phone function off and on.
my friend told me about the opportunity that this forum exists where people working on developing roms and other nice features for various mobiles and i should take a look at it. well.... i registered here, read the howtos and guides and flashing bibles and tried nearly all available roms here to improve the behaviours of my diamond, but i don't succeed, well this is the time, where i capitulate and ask for help... my provider can't help me... they said that the mobile is not so often sold and they don't hear anything about customer complaints...
info about my acutal-configuration:
mobile: htc touch diamond
spl: 1.9.30-OliNex HSPL
rom: 2.07.Gen.Y GER
radio: 1.09.25.23 (htc because mobile is still security locked)
protocoll version: 52.51.25.26H
provider: A1 mobilkom www.a1.net
location: EU/AT/VIENNA
can anyone give me suggestions what to do?
can anyone help me to make my diamond a mobilephone it should be or give me an advice what i can do?
i also think about resetting the phone to factory defaults (at the moment i'm searching for a guide) and give the handy back and pay the upgrade price for the touch hd... my friend doesn't have any problem with it and i don't know any other way out of this situation... at the moment i have a multimedia device with wich i can't phone and couldn't be reached which in my opinion is absolutly not acceptable.
kind regards
unlock it and use bsb rom
losing GSM signal when the phone is on standby? I'm just making a guess here, but I believe you might have a problem with the ROM and or just only the radio. unlock it and flash a new ROM and or a radio to see if it works
as for battery life, the Diamond battery is very bad, and the radio you use is directly related to the battery life, some radio sucks battery out dry pretty quickly, but normally, this phone requires a charge once per day