Android 2.3 port from Nexus S to Galaxy S? - Galaxy S I9000 Q&A, Help & Troubleshooting

Hey guys,
what do you think, is it possible to port the Android 2.3 Gingerbread from Nexus S to our Samsung Galaxy S. Because it has a similar hardware!
/Discuss

You're fast , just wanted to ask this. Hope some legend dude will do this.

Theoretically it should be very simple to port the software. The only difference I can see from a hardware perspective is the NFC chip which simply needs to be disabled in software, and the missing search button which will need to be mapped to a menu long-press.
I did some work on the NITDroid project back when I had an N900, and neither of these is particularly difficult to do.

For nexus S info:
http://googleblog.blogspot.com/2010/12/introducing-nexus-s-with-gingerbread.html
http://www.google.com/nexus/#!/tech-specs
http://www.google.com/phone/compare/?phone=nexus-s&phone=samsung-galaxy-s

will the iNAND be a problem?

Supercurio says the devices use different types of memory.
Might be a bit of a problem

i can't see any reason we will have issues bringing it to the galaxy s line, especially if its the same SoC... and hardware, gps might be different, but thats a huge bonus anyways

Arkanius said:
Supercurio says the devices use different types of memory.
Might be a bit of a problem
Click to expand...
Click to collapse
yea the Nexus use the 16gb iNAND...

Since Samsung closely helped Google at making the hardware, hopefully we might have a quick 2.3 Samsung version for our devices
Which will then be easier to bring down to stock with the Cyanogen team progress

It must be far easier than a sense port or even cyanogen port.
Sent from my GT-I9000 using XDA App

One thing that also caught my eye was, that the video recording isn't HD... probably to not throw away boatloads of RAM for the camera...

Arkanius said:
Since Samsung closely helped Google at making the hardware, hopefully we might have a quick 2.3 Samsung version for our devices
Which will then be easier to bring down to stock with the Cyanogen team progress
Click to expand...
Click to collapse
I wouldn't bet on that. If Sammy released 2.3 in short order for the SGS it would cannibalize Nexus S sales. The aftermarket community is still the best bet.

binary110 said:
i can't see any reason we will have issues bringing it to the galaxy s line, especially if its the same SoC... and hardware, gps might be different, but thats a huge bonus anyways
Click to expand...
Click to collapse
GPS is the same! Both using A-GPS Chips. The NFC Software must be Disabled, Bluethooth Updated to 3.0, Nexus S has only 2.1 and Video Recording Updated to 1280x720, Nexus S had 720x480
Arkanius said:
Supercurio says the devices use different types of memory.
Might be a bit of a problem
Click to expand...
Click to collapse
Thats the biggest problem, I think. SuperCurios Tweet to iNand Tweet
Leandros

This a premature thread. Once a dump or aosp is released only then can we begin to do something about it. Till then this is a discussion thread and not related to development. IMHO

What about rfs? Im sure google is not using it. We will have to work that out as well.

2.3 SDK is out so I see no problem in getting gingerbread.
Whether as a port from the NS or a homebrew I don't really care.
All I want is the integrated SIP client. Been missing this since switching from my Nokia e90 Communicator to Android 1 year ago.
I am interested how the nexus S fares against a hacked Galaxy S, don't think it will be any faster!

Mycorrhiza said:
2.3 SDK is out so I see no problem in getting gingerbread.
Whether as a port from the NS or a homebrew I don't really care.
All I want is the integrated SIP client. Been missing this since switching from my Nokia e90 Communicator to Android 1 year ago.
I am interested how the nexus S fares against a hacked Galaxy S, don't think it will be any faster!
Click to expand...
Click to collapse
Everything is virtually the same.

I call up one the powers of the all powerful XDA to port the N:S for all the SGS's that are out there, so we can forget about samsung roms and use a normal google one

The Nexus S doesn't seem to support an external sd card. Likely another problem?

bigriot said:
The Nexus S doesn't seem to support an external sd card. Likely another problem?
Click to expand...
Click to collapse
Maybe... but I can live without an external SDCARD for now...

Related

(discussion) Rom development for Galaxy

Or rather lack of it.
I start of by saying, i am not a dev.
But i see that the way rom's is made for Galaxy lack's most of the things that makes custom rom's good, SGS's rom's seem more themes than proper custom rom's.
I have used Nexus and some of the great rom's to that device.
The SGS way to update FW seems to stop all real development?
What do you think?
samsung's drivers are encrypted and this makes developing roms pretty difficult. there can only be roms based on samsung releases. at least this is what i understood .
i am sure that the growing user base of this great phone will bring more attention from great developers ( hi paul ! , who will be able to overcome most of the problems and give us great roms.
The final non-beta firmware from Samsung hasn't even arrived yet! Give it some time!
Custom roms now would be obsolete within one week because of a newer official beta Firmware.
I was aware that a few days ago paul obrien was having a conversation to cyanogen about creating a vendor tree for the sgs which would enable us to use cyanogen mod. If someone can confirm this with paul this would be very good news for us sgs owners.
Sent from my GT-I9000 using XDA App
Right now I'd settle for a vanilla Froyo (my last phone was the N1).
The SGS has potential, but the stock ROM is so infested with Samsung customisations (eg non- AOSP dialer, contacts, music, etc etc), why have they re-invented the wheel?? Before this phone I didn't think fragmentation existed, only "legacy". Now I know exactly what fragmentation is, and it's ugly, annoying.
The only reason I ditched the N1 is because Google have said there would be no N2 so I figured I find another phone.
Now I realise how bad fragmentation is, the iPhone really doesn't look so bad again ... (previous to the N1, I was on a iPhone 3G)
It's a pity vendors can't be mandated to supply optional vanilla ROMs - I know Samsung have released a bunch of source code, maybe that's a start.
I guess I'll give it six months. I'm an end-user who wants an easy life, but appreciates the potential and integration with google services that Android provides - moreso in its vanilla form.
Did anybody try compiling the sourcecode that was released by samsung to create a flashable working version of the manufacturer Android version that is currently running in our phones?
If that is possible, and we do have the source code from samsung, I don't see why it would be impossible to get at least a vanilla AOSP 2.1-update1 running on our galaxies.
The encrypted (or closed source drivers) can be linked as binaries to the new AOSP build running on top of Samsung's kernel (which we do have the source code to).
Side question, anybody knows how to flash the phone once you got all source code by samsung compiled ? I know we end up with a zImage, possibly a system.img.. can you create Odin files with these easily ? any thoughts?
miker71 said:
Right now I'd settle for a vanilla Froyo (my last phone was the N1).
The SGS has potential, but the stock ROM is so infested with Samsung customisations (eg non- AOSP dialer, contacts, music, etc etc), why have they re-invented the wheel?? Before this phone I didn't think fragmentation existed, only "legacy". Now I know exactly what fragmentation is, and it's ugly, annoying.
The only reason I ditched the N1 is because Google have said there would be no N2 so I figured I find another phone.
Now I realise how bad fragmentation is, the iPhone really doesn't look so bad again ... (previous to the N1, I was on a iPhone 3G)
It's a pity vendors can't be mandated to supply optional vanilla ROMs - I know Samsung have released a bunch of source code, maybe that's a start.
I guess I'll give it six months. I'm an end-user who wants an easy life, but appreciates the potential and integration with google services that Android provides - moreso in its vanilla form.
Click to expand...
Click to collapse
same here. previous n1 user, got sgs just after google announced no n2 wil be available.
just took some actions to make things smoother for me :
1. launcher pro
2. dialer one
3. handcent sms
i used them all on n1 and now i do on sgs. its all good again . still, untill froyo hits us i think i will still miss n1's speed. also, i think after froyo hits us, we will get some more roms and goodies for our phones.
what exactly is a vendor tree? and how would it be able to get around the driver issue which is apparant to the SGS?
Some info on the .rfs files that samsung uses:
http://movitool.ntd.homelinux.org/trac/movitool/wiki/RFS
Merging into AOSP
It seems like good idea to have the scripts merged into AOSP tree that support building stock ROMS for samsung galaxy s, with binary-only files being downloaded directly from the device (if I'm not mistaken, this is how one can build froyo for N1 from source now).
From someone else experience: would the patches that add vendor-specific support for SGS be accepted into AOSP tree? Are there known blockers for this?
Hmm.. rom development is quite sluggish due to the firmwares that are being released!
But i really don't care! the original rom is fine with WJG5!
I just use Launcher Pro and widgets to make it better! Speed is ok!
bratfink said:
I was aware that a few days ago paul obrien was having a conversation to cyanogen about creating a vendor tree for the sgs which would enable us to use cyanogen mod. If someone can confirm this with paul this would be very good news for us sgs owners.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
This still doesn't get around the fact that the drivers are locked down and are near impossible to implement into outside roms that aren't Samsung based. Talking isn't doing anything.
miker71 said:
Right now I'd settle for a vanilla Froyo (my last phone was the N1).
The SGS has potential, but the stock ROM is so infested with Samsung customisations (eg non- AOSP dialer, contacts, music, etc etc), why have they re-invented the wheel?? Before this phone I didn't think fragmentation existed, only "legacy". Now I know exactly what fragmentation is, and it's ugly, annoying.
Click to expand...
Click to collapse
This isn't fragmentation though, this is exactly what Google wanted Android to be - a base for phone manufacturers to lay their own tweaks on top of. HTC, Motorola, Samsung etc don't just want to be differentiated by how their handset looks, they want to put their own stuff on there too. Previously each had their own OS (Symbian, UIQ etc.) that took years of development time and was very slow moving. Google provided Android as a quick route to market for a phone, the manufacturers didn't really have to worry too much about the OS and then get lots of apps for free.
The thing is, the vanilla apps are a bit.. basic. The standard music player is fine, it works and does what it says on the tin. The standard contacts is fine again etc. Makers can ship a ROM based on vanilla Android and it would be good to go, but if they can improve upon the apps and brand it slightly more then all well and good.
But it's not fragmentation. Android is a base. A starting point. It's not meant to look exactly the same on every device, but it's meant to work exactly the same as much as possible. These manufacturers get a stable, standard, capable phone OS for free, which to them is awesome. It saves them so much time and is ultimately why eventually there will be nothing but Android on devices. It's the Mac vs PC all over again - cool but closed and restricted vs ubiquitous free-for-all.
psychoace said:
This still doesn't get around the fact that the drivers are locked down and are near impossible to implement into outside roms that aren't Samsung based. Talking isn't doing anything.
Click to expand...
Click to collapse
If the right people get onto it it's only a matter of time. The G1 camera drivers were reverse engineered for Eclair CM ROMs after HTC gave the community sod-all.
dirk1978 said:
If the right people get onto it it's only a matter of time. The G1 camera drivers were reverse engineered for Eclair CM ROMs after HTC gave the community sod-all.
Click to expand...
Click to collapse
Didn't they have the source for 1.6's camera drivers? At least then they had a base to start from. That is not true with Samsungs drivers.
A little bit OT but due to the fact that in this thread are some EX-Nexus users: Would you recommend switching to the SGS ?
dirk1978 said:
it's meant to work exactly the same as much as possible.
Click to expand...
Click to collapse
It's when it doesn't work, it's very very annoying. How long do we have to wait for the Samsung music player to enable scrobbling? Sure I can use a different app from the Market - meaning Samsung wasted effort on their own Music app, why didn't they build on the AOSP version which does support scrobbling and iSyncr, etc because they use standard API or whatever so these other programs can read the state or whatever they need to do.
Same with dialer and contacts - on Launcher Pro, pressing the default Contacts icon - won't get you anything except maybe a FC :-(
The AOSP Desk Clock - where is that? If I install a clock from Market then I have two different Alarm daemons which is a waste of everyone's time when the default Clock in AOSP Eclair is fine and - more importantly - compatible with stuff and API calls.
Then all the other stuff that may or may not be Samsung stuff - the DRM, the Device Management, the Samsung Account - given the option I just don't want that stuff.
I'm intending to flash JG5 (from factory shipped JF3) which may increase performance but presume won't make these other problems go away.
I'm really happy with the hardware - but currently I am dissatisfied with the software and "Samsung knows best". For me, personally, Google knows best (and I bet they have data on me to prove it!), so I really want to see Froyo AOSP version for the Galaxy. That day may come, or it may not ...
I know I know, "can't please all of the people all of the time"
PAO1908 said:
A little bit OT but due to the fact that in this thread are some EX-Nexus users: Would you recommend switching to the SGS ?
Click to expand...
Click to collapse
Right now the question for me would be "do I recommend switching from Samsung OS from Froyo" - my answer would be no, unless:
1. better multitouch is important to you (better for gaming, no axis mess-up)
2. 4" screen is important (I do really like the Samsung screen)
3. Better built-in audio quality is important (the Galaxy is noticeably louder than the N1 and I think it may have a better A/D sampler too)
So fully recommend switching for hardware, UNLESS you can't live without Froyo.
I can live with the SGS shortcomings. Well, for a few months anyway ... and even if AOSP never comes there are alternatives in the Market but does mean you have to ignore the Samsung stock apps depending what you want to do (which means added complexity to your life, which I don't always have time to deal with!)
psychoace said:
This still doesn't get around the fact that the drivers are locked down and are near impossible to implement into outside roms that aren't Samsung based. Talking isn't doing anything.
Click to expand...
Click to collapse
Do you have any proof that the drivers are actually locked down in any way?
I can see the source of all the modules provided by samsung, just 3 of them (pvrsrvkm, s3cbc and s3clcd) are just precompiled, and if you check the info they are GPL.
Am I missing something?
@miker71
Thanks a lot !

[Q] nexus one and gingerbread - past and future?

if gingerbread is the future of android devices, it suppose to support hardware capabilities that may not be on the nexus that has been around for a while.
i really wanted to buy a nexus, but it seems that when android 3.0 is out - it should be followed by high end devices by HTC and others.
i really don't know what to do here...
gingerbread is said to launch mid november - not a long time to hold off.
but hey, what do think? wait or buy nexus now?
That is Exactly what I am doing! The desire HD looks wonderful, but i think There will be a VERY nice phone coming on T mobile with new gingerbread already there around Christmas....Just my guess
It seems T mobile and Google have some sort of special deal when it comes to android, like getting stock android phones.....and there MUST be a stock gingerbread phone coming soon!
oronm said:
if gingerbread is the future of android devices, it suppose to support hardware capabilities that may not be on the nexus that has been around for a while.
i really wanted to buy a nexus, but it seems that when android 3.0 is out - it should be followed by high end devices by HTC and others.
i really don't know what to do here...
gingerbread is said to launch mid november - not a long time to hold off.
but hey, what do think? wait or buy nexus now?
Click to expand...
Click to collapse
First, Gingerbread will run fine on a N1. Second, no matter when you buy a phone in a couple months another one will come out that is even better. The N1 has an awesome modding scene though.
First, Gingerbread will run fine on a N1.
Click to expand...
Click to collapse
nobody know that for sure...the minimal requirements may suit the N1 but it may lack the ability to perform certain tasks. we've seen it happen with other phones.
Second, no matter when you buy a phone in a couple months another one will come out that is even better
Click to expand...
Click to collapse
true for most cases. to me nexus is different from others by design. that phone feels right. i really couldn't care less about all these samsungs or motorolas that are out there. and other htc devices seem too big like the desire HD that was mentioned.
basicly, the world need a NEXUS TWO!
So you think Google will develop an OS using their development phone, but not all features of the OS will work on the phone they developed it on? I highly doubt that. Google debunked the minimum requirements roomer for Gingerbread, that was nothing but a site trying to get traffic. Do a little thinking on the subject.
If I were getting a new phone soon though, I would wait till the next gen ones come out. I do love my Nexus though!
the nexus one was a success in regard of telling the world "this is what android can do right now". others did follow and it is biting the market share making other mobile OS look like code accidents.
none the less, why shouldn't gingerbread allow "facetime like" video service for capable devices? the technology for that is in the wild. that is only one example. i am sure there are more features just like that.
at this point, maybe it would be smarter to wait.
oronm said:
the nexus one was a success in regard of telling the world "this is what android can do right now". others did follow and it is biting the market share making other mobile OS look like code accidents.
none the less, why shouldn't gingerbread allow "facetime like" video service for capable devices? the technology for that is in the wild. that is only one example. i am sure there are more features just like that.
at this point, maybe it would be smarter to wait.
Click to expand...
Click to collapse
Whether or not Gingerbread includes a facetime like option is irrelevant to how it will run on the N1. Obviously any phone without a front-facing camera will not be able to do something like facetime. Gingerbread itself will run just fine on the N1. Without going into any technical reasons, just think of this. Of all the Android phones out there right now, the top ones are all in the general vicinity of the N1 in performance. If Gingerbread wouldn't run on the N1, then you cut out these phones too which means only as-yet-unreleased phones would run Gingerbread. So on what basis are you questioning it?
You should probably wait though since you don't seem sure about the N1. The only guarantee you can have is that in a few months from now an even better phone will be released. And then a few months from that once again, and repeat... Dual core snapdragons will start finding their way into phones at some point soon. If you're not rushed then just wait and see what comes out.

Nexus one and future versions of android

Gingerbread will most likely be brought to the nexus one but what about 3.0 and beyond? Do you think they will make a new device? Possibly the n2? What about tablets? Will they start a new android line just for tablets. The android phpne market is very spread out right now, phones like the Motorola charm will probobly never see froyo but phones like the Droid x and vibrant have processors that will not become outdated for several years to come. Are company's updating hardware too quickly?
This is the development forum. You want the q n a forum.
Sent from my Nexus One
mnv710 said:
Gingerbread will most likely be brought to the nexus one but what about 3.0 and beyond? Do you think they will make a new device? Possibly the n2? What about tablets? Will they start a new android line just for tablets. The android phpne market is very spread out right now, phones like the Motorola charm will probobly never see froyo but phones like the Droid x and vibrant have processors that will not become outdated for several years to come. Are company's updating hardware too quickly?
Click to expand...
Click to collapse
*sigh*
There is a general section, you know...
mnv710 said:
Gingerbread will most likely be brought to the nexus one but what about 3.0 and beyond? Do you think they will make a new device? Possibly the n2? What about tablets? Will they start a new android line just for tablets. The android phpne market is very spread out right now, phones like the Motorola charm will probobly never see froyo but phones like the Droid x and vibrant have processors that will not become outdated for several years to come. Are company's updating hardware too quickly?
Click to expand...
Click to collapse
The HTC magic, the 2nd ever android phone, got official Froyo. If a phone isn't getting it, its not because it's underpowered (with the exception of the G1).
B3astofthe3ast said:
The HTC magic, the 2nd ever android phone, got official Froyo. If a phone isn't getting it, its not because it's underpowered (with the exception of the G1).
Click to expand...
Click to collapse
Huh? The magic is a G1 less the keyboard. Processor is the same. And I think a rooted G1 can have 2.2.
Sent from my Nexus One using XDA App
HTCinToronto said:
Huh? The magic is a G1 less the keyboard. Processor is the same. And I think a rooted G1 can have 2.2.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
The G1 is memory starved. A rooted G1 can have froyo with the proper SPL.
We will get every future Android update.
Gingerbread, Honeycomb, IceCream, Jellybean, K..., L..., Mousse, Pie, Q..., ...
I don't think there needs to be a tablet developer platform designated. Screen resolution differences are something that should be simple enough d'or developers to figure out.
The entire point of a developer platform device is to develop the core OS updates on it, so I fully expect at least another year of official updates for the N1. Especially because we haven't actually seen any faster processor released into the market yet.
The secondary point of a designated developer platform would be to support a core of standard hardware under Android. Smarter OEMs should understand that if they want to have less work to port android to their devices, and to get updates on their devices more quickly, they should try to use hardware components either common to ADP or that have Linux support.
Sure, OEMs can deviate, but anything they include that isn't either compatible with ADP hardware, or already supported in Linux will have to be supported by the company making that handset. So it is up to the consumers to say if they want devices more like the Desire, or more like the X10. Laf!
The Nexus One is the official Google Development phone. Until that changes, we shouldn't have to worry about getting the latest versions first
It is one of the advantages to being a N1 owner.
xPatriicK said:
We will get every future Android update.
Gingerbread, Honeycomb, IceCream, Jellybean, K..., L..., Mousse, Pie, Q..., ...
Click to expand...
Click to collapse
Deserts are my N1's favorite meal!
Android mean Google, then there is no point to buy any phone even if it's amazing, i am with Google devices till they close the company N1 TO N100 i am with Google i just want they put some color in this coming build i feel the stock ROM is black and white

Nexus 1 Updated to 2.2.2 Nexus S 2.3.2 What about Galaxy S ?

Just read the news about these two getting the update that fixes the SMS bug but no mention of any other 2.2.x O/S'd phones getting it. Can't be far off surely?
http://phandroid.com/
I just want that SMS fix, I've seen two I9000Ms do it. I pinged Samsung Canada on Twitter, we'll see what their response is.
v.2.3 2012
v2.4 2022
v3.0 2050
maybe
My20 said:
v.2.3 2012
v2.4 2022
v3.0 2050
maybe
Click to expand...
Click to collapse
maybe ayes maybe naws
My20 said:
v.2.3 2012
v2.4 2022
v3.0 2050
(American variant releases not guaranteed)
Click to expand...
Click to collapse
Fixed that for you.
i somewhere read that we can expect 2.3 for SGS for the end for the first quarter of the year...but are you people using stock ROMS ? i think Darky's ROM is working on a multi-device able to detect and flash devices accordingly, shouldn't that fix your sms problems ?
ps: i have the i9000, but what is "the sms problem", i don't think i have it..
Everybody bug samsung to skip 2.3 and prep for 3.0.
With carriers charging 15-20¢/SMS and having a free replacement (google voice, google talk, emails)
I really couldn't care less about SMS. I should even remove the SMS app from my phone.
Why do y'all want honeycomb (3.0), it's for tablet, not SmartPhones :|
t1mman said:
Why do y'all want honeycomb (3.0), it's for tablet, not SmartPhones :|
Click to expand...
Click to collapse
It's for both.
t1mman said:
Why do y'all want honeycomb (3.0), it's for tablet, not SmartPhones :|
Click to expand...
Click to collapse
So wrong, it hurts.
rumor
the rumor is here :
i like the way they say
"site called SamFirmwares – one we’ve never heard of before."
Click to expand...
Click to collapse
they better all listen to these site ! i wonder how these big companies would react to
all the amazing roms out there !
JCopernicus said:
So wrong, it hurts.
Click to expand...
Click to collapse
Is it? Then prove me wrong...
From google:
Honeycomb is the next version of the Android platform, designed from the ground up for devices with larger screen sizes, particularly tablets.
Click to expand...
Click to collapse
http://googlemobile.blogspot.com/2011/01/sneak-peak-of-android-30-honeycomb.html
That's the reason Google is naming "honeycomb" 3.0, and later Tablet optimisez releases will be 3.x where smartphone will stay on 2.x
Before saying crap at one another, do some research...
t1mman said:
Is it? Then prove me wrong...
From google:
http://googlemobile.blogspot.com/2011/01/sneak-peak-of-android-30-honeycomb.html
That's the reason Google is naming "honeycomb" 3.0, and later Tablet optimisez releases will be 3.x where smartphone will stay on 2.x
Before saying crap at one another, do some research...
Click to expand...
Click to collapse
It's literally hurting my brain that you think that. Check back after 3.0 line is cut and put up on AOSP, you'll see all the honeycomb roms(for phones) floating around.
JCopernicus said:
It's literally hurting my brain that you think that. Check back after 3.0 line is cut and put up on AOSP, you'll see all the honeycomb roms(for phones) floating around.
Click to expand...
Click to collapse
You can get rom floating around of about anything, doesn't mean it's made for it... You can even get a whole Linux distrubution working on SGS, still it's not "official" or optimised...
Still, nothing will be official and Honeycomb is still optimised for Tablet. I don't know why your "brain hurts", but when google sais their thing is optimised for something, since they made the thing, you'd better beleive them!
hell, you can put a Corvette engine in a Civic, still it's not meant or optimised for.
t1mman said:
You can get rom floating around of about anything, doesn't mean it's made for it... You can even get a whole Linux distrubution working on SGS, still it's not "official" or optimised...
Still, nothing will be official and Honeycomb is still optimised for Tablet. I don't know why your "brain hurts", but when google sais their thing is optimised for something, since they made the thing, you'd better beleive them!
hell, you can put a Corvette engine in a Civic, still it's not meant or optimised for.
Click to expand...
Click to collapse
http://developer.android.com/sdk/android-3.0-highlights.html
Honeycomb adds "tablet" (ie big screen) specific support. It's not an independent branch, feature sets will trickle down accordingly to phones, they will both be 3.0.
P.S. A rom built from AOSP is as official as you can get in regards to Android.
JCopernicus said:
http://developer.android.com/sdk/android-3.0-highlights.html
Honeycomb adds "tablet" (ie big screen) specific support. It's not an independent branch, feature sets will trickle down accordingly to phones, they will both be 3.0.
P.S. A rom built from AOSP is as official as you can get in regards to Android.
Click to expand...
Click to collapse
You can't read title can't you?
"New UI designed from the ground up for tablets"
The reason it's (honeycomb) taking another number (3.0) instead of following the same (2.x) is because it's for tablets...
as far as AOSP vs. Official, their's a huge difference between official source code (from google) vs official rom (from samsung).
I can't tell the future, but I can most certainly say that Kies would offer 2.4 hell before 3.0 for our devices (which are smartphones, not tablet).
t1mman said:
You can't read title can't you?
"New UI designed from the ground up for tablets"
The reason it's (honeycomb) taking another number (3.0) instead of following the same (2.x) is because it's for tablets...
as far as AOSP vs. Official, their's a huge difference between official source code (from google) vs official rom (from samsung).
I can't tell the future, but I can most certainly say that Kies would offer 2.4 hell before 3.0 for our devices (which are smartphones, not tablet).
Click to expand...
Click to collapse
The large screen views (which never existed) are built from the "ground up" because, guess what? They never existed in the first place.
The reason it's taking 3.0 is because it's a huge jump in feature set, and qualifies as a version realease and not just a point release.
If a device has a certain feature it can access certain API from the android OS. If a device doesn't, then it can't. It's that simple.
"tablets" have the big screen feature and they can access the nested view API's. You don't know how android works. there is ONE line, which sits at 2.3.2, and it's device independent.
Just like the Nexus S can access the NFC api's because it has an NFC chip.
AOSP is the code that google/samsung/moto/acer/etc pull from, and build more on top.
Cyanogen roms are on par and equivalent(better actually) as google's roms, you can't get more "official" than AOSP. MFG roms are actually less true to AOSP as they are modified. You probably won't see 3.0 on the current galaxy line at all, but that has nothing to do whether it works on there or not.
Chill out dude! Take a deep breath....
This is getting nowhere, running in circle...
I'm pretty sure we won't see Honeycomb as a release by the makers (Samsungs, Motorola, LG, HTC, name em) on any smartphone. Don't know why this is such a big deal for you and what you don't get on the whole deal but if you want,
You can bookmark this thread and if you see an official honecomb as an official release by samsung or LG or HTC or google on a Smartphone, revive it from the archives and rub it on my face, I'll gladly take the fall...
Chill out? I think I'm just typing normally on a keyboard? Maybe I'm smashing keys, and don't recognize it?
You don't understand how android works if you think it won't appear on phones, we're not going around in circles. You're just wrong.

Android 4.0 Source

Android 4.0 Source is out! Any chance to get this in the LG Thrill 4G I would definitely be keeping it then.
Sent from my LG-P925 using xda premium
I was wondering the same thing. if this is possible I might not even update it to GB cause it wouldnt make sense. Hopefully its possible.
Its as possible as the source for GB turning into a GB update. That is to say, no its not possible.
LG needs to make the update and bake in the drivers. It took them a few days shy of a year for GB, maybe they can shave that down to 9 months for ICS. So, as Google announces 4.1, start looking for 4.0.
The Galaxy Nexus is not going to provide any ports to the Thrill, or any other device. Its the only device using that CPU/GPU combo. Its the only device to date with its CPU at all (processor in Thrill is different model number 4460 vs 4430, it may as well be entirely different) If ICS is your goal, the Galaxy Nexus is the fastest and easiest way. Otherwise you play the waiting game for the OEM to put out the update, then wait some more for the carrier to bloatify it, then wait some more for the small base of devs to de-bloatify it.
Sent from my Galaxy S II (i777)
quarlow said:
Its as possible as the source for GB turning into a GB update. That is to say, no its not possible.
LG needs to make the update and bake in the drivers. It took them a few days shy of a year for GB, maybe they can shave that down to 9 months for ICS. So, as Google announces 4.1, start looking for 4.0.
The Galaxy Nexus is not going to provide any ports to the Thrill, or any other device. Its the only device using that CPU/GPU combo. Its the only device to date with its CPU at all (processor in Thrill is different model number 4460 vs 4430, it may as well be entirely different) If ICS is your goal, the Galaxy Nexus is the fastest and easiest way. Otherwise you play the waiting game for the OEM to put out the update, then wait some more for the carrier to bloatify it, then wait some more for the small base of devs to de-bloatify it.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
thank your for you input on this matter. Can you please tell me which Galaxy S II is better i777 or the i727 because I am thinking of returning my LG Thrill 4G for the Skyrocket?
The skyrocket has lte actual 4g that if the only difference add far as performance
Sent from my LG-P925 using xda premium
kleeman7 said:
The skyrocket has lte actual 4g that if the only difference add far as performance
Sent from my LG-P925 using xda premium
Click to expand...
Click to collapse
That's the only difference in data speed. That's also the only area the i727 is better. In EVERY other way the i777 is better.
They have the same screen resolution, but because the 727 screen is bigger, so the pixel density is lower, most people won't notice, but its worth mentioning.
The processor in the 727 is a qualcomm chip oc'd to 1.5 GHz, vs a Exynos chip at 1.2 GHz. People say the qualcomm chip is inferior, and choppy. Most people won't notice it, but it is there. The exynos can be oc'd higher than the qualcomm chip. The qualcomm chip is the reason it won't get i777 or i9100 ROM ports. With the i777 and i9100 running the same chip you can port any i9100 ROM really easy.
I don't know specifics on GPU, but its widely accepted the i777 has better graphics and 3D processing.
The 777 is thinner and lighter.
They both have disabled nfc on board. Att to possibly unlock at a later time, maybe at ICS rollout.
If you have LTE coverage you need to think about the choice, if you don't have LTE, there is absolutely no reason to get the 727. I talked a little about other differences in your other thread.
Sent from my Galaxy S II (i777)
quarlow said:
Its as possible as the source for GB turning into a GB update. That is to say, no its not possible.
LG needs to make the update and bake in the drivers. It took them a few days shy of a year for GB, maybe they can shave that down to 9 months for ICS. So, as Google announces 4.1, start looking for 4.0.
The Galaxy Nexus is not going to provide any ports to the Thrill, or any other device. Its the only device using that CPU/GPU combo. Its the only device to date with its CPU at all (processor in Thrill is different model number 4460 vs 4430, it may as well be entirely different) If ICS is your goal, the Galaxy Nexus is the fastest and easiest way. Otherwise you play the waiting game for the OEM to put out the update, then wait some more for the carrier to bloatify it, then wait some more for the small base of devs to de-bloatify it.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
Did you check the TI site and read the 4460 documentation? The processors are almost identical. The 4460 is just a little more capable. Its still in the OMAP4 family with the exact same architecture. We'll have the LG gingerbread drivers shortly as well as the galaxy nexus ICS drivers which will get us started there. Kernel shouldn't be too big of an issue as again, same architecture on CPU, same exact gpu. Yea its gonna take a lot of time to get everything working but we don't need LG to do it. GB was more of a shot in the dark for this phone than ICS will be. Zero omap4 devices released with GB but it still got ported to a couple Motorola devices. ICS released for two devices, both omap4.
Sent from my LG-P925 using Tapatalk
I said this about GB too. I hope I'm wrong for all of your sake's. When people were saying GB was around the corner (in September), and I said December, people said I was being too cynical. Well ... here we are, December is right around the corner, and the GB port is not flashable in CWM, nor is it complete. I over-cynicized a little, but not much.
I think it's all great on paper, just like building a AOSP GB build for the phone looked simple, did that ever actually get off the ground?
As I look in the past, I use that to forecast the future. My guess is that there is no where near a functional daily use ROM for the Thrill until a ICS build comes from LG (I would guess no sooner than July). If the the Nexus S and Captivate running the exact same hardware (CPU/GPU plus lots of others) both made from the same company, cannot share ROMs with lots of dev support, I just find it hard to believe that a phone with a similar chip, packaged with other chips (WiFi, BT, USB, Power, comination unknown) by another OEM is not going to provide useful drivers for the small dev community here. Again, I would love to be wrong, but ...
To be honest I think the Thrill is more Thrilling (rim-shot) because it's an underdog, and it feels like a start-up, ground-floor opportunity to build and jury rig everything and frankenstein it together. I think it would be fun, and I would have loved to have been involved had I stayed. But, I moved on, as many others have. I can't wait for months for something like this when I will only have that phone for a year. I don't hang on to old tech, I sold my Captivate and it paid for my Galaxy S II, talk about the circle of life.
The Thrill is definately an underrated phone, but it's also not the highest end phone. As I said before, as it stands it's definately the best AT&T phone for less than $100, it's the king of the mid-range offerings. Unless you can get the i777 for $50 or less, like many places have advertised for Black Friday.
I wish everyone the best of luck with the Thrill, but the reality train is leaving the station, and I feel my welcome may just be wearing thin here.
It seems that LG doesnt really care about the consumer because they release a phone and update the firmware when its not even new anymore and its funny because it seems like the Thrill will be getting GB and everyone else will be getting ICS. =(
Demonface said:
It seems that LG doesnt really care about the consumer because they release a phone and update the firmware when its not even new anymore and its funny because it seems like the Thrill will be getting GB and everyone else will be getting ICS. =(
Click to expand...
Click to collapse
it'll be about 3-8 months before other devices will recieve ics. samsung has the same problem. they still haven't updated the charge, fascinate, captivate and infuse.
tampaboy1984 said:
Android 4.0 Source is out! Any chance to get this in the LG Thrill 4G I would definitely be keeping it then.
Sent from my LG-P925 using xda premium
Click to expand...
Click to collapse
Yes it will Ricardo from the cyanogenmod team in charge of lg devices posted a video on YouTube showing ICS running on the O3D. He posted on his google + that it took him a couple of hours to get the touchscreen working but it shows you that work has begun and we might see ICS sooner than you think.
Sent from my LG-P920 using XDA App
AeRo0 said:
Yes it will Ricardo from the cyanogenmod team in charge of lg devices posted a video on YouTube showing ICS running on the O3D. He posted on his google + that it took him a couple of hours to get the touchscreen working but it shows you that work has begun and we might see ICS sooner than you think.
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
i got so excited when i saw his videos of it on the o3d i almost jumped and threw my laptop!!! hahaha
Trekfan422991 said:
i got so excited when i saw his videos of it on the o3d i almost jumped and threw my laptop!!! hahaha
Click to expand...
Click to collapse
This is after all the reason why I got this phone cuz of the chipset and the fact that ICS is designed for it
Sent from my LG-P920 using XDA App
AeRo0 said:
Yes it will Ricardo from the cyanogenmod team in charge of lg devices posted a video on YouTube showing ICS running on the O3D. He posted on his google + that it took him a couple of hours to get the touchscreen working but it shows you that work has begun and we might see ICS sooner than you think.
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
Thats very good news , Hopefully it gets released soon. Instead of using GB I would go straight to ICS when its released. Does anyone have the link to the video because I cant seem to find it.
Those types of ports that are half functional are popping up every where for tons of phones.
They will not support some basic phone functions for months. There is no way 3D will work until LG builds the drivers, and they won't release them until they release the full ICS update. Things like WiFi, Bluetooth, GPS, data, etc will all (or mostly) be missing for quite a while. Making ICS run and making a daily driver with ICS are two very different things.
I watched that video, there is already a comporable port running on the i9100. Proof that both using similar but different omap4 processors means nothing. The processor is the most simple basic part of the functionality, its everything else that's going to be hard.
Try to keep some perspective, and realistic hopes.
Sent from my Galaxy S II (i777)
quarlow said:
Those types of ports that are half functional are popping up every where for tons of phones.
They will not support some basic phone functions for months. There is no way 3D will work until LG builds the drivers, and they won't release them until they release the full ICS update. Things like WiFi, Bluetooth, GPS, data, etc will all (or mostly) be missing for quite a while. Making ICS run and making a daily driver with ICS are two very different things.
I watched that video, there is already a comporable port running on the i9100. Proof that both using similar but different omap4 processors means nothing. The processor is the most simple basic part of the functionality, its everything else that's going to be hard.
Try to keep some perspective, and realistic hopes.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
seriously i know your trying to help us keep a grip on our excitement.. but its starting to get annoying seeing your comments pop up here all the time after you switched weeks ago.. and they are all how the thrill has potential but im so happy with my choice... like we cant even get our hopes up because your too afraid of our dreams getting dashed to pieces... we should all follow your example. i know thats not what you mean but it feels that way...
like many others i choose this phone based off the hardware specs... so i will be sticking it out for a few months at least if not for a few years.
we know the decision you made to switch and that you have support for the thrill and knew it to be a good device.. there is no rule about posting in forums for phones you dont have.. but please... please ease back a bit on clarifying all the realities for us...
there is nothing wrong in wishing.. we had no development for ages, it feels like, and now we have some things to look forward too, thats all!
so give us our hopes please... *tears up* its all we have!
quarlow said:
Those types of ports that are half functional are popping up every where for tons of phones.
They will not support some basic phone functions for months. There is no way 3D will work until LG builds the drivers, and they won't release them until they release the full ICS update. Things like WiFi, Bluetooth, GPS, data, etc will all (or mostly) be missing for quite a while. Making ICS run and making a daily driver with ICS are two very different things.
I watched that video, there is already a comporable port running on the i9100. Proof that both using similar but different omap4 processors means nothing. The processor is the most simple basic part of the functionality, its everything else that's going to be hard.
Try to keep some perspective, and realistic hopes.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
He's a legit cm dev. Its NOT a half functional port. Its the beginning of an ICS source build a day after source was released. It took him a few hours to get touchscreen working. Its NOT one of the fake SDK ports that have been floating around. They've already said it will be ATLEAST 2 months before we should even start expecting any updates on cm9. Hows your build of ics going? Your claims on timeline, etc, MUST be based on your own firsthand progress, correct? You are actually contributing something to the community with all your development knowledge, correct?
You claim to be saving us from false hopes. But the way I take that is that you are assuming we as a community are to ignorant and naive to realize the time/process of getting a new OS on a new device. NOBODY here has said we expect this to be a rapid process. We know it takes time.
Hop on your faux white horse and ride back over to your fanboy forum. You've contributed absolutely nothing to this forum and I assume the same is probably true there. But seeing how as you actually have that phone you have a reason to lurk over there.
Sent from my LG-P925 using Tapatalk
Wait wait wait...
You mean AT&T doesn't give super fast firmware updates to their phones?!
Here's what I will say about this phone so far...
I like it. It's treated me better than any Samsung phone I've had. It does everything I need it to.
I can't really remember ever saying "I wish this phone could..." that I wouldn't say about any other phone.
I hear people talk about how fast this phone is and that phone is and how fast the GSII compared to the Thrill. But how much faster is faster? The web browser pops up a second faster? A file is downloaded 10 seconds faster? I don't really think a lot of that is that big of a deal. It almost reminds me of the Crackberry forums when they were talking about not going to Android because the email isn't push (which isn't true) and so you got your emails a whole 30 seconds later. I mean, c'mon, how many of us are in a position where if we don't get that email 30 seconds faster our entire corporation loses billions?
I think it'd be cool to get 2.3 or above right now because there are a couple of games I'd like to play that are on 2.3 or above. But considering I have 25 games already installed and over 1/2 of those I ahven't touched, it's okay.
I've had a few Samsung phones and everyone of them I had had a lot of issues. I went through 8 Captivates. Now I did have to return one Thrill and exchange it but every Samsung phone I've had, I've had to get replaced at least twice. I keep saying I want a Note but then think about how bad I've had it with Samsung phones.
Phone technology is crazy. The thrill came, then the GSII, then the GSII skyrocket and the HTC Vivid, then there are three new Galaxy devices coming to AT&T in the next 2-3 months, and whatever awesome quad core devices, and then pretty soon we'll have the hologram phones in which you tell the phone to contact someone and they pop out of the phone like in Star Wars.
Honestly, I think I need a couple more pairs of shoes more than I need a newer phone.
CallMeAria said:
He's a legit cm dev. Its NOT a half functional port. Its the beginning of an ICS source build a day after source was released. It took him a few hours to get touchscreen working. Its NOT one of the fake SDK ports that have been floating around. They've already said it will be ATLEAST 2 months before we should even start expecting any updates on cm9. Hows your build of ics going? Your claims on timeline, etc, MUST be based on your own firsthand progress, correct? You are actually contributing something to the community with all your development knowledge, correct?
You claim to be saving us from false hopes. But the way I take that is that you are assuming we as a community are to ignorant and naive to realize the time/process of getting a new OS on a new device. NOBODY here has said we expect this to be a rapid process. We know it takes time.
Hop on your faux white horse and ride back over to your fanboy forum. You've contributed absolutely nothing to this forum and I assume the same is probably true there. But seeing how as you actually have that phone you have a reason to lurk over there.
Sent from my LG-P925 using Tapatalk
Click to expand...
Click to collapse
I won't get drawn into a pissing contest regarding dev support of the Optimus 3D vs the Galaxy S II (i9100).
But, I will respond.
I'm sorry I over estimated and called that port half functional, you are right: its not a half functional port.
The build status of CM9 for the phone that half the Cyanogen team was given months ago is unknown to me. I made no claims on timelines, just forecasts based on the past and opinion.
There is indeed a very similar ICS ROM built for the i9100 (and by extension the i777) from the source that just dropped, but I cannot comment as to whether or not it was put together by a "legit cm dev."
I am not a developer, no. I am just an observer, an observer that tends to be realistic with expectations, and generally accurate.
I don't accuse the community here of being ignorant or naive. I can see that some people here do have realistic expectations.
I too was once an Aria, Captivate and Thrill fanboy. Today I am a GS II fanboy. I picked my team, as you have too. I don't think there is anyone on xda that isn't passionate about their phone.
I will not dignify further condescending comments from you with a response. This is the last time you will see me on the Thrill forums. Do not take my future lack of response as an admission of your perceived superiority. And do not take my comments to imply I believe I am better than you. I know you built a ROM, and were the first to share how to port O3D ROMs. Just because I never used your contributions I will not be so arrogant to say they don't exist.
And with that, I will be on my way. Again, best of luck to every one with a Thrill.
Sent from my Galaxy S II (i777)
Just checked out the optimus 3d thread about ICS and it seems that Ricardo is getting a lot of progress done and it seems like its getting done quickly. So hopefully it gets released before Christmas
. BTW I know that's still a long wait still but it would all be worth it.

Categories

Resources