yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] gs-crash-24-7:
I've tested both CAF test kernels on official omnirom nightly from 24-05-2016. Both kernels flash succesful but reboot to recovery once trying to boot.

Flashing the kernels kills wifi after restoring the old kernel, the same happends with the CM kernel on Omnirom.

Attached is the last_kmsg of test kernel 2.

I'll be happy to do some more testing if needed and i'll try to identify the network problems after reflashing my old kernel.
[ONE Original Android Development] kalapapa:
Omni does not play nicely with caf kernels which is why it caused issues for you
[ONE Original Android Development] iker_92:
this is the log for second zip on RR
[ONE Original Android Development] erorcun:
You need to test it in CAF camera.
[ONE Original Android Development] DerRomtester:
Guys CAF means on Sultans CAF marshmallow rom. Other derivates may work. There are so many roms out here and it is hard to support all combinations of camera drivers and libs and blobs.
[ONE Original Android Development] Renosh:
Omni uses color OS camera blobs and a different kernel from CM or CAF. It definitely won't boot. You're supposed to flash it on ROMs specified as CAF such as Sultanxda CM13 or CandySix.
[ONE Original Android Development] raja4sure:
Tried both kernel on Sultan's CAF CM13 build(10/06). Doesn't boot , instead boots to recovery.

Also there's one thing i noticed. The previous kernels were booting fine in exodus ROM but the last kernel compiled by id prophecy(which i think is based on your latest changes) doesn't boot on it.

Tried the same kernel for sultan's ROM and it it booting into recovery like those 2 CAF kernel zips.

Is there any modification due to which now the same kernel doesn't boot on CAF rom also(let alone the camera)?
[ONE Original Android Development] erorcun:
Hm then it isn't related with camera, probably it was always like that on sultan's rom. Thanks.

We need to test it on jgcaap's rom then :silly: I hope Miksel12 will see that post and try it.
[ONE Original Android Development] Mecca EL:
Yes.
[ONE Original Android Development] Miksel12:
Will try, first i have to nail an exam :)
[ONE Original Android Development] erorcun:
I've not done something specific, I don't know. I will investigate CAF related things in summer anyway.

It's normal then.

That was quick, thanks. =) I will post new zip, please ignore first ones.

Edit: Here it is: http://www.mediafire.com/download/x6kv3fypn8d80ay/bacon3.10caftest.zip
[ONE Original Android Development] nikhil18:
Can you upload the changes to github so that I can test it out on darkobas thanks caf 1 and caf 2 in two different branch thanks
[ONE Original Android Development] phoenixita:
Currently on latest jcaap! Do you need me to test the latest zips? Or do you have new ones that need testing? I'll be able to test in 15 min! [MENTION=4898631]erorcun[/MENTION]
[ONE Original Android Development] erorcun:
Hey thanks =) I put the latest build to 3 posts above.

[MENTION=4633983]nikhil18[/MENTION]

It's universal driver which supposed to work on both CM and CAF and still needs a lot of work. I'll release it and it's source code in summer with my custom kernel.

----

Btw, missing vibrator commits is up in the repo.
[ONE Original Android Development] phoenixita:
I'm currently taking a backup, flash in 5 mins! Should i test if it boots and camera right?
[ONE Original Android Development] erorcun:
It's confirmed it works on jgcaap's rom, I want to know whether camera works and is it fully functional.
[ONE Original Android Development] nthacks:
The CAF zips and even the normal zip just makes it boot to recovery on sultan's rom. However, it had booted up fine with a previous version of the cm kernel.
[ONE Original Android Development] phoenixita:
I'm going to flash it rioght now! Do you have hangouts? phoenixita94 @ gmail. com

EDIT: Google Camera not working! Neither COS Camera. do you need a last_ksmeg or logcat? :) [MENTION=4898631]erorcun[/MENTION]

p.s. sorry for the tag
[ONE Original Android Development] PatrickMac:
jgcaap's ROM is now using color os blobs as far as i know.
[ONE Original Android Development] erorcun:
:/ Thanks for trying it anyway. I would like to see kernel log.
[ONE Original Android Development] phoenixita:
/proc/last_ksmg?
[ONE Original Android Development] erorcun:
If any crash occured, yeah it's fine.
[ONE Original Android Development] NeGriTa79:
This kernel works on Temasek 9.2 CM13?
[ONE Original Android Development] phoenixita:
dmesg: https://www.androidfilehost.com/?fid=24591020540822270

last_kmsg: https://www.androidfilehost.com/?fid=24591000424941307 no random reboots so i think it's useless :)

logcat just to be sure :) : https://www.androidfilehost.com/?fid=24591000424941308

Let me know if it's okay :)
[ONE Original Android Development] Lanchon:
erorcun, amazing work!! sorry to spam :)
[ONE Original Android Development] nikhil18:
I almost got the camera to work but the viewfinder stuck but actutator said set position failed
[ONE Original Android Development] erorcun:
What do you want me to do with this log? Also I'm not porting caf camera, I'm making universal driver. I'm not interested in your port dude, please.

This log helped me a lot, thanks :)
[ONE Original Android Development] Miksel12:
I can confirm, no camera on jgcaap.
[ONE Original Android Development] erorcun:
Thanks.
[ONE Original Android Development] phoenixita:
Glad this was what you was looking for.

If you need some more testing, just tag me and i'll test your work, providing logs of course. ;)
[ONE Original Android Development] erorcun:
20-06 build: http://www.mediafire.com/download/g6xacl5c89w6852/bacon3.10(20-06).zip

Vibrator intensity added back and unresponsiveness fixed (I hope), all changes can be seen in github

[MENTION=3921603]phoenixita[/MENTION]

The latest build also has my next attempt for CAF camera, can you try it when you're available?
[ONE Original Android Development] phoenixita:
I'm available! I'm testing it in 5 mins ;) just downloaded
[ONE Original Android Development] Raagh:
To flash this on cos13.1 i need to wait for an anykernel version right?
[ONE Original Android Development] phoenixita:
The last build it's not booting. Stuck at splash screen and reboots itself in the splashscreen. Not able to take a /proc/last_kmsg via recovery, anything else i can pull for you? Looks like there are no last_kmsg created on my phone...
[ONE Original Android Development] idprophecy:
Here it is. Anykernel version. Same as erorcun's source. Compiled in GOOGLE GCC 4.8.

DOWNLOAD LINK
[ONE Original Android Development] Raagh:
Ty gonna try it and check what you asked me. Apparently latwst build is not booting. But lets check
[ONE Original Android Development] idprophecy:
I've tested it and it works. I should mention it due to previous reply about latest build. :p
[ONE Original Android Development] Raagh:
Flashed on cos13.1 gonna test it, for now no issues on mobile data or camera. Thanks :)
[ONE Original Android Development] Syaani:
What's the status of GPS on the latest kernel build? Any work going on with it? Thx
[ONE Original Android Development] erorcun:
It works for me, there was some problem at the beginning but it's fixed, do you have a problem about it?
[ONE Original Android Development] nthacks:
Only the anykernel versions seem to be booting up on sultan's cm13. The camera still didn't work on latest one. But damn the performance is so good I feel like giving up the camera just for it. Any chance you could include the kcal colour controls ( option for increasing the screen saturation in kernel adiutor is missing)
[ONE Original Android Development] Syaani:
That's great! And no, just asking.
[ONE Original Android Development] erorcun:
I will include in my custom kernel soon =)

Can you post kernel log from the sultan's rom after boot? I'm curious about something.
[ONE Original Android Development] nthacks:
Is this the log you asked?
[ONE Original Android Development] erorcun:
Yep, thanks.
[ONE Original Android Development] DerRomtester:
Latest build is smooth as ****. If i notice something i let you know. Yesterday i tried to implement bfq (like on cm kernel). But i need to investigate first whats wrong with it.
[ONE Original Android Development] lordsinasina:
[MENTION=4898631]erorcun[/MENTION], is there a possibility of fixing the camera issue with sultan's cm13 any time soon ?
[ONE Original Android Development] Hingbong:
I got twice roboot,how can I get the log?
[ONE Original Android Development] erorcun:
It'll be fixed in a month but I don't know when.

It's in sys/fs/pstore/console-ramoops. Needs root.
[ONE Original Android Development] kryshnakishore:
Can I use this kernal in resurrectionremix rom for oneplus one??
[ONE Original Android Development] plantator:
Wait for [MENTION=4633983]nikhil18[/MENTION] version, it is more featured, ofc based on this so u can try for now
[ONE Original Android Development] Hingbong:
https://mega.nz/#!5lx1DJYB
[ONE Original Android Development] erorcun:
File is locked.
[ONE Original Android Development] Hingbong:
https://mega.nz/#!81wUjKwB

!MFo7J28Tt9ixuLMQQIrPzfAnv62PBR4bMTY4kiXxYzg
[ONE Original Android Development] erorcun:
Your root is erroneous and this generates stress. Either your ROMs developer or you done something wrong. I recommend changing su and su_daemon with latest CM ones.

Except that I don't know the reason. If we don't count the stress caused by root then it may be related with scheduler, and if it is then it will be fixed in 1-2 months.
[ONE Original Android Development] Hingbong:
I am using cm official nightly with SuperSU 2.74 system mode
[ONE Original Android Development] erorcun:
CM already has controllable root, you shouldn't install supersu. Clearly it conflicts with something, your system is running under stress.
[ONE Original Android Development] hawktalon:
logs from the last 2 random reboots. On 18th June nightly and previous kernel build. Hope this helps.

https://drive.google.com/open?id=0B0BsNPVkczfHZmNrRUNHMzFhbEU

After a few reboots, battery life seems to be on par with 3.4 stock cm kernel. No new issues apart from the buttons lighting up at times.
[ONE Original Android Development] Mecca EL:
Been testing for almost 24hrs, and so far so good. No weird events, USB charging is fast, and touch response is normal. Will report anything after a second full day of use. Thanks [MENTION=4898631]erorcun[/MENTION]
[ONE Original Android Development] erorcun:
Still f*ing same reason...

To everyone: I will change kernel base to LA.BF64.1.2.2 soon which is approved to work on msm8974 (sony's custom kernel uses it) and more up-to-date, so all of those problems will be gone but I won't be able to provide updates for a week.
[ONE Original Android Development] DerRomtester:
Just a small log. Unresponsive Device while using camera.

http://pastebin.com/6NgPWCRV
[ONE Original Android Development] erorcun:
It seems it's related with memory management. I will check camera for any memory leak. Also I've applied too much commits to lowmemorykiller/binder to make them match with the ones in CM. If it's related with this it will be solved after I change base.
[ONE Original Android Development] imam.krismanto:
Your latest kernel break stock root of AICP..:crying:
[ONE Original Android Development] DerRomtester:
just use cm nightlys with built in root. This kernel is designed for cm nightlys and may not work fully on all roms around here.
[ONE Original Android Development] Gigadroid:
I can't get mobile data to work with latest anykernel build on Sultans CM13 and 4.0.1.c7-00011 modem.
[ONE Original Android Development] Spider-Vice:
Wait, where is this latest Anykernel build?
[ONE Original Android Development] NickosD:
#441

Next time use the search function
[ONE Original Android Development] hawktalon:
June 21st nightly working fine with june 20th kernel build. Nothing new except for cm bugs which is cellular signal randomly lose signal.

Edit: Spoke too soon...

https://drive.google.com/open?id=0B0BsNPVkczfHS0k0TlNBZzlFNkE
[ONE Original Android Development] Spider-Vice:
Yeah, I just thought that was an earlier build for some reason. Thanks.
[ONE Original Android Development] erorcun:
I've fixed reboot(really this time), it was caused by our old base. So it's still logical to change base. I won't upload build because of I will change base soon but if anyone want the fix it is in repo currently. Also I tried to fix weird button backlight behaviour.
[ONE Original Android Development] Mecca EL:
Can anyone compile this, for us techtards?
[ONE Original Android Development] idprophecy:
I'll compile it today, but I don't know when. I am not at home at the moment.

EDIT: [MENTION=4804871]DerRomtester[/MENTION] has already compiled it.
[ONE Original Android Development] Blackscorpion3:
Are we getting anywhere with usbOTG, or closer to it working?
[ONE Original Android Development] erorcun:
It's already fixed a while ago.
[ONE Original Android Development] DerRomtester:
Latest Kernel with [MENTION=4898631]erorcun[/MENTION] changes.

changes from my side:

* added bfq I/O scheduler

* changed from gzip to xz kernel compression (just to make the kernel smaller so the upload does not take so long)

:)

#HappyFlashing

Tested on CM13 nightlys (other roms may work but are not offically supported from my side)
[ONE Original Android Development] erorcun:
Thanks =)

--

It's anykernel version btw, COS users etc. can flash too.

Does contain reboot fix too.
[ONE Original Android Development] Mecca EL:
Thanks so much. I'll report my findings.
[ONE Original Android Development] Blackscorpion3:
Still not working for me. I'll get a log when I get home.
[ONE Original Android Development] erorcun:
Ntfs could be erroneous, fat fs may not be working, also it's known that logitech products are erroneous on 3.10 kernels (i'll fix that later)

Is it something apart from those?
[ONE Original Android Development] Blackscorpion3:
Her is a catlog I'm not getting usbOTG on latest 3.10 kernel from today or the previous one. Works fine on 3.4 kernel

https://drive.google.com/file/d/0Byf8o5PcFIf4R1NkamtiTUN4NlU/view?usp=drivesdk
[ONE Original Android Development] Blackscorpion3:
It's a PNY 32 gig flash drive. Just reformatted and again runs fine on 3.4 but isn't recognized on 3.10
[ONE Original Android Development] erorcun:
[MENTION=7444165]Blackscorpion3[/MENTION]

You got wrong log, can you take dmesg? Preferably within 10 minutes of boot, thanks.
[ONE Original Android Development] Blackscorpion3:
[MENTION=4898631]erorcun[/MENTION] sorry about that hope this works. Never did this before, pretty new to android.
[ONE Original Android Development] josedb:
Is this working on Sultan´s build? maybe his camera changes are a problem here
[ONE Original Android Development] geowolf1000:
Encryption is not supported?
[ONE Original Android Development] erorcun:
Not tested.

Everything should work except camera. I tried to fix mobile data also, will be happy if you report whether it works.

Log is fine, thanks. But as I though OTG works and this is device specific problem :/ hope I can solve it. I can ask you whether it works some times.
[ONE Original Android Development] Blackscorpion3:
[MENTION=4898631]erorcun[/MENTION] I can only get it to work on 3.4 never on 3.10. I keep 3.10 as it runs great. And is so much faster than 3.4, just not sure why usbOTG is not working for me. I believe after talking with [MENTION=6277543]Mecca EL[/MENTION] he doesn't have it working for him either.
[ONE Original Android Development] erorcun:
Ok, thanks. I will get in touch with you later.
[ONE Original Android Development] Blackscorpion3:
[MENTION=4898631]erorcun[/MENTION]

No problem. Hope it helps others who may have it sometimes. Just would love to see this kernel in full swing.

I will try some other flash drives. And try to reformat this one again tomorrow. Maybe, I can get it to work. I will keep you posted.
[ONE Original Android Development] Gigadroid:
Mobile data is still not fixed on Sultans, but I can see the LTE icon in the quick settings.
[ONE Original Android Development] Leicxan:
[MENTION=4898631]erorcun[/MENTION] i always get this message in dmesg. Is it normal ?

And my usb OTG is also not working.
[ONE Original Android Development] nikhil18:
Did you try es file explorer
[ONE Original Android Development] Leicxan:
Yes, i tried es file explore, but my usb storage appear and disappear soon.
[ONE Original Android Development] DerRomtester:
This warning is harmless and can be easily fixed. It is just something that is present in the ramdisk but not anymore on the 3.10 kernel.

Edit:

pushed another two builds with the changes [MENTION=4898631]erorcun[/MENTION] made today

* charger: Really fix usb plug in errors in suspend

* camera: Add CAF camera blobs support

* power: Various enhancements

* synaptics: Sync with vendor repo

Both kernels are untested so be aware. One for CM13 and the other one for Sultans CAF rom.
[ONE Original Android Development] Raagh:
Anyone noticed that double tap to wake sometimes dont work or its just me?
[ONE Original Android Development] erorcun:
It is result of optimization, will fix it on new base.
[ONE Original Android Development] Phoque_You:
Just flashed the CAF one on the latest Sultan rom. Everything seems to work, including camera.

Edit : No data :-/
[ONE Original Android Development] Gigadroid:
Can confirm, but focusing doesn't work.
[ONE Original Android Development] geowolf1000:
To cos 13. 1 pass encryption

Supersu & xposed systemless compitible

Stock kermel value

No reboots no heat

Data and wifi working as should

Great work

i keep testing and report if somethink does not proper
[ONE Original Android Development] Spider-Vice:
Testing on Validus' CAF ROM, so far almost everything works fine. Only major issue is camera doesn't focus, yeah, and can confirm no data.
[ONE Original Android Development] Mecca EL:
Thank you for compiling this. I've ran both 3.10-7 and 8 and i'm experiencing recharging problems - I had to turn the phone off to charge, SELinux was enforced so xposed stop working, and phone ran super hot. I ended up switching back to [MENTION=4898631]erorcun[/MENTION] last build around 2am. Here's a snap shot of my battery graph. The gaps aren't because of reboots, but from the charging problems. The large gap was when I turned my phone off to recharge. I didn't get a log, but I'll reinstall and pull one if you need it.

OnePlus One, CM13 6/26 nightly, xposed, no SuperSU
[ONE Original Android Development] geowolf1000:
Xposed work with enforcing

Always did

Is any special module that need permissive?
[ONE Original Android Development] DerRomtester:
erorcun said that the kernel must run in permissive selinux mode so you should stick with it.

No logs or it did not happen. I believe you but without log it is hard to say what really happend.

Xposed can also run crazy, so.
[ONE Original Android Development] Mecca EL:
Reinstalling. Will a logcat be enough?

Xposed never ran, so I know that was a factor at all
[ONE Original Android Development] Mecca EL:
Here's [MENTION=4898631]erorcun[/MENTION] last_kmsg log

And [MENTION=4804871]DerRomtester[/MENTION] dmesg log
[ONE Original Android Development] DerRomtester:
Nice catch. I dont know what happend or caused it. I have never seen this before. :)
[ONE Original Android Development] Mecca EL:
Cool, glad I caught something. I don't know anything about kernel development, so I couldn't offer an educated guess. I do know there are different tool chains, could that affect how this one is compiled?
[ONE Original Android Development] erorcun:
Hi guys,

I gave up switching to new base, because it will need too much work due to our old TZ firmware. I can do a lot of different thing in that time, so today I focused to what we have.

- Our defconfig was a mess actually, today I fixed it and added missing USB drivers, also I think mobile data on CAF roms should be fixed too (someone should test)

- also tried to fix OTG flash memories' and logitech devices' problems (should be tested too)

- fs/proc crash should be fixed [MENTION=4633983]nikhil18[/MENTION]

- qseecom updated

- also there is a CPU commit that can affect performance

http://www.mediafire.com/download/djctkcomlq90euj/bacon3.10(27-06).zip

Putting to OP now

And I wonder, what do you guys think about this build in matter of performance and responsiveness ?

---

Yes, it can differ. But you shouldn't have used SELinux enforced, that can cause *any* problem(even system doesn't boot on enforced), so I can't say anything.

Also the last_kmsg you posted shows the known reboot bug, I think it was solved in 20-07 build, are you sure you aren't using older build? it was fixed after 20-07, so it's normal.

I didn't quite get your charging problem actually, phone didn't start charging while it's open? :/
[ONE Original Android Development] nthacks:
[MENTION=4898631]erorcun[/MENTION] the zips you post never boot on sultan's cm13. They always reboot to recovery. Only anykernel version gets flashed successfully. So I couldn't test mobile data.
[ONE Original Android Development] Mecca EL:
While recharging, with my OPO on, my phone wouldn't recharge. If I turned my phone off, I can recharge. On the 6-20 kernel you built, recharging was fine, but other issues arose. On DerRomtester's build, the recharge problem was apparent.
[ONE Original Android Development] erorcun:
Yeah I know, I should have specified that, sorry. I have no experience about anykernel but I will learn and post one tomorrow if nobody will does.

I will research that tommorrow, I may get in touch with you.
[ONE Original Android Development] idprophecy:
Here is my Anykernel Version. (As usual, it is compiled in google gcc 4.8 and up to date with source).

ENJOY :)
[ONE Original Android Development] nthacks:
Okay so I tried the newest build and mobile data still doesn't work on sultan's rom.

Here's a dmesg from a few minutes after boot if it's of any use
[ONE Original Android Development] erorcun:
Log doesn't help too much in this situation but I found new things will try them tomorrow, thanks.
[ONE Original Android Development] Spider-Vice:
Tested on CAF ROM, mobile data still not working.
[ONE Original Android Development] Mecca EL:
Heres the latest log, frOm yesterday's Update [MENTION=4898631]erorcun[/MENTION]
[ONE Original Android Development] FSadino:
[MENTION=4898631]erorcun[/MENTION] Any ideas to make this kernel AOSP compatible?
[ONE Original Android Development] gyakusetsu1215:
Try the any kernel version that idprophecy uploads.
[ONE Original Android Development] FSadino:
I don't need to try any kernel, my question was simple :)
[ONE Original Android Development] gyakusetsu1215:
Perhaps you misunderstood. There is a version that is compiled by idprophecy on this thread that modifies your ramdisk instead of using the cm ramdisk that comes with OP's builds of this kernel.

The anykernel script modifies your ramdisk directly which gets rid of most compatibility issues.

Or maybe my sarcasm meter is broken?
[ONE Original Android Development] erorcun:
No, I don't plan. But if they boots, you can use anykernel versions posted on this topic. They keep the things makes AOSP the AOSP and just change kernel.

---

Btw, memory management is a lot better now, battery reporting fixed, touchscreen driver is also final so I won't touch it anymore, all wcnss warnings have fixed and I will change prima tomorrow. There may be some build tomorrow. I got bored actually, I will switch to my custom kernel soon so these will be last ones.
[ONE Original Android Development] FSadino:
Really sorry, I didn't know about any kernel. My intention is to figure out if is possible to run N preview on our OPO since it runs 3.10

Thanks for your help and apologize for my mistake
[ONE Original Android Development] Raagh:
Amazing news. Whats your goals on your custom kernel? What kind of kernel do you want to build?(tons of features, multiple hotplugs or simple with a few things)?
[ONE Original Android Development] erorcun:
No problem, and yeah, if someone will make N for our device he can use this kernel. Probably he will make his own ramdisk(so anykernel won't be needed) but anykernel may work too, who knows.
[ONE Original Android Development] FSadino:
I will try but without modifications on kernel since I'm not developer, I'm just curious :)