Develop Bugs

Froyo source code apparently released

According to the last tweet from this guy http://twitter.com/koush

I think it's a version ported by him.

DJ_Jedi said:
I think it's a version ported by him.
Click to expand...
Click to collapse
It's not. It is the source code for froyo.

he says on aosp which is Android Open Source Project

finally we get source code
now we can start to see better froyo ROMs

OP gave me heart attack lol!
Sent from my Desire using Tapatalk

Sorry about that, but I didn't say it was for the desire

Nekromantik said:
finally we get source code
now we can start to see better froyo ROMs
Click to expand...
Click to collapse
That's what I'm hoping! Maybe the wee bugs can be ironed out too, soon!

can we see some real hacks incorporated into the new custom ROMs here like wifi N hack & 720p hack & flash player full available with the froyo source code being released to AOSP ????
i am really waiting here so impatiently to have these 3 hacks on my desire.... kindly , any devs/mods here do something & serve us the dish which we always wanted to have on our cute lil baby ( desire )....pls.....

[Q] Honeycomb port

What happened to the very buggy honeycomb port we had a month or so ago? Is there anyone working on it or did we give up after that release?

http://www.geek.com/articles/mobile/google-holds-back-honeycomb-source-code-indefinitely-20110325/
Sent from my Supersonic Evo using Xda-app.

It's only temporary until they fix their mistake, which I can give them props for. "Hey you guys can't have this yet, we messed it up and we wanna deliver the right product".
I can live with the wait.

Google has changed from open source license to apache. Now it's OK not to reveal the source of any mods. Google seems fickle.

False? Its always been that way. Open source kernel, the rest used the apache license.

kenfly said:
very buggy honeycomb
Click to expand...
Click to collapse
This is exactly why Google is TEMPORARILY withholding the HC source code. We will probably see it right around the same time that the "Ice cream" (or whatever it will officially be called) source gets released.
Because at that point devs won't need to use HC for phones, which is what Google is trying to prevent.

rstuckmaier said:
This is exactly why Google is TEMPORARILY withholding the HC source code. We will probably see it right around the same time that the "Ice cream" (or whatever it will officially be called) source gets released.
Because at that point devs won't need to use HC for phones, which is what Google is trying to prevent.
Click to expand...
Click to collapse
I don't follow in depth but I thought Google at one point said that HC was going to be tablet based only?

blizzard1017 said:
I don't follow in depth but I thought Google at one point said that HC was going to be tablet based only?
Click to expand...
Click to collapse
Google is gonna release a similar update for phones with the same look. Doesn't want people to have f*cked up ports out before they release the real deal. Makes sense to me.
Sent from my Supersonic Evo using Xda-app.

blizzard1017 said:
I don't follow in depth but I thought Google at one point said that HC was going to be tablet based only?
Click to expand...
Click to collapse
Right, that's what I was trying to say but I guess I wasn't totally clear. Google is holding HC source theoretically until IC source is ready and released. This way devs won't WANT/need to make HC builds for phones because they will be able to make IC builds.
But I'm sure some devs with try to cross pollinate "just because."

Yes I know that they are keeping the source. But I was just wondering if anyone is still working on what we have (to work with)

In short: there's no reason. It was an SDK port and will never be 100% working. Most devs just ignore the SDK ports because you can't do much with them and they will be slow. I think Androidball/thehacker (I refuse to spell that like a moron) is still working on it but he has been banned from here so it's on his own site.

[Q] Source

I have a question, while everyone says that to get cm7 we need to wait for official gb. I understand that but we got official froyo didn't we? how come we don't have cm6 if it was official froyo and i would think it came with source within 30 days?
By all means, dont take this as a rant, i was just curious.

The people working on cm6 didn't see any point in finishing the project even with source because gb and new source was supposedly around the corner. 6 months later, we still don't have gb, and imo may never, and cm6 is final. The real cyanogen team doesn't support 6 anymore afaik.
Sent from my SPH-D700 using XDA App

austin420 said:
The people working on cm6 didn't see any point in finishing the project even with source because gb and new source was supposedly around the corner. 6 months later, we still don't have gb, and imo may never, and cm6 is final. The real cyanogen team doesn't support 6 anymore afaik.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
No I asked this same question the other day and a CyanogenMod dev said it was because we never got driver sources :/ supposedly were getting them with gb but if not its gonna be hit or miss every step of the way since building aosp roms w/o source is like navigating a maze in the dark.......

theduce102 said:
No I asked this same question the other day and a CyanogenMod dev said it was because we never got driver sources :/ supposedly were getting them with gb but if not its gonna be hit or miss every step of the way since building aosp roms w/o source is like navigating a maze in the dark.......
Click to expand...
Click to collapse
i thought they had to release source within 30 days? or is the driver source not part of that?
if they didn't release the driver source with official froyo release then they probably wont for gb, then its say bye bye to official cm -.-

kwazytazz said:
i thought they had to release source within 30 days? or is the driver source not part of that?
if they didn't release the driver source with official froyo release then they probably wont for gb, then its say bye bye to official cm -.-
Click to expand...
Click to collapse
Let's clear a something up.
Official Cyanogenmod is 100% possible WITHOUT source code/drivers/etc. it just is not a practical endeavor to begin the arduous process of writing drivers and an AOSP kernel from scratch when there is a very real chance of source code being released in the near future.

kwazytazz said:
i thought they had to release source within 30 days? or is the driver source not part of that?
if they didn't release the driver source with official froyo release then they probably wont for gb, then its say bye bye to official cm -.-
Click to expand...
Click to collapse
Yeah its not impossible dude, just like 063_XBOX said..... I thought my metaphor explained it pretty well .... its possible to navigate your way out of a maze in the dark.... it'll just be a pain in the ass running into walls the whole way through..... "if we don't get any source with gb, Id think we would have nightly builds within 2-3 months assuming everyone pitched in and we had our best devs on the job..... " everything in the quotes is speculation and my personal guess so take it with a grain of salt or not at all.....
Ninja Edit: and as for source being released within 30 days of rom release, that's only for the kernel (and maybe rom?, I don't think roms have source??? I could be wrong)...... but drivers are closed source, which means they aren't required by license to give out.....

theduce102 said:
No I asked this same question the other day and a CyanogenMod dev said it was because we never got driver sources :/
Click to expand...
Click to collapse
I didn't think we ever had a sanctioned cyanogen mod dev working on the epic. Just other devs working on a port.
Sent from my SPH-D700 using XDA App

austin420 said:
I didn't think we ever had a sanctioned cyanogen mod dev working on the epic. Just other devs working on a port.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Naw we have had quite a few devs working on it but one of them just so happened to answer me....
But when I say CM dev I mean someone who actually contributed to the projects and made some progress in getting something to work in one of the builds.....

[INFO] Good News Abound - The state of DEV

I thought I'd clear some things up.
If I'm wrong please don't flame me, I'm only doing my best to subdue the general discontent in [sgh-t989]/[android development]...
Steve Kondik, also known as the creator of the godfather of all ROMS (cyanogenmod) personally owns one of our t989s (source:twitter). That, combined with the fact that this is a FLAGSHIP t-mo device probably means that our phone will be supported from the day that 9.0.0 drops.
Now, let me tell you what this means.
As you all know, for a device get non-kang CM9 our hardware must be fully supported. Camera, GPS, bluetooth, egl drivers all must work.
When a huge scale ROM like CM9 is cooked for so many devices I understand it goes something like this
[AOSP modified by Cyanogenmod(teamdouce)] +
[Android Kernel, also modified by Cyanogenmod]+
[Device tree]+
[A virgin sacrifice]=
CYANOGENMOD
Now the interesting bit, is that as soon as the device tree (Eg. Specific driver modifications for GPS, Camera, GPU) includes our device the device tree can be used to power OTHER AOSP ROMS like Miui
I know that gingerbread MIUI already makes use of the CM7 device tree, so in all likelihood they will use the CM9 device tree as well!!!
So in conclusion.
-Because CM9 has a high likelihood of dropping on our devices as soon as it comes out (most likely within the next 30 days)
-Because other AOSP-Based roms depend on the cyanogenmod device tree
-WE WILL HAVE A LOT OF FLASHING OPTIONS SOON
-Probably including CM9 AND MIUI v4 <<<<--------THAT **** CRAY
Thanks for your time, hope it helped
Don't forget the thanks button feels good when you push it.

there are a lot of other devices with cm9 alpha and we are still not an officially supported device. Still unofficially being worked on

I for one is not counting on it, frankly...
No matter how beautifully you phrase things, WE GOT NOTHING YET.
Sent from my SGH-T989 using XDA App

[A virgin sacrifice] =
SO FREK'IN EXCITED!!!!!

thanks for the info bro looking forward to it

jessejames111981 said:
there are a lot of other devices with cm9 alpha and we are still not an officially supported device. Still unofficially being worked on
Click to expand...
Click to collapse
the thing is, many of those are KANGed as in not officially supported by CM team
of the few that officially are supported is Nexus S i9020 and SGS i9000
even the "classic" SGS2 i9100 is not fully supported by CM yet, there's more bugs than... well it's not usable as a daily driver
that was just before the end of last year
they might have improved it a bit by now
even the Nexus S version of CM9 is still very buggy, that's why i have the stock official ICS4 instead on my Nexus S

Please please use words like
"death of an era." Instead of virgin sacrifice. I don't believe in that
Sent from my SGH-T989 using xda premium

iwasblown said:
Please please use words like
"death of an era." Instead of virgin sacrifice. I don't believe in that
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I don't believe in idiots, can you make them all go away?

It takes time for this stuff guys. Anyone remember how long it took to jump from donut to eclair to get a stable rom? And look how few devices there were that actually ran android. This whole "if its not done in 2 weeks then its never happening" thing is a bit unfair. Let the devs dev and those who do not can wait for them quietly.

Why this statement?
From a glaxay better than yours.

tl;dr
I am basing my entire post on the fact that Steve Kondik has our device and should theoretically be working on it.
Click to expand...
Click to collapse
Steve Kondik aka Mr. Cyanogen also works for Samsung. I am sure he gets ALL Samsung devices...

corwest said:
It takes time for this stuff guys. Anyone remember how long it took to jump from donut to eclair to get a stable rom? And look how few devices there were that actually ran android. This whole "if its not done in 2 weeks then its never happening" thing is a bit unfair. Let the devs dev and those who do not can wait for them quietly.
Click to expand...
Click to collapse
It only takes 2 weeks to modify the stock rom or cm7/9.
Its the expectation that is built when people act like quantity is all that matters. There are basically only 2 people making roms; Samsung and CM team, everyone else just waits on these 2 so that they could tweak and modify one of those 2. The funniest part is that the use of the word "kanging" is thrown around among these other people.

housecat93 said:
I thought I'd clear some things up.
If I'm wrong please don't flame me, I'm only doing my best to subdue the general discontent in [sgh-t989]/[android development]...
Steve Kondik, also known as the creator of the godfather of all ROMS (cyanogenmod) personally owns one of our t989s (source:twitter). That, combined with the fact that this is a FLAGSHIP t-mo device probably means that our phone will be supported from the day that 9.0.0 drops.
Now, let me tell you what this means.
As you all know, for a device get non-kang CM9 our hardware must be fully supported. Camera, GPS, bluetooth, egl drivers all must work.
When a huge scale ROM like CM9 is cooked for so many devices I understand it goes something like this
[AOSP modified by Cyanogenmod(teamdouce)] +
[Android Kernel, also modified by Cyanogenmod]+
[Device tree]+
[A virgin sacrifice]=
CYANOGENMOD
Now the interesting bit, is that as soon as the device tree (Eg. Specific driver modifications for GPS, Camera, GPU) includes our device the device tree can be used to power OTHER AOSP ROMS like Miui
I know that gingerbread MIUI already makes use of the CM7 device tree, so in all likelihood they will use the CM9 device tree as well!!!
So in conclusion.
-Because CM9 has a high likelihood of dropping on our devices as soon as it comes out (most likely within the next 30 days)
-Because other AOSP-Based roms depend on the cyanogenmod device tree
-WE WILL HAVE A LOT OF FLASHING OPTIONS SOON
-Probably including CM9 AND MIUI v4 <<<<--------THAT **** CRAY
Thanks for your time, hope it helped
Don't forget the thanks button feels good when you push it.
Click to expand...
Click to collapse
I'd like to believe, I really would. And I hope this does come to fruition. However, even if it doesn't, the few ROMS we do have are pretty good, and our phone still outperforms almost anything else available right now, so I'll still be happy.
I do have one request, though. Can we figure out a way to make CM based ROMS happen without a virgin sacrifice? There are so many other things in life that require those, that they are starting to become scarce

The fact that lots of other phones have alphas and repositories available to even make kangs does not fare well for our device.
Sent from my HTC_Amaze_4G using xda premium

guys chillax..slayher already has it booting..and that's news from december

good to know, thanks

Great phone, needs more dev time and hopefully that comes along with it when ics hits.
We got shafted early with the nexus release so close to the T989 and a dev that promised things but ran away.
New year brings new hope. Great respect for the devs that care about our phone.
Sent from my SGH-T989 using XDA App

Let's hope the mods don't ban what little devs we have left...
Sent from my HTC_Amaze_4G using xda premium

AznDud333 said:
guys chillax..slayher already has it booting..and that's news from december
Click to expand...
Click to collapse
I don't follow, what do you mean by booting?

synergeticink said:
I don't follow, what do you mean by booting?
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Booting

asp roms

When will we see a aosp rom for our note 3

Tomorrow when the clock strikes 12. I promise
Sent from my magic spaceship

When people stop asking for ETA's.
sent from my sm-9005.

Yerv Melkonian said:
When will we see a aosp rom for our note 3
Click to expand...
Click to collapse
When will we see people stop asking for aosp roms? Thats the real question, this phones barely a month old smh.
Sent from my note 2 ya bish!

d12unk13astard said:
When will we see people stop asking for aosp roms? Thats the real question, this phones barely a month old smh.
Sent from my note 2 ya bish!
Click to expand...
Click to collapse
We're just excited. Let us wag our tails and scratch at the door until our owner opens the door for us. So to speak. LOL!

Lol. There won't be an Aosp until the Google edition is released. Somebody has to recode removing all TW. Or Google release a base. The S4 port is in the works but taking time
Sent from my SM-N9005 using xda premium

dragonstalker said:
Lol. There won't be an Aosp until the Google edition is released. Somebody has to recode removing all TW. Or Google release a base. The S4 port is in the works but taking time
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
I would love to see that
Sent from my SM-N900T

Is there a Google edition or developer edition coming? Has that been confirmed anywhere? I too am really missing cm, aokp, pa, and especially pac man. Man, what I'd give for pac man on this beast! I REALLY hope we get some aosp love.
Sent from my SM-N900T using Tapatalk

dragonstalker said:
Lol. There won't be an Aosp until the Google edition is released. Somebody has to recode removing all TW. Or Google release a base. The S4 port is in the works but taking time
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.

CalcProgrammer1 said:
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
Click to expand...
Click to collapse
You sir have just explained the reason I fell in love with android, aosp, the rooting community. A lot of people don't get and are unappreciative of the works of ROM devs. So much greed and selfishness I've seen on xda since after the g1 days. Its always *****ing and bickering and this and that and demanding. Thank you to all the devs out there. Without you guys, android will be a Disney Land that never opened its gates
Sent from my SM-N900T using xda app-developers app

pathtologos said:
Is there a Google edition or developer edition coming? Has that been confirmed anywhere? I too am really missing cm, aokp, pa, and especially pac man. Man, what I'd give for pac man on this beast! I REALLY hope we get some aosp love.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
+24

CalcProgrammer1 said:
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
Click to expand...
Click to collapse
Why would you quote me and say exactly what i said in a long drawn out explanation. I'm guessing you missed the punctuation in my response. I mean you said everything i said, down to how the CM is a work in progress. Sheesh.

CalcProgrammer1 said:
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
Click to expand...
Click to collapse
DUDE I couldn't have said it better myself. You devs are wizards.