[KERNEL][Cedric][underclock][block wakelocks] - Moto G5 ROMs, Kernels, Recoveries, & Other Develop

{
"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"
}
Radium Kernel
This is the ONLY custom kernel yet for Moto G5 Cedric. Proudly brought to you by the team behind Radium kernel, @CodeZero, and @infixremix, this kernel supports many features.
Features
Code:
[LIST]
[*]Display tweaks
[*]Wake lock blocker
[*] Battery optimisations
[*]Better IO bfq , deadline
[*]Sound tweaks
[*]Fsync switch on and off
[*]Fast charge compatible
[*]Underclockable
[*]Kernel version 3.18.48
[/LIST]
Known issues
VDD does does not work with underclock
Please report Bugs to me on telegram @infixremix
Downloads
Kernel
XDA:DevDB Information
RADIUM kernel for Moto G5 (Cedric), Kernel for the Moto G5
Contributors
infixremix, CodeZero
Source Code: [url]https://github.com/infixremix/android_kernel_motorola_msm8937-1[/URL]
Kernel Special Features: [*]Display tweaks [*]Wake lock blocker [*] Battery optimisations [*]Better IO bfq , deadline [*]Sound tweaks [*]Fsync switch on and off [*]Fast charge compatible [*]Underclockable [*]Kernel version 3.18.48
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-10-29
Created 2017-10-29
Last Updated 2017-10-29

---

RESERVED

---

infixremix said:
RESERVED
Click to expand...
Click to collapse
Awesome Job!
(nice Logo )

---

Hope this kickstarts the development of other kernels for our device too!

---

Great Job! Since I am already running the kernel the whole weekend I can say that it runs rock solid. Now let's see if we can get hotplugging going.

---

Great work, our first Motorola G5 Cedric kernel. ? Thanks a lot lad's.

---

Just a few things iv noticed
please change the updater script - I know its meant to be a joke but its not really in the spirit of XDA
Onto the kernel itself
Can you explain the following
The big is set to a default of 652mhz yet in kernel Adiutor it doesn't show this in the options but it does show an entry for 249Mhz
The little is still set to a min of 768MHz - can this be underclocked?
Here are some screenshots to explain the points above

---

TheFixItMan said:
Just a few things iv noticed
please change the updater script - I know its meant to be a joke but its not really in the spirit of XDA
Onto the kernel itself
Can you explain the following
The big is set to a default of 652mhz yet in kernel Adoitor it doesn't show this in the options but it does show an entry for 249Mhz
The little is still set to a min of 768MHz - can this be underclocked?
Here are some screenshots to explain the points above
Click to expand...
Click to collapse
Why would we under clock small it calls for big if the frequency is over used there fore big cluster wouldn't need under clock , the reason why its not avalible is because that's what the voltage table picks which in this case was the mid value . I will be looking too fix this , personally I don't see a problem with the update-binary .
But I will Change thanks for your advice !

---

infixremix said:
Why would we under clock small it calls for big if the frequency is over used there fore big cluster wouldn't need under clock , the reason why its not avalible is because that's what the voltage table picks which in this case was the mid value . I will be looking too fix this , personally I don't see a problem with the update-binary .
But I will Change thanks for your advice !
Click to expand...
Click to collapse
it also showing core 1 to be permanently offline and it fails to load big frequencies report chart so its hard to run an analysis so I can compare with lineageos kernel
So far in the reports it shows the little to be stuck on 1094mhz and the big at 960mhz but im not sure if that is accurate due to the reporting not working

---

TheFixItMan said:
it also showing core 1 to be permanently offline and it fails to load big frequencies report chart so its hard to run an analysis so I can compare with lineageos kernel
So far in the reports it shows the little to be stuck on 1094mhz and the big at 960mhz but im not sure if that is accurate due to the reporting not working
Click to expand...
Click to collapse
Umm testers never seemed to have this , I think I'm gonna close the thread then that's not normal

---

infixremix said:
Umm testers never seemed to have this , I think I'm gonna close the thread then that's not normal
Click to expand...
Click to collapse
keep it open so others can test it as it boots fine so theres no harm to anyone testing
Have a look at kernel Adiutor and see if its the same on yours

---

TheFixItMan said:
keep it open so others can test it as it boots fine so theres no harm to anyone testing
Have a look at kernel auditor and see if its the same on yours
Click to expand...
Click to collapse
Its not one other guy had it , but do u have core control and vdd and thermal soc on ? If you do only keep one on I suggest core control never had a problem 3 or 4 people didn't have it the one that did didn't know what he was doing he restored bootimg re installed kernel and after 3 days he never had the problem again

---

infixremix said:
Its not one other guy had it , but do u have core control and vdd and thermal soc on ? If you do only keep one on I suggest core control never had a problem
Click to expand...
Click to collapse
I ran it with its default settings - What i'll do is i'll reset kernel Adiutor and test it again

---

TheFixItMan said:
I ran it with its default settings - What i'll do is i'll reset kernel Adiutor and test it again
Click to expand...
Click to collapse
If u have again I'd suggest reverting and installing again if this happens again I will close the thread

---

infixremix said:
If u have again I'd suggest reverting and installing again if this happens again I will closa the thread
Click to expand...
Click to collapse
so I flashed back the lineageos kernel
Kernel Adiutor reported all cores running with the big at 960mhz and little at 728mhz
Turned off all my start at boot options (although when I first tested I stopped it applying them on startup but just to make sure)
Flashed your kernel
It seems to be working now however
little is stuck at 1049mhz - this is because your little gov is set to performance - Changing this to interactive means the little now runs at 768mhz
also big keeps jumping up at 1401mhz where on lineageos kernel it was a stable 960mhz

---

TheFixItMan said:
so I flashed back the lineageos kernel
Kernel Adiutor reported all cores running with the big at 960mhz and little at 728mhz
Turned off all my start at boot options (although when I first tested I stopped it applying them on startup but just to make sure)
Flashed your kernel
It seems to be working now however
little is stuck at 1049mhz - this is because your little gov is set to performance - Changing this to interactive means the little now runs at 728mhz
Click to expand...
Click to collapse
OK thank you for helping

---

infixremix said:
OK thank you for helping
Click to expand...
Click to collapse
gone back into Kernel Adiutor and all the big cores are offline - I doubt they actually are its just it cant get the reporting
So theres something wrong with the reporting of the frequencies which needs to be fixed

---

TheFixItMan said:
gone back into Kernel Adiutor and all the big cores are offline - I doubt they actually are its just it cant get the reporting
So theres something wrong with the reporting of the frequencies which needs to be fixed
Click to expand...
Click to collapse
Ok I'm gonna close the thread till further notice

---

infixremix said:
Ok I'm gonna close the thread till further notice
Click to expand...
Click to collapse
like I said - no harm leaving it open as people on xda can contribute and those with better kernel knowledge than I have can suggest things
get your testers to use Kernel Adiutor and wait for about 5mins after the phone has booted and then keep opening kernel Adiutor closing it wait a min turn the screen off and so on and then check kernel Adiutor again and see what the reporting says
---------- Post added at 10:15 PM ---------- Previous post was at 09:55 PM ----------
oh and just so people know - this kernel is using a different wifi module to what lineageos uses so if people do test this kernel and then revert back to lineageos kernel please make sure if you replace the wifi module with the one from lineageos or you wont be able to turn on wifi

---

I have none of the mentioned problems. I set big and small to "interactive" and everything is fine. Scaling seems normal. No core is ever offline.