Related
I just want to warn everyone the 2003 rom has many problem, since it is an internal development version. Here is the bugs I found right now.
1.Maybe it's not a "BUG". It miss the Wireless Modem which many people asked for a long time.
2.I tried Windows Media Player and Pocket Music 1.5, both can't turn off the display, which means you have to leave the display on when you listen the music. If any one can turn off the display , please tell us, may be I got some software conflicted.
3. 2 "Power" Logo on the setting menu, but the have different content. It looks like one is the new power setting tab, but it didn't provided some old fuction in the old power setting tab, so O2 kept the old one.
4. The SIM Contacts (Sim utility provided by PPC 2003) is horrible.It has NO fuction except copy the SIM card address to the phone.
5. YOU MUST NOT install Batterypack 2003 on the phone. It looks like working after you install, but your machine will never boot up after a soft-reset except hardreset the phone. (It is PPC 2003 / Battery Pack 2003 problem, not O2 / HTC's fault).
6. You will never know if the current signal support GPRS or not. It will not display the G logo in the "signal bubble".
Please add the list if you got any problem with the new rom.
If the bug I listed can't stop you install the new rom, go ahead :twisted: .
Moreover, it's not an official / final version rom, if you want stable rom, stay with XDA SE 1.1 rom.
Sorry for my horrible english~
1.Maybe it's not a "BUG". It miss the Wireless Modem which many people asked for a long time.
Click to expand...
Click to collapse
Not a bug. it was a feature added by xda-developers.
2.I tried Windows Media Player and Pocket Music 1.5, both can't turn off the display, which means you have to leave the display on when you listen the music. If any one can turn off the display , please tell us, may be I got some software conflicted.
Click to expand...
Click to collapse
tried it with windows media player and got the same thing. Pocket music 2.0 refuses to work at all
6. You will never know if the current signal support GPRS or not. It will not display the G logo in the "signal bubble".
Click to expand...
Click to collapse
when i have grps signal i have G displayed in my bubble.
Alex
kalex said:
1.Maybe it's not a "BUG". It miss the Wireless Modem which many people asked for a long time.
Click to expand...
Click to collapse
Not a bug. it was a feature added by xda-developers.
Click to expand...
Click to collapse
No, it was added in the new ROMs by Qtek and O2. Whether it's a Microsoft or HTC tool I don't know, but it's definitely not ours...
XDA developer Peter Poelman,
didn't know that. i thought it was urs.
PPC 2003
Hi all
Only autentization to VPN over cetificates is good feature for me.
Another features :?
XDA-dev ROM 1.1 is best solution
It seems the "screen toggle" bug (can't switch off the screen probelm) can be fixed by install the PocketMusic 2.0 Bundle plus the 2.0_4_3 fix.
I can see a hotkey to turrn off display with 2.0 version.
Moreover, the "auto turn off display" fuction still works on the PocketMusic 1.5 Bundle version, and 2.0 too.
It's so strange the PocketMusic 2.0 works but WMP 9.0 doesn't work.
I'm happy with the PPC2003 now. If we have to wait to long beforce the official release, will XDA-Developer release an extra SE version based on the current version of PPC2003?
It still suffers fron some sms issues, i cant get a delivery receipt, and also the time sent stamp is actually the time received.
The auto config does not work, so as a result i can't get gprs working...
(Anyone know the settings for o2 uk ?)
All in all though a good upgrade !!
i loaded the 2003 rom and only have minor issues.
1. when connecting the network says voicestream instead of t-mobile.
2. connection seems slower even with the accelerator proxy turned on. the connection used to be as high as 40k according to spb gprs monitor. now i haven't seen it break 20k.
Unit no longer powers-on when placed in sync cradle; In order to sync the unit I now have to either (a) make sure unit is turned-on before placing it into cradle, or (b) place powered-off unit in cradle, then turn power on.
Not a major issue, but certainly a back-step in functionality. Anyone else notice this?
I'm using a TMobile XDA with updated ATT radio stack and PPC2003.
To Dondi :
I have your issue too, but I didn't think it is a problem for me, since I hate the machine suddenly power on itself when I am charging it.
i guess it s even better for the screen not to be lighted all the time when plugged on the cradle
Hey all. I just installed WM2003 PE. It looks and feels great. I only have the following comments:
I have installed the ROM on my Qtek 1010.
1. I can't seem to see any MIDI ringtone support on this one (probably because it's not a final release)
2. I'm still running on my old Radio Version 3.23 and my GPRS resumes connection seamlessly after calls - which is great.
3. I've read somewhere that applications will be visible on the 'taskbar' when running, but do not get this functionality also. No worries on this though, because 'Switch' works fine with WM2003.
4. Still no ability to add custom Operator Logos.
5. Hooray for the 'Busy' tone and indication!
SPB GPRS Monitor works fine with 2003. I also wanted to know from the rest of you guys: Do you have to manually initiate GPRS connectivity after a soft-reset? Or does it pick up your default connection and auto-connect?
To killercheung and Cyberb0b: You've given me a new perspective on the XDA not automatically switching on when placed in the cradle in the off state -- I appreciate the benefits you pointed out.
Also, I did notice that when I initially loaded the Ozone beta (prior to upgrading radio stack) the GPRS symbol was being displayed regularlyand I had no problem connecting with GPRS and getting decent performance (> 20 Kbps). However, after I convinced myself to "go all the way" and also perform the Radio Stack update, I now rarely see the GPRS symbol, and GPRS perfirmance has dropped to the 1Kbps level.
Now I wonder if Ozone also updated the radio (which I perhaps subsequently "downgraded" by loading the ATT RSU). Can anyone shed some light on this?
for what i ve seen Ozone does not modifiy the radio stack, you have to upgrade it yourself useing for exemple the O2 upgrade version 4.21.
As far as i m concern using GPRS in France with Orange as operator with SE 1.1 or with ozone i have the same brandwith capacity depending on the network trafic and my position, between 10 and 30 Kbps, i use SPB GPRS manager to monitor my connexion 24/7 and see what is my data consumption day by day (it also allow me to shut GPRS off without switching the phone off).
by now using ppc2003 for about a week, i have no gprs shut down, except going out of coverage area, we poor french are not full gprs anywhere, but it works pretty good in cities.
on thing i ve notices that i guess is significant :
however it is said that Gprs connexion isn t dropped any more when an incoming CSD call start, that is true but the transmissions are stopped.
I mean i can not send or recieve data while talking on the phone line. But this is not due to the software i guess it is due to the number of channels aviable on the device usually it s 4 + 1 or 4 + 2
whereas phones like SE P800 have 6 + 4 channels allowing the to really exchange data while using CSD channel.
But nevertheless it is a good upgrade cause i do not have to kill my irc session while talking on the phone (just have to hang up fast before the irc timesout ) ).
Hi All,
I thought I should start a new thread about VoiP/SIP in WM6 and the ROM "plague".
Up to now I have tried every possible "VOIP".cab on my Advantage (Athena) X7501 with partial success. I can call through 3G/GPRS and WiFi BUT no sound on my side. I know this has been reported many times, but no solution yet. What is annoying too, is that the original "SOLVED" thread is so big and chaotic that practically there is no discussion any more.
I have also tried swapping rtcdll.dll, changed registry entries in HKLM/Comm/RTC and HKLM/System/Voip without any progress on the sound issue. Additionally I have changed the ipdialplan.xml just to activate the "+" international global calling, but my ipdialplan.xml seems not to be taken into account.
I am really fed-up with this, also with WM6. WM6 is slow, far worse than Windows CE 2003 (1st edition).
I installed Skype instead. This works with sound (yeaahhhhh) but quality is crap. I could barely listen to my party and then switched back to my classic Toshiba E800 to enjoy magic quality!
The bottom line is that I think all this is ROM dependent. I don't know what MS, HTC and operators do in every country, but all these problems are very strange. It looks like the VOIP is sabotaged somewhere deep in the registry.
BTW, my Athena X7501 bears the original (latest) WM6 ROM as "cooked" by HTC in the US.
Hope my experience will save some time (and money) over 3G/GPRS connection attempts...
Hey people,
Yesterday I got fed up with my iPAQ 910c, put it on craigslist and sold it for not much less than what I originally paid for it.
Mainly, the lack of Cell-ID support from HP was really annoying: all kinds of times when I wanted a quick sense of where I was from Google Maps, I'd have to wait a long time for a GPS fix and make sure I held the phone out with a clear view of the sky. Not exactly convenient. And even though Rogers is selling the iPAQ 910c on contract, HP hasn't provided an rilgsm.dll with Name Display (CNAP) support. Stupid.
That, and WM6.5 brings with it (in my opinion) features that really prefer a higher-res screen. And a directional control more advanced than a scroll wheel. And a light sensor to automatically adjust brightness (as opposed to me having the 61x/91x brightness control on hotkey, lol). And more speed.
...so I'm getting an Xperia X1.
It was fun cooking with y'all, and so I leave you in the capable hands of monte & keyx. Adios amigos!
Wow!
Sorry to lose your development skills on the 910 - I always enjoyed your ROMs.
Happy trails!
many thanks to you..
i'm still running your WM6.5 on my ipaq.
but, i'm also wondering to replacing my ipaq with xperia. how does xperia compared to ipaq 912, i just want to know from your point of view.
thx
So far it is awesome - the 800x480 screen is amazing with WM6.5, and the device seems to get both better speed and battery life than the iPAQ. That, plus the Xperia has just enough less width than the iPAQ for me to wrap my hand around when I'm carrying it, running, etc. Not only does Cell-ID provide instant estimates of my location in Google Maps (which itself looks amazing at WVGA), but GPS fix seems to take a fraction of the time it did on the iPAQ.
I can't do one-handed QWERTY typing as quickly or easily as with the iPAQ, but with two hands I don't notice much difference. The screen doesn't pick up nearly as many fingerprint smudges as my iPAQ did. And the optical trackball functions more like the little "pearl" on Blackberries, something HP should have put in the middle of that giant D-PAD.
But basically the screen is the biggest improvement: I went from seeing like 3 titanium homescreen entries on the ipaq (with WM6.5) to now seeing all of them at once. That's huge. I nearly broke even on the upgrade too - bought the iPAQ on eBay this January for like $240, sold for $200 on craigslist, and just got the Xperia from Rogers on a 3-year contract for $225.
Thankfully, there is a large ROM cooking community already in place for the Xperia, so that takes some of the pressure off. My understanding is that cooking for the HP devices is relatively easy once the tools exist; the SD-Loader isn't checking for signed ROM images so no low-level device unlocking is required. HTC phones are a different story - even the ones sold "SIM unlocked" still come with a bootloader that won't accept custom ROMs, and certain XDA gurus have to make a "HardSPL" modified bootloader before custom ROMs can be flashed. Case in point: the poor suckers with the Palm Treo Pro are still without any custom ROMs whatsoever, because the phone isn't quite popular enough to have reached somebody who can make a HardSPL (they're working on that).
Once a HardSPL exists, though, HTC ROM development tends to explode because they keep using the same underlying hardware. Thus the Xperia light sensor is the same as the one on the Touch Diamond and Touch Pro; the radio hardware is interchangeable with those phones too. Moral of the story: check out the state of ROM development before you buy.
soory 2 hear u are out of ipaq roms u had good ones
anyway good luck with your new device and try 2 keep a look 4 plastic cracks
i 4 myself like the front KB like the 6900 900 i780...
i had the ipaq 800 (data messenger) with light sensor dpad sensor very fast gps...(device generl speed slower then the 900 and have no SR )
had some htc devices with sliding hard KB but on such devices i found myself using software KB (if u sms or need somthing short u will see it 2)
the screen must be a great thing
enjoy and tnx 4 all
Good look with the new toy.
Noooooooo....how dare you betray us front facing keyboard lovers!!!
It was good having your roms and knowledge...best of luck with the Xperia!!
I'm currently waiting for a replacement 910c from Rogers right now...my USB connector stopped working Maybe I'll just replace my phone altogether...but...I must have WM, front facing keyboard, gps, wifi, and 7.2mbps dl speed
We'll see what comes out...Samsung looks like it might have a good rival
Again, many thanks and good luck!
Well, congrats on the "upgrade" - I thought someone on Rogers would for sure go for a quad-band phone, but maybe the tri-band will work well enough for you where you are.
By the way - the "cell ID" thing is being worked on, and I thought I had a quick solution involving "cell broadcast" settings in the registry. It's probably only weeks away from being fixed. Keep checking back to see if we get it right.
gfinockio said:
Well, congrats on the "upgrade" - I thought someone on Rogers would for sure go for a quad-band phone, but maybe the tri-band will work well enough for you where you are.
By the way - the "cell ID" thing is being worked on, and I thought I had a quick solution involving "cell broadcast" settings in the registry. It's probably only weeks away from being fixed. Keep checking back to see if we get it right.
Click to expand...
Click to collapse
lol I'm in downtown Toronto, but the Xperia is actually quad-band GSM (850/900/1800/1900) and tri-band UMTS (850/1900/2100). Which is exactly the same as the iPAQ.
I wish you the best of luck getting the Cell-ID thing working. I'm mostly just pissed that after all this time Inventec hasn't made a few simple changes to their radio firmware, and HP has the nerve to blame the network carrier in their documentation!
Anyway EREZYAD is right, these past few days my text entry has been split about 50-50 between the software keyboard in portrait mode and the hardware keyboard in landscape. Neither are quite as good as the iPAQ 910c, but the combination is sufficient.
so long benjaminries, never used your rom's but always sad to lose a chef
gfinockio said:
Well, congrats on the "upgrade" - I thought someone on Rogers would for sure go for a quad-band phone, but maybe the tri-band will work well enough for you where you are.
By the way - the "cell ID" thing is being worked on, and I thought I had a quick solution involving "cell broadcast" settings in the registry. It's probably only weeks away from being fixed. Keep checking back to see if we get it right.
Click to expand...
Click to collapse
Whats up with the "cell ID" issue? Did you get fixed? Can you explain whats wrong with cell ID on HP iPAQ 910c?
zmadaric said:
Whats up with the "cell ID" issue? Did you get fixed? Can you explain whats wrong with cell ID on HP iPAQ 910c?
Click to expand...
Click to collapse
The fact that the 910c doesn't seem to work with Google Maps "My Location" function without using GPS.
gfinockio said:
The fact that the 910c doesn't seem to work with Google Maps "My Location" function without using GPS.
Click to expand...
Click to collapse
This is corroborated by other apps like Navizon that also don't work on the HP 91x/61x.
Basically, the RIL interface specified by Microsoft has several API functions that apps are supposed to be able to call which should return an ID code that identifies the cell tower to which the phone is currently connected. As far as I can tell, the OEM (HP) is supposed to adapt firmware and corresponding WinMo driver files like rilgsm.dll from the radio manufacturer (Qualcomm) to meet Microsoft's specification; however some OEMs like HP "choose" not to implement these APIs such that requests by apps for the Cell ID return a constant error code.
There appear to be two alternative methods of retrieving the cell ID that might have given us hope for HP: (1) broadcast channels and (2) serial requests. But the first option is unhelpful in North America where GSM carriers don't use broadcast channels, and the second option (when I tested it) didn't seem to work either - basically there are a number of direct modem commands that can be sent over COM ports to ask for the cell ID. The results of my testing suggested that the problem lies, at least in part, within the radio firmware itself - perhaps provided to HP by their main manufacturer, Inventec.
To me, the fact that HP/Inventec didn't fix these problems - despite mass outcry by users - suggests that while HP is still patching up what they can on the software side (releasing ROM updates for keyboard and sound issues), whoever created the radio firmware (Inventec?) has sort of walked away, or at least has no stake in keeping existing customers happy.
What the xda-developers community knows about and is able to do with actual HTC hardware, by comparison, is huge...
You did the best bro. It is nearly 2010 and I believe that any other phone after that time should have a BIG scren.
Hi
Have a Touch2 T3333 which has ROM version 1.28.401.4 (66092)
I bought it as I wanted a Windows phone originally for complete Exchange sync.
However I'm on the verge of just giving up with it and buying another handset, as it's just so riddled with bugs and problematic.
I thought I'd give it one last go and see if there were any updates for the OS to make it usable.
The HTC website does have an update for it which looks significantly newer, however when I try to download that and put in the S/N of the handset I get told that it isn't suitable. There is no way on there for me to part-patch up to an intermediate version then to that version.
I'm not looking for "tweaks" as such, I just want what's there to work (the weather bits, the active sync, Opera not to crash all the time, not to have to launch IE twice every time, the phone to switch properly between WiFi and 3G, YouTube to detect the network connection properly, Audible Player to sync properly, not to have to take the battery off the back and put it back on about once a week every time it locks up.. the list just goes on..)
I'm not sure if these are general issues with Windows mobile itself which has a kind of beta not-quite-finished feel to it and no version really works properly, or if the update would solve these problems.
As I'm so frustrated with the thing I don't mind all that much if I end up killing it completely and then have to throw it in the bin and go out and get an Android based replacement.
I've read about ROM updates on here and I can see in the Mega - ROM - Hotfix thread there's a ROM "WWE Europe - 1.28.401.4" which I'm guessing is the one to try. But then it appears to simply be the version I already have.
Based on how old the ROM it has appears to be (16/09/2009) how can I get the HTC updated ROM 1.33.110.2 to install (the HTC site badges it "T-Mobile" and I have O2), and would anyone else who has be able to comment on whether it's just that my experience with Windows mobile is so poor and I should persist, or whether I should call it a day and move on? (I can see plenty of people have tried getting hold of Android on this handset....could the new Windows 7 work on it in time...?)
Moved to general as not rom development
According to wpcentral (http://www.wpcentral.com/verizon-set-push-out-latest-windows-phone-os-update-htc-trophy), Spark_W's may soon be getting the official 8107 update rom Verizon!
Luckily for us, and with very many thanks to DFT and Mwang, we might be getting a Tango rom around the same time!
Yes, so thankful to DFT and mwang for their work. Although I did a lot of homebrew with WebOS, I recently got a Trophy and installed the custom rom after reviewing the documentation. Really love the options it gives me. Check out Metro Themes. Super cool.
The radio update was huge (the radio file itself is 2MB's larger, but it refuses to flash on my phone atm), but I think it is a lead up to 8107... without a doubt this proves that its on the way.
I don't actually blame Verizon for this delay... I blame HTC. The last two phones getting this update are the Trophy VZW (SparkW), and HTC Arrive (GoldC), the only two CDMA Windows Phone 7's they have in their line up at this time. This is just crappy support on HTC's end, and I hope their "One" policy will eventually help fix this by creating less models and models are are similar to one another.
I hope this fixes some of the other weird texting issues that have popped up when sending SMS via CDMA.
Besides the Radio update of 7720 Mango v3 update, we also got a slightly newer SPL (2.04), not that makes makes a difference to most... this update version number would suggest that the SPL of 2.04 will remain in place.. I'm more interested to see if they will enable Internet Sharing with Verizon's Trophy driver (instead of getting a ported release from GSM Spark... although it works in the cooking universe. )
I do, however, think that a build newer then 8107 might happen. If the CDMA texting issue that people are experiencing is indeed a system issue and not a driver issue, its possible that we will see an ever so slighly newer build of Mango (8110+ perhaps)? It will be interesting to see this update hit and see what it fixes. If the SMS issue is fixed among the other crap that's long overdue, it could be that the long wait is due to Microsoft testing an ever so slightly newer SYS to address these issues... same goes for GoldC users.
I just received a Trophy to replace my Droid Incredible and haven't been able to sync to my Google account. I got it updated using Zune after finding an update was available (even though I JUST got this phone from VZW!) indicating it fixes a Google account sync problem... but alas it also didn't help. I'm on 8107 as I look now, but keep getting a "m.google.com currently unavailable" error (error code: 85010017). Anyone seeing this error or have an idea at what the issue could be? I really need my contacts transferred, thanks guys for any advice!!!??
TheXev said:
The radio update was huge (the radio file itself is 2MB's larger, but it refuses to flash on my phone atm), but I think it is a lead up to 8107... without a doubt this proves that its on the way.
I don't actually blame Verizon for this delay... I blame HTC. The last two phones getting this update are the Trophy VZW (SparkW), and HTC Arrive (GoldC), the only two CDMA Windows Phone 7's they have in their line up at this time. This is just crappy support on HTC's end, and I hope their "One" policy will eventually help fix this by creating less models and models are are similar to one another.
I hope this fixes some of the other weird texting issues that have popped up when sending SMS via CDMA.
Besides the Radio update of 7720 Mango v3 update, we also got a slightly newer SPL (2.04), not that makes makes a difference to most... this update version number would suggest that the SPL of 2.04 will remain in place.. I'm more interested to see if they will enable Internet Sharing with Verizon's Trophy driver (instead of getting a ported release from GSM Spark... although it works in the cooking universe. )
I do, however, think that a build newer then 8107 might happen. If the CDMA texting issue that people are experiencing is indeed a system issue and not a driver issue, its possible that we will see an ever so slighly newer build of Mango (8110+ perhaps)? It will be interesting to see this update hit and see what it fixes. If the SMS issue is fixed among the other crap that's long overdue, it could be that the long wait is due to Microsoft testing an ever so slightly newer SYS to address these issues... same goes for GoldC users.
Click to expand...
Click to collapse
You'd probably read it by now, but from my research it is 8107 and it still doesn't support tethering. I'd guess the issue is they have no way to correctly bill for it, so it's easier for them to just not turn it on at this point.
http://www.theverge.com/2012/4/12/2944147/verizon-htc-trophy-update-rolling-out
There are actually 3 updates that need to be done. 7740, 8107, and the HTC firmware (guessing that's the radio update?)
http://www.ubergizmo.com/2012/04/htc-trophy-8107-update-hits-verizon-wireless/
I would update my phone to this but since it doesn't have tethering I'd rather just flash DFT's ROM.
No, update didn't support tethering. I need to get the official file list captured sometime soon...