I would imagine there won't be one. The lower production volume doesn't quite justify making one (as compared to the iPhone).

Am glad I bought my unit a week before CNY where there's only 5 units left in the shop. Hehe.

^ensure NFC and Android beam are turned on on both device. The sender needs to touch the screen when beaming as per on-screen instructions.

---

Added on January 30, 2012, 9:17 pmAnyway, is it me or the screen totally dies when a phone call is received? There is no way I can pick up a call. The screen shows a call, but it does not register any touch input. Only way to reactivate the screen is to hit power, let it sleep, hit power button again to wake it up, then only can pick up the call.

On AOKP Build 21 if that matters.

This post has been edited by DJFoo000: Jan 30 2012, 09:17 PM

I did a full wipe for b21. Even applied Superwipe lite. On franco kernel 14.4, radio = XXKK6.

Is it a kernel problem? Everything works fine, except this.

I'd recommend against using the Galaxy Nexus as your primary camera, if photography is of concern. Taking snapshots still ok, but for photography purposes, a big fat no. Sensor just not up to the job.

Zero shutter lag has nothing to do with image blur. Zero shutter lag only concerns the process after the shutter button is released, and the image being captured. Shutter lag concerns whether you capture the exact moment that you want (like you want to take a pic of a moving car in the centre of the frame, a huge shutter lag will cause the frame to totally miss the car, while a short shutter lag will let the sensor capture the image just as you want).

Image blur has to do with shutter speed (not to be confused with shutter lag). Shutter speed is the duration which the sensor is capturing the image. Think of light as particles (which it is in quantum mechanics), and you are capturing an image which only has a big dot in the centre. If the sensor is as still as possible, then the light will only hit a fixed place with little variation (clear image) and you get a clear dot in your image. If the sensor is shaking, the particles will land in a scattered area (blur image) and you get a dot with blurred edges.

To make it simple, the process of taking a picture on any camera:

1) Shutter button is half-pressed, lens focuses (in this case, you press the on-screen shutter button on your phone)
2) Shutter button is pressed fully. (in this case, you release the on-screen shutter button on your phone)
3) Shutter opens.
4) Sensor is activated for capturing image
5) Sensor is deactivated (shutter closes) and processing of image begins
6) Image is processed and is saved
7) Sensor ready to capture the next photo.

Shutter lag is between 2) and 3) [since phones don't have shutters, shutter lag concerns from 2) to 4)]. Shutter speed is in step 4). Shutter lag is the primary reason why people buy DSLRs.

Hope that helps.

Apologies for the wall of text on shutter speed vs shutter lag. Too many people are using the wrong term.

This post has been edited by DJFoo000: Jan 31 2012, 12:20 AM

^yeah was going to edit my post to talk about image blur.

Exposure (whether a picture is bright or dim) depends on shutter speed (among other things). There're 3 ways to prevent (or minimise) image blur:

1) Shoot in a bright situation, like under bright sunlight (which will require a fast shutter speed). One trick is to use a higher ISO, or a wider aperture. But that is another story altogether. If you're intersted then you might want to go visit the photography sub-forum.
2) Keep the camera as still as a rock (image clarity will not be affected by sensor shake).
3) Machine-aided image stabilisation.

Since the Galaxy Nexus lacks 3), so your best bet is 1) and 2).

Read: http://www.digital-photography-school.com/...tal-photography

Shutter speed is explained in previous post. These details are beyond the scope of this thread, so, it'll be more appropriate if you read the link I posted and or visit the photography sub-forum.

This post has been edited by DJFoo000: Jan 31 2012, 12:36 AM

SGX 544 is not a 'slight upgrade'. It's in the same class as the iPad 2 GPU, which was expected to be in the current Galaxy Nexuses since TI was announced as a partner. We all know what GPU ended up being chosen.

Having multiple hardware configurations for the same model name will give problems when it comes to modding. Just look at the Galaxy S II range of phones in US. For one, mods are not inter-flashable. The modding future of a variant depend on whether devs are picking it up.

Just look at the AT&T Galaxy S II and the Galaxy S II Skyrocket. The skyrocket has so much less ROMs compared to the non-skyrocket. The only difference is the screen IINM (4.3" VS 4.5").

http://rootzwiki.com/forum/265-att-galaxy-...eveloper-forum/
http://rootzwiki.com/forum/354-att-galaxy-...eveloper-forum/

Hopefully that SGX 544 on the NenaMark scoresheet is just a build.prop mod. That FPS bump is significant though. Epic GPU kernel overclock coming up? Haha.

Ouu... I thought you were referring to the GPU with regards to that remark, since the only thing we can extract from the NenaMark scoresheet is the GPU has changed.

But then, any hardware changes are significant, IMO, since it basically creates another hardware base for developers to develop mods for, and mods are not hardware inter-flashable. As selfish as I may sound, I'd wish the Galaxy Nexus remains the spec as it is, regardless of which carrier it lands on. Look at the SGS2 G and non-G issue.

I think hardware performance has not plateaued yet. With the Windows 8 ARM build demonstrated to be working on the Galaxy Nexus already (pending confirmation it's not a troll), the possibilities are endless.
Still hoping it's some GPU mod that gave that extra 8 FPS.

Speaking of GPU overclock, here's that email excerpt Franco posted about the non-benefit of GPU overclocking, and thus his reason for reverting to the stock GPU clock speed in Build 15 of his kernel:

http://forum.xda-developers.com/showpost.p...&postcount=4731

This post has been edited by DJFoo000: Jan 31 2012, 04:00 PM

It appears the unresponsive screen during phone call I experience is an AOKP bug, which was resolved in M3.

Erm... A very very very tiny 'lag' exists, but that's because the digitizer needs to recognise your input and for the phone to react. Are you talking about that?


When it's grey means it's not connected to Google server. Try launching the Google Talk app.

Sometimes, a noticeable lag do exist when going from lockscreen to homescreen. Could be attributed to CPU scaling though...

---

Added on January 31, 2012, 8:59 pmWhoah, LYN front page has a 32GB Galaxy Nexus review unit! Not sure if is trolling though...

http://www.lowyat.net/v2/index.php?option=...d=6162&Itemid=1



Did they mess up the specs for the LTE version of Galaxy Nexus? They mentioned:



Hrmmmmmm.....

This post has been edited by DJFoo000: Jan 31 2012, 09:07 PM

Check IMEI can be done by dialling *#06# . Universal code for all mobile phones.

This post has been edited by DJFoo000: Feb 1 2012, 05:47 PM

^need to flash GApps everytime you flash AOKP, which means you have to add your Google account everytime as well.

^put media volume to lowest.

I just answered your post in previous page. Don't you read?

Bring it for replacement. I have not one Sleep Of Death till now. I've encountered it countless times on my old Desire Z so I know how it feels like. Seriously bring it back for replacement if possible. Confirm hardware problem. Mine's perfect.

Just try and talk to them. They have a way to diagnose the problem one. Ask for a one-to-one exchange if possible.

My Papago also used to not work, then I upgraded radio to XXKK6...

EDIT: yeah Franco kernel 15.2 broke Papago. Hrmm...

This post has been edited by DJFoo000: Feb 3 2012, 02:27 AM

Your screen is barely on.

I have observed on my Galaxy Nexus a consistent battery drain of 20% for every 45 minutes the screen is on.

From my experience, leaving WiFi and GPS on does not really affect things. WiFi needs to be transmitting data, and GPS needs to be refreshing coordinates for battery drain to occur (ie, active surfing, and active GPS navigation). But those activities involve having the screen on as well, so can't totally isolate GPS and WiFi as causes of battery drain.