Android 14/15 fix launch. ????????? #1944
Comments
|
Post logcat.
|
|
12-31 17:42:19.64725186 25186 1 HwForceDarkManager: isSystemlnDarkMode isResUiModeYes: false, isDarkMode: false |
|
It looks too short. You can use pastebin alike service to post full log there. |
|
Keep in mind, you have to start writing logcat before you started the application, then run it, reproduce crash, stop logcat and post it here. |
|
Xash3D-FWGS app will launch fine when HL resources weren't installed. Created logcat with Info: |
|
I'm getting the same issue on S24 Ultra with OS Android 14, using the Xash3d fwgs Master Stable, it recognises the games (hl,of,bs) and the new Brutal Mod, but loads up the main menu then immediately crashes the app. |
|
I can't even install the app on my Android 14 device, says it's not compatible. Also, that's with old engine, which I have way better compatibility with and less bugs using. With new engine, the game exits to the home screen repeatedly if I get notifications, if I press quit, change game, or rotate my screen. I have a hard time keeping new engine open is what I'm trying to say, it doesn't crash at all because as soon as I switch back to it via recent apps, the game runs perfectly fine. |
|
It seems, i need test legacy port on android 15 (sure, it should work, but i only tested on 14)
|
|
The new engine works under Android 15 without any issues. Old engine won't work in most new phones, since the engine is 32-bit only and the latest phones will only run 64-bit code. It is, what it is... |
|
Check this video!!!! |
|
And? I can post here a video from my phone with Android 15, where the Half-Life inside Xash3D-FWGS runs just fine... |
|
Salom Alibek Sizga bitta iltimos CS 1.6 client ishlayapti Lekin 16 versiyadan oʻtmayapti iltimos yordam qiling |
|
@BekzodUzb All good, but we don't understand Turkish and even machine translate doesn't help. |
|
Hello, please release an updated version of CS 1.6 Client with Xash3D support. It would be amazing to have such a version on mobile devices. Thank you in advance! |
|
"Publish the updated version on the Play Store because there are many subscribers who are gaming enthusiasts." |
|
No, there won't be a Google Play release. I'm completely against wasting
time on this.
Also, this is completely unrelated to this issue. Please refrain from off
topic discussions.
|
|
"Will the CS 1.6 client disappear? Version 16 is almost not working." |
|
Just updated to the latest Xash3d Stable build and it's still crashing, tried a clean install as well and no luck, click play and as soon as the main menu loads it crashes to homescreen, phone S24Ultra ARM CPU Android14. |
|
@BekzodUzb cs16client currently maintained by Velaron: |
|
Thanks you |
Exactly! |
|
Engine.log : ================================================================================
|
|
Well this is certainly not tied to Android version, as it works on my Samsung on both 14 and 15. Also doesn't even looke like a crash, without logcat discussion is probably useless. |
|
на последней версии у меня снова крашит игру |
Yeah, something seems to be emitting SDL_QUIT event, judging by But I can't reproduce this on my own device. My assumption is that something sends either SIGTERM or SIGINT, which SDL2 handle for us by default and convert it to SDL_QUIT event. But even so, how should I know why exactly it does this?
Вот тоже SDL_QUIT. Попробуй записать logcat и выложить сюда. Учти что logcat нужен только со старта запуска приложения и до его закрытия. Всё что до и всё что после этого зачастую бесполезно. |
|
Just installed the newest version of Xash3d and here's the engine log for each folder, the Com/Su folder and the separate game folder, just a reminder, I'm using an S24 Ultra, hopefully it's enough to help: ================================================================================
|
|
That just means wherever you pirated your stuff it was ran on a Vita... Makes me wonder if these issues are tied to a specific copy somewhere on the internet |
|
These crashes aren't copy specific, I have a legitimate copy of HL1 bought through Steam and these issues still happen, even with the pre_aniversary branch of the game |
|
Brutal Half-Life has the same log, but Brutal Half-Life does piggyback off of regular Half-Life for some core files |
It won't work on Android anyway |
It's useless to run it on Android. |
|
I transferred my steam files primarily, that's why it showing as vita maked no sense, however for testing purposes I fully deleted everything and uninstalled Xash3D, I illegally downloaded the Sierra Original PC game data files and still ended up with the same crash issue. Shame my old phone died, Xash3D and the games worked perfectly on my old phone. Sometimes newer is not better, lol. ================================================================================
|
|
You have to legally obtain the game files, we do not support piracy here. Not only that, it's better to use Steam version of the game. |
|
I was using my legal steam version before, but switched to test it. Got one of the games working, Brutal Half-Life, didn't really like it though, so deleted it. Everything else still crashes though. |
|
This is our bug somewher but I don't know how to reproduce this bug. It just works perfectly for me. |
As for old engine, there's a version of it that I've found to work better than New Engine and Old Engine (0.19.x versions) and it's 0.20.1, it appears to look like New Engine (the icon at least) but still operates the exact same as Old Engine, and will let you place launcher widgets for each game on your home screen. Meant to reply here with that info but I also don't know where to legitimately find it on here (specifically FWGS repositories). I just got an update for android 15 so I'll try and respond here with info on whether or not it works. 0.19.2 Old Engine won't work anyways due to tighter storage permissions found in android 13+ and even if you use an app like Install With Options through Shizuku (if you're on a non-rooted device) it'll still be unable to write and read from your storage. Opposing Force is also incompatible by the way, the game crashes during the intro scene when the helicopter is supposed to explode, figured I should go ahead and mention that too. There's also far fewer graphical glitches (at least on my device) except for loading transitions, solid black boxes appear behind the touch controls when visible and behind the loading prompt. Transparent objects (microwave glass, hev suit glass sliders, door glass panels, etc. etc.) appear opaque and some don't and work fine. Also, if you use gesture navigation, if you have the option in your phone settings, make sure you have the navigation bar set to be hidden so you can be able to see the HUD. If you don't, the app doesn't automatically hide it for whatever reason and unfortunately covers it up entirely. |
|
For now I have completely wiped Xash3d and all Half-Life files off my phone. I will try another clean install later and re transfer my Steam game files across again. Opforce on my old phone ran fine by skipping the intro scene via the command console, the gamepad was ok on my old phone though. But yes there is a crash bug in the intro scene, just as it changes from first person view to the xen ship shooting down the osprey. Android 15 is not yet available where I am, so on Android 14. Edit: I just remembered my old phone had Java for Android installed. My new phone doesn't. Looking further into Xash3D builds, it does seem to run some Java related coding. Either way, will keep experimenting hopefully we will resolve this issue . |
Don't know if someone else has said it already, or if I've already said it before, but when it crashes after loading into a game, go to your recent apps and switch back to the last app. (Should be Xash3D FWGS, if you don't open another app after it crashes.) if you use gesture navigation on your phone, just swipe along the navigation bar for the previous app switch gesture to quickly go back to it. If it crashes again, just keep doing so until it loads the menu for the game. If you use standard 3 button navigation, just press the recents button twice to do the same thing as the gesture navigation. It's a bit of a jank fix, but New Engine is extremely unstable for one reason or another on android 14 / 15. That's clearly already known though. I see OpFor just didn't work to begin with during the intro scene, it isn't an issue specific to any android version. |
|
@antitheus185 to have opfor, it needs it's game logic rebuilt specifically for an Android targetting CPU architecture of your phone. There is no known rebuilds of opfor for new engine, mostly because everything Android related is not yet completed. |
|
Right, I logged in on my PC, I re transferred my HL, OF and BS files, I also transferred HLSource because why not, did a clean install of Xash3d, gave it full access permissions, and still crashed as soon as the main menu loaded. So Android 14 could be a possible issue, but it feels more like it's the ARM Cortex cpu that may just not be fully supported by the engine. However here is the log for you to view: ================================================================================
|
|
I know that the S24 Ultra uses a Snapdragon 8 Gen 3 when the S24 and the S24+ uses a Samsung Exynos 2400, maybe it's just the CPU interfering with Xash ? |
|
S24 Ultra in the United States uses Snapdragon 8th gen. S24 Ultra in the United Kingdom uses ARM64 Cortex 8core CPU. I'm not sure why but Samsung felt the United Kingdom had to use a different CPU to the rest of the world, they did the same thing when the S22 Ultra was released as well. CPU-Z for android, S24 Ultra UK: My old Razor gaming phone that died a few months ago used to have a Snapdragon 5th Gen 8core i think it was, lol. |
|
This is highly unlikely caused by CPU.
As I said above, it's our bug, but I don't know how to reproduce it. So far
it only happens on Samsung, OnePlus and few other devices, but doesn't
happen on my Sony device. The only difference is vendor's modifications to
Android, I think, which is the main cause of headaches in Android
development.
|
|
If it's means anything i got my phone from Three Mobile in the UK. Also the S24Ultra, same with S22Ultra, make it hard to view and alter the Android/data folders, modification of Android/data files is blocked for unofficial apps, Xash3d is a third party install (not through GoogleStore) and may limit storage access permissions. Funny though another third party Engine called Zeta Touch has no trouble, but it does not run through the Android/data folders, but it uses the Android/obb folder along with main user storage area instead which are not prohibited areas of storage. When we install HL,OF,BS, through Xash3d it allows us to give temporary access to prohibited areas of the storage, it may be that the permissions to that area of storage are being removed soon after. I couldn't say for certain without testing it further. It likely a Manufacturer specific Android issue, from what you've indicated in relation to Vendor. It'll get there eventually. |
|
How obb might be helpful? Does it allow access folders tree, not just 1-2 archives?
In legacy port branch i suggested to use internal files directory. Yes, it does not give direct files access to user, but at least it does not use slow and glitchy fuse wrappers. Files still may be accessed with storage access framwwork and internal webserver. And uploading files from pc to webserver is even faster than copying from user storage, because android storage performance sucks
Another idea was making separate apk for files storage, but this will require shareduid since android 11. Google breaks any ability to share folders between apps with different signature.
Anyway best way to store files is custom /data/ subfolder on rooted device with selinux permissive or patched sepolicy. In this case you would not lose files on app reinstall. Unrooted android is no an operating system at all, it's just cloud services client (for comparsion, DOS is operating system)
|
|
Because we don't care about Google Play anymore, we can just request
MANAGE_EXTERNAL_FILES permission and do stuff the old way..
|
|
fuse was disabled for MLS apps in 11, but enalbed again in some android 12 security update. But at least, engine will be able to access user storage.
MLS may be also useful in shareduid storage helper, but i do not want to use shareduid because it's not user friendly, android just says it cannot install app for now reason on signature mismatch
|
|
Jesse what the fuck are you talking about
|
|
Same issue, instant crash on Samsung Galaxy S24 Ultra. Vendor is Verizon. On very rare occasions if im quick enough i can click through the main menu, and start the game, and it wont crash...? It loads the game for just a few minutes. Otherwise nothing. |
When starting Android 14 or 15 with the latest version installed, the home screen loads for 1-2 seconds, then crashes after another 1-2 seconds.
The text was updated successfully, but these errors were encountered: