Related
Hello folks
Some of you will probably know that i am running 2.06WWE with orange ext rom on my M1000.
After several days of testing different settings etc and after talking with darren_the (respect to you man) and with help from SIN,
I finally have my M1000 running WM2003SE with BT activesync and BT Headset running 100% - just like i want it
My question is this :-
Does anyone know why the BT headset today plugin keeps disappearing and can this be fixed as it is really annoying.....
cheers again for everyones help.
(gonna go and play know)
BT headset today plugin keeps disappearing
This happen to version 2.02Ti & 2.06
as far as I know
:twisted:
Hi darran mate, i gathered that..... is they anyway to fix it
u said that u're using 2.06, but AFAIK it's the most bugged version of all the four (2.02, 2.06, 2.2CHS, 2.2ENG-TRANSLATED)... have you changed anything, ext-rom aside?
Anonymous said:
u said that u're using 2.06, but AFAIK it's the most bugged version of all the four (2.02, 2.06, 2.2CHS, 2.2ENG-TRANSLATED)... have you changed anything, ext-rom aside?
Click to expand...
Click to collapse
tought i was logged-in.. :? :? 8) :roll:
Seems to work okay for me, it does what i need it to do so.....
I tried 2.02 first a while back but could not get me BT headset to work with handsfree (no mic)
Went back to 172, for a while and tried various landscape and skinning apps, nothing was really 100% so went back to 2.06/w.02 merged from sin.
This worked great with my bt headset in headset mode and bt activesync, but i hard reset by accident and ended up with 2.06 basic
everything still worked so i'm sticking with it until sin gets his merged rom single update package uploaded or buzz lightyear completes his translation of the 2.20.07 chs rom.
Hey everyone....for some strange reason, whenver i get a call or text message the ringer or notification stays on even when im the call. I noticed this in some of the later DCD 2.2.x roms. IS anyone else having this problem or know how to fix this...any help is greatly aprpeciated
me too
I noticed this as well just upgraded yesterday using the newest sprint, then puting in a cooked DCD...Thanks, I love it, but the notification(vibrate) stays on and I get no sound from the speaker (media player, ringer, etc)...still searching for a solution
Bratcop said:
I noticed this as well just upgraded yesterday using the newest sprint, then puting in a cooked DCD...Thanks, I love it, but the notification(vibrate) stays on and I get no sound from the speaker (media player, ringer, etc)...still searching for a solution
Click to expand...
Click to collapse
my problem is a little different, im getting too much sound....lol....when im on a call and i receive another call or text, i still hear the ringtone for that action and it usually repeats itself a couple times making it so that i cant hear the person im talking to on the phone. I think i read somewhere that what ur talking about maybe due to picking Lockstream DRM as an option in the kitchen....did u do that?
not I
I didn't cook it myself, downloaded it complete. I added the registry entries I found on this board and I am closer. I still don't get a ring, bur media player now plays and the phone always vibrates when a call. It just seems a little fishy on the ringer end of things...
did you guys that cooked the rom all include the Lockstream DRM package when you built?
if so, I have some problem with the package, and leaving it out of your ROM might resolve your problem for now.
let me know.
DCD, thanks for the help with the ROM and the Kitchen! I haven't cooked up anything yet but I am sure I will give it a try.
Could this be the cause of the problems I am having...I loaded Olipro 2.40, then applied the latest Sprint ROM to my Alltel phone. This gave me the newest radio 3.35.04. I then loaded your final version 2.3.2. I have the ringer issue detailed above, as well as no camera function...I am considering reloading your 2.3.2, then going with the radio 3.27. Also, what's the deal with the PRL file, do I need to change mine from 30029 to something else?
Thanks again man...if you aren't already, you are gonna be a wealthy man some day...
dcd1182 said:
did you guys that cooked the rom all include the Lockstream DRM package when you built?
if so, I have some problem with the package, and leaving it out of your ROM might resolve your problem for now.
let me know.
Click to expand...
Click to collapse
DCD, i didnt use the Lockstream DRM package. Im not sure when i noticed this....i know its happening now and when i was using that later of ur 2.2.X series....maybe its something that happens normally and im just now noticing it, but i dont remember if even the stock roms did this....am i supposed to her the ringtone and notifications when im on the phone? is that common?
PS...thanks for ur hard work on this stuff, ur roms are great
sorry
sorry to get this thread careening off course
I found more info on the dropped speaker on this thread...
http://forum.xda-developers.com/showthread.php?t=376012&page=15
Thanks again.
I'm on a 5060 build using the Kitchen. I have HTC Home, S2U2, and anything else that was defaulted in the settings from the basekit.
I had the same problem on DCD 3.0.1 and nue 5054 and 5059. I was told it was advanced config, so I reflashed 5059 without AC, then 5060 without it. The device worked great yesterday, but this morning I couldn't answer the phone again.
I had found something that added a change soft key setting to the systems tab, I installed that and changed the setting to messaging instead of calendar, and that's when the issue returned, so I figured it was something to do with the that. I did a hard reset but the issue still remains. My next resort is a re-flash, but I really don't want to go through all that if I can avoid it.
clamknuckle said:
I'm on a 5060 build using the Kitchen. I have HTC Home, S2U2, and anything else that was defaulted in the settings from the basekit.
I had the same problem on DCD 3.0.1 and nue 5054 and 5059. I was told it was advanced config, so I reflashed 5059 without AC, then 5060 without it. The device worked great yesterday, but this morning I couldn't answer the phone again.
I had found something that added a change soft key setting to the systems tab, I installed that and changed the setting to messaging instead of calendar, and that's when the issue returned, so I figured it was something to do with the that. I did a hard reset but the issue still remains. My next resort is a re-flash, but I really don't want to go through all that if I can avoid it.
Click to expand...
Click to collapse
What do you mean you cannot answer your phone?
The calls don't go through, you cannot use the send key, what's up?
I press the answer softkey or the hardware key, and it doesn't work most of the time. It will mute the ringer, but will not answer the call.
This has been discussed elsewhere in this forum and on brand X. I also had a problem with the phone not answering. If you believe what they say....and I've tried it and it seems to be working for me now......reload a ROM without Advanced Config. This seems to be the common thread to the problem....Now my calls answer almost immediately. Try it...see if it solves the problem
I did that. My 5060 build didn't have AC in it at all.
Do you have SPB Pocket Plus installed? I had the same problems, but it hasn't returned since I uninstalled PocketPlus...
Nope. No SPB. Only default 5060 basekit and HTC home/S2U2.
I've actually gone ahead and re-flashed back to Sprint 3.35, which sucks because I really really liked the 6.1 threaded SMS, but a phone that I can't answer doesn't really do me any good.
I'll just have to wait for an official 6.1 I guess.
clamknuckle said:
Nope. No SPB. Only default 5060 basekit and HTC home/S2U2.
I've actually gone ahead and re-flashed back to Sprint 3.35, which sucks because I really really liked the 6.1 threaded SMS, but a phone that I can't answer doesn't really do me any good.
I'll just have to wait for an official 6.1 I guess.
Click to expand...
Click to collapse
the new PocketCM comes with threaded text..
A little update.
The GPRS_bye_if_device_off registry hack is what was causing me not to be able to answer my phone. It was supposed to improve battery life.
I had ran no2chem 5060 for a few weeks without it happening, then went to DCD 3.0.4 and it didn't happen until last night, I tried that hack. Sure enough, after the reboot, that hack is what did it. I was doing this hack just to test that theory so had a back up. I restored it and now the phone works properly again.
Anyone else having a wierd loud noise when a call waiting comes in? I fisrt got this after flashing radion 3.42.30 and dcd 3.2.2
I flashed to dcd 3.23, and it was still there.
I re-flashed the radio, and its still there.
jtg
(33)
yeah, I recently noticed it as well. It sounds like an alarm of some sort. Very annoying
omg yes it happened to me last night. That is horrible. Anyone have any idea what that could be? I am running DCD3.2.3 with 3.42.30 radio
I had that exact thing happen with the 3.42.02 radio from the official sprint rom. I recently switched to 3.42.30 and I've yet to experience it again. Infact I just tested it before I made this post. I know thats not much help since you all have the .30 radio, but just wanted to pass along my experience. I guess the only other thing I have done differently is before I updated the radio to .30 I switched from SPL 2.40 to 2.47.
Perhaps try doing a fresh install of the radio and then the rom+cab?
JerrytheGreat said:
Anyone else having a wierd loud noise when a call waiting comes in? I fisrt got this after flashing radion 3.42.30 and dcd 3.2.2
I flashed to dcd 3.23, and it was still there.
I re-flashed the radio, and its still there.
jtg
(33)
Click to expand...
Click to collapse
i heard it was a diamond call waiting sound if so i hate it
Hmmm...I guess I should go look for a new radio and see if it changes.
Any of the heavy hitters want to chime in?
dcd? gc14?
rickyrecaro said:
i heard it was a diamond call waiting sound if so i hate it
Click to expand...
Click to collapse
No way....It is a ear screeching sound that stops you mid sentence while talking. I was like "Holy S***t, One second please my phone is acting up" to a customer I was talking with.
i just get this weird little noise in the beginning of a outgoing call, and for some reason the phone app itself pops up after i close a window to an app.
i get that alarm sound too. its kinda random. sometimes on BT it sounds fine. but its not the radio its the rom i think. i never had the issue when i was on 3.0.4 and 3.42.30
DCD bug?
kflipproductions said:
i get that alarm sound too. its kinda random. sometimes on BT it sounds fine. but its not the radio its the rom i think. i never had the issue when i was on 3.0.4 and 3.42.30
Click to expand...
Click to collapse
DCD-u reading this? Do you think we've got a bug? I'm on alltel--others--is it carrier specific?
What dialer are you using?
the vogue dialer-dcd's default
I'm using dcd's kitchen, no OEMs added, just enterprise, entertainment, vc, and everything else as defaults.
I'm on alltel, I do use activesync with exchange, spb pocketplus, google maps, livesearch, htc gps viewer, and wififofun2.
jtg
gc14 said:
What dialer are you using?
Click to expand...
Click to collapse
Diamondish Black Titan Dialskin v.2.23
kflipproductions said:
Diamondish Black Titan Dialskin v.2.23
Click to expand...
Click to collapse
It's not the custom dialer that is doing this, because the custom dialer is just a skin (images) .
It's the Vouge Dialer found in the kitchen.
I cooked the Vouge dialer and got that annoying sound when ever I have call waiting.
I did not use the kitchen just the dcd rom 3.2.3 and radio 3.42.30...It is really getting annoying now.. anyone have any ideas?
I have the call waiting problem too. I first hear the regular call waiting sound followed by about five loud beeps that sound like someone keeps pressing a button on the other end.
It's not the custom dialer that is doing this, because the custom dialer is just a skin (images) .
Click to expand...
Click to collapse
Not every custom dialer is just a skin with images.
My thoughts
If you happen to own an old phone with caller ID that doesn't support call waiting/caller id, then you will hear a very similar sound. I believe that loud noise is actually the caller ID info being sent, on a standard pots phone it's only sent once, but it's possible that cells send multiple bursts in case the phone misses one of them.
Then again, I, who know nothing, is just giving my 2 cents on this.
BTC
gc14 said:
Not every custom dialer is just a skin with images.
Click to expand...
Click to collapse
True. But I was referring to the custom dialer he is using. Because I helped create it.
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!