Saturday, May 01, 2010

eCID - Android App

Please go to our new site: http://www.enhancedsmscallerid.com/

43 comments:

Anonymous said...

Hello Edward -

I have a specific question about your Enhanced SMS application.

I am using Tasker to set up a custom profile so that when I am in my car, My incoming texts and phone calls will be read to me.

Your application does this perfectly, but the problem I am having is that there isn't a way to disable the app when I am NOT in the car. I have set tasker to enable eCID when plugged into the car charge, and disable it when unplugged, but eCID seems to override these settings and simply stay on all the time. I do not want my texts and incoming phone calls read to me unless I am in the car.

Is there a way to disable eCID so that it only works while I am in the car?

I could not find your email address or I would have emailed you directly, but if you could email me when you see this I would appreciate it. thanks.

rubber.bullets at gmail.com

Patrick said...

Just bought the app for my HTC EVO and have a couple of problems. First of all, the caller ID announce doesn't go through the headset. When I'm not using my headset, I hear the announcements over the phone's speaker. When I have my headset on, all I hear in the headset is a ringer - the caller info still gets spoken through the phone speakers. Next, what does the SMS reader do? is it suppose to read my text messages to me when I'm driving? all it does is "say SMS from 9016" over and over.

Thanks

Ed said...

Hi Patrick,

If the notifications are being played through your phone speaker even though you have a headset plugged in then usually that implies that your headset is not A2DP compatible. Alternatively, to use any headset, there is an app available called super mono bt that other users say works with the app to allow any headset to be used with this app.

The SMS reader is meant to read your incoming SMS messages and should not be looping. If only the sender of the sms is being read, make sure that the 'Read Sender Name' option is not selected as this only reads the name of the sender and not the whole message.

Thanks.

Patrick said...

Hi Ed -

thanks for responding - I thought it might be a headset issue as well - however, I have enabled caller ID over incoming call, and when I am on a call with my headset, the incoming caller's info is clearly announced in the headset. The headset also interfaces with my other apps including vocie dialing from my headset. The model is a Plantronics Voyager Pro. I also changed the sms setting from "name only" and it now reads my text messages fully. However, now when I get a voicemail notifcation, it reads me some coded message like Voicemail from 9016, please call 408-something-1000 to hear the voicemail, from android something or other forward slash forward slash etc. I can write it out exactly if you wish. Is there a way to configure just to say "you have a new voicemail?

thanks

Patrickalsaft

Ed said...

@Patrick, what I do to exclude those SMS messages that notify me about voicemail is to check the box under SMS message options that says to ignore unknown senders. I could add an option that just speaks a notification for new SMS messages without reading either the name or message itself. Is this what you are after?

Brady said...

Hello Ed.

I purchased ECID for my new Samsung Vibrant. I am having a little difficulty getting the caller id announcement to work in the headset, which is a Q1,can you give me alittle adive. Thanks

Ed said...

Hi Brady, The Q1 is not (I think) A2DP compatible. You might try the app Super Mono bt as they have a free 5 day trial and I have heard from others that it works with my app. Sorry.

Patrick said...

Hi Ed -

a simple notification that I have a new voicemail would be fine. Also, any ideas on why I get caller ID over incoming call but don;'t hear it on an an incoming call?

Patrick said...

by the way- I did install Super Mono BT and it made no difference. I don't think it is a headset issue as all the other headset functions work including voice dialing and caller ID over incoming calls

Patrick said...

one more update - I changed the setting in ecid to"headset only" and it still comes through the speaker on the phone and does not come through the headset

Ed said...

@Patrick:
Can you install aLogCat (Free app), set up a filter (EnhancedCallerID), and enable logging from within my app? Then when the app speaks through the phone rather than the headset during headset only can you email me the log file?

Thanks.

Patrick said...

Hi Ed -

I was at bestbuy and they had an ad2p headset called the jawbone that I could buy and try for 30 days so I did. You were right about the a2dp compliance of my plantronincs - it did not have it and I apologize for questioning you on that. With the jawbone, I do hear the caller ID in the headset, but the weird thing is that the caller ID over incoming call waiting doesn't work. I unchecked the "headset only" mode and now it works - caller ID over incoming plays in the headset. any thoughts?

Ed said...

Hi Patrick, could you confirm the issue? So the call waiting only works with your headset if the headset only option is not checked? Checking the option causes it to not work, while unchecking the option causes it to work?
Thanks.

Patrick said...

Hi Ed -

well, things just keep getting weirder for me. I turned off the phone and turned it back on, and now the talking caller ID works like it should - comes through both the headset and the phone or just the headset if selected as such...but now, it will not read the name of the caller like it did yesterday. Today, it will only announce the number even for people in my contacts. The "what to say" section for incoming calls says Call from,- but it doesn't speak the name through the headset, only through the phone's speaker

Patrick said...

one more thing - when I am on a call, the caller ID over call waiting comes on and it does announce the caller's name, not just the number. One thing I noticed is that the voice that announces the caller name over the speaker and the voice that announces the caller name over incoming call are the same voice - but the voice I hear in the headset that jut announces the number when a call comes in is not the same voice - it almost seems like some other app is taking over on incoming calls

Patrick said...

I just found out something more - the jawbone hero software is overriding your app on incoming calls, so I will either need to try another headset (3rd try)or just use their app since there doesn't seem to be a way to turn it off...I like yours better but....thanks for all your efforts..hopefully others can glean something form all the fun I've had :-)

I'll keep you posted...

Ed said...

Patrick, I think you can turn they (Jawbone) software off by connecting it to your computer and going to http://mytalk.jawbone.com/jb2/mytalk/beta. Can you verify if that is the case?

Patrick said...

Hi ed -

Yes i contacted them and they told me that, so I did that - but after I did it, all you hear in the headset is a warbling tone for incoming call. It still seems to override your app.

Patrick said...

I spent some time with jawbone - their app conflicts with yours somehow and they do not know why. When their headset is on and connected, your app will not work- period. So I struck out there as well. I guess for the time being I will just need to go back to my old standby plantronics - the only thing it didn't do was announce the caller ID in the headset - everythingn else worked

Ed said...

Patrick, does this[1] help at all?

[1]http://a.imageshack.us/img651/9884/jawbonesettings.jpg

Patrick said...

Hi Ed -

I was in the mytalk app and turned off the caller ID function - didn't help. I also tried an Ant T1 headset today and it didn't work with your app either. I am going to try a samsung WEP3500 headset later on and will let you know. I don't know if the problems I'm having are because of the HTC EVO phone or what. One thing I would like to ask you about your app - what is the difference between the way the caller ID announcement an incoming call is handled and the way the caller ID over call waiting is handled? the reason I'm asking is that the caller ID over call waiting does route through the plantronics headset, but the caller ID on an incoming call does not. Why?

Ed said...

Hi Patrick, the methods for both situations are different. I am a bit confused on what your problem is now. I thought that caller id over call waiting was the problem. Is that not the case anymore?

Patrick said...

Hi Ed -

no, the problem with the plantronics has always been the incoming caller ID. I apologize if I am confusing you. As I tried to state in my original post, when I am using my plantronics voyager and my phone rings, all I hear in the headset is a tone. However, if I answer that call, and while I am still on that call another call comes in, I hear the caller of the second call loud and clear in my headset. Can you make your app handle them the both the same way?

Ed said...

Patrick, so with your non a2dp headset, you heard caller id over call waiting?

Patrick said...

yes - that is correct

Ed said...

Hi Patrick,
The phone will not allow the app to speak when there is an incoming call, only once you are in a conversation when you are using a non-A2DP headset. I just tried my old headset and tried talking like the app does for cid over call waiting.

rps60050 said...

Hi Ed -

OK - I understand about the bluetooth and the non-AD2P headset. However, I was wondering if you would be willing to work with me to find out why the caller ID no longer comes out of the phone's speaker when an AD2P headset is attached? If the caller ID at least came through the phone's speaker. I could live with that. It just seems odd to me that the app will speak the caller ID through the phone's speaker when a non-AD2P headset is connected, but will not when an AD2P headset is connected. Would the log program you suggested be able to show you why this happens?

rps60050 said...

sorry - was signed in under the wrong account - that previous post from rps60050 was from me - Patrick

rps60050 said...

Hi Ed -

I just re-read your post and now I'm confused - you said "The phone will not allow the app to speak when there is an incoming call, only once you are in a conversation when you are using a non-A2DP headset. I just tried my old headset and tried talking like the app does for cid over call waiting"

When I have your app enabled on my phone and am using a non-ad2p headset, the app does speak the number of the incoming call through the phone's speaker. Its when I connect an AD2P headset to the phone that the caller ID is no longer spoken through the phone's speaker.

Ed said...

Hi Patrick, the phone purposely does not use the phone speaker if a headset is plugged in. I assume that the user is using a headset and would like notifications through the headset. Since bluetooth headsets that dont have the a2dp profile are not supported, the app doesnt know about them and speaks as if nothing is plugged in.

If you would like the option of having it speak over both the speaker and the headset, then i can try to add that for you.

Please let me know.

Patrick said...

that would be awesome Ed - having the app speak through both the phone's speaker and my non ad2p headset would be exactly what I want. Please let me know what I can do to help (ie, logging, troubleshooting, whatever)

Patrick said...

Hi Ed -

any progress on what we talked about in my last post?

Ed said...

Hi Patrick, Could you use the new site from now on? I did look into trying to support non a2dp headsets and it does not seem possible. I tried everything and it is unclear how things work during a call.

joma said...

Hello Ed,
I have a problem with caller id announcement via bt headset Samsung HM3500(A2DP) on Samsung galaxy s 2.1. Checked Text-to-Speech is working via bt, and listening to Music and talking via bt has else no problem. What i noticed is that the call sound is not my preset one.

Any idea? thx

Anonymous said...

Hello Ed,

I can not get my app to work at all. I have selected the settings I want in the app, and it the icon pops up on my notification bar, but my normal notification sounds and my message is not read. Any idea what might be wrong?

Thanks,
Laura.

Ed said...

Hi Laura,

Can you contact me directly? Also, eCIDs homepage might be useful to you:
www.enhancedsmscallerid.com

Android app development said...

This is one of the new information compare to all post.I am so happy to read about your post.Next time again I will look forward towards the post.
Android app developers

cristianu said...

Hi. My name is Cristian. I have lenovo p780. I tested a lot o free applications that read caller's name. Some of their read only sms's sender and some read only caller name. None of one read booth. I need this kind of software and I don't know if ecid do that. If I pay for it and don't work?

Ed said...

@Cristian, Unfortunately Android doesn't natively support dual sim phones. This is where the problem is. Apps, like mine, use functionality exposed via the Android framework. Dual sim is not exposed. Maybe in the future it will be supported natively and apps will work. Until that time, if you really need an app that reads everything out, then buy a single sim phone (preferably a nexus device).

cristianu said...

I use one SIM for data and one for call. But how I said some of applications read only sms another only caller name. I think they can be combined to read both.

Ed said...

Like I said, Dual sim phones are not supported in android (even if companies make them), so the resulting behaviour is erratic and unexpected. Sometimes it works, sometimes it doesn't. The apps are not broken, the phone is.

Fero said...

Hi, Ed!
I've purchased the ECID, and I have problems with BT headset:
-ECID reads caller's name correctly ON PHONE, but not on BT headset.
I have LG Nexus 5 stock 4.4.3 ROM, with both Nuance and SVOX (Hungarian)TTS.
I have three BT headsets:
1. Plantronics M25
2. Nokia BH-215
3. Jabra Arrow
I tried all headsets, and the A2DP test of ECID checked that Plantronics and Nokia were compatible. Jabra wasn't A2DP compatible, so I put it off.
I tried all settings of ECID, still without results.
I have noticed, that if I interrupt the call while ECID reads caller's name on phone, the last word of the name could hear in the BT headset. That's why I think, it would work, but I don't know, what way.
Could you help me?
Thanks,
Fero
Hungary

Ed said...

I would suggest that you look at our site, http://www.enhancedsmscallerid.com for quick support. Having said that, try looking at the following FAQ posting. It should help you: http://www.enhancedsmscallerid.com/home/faq/caller-id-through-bluetooth-on-ics