yashsingh1/xdaforums huggingface dataset:
[Android] Nuttapat007:
Hey now i know that my boot.img names KERNEL .But I still have wondered that Is kernel particular to rom(or android versions)?:confused:

And how about toolchains .
[Android] mostafaz:
Rom & kernel talks to each other. They are particular to device hardware. Ie you can't flash a nexus-6p kernel to a samsung-s3 .it won't boot. Different hardware & settings.

There is a file named image or Zimage in boot.img which compiled codes are there.

We use toolchains (compiler) to compile codes to machine language. It's set of tools. Newer one has better options like can found bad code style &etc. Your code should be fixed to use newer toolchains like gcc 7.1.x

It's particular to cpu architecture. Arm 32 or 64 & etc.

There is also toolchains for rom.

For start you can use gcc 4.9.x or 4.8.x .Most of the manufacturer kernel source are compatible with this version & vice versa.
[Android] Nuttapat007:
That mean when i download sourcecode and i want to compile it.I have to use properly configs file for rom such as AOSP ,AOKP,CM

Is it right?:confused:
[Android] mostafaz:
I don't have info for rom but u should have proper toolchains & configuration (for kernel)

For kernel I use proper toolchains & configuration.

Ie I use gcc 7.1 64bit for my on7xelte (Samsung j7-prime) which default configuration for 64 bit is in arch/arm64/config/on7xelte_defconfig.

For 32 bit it's in arch/arm/config/

(I patched/fixed/disable warning in kernel source for gcc 7)
[Android] Nuttapat007:
There're so many toolchain uber,linaro,saber and many versions Can you recommend? :angel:
[Android] mostafaz:
It's like car companies. Some are fast some are energy-efficient. Developers works on it's codes so it's how gcc act with codes.

There is also a base they working on .it's Gnu gcc.

There is some feedback from Uber users which says it's a energy friendly gcc.others can be performance friendly. You may wants to use them to find your match. Just Google them to find correct answer.
[Android] Nuttapat007:
I compiled my kernel and flash it.but it doesn't boot.I try with this toolchains

--sambermod-arm-eabi-4.9

--ubertc-arm-eabi-4.9

Compiled successfully but device doesn't boot.

For configs : I use config files that come with source from opensource.samsung.com

What wrong i do:confused:
[Android] mostafaz:
HI

How and which file you were flashed to device?

How many file created in boot folder ?

Just image or there is also a dtb.img ?

Which model do you have?

Stacked at 1st screen ?
[Android] Nuttapat007:
https://github.com/ih24n69/android_kernel_samsung_kanas

I clone and put my zimage in kernel_zip folder and zip it.

When compiled, only zimage created (sourcecode from opensource.samsung.com)

my device -kanas (sm-g355h)

Finally,my kernel's able to boot. :fingers-crossed:

But why kernel information doesn't show abcd@blablabla of my computer which compiled it.

Do you know what files dump username of pc when compiled? :confused:
[Android] DenZxd:
Hi!

After a successful compilation los12.1, the need arose to compile the old kernel 3.0.31 with new ramdisk. Previously, the kernel was compiled without warnings, now compiles with lots of warnings and after the firmware into your device, it doesn't start.

compile log here:

https://pastebin.com/AmgLrR6g

Primary successful compile log here:

https://pastebin.com/neGWt2UF

Native kernel toolchain is arm-linux-androideabi-4.6

Kernel sources:

https://github.com/DenZxd/android_kernel_sd_x7 -b omap-mr1

config file is panda_X7_defconfig

Why can this be?

And another question: in the log compilation file warnings line does not correspond to the lines in the code files (string number moved down in function. This can be seen by comparing the log and the code). Why can it be? And how to fix it?
[Android] desalesouche:
you have to update/fix kernel according all the warnings. may be some errors come also from kernel toolchain, and i think defconfig need to be updated.
[Android] DiamondJohn:
For my Kernel, the file is: kernel/motorola/msm8960-common/scripts/mkcompile_h

However, just do a search for one of the texts

KBUILD_BUILD_VERSION

KBUILD_BUILD_HOST

KBUILD_BUILD_USER
[Android] DenZxd:
Very strange that I have to do fixes for the kernel, as I have not changed the kernel code after receiving it from the manufacturer. Just added in the config assembly the location of the initramfs. Toolchain I also always take one link:

git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6

and then even tried to download it earlier from different branches (jb-mr0-release). Also tried to install on a virtual machine in older versions of Ubuntu 13.04 and Linux Mint, but also to no avail. I also downloaded an older android source code and tried to use its toolchain, all the same. The result is that the desired toolchain (arm-linux-androideabi-4.6) I can not find and the only solution is just to edit kernel sources and pulling out of the new kernels needed the commits.

2. Still do not understand why after viewing a warning in the log, for example:

arch/arm/mm/dma-mapping.c: In function '__dma_alloc':

arch/arm/mm/dma-mapping.c:238:25: warning: array subscript is above array bounds [-Warray-bounds]

I open dma-mapping.c and function '__dma_alloc' start from line 305 (no 238).

https://github.com/DenZxd/android_kernel_sd_x7/blob/omap-mr1/arch/arm/mm/dma-mapping.c

and redownload kernel sources dont helped in this case.

How do I fix this discrepancy.

(my tablet platform is omap4)
[Android] robcore:
http://bfy.tw/Djof

Some oems are notorious for releasing sources with some slight problems like this. Check out the link to find some solutions for your gcc warning.
[Android] DenZxd:
Hi!

I received kernel sources from manufacturer with no problem in compilation:

https://pastebin.com/neGWt2UF

but long time not compiled kernel because doing cm12.1. And now I have problem with kernel building.

I am try:

change old ubuntu 64 bit version on VM

change NDK version (I try take toolchain from it)

change toolchains

redownload kernel sources

and till do not understand why after viewing a warning in the log, for example:

arch/arm/mm/dma-mapping.c: In function '__dma_alloc':

arch/arm/mm/dma-mapping.c:238:25: warning: array subscript is above array bounds [-Warray-bounds]

I open dma-mapping.c and function '__dma_alloc' start from line 305 (no 238).

https://github.com/DenZxd/android_ke.../dma-mapping.c

and redownload kernel sources dont helped in this case.
[Android] robcore:
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-February/085562.html
[Android] mustang_ssc:
Hey, thanks a lot for your detailed and quick reply, can't say the same about mine :)

After a long time i'm trying to make this work with the advices you gave me. I tried adding this commit you linked me on the makefile from the root directory but i was still facing some issues. Anyway, i will check it more deeper now that i have a better understanding of what causes it thanks to your explanation.

I don't want to seem to be like lazy or exploit your help but unfortunately i searched a lot without finding any answer.

I would like to ask you, or to anyone, this two vital doubts that in case to be answered would help me a lot and save time.

1- I always saw on kernel repos from github they have a huge amount of commits, like this one (android_kernel_huawei_msm8916) which have more than 400 000 commits compared to mine which obviously have nothing as it is the stock kernel source got from the Huawei website.

I guess that this big amount of commits are, besides many colaborations between devs, got importing your new kernel source (my case) on a more worked one (first example) like this case (Import huawei code) where we can see a big amount of speficic kernel files for that device being imported to an existing and worked kernel source.

My question is, should i perform the same importing procedure of my stock kernel source like the last example? I guess this would be most efficient.

2- While compiling my kernel source i noticed that it was failing due to a missing dtsi file which is necessary for the lcd screen of my device (android_kernel_huawei_hwt1a21l/arch/arm/boot/dts/qcom/huawei_t110p0_a21w), so i just used this one and adapted the resolution for my device.

The problem with this lcd screen file which for some reason is not present on the stock kernel source of my device is that i have huge doubts about the possible successfully of the "workaround" i performed since i would probably require the specific one for the screen of my device due to the complexity of the code of this file.

Do you know if it is normal that Huawei did not shipped by default this file for the screen hardware? probably there is nothing to do with this kernel source if this file for my device's screen is not present.

thank you again :)
[Android] rootlinux:
Nice work
[Android] mostafaz:
hi :)

in stock source we can't see what they did with codes bcause there is no history and how they figured stuff out. by importing the stock source over it's mainline you may needs to fix/decide which part of conflicts should keep, your stock source or mainlne code!? i explain it with my last experience with samsung 3.18.y source: samy source was 3.18.14 so i had 2 choice for importing the stock srource, kernel.org and linaro. linaro had more cool codes/feature than k.org but by imporing the stock it has lots of conflict than k.org, by fixing conflicts it's still bugging me about definitions which were not available (i removed them during the conflict fix) so i choose k.org with fewer conflict fix. there is much same commits which needs to just keep them (they are same) so you can use some linux commands to speed it up but it may remove codes from drivers which you needs to cherry-pick them later or not so in this scenario it's better to stay with stock source but by importing it you can have more codes in drivers and by doing "diff" you can find missing codes and merge them later like what i did with "rcu" driver from msm source to my exynos source.

you have a msm board/source so you may do that easier than my exynos, but you will get conflicts with huawei changes which they prefer/decides to have them with your device in some drivers like bt, display which varient from device to device.

you need to import it to same mainline version, i have 3.18.14 so i did with 3.18.14 from k.org then you can merge mainline updates after it.

importing means have manufactory codes in mainline codes. you can see histories and merge or revert commits. it's easier for devs to find solutions or bug hunting. stock source is stable and if you don't want these kind of stuff then no need to import. just use stock source and cherry-pick/merge improved drivers or new drivers like per-process-reclaim in mm or update lowmemorykiller driver. (you may have more codes in drivers which removed by manufatory or even lose them) :)

i've no idea about 2nd question. ask huawei or find same kernel or nearest soc to compare. :rolleyes:
[Android] TheOTO:
I have a question. I'm compiling a kernel of my own and have questions about the cpu governors. I've checked source code for some other kernels and found that the different governors found in /drivers/cpufreq/ are not in the header file > /include/linux/cpufreq.h but they are in both kconfig and makefile. What am I missing? Don't all of the governors have to be in this file? For example Intellimm and conservativex aren't found in the cpufreq.h file.
[Android] mostafaz:
Hi

If they are in cpufreq.h it means you can set them as default gov for boot. Not necessary to have them all in cpufreq.h if you dont want set them for boot. If its in makefile and built so you can use after bootup.
[Android] TheOTO:
Thank you. That helps me a lot.
[Android] Elanza_48:
https://hastebin.com/apobadoxem.rb

modify the toolchain path device_defconfig and execute the lines one-by-one. It solved the same problem of mine.
[Android] DiamondJohn:
I am trying to build a kernel, from a ROM that builds successful with this same kernel, however, when I follow the OP, the following is what I get. fail :crying:

ubuntu@ubuntu-VirtualBox:~/android/kernel/motorola/msm8960-common$ make -j1
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: 'include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CC init/main.o
In file included from init/main.c:75:
/home/ubuntu/android/kernel/motorola/msm8960-common/arch/arm/include/asm/setup.h:245: error: field 'fdt_addr' has incomplete type
scripts/Makefile.build:305: recipe for target 'init/main.o' failed
make[1]: *** [init/main.o] Error 1
Makefile:954: recipe for target 'init' failed
make: *** [init] Error 2

Why would building the kernel on its own trigger an error that building the ROM (with the kernel) would not? I have checked github, and there has been no recent changes to the code.

These are the commands I used to setup my environment: https://www.hastebin.com/uxabiqisun.nginx

These are the commands I used ti kick the build off: https://www.hastebin.com/keyokazeto.nginx

Clearly I have done something wrong, but what?
[Android] Riad khan:
Compiling error

I m facing this while i compiling kernel.. i added hyper governor and its occurs ..hlp sir ..

CC drivers/cpufreq/cpufreq_governor.o
CC net/core/net_namespace.o
CC drivers/cpufreq/cpufreq_blu_active.o
drivers/cpufreq/cpufreq_hyper.c: In function 'dbs_check_cpu':
drivers/cpufreq/cpufreq_hyper.c:825:3: error: implicit declaration of function '__cpufreq_driver_getavg' [-Werror=implicit-function-declaration]
freq_avg = __cpufreq_driver_getavg(policy, j);
^
drivers/cpufreq/cpufreq_hyper.c:844:3: error: implicit declaration of function 'cpufreq_notify_utilization' [-Werror=implicit-function-declaration]
cpufreq_notify_utilization(policy, avg_load_at_max_freq);
^
cc1: some warnings being treated as errors
scripts/Makefile.build:308: recipe for target 'drivers/cpufreq/cpufreq_hyper.o' failed
make[2]: *** [drivers/cpufreq/cpufreq_hyper.o] Error 1
make[2]: *** Waiting for unfinished jobs....
CC drivers/devfreq/devfreq.o
CC net/ethernet/eth.o
CC sound/soc/msm/qdsp6v2/msm-pcm-routing-v2.o
CC net/bridge/netfilter/ebtables.o
CC fs/proc/proc_net.o
CC net/core/secure_seq.o
LD net/ethernet/built-in.o
CC net/ipc_router/ipc_router_core.o
scripts/Makefile.build:455: recipe for target 'drivers/cpufreq' failed
make[1]: *** [drivers/cpufreq] Error 2
make[1]: *** Waiting for unfinished jobs....
[Android] mr.yukenz:
HOTPLUG

how i moddification hotplug?
[Android] marc.2377:
Hi,

I was trying to build Lineage using these:

Device tree: https://github.com/MSM8916-Samsung/android_device_samsung_e53g/tree/cm-14.1
Common device tree: https://github.com/MSM8916-Samsung/android_device_samsung_msm8916-common/tree/cm-14.1
Kernel: https://github.com/Jackeagle/kernel_stock_e53g/tree/stock

From the device tree, I had to edit BoardConfig.mk at line 27 and set TARGET_KERNEL_CONFIG := msm8916_sec_e53g_eur_defconfig.

However, I got error "You must specify VARIANT_DEFCONFIG !".

Then I went back and replaced TARGET_KERNEL_CONFIG with TARGET_KERNEL_VARIANT_CONFIG.

Then I got "Kernel source found, but no configuration was defined - Please add the TARGET_KERNEL_CONFIG variable to your BoardConfig.mk file".

So, I went back and defined both TARGET_KERNEL_CONFIG and TARGET_KERNEL_VARIANT_CONFIG to the same value of msm8916_sec_e53g_eur_defconfig.

Now the kernel won't compile.

After many errors like "forbidden warning" and "implicit declaration of function", I edited the kernel's KBUILD_CFLAGS (in the Makefile) and removed -Werror-implicit-function-declaration. I also had to define -w option to disable all warnings (setting -Wno-error wasn't enough).

Now the build almost reaches the end, but fails with:

media/Fast/Dev/android/lineage/kernel/samsung/e53g/drivers/muic/muic-core.c:14:23: fatal error: mach/irqs.h: No such file or directory
#include <mach/irqs.h>

---

Questions:

1. What is the difference between TARGET_KERNEL_CONFIG and TARGET_KERNEL_VARIANT_CONFIG, and should they be set to the same value?

2. What am I doing wrong - aka, exactly why does my build fail?

Thanks
[Android] marc.2377:
Turns out I was using the wrong kernel branch. I was at branch stock. After checkout branch cm-13.0, there was no need to edit BoardConfig.mk as I did previously, since this branch has file "arch/arm/configs/cyanogen_e53g_defconfig" which is the config file set by default as TARGET_KERNEL_CONFIG.

I figured out I had to add

TARGET_KERNEL_VARIANT_CONFIG := msm8916_sec_e53g_eur_defconfig

as well.

It compiled. I have successfully built my first LineageOS ROM for an ARM device! :D:D:cool:

Too bad my device is broken and I can't actually test it until I can buy a new display :x
[Android] platinumthis:
Can anyone help ?

DTB combiner:

Input directory: ''

Output file: '/home/whitewidow/crDroi/out/target/product/hima/dt.img'

Failed to open input directory ''

=> Found -1 unique DTB(s)

Generating master DTB... error writing output file, please rerun: size mismatch 4096 vs 4120

[ 0% 14/73829] ADSP firmware link: /home/whitewidow/crDroi/out/target/product/hima/root/firmware/image/adsp.b12

ninja: build stopped: subcommand failed.

11:36:12 ninja failed with: exit status 1

#### failed to build some targets (7 seconds) ####
[Android] covar:
Hello

I'm trying to recompile nethunter kernel for onplus5T in order to enable RFCOMM support for bluetooth devices.

I have download the source kernel from here https://github.com/arter97/android_kernel_oneplus_msm8998 (it is a custom kenel) and i have followed the instructions as showed. For some reason export CROSS_COMPILE does not work. Even if i download another toolchain still i have the same problem.

Please help.
[Android] hschabel:
Hi

is it possible to add the following functions to a cell phone:

usb ethernet

USB-Type-C-DisplayPort-Alt-Mode

or are there any vendor specific files, necessary? (e.g. like drivers for windows)

I search for information as I would like to implement and use these functions on my new toy/phone sony xperia xz premium.

I tought about copying/adding the needed files to the existing kernel (Lineage ROM).

Any help is appreciated.

Thank you.

Regards
[Galaxy S III Q&A, Help & Troubleshooting] a2441918:
Hi friends, i would like to kw wat version of s3 comes in uk when got n contraact. Is it the I9300 or other models with dual core processors?? pls help me out
[Galaxy S III Q&A, Help & Troubleshooting] d4fseeker:
UK have 3G network, so the normal international 4core 1GB Ram with model number i9300
[Galaxy S III Q&A, Help & Troubleshooting] a2441918:
In orange too na??
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
ALL uk networks use the same frequency bands with no LTE, ergo all uk s3s are the same as most of the world.

Only LTE carriers have dual core. Which is possibly only in the US
[Android Themes] WhiteBoy997:
First icon set ive ever made, made this to go with my Dark Mint theme. Overall it came out pretty well, all designs have been made from scratch. No copy and pasting here. There are a total of 36 icons along with some alternatives.

Grab the PSD and the icons. PSD is in the pack of icons. Enjoy Everyone!!

Download

BUY ME A DRINK :D
[Android Themes] johnny quest:
looking good man, love your MIUI themes too.
[Android Themes] Edvin73:
My congratulations.The icons look great, try to make some more.It's very nice that you made them, not like tons of people that claim they done it with the copy-paste ****.
[Android Themes] WhiteBoy997:
Thanks bro

Thanks alot bro. Give me requests and ill add more.
[Android Themes] yabbb:
As a designer, I would suggest brighter colors, something that draws the eyes, but as a poster on xda, nice work.
[Android Themes] mugey:
Requests for:

Dropbox

Evernote

Facebook

Foursquare

Instagram

PicFrame

Sportacular

XDA

YouTube

Thanks! :D
[Android Themes] sagi73:
Is possible alternative link?

Dropbox for example?

Thanks
[Android Themes] pa.pn2:
Request

Facebook

Whatsapp

Estrong file explorer
[Android Themes] sunny2303:
query

Will it work on SGN N7000 asylum v.15 (Cm9 based).. thanks :)
[Android Themes] john9:
great share! Thanks.
[Android Themes] jojoost:
How could icons only work on xhdpi?
[Android Themes] kcls:
Nice work bro!
[Android Themes] gametv:
nice work and great icon .. btw whether it be in mdpi (sorry for my bad english)
[Android Themes] Beachbum2049:
Love these.

Request:

Shazzam

Tapatalk

Pulse

AnyDo

Thanks
[Android Themes] revo_65:
These are awesome, nice work.

Just a couple requests:

Flip board

Shazam
[Android Themes] WhiteBoy997:
yes
[Android Themes] MamaSaidWhat?:
Great looking icons. Fantastic work mate :D
[Android Themes] yabbb:
Lol, this.

Pretty sure icons are "backwards compatable"
[Android Themes] ryan1mcq:
Icons are stunning bro, really fresh well done man!

Few requests;

Facebook

XDA

Instagram

Flipboard

Phone alt

SMS alt

TIA ;)
[Android Themes] WhiteBoy997:
a little late on requests, but whatever: here you go bruh
[Android Themes] mugey:
Those are sick! Thanks again! :D
[Android Themes] uhcref:
My congratulations.The icons look great. :D
[Android Themes] pa.pn2:
thx for the update

request for

whatsapp

estrong file explorer

thx dude
[Android Themes] WhiteBoy997:
here you go bro.
[Android Themes] blaah_gwen:
Icon request: SoundHound, App Drawer, Play Books Alt: Play Store, Gmail
[Android Themes] WhiteBoy997:
Been out of the android community for a while, though i'd share some icons with you guys.
[Android Themes] ShaharGelman:
Can you make a mtz file for those icons?
[Android Themes] can7:
sweet icons have a few requests cheers :)

tv show favs

seriesguide x

heatdroid

fotmob

fantasy football buddy

tv guide

dreamdroid
[Android Themes] crojl:
Sweet
[Android Themes] :
+1...

[sent from the squat rack...]
[Android Themes] bagarwa:
Damn, these are sexy. I must learn Photoshop someday. not finding time... :(

Anyway, in the meantime, few requests -

Flipboard, FolderSync, Moola, Titanium Backup, TinyList, Google Talk, Google Authenticator, Play Music, QuickPic, UCCW, WidgetLocker, Latitude, Solid Explorer.

These are the apps on my homescreen 'frequent' page. Would love to have them Supra'd. :good:
[Galaxy S III Q&A, (US Carriers)] vince24L:
Today I got almost 2 hours of on screen time before I hit 3% after 9 hours. So I look in battery in settings and Android System is #1 at 57%! Then screen at 20%' followed by cell standby at 9%.

What is causing android system to take up 57% and cause barely 2 hour on screen time?
[Galaxy S III Q&A, (US Carriers)] Andrew_han:
I had this issue too! after a reboot i havent had this issue agin
[Galaxy S III Q&A, (US Carriers)] drksilenc:
check what google services you have auto syncing. aka g+ calender and contacts those can make it really bad.
[Galaxy S III Q&A, (US Carriers)] droidstyle:
sounds like a rogue app of some sort.
[Galaxy S III Q&A, (US Carriers)] thakrew317:
What's a rouge ap
[Galaxy S III Q&A, (US Carriers)] David Dee:
An app that misbehaves: Sync's data or runs in the background when you are not using it, wakes device during sleep (wakelock) and performs background operations. This could be any app or game you download, usually it is more common in free apps with unknown developers....make sure to check reviews before downloading.
[Galaxy S III Q&A, (US Carriers)] vince24L:
It seems like the restart fixed it. After restart android system is 4th place at only 6%.
[Galaxy S III Q&A, (US Carriers)] vince24L:
Its doing it again today. 67% of battery is android system.

Any help?

I have better battery stats but it's some what hard to understand.
[Galaxy S III Q&A, (US Carriers)] vince24L:
I think it's bam_dmux_wakelock ...what is this?
[Galaxy S III Q&A, (US Carriers)] jiggytom:
I've got the same wakelock...no idea what it is. Not much information online.
[Galaxy S III Q&A, (US Carriers)] jasvncnt1:
Same here, killing battery. Haven't found much info for it

Zepp's V6 SuperCharger...I put that **** on everything
[Galaxy S III Q&A, (US Carriers)] Tenkie:
Yeap...I get bam_dmux_wakelock & smdcntl0 wakelock alot...

We should post in the BBS thread to get other peoples inputs... http://xdaforums.com/showthread.php?t=1179809&page=612