Hello all.
Recently rooted and installed Vanir Rom on my 2013 N7. Prior to rooting Modern Combat 4 ran great, no problems. Now it will load and all will seem fine until the gameplay actually starts. All the heads up display info is there but the screen is just black. No cut scenes, nothing at all. I thought it was because I changed LCD density but have returned it to stock and still the problem persists. I've redownloaded the game and the same problem......
Any ideas?
Related
http://forum.xda-developers.com/showthread.php?t=742081
so happy
direct link: http://www.kwaak3arena.com/
Thanks, i was playing normal kwaak3 without on screen controller using volume buttons to go straight and back that sucked ;D
Sent from my GT-I9000 using XDA App
i finally got it installed properly in my phone, the speed is FREAKING AMAZING!!!!!!!!!
it puts any computer to shame
1.It works a tad better on eclair than froyo.
2.When running kwaak close other apps for best performance.
3.Best setting - wide screen res, 16bit depth, everything else to max.
~60 fps.
It doesn't put any computer to shame
from present time that is
still..
i was comparing it to the CPU of the time when the game was released
Ahh... sorr to bump an old thread guys.. figure its better then starting a new one.
Ive been running kwaak3arena 0.2 for several weeks now without issue, but the other day it seemed to stop working properly. main issues are that the brightness of the textures seems to have increased, the controlls have been muddled up, and the application crashes sometimes in some levels. This all came on unexpectedly after running flawlessly for ~2 months!. The only thing i can think of is that after i used the application with it working perfectly, i had downloaded the XE.com app, and after that it starts screwing up. Im also noticing, though not sure if its just me, that other areas of the phone are running very slightly more laggier / choppier then they were before.. i think.
I have tried uninstalling and reinstalling kwaak3arena, as well as getting rid of the xe.com application, but still no fix.
Phone is basically standard running voodoo lagfix.
Anyone else having similar issues?
I also noticed that the developer has released a new version which he's charging for
edit: Also, for symptoms, ive noticed ive been renamed "unnamedplayer," from GalaxyS
I have been experiencing some extreme wake-up lag on my R800a running DoomKernel v11 after installing a theme. It's so bad that it takes a solid 3 seconds for the screen to light up and during those seconds, the music is choppy as hell. I wouldn't mind it if it wasn't ruining the music. I first installed this custom ROM http://forum.xda-developers.com/showthread.php?t=1321314 and I noticed the intense lag right away. I thought it was just a glitch in the ROM so I just went back to stock. Then I tried installing this theme http://forum.xda-developers.com/showthread.php?t=1464375 and I got the same problem again. I completely wiped all the user data and started from scratch twice and am still faced with the same problem. The phone runs perfectly when it's awake. There's absolutely no lag anywhere, just on the initial wake-up. I even used an app called Soft Locker so it wouldn't go into deep sleep and set my minimum CPU clock to 1.5ghz and I still got the lag. The theme is way too sexy to just give up so I was just wondering if anyone has encountered this before.
So I tried using the stock kernel with the theme and the wake up lag went away so I guess the DooMKernel was causing the problem, which is unfortunate because I love that kernel. Has anyone else had a similar problem while using the DooMKernel?
Actually SE.Tweaked isn't working well right now.
I have R800a as well, I installed it, and it wouldn't even boot. R800i users seem to have no problems, but R800a and at users seem to be having problems.
As well all ICS roms are in BETA. So things not working properly with all phones/kernels should be expected.
So it's not doomkernel, it's the ROM.
After one month it had been away, a bunch of days ago I got my Galaxy Nexus back from the tech support (motherboard failure).
I proceeded to unroot it again and I installed ParanoidAndroid (6th March beta) since I was using that rom before it broke and flashed trinity on top of it. I noticed a peculiar behavior when trying to playback youtube videos (both in the app and in the browser): sometimes the request would just hang there and if I did anything like pressing the back button, the app would be found unresponsive by the operating system and the "youtube isn't responding. Ok|wait" message would appear. I just got back my Galaxy Nexus from mI just got back my Galaxy Nexus from mI just got back my Galaxy Nexus from m If in a boot session that happens, I get the same thing happening on several apps like twitch.tv and clock. I discovered that the clock app wasn't working properly last morning, when the alarm didn't go off and I kind of overslept to uni, it wasn't nice .
I tried flashing other roms and kernels combinations as well as factory resetting, fixing permissions, installing busybox, re-installing youtube, clearing caches of various apps.
Has anyone ever experienced something similar? Thank you.
up
I am running the latest Cynogenmod Nightly on my Galaxy Tab Pro 8.4 Everything is running great except for the game 'The Walking Dead.' As soon as this game starts, there is a horrible buzzing sound from the speakers, which continues the whole time the game is running (which otherwise appears to run normally).
Unfortunately, I never installed this game on this tablet before installing Cynogenmod, so I am not sure if this is a problem with the tablet, or with Cynogenmod, and was wondering if anyone else had experienced the same issue...
stone1269 said:
I am running the latest Cynogenmod Nightly on my Galaxy Tab Pro 8.4 Everything is running great except for the game 'The Walking Dead.' As soon as this game starts, there is a horrible buzzing sound from the speakers, which continues the whole time the game is running (which otherwise appears to run normally).
Unfortunately, I never installed this game on this tablet before installing Cynogenmod, so I am not sure if this is a problem with the tablet, or with Cynogenmod, and was wondering if anyone else had experienced the same issue...
Click to expand...
Click to collapse
As much as I enjoy CM you give up so much to run it (split screen for instance).
Yes I have this problem have you figured out how to fix
I had the same problem. I had Cynogenmod installed and was enjoying it (despite the lack of multiwindow) until I tried to play Season 2 of The Walking Dead. Instead of the normal sounds all I got was buzzzzzzzzzzzz. I tried reinstalling a few times and even a new nightly of CM but nothing helped. Finally I just decided to go with another ROM altogether. I went with CleanRom for the 8.4 and haven't had any problems with the game at all.
One note, though since this is a gaming topic, when I was using CM, the game Deus Ex worked fine, now on CleanRom it doesn't. But since it still works on my Note 2 I'm going to continue running CleanRom on my 8.4.
Hi. I tried posting on another site but no one seemed to be experiencing the same issue. I recently switched from SPMC to 13.2. After just few days navigation became very slow but video played fine. It would keep getting slower despite clearing cache then it just wouldn't start--immediate crash.
I switched back to SPMC and still menu was slow, video perfect. But today it just wouldn't launch. After several reboots and clear cache from fire os menu I got it to work. It played a video with no problems, however, I know based on how navigation sticks its going to crash again. Problem is I can't force a crash. It only crashes on startup, making debugging impossible I think.
I'm basically using just genesis and a few program add-ons all from add-on installer. I've used aeon nox and ccm skins. They both do the same thing.
I'm thinking fresh start but there's little reason to think I won't end up back here.
The only other relevant piece of info (maybe) is I recently installed clockwork mod and installed rbox latest firmware. Then I updated the remote from there. It may have nothing to do with anything but without a log I don't know how else to explain it. Anyone else having similar problems? Any and all advice is welcomed. Thanks.