Got something else to discuss that is not covered by the previous forums? Post it here!
#72416 by majek
Fri Jan 07, 2011 8:37 am
Where can I file bug reports for the android mobile app?

Model: Droid X
Background: App installed, icon is blue after waiting a few hours, I can successfully make outgoing calls.

Bugs:
1) When attempting to dial out with the keypad via the cellphone provider's network, the ooma app pops up a box about it crashing asking to force close or send a report, not sure why its getting in the way of making regular phone calls. I sent a report in after I verified its a consistent reproducible bug. This doesn't happen when using phone numbers stored in contacts.

2) When making an outgoing call via ooma, the ooma app locks up and won't let me disconnect the call, meanwhile I watch my ooma minutes disappearing on the call timer. Have to hit the home button and re-enter the app then hit menu exit to stop the call.

Feature Request:
1) Preference option that lets you choose to be taken directly to the ooma contact/phone screen when tapping the icon so you can get to making your call quicker instead of hitting the phone button on the ooma menu.

Yes, I realize I'm only saving one click, however the app is installed on my wife's phone and the only way I can expect her to migrate to ooma is if making calls via ooma is as easy as making calls via the provider. Right now with these bugs and without the quick phone call feature the app is a roadblock not a convenience. I've had to force quit the app to keep it out of the way of daily use, when the bugs are fixed I'll give it another shot.
#72535 by TheSilverRing
Sat Jan 08, 2011 1:55 pm
Samsung Vibrant running Froyo

I had to uninstall the ooma application in order to reliably make cellular calls, otherwise audio would frequently not be sent over the cellular network.

When I try to make a cellular call I too get a force close message regarding the Ooma service, this seems absolutely repeatable "The application Ooma (process com.ooma.android.oomamobile) has stopped unexpectedly. Please try again."

From the stack trace;
Exception class name "java.lang.ClassNotFoundException" in PathClassLoader.java
Unable to instantiate receiver com.ooma.android.oomamobile.OutCallreceiver: java.lang

Does my phone not have some class that is expected? Maybe something is missing form the APK that happens to exist on most phones but not mine?I cannot be bothered to roll back to 2.1 to test there - besides the WiFi calling is not in 2.1 and I want that.

I have skype installed, I also have TMobile WiFi calling enabled, although neither is active when I have problems I guess they could be related.
I have not had a problem calling before the ooma app was installed.

I would be happy to help to troubleshoot.
#72767 by Dennis P
Tue Jan 11, 2011 5:46 pm
We've identified the problem with the app interfering with native dialer app calls. We should have an updated version posted before the end of the week.

We have also seen the issue where the "end call" button becomes unresponsive and you can't end the call. It only appears to affect Droid phones, many of the other Android phones we test do not seem to have this problem. We are trying to identify the source of the problem.

Who is online

Users browsing this forum: Google [Bot] and 16 guests