i used sensei kernel and kernel adiutor in miui7, but my mi4i still overheating, how should i set kernel adiutor ??
There is a termal config file which bypass the settings set by the app, try finding an override
so the thermal settings option what should I wear?
herjanasatya said:
i used sensei kernel and kernel adiutor in miui7, but my mi4i still overheating, how should i set kernel adiutor ??
Click to expand...
Click to collapse
uninstal your Kernel Adiutor
go to >> \system\etc
delete your thermal-engine-8939.conf and thermal-engine-8939.IN.conf
use this init.qcom.post_boot.sh (download on attachment) to replace init.qcom.post_boot.sh, set permission to rw-r-r and reboot
Now your device not overheating anymore. No lag, fast charge active, fast cooling down.
Glembozt said:
uninstal your Kernel Adiutor
go to >> \system\etc
delete your thermal-engine-8939.conf and thermal-engine-8939.IN.conf
use this init.qcom.post_boot.sh (download on attachment) to replace init.qcom.post_boot.sh, set permission to rw-r-r and reboot
Now your device not overheating anymore. No lag, fast charge active, fast cooling down.
Click to expand...
Click to collapse
thanks bro, i'll try now
Works on Resurrection Remix MM
I couldn't find 'thermal-engine-8939.IN.conf' but I could do the rest. Running Resurrection Remix MM 6. This works well. No lags or performance drops. Cooling is good.
Glembozt said:
uninstal your Kernel Adiutor
go to >> \system\etc
delete your thermal-engine-8939.conf and thermal-engine-8939.IN.conf
use this init.qcom.post_boot.sh (download on attachment) to replace init.qcom.post_boot.sh, set permission to rw-r-r and reboot
Now your device not overheating anymore. No lag, fast charge active, fast cooling down.
Click to expand...
Click to collapse
is it work for los 14.1?
Glembozt said:
uninstal your Kernel Adiutor
go to >> \system\etc
delete your thermal-engine-8939.conf and thermal-engine-8939.IN.conf
use this init.qcom.post_boot.sh (download on attachment) to replace init.qcom.post_boot.sh, set permission to rw-r-r and reboot
Now your device not overheating anymore. No lag, fast charge active, fast cooling down.
Click to expand...
Click to collapse
I f+++ked up, the phone drain battery and overheats like crazy but i did not have the backup for all three of the adjusted files. Can someone please help me?
Edit: I forgot the change permission last step and now it works fine. Thank for this thread.
Glembozt said:
uninstal your Kernel Adiutor
go to >> \system\etc
delete your thermal-engine-8939.conf and thermal-engine-8939.IN.conf
use this init.qcom.post_boot.sh (download on attachment) to replace init.qcom.post_boot.sh, set permission to rw-r-r and reboot
Now your device not overheating anymore. No lag, fast charge active, fast cooling down.
Click to expand...
Click to collapse
Can you explain in layman terms about the changes? Your trick worked but my phone battery is draining fast (~2 hours to drain completely) when surfing internet.
try to underclock your deice from kerner adiutor
i want 3 files deletes
Glembozt said:
uninstal your Kernel Adiutor
go to >> \system\etc
delete your thermal-engine-8939.conf and thermal-engine-8939.IN.conf
use this init.qcom.post_boot.sh (download on attachment) to replace init.qcom.post_boot.sh, set permission to rw-r-r and reboot
Now your device not overheating anymore. No lag, fast charge active, fast cooling down.
Click to expand...
Click to collapse
my phone locked in mi logo and restart again and again
i want 3 files
can u help me?
Related
How to set the settings like cpu frequency after installing elementalx kernel?
I installed the elementalx by using TWRP recovery in my nexus 5 (android 5.0.1), but how to set the settings like set the CPU frequency and enable double tap to wake up? Should I install some apps?
If I want to update later, should I install the origin kernel?
Thank you!!!
xcs1234 said:
How to set the settings like cpu frequency after installing elementalx kernel?
I installed the elementalx by using TWRP recovery in my nexus 5 (android 5.0.1), but how to set the settings like set the CPU frequency and enable double tap to wake up? Should I install some apps?
Click to expand...
Click to collapse
From ElementalX thread:
The config file is located at /etc/elementalx.conf. You can edit this file to change kernel settings. Whatever is set in this file will take effect when the device is booted (unless other scripts or apps interfere!)
Read OP for more details.
xcs1234 said:
If I want to update later, should I install the origin kernel?
Thank you!!!
Click to expand...
Click to collapse
Nope
xcs1234 said:
How to set the settings like cpu frequency after installing elementalx kernel?
I installed the elementalx by using TWRP recovery in my nexus 5 (android 5.0.1), but how to set the settings like set the CPU frequency and enable double tap to wake up? Should I install some apps?
If I want to update later, should I install the origin kernel?
Thank you!!!
Click to expand...
Click to collapse
I've been using ElementalX for some time. There's an app in the play store specifically for ElementalX kernel.
I always installed the kernel with default settings in AROMA installer since the app lets you tune all the values anyway
experience7 said:
I've been using ElementalX for some time. There's an app in the play store specifically for ElementalX kernel.
I always installed the kernel with default settings in AROMA installer since the app lets you tune all the values anyway
Click to expand...
Click to collapse
what's the name of that app?
ElementalX kernel
Here's the Play Store link: https://play.google.com/store/apps/details?id=flar2.elementalxkernel
Primokorn said:
From ElementalX thread:
The config file is located at /etc/elementalx.conf. You can edit this file to change kernel settings. Whatever is set in this file will take effect when the device is booted (unless other scripts or apps interfere!)
Read OP for more details.
Nope
Click to expand...
Click to collapse
If I want to install another kernel, can I just install it in the recovery(using the install button in the recovery mode)? Should I clean the present kernel, then install another kernel in the recovery?
There are recommendations that you should dirty flash the original ROM (which then overwrites your current kernel with the stock one). If you're on stock Android (Vanilla), fastboot flash the boot.img from the appropriate factory image. Then use your recovery to install zip > choose your kernel zip.
I've always used the 'easy method' by just dirty-flashing the kernel I want to try. Worked fine all the time [emoji14]
Hey guys,
I'm into the Android from the very beginning and I would love to get rid of a problem which is driving me crazy for some time
I was trying to flash the Viper driver to get the great sound quality again. I'm now on the latest nougat.
Already unlocked the bootloader, rooted it and flashed the TWRP. Saw an thread about how to install it properly on the Honor8 and I did everything correct in my opinion.
I have the 1.26.2-meefik busybox now installed in system/xbin path (which seems to be working correctly overall) and otherwise everything seems working good except that when I try to open the Viper it says that I don't have root OR that i have to install the driver, and after pressing yes my phone just reboots and does the very same thing as previously.
Am I missing something?
Feel free to ask something more if you need.
I had this same situation, just kept installing the driver, reboot, repeat, making no progress... I finally got mine to work thank goodness! Are you remembering to use a root file Explorer and go to /vendor/etc and rename the file named audio_effects.config to audio_effects.config.bak after flashing but before installing V4A? That was my main problem. And you have to be sure to do it on a clean setup, so if you've already installed V4A you need to clean out and start again. Also u need a kernel auditor to set selinux to permissive upon boot. These two steps are key...
Sent from my HUAWEI FRD-L04 using XDA Labs
Have same problem but this fix BigBrad75 gave didn't work.
Isn't that what I suggested? Not being a smarta**, but seriously wondering if I have got a step messed up or backwards or something...? Cause it gave me tons of trouble till I finally got lucky and it actually took
Sent from my HUAWEI FRD-L04 using XDA Labs
Rommco05 said:
I got same problem, solutions for my was:
1. install BusyBox by Meefik ( Google play)
2. install Kernel Adiutor ( https://github.com/yoinx/kernel_adiutor/raw/master/download/app/app-release.apk ) ( Kernel Adiutor from Google play dont work)
3. opem BusyBox tap Install
4. open Kernel Adiutor and go to Misc Controls, change Current SELinux Status: Permissive (after reboot SELinux stay premissive :good
5. flash Viper4 via TWRP
6. go to folder: root/vendor/etc and rename file from audio_effects.conf to audio_effects.conf.bak
7. open Viper4
8. Install driver (thats can take 1-3 min)
9. reboot - done
Click to expand...
Click to collapse
Hi Rommco05,
there are different versions of V4A floating around. Which Version of Viper4Android did you use? Download from where?
Greets....
Rommco05 said:
Hi, Honor 8/Theme,Apps,Modes/https://forum.xda-developers.com/honor-8/themes/viper4android-2-5-0-5-installation-t3468389
Click to expand...
Click to collapse
Thanks, worked for me just as you described. I'm on L09C432B389 BTW, if anybody is interested...
Thanks
I have a Interesting Issue Regarding kernel auditor whenever I install the app or when the kernel auditor has been grated superuser rights appears or the apply on boot script runs my mobile network gets disabled in SIM settings. I'm Using Lineage os 14.1 Official Magisk and Firekernel. I'm really Stuck Please HELP
minilandl said:
I have a Interesting Issue Regarding kernel auditor whenever I install the app or when the kernel auditor has been grated superuser rights appears or the apply on boot script runs my mobile network gets disabled in SIM settings. I'm Using Lineage os 14.1 Official Magisk and Firekernel. I'm really Stuck Please HELP
Click to expand...
Click to collapse
Send Screenshots
minilandl said:
I have a Interesting Issue Regarding kernel auditor whenever I install the app or when the kernel auditor has been grated superuser rights appears or the apply on boot script runs my mobile network gets disabled in SIM settings. I'm Using Lineage os 14.1 Official Magisk and Firekernel. I'm really Stuck Please HELP
Click to expand...
Click to collapse
I immediately suspect majisk.
I am using:
1. Adaway after enabling systemless in magisk settings
2. Greenify4magisk - helpful in hibernating notification hungry and backgroung running application
Both safetynetcheck are green.
Cant find SELinux permissive module. Can someone help? Also what other modules are you using?
Aj.GaLaxY aCE said:
I am using:
1. Adaway after enabling systemless in magisk settings
2. Greenify4magisk - helpful in hibernating notification hungry and backgroung running application
Both safetynetcheck are green.
Cant find SELinux permissive module. Can someone help? Also what other modules are you using?
Click to expand...
Click to collapse
For SELinux changes you could use for example this app, very simple and you can quickly toggle it (for example to test if permissive still needed after next system update).
I used to use Greenify4magisk, but in fact it works completely fine even without it. In Oreo it might not be needed at all, system has quite good doze mode, I am getting below 0.2% of idle battery usage (vs. 0.5% on Nougat).
The only module which I use is the one which I made for myself (enable EIS, C2API, fix video recording sound, add more volume steps)
Gcam freezes
_mysiak_ said:
For SELinux changes you could use for example this app, very simple and you can quickly toggle it (for example to test if permissive still needed after next system update).
I used to use Greenify4magisk, but in fact it works completely fine even without it. In Oreo it might not be needed at all, system has quite good doze mode, I am getting below 0.2% of idle battery usage (vs. 0.5% on Nougat).
The only module which I use is the one which I made for myself (enable EIS, C2API, fix video recording sound, add more volume steps)
Click to expand...
Click to collapse
Could you share that module, please? I added persist.camera.HAL3,enabled=1 to the build prop but the GCAM take a long time to open and even my stock camera. I don´t know what I am making wrong.
paqr28 said:
Could you share that module, please? I added persist.camera.HAL3,enabled=1 to the build prop but the GCAM take a long time to open and even my stock camera. I don´t know what I am making wrong.
Click to expand...
Click to collapse
You're doing it right, but there is a bug in Oreo, at the moment there is only one known workaround - set SELinux to permissive mode (for example with this or any other app/method). Gcam and stock camera will start fast in permissive mode.
Slow motion GCAM
_mysiak_ said:
You're doing it right, but there is a bug in Oreo, at the moment there is only one known workaround - set SELinux to permissive mode (for example with this or any other app/method). Gcam and stock camera will start fast in permissive mode.
Click to expand...
Click to collapse
Thank you, It finally works with SELinux to permissive, Did the Slow motion in gcam works for you? That is the only thing that doesn´t work for me.
paqr28 said:
Thank you, It finally works with SELinux to permissive, Did the Slow motion in gcam works for you? That is the only thing that doesn´t work for me.
Click to expand...
Click to collapse
Slow motion requires different media profile files, but when you replace them, stock camera will crash with slow mo mode.. As I never use this mode and I prefer fully working stock camera, I just let it be..
_mysiak_ said:
For SELinux changes you could use for example this app, very simple and you can quickly toggle it (for example to test if permissive still needed after next system update).
I used to use Greenify4magisk, but in fact it works completely fine even without it. In Oreo it might not be needed at all, system has quite good doze mode, I am getting below 0.2% of idle battery usage (vs. 0.5% on Nougat).
The only module which I use is the one which I made for myself (enable EIS, C2API, fix video recording sound, add more volume steps)
Click to expand...
Click to collapse
Couldyou please share your module? It works on oreo?
IronJacob said:
Couldyou please share your module? It works on oreo?
Click to expand...
Click to collapse
Please find the module attached, it works for me on Oreo, no guarantees though
It adds these build.prop values:
Code:
persist.camera.eis.enable=1
persist.camera.HAL3.enabled=1
ro.qc.sdk.audio.fluencetype=fluencepro
ro.config.vc_call_vol_steps=14
ro.config.media_vol_steps=30
audio.safemedia.bypass=true
_mysiak_ said:
Please find the module attached, it works for me on Oreo, no guarantees though
It adds these build.prop values:
Click to expand...
Click to collapse
Thank you very much
_mysiak_ said:
For SELinux changes you could use for example this app, very simple and you can quickly toggle it (for example to test if permissive still needed after next system update).
I used to use Greenify4magisk, but in fact it works completely fine even without it. In Oreo it might not be needed at all, system has quite good doze mode, I am getting below 0.2% of idle battery usage (vs. 0.5% on Nougat).
The only module which I use is the one which I made for myself (enable EIS, C2API, fix video recording sound, add more volume steps)
Click to expand...
Click to collapse
Fix video recording sounds? Is it bad?
_mysiak_ said:
Please find the module attached, it works for me on Oreo, no guarantees though
It adds these build.prop values:
Code:
persist.camera.eis.enable=1
persist.camera.HAL3.enabled=1
ro.qc.sdk.audio.fluencetype=fluencepro
ro.config.vc_call_vol_steps=14
ro.config.media_vol_steps=30
audio.safemedia.bypass=true
Click to expand...
Click to collapse
thank you man! to add or edit stuff in your module i can simply edit the system.prop file in your mod?
Also , i see you use "ro.qc.sdk.audio.fluencetype=fluencepro" while oher mod use "ro.vendor.audio.sdk.fluencetype=fluencepro", both valua are correct or other mod mistake this value?
riccetto80 said:
thank you man! to add or edit stuff in your module i can simply edit the system.prop file in your mod?
Also , i see you use "ro.qc.sdk.audio.fluencetype=fluencepro" while oher mod use "ro.vendor.audio.sdk.fluencetype=fluencepro", both valua are correct or other mod mistake this value?
Click to expand...
Click to collapse
Yes, you can edit system.prop to modify the values and reinstall the module to apply them. I used to be able to modify system.prop of already installed module in /magisk/module_name/system.prop file directly, but it stopped working for me - file doesn't get saved (not sure if related to Oreo).
"ro.qc.sdk.audio.fluencetype=fluencepro" was required in Nougat. In Oreo, the default value is indeed "ro.vendor.audio.sdk.fluencetype=none". However audio recording is fine as far as I can tell, so it either has been fixed by Xiaomi or "ro.qc.sdk.audio.fluencetype=fluencepro" is still working. Will check when I have more time for testing
Edit:I can't hear any difference between stock "ro.vendor.audio.sdk.fluencetype=none"; "ro.vendor.audio.sdk.fluencetype=fluencepro" and "ro.qc.sdk.audio.fluencetype=fluencepro". My guess would be that it has been fixed by Xiaomi in the January(?) Oreo update. Can anyone else confirm?
A question - if I have the EIS and HAL3 already activated as I have the Gcam previously installed I don't need to deactivate them in your module? Just install the module? What I want is the voice recorder. Or, shall I put to zero ("0") these values: persist.camera.eis.enable=1
persist.camera.HAL3.enabled=1
laotzy said:
A question - if I have the EIS and HAL3 already activated as I have the Gcam previously installed I don't need to deactivate them in your module? Just install the module? What I want is the voice recorder. Or, shall I put to zero ("0") these values: persist.camera.eis.enable=1
persist.camera.HAL3.enabled=1
Click to expand...
Click to collapse
You can keep them (Magisk merges build.prop changes from all modules), remove repeating lines or add comment sign "#" at the beginning of the line which you want to skip. The easiest way is to use module as it is, it should work without any issues..
Hello guys, anyone tried the Systemless Xposed for Oreo?
spithash said:
Hello guys, anyone tried the Systemless Xposed for Oreo?
Click to expand...
Click to collapse
Yes, many of us. It's working fine, but will break Safetynet.
These modules help me a lot everyday.
joeyhuab said:
These modules help me a lot everyday.
Click to expand...
Click to collapse
Pls Give link of Andromeda Enabler and all modules related with nav bar
sauru.660 said:
Pls Give link of Andromeda Enabler and all modules related with nav bar
Click to expand...
Click to collapse
Andromeda enabler: https://drive.google.com/open?id=1SwIza1UYLQrn0c6b0gS9zEV7p48YefKh
Soft keys only: https://drive.google.com/open?id=1kOrqcZRki8ZhEeGy8_AC515uXq6qjBkr
Navbar: https://drive.google.com/open?id=1mv1XkT_ElubR-hBUpXC2cmF7mYbplEXs
Enjoy.
joeyhuab said:
These modules help me a lot everyday.
Click to expand...
Click to collapse
Are you on Oreo or Nougat? If on Oreo, have you installed the latest update?
1. Get TWRP (Follow this guide: https://forum.xda-developers.com/t/proper-way-of-installing-twrp.4325927/)
2. Flash the vbmeta provided in the above thread
3. In TWRP, run the no verity patcher.
4. Get any A/B gsi ROM (Treble check lists wrong information)
5. Download the ChonDoe patcher
6. Rename ROM to System.img and put it on the internal storage in the same location as Chondoe patcher.
7. Run the patcher and ignore any fstab errors.
8. Success?
KNOWN BUGS: Touch isn't working after screen lock, reboot needed. Should be OK if you don't turn your screen off.
Enjoy!
There is no need for the chondoe patcher. And finaly i'm not the only one who getts does screen touch issues on gsi roms.
I don't know why you complicated it this much to install a gsi rom, it is:
1. boot in to twrp
2. wipe data, cache, dalvik
3. reboot to twrp
4. install gsi rom and reboot
and make sure dm-verify is allredy disabled.
The touch screen error is not solved if I lock and unlock the cell phone several times?
LAST_krypton said:
I don't know why you complicated it this much to install a gsi rom, it is:
1. boot in to twrp
2. wipe data, cache, dalvik
3. reboot to twrp
4. install gsi rom and reboot
and make sure dm-verify is allredy disabled.
Click to expand...
Click to collapse
How to disable dm-verity? I plan to try to install twrp to see if it works and try miui
BryanCp13 said:
How to disable dm-verity? I plan to try to install twrp to see if it works and try miui
Click to expand...
Click to collapse
You flash this file, then you format data. DO NOT rename the file.
LAST_krypton said:
There is no need for the chondoe patcher. And finaly i'm not the only one who getts does screen touch issues on gsi roms.
Click to expand...
Click to collapse
The error sucks, as anything else works great. I'll let you know if i get it fixed.
Will it be deep sleep related problem as the phone has no problems until you turned off the screen and on again?
If that is the case, using wakelock app with the CPU option enabled (which disables deep sleep) and wakelock settings> autostart on boot enabled, should make the device run fine.
However it increases idle battery drain by some extent, you have been informed about that.
Link is here.
Wakelock Revamp - PowerManager APK 3.4.0 for Android – Download Wakelock Revamp - PowerManager APK Latest Version from APKFab.com
Wakelock Revamp - PowerManager 3.4.0 latest version APK Download by darken for Android free online at APKFab.com. Easy control over Android's PowerManager.
www.google.com
LR7875 said:
Will it be deep sleep related problem as the phone has no problems until you turned off the screen and on again?
If that is the case, using wakelock app with the CPU option enabled (which disables deep sleep) and wakelock settings> autostart on boot enabled, should make the device run fine.
However it increases idle battery drain by some extent, you have been informed about that.
Link is here.
Wakelock Revamp - PowerManager APK 3.4.0 for Android – Download Wakelock Revamp - PowerManager APK Latest Version from APKFab.com
Wakelock Revamp - PowerManager 3.4.0 latest version APK Download by darken for Android free online at APKFab.com. Easy control over Android's PowerManager.
www.google.com
Click to expand...
Click to collapse
I'll try and tell you how it went. Thanks!
LR7875 said:
Will it be deep sleep related problem as the phone has no problems until you turned off the screen and on again?
If that is the case, using wakelock app with the CPU option enabled (which disables deep sleep) and wakelock settings> autostart on boot enabled, should make the device run fine.
However it increases idle battery drain by some extent, you have been informed about that.
Link is here.
Wakelock Revamp - PowerManager APK 3.4.0 for Android – Download Wakelock Revamp - PowerManager APK Latest Version from APKFab.com
Wakelock Revamp - PowerManager 3.4.0 latest version APK Download by darken for Android free online at APKFab.com. Easy control over Android's PowerManager.
www.google.com
Click to expand...
Click to collapse
Still happens, really weird
James 144 said:
Still happens, really weird
Click to expand...
Click to collapse
Well the touch screen works well until you turn the screen off and on?
What GSI do you use? Phh treble? Maybe erfangsi will work, but we don't know.
LR7875 said:
Well the touch screen works well until you turn the screen off and on?
What GSI do you use? Phh treble? Maybe erfangsi will work, but we don't know.
Click to expand...
Click to collapse
Phh Lineage 18.1. Doesn't work on normal phh treble either
I'll try erfangsi.
James 144 said:
Phh Lineage 18.1. Doesn't work on normal phh treble either
I'll try erfangsi.
Click to expand...
Click to collapse
All processes and services are running normal it is that the screen woun't recognize touch. By flashing a custom kernel and disabeling power saveing options could fix the problem.
James 144 said:
You flash this file, then you format data. DO NOT rename the file.
Click to expand...
Click to collapse
Will that remove the mount error when flashing the gsi?
LAST_krypton said:
All processes and services are running normal it is that the screen woun't recognize touch. By flashing a custom kernel and disabeling power saveing options could fix the problem.
Click to expand...
Click to collapse
Do I have to install yes or yes a kernel for that rom? (I am not Rot) since in another rom gsi it gave me mount error and permissions denied
BryanCp13 said:
Will that remove the mount error when flashing the gsi?
Click to expand...
Click to collapse
Yes.
LAST_krypton said:
All processes and services are running normal it is that the screen woun't recognize touch. By flashing a custom kernel and disabeling power saveing options could fix the problem.
Click to expand...
Click to collapse
I've found a telegram group where the rom creator is really active and willing to help. I already tried to solve it but I'm busy. Here's the link: Device name? GSI version? - #phh-treble https://t.me/phhtreble/283195 <---. Tell them that Kuba invited you and they should know that they should help with the touch screen. Rom creator said that it's 100% fixable.
what treble type is a12 has?
Jayke770 said:
what treble type is a12 has?
Click to expand...
Click to collapse
A/B. Some apps say A only but that is wrong