[Kernel tweaks][for LineageOS14.1and AEX][montana-xt1793][rainbow-32bit] - Moto G5S ROMs, Kernels, Recoveries, & Other Devel

{
"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"
}
Rainbow-Kernel 3.18.101
First!- i'm not a developper, so dont shoot me, i do this like a hobby!
Second!- each file posted are tested first by me on my device(dont want to kill someone else device )
original kernel forked from here to my github and reworked
Thanks to @kalyansundhar
fixed compiling-errors and tweaked
Tweaks for now:
first release added new governors
-Lionheart
-bioshok
-alukard
-darkness
6-02-2018 added new I/O schedullers
-row
-sio
-zen
9-2-2018 CPU over/underclock
overclocked to 1497Mhz
underclocked to249Mhz
16-02 update
+ fiops I/O scheduller
set selinux PERMISIVE
9-07 update
+KSM(Kernel Samepage Merging)
changed alucard, darkness, alessa
modules
5-09 added kernel v3.18.101
kernel v3.18.63 patched v.3.18.101
GPU underclocked to 160Mhz
(in work for overcloking GPUto 650Mhz)
8-09 added CPU Hotplug
MSM Hotplug
MSM MPDecision Hotplug
Tweaks wich i want to add:
cpu/gpu over/under clock for better performances
many other tweaks available for kernel( i can say i'm a noob in this so i have to learn about them first)
kernel v3.18.101 compiled with Ubert-4.9.4 toolchain
Kernel tested on LineageOS-14.1 rom!
Download the flashable.zip
and flash it with TWRP, then reboot
*dont forget to make a backup first for all rom partitions
in case of problems, you can restore the phone
enjoy by your new kernel!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
* to change different governors use "Kernel adiutor.apk" from play-store or simmilar apk
** need root for using this and a custom (TWRP)recovery
*** dont use stok recovery
Download kernel v3.18.101(8-09-2018)
Credits:
@kalyansundhar
to all contributors to make Moto-G5s better than ever!
kernel source https://github.com/vaserbanix/Reworked_android_kernel_motorola_msm8937
Thankyou!
Ps. if i miss something, just let me know

---

THANKS, I test away
1st test crDroid bootloop

---

lohanbarth said:
THANKS, I test away
1st test crDroid bootloop
Click to expand...
Click to collapse
extract the zImage from my boot.img and pack it in crDroid boot.img and try again
Sent from my Moto G5s using Tapatalk

---

Great work!
Some questions:
What can we do with it?
Support for 1794?(NFC?)
Battery improvement?
Can you make a zip flashable?
Many thanks for your hard work!

---

GoldeneyeS2 said:
Great work!
Some questions:
What can we do with it?
Support for 1794?(NFC?)
Battery improvement?
Can you make a zip flashable?
Many thanks for your hard work!
Click to expand...
Click to collapse
*available governors, are about 50 different governors
each one have his own "settings" for performance, battery and compatibilities
is useles to add all in the kernel and is good to make a selection of them
i added few now and i plan to add another 3-4, just to have option to choose.
*kernel source has nfc support and is enabled, so it should work on 1794.(i cant test it)
*battery improvement depend all the time by the user and thats new governors can help.
*yes, i will do it
Thanks!
Edit!
flashable.zip added in first post(atachaments)

---

vaserbanix said:
extract the zImage from my boot.img and pack it in crDroid boot.img and try again
Sent from my Moto G5s using Tapatalk
Click to expand...
Click to collapse
ok I test early in the week.

---

lohanbarth said:
ok I test early in the week.
Click to expand...
Click to collapse
you can now to flash the zip atached over any rom.
it will replace zImage(kernel) and dtb files in boot.img without changing the ramdisk!
Sent from my Moto G5s using Tapatalk

---

kernel update
added new I/O schedullers
-row
-sio
-zen

---

thx mate .
works well but I'm waiting for more additions

---

Good work, well done! Any chances to volume adjust feature? Loudspeaker volume, headphones. AFAIK Kernel Adiutor can control this, if it present.

---

MoonPWR said:
Good work, well done! Any chances to volume adjust feature? Loudspeaker volume, headphones. AFAIK Kernel Adiutor can control this, if it present.
Click to expand...
Click to collapse
Thankyou!
i dont know if that's can be modified in kernel, but i will chek.
also the audio volume can be increased from system/etc/mixer_paths.xml file
editing this lines:
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="RX2 Digital Volume" value="84" />
<ctl name="RX3 Digital Volume" value="84" />
"84" is the standard value and upgrading them to 85, 86, 87, ++ but not much becouse the sound will be distorsioned, will increase the sound volume.
recomended value form me, is max 88

---

CPU over/underclocked
see the values on firs post!
some feedbacks are wellcome!
thankyou!

---

new update
+ fiops I/O scheduller
set selinux Permisive
Thankyou!

---

vaserbanix said:
new update
+ fiops I/O scheduller
set selinux Permisive
Thankyou!
Click to expand...
Click to collapse
Great work!
Many thanks.
Why the selinux to permisive?
Can you help with this project?
https://forum.xda-developers.com/moto-g5s/how-to/discussion-treble-support-motorola-g5s-t3750093
You now a lot of kernels and help is always great full.

---

GoldeneyeS2 said:
Great work!
Many thanks.
Why the selinux to permisive?
Can you help with this project?
https://forum.xda-developers.com/moto-g5s/how-to/discussion-treble-support-motorola-g5s-t3750093
You now a lot of kernels and help is always great full.
Click to expand...
Click to collapse
"Permissive versus enforcing
A SELinux-hardened system will run with SELinux in enforcing mode, meaning that the SELinux policy is in effect and things that it doesn't want to allow won't be allowed. But when trying to debug permission problems, it might make sense to temporarily disable SELinux. In this case, you can opt to have SELinux run in permissive mode, either for the entire system, or for a specific (set of) types."
related to "help" in that project
OEM partition has only 450Mb, will not be a very important space saver.
system partition has about 3.3Gb and in lineage(for example) is used only 900Mb the rest are free(2.3Gb)
also keeping the original PIT is recomended for the future stok updates
most of the user will want to revert to stok rom (time to time) and modified PIT will make that complicate without a real necesary reazon
this is my opinion(only my opinion)
Thankyou!

---

vaserbanix said:
"Permissive versus enforcing
A SELinux-hardened system will run with SELinux in enforcing mode, meaning that the SELinux policy is in effect and things that it doesn't want to allow won't be allowed. But when trying to debug permission problems, it might make sense to temporarily disable SELinux. In this case, you can opt to have SELinux run in permissive mode, either for the entire system, or for a specific (set of) types."
related to "help" in that project
OEM partition has only 450Mb, will not be a very important space saver.
system partition has about 3.3Gb and in lineage(for example) is used only 900Mb the rest are free(2.3Gb)
also keeping the original PIT is recomended for the future stok updates
most of the user will want to revert to stok rom (time to time) and modified PIT will make that complicate without a real necesary reazon
this is my opinion(only my opinion)
Thankyou!
Click to expand...
Click to collapse
Thanks for your answer and opinion.:good:
Its not about a space saver or installing lineage on OEM partition. We want to use the OEM partition as Vendor place in Treble support. The kernel will mount OEM as Vendor and symlink it to the TWRP recovery.
If someone wants back to stock he can flash all the stock files over the existing. We are not changing the PIT.
Do you understand Treble?

---

GoldeneyeS2 said:
Do you understand Treble?
Click to expand...
Click to collapse
after your question i read better about that subject!
https://www.androidauthority.com/project-treble-818225/
https://www.xda-developers.com/how-project-treble-revolutionizes-custom-roms-android-oreo/
others too
for this, all developpers will must be reborn, dropped a lot of their work and reconsider all form start
little hard to do that but to be on top they will do, if not all at least some of them
security will be improved! dont worth to change only for that
system.img instalable on many different devices! yes this is a good thing but will take some tame until it will work how is projected
for custom's rom's!
and "Yes it can come"
also i repaked that XperienceOS for mi3s from new.dat to meta-data for better wiev without install
download the rom and study it
https://drive.google.com/open?id=1CpfoNo2gX6lg3li0aqL_gtJ1zQIqIOca
!!! do not install it!!!!

---

vaserbanix said:
after your question i read better about that subject!
https://www.androidauthority.com/project-treble-818225/
https://www.xda-developers.com/how-project-treble-revolutionizes-custom-roms-android-oreo/
others too
for this, all developpers will must be reborn, dropped a lot of their work and reconsider all form start
little hard to do that but to be on top they will do, if not all at least some of them
security will be improved! dont worth to change only for that
system.img instalable on many different devices! yes this is a good thing but will take some tame until it will work how is projected
for custom's rom's!
and "Yes it can come"
also i repaked that XperienceOS for mi3s from new.dat to meta-data for better wiev without install
download the rom and study it
https://drive.google.com/open?id=1CpfoNo2gX6lg3li0aqL_gtJ1zQIqIOca
!!! do not install it!!!!
Click to expand...
Click to collapse
Many many thanks for your support.
Can you maybe add the above to the right section?([Discussion] TREBLE Support for Motorola G5s)

---

arm64bit-kernel
so, i managed to finish compiling the arm64bit-kernel!
also are some problems here:
1. the file resulted are to large for G5s boot partition,
boot partition has 16Mb and the file has 27Mb(not enough space)
that can be from my settings(wrong) or not
2. no 64bit rom to test in case i can get the correct size!
i put my "Telegram" adress here!
if any experienced developper can help,
please contact me!
https://t.me/vaserbanix
Thankyou!

---

vaserbanix said:
so, i managed to finish compiling the arm64bit-kernel!
also are some problems here:
1. the file resulted are to large for G5s boot partition,
boot partition has 16Mb and the file has 27Mb(not enough space)
that can be from my settings(wrong) or not
2. no 64bit rom to test in case i can get the correct size!
Thankyou!
Click to expand...
Click to collapse
Hello,
1. You must rename Image.gz to boot.img-zImage. (The size will be something like 9.2mb)
2. Because there is no Vendor and Device tree for ARM64. Maybe we can port something from Cedric(Moto G5)?.