Nice @olokos
F2FS supported?
Will try it on MX ROM, dont know if it works. And building a version with UberTC 6 (just for fun)
F2FS supported?
Will try it on MX ROM, dont know if it works. And building a version with UberTC 6 (just for fun)
Thanks hope u will fix the issue asap...we will w8Lol. That's really weird. I'll flash completely stock rom when I get back home and fix it.
There's no f2fs yet, but I'll add it at some point.
Unrelated but I think prima module gives compile errors with gcc6, good luck though. Also gotta fix up some other code for it to even compile with gcc5 and gcc6.Nice @olokos
F2FS supported?
Will try it on MX ROM, dont know if it works. And building a version with UberTC 6 (just for fun)![]()
You have his custom boot logo showing at boot right? If you download Kernel Auditor you should see the new features.mates, I am new to custom kernels, I flashed this alongside .236 stock firmware. After flashing nothing changes or any additional kernel manager or kernel menu for setting preferences. Do I still need to download such things to utilized the stated features of the custom kernel? thanks in advance for you help.
You have his custom boot logo showing at boot right? If you download Kernel Auditor you should see the new features.
Doom's kernel isn't for lollipop---------- Post added at 07:21 PM ---------- Previous post was at 07:20 PM ----------
Yes mate, I'm done for everything and enjoying the kernel. I read researches and like what you advised, I figured out that I need to install the Kernel Auditor app. anyway, thank you for your informative response. At least I'm now familiar on how custom kernel works. Once it drains the current charge, I'll monitor the battery consumption if it works nicely with dStriker SP001 ROM.
By the way, may I ask how this kernel comparable to dooms?
I can confirm this! Working great with stock ROM.It works perfectly fine with stock 14.6.A.1.236 firmware. I flashed it specifically just to make sure. It bootloops with MX Rom. I'll see what can be done there.
It works perfectly fine with stock 14.6.A.1.236 firmware. I flashed it specifically just to make sure. It bootloops with MX Rom. I'll see what can be done there.
V5 = v4 + v5 featuresHello one question i see you have added new features in v5 will those be in v4 too cause i am still using (.368 )?
It should work fine as it works good on dstrikers,but you tell me. You can always flash back stock kernel at any time. I think only mx rom has some weird hacks.How will it work on RockZ1LP ?
Please share more info. What ROM are you using? What's the firmware version? Are you sure your bootloader is unlocked?Still doesn't boot on my side.
Stock 5.1.1 236, Xperia Z1 C6902, yes I'm pretty sure the bootloader is unlocked.Please share more info. What ROM are you using? What's the firmware version? Are you sure your bootloader is unlocked?
[ro.board.platform]: [msm8974]
[ro.boot.hardware]: [qcom]
[ro.boot.serialno]: [BH904KD21J]
[ro.build.version.sdk]: [22]
[ro.hardware]: [qcom]
[ro.product.brand]: [Sony]
[ro.product.manufacturer]: [Sony]
[ro.product.model]: [C6902]
[ro.product.name]: [C6902]
[ro.revision]: [0]
[ro.semc.product.model]: [C6902]
[ro.semc.product.name]: [Xperia Z1]
[ro.semc.version.cust_revision]: [R1D]
[ro.semc.version.fs_revision]: [14.6.A.1.236]
[ro.semc.version.sw_revision]: [14.6.A.1.236]
[ro.serialno]: [BH904KD21J]
[gsm.version.baseband]: [8974-AAAAANAZQ-10270086-81]
So would the only way to use the new v5 is to flash stock (.236)?V5 = v4 + v5 features
V4 =v4 features
There's no reason to flash v4. V5 is much better. I just left v4 so I could easily access every version if my kernel when opening this thread. I think if v4 worked then v5 should also work. At least I'm using .216 rom (modified to my needs) and it works well with v5.
It should work fine as it works good on dstrikers,but you tell me. You can always flash back stock kernel at any time. I think only mx rom has some weird hacks.
<6>[ 8.047226] wp_xperia_mod: Defeat system write protect version 0.1
<6>[ 8.047239] wp_xperia_mod: by flar2 / MohammadAG
<6>[ 8.063063] Hooking function 0xbf008000 with 0xbf008000
<1>[ 8.063077] Unable to handle kernel paging request at virtual address bf008000
<1>[ 8.063087] pgd = c4bec000
<1>[ 8.063093] [bf008000] *pgd=04b89811, *pte=04a8f4df, *ppte=04a8f65e
<0>[ 8.063111] Internal error: Oops: 80f [#1] PREEMPT SMP ARM
<4>[ 8.063119] Modules linked in: wp_mod(O+) byeselinux(O)
<4>[ 8.063135] CPU: 2 Tainted: G W O (3.4.0-OK_Kernel_v5-g11a8170 #103)
<4>[ 8.063148] PC is at mem_text_write_kernel_word+0x28/0x48
<4>[ 8.063157] LR is at mem_text_write_kernel_word+0x1c/0x48