Database Users

how soon till you think 2.3 is leaked

we all know its going to happen but how soon till we see the leaks

Leaks? It's already officially out. Nexus One's are receiving the update as we speak. As for an EVO specific leak from HTC/Sprint, who knows..I'm sure the devs will have something out soon if there aren't any major hardware changes / requirements.

SDK is out NOT a working rom its no "leaked" pushed yet to the nexus 1

This update sucks for me if it doesn't fix the CPU problem of almost maxing out when scrolling which causes scrolling to be laggy. If they don't fix this by the time my next upgrade comes up I'm switching to a Windows phone. I want a smooth interface.

CheesyNutz said:
SDK is out NOT a working rom its no "leaked" pushed yet to the nexus 1
Click to expand...
Click to collapse
I guess I'm not following.
According to Engadget, Gingerbread, 2.3, is running on Nexus One's. They've received the OTA update.
Although, they may have been wrong and pulled the article and didn't say anything, since
http://www.engadget.com/2010/12/06/android-2-3-update-now-rolling-out-to-nexus-one-owners/
no longer appears to be a valid link, but it was just a half hour ago.
I think this is what it said:
Nexus One owners feeling a little Nexus S envy can breathe a little easier -- we're hearing that Android 2,3 Gingerbread is being pushed out to the N1 as we speak. We'd imagine that all the slick new features that don't require new hardware (like NFC support) will be there, and we're definitely interested in playing with this built-in WiFi calling stack.
Click to expand...
Click to collapse

the latest ota pushed to the nexus was just a minor update i don't think it was 2.3

Sirchuk said:
I guess I'm not following.
According to Engadget, Gingerbread, 2.3, is running on Nexus One's. They've received the OTA update.
Although, they may have been wrong and pulled the article and didn't say anything, since
http://www.engadget.com/2010/12/06/android-2-3-update-now-rolling-out-to-nexus-one-owners/
no longer appears to be a valid link, but it was just a half hour ago.
I think this is what it said:
Click to expand...
Click to collapse
That might have been an old link where the nexus one got a security update and people jumped the gun on calling gingerbread

Looks like Engadget was wrong and pulled the story. Nobody can confirm that 2.3 is out it seems, though some have tried to get their N1's to update.
Way to go Engadget, wrong information with no clarification. At least post a "Oops, we were wrong" update or something.
The N1 forums are saying it will be out on/around the 16th.
Edit:
Think they heard me:
Update: Looks like our flood of tips came from people who were seeing their N1s get a different, less-interesting update -- we'll let you know when the actual 2.3 update roll out. Ah, the heady optimism of hope.
Click to expand...
Click to collapse

One of the main guys on the Android team tweeted that no ota was released for the nexus one and that the source would be released in the "coming weeks". My bet is that the first rom with working Gingerbread on it will be Cyanogen and within a few weeks of the source being released.

donatom3 said:
One of the main guys on the Android team tweeted that no ota was released for the nexus one and that the source would be released in the "coming weeks". My bet is that the first rom with working Gingerbread on it will be Cyanogen and within a few weeks of the source being released.
Click to expand...
Click to collapse
Yup, for our EVOs CM is the best bet and that will be AFTER the source (not to be confused with the Nexus One OTA) is released.

Award Tour said:
Yup, for our EVOs CM is the best bet and that will be AFTER the source (not to be confused with the Nexus One OTA) is released.
Click to expand...
Click to collapse
Any sense rom will have to wait till a 2.3 gingerbread source is released by HTC which could be a while, if ever. Cyanogen is already on 2.35.9 kernel which hopefully means that porting their work to 2.3 shouldn't be that hard to do.

drmacinyasha said:
I'm going to say this once to head off the countless sheep who will ask...
Do not ask when Gingerbread will make it to the EVO.
Seriously, how the hell would any of us know? We're not psychics, we're not secret HTC/Sprint/Google/CIA/Mafia/Former KGB/NSA employees, we can't predict the future, so why on God's green Earth would you ask us?
Shut up, sit down, twiddle your thumbs, and wait for a press release from Sprint, HTC, Google, etc. announcing that Gingerbread will or will not be ported to the EVO. If you really want Gingerbread, go help Team Douche port it to be CyanogenMod 7. That's the most guaranteed way to get it to our phones.
Click to expand...
Click to collapse
10 characters.

donatom3 said:
Any sense rom will have to wait till a 2.3 gingerbread source is released by HTC which could be a while, if ever. Cyanogen is already on 2.35.9 kernel which hopefully means that porting their work to 2.3 shouldn't be that hard to do.
Click to expand...
Click to collapse
Not sure if there's any confusion with what I think I read from your post but.. I'm talking about the AOSP source not the HTC source. That'll probably take a month or so after the Nexus One OTA to be released and then another month or so before CM releases a RC of CM7/2.3.

apollooff320 said:
This update sucks for me if it doesn't fix the CPU problem of almost maxing out when scrolling which causes scrolling to be laggy. If they don't fix this by the time my next upgrade comes up I'm switching to a Windows phone. I want a smooth interface.
Click to expand...
Click to collapse
windows phone? are you on crack?

I'm guessing you won't see a Sprint/HTC Gingerbread ROM until sometime next year. Rumor has the source code being released when the Nexus S ships which is allegedly on Dec 16. Expect AOSP based Gingerbread ROMs to start rolling out around then and an Official Sprint ROM after sometime well after that, after its been thoroughly QA'd.

Gingerbread source being pushed today!

http://groups.google.com/group/android-building/browse_thread/thread/091172a81604c8a0?pli=1
Nexus S went on sale yesterday morning in the US, running Gingerbread.
Just like I did for Froyo, I'm open-sourcing the matching Android
platform source code, right after the first consumers get their hands
on it. I'm going to start literally right now, and the process will
take a few hours.
I'll give more details once the source code is available. However,
there are three aspects that you need to know ahead of time:
-As part of the process to push the source code, there will be some
points in time when the master branch doesn't build. Sorry about that.
If you're working on the master branch, I recommend that you don't
sync until I send an "all clear" when I'm done and things look good.
Other branches are expected to work fine as soon as their manifests
are created.
-Even though Nexus S is designed to be suitable for AOSP work, there
are some caveats. I very strongly recommend against trying to use
Nexus S for anything related to AOSP at the moment. Trying to unlock
or use your Nexus S for AOSP work could easily turn it into a Nexus B
(where B means "brick"); I have two of those, they're not very useful.
I'll send some guidelines about what is currently possible once I've
finished pushing the source code.
-Please take it easy on the kernel.org servers. They are very helpful
in hosting the AOSP source code, and I don't want to hurt the high
quality of their service with an onslaught of full Android downloads.
If you're not going to immediately work on porting Gingerbread to
devices with the intent of distributing the result to end-users, I'm
kindly asking that you wait a few hours or a few days before you
download it (just roll a 6-sided die and wait that long). In addition,
the slower the servers are, the harder it is for me to do the push.
Thanks for being patient.
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Click to expand...
Click to collapse
Yay!
Let's bombard Cyanogen's Twitter! J/K``

Hope something good for my incredible comes out of this
Sent from my ADR6300 using XDA App

Can't wait! The quicker the source is released the faster we will have Gingerbread baked into our roms

First one to get an AOSP build of 2.3 running on the G2 will be my new hero.

lol @ the software engineer having two Nexus B's already ;D

silverton said:
lol @ the software engineer having two Nexus B's already ;D
Click to expand...
Click to collapse
Hey! It happens to best of us... I've bricked a couple myself and I was a cell tech for 5 years, worked my way up department mgr., been a pc tech/network engineer for 10 years and have A+, NET+, C++, and bachelors in computer science. Also, I bricked my wife's like 6 months ago, lol! It happenes to even the most technical person...

Wowo!!!!! Can't wait! I've been on the virtous for some time now, because I really like the sense shell, but it's strait over to CM again (been there many times allready) when 2.3 comes!!!

Yeah, I've been waiting to permaroot for CM7. I was going to permaroot for CM6.1.1 this weekend, then this news broke, so I think I'll wait for 7. Or maybe I'll go ahead with 6.1.1.
Who knows!

@cyanogen
Prepare for spam!!

I just looked at aosp and I see next to nothing updated yet so I dunno

@cyanogen WILL come through quickly for the G2. I'm sure of it.

Shady Gambino said:
Yeah, I've been waiting to permaroot for CM7. I was going to permaroot for CM6.1.1 this weekend, then this news broke, so I think I'll wait for 7. Or maybe I'll go ahead with 6.1.1.
Who knows!
Click to expand...
Click to collapse
Why wouldn't you permroot now? Nearly double CPU clock, the ability to disable throttling, superuser access.
In my experience, the first implementation of new code is often quite buggy. While I can't wait for 7.0, I suspect I may end up waiting for 7.1 or 7.0.1 before I update.

tornado9015 said:
While I can't wait for 7.0, I suspect I may end up waiting for 7.1 or 7.0.1 before I update.
Click to expand...
Click to collapse
That's half the fun

Follow cmrsc on twitter for updates on compiling a blue-berry flavored gingerbread.
Sent from my HTC Vision using XDA App

sino8r said:
Hey! It happens to best of us... I've bricked a couple myself and I was a cell tech for 5 years, worked my way up department mgr., been a pc tech/network engineer for 10 years and have A+, NET+, C++, and bachelors in computer science. Also, I bricked my wife's like 6 months ago, lol! It happenes to even the most technical person...
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
I want to be just like you when I grow up

silverton said:
lol @ the software engineer having two Nexus B's already ;D
Click to expand...
Click to collapse
I was a bit skeptical about that - seeing as he's kinda high on the totem pole @ Google/Android Devs... you would think they'd have more than a few ways to debrick a device that touts their name on it. Sure the hw is made by Samsung, but I doubt the devs were submitting all revisions and rcs of GB to Samsung like - "Hey guys, could you flash this for us, I don't think we have the tools or knowledge".

Come on msm7x30 support!

Blades said:
I was a bit skeptical about that - seeing as he's kinda high on the totem pole @ Google/Android Devs... you would think they'd have more than a few ways to debrick a device that touts their name on it. Sure the hw is made by Samsung, but I doubt the devs were submitting all revisions and rcs of GB to Samsung like - "Hey guys, could you flash this for us, I don't think we have the tools or knowledge".
Click to expand...
Click to collapse
He probably has a stack of cell phones and probably tries to brick some of them on purpose. He probably just gives back the bricks to Samsung.

ctraywick1 said:
Sent from my HTC Vision using XDA App
I want to be just like you when I grow up
Click to expand...
Click to collapse
Thanks, I guess... hard to detect sarcasm in writing My point was... bricks happen!
Just flashing the proper way, epecially packed ones with a bootloader, you can brick even when you do everything correctly. I've flashed over 500 phones (may be more) and it will happen. The nice thing is though, when you are a cell tech, just pop out the board and get another one. Manufacter's warranties for carriers are surprisingly lax... so, yeah we did brick some on purpose, lol

Cyanogen via twitter:
My G2 seems to have Gingerbeard on it. How did that happen?
Click to expand...
Click to collapse

HTC Evo Kernel Source to be released soon

I have been contacting HTC and different departments and contacts to find out when all the backlog source data will be released...
This is specific to:
3.29.651.5 updated kernel to 2.6.32.15-ge2fb08e [email protected]
3.30.651.2 updated kernel to 2.6.32-15-g0f673ed kernel #10
3.70.651.1 updated kernel to 2.6.32-17-gee557fd kernel #15
I finally got the final confirmation e-mail back from my contact.
All information about the contact has been removed due to confidentiality statements at the bottom of the e-mail.
So keep your eyes peeled on the HTC source site for these releases. If i get anymore info i will let you know
We are in the final Stages of releasing the data, as soon as we know an exact date we will let you know.
******
Technical Support Specialist
T +1 xxx.xxx.xxxx
13920 SE Eastgate Way Suite 400
Bellevue, WA 98005

Yea sounds like its coming sometime in 2011....not holding my breath

Have you really been bugging these people for this?
Sent from my PC36100 using XDA App

I was asked to by some Evo Developers who want the source code updates to look at. I have experience with getting manufacturers (specifically Samsung in the past) to actually commit and release the opensource code protected by the GNU GPL v2.

DirtyShroomz said:
Have you really been bugging these people for this?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
most developers are curious how HTC removed the 30 fps cap (took methods developers here created or some alternative way).
also, having the real drivers from HTC for the new hardware 4 phones, basically diff hardware camera is used and i dont think anybody has released a working custom kernel with the correct drivers for the hw 4 camera. it would be nice to see the source code to know for sure whether or not any other hardware changed in ver 4.
among other things, its always great to have the latest source code for the kernel they release as it allows us to keep creating custom kernels either based on HTC's latest drivers or at least be able to use their source code as reference.
hope that helps satisfy your curiosity as to why we are very very happy to finally hear a response from HTC, who hasnt released any of their linux modified kernel source code which falls under the GPL v2 license, for the last few months.

Glad to see you're on it numus I've been wondering what's taking them so long and why more people haven't been complaining about it.

^ 5 bru!!!!!

numus said:
I have been contacting HTC and different departments and contacts to find out when all the backlog source data will be released...
This is specific to:
3.29.651.5 updated kernel to 2.6.32.15-ge2fb08e [email protected]
3.30.651.2 updated kernel to 2.6.32-15-g0f673ed kernel #10
3.70.651.1 updated kernel to 2.6.32-17-gee557fd kernel #15
I finally got the final confirmation e-mail back from my contact.
All information about the contact has been removed due to confidentiality statements at the bottom of the e-mail.
So keep your eyes peeled on the HTC source site for these releases. If i get anymore info i will let you know
We are in the final Stages of releasing the data, as soon as we know an exact date we will let you know.
******
Technical Support Specialist
T +1 xxx.xxx.xxxx
13920 SE Eastgate Way Suite 400
Bellevue, WA 98005
Click to expand...
Click to collapse
They are Tech Support....they will tell you what you want to hear. Don't hold your breath on this one.

twin001 said:
They are Tech Support....they will tell you what you want to hear. Don't hold your breath on this one.
Click to expand...
Click to collapse
I actually talked to some developers at HTC... they wont directly email anything to me tho so they are using this guy as the relay.

Good job. This its essential.
Sent from my PC36100 using XDA App

"Soon" in HTC or Valve Time usually translates to "three to eighteen months."

Looks like it's finally out!
http://developer.htc.com/
HTC EVO 4G (Sprint) – Froyo MR2.5 – 2.6.32 release
HTC EVO 4G (Sprint) – Froyo MR2.51 – 2.6.32 release
HTC EVO 4G (Sprint) – Froyo MR3 – 2.6.32 release

Yea yea.....yea for beer.
Sent from my PC36100 using XDA App

Wonder how long before rom devs start incorporating this into their kernels and roms

Samsung conforms to source 100% better than HTC now. But HTC actually updates their software

I hope soon. I need some custom kernels on my evo. I got that new cam in mine.
Sent from my PC36100 using XDA App

WHo you telling. I'm living without my camera now because I NEED the better battery life.

This is awesome! Been waiting to oc to see what this thing can do.
Sent from my PC36100 using XDA App

I am amazed 50 threads have not been posted.
Sent from my iPhone with the bigger Gee Bees.

Been on a security detail the past few days.. Glad to see they finally released!

What the LTE EVO means for the OG EVO (development wise)

So once the LTE Evo/One S/OneX makes it into the hands of developers, Will devs be able to glean anything from the new HTC handsets that will help in the development of ICS for our OG EVO?

cobmojo said:
So once the LTE Evo/One S/OneX makes it into the hands of developers, Will devs be able to glean anything from the new HTC handsets that will help in the development of ICS for our OG EVO?
Click to expand...
Click to collapse
Its the kernel thats really stopping it we have a aosp but sense needs to release the source code for the kernel for dev to get to working. its where the good stuff drivers are in. Its easy to port will need the kernel so......

And HTC is obligated to release kernel info within 30 days. If I remember correctly.
sent from my ICS machinevo

Going by Ca1ne's post HTC will release 90-120 days after it's been out.
http://forum.xda-developers.com/showpost.php?p=24614403&postcount=168
Naters

NaterTots said:
Going by Ca1ne's post HTC will release 90-120 days after it's been out.
http://forum.xda-developers.com/showpost.php?p=24614403&postcount=168
Naters
Click to expand...
Click to collapse
I believe that's only relating to an OTA update. It would only make sense that a newly released device would have a shorter time frame.

LEAKED GPE KERNEL | Push for kernel source (All models)

Hey everyone. So, kernel source isn't out yet. That is a bit disturbing to me... So because of the sheer popularity of this device, everyone submit a request for all models of the m8 Kernel source. A forum letter would be as follows
Hello, my name is _____. I own the HTC one M8. As required by copyright law, htc is required to release the Linux kernel source code the day of release. The lack of kernel source is therefore breaking copyright laws, and I hereby request all Linux kernel sources be released for all released models of the HTC One M8. Many people desire this kernel source. These are all your paying customers too.
thank you, (name)
Now another thing to know is they will likely tell you "htc releases all legally required sources" do not take this answer. Require that your case be elevated, and help us get the development going properly.
Link:
http://www.htcdev.com/contact
EDIT:
GPE leaked sources:
http://www.androidfilehost.com/?fid=23329332407583185

Done. Just FYI, the GPL requires you release the code in a reasonably timely manner, not the day of release.

123421342 said:
Done. Just FYI, the GPL requires you release the code in a reasonably timely manner, not the day of release.
Click to expand...
Click to collapse
Actually the exact wording is released along side of the release of a kernel. I have talked with many Linux kernel maintainers who all agree this is equal to the same day. (Linux Kernels are my specialty, as such I've met great people along the way who worked very close with Linus)
Sent from my C525c using Tapatalk

123421342 said:
Done. Just FYI, the GPL requires you release the code in a reasonably timely manner, not the day of release.
Click to expand...
Click to collapse
Not only that it's not release day yet, official release is somewhere in April no?

xReaper7x said:
Not only that it's not release day yet, official release is somewhere in April no?
Click to expand...
Click to collapse
Release date was Tuesday. For sprint, AT&T, Verizon, gsm unlocked and the developer edition. Google play is 2 weeks from last Tuesday. Other carriers come on at different times.
Sent from my C525c using Tapatalk

This par for the course with HTC. They have never been good about releasing kernel source in a timely fashion.

According to the GPL, kernel source must be available as soon as the accompanying software is in use by the public. The "in a timely manner" aspect provides some flexibility in delivering the source, as far as distribution. Within 24 hours is acceptable, time to upload the file and make it available on the site. It needs to be available day 1. 90-120 days later is not even close to complying.
What's even more annoying than having to wait, is that there is absolutely no reason to hold it back. They obviously have it before the device is released. All they do is annoy their LOYAL customers. It's just stupid and bad business at this point.
Sent from my HTC One using xda app-developers app

Surely it's not copyright law, but the licence under which the Linux source is released, i.e., GPL v2.

BenPope said:
Surely it's not copyright law, but the licence under which the Linux source is released, i.e., GPL v2.
Click to expand...
Click to collapse
The GPL license is a form of a copyright. This makes it part of copyright laws
Sent from my C525c using Tapatalk

thats the only thing stopping me from going back to HTC.. they are horrible at releasing kernel source.. sad cause i have seem many users and kernel devs leave HTC because of this issue..

it will come in time. we don't even have s-off yet.

Pretty sure they have 90 days to comply
~Jflteusc runnin' latest Carbon Nightly
Latest KToonsez Kernel 2.1;189;480
Pegasusq
Row
Thermald:
Mpdecision:

You don't need soff to unlock. Just a unprotected unlock partition or one that's exploitable
Also they do not. If you don't agree ask any Linux mantainter. Most even see it offensively that oems do this
Sent from my HTC M8WHL

Done.
Sent from my 831C using XDA Premium 4 mobile app

The phone hasn't even been out a week... Kernel source for the M7 has been released releatively quickly after updates.
The phone has been out for 5 days...
Sent from my HTC One using Tapatalk

That doesnt matter. Kernel source should be released within 24 hours of it being public.

HTC always releases source immediately for the Google Play Edition, which means a couple weeks. They always take forever to release source for their Sense kernels.

flar2 said:
HTC always releases source immediately for the Google Play Edition, which means a couple weeks. They always take forever to release source for their Sense kernels.
Click to expand...
Click to collapse
Google told them that they had to do that if they wanted to call it a Google play device. It may be something we can work with. Let's hope that HTC senses, no pun intended, the desire.
Sent from my HTC M8WHL

MassStash said:
Pretty sure they have 90 days to comply
Click to expand...
Click to collapse
Pretty sure that is stated NOWHERE in the GPL.
Sent from my HTC One using xda app-developers app

c5satellite2 said:
Pretty sure that is stated NOWHERE in the GPL.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Oh for sure, definitely not in the stated license, not sure where the hell I heard that. Then n that note, 1) really pain in ? there isn't a time frame stated in the license to high source needs to be made available for person requesting, and 2) pretty sure these companies could charge us for distrbuting source to us, so that's kool they don't at least.
~S-Off LTEvo; Back on the Always Solid Viper4G Latest;
Expletive Deleted Kernel
cpu0/1: 1.5ghz ¦ 384mhz ¦ sleep: 486mhz max
ondemand
fiops
thermald: dynamic
With tapatalk4