Who is trying to build an Android 1.6 (Donut) rom for Hero?
I was thinking about having a stab at this over the weekend but I have a feeling that a few people are already attempting the same and I do not want to waste a weekend reinventing the wheel.
I can either lend a hand to those people trying to get a working build together or I can attempt to go it alone. I would prefer the first option.
Lox_Dev seems to be pro-actively working on something and also seems to be making good progress. Anyone else toiling away in the background?
jabbslad said:
Who is trying to build an Android 1.6 (Donut) rom for Hero?
I was thinking about having a stab at this over the weekend but I have a feeling that a few people are already attempting the same and I do not want to waste a weekend reinventing the wheel.
I can either lend a hand to those people trying to get a working build together or I can attempt to go it alone. I would prefer the first option.
Lox_Dev seems to be pro-actively working on something and also seems to be making good progress. Anyone else toiling away in the background?
Click to expand...
Click to collapse
Seems to be very low activity with Donut rom for Hero. Would be very nice to get the hardware support running in the first release of donut.
NisseGurra said:
Seems to be very low activity with Donut rom for Hero. Would be very nice to get the hardware support running in the first release of donut.
Click to expand...
Click to collapse
might seem so, but behind the scenes several people are working on this.
however this takes some time (most people have a real job
I am just wondering (i expected that this is going to move little faster) thats because i am not really an application/os/device developer ^^, but when this changes gets "splitted" will this porting process into new kernels gets faster? if this moving is going to take several days probably longer for each new version of kernel, man thats going to be so slow :-/
jabbslad said:
Who is trying to build an Android 1.6 (Donut) rom for Hero?
I was thinking about having a stab at this over the weekend but I have a feeling that a few people are already attempting the same and I do not want to waste a weekend reinventing the wheel.
I can either lend a hand to those people trying to get a working build together or I can attempt to go it alone. I would prefer the first option.
Lox_Dev seems to be pro-actively working on something and also seems to be making good progress. Anyone else toiling away in the background?
Click to expand...
Click to collapse
Why are you starting another thread when you have 2 of them on the first page ???
kkoouu said:
Why are you starting another thread when you have 2 of them on the first page ???
Click to expand...
Click to collapse
Why are you using three question marks when one will suffice?
I think you are misunderstanding the question. I am asking who needs assistance with building a Donut rom for Hero, just because those guys are working on it doesn't mean they want/need any help.
Please link me to these 2 threads you speak of where a developer is specifically making a request for others to help them on a Donut rom. If they exist by all means lets delete this thread.
OK, I got it. Sorry. Just the title is a little bit confusing. Anyway ... nice weekend and crunchy tasty Donut making
Hi guys , just asking if any one is thinking of porting the tattoo rom to the hero since the kernel is released ?
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.
Does that mean all the issues with current ICS based ROMs on the DZ will be able to be resolved completely?
Or will it just affect the camera related problems?
Also will CM team then release an official DZ release?
I only ask because it seems like the DHD guys are making some progress with HTC.
http://forum.xda-developers.com/showpost.php?p=30099204&postcount=731
Cheers guys.
Well IF (and that's a pretty big IF considering that we've had plenty of headway with camera stuff on the DZ/G2 end) they were to actually release for example full sources and such it would probably aid to the camera.
However on the DZ/G2 side we already got the andreno libs and such from them over a week ago, it's... complicated.
and PS: the link you provided isn't what I'd call "progress", until we actually see something from HTC. Remember this is the same company that 'confirmed' on 4 or 5 separate instances that the DesireHD was getting ICS from them and to not worry, only to all the sudden not get it.
I wasn't aware that HTC had released new libraries for the device, hope everyone can put them to good use.
Yeah maybe no official progress but you have to commend them for their effort so far.
raiamino said:
I wasn't aware that HTC had released new libraries for the device, hope everyone can put them to good use.
Yeah maybe no official progress but you have to commend them for their effort so far.
Click to expand...
Click to collapse
It's already incorporated as best as can be into the Andromadus branch that I know of and just bout any rom that kangs off that. (getting it going on JB is still a different story since they're meant for ICS).
What I saw is that the most recent quarterly earning reminded HTC that they actually need to keep their customer happy to get the hard earned money.
Even though I am sure I won't buy HTC again until they show some real commitment to update their devices, keep pressuring the heck out of them is a good idea so just tell me if there's another petition.
Not sure if this is a touchy subject but, does anybody know what happened to baked rom? It seems as if they just fell off the face of the earth....
Again, sorry if i shouldnt go in to this, i just cant find any info on them, and their wesite/ G+ hasnt been touched in months. To bad, was a great rom....
I don't think there is anything touchy about it. TravP just took a break. I remember the gap between Baked 8 and 9 was forever, and by that time a new Android (4.2?) was released. Then someone leaked BB9 to the forums when they shouldn't have and he decided to just scrap it. I still have a test build running on my Nexus S I think lol. I swear I saw someone post a screenshot of Trav running BB11 (might have even been trav himself on twitter) not too long ago, so maybe he will jump back in to things eventually. Baked is still the favorite ROM I've had the chance to run!
Thanks for the info, didnt know about that. That sucks it had to end that way, but i understand why he did it. It was also my fav rom. I would still run it if i could. I hope he does jump back into it. It would make me a pretty happy camper
Andromendous said:
Thanks for the info, didnt know about that. That sucks it had to end that way, but i understand why he did it. It was also my fav rom. I would still run it if i could. I hope he does jump back into it. It would make me a pretty happy camper
Click to expand...
Click to collapse
Trust me you wouldn't be the only one! On the GNex we had one of the longest threads in the forum going. Then our device maintainer got banned for something stupid and they locked the thread. (Mind you, this is probably 10 months after the last official release lol)So most of us just left XDA. My S4 isn't even rooted because I can't run AOKP or an AOKP variant. Damn I miss those days!
Ya, alot has changed in the past year or two, but it will get better
Completely OT but I figure why make a new thread. Couple questions for you. 1. Which N7 do you have? 2. Do you know of any ROMs for Deb that have a mutiwindow feature?
First off: I am NOT asking/telling developers to hurry up. I totally respect that ROM development takes time and will gladly wait for the next releases. I am simply curious about a pattern I noticed.
In early August it seemed like ROM releases were more frequent (5-7 days) whereas for PA and Slim we haven't seen a release for almost 20 days. I hope developers can appreciate my question, because instead of asking when the next release is I'm wondering what's been preventing the next release. CM has had the same bugs for almost a month as well, is there some driver that's faulty? Something that has been a PITA to get to work on our platform? Something we are missing? Just curious more about what challenges are causing a hold up, but other than that dev will get to them when they get to them and I'll just be waiting
Thanks for all your hard work devs, hopefully knowing what's been going on behind the scenes can help people to find it in themselves to have patience!
Jhdoubleoseven said:
First off: I am NOT asking/telling developers to hurry up. I totally respect that ROM development takes time and will gladly wait for the next releases. I am simply curious about a pattern I noticed.
In early August it seemed like ROM releases were more frequent (5-7 days) whereas for PA and Slim we haven't seen a release for almost 20 days. I hope developers can appreciate my question, because instead of asking when the next release is I'm wondering what's been preventing the next release. CM has had the same bugs for almost a month as well, is there some driver that's faulty? Something that has been a PITA to get to work on our platform? Something we are missing? Just curious more about what challenges are causing a hold up, but other than that dev will get to them when they get to them and I'll just be waiting
Thanks for all your hard work devs, hopefully knowing what's been going on behind the scenes can help people to find it in themselves to have patience!
Click to expand...
Click to collapse
CM has a buildbox so they can do daily automatic builds. I'm using my laptop so I have to manually do builds that take 5+ hours each. I've been a little busy lately but i did just release a build last night. I also build alot of other ROM's for our device and other devices so sometimes it'll take a bit of time between releases.