yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Original Android Development] coolypf:
Aosp & f2fs

Hi [MENTION=5996255]jollaman999[/MENTION] ,

Can I incorporate jolla-kernel with the latest AOSP 7.1.1 ROM and use F2FS for /data partition?

Thanks!
[Nexus 5X Original Android Development] jollaman999:
Of course. I'm using it now. :)
[Nexus 5X Original Android Development] coolypf:
That's great!
[Nexus 5X Original Android Development] :
Jolla, do you use f2fs on /cache? Just wondering because OnePlus only uses f2fs on /data.
[Nexus 5X Original Android Development] jollaman999:
Both /cache and /data
[Nexus 5X Original Android Development] Caspertje19:
Is it really worth converting everything to f2fs? Is it noticeable faster or is it just a placebo effect? I read so many opinions with different outcomes
[Nexus 5X Original Android Development] :
Everyone has different experience. Do it yourself and you will know. :o
[Nexus 5X Original Android Development] vampire36:
[MENTION=5996255]jollaman999[/MENTION] : Can you evaluate and see if adding blu_activ from eng_stk (1+3) latest one really would add value to bh ?
[Nexus 5X Original Android Development] Mrcactuseater:
That version of blu-activ is based quite heavily on 3.18 kernel where we have a 3.10. A lot of backporting would be needed by [MENTION=5996255]jollaman999[/MENTION]
[Nexus 5X Original Android Development] nirogu325:
I have one small feature request, if I may. Coming from other custom kernels I've noticed your kernel doesn't have many LED colors available, just the stock ones. Kernels such as the PureNexus stock kernel and the Phasma kernel display a wider range of LED colors for battery charging and notifications. I thought this feature would further complement your kernel.
[Nexus 5X Original Android Development] jugoslavpetrovic:
[MENTION=5996255]jollaman999[/MENTION]

Sorry for asking this. Is it possible to put decision of fsync into AROMA installer?
[Nexus 5X Original Android Development] jollaman999:
I will check if possible.
[Nexus 5X Original Android Development] jollaman999:
Is it same after select LED patch in AROMA installer option?
[Nexus 5X Original Android Development] jollaman999:
Okay, I will add it.
[Nexus 5X Original Android Development] nirogu325:
Yes. Very few color hues available, just like stock. I'd like to help you more but I don't know much about commits to point you to the right one, that's why I told you some kernels that have custom LED colors.
[Nexus 5X Original Android Development] khanjui:
I'm on mobile right now and it's really hard to find commits but probably this will help you. Just look the changes of 1.17 version. If I remember correct, that's what these guys talking about. [MENTION=5996255]jollaman999[/MENTION]
[Nexus 5X Original Android Development] jollaman999:
It must be related with this commit.

https://github.com/jollaman999/jolla-kernel_bullhead/commit/8b129e8a6bbbbe1631657fded7a3caf7ff723d8c

I just reverted because it shows mixed color with that patch.

Smooth LED mod must be a problem. I will find the reason.
[Nexus 5X Original Android Development] vampire36:
Thanks a ton! Looking forward to it :) Appreciate the efforts you putting in
[Nexus 5X Original Android Development] nirogu325:
Smooth LED means the smooth on-off animation, right? If so, I have it along with the better colors. Right now I'm testing Flash kernel, for reference.

Sent from my Nexus 5X
[Nexus 5X Original Android Development] vampire36:
[MENTION=5996255]jollaman999[/MENTION] : I see you already added blu_active...perfect buddy...waiting for your new build :) Thanks a lot for pulling it in this fast :) Really appreciate all the efforts :)
[Nexus 5X Original Android Development] jollaman999:
Yes, right. Thanks.
[Nexus 5X Original Android Development] jollaman999:
Nice discover! Thanks.
[Nexus 5X Original Android Development] mr.ace:
[MENTION=5996255]jollaman999[/MENTION] do you like merge zswap and upstream zram commits from The Flash kernel??
[Nexus 5X Original Android Development] jollaman999:
I heard that sometimes, upstream's swap and zram has not good effect.

So I didn't merge it since season II.
[Nexus 5X Original Android Development] vampire36:
[MENTION=5996255]jollaman999[/MENTION] : Not pushing you...but any time soon the new build coming up...wanna try blu_activ ;) Btw did you test the governor ? Hows it faring for you ?
[Nexus 5X Original Android Development] wpbear:
Yes
[Nexus 5X Original Android Development] jollaman999:
[bullhead-v4.2]

== Kernel ==

- msm_hotplug: Fix target_big calculation (Effective hotplugging and improve slow Wi-Fi.)

- sovc: Turn off touch screen when mic detected (Fix touchscreen working while on a call.)

== Recovery ==

- jolla-kernel_bullhead-v4.2 applied
[Nexus 5X Original Android Development] jollaman999:
Fixed touchscreen issue.

I'll more research about charging.
[Nexus 5X Original Android Development] bobby janow:
Then at this point you have only one troubleshooting option as I see it. Swap kernels and only the kernel. But that means you will have to reflash the rom which might fix it alone. If it works after swapping the kernel try it again with this one and report back. I had that problem about a week ago and couldn't figure it out. I have two chargers and when I tried it on my other one fast charge was there. It turned out that the Google double port charger only charges fast on one of the ports and not the other. (I just confirmed that on Elemental X kernel now) Nonetheless, I'm going back to Jollaman now since the touch thing is fixed. I'll test charging again.

---------- Post added at 08:02 AM ---------- Previous post was at 07:49 AM ----------

I'm sorry to say the vibration is still there during a phone call. Fast charging works. Would you like me to test anything. I went will defaults.
[Nexus 5X Original Android Development] jollaman999:
Try with this.

http://buf.jollaman999.com/Requests/sovc_test.zip

After flash it, enter this commands in terminal or adb shell.

su

cat /proc/kmsg | grep tomtom

Then open dial app and try phone call.

Please report what kernel says.

Thanks.
[Nexus 5X Original Android Development] bobby janow:
I'll attach as a notepad file.
[Nexus 5X Original Android Development] jollaman999:
Thank you for your log.

It says same as me and touchscreen turned off while on a call with mine.

I'm sorry, could you try again with v4.2?

In this case, please type this command.

cat /proc/kmsg | grep is_touch_on

If it working correctly, it says 'mic detected' when screen turned off while on a call.
[Nexus 5X Original Android Development] bobby janow:
Ok I'll do it now.

edit: It didn't say anything when I placed the call. No mic detected and still buzzing. Someone else probably needs to try it to see, perhaps something is different with my system. Proximity sensor doesn't go on either when I pull my phone away from my face.
[Nexus 5X Original Android Development] gleggie:
Performamce with this kernel has been phenomenal, very fluid with no stutters.

Quick question: If I am on v4.1, do I need to reflash my ROM before upgrading to v4.2?
[Nexus 5X Original Android Development] jollaman999:
Ok. Thank you very much for testing.
[Nexus 5X Original Android Development] bobby janow:
My pleasure. Just to clarify my system, I'm running latest Google image with Cataclysm Jan 6 mod over it. Flashed your kernel then superSU 2.66. Hopefully someone can test and we can compare if the mic detect goes on on their system. Thanks for the work.
[Nexus 5X Original Android Development] aamir123:
Been using this kernel for a few days now and the performance to battery life ratio is pretty good. I was trying to change the interactive governor settings in Kernel Adiutor and got the error that interactive is not tuneable on the big cluster. The little cluster is perfectly fine. Is this normal?
[Nexus 5X Original Android Development] skulldreamz:
[MENTION=5996255]jollaman999[/MENTION] i can't for the life of me get the a2dp checker app to ask for root permissions and i know it needs su to operate correctly. I listen to music so much every day using my bluetooth beats headphones and also use them to answer or make any phone call. Any help would be appreciated and also twrp still says 2.8.7.0 and it's up to 2.8.7.2 I know you said you were going to update twrp to the latest sources so just wanted to let you know about those 2 issues. Besides that i really love your work and the hotplugging is working like a champ. Maybe you could officially name your hotplug "jolla hotplug" or something so that it gets more recognition in the xda community and more people would probably be willing to try it, just a thought. Thanks again and looking forward to next release, keep up the good work ?

---------- Post added at 07:06 PM ---------- Previous post was at 07:01 PM ----------

The reason you can't tune the big cluster is because if the big cluster is offline then there is no way for any kernel app to see it's values to tune or tweak so it just looks blank in a kernel tweaking app. Once it comes online then try tweaking it
[Nexus 5X Original Android Development] bobby janow:
Skull, do you have the problem with phone vibration when in a call as I do above? I really want to go back to this but I use the phone a lot and it makes it unusable.
[Nexus 5X Original Android Development] aamir123:
This was fixed in 4.2.

Also I was able to tweak before with big cluster idling, I guess I'll have to change settings .
[Nexus 5X Original Android Development] skulldreamz:
Yeah since 4.2 all is working nice so far bobby
[Nexus 5X Original Android Development] aamir123:
Is there any way to adjust hotplug settings? I try to and they revert if I switch to a different heading in kernel adiutor. I need to get the big cores on to change settings.
[Nexus 5X Original Android Development] Schrotty35:
Can i use with pure nexus rom?

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 5X Original Android Development] jollaman999:
1. A2DP Check: I'm sorry. I don't understand what's the point of issue.

2. TWRP: Yes, I used lastest source and I saw other releases. It says 2.8.7.2 when they release it. But real source is updated version of 2.8.7.0. There are other higher versions more than 2.8.7.2.

3. hotplug: The original source is msm_hotplug developed by Fluxi. I just modified for big.little and I think we should keep original author.

Thank you.

Edit.

1. Check your SuperSU app if A2DP Checker is blocked.
[Nexus 5X Original Android Development] jollaman999:
That's because the original source developed only for 1 cpu. But our device uses 2 cpus (big and little).

So the real cores is 6. (2 for big and 4 for little.)

Kernel think there are 2 cpus and 6 cores. But msm_hotplug think there are only 1 cpu and 4 cores.

So there will be an issue when you are try to change core settings bigger than 4.

The modified msm_hotplug working as there is only 1 cpu (little/4 cores).

Then it will watch how many cores of little cpu are online after some delays.

If there are 2, turn on 1 core of big cpu.

If there are more than 2, turn on all of cores of big cpu.
[Nexus 5X Original Android Development] jollaman999:
Similar with interactive governor. But it must be change default values to increase performance.
[Nexus 5X Original Android Development] vampire36:
Cool waiting for you to push an update ;) So you playing with values for better performance ? Any eta :P
[Nexus 5X Original Android Development] eSpice:
On my device with root, TWRP and official ROM, after installing this kernel, there was an official OTA (android 7 to 7.1.1) which after trying to install it (I shouldn't have I guess!) my device gets stuck on boot with the message: " no command. ".

Is it possible to install an official OTA / IMAGE from google developer and not lose data?

Edit

I went on with the guide and everything is okay now.
[Nexus 5X Original Android Development] Psychofrantics:
[MENTION=5996255]jollaman999[/MENTION] I have a small request. I dont see touchboost option in kernel tuning apps. I mean a switch will be great.

If it is disabled, can you please add option for enabling touchboost? I dont feel like disabling touchboost. Thanks.

It is just a request if you feel doing that when you have time
[Nexus 5X Original Android Development] mr.ace:
[MENTION=5996255]jollaman999[/MENTION] why WQ POWER EFFICIENT is removed from source
[Nexus 5X Original Android Development] khanjui:
Those things are based on franco.Kernel so there is no "touch boost" setting. There is "input boost" setting which is enabled by default and little cluster is going to 1248 MHz, big cluster is going to 768 MHz when you touch to screen. You don't need to worry about it.
[Nexus 5X Original Android Development] jollaman999:
It makes little battery drain per hour in my test for a week. :(

About 5% drain in 2~3 hours with power efficient wq.

1~2% drain in 2~3 hours without power efficient wq.
[Nexus 5X Original Android Development] khanjui:
That's strange, should be opposite. But of course I trust to your tests. You may talk with Franco about it.
[Nexus 5X Original Android Development] kevtrysmoddin:
This is my first time using multi ROM and I have a question forgive me if this has been asked before but does multi ROM patch the secondary roms kernel when it installs it do I need to flash Jolla again after the ROM and gapps ??
[Nexus 5X Original Android Development] khanjui:
Just for your information.

http://xdaforums.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557/post70104070

[MENTION=5996255]jollaman999[/MENTION]
[Nexus 5X Original Android Development] jollaman999:
jolla-kernel is optional but recommended.

(There is a bug that multirom can't get device information from the secondary's kernel.)

You should install gapps to use play store.
[Nexus 5X Original Android Development] jollaman999:
That's unbelievable! Thanks. I should restore big cluster's min freq to 633.
[Nexus 5X Original Android Development] valeron94:
Wait a second guys, I'm using Jolla kernel and haven't touched any parameter. I do have the big cluster set at 633 at minimum :confused:
[Nexus 5X Original Android Development] gagp2p:
in the TWRP Thread i've read that this Kernel ZIP includes a working TWRP recovery (3.0.2-3) - where the EFS and backup / restore bug is fixed,

is it safe to only flash the recovery IMG from the zip or does it require the kernel in combination ?
[Nexus 5X Original Android Development] Stevica Smederevac:
You can flash only twrp
[Nexus 5X Original Android Development] khanjui:
Of course you can flash TWRP only. Recovery is a totally different partition.
[Nexus 5X Original Android Development] kevtrysmoddin:
Thanks
[Nexus 5X Original Android Development] jollaman999:
[bullhead-v12.0]

== Kernel ==

>> Common <<

- cpufreq: Added blu_active governor

- sdcardfs: Fix NULL pointer dereference

- Revert system_power_efficient_wq changes (It makes battery drain in idle state.)

- leds-qpnp: Multi-color smooth LED support

- leds-qpnp, mdss: Decrease led brightness when mdss backlight is less than 35%

- leds-qpnp, mdss: Add led adjustment when mdss backlight is 35~49%

- mdss, sovc: Prevent race condition when turning off the screen

- dt2w: Fix wrong touch range detection (Fix dt2w or dt2s is working when x or y is same with previous value.)

- dt2w: Fix wrong ignoration check in fb notifier (Fix screen off issue by double tap.)

- dt2w, sovc: Unregister dt2w when dt2w, dt2s and sovc are disabled

- mdss: CyanogenMod LiveDisplay support with kcal

- mdss: kcal: Fix conflict between LiveDisplay and kcal_fix_yellow

- cpuidle: don't disable cpuidle when entering suspend (Lower idle power consumption.)

- drivers: wakeup: add qcom_rx_wakelock wakeup bypass option

- f2fs: Applied dev branch patches

- kexec: Appiled linux-master upstream patches

- arm64/crypto: remove redundant update of data

- arm64: crypto: assure that ECB modes don't require an IV

- crypto: arm64/aes-ctr - fix NULL dereference in tail processing

- crypto: xts - consolidate sanity check for keys

== AIO ==

- ramdisk: disable subsystem ramdump on userdebug builds

- ramdisk: disable modem ramdumps

- ramdisk: Restore big cluster's min freq to 633Mhz

- updater-script: Remove sovc_auto_off_delay line when sovc is disabled

- led: Update led binaries

== Recovery ==

- Built with lastest cm-14.1 sources (Android 7.1.1_r6)

- Merged TWRP 3.0.3 changes

- Change MultiROM TWRP base to nkk71's source

(It also changed the theme to dark one that similar with official theme. MultiROM menu button is located on top right.)

- Revert "Fix adb shell in 7.0 tree" (It doesn't show current directory.)

** Known Issues **

- No issues! :laugh::good:

Sorry for late release.

I am busy these days because I'm preparing for employment.
[Nexus 5X Original Android Development] pepa 77:
Thanks very nice kernels :good:
[Nexus 5X Original Android Development] Nicktheprofessor:
I hope you don't mind me asking but what is it with the version update to 3.10.104 where all the patches you added, one by one, are nothing but an inflation of the version number?

If you look at the actual patches here: https://www.kernel.org/pub/linux/kernel/v3.x/incr/ you'll see that that is about 350 000 lines of code that should have been added with those patches (some of it is already included in the kernel to make things work but 99% of it isn't).

I hope you don't take this as anything but what it is, i'm just informing you of the matter and i know you were not just inflating the version number but rather adding worthless patches from a unreliable source (the 3.10.y from kernel_common).

I'm adding the actual patches to another but very similar codebase, hit me up if you want a squashed update 73-104.
[Nexus 5X Original Android Development] jugoslavpetrovic:
Marshmallow, jolla v12, screen light can't be adjusted it's stays lite as on max, also when screen off it's not off. Seems like screen is off but how to say lightning of the screen is still on.
[Nexus 5X Original Android Development] zurik:
In Jolla - Recovery, if I don't want multirom , I will uncheck the "inject multirom ... ..." when I go to flash the zip?
[Nexus 5X Original Android Development] jollaman999:
I also heard this issue from other user. I'll check. :(
[Nexus 5X Original Android Development] jollaman999:
I'm merging patches one by one from here.

https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?id=refs/tags/v3.10.104

It's same with patch files that are included in 'incr' directory.

I did not change just version.
[Nexus 5X Original Android Development] jollaman999:
Yes. But it will not work when you not installed multirom.
[Nexus 5X Original Android Development] zurik:
I don't want multirom in my device.
[Nexus 5X Original Android Development] jollaman999:
Uncheck inject multirom. Then you can use as normal TWRP recovery.
[Nexus 5X Original Android Development] jugoslavpetrovic:
I did a clean flash off all and it seems that it doesn't behave like that now. Maybe there was something if flashed over 11.2 or has something to do with LED light charging cuz I skipped it this time.
[Nexus 5X Original Android Development] jollaman999:
Yes, it seems related with LED patch. I will fix it. Thanks.
[Nexus 5X Original Android Development] pepa 77:
hi can you help me please explain what is the problem ? I don't have a problem on version 12
[Nexus 5X Original Android Development] jollaman999:
It seems updated LED binaries make problems in mashmallow.

I will release new version soon.
[Nexus 5X Original Android Development] jollaman999:
[bullhead-v12.1]

[bullhead-v12.1]

== Kernel ==

>> Common <<

- mdss, sovc: Call container_of() after all of checks finished

- mdss, sovc: Do not try turn off mdss when screen turned on

- mdss: Cancel mdss_off_work work before turning off mdss

- mdss: Fix kernel panic after added LiveDisplay support

== AIO ==

- liblight: Build with static liblog (Prevent library conflicts in some of roms.)

== Recovery ==

- jolla-kernel_bullhead_II-v12.1 applied

** Known Issues **

- No issues! :laugh::good:
[Nexus 5X Original Android Development] :
hey man, can you try this? :o
[Nexus 5X Original Android Development] jollaman999:
I don't know about this commit.

But I'll check if this is good to merge.
[Nexus 5X Original Android Development] :
thank you! it is on Flash kernel :)
[Nexus 5X Original Android Development] jugoslavpetrovic:
[MENTION=5996255]jollaman999[/MENTION] flashed 12.1 marshmallow, with charging support the same issue as in v12.
[Nexus 5X Original Android Development] jollaman999:
Hmm... Then it will be good to use previous binary. :( (No matter with cm-13.0)

Okay, I will release again with some fixes.
[Nexus 5X Original Android Development] jugoslavpetrovic:
Its not a big deal [MENTION=5996255]jollaman999[/MENTION] I m usually not using that charging led, I just wanted to see what it is and where it is to control it, Im using light flow app for all led customization. I just reported that there is still the issue so you know:)
[Nexus 5X Original Android Development] jollaman999:
You're right.

Thank you for feedback! :good:
[Nexus 5X Original Android Development] jollaman999:
I just tested with simple code to know how this value changed.

But I will withhold this commit.

Because there is no way to check guarantee with this commit by now. :rolleyes:
[Nexus 5X Original Android Development] khanjui:
https://plus.google.com/111702498717953225050/posts/PCcWMhsS5a8
[Nexus 5X Original Android Development] jollaman999:
[bullhead-v12.2]

== Kernel ==

>> Common <<

- tcp: fix more NULL deref after prequeue changes

- mdss: kcal: Prevent race condition when changing kcal values

== AIO ==

- led: Back to old binaries

(Source is same. But new build brick the marshmallow cause of depedencies.)

== Recovery ==

- jolla-kernel_bullhead_II-v12.2 applied

** Known Issues **

- No issues! :laugh::good:
[Nexus 5X Original Android Development] jollaman999:
Thanks. :o
[Nexus 5X Original Android Development] coolypf:
Hi,

I am running jolla-kernel with stock 6.0.1 rom and see the following in dmesg:

[ 3.025062] fsck.f2fs: CANNOT LINK EXECUTABLE: cannot locate symbol "__write_chk" referenced by "/system/bin/fsck.f2fs"...
[Nexus 5X Original Android Development] jollaman999:
Okay, thanks. I will check and fix it.
[Nexus 5X Original Android Development] leolawliet:
[MENTION=5996255]jollaman999[/MENTION] I really appreciate what you're doing to keep multirom and TWRP up to date. I just wanted to say thanks for that :)
[Nexus 5X Original Android Development] jollaman999:
My pleasure. Thank you. :laugh:
[Nexus 5X Original Android Development] jollaman999:
[bullhead-v12.3]

== Kernel ==

>> Common <<

- drivers: power: Fix 2% battery level drop

- f2fs: Revert dev branch changes to merge stable branch

- f2fs: Merge stable branch changes

== AIO ==

- f2fs-tools: Merge block zone support changes (Not yet supported by kernel.)

- f2fs-tools: Make binaries statically (Fix link error.)

- Merry Christmas! Happy new year! :)

== Recovery ==

- Re-built with lastest cm-14.1 sources

- f2fs-tools: Make binaries statically

- jolla-kernel_bullhead_II-v12.3 applied
[Nexus 5X Original Android Development] jugoslavpetrovic:
Thanks.

How about fsync to include beside dynamic fsync? Also maybe to include it in arome so ppl could choose.
[Nexus 5X Original Android Development] khanjui:
As I know dynamic fsync off = static fsync on.
[Nexus 5X Original Android Development] jugoslavpetrovic:
Oh, I guess you are right, that could make sense but I wasnt sure. Are you sure? Cuz with some kernels I get fsync option in kernel manager but with this one I get dynamic fsync option in same kernel manager.
[Nexus 5X Original Android Development] khanjui:
Like I said "as I know" when you turn off dynamic fsync, it will act like static fsync is on. I believe it's impossible to have dynamic and static fsync at the same time.

If dynamic fsync is on, file synchronization will continue when screen is on, it will stop when screen is off.
[Nexus 5X Original Android Development] jugoslavpetrovic:
This actually is logical as you say. Thanks.
[Nexus 5X Original Android Development] jollaman999:
khanjui is right. I will add option for dynamic fsync instead.