Database Info

[HUAWEI U8100/U8110/U8120] Froyo Kernel Development / Porting (Your help needed!)

Many people want to run a working froyo on their devices.
This won't be possible in a clean way without compiling a new kernel.
To archive this goal, we need to merge the Huawei specific device drivers (which are for 2.6.29) into a new kernel tree, the 2.6.32.9 one (or even 2.6.35 but 2.6.32.9 comes first since it is stable and thus important to us).
I did some research and preliminary work which I will explain here:
- The base kernel Huawei started with is available here (gitweb) - also check their wiki.
- Huawei started with the Q8650BSDCANLYA324020 tag on the donut_glazed branch (see instructions at the end of the post)
- Huawei has written it's own board driver (note they have used a Q8650 kernel release not a MSM7x25 one, most likely because this board driver is a little older and was not available for the version they wanted)
- After they were finished writing their drivers they released the kernel source (as you can download it from Huawei)
I have checked out the Q8650BSDCANLYA324020 base kernel version and diffed it against the kernel release of Huawei, generated a patch file (and stripped out the DOS linebreaks wtf) which can be applied to the base kernel.
Applying this patch to a more recent kernel (2.6.32.9) is not possible without merging the code into the new kernel tree (and since I'm not a programmer I can't do it - this is were your help is needed).
The other question is in which kernel tree we can port the patch I have extracted. I think we can use Q8650BSDCANLYA504005 on the froyo_almond branch since Huawei used an older version of it. Merging it into the AOSP msm-2.6.32.9 tree may be possible too (but the code aurora msm kernel is an improved AOSP version, so I guess we want that one).
My patch (and some non-pulse-mini fixup patch) alongside with a freshly extracted and fixed .config for the U8120 can be found at http://nico.core.ws/misc/huawei_kernel_u8100_8110_8120/
To port the source you need to checkout the original source (Q8650BSDCANLYA324020), create a new branch in which you apply the Huawei patch, then checkout the froyo kernel (Q8650BSDCANLYA504005) and merge your branch containing the changes from the patch into it.
Another way may be porting the froyo kernel tree back to the eclair one with Huawei patches.
Please post any results/questions/etc. here!
If we should get this working we can also enable the GPU driver (Adreno 200) as requested by many people (and much more (CyanogenMOD anyone? )).
Appendix:
Instructions on how to get the original source:
$ git clone git://codeaurora.org/kernel/msm.git
$ git checkout Q8650BSDCANLYA324020
Instructions on how to apply the patch (assuming "msm" is the kernel tree):
$ cp diff_kernel_msm_aurora_Q8650BSDCANLYA324020.diff msm/
$ cd msm/
$ patch -p1 < diff_kernel_msm_aurora_Q8650BSDCANLYA324020.diff
If you are compiling for U8100 or U8120 phones, you need to apply another
patch which fixes sensors (otherwise your phone won't be able to read battery
level and stuff):
$ cp needed_fixes_for_non_u8110_devices.diff msm/
$ cd msm/
$ patch -p1 < needed_fixes_for_non_u8110_devices.diff
Note that the above instructions will get you nothing new, only the kernel already running on your device.
This thread is about porting the Huawei patch to a froyo kernel.

Very nice! Thank you for this topic!
I hope this will be successfull

Are the Atheros sources included aswell?

[GER]Roxxor said:
Are the Atheros sources included aswell?
Click to expand...
Click to collapse
To be honest, I don't know. They should be in there though (maybe under a more generic driver name or integrated in the board driver) otherwise Huawei would have violated the GPL.

The problems with the fixes:
wifi
They got almost wifi working in other post
radio
FM radio too with an 3rd party app
dpad
dpad crash in this post too 2 pages back just disable this
screen calibration
calibration fix can meaby be fixed with HTC calibrate??(its an calibration app)
sound
I solve the sound problem with my phone is to replace the libaudio.so from 2.1rom,maybe you can try.\

cedric123 said:
here is an source for the adreno drivers.
https://www.codeaurora.org/gitweb/q...b819424af4be;hb=refs/heads/android-msm-2.6.32
Click to expand...
Click to collapse
Basically this is the complete kernel source for froyo without Huawei patches (it's the wrong tag too).
When we have ported the drivers we easily can enable that driver.
cedric123 said:
the froyo kernel source: http://www.huaweidevice.com/tcpsdow...&attachmentName=kernel-2.6.32-U8150-Froyo.zip
Click to expand...
Click to collapse
Thats the source for the U8150, not the ones we want. The only thing which may help us at a future point in there is the kernel config.
cedric123 said:
If you compile a kernel right now you'd get a kernel that won't read the batterylevel and the magnetic compass won't work so we need to make a few adjustments.
Click to expand...
Click to collapse
This is in needed_fixes_for_non_u8110_devices.diff
So nothing new here.

So what can we do to help?
Is there a way to chat in XDA?

Any news on this?

cedric123 said:
here is an source for the adreno drivers.
LINK REMOVED
Here are some are adreno 200 drivers from a Custom nexus one ROM:
Areno Drivers package contains the adreno rivers only(i could miss some drivers here so look for the package above contains all drivers from the nexus rom
LINK REMOVED
Click to expand...
Click to collapse
Possible to make an update.zip for this Adreno 200 driver on 2.1 while 2.2 is not working?

editeditediteditediteditedit

Maybe he's working on the project.

Leito92 said:
Maybe he's working on the project.
Click to expand...
Click to collapse
I dont think so he's not saying anything about it for 1 week now...

But even if he doesnt say anything, this topic can be useful.

Someone with git/kernel/c knowledge need to port the patch.

nicoderboss said:
Someone with git/kernel/c knowledge need to port the patch.
Click to expand...
Click to collapse
Who can do That?
Kallt_kaffe meaby?

nicoderboss said:
Someone with git/kernel/c knowledge need to port the patch.
Click to expand...
Click to collapse
You need some elemental knowledge in C and then simply cut and paste the text in the files.
However, I think that it is more important to be able to compile from source and install the existing Huawei Linux kernel for the U8120. That is, can we compile from source all the code for Android 2.1-update1 and install on the U8120?
It might be good to try to get CyanogenMod on the U8120 for the kernel version that Huawei provides. Then, we can cut down the 1.5MB patch into smaller parts, and even try to get the drivers included in the Linux kernel.
I have not idea how to compile Android 2.1-update1 and get the plain old android source on the phone. I am willing to invest the CPU clocks to compile it, though.

cedric123 said:
Who can do That?
Kallt_kaffe meaby?
Click to expand...
Click to collapse
Dunno, it's quite a huge and advanced task.
Sent from my Vodafone 845 using XDA App

maybe we can get some kernel developers from the desire topic to help us?
I have send Benee, deovferreira, Kali- a PM maybe they could help us

nicoderboss said:
Dunno, it's quite a huge and advanced task.
Sent from my Vodafone 845 using XDA App
Click to expand...
Click to collapse
Can we just replace the normal kernel in the command list for the new kernel so you apply patch in the new kernel(u8150)froyo kernel?

I have had contact with benee a kernel developer for the htc desire. He is willing to help but he needs a device so he can test kernels he build. It is not possible to build kernels without a device because this is a huge project without a good base.
Maybe we can setup a fund raiser to get him a device?

[Question] Kernel Compilation for Modules

First post in the Dev section but this seemed to be the place to talk about kernel compilation and module development.
I have twice now, and am working on my third kernel compilation for the purposes of custom module building for the TF700 and the TF201.
The question I have has to do with the compilation process. Every time I have gone through this with the downloadable Asus Kernel zip I run in to several issues. Either missing references in code or portions that won't compile at all. Is this normal for kernel compilations? I would have thought that it would be fully compilable out of the box ( so to speak). Is it ASUS or just android/Linux in general that works out this way?
Is there a better way to do it? Should I use some generic source with the same version numbers? The current source is just not working at all. I am using an Ubuntu distro. Have the cross compile tools etc... but it just fails. I have already resolved two missing definition references and it just keeps on failing in new places
Hopefully this question doesn't offend developers. I have moved from WinPhone to here and want to better my understanding of how this should all work but need to start with some basics before I can make a meaningful contribution.
Thanks.
P.S... I looked and didn't find a "Compiling android kernels for dummies" book

hx4700 Killer said:
I looked and didn't find a "Compiling android kernels for dummies" book
Click to expand...
Click to collapse
"Dummies" doesn't write a book on kernel dev. Too wrapped up in telling people how to download iTunes.....
Use your "Google". And when you find it, Google XDA University.
There, you will find steps for setting a build environment and kernel and cross arm.
Understand, all kernels are different, but a good place to start. Plus, you learn how to use Google. An added bonus.
Oh... and... as an extra bonus, I will move this to Q & A, as this post has no development work attached. :silly:
MD

My question wasn't HOW to cross compile. I have done it.
My question is WHY are there so many errors that need correcting when compiling the ASUS downloadable kernels and if this is typical of the source from any device or just ASUS?

hx4700 Killer said:
The question I have has to do with the compilation process. Every time I have gone through this with the downloadable Asus Kernel zip I run in to several issues. Either missing references in code or portions that won't compile at all.
Click to expand...
Click to collapse
I had to fix exactly one pair of quotes vs. angle brackets somewhere in the RIL - get the patch pack from my kernel and apply the ril include fix. Then it should compile. If not, you are doing something wrong.

Can you post any links or names of everything ill need to get started on cross compiling a kernel for my tf700t I download the source and get my config.gz and am running a ubuntu distribution but if you could post a link to a tutorial that has detailed instructions that will work for the infinity that would be greatly appreciated thankyou

alexcass4 said:
Can you post any links or names of everything ill need to get started on cross compiling a kernel for my tf700t I download the source and get my config.gz and am running a ubuntu distribution but if you could post a link to a tutorial that has detailed instructions that will work for the infinity that would be greatly appreciated thankyou
Click to expand...
Click to collapse
Step 1: Get a suitable ARM toolchain. I can't help you here with Ubuntu because I'm using Gentoo and their crossdev tool (http://www.gentoo.org/proj/en/base/embedded/handbook/?part=1).
Step 2: Cross-compiling the kernel works just as for native kernels (make menuconfig, make), but you have to pass parameters to each make, e.g. make ARCH="arm" CROSS_COMPILE="arm-gentoo-linux-gnueabi-" (or whatever your toolchain is called)
Step 3: For the TF700-specific blob stuff I have written a detailed tutorial here: http://forum.xda-developers.com/showpost.php?p=36925180&postcount=4

[Q] Building a UnORom on Gentoo

Hi there,
as I don't have permission to write on the Unofficial Rom Project Thread, I am asking here for a GUIDE to setup a jenkins server that automatically builds ROMs for my Sensation aka Pyramid.
Is anyone here who can help me to get into the build process for the first time on an continious integration server.
What did I already did?
I have set up Java 1.6 to build a Cyanogenmod 11 and I m not sure if it should be Java 7?
I downloaded the entire sources from github. I m sorry I m not allowed to post a link.
via
so I hope that isnt the wrong way as I am following multiple guides to accomplish my target.
So I wanted to set up it all for the first time to run a compilation without jenkins then I 'm stuck at the point where I integrate the UnORom files - I only could set up a
Code:
git clone https://github.com/UnORoms/android_device_htc_pyramid.git
and then i succesfully executed
Code:
./extract-files.sh
so it downloaded a couple of files from my phone.
But when I do a
Code:
lunch
there don't exists a cm_pyramid?
So I m stuck at this point and I m politely asking for help.(Maybe to accomplish my personal goal of using a continious integration server at least
Thanks in advance for your replys

Nobody knows how to build a android rom for a specific device?
In my case the HTC Sensation?
I would be glad if there where some tutorials of implementing the necessary files into my cm11-tree.
Could anyone please give it a try?

chiefdome said:
Nobody knows how to build a android rom for a specific device?
In my case the HTC Sensation?
I would be glad if there where some tutorials of implementing the necessary files into my cm11-tree.
Could anyone please give it a try?
Click to expand...
Click to collapse
I'm not 100% familiar with building roms, but I once compiled them completely from source for testing purposes.
Do you have device files and kernel in your local manifest to sync them from somewhere or did you take what you need from your phone? Not sure if it's required or not.
When I had everything ready I had to run
Code:
./device/htc/pyramid/repo-patcher.sh
then I could run
Code:
lunch cm_pyramid-userdebug
and it worked.
Not sure if it works same way here too, since I did that when I used Team-Sennyc2 device tree.

What is necessary if I want to compile a ROM?

Hi guys. 2 months ago I've came into Android World deeper than before and now I'm very fascinated. I downloaded linux, all the necessary files to compile a rom but I still don't understand some things.
My device is Redmi Note 2 and I use stock MIUI 7. As we all know mtk and/or xiaomi haven't released kernel sources (6795) so developers have to think hard how to make a rom. And there are my questions. Does kernel source is really necessary? What if I compile rom successfully and then port boot.img from stock? Will it work? However developers made some roms based on LP for this device. And I read that I need device tree and vendor, which doesnt exist for redmi note 2 or I still can't use github.
Second question which I have is: does compiling for 64 bit CPU differ from compiling for 32 bit CPU (like 6592)? If yes, could you give me some tips?
Ohh I think you can understand what I wrote
Thanks in advance and please dont blame me for silly questions

If you are looking to compile roms then you picked the wrong device to do it. They are the worst with kernel source. You can't completely compile a rom but use a patch system that does most of the work.
Yes it is different. There are some Tuts around but they are few as most don't use that type of chip.
If you really want to learn to develop then I would suggest getting a different device. One that respects the copyright and gpl laws.

zelendel said:
If you are looking to compile roms then you picked the wrong device to do it. They are the worst with kernel source. You can't completely compile a rom but use a patch system that does most of the work.
Yes it is different. There are some Tuts around but they are few as most don't use that type of chip.
If you really want to learn to develop then I would suggest getting a different device. One that respects the copyright and gpl laws.
Click to expand...
Click to collapse
Thank you for your advices. I have HTC desire 310 and I found the kernel sources. I know what I'll do in my free time

Monsterlevel said:
Thank you for your advices. I have HTC desire 310 and I found the kernel sources. I know what I'll do in my free time
Click to expand...
Click to collapse
To compile a rom u need kernel source, device tree and proprietary, bye

Need help with building kernel (ath9k)

Hi Lads,
Past few days im trying to add the ath9k module to a kernel.
I took the emotion kernel but when i started to make the kernel i constantly receiving errors.
I googled till my eyes burned out of my skull but got no solution. Probably im doing something wrong
Im looking for someone who can build the kernel easily including the ath9k driver.
My purpose is to use Kali Nethunter with the TP-Link WL722N adapter on the Note Edge N915F.
Im so desperate that i want to pay for it. Or maybe a game on steam :highfive:
Please help me out!
Greetings.
Stefjoe

Stefjoe,
I also saw your pm. I know now that you would like that module added to the tblte kernel. Kali Nethunter is not a rom, it is an overlay of sorts. Essentially a chrooted Linux distribution running over the top of your Android phone.
Kali only supports stock roms, or some "CyanogenMod variants", so I could add this to the AOKP kernel for you, but I cannot guarantee that you will have everything you need for this to work. For instance, you are going to need packet injection, module loading and unloading, force modules, etc., etc., much more than just the one item you requested. The note edge is not on the list of supported devices for a reason, it takes much dedication and effort to set it up properly. You would also need to build your custom port of Kali to go on your system. (Unless I am mistaken, no one has made one for the Note Edge yet.)
So, have you already built a working port of kali for your phone?
I say this in the kindest of regards, but if you cannot build the kernel, can you build the kali image?
As a side note, all the tools in Kali Linux are freely available, and you can download them to your phone right now, just not in the glorified package. Having Kali is like having a toolbox. Having a tool box does not make one a mechanic. Having Kali does not make one a pentester, or cacker (unethical hacker) if you are aiming for that.
I am not opposed to you having Kali, I've used it before myself (not on a phone), but in the end, I found Debian to be just as useful, downloading the tools that actually helped me in my job/tasks.
I am just curious if you have already created the kali image you need for the Note Edge phone. In theory, if the only thing you need is a kernel with the above, then it should work with your current kernel, just without that feature. If you have not even made the image yet, then I suspect that you are going to need a lot more than what you asked for.
I hope that makes sense.

AlaskaLinuxUser said:
Stefjoe,
I also saw your pm. I know now that you would like that module added to the tblte kernel. Kali Nethunter is not a rom, it is an overlay of sorts. Essentially a chrooted Linux distribution running over the top of your Android phone.
Kali only supports stock roms, or some "CyanogenMod variants", so I could add this to the AOKP kernel for you, but I cannot guarantee that you will have everything you need for this to work. For instance, you are going to need packet injection, module loading and unloading, force modules, etc., etc., much more than just the one item you requested. The note edge is not on the list of supported devices for a reason, it takes much dedication and effort to set it up properly. You would also need to build your custom port of Kali to go on your system. (Unless I am mistaken, no one has made one for the Note Edge yet.)
So, have you already built a working port of kali for your phone?
I say this in the kindest of regards, but if you cannot build the kernel, can you build the kali image?
As a side note, all the tools in Kali Linux are freely available, and you can download them to your phone right now, just not in the glorified package. Having Kali is like having a toolbox. Having a tool box does not make one a mechanic. Having Kali does not make one a pentester, or cacker (unethical hacker) if you are aiming for that.
I am not opposed to you having Kali, I've used it before myself (not on a phone), but in the end, I found Debian to be just as useful, downloading the tools that actually helped me in my job/tasks.
I am just curious if you have already created the kali image you need for the Note Edge phone. In theory, if the only thing you need is a kernel with the above, then it should work with your current kernel, just without that feature. If you have not even made the image yet, then I suspect that you are going to need a lot more than what you asked for.
I hope that makes sense.
Click to expand...
Click to collapse
Thanks for your reply again! I kinda ported the Nethunter to Note Edge with help from this video on YT ; /watch?v=jhLBJJwB88k
Everything works fine but only the TP-Link WL722N is not working because the kernel does not have this module installed. The adapter takes care of the injection so no worries i guess. I sended u a PM.
I am a certified hacker and i know what Kali Linux is but only missing this tool and it could make my work a lot easier. So i really appreciate if u can do this for me man. Endless thanking
Greetings

stefjoe said:
Thanks for your reply again! I kinda ported the Nethunter to Note Edge with help from this video on YT ; /watch?v=jhLBJJwB88k
Everything works fine but only the TP-Link WL722N is not working because the kernel does not have this module installed. The adapter takes care of the injection so no worries i guess. I sended u a PM.
I am a certified hacker and i know what Kali Linux is but only missing this tool and it could make my work a lot easier. So i really appreciate if u can do this for me man. Endless thanking
Greetings
Click to expand...
Click to collapse
Stefjoe,
I see from your PM that you are not requesting my AKLU kernel, but the TW Emotion Kernel. I can't do that for you.
To build the kernel you need the right source, the source code for the kernel has been updated since r17 ( I think it is r2X? now). That means rolling back through the commits to find the time it was built and working properly and getting that source. It is not as simple as just going straight back to r17, the r17 version you may be using may be anywhere in the commits between r17 and r18.
Then we would need the exact toolchain he/she was building with. He says Linaro 5.1, but which one, 5.1, 5.1.1, 5.1.8? There are several.
Also, I do not build TW kernels. I only build AOSP kernels. I also don't usually build off of someone else's work. I was under the impression you wanted me to add that module to my AKLU kernel instead.
To get that specific kernel built the way you want, I recommend that you ask @Pafcholini to do that for you, since he made it originally.
If you want, I can add that module to my AKLU kernel for you, but I know the rest of the needed kernel items are in there that you need (packet injecting, force module loading, etc.) so I doubt it will work for you. You would also have to switch to AOKP, which may or may not work with your porting guide.
Sorry, but after looking at your full request, I don't think I can help you with what you need.