Sipdroid that I what started with but after researching on it and from developers reviews I found that application has some missing functionality like multiple call and transferring calls etc...
I don't know but may who is expert in sip stack or have time to do can implement missing functionality but I am neither one of them so my desire to get an application that have all this functionality and by modifying it I can integrate into my application and csipsimple is the answer.
However its not easy job to build csipsimple into windows environment but there is hack how to do it. so carefully read itswiki about building project into window environment.
If you have read wiki then in "without building the native library" section last line is like
"To get the .so files, download latest nightly build from nightly build website and unpack the apk file (apk files are just zip files). Then get lib/ARCH/.so files and copy it into CSipSimple libs/ARCH/.so"
I have to clarify one important thing about that: First get .apk file of csipsimple. The version of.apk file must same to download version of yourcsipsimple source code..
Here, you can see the source code version. Download the same version .apk and do further as described in wiki.
Check pic.
To remove native library issue you have to put ".so file" into the
libs folder.
i) If you do not have this folder then right click on "csipsimple" project and add folder named "libs". Folder name should be "libs".
ii) Now next you need ".so" files so for that get .apk from
here.
Be careful your downloaded .apk file version must be same as your downloaded source code version.
iii) Now next,
right click on .apk (as we do for .zip package) and extract it.
iv) In extracted folder you will get "lib" folder. That's it.
v) Copy all folder inside the "lib" folder and paste simply into the "libs"(Eclipse folder that we create in first step) folder.
Rename it to zip... If you were under linux this kind of problem doesn't appear and you would also understand that windows is just crap with extension management and that extension is just something in the name. The associated application to open a file could be anything. But this kind of thing is hidden to windows users and many users remains in ignorance...
i just tried below steps for building project on windows and it build and run successfully.. so u can try it..
1) import Actionbarsherlock from svn link
2) then import CSipSimple from svn link and give Actionbarsherlock as a library in CSipSimple application
3) then from this link ,
nightlies.csipsimple.com/dev_helpers/org.tar.gz ,download it and unrar it..and copy pjsua folder from it and paste it in your src/org/pjsip folder of csipsimple project.
4) then from this link,
http://nightlies.csipsimple.com/trunk/ , download latest trunk and rename it to .zip and unpack it.then from its lib folder ,copy two folder armeabi and armeabi-v7a and paste it into libs folder of your csipsimple project.
5) i think after all these steps, all errors should be removed..
What steps will reproduce the problem?
1. Checkout latest CSipSimple r2093
2. Make CSipSimple JNI dependencies
3. Install Eclipse / Android SDK / Android NDK
4. Load ABS and SipHome in to Eclipse per the how-to-build Wiki
What is the expected output? What do you see instead?
SipHome should build without error. Instead Eclipse reports two null pointer exceptions. In addition the error output is flooded with reports of ISipConfiguration and ISipService not being resolved.
What version of the product are you using? On what operating system?
Android ADT bundle v21.0.1-543035
Android SDK r21.0.1
Android NDK r8d
Please provide any additional information below.
The problem is related to a files in the CSipSimple <SRC> folder which do not have extensions:
<CSipSimple>/src/com/csipsimple/api/NOTICE
<CSipSimple>/src/org/webrtc/videoengine/README
See this Android bug report:
http://code.google.com/p/android/issues/detail?id=43057
My android log file in <eclipse>/.metadata/.log shows the following:
!ENTRY org.eclipse.core.resources 4 2 2013-01-22 11:40:35.034
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
!STACK 0
java.lang.NullPointerException
at com.android.ide.eclipse.adt.internal.build.SourceProcessor.scanFolderForSourceFiles(SourceProcessor.java:374)
at com.android.ide.eclipse.adt.internal.build.SourceProcessor.scanFolderForSourceFiles(SourceProcessor.java:380)
at com.android.ide.eclipse.adt.internal.build.SourceProcessor.scanFolderForSourceFiles(SourceProcessor.java:380)
at com.android.ide.eclipse.adt.internal.build.SourceProcessor.scanFolderForSourceFiles(SourceProcessor.java:380)
at com.android.ide.eclipse.adt.internal.build.SourceProcessor.buildSourceFileList(SourceProcessor.java:353)
at com.android.ide.eclipse.adt.internal.build.SourceProcessor.prepareFullBuild(SourceProcessor.java:194)
at com.android.ide.eclipse.adt.internal.build.builders.PreCompilerBuilder.build(PreCompilerBuilder.java:304)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
The problem is resolved by adding a ".txt" extension to the files noted above.
Thanks for the early report and for sharing the possible workaround.
The root cause seems to be a bug in this new ADT version (fixed in dev channel of ADT plugin) but renaming the files with problem is affordable, so your workaround is a very good idea.
You can see the first line about drawable-xxhdpi folder that is considered as invalid by the version of AAPT used. So aapt doesn't generates auto generated resources such as aidl autogenerated interface. That's why there is all next errors about ISipConfiguration and ISipService (that are autogenerated files). Fixing the first problem will fix all others.
Aapt probably doesn't recognize drawable-xxhdpi folder because the sdk version tools are outdated. So you have two simple solutions : 1- Update the sdk in eclipse. It's pretty simple there is the little droid icon in eclipse bar that you can click and ask for update. You'll also need to update ADT probably that you can do by searching updates (in eclipse window > search for update menu). Or 2 - (worse solution but faster), remove the drawable-xxhdpi (however I'm not sure that there is not other things that depends on latest sdk version too).
or
So, here in errors I can see from the screenshot apparently, it's not able to "import com.csipsimple.R;". This package is autogenerated by the android apk toolchain when it generates the resources identifiers. It generates a class xxx.yyyyyy.R where xxx.yyyy.R is the package name of your application. I can see from the screenshot that there is apparently some modified files regarding the current source code version. Did you modify the AndroidManifest.xml file to change the com.csipsimple package name into your package name? If not, there is maybe something else that prevents generation of resources files. Maybe you can try to clean the project (go in Projects > clean all). The important error when android builds is the first you get (eclipse problems list unfortunately sometimes re-order it). Often when something goes wrong at very first it results in many other errors that has only one root cause.
////
In Android I am Getting BuildConfig.java file but it can not generate R.java File.
Please Help me this regards. I tried with Android Tool -> fix project properties. but still failed to run.
I also tried Clean and build but again failed to generate R.Java.
It is not "instead of" -- you should have both BuildConfig.java and R.java. You may have errors in your Eclipse console, or red X marks over a resource (res/) or your AndroidManifest.xml, that are preventing R.java from being rebuilt successfully.
本文详细介绍了在Android开发过程中遇到的问题及其解决方法，包括但不限于：更新依赖、导入第三方库、处理资源文件冲突、配置环境一致性、解决Eclipse相关错误等。通过遵循步骤指南，开发者可以有效避免和解决开发过程中的常见问题，提高开发效率。
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
