yashsingh1/xdaforums huggingface dataset:
[Asus ZenWatch 2] joeykrim:
Great, your Makefile cleared up the ASUS_SW_VER error!

Amazing they release kernel source that doesn't compile...

Next error...

1) TIF_MM_RELEASED undecleared

kernel/exit.c: In function ‘exit_mm’:

kernel/exit.c:510:28: error: ‘TIF_MM_RELEASED’ undeclared (first use in this function)

set_tsk_thread_flag(tsk, TIF_MM_RELEASED);

^

kernel/exit.c:510:28: note: each undeclared identifier is reported only once for each function it appears in

scripts/Makefile.build:308: recipe for target 'kernel/exit.o' failed

It does appear to be defined...

grep -irs TIF_MM_RELEASED *

arch/arm/include/asm/thread_info.h:#define TIF_MM_RELEASED	23	/* task MM has been released */

arch/arm64/include/asm/thread_info.h:#define TIF_MM_RELEASED	24

drivers/staging/android/lowmemorykiller.c:	if (test_task_flag(tsk, TIF_MM_RELEASED))

kernel/exit.c:	set_tsk_thread_flag(tsk, TIF_MM_RELEASED);
[Asus ZenWatch 2] T10NAZ:
Your grep maybe or maybe not shed light on the issue.

The first 2 are defined but not in the last 2, the last 2 are calling TIF_MM_RELEASED (at least that is my understanding) however it has a number after defining it

anyways travel to the folder kernel and open exit.c, and assuming you can see line numbers on your text editor, go to line 506, and that whole #ifndef config thing, maybe either do this:

#define TIF_MM_RELEASED 23
#ifndef CONFIG_UML
mm_released = mmput(mm);
if (mm_released)
set_tsk_thread_flag(tsk, TIF_MM_RELEASED);
#endif

or add the define TIF_MM under the config_UML.

Im almost thinking ASUS has some other things outside of the kernel source to allow it to build cleanly
[Asus ZenWatch 2] joeykrim:
Defining it either before or inside of CONFIG_UML both worked to clear the error. Thanks!

Now two more errors:

kernel/asusdebug.c: In function 'proc_asusdebug_init':

kernel/asusdebug.c:1405:15: error: 'struct mutex' has no member named 'owner'

fake_mutex.owner = current;

^

kernel/asusdebug.c: At top level:

kernel/asusdebug.c:1418:15: error: expected declaration specifiers or '...' before string constant

EXPORT_COMPAT("qcom,asusdebug");

^

scripts/Makefile.build:308: recipe for target 'kernel/asusdebug.o' failed
[Asus ZenWatch 2] T10NAZ:
Whats weird is asusdebug.c is exactly the same on the 501 and 502,

this may be a dumb question but, are you make clean after every edit?
[Asus ZenWatch 2] joeykrim:
Yes, I have been using make clean, but the system I'm using might be on newer versions that are causing issues (Ubuntu 16.04).

I'm assuming that since asusdebug.c is the same between devices, you didn't receive the same error?

I'm using the toolchain included with OmniROM: prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi- through export CROSS_COMPILE=/tmp/omni/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi-

Downgraded gcc to 4.8 (/usr/bin/gcc -> /usr/bin/gcc-4.8)

Anything else I should check? Not sure if I should just grab Ubuntu 14.04, put it in a VM and start again from there...
[Asus ZenWatch 2] joeykrim:
Excellent! Yea, not sure whether it's the not-yet-final Ubuntu 16.04 release, OmniROM's toolchain, or some odd combination. If I try again, I'll do everything in a VM with a fresh and final Ubuntu image...

Yes, please!

Once I have the kernel image, I can focus on tinkering with the sparrow build files to get wren compiling and working. Hopefully won't take too much effort and fastboot booting...
[Asus ZenWatch 2] T10NAZ:
Alrighty, I added both zImage and zImage-dtb just in case, dtb is mainly what you will work with.

And for twrp 3.0.0.0, there are a bit of changes you need to do to Sparrows files. So we will both be helping each other out with getting it stable and working right for sparrow and wren :).

https://drive.google.com/file/d/0B_Duyz8Shz-YbmZ2ZE82VUZSR2c/view?usp=sharing
[Asus ZenWatch 2] joeykrim:
Great! Using the kernel you supplied and the slightly modified Build files from: https://github.com/lj50036/platform_manifest_twrp_omni and I forked here: https://github.com/joeykrim/wren

I was able to get the recovery (TWRP-v3.0.0-0) to compile and boot. wren TWRP v3.0.0-0 recovery.img: https://joeykrim.com/android/devices/wren/twrp-v3.0.0-0.jk-v1.recovery.img

Updates now posted in the development thread: http://xdaforums.com/zenwatch-2/orig-development/recovery-twrp-3-0-0-0-wi502q-root-t3343366

Bugs (All Fixed):

1) Unable to backup recovery partition - isn't visible from backup menu

2) The screen resolution is small, but it works! Any suggestions on adjusting the screen resolution?

I'll probably start with BoardConfig.mk settings...

fb0 reports (possibly inaccurate):

vi.bits_per_pixel = 32

vi.red.offset = 0 .length = 8

vi.green.offset = 8 .length = 8

vi.blue.offset = 16 .length = 8

setting GGL_PIXEL_FORMAT_RGBA_8888

double buffered

framebuffer: 0 (280 x 280)

I:Checking resolution...

I:Scaling theme width 0.875000x and height 0.875000x, offsets x: 0 y: 0
[Desire 626 Q&A, Help & Troubleshooting] Prophecy91:
Okay everyone I'm really new to this so please bear with me. I've tried kingoroot, kingroot, I root, and many others to root my htc desire 626.. With no luck. I'm currently p.c less due to where I'm stationed at. I guess my main question is there anyway to root my device without a p.c? My main reason for rooting is to be able to use a game in conjunction with a game I have. Please any help will be greatly appreciated!!
[Xperia Z5 Premium Android Development] zacharias.maladroit:
Final notice: Since my Z5 died (it's broken into pieces, glass shattered) - development is effectively halted - NO more updates - sorry

This is a

Stock (Sony) ROM Kernel

and WILL NOT work on AOSP, CM, etc.

aka

SunKernel

for Z5 Premium + Z5 Premium Dual - Stock ROM (for now only stock)

This is an extension of the Xperia Z5/Z5 Dual "sumire" main thread over at: https://xdaforums.com/xperia-z5/dev...und-z5-wip-t3340725/post65936553#post65936553

Okay,

so the kernel is now also available for the Z5 Premium series

Please understand that I can't test whether it works due to lack of that very device - Enjoy !

Keep in mind that building for the Z5 "Stock" ROMs and "Stock" Kernels, you're constantly facing the following tradeoff:

compatibility with pre-built "core" kernel modules (e.g. texfat [proprietary exfat microSD fs driver])

compatibility with pre-built "goodies" kernel modules (e.g. video and other acceleration, hwcodecs, ...)

losing features that can NOT be replaced by similar ones (e.g. ecryptfs, wlan, exfat, etc.)

when going too far the device doesn't boot or simply hangs on bootanimation

this resulted in a couple branches (at least several dozen) that are partially or totally broken :silly:

[snip]

...

[snip]

More info on the Latest Kernel can be usually found at:

AT the end of the thread

( I KNOW - I should have reserved a few posts for better overview :( )

---------------------------------------------------------------------------------

[Download] How to get the

current

("corona", 5.11) Kernel(s) - Step by Step:

Before starting to test/use keep in mind that this is WIP (work in progress),

that means - NO guarantees,

backups before flashing are a MUST (especially your microSD card content !)

stability, speed, improved battery and satisfaction are a great side-effect to have.

You have been WARNED !

Enjoy ! :)

Obligatory Source:

(according to the rules in single commits no giant blobs, authorship kept)

https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2/branches
[Xperia Z5 Premium Android Development] Ashray_Vk:
[MENTION=3037651]zacharias.maladroit[/MENTION]

Amazing to see this and very happy too!

Let me know if you want testings to be done, will be glad to help to the best of my knowledge. Ive used two Sony phones before this, and think I can help you out with testings :)

Edit: And does this support the dual versions too? I'm outside and I can't test at the moment. So, just asked.
[Xperia Z5 Premium Android Development] GuestK00195:
Undervolting is not added?
[Xperia Z5 Premium Android Development] zacharias.maladroit:
Glad you like it !

Nope - lol, I was actually waiting for demand for the dsds models,

I've already downloaded the kernel but haven't extracted the initramfs for it yet

You have the dual version ?

*edit:*

from one of your posts - it looks like you have one

okay then - I will build one later,

let's see if the build works equally reliable for the dsds models ;)

Of course, the kernel base is by [MENTION=5169444]AndroPlus[/MENTION] <3

undervolting currently isn't working correctly right now though - values go too low (e.g. -250 mV) - so some parts might be missing,

I haven't looked into it yet - focus currently is to get the kernel working in a general sense, then later trying out the "goodies" (UV and others)

hope I can take a quick look later what might be missing
[Xperia Z5 Premium Android Development] GuestK00195:
Ok, thanks. I'll give it a try ;)
[Xperia Z5 Premium Android Development] Ashray_Vk:
Awesome :) will flash this once dual sim models are supported since I have a dual sim phone.
[Xperia Z5 Premium Android Development] KbaB.BroS:
Enabling a CPU hotplug makes the cpu warmer faster than normally. It even gets warm when I listen to music with the screen off, which never happened before.

I'm using blue_active governor for both big and LITTLE.
[Xperia Z5 Premium Android Development] zacharias.maladroit:
Thanks for your feedback,

what hotplug mechanism did you choose ? with what settings ?
[Xperia Z5 Premium Android Development] Ashray_Vk:
[MENTION=3037651]zacharias.maladroit[/MENTION]

Could you please make a version for the dual users too? I'd be thankful to you :)
[Xperia Z5 Premium Android Development] zacharias.maladroit:
done ...

Xperia Z5 Premium dsds (Dual) [E6833/E6883] supported Kernel is attached in first post now ;)
[Xperia Z5 Premium Android Development] Ashray_Vk:
Can I know how to control the tomtom sound control? Searched for it in sys/class/misc as I thought it'd be there, but I was wrong. Help us out?

Edit: And thanks a ton for the dual version. Kernel is working OK as of now except of the sound control,, need more time to comment on the battery life though.
[Xperia Z5 Premium Android Development] KbaB.BroS:
Intelliplug default settings
[Xperia Z5 Premium Android Development] Ashray_Vk:
As of today. Ive got a battery drain of 2% in three hours. Couldn't test for longer since I got only three hours of sleep and had to take the phone off idle.

I think the battery performance is good since I'm using two sims, and one was on LTE mode.
[Xperia Z5 Premium Android Development] KbaB.BroS:
Would you please include FauxSound in your next update? To me that's the only thing missing from this kernel.
[Xperia Z5 Premium Android Development] zacharias.maladroit:
Sure,

https://github.com/zachariasmaladro...ts/Sun-Kernel_32.1.A.0.xxx_AP-mod-v21_I.2_1_5

feel free to take a look at the source & adopt it to our device (or pick someone's brain to do it),

right now the settings affect nothing.

Since I'm mostly busy all the time right now I currently can't get my mind calm enough to fully get an understanding of this, :(

besides this - the kernel is finished and running much cooler (assumedly also better in terms of battery runtime)
[Xperia Z5 Premium Android Development] Ashray_Vk:
Hey

I think faux sound control was working okay with our device in auras76 kernel

Well, analog control was broken, wasn't working.

I'm not able to Control sound using Tom Tom control. Any way to do that?
[Xperia Z5 Premium Android Development] harborxperia:
Very nice kernel, stable. Does it Include DRM support?
[Xperia Z5 Premium Android Development] zacharias.maladroit:
Yeah, looks like that,

Faux Sound Control works, Kernel Adiutor - not so much, been wondering all the time why there was no difference at all :confused:

Tom Tom control afaik isn't included in that kernel source ?

Patience please, I'm currently testing a totally revamped kernel (different hotplug - cpuquiet - well, there are quite a few to choose from, lol :D ),

the usage consumption looks way better compared to the one with all those hotplug mechanisms.

That's quite a difference now but if Sony's apps (Photoanalyzer, devicemonitor, camera common, ... - I look at you :p ) and others wake up every few minutes,

there's only so much the kernel can do ...

Don't forget to use Greenify's Aggressive Doze +/- Naptime ! :)

Thanks !

Nope, not the job of the kernel, DRM patch is included in AurROM
[Xperia Z5 Premium Android Development] KbaB.BroS:
I fastbooted your kernel on a clean install of stock ROM and the DRM patch is active.
[Xperia Z5 Premium Android Development] zacharias.maladroit:
Might be something in the initramfs, then - thanks :)
[Xperia Z5 Premium Android Development] zacharias.maladroit:
updated Kernel is up !

Please download 305_corona_III.1_9_12_3_2_ctl_X

1_9_14 wasn't able to play e.g. PowerAMP while the screen was off,

IPA isn't really doing what it's supposed to do - focusing doing its job for networks

it also seems to take care for audio - for whatever reason :(

Android is some weird mess
[Xperia Z5 Premium Android Development] -DM-:
Hey Zach...

I've been using 1-9-12 with systemless superSU 2.78 and updated superSU to 2.78 SR1 the other day through recovery...

Today I updated to 1_9_12_3_2 and I was getting SU binary update nags right after boot, manual binary update from within superSU failed so reflashed 2.78-SR1 from recovery and that failed as well, the error comes from boot image patcher failing while trying to flash superSU with this latest kernel...

I had superSU 2.76 zip saved on my sd so tried to flash it as well and same problem error with boot image patcher in recovery as well....

So I extracted the 2.76 superSU apk from the zip to install it manually and updated to 2.78 from the Play Store after that...

I tried to do the same with 2.78-SR1 (extracting the apk from the zip) but end up with baniry update nag allover again...

Something with this last kernel is interfering with superSU if trying to flash it in recovery and 2.78-SR1 is bugging no matter what....

None of this going on with the previous kernel 1_9_12

I can upload the recovery log if you're interested or needed...

Other than that the kernel boots fine on my rom which is still fw. 224, will give more update after longer use of it though as I posting this problem here just right after install....

Thanks as always
[Xperia Z5 Premium Android Development] Tilman:
I had the same issue, what I did was, switch back to 1.9.12, so if you're using systemless root, you won't have root access after you flash the old version! If you do have it, unroot completely from within the app. Now install 1.9.12.3.2 & don't flash SuperSU. Just simply boot up. This way, I don't get any notifications for binary update, it works flawlessly.
[Xperia Z5 Premium Android Development] -DM-:
Yeah realized that that root access was gone after downgrading to 1-9-12 from 1-9-12-2-3, but easy remedy to the problem by flashing superSU again....

I'm on 1-9-12-2-3 right now with systemless 2.78 without any problems....my previous post was just too point out that the latest superSU beta (2.78-SR1) is bugging out with Zach's latest kernel and it was not the case with the exact same version of superSU and the previous kernel....

Also if I understand correctly your post, your on 1-9-12-2-3 without root or does the kernel contains root (in that case I didn't see any mention of it in the changelog)...?!?
[Xperia Z5 Premium Android Development] Tilman:
I am on 1.9.12.2.3 with root access, you don't need to flash systemless SuperSU after flashing the kernel, the new one has it built into it!!
[Xperia Z5 Premium Android Development] the_brad:
Yeah, had the same issue. Glad, I was smart enough to uproot from within SuperSU app before I updated the kernel (had to learn the hard way any times before). I got the same errors while flashing 2.78-SR1.zip with boot image patching. Then rebooted and was glad, root still worked. Then I wanted to flash suhide 0.55 in recovery, but that failed, nagging about missing SuperSU. [MENTION=3037651]zacharias.maladroit[/MENTION] did you repack that mentioned new ramdisk by yourself with tobias.waldvogels repacking tool? Maybe you integrated SuperSU... It worked best for me with the settings from the Screenshot, I put with the patched kernels a few months ago.
[Xperia Z5 Premium Android Development] -DM-:
Sorry wasn't quite awake when I wrote that last post ;)

By root I meant root manager app which is what superSU is after all, so you'll still need some app to manage what wants to access root...

On 1-9-12-2-3 superSU 2.78 works fine if you install the apk manually from the zip, then flash the zip from recovery afterwards to update binary, or do the same thing with 2.76 then upgrade to 2.78 from the Play Store....

2.78-SR1 won't work that way though...at least it didn't when I tried
[Xperia Z5 Premium Android Development] Tilman:
No, I didn't even install the SuperSU app. Guess it's preloaded into the kernel.
[Xperia Z5 Premium Android Development] :
Hey I can't find the download link for the E6883 Dual Sim variant, mind linking me to it? :/

EDIT:

Just to clarify, https://drive.google.com/drive/u/0/folders/0BykGGWB96CBQaVZTdnF5QnVTMU0 they all apply to EVERY Z5 Premium variants right?

and I extract boot.img from the ZIP then flash it via Flashtool?
[Xperia Z5 Premium Android Development] -DM-:
For E6883, use DSDS files, the latest kernel is 1-9-12-2-3

And no need to extract the boot image, just flash the zip from recovery...
[Xperia Z5 Premium Android Development] :
what if I cant access recovery on my phone? Can't I just extract it? :confused:
[Xperia Z5 Premium Android Development] -DM-:
Yeah go for it then...but as a piece of advise, you should install a recovery so at least you can do a backup before flashing a different kernel on your device just in case something goes wrong
[Xperia Z5 Premium Android Development] zacharias.maladroit:
Alright, so no stability issue for you Z5P users ? (reboot, NFC, bluetooth working, ...)

I'm thinking more and more that the Z5 crowd is living too risky and tweaking too much ;)

Can anyone point me to a kernel with a ramdisk that does NOT include supersu ?

I'll gladly replace the ramdisk with a new one for the latest kernel (upcoming)

Thanks
[Xperia Z5 Premium Android Development] Tilman:
Long as I remember, it was V253 III.1_9_12_2, but then it was removed from your drive.
[Xperia Z5 Premium Android Development] the_brad:
Just give me half an hour...

----

Your latest kernel seems to be the most stable and power saving so far (at least for me)! Really glad to see so much improvement over sony's stock software.

Link for patched kernel is here.

Please note, I made two versions:

One is only patched with TWRP and DRM-patch. (As I try to go more and more systemless, I would definitely prefer this one! RIC and Verity are patched by SuperSU, Busybox comes with Magisk)

Second one is patched with everything, that can be done with tobias.waldvogels tool.
[Xperia Z5 Premium Android Development] theduke7:
Hi [MENTION=3037651]zacharias.maladroit[/MENTION] , i'm using Z5Prem-DSDS_Sunkernel_Permissive_v305_corona_III.1_9_12_3_2_ctl_X_sats_dual , on my Z5p E6833 (dual)... is this the latest?...

also i saw 3 variants the one i use and one with "t2" at the end of the name and another one...can i ask whats the defference between the 3.. i search the thread and i don't seem to find the answer... also i can't find the main site or page for the files, i downloaded it from GDrive link that was given to me.?

the one i'm using is stable so far, very good work, only i think the battery is drain faster, but it can be on my end.
[Xperia Z5 Premium Android Development] -DM-:
Hey Matt, back home finally after a month...

The only thing I see with 1-9-12-2-3 is that is running warmer (so impact on battery) than 1-9-12 in general and more when scrolling pages which bring gpu way into 60°C+ while 1-9-12 stays in the 50°C+ at the max...

I thought it was maybe the poor wifi networks that I was using at time while abroad but did some tests since back home and the same goes on here on wifi and on my LTE network...

I keep a close eye on heat as I fried my audio jack while in vacation, from what I read in the "audio jack falling" thread here on xda, it looks like the jack connector is somehow hold into place by a tape and the glue has definitely weakened, I can get the jack to recognize that the headphones are plugged in if I press on the back panel quite firmly (the back panel is not lifted so still waterproof, only that jack tape has been affected so far) otherwise noise canceling and headphones in is not activated and I can't use my headphones (which sucks...no more music for now)

Thanks as usual ;)

---------- Post added at 09:36 PM ---------- Previous post was at 09:31 PM ----------

Which recovery version are you using by the way, did you try to fastboot a different one?!?
[Xperia Z5 Premium Android Development] zacharias.maladroit:
Yes, but v253 is using a pure 253 firmware ramdisk,

since 305 firmware is out I'm striving to provide a kernel that works on 224, 253 and 305 (well, as long as the firmware/ROM, ramdisk and kernel allow it)

Thanks

Excellent - thanks for the quick work :good:

I chose the minimal ramdisk and hope that it works,

I doubt that SonyRIC and dmverity are also somehow set in ramdisk but usually both need to be set to "off" (dmverity set to on from your screenshot)

This latest Kernel contains the SafetyNet mitigation patch so you can give a try and see if e.g. Google Movies, etc. works with it

Please toggle list view and take a look at the date,

1_9_12_3_2 is latest,

t2 or t3 is usually a last-minute correction build which fixes boot failure or some more severe issues I encountered after having uploaded the kernel, then replacing the already uploaded kernel with t2, t3, etc.

Thank you :)

Hi Davide,

Sounds like a design problem to me regarding the headphone jack :eek:

Okay, thanks for the temperature reports,

I can take a look and see if anything suspicious stands out from the commits that could point to that

afaik moonbutt74 also seemed to have had that issue ? (or did I confuse him with another case on XDA ?)

anyway - you're not the only one which points to a series issue or build issue of a certain line of devices - oh well :(

Thanks
[Xperia Z5 Premium Android Development] zacharias.maladroit:
Download

Z5P (satsuki): https://drive.google.com/open?id=0BykGGWB96CBQaVZTdnF5QnVTMU0

305_corona_III.1_9_12_3_3_ctl_X

This is an Troubleshooting, enhancement update

Changes:
[Xperia Z5 Premium Android Development] theduke7:
[MENTION=3037651]zacharias.maladroit[/MENTION] thanks for the reply m8...

i noticed there's also a new 305_corona_III.1_9_12_3_3 for dual , i don't know if it's meant for my device, but i tested it anyway, the phone stays at the sony logo...

please never mind this if it wasn't meant for me to try it ;)
[Xperia Z5 Premium Android Development] scarletnokarasu:
hi the new kernel doesnt boot for me too
[Xperia Z5 Premium Android Development] Tilman:
I don't know why some of the users are having issues with kernel, I only use LTE, indeed I never turn it off, and even at heavy multitasking, the maximum temperature I've seen my gpu is at 55°C. I don't live in a cool place, I live in India quite close to The Tropic Of Cancer. Maybe, I'll try 4K recording/playback to heat it more!!! Also since the past few kernels, my battery life seems a lot stable, to have at least 5hrs & 45 minutes of screen on time is fantastic. And I only charge my device everyday at 4Pm. Maybe I'm wrong, but such temperature spikes can be related to rom too. I've been using Moonwalker Amaluna Pro-Spect v1.6.0 since quite a while & I don't have any complaints.

Zach, you're doing an amazing job at the kernel, especially issuing the latest vulnerabilities.