Does anyone know of a git repo that has any history to the changes that B&N made to the kernel? I actually doubt that a repo like that exists, but thought I'd ask.
Does anyone know the git commit that B&N branched off of when they made their kernel? I'd like to know where the kernel started from so I can look into bringing new features into it.
thanks,
Jeff
Related
Well, I tried adding this to the development section, but I guess questions about actual development and how to go about it aren't welcome there, only new ROMs and kernels. If anyone who builds kernels ever ends up reading this, it would be awesome if you enabled /proc/config.gz support so those of us who are still learning can be assisted with building our own kernels. It would be much appreciated.
I generally include .config files in my git repo.....
ttabbal said:
I generally include .config files in my git repo.....
Click to expand...
Click to collapse
This is actually true, though I had forgotten. Unfortunately you're in the minority when it comes to kernel devs (for instance, you're answering questions in the General section), but I know whose repo to clone from now on. Thanks!
Hi,
i know that the build would be slow as hell but has anyone compiled ICS for the G1? just for trying it ?
i would like to try it myself but i have no clue on how and from hat i`ve heard my computer would take ages to build it
It's done for droid eris, it can be ported to G1.
http://forum.xda-developers.com/showthread.php?t=1352170
Porting would be inefficient when it can be built from source.
Unfortunately I can't do neither
Sent from my GT-I9100 using XDA App
Ice Cream Sandwich Build Help
As soon as the source was released I was thinking about trying to build it for "old reliable" (my nickname for my old G1). I know it would be slow as mud but I still want to give it a try. Problem is I've never compiled the source of Android before so I would be going in blind. I've read the info at source.android.com so I have somewhere to start. If anyone has any other guides/tutorials on how to build Android for a device then I would be really appreciative. I'm a Computer Science major so don't be afraid to throw a little code at me either. I'll include the details of my phone below in case anyone needs it.
HTC Dream
SPL: HBOOT-1.33.2005 (DangerSPL)
Radio: 2.22.19.261
OS: CyanogenMod 6.1 (Android 2.2.1)
You can have a look at Terry' ezGingerbread thread. Here he explains what to do to compile his ezGingerbread from the sources. Principally compiling ICS is the same, but you need to exchange / modify the manifest to your needs.
Sent from my Gingerbread on Dream using XDA App
Thanks, I looked it up and it was really helpful. Just a couple of quick questions. Do you know how far from stock ezGingerbread is? What do you mean when you say manifest? When people port a new version to a new device how is it normally done?
Thanks for your help. If I manage to get anything useful I'll be sure to share it here first.
Sent from my DROID3 using XDA App
hyperspace290 said:
Thanks, I looked it up and it was really helpful. Just a couple of quick questions. Do you know how far from stock ezGingerbread is? What do you mean when you say manifest? When people port a new version to a new device how is it normally done?
Thanks for your help. If I manage to get anything useful I'll be sure to share it here first.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
It's almost stock, but there are some projects from CM included and some he cloned from CM or from other sites and manages them by himself. Details you can see it in his manifest.xml located in the .repo directory. The manifest defines, what projects are to be included and what branch you want to use for these projects.
You will not want my manifest for ICS (at least unless I make an ICS branch myself)
The reason is you will want to use the ICS git repos and not the GB git repos (original or cloned by me)
That said if you are new to building an android rom look at the structure using ezgb some, and build ezgb, then when you understand the structure clone ICS from aosp (see info on source.android.com) and create your own manifest from that including cloned git repos you need from ezgb with any addtl modifications required.
The first thing is:
* Git is the source control for all parts of android, however many (well over 200) git repos are used in ICS
* Repo is a tool (python script with plugins pulled from its own git repo) for maintaining all of the git repos used in an android build, and creating the true tree of repos needed for the work directoy.
* Manifest is a special git repository with default.xml (and sometimes other manifest xmls) used by the repo script to find all the projects other git repositories, as well as what branch/commit to checkout to the work directory.
Thanks for the advice guys. Glad to see the little G1 is still getting some love. I think I'll start by building ezGingerbread to get the handle on the build process for Android and at least get up to 2.3.
If anyone knows what kinds of modifications are normally needed for a port like this then I would appreciate the help. Is it normally just editing some config files or would I have to dive into the code? Thanks again.
Sent from my DROID3 using XDA App
Looks like someone has beaten me to the punch. Anyone interested shout go have a look at this thread: http://forum.xda-developers.com/showthread.php?p=19648827
not exactly.
that is a port from a source-build for the hero
but very close
looks like the dev is trying to make a source build for the dream.
you could contact him so you can work together
Really get the cm9 source, pull forward the dream/sapphire device trees from cm7 (or firerats port of that) and it ought to be alright.
There seems little in the way of true cm bits at current (sure to change soon) but most of the hardware backwards compatibility patches are alredy in cm9 from the looks of it.. for all I know this is a cm9 build since aosp has no hero device tree out of box.
I was going to reply to that thread but since I'm still considered new I can't post to development threads. I guess I will PM the dev later to let him know I'm interested in helping him out.
Why would you build for another device if the dream has built into AOSP? Doesn't make a whole lot of sense to me unless they flat out took out the board file in ICS but you could easily put it back by pulling it from an earlier revision.
Sent from my DROID3 using XDA App
Do any of you have the source of the latest CM7 release for the kindle fire. I want to get into rom development and want a rom source so I can study the source.
ragul40 said:
Do any of you have the source of the latest CM7 release for the kindle fire. I want to get into rom development and want a rom source so I can study the source.
Click to expand...
Click to collapse
Don't know if he keeps it up to date, but here:
https://github.com/whistlestop/CM7KF
I would just run:
Code:
repo init -u git://github.com/whistlestop/CM7KF.git -b
then repo sync
As the title says, anyone know how to make aosp-based kernel compatible with cyanogenmod?
What I'm searching for is a set of particular commits that will make the kernel compatible with CM11.
Any help will be appreciated, thanks!
BTW how to search for commit message in github?
I need to search for commit that will give faux123 voltage control.
You can just take a CM11 kernel for mako for example and look at the first few commits.
As far as I know you can't search by commit message.
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
Found my answer my self
https://github.com/bedalus/nexus4/blob/225bb02af8fa5cb75f294e5e826d5910be347119/cm.patch
This is a near stock falcon 4.4.4 kernel built with the latest Linaro toolchain (Linaro GCC 4.9-2014.12) for all of those who prefer stock kernels and absolutely need those 10 extra points in Antutu
Differences from stock are just a few Cortex-A7 optimizations, F2FS patches from mainline 3.18 and linaro toolchain.
All credit goes to @bedalus, who started his kernel thread for Peregrine, fixed all the small bugs that made compiling with newer Linaro toolchains impossible and cherry picked all those F2FS patches.
Sources and tools used:
MotorolaMobilityLLC/kernel-msm
MotorolaMobilityLLC/vendor-qcom-opensource-wlan-prima
bedalus' patches
Christopher83's Linaro Toolchain
My repo, where all sources are merged
Changelog:
falcon_stock_4.4.4_linaro_4.9.3.zip
- stock kernel
- added necessary patches to make it compile with linaro
- some Cortex-A7 optimizations
falcon_kernel_4.4.4_v2.zip
- same as falcon_stock_4.4.4_linaro_4.9.3.zip
- filesystem patches in line with mainline linux 3.18
- removed some debug info
The zip can be flashed with TWRP or CWM. Not flashable through fastboot.
Thanks @knizmi. I think stock users will appreciate this
Anyone tested? How the battery?
Wysłane z MOTO G
Dizzyrul3z said:
Anyone tested? How the battery?
Click to expand...
Click to collapse
This is the stock kernel, so the batttery is as good as with stock kernel (you really can´t make it much better in any way). These screenshots are taken after some 7 hours of sleep.
Works pretty good on XT1031. Nice work! Any chance you could make a build with the kexec hardboot patch to use it with multirom?
I immediately noticed a performance improvement after flashing this kernel. Thanks!
Hi @knizmi
I said wait til I push a new branch, but I figure it's easier if you pull just a patch with
Code:
wget https://github.com/bedalus/moggy/commit/ead900a02071506c267fdebd292cbb2cdb31f4bd.patch
then you can apply it with
Code:
git am ead900a02071506c267fdebd292cbb2cdb31f4bd.patch
This is my preferred way to grab commits. Did you add my repo as a remote?
Battery life is really good on this kernel thank u dev
Sent from my XT1032 using XDA Free mobile app
bedalus said:
Hi @knizmi
I said wait til I push a new branch, but I figure it's easier if you pull just a patch with
Code:
wget https://github.com/bedalus/moggy/commit/ead900a02071506c267fdebd292cbb2cdb31f4bd.patch
then you can apply it with
Code:
git am ead900a02071506c267fdebd292cbb2cdb31f4bd.patch
Click to expand...
Click to collapse
Thanks a bunch, this should really make merging those patches easy!
bedalus said:
This is my preferred way to grab commits. Did you add my repo as a remote?
Click to expand...
Click to collapse
I have added your repo as a remote now. I was fighting with git last week quite a bit (never used that devil's tool before), but now I think I am getting used to it. For my first build I've just "patched" those files with gedit...
syrkles said:
Battery life is really good on this kernel thank u dev
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the heads up, but compiling someone else's sources doesn't make me a dev
New version uploaded.
falcon_kernel_4.4.4_v2.zip
- same as falcon_stock_4.4.4_linaro_4.9.3.zip
- filesystem patches in line with mainline linux 3.18
- removed some debug info
Thanks @bedalus.
amarc78 said:
Any chance you could make a build with the kexec hardboot patch to use it with multirom?
Click to expand...
Click to collapse
Sorry, the aim of this is to stay as close to stock as possible and only add optimizations/update drivers.
knizmi said:
For my first build I've just "patched" those files with gedit...
Click to expand...
Click to collapse
If you've got my repo as a remote you should be able to see my commits with
Code:
git log -- bedalus/moggy
depending on what you named your remote.
Once you see what commits you want, copy their hashes (the long string of letters/numbers) then
Code:
git cherry-pick *hash*
If there's a problem with the cherry-pick you can fix it manually with
Code:
git mergetool
or abort with [git cherry-pick --abort[/code]
I've installed meld as my mergetool. I'm using a debian derivative so I did
Code:
sudo apt-get install meld
That's a pretty comprehensive quick-start guide to cherry-picking from any remotes you've fetched.
Cannot downgrade to default stock.
can you make a zip with libs to go back.
everb00b said:
Cannot downgrade to default stock.
can you make a zip with libs to go back.
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/showthread.php?t=2649763
That zip doesn't have libs. I made a zip for this a while ago, but it doesn't completely put everything back to stock. The best way seems to be to reflash stock ROM zip.
amarc78 said:
That zip doesn't have libs. I made a zip for this a while ago, but it doesn't completely put everything back to stock. The best way seems to be to reflash stock ROM zip.
Click to expand...
Click to collapse
You mean in the thread I've posted. I've thought that too at the beginning, but they are there separately, look for Stock Kernel Modules: [XT1032] - 4.4.2 | 4.4.3 | 4.4.4 | 4.4.4 (GPE) | 5.0.1 (GPE) | [XT1033] (Dual-SIM) - 4.4.4. You just have to flash two zips instead of one.
Ahh, I forgot that was there. I have XT1031. Are the 1032 libs the same?
Edit: never mind. They look the same.
amarc78 said:
Ahh, I forgot that was there. I have XT1031. Are the 1032 libs the same?
Click to expand...
Click to collapse
Not sure, you can try. If there is a problem you can always reflash stock /system, backup those modules and perhaps send them to @lost101
bedalus said:
If you've got my repo as a remote you should be able to see my commits
Click to expand...
Click to collapse
Thank you for the info again. You are very helpful.
Do I understand it correctly that I need to fetch your repo before I can start cherry-picking? Searching around the internet , it looks like it. I may give it a try one day, but for now I will stick with git am, which seems like the perfect tool to pick single commits from many repos.