on 11-01-2012 7:57 AM
11-01 13:07:30.423: I/Choreographer(704): Skipped 44 frames! The application may be doing too much work on its main thread.
11-01 13:07:32.043: D/UnReg- doin Background---(704): Before Unregister
11-01 13:07:32.053: D/==>onRegistrationStatusChanged(704): App.RegStatus=204, errorCode=0, errorMsg=
11-01 13:07:32.093: D/==>onConnectionStatusChanged(704): App.ConnctionStutus=104, errorCode=0, errorMsg=
11-01 13:07:32.213: I/MocaLog(704): 01T130732, T5, ThreadID = Thread[unregisterApplication,5,main] maps to short thread id 5
11-01 13:07:32.233: W/System.err(704): fsync failed: EBADF (Bad file number)
11-01 13:07:32.233: I/MocaLog(704): 01T130732, T5, Applog Status - 1351755452094:2:4
11-01 13:07:32.373: I/Choreographer(704): Skipped 63 frames! The application may be doing too much work on its main thread.
11-01 13:07:32.483: W/System.err(704): fsync failed: EBADF (Bad file number)
11-01 13:07:32.643: I/MocaLog(704): 01T130732, T5, MocaLibrary: shutdownClient exception:
11-01 13:07:32.643: I/MocaLog(704): java.lang.UnsupportedOperationException
11-01 13:07:32.643: I/MocaLog(704): at java.lang.Thread.stop(Thread.java:1076)
11-01 13:07:32.643: I/MocaLog(704): at java.lang.Thread.stop(Thread.java:1063)
11-01 13:07:32.643: I/MocaLog(704): at com.sybase.mo.MessagingClientLib.shutdownClient(MessagingClientLib.java:249)
11-01 13:07:32.643: I/MocaLog(704): at com.sybase.mobile.Application.stopConnectionCall(Application.java:622)
11-01 13:07:32.643: I/MocaLog(704): at com.sybase.mobile.Application.access$900(Application.java:43)
11-01 13:07:32.643: I/MocaLog(704): at com.sybase.mobile.Application$2.run(Application.java:447)
11-01 13:07:32.713: W/System.err(704): fsync failed: EBADF (Bad file number)
11-01 13:07:32.773: D/com.sybase.mobile.Application(704): stopConnectionCall
11-01 13:07:32.773: D/com.sybase.mobile.Application(704): Error: 14899 Message: null
11-01 13:07:32.773: D/com.sybase.mobile.Application(704): at com.sybase.mo.MessagingClientLib.handleException(MessagingClientLib.java:1119)
11-01 13:07:32.773: D/com.sybase.mobile.Application(704): at com.sybase.mo.MessagingClientLib.shutdownClient(MessagingClientLib.java:286)
11-01 13:07:32.773: D/com.sybase.mobile.Application(704): at com.sybase.mobile.Application.stopConnectionCall(Application.java:622)
11-01 13:07:32.773: D/com.sybase.mobile.Application(704): at com.sybase.mobile.Application.access$900(Application.java:43)
11-01 13:07:32.773: D/com.sybase.mobile.Application(704): at com.sybase.mobile.Application$2.run(Application.java:447)
11-01 13:07:32.793: D/==>onConnectionStatusChanged(704): App.ConnctionStutus=101, errorCode=14899, errorMsg=null
11-01 13:07:32.917: D/unregisterUser()(704): Unable to unregister user
11-01 13:07:32.917: D/UnReg- doin Background---(704): After Unregister
11-01 13:07:32.917: D/UnReg- doin Background-RegStatus--(704): 204
11-01 13:07:33.213: I/Choreographer(704): Skipped 96 frames! The application may be doing too much work on its main thread.
11-01 13:07:33.353: I/Choreographer(704): Skipped 34 frames! The application may be doing too much work on its main thread.
11-01 13:07:33.533: I/Choreographer(704): Skipped 40 frames! The application may be doing too much work on its main thread.
11-01 13:07:33.813: I/Choreographer(704): Skipped 73 frames! The application may be doing too much work on its main thread.
11-01 13:07:34.613: I/Choreographer(704): Skipped 40 frames! The application may be doing too much work on its main thread.
11-01 13:07:35.203: D/Login(704): unable to unregister User....
11-01 13:07:46.223: I/Choreographer(704): Skipped 41 frames! The application may be doing too much work on its main thread.
11-01 13:07:48.183: D/UnReg- doin Background---(704): Before Unregister
11-01 13:07:48.183: D/Unregister Application:(704): 204
11-01 13:07:48.183: D/UnReg- doin Background---(704): After Unregister
11-01 13:07:48.183: D/UnReg- doin Background-RegStatus--(704): 204
11-01 13:07:48.393: I/Choreographer(704): Skipped 38 frames! The application may be doing too much work on its main thread.
11-01 13:07:49.033: I/Choreographer(704): Skipped 33 frames! The application may be doing too much work on its main thread.
11-01 13:07:50.593: D/Login(704): unable to unregister User....
11-01 13:09:44.763: I/Choreographer(704): Skipped 30 frames! The application may be doing too much work on its main thread.
11-01 13:16:12.134: I/MocaLog(704): 01T131612, T1, MoObject.execute -- caught TM exception - 28:com.sybase.messaging.traveler.TmException: TM Error: InterruptedIOException:Request Timed Out
11-01 13:16:12.143: W/System.err(704): fsync failed: EBADF (Bad file number)
11-01 13:16:12.296: I/MocaLog(704): 01T131612, T1, processTillStoppedGuts -- Post to server timed out (this is normal)
11-01 13:16:12.296: W/System.err(704): fsync failed: EBADF (Bad file number)
11-01 13:17:30.399: I/Choreographer(704): Skipped 35 frames! The application may be doing too much work on its main thread.
11-01 13:17:45.774: I/Choreographer(704): Skipped 34 frames! The application may be doing too much work on its main thread.
Here is the code which i wrote to unregister the application
try {
Log.d("UnReg- doin Background---","Before Unregister");
unregisterUser();
ConnectivityManager cm = (ConnectivityManager) getSystemService(Context.CONNECTIVITY_SERVICE);
NetworkInfo netInfo = cm.getActiveNetworkInfo();
if (netInfo != null && netInfo.isConnected())
{
app.unregisterApplication(30);
Log.d("Unregister Application: ", app.getRegistrationStatus() + "");
}
Log.d("UnReg- doin Background---","After Unregister");
Log.d("UnReg- doin Background-RegStatus--",app.getRegistrationStatus()+"");
}
catch (InterruptedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
XXXXDB.cleanAllData();
try
{
if(XXXXDB.databaseExists())
XXXXDB.deleteDatabase();
}
catch (PersistenceException e) {
// TODO: handle exception
Log.d("UnReg- on PostExecute---", e.getMessage()+"@@@"+e.getCause());
}
Thanks,
Ramesh Prasad
Hi,
What is the reason for you to unregister the application. Whats the whole purpose of it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rakhsit,
We have a Reset button in login screen, where they can reset the current user properties for that application and do login with the new user credentials.
The application can be used by more users by reset/changing the credentials on the same device(android).
The Unregistration has happened in android devices having android 2.2 & 2.3.3.
But when we try to reset on devices having more than Android 4.0, it is happening sometimes but not all the times.
Thanks,
Ramesh
User | Count |
---|---|
80 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.