yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] SirSoviet:
ADB is broken, device is offline/unauthorized.
[ONE Original Android Development] tofu:
Try changing the usb mode in developer settings to anything else except "MTP" (PTP, audio, midi etc. )
[ONE Original Android Development] tofu:
Flashed this over clean flashed, encrypted slim7 --> data corrupted.
[ONE Original Android Development] erorcun:
I'm really sorry.

If you're angry, you should know encryption problems are expected in kernel development, this is why I put warning to OP about encryption. I will upstream ext4 crypto codes if I can find anything new. Sorry again.
[ONE Original Android Development] fmc000:
FWIW, I had flashed a previous version on my slim7 installation, encrypted with android 6, and it worked fine. All ext4, non f2fs.
[ONE Original Android Development] Mecca EL:
I don't know what you did, but I've been testing this kernel when it was at its worse, and never had corruption of data.
[ONE Original Android Development] tofu:
Oh, sorry, I wasn't angry, it was just a report :) I had just couple of minutes before wiped my entire device (and made backups before) in order to install slim7. I also wanted to test this kernel, but it ended this way. Maybe it was because my /cache was f2fs ?
[ONE Original Android Development] erorcun:
Oh, ok then.

My cache is in f2fs too, I don't know what could be the problem :/
[ONE Original Android Development] nikhil18:
[MENTION=4898631]erorcun[/MENTION] are you going to enable cpusets or is it unstable thanks

And has any one noticed that the battery is draining faster till 90% then then the drain becomes slower it might be placebo
[ONE Original Android Development] erorcun:
I don't know what is cpusets, I haven't enabled it due to it's not enabled in CM. I'm looking to it now.

No I didn't notice it.

It's insane that latest build has been downloaded ~1000 times but we're max. 10 people :silly:

Btw, can anyone test that in it's free time? http://www.mediafire.com/file/nuaf77n6eo2zhnj/170217kernel310.zip

It's supposed to fix OTG storage devices, so you shouldn't need Mi/Es explorer.

Actually I found the fix but I'm trying to add it to AnyKernel script.
[ONE Original Android Development] idprophecy:
Can confirm that it works. Good job as usually, [MENTION=4898631]erorcun[/MENTION]!

BTW, I updated my builds in the morning, ready in mega.
[ONE Original Android Development] erorcun:
Alright, new build is up then: http://www.mediafire.com/file/nuaf77n6eo2zhnj/170217kernel310.zip

OTG storage devices is ok now too(I hope I won't spell OTG anymore), fixed the gestures for latest LinOS builds and Linux version is updated to 3.10.50.

AICL is tweaked again, so it takes more current from some chargers.

Also there is an update in charger parameters. They're placed in: /sys/devices/qpnp-charger-ed443000

I made a list with all of them.

You need to reach them from some terminal app or adb shell.

threea_charge

Making it 1 will activate experimental 2.5A charge. It's triggered if AICL mA is 2000(if you're not sure about AICL mA, simply disable AICL by below parameter), temperature is appropriate and screen is off.

Only use if you have 2.5A or above charger. Don't use QC's Quick Charge adapters.

Untested, but can't damage your phone.

disable_aicl

Making it 1 will disable AICL and charger driver will always try to take 2A from your AC/wall charger (there's no problem if you charger isn't 2A)

You need to replug adapter to see the effect.

max_aicl_rate New in this build

Max. charge current. (Not exactly if it's below 0 Celsius)

It should be one of those: 100,150,500,900,1200,1500,2000. Other values will be rounded. Values below then 100 and higher then 2000 won't be accepted.

Has no effect if AICL is disabled via above parameter.

If threea_charge is enabled and this parameter is 2000, max current will be 2.5A.

You need to replug adapter to see the effect.

fast_usb_charge New in this build

Making it 1 will charge your phone through 900 mA if it's charging via USB port.

You need to replug adapter to see the effect.

charge_limit

It only accepts values between 0-100. Charger driver will cap charge percent to entered value. It's known that capping it to 50-60 percent increases battery life.

Making it 100 will revert the effect.

soft_aicl_vol New in this build

It must be between 4350 and 5000.

Default is OP2 value (4465 - but algorithm is different from LinOS and you shouldn't directly enter Sultan's or LinOS's value).

Don't change that if you don't know what it is.

-----

Hey! There is a change in ramdisk, if you're developer you should change the line that recognizes usb disks in fstab with that:

/devices/*/xhci-hcd.0.auto/usb auto auto defaults voldmanaged=usb:auto

To do:

- Use latest Linaro Uber 6.0 toolchain if you can find better net somewhere
[ONE Original Android Development] SirSoviet:
adb devices still returns "offline" status, I've tried everything to fix it at this point. What kind of logs will help you troubleshoot this issue? last_dmesg, kmsg or what?
[ONE Original Android Development] LPW00:
Any Ideas? My Bacon gets grilled atm because I can't set min frequency below 1881mhz

Edit: sry I tried to attach a video..
[ONE Original Android Development] mp3deviant721:
Stupid question, but what terminal commands do you use to change the charge parameters? Or can you open up the files with a root capable file explorer and add in the values that way?
[ONE Original Android Development] Gawd:
In terminal emulator

su
echo 1 /sys/devices/qpnp-charger-ed443000/<rest of the path>
[ONE Original Android Development] mp3deviant721:
Awesome. Thanks man!
[ONE Original Android Development] Gawd:
Finally!!

Thanks good man! [MENTION=4898631]erorcun[/MENTION] :D

Can anyone confirm 2.5A charge? I don't have that capacity adapter..
[ONE Original Android Development] Fenvarien:
Thanks for the awesome development work, it's great to have a working 3.10.x kernel running on the OPO. :good: :)
[ONE Original Android Development] codgician:
Your data might be fine. Try revert to official kernel and clear cache.

Since this kernel is for Lineage OS, you may encounter problems on other roms, even on some unofficial lineage OS roms.
[ONE Original Android Development] SirSoviet:
Can anyone else please check if ADB works with this kernel? Thanks. Would be nice if someone replied.
[ONE Original Android Development] Gawd:
Will do tomorrow
[ONE Original Android Development] erorcun:
dmesg could be useful.

I have no idea.
[ONE Original Android Development] SirSoviet:
The thing is, I can't get logs because adb doesn't work..... Damn.
[ONE Original Android Development] Gawd:
Use this app
[ONE Original Android Development] SirSoviet:
Dang, that's a nice little app! I'll be taking logs now...
[ONE Original Android Development] thecoolkid:
It doesn't boot on my RR-M 5.7.4. Is M supported?
[ONE Original Android Development] LPW00:
I don't think so
[ONE Original Android Development] thecoolkid:
So I think the thread title should be changed ?
[ONE Original Android Development] erorcun:
I've never used Nougat. Title says it works on LinOS M/N.
[ONE Original Android Development] thecoolkid:
RR is based on CM (LinOS)
[ONE Original Android Development] erorcun:
Then there is something different in RR which makes it unable to run this kernel.
[ONE Original Android Development] stryker09:
Works on LOS N just fine here, must be RR issue
[ONE Original Android Development] thecoolkid:
I see, that's a shame...
[ONE Original Android Development] nikhil18:
[MENTION=4898631]erorcun[/MENTION] with latest build mtp Is not working I can't access my storage on PC is anyone else facing the same problem thanks
[ONE Original Android Development] Gawd:
Yes, I was gonna write the same thing. Also, no ADB as [MENTION=6917522]SirSoviet[/MENTION] said
[ONE Original Android Development] codgician:
The latest kernel is quite stable, though there are few problems:

1. MTP won't work.

2. Gestures won't work (like draw O to launch flashlight), only double tap to wake is working fine.

Anyway these issues don't affect me quite much. Just to say you've really done a great job and thanks for contributing to this device!
[ONE Original Android Development] FunkyRasta:
Quick report about AndroidPay:

Tested on latest official LineageOS with Magisk v11.1

On stock and on Boeffla kernel everything is OK. But with 3.10 kernel Magisk cannot determine CTS status (circle is circling forever). AndroidPay doesn't outright say you have modified device but is unable to add a card.
[ONE Original Android Development] natheux:
RR can't run this kernel, I tried the latest build yesterday and the kernel tried to encrypt my data and, so, corrupt my data.
[ONE Original Android Development] Prinz`:
Weird. I had this kernel on RR and I faced no such issue.

And [MENTION=4898631]erorcun[/MENTION] this kernel is so damn smooth and ultra responsive! On Marsh 2.0, June 22md build right now, with your kernel. So damn responsive and complete awesomeness! Keep up the good work mate!! Cheers :)
[ONE Original Android Development] darjwx:
Afaik its the same problem as boeflla and RR.

RR has some stuff in kernel side and sources that differs from LOS and make the rom usually incompatible with some kernels.
[ONE Original Android Development] tofu:
Formatted everything EXT4. Clean flashed latest 13.2 official LinOS nightly, encrypted, checked that everything works, and then flashed this kernel --> data corrupt.

However, I can decrypt my data with TWRP normally, and nothing seems corrupt... but the rom itself is naturally unusable.

Again, just reporting (and hoping that some guru can fix these issues).
[ONE Original Android Development] erorcun:
24/02 build is up, USB peripheral (MTP/ADB) fixed and been upstreamed a bit.

http://www.mediafire.com/file/b9to659q8ma8vbo/240217kernel310.zip

Thank you =) I tried to fix gestures in latest build, can you test it?

[MENTION=4633983]nikhil18[/MENTION]

cpusets are handy only on devices with CPU clusters, so I won't enable.
[ONE Original Android Development] nthacks:
Gestures were already working fine in the previous build as well in Tugapower N22 ROM
[ONE Original Android Development] Mr.Ak:
New build confirmed working fine with latest cm based Miui 8.

Infact it fixed the sleep wake power bug on miui8.

Great battery life and awesome charging speed.

Gestures was working fine on previous builds too and on this new build too.

Nice work mate! [MENTION=4898631]erorcun[/MENTION]
[ONE Original Android Development] nthacks:
After flashing latest build, my battery stats seem to be stuck at 41% for some reason.
[ONE Original Android Development] erorcun:
It's because of the recovery has another battery driver, it should be fixed after a while.
[ONE Original Android Development] fmc000:
It will work again after a full charge.
[ONE Original Android Development] meph02:
thanks for update
[ONE Original Android Development] codgician:
Gesture is now working well. Thank you!
[ONE Original Android Development] Mr.Ak:
Hello! [MENTION=4898631]erorcun[/MENTION]

I know I'm not allowed to ask for features but is Energy Aware Scheduling (EAS) possible for Bacon?

To know more about it,

https://www.linaro.org/blog/core-dump/energy-aware-scheduling-eas-project/

Thanks!
[ONE Original Android Development] erorcun:
It will be hard to do it on 3.10, but if I will port 4.4 or mainline kernel sometime I will enable it most probably.
[ONE Original Android Development] anzi2001:
Is 4.4 even possible to port to our device?
[ONE Original Android Development] iRhyiku:
Everything is possible.
[ONE Original Android Development] nikhil18:
[MENTION=4898631]erorcun[/MENTION] still the sync threshold is ramping the frequency a lot(hence the smoothness) and due to that the battery life has been worse than 3.4 kernel can we use the msm performance hotplug touch boosting like Sony is using it on their 3.10 kernel with CPU quiet on msm8974 devices I know it needs hmp patches but sync threshold is not worth it and none of the new devices are using it thanks also can you include the ROM building fixes which I sent you on hangouts so that ROM developers can include this kernel in their ROMs (some more header files may need changes)
[ONE Original Android Development] erorcun:
... if there's something wrong then I should take a look to cpufreq, cpuidle or hotplug codes, using CPUQuiet or another boost thing and disabling mpdecision will just shadow the real problem, it's overshot and ridicilous.

And this kernel has JUST new features, has not any behaviour change. Only button backlight enablement condition is an exception to that.

And yeah EAS is there in 3.18 but why would I port 3.18 while there is msm 4.4 kernel.
[ONE Original Android Development] nikhil18:
If I disable sync threshold the kernel works normally as the 3.4 but then the smoothness takes a hit and why do we need sync threshold when all other devices even nexus 6 have ditched it and its just increases battery consumption and giving us the false feeling of smoothness but when its just boosting the cpu to the set frequency for a long time
[ONE Original Android Development] Mr.Ak:
Wow,4.4!

Thanks!
[ONE Original Android Development] Mecca EL:
I turned off hotplugging a while ago, which helped keep the kernel in check. I'll post a pic of my battery performance, but using [MENTION=4511190]idprophecy[/MENTION] ROM and this kernel, I can easily get 14hrs on one charge, with heavy use. No performance or kernel tweaks, other than using Conservative, max/min freq set to 2457/300, gpu set to cpufreq, I/O on noop - Read Ahead at 1024kb, and TCP set to westwood.
[ONE Original Android Development] LPW00:
There will be 4.4?! Wow! Sry OnePlus, I keep my OPO a bit longer, no new phone for me.
[ONE Original Android Development] erorcun:
No, there is nothing certain =D
[ONE Original Android Development] Gawd:
But if you'd be porting it in the future, you'll enable EAS right? :D
[ONE Original Android Development] erorcun:
Hahaha, right =D
[ONE Original Android Development] LPW00:
There's no exact plan on a new phone too. At least not this year...
[ONE Original Android Development] natheux:
I think you must format your OPO to full ext4 before installing this kernel. Because every time I want to install it on f2fs, it show the "data corrupted" message. Anyway thank you for your hard work !
[ONE Original Android Development] erorcun:
I think I know the reason, probably it's due to I've enabled f2fs encryption :/ will revert it in next build.
[ONE Original Android Development] Mecca EL:
I was formatted to f2fs before I installed this on my 2nd OPO. What version of twrp are you using? My recovery is Philz - twrp was bad with installing the radio file a while back, and I can only imagine what else doesn't get installed.
[ONE Original Android Development] kkq29:
does it work on last rr 582? :D
[ONE Original Android Development] Mecca EL:
If it's CM/LOS based, yes.
[ONE Original Android Development] erorcun:
Guys, how is this build's power consumption for you?

http://www.mediafire.com/file/5a802kyzy003f27/270217kernel310.zip

Cpu-boost values must be untouched.

It has load_based_syncs enabled and migration_load_threshold is set to 20 percent. (these are 3.10+ features that I disabled until now)

You guys can make some experiments with migration_load_threshold, which is placed in sys/module/cpu_boost/parameters.

I can increase it up to 30 percent if there won't be any problem.

Migration_load_threshold = min. cpu load needed to sync cpus while migrating some thread to another cpu. increasing it too much will make sync feature unusable, and this will make migrations laggier.

Also please inform me if you live any problems about Wi-Fi, I updated prima in this build.
[ONE Original Android Development] nikhil18:
Have you tried profile GPU rendering from dev options cause it shows the ui smoothness all the red bars above the green line is lag load based sync is useless I have back ported it on 3.4 kernel and according to my observation it just cancels sync threshold but I may be wrong
[ONE Original Android Development] SirSoviet:
What will happen if I change sync threshold and input boost?

Anyways, I disabled both those and I'm getting significantly better battery life. 1 hour of SOT with 86% battery remaining, with smartmax.
[ONE Original Android Development] erorcun:
Yeah it cancels but only below that percent.

It's great. Zeroing sync_threshold will disable migration boost btw, which is something I'm not gonna do due to there is no and shouldn't be any behaviour change in this kernel. (But i will use it personally actually...)
[ONE Original Android Development] nikhil18:
OK but it would be great to implement msm performance (when your free ofc) touch boost because of that Sony has remove CPU boost configuration in their power file so no sync threshold or load based sync https://github.com/sonyxperiadev/device-sony-shinano/blob/n-mr1/rootdir/init.shinano.pwr.rc
[ONE Original Android Development] natheux:
It works on RR if you format your partitions to ext4. Tested and confirmed
[ONE Original Android Development] erorcun:
I'm NOT gonna add it.
[ONE Original Android Development] kkq29:
would u share stock kernel please :)
[ONE Original Android Development] erorcun:
Latest prima driver just caused some crash on my phone :/ I won't include it. Current one seems to be working on most of prima FWs.

And I will measure the current with various migration_load_thresholds but probably release next build with 25% migration_load_threshold, which should decrease power consumption a bit.
[ONE Original Android Development] Mecca EL:
Had some freezing, after updating to the latest version.
[ONE Original Android Development] erorcun:
There is nothing readable :/ but it was due to prima probably, which is reverted in this build.

New build is up; http://www.mediafire.com/file/4nsws8bg8cg8tm2/280217kernel310.zip

Addendum: Don't install it. 29-02 build is on the way.

f2fs encryption disabled (should fix f2fs problems), migration fairness fix from mainline linux kernel, sched load based boost freq and blocking migration boost if cpu load is below 25 percent.

Should decrease power consumption a bit. Please report if there is any decrease in performance.
[ONE Original Android Development] Mecca EL:
Good deal! Will report any findings :highfive:
[ONE Original Android Development] Mr.Ak:
Hello! [MENTION=4898631]erorcun[/MENTION]

What's new in 28 dated build?

EDIT:Got it,nevermind!
[ONE Original Android Development] Mecca EL:
[MENTION=4898631]erorcun[/MENTION]

Installed fine, but after reboot my screen is non responsive
[ONE Original Android Development] erorcun:
01-03 build: http://www.mediafire.com/file/ar65tcqcprlljlz/290217kernel310.zip

Reverted the things I've did for "migration boost" after 24-02. I won't care about "more" battery anymore, it's ok for me.

Also upstreamed again.

I got bored again, so I won't release any new builds for a while. But I'll be here. Thanks to everyone.

Edit: lol there is no 29-02 :P It's 01-03 build

Edit2: Lol I'm pulling this build too. I'm having a bad day. Please continue from 24-03 build.

Edit3:

(facepalm) it was due to my faulty touchscreen, it's up again now.
[ONE Original Android Development] Mecca EL:
Is it not working?
[ONE Original Android Development] Mr.Ak:
Finally!

The latest build works fine on Aosp+Caf Roms!!!

No more storage and camera bug.The only issue is I'm not able to turn off the capacitive buttons backlight,else all fine.

Edit: Now able to turn off Capacitive button backlight.

Thanks bruh!
[ONE Original Android Development] kkq29:
hmm would it work too in aospa 6.0 since it based on caf too ;)
[ONE Original Android Development] Mr.Ak:
Yes it will...
[MENTION=4898631]erorcun[/MENTION] I think it's safe enough to write "[AOSP]" in Thread title :D
[ONE Original Android Development] Mecca EL:
What I like about this update is, on the previous one I didn't notice anything different or missing. On this one, I'm definitely able to "feel" a speed difference. I didn't think this kernel could be anymore responsive, I was wrong. Excellent work [MENTION=4898631]erorcun[/MENTION].

I know building this can be frustrating as hell, when you were gone I made an attempt, and it was hard. I have much respect and adoration for what you do. Good job!
[ONE Original Android Development] erorcun:
What the... This is weird =D I found out the commit that adds CAF/AOSP support then. But I won't add AOSP to title because it means more responsibility.

Btw latest build causes some reboots on me, so I don't recommend using it.

=) thank you as always.
[ONE Original Android Development] SirSoviet:
Yep, with default config I get reboots when I have my phone sleeping while TiBu restores apps.
[ONE Original Android Development] Mecca EL:
As soon as I read this, I got a reboot :laugh:

I'll mess with the settings, and see what I come up with. Anything catastrophic, I'll send a log. :highfive:
[ONE Original Android Development] Mecca EL:
It went catastrophic
[ONE Original Android Development] Mr.Ak:
Yeah,I understand, bringing this kernel to this point working with many roms out there and adding awesome features to it,is itself a legendary work.Thanks!
[ONE Original Android Development] Mr.Ak:
[MENTION=4898631]erorcun[/MENTION]

Confirmed working fine with AOSiP latest weekly build too..

Just some random auto wake sleeps.

Issue with camera when using with flash.A clean while border can be seen in images like a separator or so...weird. See attachments for example.
[ONE Original Android Development] codgician:
I'm experiencing some issue with Bluetooth. When I connect my phone with my Bluetooth headphone and play music using Google play music, there is a big possibility that the device will reboot randomly. I'm not sure if it is related to the kernel. I'll try to grab some logs perhaps a few days later because currently it's inconvient for me to do so.
[ONE Original Android Development] erorcun:
Which build is it, 01-03? It reboots independently from bluetooth :p I recommend using 24-02 if you're using 01-03 one.
[ONE Original Android Development] codgician:
Yep. Thank you!
[ONE Original Android Development] Mr.Ak:
Don't just say it.... Hit it!:p
[ONE Original Android Development] kkq29:
290217 when click for 010317? :confused:
[ONE Original Android Development] SirSoviet:
2017 isn't a leap year, so the 29th of February didn't exist this year. Erorcun forgot about it, and named it the 29 build instead of 01.
[ONE Original Android Development] kkq29:
lol little bit:laugh: tricky
[ONE Original Android Development] Mr.Ak:
You're advised to stick with 24th dated build as of now.
[ONE Original Android Development] Claudiosvs:
Any chance of merging ab123321's work on OOS blobs?
[ONE Original Android Development] Mr.Ak:
Most likely it'll be a no for obvious reasons.
[ONE Original Android Development] Queentus:
flashed the latest version on Lineage OS nightly 0306, both Google Camera (came w/ GApps) and stock Lineage camera break.

previously I used ba123321 kernel w/ OOS camera blobs, but I think they have nothing to do with the camera issue because I totally reflashed my ROM.

anybody know a fix? Or is this kernel currently just not compatible with the latest Lineage OS?
[ONE Original Android Development] Mecca EL:
3.10 kernel works great with LOS. See if wiping the camera cache will remedy the issue
[ONE Original Android Development] Mecca EL:
Figured I'd give the March 1st build another go, since there have been a bunch of changes in LOS, and other than MP Decisions throwing log errors, my phone has been running just fine. I activated MP Decisions in Kernel Adiutor, where I once had it deactivated. I just updated my LOS by [MENTION=4511190]idprophecy[/MENTION] and am on the latest Magisk
[ONE Original Android Development] SirSoviet:
You're saying that the rom is causing the random reboots and not the kernel?
[ONE Original Android Development] Mecca EL:
That my have been what causing the boot loops, but I'm not sure. What I am sure of is that it's working fine now.
[ONE Original Android Development] SirSoviet:
It's still horrendously unstable for me, device hangs and is completely unresponsive (animations still play) and there's reboots when screen is off. Tested on official Lineage build from today.