For some reason, the author of the Zeus kernel has taken down his GitHub and all the boot.img releases for his Oreo kernel, and has since moved on to developing for Pie and Q. On his Telegram group, now locked, I found the only kernel file on the net, build 1.3.107 -- a damn good kernel, perhaps the best for Oreo -- but it has deep sleep and a few other issues making it unusable after a while. A poster suggested, though, that 1.3.90 was working perfect, without any problems (here's the GitLab repo for it that I've been trying to build, unsuccessfully)...
I don't know if I'll be able to get the kernel built from source anytime soon, so what I'm hoping any of you would still have here, is a boot.img or ZIP file for the Zeus kernel, version 1.3.90 or lower.
TIA
Oh come on, nobody? It's urgent, apps keep FCing for no good reason on other kernels
Can't help you as I don't have an F model
dave678 said:
Can't help you as I don't have an F model
Click to expand...
Click to collapse
What do you have? I believe N960F stuff is compatible across a few other Exynos variants like U, something like that. If you do have a boot image for this kernel, please send it anyway.
rottw3iler said:
What do you have? I believe N960F stuff is compatible across a few other Exynos variants like U, something like that. If you do have a boot image for this kernel, please send it anyway.
Click to expand...
Click to collapse
I have the U version which is Snapdragon and has a locked down bootloader.
Currently the best Kernel for stock One UI 2.5 (And to be honest the only Post-October-2020 Android Q Custom Kernel for N960F right now) is the Beastmode Kernel V2. Android Q Kernels development for N960F is kind of dead and that's the only little hope we have left.
Besides, the Zeus Kernel was incredibly unstable. A real waste. It was very, very optimized and included tweaks that pushed the 9810 to its true limit. But the overclocks applied...that was the problem. They were way...WAAAY too pushed for the majority of the devices. If he dialed down the numbers, many people wouldn't have had heating and random reboot issues.
Related
Is there a re-write or safe kernel at this time?
Do not want CM9 due to the missing functionality. I'm after as close to stock as possible without the crappy risk of screwing up the GN (which is just back from Samsung!).
TIA.
Well Chainfire thinks he might have found a workaround for the problem in his latest kernel.
Check his thread, bur remember to not blame him if somehing goes wrong.
Belfia said:
Well Chainfire thinks he might have found a workaround for the problem in his latest kernel.
Check his thread, bur remember to not blame him if somehing goes wrong.
Click to expand...
Click to collapse
I read CF's notes, which is why I'm asking about recompiles etc.
I know CF modifies stock Samsung kernels, so the faulty command is still a risk according to him.
Yes and there arent many other options I'm afraid.
I'm currently running Francos kernel. It is also based on stock but emmc bug is disabled diractly in the source code. So far there are no reports on bricking with that kernel and everything is running really smooth for me.
Belfia said:
Yes and there arent many other options I'm afraid.
I'm currently running Francos kernel. It is also based on stock but emmc bug is disabled diractly in the source code. So far there are no reports on bricking with that kernel and everything is running really smooth for me.
Click to expand...
Click to collapse
Thanks Belfia. So to be clear you are running stock ICS (e.g. LPY/LP9) and the latest Franco kernel?
No Im on criskelorom as my sig says. But franco kernel works very well with stock ics
What would be really cool is a kernel that's NOT tweaked or modified EXCEPT for the mmc bug. Someone would need to compile the sources with JUST the modifications needed to stop the bug from being triggered.
I don't want those super mega tweaked kernels. Just stock and safe.
We can always dream...
And if so, how much longer do you think? Have you seen any hints or rumors plastered on the net? Do you have any links to evidence of 3.10 coming? Are we missing out on anything of importance that 3.10 brings?
Does anyone know why we are still on 3.1, which was released in 2011? I thought Nexus devices got all the good stuff first... Or are only custom roms and kernels using 3.1?
Android devices rarely get new kernel versions anyway since the kernels tend to be customized to work with a specific device, and the binary drivers are built for a specific version of the kernel. This is not as bad as it sounds tho, since a lot of stuff can be backported meaning you get functionality from a newer kernel without the actual kernel version changing. Even more common with custom kernels. For example there's ROMs for our device that uses the F2FS file system which first appeared in the 3.8 kernel and gotten big changes every version after that, and it runs just fine backported to the 3.1 kernel.
hencke said:
Android devices rarely get new kernel versions anyway since the kernels tend to be customized to work with a specific device, and the binary drivers are built for a specific version of the kernel. This is not as bad as it sounds tho, since a lot of stuff can be backported meaning you get functionality from a newer kernel without the actual kernel version changing. Even more common with custom kernels. For example there's ROMs for our device that uses the F2FS file system which first appeared in the 3.8 kernel and gotten big changes every version after that, and it runs just fine backported to the 3.1 kernel.
Click to expand...
Click to collapse
Ok, so this quote here from Linux.com about commits that look like they are made for Nexus 7 2012, is just wishful thinking? I hope not because 3.10 is a massive jump in technology, and possibly even in performance for our device.
there are architecture-specific commits for 3.10 in the kernel/tegra project, which points to development for the 2012 Nexus 7.
Click to expand...
Click to collapse
http://www.linux.com/news/embedded-...roid-will-be-updated-to-the-v310-linux-kernel
EDIT: Ok, I see now, so many new things from 3.4 and 3.8 may already be in our 3.1 custom kernels? If Google releases a 3.10 for the N7 I hope our devs take advantage of it, instead of porting things over to 3.1. I'd like to see our device get Android 5.0 and kernel 3.10, that would really make me feel like this was one of the best investments I have ever made.
As I said, lots of the improvements from newer kernels have already been backported so there wouldn't be as big a difference in performance as you might think. The tegra commits are interesting, but sadly does not confirm anything. For example, the android police article on those same commits mentions that screenshots from the nexus 4 and 5 with the new android version still show them on kernel 3.4. The chance that the 2012 nexus 7 would get a kernel update while the nexus 5 seems awefully slim. I hope I'm wrong tho, since I think it would make things simpler for the custom kernel developers to base stuff on a newer kernel but I wouldn't get my hopes up...
hencke said:
As I said, lots of the improvements from newer kernels have already been backported so there wouldn't be as big a difference in performance as you might think. The tegra commits are interesting, but sadly does not confirm anything. For example, the android police article on those same commits mentions that screenshots from the nexus 4 and 5 with the new android version still show them on kernel 3.4. The chance that the 2012 nexus 7 would get a kernel update while the nexus 5 seems awefully slim. I hope I'm wrong tho, since I think it would make things simpler for the custom kernel developers to base stuff on a newer kernel but I wouldn't get my hopes up...
Click to expand...
Click to collapse
Ok, thanks for making it a little more clearer to me. I kept thinking our 3.1 kernel from 2011 was holding us back from getting one last great update. I think features are no longer needed and I just want them to push performance as far as this thing can be taken. So with ART and F2FS finally coming, I was hoping a better kernel would grace us as well. lol, but it looks like a newer kernel wouldn't do much that the devs haven't already done.
Thanks buddy for jumping in and clearing some of that up for me. :good:
Nvidia released their kernel 3.4.35 for tegra3
I'm coming from a vzw note 3 and iPhone territory. So kernels are new to me. What are some features that are better over the stock? I'm currently rooted on 5.0.1. I am a flashaholic so I don't mind testing each kernel but like I said, it's unknown to me. I don't want to brick my nexus quite yet haha
bmwh0r3 said:
I'm coming from a vzw note 3 and iPhone territory. So kernels are new to me. What are some features that are better over the stock? I'm currently rooted on 5.0.1. I am a flashaholic so I don't mind testing each kernel but like I said, it's unknown to me. I don't want to brick my nexus quite yet haha
Click to expand...
Click to collapse
kernels arent about features, even though some include them. kernels are about making your phone work more efficiently and about getting more performance out of your device. problem is, it all depends on how you use your device, as thats how you would set up the kernel that you are using. and stock as well, comes with its own kernel. a kernel is like the "brain" of your phone, as it will control everything.
Here's some good info about Kernel and governors.
http://forum.xda-developers.com/showthread.php?t=1680183
https://www.youtube.com/watch?v=luf4yDc6Jfs
Here's a video explaining what a kernel is.
It's impossible to brick your phone by simply flashing kernels unless you flash a kernel that isn't for your phone you shouldn't worry.
For the features, read the thread of a kernel thread and you'll see them. Personally for me, it's to change colors and not use mpdecision
Sent from my Nexus 6 using Tapatalk
Thanks everyone. The note 3 bootloader was locked so I didn't get to use kernels before. I'm going to try leankernel.
This also is a good source for kernel options/functions.
http://forum.xda-developers.com/showthread.php?t=1369817
Sent from my SinLess Shamu
Basically kernels are the medium between the software and the hardware.
Hi,
since the official maintainer "solk2" for the GT-I9506 moved on to CM12 before providing a final build incorporating his latest fixes I decided to make my own builds.
According to my personal experience the battery life has vastly improved. In particular the power consumption while the display is off has decreased substantially. Solk2 has apparently fixed some issues with the kernel so the battery issues are gone. So for everyone not yet willing to transition to CM12 (in my case inter alia due to the currently unstable state and the lack of a stable Xposed framework in Android 5) this might be a good alternative.
I will gladly share my unofficial ROMs, however I would need someone to host the files in order to do that. If anyone would be so kind as to host ROMs please let me know.
If any relevant code changes to CM11 will appear I will most certainly compile a new version.
* IMPORTANT *
Please note that these builds are based on nothing else than the unchanged official code from Cyanogenmod, solk2 and others. So every credit goes to them.
I will not and cannot make any changes to the code. The only thing I can do and will do is build a ROM thereof in case some interesting fixes etc. appear. However, since CM11 is becoming outdated there will most probably not be a lot of changes to come.
Also, it should be understood that I take no responsibilities whatsoever if anything goes wrong when you install the ROM. Like the original ROM this is completely at your own risk!
However, you can expect that any ROM I share has been installed on my own GT-I9506 (with Samsung firmware of 4.4.2 nordic countries) and runs without obvious issues. Your mileage may vary.
Here is the current version, including the CM-11.0 code base up to http://review.cyanogenmod.org/#/c/97688/ :
https://www.mediafire.com/folder/j0jynk3en95j5n1,soag9jcmrcajdhq/shared
* Note *
At least some of the issues with solk2's latest official builds were apparently caused by preceding changes to the kernel code. My builds use the latest code base of February 16 incorporating solk2's latest fixes (see https://github.com/CyanogenMod/android_kernel_samsung_ks01lte/commits/cm-11.0).
Unless solk2 will make further changes to the kernel (which I doubt as he has turned his attention to CM-12) the changes in my builds are only related to merged changes in the official Cyanogenmod code for CM-11.0 (see http://review.cyanogenmod.org/#/q/status:merged+branch:+cm-11.0). In other words the kernel will remain the same, even if the build date thereof may change.
Thank You. Perfect rom. in 2015-05-20 mms is working by default I have not find any bugs.
I'm on arter97 CM12.1 and I'd like to try this one. I can imagine a such install procedure:
-flash kk stock firmware (CNJ1 nordic) from odin
-reboot
-flash custom recovery from odin
-reboot
-flash your rom from custom recovery
Is that right?
ilfavi said:
I'm on arter97 CM12.1 and I'd like to try this one. I can imagine a such install procedure:
-flash kk stock firmware (CNJ1 nordic) from odin
-reboot
-flash custom recovery from odin
-reboot
-flash your rom from custom recovery
Is that right?
Click to expand...
Click to collapse
You do not need flash any stock. Just flash TWRP, make full wipe and flash this rom + gapps
Why is this rom so ignored? I flashed it a few days ago and I find it's great. Very very fast and absolutely rock solid. No bugs, no fc, no reboots.
ilfavi said:
Why is this rom so ignored? I flashed it a few days ago and I find it's great. Very very fast and absolutely rock solid. No bugs, no fc, no reboots.
Click to expand...
Click to collapse
I do not know how many have installed this ROM (anyone having done so please leave a reply here).
I see only a very limited number of reasons to transition to a new version of a ROM or Android in general:
1. If the new version provides functionality that I want or need (and material design isn't one of those); or
2. If the new version fixes a bug or security flaw (there is none that I know of).
At the moment CM-12 does not fulfill any of these criteria, instead I would lose the solidly working Xposed framework for an alpha version thereof.
I'm not intending to advertise this ROM, inter alia because the only thing I did was build it, so the credits should still go to solk2. But if anyone hears that someone has issues with the latest "official" version of CM-11, please direct them here.
HI !
This rom is awsome (smooth fast and stable) but is lacking of functionality...
@NeuDLi do you think I can use this rom for patchrom miui v5 or v6 on ? (as base)
And thanks for your work !
3lambda said:
HI !
This rom is awsome (smooth fast and stable) but is lacking of functionality...
@NeuDLi do you think I can use this rom for patchrom miui v5 or v6 on ? (as base)
Click to expand...
Click to collapse
I suppose so... Since it does use the official CM sources, just go ahead and try it.
Thanks for the reply
Do you have some knowledge on building stuff ? (via linux command, problem etc)
What should happen if I update via OTA as it ask me to do?
edit: I realized that the updates suggested are cm12 so can be ignored
I had one strange bug in this rom (maybe reason was in gapps): Go to SMS app, push new and write name in address line from above: phone getting list of contacts to chise. You choisew one and see wrong number (without region code) in address line.
If you push on contacts button and choise contacts here everything will be ok.
NeuDLi said:
I do not know how many have installed this ROM (anyone having done so please leave a reply here).
I see only a very limited number of reasons to transition to a new version of a ROM or Android in general:
1. If the new version provides functionality that I want or need (and material design isn't one of those); or
2. If the new version fixes a bug or security flaw (there is none that I know of).
At the moment CM-12 does not fulfill any of these criteria, instead I would lose the solidly working Xposed framework for an alpha version thereof.
I'm not intending to advertise this ROM, inter alia because the only thing I did was build it, so the credits should still go to solk2. But if anyone hears that someone has issues with the latest "official" version of CM-11, please direct them here.
Click to expand...
Click to collapse
Do you know to make compatible with this ROM, the Arter97 kernel?
Alexyerga said:
Do you know to make compatible with this ROM, the Arter97 kernel?
Click to expand...
Click to collapse
No, as stated I'm not a coder. And also why use Arter97 kernel anyway?
NeuDLi said:
No, as stated I'm not a coder. And also why use Arter97 kernel anyway?
Click to expand...
Click to collapse
Because the Solk2 kernel causes random reboots sometimes
Alexyerga said:
Because the Solk2 kernel causes random reboots sometimes
Click to expand...
Click to collapse
Then maybe you should ask Arter97 what's different in his kernel... Without any hint what difference causes this no-one has a realistic chance to find out. Or ask him to adapt his kernel to CM-based ROMs. I didn't know that his kernel does not work with CM, is that so?
Also, on my S4 I do not have frequent reboots. However, I once activate the advanced option "kernel samepage merging" and then had two reboots in 1-2 days. After resetting to deactivated no more reboots since about 2 weeks... Worth a try to check.
I would like to help, but I simply do not have anywhere near the experience and knowledge to find a kernel bug that apparently solk has not found himself!
NeuDLi said:
Then maybe you should ask Arter97 what's different in his kernel... Without any hint what difference causes this no-one has a realistic chance to find out. Or ask him to adapt his kernel to CM-based ROMs. I didn't know that his kernel does not work with CM, is that so?
Also, on my S4 I do not have frequent reboots. However, I once activate the advanced option "kernel samepage merging" and then had two reboots in 1-2 days. After resetting to deactivated no more reboots since about 2 weeks... Worth a try to check.
I would like to help, but I simply do not have anywhere near the experience and knowledge to find a kernel bug that apparently solk has not found himself!
Click to expand...
Click to collapse
Last time ago arter's kernel was compatible but he removed the support because he didn't have time to maintain two kernels.
Thanks anyway NeuDLi, i will tray the option "kernel samepage merging", it cames activated or deactivated by default? Because when I tried, I didn't change any option
Alexyerga said:
i will tray the option "kernel samepage merging", it cames activated or deactivated by default? Because when I tried, I didn't change any option
Click to expand...
Click to collapse
Well, another problem... I'm not sure if it is a bug in settings.apk or only in connection with our device. However, when you check the option is always ON, and upon leaving the settings.apk it will always return to being ON. So at least I can say that turning if OFF cannot have had an effect because it was never turned OFF.
However, I will try with KSM disabled now. For the time being you can manually disable it and lock this state (well at least until next reboot) by doing the following in an adb session or the terminal:
echo 0 > /sys/kernel/mm/ksm/run
chmod 444 /sys/kernel/mm/ksm/run
Another way would be to recompile the kernel with the option disabled. It would be far better to fix the issue in settings.apk. However, to file a bug report one would have to check if the behaviour is the same in the official nightlies... I read that someone reported this as a bug for the Oneplus One, but it was never resolved.
As an somewhat veteran in other xda-like forums, I advertised link to neudlis reply with his/her first build because it has been rock stable and fast. With my I9506 nordic.
No other customs have been this solid for 3 weeks straight, and I have been trying roms since december !
iBuu said:
As an somewhat veteran in other xda-like forums, I advertised link to neudlis reply with his/her first build because it has been rock stable and fast. With my I9506 nordic.
No other customs have been this solid for 3 weeks straight, and I have been trying roms since december !
Click to expand...
Click to collapse
Although I cannot often enough remind everyone that I did not provide or change any code but just build it that's still not too bad for the first build of a guy not that much into coding .
After a weekend with not much use but some hours of listening to audio books I was left with 21% charge after more than 3 days (see attached screenshot). That's just awesome! So I believe it can safely be said that any power consumption bug was resolved by solk2's latest patches to the kernel.
Also I believe that turning off kernel samepage merging might have helped additionally, so I encourage everyone to try it as well (see above post for manual way to turn it off as bug in settings.apk won't let you otherwise). In my opinion this option should default to off as it is said to be potentially unstable and the I9506 surely has enough RAM not to need it. So I prefer to lessen CPU load for longer battery life in exchange for potentially increased RAM occupation.
Hey guys, I suppose some of you have had a xiaomi in the past and I have two questions for you and maybe someone that has some knowledge about xiaomi.
1) Currently how's Xiomi dealing with privacy? I remember 1 or 2 years ago Xiaomi has hit with strong reports of leaking information to their government (chinese) and everything we did on the phone would be seeded to their servers, even SMS's and other stuff..
2) How's the ROM support usually for Xiaomi? Do they usually get a stock based ROM, which has no bloatware and some nice tweaks?
Thanks everyone!
Afaik, being a mi3 user, they had a "data sharing" option on by default in miui which is now changed to be off. Personally i never considered it much as there were already devs who had made custom rom for the device, i think over the last two years i might only have used miui for about 4 to 8 months.
No bloatware, but if u r not a previous user, u might find some apps useless (it has its own clean master replacement app). So yeah, there are a lot of options for tweaks n stuff by default too. Hopefully this answers your questions. (and add a question mark to the title, it looks like u r going to rant about Xiaomi by reading the title, lol)
arnabbiswasalsodeep said:
Afaik, being a mi3 user, they had a "data sharing" option on by default in miui which is now changed to be off. Personally i never considered it much as there were already devs who had made custom rom for the device, i think over the last two years i might only have used miui for about 4 to 8 months.
No bloatware, but if u r not a previous user, u might find some apps useless (it has its own clean master replacement app). So yeah, there are a lot of options for tweaks n stuff by default too. Hopefully this answers your questions. (and add a question mark to the title, it looks like u r going to rant about Xiaomi by reading the title, lol)
Click to expand...
Click to collapse
Do you think there will be much custom rom/kernel support for the Mi 5 (or does this depend on Xiaomi allowing for an unlocked bootloader together with release of kernel sources) ?
SlyUK said:
Do you think there will be much custom rom/kernel support for the Mi 5 (or does this depend on Xiaomi allowing for an unlocked bootloader together with release of kernel sources) ?
Click to expand...
Click to collapse
There will sure be support for custom roms even when the kernel source isn't there, my device had custom roms even before kernel source was released, although there were a bit bugs due to it and only a few (like 5 to 10) custom roms were there, bit with the release of sources, it jumped to 50+. And my device had the bootloader unlocked by default, which even i didn't knew until i rebooted to it. Although the fastboot wasn't able to get the info about the bootloader (like version, etc). IDK if any new devices require to unlock it but i don't think it should be hard as they support it, so that won't be a barrier for development.
TL;DR- less n buggy roms w/o kernel source, floods of roms and custom kernels after source, nothing to concern about bootloader.
There maybe some rom development from a few people that get the device and maybe from cm. But that's about it. Non of the big name team roms will have official versions, just maybe ports.
As for the security and privacy. That is up in the air as it seems even on custom roms they some how have managed to still keep track of the devices. One person on the MI note found that even while not on miui for months that they still had a current backup of all his apps and info.
Website signature
zelendel said:
There maybe some rom development from a few people that get the device and maybe from cm. But that's about it. Non of the big name team roms will have official versions, just maybe ports.
As for the security and privacy. That is up in the air as it seems even on custom roms they some how have managed to still keep track of the devices. One person on the MI note found that even while not on miui for months that they still had a current backup of all his apps and info.
Website signature
Click to expand...
Click to collapse
With regards to porting an official rom, I suppose these would be regarded as Unofficial versions. If that is the case is there any real disadvantage in having the "Port" as opposed to have the "Official" version ?
Ports normally will have some bugs as this happens due to not having some things for device built into the code.
Data leak & Software development
Yes I also heard that even with a custom ROM on the device they still found a way to make the device connected and synching information with their servers, which I don't find that funny..
I wanted to know if this data leak is still present in the previous flagship, anyone tested it recently?
It's good to know that it has nearly no bloatware from what you are saying me, but if it has something I don't find useful I may just freeze the app.
Also does anyone know if Xiaomi usually takes long times to update the software of their devices (I heard that they were an exception in relation to other Chinese manufacturers) and release the kernel sources for the ROM developing community or are they pretty good on this area?
Thanks!
:good: :good: :good:
No they are terrible about it. Normally when they post the kernel source it is incomplete and broken.
As for updating. Until very recently they based their os on 4.4 and when asked why they said they didn't care about official android versions.
As for bloat that depends on how you look at it. Miui is about as bloated as TW or HTC Sense.
@zelendel In terms of big name team roms having official versions, would kindly give a few examples ?
SlyUK said:
@zelendel In terms of big name team roms having official versions, would kindly give a few examples ?
Click to expand...
Click to collapse
The biggest are the one or two devices (cant remember their names off the top of my head) that were able to get/fix the kernel source and device trees which CM picked up. So some of the teams that use CM source as a base like AICP also picked up Official versions for the devices.
Then you have the Roms that are based on AOSP instead of CM. As they dont use CM as a base ( Maybe some parts) These roms like Slim or Dirty Unicorns seldom see official versions of the rom. Normally you might get a port here and there. It all depends on if the one of the devs gets the device as most teams don't offer official support for devices they do not own.