Provider "Inactive" after google play auto-update

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Motorola Droid with SIP account configured to local server
2.Account shows "Inactive" no matter what I do ( remove accounts, clear data, 
reinstall, anything )

What is the expected output? What do you see instead?
 "Inactive" account no matter what I do.  

What version of the product are you using? On what operating system?
Android 2.2.3

Please provide any additional information below.
Using the phone in airplane mode, wifi enabled. Network works, SIP server 
(asterisk) works. Except CSipSimple. Everything worked fine before the upgrade.

Original issue reported on code.google.com by eleon...@gmail.com on 19 Sep 2012 at 1:08

[GoogleCodeExporter]

Same issue here.  I'm on a Motorola XPRT running Android 2.2.2.

Original comment by tobias.p...@gmail.com on 19 Sep 2012 at 5:01

[GoogleCodeExporter]

Can you try to download and upgrade from :
http://nightlies.csipsimple.com/trunk/CSipSimple-r1914-trunk.apk

Apparently some device suffer of a problem with optimized builds. In version 
above I removed optimizations stuff. Let me know how it goes.

Original comment by r3gis...@gmail.com on 19 Sep 2012 at 11:29

[GoogleCodeExporter]

Works fine with the build you linked. 

Original comment by eleon...@gmail.com on 19 Sep 2012 at 11:49

[GoogleCodeExporter]

The nightly build workes on my Motorola XPRT running Android 2.2.2.  If there 
are other Versions you would like me to try, please let me know.

Original comment by tobias.p...@gmail.com on 19 Sep 2012 at 11:50

[GoogleCodeExporter]

Issue 1979 has been merged into this issue.

Original comment by r3gis...@gmail.com on 19 Sep 2012 at 1:09

[GoogleCodeExporter]

Issue 1979 has been merged into this issue.

Original comment by r3gis...@gmail.com on 19 Sep 2012 at 1:34

[GoogleCodeExporter]

Issue 1979 has been merged into this issue.

Original comment by r3gis...@gmail.com on 19 Sep 2012 at 1:43

[GoogleCodeExporter]

A release candidate is produced.
If you have time to test this version, I would be very interested by results 
you get :

http://nightlies.csipsimple.com/stable/0.04-04/CSipSimple-0.04-04-trunk.apk

Thanks !

Original comment by r3gis...@gmail.com on 19 Sep 2012 at 1:44

• Changed state: NextRelease

[GoogleCodeExporter]

Release candidate works.  Did you end up removing the "optimization stuff" or 
did you find a way around why some of the phones don't work with it?

Original comment by tobias.p...@gmail.com on 19 Sep 2012 at 5:17

[GoogleCodeExporter]

I removed it. Will try to get it landing without breaking other device later. 
But I think the devices affected by the problems are not eligible to these 
optimizations. Normally it should not break it and detect at runtime if 
eligible or not, but apparently it breaks before when loading native part of 
the application.
So I'll push this version to market. I hope it will be last hot fix for the 
0.04 and hope it will not be too boring for users to see a lot of updates 
quickly made. I got hard time on this one to stabilize for all devices :/

Original comment by r3gis...@gmail.com on 19 Sep 2012 at 9:03

[GoogleCodeExporter]

Better an extra update than a not working app! Thanks for all your work!

Jop

Original comment by j.pla...@mi-lv.nl on 20 Sep 2012 at 6:35

[GoogleCodeExporter]

To all that was previously affected by this issue,
I've re-introduced the optimization stuff. It uses now another build method but 
I'm not sure it will solve the problem you had. I have just good hope it will.

So could some of you try the latest nightly build :
http://nightlies.csipsimple.com/trunk/CSipSimple-latest-trunk.apk
And let me know if previous symptoms are there or not (and if any new problems 
appears on sip registration / call).

It will help me a lot to know if optimizations can be introduced safely without 
breaking app on some devices.
Thanks in advance :)

Original comment by r3gis...@gmail.com on 29 Sep 2012 at 5:10

[GoogleCodeExporter]

Same issue is present with this build. Cannot connect to sip provider.

Original comment by tobias.p...@gmail.com on 29 Sep 2012 at 8:39

[GoogleCodeExporter]

Thanks for the quick feedback.
If you have time to send me logs I'll be interested (menu > help > start 
recording logs & menu > help > stop and send logs). 

I'll revert to optimizations disabled for next builds.

Original comment by r3gis...@gmail.com on 29 Sep 2012 at 9:15

[GoogleCodeExporter]

Log file send 1 minute ago.

Original comment by tobias.p...@gmail.com on 29 Sep 2012 at 10:19

[GoogleCodeExporter]

A follow up about the problem.
I was able to test directly on a Motorola Milestone today.

I found the root cause of the problem and solved it. It will be in next release 
that will have optimization without breaking android 2.1/2.2 armeabi-v7a 
devices.

If you have time tomorrow to test next nightly build will be helpful to confirm 
the fix also works on Droid. But this time it's not just theoretic fix, so 
should work ;). (droid and milestone both have Omap 3 cpu running 2.1/2.2.

----
For the record : (will be useful for other devs -- probably not for users ;) )
The problem is one that will be encountered by any application trying to use 
optimized neon code on 2.1/2.2 armeabi-v7a device and the cpu-features library 
from android NDK.
The bug on android 2.1/2.2 :
http://code.google.com/p/android/issues/detail?id=5116

This method is used in cpu-features library provided by google.
A workaround is needed to have a valid implementation of pthread_once in 
cpu-feature library.
So it's fixed in r1943. The fix is inspired from bionic android source code of 
4.x version (that has valid implementation of pthread_once) and from a tip 
found in VLC bug tracker (as VLC is also impacted by the problem).

It is a rather disturbing problem because using what is provided by android 
SDK/NDK and running on stock ROM we get a failure.

Original comment by r3gis...@gmail.com on 1 Oct 2012 at 6:02