Related
Development Goals:
- stability
- energy savings due to more efficient algorithms (whether theoretical or not is unimportant)
- strictly no overclocking unless approved by the manufacturer or my source base integrates it (also, even if my source base integrates it, expect no support for it)
- no undervolting as well unless the manufacturer approves it since it's relatively pointless IMHO...
- all improvements should require MINIMAL user interaction (e.g. you don't need to do anything except flash the kernel or at the very least use SetCPU or the like to set fixed options)
- stability
Latest Kernel Here
20130625_10XX:
- updated with fix for more recent 4.1.2 Sense ROMs (should fix camera issue)
*unsure if this becomes incompatible with older 4.1.2 Sense ROMs though
20130602_07XX:
- NTFS support
- compiled using 4.8 linaro compiler
- improved workqueue queueing
- sleeper improvements
- responsiveness patches to the frequency controllers
20130531_09XX:
- fixed earpiece volume during calls
20130528_17XX:
- more optimizations (see GitHub)
20130527_18XX:
- more ARM implementations (see GitHub)
20130527_10XX:
- ARM implementations of kernel algorithms (see GitHub)
20130527_09XX:
- compiler optimization flags
20130526_22XX:
- initial version
- uses Linaro compiler
You can find my kernels at:
intersectRaven's Kernels
GitHub is at:
intersectRaven's GitHub
FAQ or something like that:
1.) Camera doesn't work!
- Try this fix from Golv here. This usually occurs on older ROMs.
*Latest 20130625_10XX version should solve this without flashing older camera libs.
Reserved 2
Reserved 3
Nice to see ir taking interest in the One. Truly a great dev
Sent from my Nexus 4 using Tapatalk 4 Beta
Uhhh nice to see you here
intersectRaven said:
Development Goals:
- stability
- energy savings due to more efficient algorithms (whether theoretical or not is unimportant)
- strictly no overclocking unless approved by the manufacturer or my source base integrates it (also, even if my source base integrates it, expect no support for it)
- no undervolting as well unless the manufacturer approves it since it's relatively pointless IMHO...
Click to expand...
Click to collapse
Could you please expound on your statement that undervolting is relatively pointless?
From my experience, undervolting
1. Improves battery life because of lower wattage (Voltage * Amperage = Wattage). Even with a really bad binned CPU, it can still make a difference.
2. Cooler operation. This means longer component life - especially important as this phone is very difficult to repair. Battery is sandwiched so the cooler we can keep the device, the longer the battery will last. (Battery longevity practices could be a topic of it's own)
3. It's Fun! Haha. But seriously. I love to tinker. How low can you go??? It's fun seeing a 25% decrease in voltage and it still run stable
I really like your approach with the rest of your points though. We should have a stable kernel that doesn't have to be tuned or tweaked at all. This however, only suites the majority. The minority may want more. I'm currently in the process of making a kernel with as few restrictions as possible. Except that I will put a ceiling on the maximum voltage (1.25v for the cpu)) because I discourage overvolting beyond spec.
Anyway, thanks for the work. The One is Awesome!
m0nz said:
Could you please expound on your statement that undervolting is relatively pointless?
From my experience, undervolting
1. Improves battery life because of lower wattage (Voltage * Amperage = Wattage). Even with a really bad binned CPU, it can still make a difference.
2. Cooler operation. This means longer component life - especially important as this phone is very difficult to repair. Battery is sandwiched so the cooler we can keep the device, the longer the battery will last. (Battery longevity practices could be a topic of it's own)
3. It's Fun! Haha. But seriously. I love to tinker. How low can you go??? It's fun seeing a 25% decrease in voltage and it still run stable
I really like your approach with the rest of your points though. We should have a stable kernel that doesn't have to be tuned or tweaked at all. This however, only suites the majority. The minority may want more. I'm currently in the process of making a kernel with as few restrictions as possible. Except that I will put a ceiling on the maximum voltage (1.25v for the cpu)) because I discourage overvolting beyond spec.
Anyway, thanks for the work. The One is Awesome!
Click to expand...
Click to collapse
Should have put a qualifier there huh? Anyways, it's pointless from a no tweaking perspective since undervolting may not work for some chips and could cause more trouble (random restarts and the like) than it's worth. It's fun for a tweaker (like when I did something like that for the N1) but not for someone who's the flash and forget type. :fingers-crossed:
Thanks
P.S you missing the ":" on the http link
Really glad to have you here iR. Missed your kernels from my nexus one days with those hybrid AVS kernels.
Camera is buggy
Sent from my HTC One using xda app-developers app
chourmovs said:
Camera is buggy
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
The camera will problably need som librarys, like most other kernels, I think. There is a zip for this in other threads (couldn't find it right away)
chourmovs said:
Camera is buggy
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
What is the problem exactly? Also, is this a custom Sense ROM or stock Sense? Just mentioning that it is buggy doesn't actually help me solve it since there are no bugs in my phone.
Sorry
I m on last ardh by mike86 and when I launch camera, it stuck on black canvas then I ve to hard exit
Sent from my HTC One using xda app-developers app
Intersect my man. Nice to see u in the HTC one forums!
Sent from my HTC One using xda app-developers app
Camera troubles
If somebody have problems with the camera, use the camera Fix from here:
http://forum.xda-developers.com/showthread.php?p=41712563
The bug is due to the old source code, released by HTC
If you are using a ROM based in 1.29.xxx.16 like the most of the new custom Roms flash just after the kernel.
Are the old camera libraries, that works with the Custom kernels.
chourmovs said:
Sorry
I m on last ardh by mike86 and when I launch camera, it stuck on black canvas then I ve to hard exit
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Can you try the link posted below by Maikeu and get back to us whether it fixes the issue?
Maikeu Locatelli said:
If somebody have problems with the camera, use the camera Fix from here:
http://forum.xda-developers.com/showthread.php?p=41712563
The bug is due to the old source code, released by HTC
If you are using a ROM based in 1.29.xxx.16 like the most of the new custom Roms flash just after the kernel.
Are the old camera libraries, that works with the Custom kernels.
Click to expand...
Click to collapse
Posted this in the second post here for future reference.
HI, after fashing this kernel , i cannot hear any sound from call dial ,
008325 said:
HI, after fashing this kernel , i cannot hear any sound from call dial ,
Click to expand...
Click to collapse
Thanks for the heads up! Missed that in my testing. :silly:
*Uploading a fix now.
intersectRaven said:
Thanks for the heads up! Missed that in my testing. :silly:
*Uploading a fix now.
Click to expand...
Click to collapse
Thank you very much i really like this kernel , smooth , cold , save battery
this issue is driving me crazy... no matter what i do i can't get good battery life with cm based roms.... no mater what i try: official, temasek, carbon, paranoid, all have **** battery life that barrely last a day.
i always end up going back to sammy based roms like wanamlite. byt i dont like it!
i greenify apps, disable gps, dormancy, startup apps, what else???
if it matters, i never change kernels..
You aren't experiencing anything new, only Samsung based roms will get good battery life on the S3.
Probably due to a lack of sources
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Probably due to a lack of sources
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
what do you mean?
Samsung don't release their exynos source code properly, so AOSP developers don't have all the information required to get similar performance out of all the hardware components
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Samsung don't release their exynos source code properly, so AOSP developers don't have all the information required to get similar performance out of all the hardware components
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
is there any aosp or aokp based rom that will provide good battery life?
They're all about the same
Sent from my GT-I9300 using Tapatalk 4
they last the same for me with custom kernels.
i wont go back to sammy
Sent from my Nexus 7 using xda app-developers app
To me, any CM/AOSP and any kernel included or custom last about the same, and that is about 40% less then stock samsung rom.
Of course depending on situation...
However I won't be coming back to stock samsung rom any time soon
Agreed, custom kernels help a lot but still not quite as much as stock. Similarly, im sticking with aosp
Sent from my GT-I9300 using Tapatalk 4
Probably irrelevant but i tried the Illusion Rom and it gave me 1d 53h of normal usage whereas sammy barely gets me through the day
Just thought id mention it
1 day + 4 days?
Sent from my GT-I9300 using Tapatalk 4
You are confusing things here...
rootSU said:
Probably due to a lack of sources
...
Click to expand...
Click to collapse
You are confusing things here - the lack of sources is somehow relevant to the kernel part, and generally the best kernels in regard to power consumption are the custom ones (like Perseus, Siyah and so on) - which are precisely started from the sources coming from Samsung.
The ROM part only talks to the kernel part, and once you have the same kernel (like Siyah) talking to both a CM ROM and a Sammy ROM and you get better power consumption in Sammy I don't really see how that can be related to "lack of sources".
rootSU said:
1 day + 4 days?
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
hahahaha sorry my bad:silly:
1d 13h
AthlonGFX said:
Probably irrelevant but i tried the Illusion Rom and it gave me 1d 53h of normal usage whereas sammy barely gets me through the day
Just thought id mention it
Click to expand...
Click to collapse
Yeah sure, I even got on couple of occasion over 2 day and maybe 3-4hrs...
But however on stock with the the approximately same usage I would still have 30-40% more usage time.
xclub_101 said:
You are confusing things here - the lack of sources is somehow relevant to the kernel part, and generally the best kernels in regard to power consumption are the custom ones (like Perseus, Siyah and so on) - which are precisely started from the sources coming from Samsung.
The ROM part only talks to the kernel part, and once you have the same kernel (like Siyah) talking to both a CM ROM and a Sammy ROM and you get better power consumption in Sammy I don't really see how that can be related to "lack of sources".
Click to expand...
Click to collapse
No im not confusing things - but you're over simplifying things. The kernel sources are complete. Siyah uses the samsung kernel sources as a base and it interacts with touchwiz roms perfectly. The same kernel does not interact with aosp roms in the same way.
Set up a touchwiz rom with basic settings and siyah kernel and compare it to aosp with the same basic settings and kernel and touchwiz will win hands down.
Samsungs kernel source may be complete but the exynos and hardware sources are incomplete. That's why an aosp rom camera is much lower quality than samsungs using the same hardware.
Also its worth noting that these dual purpose kernels are built from a mixture of samsung sources and Google sources. Otherwise they wouldn't be able to support 4.2.2 aosp roms...because 4.1 kernels are different to 4.2 kernels...hence no existing kernels can work on 4.2 sammy roms. We need their kernel sources for that, but they will come unlike complete exynos sources.
If you look at the snapdragon variants of the s3, the chipset is well documented so the developer community have much more scope to get comparable battery performance but this isn't an option for us. This is why the developer community here are so frustrated with samsung and the i9300 to the point where team hacksung decided they no longer wish to support cyanogen on exynos devices. We are unable to exploit the hardware to its full potential as we don't have what's required. Developers need to use a lot of guess work to get things working. Our s3 device tree for aosp roms is incomplete and this is samsungs fault for not being forthcoming with their non kernel sources
Sent from my GT-I9300 using Tapatalk 4
You are still confused
rootSU said:
...
Samsungs kernel source may be complete but the exynos and hardware sources are incomplete. That's why an aosp rom camera is much lower quality than samsungs using the same hardware.
...
Click to expand...
Click to collapse
That is completely irrelevant to what it was discussed - and is also false since for instance your own post is somehow trying to suggest that the AOSP camera works perfectly for non-Exynos S3 and works bad for Exynos S3 - once you get your time to check reality instead of propagating stuff you will see that is just another myth and that:
a) the AOSP camera is about as bad for BOTH CPUs
b) the information that is missing has nothing to do with the CPU from Samsung but instead with the camera itself.
And getting back to what this thread was about - POWER CONSUMPTION - the facts show that most CM ROMs have worse power consumption than most Sammy ROMs when both scenarios are run with the SAME KERNEL compiled from sources. A very remote point might be (maybe) made for device-drivers that are blobs (and where custom ioctls maybe are not documented) - but CPU / power management is not one of those! Debunking even further your childish talking point - with the same Sammy ROM the POWER CONSUMPTION is clearly better when running with one of those custom kernels then when running standard Samsung kernel - so any point that somehow any information relevant to power consumption is missing - when actually the custom open-source kernels are demonstrably better in this regard - now stands forever debunked
xclub_101 said:
That is completely irrelevant to what it was discussed - and is also false since for instance your own post is somehow trying to suggest that the AOSP camera works perfectly for non-Exynos S3 and works bad for Exynos S3 - once you get your time to check reality instead of propagating stuff you will see that is just another myth and that:
a) the AOSP camera is about as bad for BOTH CPUs
b) the information that is missing has nothing to do with the CPU from Samsung but instead with the camera itself.
And getting back to what this thread was about - POWER CONSUMPTION - the facts show that most CM ROMs have worse power consumption than most Sammy ROMs when both scenarios are run with the SAME KERNEL compiled from sources. A very remote point might be (maybe) made for device-drivers that are blobs (and where custom ioctls maybe are not documented) - but CPU / power management is not one of those! Debunking even further your childish talking point - with the same Sammy ROM the POWER CONSUMPTION is clearly better when running with one of those custom kernels then when running standard Samsung kernel - so any point that somehow any information relevant to power consumption is missing - when actually the custom open-source kernels are demonstrably better in this regard - now stands forever debunked
Click to expand...
Click to collapse
Without the exynos source the cm kernels can't take full advantage of exynos power saving features..... Simple.
On another note, I suggest you tone down your attitude, and apologise for calling rootSU childish, and don't treat this place like somewhere you can come to wind people up or I will personally introduce you to the moderators
xclub_101 said:
That is completely irrelevant to what it was discussed - and is also false since for instance your own post is somehow trying to suggest that the AOSP camera works perfectly for non-Exynos S3 and works bad for Exynos S3 - once you get your time to check reality instead of propagating stuff you will see that is just another myth and that:
a) the AOSP camera is about as bad for BOTH CPUs
b) the information that is missing has nothing to do with the CPU from Samsung but instead with the camera itself.
Click to expand...
Click to collapse
Wow, way to take something completely out of context and miss an entire point! I didn't even think this was possible. Impressive.
So firstly, I cited the camera as an example of something that relied on Samsung sources along with the exynos chipset (NOT CPU by the way, I haven't use the term CPU, so I guess you just decided to choose that term yourself). The sources are incomplete and the binaries, libs an patches provided are not enough to get everything running on the device as it should be. I, in know way stated or inferred that the camera was better on snapdragon S3's.
The point was we don't have everything in relation to the camera, ergo the camera is not as good as Samsungs. This is not because of the AOSP camera application. Instead it is down to a lack of documentation /sources for the camera HAL. It was a simple example explaining that if we haven't got everything required to run the hardware properly, we can't achieve the same performance. This is obvious with the camera and it's poorer quality images compared to the touchwiz camera using the very same hardware. This is not the case with just the camera though, this extends to all the hardware where we have incomplete information and sources.
xclub_101 said:
the facts show that most CM ROMs have worse power consumption than most Sammy ROMs when both scenarios are run with the SAME KERNEL compiled from sources
Click to expand...
Click to collapse
It is true, with the SAME KERNEL on both platforms, power consumption is different (That's exactly what my post said). However, the dual purpose kernels are compiled from 2 sets of sources, so AOSP and Touchwiz platforms do not overlap 100% with each other (usage wise) in regards to what is compiled into these kernels. Touchwiz ROMs utilise (random guess number to illustrate a point) 90% of whats in the kernel as does AOSP. Meaning there could be a (fictitious) 10% of the kernel exclusively for each platform.
xclub_101 said:
but CPU / power management is not one of those!
Click to expand...
Click to collapse
I didn't mention CPU power management. I did not say that the kernels on AOSP were any different at *managing* the power. Although thanks for bring that up... because now that you mention it, they are.
xclub_101 said:
Debunking even further your childish talking point
Click to expand...
Click to collapse
I don't understand how you can be so audacious to call my talking point childish when you've managed to avoid applying adult levels of reading to my entire post thus far and have taken every point I made conversely to how it was intended.
xclub_101 said:
with the same Sammy ROM the POWER CONSUMPTION is clearly better when running with one of those custom kernels then when running standard Samsung kernel
Click to expand...
Click to collapse
Say what now? If You're saying you think that custom kernels on a Sammy ROM are better than stock kernels on the same sammy rom for power consumption, you'd be right. I never said anything to the contrary of that. I said these custom kernels on a sammy rom are better that they are on an AOSP rom for power consumtion.
xclub_101 said:
so any point that somehow any information relevant to power consumption is missing - when actually the custom open-source kernels are demonstrably better in this regard - now stands forever debunked
Click to expand...
Click to collapse
I really don't think you are managing to get any point you're trying to make across. You're not even arguing against the point I made. Surely a rebutal must directly address my points. You seem to be meandering aimlessly, taking pot shots at what you *think* is my point.
Again, I never said anything about information pertaining to power consumption being missing. My point is simple and basic, so here it is again. We do not have everything to run the hardware optimally. Whenever this is the case, performance suffers. If it is not running as originally intended because sources are missing to provide proper and full support, things are inefficient. Inefficiencies can lead to more power being used than is needed. That's all I was saying. You seem to be going out of your way to argue points I didn't even make, and not even graciously.
Edit>
Link for reading:
http://www.xda-developers.com/android/samsung-aware-of-exynos-documentation-issue/
slaphead20 said:
Without the exynos source the cm kernels can't take full advantage of exynos power saving features..... Simple.
On another note, I suggest you tone down your attitude, and apologise for calling rootSU childish, and don't treat this place like somewhere you can come to wind people up or I will personally introduce you to the moderators
Click to expand...
Click to collapse
I would just put him on ignore. It won't be the first time he's acting like an obnoxious know-it-all and it certainly won't be his last. For all his talk, I haven't seen him contribute anything remotely useful to any sort of development, just pointless ranting, raving and demanding.
So my new redmi 3 is on its way. I've chosen this phone over redmi 4a because of kernel source already available. I love tinkering, modifying and compiling kernel. But before doing so, I need to know which rom are stable for daily usage, with better battery life and overall stability, because I'll be compiling the kernel against the rom and I'll be looking into the kernel source while waiting for the phone to arrive.
From my reading on the threads here so far, I understand that miui roms have better battery life than cm roms, is that still true? Is it noticeable better on miui compared to cm? How about stability, are cm roms still buggy?
Thank you for any feedback :highfive:
LineageOS ?
Inviato dal mio Redmi 3 utilizzando Tapatalk
CM ROMs are really really stable. For me, they feel more stable than MIUI simply because some of the MIUI modifications make some apps bug out (like the battery saver and notification shade).
On the battery side, though, MIUI is way ahead of CM in terms of battery. The hotplug in CM ROMs is INCREDIBLY bad. The one in the latest LineageOS build is always keeping 1 BIG core active (that's the default setting for it) and turns on BIG cores at any touch of the screen. Previous builds had no hotplug, and other CM-based ROMs have some horrible hotplug who turns on little cores and high demand and always keeps the BIG ones active. All of them. Seriously, some ROMs heat up faster when keeping the phone idle with the screen on than MIUI does with hotspot active.
As a battery comparison, MIUI has like 8-9 minutes/1% and CM had 2-3 minutes/1% (SoT) for light tasks. It's now better for CM, like 5-6 minutes, but still a lot behind.
Since you want to modify the kernel, the above battery issue is something you might want to modify, though. You could even get some contributions for LineageOS to make it better for everyone.
vlt96 said:
CM ROMs are really really stable. For me, they feel more stable than MIUI simply because some of the MIUI modifications make some apps bug out (like the battery saver and notification shade).
On the battery side, though, MIUI is way ahead of CM in terms of battery. The hotplug in CM ROMs is INCREDIBLY bad. The one in the latest LineageOS build is always keeping 1 BIG core active (that's the default setting for it) and turns on BIG cores at any touch of the screen. Previous builds had no hotplug, and other CM-based ROMs have some horrible hotplug who turns on little cores and high demand and always keeps the BIG ones active. All of them. Seriously, some ROMs heat up faster when keeping the phone idle with the screen on than MIUI does with hotspot active.
As a battery comparison, MIUI has like 8-9 minutes/1% and CM had 2-3 minutes/1% (SoT) for light tasks. It's now better for CM, like 5-6 minutes, but still a lot behind.
Since you want to modify the kernel, the above battery issue is something you might want to modify, though. You could even get some contributions for LineageOS to make it better for everyone.
Click to expand...
Click to collapse
Thank you for the reply!
The hotplug issue can easily be mitigated by either adding thirdparty hotplug standalone driver or inbuilt in cpu governors. I'm not sure which hotplug implementation does default miui/cm kernel uses, either standalone driver or inbuilt in cpu governor because i dont have the phone yet, but adding thirdparty standalone hotplug driver are definitely in my plan for the kernel. They usually give much more refined control on the cpu core hotplugging mechanism. Plus with thirdparty thermal driver, it should be way better than the default one in those miui/cm kernels.
Actually i like cm based rom better than miui, but reading the cm/mokee/rr threads made me believed that they're more buggy and more battery hungry than miui roms.
nulldash said:
Thank you for the reply!
The hotplug issue can easily be mitigated by either adding thirdparty hotplug standalone driver or inbuilt in cpu governors. I'm not sure which hotplug implementation does default miui/cm kernel uses, either standalone driver or inbuilt in cpu governor because i dont have the phone yet, but adding thirdparty standalone hotplug driver are definitely in my plan for the kernel. They usually give much more refined control on the cpu core hotplugging mechanism. Plus with thirdparty thermal driver, it should be way better than the default one in those miui/cm kernels.
Actually i like cm based rom better than miui, but reading the cm/mokee/rr threads made me believed that they're more buggy and more battery hungry than miui roms.
Click to expand...
Click to collapse
Buggy, not at all. Battery hungry not really, just that MIUI has better optimisations.
My vote is for CM/Lineage. I am currently on Mokee CM/Lineage Marshmallow. It would be great if there was a hotplug option available.
Please build it for CM/LineageOS
It would be nice if you can add better hotplug driver and options to underclock the GPU for better battery life
@nulldash check PM
Hello,
I'm actually vote for LineageOS based ROMs instead because the kernel source is complete. Xiaomi's official source code doesn't include Prima WiFi driver.
OP, choice is on your hand, and up to you. We could only expect for things to come.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
Hello,
I'm actually vote for LineageOS based ROMs instead because the kernel source is complete. Xiaomi's official source code doesn't include Prima WiFi driver.
OP, choice is on your hand, and up to you. We could only expect for things to come.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
i actually already expected that their original source are incomplete and broken like what they always did with their kernel source release, hence i'm syncing cm14.1 kernel source. unless cm did major changes in their source especially in graphic driver, the kernel would theoretically boot on any lp, mm and n roms if using anykernel zip installer.
already succesfully built the kernel but my phone didnt arrive yet to test :laugh:
nulldash said:
already succesfully built the kernel but my phone didnt arrive yet to test :laugh:
Click to expand...
Click to collapse
Lol,
As for AnyKernel2 template, we need to remove BusyBox in order for the template to work correctly. I've uploaded the modified one if people want to use it as the base (it's also a part of my build script).
Sent from my ASUS_Z00A using XDA Labs
I have always wondered how to achieve great camera results with custom Roms. I know it is kind of off-topic, but it would be nice to have a kernel with xiaomi's camera source for lineageOS etc. Though, I have no idea if the kernel source release included camera sources.
George_ioannidis said:
I have always wondered how to achieve great camera results with custom Roms. I know it is kind of off-topic, but it would be nice to have a kernel with xiaomi's camera source for lineageOS etc. Though, I have no idea if the kernel source release included camera sources.
Click to expand...
Click to collapse
I think no. Blame Xiaomi why they release incomplete sources
Sent from my ASUS_Z00A using XDA Labs
I prefer MIUI and I would appreciate the function DT2W (double tap to wake).
The most stable rom I've ever seen is RRemix. Battery life is great and there are no bugs (at least I did not see)
vesi said:
I prefer MIUI and I would appreciate the function DT2W (double tap to wake).
Click to expand...
Click to collapse
There is already a kernel for miui with dt2w. I would like one for lineage with dt2w
Enviado desde mi Redmi 3 mediante Tapatalk
could anyone upload, or just paste the content of /system/etc/init.qcom.post_boot.sh please? if want to paste please use code tags to preserve whitespace
nulldash said:
could anyone upload, or just paste the content of /system/etc/init.qcom.post_boot.sh please? if want to paste please use code tags to preserve whitespace
Click to expand...
Click to collapse
I'm on lineage official nightly, can't find what are you looking for
ainurrofiq said:
I'm on lineage official nightly, can't find what are you looking for
Click to expand...
Click to collapse
It's on the root of the ramdisk.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
It's on the root of the ramdisk.
Click to expand...
Click to collapse
So I have to unpack boot.img first?
I'll send boot image for you
---------- Post added 26th January 2017 at 12:23 AM ---------- Previous post was 25th January 2017 at 11:56 PM ----------
ainurrofiq said:
So I have to unpack boot.img first?
I'll send boot image for you
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B4H7TUQI5FnxSU8tZEVKam83a0E/view?usp=sharing
Introduction
Hello everyone! Some of you might recognize me from the Xthermal Fast Charge thread, where I had earlier created and posted unified zips for modifying the stock thermal config file on the Nexus 6P, combining the work of two different mods, namely CTTMod and Xthermal Fast Charge Mod.
Since I was earlier maintaining my unified zips in the Xthermal Fast Charge Mod thread, I have now decided to create a separate thread for them since there is still interest and I don't want to unnecessarily clutter somebody else's thread. Let's get straight to it then!
Detailed Information
CTTMod - Thread Link
When CTTMod was initially released, it changed certain values in Nexus 6P's stock thermal file to raise the temperatures at which the phone would start to use thermal throttling. This change led to an increased overall performance and the phone could be used for a longer period of time without any crippling of performance due to thermal throttling, at the cost of heat. Therefore, after using this mod, the phone would feel slightly warmer as compared to how it would've felt if this mod had not been used, but with higher sustained performance.
Xthermal Fast Charge Mod - Thread Link
When Xthermal Fast Charge Mod was initially released, it also changed certain values in Nexus 6P's stock thermal file to raise the temperatures which prevented the charging current to exceed a certain value (usually ~1500 mAh to 1700 mAh) even though the stock OEM charger was capable of delivering a current upto 3000 mAh. This change led to an increased average current drawn (~2600 mAh to 2800 mAh), thereby leading to a decrease in the time taken by the phone to charge, again, at the cost of heat. Thus, a faster fast charge.
Unified Thermal Mod
Since both the base mods target the same stock thermal file, they can't be used together and using one would override the changes done by the other. In other words, one can only use CTTMod or the Xthermal Fast Charge Mod, exclusively. My unified thermal mod provides a workaround for this by taking the best from both of the above mentioned mods and combining their changes into one file, packaged into a Magisk module/TWRP flashable zip, so that one can take the advantage of both, increased performance due to an increase in thermal throttling temperature limits as well as a faster fast charge.
Compatibility
Device(s)
Nexus 6P
ROM(s)
All ROMs
Android Version(s)
Android Marshmallow 6.x.x
Android Nougat 7.x.x
Android Oreo 8.x.x
Android Pie 9.x.x
Android Q 10.x.x
Download
Direct Link
Important Read-Me Points
Installation/Uninstallation
In case you wish to install the modified libraries directly in the system partition and not as a Magisk module, then add "sysover" (without the quotes) to the zip name and flash it via TWRP.
The zip will abort the installation if you try to flash it on any other device except the Nexus 6P and if you aren't running Android Marshmallow, Nougat, Oreo, Pie or Q.
The zip auto-detects your Android version and installs the correct modified thermal configuration file automatically.
To uninstall the mod, just reflash the zip via TWRP and it will undo any changes it did (whether installed as a Magisk module or directly in the system partition).
General
The mod only works with the stock OEM charger. If you're using a third party charger (irrespective of the fact whether it supports Qualcomm QuickCharge or any other fast charge capability) this mod won't work.
The lower your battery percentage is, the faster your phone will charge, i.e. as the battery charge percentage increases, the current drawn by the phone will decrease. This is stock behaviour.
The mod doesn't change the USB charge current. That is controlled by the kernel.
Regarding the thermal driver, it is preferred that you enable msm_thermal and disable core_control for effective results. However, if doing that causes issues for you (for example, cores don't come online automatically after going offline while using msm_thermal), then disable msm_thermal and enable core_control via a kernel tuning app, like EX Kernel Manager.
If possible, avoid playing games/use performance heavy apps while the phone is charging. Doing so won't cause any issues, but it is preferred not to do so while the phone is on charge.
Disclaimers
I am not the original developer of the base mods used, i.e. CTTMod and Xthermal Fast Charge Mod. I merely combined the two since they couldn't be used together. I take no credit for the original work. Please direct all your thanks and/or donations towards @Robshr and @ravinder0003, the original developers of the mods.
You are doing this at your own risk. I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you are unsure of how to go about something.
Thanks To
@Robshr, for his work on the original CTTMod
@ravinder0003, for his work on the original Xthermal Fast Charge Mod
@Zackptg5, for Unity Installer and all the work he's ever done for the community
@topjohnwu, for Magisk and all the work he's ever done for the community
All of you guys for viewing this thread and using the mod
Changelog
v1.0 - Initial release for Magisk v14.0
v1.1 - Updated to include changes from CTTMod's latest release for Android 8.x Oreo
v2.0 - Update for Magisk v15.0
v3.0 - Update for Magisk v17.0
v4.0 - Updated the zip base to the Unity Installer template
v5.0 - Added support for Android 10, updated the base template to Unity v4.4 and EOL update
OP Information
Thread Update Information
Created: September 15, 2017
Last Updated: September 29, 2019
Source Code
GitHub
@shadowstep
So you are here...
Nice mods work great
phantom146 said:
@shadowstep
So you are here...
Click to expand...
Click to collapse
Haha! I'm actually still there, but decided to keep this going even though I don't have the device anymore, but have a few testers who are available to help, so why not!
adame09 said:
Nice mods work great
Click to expand...
Click to collapse
Thank you!
Thanks for this mod! Working great on Oreo (superXE Rom with ElementalX).
Working perfect here too. Thank you
Sent from my Nexus 6P using Tapatalk
@shadowstep I would really love to try this but unfortunately, I live in a tropical country where we have above normal temperatures. The external temperature is hot enough, and if I did this, I'm risking global warming with my angler
phantom146 said:
@shadowstep I would really love to try this but unfortunately, I live in a tropical country where we have above normal temperatures. The external temperature is hot enough, and if I did this, I'm risking global warming with my angler
Click to expand...
Click to collapse
Haha, come on now, I'm not far from the Philippines (I'm in India) and I gave it a shot. Jokes apart, I know what you mean man. For us, in summers especially, this might not be the best mod to use on a daily basis, more so if the usage is heavy. In winters, however, it's a different story entirely, and I found this mod really helpful.
shadowstep said:
Haha, come on now, I'm not far from the Philippines (I'm in India) and I gave it a shot. Jokes apart, I know what you mean man. For us, in summers especially, this might not be the best mod to use on a daily basis, more so if the usage is heavy. In winters, however, it's a different story entirely, and I found this mod really helpful.
Click to expand...
Click to collapse
Back at you, we don't have winter :laugh:
Right now i'm not gonna bake my already half-baked phone and almost dying battery. I'd stay off of thermal mod for now but im really eager to try cttmod out.
phantom146 said:
Back at you, we don't have winter :laugh:
Right now i'm not gonna bake my already half-baked phone and almost dying battery. I'd stay off of thermal mod for now but im really eager to try cttmod out.
Click to expand...
Click to collapse
Haha, oh we do, chilly ones!
Also, you might want to consider a battery replacement if you plan on keeping your 6P for some time. I got it done from the Huawei Service Centre in my area, and the original one didn't cost a bomb at all. After the change, my SOT started averaging 4.5-5 hours (up from 2.5-3 hours).
shadowstep said:
Haha, oh we do, chilly ones!
Also, you might want to consider a battery replacement if you plan on keeping your 6P for some time. I got it done from the Huawei Service Centre in my area, and the original one didn't cost a bomb at all. After the change, my SOT started averaging 4.5-5 hours (up from 2.5-3 hours).
Click to expand...
Click to collapse
Yeah i've really considerd replacing it and I've heard its quite cheap. Though last april or so I've heard somebody talking about battery replacement on PH and huawei said that they're running out of "stock" with angler. So I guess I better check it out. I might not be buying anyreplacement sooner or later but I have plans next yr to buy the OP6 or Pixel 2.
phantom146 said:
Yeah i've really considerd replacing it and I've heard its quite cheap. Though last april or so I've heard somebody talking about battery replacement on PH and huawei said that they're running out of "stock" with angler. So I guess I better check it out. I might not be buying anyreplacement sooner or later but I have plans next yr to buy the OP6 or Pixel 2.
Click to expand...
Click to collapse
Yep, like I said before, it's not expensive, so if you manage to get your hands on one, definitely go for a replacement. Hopefully, some are still available and not out of stock. Also, I'm not too keen on Pixels anymore, seeing how comparatively difficult it is for developers to get stuff working on it + they cost a bomb! That's why I went for OnePlus 5. Had Google stuck with the Nexus line-up, I would've never bought anything else to be honest, but well..
shadowstep said:
Yep, like I said before, it's not expensive, so if you manage to get your hands on one, definitely go for a replacement. Hopefully, some are still available and not out of stock. Also, I'm not too keen on Pixels anymore, seeing how comparatively difficult it is for developers to get stuff working on it + they cost a bomb! That's why I went for OnePlus 5. Had Google stuck with the Nexus line-up, I would've never bought anything else to be honest, but well..
Click to expand...
Click to collapse
Yep if only they continued nexus, I'm gonna be fanboy on nexus forever lol. Well im interested at nokia right now as well as android one, hope they get a good community tho
I'm on oreo stock rom but using Elemental kernel, which versión should I use? The Overclocked one or the stock frecuency kernel?
phantom146 said:
Yep if only they continued nexus, I'm gonna be fanboy on nexus forever lol. Well im interested at nokia right now as well as android one, hope they get a good community tho
Click to expand...
Click to collapse
Me too! :highfive: Coming to Nokia, they're definitely upping their game, but I'm not sure about the developer backing it will get vis-à-vis OnePlus; the latter has the best developer backing after Google. Android one is relatively new, so let's see where does it go. The new Mi A1 could be start of something great.
jsecruzvalencia said:
I'm on oreo stock rom but using Elemental kernel, which versión should I use? The Overclocked one or the stock frecuency kernel?
Click to expand...
Click to collapse
If while flashing the kernel, you selected the overclocked frequencies for your cores, then use the overclocked oreo variant of the mod. If you didn't make any changes in the frequency screen/aren't sure if you're overclocked or not, just use the normal oreo variant and you should be good.
I notice higher temperatures as expected.
Actually my N6P reached 44.5C, are we fine?
I am talking about battery temperature
Actually I just answered my question, flashing Oreo stock throttling .zip
Thanks for the mod, no offence.
Have fun, George.
How to know if my kernel is overclocked or not? I am using Flash kernel v2.5
teohguangli said:
How to know if my kernel is overclocked or not? I am using Flash kernel v2.5
Click to expand...
Click to collapse
Not overclocked.
Pipiou211 said:
I notice higher temperatures as expected.
Actually my N6P reached 44.5C, are we fine?
I am talking about battery temperature
Actually I just answered my question, flashing Oreo stock throttling .zip
Thanks for the mod, no offence.
Have fun, George.
Click to expand...
Click to collapse
Yes, that is expected, because the mod increases performance at the cost of heat, so temperatures will be slightly higher as compared to stock. It's been mentioned in the OP as well.
Also, no offence taken, at all. Feel free to use/not use the mod, whatever you feel comfortable with. Thanks for stopping by!
teohguangli said:
How to know if my kernel is overclocked or not? I am using Flash kernel v2.5
Click to expand...
Click to collapse
You can use a kernel manager app like EXKM or Kernel Adiutor to check that. If the maximum CPU frequencies for the little and big cluster are 1708 MHz and 2054 MHz, respectively, then you're running an overclocked kernel. However, if they are 1555 MHz and 1958 MHz, respectively, then you're running a non-overclocked/stock frequency kernel.
I know asking for ETA isn't allowed but could you do a fast charge only version for Oreo? I really dislike the thermal mod but would love to have the fast charge one
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
~~A custom kernel for (most) V20 variants~~
Swan2000 is an android kernel based on the very latest Qualcomm 4.4 CAF sources for MSM8998 (which is also compatible with MSM8996), aiming to bring new features and updates over official kernels, and also improve LGE MSM8996 devices with some extra tuning, fixing and additional features tailored specifically for their performance characteristics and feature sets, while trying to maximize the battery life and responsiveness of those devices at the same time.
Its name comes from a merge between Swankernel(@AShiningRay) and mk2000(@askermk2000), as they were the main heads behind this kernel's development.
__Disclaimers__First and foremost: DO NOT bother official LineageOS threads with bugs if you're using this kernel, only bug reports with logs pointing to the official kernel will receive support there!!!
Now for the usual XDA disclaimer:
We are not responsible for bricked devices, dead SD cards, tactical nukes being set up (with the V20 you never know), alien invasions, google spying on you, or you getting fired because the alarm app failed after you removed all traces of google services from your phone so that google couldn't spy on you.
YOU are choosing to make these modifications, and if you point the finger at us for somehow messing up your device despite YOU being the one explicitly making these modifications, we will laugh at you.
DO NOT expect support on official ROM threads if you are running this kernel. Also don't try to hide it because we will know, and we will also laugh at you.
Your warranty is most likely void at this point anyway, but nevertheless, it is now definitely void if you tamper with any part of your device / software.
Click to expand...
Click to collapse
__Which V20 variants/models does this kernel support?__
The kernel currently supports the following V20 variants:
H910 / H915
H918
H990(DS / TR)
LS997
US996
US996D(Dirtysanta)
VS995
Those seem to cover every rootable variant thus far, but additional variants can be added in case a breakthrough happens on F800 for example.
__What does this kernel intend to achieve?__
The main goal here is to have a kernel that not only has extra features and improvements, but is also clean and concise, having only features that are truly needed from a kernel that will run alongside a Android 12.1-based ROMs and beyond.
This kernel does have a battery life bias, but will still scale up to maximum performance when needed. Gaming variants basically mean that the kernel comes overclocked by default, no additional tweaking is needed.
__Does it have any features over official?__
Yes, quite a few. The kernel is divided into two variants and their respective gaming modes, here are the features all variants have over Lineage's 4.4 kernel:
GPU and CPU/Cache Undervolt for better power efficiency on load.
Almost no unnecessary debug flags on the kernel for better kernel performance.
USB Fast Charge.
KCAL Control (although not really needed for LOS, other custom roms might surface with the need for this)
Multiple cherry-picks from different msm8996 sources with fixes and improvements to the kernel.
Built with newer GCC toolchains (GCC 12) with optimized inlining and other compiler optimizations for 8996
Updated LZ4 libraries for faster ZRAM
Cryptographic function optimizations, slightly improving the phone's performance when calculating hashes and so on.
The Extreme variant really only has one extra feature over the Safe variant, that being:
Stronger Undervolts (i'm talking about borderline unstable undervolts here, so i really recommend that you flash the Safe variant first).
The "Gaming" versions are basically overclocked variants of Safe and Extreme, which means they also only differ in undervolt levels.
__Are there any bugs?__
As of now, the only actual kernel bug the V20 and G5 have comes down to their insanely over-engineered USB ports. You can't use them as a MacBook by plugging a fully powered hub into them like you could in 3.18 yet.
__Download & Installation__
The folders containing each kernel variant can be found here (use Ctrl+F to search for your phone model and kernel variant, there's just too many versions to neatly organize in folders and such as it would take too much time):
GITHUB KERNEL RELEASES
To install the kernel, it's the standard procedure:
Download the kernel you want for your device
Place it into the phone's storage
Boot into recovery, select it and then flash
Wipe Dalvik Cache (optional, you only need to wipe it if you face random Force Closes, but it is a good practice anyway)
Reboot.
Use AIDA64, go into the "Android" tab and look for "Kernel Version", where it should show "4.4.302-Swan2K-...".
Enjoy the experience!
As usual, we do not take responsibility if you fail to make backups before flashing this kernel, you have been warned!
__Changelog__
Spoiler: Changes done in recent versions:
*********** Swan2000 V0.1-BETA8+ ***********Small release with BCL tweaks for all devices, some msm8998 merges and minor hotspot fixes for G6.
_________________________________________
*********** Swan2000 V0.1-BETA8 [First Release] ***********This one is pretty straightforward: Basically lineage's kernel with all the features and improvements listed above, plus a few additional tweaks that would take too much space to note.
__Closing notes__
If you have any suggestion or idea that can possibly improve the kernel, do not hesitate to share, i will try to implement it when time allows it. If there are any problems that only happen on this version of the kernel, submit a log and i'll try to look at it.
I'll say it again: Please DO NOT bother official Lineage with bugs if you're running this kernel, only lineage's official kernel is supported over there.
___________________________________
The kernel's source code can be found here. It is also shared between G5 and G6!
And last but not least, special thanks to those that helped this major revamp on LGE_8996 become a reality by developing, testing, and even helping things indirectly, the dev community on all three phones had to come together for this:
@xxseva44
@npjohnson
@askermk2000
@thewolfsvk
@ROMSG
@bernardobas
@VortexHD
@Michele_Catella
And many, many others
Reserved.
Might need an additional post at the top later.
First of all thanks! To everyone involved, you guys rock!
A little tangent (bear with me for a while, please)
I had an OP3 before this V20, and like some "developers toy's" received a good attention for some time that phased out and was replaced by many more quickly than his predecessors in my opinion.
Besides SultanXDA Lineage 14 that he customized the kernel+ROM (achieving 6h screen time with ease), the thing that had me impressed was EAS and was beautifully implemented by mcdachpappe in this kernel. That really was responsive and also have some endurance. Other device that I still have it's my LG G4 and the devs ported so many kernels (I used blu_active most of all), but I didn't have the time needed to tweak.
After that detour, I would like to know: (no pressure, complains, just curiosity from my part)
1) EAS it's still relevant? Did you have any plans to implement it? Since the OP3 "has the same msm8996" could it be ported or benefit from this governor?
2) I noticed that you have on this kernel the "basic" governors : interactive, conservative, ondemand, userspace, powersave, performance. Do you consider other addition? Or it's an unnecessary problem?
3) I would love to not need any app than necessary, but to reduce some "image retention" there are many posts to help mitigate this issue, but the configuration it's for some app and trying to replicate in the system settings won't have near the results. Do you have any suggestion?
4) Any recommendations for applications to adjust the kernel? I used many moons ago the Kernel Audtor but the most close replacement that I'm aware it's the SmartPack-Kernel Manager?
5) A feature that always intrigue me in some Sony devices was the ability from stock to limit/manage the battery, "setting a max capacity" to stop charging at determined percentage, theoretically "extending" the life-span. How demanding, and it would benefit our devices this feature?
6) You mention the USB issue. Right now I don't have any hub and would be a nice thing in the future to plug an ethernet cable, be able to use a mouse + keyboard in some situation, and technically the V20 has HDMI out. But in this new kernel the problem comes only to being able to charge with any hub or I didn't get properly what the exact problem was?
7) The "only bug" on my H990DS that I encountered so far it's when I installed the SmartPack-Kernel Manager and in the "Overall Statistics" the CPU temperature are "-4.0°C" (I didn't install this app before with the stock kernel because I didn't needed this app). So how to properly report it?
I can't believe how much more responsive the device is, looks like magic!
dextructor said:
First of all thanks! To everyone involved, you guys rock!
A little tangent (bare with me for a while, please)
...
Click to expand...
Click to collapse
1 - No, not really. While EAS was included in this kernel's earlier versions, we opted to drop it from both official and Swan2000 when shipping lineage. EAS just doesn't bring that many benefits, if any, to msm8996 and 8998 devices when the device sources are already well tuned. And that's what we saw by going back to HMP: No significant perf/power difference on V20, G5 or G6, although the results favored HMP a bit since EAS boosted too much.
2 - No other CPU governor additions are planned, interactive can be configured to do pretty much everything you need (our device trees on lineage already have it pretty balanced), and if you can use conservative if a inherent battery life bias is needed.
3 - Lineage 19.1 has LiveDisplay support by default(Settings->Display->Color->LiveDisplay), not needing any kernel additions on that front. Those guides use KCAL control, which is there on the kernel in case other custom roms show up without LiveDisplay. Personally i use a LiveDisplay Color Calibration profile of 94%R, 90%G, 92%B to nearly eliminate image retention on mine, though that's because my display has a green tint ever since i bought it, might not be the same for you. Intensity and contrast values don't seem to affect retention that much so it's up to you.
4 - SmartPack is pretty much the continuation of Kernel Adiutor in case you really need a kernel manager.
5 - It is possible to do that, but requires ROM integration and can also be buggy sometimes (my Xiaomi Mido has that feature on its custom rom and sometimes it simply doesn't charge if i enable the battery limit and it hits the threshold, only charging again after a cold reboot). Since the V20 has a user-replaceable battery, that's not a big deal.
6 - The bug is not on the usb features themselves. HDMI support is perfect, as is OTG, mouse and keyboard as well (and i also think ethernet). The problem arises when fully powered hubs come into play: The phone simply refuses to charge at the same time it's in Host/OTG mode because we didn't fully figure out USB-PD on the new kernel just yet, and as a result powered hubs don't work, though you can still use simpler hubs that don't need additional power, or charge the phone. Since the V20 and G5 are pretty much the only 8996 devices on 4.4 that have this fully-featured usb port, it's hard to conceptualize a fix that doesn't break something else.
7 - SmartPack reporting incorrect cpu temps has always happened in 4.4. Apparently it's a bug in the app because AIDA64 doesn't suffer from the same issue, nor does CPUFloat (although CPUFloat does seem to invert GPU and CPU temps in some roms). I guess that's because there aren't that many Snapdragon 82x devices running 4.4 so most apps focus on 3.18's sensor configuration.
AShiningRay said:
1 - ...No significant perf/power difference on V20, G5 or G6, although the results favored HMP a bit since EAS boosted too much.
2 - No other CPU governor additions are planned
Click to expand...
Click to collapse
Beautifully explained, much more than I needed, and very well tuned.
AShiningRay said:
3 - Lineage 19.1 has LiveDisplay support by default(Settings->Display->Color->LiveDisplay), not needing any kernel additions on that front
Click to expand...
Click to collapse
I was aware, but thanks for the reminder, and your settings. When I was using the OP3 in the beginning I disliked very much the punchy color calibration that was used until they released "sRGB" profile that I used ever since (I guess that I couldn't have a Samsung device with their saturated profiles). And I tried to replicate some of the configs but the values don't match if you don't try to calculate. For example I liked this config that I copied from this video description and give me an very soft and neutral color spectrum (too bland for some, and with more time I would search for how to improve it):
Red 256 | Green 241 | Blue 226
Minimum RGB Value 0 | Saturation Intensity 12 | Screen Hue 0
Screen Value 128 | Screen Contrast 128
The color values are really straightforward, but "Minimum RGB"? The "Saturation Intensity" it's separated in 2 distinct values like "Saturation" and "Intensity"? Do you understand the difference?
AShiningRay said:
4 - SmartPack is pretty much the continuation of Kernel Adiutor in case you really need a kernel manager.
5 - requires ROM integration and can also be buggy sometimes
Click to expand...
Click to collapse
Clear enough, it was just as a suggestion.
AShiningRay said:
6 - The phone simply refuses to charge at the same time it's in Host/OTG mode because we didn't fully figure out USB-PD on the new kernel just yet
Click to expand...
Click to collapse
No problem, I was just mention because my ex-wife had a Pixel XL and I bought to her this USB Hub (UCN 3273) and everything worked (except HDMI because Google intentionally disable HDMI out just to sell more Chromecasts) including PD charging. It was used with ethernet (because a real gigabit connection beats many wifi speeds and consistency, and spots with bad coverage) and even an external USB mic to make video-calls (that without powering the HUB won't work). OK if this features could come to the device, until then no need to rush.
AShiningRay said:
7 - has always happened in 4.4
Click to expand...
Click to collapse
Ok, I didn't know. It's better to know than make trouble unnecessarily.
I remember reading about low volume on audio recording and decided to test on both OP3 and H990DS with Audio Recorder (M4a +48kHz +256kbps + stereo settings). Both devices recording the same initial 20s dialogue from this video at the same distance from the speaker of my computer but very different results.
I even analyzed in Audacity on the computer and it was indeed not only much lower, but was mono instead of stereo.
How can I help you guys properly identify this problem?
Thanks again!
dextructor said:
The color values are really straightforward, but "Minimum RGB"? The "Saturation Intensity" it's separated in 2 distinct values like "Saturation" and "Intensity"? Do you understand the difference?
Click to expand...
Click to collapse
Minimum RGB is pretty useless, it was supposed to deal with the black levels (in essence, how dark should the darkest pixels be on the screen) but never seen it do anything useful on any of my phones, OLED or not.
As for Saturation and Intensity being separated... "Saturation Intensity" is just "Saturation" on LiveDisplay, while "Intensity" on LiveDisplay is the same as "Screen Value", which dictates the overall brightness of the screen's pixels (just don't go too far on this one, or else you'll get overblown whites, also balance it with contrast and you get a nifty max brightness boost for free).
dextructor said:
No problem, I was just mention because my ex-wife had a Pixel XL and I bought to her this USB Hub (UCN 3273) and everything worked (except HDMI because Google intentionally disable HDMI out just to sell more Chromecasts) including PD charging. It was used with ethernet (because a real gigabit connection beats many wifi speeds and consistency, and spots with bad coverage) and even an external USB mic to make video-calls (that without powering the HUB won't work). OK if this features could come to the device, until then no need to rush.
Click to expand...
Click to collapse
It might come at some point since we really want to fix every major hardware feature of all three phones, though it's one of the peskiest issues to deal with on the kernel side since we have 5 or 6 usb drivers that communicate with each other.
dextructor said:
I remember reading about low volume on audio recording and decided to test on both OP3 and H990DS with Audio Recorder (M4a +48kHz +256kbps + stereo settings). Both devices recording the same initial 20s dialogue from this video at the same distance from the speaker of my computer but very different results.
I even analyzed in Audacity on the computer and it was indeed not only much lower, but was mono instead of stereo.
How can I help you guys properly identify this problem?
Thanks again!
Click to expand...
Click to collapse
AFAIK that's a known problem on AOSP roms as a whole (happens in 3.18, happens in 4.4, not kernel-side), mics on V20 and others just don't work as intended compared to stock. It's on the list of things we're gonna look at, but it's not a priority right now because we're trying to sort out Bluetooth in order to bring Lineage 20 in.
Once we start debugging the mics, i'll see if i can get one of our rom-side devs to approach you with more info if you're still available by then. Thanks!
AShiningRay said:
Once we start debugging the mics, i'll see if i can get one of our rom-side devs to approach you with more info if you're still available by then. Thanks!
Click to expand...
Click to collapse
No problems, you guys are really good at improving/fixing this devices. And I'll be here if I can help in anyway.
Very good explanations, really good knowledge on this thread. Thanks!
dextructor said:
No problems, you guys are really good at improving/fixing this devices. And I'll be here if I can help in anyway.
Very good explanations, really good knowledge on this thread. Thanks!
Click to expand...
Click to collapse
Yea in regards to the mic level, this has been a known issue on the v20. However i was not aware of it recording in mono, that is very odd. The level issue is mixer path related, but the mono recording, i'm not too sure. I will admit, it may be a while until this issue is fixed as we're heading into los 20 and getting that ready. But this will definetly get looked at. Could you grab logs of when you record? I wand to see what the audio hal is doing and how it sets up for recording.
xxseva44 said:
Could you grab logs of when you record? I wand to see what the audio hal is doing and how it sets up for recording.
Click to expand...
Click to collapse
Since I couldn't download the latest build because the page error 502, I clean flash 2023-04-23 build and only install the Magisk so I could get an dmesg and the Recorder app mentioned before.
Have 2 sets of archives, the stock kernel and the Swan2000 with logcat and dmesg.
If I can provide more help, please just ask.
What's the significance of H830, H850, H870?
andruyd said:
What's the significance of H830, H850, H870?
Click to expand...
Click to collapse
Those are G5 and G6 models. This kernel supports all three LGE_8996 phones, we just separated the threads for each of them.
@AShiningRay
I didn't see anything explicitly on this thread or in the github page, but it's BCL implemented on this new Kernel or it depends also from the ROM?
@xxseva44
Was the logs that I send any useful to help diagnose the audio recording issues?
Thank you all!
dextructor said:
@AShiningRay
I didn't see anything explicitly on this thread or in the github page, but it's BCL implemented on this new Kernel or it depends also from the ROM?
Click to expand...
Click to collapse
BCL is enabled by default on all 4.4 builds since it's nowhere near as aggressive as 3.18, but you can disable it from userspace but it requires root... though i don't really recommend doing that.
dextructor said:
@AShiningRay
I didn't see anything explicitly on this thread or in the github page, but it's BCL implemented on this new Kernel or it depends also from the ROM?
@xxseva44
Was the logs that I send any useful to help diagnose the audio recording issues?
Thank you all!
Click to expand...
Click to collapse
Ah yea, so far i haven't found anything odd. If possible, can you reboot, record something and then send the logs right after? It'll help with locating the issue if that's all that audio did the entire time the device was on.
AShiningRay said:
BCL is enabled by default on all 4.4 builds
Click to expand...
Click to collapse
So even the stock Lineage Kernel and the Swan2000 has BCL enabled, it's that right?
xxseva44 said:
If possible, can you reboot, record something and then send the logs right after? It'll help with locating the issue if that's all that audio did the entire time the device was on.
Click to expand...
Click to collapse
I'm sorry, but I didn't fully understand what you requested me. So let's recapitulate:
1) Reboot
2) Record
3) Log (Only logcat or with dmesg as well)?
Little off-topic: I noticed a strange behavior last night, when for the first time I tried to record an video with GCam (if you/anyone have another version, build to suggest, I'll be grateful) and no audio at all. So I opened the stock Camera and the audio was loud and clear. And with the stock audio recorder was also very low volume as with the other app.
Are those things even remotely related?
Thanks!
dextructor said:
So even the stock Lineage Kernel and the Swan2000 has BCL enabled, it's that right?
Click to expand...
Click to collapse
Yes
dextructor said:
So even the stock Lineage Kernel and the Swan2000 has BCL enabled, it's that right?
I'm sorry, but I didn't fully understand what you requested me. So let's recapitulate:
1) Reboot
2) Record
3) Log (Only logcat or with dmesg as well)?
Little off-topic: I noticed a strange behavior last night, when for the first time I tried to record an video with GCam (if you/anyone have another version, build to suggest, I'll be grateful) and no audio at all. So I opened the stock Camera and the audio was loud and clear. And with the stock audio recorder was also very low volume as with the other app.
Are those things even remotely related?
Thanks!
Click to expand...
Click to collapse
All logs, grab them via adb right after running the recording. As for the wonky audio levels in different apps, yes they are related. Something does not seem to be right in terms of the mixer levels so I'll need you to log all the apps that behave weird so i know what routes to look at.
So far so good. I've only had one random reboot and that was on the Safe kernel. I'm now on the Extreme kernel and no issues so far. My H990 definitely doesn't get as warm compared to the stock kernel and it still looks and feels snappy.
xxseva44 said:
I'll need you to log all the apps that behave weird so i know what routes to look at.
Click to expand...
Click to collapse
Ok I'll do probably today or tomorrow and post it later.
Since I don't play any games anymore on my phone since Clash Royale many, many years ago, the most intensive thing that I do it's occasionally video-calling via Telegram FOSS. But let me tell about my history with this V20 H990DS
I bought this device used, and the seller said that the battery needed to be replaced, and randomly it gave me green-screen reboot messages when below 30% and the thermals wasn't great because it was the end of summer here in Brazil. Since everywhere that I searched about buying new LG batteries anyone tells that it's hard to find a real original and reliable I decided to try this one from Aliexpress, and also ordered some copper shims (0.5mm and 0.6mm) to put thermal paste and improve things. And a 128GB SDcard since it was cheap now (compared to years ago... I tested with H2testw and it works perfectly)
So the battery arrived first, and even before it arrived I installed the Lineage 19 and with the new 4.X Kernel it almost never gave me more green-screen reboots, but few random reboots when below 35%.
With Lineage 18 + SwanKernel Extreme gave the most stable scenario but only one time I did try to video-call with Telegram and it went stable, but slow (probably due underclock, maybe?)
But last Friday using the new battery I tried to video-call through Telegram some relatives that live abroad, and with only 5 minutes of calling it rebooted and was warm-ish? So the copper shims arrived early that week and I decided to do the thermal mod this week.
With the 0.6mm it pressed the LCD giving a darker spot, so I decided to replace with the 0.5mm, put new thermal paste and try again... So no dark spot on the screen.
I installed Telegram on other computer and tried to call and test the V20, but it still reboots after some time, but the strange thing it never reaches 62 or higher.
I tried the CPU Throttling Test to test the thermals and it barely reaches 60 with the Extreme+Gaming or with only Extreme as well.
So after all of this, I remember that H990DS have the reputation for drawing a lot of power:
1) Even a "compatible non OEM" battery can't provide what this device demands in terms of power consumption?
2) Having a dual-sim gives me freedom in terms of separate personal-work calls etc and not having to carry 2 phones. Could a dual sim card adapter could be a better approach?
3) There's a chance that this H990DS motherboard it's problematic/defective somehow and replacing with another H990DS would fix things (or even a H990 non-DS with that dual-sim adapter)?
4) The random reboots could give some useful information somehow for you devs? And how the best way to collect it?
5) Are video-calling that demanding, even if it don't reach the same temperatures that the pure CPU stress?
6) Any tips, suggestions?
Thanks!
PS: @xxseva44 sorry I couldn't give you the logs, but the instability/problems here are taking much more time that I initially planned.