Related
Hi
I downloaded from HTC website the hotfix for bluetooth
Kai06492.CAB I installed the file and deleted the cab file now I have an icon showing the hotfix as a program!!
I have deleted the cab and soft reset my phone and i still have the icon on my program files.
does anybody has the same problem? how can I delete it from my programs
Thanxs
the icon in the programs menu is just a shortcut (in /windows/start menu/programs/) im sure you can just delete the shortcut and have it gone from the menu
defaultdotxbe said:
the icon in the programs menu is just a shortcut (in /windows/start menu/programs/) im sure you can just delete the shortcut and have it gone from the menu
Click to expand...
Click to collapse
Thank you very much!
I haven't heard of such a fix before. Does it work? I went to the HTC site and could not find it. I searched this whole site and could not find it. Does anyone have a copy please.
AGY said:
Hi
I downloaded from HTC website the hotfix for bluetooth
Kai06492.CAB I installed the file and deleted the cab file now I have an icon showing the hotfix as a program!!
I have deleted the cab and soft reset my phone and i still have the icon on my program files.
does anybody has the same problem? how can I delete it from my programs
Thanxs
Click to expand...
Click to collapse
From the name of the CAB and from this post, http://forum.xda-developers.com/showthread.php?p=1750060 it appears that this is for the Kaiser. Can anyone confirm that this works for the Titan/Mogul? If so, this might be the Holy Grail to get Bluetooth working on my PPC-6800.
Has anyone tried this, and can confirm or deny if this fixes any Bluetooth issues on their Titan/Mogul?
what bluetooth issues are we talking about now (since 2.17 came out, my BT has been perfect)?
Dishe said:
what bluetooth issues are we talking about now (since 2.17 came out, my BT has been perfect)?
Click to expand...
Click to collapse
I haven't had my Mogul that long, but with the DCD 1.6.10 kitchen and either my Blueant Z9 or my Plantronics 510, I sometimes lose my BT connection if I have my headset in my right ear and the phone on my left hip or even in my left inside jacket pocket.
With MSVC 1.6, about half the time I get asked to repeat my command, but it never accepts the repeated command. I think this is the same problem as VC confirmation, which is known not to work on the Mogul.
When VC does understand my command, it takes 5-10 seconds before it repeats it back and acts on it, and most times the voice is very low volume and scratchy.
To JimSmith94,
FYI...
Bluetooth radio waves do not travel through water and since the human body comprises of 70% water, you may lose signal if your BT headset and phone are located on opposing sides of your body.
I wear mine on the same side and never lose BT signal...
xweaponx said:
To JimSmith94,
FYI...
Bluetooth radio waves do not travel through water and since the human body comprises of 70% water, you may lose signal if your BT headset and phone are located on opposing sides of your body.
I wear mine on the same side and never lose BT signal...
Click to expand...
Click to collapse
Yes, I am aware of how Bluetooth works. The point I was trying to make, but apparently didn't, is that I had none of these issues with MSVC 1.6 and my PPC-6700. It seems that Bluetooth in general and MSVC specifically don't work nearly as well on my Mogul as they did on my Apache.
If no one else has these issues with the Mogul, could this be a kitchen issue, or a hardware problem that I need to talk to Sprint about, and see about swapping out my phone?
JimSmith94 said:
Yes, I am aware of how Bluetooth works. The point I was trying to make, but apparently didn't, is that I had none of these issues with MSVC 1.6 and my PPC-6700. It seems that Bluetooth in general and MSVC specifically don't work nearly as well on my Mogul as they did on my Apache.
If no one else has these issues with the Mogul, could this be a kitchen issue, or a hardware problem that I need to talk to Sprint about, and see about swapping out my phone?
Click to expand...
Click to collapse
The BT drivers on the titan do not work as it should and M$VC 1.6 does not work with WM6 as it should either, if you search around you will find this to be true from day one.
With this new rom I can now enable conformation when using MS voice command 1.6. Before i would have to disable conformation in order to use bluetooth with MS voice command, this is no longer a problem; can any one else confirm this?
Wow, I so have to check this out.
No lie! ha ha ha it works! saweet!
well, now caller id and messages arent sent through
there is a reg tweak which will let the caller id come through the bt headset,
sorry but not sure where it is.
Notification
I set the notification options to "Announce notifications using bluetooth hands free if available" and it works. When the phone rings I hear the ringing and the announcement through the headset. I did not do any registry changes as I used to do before this ROM. I am using a Jabra 8010.
I'm more excited about the confirmations working on 3.16 than even GPS and EVDO-A. I don't keep my headset in my ear very much, so I haven't even checked to see if notifications work through the headset.
JimSmith94 said:
I'm more excited about the confirmations working on 3.16 than even GPS and EVDO-A. I don't keep my headset in my ear very much, so I haven't even checked to see if notifications work through the headset.
Click to expand...
Click to collapse
I can also confirm that this problem is fixed. I took the plunge with the pre-release ROM and it's been working like a charm. I have not had to modify the registry to get notifications to work, either. I just went to Settings->Voice Command and setup my preferences.
I also have to agree that the Bluetooth fix is more exciting to me than the GPS stuff since I use this feature way more than I use GPS.
where can I get this fix?
HTC TOUCH
VOICE COMMAND 1.6
NO CONFIRMATIONS THOUGH BLUETOOTH
Where can I get this fix?
mtnTOUCH said:
HTC TOUCH
VOICE COMMAND 1.6
NO CONFIRMATIONS THOUGH BLUETOOTH
Where can I get this fix?
Click to expand...
Click to collapse
touch forum? lol. we have a newer radio rom and bt drivers witch fixed the issue, so wait for someone to port them over. Sorry man.
Question: bluetooth definitely seems to be working 100% better (no longer disconnecting randomly, I can shift all sound to it now if I want, etc), but the button on my bluetooth earpiece no longer brings up the voice command prompt. When I run the bluetooth voicecommand proggy thingy it works, but I can't do it from the earpiece.
Am I missing something ridiculous? I've done some searching on the forums, but haven't found anything. ('course, I might just be pathetic and searching)
taxilian said:
Question: bluetooth definitely seems to be working 100% better (no longer disconnecting randomly, I can shift all sound to it now if I want, etc), but the button on my bluetooth earpiece no longer brings up the voice command prompt. When I run the bluetooth voicecommand proggy thingy it works, but I can't do it from the earpiece.
Am I missing something ridiculous? I've done some searching on the forums, but haven't found anything. ('course, I might just be pathetic and searching)
Click to expand...
Click to collapse
Did you assign Voice Command to Button 5? (Start > Settings > Buttons). I have Button 5 set to Voice Command, and Button 5 (Press & Hold) set to Record.
mtnTOUCH said:
HTC TOUCH
VOICE COMMAND 1.6
NO CONFIRMATIONS THOUGH BLUETOOTH
Where can I get this fix?
Click to expand...
Click to collapse
This worked for me on my wizard and Hermes
taxilian said:
Question: bluetooth definitely seems to be working 100% better (no longer disconnecting randomly, I can shift all sound to it now if I want, etc), but the button on my bluetooth earpiece no longer brings up the voice command prompt. When I run the bluetooth voicecommand proggy thingy it works, but I can't do it from the earpiece.
Am I missing something ridiculous? I've done some searching on the forums, but haven't found anything. ('course, I might just be pathetic and searching)
Click to expand...
Click to collapse
i have the same problem. after a hard reset and then installing ONLY voice command, it works PERFECTLY - announcements, confirmations, everything. after a soft reset something gets changed in the registry and it no longer is activated from the headset.
is there a program that can tell you what has been changed in a registry?
its frustrating that is working PERFECTLY and only upon a soft reset does it not work anymore...
ok... still trying to isolate what the problem is.
here are the symptoms. as before, everything works GREAT until i soft reset.
then, rather than the headset triggering the voice command, it opens the dialer app and hangs open. i have to uncheck the object in bluetooth settings, save, then recheck to reset headset.
i am trying some more stuff...
i found a PITA fix. apparently whatever happens after a soft reset messes up the bluetooth files. so i uninstall, soft reset, then reinstall.
sad thing is - i'd rather do this than keep trying to figure out what is causing this conflict...
1.6 Voice Command; announcements not coming over incoming calls
I have a ppc-6800 sprint mogul.
I have WM6 Professional
CE OS 5.2.1238 (Build 17745.0.2.3)
My issue is that when I installed VC 1.6, everything works fine, except I don't get the incoming call or calendar announcements. I have checked the appropriate boxes in the VC options settings to no avail.
I am certainly no xda-developer, and can become easily confused when talking about registry edits and .dll files. If anyone can provide explicit directions on how to fix, I would truly appreciate.
JFA
Hi people,
I just bought myself a Prophet so now I'm putting it through the paces configuring it the way I want it.
Everything is dandy on the new ROM I flashed (Prophet ROM CE OS 5.2.20721) but I am having trouble getting MS Voice Command to activate via Bluetooth.
I did a search in the forums but could not find anything on it, my question is does anyone here use BT with MSVC and can they activate MSVC with their bluetooth? If so, what ROM are you using, and what Radio Version? I'd like to get this to work as it is the most important app for me in a phone.
Thanks
Try read this topic:
http://forum.xda-developers.com/archive/index.php/t-256855.html
Thanks, that trick never worked for me over 5 different devices, but anyway the good news is, for some reason, it suddenly worked.
I currently have Vincent's Speedy Diamond ROM (Build 20273.1.3.3) with radio 2.69. I installed Voice Command 1.6.19209, and it did not work. Then I uninstalled it, reinstalled VC 1.6.19213, still no dice, then I uninstalled that then reinstalled VC 1.6.19209, then it *still* didn't work.
Then I did a soft reset and all of a sudden it works. =_= The world is a mysterious place.
did you check this?
This cab is good for me, but to make it work with the button on your bluetooth headset
you also need to do the following changes in the registry:
HKLM\SOFTWARE\Microsoft\Bluetooth\AudioGateway\BTA GExtModule\"Windows\OEMAGW.dll"
My headset only make the "input speech name" after this change.
regards
Thanks. I prefer MS Voice Command but I'll use that if ever the miracle that happened screws up later. For now it somehow worked so I'll just hope it stays fixed!
Sorry. I can't find an answer to this. I have found several possibilities, but none work.
I have the XV6800 with DCD's 3.2.6 ROM installed and Voice Command 1.6 (I purchased it myself)
I can't get the bluetooth button to work with VC. I tried installed Cody's "Fix" for this but afterwards, my phone reboots everytime I go into "Settings" from the main menu.
Has anyone else gotten this to work with DCD's 3.2.6?
Please help!
Thanks in advance!
You need to have these two registry entries for VC to work over bluetooth.
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\AudioGateway]
"BTAGExtModule"="vcbthag.dll"
[HKEY_LOCAL_MACHINE\Software\OEM\VoiceCommand]
"Path"="\\Windows\\VoiceCMD.exe"
Also, if you use a wired headset, place a copy of voicecmd.exe and call it sddialer.exe in the \windows\ folder. This will allow you to use your headset's talk button to call voice command.
findthisfunny said:
You need to have these two registry entries for VC to work over bluetooth.
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\AudioGateway]
"BTAGExtModule"="vcbthag.dll"
[HKEY_LOCAL_MACHINE\Software\OEM\VoiceCommand]
"Path"="\\Windows\\VoiceCMD.exe"
Also, if you use a wired headset, place a copy of voicecmd.exe and call it sddialer.exe in the \windows\ folder. This will allow you to use your headset's talk button to call voice command.
Click to expand...
Click to collapse
Are there supposed to be 2 "\\" in front of "Windows" as well as 2 "\\" in front of "VoiceCMD.exe"?
The other registry key was already there.
?
It didn't work. Is there something I'm missing?
Sorry, that's all I have. I don't know why it's not working for you. As far as the registry entries go, you only need one '\' when you're entering it in manually.
I have the puchased version of VC as well and once I enter these registry keys and reboot, it works perfectly for me.
All credits goes to myn. Here is the original thread [ROM] Myn’s Warm Eclair - [RLS1 - 06/17/2010] - An Accelerated Experience
Confirm working good on my NIKE100 on ext2 SD, so withour flashing, i can use Winmo n Android on the same device.
How to:
1. Download from the original thread, i'm using NoMORootFS for SD with 240x320 version
2. Backup! than, clear whatever "android" stuff you have from sdcard (I dont want it to get caught up in the install) especially your andboot folder
3. Extract contents of downloaded zip to temporary directory
4. Copy extracted /andboot folder to the ROOT of your SDCard
5. copy zimage to /andboot folder with this version (credit to mblaster) get in from http://84.23.71.227/kerneloftheday (i'm using zimage with vibration on my nike100 with zimageNike name)
6. overwrite default.txt with attached default.txt
7. Run HaRET, than hit “run” to launch android
8. Press and hold center of dpad after hitting "run" and follow the directions in the NoMoRootFs menu system
9. Install android system
10. Quit installer
11. Booting into Android
12. After you can see android logo wait about 15 minute
13. then shutdown and open up your phone again (should boot into winmo)
14. start haret and boot again to android
15. your android is ready to use
Working: Call, sms, ring, data (although there seems to be a little problem)
Not Working: Bluetooth, camera
Great job and a good tutorial buddy, I defenitly gonna give it a try.
ok, try it and share here, maybe it can make us nike user more familiar with android
Nice... But!
Nice one there. There is seems problem with the hardware keypad. The hardawre keypad works though keypad #1 when pressed twice sleeps nike. Maybe the said button is mapped for that function. Better if we can bring it back to the original function. Thanks again.
uhm...
Hey,
I copied everything onto my SDcard, into the /andboot directory
Haret.exe starts, holding the D-pad...Linux starts etc, but...then it hangs with an error "sh: 2 unkown operand
losetup: /dev/block/loop1: No such file or directory
Failed
Failed to reach system.img on SD card"
And from there on every button I press gives my weird syntax...
anybody knows what I'm doing wrong..?
Installed on ext2 partitions, now take some tests on my nike 100.
Problems I found:
- On boot I have Voice Search not responding.
- If I try to set mms settings the apn disappear (i use Wind in Italy), setting only apn and name work (i'm syncronizing with gmail)
Thanks a lot for this tutorial!
Many thanks for this post.
Three questions:
You are using kernel with vibration for niki200/300 on your nike100 and your screen dont freeze?
What's the problem with data connections?
It's android 1.6?
Regards!
ebautista said:
Nice one there. There is seems problem with the hardware keypad. The hardawre keypad works though keypad #1 when pressed twice sleeps nike. Maybe the said button is mapped for that function. Better if we can bring it back to the original function. Thanks again.
Click to expand...
Click to collapse
what do you mean by keypad #1? hardware numeric and alphabetically works on me.
and the android device keypad is different with winmo, in android there are back, menu, end key (CMIIW). so we need to map our device keypad to android one
hansie_k said:
Hey,
I copied everything onto my SDcard, into the /andboot directory
Haret.exe starts, holding the D-pad...Linux starts etc, but...then it hangs with an error "sh: 2 unkown operand
losetup: /dev/block/loop1: No such file or directory
Failed
Failed to reach system.img on SD card"
And from there on every button I press gives my weird syntax...
anybody knows what I'm doing wrong..?
Click to expand...
Click to collapse
when it tolds to hold d-pad, try to hold it or press it twice,it will come to installer screen, then install it first, after that you can boot android
vocione said:
Installed on ext2 partitions, now take some tests on my nike 100.
Problems I found:
- On boot I have Voice Search not responding.
- If I try to set mms settings the apn disappear (i use Wind in Italy), setting only apn and name work (i'm syncronizing with gmail)
Thanks a lot for this tutorial!
Click to expand...
Click to collapse
voice search: i don't use that, maybe that is the build error
never set mms, but if we set apn other MNC and MCC then it will disappear on apn list but it do work, myn is trying to fix this problem
Maxxd01 said:
Many thanks for this post.
Three questions:
You are using kernel with vibration for niki200/300 on your nike100 and your screen dont freeze?
What's the problem with data connections?
It's android 1.6?
Regards!
Click to expand...
Click to collapse
yes, my screen is not freeze
data connection?my apn setting no showing on apn list but it do connect, but sometimes i find it is more difficult to make connection, don't know if it is eclair probelm or network problem
no, it is eclair, android 2.1
waiting for froyo to come here
youngsien said:
voice search: i don't use that, maybe that is the build error
never set mms, but if we set apn other MNC and MCC then it will disappear on apn list but it do work, myn is trying to fix this problem
Click to expand...
Click to collapse
youngsien said:
yes, my screen is not freeze
data connection?my apn setting no showing on apn list but it do connect, but sometimes i find it is more difficult to make connection, don't know if it is eclair probelm or network problem
no, it is eclair, android 2.1
waiting for froyo to come here
Click to expand...
Click to collapse
The APN editing issue is caused from the paid market enabler script that is running as a service. It is trumping changes made to the APN list.
I am going to talk to dzo about making the same changes he made in the Donut ril for me. This should hopefully eliminate this issue.
The Voice Search Wait/Force close on start is a known issue and unfortunately in this build is more of an annoyance. For now just click the "Wait" button.
Okay, tested it today almost the whole day, started with full battery at 08.00, very surprised about the graphics and the response of my Niki, lot's of stuff are working, internet connection worked, hardware keypad was working normally, Gmail working, incoming and outgoing call's working, sms working.
Only tested those things because it's a phone and those things are the most important for a phone (my opinion).
Try to acces my sim-card to add contacts but wasn't able to do that.
Okay at 19.45 my battery is empty, be aware my battery is 3 years old.
Conclusion, for me it is a perfect working phone, sometimes you need a little bit patience to let the phone do his job.
Thanks youngsien
Any chance of getting CDMA functionality for this?
youngsien said:
when it tolds to hold d-pad, try to hold it or press it twice,it will come to installer screen, then install it first, after that you can boot android
Click to expand...
Click to collapse
I've tried after I read this reply , ( try to hold d-pad or oress it twice)...
It's still not work.
maybe we need the file = "system.img") that not provided on sdcard.
myn said:
The APN editing issue is caused from the paid market enabler script that is running as a service. It is trumping changes made to the APN list.
I am going to talk to dzo about making the same changes he made in the Donut ril for me. This should hopefully eliminate this issue.
The Voice Search Wait/Force close on start is a known issue and unfortunately in this build is more of an annoyance. For now just click the "Wait" button.
Click to expand...
Click to collapse
hey, the creator Myn is here, is it ok if i post your build in here? i hope nike user can has some fun to get android run on their device.
Can you please talk to dzo to make bluetooth enable for nike too? i think this is the minus one for nike user, kaiser and polaris even can use wifi and bluetooth but for us nike user, we don't have wifi but we can't use bluetooth also
will wait for your next release. thanks.
Rataplan said:
Okay, tested it today almost the whole day, started with full battery at 08.00, very surprised about the graphics and the response of my Niki, lot's of stuff are working, internet connection worked, hardware keypad was working normally, Gmail working, incoming and outgoing call's working, sms working.
Only tested those things because it's a phone and those things are the most important for a phone (my opinion).
Try to acces my sim-card to add contacts but wasn't able to do that.
Okay at 19.45 my battery is empty, be aware my battery is 3 years old.
Conclusion, for me it is a perfect working phone, sometimes you need a little bit patience to let the phone do his job.
Thanks youngsien
Click to expand...
Click to collapse
yup, seems like battery problem still there,can't compare to winmo. Lose in battery, bluetooth, and camera. hey you can manage it for a long time, do you have data always on?how was you using it?
88fingerslukee said:
Any chance of getting CDMA functionality for this?
Click to expand...
Click to collapse
don't know about that. soryy....
Dricos said:
I've tried after I read this reply , ( try to hold d-pad or oress it twice)...
It's still not work.
maybe we need the file = "system.img") that not provided on sdcard.
Click to expand...
Click to collapse
no, system.img is created in /andboot when installing, no need to copy file "system.img". here is the step i usually use. when starting haret and hit run, lot of text (linux boot style) come out. ok from now press and hold center d-pad, after some page it will halt with the message "press center d-pad to....." then release your 1st d-pad hold then press and hold once again. you should see some weird code on your screen but that's ok. after that you will come to installer screen to make system.img and data.img on your sd.
hope you understand, sorry for my english
thanks
youngsien said:
don't know about that. soryy....
Click to expand...
Click to collapse
Darn.
I think it actually already has CDMA functionality since this came from the Vogue thread, but I'm not unsure as to how to get the default.txt file right so that it will boot. Does anybody know of a guide to the the android linux boot commands? It's possible that the devices differ enough to require some different commands.
88fingerslukee said:
Darn.
I think it actually already has CDMA functionality since this came from the Vogue thread, but I'm not unsure as to how to get the default.txt file right so that it will boot. Does anybody know of a guide to the the android linux boot commands? It's possible that the devices differ enough to require some different commands.
Click to expand...
Click to collapse
theoritically is right, but i don't know about that, do you ever asked mblaster on his nike myn donut thread?he is more master in this, because he can compile zimage kernel for nike. maybe he know the answer.
Hi all, I've tested yesterday and this morning...
I found it unstable, after I have set the apn I tried to sync with gmail accont, but never work (always "problem with the sync" reported).
Sending and receiving sms work, make calls work difficult, sometimes i heard but on the other side doesn't hear me.
I try to reinstall and don't set the APN, but anything solved.
Last, after reinstall, when I call it goes to sleep mode but no more wake up (using camera button twice, or other buttons).
I'll do more test, hope this can help.
Bye
p.s. sorry, I speak english only a little bit
Hi all,
Nice build...
Anyway, although it's very hard to resist, imho it's a good idea to wait a few more days until Myn releases the next Versions. If you follow the original Thread in the Vogue forum, you'll see that there are still a lot of problems even for the Vogue Users. For that reason it's probably a good idea to wait until the big one's have been fixed...