yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Original Android Development] prbassplayer:
It's not merged, I just modified the msm8974.dtsi. But somewhere else seems to limit the amount of clock steps possible with a defined gap between them, I didn't continue exploring (might after the 4.4 merge comes in). The change is on our gerrit if your interested.
[Xperia Z1 Original Android Development] husky69:
Does this kernel work with SlimKat now?

I know it didn't some time ago, but maybe it changed since?
[Xperia Z1 Original Android Development] prbassplayer:
I honestly don't know, I haven't flashed your kernel since debugging the wifi problem. I assume so as people stopped complaining about it on my thread, though that could just mean they opted for CM. I'll give it a try some time tonight
[Xperia Z1 Original Android Development] 3x3cUt0r:
It does, but the F2FS version bootloops.
[Xperia Z1 Original Android Development] prbassplayer:
I haven't looked in the zip, but possibly because I don't have the f2fs libs in the rom, so recovery probably has a fit trying to format (just a guess) I'm going to start messing with f2fs soon, but in all honesty the 4.4 merge killed my motivation lol. Need to do some rework on slim caf side, probably means a new kernel. Right now Restarting smdk4412 kernel from fresh source, try to debug some problems smdk4210 devices are having.
[Xperia Z1 Original Android Development] YamazakiRobert:
the cm team have pushed some commits to fis SoD

http://review.cyanogenmod.org/#/c/61777/
[Xperia Z1 Original Android Development] _Garry_:
Is trwp showing the format as making it to ext4?

I tried to get slimkat running on it, but the formating screen irritates me, dunno if it now realy f2fs or ext4.

Gesendet von meinem Xperia Z1 mit Tapatalk
[Xperia Z1 Original Android Development] Juzman:
I don't have any SoD with latest SlimKat and Pimped Kernel. Runs smooth. :)
[Xperia Z1 Original Android Development] LLars_PL:
So as i understand its only for 4.4x cm based roms yes?

What about stock based 4.4.2 rom??

Would love your kernel but i don`t like cyanogen mod.

-Sorry if this kind of question was already asked

Thanks
[Xperia Z1 Original Android Development] gallardo5:
It was asked. It's not compatible with stock based ROMS;) aosp kernels doesnt work with sony based roms
[Xperia Z1 Original Android Development] LLars_PL:
Oh Thats sad to me.. Thanx for the info.

Wysłane z mojego C6903 przy użyciu Tapatalka
[Xperia Z1 Original Android Development] zhuoyang:
[MENTION=4752917]Androguide.fr[/MENTION]

I know I am asking too much, but can you compile a kernel with F2FS and other features for stock rom?
[Xperia Z1 Original Android Development] Destroyedbeauty:
I think he said no on this because it would require to much work to get every custom kernel module / addon to fully work with satisfying results..
[Xperia Z1 Original Android Development] rdejager:
I also noticed that and then I noticed the rom does not boot at all. When I manually format the cache and userdata part within adb with a command I found a page or 2 back. It booots just fine
[Xperia Z1 Original Android Development] _Garry_:
My tries ended at the bootanimation.

Could be because I tried to format the cache/userdata using the update-script from the start. I guess I made a mistake in the format/mount part.

Trying to find an other way so setup ROM.

My goal:

Switch boot.IMG

Change/switch update-script

Place on phone and flash.

I'm new to trwp, so I'm cursed to make mistakes in the beginning of learning.

Gesendet von meinem Xperia Z1 mit Tapatalk
[Xperia Z1 Original Android Development] Ashray_Vk:
I followed the instructions too but then I'm stuck at boot animation. Any help ?

Edit : The experimental kernel is what I'm talking about
[Xperia Z1 Original Android Development] Androguide.fr:
CPU OC up to 2.26GHz is now implemented, will be included next build (most likely later today, in both ext4 & f2fs versions).

This isn't actually OC per-se as it didn't add a higher frequency step to the current table, but instead it's a workaround which forces the CPU to use the frequency table designed for higher-binned S800 CPUs (the one used in S800 devices that come clocked at 2.3GHz stock).

[MENTION=3877985]prbassplayer[/MENTION] here is my commit if that's something you're interested in: https://github.com/PimpedKernel/and...mmit/39833a3cbe5afdaedbdbbebfcd61a40bdbc813e7

EDIT: I'm going to try and force the *pvs variable too, as higher pvs tables require less voltage for each step.

Might not be stable for everyone passed a point, though, depending on your actual CPU binning level.
[Xperia Z1 Original Android Development] Androguide.fr:
Now that with the 4.4 sources the stock wlan drivers work I might fork DoomKernel and try to add F2FS and some other features (sending pull-requests back to [MENTION=2784807]DooMLoRD[/MENTION] if the features work properly, of course).

I wanted to give stock kitkat a try, so that could be a good reason to do so, but I can't keep switching between CM & Stock to maintain both a Stock-based & a CM-based kernel, I only have one C6903 and it's my only phone.
[Xperia Z1 Original Android Development] :
Did I read stock kitkat? :D
[Xperia Z1 Original Android Development] prbassplayer:
Elegant solution. You got to be careful about forcing a bin voltage table for all. On mako for example lowering the voltage to the next best one would almost always render 70% of the users with that bin to constant reboots or massive instabilities. It would be wiser to implement a voltage adjuster, though that is annoyingly difficult since z1 are among the "first" with this new clock setup source wise. At any rate maybe (hopefully) I'm wrong lol

Edit: Imoseyon is working on a CM hlte kernel and he seems to have undervoltage tunable on it. Maybe something to look at and possibly port in the future https://github.com/imoseyon/leanKernel-note3/commit/e71536389e268d4851002678114b527e29320b14 . I might try this later tonight see how it fairs.
[Xperia Z1 Original Android Development] Androguide.fr:
Yeah, a sysfs interface for voltage control would be awesome but porting that to the new cpu freq sources seems out of reach for my poor C knowledge.

Plus it's the kind of thing where an error could easily fry your device^^

I'm gonna experiment with forcing the pvs bin to 3 or 4 with the speed1 table on my device, see how stable it is.

I remember that I checked my actual pvs binning a while back and I got quite lucky.

I can't verify now on CM because for some reason running dumpstate | grep pvs reboots the device and spits nothing out, but if I remember correctly I have a 6 :victory:.

I think until an 'actual' kernel dev implements a userspace-configurable voltage control on this setup, I'm left with either providing several builds with different pvs bin levels set for users to test and find which one works for them, or trying to revert back to acpuclock, which is probably doable given the CM kernel used to use acpuclock at the beginning, but this seems pointless to me.

EDIT: saw your edit, amazing news, I'll give it a try too.
[Xperia Z1 Original Android Development] prbassplayer:
Well it works lol. I undervolted by 50mV across the board and my device rebooted after a few min. Seems fine with -25mV though. Course km using your oc commit so need to compare voltage tables see the difference. But it does seem to work.

Edit: Ok So using speed1 vs speed 2 (without modifying it) means the device will be undervolted by default by ~ 25mV, which would explain why undervolting -50mV would cause instability since I'd be undervolting by -75mV by sony's standard. So careful with that.
[Xperia Z1 Original Android Development] moritz31:
Hey,

i noticed that the On-Time is very great 4h screen running time with my navigon app :)

but other way arround the standby time is bad :/ had 50% after 8hours with only 30min display runtime :(

is that normal ?
[Xperia Z1 Original Android Development] CappyT:
[MENTION=4752917]Androguide.fr[/MENTION] here is a kernel for stock 4.4.2 with tap2wake for our z1... Can this be ported?

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

Inviato dal mio Xperia Z1 utilizzando Tapatalk
[Xperia Z1 Original Android Development] prbassplayer:
Possibly, might need a little cleaning but touch driver bits should be mostly the same. Between stock and aosp. But this is from a very quick peek
[Xperia Z1 Original Android Development] Androguide.fr:
Already cherry-picked ;) https://github.com/PimpedKernel/android_kernel_sony_msm8974/commits/pimped-kernel

All the patches mostly apply without conflicts, or just blank-line conflicts. I'm rebuilding to test right now.

EDIT: it does work properly, props to [MENTION=2011359]MohammadAG[/MENTION]
[Xperia Z1 Original Android Development] lowrider_05:
can´t wait to have this feature, thanks for all your work and this great kernel :good:
[Xperia Z1 Original Android Development] Ashray_Vk:
tap to wake v1.1 is out, fixes few problems, [MENTION=4752917]Androguide.fr[/MENTION] , make sure the new version's fixes are included when you release the new kernel :)

Waiting for the new release anyway! :)
[Xperia Z1 Original Android Development] Androguide.fr:
I picked the latest commits, don't worry about that.
[Xperia Z1 Original Android Development] prbassplayer:
How is the battery life? Wakelock I mean whats staying awake and for how long. Touch to wake type of things always bother me on implementation lol. Won't be able to mess with it till tonight.
[Xperia Z1 Original Android Development] Androguide.fr:
2014-03-30 Build

Here's the shiny new build with some major new features:

Changelog

Downloads

Instructions for switching to F2FS
[Xperia Z1 Original Android Development] Androguide.fr:
Well I can't really report about this now, it's too soon and I've been testing with my device hooked-up to adb.

But I don't think it will use more than maybe 1 or 2 percents battery overall, a good part of the implementation was already in the driver, there is no use of wakelocks.

To quote MohammadAG: "The touch sensor runs in LPM doze mode, so it doesn't guzzle battery".

I guess we're pretty close to the Xperia Z2 implementation on that one.
[Xperia Z1 Original Android Development] dbolivar:
[MENTION=4752917]Androguide.fr[/MENTION] , first I'd like to publicly thank you for replying my PM about a week ago, regarding porting your kernel to the ZU, with some important tips about kernel compilation - indeed, building it inside the CM11 tree did the trick. :) And of course, thanks and congrats for this amazing kernel!

Well, with that said, I could successfully port SlimKat's kernel to the ZU, but your Pimped Kernel always bootloops right after the Sony logo (can't even get to recovery). So I'd like to ask you:

1) Which branch on your Github should I use? I see that the "pimped-kernel" branch has the latest experimental features, so I'm wondering if there is a "stable" branch I could use?

2) There are 2 defconfigs with Pimped Kernel options: cm_rhine_honami_defconfig (older) and pimped_rhine_honami_defconfig (newer, including latest experimental features). Should I always use the pimped defconfig, or is it only for experimental features?

3) Is it necessary to compile your kernel using your CM11 repos in your Github? I see there could be slight modifications over the stock CM11 (e.g. android_device_sony_rhine-common).

Thanks again!!!
[Xperia Z1 Original Android Development] Androguide.fr:
No problem, glad to hear you made progress on that.

To answer point by point:

You should always use the pimped-kernel branch. It indeed has the latest features, but at least you can be sure it builds and boots properly on the Z1. Other branches are either outdated or are topic-related (i.e: the showp_mpdecision branch holds the commits for showp1984's mpdecision)

You should of course use neither of these defconfigs if you are building for the Z Ultra. You need to add the specific flags in pimped_rhine_honami_row_defconfig to a copy of your device's CM defconfig, say pimped_rhine_togari_row_defconfig.

All the flags for the specific kernel features are at the beginning of the pimped_rhine_honami_row_defconfig, and more or less ordered by category. You'll just need to copy those over and make sure to remove any duplicates from already existing flags (for example for the governors, I/O schedules, etc..).

Then make sure you add/modify the following line in the togari device-tree's BoardConfig.mk:

TARGET_KERNEL_CONFIG := pimped_rhine_togari_row_defconfig

And if you're not using my rhine-common repo (see next point), modify the following line in rhine-common's custombootimg.mk

[COLOR="DarkRed"]- SOMC_BOARD = $(shell echo $(TARGET_KERNEL_CONFIG) | sed -e "s/cm_//" | sed -e "s/_defconfig//")[/COLOR]
[COLOR="Olive"]+ SOMC_BOARD = $(shell echo $(TARGET_KERNEL_CONFIG) | sed -e "s/pimped_//" | sed -e "s/_defconfig//")[/COLOR]

It's necessary to use my rhine-common repo only if you're planning on using either TWRP or the F2FS support or both.
[Xperia Z1 Original Android Development] ilia1985:
Hi first off thank u for your awesome work... Quick question how long does it take to format f2fs caches? I flashed f2fs-cache.zip after flashing your f2fs kernel and rebooting recovery on latest carbon rom... Bun in twrp right after flashing f2fs-cache.zip it just keeps on saying formatting cache...
[Xperia Z1 Original Android Development] Androguide.fr:
It shouldn't take more than a second, that's weird.

Did you reboot to see if it booted properly or not ?

What you can do otherwise is to flash this previous F2FS build which includes CWM, reboot recovery to be in CWM, then go to mounts & storage -> format /cache.

Then just reflash the latest build and reboot.
[Xperia Z1 Original Android Development] Kingcool88:
Running latest kernel now with DT2W feature, and its working like a charm!

Tnx alot for all the time you spend on making this kernel amazing!

Edit: seems that my phone doesnt get into deep sleep after installing the kernel, is it because of DT2W feature?

Edit 2:

It took a while but at last it went into deep sleep, BUT then DT2W didnt work. I had to use the power button!
[Xperia Z1 Original Android Development] Androguide.fr:
This seems to be a known issue in MohammadAG's thread as well, don't worry it will probably be fixed soon.

I'll include DooMLoRD's fastcharge port in the kernel next build.
[Xperia Z1 Original Android Development] Poesini:
I don't like DT2W, how can I disable it?
[Xperia Z1 Original Android Development] Androguide.fr:
Either wait for the PimpMyZ1 update or in terminal:

echo 0 > /sys/devices/virtual/input/clearpad/wakeup_gesture
[Xperia Z1 Original Android Development] Androguide.fr:
New build with fast charge

Yet another build, the only change is I added fast charge (thanks to [MENTION=2784807]DooMLoRD[/MENTION] for the port).

An update to Pimp My Z1 has been pushed which adds dt2wake control & fast charge control.

Please READ THE WARNING in the app about fast charge before setting the wrong amperage on the wrong charger/usb port.

Download
[Xperia Z1 Original Android Development] Juzman:
Great work on the kernel mate. I'm thinking of swapping to F2FS but don't want to have to reinstall everything from /data. Ah well, ext4 is still great!
[Xperia Z1 Original Android Development] ilia1985:
I tried it but after flashing older f2fs kernel get cache mount error in cwm after formating cache... Then after i flash new kernel reboot recovery and try to format data twrp goes all crazy with screen blinking between different menus...
[Xperia Z1 Original Android Development] gallardo5:
I flashed latest cyanogenmod, then old kernel, formated cache, then with the latest one formated data but after boot up phone says that deencrypting data failed and I need to wipe my data. It happens everytime, and when I try to wipe data it just wipes for loooong time and doesnt work
[Xperia Z1 Original Android Development] ilia1985:
+1
[Xperia Z1 Original Android Development] Poesini:
I'm going to post what I did when I had my stuff formatted as ext4 (before going to f2fs)

Go to recovery (TWRP) and then go to command input:

cd /dev/block/platform/msm_sdcc.1/by-name/

mkfs.f2fs -l cache cache

mkfs.f2fs -l data userdata

Now set in advanced settings to "rm -rf instead of wipe" and then wipe system

Now you will probably have nothing in your phone since you almost wiped everything so you will probably have to sideload (adb sideload xxxxx.zip) or push it though adb (adb push xxxxxx.zip /sdcard/), then you can reboot and voila!, enjoy!
[Xperia Z1 Original Android Development] ilia1985:
Edit: as soon as i enter mkfs.f2fs -l cache cache the twrp goes crazy.... :(

Thnx will give it a go.. Will it also wipe external sdcard?
[Xperia Z1 Original Android Development] Poesini:
No it wont wipe your external SDCard, but if you are afraid or so, you can do the whole process with it removed and then when its totally booted, put it back again
[Xperia Z1 Original Android Development] lowrider_05:
http://d-h.st/H8f

just use the cm f2fs kernel from above and format as described and after that flash the newest kernel with twrp and everything is working
[Xperia Z1 Original Android Development] Ashray_Vk:
Is the gpu overclock removed ? Im not able to reach 450+ clock rates both by terminal and pimp my z1 app
[Xperia Z1 Original Android Development] Androguide.fr:
[MENTION=4590490]Poesini[/MENTION] reported that too, but I really don't understand what could cause that on your devices, I do have the 600, 533 & 487.5 MHz steps in the last build, running CM.
[Xperia Z1 Original Android Development] Ashray_Vk:
[MENTION=4590490]Poesini[/MENTION] , is your gpu oc alright now ? if yes, what have you done to make it right ?
[Xperia Z1 Original Android Development] ilia1985:
Thank you so much :) worked like a charm
[Xperia Z1 Original Android Development] ilia1985:
Same here... Only have GPU up to 450 only....
[Xperia Z1 Original Android Development] lowrider_05:
for me it is working just fine with the latest kernel
[Xperia Z1 Original Android Development] Androguide.fr:
That's really strange
[Xperia Z1 Original Android Development] dettofatto:
Also for me... But for me it's better! ;)
[Xperia Z1 Original Android Development] 3x3cUt0r:
Same here, max gpu clock is 450, btw it's normal that the gpu always runs at 320 while running pimp my kernel.
[Xperia Z1 Original Android Development] Poesini:
Not really, I am waiting for Omni next build so I can dig more into it... Still @ 450 max, althoug like others say, its enough
[Xperia Z1 Original Android Development] Ashray_Vk:
Was benchmarking... So I needed that extra push.. :D
[Xperia Z1 Original Android Development] ntmohammad:
sry for my question if it is not good. which roms support f2fs kernel ?

thx
[Xperia Z1 Original Android Development] Androguide.fr:
Any ROM will support f2fs, this relies solely on the kernel for our device.
[Xperia Z1 Original Android Development] _Garry_:
Yeah got SlimKat build 4 running with f2fs version.

Needed to use the cm f2fs way but it works fine.

And ROM runs smooth and fast.

The for the kernel Androguide.fr.

But my GPU is showing same as the others 450 at max.

As I was playing around with the values I saw that the slider only shows this steps:

27 - 200 -200 - 320 - 320 - 320 - 389 - 450

And this counts for both sliders.

Gesendet von meinem Xperia Z1 mit Tapatalk
[Xperia Z1 Original Android Development] Juzman:
When I flashed the F2FS Cache zip. TWRP just kept flashing. So rebooted, then went to Wipe Data, and rebooted. Now just stuck on CM11 boot logo.

Also, if I get F2FS going, do I have to flash the F2FS-Cache and Kernel on each nighly update, or just the kernel?

Edit: Gave up on F2FS, back to EXT4.
[Xperia Z1 Original Android Development] Kingcool88:
On kernelversion from 21/3 i have 600mHz GPU, but not in this latest!

Not that i use the 600, but just for info!
[Xperia Z1 Original Android Development] ilia1985:
Had a same problem at first... Use method found on page 55 post 545... It worked like a charm
[Xperia Z1 Original Android Development] zero_5:
sorry I have a question as I can install the Kernel in SlimKat Pimped F2FS? :confused:
[Xperia Z1 Original Android Development] Juzman:
I just stuck with EXT4. It works, works well. :)
[Xperia Z1 Original Android Development] _Garry_:
[MENTION=4459157]zero_5[/MENTION]

Yes you can.

Depending on your z1 you can use the f2fs flash zip OR you need to use the cm-f2fs way.

The cm kernel is posted a few pages back in this thread.

Gesendet von meinem Xperia Z1 mit Tapatalk
[Xperia Z1 Original Android Development] zero_5:
Thank install Kernel pimped achieved. :o when I put flashee F2FS-cache.zip in TWRP recovery is that clearing the cache and not advance, I have to press the pantallar several times to restart, and I stay in slimkat logo, however when using a CM file pages behind me and if I run going great.
[Xperia Z1 Original Android Development] Hav4k:
Unistalled due to high battery drain.
[Xperia Z1 Original Android Development] Androguide.fr:
Probably just the intelliplug bug/race condition with mpdecision, simply toggling intelliplug off and back on in Pimp My Z1 should fix your problem (verify that you don't have all 4 cores online in the CPU control).

This will probably be fixed soon.

I merged some nice additions to intelli_plug made by dorimanx & Alucard24 and a possible fix for this issue (the ksoftirqd high CPU usage bug).

These modifications allow to set the max amount of cores to set online in eco mode (= single & triple-core eco-modes), plus they expose more intelli_plug parameters to sysfs for your tweaking pleasure.

This'll be available next build, along with updated controls in Pimp My Z1.
[Xperia Z1 Original Android Development] xperseus:
My question might sound stupid, but I just want to make sure. I can see it's CM based kernel. But will it work with kitkat stock ROM?

Edit: the ext4 one.
[Xperia Z1 Original Android Development] lowrider_05:
no
[Xperia Z1 Original Android Development] Ashray_Vk:
Try to fix the gpu clocking if possible [MENTION=4752917]Androguide.fr[/MENTION]
[Xperia Z1 Original Android Development] Androguide.fr:
For that I need to understand what causes it first...

I have a hunch that it might be related to CPU pvs binning, as on the same build some people have the issue and some people don't.

Maybe there is a mechanism that for lower-binned CPUs the GPU frequency table is limited.

To everyone, please post the result of this command and precise whether you have GPU OC up to 600MHz or not on the latest build:

Open terminal emulator (free on the playstore) and type the following:

dmesg | grep PVS

If there is no output, use this instead:

cat /proc/last_kmsg | grep PVS

(If you still go nothing, just reboot and do it again)

I'll start, I have GPU OC working properly, and a pvs of 4:

[ 0.851221] clock-krait-8974 f9016000.qcom,clock-krait: PVS bin: 4
[ 0.851387] clock-krait-8974 f9016000.qcom,clock-krait: PVS version: 0
[Xperia Z1 Original Android Development] lowrider_05:
1|root@honami:/ # dmesg | grep PVS

<6>[ 0.937242] clock-krait-8974 f9016000.qcom,clock-krait: PVS bin: 5

<6>[ 0.937405] clock-krait-8974 f9016000.qcom,clock-krait: PVS version: 0

And yes i get 600 mhz
[Xperia Z1 Original Android Development] Poesini:
I dont have GPU OC working and this is:

[ 0.937862] clock-krait-8974 f9016000.qcom,clock-krait: PVS bin: 2

[ 0.938024] clock-krait-8974 f9016000.qcom,clock-krait: PVS version: 0
[Xperia Z1 Original Android Development] _Garry_:
This is my result:

root@android:/ # dmesg | grep PVS
<6>[ 0.937856] clock-krait-8974 f9016000.qcom,clock-krait: PVS bin: 0
<6>[ 0.938017] clock-krait-8974 f9016000.qcom,clock-krait: PVS version: 0

GPU setting min 27/ max 450

Gesendet von meinem Xperia Z1 mit Tapatalk
[Xperia Z1 Original Android Development] ilia1985:
gpu 27mz - 450mz no OC

root@android:/ # dmesg | grep PVS

<6>[ 0.936977] clock-krait-8974 f9016000.qcom,clock-krait: PVS bin: 5

<6>[ 0.937137] clock-krait-8974 f9016000.qcom,clock-krait: PVS version: 0

root@android:/ #
[Xperia Z1 Original Android Development] Androguide.fr:
Alright, so apparently it's not related to PVS, you guys can stop posting your results, thanks all.
[Xperia Z1 Original Android Development] ilia1985:
So is it correct to assume that higher pvs is better?