Develop Bugs

KingKlick has been banned..question about Kings #6 BFS and SetCPU

It's well reported here:http://home.comcast.net/~ttechnology/htc.html that Kings kernel #6BFS and Baked Snack #6 are the best kernels for battery life. I'm interested in doing some testing on my own with these and am just curious about everyones experiences with them and SetCPU.
Anyone reporting better battery life with another kernel/underclock widget?
So far the tweak has been the best for me.

jhoffy22 said:
It's well reported here:http://home.comcast.net/~ttechnology/htc.html that Kings kernel #6BFS and Baked Snack #6 are the best kernels for battery life. I'm interested in doing some testing on my own with these and am just curious about everyones experiences with them and SetCPU.
Anyone reporting better battery life with another kernel/underclock widget?
So far the tweak has been the best for me.
Click to expand...
Click to collapse
I've been getting great battery life with Netarchy's CFS kernals, I tried King's and Net's BFS kernals for awhile but they just don't run nearly as smooth as the CFS ones do. I get at least 8 or 9 hours with very heavy use. When I'm not using it heavily I normally don't get to see how long it will last because I always end up charging it before it dies.

Why the hell was King banned??

thefoss said:
Why the hell was King banned??
Click to expand...
Click to collapse
Supposedly he posted a link to his website therefore bypassing the donation system implemented by xda into the development section.

Wow, this place is just full of b*****t.
Ban the developers that make this place what it is, that's real f****g smart.
[highlight]Mod Edit: Watch your language[/highlight]

_MetalHead_ said:
Wow, this place is just full of b*****it.
Ban the developers that make this place what it is, that's real f*****g smart.
Click to expand...
Click to collapse
+1 agreed ok so he bypassed the donation deal but the better question is was it worth it for them to ban an incredible developer that has made some of the best kernel's for the evo (I know I know what is considered best is a matter of opinion) so now its netarchy and stock from what i can gather cause I won't run cyanogen and their kernels are rom specific

I got banned for quoting a movie.
Sent while sitting on the toilet.

Reguardless of his contributions to this site and its many users he charges for access to his work which goes against everything xda is about. This is a place to share openly with others, and yes i agree king is a genieus and many things wouldnt be possible without him but making people pay for access to his work dont fly here. Xda is doing a good thing by making an example of him and keeping everything accessable to everyone.

Prepare for lockdown as with all of the previous topics regarding King's ban....

I wonder if it's going to be a temporary or permanent ban? Hopefully it is only temporary.

King still giving his kernels for free is just his roms that request donations thats why he does not post them here, just following the rules,
Sent from my PC36100 using Tapatalk

Since many people don't seem to understand that Android is open source, and what that means, I'll try to explain it some. If I get anything wrong feel free to correct me.
Open Source Definition
Android is basically an OS on top of an OS, with the base being the Linux kernel. Both are open source, Linux created by Linus Torvalds and Android owned by Google and maybe thirty other companies. Android ROMs, the kernels and any creation or monstrosity that comes from modifying them are still owned by the people or companies that originally created them. Trying to sell it as your own is Illegal...
You're not going to rip iOS off an iPhone, change a few pictures, and then sell it as your own creation and if you're smart you won't try doing it with Android ROMs either.

xHausx said:
Since many people don't seem to understand that Android is open source, and what that means, I'll try to explain it some. If I get anything wrong feel free to correct me.
+100
Open Source Definition
Android is basically an OS on top of an OS, with the base being the Linux kernel. Both are open source, Linux created by Linus Torvalds and Android owned by Google and maybe thirty other companies. Android ROMs, the kernels and any creation or monstrosity that comes from modifying them are still owned by the people or companies that originally created them. Trying to sell it as your own is Illegal...
You're not going to rip iOS off an iPhone, change a few pictures, and then sell it as your own creation and if you're smart you won't try doing it with Android ROMs either.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

WELL, if he followed the rules just like other devs here, he wouldnt be in this predicament, he did great work around here, but not exempt from rules. I actually thought that he was making huge bank off this stuff. It had been brought up in a few of his threads

_MetalHead_ said:
Wow, this place is just full of b*****t.
Ban the developers that make this place what it is, that's real f******g smart.
Click to expand...
Click to collapse
I can sense either a thread lock or ban coming really soon here....... just sayin'....

He has a new evo rom just released today.
Should be on google since it's android.

xHausx said:
Since many people don't seem to understand that Android is open source, and what that means, I'll try to explain it some. If I get anything wrong feel free to correct me.
Open Source Definition
Android is basically an OS on top of an OS, with the base being the Linux kernel. Both are open source, Linux created by Linus Torvalds and Android owned by Google and maybe thirty other companies. Android ROMs, the kernels and any creation or monstrosity that comes from modifying them are still owned by the people or companies that originally created them. Trying to sell it as your own is Illegal...
You're not going to rip iOS off an iPhone, change a few pictures, and then sell it as your own creation and if you're smart you won't try doing it with Android ROMs either.
Click to expand...
Click to collapse
The issue is that you can accept donations, but not hold out and demand pay (AFAICT). Also, a minor point, but the Android OS is under a different license than the kernel. This was done to appease carriers and phone manufacturers, both of whom are hesitant to release full source for their products.

I just checked his website out. $5.50 a month as an option? I don't know, man. Developers should receive donations and all for their work but he's pushing that envelope a little further than I'm comfortable with.

Under forums, evo development, on kings site there are free kernels and other free evo releases.

halorin said:
I just checked his website out. $5.50 a month as an option? I don't know, man. Developers should receive donations and all for their work but he's pushing that envelope a little further than I'm comfortable with.
Click to expand...
Click to collapse
That's pretty egregious, but it's bound to happen when people are tossing around the term "genius" to describe his work.

[Q] Why dont we have GB Sense Kernels?

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.

Inc no longer receiving 2.3, according to HTC Rep?

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

[INFO] Good News Abound - The state of DEV

I thought I'd clear some things up.
If I'm wrong please don't flame me, I'm only doing my best to subdue the general discontent in [sgh-t989]/[android development]...
Steve Kondik, also known as the creator of the godfather of all ROMS (cyanogenmod) personally owns one of our t989s (source:twitter). That, combined with the fact that this is a FLAGSHIP t-mo device probably means that our phone will be supported from the day that 9.0.0 drops.
Now, let me tell you what this means.
As you all know, for a device get non-kang CM9 our hardware must be fully supported. Camera, GPS, bluetooth, egl drivers all must work.
When a huge scale ROM like CM9 is cooked for so many devices I understand it goes something like this
[AOSP modified by Cyanogenmod(teamdouce)] +
[Android Kernel, also modified by Cyanogenmod]+
[Device tree]+
[A virgin sacrifice]=
CYANOGENMOD
Now the interesting bit, is that as soon as the device tree (Eg. Specific driver modifications for GPS, Camera, GPU) includes our device the device tree can be used to power OTHER AOSP ROMS like Miui
I know that gingerbread MIUI already makes use of the CM7 device tree, so in all likelihood they will use the CM9 device tree as well!!!
So in conclusion.
-Because CM9 has a high likelihood of dropping on our devices as soon as it comes out (most likely within the next 30 days)
-Because other AOSP-Based roms depend on the cyanogenmod device tree
-WE WILL HAVE A LOT OF FLASHING OPTIONS SOON
-Probably including CM9 AND MIUI v4 <<<<--------THAT **** CRAY
Thanks for your time, hope it helped
Don't forget the thanks button feels good when you push it.

there are a lot of other devices with cm9 alpha and we are still not an officially supported device. Still unofficially being worked on

I for one is not counting on it, frankly...
No matter how beautifully you phrase things, WE GOT NOTHING YET.
Sent from my SGH-T989 using XDA App

[A virgin sacrifice] =
SO FREK'IN EXCITED!!!!!

thanks for the info bro looking forward to it

jessejames111981 said:
there are a lot of other devices with cm9 alpha and we are still not an officially supported device. Still unofficially being worked on
Click to expand...
Click to collapse
the thing is, many of those are KANGed as in not officially supported by CM team
of the few that officially are supported is Nexus S i9020 and SGS i9000
even the "classic" SGS2 i9100 is not fully supported by CM yet, there's more bugs than... well it's not usable as a daily driver
that was just before the end of last year
they might have improved it a bit by now
even the Nexus S version of CM9 is still very buggy, that's why i have the stock official ICS4 instead on my Nexus S

Please please use words like
"death of an era." Instead of virgin sacrifice. I don't believe in that
Sent from my SGH-T989 using xda premium

iwasblown said:
Please please use words like
"death of an era." Instead of virgin sacrifice. I don't believe in that
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I don't believe in idiots, can you make them all go away?

It takes time for this stuff guys. Anyone remember how long it took to jump from donut to eclair to get a stable rom? And look how few devices there were that actually ran android. This whole "if its not done in 2 weeks then its never happening" thing is a bit unfair. Let the devs dev and those who do not can wait for them quietly.

Why this statement?
From a glaxay better than yours.

tl;dr
I am basing my entire post on the fact that Steve Kondik has our device and should theoretically be working on it.
Click to expand...
Click to collapse
Steve Kondik aka Mr. Cyanogen also works for Samsung. I am sure he gets ALL Samsung devices...

corwest said:
It takes time for this stuff guys. Anyone remember how long it took to jump from donut to eclair to get a stable rom? And look how few devices there were that actually ran android. This whole "if its not done in 2 weeks then its never happening" thing is a bit unfair. Let the devs dev and those who do not can wait for them quietly.
Click to expand...
Click to collapse
It only takes 2 weeks to modify the stock rom or cm7/9.
Its the expectation that is built when people act like quantity is all that matters. There are basically only 2 people making roms; Samsung and CM team, everyone else just waits on these 2 so that they could tweak and modify one of those 2. The funniest part is that the use of the word "kanging" is thrown around among these other people.

housecat93 said:
I thought I'd clear some things up.
If I'm wrong please don't flame me, I'm only doing my best to subdue the general discontent in [sgh-t989]/[android development]...
Steve Kondik, also known as the creator of the godfather of all ROMS (cyanogenmod) personally owns one of our t989s (source:twitter). That, combined with the fact that this is a FLAGSHIP t-mo device probably means that our phone will be supported from the day that 9.0.0 drops.
Now, let me tell you what this means.
As you all know, for a device get non-kang CM9 our hardware must be fully supported. Camera, GPS, bluetooth, egl drivers all must work.
When a huge scale ROM like CM9 is cooked for so many devices I understand it goes something like this
[AOSP modified by Cyanogenmod(teamdouce)] +
[Android Kernel, also modified by Cyanogenmod]+
[Device tree]+
[A virgin sacrifice]=
CYANOGENMOD
Now the interesting bit, is that as soon as the device tree (Eg. Specific driver modifications for GPS, Camera, GPU) includes our device the device tree can be used to power OTHER AOSP ROMS like Miui
I know that gingerbread MIUI already makes use of the CM7 device tree, so in all likelihood they will use the CM9 device tree as well!!!
So in conclusion.
-Because CM9 has a high likelihood of dropping on our devices as soon as it comes out (most likely within the next 30 days)
-Because other AOSP-Based roms depend on the cyanogenmod device tree
-WE WILL HAVE A LOT OF FLASHING OPTIONS SOON
-Probably including CM9 AND MIUI v4 <<<<--------THAT **** CRAY
Thanks for your time, hope it helped
Don't forget the thanks button feels good when you push it.
Click to expand...
Click to collapse
I'd like to believe, I really would. And I hope this does come to fruition. However, even if it doesn't, the few ROMS we do have are pretty good, and our phone still outperforms almost anything else available right now, so I'll still be happy.
I do have one request, though. Can we figure out a way to make CM based ROMS happen without a virgin sacrifice? There are so many other things in life that require those, that they are starting to become scarce

The fact that lots of other phones have alphas and repositories available to even make kangs does not fare well for our device.
Sent from my HTC_Amaze_4G using xda premium

guys chillax..slayher already has it booting..and that's news from december

good to know, thanks

Great phone, needs more dev time and hopefully that comes along with it when ics hits.
We got shafted early with the nexus release so close to the T989 and a dev that promised things but ran away.
New year brings new hope. Great respect for the devs that care about our phone.
Sent from my SGH-T989 using XDA App

Let's hope the mods don't ban what little devs we have left...
Sent from my HTC_Amaze_4G using xda premium

AznDud333 said:
guys chillax..slayher already has it booting..and that's news from december
Click to expand...
Click to collapse
I don't follow, what do you mean by booting?

synergeticink said:
I don't follow, what do you mean by booting?
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Booting

why are we waiting...

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