So I dived into the N7100 kernel, and tried a defconfig with Samsung's config. After a couple of setbacks in the form of toolchain related errors, I got it to create a zImage with the NDK/gcc4.4.3. But on booting, I noticed that the capacitative touch keys would no longer work. I'm guessing that I'm missing something in .config.
So where should I be looking in .config and the source tree for code related to the capacitative buttons?
I'm thinking we might work on a collaborative wiki for N7100 kernel source tree.
Samsung didn't share that with ANY of the "note II" variant source drops. However, you can pull the source directory from the i9300 kernel source. I forget the exact path (I'm at work atm), but it's something like drivers/input/keyboard/cypress
Take care
Gary
garyd9 said:
Samsung didn't share that with ANY of the "note II" variant source drops. However, you can pull the source directory from the i9300 kernel source. I forget the exact path (I'm at work atm), but it's something like drivers/input/keyboard/cypress
Take care
Gary
Click to expand...
Click to collapse
You grab it from the n8000 source which is full of updates for our devices. Or check my t889 kernel on github. I put the cypress drivers in a clean commit you can then create a patch from.
garyd9 said:
Samsung didn't share that with ANY of the "note II" variant source drops. However, you can pull the source directory from the i9300 kernel source. I forget the exact path (I'm at work atm), but it's something like drivers/input/keyboard/cypress
Take care
Gary
Click to expand...
Click to collapse
Except the HK source?
I was just looking into your git and found cypress in your initial commit and that you'd actually based the git on the HK source drop.
I untarred the HK source and found cypress there too. What did Samsung think? That international users could do without the capacitative buttons?
Edit: Compiled without a single error. Thank you.
Droidzone said:
I was just looking into your git and found cypress in your initial commit and that you'd actually based the git on the HK source drop.
Click to expand...
Click to collapse
You quoted me in that response... but I don't have any HK source drops in my github. The only Note II source drop I have is the SGH-i317 drop (and it's missing the cypress drivers as well.) Hmm..
garyd9 said:
You quoted me in that response... but I don't have any HK source drops in my github. The only Note II source drop I have is the SGH-i317 drop (and it's missing the cypress drivers as well.) Hmm..
Click to expand...
Click to collapse
lol..Sorry, I must've confused your repo with someone else's.
Anyway, check out the HK N7100 repo. It is complete and is about 10 MB more than the international stuff.
Droidzone said:
Except the HK source?
I was just looking into your git and found cypress in your initial commit and that you'd actually based the git on the HK source drop.
I untarred the HK source and found cypress there too. What did Samsung think? That international users could do without the capacitative buttons?
Edit: Compiled without a single error. Thank you.
Click to expand...
Click to collapse
Hi I'm having your problem, I'm download kernel source's and try bulding my First kernel for Gt N 7102, workinkg all except touchkeys.
Help me ?
Thanks bro
Sent from my GT-N7102 using Tapatalk 2
Did you use the HK source? What's the error?
Edit: Missed the N7102 part. See if cypress is present
Code:
cd /pathto/kernel
find . -iname cypress -type d
Droidzone said:
Did you use the HK source? What's the error?
Edit: Missed the N7102 part. See if cypress is present
Code:
cd /pathto/kernel
find . -iname cypress -type d
Click to expand...
Click to collapse
In original samsung source's cipress is not present but, I'm download from other source and insert in the correctly tree.
I'm modify kconfig file.
Try make menuconfig and cipress comparte to device input-->keyboard.
Make and install new kernel but touch keys not working.
Excuse my English and 'horrible.
Emblema said:
In original samsung source's cipress is not present but, I'm download from other source and insert in the correctly tree.
I'm modify kconfig file.
Try make menuconfig and cipress comparte to device input-->keyboard.
Make and install new kernel but touch keys not working.
Excuse my English and 'horrible.
Click to expand...
Click to collapse
Check your makefiles, and see that cypress has been asked to build.
Related
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?
As per my request Samsung updated the source code to the version we have currently on our phones.
h ttp://opensource.samsung.com/reception/reception_main.do?method=downLoad&attach_id=1036
What else do we need now to get cyanogen on here? lol
Get CWM working!
Sorry for being the outdated, uneducated, tool but what exactly does this mean?
I'll be honest I'm not sure... I'm not a programmer for android but I do know someone mentioned that we don't have it. So I went ahead and emailed Samsung and they actually responded. So thought I would throw it out there.
it's for devs and builders. the kernel tar is labeled kb7, actually. krylon probably had this already but still.... good lookin' out man.
So does the source code include the kernel? I want to help get the ball rolling but I need to know whats missing...
Galaxy S 4G
soundwave123 said:
So does the source code include the kernel? I want to help get the ball rolling but I need to know whats missing...
Galaxy S 4G
Click to expand...
Click to collapse
kernal is included yes
So are we trying to figure out how to "unfreeze" it?
Galaxy S 4G
Warning -- as Krylon points out, this appears to contain KB7 source and the device appears to be running KB5
Thanks!
http://opensource.samsung.com/reception/reception_main.do?method=downLoad&attach_id=1036
$ cat readme.txt
HOW TO BUILD KERNEL
1. Visit http://www.codesourcery.com/, download and install Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI.
2. Extract kernel source and move into the top directory.
3. Execute 'make vibrantplus_rev00_defconfig'.
4. Execute 'make' or 'make -j<n>' where '<n>' is the number of multiple jobs to be invoked simultaneously.
http://www.codesourcery.com/sgpp/lite_edition.html
http://www.codesourcery.com/sgpp/lite/arm/portal/release1600
Thanks again -- just what I was looking for -- Kernel_T959V_KB7/drivers/net/tun.c
Good news for the developers i was provided with the kernels for the A31 chipset.
the source is allwinners
1.A31 U-boot "allwinner-sunxi-a31"
git.hands.com Git - u-boot.git/tree
2. A31 Linux 3.3 kernel source "allwinner-sunxi-a31"
git.hands.com Git - linux.git/summary
Great news!. It may be useful to post under Android TV stick. This will make MK810 be a powerful Linux box.
aruangra said:
Great news!. It may be useful to post under Android TV stick. This will make MK810 be a powerful Linux box.
Click to expand...
Click to collapse
Please if you can cpmpile it publish the tutorial and also the ported verision of linux.
Sent from my MOMO11 四核 using Tapatalk 2
Yeah, this is the first time a Chinese manufacturer release code of its chip. Nice.
kcthomlau said:
Yeah, this is the first time a Chinese manufacturer release code of its chip. Nice.
Click to expand...
Click to collapse
well, no, this is the fourth chip Allwinner releases the kernel source for, Amlogic is also good at releasing code, so it's not unheard of.
git gives error:
Code:
:~$ git clone http://git.hands.com/linux.git
Cloning into 'linux'...
warning: remote HEAD refers to nonexistent ref, unable to checkout.
suleymanovemil8 said:
git gives error:
Code:
:~$ git clone http://git.hands.com/linux.git
Cloning into 'linux'...
warning: remote HEAD refers to nonexistent ref, unable to checkout.
Click to expand...
Click to collapse
Seems like someone did a bad commit on the HEAD branch. Thankfully, you can still recover the content by first cloning the repo, and then checking out the appropriate branch:
Code:
git checkout allwinner-sunxi-a31
im trying to build the kernel from androids googlesource website, and want to know which defconfig i need to use to start the build
tegra3_android_defconfig
tegra_android_defconfig
tegra3_defconfig
tegra_defconfig
i couldnt find a grouper specific one
azoller1 said:
im trying to build the kernel from androids googlesource website, and want to know which defconfig i need to use to start the build
tegra3_android_defconfig
tegra_android_defconfig
tegra3_defconfig
tegra_defconfig
i couldnt find a grouper specific one
Click to expand...
Click to collapse
tegra3_android_defconfig seems to be the one.
Yes, I am trying to rebuild their from source. But, when I have testing on running. There are found red splash when I click them on screen. May I know what the caused of this ?
Thanks.
Ok, The problem has resolved now .
AOSP's guide to building kernels is quite useful. I actually used it earlier today.
http://source.android.com/source/building-kernels.html
It contains building instructions (obviously) as well as the proper defconfig for all AOSP devices.
Hi there,
I'm trying to make a lineageos ROM for our great Xperia XZ but I face some problems.
I done all the steps of the ultimate ROM making thread on XDA, and i can't see my XZ in the device list of the lunch command.
To be precise i see it as aosp_f8331 and not lineage_f8331 nor lineage_kagura.
I already tried to build aosp on XZ without any success.
Maybe someone can light my candle.
Thanks
fastbooking said:
Hi there,
I'm trying to make a lineageos ROM for our great Xperia XZ but I face some problems.
I done all the steps of the ultimate ROM making thread on XDA, and i can't see my XZ in the device list of the lunch command.
To be precise i see it as aosp_f8331 and not lineage_f8331 nor lineage_kagura.
I already tried to build aosp on XZ without any success.
Maybe someone can light my candle.
Thanks
Click to expand...
Click to collapse
Looks like you haven't changed the "vendorsetup.sh" file
Should look like THIS (But where carbon is, put lineage)
You can also use "lunch lineage_kagura-userdebug"
THANKS,
Maybe this will help me a lot !
I was looking all over internet to find an answer and you gave it.
nzzane said:
Looks like you haven't changed the "vendorsetup.sh" file
Should look like THIS (But where carbon is, put lineage)
You can also use "lunch lineage_kagura-userdebug"
Click to expand...
Click to collapse
hey, now i'm here.
Code:
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_f8331". Arrêt.
Device f8331 not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for f8331 not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_f8331". Arrêt.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_f8331". Arrêt.
** Don't have a product spec for: 'lineage_f8331'
** Do you have the right repo manifest?
can you guide me or pm the steps.
I would like to write and post a detailed tutorial for building roms for our phone with all the links to the needed files etc.
Cheers
fastbooking said:
hey, now i'm here.
Code:
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_f8331". Arrêt.
Device f8331 not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for f8331 not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_f8331". Arrêt.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_f8331". Arrêt.
** Don't have a product spec for: 'lineage_f8331'
** Do you have the right repo manifest?
can you guide me or pm the steps.
I would like to write and post a detailed tutorial for building roms for our phone with all the links to the needed files etc.
Cheers
Click to expand...
Click to collapse
https://github.com/nzzane/device-sony-kagura/blob/cm-14.1/vendorsetup.sh
Like that
Yeah I just understood that way and done that, the error is after the edit
fastbooking said:
Yeah I just understood that way and done that, the error is after the edit
Click to expand...
Click to collapse
@nzzane
fastbooking said:
@nzzane
Click to expand...
Click to collapse
Is your repo clones from the official device repo or made yourself?
nzzane said:
Is your repo clones from the official device repo or made yourself?
Click to expand...
Click to collapse
I cloned the lineageos repo and added Sony's device specific files after and edited local_manifest.xml
fastbooking said:
I cloned the lineageos repo and added Sony's device specific files after and edited local_manifest.xml
Click to expand...
Click to collapse
Can you link me to your repo?
I can have a look for you and see whats up
nzzane said:
Can you link me to your repo?
I can have a look for you and see whats up
Click to expand...
Click to collapse
Hum I'm a bit new, i need to fork everything i used ?
Or maybe i can upload my entire work file (i have fast internet 950mb/s Down and 250mb/s up)
fastbooking said:
Hum I'm a bit new, i need to fork everything i used ?
Or maybe i can upload my entire work file (i have fast internet 950mb/s Down and 250mb/s up)
Click to expand...
Click to collapse
Just upload your device folder: device/sony/kagura
and setup a new repo if you haven't already https://github.com/
and upload your Kagura folder's contents into the new repo
I see, I'll do it after school tomorrow (16 yo french boy), thanks for help tho
fastbooking said:
I see, I'll do it after school tomorrow (16 yo french boy), thanks for help tho
Click to expand...
Click to collapse
All good, XDA is a great place to learn, as long as the devs are friendly ?
If you need help, you can reach out to me
I figured out for the build issue,( thanks to @nzzane)
Now the kernel issue some files are missing so if anyone can help me,
I'll post a full tutorial from scratch and give ALL the needed files for building
?