Related
I now run gingerbread as my daily rom and it is awsome. One feature that has been added recently is the vibrate after call is connected. I was wondering if it is possible to disable this feature? Full details of the rom and phone are in my signature below. It is an awsome rom and would recommend it. Love working led lights and usb mas storage. Just would really like to disable the vibrate.
I would like to keep the main vibrate option available so that when I do have an in comming call I can keep the phone on silent/vibrate mode.
im not sure about that rom but it should be under settings, call settings.
montecarlo5 said:
im not sure about that rom but it should be under settings, call settings.
Click to expand...
Click to collapse
I think it was an option the chiefs put into the rom rather than a native function. I was just hoping to be able to disable it again. I know it is not on other gingerbread roms, but I like the functionality of this one and would just like to disable it.
Ahem...24 thanks and not able to go to settings, call settings, and uncheck "vibrate on answer"...?
Sorry I'm rude, but XDA servers, although they cannot talk, just agree you shouldn't have posted ANOTHER thread. This is just useless cluttering.
My 2 cents.
And no, it's been answered before, and wasn't worth a thread. Just so u know.
Like there or elsewhere.
RedWave31 said:
Ahem...24 thanks and not able to go to settings, call settings, and uncheck "vibrate on answer"...?
Sorry I'm rude, but XDA servers, although they cannot talk, just agree you shouldn't have posted ANOTHER thread. This is just useless cluttering.
My 2 cents.
And no, it's been answered before, and wasn't worth a thread. Just so u know.
Like there or elsewhere.
Click to expand...
Click to collapse
In Gingerbread gone into settings -> call settings and options I have are:
Fixed Dialing numbers
Voicemail Service
Voicemail settings
Call forwarding
Aditional Settings -> Caller ID Call waiting
Accounts -> Receive incomming calls
Use interet calling
Nothing regarding the vibrate on call answer. If you have a look at the thread the rom, the Chief actually added that option him self. I think he modified the framework file to enable it. I have used other gingerbread roms that do not have this function and just wondered if it is possible to disable it by changing the code.
I have also disabled all other Haptic Feedback settings in the sound and keyboard options, and gone in to the phone dialer to see if there are any native settings there. I might be able to fix it by downlaoding another dialer and using it, but I would prefer to use the native dialer if possible.
That was also the reason why I created this thread as it is a spesific option on this build. I did ask the question on the orgional rom's thread but did not get any reply. It may not be possible to do which is fine but I was just curious.
I was having same problem with my Thunderbolt....my problem turned out to be the "profile" setting I was on. I went back to the default profile and it solved my problem.
I no longer run gingerbread, and I'm on my cell so I can't see your signature. But at one time vibrate on answer was a standard feature, and could be disabled in the settings, just like stated above.
Sent from my HD2 using xda premium
Dunno if I'm just crazy. I could have sworn at some point I saw an option on my Epic 4G to speak the incoming caller ID out loud. Am I not looking enough? Was it Cyanogenmod I saw it on? Or am I just delirious? If so, could you please help me find an app good enough at doing this, no battery drain, and possible to listen to through bluetooth? I'd love it (not need it) if it also spoke incoming message sender.
There was an option in 2.1 stock rom to enable vocal caller id, but it has been removed in 2.2. So far I haven't seen it in any roms that I've tried, including the unofficial leak. It really irks me that it was removed. I posted about it a while back and didn't get any response.
Caller I'd reader on the market reads the names and numbers out aloud. Hope it helps
Sent from my Evo Killer!!!
I prefer "SayMyName" found on the market. Can read incoming calls, texts, emails and tweets as well as their contents if you so choose. Has a text replacer too for those hard (or poorly) pronounced words/names so you can specify how they are supposed to sound. Been using it happily for a bit on various phones and various android versions and rom builds.
Tasker, IMO. That app does everything.
I'll put in a vote for drive safe.ly, look it up...
Unfortunately, I tried all your apps, and they are all great (especially SayMyName), but none of them will speak through my bluetooth headset! That's the whole point, actually. I have yet to try Tasker, which I will now.
Sent from my SPH-D700 using Tapatalk
regarding SayMyName.. did you enable Bluetooth/Headset-support in the Advanced Settings? (very bottom of the options)
Saymyname is an awesome app. I actually use it now. Thanks
Sent from my Evo Killer!!!
REDACTED
FaultException said:
To participate in this poll, download the LATEST CM9 nightly from here, keep everything stock, no kernel changes, framework, or build.prop mods. Follow the instructions in this post, if it fails, do what it says in the post, and provide me with that dumpstate file (via a PM, do not post it here).
* By "completely stock" in the poll question, I mean completely stock CM9, not the stock Android that came with your phone.
* By submitting a poll choice, you agree that you are running COMPLETELY VANILLA CM9; STOCK KERNEL; STOCK FRAMEWORK; STOCK BUILD.PROP
Click to expand...
Click to collapse
For this test, do any of your updated GPS kernels count as stock?
Thanks.
salazar.r1 said:
For this test, do any of your updated GPS kernels count as stock?
Thanks.
Click to expand...
Click to collapse
Yes they do.
Awkward experience, I tested it with my first Vibrant (I have 2) and it didn't work, so i voted The call failed. Then i thought about it, and tried it with my other Vibrant, and returned it to stock CM9, and it worked. Unfortunately the call supporter i got was a big **** about me calling to check in if my location was posted etc. So i didn't call multiple times, but the first time i called with second Vibrant, it worked.
I honestly think its just random for this to happen.
xriderx66 said:
Awkward experience, I tested it with my first Vibrant (I have 2) and it didn't work, so i voted The call failed. Then i thought about it, and tried it with my other Vibrant, and returned it to stock CM9, and it worked. Unfortunately the call supporter i got was a big **** about me calling to check in if my location was posted etc. So i didn't call multiple times, but the first time i called with second Vibrant, it worked.
I honestly think its just random for this to happen.
Click to expand...
Click to collapse
You didn't reboot after the call on your first Vibrant did you? Get me that dumpstate file...
I said in the OP if it fails get me the file
My bad, I actually already flashed another ROM.
I'll get back onto you with that possibly tomorrow. Busy studying for a test tomorrow, so I may get back to you on that. I'll call them again.
xriderx66 said:
My bad, I actually already flashed another ROM.
I'll get back onto you with that possibly tomorrow. Busy studying for a test tomorrow, so I may get back to you on that. I'll call them again.
Click to expand...
Click to collapse
No problem, it's just important to get that file when it does fail, so I can take a look. I raised the note to red letters and a bigger size, so hopefully everyone else that tries will see it.
FaultException said:
To participate in this poll, download the LATEST CM9 nightly from here, keep everything stock, no kernel changes, framework, or build.prop mods. Follow the instructions in this post.
If it fails, provide me with a dumpstate file (via a PM, do not post it here).
The instructions on how to get that file are also in the above link.
* By "completely stock" in the poll question, I mean completely stock CM9, not the stock Android that came with your phone.
* By submitting a poll choice, you agree that you are running COMPLETELY VANILLA CM9; STOCK KERNEL; STOCK FRAMEWORK; STOCK BUILD.PROP
Click to expand...
Click to collapse
Can the dumpstate file be created with terminal? I want to help test, but adb is somehow not working for me. Is there some way that I can produce the file using only commands on my phone?
Thanks,
I tested and reported success in the poll.
I discovered one thing in my testing - it may be of interest to other testers.
I use the "dialer one" app to dial phone numbers. When I dialed 911 and pressed the "call" button, the call did not directly dial - instead I wound up at the built in dialer screen. On the dialer screen "911" was in the number display, and I had to press the "call" button on the build in dialer to actually make the call. Typically a second press of the "call" button is not required to make a call.
Bottom line - when testing 911, if there are any unexpected results, make sure that there is not another dialing application involved in the process. Similarly if there is a real emergency you may want to just use the real dialer.
I hope this is helpful (feel free to leave a thanks if it is
ewillner said:
Can the dumpstate file be created with terminal? I want to help test, but adb is somehow not working for me. Is there some way that I can produce the file using only commands on my phone?
Thanks,
Click to expand...
Click to collapse
Yes:
Code:
su
dumpstate -o /sdcard/CM_dumpstate.txt
ewillner said:
I tested and reported success in the poll.
I discovered one thing in my testing - it may be of interest to other testers.
I use the "dialer one" app to dial phone numbers. When I dialed 911 and pressed the "call" button, the call did not directly dial - instead I wound up at the built in dialer screen. On the dialer screen "911" was in the number display, and I had to press the "call" button on the build in dialer to actually make the call. Typically a second press of the "call" button is not required to make a call.
Bottom line - when testing 911, if there are any unexpected results, make sure that there is not another dialing application involved in the process. Similarly if there is a real emergency you may want to just use the real dialer.
I hope this is helpful (feel free to leave a thanks if it is
Click to expand...
Click to collapse
Maybe Dialer One defers the 911 call to the standard dialer just to be safe.
Hi everyone,
Can someone help me change the default dialer and contacts app? Coming from the iOS land, I find this extreme "blackness" of the default dialer really ugly, and thus I'm desperately trying to get rid of it by using either Contacts+ or Go Contacts. The thing is that every time I make or receive a phone call, the phone defaults to the stock dialer. After some googling around, I couldn't find any definite answers as to whether this is possible.
Many suggested going to App Management, locate the Contacts app and press the "Clear Defaults" button (same for Phone app). Unfortunately that button for both apps is disabled for me.
Any suggestions? Has anyone managed to successfully use another dialer?
Thanks in advance!
You're confusing the dialer app with what you see in call, which is separate. You can change the in call graphics with a change of framework/systemui but it takes a bit of work. Swapping the dialer app for something like ExDialer or Go Dialer won't do anything to what you see once the call is taking place.
Sent from my Qualcomm Galaxy S4
Pagnell said:
You're confusing the dialer app with what you see in call, which is separate. You can change the in call graphics with a change of framework/systemui but it takes a bit of work. Swapping the dialer app for something like ExDialer or Go Dialer won't do anything to what you see once the call is taking place.
Click to expand...
Click to collapse
So essentially, all these dialer apps *have* to revert to the default "in-call" screen simply because they do not support their own? Is this an Android limitation one has to live with, or is there some sort of work around?
It's a limitation of Android. The look and behaviour in call is a fundamental part of the OS, rather than something that can be changed with an APK.
Sent from my Qualcomm Galaxy S4
That explains why I couldn't find anything on that subject. Thanks a lot!
There's nothing stopping you using a custom rom though which may be different. At the moment you're seeing the touchwiz one. If you put stock android on there instead it'd be different, on HTC and Sony phones it'd be different again, etc. Nothing is limited on android, so long as you know enough to be able to edit it. Get root access, and get talking to some custom rom developers who may be able to give you a bit of an insight on how you'd do it. It's not impossible.
Hi everyone,
I've got an ATT I337 running the awesome Hyperdrive ROM version 17.1. Several of us --but clearly not all of us!-- over in that thread have noticed a problem with incoming calls. I think there's a setting somewhere that can fix it, so I'm opening it to a wider audience by posting it here, in hopes someone from this group will know what to tweak.
Here's the specific problem.
If my cell phone receives a call from a known contact "Bob" and Bob's contact info (being a U.S. phone number) is 317-555-1212, so far the phone seems to recognize the call as coming from Bob. However, it reports it as coming from +317-555-1212. When I go into the call log and try to return the call, it dials +317-555-1212, and the extra + causes the system to interpret it as an international call attempt, and the call fails. Cannot be completed as dialed, the message says. If it's an non-contact number, the + is still added. IT's not JUST for contacts.
Let's say Bob leaves a message. The voicemail indicator shows and it says offers to dial *86, the correct access code for voice mail for ATT as I understand it. However, tapping that actually dialed +11 then my ten digit phone number. Call fails.
At the dialpad, pressing and holding 1 to invoke voicemail has the same problem.
In Contacts, contacts are NOT listed with +s, and clicking the call button for them makes them dial OK without a + being prepended.
So, this looks like some international feature is being enabled that I'm not sure how to turn off. Does anyone have any idea how to turn this off? Sorta puts a crimp in the basic phone functionality. Seriously, who actually calls anyone these days? But it would be good to fix.
Please, if anyone has an idea of what might be at the root of this, I would appreciate your help!
Marc
I am confused. Does this only happen on the Hyper rom or all roms for you.
Not sure how anyone else does their contacts. But, I always enter numbers as 1-555-555-5555 even if local.
My voicemail number is set as +15555555555
I never had issues--
I remember some talk of that on Hyper awhile back. But, never paid attention--
Only happens on Hyperdrive. Or at least, I can say I never saw it on stock. Hyper is the only ROM I've actually gotten so far as to run while SIM card is inserted. :good:
My contacts are almost all US based and are just ten digits, no leading 1. I did try editing the contact to my work cell phone by adding a 1 to it, and calling my S4 phone. It still was registered as +317-555-1212 format and return call didn't work.
So, it's not really about the way the contacts are stored, more about how the phone interprets incoming calls.
Try the 1+ and see what happens. Just do a few of your most used numbers to start--
Can you put a different dialer on phone and see
rugmankc said:
Try the 1+ and see what happens. Just do a few of your most used numbers to start--
Can you put a different dialer on phone and see
Click to expand...
Click to collapse
Just edited above, adding 1 to the way contacts are stored doesn't change the behavior. I can certainly try a different dialer and see what happens, but it seems to be based on how incoming calls are interpreted. I'm guessing there's a build.prop item or somesuch that needs a-tweaking.
Marc
so you changed the contact number to 1-555-555-5555 with hyphens
i ran hyper for quite a bit awhile back never any issues. of course could be something new--
i am not thinking rom or a lot more would have issue--
I did some tests.
On the phone in question, I edited the google contact for a test phone number. I then called the phone from that tested phone number.
It didn't matter whether the contact was saved in the formats:
317-555-1212
1-317-555-1212
+1-317-555-1212
+317-555-1212
In all cases, the incoming call was recognized as +317-555-1212, which isn't a valid call-back number, and return calls failed. Since this only happened when I put a custom ROM on, I'm sure it's something buried inside the ROM. However, I'm at a loss as to where to check various settings.
Gotta be something deep in there...
If all else fails you can Odin back to stock, reformat your internal card and reroot.
Under Phone Settings/Additional Settings/My Phone Number--is it in format 15555555555
Also, and I don't know where to check, your country code may not be set. I don't know if we even have that setting anymore or would it be in Build Prop.
Probably under ro.something
rugmankc said:
If all else fails you can Odin back to stock, reformat your internal card and reroot.
Under Phone Settings/Additional Settings/My Phone Number--is it in format 15555555555
Also, and I don't know where to check, your country code may not be set. I don't know if we even have that setting anymore or would it be in Build Prop.
Probably under ro.something
Click to expand...
Click to collapse
Interesting thought. I had gone into the dialer settings, and checked the Current Country... it listed United States of America. Then I stopped. But looking further it turns out that in the Assisted Dialing settings just below that, there might be stuff that matters. Currently my assisted dialing is OFF. The settings inside are:
Country code: 1
IDD prefix: 011
NDD prefix 1
City/area code: 131
National number length: 11
The area code probably doesn't matter, but I'm interested in the national number length. Ours tend to be 10. Could you please see what your settings are in there, and let me know if anything is different?
I can always backup (ug, safestrap backup), return to stock, poke around, re-root/restore. But if you could take a quick peek I'd be grateful.
Thank you!
Marc
I tried an alternative dialer... it acted just like the stock with the + thing.
I am on a rom that doesn't have those settings--sorry
Thanks anyway! I experimented changing the last setting to 10, and enabling assisted dialing, and it didn't change anything. Sigh.
Ok, you can still go back to stock with Odin. Or, try one of iB's roms they are very good too, I use them almost exclusively now--
Good Luck--:good:
Yeah. I've been back to stock a couple times with Odin. I've got the process down pat! I prefer the hyperdrive rom if I can work through the few small warts. It's just such an elegantly crafted piece of work. Worth the effort, if I eventually sort out the call issue. Appreciate your help.
Sent from my SCH-I337 using Tapatalk
Frankenscript said:
Yeah. I've been back to stock a couple times with Odin. I've got the process down pat! I prefer the hyperdrive rom if I can work through the few small warts. It's just such an elegantly crafted piece of work. Worth the effort, if I eventually sort out the call issue. Appreciate your help.
Sent from my SCH-I337 using Tapatalk
Click to expand...
Click to collapse
i got the same problem too. We'll get it figured out!
Damani311 said:
i got the same problem too. We'll get it figured out!
Click to expand...
Click to collapse
I figured out the clock on status bar thing. Like someone else said it was under the alignment options ... hidden by default. One by one warts going away.
Sent from my SCH-I337 using Tapatalk
Have the same issue here ..can't dial vm..on hyper
Sent from my SCH-I545 using XDA Premium 4 mobile app
jshua said:
Have the same issue here ..can't dial vm..on hyper
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you haven't done so yet i suggest noting the issue in the hyper thread ... either the Verizon or att one depending on your phone. Seems to be a bunch of us... more folks report it the common thread will emerge.
Sent from my SCH-I337 using Tapatalk
Same issue here i can not dial voicemail and can not call a number back without typing the number in manually. Deal breaker for me hope it gets fixed soon so i can go back to Hyperdrive. Or somebody comes up with some sort of fix.
Download Prefixer and remove the + for outgoing call
BBG037 said:
Download Prefixer and remove the + for outgoing call
Click to expand...
Click to collapse
When I get back from vacation I will have to try this. Thanks!