***** The Official Galaxy Nexus Thread *****

I don't really know what "like lighting" means because this is the first smartphone I've owned and it certainly doesn't respond to simple actions instantly (more like... about 100ms later :D). Perhaps smartphones were genuinely sluggish for a while and I didn't notice because I didn't own one? So my perception of sluggishness is different. And of course I am not blaming it for things like slow web pages etc that are network bottlenecked.

By graphics being poor I didn't mean in actual games of course (that would be an invalid comment as you rightly pointed out). I was highlighting my concern for the graphics chip compared to how many pixels the device has. No doubt in the future it will struggle with any marginally demanding games compared to a phone like the GS2 (which is vastly more graphically capable). Though I could have just said that in my first post >_<. And of course the GS2 could also be considered slow in 2 years because the tech is moving so fast.

Currently getting about 1800 on Quadrant which I thought was quite low (to last for 2 years) but maybe with a custom rom it will nearly double.
But clearly if I wanted the best possible gaming on a phone (why lol) I could have opted for a different handset so I can't exactly complain. The pixel count is great for everything else.

As someone who owns nearly every high end phone there is, it has no issues with responsiveness, it's very fast.

It sounds like you have a dodgy unit if your volume bug wasn't fixed by the OTA update.

As for the graphics chip and quadrant, why do they matter? It isn't cutting edge in the graphics department but it can easily run every single game on the market at the moment and that won't change for quite some time - if at all - in the time period that you own it.
 
I got one of these the other day. Stuck a Giffgaff sim in for instant win.
Fantastic piece of kit, especially the big high-res screen.

The volume bug is NOT fixed for me after the update though. But it only seems to be me and nobody else :(

Gonna flash it soon enough, the default ROM is extremely sluggish like they always are. But at least they openly allow it to be flashed.

The graphics are pretty poor considering the number of pixels, slowdowns in games etc. But phone games are meh anyway at the moment ;) It gives me a good benchmark for development though and I can borrow a SG2 from uni for development if I need something with more performance per-pixel.

It makes sense to opt for the large screen if you want to be able to browse full sized web pages and type faster.

eerrrr

either you or your handset are faulty.
 
I haven't actually got the OTA update (volume fix) yet, but I assume that's because the phone isn't officially out in Norway yet so Samsung haven't pushed it.
 
...No doubt in the future it will struggle with any marginally demanding games compared to a phone like the GS2...
As mentioned by someone else, Quadrant isn't a good benchmark. Additionally, it doesn't work with ICS properly, so scores are skewed.
Using a benchmark that does work with ICS, like AnTuTu, its still getting 50-60fps in a benchmark that has FAR better graphics than most games still on the market.
 
Not if that involves any messing about (as the bug itself barely happens and doesn't bother me), how would you suggest doing it?

Sorry about the late response :(

The android peeps have kindly provided the fastboot shell scripts with the updates themselves which is nice. What you need to do is prepare an environment which allows these scripts to run. This means

1) Installing the Android SDK
2) Getting the fastboot executable

You're supposed to set environment variables so that fastboot can find the SDK but I just put the executable inside the platform-tools folder of the SDK to circumvent all that. I put the update files I want to apply there too.

Once the environment is ready you can just reboot the phone into fastboot mode and then run the shell script in the update.
 
Back
Top Bottom