I have enabled the SIP client (BTW it works but very limited) following the instructions in general threats.
After reboot and some tests, I've realised that the GPS dosn't work any more.
Basically it is not detected by any SW (TTN, Google, AutoGPS, ..)
Any suggestion?
I JUST went throught the same thing 2 days ago - I had MS native VOIP working on my 6700 and didnt notice a problem obviously, as it has no GPS.
Here's whatcha gotta do:
You wont be able to remove the Sleuth's VOIP program - it will always fail. You need to open the cab on your desktop, extract and examine the setup xml and manually remove the files from the windows dir on your device and reg entries contained therein.
Or hard reset... whichever is easier for you.
The problem file is dnsapi.dll, but you wont get GPS back until you regedit and remove the files.
THEN, you can have your cake and eat it too, by installing THESE files.
Use SIP config to setup your provider.
Use Dontsleep Wifi to prevent the phone from auto sleeping during voip calls.
Use AutoAudioRoute/AudioRoute to push the audio to the earpiece instead of the speakerphone/Headphones, as is the case with all VOIP clients in WM6.
Hope this helps!
Related
Indeed clicking as much as one time on "Bluetooth Explorer" will cause TomTom not to function properly any more (maps/voices not found etc.).
I have learnt that the hard way!!!
Many members of this forum speculated that the Artemis SD card housing is somehow related to TT's maps to vanish.... NOT TRUE!!!
After a hard reset I have tested that TT was fully functional and I have (intentionally... just to find out) clicked on Bluetooth Explorer and BINGO the TT6.1 maps&voices are GONE!!!
If some of the forum experts would happen to read this and would feel like giving instructions to disable Bluetooth Explorer it would be very helpful.... this will surely avoid SEVERAL hard resets to many people.
I have read that one should go to Settings/Connections then select the FTP tab and uncheck "Enable Bluetooth Explorer" but this is not to be found on my ARTEMIS (P3300)... Let's see if somebody will find a moment to share his/her wisdom with the rookies and shed some lights on this annoying problem.
Cheers!
SiperX
On my Orbit you do the following to disable the Bluetooth Explorer
Settings / Connections / Bluetooth / FTP (tab)
Then select or de-select Bluetooth Explorer.
I appreciate your kind reply Patrick but as you can read in my thread this path (Settings / Connections / Bluetooth / FTP (tab)) is not available in the Artemis/HTC P3300.... Anybody else?
Do you have a comms manager? If so you can access the ftp option of the bluetooth settings from here.
TomTom and Bluetooth explorer both work on my xda orbit.
herghost, what version of TomTom are you running?
I m unable to have Bluetooth Explorer enabled on my Orbit, and get TomTom to find the maps. I am running ver 6.02
perfect, i wasnt able to make tomtom recognize maps on orbit(on universal it works w/o probs) i switched bt expl. off and it works. thx
Guys, there is no doubt. TT (mine is version 6.1) and BT Explorer are NOT going to work together! I am glad to hear that phsnake could get his orbit to resume TT functions.... And (also) I found out that my old rom (the one originally shipped with the P3300) had the path (Settings / Connections / Bluetooth / FTP) to disable BT Explorer (as Patrick_UK explained) ... but the one I am using now does not offer the chance to enable/disable BTE.... any registry master would be kind enough to offer his/her expertise to make this possible? I am not so keen on editing the REG unless I know exactly what has to be done
rom 1.28.0.0 wwe
rom date 11-06-06
radio 02.69.90
protocol 4.1.13.30
ext. rom PDAMobiz.com
SiperX:I'll try today to find reg solution, i cannot promise anything, but i'll do reg export with btexpl. switched on, then with switched off and compare reg.files. hopefully i'll find the right one key.
Phsnake, this sounds like a great idea! Thanks in advance!!! I really hope that you can succeed and give me support in this matter.
By the way where did you find the rom (ROM: DOPOD IPL: 1.25.0001 SPL:1.27.0000 GSM: 2.69.90 OS:1.28.0.0 WWE) you are running now? It sounds lke the right one for my T-Mobile Artemis.
so i compared the regs and diff follows:
Code:
[HKEY_CURRENT_USER\Software\HTC\BluetoothFolder]
"EnableClient"=dword:00000001
"HDEVICE"=dword:00031380
[HKEY_LOCAL_MACHINE\Drivers\Active\68]
"ClientInfo"=dword:00000000
"Hnd"=dword:00031380
"Key"="Drivers\\BlockDevice\\BTDisk"
"Name"="BTD1:"
i guess all U need 2 do is change "EnableClient" from 1 to 0. try it and let us know. (i can disable it thru bt settings). or remove above posted reg entries.
ROM:its standard dopod shipped(the latest one) should be on wm-gurus.com
Thanks man! The registry editing you suggested worked and the BT Expl. is now OFF and TT finds the maps again!!!
But the option to enable/disable the BT Expl. (via BT settings as you say) is still not available any chance you could send me a screenshot of your reg for both [HKEY_CURRENT_USER\Software\HTC\BluetoothFolder] and [HKEY_LOCAL_MACHINE\Drivers\Active\68]?
For your Dopod rom, could you please give me a precise link where I can download it? I could not find it at wm-gurus.com.
Thanks a lot
ftp.wm-gurus.com/Artemis/Shipped_Complete_Updates/ARTE_DOPODAU_12570702_026990_WWE_SHIP.exe
yes i know that wont allow u to switch off btexpl. thru bt control panel.
Here are regentries U requested, but i dont think it'll help. but try.
Thanks again!
BTW, the same file (ARTE_DOPODAU_12570702_026990_WWE_SHIP.exe) was available at XDA too.... I have tested it a few weeks ago it and -being an AU (Australian rom) my sim (Dutch T-Mobile) did not get registered as the operator is apparently not quoted .... strange that you can use it in Scotland.
For regs I will see what I manage to put together and will let you know... Great (and prompt) support was very appreciated...
Hi again,
I have flashed once more the ARTE_DOPODAU_12570702_026990_WWE_SHIP.exe onto my Artemis and I have (FINALLY) noticed that the SIM does register and I am able to use the phone (incoming & outgoing calls).
The only problem is that every time I reboot I get a notification from the "NETWORK WIZARD" which says "your current operator (20416) is not supported. You should obtain an update from your device vendor".... Any idea how I can get this nag off my back?
Thanks
try to check \windows\startup
I have deleted (& made a copy for backup) these 5 files:
netwiz.cpl
netwiz.dat
netwiz.exe
netwiz.exe.0404.mui
netwiz.ini
from the Windows folder of my Artemis.
After rebooting the Network Wizard notification does NO LONGER pops up!!!! So I would say "Problem solved", right?
I am glad that -thanks to the recent communications we exchanged- you "inspired" me to give one more try to the Dopod rom and I finally seem to have found what I wanted.
Only one final point: In other roms if you click on the phone signal bar you get the option to turn on/off the flight mode and if you click on the icon on the right of the phone signal bar you culd turn on/off the WiFi... in this rom you get a small (blue) Comm Manager link to follow in order to enable/disable these functions.... did you find any faster ways to activate WiFi or Flight mode? May be they can be added to the voice commands?
Cheers
u can use phonealarm-some skins supports one click wifi, gprs,btooth switch,
I saw phonealarm but I have decided to spend the end of the weekend configuring my newly installed rom (immediately after I will make a Sprite backup) and along the way try to think of something to keep to a minimum the amount of additional SW installed. What do you think if I use "tray launch", would that allow me to make the necessary shortcuts?
By the way (with previous roms) I kept my Artemis overclocked at 240 Mhz and it was pretty stable, did you test any higher frequency on the Dopod rom?
I'm struggling to restore BT Dial-Up Networking profile in my i780. I've used known solution for this, but it doesn't work exactly as it should.
After changing HKLM\Software\Microsoft\BTHATCI\Port from '5' (default) to '3', I've managed to get to the stage, where DUN profile is recognised by other devices (my Nokia N810 Internet Tablet in particular), but when I try to actually connect - it fails. However, it seems like really close to the definitive connection - there is BT communication between devices, even Data Call Manager in i780 indicates 'general.t-mobile.uk' data call, while N810 is still waiting for connection and eventually dies.
Because I've had DUN working excellent between N810 and HTC Kaiser, powered by dutty's WM6.1, I've manually checked all DUN-related registry settings in Kaiser and i780 - they are all the same. The only different bits that are relevant here, are \Windows\atcmdint.dll and \Windows\bthatci.dll files. I've tried to copy them across from Kaiser to i780, but I can't - as they are protected by the system.
I don't have any other ideas what could cause such problems. DUN service is detected, I can initiate connection, but I can't get it finally connected. I think mentioned above files are the very last resort in this case. Is there any way of extracting system-protected files from \Windows directory? Or maybe someone has it saved somewhere and could send them out? Thanks in advance for any advise.
I've managed to figure out that phone doesn't respond to ATDT command. It takes AT+CGDCONT=1,"IP","general.t-mobile.uk" initstring correctly (hence Data Call Manager shows APN), but when it comes to ATDT*99# - it fails with the error. I've also tried to dial ATDT*99***X# where X=0-6 but also no luck.
Any suggestions?
WM6.0 SIP client configuration - Not working
--------------------------------------------------------------------------------
Hi all,
I have followed the procedure in
http://forum.xda-developers.com/showthread.php?t=299950 and now i get Internet calling enabled in my device. However i could not make call. I am using the ondo SIP server for testing, no real service provider. I have tried many times and am not successful in getting it work.
However my doubt now is can the SIP client be configured in any of the three WM6.0 Operating system. It has 3 flavours :
1. WM6.0 Classic
2. WM6.0 Professional
3. WM6.0 Standard.
Can the SIP client be unlocked and worked from all the three or any specific flavour only ?
I think those who have made it work can provide insights into it. This is quite important for me. As till now i have been testing with WM6.0 professional. We intend to buy a WM6.0 device, so which flavour should we opt for ?
Hoping to get an earliest positive response.
im goin to be honest:
1. WM6.0 CLassic --> It works, but speakerphone sound (no earpiece)
2. WM6.0 Proff--> Same as classic
3. WM6.0 Standard--> Works bcoz says Internet Calling not available but when I configure a working server, it freezes my device at startup, so I have to hardreset it
Clear voice, Good responsiveness. So WM6.0 VoIP is quite good
I am using a LAN setup . Server used in Ondo server. But then my SIP client does not get registered with the server. Is it possible to try making calls using direct IP without any servers involved ?
kk2202,
Are you using any firewall at the SIP Server's machine?
I think you need to open SIP port (UDP 5060) at the firewall or disable it.
I'm using Ondo server (aka Brekeke SIP Server) without any problem.
Hi, did you make a _setup.xml with your settings and manage to install it?
If not make sure your phone is application unlocked and then follow the instructions again.
I'm successful on WM 6.1 Standard
You might also check for the Prov0Settings file and attach your xml here for verification.
My NAT creates problems for my Sipura 2100 box, but my softphones including the WM6.1 client gets through it without problems. For this reason I don't think your issues are NAT related. You might see the searching state, however when the IP phone icon appears in the top bar you should be good to go.
I might also add that if you suspect NAT issues you could try Fring www.fring.com/cab it is really easy to setup. If that works then it's clearly a configuration issue.
Hi,
I have attached the _setup.xml for verification. 192.168.0.101 is the machine where the ondo SIP server is running.
What should i check in Prov0Settings in this file. It gets created when i install my .cab file.
Fring is not working on WM6
Hey guys,
Im new to the XDA developer site, recently i have upgraded my Imate Jas Jam from WM5(Telestra) to WM6(3 Network) using "HERM_DOPODASIA_WWE_3.54.707.3_6275_CustomRUU" I have downloaded fring from www.fring.com/cab
Installation is successful, but when i start Fring it simplay shows up the screen which says fring is loading then close application, tried too many times could'nt make this to work, any ideas...
your help is appreciated
Hello everyone. I have just recently updated/flashed/done something to my phone to the Artemis Touch 4.02. Great rom so i have seen, no complaints with it. (Unsure what the proccess is actualy called.)
Only setback i have is that files i recive by bluetooth go straight to my main memory. What i would like to do is to have it go straight to my micro sd card, and to have a progress bar showing me the status.
I have tried a few programs.
DrYAR Bluetooth manager 1.5: Does what i need, but seems to be a little unstable. Sometimes freezes or will not connect to most phones.
DrYAR Bluetooth manager 1.6: Works great, only problem, if constently asks for every bit of the file you recive. So if its set to auto recive, theres alot of beeping going on.
DrYAR Bluetooth manager 2.0: I have seen this version somewhere, but i cant seem to download it
BT Tools: Dosnt seem to have many options.
Enable A2DP:Not sure where i got this from, but i had it from when i had a MDA Compact II. Worked for what i needed then. Dosnt seem to work on this one.
Broadcom Bluetooth Manager:Looks fantastic, many options to mess around with, but it just wount run on my device. Says there is not enogh memory to turn on bluetooth.
Is there any way i might make the first or last options work well, or is there another app i can try? So far it is a pain to move them over. I would like to keep the internal memory as free as possible.
Any more information you want do let me know.
PS Sorry for any spelling errors.
Is no one able to reply?
How about moBlue, works well on my Artemis and Diamond
HTH
Kim
Dosnt seem to work well on mine, still wants to use the windows version. Or sometimes the phone/whatever just doesnt connect
Well, I use moBlu as well on my Artemis & it works well. For it to work, you need to launch it before receiving a transfer via Bluetooth. You can set it up in its settings to make your phone discoverable when you launch the app & disconnect bluetooth when app is closed. And in the filters you will find 2-3 default filters, just select the "*.*" filter & set the location to a folder on your card. You can delete the other two filters or edit them & also add more if you want. They are file extension filters so if any file you are receiving matches them the filter will be applied & your file will be automatically stored in that specified filter folder.
After installing PhoneAlarm 2.13 I cannot send files via my windows XP computer to my HTC HD.
I can send files from the HD to the PC but not the other way round. In fact I can activesync using bluetooth and then use the activesync window on my PC to cut and paste files from the PC to the HTC but not by right clicking the file and then using the "send to" command.
I am positive that the problem is due to PhoneAlarm because when I uninstall it and hard reset my device everything seem starts working normally but again fails after PhoneAlarm installation.
Anyone else experiencing this problem and please help.
Regards
I had the same problem, could send files from my HD, but not to my HD.
Never installed PhoneAlarm though.
What I did to fix it:
- In Advanced Config, go to "Bluetooth". "Obex" was disabled. I enabled it, saved settings and did a soft-reset.
- In HD Tweak, also go to "Bluetooth". "Files reception" was disabled. I enabled it, saved settings and did a soft-reset.
Hope it solves your problems!
If I remember correctly you need to activate IRDA in the phonealarm settings to allow the bluetooth to work (I think it even mentions bluetooth next to the IRDA check box - odd but it then worked on mine)
Activate IR
sillysquid said:
If I remember correctly you need to activate IRDA in the phonealarm settings to allow the bluetooth to work (I think it even mentions bluetooth next to the IRDA check box - odd but it then worked on mine)
Click to expand...
Click to collapse
This is correct. You need to activate IR in the profiles in PhoneAlarm you use to receive files over bluetooth.
No need for hard reset
I have had the same problem even after uninstalling phonealarm. No file receiving over bluetooth. Then I have re-installed phonealarm again, enable infrared and uninstall it. Everything works fine now. I think some changes in registry would have solve it too, but this is easier I mean.
Registry Settings
woxydator said:
I have had the same problem even after uninstalling phonealarm. No file receiving over bluetooth. Then I have re-installed phonealarm again, enable infrared and uninstall it. Everything works fine now. I think some changes in registry would have solve it too, but this is easier I mean.
Click to expand...
Click to collapse
To enable file transfer in registry:
HKLM\\Software\Microsoft\OBEX and change the IsEnabled value from 0 to 1
The OBEX_inbox.cab can also be useful if your rom lacks it.