Hello!
I bought my Diamond - Windows 6.1 - Vodafone Branding 2 days ago and I can say it is very slow...
I thought it shouldn't bother me because there are many software and support for this device... so no problem.
But the biggest problem as a phone is:
When anyone wants to call me after ca. 2,5 rings my diamond begin to ring to... but this is too late... because it leads the caller by 3 rings to the mailbox.
Is there any solution to better the reaction time for a call?
SOLVED:
by using a .wav tone and disabling the HTC design for the phone-aplication. This can be done with the application DiamondTweak
I have the same problem on my T-Mobile MDA Compact IV - I've missed so many calls, even though to the caller its been ringing for ages! Surely HTC should have tested this?
search 1st please
if you search the forum this question has been asked and answered many times
http://forum.xda-developers.com/search.php?searchid=16966072
look its that easy
also if you want the phone faster...you need to flash the rom with one of many cooked roms here on this forum
http://forum.xda-developers.com/showthread.php?t=258109
there is a patch for WM5, but i've WM6 on my diamond... is it ok?
it will work just fine with wm6.x!
hargibi said:
it will work just fine with wm6.x!
Click to expand...
Click to collapse
it didn't... after installing I had no sound on the diamond!
I tried a .wav ringtone... now it rings after ca. 1,5 rings on the phone....
my nokia rings before the first ring...
has anyone a better idea?
redliner51 said:
Slow...Slower...Diamond??
I thought it shouldn't bother me because there are many software and support for this device... so no problem.
Click to expand...
Click to collapse
1.34 Stock...1.35 Stock...1.37 Stock...1.93 Stock... 1.93 CE 5.2.20755 Custom ROM
Indeed, don't let it bother you. With each released stock ROM and the custom cooked ROM's based on those stock ROM's, the speed, functionality and stability increased.
Even the current official stock 1.93 ROM, which you can upgrade to without losing warranty, is considerably faster than the early ones.
And as for the phone reaction time, it's a known annoying issue, so search and read what many before you have posted about the subject. Good luck!
I've the 1.37.162.2 GER ROM...
How much would this upgrade help the speed?
too much
http://www.htc.com/europe/SupportDownload.aspx?p_id=133&cat=2&dl_id=2
is that the newest ROM? Date: 2008-07-31 ?
Is it in German, too?
I installed the new Touch FLO 3d... is that the same effekt?
no, you have to upgrade rom too
Ok, I updated to the newest Vodafone ROM... everything is a bit faster apart from the ring delay...
it begin to ring after the second ring...
no solution?
there is a solution... cant remember where it is, on this forum.
I've the Vodafone ROM 1.93.162.3 GER
is the following TouchFLO3D newer than mine?
http://forum.xda-developers.com/showpost.php?p=2358935&postcount=225
redliner51 said:
I've the Vodafone ROM 1.93.162.3 GER
is the following TouchFLO3D newer than mine?
http://forum.xda-developers.com/showpost.php?p=2358935&postcount=225
Click to expand...
Click to collapse
go into 'Settings' tab on TouchFLO3D and scroll to the bottom to the 'About' bit.
shows you version number there
(mine is 1.2.34837.3_1813.6)
Ok, I've the 1.1.34574.1_1630.38
but what is with the ring delay now?
i installed this ring_delay_patch.cab from this forum too... now it rings some milliseconds before the second ring...
i can't understand this... so many people have a diamond and diamond should be a mobile phone but its phone capabilities are less than an old mobile phone....
do you use a .wav file as ring tone?
because if you use a .wma file it is normal that the ring is delayed... this because a .wma file is compressed so it takes much more time to be loaded by the OS, instead if the ring tone is a wav file it is very fast (because not compressed), so you mobile will start to ring soon
this is a normal behaviour in WM, I had the same issue some years ago, then after some searches I realized how to solve
suiller said:
do you use a .wav file as ring tone?
because if you use a .wma file it is normal that the ring is delayed... this because a .wma file is compressed so it takes much more time to be loaded by the OS, instead if the ring tone is a wav file it is very fast (because not compressed), so you mobile will start to ring soon
this is a normal behaviour in WM, I had the same issue some years ago, then after some searches I realized how to solve
Click to expand...
Click to collapse
+1
(sorry forgot about this )
I forgot to mention that the wav file should be no longer than 30/40 seconds
Related
Update: Solved!
Try your simcard in another (non-pda, non smartphone) cellphone.
If there is still the same delay, then its a providerproblem and you should contact your service hotline. In my case, this was the solution!
If the delay only occurs on your WM5 / WM6 device:
Then THIS here is the solution for you:
check this registry key: HKCU\\Control Panel\Sounds\RingTone0\script
simply change existing "3"'s to zeros... this string defines what the phone should do when a call comes in (a=begin script, r=repeat script, p=play ringtone, v=vibrate, w=pause, f=flash, c=volume)
in most cases, this should have been the solution for you.
if there exit still any delay problems:
try a wma standard ringtone which is stored in the phones main memory (NOT storage card). If this is the solution, then transform your desired ringtone into this format and move it into mainmemory.
(Addtionally you should be sure that there is no silence at the beginning of the ringtone itself... of course *g*)
I hope this helpful, good luck
-------------------------------
(Original Post)
Hi!
It looks like an old problem is back: the famous 3-4sec. delay of ringtones on incoming calls: The caller hears 3 to 4 "rings" while the kaiser which receives the call stays sleeping/silent and starts ringing with a delay (as mentioned 3-4 "rings").
Device Info:
HardSPL, Super CID, unlocked
Radiorom R 1.27.12.11
Protokollversion: G 22.45.88.01H
D 1.56.00.00
ROM Version: 1.56.112.4 (09/01/07) (german/Austrian T-Mobile )
Anyone got a solution so far?
I tried tweaks2k2, http://forum.xda-developers.com/showthread.php?t=258109&highlight=ring+delay and playing around with different ringtone files as well - but no improvement.
Any hints are highly appreciated.
PS: Beside this one, Kaiser is really rocking!
I think its pretty normal
Its not a GSM , kaiser must launch an application to start ringing, that just takes time, the more tools you install, the slower the application starts.
Try not to install to many programs in memory background, tweak your htc....
Of course you are right with the fact that Kaiser is no GSM and needs an app for that - but I am pretty sure that this is not the real problem: On Hermes we had the same problem which could be solved (see Schaps ROM) with the same apps / ringtones installed.
licht77 said:
Hi!
It looks like an old problem is back: the famous 3-4sec. delay of ringtones on incoming calls: The caller hears 3 to 4 "rings" while the kaiser which receives the call stays sleeping/silent and starts ringing with a delay (as mentioned 3-4 "rings").
Device Info:
HardSPL, Super CID, unlocked
Radiorom R 1.27.12.11
Protokollversion: G 22.45.88.01H
D 1.56.00.00
ROM Version: 1.56.112.4 (09/01/07) (german/Austrian T-Mobile )
Anyone got a solution so far?
I tried tweaks2k2, http://forum.xda-developers.com/showthread.php?t=258109&highlight=ring+delay and playing around with different ringtone files as well - but no improvement.
Any hints are highly appreciated.
PS: Beside this one, Kaiser is really rocking!
Click to expand...
Click to collapse
I have been using HelmiC's Clean/BigStorage version and I have had no problems with the ringtones. I have even tested it multiple times and it starts ringing at the very first ring. Do you have your ringtones on the phone or the storage card? If latter, try placing the ringtons on the phone (\My Documents\).
Hi! Thanks for your idea, und yes my ringtones are of course in the main memory for performance issues. As well I tried different formats (wav e.g.) with no improvement.
Any other statements to my problem? Are there other Kaiser ROMs which have the same problem or am i the only lucky one?
For your information: I tried tweaking the registry:
HKCU\ControlPanel\Sounds\RingTone0
Originally, my Kaiser had av0pw3r as Scriptvalue... I tried apr and av0pr but no improvement...
Any suggestions / comments?
(PS: Yes: tried different ringtone formats, ringtones are NOT on the storage card)
I had the same problem on the 8525 using MP3 files as ringtones. I converted my ringtone to a WAV file and the delay was much less. On my 8925, I'm using the same WAV ringtone file (in main memory) and my delay is usually just one ring on the callers end.
Which ROM are you using?
(btw.: tried of course different formats - wav, wma, mp3 -> all the same delay)
Machine: Original HTC TyTN2
ROM: 1.56.407.3, german
RADIO: 1.27.12.11
Provider: T-Mobile Austria
Ringtone: I'm using the standard ringtone from rom.
On my machine there is a delay of 1 ring until the Kaiser turns on and with the 2nd ring the Kaiser plays its ringtone. So I think this is fully normal.
I think you are all on the wrong track re ringtones...
The OP's actualy problem is that his device takes too long to actually wake on receiving a call.
I would bet $10 that it will be down to an application installed on the device that is screwing with its phone app responsiveness.
so there is no delay on plain devices with htc rom?
Is the ringtone present in main memory or on the sdcard ?
Maybe moving the ringtone to the main memory solves a bit of the problem.
On my TytnII the problem doesn't occur but the ringtone is placed in the main memory.
Simple to prove whether it is a ringtone. Just change the ring to one of the built in ones. If the device still delays waking on incoming calls, then you know its something else...
As mentioned in the opening post, the ringtone is on main memory and i tried standard tones too.
So what about your delays? Do you have one or not on your ROMs?
Is there an SCI (Slot Cycle Index) equivalent on 3G systems? On my Apache through Verizon (CDMA), lowering the SCI (how often your phone polls the tower for incoming calls) fixed this issue. So if there is an equivalent here, we should look into that.
Does anyone know how to get to the Kaiser's provisioning screen so I can check this out?
I have the same delay of 1 ring, then the kaiser wakes up and starts to play the ringtone.
Checked
I have just checked the delay on call arrives, and only 1 second.
I have optimized WMA (whichever little, better) file on \windows\rings
I my hermes i have more delay that in my Kaiser. And the cause in my hermes was related to the time the Hermes took to switch on. This time is lower in the Kaiser. When you press the On button, the Kaiser switch on quickly. See this posts on hermes section http://forum.xda-developers.com/showpost.php?p=1440403&postcount=266 and http://forum.xda-developers.com/showpost.php?p=1461092&postcount=406 for refference.
If you have notifications on wake-up, this can cause delay on the switch on when a call arrives, so take care of this too.
So no significant delay for me.
Hmm... "Slot Cycle Index" is a nice hint - i will have a closer look to this.
For the other ideas: Of course i am using an optimized WMA ringtone - stored in main memory - too.
In fact i encounter this delay of 3 rings even when my phone is switched already on... - and i guess thats not normal.
I got a bunch of applications installed - but the same like on my Hermes where I didnt had these delays. So if there are no other ideas i will try to hardreset and figure out if the problems occur with a plain german ROM too.
If not, then i will install application by application and give feedback which one did the delay.
I didn't check it with calls yet. But with SMS i noticed that my screen goes on, and then after 2secs the sms-tone goes off. So there's definately a delay.
Hello,
HTC have publied a HOT FIX FOR BLUETOOH
"/12/2007
Bluetooth Hot Fix (for HTC TyTN II)
Dropped calls sometimes occur when Bluetooth is on. If you encountered the same problem, please download this Bluetooth Hot Fix and install it on your device.
Go to htc club an enjoy.
Downloaded it from HTc.cOM
Installation instructions
Follow the instructions below to download and install the hot fix on your device:
Make sure you have Microsoft ActiveSync® installed on your Windows XP PC or Windows Mobile Device Center on your Windows Vista® PC. You can find Microsoft ActiveSync from this link or Windows Mobile Device Center from this link.
Connect and synchronize your device with your PC via Microsoft ActiveSync® or Windows Mobile Device Center using the USB cable.
To download thehot fix, first select the check box below. Next, select thehot fix and the desired FTP site then click Download.
Copy the hot fix, which is a cab file, to your device.
To install the hot fix, tap the cab file and follow the on-screen instructions.
Here is the file:
http://rapidshare.com/files/77588898/TyTNII_BT_Hotfix.zip
Enjoy,
Nadavi
for tytnII, but how about att tilt? is it rom specific?
Hope this will work. Thanks for the tip.
private69 said:
Hello,
HTC have publied a HOT FIX FOR BLUETOOH
"/12/2007
Bluetooth Hot Fix (for HTC TyTN II)
Dropped calls sometimes occur when Bluetooth is on. If you encountered the same problem, please download this Bluetooth Hot Fix and install it on your device.
Go to htc club an enjoy.
Click to expand...
Click to collapse
This does not show up on the updates for my TyTynII (downloads are serial number specific) only in the generic downloads.
I think its best if you only apply this IF you suffer with any Bluetooth problem.
The old adage, 'If it ain't broke, don't fix it!'
Re: does this work on AT&T Tilt?
In the HTC 1.56 ROM, this file is a replacement for \Windows\TIInit_4_2_38.bts a.k.a. (OEM\OEMDrivers\TIInit_4_2_38.bts for chefs). There is nothing else in that cab (see upgrading forums thread for better description)
Edit: I was wondering if I kept quiet, how many people would have experienced a placebo effect and said that it works great and makes bluetooth 10x better on AT&T...
Summary
If you happen to be an AT&T Tilt user that has flashed to an HTC ROM, this fix will work for you. If you're running an AT&T ROM, or you have no idea what a ROM is, but you know your phone says AT&T on it, it does nothing.
Does this fix the issue were bluetooth is dropped after finishing a call ?
Thanks for letting us ATT users know that it doesn't do anything. Guess we don't have this issue But on a serious note does this actually fix anything besides a supposed call dropping? I don't have that issue but of course we all have tons of issues with BT quality.
I have install the update listed above on a Tilt running the RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship Rom and the Bluetooth quality has jumped 100%. My Bluetooth stereo headphones sound great.
Thanks for starting this thread.
Awesome, thanks! I was going to ask if anyone had drop call problems as it happened to me twice last night and I happened to have my BT headset on
sirooga said:
Thanks for letting us ATT users know that it doesn't do anything. Guess we don't have this issue But on a serious note does this actually fix anything besides a supposed call dropping? I don't have that issue but of course we all have tons of issues with BT quality.
Click to expand...
Click to collapse
I have a lot of crackling background on my BT headset. Did not have that on the 8525. Also, there seems to be less functionality supported in the Tilt implementations, regarding the BT, vs the 8525 (I was running a cooked ROM though on my 8525). What i mean by that, is that I was able to use the BT buton to activate the voice dial using the MS VM. In addition, hitting the BT button twice was getting me a redial. Not anymore. I wonder is this has to do with the AT&T ROM or not? Is this a genuine HTC issue?
kaluzu said:
I have a lot of crackling background on my BT headset. Did not have that on the 8525. Also, there seems to be less functionality supported in the Tilt implementations, regarding the BT, vs the 8525 (I was running a cooked ROM though on my 8525). What i mean by that, is that I was able to use the BT buton to activate the voice dial using the MS VM. In addition, hitting the BT button twice was getting me a redial. Not anymore. I wonder is this has to do with the AT&T ROM or not? Is this a genuine HTC issue?
Click to expand...
Click to collapse
Before I switched to Dutty's ROMs, I was running the stock Tilt Rom for a few days, and then the newer Tilt ROM for a week. Both of those AT&T Tilt Stock roms gave me no issues like you mentioned. I heavily use my BT headset (Jawbone), and use Microsoft Voice Command (I very seldom use the dialer as its easier to just speak and have the phone dial for me). Pressing once on my headset would always bring up MS VC so I could issue it commands, and pressing twice on my headset always did a redial.
Now that I'm on Dutty's 7b, I have the same behaviors there too. Not sure what to tell you (other than some BT headsets don't work well with WM6, but if you were using the same headset on your 8525 then thats probably not the case).
As always... YMMV
_Alex_ said:
This file does not exist in the AT&T Tilt ROM, so it's doubtful it will harm or help to install this.
Click to expand...
Click to collapse
I checked the AT&T's 1.60.502.3 rom and it does exist. I didn't check the stock AT&T rom so I don't know if it wasn't there. I did a file comparison with ExamDiff between HTC's fix (22,490 bytes), AT&T's 1.60.502.3 version (22,490 bytes) and HTC's 1.56.405.5 version (23,899 bytes). It appears AT&T's newest rom already has the fix so anyone using the following roms should not have to apply the fix:
AT&T stock 1.60.502.3
Kyphur's XDA Live
Dutty's AT&T Variants
Custel's Series
_Alex_'s 1.60
any of DK's roms (shameless plug)
Is rapidshare the only place to get this? I am behind a firewall.
jgermuga said:
Is rapidshare the only place to get this? I am behind a firewall.
Click to expand...
Click to collapse
Cab fix attached.
akadonny said:
I checked the AT&T's 1.60.502.3 rom and it does exist. I didn't check the stock AT&T rom so I don't know if it wasn't there. I did a file comparison with ExamDiff between HTC's fix (22,490 bytes), AT&T's 1.60.502.3 version (22,490 bytes) and HTC's 1.56.405.5 version (23,899 bytes). It appears AT&T's newest rom already has the fix so anyone using the following roms should not have to apply the fix:
AT&T stock 1.60.502.3
Kyphur's XDA Live
Dutty's AT&T Variants
Custel's Series
_Alex_'s 1.60
any of DK's roms (shameless plug)
Click to expand...
Click to collapse
Just realized this while doing some diffs and was going to repost. (Microsoft file find sux ) Original post edited...
mfrazzz said:
Before I switched to Dutty's ROMs, I was running the stock Tilt Rom for a few days, and then the newer Tilt ROM for a week. Both of those AT&T Tilt Stock roms gave me no issues like you mentioned. I heavily use my BT headset (Jawbone), and use Microsoft Voice Command (I very seldom use the dialer as its easier to just speak and have the phone dial for me). Pressing once on my headset would always bring up MS VC so I could issue it commands, and pressing twice on my headset always did a redial.
Now that I'm on Dutty's 7b, I have the same behaviors there too. Not sure what to tell you (other than some BT headsets don't work well with WM6, but if you were using the same headset on your 8525 then thats probably not the case).
As always... YMMV
Click to expand...
Click to collapse
Give this a read. I have MS VC 1.6 working just fine on my Jabra BT250 after following the instructions.
you can ignore the first part about removeing the cybertron dialer or whatever.
http://forum.xda-developers.com/showpost.php?p=998205&postcount=9
I'll try it. Thx for the tip. I am not sure if this only works for 8525/TyTn (I do have the TyTn II/Kaiser)
Edit:
Tried. Sorry, did not work. Oh well. will see, but for now I wil stick with the AT&T ROM.
Hi,
there is something weird about that fix:
when the cab is on the kaiser, you tap on the file to install it.
you believe it's installed but in program files , you may find
a "kai6492_hotfix" shortcut, you tap on it and the choices are install or exit
it's seems there an identity check to be sure it's on a kaiser
"module id is kais(required kais)"
then if "equal" "ok" then install
and soft reset needed
why two install required ?
the kai6492_hotfix is still in program files after that
and last VC1.6 was working on my bt headset(but the voice recognition succeded about only 10%,i think because of audio quality when i am speaking) but i could ear vc1.6 replies ou questions)
now it is not working anymore.
when i click on the button(headset) before it was launching voice command as the harware button (assigned to it) could do it
now the same button launches the phone dialer(as i was tapping on "call"(green phone)).
ps; since that hotfix, i haven't been able, any more, to install btIO-0.6-wm5 cab
Deleted cause not worth it....
Hi All!
Currently having some issues with my Tytn.
1st problem!
Since upgrading to different Radio's - currently Dutty's V2. Hard spl 3.29
Receiving calls (incomming) only rings for about only 5 seconds. Which sometimes is not long enough for me to pick up. I cant find an option to extend the time on the phone before going to voicemail.I have had this problem since upgrading to 6.1. Tried every damn method with no luck... its driving me insane! Is anyone else having this problem?
2nd problem!
Since upgrading my Tytn to 6.1 with different roms my ringtones no longer works. when i go to phone setting and trying to select a ringtone a msg appear "this ring tone file is corrupted or unavailable"try reseting and using different roms with hard reset with no luck!
Any suggestion or how to resolve my issues ?
thanks in advance
Exactly what rom are you using?
And what radio(s) are you using?
SouthernLuke said:
Exactly what rom are you using?
And what radio(s) are you using?
Click to expand...
Click to collapse
Rom - Dutty's V2
Radio - 1.65.16.25
I also have the audio problem. It looks like it is missing some basic codecs . does anyone have a link for the standard codec for win mo 6.1
Similar issue with stock ROM
I've got the stock AT&T 6.1 ROM and I get the same issue, but not every time. It seems to happen to some callers, but not others, and I'm not sure it happens to the same callers all the time. When it happened this morning I heard one short ring, and the missed call icon lit up. The caller said it rang 5 times on her end. I was wondering if it had something to do with my forwarding settings with Youmail, but I haven't got around to checking.
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
MMS are not coming until I won't wake up the phone. This is very annoying issue.Sometimes it wakes up but more often doesn't. I'm using original newest HTC rom 2.03. Any solution and opinion for that ??
This is a known issue which HTC fixed with a new ROM 3 days ago (16/01/2009) - for network-free/unlocked Diamonds at least:
Improved Functions and Fixes
1. When you launch the Camera while the system is working on other programs, the preview screen may become black.
2. When playing a video, sometimes a portion of the video will be cut off a little bit.
3. Fixes Audio playback problem with the speaker. Specific issues: sometimes the music will turn off and on after 10 minutes, or there is a buzzing sound or no sound at all.
4. Fixes the problem of not being able to receive MMS when in standby mode.
5. When launching music via the Music tab on TouchFLO 3D, the sound may intermittently turn off for a second and come back on.
http://www.htc.com/europe/SupportViewNews.aspx?dl_id=483&news_id=44
If your Diamond is network locked the download will not work so you will have to wait for your network's updated ROM.
HTH.
I have diamond sim free unlocked I bought it directly from HTC Distributor in my country.I'm not able to download this rom. What version is it??? -can I take it from somewhere else? I have HARDSPL etc ?
MMS work with the new ROM.
But the MMS notification has no sound and no vibration, even if checked in the settings.
Did you also experience this ?
pegaz said:
I have diamond sim free unlocked I bought it directly from HTC Distributor in my country.I'm not able to download this rom. What version is it??? -can I take it from somewhere else? I have HARDSPL etc ?
Click to expand...
Click to collapse
If you are talking about Polish distribution, seems there is no matching ROM yet. As I am interested in it too, I asked HTC support about date of release for my phone. They said they'll look into it.
I put hardSPL and upgraded to the newest 2.03 rom and MMS are working but I need s2u2 to lock my phone and with that it stops working.tried all possible s2u2 settings , exception,writing to A_C etc. and nothing. I don't wanna rotate my phone,shaking,light lock etc just wanna proper normal keylock like s2u2 does...