yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] endstille:
hey sorry to bother you again, but i think this is my best approach :)

if i try to compile i get this:

marc@nerberd:~/android/kernel/android_kernel_oneplus_msm8974-3.10$ make defconfig
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/zconf.lex.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
*** Default configuration is based on 'versatile_defconfig'
#
# configuration written to .config
#
marc@nerberd:~/android/kernel/android_kernel_oneplus_msm8974-3.10$ make
scripts/kconfig/conf --silentoldconfig Kconfig
WRAP arch/arm/include/generated/asm/auxvec.h
WRAP arch/arm/include/generated/asm/bitsperlong.h
WRAP arch/arm/include/generated/asm/cputime.h
WRAP arch/arm/include/generated/asm/current.h
WRAP arch/arm/include/generated/asm/emergency-restart.h
WRAP arch/arm/include/generated/asm/errno.h
WRAP arch/arm/include/generated/asm/exec.h
WRAP arch/arm/include/generated/asm/ioctl.h
WRAP arch/arm/include/generated/asm/ipcbuf.h
WRAP arch/arm/include/generated/asm/irq_regs.h
WRAP arch/arm/include/generated/asm/kdebug.h
WRAP arch/arm/include/generated/asm/local.h
WRAP arch/arm/include/generated/asm/local64.h
WRAP arch/arm/include/generated/asm/msgbuf.h
WRAP arch/arm/include/generated/asm/param.h
WRAP arch/arm/include/generated/asm/parport.h
WRAP arch/arm/include/generated/asm/poll.h
WRAP arch/arm/include/generated/asm/resource.h
WRAP arch/arm/include/generated/asm/sections.h
WRAP arch/arm/include/generated/asm/segment.h
WRAP arch/arm/include/generated/asm/sembuf.h
WRAP arch/arm/include/generated/asm/serial.h
WRAP arch/arm/include/generated/asm/shmbuf.h
WRAP arch/arm/include/generated/asm/siginfo.h
WRAP arch/arm/include/generated/asm/sizes.h
WRAP arch/arm/include/generated/asm/socket.h
WRAP arch/arm/include/generated/asm/sockios.h
WRAP arch/arm/include/generated/asm/termbits.h
WRAP arch/arm/include/generated/asm/termios.h
WRAP arch/arm/include/generated/asm/timex.h
WRAP arch/arm/include/generated/asm/trace_clock.h
WRAP arch/arm/include/generated/asm/types.h
WRAP arch/arm/include/generated/asm/unaligned.h
CHK include/generated/uapi/linux/version.h
UPD include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
UPD include/generated/utsrelease.h
Generating include/generated/mach-types.h
CC kernel/bounds.s
gcc: error: unrecognized argument in option ‘-mabi=apcs-gnu’
gcc: note: valid arguments to ‘-mabi=’ are: ms sysv
gcc: error: unrecognized command line option ‘-mlittle-endian’
gcc: error: unrecognized command line option ‘-mapcs’
gcc: error: unrecognized command line option ‘-mno-sched-prolog’
/home/marc/android/kernel/android_kernel_oneplus_msm8974-3.10/./Kbuild:35: die Regel für Ziel „kernel/bounds.s“ scheiterte
make[1]: *** [kernel/bounds.s] Fehler 1
Makefile:873: die Regel für Ziel „prepare0“ scheiterte
make: *** [prepare0] Fehler 2
marc@nerberd:~/android/kernel/android_kernel_oneplus_msm8974-3.10$

PS: i can compile complete cm13 without a problem so i guess all generally needed tools are already installed.

Any idea :confused:

Thanks for your help!

Kind regards Marc
[ONE Original Android Development] bobglaus:
Hey so here's the issue with ROM compiling. Read the comments. https://github.com/TipsyOs-Devices/...mmit/4b62fd0f433f72267a0e0114dd81b5de0eee02d0 also the other thing I had was that and that on aosp based roms I had to bring in cm hals. Idk if thats what fixed my issue or what but that's what I did and it works now

---------- Post added at 07:10 PM ---------- Previous post was at 07:10 PM ----------

Also there's a commit where we disabled it but preferably getting it fixed instead of disabled would be better
[ONE Original Android Development] erorcun:
[MENTION=4228949]endstille[/MENTION]

You didn't read my post carefully, I said 'make bacon_defconfig'

Also I don't know are you compiling it with rom, but as I said, you should compile it seperately.
[ONE Original Android Development] endstille:
sorry for not reading carefully.

naaa, I'm compiling in completely separate path, independent from cm13.

i tried make bacon_defconfig && make but it's the same result. Thanks for your help anyway :)
[ONE Original Android Development] erorcun:
:/ Then I don't know the problem, sorry. Np.
[ONE Original Android Development] erorcun:
For the people who haven't seen it yet, in last week;

OTG and 10-sec flash is fixed

Issues in charging fixed / charge speed increased (there were errors from oppo again)

Touchscreen latency is improved (today pushed something about that too)

And I just pushed a commit that blocks touchscreen events to light button backlight. (Only nav. buttons activates it) It was disturbing so mandatory for me. (configurable but enabled by default - it's better than boeffla's one so only thing it does is preventing touch event, doesnt interfere CM brightness settings)

I don't put zip because there are still critical bugs (unresponsiveness and power system related reboots)
[ONE Original Android Development] endstille:
i took some thoughts into this and i'm sure the problem is my compiler / toolchain (as i'm running debain sid and therefore gcc 5.1 i guess).

i googled a little bit and found this: https://source.android.com/source/building-kernels.html

Am i right to export the path and toolchain variables to the cm13 paths? if so, are i guess i can see the needed ARCH and so on if i "breakfast bacon" in CM tree, right?

thanks again :fingers-crossed:
[ONE Original Android Development] abhibnl:
Man the speed at which the development is moving is great!! Just 1-2 months and i hope it'll get stable.
[ONE Original Android Development] erorcun:
[MENTION=4296062]abhibnl[/MENTION]

I hope so.

[MENTION=4228949]endstille[/MENTION]

I'm busy right now, will reply tomorrow.

---

Ok guys, I think all the unresponsiveness issues, all filesystem related and power system related reboots, sleep failures and livedisplay calib. mismatch should be fixed.

I've simply synced filesystem-system, power system, cpufreq and interactive governor with LA.BF64.1.2.2 which is known as the base of xperia's kernel. Also synced f2fs with latest version.

Also I must say, this version's power consumption is a lot better then 3.4 tuned boeffla kernel for me.

https://www.mediafire.com/download/hdpce28pp3d3ctk

Also putting to OP now. Feedbacks are welcome (and very needed)
[ONE Original Android Development] usmani:
The funny thing is, now for the first time I'm having unresponsive screen and mobile hanging with your kernel. How do I get logs for this?
[ONE Original Android Development] endstille:
@ compile: no stress, i'm gratefull for every idea, but don't expect anything :)

@ kernel: sounds great! i've just installed it and can agree after some minutes of usage. gonna report back this evening or so :) :good:

cheers
[ONE Original Android Development] corando98:
Since the ramdisk is based on cm13, apart from nightlies what other rom are people who use this kernel using?
[ONE Original Android Development] erorcun:
No need to get log, I have already. thermal driver was always giving errors about cpufreq, I thought it points to cpufreq but it seems problem's itself was inside of thermal, it should be fixed now.(in repo) all thermal errors disappeared from log.

You can look to previous pages.
[ONE Original Android Development] spanish33:
No reboots so far for me on 17th June version

Sent using XDA One
[ONE Original Android Development] CooperBrick:
touch not responsive on latest nightly
[ONE Original Android Development] erorcun:
I use 03/06 nightly, there might be something new
[ONE Original Android Development] Miksel12:
Newest build is pretty amazing, battery drain is gone for me and performance is great.

While playing games it stays incredibly cool. Great job [MENTION=4898631]erorcun[/MENTION]!

PS: I'm using Jgcaaps CM13.
[ONE Original Android Development] zipperX:
So it doesnt break the camera?
[ONE Original Android Development] Miksel12:
Yes it does but that is not a problem for me really.
[ONE Original Android Development] kanyazsombor:
It's ok that not problem for you, but if you don't mention it, you kind of mislead others. Of course you can't test everything about a kernel, but camera is quite important on a smartphone (even if you don't use it).

So in a development thread would be good to mention if something so basic feature is broken, even though everything else is perfect.

Thanks!
[ONE Original Android Development] plantator:
Does it support f2fs on data and cache?

Tried flash on RR latest, bootlop

NVM booted first rom then flashed kernel.
[ONE Original Android Development] erorcun:
[MENTION=4228949]endstille[/MENTION]

I'm back, I'm pretty sure this kernel won't be compiled with gcc 5.1, it needs modification, you should use 4.8.

You can export toolchain paths to anywhere that has gcc 4.8, it doesn't matter.

You don't need to set ARCH on this kernel.

Also breakfast command is used only for ROMs, only thing you need is 'make' in here.
[ONE Original Android Development] Miksel12:
I can understand that but it's known that jgcaap uses other cam libs so it's not a short comming of the kernel, even other (normal) cm13 kernels dont have working cam on jgcaaps builds.

But I understand it can misleading, sorry.
[ONE Original Android Development] erorcun:
This kernel has ALL the things 3.4 kernel has - except some problems about headset buttons.
[ONE Original Android Development] plantator:
I don't use it anyway:P Can have a litlest request? Can you add vibration strenght control?
[ONE Original Android Development] erorcun:
Oops, I forgot that :P I will add tomorrow.
[ONE Original Android Development] Spider-Vice:
To think that less than a month ago we still had sound problems. What an amazing progress with this kernel! Can't wait for it to be stable enough for someone to port CAF/Sultan camera libraries so it's compatible with other ROM's that use it.
[ONE Original Android Development] erorcun:
Thanks =) I will begin making my custom kernel for both CM/CAF this summer and they will be updated weekly. (Also they will have some unique features which none of other kernels have) Let's see what's gonna happen :whistle:
[ONE Original Android Development] plantator:
Forn now all good on latest RR, it performs much faster than any kernel,will stick with it as daily one qnd test battery
[ONE Original Android Development] Raagh:
Could someone post the lastest kernel from a different source? I cannot download this from mediafire
[ONE Original Android Development] abhibnl:
That is some great news!! Waiting for a Sultan CAF version of this kernel to test.
[ONE Original Android Development] endstille:
definitly yes, as i'm using it on f2fs :)

---------- Post added at 08:36 AM ---------- Previous post was at 08:28 AM ----------

@erorcun i have a little understanding issue :)

I'm back, I'm pretty sure this kernel won't be compiled with gcc 5.1, it needs modification, you should use 4.8.

> check, i totaly agree

You can export toolchain paths to anywhere that has gcc 4.8, it doesn't matter.

> i'm not sure here: do you mean i can export whatever i want, it has no affect and therefore doesn't matter, or that i can export anything i want (and therefore doesn't matter) i should work?

i'm just reverting my build-machine back to debain stable (made an image some weeks ago, before switching to debian sid). gonna try a little more.

You don't need to set ARCH on this kernel.

> good to know, thanks :)

Also breakfast command is used only for ROMs, only thing you need is 'make' in here.

> of course, what i meant was, to run breakfast to get some variables which i should export, but that was wrong, never mind it :)

thanks for all your time again and thanks for this awesome kernel!!

PS: last night, i had a random reboot, before getting in my car to drive home, navigation was active already (17.06th version). but i'm not 100% sure if i simply kept my fingers on the power button while loading the car or something... i did not happen before or again.

EDIT: i guess i finally did it! i had to export the PATH and a prefix for the files to be used:

$ PATH=~/android/cm13/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/:$PATH

$ export PATH

$ export CROSS_COMPILE=arm-eabi-

now it is cooking :)
[ONE Original Android Development] pankspoo:
[MENTION=4898631]erorcun[/MENTION] its very hard to download files from mediafire!

Any other link plz specifically androidfilehost
[ONE Original Android Development] raja4sure:
I think this would help
[ONE Original Android Development] Leicxan:
[MENTION=4898631]erorcun[/MENTION] Today is my first time follow a tutorial to complete kernel, I complete it with GCC 4.8, finally i got a zImage file.

But i don't know how to build the boot.img. I use Android image kitchen and use it to unpack Stock cos13.1's ramdisk, i modify it as you remind in OP. And repack the ramdisk with the new zImage file. Now i get the new boot.img file and flash on my OPO, pretty fine till now.
[ONE Original Android Development] fritzcola:
Normally you use the command "make bootimage" to build boot.img
[ONE Original Android Development] erorcun:
Yeah it's like that, congrats. But don't forget to look boeffla's build script(bbuild.sh) for dtbtool and mkbootimg parameters.

[MENTION=5326976]pankspoo[/MENTION]

I will think that.

[MENTION=4228949]endstille[/MENTION]

Congrats!
[ONE Original Android Development] DerRomtester:
Next big step would be the Linux mainline kernel. :) This is already a huge big step what you and Sultan have done.
[ONE Original Android Development] Spider-Vice:
I wonder if the call stuff can't be fixed by backporting something from 3.4. Sure it wouldn't be pure 3.10, but would definitely make it usable for the time being.
[ONE Original Android Development] erorcun:
Most of sound system already ported and adapted to 3.10, i will look for other part sometime (qdsp6v2)
[ONE Original Android Development] Spider-Vice:
Yeah, it looks like it's not just in calls, the mic itself isn't working whatsoever, other apps also don't work with it.
[ONE Original Android Development] crisis_trustee:
3.10 is the best kernel!
[ONE Original Android Development] Spider-Vice:
There are definitely differences in performance, can't wait until this is one day perfected. I'd use it as a daily driver if it weren't for the mic stuff.
[ONE Original Android Development] erorcun:
Mic works until you call someone, there is a chaos going on.
[ONE Original Android Development] aukdrck:
Bluetooth and xposed work fine. Only problem I've found so far is the call quality. I barely can here others and others cannot hear my voice clearly.
[ONE Original Android Development] nikhil18:
[MENTION=4898631]erorcun[/MENTION] i have added this commit https://github.com/sultanxda/androi...mmit/b92d210669985b7d9def68dac0c33ea3fb720a5c

but i still cant build the project device tree thanks
[ONE Original Android Development] erorcun:
Compiled DT should be in arch/arm/boot, it's location different from 3.4. DT is already okay, don't use that commit.
[ONE Original Android Development] nikhil18:
so zimage already contains dtb any way to separate the files because i am using anykernel and it repacks zimage and dtb file using dtb tool so i want flash this kernel on other roms thanks
[ONE Original Android Development] erorcun:
At first dtb didn't get created on me too, I solved it by taking LA.BR's some Makefile codes but it's already included in my repo so I don't know what you can do and what causes that :/ but you can solve it I think, because the file is obvious, it's msm8974-14001.dts in arch/arm/boot/dts and you can try compiling it with some external tool etc.
[ONE Original Android Development] DerRomtester:
Check your build script my friend. I think the location of the dtb file has changed.
[ONE Original Android Development] nikhil18:
Found it thanks it was in dts folder I was confused because I saw a line which said nothing to be done for dtbs and I did not see the file get compiled during compilation so I thought the file did not get compiled anyway thanks
[ONE Original Android Development] pankspoo:
O my god what a great development coming to one plus thanks dev for your all hard work.

Will test whrn f2fs and calls bug will be solved

Thanks you again
[ONE Original Android Development] Arju:
This is fantastic, just when I thought this device was getting old and then BAM! Will definitely follow this. Once mic and sound issue gets sorted I'll jump on board. Glad to so soo many kernel devs here helping each other out.
[ONE Original Android Development] Spider-Vice:
I hadn't made any calls when I tested the mic and it wasn't working already so idk.
[ONE Original Android Development] erorcun:
You guys can try picking CM commits for sound/soc/msm/qdsp6v2 dir. btw, I haven't touched there and I think sound problems' cause is that. And I won't be able to do that for a few weeks.
[ONE Original Android Development] Spider-Vice:
Now I wish I could build kernels. :p
[ONE Original Android Development] nikhil18:
actually mics are not at all working and there is nothing in dmesg which can pinpoint the problem maybe [MENTION=4800121]Sultanxda[/MENTION] can help us out on this
[ONE Original Android Development] DerRomtester:
Only if you use the cm build system. Not everyone wants to sync the hole source.
[ONE Original Android Development] endstille:
Thanks for this, dude it worked for me as well!

First I compiled using linaro tolchain but got in stand reboots after entering pin.

Then I compiled using cm tolchain and it worked.

But I got two reboots already, one after trying to write this in my mobile Firefox and another after entering a wrong pin after the first reboot.

Maybe its due to yesterday's git change, I don't know.

Cheers
[ONE Original Android Development] Leicxan:
I forgot to complete dt.img. So i faced some strange problem.:eek: Maybe i should recomplete the kernel with DT. It seems the dt.img doesn't complete after i complete the kernel.
[ONE Original Android Development] Raagh:
Amazing kernel cannot wait for a cos13.1 compatible version of this :)
[ONE Original Android Development] hawktalon:
Flashed the kernel. Responsiveness is SO much better but the battery life is alot worse. Cell standby takes 55% of the battery tho. 2 hours screen on time and I'm down to 35% already. Will continue testing. Thanks for the effort!
[ONE Original Android Development] nikhil18:
Its related to your rom or app wakelocks
[ONE Original Android Development] endstille:
yeah i think i just solved this, as i've seen it as well.

here my complete personal howto, all needed steps should be included (ink. dtb)

################# TOOLCHAIN #################
## cm13 ##
marc@nerberd:~/android/kernel/android_kernel_oneplus_msm8974-3.10$
export PATH=/home/marc/android/cm13/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin:$PATH
export CROSS_COMPILE=arm-eabi-

## UBER ##
export PATH=/home/marc/android/toolchain/arm-eabi-4.9/bin:$PATH
export CROSS_COMPILE=arm-eabi-

make bacon_defconfig
make -j8
./dtbToolCM -2 -o /home/marc/android/kernel/android_kernel_oneplus_msm8974-3.10/arch/arm/boot/boot.img-dtb -s 2048 -p /home/marc/android/kernel/android_kernel_oneplus_msm8974-3.10/scripts/dtc/ /home/marc/android/kernel/android_kernel_oneplus_msm8974-3.10/arch/arm/boot/dts/
#mv /home/marc/android/kernel/android_kernel_oneplus_msm8974-3.10/arch/arm/boot/zImage /home/marc/android/kernel/android_kernel_oneplus_msm8974-3.10/arch/arm/boot/boot.img-zImage

################# AIK-Linux #################
unpack image
./unpackimg.sh boot.img
cp arch/arm/boot/zImage ~/android/AIK-Linux/split_img/boot.img-zImage
./repackimg.sh
rm boot.img
mv image-new.img boot.img
repack
./cleanup.sh

## DONE ##

hope it help.

cheers Marc

PS: just realized, UBER kills whatapp, better stick with default gcc
[ONE Original Android Development] Mecca EL:
Here's a log of the past hours activities. Hope this helps - https://www.dropbox.com/s/zboh49ybx0ud2i1/2016-06-19-18-44-54.txt?dl=0
[ONE Original Android Development] Leicxan:
Thank you. Now i get the dt.img. Using boeffla's bbuild.sh to pack dt, ramdisk and zimage.

Cheers :victory:
[ONE Original Android Development] Mecca EL:
Here's another log, phone was unresponsive after unplugging from the charge port. Had to do a power button reboot - https://www.dropbox.com/s/jdnp7ltf3z5casu/2016-06-19-22-32-06.txt?dl=0
[ONE Original Android Development] erorcun:
Are you using the build from OP?
[ONE Original Android Development] DerRomtester:
The same happend to me yesterday. I did not report it yet because i wasn't able to grab a log yet. I think it has something to do with the prima driver.
[ONE Original Android Development] erorcun:
It seems your repo doesn't contain my thermal commit, which fixed thermal errors that appear randomly and the ones appear in that unresponsiveness - I don't know the unresponsiveness is gone completely, but I think yes.

And yeah, there is many of prima reports these days, so I think it's time to pay attention to prima. I will try 3.10 prima soon.

---------------

Good morning guys. (it's early in the morning in here)

I prepared some zips for CAF camera, will be happy if someone can find does any of them works. =)

Firstly:

http://www.mediafire.com/download/g3dbci25a9xv95x/bacon3.10caftest1.zip

If the above one doesn't:

http://www.mediafire.com/download/wz4oj4ncc96dwgh/bacon3.10caftest2.zip

And of course if none of them works, I'll be happy to see log. (dmesg)
[ONE Original Android Development] DerRomtester:
I dont use my own kernel. I flashed the one from op.

Here is the log i was able to grab one

http://pastebin.com/UsBmGkx7
[ONE Original Android Development] erorcun:
The one on the OP doesn't contain it too.

I'm checking the log now, if I'll see any error about thermal, probably it's the reason.

Edit: I couldn't see anything. The last thermal commit would fix it but I don't know, you should try.

Also do you know why your NFC constantly gives error? I have never ever seen any line that contains "pn544" or "nfc" in my logs.

Edit2: Because I wasn't activating it. Great.
[ONE Original Android Development] DerRomtester:
Ok good i try an up to date version soon.
[ONE Original Android Development] hawktalon:
Running 18th June Nightly. Just had a random reboot. How do I get and submit logs?

Also, I noticed that ever since I flashed this kernel the chinbar buttons (home, back, menu) lights up at times. Did anyone notice this as well?
[ONE Original Android Development] Leicxan:
I noticed this too. Also,i found the button's backlight will turn on after i lock the screen, cover the proximity sensor and double tap the screen. Normally the button's backlight won't turn on.
[ONE Original Android Development] erorcun:
You need root. sys/fs/pstore/console-ramoops

Always on lights was disturbing me (they light up on all touch events) so I restricted it to only buttons. It's best implementation available for bacon but there could be bugs though. (Currently it's possible to disable it only in compile time btw)
[ONE Original Android Development] iker_92:
[MENTION=4898631]erorcun[/MENTION] Tested the two CAF zips on 17/06 RR..first one back camera okay but front give FC, second one FC for all cameras
[ONE Original Android Development] Naresh Rawat:
Does this kernel worked on the latest build of RR (20160617)??????
[ONE Original Android Development] erorcun:
You just tested universal camera drivers which works on both CAF and CM, congrats =) (there are still some bugs though)
[ONE Original Android Development] iker_92:
Yes like a charm
[ONE Original Android Development] Shadowghoster:
[MENTION=5491297]iker_92[/MENTION] why you test CAF Zips on RR which isn't based off the CAF camera HAL? Camera should work with this kernel naturally on RR.
[ONE Original Android Development] erorcun:
...

I hope someone can test those zips on CAF camera.