Related
After creating and installing a new ROM based on ENG-4-00-05 using the kitchen at www.yorch.net (did this a couple of months ago), I have been unable to get either of my GPS receiver software packages (CoPilot & Pharos) to attach to the comm port. I have no problems with ActiveSync 3.7.1 which uses the same comm port. BTW, this is a Siemens SX56 running on the US AT&T network.
Both software packages seem to think that the port is unavailable, but it is NOT clear if they think the port is missing or in use by another program.
When I first discovered this problem, I did build several different ROMs just as a sanity check, but they all seem to have the same issue. Is there a problem with 4-00-05 base code? Other than this problem, I have NO problems with the new ROM code and really enjoy the new features of WM2003.
Any help will be appreciated
David
be sure that beams is not checked under settings/connections/beams, also the foling keyboard driver if present will grab the com1 port also, you need to disable it, it will re-enable after reset so will need to be done after each reset.
hey, searched the forum a bit but there is no real answer to this one..
where can i get the widcomm btstack for 2003se. i'm using 1.5.0.0801 from mamaich but it's not working properly..
edit: not working correctly meaning freezing today screen items like CT PLUS, spb plus. sometimes freezing entire ppc, start menu not accesible etc..
my widcomm stack 1.5.0.0801 is not conflicting with other apps ( spb apps, etc. ) but always display "could not be correctly initialized " when other apps is opened. we all know that widcomm stack is memory hogger..i think there is a .reg patch to apply to make it more stable in SE..
i have the same probs as dutty
Widcomm BT 1.5
Hi Guys!
First of all:
Copy all the BT files to windows directory, then place the BTCE in windows\startup
Second:
Use the regeditor and delete the HKLM\Software\Microsoft\Bluetooth
Use the reeditor and delete de HKLU\Software\Microsoft\Bluetooth
soft-reset the pda...and that's all folks!!! the bt works like a charm, you can put the BT in "ON" and soft-reset your device that it connects again without problems!!
Sorry....
I forgot to say that you must run the file with the reg settings that exists in this forum.
errr cant find it (the reg) ^^
Here it goes....
Well... i'm sending in attach the file.
Cheers!
Sorry....
I forgot the file...
well, thx for the reg, but same prob as before
mbsb0812 Posted: Tue Dec 07, 2004 06:25 Post subject: Widcomm BT 1.5
--------------------------------------------------------------------------------
Hi Guys!
Copy all the BT files to windows directory, then place the BTCE in windows\startup
Second:
Use the regeditor and delete the HKLM\Software\Microsoft\Bluetooth
Use the reeditor and delete de HKLU\Software\Microsoft\Bluetooth
soft-reset the pda...and that's all folks!!! the bt works like a charm, you can put the BT in "ON" and soft-reset your device that it connects again without problems!!
=========================
i already did that procedures before and my BT stack is working but as i said, it intermitently flashes " could not be initialized" when you opened an app, said internet explorer. it seems to hog all of my memory...i reckon a .reg patch to prevent it. ( just forget where.. )
PS.
upon applying that .reg. you should run this patch for the sound to run well..
[/quote]
where is the widcomm software itself since we already have the registry patch?
thanks
tried on the MDA Compact, doesn't run (same thing for the 1.4.59).
I like the way the Internet sharing works on the new ROM, with simply starting the program and plugging it in. Is there anyway to make this work for the old ROMs?
Thanks, Lew
P.S. I just cant stand the loss of soooo many hardware buttons on the Cing rom. I may try the test rom =)
havent tried this as it is embedded into the OS, not sure of the dependicies required also... i will do some testing tonight for you and let you know... have you tried copying the exe's from the new rom onto your old one and running them?
i was looking into this this past weekend and tried to get internet sharing off the new cingular rom working on the softbank rom (aku2.6). first of all, you can't just copy the files directly from the \windows dir, you have to unpack the os.nb file and pull the files off that way. i don't know what the dependencies are either so i just pulled four files:
intshrui.exe
intshare.dll
intshrui (shortcut in \windows)
internet sharing (shortcut in programs)
and two registry settings.
i put it all into a cab (attached) and tried to install it on the softbank rom but no go. i get an error that says something to the affect of "intshrui.exe is not a valid pocket pc application". i'm not sure if that means i'm just missing needed dlls or if the executable itself is hard-coded to look for an aku value > 3. if you guys figure out what dlls are needed, let me know and i'll update the cab.
Unfortunately, it can't be THAT easy - the BT stack has also been heavily modded in AKU3 to include the BT PAN (and to get rid of BT DUN) profile. Try including the MS BT stack-related DLL's too.
I dont "need" it to work over bluetooth (although it would be nice) I would settle for usb.
lewcamino said:
I dont "need" it to work over bluetooth (although it would be nice) I would settle for usb.
Click to expand...
Click to collapse
but i believe that the application has bluetooth dependencies so inturn will not load...
Has anyone managed this? I'd be interested in whacking this onto my Works's M3100 which won't get AKU 3.3 / WM6 until:
(a) Orange UK release it
(b) the IT chaps sign it off
Soooo the day after never !
I have a Softbank X02HT (a HTC Cavalier Smartphone) - they cripple Internet Sharing by removing the required bits (so that you have to pay big bugs for PC data).
I got the files and registry keys installed and I can see the GUI, but the content of the selection options for "PC Connection" and "Network Connection" are blank - (the values are missing)...
Has anyone else got this working yet?
I post this under the ROM dev for numerous reasons.
The Radio thread is scattered with confusing information about it.
You may wreck your phone by just copying it over the existing one.
There seems to be a requirement to be met by the ROM (patched NK.EXE if I recall right).
There seems to be a patch if NK is not patched by the chef.
Can one really explain what's behind that file and interaction with the Radio?
Admins, if you mind this post here either delete or move though I think it's ROM
related.
tyguy said:
I post this under the ROM dev for numerous reasons.
The Radio thread is scattered with confusing information about it.
You may wreck your phone by just copying it over the existing one.
There seems to be a requirement to be met by the ROM (patched NK.EXE if I recall right).
There seems to be a patch if NK is not patched by the chef.
Can one really explain what's behind that file and interaction with the Radio?
Admins, if you mind this post here either delete or move though I think it's ROM
related.
Click to expand...
Click to collapse
I can answer part of this.
The NK.exe must be patched to allow signed dll files to be added to the rom.
I have not heard of any way to get around the nk.exe patch. If there is Id like to hear it
It remains to be seen if the rilphone dll really makes much difference radio wise. However it does contain some carrier specific stuff in some cases. Da_G is more capable of explaining the technical details.
Thanks arupp I thought so too that there isn't a patch though one of the chefs had a comment on that
http://forum.xda-developers.com/showpost.php?p=3296537&postcount=794
I couldn't find it.
Thank you for starting this thread. I had searched everywhere for the Cmonex's autopatcher, but couldnt find it. Da_G also referenced it in the Radio thread here: http://forum.xda-developers.com/showpost.php?p=3229451&postcount=1012
so to patch or not to patch. That is the question.
Do i patch if i have a custom ROM?
Do i patch if i have the leaked version of the touch pro ROM official HTC (well almost) ?
Good thread thanks.
Found the thread Monx and Da_G referenced here: http://forum.xda-developers.com/showthread.php?t=384137
Post with patcher here: http://forum.xda-developers.com/showpost.php?p=2812111&postcount=23
Wtf??? i need to read the thread a few more times bc im still not sure what to do
Cmonex's autopatcher program is not really intended for the end-user, but more for the chef (it needs to be applied to xip.bin or os.nb.payload)
Her post says it might work directly on the .nbh before you flash it, but it's not guaranteed. I haven't tried it that way either - only directly on nk.exe inside the xip.
So, what you want to do is use the autopatcher directly on the .nbh - but again her post says it's not guaranteed to work.
Da_G thanks for chiming in!
So let me recap:
NK.EXE patch tool designed for chefs, not for Joe Doe users
No direct patch/fix for existing installation
Patch to be applied in ROM image NBH not Radio image NBH (---> hard reset)
Effects not really clear
From what I've read the rilphone.dll interacts with the Radio ROM and may be beneficial for reception and battery life but it's not proven that there will be a positive effect on the GPS for example (we all have lag ).
Furthermore, wrong ril... /Radio combo my make Radio unusable.
For GPS issues a NVRAM fix must be applied (early hardware boot-stage fix) which may not be even possible with the current ROM basis.
Conclusion:
Keep your hands off copying whatever rilphone.dll files are flying around in the Radio thread into your Windows dir and play it secure until the chefs figured it out BUT keep this post updated for general information.
Please tell me if I'm wrong.
tyguy said:
Da_G thanks for chiming in!
So let me recap:
NK.EXE patch tool designed for chefs, not for Joe Doe users
No direct patch/fix for existing installation
Patch to be applied in ROM image NBH not Radio image NBH (---> hard reset)
Effects not really clear
From what I've read the rilphone.dll interacts with the Radio ROM and may be beneficial for reception and battery life but it's not proven that there will be a positive effect on the GPS for example (we all have lag ).
Furthermore, wrong ril... /Radio combo my make Radio unusable.
For GPS issues a NVRAM fix must be applied (early hardware boot-stage fix) which may not be even possible with the current ROM basis.
Conclusion:
Keep your hands off copying whatever rilphone.dll files are flying around in the Radio thread into your Windows dir and play it secure until the chefs figured it out BUT keep this post updated for general information.
Please tell me if I'm wrong.
Click to expand...
Click to collapse
I can say the majoriity of custom roms have the nk.exe patched. If you dont know if your rom is patched ask your chef.
if you look at rilphone.dll in a PE viewer app, you'll see some references in the file to "AGPS". I think it's simply setting AGPS on or Off......or it might be more than that but I do see some references to AGPS in that dll (using the latest dll provided in the 5.05 release which is about 500kb in size)
I notice that my reception varies with different ROMs. I would say that I was getting the best reception with the 5.05 ROM and the 1.11.25.01 Radio. Then when I switched to some custom ROMs, things get a bit worse. The signal strength seems to vary more and I find the phone often switching between 3G and Edge or between Edge and GPRS/GSM. It keeps doing that even when I stay in the same place. I'll make a call with 5 bars of Edge and by the end of the call, be on GPRS when I didn't physically more. Or sometimes the phone will hang on to an HSDPA signal until I drop a call and never switch to Edge, which has 3 or 4 bars of signal strength once it finally does switch. I would imagine that all this switching to different signals is wasting battery too.
1) Could this be an issue with the custom ROMs rilphone.dll? I'm using EnergyROM 1.1a and 1.11.25.01 at the moment.
2) How can I know which radio version my ROMs rilphone.dll is designed to work with?
3) Does having that NK.exe patched allow me to just copy in a different version of the file with no adverse affects?
TheSopranos16 said:
I notice that my reception varies with different ROMs. I would say that I was getting the best reception with the 5.05 ROM and the 1.11.25.01 Radio. Then when I switched to some custom ROMs, things get a bit worse. The signal strength seems to vary more and I find the phone often switching between 3G and Edge or between Edge and GPRS/GSM. It keeps doing that even when I stay in the same place. I'll make a call with 5 bars of Edge and by the end of the call, be on GPRS when I didn't physically more. Or sometimes the phone will hang on to an HSDPA signal until I drop a call and never switch to Edge, which has 3 or 4 bars of signal strength once it finally does switch. I would imagine that all this switching to different signals is wasting battery too.
1) Could this be an issue with the custom ROMs rilphone.dll? I'm using EnergyROM 1.1a and 1.11.25.01 at the moment.
2) How can I know which radio version my ROMs rilphone.dll is designed to work with?
3) Does having that NK.exe patched allow me to just copy in a different version of the file with no adverse affects?
Click to expand...
Click to collapse
-----------------------------------------------------------------
Only NRGZ28 should be able to answer your ????
As he as mentioned in 1st page of thread "
This ROM is CE OS 5.2.20764 (build 20764.1.4.3) and the version is: 5.05.405.1 ,all from official Raphael ROM." using same build with which 1.11.25.01 radio is attached. Obviously it should have same DLL file if he has not altered it during cooking.......
Here's a bit more of a technical explanation for the whole thing:
rilphone.dll is the 'interpreter", or the "middle man" inbetween the Microsoft-desgined "Radio Interface Layer" or RIL - you can think of it as the Radio ROM speaks spanish, and Windows Mobile speaks english.. so when a program wants to do something involving the cellular radio, say, determining the signal strength to display the "bars", it issues a command to the RIL.. the RIL forwards this command to rilphone.dll, which interprets it into an AT Command. rilphone.dll then communicates through a standard serial port connection through SMD9: to communicate back and forth with the Radio ROM. Any responses are then translated again by rilphone.dll, and passed on to the RIL.
So, let's say a new command gets added to the radio. In this case we'll use a new command that was in fact added in 5.05, [email protected] - if the rilphone.dll is not updated, it is not aware of this new radio command, and will never issue it to the radio ROM. So you'd potentially be missing out on whatever that command does. Also, if a change is made to the required format of some other AT Command, the rilphone.dll will not be aware of this change and still be using the old format.
Carrier-specific rilphone.dll's also have features that generic ones do not (such as the 5.05 rilphone.dll in the htc-branded build most custom roms are using) - one such feature is CNAP support for Rogers - it seems support is built into all radio ROM's, but if rilphone.dll does not have specific support for CNAP, it never reads the caller name into the registry for display on the dialer. There are a number of similar carrier-specific features i've observed.
That should cover the function of rilphone.dll and the reason you'd want to keep it on-parity with the radio ROM... and in some cases why you'd want to use an older rilphone.dll (to maintain support for CNAP, etc)
Now on to the nk.exe patch -
nk.exe is the "boot process" for Windows Mobile.. it brings up hardware to initial values and displays the radio/protocol/build version info on the intial boot screen.. nk.exe controls such low-level things as the size of the page pool, certificate checking, etc.
This is where the nk.exe patch comes into play.. it replaces the code that checks certificates with a "No Operation" - so the system now trusts all code installed, regardless of if it has been signed by a trusted provider or not - this is a good thing, as you control all code being installed on the device, rather than the OEM, and one would presume at the point you want such checks removed, you know better than the OEM
Without the nk.exe patch, when you replace rilphone.dll, the system checks it against it's internal certificate store, finds that it's not signed with a trusted certificate, and refuses to load it. This is why replacing rilphone.dll on unpatched ROM's results in no radio function.
Once you have a patched nk.exe you can replace any trusted file in the system with an unsigned file and not have to worry about the checks - note you no longer need sdkcerts.cab either as this is intended to load onto your device's root certificate store, and then manually sign the files you're replacing with the sdk certificates, then it would be loaded up as a trusted file.. however this doesn't work on drivers that are loaded early in the boot process, as there are 2 "states" of the certificate store - one early boot state where the drivers are loaded, where it's using a pre-defined set of root certificates (specifically sysroots.p7b in XIP, which contains 17 certificates from trusted root providers) - the 2nd "state" of the certificate store is farther on in the boot process, after drivers and services are loaded - this is when it would load in the sdk certificates and allow you to load manually-signed drivers. But again this is too late in the boot process to allow sdkcerts.cab to work for Drivers and Services - which is why the nk.exe patch is needed.
Note that any files/modules cooked into ROM are automagically treated as trusted, regardless of nk.exe patching status or if the files are actually signed with a trusted authority - it's assumed by Windows Mobile if the file is cooked into ROM, it must be trusted.
Incidentally, I believe this is the reason HTC created the "BootLauncher" service - so that they could load up services signed with their own stuff after creation of the ROM (patches, hotfixes, etc). Basically BootLauncher loads up during the services stage, and waits for a pre-defined period of time before then loading it's own set of services (wait time and services to load are defined in the registry under HKEY_CURRENT_USER\Software\HTC\BootLauncher)
the autopatcher searches for a string to replace, so it might work on the .nbh.. the feeling i get from cmonex's post is that she didn't design or test it against that scenario, but it might work
Hope that sheds some light on the situation, and isn't too complicated!
Hi DA_g
Thank you Da_g for such a beneficial explanation....
I hope its going more complicated now..... as you have explained
"Carrier-specific rilphone.dll's also have features that generic ones do not (such as the 5.05 rilphone.dll in the htc-branded build most custom roms are using) - one such feature is CNAP support for Rogers - it seems support is built into all radio ROM's, but if rilphone.dll does not have specific support for CNAP, it never reads the caller name into the registry for display on the dialer. There are a number of similar carrier-specific features i've observed."
all radios have Carrier-specific rilphone.dll's so obviously all its not only with 1.11.25.01 (Raphael radio) all other radio's i.e, for example .16,.19,.28,.32,.20 if so obviously the results would be not stable for all the users with different ROM's and Radio's.......... Now the big ? rilphone.dll should be programed for different carriers to the specific radio
The way it seems to work from my observations is this:
Carrier X issues a "ROM Request" to HTC, specifying what support and configuration they require (such as CNAP support for rogers)
HTC then assembles the ROM to their specifications, using the latest drivers, etc, available at the time.
All radio rom's seem to include support for all carrier-specific options, they just need a rilphone.dll that is aware of the particular option to enable it.
So for us to get a newer rilphone.dll with rogers support (say, 5.05), rogers would need to issue a "ROM Request" to HTC, and they would need to fill it.. then we would have the rogers 5.05 rilphone.dll.
Using an older rilphone.dll has unknown effects (as it will not be aware of newer features in new radio version, etc) but so far has not shown to cause specific issues.
Hi DA_g
I need your help regarding this...how to edit rilphone.dll i am working as switch engineer for Ericsson india for GSM ...hope fully i would be able to understand some of the specifications present in this file.
Editing a .dll is beyond the scope of my ability to explain in a forum post, you need to do some research into reverse engineering and ARM disassembly..
Particularly, if this screenshot scares you: http://www.hex-rays.com/idapro/pix/idalarge.gif
You probably don't want to even get into it
Da_G said:
Editing a .dll is beyond the scope of my ability to explain in a forum post, you need to do some research into reverse engineering and ARM disassembly..
Particularly, if this screenshot scares you: http://www.hex-rays.com/idapro/pix/idalarge.gif
You probably don't want to even get into it
Click to expand...
Click to collapse
Ha ha ha really it is scary...............
But in my opinion individual Radio should be mapped to rilphone.dll with carrier specification with out this non of the radio would give best result .....
Depends on one using carriers with different frequencies for example.... i got tp with radio ver .28 (raphael) which is made for IDEA operator which uses 1800mhz freq, where power of the cell site & TP might be programmed vious according in rilphone.dll.....
i did SIM unlock.....Now i am using TP on Airtel operator which work on dual band 900 & 1800 so it is obvious that RADIO would not give me best results.
Results are vigorous ....dropped calls, voice break, poor coverage, poor battery performance,e.t.c................
So all ROM with associated with RADIO would work better on TP who uses specified Carrier...
Is there a way to get or create an universal rilphone.dll ?
Only someone with access to rilphone.dll source code could create a universal rilphone.dll.
Quite doubtful that HTC would be interested in doing this
aruppenthal said:
I can answer part of this.
The NK.exe must be patched to allow signed dll files to be added to the rom.
I have not heard of any way to get around the nk.exe patch. If there is Id like to hear it
Click to expand...
Click to collapse
I think you mean unsigned.
there is a way around... you import your own certificate into the device's trusted certs store and then sign the system DLL with your cert and copy it over... WM accepts this no problem and this is exactly how I used to do things.
HTC has realesed a Hotfix for TP's GPS problems...
Still haven't test it, but what have you, Chef's, to say about it?...
On HTC's Support page:
Software Download
This software is suitable for the following devices : HTC Touch Pro
Hotfix for resolving difficulties finding or locating a position when using GPS for HTC Touch Pro Release Date: 2009-05-25
If it is difficult to find or locate a position when using GPS, please download this hotfix to solve the problem.
Installation Instructions:
Follow the instructions below to download and install the hotfix 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 this hotfix select the hotfix below and the location closest to you then click Download.
Copy the hotfix, which is an .exe file, to your device. To install the hotfix, tap the .exe file and follow the on-screen instructions.
Note: If you perform a device hard reset, you will need to reinstall the hotfix after the hard reset.
So where did this come from? Would be nice to have more information than what you've currently posted, please elaborate..
In addition, most of the newer roms have the aGPS working, so the gps issue is a moot point.
Which GPS problem I wonder, I can think of 4, one being aGPS (which works great now after 5.08 AT&T)
There's also the issue of 'speed lag' and then the issue of 'position lag', and finally the issue of 3rd party gps programs not showing satellites/losing fix every xxx seconds/etc.
/me snags the goodies
X2D said:
So where did this come from? Would be nice to have more information than what you've currently posted, please elaborate..
Click to expand...
Click to collapse
Updated first post...
Anyone actually worked out what this does yet?
Ok, so this installs cleangpsdata.exe to \Windows (same ver that can be found on blackstone and other stock msm 72xx ROMS)
It copies a link into \windows\startup (same as the cleangpsdata package from blackstone does)
The functionality of the cleangpsdata program is simple, it opens the GPS0: hardware port and sends an IOCTL to wipe out the stored epheremis and other cached data in the chipset's NVRAM.
The problem this is intended to fix would seem to be extremely long startup times for gps (due to bad cached data that needs to be cleaned out)
With aGPS functioning it should have no effect; without aGPS it should only have an effect if your cached gps data gets corrupted for some reason and a quickgps re-download/re-inject won't fix it.
i'm wondering if it's works with WM6.5
So as a chef, would you recommend cooking in this fix and executing it in config operator or just cooking in clean gps and creating the startup link in app.dat??
Same effect either way (cleangpsdata as a package, i.e. from blackstone or this hotfix .exe)
I used to cook it in prior to aGPS being fixed.
Also, there's no relation to WM 6.5 with this hotfix, it talks to gpsdriver.dll, which is compiled independantly of the OS.
In addition, if you snag the latest HTC GPS Tool, there's a "Cold Start" menu option in it - sends the same IOCTL!
I do not use aGPS and am a bit scred to install this hotfix
I'm in Canada...I have no assistance server for AGPS...so would this help?
well I just tried installing it on my fuze which runs energyrom 3.0 the May 22nd build and it says "incorrect version, this hotfix is not compatible with your device.
Re: Not having an assistance server for AGPS
There are several publicly accessible servers available, check out the agps thread, as long as you have a data plan you should have no problem getting agps working with a few registry tweaks
Daemos said:
incorrect version, this hotfix is not compatible with your device.
Click to expand...
Click to collapse
same error here.....
not that I care though, I have good gps reception
Daemos said:
well I just tried installing it on my fuze which runs energyrom 3.0 the May 22nd build and it says "incorrect version, this hotfix is not compatible with your device.
Click to expand...
Click to collapse
Check your \windows folder; you probably already have cleangpsdata cooked in.
are you guys (who are using this hotfix) having the data plan?
or do you have entire map saved on the storage card?
Not that I've bad reception but after all this time from htc to post an answer to gps issue I had to install it and tried it..
Did not tested yet, tomorrow will post if I see any difference! Maybe it will take longer, cause it cleans the gps data all the time i reset. Or am I wrong?
@zenithcoolest: I use maps always on storage card... Data Plan is expensive and it's impossible to use with frequency!
Daemos said:
I'm in Canada...I have no assistance server for AGPS...so would this help?
Click to expand...
Click to collapse
You can use supl.nokia.com if you have a data plan, works great in Guatemala
You can find info in this thread: http://forum.xda-developers.com/showthread.php?t=489887
It didn't do jack-squat for me. Well, instead of getting a fast lock like I was getting yesterday, I had to wait five minutes. So it did do something.