Ooma Mobile HD App 5.2 (105129) iOS

Anything related to the Ooma Residential calling app
Post Reply
Clifftr
Posts:47
Joined:Fri May 09, 2008 4:31 am
Location:Nashville, TN
Ooma Mobile HD App 5.2 (105129) iOS

Post by Clifftr » Wed Mar 25, 2015 3:24 pm

I just started using the Ooma Mobile HD app on my iPod Touch 5th generation (ME979LL/A) running iOS 8.2 (12D508), and I'm noticing that whenever I power off my iPod, then power it back on, every time I have to launch the app in order for it to auto Login - I does retain my login information, but unless I manually launch the app it doesn't Login. Also each time I have to go to iOS Settings | General | Background App Refresh and re-enable OomaMobile. This is getting very annoying! I don't know what else to do so the app will auto login when the device is powered on?
I have tried the Google Hangouts app, and I don't experience this issue with it - in fact it is quite robust in this area, so I don't have to worry about missing a call because it didn't auto login.

Also it would be really wonderful if the app gave us the option to either use the iOS Sounds, or even better, to use our own custom sounds - something Google Hangouts doesn't offer. :D

Tom
Ooma Moderator
Posts:4378
Joined:Sat Sep 05, 2009 8:07 am

Re: Ooma Mobile HD App 5.2 (105129) iOS

Post by Tom » Wed Mar 25, 2015 5:11 pm

Thank you. We've entered a bug for this.

Clifftr
Posts:47
Joined:Fri May 09, 2008 4:31 am
Location:Nashville, TN

Re: Ooma Mobile HD App 5.2 (105129) iOS

Post by Clifftr » Thu Mar 26, 2015 7:12 pm

Tom, Thank you for your prompt reply. ;)
This also appears to be a bug in the Ooma Mobile HD app: during an incoming call, the volume of the ring is very low, and when the volume is turned up all the way while ringing, it does get somewhat louder, but then during the next ring or so, the volume drops back down - almost as if being muted.

Device: iPod Touch 5th generation (ME979LL/A)
OS: iOS 8.2 (12D508)

Tom
Ooma Moderator
Posts:4378
Joined:Sat Sep 05, 2009 8:07 am

Re: Ooma Mobile HD App 5.2 (105129) iOS

Post by Tom » Thu Mar 26, 2015 9:56 pm

Fix for that bug should be in the next release.

Post Reply