Database Users

Samaung testing 2.3 on our I9000!

Samfirmware twittered last night http://mobile.twitter.com/samfirmware/status/34382086026567681
Samsung test Android 2.3 for i9000 and p1000 we have no more info at the moment.
Click to expand...
Click to collapse
This is very good news!

Why make another thread for this ? It's already in the "Android 2.3 any info?" post.. It's XDA Forum here, not Twitter, we don't need zillion of posts about 2.3 status.

very good!!!!!

I think they testing on their own i9000 because mine still got 2.2 froyo wich is also not official rom because no foryo yet released for pakistan

samsung is extremely lazy in releasing updates, so relax and go to sleep !

Haven't they been 'testing' for months....
Useless!!
I was personally told they were testing 2.3 before froyo was even released for the sgs.
Come upgrade day, not sure I will stick with Samsung, I love my sgs but the updates and software coding they do to their own android versions, really does suck.
Sent from my GT-I9000 using Tapatalk

While i agree with the Samsung bashing about software quality and other updates.
Is there any real benefit to roms on other devices. I know of cyanogen name miui. But at the end of the day there ain't too much of a benefit over what we already have.
At the end of the day what Samsung may lack in software they made up for in the hardware on our devices.
Everybody here will have done their research before buying the device, it weren't hard to work out Samsung were still getting to grips with android.
Im sure in time they will mature and make very good software, but this will take time. Rome wasn't built in a day.
Sent From My GalaxyS Iphone Killer

Totally agree man, the SGS was my first android, and also my first Samsung and I have been with them ever since. I have bought a nexus S the day it came out. Samsung hardware is great but they seemed to be overwhelmed with the different models and such. And with the SGS2 coming out soon, I am not sure about 2.3 for us. However that is why XDA is so important for us.
Rome might not be built in a day, but ROMs can be
SkinBobUk said:
While i agree with the Samsung bashing about software quality and other updates.
Is there any real benefit to roms on other devices. I know of cyanogen name miui. But at the end of the day there ain't too much of a benefit over what we already have.
At the end of the day what Samsung may lack in software they made up for in the hardware on our devices.
Everybody here will have done their research before buying the device, it weren't hard to work out Samsung were still getting to grips with android.
Im sure in time they will mature and make very good software, but this will take time. Rome wasn't built in a day.
Sent From My GalaxyS Iphone Killer
Click to expand...
Click to collapse

While I appreciate the fine work done on the xda ROM's, I would much rather like the official ROM that has undergone a lot of testing and has the backing of the manufacturer. Since Samsung has not given any indication of its commitment to a phone beyond a few months, the Galaxy S would probably be the last Samsung product that I buy.

chrisjcks said:
Haven't they been 'testing' for months....
Useless!!
I was personally told they were testing 2.3 before froyo was even released for the sgs. Come upgrade day, not sure I will stick with Samsung, I love my sgs but the updates and software coding they do to their own android versions, really does suck.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
This might come as a shock, but it's one thing to ship a customised ROM with plenty of upgrade issues (etc).
It's a total other for a major company to do so. I know the guys at XDA make ROM development seem easy, but the reality is, that's because Samsung has already done most the work for them.. Lets be realistic, any ROM out there in the community which isn't a slightly modified Samsung ROM, is extremely buggy still.. Furthermore, Samsung needs to consider the various rebranded models, etc.

Auzy said:
This might come as a shock, but it's one thing to ship a customised ROM with plenty of upgrade issues (etc).
It's a total other for a major company to do so. I know the guys at XDA make ROM development seem easy, but the reality is, that's because Samsung has already done most the work for them.. Lets be realistic, any ROM out there in the community which isn't a slightly modified Samsung ROM, is extremely buggy still.. Furthermore, Samsung needs to consider the various rebranded models, etc.
Click to expand...
Click to collapse
Bro, have you tried CM7? It's fricken amazing.
A lot of folks here on XDA are (almost) as talented, or even more so, than half the clowns working at Samsung. I'm sure they learn a thing or two from around here.
Only reason the Nexus S is so good is because Google did all the development.
Yes, Samsung has eventually shipped very nice & fast 2.2.1 ROMs. But how long did it take, and how long will it take for Gingerbread?
I'm placing my faith in CM7 which will continue to improve.

chambo622 said:
Bro, have you tried CM7? It's fricken amazing.
A lot of folks here on XDA are (almost) as talented, or even more so, than half the clowns working at Samsung. I'm sure they learn a thing or two from around here.
Only reason the Nexus S is so good is because Google did all the development.
Yes, Samsung has eventually shipped very nice & fast 2.2.1 ROMs. But how long did it take, and how long will it take for Gingerbread?
I'm placing my faith in CM7 which will continue to improve.
Click to expand...
Click to collapse
I wouldn't doubt samsung used some of the kernel devs from heres code in their 2.2.1 roms (namely lastufo, hardcore and trasig)

jaganm said:
While I appreciate the fine work done on the xda ROM's, I would much rather like the official ROM that has undergone a lot of testing and has the backing of the manufacturer. Since Samsung has not given any indication of its commitment to a phone beyond a few months, the Galaxy S would probably be the last Samsung product that I buy.
Click to expand...
Click to collapse
Unfortunately that is also my point of view and I cannot spend my hard earned money to a company that cannot commit itself to it's costumers. Probably the Galaxy S will be the last phone from Samsung that I buy.
On a side note, I'm looking forward for the Nokia / Microsoft partnership. I played with a WP7 this days and I got very surprise by the build quality and software.

Arkymedes said:
Unfortunately that is also my point of view and I cannot spend my hard earned money to a company that cannot commit itself to it's costumers. Probably the Galaxy S will be the last phone from Samsung that I buy.
On a side note, I'm looking forward for the Nokia / Microsoft partnership. I played with a WP7 this days and I got very surprise by the build quality and software.
Click to expand...
Click to collapse
WP7 would be mistake buddy ....

if we can't get 2.3 from samsung, maybe ROM modders here in XDA can

chambo622 said:
Bro, have you tried CM7? It's fricken amazing.
A lot of folks here on XDA are (almost) as talented, or even more so, than half the clowns working at Samsung. I'm sure they learn a thing or two from around here.
Only reason the Nexus S is so good is because Google did all the development.
Yes, Samsung has eventually shipped very nice & fast 2.2.1 ROMs. But how long did it take, and how long will it take for Gingerbread?
I'm placing my faith in CM7 which will continue to improve.
Click to expand...
Click to collapse
I'm afraid this post is pure tripe!
CM7 is nowhere near stable yet; not even all the "advertised" features work! I'm not bashing them, because they know there's still bugs, but just think for a minute.... how vocal would you be, in a very demeaning manner, if Samsung had put out CM7 as it stands now?
As for Google "doing all the development [on Nexus S] - I think you'll find that they only did (at most) 50%. Most, if not all, the initial hardware driver support, which is the KEY to making Android work on any device, will have been done by Samsung, as it's them who has the knowledge, skills & facilities to make the phone. Once you've got the hardware drivers / abstraction layer; its very easy to put any OS you want on top! (do you really, really think there's a huge hardware difference between Samsung's Bada, Android, WP7 & even Symbian phones?)
Now, I'm not saying Samsung are the best at delivering updates, but they're better than some *cough* Motorola *cough* and their hardware is still the pinnacle of what's available. And yes, there's a few talented people on XDA, but there's also a hell of a lot more who muddy the waters and generally add to the nonsense going round by wrongly accusing Samsung / XDA devs / polar bears of X, Y, & Z.

Some of you have to take a good look into all that is "technology" and the likes...Most likely, once a device is out, YOU WILL NOT GET MAJOR UPDATES besides bug correction. And this is valid for every company.
Consider yourself lucky to get major release like 2.2 or 2.3, most of the others makers (HTC, Sony, Motorola) are still on 2.1.
Take a good look there and see by yourself:
http://en.wikipedia.org/wiki/List_of_Android_devices
Most of the devices don't even have 2.2.1 and the only one with 2.3 is still Nexus S.
WP7 had a long run before releasing the first bug correction (not even sure if it's out yet...)
Even worst, iOs users have to PAY for their release
So, you can complain all you want but reality is far from what you are thinking...
Now, as for 2.3, it's supposed to be optimised for SGS hardware (because of the Nexus S), can't wait to see how it goes!

theres a good chance we will get 2.3 because galaxy s phone are still being sold and the 4g ones

I sincerely hope samsung is gonna surprise us one of these days (even then probably later rather than sooner), since 2.3 is finally optimized for the hummingbird aswell... Also the screen shutdown animation kicks ass.
On another note: Samsung should really communicate better, and ffs train your customer support. I tried to poke for some information earlier this week, and I got a response saying: Samsung is not responsible for the updates, please contact the responsible party, in this case "Android".

Testing ! In galaxy S2 v2.3 ... S3 v2.4
Galaxy S 16Gb Int
CM7 Honeycomb

Google - No Honeycomb AOSP for you!

http://www.businessweek.com/technology/content/mar2011/tc20110324_269784.htm
Google says it will delay the distribution of its newest Android source code, dubbed Honeycomb, at least for the foreseeable future. The search giant says the software, which is tailored specifically for tablet computers that compete against Apple's iPad, is not yet ready to be altered by outside programmers and customized for other devices, such as phones.

almostinsane said:
http://www.businessweek.com/technology/content/mar2011/tc20110324_269784.htm
Google says it will delay the distribution of its newest Android source code, dubbed Honeycomb, at least for the foreseeable future. The search giant says the software, which is tailored specifically for tablet computers that compete against Apple's iPad, is not yet ready to be altered by outside programmers and customized for other devices, such as phones.
Click to expand...
Click to collapse
More beta BS. I'll sell you a car but we only completed the frame.

Yup - Its why I just sent my Xoom back to Moto.

Perhaps it's time to change your ID to "completelyInsane".
Sent from my SCH-I500 using XDA App

_RTFM_ said:
Perhaps it's time to change your ID to "completelyInsane".
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
LMAO!
Sent from my PC36100 using XDA Premium App

i dont understand what will make it "ready" if they are planning on eventually releasing it what will keep it from being ported to phones then. If its a matter of incompleteness then what's changed since Cupcake which everyone agrees was more .8 than 1.0. Releasing it to dev's will allow for bugfixes and tweaks to get merged upstream.

It will leak eventually. It always does...
Sent from my Xoom using XDA App

Yea I dont understand google some times. I understand the the OS isnt ready, but if it really is that bad and that unstable then why even put it on a tablet. And really what harm does it do the put out the code, so people will port it to other devices, you can keep doing what you will but make lots of devs happy.

They say they're worried about a poor user experience. Who do they think these users are? "I he4rd on the int3webz I can haz h0neycombz on my G1?" I mean we already know that the percentage of people running custom Roms, while large for what it is, is not the bulk of people using Android. And we know that what we're doing may not be the smoothest experience. The SDK has already been ported to pretty much everything, and they're worried about the actual 3.0 being a poor experience? Come on Google, what's this really about?

This wasn't the best source to quote from. Google said they don't want developers trying to port it to phones yet since they can't guarantee a good user experience on phones. They're afraid XDA is going to port it, people try to run it on their phones and then say how crappy it runs on a phone even though that's not what it was designed for. You know it would happen, and word would spread that it sucks on phones and yada yada it doesn't get a fair chance.
Sent via EVO

As much of a ROM guy as I am, I admit this makes sense from a business stand point. Google makes $ from licensing and distribution (with regards to Android). The hacker communities do not make up said market for the most part.
The worst thing companies combat these days is negative publicity.
I owned an iPhone, two iterations, the 3G and the original. Why did my mother never purchase one, nor my sister? Simply because of how locked down they are due to MY advice. Were they ever going to buy said device due to their hackability? Hell no. But because I said it was sh**** that Apple locks their stuff down so much, they declined to buy said hardware.
Releasing the software for Google could have a lot of negative effects on a BRAND NEW operating system for a BRAND NEW market for Google. If people are throwing this on phones, you search it out on the internet, and everything is Honeycomb this sucks, and honeycomb that sucks, due to people using it on phones, most people who try to do basic research, like my mother, or sister,
will only see "THIS SUCKS".
Just my 2c, but I can see their stand point. Until they can find a way to keep it off the phones, I see this as an issue for google.
~m

familiarstranger said:
They say they're worried about a poor user experience. Who do they think these users are? "I he4rd on the int3webz I can haz h0neycombz on my G1?" I mean we already know that the percentage of people running custom Roms, while large for what it is, is not the bulk of people using Android. And we know that what we're doing may not be the smoothest experience. The SDK has already been ported to pretty much everything, and they're worried about the actual 3.0 being a poor experience? Come on Google, what's this really about?
Click to expand...
Click to collapse
Uhmm, are we reading the same forum? Where people knowingly purchased a device that didn't have flash or lte or an ad card working at launch but are still *****ing and whining and returning their xoom regardless? What I mean is, those same people will install Honeycomb and complain that google released a lousy product.
Sent via EVO

thegeektern said:
I understand the the OS isnt ready, but if it really is that bad and that unstable then why even put it on a tablet. And really what harm does it do the put out the code, so people will port it to other devices, you can keep doing what you will but make lots of devs happy.
Click to expand...
Click to collapse
My understanding of that article is that Google doesn't feel its ready for phones. It's not that its not ready for tablets. They understand that they won't be able to stop people from using HC on phones, but trying to stave off the inevitable...
this HC thing looks like crap.... oh.. on my phone. In the end.. we are talking about a company here.. a company that needs to keep it's image.. and products.. (or software as you may call it).. as good as possible.
I don't think it's the best move Google could have made, but I think Google should do things in it's best interest to keep itself as a company in good standing. Long and short of it.. if things go south for google.. we'll all be unhappy. Just getting things out for the sake of allowing devs to play doesn't mean its the most sound decision for the company making it.
Yes, I know.. it's 'open source', but it is still a work-product. I think it's also entirely likely this is just a marketing ploy to say 'we told you so'.. and then it will get leaked and everything will go back to normal. But I still think people often forget that this is still a company that has to keep itself together to survive.
EDIT: So many things get written in the same time when you respond to a post! It seems as though I am joining the choir of.. this isn't so bad.

Sirchuk said:
This wasn't the best source to quote from. Google said they don't want developers trying to port it to phones yet since they can't guarantee a good user experience on phones. They're afraid XDA is going to port it, people try to run it on their phones and then say how crappy it runs on a phone even though that's not what it was designed for. You know it would happen, and word would spread that it sucks on phones and yada yada it doesn't get a fair chance.
Sent via EVO
Click to expand...
Click to collapse
Well that hasn't stopped devs on xda porting it already - http://forum.xda-developers.com/showthread.php?t=978939

Darn you almostinsane, I was just about to post this but you beat me to it!
Its really unfortunate that Google is doing this, whatever happened to a completely open source OS? In my honest opinion I think they should release it to the public and let the various devs have at it and see what can be improved and take those improvements into consideration for the next release of Android. If the OS was only meant for tablets who is to say that x developer can port it to a handheld flawlessly? It would be a HUGE leap ahead for us and for big ol' G.
Either way, it'll happen with or without Google releasing the source as our one dev spacemoose1 has shown us with making a near perfect port to the Samsung tab of honeycomb.
Stinks money is such an issue, Google doesn't really need anymore haha.
Done with my rant now
Sent from my ADR6300 using XDA App

Another business reason for this decision: Google may not have programmed Honeycomb well.
An obvious(?) repercussion for grimy source code going public is more bashing of Honeycomb's alleged "beta-ness". The more app developers that use the ...poisonous open-source code, the more ...poisoned apps there will be.
Or, they want to curb full-blown Honeycomb from appearing on devices other than the Xoom for just a little longer.

you're right. I just hate that its true. Your sig shows you remember the G1 days when we were all just so happy about what our phone COULD do. It's gotten a lot whinnier around here since then.
Sirchuk said:
Uhmm, are we reading the same forum? Where people knowingly purchased a device that didn't have flash or lte or an ad card working at launch but are still *****ing and whining and returning their xoom regardless? What I mean is, those same people will install Honeycomb and complain that google released a lousy product.
Sent via EVO
Click to expand...
Click to collapse

As a ROM enthusiast; yea this sucks. Business it's understandable; but as the former it doesn't make me happy.
My NC sorely needs a aosp honeycomb, HC's tablet interface is superior to even CM7 on it.
Honestly though it's a lot of speculation here on why, but it really just sounds like an excuse (Bad one) to quiet the devs while really being a straight business decision.

How is not releasing honeycomb aosp right away not being open? Would you like all your roms without SD card support right now? Honeycomb is most likely stable enough for normal use for the average consumer and Google had to make footprint in the tablet industry before ipad2 was announced. Things were obviously rushed so i rather wait for them get everything situated. I think this unfortunate news but I'm not gonna cry foul when its something that's probably for the better. Google has proven with each iteration of android they have released source so just be patient
Sent from my Xoom using Tapatalk

almostinsane said:
Yup - Its why I just sent my Xoom back to Moto.
Click to expand...
Click to collapse
I don't understand the logic here. What alternative are you seeking? Take it back for the Galaxy 10.1? It runs the same OS. Take it back for an iPad? It runs a closed OS.
The AOSP release is delayed ... maybe. Why would you return your Xoom because of this?
Sent from my Nexus One using XDA Premium App

Samsung Sent Galaxy S II’s to Cyanogenmod Dev

Well this is both shocking and awesome. It appears Samsung has sent at a complimentary Galaxy S II to at least one of the developers over on the Cyanogenmod team. Atinm, one of the developers working on porting CM7 to the original Galaxy S tweeted today this welcome news. This is a bold move on Samsung’s part and just earned them a ton of brownie points in my book.
Cyanogenmod started on the original Android phone, HTC’s G1. Since then it has expanded to many other devices, but the list of supported devices remains fairly HTC heavy. While Cyanogenmod’s future on HTC phones may have been a bit shaky until the recent decision to stop locking bootloaders, it appears Samsung is also aware of how influential the power users that love CM are. It may be a bit until we see CM7 running on a GSII, since the original Galaxy S is still a work in progress, but just the fact that it’s coming is exciting
I have to applaud Samsung’s stance towards Android hacking and development lately, especially as other OEMs danced with locked bootloaders and heavily skinned UI’s. Samsung appears to be paying much more attention to not crossing the developers and power users, who tend to be some of the most enthusiastic about Android. In my opinion this is going to pay off as customers, such as myself, who want that freedom Samsung is giving us, are often the ones less tech-savy friends and family go to for purchasing advice. Other hardware manufacturers take note! Let’s hope Samsung keeps this sort of attention to developers up.

And this is why I like Samsung so much. They have great R&D, good developers and they're the most opened among all bigger phone manufacturers. How to not love them? ;-)

Brut.all said:
And this is why I like Samsung so much. They have great R&D, good developers and they're the most opened among all bigger phone manufacturers. How to not love them? ;-)
Click to expand...
Click to collapse
Obviously you didn't bought the SGS, or you must be mad

Razer(x) said:
Obviously you didn't bought the SGS, or you must be mad
Click to expand...
Click to collapse
I have SGS2 and Samsung TV. I was playing with friend's SGS1 and it was really good, but of course he has installed custom ROM with fixes.

Obviously you didn't bought the SGS, or you must be mad
I am mad then well pleased with SGS 1 on 2.2.1 and even more pleased on rom kitchen build .
Just as well pleased with SGS2 no problems .
jje

Razer(x) said:
Obviously you didn't bought the SGS, or you must be mad
Click to expand...
Click to collapse
exactly .. samsung wants cyanogemod team to fix thier issues

Do you think that CM7 on sgsII would be able to include hardware acceleration in the browser like the stock firmware? Cos it makes browsing so buttery smooth!
Sent from my GT-I9100 using XDA Premium App

alexeiw123 said:
Do you think that CM7 on sgsII would be able to include hardware acceleration in the browser like the stock firmware? Cos it makes browsing so buttery smooth!
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
i doubt it very much. unless samsung offers some kind of source for their browser so it can be included in the ROM.

HTC Releases Source Code For Desire Z, Incredible S and Flyer

One of the development community’s ultimate resources when working on a phone is the source code. Among other things, the source code helps to make it possible to get some really exciting work done in terms of custom ROMs and kernels.
If you want to take a look through the code, you can visit the source link below. The top three entries are for the Desire Z, Flyer and Incredible S respectively.
http://www.everythingandroid.org/ht...r-desire-z-incredible-s-and-flyer/2011/07/19/
http://developer.htc.com/

This is very good too see....can't wait too see what comes from this in the dev community

On one hand, it's discouraging to see HTC take so long to release the code.
But on the other hand, this reminds us of why open source is (or should be) the future of technology. At the same time we can appreciate how much hard work the original developers put into the software, and how now the power is put into the hands of everyone with enough energy and devotion to refine the software.
Why not make the whole world part of the team, and let participation be voluntary? It's got so much potential.
Sent from my HTC Vision using XDA App

Beautiful idea man. but your preaching to the choir. send an email to moto or samsung. maybe they will take the time to tell you what they think of you.
also. Companies are not going to make money off their ideas by just giving them away to the public. Remember there is a bottom line in every company. that is MONEY! And everyone wants more. Think about how much better cyanogen could be if all the device specific devs didn't have to have real jobs and worked on cm all the time 8 hours a day. but they would have to pay their bills somehow. If they charge to download a flashable cm .zip file but also made their work public would everyone buy it or just wait until someone compiled if and released it on here? some would buy. most would wait.
open source is kind of like socialism. A small minority of the people are doing all the work and the majority are benefiting from their had work. it works on a small scale for a little while.
Now don't get me wrong. I am a full supporter of open source and believe if you have fun programming and can fix something; that is awesome and i appreciate the people who do it. But i don't think i would run cm if i had to pay for it.

ngc604 said:
Beautiful idea man. but your preaching to the choir. send an email to moto or samsung. maybe they will take the time to tell you what they think of you.
Click to expand...
Click to collapse
LOL! Maybe that's part of the reason why their UI's are so...._________?
This raises a question: if they use android as a base, why are they not also bound by open source legalities? Or are they, just resentfully?
Sent from my HTC Vision using XDA App

jontornblom said:
LOL! Maybe that's part of the reason why their UI's are so...._________?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
HAHAAH nicely put there, i know of soo many word i can put there to complete that phrase
non of the are positive tho

ngc604 said:
it works on a small scale for a little while.
Click to expand...
Click to collapse
companies like redhat disagree with you
jontornblom said:
This raises a question: if they use android as a base, why are they not also bound by open source legalities? Or are they, just resentfully?
Click to expand...
Click to collapse
they are and they do (well, some do), but you're blaming the wrong people. open sauce doesnt mean very much, it all depends on the license, the linux kernel requires all distributed modifications be avilaable (and even then, you only have to make the changes available to the people you distribue to, however they are free to pass it on), most of the rest of Android is Apache licensed which removes that requirement.

[Exynos sources are up]Let's the magic begin !

http://www.origenboard.org/wiki/index.php/Resources
Thx to http://forum.xda-developers.com/showthread.php?t=2003832

I hope this is it not some broke ass thing Samsung pointed us at to calm us down for a while
Sent from my GT-I9100 using Tapatalk 2

I hope this is what the devs needed, I tried the 4.1.2 leak and I came back to CM10 nightly hope it reaches stable.

Galaxy S2 has a Exynos 4210 processor, and apparently has published the user's guide and pre-built images: http://www.origenboard.org/wiki/index.php/Resources#Software_User.27s_Guide
Surely you can do something with it!

jrsoft said:
Galaxy S2 has a Exynos 4210 processor, and apparently has published the user's guide and pre-built images: http://www.origenboard.org/wiki/index.php/Resources#Software_User.27s_Guide
Surely you can do something with it!
Click to expand...
Click to collapse
Only a dev can tell...someone like entropy maybe
Sent from my GT-I9100 using Tapatalk 2

I doubt that they are not sources but some kind of trolling from Samsung. I wish i would be wrong.
EDIT::I AM SURE THEY ARE NOT THE REQUIRED SOURCES.
Sent from my GT-I9100 using Tapatalk 2

Nothing to see here, devs have already said this is useless for the stuff that needs fixing.

http://git.insignal.co.kr/samsung/exynos/android/platform/hardware/samsung_slsi/exynos4/
Note that the last commit date is October 25. Nothing new at all here. We saw that within a day after it went up, poked at it, and:
It has some additional HDMI stuff
It has some additional Low Power Audio (LPA) stuff
Other than that, it's almost identical in source code (and is identical in behavior) to the outdated broken **** that got Samsung in trouble in the first place. HWComposer is totally broken (indistinguishable in operation from no HWC at all), and without working HWC, the HDMI stuff is useless. (It's all tied together.)

Entropy512 said:
http://git.insignal.co.kr/samsung/exynos/android/platform/hardware/samsung_slsi/exynos4/
Note that the last commit date is October 25. Nothing new at all here. We saw that within a day after it went up, poked at it, and:
It has some additional HDMI stuff
It has some additional Low Power Audio (LPA) stuff
Other than that, it's almost identical in source code (and is identical in behavior) to the outdated broken **** that got Samsung in trouble in the first place. HWComposer is totally broken (indistinguishable in operation from no HWC at all), and without working HWC, the HDMI stuff is useless. (It's all tied together.)
Click to expand...
Click to collapse
i had a feeling our hopes will be crushed any ways how you feeling? got well from your cold ?

Read the schedule people. If its the same old **** on 14 december then they wont provide what they promised.
Close this one please.

Entropy512 said:
http://git.insignal.co.kr/samsung/exynos/android/platform/hardware/samsung_slsi/exynos4/
Note that the last commit date is October 25. Nothing new at all here. We saw that within a day after it went up, poked at it, and:
It has some additional HDMI stuff
It has some additional Low Power Audio (LPA) stuff
Other than that, it's almost identical in source code (and is identical in behavior) to the outdated broken **** that got Samsung in trouble in the first place. HWComposer is totally broken (indistinguishable in operation from no HWC at all), and without working HWC, the HDMI stuff is useless. (It's all tied together.)
Click to expand...
Click to collapse
What is to prevent us from thinking that Samsung wants to fix bugs first before CM / AOSP devs fix them.
I mean pride is at stake here. Especially if the coders are Korean.

Noob question, but what are the reasons that a manufacturer would want to withhold sources?
The only things I can think of are that it might need more qualification and review before the public are allowed to root through it to ensure there's no embarrassing mistakes / inefficiencies in there which would affect their reputation.

seanp25 said:
Noob question, but what are the reasons that a manufacturer would want to withhold sources?
The only things I can think of are that it might need more qualification and review before the public are allowed to root through it to ensure there's no embarrassing mistakes / inefficiencies in there which would affect their reputation.
Click to expand...
Click to collapse
Because manufacturers are MEANIES!!!
Real and possible reasons:
1. Proprietary driver code from third parties which post licensing issues
2. Generally poorly documented source that is shameful to release
3. Because the only people who care about source are geeks which are a very low proportion of their userbase, the rest don't even know source exists for their phone
4. Because their Exynos line isn't fairly widespread like other solutions (Snapdragon/OMAP) except in their own phones, so programming specialists are limited mostly to what Samsung provides (And the less prominent groups that muddle through the broken mess like the CM team)
5. Insert your own reason here
6. Insert Entropy's reasons here
7. loop;

karendar said:
2. Generally poorly documented source that is shameful to release
Click to expand...
Click to collapse
I can't help but feel as though this is the biggest reason. Back when 4210 was being actively developed and mainstream, Samsung had zero intention on making the source available for public scrutiny. They probably didn't bother documenting anything that didn't need it. Now that the pressure is on for them to be more transparent with their source, there is probably little motivation for them to dedicate the manpower needed to go back to what is essentially legacy code and clean it up so that it can be made public.
As more and more people get rid of their SIIs and Notes in favour of the next-gen Sammys, the pressure on Samsung to release 4210 sources becomes less and less. They're almost certainly just hoping that the problem will eventually go away. And unfortunately, it will.

Is this some kind of ad bing run by Samsung. if it is then just *****

Gillion said:
Especially if the coders are Korean.
Click to expand...
Click to collapse
Woah that was kind of racist.
Sent from my SHW-M250K using xda app-developers app

karendar said:
Because manufacturers are MEANIES!!!
Real and possible reasons:
1. Proprietary driver code from third parties which post licensing issues
2. Generally poorly documented source that is shameful to release
3. Because the only people who care about source are geeks which are a very low proportion of their userbase, the rest don't even know source exists for their phone
4. Because their Exynos line isn't fairly widespread like other solutions (Snapdragon/OMAP) except in their own phones, so programming specialists are limited mostly to what Samsung provides (And the less prominent groups that muddle through the broken mess like the CM team)
5. Insert your own reason here
6. Insert Entropy's reasons here
7. loop;
Click to expand...
Click to collapse
Absolutely spot on.
Sent from my GT-I9100 using xda premium

Totally agree with mckeowngoo.
We live in very wired world :cyclops:

Kitschki said:
Woah that was kind of racist.
Sent from my SHW-M250K using xda app-developers app
Click to expand...
Click to collapse
Ummm -_- ..........Sigh....... never mind.