I can't even get it to show up in Market!
I have a 1280X752 160 PPI device that worked with your application on Honeycomb 3.1.
However, as of my upgrade to Honeycomb 3.2 yesterday, I can't find your application in the market.
I have tried all the usual tricks by setting my PPI to different values and "clear cache" on Market and restarting Market after "force closing" it.
I suspect the issue is tied to the fact that Google lets developers pick specific resolutions and PPI values as of Honeycomb 3.2.
Please see http://developer.android.com/guide/practices/screens_support.html#DeclaringTabletLayouts
Please strongly consider republishing your OBiON application so that it doesn't limit by screen resolution and PPI (items that are now important as of HC 3.2).
P.S. This obscure device having the problem is none other than the popular WIFI Motorola Xoom running Honeycomb 3.2 ;>
Obihai being the great company that they are provideshttp://www.obihai.com/firmware/OBiON.apk
However, this version is 1.2.1 (2294)
The current version is: 1.2.1 (2630)
Please update your server to provide an updated .APK file.
The application will start, register, and dial.
However, when using the latest late November released Obi firmware for my Obi devices, I find that as soon as it connects, the app crashes.Update:
Since I run Obi on both Android phone (still listed in Market) and both devices were rooted, I SCP into phone, and yanked down /app and got the following file "com.paad.hello-1.apk", and then transfer to my problem Xoom device. Once there, just used "app installer" or similar to install.
Of course, I also updated firmware in Obi100, and started getting the one way audio problem others have reported. I put the OBi into the router's DMZ and licked that one too.
Ultimately, you guys need to probably keep up the download link with what you are releasing to market.
I'm not 100% sure that it's a new firmware thing, rather might be something within the ObiTalk network.
I have 4 devices, and only one on the new firmware. I used the other devices, and got the same one-way audio issues with the older firmware. I have also been getting random voice calls with one way audio (via the ATA wired handset) since early December too. Something changed...somewhere.