FuguMod is a secure, open, reliable and no nonsense kernel
This is probably the only custom kernel for the Nexus 5 which adds security instead of removing it.
Current features are:
- compiled with linaro gcc4.7.4
- various small fixes
You can download the kernels at:
http://fugumod.org/nexus5
Source and changelog can be found here:
https://github.com/renaudallard/nexus5_kernel
IRC channel:
irc.freenode.net #fugumod
Flashing
Kernel zips are intended to be flashed with CWM ot TWRP, if you want to flash using fastboot, you need to unpack the zip and flash the boot.img which is inside
Versions
Kernels are based on the below version scheme
kernel_FuguMod_20131104_r1-4.4.img
20131104 is the date it has been packaged
r1 is the release number
4.4 is the ROM it is compatible with
Stable vs Testing
There are sometimes kernels in testing folder. These may be very stable or may not boot at all. Be sure to have an USB cable and fastboot under the hand if you try one of these. That said, in general, if they stay into testing folder for more than 15 min, they should at least boot and work more or less. I tend to remove non booting kernels from testing folder in less than 10 min (depending a little bit on the speed testers take them), and so if you see them one hour later, you should assume they are safe enough to flash.
So, in general Stable is the safest bet, but Testing may be the best. I, myself, generally run testing one.
Deprecated folder
In general, unless you really know what you are doing, you should avoid flashing those, they are mainly there for historical reasons.
Check for vulnerabilities
http://www.xray.io
Compatibility with hackish style apps
All apps which require direct memory write, access to symbols or memory offsets or modules will NOT work. And, no, don't ask they won't be supported in the future. Example: Arararagi's light is only provided as a module and will not be supported unless he produces a patch.
Security
If you want good security when your phone is stolen, in addition to encryption, don't forget to turn debugging off. Also, use enpasschanger to change your encryption password, any short PIN encryption can be cracked in a few minutes easily (for example, using my script at http://pastebin.com/Mdu06RZN)
Redistribution
As per GPL, you are authorized to redistribute this kernel with any of your custom ROMs provided you give out the source code like I do. You can link to my github in your distribution site.
However, if you modify the kernel yourself, whatever the modification is (compiling it yourself with a different compiler is a modification), you are not authorized to name it FuguMod, although you can credit me and tell the base comes from FuguMod but you cannot call the kernel itself FuguMod.
XDA:DevDB Information
FuguMod, a Kernel for the Google Nexus 5
Contributors
renaud, http://forum.xda-developers.com/member.php?u=2859799
Kernel Special Features: Open, stable, reliable and secure
Version Information
Status: Testing
Created 2013-11-04
Last Updated 2014-01-29
Glad to see you here renaud. I loved your Galaxy Nexus kernels.
First test version is now available
If anyone can confirm it was flashed correctly and boots, that would be great.
I'll test it right after the postman makes me happy
Haeretik said:
I'll test it right after the postman makes me happy
Click to expand...
Click to collapse
Just got a confirmation that mine will come tomorrow
flashed kernel_FuguMod_20131104_r1-4.4.zip and it reboots to bootloader.
Hello @renaud.
It's really nice to find a lot of people coming from Galaxy Nexus to the Nexus 5. As the Galaxy Nexus is an oldie (yes, two years), there are less and less threads supported. I hope, you will still support the Galaxy Nexus - but also the Nexus 5, of course. Good to have you in here! :laugh:
proxuser said:
flashed kernel_FuguMod_20131104_r1-4.4.zip and it reboots to bootloader.
Click to expand...
Click to collapse
When flashing or when booting?
renaud said:
When flashing or when booting?
Click to expand...
Click to collapse
after booting, i flashed it via bootloader.
proxuser said:
after booting, i flashed it via bootloader.
Click to expand...
Click to collapse
I suppose you meant you flashed with fastboot.
Whatever, till how far does it go?
I am wondering, did you unpack the zip and flashed boot.img through fastboot, or did you flash the whole zip through fastboot??
I'm glad you got the new nexus because I've been waiting for your kernels for awhile now.
Sent from my Nexus 4 using Tapatalk
tried out your kernel, alot of nice features but stock seemed to run faster. cant wait to see what the community has to offer over the next couple of months. pushing the phone to its limits / extending battery life.
dandwhelan said:
tried out your kernel, alot of nice features but stock seemed to run faster. cant wait to see what the community has to offer over the next couple of months. pushing the phone to its limits / extending battery life.
Click to expand...
Click to collapse
Thank you for confirming that it boots. Currently it has no features except being smaller than the stock one. I was waiting for the boot confirmation before developing.
Nice to see you again Renaud. Glad to be owning a device you're deving on again.
I have now received my N5. Real stuff will begin.
OK, thanks for some reporting as booting, but in fact it does not because my img doesn't support dtb yet.
Glad you got the phone and now hopefully fugukernel updater will work for this phone.
Sent from my Nexus 5 using Tapatalk
unforgivenmercy said:
Glad you got the phone and now hopefully fugukernel updater will work for this phone.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I was not doing it myself, but I guess I can ask for the code to not have to rewrite everything by myself
r3 is out.
It boots and is compiled with linaro GCC 4.8
Further optimizations are on the road.
Whats with colour calibration?
Sent from my Nexus 5 using xda app-developers app
Related
[ 02/09/2012: Screen Flicker / Brightness is an issue. I'll be looking at it. ]
Hi guys,
In an attempt to help further kernel development for the Kindle Fire, I'd like to share my stock defconfig. It's a bit different than the original otter_android_defconfig that g1011999 came up with.
I was never able to get a usable kernel. So I took some time and built up mine.
https://github.com/KFire-Android/kernel_omap/blob/stock/arch/arm/configs/otter_android_defconfig
This kernel builds using the preferred TI compiler used in all of their walk-thrus: CodeSourcery 2010-q1
Moving forward into CM9/ICS, some changes need to happen to the kernel over time. The migration kernel is found in a branch: "L27.13.1-ICS". The END result of this will be a kernel / source that fully support hw codecs for ICS.
[02/08/2012] FLASH ZIP FOR THOSE RUNNING NIND'S BUILDS: http://bit.ly/xYOf0V
The following ROM is built from the sources at GitHub under the KFire-Android org. Many of those files and configurations are the result of countless hours of development by JackpotClavin. I don't want there to be any confusion as to who put in a ton of time getting this to work.
[02/09/2012] FULL ROM INSTALL: http://bit.ly/ygVvQB
Changelog:
- Screen flicker IS an issue right now. Digging into it
- Touchscreen "Slop" set to 16. This should help touches register on the touchscreen.
- Working Data usage stats (xt_qtaguid / xt_quota2 kernel modules)
- TUN, CIFS support
- USB mounting fixes
Thanks Hashcode, currently building a latest ICS version of it.
A little note for those who also want to compile: arm-eabi-4.4.3 and arm-eabi-4.4.0 did not work for me, they ended the compile without any errormessage in the middle of nowhere, arm-eabi-4.3.1 did the job. Took me some time to figure that out ...
nind said:
Thanks Hashcode, currently building a latest ICS version of it.
A little note for those who also want to compile: arm-eabi-4.4.3 and arm-eabi-4.4.0 did not work for me, they ended the compile without any errormessage in the middle of nowhere, arm-eabi-4.3.1 did the job. Took me some time to figure that out ...
Click to expand...
Click to collapse
If you want to follow a very good step by step guide for setting this up the same way TI (the CPU maker) intended, then follow this:
http://www.omappedia.com/wiki/PandaBoard_L27.12.1-P2_Release_Notes#Setting_up_build_environment
Obviously, that's for PandaBoard, but the Toolchain source and setup are very good.
It goes into deep sleep for me and turning off the stay awake option in settings, developer options, the screen goes off like its supposed to.
Hashcode said:
Hi guys,
In an attempt to help further kernel development for the Kindle Fire, I'd like to share my stock defconfig. It's a bit different than the original otter_android_defconfig that g1011999 came up with.
I was never able to get a usable kernel. So I took some time nd built up mine.
https://github.com/KFire-Android/kernel_omap/blob/stock/arch/arm/configs/otter2_android_defconfig
This kernel builds using the preferred TI compiler used in all of their walk-thrus: CodeSourcery 2010-q1
Tonight, I'll go back to both of my in-progress kernels and do some testing to see if they'll boot.
EDIT:
Current issues being looked at with this kernel:
- Power off doesn't really power all the way down. It goes to a black screen, but requires long press to turn off.
- Deep sleep isn't happening. The backlight is on a tad while the screen should be off.
But this config is still MUCH better than trying the original.
Click to expand...
Click to collapse
So does this boot cm7 or anything? My kernel builds boot stock kindle but not cm7
Its something to do with netd/dnsproxyd. Just finding a fix that works is a PITA common issue, but then people dont say how they fixed it..
Right now ive only tested this with CM9
Sent from my DROID RAZR using XDA App
touch points
Any chance you're looking into enabling more than 2 touch points in this kernel?
foxdog66 said:
It goes into deep sleep for me and turning off the stay awake option in settings, developer options, the screen goes off like its supposed to.
Click to expand...
Click to collapse
I'm running nind/sitic's cm9-02-04 build with this kernel baked in. I, too, have Stay Awake disabled in Developer Options, and my Kindle is going into deep sleep. I am experiencing the power down issue, though.
It's something I'm absolutely willing to live with for the time being. This is good stuff. Thanks Hashcode!
jabdo79 said:
Any chance you're looking into enabling more than 2 touch points in this kernel?
Click to expand...
Click to collapse
Thats really the future of this kernel. I needed a solid base to start from.
Sent from my DROID RAZR using XDA App
Well reason I asked was because my kernel wont boot cm7 or cm9. It boots the stock kindle fire os okay. Im getting netd/dnsproxyd errors in the kernel when I try booting cm7.
death2all110 said:
Well reason I asked was because my kernel wont boot cm7 or cm9. It boots the stock kindle fire os okay. Im getting netd/dnsproxyd errors in the kernel when I try booting cm7.
Click to expand...
Click to collapse
Right now the difference between this kernel and stock is:
- About 8 ip6 netfilter modules were added
And that's about it.
death2all110 said:
Well reason I asked was because my kernel wont boot cm7 or cm9. It boots the stock kindle fire os okay. Im getting netd/dnsproxyd errors in the kernel when I try booting cm7.
Click to expand...
Click to collapse
Are you using the stock ramdisk or the modified ramdisk for cm? I know there must be a difference, as intersectRaven puts out several different variations of his kernel in boot.img form, but I haven't gotten around to diffing them yet
wdfowty said:
Are you using the stock ramdisk or the modified ramdisk for cm? I know there must be a difference, as intersectRaven puts out several different variations of his kernel in boot.img form, but I haven't gotten around to diffing them yet
Click to expand...
Click to collapse
ill look into insectraven's cm kernel thanks!
Edit: That worked! Thanks!
he starts the dnsproxyd differently than what I've seen. But it works!
So I noticed that /mnt/ is mounted read-only which causes issues with apps installing to the sdcard and probably the issue people are having with mounting the sdcard to the computer. Some apps insist on installing to the sdcard (I hate that)
Edit: or do I have this all wrong? Lol I'm no dev remounting it r/w gets the job done.
Is there any websites or anything that you guys would recommend to learn about the Linux kernel and development of it?
Tonight, I went back through and cleaned up my config some more. Removed extra power controls, usb mtp settings and omap mmc host controller (for sd card slot boards).
From my tests, everything deep sleeps correctly and the power off issue is fixed.
https://github.com/KFire-Android/kernel_omap
will you be posting a installable zip or boot.img? I'm running nind's cm9-02-05 build which has this kernel and its by far the most stable for me. I would like to update without waiting for someone to include it in a rom please
foxdog66 said:
will you be posting a installable zip or boot.img? I'm running nind's cm9-02-05 build which has this kernel and its by far the most stable for me. I would like to update without waiting for someone to include it in a rom please
Click to expand...
Click to collapse
I'll see what I can do. boot.img would be ok?
Sent from my XT912 using XDA App
Hashcode said:
I'll see what I can do. boot.img would be ok?
Sent from my XT912 using XDA App
Click to expand...
Click to collapse
Yeah that's cool.
foxdog66 said:
Yeah that's cool.
Click to expand...
Click to collapse
Here's an updated boot.img for nind's 2/5 build:
[ UPDATED OP W/ FLASH.ZIP FILE ]
As a proof of concept I compiled Kit Kat for our Acer Inconia. It needs a new build of CWM in order to flash. I have not been able to boot up CWM that I compiled so anyone here that has built recovery on here before try to build latest CWM and/or TWRP then we can try out this KitKat build to see if it boots or not. It may need some kernel patches. It's using pio_maski's jb-mr2 trees that I modified for 4.4 for a100 (note: I haven't uploaded yet and won't unless it boots).
Download: http://d-h.st/aKr
What you can do to help:
1. Compile the latest TWRP or CWM and post if it boots. Only do this if you've done it before; I'm not going to teach because it is out of my knowledge why CWM won't boot. If you come across any errors and don't know how to fix PM me or post here I'll help you fix it.
2. NOTHING can be done until we have a working (latest) recovery.
Sources:
Device: https://github.com/awid777/android_device_acer_a100 (cm10.2 branch)
Note for the sources: This isn't the source I used to compile the initial build. However, they are almost identical. The credits for the sources for the ROM go to @pio-masaki for his device and commons trees and prebuilt kernel. I would post the sources I used but I never uploaded them because I ended up deleting them early on as I prefer to use a single device tree. All my commits will now be posted to the listed source.
awidawad said:
As a proof of concept I compiled Kit Kat for our Acer Inconia. It needs a new build of CWM in order to flash. I have not been able to boot up CWM that I compiled so anyone here that has built recovery on here before try to build latest CWM and/or TWRP then we can try out this KitKat build to see if it boots or not. It may need some kernel patches. It's using pio_maski's jb-mr2 trees that I modified for 4.4 for a100 (note: I haven't uploaded yet and won't unless it boots).
Download: Pending upload.
What you can do to help:
1. Compile the latest TWRP or CWM and post if it boots. Only do this if you've done it before; I'm not going to teach because it is out of my knowledge why CWM won't boot. If you come across any errors and don't know how to fix PM me or post here I'll help you fix it.
2. NOTHING can be done until we have a working (latest) recovery.
Click to expand...
Click to collapse
I am not a "DEV", however I have a good amount of talent with photoshop and have some self taught coding experience with linux and html5. I also am willing to learn/eager to learn. I know you mentioned you don't want to teach. Just know if you point me in the direction I am willing to do the work on my end to get the knowledge and apply it. I have been playing with this tablet and working on a hybrid kitkat look alike using 4.1.2 as my base. I tried using 4.3 and applying 4.4 goodies to it. Didn't work that well. The 4.3 Jellytime was a bit quirky at times and didn't seem stable as a daily driver. I have put together a couple new boot animations to compliment kitkat already. I have also modified Arora installer with a very good kitkat theme. I have used it several times to verify it works correctly. I can provide that if wanted. I am waiting for a stable build and willing to help where I can. I plan on installing this tablet into my dash in the very near future. Once that is done, unfortunately I will only be able to help with themes and basic items that don't require the tablet all the time. I have contemplated having the ability to remove the tablet whenever I leave the car so I guess we will see when I get there. Apologize for the long post.
po8pimp said:
I am not a "DEV", however I have a good amount of talent with photoshop and have some self taught coding experience with linux and html5. I also am willing to learn/eager to learn. I know you mentioned you don't want to teach. Just know if you point me in the direction I am willing to do the work on my end to get the knowledge and apply it. I have been playing with this tablet and working on a hybrid kitkat look alike using 4.1.2 as my base. I tried using 4.3 and applying 4.4 goodies to it. Didn't work that well. The 4.3 Jellytime was a bit quirky at times and didn't seem stable as a daily driver. I have put together a couple new boot animations to compliment kitkat already. I have also modified Arora installer with a very good kitkat theme. I have used it several times to verify it works correctly. I can provide that if wanted. I am waiting for a stable build and willing to help where I can. I plan on installing this tablet into my dash in the very near future. Once that is done, unfortunately I will only be able to help with themes and basic items that don't require the tablet all the time. I have contemplated having the ability to remove the tablet whenever I leave the car so I guess we will see when I get there. Apologize for the long post.
Click to expand...
Click to collapse
This is not a port, thus doesn't need modification. It is compiled (built) from source and the work that needs to be done is in the source code so it can be compiled properly and work without modification
http://wiki.cyanogenmod.org/w/Development
awidawad said:
As a proof of concept I compiled Kit Kat for our Acer Inconia. It needs a new build of CWM in order to flash. I have not been able to boot up CWM that I compiled so anyone here that has built recovery on here before try to build latest CWM and/or TWRP then we can try out this KitKat build to see if it boots or not. It may need some kernel patches. It's using pio_maski's jb-mr2 trees that I modified for 4.4 for a100 (note: I haven't uploaded yet and won't unless it boots).
Download: [url]http://d-h.st/aKr[/url]
What you can do to help:
1. Compile the latest TWRP or CWM and post if it boots. Only do this if you've done it before; I'm not going to teach because it is out of my knowledge why CWM won't boot. If you come across any errors and don't know how to fix PM me or post here I'll help you fix it.
2. NOTHING can be done until we have a working (latest) recovery.
Click to expand...
Click to collapse
Thanks for the link and quick response, will take a look through some of that stuff and see if there is anything I can do to help. Also I noticed while I was typing the first one you put up a download... Did you get it to boot. I downloaded and tried using TWRP and was unsuccessful. I tried a couple times to make sure it copied over from the computer correctly. Still the same result.
4.4 updates different. Latest cwn will flash it. Maybe there's an easy way to do this
Sent from my SPH-L710 using XDA Premium 4 mobile app
Ok so I am stuck right now. I spent a couple hours building an environment and started compiling from source. I am stuck at this point:
$ source build/envsetup.sh
$ breakfast a700
Where a700 is, should be a100. I get errors when doing this because CyanogenMod does not have the device in it's file system. Whoever has successfully done this, please advise. I am over half way with this and would like to complete the build. I have about 20gbs of data sitting on my cpu waiting to compile this so the sooner we can find the solution the better. Thanks in advance.
Need help solving this to move further... There might be a work around, however I have never done this and I am stuck.
Wait till tonight. I'll post my code.
Sent from my One SV using Tapatalk
awidawad said:
Wait till tonight. I'll post my code.
Sent from my One SV using Tapatalk
Click to expand...
Click to collapse
Sounds good. I spent a good part of 3 hours compiling a master build of Kitkat which was complete prior to me leaving for work this morning, however my daughter kicked the power strip under the desk and shut everything down. I will try and find a little time tonight to recompile.
Am I missing something?
Sent from my SPH-L710 using XDA Premium 4 mobile app
TWRP Version?
Is this TWRP new enough for your needs if not what is the newest version you are aware of
a100 TWRP 2.6.1.0 windows installer: as far as I can tell the Twrp image is based of linuxsociety's/GodMachine's work I know for sure the installer is his
http://d-h.st/Rfm
I have flashed this and all seems to work well
I also took the 2.6.1.0 from the above linked installer and put it into a flashable.zip that originaly contained GM's 2.2.2.1 TWRP
I updated the script to show the proper version as well attatched below
AngryManMLS Is responsible for both 2.6.1.0 and 2.6.3.0, "if I am not mistaken"?
His windows/Linux installers can be found here: http://www.androidfilehost.com/?a=show&w=files&flid=9577
and Here:http://forum.xda-developers.com/showpost.php?p=47555451&postcount=109 For 2.6.3.0
I also invited AngryManMLS to build the TWRP needed for this project So We'll have to wait and see if he can help "Break US OFF A PEICE OF SOME KIT-KAT---- Iconia???!!!!!!"
I just want to correct something. The only thing I have done was updating the Windows and Linux installers for TWRP. I have no responsibility with the compiling of TWRP itself. At this point we're waiting for the TWRP folks themselves to fix whatever issues that lie with Kit Kat 4.4. I don't know what to say beyond that. Sorry.
AngryManMLS said:
I just want to correct something. The only thing I have done was updating the Windows and Linux installers for TWRP. I have no responsibility with the compiling of TWRP itself. At this point we're waiting for the TWRP folks themselves to fix whatever issues that lie with Kit Kat 4.4. I don't know what to say beyond that. Sorry.
Click to expand...
Click to collapse
My Bad I shouldn't have assumed do you know who is doing the compiling?
I'm going to go ahead and compile TWRP. I've educated myself on the a100 (I've never done programming on this device or any other Tegra based device... Used to Qualcomm and HTC) hopefully it will work. Current TWRP branch on GitHub is twrp2.7 and has all KitKat changes in it. I'll have a build tomorrow morning. Tonight I have to finish my essays and other homework. I'll let you all know if recovery boots or not. If it does boot, I'll go ahead and attempt installing and booting KitKat
hello! I wonder if owners will share files as well as the vendor, I've wanted to compile pacman for this tablet but can not find the source code! Thanks in advance!
josegalre said:
hello! I wonder if owners will share files as well as the vendor, I've wanted to compile pacman for this tablet but can not find the source code! Thanks in advance!
Click to expand...
Click to collapse
Once I have time, which won't be until later tonight. You could use www.github.com/pio-masaki too. Use the jb-mr2 branch for 4.3
http://forum.xda-developers.com/showpost.php?p=41990263&postcount=1
awidawad said:
Once I have time, which won't be until later tonight. You could use www.github.com/pio-masaki too. Use the jb-mr2 branch for 4.3
Click to expand...
Click to collapse
hardslog said:
http://forum.xda-developers.com/showpost.php?p=41990263&postcount=1
Click to expand...
Click to collapse
thank you! I have to have fun these days!
Well I compiled latest TWRP it didn't work it has same errors. I'll take this up with Dees_Troy. Because when I place the same trees and TWRP into the cm-11 source it won't compile, whereas it compiles fine in cm-10 source. When I manually fix compilation errors it compiles but when flashed it doesn't boot. Same story with CWM
Sent from my One SV using Tapatalk
awidawad said:
Well I compiled latest TWRP it didn't work it has same errors. I'll take this up with Dees_Troy. Because when I place the same trees and TWRP into the cm-11 source it won't compile, whereas it compiles fine in cm-10 source. When I manually fix compilation errors it compiles but when flashed it doesn't boot. Same story with CWM
Sent from my One SV using Tapatalk
Click to expand...
Click to collapse
Try compiling cwm then.
Sent from my SPH-L710 using XDA Premium 4 mobile app
Presenting CM13 unofficial. Built from mostly pure CyanogenMod sources, with a few tweaks that I try to keep updated on my github. This is only possible due to the work of Ziyan and MWisBest.
Instructions
First time flashing CM13 to your toroplus (or coming from another ROM)?
Unlock & install a recovery
Wipe data & cache partitions
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Updating from a previous build?
Just install the latest ROM zip. If you had Google Apps installed, they will be reinstalled automatically.
Click to expand...
Click to collapse
Downloads
Latest cm-13.0 build: https://www.androidfilehost.com/?fid=24588212152305191
Final cm-12.1 build: https://www.androidfilehost.com/?fid=24438995911970260
All builds: https://www.androidfilehost.com/?w=files&flid=23531
Unofficial TWRP recovery: https://www.androidfilehost.com/?fid=24459283995311440
Google Apps: http://opengapps.org/
- Platform: ARM
- Android: 6.0
- Variant: pico (recommended), or nano
Bugs
LTE Data does not work. (3G works)
XDA:DevDB Information
UNOFFICIAL CyanogenMod 13.0 (DDK 1.9), ROM for the Samsung Galaxy Nexus
Contributors
musical_chairs
Source Code: https://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-09-25
Last Updated 2016-07-15
now with Marshmallow!
Will this be updated to work with the new GPU drivers? Thank you!
Sent from my LG-LS980 using XDA Free mobile app
illinoissparks18 said:
Will this be updated to work with the new GPU drivers? Thank you!
Sent from my LG-LS980 using XDA Free mobile app
Click to expand...
Click to collapse
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
musical_chairs said:
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
Click to expand...
Click to collapse
OK I am going to be on board with testing for sure. I left a post in the now no longer current official thread that I flashed the last official build yesterday and I had perfect 3G to LTE to 3G handoff, rock solid WiFi strength, basically everything seemed to work very well. I am looking forward to seeing how things progress. I haven't been able to keep any of the official CM builds from bootlooping until now. Hopefully you stick with it because I am getting better performance from this device than I have seen in a long while
Sent from my Galaxy Nexus using Xparent Gray Tapatalk 2
musical_chairs said:
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
Click to expand...
Click to collapse
Awesome!! Thank you!!
Sent from my LG-LS980 using XDA Free mobile app
I should've had a machete to hack through the jungle of build errors from pulling a modified OmniROM device tree into a CyanogenMod build. Looks like the build is rolling now though, with any luck it might just complete successfully - who knows, it might even boot.
The only thing slower around here than me is my poor old computer.
Its kind of ironic that the Galaxy Nexus was the first official LTE device for Sprint and I am only just recently starting to get LTE on a semi regular basis.
@musical_chairs, take your time with your builds. I assure you that they are appreciated. Now that this device is actually getting decent (for Sprint) signal and still has current builds makes it more enjoyable to use than just about any time I can remember....I just miss Imoseyon's Lean kernels. I got GREAT battery on those. They were compiled in the now deceased (I think) CMRemix ROMs but the LTE is definitely a plus
Update: For now, I have stopped working on building CyanogenMod with the DDK 1.9 drivers. I was ending up with a completely unsustainable mess of a device tree, and was still running into build errors. If new drivers are what you want, use FML. I'll focus on keeping the regular CM builds updated for the time being.
musical_chairs said:
Update: For now, I have stopped working on building CyanogenMod with the DDK 1.9 drivers. I was ending up with a completely unsustainable mess of a device tree, and was still running into build errors. If new drivers are what you want, use FML. I'll focus on keeping the regular CM builds updated for the time being.
Click to expand...
Click to collapse
Link to toroplus build for fml?
Zeinzu said:
Link to toroplus build for fml?
Click to expand...
Click to collapse
I'm following its developements, but haven't had time to try it personally yet.
http://forum.xda-developers.com/galaxy-nexus/sprint-develop/rom-fml-fork-life-10-13-2014-t2903695
Thanks for trying anyhow. I'm glad cm11 still has a fighting chance with the GNex, thanks to you, and all the others who are able to help out.
We're all waiting for cm12 to get to a buildable state. In the meantime, I've been working on upgrading my build box. My old machine was just barely capable of building android, the 'new' one isn't new but it was a real beast in its day. Time for a clean build has dropped from a day and a half to two and a half hours. I'm happy...
jd14771 said:
just curious, how difficult is it to compile roms? Do you need to know how to write your own code or is it over glorified copy and pasting with packages and stuff?
Click to expand...
Click to collapse
I do a lot of copying and pasting, a lot of reading guides, and a whole lot of google-ing. I don't know how to write my own code, but I have lots of experience with applying patches. Compiling roms is not that hard if you're a Linux user, have a working knowledge of the command line, and have a basic understanding of git. Take away any one of those things and it becomes a whole lot harder.
jd14771 said:
Yeah i haven't gotten to play with linux, nor do i know what git's are (i think they are large batch's of code posted in plain text?) . always wanted to try but don't have the time.
Click to expand...
Click to collapse
git is the software the devs use to keep track of changes in the code. Most Android devs have their git repositories on Github, those are probably what you are thinking of. Every little change (called a 'commit') has its own unique hash number. It's pretty amazing, you can look through somebody else's commits and find one that fixes a bug you are working on, or split tens of thousands of changes in half, then in half again, then in half again, etc., and pinpoint the exact commit that causes a bug on your system - though that's more useful in Linux kernel development than in Android.
I don't really have the time either, but it's such a fun hobby...
Using quickboot?
Coming from Vanir. Really like the facility quickboot gives. Anyone "enabled" it? I can't seem actually show the field to turn it on. Settings search finds it, but that's it... Noticed Dev options is hidden also. What's up?
Props for keeping CM11 updated. Really like I can actually use SMS in Hangouts.
I haven't been following the nightly changes since toroplus went dark, but I ran a build today--nothing special, just the latest cm...whatever changes they are. I could post it but don't know if I should make another thread or just link to it in here.
Anything substantial get added to general cm in the last few months?
I tried to run a build of cm12 but it looks like things still aren't ready for building yet, either that or I'm not sure how to switch back and forth between the cm11 repo and cm12 without getting repo update errors.
yotvb531 said:
I tried to run a build of cm12 but it looks like things still aren't ready for building yet, either that or I'm not sure how to switch back and forth between the cm11 repo and cm12 without getting repo update errors.
Click to expand...
Click to collapse
I got cm12 built and booting for toro for the first time today. I'm trying to get mobile data working on that, then I'll give toroplus a shot. Looks like it shouldn't be too much trouble. Feel free to post any of your builds here, or start your own thread if you prefer.
Here's my cm11 build from yesterday--equivalent to a plain nightly. It's been running fine since I dirty flashed it last night. Md5sum is linked as well and noted below.
https://www.dropbox.com/s/lp4j3yayuktmlot/cm-11-20141227-UNOFFICIAL-toroplus.zip?dl=1
https://www.dropbox.com/s/z1b72j7oh70eg5w/cm-11-20141227-UNOFFICIAL-toroplus.zip.md5sum?dl=1
MD5 Sum: e6c265c57e00b4949362d6ff53c9a799
Well I got cm12 built and booting on toroplus, unfortunately the RIL is completely borked, so no cell service at all at this point. I'll keep working on that, in the mean time check out the updated cm11 build in the post right above this one.
Those of you who have been around for a while have heard of leanKernel. Well this isn't a leanKernel, in fact, I haven't developed leanKernels in 3 years. This is essentially the stock kernel with some enhancements.
I think google stock kernels are great nowadays, but when I learned that my Pixel 3a came with eMMC rather than UFS, I thought maybe there are some storage related tweaks I can apply to the stock kernel, so that's what I attempted here.
Again, this is the stock kernel recompiled with the following changes (otherwise should work and behave exactly like stock):
Some f2fs backports from latest f2fs/android sources, mostly around discard and garbage collection including Rapid GC implementation from arter97. The f2fs optimizations around GC/discard are designed to alleviate eMMC write performance degredations over time, thus improving performance over time as well.
Compiled with gcc 9.2 (kdrag0n) with some architecture and cpu dependent compile optimizations.
Drivers (including wifi driver optimized by arter97) compiled in rather than loading in as modules.
LZMA enabled for TWRP support.
Use fastboot to install. (TWRP or kernel manager flash should work as well, as long as they support boot image flashing).
Three files: stock, stock-modified-nomagisk, and stock-modified-magisk.
Most of you will probably want to "fastboot flash boot stock-modified-magisk.img". Flash stock when you want to go back to stock.
Install files
Source: https://github.com/imoseyon/pixel3a-kernel
Absolutely awesome news. I was interested to know about eMMc after I heard some people mention it. Anyway, thank you and welcome back.
A couple of quick questions if you wouldn't mind, since a lot of us are new to the "Pixel experience", having come from devices that previously only had one or two new firmware versions within the device's lifetime, and are now enjoying monthly updates, with that bringing its own set of issues...
Is this kernel considered a stock variation that cannot be tweeted by a kernel manager, or custom and is tweakable? What is gained by using this one over some of the other custom kernels?
Since the boot image on this device can contain Magisk, custom kernel, and TWRP, does that mean with every update a new image would have to be built, rooted, and TWRP installed, or is there an easier way to get this accomplished?
Thx and happy to see you back on board with this device...
duh1 said:
A couple of quick questions if you wouldn't mind, since a lot of us are new to the "Pixel experience", having come from devices that previously only had one or two new firmware versions within the device's lifetime, and are now enjoying monthly updates, without that bringing its own set of issues...
Is this kernel considered a stock variation that cannot be tweeted by a kernel manager, or custom and is tweakable? What is gained by using this one over some of the other custom kernels?
Since the boot image on this device can contain Magisk, custom kernel, and TWRP, does that mean with every update a new image would have to be built, rooted, and TWRP installed, or is there an easier way to get this accomplished?
Thx and happy to see you back on board with this device...
Click to expand...
Click to collapse
First, with respect to the kernel manager it will behave exactly like the stock kernel. There may be a few tweakable settings the manager apps can see that are in stock which will also show up for this kernel. This is not a true custom kernel with lots of configurable settings - if that's what you want then definitely go for elemental or despair which are developed by excellent devs.
Regarding boot image, you are correct. However, once Pixel 3A gets an official TWRP I should be able to include that in the boot image along with Magisk (currently only Magisk is included). And as long as I have the device I will provide at least one set of updates for each security update from Google.
Imoseyon said:
First, with respect to the kernel manager it will behave exactly like the stock kernel. There may be a few tweakable settings the manager apps can see that are in stock which will also show up for this kernel. This is not a true custom kernel with lots of configurable settings - if that's what you want then definitely go for elemental or despair which are developed by excellent devs.
Regarding boot image, you are correct. However, once Pixel 3A gets an official TWRP I should be able to include that in the boot image along with Magisk (currently only Magisk is included). And as long as I have the device I will provide at least one set of updates for each security update from Google.
Click to expand...
Click to collapse
Thank for the kind words! I actually took a look at your source and I am grabbing the f2fs changes you have, those are a good find. Have always followed your work and have used some of your contributions as well.
Holy... Haven't seen you around since the days of the Samsung charge iirc...
Imoseyon said:
First, with respect to the kernel manager it will behave exactly like the stock kernel. There may be a few tweakable settings the manager apps can see that are in stock which will also show up for this kernel. This is not a true custom kernel with lots of configurable settings - if that's what you want then definitely go for elemental or despair which are developed by excellent devs.
Regarding boot image, you are correct. However, once Pixel 3A gets an official TWRP I should be able to include that in the boot image along with Magisk (currently only Magisk is included). And as long as I have the device I will provide at least one set of updates for each security update from Google.
Click to expand...
Click to collapse
Is your kernel also working on the 3a XL, or is it only for the regular 3a?
xFirefly93 said:
Is your kernel also working on the 3a XL, or is it only for the regular 3a?
Click to expand...
Click to collapse
I think it might. I have no way to test it though..
Imoseyon said:
I think it might. I have no way to test it though..
Click to expand...
Click to collapse
Well, is the kernel source the same for the 3a and 3aXL, or if not, could you make the same mods to the XL source?
I was wondering if this could be built and installed as a zip file, so we could make use of the the kernel managers for easy switching between different kernels for testing. If not, what makes this different that requires an image? Thx...
duh1 said:
Well, is the kernel source the same for the 3a and 3aXL, or if not, could you make the same mods to the XL source?
I was wondering if this could be built and installed as a zip file, so we could make use of the the kernel managers for easy switching between different kernels for testing. If not, what makes this different that requires an image? Thx...
Click to expand...
Click to collapse
Kernel source and even the defconfig file are identical between 3a and 3axl, so I'm fairly confident that it works on both.
Have you tried flashing the boot image files in your kernel manager? I think some, if not all, should work with image files as well.
Imoseyon said:
Kernel source and even the defconfig file are identical between 3a and 3axl, so I'm fairly confident that it works on both.
Have you tried flashing the boot image files in your kernel manager? I think some, if not all, should work with image files as well.
Click to expand...
Click to collapse
Will give it a try flashing it that way, but wondering is there a technical reason why this particular kernel must be an image, not a zip?
xFirefly93 said:
Is your kernel also working on the 3a XL, or is it only for the regular 3a?
Click to expand...
Click to collapse
Imoseyon said:
I think it might. I have no way to test it though..
Click to expand...
Click to collapse
It will work for both.
duh1 said:
Will give it a try flashing it that way, but wondering is there a technical reason why this particular kernel must be an image, not a zip?
Click to expand...
Click to collapse
No real reason other than i didn't think a zip file was needed especially since this kernel is supposed to be more or less the same as stock. I will add a zip file into the folder soon though.
Imoseyon said:
No real reason other than i didn't think a zip file was needed especially since this kernel is supposed to be more or less the same as stock. I will add a zip file into the folder soon though.
Click to expand...
Click to collapse
Can this can be used on Q beta6?
caballon said:
Can this can be used on Q beta6?
Click to expand...
Click to collapse
Nope sorry. Will be working on Aug updates this weekend. Been out of town.
Aug update is up. Toolchain updated to gcc 9.2 as well.
How can I verify that I am actually running your kernel?
Screenshot of About Phone
EDIT: I guess the build date matches that of your upload date.
benji said:
How can I verify that I am actually running your kernel?
Screenshot of About Phone
EDIT: I guess the build date matches that of your upload date.
Click to expand...
Click to collapse
Yup that's it
Will change the version string in my next build so it's less confusing. Good catch.
Will this let TWRP stay installed or no? Do you have to install a custom rom for that and use the other kernel?
crackedvenom2 said:
Will this let TWRP stay installed or no? Do you have to install a custom rom for that and use the other kernel?
Click to expand...
Click to collapse
Interesting, looks like I may need to enable lzma compression. I haven't tried installing twrp yet, let me give it a shot this weekend. Should be easy enough.
For those familiar with Velocity Rom this is the kernel I build for it. Velocity hasnt been on XDA as a rule so Im sure not many are familiar. Velocity is my personal Rom Ive been building for years and have shared with all that are interested. This isnt and will never be an "official development project" but will always exist as long as I continue to develop Android roms.
Velocity is focussed on speed, stability, and efficiency and not on adding every imaginable feature. As this is my personal Rom it will have everything I deem useful to me and/or that doesnt compromise the goals of the project.
I dont add every conceivable governor, I/O scheduler, or other user tweakable options. In fact, I typically remove all the options and keep the best. This is designed as a plug and play kernel, not something to be changed. Its also not designed for other Roms.
Please do not ask for features, ETA's, or related. Again, this is my personal kernel for my personal Rom and will be shared accordingly. That said, I do encourage healthy, friendly dialog in my threads.
Flashing instructions
1) Reboot to bootloader
2) Fastboot boot 'bootimage_name'.img to make sure it boots with no issues
3) Reboot to bootloader again
4) Fastboot flash boot 'bootimage_name'.img
5) Buckle up for safety - optional of course
Changelog
Download
Source
This is basically a crosspost from the 3a XL forum. I only own the 3a XL but Im told this works fine on the 3a as well. There are both patched and unpatched boot.img's available depending on whether you want root or not. There is a lot more info over in the 3a XL thread if you have any questions.
New build up....see changelog. This was built from November security patch source and I havent tried it on the October build so ymmv if flashing on a build prior to November security.
New build up. See changelog for details. Also Sargo will now be getting its own builds vs sharing a Bonito one. Download links have changed in the OP.
ctfrommn said:
New build up. See changelog for details. Also Sargo will now be getting its own builds vs sharing a Bonito one. Download links have changed in the OP.
Click to expand...
Click to collapse
Are there some changes except for the name? I didn't realise and flashed the bonito build, but it works fine on sargo.
I_am_Groot! said:
Are there some changes except for the name? I didn't realise and flashed the bonito build, but it works fine on sargo.
Click to expand...
Click to collapse
No, the boot images are now built using the respective devices but for all intents and purposes its the same build. This change was mostly for allowing me to better keep track of downloads. Its possible there are minor differences based on device too but as they both work interchangeably I doubt its anything big, if at all.
New build up.....see changelog.
Anyone interested in (or willing to) flash and test kernels prior to releases please PM me. I can always use people to help especially as I start looking at more experimental changes/optimizations.
New build up. Substantial changes on this one.
ctfrommn said:
New build up. Substantial changes on this one.
Click to expand...
Click to collapse
Can this kernel can be flash with kernel tools?
caballon said:
Can this kernel can be flash with kernel tools?
Click to expand...
Click to collapse
Flashed it many times without problems in flar's EX kernel manager.
j-a-d-z said:
Flashed it many times without problems in flar's EX kernel manager.
Click to expand...
Click to collapse
What's the difference between the two kernels ?
cellatom said:
What's the difference between the two kernels ?
Click to expand...
Click to collapse
Don't know what the inside differences are, because I'm not a developer, but mvk seems faster for me and more battery friendly at the same time. So I use this kernel for now.
cellatom said:
What's the difference between the two kernels ?
Click to expand...
Click to collapse
I wont speak for Flar as I dont know him but from a code standpoint these are 2 very different kernels. My goals (as stated in the OP) are maximum performance without sacrificing efficiency and stability. I delve deep into the experimental and push things to their limits. So while both share the same (or similar) base the additions are very different.
Hi ctfrommn,
I'm seeing this error when trying to boot from the img. Tried 10.16-10.18 magisk and unpatched, sargo and bonito.
fastboot boot MVK_Sargo_v10.18_magisk_patched.img
Sending 'boot.img' (26872 KB) OKAY [ 0.723s]
Booting FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
fastboot: error: Command failed
Click to expand...
Click to collapse
When I flash the img and reboot the 3a goes to fastboot mode and shows "Enter reason: error boot prepare"
Any idea why?
h4m74ro said:
Hi ctfrommn,
I'm seeing this error when trying to boot from the img. Tried 10.16-10.18 magisk and unpatched, sargo and bonito.
When I flash the img and reboot the 3a goes to fastboot mode and shows "Enter reason: error boot prepare"
Any idea why?
Click to expand...
Click to collapse
If your on December update then Yea it won't boot
New build up. See changelog.......This works on both November and December builds.
ctfrommn said:
New build up. See changelog.......This works on both November and December builds.
Click to expand...
Click to collapse
Keep it coming
Anyone willing to give a comparison of this vs. other custom kernels that they've used?
Sent from my Pixel 3a using Tapatalk
New build time. I just spent the last month rebasing and rebuilding this. Everything was rethought, tested, and only kept if it objectively and subjectively improved either performance or efficiency. This is up to date with the latest AOSP and Linux kernel sources. This is built off January security but "should" work on older builds as well.
See changelog for changes and enjoy.