Best Alternative to Franco Kernal and its App - ONE Q&A, Help & Troubleshooting

I need to update to Android 5.1, and I've heard that 5.0 kernals don't work on 5.1. However Franco has been AWOL for a while and hasn't posted an updated kernal for 5.1. So I need an alternative to Franco Kernal with a similar feature set and an nice companion app(official or otherwise).
Features I use the most:
-CPU control
-Volume boost
-Color control with Flux
Any suggestions?
PS: If somebody has built a Franco Kernal from source for 5.1, that'd be fine as well.

Related

[Q] Q: Kernel Testing - Netarchy Sound Driver

I've recently Installed Netarchy Nexus - 1.3.4-cfs-2.3.4 (For stock 2.3.4 roms) on my Rooted Stock Nexus S i9020A running 2.3.4 and suddenly my phone refuses to load the voodoo sound driver.
Voodoo Control Plus say that My Nexus S doesn't run a kernel supporting extended sound controls. My phone Loads the voodoo video drivers just fine however. Voodoo Control Plus has SuperUser permissions, so I'm interested if anyone has any ideas regarding what could be causing the conflict with the sound driver. I read somewhere that widget locker can cause problems so I disabled it. I would have posted this question in the Netarchy forum, but apparently I don't have the required number of posts just yet, because I'm pretty self sufficient and relatively decent at hacking my phone most days.
Any ideas or help would be greatly appreciated. Netarchy worked fine until I migrated to stock 2.3.4
Netarchy Nexus - 1.3.4-cfs-2.3.4 (For stock 2.3.4 roms) may simply not support Version 9 of the Voodoo Kernel Module just yet. It appears it was compiled with version 8. However, this still doesn't explain the module refusing to load at all from time to time.
Voodoo likes the stock Kernel for sound. Of course the stock Kernel doesn't support the video drivers.
guppetto said:
I've recently Installed Netarchy Nexus - 1.3.4-cfs-2.3.4 (For stock 2.3.4 roms) on my Rooted Stock Nexus S i9020A running 2.3.4 and suddenly my phone refuses to load the voodoo sound driver.
Voodoo Control Plus say that My Nexus S doesn't run a kernel supporting extended sound controls. My phone Loads the voodoo video drivers just fine however. Voodoo Control Plus has SuperUser permissions, so I'm interested if anyone has any ideas regarding what could be causing the conflict with the sound driver. I read somewhere that widget locker can cause problems so I disabled it. I would have posted this question in the Netarchy forum, but apparently I don't have the required number of posts just yet, because I'm pretty self sufficient and relatively decent at hacking my phone most days.
Any ideas or help would be greatly appreciated. Netarchy worked fine until I migrated to stock 2.3.4
Click to expand...
Click to collapse
Voodoo sound works fine in 1.3.4. Voodoo plus does not need to load a driver on my builds because the driver is already built in. If you are seeing the generic module load error, just hit continue and you should be fine. The bundled driver in voodoo plus only applies to kernels that dont have voodoo sound in them already.
Sent from my Transformer TF101 using Tapatalk
Beware of Voodoo Plus Upgrades
netarchy said:
Voodoo sound works fine in 1.3.4. Voodoo plus does not need to load a driver on my builds because the driver is already built in. If you are seeing the generic module load error, just hit continue and you should be fine. The bundled driver in voodoo plus only applies to kernels that dont have voodoo sound in them already.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
You're correct, it's not the Beta Kernel that has the issue. The most recent update of Voodoo Plus causes a conflict that prevents the voodoo sound driver from loading period. You're current Beta Kernel comes with version 8 of the sound driver and the recently updated Voodoo Plus now comes with version 9, but apparently, during the boot process a conflict is occurring on my Nexus S i9020A Stock 2.3.4 between you're Kernel Driver and the Latest Voodoo Plus Kernel driver because neither version of the sound driver is being loaded. The video driver loads just fine.
To make sure this was the issue, I used Titanium Backup to restore a previous version of Voodoo Plus and sure enough, while I received the module message, I could indeed hit continue and verify that version 8 of the driver baked into your Beta Kernel had in fact loaded. I'm not sure if Supercurio is aware. I doubt he tests Voodoo Plus against the various versions of kernels out there. You may want to make note of the potential issue in you're release notes if more of these questions pop up from those that have upgraded Voodoo Plus
Do you have any plans to update the voodoo sound driver to version 9 in one of your beta builds or will you stick with version 8 until you release your next stable build? Version 9 has Direct Hardware Amplification (Hardware based Bass Boost) that Many devices will greatly benefit from sound wise.
Oh yeah, thanks for the great Kernel work. You're Kernels gives amazing battery life and Keep My Nexus S running like a champ. I haven't even bothered to overclock my device because everything's running so smoothly with your kernel.
guppetto said:
You're correct, it's not the Beta Kernel that has the issue. The most recent update of Voodoo Plus causes a conflict that prevents the voodoo sound driver from loading period. You're current Beta Kernel comes with version 8 of the sound driver and the recently updated Voodoo Plus now comes with version 9, but apparently, during the boot process a conflict is occurring on my Nexus S i9020A Stock 2.3.4 between you're Kernel Driver and the Latest Voodoo Plus Kernel driver because neither version of the sound driver is being loaded. The video driver loads just fine.
To make sure this was the issue, I used Titanium Backup to restore a previous version of Voodoo Plus and sure enough, while I received the module message, I could indeed hit continue and verify that version 8 of the driver baked into your Beta Kernel had in fact loaded. I'm not sure if Supercurio is aware. I doubt he tests Voodoo Plus against the various versions of kernels out there. You may want to make note of the potential issue in you're release notes if more of these questions pop up from those that have upgraded Voodoo Plus
Do you have any plans to update the voodoo sound driver to version 9 in one of your beta builds or will you stick with version 8 until you release your next stable build? Version 9 has Direct Hardware Amplification (Hardware based Bass Boost) that Many devices will greatly benefit from sound wise.
Oh yeah, thanks for the great Kernel work. You're Kernels gives amazing battery life and Keep My Nexus S running like a champ. I haven't even bothered to overclock my device because everything's running so smoothly with your kernel.
Click to expand...
Click to collapse
Ok, an update of SU seems to now allow Version 9 of the sound driver to load using you're Beta Kernel. This is weird, but the desired result. An update of Voodoo Plus still breaks voodoo sound though.

[Q] CM11 and gamma settings

Hello! I have recently installed the CyanogenMod 11 M3. I've noticed that the option for display gamma settings aren't integrated, so I tried to install Franco's kernel in order to use his Nexus Display Control apk. The problem is that, despite Franco's kernel should be compatible with CM11, after flashing it the phone doesn't boot and freezes on Google logo.
Do I have another option to set display gamma? Otherwise how can I install and use Nexus Display Control apk? tnks
Hi,
With the last CM Franco kernel doesn't work (for now) since CM have indroduced some changes.
If you want to use the app you need a kernel that supports the same gamma control interface as Franco...
You can try this kernel for example, compatible with CM and with colour control: http://forum.xda-developers.com/showthread.php?t=2551441, it has its own app, don't know if Nexus Display will work with this kernel...
Franko does not work with cm11 or any CAF rom. You'll need to find a CAF kernel that does what you want it to.
Sent from my Nexus 5
What does "CAF" mean?
nicari92 said:
What does "CAF" mean?
Click to expand...
Click to collapse
Code aurora forum. It's coding that cm has moved to.
Sent from my Nexus 5
I've successfully flashed the Chaos Kernel and used the N5 Gamma Calibration apk. It works, but it is everything but user-friendly. Hope someone will develop something more intuitive.

Is there any kernel compatible with Display Control app?

A kernel similar to stock no elementalx or fk, thank you.

[Q] 4.4.3 kernel with color and gamma control?

Hi, is there any stock 4.4.3 kernel with color and gamma control?.
I know we have kernels to do this like Franco and others, but i want to stay with the stock kernel.
Thanks.
ElementalX allows you to choose stock tuning in the installer.
Thanks.

[Q] Overclocking in KitKat 4.4.4

Does anyone know a ROM or kernel that will support over clocking on the Nexus S running Kitkat 4.4.4 ?
Kytro said:
Does anyone know a ROM or kernel that will support over clocking on the Nexus S running Kitkat 4.4.4 ?
Click to expand...
Click to collapse
Devil kernel is still compatible and overclocks..
I'm using Guru Kernel http://forum.xda-developers.com/nexus-s/development/kernel-guru-t2783561 with Omni CM 11 KK 4.4.4 and can OC to 1.4, it also has memory booster to 409MB. Perfect stability except when using the camera, but I had that problem with the Matr1x kernel in JB Omni too even with a 1.2OC. I just remove the OC if I need to use the camera, which is rarely.
the OmniROM that you can find HERE is a 4.4.4 with selectable OC in the settings menĂ¹

Categories

Resources