just50415 / android-rcs-ims-stack

Automatically exported from code.google.com/p/android-rcs-ims-stack
0 stars 0 forks source link

RCS-e on Tablet #31

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

Is tablet(Androd 3.x platform) suppoprted?

I have installed RCS-e stack/provision/service on a Xoom Tablet and 
Thunderbolt.  I have no problem of starting/registering RCS-e client on the 
Thunderbolt (Android 2.x).  However, I am not able to start RCS-e service on 
the Xoom.  DDMS shows that following errors.  

Thanks in advance,
Feng

09-26 15:05:04.160: INFO/[RCS][Core](844): Terminal core initialization
9-26 15:05:04.160: ERROR/[RCS][RcsCoreService](844): Can't instanciate the RCS 
core service
09-26 15:05:04.160: WARN/System.err(844): java.lang.NullPointerException
09-26 15:05:04.160: WARN/System.err(844):     at 
com.orangelabs.rcs.utils.DeviceUtils.getDeviceUUID(DeviceUtils.java:32)
09-26 15:05:04.160: WARN/System.err(844):     at 
com.orangelabs.rcs.core.Core.<init>(Core.java:127)
09-26 15:05:04.160: WARN/System.err(844):     at 
com.orangelabs.rcs.core.Core.createCore(Core.java:93)
09-26 15:05:04.160: WARN/System.err(844):     at 
com.orangelabs.rcs.service.RcsCoreService.startCore(RcsCoreService.java:221)
09-26 15:05:04.160: WARN/System.err(844):     at 
com.orangelabs.rcs.service.RcsCoreService.onCreate(RcsCoreService.java:158)
09-26 15:05:04.160: WARN/System.err(844):     at 
android.app.ActivityThread.handleCreateService(ActivityThread.java:2039)
09-26 15:05:04.160: WARN/System.err(844):     at 
android.app.ActivityThread.access$2500(ActivityThread.java:122)
09-26 15:05:04.160: WARN/System.err(844):     at 
android.app.ActivityThread$H.handleMessage(ActivityThread.java:1059)
09-26 15:05:04.160: WARN/System.err(844):     at 
android.os.Handler.dispatchMessage(Handler.java:99)
09-26 15:05:04.160: WARN/System.err(844):     at 
android.os.Looper.loop(Looper.java:132)
09-26 15:05:04.160: WARN/System.err(844):     at 
android.app.ActivityThread.main(ActivityThread.java:4028)
09-26 15:05:04.160: WARN/System.err(844):     at 
java.lang.reflect.Method.invokeNative(Native Method)
09-26 15:05:04.160: WARN/System.err(844):     at 
java.lang.reflect.Method.invoke(Method.java:491)
09-26 15:05:04.160: WARN/System.err(844):     at 
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:844)
09-26 15:05:04.160: WARN/System.err(844):     at 
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:602)
09-26 15:05:04.160: WARN/System.err(844):     at 
dalvik.system.NativeStart.main(Native Method)
09-26 15:05:04.170: INFO/AudioHardware(226): mSetVolumeIndex=0, 
mIsMusicPlaying=0, musicvolumeindex=8

Original issue reported on code.google.com by hea...@gmail.com on 26 Sep 2011 at 8:00

GoogleCodeExporter commented 8 years ago
I never tested on this tablet and 3.x release.

It seems that the method getDeviceId() of Telephony API returns a null value. 
But why?

Original comment by jmauffret@gmail.com on 28 Sep 2011 at 8:10

GoogleCodeExporter commented 8 years ago
Nevertheless we should add an additional test to avoid NullPointerException in 
this case. This will be available in the next sprint (begining of October).

Original comment by jmauffret@gmail.com on 28 Sep 2011 at 8:29

GoogleCodeExporter commented 8 years ago
Thanks for replying.  FYI: The same null pointer error of getDeviceUUID is 
observed on the Samsung Galaxy 10.1" tablet.

Original comment by hea...@gmail.com on 28 Sep 2011 at 1:20

GoogleCodeExporter commented 8 years ago
Ok I will test on Galaxy tab. Thks

Original comment by jmauffret@gmail.com on 28 Sep 2011 at 1:29

GoogleCodeExporter commented 8 years ago
Just like to double check - the fix will be available early this October, 
right?  Thanks!

Original comment by hea...@gmail.com on 28 Sep 2011 at 2:03

GoogleCodeExporter commented 8 years ago

Original comment by jmauffret@gmail.com on 18 Oct 2011 at 2:20