I just installed this game and I am really disappointed in the performance on my Nexus. I'm running the latest CM rom with 33.1 kernel and even when overclocked to 1133 the game gets unplayable in most spots...
Anyone has any thoughts on that ? I search around and Droid users seem to get better framerates. Is the Nexus GPU so bad after all ???
Performance
I see what you are saying, but I don't find it excruciatingly laggy at all. Its pretty decent, but I do see the performance limits of the Nexus gpu. I also see the need for performance upgrades to the game itself. Other games go much smoother then this one (both are smooth though, just others are much smoother). Raging Thunder 1 and 2 are pretty beast on the nexus.
I don't find it a big problem at all. If anything, devs need to adapt for the nexus market
This is like the best to come to nexus I have a lot of the cars unlocked and get to play my music while I play. =) I dont see much lag on enoms with his oc/uv works great next update should be a bit faster.
Before I used Ivan's JIT this game was pretty choppy with long loading times, even with pershoot's ocuv. Now with Ivan's JIT and ocuv kernel, this game is super smooth with very fast loading times. If it can be optimized to run smoothly without JIT it would be even better.
I am also using CM's latest ROM and am getting pretty bad lag at times, I am thinking about going to Modaco's once the new version comes out. Is performance for this game really that different between ROM's?
Kutthoat5150 said:
I am also using CM's latest ROM and am getting pretty bad lag at times, I am thinking about going to Modaco's once the new version comes out. Is performance for this game really that different between ROM's?
Click to expand...
Click to collapse
I don't think it's a ROM issue as much as it is a developer issue.
Using enom's rom and it plays brilliantly on my N1
Gameloft has admitted it needs to be tweaked for the N1. It's not optimized but still looks great. My wife has an iPhone and it looks fantastic on it.
I wish developers would make graphically pretty games for Android that aren't racing games. Seriously, how many do we really need?
denimjunkie82 said:
Before I used Ivan's JIT this game was pretty choppy with long loading times, even with pershoot's ocuv. Now with Ivan's JIT and ocuv kernel, this game is super smooth with very fast loading times. If it can be optimized to run smoothly without JIT it would be even better.
Click to expand...
Click to collapse
Well I didn't buy the game to confirm that, but if it really runs faster with JIT it means it's written in java and it's going to run like crap anyway... In that case they don't need to optimise it, they need to rewrite it as a native app.
It is smooth but not extremely, yeah it stil need to tweak, as I notice it actually play extremely smooth in Motorola Droid (Milestone).
It still playable with decent speed just slightly lagging when your car bang, fly over, then you notice the lagging issue.
BlueScreenJunky said:
Well I didn't buy the game to confirm that, but if it really runs faster with JIT it means it's written in java and it's going to run like crap anyway... In that case they don't need to optimise it, they need to rewrite it as a native app.
Click to expand...
Click to collapse
All "native apps" are run from within a java shell. Basically, each frame the java code has to call into the native code. The alternative would be essentially writing OpenGL from the ground up in the native code, although even then it'd still need to be called from an active java app and all controls, sound, etc, would need to be handled in java. There's simply no other way to write native apps in Android.
Yes, sorry, that's what I meant by "native app" (that's how kwaak3 works for example). I can be wrong but I think if only input and audio are handled by java, the use of a different virtual machine using JIT can't make such a difference...
BlueScreenJunky said:
Well I didn't buy the game to confirm that, but if it really runs faster with JIT it means it's written in java and it's going to run like crap anyway... In that case they don't need to optimise it, they need to rewrite it as a native app.
Click to expand...
Click to collapse
I played the game while running JIT and it made zero difference. It was still laggy at times. No ROM will make a difference as it's not the software here that is the limiting factor but the GPU. The snapdragon has a great CPU but unfortunately a pretty poor GPU compared with other phones say the Droid. The Droid was much smoother and even smoother was the iPhone.
Gameloft needs to optimize this game keeping in mind the hardware specs for each device. Just my two cents.
Using Enomther rom, no lag whatsoever, plus you can overclock over 1 ghz...
Imperial.mack said:
Using Enomther rom, no lag whatsoever, plus you can overclock over 1 ghz...
Click to expand...
Click to collapse
Interesting, with Enom's I always get lag. Good to hear that it works well for you.
Many people will probably have different views on what lag is, i get a lag when playing it and so will everyone else, some people may not notice it as much as others and in some cases it may occur less due to there actual set up but the ROM should not make a difference as it was not developed with the nexus one in mind, hence why it doesn't utilize the N1 as well as it utilizes the Moto
lolittle said:
Many people will probably have different views on what lag is, i get a lag when playing it and so will everyone else, some people may not notice it as much as others and in some cases it may occur less due to there actual set up but the ROM should not make a difference as it was not developed with the nexus one in mind, hence why it doesn't utilize the N1 as well as it utilizes the Moto
Click to expand...
Click to collapse
Actually this game was developed for the iPhone it lags pretty bad on the Moto Droid as well.
I guess there is no game till now that has used N1's potential fully. Whats stopping game development on Android ??
faraz1992 said:
I guess there is no game till now that has used N1's potential fully. Whats stopping game development on Android ??
Click to expand...
Click to collapse
The market. Not the "Android Market", but the market for heavily investing in optimizing a game. Every Android handset is different - different plug-ins, different hardware, different software, etc. If you want to design a great game that performs brilliantly for 2 dollars, you need to sell a LOT of copies of it. Hundreds of thousands or more. Well, only the Droid has even sold that many handsets, and you'll never get 20%-50% penetration into a market with just one application.
Sure, Asphalt will run on nearly anything, BUT, it isn't going to run as well as it does on the iPhone despite the inferior hardware on that device, simply because optimizing it for one platform in Android (except MAYBE the Droid) isn't economically efficient.
The iPhone's biggest advantage (though that is looking to be short-lived now...) is the absolute lack of platform fragmentation. Every single iPhone or iPod Touch can run 99.5% of the available applications, and run them well. Almost all of them are running exactly the same software (obviously, there are some kernel differences and baseband differences, but the userspace kit is almost exactly the same). And there are 80 million of them. A developer just needs to hope for 1 percent penetration to make a killing on even a cheap application.
Until Android can get rid of excessive fragmentation (to at least a reasonable extent), it will suffer in the game world compared to Apple's kit. If Android can get down to just one version on effectively everything, with one set of APIs to address graphics at high speed, it'll be too expensive to make something perform as well - unless you want to pay $30 for an Android game (and I sure won't do that...).
I saw in a google + thread that android, since 1.5 version was software rendered, would our little GPU be able to render some launchers? If yes, i'm looking for a method to enable it, I think our phones would be a lot smoother and less laggy (I overclocked a little time ago but i didn't saw any difference)
JPQ Firmware rooted firmware
VOODOO
G3MOD Kernel NON-OC
MIUI Theme
most people say our little g3 doesnt have a GPU :'(
well youll have to edit the elg.cfg to enable HW redering though
Thanks, Well I'm going to give it a try, but our little SG3 has a smll FIMG 3DSE GPU, maybe Tom3q OpenFIMG will help us to have better smoothness then
GPU Rendering is one of the reason of the importance to get Android 4.0 working on our G3, because GPU is used for smooth animation and very smooth luncher .
ICS is a mix of gingerbread and Honeycomb and it has fully hardware acceleration unlike honeycomb which has partially.
I do wonder why navigating in ICS with a Galaxy Nexus isn't as fluid and smooth as let's say a Samsung Galaxy tab?
Here's an example on Samsung Galaxy Tab 7.0
http://www.youtube.com/watch?v=ftljZ9yGsiE
And if you have used a Galaxy Nexus or seen video with it, you can clearly see that when opening the app drawer and navigating in the OS isn't as smooth as Honeycomb.
Could anyone clear this out for me?
I noticed that too, even apps running on GB is much faster than ICS . There are still many performance tuning work to do I believe.
BTW: by default , GPU acceleration in ICS is disabled , right ?
coolsixty said:
I noticed that too, even apps running on GB is much faster than ICS . There are still many performance tuning work to do I believe.
BTW: by default , GPU acceleration in ICS is disabled , right ?
Click to expand...
Click to collapse
I really don't know, maybe someone else can anwear this?
read this about hw accel first
https://plus.google.com/105051985738280261832/posts/2FXDCz8x93s
I have tried a couple of AOSP-like ICS ROMs (HyperNonSense, Virtuous Inquisition 4.0) and I am not very happy with the performance. Pressing the back button often causes a small stutter or lag, and browsing (although fast) has lag on occasion or stutters.
It is not that the experience is 'bad', but it is not as fluid and fast as one would expect it to be from a dual-core phone with the kind of specs included within.
To give you a better idea, my Samsung Galaxy S (i9000), running the BlueLighting ROM (ICS 4.0.3) with a 'mild' OC to 1.2 GhZ runs buttery smooth, and beats my Sensation XE (ICS 4.0.3, tested at 1.2 GhZ 'underclock, 1.5 Ghz 'stock' and 1.7 Ghz 'OC') every time and in every situation: Browsing pictures, using stock browser, browsing applications, contacts, pressing the back button etc.
Why does a phone with a single-core CPU, clocked lower, and what seems to be inferior specs outperform a phone that should be doing much better?
I love AOSP experience, and I would ideally avoid any Sense-ROMs (although Sense-lite are ok, I suppose).
Can anyone tell me what their mileage is, with which ICS ROM, and whether you think there is a ROM I should try?
Thanks!
I also had the Virtous Inquisition Rom on my Sensation and i have to say it works very well.
Maybe you have to try another aosp rom like the Cyanogen mod9 from ultimate sensation,it also works very good for me
Thanks I will give it a try and let you know!
Also, can anyone suggest a good ICS kernel? I have had trouble finding a stable kernel. Some can work fine at speeds above 1.6GhZ, but some will not even boot -- perhaps they are not for ICS. I will have to look around. I am surprised there is (no offence!) little variety and option on offer in regards to kernels -- particularly for those interested in the more exotic CPU profiles.
I have also used both Hyper NonSense (1.5 currently, no longer being developed but is stable) and early Virtuous Inquisition releases. For me, both were quite fast - Hyper NonSense more so, but I haven't used a recent release of VI. In both cases, I stuck with the stock kernel distributed with the ROM.
FWIW, Hyper NonSense has also been giving me EXCELLENT battery life. It's a shame to see development stop on it.
I own my moto g from more than 3 years. The official update that we got for this device till lollipop, the device used to run fine for the hardware it had but compared to how it performs these days on these custom roms, especially the nougat ones, the performance has gone down so bad that it's pretty much struggling to perform even basic functions without the stutters or lags.
Now all that is understandable that it's an over 3 year old mid ranger but my questions are, 1) does everyone experience the same with their moto g, 2) what exactly has reduced the device's performance over time because it used to run fine on older android versions. So is it that the new android updates and apps etc aren't optimized for this old hardware or did the performance of these hardware components like the SoC just got reduced over time?
I'd be glad to read everyone's opinions below.
Personally, I don't experience any lag, decrease in performance, not even poor battery life running nougat (latest commotio), zero byte r4 kernel..
Could you be 'more specific' regarding your setup?
Ænimal said:
Personally, I don't experience any lag, decrease in performance, not even poor battery life running nougat (latest commotio), zero byte r4 kernel..
Could you be 'more specific' regarding your setup?
Click to expand...
Click to collapse
Since when do you own the device?
hsn97 said:
Since when do you own the device?
Click to expand...
Click to collapse
All the way from jelly bean