I install the new droidplanner2 with full anticipation, but once installation completed and click open, a blank window with only the logo and that unfortunate massage is what all I get. I use Samsung note 10.1, old version. The previous version of droidplanner work well with this same device. In fact I had both version installed but only the old droidplanner able to work.
I am not sure if this is a hardware problem because the old droidplanner work perfectly. Please advice what should I do. Thanks
seems to be working on my gtp3113 also old… 4.03 ICS BUT cant find the Region of Interest feature no matter which beta I download it seems
sigh
HZL- Make sure you have the latest release github.com/DroidPlanner/droidpl … v2.2.4_RC6
- Try open that release
- If you have a problem, then go to the /Droidplanner/LogCat/ folder inside your device storage (plug it in a computer via usb), and copy and paste (on the forum) the contents of the latest file inside that folder.
@hotelzululima
ROI has been removed from the stable release since it wasn’t fully finished.
github.com/DroidPlanner/droidplanner/wiki/FAQ
Hy arthur i have the same problem. Note 10.1 wifi version Android version 4.1.1.
Here is the log
.java.lang.RuntimeException: Unable to start activity ComponentInfo{org.droidplanner/org.droidplanner.activities.FlightActivity}: android.view.InflateException: Binary XML file line #19: Error inflating class
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2110)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2135)
at android.app.ActivityThread.access$700(ActivityThread.java:140)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1237)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4921)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1038)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:805)
at dalvik.system.NativeStart.main(Native Method)
Caused by: android.view.InflateException: Binary XML file line #19: Error inflating class
at android.view.LayoutInflater.createView(LayoutInflater.java:613)
at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)
at android.view.LayoutInflater.onCreateView(LayoutInflater.java:660)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:685)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:746)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:749)
at android.view.LayoutInflater.inflate(LayoutInflater.java:489)
at android.view.LayoutInflater.inflate(LayoutInflater.java:396)
at org.droidplanner.fragments.TelemetryFragment.onCreateView(TelemetryFragment.java:36)
at android.support.v4.app.Fragment.performCreateView(Fragment.java:1500)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:927)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1104)
at android.support.v4.app.BackStackRecord.run(BackStackRecord.java:682)
at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1467)
at android.support.v4.app.FragmentActivity.onStart(FragmentActivity.java:570)
at org.droidplanner.activities.helpers.SuperUI.onStart(SuperUI.java:30)
at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1178)
at android.app.Activity.performStart(Activity.java:5216)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2083)
… 11 more
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Constructor.constructNative(Native Method)
at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
at android.view.LayoutInflater.createView(LayoutInflater.java:587)
… 29 more
Caused by: java.lang.NumberFormatException: Invalid int: "1.0dip"
at java.lang.Integer.invalidInt(Integer.java:138)
at java.lang.Integer.parse(Integer.java:375)
at java.lang.Integer.parseInt(Integer.java:366)
at com.android.internal.util.XmlUtils.convertValueToInt(XmlUtils.java:123)
at android.content.res.TypedArray.getInt(TypedArray.java:254)
at android.widget.TextView.(TextView.java:1004)
at android.widget.TextView.(TextView.java:569)
… 32 more
Thx for help
Thanks topografus, that stacktrace was really helpful. And it probably is an easy fix.
Keep an watch on this issue: github.com/DroidPlanner/droidplanner/issues/712 , or at this forum thread. I’ll comment when the issue is solved, and as for a test volunteer.
I’m having the same problem with my Samsung Galaxy Tab 3. It’s running 4.1.2 and like others I can load and run Droid planner one, but when I try to open Droid Planner 2 I get the 'Unfortunately droid planner has stopped. Like others I do see a white screen with the logo in the top left corner for a second or two and then the crash happens. Thanks for any help you can give.
Android 4.1.2
Kernel version 3.4.5-1304745-user
Samsung Galaxy Tab 3 - model SM-T210R
Build is JZ054K.T210RUEAMK1
Hi Arthur,
I’ve the same problem on Samsung Galagy Tab 2. (test on 2 Tab 2 platform)
Android 4.1.2
Kernel 3.0.31-812001
French language date numbers…
The apps crash at startup. The error log is the same above.
I hope you can make a realease?
Regards
Laurent
Just wish Arthur will release an update soonest possible.
Hi,
I have the same bug with the exactly same log.
Work fine with DP 1 but get msg"Unfortunately…" on DP2
Samsung TAB2 10.1(GT-P5110)
Android 4.1.2
Just an fyi… I have had that issue and it cleared up by going to the droid settings… apps… click on any and all versions of DP or anything similar and select force quit. Do it for all of them. Then try and relaunch the latest version of DP. Sometimes the tablet or phone OS doesn’t seem to fully quit the apps and they are hung or running in the background and you can accidentally have both trying to run at the same time. Or it’s getting in an argument with itself over the OTG cable. 
Not sure if it will work for you but it did / does for me. 
unless I am mistaken, this DP2 application is not compatible for Galaxy tab 2. 