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
After seeing these 2 links out there I refuse to buy V30 as long as it has outdated kernel without sched governor support
What do you think?
Then don't get it. I'm going to.
Sent from my iPhone using Tapatalk Pro
Request a dev add it.
We'll have custom kernels.
ChazzMatt said:
Request a dev add it.
We'll have custom kernels.
Click to expand...
Click to collapse
No. I don't want to drop $840 for top-phone and than seek paths to get it hacked, rooted and flash custom kernel in it to get just the same experience which others have in their $400-$550 phones. Like Xiaomis which vendors are fast to deliver modern linux and android kernel enhancements
That's what EAS it for https://forum.xda-developers.com/z5-premium/general/announcement-energy-aware-scheduling-t3620897
I'm willing to bet it doesn't. Pixel devices were the first to launch with it because the code is baked into the AOSP mainline kernel. As much tinkering as every manufacturer does to their device, and the relative newness of this kernel schedule, chances are that it's not.
Sent from my VS995 using Tapatalk
ChazzMatt said:
Request a dev add it.
We'll have custom kernels.
Click to expand...
Click to collapse
Billy Madison said:
No. I don't want to drop $840 for top-phone and than seek paths to get it hacked, rooted and flash custom kernel in it to get just the same experience which others have in their $400-$550 phones. Like Xiaomis which vendors are fast to deliver modern linux and android kernel enhancements
That's what EAS it for https://forum.xda-developers.com/z5-premium/general/announcement-energy-aware-scheduling-t3620897
(This below is a quote from post #1 of that link, so this is what he wants you to read... I'm posting it so you don't have to go there. But feel free to click the link anyway if you wish.)
PDesire said:
In help with @zacharias.maladroit we ported Energy Aware Scheduling (EAS) to our Xperia Z5 Premium
The benefits I already see:
The CPU is really cooler (that what Snapdragon 810 needed)
The idle time has been increased ALOT (like 50% more idle time)
Also it seems battery life has been improved alot
The Port repo:
https://github.com/PDesire/XperiaSatsukiEliteKernel/commits/hotplug
Stay Tuned, this kernel will go online soon
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Too funny. The link you just posted was a dev ADDING it to a Sony Experia Z5 custom kernel -- just like I said could be done easily for our LG V30 (if it doesn't have it already).
You proved my point.
Tbh why everyone wants EAS ? To have a ****ty Scheduler implementation provided by CodeAurora and get disappointed by it ?
The only device which works very well with EAS is the Pixel, and do you know why ? They don't use the CodeAurora implementation, they use their own one. And to use Google's implementation you need Google kernels and not kernels which are based on CAF (like most Snapdragon kernels are).
So keep with HMP, it's not bad like everyone is thinking
Your PDesire
Whats next? To blame the V30 cause it wont include itunes.. (-_-)
PDesire said:
Tbh why everyone wants EAS ? To have a ****ty Scheduler implementation provided by CodeAurora and get disappointed by it ?
The only device which works very well with EAS is the Pixel, and do you know why ? They don't use the CodeAurora implementation, they use their own one. And to use Google's implementation you need Google kernels and not kernels which are based on CAF (like most Snapdragon kernels are).
Click to expand...
Click to collapse
Thanks, mate. I see that you know vastly more than I do in android development space
But please look at that
Even if not look into second run which V30 supposedly loose due to 4Gb onboard vs 6Gb the first round speed is also pathetic. And this link in OP is telling us of very much improved kernel in Galaxy Note 8 compared with all previous generations of Touchwiz and Samsung kernels. Samsung was a beaten boy for it's proverbial lage but it is no more. While LG is becoming the most laughed at Android vendor with it's stutters, lags and hiccups every one complaining about. LG doesn't do nothing to improve in that space, what leads to frustrated and disgruntled customers hence loss continuing for 12 quarters loss of sales and market share. With that pace LG is gonna vanish and be sold to Google as ODM like HTC at best
Does Oreo for V30 support Energy Aware Scheduling (EAS) ?
Can anyone here tell me that which custom ROM is best for gaming and on the other hand which provides the most customization
All though I've never tried it I hear corvus os is the best for gaming
gaming roms doesn't exist and they never existed
corvus was never meant for gaming
alonsoj636 said:
gaming roms doesn't exist and they never existed
corvus was never meant for gaming
Click to expand...
Click to collapse
I didn't say it was a "gaming rom". But there are people that use it for that because of the performance. Its spoken highly of in that regard
3MrBojangles3 said:
I didn't say it was a "gaming rom". But there are people that use it for that because of the performance. Its spoken highly of in that regard
Click to expand...
Click to collapse
well , in case of performance... i didn't feel any difference regarding custom roms.. so i'm using MIUI right now
Corvus performance is not amazing of course tried on some other phones
alonsoj636 said:
well , in case of performance... i didn't feel any difference regarding custom roms.. so i'm using MIUI right now
Corvus performance is not amazing of course tried on some other phones
Click to expand...
Click to collapse
In my experience you can definitely feel a difference between roms. Some are more smooth, some styles are more efficient for how i use my phone. There are factors to consider when choosing a rom. And I've seen a lot about gaming and corvus so that was my recommendation. Are you saying he shouldn't care what rom he plays games on because they are basically the same?
3MrBojangles3 said:
In my experience you can definitely feel a difference between roms. Some are more smooth, some styles are more efficient for how i use my phone. There are factors to consider when choosing a rom. And I've seen a lot about gaming and corvus so that was my recommendation. Are you saying he shouldn't care what rom he plays games on because they are basically the same?
Click to expand...
Click to collapse
all roms use the same kernel so performance shouldn't change drastically. So he should choose a rom according to his tastes, not performance ... for that we have to wait for the custom kernels
All roms use the same kernel?
3MrBojangles3 said:
All roms use the same kernel?
Click to expand...
Click to collapse
Yes , kernel of pixel experience (by Zidan44)
My main question is which custom rom provides the best performance I mostly do gaming Thats why I am asking Plz only mention the rom which is already available for redmi note 10
muneeb rizwan said:
My main question is which custom rom provides the best performance I mostly do gaming Thats why I am asking Plz only mention the rom which is already available for redmi note 10
Click to expand...
Click to collapse
all roms use same kernel no difference in performance (there is no "best rom")
Maybe one did.
MIUI has some turbo mod in the settings.
It could run the processor in peak performance mode.
So try this.
Actually, first, please define "Gaming ROM", since you're not even clearly understanding what is Gaming ROM, how can u ask for it? Besides, @alonsoj636 was right in one thing, whatever ROM u use, still sharing the same kernel ( until we have Custom Kernel too ), hence, the performance would be slightly different. But one thing that some ROM does have is Boosting Touch Sampling Rate, and that function does help your gaming experience more smoothly.
I am looking for something similar i don't why but the pubg performance in miui 12 is very bad i have 4,64 variant but frame drops are very annoying i guess the sd 678 is not yet optimised for gaming considering its a fairly new chipset introduced in phones
ak****@geekybundmaster said:
I am looking for something similar i don't why but the pubg performance in miui 12 is very bad i have 4,64 variant but frame drops are very annoying i guess the sd 678 is not yet optimised for gaming considering its a fairly new chipset introduced in phones
Click to expand...
Click to collapse
Yes , is new ... But the SD 678 is a low-end chipset is not meant for gaming... go for the 732G or better if u want decent gaming experience
Yes , MIUI still is very heavy for this device ... need optimization