Installing codes using processing 4.2, even if the given sample codes are successfully installed on the Android device/phone, crashes when I try running them. It worked before in processing 3, can’t find the issue. Any insights that you could share? Thank you

Hi @Myrdalm, Welcome to the forum! :wink: Without any information about your device / logs in the output window we can’t help you further with this! Can you provide more debug material?

Hi [image] [Android] 'Text is garbled.' When will it be resolved? help me Processing for Android ref link : [Android] Regarding the Android mode, has the text breakage been resolved? [Screenshot_20220925-122447] Please refer to the image. example) Korean / Japanese / English If you experiment through, All texts are broken except in English. CharSequence[] Choice_v = {"공급기-1","공급기-2","공급기-3","공급기-4","공급기-5","공급기-6"}; // Korean CharSequence[] Choice_v = {"FEED-1","FEED-2","FEED-3","FEED-4","FEED-5","FEED-6"}; // English I’ve mentioned it before. 2-1) There is no ‘text break phen…

Hello, I used the NoBackgroundTest code sample void setup() { size(400, 400, P2D); background(255, 0, 0); fill(255, 150); } void draw() { ellipse(mouseX, mouseY, 100, 100); } And below is the output in the console: Build folder: C:\Users\MMM\AppData\Local\Temp\android15489222564811472272sketch WARNING:We recommend using a newer Android Gradle plugin to use compileSdk = 33 This Android Gradle plugin (7.1.0) was tested up to compileSdk = 32 This warning can be suppressed by adding android.suppressUnsupportedCompileSdk=33 to this project’s gradle.properties The build will continue, but you are strongly encouraged to update your project to use a newer Android Gradle Plugin that has been tested with compileSdk = 33 Observed package id ‘platforms;android-33-ext5’ in inconsistent location ‘C:\Users\MMM\Documents\Processing\android\sdk\platforms\android-33’ (Expected ‘C:\Users\MMM\Documents\Processing\android\sdk\platforms\android-33-ext5’) Observed package id ‘platforms;android-33’ in inconsistent location ‘C:\Users\MMM\Documents\Processing\android\sdk\platforms\android-33-2’ (Expected ‘C:\Users\MMM\Documents\Processing\android\sdk\platforms\android-33’) Task :app:preBuild UP-TO-DATE Task :app:preDebugBuild UP-TO-DATE Task :app:mergeDebugNativeDebugMetadata NO-SOURCE Task :app:compileDebugAidl NO-SOURCE Task :app:compileDebugRenderscript NO-SOURCE Task :app:generateDebugBuildConfig Task :app:javaPreCompileDebug Task :app:generateDebugResValues Task :app:generateDebugResources Task :app:checkDebugAarMetadata Task :app:createDebugCompatibleScreenManifests Task :app:extractDeepLinksDebug Task :app:mergeDebugResources Task :app:processDebugMainManifest Task :app:processDebugManifest Task :app:mergeDebugShaders Task :app:compileDebugShaders NO-SOURCE Task :app:generateDebugAssets UP-TO-DATE Task :app:mergeDebugAssets Task :app:compressDebugAssets Task :app:processDebugJavaRes NO-SOURCE Task :app:checkDebugDuplicateClasses Task :app:mergeDebugJavaResource Task :app:mergeDebugJniLibFolders Task :app:mergeDebugNativeLibs NO-SOURCE Task :app:stripDebugDebugSymbols NO-SOURCE Task :app:validateSigningDebug Task :app:processDebugManifestForPackage Task :app:writeDebugAppMetadata Task :app:writeDebugSigningConfigVersions Task :app:processDebugResources Task :app:compileDebugJavaWithJavac Annotation processing got disabled, since it requires a 1.6 compliant JVM Task :app:dexBuilderDebug Task :app:desugarDebugFileDependencies Task :app:mergeExtDexDebug Task :app:mergeDexDebug Task :app:packageDebug Task :app:createDebugApkListingFileRedirect Task :app:assembleDebug Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0. You can use ‘–warning-mode all’ to show the individual deprecation warnings and determine if they come from your own scripts or plugins. See Command-Line Interface BUILD SUCCESSFUL in 37s 27 actionable tasks: 27 executed Though it is installed successfully, when I run the app, the app in the phone crashes, this only started when I started using processing which does not happen before when I used processing 3. [350350876_265617795951330_3640855877575243864_n]

Hi @Myrdalm. What version of Android is installed on your device? Which version of Android mode do you have installed with Processing? Also use the Processing Android examples to be certain that isn’t the issue. Try: void setup() { fullScreen(); noStroke(); fill(0); } void draw() { background(204); if (mousePressed) { if (mouseX < width/2) { rect(0, 0, width/2, height); // Left } else { rect(width/2, 0, width/2, height); // Right } } } Finally, check the Processing console print out for any other information. Usually it will provide information on what was the cause of the crash. If not there are apps for Android that print the crash logs. We need more info to figure out the issue.

I am using the Android 11 Version on my device. I am using Android Mode 4.5.1. intstalled with Processing. SDK updater has also updated everything to all the latest versions. The sample I used on my first test was from a Processing Android example. The code you used also had the same issue as the code I used earlier. Processing console print is the same as before, copied and paste below: Build folder: C:\Users\MMM\AppData\Local\Temp\android12071222152819130336sketch WARNING:We recommend using a newer Android Gradle plugin to use compileSdk = 33 This Android Gradle plugin (7.1.0) was tested up to compileSdk = 32 This warning can be suppressed by adding android.suppressUnsupportedCompileSdk=33 to this project’s gradle.properties The build will continue, but you are strongly encouraged to update your project to use a newer Android Gradle Plugin that has been tested with compileSdk = 33 Observed package id ‘platforms;android-33-ext5’ in inconsistent location ‘C:\Users\MMM\Documents\Processing\android\sdk\platforms\android-33’ (Expected ‘C:\Users\MMM\Documents\Processing\android\sdk\platforms\android-33-ext5’) Observed package id ‘platforms;android-33’ in inconsistent location ‘C:\Users\MMM\Documents\Processing\android\sdk\platforms\android-33-2’ (Expected ‘C:\Users\MMM\Documents\Processing\android\sdk\platforms\android-33’) Task :app:preBuild UP-TO-DATE Task :app:preDebugBuild UP-TO-DATE Task :app:mergeDebugNativeDebugMetadata NO-SOURCE Task :app:compileDebugAidl NO-SOURCE Task :app:compileDebugRenderscript NO-SOURCE Task :app:generateDebugBuildConfig Task :app:javaPreCompileDebug Task :app:generateDebugResValues Task :app:generateDebugResources Task :app:checkDebugAarMetadata Task :app:createDebugCompatibleScreenManifests Task :app:extractDeepLinksDebug Task :app:mergeDebugResources Task :app:processDebugMainManifest Task :app:processDebugManifest Task :app:mergeDebugShaders Task :app:compileDebugShaders NO-SOURCE Task :app:generateDebugAssets UP-TO-DATE Task :app:mergeDebugAssets Task :app:compressDebugAssets Task :app:processDebugJavaRes NO-SOURCE Task :app:checkDebugDuplicateClasses Task :app:mergeDebugJavaResource Task :app:mergeDebugJniLibFolders Task :app:mergeDebugNativeLibs NO-SOURCE Task :app:stripDebugDebugSymbols NO-SOURCE Task :app:validateSigningDebug Task :app:writeDebugAppMetadata Task :app:writeDebugSigningConfigVersions Task :app:processDebugManifestForPackage Task :app:processDebugResources Task :app:compileDebugJavaWithJavac Annotation processing got disabled, since it requires a 1.6 compliant JVM Task :app:dexBuilderDebug Task :app:desugarDebugFileDependencies Task :app:mergeExtDexDebug Task :app:mergeDexDebug Task :app:packageDebug Task :app:createDebugApkListingFileRedirect Task :app:assembleDebug Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0. You can use ‘–warning-mode all’ to show the individual deprecation warnings and determine if they come from your own scripts or plugins. See Command-Line Interface BUILD SUCCESSFUL in 36s 27 actionable tasks: 27 executed After using and updating processing android 4 and returning to processing 3, processing 3 is also not working anymore.

[image] Myrdalm: returning to processing 3, processing 3 is also not working anymore. Hi this works with processing 3 [image] Export to exe file Processing for Android I don’t have problems with this at all. I just use this SDK folder and unzip it in the documents/processing folder or elsewhere. Then open I the preferences.txt file. (The location you can find at the bottom of the File/settings menu.) In the android parameters you will find something like: android.emulator.image.abi=x86 android.emulator.port.phone=5566 android.sdk.ar=1.12.0 android.sdk.gvr=1.180.0 android.sdk.path=D:\an\android\sdk android.sdk.play_services=16.0.1 android.sdk.support=28.0.0 a…

@Myrdalm, If you are not seeing any other errors than the only other thing I can think of is to try setting your target sdk to 31 in your AndroidManifest.xml or you could change your compile sdk to 31 but you would have to have that installed. It looks like you’re compiling for sdk 33, aka Android 13, which usually doesn’t break things when testing on lower versions. But that is the only thing I can see that is different. Otherwise there are Android apps that let you read the debug log and there may be more information there, but it doesn’t appear that you are doing anything “wrong.” So my guess is it is either the device itself or the sdk version.

I tried using processing 3, but now it is updated with processing for, it is not working anymore compared to before. Below is the SS when I use processing 3 now. [342493221_685719969909223_6911726853347859757_n]

How do I set target sdk? I prefer using processing 4 though, due to the reason that it is the latest version. Have you tried using processing 4 in Android 11, 12 and 13? If so, can you share what you experienced and did it worked? I would appreciate it if you would be able to help me make it work instead of it crashing. Thank you

You can set the target sdk by editing the Preferences file. On a Windows 11 system it is located at C:/Users/yourName/AppData/Roaming/Processing/Preferences. However, when I try to change the value from 33 to 32, it just overwrites the file when I run the app the next time and sets it back to 33. The edit doesn’t ‘stick’; and yes, the Processing editor was closed when I made the change. I have an experience similar to yours and I run in Android mode on both Windows and Mac. The last update made it impossible for me to use the Windows OS for Processing Android apps. I got the Mac version to run after downloading a custom Android mode from github:https://github.com/processing/processing-android/issues/729#issuecomment-1516919114 Addendum: I just replaced the Android mode file on my Windows system with the github file above and it is now fixed; Android runs as expected except for the Gradle warning (which I have yet to figure out how to fix). However, my issue may be different from the one you are experiencing.

Installed Apps Crashes using Processing 4.2 Android Mode

Processing for Android

jafal May 31, 2023, 11:58pm 7

Hi this works with processing 3

Topic		Replies	Views
Android compilation fails also with the new Processing version 4.5.6 Processing for Android	13	409	August 16, 2026
Cannot run sketch on old Android kitkat device, using Processing 4 IDE Processing for Android	53	722	May 4, 2025
Problem with running a simple sketch on Android Processing for Android	53	1511	February 27, 2023
Android Mode Compiler, problem not solved yet Processing for Android	6	189	August 24, 2026
Android Programming for Beginners Processing for Android	14	472	August 1, 2025

Installed Apps Crashes using Processing 4.2 Android Mode

Related topics