(11-09-2021 12:25 AM)Thomas Okken Wrote: (11-09-2021 12:00 AM)rprosperi Wrote: I'm honestly confused as to why 3.0.6 worked before if nothing in this area changed As long as it's documented! All this is a bit annoying for people who still remember when Android apps basically had the run of the entire filesystem.īTW, the built-in skin loader will load skins to /data/data//files, so as long as you're trying to use skins that are available for download from an HTTP server somewhere, that method of putting skins in the right place should always work. I don't see any strong reason to jump through hoops to allow Free42 to access other corners of the filesystem, as long as users are able to store skins in the standard data directories without a lot of trouble. I should probably add a note to the documentation that that's the right place to store skins. The former, or rather, /data/data//files, is where Free42 stores its state files, so if that /Free42 directory you can see in the file manager contains files named "state" and "print", and the *.f42 state files, it's the right one. There are two commonly used directories that Android apps should have access to even without being granted any special permissions: /data/data/, which is in the main filesystem, and /sdcard/Android/data/, in external storage. Maybe this helps? I'd rather not side-load if it can be avoided, due to a troubled past doing so in very early Android days. So, it must have something to do with folder access, or permissions, etc. I have confirmed that Free42 is sensing the rotation and "knows" which mode it's in when opening the dialog. I then copied the *.layout files to the /Downloads folder and then navigate there in the "Skin: Other" dialog and these files are also not visible there, where they should be as this folder is obviously available to the user. Quick update - I compared my new phone (A12) with my old phone (A8) side-by-side and I now notice that when in the "Skin: Other" dialog, the *.layout files are not visible (in the file display area where one would pick a file), even though I've confirmed that these files are actually in the /Free42 folder. I uploaded a 3.0.7 build with target sdk = 29 to - Bob (or anyone else experiencing the screen rotation issue), could you try installing this, and let me know what happens? (11-08-2021 10:31 AM)Thomas Okken Wrote: I haven't been able to reproduce the problem in the Android 11 and 12 emulators (API levels 30 and 31). changes that should affect this deliberately, it's not impossible I've changed something by mistake there's a lot of new and different things in A v12. It appears to be something that changed in 3.0.7, but I can't 100% rule out that something in the phone (or Android 12) might be the cause. My new phone is actually Android 12 (a Pixel 6 Pro) but as I noted, 3.0.6 was working yesterday on the same phone. My own phone, running Android 8.1, doesn't have the rotation problem, so it's of no use for spotting or troubleshooting the issue I'll see if I can reproduce it in the Android 11 emulator tomorrow. The whole thing was a bit mysterious to me to begin with. Maybe that change defeated the 2.5.24a fix. With 3.0.7, I had to change the target sdk version from 29 to 30, i.e. (11-08-2021 12:10 AM)Thomas Okken Wrote: That sounds like the issue that I fixed in 2.5.24a, back in January: the app not switching between portrait and landscape skins on Android 11.
0 Comments
Leave a Reply. |