j9.7.0-beta4

[Paul Jackson]

The beta4 update on Windows 11 removes the failure Cameron reported and gets the correct answer.

  ]X=: 3 8 4 3 2,:7 8 3 1 0

  ]Y=: (,:,:8);(,:3 2);,:3 1   

  X ([:I.E.~)&.(a:`>) Y  NB. correct answer

  X I.@E.~&.(a:`>) Y   NB. now also correct answer

However, on Android 12 the visible interface crashes before installation is complete. I assume J itself is continuing to run as I continue to see alerts appear and disappear. Also, the folders.cfg file is overwritten. Subsequently clicking on the J icon for the beta immediately crashes with no messages.

Because I've been curious about overcoming the problems with Android 15, I attempted an install of beta4 there. Unlike all previous releases, this install appears to have run to completion. However once installed it fails in exactly the same way as the install on Android 12.

[Jan-Pieter Jacobs]

I updated to J9.7-Beta4 on Android 14 (Samsung version) and couldn't make it work either. As Paul mentioned, the interface closes the moment it is opened, but some toaster pop ups still appear.

A clean reinstall gets the same results as updating the app.

Jan-Pieter

To unsubscribe from this group and stop receiving emails from it, send an email to forum+un...@jsoftware.com.

[bill lam]

I have updated the android tool chain and migrated to api level 24. It works for android-10, my android phone and tablet;-).

From emulator logcat, the crash happened in JE. Maybe some security issues. I am working on it.

[bill lam]

Did jandroid work on android 11 & 12 previously?

To unsubscribe from this group and stop receiving emails from it, send an email to forum+un...@jsoftware.com.

[Paul Jackson]

Yes, I have two devices which cannot be upgraded beyond Android 12. Both work fine through 9.6.3. I've installed 9.7, and everything was working until beta 4. Please note, after installing beta 4, I have difficulty getting things cleaned up well enough to reinstall beta 3, however beta 1 reinstalls without problems.

I'm happy to keep testing support for Android's api level 24 as a Google search has confirmed that's the minimum requirement for installing on Android 15. My current phone is at Android 15, and the current beta 4 is the first release which has installed on it.

Paul

[bill lam]

I modified the AndroidManifest and it now works on emulator Android 16 beta.
Please download and test again. Thanks.

[Paul Jackson]

J9.7 beta 4 now installs on a new system without complaint. However once I give it file access and copy my startup.cfg to ~config, I can't get to my code in public directories.

I described the condition to Google search, and the following sounds like what I see with the J dir verb. In a public path, directories are visible but files are not.

• In Android API 31 (Android 12), an app might be able to list directories but not see files within them. This is because of the Scoped Storage model introduced in Android 10 (API 29), which restricts access to shared files to ensure user privacy and security. 

• Here's a breakdown of the issue and potential solutions:

• Scoped Storage:
  Android 12 (and later) enforces Scoped Storage, limiting apps' direct access to shared files on external storage. This means an app might be able to see a directory in a file manager, but not the files inside it if those files were not created or modified by the app itself. 

• Permissions:
  You might need to request and grant the necessary permissions (e.g., READ_EXTERNAL_STORAGE) to access external storage, according to Stack Overflow. 

• Storage Access Framework (SAF):
  To access specific files or directories, use the SAF. The ACTION_OPEN_DOCUMENT_TREE intent action allows users to grant access to a directory and all its sub-directories.