This is all guide with bug fixing on minicm7 2.1.X
Screen Cut:
Only in CWM/CWR
NMEAListener:
I think NMEAListener is GPS
I found that gps.conf is europe settings
since that i have no problem with it
for non-europe residence Here Patch
Compass:
Wait till nAa fix
Video Recording Lag:
did you experience this
use this file Download
Auto Brightness:
use this tutorial
Code:
1. disable auto brightness first in display
2. go to cm settings --> display --> automatic backlight --> choose use custom and allow light decrease
3. tick edit other level
4. set number of levels to 13
5. look at this pic [URL="http://attachments.xda-developers.com/attachment.php?attachmentid=874309&stc=1&d=1327627892"]Here[/URL] And [URL="http://attachments.xda-developers.com/attachment.php?attachmentid=874311&stc=1&d=1327627892"]Here[/URL]
6. enable auto brightness in settings (not cm)
7. restart
8. enjoy
Android market app won't show up:
clear data on app settings
Just use recommended tweak:
Non-Recommended tweak make ur phone less stable
Recommended:
SuperCharger
Ram Manager / PRO
Juwe Ram's script
Etc...
Non-Recommended
Build.prop tweak
init.d tweak
IPV4/IPV6
Etc...
End of first post continued in 2nd post
Guide for Minicm7
Notice ADW launcher Lag use this settings:
Code:
1) Screen Preferences - Desktop scrolling speed - set to something low-ish like 150-200, default settings are just plain moronic here. Desktop overshoot should be fine at 30 or 40.
2) Drawer Settings - Horizontal Drawer definite on (this is far superior to the scrolling drawer if you have more than a few apps, and feels much smoother).
3) Drawer Settings - Zoom effect speed - 400 is a decent setting, default was way too high.
4) Drawer Settings - Columns/Rows - 4x4 is a nice setting for portrait, if you don't like a crammed screen.
5) System Preferences - Wallpaper Hack - check this. If you have issues, change wallpapers to something of a sane size.
6) System Preferences - Use Screen Cache - check this.
7) System Preferences - Scrollable Widget support - you should start with this unchecked. Only check it if you have issues with some
Make ur phone fast without tweaks?
here my perfomance settings
Go to CyanogenMod Settings --> perfomance settings
Code:
1.) Set compcache ram usage to 18%
2.) Enable use jit
3.) Disable Surface Dithering (optional)
4.) Enable 16bit transparency
5.) Enable Allow purging of assets
6.) VM heap size 48mb
7.)
SDcard cache size 1024kb Class 1,2
SDcard cache size 2048kb Class 3,4
SDcard cache size 3072kb Class 4,5,6,7,8
SDcard cache size 4096kb Class 9,10
Go to CyanogenMod Settings --> perfomance settings --> cpu settings
Code:
1.) Available gorvernor set to smartassV2
2.) Min Cpu frequency 245mhz
3.) Max Cpu frequency 691mhz+ (optional)
4.) Set on Boot
Make minicm7 more battery save?
here my battery save settings
Note: this settings overwrite "Make ur phone fast without tweaks"
Go to CyanogenMod Settings --> perfomance settings --> cpu settings
Code:
1.) Available gorvernor set to smartassV2
2.) Min Cpu frequency 19mhz
3.) Undervolt
4.) Set on Boot
final step: Delete Unused App
Extra Section
Coming Soon
End Of My Post
LtHuNTer_StepheN said:
Don't use any tweaks:
tweaks make your phone fast but less stable
and don't use xloud and mobile bravia
they are fake
Click to expand...
Click to collapse
+1 10char..
I agree with other settings, but would you mind explaining why VM heap size is 48? I've read that 32 is better in the FAQ thread of minicm7, and 2048 sd cache cause hiccups while playing music in lower class sd cards, if you can, try to edit some things for lower class cards and higher class cards, for lower class cards 128 sd cache is better and doesnt cause hiccups, just a suggestion . On the other hand, I will try your CPU settings, the smartass v2 settings with min 248mhz and 691mhz, 691mhz is indeed the most stable for nAa kernel. BTW I use tweaks without any stability issues, supercharger v8 and sometimes ram manager pro.
This is the thread that I have read:
forum.xda-developers.com/showthread.php?p=17648469
hixvolnutt said:
I agree with other settings, but would you mind explaining why VM heap size is 48? I've read that 32 is better in the FAQ thread of minicm7, and 2048 sd cache cause hiccups while playing music in lower class sd cards, if you can, try to edit some things for lower class cards and higher class cards, for lower class cards 128 sd cache is better and doesnt cause hiccups, just a suggestion . On the other hand, I will try your CPU settings, the smartass v2 settings with min 248mhz and 691mhz, 691mhz is indeed the most stable for nAa kernel. BTW I use tweaks without any stability issues, supercharger v8 and sometimes ram manager pro.
This is the thread that I have read:
forum.xda-developers.com/showthread.php?p=17648469
Click to expand...
Click to collapse
For Perfomance it's better set 48mb
this help app memory management
this heap size is usefull for HD games
Oh i forgot
i will edit it
for that tweak is already tested
what i say is
Code:
build.prop tweak
mobile bravia engine
and useless tweak
for that tweak it may increase stability
i will edit so people understand
Post Updated
Thanks
Is there any way to fix compass?the compass is somehow inverse
for auto brightness setting, how many level are you using? Ultra brightness enable or not?
Sorry, but screen cutting still exist even with bootanim enabled..especialy when in recovery..
Btw nice thread...^^v
Sent from my E15i using Tapatalk
Post Updated
LtHuNTer_StepheN said:
Post Updated
Click to expand...
Click to collapse
Oops, i'm still using nAa 08...maybe because of that...0_x
Sent from my E15i using Tapatalk
bayumahendra24 said:
Sorry, but screen cutting still exist even with bootanim enabled..especialy when in recovery..
Btw nice thread...^^v
Sent from my E15i using Tapatalk
Click to expand...
Click to collapse
i think screen cut happen with smartass v2
D E V I L said:
i think screen cut happen with smartass v2
Click to expand...
Click to collapse
Flash the new nAa-08b kerner. This fix the problem
Hi!! I have just one question. The tethering wifi always disconnects when screen turns off. I tried wi-fi settings, advanced, never sleep but does not work. Do you have other solutions? Thanks
still score highly!!!
plus avent updated kernel and rarely get screen cuts!!
so id say great rom plus kernel!!
flegga92 said:
Flash the new nAa-08b kerner. This fix the problem
Click to expand...
Click to collapse
Still using nAa 08 (havent change kernel because what i see on the changelog, the difference between nAa 08 and 08b only the screen cuts fix) with:
- Cpu freq 19-600mhz
- smartassv2 on
- undervolt on
- bootanimation enabled
No more screen cuts since my prev post.
Screen cuts SOMETIMES only appear when i'm in cwm req...thats good enough for me..
For the video lag fix,does it work with other rom which have the same problem?flash with xrec or cwm?
Hello to everyone and excuse me if my question is probably going to be dumb (for sure it's an OT so please forgive me about that) but I'm quite clueless about the issue I'm experiencing and I hope to find an advice here.
I own and X10 mini with MiniCM 2.1.6 and 2.6.29.6-nAa-08 kernel. Everyhing's fine, really a great piece of work that has put new life into my beloved X10 Mini but I'm experiencing the 'screen cut' issue that's discussed here too: it happens only with some apps (Labyrinth for example) but it happens and I'd like to get rid of this.
I don't know if it could be an issue related to the apps not being designed for Gingerbread but I don't think so because I expect something different should this be the case.
I've read that the kernel nAa-08b is intended to solve this issue but it seems (maybe I'm wrong) that it isn't suitable for my X10 mini (I've made some digging around and the latest kernel version for my mini seems the one that I've already installed while the 08b seems to be intended for the X8). I'm sure that the reply is already around here but I couldn't succeed in finding it though I've read a lot (really a lot!) of posts here and there, especially on the official thread:
http://forum.xda-developers.com/showthread.php?t=1068553
where unfortunately I couldn't post because I'm a new member with less than ten posts. Some advices? Thanks anyway!
very good guide
thanks you very mach!
post updated
sorry im busy lately
I need maximum battery time. So what is the best kernel for this and it´s configuration? I don´t need answers like "search for it" . Go hell those stupid guys.
voidvader said:
I need maximum battery time. So what is the best kernel for this and it´s configuration? I don´t need answers like "search for it" . Go hell those stupid guys.
Click to expand...
Click to collapse
there is no such thing as perfect kernel or perfect configuration,
the factors that can determine the amount of battery usage depends heavily on the nature of the usage under the user itself,
most kernels with undervolt support and underclocking will do fine,
i'd suggest you try out tweaks and preferences yourself since no one can guarantee you an exact time frame,
but i'll give you mine,
ROM: WP8 Monochromatic 5.1
Kernel: Built-in rom (savie's)
Tweaks: Built-in rom
Scaling freq: 156min 624max
CPU Governor: ondemandx
reduced all bloatwares even gmail and maps,
Battery Time (heavy usage): 4hrs max (medium usage): 1-1.5 day max (minimal usage) 2-3days max
that's just about it,
please take the time to conduct a research on what is your best prefered battery saving method,
don't call anyone stupid,
it's bad and potato disapproves
Rom doesnt matter really if you manage the applications well.
Use kuros kernel + kuros tweaks. Thats the best battery saving combo Ive tried.
For governor, use ondemand, the most battery efficient governor and use deadline for i/o
deathnotice01 said:
there is no such thing as perfect kernel or perfect configuration,
the factors that can determine the amount of battery usage depends heavily on the nature of the usage under the user itself,
Click to expand...
Click to collapse
Not really. Change between Merruk #206 and kuros latest, you can really notice the battery drain difference. Its battery efficient than stock kernel in my tests.
Here u go:
Before all id reccomend updating the software to the latest version xD
Use the latest white kernel
Use v6 supercharger and some other tweaks
Reduce the screen brightness
Lower the system volume in the sounds options
Disable animation
Disable auto-sync
Disable backup settings
Disable roaming ^^,wifi,mobile internet,bluetooth when you dont use it(gps even if turned on allways is only actually active when theres a open app that uses gps ^^)
Disabling more sound effects will make it ugly and not cool lol,so do as u wish with thease:
Keyboard sounds
Lock screen sounds and vibration
set a boot frequency in set cpu like:
312-832,conservative,sio
Set up proper profiles in set cpu like
Screen off
312-312,powersave,noop
Charging
312-832,ondemand,sio
Battery 50 F
312-832, conservative,noop
Battery <16
312-832, conservative, noop
here just take my setcpu profiles, i made it in setcpu 3.07 just put it in the root of your sdcard and in setcpu enable profiles and click on restore profiles and click on that
http://www.mediafire.com/?ru786ho4o9i7jdp
Here are some build.prop tweaks
ro.ril.power.collapse=0
ro.ril.disable.power.collapse=0
dalvik.vm.heapstartsize=4
dalvik.vm.startheapsize=4
this one is alredy in v6 supercharger ;P
pm.sleepmode=1
remove some useless apps that u dont use but their allways running in the background(yeah remove anything u will never use)
Google maps
email(not gmail)
software update
and buying a new, better battery isnt a bad idea too ? is it (obviously xD)
I hope i Helped, this and some of my other build.prop tweaks made my battery go like lol xD it was lasting so long idk how much was it
Thank you all! Thanks so much guys!:good:
Filip98 said:
Here are some build.prop tweaks
ro.ril.power.collapse=0
ro.ril.disable.power.collapse=0
dalvik.vm.heapstartsize=4
dalvik.vm.startheapsize=4
this one is alredy in v6 supercharger ;P
pm.sleepmode=1
I hope i Helped, this and some of my other build.prop tweaks made my battery go like lol xD it was lasting so long idk how much was it
Click to expand...
Click to collapse
the correct one is "dalvik.vm.heapstartsize". dalvik.vm.startheapsize is not exist. nevertheless, this script only work for ICS. GB based rom doesnt have these prop. please be carefull with any prop for virtual memory like this one. if you clean your dalvik-cache you might ended up in bootloop.
Lots of information.
Thanks guys.
Sent from my GT-S5360 using xda premium
Custom kernel for Samsung Galaxy S Advance
Code:
/*
* Your (probably expired) warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Features:
Universal kernel for JB, KK, LP and MM-based ROMs
CPU, GPU and DDR OC support
more governors and I/O schedulers
Lite kernel - some kernel features moved as modules
F2FS support
ABB-charger tweaks
many others features and tweaks...
Credits:
@dh.harald and @hafidzduddin for contribution on U8500 platform sources
@ Team Canjica for a base for this kernel
@ Nova Fusion for F2FS implementation
@zwliew for contribution on TC kernel
@cocafe for LiveOPP, GPU OC, abbamp and abb-charger tweaks and many cool patches which I've used from his kernel
@faux123 for dynamic Fsync implementation
@Christopher83 for dynamic management of dirty page writebacks implementation
@KINGbabasula for contribution on TC kernel sources
@boype for SIOPlus tweaks and OndemandPlus governor
@Adi_Pat for abbamp, kernel tweaks
@PolishVodka for initramfs scripts for 4.2.x and 5.0.x
@Rox for help in fixing initramfs scripts for 4.1.2
@ace2nutzer for optimization CPU OC and for whatever scripts which I have used in my kernel
@Meticulus for BLN, Sweep2wake and Doubletap2wake
@mkaluza for huge LiveOPP/Mali improvements and Dynamic governor
@yanpol199 for help with F2FS support in TWRP
@ all users who tests this kernel and directs the development along the right path
@ all those users, who I forgot to mention (PM me if so)
Team Win for TWRP recovery
Samsung for opening kernel source
Linus Torvalds for Linux sources
Special Thanks:
@isaak, @enkflr, @Pdevo, @prometej-zg for donating this phone!
[*]@S.AMU for providing FTP-Server
Source Code:
LK 3.10.y based releases
r5.7.x (LK 3.4.y based releases)
Installation:
Flash temporary kernel (if coming from other recoveries than TWRP 3.1.1)
Reboot recovery
Flash kernel zip
Compatibility:
I only add those ROMs that are confirmed to work by me or someone else:
Stock 4.1.2 ROM
LineageOS 11
CyanogenMod 13
Notice: this kernel is not compatible with NovathorSettings app, be sure to remove it before installing a kernel!
Download:
FTP
XDA:DevDB Information
Chrono Kernel, Kernel for the Samsung Galaxy S Advance I9070
Contributors
ChronoMonochrome, cocafe, faux123, zwliew, mkaluza, Meticulus, KINGbabasula, ace2nutzer, TeamCanjica
Source Code: https://github.com/ChronoMonochrome/Chrono_Kernel-1/commits/master
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R5.7.1
Stable Release Date: 1974-11-11
Beta Release Date: 1974-11-11
Created 2018-03-09
Last Updated 2018-04-16
Changelogs and features
Changelog
R5.9.1
Resolved (hopefully) deepsleep issues *
Fixed touchkey not working issue **
* tested in about 24 hours so far with ~6 hours of deep sleep on UltimateROM 6.0.1 without any issues with wakelocks.
** It seems that in r5.9 was introduced a bug - touch keys weren't working (at least, on 6.0.1) after device wake up.
R5.9
Bring up all the latest CK code from Codina kernel
Fix a severe performance issue on r5.8.2 build
BLN is finally FIXED! *
* Apparently, issues with BLN were related to Janice touchkey driver that was putting the device to sleep (when the display is off) regardless of a BLN wakelock usage. Reverting this behavior seemed to enable BLN to work.
R5.8.2
In-kernel vibrator fix for Android 6.0+
R5.8.1
PowerHAL fixes for 4.4.4
Experimental fix for CPU governor issue on 4.4.4
LCDCLK: revert to TeamCanjica kernel implementation
R5.8
Memory management hugely improved (finally LMK works properly)
Fixed powersave interface on JB 4.1.2 stock
Experimental fixes to PowerHAL on 4.4.4
LiveOPP: merged changes from refresh kernel (removed some CPU freq steps)
Dynamic: adjust tunables (same like in refresh kernel)
Possible vibrator fix on 6.0+ (not tested)
(old changelog)
R5.7.1
Initial build for janice (kernel sources based on LineageOS 15.1 kernel for Codina)
Fixed bluetooth issue on 4.1.2
Squash-reverted GPU-related code logic from CPU governor Dynamic
J4FS module code cleanup
Reverted forcing minimum CPU freq to 800 MHz
Enabled CONFIG_CPUSETS (required by Android 6.0.x+ ROMs to function properly)
Kernel Tweaks:
(GPU/CPU undervolting and related tweaks)
Undervolting the CPU/GPU will bring battery savings but possible instability.
1) to undervolt CPU use ChronoKernel app or via init.d scripts:
Code:
echo *cpufreq* varm=xx > /sys/kernel/liveopp/arm_summary
for example, following sets voltage varm=0x10 for 200 MHz:
Code:
echo 200000 varm=0x10 > /sys/kernel/liveopp/arm_summary
or
Code:
echo 200000 varm-=10 > /sys/kernel/liveopp/arm_summary
(default varm voltage for 200 MHz is 0x1a but, code above sets 0x1a - 0xa(10) = 0x10 )
2) to undervolt GPU use init.d script:
Code:
echo x vape=yy > /sys/kernel/mali/mali_dvfs_config
Example:
Code:
echo 2 vape=0x1c > /sys/kernel/mali/mali_dvfs_config
"2" stands for DVFS idx (look at mali_boost_high/mali_boost_low).
To prevent overriding of such settings by ChronoKernel app, add line to your init.d script after GPU undervolting
Code:
chmod 444 /sys/kernel/mali/mali_dvfs_config
Don't change voltage of both GPU/CPU at the same time - otherwise if you'll get reboot if won't know what it caused. The same is for different frequencies - if you'll change voltage of too many steps you won't know which frequency caused reboot. It's not easy process, though, following method simplifies it: https://github.com/mkaluza/i9070_kernel_CoCore-E/wiki/Undervolting-janice .
3) Custom LiveOPP table.
By default some LiveOPP steps such as 100, 200, 500 ... MHz aren't used. You can re-enable those by following way:
Code:
echo 200000 enable=1 > /sys/kernel/liveopp/arm_summary
Or use CK app instead. Don't enable it unless it uses the same voltage as 400 MHz. The same is for the rest frequencies - until some of them uses same voltage, no point to enable steps with lower freq. I've added 100 MHz just to further make some tests with it once again. It can't use lower varm than 200 MHz - that's why it's disabled by default. Furthermore, not all phones well keep undervoltage, that's why 100-400 MHz steps uses same stock voltage varm=0x1a.
UPD. thanks to @borkins for this nice editor LiveOPP ARM steps: http://forum.xda-developers.com/showpost.php?p=60311291&postcount=2921
(CPU freq management tweaks)
CPU freq. limiter for screen OFF, adjust it via:
Code:
SYSFS=/sys/kernel/cpufreq/cpufreq_limits_on_suspend
echo min=100000 > $SYSFS
echo max=400000 > $SYSFS
echo on > $SYSFS
Too low frequency may cause freezes after wakeup and sound scrathes. If you use Dynamic govermor, it make no sense to use cpufreq limiter, because Dynamic already takes care about CPUfreq usage optimization. For more, read wiki.
Input boost
This feature has been originally written by zwliew.
Not all governors support input boost. Supported governors: ondemand, interactive, conservative, ZenX, lionheart and some others. Dynamic governor has its own boost interface.
Default boost frequency is 400 MHz.
Code:
echo 450000 > /sys/kernel/cpufreq/input_boost_freq # echo '0' to disable
echo 35 /sys/kernel/cpufreq/input_boost_ms
(BackLight Notification)
To configure time intervals of BLN blinking type(bln_ondelay stands for time of blink and bln_offdelay - delay between two blinks):
Code:
echo bln_ondelay=500 > /sys/kernel/bln/blink_mode
echo bln_offdelay=6000 > /sys/kernel/bln/blink_mode
Make sure BLN enabled:
Code:
echo 1 > /sys/class/misc/backlightnotification/enabled
# to enable bln_wakelock.
echo on > /sys/kernel/bln/bln_wakelock
Use /sys/devices/virtual/misc/backlightnotification/blink_mode to changes modes.
Blink modes:
0 = no blinking
1 = blink backlight only
2 = blink backlight + rear cam flash
3 = blink rear cam flash only
(Module autoload)
Now there is a simple way to load modules at boot. Just move needed modules to /system/lib/modules/autoload and reboot device(or execute /etc/init.d/00autoload)
(DDR overclock)
This feature has been developed by me and allows you to improve DDR and GPU performance. Please note, that DDR OC might work unstable and cause filesystem corruption. Though, DDR clock of 975 MHz has been highly tested and should work fairly stable on most devices.
Overclocking DDR over 975 MHz is highly NOT recommended, especially in case if you not sure that you can deal with possible consequences.
How to OC DDR:
1) by using
this script .
2) by using Terminal Emulator(in example below 975 MHz):
Code:
echo 0x5017f > /sys/kernel/liveopp/pllddr_oc_on_suspend
This setting will be applied right after disabling screen.
(Minimum APE/DDR OPP on screen on)
This feature has been developed by me and allows to set minimum APE/DDR OPP states which are used when screen is ON. APE controls many systems such as an image, video, audio system etc. DDR OPP determines performance of DDR. Default values are APE50 and DDR50. Lower states(APE25/DDR25) reduces power consumption, but may cause graphical glitches like screen blinking or filling it by vertical grey lines. If you don't have mentioned effects, it's recommended to use APE25/DDR25:
Code:
echo ddropp=25 > /sys/devices/pri_lcd_ws2401.0/mcde_screenon_opp
echo apeopp=25 > /sys/devices/pri_lcd_ws2401.0/mcde_screenon_opp
* if you don't have folder /sys/devices/pri_lcd_ws2401.0, use /sys/devices/pri_lcd_s6d27a1 instead.
(Screen refresh rate)
This feature has been developed by cocafe and modified by me. Lower lcdclk frequency cause less power usage, but too low values makes system unusable.
Following command allows to change screen refresh rate:
Code:
echo x > /sys/kernel/mcde/lcdclk
use
Code:
cat /sys/kernel/mcde/lcdclk
to see supported lcdclk modes. Default mode is 60 Hz which is recommended in most typical cases. If you've screen tearings, blinking etc. change resresh rate mode to "60+ Hz":
Code:
echo 0 > /sys/kernel/mcde/lcdclk
(ABB charger tweaks)
added tweakable interfaces for termination current. To adjust it type(just an example):
Code:
echo 90 > /sys/kernel/abb-chargalg/termination_curr_1st
echo 70 > /sys/kernel/abb-chargalg/termination_curr_2nd
curr_2nd should be less or same as curr_1st. Lower values prolongs battery lifetime, but also slows battery charging.
Default values are curr_1st == curr_2nd == 150 mA. Please note, too low values maybe aren't usable.
(Dynamic FSync)
This feature has been developed by Faux123 and allows to dynamically manage the synchronous writes performed on file system (FSync).
It uses asynchronous writes when the screen is on, instead of synchronous writes, to have better performance and a slightly lower battery drain, while when the screen is off the synchronous writes are re-enabled to flush all the outstanding writes and prevent possible data loss.
How to enable/disable the Dynamic FSync (default enabled):
1) By downloading and using Trickster MOD
2) By directly editing the file /sys/kernel/dyn_fsync/Dyn_fsync_active and setting 1 to enable the dynamic fsync, 0 to disable it (note that set value will be lost after a reboot/shutdown)
3) By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run this command to disable the dynamic fsync feature
Code:
su
echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active
- Or run this command to re-enable the dynamic fsync feature
Code:
su
echo 1 > /sys/kernel/dyn_fsync/Dyn_fsync_active
Click to expand...
Click to collapse
(Software CRCs)
Disabling software CRCs gives you a slight bump(10-30% is what they say) of MMC performance, at the cost of a possibility of your Ace 2 freezing randomly.
Code:
echo 0 > /sys/module/mmc_core/parameters/use_spi_crc
Click to expand...
Click to collapse
(Dynamic dirty page writebacks)
This feature has been developed by Christopher83 and allows to dynamically manage the dirty page writebacks with two different intervals, one when the screen is on and another when the screen is off.
It is based on a commit of Francisco Franco, but instead of using hard coded values and of disabling at all the dirty page writebacks while the screen is on (possibility of data loss).
By using a higher interval we have better performance and less battery consumption, with a very low risk of data loss.
How to customize the dynamic dirty page writebacks feature (default disabled):
Three new procfs parameters are exposed inside /proc/sys/vm path:
- dynamic_dirty_writeback is the activation status of this feature, set 1 to enable it, set 0 to disable it and use the standard behaviour
- dirty_writeback_active_centisecs is the interval for the dirty page writebacks when the system is active (screen on), the default value is 1500 centisecs (15 seconds)
- dirty_writeback_suspend_centisecs is the interval for the dirty page writebacks when the system is suspended (screen off), the default value is 500 centisecs (5 seconds)
1) By directly editing one of the file written above inside /proc/sys/vm and setting the preferred value (note that set value will be lost after a reboot/shutdown)
2) By using Terminal Emulator (note that set value will be lost after a reboot/shutdown)
- Open Terminal Emulator
- Run this command to disable the dynamic dirty page writebacks feature
Code:
echo 0 > /proc/sys/vm/dynamic_dirty_writeback
- Or run this command to re-enable the dynamic dirty page writebacks feature
Code:
echo 1 > /proc/sys/vm/dynamic_dirty_writeback
- Run this command to set customize the two intervals (30 seconds while the screen is on, 10 seconds when the screen is off)
Code:
echo "3000" > /proc/sys/vm/dirty_writeback_active_centisecs
echo "1000" > /proc/sys/vm/dirty_writeback_suspend_centisecs
(Tweak app)
ChronoKernel settings
Thanks mars_army for this app!
Bug reports:
after experiencing a random reboot, type in terminal:
Code:
su
cat /proc/last_kmsg > /storage/sdcard0/last_kmsg.txt
report it in the thread and attach the last_kmsg.txt
Misc
Storages switch
By default, this kernel comes with internal and external storages switched. You can revert this behavior, by changing the line
Code:
use_swap=1
to
Code:
use_swap=0
in file /ramdisk/fstab_specs.txt and flashing the kernel package. This setting will remain until you format /ramdisk partition.
@ChronoMonochrome
I tested "chrono_kernel_r5.7.1-test-40-g169a68f4f29d-janice.zip" on Lineage OS 11.
Result: I have the same hiccups in the youtube video like before.
I think that you can revert the LCDCLK frequency to the default 60 Hz value, because I didn't notice any significant difference.
And I had an isolated crash while I was navigating in settings.
My usual running apps & services are: Should I answer?, Nova Launcher, Tesla Unread, Google Play Services 11.9.75, Ginger Keyboard, Skype 7.46.0.596 (old version from apkmirror), Quickpic, Terminal Emulator, CCleaner, Google Play Store 9.0.15, Tubemate 3.0.11, My Vodafone, Naked Browser, Titanium Backup, Fx File Explorer, Gmail, Google News & Weather, MX Player.
I hope that these logs can help you.
isaak said:
@ChronoMonochrome
I tested "chrono_kernel_r5.7.1-test-40-g169a68f4f29d-janice.zip".
Result: I have the same hiccups in the youtube video like before.
I think that you can revert the LCDCLK frequency to the default 60 Hz value, because I didn't notice any significant difference.
And I had an isolated crash while I was navigating in settings.
My usual running apps & services are: Should I answer?, Nova Launcher, Tesla Unread, Google Play Services 11.9.75, Ginger Keyboard, Skype 7.46.0.596 (old version from apkmirror), Quickpic, Terminal Emulator, CCleaner, Google Play Store 9.0.15, Tubemate 3.0.11, My Vodafone.
I hope that these logs can help you.
Click to expand...
Click to collapse
Thanks for the report! Unfortunately, the last_kmsg log appears to be taken from MaxiCM kernel, so the crash isn't captured here. In the meantime I'll install some of those apps to test how it goes under increased memory pressure. Was /proc/meminfo log taken before or after reboot? It would be useful to check this sysfs interface when the phone is encountering laggs (if it does), but after reboot this info won't help. About lowmemorykiller changes: were apps running faster / slower? So far Youtube playback is the only issue or phone laggs too?
ChronoMonochrome said:
Thanks for the report! Unfortunately, the last_kmsg log appears to be taken from MaxiCM kernel, so the crash isn't captured here. In the meantime I'll install some of those apps to test how it goes under increased memory pressure. Was /proc/meminfo log taken before or after reboot? It would be useful to check this sysfs interface when the phone is encountering laggs (if it does), but after reboot this info won't help. About lowmemorykiller changes: were apps running faster / slower? So far Youtube playback is the only issue or phone laggs too?
Click to expand...
Click to collapse
/proc/meminfo log was taken before the reboot. Youtube playback is not the only issue. I can just say that the best way to reproduce a crash or a slowdown is switching from an app to another as quick as possible and/or try a cleaning with CCleaner. Ah, in that list I forgot some apps, so I've updated my previous post.
So far I've tested as much as possible on stock 4.1.2 rom and everything is working fine.
-Bluetooth is definitely fixed, working like a charm.
-CRC, FSYNC and other tweaks give me no issue at all and work good.
-Tested a bit of undervolting, firstly cpu, then gpu, and DDR OC, and here too, no problems.
-Really great the supension min and max cpufreq, tested it with some init.d scripts.
Overall stability and responsiveness of the system is impressive, really positive, you really made a big surprise
These instead are the few things I noticed not working, I think the first two are really not a major problem at all and maybe I am messing with something:
1. I have noticed that trying to set governor by init.d script doesn't seem to take effect and at boot completed I find performance setted as governor:
busybox echo dynamic > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor;
Click to expand...
Click to collapse
Running then the script manually set dynamic as governor correctly.
(SOLVED WITH A BUSYBOX CHMOD COMMAND BEFORE EVERY PARAMETER SET)
2. I tryed using exfat support, loaded fuse.ko and exfat.ko modules on boot, then used the same binary from cocafe twrp kernel I was using fine (and here I think there is the issue) with this command:
exfat-fuse /dev/block/mmcblk1p1 /storage/extSdCard;
Click to expand...
Click to collapse
Sdcard isn't recognized and android is asking to format it as usual.
3. I guess should be the number one: Recovery doesn't seem to work, tryed many times, also removing battery first, but I can't enter in recovery. Next time I flash kernel I will do it manually from terminal, or Universal Kernel Flash app
EDIT1:
I found that the path where lcd parameters are located would be:
/sys/kernel/s6e63m0/panel/lcd_clk
Click to expand...
Click to collapse
instead of:
/sys/kernel/mcde/lcdclk
Click to expand...
Click to collapse
EDIT2:
Seems like deepsleep is broken, because in my situation phone doesn't enter in deepsleep mode and having a look at /d/supsend_stats and d/suspend directory confirm my issue.
I found at first strange the absence of /d/cpuidle directory and so the deepest_state configuration file, like something is missing here.
EDIT3:
I think I found another last issue, BLN is not working, but I think could be again something to do with files and folder structure, for example I can't find:
/sys/class/misc/backlightnotification/enabled
Click to expand...
Click to collapse
Again, this is still something not so important tough
EDIT4:
I was experiencing before issues with phone calls, making phone app freezing and signal loss, going to "no service" mode. Had to flash backup kernel for now, tomorrow as I get some time again I will provide logs
Pdevo said:
So far I've tested as much as possible on stock 4.1.2 rom and everything is working fine.
-Bluetooth is definitely fixed, working like a charm.
-CRC, FSYNC and other tweaks give me no issue at all and work good.
-Tested a bit of undervolting, firstly cpu, then gpu, and DDR OC, and here too, no problems.
-Really great the supension min and max cpufreq, tested it with some init.d scripts.
Overall stability and responsiveness of the system is impressive, really positive, you really made a big surprise
Click to expand...
Click to collapse
Thanks for a review!
2. I tryed using exfat support, loaded fuse.ko and exfat.ko modules on boot, then used the same binary from cocafe twrp kernel I was using fine (and here I think there is the issue) with this command:
Sdcard isn't recognized and android is asking to format it as usual.
Click to expand...
Click to collapse
Honestly I didn't test exfat for a long time. These issues might come due to the filesystem driver updates. Anyway I need to test things myself before I'll have clues on how to fix it.
3. I guess should be the number one: Recovery doesn't seem to work, tryed many times, also removing battery first, but I can't enter in recovery. Next time I flash kernel I will do it manually from terminal, or Universal Kernel Flash app
Click to expand...
Click to collapse
Are you sure you have followed the installation guide to flash the kernel? Especially, using TWRP is required to flash a kernel (other recoveries aren't tested and can be a cause for a bugs) I was returning to a stock for a short time to test if bluetooth works and recovery was working for me when I was returning to UltimateROM 6.0.1 afterwards.
Don't use manual flashing or UKF app to flash the kernel! The installation method is quite complicated (compared to installation of other kernels), so a full and proper installation is only possible if you flash it from recovery.
EDIT1:
I found that the path where lcd parameters are located would be:
instead of:
Click to expand...
Click to collapse
I have moved the interface to match the implementation of LCDCLK management on codina.
EDIT2:
Seems like deepsleep is broken, because in my situation phone doesn't enter in deepsleep mode and having a look at /d/supsend_stats and d/suspend directory confirm my issue.
I found at first strange the absence of /d/cpuidle directory and so the deepest_state configuration file, like something is missing here.
Click to expand...
Click to collapse
This is entirely possible due to deepsleep driver changes in a kernel. I never tested if it works on stock, I guess I'll have to return to stock once again.
EDIT3:
I think I found another last issue, BLN is not working, but I think could be again something to do with files and folder structure, for example I can't find:
Again, this is still something not so important tough
Click to expand...
Click to collapse
I was thinking BLN isn't working on this phone at all, so I disabled the kernel support. Is the stock ROM only where BLN works?
Yes sir, I flashed your kernel exactly from twrp, coming from cocore refresh24, I referred to UKF or terminal emulator to say I would use that method now that I can't enter recovery mode, but I never use these ways at all, always from recovery, because I know that kernel come with scripts and other files that without recovery wouldn't be installed
Tomorrow I will do further testing
ChronoMonochrome said:
I was thinking BLN isn't working on this phone at all, so I disabled the kernel support. Is the stock ROM only where BLN works?
Click to expand...
Click to collapse
As far as I know no dev on Janice introduced BLN, but I don't see any reason why it shouldn't be technically possible if it works on Ace II.
Please don't give up on this unless you're sure at 100%.
@cocafe had it on his todo list, but at the end he didn't implement it for unknown reasons. I asked to him but he never explained it.
ChronoMonochrome said:
I was thinking BLN isn't working on this phone at all, so I disabled the kernel support. Is the stock ROM only where BLN works?
Click to expand...
Click to collapse
Until now, BLN never been working or supported on custom and stock roms, as said by @isaak, the reason behing that I think is properly known by developers such as cocafe.
Yesterday I made a little try using the commands you point in the thread, a little go, but in fact is not working. Would be a cool feature, but nothing so important at all for me, at least for now
UPDATE:
I flashed again the kernel, starting from freshly downloaded zip, and I got an infinite bootloop trying to get to recovery, the only way to go back working was flashing stock rom with odin.
I can now safely say there is an issue with recovery using the stock rom.
UPDATE 19:30
I took two logs, one for incoming call and one for outgoing call, reproducing the issue I was referring in previous post.
In the first case, incoming call, notification appear but scrolling to accept call make phone unusable and I could just shutdown it to solve the situation.
In the second case, outgoing call, after I start the call the phone app isn't responding, I see the notification widget but tapping on every possible button, to terminate call or enter in dialog, doesn't work and phone is very unstable until a sort of a timeout is running out and call stop itself.
Hi @ everyone!
Because of th numerous issues found with the current release, I'm starting to work on a fresh kernel sources (3.0.101), almost from scratch. My primary focus for now will be a multitasking, that is the main issue with the current release. Because of yet unknown root cause of the issue it could take a while to reveal it, but I hope to release a new build these days (and after playing with some kernel configuration find out more appropriate one for a multitasking). Stay tuned!
For sure we stay tuned!, thank you so much for the efforts and take all the time you need Chrono
isaak said:
My usual running apps & services are: Should I answer?, Nova Launcher, Tesla Unread, Google Play Services 11.9.75, Ginger Keyboard, Skype 7.46.0.596 (old version from apkmirror), Quickpic, Terminal Emulator, CCleaner, Google Play Store 9.0.15, Tubemate 3.0.11, My Vodafone, Naked Browser, Titanium Backup, Fx File Explorer, Gmail, Google News & Weather, MX Player.
I hope that these logs can help you.
Click to expand...
Click to collapse
I have set up all these apps about 10-12 days ago. I should say, removing CCleaner seemed to help a lot to increase the phone performance. It's doing a lot of background CPU and I/O work, making the phone almost unusable on r5.7.1 and severely affects performance on r4.1 / r4.6.
ChronoMonochrome said:
I have set up all these apps about 10-12 days ago. I should say, removing CCleaner seemed to help a lot to increase the phone performance. It's doing a lot of background CPU and I/O work, making the phone almost unusable on r5.7.1 and severely affects performance on r4.1 / r4.6.
Click to expand...
Click to collapse
The new CCleaner version is on the heavy side, so I had to freeze some background services with My Android Tools app. Anyway I've just uninstalled it definitively.
New build r5.8 is up!
R5.8
Memory management hugely improved (finally LMK works properly)
Fixed powersave interface on JB 4.1.2 stock
Experimental fixes to PowerHAL on 4.4.4
LiveOPP: merged changes from refresh kernel (removed some CPU freq steps)
Dynamic: adjust tunables (same like in refresh kernel)
Possible vibrator fix on 6.0+ (not tested)
ChronoMonochrome said:
R5.8
Memory management hugely improved (finally LMK works properly)
Fixed powersave interface on JB 4.1.2 stock
Experimental fixes to PowerHAL on 4.4.4
LiveOPP: merged changes from refresh kernel (removed some CPU freq steps)
Dynamic: adjust tunables (same like in refresh kernel)
Possible vibrator fix on 6.0+ (not tested)
Click to expand...
Click to collapse
I tried 5.8.5 and I have still issues with LineageOS 11:
1) I've got a screen flicker issue while I was browsing in Naked Browser with the new LCDCLK frequency.
Tried to set echo 1 > /sys/kernel/mcde/lcdclk, but I've noticed that this value is not kept after a reboot.
Very annoying, because I can't restore 60 Hz permanently.
2) There are still issues about some values not kept in the performance UI of Lineage Os.
For example:
- Try to set Zenx as governor, min. 200 max 1000, Noops scheduler. Reboot. Scheduler will be resetted to Deadline.
- There is still a bug with max clock value of Dynamic governor (I can reproduce it with ZenX governor too). I set it to 800 MHz, I go back to the settings screen, then I return to the Performance -> Processor section to check if the 800 MHz value is maintained. But the UI automatically restored the max clock to 1000 MHz without my consent.
For your information, these issues occur only randomly and with particular combinations. So, if you can't reproduce them, the best way is to set these, one at a time:
1) Zenx as governor, min. 200 max 800, Noops scheduler. Reboot.
2) Zenx as governor, min. 200 max 800, Fiops scheduler. Reboot.
2) Zenx as governor, min. 200 max 800, Sioplus scheduler. Reboot.
After the first, the second or the third reboot, some of these values you've set will change spontaneously on their own.
"Set on boot" options are correctly set for both Processor and I/O Scheduler.
And I keep "Enable per-app profiles" option turned off.
3) On the Performance UI, performance profile results automatically set on Balanced after any reboot. But if you cannot fix it, I can live with that, don't worry. It doesn't keep "Power save" or "Performance" profile between reboots.
PS: I would appreciate if you could update the installation steps in this thread with the same steps of the refresh topic:
Flash temporary kernel (if coming from other recoveries than TWRP 3.1.1)
Reboot recovery
Flash kernel zip
isaak said:
I tried 5.8.5 and I have still issues with LineageOS 11:
1) I've got a screen flicker issue while I was browsing in Naked Browser with the new LCDCLK frequency.
Tried to set echo 1 > /sys/kernel/mcde/lcdclk, but I've noticed that this value is not kept after a reboot.
Very annoying, because I can't restore 60 Hz permanently.
Click to expand...
Click to collapse
Sorry, I thought I've reverted this change. Can you confirm that setting old LCDCLK freq fixes issue? As a temporary solution you can use init.d script to set the appropriate LCDCLK freq index.
2) There are still issues about some values not kept in the performance UI of Lineage Os.
For example:
- Try to set Zenx as governor, min. 200 max 1000, Noops scheduler. Reboot. Scheduler will be resetted to Deadline
Click to expand...
Click to collapse
Can confirm now. I have a guess for that, for now the solution as follows:
remove /ramdisk/modules/autoload/sioplus-iosched.ko, reboot. I have to test this a bit more time to be sure 100%, but so far I couldn't reproduce an issue after removing this module (no other CPUfreq governor or I/O scheduler must be loaded as well).
- There is still a bug with max clock value of Dynamic governor (I can reproduce it with ZenX governor too). I set it to 800 MHz, I go back to the settings screen, then I return to the Performance -> Processor section to check if the 800 MHz value is maintained. But the UI automatically restored the max clock to 1000 MHz without my consent.
Click to expand...
Click to collapse
It's not a bug, but rather intended behavior - due to PowerHAL changes implemented, CPUfreq can only be changed via script (see /ramdisk/perf.sh). I've previously asked if anyone would prefer to adjust CPUfreq usual way, In this case I can just remove the corresponding lines from the PowerHal script. This will make PowerHAL settings a bit more useless, but will gave easier control over CPUfreq.
3) On the Performance UI, performance profile results automatically set on Balanced after any reboot. But if you cannot fix it, I can live with that, don't worry. It doesn't keep "Power save" or "Performance" profile between reboots.
Click to expand...
Click to collapse
The script actually works, though you're right, it works buggy and everytime shows the default profile (you can set, e.g. Powersave profile and check min/max CPU freq, to check if it actually works).
PS: I would appreciate if you could update the installation steps in this thread with the same steps of the refresh topic:
Flash temporary kernel (if coming from other recoveries than TWRP 3.1.1)
Reboot recovery
Flash kernel zip
Click to expand...
Click to collapse
Done!
isaak said:
I've got a screen flicker issue while I was browsing in Naked Browser with the new LCDCLK frequency.
Tried to set echo 1 > /sys/kernel/mcde/lcdclk, but I've noticed that this value is not kept after a reboot.
Very annoying, because I can't restore 60 Hz permanently.
ChronoMonochrome said:
Sorry, I thought I've reverted this change. Can you confirm that setting old LCDCLK freq fixes issue? As a temporary solution you can use init.d script to set the appropriate LCDCLK freq index.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Yes, I can confirm that setting old LCDCLK freq fixed the flicker issue for my screen. I think it would be better to set it as default in the next release.
isaak said:
There are still issues about some values not kept in the performance UI of Lineage Os.
For example:
- Try to set Zenx as governor, min. 200 max 1000, Noops scheduler. Reboot. Scheduler will be resetted to Deadline
etc etc....
ChronoMonochrome said:
Can confirm now. I have a guess for that, for now the solution as follows:
remove /ramdisk/modules/autoload/sioplus-iosched.ko, reboot. I have to test this a bit more time to be sure 100%, but so far I couldn't reproduce an issue after removing this module (no other CPUfreq governor or I/O scheduler must be loaded as well).
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I tried your steps, unfortunately they didn't work for me.
ChronoMonochrome said:
It's not a bug, but rather intended behavior - due to PowerHAL changes implemented, CPUfreq can only be changed via script (see /ramdisk/perf.sh). I've previously asked if anyone would prefer to adjust CPUfreq usual way, In this case I can just remove the corresponding lines from the PowerHal script. This will make PowerHAL settings a bit more useless, but will gave easier control over CPUfreq.
Click to expand...
Click to collapse
Personally I would prefer more control over CPUfreq. Could you list the main advantages to limit CPUfreq changes only via script? Is it a sort of auto-optimization? This point is not clear to me. If you think that any change to this mechanism would affect negatively the battery life, then don't change anything.
isaak said:
On the Performance UI, performance profile results automatically set on Balanced after any reboot. But if you cannot fix it, I can live with that, don't worry. It doesn't keep "Power save" or "Performance" profile between reboots.
ChronoMonochrome said:
The script actually works, though you're right, it works buggy and everytime shows the default profile (you can set, e.g. Powersave profile and check min/max CPU freq, to check if it actually works).
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I tried Powersave and Performance profiles, in both cases the maximum freq varies between 400 MHz and 1000 MHz, rarely reaching 800 MHz. Minimum freq is always 200 MHz and it doesn't change visually like the maximum freq. Balanced profile is always shown visually after a reboot.
isaak said:
Personally I would prefer more control over CPUfreq. Could you list the main advantages to limit CPUfreq changes only via script? Is it a sort of auto-optimization? This point is not clear to me. If you think that any change to this mechanism would affect negatively the battery life, then don't change anything.
Click to expand...
Click to collapse
Because of some CPUfreq scaling tunables were changed (in the case of Dynamic governor), it makes sense to implement a PowerHAL profiles, which would limit / restore the max CPUfreq. But I think I've found a solution - I will make it possible to change CPUfreq for a Balanced profile.
I tried Powersave and Performance profiles, in both cases the maximum freq varies between 400 MHz and 1000 MHz, rarely reaching 800 MHz. Minimum freq is always 200 MHz and it doesn't change visually like the maximum freq. Balanced profile is always shown visually after a reboot.
Click to expand...
Click to collapse
Ok, I found some logical errors in the script, should be fixed in upcoming release.
Hi!
After a period of use, I will recommend to everyone the optimal Mod version for Mi 9.
Support for Pie and Q
List of changes:
Version 4.0.2: (Fix)
- Add governors: conservative, ondemand
- Governors:
+ conservative ( support kernel stock )
+ ondemand ( support kernel stock )
+ schedutil ( support kernel stock and kernel evira )
+ schedutil_pixel ( support kernel evira )
+ smurfutil ( support kernel evira )
- Delete edit profile
- Updated GPU Optimizer
- Updated CPU Optimization
- Updated I/O Optiomization
- Updated RAM Optiomization
Note: We recommend using the ondemand governor to save battery power for kernel stock and kernel MOD.Q
Version 3.7:
- Improve CPU performance at the lowest level to optimize battery and performance. The mod works fine on the kernel evira
Version 3.4.1:
Support Magisk 20.2
Version 3.3:
- Improve stability
- Updated two versions: battery saving mode, performance mode
Version 3.2:
- Improve stability
Version 3.1:
- Improve stability
Version 3:
- Temperature control
- Improved multitasking
- Turned off Ramdump
- ZRAM 1G
- Double your bandwith
- Increase the speed of reading and writing of the system
- Battery saving mode optimized for Cpu by @mslezak (XDA)
Version 2:
- The charging current limit is modified to 6000mA
- Temperature control
- Forced to charge full blood fast (removed)
- Turned off Ramdump
- ZRAM 1G
- Turned off LMK adaptive mode
- Double your bandwith
- Improve touch and slide fluency
- Increase the speed of reading and writing of the system
- Optimized for Cpu by @mslezak (XDA)
Version 1:
Optimized power in standby mode
Forced to charge full blood fast
Turned off Ramdump
Add ZRAM 1G
LMK adaptive mode
Double your bandwith
Thermal S855 balanced-42℃ Performance-46℃ Gaming-55℃
Optimized for Cpu by @mslezak
All mod edits by NTH for Mi9
https://t.me/Mi9Mod
https://t.me/ModByNTH
Thanks for giving a contribution!!!
Awesome this is what I hoped people would go out and do - make their own modules to use with the kernel. I will post in TG and reference you.
NTH94 said:
Hi!
After a period of use, I will recommend to everyone the optimal Mod version for Mi 9.
List of changes:
Optimized power in standby mode
Forced to charge full blood fast
Turned off Ramdump
Add ZRAM 1G
LMK adaptive mode
Double your bandwith
Thermal S855 balanced-42℃ Performance-46℃ Gaming-55℃
Optimized for Cpu and Ram by @mslezak
All mod edits by NTH for Mi9
https://t.me/ModByNTH
Click to expand...
Click to collapse
Is this for android 9 only?
mslezak said:
Awesome this is what I hoped people would go out and do - make their own modules to use with the kernel. I will post in TG and reference you.
Click to expand...
Click to collapse
Yes
sepsep 21 said:
Is this for android 9 only?
Click to expand...
Click to collapse
Tested on Android 9 and Android 10 both work on a Miui 10 and 11 basis
Thank you for your awesome mod. One question is it possible to do a mod for change of switch off animation, for example CTR (old tv) ect. It was on exposed but now no one do it till now.
Best Regards.
zoltan78 said:
Thank you for your awesome mod. One question is it possible to do a mod for change of switch off animation, for example CTR (old tv) ect. It was on exposed but now no one do it till now.
Best Regards.
Click to expand...
Click to collapse
You can go to developer options to turn it off
NTH94 said:
You can go to developer options to turn it off
Click to expand...
Click to collapse
I am thinking about animation when you turn off screen. In exposed module called "switch off animation" you can choose stile of this animation. In developer option there is not.
zoltan78 said:
I am thinking about animation when you turn off screen. In exposed module called "switch off animation" you can choose stile of this animation. In developer option there is not.
Click to expand...
Click to collapse
I understand your problem, can you tell me more about it and Mod about it
It is not this. Something like this
https://youtu.be/CnjxkpZDsgw
zoltan78 said:
It is not this. Something like this
https://youtu.be/CnjxkpZDsgw
Click to expand...
Click to collapse
It needs Xposed to work, I can't help you
Thanks for answer. I thought that it is possible to do something similar like this for magisk. BTW thanks for all your hard work. [emoji106]
is this work miui11 android10 ?
sefai77 said:
is this work miui11 android10 ?
Click to expand...
Click to collapse
Yes
Does it realy extend battery life in stnadby? Is there option to switch off fast charging?
Khotu said:
Does it realy extend battery life in stnadby? Is there option to switch off fast charging?
Click to expand...
Click to collapse
If you are afraid of their battery life, I recommend you not to use it
where can i check that it works ? Can I share the module in another forum ?
sefai77 said:
where can i check that it works ? Can I share the module in another forum ?
Click to expand...
Click to collapse
That's just your experience, not verifiable, you can share whoever you want
Do all other modules from magisk have to be deactivated before it's installation, or I can install on top of it?
catalindobre said:
Do all other modules from magisk have to be deactivated before it's installation, or I can install on top of it?
Click to expand...
Click to collapse
If you want the best experience, you should delete the optimal module on the device