I just read gingerbread 2.3 source is release .. - G Tablet General

I just read on engadget's web site the source code for Googles Gingerbread
was release to the public. Does this mean we might see a new build of TnT
lite or Vegan for the gtab in the coming weeks?

We don't have the important stuff, like the Tegra-specific source code or kernel drivers. Hopefully VS is going to do something about that, soon. But I'm not getting my hopes up.

Related

Did i read this right? Devs have their hands on gingerbread, are porting to devices

http://www.xda-developers.com/andro...her-phones-heres-our-frequently-updated-list/
Thread title says it all.
They have the AOSP source code so yes many phones have gingerbread right now but not an official release or anything like that
cyanogenmod 7 nightlies start next week.
Moved to general
Allenfx,
I went to several of the sites and as I understand it what has been done is release the stock Android 3.0 Honeycomb stuff to the developers. But now they will have to tailor it to the hardware of the individual devices. I did see tegra2 stuff where I looked.
So I think you might say it is coming. But it will depend on how long it takes to get all the drivers and settings to work.
It will not be a quick process like the updates for VEGAn, TNT, etc. Much more work and detail to be done.
If this doesn't answer the question, someone straighten me out!
Rev
Nice to know its being worked on
Not sure it makes any sense to spend too much time working on GTablet ports to Gingerbread (i.e. Android 2.3) when I'd expect that Honeycomb (Android 3.0) devices will be out shortly and the Honeycomb source will drop for AOSP use within a couple of weeks of the first device -- which looks like it may be the Motorola Xoom...
As mentioned, Cyanogenmod 7 will be Gingerbread and will likely be the first ported to the GTablet (assuming that there isn't too much driver tweaking involved between Froyo and GB)
2.3-3.0
I think we will see gingerbread in early summer officially released by viewsonic, although modders here will most likely have a great Rom based on 2.3 before then. My bet(just my opinion) we wont see Honeycomb on the G tab until sometime in the fall.
Would love to be wrong and see 3.0 sooner.....
WantADroid said:
I think we will see gingerbread in early summer officially released by viewsonic, although modders here will most likely have a great Rom based on 2.3 before then. My bet(just my opinion) we wont see Honeycomb on the G tab until sometime in the fall.
Would love to be wrong and see 3.0 sooner.....
Click to expand...
Click to collapse
What is your source for Gingerbread being available in summer from Viewsonic?
Source Please?
Notice how he said "I think" and "my opinon". The source is himself.
markalanlewis said:
Notice how he said "I think" and "my opinon". The source is himself.
Click to expand...
Click to collapse
That was a little joke for my amusement.
But thank you, I think you made my point for me. I had made a comment in another post and gave my opinion and wantadroid asked me to site my source of information (inside info). I posted that I have read... and I got this reply:
"Please give us your inside info on the hardware problems.... I haven't found A thing to make me believe the G tab won't EVENTUALLY get Honeycomb."

[Q] Samsung Captivate Source Code Now Open?

I think I just made a mess in my pants. Can someone confirm this??? Here is the letter:
Dear _____________,
You can download the source code of SGH-I897 on this site in Mobile Category, SGH-I897 model.
Thank you.
Weighing in at about 161 megabytes, the code should assist developers wishing to work on custom Captivate ROMs. Samsung Captivate owners have been eager to see their first custom builds as the device has sold thousands already since its nationwide launch at AT&T on the 18th.
In particular, there is one mod that Captivate owners are excited about the most: the “mimocan external SD card lag fix.” The fix promises to double Quadrant benchmark scores as the application data is moved to the external memory. Right now, the Samsung Galaxy S series outperforms every processor in every phone in every category except for the I/O benchmark in Quadrant. The Galaxy S scores so poorly because of Samsung’s implementation of the internal memory, but mimocan’s lag fix remedies this problem and raises Quadrant scores to new heights around 1750.
With Android 2.2 just around the corner for American Samsung Galaxy S owners, Captivate users could be seeing benchmarks around 2000-3000 with the JIT compiler and mimocan lag fix.
So, what are you waiting for? You can download the open source code below or at Samsung’s Open Source website.
Download SGH-I897_Opensource.tar.gz
Click to expand...
Click to collapse
Originally Posted Here
Google is your friend https://encrypted.google.com/search...s=org.mozilla:en-US:official&client=firefox-a this letter is from last summer. Now go clean up and put on some new pants.
Every time they officially release a firmware, they are required to release source code. So, yes, captivate source code has been available for JF6 and JH7 for a while.
And with Rogers already released 2.2 firmware, they will have to release source code to Roger 2.2 as well.
Mind you, not everything is released in source code. For most part, drivers are not open source released.
Someone just posted over in the dev forums, the Rogers 2.2 Source is live (just downloaded this morning) so hopefully we'll see some nice updates on the ROMs in the next several days...
pinoymutt said:
Someone just posted over in the dev forums, the Rogers 2.2 Source is live (just downloaded this morning) so hopefully we'll see some nice updates on the ROMs in the next several days...
Click to expand...
Click to collapse
these have all been out for a while

Samsung releases official Froyo for Captivate then quickly takes it back

Samsung Captivate Android OS 2.2 Upgrade Released Then Quickly Pulled
By Ed Hardy, Brighthand.com Editor | 2/17/2011
Send Mail Comments Print Bookmark and Share
The long-awaited upgrade to Android OS 2.2 (Froyo) for AT&T's Samsung Captivate was released today... only to be quickly withdrawn.
Currently, it's not clear if this system software upgrade was released by mistake, or if a bug was found in it almost immediately.
This is just another blow to users of the Captivate, which was released last summer with Android OS 2.1, even though the latest version of Google's mobile operating system at that time was already OS 2.2.
Although Samsung has committed to releasing an upgrade for this model, and at one point said this would be available by the end of November, users of this smartphone are still waiting.
Since then, Google has introduced Android OS 2.3, which is currently available only on the Samsung Nexus S.
New in Android OS 2.2 (Froyo)
Android OS 2.2 is required for devices to run Adobe Flash Player 10.1, which allows the web browser to fully make use of websites that use Flash for navigation, games, and showing video.
This version of Google's operating system also contains a number of other enhancements, such as faster performance thanks to a new JIT compiler and the ability to store applications on a removable memory card.
In addition, Samsung has promised that this system software upgrade will include a fix for a bug that sometimes causes these smartphones to be unable to get a GPS lock.
source: brighthand.com/default.asp?newsID=17530&news=Samsung+Captivate+Google+Android+OS+2.2+Froyo+Upgrade
Also, see:
gizmocrunch.com/android/5414-samsung-captivate-froyo-update
This news is days old and there have been at least 5 threads about this already...mods please close this.
/flameon
something pretty significant has happened (release of froyo source for both epic and vibrant). Both were released pretty quietly and have started seeing some reports of the epics push starting the 21st.
I don't think it will be long before we see the source released for the captivate.
Its kind of weird for me personally...
Do I really care about the official Froyo 2.2? Not really...
Do I want AT&T/Samsung to release it? If they promised it, they should...
I only want to see it release to know that a major company kept their word. Plus, if it helps the devs here release other ROMs based on a true US Cappy build, then I'm all for it.
I'd like to see it released, but I'm not so sure that I'll be rushing back to stock so I can update to it.
And the story is wrong. Froyo was never released... no one downloaded it.
The only thing that was released was some instructional pages.
Posting a story that is wrong is even worse then posting rumors.

Ice Cream Sandwich and HoneyComb Source Released to AOSP

https://groups.google.com/forum/#!msg/android-building/T4XZJCZnqF8/WkWhGUYb4MAJ
Hi! We just released a bit of code we thought this group might be interested in.
Over at our Android Open-Source Project git servers, the source code
for Android version 4.0 (Ice Cream Sandwich) is now available.
Here's how to get it:Follow the instructions at
http://source.android.com/source/downloading.htmlCheck out the
'ics-release' branch:repo init -u
https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
That's it! However since this is a large push, please be aware that it
will take some time to complete. If you sync before it's done, you'll
get an incomplete copy that you won't be able to use, so please wait
for us to give the all-clear before you sync.
This is actually the source code for version 4.0.1 of Android, which
is the specific version that will ship on the Galaxy Nexus, the first
Android 4.0 device. In the source tree, you will find a device build
target named "full_maguro" that you can use to build a system image
for Galaxy Nexus. Build configurations for other devices will come
later.
Unfortunately we still don't have our Gerrit code review servers back
online. That remains our top priority though, and we hope to have them
back soon.
This release includes the full history of the Android source code
tree, which naturally includes all the source code for the Honeycomb
releases. However, since Honeycomb was a little incomplete, we want
everyone to focus on Ice Cream Sandwich. So, we haven't created any
tags that correspond to the Honeycomb releases (even though the
changes are present in the history.)
JBQ, on behalf of the AOSP team.
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Click to expand...
Click to collapse
It looks like the HoneyComb source was released also. Will this help any active HoneyComb ROMS?
Getting some real support for the Tegra in the Gtab is all I care. Might as well just skip HoneyComb and go straight to ICS.
I thought I had a much longer wait for this, can't wait for the CyanogenMod 9 builds.
Yes, it will help. I hope that people can post the rest of the ICS posts under this topic because with the release of the Honeycomb and Ice Cream Sandwich source codes noobs are gonna go crazy.
Noob here and yes I am going crazy.
Woooooo!!!!
Sent from my Eris using XDA App
HwyXingFrog said:
Getting some real support for the Tegra in the Gtab is all I care. Might as well just skip HoneyComb and go straight to ICS.
Click to expand...
Click to collapse
Ditto on that. Honeycomb really is (was) the Vista of Android.
well
I hope we get a smooth running build of one of the two. I am currently running Vegantab and its pretty smooth but it might freeze here and there or hang on the browser, etc.. Its still my daily runner.... So again, I simplty hope we get a very stable ROM egardless of which. Plus, as HWYxingfrog said, some actual tegra support would be great...
Woot
Sent from my Epic 4G Touch
ICS source released. Will gtab be getting it?
I hope so and will support the devs who are!
please keep topics like this in this thread. http://forum.xda-developers.com/showthread.php?t=1346829
It will help....but keep in mind that there are still no hardware drivers/kernel for the Gtablet beyond Froyo (OS 2.2).
The same issues getting Honeycomb running will be present with ICS though more insight in to the OS will be available with the source. Still no Nvidia "Harmony" kernel or drivers though....
Y'all work on this...
I'll be in Skyrim!!!
I would be surprised if Nvidia released anything for the Harmony board. Considering they already have an HC 3.2 image for Ventana, my guess is this is were all their efforts will go. Afraid we will be stuck with ported versions with no supported drivers.
what happened with the .36 kernel and all the current development for gtab?? are the devs going to have to start all over? why no update for gtabcomb? it ne'er came out of beta? hmmmm...why develop for transformer and galaxy tab if;they already have stable version of os?
jedibbq said:
what happened with the .36 kernel and all the current development for gtab?? are the devs going to have to start all over? why no update for gtabcomb? it ne'er came out of beta? hmmmm...why develop for transformer and galaxy tab if;they already have stable version of os?
Click to expand...
Click to collapse
It's still being worked on. IF you read my posts in this thread I've posted basically all the recent updates the devs have made with the .36 kernel.
http://forum.xda-developers.com/showthread.php?t=1231577&page=10
jedibbq said:
what happened with the .36 kernel and all the current development for gtab?? are the devs going to have to start all over? why no update for gtabcomb? it ne'er came out of beta? hmmmm...why develop for transformer and galaxy tab if;they already have stable version of os?
Click to expand...
Click to collapse
Allow me to disavow this uninformed complaining. Thanks for all the hard work devs.
The HC roms run pretty smoothly for the most part, is the release of the source code going to help the development of ICS roms? I know itll help but I mean will it make it easier then it was trying to get HC on the G-Tab
I remember something about nvidia/vsonic (cant remember which one) saying they wouldnt release something for honeycomb since google didnt release the source code..
So i xpect they at least release driver specs or source this time
Sent from my DROID3 using Tapatalk
brettdwagner said:
Allow me to disavow this uninformed complaining. Thanks for all the hard work devs.
Click to expand...
Click to collapse
not complaining just asking legitimate questions.. supposedly even though google sort of released the code for honeycomb its still up to nvidia to release drivers.without those no working ics rom for gtablet
jedibbq said:
not complaining just asking legitimate questions.. supposedly even though google sort of released the code for honeycomb its still up to nvidia to release drivers.without those no working ics rom for gtablet
Click to expand...
Click to collapse
Double question marks "??" and "hmmmmm..." don't typically accompany legitimate questions.
"Why isn't this out of beta? Why are they working on other devices and not mine?"

Google already rolling out ICS 4.0.4?

This is what makes me crazy about Google and Android (and yes, companies like Samsung) - the uneven distribution of updates (I know, I know). In this case, some devices are already receiving 4.0.4 while many of us are still stuck waiting for the (empty?) promises to update to 4.0.
Just sayin'.
http://androidcommunity.com/android-4-0-4-ics-rolling-out-for-nexus-s-xoom-and-galaxy-nexus-20120328/
Google just develop the OS itself. Whether the device run the system depends on hardware vendor.
The current situation is like MS just released Windows 7 but your PC(part) manufacturer has not released new driver yet.
That is a good way to look at it and completely agree with it. The laptop I have hasn't seen a graphics driver update in 6 months now. Something that should be kept up to date on a monthly basis
If it really comes down to it hopefully Samsung will get their act together and release the full source code for our Tablet. Than at that point we can take matters into our own hands.
C'mon guys. The 4.0.3 had lots of bugs. I updated it on my GF'S Nexus S when just been released and battery was drained in few hours. Devs from all devices (for example Xoom - which I have) had to work out to fix issues that have been fixed by Google after months in 4.0.4
So I'm not so disappointed for having not received the 4.0.3 (even 'cuz we have too few devs). I trust in Samsung and believe there will be avaible on April Let's wait
N.b.
I have a Galaxy Note and the only ROMS for ICS avaibles are leaked from the Chinese version of my device. ICS has not been released yet (and we're talking about NOTE...)
Sent from my Galaxy Note with DarkyROM 3.3
i don't really care what bs version samsung is going to release for tab plus's ICS.
the only thing i care is the source code! the faster they release the source code, the faster someone could work on CM9 for tab7plus. THAT is what matter!
gingerboy92 said:
i don't really care what bs version samsung is going to release for tab plus's ICS.
the only thing i care is the source code! the faster they release the source code, the faster someone could work on CM9 for tab7plus. THAT is what matter!
Click to expand...
Click to collapse
ICS source from Samsung has no real effect on CM9. CyanogenMod is an AOSP ROM which means that it's not built from Samsung's sources, it's built straight from Google's upstream sources. That's how devices like the HP TouchPad, Kindle Fire and Nook Tablet have CM9 builds now - none of these devices ever had ICS sources released.
Right now, the only thing that's really holding back CM9 development on the tab7plus is a lack of tab7plus owners contributing to a CM9 port.
yeah Im waiting for CM9, gave up on Samsung. If they release it great. Id rather CM9 anyday, even with no wifi!!
h2g2 said:
ICS source from Samsung has no real effect on CM9. CyanogenMod is an AOSP ROM which means that it's not built from Samsung's sources, it's built straight from Google's upstream sources. That's how devices like the HP TouchPad, Kindle Fire and Nook Tablet have CM9 builds now - none of these devices ever had ICS sources released.
Right now, the only thing that's really holding back CM9 development on the tab7plus is a lack of tab7plus owners contributing to a CM9 port.
Click to expand...
Click to collapse
not the kernel source, and don't forget the wireless chip/adapter/card(?)'s source code.
but yeah, i do agree. we need more devs to work on our tab!
We're still lacking driver source (i.e. our Atheros wifi driver) so even if we got someone to port CM9 to our tabs, we'd have no wifi functionality. The only way to get drivers (with no proper source code released for them) is to reverse engineer the driver(s) themselves, which is a difficult task to say the least.
The reason why most of us say we're waiting for our tabs "ICS Source" is because we're hoping Samsung actually releases our wifi Driver Source code this time.
But...if I remember correctly...someone had pointed out that although Samsung had not released proper source code for our wifi driver, another Sony device that uses it had released code that we could "possibly" use. No one has really confirmed nor denied anything past that recently. Maybe Gary can comment on this issue soon, could clear up a lot of questions for me and everyone else
Sent from my SPH-D700 using xda premium
the real problem here is that samsung is "promising" ICS "soon". it would be easier if they say they are going to release it next year or even not going to release it at all.
gingerboy92 said:
not the kernel source, and don't forget the wireless chip/adapter/card(?)'s source code.
but yeah, i do agree. we need more devs to work on our tab!
Click to expand...
Click to collapse
Kernel source doesn't mean driver sources. Remember that drivers don't need to be integrated into the kernel - if Samsung (or the manufacturer of the device) chooses to implement the driver as a binary-only lkm, there's no obligation on Samsung's part to release the source code for the driver.
This has been a problem with Linux drivers in general for a while. I could be wrong, but my sense is that if the needed driver isn't already available in source code from the manufacturer directly, it's unlikely that Samsung will include it in their kernel sources.
---------- Post added at 10:35 PM ---------- Previous post was at 10:20 PM ----------
Ceelos09 said:
We're still lacking driver source (i.e. our Atheros wifi driver) so even if we got someone to port CM9 to our tabs, we'd have no wifi functionality. The only way to get drivers (with no proper source code released for them) is to reverse engineer the driver(s) themselves, which is a difficult task to say the least.
The reason why most of us say we're waiting for our tabs "ICS Source" is because we're hoping Samsung actually releases our wifi Driver Source code this time.
But...if I remember correctly...someone had pointed out that although Samsung had not released proper source code for our wifi driver, another Sony device that uses it had released code that we could "possibly" use. No one has really confirmed nor denied anything past that recently. Maybe Gary can comment on this issue soon, could clear up a lot of questions for me and everyone else
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
My guess is that if Samsung has not released the needed sources previously, they probably won't do so with ICS. This is just pure speculation on my part, it's possible Samsung's failure to release wifi driver source was an oversight on Samsung's part but if that were the case, it seems like they would have fixed that already.
I don't know what chip the GT7P uses but some Googling suggests that it's an Atheros 6000 series. If that's the case, the Linux driver source is available: http://linuxwireless.org/en/users/Drivers/ar6k
ar6k isn't part of the mainline Linux kernel so there's no obligation on Samsung's part to release it as part of their kernel source release. Whether Samsung is obligated to release their ar6k driver source is probably dependent on their agreement with Atheros (ie, just because an open source Linux ar6k exists doesn't preclude the possibility that Samsung licensed a non-GPL version of the driver).
h2g2 said:
Right now, the only thing that's really holding back CM9 development on the tab7plus is a lack of tab7plus owners contributing to a CM9 port.
Click to expand...
Click to collapse
What is the best way for us Tab 7.0+ owners to contribute?
h2g2 said:
Kernel source doesn't mean driver sources. Remember that drivers don't need to be integrated into the kernel - if Samsung (or the manufacturer of the device) chooses to implement the driver as a binary-only lkm, there's no obligation on Samsung's part to release the source code for the driver.
This has been a problem with Linux drivers in general for a while. I could be wrong, but my sense is that if the needed driver isn't already available in source code from the manufacturer directly, it's unlikely that Samsung will include it in their kernel sources.
---------- Post added at 10:35 PM ---------- Previous post was at 10:20 PM ----------
My guess is that if Samsung has not released the needed sources previously, they probably won't do so with ICS. This is just pure speculation on my part, it's possible Samsung's failure to release wifi driver source was an oversight on Samsung's part but if that were the case, it seems like they would have fixed that already.
I don't know what chip the GT7P uses but some Googling suggests that it's an Atheros 6000 series. If that's the case, the Linux driver source is available: http://linuxwireless.org/en/users/Drivers/ar6k
ar6k isn't part of the mainline Linux kernel so there's no obligation on Samsung's part to release it as part of their kernel source release. Whether Samsung is obligated to release their ar6k driver source is probably dependent on their agreement with Atheros (ie, just because an open source Linux ar6k exists doesn't preclude the possibility that Samsung licensed a non-GPL version of the driver).
Click to expand...
Click to collapse
thanks for the clarification.
bittersound said:
What is the best way for us Tab 7.0+ owners to contribute?
Click to expand...
Click to collapse
In a general sense, there is no answer as it depends on what the problem is. If there are willing developers who don't have access to hardware, you can always donate hardware or chip in to help with that. If there aren't enough willing developers, well, you just have to learn to code or chip in for a bounty to get a developer interested. If, on the other hand, it's a lack of vital documentation or source code from Samsung, well, there's not much you can do except perhaps get some sort of letter writing or phone call campaign over to the appropriate corporate offices.
In a specific sense, best bet is to go over to the development sub-forum, find someone with a project you'd like to support and ask them what help they need.
Gary once mentioned he would help with porting CM9, but he did make it clear to us that it would be a while until he would jump in to help. Life must be keeping him busy atm.
For now, I'm working on learning some code, maybe I'll be of "some" help down the road.
Sent from my SPH-D700 using xda premium

Categories

Resources