Lower charge voltage (kernel patch) - Xperia Z1 Compact General

Is this worth of trying/practicing?
I see that several kernels have this option, ElementalX - Nexus 7 FHD for example.
Is there a way to somebody create "universal" (stock 4.4.4 kernel, doom kernel and aosp kernels) flashable zip for changing parameters?
And zip to reverting to original state.
Manual methods and explanation/instructions are also welcome if above are not possible.

Related

[Q] Franco Kernel with stock?

Stock with Franco:
Will it work? Will it give the same benefits as CM 10.1?
Will OTA work? If I sideload OTA will I have to reflash kernel?
CM 10.1:
If I flash new ROM/update ROM, will kernel stay?
Thanks,
Yes the kernel will work. The kernel and rom in CM10.1 is obviously different to stock and francos so im not sure how they compare - try both yourself ?
Im not sure about OTA. I would just flash a AOSP stock ROM every time there is an update just in case if you want to stay on stock.
If you flash a new ROM no the kernel will not stay you have to flash the kernel again as CM10.1 (like most ROMs) comes with its own kernel that will overwrite your current one.
I've been wanting to ask this about faux's kernel since I'm having the (very common) msm_hsic_host wakelock issue. Since we're on the subject: does anyone have a suggestion for the most stable, closest to stock, AOSP ROM?

[Q] Rom with init.d scripts, but custom kernel without init.d support

I have tried tons of different roms and kernels, and settled (provisionally) to slim bean ROM and franco kernel. However, I have noticed that while slim bean includes several scripts ini init.d, franco kernel does not support init.d scripts by default (I have read that this depends on its default initramfs), so that these scripts are not executed at boot. What should I do? Is perhaps the idea that those scripts are for slim bean stock kernel and that actually they should not be run with franco kernel, leading perhaps to some potential conflict? Or am I loosing some functionality in the rom, so that I should resort to one of those several ways to add init.d support to any kernel (such as uni-init and others: http://forum.xda-developers.com/showthread.php?t=1933849)?
Please note that I do not need to add other personal scripts to init.d, I wonder only if I am facing some kind of conflict between rom and kernel. Note also that I am not observing any practical negative effect ATM, I am only wondering if this general situation (rom with init.d scripts, custom kernel disabling them) is on purpose or something that I should fix.

[Q] Reflashing Stock Kernal...

Hello Guys
Need your help,
I have rooted my nexus 4 and have reflashed stock 4.2.2 rom, and i also have flashed Enhanced Stock 4.2.2 Kernel (STOCK + UV + HSIC Fixes + Gamma + Speaker)
I used Faux display app to calibrate the display
My main motive behind rooting was to get better colours and display..Now my main dilemma is that if i flash back the stock kernal and unroot my Nexus, will it go back to the original colour settings..?? or modified colours will be there
Please answer
You will not, of course, have the modified colors.
Sent from my iPad 4
Nope you will not have the modified colors. Thats the whole point of flashing custom ROMs and kernels to have additional features that the stock ROM/kernel cannot offer.

[Q] Rooting, flashing custom rom but necessary to flash a kernel as well?

Hi,
Quick question I am still having trouble wrapping my head around the concept about kernels. I am planning to root my nexus 4 and flash a custom rom (purity rom) but am i required to also flash a custom kernel? Or am I suppose to leave the kernel as is?
Thanks!
Next123 said:
Hi,
Quick question I am still having trouble wrapping my head around the concept about kernels. I am planning to root my nexus 4 and flash a custom rom (purity rom) but am i required to also flash a custom kernel? Or am I suppose to leave the kernel as is?
Thanks!
Click to expand...
Click to collapse
Depends upon your requirement .
As an example i use Fast USB charge a lot and is not available in any custom rom .
I also use Headphone volume boost which is yet again a kernel level change.
I would suggest you to use a custom kernel since it also gives better battery than stock .
If you are happy without it then forget about kernels . And in case u plan on flashing one make a CWM backup just in case.,
You could if you want to since you're already flashing custom roms. However, most custom rom come with custom kernel, so when you flash a custom rom it will replace your kernel with it's own. You can manually flash back your stock kernel if you want, using fastboot, but there is a flashable package as well in the Dev section.
Just know that due to codes and drivers, different kernels work with different roms. If you flash a 4.3 kernel to a 4.4 rom, it might lack certain necessary driver, such as PRIMA, so your wifi will no longer work. (You can fix this by flashing dePRIMAtor). CyanogenMod use Code Aurora Forum drivers, so if you use a kernel that doesn't support CAF, the screen colors will be messed up (you can lash a colorfix package which replace it with the non-CAF liboverlay.so).
A lot of people get wrapped too far up into flashing kernel and thinking it determine everything (performance + battery life) in their phone. As much of a heavy flasher that I am, I am willing to bet that you generally get the best battery life and stability just running stock. I did my own trial for this, with stock rom and kernel, the phone staying cooler and screen on time was longer. This is just my personal experience, it varies for each person.
But I mainly use custom kernel for features. Such as kernels that incorporate Faux color and sound, this allows changing their settings for much a better screen color and making the speaker louder. I also use the sweep2wake/sleep feature to turn on and off the screen.
If you intend to use custom kernels, I recommend using TricksterMod, it's the best app for modifying kernel settings.
Also just to mention this ahead of time, it's against XDA rules to make threads about what is the best rom/kernels.

Which kernels work on Lineageos?

Which kernels work on Lineageos? I'm interested in flashing vegito but I'm unclear if it works? It says to flash over only stock kernel, which lineageos doesn't have, but would it work if I flash stock kernel of lineageos first, then flash vegito?
lightningglasses said:
Which kernels work on Lineageos? I'm interested in flashing vegito but I'm unclear if it works? It says to flash over only stock kernel, which lineageos doesn't have, but would it work if I flash stock kernel of lineageos first, then flash vegito?
Click to expand...
Click to collapse
ElementalX, vegito and quark kernels should work on Lineage OS without issue (though still check their respective pages!)
By flashing only over the stock kernel, the instructions usually mean only flash over the kernel that originally came with the ROM. I imagine it's a bit confusing given the Motorola ROM kernel is also regarded as the stock kernel, but in this case, the 'stock kernel' refers to whatever kernel the ROM you flashed came with. (As an aside, don't try to flash the Motorola kernels on custom ROMs...)
Lineage OS, as with other custom and stock (Motorola) ROMs come with their own kernel included, which you replace when you flash the custom kernel. A reason for requiring that you flash over the stock (originally coming with the ROM you've flashed) kernel only appears to be because custom kernels modify the ram disk of the kernel, which other custom kernels will be incompatible with and may lead to random issues. The stock (in this case, the original ROM kernel) is clean and has no modified ram disk, so should be stable, and thus suitable for flashing a custom kernel.
If you have the original Lineage OS kernel already, then you can flash vegito in TWRP. I'd recommend taking a TWRP backup of your system and of your boot partition before flashing. The boot partition should contain your kernel as it was, so if it's clean, you can revert back from vegito by flashing the boot partition backup. And the system backup is just in case anything happens!
Alternatively, a dirty flash of your current Lineage OS build may flash an original kernel if you don't have one already.

Categories

Resources