I got this to compile but...

[chronic8000]

How can I put the wad in the Android/data/obb/com.whateveritwas/files folder? I don't seem to have write access to that folder. I know Android is a nightmare for this do you know any workarounds? I got it to compile OK and also for Android Wear so I can run it on the Pixel Watch but I don't appear to be able to get it to recognise the doom.wad. Any help would be appreciated thanks for your work so far!

[chronic8000]

[deqart]

you have to create the folder "app/src/main/assets" with a file inside matching any of these wad names
static const iwad_t iwads[] = { { "doom2.wad", doom2, commercial, "Doom II" }, { "plutonia.wad", pack_plut, commercial, "Final Doom: Plutonia Experiment" }, { "tnt.wad", pack_tnt, commercial, "Final Doom: TNT: Evilution" }, { "doom.wad", doom, retail, "Doom" }, { "doom1.wad", doom, shareware, "Doom Shareware" }, { "chex.wad", pack_chex, shareware, "Chex Quest" }, { "hacx.wad", pack_hacx, commercial, "Hacx" }, { "freedm.wad", doom2, commercial, "FreeDM" }, { "freedoom2.wad", doom2, commercial, "Freedoom: Phase 2" }, { "freedoom1.wad", doom, retail, "Freedoom: Phase 1" }, { "heretic.wad", heretic, retail, "Heretic" }, { "heretic1.wad", heretic, shareware, "Heretic Shareware" }, { "hexen.wad", hexen, commercial, "Hexen" }, { "strife1.wad", strife, commercial, "Strife" }, };

[chronic8000]

Legend! Just got Doom 2 running on Pixel Watch Emulator. I gonna upload to watch now and see how it works. I'll drop a YouTube video link once it's live! Thanks again!

[chronic8000]

Done a video of it running in Android Studio Wear OS 3.0 emulator. Sadly crashes on real hardware right now.

https://youtu.be/388e4lz8OtE

[deqart]

If you can post the lldb backtrace of the crash i would love to help.

[chronic8000]

Apologies for the late reply but DOOM runs on a watch although it is pretty much unplayable. All the controls are in the wrong places but it works on Pixel Watch! Watch on YouTube

The error I caught via logcat in the emulator is below. I am not very good at development just trying to learn so not sure where to find the lldb backtrace I was just using logcat.

Signal Catcher"]: reacting to signal 3

Which is apparently the process getting killed by Android likely due to lack of system resources but it doesn't produce this error every time. Re-iterating the fact it probably is getting killed due to lack of RAM or CPU at time of launch.

2023-07-27 00:22:58.603 6036-6044 om.deckart.doo com.deckart.doom I Thread[3,tid=6044,WaitingInMainSignalCatcherLoop,Thread*=0xecf19a00,peer=0x12cc4158,"Signal Catcher"]: reacting to signal 3
2023-07-27 00:22:58.603 6036-6044 om.deckart.doo com.deckart.doom I
2023-07-27 00:22:59.194 6036-6044 om.deckart.doo com.deckart.doom I Wrote stack traces to tombstoned
2023-07-27 00:23:07.778 6036-6036 threaded_app com.deckart.doom V Pause: 0xe19be100
---------------------------- PROCESS ENDED (6036) for package com.deckart.doom ----------------------------

[deqart]

To get the lldb backtrace you have to launch the app in debug mode. Logcat is great for understanding errors in java and kotlin code but for native c and c++ code native debugging via lldb is required. If you think the issue is caused by lack of resources i recommend changing DEFAULT_RAM and MIN_RAM defines in the i_system.c file.

[chronic8000]

It actually runs now and I haven't had it crash. Just need to work out how to move the on screen joysticks so it can actually be somewhat playable. Did you ever try with getting sound working. Be sweet to hear that E1M1 Doom 2 Entryway music. I see you only tested with Shareware wads did you but seems to work fine with retail DOOM and DOOM2 wads. Yet to try it with any modded wad files. Great work though and thanks for your help I am such a noob when it comes to programing.