yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Matthew_333:
It should be N compatible, i tried it yesterday and it booted and everything worked except wifi and bluetooth. I didn't have time to pick kernel/common commits yet, but i see you did it now :P will cherry-pick now from you
[ONE Original Android Development] erorcun:
Actually there is a commit which created conflict so I gave up :P

https://github.com/updateing/androi...mmit/a8403bd0641dddf3489b231976854af50fbc28af

You can try to fix it if wi-fi won't work.

Waiting for your test, thanks.
[ONE Original Android Development] Matthew_333:
Will report back in few minutes :D

---------- Post added at 18:40 ---------- Previous post was at 18:32 ----------

@erorcun wifi and bluetooth still don't work with latest commits.

did you maybe take a look at sony's 3.10 n source? I think those sources were used with previews on z3: https://github.com/SonyAosp/kernel/commits/n

It seems that we have all the selinux commits applied but for others i didn't take a closer look

---------- Post added at 18:51 ---------- Previous post was at 18:40 ----------

@erorcun i think the commit you were trying to pick is for 3.4 only, that's why it makes trouble.

I found this one in shamu tree: https://github.com/android/kernel_msm/commit/c31e2a62ebd1e1e38dbf50303236119629933647

It applies perfectly well. I'll build and report back in few minutes

---------- Post added at 18:55 ---------- Previous post was at 18:51 ----------

Even this commit doesn't fix wifi. :(
[ONE Original Android Development] erorcun:
[MENTION=6578743]Matthew_333[/MENTION]

:/ Thanks. I will pick 7 more commits from Google repo, if it won't work again it will mean that we need to flash updateing's ramdisk along with kernel.
[ONE Original Android Development] Matthew_333:
Just an idea, maybe the prima is compiled as a module in cm kernel? When working with omni kernel i always had to make a module. Maybe his n build needs module as well. But i have no idea how would this make impact on bluetooth.

EDIT: if we are using anykernel his ramdisk stays the way it is, just with few modifications. I think ramdisk doesn't have to do anything with that, but i might be wrong. His ramdisk has really a lot of modifications :/

EDIT2: maybe qcom_diag removal in init.bacon.rc. It's connected to networking things as it seems. https://github.com/updateing/androi...mmit/0b44152768b72423b818f8a45c084b0c86db28aa
[ONE Original Android Development] erorcun:
No, prima isn't compiled in CM. But they can affect each other since both of them use same frequency.

Only thing I can relate with that is ramdisk. qcom_diag removal may be related too, I don't know. I will prepare 2 zips, one with anykernel and one with updateing's ramdisk, I hope you can test.
[ONE Original Android Development] Matthew_333:
Yeah, i have n just for testing purposes now, i can test anything today, tomorrow i'll go back to marshmallow.. 3.10 is way more important than nougat to me xD so i'm waiting for your zips :)
[ONE Original Android Development] erorcun:
Thanks =D will be available in 20 mins.
[ONE Original Android Development] erorcun:
[MENTION=6578743]Matthew_333[/MENTION]

I'm so sorry but it won't be available within 4-5 hours, it turned out CAF's and Google's "net: core: Support UID-based routing." commits are different and it's impossible to switch between them without reverting some other commits and I have to go out. :/ I hope you or someone else can test them later.
[ONE Original Android Development] BoboBrazil:
So does 8/28 build work well on cm 13? I'd like to try. Anything not working?
[ONE Original Android Development] erorcun:
Yep, but I compiled 29/8 build just now: http://www.mediafire.com/download/yjp7s3724hs12on/290816kernel310.zip

Everything works but if you have encrypted data I recommend you to backup them, just in case.

Only problem currently is reboots. I'll be happy if you come across with a reboot and provide log to me.

----

Latest build is N-ready. I don't count ramdisk, so wifi and bluetooth may not work but it's another thing.
[ONE Original Android Development] Gigadroid:
I can confirm that Bluetooth and Wifi don't work on Nougat yet.
[ONE Original Android Development] BoboBrazil:
Thanks, testing now.

---------- Post added at 01:27 AM ---------- Previous post was at 01:21 AM ----------

Just had a reboot using Chrome. How do I get logs?
[ONE Original Android Development] NickosD:
With an app like synapse of kernel adiutor mod.
[ONE Original Android Development] erorcun:
sys/fs/pstore/console-ramoops
[ONE Original Android Development] BoboBrazil:
Thanks, next time it crashes I will do a log. Been stable since the chrome reboot.
[ONE Original Android Development] Leicxan:
[MENTION=4898631]erorcun[/MENTION] Got one random reboot, log file was attched.

I'm on cos13.1.2 ZNH2KS3P0.
[ONE Original Android Development] erorcun:
[MENTION=4394458]Leicxan[/MENTION]

Thanks, that helped me.

----

(2) 29/08 build will be available in a min., memory management is mostly in sync with Google repos now, also includes some attempt to fix memory management reboots.

Also there is a minor version change, now it's 3.10.41 (it was 3.10.40)

Here it is: http://www.mediafire.com/download/vm2f6e6y89huw36/2.290816kernel310.zip
[ONE Original Android Development] Hingbong:
Is it compatible Nougat rom?
[ONE Original Android Development] erorcun:
Wifi and bluetooth doesn't work on it yet.
[ONE Original Android Development] DarKAngel1234:
A few questions erorcun. I have been watching this thread and following along for quite some time now since well before the problems you had with your computer. I have also test versions of your kernel base from Nikhil as well. Since it took you awhile to start implementing anykernel kernel releases, I will running ID builds on again off again, he has no settings fro hotplug under KA in his kernel. The latest build you just posted this morning 0829, is the first time just running your builds. The really question I ask is under Nikhil kernel, he was always trying to enable the Zen Decision Hotplug, so all four cores are always active, after I put in your kernel this morning, I was surprised to find MP Decision as the default and enabled hotplug. So are you to trying to enable four core's quad mode as well or not your intention.?
[ONE Original Android Development] erorcun:
I don't want to add any mod. to this kernel due to I want to keep it stock to the utmost.
[ONE Original Android Development] DerRomtester:
The main aim of this kernel is to get a working port of the 3.10 kernel running ( on cm nightlys) with all bugs fixed and not to add features without fixing the already existing bugs.
[ONE Original Android Development] BoboBrazil:
no reboots on this build yet:good:
[ONE Original Android Development] Leicxan:
Got another reboot on (2) 29/08's build..

log file posted. [MENTION=4898631]erorcun[/MENTION]
[ONE Original Android Development] erorcun:
You're using old build.

Edit: no, my mistake, sorry.

It's different crash than last one but unfortunately there is no complete crash log :/ we should wait until it happen again.
[ONE Original Android Development] Leicxan:
:highfive: Okay, i will continue test your kernel, let's see what's going on. Thanks for your hard work.
[ONE Original Android Development] Mecca EL:
On the past three builds, I've not experienced any reboots that were kernel related. Mine was a bad app that corrupted System UI.
[ONE Original Android Development] erorcun:
Yeah, there were soft reboots in your logs, I remember. It's good news then.

----

30/08 build is up: http://www.mediafire.com/download/nm5j1daj53wn79v/300816kernel310.zip

Minor version bump again (3.10.41 => 3.10.42)

Lowmemorykiller also in sync with CM now, I think that will solve latest reboot I experienced

I started to move gpios to pinctrl, which means moving to newer kernels will be easier :whistle:
[ONE Original Android Development] Miksel12:
Why not bump up the 3.10 kernel too the latest version?
[ONE Original Android Development] erorcun:
I examine all conflicts and it takes time.
[ONE Original Android Development] A$h!$h:
latest one support android nougat rom??
[ONE Original Android Development] erorcun:
Wifi and bluetooth don't work, but will work in next version.
[ONE Original Android Development] idprophecy:
Wow, I've been away for few days and now I logged on xda seeing you've made so much changes. Glad to test it tomorrow, good job! :P

Builds are up if somebody is interested.
[ONE Original Android Development] Mecca EL:
Phone feels like it's on steroids. Nice progress. Any forecast on OTG?
[ONE Original Android Development] erorcun:
Are you sure it doesn't work? I didn't try usb sticks yet but my keyboard and mouse do work.
[ONE Original Android Development] KenjiHannya:
With WiFi and bt in next build?

I will test in N

Tnx all :D

Lov u
[ONE Original Android Development] Mecca EL:
I'll test with another adapter, but the one I use regularly isn't being recognized at all. Is a log generated? I'll send you what I have.
[ONE Original Android Development] imam.krismanto:
[MENTION=4898631]erorcun[/MENTION] Working well on nougat, but DT2W not working??
[ONE Original Android Development] Mecca EL:
Spare jump drive registered, but files didn't appear.
[ONE Original Android Development] erorcun:
Yeah that's possible, probably will be configurable on next build.

Ok, going to look at it. What filesystem does jump drive use?
[ONE Original Android Development] ezet:
http://cloud.tapatalk.com/s/57c6c417c4b0b/log.txt

Crash with latest kernel.
[ONE Original Android Development] Mecca EL:
Jumpdrive is FAT32 - this one is the screen shot I posted

OTG slave with SD card is exFAT - this one doesn't register at all
[ONE Original Android Development] BoboBrazil:
No crashes on latest version ? Battery life doesn't seem to be as good as stock cm kernel though.
[ONE Original Android Development] Dward40:
Battery life like on stock
[ONE Original Android Development] Hingbong:
Can't use BT , wifi and DT2W with nougat, I hope you can fix it.
[ONE Original Android Development] Blackscorpion3:
Reboot stock CM13, not sure if it's kernel related or not, logs attached.

https://drive.google.com/file/d/0Byf8o5PcFIf4QjlSdzFjc0ttOTg/view?usp=drivesdk
[ONE Original Android Development] erorcun:
You should have get sys/fs/pstore/console-ramoops, this log is useless currently.
[ONE Original Android Development] Blackscorpion3:
Here's another not sure which you needed.

https://drive.google.com/file/d/0Byf8o5PcFIf4YUNCV3AwVVhWSEU/view?usp=drivesdk
[ONE Original Android Development] erorcun:
That's full of question mark :P It's not your fault ofcourse

Reason of USB sticks don't work was power wasn't being supplied to devices :/ This is why mouse/keyboard with battery do work. It should be fixed in next build.

Also next build should have lower power consumption.

I'm %100 sure only reason of wifi/bt/DT2W don't work in N is ramdisk(enforced selinux may be reason too, I don't know does it work in enforced). I will put updateing's ramdisk and make sure it runs in permissive for seperate N build.
[ONE Original Android Development] kalapapa:
N wasn't booting at all in enforcing

They kept it on permissive
[ONE Original Android Development] evronetwork:
Similar but not the same(just a bit worse, compared to COS13.1.1)

What do you mean stock CM13, you mean stock COS13? ..tested on COS13.1.1 and works as expected
[ONE Original Android Development] GXGOW:
I was very curious to see how well this would run, so I flashed it on my device running Sultanxda's CM13. So far, no issues apart from the camera and flashlight not working at all (even the tile disappeared from the QS menu). Of course, you probably can't do much with words, so I've taken a logcat, which you can find here.

Apart from that, you've really done an amazing job with this kernel. I'm very amazed that this is the only issue left in your kernel. Good job man! :D
[ONE Original Android Development] gyakusetsu1215:
You have to flash a caf based kernel on sultan's ROM. This has cm camera blobs. Sultan's has his own camera blobs. That's why you have camera issues.
[ONE Original Android Development] GXGOW:
Oh, so that's why. Thanks for the clarification.
[ONE Original Android Development] hyper_davide:
I install the kernel in RR rom it's perfect but when I load the phone off the screen turns off.

please resolve the problem. thanks
[ONE Original Android Development] gyakusetsu1215:
I'm going to say this relatively nicely since someone else might be less kind. I see you're new here. It's not taken well by developers when you come into a thread and have a demanding tone. Devs provide their work for free here and don't owe anybody anything. Remember that when you post. We're lucky to have great devs still supporting this device. Posts like yours have run off devs. Try to have a less demanding tone in the future.
[ONE Original Android Development] hyper_davide:
mine was not a command , I'm glad that there are developers who keep alive this device for free, it was just a question which required if it solved in the next update , but in a kind.

forgiveness for my english but it's not my native language
[ONE Original Android Development] gyakusetsu1215:
I forgot to add to my comment that I was hoping it was just a communication issue due to using a second language. I just wanted to let you know that some people may be quite rude about something that seems like a command, even if that not the intention the comment. I didn't want someone else to flame you for your wording. Have a good day/night friend.
[ONE Original Android Development] Ilfuma:
wich app can I use to modify the parameters of the kernel?

wich app can I use to modify the parameters of the kernel? with the kernel I was using before I used synapse, wich app suits your kernel?
[ONE Original Android Development] idprophecy:
Kernel Adiutor for example.
[ONE Original Android Development] erorcun:
Guys, the project is discontinued.

I think it's hard to get it to stable, and I have no time.

Except reboots there is no problem left. As for OTG, I found some necessary config which is disabled on us, it is CONFIG_USB_MSM_ACA. Probably activating it will solve the problem.

Also I should say most of current reboots are caused by my failed attempt to update GPU drivers.

Thanks to everyone who've tested and contributed =)
[ONE Original Android Development] KenjiHannya:
Tnx dude!
[ONE Original Android Development] Setting.Out:
Thanks for all the hard work.. :)
[ONE Original Android Development] erorcun:
Currently my repo uses 3.11 version of f2fs but CM follows stable one (which means f2fs of kernel 4.6)

I don't know do you know here, I learned it just yesterday, this place backports all stable f2fs commits to 3.10, just sync with here and done:

http://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs-stable.git/log/fs/f2fs?h=linux-3.10.y
[ONE Original Android Development] DerRomtester:
Thank you my friend. When i got it fixed i am gonna send you a pull request.
[ONE Original Android Development] erorcun:
Hahaha I think I solved sound problems guys, but I can't try right now.

Can someone try changing 'Slimbus 2 Playback' to 'SLIMBUS_2 Hostless Playback' and 'Slimbus 2 Capture' to 'SLIMBUS_2 Hostless Capture' in sound/soc/msm/qdsp6v2/msm-dai-q6-v2.c ?

And I recommend applying yesterday's sound patches ofcourse.
[ONE Original Android Development] nikhil18:
ok bro doing it right now and one more thing how do i remove cm camera drivers from camera v2 so that i can use this kernel with oxygen os cam blobs thanks
[ONE Original Android Development] erorcun:
Port it but don't touch camera_v2/isp folder, if there are necessary changes in isp folder of oxygen, do them by hand.

And there are changes in v4l2 framework but compiler will tell you what to do.
[ONE Original Android Development] nikhil18:
.playback = {
.stream_name = "SLIMBUS_2 Hostless Playback",
.aif_name = "SLIMBUS_2_RX",
.capture = {
.stream_name = "SLIMBUS_2 Hostless Capture",
.aif_name = "SLIMBUS_2_TX",

[ 4.720383] slimbus:1 laddr:0xcb, EAPC:0x1:0xa0<6>[ 4.720496] taiko-slim taiko-slim-pgd: wcd9xxx_slim_device_up: slim device up

[ 4.727144] pil-q6v5-mss fc880000.qcom,mss: mba: Brought out of reset

[ 4.720874] slimbus:1 laddr:0xca, EAPC:0x0:0xa0

[ 4.728669] taiko-slim taiko-slim-pgd: wcd9xxx_check_codec_type: detected taiko_codec, major 0x102, minor 0x1, ver 0x2

[ 4.728678] wcd9xxx_core_res_init: num_irqs = 31, num_irq_regs = 4

[ 4.736955] pil-q6v5-mss fc880000.qcom,mss: modem: loading from 0x08000000 to 0x0ce00000

[ 4.736977] M-Notify: General: 6

[ 4.740310] platform qcom,mdss_fb_wfd.173: Driver mdss_fb requests probe deferral

[ 4.740681] of_get_named_gpio_flags exited with status 276

[ 4.740693] msm8974-asoc-taiko fe02c000.sound: msm8974_asoc_machine_probe(): No hdmi audio support

[ 4.741270] msm8974-asoc-taiko fe02c000.sound: ASoC: CPU DAI msm-dai-q6-dev.16388 not registered

[ 4.741300] platform fe02c000.sound: Driver msm8974-asoc-taiko requests probe deferral

added those lines but now its says internal error microphone may be in use when i record some thing from sound recorder
[ONE Original Android Development] erorcun:
Ok than, I will look later, thanks.
[ONE Original Android Development] nikhil18:
one more thing no music is being played
[ONE Original Android Development] erorcun:
After doing it?
[ONE Original Android Development] nikhil18:
Ya
[ONE Original Android Development] DerRomtester:
I got an idea about your sound issues. I am gonna try it when i am back from work.
[ONE Original Android Development] erorcun:
Sound issues are caused by name mismatching of DAI's between msm-dai-q6-v2.c and msm8974.c file btw, I'm %90 sure. But I don't have time to look at it, will be happy if you fix it.

3.4 wasn't taking names into the account but 3.10 has changed it.
[ONE Original Android Development] abhibnl:
Man this is so exciting!! Great work [MENTION=4898631]erorcun[/MENTION]

Looking forward towards the first fully working build of this kernel. Take all the time you need :) Let me know if you would want me to try n flash any kernel build but i'm on 5.1.1 SlimSaber based off Sultan's sources n kernel.
[ONE Original Android Development] DerRomtester:
Sent you a pull request:

fixed f2fs --> check ok --> it is booting now on f2fs filesystems
[ONE Original Android Development] erorcun:
I will get in touch with you if I consider something for 5.1.1, thanks =)

Thanks! picking asap.
[ONE Original Android Development] erorcun:
Thanks to DerRomtester F2FS is working now, but 'noatime' should be removed from fstab.

And I won't update test zip, sorry if someone was willing to test it.
[ONE Original Android Development] Spider-Vice:
Hopefully once the sound issues are fixed someone uploads their own zip. Great progress being made here.
[ONE Original Android Development] Miksel12:
Nice! Very eager to test
[ONE Original Android Development] fmc000:
Once the sound / mic issues are fixed I will test this with SlimSaber.
[ONE Original Android Development] erorcun:
https://github.com/erorcun/android_...mmit/be1dfc13534908246d1c4b95f33ddfd224ad8b21

Can someone try reverting this commit? For sound issue.
[ONE Original Android Development] idprophecy:
Thanks.
[ONE Original Android Development] Mecca EL:
Thanks for your work. I'm still using this as my daily driver, the 9/03 version that [MENTION=4511190]idprophecy[/MENTION] cooked up. Outside of not having otg, it's been running great.
[ONE Original Android Development] -Fedde-:
Thanks for your work!

And thanks for telling us your project is no longer continued.
[ONE Original Android Development] Mecca EL:
I know the project is stalled, but I've been using [MENTION=4511190]idprophecy[/MENTION] 10-09-16 version, and it's been running great. Instead of enhancements, can anyone add features like different governors, etc., updating the DirtyCOW fix, and maybe fix OTG? I've used a bunch of different kernels on my OPO, but this runs the best.
[ONE Original Android Development] :
eagerly waiting for 7.1 support

hehhehehheheheheheh

out
[ONE Original Android Development] DerRomtester:
I think this wont happen until we get that kernel fully stable and working.

Why would you add features without fixing the already existing bugs?
[ONE Original Android Development] Mecca EL:
I've been using the last build for almost a month, and it's been stable. Maybe I'm missing something, but this is the best kernel for my needs. The only bug I'm aware of is OTG. What else is broken?
[ONE Original Android Development] erorcun:
My device reboots itself regularly, that was why I have cancelled the project. Now I started to think it was my compiler and some commits that idprophecy has reverted :/ I will try idprophecy's kernel for some time and if it won't reboots my device I will continue to the development.
[ONE Original Android Development] arjun:
damn... please do.
[ONE Original Android Development] Mecca EL:
I don't know what he's done, or if CM fixed some hidden problems, but [MENTION=4511190]idprophecy[/MENTION] 3.10 uberized linaro 6x build, based on what you've done so far, is working damn great for me. I have the governor set to Conservative, mpdecisions enabled, msm thermal enabled, core control enabled, GPU governor on simple ondemand, I/O scheduler on noop, TCP at westwood

The only reboot I've experienced were from a beta xposed module, or a beta theme that I'm testing - which I spot in a logcat easily.

But no kernel is as fast responding as this one. I've been through them all on my OPO. Lord Boeffla's is stable and sure, but your 3.10 build is ultra fast and responsive. Honestly, if you can get OTG functional, you wouldn't have to do anything else. That's the only thing missing.
[ONE Original Android Development] erorcun:
Ok, I will fix OTG, GPU drivers and release it after a week with different toolchain if it won't cause any reboot. Thanks a lot.
[ONE Original Android Development] Mecca EL:
Glad you're back in the game!!! :highfive:
[ONE Original Android Development] idprophecy:
Good luck! :good: ;)
[ONE Original Android Development] erorcun:
Today I got 6th reboot. And they're either paging request fails at spinlocks or random undefined instruction errors, which are things that I can't fix. They were there in CM, now I'm using COS and they're still there. I will release the build that has OTG some time, but I won't continue to develop this kernel and I don't recommend using it.
[ONE Original Android Development] Mecca EL:
I can send you a copy of my device log, if there's anything in there that might help you see how well my device is running? It probably won't help, but I appreciate all you've done for the community. Thank you.
[ONE Original Android Development] MexiDroid:
thanks!, one question, with this i will have 2 secs or 64 secs of slow shutter speed? :)
[ONE Original Android Development] nikhil18:
You will also have 128 secs and 1hr of slow shutter speed
[ONE Original Android Development] MexiDroid:
I dont get the joke?

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] nikhil18:
Camera shutter speeds are not dependant on kernel but on the cam blobs in the rom
[ONE Original Android Development] MexiDroid:
Man, with sultan only have 2secs of shutter speed because qualcomm based (i donde remember the name)

With normal kernel u have up to 65secs

Slow shutter is not slow motion

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] DerRomtester:
Like nikhil said. It has nothing to do with the kernel.
[ONE Original Android Development] MexiDroid:
So weird

With caf kernelx u only have up to 2secs of slow shutter in opo (sultan said he cannot make 65secs of slow shutte i dont remember why)

With cm kernel u have up to 64 secs os slow shutter in opo

I will try it but my question was

How many secs i have of slow shutter?

But with sultan u have 60fps non slow mo but only 2secs of slow shutter

With other roms u dont have 60fps non slow mo

But u have up to 64secs of slow shutter

Enviado desde mi A0001 mediante Tapatalk
[ONE Original Android Development] gerciolisz:
As others said it depends on Hals and blobs used in ROM not the kernel itself. Try other roms but read what features they have.