Related
i have a motorola droid and it is rooted.i flashed a new rom and then i flashed sprecovery,i let it run its course and i disconnected the phone.when the phone turns on it starts up and then a red light comes on and my phone says please connect charger.it keeps saying android process is not responding and then the phone shuts itself off.ive tried to boot it into recovery mode and do a restore,it keeps giving me an error that says nandroid exited with status 20 and its also not reading my sd card.can somebody tell me whats happened and if it can be fixed???please and thank you
Well, seems as if you need to reflash or restore because of bad flash. If you try flashing again make sure you wipe data and cache. As far as not reading sdcard I have same problem not sure why but when I'm in recovery and I choose install zip which I used clockworkmod recovery, if it fails then it reboots automatically after couple seconds not sure if this happens with sprecovery. After sdcard mount fail it shuts down and reboots so before it reboots I pull the battery and wait a minute or two before trying again. It may take me 3 to 4 times of doing this but eventually it will mount sdcard in recovery. I recommend keep trying till it allows you to apply recovery file and then flash to either clockworkmod or sprecovery which ever one you not using and then flash back to the one you want. I'd also recommend try if after all this you flash rom again and same thing happens redownload it and try again. Good luck.
Sent from Droid using, Sapphire v1.0.0/ 928Droid Black Glass 2.2 Theme/ Sholes 1.0 Ghz 7 Slot Kernel.
Please install Advanced Task Manager and from the setting use what ever setting that might suite you.
For me i use the following setting:
Auto Kill Level --> Safe
Auto Kill Frequecny --> Every One Hour
Security Level --> Meduim
With the above setting, i didn't face any performance problem and reduced reboot frequency (General Problem in the Android).
Feel free to ask any question and I will be ready for you
fadimck said:
Please install Advanced Task Manager and from the setting use what ever setting that might suite you.
For me i use the following setting:
Auto Kill Level --> Safe
Auto Kill Frequecny --> Every One Hour
Security Level --> Meduim
With the above setting, i didn't face any performance problem and reduced reboot frequency (General Problem in the Android).
Feel free to ask any question and I will be ready for you
Click to expand...
Click to collapse
Please note, that there have been wide reports of people having issues with various task killer apps consuming excessive amounts of battery life when used on a Droid with Froyo.
Please install Advanced Task Manager and from the setting use what ever setting that might suite you.
For me i use the following setting:
[*]Auto Kill Level --> Safe
[*]Auto Kill Frequecny --> Every One Hour
[*]Security Level --> Meduim
With the above setting, i didn't face any performance problem and reduced reboot frequency (General Problem in the Android).
Feel free to ask any question and I will be ready for you
Click to expand...
Click to collapse
Please note, that there have been wide reports of people having issues with various task killer apps consuming excessive amounts of battery life when used on a Droid with Froyo.
Click to expand...
Click to collapse
Okay, I didn't know this info as I've Milestone with stock OS 2.1
Sent from my Milestone using XDA App
Q&A for [Kernel][CPU OC][GPU OC][F2FS] CroPol kernel
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
doesn't work
I've got an error on boot, something like 0x0000d0d2. I got it with all versions. I use the latest cm10.2 by novaFusion with PurePerformanceX installed.
vietnam131 said:
I've got an error on boot, something like 0x0000d0d2. I got it with all versions. I use the latest cm10.2 by novaFusion with PurePerformanceX installed.
Click to expand...
Click to collapse
Afaik it doesn't support 4.3.x ROMs. Try any 4.4.x ROM.
Ok, I will try. But if you can make this kernel for previous versions of Android, it would be nice.
i cant get 1150/2000 mhz
what cpu governor and i/0 scheduler are you guys running to get 1150/2000 mhz? i have the normal s3 mini, not the nfc version and im running cyanogenmod.
snakeboy1011 said:
what cpu governor and i/0 scheduler are you guys running to get 1150/2000 mhz? i have the normal s3 mini, not the nfc version and im running cyanogenmod.
Click to expand...
Click to collapse
Try pegasusqplus+sioplus.
mauam said:
Try pegasusqplus+sioplus.
Click to expand...
Click to collapse
what should i put as the min frequency?
snakeboy1011 said:
what should i put as the min frequency?
Click to expand...
Click to collapse
100 or 200. You need to try by yourself
what ROM do you use as I don't think CyanogenMod supports 1150/2000mhz?
mauam said:
100 or 200. You need to try by yourself
Click to expand...
Click to collapse
Sorry for your time
deep sleep bug? reboot bug? voltage limits? persistent config by userinit.sh?
Hello!
I got several questions regarding the usage of this kernel's voltage and clocking/voltage options:
1. Everytime my mobile goes to deep sleep, it sets maximum clock to 400MHz and minimum clock to 100MHz. It stays so after enabling and while using the phone. It's horrible slow. So I got to increase maximum clock by hand everytime the phone was in deep sleep before.
What's the problem there?
2. After rebooting the maximum clock is always reset to 1000MHz, although i had set it to 1150/1200MHz before.
Why?
3. I noticed 1200MHz not being completely stable on my device. So I wanted to increase the voltage for step9.
In /sys/kernel/liveopp/arm_slot09 i saw the default hex value for VARM was 0x3f. So I tried increasing this to 0x40 and 0x41, but the voltage shown in this file didn't increase anymore.
3a) So is the voltage capped at 1362,5000mV or is it just not displayed correctly?
3b) Will increasing Varm to more than 0x3f do anything at all?
Also I've seen the voltage called Vbbx (default value for step9: 0xff)
3c) What exactly is this voltage, and how does it go together with Varm?
3d) Is there a way for increasing voltage any further than 0x3f for Varm and 0xff for Vbbx?
4. For persistence I tried automatically setting changed voltage parameters on boot, using userinit.sh.
The file didn't exist before, so i created it as /sys/local/user/userinit.sh, set the perissions to 755, and added the following content:
Code:
#!/system/bin/sh
echo set_volt= 1 > /sys/kernel/liveopp/arm_slot09
echo set_varm = 0x41 > /sys/kernel/liveopp/arm_slot09
But the script doesn't work. After rebooting varm for step09 is always at default value (0x3f).
4a) Why doesn't this work?
4b) I think it maybe is not working because the above command needs to be run as root, but how could i do this in userinit.sh without sudo?
Many thanks for patience and help!
Elmarigo said:
1. Everytime my mobile goes to deep sleep, it sets maximum clock to 400MHz and minimum clock to 100MHz. It stays so after enabling and while using the phone. It's horrible slow. So I got to increase maximum clock by hand everytime the phone was in deep sleep before.
What's the problem there?
Click to expand...
Click to collapse
First of all, notice that deep sleep is a power state in which the CPU has a very low voltage consumption.. Therefor its not even clocked at 100 Mhz. With this Kernel, when screen is off, the clock is set 100-400 MHz if its needed (by wake locks).
Now, I see that the problem here is that it stays when you wake the phone. What ROM are you using? You could try flashing the Kernel again.
Elmarigo said:
2. After rebooting the maximum clock is always reset to 1000MHz, although i had set it to 1150/1200MHz before.
Why?
Click to expand...
Click to collapse
Unless this values are set compiled in kernel, you will have to manually set everytime you boot. But a quick solution is to enable the "apply settings on boot" on the app that you are using to OC. (You can use ROM Toolbox if your ROM doesn't have built in this options)
Elmarigo said:
4. For persistence I tried automatically setting changed voltage parameters on boot, using userinit.sh.
The file didn't exist before, so i created it as /sys/local/user/userinit.sh, set the perissions to 755, and added the following content:
Code:
#!/system/bin/sh
echo set_volt= 1 > /sys/kernel/liveopp/arm_slot09
echo set_varm = 0x41 > /sys/kernel/liveopp/arm_slot09
But the script doesn't work. After rebooting varm for step09 is always at default value (0x3f).
4a) Why doesn't this work?
4b) I think it maybe is not working because the above command needs to be run as root, but how could i do this in userinit.sh without sudo?
Click to expand...
Click to collapse
Try deleting the space between "1" and ">" like this:
Code:
#!/system/bin/sh
echo set_volt= [B]1>[/B] /sys/kernel/liveopp/arm_slot09
echo set_varm = 0x4[B]1>[/B] /sys/kernel/liveopp/arm_slot09
xhhb said:
First of all, notice that deep sleep is a power state in which the CPU has a very low voltage consumption.. Therefor its not even clocked at 100 Mhz. With this Kernel, when screen is off, the clock is set 100-400 MHz if its needed (by wake locks).
Now, I see that the problem here is that it stays when you wake the phone. What ROM are you using? You could try flashing the Kernel again.
Click to expand...
Click to collapse
Hello!
I'm using Carbon Rom by novafusion. There's an update from 27.10. now, and I'll see later if this helped against this particular problem!
xhhb said:
Unless this values are set compiled in kernel, you will have to manually set everytime you boot. But a quick solution is to enable the "apply settings on boot" on the app that you are using to OC. (You can use ROM Toolbox if your ROM doesn't have built in this options)
Click to expand...
Click to collapse
In Carbon there's an option for applying saved values on boot. I used these and I also tried CoCoreManager, but both didn't apply my saved config although I had enabled this setting.
xhhb said:
Try deleting the space between "1" and ">" like this:
Code:
#!/system/bin/sh
echo set_volt= [B]1>[/B] /sys/kernel/liveopp/arm_slot09
echo set_varm = 0x4[B]1>[/B] /sys/kernel/liveopp/arm_slot09
Click to expand...
Click to collapse
Ok, I will try this. Is userinit.sh being executed as root by automatic?
Thank you!
Ok, i found multiple bugs in my script and corrected these.
The script currently is like:
Code:
#!/system/bin/sh
echo set_volt=1 > /sys/kernel/liveopp/arm_step09
echo varm=0x41> /sys/kernel/liveopp/arm_step09
The commands are working from terminal/SSH, but playing them in /data/local/userinit.sh doesn't change anything after reboot. (file is marked as executable!)
So can anyone help please how to make this working?
I still believe it's maybe because of the script not being executed with root permissions, but I'm not sure about that and I don't know how to work around this without a sudo command.
Also I still could use help with my remaining questions from my older post: http://forum.xda-developers.com/showpost.php?p=56343298&postcount=10
Thank you!
PS: this 10message restriction for 'new users' doesn't seem like a working way for keeping the forum's content at good quality.
I'm forced to writing in Q&A-Thread, while the creator and the other most experienced users of original thread don't even seem to look here.
Aswhile, the 'more experienced' users, having more then 10messages, in original thread are keeping the most experienced users busy, asking questions that are even way more basic than mine, but regarding the same topic (persistent undervolting). So I can't help these users and no one from that other thread can help me
Not working on miui
I flashed it on miui v5 http://forum.xda-developers.com/showthread.php?t=2647472 and it won't boot!!! Need help!!!!
chaudhary1122 said:
I flashed it on miui v5 http://forum.xda-developers.com/showthread.php?t=2647472 and it won't boot!!! Need help!!!!
Click to expand...
Click to collapse
Did you delete your Cache and reboot twice?
If you already did, then flash your full ROM again.
Elmarigo said:
Did you delete your Cache and reboot twice?
If you already did, then flash your full ROM again.
Click to expand...
Click to collapse
Nope, I guess not. So I'll give it a try now!!! Thanx!!!!
Elmarigo said:
Did you delete your Cache and reboot twice?
If you already did, then flash your full ROM again.
Click to expand...
Click to collapse
Did it but still not working!!! Not booting first the Samsung startup screen with the name and model is replaced with a white screen and then comes a black screen with red text at the top left corner I don't actually remember what it says!!!! Need help!!!
wifi and bt not work
I have a problem with this kernel , no wifi or bluetooth install on virginity v14 rom with option 2 for stock based rom otherwise I will work perfect kernel 1.1 ghz wifi but I need someone a suggestion? Do not attempt to try to option 1 cm based on that I guess should be different thanks
chaudhary1122 said:
Did it but still not working!!! Not booting first the Samsung startup screen with the name and model is replaced with a white screen and then comes a black screen with red text at the top left corner I don't actually remember what it says!!!! Need help!!!
Click to expand...
Click to collapse
I think for saving your phone you should flash your previous ROM (the one you had on that phone before) using Odin from a PC. If this doesn't help either you should try Full Wipe and flash stock ROM.
Follow these instructions: http://forum.xda-developers.com/showthread.php?t=2159660
LaInfluenza said:
I have a problem with this kernel , no wifi or bluetooth install on virginity v14 rom with option 2 for stock based rom otherwise I will work perfect kernel 1.1 ghz wifi but I need someone a suggestion? Do not attempt to try to option 1 cm based on that I guess should be different thanks
Click to expand...
Click to collapse
I didn't see anyone else trying the kernel on stock-ROM, yet. You should write a PM to ChronoMonochrome about this, so he can tell the developer.
Elmarigo said:
I think for saving your phone you should flash your previous ROM (the one you had on that phone before) using Odin from a PC. If this doesn't help either you should try Full Wipe and flash stock ROM.
Follow these instructions: http://forum.xda-developers.com/showthread.php?t=2159660
I didn't see anyone else trying the kernel on stock-ROM, yet. You should write a PM to ChronoMonochrome about this, so he can tell the developer.
Click to expand...
Click to collapse
The fact that the kernel is pretty good, I loved it but I need the wifi I use it all day and does not serve me well beyond virginity v14 rom that I really like, I tried it on the newest cm11 but I do not really like this rom I hope for the next update will fix this kernel as serious buenisimo roms have oc in stock or stock -based.
Description
This module is my port of Crossbreeder, the old version was designed for Android 4.4 and below. So if you try use it on Android 5.0 and above, you will have some problems with it.
But now I have fixed that problem, and have changed some of the script; which was out-of-date. I have also added some new features of my own.
Details
For those who want to know what is this mod for, here are the details:
Random/Frandom tweak
Remove /dev/random as it's blocking . Link it to non-blocking /dev/urandom. Since /dev/random is blocking and designed to protect us from Quantum alien cryptographers with mathematical certainty and urandom is non blocking pseudo-random device that most apps and OSs are using anyway and with Haveged running, is as secure anyway as it's very difficult to empty the entropy pool faster than Havege can replenish it. Pre ICS devices have a lot to gain with this but ICS+ devices show visible gains too.
Haveged/Entropy tweak
Modulate OS entropy levels for lag reduction ala Seeder. The whole OS reads either /dev/random or /dev/urandom and both need entropy. However this mod uses a completely different, lightweight and efficient random number generator called Havege . This sharply reduces cpu consumption and corresponding battery life loss compared to Seeder. It also does a better job at keeping entropy levels high hence your device is more responsive. It doesn't run in a CPU intensive loop either. The extend queue functionality has also been added to CrossBreeder. See here for another rationale favouring Havege compared to Rngd - ( Look for the limitations)
Fix "Only position independent executables (PIE) are supported" problem on Android 5.0+ device
Here is how to fix it :
1. Install the Hex Editor.
2. Open the file in Hex Editor.
3. Find the 17th number, if the number is 02, change it to 03.
4. Save the file, that's it !
[Add-on 1] Dynamic Z-RAM/LMK
This tweak will automatic find how much ram do you have, how much ram do you left, then according to these value to set zram/lmk size.
[Add-on 1] Dynamic Power Saving
Here is the original post, I found this feature in Feradroid v0.24
A little translate:
DynBS can significantly reduce power consumption without shutting down the main functionality of the Android device (such as Wi-Fi, Bluetooth, mobile Internet, screen brightness, background processes) by reducing unnecessary high-frequency CPU when not needed.
Magisk Busybox Restorer
This module will let the busybox can be used externally at Magisk v15+
By linking the busybox in /data/adb/magisk to /sbin
Only support Magisk v15+
Trouble Shooting
1. Stuck at the boot stage
---> Reboot again ---> Not work? ---> Flash it again to uninstall it.
2. Application keep crashing after installed this module
---> Just disable Dynamic LMK.
3. CTS Profile miss match
---> Enable all the ways that you can hide the magisk, if its not work, then you can try Universal SafetyNet Fix
4. Any problem about CPU frequency, like your device become so slow, or become warmer, etc.
---> Disable DynBS can fix the problem
5. How to open the setting menu?
---> Open terminal, and type "cbconf" can open it.
6. The phone shows the message of rebooting/turning off but after 30 mins ,the process is not finished
---> Try to forced shutdown
7. Busybox-ndk failed because of install CrossBreeder
---> Try to use mine busybox
This module only test on my HTC One M7 running latest Slim 7.1.2 with Magisk 15.3
Not tested with Android 8.0+ yet.
If you want to install any add-on, you must install the main mod first.
Credit
1. Crossbreeder ( https://forum.xda-developers.com/showthread.php?t=2113150 ) - For most of files
2. FeraDroid Engine ( https://forum.xda-developers.com/an...beta-feradroid-engine-v0-19-ultimate-t3284421 ) - For the Governor Tweak
3. Dynamic Power Saving ( http://4pda.ru/forum/index.php?showtopic=620736&st=1120 )
Github Link
I'm on Lineage OS, OnePlus 3T, Radioactive Kernel, and for some reason whenever I enable this module, it breaks Root (MagiskSU). I'm not sure if this is a known problem, but if not, now you know. ;P
Yea it breaks safetynet for me when I enabled it on magisk. Though for the mod itself that seems to be working great, don't know if it's placebo but I am noticing a little less "lag" on some apps.
Finally, was searching for any information on this module, and got nothing except the original. Any reason why it took so long for a thread to be created about it?
loocool2 said:
Finally, was searching for any information on this module, and got nothing except the original. Any reason why it took so long for a thread to be created about it?
Click to expand...
Click to collapse
I messaged Rorsch about making a thread for their module a couple of days ago, so I assume the thought just didn't occur to them to make a thread. But now it's all good because there's a thread for it
Breaks Root? Try this
ht#tps://drive.google.com/open?id=0B1nFPsNMRIiiYzlsbWxxazlPUkk <------- Remove #
Test on Slimroms 7.1.2 / HTC ONE M7
Rorsch_X1 said:
Breaks Root? Try this
ht#tps://drive.google.com/open?id=0B1nFPsNMRIiiYzlsbWxxazlPUkk <------- Remove #
Test on Slimroms 7.1.2 / HTC ONE M7
Click to expand...
Click to collapse
Seems to be working! Although it's not 100% stable, it's better than having a totally broken Root.
This module gets me stuck in a strange bootloop everytime: I've tried 0.3a version some a week's ago and now with 0.8b. Phone seems to be booting, it passes Google splash screen, there's that little vibration that means the phone's booting right and then it gets stuck in there. Which logs should I provide to be helpful? Maybe last-kmsg?
Sent from my Nexus 5X using XDA Labs
edoardotavecchio said:
This module gets me stuck in a strange bootloop everytime: I've tried 0.3a version some a week's ago and now with 0.8b. Phone seems to be booting, it passes Google splash screen, there's that little vibration that means the phone's booting right and then it gets stuck in there. Which logs should I provide to be helpful? Maybe last-kmsg?
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Maybe... but we could just try something easier... ;P
What tweaks have you got? Like; are you using other Magisk modules? Have you changed your build.prop via an app like L Speed, or something like that? Have you made any kernel tweaks? What CPU governor are you using?
It sounds like something CB is trying to modify is conflicting with something else.
edoardotavecchio said:
This module gets me stuck in a strange bootloop everytime: I've tried 0.3a version some a week's ago and now with 0.8b. Phone seems to be booting, it passes Google splash screen, there's that little vibration that means the phone's booting right and then it gets stuck in there. Which logs should I provide to be helpful? Maybe last-kmsg?
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Maybe you have too many file in the /system or installed too many modules
It will take a lot of time on the mount stage
Send me your magisk log
nan0s7 said:
Maybe... but we could just try something easier... ;P
What tweaks have you got? Like; are you using other Magisk modules? Have you changed your build.prop via an app like L Speed, or something like that? Have you made any kernel tweaks? What CPU governor are you using?
It sounds like something CB is trying to modify is conflicting with something else.
Click to expand...
Click to collapse
As tweaks, I've removed HEBF and LSpeed apps because I've had the same idea as you. As Magisk Modules, I've installed some camera and audio mods (Some very common mods for 5X: eis, 60fps libs, surround audio mod), Universal Deep Buffer remover, Selinux permissive script and Viper. The only one which modifies build.prop is EIS module. Does Crossbreeder modify build.prop too? Should I remove EIS in order to make this work?
As CPU governor, I'm using interactive (governor profile:Glasscannon)
Rorsch_X1 said:
Maybe you have too many file in the /system or installed too many modules
It will take a lot of time on the mount stage
Send me your magisk log
Click to expand...
Click to collapse
That's strange because usually it's very very fast, it takes something like 3-4 seconds after the vibration. Eith this module installed, I've tried to wait even 10 minutes without any success.
Now I'll retry and send you Magisk log.
Sent from my Nexus 5X using XDA Labs
That's my magisk log without having crossbreed installed. Can you take a look and see if there's something in conflict with your module? @Rorsch_X1
Sent from my Nexus 5X using XDA Labs
edoardotavecchio said:
That's my magisk log without having crossbreed installed. Can you take a look and see if there's something in conflict with your module? @Rorsch_X1
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
I don't know about conflicts, but I saw you're using the audmodlib module by @ahrion with the V4A module by @metaspook. That Viper module isn't made to utilise the audmodlib... You probably wanted this one: https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
Didgeridoohan said:
I don't know about conflicts, but I saw you're using the audmodlib module by @ahrion with the V4A module by @metaspook. That Viper module isn't made to utilise the audmodlib... You probably wanted this one: https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
Click to expand...
Click to collapse
I know that and I've tried it but it didn't work.
Edit: Now it is working. what
Thanks for your suggestion.
Sent from my Nexus 5X using XDA Labs
crayola555 said:
Yea it breaks safetynet for me when I enabled it on magisk. Though for the mod itself that seems to be working great, don't know if it's placebo but I am noticing a little less "lag" on some apps.
Click to expand...
Click to collapse
I am a big fan of crossbreeder... However...
Iirc without frandom... You are not actually generating "random"
And according to what I have read (stop me if I'm wrong)... The less "lag" you are seeing is from that random number generation keeping your processor a little more ramped up... Equivalent to turning touchboost up a notch... Or raising your cpu min frequency...
Sent from my Nexus 6 using Tapatalk
This work on rooted s7 w/ Exynos CPU?
pan.droid said:
This work on rooted s7 w/ Exynos CPU?
Click to expand...
Click to collapse
Yes, it works on all ARM devices.
edoardotavecchio said:
That's my magisk log without having crossbreed installed. Can you take a look and see if there's something in conflict with your module? @Rorsch_X1
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
I have tried am3d & v4a & Audio-Modification-Library & deep buffer remover with my CrossBreeder , but they all works fine.
Where were you stuck at? Boot Animation or Boot logo?
By the way, are you using Android O? I see libfmas.so & android.hardware.audio.low_latency.xml & android.hardware.audio.pro.xml in the log you sent to me.
Rorsch_X1 said:
I have tried am3d & v4a & Audio-Modification-Library & deep buffer remover with my CrossBreeder , but they all works fine.
Where were you stuck at? Boot Animation or Boot logo?
By the way, are you using Android O? I see libfmas.so & android.hardware.audio.low_latency.xml & android.hardware.audio.pro.xml in the log you sent to me.
Click to expand...
Click to collapse
I get stuck at bootanimation after the "boot completed" vibration (that little vibration which runs a few seconds before the phone booting, usually reporting that boot process has been nearly completed). I've never experienced a situation like this in 6 years of modding so I don't know what could have gone wrong: the vibration usually doesn't trigger (when phone can't boot and gets stuck in a bootloop) or after a few minutes, a few seconds before booting (when the OS takes a lot to mount partitions or compiling caches, per example when you clean flash a new OS and caches have to be rebuilt). It's so strange that vibration fires and the phone doesn't boot anyway. I've tried to let the phone work for something like 20 minutes (which I consider is even too much for a simple boot) but nothing happens anyway.
Anyway no, I haven't updated to O yet because some mods aren't compatible with it yet so I've stopped on 7.1.2 which is stable and fully supported.
edoardotavecchio said:
I get stuck at bootanimation after the "boot completed" vibration (that little vibration which runs a few seconds before the phone booting, usually reporting that boot process has been nearly completed). I've never experienced a situation like this in 6 years of modding so I don't know what could have gone wrong: the vibration usually doesn't trigger (when phone can't boot and gets stuck in a bootloop) or after a few minutes, a few seconds before booting (when the OS takes a lot to mount partitions or compiling caches, per example when you clean flash a new OS and caches have to be rebuilt). It's so strange that vibration fires and the phone doesn't boot anyway. I've tried to let the phone work for something like 20 minutes (which I consider is even too much for a simple boot) but nothing happens anyway.
Anyway no, I haven't updated to O yet because some mods aren't compatible with it yet so I've stopped on 7.1.2 which is stable and fully supported.
Click to expand...
Click to collapse
Maybe the some script conflict with your system, try this version, you can enable/disable the tweak by yourself.
https://drive.google.com/open?id=0B1nFPsNMRIiiM2xocl9RTGt3OEk
After install this version, you need to go to /data/CrossBreeder, open the file with text editor then change the 0 to 1 to enable the tweak, I disable all in these config files.
P.S. Don't edit the CONF
ROM IS TESTED ON 2 DEVICES AND FORCE CLOSES SHOULD BE GONE. AFTER RUNNING DO CHECK PERMISSIONS IN MiASSISTANT (check also accelarator/settings/disable "lock screen boost" and set protected apps list ; also set right permissions for apps not to sleep/stop....) AND PERMISSIONS UNDER BATTERY SETTINGS PHONE....
Made an AROMA SL!M DF!NR rom of the chinese A2017 V2.0 B13 MiFavor 5.0 version focused on :
* Force closes on google apps
* JoJoc Battery Tweak : https://forum.xda-developers.com/axon-7/how-to/tweak-jojoc-tuning-battery-focused-t3704831
Thnx @nfsmw_gr for our work together ! Gave me an amazing 8.30h SOT !
*EDIT : as this BXSRVEngine tweak may interfere in some cases with your dialer app and may cause a higher volume on your in-call or speakermode and can not be adjusted in some cases, I advice better not to install this tweak in aroma features - it was just intended to have some better pics/video quality but then again not that necessary.
BXSRVEngine : https://forum.xda-developers.com/an...recompeliren-bravia-engine-x-reality-t3141461
SUITED FOR ALL VERSIONS
Just follow procedure in detail and you should be OK !
Hope you’ll E N J O Y !!!
Based on : A2017 V2.0 B13 MiFavor 5.0
INSTALL : ( TWRP ) IN FOLLOWING ORDER !
I do advice to install :
JoJoc and (BXRVEngine) and either SuperSU or Magisk to check all features are working
Let’s begin….
0. In case you want to reflash your own apps backup your personal apps with f.e. TB, ZipMe... (or whatever)
00. running TWRP 3.1.1.0 (!)
1. Make a full backup of your current device in TWRP ! (use it to RESTORE if necessary) DON’T FORGET !
2. Wipe cache / dalvik / data / system
3. Install but do not boot : A2017 V2.0 B13 AROMA MiFavor 5.0 SL!M DF!NR : https://androidfilehost.com/?fid=673791459329066042
3a When ready in aroma, DO NOT REBOOT. Stay in TWRP and go to (4)
4. CHOOSE ! : 4a or 4b
4a. Install : bootstack B13 FIX 2 when coming from another rom : https://androidfilehost.com/?fid=745849072291693516
GOTO (5)
4b. Install : bootstack Universal B15 “adapted 3.1.1.0” when already on a MiFavor 5.0 rom
https://androidfilehost.com/?fid=673791459329066038
GOTO (5)
5. Install : MODEM (G) : https://androidfilehost.com/?fid=962021903579492190
( flash modem for A2017U model : https://androidfilehost.com/?fid=817550096634745612 )
( flash modem for A2017 model : https://androidfilehost.com/?fid=457095661767137840 )
6. REBOOT :
6a When you were already on a MiFavor rom ( and of course did 4b ), you’ll normaly have a clean (double) boot
6b When you came from another rom ( and did 4a ), your phone will power off (3 red led). Don’t reboot ! Hold power+vol+ to enter back into twrp. Just flash B15 adapted (4b) with TWRP3.1.1.0 and reboot. No need to flash TWRP3.1.1.0 again. You’ll have a clean boot too.
6c. Once booted : When you’ve chosen JoJoc tweak AND Magisk togheter, go back in TWRP and install this installer for Jojoc Magisk. It enables just the script : https://androidfilehost.com/?fid=889964283620770880 (Jojoc+SuperSU : no need to do anything extra)
7. IMPORTANT ! Follow steps !
7a. setup WIFI/data
7b. go into SuperSU or Magisk and check if all ok
7c. tap ADAWAY and give permissions
7d. see if the JoJoc Battery tweak has enabled with the proper values (https://forum.xda-developers.com/showpost.php?p=74752134&postcount=39)
7e. tap addless youtube app. You’ll be asked to log in and update google services ! Do so and wait.
7f. tap google playstore, settings/disable autoupdates
7g. go to google services ( even if you’re on the latest 11.9.51 (440-177350961) or 11.7.46 (440-175121617)) Uninstall ! Reboot, go into youtube app again and update services AGAIN ! YEP !
7h. try an app like google maps(enable gps and get a fix), hangouts or chrome and you’ll normaly see that force closes should be gone !
Everything is working as far as i can see...
INFO :
AROMA Features to choose from :
Debloat almost all remaining apps
Choose SuperSU 2.82 or Magisk14.0 (safetynet asure)
Add Google Dialer
Add Google Keyboard, Touchpal (activate in settings)
Double tap to camera
JoJoc Battery tweak ( gave me 8.30h SOT with this rom ! )
(BXSRVEngine Bravia4, Super-Vivid, X-reality )
.....
Stripped off :
....
Zte clock replaced by Google Clock
Zte calendar replaced by Google Calendar
....
Baked into :
AdAway
Google Calender
Google Clock
YouTube Adfree Black Themed (dont update !)
Minor Modifications :
Boot :
• Init.d enabled
• Dm-verity disabled
Zip aligned apk’s
Build.prop tweaks : (remove them in system/build.prop if not needed)
• Improved performance
• Faster boot
• Phone rings immediately
• Wifi scan interval 180sec
• Better call voice quality
• Better network signal
Added sounds LOS
Faster UI (thanks ADM)
Magisk 14.0 (more stable to safetynet imo)
SuperSU 2.82
Busybox 1.27.2
Hope you'll E N J O Y !!!
Contributors :
me, myself and I
Credits :
@_alexndr
@amarullz
@SuperR.
@bkores (for our work together on DoubleTapCamera , thnx !)
@Plamb1r (BXRSV Engine)
@nfsmw_gr (for our work together on his JoJoc tweak , thnx !)
@joaste ( testing/follow up – Big Thnx !)
@Ayush Singh
@ZaneZam (iYTB Thnx !)
@Chainfire
@topjohnwu
@jcadduono
@Didgeridoohan
ROM OS Version : 7.1.1 Nougat MiFavor 5.0 (chinese)
Source : ZTE stock-rom A2017UV2.0.0B13 / original ZTE upload/reuploaded : https://androidfilehost.com/?fid=889764386195932870
Kernel : stock
Version Information :
Status : Stable
Created : 2017-12-04
Release : 2017-12-08
Lookin' great man, congrats.
nfsmw_gr said:
Lookin' great man, congrats.
Click to expand...
Click to collapse
Yeah, hope so. And hope they'll enjoy your JoJoc tweak as i do for my battery :good:
Thank you Very much, will Flash this Later
Lycidias said:
Thank you Very much, will Flash this Later
Click to expand...
Click to collapse
When flashed do update on battery usage - SOT, force closes. Thnx !
Hi !
Thx for this ROM.
Out of couriosity I installed this ROM (exactly followed the instructions).
Even if it's good looking I have problems with this ROM. Some of the applications simply don't start.
e.g. google play games hangs on start screen. as well as google maps.
Any ideas, what's wrong or going on?
No more experiances with this ROM yes, as I just installed it
regards
flushbeer said:
Hi !
Out of couriosity I installed this ROM (exactly followed the instructions).
Even if it's good looking I have problems with this ROM. Some of the applications simply don't start.
e.g. google play games hangs on start screen. Even phone restart hangs so that the phone cannot be rebooted.
Any ideas, what's wrong or going on?
No more experiances with this ROM yes, as I just installed it
regards
Click to expand...
Click to collapse
Thnx for feedback.
We've tested play games too (like maps, chrome, hangouts...) and had no issues at all. As a matter of fact I tested them all working together, opening closing opening and so on, no problems.
What about your boot is strange. Did you install B15 adapted as described? We had no issues booting.
Perhaps wipe all again and redo because this sounds weird.
Which model and Rom were you on?
PS : did you deinstall / reinstalled services like described?
flushbeer said:
Hi !
Thx for this ROM.
Out of couriosity I installed this ROM (exactly followed the instructions).
Even if it's good looking I have problems with this ROM. Some of the applications simply don't start.
e.g. google play games hangs on start screen. as well as google maps.
Any ideas, what's wrong or going on?
No more experiances with this ROM yes, as I just installed it
regards
Click to expand...
Click to collapse
I agree with raystef66. I would restart from scratch.
Start by making sure you're on twrp 3.1.1, that system is mounted. Wipe system, data cache and dalvik (internal storage is not necessary).
Try installing the b13 bootsack file first, then reboot recovery.
Install the b15 fix2 file and reboot recovery.
Install the ROM and reboot.
Hi !
Thx for your feedback (both of you).
boot is ok (no idea what happened)
google maps: it starts, but it seems that it takes ages after a reboot.
play games: still does not start.
I installed exactly like joaste desribed, but I will try again.
thx
regards
flushbeer said:
Hi !
Thx for your feedback (both of you).
boot is ok (no idea what happened)
google maps: it starts, but it seems that it takes ages after a reboot.
play games: still does not start.
I installed exactly like joaste desribed, but I will try again.
thx
regards
Click to expand...
Click to collapse
Did you disable play services and re enable it?
Once done and play services has been updated, go to settings, apps, maps and clear cache and data then open maps.
What happens?
flushbeer said:
Hi !
Thx for your feedback (both of you).
boot is ok (no idea what happened)
google maps: it starts, but it seems that it takes ages after a reboot.
play games: still does not start.
I installed exactly like joaste desribed, but I will try again.
thx
regards
Click to expand...
Click to collapse
Sure. As we have the same phone all should work. At the moment I've all those app installed and running. And no hitches. I'm on supersu.
BTW, this morning started with 100 % battery, after 1h SOT, still on 88%. With full use of phone, on wifi, 4g. So like said, the jojoc tweak does its work for me. Never had above average of 5h, now always above 7.30 depending use.
EDIT : 2h SOT still 78% :cyclops:
flushbeer said:
Hi !
Thx for your feedback (both of you).
boot is ok (no idea what happened)
google maps: it starts, but it seems that it takes ages after a reboot.
play games: still does not start.
I installed exactly like joaste desribed, but I will try again.
thx
regards
Click to expand...
Click to collapse
Check if you have anything frozen or disabled and restore them to their normal state.
Also go to play store and make sure everything is updated.
The notify flash option in settings force closes
Raffikie said:
The notify flash option in settings force closes
Click to expand...
Click to collapse
Have checked these options again but no fc's there....dont see why btw.
As said, i'm days on this version now and all ok. No fc's, sync ok and so on.
In previous version i had some fc's too from time to time, but with this one imo all is ok.
Important : follow all procedure, check permissions, deinstall existing services and reinstall services till you get latest 11.9.51 (440-177350961)
Also don't forget the B15 adapted...
Should be all running ok.
Perhaps some other users (50 downloads now over one night ) can give feedback too as we're interested :good:
BTW : as i see the ROM download is almost double as for the new B13 fix2 and B15 adapted...i can imagine some things go wrong, so download all files....and use them...
Hey
I installed it and everything as good as it should.
It took some time to set itself, but now is well.
I got the G version and it was installed flawlessly.
But I must confirm that notice flash crashes here as well. But I don't care 'cause I don't know what it is for :angel:
Sent from my ZTE A2017U using XDA Labs
Orlando.Rodriguez said:
Hey
I installed it and everything as good as it should.
It took some time to set itself, but now is well.
I got the G version and it was installed flawlessly.
But I must confirm that notice flash crashes here as well. But I don't care 'cause I don't know what it is for :angel:
Sent from my ZTE A2017U using XDA Labs
Click to expand...
Click to collapse
Thnx for your feedback ! Much appreciated :good:
Btw, now on 3h05 SOT already and 60% left
Raffikie said:
The notify flash option in settings force closes
Click to expand...
Click to collapse
Orlando.Rodriguez said:
Hey
I installed it and everything as good as it should.
It took some time to set itself, but now is well.
I got the G version and it was installed flawlessly.
But I must confirm that notice flash crashes here as well. But I don't care 'cause I don't know what it is for :angel:
Sent from my ZTE A2017U using XDA Labs
Click to expand...
Click to collapse
OK, now i understand. I thought you were mentioning the notifications under settings.
But indeed the "notice flash" under advanced settings was some feature in previous version, but in russian and i left it out.
I was just an app that did make your flash go off when a notification came in.
But as said, it was in russian and imo : useless.
update:
I went through the installation procedure again, now everything seems to run fine. I have no idea what happened after the first install.
No force closes yet (but didn't check notice flash)
I cannot report on screen on time because phone ist not running long enough with this ROM.
thx
regards
flushbeer said:
update:
I went through the installation procedure again, now everything seems to run fine. I have no idea what happened after the first install.
No force closes yet (but didn't check notice flash)
I cannot report on screen on time because phone ist not running long enough with this ROM.
thx
regards
Click to expand...
Click to collapse
Ok nice to know ! :good:
The notice flash was an app in russian and rather useless imo and left it out. Still in settings though but then again not that important.
Hello,
Im having some trouble disabling the on-screen buttons through build.prop, I already disabled disemmcwp via ADB on a PC and from an terminal emulator app. It reboots and I stillt reverts my build.prop.
And clues on how to fix this?
sincerely, me
Requirements :-
1. Rooted phone with Magisk installed.
2. Xposed framework (install 'busybox' module --reboot-- install 'riru core' module --reboot-- install 'riru edxposed sandhook' module --reboot--) & later install the 'edexposed manager' apk.
3. Magisk modules - 1. Debloter 2. Bromite Systemless Webview (optional but recommended)
4. Greenify app (full version i.e. donation package)
5. Swift Installer
Note - Please reboot after each magisk module is installed. If rebooting after multiple module installed at once phone may stuck on bootloop.
Steps -
Kernel Adiutor
1. Install FKM (Franko kernel manager) - go to the app ->
click on CPU tab ->
For 'Big Cores' set maximum frequency to 2169 Mhz ->
later set CPU governor to 'powersave' only for 'Big Cores -> toggle the option to 'on'.
Thats it, leave the 'little cores' as it is. -> REBOOT
2. Ater the FKM settings has been applied, install the 'Kernel Adiutor' app ->
click the 3 lines options from the top left screen ->
Click on 'CPU' tab -> For 'Big Cores' set maximum frequency to 2169 Mhz ->
set CPU governor to 'powersave' only for 'Big Cores ->
set CPU governor to 'schedutil' for 'little Cores'. turn on 'Apply on boot' option.
3. Now go to the 'GPU' tab from 3 lines menu -> set CPU governor to msm-adreno-tz' ->turn on 'Apply on boot' option.
4. Now go to the 'Low memory killer' tab from 3 lines menu -> click once on 'very light' -> turn on 'Apply on boot' option.
5. Uninstall the FKM app. REBOOT.
Debloat
Warning : For this please keep ready the LGUP tool and proper .kdz file for your device [i repeat do not ignore this]
Here are some of the apps that i debloted using 'debloat' magisk module->
1. Photos
2. Lens
3. Google Play Music
4. Calender (dont debloat if you want to sync it)
5. Chrome
6. Docs
7. Google text-to-speech engine
8. Gmail
9. Duo
10. Slides
11. Sheets
12. Gboard (Google keyboard)
13. Google Play movies
14. Google Maps
15. Google News
16. Facebook App Manager
17. Facebook App Installer
18. Youtube (If you debloat it, it wont run, it needs system access. Since i used Youtube Vanced i dont care)
Until this after rebooting all worked well.
But After debloating '19. Google' and rebooting my phone, it bootlooped. Thus, I have to LGUP and select the 'upgrade' option and flash the stock again and it worked fine and i successfully debloated the 'Google' app too. This is the main battery culprit. Or you you can just disable it. see if it works for you or not.
Note :- Debloat doesn't mean uninstalling, it means converting system apps to normal apps just opposite what the 'Sytemizer' magisk module does.
Greenify
1. install the greenify app (full version needed) -> then go to the Edxposed Manager -> click on 3 line menu -> click on module -> turn on 'greenify' -> REBOOT.
2. Open Greenify app -> Give it all the permissions needed -> now to go the setting from the 3 dots menu -> It should be showing working mode 'Root + Boost (Xposed)'.
3. Smart Hibernation = Enabled; Aggressive Doze = Enabled; Wake-up tracking and cut-off = Enabled; Automatic Hibernation = select it; Always ignore backgrounf free = select it.
4. Now click on Xposed-based features -> select each and every options.
5. Reboot the greenify app.
6. Now on the main screen of greenify, click on the 'zzz' icon and select the apps it recommends and most of the apps u dont care much about and click them for sleep just once and never again.
Swift Installer -
1. If you are using substratum please STOP. It drains a hell lot of battery.
2. Use swift installer instead for theming various apps you like.
3. And for system theming any good theme from PlayStore could work.
Major Note :- This isn-t the fool proof method of increasing battery life out of nowhere without losing some performance.
Sure it will, but you will even not notice it and will easily get you through it. Atleast it happens well with me
For Gamers : Just take away the root access from the Kernel Aduitor from Magisk Manager and reboot when you want to play system heavy games.
For All : if you notice any lag which annoys you, please start tweaking the 'Greenify' first rather than going directly after 'Kernel Aduitor'.
Please provide the precious feedback and other tweaks and tricks here to further improve the Battery and Performance of our beloved Phone LGv40.
I will be posting battery backup, SOT proofs stay tuned.
Using of Hotspot Still drains battery like water.
smartybro7788 said:
Requirements :-
1. Rooted phone with Magisk installed.
2. Xposed framework (install 'busybox' module --reboot-- install 'riru core' module --reboot-- install 'riru edxposed sandhook' module --reboot--) & later install the 'edexposed manager' apk.
3. Magisk modules - 1. Debloter 2. Bromite Systemless Webview (optional but recommended)
4. Greenify app (full version i.e. donation package)
5. Swift Installer
Click to expand...
Click to collapse
What system are you on? I'm on UA20a Pie! Will it matter?
smartybro7788 said:
Requirements :-
1. Rooted phone with Magisk installed.
2. Xposed framework (install 'busybox' module --reboot-- install 'riru core' module --reboot-- install 'riru edxposed sandhook' module --reboot--) & later install the 'edexposed manager' apk.
3. Magisk modules - 1. Debloter 2. Bromite Systemless Webview (optional but recommended)
4. Greenify app (full version i.e. donation package)
5. Swift Installer
Note - Please reboot after each magisk module is installed. If rebooting after multiple module installed at once phone may stuck on bootloop.
Steps -
Kernel Adiutor
1. Install FKM (Franko kernel manager) - go to the app ->
click on CPU tab ->
For 'Big Cores' set maximum frequency to 2169 Mhz ->
later set CPU governor to 'powersave' only for 'Big Cores -> toggle the option to 'on'.
Thats it, leave the 'little cores' as it is. -> REBOOT
2. Ater the FKM settings has been applied, install the 'Kernel Adiutor' app ->
click the 3 lines options from the top left screen ->
Click on 'CPU' tab -> For 'Big Cores' set maximum frequency to 2169 Mhz ->
set CPU governor to 'powersave' only for 'Big Cores ->
set CPU governor to 'schedutil' for 'little Cores'. turn on 'Apply on boot' option.
3. Now go to the 'GPU' tab from 3 lines menu -> set CPU governor to msm-adreno-tz' ->turn on 'Apply on boot' option.
4. Now go to the 'Low memory killer' tab from 3 lines menu -> click once on 'very light' -> turn on 'Apply on boot' option.
5. Uninstall the FKM app. REBOOT.
Debloat
Warning : For this please keep ready the LGUP tool and proper .kdz file for your device [i repeat do not ignore this]
Here are some of the apps that i debloted using 'debloat' magisk module->
1. Photos
2. Lens
3. Google Play Music
4. Calender (dont debloat if you want to sync it)
5. Chrome
6. Docs
7. Google text-to-speech engine
8. Gmail
9. Duo
10. Slides
11. Sheets
12. Gboard (Google keyboard)
13. Google Play movies
14. Google Maps
15. Google News
16. Facebook App Manager
17. Facebook App Installer
18. Youtube (If you debloat it, it wont run, it needs system access. Since i used Youtube Vanced i dont care)
Until this after rebooting all worked well.
But After debloating '19. Google' and rebooting my phone, it bootlooped. Thus, I have to LGUP and select the 'upgrade' option and flash the stock again and it worked fine and i successfully debloated the 'Google' app too. This is the main battery culprit. Or you you can just disable it. see if it works for you or not.
Note :- Debloat doesn't mean uninstalling, it means converting system apps to normal apps just opposite what the 'Sytemizer' magisk module does.
Greenify
1. install the greenify app (full version needed) -> then go to the Edxposed Manager -> click on 3 line menu -> click on module -> turn on 'greenify' -> REBOOT.
2. Open Greenify app -> Give it all the permissions needed -> now to go the setting from the 3 dots menu -> It should be showing working mode 'Root + Boost (Xposed)'.
3. Smart Hibernation = Enabled; Aggressive Doze = Enabled; Wake-up tracking and cut-off = Enabled; Automatic Hibernation = select it; Always ignore backgrounf free = select it.
4. Now click on Xposed-based features -> select each and every options.
5. Reboot the greenify app.
6. Now on the main screen of greenify, click on the 'zzz' icon and select the apps it recommends and most of the apps u dont care much about and click them for sleep just once and never again.
Swift Installer -
1. If you are using substratum please STOP. It drains a hell lot of battery.
2. Use swift installer instead for theming various apps you like.
3. And for system theming any good theme from PlayStore could work.
Major Note :- This isn-t the fool proof method of increasing battery life out of nowhere without losing some performance.
Sure it will, but you will even not notice it and will easily get you through it. Atleast it happens well with me
For Gamers : Just take away the root access from the Kernel Aduitor from Magisk Manager and reboot when you want to play system heavy games.
For All : if you notice any lag which annoys you, please start tweaking the 'Greenify' first rather than going directly after 'Kernel Aduitor'.
Please provide the precious feedback and other tweaks and tricks here to further improve the Battery and Performance of our beloved Phone LGv40.
I will be posting battery backup, SOT proofs stay tuned.
Click to expand...
Click to collapse
Hey all. To be honest this is the best battery saving guide among others after searching it for so long. I'm using LG V40 V409N with magisk root, of course. I would able to get close to 8 hours of SOT. Followed it to the letter. Two minor differences are my phone didn't boot loop after debloat Google and I'm using Franco Kernel app to substitute Kernel Adiutor. I'm satisfied with the result. I used to get only 3 to 4 hours of SOT. So increment of double the SOT is awesomely welcome.
I tried it with Oneplus Nord that my wife is currently using and can get 7 hours SOT with it. That is way better than 4 hours of SOT before. One thing is clear, this guide is working. Solute to smatybro7788 that make this guide. And thank you.
Battery has been my concern with this phone. Rom is not stable after root and crossflash i noticed that after a while you will start to see screen flickers here where battery consumption going crazy a factory reset will put things back to normal till screen flickers again.I am not an expert i know a little i discovered that if i go to maximum power saver phone go easy on battery magically (whyyyy) that's why this tutorial is aiming to address this issue thank you.