Google dropped 2.0 in AOSP!!! - G1 Android Development

It seems that as of now the new sdk is available for download and so on, that is a great news I can hardly wait to put my hands on a blazing fast 2.0 ROM!!!!!!!!!!! (as soon as someone releases one )
http://developer.android.com/index.html

Everybody that follows Cyanogen on Twitter already knows this man and there's no need for another thread (yea someone already beat you to it)

woo hoo! luckily the dream will be able to handle it

There's already a thread on this. Thanks.

Well, Cyanogen, I hate to break it to you.. but you've got a long night ahead of you. And a long weekend.

matt_stang said:
Well, Cyanogen, I hate to break it to you.. but you've got a long night ahead of you. And a long weekend.
Click to expand...
Click to collapse
Looking forward to what Cyanogen has coming out.. loyal fan of his ROMS.

dilfatx said:
Looking forward to what Cyanogen has coming out.. loyal fan of his ROMS.
Click to expand...
Click to collapse
I wouldn't expect anything this weekend.

chaosan said:
woo hoo! luckily the dream will be able to handle it
Click to expand...
Click to collapse
hopefully the dream will be able to run it, it all depends whether or not htc decides to give use the proprietary drivers to have 2.0 working on our phones.
RT @cyrowski
"Eclair won't build for ADP1 or ADP2 out of the box. Will need to wait on vendors for proprietary drivers."
RT @cyanogen
"cyanogen
Probably will start by backporting features- we need new proprietary drivers for our Dream/Magic devices."
====
jbqueru :
@maxisma Unfortunately, the drop doesn't compile for the ADPs
maxisma :
@jbqueru Whats the problem? Just the drivers in the kernel? Hope not more..
jbqueru :
@maxisma Actually, user-space libraries that talk to the various components (especially media-related stuff).
maxisma :
@jbqueru damn Hope @htc will provide support for our already "outdated" devices.. Thanks for your answer
EDIT:
cyanogen
Just booted Eclair on my G1

Pinesal said:
I wouldn't expect anything this weekend.
Click to expand...
Click to collapse
can't rush art....
just be a good boy and wait for the magic to happen

yoshitoshi said:
can't rush art....
just be a good boy and wait for the magic to happen
Click to expand...
Click to collapse
Already been released.
Sorry had to. Someone toss me in the PUN-tentary.

Honestly,
I have a feeling we won't ever see drivers for 2.0 for the Dream/Magic. I'm with the camp that feels they're being EOL'd only a year in. If HTC doesn't release a 2.0 for dream/magic, then we'll never have fully operational devices past 1.6.
This is pretty much the only thing I *do not* like about Android, is that Google treats backward compatibility the same way Linux does: by not considering it at all. Of course, I can hope I'm wrong, because I'm *not* switching to Verizon, and I don't see anything decent coming down the pipe at T-Mobile.

lotherius said:
I have a feeling we won't ever see drivers for 2.0 for the Dream/Magic. I'm with the camp that feels they're being EOL'd only a year in. If HTC doesn't release a 2.0 for dream/magic, then we'll never have fully operational devices past 1.6.
This is pretty much the only thing I *do not* like about Android, is that Google treats backward compatibility the same way Linux does: by not considering it at all. Of course, I can hope I'm wrong, because I'm *not* switching to Verizon, and I don't see anything decent coming down the pipe at T-Mobile.
Click to expand...
Click to collapse
How did cyanogen just boot donut on his g1?

Frito37 said:
How did cyanogen just boot donut on his g1?
Click to expand...
Click to collapse
He backported features one by one until an official release of Donut was made. Also, booting is different than fully functional. Fwiw, someone out there actually booted up Android on a Treo 650 recently. Doesn't mean any of the drivers worked properly! Same here - booting is only the first step.

lotherius said:
I have a feeling we won't ever see drivers for 2.0 for the Dream/Magic. I'm with the camp that feels they're being EOL'd only a year in. If HTC doesn't release a 2.0 for dream/magic, then we'll never have fully operational devices past 1.6.
This is pretty much the only thing I *do not* like about Android, is that Google treats backward compatibility the same way Linux does: by not considering it at all. Of course, I can hope I'm wrong, because I'm *not* switching to Verizon, and I don't see anything decent coming down the pipe at T-Mobile.
Click to expand...
Click to collapse
That Sony Xperia has the 1700 Mhz band. And it looks sexy as all get out.

Eclair, eclair, eclair, eclair.
Tasting some eclairs now.

coolbho3000 said:
Eclair, eclair, eclair, eclair.
Tasting some eclairs now.
Click to expand...
Click to collapse
Are you really testing it?

dilfatx said:
Looking forward to what Cyanogen has coming out.. loyal fan of his ROMS.
Click to expand...
Click to collapse
Same here since day 1...!!!!!

lotherius said:
I have a feeling we won't ever see drivers for 2.0 for the Dream/Magic. I'm with the camp that feels they're being EOL'd only a year in. If HTC doesn't release a 2.0 for dream/magic, then we'll never have fully operational devices past 1.6.
This is pretty much the only thing I *do not* like about Android, is that Google treats backward compatibility the same way Linux does: by not considering it at all. Of course, I can hope I'm wrong, because I'm *not* switching to Verizon, and I don't see anything decent coming down the pipe at T-Mobile.
Click to expand...
Click to collapse
I don't think you understand Linux then. Linux is about as backward compatible as an OS gets. Can you put Windows on a i386 and expect it to work. No. Linux still boots just fine on a i386 and still runs very decent (Actually, it even runs on a i286). Linux also supports most architectures out there, unlike Windows and Mac. Only OS that supports more I believe is NetBSD.
Open-Android-Alliance wants to replace all proprietary with open source pieces. I don't know if that includes drivers or not. We will see. Actually, I see HTC releasing drivers for 2.0. Just not much after that. I just hope the Linux community can reverse engineer the drivers to create open source version so our phones can keep being updated.
There is no other phone on the market that I would want more right now than the G1. I use *nix for pretty much all my computing needs and having a five row keyboard with all the keys I need in *nix is very important to me.

We will get it working, don't worry

cyanogen said:
We will get it working, don't worry
Click to expand...
Click to collapse
I just might have to buy you a CASE OF BEER!!!!

Related

Google Maps Navigation for CDMA Hero???

Has anybody gotten this to work on CDMA Hero's???
http://www.gadgetvenue.com/google-maps-navigation-works-usa-11233152/
1.6 only....we are on 1.5. Not going to happen.
As noted, requires 1.6+.
We will be getting 2.0 eventually, probably a few months from now. Keep your fingers crossed.
Why are we waiting?
This is not how open source is supposed to work. We're not birds in a nest waiting for a worm. We don't wait for them, they have to keep up with us.
IMHO we should put aside the idea of holding out for Sprint, months or even weeks for 2.0 is WAY too long in 2009. The code is up (all of it now?), the SDK is up. Let's build it!
This, to me, is one of the most disturbing trends in Android, each manufacturer providing tweaks or proprietary GUI's that put them in control of the development cycle. In my humble opinion we need to get past that as soon as humanly possible. If that means ditching Rosie and Blur, so be it.
Today we wait for Google Nav, tomorrow we'll wait for security updates bugs, optimizations, and most importantly cool developer tweaks. Hell, we waited 6 weeks for the piddly MR update that fixed problems that should have been solved before the phone left the store.
Can someone with more intimate knowledge of Android (I'm studying it now myself so I can help) say something about how to get to a clean, universal Android ROM? I'm happy to help however I can.
5tr4t4 said:
This is not how open source is supposed to work. We're not birds in a nest waiting for a worm. We don't wait for them, they have to keep up with us.
IMHO we should put aside the idea of holding out for Sprint, months or even weeks for 2.0 is WAY too long in 2009. The code is up (all of it now?), the SDK is up. Let's build it!
This, to me, is one of the most disturbing trends in Android, each manufacturer providing tweaks or proprietary GUI's that put them in control of the development cycle. In my humble opinion we need to get past that as soon as humanly possible. If that means ditching Rosie and Blur, so be it.
Today we wait for Google Nav, tomorrow we'll wait for security updates bugs, optimizations, and most importantly cool developer tweaks. Hell, we waited 6 weeks for the piddly MR update that fixed problems that should have been solved before the phone left the store.
Can someone with more intimate knowledge of Android (I'm studying it now myself so I can help) say something about how to get to a clean, universal Android ROM? I'm happy to help however I can.
Click to expand...
Click to collapse
I can't agree with you more. When I transfered to the android platform I was under the assumption that what u said supposed to happen was the case.
However I hear it's very difficult to build a 2.0 for hero.
You see the "drivers" that are in the hero right now will not work on 2.0. If you build the provided open source 2.0 rom, you will get an OS with no tie to the hardware. a map with gps a phone with no radio and a browser with no wifi. which will be useless to any one.
sm_x said:
You see the "drivers" that are in the hero right now will not work on 2.0. If you build the provided open source 2.0 rom, you will get an OS with no tie to the hardware. a map with gps a phone with no radio and a browser with no wifi. which will be useless to any one.
Click to expand...
Click to collapse
Uha, I know. The Linux guys warned us years ago about allowing proprietary drivers in Linux (see the old NVIDIA debate, for instance). So you have a kernel that can't talk to the hardware until manufacturer X says it can.
And so we wait for HTC or Qualcomm or whomever to release their drivers.
Sorry for the rant (and thanks for the solidarity, sm-x), this Google Nav thing just set me off. The hack-a-day progress on XDA is really wonderful but we should have real access to the code so we can make it better, not just reverse engineering...I can do that on my iPhone/iPod.
2.0 is out of the question without the binaries from HTC, but 1.6 should be doable with the 1.5 bits. It'd take someone with a lot of time and dedication, though.
kRutOn said:
2.0 is out of the question without the binaries from HTC, but 1.6 should be doable with the 1.5 bits. It'd take someone with a lot of time and dedication, though.
Click to expand...
Click to collapse
How about tricking the rom into showing itself as 1.6? Not sure what all that would entail tho
5tr4t4 said:
This is not how open source is supposed to work. We're not birds in a nest waiting for a worm. We don't wait for them, they have to keep up with us.
IMHO we should put aside the idea of holding out for Sprint, months or even weeks for 2.0 is WAY too long in 2009. The code is up (all of it now?), the SDK is up. Let's build it!
This, to me, is one of the most disturbing trends in Android, each manufacturer providing tweaks or proprietary GUI's that put them in control of the development cycle. In my humble opinion we need to get past that as soon as humanly possible. If that means ditching Rosie and Blur, so be it.
Today we wait for Google Nav, tomorrow we'll wait for security updates bugs, optimizations, and most importantly cool developer tweaks. Hell, we waited 6 weeks for the piddly MR update that fixed problems that should have been solved before the phone left the store.
Can someone with more intimate knowledge of Android (I'm studying it now myself so I can help) say something about how to get to a clean, universal Android ROM? I'm happy to help however I can.
Click to expand...
Click to collapse
I also agree with this. I wrote up a little article about it:
http://www.thesearethedroids.com/2009/11/24/a-look-into-custom-ui/
well said gents

Dream devs have a Hero 2.1 dump er,... rom!

Update!!!
Looks like Drizzy and the Dream boys unwatermarked the dump and made a G1 rom out of it. I will try to talk to Drizzy and ask if I can have the unwatermarked dump but if not we should be able to re-port this back to CDMA and possibly have Hero 2.1. Just remember this wont work as well with our phone as the official one will but a little taste of an Eclair might be good
http://forum.xda-developers.com/showthread.php?t=592568
Hey guys, didnt know if anyone saw this yet but the Dream devs have a Hero 2.1 dump. Drizzy got it and is sharing it with a couple devs but no Hero devs. Not sure why yet but Im trying to find out. I would assume it's because of watermarking and once they get that worked out then they will release it to us. Some of the Dream users don't like us because we have more ram than them (yes, thats the only reason why) but the devs over in the Dream scene are overall good guys. Drizzy, KingClick, BarakInFlorida, Crykowski and the rest are all good guys so I'm sure once they work things out we will get ahold of it. Lox_Dev (from GSM Hero) is already trying so, let's hope and pray.
Does this mean that HTC already has sense skinned on top of 2.0?? If so, does the Hero 2.1 dump you are talking about mean that we could have Sense on 2.0 before its even officially released by HTC? (And even modified and optimized on top of that?!!!) I'm really excited if any one of your answers will be "yes".
I'm new to all this stuff, but I'm really enjoying it so far! Thanks in advance for answering my questions. God bless!
-alex
alexthearmo said:
Does this mean that HTC already has sense skinned on top of 2.0?? If so, does the Hero 2.1 dump you are talking about mean that we could have Sense on 2.0 before its even officially released by HTC? (And even modified and optimized on top of that?!!!) I'm really excited if any one of your answers will be "yes".
I'm new to all this stuff, but I'm really enjoying it so far! Thanks in advance for answering my questions. God bless!
-alex
Click to expand...
Click to collapse
Yes, pretty much. First, I just want to say that Sense is not a "skin" it is an application but more than that, it is an application framework built by HTC. That said, it looks like HTC has created a Sense for Android 2.1, which hasnt even been released yet and someone from the inside of HTC leaked it out. Now, a Hero guy (E2K) was able to get it from Drizzy apparently but we are still waiting to see if he actually got it or is bsing us.
Also, please note that usually when an HTC dump is leaked this means that it is pretty close to release. They are just sending out to testers and fixing all the bugs. This means that HTC could be giving us a Christmas present soon. Also remeber though that after HTC releases it, Sprint still needs to work their "magic" into it so it may take a little longer than normal. Also, if your phone is rooted us devs will want to make sure nobody loses root in upgrading.
OMGAD release it then ! now
thanks for clarifing
dude thank you. im so tired of everyone calling "Sense U - fu*king - I (USER INTERFACE) its a app. Just like the Adv Launcher. If you dudes could get your mind over having some cool ram additive, rather than all the ammenities of the Dream, than you would realize that you could be running 2.0 like the rest of us, rather than 1.5, and have waaaay more bad ass **** on ur phones!
Examplessss
CubeUI - Samsung Behold 2
TouchWizUI - LG EVE
SenseUI - Hero, Rooted g1's
AndroidUI - Dream, Droid, ADP1, Rogers Dream, Etc....
See its all just a different setting for a different phone .. All thus running on Android OS. Its rather simple. LOOK OUT FOR 2.1
Thanks for the answers! That's great news! I'm rooted and flashed running FRESH 0.6. I plan on NOT getting Sprints update when it comes out, but getting it from you XDA guys in some optimized/tweaked ROM without all the crap they put in to bog it down. I'm so pumped! Thanks again for the answers! God bless!
-alex
georgegreco86 said:
dude thank you. im so tired of everyone calling "Sense U - fu*king - I (USER INTERFACE) its a app. Just like the Adv Launcher. If you dudes could get your mind over having some cool ram additive, rather than all the ammenities of the Dream, than you would realize that you could be running 2.0 like the rest of us, rather than 1.5, and have waaaay more bad ass **** on ur phones!
Examplessss
CubeUI - Samsung Behold 2
TouchWizUI - LG EVE
SenseUI - Hero, Rooted g1's
AndroidUI - Dream, Droid, ADP1, Rogers Dream, Etc....
See its all just a different setting for a different phone .. All thus running on Android OS. Its rather simple. LOOK OUT FOR 2.1
Click to expand...
Click to collapse
Well just because we have Sense doesnt mean we can run other roms. In fact we cant. I have tried porting over tons of different roms to Hero and they never seem to work. Sense is good too. Personally, I prefer it over Vanilla Android. Plus, the HTC apps such as messaging and whatnot are better in my opinion. Personal preference. Once optimized, Rosie flies. Sense isnt bad. I just wanted to say it's an application. Not a skin or anything.
Regardless, hopefully we will have 2.1 soon
sounds Great Im excited...God Bless
Is it really that simple though? I imagine the dump is based off the Euro(GSM) Hero.
Natty_lite said:
Is it really that simple though? I imagine the dump is based off the Euro(GSM) Hero.
Click to expand...
Click to collapse
Most likely is. But 1.6 on up has native CDMA support. Either way, Lox from the GSM dream forums says that the guy who leaked the rom to us just will not give up his source which means that if we do get this we cant release anything. Looks like we are gonna have to wait a few weeks anyway. I also was reading that Drizzy just wasnt thrilled with this build. As it is beta (or *gasp* alpha) there is too much that isnt working. Good news is we know it's coming.
http://twitter.com/Official_Drizzy/status/6156799589 "Official RUU for WWE Hero 2.1....."
Hmm.. does this mean we could possibly see a build for our CDMA Hero sooner than we thought?
Exciting news! I'll be watching this thread closely for any updates. Also, like others have said, I will be coming here for an optimized/bloatware free 2.1 from one of the awesome devs who do great work for our Heros!
chuckhriczko said:
Most likely is. But 1.6 on up has native CDMA support.
Click to expand...
Click to collapse
What does this mean for us? The possibility of cross-platform roms?
Dunno if this has already been posted:
Screenshots
Yeah I really can't wait for that landscape mode on home menu
ruskiyab said:
What does this mean for us? The possibility of cross-platform roms?
Click to expand...
Click to collapse
Possibly, yes. One of the reasons it is so hard to port over roms to our phone is because it is CDMA. 1.5 does not have CDMA built in. For instance, try porting over any GSM rom and it wont work because HTC "hacked" in the CDMA support (i.e. built a custom driver). Since 1.6 and up have built in CDMA support the possiblity for us to make cross platform roms is a lot higher. Not saying definite. Just more possible.
chuckhriczko said:
Possibly, yes. One of the reasons it is so hard to port over roms to our phone is because it is CDMA. 1.5 does not have CDMA built in. For instance, try porting over any GSM rom and it wont work because HTC "hacked" in the CDMA support (i.e. built a custom driver). Since 1.6 and up have built in CDMA support the possiblity for us to make cross platform roms is a lot higher. Not saying definite. Just more possible.
Click to expand...
Click to collapse
Is there something "missing" from Google's 1.6 or 2.0 sources that a build of either of those prevents the CDMA Hero from running them at all? Or will they at least boot up and work with some stuff not working?
I tried installing it on my Sprint hero, well not 2.1 but the 2.0 that works on the gsm, it doesn't work.
chuckhriczko said:
Possibly, yes. One of the reasons it is so hard to port over roms to our phone is because it is CDMA. 1.5 does not have CDMA built in. For instance, try porting over any GSM rom and it wont work because HTC "hacked" in the CDMA support (i.e. built a custom driver). Since 1.6 and up have built in CDMA support the possiblity for us to make cross platform roms is a lot higher. Not saying definite. Just more possible.
Click to expand...
Click to collapse
Yeah. The kernel. I tried booting both but neither even bootup.
you still need to compile the hero cdma radio driver for android 2.x

[Think Tank] Eclair video codecs issue ...

So I've been looking at the video codecs issue that blocks YouTube HD and video recording on the Dream. Seems there are two underlying issues, libsgl from donut was merged into a new library, and that theres an API break in libhardware.
On the first issue, its fairly easy to build donut's libsgl.so on eclair with some minor changes to source to get it, build it, and it seems that it works properly (as far as I can tell, the OpenGL 3D interface it binds to has had a stable API). I don't have a strong test case to use it on.
The second problem is more interesting. It seems to me that the problem with the API break is that Qualcomm is using enum's in a way that is absolutely stupid, and added new numbers that broke the magic numbers copybit needs. This causes a set of copybit failures when blitting stuff to the screen. Rebuilding the proprietary libraries would fix the problem, but as we only have libraries built against 1.6, this obviously won't work, so I'm seeing if theres a better solution we can use to solve this problem. Any ideas welcome.
NCommander, you've done amazing work here before
unfortunately, based on my research and trying to merge patches from 1.6 into 2.0 source and vice versa, that this is nearly impossible.
I would expect that the only feasable way would be to make a whole new composition method for android, based loosely off the methods shown in the 1.6 source.
Unfortunately, i think that it will be best to wait for HTC to work with qualcomm, and actually release something. I've heard that the MyTouch will be getting the 2.0/2.1 update, and hope that this release will solve our problems.
Noting is impossible
jcarrz1 said:
NCommander, you've done amazing work here before
unfortunately, based on my research and trying to merge patches from 1.6 into 2.0 source and vice versa, that this is nearly impossible.
I would expect that the only feasable way would be to make a whole new composition method for android, based loosely off the methods shown in the 1.6 source.
Unfortunately, i think that it will be best to wait for HTC to work with qualcomm, and actually release something. I've heard that the MyTouch will be getting the 2.0/2.1 update, and hope that this release will solve our problems.
Click to expand...
Click to collapse
Camera didn't work but now it does. Youtube will work 100% very soon
Interesting.... could we possible encapsulate the existing libhardware and create a new interface to it to translate the new calls (enums) to existing? Just throwing the idea out there - probably too simple and I am missing something not knowing too much of the details. I guess I would think of a libWINE like approach, interface just translates the new expected calls to the old driver....
if all goes well, will this also help speed up things like live wallpapers? (sorry if this is a noob question)
smackdown85146 said:
if all goes well, will this also help speed up things like live wallpapers? (sorry if this is a noob question)
Click to expand...
Click to collapse
In theory, it would allow any opengl call to be handled on the GPU. Not only would the livewallpaper speed up, but you'd have more available CPU time for other operations.
The idea is sound, the tricky part is making them efficient enough to actually be a net benefit. It could decent stopgap until new drivers are released.
????-????
So your saying that the first eclair roms where 1.6 with 2.0 skins?
llxll0m3g4llxll said:
So your saying that the first eclair roms where 1.6 with 2.0 skins?
Click to expand...
Click to collapse
No, not entirely...when the Eclair Roms roms were first being made in the beginning Devs didnt have the drivers for the camera. But, thanks to NCommander we do now =)
Android G1 2.0 Update
T-Mobile Czech Republic officialy announced 2.0 update for G1 for end of January (1-2 weeks). Maybe is better wait for this release.
pinkolin said:
T-Mobile Czech Republic officialy announced 2.0 update for G1 for end of January (1-2 weeks). Maybe is better wait for this release.
Click to expand...
Click to collapse
Isn't january ending... tomorrow?
vincom2 said:
Isn't january ending... tomorrow?
Click to expand...
Click to collapse
yeah, my senses tell me that it is
Yes, but this is Europe, "End of January" is in T-mobile speak half of February :-D. I have Google Translate page with this info, but i'm Junior member without rights :-D.
Eh would probably be too lazy to go back to stock anyways, will just have to wait for those video drivers =)
pinkolin said:
Yes, but this is Europe, "End of January" is in T-mobile speak half of February :-D. I have Google Translate page with this info, but i'm Junior member without rights :-D.
Click to expand...
Click to collapse
This can be "helpfully" for your work on this thread. More info:
http://forum.xda-developers.com/showthread.php?t=625108
http://www.4shared.com/file/207649694/b347bfad/RUU_Sapphire_HTC_Europe_304401.html
Is a full origianl ROM 2.1 for HTC Sapphire, the problem is that it only works on 32A, and I think that this can be a problem.
shawe_ewahs said:
This can be "helpfully" for your work on this thread. More info:
http://forum.xda-developers.com/showthread.php?t=625108
http://www.4shared.com/file/207649694/b347bfad/RUU_Sapphire_HTC_Europe_304401.html
Is a full origianl ROM 2.1 for HTC Sapphire, the problem is that it only works on 32A, and I think that this can be a problem.
Click to expand...
Click to collapse
I don't see anyone in that thread indicating that it's a 2.x ROM, just that it's a potential way to root some newer 32A SPLs. Might help some Rogers people out. Am I missing something? Have you pulled the build.prop?
olearyp said:
I don't see anyone in that thread indicating that it's a 2.x ROM, just that it's a potential way to root some newer 32A SPLs. Might help some Rogers people out. Am I missing something? Have you pulled the build.prop?
Click to expand...
Click to collapse
Its probably the default rom that comes with the phone.
How close is the camera in the g1 to the camera in the Hero ? I keep seeing articles that HTC is releasing 2.1 upgrade for the hero. Will this help the g1 ?
menace said:
How close is the camera in the g1 to the camera in the Hero ? I keep seeing articles that HTC is releasing 2.1 upgrade for the hero. Will this help the g1 ?
Click to expand...
Click to collapse
yup with the 2.1 upgrade ur g1 can take 10mp pics
bakgwailo said:
Interesting.... could we possible encapsulate the existing libhardware and create a new interface to it to translate the new calls (enums) to existing? Just throwing the idea out there - probably too simple and I am missing something not knowing too much of the details. I guess I would think of a libWINE like approach, interface just translates the new expected calls to the old driver....
Click to expand...
Click to collapse
Sounds like ndiswrapper for linux
gregnotcraig said:
Sounds like ndiswrapper for linux
Click to expand...
Click to collapse
doesnt it though

[Source code][GINGERBREAD]Android 2.3 just dropped

http://developer.android.com/sdk/android-2.3.html
Sent from my SPH-D700 using Tapatalk
Oh my. +99
Sent from the future.
I await all ROMs with gingerbready Greatness!!
And to be honest, I thought we'd be a little ways into Jan before we seen the source code. Glad it took just 1 day after the Nexus S release. Now, the many-months wait for OEMs to get Official updates out to the devices =\
if that was sent from the future, that comment must mean that you are afraid for us because something is WRONG with gingerbread because you would have KNOWN about this already! LOL so HOW IS IT?!?!?
Yay!
Sent from my Epic 4G
Yet still no official 2.2 for us.... awesome.
Is this different from what was dropped last week?
Sent from my SPH-D700 using XDA App
How did GB source C drop before FroYo????????
If you are referring to what I posted, it was source code
For the Nexus S kernel Android version 2.3
And yes, pretty cute we have available source code for a new
OS before we seen a piece from any Android 2.2 source code for our Epic
jaaka78 said:
Is this different from what was dropped last week?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Sent from my SPH-D700 using Tapatalk
Now for the million dollar question. What are you predictions for a working 2.3 rom for our Epics?
sprice5 said:
Now for the million dollar question. What are you predictions for a working 2.3 rom for our Epics?
Click to expand...
Click to collapse
Slow down, Sprice. Gotta get 2.2 first.
sprice5 said:
Now for the million dollar question. What are you predictions for a working 2.3 rom for our Epics?
Click to expand...
Click to collapse
I think the million dollar question is what are the predictions for an official 2.2
rom for our Epics? jk but I think after samsung and sprint gets ahold of it first.
Otherwise it would be another AOSP like cyanogen.
I've got a related (and hopefully not stupid) question regarding the process.
So, I know we're waiting for the 2.2 kernel source for our epics, obviously.
Generally, what's the process in between Google dropping a version's source, and it being released (by samsung) to us? This is not a complaint-- I'm really just curious how it works.
decalex said:
I've got a related (and hopefully not stupid) question regarding the process.
So, I know we're waiting for the 2.2 kernel source for our epics, obviously.
Generally, what's the process in between Google dropping a version's source, and it being released (by samsung) to us? This is not a complaint-- I'm really just curious how it works.
Click to expand...
Click to collapse
I know someone can explain better than I can.
Google drops the stock rom. This wont run on our phones without drivers, and support for specific hardware for our device. Then you have Sprint carrier modifications like VVM, ota updates, 4G and other configured apps. After all the work is done, developers can go back and modify things to their liking.
Otherwise you would have a from the ground up like CM,
where its a lot of trial and error, getting the ROM to support hardware/software.
sprice5 said:
Now for the million dollar question. What are you predictions for a working 2.3 rom for our Epics?
Click to expand...
Click to collapse
I'm no developer or expert, but i'd give it a week or two before we see a slew of ROMs, maybe less. Its great that Cyanogen has 4G working on the Evo, so cant wait for 4G-enabled CM6/7 for our Epics. As for an official 2.3 update from Samsung.... March is my earliest guess
hayabusa1300cc said:
I think the million dollar question is what are the predictions for an official 2.2
rom for our Epics? jk but I think after samsung and sprint gets ahold of it first.
Otherwise it would be another AOSP like cyanogen.
Click to expand...
Click to collapse
I'd say we get official 2.2 updates in a few weeks. The leak is out, so they are probably just cleaning it up for release. The plain-jane (no custom ROM) leak works flawlessly on my phone tho.
At this point Noobnl is going to deliver faster than Samsung is on the Froyo. He's got CM pretty much done it seems. Whenever Cyanogen's done with gingerbread source for CM7(im presuming) noobnl will hopefully start on that as well.
I bet that the hardware drivers for 2.2 will work with 2.3, sounds like 2.2 to 2.3 is a lot less of a change than 2.1 to 2.2, but I could be wrong.
sent from my nexus s with a keyboard
For Samsung it's more rational for them to use their dev's time to spend on making new working firmware for new devices that are debuting at CES and to ready the firmware for those devices.
Samsung's strategy has changed over the years and is now executing the mantra "first out the door with new technology." While this is great for those of us who like new toys, it's a set back when we want long term support for our new toys. If their R&D resources are tied up working out new firmware for the next gen, they lose focus on their current customers.
If you've kept up on the latest engadget, gizmodo, boy genius, etc etc news - you'll know there's a dual core super duper galaxy whatever chip coming out soon. That's where the resources are now. For a company that has been lagging behind in innovation for the last few years in the mobile area, this is their new direction... Innovate quickly and be the first to market. Support resources are but a second thought; overhead.
http://www.bloomberg.com/news/2010-...uct-crisis-as-choi-tries-to-triple-sales.html might give you a better perspective of the company.
So if I am reading this right....
Once we have CM6 running on our epics it will be a lot easier for us to get Gingerbread installed; for that matter any new verisions?
Does this really need to be in the Epic section?

Gtablet gingerbread nvidia drivers available now..

http :// android.modaco.com/content/lg-optimus-2x-2x-modaco-com/338920/6-may-v20c-gingerbread-rom-leak-for-the-t-mobile-g2x/ is the new tmobile beta release for the G2x which has the drivers for ginger in it. Just wanted to give it to the devs so they can make use of it.
Awesome!!!! Go gojimi
Awesome. Very good news.
It looks to me like that leak is a rom for a phone. Does anyone know if it is based on the harmony tegra 2 chip like the gtab? If so, then this may be really great news.....
I'll hold off my excitement until someone who knows better can chime in and confirm.
G2x has the harmony chipset its a Tmobile phone suppose to be getting ginger from a OTA update in a few months. Essentially the same drivers we use are compatible with this phone so that means there is our ginger drivers.
I remember they have source codes for the driver already, just need to integrate, if I am not wrong.
Unless they just got it because nvidia still hasnt released them to the public. Thats what the fuss was about for the past month.
dynamicj said:
Unless they just got it because nvidia still hasnt released them to the public. Thats what the fuss was about for the past month.
Click to expand...
Click to collapse
cannot remember the exact news source,
fyr
http://forum.xda-developers.com/showpost.php?p=13510312&postcount=1085
I stand corrected from what I seen I never knew they recieved the acceleration drivers for it.
haymant said:
cannot remember the exact news source,
fyr
http://forum.xda-developers.com/showpost.php?p=13510312&postcount=1085
Click to expand...
Click to collapse
I think CM7 only has hacked drivers ( reverse engineered), not the originals from Nvidia.
So this phone IS harmony based...... OK....I am a wee bit excited.
JUST A WEE!!
This is what I love about this community, XDA is about information.
Information is the drug of today's society and no one brings it faster than the collective.
I was thinking maybe on the way of hacked up drivers because my quadrant score is retarded low on cmod7.0.3
Kinda curious why none of the devs commented on this yet. wonder if were high hoping for nothing....
Thread title isn't really accurate. We have a rom from the gx2 that should contain the drivers we need. So far I don't think we have the drivers yet, not until someone with the skills has the chance to tear them out of that rom dump and get them working.
That didn't I can't wait, it's the only thing keeping me from running cm7

Categories

Resources