yashsingh1/xdaforums huggingface dataset:
[Nexus S Q&A, Help & Troubleshooting] kuntstubble:
Well I consider myself quite loyal to the Android platform and handset manufactures. Bought (and all SIM free) HTC Magic, Motorola Milestone, HTC Desire, Nexus One, Galaxy S, Nexus S.... now that's quite a bit of cash I have spent.

So, after deciding to settle with the Nexus range, as I do like the idea of getting a vanilla android OS, plus the latest and greatest updates.... As I did with the Nexus One.

Well I have two Nexus S's, one for me and one for the girlfriend.... so we are looking nearly 1000€ at the time of purchase.

Both handsets are the i9020 models... and both running 2.3.4

So, out pop's 2.3.5, and it's only for the Nexus S 4G ... well, OK I can live with that.

Now out pop's 2.3.6 ... and once again, or at least for the moment, nothing for the i9020 owners.

To me this is just simply wrong. Plain and simple. There are too many variants of the handset now, but as someone who generally buys on day of release I am expecting to the get the updates.

I can not believe I am alone in thinking this, but one thing is for sure I will be seriously debating purchasing the Nexus Prime or whatever it may be called in the end, if this is how OTA's will be handled.

Interested to see if anyone feels the same about this.
[Nexus S Q&A, Help & Troubleshooting] lballer69:
U do know that there just bug fixes for our phone .....y would u want an ota that has nothing to do wit ur phone ...
[Nexus S Q&A, Help & Troubleshooting] kuntstubble:
There are plenty of bugs in 2.3.4 on i9020 .... most of the problem is Samsung firing out god knows how many variants of the handset. OK, with the Nexus One they had no choice due to supplies of the displays.

It should all be streamlined, not so fragmented.
[Nexus S Q&A, Help & Troubleshooting] matt2053:
There are important security patches in these updates too.
[Nexus S Q&A, Help & Troubleshooting] kuntstubble:
Which would apply to the i9020 I assume. Also I guess the android source is on 2.3.6 now... so our handset will be not up to date.
[Nexus S Q&A, Help & Troubleshooting] bozzykid:
This isn't unusual when you provide phones to multiple carriers.
[Nexus S Q&A, Help & Troubleshooting] kuntstubble:
Yeah OK, but if I pay good money for a SIM free and unlocked handset, which also is meant to be THE purest Android handset on the market, then WTF are we lagging on versions? Sure if they find a carrier specific error, shoot out an update and name it GR1234. But if the base Android platform is update I expect and so should everyone to get them.
[Nexus S Q&A, Help & Troubleshooting] splmonster:
You are incorrect on one thing. Is that Samsung has anything to do with Nexus updates. They don't, this is all Google. Another thing, the update just dropped like a week ago, and isn't even widespread to those who are getting it. Doing research also would of helped your cause in this case. Sprint has already announced on the support page that it's coming. You should read my article.. http://the-android-world.blogspot.com/2011/09/nexus-s-update-build-gwk15f-outed.html

You sound as bad as Fixxer did with the Nexus. Be patient... It just dropped, the fix was mostly intended for the voice search bug. Which not all Nexus S's had the issue.
[Nexus S Q&A, Help & Troubleshooting] kuntstubble:
OK some of your comments are valid. And I know fine well that Google provide the OTA's and not Samsung. Think you are missing my point tho... and it's as simple as this, there is fragmentation of the version numbers and functionality too... I'm not banging on about the baseband, but the actual OS...
[Nexus S Q&A, Help & Troubleshooting] bozzykid:
2.3.4 was suppose to be the last Gingerbread release. 2.3.5 was for the Nexus S 4G because of network issues. 2.3.6 was for the versions experiencing the search popup bug. It would make sense that they are holding off releasing anything to the other Nexus variants until ICS is ready.
[Nexus S Q&A, Help & Troubleshooting] matt2053:
There are many more changes than just the major updates you see in the promo materials. 2.3.5 changed way more than just network stuff for NS4G. and 2.3.6 changes way more than just fixing the search popup bug.

It would be nice to get all the latest security patches and bug fixes from 2.3.6 on my T-Mobile Nexus S. BUT, I know resources are often stretched thin especially ahead of a major new release like Ice Cream Sandwich, so I am totally fine with Google putting their attention and resources on that rather than updating my Nexus S with some security patches and bug fixes that the average user will never notice.

Also, the cool thing about Android is, if you really really want 2.3.6 on your NS4G or T-Mo Nexus or Nexus One.... well go here http://source.android.com/source/initializing.html and follow the directions and you can download the 2.3.6 source and build it for any Nexus device.
[Nexus S Q&A, Help & Troubleshooting] kuntstubble:
But do you not think that if you fork out for a vanilla android handset, that you should get every single update. If the source is on 2.3.6, I expect my vanilla handset to also be on that. I do not think it is too much to ask considering it is still sold and marketed as being the real google android phone.

I never had this problem with the Nexus One, and I sure as hell did not expect it with the Nexus S... I feel I have been short changed a little by Google.
[Nexus S Q&A, Help & Troubleshooting] rican408:
Seriously CRYING for NOTHING. Take a breath and put the phone down. We will probably get the update soon. Chill out. And because of this you don't want another nexus? Have fun waiting for almost a year for updates.
[Nexus S Q&A, Help & Troubleshooting] kuntstubble:
Not crying for nothing. I just don't think it's fair.
[Nexus S Q&A, Help & Troubleshooting] AndroidUser00110001:
Ever try to compile your own ROM? It is very simple and Google has very detailed instructions. The most difficult part, if it is difficult is getting linux and your dev enviroment up and running. Then you can compile your own ROM from source which will add another dimension of fun to your phone :-)
[Nexus S Q&A, Help & Troubleshooting] Rem3Dy:
Life isnt fair little Guy. I'm sorry you have to live in such a terrible world where everyone has choice. Someday when you are old enough to vote you can try to elect someone who will force everyone to be identical and all own Motorola razrs. Until that day comes, we will be stuck here forced to suffer as we wait for a small bugfix update that was much needed for hardware that isn't the same as the phone we own. Keep those dreams alive squirt. Never lose hope!
[Nexus S Q&A, Help & Troubleshooting] Rem3Dy:
Do you cry when your girlfriend gets the OTA notification before you do? Its not fair! Why does she get it first? They activated my phone before hers!
[Nexus S Q&A, Help & Troubleshooting] kuntstubble:
Wow, you really are a total prick... but then again, I guess you can not afford SIM free and are roped into a contract.

Grow some pubes.

As one person stated there are changes and bug fixes that would also benefit i9020 owners, you know, the ones who can afford to splash out cash on handsets.

Finally you jumped up little spunk stain, I've never installed via OTA, I just grab the download link and slap it on as an update.zip
[Nexus S Q&A, Help & Troubleshooting] matt2053:
It's been entertaining gentlemen, but please take it to PM if you wish to continue.
[Nexus S Q&A, Help & Troubleshooting] diversificationied:
There was only one true "nexus" phone and that was the Nexus One. Google is now bright eyed about the making money from hardware business. Expect them to fold like a house of cards to the carriers in the US.

Dems the breaks.

(this is why nobody should support cdma phones)
[Nexus S Q&A, Help & Troubleshooting] LordLugard:
You definitely are crying, nay, whining for ABSOLUTELY nothing, OMG. For example, some Canadian Nexus S models have a voice search bug which didn't affect NS models elsewhere and as such an OTA was released to address that issue affecting those specific models. Should i in the U.S be crying that those folks got an update to fix an issue affecting their handsets that isn't affecting mine?!! Get over your sense of entitlement. And just to rub it in a bit more, my NS4G only cost me $170, new in box, contract free.... (you paid 500 Euros...sigh)
[Nexus S Q&A, Help & Troubleshooting] simms22:
ive been reading your comments.. youre angry about something that is a non issue. imagine if you were on a carrier branded phone, how long do you think that youre going to have to wait for 2.3.6 or even 2.3.5? 5 months.. a year? lol. the tmo nexus s doesnt have those bugs that the update fixes. there is no difference in functionality. do you just want your phone to say 2.3.6? is that what the fuss is about? why dont you just root your phone and edit your build.prop file. itll say 2.3.6 or 2.3.9 if you want. what are you really angry about? what you SHOULD be angry about is that i have a rooted tmobile nexus s that is running CM7 and the Trinity kernel that has at least 70% more functionality that has been added to it and your unrooted nexus s doesnt. you bought a nexus s, root it. thats what it was meant for, set it free.
[Nexus S Q&A, Help & Troubleshooting] uansari1:
Yeah..not crying, lol..
[Nexus S Q&A, Help & Troubleshooting] derekwilkinson:
Dude, the update was JUST announced!!!! God.
[Nexus S Q&A, Help & Troubleshooting] mapin0518:
What irks me is that they are incrementing the version number for mere bug fixes of specific models (and not all models). If it's just for a specific model, then send an OTA update but don't increment the Android version unless it's an across-the-board release of Android. I know I'm probably naive about these things, but that would make more sense to me.

The way they do it now makes it seem like all phones except one AT&T model Nexus S are running an older version of Android.
[Nexus S Q&A, Help & Troubleshooting] mapin0518:
Curious what's the 70% added functionality? All I see of value are drop-down notifications, BLN support, and over/under clocking/volting. Nothing else seems really that useful (to me at least).

The consistent instability of what is it, like nightly 13007, doesn't make those few added features really worth it to me. Maybe on a crappy bloated phone I'd put up with CM7 over whatever it shipped with, but on a Nexus S, having pure stock is one of the big draws of having a Nexus device for many people (not installing custom ROMs). I'd argue that a Nexus is meant to enjoy pure stock goodness and frequent direct updates, not to "set it free" and install custom ROMs. I mean you're free to do that, but it's not really the point of Nexus.

I gave up on even trying CM7 until a stable release comes. In the end it wasn't doing *that* much more for me over stock. Also GPA17, which is basically stock-like works quite well too, but again not enough for me to leave stock.

As they say in other places, down vote away.
[Nexus S Q&A, Help & Troubleshooting] simms22:
then this should piss a few people off.. hehehe(evil laugh) ;)
[Nexus S Q&A, Help & Troubleshooting] simms22:
cm7, not stable? you must be doing something wrong.

some of the changes/fixes, not all are nexus s but most are.
[Nexus S Q&A, Help & Troubleshooting] rican408:
I actually agree that cm7 is no where near as stable as it was on the evo. I've tried everything except miui, nothing is as rock solid as stock.
[Nexus S Q&A, Help & Troubleshooting] mapin0518:
well riddle me this, if it's so stable, why still on nightlies? :p

it ain't more solid than stock, that's all i'm sayin'
[Nexus S Q&A, Help & Troubleshooting] simms22:
if you could meet my phone, you would think different :D
[Nexus S Q&A, Help & Troubleshooting] Rem3Dy:
Because they keep adding more features. It is incredibly stable.
[Nexus S Q&A, Help & Troubleshooting] Rem3Dy:
Thanks for the laughs.
[Nexus S Q&A, Help & Troubleshooting] willverduzco:
Amen. Pointless thread closed.
[Continuum General] MarkZJS:
When can we get the Gingerbread?I have waited for so long --!

I have found that sprint EPIC 4G had got the Gingerbread,but we only get froyo.

Speed up Verizon!:(
[Continuum General] Txwolf1980:
LOL, we aren't even supposed to have froyo. Gingerbread (unless IMNUTS pulls another rabbit out of his hat) won't happen, that I can see. According to another post, they are working on a symbian rom... that should be interesting.
[Continuum General] nodixe:
If we all took up a colkection and paid a dev (or sammy employee for sum source haha) then we might get sump cool... but even then probably not GB....not till they release it for fascinate....but then again I dont know this jus my humble opinion....but im serious about donating for dev help!

sent from my XDA phone - its more than a continuum
[Continuum General] Nuckin:
I'm a developer (not for android though) and I can tell you it would be one hell of an undertaking. Best case is to wait, Samsung did announce GB for Galaxy S devices, however none of the US devices have gotten it yet.

And fascinate ROMs don't work all that well for us unfortunately
[Continuum General] logan302:
Update

The Symbian ROM has been put on hold. We are now working on DOS Mobile.:D
[Continuum General] MarkZJS:
Oh,DOS Mobile,I think it will be great,haha:D
[G2 and Desire Z General] arinrizk:
dears

I searched alot and can't find the official RUU rom for the desire z

I found the www and asia ruu but can't find the MEA /ARA /EGYPT RUU

even in the shipped roms site

shipped-roms.com/index.php?category=android&model=Vision

you can find the :

RUU_Vision_Gingerbread_S_hTC_Asia_TW_2.42.709.10_Radio_12.56.60.25_26.10.04.03_M_release_201045_signed.exe

RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe

But not the aravic support MEA version

please help

thanks mates
[XPERIA X10 Q&A, Help & Troubleshooting] shroomhead:
I'm attempting to install the new Zmod Cyanogenmod 7.1 but am encountering problems with xrecovery unable to read the SD/card when installing. Supposidly the new version of xrecovery will fix my issue but when I looked at the thread listed "2.3 STOCK ROM" as a requirement.

Now I cant update to the official 2.3.3 rom as im on O2UK, but I'm currently running Cyanogenmod 7.0.3 (on baseband 0.52) so will I still be ok to update to the new version of xrecovery?

Also just a quick question as its been a while since I installed a new rom, it's baseband first (any .71?). My phone will still be rooted, busybox still installed, etc, as I've done all this before? Then install new .zip via xrecovery?

(I've already read the newbie threads so please don't just point me there, simple yes/no answers will suffice. I'm just a little confused about going from custom install to custom install.)

edit: could this be a problem with going from a 0.52 baseband to a 1.71? This thread talks about 0.54 but could it be something simiar? http://xdaforums.com/showthread.php?t=1053221
[XPERIA X10 Q&A, Help & Troubleshooting] JimzFreebies:
install xRecovery-0.3 (GBready) using flashtool

Here is the guide:

http://xdaforums.com/showthread.php?t=1196808
[XPERIA X10 Q&A, Help & Troubleshooting] Dark Nightmare:
He needs to install baseband .71, better if he just installed gb and root it.
[XPERIA X10 Q&A, Help & Troubleshooting] spitespy:
from 2.1 or 2.2 baseband less then 2.1.71

u need flash 2.3.x room 1st after that use flash tools flash baseband 2.1.71....

if from 2.1/2.2 u flash baseband 2.1.71 after flash the 2.3.x rom that xrecovery cant use anymore,

u neef flash via flash tool to baseband to 2.1.67, do it from 2.1/2.2 as well
[XPERIA X10 Q&A, Help & Troubleshooting] spitespy:
7.03 android 2.2.3 baseband 2.1.67

7.10 android 2.3.5 baseband 2.1.71
[XPERIA X10 Q&A, Help & Troubleshooting] shroomhead:
So install the zmod 7.1 .zip through my current version of xrecovery first, then use flashtool to upgrade the baseband to .71, root and then install the new xrecovery (as in the first reply)?

I might give this a try first as at least I'll have a fully working x-recovery before I start. After I've installed it this way can I go back to my 0.52 baseband and CMod 7.0.3 if I want?
[XPERIA X10 Q&A, Help & Troubleshooting] shroomhead:
Well I installed xrecovery via the instructions on that link and my phone is now stuck on the SE loading screen. This is exactly what I wanted to avoid as my phone is not running stock 2.3.3. Can I have a fix please!

edit: Ok got it working by installing the .zip and flashing the .71 baseband. Thanks.
[Thunderbolt Q&A, Help & Troubleshooting] droid fetish:
I am on shiftsense 1.3 and am trying to find a way to erase (bal,data,min,pmt,warranty and global support) no where in any of the menus is there an option to delete.
[Thunderbolt Q&A, Help & Troubleshooting] UndergroundWire:
I've asked this question before with no help on the matter. It's a shame because those contacts are quite annoying.
[Thunderbolt Q&A, Help & Troubleshooting] Absolute_Zero:
Never used shiftsense (or any sense for long) so not sure how exactly the contacts app is preventing it but if it won't give you the option to delete them when pressing the menu button after selecting, have you tried deleting them from your Google contacts? If you have contacts backed up to Google you can go to www.google.com/contacts and select ones you want to delete. Then when it syncs it should remove them unless for some reason shiftsense prevents that. :shrug:
[Galaxy S II Q&A, Help & Troubleshooting] shillier123:
Ive search high and low on xda developers to find a rom with a aosp bluetooth stack and mhl cable support. My plan is to use the Sixaxis Controller app with the mhl cable but so far ive only been able to find roms that do only one of those functions.

Also is there anyway to install a new bluetooth stack and the Original XXKG firmwares.

Would appreciate any help.

Device: Samsung Galaxy S2, Running MIUI.
[Galaxy S II Q&A, Help & Troubleshooting] jim dinamita:
That's something many gamers wish... but after a few months without any luck I think the only way is to buy a specific gamepad like phonejoy, etc. as long as CM (and MIUI consequently) doesn't support mhl yet. And maybe never...

The cool thing could be something like you are talking: someone making a stock rom but with aosp bluetooth drivers instead of samsung ones

Edit: I write from the complete ignorance, and don't know if it's easy to do or even possible. Please excuse me if i'm saying something stupid
[Galaxy S II Q&A, Help & Troubleshooting] pileot:
I too am wondering

If one could just copy the AOSP bluetooth over the stock roms we would have the best of both worlds
[Galaxy S II Q&A, Help & Troubleshooting] Warrimonk:
The bluetooth stack in Cyanogenmod 7 works with sixaxis. I used my ps3 controller to play my emulated games.

Although I do perfer non-aosp, as the kernel/rom selection is better and the touchwiz apps are better (IMO) . I cant live without fm radio.

If any devs could add find a way to get the aosp bluetooth stack on a non aosp rom, we would all be very grateful.
[Galaxy S II Q&A, Help & Troubleshooting] otakukj:
I want to bump/1 up this thread

I am using lite'ning rom 6.1 and I really love this rom, but at the same time I want to be able to use my ps3 controller so thumbs up for anyone who can do this, even information on how to or why it's not currently done would be nice, my brother knows a bit about programming if we knew where to look maybe we could try to do it ourselves. I really want to see this done. :cool: I know it's possible somehow!
[Galaxy S II Q&A, Help & Troubleshooting] tainka:
I'm trying to understand how many people affected buy it, if it is a very little amount of people, maybe Samsung will not fix it. Is this problem big enough?
[Galaxy S II Q&A, Help & Troubleshooting] anshmiester78900:
Well no problem here
[Galaxy S II Q&A, Help & Troubleshooting] beleta:
I have the pink spot.
[Galaxy S II Q&A, Help & Troubleshooting] B3311:
Give it a break, for god's sake.

This is at least the 4th thread you've started on the pink spot, who has it, who doesn't etc.

Do you think repeated posting will fix it?

Stop whining.
[Galaxy S II Q&A, Help & Troubleshooting] Omega Frost:
After reading this thread i've found that i also have the pink spot, but it's so unnoticeable... seriously unless your hobby is to take shots of bright white walls it won't be an issue.
[Galaxy S II Q&A, Help & Troubleshooting] tainka:
You did not answer if you have it or not. If you don't- there is nothing to whine about. I paid a lot of money for this phone, this is a huge disappointment for me. If there is enough people with this problem, maybe Samsung will do something to fix it. Anyway, this is my last post about it.
[Galaxy S II Q&A, Help & Troubleshooting] B3311:
As tempting as it is not answer you, I don't have it.

Now please answer my question - do you think repeated posting will fix it?

I think xda-developers.com and Samsung Customer Support shouldn't be to difficult for even the tiniest of minds to differentiate between. I'm obviously mistaken.

So one more time - stop whining.
[Galaxy S II Q&A, Help & Troubleshooting] maddada:
I have it, but its not that big of a deal I think it can be fixed with a software update.

Sent from my Beastly Galaxy S II
[Galaxy S II Q&A, Help & Troubleshooting] EarlZ:
I have it and as well as several other users, I've yet to see someone who does not have it though but there are special conditions to make this appear so its not a big deal for everyone.

I understand you just want to know if this is a defect on all or just a select number of units. On another local forum with over hundreds of S2 owners none of them reported not having a pink spot when the conditions are met.
[Galaxy S II Q&A, Help & Troubleshooting] leminhnguyen0703:
For god sake, just download the camera software update from samsung apps, and there you go. Pink spot my ass :))
[Galaxy S II Q&A, Help & Troubleshooting] tainka:
.............
[Galaxy S II Q&A, Help & Troubleshooting] tainka:
Exactly. I just need to know if this problem affecting all S2 units. There are people who say that they don't have this issue.
[Galaxy S II Q&A, Help & Troubleshooting] htcplussony:
I noticed I got the pink spot when I pointed the camera to on my carpet.

Love to download the camera firmware but Samsung didn't release it for my phone's region. Haven't had the guts to try the ones xda members updated yet.
[Galaxy S II Q&A, Help & Troubleshooting] EarlZ:
A lot of users actually get offended if you post such threads, they say your looking for specific issues that dont exist in normal usage or your expecting DSLR quality for the cam.
[Galaxy S II Q&A, Help & Troubleshooting] xan:
Doesnt fix anything ;p update my ass :P
[Galaxy S II Q&A, Help & Troubleshooting] leminhnguyen0703:
Well you got a crap camera then lol. Just kidding, try updating the camera firmware, worked for me. It was like red before and now its clean, and the app runs faster as well
[Galaxy S II Q&A, Help & Troubleshooting] marcadam:
What pink spot?
[Galaxy S II Q&A, Help & Troubleshooting] xan:
Tried, says Its already latest.. :(

Crap camera -> sounds reasonable.
[Galaxy S II Q&A, Help & Troubleshooting] pukemon:
I don't have a pink spot but I know a chic or two that do.

I voided my warranty and your mum.
[Galaxy S II Q&A, Help & Troubleshooting] ziggazee:
No pink spot here.

Edit: never mind i just checked properly and i guess i do have the pink spot lol ohwel life moves on.
[Galaxy S II Q&A, Help & Troubleshooting] joshlusignan:
ah ahhahahahahahhh, lol...thanks for a good laugh!

oh and I also have pink spot, on the camera, no where else. Cant seem to find this firmware upgrade from samsung app store, anyone got a link? Thanks!
[Galaxy S II Q&A, Help & Troubleshooting] SugarySnack:
I am almost positive EVERYONE has the pink spot in certain lighting conditions. Those who say no just haven't used it in the lighting that causes it. It is a white balance issue that is a software issue.

This issue has happened to other phones before the S2.
[Galaxy S II Q&A, Help & Troubleshooting] aegisfreedom:
I also have a pink spot, on a white backgroud. Doesnt even matter if im using the camera or not. Even using the stock browser with white background.