This isn't a request about getting the Honeycomb on the G-Tab, so lighten up, Francis.
My question is more about the source code for Android 3.0 and how Google goes about releasing that to the public. I don't really understand their processes in developing a new OS and releasing it for the world to use.
Do they typically only provide it to hardware developers like Motorola, then after a period of time give it to anyone else that wants it?
When they post it, it will be available to anyone to download...
http://source.android.com/index.html
Sooo, my question was more about the processes they go through to get to that point. I know it'll be on the source code page "when it's ready"...but I'm looking for maybe an overview of what it is that they're doing from a business perspective to get it to the masses.
anyone call me francis, and I'll kill ya...
gingerberry said:
anyone call me francis, and I'll kill ya...
Click to expand...
Click to collapse
LOL. Any of you guys touch my stuff...and I'll kill ya.
gingerberry said:
anyone call me francis, and I'll kill ya...
Click to expand...
Click to collapse
How about Ginger?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just want you guys to know, when Honeycomb development starts, I'll be right behind you every step of the way.
On a more serious note, here's their explanation of their release process:
"What is involved in releasing the source code for a new Android version?
Releasing the source code for a new version of the Android platform is a significant process. First, the software gets built into a system image for a device, and put through various forms of certification, including government regulatory certification for the regions the phones will be deployed. It also goes through operator testing. This is an important phase of the process, since it helps shake out a lot of software bugs.
Once the release is approved by the regulators and operators, the manufacturer begins mass producing devices, and we turn to releasing the source code.
Simultaneous to mass production the Google team kicks off several efforts to prepare the open source release. These efforts include final API changes and documentation (to reflect any changes that were made during qualification testing, for example), preparing an SDK for the new version, and launching the platform compatibility information.
Also included is a final legal sign-off to release the code into open source. Just as open source contributors are required to sign a Contributors License Agreement attesting to their IP ownership of their contribution, Google too must verify that it is clear to make contributions.
Starting at the time mass production begins, the software release process usually takes around a month, which often roughly places source code releases around the same time that the devices reach users."
http://source.android.com/faqs.html
So it sounds like they go through the regulatory and operator process, then release it to the manufacturers while at the same time going through their own preparations. But it's a different process, which is why manufacturers can end up releasing their products before the source code is made available to the public.
Too Funny!
[email protected] pic of "Francis Sawyer" aka Phsyco!
Too Funny!!
Closing thread to avoid inevitable flaming war due to post being about Honeycomb. Good overall question though.
Related
Paul over at MoDaCo is starting to get some interest in a new application he's developing - basically it involves developers providing some XML with their installer that ties in with some similar XML on the applications' download page on their web server.
When a new version is released, the XML on the download page is updated, "AppToDate" will check the download server and you'll be able to see that a new version is available.......
AstraWare, Developer One and SK-Tools have already expressed an interest in making their software work with "AppToDate".......what are you waiting for!?!?!
I'll stop babbling, this is what Paul posted over at MoDaCo "AppToDate"
I have a dream! OK, so it's not quite as ground breaking as some other dreams of our time, but it's a dream none the less. It goes something like this...
I have a whole bunch of software on my device. Probably 15 apps at least. I also write software, which is downloaded by a fair few people, both commercial and free. I like to ensure that my software on my device is up to date with the latest versions, and it's a right pain in the ****. Not only that, I'd like my end users to have the latest versions installed to get the best possible experience... and to facilitate that I have to write a custom update checker into each of my applications. Fine for big apps, not great for quickly rustled up apps or tweaks.
But there could be another way.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What if you could have an application that lived on the device, that wasn't tied to any one application or vendor, that could check for updates for everything installed on your device? IMHO, that would be awesome. A dream. For such an approach to work, you'd need a few things...
Someone to write the update application, and to develop it. A community project perhaps?
The update application MUST be FREE for end users and developers
The update application MUST be easy for developers to plug in to
The application needs to be used by end users!
Freeware developers need to use the application!
Commercial developers need to use the application!
Now here comes the audience participation part - if you are a user, would you like to see such an application? If you are a developer - either freeware or commercial - would you like - and would you use - such an application? Make your voice heard here, and if there's an appetite for this, let's make it happen! I'll be updating this topic to list developers who would like to be involved.
Oh, I forgot to mention... I've basically written the update application! It's simple, has plenty of scope for future development, can update itself (of course) and in order to be used by a 3rd party, just needs an XML file dropped into the updater directory from your install CAB, and a current version XML on your server!
Beautiful! The response to this topic will determine how much time I spend on getting it production ready
P
Click to expand...
Click to collapse
Lend your support to this - with all the updates for various applications flying around, it's an almost impossible task to know if you're running the latest and greatest version - hopefully it will grow into a REALLY useful tool.
Thanks for listening
Mark.
Cheers for the post Mark!
I'd love to see support for all the great apps on XDA-Devs - who's interested?
P
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://www.engadget.com/2011/05/10/google-partners-with-oems-and-carriers-to-guarantee-android-upda/
We're here live at Google I/O, and the folks from Mountain View have just shared something rather sweet -- a coalition of manufacturers and carriers committed to making sure their Android devices receive the very latest updates. All four major US carriers (and Vodafone) as well as HTC, Samsung, Sony Ericsson, LG and Motorola are on board, and all will guarantee you timely upgrades to the latest version of Android for eighteen months after release, provided the hardware's capable. Now that's change we can believe in.
Click to expand...
Click to collapse
Good news?
Also Honeycomb 3.1
http://www.gsmarena.com/events_roun...okia_and_microsoft_later_in_may-news-2629.php
great news. had this program been in place a year ago there wouldn't be so many bad attitudes in the vibrant forum -_-
What does "timely" mean? And does this represent a change from what they were previously doing? My impression is that most/all of these companies would say that they already roll out updates in a "timely" fashion, regardless of what we impatient users think, and that this is just a commitment not to stop doing that.
lol we'll see. i'll believe it when it happens, but my fingers are crossed cuz that'd be awesome!
don't hold your breath.
I think an actual number should be set in place like 3 months after initial release of the newest version of android? Im not sure if thats reasonable or not but the galaxy S series didnt even start getting 2.2 updates until 2.3 was released. Thats just plain wrong haha.
Google announcement bad news for G2X
This is typical Google BS - saying one thing and getting everyone ready for that, and then turning everything upside down with a different "plan".
2.4 was supposed to be a functional update for 2.3 the optimize it for dual core performance. If you search "android 2.4" - you will still see most links stating just that.
Now, from the above announcement link, it is supposed to be the end-all OS for all devices. Don't expect to see that any time soon now. The "original" 2.4 was supposed to be coming out soon, and I was looking forward to a port or possibly even an G2X/O2X update.
I am annoyed enough with Google that I suggest that take their "Ice Cream Sandwich" and stick it both up where the sun does not shine and where it will melt!
I want a duel core OS and I want it now, as per their earlier alleged plan - it was due out in April.
Bull****. We won't be seeing 2.3 anytime soon.
XDA-DEVELOPERS AND THE GPL
Hello Everyone,
As many of you know, here at XDA we have strict policy regarding GPL v2. What you may not understand is what that means and what effects it may have on you. Simply put "The GNU GPL is a software license agreement, under which parts of the Tizen operating system are licensed. The majority of Tizen is licensed under the Apache license, but the Linux Kernel (which is present in every running Tizen ROM in some shape or form) is licensed under the GPL (version 2)".
So what does this mean for the average user?
To keep things simple, this license is one of the reasons Tizen exists in the open source capacity that it does. It requires developers to keep their kernel source open and has created the community sharing programs that have made Android so wonderful.
If you are a developer what does this mean for you?
It doesn't matter if you are creating a whole rom or just the kernel, the process of being GPL complaint is a very simple one to explain. Basically, we expect you to either link the source that you have chosen to use or upload the source you have created into a format that can be viewed by everyone and anyone. Below are the 3 most common situations that developers run into when needing to stay GPL complaint under XDA rules.
1. If you are using a stock kernel you MUST have a link leading to where the manufacture has uploaded their source.
2. If you are using a community driven source build (e.g. CyanogenMod, AOSP, or Parandroid) or a singular developer's source you MUST link directly to the repository that contains the kernel for that specific device. If you are only linking to another thread or to a general repository, this will not be considered as being GPL complaint.
3. If you are forking a repository that is similar to the examples listed above in #2, you MUST publish and link your entire kernel source. This includes any and all changes that you have made. Two of the most common ways developers publish their source on XDA is either with Gerrit, or GitHub. While these two methods are recommend, they are not the only routes you can choose to accomplish this. All that is required is that the source can be viewed and downloaded by anyone who wishes to do so. When releasing an update, your repository must be updated the moment you release your kernel on XDA. If you can post your update to XDA, there should be no reason as to why you cannot release your source.
What if the manufacture for my device has not released their kernel source?
In a perfect world this would not happen but unfortunately this is not the case. Pulser-G2 recently wrote a portal article explaining a certain situation that has come across our desks.
With all of that being said I will leave you with this...
By posting your work on XDA-Developers, you are agreeing that it complies with relevant licensing conditions. As such, by posting a kernel or other work containing GPL code, you are confirming to us that you have made this source code available publicly under the GPL. Failure to follow this policy will result in the closure of your thread and the removal of the download links.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XDA-DEVELOPERS AND THE GPL
Hello Everyone,
As many of you know, here at XDA we have strict policy regarding GPL v2. What you may not understand is what that means and what effects it may have on you. Simply put "The GNU GPL is a software license agreement, under which parts of the Tizen operating system are licensed. The majority of Tizen is licensed under the Apache license, but the Linux Kernel (which is present in every running Tizen ROM in some shape or form) is licensed under the GPL (version 2)".
So what does this mean for the average user?
To keep things simple, this license is one of the reasons Tizen exists in the open source capacity that it does. It requires developers to keep their kernel source open and has created the community sharing programs that have made Android so wonderful.
If you are a developer what does this mean for you?
It doesn't matter if you are creating a whole rom or just the kernel, the process of being GPL complaint is a very simple one to explain. Basically, we expect you to either link the source that you have chosen to use or upload the source you have created into a format that can be viewed by everyone and anyone. Below are the 3 most common situations that developers run into when needing to stay GPL complaint under XDA rules.
1. If you are using a stock kernel you MUST have a link leading to where the manufacture has uploaded their source.
2. If you are using a community driven source build (e.g. CyanogenMod, AOSP, or Parandroid) or a singular developer's source you MUST link directly to the repository that contains the kernel for that specific device. If you are only linking to another thread or to a general repository, this will not be considered as being GPL complaint.
3. If you are forking a repository that is similar to the examples listed above in #2, you MUST publish and link your entire kernel source. This includes any and all changes that you have made. Two of the most common ways developers publish their source on XDA is either with Gerrit, or GitHub. While these two methods are recommend, they are not the only routes you can choose to accomplish this. All that is required is that the source can be viewed and downloaded by anyone who wishes to do so. When releasing an update, your repository must be updated the moment you release your kernel on XDA. If you can post your update to XDA, there should be no reason as to why you cannot release your source.
What if the manufacture for my device has not released their kernel source?
In a perfect world this would not happen but unfortunately this is not the case. Pulser-G2 recently wrote a portal article explaining a certain situation that has come across our desks.
With all of that being said I will leave you with this...
By posting your work on XDA-Developers, you are agreeing that it complies with relevant licensing conditions. As such, by posting a kernel or other work containing GPL code, you are confirming to us that you have made this source code available publicly under the GPL. Failure to follow this policy will result in the closure of your thread and the removal of the download links.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://www.change.org/p/vivo-obtai...m_medium=copylink&utm_campaign=share_petition
Above is the link for a petition asking vivo to release sourcecode. They are stubborn about not releasing sourcecode, let's push them to provide us sourcecode, we don't want to use their crappy stock rom. Let's everyone sign above petition in large number!
vvvvv5 said:
https://www.change.org/p/vivo-obtai...m_medium=copylink&utm_campaign=share_petition
Above is the link for a petition asking vivo to release sourcecode. They are stubborn about not releasing sourcecode, let's push them to provide us sourcecode, we don't want to use their crappy stock rom. Let's everyone sign above petition in large number!
Click to expand...
Click to collapse
Great effort. Just now signed it.
Do keep us updated regarding any progress in this matter.
Signed. Hope vivo notices this petition.
signed!
signed
Signed!
Signed
I don't have the device but I have signed.
Holding out for a win so I can finally buy this device with that android freshness
Signed!
Signed! Fingers crossed we get it. Got my global version coming in during the next week or so
Signed!
Don't own the device but I still signed it. A phone like this deserves every bit of freshness and as a lover of bezel less phones I'd consider buying this one as long as there's an active development going on.
Also you might want to consider sharing the petition on social media such as Twitter. Don't think it'll be too difficult finding the people who already own a nex.
Sent from my Xiaomi MI MIX using XDA Labs
Signed
191...!!
Lets keep going share the link on all social media platforms . Tagg vivo everywhere as possible
Pman said:
I don't have the device but I have signed.
Holding out for a win so I can finally buy this device with that android freshness
Click to expand...
Click to collapse
This is aimed at all of vivo's source code. I've been chatting with their support on facebook (however, i dont know how official their support is) and showing them the petition progress.
[email protected]
[email protected]
I email these addresses nearly daily. I suggest everyone else add to the bombardment.
Answer from Vivo's devs ...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Signed, fingers crossed
Guys I am user of vivo y51l they didnt release our kernel sources yet signed many petitions sended many mails but they are not releasing source they are not upgrading the android versions of our device we (vivo y51 users) still stuck on lollipop. I ha e signed the petition
Signed it too.
If they refuse to release the source code, would there ever be a way for us to install a custom rom? Is it a matter of too much work or simply impossible?