Hi guys,
I'm by no means a pro at kernel building but I've put lots of effort into this kernel so I thought I'd share it with you. I do not own a Moto X so I haven't had a chance to test it. The kernel is still in testing stage and optimised with Linaro 4.10.0 toolchain. It's built from source and has added tweaks such as those used by Faux in his kernel.
This is for stock ROM only.
For GSM devices with unlocked BL.
It should work in theory but since I do not own the device, I can't be certain.
Kernel Source: here
If someone would be kind enough to test them for me, I'd be really thankful.
ISSUES:
Code:
# Please point out if any
Download Links:
Code:
Initial Release (boot.img) : First release to see if everything is in order.
[URL="http://www.androidfilehost.com/?fid=23501681358562192"]boot.img[/URL]
If the kernel boots and you would like to use it as daily driver, flash [URL="http://www.androidfilehost.com/?fid=23501681358562191"]this[/URL] zip.
Also, you will not end up in a bootloop or lose data after flashing this kernel. Just use the command
Code:
fastboot boot boot.img
instead of
Code:
fastboot flash boot boot.img
and if there are any problems, your phone will come back to the original state on next boot.
If the kernel crashes or fails to boot, please get me a last_kmsg so I can debug it.
Code:
adb shell cat /proc/last_kmsg > kmsg.txt
or a logcat
Code:
adb logcat
Changelog: here
Code:
fixed compilation error
updated touchscreen drivers
WIP:Intelli_Plug by Faux123
drivers/usb/gadget/f_qdss.c: gcc 4.8 fixup
drivers/Makefile: add exFat support
Added exFat support
drivers/tty/n_tty.c: fix CVE-2014-0196
Optimized autosleep.c
powersuspend: new PM kernel driver for Android w/o early_suspend
Added CPUfreqs
Updated cgroup_subsys.h for build bits for BFQ-v6-3.4
Add BFQ, FIOPS, SIO I/O scheduler
lib/lzo: Update LZO compression to current upstream version
fix compilation errors
Makefile: add some optimization flags for ARM
ext4: add support for read_iter and write_iter
Updated crypto/Makefile
crypto: Add lz4 Cryptographic API
WIP: Add LZ4 compression support
arch/arm/Kconfig: enable unaligned capability for ARM
scheduler: compute time-average nr_running per run-queue
lib/string: use glibc version
added memcopy libs
Pronto WLAN: Merge with Kernel tree
Ramdisk tweaks and fixes
fixed derpy kernel source by Moto
Can anyone confirm this to be working?
Plz list the features of the kernel too. Ill try when I reach home. And thanks for your work
Tried to use the fastboot boot boot.img command but fastboot gives me INFOCommand restricted. This must be for bootloader unlocked devices I'm assuming?
As soon as I get home I'll give this a whirl. Is this for all Ghost phones or T-Mobile only. Verizon? 4.4.2 or 4.4.3?
EDIT/UPDATE
Does not boot on Verizon Developer Edition running Eclipse V3.3 (Android 4.4.2)
Bootloops and gets stuck on warning screen.
bootloaderloader command restricted error after using command. Im on Sprint X1056
Edit: btw My bootloader is unlocked soo.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rebretz000 said:
As soon as I get home I'll give this a whirl. Is this for all Ghost phones or T-Mobile only. Verizon? 4.4.2 or 4.4.3?
EDIT/UPDATE
Does not boot on Verizon Developer Edition running Eclipse V3.3 (Android 4.4.2)
Bootloops and gets stuck on warning screen.
Click to expand...
Click to collapse
Same for Sprint XT1049 (Republic Wireless) version.
For comparison, I installed the Faux kernel last night for the first time. I also use the Greenify app. Rooted Stock ROM, Verizon Dev model Moto X...
I am about 11 hours into my day, and would normally be down to about 30% battery left. I'm at 53% with same type of moderate usage today.
Highly recommend Faux and Greenify...solid and stable. I'm using the 008m version...
http://forum.xda-developers.com/moto-x/orig-development/kernel-007-kk442-gsm3-4-hybrid-oc-t2645356
hijax2001 said:
For comparison, I installed the Faux kernel last night for the first time. I also use the Greenify app. Rooted Stock ROM, Verizon Dev model Moto X...
I am about 11 hours into my day, and would normally be down to about 30% battery left. I'm at 53% with same type of moderate usage today.
Highly recommend Faux and Greenify...solid and stable. I'm using the 008m version...
http://forum.xda-developers.com/moto-x/orig-development/kernel-007-kk442-gsm3-4-hybrid-oc-t2645356
Click to expand...
Click to collapse
That's great and all. But this is his thread and to help get his kernel up and going.
Sent from my XT1053 using XDA Premium 4 mobile app
It's nice someone is attempting to provide us with another option. I like Faux's and Krypto's but would like to try another option.
Will try this on xt1053. In the process of trying to calibrate battery. Stays on 1% for hours and I'm currently at 1%. So when I fully charge I'll let you know how it goes.
Sent from my XT1053 using XDA Premium 4 mobile app
Thanks a lot to everyone trying to boot this kernel. Really appreciate it.
Please report your tests in the following manner:
1. Ghost model
2. CDMA/GSM
3. Android version
Also, can someon give me the stock boot.img for all variants of Moto X? That would be really helpful.
Can someone test it on XT1058 (international GSM) first?
Cheers!
1. X1056
2. CDMA (Sprint
3. 4.4.2
It doesnt boot, gives a bootloader command restricted error.
Boot.img for X1056
XT1060 Verizon Developer Edition
CDMA
Eclipse ROM V3.3 (Android 4.4.2)
Phone bootloops at warning screen after flashing
Stock kernel. https://www.dropbox.com/s/ltkwk42ma6swr2w/boot.img
1)XT1049
2)CDMA
3)4.4.2
Bootloop on bootloader unlock warning
Sent from my XT1049 using XDA Free mobile app
1. Xt1058
2. Rogers GSM .
3. Boot loops on latest krypton. 4.4.3
Bootloop.
XT1080DE
Verizon
Stock 4.4.4
boot.img
1. xt1053
2. gsm
3. 4.4.3 gpe
Bootloop at bootlogo.
xt1053 4.4.3 boot.img https://www.dropbox.com/s/8gfsw4r7cvmmx8o/boot.img
Sent from my XT1053 using XDA Premium 4 mobile app
XT-1052
Retail version
Boot loop
Boot.img ---->https://drive.google.com/file/d/0B_TBj5SDLI2eR09KdW1sRHJoZ2c/edit?usp=sharing
newhor1z0n said:
Thanks a lot to everyone trying to boot this kernel. Really appreciate it.
Please report your tests in the following manner:
1. Ghost model
2. CDMA/GSM
3. Android version
Also, can someon give me the stock boot.img for all variants of Moto X? That would be really helpful.
Can someone test it on XT1058 (international GSM) first?
Cheers!
Click to expand...
Click to collapse
Sprint (xt1056) source for latest build I do believe.....HERE
Related
R800x Users, I have just compiled a kernel based of the 3.0.1.E.0.88 Sources.
I need a few testers, Big update, read the update section for v.2 (2012 Feb 12)
Pax
Update 01: 2012 February 08 1500 CST:
Code:
Working:
Stock kernel (no overclocking yet)
Boots
No random reboots (yet)
Autobrightness is disabled (as it was in 2.3.3 update)
Not Working:
Wifi (came from DooMLoRD's Kernel, need to check coming from stock update: need to flash Doom's stock wifi)
Recovery (need to look into this, in the meanwhile, use market link below)
Will be added Later:
Governers
I/O Schedulers
Overclocking
Auto-rooting
Note: This kernel's ramdisk is ro.secure = 0, which means it can be rooted, you'll just have to do the work.
Update 2012 February 08 -- 1900
Attached boot.img
Update: 2012 February 12 -- 2020
Code:
Big update to the kernel
I switched from my ramdisk, which ended up being a headache to DooMLoRD's v10 ramdisk
That means:
Wifi Works
Autoroot (should) work (I haven't tested it yet)
Recovery Works
New Splash on boot (thanks [URL="http://forum.xda-developers.com/showthread.php?t=1494076"]KeiranFTW[/URL] )
What I've added:
Overclocking is possible up to 2.0ghz (be warned, I have not had a chance to completely test it out, and my device only works up to 1.6ghz) (Freqs are from DooM v10)
Governors added:
brazillianwax
smoothass
smartassv2
savagedzen
interactivex
lagfree
Scary
smartass
Original governers
UPDATE: 2012 Feb 12 1055
Noticed that when I switched to DooMLoRD's ramdisk, autobrightness got re-enabled. Fixed that. Uploaded new kernel.
UPDATE: 2012 Feb 13 1335
Changed version from .2 to 1.0
Added IO Schedulers:
Anticipatroy
CFQ
V(R)
SIO
UPDATE: 2012 Feb 13 -- 1400
Realized last update unintentionally removed governors, as soon as I get a stable internet connection, i'll upload completely working kernel.
UPDATE: 2012 Feb 13 -- 1525
Uploaded fixed kernel.
Note: I am not to be held responsible if your device fails you. By flashing this, you are taking your device's ability to work into your own hands. ESPECIALLY WITH OVERCLOCK. TEST BEFORE YOU DECIDE TO SET ON BOOT. IF YOUR PHONES FAILS YOU, IT IS YOUR RESPONSIBILITY
Follow these instructions from Doom if you don't know what to do
download the boot.img
save the boot.img in the folder with fastboot binaries (fastboot.exe files)
power down device
start device in fastboot mode
use the following command to flash the boot.img
Code:
fastboot -i 0x0fce flash boot boot.img
reboot phone and enjoy the kernel
What's Left to be added:
What do people want?
To get into recovery, use the exact same key as you would on DooM's
Sources for code:
Github -- Ramdisk (From ftf, if you really want to mess with this, have fun, but it's not worth the time.): https://github.com/paxchristos/R800x-Ramdisk
Github -- Kernel Source: https://github.com/paxchristos/R800x-2.3.3-Kernel
Big thanks to Keiran/Doom for the help in getting this to work.
Reserved for future use
Any modifications regarding I/O schedulers & CPU governors? Any additional kernel modules?
CrimsonKnight13 said:
Any modifications regarding I/O schedulers & CPU governors? Any additional kernel modules?
Click to expand...
Click to collapse
There well be, as of right now, this is pretty much an alpha release. I'm in class for a little bit, then I'm going to actually flash it (
I just did a fastboot boot) and start bug checking ...
Sent from my R800x using Tapatalk
paxChristos said:
R800x Users, I have just compiled a kernel based of the 3.0.1.E.0.99 Sources.
I need a few testers, I will post soon (I literally just got it to boot)
expect more info soon!
Pax
Click to expand...
Click to collapse
I'm game for trying it out.
With this kernel we can overclock? Like with SetCPU?
I'll try this later when some other stuff is fixed. But nice job.
Is this a kernel for 2.3.3?
What's to prevent you from grabbing sources from a later version and doing this?
i think this kernel is for unlocked bootloaders???
Because locked can't flash kernels
nickholtus said:
i think this kernel is for unlocked bootloaders???
Because locked can't flash kernels
Click to expand...
Click to collapse
There can be kernels that can be flashed with CWM Recovery.
I'm SOOO ready to test! Hit me with your best shot!
EDIT: Do you think this kernel will eventually evolve into a kernel that will be able to boot Cyanogenmod and/or MIUI? I'm assuming that's what you're aiming for. lol
Nope we can't flash kernels with cwm on SEMC devices
PariahLantern said:
Is this a kernel for 2.3.3?
What's to prevent you from grabbing sources from a later version and doing this?
Click to expand...
Click to collapse
I have a R800x (the Verizon Xperia Play) and I play to focus development on sources exclusively for the R800x. If the R800x gets new sources, I will update code based on that, not sources for GSM.
nickholtus said:
i think this kernel is for unlocked bootloaders???
Because locked can't flash kernels
Click to expand...
Click to collapse
You are correct sir, I was updating between classes and posted the wrong info *fixed*
Selim873 said:
There can be kernels that can be flashed with CWM Recovery.
I'm SOOO ready to test! Hit me with your best shot!
EDIT: Do you think this kernel will eventually evolve into a kernel that will be able to boot Cyanogenmod and/or MIUI? I'm assuming that's what you're aiming for. lol
Click to expand...
Click to collapse
Sorry, only for unlocked boot loaders, my bad
Eventually I might get into other development. First I wanna get this working, perfectly.
nickholtus said:
Nope we can't flash kernels with cwm on SEMC devices
Click to expand...
Click to collapse
Yupp, the /boot partition is locked so we can't flash kernels that way
(hint: if you do (from terminal emulator as root) cat /proc/mtd and you see /boot, you can use CWM to flash kernels.)
Kernel v.1 is uploaded and attached to post 1
Selim873 said:
There can be kernels that can be flashed with CWM Recovery.
I'm SOOO ready to test! Hit me with your best shot!
EDIT: Do you think this kernel will eventually evolve into a kernel that will be able to boot Cyanogenmod and/or MIUI? I'm assuming that's what you're aiming for. lol
Click to expand...
Click to collapse
Probably. We are gonna end up finding another exploit.
paxChristos said:
Yupp, the /boot partition is locked so we can't flash kernels that way
(hint: if you do (from terminal emulator as root) cat /proc/mtd and you see /boot, you can use CWM to flash kernels.)
Click to expand...
Click to collapse
nope u cant see /boot and it cant be flashed to using CWM (on xperia devices)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DooMLoRD said:
nope u cant see /boot and it cant be flashed to using CWM (on xperia devices)
Click to expand...
Click to collapse
Couldn't we not "find" the boot partition values and then mount the boot partition? Would require a little kernel editing but would be well worth it.
KeiranFTW said:
Couldn't we not "find" the boot partition values and then mount the boot partition? Would require a little kernel editing but would be well worth it.
Click to expand...
Click to collapse
I didn't think about that! I would love to try to get at it, but I'm only a user and know nothing of development... I'm sure that'll get cracked eventually.
Selim873 said:
I didn't think about that! I would love to try to get at it, but I'm only a user and know nothing of development... I'm sure that'll get cracked eventually.
Click to expand...
Click to collapse
The only problem (that I can see) with what Keiran is suggesting is that the you'd need a custom kernel to affect the /boot partition, which once again, makes it useless for anybody with a locked bootloader...
paxChristos said:
The only problem (that I can see) with what Keiran is suggesting is that the you'd need a custom kernel to affect the /boot partition, which once again, makes it useless for anybody with a locked bootloader...
Click to expand...
Click to collapse
I understand that, but since it was based off the stock kernel, would the values be the same for everybody with a locked bootloader? I know that you meant when you said that, but what I was thinking was that someone could dig around the kernel to find those values and what trigger the /boot partition in the first place, then use the correct adb shell command, whatever it is, to make that show up on locked devices. Whether the device is on it's recovery mode (Back+Power) or fastboot (Search+Power) state. Like I said, I don't know anything about developing, and I might just be walking off a cliff at the moment, but it's just a thought.
EDIT: As in looking and thinking on the modified "stock" kernel, and applying on the locked devices. Trial and Error.
Just a quick update,
I'm trying to get the overclocking working, but right now it's being a stone cold b*tch with compiling
As soon as I get it working, i'll upload a new kernel version
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Only for CM 13.0-based ROMs!
Downloads:
https://www.androidfilehost.com/?w=files&flid=51727
Supporting my work:
To motivate me and keep me going, simply click the 'thanks' button.
XDA:DevDB Information
zwliew Kernel, Kernel for the Moto X
Contributors
zwliew
Source Code: https://github.com/zwliew
Kernel Special Features: Smooth performance? Check. Solid battery life? Check. Customization options? Check. Enjoy.
Version Information
Status: Stable
Current Stable Version: r13
Stable Release Date: 2016-03-10
Created 2014-11-02
Last Updated 2016-03-10
Changelogs:
r13
Fixed several kernel vulnerabilities
Fixed several cpufreq issues - most notably the bug whereby CPU1 is stuck on 1.5 GHz (patch awaiting approval from CM)
Fixed a whole ton of deadlocks and issues in the scheduler subsystem, potentially improving performance and power
Fixed many issues in several kernel subsystems (including patches from CAF and Linux-stable)
Increased IO performance
Reduced boot times (patch partially merged by CM)
Enabled and optimised a kernel option that allows the CPUs to go to idle states faster, improving power consumption
Merged a series of patches that simplify the hotplug architecture greatly, improving power consumption
Many other misc. improvements and fixes - check out the GitHub!
Features coming soon:
FauxSound (or a similar sound control driver)
Color calibration
The kernel is pre-tweaked for a nice balance between smooth, buttery performance, and solid battery life.
If the expert in you absolutely wants to customise some more, stay tuned for further documentation!
I guess you have provided a wrong kernel in your directory. I think the one you have provided is for Samsung Ace 2. Plz look into it. Really would like to try your kernel.
Downloaded the file zwliew-kernel-r1.zip
Got error in recovery. After checking updater script, it appears something is wrong
Booted with Krypton Rom 1.4.1
Need feedback and I install ?
Sent from my XT1052 using XDA Free mobile app
athulele said:
Downloaded the file zwliew-kernel-r1.zip
Got error in recovery. After checking updater script, it appears something is wrong
Click to expand...
Click to collapse
What error is it? I'll take a look soon.It seems fine to me.
DaRkRhiNe said:
I guess you have provided a wrong kernel in your directory. I think the one you have provided is for Samsung Ace 2. Plz look into it. Really would like to try your kernel.
Click to expand...
Click to collapse
I've updated the links, go check it out.
Good work friend.... Impossible flash in XT1052 with TWRP.....
isaakmg said:
Good work friend.... Impossible flash in XT1052 with TWRP.....
Click to expand...
Click to collapse
Sorry guys! I screwed up big time! The links were all garbled
Now they work fine.
zwliew said:
Sorry guys! I screwed up big time! The links were all garbled
Now they work fine.
Click to expand...
Click to collapse
Booted fine here with latest fix, everything working so far. Krypton 1.4.1 xt1060
boots fine with epsilon 3.1. Will report if I find any bugs
isaakmg said:
Good work friend.... Impossible flash in XT1052 with TWRP.....
Click to expand...
Click to collapse
That's what happened to me.
XT1060 TWRP 2.8.1.0 Krypton 1.4.1
isaakmg said:
Good work friend.... Impossible flash in XT1052 with TWRP.....
Click to expand...
Click to collapse
rebretz000 said:
That's what happened to me.
XT1060 TWRP 2.8.1.0 Krypton 1.4.1
Click to expand...
Click to collapse
I've updated the download links a little while ago. Are you sure you're flashing the file "zwliew_ghost_r1.zip"? That is the kernel.
Running on XT1053 4.4.4 Generic GSM FXZ.
Flashed with TWRP 2.8.1
Sent from my XT1053 using XDA Free mobile app
kenosis said:
Running on XT1053 4.4.4 Generic GSM FXZ.
Flashed with TWRP 2.8.1
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Any question Work in stock rom 4.4.4 sprint rom whit root and recovery brot ????
makysssdroid said:
Any question Work in stock rom 4.4.4 sprint rom whit root and recovery brot ????
Click to expand...
Click to collapse
It works
Ok I am confused why are the build dates of all the files JULY but the commits are as new as 10 hours ago?
Anyone seen any performance improvements or other user noticeable improvements over lets say faux or krypton? Just curious looks like way more activity on this kernel
adm1jtg said:
Ok I am confused why are the build dates of all the files JULY but the commits are as new as 10 hours ago?
Anyone seen any performance improvements or other user noticeable improvements over lets say faux or krypton? Just curious looks like way more activity on this kernel
Click to expand...
Click to collapse
Last and final fix to the links in OP. The downloads are in XDA DevDB downloads section.
http://forum.xda-developers.com/devdb/project/?id=6479#downloads
I messed up the links when copying over from my old XDA thread for another device.
Work on stock rom or CM rom only ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is my custom kernel that I've been using personally since the Nexus 9 was released. I have started updating it more frequently, and it has some unique features that other kernels on this device do not have currently.
Some of the features include:
SELinux Permissive (for root on M)
Faux's Intelliplug
Custom Governors:
bioshock, blu_active, lionheart, zzmoove, yank active, intelliactive
Arm64 topography
BFQ Scheduler (my clear favorite, there are others!)
Graphite Build Optimizations
Uber 5.3.1 aarch64 Toolchain
Linux 3.10.98 (always will be the most current linux stable)
CPU Overclock
No forced encryption
Instructions:
Flash zip in recovery
Flash SuperSU for root
Here's a link to the download (flash via twrp)
https://www.androidfilehost.com/?fid=24438995911967758
Here's a link to source
https://github.com/gchild320/flounder
Please make a backup before flashing. I'm not responsible for anything that happens to your device.
Thanks to anyone and everyone that I've picked commits from. I try very hard to ensure authorship is kept.
I recommend kernel adiutor
V1.3
Upstream Linux 3.10.93
Yankactive Governor
V1.2
Upstream Linux 3.10.60
V1.1
Upstream Linux 3.10.48
No Force Encryption
Flashable zip instead of boot.img
V1.0
Initial release
Reserved for changelog.
Tells me I need to be logged in to download from AndroidFileHost.
access denied
looks like you don't have permission to access this folder. Make sure you are signed in to an account that has permission, or check with the developer to request access.
This is what I get from AFH.
Erik
I found it here
Thanks my fault on the link, fixed.
Sent from my Nexus 6 using Tapatalk
Quick question, does it have the no force encryption also? Didn't see it in the OP.
Thanks.
Sent from my Nexus 6 using Tapatalk
ricco333 said:
Quick question, does it have the no force encryption also? Didn't see it in the OP.
Thanks.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
From my understanding it's not the kernel that forces encryption, but the fstab included while flashing whatever rom. If I'm wrong I will add whatever is necessary to kernel.
Sent from my Nexus 6 using Tapatalk
gchild320 said:
From my understanding it's not the kernel that forces encryption, but the fstab included while flashing whatever rom. If I'm wrong I will add whatever is necessary to kernel.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
fstab is always in ramdisk (so it's inside boot.img). You need to unpack and patch fstab.flounder and fstab.flounder64 (replace forceencrypt to encryptable). I wrote a quick flasheable zip yesterday to edit those files in TWRP, but maybe I missed something and that weird message of corrupted device appears in early boot. After that I flashed fire-ice kernel and it boots normally. I can share my zip with you if you want.
jolinnard said:
fstab is always in ramdisk (so it's inside boot.img). You need to unpack and patch fstab.flounder and fstab.flounder64 (replace forceencrypt to encryptable). I wrote a quick flasheable zip yesterday to edit those files in TWRP, but maybe I missed something and that weird message of corrupted device appears in early boot. After that I flashed fire-ice kernel and it boots normally. I can share my zip with you if you want.
Click to expand...
Click to collapse
Thanks I didn't think of it that way since I usually build ROM+kernel together and end up editing fstab in my device files.
Sent from my Nexus 6 using Tapatalk
Update to v1.1
Upstream Linux changes, no force encryption, flashable zip.
Thanks to @jolinnard for helping me further understand the encryption stuff!
https://www.androidfilehost.com/?fid=24052804347849159
Any plans to add f2fs support? i flashed the latest and hung so i figured it was because my data was f2fs
joeyddr said:
Any plans to add f2fs support? i flashed the latest and hung so i figured it was because my data was f2fs
Click to expand...
Click to collapse
Sure will do.
Sent from my Nexus 6 using Tapatalk
gchild320 said:
Update to v1.1
Upstream Linux changes, no force encryption, flashable zip.
Thanks to @jolinnard for helping me further understand the encryption stuff!
https://www.androidfilehost.com/?fid=24052804347849159
Click to expand...
Click to collapse
You are welcome.
Flashing new build now!
Ahoy "old friend" @gchild320 THX for your work ...
Clean Flash etc & Co tried and nothing has helped. Neverending Bootloop ...
BTW
I saw nice new BrokenOS Marshmallow screenshots ... have or you may know more infos ?!
MotoFlasher said:
Ahoy "old friend" @gchild320 THX for your work ...
Clean Flash etc & Co tried and nothing has helped. Neverending Bootloop ...
BTW
I saw nice new BrokenOS Marshmallow screenshots ... have or you may know more infos ?!
Click to expand...
Click to collapse
I've installed Ubermallow + Slim gapps and ninja kernel. It's smooth and all is running fine and smooth. Kernel is great as far as I can tell.
Hmmm ok
I test again ...
Edit
No idea what was going on ... All good now.
Nice standby ☺
Sent from my Nexus 9 using Tapatalk
gchild320 said:
Nice standby
Click to expand...
Click to collapse
Running great here too... What settings do you have? Never seen bioshock or zzmoove... I'm on bioshock now with hotplug enabled and SIO (CFQ is for hard drives). So far everything seems good (performance and battery).
I run BioShock or Lionheart usually, always underclocked...I don't typically hotplug but as far as schedulers bfq.
Sent from my Nexus 6 using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Back again!
You may remember me from my SkyDragon roms/kernels and HolyDragon kernels for OP6/OP6T/OP3/N6/M8/M7/G3 among other devices. This is the latest sm8150 kernel+audio source from OnePlus. For now just some latency reductions and a couple listed features while I work on optimizing it. No plans for any overclocking cpu/gpu that slowly kill your phone. No plans to upstream anything as most of the time there's either no benefit at all or it performs worse than stock. I don't care about f2fs and recommend only ext4 as the stock filesystem. My only goal, as always, is to get the best performance *and* battery life out of our phone as possible. Kernel zip uses Anykernel3 by Osm0sis to install so no fear of losing root or ramdisk changes or anything.
~*~*Information*~*~
Flashable Kernel zip supports all OnePlus 7 and OnePlus 7 Pro(non-5G) devices running OOS Stable 10.x
Kernel source is based on official OnePlus 7/7Pro unified source code to ensure best performance
No user setup required - Optimal settings already applied
Compiled with Google Clang 9.0.5(r353983e) and gandalf02's aarch64-9.1 GCC
~*~*Features*~*~
250HZ Kernel
ExFat Support
No user clock-speed modifications
BBR TCP Congestion Profile (set as default
CRC Check Toggle-able (disabled by default)
Power Efficient Workqueue's Toggle (enabled)
Maple IO Scheduler (set as default)
Flar2's Wake Gesture support
KCAL
Boeffla Wakelock Blocker
Latest WireGuard Built-In
~*~*Credits and Thanks*~*~
xanaxdroid
SultanXDA/KernelToast
RandomBlame/Kelsirae
Pafcholini
MLucy
Flar2
MyFluxi
DespairFactor
FranciscoFranco
KDrag0n
Osm0sis
Mauronofrio
Joshuos
dabug123
~*~*Downloads*~*~
To Install :
Make sure bootloader is unlocked
Make sure you're on latest TWRP
Download this kernel zip
Reboot device to TWRP
Find this zip and install
Reboot to system and enjoy!
---
Could also copy zip or image to usb otg drive and flash in twrp
Do not flash with EXKM app
For Oneplus 7/7 Pro(Non 5G) and Oneplus 7T/7T Pro(Non 5G)
SDK_OP7TP_OOS10_RV.10.1
Flashable Zip
AFH
GDrive
--
Telegram Group
TG
Discord Server
Discord
~~~~~~~~~~~~~~~~~~~~~~~~
You can find changes(changelog) by looking at my posted source. You can also find my custom toolchain's, crosstool-ng, and other sources listed there. Any bug reports require logcats/dmesg, thanks!
~*~*Donations*~*~
If you want to donate to my coffee fund, I prefer any cryptocurrency over paypal but either is fine.
Donate with Coinpayments
or just use paypal, thanks!
XDA:DevDB Information
[KERNEL][OP7/7PRO][18 SEP][ SkyDragon [OOS10], Kernel for the OnePlus 7 Pro
Contributors
HolyAngel, Liam_Davenport, Imotep95
Source Code: https://gitlab.com/holyangel/OP7.git
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: Current
Stable Release Date: 2019-05-23
Beta Release Date: 2019-05-21
Created 2019-05-21
Last Updated 2020-09-18
SkyDragon OOS Magisk Mod
Reserved
Reserved
Frequently Asked Questions
Before issues should be reported:
1. Rom needs to be clean flashed
2. No Xposed, AKT Profiles, Helix Engine, other magisk modules, or other mods, etc.
3. Do not restore any apps with TiBu or Swift or some other app restoring application
4. No Substratum themes installed
If you can still reproduce the issue you're having:
1. Logcat/logs must be provided with your report in order to receive any support.
2. I also need a full description of what happened, what you were doing when it happened, and a way to guarantee-ably reproduce the problem. If I or my testers cannot reproduce it, not only will it likely not get fixed, it likely isn't even an issue with the rom/kernel.
3. Screen record or picture of the issue is also helpful.
If you're not familiar with how to get logs, you can reference this great XDA Thread here.
If you can't give logs for errors or possible bugs, I literally cannot help you solve it.
Can't wait to try this out! Thanks!!
This could be a really dumb question, but could the zip be flashed in TWRP from a USB DRIVE..?
Or within an app like EX Kernel Manager?
reaper000 said:
This could be a really dumb question, but could the zip be flashed in TWRP from a USB DRIVE..?
Or within an app like EX Kernel Manager?
Click to expand...
Click to collapse
Not dumb at all, you could totally do either of those to flash it :good:
Wireguard support?
JedixJarf said:
Wireguard support?
Click to expand...
Click to collapse
No and won't be until they can pass a security audit. Says right on their site not to rely on their code until they do.
HolyAngel said:
No and won't be until they can pass a security audit. Says right on their site not to rely on their code until they do.
Click to expand...
Click to collapse
No problem thanks ?
Bacc at it again! Great job!
Excellent! I'm assuming Skydragon ROM eventually =).
SoullessMexican said:
Excellent! I'm assuming Skydragon ROM eventually =).
Click to expand...
Click to collapse
Yes will come when it's ready
Wouldn't you think that the CRC toggle is obsolete on any Oneplus device you support.
HolyAngel said:
CRC Check Toggle-able (disabled by default)
Click to expand...
Click to collapse
Hey buddy,
I was having a look at CRC check and what it does.
https://gitlab.com/HolyAngel/op7/commit/818f89d20f197ddf81aa2c8a40551b96173f2c2e
I've noticed your commit is in the mmc driver but given that we have UFS3.0 (not emmc 5.1) and that we don't have a micro SD slot, isn't this a worthless change because we will never be using mmc based storage?
Regards,
Ravi
Sent from my OnePlus7Pro using XDA Labs
Telegram Group
Are there any telegram groups for this kernel/rom?
@HolyAngel
Welcome & thank you.
@HolyAngel I flashed the kernel with EXM and after reboot it shows me a message: "There is an internal problem in your device. Please contact your manufacturer."
Hirs_E_Fruit said:
@HolyAngel I flashed the kernel with EXM and after reboot it shows me a message: "There is an internal problem in your device. Please contact your manufacturer."
Click to expand...
Click to collapse
If the same as on OP6, then you can dismiss it on each reboot. Last year it took a couple of weeks to figure out what caused it and it was subsequently addressed. It doesn't have any impact on the working of your phone.
Sent from my OnePlus7Pro using XDA Labs
rav101 said:
Hey buddy,
I was having a look at CRC check and what it does.
https://gitlab.com/HolyAngel/op7/commit/818f89d20f197ddf81aa2c8a40551b96173f2c2e
I've noticed your commit is in the mmc driver but given that we have UFS3.0 (not emmc 5.1) and that we don't have a micro SD slot, isn't this a worthless change because we will never be using mmc based storage?
Regards,
Ravi
Click to expand...
Click to collapse
Yeah most likely useless at the moment but the stock defconfig compiles the mmc driver anyways.
Hirs_E_Fruit said:
@HolyAngel I flashed the kernel with EXM and after reboot it shows me a message: "There is an internal problem in your device. Please contact your manufacturer."
Click to expand...
Click to collapse
Yes this is the message on boot listed in the op that will be fixed soon. Can safely ignore it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mint Kernel for the Samsung Galaxy A50
Freshen up your Galaxy.
Mint is an optimized kernel source based on Samsung's open-source kernel drops of the Galaxy A50.
Additional features include:
Built with LLVM/Clang (proton-clang) 13
Built with Link-Time Optimizations (LTO) enabled
A fully-revamped Exynos Mobile Scheduler (EMS) optimized for low-latency tasks.
A smarter governor with boost algorithms from the Galaxy S10 as well as 'inferencing' from the S20.
Added additional I/O schedulers, anxiety is set as default.
Various kernel and performance improvements from Linux upstream, and even from Qualcomm devices.
Backported changes from multiple devices, including newer Galaxy devices.
RAM Plus support (requires ROM support), including support for per-process swap.
Disabled basic Samsung hardening (Knox, etc).
Added support for WireGuard VPN tunnel.
Additional I/O schedulers:
Anxiety - set as default for great performance and good battery life
Maple
SIO
Zen
FIOPS
CFQ - optimizations from Android upstream
Additional TCP Congestion algorithms:
westwood - default
reno
bbr
bic
cubic
htcp
Get the latest Mint Kernel release from GitHub:
See Mint's source here.
The device must have an unlocked bootloader; as well as TWRP, SHRP, or any recovery of your choice installed.
Download latest available release from GitHub Releases.
Copy the ZIP file to your SD card if necessary.
Reboot to recovery.
Flash downloaded ZIP.
Reboot to System instead of recovery.
???
Profit
Q: What bootloader does this need?A: It is strongly advised to install the One UI 3.1 update before installing Mint, for the most stable experience. Installing on Android 10 will cause issues, and is not supported.Q: I'm locked out (bootloop) after installation. What do I do?A: If you ever experience being locked out after installing any build, with SystemUI restarting after entering your password/PIN, and Samsung Account showing a Samsung Account logged out notification, you may have been experiencing the "Pin Problem".
Several builds of TWRP and OrangeFox have a security patch level (SPL) of 2099-12 (December 2099), but Mint follows the latest SPL available to the device. This causes the device to act up once booted into the kernel.Please note that it is intended behavior by the system and is not a bug.You can flash PassReset, or wipe your device to fix it.See here for more information.Q: I'm signed out from my Samsung Account and cannot log back. What do I do?A: Clear Samsung Account data. You can do either of the following:
With a PC and ADB installed, run this command:
Code:
adb shell pm clear com.osp.app.signin
On a terminal app with root access, do:
Code:
su -c pm clear com.osp.app.signin
Q: I'm experiencing other issues.A: Please report through this feedback form, or the Fresh Community on Discord. Please include logs, screenshots, or screen recordings so I can help you better.
Mint will never be possible without the unwavering work of these awesome people. I have tried my best to keep their authorships on Mint's commit history. Thank you very much!
Cruel Kernel for the Galaxy S10/Note10 (evdenis)
ThunderStorms Kernel for the Galaxy S10/Note10 (ThunderStorms21th)
Cosmic Fresh (Dark-Matter7232) and Optimized M21 Kernel (repinger) for the Galaxy M21.
Destrictize Project (DestrictizeProject)
Motorola One Action/Vision Kernel Sources
Quantum Kernel (prashantpaddune)
Zeus Kernel for the Galaxy Note9 (THEBOSS619)
Custom Galaxy A51 Kernel (ianmacd)
StormBreaker Kernel (stormbreaker-project) and Stratosphere Kernel (Stratosphere-Kernel) for the POCO X3
Artemis Kernel for the Pixel 4 XL (celtare21)
GS101/Tensor SoC Kernel Source (Google/AndreiLux)
Reserved 2
You're great.
Is cts profile pass on this kernel ?
I'm using snake os + kakarot kernel and unable to pass cts profile, hence I'm unable to use any banking apps
aaki_rocker said:
Is cts profile pass on this kernel ?
I'm using snake os + kakarot kernel and unable to pass cts profile, hence I'm unable to use any banking apps
Click to expand...
Click to collapse
Passing SafetyNet is handled by your ROM, not the kernel. :>
Oo okay. Thanks
TenSeventy7 said:
Passing SafetyNet is handled by your ROM, not the kernel. :>
Click to expand...
Click to collapse
Is this good for gaming and is this better than prishkernel
One of the best kernel
is the selinux switchable ?
JULiO.7 said:
is the selinux switchable ?
Click to expand...
Click to collapse
Yes. :>
Hiya
I have your fresh rom installed
And I've been using it for quite a while (Amazing rom btw)
Can i flash the kernel with this rom installed?
Will this work on my A505w with stock oneui 3.1?
so im on stock with root already - when i flash this (root) will it over write my magisk and modules or when i flash nonroot will it clear all my magisk stuff? ...
Quick Update:
I'm currently pulling out the Mint 11.5 release as I have observed instabilities when using specific applications. I thought those were fixed from testing but it seems the issue stems deeper than just a single commit revert.
HUGE apologies. The performance is great if I say so myself, but there are some major issues needed to be fixed.
Thank you for your understanding.
Hello, sorry if its a stupid question, but there is something wrong with a50 ever since it was been updated to android 10/android 11, at least on my a505gt, whenever i get into a discord call, the audio starts to cut alot and it goes to mono sound, would a kernel fix it?
Currently I'm using your kernel with SnakeOS v4.0 and it running smooth like good peanut butter, good work.
@TenSeventy7
The question is, can I use it with any AOSP Android 12 ROM?
TheHEARER said:
Currently I'm using your kernel with SnakeOS v4.0 and it running smooth like good peanut butter, good work.
@TenSeventy7
The question is, can I use it with any AOSP Android 12 ROM?
Click to expand...
Click to collapse
I tested this kernel with ProjectRadiant, Corvus, and PixelPlusUI. a bit laggy but I don't think it's relevant with this kernel.
aybrk27 said:
I tested this kernel with ProjectRadiant, Corvus, and PixelPlusUI. a bit laggy but I don't think it's relevant with this kernel.
Click to expand...
Click to collapse
TheHEARER said:
Currently I'm using your kernel with SnakeOS v4.0 and it running smooth like good peanut butter, good work.
@TenSeventy7
The question is, can I use it with any AOSP Android 12 ROM?
Click to expand...
Click to collapse
There's a separate builds for android 12 ROMS
JuanTamqd21 said:
There's a separate builds for android 12 ROMS
Click to expand...
Click to collapse
I am using this with SnakeOS mainly.
I just tested it with the others.