Related
I've only got my galaxy tab 10.1 for a week or so. It ran rather smoothly out of the box. But then it just slowed down. Now it frequently stutters when multitasking, screen rotating orientation, or even just running some applications. Things get particularly worse when live wallpaper is on. I checked in the setting/applications/running services to make sure I didn't run out of RAM (there was often still 300 something MB free).
Did any of you experience that? What would you suggest me doing to resolve this issue? Or is there no solution to this? I do remember everything running fine without lagging when I first used it.
Any sharing or suggestions are much appreciated.
None of the available tablets are capable of running live wallpapers smoothly. I don't have any problem otherwise though. Try doing a factory reset.
thanks. i probably should.
The Tegra 2 chip is not capable of running live wallpapers smoothly due to its crippled 32bit memory interface. It simply does not have enough memory bandwidth to process. Tegra 2 was SUPPOSED to have dual channel memory but Nvidia decided to ditch the second 32bit channel (which would have greatly improved performance under live wallpapers and games) to save power
This is the same reason why you notice your tablet slowing down after using it for a little while. Once system memory starts to get filled Android OS needs to shuffle around memory, remove apps from memory to make room for newly launched apps, ect. This all takes alot of memory bandwidth and with only a 32bit wide channel you can see why your tablet slows down. Especially when doing anything visual like swiping home screens across.
Most people dont know that Tegra 2 is an old chipset. Its been around for over a year now. I was blown away and shocked when I found that Nvidia used a crippled 32bit single channel memory interface. Not sure what they were thinking
I cant wait for TIs dual-core SoC, they run dual channel memory and have a GPU many times faster that Tegra 2. If you want to run live wallpapers its best to skip any Tegra 2 device and wait for a unit with TIs SoC later this summer or a Tegra 3 which will be in tablets in 5 months.
Many people feel their tablets and phones perform a lot better (at least when on the home screens) when you use a third-party launcher like ADW Launcher Ex or Launcher Pro.
kytz said:
Many people feel their tablets and phones perform a lot better (at least when on the home screens) when you use a third-party launcher like ADW Launcher Ex or Launcher Pro.
Click to expand...
Click to collapse
third-party launcher will do nothing to improve performance and has absolutely nothing to do with live wallpapers or the performance of the unit.
magic smoke
I re flashed the tab 10.1 back to the 3.01 OS and It runs live wall papers great. No shuddering and my applications load quickly. I Do use android assistant and shut down any programs I don't use. Gonna try the new kernel.
so 3rd party launchers are bad... why? also, a new kernel for the tab? already?
beaker2007 said:
so 3rd party launchers are bad... why? also, a new kernel for the tab? already?
Click to expand...
Click to collapse
3rd party launchers are just apps. There is nothing wrong with them but they certainly don't improve performance of any aspect of the device.
Any upcoming devices that will have the TI dual core cpu in it? Or will Tegra 3 be far superior by that time?
ericc191 said:
Any upcoming devices that will have the TI dual core cpu in it? Or will Tegra 3 be far superior by that time?
Click to expand...
Click to collapse
Archos is launching a tablet with the 1.5ghz TI dual core chip really soon. Itll be much faster than tegra 2 and have 3 times the gpu performance. The gpu performance on the tegra 2 is just plain awful even for a 1st gen device.
Thanks 5thElement for your detailed information. Now I have a much better understanding of how this problem came to be. For now though, I couldn't stand the lagging behind any more and reset the tab to factory setting. Smooth all around once again. Will have to re-purchase all the apps I paid for though. This part sucks!
Actually just found out u need not repurchase anything. Google sync remembers everything and does a full recovery of all settings and apps for u. Kudos to google!
5thElement said:
If you want to run live wallpapers its best to skip any Tegra 2 device and wait for a unit with TIs SoC later this summer or a Tegra 3 which will be in tablets in 5 months.
Click to expand...
Click to collapse
and those tablets are...?
5thElement said:
Archos is launching a tablet with the 1.5ghz TI dual core chip really soon. Itll be much faster than tegra 2 and have 3 times the gpu performance. The gpu performance on the tegra 2 is just plain awful even for a 1st gen device.
Click to expand...
Click to collapse
They will indeed be more than likely faster than Tegra 2 but for the record the TI OMAP 4460 uses Imagination Technologies PowerVR SGX 540 GPUs which are the same GPUs used in the Samsung Galaxy S phones (not the new SIIs). That isnt a massive difference between Gefore ULP.
Now, the TIs OMAP 5 chipset does use a shock and awesome GPU that is dangerously similar to the iPads GPU which is from ITs PowerVR SGX 544 MP line and those are a true dual core GPU. Anandtech has some GPU benchmarks covering this....
MrSewerPickle said:
They will indeed be more than likely faster than Tegra 2 but for the record the TI OMAP 4460 uses Imagination Technologies PowerVR SGX 540 GPUs which are the same GPUs used in the Samsung Galaxy S phones (not the new SIIs). That isnt a massive difference between Gefore ULP.
Now, the TIs OMAP 5 chipset does use a shock and awesome GPU that is dangerously similar to the iPads GPU which is from ITs PowerVR SGX 544 MP line and those are a true dual core GPU. Anandtech has some GPU benchmarks covering this....
Click to expand...
Click to collapse
The PowerVR 540 will be significantly faster than tegra 2 not only because it has a unified architecture but because TIs SoC will have dual channel memory unlike the crippled single channel memory the Tegra 2 has. The memory bandwidth on the tegra 2 is pathetic and it has to be shared with video which is seriously crippling for the Tegra 2 and its poor performance sticks out like a sore thumb as you can see when you try to run live wallpapers.
switched to launcher pro live wallpapers run fine
5thElement said:
third-party launcher will do nothing to improve performance and has absolutely nothing to do with live wallpapers or the performance of the unit.
Click to expand...
Click to collapse
You are wrong my live wp work fine no stutters now. Thanks for the single channel knowledge.Although launcher pro seemed to fix my issue
5thElement said:
third-party launcher will do nothing to improve performance and has absolutely nothing to do with live wallpapers or the performance of the unit.
Click to expand...
Click to collapse
On MY Tab, Adw EX outperforms the stock launcher by leaps and bounds. I don't know what they did programatically, but it consistently moves smoother, faster than the stock launcher.
Live wallpapers are still problematic, but I do feel the presentation of icons/widgets is better. Not all launchers are created equal... including the default one.
I've just received the Galaxy Tab 10.1 and I already own a Galaxy S2 phone. I was very disappointed with the stutter and lag in the GT 10.1 compared to the GS2. In fact I was sort of amazed because I hadn't seen any reference to the poor video and livewallpaper performance when looking at reviews of the tab.
I've tried resetting to factory defaults after installing the latest firmware update from Samsung and I simply can't use a livewallpaper - the slowdown in performance of the tablet is quite noticable.
I've got videos on my GS2 that play fine but on the Galaxy Tab, they just stutter (and I'm not using a livewallpaper). I've tried all sorts of video player apps as well.
I wished I'd known that the Tegra 2 would not be capable of the sorts of things my GS2 is. It's just weird that I hadn't seen any reference to this before.
As suggested, try using a different launcher. While it doesn't change the hardware, most users find that the stock launcher is inherently laggy. ADW for example also has user adjustable tweaks which can improve perceived speed.
As for live wallpapers, some are worse than others of course. Experiment a bit. Also check widgets you may have on screen which could be causing slow downs. Things like circle launcher and updating social apps are known to cause slowness.
I am running Bonsai ROM with various tweaks, overclocked at 1.4gHz and can run live wallpapers smoothly with no problems.
Edit: You should also be able to run video smoothly. Using stock player or Rockplayer, etc. I regularly watch movies and videos, as well as Netflix with no issues. Of course video type, size, etc will make a difference, but even non-optimized movies seem smooth for me.
I was trying to load Bejeweled blitz from facebooks desktop site and it looks choppy and unsmoothed. I tried it on my friends sg2 and its smooth as butter.
Making me wonder if the sg2 is much better than the prime? I have a g2x and its no where near the speed of the sg2 and I really thought the prime was able to load flash much better but not the case.
Nvidia always!
I cant reproduce it with flash games, but my experience so far is that the Galaxy S2 is MUCH smoother than the Prime in EVERY respect (with the exception of hardware video decoding, but hey...).
HOWEVER I definitely hope that is because of Honeycomb rather than Tegra 3. But I'll have to wait another 2 1/2 weeks for ICS to decide that...
The bizarre thing is that from pure specs, even the Tegra 2 is a faster/more powerful SoC than the Exynos in the SGS2, but it's lacking the NEOS which the SGS2 has. Also remember the SGS2 has to drive a much smaller screen. Also, flash can probably not use the quadcore (?) well.
So far I have to say in general smoothness Tegra 3/HC has been very underwhelming. And the 3 week delay of ICS in Germany does not bode well.
I am on ICS and its not that much of a difference in resolution for it to lag so much. All I can think of is tegra doesn't do well with flash.
Nvidia always!
Wow so I installed chainfire 3d on my g2x and installed the nvidia plug in and guess what? Seems as fast as the sg2. I take it flash just isn't optimized for nvidia. I am gonna try this on the prime and see what the results are
Nvidia always!
Alot smoother and just with chainfire. I wonder how or why?
Nvidia always!
A member of the Android team posted this about smoothness comparisons between the GS2 and the Galaxy Nexus. I think this may apply to the Prime as well.
"Some have raised points along the lines of Samsung Galaxy S2 phones already having a smoother UI and indicating that they are doing something different vs. the Galaxy Nexus. When comparing individual devices though you really need to look at all of the factors. For example, the S2's screen is 480x800 vs. the Galaxy Nexus at 720x1280. If the Nexus S could already do 60fps for simple UIs on its 480x800, the CPU in the S2's is even better off.
The real important difference between these two screens is just that the Galaxy Nexus has 2.4x as many pixels that need to be drawn as the S2. This means that to achieve the same efficiency at drawing the screen, you need a CPU that can run a single core at 2.4x the speed (and rendering a UI for a single app is essentially not parallelizable, so multiple cores isn't going to save you).
This is where hardware accelerated rendering really becomes important: as the number of pixels goes up, GPUs can generally scale much better to handle them, since they are more specialized at their task. In fact this was the primary incentive for implementing hardware accelerated drawing in Android -- at 720x1280 we are well beyond the point where current ARM CPUs can provide 60fps. (And this is a reason to be careful about making comparisons between the Galaxy Nexus and other devices like the S2 -- if you are running third party apps, there is a good chance today that the app is not enabling hardware acceleration, so your comparison is doing CPU rendering on the Galaxy Nexus which means you almost certainly aren't going to get 60fps out of it, because it needs to hit 2.4x as many pixels as the S2 does.)"
A link to the rest of the article is in my sig.
Yeah but why does it work as smooth when applying chainfire 3d? I mean its a world of difference there on both my devices.
Besides the prime has a quad core with a much powerful gpu than the s2
Nvidia always!
Try going to blitz on Facebook or g+ and play without chainfire and then with.
Nvidia always!
Got an s3 now and flash is awesome
Sent from my GT-I9300 using XDA Premium HD app
As the topic says which is better?
Sent from my GT-S5830 using xda premium
Bump
Sent from my GT-S5830 using xda premium
mali 400...
I havent tested mali, but the downside with tegra 2 is that they say that nvidia haven't released the source code, leaving developers fumbling in darkness. I have an LG Optimus 2X with tegra 2 gpu, and I really like the smoothness and quickness of my graphics. I haven't seen any graphical problems yet, though I have played lots of demanding games.
You could check these out: http://www.anandtech.com/show/4177/samsungs-galaxy-s-ii-preliminary-performance-mali400-benchmarked and http://www.differencebetween.com/difference-between-mali-400mp-gpu-and-vs-tegra-2/.
Theonew said:
You could check these out: http://www.anandtech.com/show/4177/samsungs-galaxy-s-ii-preliminary-performance-mali400-benchmarked and http://www.differencebetween.com/difference-between-mali-400mp-gpu-and-vs-tegra-2/.
Click to expand...
Click to collapse
Thx bro.
Sent From My SGA via Xda Premium App
That was Anandtech Feb 2011 benchmark.
I admit those scores also misled me for the longest time, which is what brought me to purchase a Tegra 2 tablet. Then after a while, seeing that there is little gaming support for Tegra 2 (couldn't even run Dead Space, and Real Racing 2 ran like a dog), I fell out of that wagon pretty fast and got an iPad 2, which ran basically ANYTHING, and freaking hell smoothly I might add.
Now I got to play with a friend's Galaxy that comes with a Mali 400MP. What amazes me is that it can run NOVA 3 relatively well, whereas Tegra 2 version can't even show you any shader effects, that is, if you get it to run at all. So after some more Googling, I found another benchmark from Anandtech that claims a totally different thing. Have yourself a look.
http://www.anandtech.com/show/4686/samsung-galaxy-s-2-international-review-the-best-redefined/17
Now if you base your performance on the first 2 graphs, of course you'd think the Tegra 2 is so much faster than Mali 400MP. But hang on, scroll down a little further, and you'll see how wrong you are. For on every graph that follows, Mali 400MP freaking hands the other players their asses! All except Flash, which it ties with Tegra 2.
i think they are performing close together, any rumor? no i dont think so,
These Benchmarks are only theoretical values.
I'm running my Sony Xperia P which contains a cutted Mali400 with Chainfire3d fired up with Nvidia Plugin so i'm able to play the Tegra 2 Games and they are smooth like Hell even with 4xMSAA.
So Benchmarks are one Hand but real feel Values are the better one Solution to mention about Performance
(Xperia P has only 1Core Mali400MP the SGSII has 4Core Mali400MP4)
And how does that contradict what I said about Tegra 2 vs Mali 400MP? Mali 400MP > Tegra 2, totally contrary to what a lot of people have asserted on this thread:
http://forum.xda-developers.com/showthread.php?t=977412
And if you're a Tegra fan looking for more aggravation, just look up "tegra 2 NOVA3" and watch a few videos, and watch a few videos of how Mali 400 runs the same game.
Tegra 2
But mali400 have support more than tegra 2 video codecs
I noticed some games are choppy at some parts. Is this because the Quad Core and Mali 400 aren't as strong as said to be, or is it due to poor optimization. I believe it is poor optimization and if it is do you think they will optimize games soon to take advantage of the chip set?
temple run brave did lag some
Sent from my GT-I9300 using Tapatalk 2
Last summer, I decided to buy a Nexus 7 for using it mainly as an ebook reader. It's perfect for that with its very sharp 1280x800 screen. It was my first Android device and I love this little tablet.
I'm a fan of retro gaming and I installed emulators on every device I have: Pocket PC, Xbox, PSP Go, iPhone, iPad3, PS3. So I discovered that the Android platform was one of the most active community for emulation fans like me and I bought many of them, and all those made by Robert Broglia (.EMU series). They were running great on the N7 but I found that 16GB was too small, as was the screen.
I waited and waited until the 32 GB Nexus 10 became available here in Canada and bought it soon after (10 days ago). With its A15 cores, I was expecting the N10 to be a great device for emulation but I am now a little disapointed. When buying the N10, I expected everything to run faster than on the N7 by a noticeable margin.
Many emulators run slower on the N10 than on the N7. MAME4Ddroid and MAME4Droid reloaded are no longer completely smooth with more demanding ROMs, Omega 500, Colleen, UAE4droid and SToid are slower and some others needed much more tweaking than on the N7. I'm a little extreme on accuracy of emulation and I like everything to be as close to the real thing as possible. A solid 60 fps for me is a must (or 50 fps for PAL machines).
On the other side, there are other emus that ran very well: the .EMU series and RetroArch for example. These emulators are much more polished than the average quick port and they run without a flaw. They're great on the 10-inch screen and I enjoy them very much. The CPU intensive emulators (Mupen64Plus AE and FPSE) gained some speed but less that I anticipated.
So is this because of the monster Nexus 10's 2560x1600 resolution? Or is it because of limited memory bandwith? Maybe some emulators are not tweaked for the N10 yet. I wish some emulators had the option to set a lower resolution for rendering and then upscale the output. I think that many Android apps just try to push the frames to the native resolution without checking first if there is a faster way.
The N7 has a lower clocked 4 core CPU but has only 1/4 the resolution. I think that it's a more balanced device that the N10 which may have a faster dual core CPU but too much pixels to push. It's much like the iPad3 who was twice as fast as the iPad2 but had a 4x increase in resolution.
I am now considering going for a custom ROM on the N10 but I wonder if I will see an increase in emulation speed. Maybe those of you who did the jump can tell me. I'm thinking about AOKP maybe.
Any suggestion on that would be appreciated, thanks!
The emulators just need to be tweaked a bit to better perform on the completely different processor architecture. Really our processor is far more powerful than the Nexus 7 so the emulators should run faster. I too am a fan of the old games, and I play Super Nintendo and Game Boy Advance (and some Color) games quite often. I find performance to be perfect with no issues at all, but then again those arent exactly "demanding" emulators.
We do not have any sort of memory bandwidth limitation on the Nexus 10. The tablet has been designed to give the full needed 12.8 GB/s of memory bandwidth that is required for 2560x1600 resolution.
EniGmA1987 said:
The emulators just need to be tweaked a bit to better perform on the completely different processor architecture. Really our processor is far more powerful than the Nexus 7 so the emulators should run faster. I too am a fan of the old games, and I play Super Nintendo and Game Boy Advance (and some Color) games quite often. I find performance to be perfect with no issues at all, but then again those arent exactly "demanding" emulators.
We do not have any sort of memory bandwidth limitation on the Nexus 10. The tablet has been designed to give the full needed 12.8 GB/s of memory bandwidth that is required for 2560x1600 resolution.
Click to expand...
Click to collapse
Hmm, if no memory bandwidth limitation exists on the N10, wouldn't I be able to run GTA 3 at 100% screen resolution and not have significantly lower FPS, as compared to 50% resolution?
Even Beat Hazard Ultra seems to be a bit laggy on the N10. When I inquired about it to the developer, he said:
Having to render to that size of screen [2560x1600] will slow the game down. It’s called being ‘fill rate bound’. Even for a good processor it's a lot of work as the game uses quite a lot of overdraw.
The solution is to draw everything to a smaller screen (say half at 1280x800) and then stretch the final image to fill the screen.
Click to expand...
Click to collapse
A sad true my nexus 10 get dam hot and i have to play games at 1.4 or 1.2 that sux
Sent from my XT925 using xda app-developers app
espionage724 said:
Hmm, if no memory bandwidth limitation exists on the N10, wouldn't I be able to run GTA 3 at 100% screen resolution and not have significantly lower FPS, as compared to 50% resolution?
Even Beat Hazard Ultra seems to be a bit laggy on the N10. When I inquired about it to the developer, he said:
Click to expand...
Click to collapse
But fillrate isnt memory bandwidth. We need both more MHz and more raster operations to get higher fill rate of pixels per second. We can overclock the GPU to get the MHz, and that will help, but we have to find a way to solve the higher heat output too from that. More ROP's are impossible as it is a hardware design for how many we have. If we ever get to overclock up to around 750 MHz then we should see a 30-40% improvement in fill rate. At that point we may have memory bandwidth problems, but we wont know for sure until we get there. But the 12.8GB/s of bandwidth that we currently have is enough to support 2560x1600 resolution at our current GPU power. Our Nexus 10 also has the highest fillrate of any Android phone or tablet to date, about 1.4 Mtexel/s. And if we have memory bandwidth limitations, then we would see no improvement at all from the current overclock we do have up to 612-620MHz because the speed wouldnt be where the bottleneck is. Yet we can clearly see in benchmarks and real gaming that we get FPS increases with higher MHz, thus our current problem is the fillrate and not the memory bandwidth.
Also, the solution is not to render the game at half the resolution as that is a band-aid on the real problem. If the developer of a game would code the game properly we wouldnt have this problem, or if they dont feel like doing that then they should at least stop trying to put more into the game than their un-optimized, lazy project is capable of running nicely.
espionage724 said:
Hmm, if no memory bandwidth limitation exists on the N10, wouldn't I be able to run GTA 3 at 100% screen resolution and not have significantly lower FPS, as compared to 50% resolution?
Even Beat Hazard Ultra seems to be a bit laggy on the N10. When I inquired about it to the developer, he said:
Click to expand...
Click to collapse
With that logic you could buy any video card for a PC and it would run any game at the resolution the video card supports. That isn't the case because rendering involves more than just memory fill rate. There are textures, polygons, multiple rendering passes, filtering, it goes on and on. As EniGmA1987 mentioned nothing has been optimized to take advantage of this hardware yet, developers were literally crossing their fingers hoping their games would run 'as is'. thankfully the A15 cpu cores in the exynos will be used in the tegra 4 as well so we can look forward to the CPU optimizations soon which will definitely help.
Emulators are more cpu intensive than anything else, give it a little time and you won't have any problems with your old school games. Run the new 3DMark bench to see what this tablet can do, it runs native resolution and its not even fully optimized for this architecture yet.
2560*1600*4*60/1024/1024 = 937,3 MB/s for a 60 fps game at 32-bit depth. Most emulators don't use 3D functions so fillrate, rendering, overdraw won't be a factor. Most emulators are single-threaded (correct me if I'm wrong) and the A15 should shine in this particular situation and even more so in multi-threaded scenarios. With its out-of-order pipeline and greatly enhanced efficiency it should be perfectly suited for the job.
We have the fillrate, we have enough CPU power and I'm still wondering why simple app like emulators aren't much faster than that. Is it Android? Is it the Dalvik VM? Or is it because some emulators need to be written in native code instead of using Java VM? I'm not a developer and I have only minimal knowledge in this department. I can only speculate but I'm curious enough about it that I started googling around to find why.
Lodovik said:
2560*1600*4*60/1024/1024 = 937,3 MB/s for a 60 fps game at 32-bit depth
Click to expand...
Click to collapse
Just curious but what is that calculation supposed to be? total bandwidth needed? Cause I don't see your bit depth in there, unless the 4 is supposed to be that? If that is true than you are calculating on 4-bit color depth?
And then the result would just be bandwidth required for pixel data to memory wouldnt it? It wouldnt include texture data in and out of memory and other special functions like post processing.
2560*1600 = number of pixels on the screen
4 = bytes / pixels for 32-bits depth
60 = frames / second
/1024/1024 = divide twice to get the result in MB
Actually, I made a typo the result is 937,5 MB/s or 0.92 GB/s. This is just a rough estimate to get an idea of what is needed at this resolution just to push the all pixels on the screen in flat 2D at 60 fps, assuming that emulators don't use accelerated functions.
My point was that with 12.8 GB/s of memory bandwith, we should have more than enough even if this estimate isn't very accurate.
Thanks for the explanation
If there really were a memory bandwidth limitation the newer Trinity kernels and newest KTManta should help. In addition to the higher GPU speed they both allow (KTManta up to 720MHz) both ROM's have increased memory speeds which increase memory bandwidth to 13.8GB/s, up from 12.8 on stock.
Thanks for the info. There's so many configuration options available for the Nexus 10. I really enjoy having all those possibilities.
EniGmA1987 said:
If there really were a memory bandwidth limitation the newer Trinity kernels and newest KTManta should help. In addition to the higher GPU speed they both allow (KTManta up to 720MHz) both ROM's have increased memory speeds which increase memory bandwidth to 13.8GB/s, up from 12.8 on stock.
Click to expand...
Click to collapse
=Lodovik;40030*1600*4*60/1024/1024 = 937,3 MB/s for a 60 fps game at 32-bit depth. Most emulators don't use 3D functions so fillrate, rendering, overdraw won't be a factor. Most emulators are single-threaded (correct me if I'm wrong) and the A15 should shine in this particular situation and even more so in multi-threaded scenarios. With its out-of-order pipeline and greatly enhanced efficiency it should be perfectly suited for the job.
We have the fillrate, we have enough CPU power and I'm still wondering why simple app like emulators aren't much faster than that. Is it Android? Is it the Dalvik VM? Or is it because some emulators need to be written in native code instead of using Java VM? I'm not a developer and I have only minimal knowledge in this department. I can only speculate but I'm curious enough about it that I started googling around to find why.
Click to expand...
Click to collapse
You are taking what I said out of context. I was responding to someone else, thus the "quote" above my post.
Since you posted I loaded up some Super Nintendo, N64, and PlayStation games on my n10 without any issues. It may just be your setup. There are a lot of tweaks out there that could easily increase performance. One great and very simple one is enabling 2D GPU rendering which is in developer options. Just do some searching. GPU Overclocking won't help much, as you said above your games are only 2D. I am sure you can get them running just fine.