Anything better than JPC froyo?
Sliced Bread?
No. Its the best IMO and I've tried 3 2.2 firmwares. With any luck Samsung will release the official one this month.
I hope so.
Jm7 is way better
Sent from my GT-I9000 using Tapatalk
my question is how come on the current froyo roms the linpack scores don't jump much... on the desire and nexus get somewhere in the region of 40 mflops...
Is it just cause they haven't properly optimised jit on the SGS yet?
Toast?
Sent from my GT-I9000 using XDA App
Sorry the HK 2.2 is by far better than JPC...
Ibanez33 said:
my question is how come on the current froyo roms the linpack scores don't jump much... on the desire and nexus get somewhere in the region of 40 mflops...
Is it just cause they haven't properly optimised jit on the SGS yet?
Click to expand...
Click to collapse
In another thread i pointed out the same thing as you are, because i read somewhere else that HTC had to do very little job to optimize JIT for Snapdragon, having google done that with AOSP.
They replied to me saying that first Froyo FWs for Desire and N1 reached ~ the same jump from Eclair Build: 8 to 14 Mflops. Only later, with progressively better setup, they reached the 40 Mflops zone.
It could also be that JIT, the feature that most of all power up Linpack benchmark, is completely disabled in Froyo builds like JPC. I asked how we could check this, but no-one answered properly to that until now.
I've just upgraded from JM2 to JPC and for sure JM2 is better. JPC has poor responce on finger gestures and is sometimes slow. I hope these problems are solved in the final release. I'm downgrading today!
clubtech said:
Sorry the HK 2.2 is by far better than JPC...
Click to expand...
Click to collapse
Care to elaborate and cite the differences?
Stefanauss said:
In another thread i pointed out the same thing as you are, because i read somewhere else that HTC had to do very little job to optimize JIT for Snapdragon, having google done that with AOSP.
They replied to me saying that first Froyo FWs for Desire and N1 reached ~ the same jump from Eclair Build: 8 to 14 Mflops. Only later, with progressively better setup, they reached the 40 Mflops zone.
It could also be that JIT, the feature that most of all power up Linpack benchmark, is completely disabled in Froyo builds like JPC. I asked how we could check this, but no-one answered properly to that until now.
Click to expand...
Click to collapse
Oh right.. I assumed JIT was enabled but poorly implemented. 14 Mflops without JIT it pretty good! can't wait to see what happens.. Can't wait for a better leak or a proper release..
Ibanez33 said:
Oh right.. I assumed JIT was enabled but poorly implemented. 14 Mflops without JIT it pretty good! can't wait to see what happens.. Can't wait for a better leak or a proper release..
Click to expand...
Click to collapse
JIT is enabled in JPC. We might see a 20 in the final release if we're lucky, but definitely nothing more than that. The Snapdragon phones apparently have a dedicated FPU which enable them to reach such ridiculous scores. Droid X, Droid 2 and all other 1GHz non-snapdragon phones get sub 20 linpack scores on Froyo.
Sent from my GT-I9000 using XDA App
ed10000 said:
JIT is enabled in JPC.
Click to expand...
Click to collapse
How do you know that for sure?
It's a proper question, it's not that i don't believe you.
Stefanauss said:
How do you know that for sure?
It's a proper question, it's not that i don't believe you.
Click to expand...
Click to collapse
I didn't think it was.
EarlZ said:
Care to elaborate and cite the differences?
Click to expand...
Click to collapse
- Does not mess with you efs folder. That alone makes the HK version a winner.
- Excellent GPS reception and lock.
- Excellent battery life
- No lag
- I only had ONE FC with the HK JP2, unlike JPC.
Stefanauss said:
How do you know that for sure?
It's a proper question, it's not that i don't believe you.
Click to expand...
Click to collapse
There are messages about it in the log e.g.
I/dalvikvm(18078): Jit: resizing JitTable from 8192 to 16384
D/dalvikvm( 2477): JIT code cache reset in 5 ms (1048428 bytes 19/0)
we'd need samsung to optimize the jit for their hummingbird, while it might not reach N1 scores it could probably get quite a bit better
but having seen how good samsung code is, well, that just isn't happening
ps: i agree i got less issues with jp2 hk than jpc as well, especially the lags and FC's and *battery life* (it's like double time)
I've been running JPC for 5 days now, and it's great. I have no desire to switch back to an Eclair rom. I still don't have a lag fix installed and don't feel I need to. I'm also not getting any FCs at all.
What's the deal with everyone wanting massive Linpack scores anyway? What software requires that grunt? Movies run perfectly, games are fast, and most other software wouldn't even touch the capabilities of either the Snapdragon or Hummingbird processors.
If it's a pissing contest you want to win against an N1 or Desire owner, simply load up Real Football 2010 and show them how comically fast it is, since it was written for their phone and no frame limiter was appied.
For me it's not about the benchmark per se.
JIT is one of those great Froyo features, and it can massively impact performance (it's clear, for instance, that Snapdragon vs Hummingbird architecture has very little percentage impact on Linpack, it's all about JIT optimization, like 15 to 40 just tuning JIT), not just in some pointless floating point benchmark.
Nevertheless, JIT is an issue where Samsung has to put its hands on code-wise, and they definitely proved during this childhood of this phone that they can very very very much suck at that.
So this benchmark could be helpful to understand how much effort Sammie is putting into Galaxy S Development, maybe.
Related
I just read about a G1 getting a LinPack score of about 3.5ish. Most of the nearly 100% improvementwas attributed to using a rom with JIT. Since the G1 is very similar to the Vogue shouldn't we be able to get similar results.
I am currently getting 1.65.
D
-------------------------------------
Sent via the XDA Tapatalk App
If you thinks that's impressive, you should check out the new Froyo 2.2.
The Nexus One, which has 2.1 got a scrore of 6.5-7 MFLOPS, but with 2.2 it got 37.5 MFLOPS! That's an incredible performance increase.
I want 2.2, the G1 owners can keep their JIT compiler. Them fancy pants people. BTW, the article says that the HTC Hero averages a measly score of about 2 MFLOPS, so us getting 1.65 isn't bad. Though why the Nexus One gets 37.5 MFLOPS with 2.2 makes me wonder. It could be that 2.2 uses the FPU that's in the SnapDragonl, instead of the interger. If that's the case then our devices can only ever do ~1.65, cause they don't come with a FPU processor.
Though if JIT does give G1 owners a boost, then it'll certainly give us a boost. G1 doesn't have a FPU either. I'm also concerned about the 3D accelerator, as we get bad performance in some tests.
The G1 and Vogue share the same chipset--although their CPU is clocked at 528 Mhz, and ours at 400 (at least natively, that is.)
That probably accounts for the difference of 1.65 vs. 2 MFLOPs result.
If the Linpack test is to scale across all platforms, and we estimate an average 400% improvement in floating point performance, we can probably expect 6-8 in terms of a MFLOPs score on Linpack with Froyo.
Real-world applications (integer arithmetic) will not benefit nearly as well as FP arithmetic, because FP arithmetic is incredibly burdensome. However, perhaps an expected improvement of.. 100%, or 2x, is reasonable (depending). Programs with small rapid loops, etc. will see the most benefit. It'll be interesting to see how the Vogue performs.
In regards to graphics / the Vogue GPU:
I'm not completely up to speed on it, but I believe a primitive driver does work for OGL 1.0-based acceleration (Neocore?) but that's it; nothing more than 1.0 (which would explain why Live Wallpapers do not accelerate properly/crash, etc.)
I was under the impression the chipset between the Vogue and the G1/Hero/Eris was the same, and that if we simply used the driver from the G1/Hero/Eris's 2.1 ROM, we'd have full 3D acceleration.. but I don't think that's the case. There's plenty of smarter individuals here who would've ascertained the same thing, but nothing available.
I think (from a GPU perspective) we have official OGL 1.0 support and that's it.
The Kaiser, like the Vogue, uses the 400 Mhz Qualcomm chip. The difference between the chip in the Vogue/Polaris/Kaiser and devices like the G1 is Mhz and small changes done to the ATI accelerator. Though, I don't think the changes for the accelerator are major.
I have no idea about our Android setup. Is it using open source drivers? Is it using a driver taken directly from another Android device and modified, like from the G1?
I also wondered about the battery life using Android with 3D acceleration. Since Android is linux and linux open source graphic drivers are horrible and usually don't have any power management, could it be our poor battery life is due to the graphics driver?
Could it also be that the graphics driver from the G1 would work on our devices, but is a proprietary driver, and therefore can't be distributed? So instead we use open source drivers to avoid legal action?
If anyone knows the answers to these questions that would be great. I'm trying to wonder why my Kaiser with Android uses more battery life when not in use. Browsing the web or talking on the phone the battery life seems normal, but it's when it's idle that it consumes power twice as fast as Windows Mobile. To me it seems something isn't totally off when the device is in standby, and I'm thinking it's graphics related.
I've tested JIT enabled dalvikvm's on both Donut and Eclair. I never saw any noticable improvement in speed. I did however observe longer boot times and odd behavior from heavy memory intensive applications. For example, the browser sometimes doesn't launch when you have clicked it.
Give the JIT dalvikvm a try. Let me know if you experience anything positive on our vogues.
Here's a post for the G1 that uses JIT.
licknuts said:
The libdvm.so that t3steve cross compiled for the DROID at the time was for Android 2.0, the library works for with newer ROMs Android 1.6 that have some eclair pieces built into the kernel, CyanogenMOD has been using bits and pieces for a while now, if other ROM builders have been using his kernel and framework than a good chance it will work for your phone as well.
Click to expand...
Click to collapse
So, does that mean we just need eclair based roms, or is there more to that?
Dukenukemx said:
Here's a post for the G1 that uses JIT.
So, does that mean we just need eclair based roms, or is there more to that?
Click to expand...
Click to collapse
Eh, I'd just wait for Froyo, for an official JIT system designed specifically for use with the native apps in Froyo as well. Running an unofficial JIT compiler with older apps may cause some problems/force closes.. who knows.
Dukenukemx said:
I want 2.2, the G1 owners can keep their JIT compiler. Them fancy pants people. BTW, the article says that the HTC Hero averages a measly score of about 2 MFLOPS, so us getting 1.65 isn't bad. Though why the Nexus One gets 37.5 MFLOPS with 2.2 makes me wonder. It could be that 2.2 uses the FPU that's in the SnapDragonl, instead of the interger. If that's the case then our devices can only ever do ~1.65, cause they don't come with a FPU processor.
Click to expand...
Click to collapse
Without JIT (multiple test runs):
~ 1.65 MFLOPS for first 15 mins or so after startup
~ 2.33 MFLOPS after 15 mins after startup
Time to enable JIT and possible problems with apps, etc. it may cause probably isn't worth it to me.
You guys should check out this thread made by garringm from the Kaiser forum, if you wanna enable JIT. It should work, considering Kaiser users are using Vogue Android builds.
You'll need the Android SDK installed on your PC. Works with Incubus26Jc's Super Eclair and mssmison's CM 5.0.7 test 3. I ran linpack and got 3.3 MFLOPS.
I find at least for our vogues, linpack is not the best thing to judge by. It more calculations based which in most cases doesn't judge load times and the agility of our applications.
As I mentioned, I've used jit on a number of Donut and Eclair roms and although linpack may report a higher score the user experience in the speed dept wasn't improved.
Infact I found app load times to be longer with a jit enabled dalvikvm.
Are you sure the linkpack score isn't acting as a placebo?
Part of the issue is using (an unofficial) JIT compiler on a system not truly designed for it.
Froyo's compiler (along with Froyo's system) are designed to work with and efficiently use the new compiler, which means the best performance (and user experience) is going to come with Froyo, not Eclair/Donut/Cupcake with an unofficial JIT compiler.
I think we should just be patient--Froyo will be out soon, and we will surely port it to the Vogue, which will answer all of our questions.
myn said:
I find at least for our vogues, linpack is not the best thing to judge by. It more calculations based which in most cases doesn't judge load times and the agility of our applications.
As I mentioned, I've used jit on a number of Donut and Eclair roms and although linpack may report a higher score the user experience in the speed dept wasn't improved.
Infact I found app load times to be longer with a jit enabled dalvikvm.
Click to expand...
Click to collapse
Yes, the load times of applications are longer. Especially when applications are already loading slowly, this certainly doesn't help.
Are you sure the linkpack score isn't acting as a placebo?
Click to expand...
Click to collapse
Linpack is probably correct, as are the delays. I've played with emulators in the past, and I understand a bit about JIT. JIT is related to dynamic compilation, which a lot of emulators used in the past. Modern emulators like Dolphin uses JIT.
The idea is that instead of compiling data interpretively, it does it all in one shot, before the program executes. That way the program runs like it was made natively for the hardware. It would make sense that the applications have a delay in execution with JIT.
G1 owners don't have a problem with this since applications launch instantly on their phones. Running JIT for them makes no tangible difference. For us it's worse because we already have a 2-10 second delay to execute applications. This just makes it worse.
Another thing to consider is that many applications don't use MFLOPS, which is the FPU we don't have. Only 3D applications use that, and we don't use many of those. At least not yet. I'd like to try Quake 3 with it and see how it runs.
Hi guys..
I sad Google developed 2.2 to improve snapdragon cpu and becuase of that the benchmarks shows 3X faster cpu on nexus,
will work 2.2 on galaxy like nexus ? or not for SGS cpu!
at all what you think about power of CPU/GPU in SGS on 2.2 ?
Is nexus cpu better than galaxy on Android 2.2 ?
The Galaxy's CPU/GPU is the best on the market right now and with 2.2 it should fix a lot of software problems with the SGS.
Actually can't wait for 2.2, and it's released around about my birthday!
When is your birthday
22nd September mate. You can buy me a Galaxy S as a spare if you want
well I have to see it first.
Guess Samsung finds a way to **** up the phone again i'm sure of that.
matty___ said:
well I have to see it first.
Guess Samsung finds a way to **** up the phone again i'm sure of that.
Click to expand...
Click to collapse
If it has rfs file format and TouchWiz, consider it ****ed up.
kgk888 said:
If it has rfs file format and TouchWiz, consider it ****ed up.
Click to expand...
Click to collapse
If froyo on the SGS sucks, then the chefs in here will cut it open and make it run properly and it won't matter what the FW was like when samsung sent it out. Also, TouchWiz is fine, even if it does have a dumb name.
I have been worried about this. The sgs line and droid line do not get over 15 in linpack with 2.2. I dont see the same increase in speed as I do with snapdragon based phones. I have read this is due to the snapdragon having 128 bit vs 64 bit something but cant find the forum post about this. The sgs line with 2.1 is still faster then a 2.2 snapdragon based phone but it must have the lag fix installed. Without the lag fix it is slower for sure. I will try to find the forum post about 128bit vs 64bit.
http://www.youtube.com/watch?v=gKsAUR61ByM
http://www.youtube.com/watch?v=ji49qFNxC4c
Edit: found the forum post
Originally Posted by Gimic26
Your question was answered already...it comes down to processor architecture. Qualcomm's Snapdragon platform and more specifically the Scorpion application processor, while being related to TI's Omap Arm series, has enhancements made by Qualcomm. The part of the cpu that handles the SIMD instructions has a wider pipeline, 128 bits vs 64 bits in TI's Omap. Scorpion also has a deeper pipeline to better handle all that data which I'd assume offsets some of the performance benefits a little bit.
As far as the difference between the two benchmarks, they are written to benchmark two different things. Linpack can run almost entirely within the SIMD/NEON portion of the cpu thereby showing off the enhancements made by Qualcomm. Quadrant stresses the entire core showing off total system performance showing that only in certain situations will Snapdragon outperform any other Arm based core.
shep211 said:
I have been worried about this. The sgs line and droid line do not get over 15 in linpack with 2.2. I dont see the same increase in speed as I do with snapdragon based phones. I have read this is due to the snapdragon having 128 bit vs 64 bit something but cant find the forum post about this. The sgs line with 2.1 is still faster then a 2.2 snapdragon based phone but it must have the lag fix installed. Without the lag fix it is slower for sure. I will try to find the forum post about 128bit vs 64bit.
http://www.youtube.com/watch?v=gKsAUR61ByM
http://www.youtube.com/watch?v=ji49qFNxC4c
Edit: found the forum post
Originally Posted by Gimic26
Your question was answered already...it comes down to processor architecture. Qualcomm's Snapdragon platform and more specifically the Scorpion application processor, while being related to TI's Omap Arm series, has enhancements made by Qualcomm. The part of the cpu that handles the SIMD instructions has a wider pipeline, 128 bits vs 64 bits in TI's Omap. Scorpion also has a deeper pipeline to better handle all that data which I'd assume offsets some of the performance benefits a little bit.
As far as the difference between the two benchmarks, they are written to benchmark two different things. Linpack can run almost entirely within the SIMD/NEON portion of the cpu thereby showing off the enhancements made by Qualcomm. Quadrant stresses the entire core showing off total system performance showing that only in certain situations will Snapdragon outperform any other Arm based core.
Click to expand...
Click to collapse
From what I've seen and read, the 2.2 builds for the Galaxy S do NOT have a JIT compiler enabled which explains the lower scores. The N1 got the huge CPU boost from having JIT enabled. That doesn't explain the Droid X's scores, but then again I haven't read enough about 2.2 running on the DX to see if it has JIT installed.
What're you think? I'll buy SGS 2.1 or wait for SGS 2.2 ?
It's very important to buy most powerfull phone.
I like Nexuse cus it's tested sucssasfuly in Android 2.2 and I'm gono love SGS if it will be better than nexus in 2.2.
Help me to choose better path )
Vogie said:
What're you think? I'll buy SGS 2.1 or wait for SGS 2.2 ?
It's very important to buy most powerfull phone.
I like Nexuse cus it's tested sucssasfuly in Android 2.2 and I'm gono love SGS if it will be better than nexus in 2.2.
Help me to choose better path )
Click to expand...
Click to collapse
I would wait at this time before purchasing an SGS if that's your concern.
Out of the box, the current phone/software is laggy and disappointing. If you're willing to hack it with some of the various fixes found here (I prefer samset with mimocan kernel), then you won't be unhappy with the phone, but there's no guarantee that Samsung will get FroYo right, and that if they do get it wrong that the devs here will be able to bring you a hot, non-laggy, super FroYo ROM before there's better, or at least comparable hardware done right by the manufacturer available.
That's no reflection on the devs here at all, I'm just thinking that Samsung won't release the firmware until the end of September, the devs will need a couple of weeks to make magic at least, and so now we're well into October. By October, the SGS will be a six month old phone. Six months is a very long time in the Android hardware world, and we'll likely see a landslide of new phones with faster CPU, maybe even dual-cores in the fall for the holiday season. The only thing the SGS will have over other phones at that point is the Super AMOLED screen by Samsung, since they're holding it all to themselves. I wouldn't be surprised if Moto or HTC try to kang the iPhone display tech for newer models if they can't get Super AMOLED for themselves.
In the android world it is nearly impossible to but a device that won't be out of date within at most a year and sometimes within 6 months.
Having said that, I don't see anything that will topple the sgs quite that soon. Although there is talk of dual core snap dragons, there has been nothing announced yet, and indeed the two new Desire handsets are still on the same chip.
I wouldn't expect to see anything that will have more raw power than the sgs until at least mid 2011. If there was anything closer than that it'd already be getting hyped.
If you keep looking at what is just over the horizon then you won't end up ever getting one, because there always seems to be something new out in a few months time. The sgs isn't prefect, but it beats the hell it of most anything that you'll be able to buy this year.
My humble opinion of course, but I think that if you want top end hardware, the sgs will serve you very well.
Sent from my GT-I9000 using XDA App
Based on your responses so far, I'd just get an iPhone 4 and be done with it.
There are a lot of people here and elsewhere who are perfectly happy with the device. I for one haven't installed the lag fix and I don't experience any lags, except for the situations below:
1. I'm trying to do something while there are several apps being installed/downloaded from the marketplace in the background. I think this will be resolved with the dualcore next gen CPU's.
2. Using LauncherPro, for all that is good and nice on this earth, I do not know why it took me 3 months before the option to change the shortcut on its drawer was shown to me. Imagine that, 3 months just to show the option to add a shortcut. Jeezus. I click on add shortcut and it took 3 months. Someone shoot me. I'm using ADW now and am very happy.
Out of sheer curiosity, why is it that you need "THE MOST POWERFUL PHONE"?
shep211 said:
As far as the difference between the two benchmarks, they are written to benchmark two different things. Linpack can run almost entirely within the SIMD/NEON portion of the cpu thereby showing off the enhancements made by Qualcomm. Quadrant stresses the entire core showing off total system performance showing that only in certain situations will Snapdragon outperform any other Arm based core.
Click to expand...
Click to collapse
The hummingbird core is widely recognized to be faster than the snapdragon core. Benchmarks do not tell you everything. Reference:
You might think that the Hummingbird doesn’t stand a chance against Qualcomm’s custom-built monster, but Samsung isn’t prepared to throw in the towel. In response to Snapdragon, they hired Intrinsity, a semiconductor company specializing in tweaking processor logic design, to customize the Cortex-A8 in the Hummingbird to perform certain binary functions using significantly less instructions than normal. Samsung estimates that 20% of the Hummingbird’s functions are affected, and of those, on average 25-50% less instructions are needed to complete each task. Overall, the processor can perform tasks 5-10% more quickly while handling the same 2 instructions per clock cycle as an unmodified ARM Cortex-A8 processor, and Samsung states it outperforms all other processors on the market (a statement seemingly aimed at Qualcomm).
Click to expand...
Click to collapse
Here is a GPU comparison for some of the leading smartphones:
Motorola Droid: TI OMAP3430 with PowerVR SGX530 = 7-14 million(?) triangles/sec
Nexus One: Qualcomm QSD8x50 with Adreno 200 = 22 million triangles/sec
iPhone 3G S: 600 MHz Cortex-A8 with PowerVR SGX535 = 28 7 million triangles/sec
Samsung Galaxy S: S5PC110 with PowerVR SGX540 = 90 million triangles/sec
Click to expand...
Click to collapse
Wait for G2 as nexus one is old news and i think they are winding down production. Frankly i love my sgs. Get it now cos frankly froyo is way over hyped compared to what sgs can do now with a lagfix
Sent from my GT-I9000 using XDA App
ickyboo said:
Wait for G2 as nexus one is old news and i think they are winding down production. Frankly i love my sgs. Get it now cos frankly froyo is way over hyped compared to what sgs can do now with a lagfix
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
You can't really say froyo is over hyped, I mean its free, and beyond that its an incremental upgrade.
I don't see why anyone would be staying on eclair once official froyo drops, and you can't deny that it will bring a performance boost.
Now I doubt it will bring quite as much of a boost as it gave to the N1 until we get a few months of development to really get it running sweetly, but all the same its still not over hyped if I ask me.
With optimized ROMs and whatever fixes we need (cuz samsung WILL break something) I figure the sgs will shred the N1's new scores. I recon we'll see around 3k in quadrant.
Considering how far ahead of almost everything a lag fixed non-stock-rom sgs is now, we'll see something really special once froyo starts rocking our crotches.
Sent from my GT-I9000 using XDA App
The.Opethian said:
Based on your responses so far, I'd just get an iPhone 4 and be done with it.
There are a lot of people here and elsewhere who are perfectly happy with the device. I for one haven't installed the lag fix and I don't experience any lags, except for the situations below:
1. I'm trying to do something while there are several apps being installed/downloaded from the marketplace in the background. I think this will be resolved with the dualcore next gen CPU's.
2. Using LauncherPro, for all that is good and nice on this earth, I do not know why it took me 3 months before the option to change the shortcut on its drawer was shown to me. Imagine that, 3 months just to show the option to add a shortcut. Jeezus. I click on add shortcut and it took 3 months. Someone shoot me. I'm using ADW now and am very happy.
Out of sheer curiosity, why is it that you need "THE MOST POWERFUL PHONE"?
Click to expand...
Click to collapse
Why powerfull phone? ok i'll tell u:
Because I don't like to buy an expensive phone (like SGS) that power is lesser than a chipper phone (like N1) !
Because I'd rather a phone without stalling (lagging) to play games and running big applications. I will very gray if i'll se lagging/stalling...
Because I need a phone with a good support (it's enough, don't need mazing support). a phone with a clear (alive or nice) Future
JIT for Hummingbird should be promising.
High Mem
anyone got any idea on the high mem issue?... when i was browsing the Gmarket.com, i realize 305 total available memory is not enough for me... and the web page just closed....
I posted this on another forum with little avail... I didn't want to clutter this one up... However, without a clear answer, and actually very little intelligent conversation that resultant in my reluctance to actually respond... I have to resort to placing this here.
"
So I have been playing around with the OTA 2.2 and decided to run linpack, I noticed an incredibly low score for froyo, (around 12-14) in comparison to the average Froyo score of 30-40. Figured I would play around in the build.prop, noticed JIT was not mentioned. Did they leave out enabling JIT for the Droid X froyo? Or am I missing something here...
"
This was posted back on the 27 of September, since then I have poked around more and still have found little to answer my original question. Seriously, is it possible to have Froyo without JIT enabled... I know better than anyone to take benchmark scores with a grain of salt, it just seems a little odd to me. As a side note, Java performs worse than my Droid Incredible did, while the snapdragon is indeed a better computational processor, it quite significantly outperformed the Droid X in both Linpack and Java (I don't believe in quadrant enough to even run it...) which it truly should not...
Anybody have any reasonable input?
Where did you ever get the idea that 30-40 is a reasonable score for JIT enabled phones? Because of the N1? As I understand it, the N1's processor offloads the JIT compiler, vastly speeding up MFLOPS (Millions of Floating Operations Per Second) which is GREAT for linpack benchmarks, but its really not important as far as real world performance.
Stop taking so much stock in meaningless benchmark tests. MFLOPS are a terrible way to compare device speeds. Especially when you bring a phone into the mix that has a special way of handling MFLOPS.
Apps that test video decoding/encoding and FPS are much more likely to give you a better idea of real-world phone performance
If I'm wrong in any way people, please feel free to enlighten me.
LexusBrian400 said:
Where did you ever get the idea that 30-40 is a reasonable score for JIT enabled phones? Because of the N1? As I understand it, the N1's processor offloads the JIT compiler, vastly speeding up MFLOPS (Millions of Floating Operations Per Second) which is GREAT for linpack benchmarks, but its really not important as far as real world performance.
Stop taking so much stock in meaningless benchmark tests. MFLOPS are a terrible way to compare device speeds. Especially when you bring a phone into the mix that has a special way of handling MFLOPS.
Apps that test video decoding/encoding and FPS are much more likely to give you a better idea of real-world phone performance
If I'm wrong in any way people, please feel free to enlighten me.
Click to expand...
Click to collapse
With all do respect, it is responses like yours that anger me slightly (albeit very slightly...). I specifically stated in my post that I do not hold benchmark tests in any regard, in fact I despise them... Quadrant in particular is so incredibly broken that a simple trickery in database write caching can bloat your score to such ridiculous heights, that it is not worth even turning an eye to any more. I did state however, that the benchmark did catch my attention enough to make me investigate the JIT compiler on our device. The only comparison I had to make were with 2.1 devices, in which JIT was referenced in the build.prop. I am unaware how it is enabled in 2.2, hence the question. I specify that as a common score as the Devour, EVO, Nexus, Droid Incredible, Samsung Galaxy I900, and iPhone (yes, i said it...) all see scores in the 30's through linpack. I am not giving those scores any relation to performance, because as I stated in my original post, "I know better than anyone to take benchmark scores with a grain of salt"... but thank you for not reading the full post, and discrediting my post *moderately angry face* (but more jokingly).
But in all seriousness, those phones showing the benchmark, while not giving an impression of performance, did give an impression, or rather a relation, to JIT. While JIT does not give performance increases in the amount shown through benchmarks, the performance gain is significant in some areas, and I would be heartstrucken if they managed to provide Froyo without JIT to the Droid X. I was just looking for confirmation that JIT is enabled, or a way to check. If I cannot get a straight answer around here, I will discover it sooner or later on my own. I am not even sure it is possible to have Froyo without having JIT enabled, but it caught my attention enough to have it investigated.
Sorry, i did not mean to upset you by taking time out of my day to TRY and answer your question. (Twice now)
Yes, JIT is enabled.
Edit:
And I guess I should have noted that I wasn't really talking DIRECTLY to you when I mentioned about people should stop taking so much stock in benchmarks. My bad. That was for others who happen to read this.
You guys... let's play nicely.
FWIW I've heard that JIT is in fact enabled...but the reason it's not very prevalent is because JIT was designed to be very efficient mainly with the qualcomm snapdragons and such..not the TI omap. I could be wrong but I believe this is why...and I believe the X still performs just a smoothly as those snapdragons which score higher on the benchmarks (which, I know, is not the question at hand, just giving my 2 cents).
LexusBrian400 said:
Sorry, i did not mean to upset you by taking time out of my day to TRY and answer your question. (Twice now)
Yes, JIT is enabled.
Click to expand...
Click to collapse
Clearly you did not catch the sarcasm and joking tone I had in my writing, my apologies, I updated it to more clearly represent it ;-). Truly was not trying to sound angry, more sarcastically hurt... And I take time out of my day to help people all the time as well... look back at my posts, this is one of the few questions I've asked... I'm not a fan...
I understand, I know who you are... You've done a lot for the community... Thanks... I appreciated the incite and really didn't even care about the comment, I was more just joking about it in that I stated how I don't actually take heed to benchmark scores. Regardless, JIT was an area I am not really all that familiar with, and appreciate the answer. I play more on the system level as I am a Linux Server Administrator and deal mostly with script writing over actual compiling. Sorry if you thought I was taking shots at you ;-)
EDIT: FYI this isn't the first time people have thought I was being an ass to them... I am... what do they call it... anti-social... I just come across that way, I don't mean to however. I think I have actually had this conversation with another Developer on another forum, it ended in him admitting to the same problem... I think we then had crumpets and tea... well maybe not the crumpets and tea, but the rest is true...
Its all good captain taco, I truly wish I had a better answer for you.
the Jit ON/OFF switch, in my other phone, is in the build.prop. However, I do not see it in the Droid X build.prop
From 2.1 to 2.2, the linpack jumped over 6 points. And seeing that its just a software update, I guess you could say I'm blindly assuming that JIT is enabled, but I also want you to take note that apps that have trouble running in conjunction with JIT, also did not perform well until they were updated to work with it.
I can say in 100% confidence and (barely) educated guess, that JIT is in fact, enabled.
Have a good day Taco
LexusBrian400 said:
Its all good captain taco, I truly wish I had a better answer for you.
the Jit ON/OFF switch, in my other phone, is in the build.prop. However, I do not see it in the Droid X build.prop
From 2.1 to 2.2, the linpack jumped over 6 points. And seeing that its just a software update, I guess you could say I'm blindly assuming that JIT is enabled, but I also want you to take note that apps that have trouble running in conjunction with JIT, also did not perform well until they were updated to work with it.
I can say in 100% confidence and (barely) educated guess, that JIT is in fact, enabled.
Have a good day Taco
Click to expand...
Click to collapse
Sounds good to me, that's about as good of an answer as it gets. Thanks
Is there not a way to get a real answer to this question? Motorola should be the source I suppose. Anyone have contact info or access to a Moto android software engineer?
Can someone be motivated to ask Moto if jit is enabled in 2.2 on the X?
We can speculate all we want.
Sent from my DROIDX using XDA App
Izord said:
Is there not a way to get a real answer to this question? Motorola should be the source I suppose. Anyone have contact info or access to a Moto android software engineer?
Can someone be motivated to ask Moto if jit is enabled in 2.2 on the X?
We can speculate all we want.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I feel as though his answer gives fair evidence that JIT is indeed enabled. It's likely just placed elsewhere, after all it was just a single line calling JIT in the build.prop, it could have been placed in any of the startup files, could be in the boot.img for that matter. I really haven't searched through all of the init scripts, and after reading LexusBrian400's response, I likely won't, I feel pretty assured it is enabled.
read the blog about 1/2 way down on nenolod.net titled "how to improve user performance on android phones"
mcsinfl said:
read the blog about 1/2 way down on nenolod.net titled "how to improve user performance on android phones"
Click to expand...
Click to collapse
Have you tried this yourself???
mcsinfl said:
read the blog about 1/2 way down on nenolod.net titled "how to improve user performance on android phones"
Click to expand...
Click to collapse
I believe that blog was meant for pre 2.2 android. I am not even sure we are able to make that change in 2.2, though do not hold me to that.
/etc/sysctl.conf is not a file in our system, and at the end of his post the author quotes "Update: Disabling NORMALIZE_SLEEPERS on Android 1.6/2.0/2.1 is a good idea."
Edit: Scratch the above, further digging in the comments section of that particular post:
nenolod says:
July 22, 2010 at 4:56 am
@moo: these are all scheduler enhancements made upstream already. Froyo already has them.
Click to expand...
Click to collapse
CaptainTaco said:
I believe that blog was meant for pre 2.2 android. I am not even sure we are able to make that change in 2.2, though do not hold me to that.
/etc/sysctl.conf is not a file in our system, and at the end of his post the author quotes "Update: Disabling NORMALIZE_SLEEPERS on Android 1.6/2.0/2.1 is a good idea."
Edit: Scratch the above, further digging in the comments section of that particular post:
Click to expand...
Click to collapse
The rubix rom has that mod in it. In the changelog, where he mentions "tweaks by nenolod" The Sleepers mod is what he is talking about. I just ran the code from nenlods blog and it went through fine. (on rubix) Sometimes sysctl.conf is in the /sys file I believe. I think thats what nenlod said, I talked to him last night about it because I was curious.
Anyway, it works on Rubix
JIT is enabled without a doubt.
The only reason there was a line in the build.prop was because it was a homemade JIT compiler for our phones. This is probably embedded into Froyo.
Just wanted to confirm, I watched a logcat today for about 15 minutes, JIT came up several times.
Download Alogcat and have a looksee for yourself.
It may take a while, but it'll come up for sure.
CONFIRMED
/end thread
LexusBrian400 said:
The rubix rom has that mod in it. In the changelog, where he mentions "tweaks by nenolod" The Sleepers mod is what he is talking about. I just ran the code from nenlods blog and it went through fine. (on rubix) Sometimes sysctl.conf is in the /sys file I believe. I think thats what nenlod said, I talked to him last night about it because I was curious.
Anyway, it works on Rubix
Click to expand...
Click to collapse
i had a little trouble finding the sysctl file on my phone but it turned up in the /system/bin .
i like to keep a copy of any file i change, incase anything goes awry and I tried viewing the contents of the file on my PC but it was just a bunch of cryptic symbols. Is there a way to see what the file contains?
and thanks for the logcat confirmation of jit
drewden123 said:
FWIW I've heard that JIT is in fact enabled...but the reason it's not very prevalent is because JIT was designed to be very efficient mainly with the qualcomm snapdragons and such..not the TI omap. I could be wrong but I believe this is why...and I believe the X still performs just a smoothly as those snapdragons which score higher on the benchmarks (which, I know, is not the question at hand, just giving my 2 cents).
Click to expand...
Click to collapse
This is exactly true. The OMAP doesn't see nearly the gains from JIT as the hummingbird/snapdragon does.
The possibilty of Android 2.2 speed improvements made us Vibrant owners salivate in anticipation for the JIT compiler but didnt see a significant increase in performance like it did with the nexus one. One thing that could eliminate lag in addition to lag fixes is optimization of JIT for our CPU hardware. We would like a proactive effort for developer to investigate for the above avg user. (Non-Developers) JIT Optimization = Higher Linpack MFLOPS
I think we're getting it in gingerbread =p
Sent from my SXY-T959
Im tired of hearing about linpack and quadrent scores already,they mean nothing.This is the fastest phone on the market right now period,if you dont like it trade it for a g2 or what have you like the rest of the idiots on craigslist.I personally have used every android phone available on tmo including the nexus1,g2,and mt4g.I xan tell you imho this phone is way faster and more responsive,and obviously the display and graphics are 2nd to none.complain about the lack of flash or ffc,but please dont complain about speed and performance,and as far as lag,try flashing a bionix rom after a clean stock odin,I've been using it since it came out and can tell you bionix final v2,and my current rom obsedion v5 run smooth as hell w/ no lagfix or oc kernal.So do yourself a favor,ignore linpack scores.
Jerzeeloon said:
Im tired of hearing about linpack and quadrent scores already,they mean nothing.This is the fastest phone on the market right now period,if you dont like it trade it for a g2 or what have you like the rest of the idiots on craigslist.I personally have used every android phone available on tmo including the nexus1,g2,and mt4g.I xan tell you imho this phone is way faster and more responsive,and obviously the display and graphics are 2nd to none.complain about the lack of flash or ffc,but please dont complain about speed and performance,and as far as lag,try flashing a bionix rom after a clean stock odin,I've been using it since it came out and can tell you bionix final v2,and my current rom obsedion v5 run smooth as hell w/ no lagfix or oc kernal.So do yourself a favor,ignore linpack scores.
Click to expand...
Click to collapse
i love this guy.
well said.
Jerzeeloon said:
Im tired of hearing about linpack and quadrent scores already,they mean nothing.This is the fastest phone on the market right now period,if you dont like it trade it for a g2 or what have you like the rest of the idiots on craigslist.I personally have used every android phone available on tmo including the nexus1,g2,and mt4g.I xan tell you imho this phone is way faster and more responsive,and obviously the display and graphics are 2nd to none.complain about the lack of flash or ffc,but please dont complain about speed and performance,and as far as lag,try flashing a bionix rom after a clean stock odin,I've been using it since it came out and can tell you bionix final v2,and my current rom obsedion v5 run smooth as hell w/ no lagfix or oc kernal.So do yourself a favor,ignore linpack scores.
Click to expand...
Click to collapse
yes, basing everything off benchmarks is dumb. however, you can't ignore the fact that optimizing JIT for the hummingbird will net real world performance improvements.
funeralthirst said:
yes, basing everything off benchmarks is dumb. however, you can't ignore the fact that optimizing JIT for the hummingbird will net real world performance improvements.
Click to expand...
Click to collapse
thank you.....and plus i kno about the myth of high linpacks = better performance. i said "JIT optimization = High linpacks". High Linpack is a side affect of the performance increase. The nexus One performance has jumped exponentially from 2.1 to 2.2 because of the JIT optimization of the Snapdragon in theory, it should do the same for the vibrant as well. Everybody's phone reacts to sofware differently. think im lying, ask the ppl who had vibrants that couldnt OC like the rest like myself or ppl who cant have Voodoo. Trust me lil boy i aint nowhere a noob. Please take ur trollism to some1 else who dont kno wtf theyre talkin about. Actually G2 is the fastest phone on the Market FYI despite being clocked at @806MHz w/o root. If i really wanted to get another phone, i wouldnt be posting stuff like this or being an active poster in a Vibrant forum right? Right????? Checkmate....
1 last thing...f##k yo couch
This has been discussed before, certain Qualcomm chips are better optimizer for arithmetic calculations than the Hummingbird it. It means nothing in real world usage, where the Galaxy S variants still dominate (with a "lag" fix, of course)
Still, despite obvious advantages of Qualcom's CPU, the Hummingbird still can benefit from software optimizations of JIT to efficiently interface the hardware. Performance may not jump like it did w/ the N1, but it would help. Just like a car w/ 600 HP. A car w/ that amount of power is just useless unless it efficiently gets ALL that power to the tires right? same concept applies.
We are not getting it in gingerbread. The snapdragon have faster FPU performance due to a 128 bit SIMD FPU datapath compared to Cortex-A8's 64 bit implementation. Both FPUs process the same SIMD-style instructions, the snapdragon just happens to be able to do twice as much.
http://www.insidedsp.com/Articles/t...ualcomm-Reveals-Details-on-Scorpion-Core.aspx
shep211 said:
We are not getting it in gingerbread. The snapdragon have faster FPU performance due to a 128 bit SIMD FPU datapath compared to Cortex-A8's 64 bit implementation. Both FPUs process the same SIMD-style instructions, the snapdragon just happens to be able to do twice as much.
http://www.insidedsp.com/Articles/t...ualcomm-Reveals-Details-on-Scorpion-Core.aspx
Click to expand...
Click to collapse
Look at who made the N1 tho.... HTC is the King at making Android phones. Comparing a N1 to the Vibrant is like comparing a Honda to Ford (Fix Or Repair Daily ) lol I still love my Vibrant tho its a Ford lol
Jerzeeloon said:
Im tired of hearing about linpack and quadrent scores already,they mean nothing.This is the fastest phone on the market right now period,if you dont like it trade it for a g2 or what have you like the rest of the idiots on craigslist.I personally have used every android phone available on tmo including the nexus1,g2,and mt4g.I xan tell you imho this phone is way faster and more responsive,and obviously the display and graphics are 2nd to none.complain about the lack of flash or ffc,but please dont complain about speed and performance,and as far as lag,try flashing a bionix rom after a clean stock odin,I've been using it since it came out and can tell you bionix final v2,and my current rom obsedion v5 run smooth as hell w/ no lagfix or oc kernal.So do yourself a favor,ignore linpack scores.
Click to expand...
Click to collapse
Couldn't disagree more. I've also used just about every Tmobile compatible android smartphone. I currently have a Vibrant and I wish I would have kept my N1. And I almost pulled the trigger on trading in this POS for a G2 but the financial loss was just too great. I've yet to try any Bionix based MOD that was worth a damn. Not a one. Admittedly I've quit trying but I can't imagine much has changed.
The only thing keeping me from throwing this phone in the ocean some days is Cyanogen's team is getting close. I'm running the beta on a Euro SGS I have. Hate it as much as the Vibrant but I'm hopeful CM can save this phone from a sledgehammer.
You may be tired of hearing it but from my seat, as long as Samsung controls anything on these phones you will continue to hear it. Loudly.
boimarc89 said:
Look at who made the N1 tho.... HTC is the King at making Android phones. Comparing a N1 to the Vibrant is like comparing a Honda to Ford (Fix Or Repair Daily ) lol I still love my Vibrant tho its a Ford lol
Click to expand...
Click to collapse
Please, stop embarrassing yourself. The Nexus One is and was a great phone, but the Vibrant is better in almost every way. Better hardware, bigger screen, better screen, faster, and more units sold.
boimarc89 said:
Look at who made the N1 tho.... HTC is the King at making Android phones. Comparing a N1 to the Vibrant is like comparing a Honda to Ford (Fix Or Repair Daily ) lol I still love my Vibrant tho its a Ford lol
Click to expand...
Click to collapse
Wonderful analogy. I however do not love my Vibrant. I love the hardware and screen but because Samsung pulls the strings, usually I want to drop kick the thing because of it's limitations, instability and overall suck of the Samsung ROM. And yes, pretty much all the mods to it on here. Though Axura is about the closest thing my phone actually likes.
What makes you even think the Galaxy S line is even going to see Gingerbread? This is Samsung we are talking about...
boimarc89 said:
Look at who made the N1 tho.... HTC is the King at making Android phones. Comparing a N1 to the Vibrant is like comparing a Honda to Ford (Fix Or Repair Daily ) lol I still love my Vibrant tho its a Ford lol
Click to expand...
Click to collapse
Htc fell off and google knows it,thats why the new nexus is made by samsung,htc may have pioneered android but there sound always sucked and right now samsung kinda controls the display game,nobody else can produce super amoled and there abou to release super amoled 2,admitidly samsung has a bad rep for not supporting current models(i.e. The whole behold 2 debacle.) And words can't describe how much I hate motorola,htc is still good but I wouldnt call them the android kings,I feel samsung has alot of potential to become the flagship brand for google.
pigs3littleones said:
Couldn't disagree more. I've also used just about every Tmobile compatible android smartphone. I currently have a Vibrant and I wish I would have kept my N1. And I almost pulled the trigger on trading in this POS for a G2 but the financial loss was just too great. I've yet to try any Bionix based MOD that was worth a damn. Not a one. Admittedly I've quit trying but I can't imagine much has changed.
The only thing keeping me from throwing this phone in the ocean some days is Cyanogen's team is getting close. I'm running the beta on a Euro SGS I have. Hate it as much as the Vibrant but I'm hopeful CM can save this phone from a sledgehammer.
You may be tired of hearing it but from my seat, as long as Samsung controls anything on these phones you will continue to hear it. Loudly.
Click to expand...
Click to collapse
Oh Ye of little faith.......... Get real I have had almost every phone on the market (I can afford to buy what I want when I want) and after so many this has come closet to what I've been looking for especially since the 2.2 roms are out. My Biggest complaint about people knocking the phone is they always blame the phone for their poor flashing skills. This phone rocks and it is flexible enough to allow gingerbread whenever it arrives. Try that with a DroidX or HD7......(you fill in the name)....BTW I have a FFC and talk over 3g on it using tango without lag. I just need to make it so I can video a call to a computer and I am golden.
Bottomline..........this is a great phone........that is why there are so many devs playing with it.
boimarc89 said:
thank you.....and plus i kno about the myth of high linpacks = better performance. i said "JIT optimization = High linpacks". High Linpack is a side affect of the performance increase. The nexus One performance has jumped exponentially from 2.1 to 2.2 because of the JIT optimization of the Snapdragon in theory, it should do the same for the vibrant as well. Everybody's phone reacts to sofware differently. think im lying, ask the ppl who had vibrants that couldnt OC like the rest like myself or ppl who cant have Voodoo. Trust me lil boy i aint nowhere a noob. Please take ur trollism to some1 else who dont kno wtf theyre talkin about. Actually G2 is the fastest phone on the Market FYI despite being clocked at @806MHz w/o root. If i really wanted to get another phone, i wouldnt be posting stuff like this or being an active poster in a Vibrant forum right? Right????? Checkmate....
1 last thing...f##k yo couch
Click to expand...
Click to collapse
You, my friend, are not very smart. This thread needs to be closed or moved to general. Just as you would make an idiot of yourself trying to argue relativistic quantum mechanics with physicists, you are doing now.
This thread got interesting. As has already been said the Snapdragon benefits from JIT more because of its 128bit SIMD. While I am sure there is probably some room left to optimize JIT for the Hummingbird I wouldn't expect anything near the gain the N1 saw. I guess it is good or bad depending on how you look at it but the latest 2.2 ROMs floating around is as good as it gets regarding 2.2 and JIT. Don't expect much if any gain there.
But lets face it in the real world the phones perform about the same which leaves me to believe the benchmarks are that much more meaningless because they usually don't test things you actually use the phone for. Some of them would have you belive the N1 is twice as fast as the SGS and anyone with a grasp on reality just knows that isn't true. This also makes me curious when I read about people saying their phones are slow. It makes me wonder what they have done to them to slow them down because even on the stock ROM my phone was pretty snappy. And on Onyx 4.2 my phone is blazing fast with no lag fix or OC! Seriously this ROM is crazy smooth and fast and everything works.
Don't expect much from CM that you can't already get in the 2.2 ROMs floating around here. CM will still be RFS and they are using the same lag fix as everyone else here and really there isn't much of an advantage to their ROM as long as that is the case. Sure they will have features that you won't see in other ROMs here but overall I expect the CM ROMs will perform about the same as the SGS source based ROMs.
As I have already said I think this phone is fast but if there is any real speed gain to be had it will be accomplished by replacing RFS with something more efficient.
pigs3littleones said:
Couldn't disagree more. I've also used just about every Tmobile compatible android smartphone. I currently have a Vibrant and I wish I would have kept my N1. And I almost pulled the trigger on trading in this POS for a G2 but the financial loss was just too great. I've yet to try any Bionix based MOD that was worth a damn. Not a one. Admittedly I've quit trying but I can't imagine much has changed.
The only thing keeping me from throwing this phone in the ocean some days is Cyanogen's team is getting close. I'm running the beta on a Euro SGS I have. Hate it as much as the Vibrant but I'm hopeful CM can save this phone from a sledgehammer.
You may be tired of hearing it but from my seat, as long as Samsung controls anything on these phones you will continue to hear it. Loudly.
Click to expand...
Click to collapse
From what I understand cm for the vibrant still has a lot of proprietary samsung stuff in it, because otherwise it just wouldn't work.
Sent from my SGH-T959 using XDA App
boimarc89 said:
Look at who made the N1 tho.... HTC is the King at making Android phones. Comparing a N1 to the Vibrant is like comparing a Honda to Ford (Fix Or Repair Daily ) lol I still love my Vibrant tho its a Ford lol
Click to expand...
Click to collapse
...did you just say Honda is the king of making cars?
Simply put, I just flashed GB (3/26), and the first thing I noticed was that games (MX moto light in particular) were playing like a slideshow compared to the froyo rom I just came from. This is one of the few games that actually plays well on the hero (on froyo at least), but GB just doesn't respond well at all. Does anyone have a solution?
FWIW, I have tried JIT on/off, tinkered with VM Settings and other performance options and it plays just as bad.
Thanks!
*looks around for il Duce*
Many changes have come to Gingerbread, and no rom, as far as I'm aware, is considered "Stable" on the HeroC. Maybe aosp's. But that said, they definitley haven't entered the "tweak every ounce of performance out of it" phase, and might explain why.
Feel free to join the Devs, and please post in the Questions section next time
Weird. I am on the same rom and that game plays great. I have jit on, Purging of assets on, CPU @ 768 with the performance governor. I did notice a slight slowdown coming from froyo. Perhaps consider doing a full wipe.
macraze said:
Weird. I am on the same rom and that game plays great. I have jit on, Purging of assets on, CPU @ 768 with the performance governor. I did notice a slight slowdown coming from froyo. Perhaps consider doing a full wipe.
Click to expand...
Click to collapse
Hmm... Well I actually originally flashed GB about 2 months ago, and went back to froyo after only a week because of the exact same issue. So I did a full wipe essentially twice; I think it's safe to say I can rule that out, unless I did something wrong twice that I don't know about (?).
This time around, GB seems to be running overall on par, if not better than froyo, except for this game. Another game I just tested (Ninja Rush Deluxe) seems to be running as well as it did on froyo, which is weird considering how bad MX Moto runs.
cybertimber2007 said:
Many changes have come to Gingerbread, and no rom, as far as I'm aware, is considered "Stable" on the HeroC. Maybe aosp's. But that said, they definitley haven't entered the "tweak every ounce of performance out of it" phase, and might explain why.
Feel free to join the Devs, and please post in the Questions section next time
Click to expand...
Click to collapse
your the 2nd person to say to post in the Q&A section next time.... this is the Q&A section! lol
commandment 7:
THOU SHALT LEARN HOW TO TWEAK YOUR DEVICE
cp0020 said:
your the 2nd person to say to post in the Q&A section next time.... this is the Q&A section! lol
Click to expand...
Click to collapse
Both of the threads you're referring to were originally in dev, and were moved.
seriously OP, try using and tweaking the ROM for a day or two, ANY variant of GB blows froyo out of the water for games, but maybe requires a little more tweaking. I would suggest aospCMod, 352 min interactive, JIT, purge, opengles version 131072, sd tweak, comcache 26, dithering, vm heap 32 or 48.