While the browser performance in Honeycomb seems to have been improved, the Xoom's browser still struggles to render some pages. The main forum index page at xda-developers is a perfect example:
http://forum.xda-developers.com/index.php
That page kills the usability of my Xoom's stock browser -- scrolling on that page is quite unpleasant.
But of course, the same page renders buttery smooth on an iOS device. So why is that? 2D GPU acceleration is apparently enabled in Honeycomb, so why does a dual-core tegra 2 device with a gig of ram have such a hell of a time rendering web pages? Has google commented on this? Do any roms or tweaks address this issue?
Go down to the bottom left of the page and select xda classic you will see a world of a differance with scrolling and typing.
The honeycomb browser has poor standards implementation. There is a good review below.
http://www.sencha.com/blog/motorola-xoom-the-html5-developer-scorecard/
Related
Greetings.
I've been intrigued by the true benefits of overclocking one's phone. It's hard to tell what the differences are by just looking at Quadrant scores. They don't translate very well to user experience.
Therefore I've made a video investigating the qualititive effects of OC-ing your Vision. This is shown in terms of webpage handling (scrolling and pinch zooming) and handling of a PlayStation 1 emulator.
My methodology is to scroll through PhoneDog.com first at 800MHz and then at 1.5GHz. PhoneDog.com was preloaded on the browser. It was chosen so that comparison can be made with phones that have been reviewed by PhoneDog.
Then I fired up FPSe playing Tekken 3. First was again at 800MHz and then followed by 1.5GHz. The FPS for the 2 clockspeeds were noted.
Then I tried an intermediate OC at 1.1GHz. Browser and emulator performance were noted as well.
The results were as expected and after overclocking the overall performance of the phone did increase by some margin.
This video is for people who have not tried rooting yet and is curious about the true difference before and after overclocking the phone.
Comments appreciated. I've made some other videos as well. Do check out my channel for more of my work.
Note: I'm as noob as everyone else. I just had a lot of time on my hands to be making this video.
Someone please confirm this, I find it hard to believe it doesn't on the camera app, being that everything there is so buttery smooth from pinch to zooming from the little boxes popping up when clicking share, or delete.
T-Mobile G2 1.42 GHZ
Yep, it does
Sent from my HTC Vision using XDA App
Yep, it does
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Hahaha I knew it, and wow its sad that google doesn't allow gpu acceleration throughout the whole device not just the cam app, and these phones have very powerfull gpu so I don't understand why this delay in adding gpu acceleration, the first generation iphone was buttery smooth due to GPU accel and the hardware was not nearly as capable as the G2 or any high end android device. And honeycomb finally supports gpu acceleration throughout the whole device and its awesome, no stutters when pinch and zooming everything is just as buttery smooth as the ipad! Check out the comparison between the xoom and the ipad they go hand in hand with smoothness.
The cam app is the most delightful place to be @ in the G2, you will always find pinch to zooming the pics lmao wishing the browser pinch to zoom was just as smooth as the cam pinch to zoom
I really hope ice cream sandwich allows gpu acceleration throughout the whole device, we been waiting enough for this already.
T-Mobile G2 1.42 GHZ
If you want a hardware-accelerated browser, try Opera Mobile it's very fast.
Sent from my HTC Vision using XDA App
androidfeen809 said:
the first generation iphone was buttery smooth due to GPU accel and the hardware was not nearly as capable as the G2 or any high end android device.
Click to expand...
Click to collapse
All iPhones before iPhone 4 have really low resolution (320 x 480), which obviously helps with faster graphics rendering.
Anyone who uses twitter should download the plume app from the market. I rarely use twitter bit this app makes me be on twitter lol. Its the gpu accelerated twitter very great smoothness there, finally after honeycomb google is focusing on the gpu use on amdroid devices.
T-Mobile G2 1.42 GHZ
and every other Tablet for good measure... so much for an additional $100
http://hothardware.com/Reviews/Samsung-Galaxy-Tab-101-Review-Android-31-Tablet/?page=4
To be fair, they did mention the fact that the Galaxy Tab is running HC 3.0
Real World Performance is What Really Matters But This is Still Surprising. Asus just needs to fix typing and browser lags and all is gravy for me. Oh Also Samsung 10.1 Doesn't have 3.1 yet so that might boost its quadrant scores.
HorsexD said:
Real World Performance is What Really Matters But This is Still Surprising. Asus just needs to fix typing and browser lags and all is gravy for me. Oh Also Samsung 10.1 Doesn't have 3.1 yet so that might boost its quadrant scores.
Click to expand...
Click to collapse
Pretty sure the 10.1 is now shipping with (or being upgraded to) 3.1
http://www.infosyncworld.com/reviews/internet-tablets/samsung-galaxy-tab-10.1-review/12086.html
Nice results for the G-Tablet. Not bad for a $250 tablet.
S4F4M said:
To be fair, they did mention the fact that the Galaxy Tab is running HC 3.0
Click to expand...
Click to collapse
That's not fair to mention at all, since TF101 ALL benchmarks went down not up after 3.1 update.
I hope someone can figure out why it's getting such poor performance results. What makes this really odd is that most reviews site its snappy performance when web browsing and its ability to play back 1080p movies very well.
nothing odd about it - simulated benchmarks are useless because they can never properly simulate real world usage or properly simulate the differences in hardware and software on the devices being benchmarked.
For instance 1080p video playback has absolutely nothing todo with the instructions being simulated in benchmarks like these, videoplayback are handled by a hardware codec and the abilities of this codec has nothing todo with the rest of the cpu, or weather the cpu are 600mhz or 1.2ghz, single core or dual core etc.
Quadrant scores etc. tells nothing about how optimized the software on the device is - like how smooth the device feels in normal operations. Example, the same device will score the same quadrant score no matter which launcher is used, and no matter how smooth or how laggy this launcher operates when swiping homescreens. It will score the same result no matter how laggy a device may feel because of wrong memory management configuration and so on, it will score the same result no matter if the device has 512mb or 1gb ram, despite the device with 1gb will feel smoother in operations because it can store more open applications in ram. Etc. etc.
Quadrant score shows nothing except how good a device can run Quadrant, and this may differ depending on how Quadrant are optimised for the specific chipset/cpu.
It wont show anything else, it wont show how good the device can run specific games because this depends on the individual game and how this is optimised for the specific cpu/gpu, it wont show how smooth the device feels in general operation handling the gui or different applications because this depends on so many other things which cant be simulated, it wont show how good it can handle different video because this also depends on other things which cant be simulated.
Quadrant scores and other test scores like it are good for only one thing
They are tools for "big boys" that needs to compare "**** sizes"
- but since you cant go around showing pictures of your ****, you can allways show a screenshot of a quadrant score and go "mines bigger than yours"
spawndk said:
Quadrant scores and other test scores like it are good for only one thing
They are tools for "big boys" that needs to compare "**** sizes"
- but since you cant go around showing pictures of your ****, you can allways show a screenshot of a quadrant score and go "mines bigger than yours"
Click to expand...
Click to collapse
Great description of Quadrant. There's a t-shirt in there somewhere
Sent from my Transformer TF101 using XDA Premium App
spawndk said:
nothing odd about it - simulated benchmarks are useless because they can never properly simulate real world usage or properly simulate the differences in hardware and software on the devices being benchmarked.
For instance 1080p video playback has absolutely nothing todo with the instructions being simulated in benchmarks like these, videoplayback are handled by a hardware codec and the abilities of this codec has nothing todo with the rest of the cpu, or weather the cpu are 600mhz or 1.2ghz, single core or dual core etc.
Quadrant scores etc. tells nothing about how optimized the software on the device is - like how smooth the device feels in normal operations. Example, the same device will score the same quadrant score no matter which launcher is used, and no matter how smooth or how laggy this launcher operates when swiping homescreens. It will score the same result no matter how laggy a device may feel because of wrong memory management configuration and so on, it will score the same result no matter if the device has 512mb or 1gb ram, despite the device with 1gb will feel smoother in operations because it can store more open applications in ram. Etc. etc.
Quadrant score shows nothing except how good a device can run Quadrant, and this may differ depending on how Quadrant are optimised for the specific chipset/cpu.
It wont show anything else, it wont show how good the device can run specific games because this depends on the individual game and how this is optimised for the specific cpu/gpu, it wont show how smooth the device feels in general operation handling the gui or different applications because this depends on so many other things which cant be simulated, it wont show how good it can handle different video because this also depends on other things which cant be simulated.
Quadrant scores and other test scores like it are good for only one thing
They are tools for "big boys" that needs to compare "**** sizes"
- but since you cant go around showing pictures of your ****, you can allways show a screenshot of a quadrant score and go "mines bigger than yours"
Click to expand...
Click to collapse
Quadrant Envy?
Honestly the benchmarks results are the more relevant part of that review. Obviously that review was either paid for or the writer is devout samsung fanboy. I'm not going to to defend the benchmarks(which do have value), however to write a review where the reviewed device loses is almost every category and then summarize that the benchamrks you yourself chose to run are meaningless and that the reviewed device is obviously superior to the other devices is amazing. Rings of many ipad reviews.
Hi everyone, I have heard a lot of different story about forced gpu rendering.
I have decided to tried it out myself, after about roughly 6 hours of use (not a lot i know!), I feel that gpu rendering is making my scrolling slightly, only VERY SLIGHTLY smoother (mainly in landscape mode, esp scrolling between pages wiht **** load of widgets)
Thats a good sign to me, personally I am ok with it taking more ram. However I am concerned about the power consumption.
I have heard a lot of different version of story about it:
GPU takes more power.
GPU is more efficient, thus taking less power.
Power consumption remain the same.
I am a little confused here.....anyone know for sure?
Android already uses GPU acceleration throughout the entire system and default apps. Turning on that option forces GPU acceleration is apps they have not implemented it, like the very own XDA app. You'll notice huge increases on performance in apps like this one, Bible, Facebook, Twitter. Basically any app that has not implemented GPU acceleration.
Sent from my Nexus 7 using xda app-developers app
Also in relation to this, can anyone explain to me what the 'disable hw overlays' setting would achieve?
Good or Bad?
I am running a trial version of ezpdf on the Note 2 LTE. The speed is faster than that of last year but I would be happier if it were faster especially the rendering when I zoom in and out. Given that the Note 3 LTE has a faster processor, will I see an increase in performance running ezpdf and reading the same pdf file on the Note 3?
hajime_android said:
I am running a trial version of ezpdf on the Note 2 LTE. The speed is faster than that of last year but I would be happier if it were faster especially the rendering when I zoom in and out. Given that the Note 3 LTE has a faster processor, will I see an increase in performance running ezpdf and reading the same pdf file on the Note 3?
Click to expand...
Click to collapse
Without any reference from your side I don't know what to look for. Just "faster" is very subjective. During installation ezPDF (latest version) also installs an example document (" A 2013 Planner"). Zooming (pinching) in and out with this document is almost instant, no lag, like zooming in and out of a webpage. Swiping through the 3 pages is also almost instant, without any lag.
I tried a graphically intensive pdf (about 80 pages) created from PowerPoint. Rendering of words when zooming in and out takes time. Moreover, the app crashed 2-3 times. Don't know if it is the problem with the app or with the file.
hajime_android said:
I tried a graphically intensive pdf (about 80 pages) created from PowerPoint. Rendering of words when zooming in and out takes time. Moreover, the app crashed 2-3 times. Don't know if it is the problem with the app or with the file.
Click to expand...
Click to collapse
If you absolutely want to know, just try another graphical intensive pdf file from the web and share the link so I can try it on my note 3.