yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] erorcun:
I've already added it and I've assumed it works but it seems it doesn't. So it's a bug.

It highly depends on device's own drivers, so there isn't too much thing CAF can do.
[ONE Original Android Development] Blackscorpion3:
Yes, usbOTG is still not working. But if you think you have it fixed on another build, I'll try it out.
[ONE Original Android Development] Mecca EL:
This kernel is super responsive!!! Thank you all who have contributed. Is Swipe to Wake active for anyone?
[ONE Original Android Development] Blackscorpion3:
I second this...swipe to wake would be a very welcome addition.
[ONE Original Android Development] kryshnakishore:
good that it worked for RR ROM, for changing settings which app are u using? kernal auditor?
[ONE Original Android Development] DerRomtester:
This aim is not to add random features. We want it to become stable and if it's ready other developers can pick up this kernel and do their magic. And I think [MENTION=4898631]erorcun[/MENTION] thinks the same about this.

1. make it stable

2. implement all features that are on the cm nightlys

3. fix bugs (refers to 1)

Guy have you tried switching to the conservative cpu governor?

Does it go down to 300mhz?

Sometimes the CPU goes crazy i think. Staying at max freq with zero or low cpu load. Or is it a bug with my Builds?

Also the cpu load showed up in kernel adiutor higher than 100% e.g. 135.
[ONE Original Android Development] usmani:
Would someone be kind enough to post a build with latest changes?
[ONE Original Android Development] Hingbong:
is there a bug that is Notification Bar can not pull down? in cm nightly build,my opo has this issue.
[ONE Original Android Development] abhibnl:
Thanks for the info. I hope all the device drivers will be compatible with the upstreamed kernel.

Sent from OnePlus One
[ONE Original Android Development] Thomson2412:
Holy crap dude can't believe I never noticed this thread until now. Great work this is really inspiring. Keep it up and hope you enjoy doing it :)
[ONE Original Android Development] DerRomtester:
No Problem with 29 nightly
[ONE Original Android Development] geowolf1000:
Has reported from other members with stock kernel
[ONE Original Android Development] erorcun:
I think same my friend.

I've never tried consarvative, so I can't say anything.
[ONE Original Android Development] Hingbong:
do you clean flash it?

because I delete CyanogenSetupWizard,it makes the issue appare.
[ONE Original Android Development] plantator:
Her [MENTION=4898631]erorcun[/MENTION] I'm facing bad bug in your and [MENTION=4633983]nikhil18[/MENTION] 3.10 kernel- my flashlight stops working after 9secs after launching, tested with your kernel, nikhil one, with 4 versions of resurection remix rom and always the same, on lightning v21 there is no problems, here i post my logs, mayby they will help: http://xdaforums.com/showpost.php?p=67067984&postcount=7782
[ONE Original Android Development] tekanina:
Experienced the same issue last night.
[ONE Original Android Development] erorcun:
I've experienced the same thing once too. I will fork QCOM's power hal and edit it it seems.
[ONE Original Android Development] aukdrck:
Running fantastic for last few days. Feels like gliding on butter. SOT is around 5hrs which is very good for me. Only problem is that friends complained low mic volume when in a call. Is there any way to increase the in-call volume? Other than that this is one hell of a kernel and can't wait to see the final release with all the fixes. Thanks a lot for the hard work mate.
[ONE Original Android Development] erorcun:
Thanks :)

I'll investigate this issue. Currently there are a few ways you can go through. One of them is that: https://forums.oneplus.net/threads/fixed-for-good-microphone-issue.222059/
[ONE Original Android Development] droppinbaums:
Changed over to this kernel yesterday and have only had one random reboot. Rebooted in the middle of a call. Other than that, kernel is extremely fluent and has battery life similar to the CM nightly stock kernel.
[ONE Original Android Development] imam.krismanto:
kernel working fine on aicp rom, but aicp extra is fc.. i don't know why..
[ONE Original Android Development] DerRomtester:
Please a grab log next time.

---------- Post added at 06:47 AM ---------- Previous post was at 06:46 AM ----------

This kernel +its ramdisk are designed for cm nightlys.
[ONE Original Android Development] bobglaus:
heres the error i spoke of earlier compiling inline with the rom. any help would be appreciated. im just starting to look at it now http://hastebin.com/guwicefowu.js
[ONE Original Android Development] usmani:
anyone?
[ONE Original Android Development] raja4sure:
[MENTION=4898631]erorcun[/MENTION] Awesome work mate. I thought 3.10 was dead since sultanXDA left the project. But you did wonders. I am glad that you proved me wrong.

[MENTION=4804871]DerRomtester[/MENTION] [MENTION=4511190]iD PropheCy[/MENTION] [MENTION=4633983]nikhil18[/MENTION] Great work guys. You are helping many out here by compiling latest commits from erorcun.

The Kernel is fast and awesome . I've been using it since the first Test release and its certainly getting better and better over time.

I was having the same issue before. Try updated kernel compiled by DerRomtester. You can find it 4 pages back.

See Above.
[ONE Original Android Development] erorcun:
Some of them is easy to fix but I'm not sure about others. I'll look at it this summer.

You can try to fix it by comparing 3.4 v4l2 and 3.10 v4l2.
[ONE Original Android Development] DerRomtester:
Grabbed a log with the flashlight turning off after around 10 seconds maybe this is helpful.

https://drive.google.com/file/d/0B4NfU3dQXHeiNUt3aHI3b1ZBZzg/view?usp=drivesdk
[ONE Original Android Development] erorcun:
Did you disable mpdecision?
[ONE Original Android Development] DerRomtester:
I don't know anymore. I disabled it for testing purpose but I am currently not running that anymore because all cores running are producing much heat. Does that matter?
[ONE Original Android Development] erorcun:
I thought powerhal-mpdecision was causing it first (because of powerhal error messages in someone's log) but after I looked to your log I tried it on me too and now I'm happy to learn it's not related with powerhal :P

I think it will be easy to fix, i will see what i can in next days.
[ONE Original Android Development] DerRomtester:
Yeah good that it's not the powerhal. :)

I found that out, too after reading my log. It is always just a small simple thing and you need hours to find and fix it.
[ONE Original Android Development] erorcun:
Hehehe it's true.
[ONE Original Android Development] erorcun:
Today I fixed phone's warming up, it was due to GPU. Now it's okay and battery consumption is lower also (there is a new change in ramdisk too but it's unrelated with this)

I will focus on selinux and flash after now.

Zip is coming in a min. Zip is up.
[ONE Original Android Development] plantator:
Going to test on RR, is flashlight hard to solve? need any logs or smthing?

And whats wrong with sellinux for now?
[ONE Original Android Development] erorcun:
It freaks out if there is some broken file on your system.

There is nothing on logs about torch, so no thanks, i will try to fix it by comparing camera drivers.
[ONE Original Android Development] plantator:
Okay, now waiting for your fixes, then for [MENTION=4633983]nikhil18[/MENTION] port with his features and will be best kernel, even now rom is faster than normal nikhil's v21 3.4 kernel :P but i love many settings in synapse:P

Great work!
[ONE Original Android Development] Blackscorpion3:
The same link that's in the OP?
[ONE Original Android Development] erorcun:
Yep.
[ONE Original Android Development] Blackscorpion3:
Thanks, Boss. Just wanted to double check.
[ONE Original Android Development] erorcun:
[MENTION=4804871]DerRomtester[/MENTION]

Does your display still flicker with my latest commit?
[ONE Original Android Development] Hingbong:
I see your source code is updated,will you make a flushable zip?
[ONE Original Android Development] DerRomtester:
I did not try it yet. I disabled pwm completely.
[ONE Original Android Development] erorcun:
Yeah I saw, can you try it sometime?
[ONE Original Android Development] DerRomtester:
Yes i just need to boot into my ubuntu and recompile.

Seems working so far but i need to wait until i am in bed :)

Uploaded it for you guys if you want to flash.

Sry Ramdisk is ****ed up.

It works btw. if i did not meantion it already.
[ONE Original Android Development] erorcun:
[MENTION=4804871]DerRomtester[/MENTION]

Ok, thanks. I changed it one more time but it'll work still probably.

----

I updated repo today. There are improvements mostly for touchscreen&backlight but there are some for workqueue and msm-thermal too.

And I reverted back to old touchscreen firmwares, because their battery consumption side was superb for me ^^

Test zip: http://www.mediafire.com/download/k8avsrejpkne8in/bacon3.10(2).zip

Also on OP.
[ONE Original Android Development] DerRomtester:
Ok flashing soon. Have you noticed any major Bugs?
[ONE Original Android Development] erorcun:
No, except 10-sec flash and otg.
[ONE Original Android Development] Leicxan:
i flashed latest 0607 kernel and stuck at oneplus boot logo. Revert to 0602 kernel it works fine. I'm on cos13.1 ZNH2KAS1KN.
[ONE Original Android Development] erorcun:
Omg has it released o_O

This kernel is designed for nightlies, I will prepare one for cos soon.
[ONE Original Android Development] Leicxan:
Yes, i flashed it yesterday.It works like a charm.:laugh:
[ONE Original Android Development] iker_92:
on 06/06 RR last kernel works great!
[ONE Original Android Development] erorcun:
10-sec torch fixed. (in repo)
[ONE Original Android Development] Arju:
You are amazing!!!
[ONE Original Android Development] idprophecy:
Here is anykernel version with latest changes compiled few minutes ago.

DOWNLOAD LINK

EDIT #3:

Will build with ramdisk changes soon.
[ONE Original Android Development] DerRomtester:
Have you included the ramdisk changes from op?

Edit:

Have you noticed that the device sometimes becomes very unresponsive. It freezes almost and does react very slowly. Also when I do press the power button it takes about 10 seconds until the screen goes off. So. Times only pressing the power button works. I wasn't able to grab a log yet because it does not happen quite often maybe once a day or once two days.
[ONE Original Android Development] erorcun:
No, it has never happened to me, hope I can see it. I think there are some missing commits in cpufreq, I will look at there sometime.
[ONE Original Android Development] Mecca EL:
I can confirm this. Had to go back to using the first kernel you compiled [MENTION=4804871]DerRomtester[/MENTION]
[ONE Original Android Development] Miksel12:
I have used 7/6 build for a day now and performance is really good, it's fast and responsive. Only downside is the battery drain, it's better than the first builds but still very noticable.

Also sound sounds different, has that been changed?
[ONE Original Android Development] DerRomtester:
There are still some things i dont like to see in the logs:

The battery **** takes alot of time so booting is quite slow:

http://pastebin.com/KSvyxaig

Full dmesg:

http://pastebin.com/1pZmH4kk
[ONE Original Android Development] erorcun:
Lines other than wcnss and battery appear on CM too. Wcnss warnings are harmless but must be fixed ofcourse.

Our qpnp-charger has some new features-checks, battery lines may be related with it or it can be some missing sensor simply. It's in my mind. Will look it after cpufreq.

No, it hasn't been touched after I've fixed mic.
[ONE Original Android Development] updateing:
Hi,

I'm running this kernel (bacon3.10(2).zip from OP) through kexec from CM kernel (20160528 nightly with hardboot patch). In this build, I found that the phone stayed awake through the night, and event0/event2/event3 held the wakelocks.

Here is the result of getevent when the screen is off. It seems that event0/2/3 is sending key events every ~3 secs when screen is off. This does not happen when screen is on or charger is plugged in. I captured this output by adb over WiFi, but it will produce the same result if I run the command on the phone with a terminal emulator.

root@bacon:/d # getevent
add device 1: /dev/input/event4
name: "msm8974-taiko-mtp-snd-card Headset Jack"
add device 2: /dev/input/event3
name: "msm8974-taiko-mtp-snd-card Button Jack"
add device 3: /dev/input/event1
name: "qpnp_pon"
could not get driver version for /dev/input/mice, Not a typewriter
add device 4: /dev/input/event2
name: "gpio-keys"
add device 5: /dev/input/event0
name: "synaptics-rmi-ts"
/dev/input/event3: 0000 0000 00000001
/dev/input/event2: 0000 0000 00000001
/dev/input/event0: 0000 0000 00000001
/dev/input/event3: 0000 0000 00000001
/dev/input/event2: 0000 0000 00000001
/dev/input/event0: 0000 0000 00000001
/dev/input/event3: 0000 0000 00000001
/dev/input/event2: 0000 0000 00000001
/dev/input/event0: 0000 0000 00000001
/dev/input/event3: 0000 0000 00000001
/dev/input/event2: 0000 0000 00000001
/dev/input/event0: 0000 0000 00000001
/dev/input/event3: 0000 0000 00000001
/dev/input/event2: 0000 0000 00000001
/dev/input/event0: 0000 0000 00000001
/dev/input/event3: 0000 0000 00000001
/dev/input/event2: 0000 0000 00000001
/dev/input/event0: 0000 0000 00000001
/dev/input/event3: 0000 0000 00000001
/dev/input/event2: 0000 0000 00000001
/dev/input/event0: 0000 0000 00000001

And dmesg shows the phone is altering between sleep and wake state. dmesg is attached in the post.

Also, the scroll distance after flinging is significantly shorter on the 06/07 build. I didn't update system during these period. Is this due to the touchscreen driver replacement?

Finally, color calibration will fail sometimes after the screen is turned on. I set R/G/B=100%/95%/85% in LiveDisplay, but when this problem happens, it appears as (about) 100%/100%/85%. Turning the screen off and back on will solve this problem.

Thanks in advance!
[ONE Original Android Development] erorcun:
Scroll distance is related with older touchscreen firmware I started to use, I'm aware of it. But it gives me far better battery consumption so I don't know what to do :/ maybe I will revert it after I really fix battery drain.

I'm also aware of broken color calibration but never researched it, it must be fixed too.

Investigating key presses will be my first job after I access PC o_O

Thanks for findings =)
[ONE Original Android Development] DerRomtester:
We should also try to look at that warning. Maybe it is harmless. Programmers just solve errors :)

WARNING: at fs/sysfs/dir.c:530*
[ONE Original Android Development] erorcun:
I already know how to solve it, it's caused by an unnecessary extra node in DT definition of mdss. but i will fix it in next build because of you highlighted it :p
[ONE Original Android Development] nikhil18:
Bro where is the clock-8974.c file I have finished porting the caf camera drivers
[ONE Original Android Development] erorcun:
It's divided into 4-5 files, clock-gcc-8974 clock-rpm-8974 etc.
[ONE Original Android Development] idprophecy:
Not at the time of first upload, but now it is included.
[ONE Original Android Development] pijas82:
This kernel works in RR?

Anyone use it?

Thanks

Great work
[ONE Original Android Development] pankspoo:
This kernel is same as lightening kernel

Lightning working

So this must be working on RR
[ONE Original Android Development] idprophecy:
Here is anykernel build also with ramdisk changes (it should change also on omni based roms).

DOWNLOAD LINK

If crashes, this will work.

Also here is part of anykernel script that does these changes. Who knows anykernel, please check it, if it changes properly. Thanks.

## 3.10 ramdisk fixes

# fstab

if [ -f fstab.bacon ]; then
fstab="fstab.bacon";
backup_file $fstab;
elif [ -f fstab.qcom ]; then
fstab="fstab.qcom";
backup_file $fstab;
fi;

if [ -n $fstab ]; then
replace_string $fstab "/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs nosuid" "/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs noatime,nosuid" "/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs nosuid";
replace_string $fstab "/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs nosuid" "/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs noatime,nosuid" "/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs nosuid";
fi;

# init.recovery.bacon.rc

if [ -f init.recovery.bacon.rc ]; then
qcomrecovery="init.recovery.bacon.rc";
backup_file $qcomrecovery;
fi;

if [ -n $qcomrecovery ]; then
replace_string $qcomrecovery "cpubw.47" "cpubw.40" "cpubw.47";
fi;

# init.qcom.power.rc

if [ -f init.qcom.power.rc ]; then
qcompower="init.qcom.power.rc";
backup_file $qcompower;
fi;

if [ -n $qcompower ]; then
replace_string $qcompower "cpubw.47" "cpubw.40" "cpubw.47";
fi;

# init.bacon.rc

if [ -f init.bacon.rc ]; then
qcomdevice="init.bacon.rc";
backup_file $qcomdevice;
elif [ -f init.oppo.common.rc ]; then
qcomdevice="init.oppo.common.rc";
backup_file $qcomdevice;
fi;

if [ -n $qcomdevice ]; then
replace_string $qcomdevice "# loc_launcher qcom_oncrps not needed" " group gps qcom_oncrpc inet" " # loc_launcher qcom_oncrps not needed\n group gps inet";
replace_string_multiline $qcomdevice "# fix netmgrd service" "service netmgrd \/system\/bin\/netmgrd\n class main\n user root\n group radio" "service netmgrd \/system\/bin\/netmgrd\n class main\n user root\n # fix netmgrd service\n group radio system";
replace_string_multiline $qcomdevice "# fix qmuxd service" "service qmuxd \/system\/bin\/qmuxd\n class main\n user radio" "service qmuxd \/system\/bin\/qmuxd\n class main\n # fix qmuxd service\n user root";
fi;

## 3.10 ramdisk fixes
[ONE Original Android Development] raja4sure:
Flashlight issue is fixed . confirmed.
[ONE Original Android Development] DerRomtester:
Actually not the same. Lightning is based on it. Also I don't like his patching style. Syncing with different kernel sources from another device. And adding many features without fixing the already existing bugs.
[ONE Original Android Development] Mecca EL:
Is this an update to your build from 6-10-2016? Thank you!!
[ONE Original Android Development] idprophecy:
10th build didn't have ramdisk changes I think. Here it is implemented to anykernel script, but it still needs a rework.
[ONE Original Android Development] Hingbong:
After flashing this kernel,a lot of apps get force close on cm nightly build
[ONE Original Android Development] idprophecy:
Try this one.
[ONE Original Android Development] Hingbong:
Thanks,it is fixed.
[ONE Original Android Development] lokesh.3440:
Has anybody tested with Paranoid Andorid 6.0 ??
[ONE Original Android Development] erorcun:
[MENTION=4812336]updateing[/MENTION]

Input events happen on CM too. Tried to find who sends it but whoever sends those events don't send them with natural way, so I couldn't see the source in a quick look.

What's the difference?
[ONE Original Android Development] idprophecy:
This one is compiled in stock google gcc 4.8. Previous build, that crashes, is in the self-compiled uber-tc 4.9.
[ONE Original Android Development] erorcun:
Oh ok, thanks.

[MENTION=4633983]nikhil18[/MENTION]

You were wondering why it crashes.
[ONE Original Android Development] nikhil18:
Oh OK so I will keep binder in sync with 3.10 haven't faced any problems yet
[ONE Original Android Development] imam.krismanto:
That kernel still brick built in SU on aicp ROM, can you fixed?
[ONE Original Android Development] idprophecy:
Hmm, strange. It works for me.
[ONE Original Android Development] imam.krismanto:
Oh sorry, working fine on latest nightly (06/11).. Thank.. !
[ONE Original Android Development] erorcun:
OTG and charger log flood fixed, there are also some improvements made to touchscreen driver.

I can't post zip due to my crappy internet, sorry.

To do list:

- Fix cpufreq (I think responsiveness that some people came across is caused by that)

- Import some commits from CM gpu/kgsl

- Fix and sync memcg and activate it

- Import high resolution scheduler and activate it

- Fix charger trying to start charge in suspend generates flood in log

- Sync some parts with LA.BF64 and cyanogen

- Fix compile errors with rom

- Look for is there any sound problem

- Fix wcnss warnings

- Decrease GPU voltage like franco and myfluxi did
[ONE Original Android Development] idprophecy:
Here is build with aforesaid changes. (download)
[ONE Original Android Development] DerRomtester:
Do you think sync with 3.10y is a good idea?
[ONE Original Android Development] erorcun:
I will sync with xperia's 3.10 LA.BF64 kernel.

Btw, logitech mouses don't work on 3.10 kernels it's a known issue, I will fix it on next build.
[ONE Original Android Development] erorcun:
I just faced with that unresponsiveness and I managed to get log, it's related with cpufreq/msm_thermal as I guess. Will fix it asap.
[ONE Original Android Development] DarKAngel1234:
Deleted Thread
[ONE Original Android Development] Arju:
Wrong thread?
[ONE Original Android Development] DarKAngel1234:
Deleted thread
[ONE Original Android Development] Arju:
Thought your question was directed to nikhil18 in this thread: http://xdaforums.com/oneplus-one/orig-development/cm13-lightning-kernel-3-10-94-v1-t3385696

This thread here is erorcuns thread.
[ONE Original Android Development] DarKAngel1234:
All good
[ONE Original Android Development] DerRomtester:
Just got a random reboot seems to be related to f2fs.

https://drive.google.com/file/d/0B4NfU3dQXHeiSjdXNjNudHJuV28/view?usp=drivesdk

I am gonna take a look at it tomorrow.
[ONE Original Android Development] tekanina:
No camera
[ONE Original Android Development] raja4sure:
I was having many random reboots in all previous builds... But in 12/06 build from Id prophecy it seems like random reboots are gone.

I was getting random reboots in 2-3 conditions.

1. When phone was heating.

2. During call.

3. When GPS was turned on(most of the times).

I am having data and cache as F2FS .
[ONE Original Android Development] DerRomtester:
We need logs to debug that. Just pick up the file /sys/fs/pstore/console-ramoops and copy it to your sdcard and rename it to console-ramoops.txt and upload it. Google Drive is quite simple. Open Google Drive app press the + and than choose the txt file and share the link. Without we can't do anything or guess what happened.
[ONE Original Android Development] gs-crash-24-7:
Indeed it seems to be related to line 355 in file fs/f2fs/inode.c containing : "f2fs_bug_on(sbi, get_dirty_pages(inode));" .

As far as i understand this is related to cleaning bad sectors in the memory and filesystem.
[ONE Original Android Development] raja4sure:
Here is the log file for a fresh reboot which happened during a call.
[ONE Original Android Development] erorcun:
Same thing happened to me once too. I will investigate, thanks.
[ONE Original Android Development] droppinbaums:
http://cloud.tapatalk.com/s/5761b6dd7abb7/console-ramoops.txt

Log file for random reboot while listen to music today. Happened twice.
[ONE Original Android Development] endstille:
how to compile

hey, sorry for the noob question, but might someone tell me how to compile this?

i compile stock cm13 for years and did also play around with linaro some time ago. But i've never compliled a separate kernel for cm.

do i ln the path into the source tree, or do i standard make menuconfig and compile it, or is there any build skript included, or....

Thanks for enlighten me :fingers-crossed: :o :highfive:

cheers marc
[ONE Original Android Development] erorcun:
Compiling is easy but packaging is hard to tell :/ you need to compile kernel(gcc 4.8) and devicetree(dtbtool), package ramdisk and put them in one file.

Compiling the kernel with rom gives errors, you should compile it seperately. Firstly type make bacon_defconfig then type make.

You can learn other parts from boeffla's build script, check bbuild.sh from boeffla's bacon kernel repo. It includes necessary binaries too(such as dtbtool). Good luck =)
[ONE Original Android Development] endstille:
awesome, thanks :)
[ONE Original Android Development] erorcun:
I have increased charge speed today. ("Times that speed is at max" is better term actually)

( [MENTION=4633983]nikhil18[/MENTION] )