Page 1 of 2
Crash at startup (Sony Xperia dual M)
Posted: 13 Sep 2015, 22:42
by kjiratsiekoedel
Just got my Nissan Consult bluetooth device. However I don't get NDS1 lite working on my phone. When I start the app it crashes after 1 second. I Have a Sony Xperia dual M running Cyanogenmod 11.
But the same problem occurs with the phone of my wife (Sony Xperia dual M stock ROM).
Same problem with NDS2 lite (not that I can use it for my car, but just to try)
Any idea how to solve this?
Re: Crash at startup (Sony Xperia dual M)
Posted: 21 Sep 2015, 11:09
by Tom
Are you able to submit a crash report when it happens again? We can then have a look at what is causing the problem.
Re: Crash at startup (Sony Xperia dual M)
Posted: 21 Sep 2015, 19:39
by kjiratsiekoedel
No, it just tells that 'the application has stopped' and then it closes down.
Re: Crash at startup (Sony Xperia dual M)
Posted: 22 Sep 2015, 12:19
by Jason
What Android version is it?
Re: Crash at startup (Sony Xperia dual M)
Posted: 24 Sep 2015, 23:48
by kjiratsiekoedel
Phone: Sony Xperia dual M (model c2005)
Android: 4.4.4 (cyanogenmod 11)
My wife has the same, but running stock android 4.3 ROM
Re: Crash at startup (Sony Xperia dual M)
Posted: 01 Oct 2015, 22:12
by kjiratsiekoedel
Just updated to CM12.1 (android 5.1.1)
Same problem, but now I'm able to upload a crash report. How can I send this to you?
Re: Crash at startup (Sony Xperia dual M)
Posted: 07 Oct 2015, 17:02
by Tom
Are you able to send it to our email address
nissandatascan@yahoo.com?
We are still trying to replicate the fault.
Re: Crash at startup (Sony Xperia dual M)
Posted: 15 Oct 2015, 19:30
by Tom
I think we have identified the problem. It's related to the resolution of your screen.
Can you try starting the app when the phone is in landscape orientation?
Re: Crash at startup (Sony Xperia dual M)
Posted: 15 Oct 2015, 21:24
by kjiratsiekoedel
yes# you've fond it!
If I start landscape it doesn't crash. When I turn to portrait it crashes
Re: Crash at startup (Sony Xperia dual M)
Posted: 24 Oct 2015, 00:38
by Tom
It's due to a unique screen resolution of your device. We are working on a fix and it will be implemented in the next release.