I figured that a shortcut to these on here is best.
First is the file which seems to contain the proprietary data for Froyo
Froyo Data
Next we have the Kernel source code
Kernel Source Code
Last but not least here is the text from the readme file.
How to build
1. Android build
(1) Get the android base source code.
- Download the original android source code (Android 2.2.2 Froyo) from http://source.android.com
(2) Overwrite modules that you want to build.
- Untar opensource packages of star_lgp999_froyo.tar.gz into downloaded android source directory
- And, merge the source into the android source code(froyo)
(3) Run the build scripts.
- You have to add google original prebuilt source(toolchain) before running build scripts.
- Run the following scripts to build android
a) . ./build/envsetup.sh
b) choosecombo 1 1 generic 1
c) make -j4
into the android folder
- If the android is built sucessfully, you will find the outputs in this directory,
"out/target/product/generic".
2. Kernel Build
(1) Untar using following command at the android folder
- tar xvfz star_lgp999_kernel.tar.gz
(2) Execute make.
- Set the compile environment
- gcc 4.4.3
- Ubuntu 10.04.1
- cd kernel
- make star_android_defconfig ARCH=arm
- make ARCH=arm CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-eabi-4.3.1/bin/arm-eabi-
- make ARCH=arm CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-eabi-4.3.1/bin/arm-eabi- zImage
- If the kernel is built sucessfully, you will find the build images in this directory,
"arch/arm/boot"
How to use dosfsck
1. NAME
dosfsck - check and repair MS-DOS file systems
2. build
- build with your host PC compiler, eg. arm-gcc
- dosfsck needs header files from dosfs.9 (or later) to compile.
3. install
- simply just copy output(dosfsck) at your target device
- and execute dosfsck with some options
4. usage: dosfsck [-aAflrtvVwy] [-d path -d ...] [-u path -u ...]
device
-a automatically repair the file system
-A toggle Atari file system format
-d path drop that file
-f salvage unused chains to files
-l list path names
-n no-op, check non-interactively without changing
-p same as -a, for compat with other *fsck
-r interactively repair the file system
-t test for bad clusters
-u path try to undelete that (non-directory) file
-v verbose mode
-V perform a verification pass
-w write changes to disk immediately
-y same as -a, for compat with other *fsck
-example
#/system/bin/dosfsck -v -w -p /dev/block/mmcblk1p1
you can get more information with man page.
#man dosfsck
Click to expand...
Click to collapse
Nice post, thanks.
Is it normal for a company to release code this easily? I come from the Samsung Vibrant forums and it was a running joke as to how long it would take for them to release new code.
DataJunkie said:
Is it normal for a company to release code this easily? I come from the Samsung Vibrant forums and it was a running joke as to how long it would take for them to release new code.
Click to expand...
Click to collapse
No, but it IS pretty damn awesome.
DataJunkie said:
Is it normal for a company to release code this easily? I come from the Samsung Vibrant forums and it was a running joke as to how long it would take for them to release new code.
Click to expand...
Click to collapse
LG is supporting cyanogenmod thats the thing. They are releasing the source for us
yeaaaaaaa we got Kernel Source Code!!!!!!!
know we need to call "MOrfic" !!!!!!!!!!!!!!!!!! (from nexus s developer)
death1246 said:
LG is supporting cyanogenmod thats the thing. They are releasing the source for us
Click to expand...
Click to collapse
Seriously? I did hear rumors about T-Mobile being in touch with the developer of CM.
DataJunkie said:
Seriously? I did hear rumors about T-Mobile being in touch with the developer of CM.
Click to expand...
Click to collapse
T-Mobile is the most dev friendly among the carriers.
http://twitter.com/#!/TMobile/status/60111542494048256
"We're looking forward to seeing what @cyanogen does with the G2x. CM7 is great!"
I knew the g2x was superior to the Pyramid/Sensation because of the pure Google experience. This is ridiculously open source considering I too came from the Vibrant and Samsung waited months and months to release any source code.
DataJunkie said:
Seriously? I did hear rumors about T-Mobile being in touch with the developer of CM.
Click to expand...
Click to collapse
Yeah. The official T-MO twitter account had a conversation with cyanogen. T-mo tweeted cyanogen how excited they are too see cyanogen's work for g2x. T-mo actually tweeted too that they will give cyanogen a free g-slate so that cyan can play with it too. Wish every carrier would be as supportive as t-mo
Edit: the link to t-mo's tweet is posted above
joackie27 said:
T-Mobile is the most dev friendly among the carriers.
http://twitter.com/#!/TMobile/status/60111542494048256
"We're looking forward to seeing what @cyanogen does with the G2x. CM7 is great!"
Click to expand...
Click to collapse
I particularly like this one too... http://twitter.com/#!/TMobile/status/60771248325664768
/jealous
Diceman4 said:
No, but it IS pretty damn awesome.
Click to expand...
Click to collapse
I concur.....from my perspective, this is how it should be.....With the Vibrant, I regretted my investment. So far with the G2X I don't feel that way....
Vision77 said:
I concur.....from my perspective, this is how it should be.....With the Vibrant, I regretted my investment. So far with the G2X I don't feel that way....
Click to expand...
Click to collapse
T-Mobile was very smart here. Instead of playing a cat and mouse game with developers, they are embracing it. They probably realize the costs of locking down phones just to have them cracked anyway is not worth it. Instead, work alongside the development community and improve upon the phones.
1,000 brains are better than the few that work for them.
momentarylapseofreason said:
T-Mobile was very smart here. Instead of playing a cat and mouse game with developers, they are embracing it. They probably realize the costs of locking down phones just to have them cracked anyway is not worth it. Instead, work alongside the development community and improve upon the phones.
1,000 brains are better than the few that work for them.
Click to expand...
Click to collapse
So we can assume HTC was lying when they said that it was the carriers that are pushing them to lock the bootloader. Cause if thats the case G2x too would have a locked bootloader cause the sensation and g2x are both on t-mobile.
peacekeeper05 said:
So we can assume HTC was lying when they said that it was the carriers that are pushing them to lock the bootloader. Cause if thats the case G2x too would have a locked bootloader cause the sensation and g2x are both on t-mobile.
Click to expand...
Click to collapse
Why would HTC be lying? Companies (ie T-Mobile) pay the vendors to lock things down. I fail to see your logic here. T-mobile and other telcos were (and are) paying the phone manufacturers to lock the phones.
Even companies like Sony outsource security attempts. It is a frivolous and wasteful use of their funds.
momentarylapseofreason said:
Why would HTC be lying? Companies (ie T-Mobile) pay the vendors to lock things down. I fail to see your logic here. T-mobile and other telcos were (and are) paying the phone manufacturers to lock the phones.
Even companies like Sony outsource security attempts. It is a frivolous and wasteful use of their funds.
Click to expand...
Click to collapse
Lol. My post above was just a mere speculation. No need to get angry and defensive. My logic is just simple, why lg w/ the same carrier(t-mo) has their phones unlocked and why htc with their sensation(also on t-mo) has a locked bootloader. Htc said t-mo pushed them to do it and they don't have any choice.
joackie27 said:
T-Mobile is the most dev friendly among the carriers.
http://twitter.com/#!/TMobile/status/60111542494048256
"We're looking forward to seeing what @cyanogen does with the G2x. CM7 is great!"
Click to expand...
Click to collapse
I am completely shocked by that tweet from T-Mobile. That alone makes me want to switch to T-Mobile. I can't believe it.
peacekeeper05 said:
Lol. My post above was just a mere speculation. No need to get angry and defensive. My logic is just simple, why lg w/ the same carrier(t-mo) has their phones unlocked and why htc with their sensation(also on t-mo) has a locked bootloader. Htc said t-mo pushed them to do it and they don't have any choice.
Click to expand...
Click to collapse
Not trying to sound angry or defensive. I just didn't see your point. I think that after Tmo's take on phones like the Nexus One and now the G2X, HTC and others might get in the ballgame with keeping the phones easily unlockable.
T-Mobile did push companies to lock em down for customer service related issues, but I think times are a changin'
momentarylapseofreason said:
Not trying to sound angry or defensive. I just didn't see your point. I think that after Tmo's take on phones like the Nexus One and now the G2X, HTC and others might get in the ballgame with keeping the phones easily unlockable.
T-Mobile did push companies to lock em down for customer service related issues, but I think times are a changin'
Click to expand...
Click to collapse
I don't buy that for a second. The G2X and Sensation have been in the pipeline at the exact same time, it makes no sense for T-Mo to be telling HTC one thing and LG another at the same time.
I was a big HTC fan for a while, but I smell BS from their end.
cyberchuck9000 said:
I don't buy that for a second. The G2X and Sensation have been in the pipeline at the exact same time, it makes no sense for T-Mo to be telling HTC one thing and LG another at the same time.
I was a big HTC fan for a while, but I smell BS from their end.
Click to expand...
Click to collapse
I know for certain that telcos were asking for a lock-down on the phones. There is really no reason for HTC to lock it up since they're not dealing with customer service issues outside of hardware. The telcos, on the other hand, do have to deal with people bricking phones etc because they don't know what they're doing.
Consider HTC's Nexus One, Google asked it to be unlockable and it was.
Related
Maybe with the "Nexus S" coming soon with gingerbread, samsung will skip froyo and get all galaxy s phones running the newest version first. That would be a nice end of year present. Any thoughts? Just tossing out a hope beyond hopes. Lol
Sent from my SAMSUNG-SGH-I897 using XDA App
I disagree.
Sent from my Captivate
No .
It`s taking a long time to getting froyo in the states as it is .
I believe I read that Samsung already released froyo to the carriers and the carriers are what's holding it back.
The Fragmentation will get worse and worse until Google fixes it, or Android implodes.
Very simple.
Imagine if you bought a new computer, and you were stuck on Windows XP all the way until now... when you were finally granted access to Vista.
gdbusby said:
Maybe with the "Nexus S" coming soon with gingerbread, samsung will skip froyo and get all galaxy s phones running the newest version first. That would be a nice end of year present. Any thoughts? Just tossing out a hope beyond hopes. Lol
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It is pretty clear that Google has it under wraps - most manufacturers don't even have the specs. So the likelyhood of our phone getting it when the specs have not been made public and no one else has it is zero.
gdbusby said:
Any thoughts?
Click to expand...
Click to collapse
Yeah, give us Froyo all ready.
See avatar!
MikeyMike01 said:
The Fragmentation will get worse and worse until Google fixes it, or Android implodes.
Very simple.
Imagine if you bought a new computer, and you were stuck on Windows XP all the way until now... when you were finally granted access to Vista.
Click to expand...
Click to collapse
Yeah, fragmentation is bad. Want to hear about some fragmentation? The chrysler 300 is available in 9 trim levels, awd and rwd, with 4 different engines! Holy fragmentation batman .
thedon809 said:
Yeah, fragmentation is bad. Want to hear about some fragmentation? The chrysler 300 is available in 9 trim levels, awd and rwd, with 4 different engines! Holy fragmentation batman .
Click to expand...
Click to collapse
ROFL
Ten Chars
hahahah that would be freaking hilarious if they did htat
gdbusby said:
Maybe with the "Nexus S" coming soon with gingerbread, samsung will skip froyo and get all galaxy s phones running the newest version first. That would be a nice end of year present. Any thoughts? Just tossing out a hope beyond hopes. Lol
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
No freaking way they will do that. Samsung is in the business to make money, updating existing devices mean less people will buy their new phones. Count yourself lucky when you get Froyo.
and maybe a unicorn will fly out of my ass.
sorry for the sarcasm.....but whats the point of pure speculation?
MikeyMike01 said:
The Fragmentation will get worse and worse until Google fixes it, or Android implodes.
Very simple.
Imagine if you bought a new computer, and you were stuck on Windows XP all the way until now... when you were finally granted access to Vista.
Click to expand...
Click to collapse
Nothing wrong with XP ... I still run it by choice ...
saint168 said:
No freaking way they will do that. Samsung is in the business to make money, updating existing devices mean less people will buy their new phones. Count yourself lucky if you get Froyo.
Click to expand...
Click to collapse
Changed to what it should have read.
not gonna happen
the way I see it, the Nexus S wont be terribly dissimilar to the current SGS series of handsets (from a hardware platform). Google wont buy into this "oh we'll get around to it" bull**** of source releases (they can't, it will be their lead dev platform).
So even if Samsung/AT&T continue to be ****house at releasing fw for the Captivate, it wont matter as much as it does now, because we will have source for a lot more stuff.
1randomtask said:
the way I see it, the Nexus S wont be terribly dissimilar to the current SGS series of handsets (from a hardware platform). Google wont buy into this "oh we'll get around to it" bull**** of source releases (they can't, it will be their lead dev platform).
So even if Samsung/AT&T continue to be ****house at releasing fw for the Captivate, it wont matter as much as it does now, because we will have source for a lot more stuff.
Click to expand...
Click to collapse
+1
I really think with the remote possibility of similar hardware or at worst case scenario Samsung went with a dual core I think that they will use as much of the existing code as possible.... (It appears as if they may be alittle lazy in the coding dept. I've been trying to tinker with the i9000 headset issue and the difference seems to be alot of code added to the Captivate so that the headset hardware in the US worked like every other phone out there instead of the lazy way that Samsung first implemented it)
And if they are as lazy as above, we should have something that may be easier to port.... or at least somewhat easier to port. Especially with the progress that the CM6.1 SGS team is making as well with ditching the rfs system.... We'll get it soon enough.... not as fast as N1s, but fairly fast.
bedwa said:
And if they are as lazy as above, we should have something that may be easier to port.... or at least somewhat easier to port. Especially with the progress that the CM6.1 SGS team is making as well with ditching the rfs system.... We'll get it soon enough.... not as fast as N1s, but fairly fast.
Click to expand...
Click to collapse
Isn't RFS dead if you use a ext4/voodoo based kernel anyway? Dead as in, the phone can read ext4, we can just partition everything as ext4 and move along, nothing to see here.
zero likelyhood of gingerbread this year
its the crazy sh!t samsung is pulling that makes me wonder if i shouldnt have gotten an aria(only other real android option on att)
Kagoshema said:
zero likelyhood of gingerbread this year
its the crazy sh!t samsung is pulling that makes me wonder if i shouldnt have gotten an aria(only other real android option on att)
Click to expand...
Click to collapse
Not sure I'd get the Aria, did it upgrade to 2.2 yet? It's also weaker and smaller than the Captivate. But I definitely agree, after seeing the speed of update and the GPS debacle.. not sure I'll get another Samsung handset again.
With AT&T though... there isn't exactly a wide range of selections.
EDIT: Them Windows 7 Mobile phones sure look tempting.. even then, I'd be eyeing the Samsung Focus.. -_-
Will the phone get updates from Google or T-mobile?
I'm guessing neither. LG has a desktop app that they push updates through. Unless something's different with the G2X I'd assume they'll come through the LG app.
You could also get them from www.cyanogenmod.com!
jimbo831 said:
You could also get them from www.cyanogenmod.com!
Click to expand...
Click to collapse
Quoted for truth.
Hmm. So we could possibly be waiting for LG to do this? That is a potential deal-breaker for me. With pure Google experience and updates we are much more future proof.
borchgrevink said:
Hmm. So we could possibly be waiting for LG to do this? That is a potential deal-breaker for me. With pure Google experience and updates we are much more future proof.
Click to expand...
Click to collapse
You're looking at getting a Nexus S or Nexus One then. For those of us not willing to pay full price, and wanting better hardware, we have to deal with manufacturers instead.
MWBehr said:
You're looking at getting a Nexus S or Nexus One then. For those of us not willing to pay full price, and wanting better hardware, we have to deal with manufacturers instead.
Click to expand...
Click to collapse
I know, but this has more appealing hardware. I just don't get it if it really is LG pushing updates... Why not just let Google handle everything?
Yeah but the update has to go through tmo first before the release it, the have to make sure their crapware is in there.
Sent from my LG-P999 using XDA App
borchgrevink said:
I know, but this has more appealing hardware. I just don't get it if it really is LG pushing updates... Why not just let Google handle everything?
Click to expand...
Click to collapse
What I'm saying is no phone out there but the Nexus S or Nexus One has AOSP Android. Every other phone has a version modified by the manufacturer. Google has nothing to do with these changes. The only one who can release updates is the manufacturer (or service provider if the manufacturer chooses to send the update to them first).
That's just the way it is.
Are you opposed to rooting your phone and installing custom ROMs? If you are interested in that, CM will be your best bet by far as you get the best of both worlds (CM had Gingerbread on even the Nexus One before Google did!).
If you don't want to use unofficial software, you should stick with the Nexus line. Even pure vanilla Android devices get updates through the carriers, that is how it is and how it always will be. Nexus phones are different as they are not sold through the carriers, just designed to work on them. They are managed entirely through Google which means updates come from Google.
MWBehr said:
What I'm saying is no phone out there but the Nexus S or Nexus One has AOSP Android. Every other phone has a version modified by the manufacturer. Google has nothing to do with these changes. The only one who can release updates is the manufacturer (or service provider if the manufacturer chooses to send the update to them first).
That's just the way it is.
Click to expand...
Click to collapse
I was under the impression that the vanilla devices (like the G2x obviously) was AOSP. Do you know what is modified on this version by LG? I know there is preinstalled software, but that is different than changes to AOSP.
borchgrevink said:
Hmm. So we could possibly be waiting for LG to do this? That is a potential deal-breaker for me. With pure Google experience and updates we are much more future proof.
Click to expand...
Click to collapse
LG's committed to before Summer. The O2X forum has them giving June as a time frame.
BarryH_GEG said:
LG's committed to before Summer. The O2X forum has them giving June as a time frame.
Click to expand...
Click to collapse
Just because they have the update for the O2x by June, doesn't mean the G2x will be ready. The two use different software, plus there are different expectations I think between the US market and European. I hope they come together, but I wouldn't be surprised if LG does the O2x first and then gets working on the G2x.
Bob from Wirefly.com said that he talked to someone from T-Mobile when he got the G2X for review and they said the 2.3 update was coming in one month. I'm not holding my breath, though.
Sent from my LG-P999 using XDA Premium App
scmurphy13 said:
Bob from Wirefly.com said that he talked to someone from T-Mobile when he got the G2X for review and they said the 2.3 update was coming in one month. I'm not holding my breath, though.
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
LOL. "Bob from Wirefly" has the inside scoop, huh.
Don't ever believe anything somebody tells you when they're trying to sell you something. That's all I'm saying.
jimbo831 said:
I was under the impression that the vanilla devices (like the G2x obviously) was AOSP. Do you know what is modified on this version by LG? I know there is preinstalled software, but that is different than changes to AOSP.
Click to expand...
Click to collapse
It's not AOSP vanilla, but it's the closest you will get to it without buying a Nexus phone. There's lots of little tinkering to the OS on the LG2x. For example there's a "DTS" button in the music player to enable dts sound. Also, there's the T-Mobile motto when you drag down the status bar. There's a "tethering may incur charges" warning when you turn on wifi hotspot. There are different notification and ringtones put in. Etc etc. If you put this phone next to a Nexus phone, you will see lots of little differences beyond just the T-Mobile bloatware installed.
mapin0518 said:
It's not AOSP vanilla, but it's the closest you will get to it without buying a Nexus phone. There's lots of little tinkering to the OS on the LG2x. For example there's a "DTS" button in the music player to enable dts sound. Also, there's the T-Mobile motto when you drag down the status bar. There's a "tethering may incur charges" warning when you turn on wifi hotspot. There are different notification and ringtones put in. Etc etc. If you put this phone next to a Nexus phone, you will see lots of little differences beyond just the T-Mobile bloatware installed.
Click to expand...
Click to collapse
Interesting. Mine will be delivered tomorrow so I guess I'll see soon. I've had a Nexus One since release, so I'm sure whatever is different, I will notice. Thanks for the clarification.
Not sure where, but I read from one of the CM guys (I think, don't kill me) that it's not AOSP at all! It's actually that same O2X ROM themed to look like AOSP Froyo
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.
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 ...
Sent from my Nexus S 4G using XDA App
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.
There are important security patches in these updates too.
Sent from my Nexus S using XDA App
matt2053 said:
There are important security patches in these updates too.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
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.
kuntstubble said:
most of the problem is Samsung firing out god knows how many variants of the handset.
Click to expand...
Click to collapse
This isn't unusual when you provide phones to multiple carriers.
bozzykid said:
This isn't unusual when you provide phones to multiple carriers.
Click to expand...
Click to collapse
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.
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.
splmonster said:
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.
Click to expand...
Click to collapse
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...
kuntstubble said:
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.
Click to expand...
Click to collapse
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.
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.
matt2053 said:
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.
Click to expand...
Click to collapse
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.
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.
Not crying for nothing. I just don't think it's fair.
kuntstubble said:
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.
Click to expand...
Click to collapse
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
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!
Sent from my Nexus S 4G using xda premium
kuntstubble said:
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.
Click to expand...
Click to collapse
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!
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
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!
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
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
Rem3Dy said:
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!
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
kuntstubble said:
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
Click to expand...
Click to collapse
It's been entertaining gentlemen, but please take it to PM if you wish to continue.
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)
http://www.androidcentral.com/asus-says-bootloader-unlock-tool-coming-gps-hard-yall
so, I know I personally am absolutely 100% enraged to read about this, since we still haven't heard anything about an official ota for NS4G.
Google is ****ing up big time, and they may lose a LARGE chunk of nexus users over this. I may be one of them, too, if they can't fix this problem asap!!
Ya, it is a bit disturbing.
Well, the work week just started back up for them, so maybe we will hear something in the next couple days?
hp420 said:
http://www.androidcentral.com/asus-says-bootloader-unlock-tool-coming-gps-hard-yall
so, I know I personally am absolutely 100% enraged to read about this, since we still haven't heard anything about an official ota for NS4G.
Click to expand...
Click to collapse
Sprint says we'll be "among the first" to updates, not "the first".
hp420 said:
Google is ****ing up big time, and they may lose a LARGE chunk of nexus users over this. I may be one of them, too, if they can't fix this problem asap!!
Click to expand...
Click to collapse
I'd be amazed if this is Google's doing.
Sprint's website says "It runs Android™ 2.3 (Gingerbread) the latest version of Android for smartphones." They're the ones that are clueopenic, not Google.
Don't get me wrong: I'm plenty annoyed at not getting OTA ICS. It's just that I don't actually expect Sprint to live up to their promises, since this is not something they've ever tended to do in the past. Sprint users go through this with every software update for every platform on every phone.
mstevens said:
Sprint says we'll be "among the first" to updates, not "the first".
I'd be amazed if this is Google's doing.
Sprint's website says "It runs Android™ 2.3 (Gingerbread) the latest version of Android for smartphones." They're the ones that are clueopenic, not Google.
Don't get me wrong: I'm plenty annoyed at not getting OTA ICS. It's just that I don't actually expect Sprint to live up to their promises, since this is not something they've ever tended to do in the past. Sprint users go through this with every software update for every platform on every phone.
Click to expand...
Click to collapse
The update does come directly from Google. Sprint works with Samsung to create proprietary hardware drivers that contain everything you need to access Sprint's cell phone network. These drivers are then made available in binary only form to Google. Google then adds these drivers to their official build. The final product is then delivered directly from Google to your Nexus S 4G phone.
Click to expand...
Click to collapse
this quote came from sprint community forums. http://community.sprint.com/baw/message/380145#380145
Sprint does NOT provide our update...google does. Google is falling behind, and they need to be held accountable for their screw-ups. Just because they didn't say "NS4G will be the first" does not make it acceptable for 3rd parties to get an update before they can even get off their lazy asses just to push a button for their OFFICIAL FIRST-PARTY USERS. Everything we need is on their server for download, and if devs here can get off their asses top compile this rom, google sure as hell can do the same!!!
No. Google is waiting on Sprint, not the other way around.
In addition to providing CDMA drivers, Sprint has to approve the final package that is pushed, and they haven't yet done that.
mstevens said:
No. Google is waiting on Sprint, not the other way around.
In addition to providing CDMA drivers, Sprint has to approve the final package that is pushed, and they haven't yet done that.
Click to expand...
Click to collapse
Source or GTFO. And we've already got the drivers, I'm using ICS on my NS4G right now. 4g and everything.
mstevens said:
No. Google is waiting on Sprint, not the other way around.
In addition to providing CDMA drivers, Sprint has to approve the final package that is pushed, and they haven't yet done that.
Click to expand...
Click to collapse
lol...is that why every single file needed to build a FULL ics rom is already on the server??
I'm not saying you're wrong, but in my opinion, it does not look like it's sprint's fault. It looks like Google is either lazy about releasing it, or they are too dumb to build a rom that's working properly so it's stuck in pre-release testing. However, this is just my opinion....but as far as actually building/releasing the OTA, that is 100% on google's end. whether or not the authorization is coming/has to come from sprint is another story entirely....the point is, if that is the case, google isn't doing their jobs and telling them to screw themselves so they don't look like the bad guy in this!! It's not sprint who will have the damaged reputation after this is all said & done.
jesusice said:
Source or GTFO. And we've already got the drivers, I'm using ICS on my NS4G right now. 4g and everything.
Click to expand...
Click to collapse
<shrug> it's the way it's always worked.
This worked in our favor earlier when Sprint okayed deployment of Google Wallet on our devices and GSM users were foaming at the mouth to get it. In those cases, too, it wasn't Google (which has excellent reasons for getting Wallet into as many hands as possible) but the carriers which held up release.
---------- Post added at 02:02 PM ---------- Previous post was at 01:59 PM ----------
hp420 said:
lol...is that why every single file needed to build a FULL ics rom is already on the server??
Click to expand...
Click to collapse
No.
What is the connection between having all the files on the server and Sprint's approval of a final release version?
In your earlier quote lifted from another site, the poster was saying the updates are pushed from Google's servers, not Sprints. That's correct. However, they can't just start pushing updates without carrier approval. This is why, for example, T-Mobile got ICS before ATT.
mstevens said:
<shrug> it's the way it's always worked.
This worked in our favor earlier when Sprint okayed deployment of Google Wallet on our devices and GSM users were foaming at the mouth to get it. In those cases, too, it wasn't Google (which has excellent reasons for getting Wallet into as many hands as possible) but the carriers which held up release.
---------- Post added at 02:02 PM ---------- Previous post was at 01:59 PM ----------
No.
What is the connection between having all the files on the server and Sprint's approval of a final release version?
In your earlier quote lifted from another site, the poster was saying the updates are pushed from Google's servers, not Sprints. That's correct. However, they can't just start pushing updates without carrier approval. This is why, for example, T-Mobile got ICS before ATT.
Click to expand...
Click to collapse
that was a result of carriers' investment in other companies that developed very similar software to google wallet....exactly the same as when the GN was delayed for verizon because google wanted wallet on their official device and verizon had a coronary about it because they had already backed another company's software that does exactly the same thing.
as for carrier approval, google can only wait so long before they just snap and push the update anyway. carriers can not make the rest of the world wait for an update just because they don't want it released to their devices yet. Google needs to just ***** slap sprint, tell them to shut the hell up, and push the update before this damages their reputation any more than it already has. Like I said, it won't be sprint whose rep is damaged from all of this, just like no one looks towards verizon for the GN delay...the world will blame google, and they aren't even standing up for themselves.
hp420 said:
lol...is that why every single file needed to build a FULL ics rom is already on the server??
Click to expand...
Click to collapse
Sure, they could build ICS for the NS4G but the 4G radio wouldn't work. Drivers aren't part of AOSP.
Also, didn't Google pulled the ICS update for the (tmobile) Nexus S? If that's still true, they're clearly working out the issues with ICS before releasing it to the NS4G, etc.
It is most likely *not* Googles doing. I don't know where half of you get these crack pot ideas from that Google or any other OEM is in control over how and when they push an update.
- OEM builds ROM
- OEM submits ROM to carriers (i.e. Sprint branded phone would require Sprint to approve the update).
Carriers can be total dicks about updates and providing OTA. I've seen it all first hand from when I had a Motorola Milestone (Motorola telling us the 2.1 has been built and has gone through testing but they are waiting for carriers to approve them on their networks) we had to waiting months for the updates due to some carriers.
nside said:
Sure, they could build ICS for the NS4G but the 4G radio wouldn't work. Drivers aren't part of AOSP.
Also, didn't Google pulled the ICS update for the (tmobile) Nexus S? If that's still true, they're clearly working out the issues with ICS before releasing it to the NS4G, etc.
Click to expand...
Click to collapse
Driver binaries are on Google's servers for nexus devices. 100% built from source and 4g works just fine.....
Sent from my Nexus S 4G using xda premium
we are waiting for sprint to approve the new radio that will come with the ota. That is what causes the holdup.
Sent from my Nexus S 4G using xda premium
maybe Google is still fixing what does not go to ics now and then....maybe xD we can see ics on all nexus ^^
hp420 said:
that was a result of carriers' investment in other companies that developed very similar software to google wallet...
Click to expand...
Click to collapse
Precisely. I'm glad you finally see my point that Google can't just push out an update because they want to, but are hampered by needing carrier approval.
---------- Post added at 02:33 PM ---------- Previous post was at 02:28 PM ----------
hp420 said:
carriers can not make the rest of the world wait for an update just because they don't want it released to their devices yet.
Click to expand...
Click to collapse
When did this start being true?
It's absolutely true that carriers CAN prevent official release of an update for any reason, or for no reason. They've done it many times before and they'll do it again. Sprint has a long track record of doing exactly this.
hp420 said:
Google needs to just ***** slap sprint, tell them to shut the hell up, and push the update
Click to expand...
Click to collapse
You have an awfully lot to learn about how contracts work.
If I run a massive business and another massive business violates my contract with them (for example, pushes an unapproved update to what I think of as "my" devices irrespective of the beliefs or desires of my subscribers), many lawyers are going to be fed and I will expect a massive transfer of assets from that other company to mine.
mstevens is dead on. Sprint will not allow the push of an ota until they can be sure this update won't toast peoples phones, and for the people in the world that have a nxs4g and don't do modding, if the update is broken, they can't just fix what Google's update did. My brother has the GSM version, and received the update, and honestly were not missing anything. The user made roms are already becoming superior builds anyway. We will eventually get the update, I for one am glad sprint said no at the moment though, I would hate to waste my time on a broken ota lol
Sent from my Nexus IcS 4G using xda premium
lol...too many people to quote you all, so I'm gonna do my best to answer everyone
Ok, I understand how contracts work. My point is this: yes, google has a contract with sprint (or any other carrier, for that matter) to provide radios, wimax drivers, what-have-you, and I understand that if sprint won't sign, there's not much the manufacturer can do...I get that. But my biggest concern with all of this is that google is not flexing their muscles. They have made a guarantee to their customers (not explicit, but still implied) that they would provide ALL NEXUS UPDATES in a timely manner. Sprint is now holding google back from seeing this implied promise carried through, and the fact that other manufacturers are already pushing full ota updates now makes google look bad (grounds for a lawsuit).
I understand that if google were to break that contract by circumventing sprint by releasing the update anyway, they could be sued...I get that. However, google could also counter-sue for making customers wait an unreasonable amount of time for an update that is, by all rights, a "god-given right" to all nexus users prior to anyone else getting it.
Now let's talk about how many people use an NS4G to develop software that they get paid top develop. By sprint not releasing an official update, they are now inhibiting developers from doing business, and therefore they are taking money out of people's pockets. Yes, I know this last example is far-fetched a little bit, but honestly, it's really not all that far off. Yeah, people can just compile aosp themselves, and if they are truly developers, they should know how to do that....but let's say they are working on one particular app that is exclusive for sprint users, and they want to make sure it will run properly on sprint's network via an ICS handset....oh, wait...they can't because sprint are a bunch of lazy pieces of **** who won't sign. This is grounds for class-action, IMHO.
I may not be a lawyer, but it's blatantly obvious to me that if sprint holds out long enough, they are absolutely 100% vulnerable to class-action suits...and maybe even a suit from google, as well. Let's face it, no one but sprint & google execs really know the terms of the contract, but for all we know, it IS in the contract to provide timely updates. If this is the case, I hope someone gets sued like a SOB for this delay, because it's unacceptable!!!!!
hp420 said:
Google is ****ing up big time, and they may lose a LARGE chunk of nexus users over this. I may be one of them, too, if they can't fix this problem asap!!
Click to expand...
Click to collapse
I suggest that this LARGE chunk of nexus users may be better served by one of the many other smartphone mfrs who provided a pure ICS update (i.e. no BS extra UI layer and no bloat) over the holiday. Which one will you choose? Oh, wait.
hp420 said:
I hope someone gets sued like a SOB for this delay, because it's unacceptable!!!!!
Click to expand...
Click to collapse
Really. You want a lawsuit, because a bunch of software developers wouldn't work at your whim over the nation's biggest holiday?
The111 said:
I suggest that this LARGE chunk of nexus users may be better served by one of the many other smartphone mfrs who provided a pure ICS update (i.e. no BS extra UI layer and no bloat) over the holiday. Which one will you choose? Oh, wait.
Really. You want a lawsuit, because a bunch of software developers wouldn't work at your whim over the nation's biggest holiday?
Click to expand...
Click to collapse
actually, since the drivers, kernel, etc. was all pushed to google's update servers WELL over a week before christmas, they wouldn't have been working during the holiday at all to get it pushed to NS4g...they just had to click a few buttons....something I've done a few hundred thousand times in the last 5 minutes.
BTW, no need to be a smartass about it. if I want to switch from nexus to get a pure android ui, I can always just root and modify the ota to have a stock theme. So now what do you have to say about that, smartass??? Oh wait...
tool.
hp420 said:
actually, since the drivers, kernel, etc. was all pushed to google's update servers WELL over a week before christmas, they wouldn't have been working during the holiday at all to get it pushed to NS4g...they just had to click a few buttons....something I've done a few hundred thousand times in the last 5 minutes.
Click to expand...
Click to collapse
You're making multiple assumptions. You assume that by the existence of particular source files on a particular server, you know what Google's stance as to the public release candidacy of a compiled package is. Please explain why you believe this. There are only two ways we could know such a thing:
1) Google publicly declares it (i.e. this compiled package IS ready for public use... or vice versa)
2) Google actually pushes the compiled package (in the absence of such an action, the logical assumption to make is that they are not ready to do such a thing yet, for their own reasons... i.e. there is still something else they need to do. NOT that they are "too lazy/stupid to push a few buttons")
hp420 said:
BTW, no need to be a smartass about it. if I want to switch from nexus to get a pure android ui, I can always just root and modify the ota to have a stock theme. So now what do you have to say about that, smartass??? Oh wait...
Click to expand...
Click to collapse
You're right, the sarcasm is 100% optional. It's an option that I quite enjoy though. I won't, however, stoop to personal attacks.
How about this. Sarcasm removed for you, I will ask the question that was clearly evident in my last post. If you decide to "leave Google" because of your discontent, which handset vendor will you turn to? Who do you believe is a better option? Who will give you a pure Android update in a shorter timespan? I am genuinely (no sarcasm) interested!
As Galaxy S owners, we are all united. As Android users we are all united. As far as Samsung is concerned we are all NOT created equal. Our device, the Vibrant (SGH-T959), is now being left to the wayside for any future updates from Samsung even though our core specs are extremely similar to the Google Nexus S, which has already received the ICS update. The CyanogenMod team has left us due to the on-going issue of 911/e911 and the lack of the proper code from Samsung to alleviate a potentially fatal result of a custom ROM. It is our intentions to serve Samsung with a petition asking for the update to ICS, which will in-turn, alleviate the 911/e911 issue as well.
We are asking all Galaxy S users to sign this petition to get Samsung to reconsider giving all top end Galaxy S devices the ICS update. Please help us with our goal and sign the petition. If you are on a Galaxy S phone, this affects you too.
Thank you for reading this and please see this link for more details and this link to sign the petition.
Ok, since it was explained a bit better to me, I'm allowing this to be reopened, however, I'll be keeping an eye on it. Keep it civil.
Thank you, Ann.
thanks for the update..hope things look up !!
I plan to sign this petition, but I'm a bit confused about how it includes all SGS devices. The entire letter speaks specifically to the Vibrant. Is a new letter still being written? Or how is it being conveyed that all SGS owners are signing this?
Sent from my SAMSUNG-SGH-I897 using Tapatalk
The issue with the 3rd paragraph about how the Vibrant was released with 2.1 and then we fought for 2.2 only to be denied GB/ICS is in there to paint the picture of how consumer support has failed. It is specific to the Vibrant but the picture is for all Galaxy S users.
The CM team portion leaving the Vibrant is a problem (911/e911) that effects us all. For some reason they just dropped ONLY the Vibrant from their supported devices list b/c of this issue.
Still, we want to thank you for your support and help with this and hopefully they will at least listen to us.
Links to Samsung Twitter/Facebook/Google+:
Twitter:
- twitter.com/samsungtweets
- twitter.com/samsungmobileus
- https://twitter.com/SamsungJohn
- https://twitter.com/DigitalTrends
Facebook:
- www.facebook.com/SamsungUSA
- www.facebook.com/SamsungMobileUSA
Google+:
- https://plus.google.com/114303379611712597260/posts
let's be honest guys. Samsung did a logical thing by NOT giving us ICS update. I mean come on now.. even if they do decide to give us ICS, chances are it will be buggy as gs1 doesn't have enough memory to have ICS and TW... so really there is no point in giving us ICS, not only Samsung won't make any profit from doing this they might get flamed even more for making the phone slower buggier .. etc and
some people are saying they want stripped version of ICS on gs1 then why don't you just go buy yourself a nexus phone? Why would people buy nexus over galaxy when they're the same thing ? I could go on and rant about how samsung would have to meet terms with google, service providers and etc but ill stop here
Gingerbread from Samsung has been released. Rogers released it AGES ago.Gingerbread from AT&T has NOT been released.
your problem for Gingerbread is with AT&T. NOT SAMSUNG. Samsung released gingerbread to the carriers.
and to the post above, its not about buying an SG1 over a nexus, its about ALREADY OWNING SG1... and not enough memory for ics and touchwiz?? thats a propaganda lie. it would run fine. touchwiz consists of a launcher and a second (TW)framwork-res.apk and a few code changes to other system files. every rom has a laucher, so no loss there, wow extra 7mb framework... ohhh.. noo!
POST 3000!!!!!!
xriderx66 said:
Thank you.
Click to expand...
Click to collapse
Signed even though I don't own one. you guys should get updates too!!
Sent from my Nexus S using xda premium
TRusselo said:
Gingerbread from Samsung has been released. Rogers released it AGES ago.Gingerbread from AT&T has NOT been released.
your problem for Gingerbread is with AT&T. NOT SAMSUNG. Samsung released gingerbread to the carriers.
and to the post above, its not about buying an SG1 over a nexus, its about ALREADY OWNING SG1... and not enough memory for ics and touchwiz?? thats a propaganda lie. it would run fine. touchwiz consists of a launcher and a second (TW)framwork-res.apk and a few code changes to other system files. every rom has a laucher, so no loss there, wow extra 7mb framework... ohhh.. noo!
POST 3000!!!!!!
Click to expand...
Click to collapse
Just curious how do you know Samsung released GB to the carriers? Any sources?
EDIT: it is just me who finds big size fonts very irritating and irrelevant?
viny2cool said:
Just curious how do you know Samsung released GB to the carriers? Any sources?
EDIT: it is just me who finds big size fonts very irritating and irrelevant?
Click to expand...
Click to collapse
All carrier control the release of the updates, manufacturers create the updates for the phone, except for the Nexus line which is controlled by Google. The new exception to that might be the Verizon Nexus. The evidence is that the I-896 and I897 are the exact same phone, except one says ATT on the front.
Can someone explain this 911 issue? I mean how can you dial 911 and it won't work? IT seems like any number would work! I'm a bit confused by it, am I missing something? Thats seems like a phone being unable to dial, well Pizza hut, I dunno. It doesn't make sense.
Oh and I signed the petition.
Cor-master said:
Can someone explain this 911 issue? I mean how can you dial 911 and it won't work? IT seems like any number would work! I'm a bit confused by it, am I missing something? Thats seems like a phone being unable to dial, well Pizza hut, I dunno. It doesn't make sense.
Oh and I signed the petition.
Click to expand...
Click to collapse
I think its related to dialing 911 when u don't have any network. I mean when u don't have sim card you can still make emergency calls.
sent from my cappy rocking ICS
popfan said:
All carrier control the release of the updates, manufacturers create the updates for the phone, except for the Nexus line which is controlled by Google. The new exception to that might be the Verizon Nexus. The evidence is that the I-896 and I897 are the exact same phone, except one says ATT on the front.
Click to expand...
Click to collapse
I agree that they control it. But we don't know if Samsung actually gave it to ATT yet. Also there is no need of those kind of statements like in the post above my first post. No one is forcing him to sign the petition.
sent from my cappy rocking ICS
GB update (using KIES) for captivate:
http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00024051&fm_seq=24219
viny2cool said:
I agree that they control it. But we don't know if Samsung actually gave it to ATT yet. Also there is no need of those kind of statements like in the post above my first post. No one is forcing him to sign the petition.
sent from my cappy rocking ICS
Click to expand...
Click to collapse
I support this, samsung should definitely take some initiative in regards to their previous devices.
Signed!
Sent from my SGH-I897 using xda premium
I will always be your side.But is it useful?