Related
Hi developers,
I was tired of staring at the HTC Developers page to find out, if there is a new version of the Bravo-Source available.
So I made this a bit "friendly"
http://home.bestblog.de/source-check/index.php
Maybe useful, maybe not
Niceeeee We need a HAVS OC kernel
My compiling-machine is just waiting for the HTC sources
Nice. How long did it take for htc to release the source for eclair ? Quite a bit if I'm not mistaken ? Just to make an estimate...
andycted said:
Nice. How long did it take for htc to release the source for eclair ? Quite a bit if I'm not mistaken ? Just to make an estimate...
Click to expand...
Click to collapse
As the sources of FROYO for the EVO4G are already out, I can't believe it should take too long
If I don't totally fail, I even know, what the name and URL of the source will be. For the names-convention on HTC Dev-Page it should be one of these:
http://member.america.htc.com/download/RomCode/Source_and_Binaries/bravo-2.6.32.15-gf9c0527.tar.gz
http://member.america.htc.com/download/RomCode/Source_and_Binaries/bravo_gf9c0527.tar.gz
But I make the check for a new version another (more reliable) way
I really don't understand why the Desire is ALWAYS the last of the batch to get the sources released...raaaaage.
<Monty Burns>Excellent...</Monty Burns>
Can't wait to have some tweaks.
If I recall correctly, it took way longer for the eclair source to be relased, to the point that people were afraid they wouldn't ever do it.
i know most of the devs said in order to have custom kernels for the new sense leak we have to wait for the official release or source to drop. i guess my question is, why not take the current shipped kernel and tweak it a bit and add sbc mod to it for the time being?
is this even possible and if so is anyone like toast/netarch working on this?
at this point i think it was said that the current kernel was very incomplete so devs are waiting for htc to drop the KERNAL source code
fixxxer2008 said:
i know most of the devs said in order to have custom kernels for the new sense leak we have to wait for the official release or source to drop. i guess my question is, why not take the current shipped kernel and tweak it a bit and add sbc mod to it for the time being?
is this even possible and if so is anyone like toast/netarch working on this?
Click to expand...
Click to collapse
Mainly, the 2.2 kernel is based on 2.6.32, while the 2.3 kernel included with the last leak was based on 2.6.35. Two different trees totally. With no source for the newer kernel yet, it's almost impossible to do anything... at least easily.
It's easier to just wait for HTC to drop their source for the .35 kernel they are going to use, then the devs can go to town on it fixing what's broken as usual.
I'm not a kernel expert, so there may be things I left out or assumed.
3 months later and still no source code
jbrawley1 said:
3 months later and still no source code
Click to expand...
Click to collapse
3 months? Its only been a little over a month since the official 2.3 update
We're comin from a pure power source.
HTC has released the source code in a month or less in the past for the Evo.
Unfortunately, I don't expect that to happen this time because several of the bugs with the current 2.3.3 release seem kernel related to me. So my guess is we won't see source until after they release the next update. I just can't see them releasing source for something that is so screwed up, but that is pure speculation on my part.
Yeah, if there is already so much talk of another update, then that would make sense. Plus, according to HTC they have 90-120 days to release the source code.
I thought it was 30 days. I know toast wants kernel source for evo 4g and evo shift. Hopefully HTC realizes its been over a month. I don't think it matters if 2.3.3 has bugs, since it was officially released I think they are required to post kerenel source of what they used for 2.3.3
Maybe we should give a reminder to @HTC on twitter
Sent from my PC36100 using XDA Premium App
deviouskater said:
I don't think it matters if 2.3.3 has bugs, since it was officially released I think they are required to post kerenel source of what they used for 2.3.3
Click to expand...
Click to collapse
I don't think their is any requirement for them to release source until they get it working. For example, I can almost guarantee we will never see source for the 4.22.651.2 update, and as I said before, it wouldn't surprise me if we got another update and never see source for the current 4.24.651.1 update either. I can think of several good reasons why they wouldn't release source with known problems.
Every time I back out of an app and have to wait for sense to reload, or whenever I try to switch to an app that was supposed to be running in the background and it has to reload and start over, it is obvious that this kernel has serious issues. I would bet HTC is working on it now to figure out what those issues are.
So... i know that there aren't any devs working on modifying the kernels from the 2.3 Sense Leak, but this is something I dont really understand.
Netarchy and crew (among many others) had kernels pushed out for the EVO WAAAAYYY before they released any source info. and even when we moved to 2.2, there were kernels ready soon after.
Obviously, the brightness fix is in a ton of working 2.2 kernels. Why cant we pull that out and put it in another kernel? Maybe add SBC and/or some battery tweaks?
I know that devs dont want to have to start over if there is a major difference in the Kernels from beta to release, but what would be the major change? Wouldnt the 2.3 be a good place to start messing around, and then make small adjustments when the full kernel is released? You could easily get a leg up on other devs and incorporate it into the TONS of 2.3 Roms that are out there now.
Im ignorant as hell when it comes to kernels and compiling, but speaking on a tiny modicum of common sense, there should be a way to prod and poke this kernel into submission.
ignore me if in being dumb. I just felt like i had to ask this.
EDIT:
Id like to keep this a conversation between people who want this and people who know. Please dont add your 2cnts in to say the same things we have all heard (we need source, cant do it, no reverse engineering, blah blah)
If you are a dev and can give some REAL PROPER insight, we would love to hear it. even if its to tell us to stuff it LOL.
rawdikrik said:
So... i know that there aren't any devs working on modifying the kernels from the 2.3 Sense Leak, but this is something I dont really understand.
Netarchy and crew (among many others) had kernels pushed out for the EVO WAAAAYYY before they released any source info. and even when we moved to 2.2, there were kernels ready soon after.
Obviously, the brightness fix is in a ton of working 2.2 kernels. Why cant we pull that out and put it in another kernel? Maybe add SBC and/or some battery tweaks?
I know that devs dont want to have to start over if there is a major difference in the Kernels from beta to release, but what would be the major change? Wouldnt the 2.3 be a good place to start messing around, and then make small adjustments when the full kernel is released? You could easily get a leg up on other devs and incorporate it into the TONS of 2.3 Roms that are out there now.
Im ignorant as hell when it comes to kernels and compiling, but speaking on a tiny modicum of common sense, there should be a way to prod and poke this kernel into submission.
ignore me if in being dumb. I just felt like i had to ask this.
Click to expand...
Click to collapse
Unfortunately, there is nothing that can be done until HTC releases source code for the kernel, or until HTC releases a new, working kernel. The kernel that is out now, that causes the brightness issue, is basically an incomplete kernel, from a leaked rom. Something that is fully working, and more stable is needed.
k2buckley said:
Unfortunately, there is nothing that can be done until HTC releases source code for the kernel, or until HTC releases a new, working kernel. The kernel that is out now, that causes the brightness issue, is basically an incomplete kernel, from a leaked rom. Something that is fully working, and more stable is needed.
Click to expand...
Click to collapse
I appreciate you saying that... but it doesnt explain why we had kernels for 2.1 and 2.2 before any source was released. I would like to hear from the devs directly.
Thanks for chiming in though.
From the little and probably wrong information I'm making up, you can't decompile kernels from a Rom, you need source to download from, then apply your mods and then can compile a fixed kernel
Edit: complete speculation, if it is in fact true i will modify post to reflect my all knowing powers
NewZJ said:
From the little and probably wrong information I'm making up, you can't decompile kernels from a Rom, you need source to download from, then apply your mods and then can compile a fixed kernel
Click to expand...
Click to collapse
Thank you... but this is what I am trying to avoid. Id like to remove the misinformation and get a real set of reasons and information. We can all speculate. I want a real answer... and im sure im not the only one.
rawdikrik said:
Thank you... but this is what I am trying to avoid. Id like to remove the misinformation and get a real set of reasons and information. We can all speculate. I want a real answer... and im sure im not the only one.
Click to expand...
Click to collapse
Can't make kernels unless they are 1.) reverse-engineered 2.) or HTC releases the source code for a specific device.
Too time consuming. And by the time, it goes through a psuedo-SDLC, HTC would have probably already released the newest one and devs here already working on a custom kernel.
Hope that answers your question
I believe net said he would work on one as soon as the source is released....I think I read it in his thread
Sent from my PC36100 using XDA App
pinky059 said:
Can't make kernels unless they are 1.) reverse-engineered 2.) or HTC releases the source code for a specific device.
Too time consuming. And by the time, it goes through a psuedo-SDLC, HTC would have probably already released the newest one and devs here already working on a custom kernel.
Hope that answers your question
Click to expand...
Click to collapse
So in other words the reasons that they arent bothering is because they dont want to invest the time when it could become obsolete before it is even released?
mutant13 said:
I believe net said he would work on one as soon as the source is released....I think I read it in his thread
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I dont see that happening any time soon.
Not only that, but i think i remember NET working on one before any source came out for 2.2 and 2.1, especially to fix the FPS cap.
I think that he didnt want to touch it because it is beta and can change between now and an official 2.3 release, like most devs have stated.
rawdikrik said:
I appreciate you saying that... but it doesnt explain why we had kernels for 2.1 and 2.2 before any source was released. I would like to hear from the devs directly.
Thanks for chiming in though.
Click to expand...
Click to collapse
Not a problem. I don't have an answer for you about kernels being released for 2.1 and 2.2 before source was released, other than that you're most likely mistaken about that. Based on what I've been told by devs, and what I've seen devs say (netarchy said he'd work on this kernel as soon as source was released, and that there was nothing that could be done prior to source being released....he said it in his kernel thread), it is nearly impossible to mod/tweak a kernel without the source code. Without source code, it would need to be reverse engineered. By the time that was to happen, a new kernel would already be released most likely.
That's all I got on that issue. So basically, no custom kernels without kernel source.
k2buckley said:
Not a problem. I don't have an answer for you about kernels being released for 2.1 and 2.2 before source was released, other than that you're most likely mistaken about that. Based on what I've been told by devs, and what I've seen devs say (netarchy said he'd work on this kernel as soon as source was released, and that there was nothing that could be done prior to source being released....he said it in his kernel thread), it is nearly impossible to mod/tweak a kernel without the source code. Without source code, it would need to be reverse engineered. By the time that was to happen, a new kernel would already be released most likely.
That's all I got on that issue. So basically, no custom kernels without kernel source.
Click to expand...
Click to collapse
I may very well be COMPLETELY WRONG. LOL. Im not against that. I am right now doing my homework to confirm what ive been thinking.
EDIT: After doing some homework, it looks like Net and Toast were making changes to the stock 2.1 kernel before any source was released. This i remember because the 2.2 Kernels that they first made broke the camera, which wasnt fixed until the source was released. I remember waiting with my hand over f5 til HTC released the source.
They we working hard on using Kernels from other devices and tryign to get the FPS cap removed along with getting the HDMI working.
All i did was go over this ANCIENT thread
http://forum.xda-developers.com/showthread.php?t=719763&highlight=source
rawdikrik said:
I may very well be COMPLETELY WRONG. LOL. Im not against that. I am right now doing my homework to confirm what ive been thinking.
EDIT: After doing some homework, it looks like Net and Toast were making changes to the stock 2.1 kernel before any source was released. This i remember because the 2.2 Kernels that they first made broke the camera, which wasnt fixed until the source was released. I remember waiting with my hand over f5 til HTC released the source.
They we working hard on using Kernels from other devices and tryign to get the FPS cap removed along with getting the HDMI working.
All i did was go over this ANCIENT thread
http://forum.xda-developers.com/showthread.php?t=719763&highlight=source
Click to expand...
Click to collapse
Well, maybe there are certain things that can be worked on without source, but I believe for this type of problem (brightness issue), source is needed. Probably similar to how you said that the 2.2 kerneles broke the camera at first, and couldn't be fixed until source was released. This is the same type of deal. Hopefully Sprint will release an OTA within 30-60 days. I wouldn't get my hopes up for anything before that, unfortunately.
k2buckley said:
Well, maybe there are certain things that can be worked on without source, but I believe for this type of problem (brightness issue), source is needed. Probably similar to how you said that the 2.2 kerneles broke the camera at first, and couldn't be fixed until source was released. This is the same type of deal. Hopefully Sprint will release an OTA within 30-60 days. I wouldn't get my hopes up for anything before that, unfortunately.
Click to expand...
Click to collapse
The word around the grapevine is that sprint isn't releasing the OTA until after the release of the evo 3d (marketing scheme, you know how it is).
AbsolutZeroGI said:
The word around the grapevine is that sprint isn't releasing the OTA until after the release of the evo 3d (marketing scheme, you know how it is).
Click to expand...
Click to collapse
I heard that too. That wont be til June/July and then they have another 60days of waiting time they usually take to release source.
and that is IF They do the upgrade, since usually they only want a single upgrade in the life cycle of a product. They will most likely REALLY think about it, to not risk stealing sales from the newer phones coming out over the summer.
AbsolutZeroGI said:
The word around the grapevine is that sprint isn't releasing the OTA until after the release of the evo 3d (marketing scheme, you know how it is).
Click to expand...
Click to collapse
Correct. I predict the 3D to drop within 30-60 days from now though. Then shortly after that, the OTA will probably roll out. As rawdikrik said, source will probably come a month or two after the OTA. The good thing though, is that if/when an OTA is released, it will have a working kernel in it. So even without source being released, a working kernel will be in circulation at that point, which will most likely resolve the brightness issue.
Evo 3D is supposedly hitting June so I'm going to say July just to give it some breathing room. If OTA hits around August maybe September, then its another 30-45 days to release source. So were talking around September-October ish for complete source. This is all speculation but sprint/HTC operate that way. My guess is september for a fully working kernel for GB based on the source code. Stupid marketing scheme to get us to buy the evo 3D.
Sent from my PC36100 using XDA Premium App
I'm so going to buy the EVO 3d
not sure how i feel about the 3d gimmick...
Can we keep this on topic though? THanks guys... Im just waiting to hear something from the big dogs.
Keep in mind it's entirely possible that we will see another leaked kernal long before the OTA is out, this one fully functional. This is especially true if(as many of you seem to suspect) this "leak" was actually no leak at all but an intentional way to let the Chefs and Power Users test their new ROM for them and get feedback on it.
Not sure if you (the Op) have ever tried programming... But (in perspective of the difficulty), basically this would be like me writing a "Hello World" app in Java or C++, and it having an extra space in between the words that bothered you. You would have to cipher through hundreds of lines of code in a hexidecimal editor trying to find the "call" to the display API, and then find which variable or constant it was using for the text output, and change it.
Then you would have to re-compile, and hope it worked without breaking anything else already in place. If you broke something, it's INCREDIBLY hard to debug without real source code.
Hi All,
Below a message from google about releasing ICS Time to DEV !
Greatings
Antonius
https://groups.google.com/group/android-building/msg/c0e01b4619a1455a
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.html
Check 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.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
Yessssssss
now let the games begin!!
Good news! Hopefully the devs can do something magic!
What does this actually mean for us DHD users? is it simply a matter of putting 2 and 2 together, and bam we have a rom? or will it take a few weeks, and be extremely difficult because I notice everyone saying this is only for the Galaxy Nexus, so it is pretty much like porting I guess?
Repsys7 said:
What does this actually mean for us DHD users? is it simply a matter of putting 2 and 2 together, and bam we have a rom? or will it take a few weeks, and be extremely difficult because I notice everyone saying this is only for the Galaxy Nexus, so it is pretty much like porting I guess?
Click to expand...
Click to collapse
It will be very easy
Thanks for letting the devs know
Sent from my Desire HD using XDA App
@Antonius
Really? I hardly believe that.
Having the source code is very important, not everything. Release source code is for Galaxy Nexus, a different device. We need a working kernel and support for our hardware. Real devs are probably working on that now. The real work begins from here, and I hardly believe we will have something functional until CM9 starts having night builds... 1-2 months from now
Maybe we get the first nightly as a christmas gift.
alienmind said:
@Antonius
Really? I hardly believe that.
Having the source code is very important, not everything. Release source code is for Galaxy Nexus, a different device. We need a working kernel and support for our hardware. Real devs are probably working on that now. The real work begins from here, and I hardly believe we will have something functional until CM9 starts having night builds... 1-2 months from now
Click to expand...
Click to collapse
I think you need to read the post again this is the Source code it is a build up for gingerbread as i saw the code this night it was released the drivers and support are gonna be build very easaly but still it can take up to 1 a 2 weeks before release (Altrough i think some devs will release today for other devs to work on it) Also we need to keep in mind that there will be bugs in the system (Its still a child )
Greatings
Antonius
Multiple threads already on this. One is enough for development section. Moving to General
hahaha :-D at last.............waiting 4 it
In the words of many a drunk person at music festivals across the country
"HERE WE, HERE WE F*CKING GO"
Antonius123 said:
I think you need to read the post again this is the Source code it is a build up for gingerbread as i saw the code this night it was released the drivers and support are gonna be build very easaly but still it can take up to 1 a 2 weeks before release (Altrough i think some devs will release today for other devs to work on it) Also we need to keep in mind that there will be bugs in the system (Its still a child )
Greatings
Antonius
Click to expand...
Click to collapse
I think you need to read a bit harder
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
Click to expand...
Click to collapse
This still needs porting, new kernel building, etc. I think a couple of months for alpha/nightly builds for DHD sounds about right.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
I hope as soon as possibile!
You where mistaken my friend: http://forum.xda-developers.com/showthread.php?t=1343361
check this thread!
hopscotchjunkie said:
I think you need to read a bit harder
This still needs porting, new kernel building, etc. I think a couple of months for alpha/nightly builds for DHD sounds about right.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
Click to expand...
Click to collapse
Being a photographer is not conducive to having ICS beta builds without camera... and i'm a flashaholic! What am I to flash?!
what will happen after arco's buy a new phone are any one will continue his work or his project will close !!
I think Arco will continue the development for this phone (even though it could be just an hobby). Or maybe someone can took his github tree and continue the development he left. Even though he will be with us more 2 months so let's wait to see what happens.
Also, I hardly believe that will be another version of android for this phone after android 4.2.2. As arco said in one of the threads present on this forum due to hardware limitations that would be kinda difficult. So, mostly probably what this phone can wait s bug fixes from Arco and anyone who wants to contribute for this phone. In fact, that's what opensource is all about.