[Kernel] Adam Kernel Development - Adam Android Development

I have the stock kernel source here: https://github.com/rothnic/Adam_Kernel
Pershoot's Gtab source with Adam additions is here: https://github.com/rothnic/gtab-2632
Once pershoot's source is confirmed working (currently it is compiling), we will be able to merge the adam changes into his main repo

So what new modifications do you think can be done now that we have this code? is this going to be more of a bonus for other tabs rather than the Adam?

Lord_alias said:
So what new modifications do you think can be done now that we have this code? is this going to be more of a bonus for other tabs rather than the Adam?
Click to expand...
Click to collapse
This is only really a bonus for the Adam. If we have the Adam specific code merged into pershoot's kernel, then as he works on it, we can continue to get his updates. Which means we don't have to manage two separate projects since the gtablet kernel is so close to the adam kernel.

Sweet, Should keep the Adam alive as long as the ROM does

the ROM is Over layer on kernel.....
so there is one kernel and many ROMs working with this same kernel....
kernel is important for tweaking bug fixing and so on.....
cheers

Thats awesome!! That means we will have overclocking, right?
also it will be easier to port ROMs from the G TAB (including CM)...
Keep up the good work!

rothnic said:
I have the stock kernel source here: https://github.com/rothnic/Adam_Kernel
Pershoot's Gtab source with Adam additions is here: https://github.com/rothnic/gtab-2632
Once pershoot's source is confirmed working (currently it is compiling), we will be able to merge the adam changes into his main repo
Click to expand...
Click to collapse
So awesome =]
Is Pershoot's kernel just for gingerbread or is he still working on a froyo version? Thanks

How hard would you suggest it would be to upgrade to a 2.6.38 kernel now that we have these "combined efforts"? It's just a matter of upgrading a Gingerbread kernel, right?

After the compiling is done, can I use it for my BEAST ROM ?

archanox said:
How hard would you suggest it would be to upgrade to a 2.6.38 kernel now that we have these "combined efforts"? It's just a matter of upgrading a Gingerbread kernel, right?
Click to expand...
Click to collapse
Hard.
10chars

rothnic said:
I have the stock kernel source here: https://github.com/rothnic/Adam_Kernel
Pershoot's Gtab source with Adam additions is here: https://github.com/rothnic/gtab-2632
Once pershoot's source is confirmed working (currently it is compiling), we will be able to merge the adam changes into his main repo
Click to expand...
Click to collapse
Which cross compiler are you using for this? Will CodeSourcery G++ Lite work? Also, is there a repo for the initramfs yet?

Related

AOSP eclair build from Samsung Vibrant Source code.

Hi all,
If anyone wants to play with this and let me know how it works feel free.Its the system directory from an AOSP eclair build using the Samsung Vibrant source download from the opensource website.I have no Vibrant myself I just built this as a test to see if it would build clean with no errors using the samsung files as a test for when the Epic 4g sources get released.Please feel free to use it in a rom or whatever you chose and post back if it works or not.
www[DOT]mediafire[DOT]com/?wytytv44odtdsdx
EDIT: This is not flashable! This is a stock /system filesystem from a build of AOSP android this is the base for a ROM not a complete ROM in itself.
Most likely it won't work cause Eugene is working from the aosp but is running into problems getting sound and camera to work.
I was just surprised it compiled the first run I saw another post where they were getting a lot of errors.And I figured there would be corrupt files I had a hell of a time extracting the archieve.
Sent from my SPH-M900 using Tapatalk
Thanks for posting that. I would like to have a look around but I wasn't sure where and what to grab.
www.mediafire.com/?wytytv44odtdsdx
heh
10char
Rhcp thanks for reposting a real link kinda sucks not being able to post them.
Sent from my SPH-M900 using Tapatalk
skeeterslint said:
Rhcp thanks for reposting a real link kinda sucks not being able to post them.
Sent from my SPH-M900 using Tapatalk
Click to expand...
Click to collapse
Not a problem. Post some more so you can update your OP.
Good work on the build. Did you build the kernel too?
rhcp0112345 said:
Not a problem. Post some more so you can update your OP.
Good work on the build. Did you build the kernel too?
Click to expand...
Click to collapse
There is no Kernel in a system image.
just got home, gonna dl and see what cooking
rhcp0112345 said:
Not a problem. Post some more so you can update your OP.
Good work on the build. Did you build the kernel too?
Click to expand...
Click to collapse
I haven't tried building the kernel yet but I pulled the intramfs from a vibrant and captivate kernel to compare them togther and see if there are any real differences which it seems there really isn't that I noticed.One thing I did notice though is that the samsung kernel sources don't build the initramfs into the kernel that I noticed.With the Samsung Moment the sources had a file to build the kernel modules and a couple other programs that went into the intramfs and it had the initramfs_list file hidden inside the source somewhere it doesn't seem like they did that with the vibrant kernel source.How do they expect you to build a kernel that requires an initramfs in it and not build it into the kernel during the compile?I am gonna tinker around and probably use the initramfs_list file from the Moment initramfs and just add in all the directorys and files that are in the vibrant/epic/captivated initramfs.
it gets stuck on "installing update"
my clockwork does that from time to time with any zip file, just pull the battery and retry
Thats just a raw /system filesystem it would need to be cooked into a rom for it to be flashable.I threw it up there for someone to try and cook a rom out of it.
Has anyone had the problem when trying to compile a kernel that the suppiled build script doesn't build the modules?I can get the zImage to build but it won't build the modules at all.I would like to at least get it built with the samsung script and get the modules built then use the modules in the initramfs and try to build it with another script with the initramfs in the kernel.
skeeterslint said:
Thats just a raw /system filesystem it would need to be cooked into a rom for it to be flashable.I threw it up there for someone to try and cook a rom out of it.
Has anyone had the problem when trying to compile a kernel that the suppiled build script doesn't build the modules?I can get the zImage to build but it won't build the modules at all.I would like to at least get it built with the samsung script and get the modules built then use the modules in the initramfs and try to build it with another script with the initramfs in the kernel.
Click to expand...
Click to collapse
same problem I had with building the kernel
chaoscentral said:
same problem I had with building the kernel
Click to expand...
Click to collapse
The captivate kernel builds with the samsung script with no problem modules and all, used the captivate script with the vibrant kernel source same deal builds the kernel but no modules.
Almost Done! http://twitpic.com/2et5cb
eugene373 said:
Almost Done! http://twitpic.com/2et5cb
Click to expand...
Click to collapse
You're out of your mind - in a good way. Vanilla has got to FLY on this thing, right?
eugene373 said:
Almost Done! http://twitpic.com/2et5cb
Click to expand...
Click to collapse
Thank you so much for your hard work Eugene! Now if only we can get a mod or someone to lock your threads so only you can update, I'm tired of having to explain adb push/pull to people over-and-over, so I know you must be too.
Cheers,
=)
eugene373 said:
Almost Done! http://twitpic.com/2et5cb
Click to expand...
Click to collapse
Eugene,
If I'm not mistaken...that's the stock home launcher for 2.2 isn't it? Or are you running adw/launcherpro
Sent from my SGH-T959 using XDA App

[Kernel][AOSP] Tiamat 1.1.4 | 2.6.35.14 | 10/4/11

​
AOSP Kernels for HTC's 8x50, 7x30, and 8x60 Devices
Also available for the Motorola Xoom​
Tiamat kernels are designed for use on all ROMs that are built from the AOSP source code. This includes ROMs built from MIUI, CyanogenMod, and others.
Tiamat receives no support for use with ROMs based on HTC's Sense - use at your own risk.
Click to expand...
Click to collapse
Tiamat Kernels​​
You can find full details about Tiamat Kernels at our website. The site is up and running and serves as a more centralized location to get updates, downloads, and changelogs for all Tiamat Kernels. There is no forum or Registration, it’s just a more convenient way to keep things organized as we work to add support for more devices.​
Click to expand...
Click to collapse
Support
Join the Tiamat Kernel developers on IRC at irc.freenode.net, #tiamat. Support and questions are generally handled faster there than the forums. You can easily join via webchat here.​
Click to expand...
Click to collapse
​
Special Thanks to:
toastcfh, slayher and the CyanogenMod team for the base kernels and everything else they do for the Android community
bcnice20 for generally being awesome
TeamWin for also generally being awesome
netarchy, chad0989, cuviper, and invisiblek for some great code
intersectRaven and redstar3894 for the Mjolnir compiler
JasonK75 for updating threads​
Click to expand...
Click to collapse
​
Quick Links​
Click to expand...
Click to collapse
8x50 Changelog
8x60 Changelog
7x30 Changelog
Downloads
FAQ
Source Code​
Finally ... a new kernel for cm7 ... thanks guys
EDIT: bro i can help you test if u want ... ur website says u need incS testers ... i am willing to contribute ..
Sent from my Incredible S using XDA App
Wi-Fi doesn't work~
vere850211 said:
Wi-Fi doesn't work~
Click to expand...
Click to collapse
Same, wifi cannot search any signals
vere850211 said:
Wi-Fi doesn't work~
Click to expand...
Click to collapse
Try 1.0.3 and let me know if the issue persists.
knightrocker said:
Finally ... a new kernel for cm7 ... thanks guys
EDIT: bro i can help you test if u want ... ur website says u need incS testers ... i am willing to contribute ..
Sent from my Incredible S using XDA App
Click to expand...
Click to collapse
I do need testers on this device. Hit me up on IRC (irc.freenode.net) in #tiamat. If you're not familiar with IRC, use http://tiamat-dev.com/web-chat/ to log in to the channel.
Hey, the desire s needs an AOSP kernel. It runs on the same processor as this phone (MSM 8255), so maybe you can make one........
If someone can tell me how to reflash the CM7 kernel (in case wifi bug still exists), I'd be happy to test this out also.
Would I just reflash the CM7 nightly I want to run, as (afaik) the kernel is packaged with it?
Yep ... reflash the nightly and you will hav the cm kernel again
Sent from my Incredible S using XDA App
Ok, well 1.0.3 has fixed the wifi issue. This puts you 1 step ahead of CM right now, as in the latest nightly the kernel was updated and wifi was broken in the process .
It's 245am here, so I will try and write more tomorrow. Just wanted to report that wifi is working .
shrome99 said:
Hey, the desire s needs an AOSP kernel. It runs on the same processor as this phone (MSM 8255), so maybe you can make one........
Click to expand...
Click to collapse
CM hasn't merged support for the saga (Desire S) in to their kernel yet, but the HTC source is out. I would love to add the device in with this series of kernels (and the lexicon -merge- when that source is out), but that isn't a project I can commit to without some testers or having the device.
If you're willing to test, let me know and I can work on it.
Cayniarb said:
CM hasn't merged support for the saga (Desire S) in to their kernel yet, but the HTC source is out. I would love to add the device in with this series of kernels (and the lexicon -merge- when that source is out), but that isn't a project I can commit to without some testers or having the device.
If you're willing to test, let me know and I can work on it.
Click to expand...
Click to collapse
Yes i am, and not just me, there's a bunch of people dying to have an AOSP kernel for the CM7 port. Check this - you'll find many enthusiasts here http://forum.xda-developers.com/showthread.php?t=1166867
Cayniarb said:
that isn't a project I can commit to without some testers or having the device.
If you're willing to test, let me know and I can work on it.
Click to expand...
Click to collapse
Hi Cayniarb
Count me in for Desire S kernel testing.
I would certainly be happy to test a Desire S kernel too. Using a stripped down Sense ROM right now because of the battery drain on the unofficial CM7 mod, but would love to switch to CM7 full time.
Have plenty of Linux experience and know my way around Android, ADB, fastboot / etc.
Cheers =)
Since this is quickly turning in to a Desire S thread...........
I have a built kernel for the device - but as I don't have it, I have no clue if it works. I'd rather not post a link for a test build like this publicly.
I have the code isolated in a branch away from the mainline (cm-like, really cm+ tbolt) branch for testing, but I see nothing that should make merging it in very difficult. Check it here: http://code.tiamat-dev.com/7x30/htc-kernel-msm7x30/commits/android-msm-2.6.35-saga
The best way to contact for testing is via IRC. If you're not familiar with it, I have a webportal for it setup on my site to make it easy: http://tiamat-dev.com/web-chat/
wonderful .
Can someone please tell me the difference between this kernel and the CM7 one?
Aodhan said:
Can someone please tell me the difference between this kernel and the CM7 one?
Click to expand...
Click to collapse
http://tiamat-dev.com/7x30-changes/
everything listed is a difference from cm7
Works great on MIUI 1.7.22 so far, fantastic work XD
Blodia said:
Works great on MIUI 1.7.22 so far, fantastic work XD
Click to expand...
Click to collapse
Yes, I'll second this. Am running MIUI with Tiamat 1.0.4 and Vipermod to undervolt, setcpu down to 650/192mhz and running on conservative governor. Experiencing great battery life, full stability, and the rom still runs smooth. Amazing job!

[KERNEL] {ADA} *NEW AOSP* v3.0.51 ZenSERIES v2 *BreakingGround* {Jelly Bean} [KERNEL]

Please stay tuned
Reserved
I heard this kernel is one of great kernel in GNex forum.
I'll flash it right away
Sent from my Nexus S using Tapatalk 2
Cool, I love flashing new releases
A new challenger appears! I'll have to try this out sometime in the near future, but it will be hard to tear me away from Marmite.
Sent from my Nexus S using xda app-developers app
Does not boot.
using latest CM10 nightly
Brishen said:
Does not boot.
using latest CM10 nightly
Click to expand...
Click to collapse
No Custom IOCTL stuff I guess..
Sent from my Nexus S using Tapatalk 2
Op does not Specify weather this Kernel is for,
CM Based roms
AOSP Based roms
AOKP Based Roms
I Tried it on Latest Paranoid Android (CM Based) and it black screens.
Is now compatiable with AOSP ROMS Only. I will have bbedward from post #2 look into some of the comments here. He is our kernel developer building blindly on this device
Thank you all for trying and posting your experiences, we will certainly get you fixed up!
Purian23
Thank you for your sharing.
purian23 said:
Should be compatible with all ROMS out there. Same as it is on the Nexus. I will have bbedward from post #2 look into some of the comments here. He is our kernel developer building blindly on this device
Thank you all for trying and posting your experiences, we will certainly get you fixed up!
Purian23
Click to expand...
Click to collapse
AOSP and AOKP based roms use the same Kernels but CM Based roms use different Kernels and will not work unless setup specifically for CM Roms.
This is 5.4 MB? Hmmm...need to see how it performs.
Tested this kernel. Overall snappy & fast with Ondemandx even at stock speeds. There is no bigmem support. This is very important for Nexus S due to low available memory. Screen colors look too yellow. This can be adjusted by user if Voodoo color is included. Inclusion of USB fast charge will give an added advantage.
anshumandash said:
Tested this kernel. Overall snappy & fast with Ondemandx even at stock speeds. There is no bigmem support. This is very important for Nexus S due to low available memory. Screen colors look too yellow. This can be adjusted by user if Voodoo color is included. Inclusion of USB fast charge will give an added advantage.
Click to expand...
Click to collapse
also no Crt Fix ..
Didnt work for me with a cm10.
raducux said:
Didnt work for me with a cm10.
Click to expand...
Click to collapse
will a cm10 version be available?
Its based on aosp source and was tested on crossbones ROM, I'll get the rest of you guys figureld out soon.
---------- Post added at 02:18 PM ---------- Previous post was at 01:22 PM ----------
Big Dog KMc said:
AOSP and AOKP based roms use the same Kernels but CM Based roms use different Kernels and will not work unless setup specifically for CM Roms.
Click to expand...
Click to collapse
I understand, looks like CM requires a kernel patch for this http://review.cyanogenmod.org/#/c/23541/
I was unaware as it was tested on an aosp based rom
We made a decision here, we're not going to support CyanogenMOD officially.
We will update the OP accordingly, it's just not desirable to maintain 2 builds for 1 device. The kernel should be fully compatible with AOSP/AOKP, and will be the kernel bundled with the CrossBones rom.
If you wish to use this kernel on CyanogenMod, you may build a copy yourself using herring_zen_defconfig and setting CONFIG_FOR_CYANOGENMOD=y . Keep in mind unofficial builds won't be officially supported by us. Please when building an unofficial kernel ALWAYS SET CONFIG_ZEN_VERSION_CODE=0. While it may not have any affect now, it may affect some userspace apps.
The kernel source is located here: https://github.com/AndroidDeveloperAlliance/ZenKernel_Crespo
We also provide a custom prebuilt GCC toolchain you can use here: https://github.com/AndroidDeveloperAlliance/ZenKernel_ARCH_armv7a_compiler
Only official builds are supported!
Thanks
bbedward said:
We made a decision here, we're not going to support CyanogenMOD officially.
We will update the OP accordingly, it's just not desirable to maintain 2 builds for 1 device. The kernel should be fully compatible with AOSP/AOKP, and will be the kernel bundled with the CrossBones rom.
If you wish to use this kernel on CyanogenMod, you may build a copy yourself using herring_zen_defconfig and setting CONFIG_FOR_CYANOGENMOD=y . Keep in mind unofficial builds won't be officially supported by us. Please when building an unofficial kernel ALWAYS SET CONFIG_ZEN_VERSION_CODE=0. While it may not have any affect now, it may affect some userspace apps.
The kernel source is located here: https://github.com/AndroidDeveloperAlliance/ZenKernel_Crespo
We also provide a custom prebuilt GCC toolchain you can use here: https://github.com/AndroidDeveloperAlliance/ZenKernel_ARCH_armv7a_compiler
Only official builds are supported!
Thanks
Click to expand...
Click to collapse
Looks like I won't be trying this kernel, then.
Stay tunes for V2, thanks for the feedback from some of you. Added bigmem, voodoo color support, usb fast charge support, some more lowmemorykiller upstream updates, and also cifs+fuse FS support.
ScOULaris said:
Looks like I won't be trying this kernel, then.
Click to expand...
Click to collapse
We're offering this to the community with no expectations that you use it, but for those who do use it we want them to be completely satisfied.
If it doesn't work for you, then I encourage you to use something from one of the other great development teams out there.
I thought of a couple solutions: 1.) creating 2 kernel builds, 2.) creating a sysfs interface so CM users could flash an init script that'd enable the CM ioctl's. Basically it comes down to this - neither solution is up to my standards for now.

SGS4 Kernel Source Available

http://www.androidpolice.com/2013/0...or-sprint-and-us-cellular-galaxy-s4-variants/
Let the custom ROMs begin.
agentfazexx said:
http://www.androidpolice.com/2013/0...or-sprint-and-us-cellular-galaxy-s4-variants/
Let the custom ROMs begin.
Click to expand...
Click to collapse
roms have nothing to do with kernel source, just kernels
luckily enough the other variants had kernel source out already and were close enough so i already know the new tricks samsung included it the source
shabbypenguin said:
roms have nothing to do with kernel source, just kernels
luckily enough the other variants had kernel source out already and were close enough so i already know the new tricks samsung included it the source
Click to expand...
Click to collapse
Kernel sources do indeed help in ROM creation though. Helps so one does not have to hack up a kernel to use.
agentfazexx said:
Kernel sources do indeed help in ROM creation though. Helps so one does not have to hack up a kernel to use.
Click to expand...
Click to collapse
you can make a rom without ever touching the kernel. and without kernel source all you can do is unpack it and edit the text files in the ramdisk. its not really hacking.

[REQ] Lollipop Kernel

Can someone create a modified kernel for Cyanogenmod12 24.11.2014 build, or make Williams kernel working for the same rom? Something with the same fuctions as Williams Kernel (oc,fauxsound and so on). Thanks in advance.
fantamadnesss said:
Can someone create a modified kernel for Cyanogenmod12 24.11.2014 build, or make Williams kernel working for the same rom? Something with the same fuctions as Williams Kernel (oc,fauxsound and so on). Thanks in advance.
Click to expand...
Click to collapse
Can someone also produce a fully working non crashing lollipop build by next tuesday please.
/sarcasm off
Asking for something like this is quite cheeky really, if someone like pecora is working on a lollipop kernel then they will but it takes a lot of work and effort to make something like a kernel. Learn how to code it yourself or just keep en eye on the development folder or better yet ask in pecoras thread if they will be updating for cm12 at all.
Oblox said:
Can someone also produce a fully working non crashing lollipop build by next tuesday please.
/sarcasm off
Asking for something like this is quite cheeky really, if someone like pecora is working on a lollipop kernel then they will but it takes a lot of work and effort to make something like a kernel. Learn how to code it yourself or just keep en eye on the development folder or better yet ask in pecoras thread if they will be updating for cm12 at all.
Click to expand...
Click to collapse
lol, i know its hard but i thought that is not so complicated, since williams kernel v8 is based on 12.1.A.1.207 sources, and so is cm12... So maybe "porting" williams kernel v8 kernel to cm12 is not so complicated? Maybe im wrong, explain me better
EDIT: Mr Steve did it again! By following these instructions Williams Kernel v8 will work on cm12 24.11.2014 build
MrSteve555 said:
Actually the bootloops on Williams kernel started when I added the kernel modules loading on boot in the ramdisk. It could clash with the inbuilt governors and other stuff, so kernel panics could occur.
I think that maybe removing these from the ROM zip could help:
/system/lib/modules/symsearch.ko
/system/lib/modules/cpufreq_limit.ko
/system/lib/modules/cpufreq_abyssplug.ko
/system/lib/modules/cpufreq_adaptive.ko
/system/lib/modules/cpufreq_badass.ko
/system/lib/modules/cpufreq_conservative.ko
/system/lib/modules/cpufreq_intelliactive.ko
/system/lib/modules/cpufreq_intellidemand2.ko
/system/lib/modules/cpufreq_intellimm.ko
/system/lib/modules/cpufreq_lagfree.ko
/system/lib/modules/cpufreq_lionheart.ko
/system/lib/modules/cpufreq_powersave.ko
/system/lib/modules/cpufreq_smartass2.ko
/system/lib/modules/cpufreq_wheatley.ko
/system/lib/modules/bfq-iosched.ko
/system/lib/modules/fifo-iosched.ko
/system/lib/modules/fiops-iosched.ko
/system/lib/modules/row-iosched.ko
/system/lib/modules/sio-iosched.ko
/system/lib/modules/vr-iosched.ko
/system/lib/modules/zen-iosched.ko
/system/lib/modules/zsmalloc.ko
/system/lib/modules/lzo.ko
/system/lib/modules/zram.ko
/system/lib/modules/tcp_bic.ko
/system/lib/modules/tcp_highspeed.ko
/system/lib/modules/tcp_htcp.ko
/system/lib/modules/tcp_hybla.ko
/system/lib/modules/tcp_illinois.ko
/system/lib/modules/tcp_lp.ko
/system/lib/modules/tcp_scalable.ko
/system/lib/modules/tcp_vegas.ko
/system/lib/modules/tcp_veno.ko
/system/lib/modules/tcp_westwood.ko
/system/lib/modules/tcp_yeah.ko
It's the full list, maybe some of them are missing in CM12 package which is not supposed to be used as a daily driver anyway. In the CM11 the files ought to be removed also from 12.5 delta patch. It has a big chance to work
But if it doesn't, well, I can't do much :/
Click to expand...
Click to collapse

Categories

Resources