I thought that ics had a hardware accelerated browser.
Dianne Hackborn said:When people have historically compared web browser scrolling between Android and iOS, most of the differences they are seeing are not due to hardware accelerated drawing. Originally Android went a different route for its web page rendering and made different compromises: the web page is turned in to a display list, which is continually rendered to the screen, instead of using tiles. This has the benefit that scrolling and zooming never have artifacts of tiles that haven’t yet been drawn. Its downside is that as the graphics on the web page get more complicated to draw the frame rate goes down. As of Android 3.0, the browser now uses tiles, so it can maintain a consistent frame rate as you scroll or zoom, with the negative of having artifacts when newly needed tiles can’t be rendered quickly enough. The tiles themselves are rendered in software, which I believe is the case for iOS as well. (And this tile-based approach could be used prior to 3.0 without hardware accelerated drawing; as mentioned previously, the Nexus S CPU can easily draw the tiles to the window at 60fps.)
I dropped my T-Mobile Android G1 on the concrete earlier this and it's been playing and so today I went and got it replaced with Galaxy S II. I should have done some more research but I was desperate for a replacement, the girl and Carphone Warehouse told me this phone is the best on the market. Judging by the size of this thread I'm guessing she's not far wrong?
I swear I am having the worst luck with phones. The first had a problem with the screen, and the 3rd has nothing wrong with the screen, but this:
Anyone got a clue what the hell is wrong with this 1?![]()
Prob nothing as mine does the same, why would you need to mess with that anyway?
I was doing the tests to see if there was any problems with it, and that was something none of the previous phones did. Just confused what the hell it is and if there is a problem with it or not.
I don't see a problem?
Think its to do with the noise as its a screen test
it's not just a screen test. that's why it's called "receiver (white)", just like the vibration test is called "vibration(black)". It tests a receiver but i couldn't tell you which one or in what capacity.
I would suggest not messing around in test menu and dev apps unless you know what those tests are supposed to be doing.
no.The first makes a really loud noise when the test starts, the other makes no sound at all. Do you think it's nothing worth worrying about?
oL said:I might have a problem with my phone and hoping someone can offer some advice. Everyone who I've called so far say that there is an echo (I think their voice echos) but it sounds fine to me.
I was thinking it could be caused by the network, the signal seems fine most of the time but the internet is often too slow to use. Could it be caused by my network? Or do you think it's a fault with the phone itself?
The network I'm with is GiffGaff, so effectively O2. I bought the phone off ebay, it was not listed as faulty.
Any ideas?
no.
btw do you have audible selection disabled? (settings >> sound >> Audible selection). because mine makes a loud sound with it enabled and not when it's disabled. Either way you shouldn't need to be in there messing. Stop worrying about it, your phone is fine![]()
stuff
I've seen problems with echoing before, probably in this thread. I cant remember what the cause was of if there was a fix however. The sgs2 has two mics doesnt it? check if one's blocked maybe. Try toggling the noise cancelling(when in a call) and see if that improves it as well. other than that, I don't know.
Could be modem related? What version are you using?
ok thanks I will try toggling noise cancelling. Not sure if it has 2 mics, I did try recording my voice and playing it back, it sounded fine.
KL1 at the moment but I think same was happening with KI3.