A huge thanks to him for taking his time to answer these rather "easy" questions.
I focused mainly on the questions which are floating around at xda these days, now we do have some educated answers (aka "the truth").
If someone wants to read a little more, I had collected a couple G+ quotes about Nvidia/LG from him some time back, see here.
To make this post clearer I removed some of the crap I wrote and focused on the important answers from him.
Didn't change anything in his lines of course.
tonyp: first, what's your opinion about LG & Nvidia here.
tonyp: at least it looks like we'll get an official update eventually, Paul's post from his internel LG source looks promising
arcee: LG has been working on that model since February
arcee: as far as I know, they've been stamping out bugs ever since
arcee: in any case, there's 2 sets of issues for a device like the 2x
arcee: 1 - for people like me, nvidia is utterly useless
arcee: I can't do anything on a tegra device unless the vendor does it first
arcee: 2 - as far as stock updates are concerned, that's almost entirely up to LG
tonyp: yes, that's really something TI and otheres are ahead of Nvidia :(
tonyp: but shouldn't LG have some kind of reference source code?
tonyp: aka something that would help "people like you" to implement it yourself
arcee: the reference code is nvidia's
arcee: LG, or any other nvidia customer, can't share it. even if they customize it (and they do), it still started from nvidia intellectual property
tonyp: yes that's obvious
tonyp: what I meant was if LG needs help from Nvidia or if they could help themselves with these reference source code
arcee: they usually have to work together, especially early on
arcee: nvidia is sloppy, their first iterations tend to be, to various degrees, broken
tonyp: Is the tegra2 chipset a problem here?
arcee: no, it isn't
arcee: the chipset is common as much
arcee: the problem is that nvidia chose a very uncommon approach to their android design
arcee: in particular, the userspace libraries and HALs have a ton of hardware-specific logic
arcee: **** that on other platforms is confined to kernel space (like "how to enable the audio amplifier" or whatever), is put in libraries when it comes to tegra
arcee: so for the most part, you can _not_ use a device's libraries on another, unless they share the same hardware components
arcee: and since nvidia publishes zero code, we can't just write our own
tonyp: iirc even things like auto brightness are controlled with nvidia libs?
arcee: yes. sensors, in this case
tonyp: and how specific is this implementation - would we need another device which uses the star platform (which aren't many) or could the Samsung Galaxy R for example help as well
tonyp: you wrote at Twitter that the ZTE Grant (or Mimosa) X won't really help
arcee: at all
arcee: the star, the galaxy R, and the grand X are completely different devices
arcee: different components, different resolutions, different radios
arcee: different audio amps, different panel manufacturers, different almost everything
arcee: the designs have nothing in common other than being T2
tonyp: so it's either LG or nothing?
tonyp: and you're planning to get CM10 to the 2x then? :)
tonyp: because if I understood you correct you won't release any "broken" releases like you did with CM9 anymore. I do get the point, people blaming the apps when in reality the facebook rotation crash is related to a failed attempt of 2d hardware drawing.
arcee: if LG does come out with a release I can use, yes
arcee: else, no
tonyp: that's something :)
tonyp: and which updated libraries are exactly needed? Or are there too many to list?
arcee: pretty much everything
arcee: ICS is just too different from GB