I recently purchased an unlocked T-mobile Dash and activated it with Rogers. I got the two lines put on it(one business number, one personal number). Everything is working fine, I receive calls, txt and voice mail through both lines. Unfortunately I cannot seem to be able to make outgoing calls through the 2nd line.
I was wondering which if any of the wm6.1 firmwares or perhaps a add-on program would be able to activate the line selection on the phone. I am currently using the T-Mobile WM 6.0 firmware.
I have spent the better part of 5hours searching these forums and new firmwares but cannot find anything on the 2nd line support.
Any help is greatly appreciated.
Please any help would be appreciated. Someone must know if any of the 6.1 firmwares would have this feature enabled. I have tried looking but there nothing in the firmware notes.
I would rather not have to update one at a time.
motaguy said:
I recently purchased an unlocked T-mobile Dash and activated it with Rogers. I got the two lines put on it(one business number, one personal number). Everything is working fine, I receive calls, txt and voice mail through both lines. Unfortunately I cannot seem to be able to make outgoing calls through the 2nd line.
I was wondering which if any of the wm6.1 firmwares or perhaps a add-on program would be able to activate the line selection on the phone. I am currently using the T-Mobile WM 6.0 firmware.
I have spent the better part of 5hours searching these forums and new firmwares but cannot find anything on the 2nd line support.
Any help is greatly appreciated.
Click to expand...
Click to collapse
I have two lines but I use a dual SIM adapter which allows me to switch between the lines for outgoing calls via an interface. This may be the way you have to go as well as I do not know of any other way to do it.
Well, I finally decided to try and put the Rogers firmware on the phone, that seems to have solved the line issue. It still would be nice to know if any of the 6.1 firmwares have the line selection in the phone options.
Bupahs said:
I have two lines but I use a dual SIM adapter which allows me to switch between the lines for outgoing calls via an interface. This may be the way you have to go as well as I do not know of any other way to do it.
Click to expand...
Click to collapse
That is the most common way it is done, and it is the only way I know works for sure... So if anyone wants to do this I would recommend doing it...
Hi Guys,
I've just ordered 17 touch pro 2's for work and I'm very impressed with them so far. Absolutely awesome phone. We've just got one issue which is the fact that when the phone is locked (we used centralised policies with exchange) you can't dial from our Parrots. The phone says you must unlock the device to allow bluetooth connection.
Does anyone know a way around this without taking the locks off of the phone which is a big no no. Tested it with a collegue's Omnia and it works fine.
You can replicate this issue by using the Bluesoleil dialer which is what I've been doing for testing.
The parrot receives calls fine, just can't make them he the phone is locked.
TIA.
Same problem
Hi there,
I'm having the same issue for dialling out via bluetooth whilst the phone is locked. The TP2 says it needs to be unlocked before answering the call.
There MUST be some registry key to change to prevent this "feature" ... none of the previous HTC phones I have had have had this problem.
Thanks in advance for any help!
i have the same problem, i installed s2u2, which solves the not being able to dial out when its locked, but it's not the most reliable solution.
i'd rather have it working like it did on my kaiser before this phone.
hope someone helps us out.
I tried out S2U2, but the problem is it's only a keypad lock, so plug the phone in USB for example and you still have full access to the device.
S2U2 also does not stop you sliding out the keyboard and pressing the mail button to read the emails on the phone, so this isn't a solution we can use, it's not even a compromise
Haven't had much luck with HTC support either. They are very quick to respond but don't respond with anything of value.
I just wanted to bump this thread -- I picked up a Tilt2 and have the same problem -- really annoying when trying to dial from the car and having to unlock (didn't have this issue on my Fuze).
Yeah this is the most annoying thing I have ever seen. There must be a way to turn it off. I use Ford Sync and really don't want to have to worry about my phone being locked or unlocked. Seems like this goes against all those phone laws. You are making me look at my phone first to make sure it isn't locked before I can safely dial.
Wish I had found this thread before I went ahead with getting a Tilt 2. Didn't have this problem with my Tilt.
Is this a WM6.5 limitation? Hopefully there is an obscure setting that I'm too stupid to find.
Cheers
... and I was just about to ask on this thread whether or not this was still a problem in WM6.5 but I guess I have my answer now.
It's definitely an issue in WM6.0
I contacted AT&T and they said to contact HTC.
HTC gave me this answer:
Thank you for contacting HTC Technical Assistance Center. I apologize for the length of time it took me to respond to your email. I understand how important it can be to use Bluetooth from your device when your device is locked. I will be happy to address the concern for you.
There is not a setting on your ATT Tilt 2 for enabling Bluetooth when your device is locked. When pairing Bluetooth with your vehicle your device must remain unlocked to use the correct functionality. I would suggest placing your device into hibernation mode and keeping your device in a carrying case.
Hi,
I have upgraded by TP2 with the offical HTC rom for 6.5 and installed my blackberry connect 1.06 client. Now, even with the BB lock enforced, as it was with the TP2 using 6.0 and it is working perfectly handsfree in my CAR, locked or not. Previously the TP2 with the stock 6.0 ROM wouldn't make calls when locked.
If people are reporting here that is didn't work in 6.5, then there must be a registry setting somewhere to enable or disable it.
I am just happy that I can make a call in the car, without having to pull over and unlock my phone.
If someone can give me a hint as to where in the registry to look I can compare some settings?
I have a stock AT&T Tilt-2, I loaded loaded "smartlock 1.7" to autolock the phone at power off and also when "in-call" to avoid random dialing. I don't use the PIN for locking.
I can dial hands free BT in my car and with headsets with no issues, power on/off whatever.
Maybe it'd disabled when locked with the PIN?
I am seeing the same issue with two of my users:
One is using a Verizon Wireless TP2 with MW6.1 stock ROM
The other is using an Unlocked HTC touch Pro 2, on the AT&T wireless network (not a Tilt2) with the HTC WM6.5 ROM upgrade.
The Verizon users is using Sync on his Ford Vehical. The other is using whatever system is in his BMW.
Both can pair with the car's system, but if the phone is locked with a PIN the user is not able to place a call without first unlocking the phone.
Has anyone found any information on this?
If MSVC is an option then it has the ability to dial while password protected.
Just noticed this has been bumped. I upgraded all of our phones to the standard Windows Mobile 6.5 from Vodafone when it came out a month ago and this problem is now resolved you'll be glad to know.
I've got 25 handsets currently working fine with no real issues. All the niggles that I had have gone away with 6.5 so it's definately worth the upgrade.
6.1 was screwed and no use with handsfree dialing if you use windows lock which we enforce on our exchange server.
Seems like every provider is a little different.
I have the AT&T Tilt 2 which came with WM6.5, AT&T support claims its a Microsoft and HTC problem. HTC claims its a Microsoft problem.
Anyone have a good support link to Microsoft to get this problem resolved?
Can someone with a working 6.5 rom please post the following registry info to see if there is a way to enable the bluetooth dialing on the roms that are not working?
HKLM\Software\Widcomm\General
When you get the unable to dial message it puts a new key in there called DontAskHfpCallFailOnDeviceLock and I figure that the bypass might be in this same area.
Registry
Here is everything under the BTConfig\General section.
[HKEY_LOCAL_MACHINE\Software\WIDCOMM\BTConfig\General]
"StackMode"=dword:00000001
"DeviceName"="HTC-ST7377"
"BDAddr"=hex:\
00,23,76,37,a9,89
"BlockBTIfHopper"=dword:00000001
"SendCompressedTelProperties"=dword:00000001
"UsePocketPCName"=dword:00000000
"UnnamedDeviceName"="<No Name>"
"UartPriority"=dword:00000096
"TransmitPriority256"=dword:00000098
"SuspendWithScoConnected"=dword:00000001
"SuspendTimeout"=dword:00001388
"SndPriority"=dword:0000009b
"SecurityType"=dword:00000002
"SCODelayTime"=dword:000007d0
"ReceivePriority256"=dword:00000097
"RadioInitLibrary"="BRCMInit.dll"
"PowerControlLibrary"="Serial_BTUR_DM.Dll"
"PCRemoteAutoConfig"=dword:00000001
"OriginalAudioDriver"="wavedev.dll"
"KeepStackLoaded"=dword:00000001
"EnableAFH"=dword:00000001
"DiscoverableTimeout"=dword:0000003c
"DeviceInactivityDuration"=dword:0000003c
"ConnectRelatedDefault"=dword:00000000
"BIPEnabled"=dword:00000001
"AFHAvoidedChannels"=dword:00000014
black88mx6 said:
Can someone with a working 6.5 rom please post the following registry info to see if there is a way to enable the bluetooth dialing on the roms that are not working?
HKLM\Software\Widcomm\General
When you get the unable to dial message it puts a new key in there called DontAskHfpCallFailOnDeviceLock and I figure that the bypass might be in this same area.
Click to expand...
Click to collapse
erenken said:
Here is everything under the BTConfig\General section.
[HKEY_LOCAL_MACHINE\Software\WIDCOMM\BTConfig\General]
"StackMode"=dword:00000001
"DeviceName"="HTC-ST7377"
"BDAddr"=hex:\
00,23,76,37,a9,89
"BlockBTIfHopper"=dword:00000001
"SendCompressedTelProperties"=dword:00000001
"UsePocketPCName"=dword:00000000
"UnnamedDeviceName"="<No Name>"
"UartPriority"=dword:00000096
"TransmitPriority256"=dword:00000098
"SuspendWithScoConnected"=dword:00000001
"SuspendTimeout"=dword:00001388
"SndPriority"=dword:0000009b
"SecurityType"=dword:00000002
"SCODelayTime"=dword:000007d0
"ReceivePriority256"=dword:00000097
"RadioInitLibrary"="BRCMInit.dll"
"PowerControlLibrary"="Serial_BTUR_DM.Dll"
"PCRemoteAutoConfig"=dword:00000001
"OriginalAudioDriver"="wavedev.dll"
"KeepStackLoaded"=dword:00000001
"EnableAFH"=dword:00000001
"DiscoverableTimeout"=dword:0000003c
"DeviceInactivityDuration"=dword:0000003c
"ConnectRelatedDefault"=dword:00000000
"BIPEnabled"=dword:00000001
"AFHAvoidedChannels"=dword:00000014
Click to expand...
Click to collapse
erenken,
Thanks for the info. The only item different on my 6.5 Tilt2 is that I also have a key "DontAskHfpCallFailOnDeviceLock"=1. Sounded very promising.
Unfortunately, changing this key to 0 and even deleting it doesn't make a difference: I still cannot dial via bluetooth while the phone is locked with a pin. I tried these changes both with and without a soft reset between.
mnunes:
Were you able to find a fix for this? I am in the same boat.
DaBody1 said:
mnunes:
Were you able to find a fix for this? I am in the same boat.
Click to expand...
Click to collapse
No, so far no luck. I can't say I've been looking very hard, though. It's one of those things I've started to learn to live with, as annoying as it is.
I just picked up a Note II from Sprint and it had 4.1 on it. I connected it to my Jeep Wrangler (2012 Unlimited) UConnect Radio (Model 130) and everything worked great when making a phone call. (I first this last friday tried a Note 3, but that wouldn't make calls at all from my jeep and Sprint said that they know and it might never be compatible, so I had to return it and swapped it out for the Note II on monday.)
The phone then upgraded to Android 4.3. Now I have a unique Bluetooth issue that I have exhausted searching for an answer to but cannot find one.
The phone will answer calls just fine through the UConnect radio, and it will make calls to some people just fine through the bluetooth. But when I call some people it will ring thought the speakers just fine, and then when they answer the UConnect radio announces "Call Ended." However the person is still connected and it still shows the bluetooth connected just fine in my action/notification bar and the headset button in the call is still highlighted green. But I have to hit the speaker button to speak top the people at that point. Again, this doesnt happen on every call so thats why I am confused.
I have found a solution however, and this is where I need the help of one of the superusers on here. (To preface this, I have read about 150 posts online about the Note 2 and bluetooth issues. I have deleted and repaired the phone from the Jeep UConnect and removed the Uconnect from the phone about 20 times. I have tried Bluetooth Auto connect, I have tried Tasker, I have tried disabling the media audio option, IU have tried bth allowing MAP and not allowing MAP. I have tried both allowing the phonebook and call history download and tried not allowing it. I have called Sprint...NO HELP, and I have called Jeep...NO HELP. Both Sprint and Jeep told me there were no firmware updates available to fix this (Jeep said they cant do firmware updates on my radio) and Sprint said there were no plans to fix this kind of bug in the future)
When the UConnect announces "Call Ended", I can drag down my top action/notification bar, click on the gear for settings, click on Bluetooth, then click on the UConnect gear for settings, uncheck the "Call audio Use for phone audio", and then re check it. Once this has been rechecked, the Uconnect picks back up the audio just fine and I can continue the call on the radio handsfree like it is supposed to be.
I live in CA where is is required to be handsfree so I really need a solution to not fumble with the phone for 10 seconds trying to make it do what it should do automatically. (Like my 4 year old Galaxy S2 did just fine).
I have tried tasker but cant seem to find a way to make it perform those steps I need.
My big question then is this... Is there an app or someone that knows how to write a simple app that would simply disable then re-enable the call audio checkbox under the Uconnect settings with the press of one button. or the press of an app icon from the home screen or something. Or has anyone seen this and knows of a fix?
Sorry for being long winded, just want to make sure the problem is clearly explained. I am truly at my wits end.
Thanks in advance for any help you can give, it is greatly appreciated.
So couple questions. Are you pure stock, got root, custom recovery?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Sorry, guess I forgot that part.
I am pure Stock Sprint (Afriad to try a rom yet since my friend bricked his Note II)
Android Version 4.3
Android Model SPH-L900
Build JSS15J.L900VPUBMK4
Hardware Version L900.09
Kernel version 3.0.31-2106854
I have a Samsung Galaxy Note 4 Edge from Verizon. Everything worked fine on the phone until one day a problem just occurred and even with the help of Verizon’s tech support, I haven’t been able to resolve it. The problem is whenever I receive an incoming call, the caller cannot hear a tone when I press anyone of my dial pad keys. This makes it impossible to proceed through an automated system that requires you to press certain numbers in order to advance. NOTE … I only experience this problem on incoming calls! If I initiate the phone call, the party I’ve called can hear a tone whenever I press a key on my dial pad. That means I can place a call to an automatic system and proceed through it by pressing the keys necessary to reach my desired destination.
Verizon’s tech support suggested that I reset my phone to its new, out of the box condition. I did that and it didn’t fix the problem. I tried starting the phone in safe mode, thus taking any 3rd party apps out of the equation and that didn’t help. I tried changing the DTMF setting from normal to long and that made no difference. Finally Verizon sent me out a new phone and that didn’t fix the problem. And last but not least, Verizon gave me a new sim card, which still didn’t fix the problem. Now I have all new hardware and the same old problem! Verizon keeps bumping me up the tech assist ladder, but so far no one has come up with a solution.
If anyone has any ideas, thoughts or suggestions that would help to solve this mystery, I would be eternally grateful!
Thanks in advance!
Good luck! I'm on my 4th replacement and still have all of the same problems. Now they are sending the phone to Samsung to tear apart and checking my cell area for related problems. Both mine and my wife's note 4s are plagued by the same problems. I guess the next step is trying a different manufacturer.
Sent from my SM-N910V using Tapatalk
I had his same issue on Verizons iphone 6 and iphone 6 plus, could never get through automated menus.
Now that I think of it, I have had this issues on my G4 and G3 and pretty much any device on Verizon.
Hi guys, first of all, im currently running one ui 5 android 13
I have tried a lot of apps to record phone calls and every time the recorded audio sound is blank
I have seen that this is due to google politics or something, do u know how can i record it.
I want to be able to record it because several people have told me they stop listening to me properly during phone calls, but i listen to them good. Its not problem of my SIM because in other phones i dont have that problem and samsung technical support already "fixed my phone", i even sent them my phone so they would fix it.
Im pretty dissapointed with this phone.
Any suggestions of how can i record a phone call or even better, if u know any solution of my problem with the calls? Thanks!
The easiest solution is to use native samsung call recording. You can use this method, worked for me as well: https://forum.xda-developers.com/t/...ith-galaxy-a52s-solved.4423477/#post-86660135
I chose XID as well. When downloading new ROM to extract HOME_CSC from, be sure to download the same version, e.g. A528BXXS1DVL2 for A13 with December 2022 security patch, you can find the version in "software update" in settings as the first string after "current version".