Post

2 followers Follow
0
Avatar

Flaky Call Log Handling Issues... (Sorry if it sounds harsh)

#1 Okay, so I use this in App form on a phone that has service through another provider.  However I get people who call my actual cell phone number and not the TextNow number.  Why would I have a Incoming Call in a blank chat dialog for someone who didn't call my TextNow Number?  The program should not be lurking/monitoring/documenting anything going on with my actual cell number...  I have to compare my actual missed call log with TextNow to figure out which are unique to TextNow to figure out which number they actually called.  Then delete the Incoming Call "Conversations" that aren't relevant to TextNow at all.  But that person called my Cell number and TextNow needed to document it?  I have a call log for my phone, it works great!  Thanks though...

#2 If one of my devices looses connectivity when a call comes in, that device doesn't ring (of course).  But I also do not get a missed call entry either.  This should be no different than Text or Voicemail.  This should be recorded into the conversation history on the server side when the call actually comes in.  That way if someone should call while the phone is out of service range they can see later that someone did infact try to call you even if no voicemail was left.  This should also be true of Outgoing calls.  It only shows that entry on the device that did the outgoing call.  If I clear the app and relogin, the outgoing and incoming call entries disappear.

Honestly, there should be a server side call history that is kept in a separate tab in the program (Caller ID, Time, Date and Call Duration).  There is no reason to open a new "Conversation" just to document an Incoming or Outgoing call.  This is really a "fake" Conversation as it does not show up on the Web when you login here or when you login from another device.  But one step at a time.  Just make it stop importing my missed call history from my actual phone.  I'd be okay with just that...

Raymond Boettcher

Please sign in to leave a comment.

4 comments

0
Avatar

Hey Raymond, 

Thanks for bringing this to our attention, we certainly do appreciate the feedback! 

With regards to the call log showing up on your TextNow account, we have been made aware of the issue and a fix is set to be deployed with the newest update, coming out next week. 

Due to the VoIP nature of our service, missed calls during a connection loss are going to be logged differently than traditional carriers. Clearing the app's cache and data serves the purpose of clearing those logs as well. I would like to assure you that our developers are constantly working on improving the app's service with regards to reliability and functionality. I can certainly pass along the rest of your feedback to them for future use :)

Please let us know if you have any more questions, and/or concerns. 

 

 

Valeria TextNow Support 0 votes
Comment actions Permalink
0
Avatar

Yes but my main point is that the Missed Call/Incoming Call or Outgoing Call should be recorded server side.  If you loose connection and a call comes in, you have no idea that the call came in, in the first place (Unless they leave Voicemail).  The fact that the program needs access to my cell phones call logs as a permission is bogus...  In-fact, the program runs on my tablet, which is void of any type of cellular hardware.  It knows WiFi, and the program is happy with that...  This program has no bearing on my cell phone number or anything related to it at all except access to my 4G Service.  Maybe this is different when it comes to TextNow Cell Phones on Sprint Service...  Maybe the program wants to know if my phone is currently doing something, ie: in call, dialing, answering or idle.  That way the program doesn't try to interrupt my actual cell call, I have no idea....

Raymond Boettcher 0 votes
Comment actions Permalink
0
Avatar

Hey again, 

I cannot divulge information with regards to the technical background that resulted in the app keeping track of your regular phone's call log, however, I can assure you that it was not intentional. We have tracked the issue promptly, and our developers have found the bug, and are simply waiting for the deploy of the next update to resolve that issue! 

And once again, with regards to the call history being saved on a server, that isn't a feature that we can technically support at the moment. It is certainly something that we can look into in more detail with future updates, but I do not have an ETA on that for you as it stands. 

Hopefully that helps in answering your concerns! 

Valeria TextNow Support 0 votes
Comment actions Permalink
0
Avatar

Okay, awesome.  For now I'm taking the App out of trusted status and Forbidding the App access to Write/Delete Call Log and Read Call Log.

Raymond Boettcher 0 votes
Comment actions Permalink