I have tried Tuma, Logout and Ivans versions and agree with the comments elsewhere on speed, reliability, battery use etc. However, I have had a problem with ALL of these ROMS - the phone stops working after 60 seconds (or less)!?! I have also tried 1.12, 1.13 and 1.15 of Radio but still the phone calls drop.
No-one else seems to have reported this problem so thought it was my device but I've reverted back to WM2003SE and it works fine. I really want to use WM5 and wonder whether there is an issue with the operator ID or if for some reason Orange are only allowing emergency type calls?
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
I recently flashed my phone to Dutty's dual touch 6.1 rom (from hyperdragon 3) and ever since i did phone calls have been a bit hit & miss. Ill ring someone and they wont be able to hear me, or ill ring someone and from the minute it ''connects'' i get a sort of staticy noise even after i hang up. Only way to get rid of it is to do a soft reset.
Am i right in thinking this is probably to do with the radio being miss matched? never had the problem before so just wanted to check it is before i started playing around with it.
if it is the radio, is it just a matter of hunting around for a new radio that goes with duttys ROM & flashing it in a similar way to flashing a new rom?
thanks guys
========================
MOD EDIT:
Please refrain from creating multiple posts about same topics. This is against xda forum rules. I have merged both of your threads together.
i also struggle to connect to any wifi networks. iv reflashed Dutty's latest 6.1 ROM (dual touch afaik) but it still has problems. I always thought dutty's Rom came with their own radio?
thanks guys
Wifi - unable to connect?
Last few days iv struggled to conect to any wifi network. When i select the network and try and connect the phone just sits there ''connecting'' until it tells me its unavaliable. iv tried on 2 different networks, both which have worked in the past.
It started when i flashed to Hyperdragon III ROM, then reflashing two of Dutty's ROM (latest 6.1 and dual touch) still hasnt sorted the problem.
Iv tried searching and couldnt find anything, and im getting a tad desperate tbh. I thought it could have been a problem with the radio, but both of duttys ROM come with their own radios and they have worked for me in the past.
This is a clean install, on Duttys latest 6.1 ROM and im lost for ideas!
Can anyone offer any advice? cheers guys
Hi everybody, i am new here and i need a little help on my Tytn II
So, i got a tytn II from orange but i was a little bit dissapointed by wm 6.0 which came on the device(slow drivers and so on) and put a wm 6.1 rom with hardspl(RUU_Kaiser_HTC_WWE_3.28.405.0_radio_sign_25.83.40.02_1.65.17.56_Ship)
Science then (and maybe also with 6.0) but i am not shure, i am experiencing some cpu hangs for few second from time to time. Most of the time it's after it returns from Stand By mode. It works fine for a few seconds than PAFF! hangs for a couple of seconds(touchflo not working). it's not the flo because also if i move some cursors with the keys from the phone it is still blocked. After a while it is stable but from time to time still hangs. I am so nervous because i keep pressing the tochflo and nothing happends.
I also tried this manila rom(it is currently installed) L26_KaiserTouch_V1M2D.rar with updates and still the same thing. I have tried to kill all the processes from the memory with celetask but again no feedback. Even turn off the radio by switching to airplane mode. What do you advise me to do? should i switch back to wm 6.0 which i hate? can i find another rom which works? why is the cpu hanging?
Thanks alot. I like the phone, it's cool, but this slowing it's drivin' me nuts!!
plase move this to kaizer general, i dind't see it(or is it a rom prolem?)
Hi!
I also have this problem. It happens with the original 6.0 Rom as well as with the 6.1 Rom from the HTC Website. Sometimes it works for days without an issue. Other days it freezes frequently for a few seconds.
Also, everybody else I know, who have the HTC Kaiser, have this issue.
I noticed that the dimming of screen works even when it is "frozen". Also the on/off button always works. So it is not really freezing but something else is going on?!
BlackICE said:
I also have this problem. It happens with the original 6.0 Rom as well as with the 6.1 Rom from the HTC Website.
Click to expand...
Click to collapse
I don't get pausing with the ROM/RADIO/SPL in my sig (HTC not Orange branded) but certainly the UK released HTC WM 6.1 ROM had the pausing bug. The OP is right in that WM 6.0 is slower than 6.1 but the setup I'm running is really very reliable when compared to WM 6.1. If the wrong SPL (or hardSPL in this case) is being used for the version of Windows Mobile (1.xx for WM 6.0 and 3.xx for WM 6.1), this will also exacerbate any pausing. SPL 1.93 was put on my phone by HTC when they reverted from WM 6.1 so if anyone is getting pausing under WM 6.0, maybe that SPL will fix things.
Hi,
I'm having the same problem as described above.
Anyone knows a solution for this?
I'm using WM 6.1 and my phone IS NOT locked at all...
Thanks in advance!
Sam
Sounds like a well known issue with a well known fix. Do you have the right HardSPL?
http://forum.xda-developers.com/showpost.php?p=2261226&postcount=2
http://forum.xda-developers.com/showthread.php?t=498320
Hi,
Thanks for your reply!
I flashed my "HardSPL"...
I hope now it does the trick!
Thanks again!
Sam
Inherited a HTC Fuze recently loaded with a custom Win 6.5 ROM. Noticed a couple of glitches that need fixing. Posting version below and then the issues I'm facing. Help appreciated as I'm new to this forum!
Rom Version : 23034_beta2 WWE 05/15/09
Radio Version : 1.02.25.32
Issues -
- Wifi not working. The fuze is unable to connect to the wifi network. All other devices I have recognize the network and connect. The fuze just can't.
- Fuze randomly starts adjusting system volume, then opens camera application and takes pictures. All without any intervention or touch from my side. Removing battery and then rebooting helps for a while, but the problem is persistent.
Clarifications Sought -
- Was thinking of flashing the Energy ROM Phoenix2 onto this. Would it solve
some problems?
- Does the radio need an upgrade? version mentioned above
Thanks
I'd recommend flashing to a new energyrom and upgrading the radio to 1.12.25.19 or the 1.17.25.09 one. I'm using the EnergyROM_28011_RAPHAEL_12.Dec.2009_StandardM2.5_MaxManila.rar
with the 1.17.25.09 radio and everythings working good.
Only thing about Manila 2.5 is that it doesn't have landscape and the 20811 roms have the start menu and other bottoms on the bottom of the screen, while the 21884 have them on the top like normal Windows Mobile builds.
Btw, im located in New York.
Hey,
Flashed to |RAPH|6.5.3|WWE| ★ EnergyROM 'Phoenix 2' (28011/21884) ★|Dec 9|Manila 2.1/Titanium but now the wifi button is greyed out....
Should I try a radio upgrade?
let's try to maximum performance for wifi
changing the wifi channel fixed it!