TouchDRO app won't start

[ycroosh]

OK, so I know what the error is, but I have no clue how it happens.
I got two crash reports (both for Samsung devices) that are complaining about a problem with a gradient background having invalid settings.

Two problems:
1. I can't reproduce this on ANY of my tablets, Samsung or otherwise
2. I don't have a single gradient in the app, so I don't even understand how this could be happening.

 

[ycroosh]

My tablet is connected to the internet if there is something i can do to help you , please ask

I made some tweaks to the colors and pushed out a new Beta build. I have no clue if it will make any difference.
None of my tablets are experiencing this crash, so it's something very specific to a tablet/build combination.

 

[Garryloy]

Yuriy, I uninstalled my old version of the app, and installed the offering on google play store (build 2024-06-18. My tablet is a Samsung galaxy S2 like Steven's, running android 6). SUCCESS! Everything works now. I had to recalibrate, all three axis no problem. Now I'm checking the tablet options every couple of days to make sure automatic updates are not allowed.

Thank you for a super product. What do you do in your spare time?

 

[ycroosh]

Thank you for a super product. What do you do in your spare time?

Leet me check the dictionary to see what is that "spare time" thing you are speaking of ...
Seriously, though, if I had spare time, I'd be turning some innocent metal into scrap in my garage.

Glad the update got you going.

Regards
Yuriy

 

[RJSakowski]

Not related to the OP's problem but if you feel you need to reinstall and and need to recalibrate, can't you write down the CPI values for each axis an re-enter them when you reinstall?

 

[ycroosh]

Not related to the OP's problem but if you feel you need to reinstall and and need to recalibrate, can't you write down the CPI values for each axis an re-enter them when you reinstall?

Not when the app is crashing on start, unfortunately.
Also, I think there are two different issues at play here.
Garry likely had a problem due to the upgrade path. Looks like his version was pretty old, and some piece of data broke the upgrade. Reinstall is probably the only way to deal with it.
Steven is running into a theme problem with a specific Samsung tablet. Reinstalling the app won't do anything to the crash.

Going forward, I think I will need to add some sort of online backup option/function, so if one needs to reinstall or replace the tablet, the settings and the data can be restored.

 

[RJSakowski]

Not when the app is crashing on start, unfortunately.
Also, I think there are two different issues at play here.
Garry likely had a problem due to the upgrade path. Looks like his version was pretty old, and some piece of data broke the upgrade. Reinstall is probably the only way to deal with it.
Steven is running into a theme problem with a specific Samsung tablet. Reinstalling the app won't do anything to the crash.

Going forward, I think I will need to add some sort of online backup option/function, so if one needs to reinstall or replace the tablet, the settings and the data can be restored.

I was thinking that several people had a previous version working. I have a hard copy of all the settings for the axes so I can just re-enter them if/when I do a full install or an install on another device.

 

[ycroosh]

I was thinking that several people had a previous version working. I have a hard copy of all the settings for the axes so I can just re-enter them if/when I do a full install or an install on another device.

This is smart. I'm still not super proud that TouchDRO just bricks itself during update for random people. I get one or two of those per month, and it's always when upgrading from an old V3 build.
That code is executed on every upgrade on every tablet, and once in a blue moon the underlying database just throws up on that specific line. I've been chasing this error for a year, and can't reproduce it on anything. (I don't know how many hundreds of thousands of upgrades happen per month, but computers are not supposed to do random things )

This is the crash report for the last 30 days. The error in the middle (addMaxOrdinalColumn) is the thing that bricked Garry's app. (The others are not real crashes - they happen when the app is closed in the background when a dialog is open; users never see those).
The problem is that I have no control or visibility over how that process fires.

 

[Schtimpy]

Hi Yuriy,
Mine did not auto- update (since you released the tweak on Nov 5th) so i bit the bullet and uninstalled/reinstalled. Post reinstall I still have the same problem.
I cannot open the app at all: i get the same errors,
Regards
Steven

 

[ycroosh]

Hi Yuriy,
Mine did not automupdate so i bit the bullet and uninstalled/reinstalled i still have the same problem.
I cannot open the appbat all: i get the same errors,
Regards
Steven

Steven,
Unfortunately, I can't even figure out what is broken. I didn't even get a crash report today (your tablet might have "Send diagnostic data" disabled, or you are offline).
I tweaked some colors (just a wild guess, just in case). Today's build is "pending approval". Should be "2024-11-10".
Otherwise, I don't have good ideas for the next steps, short of hoping that this will break for someone else (there are about 978 active beta testers with the latest build...).
Regards
Yuriy