yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Original Android Development] Destroyedbeauty:
Is it anyone that ever are going to use 4 different governors at the same time? I can't see any benefits from it, can you? :P
[Xperia Z1 Original Android Development] Androguide.fr:
Sure, I can, you could set battery-friendly governors for the first 2 cores, and performance-oriented governors for the last 2 cores, this way if the hotplug driver does its job propery you get a battery-friendly behavior when idle/browsing the web and more performance when the last 2 cores are online, like when gaming.

This is just an example, but it gives you a lot more control over the cpu's behavior. Only MSM chips allow this, so let's take advantage of it.
[Xperia Z1 Original Android Development] Destroyedbeauty:
Will try it with an intellidemand x2 / intelliactive x2 combo later! :)
[Xperia Z1 Original Android Development] Androguide.fr:
Ok, please report back if you see any improvement ;)

EDIT: I pushed a new update to google play, it allows to set the per-core governors even if the cores are offline, and adds msm_thermal control.
[Xperia Z1 Original Android Development] Destroyedbeauty:
Haha, when it comes to Faux123 related stuff - everything becomes battery friendly :)

Msm_thermal - that is Qualcomms own thermal-crap-driver?
[Xperia Z1 Original Android Development] vnblueberry:
CWM

I tried a search but couldn't find anything - can I reboot to CWM Recovery instead of TWRP?

edit: just saw on the changelog that it's now TWRP ..
[Xperia Z1 Original Android Development] ->---:
You can flash this

http://xdaforums.com/showthread.php?t=2261606

after PimpedKernel so you can choose from 3 different Recoverys. CWM just through reboot with the NDRUtil as part of the Multi-Recovery.

Edit: One suggestion for the CPU Control tab. If I change frequencies the app is directly forcing them into the system. So, if I like to adjust the frequency it is permanently changing the frequency in the system. Wouldn't it be better if there is a SET button, which forces the app to set frequencies? In that case somebody could adjust as often as he likes, and after he has decided, the app can change them. As it is now, you have permanent messages that the frequencies in different system parts are changed and you can not exactly see and use the sliders.
[Xperia Z1 Original Android Development] tospace2006:
I flashed the zip file over CM11 but I'm just stuck on the boot logo... am I doing something wrong? sorry if it's something ovious but I couldn't findthe answer
[Xperia Z1 Original Android Development] Michealtbh:
I had this problem too. Let Cyanogenmod boot once first, then reboot to recovery and flash the kernel
[Xperia Z1 Original Android Development] tospace2006:
Now can't get SIM card to read know a solution?
[Xperia Z1 Original Android Development] vnblueberry:
i had a similar problem

i had to flash back to 136 and it worked fine from there

hope you find an easier option ..
[Xperia Z1 Original Android Development] KWOKSFUNG:
Maybe a noob question but does it work for stock or stock based 4.4 rom?? (Unlock Bootloader ofcoz)
[Xperia Z1 Original Android Development] Poesini:
In the title it says for CM based ROMs so stock isnt CM based
[Xperia Z1 Original Android Development] ->---:
I have the suspicion that, with the latest version, power consumption in standby is a little higher than in former versions. All settings are on. GPU-rendering is forced for 2D. Can somebody verify this? Which setting could be the trigger?
[Xperia Z1 Original Android Development] berimornils:
ART work this kernel?

Отправлено с моего Xperia Z1 через Tapatalk
[Xperia Z1 Original Android Development] Androguide.fr:
Open Pimp My Z1 and make sure you don't have all cores enabled (i.e: "Cores online: 4/4"). If you do, then go to the power management section and disable intelliplug and eco mode, wait like 2 seconds and re-enable intelliplug, then eco mode (in that order) and go back to the CPU Control section to verify it worked.

Also, which governor(s) are you using, etc ?

Forcing GPU rendering is pretty silly if you ask me, a pure waste of battery, especially with such a beast of a GPU that is the adreno 330.

The hw overlays can handle 2d rendering very well, I don't see why you'd need to do that.

This depends on the rom, not on the kernel. It won't prevent using ART, anyway.
[Xperia Z1 Original Android Development] ->---:
The core management worked well. Just 1 active most of the time. I tried to use the preset governors. Core 1 &2 intellidemand, core 3 & 4 intelliactive. But everytime I left the tab CPU Control and reentered it, core 2 was set to intelliactive. I now use the setting one gov 4 all.

I thought I could save energy by forcing GPU for 2D rendering and chopping frequency at 200.

What are the different TCP algorithms do? I cannot figure it out from the wiki descriptions. Is there a better one than the preset one for data transfer?

Edit: Found those documents:

http://innovation.vrt.be/sites/innovatie.vrt.be/files/generated/files/blogs/report_congestion_control.pdf
http://w.naun.org/multimedia/UPress/cc/cc-27.pdf

Depending on these information I will give YEAH a try.
[Xperia Z1 Original Android Development] mnickkk:
Have you ever thought about implementing screen control features (like gamma, white balance etc)? My screen is just awful (that's my opinion after having Galaxy S3 and Nexus 5). I'd love to play with some settings, if you're not going to implement this anytime soon, could you give me a hint where should I look for?
[Xperia Z1 Original Android Development] Androguide.fr:
It's not an easy port at all, and I don't think it'll implemented anytime soon. If you need white balance you're stuck with stock atm (or the screen filter apps on the playstore, but meh).

To simplify greatly, the TCP congestion algorithms could be considered governors for TCP traffic.

They define the strategy to use depending on how many TCP packets are going in and out, and try to avoid congestion as much as possible.

I haven't done much benchmarking, but westwood is known for being a good algorithm for wifi networks. If I do get around to benchmarking the algorithms included in the kernel I'll make sure to post the results.
[Xperia Z1 Original Android Development] ->---:
Thx :good: I read the documents you linked in the first post and also some I googled. After comparing the specs I think YEAH is a good choice. In YEAHs documentation als well as in one of the links I posted, many of the governors you implemented are compared. I am far from understanding all of the stuff but the graphs gave me some points to hold on for my decision.
[Xperia Z1 Original Android Development] _Garry_:
About f2fs:

When I remember correct with CWM its possible to format to f2fs. Why not using CWM instead of TWRP??? Just curios question.

Gesendet von meinem Xperia Z1 mit Tapatalk
[Xperia Z1 Original Android Development] Michealtbh:
Probably because TWRP has more features, a better ui and ux, and is much quicker at backing up and restoring
[Xperia Z1 Original Android Development] _Garry_:
You are right about those features. But what is the main part which makes twrp better then cwm??

IMO ui/ux are gimmicks.

Quicker backups/restore indeed are fine but is it really that important?

Some features are really handy/ useful.

Well with cwm you can use f2fs. And I only know this because my old note2 is running slimkat using f2fs.

No offence or so, I just try to understand the main difference between twrp and cwm.

Gesendet von meinem Xperia Z1 mit Tapatalk
[Xperia Z1 Original Android Development] Androguide.fr:
Both CWM & TWRP can natively support f2fs, as long as you provide them with statically linked f2fs-tools binaries (mkfs.f2fs, e2fs.f2fs, fibmap.f2fs).

I'm working on getting the f2fs support ready, just hang tight, I'll release it as soon as I get it working properly.
[Xperia Z1 Original Android Development] _Garry_:
OK. I'm waiting. Take your time ;)

Gesendet von meinem Xperia Z1 mit Tapatalk
[Xperia Z1 Original Android Development] germsandbugs:
Excellent work, haven't given your rom a try yet (will do soon), but your kernel rocks on cyanogenmod.

Don't like cwm either, (date and time setings keep getting set to 1970,lol!), but Philz is pretty good though, how would one go about to add these when wanted and how does one then bind them to a hardware button? (since i think Cyanogen only does the autoinstall via cwm?).

Does anybody know of a xposed module that let's you select the recovery/hardware button to reboot to/ reboot with?

Keep up the good work mate, would love to see one that works with the stock rom though?

Greets,
[Xperia Z1 Original Android Development] Androguide.fr:
I have close to no experience with recoveries, I don't know how they manage the dual recovery thing at all, maybe ask to NUT in his dual recovery thread if you wanna know more.

I'm experimenting with f2fs atm, couldn't boot successfully with /data and /cache formatted as f2fs right now, it panics and reboots right when the boot would be complete, probably just an fstab flags problem.

It's quite painful to test/debug as it wipes all data on the sdcard (obviously), which causes adb to be disabled, and is quite a pain in the ass to get back to ext4 (couldn't format back to ext4 using TWRP, only CWM managed to handle it).
[Xperia Z1 Original Android Development] germsandbugs:
Found this:

Quote:

Originally Posted by vnblueberry View Post

I tried a search but couldn't find anything - can I reboot to CWM Recovery instead of TWRP?

edit: just saw on the changelog that it's now TWRP ..

You can flash this

HTML Code:

http://xdaforums.com/showthread.php?t=2261606 after PimpedKernel so you can choose from 3 different Recoverys. CWM just through reboot with the NDRUtil as part of the Multi-Recovery.

It installs fine and gives me the desired recovery, only the hardware buttons do not select the proper recovery, NDRUtils does the trick though when rebooting :confused:

Oh well, the life of a flash-a-holic is never dull :D, I'll ask in the NUT thread, cheers
[Xperia Z1 Original Android Development] Androguide.fr:
F2FS Support Incoming

F2FS support is now almost ready for release, it's working properly and I have to say the performance boost is quite impressive :victory:

I have /data and /cache partitions formatted in f2fs as you can see in the screenshots below.

I made those screenshots with a stock CM kernel onto which I added my f2fs port and modified the fstab (I did that in order to avoid any incompatibilities from my other commits), so I'm rebuilding my kernel with those changes, I'll do a quick test to make sure it works as well, and then I'll release the kernel and instructions.

Next step will be to try using f2fs for the /system partition as well.
[Xperia Z1 Original Android Development] _Garry_:
WooooooT.....can't wait to use the new kernel.

Gesendet von meinem Xperia Z1 mit Tapatalk
[Xperia Z1 Original Android Development] Destroyedbeauty:
[MENTION=4752917]Androguide.fr[/MENTION]

1) Is it possible to tune the CPU Boost module tunable files under /sys/module/cpu_boost/ for saving some extra battery or are those totally non-editable. I got some rapid battery drains on latest kernel and though those got something to do with this..? Any advice?

2) In the Intelliplug parameters /sys related folder - there are two files called 'nr_fshift' and 'nr_fshift_hysteresis' with default values of 3 respective 8.. Can Intelliplug also be tuned with changing the parameters of those two? What should I use for each file, higher or lower values? *confused*

EDIT: CPU Input Boost seems to cause the issues, because there was a similiar overheating / battery drain problem on Doomkernel when [MENTION=2784807]DooMLoRD[/MENTION] used the same feature..
[Xperia Z1 Original Android Development] Androguide.fr:
Sure, you could for example lower the boost frequency (input_boost_freq tunable), but cpu boost has been enabled for about 4 or 5 builds I think.
[Xperia Z1 Original Android Development] Androguide.fr:
[EXPERIMENTAL] F2FS-enabled kernel & recovery

Ok guys, so here we are, here is an experimental build with F2FS support for the /data & /cache partitions.

If you want to use it, please follow the instructions below to the letter.

Warnings

A few things to keep in mind before using this F2FS-enabled kernel:

Switching to F2FS will wipe all your user data as well as all the data on your internal storage

You will not be able to use kernels without F2FS support (just reflash the kernel after flashing a nightly), unless you go back to ext4, of course

Instructions

Boot to your current recovery and flash the kernel's zip provided below

Reboot to recovery, you should now be in CWM

Flash the ROM you want to use

Flash the gapps

Re-flash the kernel (the rom will have overwritten it)

Reboot to recovery again

Go to mounts & storage and select "format /data and /data/media (/sdcard)"

Still in mounts & storage, select "format /cache"

Reboot & Enjoy ;)

Going Back to ext4

Download the latest CM nightly

Boot to recovery and flash the nightly

Boot to the stock CM recovery

Go to mounts & storage and select "format /data and /data/media (/sdcard)"

Still in mounts & storage, select "format /cache"

Reboot

Download
[Xperia Z1 Original Android Development] Juzman:
Will Windows PC's still be able to read/write to the phone via USB if formatted as F2FS?
[Xperia Z1 Original Android Development] Destroyedbeauty:
What about tuning Intelliplug in the nr_fshift tunables - lower or higher values?
[Xperia Z1 Original Android Development] Androguide.fr:
I'll verify, but it should, yes.
[Xperia Z1 Original Android Development] Androguide.fr:
Full-Featured Kernel with F2FS

Here is the full Pimped Kernel with F2FS enabled and TWRP recovery with F2FS support.

Same instructions as the previous CM kernel with F2FS, quoted below.

Download
[Xperia Z1 Original Android Development] Kingcool88:
I really love your kernel, but whats the benefits with F2FS vs ext4? Stupid question maybe but...

Will you make 2 versions of the kernel in the future, one with ext4 nad one with F2FS?
[Xperia Z1 Original Android Development] zhuoyang:
I am pretty sure the kernel support both f2fs and ext4
[Xperia Z1 Original Android Development] _Garry_:
F2fs for system too????

Gesendet von meinem Xperia Z1 mit Tapatalk
[Xperia Z1 Original Android Development] Poesini:
Is this new kernel in sync with 4.4 baseband and stuff? Or is this ROM related?
[Xperia Z1 Original Android Development] Androguide.fr:
F2FS is a file system that's built from the ground-up with flash storage in mind (like the eMMC chips & SDCards in our smartphones), as the name implies (Flash Friendly File System).

It provides a huge I/O performance improvement over ext4 (just an example but on nexus 7 the users reported an increase of 3k+ points on Antutu benchmark with the same settings, just by switching from ext4 to f2fs).

This doesn't only make files copy faster, pretty much everything relies on the I/O, so it makes everything snappier.

Of course this is more visible on aging devices like the original nexus 7, as the Z1 is very snappy on ext4 as well.

Yes, I will make both an ext4 & an F2FS versions of the kernel available, or maybe use aroma to let you choose between the two in the same zip.

Not in this build, only /data & /cache are supported.

But I'll add /system soon after some testing to see if it's stable, it's just one line to change in the fstab.

The kernel is in sync with the latest CM kernel. Baseband is a different thing, you can probably update your baseband using flashtool with the latest stock firmware and only ticking the baseband/radio checkbox (don't quote me on that, though).

I've also update intelliactive to the latest faux commits, fixed & enabled VMALLOC_SAVINGS, some RNGD improvements and some bluetooth-related commit.
[Xperia Z1 Original Android Development] Poesini:
I am saying this because I tried the Cyanofire ROM and when I installed your kernel before first boot it wouldnt get signal so I had to flash the entire ROM without anything and it worked so I dont know if its kernel or ROM related (I did flash the latest FTF)
[Xperia Z1 Original Android Development] Androguide.fr:
I don't know about Cyanofire.

I'm running the 26/03 CM nightly with the F2FS kernel and I have data/signal.
[Xperia Z1 Original Android Development] Poesini:
I was talking about Cyanofire because its supposedly based on Omni so I guessed you could know

And speaking of F2FS, how could we benefit just from /data and /cache performance improvements with it (would you say XX % of having the whole ROM with F2FS?), I mean, how much of the whole IO does /data and /cache have to do with

Thanks man :) :victory:
[Xperia Z1 Original Android Development] Androguide.fr:
I'd say about 80% of the I/O operations are done on the /data & /cache partitions.

The improvement we would (and will) get by using F2FS on the /system partition as well is minor compared to the improvement brought by switching the /data partition for example.
[Xperia Z1 Original Android Development] prbassplayer:
This is right. The main bulk of I/O is done on /data and cache, system rarely gets written to and only read. That being said there wouldn't be any negatives to using it on system either. My question is, is the performance really that much better? I'm talking about benchmarks not the "it feels smoother". I've read so many contradicting reports and very few benchmarks. I'd also like to know how it fairs on a fresh system (fully wiped new) vs one that has a load of data and has been in use for a while.
[Xperia Z1 Original Android Development] Androguide.fr:
I'll be doing thorough before/after benchmarking very soon with all 3 partitions formatted as f2fs.

Most reports we see are from freshly wiped systems, so as you said it could be interesting to see how/if the performance sustains the time and cluttering, I'll try to do the same benchmarks with the same protocol a month after the first round to see how the results compare.

If you have benchmark suggestions let me know. I'm currently thinking using 0xBenchmark, CF-Bench and Antutu.
[Xperia Z1 Original Android Development] _Garry_:
Here is an old benchmark f2fs vs ext4 and other formats:

http://www.phoronix.com/scan.php?page=article&item=linux_f2fs_benchmarks&num=1

Keep in mind that f2fs is still not there where it should be. Ex the f2fs got a new "upgrade" for better write/read performance - when I'm not wrong, the update was made in the beginning of this year!?!

Gesendet von meinem Xperia Z1 mit Tapatalk
[Xperia Z1 Original Android Development] ->---:
Is a conversion like in the description

http://www.howtoforge.com/how-to-convert-an-ext3-ext4-root-file-system-to-btrfs-on-ubuntu-12.10-p2

also possible for ext4 to f2fs? Maybe with an windows based program, in a form like Wugs Nexus Toolkit? I think the acceptance of a conversion would be much higher, and if f2fs is not the burner it would be easier to return to ext4 without loosing all data, settings and so on.
[Xperia Z1 Original Android Development] lowrider_05:
it doesen´t work for me at all, i tried with the instrucions provided exactly step by step and with cyanogen nightly cm-11-20140326-NIGHTLY-honami.zip and it does not work is there something else i could try ?

it does not work with the pimped version for me but with the cm based kernel it works on first try !?

edit: and after that the pimped kernel does work (Strange)
[Xperia Z1 Original Android Development] Androguide.fr:
This is pretty much exactly what the recovery does behind the scenes.

I could make the process easier by formatting the partitions in the kernel's updater-script, but that wouldn't work as the recovery needs to be rebooted after the kernel has been flashed, in order to get into the f2fs-enabled recovery (unless you already have an f2fs-enabled recovery at the beginning of the process).

Best I can do is provide a flashable zip that will format the partitions to f2fs (and another one that formats back to ext4), which you'll need to flash after flashing the kernel and rebooting the recovery.

I honestly don't think a program requiring a pc (let alone a windows install) would see a better acceptance rate than a method using the on-device recovery.

EDIT: this gave me an idea, maybe I can pack the f2fs-tools binaries in my flashable zip, copy those to the recovery's /sbin folder and format right away, but I need to test if that works.
[Xperia Z1 Original Android Development] Androguide.fr:
Thanks for reporting, it seems TWRP is falling-back to using rm -f instead mkfs to format /cache, but CWM handles it properly, that's probably why you had this scenario.

I'll either provide a flashable zip that formats the partitions for you or switch back to CWM next build.
[Xperia Z1 Original Android Development] Poesini:
Im trying ¨mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/system¨ and it succeeds, but when I try to sideload Omni 3/15 (I removed the format and mount lines as ext4 from the updater-script) it fails at symlinking, to see if I can install with /system as f2fs too...

Am I missing something here?

PD: I also see it is make_ext4fs /cache

Edit: fixed it by adding doing ¨mkfs.f2fs -l system /dev/block/platform/msm_sdcc.1/by-name/system¨ , but it hangs at kernel logo :(
[Xperia Z1 Original Android Development] Androguide.fr:
You won't be able to boot with /system formatted with f2fs unless the fstab.qcom specifies the /system partition should be f2fs.

You'll need to either wait for next build or unpack the boot.img, change the fstab.qcom's /system line (basically just replace "ext4" with "f2fs" and replace the mount flags with the ones used in the /data line) and repack it.

About the symlinking, it's probably just because you removed the mount lines instead of mounting with f2fs instead of ext4, the partition isn't mounted so the recovery complains it can't symlink. Just a guess.
[Xperia Z1 Original Android Development] Poesini:
I failed to repack the boot.img :( it just gives me a different filesize... Maybe I am using the wrong tools?
[Xperia Z1 Original Android Development] Androguide.fr:
F2FS vs EXT4 benchmarks

I published my F2FS vs EXT4 benchmark results, and the results show pretty clearly that F2FS provides better performance than ext4 in most cases/scenarios.

I'll re-run the same benchmarks in the same setup with /system formatted as f2fs as well to see how it plays out on the numbers.

And as suggested by [MENTION=3877985]prbassplayer[/MENTION], I'll re-run those tests about a month from now to see if the performance has significantly degraded or not.

You can check-out the results in detail in the dedicated thread: http://xdaforums.com/showthread.php?p=51433509
[Xperia Z1 Original Android Development] _Garry_:
When can might you be read to give us a "stable" f2fs2 kernel incl system partition?
[Xperia Z1 Original Android Development] YamazakiRobert:
your kernel support cm performace profiles?

thamks for your hard work
[Xperia Z1 Original Android Development] Androguide.fr:
Soon enough.

Yes it does, but I haven't fine-tuned the profiles to use the kernel features, so you'll basically have the same profiles as on the CM kernel.

I recommend you use the preset profiles in my Pimp My Z1 app instead.

CPU Overclock might be coming soon, I think I have identified a way to implement it on the "new" dts-based driver (the one CM kernels now use as opposed to stock kernels)
[Xperia Z1 Original Android Development] prbassplayer:
Not just cm. Sony Xperia z2 source doesn't seem to have appropriate acpuclock for the SoC. Think this is just the direction qcom soc will move. I've only managed to replace the 2.2ghz step with 2.3ghz lol
[Xperia Z1 Original Android Development] Androguide.fr:
On the cpuclock-krait-8974.c / msm8974.dtsi combo ?

I was thinking of forcing the PVS speed bin to be set to 1 (*speed variable in the get_krait_bin_format_b function), so that it picks-up the table with 2.26GHz instead of the default 2.15GHz table.

But if you already have CPU OC implemented in your Slim kernel then I'll just cherry-pick it^^