Database Info

Git repository for kernel

Created a git repository for the kernel for easier collaboration in the future, plus Acer's download site is pretty slow.
Link: https://github.com/pawitp/android_kernel_acer_t30
Compiler: Use gcc 4.6 from AOSP Jellybean prebuilts
Compiling
Code:
export ARCH="arm"
export CROSS_COMPILE="/path/to/arm-eabi-4.6/bin/arm-eabi-"
make picasso_mf_defconfig
make -j4 zImage modules
Then you can flash the zImage with the extracte stock ramdisk using fastboot
Code:
fastboot flash:raw boot /path/to/zImage /path/to/ramdisk.gz

the good one
Link: https://github.com/pawitp/android_kernel_acer_t30

Thanks, I changed the url but forgot to update it.

no trouble, just to help
hope that you'll have a working tab soon, we should set-up a petition online to badger Acer to get nvflash

Is the kernel published here the same as on acer's website?
Is the one published on the acer's website the same that runs on the A700/A701 tablets now in fw 15 and 17?
Did you find what locks the system remount in the sources, or that's something acer added after they've published the sourcecode to the website?

andlommy said:
Is the kernel published here the same as on acer's website?
Is the one published on the acer's website the same that runs on the A700/A701 tablets now in fw 15 and 17?
Did you find what locks the system remount in the sources, or that's something acer added after they've published the sourcecode to the website?
Click to expand...
Click to collapse
It's the source imported from Acer's source site, with modification as seen in the git history. I'm not aware of any new kernel release from Acer. The remount block is something not present in the source (which would be a violation of GPL on Acer's part).

pawitp said:
It's the source imported from Acer's source site, with modification as seen in the git history. I'm not aware of any new kernel release from Acer. The remount block is something not present in the source (which would be a violation of GPL on Acer's part).
Click to expand...
Click to collapse
Thanks for clarification.
In this post: http://forum.xda-developers.com/showpost.php?p=31105735&postcount=5 you say there is a kernel block.
I'm determined to have root with ability to remount (for adfree to work at least)
Any ideas how to proceed?

MT6516 kernel and other files

Find here the source code of MT6516 kernel and other important files.
Kernel source code MT6516:
http://sourceforge.net/projects/alcatel/files/?source=navbar
Select this file: OT_890D_20120725.tar.xz

ajparag said:
Find here the source code of MT6516 kernel and other important files.
Kernel source code MT6516:
http://sourceforge.net/projects/alcatel/files/OT_890_20120110.tar.xz/download
More coming up soon
Click to expand...
Click to collapse
can this unbrick my phone????
what to do after downloading this??

ajparag said:
Find here the source code of MT6516 kernel and other important files.
Kernel source code MT6516:
http://sourceforge.net/projects/alcatel/files/OT_890_20120110.tar.xz/download
More coming up soon
Click to expand...
Click to collapse
Hi.
The above sources are total incomplete for the mt6516 Platform.
It miss several important Files like the makeMtk Perl Script.
I am looking my self for the mt6516 Linux Kernel Sources now for several weeks to rebuild the Linux Kernel for my self.
If somebody has the complete linux source for the mt6516 please tell it me.
Thanks in advance.

ARAN said:
Hi.
The above sources are total incomplete for the mt6516 Platform.
It miss several important Files like the makeMtk Perl Script.
I am looking my self for the mt6516 Linux Kernel Sources now for several weeks to rebuild the Linux Kernel for my self.
If somebody has the complete linux source for the mt6516 please tell it me.
Thanks in advance.
Click to expand...
Click to collapse
Try this link: http://sourceforge.net/projects/alcatel/files/?source=navbar
From here download this version - OT_890D_20120725.tar.xz
ATB!

Kernel source tree location for the capacitative touch keys

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.

How to get kernel source for specific Qualcomm msm board

I have studied the google's official documentation and I got the source with this command
$ git clone https://android.googlesource.com/kernel/msm
Now how can I get kernel source for specific Qualcomm Board like msm8994 or any other board

yuvraj_reckon said:
I have studied the google's official documentation and I got the source with this command
$ git clone https://android.googlesource.com/kernel/msm
Now how can I get kernel source for specific Qualcomm Board like msm8994 or any other board
Click to expand...
Click to collapse
You would need to look for the stock source used in the stock firmware from the manufacturer or carrier of the specific device in question.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

git branch -a in the msm directory will give you the list of branches for particular boards / Kernel. you can checkout one of those branches using git checkout <branch name>

General [info] Xiaomi 13 (fuxi) Open Source Kernel and Lineage Device Tree

Hi all,
For those of you, like me, who are interested in learning more about developing for custom ROMs, the following links will be helpful for finding .
First is the inclusive list of open source kernel releases by Xiaomi: https://github.com/MiCode/Xiaomi_Kernel_OpenSource
At the bottom of said list is the Xiaomi 13 (fuxi).
Second is the device tree (based on Lineage OS and said to be WIP) by YuKongA: https://github.com/YuKongA/device_xiaomi_fuxi

What is the primary difference between official xiaomi 13's device tree https://github.com/MiCode/kernel_devicetree/tree/fuxi-t-oss and https://github.com/YuKongA/device_xiaomi_fuxi ?

YuKongA's contribution is for Lineage OS, or instead of MIUI it's AOSP. I think.

To give additional information, the Lineage-derived device tree likely originates from: https://github.com/imasaru/android_device_tree_template

Also, the kernel includes a lot of stuff for the hardware and is accompanied by a kernel device tree, which is a kind of 'table of contents' (unless I'm mistaken about the analogy).
"The 'Open Firmware Device Tree', or simply Devicetree (DT), is a data structure and language for describing hardware."
Linux and the Devicetree — The Linux Kernel documentation
I imagine a lot of compatibility issues are lining up the system image and the kernel+device tree.
...
(At this point, I'm really just spouting off some things as I'm learning, so feel free to correct or ignore me as I'm going along!)

Aquariuslt said:
What is the primary difference between official xiaomi 13's device tree https://github.com/MiCode/kernel_devicetree and https://github.com/YuKongA/device_xiaomi_fuxi ?
Click to expand...
Click to collapse
1/Xiaomi Kernel OpenSource
2/Xiaomi fuxi prebuilt

Veiranx said:
To give additional information, the Lineage-derived device tree likely originates from: https://github.com/imasaru/android_device_tree_template
Click to expand...
Click to collapse
You can find older ones.