Has anyone else come accross this? Mine started it a couple of days ago, all sound mutes, even when you move volume slider back up it resets itself to sound off. I did a hard reset after the first occasion, then it did it again. I have not installed any new software so don't think that is the issue. IF you have come accross this and found a work around that does not involve a hard reset I would be grateful for the advice.
soft-reset cures it on mine
Soft resetting does not do anything on mine, only a hard reset cures it, and then only for a couple of days, have aslo lost BT now!!! Can see my headset, pairs with it but wont connect. I have re-flashed the ROM, but problems still exist. O2 are now sending a replacement as the other one is only 2 months old (took some haggling though, O2 customer services is truely diabolical)
o2 online or retail? either way take it to an o2 shop, they HAVE to sort it for you
It was O2 online, they have now told me there is a problem with the new rom and some bt devices!!!!! Still not sure what the problems are, but am sure they are linked to TT3 as well. so will upgrade and se if that helps!
this happened to me... even a hard reset didnt fix it.
For some reason, leaving it to charge in the USB docking cradle all day has cured it
I'm such a liar!
Stupid things started doing it again, worse than ever
Have you got the broadcom BT update loaded on? If so get rid of it, thats what the problem was with mine. But then getting rid of that stopped my headset working if TT3 was loaded, so I have had to upgrade to TT5 to cure that problem!! My problems, though now resolved, all started after I did a rom upgrade from o2!!!!
There have been several problems with the 169 ROM by O2, which versions are you all using?
pug said:
There have been several problems with the 169 ROM by O2, which versions are you all using?
Click to expand...
Click to collapse
I did have, but have now rolled it back to the previous version. Even o2 admit that ver 69 has problems with BT devices!!! Wish they would check things before they release them!!
.169 killed my GPS and tom tom :'(
Crap. The problems started when I installed 169... and I've just ordered a TomTom from Ebay :'(
What should I roll back to? Or are there any "unofficial" later roms?
Hello everyone,
I have generated this post to get some feedback from those of you who may have upgraded your BAs from WM2003SE to WM5.0. I have been following all the updates rather close. All I can say is that Mamaich and Tuatara are 2 absolute heroes in my book. The latest (for those of you who are not sure of what verison of the rom is out there) TuMa v1.3 seems to be the cream of the crop at this point.
Anywho, what I would like to get from this post is feedback on the following (all of these are to be compared to WM2003SE, so keep that in mind when replying):
*Speed of the device
*Overall stability
*Issues (other than the infamous BT disconnect). BTW, we are counting on you for this, Mamaich and Tuatara. 8)
Keep in mind that I want to try to get a good comparison between the OS's. Please remember that the point is to inform people who, very much like myself, does not know squat about programming, but has some knowledge about certain things and want to upgrade to WM5 just because he/she can Personally, my SX66 works like an absolute charm with WM2003SE, but I am really curious as of the new capabilities of WM5 (and at the same time, I do not want to turn it into a brick with a sliding keyboard--- :? . --- --- --- R.I.P. MPx200 (after attempting to upgrade to WM5)
Anyway, any feedback on this will be greatly appreciated.
Thanks guys and may xda-developers live forever!!!!
Personally, I can't see many extra features of WM5 for what I use it for. The only difference for me in all honesty is the fact WM2003 is so ugly when you've used WM5.
Bluetooth is worse, not just the d/c problems but not as feature-full as yet. I miss being able to browse peoples devices etc.
The device becomes really lagged when you use Wi-fi and Media Player
Media Player has trouble with MP3's (not actually tested with wma) for the first minute or so while it buffers.
However, saying all this, I wouldn't go back. Despite WM2003's profound ugliness, the recent TuMa 1.3 works a treat and really feels secure, even securer than I felt with WM2003. The speed is excellent too, except when using Wi-Fi or using Media Player. TuMa 1.3 is also reeeaally easy to patch to your operator, all you need to do is open a command window (Start > Run > type cmd > navigate to the folder > then SetOperator <type your operator value next to it>.
Quite frankly, if you are even slightly eager to try it, you still wont really feel content until you do despite matter what we say. Just go out and try it and you shant want to go back!
Hope this helps!
Leo
now WM5 pack3.1 is very fast,i like it
My opinion is that the Bluengel gets very slow with WM5.. I'm considering to go back to WM2003 again...
My opinion is that the Bluengel gets very slow with WM5.. I'm considering to go back to WM2003 again...
is the keyboard repeating issue resolved?
alex_zou said:
now WM5 pack3.1 is very fast,i like it
Click to expand...
Click to collapse
what pack 3.1????
I guess he meant v1.3. He just got it backwards, By the way, thank you all for the good feedback. Keep it coming though!!!
Hi,
The V1.3 rom is good and it's quite fast but I have had too many problems with the phone side to keep using it. These are the problems that I've peronally had which Have Forced me to go back to 2003:
1) Recieving phone calls. When some calls me it goes through to the voice mail but if they hang up and call me again it comes through.
2) Making phone calls. When I dial someone the call is immeadtly ended then I dial again and it take about 20-30s for the call to be dial and then it end the call after 1 min
3) When i run an application and close it the running tasks tells me it's still running.
These all seem to specific to my device as there are mayeb 1/2 other people with these problems(phone), one of whom has also gone back to 2003.
Just my 2 pence worth.
Thanks
satpal
I agree WM5 is cuttier and more steady. As of the new TuMa 1.3 upgrade, I've never seen my device so glad to run a ROM yet
IT'S REally feature-packed, even when I won't use all of the features. It felt very strong, stable and FAST!! (I don't notice the slowliness some others say, moreover it feels faster than with 2003), more than any other ROM I've tried to date. WOW WHAT A JOB!!
I'm having a problem with the phone where I can not get any sounds from the phone making, nor receiving calls. I can not hear or be heard using the loudspeaker. Using the Bluetooth headphone works, though. But, bluetooth is sooo weeak on this device (my impression) that for me is not really worth it. I was using a Nokia phone (80something) and the Bluetooth stack felts very strong and stable and, at the very least, you could hear the sound clearly, without the scratchs and noises I'm used to sort in a bluetooth conversation using my BA.
That's why I revert my BA to WM2003, to check if the problem was because of WM5 but, now, the problem persists, and I don't have so many other options...
Just a thought: if you wanna better Bluetooth thingie, don't go WM5: M$ stack is a crap... lacks everything...
it's definitelly worth trying... I like the usability and keyboard navigarion better... in 2k3, it is impossible to even close a simple gprs popup without touching screen where as in wm5 you can simply press right arrow key and enter to close it... there are plenty of small things which make it more usable for day to day usage
plus It gives you the courage to upgrade to a more steadier device with wm5 pre installed... like I bought universal after using BA for couple months
[edit] the WM5 version I tested was 1.3 TuMa.
My QTEK 9090 really didn't like WM5.
I love the look and feel, and particularly the MSN integration, but had to go back to 2003SE.
Do tell me if I missed anything that would fix the issues below and allow me to go back to WM5 :-
1 - SLOOOW. Some apps more than others, for example reading an SMS takes 5-6 seconds to open a 30 character message.
2 - Phone. Keypad very slow. Audio cuts out halfway through a call, seemingly at random.
The second point is what forced me to downgrade. If my smartphone is not a phone, then it's no use to me.
The last test I did with WM5 was using the 1.13 radio ROM. I've since updated it to 1.15. Has anyone seen any WM5 improvement with higher radio versions on PH20B hardware? I ask because I've been through the reflashing process so many times, I realise I am pushing my luck and will end up with a brick sooner or later.
Updates are in BLUE
Okay, time for a long post... (and please remember this is all subjective, and personal experiences, your's may be different!)
Preamble:
I've had my BA for a couple of months now, prior to that it has always been PalmO OS devices which I loved, but I wanted a phone enabled device and the Treo was just too expensive to justify it... so ebay beckoned and £100 later I was a proud owner of an O2 XDA IIs...
I'm a fairly heavy user of my PDA's I use them for all my network admin, work documentation, mail on the move, a heavily laden calendar and everything else a busy professional with a family does... with loads, and loads, of travel!!
First thoughts:
I was, to be honest, dreading the move to M$, I have always been a promoter of opensource, Palm, and anything other than the big M, but I was pleasantly surprised... with relativley little pain I got into the WM2003SE way of things, and after a quick read of the Wiki, I cooked my own ROM and had an O2 device which worked really well... I could use my BT headset as stereo headphones or a headset, while connecting to my GPS, I had my Gmail, O2, Hotmail and other accounts set up, I could chat with Skype, GoogleTalk, MSN and ICQ, I had a WiFi sniffer, and all the other trappings as well as a GPRS connection for TomTom Traffic etc... and the media capability was cool, TCPMP worked really well, and with a 1Gig SD card I could take a couple of movies/TV episodes for the journey... in short, I no longer had to worry about taking a laptop on the road.
But that wasn't enough, I was reading about these WM5 ROMS and felt that, after being pleasantly surprised with WM2003SE, it was worth a shot... over the last few days I have tried several ROM's and they all have up/down sides... what follows is a (not so brief) summary of my experiences...
I load up my BA fairly heavily, and I had specific requirements... speed, callerid, space, preferrably A2DP, and again, speed!!
TuMa 1.4 (MS BT Stack):
Some see this as the 'Daddy' of the WM5 ports and I must admit, with one major bugbear, this is an impressive ROM... it includes a lot of stuff in the build which some might prefer was left out, but for the basic user it's helpful to have some of these...
(A Really COOL Boot Logo!!)
TotalCommander
PocketRAR
Extra Games
Cyberon Voice Dialler
GB-Soft Tweak
vBar
pShutXP
IP Utilities
Pocket FTP
SMS Name Notify
ClearVue PDF
BT Headset Today Plugin
BT Stereo Control
Device Lock Today Plugin
and other bits and bobs...
This may well be considered as a 'bloated' ROM (but remember they are all installed in ROM, so no space is taken up from your 'own' space), there is an Ext_ROM option, from SD Card, in this ROM so the memory works out like this... 60MB Storage (- whatever you set up as an Ext_ROM) and 91MB Program Memory... you also get a 32MB Temp_Drive ( I assume this is like a RAMDISK?)... available on a clean install is:
Storage: 57.62MB
Program: 72.53MB
TEMP_Drive: 31.85MB
Total: 162MB (Storage & TEMP_Disk available for app install = 89.47MB)
Out of the Box:
BT: Works very well... including A2DP, I had no problems, whatsoever with this BT Stack/Setup.
WiFi: Again no problems and no reset once I'd applied the Reg Hack.
Base OS: This is where, for me, it all falls apart... even with eveything else working like a dream, the 'Pictures & Videos' app in this build just does not work, at all! This means that the CallerID functionality is kaput... I can't live with this, I love the ability to 'see' who is calling, I have many, many numbers in the work category, and being able to put a face to a number beats having only a name any day... other than that this ROM works really well, and the additional install space means I can have all my apps installed without the 'critical' low storage warning... in addition to this another glitch I have come across is 'sticky' buttons... both the D-Pad and the hardware keyboard can result in stuck keys/repeated entries... BT Voice Dialling works with Cyberon, and even better with MS Voice Command (if you hack a little), and with the A2DP profile the MS option works through the BT headset rather than the PDA speaker,,,
Ivan V4 R3 (WidComm BT Stack):
Built as a 'clean' ROM, this one really comes with no bells or whistles, included are:
BT Headset Today Plugin
Cyberon Voice Dialler (I Think!)
and apart from the Base OS stuff, that's about it!
This is a relatively speedy ROM on first impressions, but it slows dramatically down when loaded with apps... you can setup an Ext_ROM with this one, or use the full 60MB as storage... there is no Ramdisk or Temp_Drive option so you get 60MB Storage (- whatever you set up as an Ext_ROM) and 123MB Program Memory... available on a clean install is...
Storage: 57.64MB
Program: 98.40MB
Total: 156.04MB (Storage available for app install = 57.64MB)
Out of the box:
BT: works okay, although there is no A2DP functionality,but I can connect to my headset and my GPS... (which is a big thumbs-up for me). I have experienced a few of the system restarting glitches, but not the BT not restarting/dropping out with this ROM so that's an upside.
WiFi: Connectivity is okay (typical BA signal strength) and once you apply the 'ResetOnResume' Reg hack then it works very well, I have had no dropouts or non-restarts with it at all.
Base OS: A big upside for this is the Pictures & Video, it works! This means I can use the CallerID function on the WM5 dialler, which I do, extensively!!
Logout V5.4.03 (WidComm BT Stack):
Read great reviews of this on the forum, so thought I'd give it a bash... included are (if you install the Ext_ROM):
Cyberon Voice Dial
ResInfo
Task Manager
Device Lock Today Plugin
TuMa Keyboard (I think, although it looks nicer!)
Just installed this one today... first impressions weren't very good as many of the apps which were meant to be there couldn't be found on startup... then I realised I hadn't cleaned my Registry Hive before the Flash!! The speed in this one is blinding! Compared to both of the others this one is as fast as 2003SE, again, it uses a Ramdisk so you have added space for installs, and it can also use an Ext_ROM, so you have your choice... so you get 60MB Storage (- whatever you use for Ext_ROM), 93MB Program Memory and a 32MB Ramdisk... available on a clean(ish) install (I installed the MMS/Album/Voice Dial and Resinfo Cabs) is...
Storage: 52.8MB
Program: 71.9MB
RAMDISK: 31.8MB
Total: 156.6MB (Storage available for app install = 84.6MB)
Out of the Box:
BT: What there is available works fine... but no A2DP... not experienced any restart issues yet, but it's ealry days
WiFi: Again, all seems fine
Base OS: As stated above this one is blindingly fast... so much so that I actually forget it's a ported WM5 ROM at times, the Pictures & Videos app works, so that's a biggy on the plus side for me, everything seems to be ticking along quite sweetly...
UPDATE 1: Logout ROM seems to lag for a while after installs of S/W... but it settles down again, had one occurrence of s-s-s-stuttering keyboard, but nothing major, and no 3s delay on phone ring, even without reg hack
Artz (WM5_ArtZ_upgrade_WWE_1.7.1.3400_SDCard)
Iloved this ROM at first sight, it had the Stereo Audio BT profile without any updating, it was clean, smooth and fast, but then I tried using it... I'm not sure what went wrong but it just didn't 'gel':
BT: As stated this looked good from the outside, and it did recognise both my GPS and my headset, and it would connect with both, but, andit's a huge but! It wouldn't get any services from my headset on reconnection, it wouldn't recognise my headset as stereo (even though it though it would recognise the profile?) and as vor a 'normal' BT headset, it just sent my i.Tech headset haywire, beeping, pinging and ringing constantly... I couldn't stop it!
WiFi: Again, issues with this... no matter what I did, this ROM would not reconnect to my AP after a reset or power down...
Base OS: At face value this ROM was excellent, it had all I needed to start setting up my BA, and the option for Ext_ROM from an SD card is great... but with the issues above, and the spped at which it 'slowed down' with apps added it was unworkable
Obviously I will update each of these as I continue to 'tinker'... and wait for Logout 5.4.5 or TuMa 1.5, if either of these fix the little issues I've mentioned (A2DP for Logout and P&V for TuMa) then I'll be in BA WM5 Nirvana!
In summary, heres a little overview (TuMa, Ivan, Logout):
Speed: 3, 2, 1 (And then some!)
Apps: 1, 3, 2
A2DP: Y, N, N
P&V: N, Y, Y
Voice Dial: Y*, Y, Y
Available Mem: 162/89, 156/57, 156/84
*TuMa's is the only ROM I tested with MS Voice command, so BT Mic+PDA speaker for the other two, complete headset for TuMa.
So there you have it... a 'brief' insight into a few days of WM5 experience, personally I'm going to stay with Logout's ROM, the speed is unsurpassed, it has ample space for installs, I get my CallerID due to P&V working, and if there's one thing about TuMa's ROM I could do without it's the 'free' installed apps... I don't use TtlCmd, I don't use Pocket FTP and I don't use Pocket RAR (Resco Explorer covers those 3 and then some), I use Tweaks2k2 to apply most of my hacks, so the GB-Soft Tweak is mostly redundant, and I use Wisbar instead of vBar... but it's a personal preference thing... in the end, it's up to you... (I now use Total Commander loads Thx TuMa)
I'll update this as I try other ROM's or find other benefits/problems/fixes...
*** See my other post in this thread dated 23/06/06 for other issues which I have come across with WM5...***
Logout 5.4.05
I had high hopes for this ROM, 5.4.03 was nearly there, and built on the best of TuMa and Ivan's ROM's...
Out of the Box
An incredibly fast ROM, by far the fastest in basic form compared to all the others available... there are many little tweaks in the software and add-ons included as standard which are useful, such as the SMS Alert Fix etc. It's up to you to make the Ext_ROM, but this is good for 'tweakers' as you can build it to your liking.
BT: Basically, a nightmare! I believe this uses the WidComm stack and as such I can't get the A2DP to work, yes it recognises my Headset, and yes it says there is a 'Wireless Stereo' capability, but when you try to enable that profile it says 'No Device Found'... in addition, and I'm not sure if this is due to the BT switching off fix, my device was switching on at least once every two minutes!!
WiFi: I didn't get round to test this for the reason above, and also the power up issue causing me major headaches.
Issues: I had too many issues with this ROM to detail them all, a short list would be:
No A2DP
Random Power Ons
Software Not Installing Correctly
Software Not Removing Correctly
Software Not Running (Tweaks2K2, WiFiFoFum and others)
BT Dropping Out (While Powered Up)
OS Locks Out (Random, No Common Factor)
And the speed once a few 'heavy' apps are installed deteriorates dramatically...
I have now resorted to TuMa 1.4... I know I have stated previously that I couldn't use it, but I have found a workaround to the Caller ID issue, and the BT works very well (including A2DP), with both 1.13 and 1.15 Radio ROM's, and I have not experienced one unwanted power up, and the BT has stayed on for ages regardless, in addition as long as I don't install WisBar the speed of this ROM beats all the others hands down once all my other apps are loaded. Also, I have had the BA on for 7 hours now, using bluetooth for 1 hour solid in the gym for music, making several calls, setting up my software etc and the battery is still at 75%... not bad at all in my books.
As I said earlier, bring on TuMa 1.5!
Now this is useful! Thanks for sharing and I give my thumbs up for updating the first post as you go on trying.
I'm very happy to read your review.
I'm surprised you did not mention the battery drain (false indications that your battery is dead, when in fact it is not) with TuMa 1.4
Great Work!!!!
G8 work. Good detailed description which i am sure a lot of people will appreciate. i
Logout Rom = Speaker phone icon does not disappear after call
WMP 10 crackling noise for first 30 -60 sec of song
@snapper - Can't say I noticed it, but then again, whenever I sit down for more than 30mins, my brick goes on to power anyhow...
Why does everybody forget about ArtZ's ROM? :/
http://forum.xda-developers.com/viewtopic.php?t=48215
Not forgotten, just not used,,,
If you read the last couple of para's I do state that I'll get round to Artz's and update the post...
Yup, missed that (was in hurry, checked only the explicitly enumerated ROMs :| )
The Artz of ROM's
Hmm, d/l'ing this one now... expect an update over the next day ot two... encountered a few 'glitches' with the Logout ROM tday, nothing too major, but enough to get my goat!
Is there any reason why, with certain ROM's, certain apps decide my BA is a VGA device? This has cased me no end of trouble today, and I can't for the life of me, work out the reason...
Anyway, expecting good things from the Artz ROM, just read the forum a few mins ago and notice it's a 'clean' ROM with the BT stack! Could be I get my wishlist... let's just see if P&V works...
Mad props for a very well written article.
I've gone down the wm5 road the last week as well. I tried tuma 1.3, tuma 1.4, ivan, and now i'm on logout. I was wondering how extensively you tested the wifi? I have had problems with it on all the roms.
The issue happens when wifi is ON and the device shuts off after 1 minute. Then the device powers back up when i press the power button and the wifi will continually try to reconnect to the AP that it was just on but will never make a connection. Clearing the settings on the connection doesn't work and it inhibits the ability of the device to detect any new networks.
I was wondering if you had any problems like this and if resetonresume fixes this?
Also i'm a little confused about the location of the storage memory and the programs memory in the file structure of wm5. Could someone explain this or send me in the right direction? (aka. search terms or thread link)
willpower102 said:
Mad props for a very well written article.
I've gone down the wm5 road the last week as well. I tried tuma 1.3, tuma 1.4, ivan, and now i'm on logout. I was wondering how extensively you tested the wifi? I have had problems with it on all the roms.
The issue happens when wifi is ON and the device shuts off after 1 minute. Then the device powers back up when i press the power button and the wifi will continually try to reconnect to the AP that it was just on but will never make a connection. Clearing the settings on the connection doesn't work and it inhibits the ability of the device to detect any new networks.
I was wondering if you had any problems like this and if resetonresume fixes this?
Also i'm a little confused about the location of the storage memory and the programs memory in the file structure of wm5. Could someone explain this or send me in the right direction? (aka. search terms or thread link)
Click to expand...
Click to collapse
I had this problem on my BA with 03se just a couple days ago so I don't think its related to just 05. I used the vx ip utility to release and renew the IP and I believe that fixed it.. I think it has something to do with the DHCP reservation
Great guide, very handy for begginers. Should be sticked :idea:
willpower102 said:
Mad props for a very well written article.
I've gone down the wm5 road the last week as well. I tried tuma 1.3, tuma 1.4, ivan, and now i'm on logout. I was wondering how extensively you tested the wifi? I have had problems with it on all the roms.
Click to expand...
Click to collapse
Using wifi on my BA for over a wk everyday @ work & home, no such problems faced with Ivans ROM, have not tested logout, but will do that this wkend.
Guess its a hardware issue! again, thats just a guess
Yaantra
Great info!
This is great info and was very useful to me. I am on WM2003 and have not yet upgraded. With 2003, my only issues are that MS voice command won't work via the BT headset, the 80211b wireless requires a reboot to turn on and off, and the phone requires a reboot perhaps once a week. Otherwise it works well and I want my 2005 to be equal or better. I thin TuMA 1.5 will be it.
Has anyone actually got a working MMS Client primarily for Logout's new ROM
WiFi Issues...
@ will...
Yes, I noticed on first flashing that, even though I had entered the settings for my AP, when the system resumed then it would not reconect, after using the resetonresume reg hack all was well...
I also noticed this on Artz's ROM which I will be adding to my first post over the next day or two, as well as a few other points/comparisons...
All I will say at the moment is that all has not been a bed of roses in my WM5 world and backward steps may be ahead... (unless Logout 5.4.0.5 or TuMa 1.5 are here soon... and they deliver on our expectations!!)
Tuma / Logout roms
sounds to me that you will be heading back to wm2003. main reason for saying this is how you use your pda. Your demands are high (as they should be) and you use your pda very heavily (wifi, bluetooth etc) hence functionality and speed are your highest priorities.
having said all this i think and hope tuma/logouts new roms will hit the spot (i have faith).
FYI just upgraded to 1.15 radio and the sound quality is good!!!!!!
Issues, concerns and resolutions...
Well, the first post will be updated later today, but just as a heads up, I experienced BT issues with all ROM's except the TuMa 1.4, and various other 'niggles'... issues which I couldn't live with unfortunately:
BT: I like the A2DP functionality, I use GPS heavily and need them to work every time, with the other 3 ROM's I've tried I experienced various problems such as BT not reconnecting to paired devices, BT connecting but causing mayhem with my headset (in Artz' update later), crackly sound, dropouts, no phone, no voice dial, ad infinitum...
WiFi: This worked fairly well in all the ROMs, I managed to get all 4 tested to reconnect after standby/soft reset/battery change etc.
Battery: The experiences I had with battery life weren't actually that bad, yes it was heavier than 2003SE, but that's to be expected... my main issue was that on a couple of the ROM's I experienced the 'no Radio ROM' syndrome after a battery change, not major, but a pain in the butt anyway!
Usage: These are all ROM's that are designed for 'newer' machines at their hearts, and as such, as soon as you load up some heavy apps the whole system starts to drag, I cannot afford to wait over 1 minute for my PDA to boot after soft reset, or 30 secs for an app to open... and I certainly don't like it to be 'hit or miss' if an app opens when I ask it to!
Summary: I really love the WM5 interface, the smoother way that notifications are dealt with, the 'soft-menu' buttons are a godsend, the built in GPS management, and any of the other 'tweaks' MS have included make it a PDA users dream, unfortunately, at the moment it's just that, a dream... the BA is not 'Designed for Windows Mobile 5' and until TuMa, Logout, or Artz [I believe Ivan has left for a new device ] manage to get it 'right' (and major kudos to them all for their perseverence in what must be a most frustrating endeavour) I, as an everyday, heavy, PDA user will remain with WM2003SE... I'm not happy about it, but needs must
Re: Issues, concerns and resolutions...
spkr4thdd said:
Usage: These are all ROM's that are designed for 'newer' machines at their hearts
Click to expand...
Click to collapse
Just FYI that is incorrect, Artz and Ivan's ROMS are based on an actual BA BEAT build of WM5 that was made by microsoft, that has been patched and edited with later versions of the components, whereas TuMa and Logout's Rom are based on a Wizard ROM.
spkr4thdd said:
the BA is not 'Designed for Windows Mobile 5'
Click to expand...
Click to collapse
Read up, Basically every WM2003SE device has a WM5 Version made for it, however the operators in thier infinate wisdom decided that they didnt want people having WM5 on thier 'old' phones and would rather that people brought new ones.
Re: Issues, concerns and resolutions...
Midget_1990 said:
Just FYI that is incorrect, Artz and Ivan's ROMS are based on an actual BA BEAT build of WM5 that was made by microsoft, that has been patched and edited with later versions of the components, whereas TuMa and Logout's Rom are based on a Wizard ROM.
Click to expand...
Click to collapse
I stand corrected... I was under the impression that all the ROM's were 'ported' from different devices, I believe that was the case originally wasn't it?
Midget_1990 said:
Read up, Basically every WM2003SE device has a WM5 Version made for it, however the operators in thier infinate wisdom decided that they didnt want people having WM5 on thier 'old' phones and would rather that people brought new ones.
Click to expand...
Click to collapse
Read my post!! WM5 wasn't released when the BA came out, so it was built around WM2003SE, the fact that a ROM became available, albeit not publicly, doesn't mean they redesigned the handset!
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