Related
I thought it worth opening a discussion on the recent Google engineer's Google+ post on how ICS handles hardware acceleration vs. Honeycomb. That is to say, it doesn't offer "more" hardware acceleration at all.
https://plus.google.com/105051985738280261832/posts/2FXDCz8x93s
Not to say that ICS won't be more highly optimized nor that it might not have better multi-core support (I have no idea if it does or doesn't), but it's not going to offer magically better hardware acceleration than Honeycomb.
Thoughts?
That was an interesting read when I saw it earlier, yes. I can't really say what the consequences of it are, as I haven't used Honeycomb. At least we can take from it that, as Tegra 3 has the most powerful GPU on any Android device, it has the most potential to be the smoothest in operation?
Mithent said:
That was an interesting read when I saw it earlier, yes. I can't really say what the consequences of it are, as I haven't used Honeycomb. At least we can take from it that, as Tegra 3 has the most powerful GPU on any Android device, it has the most potential to be the smoothest in operation?
Click to expand...
Click to collapse
Unlikely.
When it comes to hardware acceleration and multi-core support, then Android 4.0 is pretty much the same as Honeycomb. My only hope is that the UI of Android 4.0 is better, as it is not very laggy on my Galaxy Nexus.
Multi-core will play more role when there are a lot of parallel tasks, it might affect some games, but overall, while it will be the best Android tablet yet, it won't be the best tablet ever. For that we still have to wait at least a year or more.
so they're saying it's just their piss poor optimization for ANYTHING that makes dual core devices with 1GB of ram run like crap on their OS.
dissapointing.
kristovaher said:
Unlikely.
When it comes to hardware acceleration and multi-core support, then Android 4.0 is pretty much the same as Honeycomb. My only hope is that the UI of Android 4.0 is better, as it is not very laggy on my Galaxy Nexus.
Multi-core will play more role when there are a lot of parallel tasks, it might affect some games, but overall, while it will be the best Android tablet yet, it won't be the best tablet ever. For that we still have to wait at least a year or more.
Click to expand...
Click to collapse
It's...a paradox!
Optimization is the name of the game. ICS will help the Tegra 2 tabs, but i suspect it will have an even greater impact on the prime.
kristovaher said:
When it comes to hardware acceleration and multi-core support, then Android 4.0 is pretty much the same as Honeycomb.
Click to expand...
Click to collapse
Indeed. I was really referring to this in the linked article:
As device screen resolution goes up, achieving a 60fps UI is closely related to GPU speed and especially the GPU’s memory bus bandwidth.
Click to expand...
Click to collapse
I think the reality is ...
Google screwed the pooch when it came to having non-native apps (aka framework based) be accelerated *efficiently* in pre-3.0 days. Some operations did go to the GPU then, but the fact was some sub-view getting invalidated caused much more rendering than was needed.
In 3.x they added an option to have apps say "please accelerate me", but that option is an "opt-in". That choice was done for back-compatibility (not *every* operation in the framework is allowed to be accelerated which means some apps could break).
In reality, most of the "OS" level apps did an opt-in, but not everything. I also doubt general "market" apps do the opt-in (unless they are 3.x+ only).
In 4.x, it's going to be an "opt-out" strategy. So, if an app is broken in ICS, then the developer needs to update/fix their code (IFF necessary, since most are likely to "just work").
kristovaher said:
Unlikely.
When it comes to hardware acceleration and multi-core support, then Android 4.0 is pretty much the same as Honeycomb. My only hope is that the UI of Android 4.0 is better, as it is not very laggy on my Galaxy Nexus.
Multi-core will play more role when there are a lot of parallel tasks, it might affect some games, but overall, while it will be the best Android tablet yet, it won't be the best tablet ever. For that we still have to wait at least a year or more.
Click to expand...
Click to collapse
From what I understand, Honeycomb offers dual-core support. ICS offers greater support than only dual-core.
While that whole read was a little bit disappointing, I am still convinced that ICS overall has been cleaned up compared to Honeycomb/Gingerbread and will make better use of the exceptional hardware of Android devices. The Verge gave ICS an absolutely glowing review in their review of the Galaxy Nexus (they notably said that it was the single greatest leap in the Android OS), and for my particular phone (HTC Sensation), the people who have tried a pre-alpha build of ICS have said that it's already a good deal smoother than Gingerbread ROMs, and of course they aren't even using fully fleshed out builds of ICS.
Whether or not ICS offers things a lot of people have been talking about like greater hardware acceleration, I don't care. As long as it's smoother and can finally hold up a torch to the speed of iOS, that's all that matters. I couldn't care less about the means to achieve that.
I think the biggest gain tye dev community (and in turn the userbase) is going to get from ics is that they will finally release source for a tablet branch of android.
The Janitor Mop said:
the people who have tried a pre-alpha build of ICS have said that it's already a good deal smoother than Gingerbread ROMs, and of course they aren't even using fully fleshed out builds of ICS.
Click to expand...
Click to collapse
I've no doubt that ICS significantly improves on Gingerbread on phones. The question is, how significant will the improvement be from Honeycomb on tablets?
Not saying either way, just moving the discussion along.
wynand32 said:
I've no doubt that ICS significantly improves on Gingerbread on phones. The question is, how significant will the improvement be from Honeycomb on tablets?
Not saying either way, just moving the discussion along.
Click to expand...
Click to collapse
Of course, there is no way to say for sure. But Gingerbread has dual-core support just like Honeycomb does. Assuming part of the reason these pre-alpha ICS builds for my phone are so fast is better multi-core support, then I would think there's good evidence ICS would also improve multi-core support over Honeycomb. I don't think there's any reason to doubt that ICS will be faster on tablets than Honeycomb was, though I will admit we really do have no way of knowing how much. Ultimately, I say we give up the whole "in theory" game, wait for our TF Prime's to ship, and then update them to ICS once that update becomes available. Considering that Asus promised a before the end of the year update, I'd assume that means mid-January is the latest we get ICS. That's only about 5-6 weeks from now to wait to personally be able to see what ICS can do.
A great reply to the initial post:
https://plus.google.com/100838276097451809262/posts/VDkV9XaJRGS
If you're into this stuff, it's a pretty interesting read.
I'll read it, but he starts by saying that webOS performs without lag. Um, what?
Sent from my SPH-D710 using Tapatalk
Even Nvidia have confirmed already that software will not matter when it comes to the tegra 3 chipset...
It treats all software the same quad core optimized or not. I dont think ICS will improved anything other than maybe anti-piracy. It will also suck down your 1gb ram alot quicker too because it requires more ram to operate than honeycomb.
Here is a video from nvidia showing how the cores work with software, quad core optimized or not.
http://www.hardwareclips.com/video/5447/NVIDIA-Tegra-3-Fifth-Companion-Core
ModestMuse23 said:
A great reply to the initial post:
https://plus.google.com/100838276097451809262/posts/VDkV9XaJRGS
If you're into this stuff, it's a pretty interesting read.
Click to expand...
Click to collapse
wynand32 said:
I'll read it, but he starts by saying that webOS performs without lag. Um, what?
Click to expand...
Click to collapse
Haha! He's mostly right, but as the owner of a TouchPad he probably should have kept WebOS off his list of those that "do it right".
Hi all,
I've been playing with the ICS builds (be it CM9, AOKP, or Butter) and they all suffer from what I refer to as choppiness. This is most easily seen scrolling the homescreens which feels slightly jerky. It can be pinpointed using the program fps2D (you have to get it from another device, doesn't show up on the market with the Touchpad). When you launch fps2D you will see how the ball moves smoothly and every now and then it jerks back and forth.
This creates the really bad score that it receives in the benchmark. 3D performance is also rather bad for some reason.
Why am I starting this topic? No, its not a rant. I'm letting everyone know this same issue was encountered with the T-Mobile Galaxy S2 which is based I believe on the same chipset. Initially, the device had really bad stutter which it seems is very similar to the stutter I am seeing when I run fps2D on the touchpad. After some experienced devs started tracking the issue down, they found it was the 2D GPU drivers causing the issue and they fixed it by using the AT&T Skyrocket 2G GPU drivers. The skyrocket also uses the same chipset. I believe this same bug is currently plagueing the HP Touchpad ICS builds as the choppy performance is stemming from the GPU.
Can a kernel dev look into the issue? The Skyrocket GPU drivers (and now the fixed T-Mobile SGS2) should have the answer.
As far as i can understand, devs can't just take and use any driver, they need this driver to be made for ICS, which is a problem right now, since there are no dual-core Qualcomm devices with official ICS.
I'm coming from the uk galaxy s2 and this phone seems a bit choppy .. like when typring it takes a bit to catch up? Any way to speed it up? Should I turn something on or off?
The Samsung keyboard is very slow. I've had the best luck with smart keyboard. I still get the occasional hiccup once and a while tho.
I'm suprised I haven't seen any build.prop tweaks yet
Sent from my SAMSUNG-SGH-I717 using xda premium
I use A.I keyboard, its always been great..
I mean the over all system, I'm really thinking of returning it for the Skyrocket, this bothers me. I'm guessing ICS will be more intensive, and if it's already chocking on Gingerbread well, heck the phone will really have a tough time with ICS! Any thoughts on this?
Thremix said:
I use A.I keyboard, its always been great..
I mean the over all system, I'm really thinking of returning it for the Skyrocket, this bothers me. I'm guessing ICS will be more intensive, and if it's already chocking on Gingerbread well, heck the phone will really have a tough time with ICS! Any thoughts on this?
Click to expand...
Click to collapse
ICS optimizes performance, based on the performance of the Gnex atleast. It has a weaker 4430 TI cpu, and a slightly lower resolution screen.
I'm not sure what you mean by choppiness, even with system powersaving and battery saver on, it's not choppy for me. Android 3.0... now that was choppy!
You might try the OC kernel, that should help your performance, even at stock.
spykerv said:
ICS optimizes performance, based on the performance of the Gnex atleast. It has a weaker 4430 TI cpu, and a slightly lower resolution screen.
I'm not sure what you mean by choppiness, even with system powersaving and battery saver on, it's not choppy for me. Android 3.0... now that was choppy!
You might try the OC kernel, that should help your performance, even at stock.
Click to expand...
Click to collapse
The Galaxy Nexus has an OMAP 4460..
Sorry, I think I was thinking of the Droid Razr (which afaik has that).
Well, the 4460 has comparable performance no? Look at the Gnex on ICS, its fantastic! There are many optimization, if anything, it will run much faster once ICS rolls around.
I had a Skyrocket and my stock, rooted Note is every bit as fast.
Huh.. I might try a factory reset, think this would help? Or maybe I got something running taking up the ram? How should I go about this investigation?
ICS will do so much better on this phone than most phones currently on the market and if Samsung and At&t dont bloat it too much, most likely better the the Gnex, the specs are just better on this phone
Sent from my SAMSUNG-SGH-I717 using XDA
Use this ICS themed keyboard in the market.
https://market.android.com/details?...sMSwyLDEsImlucHV0bWV0aG9kLmxhdGluLnBvcnRlZCJd
**DISCLAIMERS**
This thread has no intention of attempting to complain, diminish, degrade, or criticize any developers on this forum or any of their work, as all of us are nothing but grateful for the amount of free, altruistic, and superior quality code that they provide us with. :good:
This thread has no intention of trying to reiterate the content of the "Butery Smoothness" thread found at http://forum.xda-developers.com/showthread.php?t=1814010 nor to define what "Buttery Smoothness" is, as the previous thread defines it well enough already through the posts and insight of multiple users.
This thread has been created with full knowledge and consideration of the alpha development stage that Android 4.1.1 is currently in and all content discussed in this thread is stated with regard to said knowledge and should only be perceived as an attempt to contribute to at least one of multiple bug fixes to further improve the state of Android 4.1.1 on the SGH-i717 for the good of all users
Purpose
The purpose of this thread is to solve the perceived lack of graphical smoothness and fluidity inside of Android 4.1.1 (Jelly Bean) on the SGH-i717 which has been noticed and reported by many users in multiple ROM's through the collaboration of information, ideas, and solutions between all users and developers.
Background
Many users have reported a significant lack of graphical performance in multiple Jelly Bean ROM's for the SGH-i717 in various scenarios such as home screen navigation, UI animations, and in-app scrolling where there is not only a user-noticeable drop in performance but a quantifiable drop in frame-rate. With Google's Project Butter being a highlight of Jelly Bean, the lack of smoothness in its current state for our device brings not only dismay but logical confusion as other, older devices with lower specifications (such as the Galaxy Nexus for example) perform better graphically than the SGH-i717 with higher specifications. The higher graphical performance in the older Ice Cream Sandwich indicates that the highlighted performance issue in Jelly Bean is not related to hardware incapability but to software utilization of the hardware.
I want to leave as little of my insight in this thread as possible because I want to hear from other users but I'll post some initial information and questions to provoke some response.
Ever since Jelly Bean development began, I've noticed this issue on my device and have even had a replacement device with the same experience so hardware isn't a likely culprit in my opinion. h0tw1r3 was one of the first developers to bring a Jelly Bean ROM to SGH-i717 users and other ROM's were formed briefly after his using it as a base. Until about the third or fourth build ( 8-21 I believe), the performance was sluggishly the same. After this build though, there was a noticeable increase in graphical performance, although still significantly behind ICS. That new standard hasn't changed much since until the latest CM10 nightly builds where I've noticed quite an increase in graphical performance putting it a little closer to ICS performance but still painfully behind such that Dolphin is the only browser that feels smooth enough to use efficiently.
I have also noticed an odd phenomenon where the performance varies from build to build without a noticeably significant change. For example, I remember using DaGr8's AOKP port for a while and finding it smoother than other ROM's at the time but once installing his next build (that only mentioned minor unrelated changes, although some could have been unlisted) the performance was back down again. I have experienced this with multiple different ROM's though which is what is most peculiar that there is so much inconsistency.
Helpful Questions
Have you noticed any of these issues before? If so, which ones?
Do you think the issue is hardware or software/driver related?
How would you compare your best JB experience to stable ICS builds?
Which processes/applications perform the best and the worst for you graphically?
Which ROM's run smooth for you and which ones don't?
Which browsers have you tried in Jelly Bean and which ones do you prefer the most?
Have you noticed graphical performance issues in Chrome consistently at all? If so, in which ROM's or instances have you experienced such?
Do you have any ideas/suggestions as to what is causing or what could fix this issue?
And regardless of the inevitable bugs we are experiencing in alpha software, are you extremely grateful for the developers who have provided us with them? (SAY YES!!)
If any of you would like to add more content or questions to this list (and PLEASE do), just ask them and I'll add them to this OP.
Suggestions and Modifications for Improvement (list will grow over time as new information is presented)
1) Verify that the "debug.mdpcomp.maxlayer" parameter in build.prop is set to the value of 3 and not 2 when you first install a ROM (thanks to NYConex for the tip!). Some developers/ROM chefs (lol) will customize this setting based on their preference. This setting disables (value 2) and enables (value 3) GPU acceleration taking the load off of the CPU. Disabling has fixed the flicker issue that has developed in Jelly Bean for many people but will severely impact performance and graphical smoothness as well as battery life potentially. For flickering, I instead recommend using a live wallpaper which will force the GPU to refresh the screen much more often disabling flicker (in the homescreen at least).
2)**ESSENTIAL FIX FOR SIGNIFICANT IMPROVEMENT** Change the debug.composition.type in /system/build.prop from "dyn" to "gpu" and reboot. This makes a MAJOR difference in ALL areas of performance. The existing string that is entered by default is a "dynamic" setting which alternates putting the graphical load on either the GPU or CPU depending upon resource allocation. Changing the setting to "gpu" will force Android to constantly use the GPU for graphics so you won't notice stutter and lag as Android switches the load from the CPU and GPU. Using this setting also increases overall system speed IMMENSELY as it allows the CPU to do more central tasks like launching applications and communicating with hardware instead of handling the graphics. This "constant GPU setting" plays very nicely with Project Butter in the sense that it uses a constant component of hardware to render graphics along with the constant frame rate that VSync provides. I may try to learn how to make my first ROM sometime soon and when I do, I'll be sure and integrate this into the ROM. Either thank the post or let everyone know if this has helped you!
I have noticed that the liquid ROM as well as the most recent nightly (2 SEP) have been pretty smooth. Nova launcher works great and I don't really see a lot of lag outside the launchers. One thing that kinda brothers me is the lag that is introduced when you enable the nav bar. I don't know exactly what happens behind the scenes (other than it disable the hw keys and enables the soft keys) but it adds a lot of lag. Is there a way to monitor exactly what happens when doing things to your phone? When I use liquid it changes without a reboot but with cm10 I have to manually disable the hw keys so it requires a reboot. Anyone know what's going on with it?
NYConex said:
I have noticed that the liquid ROM as well as the most recent nightly (2 SEP) have been pretty smooth. Nova launcher works great and I don't really see a lot of lag outside the launchers. One thing that kinda brothers me is the lag that is introduced when you enable the nav bar. I don't know exactly what happens behind the scenes (other than it disable the hw keys and enables the soft keys) but it adds a lot of lag. Is there a way to monitor exactly what happens when doing things to your phone? When I use liquid it changes without a reboot but with cm10 I have to manually disable the hw keys so it requires a reboot. Anyone know what's going on with it?
Click to expand...
Click to collapse
Good question. I know there are settings in Developer options that allow you to show GPU status and updates which may provide some insight into GPU/CPU utilization. I don't have an immediate answer for you though. I'll do some research and report back.
With the Liquid ROM, I noticed it to be of the poorest performance as others. Was your experience smooth out of the box or did you have to change the debug.mdcomp.maxlayer from 2 back to 3 first?
**EDIT**
I just tried the Liquid ROM again and realized the debug.mdpcomp.maxlayer setting was set to 2 by default in that ROM and after the changing it, the performance was much better, though about the same as CM10 nightlies.
The mdcomp.maxlayer is always the first thing I check after flashing a ROM. I always set it to 3. But if you go back to liquid try the navbar and you will see what I mean. In not home right now but when I get back I'll mess with it a little.
I'm on the Liquid ROM and I don't notice any lag. So i don't think anything needs fixed...since I dont have the problems u describe.
I use almost all aspects of the Note except little music and games.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Try pulling down the notification drawer. Now sit there and tell me to my face its 60fps. No its not... its really choppy.
Fasty12 said:
Try pulling down the notification drawer. Now sit there and tell me to my face its 60fps. No its not... its really choppy.
Click to expand...
Click to collapse
Lol damn right. I'd say its between 14-21 FPS variably.
Which ROM's have worked the best for you so far?
On mobile, had 2 scroll forever to read topic
SayWhat10 said:
On mobile, had 2 scroll forever to read topic
Click to expand...
Click to collapse
Are you saying that my OP is too long which made you scroll forever or are you saying that the lag in Jelly Bean cause you to scroll forever?
andrawer said:
I'm on the Liquid ROM and I don't notice any lag. So i don't think anything needs fixed...since I dont have the problems u describe.
I use almost all aspects of the Note except little music and games.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Do you use Google Chrome? If so, how would you describe its performance in comparison to Ice Cream Sandwich?
The CM10 nightly has been the smoothest this far. So going by experience heres the rankings ATM.
1) Nightly... Smooth but constant flicker.
2) Liquid
2) Paranoid
3) Aokp
4) manualscout4life's rom.
Fasty12 said:
Try pulling down the notification drawer. Now sit there and tell me to my face its 60fps. No its not... its really choppy.
Click to expand...
Click to collapse
not sure if i understand.
I use my thumb to initiate the notification bar/drawer pulling down and it's immediate and smooth?? Up/down/up/down/up/down...smooth...just tried it. Not even a hint of lag...and that's with 4 notifications waiting for me to do something.
The mentioned lag on jellybean compared to anything previous doesn't come from anything done by Google or issues with software but comes from the lack of hardware acceleration which we don't get to use with jellybean, so our device is not being used to the fullest, is known like previous versions of android when it comes out and ported , is not going to performed like it's supposed to until HWA becomes available. This is the performance drop in fps compared to ICS. Some think because is a newer version of android is going to be better performing out of the box, but that won't happen unless an official version with HWA becomes available or a developer figures out how to implement it into a ROM.
I think JB is amazing and smooth in the little time it has been out.
RoloRacer Paranoid on JellyBean
I agree about the sluggishness of JB at its current state, its normal since we don't have HW acceleration, I'm on Paranoid and flashed Flaps Hot kernel, OC'ed to 1.7Ghz and its performing really well, you should try it out
Sent from my Nexus 7 using xda premium
egomezmorales said:
I agree about the sluggishness of JB at its current state, its normal since we don't have HW acceleration, I'm on Paranoid and flashed Flaps Hot kernel, OC'ed to 1.7Ghz and its performing really well, you should try it out
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
So when will we get hardware acceleration? When jb officially comes out for the note?
roloracer said:
The mentioned lag on jellybean compared to anything previous doesn't come from anything done by Google or issues with software but comes from the lack of hardware acceleration which we don't get to use with jellybean, so our device is not being used to the fullest, is known like previous versions of android when it comes out and ported , is not going to performed like it's supposed to until HWA becomes available. This is the performance drop in fps compared to ICS. Some think because is a newer version of android is going to be better performing out of the box, but that won't happen unless an official version with HWA becomes available or a developer figures out how to implement it into a ROM.
I think JB is amazing and smooth in the little time it has been out.
RoloRacer Paranoid on JellyBean
Click to expand...
Click to collapse
This has been my thought and awareness all along and what I've wanted to work on repairing. Perhaps it's everyone's use of the term "smooth" that is making everything amiss. When people boast that their JB experiences are "incredibly smooth!" and even more specifically "smoother than ICS!" I think they are making very fallible statements because I don't think that my perception of JB being behind ICS in smoothness can be interpreted as just a "difference in opinion or interpretation". It's definitely factual and quantifiable when testing frame rates and comparing them to ICS. Perhaps it's safe to say that "Jelly Bean is remarkably usable right now considering its alpha state", but to say that it is smooth is quite a fallacy. It's really not much better than Gingerbread and Gingerbread lacked HW acceleration altogether.
But if JB lacks hardware acceleration completely, then how is toggling the maxlayer setting and HW overlay setting in developer options clearly affecting performance if HW acceleration isn't even supported at all in the first place? Some sort of acceleration is clearly being enabled for the evident difference in performance to occur.
I am grateful that you recognize JB's current state to be behind and also attribute it to HW acceleration as I initially did. Now we can hopefully gain some momentum on finding the hindrance of bringing HW acceleration to JB!
If there's anything we've learned thus far, it's not to label a ROM officially "smooth" unless you can prove it greater than or equal to stable ICS builds with quantifiable means!
The word "smooth" is beginning to become a profanity for me, which is rather extreme, as there aren't many words I don't say! Lol...
Everyone should read this.
http://www.androidpolice.com/2012/0...roject-butter-how-it-works-and-what-it-added/
Jb runs exceptionally well for me with just the 2 buffers. Are all the animations perfect every single time? No, but it's perfectly usable, and slick enough for my dd. I'm sure it will be sorted in time.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
So far the smoothest jb rom for me has been dagr8's aokp Sept 1 build.
HW overlays are disabled and cpu at stock frequencies. Running Nova 1.2.2 and have fluid home screen transitions and overall smoothness.
If I were to nitpick, the notification bar is the only thing that seems somewhat sluggish but only when I pull it down on the home screen (I am running a live wallpaper.)
No reboots or sleep of deaths so far, loving this rom at the moment.
yollasho said:
Everyone should read this.
http://www.androidpolice.com/2012/0...roject-butter-how-it-works-and-what-it-added/
Jb runs exceptionally well for me with just the 2 buffers. Are all the animations perfect every single time? No, but it's perfectly usable, and slick enough for my dd. I'm sure it will be sorted in time.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Really interesting read, thanks for sharing!
Sent from my Nexus 7 using xda premium
---------- Post added at 01:04 PM ---------- Previous post was at 01:04 PM ----------
Fasty12 said:
So when will we get hardware acceleration? When jb officially comes out for the note?
Click to expand...
Click to collapse
Yep, or that a developer taps on how to get HW acceleration
Sent from my Nexus 7 using xda premium
We've had hardware acceleration.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Yes I am noob, but I would like to learn more, so here I am, long time looker, joining the ranks. I tried searching but all I found was 2-3 year old stuff or non specific answers.
*Edit* CRAP SORRY, saw that questions shouldn't be posted in general. Such a noob move sorry...
I am currently loading old school gaming roms on my phone and soon to be tablet. Years ago I had n64 roms and they were laggy, I figured years later they would run without a hitch, not so much.
Here is what I am running.
Verizon Droid RAZR HD
Micro SD (class 4) 32GB
Snapdragon S4 MSM8960
CPU 1.5 GHz dual-core Krait
GPU Adreno 225
Memory 1GB Dual-channel, 500 MHz LPDDR2 RAM
I am running the standard vanilla rom so it's stock with Verizons bloatware, so I now a bit of lag could rest there.
I am looking to buy a cheaper android tablet that will run Ps1/N64 games without a hitch if possible. I guess what I am wondering is what controls ROM's lag, is it the GPU? Memory? Processor? The ROM/Program itself? I am wondering what hardware (if any) runs these without major issues.
Thanks a ton guys, very happy to help join the ranks. If I missed a thread that covers this please point me in the right direction!
Bump please
Guess I'll try again
Millni6 said:
I guess what I am wondering is what controls ROM's lag, is it the GPU? Memory? Processor? The ROM/Program itself? I am wondering what hardware (if any) runs these without major issues.
Thanks a ton guys, very happy to help join the ranks. If I missed a thread that covers this please point me in the right direction!
Click to expand...
Click to collapse
In all honesty it is a combination of all the factors you mentioned above. Because mobile processors work on a SoC (System on a Chip) design model if you have a weak CPU all the others components on the chip such as RAM and GPU will be weak as well, likewise a strong CPU will most often be coupled with powerful components increasing performance. That being said emulating games is mainly GPU and some CPU intensive of a task. Also the ROM app itself can be a major factor because the games are not being run on there native optimized hardware (Such as the N64) game performance can surfer, a poorly optimized game emulator will lead to poor playback of emulated games. As far as hardware that runs these without issue my Galaxy S3 and Nexus 10 have ran whatever emulator ROM I throw at them. Also keep in mind some game ROMs just don't work or are poorly optimized so no matter what emulator or hardware you have they will have problems with lag.
Sent from my Nexus 10 using xda premium
shimp208 said:
In all honesty it is a combination of all the factors you mentioned above. Because mobile processors work on a SoC (System on a Chip) design model if you have a weak CPU all the others components on the chip such as RAM and GPU will be weak as well, likewise a strong CPU will most often be coupled with powerful components increasing performance. That being said emulating games is mainly GPU and some CPU intensive of a task. Also the ROM app itself can be a major factor because the games are not being run on there native optimized hardware (Such as the N64) game performance can surfer, a poorly optimized game emulator will lead to poor playback of emulated games. As far as hardware that runs these without issue my Galaxy S3 and Nexus 10 have ran whatever emulator ROM I throw at them. Also keep in mind some game ROMs just don't work or are poorly optimized so no matter what emulator or hardware you have they will have problems with lag.
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
Wish I could give you more props for answering that, thanks a ton!!
A few follows ups. Isn't my Razr HD pretty close to the same specs as your S3 (short of yours has 2GB of ram) or now are we talking about the fact that I have the stock bloatware of Verizon?
So something like a Tegra 3 would work perfectly fine correct?
Your last sentence makes me worried. For instance it seems like Golden Eye, Super Smash Bros and Final Final Fantasy 7 all seem to hit small short lag spikes with audio and the N64s hit preformance spikes. It's subtle but enough to be annoying.
Millni6 said:
Wish I could give you more props for answering that, thanks a ton!!
A few follows ups. Isn't my Razr HD pretty close to the same specs as your S3 (short of yours has 2GB of ram) or now are we talking about the fact that I have the stock bloatware of Verizon?
So something like a Tegra 3 would work perfectly fine correct?
Your last sentence makes me worried. For instance it seems like Golden Eye, Super Smash Bros and Final Final Fantasy 7 all seem to hit small short lag spikes with audio and the N64s hit preformance spikes. It's subtle but enough to be annoying.
Click to expand...
Click to collapse
You are correct the Razr HD is very close in specs to the US version of my Galaxy S3 apart from the 2GB or RAM, the 2GB of RAM can help performance but won't cause a massive difference in performance. Additionally the Verizon bloat will chew up resources and depending on what other applications you have running the background can take away resources from the emulator. In general carrier bloatware will slow down the entire device making it seem sluggish. Since you mentioned you were looking to get a cheaper Android tablet to play emulated games on I would definitely check out the Nexus 7, it has good gaming performance for emulated games and gaming performance in general. And like I said previously some games will always just lag or have jumps in the audio and can be annoying unfortunately that part of the problem with playing emulated games.
shimp208 said:
You are correct the Razr HD is very close in specs to the US version of my Galaxy S3 apart from the 2GB or RAM, the 2GB of RAM can help performance but won't cause a massive difference in performance. Additionally the Verizon bloat will chew up resources and depending on what other applications you have running the background can take away resources from the emulator. In general carrier bloatware will slow down the entire device making it seem sluggish. Since you mentioned you were looking to get a cheaper Android tablet to play emulated games on I would definitely check out the Nexus 7, it has good gaming performance for emulated games and gaming performance in general. And like I said previously some games will always just lag or have jumps in the audio and can be annoying unfortunately that part of the problem with playing emulated games.
Click to expand...
Click to collapse
You sir are a pro, I think I am going to buy the Acer Iconia 7 A110, it has a Tergra 3 just like the Nexus and is on sale refurbed at Walmart for 140.0
http://www.walmart.com/ip/Acer-Icon...an-Operating-System-Gray-Refurbished/23662167
Millni6 said:
You sir are a pro, I think I am going to buy the Acer Iconia 10.1 A210, it has a Tergra 3 just like the Nexus and is on sale refurbed at Walmart for 180.
http://www.walmart.com/ip/Acer-Icon...13700444333861315661&affillinktype=10&veh=aff
Click to expand...
Click to collapse
Thank you for the compliment and that is defiantly a good choice, my only piece of advice when buying devices refurbished is ask them if you can try the exact device your gonna buy before you pay for it. I have known several people who have bought refurbished electronics from stores where the guarantee said the device was fully working but when they got home it either didn't power on or something else didn't function properly.
shimp208 said:
Thank you for the compliment and that is defiantly a good choice, my only piece of advice when buying devices refurbished is ask them if you can try the exact device your gonna buy before you pay for it. I have known several people who have bought refurbished electronics from stores where the guarantee said the device was fully working but when they got home it either didn't power on or something else didn't function properly.
Click to expand...
Click to collapse
Yup for sure, they have a 15 day return period, so for whatever reason it does not work, I'll return it. I also saw an Amazon review where they were talking about n64/ps1 roms seems to me like the guy got them to work without any lag issues.