Damn. So, I'm definitely losing my save data no matter how we do this?
I am more suprised that the developers behind TiTS didnt take it into account I think there is a babel/webpack plugin that will do it.
It's all good, crap happens.
As long as intentions are good, can't fault someone, really. :] As far as save data goes, you'd only be able to back up with root until they fix it. Quite frankly, it'd be easier to play via browser. At least then you could tell it to use Desktop Mode and get touch to work natively...and local file backups if that isn't broken on Android too as files.. It's been a few years since I used local HTML files in Android...anyone know if still possible? (If you need a quick setup, use uas to sign, 
java -jar ./uas.jar -a ./com.fenoxo.tits.apk).
I played using the browser for the first couple months until they actually made a .apk build. Desktop mode did not enable the tooltips to work natively, unfortunately. It'd be the same issue. (Though I guess at least then I could pop the .js file open and do it myself.)It's all good, crap happens.
It'd be easiest to tell the developer(s) of TiTs to add those functions.
The Desktop Mode might enable the file saving, is what I was wondering. Combine that with the main.*.js patch, you might have a nice setup until the developer(s) add the change. I use rooted Android 11+, so I don't have Scoped bull on me.I played using the browser for the first couple months until they actually made a .apk build. Desktop mode did not enable the tooltips to work natively, unfortunately. It'd be the same issue. (Though I guess at least then I could pop the .js file open and do it myself.)
Afaik, using HTML files locally in android works except maybe in android 11 and 12. I think that the scoped storage update/storage system changes they made after 10 effectively broke it. Not sure since I don't have a device that new to test it on.
Edit:I have now moved on to testing my dumb idea. initial results show promise. Nevermind. broke the app.
Ah, gotcha. Saving to file does work in browser, yeah. I switched to the app because I had accidentally cleared my local browser cache without backing up my saves first (a classic 3 AM ultra-tired brain mistake) and lost my saves. Didn't want to worry about that again.The Desktop Mode might enable the file saving, is what I was wondering. Combine that with the main.*.js patch, you might have a nice setup until the developer(s) add the change. I use rooted Android 11+, so I don't have Scoped bull on me.
Go for it.
Remember to let them know that tapping still clicks, you basically just 'finger on and move out of the way and keep the finger on screen to see the description'. I think the APK won't ever have local saving just because it is a sandbox browser. Not sure how to resolve that one, I don't do Electron. They should be able to simply alias the names with the touch-enabled names, and it'll work for both without needing anything else. Never rely on a browser for anything. Always use external saves.
in terms of electron downloading the closest thing I found from simple googling is thisGo for it.
Done. Hopefully the dev actually implements it. (Doubtful, though.) In only semi-related news, I discovered while working with another device to test out modifying the apk with luckypatcher that total commander apparently removed the ability to install .apks from it at google's request. So that's a thing. Can't do shit with your own devices anymore apparently.Go for it.
Electron works fine outside of Android. I think it might have something to do with APK permissions...I'm too lazy to logcat. It CAN load files. Edit: Checked permissions, Files and Media was set automatically to Denied. Makes no difference when allowed, Save to File doesn't even throw an error in the backend..
Yup. Here's what google cited in their warning to the dev:
I would if I could. Unfortunately I use Verizon as my carrier (I work in some very rural areas where they're literally the only carrier with anything approaching reliable service) and verizon phones are... difficult... to root. They tend to have some proprietary firmware shit which makes it so rooting doesn't work the same way it does for the same model of phone not from verizon. Depending on the phone, you can still root, but it's not as straightforward. I just don't like to chance it.
You can debrand a lot of specific-brand devices. I've often converted a lot of Samsungs that way, flashed custom CSCs and even modified a few CSCs to support features from other carriers.
Yeah, fair. Rooting is a very good thing and I highly recommend people do it, I'm just not willing to do it myself because the last time I tried, I bricked my phone (after I had replaced it, thankfully)
If it is a Qualcomm chipset, you can always use EDL to restore it, even if completely bricked.
Well, there's also the part where I don't know what EDL is. I'm currently using a 2017 motorola XT-1635. My bricked phone was a Galaxy S3, I believe I hit a Knox trigger or something and it just completely locked the phone. Couldn't boot into recovery or anything.
Knox is only about whether a phone has been rooted. Won't stop a phone from booting. Play Store uses it to help apps say 'f-off, omg you took control of your device, we no trustz you'. Netflix and other banking apps will not show up in Play Store for that device. Probably flashed/rooted incorrectly, it happens. Check out XDA sometime.
I'm familiar with XDA, it was of tremendous help in fixing up my fire tablet to work like a decent android tablet instead of being locked to only Amazon crap.