Related
i know most of the devs said in order to have custom kernels for the new sense leak we have to wait for the official release or source to drop. i guess my question is, why not take the current shipped kernel and tweak it a bit and add sbc mod to it for the time being?
is this even possible and if so is anyone like toast/netarch working on this?
at this point i think it was said that the current kernel was very incomplete so devs are waiting for htc to drop the KERNAL source code
fixxxer2008 said:
i know most of the devs said in order to have custom kernels for the new sense leak we have to wait for the official release or source to drop. i guess my question is, why not take the current shipped kernel and tweak it a bit and add sbc mod to it for the time being?
is this even possible and if so is anyone like toast/netarch working on this?
Click to expand...
Click to collapse
Mainly, the 2.2 kernel is based on 2.6.32, while the 2.3 kernel included with the last leak was based on 2.6.35. Two different trees totally. With no source for the newer kernel yet, it's almost impossible to do anything... at least easily.
It's easier to just wait for HTC to drop their source for the .35 kernel they are going to use, then the devs can go to town on it fixing what's broken as usual.
I'm not a kernel expert, so there may be things I left out or assumed.
3 months later and still no source code
jbrawley1 said:
3 months later and still no source code
Click to expand...
Click to collapse
3 months? Its only been a little over a month since the official 2.3 update
We're comin from a pure power source.
HTC has released the source code in a month or less in the past for the Evo.
Unfortunately, I don't expect that to happen this time because several of the bugs with the current 2.3.3 release seem kernel related to me. So my guess is we won't see source until after they release the next update. I just can't see them releasing source for something that is so screwed up, but that is pure speculation on my part.
Yeah, if there is already so much talk of another update, then that would make sense. Plus, according to HTC they have 90-120 days to release the source code.
I thought it was 30 days. I know toast wants kernel source for evo 4g and evo shift. Hopefully HTC realizes its been over a month. I don't think it matters if 2.3.3 has bugs, since it was officially released I think they are required to post kerenel source of what they used for 2.3.3
Maybe we should give a reminder to @HTC on twitter
Sent from my PC36100 using XDA Premium App
deviouskater said:
I don't think it matters if 2.3.3 has bugs, since it was officially released I think they are required to post kerenel source of what they used for 2.3.3
Click to expand...
Click to collapse
I don't think their is any requirement for them to release source until they get it working. For example, I can almost guarantee we will never see source for the 4.22.651.2 update, and as I said before, it wouldn't surprise me if we got another update and never see source for the current 4.24.651.1 update either. I can think of several good reasons why they wouldn't release source with known problems.
Every time I back out of an app and have to wait for sense to reload, or whenever I try to switch to an app that was supposed to be running in the background and it has to reload and start over, it is obvious that this kernel has serious issues. I would bet HTC is working on it now to figure out what those issues are.
So... i know that there aren't any devs working on modifying the kernels from the 2.3 Sense Leak, but this is something I dont really understand.
Netarchy and crew (among many others) had kernels pushed out for the EVO WAAAAYYY before they released any source info. and even when we moved to 2.2, there were kernels ready soon after.
Obviously, the brightness fix is in a ton of working 2.2 kernels. Why cant we pull that out and put it in another kernel? Maybe add SBC and/or some battery tweaks?
I know that devs dont want to have to start over if there is a major difference in the Kernels from beta to release, but what would be the major change? Wouldnt the 2.3 be a good place to start messing around, and then make small adjustments when the full kernel is released? You could easily get a leg up on other devs and incorporate it into the TONS of 2.3 Roms that are out there now.
Im ignorant as hell when it comes to kernels and compiling, but speaking on a tiny modicum of common sense, there should be a way to prod and poke this kernel into submission.
ignore me if in being dumb. I just felt like i had to ask this.
EDIT:
Id like to keep this a conversation between people who want this and people who know. Please dont add your 2cnts in to say the same things we have all heard (we need source, cant do it, no reverse engineering, blah blah)
If you are a dev and can give some REAL PROPER insight, we would love to hear it. even if its to tell us to stuff it LOL.
rawdikrik said:
So... i know that there aren't any devs working on modifying the kernels from the 2.3 Sense Leak, but this is something I dont really understand.
Netarchy and crew (among many others) had kernels pushed out for the EVO WAAAAYYY before they released any source info. and even when we moved to 2.2, there were kernels ready soon after.
Obviously, the brightness fix is in a ton of working 2.2 kernels. Why cant we pull that out and put it in another kernel? Maybe add SBC and/or some battery tweaks?
I know that devs dont want to have to start over if there is a major difference in the Kernels from beta to release, but what would be the major change? Wouldnt the 2.3 be a good place to start messing around, and then make small adjustments when the full kernel is released? You could easily get a leg up on other devs and incorporate it into the TONS of 2.3 Roms that are out there now.
Im ignorant as hell when it comes to kernels and compiling, but speaking on a tiny modicum of common sense, there should be a way to prod and poke this kernel into submission.
ignore me if in being dumb. I just felt like i had to ask this.
Click to expand...
Click to collapse
Unfortunately, there is nothing that can be done until HTC releases source code for the kernel, or until HTC releases a new, working kernel. The kernel that is out now, that causes the brightness issue, is basically an incomplete kernel, from a leaked rom. Something that is fully working, and more stable is needed.
k2buckley said:
Unfortunately, there is nothing that can be done until HTC releases source code for the kernel, or until HTC releases a new, working kernel. The kernel that is out now, that causes the brightness issue, is basically an incomplete kernel, from a leaked rom. Something that is fully working, and more stable is needed.
Click to expand...
Click to collapse
I appreciate you saying that... but it doesnt explain why we had kernels for 2.1 and 2.2 before any source was released. I would like to hear from the devs directly.
Thanks for chiming in though.
From the little and probably wrong information I'm making up, you can't decompile kernels from a Rom, you need source to download from, then apply your mods and then can compile a fixed kernel
Edit: complete speculation, if it is in fact true i will modify post to reflect my all knowing powers
NewZJ said:
From the little and probably wrong information I'm making up, you can't decompile kernels from a Rom, you need source to download from, then apply your mods and then can compile a fixed kernel
Click to expand...
Click to collapse
Thank you... but this is what I am trying to avoid. Id like to remove the misinformation and get a real set of reasons and information. We can all speculate. I want a real answer... and im sure im not the only one.
rawdikrik said:
Thank you... but this is what I am trying to avoid. Id like to remove the misinformation and get a real set of reasons and information. We can all speculate. I want a real answer... and im sure im not the only one.
Click to expand...
Click to collapse
Can't make kernels unless they are 1.) reverse-engineered 2.) or HTC releases the source code for a specific device.
Too time consuming. And by the time, it goes through a psuedo-SDLC, HTC would have probably already released the newest one and devs here already working on a custom kernel.
Hope that answers your question
I believe net said he would work on one as soon as the source is released....I think I read it in his thread
Sent from my PC36100 using XDA App
pinky059 said:
Can't make kernels unless they are 1.) reverse-engineered 2.) or HTC releases the source code for a specific device.
Too time consuming. And by the time, it goes through a psuedo-SDLC, HTC would have probably already released the newest one and devs here already working on a custom kernel.
Hope that answers your question
Click to expand...
Click to collapse
So in other words the reasons that they arent bothering is because they dont want to invest the time when it could become obsolete before it is even released?
mutant13 said:
I believe net said he would work on one as soon as the source is released....I think I read it in his thread
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I dont see that happening any time soon.
Not only that, but i think i remember NET working on one before any source came out for 2.2 and 2.1, especially to fix the FPS cap.
I think that he didnt want to touch it because it is beta and can change between now and an official 2.3 release, like most devs have stated.
rawdikrik said:
I appreciate you saying that... but it doesnt explain why we had kernels for 2.1 and 2.2 before any source was released. I would like to hear from the devs directly.
Thanks for chiming in though.
Click to expand...
Click to collapse
Not a problem. I don't have an answer for you about kernels being released for 2.1 and 2.2 before source was released, other than that you're most likely mistaken about that. Based on what I've been told by devs, and what I've seen devs say (netarchy said he'd work on this kernel as soon as source was released, and that there was nothing that could be done prior to source being released....he said it in his kernel thread), it is nearly impossible to mod/tweak a kernel without the source code. Without source code, it would need to be reverse engineered. By the time that was to happen, a new kernel would already be released most likely.
That's all I got on that issue. So basically, no custom kernels without kernel source.
k2buckley said:
Not a problem. I don't have an answer for you about kernels being released for 2.1 and 2.2 before source was released, other than that you're most likely mistaken about that. Based on what I've been told by devs, and what I've seen devs say (netarchy said he'd work on this kernel as soon as source was released, and that there was nothing that could be done prior to source being released....he said it in his kernel thread), it is nearly impossible to mod/tweak a kernel without the source code. Without source code, it would need to be reverse engineered. By the time that was to happen, a new kernel would already be released most likely.
That's all I got on that issue. So basically, no custom kernels without kernel source.
Click to expand...
Click to collapse
I may very well be COMPLETELY WRONG. LOL. Im not against that. I am right now doing my homework to confirm what ive been thinking.
EDIT: After doing some homework, it looks like Net and Toast were making changes to the stock 2.1 kernel before any source was released. This i remember because the 2.2 Kernels that they first made broke the camera, which wasnt fixed until the source was released. I remember waiting with my hand over f5 til HTC released the source.
They we working hard on using Kernels from other devices and tryign to get the FPS cap removed along with getting the HDMI working.
All i did was go over this ANCIENT thread
http://forum.xda-developers.com/showthread.php?t=719763&highlight=source
rawdikrik said:
I may very well be COMPLETELY WRONG. LOL. Im not against that. I am right now doing my homework to confirm what ive been thinking.
EDIT: After doing some homework, it looks like Net and Toast were making changes to the stock 2.1 kernel before any source was released. This i remember because the 2.2 Kernels that they first made broke the camera, which wasnt fixed until the source was released. I remember waiting with my hand over f5 til HTC released the source.
They we working hard on using Kernels from other devices and tryign to get the FPS cap removed along with getting the HDMI working.
All i did was go over this ANCIENT thread
http://forum.xda-developers.com/showthread.php?t=719763&highlight=source
Click to expand...
Click to collapse
Well, maybe there are certain things that can be worked on without source, but I believe for this type of problem (brightness issue), source is needed. Probably similar to how you said that the 2.2 kerneles broke the camera at first, and couldn't be fixed until source was released. This is the same type of deal. Hopefully Sprint will release an OTA within 30-60 days. I wouldn't get my hopes up for anything before that, unfortunately.
k2buckley said:
Well, maybe there are certain things that can be worked on without source, but I believe for this type of problem (brightness issue), source is needed. Probably similar to how you said that the 2.2 kerneles broke the camera at first, and couldn't be fixed until source was released. This is the same type of deal. Hopefully Sprint will release an OTA within 30-60 days. I wouldn't get my hopes up for anything before that, unfortunately.
Click to expand...
Click to collapse
The word around the grapevine is that sprint isn't releasing the OTA until after the release of the evo 3d (marketing scheme, you know how it is).
AbsolutZeroGI said:
The word around the grapevine is that sprint isn't releasing the OTA until after the release of the evo 3d (marketing scheme, you know how it is).
Click to expand...
Click to collapse
I heard that too. That wont be til June/July and then they have another 60days of waiting time they usually take to release source.
and that is IF They do the upgrade, since usually they only want a single upgrade in the life cycle of a product. They will most likely REALLY think about it, to not risk stealing sales from the newer phones coming out over the summer.
AbsolutZeroGI said:
The word around the grapevine is that sprint isn't releasing the OTA until after the release of the evo 3d (marketing scheme, you know how it is).
Click to expand...
Click to collapse
Correct. I predict the 3D to drop within 30-60 days from now though. Then shortly after that, the OTA will probably roll out. As rawdikrik said, source will probably come a month or two after the OTA. The good thing though, is that if/when an OTA is released, it will have a working kernel in it. So even without source being released, a working kernel will be in circulation at that point, which will most likely resolve the brightness issue.
Evo 3D is supposedly hitting June so I'm going to say July just to give it some breathing room. If OTA hits around August maybe September, then its another 30-45 days to release source. So were talking around September-October ish for complete source. This is all speculation but sprint/HTC operate that way. My guess is september for a fully working kernel for GB based on the source code. Stupid marketing scheme to get us to buy the evo 3D.
Sent from my PC36100 using XDA Premium App
I'm so going to buy the EVO 3d
not sure how i feel about the 3d gimmick...
Can we keep this on topic though? THanks guys... Im just waiting to hear something from the big dogs.
Keep in mind it's entirely possible that we will see another leaked kernal long before the OTA is out, this one fully functional. This is especially true if(as many of you seem to suspect) this "leak" was actually no leak at all but an intentional way to let the Chefs and Power Users test their new ROM for them and get feedback on it.
Not sure if you (the Op) have ever tried programming... But (in perspective of the difficulty), basically this would be like me writing a "Hello World" app in Java or C++, and it having an extra space in between the words that bothered you. You would have to cipher through hundreds of lines of code in a hexidecimal editor trying to find the "call" to the display API, and then find which variable or constant it was using for the text output, and change it.
Then you would have to re-compile, and hope it worked without breaking anything else already in place. If you broke something, it's INCREDIBLY hard to debug without real source code.
I hate to do this but did you guys see this. I really wish we were so close on the Epic. Is our phone really so different(I admit I don't know much about the differences)?
I have been following a Twitter that I think should be showing the commits but haven't seen any changes in a while. Has anyone heard anything recently? Are people still working on it? Ready but wait for the source to GB? Or has it been given up on?
Waiting on source from GB
Sent from my SPH-D700 using XDA Premium App
I almost posted this the other day, but I figured i'd get flamed cause it probably affects us 0% that they have it
Posted by Mr. Z's Epic 4G.
No dude? When did the Fascinate get source?
EDIT: *Chanting* MAKE A PORT! MAKE A PORT! MAKE A PORT! MAKE A PORT!
We'd have a better change getting official gingerbread tonight than getting a port of thay imo
Posted by Mr. Z's Epic 4G.
I agree with Zanderman. Although ports seem to "sound easier" to accomplish, that isn't always the case. I've heard lots of talk about it being easier and a lot more productive if we got Devs to build it once source is released opposed to porting it. patience is key here, which a lot of us don't seem to have anymore -__- I'm confident our Devs will get it working soon tho, we just need good ol' Samsung to release code, which they like taking their sweet time with -__-
Sent from my SPH-D700 using XDA App
But isn't the only difference that affects the Rom, the different bands that Sprint and Verizon use? They're both CDMA, so if we built a AOSP GB Kernel, we could probably use their ROM, but if not, it'd be easier to port than the GSM Galaxy S and variants. Keyboard shouldn't affect the ROM much.
But they don't have Source either! How did they get it is my question.
Bump and a thanks if you answer my question
Because their developers decided they needed to build their own, and got it right. We have to wait becase we know we're getting future updates.
Posted by Mr. Z's Epic 4G.
I have a question, while everyone says that to get cm7 we need to wait for official gb. I understand that but we got official froyo didn't we? how come we don't have cm6 if it was official froyo and i would think it came with source within 30 days?
By all means, dont take this as a rant, i was just curious.
The people working on cm6 didn't see any point in finishing the project even with source because gb and new source was supposedly around the corner. 6 months later, we still don't have gb, and imo may never, and cm6 is final. The real cyanogen team doesn't support 6 anymore afaik.
Sent from my SPH-D700 using XDA App
austin420 said:
The people working on cm6 didn't see any point in finishing the project even with source because gb and new source was supposedly around the corner. 6 months later, we still don't have gb, and imo may never, and cm6 is final. The real cyanogen team doesn't support 6 anymore afaik.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
No I asked this same question the other day and a CyanogenMod dev said it was because we never got driver sources :/ supposedly were getting them with gb but if not its gonna be hit or miss every step of the way since building aosp roms w/o source is like navigating a maze in the dark.......
theduce102 said:
No I asked this same question the other day and a CyanogenMod dev said it was because we never got driver sources :/ supposedly were getting them with gb but if not its gonna be hit or miss every step of the way since building aosp roms w/o source is like navigating a maze in the dark.......
Click to expand...
Click to collapse
i thought they had to release source within 30 days? or is the driver source not part of that?
if they didn't release the driver source with official froyo release then they probably wont for gb, then its say bye bye to official cm -.-
kwazytazz said:
i thought they had to release source within 30 days? or is the driver source not part of that?
if they didn't release the driver source with official froyo release then they probably wont for gb, then its say bye bye to official cm -.-
Click to expand...
Click to collapse
Let's clear a something up.
Official Cyanogenmod is 100% possible WITHOUT source code/drivers/etc. it just is not a practical endeavor to begin the arduous process of writing drivers and an AOSP kernel from scratch when there is a very real chance of source code being released in the near future.
kwazytazz said:
i thought they had to release source within 30 days? or is the driver source not part of that?
if they didn't release the driver source with official froyo release then they probably wont for gb, then its say bye bye to official cm -.-
Click to expand...
Click to collapse
Yeah its not impossible dude, just like 063_XBOX said..... I thought my metaphor explained it pretty well .... its possible to navigate your way out of a maze in the dark.... it'll just be a pain in the ass running into walls the whole way through..... "if we don't get any source with gb, Id think we would have nightly builds within 2-3 months assuming everyone pitched in and we had our best devs on the job..... " everything in the quotes is speculation and my personal guess so take it with a grain of salt or not at all.....
Ninja Edit: and as for source being released within 30 days of rom release, that's only for the kernel (and maybe rom?, I don't think roms have source??? I could be wrong)...... but drivers are closed source, which means they aren't required by license to give out.....
theduce102 said:
No I asked this same question the other day and a CyanogenMod dev said it was because we never got driver sources :/
Click to expand...
Click to collapse
I didn't think we ever had a sanctioned cyanogen mod dev working on the epic. Just other devs working on a port.
Sent from my SPH-D700 using XDA App
austin420 said:
I didn't think we ever had a sanctioned cyanogen mod dev working on the epic. Just other devs working on a port.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Naw we have had quite a few devs working on it but one of them just so happened to answer me....
But when I say CM dev I mean someone who actually contributed to the projects and made some progress in getting something to work in one of the builds.....
Ok .. we all know that XDA members and especially the Dev's are anxious to get there hands on an OFFICIAL AT&T release of JellyBean 4.1.x for our SGSIII's .. well, I can tell you this .. so far, AT&T (that I'm aware of) have already gone through 3 releases .. and NOT one of them have found there way up here on XDA.
The 4 builds so far are:
samsung/d2uc/d2att:4.1.1/JRO03L/I747UCDLI7:user/release-keys
samsung/d2uc/d2att:4.1.1/JRO03L/I747UCDLJ2:user/release-keys
samsung/d2uc/d2att:4.1.1/JRO03L/I747UCDLJ3:user/release-keys
samsung/d2uc/d2att:4.1.1/JRO03L/I747UCDLJ3c:user/release-keys
So .. if ANYONE knows, has access, secrets .. etc etc etc .. please release or leak so that our Dev's can have some real fun
I have searched high and low all over the internet .. I have been unable to find absolutely ZIP on all 3 releases.
And just how did you come across this information?
mrhaley30705 said:
And just how did you come across this information?
Click to expand...
Click to collapse
http://www.glbenchmark.com/phonedetails.jsp?benchmark=glpro25&D=Samsung+SGH-I747+(Samsung+Galaxy+S+III+AT+and+T)&testgroup=system
Ya seriously, we need someone on the inside to release these leaks.
I have been toying with installing a JB custom ROM from here, but all of them have things that just aren't working.
Sometimes I am tempted to just go back to the iPhone and get a 5.
I would love to install an official leak. Would make me feel better.
I am sure we will see something very soon in the form of a leak or info on official release. A Sprint document was just leaked stating the their official JB update pushes tomorrow. Unfortunately its always the case that AT&T takes longer on updates than others.
Ooo, watching this thread eagerly. Phandroid released an article today that Sprint is going to start JB updates for their GS3s starting tomorrow:
http://phandroid.com/2012/10/24/sprints-samsung-galaxy-s3-jelly-bean-rollout-starts-october-25th/
Would love to get my hands on one of these leaks until the official makes its way out.
jmacdonald19 said:
Ooo, watching this thread eagerly. Phandroid released an article today that Sprint is going to start JB updates for their GS3s starting tomorrow:
http://phandroid.com/2012/10/24/sprints-samsung-galaxy-s3-jelly-bean-rollout-starts-october-25th/
Would love to get my hands on one of these leaks until the official makes its way out.
Click to expand...
Click to collapse
Here's the article that specifically references the Sprint exclusion that I referenced on the other thread. As evidenced by today's development, the Examiner was correct.
http://www.examiner.com/article/samsung-galaxy-s-iii-may-not-get-jelly-bean-u-s-until-2013
kgbkny said:
Here's the article that specifically references the Sprint exclusion that I referenced on the other thread. As evidenced by today's development, the Examiner was correct.
http://www.examiner.com/article/samsung-galaxy-s-iii-may-not-get-jelly-bean-u-s-until-2013
Click to expand...
Click to collapse
Well nuts. I wonder why only Sprint is getting the love? Supposedly there are AT&T JB betas out there in the wild being tested, but none of them have leaked.
Can't come soon enough, if only because it'll eventually help our AOSP jelly roms wrt the proprietary bits.
There's no going back to a stock touchwiz rom, even if it is jellybean. )
(EDIT: Somebody gave this thread a 1-star rating, so I gave it a 5 to raise the current avg to 3)
zmore said:
Can't come soon enough, if only because it'll eventually help our AOSP jelly roms wrt the proprietary bits.
There's no going back to a stock touchwiz rom, even if it is jellybean. )
(EDIT: Somebody gave this thread a 1-star rating, so I gave it a 5 to raise the current avg to 3)
Click to expand...
Click to collapse
yeah, even if I won't use the stock JB rom, devs will to make our CM/AOKP much much better.
awaiting development.
joeyl said:
awaiting development.
Click to expand...
Click to collapse
And they are waiting for leakage.
By the looks of it .. there is now another release out there somewhere for AT&T :
samsung/d2uc/d2att:4.1.1/JRO03L/I747UCDLJ3c:user/release-keys
It doesn't matter if there are a million leaks, without the ability to dl, it doesn't do a lot of good.
Sent from my SGH-I897 using xda premium
mrhaley30705 said:
It doesn't matter if there are a million leaks, without the ability to dl, it doesn't do a lot of good.
Click to expand...
Click to collapse
I know .. it just sucks that all these are out there somewhere, and we can't get our hands on any of them !!!
Randomacts said:
yeah, even if I won't use the stock JB rom, devs will to make our CM/AOKP much much better.
Click to expand...
Click to collapse
Except that CM/AOKP are built almost entirely from source. Considering there isn't really a whole lot that's different between the Sprint, Bell, or whatever other carriers leaked/released their official JB builds for the GS3, i can't imagine having an AT&T specific ROM providing more aide than any of the others have already done.
elementaldragon said:
Except that CM/AOKP are built almost entirely from source. Considering there isn't really a whole lot that's different between the Sprint, Bell, or whatever other carriers leaked/released their official JB builds for the GS3, i can't imagine having an AT&T specific ROM providing more aide than any of the others have already done.
Click to expand...
Click to collapse
Regarding what leaks are already out there .. Sprint, Bell, Rogers, T-Mobile etc etc etc // There are still bugs with each one of them on our AT&T SGS3's .. and again, these are of cause leaks .. except the Sprint release which is now Official, and there are even still bugs with that when ported over to ours.
At least, if we can get our hands on a original AT&T leak .. we can see if these same bugs exist between the builds, or if AT&T has everything working as it should .. who knows !!!
That's why I've been posting that there are test builds out there for AT&T .. just cannot find them, or get our hands on them .. I know there is someone out there that has access to these builds .. problem is, that person is telling me that he does "not have permission to release" !!!
I couldn't even get the fella to verify the build numbers for me.
Some devs have serious connections when it's available out well be here
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
Some devs have serious connections when it's available out well be here
Click to expand...
Click to collapse
Ohh I'm fully aware of that .. alot of Devs do .. worse part of all this, I know someone on here that already has access to and has been using it .. I cannot persuade him to release/leak what he has, keeps telling me "I don't have permission" !!! SUCKS
His last response to me on Twitter was "I'm good, many people send drama my way for giving them free stuff. some people in the android community just ruin it for everyone." and I haven't heard from him since.