Related
Hi All,
I don't know if this as been posted before, i couldn't find it if it was.
I'm looking for an app which will take voice mail and record it right on the phone when i miss a call. I've seen it for S60 phones but never for WinMo. I've been looking for almost a year off and on but have never found anything near what i want. If anyone has seen it send me the name please, it would be a great time saver.
Chris
Grandcentral?
I don't know if you'd be interested in all that it entails but check out http://www.grandcentral.com as a possible solution. It's not exactly what you're after but may work out for you....
Hey, thanks for the link. I think i may have found what i'm looking for! I have not tested or installed this yet, i'm at work. I'll be installing it over dinner and putting it to the test. Heres the link:
http://www.isecretary.net/download.php
Chris
I've been using Callwave: http://www.callwave.com/landing/mobileVisualVoicemail.aspx?r=NONE
Again, it's not exactly what you said, but you can set it to send you and email with attachment which you can save to your phone.
I was using SimulScribe/SimulSays, but their customer service is atrocious. So bad that at one point the CEO emailed me to apologize for how I was treated after reading the email exchanges only to ignore my response email asking if my lost voicemails could be recovered. I guess the answer was no.
The other nice thing about Callwave is that it will transcribe your voicemail (good for reading messages while you're in meetings). I don't know if that's free longterm however.
i'll be interested to hear how the isecretary worked out...
HI,
I haven't had a chance to really test it out yet, I've been super busy. I did test it when i first downloaded it and i think it may have deleted all of my contact #'s. Not sure it was the program or something i did as messing with my phone seems to be my new habit. At present i can record a message from an incoming call but i'm having trouble getting the greeting to play. Adjusting the settings may be all thats needed but i don't have the time to do it yet. If i get it under control i'll post what i did to get it to work.
Chris
I've been reading about this bug for awhile now and it finally hit me. What happens is if contact A sends you a txt message and you respond. The message thread will show that your response went to contact A, but the reality is that A may not have received the response, however C,D,E,F, Z,Y and X did! It seems to be totally random, will happen regardless of the SMS app or ROM you use and can be quite dangerous. This bug renders my N1 virtually useless. Anyone else experience this or has an update on the fix for this dangerous bug?
I recommend anyone with an Android phone to be use extreme caution when sending txts or mms messages as you never know who may actually get it
Have read about it, but it's never happened to me.
Can you reproduce the bug reliably?
Can you dump the logs (/proc/kmsg and logcat, or bugreport) immediately after it happens?
Any pattern connecting recipient A and the rest?
Nightmare!
Sent from my Nexus One using XDA App
How come that not even one person from those reporting having "this bug", wants to help find out, what it is? Very interesting.
I have found that using handcent resolves this problem for me.
Sent from my Nexus One using XDA App
My wife have experienced the problem twice with Galaxy S, I haven't have similar troubles with my N1, although every now and then it takes time for some messages to go through. That is probably due the carrier, not the device.
Sent from my Nexus One using XDA App
The only trouble with messaging i have is that sometimes when i select to open the thread at the top of the list, the one at the very bottom of the screen opens. Frustrating!!!
cymru said:
The only trouble with messaging i have is that sometimes when i select to open the thread at the top of the list, the one at the very bottom of the screen opens. Frustrating!!!
Click to expand...
Click to collapse
I have this too in a pre 6.1 nightly...
But it's not the first time i hear the bug that SMS are sent to everyone, so it definitely exist
Sent from my Nexus One using XDA App
I saw the "reports" on the net popping up once in a huge while, but I never saw anyone that would report this bug and actually try to solve it, or assist anyone in solving it. Doesn't look like a normal bug report to me, and doesn't look like there is a bug. I know over 15 people with all kinds of Android, at least 6 with Nexus, and it never happened to anyone. The "bug" looks very fishy.
Jack_R1 said:
I saw the "reports" on the net popping up once in a huge while, but I never saw anyone that would report this bug and actually try to solve it, or assist anyone in solving it. Doesn't look like a normal bug report to me, and doesn't look like there is a bug. I know over 15 people with all kinds of Android, at least 6 with Nexus, and it never happened to anyone. The "bug" looks very fishy.
Click to expand...
Click to collapse
I can assure it is a bug and a major one. It is well documented if you google it. It appears to be across many different hardware platforms and therefore is most likely a source code issue written incorrectly in the android OS. And just because the 15 people you know aren't having the issue does not mean the rest of the world isn't. This is my 3rd android phone and this is the only one that does it and from I've been reading there are many others who are also having this random issue...I assure you, this isn't something that someone can do by mistake or accident...
In that case, if it's so well documented, how come that nobody has ever assisted anyone else in debugging it, yourself included?
It's happened to me.
I receive certain friend's facebook updates as sms. One time I got the facebook sms. I closed it then replied to another friend's sms. Guess what happened.... what I sent to my friend got sent as a comment to my friend's facebook status.
Looking back at the sms log, I definately wrote my reply to my friend, not the facebook sms, but somehow it was replied to the facebook sms.
This bug has been around since Android existed.
There's really no way to debug this I don't think, unless you only have a few contacts that will text u if you write something weird... cuz having a phone full if phone numbers, your text can be sent to any number, even non mobile phones, you wont know since you thought u texted the right person.
Sent from my Nexus One
There's a ton of ways to debug everything, including even specifically modified SMS app for dumping debug data - it's an open OS, yes? If I got some beta application versions for debugging from app devs to test things, I'm sure Google wouldn't do less to debug it.
For starters, the next SMS I'll check the records in kernel log and see if there's any useful data to start from there.
Jack_R1 said:
In that case, if it's so well documented, how come that nobody has ever assisted anyone else in debugging it, yourself included?
Click to expand...
Click to collapse
Well I think you bring up two entirely non-related issues... First, if you google it, you will find a vast amount of people all having that same issue, which in my mind establishes the "well documented" part of my statement. Secondly, as far as me or anyone else participating in debugging, I would love to, but it's a little out of my sphere of knowledge. If you could give me a little insight into what needs to be done, I would be more than happy to do what I can to help solve the problem. This $500 phone is totally useless to me if I can't be certain who will be receiving my txt messages. Mainly, I've been waiting and watching in the hopes that google would get involved and resolve this issue without my having to get involved. It would appear that this goes back a considerable amount of time.
Can you list out a step by step process to go about this so that all who are having this issue can also participate? What should be my next step
To even try to start with debug, you have to have a rooted phone.
The useful place to look at would be /proc/kmsg. The question is - how much data it contains after sending sms. I didn't try to dump it after SMSing yet, didn't have time for it. I'll try to find time over the weekend.
If it won't contain enough data, modification in SMS application is needed, to dump the data there to help with debug. This is much harder for me, because I'm not an app dev, and I'll have a hard time trying to find and understand the relevant data structures to dump there. Basically, when you hit "reply", some kind of indicator of current SMS thread needs to be dumped, and everything else that might result in wrong number being selected - all the chain that determines the number that the SMS goes to. Then, once the SMS was sent to wrong recipient, the info needs to be dumped and checked.
The later part is "slightly" beyond my skills. It requires knowledge of SMS application and its data structures.
It obviously happens only to those that have their Facebook contacts integrated, so the mechanisms that take care of joined contacts might be something to look at.
It never happened to me, and I've sent 12000 sms from my Nexus. Try using Handcent until this is officially fixed. Handcent is free and many people say it's not affected by the bug.
Jack_R1 said:
To even try to start with debug, you have to have a rooted phone.
The useful place to look at would be /proc/kmsg. The question is - how much data it contains after sending sms. I didn't try to dump it after SMSing yet, didn't have time for it. I'll try to find time over the weekend.
If it won't contain enough data, modification in SMS application is needed, to dump the data there to help with debug. This is much harder for me, because I'm not an app dev, and I'll have a hard time trying to find and understand the relevant data structures to dump there. Basically, when you hit "reply", some kind of indicator of current SMS thread needs to be dumped, and everything else that might result in wrong number being selected - all the chain that determines the number that the SMS goes to. Then, once the SMS was sent to wrong recipient, the info needs to be dumped and checked.
The later part is "slightly" beyond my skills. It requires knowledge of SMS application and its data structures.
It obviously happens only to those that have their Facebook contacts integrated, so the mechanisms that take care of joined contacts might be something to look at.
Click to expand...
Click to collapse
This is why I haven't, as you say, participate in resolving the issue...the level of of debugging required to get to the source of the problem is deeper than a non-developer like myself can go. And for the record, this is NOT related to the facebook app in anyway as I do not even have that app installed. This is 100% an Android code issue...
Are all your contacts Gmail-synced contacts?
Does it happen frequently enough to try to debug?
This is what happens with my N1:
I get a new text message, alerted in my notification bar
Rather than open it from the notification bar, I open the messaging app and tap the first message (just a habit, I guess)
The ninth message opens instead of the first one​
I'm not sure if this happens every single time, but it does happen frequently.
I'm wondering if it might be a bug in CyanogenMod instead, I've only started noticing it recently.
PS: I do not have a Facebook account nor any accounts synced with it. The only contacts I sync are my Google contacts.
Happily running CM7 with one issue:
If I dial my own number (or longpress "1" in the dialer) to access my real voicemail box, I have many "new" messages.
But I have been receiving, listening to, and deleting these same messages using the Sprint Visual Voicemail program installed as per the usual method (see http://forum.xda-developers.com/showpost.php?p=12219741&postcount=2 under "visual voicemail" for the one-sentence version).
Why are the two voicemail "boxes" not in sync?
I'm pretty convinced this is a bug-not-a-feature because it gives two different versions of the "truth" to anyone who uses both methods to check VM (because, say, your bluetooth headset doesn't allow you to hear locally-stored VVM audio files.. but that's another topic..). I'm not even sure what happens when this goes on for a month or two- do callers hear some kind of "mailbox full" announcement? Do the oldest messages just go away once they reach a certain age?
I have returned to a sense-based ROM and tried to "update my profile" and PRL, I have sent a VVM to [email protected], and I have gotten the little "toast" that says I have been provisioned successfully. But no sync. I have rebooted. I have waited overnight. I have turned off wi-fi to force 3G communication with Sprint. I have scoured the internet for these and other recommendations. Still no sync. The only thing I haven't done is called Sprint and asked them to get involved (which of course is a bit of a last resort considering we are talking about a rooted phone here).
So I'm asking for help from a) anyone who has experienced this and solved it and/or b) anyone who can shed some light on how Sprint VVM synchronization works.
Thanks in advance...
PS- I already know I can always "solve" my Sprint VVM issues by switching to Google Voice: I'm sure GV is great, but my question is not about GV. I'm just looking for basic information on the signalling method Sprint uses to synchronize your VVM with the cloud. Thanks!
I've been wondering and experiencing the same exact stuff that you mentioned, any input is appreciated here too!
NxNW said:
Happily running CM7 with one issue:
If I dial my own number (or longpress "1" in the dialer) to access my real voicemail box, I have many "new" messages.
Click to expand...
Click to collapse
After reading your post I pressed 1 to go into my voicemail and it said I had 12 messages. Never noticed this issue before (I never actually call for my messages, I just use the app), very strange. Unfortunately I don't know the answer.
Thanks ausch- I should have cited your FAQ as another excellent one-sentence summary of the basic method for getting Sprint VVM to run on CM7. And then of course there's this thread http://forum.xda-developers.com/showthread.php?t=982966 which spells it out a little more explicitly and, after getting a bunch of blog mentions at some point, had quite a bit of traffic for awhile. I originally reported this issue there but got no response after a few days so I just started up a new thread to get some more visibility.
I think you need another apk installed for that part to work.
This one. I think it is what updates your visual voicemail and deletes messages, not positive though.
aimbdd said:
I think you need another apk installed for that part to work.
This one. I think it is what updates your visual voicemail and deletes messages, not positive though.
Click to expand...
Click to collapse
I just installed that through ES File Explorer, we'll see if it works.
NxNW said:
I should have cited your FAQ as another excellent one-sentence summary of the basic method for getting Sprint VVM to run on CM7.
Click to expand...
Click to collapse
Lol, yeah when I was typing all that **** up I got lazy and just wrote it up real quick. Probably should have gone a little more in depth.
I installed it too (thank you for the suggestion aimbdd) but it force closes a lot and generally does not seem to fix my issue.
I'm getting plenty of notifications (my VVM "widget" shows the right number of unheard messages and the stock android VM notification up in the status bar shows the right number as well), the version is 5.1.0.34, and everything seems to function pretty well with this one exception.
I see references to Sprint_App_Updater.apk in lots of places (here's an example: http://forum.xda-developers.com/showpost.php?p=7246771&postcount=35 ) but it's not clear to me if the app is actually essential to the VM sync issue I'm talking about.
And one last thing, just a random quote (from http://www.evo4gforum.net/htc-evo-4g-how-to/visual-voicemail-9708/ ) from a person who had the exact *opposite* issue: he prefers using phone-call-based voicemail and wanted his visual voicemails to go away: "I did talk with Sprint and ... I asked them why are the messages that I delete on Sprint VM (#1) still going to VVM and not being deleted. No real answer except for that's the way the VVM app works. He assured me that if I delete a VVM that it will also delete it on Sprint's (#1), but for whatever reason it doesn't work the opposite way. "
This last sentence tells me there is supposed to be at least one-way sync.
I accept that the VVM app holds previously-downloaded audio files and it may not be desired (or even feasible) for Sprint to reach into your phone and delete a static audio file just just because you called into your voicemail and manually erased the original voicemail that spawned it. So maybe we will never have two-way sync.
But that quote above clearly promises that when things are functioning normally the mailboxes *do* sync in the direction I care about: if you delete a message from your phone, a signal goes back to the cloud so that the original is deleted there also.
aimbdd said:
I think you need another apk installed for that part to work.
This one. I think it is what updates your visual voicemail and deletes messages, not positive though.
Click to expand...
Click to collapse
I just got a voicemail and it was still in Sprint's system after deleting it from the app so I don't think this fixes the problem. Thanks for the suggestion though.
Today's PRL update did not change the behavior.
I might start casting about for answers outside the EVO 4G forum. Seems like it would be a generic Sprint issue that would apply to more than just EVO users..
Well just to close this out, I did find a solution after posting in various other threads until someone came up with the simple suggestion of uninstalling and reinstalling.
So the issue that prompted my question is resolved and my voicemail boxes *do* sync.
But I still never did find out *how* they sync.
Seems strange the underlying sync mechanism isn't more widely understood. Guess I'll let it drop for now. Thanks to everyone who chimed in.
NxNW said:
Well just to close this out, I did find a solution after posting in various other threads until someone came up with the simple suggestion of uninstalling and reinstalling.
So the issue that prompted my question is resolved and my voicemail boxes *do* sync.
But I still never did find out *how* they sync.
Seems strange the underlying sync mechanism isn't more widely understood. Guess I'll let it drop for now. Thanks to everyone who chimed in.
Click to expand...
Click to collapse
question, how did you uninstall and reinstall this...was it from titanium backup or something similar?
Nevermind, I found the fix/culprit (go sms) and now I'm all good.
So, I've been trying to get SMS working through google voice on my NC, with the latest nightly of CM7 running.
I got the latest "working" google voice I could find linked here on the forums. Got it setup and was able to get the voicemails on my account...
My issue though, is that I can't for the life of me get texting to work. Most of the threads I find on here about it are mostly people saying "It just worked for me." ...unfortunately, that doesn't really help if it didn't "just work".
Anyone have any tips on how to get it working, if it doesn't out of the box?
try DESKSMS
Yoinx said:
So, I've been trying to get SMS working through google voice on my NC, with the latest nightly of CM7 running.
I got the latest "working" google voice I could find linked here on the forums. Got it setup and was able to get the voicemails on my account...
My issue though, is that I can't for the life of me get texting to work. Most of the threads I find on here about it are mostly people saying "It just worked for me." ...unfortunately, that doesn't really help if it didn't "just work".
Anyone have any tips on how to get it working, if it doesn't out of the box?
Click to expand...
Click to collapse
I Use DeskSMS for all my texting, its by far the best. It can link up through several accounts, and i use Trillian as my client, but you can use any client.(which i got free from Amazon free app day a while ago)....its still apparently in Beta, and i think its almost finished. Ive had it from the very beginning. Its FREE right now on the market, until they release the final version. Hope this helps...at least with the texting its flawless!
Bobby
Thanks for the info.
DeskSMS looks like it links up to itself running on your phone. I'm not really looking for something like that (phone's old school and not a droid) since it's not really a viable option.
I see people talking about how they are using Gvoice to send texts. Which is what I'm trying to get working, but it just absolutely refuses to. Like I was saying, I can access voicemails through the gvoice app. When I try to send a message in the messaging app, all I get is a "Service is unavailable" message.
I use the latest version in the market and have never had a problem with it.
This right here is your problem:
Yoinx said:
When I try to send a message in the messaging app, all I get is a "Service is unavailable" message.
Click to expand...
Click to collapse
You need to use the Google Voice app to send the SMS messages, not the native Android App.
Thanks dormido.
I actually just saw something about that while I was browsing around between the last post and yours.
The posting I had found said something about hitting "t" to bring up the texting window. I haven't gotten the keyboard up in the GV app yet, but I guess I'll have to look at it a little more since I have confirmation that's how it's done now.
Thanks
Actually....
I figured this out now.
Apparently, since I've had the same google voice number since it was closed beta (and haven't really used it since). It didn't have all the features enabled anymore. The site was missing the voicemail and text widgets as well. Changed to a new Gvoice number in settings, and it all works fine now.
I feel like an idiot for it being such a basic fix.
I send out the same text to a group of people quite often and I get a message saying messenger is sending a large amount of messages do you want to allow this? I have to click on it for each message that goes out. Is there any possible way to change the limit? I know you used to be able to set it to anything you want in settings/security but it's not there anymore. Any help would be greatly appreciated...this is so annoying.
Have you tried GoSMS Pro?
Maybe I've never sent to as many as you, but I've never encountered that warning or behavior. I've used GoSMS for several years.
I've only seen this when I send many messages in quick succession (either with Google Messenger or something like Tasker). There should be a checkbox that says to always allow.
I'm also looking for a solution. I was using ResurrectionRemix (a CM based ROM) and it has an option to set the text restriction. So, it CAN be done. We just need to know WHERE the code is so that it can be changed. I can't find any search results explaining how to accomplish this. That SMS Limit Unlock app doesn't work on later ROMS.
After hours of searching today - it appears that the setting has been moved into the framework?
com.android.internal.telephony
https://android.googlesource.com/pla...geMonitor.java
I hope I'm wrong as I'm no Android dev.... But, if I'm correct the only way I know of to "fix" it is to make the change in a custom Android build/ROM.
This SUCKS as I use mass texting for business purposes (communicating with many individuals who sign up for contract work). I really like Android N (along with AndroidPay) - but, looks like I'll be going back to M (on a custom ROM)...
If anyone locates/determines a way to alter that file using RootExplorer/Sqlite or some other way - please let me know.