Related
I use Omni on the Find 7a. There's a lot of chatter about LVM in that development thread, over in AOSPA too. I'm just wondering how mature this feature is before I go about flashing one of the LVM ROMs. Are they stable enough as a daily drivers? Thanks!
RonaldusMagnus said:
I use Omni on the Find 7a. There's a lot of chatter about LVM in that development thread, over in AOSPA too. I'm just wondering how mature this feature is before I go about flashing one of the LVM ROMs. Are they stable enough as a daily drivers? Thanks!
Click to expand...
Click to collapse
For sure !
stable is stable but it's still experimental, this means it may change in future and they don't promise nothing about stability
I do not use due the fact 3g data is good for me,I have 2 games and social
but you are free to try and if there's some problem go back to split layout
be sure to use always lvm compatible Rom and backup to your sd all apps daily
avoid backup in internal memory due the fact it's inside lvm cluster
I had been wondering if I was having some LVM-specific issues on my device, but it turns out the issues were a different patch I'd applied at about the same time I started working with LVM. Ooops.
Right now other than some recovery user interface/user experience issues, and some SELinux logspam I need to fix, there aren't any issues with LVM itself. Any issues you'll encounter on an LVM-capable package will affect the same firmware with a standard layout too.
Remixed Kernel
/only for KitKat/
Remember i am not an developer, this is just my personal builded kernel for my own needs.
Also i am not responsible if your device bricked or else, i give my best and test every build that bad things don't will happen.
If you want to support my work, you can do it here
Changelog remixed.kernel-sr1
- GPU OC up to 512 Mhz
- Fixed OC up to 1,6 Ghz
- Revert few commits for performance reason
DOWNLOAD KERNEL HERE
Sources proper the GPL
Last but not least, my biggest thanks and with them credits goes to:
@Ziyan, @MWisBest, @pattyboi:), @franciscofranco, @boype, @bsmitty83, @osm0sis, @Christopher83 and all other i have forgotten :good:
Reserved for future...
So you decided to share it. Thank you
Nice. Got the sources listed anywhere? I want to create my own personal SuperRAM version. (Plus...that GPL stuff ya know )
redj12 said:
So you decided to share it. Thank you
Click to expand...
Click to collapse
Yes, its ready and as i think good to go but this will show the time.
Culex316 said:
Nice. Got the sources listed anywhere? I want to create my own personal SuperRAM version. (Plus...that GPL stuff ya know )
Click to expand...
Click to collapse
Github can be found in my profil...
I flashed this kernel on omni ROM and it works very well, my phone works smoothly
f2fs support?
It has same features as franco kernel so if francos has it, this also has it
Testing!!! thanks for keeping the scene alive. I'll back with comments.
Edit: not working for me. It doesn't pass boot animation. Vanir ROM with /data and /cache in F2FS.
Wiped cache and dalvik and neither works.
sergialess said:
Testing!!! thanks for keeping the scene alive. I'll back with comments.
Edit: not working for me. It doesn't pass boot animation. Vanir ROM with /data and /cache in F2FS.
Wiped cache and dalvik and neither works.
Click to expand...
Click to collapse
franco doesn't support F2FS because F2FS is bullsh*t.
qtoo941 said:
franco doesn't support F2FS because F2FS is bullsh*t.
Click to expand...
Click to collapse
Strange... I'm pretty sure I've read that it was supporting F2FS. Anyway... I won't argue if F2FS is good or bad. I've been using it since BSmitty featured it first time in the GNex, and I'm satisfied. So... back to my beloved Fancy, which supports F2FS without inconvenience.
qtoo941 said:
franco doesn't support F2FS because F2FS is bullsh*t.
Click to expand...
Click to collapse
how is f2fs bullsh*t.
pattyboi:) said:
how is f2fs bullsh*t.
Click to expand...
Click to collapse
f2fs is just experimental. tried it and actually .. it is not as stable as ext4. the whole story about f2f's performance over ext4's performance is just placebo effect. tried it on galaxy nexus and also on s4.. both models without any real benefit from f2fs system. EXT4 is just better and most stable. that's it.
Don't really know much about f2fs because i never used it...
But if you want it, i can add it into the kernel then you can take your decision what you want use
qtoo941 said:
f2fs is just experimental. tried it and actually .. it is not as stable as ext4. the whole story about f2f's performance over ext4's performance is just placebo effect. tried it on galaxy nexus and also on s4.. both models without any real benefit from f2fs system. EXT4 is just better and most stable. that's it.
Click to expand...
Click to collapse
mind i ask which kernel you tried f2fs with on a gnex? i gain 200+ mbs on writes with f2fs on my gnex on a bad day. && how can you actually prove is just placebo? have you done tests showing it doesn't gain ANY write/read performance compared to ext4?
Guys please... if you wanna have f2fs support hit "THANKS" lets see how many want it.
This shows how many need it and want it, if enought need/want it i will add support in next release
sgspluss said:
Guys please... if you wanna have f2fs support hit "THANKS" lets see how many want it.
This shows how many need it and want it, if enought need/want it i will add support in next release
Click to expand...
Click to collapse
I did it in the OP. If you don't mind, please try to support it as long as you can. Thanks.
Enviado desde mi Galaxy Nexus usando Tapatalk 2
sgspluss said:
Guys please... if you wanna have f2fs support hit "THANKS" lets see how many want it.
This shows how many need it and want it, if enought need/want it i will add support in next release
Click to expand...
Click to collapse
f2fs support was in r398, franco just missed one or two commits for the ramdisk i think so f2fs didn't work....but @osm0sis'es last synapsed version works very well with f2fs on data and cache and system on ext4.
i think he gave permission to use his latest ramdisk
pattyboi:) said:
mind i ask which kernel you tried f2fs with on a gnex? i gain 200+ mbs on writes with f2fs on my gnex on a bad day. && how can you actually prove is just placebo? have you done tests showing it doesn't gain ANY write/read performance compared to ext4?
Click to expand...
Click to collapse
fancy and smitty. yes, it shows upgrade in w/r performance at tests but there is no feeling of anything better compared to ext4. Do you know why PA-Team has never supported f2fs? Totally because it's experiment. The same like ART in KitKat. You can send logs to check some bugs only if its on dalvik runtime, but if you were on art runtime nobody would even check your log. ART became official and fully stable in lollipop... i truly think that f2fs can become more stable but i don't actually know when. At this moment ext4 has nearly the same performance as f2fs but is times more stable. It is not worth spending this stability for such a performance upgrade.
qtoo941 said:
fancy and smitty. yes, it shows upgrade in w/r performance at tests but there is no feeling of anything better compared to ext4. Do you know why PA-Team has never supported f2fs? Totally because it's experiment. The same like ART in KitKat. You can send logs to check some bugs only if its on dalvik runtime, but if you were on art runtime nobody would even check your log. ART became official and fully stable in lollipop... i truly think that f2fs can become more stable but i don't actually know when. At this moment ext4 has nearly the same performance as f2fs but is times more stable. It is not worth spending this stability for such a performance upgrade.
Click to expand...
Click to collapse
I find F2FS absolutely stable, and I don't know in what manner it could compromise stability.
ART is working amazingly well in my Moto G, so I don't agree when you saying it's an experiment in KitKat. The fact that ART is choking for our GNex, doesn't mean it's an experiment. Are you a Google engineer to say that ART is fully stable in lollipop?. I think it never won't work smooth in our devices.
You defend EXT4. I defend Dalvik
ok i have a samsung galaxy SM-T700 what rom and kernal has F2FS support i have searched the forms but nothing for this model came up with a answer.....
thanks very much in advance..
Monster212 said:
ok i have a samsung galaxy SM-T700 what rom and kernal has F2FS support i have searched the forms but nothing for this model came up with a answer.....
thanks very much in advance..
Click to expand...
Click to collapse
Probably none of them do. Developers usually only implement F2FS if the device has slow write speeds on its built in eMMC, such as the original Nexus 7 (and a few others). Some devices have native F2FS support such as the Nexus 9 (which is why it gets its extremely high bench scores). However for this device, it has plenty fast storage already, so the benefit would be almost impossible for the human senses to notice. With all that said, I too would love to use F2FS on at least the cache partition.
SkOrPn said:
Probably none of them do. Developers usually only implement F2FS if the device has slow write speeds on its built in eMMC, such as the original Nexus 7 (and a few others). Some devices have native F2FS support such as the Nexus 9 (which is why it gets its extremely high bench scores). However for this device, it has plenty fast storage already, so the benefit would be almost impossible for the human senses to notice. With all that said, I too would love to use F2FS on at least the cache partition.
Click to expand...
Click to collapse
thank you very much for the reply.. i learned something new...
Monster212 said:
thank you very much for the reply.. i learned something new...
Click to expand...
Click to collapse
Actually, if you install TWRP recovery from here http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Then you can have F2FS support. You then just need to look for a rom that supports F2FS, or a kernel that does. I'm still looking myself, so not sure if any ROMs actually do support F2FS yet, but at least you already have F2FS format support. :good:
SkOrPn said:
Actually, if you install TWRP recovery from here http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Then you can have F2FS support. You then just need to look for a rom that supports F2FS, or a kernel that does. I'm still looking myself, so not sure if any ROMs actually do support F2FS yet, but at least you already have F2FS format support. :good:
Click to expand...
Click to collapse
Thank you for the info, I will now be looking for a good rom or kernal.....
Sent from my SM-T700 using Tapatalk
You can test my kernel here: http://forum.xda-developers.com/showthread.php?t=3139716
ashyx said:
You can test my kernel here: http://forum.xda-developers.com/showthread.php?t=3139716
Click to expand...
Click to collapse
thank you i will install it now and see how it goes...
I would like to do benchmark test results for before and after F2FS. Curious how it compares to my Nexus 7. On cache it was a good performance increase, but on system it did nothing better. EXT4 seems to be the better file system for the system partition, at least on my Nexus 7.
Sent from my SM-T700 using Tapatalk
SkOrPn said:
I would like to do benchmark test results for before and after F2FS. Curious how it compares to my Nexus 7. On cache it was a good performance increase, but on system it did nothing better. EXT4 seems to be the better file system for the system partition, at least on my Nexus 7.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
The kernel I posted doesn't support f2fs on the system partition nor does my guide include it.
As you rightly stated the system partition does not benefit from f2fs as its read only. Ext4 is capable of high read speed.
ashyx said:
The kernel I posted doesn't support f2fs on the system partition nor does my guide include it.
As you rightly stated the system partition does not benefit from f2fs as its read only. Ext4 is capable of high read speed.
Click to expand...
Click to collapse
Yeah agreed, EXT4 is slightly faster at reading, but just by a hair on my N7. However, on partitions that have write permissions, it can "sometimes" be three times faster at random writes. I been using F2FS since feb 2014 "religiously" on my Nexus 7 (and wont run a non-f2fs setup on it), so I am very well versed in its use. Legolas was the first one to bring it to custom Android (I know because I was one of his support techs helping users convert to it, until he disappeared that is lol. Then I started helping USBhost with CarbonROM), and was the first to release a F2FS app in the play store. He was also the first, and only individual, to have a Conversion app to convert your ROM to f2fs, which gave new life to my N7 and any ROM I tried back in 2014 (it did not support 5.0 though). Without F2FS, sadly my Nexus 7 is almost worthless.
If only I can find the many screenshot test results we've done with F2FS, it would come in handy here too. On the N7 its a night and day difference, but here this device is already plenty fast. Id love to see some insane results though.... If only Jaegeuk would develop a Windows driver already. I would like to use it for my Linux box, Windows and Android tbh, and format the sdcards with it, and maybe even USB storage drives to try and pick up on the write speeds a bit. Well see I guess...
My SkyHigh TW LL 5.0.2 kernels support both EXT4 and F2FS for DATA and CACHE partitions.
Note: You need to have supported base firmware for successful flash.
Deathly Aosp Kernel supports Ext4 and f2fs on cache and data
Rom support for it is included on aicp, slim, carbon, liquid
deadman96385 said:
Deathly Aosp Kernel supports Ext4 and f2fs on cache and data
Rom support for it is included on aicp, slim, carbon, liquid
Click to expand...
Click to collapse
ANY ROM can support F2FS. Its just the Kernel that needs to be built with support.
It's possible to convert any partition using various scripts (adjusted to suit device) that are about. But the easiest way is to use ashyx F2FS recovery. It saves a lot of pain.
UpInTheAir said:
ANY ROM can support F2FS. Its just the Kernel that needs to be built with support.
It's possible to convert any partition using various scripts (adjusted to suit device) that are about. But the easiest way is to use ashyx F2FS recovery. It saves a lot of pain.
Click to expand...
Click to collapse
Yeah the roms i listed already have native support no scripts or anything because the f2fs lines have been added too the fstab. So all you need to do is format cache and data in twrp and your done.
deadman96385 said:
Yeah the roms i listed already have native support no scripts or anything because the f2fs lines have been added too the fstab. So all you need to do is format cache and data in twrp and your done.
Click to expand...
Click to collapse
Those ROMs probably use a kernel which has already been patched for F2FS and compiled in-line with the ROM.
Same goes for my SkyHigh kernel, but compiled on its own. All you need to do is format your relevant ROM partitions via script or supported F2FS TWRP. No difference to method except having to flash the kernel separately.
UpInTheAir said:
Those ROMs probably use a kernel which has already been patched for F2FS and compiled in-line with the ROM.
Same goes for my SkyHigh kernel, but compiled on its own. All you need to do is format your relevant ROM partitions via script or supported F2FS TWRP. No difference to method except having to flash the kernel separately.
Click to expand...
Click to collapse
Yep they include my deathly kernel which has f2fs, but without that fstab changes it wont boot on aosp if you convert it unless the tab s is different
deadman96385 said:
Yep they include my deathly kernel which has f2fs, but without that fstab changes it wont boot on aosp if you convert it unless the tab s is different
Click to expand...
Click to collapse
It's the same (similar) ramdisk fstab changes for Samsung based kernel as well, not just source. Edit: As I said, all you need to do to actual "ROM" is just format the relevant partitions.
Hello everyone, after a great success on building roms for bacon device. I've decided to share my work with other devices. So I've started with angler! After positive feedback on the rom today I'll publish here the rom.
Kernel and Device tree are untouched so everything should be working smoothly. You can use a custom kernel in case you like, but i'll only give support to stock kernel as I do not yet own an device. So CM bugs are basically also our bugs, and from what I know there is none. Still I'm open to suggestions.
Download
GAPPS
Features:
Updated SQL to 3.9.0.2
Optimized SQL code for faster Read/Write
CM Super User (for now is the most stable one)
Kernel with F2FS support
Improved Code of frameworks
Optimized Build with custom toolchain on ROM and Kernel
Optimizations for our chip
Improved sound with speex resampler
Improved bionic with many optimized libraries (faster rom)
Improved Art with upstream patches
Optimized native frameworks for our device
LZMA updated to the latest
Proguard 5.2.1
Google Webview
F2FS ready for data and cache
Immersive mode
Expanded Notifications
CAF Task Manager
Snapdragon Camera
Network Monitor
More coming soon
I'm a very praticle user, and my aim will be to get a very fluid stable system, at same time with speed and battery, keeping most stock possible with the optimizations which will improve for real our experience.
Thanks
As you might know, all credits go to CyanogenMod Team.
Source Code
If you like my work, please consider a donation.
Reverve
Frequently Asked Questions:
Q: What changes have you made between versions?
A: All changes made are the same as CyanogenMod ROM which can be found here: http://www.cmxlog.com/13/bacon/ and all manual changes will be also stated on 2nd post.
You can also check on Settings --> About where is all the changes .
Q: What is LZ4?
A: Read here about the project: https://github.com/Cyan4973/lz4
Q: Was latest build used LZ4?
A: This is still under testing and I'm working on it. It'll be on the test folder.
Q: What is the test folder?
A: Unstable, and test builds where I seek to study a new configuration to enhance user experience.
Q: Why don't you always share change logs?
A: Limited time. Sorry about it.
Q: Why do you many times ask for donations?
A: Well... This work is free, and as you know if you like it and on your own free will you think I deserve and currently wish to help me out as I am currently going to become unemployed and as also I study for my Masters in Finance , I believe is only fair. While you use, I'm testing and investing my time on it. Should be rewarded because of that right? Is only fair.
Q: Do you receive alot of donations?
A: Since last year until today I've received around 300 euro. But I've invested 1000 hours on these android builds. That gives a ratio of 30 cents an hour.
Q: Why do you still invest on android since it doesn't provide you any feasible income? I would have already quited!
A: Basically this forum makes me relax.
Q: Will you leave cm builds when exodus is released ?
A: I didn't plan on giving my cm builds, but if exodus prove to be superior why should i have double work right? Only time and users will tell.
Q: I'm confused. I have no clue which build is the latest!
A: You can always download again!
Q: Your site have ads why?
A: Need help on extra wealth to survive. Leave some clicks while you visit is only nice.
Q: I want more from the rom!
A: Me too!
Q: Why you sometimes ignore users?
A: I never ignore, just don't have time to answer all. Please help one another and also use search button. I think you prefer me learning to bring something nice than post all the time right? hehe
Q: I have so many questions to ask you!
A: I can provide many answers! Just ask!
Q: Can I PM you?
A: Only when is urgent!
Q: How to report bugs?
A: Our bugs are CM bugs. Report on JIRA: https://jira.cyanogenmod.org
Q: Are you CyanogenMod maitainer?
A: No, just an user which wants to have better builds possible. But would be nice to see CM adding me to the contributions list.
Q: Why Slim gaaps? Open Gaaps are so much cool!
A: Open Gaaps has provided many unstable issues which makes the phone unusable until a clean format. Slim gaaps have shown to be better on that.
Q: Why some buttons of UKM don't work?
A: Need time to improve that..
Q: I want an update app to auto update roms. To lazy to check the thread!
A: I understand, for now is not feasible to do it as I need time to analyse and understand best solution as I update tool-chains regularly and also is not my priority. Remember time is limited for me.
Just to clarify, TWRP for Angler still cannot format partitions to F2FS, correct?
tibere86 said:
Just to clarify, TWRP for Angler still cannot format partitions to F2FS, correct?
Click to expand...
Click to collapse
Actually I dont know casue this is old, but TWRP is well advanced now, https://plus.google.com/+ChetKener/posts/7No16fUQaFz
Oh wow.. Ur ROM was the first custom ROM i had on OPO.. Nice to see you here
I have to admit I didn't check yet on cm source but I'll review.
yung40oz84 said:
Actually I dont know casue this is old, but TWRP is well advanced now, https://plus.google.com/+ChetKener/posts/7No16fUQaFz
Click to expand...
Click to collapse
@jgcaap What do you say about that? Is it worth installing the rom without F2FS?
Do we need to flash the correct vendor image from February's security patch?
Kookitza said:
@jgcaap What do you say about that? Is it worth installing the rom without F2FS?
Click to expand...
Click to collapse
Will work both ways... But f2fs is very nice.
jgcaap said:
Will work both ways... But f2fs is very nice.
Click to expand...
Click to collapse
But F2FS is not work on our device so....
jgcaap said:
Will work both ways... But f2fs is very nice.
Click to expand...
Click to collapse
Yes, I have heard good things about it! So if I do not change /system to F2FS then I will be able to flash this ROM and other ROMS as normal correct? As long as they support F2FS of course for the other partitions I have converted. But some recommend system as F2FS as well, if I did that then what is the draw back? I would have to convert ROMS to be able to flash correct?
Sent from my Nexus 6P using Tapatalk
Kookitza said:
But F2FS is not work on our device so....
Click to expand...
Click to collapse
Oh. Didn't know that. I'll remove my comment. Thanks. Please try out everything and let me know if is all working well.
jgcaap said:
Oh. Didn't know that. I'll remove my comment. Thanks. Please try out everything and let me know if is all working well.
Click to expand...
Click to collapse
I don't know this for sure. I read that in one of the previous comments. Maybe someone can confirm this.. [emoji53]
Sent from my Nexus 6P using Tapatalk
When you say no bugs, did you fix the broken Bluetooth?
jclendineng said:
When you say no bugs, did you fix the broken Bluetooth?
Click to expand...
Click to collapse
Cm has also that bug?
Does this ROM force encryption?
Sent from my Nexus 6P using Tapatalk
Tomorow I'll answer all questions calmly as tomorow I have an exam. I want to deliver here what I delivered on bacon. Smooth experience.
Until then please test and let me know any bugs. Thanks!
Is anyone having issues with the camera?
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.