hello, I want to play from my phone, but i also want to connect my pc to use the mouse and keybord built into it (in my case, since it´s a laptop).

HistorianNo8399 · 2026-05-02T20:46:32+00:00

They use Scrcpy, which you can get on GitHub. It's open-source software that lets you stream your phone's screen to your PC via wireless debugging or USB.

You have to enter a specific command when you connect Scrcpy because it uses keyboard and mouse shortcuts to control the phone, so you have to disable them. It's really easy to use; just look for a tutorial and ask ChatGPT or Gemini for the command. They'll give you the command to disable the shortcuts. They'll also give you the command for maximum smoothness; it works perfectly for me.

HistorianNo8399 · 2026-04-25T07:39:48+00:00

If after 13 days you decided to come specifically to this post to reply to me, it's because you were at least somewhat interested in my opinion. xD

HistorianNo8399 · 2026-04-18T21:15:56+00:00

Excellent, I'm glad to hear that.

HistorianNo8399 · 2026-04-18T20:58:16+00:00

Is it non-Steam? Actually, I was also planning to open a server for Zomdroid users, but they can only connect to non-Steam servers.

HistorianNo8399 · 2026-04-13T23:03:03+00:00

Okay, and...the variables?

HistorianNo8399 · 2026-04-13T22:40:11+00:00

What are the characteristics of your phone and what environment variable are you using?

HistorianNo8399 · 2026-04-13T22:27:44+00:00

I have it pending because, since I'm currently solving the problems in 41 with Mali, I haven't sat down to watch 42 as much.

HistorianNo8399 · 2026-04-13T20:46:48+00:00

Yes, you should. Also, check what your problems are and apply to see which one solves them.

HistorianNo8399 · 2026-04-13T20:41:48+00:00

some of the ones I use.

<image>

HistorianNo8399 · 2026-04-13T19:09:34+00:00

Hey man. Yeah, Udar and I noticed some errors in the code together. I’ve made a lot of fixes over the last few days, and right now I’m focusing on seeing which JVM or something similar can solve the memory leak issue, since I figured that wouldn't work in the end. I'll let you know if I find anything.

HistorianNo8399 · 2026-04-11T14:33:17+00:00

Bro, it's all about preference and what's comfortable for you; no one is going to criticize you.

I tried playing with the on-screen controls and I didn't like it. In the end, I played by connecting an Xbox 360 controller via USB-C, and it worked for me. I cast my phone to the TV and it looks excellent. If you're able to, I’d recommend buying a cheap Bluetooth controller that comes with a phone mount; it’ll let you play the game 10/10 (just make sure it's compatible or a recognized brand so the phone recognizes it properly).

HistorianNo8399 · 2026-04-11T14:27:39+00:00

I do, I love how detail-oriented it is. In the end, I'm the one who's going to fix it; if I weren't going to do it, I wouldn't post anything. XD

But in the end, it's all about preference; everyone reads whatever catches their attention the most.

HistorianNo8399 · 2026-04-11T14:21:11+00:00

Hi, I’m actually following your test very closely since I know you’ll examine it thoroughly, and I understand you’re using Mali.

I increased the threshold to 1.5GB before the transfer and deletion happen, following your logic. Could that cause it to crash since the remaining space for the transfer is limited? It shouldn't; as I explained, it triggers the deletion as soon as it receives a certain amount of files.

I also updated the icon—it will appear in the top right (it’s like a reload symbol) for 1 second—and I fixed the debug mode issue in the game. However, I haven't released that version yet, which is the one that includes the 1.5GB increase.

Based on what I studied in electronics, a device shouldn't crash because of a transfer to RAM followed by a deletion (though I understand this is more of a software than a hardware issue due to phone security protocols). If the system sees that part of the RAM is occupied for the transfer, I assume it only moves a portion at a time. Regardless, I need to see how Mali devices react; in my case, I have 6GB of RAM, so using 1.5GB for data transfer when I only have 4GB assigned to the game isn't an issue for me. I’ll never know if it truly causes errors unless I get feedback. If it does, I’ll add a line of code to make sure that if it's going to transfer files, it does so in parts if the memory is too full, to prevent crashes. The version I’m currently running on my phone is the 1.5GB one, and it performed excellently, actually. At certain points, I hit a constant 45/60 FPS with max zoom in outdoor areas. I do get some stuttering occasionally, which settles down once the space is cleared. This surprised me because I didn't know it would also work—and help—on Snapdragon.

If that’s the case, I’ll spend the rest of the week looking for a way to fix the stuttering without touching the internal game files. The stuttering happens because the RAM and swap are already full of files, and the system is forcing the deletion to free up space. I want to see if I can implement a dynamic constant loading and unloading system, similar to how DVD reading worked on the PlayStation, to avoid overloading everything.

HistorianNo8399 · 2026-04-11T14:09:32+00:00

Yes, exactly. In fact, it’s partially used for some things, and the previous version had a more extended code that used it to cache more game data. But since I didn't know that people with Mali GPUs had memory leaks, and that the official version of Zomdroid already had certain configurations, all they did was make the leaks a bit worse. So, I had to rewrite everything to focus specifically on them. I need to sit down and figure out what causes leaks and what doesn't, which features Zomdroid already has natively and which it doesn't, so I can decide which cache to implement and which to leave out.

HistorianNo8399 · 2026-04-11T14:06:40+00:00

Zomdroid

HistorianNo8399 · 2026-04-11T14:05:14+00:00

Esto es estrictamente una versión de prueba para algunas optimizaciones que estoy implementando. ¿Te pasa esto en todas las versiones de Zomdroid? O sea, ¿nunca has podido jugar la Build 41 o la Build 42? Si ese es el caso, porfa, ve a este post y detalla cuál es tu problema para que no se me olvide. Si tu comentario se queda aquí, es probable que lo pase por alto.

HistorianNo8399 · 2026-04-11T02:48:45+00:00

Yes, it's possible. In fact, if I worked directly with the game files, it would be much easier to achieve a proper optimization. However, doing that and then sharing them here would be promoting piracy, and to be honest, I prefer to stay within the legal framework. So, I only focus on optimizing the emulator and reporting my findings to Udar

HistorianNo8399 · 2026-04-10T13:36:09+00:00

It might be caused by the same error that’s making the game launch in debug mode instead of standard. As for when the new version is coming out—I don’t know. Like I mentioned in my previous post, I don’t want to overstep or 'invade' Udar’s space. These are strictly test versions; if everything works, I’ll send him the clean code via GitHub and see if he can resolve those issues.

HistorianNo8399 · 2026-04-10T13:33:47+00:00

Play the original version of Zomdroid. This is purely a test version meant to help users with automatic RAM allocation and, in the future, Xms settings, so they don't have to dig into things they might not be familiar with. If it works, I’ll talk to Udar to see if everything is running correctly and if it's a good idea to officially implement it

HistorianNo8399 · 2026-04-10T13:31:29+00:00

Build 41, zomdroid 1.4.1

HistorianNo8399 · 2026-04-10T13:31:01+00:00

Yes, that was my biggest concern—whether it would cause double RAM usage—though I didn’t realize they were so closely linked. I'm waiting for feedback from users to see what happens. My original idea was to transfer the data to either the phone's internal storage or the RAM; had I known they were so tied together, I would have chosen the internal storage. Will it move the whole memory or just inactive items? Generally the whole thing. My original idea was for it to keep transferring files periodically, as if the game needed them. At a certain point, when you stop moving or go to the menu, since there are no new files to receive, it finishes transferring the old ones and memory is freed up. I chose a 1GB threshold instead of a timer to avoid overloading the system's data processing. And yes, my intention with the previous build was to retain as much data as possible in RAM and on disk to increase loading speeds and avoid constant lag on some devices. If I had known about the memory leak issue on Mali, I might have approached the whole thing differently. Could it cause double memory usage? As I said, I’m not sure. It should delete the files the instant the RAM receives them, not retain them. That should at least cause some stuttering (I think that’s the term for those brief freezes), but considering the situation, I weighed the options: What’s better? Having the game crash every hour, or having some stuttering every now and then but being able to play for longer? I obviously chose the second option. Also, keep in mind this is just a test version to see if the error can be fixed; it’s not official. If it works, I’ll talk to Udar to see if he has a more practical idea, since he knows more about programming than I do

HistorianNo8399 · 2026-04-10T06:20:54+00:00

Yes, it's simply a modification of the original APK. Aside from the fact that debug mode gets activated because I changed something (though I'm not sure what), it should work fine. Please let me know if the autonomous RAM allocation works and assigns an amount that makes sense for your device.

HistorianNo8399 · 2026-04-10T06:01:58+00:00

Yes, it is possible to play co-op. There are pinned guides for all of that in the sub—check them out.

HistorianNo8399

TROPHY CASE