No clue if this kernal will help the eris world out. but just wanted to post it just in case:
from:
http://developer.htc.com/
http://dl4.htc.com/RomCode/Source_and_Binaries/legend-MR-2.6.32-g732a780.tar.gz
I believe(may be wrong) tenzo and tazz are working on this kernel right now. Trying to back port to the .29 kernel. If they can get it working it should fix the only remaining issues with sense froyo roms, the camera and bt audio.
Sent from my ERIS using XDA App
The 2.6.32 kernel source is out for several devices now. It is my understanding that we can use this two different ways...
1) use one of the 2.6.32 kernels as a base and forward port the Eris specific stuff from 2.6.29 to the new base
2) use the Eris 2.6.29 kernel as a base and backport any fixes from the 2.6.32 kernels
It seems to me that #2 is mostly what's going on now, although there has been some work on the Hero CDMA with using the Wildfire 2.6.32 kernel as a base.
Some other devices actually have 2.6.34 and 2.6.35 kernels, but until we get a kernel dev with the knowledge, time, and motivation to do such things... We are stuck with grabbing commits from other kernel devs using method #2.
Again, this is how I understand things. I might be wrong, but I don't think so.
Digging around in the kernel code is good, geeky fun. I've learned a lot just by jumping in over and over again and not worrying about how much I know or don't know at any given time.
gnarlyc said:
The 2.6.32 kernel source is out for several devices now. It is my understanding that we can use this two different ways...
1) use one of the 2.6.32 kernels as a base and forward port the Eris specific stuff from 2.6.29 to the new base
2) use the Eris 2.6.29 kernel as a base and backport any fixes from the 2.6.32 kernels
It seems to me that #2 is mostly what's going on now, although there has been some work on the Hero CDMA with using the Wildfire 2.6.32 kernel as a base.
Some other devices actually have 2.6.34 and 2.6.35 kernels, but until we get a kernel dev with the knowledge, time, and motivation to do such things... We are stuck with grabbing commits from other kernel devs using method #2.
Again, this is how I understand things. I might be wrong, but I don't think so.
Digging around in the kernel code is good, geeky fun. I've learned a lot just by jumping in over and over again and not worrying about how much I know or don't know at any given time.
Click to expand...
Click to collapse
Ok, so why don't you make us a 2.6.32 Kernel?
workshed said:
Ok, so why don't you make us a 2.6.32 Kernel?
Click to expand...
Click to collapse
I think his point is that that's not what we're doing. We're backporting.
workshed said:
Ok, so why don't you make us a 2.6.32 Kernel?
Click to expand...
Click to collapse
Ok, so why don't you... Oh, nevermind.
Originally Posted by Hungry Man
I think his point is that that's not what we're doing. We're backporting.
Click to expand...
Click to collapse
workshed is just pestering me.
I have actually forked the cm 2.6.35 kernel and looked at it and played with it a little. The issue is like with most things in life: time and motivation. As time goes on and Android progresses on to newer version, someone might have to do something like this in order to keep the Eris up to date.
I would love to work that out. It's going to be time consuming even for someone who has the knowledge and experience doing it. Unfortunately, I'll probably be adding a programming class to my schedule in January, so I'll have less Android time. Fortunately, it's a C programming class, so maybe by May I'll have a better understanding of the kernel source! (And, I'll have my Eris at least through Oct. of next year when I get my upgrade pricing.)
Rock on!
Hungry Man said:
I think his point is that that's not what we're doing. We're backporting.
Click to expand...
Click to collapse
Man, I get no respect.
Backporting is much easier and really the most appropriate engineering approach. Let's just say the other way around is a more hackish approach.
I guess I'll see what I can do on seeing what can be done with getting performance based aspects into .29.
Thanks for putting this link up. Didn't know work was already being done. You guys rock!
hakkeshou said:
Backporting is much easier and really the most appropriate engineering approach. Let's just say the other way around is a more hackish approach.
I guess I'll see what I can do on seeing what can be done with getting performance based aspects into .29.
Thanks for putting this link up. Didn't know work was already being done. You guys rock!
Click to expand...
Click to collapse
If you look at the source for the Decafuct kernels -
https://github.com/Conap30/htc_kernel_desirec_cfs
https://github.com/Conap30/htc_kernel_desirec_bfs
You'll see that is what Conap, Decad3nce, etc. have been doing. There are also bits like camera fixes, for instance...
I guess I'm pointing those out because they might be a better place to start than starting with stock, unless you just like starting fresh. (I do when I really know what I'm doing.)
Thanks for helping!
Related
Hi guys, reading up on the Eris a little (I have a Moto Droid as my main phone). Got it rooted with 2.1 and flashed over Evil Eris and the LWP/Launcher2 updates and it seems pretty good so far! My question is when is overclocking going to be coming to this phone? Had my Droid clocked at 1.25GHz and it was rockin'! I didn't see a thread on it here (yes, I did search!) so I thought I would make one.
Thanks!
We need HTC to release the 2.1 kernel source first. Can't do any overclocking without that.
Send them an email to nag them.
Apparently No one has modified the system kernals on anything so far, so over clocking isn't available yet... I'm sure a dev is working on it though...
GrdLock said:
We need HTC to release the 2.1 kernel source first. Can't do any overclocking without that.
Send them an email to nag them.
Click to expand...
Click to collapse
you know it.
Of course the .27 kernel source is available, we've tried that kernel with 2.1 and it doesn't work right, and would take a lot of work to get working right, then more work to overclock. Not worth it really. We need the newer .29 source.
In the weeks ahead I will backport all the drivers from .29 to .27 needed to make it all but camera fully functional as I did with the heroc and have began doing for the gsm hero. Overclockin to 700mhz is possible for the turbo msm7k devices. I have a patch to enable it but there is some sort of conflict in the kernel that sops it from booting. Ramconsole shows it setting the desired clocks but then that's just the end of it. No more messages after that. The source is proven to work on all msm7k CPUs and it just seems to have an issue with something HTC added to our source. I haven't had much time to play with it but I've started a thread on it in the cdma hero forum. U can check there for more details on it. The patch I posted will apply clean to the Eris kernel source and all instructions are there for how to set it up. Anyone who wants to try and see what's causing it not to boot is welcome to. All I ask OS u post it findings in that thread as I would like to get it working and I always share my soutce, findings, and work. I just ask for others to do the same.
source code is easier than you might think
ok since android is linux and therefor open source htc is law bound to give you any source code you want as long as you ask them so if you really want it all you have to do is request it
rrmimms said:
ok since android is linux and therefor open source htc is law bound to give you any source code you want as long as you ask them so if you really want it all you have to do is request it
Click to expand...
Click to collapse
But, if the version isn't officially released, in regaurds to the Eris, do they still have to release that sourse code?
trav473 said:
But, if the version isn't officially released, in regaurds to the Eris, do they still have to release that sourse code?
Click to expand...
Click to collapse
Just wait maybe 2 days, it will apparently be released very soon.
CPCookieMan said:
Just wait maybe 2 days, it will apparently be released very soon.
Click to expand...
Click to collapse
Supposedly the Hero update will hit April 26th. At least that's what engadget says, so we should also have our update around that time. My guess would be either the same day or slightly later because they keep referring to the Hero and not the Eris.
sms440 said:
Supposedly the Hero update will hit April 26th. At least that's what engadget says, so we should also have our update around that time. My guess would be either the same day or slightly later because they keep referring to the Hero and not the Eris.
Click to expand...
Click to collapse
i would say with in a week
the latest leak 3/24 is solid its release material if you ask me
i dont see vzw taking much longer than a week
jamezelle said:
i would say with in a week
the latest leak 3/24 is solid its release material if you ask me
i dont see vzw taking much longer than a week
Click to expand...
Click to collapse
I sure hope so.
ok sorry if this is going off topic but i was just curious as to if when overclocking is possible if it is dangerous or risky to overclock i heard u can burn out ur phone if u overclock it too much.
Dizzy_Dez said:
ok sorry if this is going off topic but i was just curious as to if when overclocking is possible if it is dangerous or risky to overclock i heard u can burn out ur phone if u overclock it too much.
Click to expand...
Click to collapse
that is possible with most things your overclock. you have to find a nice balance between temp, voltage, and speed. Generally, overclocked cpus tend to have a shorter lifespan. I am not sure on the eris overclocking time frame. I think we need the kernel first?
ch4sethe5un said:
that is possible with most things your overclock. you have to find a nice balance between temp, voltage, and speed. Generally, overclocked cpus tend to have a shorter lifespan. I am not sure on the eris overclocking time frame. I think we need the kernel first?
Click to expand...
Click to collapse
yeah the cpu in the eris is the same as the hero cpu. ive been working on overclocking the heroc for some time now. the truth is that it can be overclocked to 700mhz max and winmo guys are already doing this. they found a sweet spot with our same cpu in their devices around 600mhz some go a little more. ive been usingtheir work along with my own skills and trying to get it working on native android devices. such as the hero and the eris. its a pain but i believe it can be done. im using the .27 kernel source for the heroc btw. ive managed to port all but the camera driver from .29 to .27. making itfully functional except camera. my hope is to get this working in .27 and possibly merge my changes into .29 6 months from now when HTC feels froggy anyhow yeah u can go and view all my threads ive started and a older patch is on my OC thread, in case anyone here has some C skills. fel free to contact me if u have any questions on it. i havent released my current patch as it isnt finished and im not so sure itll do much more then the one i posted on my thread.
toastcfh said:
yeah the cpu in the eris is the same as the hero cpu. ive been working on overclocking the heroc for some time now. the truth is that it can be overclocked to 700mhz max and winmo guys are already doing this. they found a sweet spot with our same cpu in their devices around 600mhz some go a little more. ive been usingtheir work along with my own skills and trying to get it working on native android devices. such as the hero and the eris. its a pain but i believe it can be done. im using the .27 kernel source for the heroc btw. ive managed to port all but the camera driver from .29 to .27. making itfully functional except camera. my hope is to get this working in .27 and possibly merge my changes into .29 6 months from now when HTC feels froggy anyhow yeah u can go and view all my threads ive started and a older patch is on my OC thread, in case anyone here has some C skills. fel free to contact me if u have any questions on it. i havent released my current patch as it isnt finished and im not so sure itll do much more then the one i posted on my thread.
Click to expand...
Click to collapse
Awesome info! I was just wondering what it could be OC'd too if anyone knew. Good to know the same chip is in other phones so you know what they've pushed it too. What does it run stock? I don't think I've seen it posted anywhere.
So SetCPU doesn't work properly on the Eris, right? I had it running for a while but it always said min = 480, max = 528, no matter what I set it to. Also, the battery was draining FAST! It would die in about 10 hours. I turned it off today and it was at 80% battery left after 10 hours and I didn't notice any difference in performance.
piercedtiger said:
Awesome info! I was just wondering what it could be OC'd too if anyone knew. Good to know the same chip is in other phones so you know what they've pushed it too. What does it run stock? I don't think I've seen it posted anywhere.
Click to expand...
Click to collapse
528mhz is stock, 700mhz is max supported. Sweet spot seems to around 600mhz. Battery drain won't be a massive issue as long as we can still use freq scaling
toastcfh said:
528mhz is stock, 700mhz is max supported. Sweet spot seems to around 600mhz. Battery drain won't be a massive issue as long as we can still use freq scaling
Click to expand...
Click to collapse
thanks. That would speed things up a little.
Anyone know what effect this will have to games, and live wallpapers?
Hey guys, i kinda felt bad for you guys, how you guys still don't have a true aosp build (minus the crappy froyo sdk which isn't built for any target). so i decided to make you guys a kernel that should work on your phones. i'm only gunna supply the zImage for you guys, if you want to know how i got the touchscreen to work, all i did was take the drivers/input/touchscreen/synaptics_i2c_rmi.c from cm-kernel and put it into my kernel source. well devs, have fun with this. you guys can now make a real cyanogenmod or aosp rom. This kernel is OC'd at 768 mhz. I'm only gunna supply the zImage, you devs make this work for your roms
Thanks Toastcfh for getting overclock to work on msm7k android devices
Kernel
wlan.ko
darchstar said:
Hey guys, i kinda felt bad for you guys, how you guys still don't have a true aosp build (minus the crappy froyo sdk which isn't built for any target). so i decided to make you guys a kernel that should work on your phones. i'm only gunna supply the zImage for you guys, if you want to know how i got the touchscreen to work, all i did was take the drivers/input/touchscreen/synaptics_i2c_rmi.c from cm-kernel and put it into my kernel source. well devs, have fun with this. you guys can now make a real cyanogenmod or aosp rom. This kernel is OC'd at 768 mhz. I'm only gunna supply the zImage, you devs make this work for your roms
i will supply the wlan.ko to accompany this soon
darchroms.pocketdevelopers.com/zimages/zImage
Click to expand...
Click to collapse
thanks man
Thanks man
I was about to start on this.
This will make my job million times easier.
btw,
Is this cm kernel you're talking about the one that is on your github?
The work is appreciated!
Framework43 said:
Thanks man
I was about to start on this.
This will make my job million times easier.
btw,
Is this cm kernel you're talking about the one that is on your github?
The work is appreciated!
Click to expand...
Click to collapse
cyanogen-kernel. its the one from his github
much appreciated Darch.
darchstar said:
cyanogen-kernel. its the one from his github
Click to expand...
Click to collapse
********************
hmmmmmmmmmm
oh man, now I can smell true AOSP cooking up right now somewhere in here... time to get rid of those chunky SenseUI. Dont get me wrong, There's nothing wrong with Sense UI, it's matter of personal preference and I'm just old school from G1 and loyal fan of AOSP build.
ChillCola said:
You are here making noise, butthurt that your rom didnt hit the news like Punkaos's did, and now you want to cause more drama. Don't thank him, his kernel doesn't work. The Touchscreen drivers are not right.
Are you violating the Linux license by not releasing the source? Kanging from 1000s of developers! How awful. I see no credit given!
Click to expand...
Click to collapse
ROFL, have you asked him for source code rather than jumping conclusion? people like you like to stir up drama
By the way I believe he did gave cyanogen credit, when he mention it's from his github....
ChillCola said:
You are here making noise, butthurt that your rom didnt hit the news like Punkaos's did, and now you want to cause more drama. Don't thank him, his kernel doesn't work. The Touchscreen drivers are not right.
Are you violating the Linux license by not releasing the source? Kanging from 1000s of developers! How awful. I see no credit given!
Click to expand...
Click to collapse
why would i need to re-release source for your kernel. does that make sense. all i did was edit two files in the source. those files are on toastcfh's github. i don't need to re-release the source. that would be a waste of time and effort. please, if you don't like me, just pm me and we'll settle things.
also, i'm pretty sure this works unless i forgot to recompile your source after i changed the file
has anyone else tried it besides the preteen who blatantly has some sort of bias against me?
Thanks darchstar! I've always been envious of your AOSP roms.
alexhendershott said:
Thanks darchstar! I've always been envious of your AOSP roms.
Click to expand...
Click to collapse
AOSP Eclair is done
Wait for it soon
Framework43 said:
AOSP Eclair is done
Wait for it soon
Click to expand...
Click to collapse
so that preteen was wrong then . alright cool. seems my work here is done
this is awesome news. Thanks darc for the kernel, and thanks framework for your aosp rom. can't wait to flash it!!!!
darchstar said:
so that preteen was wrong then . alright cool. seems my work here is done
Click to expand...
Click to collapse
Actually, its true what he says. The kernel doesn't fix the touchscreen.
Framework43 said:
Actually, its true what he says. The kernel doesn't fix the touchscreen.
Click to expand...
Click to collapse
oh, ok then, then you just followed my directions in what i did and it worked for you?
omg...omg..omg...... can we keep this thread drama free cola? I read to have a badass phone..not to imagine a sitcom.
darchstar said:
oh, ok then, then you just followed my directions in what i did and it worked for you?
Click to expand...
Click to collapse
I'm using whatever Kaos did to his kernel.
ChillCola said:
Bit cocky for someone who's #### doesn't work.
Click to expand...
Click to collapse
try it now, i updated it
ChillCola said:
Bit cocky for someone who's #### doesn't work.
Click to expand...
Click to collapse
I think I smell drama bomb in here... what do you expect? perfectly functional kernel on first try? LOL took me about 2-3 tries to get it working right for my Ubuntu.
ADVANCED USERS ONLY.
MAKE A BACKUP. THESE BUILDS COULD MAKE THE PHONE USELESS AS A PHONE!
SERIOUSLY. This is an unofficial CM7 build with cherry picks (from CM's Gerrit) of unfinished mods and/or broken code that is continually changing. New users should STAY AWAY FROM HERE. There is NO SUPPORT for this build, by myself or anyone else, so don't expect it. Do not file bug reports on the CM issue tracker from these builds. If you have to ask about compatibilities (which HBOOT version is needed, if A2SD scripts work, etc) you SHOULDN'T BE HERE. Don't PM me with silly questions, because they probably won't be answered.Rebased to CM source @ 8/1/11
I understand there is no support provided, and I will brick my phone by flashing this! OLD 3/31 BUILD
md5sum: 2d66e2e72e775ef736b0daa49ab22b6b
SHA1: dce98e947a08b52726fb0a2bf324e05ef2581b12
All credit goes to cyanogen & #teamdouche, I'm just a guy with a spare computer that learned how to compile and install Ubuntu without breaking Windows 8....
Credit to @RyanMacG for #Euroskank hosting!Some recent device related CM7 commits since last build:
None. At least on the official CM git.
Items from CM's Gerrit I have manually cherry-picked:
Not seeing any good ones. Look and suggest some!
If I stop using certain cherry picked commits all of a sudden, it's either: because they were merged, or the mod is based on older code than what is in CM currently and merge fails.
Known Bugs:
None apart from what the latest official slayher build has AFAIK
Build Status
Getting source for mecha related stuff and finding code to cherry pick. Should be built and uploaded by 9:30AM 8/2/11 CST
Please visit @cmsrc or CM's Gerrit for a complete list of commits.
Style of thread kanged from fitsnugly's Nexus One thread with permission.
So there are still a lot of issues with the gb build then? Or are they nearing a final working version? And by no means am i asking for an eta or anything just curious as to the progress being made.
Right now it runs. That's all I can say. But it is a lot better of a first build than other devices.... If I can get a working vendor built this weekend,we may see some progress(wifi working maybe....)
Sent from my ADR6400L using XDA Premium App
Same thing that was with my builds guys. Not worth it. Compile on your own for now if you really want this. There is no data, no calls, nothing. Until RIL is figured out, then CyanogenMod 7 is useless. I will be building full time once RIL is sorted but for now, these are useless other than having bragging rights. Not trying to discourage the OP but rather letting the masses know what's up.
otto888 said:
Right now it runs. That's all I can say. But it is a lot better of a first build than other devices.... If I can get a working vendor built this weekend,we may see some progress(wifi working maybe....)
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Might be able to get some help from @gearheadcustoms and @gridlock (Twitter) in fixing some of the issues you mentioned. A running CM7 nightly is progress. Sure this will be all fixed up within due time. Thanks to Euroskank, with corpses
ProTekk said:
Same thing that was with my builds guys. Not worth it. Compile on your own for now if you really want this. There is no data, no calls, nothing. Until RIL is figured out, then CyanogenMod 7 is useless. I will be building full time once RIL is sorted but for now, these are useless other than having bragging rights. Not trying to discourage the OP but rather letting the masses know what's up.
Click to expand...
Click to collapse
What's the issue with RIL?
i have a build from another dev that runs and i have gapps but no data so you cant sign in and wifi throws you into a bootloop...we needa kernel and i think we will finally have GB for the TB!
RIL: Radio Interface Layer.
The only reason that we have no data/text/calling/etc for CM 7. These threads are beating a dead horse. Wait until we have a working test build. I'll start building again once we have that.
The issue is, it's not open source.
ProTekk said:
RIL: Radio Interface Layer.
The only reason that we have no data/text/calling/etc for CM 7. These threads are beating a dead horse. Wait until we have a working test build. I'll start building again once we have that.
The issue is, it's not open source.
Click to expand...
Click to collapse
Right I thought RIL was made open source, guess not. But like all development, it starts with baby steps. Thank ProTekk
Man i cant wiat till yous figure this out...Im jonesin for sum GB
I think the title needs changing, and I really wish these builds were not posted if no one was willing to support them.
We end up getting the questions on irc, people don't read the disclaimers/warnings. The howto stealing sites (thats you A.T.) remove the warnings.
Maybe change title to "CM Builds - DATEHERE - NON-FUNCTIONAL" so less ppl will mess with it.
So we need to find the RIL files leaked? Or how do you get them?
andrew53517 said:
So we need to find the RIL files leaked? Or how do you get them?
Click to expand...
Click to collapse
You give the devs time to RE them, and write new ones.
jcase said:
You give the devs time to RE them, and write new ones.
Click to expand...
Click to collapse
Oh gotcha. So they have to make them compatible. That makes more sense. Now the closed source comment makes sense.
Thunderbolt Rooted!
This is absurd. Mods should lock this thread until we get a working rom.
No offense... but why? This thread is misleading, this thread will cause noobs too eff up their sh*t (despite your clearly stated warnings, they will not take them seriously), this thread is utterly useless because CM7 is not working, CM Parts are not working, RIL is not working...
Flashing this will make your phone useless (just like this thread).
Besides, there are already threads dedicated to compiling daily builds of CM7. Those threads have been put on hold (like they should) until CM7 is ready to be compiled. Even then, many people will flash extremely early builds of CM and wonder why certain functionality is missing or why x,y, and z does not work.
The underlying point is that this thread is going nowhere fast and will only cause problems. At least wait until the RIL is re-engineered and working.
Thank you.
Prrrooo sup d; ?
Sent from my ADR6400L using XDA Premium App
nerogold said:
Prrrooo sup d; ?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Not much back full time again
Sent from my ADR6400L using XDA Premium App
Good to see .anxious to flash cm7.
Sent from my ADR6400L using XDA Premium App
http://forum.xda-developers.com/showthread.php?t=1073930 - the original thread
https://github.com/doixanh/X8Features - the github source
Are there any DEVs willing to compile this in there ROM (lookin at you ACS) lol I have wanted this so badly, but am unwilling to take the performance hit that ee03 causes compared to SRF 1.1.1.
Dont take the dive to gb
Even though the devs try hard some things just cannot be
Like taking the crap**** gb leak and turn it into gold
Sent from my Nexus S 4G using XDA Premium App
gtuansdiamm said:
Dont take the dive to gb
Even though the devs try hard so things just cannot be
Like taking the crap**** gb leak and turn it into gold
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
This makes no sense? The developer dioxanh got this to work perfectly on froyo and put the source on github for other DEVS to compile for there ROMs. It can be because he has done it
I meant that the gb link is über slow and it probably wont get better till the next leak
Sent from my Nexus S 4G using XDA Premium App
All the Epic ROM's with the exception of MIUI and CM7 are NOT compiled from source code.
They are merely customizations and hacking based off of the compiled libraries. It would likely be impossible to reverse engineer this into any of the ROM's. It would need to be done in Smali... if that's even possible..
Syndicate is in fact compiled from source if I'm not mistaken, that's why they always wait for a few days source leaks to release.
TheDub said:
They are merely customizations and hacking based off of the compiled libraries. It would likely be impossible to reverse engineer this into any of the ROM's. It would need to be done in Smali... if that's even possible..
Click to expand...
Click to collapse
Look all I know is that this DEV made it possible to implement into custom ROMs for froyo. It says so clearly in the forum I posted if you had bothered to read it at all.
Actually read it .. Good work on dev for doing this! .. But it must be cooked into roms only and only works for a few roms
Sent from my SPH-D700 using XDA Premium App
I know Impaler and Mystery and others are busy workin on 1.2, and It would be cool if they lookd into implementing this into it.
jspsuperman said:
Look all I know is that this DEV made it possible to implement into custom ROMs for froyo. It says so clearly in the forum I posted if you had bothered to read it at all.
Click to expand...
Click to collapse
I did "bother" to read it. It's Froyo source code to implement this feature. We don't have 100% of Samsungs source code for Froyo/Eclair/Gingerbread, they don't release it.
We only receive the kernel source code. This could only be baked into a Froyo based AOSP ROM which other then the very dated CM6 we do not have.
The kernel source code and the entire operating system (AOSP) are two completely different things, and the code to make this work isn't in the Kernel it's in the Framework.
ACS's ROM is not AOSP.
AOSP: Android Open Source Project - I'm using it to reference having the entire operating system's source code available, not just the kernel.
I wasnt aware that only the kernal source was released. What a bummer if a sony X8 can do this but our epic cant without gingerbread
Yeah just the way it is...
Most phones don't have 100% complete source drops, the popular two phones that do of course are the Nexus One and Nexus S, this is why the Nexus phones so easily get ROM's like CyanogenMod working. With the Epic and Galaxy S developers are forced to "rewrite" lots of code to get things interfacing with the Samsung proprietary drivers properly.
If we had 100% of the source code I don't doubt ROM's would be very different today, there would have also been a official CyanogenMod by now I'm sure.
If you want to see for yourself what Samsung releases you can go to:
https://opensource.samsung.com/
Do a search for I9000 for example and download one of the releases (I looked at I-9000-Opensource.zip)
You will see a few files in there.. one labeled kernel, the other eclair.
The kernel one is obvious, the eclair one contains only the hardware libraries.
So unfortunately, this really isn't possible in any of our existing Froyo ROM's, except CM6.
PS: I9000 is the model number for the European Galaxy S.
jspsuperman said:
I wasnt aware that only the kernal source was released. What a bummer if a sony X8 can do this but our epic cant without gingerbread
Click to expand...
Click to collapse
Don't mess with TheDub
qbking77 said:
Don't mess with TheDub
Click to expand...
Click to collapse
Apparantly lol That sucks but I guess gingerbread will be official soon enough then we will have somthin else kickass from U ACS folk lol
063_XOBX said:
Syndicate is in fact compiled from source if I'm not mistaken, that's why they always wait for a few days source leaks to release.
Click to expand...
Click to collapse
This is not true, just so you know.
Sent from my SPH-D700 using XDA App
After that many people ask me to compile a version of phenomenal (an undervolted speedmod kernel) for galaxy note, I decided to do it.
So, I HAVEN'T GALAXY NOTE! For this reason I need your help.
First I'd like know your undervolted experience, to know what voltages do you use?
Thanks!
fenomeno83 said:
After that many people ask me to compile a version of phenomenal (an undervolted speedmod kernel) for galaxy note, I decided to do it.
So, I HAVEN'T GALAXY NOTE! For this reason I need your help.
First I'd like know your undervolted experience, to know what voltages do you use?
Thanks!
Click to expand...
Click to collapse
Nice...I was using your kernel on sgs2...
For gingerbread?
robertberma said:
For gingerbread?
Click to expand...
Click to collapse
indeed this kernel for gingerbread
When ics is around the corner? Gb is a dying rase, i hope this kernel is comming before ics than.
robertberma said:
When ics is around the corner? Gb is a dying rase, i hope this kernel is comming before ics than.
Click to expand...
Click to collapse
Considering the issues with emmc and stability, I would say that Sammy is not even close to providing a correct ICS rom.
Let them just release the drivers, after all here at XDA we have all the good devs to cook us a good set of kernels for TW or AOSP roms, don't we?
That is just wishful thinking of course;-)
Sent from the great Note
Please make one for ICS.
There's a missing hole in my device, it cries out for SmartAssv2 governor on an optimized kernel. (Frequency is 400Mhz under/1.4GHz over, we don't have the voltage option yet, sigh)
I use this daily (the ones that say current, the saved ones are the original voltages) with abyss kernel 100% stable and I usually set the min speed to 400MHz and Max to 1400MHz or 1700MHz depending on my needs.
I can lower all voltages by 0.025v but then I'll get a couple crashes a week so i prefer to keep the voltages just one step higher.
robertberma said:
When ics is around the corner? Gb is a dying rase, i hope this kernel is comming before ics than.
Click to expand...
Click to collapse
I agree. We really need some good ICS metals. Apart from the CM9 kernel and DAFUQ, I do not see anything else here.
And after Entropy's warning not to flash leaked kernels, I am beginning to wonder if there is some other good kernel for ICS ROMs.
We would be grateful if make this an ICS kernel. We can live with one less good GB kernel /methinks
Sent from my GT-N7000 using xda premium
gramessh said:
I agree. We really need some good ICS metals. Apart from the CM9 kernel and DAFUQ, I do not see anything else here.
And after Entropy's warning not to flash leaked kernels, I am beginning to wonder if there is some other good kernel for ICS ROMs.
We would be grateful if make this an ICS kernel. We can live with one less good GB kernel /methinks
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Does chinese leaks we must forget. Nothing wrong with thise kernels if you have a chinese Note. Look at sgs2 forum. Already samsung released there the sources and there are 5 ore more custom kernels. So samsung is doing a great job for them releasing so soon sources. We have to be patient and not start making cm9 with sources from sgs2. So stupid.
robertberma said:
Does chinese leaks we must forget. Nothing wrong with thise kernels if you have a chinese Note. Look at sgs2 forum. Already samsung released there the sources and there are 5 ore more custom kernels. So samsung is doing a great job for them releasing so soon sources. We have to be patient and not start making cm9 with sources from sgs2. So stupid.
Click to expand...
Click to collapse
True but SGS2 sales are at least four times more than that if the note. The note is like a flagship device but its not getting the best treatment yet. We can't expect the sources to be out before the official ICS release.
I am just happy we even have official CM9 support. The problem though, is because DAFUQ supports only TW ROMs :-| and we have no good kernels (except leak ones) for the AOSP/AOKP ROMs.
So much good ROM development here for AOSP. Yet, no real safe kernels for em yet. Pity!
He's back! Another robertberma anti-spirit comment.
Excuse me for the intro, but most of the work here at XDA started with hacking and making open sourced stuff out of closed source material.
Indeed we already have a few good GB kernels, and an additional developer on ICS would be greatly appreciated. ICS is coming soon, and considering the time spent on tuning a kernel, I think that it would be more productive to start working on an ICS kernel than on GB.
However if this GB kernel is a first step to get knowledge of the Note specifics and followed by an ICS one, it's all good.
Sent from the great Note
@fenomeno83
Forgive me if this question is really nooby.
Is it possible for a custom ICS kernel to support both TW and AOSP? Are their frameworks too different?
Most (or maybe all) of the GB kernels I see here are for GB. They may be themed but I still see the TW framework everywhere.
If possible, wouldnt it be nice to make a kernel that supports both?
sudisk said:
He's back! Another robertberma anti-spirit comment.
Excuse me for the intro, but most of the work here at XDA started with hacking and making open sourced stuff out of closed source material.
Indeed we already have a few good GB kernels, and an additional developer on ICS would be greatly appreciated. ICS is coming soon, and considering the time spent on tuning a kernel, I think that it would be more productive to start working on an ICS kernel than on GB.
However if this GB kernel is a first step to get knowledge of the Note specifics and followed by an ICS one, it's all good.
Sent from the great Note
Click to expand...
Click to collapse
Hahaha I think it will not help developing ics kernel by develop a gb kernel. I just say we have to be patient and wait for sourses to continue develop a ics kernel that is save. We have great devs for aosp and cm9 roms but there hands are tied behind there backs without sourses. Now they use stupid chinese **** thats not save. We getting of topic here.
Make this gb kernel fast and i hope he continue his work when ics comes out. And make a speedy ics kernel for sammy, aosp and cm9 roms. ONE KERNEL FOR ALL ROMS.
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
gramessh said:
@fenomeno83
Forgive me if this question is really nooby.
Is it possible for a custom ICS kernel to support both TW and AOSP? Are their frameworks too different?
Most (or maybe all) of the GB kernels I see here are for GB. They may be themed but I still see the TW framework everywhere.
If possible, wouldnt it be nice to make a kernel that supports both?
Click to expand...
Click to collapse
Yes look at sgs2 forum. They are loaded with does kernels for all roms.
robertberma said:
Now they use stupid chinese **** thats not save.
Click to expand...
Click to collapse
Ah, welcome back, Bobby.
I cannot even begin to tell you how we all missed your sunny disposition, bubbly personality, observant mind and
always original, refreshing and precise way of expressing your comprehensive thoughts.
chasmodo said:
Ah, welcome back, Bobby.
I cannot even begin to tell you how we all missed your sunny disposition, bubbly personality, observant mind and
always original, refreshing and precise way of expressing your comprehensive thoughts.
Click to expand...
Click to collapse
Missed you to and your startrek picture quote on every noob quastion.
robertberma said:
Missed you to and your startrek picture quote on every noob quastion.
Click to expand...
Click to collapse
I hase™ a quastion™ too! Where have you been dude?
Back to topic: The need for kernels are so relative to the users that need it.
Variety truly is nice.
Reb0rn said:
I hase™ a quastion™ too! Where have you been dude?
Back to topic: The need for kernels are so relative to the users that need it.
Variety truly is nice.
Click to expand...
Click to collapse
Banned for having two accounts. I am little bit Schizophrenic. Whaha
sudisk said:
He's back! Another robertberma anti-spirit comment.
Excuse me for the intro, but most of the work here at XDA started with hacking and making open sourced stuff out of closed source material.
Indeed we already have a few good GB kernels, and an additional developer on ICS would be greatly appreciated. ICS is coming soon, and considering the time spent on tuning a kernel, I think that it would be more productive to start working on an ICS kernel than on GB.
However if this GB kernel is a first step to get knowledge of the Note specifics and followed by an ICS one, it's all good.
Sent from the great Note
Click to expand...
Click to collapse
I do not see any anti- spiritism in his comment. He was saying the obvious fact
Sent from my GT-N7000 using xda premium
Moved To General
As this contains no development, it belongs in the general section.