yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] erorcun:
Oh ok you meant camera, I already know it. Hopefully it will be done soon too.

Edit: Today I tried my mouse and it didn't work. OTG is still problematic. goddamn
[ONE Original Android Development] Mecca EL:
I'll test out my PS4 Pro controller, and see if OTG is functioning with that. As far as storage, it's working fine.
[ONE Original Android Development] SirSoviet:
It's insane how much smoother Android gets with this kernel! With this kernel I think this phone will easily last another year or two. Thank you so much for your work, dev.
[ONE Original Android Development] fmc000:
Does this kernel still jump between the maximum frequency and deep sleep, as for example in the second pic o post #869 ?
[ONE Original Android Development] codgician:
Just tried f2fs encryption, but no luck. Although the encryption process seems successful and startup PIN validation seems to be working, but after entering the PIN I got stuck at the android logo. I've waited around an hour. But I can confirm that ext4 encryption do work.

I guess the issue might not lay in your kernel but the system. I'll try Marshmallow sometime.

Thanks for your great work! :good:
[ONE Original Android Development] Mecca EL:
Possible. I have my kernel set to Conservative, which stopped the ramping at the time. Since [MENTION=4898631]erorcun[/MENTION] has also updated the kernel version, that may have alleviated the problem.
[ONE Original Android Development] tmotard:
Yes, that's the case.
[ONE Original Android Development] fmc000:
That's most unfortunate, hope this bug can be fixed.
[ONE Original Android Development] Blackscorpion3:
[MENTION=4898631]erorcun[/MENTION] if you need any logs from me to try to narrow down the usbOTG issue on AOSP let me know and also which logs you will need.
[ONE Original Android Development] therishabh:
will this kernel work on last cm snapshot?
[ONE Original Android Development] erorcun:
I will look to that frequency jumping guys.

It works on all CM/LinOS versions.

I will like to see it. I need kmsg/dmsg.
[ONE Original Android Development] Blackscorpion3:
Here are the logs
[ONE Original Android Development] Gawd:
Here mate.

I'm on official AICP and it doesn't recognize the external HDD at all. However Mixplorer does prompt a message but doesn't do anything beyond that. I'm attaching some screenshots and the logs. I also don't know why Syslog greyed out last kernel log.

[MENTION=4898631]erorcun[/MENTION] I'm so glad that you're working on this. Thank-you so much for investing your time, and making this device even better.
[ONE Original Android Development] erorcun:
[MENTION=6363737]Gawd[/MENTION]

l'm grateful that there are people like you guys in here, my pleasure.

Btw, I've looked to logs of both of you and fixed really a lot of things: https://www.mediafire.com/?fgfiy57r45y1v7j

Ofc I couldn't test it but I think it's done now. But if not, please give it a try with permissive selinux.
[ONE Original Android Development] :
I'm really excited to see possible encryption with f2fs in this kernel. Long has our phone been plagued with the disabled 3.4 encryption for no apparent reason. Will be watching this thread closely :)
[ONE Original Android Development] Ninnix96:
Its compatible with data and cache f2fs?
[ONE Original Android Development] Blackscorpion3:
Still no usbOTG on AOKP
[ONE Original Android Development] Syaani:
Wait you are using SELinux as enforcing. And it is working well?
[ONE Original Android Development] Mecca EL:
Yes. I've not ever changed SELinux rules.
[ONE Original Android Development] Ninnix96:
I stay on this kernel but miss many governor, smartmax? Nightmare?
[ONE Original Android Development] Gawd:
It's in experimental stage! Once it's all done and tested, this would be the finest of them all. Just wait. :)
[ONE Original Android Development] erorcun:
I tried a lot of things about OTG but it just doesn't like some devices. One of my mouses works(usb 1.1) but other one(usb 1.0) doesn't. I must research more.

I think I can try fixing CAF camera focus instead of OTG for a while.

Can anyone try this on CAF cam blobs please: https://www.mediafire.com/?4g1b9f45j625eai

A reminder; anyone can compile this with enabling CONFIG_CAF_CAMERA_DRIVER. Also today I added new toggle: CONFIG_UPSIDE_DOWN_CAMERA for find7/coloros blobs.

Also source got updated but I won't put new non-CAF build since OTG is still erroneous.

Yeah, I've switched to enforced after I've started to use AnyKernel. It has been long time.
[ONE Original Android Development] mustang_ssc:
Tested on latest NitrogenOS build (https://xdaforums.com/oneplus-one/development/nitrogen-os-7-1-0-nde63p-t3491386) which has Sultan's camera HAL and the camera is working. I've tested it a bit and it saves pictures and videos from both cameras (primary and secondary), but focus doesn't work.

So, i found the following issues:

-wifi doesn't turn on

-if i enable Bluetooth, the device automatically reboots

-camera focus doesn't work

-according to the ROM all the cpu cores keep awake all the time, even if there are no relevant activity. Not really sure about this one.

-got a reboot while using root explorer and trying to open a file in /proc.

I wanted to post a last_kmsg file but not sure why it isn't in /proc, maybe I'm doing something wrong. In that case tell me and I'll try to send it.

Logcat: https://drive.google.com/file/d/0B25zhqsy3xaYWWlacUF2aklJalk/view?usp=drivesdk
[ONE Original Android Development] erorcun:
it's at /sys/fs/pstore/console-ramoops in 3.10 kernels.

Thank you. But I need kmsg or dmsg to solve focus problem, hope you can send.

Wifi,bt etc. has been always problematic in updateing's N base. I don't have any plan to solve it in short term because it will require a lot of work, maybe later.
[ONE Original Android Development] Mecca EL:
I'll install and get those for you.
[ONE Original Android Development] mustang_ssc:
Ok, got it.

Here it is after the focus issue: https://drive.google.com/file/d/0B25zhqsy3xaYOTZiTW1kVzR2Tms/view?usp=drivesdk

Also I've got it with syslog app (dmesg), they should be the same file but there is a little size difference so better send two than one :p https://drive.google.com/file/d/0B25zhqsy3xaYSVpzZUNCTV93c1k/view?usp=drivesdk
[ONE Original Android Development] erorcun:
Thanks. Unfortunately there is no clue of problem on logs :/ But I'm still going over it.

Btw, to give one more chance to f2fs encryption, I updated f2fs to 4.10-rc1 version of kernel.

Ofcourse I took it from stable backports branch as always but since it's a filesystem I can't guarantee that there won't be any data loss. So I recommend taking backup if there is any f2fs partitions.

https://www.mediafire.com/?u0g3v6jg92ixi63
[ONE Original Android Development] siropchik:
this kernel not work on Sultan Rom?
[ONE Original Android Development] iRhyiku:
Can't you read the last few posts?
[ONE Original Android Development] Gawd:
Keep the ball rolling, mate!

This project should not die.
[ONE Original Android Development] erorcun:
Hi again,

I made one more build, everything works but I don't know about touchscreen because of mine's broken. Here it is: http://www.mediafire.com/file/ds9curoz3myfz6j/310117kernel310.zip

Hope someone can try it.

It includes KCAL, camera bugfixes, OTG bugfixes(OTG isn't done yet, still problematic), a bit faster boot due to improvements in touchscreen driver, latest f2fs version as I've mentioned in my previous post, also has f2fs encryption enabled - but I don't know does it work, latests commits from CM and some other things.

Also I started to work on X support :silly: It doesn't boot yet but I'm hopeful.
[ONE Original Android Development] nikhil18:
Sync threshold is very aggressive and it keeps the CPU at high frequencies a lot
[ONE Original Android Development] erorcun:
I just looked to sync threshold code and it's okay. Also first place that sets it is init.qcom.power.rc, it's being initialized from there which means it's default CM value.
[ONE Original Android Development] Mecca EL:
Touchscreen was only responding to dt2w. Nothing else beyond that.
[ONE Original Android Development] nikhil18:
But then for some reason the high frequencies are being used a lot it may be the governor,mpdecision or sync threshold and none of the new devices use sync threshold
[ONE Original Android Development] Mecca EL:
Yeah, definitely something wrong with touchscreen. When I reboot, I can access my phone fine. Once the screen times out, I can't resume. [MENTION=4511190]idprophecy[/MENTION], can you look into this for [MENTION=4898631]erorcun[/MENTION] please. I was impressed with the responsiveness of this update.
[ONE Original Android Development] erorcun:
Did you try after turning off all screen off gestures? Also can you send dmsg?
[ONE Original Android Development] Gawd:
Yes, I did. Touchscreen won't work after I leave my phone screen off for a minute.

https://drive.google.com/file/d/0Bzedbk3OVKq1WEpMaDRNSHVyNlE/view?usp=drivesdk
[ONE Original Android Development] idprophecy:
Same happens to me. After reverting of all commits to bring support for X (I was lazy due to lack of time to test one commit by one), it works fine. I think that it is one of these commits (first commit, second commit) especially due to changes for synaptics. But I may be wrong since I have not good knowledges to these things.
[ONE Original Android Development] erorcun:
Ok, does this build work? https://www.mediafire.com/?ds9curoz3myfz6j
[ONE Original Android Development] idprophecy:
Yes, it does.
[ONE Original Android Development] erorcun:
Ok, thank you. I had to disable some trick I've seen first time in X's touchscreen driver. It should have shortened the boot time, but whatever.

I put latest build to OP.
[ONE Original Android Development] idprophecy:
Great!

Edit:

By the way, If somebody wants, my build is ready in mega folder.
[ONE Original Android Development] Mecca EL:
Thought I had it attached before I commented. Sorry about that.
[ONE Original Android Development] erorcun:
Which governors/schedulers do you guys want? I think it's time to include them. (I will add BFQ for sure.)
[ONE Original Android Development] Mecca EL:
Governors: zzmoove, intelliactive, intellidemand, wheatley, smartmax, slim, intellimm, pegasusq, nightmare, lionheart

Schedulers: fiops, bfq, sio, tripndroid, zen

And if you're feeling nice: Swipe2Wake gesture
[ONE Original Android Development] mustang_ssc:
Besides that ones smartmax_eps, yankactive and interactive_pro governors would be interesting.

The problem of adding some governors is the instability and reboots that some of them could cause, but i think it would be worth anyway, at least some test builds to see how it behaves.
[ONE Original Android Development] Mecca EL:
[MENTION=4898631]erorcun[/MENTION], having trouble with kernel settings. I can't select any other governor. And I'm losing WiFi functionality with some apps. Also, I couldn't restart normally. My phone froze at restart.
[ONE Original Android Development] erorcun:
How do you change cpu frequencies, via an app or by hand? If you're doing it by hand can you try adding 3 more zero to end? It's like that on kernel.
[ONE Original Android Development] Mecca EL:
I use kernel adiutor.
[ONE Original Android Development] erorcun:
Maybe it's some app bug? :/ I haven't made any change to cpu or cpufreq related things after 01/11 build, but I'll check tomorrow.
[ONE Original Android Development] Mecca EL:
I was wondering the same. I'll get with the dev.
[ONE Original Android Development] fmc000:
Before adding new governor it would be better fixing the frequency scaling on the standard ones IMHO.
[ONE Original Android Development] bobbydigital222:
can this solve a low in call volume issue in lineage os nightly?
[ONE Original Android Development] Gawd:
nien.
[ONE Original Android Development] bobbydigital222:
I have tried editing build prop, flashing audio mods nothing works I thought maybe a different kernel might help
[ONE Original Android Development] Jole7:
Great work man thank you and for the guys who help you amazing skills bud.
[ONE Original Android Development] DerRomtester:
I can try in the evening. In about 7 hours.
[ONE Original Android Development] nikhil18:
nope no sound and i have an idea xpera z3 has 3.10 kernel maybe we can cross reference https://github.com/sonyxperiadev/kernel
[ONE Original Android Development] DerRomtester:
Empty
[ONE Original Android Development] erorcun:
I know, no, it won't work.

Thanks for trying it, I will try something else.
[ONE Original Android Development] nikhil18:
here is the full log

[ 5.150039] msm-pcm-routing msm-pcm-routing: ASoC: no dapm match for VOICE2_STUB_DL --> Voice2 Stub --> INTERNAL_BT_SCO_RX_Voice Mixer

[ 5.150051] msm-pcm-routing msm-pcm-routing: ASoC: Failed to add route VOICE2_STUB_DL -> Voice2 Stub -> INTERNAL_BT_SCO_RX_Voice Mixer

[ 5.178405] msm-pcm-routing msm-pcm-routing: ASoC: mux SLIM_0_RX AANC MUX has no paths

[ 5.226900] msm-dai-q6-dev msm-dai-q6-dev.16388: ASoC: no source widget found for SLIMBUS_2_RX

[ 5.226912] msm-dai-q6-dev msm-dai-q6-dev.16388: ASoC: Failed to add route SLIMBUS_2_RX -> direct -> Slimbus2 Playback

[ 5.226942] msm-dai-q6-dev msm-dai-q6-dev.16389: ASoC: no sink widget found for SLIMBUS_2_TX

[ 5.226948] msm-dai-q6-dev msm-dai-q6-dev.16389: ASoC: Failed to add route Slimbus2 Capture -> direct -> SLIMBUS_2_TX
[ONE Original Android Development] nikhil18:
same log on xperia z5 https://talk.sonymobile.com/t5/Kernel/Phone-reboots-as-soon-as-call-ends/td-p/1022774

so these lines are not related to mic

[ 13.872238] msm-pcm-routing msm-pcm-routing: ASoC: no dapm match for VOICE2_STUB_DL --> Voice2 Stub --> INTERNAL_BT_SCO_RX_Voice Mixer

[ 13.872243] msm-pcm-routing msm-pcm-routing: ASoC: Failed to add route VOICE2_STUB_DL -> Voice2 Stub -> INTERNAL_BT_SCO_RX_Voice Mixer

[ 13.894358] msm-pcm-routing msm-pcm-routing: ASoC: mux SLIM_0_RX AANC MUX has no paths
[ONE Original Android Development] erorcun:
I've noticed it too.

I pushed some commits to repo, but they don't fix anything so there is no need to pull yet. I'll head to wcd9320 soon, I'm done with qdsp6v2 I think.

Edit: No, problem is probably with mixer_paths.xml. I will look soon.

Edit: nope, I was wrong again

Today I will push a bunch of patch, lets see what's gonna happen, I'm hopeful this time
[ONE Original Android Development] erorcun:
I pushed some commits today but none of them worked, but they've provided stability at least.

[MENTION=4800121]Sultanxda[/MENTION] , do you know what can cause mic to not working after call received? Something in call process brokes it :/ Is there any gpio or clk that I can control?

This is only thing in log related with this:

qdsp_cvp_callback: cmd = 0x112c2 returned error = 0x9
[ONE Original Android Development] mekanismen:
Can it possibly have anything to do with fluence (active noise reduction)? I know that this has been an issue with the OPO and other devices before.
[ONE Original Android Development] erorcun:
Ok, I will try someday.

I've finished pulling all CM commits except unrelated ones, none of them worked.

I will play with msm8974.c file soon. (And that fluence thing)

Edit: It's still same without fluence.
[ONE Original Android Development] erorcun:
Problem may be mic goes to suspend but doesn't come back, I've added suspend ignore codes from other chips and the result is same but this is only thing I can think.
[ONE Original Android Development] Miksel12:
Did Sultans 3.10 kernel have sound?
[ONE Original Android Development] erorcun:
All sound problems are fixed.

It became even better than before if you ask me :p

All feedbacks are welcomed.

--------

I think it never had sound.
[ONE Original Android Development] stryker09:
Is the same f2fs branch as cm baked in? Not sure if differing branch versions will be compatible :confused:
[ONE Original Android Development] erorcun:
Ours is 5-6 months ahead of it, but it's confirmed it works.
[ONE Original Android Development] barisuraz:
What up now qualcomm?

---------- Post added at 02:56 PM ---------- Previous post was at 02:54 PM ----------

Hey boss can you please post the test zip like nikhil18 did with AnyKernel so that we can also use it on CAF based roms?
[ONE Original Android Development] erorcun:
Anykernel yapsam bile CAF farklı kamera driverı istediğinden çalışmaz.

(It won't work with Anykernel even because CAF uses different camera driver.)
[ONE Original Android Development] barisuraz:
Hasikiyim ya

(thanks for the effort)
[ONE Original Android Development] erorcun:
Hahaha sağol =D

(Thank you too)
[ONE Original Android Development] erorcun:
https://www.mediafire.com/?6b65w14zjlot7p0

I adapted stock 3.4 interactive governor and cpu-boost driver to 3.10, can anyone tell has frequency scaling problem gone now?

I'm not planning to use 3.4 things, just trying to diagnose the problem.

Also this build has zzmoove, intellimm, intelliactive and wheatley governors. But I haven't tested them. Already this build isn't intended to use as daily driver.

Edit: Off-screen gestures' switch path has changed starting from todays' LinOS build. It's normal if you run into some problem about gestures.
[ONE Original Android Development] Mecca EL:
I've been waiting for this moment, since you started this journey!!! Super excited.

Glad you found the gesture issue. Testing and will report. Thanks again :highfive:
[ONE Original Android Development] Mecca EL:
This is officially the best month of 2017!! [MENTION=4898631]erorcun[/MENTION] Thanks for all your hard work bro. Even when it was frustrating, you took a break, found your center, and made it work!!!
[ONE Original Android Development] erorcun:
Hahaha, you're spoiling me =D Thank you too as always.

What about frequency scaling and invalid target_freq problems, are they gone?
[ONE Original Android Development] Mecca EL:
Gone. Everything is working great so far. I haven't checked OTG yet, but I'll test and report
[ONE Original Android Development] erorcun:
There is no new progress on OTG, even it may be worse, we still have some way to go on it.

Then I will continue from 3.4 interactive gov. and cpu-boost driver. thanks =)
[ONE Original Android Development] erorcun:
Fixed some bugs. Also added Smartmax and Smartmax EPS too :silly:

New build(also putting to OP): http://www.mediafire.com/file/twzuwv8jqr2i7so/020217kernel310.zip

-----

Differences from 31/01 build:

* New governers added: Smartmax_eps, smartmax, wheatley, zzmoove, intellimm, intelliactive

* We're using 3.4 interactive governor & cpu-boost driver now, with some bugfixes.
[ONE Original Android Development] mysteres:
Flashed in tuga18 .

Superb Work ... I will edit later if i encounter something
[ONE Original Android Development] fmc000:
Works fine (idprophecy build) on Slim 7.1.1 . Only bug noticed so far: the battery stats are completely borked. I flashed the kernel with 50% of battery left, the phone booted with 25% and it stayed that way until now (about three and a half hour have passed). I have actually rebooted another time but it did not change.

Edit: USB-OTG still not working for my Kingston pendrive.
[ONE Original Android Development] erorcun:
Yeah I know, it's like that for a long time. But it's normal since I'm using completely different battery driver(OP 3's one), it just takes some time at start to adjust itself. I can develop some workaround about it but I don't want to.

Glad to see other problems are gone.
[ONE Original Android Development] fmc000:
Except OTG unfortunately.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] Shadowghoster:
All working well here on RR 5.8.1, thanks for all your efforts, guys!

CPU scaling is working properly and smartmax does its job well for me.

Something I am wondering about: the kernel version of most recent 3.10 linux kernel is 3.10.104 and this one is listed as 3.10.44 in phone info, so are we "missing" patches or is it just numbering? If we "miss" patches is it a big workload to patch the source up to mainline or not (is it even possible?)?
[ONE Original Android Development] fmc000:
USB-OTG included?
[ONE Original Android Development] erorcun:
It takes half a day to increase it .1, I have increased it .4 in past and I will continue to patch, but I don't know when it will reach to 3.10.104.
[ONE Original Android Development] Shadowghoster:
Nope didn't test it, but I can test after I found my cable... (I started writing my post before you posted)

[MENTION=4898631]erorcun[/MENTION] thanks for the info.

Edit: OTG doesn't work. And I see a lot of selinux errors regarding CPU. Log on Dropbox since mobile upload didn't work as attachment: Dropbox
[ONE Original Android Development] erorcun:
Hi.

I replaced my phone's screen and I'm ok now.

I found the mistake and OTG is solved forever now, currently all input devices works(device support is larger then stock kernel even) but for storage devices there may be problems related with selinux. But if selinux is in permissive then there won't be any problem for sure.

Can HDD/flash owners report does it work without permissive selinux? Thanks. http://www.mediafire.com/file/ca8jxx72punlh0d/130217kernel310test.zip

P.S. off-screen gestures may gone crazy. I didn't applied latest LinOS change. This is test build anyway.

Also I used old build for a week and I didn't encountered any reboot. I'm surprised actually.
[ONE Original Android Development] Syaani:
That's great news man! Thank you!
[ONE Original Android Development] Mecca EL:
Woo-hoo, you got it bro!!! USB-OTG is in full effect!! I knew you'd finally get it working. Thank you, thank you, thank you!!!
[ONE Original Android Development] Gawd:
I have a request, can you merge these commits in the future builds?

Mixplorer crashed as soon as I attached my external HDD using an OTG, with Permissive SELinux. Didn't recognize it. I'm attaching the logs.

Mixplorer crashed again with Enforcing SELinux, attaching the logs again. Didn't recognize in both cases.
[ONE Original Android Development] Mr.Ak:
It worked with Es file explorer! :D

However still unrecognizable by system.

Off-screen gestures also working fine.

Selinux status- enforcing.

Thanks!
[ONE Original Android Development] erorcun:
Only important line in that commit is SOFT_AICL_VOL one. And nikhil18 recommended me to do it before but I didn't want it due to it makes AICL less meaningful. But I will do it anyway. Btw, until new build is released you can disable AICL which will boost charge speed to max, but I forgot it's toggle path :silly: it's in qpnp-charger's dir and file name is disable_aicl.

For storage, everything seems ok on both logcat and dmesg, I don't know what to do.
[ONE Original Android Development] Gawd:
/sys/module/qpnp_charger/parameters/disable_aicl

Thanks for your work
[ONE Original Android Development] erorcun:
It's in /sys/devices/qpnp-charger-ed443000 btw :P
[ONE Original Android Development] Gawd:
I think I'm on a high dose of cocaine
[ONE Original Android Development] :
I've looked through the thread history, but can anyone here confirm that encryption works with /data and /cache as f2fs?
[ONE Original Android Development] erorcun:
It's enabled but nobody tested it after I've updated f2fs version.
[ONE Original Android Development] lumufei:
Any one tried this kernel on aosplus ROM ?
[ONE Original Android Development] Blackscorpion3:
[MENTION=4898631]erorcun[/MENTION] thank you so much for your hard work on this. I've been testing along with [MENTION=6277543]Mecca EL[/MENTION] since the beginning. Now, finally having usbOTG working fully, makes this my daily driver kernel.

Can't contain my excitment.
[ONE Original Android Development] :
Wow, really? I'll test if I can, only thing is I'm on a ROM with color os camera hal. Encryption with f2fs would be a dream come true
[ONE Original Android Development] erorcun:
=)

I hope the same too. Old ColorOS blobs just needs rotating the image so it's easy, for the new ColorOS(oxygen/sultan) one I've adapted the kernel driver for them too but auto-focus is currently broken, hope I can fix it in future.
[ONE Original Android Development] Prashanthme:
Phone in bootloop in rr nougat build.. Cache in f2fs.. Is it the problem
[ONE Original Android Development] erorcun:
My cache is in f2fs too. I don't know.