Related
This is a kernel compiled from GT-I9505G sources and packed with MF8 initramfs.
I suggest to use it with one 4.2.2 Google Edition rom but is working good also with TW Samsung’s rom.
Is not something special, is a stock kernel i compile because i see some diffs between I9505 & I9505G sources..
Test kernel for Samsung XXUEMJ5 here.
----------------------------------------------------------------------------------------------------------------
@V1
Tested and working:
WiFi
Exfat with Samsung forced to load modules
Mtp
Insecure
Cache & dalvik cache it will auto deleted at installation of the zip.
----------------------------------------------------------------------------------------------------------------
@V2
V1+ Fixed:
Smart Screen on TW rom's.
Screen rotation on TW rom's.
Changes:
Ex-fat modules from android 4.3 leaked rom.
----------------------------------------------------------------------------------------------------------------
@V3
V1+V2+ Fixed:
Core0 MHz
Changes:
Added smart charging from Samsung source (More info)
----------------------------------------------------------------------------------------------------------------
@V4
V1+V2+V3+ Changes:
Updated Linux kernel to latest 3.4.52
Disable Gentle Fair Sleepers (Thanks @broodplank1337)
Disable rooting restrictions (Just in case. Forgot it before..)
Disable all debuggers (Seems unneeded and by disabling those gives better battery life)
----------------------------------------------------------------------------------------------------------------
@V6
V1+V2+V3+V4+V5(test)+ Changes:
Enable CPU under clock (Thanks @ktoonsez)
Removed lot of dmesg log spams (Better battery?) (Thanks @faux123)
Add voltage control (Thanks again @faux123)
GPU OC (Thanks again @faux123)
Added Convervative ConvervativeX and intellidemand governors (Thanks @broodplank)
----------------------------------------------------------------------------------------------------------------
@V7
V1+V2+V3+V4+V5+(test)+V6+ Changes:
Fixed GPU overclock and added {128-200-320-400-450-533-600} Frequencies (Thanks to Talustus) default is 450.
----------------------------------------------------------------------------------------------------------------
@V11
Changes&New thinks:
Updated Linux kernel to latest 3.4.54.
Reworked from scratch CPU OC - UC - VD. (Many thanks to @ktoonsez))
All cores runs at frequencie you set.
(That is very important and you can chek it with kernel tuner app from playstore)
All cores runs on ondemand governor.
(That is also very important and you can again check it with kernel tuner app from playstore)
Added faux sound control (Thanks to @faux123 for his work)
Added kthermal and auto_hotplug. "mpdecision is not works because auto_hotplug take his place if you whant to completly remove mpdecision you can rename /system/bin/mpdecision to mpdecision.back but if you change to other kernel do not forget to rename the file". (Thanks again to @ktoonsez))
Max CPU OC @ 2160000. (I dont need more)
GPU OC steps 128/200/320/450/600 (Disable some frequencies because of the new method ktoonsez use to OC, all apps except his app doesn't want to set anything).
Added Fading-led mod and it is working with everything, Missed call-sms user apps etc...
Disabled Gentle Fair Sleepers.
Enable Fat/MSdos/Vfat and Ntfs(as module) File systems (Thanks to @ktoonsez))
Added CIFS as module.
Ioschedulers: row-bfq-noop-deadline-fiops-sio-vr-zen-fifo-cfq.
Added fast charge.
Other mini thinks that i dont remember now...
----------------------------------------------------------------------------------------------------------------
@V13
Updated Linux kernel to latest 3.4.55.
Added an option to app to control the led (Fade - non fade - speed)
Added an app to manage some basic kernel features based on scripts thanks to HM.Carbide.
Created a new function called set_cpu_min_max which will set the cores specified using a workqueue. (Many thanks to ktoonsez)
Fixed Screen-Off Mhz function. (Now is working)
Auto-Hotplug enabled by default.
NoteThe app and his scripts is on alpha stage need to add more)
----------------------------------------------------------------------------------------------------------------
@V14
A small update..
Updated Linux kernel to latest 3.4.59.
Fixed power ON while charging.
Fixed charging led notification.
Removed force loaded exfat modules code and added exfat modules 1.2.4 compiled from source. (Thanks samsung)
Probably fixed random restarts.
Other changes for better stability and performance.
More to come....
----------------------------------------------------------------------------------------------------------------
@V15
Compiled with latest GCC 4.7 toolchain (Thanks to faux)
Added CPU governors: abyssplugv2 - adaptive - asswax - badass - dancedance - intellidemand - smartassH3 and wheatley. (Thanks to ktoonsez)
Added GPU governor: Simple (Thanks to faux)
Fixed app doesn’t load user settings after restart.
Added thermal control tweaks to app.
Added faux sound control tweaks to app. (Thanks to faux for sound control driver)
Added a function to auto backup efs to /sdcard/ausdim-kernel-data. (For safe)
Added a function to copy last_kmsg to /sdcard/ausdim-kernel-data. (For helping me)
Reworked whole app with other mini changes and now is fully working.
Other mini kernel changes for better stability and performance.
Note: Before flash the kernel please delete manually init.d scripts from /etc/init.d/ folder or by the Ausdim kernel manager app.
----------------------------------------------------------------------------------------------------------------
@V16
Fixed charging when device is off.
Fixed app re-installation after restart.
Fixed set minimum throttle mhz at app.
Removed some ondemand tweaks added at v15.
Removed wipe /cache and /dalvik-cache from the updater-script.
Thanks and sorry for that quick update.
Note1:The app is inside on ramfs at boot.img and is auto installed/update if it's needed or not allready installed when device reboot to os.
Note2: Before flash the kernel please delete manually init.d scripts from /etc/init.d/ folder or by the Ausdim kernel manager app.
----------------------------------------------------------------------------------------------------------------
@V17
Compiled with latest gcc 4.8 and -o3.
Cifs 4.2.x fix. (Now we have cifs tested and fully working. Thanks @andreasy for notice that and report it also thanks @mkasick for the actual fix)
Fixed that damn lag. (Huge thanks @nfsmw_gr for thousands tests and suggestions)
Reworked led notification driver.
Disable multicast on suspend. (Save battery if to many users is on same network. That damn wlan_rx_wake wake locks. Thanks @pi-xel to note that)
Latest linux kenrel 3.4.61.
Added zram as module.
Added dynamic sync control. (Thanks to @faux)
Added ktoonservativeq cpu governor. (Thanks @ktoonsez)
Added sysfs to make Gentle Fair Sleepers configurable via app.
Added some zram and swappines settings at my app (Thanks @nfsmw_gr) if you want more then you can use Turbo-Zram. (Thanks @rlorange)
Added Android Logger switch trough App. (Thanks @wanam)
Added a Knox security removal. (Thanks @wanam)
Kernel compression: xz (To reduce zimage size)
Some others here and there...
Note1:The app is inside on ramfs at boot.img and is auto installed/update if it's needed or not already installed when device reboot to os.
Note2: Before flash the kernel please delete manually previous init.d scripts from /etc/init.d/ folder or by the Ausdim kernel manager app.
----------------------------------------------------------------------------------------------------------------
@V18.1
This update is focusing to stability and performance.
Lot of changes time and reverts to be Completely Lag Free....
Latest Linux kernel 3.4.64.
Updated Tsp firmware (From MGG update3) You can check the current firmware by *#2663#
Updated Ssp firmware (From MGG update3) You can check the current firmware by *#2663#
Updated Wireless drivers (From MGG update3)
Zram no more loaded as module and has now 4 disks default.
Zram can now be disabled via my app.
Other thinks that i don't remember....
Again many thanks @nfsmw_gr and @pjbuser for trying many test kernel's
----------------------------------------------------------------------------------------------------------------
@V19
This update is focusing to stability and performance.
Latest Linux kernel 3.4.66.
Fix random reboots. (Need test)
Disabled ktoonsez auto_hotplug and add intelli_plug with eco mode by faux.
Many thanks @all for testing and patience.
----------------------------------------------------------------------------------------------------------------
Tip:
If for some reason after set extremely settings you cant boot then you have to run aroma file explorer from CWM recovery and delete the responsible script at /etc/init.d folder.
If for some reason you lost root after flashing my kernel then you can simply download Chainfire's UPDATE-SuperSU-v1.51.zip and install it via CWM like you did with the kernel.
You can use Trickster MOD Kernel Settings from playstore to under clock and play with voltages governors and gpu.
Millions of thanks to:
@nfsmw_gr (For helping me with the scripts/debug/tests realy great man)
@pjbuser (For many tests and suggestions)
@broodplank1337 (for his great help about git-hub really great and friendly developer) and @ktoonsez for his great work and
@faux123.
Source code:
https://github.com/ausdim/GE-Edition-I9505-jfltexx
.:.I you want to Donate me.:.
Make me a flashable ZIP
jamal2367 said:
Make me a flashable ZIP
Click to expand...
Click to collapse
Uploaded here...
Thank's
Thanks
i've flashed deodexed and not google edition's rom but i've problems with wifi... can i flash this? i come from MEA...
MTP working?
coolpix90 said:
i've flashed deodexed and not google edition's rom but i've problems with wifi... can i flash this? i come from MEA...
Click to expand...
Click to collapse
The kernel is compiled from 9505G sources.
Wifi is working.
If the wifi is not working in your device try to change the rom.
Thank's
ausdim said:
The kernel is builded from 9505G sources.
Wifi is working.
If the wifi is not working in your device try to change the rom.
Thank's
Click to expand...
Click to collapse
From which kernel did you take the ramdisk from?
I didn't find any i9505G Stock Kernel
nolinuxnoparty said:
From which kernel did you take the ramdisk from?
I didn't find any i9505G Stock Kernel
Click to expand...
Click to collapse
As i said to the first post the kernel is builded from I9505G sources released by Samsung and is packed with MF8 ramdisk.
Thank's
ausdim said:
As i said to the first post the kernel is builded from I9505G sources released by Samsung and is packed with MF8 ramdisk.
Thank's
Click to expand...
Click to collapse
therefore i need to go to MF8 then install GE rom and then your kernel right?
Flashed it but system wouldn't boot. Cleaned cache and dalvik and reflashed and now it boots.
You have to wipe cache and dalvik before or after flashing this.
---------- Post added at 12:28 PM ---------- Previous post was at 12:19 PM ----------
Oh... my....god! This kernel is magical! With ktoonsez kernel, I had roughly 15k i Antutu, but now I have 24k! Not that it means a whole lot but still. I'm stumped.
Theshawty said:
Flashed it but system wouldn't boot. Cleaned cache and dalvik and reflashed and now it boots.
You have to wipe cache and dalvik before or after flashing this.
---------- Post added at 12:28 PM ---------- Previous post was at 12:19 PM ----------
Oh... my....god! This kernel is magical! With ktoonsez kernel, I had roughly 15k i Antutu, but now I have 24k! Not that it means a whole lot but still. I'm stumped.
Click to expand...
Click to collapse
Thank's for that note..
ZIp reuploaded at first post and it will clear cache and dalvik.
Thank's
ausdim said:
Thank's for that note..
ZIp reuploaded at first post and it will clear cache and dalvik.
Thank's
Click to expand...
Click to collapse
This kernel's pure magic, mate! :good:
Not just the Antutu score is higher, things generally feel a lot more snappier now!
My S4 Google Edition is much better now, better temperature, is fresher now.
Thanks
I have also installed and working good and mtp working.
The camera with this kernel works fine?
felipepx said:
The camera with this kernel works fine?
Click to expand...
Click to collapse
Dude, really sorry but are you some kind of bot / complete moron? You've asked that exact question in basically every thread I've come across since yesterday. They all work, besides some auto-focus issues with night scene mode, which is rom-related I suppose.
slind said:
Dude, really sorry but are you some kind of bot / complete moron? You've asked that exact question in basically every thread I've come across since yesterday. They all work, besides some auto-focus issues with night scene mode, which is rom-related I suppose.
Click to expand...
Click to collapse
I'm just asking myself referring to these problems that were appearing since yesterday, I asked wondering if with this kernel everything is ok or if the problems continue ...
ausdim said:
This is a kernel compiled from GT-I9505G sources and packed with MF8 initramfs.
I suggest to use it with one Google Edition rom.
Is not something special, is a stock kernel i compile because i see some diff's between I9505 & I9505G sources..
Tested and working:
WiFi
Exfat with samsung forced to load modules
Cache & dalvik cache it will auto deleted at installation of the zip.
Thank's
Click to expand...
Click to collapse
Thanks.
Camera working fine here.
In this post, I would like to explain what kexec-hardboot patch is.
@kernel developers: I would like to ask you to merge this patch to your kernels, because it is essential part of MultiROM - it allows me to boot any kernel without changing the boot partition. I realize that it is no small request, but the patch is not big, touches relatively stable parts of kernel and should not cause any problems. Thank you.
What is kexec?
It is syscall of Linux kernel, which allows you to boot another Linux kernel without restarting the device - "Linux boots itself". The functionality is equivalent to fastboot -c *cmdline* boot zImage initrd.img, but without PC and fastboot. It is fairly known thing, so more info at wikipedia and man kexec.
Standard kexec call unfortunatelly does not work on Nexus 4. It freezes somewhere, and it is very difficult to find out where - probably some of the drivers are not shut down/re-initialized properly, it is a commong thing among Android devices, which is why kexec-hardboot was made.
What is the difference between normal and hardboot exec?
Kexec-hardboot patch adds a real device restart to that process, so that all the drivers can be properly reinitialized. It stores new kernel to RAM, reboots the device as usual, and kernel from boot partition immediately jumps to the one which was stored to RAM before reboot.
Unlike grouper's kexec-hardboot patch, this one only requires the host kernel to be patched. This is one of the improvements I made, and I think it is pretty significant.
To sumarize the process:
kexec --load-hardboot.... is called and kernel it loaded into RAM.
kexec -e is called. Special info is written to memory (to area which is not overwritten on reboot) and the device is rebooted.
After reboot, very early in the boot process, kernel checks if that special info is present in RAM and if so, it loads new kernel from RAM and jumps to it.
Kexecd' kernel starts and boots.
For more info, read the original thread.
Patches:
Kernel patch: https://gist.github.com/Tasssadar/7833796, 4.4 AOSP kernel repo
This is the kernel patch. Only the host kernel needs to be patched.
Related CONFIG options:
CONFIG_KEXEC=y
CONFIG_KEXEC_HARDBOOT=y
CONFIG_PROC_DEVICETREE=y
CONFIG_ATAGS_PROC=n # This one is turned on automatically, but it is not needed, so you can disable it.
All these options must be enabled.
Userspace kexec binary: https://github.com/Tasssadar/kexec-tools
I had to change some things in kexec userspace binary because of some kernel bugs, complete description is in that repository. You can get statically built binary at https://github.com/Tasssadar/multirom/blob/master/install_zip/prebuilt-installer/multirom/kexec
Usage:
Once you have the kernel patches and kexec userspace binary in place, just run following command to boot into new kernel:
Code:
kexec --load-hardboot zImage --initrd=initrd.img --mem-min=0x20000000 --command-line="$(cat /proc/cmdline)" --dtb
kexec -e
Note the command line parameter - cmdline from bootloader is not added automatically, you have to put it there by yourself.
Authors:
This patch was made by Mike Kasick for Samsung Epic 4G. Since that, it was ported to several devices, one of them is Asus Transformer TF201 - I used patch from TF201 and modified it a bit (basically just changed few SoC specific constants). People at #ubuntu-arm helped me out with that, thanks.
For hammerhead, I've improved the patch a bit - only the host needs to be patched now and I've added support for DTB.
Merged, thanks again for the awesome work @Tasssadar!
Good deal.My day is getting better.
@show-p1984 would love to see this in bricked kernel too! ?
@neobuddy89 did you see this?
Sent from Nexus 5 on Slimkat
thanks for the hard work.. thats awesome.
AndroidSlave said:
@neobuddy89 did you see this?
Sent from Nexus 5 on Slimkat
Click to expand...
Click to collapse
Yeah, I saw this.
neobuddy89 said:
Yeah, I saw this.
Click to expand...
Click to collapse
I asked that 6 months ago
Sent from my Nexus 5 using Tapatalk
awesome work bro...
much needed..
AndroidSlave said:
I asked that 6 months ago
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, I know and I saw that days back..
Enough of OT. :fingers-crossed:
Help with applying the patch
Okay so I have my aosp kernel made. I have my working directory too. Can you just guide me on how do I apply this partch to it?
Is it possible to add that patch from a on the fly flashable zip ?
@Anoopnk since the patch is for the kernel(zImage) its not possible to patch it like that. Or you have to compile the kernel or you need to ask your kernel dev friendly or he can include it in his kernel.
Hello, first I'd like to apologize for dredging up an old thread. Second, I am attempting to build a CM13+kali+kexec compatible kernel, with extra wifi drivers as the base kernel doesnt support my wifi card. Based on that goal, I have a multi-part question for the OP, or anyone else with the know-how to assist me in my quest.
1)Is there a source available for your kernel_kexec_hammerhead_cm13-01-2c39db662.zip listed on the multirom page for nexus 5? I'm attempting to build a new kernel, for kali+CM13+multirom, and your android_kernel_google_msm git only has branches going up to CM12. It would be far easier for me to start with a 'clean' CM13+kexec source then trying to patch myself as per question #2
2) I've attempted to patch a plain old hammerhead_defconfig from CM13 git, however I believe I am doing so wrong. I have managed to compile kexec-tools and aquired the hammerhead 3.4.x patch. Now am I supposed to patch my produced zImage-dtb AFTER build, running the patch from the kexec-tools folder and against the zImage-dtb? Is it something like 'KEXEC.patch -p1 < zimage-dtb'
Any clarification on the use of the kexec-tools patch, or simply a link to github source of a 'clean' CM13 kernel with the kexec patch already applied, would be incredibly helpfull on my journey down the rabbit hole
~EDIT~
Ok so I've managed to figure out the patch and feel like a dumbass. For anyone else looking to get into kernel dev, and wanting to use the kexec patch, heres the basics:
1- run patch within your kernel source directory
2-ensure that the config settings in OP are set (I had to add them to my source by hand as they werent there)
3-when zipping up your kernel, add the sbin and lib/kexec-tools folders from the kexec-tools source build, and be sure your updater-script / updater-binary is set to move these folders into /sbin and /lib respectively.
4-Flash and enjoy Kexec! (check with multirom manager)
This is a kernel you can flash on any rom for amami, which uses the caf-based libraries and stock rom.
The most work on this was not done by me, this is more a package of work done by other people.
See the next post for installation instructions.
Features
- f2fs support
- cpuquiet cpu hotplug driver(disabled mpdecision automatically)
- lz4 support and lz4 kernel compression
- optional underclocking to 268 Mhz
- fiops i/o scheduler
- lcd color calibration support
- cpu undervolting support
- enabled zram
- faux123's sound control
- fastcharge support
- dynamic sync control by faux123
- '-Ofast'-optimizations
- 'proc/last-kmsg'
- vibration density sysfs interface
- TWRP recovery with f2fs support(stock-based only)
- [WIP] f2fs-compatible ramdisk(stock-rom only, for aosp-based check this
- init.d support(stock romonly, but already included in the most aosp-based roms)
- disabled ric service(stock only, not needed with aosp-based roms)
- prima wifi module
Issues
- exfat sdcards and usb storage can't get mounted
XDA:DevDB Information
MoshKernel-amami[aosp-based + stock], Kernel for the Sony Xperia Z1 Compact
Contributors
CoolDevelopment, faux123, DooMLoRD, FreeXperia, every android kernel developer
Kernel Special Features:
Version Information
Status: Testing
Current Beta Version: 0.3
Beta Release Date: 2014-09-08
Created 2014-07-16
Last Updated 2014-09-08
Reserved
How to configure cpuquiet
You can configure cpuquiet to the pefect use with your phone. You need root permissions and any shell, i. e. Terminal Emulator.
First run 'su' to get root permissions.
Change the minimum and maximum amount of online cpu cores:
Code:
file for max. amount of online cpus: /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/max_cpus
file for min. amount of online cpus: /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/min_cpus
Example:
echo 3 > /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/max_cpus
echo 2 > /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/min_cpus
The cpuquiet driver supports different governors, a bit like cpufreq governors. The governors which are currently present are: "runnable", "rq_stats", "load_stats", "balanced"
Find the best one for you by yourself
Code:
sysfs file: /sys/devices/system/cpu/cpuquiet/current_governor
Example: echo balanced > /sys/devices/system/cpu/cpuquiet/current_governor
Change the max screen-off cpu frequency and online cpus:
Code:
sysfs file for max. screen-off-freq: /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/screen_off_cap
syfs file for max. screen-off online cpus: /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/screen_off_max_cpus
Example:
echo 960000 > /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/screen_off_cap
echo 1 > /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/screen_off_max_cpus
Disable cpuquiet(and enable mpdecision):
Code:
sysfs file: /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/enabled
Example:
echo 0 > /sys/devices/system/cpu/cpuquiet/cpuquiet_driver/enabled
start mpdecision #enable mpdecision
These settings only stick until you reboot. So better setup an init.d script, which applies your settings every boot.
If you aren't sure, what init.d scripts are, ask google.
Reserved
AOSP-based roms
The kernel for asop-based roms gets flashed using a special .zip, which only flashes zImage and dt. That means, there are no ramdisk-problems, which you didn't got before. The scripts inside the script are also modifying the ramdisk to don't have mpdecision enabled by default.
Installation
1. Flash the zip file through a recovery
Download
https://s.basketbuild.com/devs/CoolDevelopment/MoshKernel-amami/aosp-based/
Source: https://github.com/CoolDevelopment/MoshKernel-amami/tree/caf
Stock rom/Stock-based roms
Installation
1. Be sure you have an unlocked bootloader
2. Be sure you have installed busybox
3. Flash the zip file through a recovery
Download
https://s.basketbuild.com/devs/CoolDevelopment/MoshKernel-amami/stock-based/
Source: https://github.com/CoolDevelopment/MoshKernel-amami/tree/14.4.A.0.xxx
https://github.com/CoolDevelopment/MoshKernel-amami-stock-based-initramfs
Changelog
0.1
- initial commit
0.1.1
- revert back to row as default i/o scheduler
0.1.2
- update f2fs to current upstream
- replace Cyanogenmod branding with mine
- strip kernel modules, you don't need to download 30mb+ anymore
0.2
- removed intelliplug
- added cpuquiet cpu hotplug driver
- automatically disabled mpdecision(the scripts are modifying the ramdisk)
- fastcharge support
- '-O3'-optimizations
- lz4 support and kernel compression
- remove overclocking
0.3
- stock-rom support
. dynamic fsync control by faux123
- changed default configuration for cpuquiet
- prima wifi module for stock rom
- upstreamed f2fs commits from linux 3.17rc4
Any roms, Also cm11?
Inviato dal mio Xperia Z1 Compact
cicci0 said:
Any roms, Also cm11?
Inviato dal mio Xperia Z1 Compact
Click to expand...
Click to collapse
Yes
Whaa!! for CM based ROMs and Sony based ROMs!! that would be interesting,
also I like the idea of not having a ramdisk inside the zip, I'll probably use it for next releases of Pimped kernel,
And did you strip the kernel modules before putting them inside the zip??
the wlan.ko module is 43.5MB!! the kernel's zip is around 35MB!!!! that is alot.
BTW, great work, thanks for contributing again and again for our beloved device,
hope you the best:angel:
OmarEinea said:
Whaa!! for CM based ROMs and Sony based ROMs!! that would be interesting,
also I like the idea of not having a ramdisk inside the zip, I'll probably use it for next releases of Pimped kernel,
And did you strip the kernel modules before putting them inside the zip??
the wlan.ko module is 43.5MB!! the kernel's zip is around 35MB!!!! that is alot.
BTW, great work, thanks for contributing again and again for our beloved device,
hope you the best:angel:
Click to expand...
Click to collapse
I am sorry but it may not work on sony roms, you can try if you want. I didn't test it.
I did not even know that kernel modules can be stripped
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
CoolDevelopment said:
I am sorry but it may not work on sony roms, you can try if you want. I didn't test it.
I did not even know that kernel modules can be stripped
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well yeah that is the problem, I'm kinda sure that you can't use the same kernel for Sony and AOSP based ROMs in the same time!!
so you should mention in OP or in title that this kernel is for AOSP based ROMs so that users don't get confused...
Also if you haven't searched and found out about the stripping, you can do it by executing this:
<dir-to-toolchain>/bin/arm-eabi-strip --strip-unneeded <dir-to-modules-folder>/*
of course the arm-eabi-strip part depends on what toolchain you're using.
Hopefully that would help.
Works on unofficial slimkat
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
It also works great with this : http://download.mokeedev.com/?device=amami
ps: Always love to use the FauxSound Audio/Sound Control and FauxClock apps
Thank You !!!!
:good:
Version 0.1.2:
- update f2fs to current upstream
- replace Cyanogenmod branding with mine
- strip kernel modules, you don't need to download 30mb+ anymore
If you want to use f2fs, I really suggest you to install this, the fixed bugs are really important. Else it is almost unneccessary
@CoolDevelopment
Very nice job! Finally we get a dedicated custom kernel for Amami
Oh and I saw the commits on CM gerrit. Nice job man :good:
I'll try flashing this on PAC. If what you say is true, that it doesn't modify the ramdisk, then it should boot. Otherwise I'll get stuck in a bootloop because PAC has custom jar files.
Finally some exciting development on Amami, testing now
EDIT: just a tip, you should ask a mod to move this thread to original development, because it really belongs there
EDIT2: it works perfectly
Yes it doesnt work on pa aslo :/
ygecesefa said:
Yes it doesnt work on pa aslo :/
Click to expand...
Click to collapse
Please give me details else i can't help
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
it work on candykat rom
@cooldevekopment Is it possible to include TWRP instead of CWM in your kernel. I know there is a patch for f2fs that has TWRP buid-in, but anyway.
da900 said:
@cooldevekopment Is it possible to include TWRP instead of CWM in your kernel. I know there is a patch for f2fs that has TWRP buid-in, but anyway.
Click to expand...
Click to collapse
this kernel has no ramdisk, meaning it doesn't contain nether CWM nor TWRP,
whatever recovery you'll flash the kernel through, it won't be replaced with any other recovery
OmarEinea said:
this kernel has no ramdisk, meaning it doesn't contain nether CWM nor TWRP,
whatever recovery you'll flash the kernel through, it won't be replaced with any other recovery
Click to expand...
Click to collapse
Does this mean I can flash it even on a rooted stockrom?? 4.4.4 108 for example
djdana said:
Does this mean I can flash it even on a rooted stockrom?? 4.4.4 108 for example
Click to expand...
Click to collapse
Nope, because it is based on AOSP kernel source, which won't work on Sony based ROMs,
this kernel will only work on AOSP-based (CM-based) ROM..
To bad haha thanks for the quick reply
Overview:
This is a custom kernel based on Omni sources for our legendary i9000. This is only for 5.1.1/6.0.1 roms and no other version of android will be suppported
It works on any Omni based 5.1.1/6.0.1 rom.
>The zip you will download is flashable via recovery.
>> Use devil kernel manager or NStools to edit the kernel settings.
Features : - Multiple CPU governors (lulzactive, smartassV2, wheatley, lagfree, ondemandX)
- Tweaked smartassV2
- BFQ, Zen, VR & SIOPLUS I/O schedulers added
- Tweaked VR
- New TCP algorithms (westwood is default)
- Bigmem, up to 430mb
- CMA (MM only for now)
- Kernel compressed with XZ
- Compressed initramfs
- Dynamic page writeback
- Dynamic Fsync
- Custom ARM & INT voltages
- Voltages fixed for more stable OC
- Selectable GPU OC (not working properly for now)
- Fast charge
- BLX
- Live OC
- FULL O3 optimisations
- Call volume hack
- Touchwake
- BLN
- Zram
- Swap / Zram optimisations
- LMK tweaks
- SLQB memory allocator
- NEON optimized crypto routines
- Voodoo color
- SquashFS support (module)
- EXfat support (module)
- 720p patched bigmem libs
- Built from the latest Omni source
- Built using custom Cortex-A8 optimized UBERTC 5.3 toolchain of @Cl3Kener
Todo:- Backport more things from higher linux versions and fix remaining conflicts ...
- Fix GPU OC ... Well we have live OC, not worth the time i guess.
- Make CGROUP_TIMER_SLACK work
- GPU driver to DDK [email protected]
- Make a better (and more fancy) updater script
- Fixing the remaining issues [...]
What I wont do : - Enable TV out
- Upgrade linux version
- Add useless CPU governors or I/O schedulers
- make your phone as fast as a i9500
Please use it at your own risk! I am not responsible for any damage that may occur to your device.
Download :
Latest android 5.1.1 kernel :
Kernel_ION.zip MD5 : 2060f96fbffc98a1f2fae9108066b69a
http://www50.zippyshare.com/v/zVr8YvZ4/file.html
Latest android 6.0.1 kernel :
Kernel_CMAEXP.zip MD5 : 236f89a961b559c666a1c064aaccd728
http://www43.zippyshare.com/v/Yxm6WDuA/file.html
Old versions :
https://mega.nz/#F!3x5VTbiQ!87aMOGoDBuQZmiELhKlUkQ
Thanks:
@humberos
@DerTeufel1980
@kasper_h
@Alberto96
@Ezekeel
@xc-racer99, for his help on setting up my Github
@(°_o)
Anyone else who helped me
Source Code:
https://github.com/Coldwindofnowhere/android_kernel_samsung_aries
Custom built UBERTC with A8 optimisations : https://bitbucket.org/Coldwindofnowhere/
XDA:DevDB Information
Omni kernel, Kernel for the Samsung Galaxy S I9000
Contributors
Coldwindofnowhere, xc-racer99
Version Information
Status: Beta
Created 2015-10-02
Last Updated 2016-03-06
>If you like my work, hitting the thanks button won't hurt you<
good luck
Thanks for sharing ! I really want to check this kernel out, can someone tell me what is the recommended Omni LP release to be used with this kernel? A link in PM or a reply would be great.
Sent from my Nexus 7 using Tapatalk
idCyber said:
Thanks for sharing ! I really want to check this kernel out, can someone tell me what is the recommended Omni LP release to be used with this kernel? A link in PM or a reply would be great.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=61937705
Gesendet von meinem SM-G900F mit Tapatalk
idCyber said:
Thanks for sharing ! I really want to check this kernel out, can someone tell me what is the recommended Omni LP release to be used with this kernel? A link in PM or a reply would be great.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
If you can , that would be great if you test if on different 5.1.1 roms and tell me if it works or not
Coldwindofnowhere said:
If you can , that would be great if you test if on different 5.1.1 roms and tell me if it works or not
Click to expand...
Click to collapse
This kernel works with Code rom 5.1.1 the latest build and mostly everything work perfectly. However, to test this i ported it to my good old vibrant. The only issue is since Im guessing devil kernel manager doesnt support vibrant cant seem to change any values in devil. Thanks for building this kernel
falconscrest123 said:
This kernel works with Code rom 5.1.1 the latest build and mostly everything work perfectly. However, to test this i ported it to my good old vibrant. The only issue is since Im guessing devil kernel manager doesnt support vibrant cant seem to change any values in devil. Thanks for building this kernel
Click to expand...
Click to collapse
Assuming you used the kernel source (github.com/omni) to port to the vibrant, you won't have any options other than bigmem. The source code linked there doesn't have things such as Fast Charge, etc.
However, you can see if support for them is there by manually putting a "1" in the file /sys/kernel/fast_charge/force_fast_charge
(ie echo 1 > /sys/kernel/fast_charge/force_fast_charge from a terminal/adb shell).
Also, look out for selinux issues. If selinux is in enforcing mode, the Devil Manager may or may not be able to access the sysfs paths. Run "setenforce 0" to put it to permissive mode.
Speaking of source code, @Coldwindofnowhere have you uploaded the complete kernel source you used somewhere? I'd be curious to see it. Thanks for taking this project on!
xc-racer99 said:
Assuming you used the kernel source (github.com/omni) to port to the vibrant, you won't have any options other than bigmem. The source code linked there doesn't have things such as Fast Charge, etc.
However, you can see if support for them is there by manually putting a "1" in the file /sys/kernel/fast_charge/force_fast_charge
(ie echo 1 > /sys/kernel/fast_charge/force_fast_charge from a terminal/adb shell).
Also, look out for selinux issues. If selinux is in enforcing mode, the Devil Manager may or may not be able to access the sysfs paths. Run "setenforce 0" to put it to permissive mode.
Speaking of source code, @Coldwindofnowhere have you uploaded the complete kernel source you used somewhere? I'd be curious to see it. Thanks for taking this project on!
Click to expand...
Click to collapse
I didnt use the source code to do anything just replaced the boot image with that of vibrant and it seemed to boot up just fine and i could switch between smartass v2, and other addition. the only thing cant change the bigmem option over xl. It was just random since i have no clue how to build stuff.
falconscrest123 said:
I didnt use the source code to do anything just replaced the boot image with that of vibrant and it seemed to boot up just fine and i could switch between smartass v2, and other addition. the only thing cant change the bigmem option over xl. It was just random since i have no clue how to build stuff.
Click to expand...
Click to collapse
Ah, ok. I could be wrong, but I think if you replaced the boot.img with one from the Vibrant, then you're not even using the kernel from here. Weird that you still had the smartassv2 option...
If I'm wrong, someone please correct me
431mb ram possible??
xc-racer99 said:
Ah, ok. I could be wrong, but I think if you replaced the boot.img with one from the Vibrant, then you're not even using the kernel from here. Weird that you still had the smartassv2 option...
If I'm wrong, someone please correct me
Click to expand...
Click to collapse
Im not sure either because i have all govenors mentioned above while i can tweak everyone of them using kernel aditor apk and plus i can also toggle fast charge which wasnt present in omni rom for the vibrant. I have uploaded some screenshots and it is from code rom.
xc-racer99 said:
Assuming you used the kernel source (github.com/omni) to port to the vibrant, you won't have any options other than bigmem. The source code linked there doesn't have things such as Fast Charge, etc.
However, you can see if support for them is there by manually putting a "1" in the file /sys/kernel/fast_charge/force_fast_charge
(ie echo 1 > /sys/kernel/fast_charge/force_fast_charge from a terminal/adb shell).
Also, look out for selinux issues. If selinux is in enforcing mode, the Devil Manager may or may not be able to access the sysfs paths. Run "setenforce 0" to put it to permissive mode.
Speaking of source code, @Coldwindofnowhere have you uploaded the complete kernel source you used somewhere? I'd be curious to see it. Thanks for taking this project on!
Click to expand...
Click to collapse
Sure, i'll set a github soon, but trust me there are only minimal changes to the origianl code (even if adding liveOC seems harder since i only got build errors xD).
Btw i won't build anything this week, i'm busy with exams.
Github is up !
Coldwindofnowhere said:
Could someone help me to setup my github please ? (PM me)
Click to expand...
Click to collapse
Check your PM, let me know if you need more help.
Hey.
I tested it on 5.0.2 . stuck on bootanimation. Better mention that its for 5.1.1 .
Can you add support or please tweak it for 5.0.2
Now iam using RR lp 5.0.2
I removed some apps. And it have the same apps like omni. Its works faster than ever. Working theme engine. Only removed music and added apollo.
Has anyone have a bug where when you call someone the speaker mode work fine but the audio stops working when you turn off speaker mode
I had no problem with original omni kernel any fix because this is an awesome kernel
falconscrest123 said:
Has anyone have a bug where when you call someone the speaker mode work fine but the audio stops working when you turn off speaker mode
I had no problem with original omni kernel any fix because this is an awesome kernel
Click to expand...
Click to collapse
That's weird, i haven't changed anything concerning the audio in the kernel. You're using it on a vibrant right ? This might be the problem. I'm gonna try to reproduce this bug on my i9000 and see ....
Edit: try this http://www42.zippyshare.com/v/aZ6XgBlE/file.html
DO NOT FLASH, IT DOESN'T WORK (except if you want to give me a log or if you're really curious)
Any feedback on the vibrant version ?
Coldwindofnowhere said:
Any feedback on the vibrant version ?
Click to expand...
Click to collapse
The kernel didnt even flash no errors nothing whenever i flashed via twrp it would instantaneously reboot to recovery. Thanks again for atleast trying to fix the issue.
Coldwindofnowhere said:
Any feedback on the vibrant version ?
Click to expand...
Click to collapse
Bro. Can you add fast charge and the governers in omni kernal 5.0.2. Please
Thanks
Kirisakura-Kernel for the Asus Rog Phone 2
Hello everyone,
I proudly present Kirisakura-Kernel made for the Asus Rog Phone 2 aka Yoda!
Kirisakura - Kernel is designed to bring a handful of beneficial features to the device, while ensuring excellent performance and smoothness to get you safely through the day!
This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security and performance, while keeping stability as the foucs during testing! This includes Linux-Stable, CAF-Upstream and kernel/common.
Kernel Control Flow Integrity (Kernel-CFI), which is achieved by linking the kernel with LLD and Link Time Optimization (LTO), more precisely ThinLTO, are quite unique security features. In fact this may be one of the only 4.14 msm kernels with a fully working Kernel-CFI implementation and CFI-Violations fixed on a smartphone.
The only kernels made by OEMs offering this security feature are the ones for the Pixel 3 and Pixel 4 devices.
If that got you curious,have a read about Linux-Stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
Quick explanation of CAF-Upstream. CAF is short for Codeaurora-Forums. This is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 855+ that´s built into the Asus Rog Phone 2.
The kernel-bases available on the Codeaurora-Forums, are basically the foundations OEMs use to build their own kernel additions on top, for devices featuring Qualcomm SoCs.
The Qualcomm developers push regular updates to the bases of the different SoCs, a bit similar to how Linux-Upstream works. OEMs usually stop updating the initial base after the phone is released.
This kernel focuses amongst others to provide the latest CAF-Updates merged in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.
The kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
Many others contributed in some way or another to this kernel.
A big thanks to all of them at this place!
Now lets continue with a list of features in the next paragraph!
Main Features:
- Based on latest kernel sources from Asus for Android 11 and intended for use on Asus Stock Rom
- compiled with Clang 13.0.1 and built with -O3 speed optimizations
- Linux-Stable-Upstream included to 4.14.243
- CAF-Upstream merged
- Link the kernel with LLD and use KASLR
- include all important fixes/improvements from kernel/common
- F2FS implementation updated to latest state of kernel/common and kernel.org maintained by Jaegeuk Kim.
- Safety Net patches are included -> Kernel passes Safety Net
- Flashing the kernel will keep root!
- Sweep to sleep functionality
- Flashable via EXKM and FKM on a rooted system!
- specifically tuned EAS for the Asus Rog Phone 2
- removed nolog usage, remove rtb logging from the kernel
- remove selinux auditing from kernel for lower overhead
- remove IPC logging from the kernel
- Anykernel zip is based on the all new Anykernel3 release from @osm0sis
- option for 144hz refresh rate (Android 10 only)
- option to improve visibility in dark scenes
EAS related features:
- EAS implementation patched up to latest CAF state
- disable autogroups and use cgroups for more efficient task placement!
- Dynamic Stune Boost to inflate task utilization and not overload cores on interaction (thanks to @RenderBroken and @joshuous )
- improved schedutil governor
- updates from kernel/common
CPU related features:
- Power saving workingqueues enabled by default
have a read here: https://lwn.net/Articles/731052/
this complements EAS in general
- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to user power efficient workingqueues. This should work well in conjunction with EAS
- include cpuidle patches from CAF
- improvements to cpufreq/times/stats
- vDSO 32 patches to improve 32-bit performance
- arm64: lse: Prefetch operands to speed up atomic operations (thanks to @kdrag0n )
File System related features:
- F2FS implementation updated to latest state of kernel/common and F2FS-Mainline on kernel.org maintained by Jaegeuk Kim.
- Include rapid GC by @arter97 ( best thing is to read the commit description linked here. I compared GC on stock google f2fs, upstreamed f2fs and f2fs with rapid GC. Rapid GC is the most effective, followed by upstreamed f2fs.)
- adapt F2FS to be inline with Pixel 4s code from Google, which is also directly maintained by Jaegeuk Kim
- include a few F2FS fixes from the Pixel 4 kernel
- include optimizations to UFS-Driver from Pixel 4
- various improvements to FS-Performance from the Pixel 4
- f2fs fix to prevent data loss in case of sudden power failure
GPU related features:
- Update GPU driver to latest CAF state
- remove debugging and non-sd855+ specific code from the GPU driver
- introduce low priority worker thread to improve performance in UI-critical situations
Network related features:
- Wireguard Support (Details)
- advanced TCP algorithms enabled
- includes new bbr and bbr2
Memory related features:
- Speculative Page Faults (1. 2) (CAF default)
- enabled per process reclaim (CAF default)
- Fix various memory leaks in different subsystems
- improved mm with patches from latest mainline
- various other changes from mainline
- included zstd and lz0-rle as options for ZRAM-algorithm (lz4 is probably the best all around, so only change it if you know why and what you are doing)
- allow swappiness up to a value of 200
- remove unused mem regions to free more RAM (thanks to @kdrag0n )
Security related features:
- Control-Flow-Integration (CFI) andLink-Time-Optimization (LTO) ported from 4.14 kernel/common and Pixel 4 Kernel
- Shadow Call Stack ported from 4.14 kernel/common and Pixel 4 Kernel
- enable init_on_alloc for even more security, more information can be found in the commit message
Misc Features:
TCP Congestion Algorithms:
- advanced algorithms enabled
- includes new bbr2
Wakelock Blocker:
- advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
- please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info
Other features:
- disable logging and debugging to make the kernel more lightweight in various places (includes binder, mm, vma, gpu, ipa etc)
- remove VLAs from the kernel (more info)
- add support for steam controller
- add support for nintendo switch controller
Feature section for the "non visible" but perceptible improvements:
- updated binder section (responsible for interprocess communication)
- updated sdcardfs ; have a read about it here:
- fix CFI violations
- add ramoops/pstore support (thanks @luca020400)
Requirements
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root
- a backup of boot.img and dtbo.img to be able to restore to stock. you should be able to do this easily via TWRP.
How to flash the Kernel:
1. Download the latest kernel.zip and make sure you have properly updated to the latest Asus Firmware
1a. Optional: While it may not be necessary all times, you may want to restore stock boot.img and dtbo.img, re-root with magisk and optionally install twrp.zip if coming from another kernel. Before reporting issues make sure you do that! Thank you!
2. Make sure to use latest Magisk stable. (not the latest canary!)
3. Flash the kernel.zip via latest EXKM or FKM app, or TWRP (haven´t tested TWRP myself as I don´t need it) and do a full reboot.
4. Flash the kernel again. This step is needed because flashing the kernel disables verity on vendor in order to modify two files. Disabling verity takes a reboot. Flashing the second time allows the two files to be changed correctly. This step is necessary if you flashed a firmware update. (This step should not be necessary when updating my kernel, if you are already running it, but if you want to be on the safe side just flash it twice)
5. Reboot and profit. It will take around 15 seconds for the kernel and the system to execute all changes done by flashing the kernel.zip. After 15 seconds 120fps will kick in, if you use 120fps setting!
DOWNLOAD:
Download is located always in this folder:
https://www.androidfilehost.com/?w=files&flid=303784
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 9
1.0.0 Initial Release
1.0.2 https://forum.xda-developers.com/showpost.php?p=81389411&postcount=33
Android 10
2.0.0 https://forum.xda-developers.com/showpost.php?p=82238713&postcount=141
2.1.0 https://forum.xda-developers.com/showpost.php?p=82317211&postcount=191
2.6.0 https://forum.xda-developers.com/showpost.php?p=82495531&postcount=252
2.6.2 https://forum.xda-developers.com/showpost.php?p=82560081&postcount=261
2.6.4 https://forum.xda-developers.com/showpost.php?p=82602927&postcount=267
2.7.2 https://forum.xda-developers.com/showpost.php?p=82834055&postcount=281
2.7.5 https://forum.xda-developers.com/showpost.php?p=82837791&postcount=285
2.9.0 https://forum.xda-developers.com/showpost.php?p=83100663&postcount=306
3.0.6 https://forum.xda-developers.com/showpost.php?p=83526987&postcount=391
3.1.0 https://forum.xda-developers.com/showpost.php?p=83606511&postcount=406
3.1.3 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-84124933
3.1.5 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-84617449
3.2.0 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-84717691
3.2.1 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-84799241
3.2.2 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-85145887
3.2.3 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-85431627
Android 11
1.0.0_R https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-86201183
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee
If you like my work: http://paypal.me/freak07
Credits:
Asus for the Rog Phone 2
@osm0sis for all his work, including the ak3 installer!
@tbalden for being the best HTC wingman!
@LeeDroid for his awesome roms!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for his help too
@topjohnwu for magisk!
@osm0sis for anykernel!
XDA:DevDB Information
Kirisakura Kernel, Kernel for the ASUS ROG Phone II
Contributors
Freak07
Source Code: https://github.com/freak07/Kirisakura_Yoda
F.A.Q:
Question: Why does the kernel version show as "unavailable" in settings after flashing it.
Answer: Asus does not allow for custom kernel names in their settings. Use a kernel manager to check the kernel version.
Question: Is root preserved when flashing this kernel?
Answer: Yes the Anykernel Zip will detect root and keep it.
Question: How do I return back to stock or another kernel.
Answer: Extract boot.img as well as dtbo.img from matching firmware you are on and flash the extracted boot.img via fastboot.
Question: How to report bugs properly?
Answer: Have a look at post #3 in this thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re not using any mods, magisk modules, scripts or other modifications that alter various functions like sound mods, data traffic etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Provide logs, otherwise debugging is a lot harder. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
If the device force reboots/randomly reboots (that means you see the bootloader unlocked screen!) provide a ramoops file.
Easiest way is immediately after booting up, with a root explorer navigate to sys/fs/pstore. Copy the contents to your internal storage, zip it up and send it to me.
If the issue happens while the device is running provide a dmesg plus a logcat that you take while/shortly after the issue happens. This will log what´s running in the current session. Try to be as detailed as possible what´s happening when the issue appears. It will also help me in reading the log!
Useful Resources
How to report bugs:
It is incredibly useful if bug reports are done in a proper way. That saves everyones time and will ultimately lead to a faster bugfix (hopefully).
The following guide from @nathanchance is a very good guideline on how to properly report a bug!
android-tools/guides/proper_bug_reporting.txt at main · nathanchance/android-tools
Publicly available Android stuff. Contribute to nathanchance/android-tools development by creating an account on GitHub.
github.com
and one more for me
Wow!!! Awesome! Plans for kcal in the future?
Thank you so much for giving me a reason to unlock the bootloader. Finally am happy to see development for the device and that too from a well known developer ???? cheers mate and a very happy new year.
Can I flash Android 10 beta fota file to my cn version phone using this recovery?
I love your work bro keep this devlopment continue
All rog2 user support your hardwork ,
And more developer will come after seeing your hardwork
a5he said:
Can I flash Android 10 beta fota file to my cn version phone using this recovery?
Click to expand...
Click to collapse
please help..now my device stuck and keep looping in bootloader mode after trying to flash this kernel on Android 10 beta fota..and i cant reboot into twrp recovery and system..
sakamaki izayoi said:
please help..now my device stuck and keep looping in bootloader mode after trying to flash this kernel on Android 10 beta fota..and i cant reboot into twrp recovery and system..
Click to expand...
Click to collapse
flash the boot.img extracted from the android 10 beta firmware via fastboot.
Kernel is made for Android Pie as stated in the OP.
Welcome bro and thanks for the first rog 2 custom kernel.. ?
After flashing in twrp it says i should flash companion magisk module. Is there one yet?
mohammed510 said:
Welcome bro and thanks for the first rog 2 custom kernel.. ?
After flashing in twrp it says i should flash companion magisk module. Is there one yet?
Click to expand...
Click to collapse
Oh that’s a remnant of another kernel in the flashing script.
No there is none needed. I’ll remove that message in the next release!
thanks for the hint!
You just gave me a reason to unlock my bootloader and go back to Pie
What a day! Thanks a lot @Freak07! I'm happy for you being around!
Cheers,
anthonws.
sakamaki izayoi said:
please help..now my device stuck and keep looping in bootloader mode after trying to flash this kernel on Android 10 beta fota..and i cant reboot into twrp recovery and system..
Click to expand...
Click to collapse
Extract the boot.img from Update and flash it under .img in twrp.
Goodluck
Very thanks
Please work on power saving and governor
Thank you for joining the ROG 2 Forums @Freak07
apollo3x said:
Extract the boot.img from Update and flash it under .img in twrp.
Goodluck
Click to expand...
Click to collapse
How to extract the Payload file of Android 10 FOTA?
The current Payload dumper doesn't support it.
Thank you so much for your hard work, I can't wait for you to make an version for Android 10 , hopefully once we have a custom kernel we can finally enjoy the 6000 mah battery
Mohamad313 said:
Very thanks
Please work on power saving and governor
Click to expand...
Click to collapse
avivv said:
Thank you so much for your hard work, I can't wait for you to make an version for Android 10 , hopefully once we have a custom kernel we can finally enjoy the 6000 mah battery
Click to expand...
Click to collapse
No idea about Android 10, but I’m enjoying the 6000mah on Pie already. That Android 10 build floating around is no finished or final piece of software.
I’ll attach my current stats from this morning.
No extensive gaming, mainly browsing, exploring the phone, massaging, videos, some calls etc.
but all on constant 120hz.
Wow that's great stats, when I had android 9 I the battery life was worst than I expected, if there was a way to rollback to android 9 without wiping the data I would have done it just to try this kernel.
would it be possible to add battery charge limiting support? currently apps like ACC don't work with this phone.