

1) I need it now (work depends on it).
2) no early adopter issues.
3) those new ones can easily be 4-5-6 weeks away for Dutch folk. Can't go that long without income.
4) there's always something new right around the corner. I don't live my life based on that.
Yes, I had three computers die in a few months' time.
?
The same goes for QR scans and NFC – Samsung’s TouchWiz UI makes the dialer automatically execute the sequence, which can potentially force a factory reset code onto your unsuspecting phone, and wipe your data.
It's not browser based..
This sucks because regular users have no clue how to use a ROM and almost no one buys nexus phones, Samsung barely markets theirs.
In this case, I don't think another browser would help. If I understand the exploit correctly, Samsung's modified dialer is the issue here, not the browser itself. In other words, unless your browser does not do phone number detection (which will pass phone numbers to the dialer when clicked) then you can be hit by this no matter which browser you are using. There's no safety for this one if you're using one of these, except plain old common sense. The old rule still holds: If you suspect a malicious link, don't click it.
Not safe enough : an URL can be resolved automatically without user interaction, like an HTML frame src URL, or a QRCode reader.
Or a RSS app: RSS Republic & co does it and, ironically, many android users actually notice the exploit news article and experience what it can do actually at the same times, thanks to their news feed app ;-).
I recently bought a Samsung 7.7 Tab. I have a Galaxy Phone as well, which I rooted and put a custom ROM on long ago. I forgot how misarable and downright shitty Touchwiz is. It adds *nothing* to stock Android. Id be willing top pay 10 euro s more for a clean device so I would nt have the hassle of flashing and so on, to take off the unneeded bloat that.s called TouchWiz
There are a lot of conflicting reports on this. From this Google's commit:
https://android.googlesource.com/platform/packages/apps/Contacts/+/3...
it seems like this was a stock Android dialer bug that was fixed in June. This is consistent with the claim here: http://securitywatch.pcmag.com/none/303097-dirty-ussd-hack-wipes-sa...
that it was reported to Samsung and Google in June.
There are reports that this fix was shipped in 4.0.4 and 4.1 stock builds and Samsung pushed OTA updates where it could. Of course, those using carrier-provided ROMs can be out of luck.
Androidpolice says most US carriers likely pushed a fix last week: http://www.androidpolice.com/2012/09/25/video-most-galaxy-s-iii-dev...
This is for S3, don't know about other models.
They didn't pushed a *fix*, but a full upgrade to Android 4.0.4 or sooner, which already include the fix.
I'll bet that they didn't even knew that the issue existed on the first place and that only this upgrade comes with the fix. May Jelly Bean was not ready to broadcast, I'm pretty sure no official fix will be available yet.
The root bug is in the stock Android Dialer app, and was fixed in 4.0.4. An hotfix patch was pushed toward custom ROMs makers, but it seems that phone markers were more busy polishing their custom look & feel than fixing venulverality holes.
Meanwhile, install and make it default TEL handler this proxy dialer quickly hacked by XDA developers last night:
https://play.google.com/store/apps/details?id=org.mulliner.telstop
This reminds me of these iOS exploits that one used for jailbreaking back in the old days. You just opened a specially crafted web page or PDF document and boom ! Out came root access !
Seriously, mobile OS security is such a joke, I can only wonder why all the flaws of our beloved gadgets haven't been used for large-scale cyber-warfare yet.