|
|
Post by charixfox on Jan 6, 2020 19:07:05 GMT
When loading either default Elite Dangerous project or the Star Citizen Tablet project on a Samsung Galaxy Tab A 10.1, the app turns to a black screen then crashes.
Please let me know if dumps or any debug or diagnostic information will be helpful.
I stripped the project down substantially for attrition testing and finally got it to load. Not certain whether it is a control specific to the white panel on the Fight tab or something else (such as memory exhaustion on the tablet or tablet-specific App-whacking for whatever reason.)
|
|
|
|
Post by Admin on Jan 9, 2020 18:48:40 GMT
do you only have a problem with the default ED or SC project ?
|
|
|
|
Post by charixfox on Jan 10, 2020 0:27:43 GMT
Of the default projects, yes.
I stripped the majority of the default project and it worked. Then added more things and it worked. But then the other user here added more more things and it crashed again. Then apparently changed some things and it worked again. It may be related to copies of nodes. Getting more difficult to do troubleshooting and testing since the tablet is in her possession now and she just wants to Use It.
|
|
|
|
Post by khontrol on Feb 7, 2020 1:14:00 GMT
Same here on Samsung Galaxy Tab A 10.1 (T515N). On the 3rd screen I wanted to have a keyboard. So I started with a panel. On it I put duplicated buttons an saved. Everything went fine until I started to change the texts of the buttons (a different key per button). At some point after editing a few buttons and saving, LEA just crashed (back to home screen) on the tablet. On my Samsung Galaxy Note 4 it works fine.
For troubleshooting reasons I started to work with one panel per row. I could reproduce the crash bug. The first screenshot I attached works on the tablet. When I change one more button text, any text, and save, LEA crashes. Reverting back to the previous text and saving does not work. I need to delete the panels and get them back (via template) to get it running again. I have tested further and can use 4 or more identical rows but not two rows with different texts (second screenshot) for example. Also, but not so important by far: The screen is stretched vertically on both devices (see photo of tablet - good to see on the circle). I hope you can help soon. I just bought the software and was really excited to have a game themed keyboard on my tablet. Ah, and another one: The white vertical lines in the top bar shouldn't exist. As you can see, the last vertical line is not visible. I tried everything but can't get them to disappear or just be black. Also, when I choose to not show the top bar, the hamburger menu is not placed in the space for the top bar but into the button zone, partly concealing the top right button. So you don't gain the extra space when choosing not to use the top bar and in fact have less space...  Attachments:
|
|
|
|
Post by jordan on Feb 8, 2020 19:42:59 GMT
I've got 2 Samsung tablets, a Tab S2 8.0 and a tab S4 and the default Elite Dangerous projects work on the tab S2 but not on the tab S4. It crashes when loading. I am trying to work through it and to figure it out. If you need anything from me please let me know.
|
|
|
|
Post by talktoadocabouted on Feb 10, 2020 5:15:29 GMT
I found this thread because I had a very similar problem. The stock Elite Dangerous has always caused a client crash on all of mobile devices; a Samsung Galaxy Tab A 10.1 (T580), a Pixel XL running Android 10, and a Pixel 2 XL also on Android 10.
I created my own control screen and it had worked perfectly fine... until I added a new screen with a slew of new buttons. They were all just Button resources and none of them with complicated macros. When loading the project, the client would lock briefly, then exit.
After a whole lot of troubleshooting and frustration, I started removing one button at a time from the new screen. I finally found *the* button that seemed to be causing the crash. Removing *only* that button got the clients to work. The only thing I can tell that was different about that button was the background color; it was set to _completely) red (R:255,G:0,B:0,A:255). On a whim I slid the picker further down (R:226,G:29,B:29,A:255) and have had no issues since.
It seems unlikely that this is the exact cause of anyone else's crashes, but hopefully it provides a data point that makes chasing down whatever is behind it easier.
|
|
