yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 Compact Original Android Development] okij:
Ah, OK. I thought that they were undervolted a bit in favour of battery performance, but I didn't check. Still I have the feeling that battery is performing a bit better than with the standard kernel, is it because of 268 instead of 300 MHz as min. CPU frequency?

That's great, thanks a lot! :) When the new version is out, I will make a post on the Z3c LineageOS and on the CarbonROM threads to inform other users about it.

Yep, I've just set it to enforced, like it was on the standard kernel too, and everything works fine.

That would of course be nice, especially if the OS devs would implement a swich in the settings to toggle it. But for me it's already great as it is (just flash and forget. ;))

Cheers! :)
[Xperia Z3 Compact Original Android Development] funiewski:
Off topic:o nice to see you are back and there is some action in z3c forums, sadly I don't use this device any more, my daily now is P10, nice phone but very strange flashing
[Xperia Z3 Compact Original Android Development] JDC2389:
Hey there, just letting you know that with the latest kernel update the clocks and kernel performance is amazing, only problem is it seems to kill wifi. I reflashed the new Carbon weekly to try the stock kernel again and wifi is working. Here's a log a hope it's helpful if not let me know if I can get a better log somehow.
[Xperia Z3 Compact Original Android Development] someone755:
You can't, and I ain't fixing this -- however simple it may be. S'hit works fine with Lineage.

This week's Carbon build diverges from the Lineage trees. I don't intend to keep several kernel trees downloaded and in-check just so I can support every fork. You can ask in the Carbon and Lineage threads if they're going to work together or at least keep a common base.

*Probably* this will be solved by Carbon's next weekly build, but I'm not holding my breath -- I'm off for some much needed vacation. Cheers!
[Xperia Z3 Compact Original Android Development] okij:
Yes, I experienced the same and already contacted [MENTION=4275152]someone755[/MENTION] about it.

Problem is that the current Carbon weekly isn't in sync with the current LineageOS devicetree, so there are also differences in the kernel which break the Wifi functionality. Therefore I hope that [MENTION=3816568]Myself5[/MENTION] will fully sync the devicetree for the next weeklies again. :fingers-crossed:

In the meanwhile, I'm using the latest LineageOS build, which now also has working BT calls, as well as a working camera button. :good:

I don't want to miss [MENTION=4275152]someone755[/MENTION]'s Kernel12, especially since it now prevents the magnetic charger from invoking the useless Desk Dock Mode. :)

Edit: I just saw that, while I was typing, someone755 already posted an answer.

[MENTION=4275152]someone755[/MENTION]: Enjoy your vacation! :cool:
[Xperia Z3 Compact Original Android Development] JDC2389:
Thanks for the heads up, looks like I'm jumping ROMs. Enjoy your vacation!
[Xperia Z3 Compact Original Android Development] Myself5:
Wowowowow... Hold on... It's Lineage that is outdated this time. Carbon has working 5GHz Wifi on devices without the SIM card. I already talked with Jari about it (we talk on a daily base) and it will be fixed soon.
[Xperia Z3 Compact Original Android Development] okij:
Thanks for your feedback, much appreciated! Sorry if I was a bit too harsh. :)

BTW, 5Ghz Wifi isn't fully working on both ROMs yet. With my FritzBox 7490 I just get 200 Mbps, while on stock ROM I was getting full 433 Mbps. Signal strength is worse than on stock. Besides this, screen cast isn't working yet, as I reported on both ROM threads. I guess that most or all of these problems could be solved when stock .291 Wifi drivers were used.

I really wish that there was a closer cooperation between the devs to get the last major devicetree bugs sorted.
[Xperia Z3 Compact Original Android Development] someone755:
I got upgraded from 5/4 Mbps to 30/5 Mbps in October, and I should be getting 100/20 by the end of the month. I'm the envy of most of my friends with these speeds.

Honestly screw both of you :(
[Xperia Z3 Compact Original Android Development] okij:
Haha. ;) Sorry, but we're talking about different things. :)

433 MHz is just the Wifi speed between the phone and the router on the 5Ghz band. This can (theoretically) be used when transferring files to / from the PC.

DSL-wise I "just" have a 50/10 Mbps line since two months, before it was only 16/1. I didn't even want to upgrade (DL was OK, upload of course a bit slow), but German Telekom forced me because of their change to VoIP.
[Xperia Z3 Compact Original Android Development] someone755:
Thing is I don't get a 5GHz router from my ISP -- so their cra'ppy modem only allows for a few MB/s transfer locally. It's actually about as fast as uploading the file to cloud and then downloading on the other computer lol.
[Xperia Z3 Compact Original Android Development] someone755:
r_11: http://bit.ly/changelog12-1
[Xperia Z3 Compact Original Android Development] Loken88:
How do you set up the kernel to keep the battery running all day long?
[Xperia Z3 Compact Original Android Development] someone755:
Well as you know this is in no way specific to each phone and each person's use scenario, so it is very simple. Set the minimum and maximum frequencies to the same values (preferably a value over 2 GHz) , add about 50 mV to that voltage. Make sure to use MPDecision and completely ignore the thermal throttling.

The other extreme, of course, is setting both frequencies to 192 MHz, lock the GPU to 27 MHz, and only use one core.

Try it out mate, there isn't really much you can get wrong, especially if your kernel app doesn't apply the changes at boot. I personally get 4 hours of screen per day (sometimes two) with what I'd call relatively heavy usage (without playing games). Using the default Intelli plug settings, max CPU screen off freq at 1190, interactive governor, adreno idler default settings, ranging from the lowest available gpu freq to the second highest. Max cpu freq is 1.7GHz. Thermal throttling at 50 for cores and 60 for frequency. Cpu boost to ~700MHz on touch event.

Again, this is very specific to the user. I've been using my phone long enough to know these settings by heart, and I've tried enough sh'it to know that these settings will work for me, for what I do with the phone, for how long I expect it to last, and how smooth I want it to run. It's the perfect combo, but will likely not work for you. Start with the basics and try if they change anything for you. Then one by one try different options to see how you (don't) benefit from them. There's no one size fits all answer to this.
[Xperia Z3 Compact Original Android Development] okij:
[MENTION=4275152]someone755[/MENTION]: In LineageOS the kernel has been updated from 3.4.0 to 3.4.113 (I don't know if this has already been merged into CarbonROM too).

Do you think it would be worth updating your kernel as well?
[Xperia Z3 Compact Original Android Development] 2muchpain:
Does this kernel have F2FS support?
[Xperia Z3 Compact Original Android Development] someone755:
Nope. As far as I can tell the lads are moving to cm-15 and I can't be arsed to bring the current changes to Carbon. M5 says it's likely that one merge won't cut it so I'm sitting it out.

Besides, I've been reading the lineage thread and lots of people seem to be having BT/WiFi problems that weren't there with the older builds. This is my only phone after all, I do want to play it safe.

The stock Lineage/Carbon kernel should. I haven't tested it out, and I haven't tweaked the filesystem drivers so if it works there then it works here. Do note that k12 isn't up-to-date with Lineage so it likely won't work with the newer builds.
[Xperia Z3 Compact Original Android Development] :
Pffffft, git gud

*proceeds to wipe device to test O for the 100th time*
[Xperia Z3 Compact Original Android Development] okij:
That's perfectly alright for me. :)

I'm also following the Lineage thread and that's what I thought as well. :p

Honestly, I'm really happy that everything runs rock stable on CarbonROM with the 3.4.0 kernel. Besides this, I don't even know what would be the benefit of the 3.4.113 kernel.
[Xperia Z3 Compact Original Android Development] someone755:
At least my phone has one working custom ROM. Likely because it doesn't have to rely on sodp. Cough, cough.
[Xperia Z3 Compact Original Android Development] Cirra92:
I have successfully flashed your kernel on top of latest Carbon rom (Sept 5), and it worked, but I had couple random reboots and once the device just turned off by itself. I guess that's what you pointed out anyway, that since you didn't update kernel, it might not work. However Carbon is still at 3.4.0 kernel, so is there any chance of a small update of your kernel so that it works with it? If that doesn't require too much hassle since their base hasn't changed. ( If it does, well I'll have to live with it :crying: )

I have used your kernels in past, since they had all essentials built in, great work :D
[Xperia Z3 Compact Original Android Development] okij:
For what it's worth: I'm using the exact same combination on my Z3c without any problems.
[Xperia Z3 Compact Original Android Development] Cirra92:
With or without Magisk? Maybe that's where the conflict was. Will try flashing the kernel again then, thanks for the feedback.
[Xperia Z3 Compact Original Android Development] okij:
With Magisk.
[Xperia Z3 Compact Original Android Development] someone755:
As far as I know, Carbon kernel trees have barely changed since the last k12 update.

I'm still using a homebrew Carbon build from 30/7 because nothing significant except for the ROM itself has been updated. Magisk and all, for what it's worth.

Also good basketball game, really got intense, well played :)
[Xperia Z3 Compact Original Android Development] Cirra92:
It seems that I f*cked up somewhere on previous attempt, I'm running the same mentioned config from last night and everything is good so far :)

Haha oh yeah, really nail biting game, but good one, worthy of final, and considering the players we brought (missing 7 of the best), this is amazing achievement, and you've deserved the gold anyhow :) Even better is the fact that you kicked out Spain, I swear I can't watch them play, it's disrespectful for basketball :D
[Xperia Z3 Compact Original Android Development] Bluestar01:
Should this Kernel work with newest Carbon release?
[Xperia Z3 Compact Original Android Development] okij:
Yes, it's working fine with CARBON-CR-5.1-MOO-RELEASE-z3c-20170918-1012. :good:

Edit: P.S. [MENTION=4275152]someone755[/MENTION]: Since you are using CarbonROM too, how about adding it to the thread title?
[Xperia Z3 Compact Original Android Development] Bluestar01:
I am on latest Carbon Rom CARBON-CR-5.1-MOO-RELEASE-z3c-20170918-1012

i tried to flash this kernel.

First time without pressing any button during TWRp--ended up in black screen, only one vibrate while power on.

Reinstalled old system by flashtool, and went back to recovered system again.

Second try i pressed volume up button for SELinux but the same situation.

Can you give me a small help?
[Xperia Z3 Compact Original Android Development] Bluestar01:
I think i found out:

In r_11 on download page of Kernel, the boot.img is missing.

I only found boot.img in renf_01.zip , but not in r_11.zip

Do i manually need to produce a boot.img?
[Xperia Z3 Compact Original Android Development] Bluestar01:
Sorry once again, but i don´t get it working

Can anyone explain, how to flash this kernel for latest carbon rom, please?

Thank you!
[Xperia Z3 Compact Original Android Development] drorcun:
same situation for me, but not only this kernel, the other custom kernels made before for z3c give the same result, black screen and a short vibration :( think some z3c like ours has different hardware configurations..

Xperia Z3C cihazımdan Tapatalk kullanılarak gönderildi
[Xperia Z3 Compact Original Android Development] beflythis:
is there any way to flash this kernel via fastboot/adb? i (like a noob) installed a broken kernel on another thread that removed recovery. can't get it back through any means, so trying to change the kernel first but have no recovery. help?

edit: believe I would need the kernel in an .img format, yes?
[Xperia Z3 Compact Original Android Development] someone755:
fastboot flash recovery recovery.img

Assuming, of course, that you're running the most recent bootloader (the Marshmallow one, .291 I think it was?). An alternative is to extract the zImage from this zip and use mkbootimg to merge with your preferred ROM's ramdisk.

Please bear in mind that this kernel in and of itself does not offer a recovery (because that's not what kernels do) -- the functionality depends entirely on the ramdisk, which my script does not modify.
[Xperia Z3 Compact Original Android Development] Infy_AsiX:
Thanks for the kernel. I'm testing and comparing with a couple of Z3Cs. I'm finding that LOS runs hotter than .291 with similar settings on elitekernel. For instance if I set intellithermal's throttle freq' equally, the frequency when being throttled is a little lower while the temperature remains about the same. With the throttle temp setting equal to a lowered stock value, LOS will be too slow during moderate gaming. This means I have to set LOS's freq throttle 4 degrees higher. The issue then is the battery is typically pushed a few degrees higher into the hot low to mid 40's.

I even swapped the boards between the phones to check it's not my replacement screen's fault. Maybe it's a ROM fault, I'm not sure as I only started testing recently, however LOS has no bloat and minimal background apps set up still.

On a different note the sound control resets to max analog gain of 6 after playback is stopped for a few seconds. I still prefer having it for adjusting the analog gain to suit the headphone sensitivity for audio quality. I've got a few Tasker commands to help readjust the gain, though it's far from ideal. Back on custom stock the analog gain only reset upon replugging in, not on new playback.
[Xperia Z3 Compact Original Android Development] someone755:
Thanks for trying it out!

I can't comment on that, sadly, as it's out of scope for my use cases. I can, however, say that the LOS stock kernel, by default, does allow the phone to get much hotter than if running intelli_thermal; Why there would be a difference in frequency throttling between k12 and ek I can't say.

The functionality of kernel-driven sound control depends entirely, as far as I'm aware, on its implementation in the kernel. Keep in mind though that it has always been broken to some extent. If the kernel you ran with stock used a different version of the sound control driver then it's more than likely that that's why it functioned differently. As of now I can't do anything to test its functionality, even if I had any intention to, because my headphone jack isn't working.
[Xperia Z3 Compact Original Android Development] Infy_AsiX:
It's a pleasure. Tweaking and audio quality are a must for me :fingers-crossed:.

I'll have to give it a test. As it is already, just moderate usage is running the battery hot.

Edit: Tested, wow LOS was like an act of violence to my battery temperature. Maybe I'm just doing it wrong. A couple of extra degrees on K12 is nothing in comparison.

Edit2: Well I fixed my problem. Turns out the major difference was not having my undervolt values applied on LOS. That's a huge difference, I hadn't a direct comparison when I first applied them on stock long ago to realise their significance. I had tried to apply them on LOS a few days back but was incidentally met with an instant crash that threw me off. I can use the same Intellithermal freq' throttle temp' as stock custom with similar performance. Cheers :victory:

Edit 3: :silly: aaand I just crashed. Seems UV values can't be as aggressive as were on stock. This is on a better PVS9 bin versus PVS6 stock same values too. Will scale back

Yes it was EK, which used fauxsound 3.6 whereas K12 is 3.8. If that's the difference I'm willing to test for you.

A jack from Ebay is cheap. The installation is the tricky part though also losing waterproofing. May be worth it if it's important to you though.
[Xperia Z3 Compact Original Android Development] beflythis:
sorry, not following - where am i sourcing the recovery.img file?
[Xperia Z3 Compact Original Android Development] someone755:
Oh no worries, I still have this thing in warranty until 2019 -- Crazy, I know, I bought the phone in October 2014 hehe.

I can go through EK's commits and try to make k12 run the same sound control driver, if you're willing to test it.

Wherever your heart desires (:

There's a myriad of TWRP builds for this phone out there, just pick one and flash it.
[Xperia Z3 Compact Original Android Development] Infy_AsiX:
Wow that's commitment and foresight, on release too. Perhaps this means long term kernel support for us ;).

Nowadays in hindsight I'd want extended warranty for keeping this unique quality package together. Nothing since has quite matched or succeeded overall. It seems Sony Mobile's cuts after the Z3 release has apparently had detrimental long term effects. Though I've only ever purchased them secondhand. I've lost two Z3C's to damage and have two left now. Those two left have replaced audio jacks, a replaced screen and a partially broken screen. Though I've also modded the batteries to be removable swappable and I'm in the process of adapting a GS8+ 3500mAh replacement battery.

If you can get the battery replaced under warranty considering it needs a jack too that seems worthwhile. Long extended warranty basically covers the need for a replacement battery. At 80% retained capacity a battery is considered depleted. Capacity loss is greatly accelerated after 80% as is the risk of safety measure failure

https://qnovo.com/what-happens-after-80-percent/. The industry leader in support and sales by model volume, Apple's warranty policy follows this guideline https://support.apple.com/en-au/iphone/repair/battery-power. Though with unofficial extended warranty it's more likely they'll give you a successor replacement if a fix isn't accessible anymore.

I'm more than happy to test for audio improvement!:laugh: I use analog gain at minimum for my power sensitive in ear monitors and light over ear headphones. Currently with Tasker to detect app playback notification to run the audio fix I get momentarily blasted with max gain when pressing play :eek:. Tasker can get delayed under a busy system load too. I need to physically remove or lower the volume before starting any media to avoid that. It also occurs when using skip next media key, I guess this restarts the media stream. Stopping or pausing media for greater than about three seconds resets the amp volume.

EK seems to have tested PDesire kernel audio later but I think that's after the final v3 release. Hopefully some kernel analog gain adjust works out. Even with the current problems I prefer dealing with it for having analog audio quality output rather than any loss or clipping using digital gain alternatively.
[Xperia Z3 Compact Original Android Development] someone755:
Haha it wasn't even an extended warranty, I got it with the standard EU 2 year warranty. Got a motherboard replacement so got the warranty renewed (since the phone had a different IMEI now), and another time I just got a whole new phone -- This last replacement happened in (I think) May this year, so the current unit is pretty much new (aside from the normal wear and tear, and obvious loss of DRM). This thing is gonna last me longer than my old Nokias, lack of updates be damned!

So you're saying PDesire's driver is working? I guess I'll try and bake that in, then, along with one build that includes a downgraded SC driver.
[Xperia Z3 Compact Original Android Development] Infy_AsiX:
And that's an example of how the EU puts human values and care first.

I got one of my motherboards replaced here with Sony Australia's only licensed (somewhat dodgy) warranty repairer. All repairs only grant an extra three month warranty period if normal warranty is expired. Although Australia's consumer laws are fairly good too but not EU good.

I've no idea on PDesire audio. IIRC I had tried it once on some early kernel way back and it lacked the control and effectiveness of fauxsound. I don't think it had been applied yet on any EK release. I know this guy has been playing around a lot with fauxsound and other related kernel audio fixes in attempt to mitigate Z5's audio hiss noise problem https://xdaforums.com/xperia-z5/development/kernel-zachs-kernel-playground-z5-wip-t3340725. I saw he'd been dealing with fauxsound's gain lock issues too. He delves into all sorts of other crazy kernel dev too.

Btw I'm ok if you take your time on fixing audio. I'm ok on my flawed workaround. Prefer more effective use of your time than complicating a rush
[Xperia Z3 Compact Original Android Development] :
Is this kernel compatible with CarbonROM since it is very similar to Lineage?
[Xperia Z3 Compact Original Android Development] stefx98:
Yes, it is :D
[Xperia Z3 Compact Original Android Development] someone755:
Nah I have a few days off this week, reckon I should run an update on my phone anyways haha!

I study electrical engineering anyways so as long as there are no exams around anything is a better way of spending time!

I'm running a July Carbon build on my phone, and Carbon has since only fixed the bluetooth vulnerability. Yes, I know I should pull that patch, I've already heard it from the Carbon maintainer hehe.

What I don't know is whether the kernel works with Lineage anymore. Those guys went from pushing changes into the LineageOS repos to a private repo and I've only heard a bunch of bug reports from that end.
[Xperia Z3 Compact Original Android Development] :
0

I am gonna try it out and I will tell you how it goes.

Edit: For now it works fine and loving the undervolt feature since I have a faulty battery,helps a lot!
[Xperia Z3 Compact Original Android Development] okij:
So the BT vulnerability fix is part of the kernel sources and not of the ROM itself?

If so, I would be happy if you could compile a new release with the fix! Kernel12 r_12 would sound good, what do you think? :cool: