Database Develop

Ice cream sandwich to release next week?

Ice cream sandwich to release next week?
http://news.cnet.com/8301-1023_3-20...xt-week/?part=rss&subj=news&tag=2547-1_3-0-20
CNET said:
Google is expected to serve up Ice Cream Sandwich--the newest version of Android--on Tuesday at the Samsung Unpacked event in San Diego.
That revelation comes courtesy of the official Android Developers YouTube channel, which earlier today posted a placeholder video titled "Android ICS launch." The site now says, "This live event is no longer available. Sorry about that." Google Executive Chairman Eric Schmidt said last month that the next flavor of the company's mobile operating system would debut sometime in October or November.
Samsung is also expected to use the event to unveil a new Android phone, perhaps the Nexus Prime, which would likely be the first Ice Cream Sandwich phone. Samsung has posted a teaser video that includes the words "Something big is coming"--perhaps an indication of the phone's screen size.
Ice Cream Sandwich is Google's first attempt to create one single unified mobile OS, taking Honeycomb features and interfaces and adapting them to run across both smartphones and tablets. ICS developers will get new open-source APIs and a framework that will help them optimize their apps to run on a variety of different Android phones and tablets.
Click to expand...
Click to collapse
Hoping to see this on my nook soon
Sent from my NookColor using xda premium

Hopefully we get a full source release soon after.
---------------------------------
Sent from my LG Optimus V using Tapatalk
If this post helped you don't forget to say thanks!

Doesn't Google usually release to one manufacturer first and then to everyone else some 6 months later? I recall that has been a concern of phone manufacturers since Google announced they wanted to buy Motorola, ie; Motorola might then exclusively get the 6 month jump. Usually Google would rotate manufacturers.

The question now is, which will come first: CM7.1 stable, or CM8?

CM8 FTW!!!!!!!!

CANCELLED!
Just saw the announcement from Samsung

I don't think we will see any ICS code anytime soon.
Personally, I think, first, they introduced the ICS (which just got delayed) then waiting for certain period of time (who know how many months) before release the source codes.
I think it's good to call CM8.

votinh said:
I don't think we will see any ICS code anytime soon.
Personally, I think, first, they introduced the ICS (which just got delayed) then waiting for certain period of time (who know how many months) before release the source codes.
I think it's good to call CM8.
Click to expand...
Click to collapse
No, I'm strongly disagreeing with this statement, with the exception of Honeycomb, Google pushes its source code to the repo's within hours or at the most a couple of days after it launches. With all the leaks lately, I wouldn't be surprised to see ICS leaked pretty soon. If it doesnt though, I'm sure we'll have source within 2-3 weeks tops.

RileyGrant said:
No, I'm strongly disagreeing with this statement, with the exception of Honeycomb, Google pushes its source code to the repo's within hours or at the most a couple of days after it launches. With all the leaks lately, I wouldn't be surprised to see ICS leaked pretty soon. If it doesnt though, I'm sure we'll have source within 2-3 weeks tops.
Click to expand...
Click to collapse
See my post above. Google usually gives one manufacturer a jump on the rest and rotates. "hours" is not really much of a jump unless they are going to change their release habits.

patruns said:
See my post above. Google usually gives one manufacturer a jump on the rest and rotates. "hours" is not really much of a jump unless they are going to change their release habits.
Click to expand...
Click to collapse
Yeah, I read that post, but that's not the case. They don't do that with the software, just the phones. For instance, the Nexus S came out on T-Mobile, then eventually Sprint, etc. When the new software is released/launched however, they push it directly to their "AOSP" (Android Open Source Project) repositories, and from there, developers have open access to the source code. Technically, since Android is licensed under the Apache Open Source license, if they are to call it "Open Source" they must post the source code within a certain time limit (which is only a couple of weeks) or else it violates the license.

Well I'm pretty excited to see some ICS efforts. New OSs are fun. I'm particularly interested in trying out the newest stock web browser.

RileyGrant said:
Yeah, I read that post, but that's not the case. They don't do that with the software, just the phones. For instance, the Nexus S came out on T-Mobile, then eventually Sprint, etc. When the new software is released/launched however, they push it directly to their "AOSP" (Android Open Source Project) repositories, and from there, developers have open access to the source code. Technically, since Android is licensed under the Apache Open Source license, if they are to call it "Open Source" they must post the source code within a certain time limit (which is only a couple of weeks) or else it violates the license.
Click to expand...
Click to collapse
You know they promised then delayed then ignored then decided not to release the Honeycomb source code, right?
There is no such a "must" from them.
But anyway, if you're correct, which I and the rest of us also wish, then it's great. I want to see them release ICS code ASAP, 3 weeks like you said is reasonable and if 3 days or even 3 hours then it's more than expect.
We all hope for the CM8, should we?

votinh said:
You know they promised then delayed then ignored then decided not to release the Honeycomb source code, right?
There is no such a "must" from them.
But anyway, if you're correct, which I and the rest of us also wish, then it's great. I want to see them release ICS code ASAP, 3 weeks like you said is reasonable and if 3 days or even 3 hours then it's more than expect.
We all hope for the CM8, should we?
Click to expand...
Click to collapse
They released what was required by the license for honeycomb but Google has confirmed that ICS will be an open source release.
---------------------------------
Sent from my LG Optimus V using Tapatalk
If this post helped you don't forget to say thanks!

votinh said:
You know they promised then delayed then ignored then decided not to release the Honeycomb source code, right?
There is no such a "must" from them.
But anyway, if you're correct, which I and the rest of us also wish, then it's great. I want to see them release ICS code ASAP, 3 weeks like you said is reasonable and if 3 days or even 3 hours then it's more than expect.
We all hope for the CM8, should we?
Click to expand...
Click to collapse
Reason I heard is that Honeycomb was a quick throw together for a tablet OS.
Not really an excuse, but considering they've been working on ICS for quite a while now, I think it'll be in the repos pretty quickly.

RileyGrant said:
Yeah, I read that post, but that's not the case. They don't do that with the software, just the phones. For instance, the Nexus S came out on T-Mobile, then eventually Sprint, etc. When the new software is released/launched however, they push it directly to their "AOSP" (Android Open Source Project) repositories, and from there, developers have open access to the source code. Technically, since Android is licensed under the Apache Open Source license, if they are to call it "Open Source" they must post the source code within a certain time limit (which is only a couple of weeks) or else it violates the license.
Click to expand...
Click to collapse
I will agree to disagree But I do hope I am wrong!

Alright, let's hope that they do what they should have been doing.

Dalingrin said the HP Touchpad will get ICS and maybe the Nook Color.

patruns said:
I will agree to disagree But I do hope I am wrong!
Click to expand...
Click to collapse
Ya thats fine, a previous comment mentioned that they didnt have to release code such as what they did for honeycomb, however, they did release the required source for honeycomb but did not push the framework and what not because it was being saved for what we now know is ICS.

RileyGrant said:
Ya thats fine, a previous comment mentioned that they didnt have to release code such as what they did for honeycomb, however, they did release the required source for honeycomb but did not push the framework and what not because it was being saved for what we now know is ICS.
Click to expand...
Click to collapse
I think one of the main reasons for Google not releasing the source code was because they didn't want people to run it on phones, being a tablet OS.

Dalingrin said the HP Touchpad will get ICS and maybe the Nook Color.
Click to expand...
Click to collapse
When did he say that? That makes it sound that the touchpad will definitely get ICS and the nook color may get it.

[Q] Anyone working on porting ICS to N1?

Its sad that the Nexus one wont be getting any official updates but I still have my hopes high about 3rd party roms. I just wanted to ask if anyone is determined to port it to the good ol Nexus?

You can check the development forums, there is already work being done. As far as a full port that probably wont be done till the source is released to AOSP. That should not happenen until after the Galaxy Nexus is officially released.
After the source is released I'm sure there will be ROM's developed for N1. It is still a good phone that plenty of people including deb's use. I would guess about 2 weeks or so after the source code gets released there will be ICS ROM's ready to be flashed.

[KERNEL] Generic Android 3.0 kernel source

I have found sources on the Google git which look like the generic (non device-specific) Android 3.0 kernel sources and have uploaded them to my git https://github.com/Ezekeel/android-3.0. I guess it might be possible to merge these into current Nexus S kernels (and also kernels for other devices) to get a kernel compatible with ICS. I will try that later on; until then I guess other kernel devs probably also find these interesting and useful.

Ezekeel said:
I have found sources on the Google git which look like the generic (non device-specific) Android 3.0 kernel sources and have uploaded them to my git https://github.com/Ezekeel/android-3.0. I guess it might be possible to merge these into current Nexus S kernels (and also kernels for other devices) to get a kernel compatible with ICS. I will try that later on; until then I guess other kernel devs probably also find these interesting and useful.
Click to expand...
Click to collapse
Yes, thanks Ezekeel, I've been browsing through the tree since minutes ago when you opened it and one thing I noticed at least is that it lacks drivers/video/samsung for Nexus S, dunno more of what is missing from our device specific tree, but it might be possible to make this 3.0 working ye.

Lol Ezekeel, I've seen you praying Jean-Baptiste Queru for the Crespo-tree sources! I Think we have to wait one or two weeks...

franciscofranco said:
Yes, thanks Ezekeel, I've been browsing through the tree since minutes ago when you opened it and one thing I noticed at least is that it lacks drivers/video/samsung for Nexus S, dunno more of what is missing from our device specific tree, but it might be possible to make this 3.0 working ye.
Click to expand...
Click to collapse
Pretty much all the device-specific stuff is missing, but maybe we are lucky and no changes have to be made in the device-specific source for the Nexus S and we can simply keep these parts from our current code.

franciscofranco said:
Yes, thanks Ezekeel, I've been browsing through the tree since minutes ago when you opened it and one thing I noticed at least is that it lacks drivers/video/samsung for Nexus S, dunno more of what is missing from our device specific tree, but it might be possible to make this 3.0 working ye.
Click to expand...
Click to collapse
I'm pretty sure this is known, but in case it's being overlooked. The gpu in the galaxy nexus is the same as in the nexus s, just supposedly higher clocked. so if drivers are available for the galaxy nexus gpu, can't they be made to work with nexus s somehow? or does it make a huge difference cause they are on different SoC's?

Luxferro said:
I'm pretty sure this is known, but in case it's being overlooked. The gpu in the galaxy nexus is the same as in the nexus s, just supposedly higher clocked. so if drivers are available for the galaxy nexus gpu, can't they be made to work with nexus s somehow? or does it make a huge difference cause they are on different SoC's?
Click to expand...
Click to collapse
JBQ said that even if gpu is the same (omap4430) in galaxy nexus and in pandaboard he wasn't able to run the gnexus driver on the pandaboard and vice-versa because of some library-dependencies. So I think the drivers will not work out of the box...

awesome!
so your efforts semi paid off. lets hope the device specific stuff gets released shortly.

Nice to know

simms22 said:
awesome!
so your efforts semi paid off. lets hope the device specific stuff gets released shortly.
Click to expand...
Click to collapse
I expect the date we get proprietary files and the date of the ICS OTA to somehow magically be the same.....
Sent from my Nexus S using XDA App

matt2053 said:
I expect the date we get proprietary files and the date of the ICS OTA to somehow magically be the same.....
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You might be right. It might also coincide quite nicely with the Galaxy Nexus release date. I got a funny feeling that it will not be officially available on the Nexus S before it launches on the Galaxy Nexus.

Maximilian Mary said:
You might be right. It might also coincide quite nicely with the Galaxy Nexus release date. I got a funny feeling that it will not be officially available on the Nexus S before it launches on the Galaxy Nexus.
Click to expand...
Click to collapse
In one of the google groups replies JBQ said that they will always focus on the flagship phone.
Up until recently that was Nexus S.
Now the torch was passed and it's Galaxy Nexus first.
They will not dull the luster of their flagship phone by making libs and drivers for released phones available before the flagship phone has had time to shine.

I merged these sources into the android-samsung-2.6.35 source and got 450 merge conflicts that I would have to resolve manually. That would a giant pain in the ass and probably not worth to effort.

Ezekeel said:
I merged these sources into the android-samsung-2.6.35 source and got 450 merge conflicts that I would have to resolve manually. That would a giant pain in the ass and probably not worth to effort.
Click to expand...
Click to collapse
That will be a huge effort to fix, and it would probably cause more harm than good if you managed to fix the conflicts. I'm sure we'll have our sources in one/two weeks tops, so that's not worth the hassle in my opinion.

Ezekeel said:
I merged these sources into the android-samsung-2.6.35 source and got 450 merge conflicts that I would have to resolve manually. That would a giant pain in the ass and probably not worth to effort.
Click to expand...
Click to collapse
Thanks for all the effort on that, and for "reminding" Google to release that source.
I'm going to guess that this wouldn't work out, but would it be possible to try to crowd source this at all? Is it the type of thing that would require a lot of knowledge about the kernel, or would a competent programmer be able to walk his way through the conflicts and resolve them?

dvgrhl said:
Thanks for all the effort on that, and for "reminding" Google to release that source.
I'm going to guess that this wouldn't work out, but would it be possible to try to crowd source this at all? Is it the type of thing that would require a lot of knowledge about the kernel, or would a competent programmer be able to walk his way through the conflicts and resolve them?
Click to expand...
Click to collapse
I guess one could make a community effort to get this done. However it still is not guaranteed that the sources, even if properly merged without errors, will compile, because some device specific updates may be missing. Or some of the proprietary files included also need an update. It just seems like a lot of work for something that potentially never will work - especially since a properly working kernel with everything in place will be released in a few weeks tops.

Ezekeel said:
I guess one could make a community effort to get this done. However it still is not guaranteed that the sources, even if properly merged without errors, will compile, because some device specific updates may be missing. Or some of the proprietary files included also need an update. It just seems like a lot of work for something that potentially never will work - especially since a properly working kernel with everything in place will be released in a few weeks tops.
Click to expand...
Click to collapse
First thanks for opening this thread, is a good idea.
At this moment I will wait some days to see if the crespo kernel 3.0 goes into public git, otherwise I will join the project to move the kenel since it will have multiple benefits.
Kalim

Samsung - CM - Exynos... whats all the fuss about?

Hello
I'm reading a lot of comment about people never buying a SAMSUNG phone again on this forum.
I believe it has something to do with CM team ( who are these guys? ) and the CPU type and source code.
Could you please care to elaborate? As I am planning on upgrading to GN2 but ofc I need root access and the latest OS all the time
Thank you.

Which post are you refering to? I just seem to see post saying how awesome the Note 2eand SIII are!

Dmwitz said:
Which post are you refering to? I just seem to see post saying how awesome the Note 2eand SIII are!
Click to expand...
Click to collapse
It's not just 1 post,
All around the forum , especially in the GN forum ( where I spend most of my time ) I see people complaining about Samsung devices in the future and how they will never buy another samsung again ...

I guess it all depends whether or not you want to run CM custom roms on your device.
Furthermore Samsung promised to release the Exynos sources...So we'll just wait and see

Problem ist that the source code is no available and without no new CM AOSP AOKP Roms possible. The company said in the past that they will release the code, but till today they don't.
Other companies like Sony did it better and supports the community. That's also a reason why great Dev won't work for our Note...

It's not impossible to bring new roms without sourcecode - we still have CM10 and will get CM10.1 - but the experience is not the best, and devs have to put A LOT of work to even make it work.
Samsung promised they will release their sources - yet untill today - they didn't. So it's simple as that, if they release sources - devs might finally fix some bugs and push CM10 into stable. Without sources we might never go out of nigthlies because some bugs might never get fixed.
As for SONY, yes they release all their sources, but remember that they used to be like Samsung untill their market share shrinked, so now they're most likely just trying to appeal to customers with that. Hope they won't change their mind about it when/if their sales go high again ( I'm looking at you Xperia Yuga )

User_99 said:
Problem ist that the source code is no available and without no new CM AOSP AOKP Roms possible. The company said in the past that they will release the code, but till today they don't.
Other companies like Sony did it better and supports the community. That's also a reason why great Dev won't work for our Note...
Click to expand...
Click to collapse
Very true, but I think they don't give a ....about a few devs and users being frustrated when they sell millions of devices...Like most of the big selling companys

bebseh said:
It's not just 1 post,
All around the forum , especially in the GN forum ( where I spend most of my time ) I see people complaining about Samsung devices in the future and how they will never buy another samsung again ...
Click to expand...
Click to collapse
I think u r talking abt this thread..especially this one..

a pall of gloom has descended on the community it seems
check out CM 10 thread
i hope its a temporary phase -
http://forum.xda-developers.com/showpost.php?p=35210934&postcount=1651

Samsung didnt want the devs to work for the android community because in the end it gives an advantage to google and its os. Samsung wants people to buy its phones because of their new features added in their TW that are not available on true android. They in the future wants their devices ti be free from the android pool. Because of the tiring update process. No source code release is just what keeps dev from moding their devices so they can market their new phones and limit those features in the old models. I dont think they will care about dev going to other vendors. Because once they got hold of a new indigenous OS. they will market its dev kits and hardware for developers and they know how to bring them back.
Sent from my GT-N7000 using xda app-developers app

[Q] Droid3 and TI OMAP4 GPU Drivers for Android 4.4 KitKat?

Hi!
Someone know if this Drivers give us some possibility to adapt a ROM with Android KitKat 4.4 for our Droid3 phones?
I have a Milestone 3 (XT860), and I think they have the same micro.
I´m sorry for mi english, I write you from Buenos Aires, Argentina.
Link
http://www.xda-developers.com/andro...possibly-aid-galaxy-nexus-kitkat-development/
Thank you very much!!!

I'm hoping, but we just don't have a dev strong enough to build some ROMs for us. I've been following and dhacker29 has been hard at work on this which really surprises me. It's actually coming together quite well. I will be curious to see how it progresses.

MrObvious said:
I'm hoping, but we just don't have a dev strong enough to build some ROMs for us. I've been following and dhacker29 has been hard at work on this which really surprises me. It's actually coming together quite well. I will be curious to see how it progresses.
Click to expand...
Click to collapse
I'm just a newbie when it comes to developing for android and such, but knowing the specs of the D3 and what KitKat is supposed to run on, there honestly should be no real excuse. I understand it's a two year phone, but I wish Motorola would stop and think about old high end phones that people end up buying for cheap a year or two after release.

I think that's the point of the G. The problem isn't that Motorola or Google couldn't make a Kit Kat rom as much as TI got out of the mobile chipset business but didn't give out the source for everything. If we had the source getting a developer to help would be much much easier. I am like you in that I am not a developer but just good at fixing things and have a job helping others fix computers on the high end.
We could sure try but the other problem is that 4.4 made drivers basically need to be recompiled for a newer kernel and we can't just reuse the drivers from older builds.
Sent from my XT862 using xda app-developers app

I stand corrected:
https://twitter.com/Hashcode0f/status/412085997740888064
Hashcode
‏@Hashcode0f
 @Xbacko The current Moto OMAP CM11 build needs some minor fixes and then it will be compatible for Droid 3. Still no camera tho.
Reply Retweet Favorite More
9:05 PM - 14 Dec 13

Waiting anxiously for kitkat on solana! (and maybe full camera working?)