yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Original Android Development] jollaman999:
[jolla-kernel_bullhead-v3.0]

== Kernel ==

- hotplug: Add msm_hotplug driver and adaptive for big and little

- touchscreen: Add doubletap2wake and sweep2wake

- touchscreen: Temporary enable dt2w when playing music

- leds-qpnp: Smooth blinking charging LED & smooth notifier LED

- power:qpnp-charger: extended charge time from 30s to 100s when battery status is near to full

- hwrng: Avoid manual device_create_file() calls

- cpufreq: Add impulse elementalx, wheatley, impulse, conservative governors

- cpufreq: interactive: Applied some of patches

- tcp: enable sockets to use MSG_FASTOPEN by default

- mdss_fb: backlight dimmer option

- power: Disable the lge crash handler

- f2fs: Fix a system panic caused by f2fs_follow_link

- f2fs: remove unnecessary new_valid_dev() check

- f2fs: Add f2fs_kvfree from f2fs-stable repository

- random: Add /dev/frandom support

- random, random32: Applied Linux upstream patches

- zram, zsmalloc, zpool: Appiled upstream patches

- crypto: msm: Appiled some of patches

- md: Appiled some of patches

- dm verity: Appiled some of patches

== Recovery ==

- Built with lastest omni android-6.0 branch TWRP sources

- Use lastest cm-13.0 sources as base

- f2fs-tools: v1.6.0 applied

- jolla-kernel_bullhead-v3.0 applied

== AIO ==

- fstab.bullhead: Fix f2fs boot issue

- A2DPChecker: Temporary enable dt2w when playing music

- Revert "disable device verification of /system /vendor"
[Nexus 5X Original Android Development] jollaman999:
OK. I'll check later.
[Nexus 5X Original Android Development] buru898:
I still got reboots after completely removing any themes...

What I did was flashing to the previous kernel and installed busybox in the proper location... So far so good.

You're probably right, maybe I need to reformat my data partition. This just started happening yesterday while I was in my car on Google Maps and playing music from Rocket Player via Bluetooth. There must be a connection there!
[Nexus 5X Original Android Development] skulldreamz:
Yeah i would do i complete clean install and then flash supersu 2.67 and then j-kernel 5.2 and you'll be squared away. I use Google maps on a daily basis and i have never had a issue with a single thing. Never a random reboot since this kernel has been alive. What package of gapps do you use if you use a custom rom?
[Nexus 5X Original Android Development] buru898:
I installed cataclysm so it's stock gapps from that.

Yeah I wasn't having any issues on the new version, I am thinking its my data partition that's messed up.
[Nexus 5X Original Android Development] mohammed510:
No plans for cpu oc? :)
[Nexus 5X Original Android Development] jollaman999:
I'll consider it.
[Nexus 5X Original Android Development] Maritus1:
I will never understand why there is any need for OC on the 5x, except for benchmarking. The device is fast as hell and I personally do underclock to get better battery life and don't notice a real difference in daily life tasks...
[Nexus 5X Original Android Development] mohammed510:
Its a matter of preference. I would oc my desktop CPU simply because I like oc.ing.
[Nexus 5X Original Android Development] skulldreamz:
Could anybody that has ran a benchmark let me now if this score is good, bad, it about average please. I never run benchmarks but decided to for my first time, thanks.
[Nexus 5X Original Android Development] mohammed510:
It's very good but, if you update to the latest 6.0.5 I guess. Your score will be much lower. Its like they won't allow you to beat any SD810 CPU. I used to get 104k on a f2fs formated data and cache. However, with the latest update, it went down to 75k despite being on the same ROM and kernel.

I don't trust benchmarks anymore.... The whole benchmark thing is a game..
[Nexus 5X Original Android Development] cgibbons51:
I was wondering what kernal tweaker you guys recommend. I'm using trickster and for some reason the kernal keeps getting stuck clocked at 960mhz even if I change it. Great kernal just getting a little slow at times because that
[Nexus 5X Original Android Development] domicq:
Is there chance of f2fs on stock rom?
[Nexus 5X Original Android Development] Topse:
With this kernel and TWRP recovery you are able to do.

Look at op.

I changed my cache and data to f2fs (with custom ROM). But I think this work with stock to.

And don't forget this wipe your data partition ...

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 5X Original Android Development] jollaman999:
[bullhead-v6.0_beta]

== Kernel ==

- kexec hardboot support

== AIO ==

- MultiROM Support!! (Experimental)

- Included in Aroma Installer

- You can't set lock security settings in secondary ROMs (For prevent conflict with primary rom)

- When you select one of secondary ROM it will stop at Google logo. Just press the power button for a long time for reset.

Then secondary Rom will boot!

- It seems adbd not working properly in recovery and MultiROM selection screen.

- My kernel will not install in secondary roms. There will be no changes if you try installation. Same with some other kernels.

- If you use f2fs in main rom, you should make your own boot.img for secondary ROMs in flashable zip to use f2fs.

== Recovery ==

- MultiROM TWRP v3.0.0-0

- jolla-kernel_bullhead-v6.0_beta applied
[Nexus 5X Original Android Development] roofrider:
[MENTION=5996255]jollaman999[/MENTION] will you be making a standalone release of MultiROM and the modified TWRP?

-edit-

I just installed the modified recovery alone via your Aroma installer, cheers! But i didn't see an option to install MultiROM though.
[Nexus 5X Original Android Development] jollaman999:
Did you installed with v6.0_beta? It will located at main screen. :confused:

No plans for standalone. Cause of kernel and installation methods.
[Nexus 5X Original Android Development] roofrider:
Yup I installed the beta, but only installed the recovery since I was on elementalx kernel. I thought the recovery, multirom, and the kernel can be installed separately, but looks like the kernel and multirom are a package. I'll install the kernel later today and report.
[Nexus 5X Original Android Development] jollaman999:
Yes, you're right. Thanks!
[Nexus 5X Original Android Development] skulldreamz:
Again awesome development and hard work from [MENTION=5996255]jollaman999[/MENTION] Thanks so much for all that you do for this phone!! ? Well be trying this asap!!!
[Nexus 5X Original Android Development] reylafo:
"same question"

Bump. Thanks.
[Nexus 5X Original Android Development] Grumbar_9:
Multirom & AndroidO DP-3

Is there a possibility to install AndroidO as secondary ROM with Multirom?

For now i'm recive a massege like "no Diggest file found", Erorr type 6. Is it absolutely incompatible with this feature and shall we only wait for updates?
[Nexus 5X Original Android Development] edoardotavecchio:
Should jolla's TWRP work on android O DP3?
[Nexus 5X Original Android Development] buffer overflow:
In aroma installer have options to choose between 7.1 and O. So, in this case... ;)
[Nexus 5X Original Android Development] bbs3223474:
Yeah, the problem is, even I turn off the thermal detector (or anything like that matters the hotplug) or turn the threshold up to 80 ℃ by Kernel Adiutor, nothing has changed but keeping low performance. That's what I'm not satisfied with, really.

I can understand you guys are willing to sacrifice some performance to gain better battery life, but I just want it to be more balanced.
[Nexus 5X Original Android Development] zaffar.mughal:
I'm also facing the exact same problem, tried to ask but no answer. so i have tried to swop the roms and it worked, although i have to do it twice or thrice, but it worked. Dont know what is the problem.

So, if you want to have secondary rom, you need to install the secondary rom and let it run, setup will not be completed and it will restart. Now, go to recovery and swop the roms(secondary to primary) and then let the setup complete. this will work. atleast it worked for me...

Regards,
[Nexus 5X Original Android Development] jollaman999:
[bullhead-v26.0]

[bullhead-v26.0]

August! Restore balanced performance! More upstreams!

== Kernel ==

>> Common <<

- Applied Google August security patches

- Applied Google Android O Preview 4 patches

- sdcardfs: Applied lastest patches from Google android-3.10

- f2fs: Merged f2fs-stable-4.13-rc2-4.9 upstream patches

- power: bcl: Remove useless __ref and __refdata flags

- msm_thermal: Increase 'temp_little_off_threshold' (Restore balanced performance.)

- fs/exec: Fix the crash in su vulnerability patch (from Lineage OS)

- clk: qcom: clock-pll: Applied fixes patched by myfluxi

- scsi: sg, af_key, perf/core: Applied some upstream patches from Google android-3.10

- arm64: avoid overflow in PAGE_OFFSET (Linux master upstream)

- s2w, dt2w: Add vibration on/off option

- ext4: Applied some overflow and error fixes from Linux master upstream

- qcacld-2.0(wlan driver): Update to LA.BF64.1.2.3_rb1.15

== AIO ==

- multirom: ui: Prevent interaction with booting final card

- multirom: trampoline: Fully handle /proc/cmdline outputs

- Updater: Update libraries

- Updater: Change the digest from md5 to sha256

- Updater: Version up to v1.10

- MultiROMMgr: Update libraries

- MultiROMMgr: Change the digest from md5 to sha256

- aroma: s2w, dt2w: Add vibration on/off option

== Recovery ==

- Built with lastest LineageOS sources

- Appiled jolla-kernel_bullhead_II-v26.0

* Supports Android 7.x.x and Android O.

* If USB Keyboard application stopped at "Opening /dev/hidg0 and /dev/hidg1" message!

Check root permission and download "SELinuxModeChanger_MOD" from Server Folder.

http://tp.jollaman999.com/jolla-kernel_AIO-bullhead/SELinuxModeChanger_MOD/

Change SELinux to Permissive then re-open USB Keyboard.

Restore SELinux to Enforce after used USB Keyboard for security.

* In my test, Bluetooth's aptX codec is only worked with LineageOS. (Android O already has this feature in developer options.)
[Nexus 5X Original Android Development] BreckZeBoulay:
[MENTION=5996255]jollaman999[/MENTION]

First many thx to you to port MultiRom on N5X ! :good:

Coming from N5, I was worried not to have MR on N5X.

May be I don't see the option but....

Is it possible to mod your multirom recovery to have the possibility not use a kernel with kexec patch ?
[Nexus 5X Original Android Development] zurik:
The 26 should work with OPR6. right?
[Nexus 5X Original Android Development] jugoslavpetrovic:
I believe so, but extract boot.img from the zip of your rom in case of the worse with wrong kernel you cant boot, then just get back to twrp and flash the boot.img as image to boot partition and you are cool.
[Nexus 5X Original Android Development] zurik:
I will wait until next update. Thank for your answer.
[Nexus 5X Original Android Development] Xeust:
Both are the same kernel version so yes it should work and is working fine on mine :)
[Nexus 5X Original Android Development] zurik:
Thanks for your answer!
[Nexus 5X Original Android Development] C.H.T.J.:
Great Kernel Great WORK! THANK YOU!
[Nexus 5X Original Android Development] C.H.T.J.:
Can someone confirm Dt2w or S2w is working on Android O?
[Nexus 5X Original Android Development] :
Hello,

What are the best governor and io scheduler for battery ?
[Nexus 5X Original Android Development] buffer overflow:
Interactive and Noop or Zen.
[Nexus 5X Original Android Development] jugoslavpetrovic:
Noop 128kb, and consider also conservative cpu governor to gain a bit of battery.
[Nexus 5X Original Android Development] yikestone:
Could you pls modify final boot.img to use 4 cores (https://xdaforums.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199). I want to use it on my boot looped Nexus 5X. I am running stock Android Oreo, with modified kernel from the link given..
[Nexus 5X Original Android Development] Doomkopf:
I don't think so. I think the row-scheduler is the best for normal use. As the name says (read over write), the scheduler focusses on the read- speed, which makes the overall experience very smooth and faster, especially the boot. I also think 512kb as the read-ahead-value is more efficient, because the value garatuees more speed without being too big.
[Nexus 5X Original Android Development] jugoslavpetrovic:
Guy asked for more battery oriented choice.
[Nexus 5X Original Android Development] :
I finally choosed zen ans 2048kb readahead.

And set Big cores off.

I also choosed conservative that I tweaked for more battery and locked frequencies at 960mhz.

As io scheduler use very less battery than cpu I prefered to lower cpu and choose the best io scheduler (not deadline as it's too much).
[Nexus 5X Original Android Development] jugoslavpetrovic:
My setup lately includes zen/128kb, little cores some of performance oriented and big conservative, thermal threshold 42 - both on. So my idea is to be responsive at wakeup but still with big cores slower cuz I don't play games. I like how it keeps cooler device with decent performance.
[Nexus 5X Original Android Development] Nicktheprofessor:
You now have a device as responsive and useful as a $50 phone.

What is the point of crippling your performance when in the end the same work will have to get done through less efficient means meaning that you'll get the same useful time out of your battery but now you'll spend more time waiting for your device to catch up?

The IO scheduler doesn't really matter, NOOP is better in almost all cases since it doesn't involve any scheduling at all, it is basically a dumb passthrough that doesn't act like a scheduler at all.

Read ahead should be set at around 512, less will decrease performance but more won't really increase performance much at all.

In the end, all these tweaks will give you longer screen on time but you'll spend most of that time waiting for your phone to catch up so the productive time will be less and the annoyances a great deal more.

When I developed for another phone I specifically wrote a manager that would race to idle, that is, it would boost everything to accomplish the task as fast as possible so it could return to idle as swift as possible, this was as power efficient as leveling and hotplugging but meant that the device was extremely responsive at all times. If you have to wait 15 seconds for a task that should take half a second then those 15 seconds will cost your device more power than the half a second of complete burst of all cpu's.

Don't mess too much with what is known good, you'll only end up with a slower and less power efficient device in the end.

---------- Post added at 01:54 AM ---------- Previous post was at 01:48 AM ----------

How do you think this will help? Using the big cores to perform the task faster means that less power is used in the end since it'll take the small cores longer and returning to an idle power saving mode will take longer too. Meanwhile, while you wait for the task to complete, your screen is still on and all you'll really accomplish is a slower device.

Leave all cores operating as they should at all times, the faster the job is done the faster they can return to idle and power saving mode.

The only thing that you have a point on here is heat build up but you don't play games so even if you used performance on both clusters you should never see it go over 40C.
[Nexus 5X Original Android Development] :
I will agree with you if I was a little boy playing or if we were at the time of Android 4 but today the Android OS is so well optimized that this config is enough to be as smooth as the stock but providing a day of use.

And a 50 dollars phone is not as well optimized on some points as our device.

Trust me that if I were losing any performances I will not do this I'm not do crazy.

I'm usinng Lspeed too to accomplish that.

Finally for heavy tasks like using camera I had created profiles with tasker to set the cpu frequencies higher for this task.

So I get 6 hours of sot instead of 3 on wifi and 4 instead of 2 in 4G. That's pretty useful for me and as I said I don't lose "any" performances my phone is smooth as hell anyway...
[Nexus 5X Original Android Development] jugoslavpetrovic:
I hardly saw temps below 40 to be honest. But I will try your suggestion. It makes sense.
[Nexus 5X Original Android Development] Eugene729:
Hi, could anyone port a version of the multirom twrp 3.1.1.0 to work on only 4 cores? I really need one badly. I really appreciate it.
[Nexus 5X Original Android Development] Nicktheprofessor:
*sigh* The Android distribution (which is like any other Linux distribution but meant for embedded devices) is not optimized in the least and with every version it gets worse.

This phone would FLY on KitKat and have a much better battery life so this isn't it.

It seems to me that you don't have a clue what you are doing but are looking for optimizations through tools that don't actually do anything at all. L speed won't actually do anything useful on this device at all.

You spent more time making your phone work properly than you have done using it and for what? A phone that is less responsive over all where you are wasting time waiting for tasks? What use is increased screen on time if all of it and then some is wasted on waiting?

It's great that you sit there waiting for 3 out of six hours since everything takes twice as long to finish but really, other than bragging about it, what use is it?
[Nexus 5X Original Android Development] BS86:
It would totally NOT.

Kitkat misses a ton of battery optimizations that we now have. The 2-step doze alone is a huge battery saver. If you would throw KitKat on a N5X, it would rock performance wise, that is true. But it would suck the 2700mAh battery empty in 0.5 hour SOT or 6 hours in idle.

Kitkat phones rarely had 5.2" IPS screens with 1920x1080 resolution, and they also had no 6 core powerhouse to be kept alive. Also, LTE was not used on KitKat devices and they also missed NFC most of the time. 5GHz WiFi was also not there on most KitKat devices. Those things all consume a lot more power than the components of typical KitKat phones did.

Still we can get 1-3 days of battery life and 2-3 hours SOT easily now on stock ROMs, without having much larger batteries than we had back then.

I remember that back on KitKat, I was happy that I could run 1 day with 2 hours SOT on my 1500mAh LG dualcore phone with 4" screen and 840x600 resolution, which required a really well modified custom kernel and custom rom.

Stock LG crapware back then meant a maximum of 1 hour SOT if i wanted to have the phone run the whole day without recharging.
[Nexus 5X Original Android Development] Nicktheprofessor:
You do realize that it takes HOURS for doze to kick in? You do realize that normal sleep was just as power efficient since drivers were specifically configured to go to sleep back then?

Sleep on Linux has been around since 1992 and KitKat kernels used earlysuspend to make use of it which is why it worked just fine which is why power hungry devices like the LG 4X HD had pretty good battery life and better battery life on sleep than this device does even though it's more power efficient hardware wise.

One thing users don't get is that we used to have earlysuspend, now the newest suspenders are EAS based and we still have HMP (which might change, I'm doing a full kernel upgrade to 3.18 and we can use most newer drivers kernel side so we just have to build a vendor image using them vendor side), we are using the worst of all worlds. We have devices that do not conform to EAS and that won't go to sleep for hours using doze and we don't have the suspend sleep states of old either.

Stock LG is far better than Samsung or OnePlus AND it's dealt with by Google, you have no idea what so ever on any of these things.

Please, stop talking, you've made enough of a fool out of yourself for one day.
[Nexus 5X Original Android Development] BS86:
ROFL

We now have phones that's components suck 4 times the energy then on KitKat times.

Still the batteries are only 0.2 times bigger AND we still get better battery life due to a lot better energy management.

If the phone batteries would be 4 times as big as back then, too (which would mean 6000mAh) - we would have Nougat and Oreo phones that last weeks on idle and have 10+ hours of SOT without modifications needed.

THAT is the point that YOU don't get.
[Nexus 5X Original Android Development] Nicktheprofessor:
What does that have to do with sleepstates and how KitKat would be better and more power efficient than Nougat or Oreo?

Also, you're wrong, apparently you don't get hardware as well as software. Older chipsets were more power hungry because of the production technique which would require more current.

You just can't stop, can you? You are determined to show your ignorance on all things.

The battery on the 4X HD and generally any phone with similar performance was about 3/4'ths of what we have today, not a SINGLE ONE were 6000mAH, most were 1200-1800mAH.

The point that you don't get is that changing the subject to hardware or to batteries doesn't really help since you don't know jack **** about that either and I do.

The mods frown on me using the proper words to describe your kind so suffice to say this discussion ends here.
[Nexus 5X Original Android Development] BS86:
apparently, you are not even understanding english.

so yeah, no point in further discussing this thing as your last post shows that you seem to understand the opposite of what I write.

Edit: And yeah, good luck in getting Kernel 3.18 booting with the N5X - there already were bigger minds on that and did not succeed.
[Nexus 5X Original Android Development] Nicktheprofessor:
Are you sure you are German, you don't sound reasonable at all. You were wrong about the software and the hardware and about the battry too, they are much larger and holds more mAH today.

So so far all wrong and it's not the first time I've upgraded a kernel to a new version, parts of it with some new code has already been published in another thread.

Thank you for wishing me good luck with this very simple but much time consuming task though, a few tenths of thousands of commits to go and it's done and btw, I've been developing for Linux since 1992 so this isn't really a big thing and not hard at all, but it is time consuming. Ask all of the guys that have upgraded parts of it already how time consuming it is.
[Nexus 5X Original Android Development] BearOfXDA:
So, I'm new to this whole kernel thing. I'm running LOS and was looking for tweaks to improve battery and such, so what would I use to control this kernel?
[Nexus 5X Original Android Development] :
So first thank you for developping our device.

Secondly you are an expert and I'm not so I suppose that you are right on some things but about my setup you are wrong : I have no lags and I can just use my apps more longer (I can send you a video if you don't trust me).

Sure 960mhz is not enough for few tasks like taking pictures and that's why I created profiles for these tasks.

Thanks again for developping Linux since a long time and I don't want to enter in a fight with a more experimented person like you.