Related
Is there a stable Froyo with Sense out there, one based on the Evo's ROM cause I did flash a rom by avalaunch. But it was based on the desire. I didn't like that and it didn't seem as fluid. So my question is... Is there a Froyo with Sense ROM out there thats stable and based on the Evo? and if there is what features are not working (if any) thank you
So far, all the FroYo roms are missing ( at the very least ) the back camera & 4G. However DamageControl & Cyanogen should have working ROM's within the next few days. Cyanogen will be AOSP, but i think DC might be Sense UI.
I initially thought I'd want an AOSP rom but after trying them I much prefer Sense, mainly for the widgets. Lets hope DC has sense! Wouldnt that be a slap in the face to HTC devs who need until December to complete it.. and DC does it with 2 devs in their spare time?
OneStepAhead said:
I initially thought I'd want an AOSP rom but after trying them I much prefer Sense, mainly for the widgets. Lets hope DC has sense! Wouldnt that be a slap in the face to HTC devs who need until December to complete it.. and DC does it with 2 devs in their spare time?
Click to expand...
Click to collapse
Htc devs are in no rush and it's not due to be released in December but BY December meaning any time until then
Is there any time frame for when DC development will come out with froyo with sense ROM. I currently am running DC 3.2.3. If they release it will it be listed in DCupdater?
From what I understand Google will not let anyone release 2.2 until N1 has it for a while. HTC has no control over it. It is google's way of keeping the N1 atop of the phone ladder. The same will happen with the next version. Its google's game, we have to play by their rules.
eskomo said:
From what I understand Google will not let anyone release 2.2 until N1 has it for a while. HTC has no control over it. It is google's way of keeping the N1 atop of the phone ladder. The same will happen with the next version. Its google's game, we have to play by their rules.
Click to expand...
Click to collapse
I don't think that's true... The source code is released so anyone can compile it whenever. That's the whole point of it being open.
Where did you hear that?
hved999 said:
Is there any time frame for when DC development will come out with froyo with sense ROM. I currently am running DC 3.2.3. If they release it will it be listed in DCupdater?
Click to expand...
Click to collapse
I've been stalking the DC thread for the past few days & it looks like they're starting to wrap things up. They didn't give an exact ETA, but based off the few comments they have made, i'd guess within the next few days ( i would love it for this weekend ), but i guess we'll just have to wait & see .
eskomo said:
From what I understand Google will not let anyone release 2.2 until N1 has it for a while. HTC has no control over it. It is google's way of keeping the N1 atop of the phone ladder. The same will happen with the next version. Its google's game, we have to play by their rules.
Click to expand...
Click to collapse
Well, not entirely. When Google is finished testing on their "standard" hardware (in this case, the Nexus One) they will designate a final version. Then, HTC needs to get hold of this final version and add support for any unique hardware or software that their devices have. Think of it like release candidates and RTM versions of Windows. PC manufacturers get hold of the release candidates and test versions so that they can develop drivers and make sure their devices all work with the new OS. Then they get the final version, tweak what needs to be tweaked, run it through bug testing, and then pass it along.
In this case, HTC has to get the final version, make sure all of their apps and drivers work, make sure it works on their phones, and then pass it to Sprint for *more* testing to make sure it plays nice with the network and performs well.
Veritas06 said:
I've been stalking the DC thread for the past few days & it looks like they're starting to wrap things up. They didn't give an exact ETA, but based off the few comments they have made, i'd guess within the next few days ( i would love it for this weekend ), but i guess we'll just have to wait & see .
Click to expand...
Click to collapse
I am aware that for many ROMs the camera doesn't work. Will it be working DC's ROM? And will it have sense? Is there any speculations of certain features not working? sorry these questions but since you have been "stalking" their thread you would know this stuff more than other (atleast I guess).
hved999 said:
I am aware that for many ROMs the camera doesn't work. Will it be working DC's ROM? And will it have sense? Is there any speculations of certain features not working? sorry these questions but since you have been "stalking" their thread you would know this stuff more than other (atleast I guess).
Click to expand...
Click to collapse
According to a Tweet from Damageless himself last night "finishing porting cameras to Android 2.2... getting close."
Also the ROM will include Sense w/ the option to disable if desired.
-kp
kperry1911 said:
According to a Tweet from Damageless himself last night "finishing porting cameras to Android 2.2... getting close."
Also the ROM will include Sense w/ the option to disable if desired.
-kp
Click to expand...
Click to collapse
Thank you very much. Is there a approximate release date for the ROM?
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.
From Droid Life on Twitter:
Droid Life
I must stay, not surprised if it's true. The time it was "supposed" to happen came and went, with no word. I bet they do the same thing with the 2.3 release that they did with the HTC Desire, put it out there on their development site and state that it's for "advanced users". Good thing we had the leak a little while back, and amazing developers who spend endless hours tweaking and adding things to make it usable!
Hopefully this is a mistake. Otherwise, it would be nice if they could release the source code so that those who actually care (xda devs, etc) can deliver the goods. However that's wishful thinking.
Sent from my Droid Incredible using the XDA app.
i could have told you that in march when it EOL'd HTC still sells and supports the device, and alot of verizon stores have accessories for the phone on clearence as in, under 4 bucks sitting in a cardboard box in the back clearence, (IE. they want to get rid of them)
so, yeah, i could have told you that already, and we probably will see a source code release, they released the source code for GB on the samsung galaxy s phones, and i think either MIUI or cyanogenmod already has 2.3.4 on the fascinate, with the right kernel.
And here too:
http://www.androidpolice.com/2011/0...bringing-gingerbread-to-the-droid-incredible/
I never really cared about a gingerbread ota, I just want that sense .35 kernel source.
Sent from my ADR6300 using XDA App
i said it before, and i will say it again, ROOT YOUR PHONES IF YOU WANT MORE OUT OF IT!.
there are some non-tech users, yes, but those of us that are power users, like the idea of having a good phone, i'm close to ordering an extended battery (just going to mod the siliconecase i have now with a pocket knife, no need to speed 15 bucks on somthing you can do yourself )
Kiboe said:
i could have told you that in march when it EOL'd HTC still sells and supports the device, and alot of verizon stores have accessories for the phone on clearence as in, under 4 bucks sitting in a cardboard box in the back clearence, (IE. they want to get rid of them)
so, yeah, i could have told you that already, and we probably will see a source code release, they released the source code for GB on the samsung galaxy s phones, and i think either MIUI or cyanogenmod already has 2.3.4 on the fascinate, with the right kernel.
Click to expand...
Click to collapse
I don't think we'll be seeing source code. AFAIK, they're only obligated to opensource within 30 days of officially releasing it.
snq- managed to reverse engineer the desire's gb kernel when it was leaked, and created a closed-source kernel with governers and oc/uv as modules. So it's possible to have a custom kernel, but I know for a fact that I don't possess the skill required to do that. We'd have to talk to the resident kernel hackers about that.
tcberg2010 said:
I never really cared about a gingerbread ota, I just want that sense .35 kernel source.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Yeah, kernel source would be nice.
wdfowty said:
I don't think we'll be seeing source code. AFAIK, they're only obligated to opensource within 30 days of officially releasing it.
snq- managed to reverse engineer the desire's gb kernel when it was leaked, and created a closed-source kernel with governers and oc/uv as modules. So it's possible to have a custom kernel, but I know for a fact that I don't possess the skill required to do that. We'd have to talk to the resident kernel hackers about that.
Click to expand...
Click to collapse
what device does -snq own?
Kiboe said:
i said it before, and i will say it again, ROOT YOUR PHONES IF YOU WANT MORE OUT OF IT!.
there are some non-tech users, yes, but those of us that are power users, like the idea of having a good phone, i'm close to ordering an extended battery (just going to mod the siliconecase i have now with a pocket knife, no need to speed 15 bucks on somthing you can do yourself )
Click to expand...
Click to collapse
Agreed, time to root to take advantage of this phone if you haven't. Not only can you run Gingerbread, but get better battery life and better overall feel.
I saw the reverse engineered HTC Desire kernel, as since my g/f has one on USCC now. I couldn't figure out how it was done, other than reverse engineered...impressive.
Maybe we'd get lucky and some developer would do the same, as I think it'd make the 2.3 Sense ROMs run better...
I am so thankful for our devs/modders/themers who put in the time!
JoelZ9614 said:
what device does -snq own?
Click to expand...
Click to collapse
I've seen him a lot in the Desire forums, and Xoom too...but not sure what device he owns for sure (maybe both, if not more?).
bollocks!
/10char
The biggest problem we will have, if HTC doesn't release the update, is that they will not HAVE to release the Gingerbread kernel source. That means no OC or other great tweaks to the kernel.
I just want a tun.ko module for the gingerbread kernels so that I can use VPN again with the new Sense 3.0 ROMS! Come on, we atleast need the source!
I'd be way more upset about not getting gingerbread if it wasn't already available with the aosp roms.
Sure it sucks not getting the code to modify sense kernels, but honestly, with the dev community around here, that's not a huge loss.
Sent from my ADR6300 using XDA App
Lets start nagging them about ICS
Maybe there's a way to get HTC to start putting leaks on their dev center site so that the community can play with them too. Is there a way to mod one of the other GB kernels source codes to fit the Inc?
http://htcdev.com/devcenter/downloads
kzoodroid said:
Maybe there's a way to get HTC to start putting leaks on their dev center site so that the community can play with them too. Is there a way to mod one of the other GB kernels source codes to fit the Inc?
http://htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
Actually yes. Having a kernel dev that has the knowledge or is willing to that for us....
seems that chad is the only active kernel dev left in this forum. i found a site that had pretty detailed instructions on how to set up a linux box to build kernels and it doesn't look all that difficult. my only problem is linux, i kind of suck at it, though i've played with it off and on for the last 6 years. right now i don't have a linux box but in december i'm getting a new laptop and will turn the old one into a dedicated linux box so maybe i'll look at it then. i also plan to move to the iphone, i know you don't have to say it i drank the kool-aid, but this will free up my inc for me to do more experimentation with.
We will have to wait and see! THe new HTC Vigor is looking promising.
^noob
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?!
Waiting for the sources that is, what are porters planning on sticking on this? Personally I want the sources to attempt to port Sailfish, only reason I bough the phone. I currently have the Nexus 5 and the OS runs buttery smooth thanks to the porters over at #sailfishos-porters
Am even wondering did I make a mistake buying this device when the Nexus 5, is more than enough omph to power the OS. But I've got it and gotta try, to atleast expand my own knowledge base.
also do you guys know how chainfire managed to build the kernel for it without the sources?
WTF?
The phone has been out for less than a month. Have some patience or start learning to develop yourself, rather than creating a useless thread, just to whine.
I got my 5x last Tuesday and forgot how little I like "pure" android. I think the usual progression is flash aosp then flash cyanogenmod once the nightlies start to stabilize. I know I'm in the minority but the nexus phones usually have too much Google on them for my taste. I like the hardware, but the software is another story.
At any rate, I'm also waiting for the binaries and device tree so that I can start building my own.
m4r0v3r said:
Waiting for the sources that is, what are porters planning on sticking on this? Personally I want the sources to attempt to port Sailfish, only reason I bough the phone. I currently have the Nexus 5 and the OS runs buttery smooth thanks to the porters over at #sailfishos-porters
Am even wondering did I make a mistake buying this device when the Nexus 5, is more than enough omph to power the OS. But I've got it and gotta try, to atleast expand my own knowledge base.
also do you guys know how chainfire managed to build the kernel for it without the sources?
Click to expand...
Click to collapse
If you knew much about how android works, you'd know that chainfire didn't make a kernel. He took the boot image and modified some fstab, prop, and sepolicy stuff, repackaged it, and released it. He didn't build his own kernel.
In any case, I'm curious about this, how long does it usually take google to release their sources?
Sent from my Nexus 5X using Tapatalk
sn0warmy said:
WTF?
The phone has been out for less than a month. Have some patience or start learning to develop yourself, rather than creating a useless thread, just to whine.
Click to expand...
Click to collapse
oh yeah Ill just go and create a kernel, and while am at it, I may as well write my own drivers. Maybe I'll call my kernel linox, and adopt this policy of sharing my source code so other people could collaborate. Maybe using some sort of version control, call Hit or something, maybe on some website called HitHub.
Yeah that sounds like a good way to develop it...Or Google could hurry the **** up and release the sources and binaries so I wouldn't have to.
Well if you read my post you'd see I was curious about what people wanted to port.
drsn0w said:
If you knew much about how android works, you'd know that chainfire didn't make a kernel. He took the boot image and modified some fstab, prop, and sepolicy stuff, repackaged it, and released it. He didn't build his own kernel.
In any case, I'm curious about this, how long does it usually take google to release their sources?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Not make but people have been saying it was built with forceencrypt disabled so I thought he built the kernel with that flag, (ie he had the sources). But it seems thats not the place to change it
Wow the self-entitlement is real nowadays, patience bro. You cant have everything instantly when you want it.
m4r0v3r said:
oh yeah Ill just go and create a kernel, and while am at it, I may as well write my own drivers. Maybe I'll call my kernel linox, and adopt this policy of sharing my source code so other people could collaborate. Maybe using some sort of version control, call Hit or something, maybe on some website called HitHub.
Yeah that sounds like a good way to develop it...Or Google could hurry the **** up and release the sources and binaries so I wouldn't have to.
Well if you read my post you'd see I was curious about what people wanted to port.
Not make but people have been saying it was built with forceencrypt disabled so I thought he built the kernel with that flag, (ie he had the sources). But it seems thats not the place to change it
Click to expand...
Click to collapse
timjp692 said:
Wow the self-entitlement is real nowadays, patience bro. You cant have everything instantly when you want it.
Click to expand...
Click to collapse
what to expect an open source based phone to have the sources with it?
No I know I can't have everything when I instantly want it, but really what could be the reason for the delay. Since am already pretty pissed about the force encryption.
m4r0v3r said:
what to expect an open source based phone to have the sources with it?
No I know I can't have everything when I instantly want it, but really what could be the reason for the delay. Since am already pretty pissed about the force encryption.
Click to expand...
Click to collapse
I'm sorry, but you sound like a whiney little 12 year old who is used to having everything they want RIGHT when they want it. Kind of sums up the turn this forum has taken over the past couple of years.
In the real world you'll learn that good things take time. The phrase, "patience is a virtue" holds true merit.
Offer a bounty if you're that impatient.
sn0warmy said:
I'm sorry, but you sound like a whiney little 12 year old who is used to having everything they want RIGHT when they want it. Kind of sums up the turn this forum has taken over the past couple of years.
In the real world you'll learn that good things take time. The phrase, "patience is a virtue" holds true merit.
Click to expand...
Click to collapse
Apology accepted.
bblzd said:
Offer a bounty if you're that impatient.
Click to expand...
Click to collapse
For what exactly? Someone to break in Google servers and take the source code? lol
m4r0v3r said:
For what exactly? Someone to break in Google servers and take the source code? lol
Click to expand...
Click to collapse
I'm waiting too- it's not like google is still working on the binary drivers and just building the production rom with hacked up device trees until they get the real ones. I could be mis-remembering, but in the past, I thought the factory roms and binary drivers were available the day the devices were released.
I can certainly understand being patient with devs who are working on roms (for free/beer/donations), but google is done with the rom and has already released it to production. The factory image for the 6p was delayed as well. It's not a secret- they are going to push it to every one who bought a phone. My conspiracy theory is that google is trying to bury aosp, and merging android and chrome will be another stab into the heart of both privacy and freedom.
and its outtt
m4r0v3r said:
and its outtt
Click to expand...
Click to collapse
Waiting for some real nexus thing then