TheShanMan 34 Posted March 25, 2014 Share Posted March 25, 2014 I entered my user's password and the screen said "authenticating" but the spinner was frozen, the home button does nothing, and the clock in the status bar doesn't update. I had to press the lock button to unfreeze my phone. I'm getting tired of the app crashing and/or freezing my phone so I finally tried to dig around for the log file but can't seem to find it. Where do I find it? I have to say, I realize this is cutting edge stuff but as unstable as this app has been (for me at least) it seems like putting the app in the app store and charging money for it was premature. Hopefully I'm an isolated case though and if I can find the log file, the problems will be fixable and I'll get a stable app soon. Link to comment Share on other sites More sharing options...
Tikuf 663 Posted March 25, 2014 Share Posted March 25, 2014 I use it everyday and it doesn't crash for me so I would suggest it is actually your device(or server or network) rather than the app. That said logs will be on your phone you will need a file explorer. Look for a dir called Mb3AndroidData in your internal storage or sd card. I would suggest clearing it out then replicating the issue then posting the full log from the phone and the mb server log (debug) So Red can have a look at it Link to comment Share on other sites More sharing options...
Vidman 589 Posted March 25, 2014 Share Posted March 25, 2014 I have ALOT of problems with the android app too.... So you aren't an isolated case Link to comment Share on other sites More sharing options...
TheShanMan 34 Posted March 25, 2014 Author Share Posted March 25, 2014 Thanks. Somehow I overlooked that directory. However, I think it's a little silly to blame my device, server, or network rather than the app. The app should have sufficient error/exception handling. By a MILE this is the most unstable app on my phone. Of course it is likely related to something like server config, network, what have you, but the blame likely doesn't lie there. Anyway, I grabbed the entirety of the android and server logs for that time period. Pretty short and sweet, so hopefully this helps. [Mon Mar 24 18:44:31 PDT 2014] , Info , Application Version: 1.0.31 , 1 , main[Mon Mar 24 18:44:31 PDT 2014] , Info , Device: SAMSUNG-SGH-I337 , 1 , main[Mon Mar 24 18:44:31 PDT 2014] , Info , Screen Width: 1080 , 1 , main[Mon Mar 24 18:44:31 PDT 2014] , Info , Screen Height: 1920 , 1 , main[Mon Mar 24 18:44:31 PDT 2014] , Info , Total Memory Available: 246 MB , 1 , main[Mon Mar 24 18:44:31 PDT 2014] , Info , Max Memory usable per Application: 128 MB , 1 , main[Mon Mar 24 18:44:31 PDT 2014] , Info , Application object initialized , 1 , main[Mon Mar 24 19:08:19 PDT 2014] , Info , Logger Started , 1 , main[Mon Mar 24 19:08:19 PDT 2014] , Info , Initializing FileUtils helper class , 1 , main[Mon Mar 24 19:08:19 PDT 2014] , Info , Loading server list from app directory , 1 , main[Mon Mar 24 19:08:19 PDT 2014] , Info , Trying to load last connected server from file system , 1 , main[Mon Mar 24 19:08:19 PDT 2014] , Info , Loading last connected server from app directory , 1 , main[Mon Mar 24 19:08:19 PDT 2014] , Info , Reconnecting to @ <edited> , 1 , main[Mon Mar 24 19:08:19 PDT 2014] , Info , Connectivity reports it should connect , 1 , main[Mon Mar 24 19:08:19 PDT 2014] , Info , User Selection Fragment: onCreateView , 1 , main[Mon Mar 24 19:08:20 PDT 2014] , Info , User Selection Fragment: User available, initializing view , 1 , main[Mon Mar 24 19:08:22 PDT 2014] , Info , User Login Activity: User 0 clicked. , 1 , main[Mon Mar 24 19:08:22 PDT 2014] , Info , User Login Activity: User has password , 1 , main[Mon Mar 24 19:08:22 PDT 2014] , Error , User Login Activity: User has password, showing password entry dialog , 1 , main[Mon Mar 24 19:08:28 PDT 2014] , Info , Attempting Authentication , 1 , main[Mon Mar 24 19:08:28 PDT 2014] , Info , AuthenticateUserCallback , 1 , main[Mon Mar 24 19:08:28 PDT 2014] , Info , Data received , 1 , main[Mon Mar 24 19:08:28 PDT 2014] , Info , HTTP RESPONSE 200 , 1 , main[Mon Mar 24 19:08:28 PDT 2014] , Error , Uncaught Exception , 1 , main[Mon Mar 24 19:08:28 PDT 2014] , Error , Stack Trace: java.lang.NullPointerException at com.mb.android.activities.MainActivity$AuthenticateUserCallback.Execute(MainActivity.java:671) at com.mb.android.api.asyncrequests.AsyncPost.onPostExecute(AsyncPost.java:141) at com.mb.android.api.asyncrequests.AsyncPost.onPostExecute(AsyncPost.java:25) at android.os.AsyncTask.finish(AsyncTask.java:631) at android.os.AsyncTask.access$600(AsyncTask.java:177) at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:644) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:137) at android.app.ActivityThread.main(ActivityThread.java:5419) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:525) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1187) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003) at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:126) at dalvik.system.NativeStart.main(Native Method) , 1 , main 2014-03-24 19:08:30.2614 Debug - HttpServer: HTTP POST http://<edited>:8096/mediabrowser/Users/7ae39702177807ab58138da9a6d7d855/Authenticate?format=json2014-03-24 19:08:30.2614 Info - App: Authentication request for Adults has succeeded.2014-03-24 19:08:30.2614 Info - App: Sending web socket message UserUpdated2014-03-24 19:08:30.2614 Debug - HttpServer: HTTP Response 200 to 192.168.217.113:34293. Response time: 3.0003 ms Url: http://<edited>:8096/mediabrowser/Users/7ae39702177807ab58138da9a6d7d855/Authenticate?format=json2014-03-24 19:08:30.2614 Debug - HttpServer: HTTP GET http://<edited>:8096/mediabrowser/Users/7ae39702177807ab58138da9a6d7d8552014-03-24 19:08:30.2734 Debug - HttpServer: HTTP Response 200 to 192.168.217.99:51717. Response time: 3.0003 ms Url: http://<edited>:8096/mediabrowser/Users/7ae39702177807ab58138da9a6d7d8552014-03-24 19:08:34.7979 Debug - HttpServer: HTTP GET http://<edited>:8096/mediabrowser/System/Info?format=json2014-03-24 19:08:34.8329 Debug - HttpServer: HTTP Response 200 to 192.168.217.113:42042. Response time: 34.0034 ms Url: http://<edited>:8096/mediabrowser/System/Info?format=json Link to comment Share on other sites More sharing options...
TheShanMan 34 Posted March 27, 2014 Author Share Posted March 27, 2014 Are my logs helpful enough to fix this problem? Link to comment Share on other sites More sharing options...
Redshirt 1487 Posted March 27, 2014 Share Posted March 27, 2014 I haven't looked at this in depth yet, but it will be fixed for next release. Link to comment Share on other sites More sharing options...
TheShanMan 34 Posted March 28, 2014 Author Share Posted March 28, 2014 Awesome. It's about time I got off my butt and rather than just complaining about stability, actually helping you pinpoint the problems. Any thoughts on when the next release will be coming? Thanks! Link to comment Share on other sites More sharing options...
Redshirt 1487 Posted March 28, 2014 Share Posted March 28, 2014 Hopefully I'll release to my beta team this weekend. Then release publicly some time next week, or that weekend. If you give me logs, combined with steps to reproduce issues, I'll do everything in my power to fix those issues. If you just complain that I could be a better programmer, which I admit is true... I'm not going to do anything other than feel sad Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now