Related
I don't know if this has been answered yet I was wondering why we don't have a overclock kernel for dk28. Thanks In advance for your answers.
Sent from my SPH-D700 using XDA App
No source code for DK28 has been released.
Questions in Q&A please, and No Source = No Overclock
flopez76 said:
Questions in Q&A please, and No Source = No Overclock
Click to expand...
Click to collapse
at least it went here instead of the dev section
good job op
brian2220 said:
at least it went here instead of the dev section
good job op
Click to expand...
Click to collapse
Exactly!!
Sent from my SPH-D700 using XDA App
So where did we even get DK28 in the 1st place?
Sent from my SPH-D700 using XDA App
It was leaked fully compiled
So there is no way to make a custom kernel with no source?
Sent from my SPH-D700 using XDA App
Not a practical one, it can be done but takes a LOT of work in comparison to one based off of source code
Ok thanks I was wondering about that for a bit now!!
[derail]
DJ29, DK05, DK17, and DK28 were all leaked within a matter of days from each other. And after that we haven't been given any new leaks. Was the guy who released the builds fired?
On top of that, DK05 and DK28 were compiled within 23 days of each other. The differences between those two were pretty big and if development continued at that rate, we would have a released build by now. Perhaps Samsung took a break for the other phones?
[/derail]
Nice observation.
arashed31 said:
[derail]
DJ29, DK05, DK17, and DK28 were all leaked within a matter of days from each other. And after that we haven't been given any new leaks. Was the guy who released the builds fired?
On top of that, DK05 and DK28 were compiled within 23 days of each other. The differences between those two were pretty big and if development continued at that rate, we would have a released build by now. Perhaps Samsung took a break for the other phones?
[/derail]
Click to expand...
Click to collapse
Source code has been released for I-9000
Sent from my SGH-T959 using XDA App
lets hope we get 2.3 then source a day later...
wow am i dreaming?
probably.
Old news ;]
Seriously, do people not search?
Even though this is the vibrant section, i9k new does get posted here, and something as major as 2.3 kernel source is NOT going to go unnoticed. This is what, the 4th or 5th thread about it? And wasn't the kernel source dropped sometime over the weekend?
Sent from my SGH-T959 using XDA App
wait... they're making gingerbread for the vibrant?! When was this information released!?!
/end sarcasm
It was posted on the samsung site 3-4 days ago I down loaded the source code for GB on Saturday
Doesn't
-Help with froyo roms
-Fix eh17 problems without further work
-Support ext 4 yet
Does
-allow fixes to be made by the developers
-helps the AOSP developers fix issues
-allow overclock without tregrak
-allow voodoo sound without the payed app
-allow other tweaks like the keyboard skip fix
Sent from my SPH-D700 using XDA App
So it won't help stop the random reboots even though it appears to be a voltage/deep sleep transition issue?
Sent from my SPH-D700 using XDA App
marcusant said:
Doesn't
-Help with froyo roms
-Fix eh17 problems without further work
-Support ext 4 yet
Does
-allow fixes to be made by the developers
-helps the AOSP developers fix issues
-allow overclock without tregrak
-allow voodoo sound without the payed app
-allow other tweaks like the keyboard skip fix
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Glad you posted this. Maybe will help clean up the other thread
ugothakd said:
Glad you posted this. Maybe will help clean up the other thread
Click to expand...
Click to collapse
People don't read these answers in that other thread, so they're certainly not likely to visit this thread first - don't get your hopes up
Sent from my CyanogenMODed Epic
kennyglass123 said:
So it won't help stop the random reboots even though it appears to be a voltage/deep sleep transition issue?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I would think it could give the devs the ability to fix it
Sent from my SPH-D700 using xda premium
kennyglass123 said:
So it won't help stop the random reboots even though it appears to be a voltage/deep sleep transition issue?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
rgregg504 said:
I would think it could give the devs the ability to fix it
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Yeah, I think so too. The kernel will allow all those things to be fixed, but some things will take longer to develop than others. Like even though the kernel doesn't automatically fix EH17 bugs or turn into EXT4, I'm positive you'll see kernels that fix EH17 bugs as well as EXT4 converted.
My question? Does this mean wimax in cm7 or is that still samsungs private code?
sent from "The Other Woman"
And it won't fix the GPS crapshoot issues on EH17 I take it....this is why we need the official ish...
Sent from my SPH-D700 using XDA Premium App
usagi111 said:
And it won't fix the GPS crapshoot issues on EH17 I take it....this is why we need the official ish...
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
GPS is amazing on CM7. And this is the "official" source for the Epic from Samsung.
Does this give us the ability to get tv-out working?
Define "Amazing", Plus CM7 doesn't has TW and has audio issues... I'm not trading one hiccup for another...
Sent from my SPH-D700 using XDA Premium App
usagi111 said:
Define "Amazing", Plus CM7 doesn't has TW and has audio issues... I'm not trading one hiccup for another...
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Then don't.
If someone could please clarify the following questions:
1) What exactly does the Epic 4g need that it does not have to run the latest cyanogenmod with full functionality?
2) I assume this source code release does not directly help in implementing cm7. Is that correct?
3) What are the prospects of the Epic 4g being a fully supported cm7 phone sometime in 2012?
Thanks
garyf said:
If someone could please clarify the following questions:
1) What exactly does the Epic 4g need that it does not have to run the latest cyanogenmod with full functionality?
2) I assume this source code release does not directly help in implementing cm7. Is that correct?
3) What are the prospects of the Epic 4g being a fully supported cm7 phone sometime in 2012?
Thanks
Click to expand...
Click to collapse
Okey doke, I've got you.
1) Well for the longest while we've needed an AOSP kernel based on our kernel which we didn't have source to. A GB kernel with source which of course we had gotten due to Mkasick, Rodderik, Jt countless others. As well as a close to official build of CM7(7.1) which is also greatly made possible due to Decad3nce and Jt, and countless others. We're closer because they were coding in the dark kernel wise before now. And Samsung released their official build as well. (Damn you Samsung)
2) It does help, because they now have a basis to work off of to try to get an AOSP kernel which may take time, but we've some of the most talented Rom developers and kernel developers working together to do this.
3) It could happen befoe 2012, there isn't an eta we can give for something such as this when the catalyst we've needed for months has finally been given to us.
I hope I was of some help. If any more questions ask me I'll gladly answer.
Sent from my Epic 4G
Wait, wait, wait, we never covered the essential question:
Can the source enable my phone to make coffee?
It does: have a cute name called source
It does: have the ability to be downloaded, its available right now.
It does: happen to be something everyone's always asked for.
It does not: help you walk your dog.
It does not: improve your Call of Duty skills
It does not: like the fact that I'm making jokes about it.
K'done .
Sent from my SPH-D700 using XDA App
I see I don't understand the basics of what's going on here.
We've had Froyo source for months, but that was not AOSP?
Or have Samsung/Sprint released something with Gingerbread that they did not release with the Froyo source?
Am I understanding correctly that there are now no remaining structural obstacles and implementing CM is just a matter of development time?
Another question: What is the advantage of cyanogenmod over the stock and custom roms already available for the Epic 4g, meaning what will be better once CM7 is running?
garyf said:
I see I don't understand the basics of what's going on here.
We've had Froyo source for months, but that was not AOSP?
Or have Samsung/Sprint released something with Gingerbread that they did not release with the Froyo source?
Am I understanding correctly that there are now no remaining structural obstacles and implementing CM is just a matter of development time?
Another question: What is the advantage of cyanogenmod over the stock and custom roms already available for the Epic 4g, meaning what will be better once CM7 is running?
Click to expand...
Click to collapse
Okay, Ill try to help.
Froyo was AOSP
No, Froyo source came out late with GB was "right around the corner". So development stopped waiting for GB source.
Yes
CM7 = profit.
usagi111 said:
Define "Amazing", Plus CM7 doesn't has TW and has audio issues... I'm not trading one hiccup for another...
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Amazing- (adj.)to amaze.
CM7 will not have TW since uh duh it would ruin the whole "AOSP" aspect, and it is an alpha build, its not going to be perfect, yet.
Sent from my SPH-D700
ac16313 said:
Amazing- (adj.)to amaze.
CM7 will not have TW since uh duh it would ruin the whole "AOSP" aspect, and it is an alpha build, its not going to be perfect, yet.
Sent from my SPH-D700
Click to expand...
Click to collapse
Riiiiiiight....and for someone to say CM7's GPS is amazing and then I load it and get 3 satellites out of 9 to lock means his definition of amazing is WAY THE HELL OFF!!!
If people are going to endorse a ROM at least be truthful to it's claims....</SNARK>
Heck yeah. Finally
Sent from my GT-I9100 using xda premium
What an informative thread!
It's nice to see they have been released though
Direct link for anyone interested:
Download here
What?! Sammy officialy released it? They didnt even released official ICS for my region xD
Great news tho, gonna install CM9 as soon as they fix stuff.
Sent from my GT-I9100 using xda premium
boba23 said:
Great news, I hope Team Hacksung will be able to fix the non-working Stuff using those sources. Video Recording, GPS half-working etc. are still too many show stoppers for daily usage in my eyes.
boba
Click to expand...
Click to collapse
my understanding is all they were waiting on was for the source to drop and it's doable!
IakobosJ said:
What an informative thread!
It's nice to see they have been released though
Direct link for anyone interested:
Download here
Click to expand...
Click to collapse
Oh come on... . Celebrate!
Sent from my GT-I9100 using xda premium
plessh BURNER
Late to the party!
dwd3885 said:
my understanding is all they were waiting on was for the source to drop and it's doable!
Click to expand...
Click to collapse
Install the GPS fix file for CM9 and it works perfectly.
They didnt even released official ICS for my region xD
Click to expand...
Click to collapse
Same here. Brazil, ZTA... not even an announcement for a far away release of ICS.
I hope Samsung hasn't hidden any secrets away from the released source code (like code to very specific drivers). If they have, having the sources won't suffice for a properly working ICS Galaxy S 2.
on the other hand, this may be an indication that Samsung hasn't been able to correct bugs still present in their pseudo-official ICS release, and this is their last resort: release the code so that the developers community can fix bugs Samsung hasn't be able to fix. Not that Samsung didn't have to make such release - they should and it is high time they do so.
Simonetti2011 said:
Same here. Brazil, ZTA... not even an announcement for a far away release of ICS.
I hope Samsung hasn't hidden any secrets away from the released source code (like code to very specific drivers). If they have, having the sources won't suffice for a properly working ICS Galaxy S 2.
on the other hand, this may be an indication that Samsung hasn't been able to correct bugs still present in their pseudo-official ICS release, and this is their last resort: release the code so that the developers community can fix bugs Samsung hasn't be able to fix. Not that Samsung didn't have to make such release - they should and it is high time they do so.
Click to expand...
Click to collapse
We know for a fact that there are bugs that Samsung is too clueless to notice/fix... But they are also too clueless to pull the fixes from the community.
See the fuel_alerted wakelock bug for example... Fixed for around 6 months by the community, still broken in Samsung kernels.
WTF!! really
this is great news.. wow cant wait for the fully working AOKP release
awesome, might now be able to get a decent kernal...and CM9 fully working on this bad boy!
Finally
I've been waiting for this so i can finally change to ICS (CM9) once everything is fixed
i feel like some one give me a million dollar
i hope we will got soon stable aosp and akop
i9100 ICS Update 4 sources on github:
https://github.com/myfluxi/xxICSKernel
Fork away.
Sweet - looking forward to some proper hardware acceleration on CM9! Thanks guys!
coolius said:
Sweet - looking forward to some proper hardware acceleration on CM9! Thanks guys!
Click to expand...
Click to collapse
Proper hw acceleration? What do you mean?
Sent from my GT-I9100 using xda premium
iamnotkurtcobain said:
Proper hw acceleration? What do you mean?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I think he meant video hw acceleration, but correct me if i'm wrong
New Kernel with better touchscreen would be nice. And faster system, smoother and battery friendly . Yahooooo
Sent from my GT-I9100 using xda premium
So with this, we might see CM9 with working/bugfree camera/video recording?
WOOT! Fully working AOSP ROM, here we come!
http://rootzwiki.com/news/_/article...-jelly-bean-source-is-now-being-released-r955
http://www.androidpolice.com/2012/07/09/android-4-1-jelly-bean-released-to-aosp-right-now/
Damn it you beat me to the punch lol
Sent from my SGH-I747M using Tapatalk 2
CM10 soon!!!!!!
Sent from my SGH-T999 using xda premium
hopefully we get CM9 support first
lets see how fast we see something for s3
MMontanez347 said:
hopefully we get CM9 support first
Click to expand...
Click to collapse
Why would they make CM9 for this phone when JB source is released? Lol that makes absolutely no sense.
Sent from my SGH-T999 using xda premium
Serious_Beans said:
Why would they make CM9 for this phone when JB source is released? Lol that makes absolutely no sense.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I believe it was said that jb code is very similar to ics. Cm9 is very close for us. A stable cm9 to cm10 would probably be faster than cm10 built from scratch. Just a guess though, I'm not a dev.
Sent from my GS3
Restola said:
I believe it was said that jb code is very similar to ics. Cm9 is very close for us. A stable cm9 to cm10 would probably be faster than cm10 built from scratch. Just a guess though, I'm not a dev.
Sent from my GS3
Click to expand...
Click to collapse
Nah I mean working off of CM9 would make sense if they could just merge the changes but I doubt it would officially be released just for them to release CM10 after that.
Sent from my SGH-T999 using xda premium
MMontanez347 said:
hopefully we get CM9 support first
Click to expand...
Click to collapse
I really hope we get CM7 before that
/sarcasm
really? why would you want the outdated one?
The CM team is merging the update as we speak. I think we will probably just get CM10 and not CM9 first (could be wrong though)
Sent from my SPH-L710 using xda app-developers app
We will get CM10 before CM9. All development on CM9 is being ceased after version 1.0.0. Just be patient, the source was uploaded something like 2 or 3 hours ago.
I think we will have something by next week
razorseal said:
I think we will have something by next week
Click to expand...
Click to collapse
I think we'll have something by tomorrow morning.. ;-)
Joking aside, this is cool to see.
Sent from my SPH-L710 using xda premium
jsmcmahon89 said:
I think we'll have something by tomorrow morning.. ;-)
Joking aside, this is cool to see.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Joke? don't underestimate the developers on THIS phone, of all phones ) I'm gonna definatelly keep an eye on these forums. if nothing else i expect someone starting a WIP thread, an AOSP built rom, most likely not fully functional ofcourse, but compiled enough to boot up, just to give us a taste while development begins in earnest
This is just what was needed to jump-start development for the SIII
I'm curious, with Verizon's S3 flashing abilities currently being limited to roms stripped of kernels, how will this affect a jellybean rom? Is the ics kernel the same as the jb kernel?
Just rambling here, no disrespect intended and none meant at all just want to learn as much as possible....ICS source has been available the whole time, why wouldn't we have seen a CM9 build if it were that simple (as to have source)? Just cause source for 4.1 is out, it is going to make it that much easier to build an AOSP rom now? Again just trying to learn I know people are pretty snappy at questions like these, lol.
Sent from my LG-P999 using xda premium
mt3g said:
Just rambling here, no disrespect intended and none meant at all just want to learn as much as possible....ICS source has been available the whole time, why wouldn't we have seen a CM9 build if it were that simple (as to have source)? Just cause source for 4.1 is out, it is going to make it that much easier to build an AOSP rom now? Again just trying to learn I know people are pretty snappy at questions like these, lol.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Reason people are saying that we could see CM10 soon is because the CM team think the code should be able to merge right into what they have with CM9, and not break that many things. With CM7 to CM9, they had to basically do everything from the ground up again because ICS was such a huge update over GB. Now JB isn't that big of an upgrade over ICS, in a way it is, but in a way it isn't. Sorry if that sounds confusing.
bigant262 said:
Reason people are saying that we could see CM10 soon is because the CM team think the code should be able to merge right into what they have with CM9, and not break that many things. With CM7 to CM9, they had to basically do everything from the ground up again because ICS was such a huge update over GB. Now JB isn't that big of an upgrade over ICS, in a way it is, but in a way it isn't. Sorry if that sounds confusing.
Click to expand...
Click to collapse
That's easy to understand, and not what I'm asking... what you are saying is its easy to incorporate 4.1 to 4.0, just like it was easy to go to 2.2 to 2.3... I'm asking why is everyone so excited to get 4.1 AOSP, when we don't even have 4.0 AOSP?
Sent from my LG-P999 using xda premium
mt3g said:
Just rambling here, no disrespect intended and none meant at all just want to learn as much as possible....ICS source has been available the whole time, why wouldn't we have seen a CM9 build if it were that simple (as to have source)? Just cause source for 4.1 is out, it is going to make it that much easier to build an AOSP rom now? Again just trying to learn I know people are pretty snappy at questions like these, lol.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I am no dev, but heres how i understand it works;
we start with an announcement of an OS, this is done generally at Google I/O or a Nexus Event, in this case was Google I/O.
On the announcement day, devs receive the SDK; Software Development Kit.
This is released to allow the devs to begin making apps that match and run on the new OS. However, aspiring rom devs then begin to build a rom off the released SDK, generally called an sdk port.
These tend to be made simply to give us an idea of how the system would work and function, and generally might boot up and have a couple working things, but major things tend not to function because the SDK is not made for that.
Then comes the Source code, this is the real deal, it is full code of the system, code that can then be compiled to produce a fully working system, or nearly fully working. Only thing that remains missing is proprietary drivers and such, these tend to be the things specific to each phone, files that would make particular chips work, particular functions, the specific phone kernel, etc. but once you have the source code, you're over 80% done as far as having the resources needed to develop a full rom. at this stage, some devs can produce a fully working, stellar rom, but it will take quite a bit more work than devs who choose to wait for the final stage
Then comes the OTA. this is where all the device-specific stuff comes to the devices, and devs have the absolute and complete freedom to produce a fully working, better than stock, experience. This is where roms flood the dev forums.
So as far as not having AOSP yet, and now this is our chance at AOSP? No, thats not why we dont have AOSP. we dont have it cause no one built it yet; the Touchwiz UX is sooo integrated in the system that untangling and taking it all out is a long and drawn out process, and theyd need to deconstruct what we currently have, take out elements of touchwiz until its all clean, all the while making sure it doesnt break anything else.
but getting the jellybean source code propels devs because now this is a new OS, a new AOSP with its own new interesting properties. and because Jelly bean is a small update compared to ICS, now that we have source code, many of the device specific stuff wont be broken by implementing jellybean code into it, therefore building a Jellybean rom is a faster path to AOSP than untangling the current ICS for Galaxy S III
Does that make sense?
mt3g said:
That's easy to understand, and not what I'm asking... what you are saying is its easy to incorporate 4.1 to 4.0, just like it was easy to go to 2.2 to 2.3... I'm asking why is everyone so excited to get 4.1 AOSP, when we don't even have 4.0 AOSP?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
AOSP in this case is talking about the actual Android Open Source Project. so it is a bunch of code. so why are we excited? we've had ICS AOSP code for nearly a year now, what we dont have is AOSP roms. building an ICS AOSP rom is much harder than building a JB Rom, and we currently have icecream sandwich on the SIII even if its touchwized, and undoing touchwiz is quite a bit of work. but Jellybean...Oh Jellybean, now we got the source, we will start getting that baby soon and it'll boost dev on these devices. make sense?
mt3g said:
That's easy to understand, and not what I'm asking... what you are saying is its easy to incorporate 4.1 to 4.0, just like it was easy to go to 2.2 to 2.3... I'm asking why is everyone so excited to get 4.1 AOSP, when we don't even have 4.0 AOSP?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Not sure if you were trying to come off rude or not, but people are excited because its the newest update, duh. Reason being we don't have 4.0 AOSP is because the phone hasn't been out that long for the US carriers.