App crashes consistently on ET1 JB 4.1.1 -- works flawlessly on all other tablets

D Didrik Wold 3 years 7 months ago
3 2 0

Thanks in advance for your time and consideration.
 
I got the tablet updated and all the patches/fixes installed and everything looked great.
 
However, I've now run into another problem. The application that we use to carry out our inspections, keeps crashing at the same point when I try to run it on the ET1. It's 100% consistent and repeatable. It's something as simple as every time I try to select an option from a specific drop-down menu, the app crashes immediately.
 
The app functions flawlessly on every single other Android device I've tried, with the exception of the ET1. The only difference that I can see is the custom AOSP-based operating system you have on the ET1. What is missing there that could cause this problem? I'm guessing there's some framework/api/etc that's missing that the app needs? I just don't know what it is, or how to fix it.
 
The other problem I have is that I neither have access to the source code, nor the developer of the app, to try and debug and figure out WHY this is happening.
 
I really need to figure this out because without this particular application, the tablet is essentially useless to me.
 
What can I do?
 
Thanks again.
 
All the best,
Didrik
 
PS - Is there a way to get root access on this tablet?

Please Register or Login to post a reply

2 Replies

Y Yanis Dalabiras

What would help to get to the bottom of this would be logs from the device.  If you are familiar with ADB (usually used by developers), you could run ADB logcat and take a look in the debug log to see what errors might be happening when the app crashes. You would need to load our USB driver on your Windows machine to use ADB with the ET1. 
https://portal.motorolasolutions.com/Support/US-EN/Resolution?solutionI…
You would also need to load some Android developer SDK stuff. 
Android Debug Bridge | Android Developers

Adb can be a little difficult to setup and get working properly, and the Android SDK is very large, so if you are not familiar with adb and already have it working, it might be easier to use our RxLogger tool to grab the logs.    Not sure if RxLogger is preloaded on the ET1, but if not you should be able to download it from here.
Tips and Tricks

If you can get a logcat log from when the app crashes and post the relevant section here, we might be able to at least tell you what appears to be causing the app to crash.

D Didrik Wold

Hi Daniel -- thanks for the quick reply!

See below for the error log (not having the original source code, I don't think I can debug any further than this):

10-09 20:55:47.019: W/ActivityThread(5690): Application com.PIC can be debugged on port 8100...
10-09 20:55:47.065: D/dalvikvm(5690): GC_FOR_ALLOC freed 84K, 10% free 7391K/8131K, paused 24ms, total 25ms
10-09 20:55:47.073: I/dalvikvm-heap(5690): Grow heap (frag case) to 8.304MB for 539252-byte allocation
10-09 20:55:47.104: D/dalvikvm(5690): GC_CONCURRENT freed

CONTACT
Can’t find what you’re looking for?