Related
Hey guys, I'm currently running CM6, and when I tried to upgrade to CM7, from the version with overclocking and undervolting added, my fone always reboot and lag continously, unusable until i restore using factory reset.It never happened with any previous version of CM7. A couple day back, I tried the overclocking tweak for CM6, and the same thing happens. I have to restore using Xrecovery. Does anyone knows what the problem is ? I really want overclocking function
stable overclocking is 768 or less.... this much i knw some dev will help you
You did say that you used the overclocking patch , but did not tell did you use SetCPU with set on boot option ? Also what is ur max and min settings in setcpu ?
Anyways , not sure if you will now be able to go inside setcpu , since ur phone is restarting.
On mini pro , for me 780+ Mhz caused reboot. And if you have setcpu set to set it on each boot , then u will end up in infinite loop. For me it happened , but luckily if you do not touch ur phone (touch screen touch ;-) ) after a reboot , it wont reboot (atleast for me).;
So after a reboot :
1. connect phone to PC
2. use adb to uninstall the setcpu
3. reboot again.
This time you should not be having trouble as your phone should behave normally.
Again install setCPU (if you are interested still !!) and set the max to anything below 760Mhz.
What should we do if there is the reboot loop but setcpu is already uninstalled? Or if its installed but overclock is not set on boot?
Hey thanks for the help, but I can't do anything at all with the phone after the patch, with or without setcpu. It booted up, on lockscreen, lag for 30sec and continous reboot then -.-''
Sent from my U20i using XDA Premium App
will make much more sense letting people know what you have done. Just the normal OC module should not have ur phone rebooting.
Does the phone reboot if you do not touch it but just keep it connected to PC ? please answer or else its very hard to try and figure out an answer.
if you feel its causing an issue , then u got to figure out a way to disable that module.
The module gets loaded as x8oc.ko.
In CM6 - v4 , this is not there by default but will appear in hw_config.sh if you have patched it.
So u got to get /system/etc/hw_config.sh and comment out the line insmod for x8oc.ko and anything associate with it .
Did fresh install of v4 after factory reset, resulted in no overclock options and completely stable. Installed oc zip from cm6 oc thread which resulted in infinite reboots even when attached to pc, was not able to touch any settings. Reflashed v4 without factory reset and am back to no overclock and completely stable. Setcpu was not installed, recently installed on fresh v4, no options beyond 600mhz.
yep ..if u did a fresh install of v4 , it means the overclock is not functional as the module is not loaded in it.
Changelog for v4 says overclocked and undervolted, but never mind that. Installing oclock.zip as per instructions in that thread results in infinite reboot, does not stay up long enough to use adb shell or access setcpu. The fresh install of v4 does have overclock options in cyanogenmod settings, but values cannot be edited.
Are you implying that v4 will not support the oclock.zip or simply replying only to first sentence of explanation?
Any help is appreciated.
ok . so let me explain ( i know its quite hard on both ways ) . The overclock module (x80c.ko) is NOT loaded by the default V4 version. So if the module is not loaded Cyanogen setting will only show you the max (600 Mhz i thnk) and min (122 Mhz - I think). I did not find that module to be loaded in any of the init* scripts or in hw_config.sh. But the module is present with the build in the modules folder (but not active as its not loaded with insmod).
So if you just coming just after applying V4 - with no other patch. Then you do not have active overlocking module - hence overclocking wont work with SetCPU. Cyanogen does NOT provide you a scope to change the frequencies - you need setCPU - (you can change the max thru command line after enabling the module).
Now if you have patched the same with the oc patch , you have the module active (insmod works) , but another line of it in the hw_config.sh (patched one) does not become effective for me (some people reported it worked for them though).
The constant reboot which i faced was because i (with the help of SetCPU) had set very high frequency (causing the system to become unstable).
So inorder to fix it , you can do the following:
1. Full wipe through xrecovery
2. Apply V4 again.
3. Change hw_config.sh to add the insmod command to load x8oc.ko module.
4. Reinstall setcpu and see if you can set the max/min to safe values (say around 719 Mhz max and min as 300 or 400 Mhz).
5. If you see the system to be stable , well and good.
If by above , setCPU does not detect max/min (max should be 825 Mhz) , then you need to add the echo x27 > /proc/x8oc to hw_config just after the insmod line of x8oc.ko. (you will see some threads where sleep 2 or sleep 4 is also asked to be put in , but for unknown reason it did not work for me).
Whew!! that was long . But thats the way it worked for me.
For me when the reboots were happening , i had my phone connected to PC , but i was not touching the phone at all (if i touch , it used to reboot - but adb shell was working if i do not touch it).
If any further clarificaiton required , i would be glad to assist.
But before puting in a query , please try and give as much information was to what you did after which the reboots started (not just saying that i did the OC patch - cos for me just the OC patch never resulted into the reboots).
Thank you for that awesome explanation and sorry for the lack of relevant information earlier in the thread.
Should be able to do as you have suggested when I get home and will report back, either way your explanation has made it all clear and I can see where I have missed important steps. Many thanks.
Edit: edited hw config.sh, inserted insmod, sleep and echo lines. Stable ay 729, reboots at 748. Thanks again
good to know it worked !
same problem with my minni.... reboot again and again
Check your baseband, it must be xxx15 or it won't work because of different kernel
Nah got everything rite, basband and kernel, just when I apply the OC tweak, the fone would boot up, but freeze at lockscreen. IT DOES BOOT UP, BUT STUCK AT LOCKSCREEN !!! So bloody annoying, then stuck on bootloop until restore /system using xrecovery
Sent from my U20i using XDA Premium App
Don't apply the oversclock tweak from xrecovery, instead try editing hw_config.sh to have:
# x8 overclock
insmod /system/lib/modules/x8oc.ko
sleep 2
echo x27 > /proc/x8oc
I believe i had the same issue until i did this, then it was stable.
my mini max cpu is only 691 mhz or else the reboots and its laggy as hell. LIKE all your work every wear
have your lovely MDDI on to it help alot but still scrolling lag. maybe fresh install via seus?
wrong thread
i'm running virtuous unity ROM on my htc inspire 4g. i'm trying to underclock my phone to save battery. i read info on this from this webpage on xda:
http://forum.xda-developers.com/showpost.php?p=14529333&postcount=5
in the 'wake governor' file, its originally set to 'ondemand'. i'd like to edit it to save battery, but not to kill too much smooth performance. below are the options given. can you please rank the the following in terms of performance and battery life? and which is the best for my needs?
- SavagedZen
- Scary
- smartass
- interactive
- conservative
- userspace
- ondemand
- performance
.
There's now smartass v2, has all the benefits of smartass(no set cpu required, v. quick swiych of freq. after screen on/boot) but also v. stable. It's built in to my custom kernel (xperi arc) but google it
sinkster
sinkster said:
There's now smartass v2, has all the benefits of smartass(no set cpu required, v. quick swiych of freq. after screen on/boot) but also v. stable. It's built in to my custom kernel (xperi arc) but google it
sinkster
Click to expand...
Click to collapse
hi, sinkster.. thanks for the reply. but i really dont know what these terms mean. can you tell me what ranking they have on a scale from 1 to 10 in terms of battery life and also in terms of perfomance?
this is importsnt for me to decide what to set my phone at. especially when i want to save battery but at the same time, not sacrifice performance. thanks.
trapzz said:
hi, sinkster.. thanks for the reply. but i really dont know what these terms mean. can you tell me what ranking they have on a scale from 1 to 10 in terms of battery life and also in terms of perfomance?
this is importsnt for me to decide what to set my phone at. especially when i want to save battery but at the same time, not sacrifice performance. thanks.
Click to expand...
Click to collapse
The rom your running has its own custom kernel, which still only has the original smartass governor, which the thread you posted a link to talks about the flaws of it and came up with their own solution to bypass those flaws. There is a newer version of the smartass governor that fixes those flaws, so you dont have to manually edit the files that the thread is talking about doing, like your trying to do. In order to get the new version of the smartass governor, the developer of the kernel that your rom's dev. is using has to update it (i would recommend searching the forum for the original thread of the kernel). Or you could find another kernel that will work with your current rom but is also updated that includes the new smartass governor. As for the differences of the profiles, Smartass seems to be the most complex but best option for saving alot of battery while not affecting performance of the phone. It saves battery while the screen is off, and when the phone doesnt need to use its cpu fully. It basically learns and throttles between the cpu frequencies you have set based on phone usage while always using the bare minimum frequency while the screen is off and when no applications are being used and a higher/highest frequency you have set for when your using applications so they still run smooth. I would recommend getting Setcpu, it will detect what frequencies your phone is capable of and will allow you to set the smartass governor and the min/max frequencies for it to throttle between. I would also search your Rom's thread and the Kernel's thread(if there is one) to see what the min/max frequency people are having pleasant experiences with.
Synergies14 said:
The rom your running has its own custom kernel, which still only has the original smartass governor, which the thread you posted a link to talks about the flaws of it and came up with their own solution to bypass those flaws. There is a newer version of the smartass governor that fixes those flaws, so you dont have to manually edit the files that the thread is talking about doing, like your trying to do. In order to get the new version of the smartass governor, the developer of the kernel that your rom's dev. is using has to update it (i would recommend searching the forum for the original thread of the kernel). Or you could find another kernel that will work with your current rom but is also updated that includes the new smartass governor. As for the differences of the profiles, Smartass seems to be the most complex but best option for saving alot of battery while not affecting performance of the phone. It saves battery while the screen is off, and when the phone doesnt need to use its cpu fully. It basically learns and throttles between the cpu frequencies you have set based on phone usage while always using the bare minimum frequency while the screen is off and when no applications are being used and a higher/highest frequency you have set for when your using applications so they still run smooth. I would recommend getting Setcpu, it will detect what frequencies your phone is capable of and will allow you to set the smartass governor and the min/max frequencies for it to throttle between. I would also search your Rom's thread and the Kernel's thread(if there is one) to see what the min/max frequency people are having pleasant experiences with.
Click to expand...
Click to collapse
hi, Synergies14.. i truly do appreciate your in depth info. i got 3 questions:
1) you suggested i use 'smartass' as the best option to save battery life. but dont you think that this option sounds like a battery draining option?
2) you suggest i use smartass as the best option for increasing battery life. i set 'smartass' as the option for wake governor. should i also apply it to sleep governor? the sleep governor is currently set to conservative. let me know.
3) can you explain rank each of the 8 terms in terms of battery life and perfomance?
thank you. i appreciate it.
trapzz said:
hi, Synergies14.. i truly do appreciate your in depth info. i got 3 questions:
1) you suggested i use 'smartass' as the best option to save battery life. but dont you think that this option sounds like a battery draining option?
2) you suggest i use smartass as the best option for increasing battery life. i set 'smartass' as the option for wake governor. should i also apply it to sleep governor? the sleep governor is currently set to conservative. let me know.
3) can you explain rank each of the 8 terms in terms of battery life and perfomance?
thank you. i appreciate it.
Click to expand...
Click to collapse
Trapzz, my apologies for not responding to your post back on the 17th. As to question 1, the answer is no. The smartass governor throttles your cpu frequency based on the min/max frequencies you have set in Setcpu for when the screen is off, even if the screen is on and your not using any performance hog apps. The smartass governor is alot better at throttling between the frequencies than any of the other governors. For example, while your screen is off, it will have the cpu using the minimum frequency, even if the screen is on and your looking at text messages, it will only raise the frequency untill the text messages load and then it will scale back down after its done loading. Other governors keep the frequency raised the whole time your in your text messages, even after its loaded, untill you exit it and turn the screen off.
As for question 2, you shouldnt have any profiles set while using the smartass governor, as how the smartass governor works, you dont need any profiles set. Smartass takes care of it all on its own.
As for question 3, im not exactly sure how to rank each governor based on performance/battery life besides other than conservative is used for battery life, and performance is for performance and not saving battery. But with how smartass works, its auto scales the frequencies automatically. Its the best for saving battery, but its also best for performance as it scales to the highest frequency you have set and keeps it there for as long as your app needs it.
Hope i helped answer what you were asking! If you need anything else or any other questions feel free to reply or shoot me a personal message.
Sent from my Mik'd Supersonic OG Evo using xda premium
Synergies14 said:
Trapzz, my apologies for not responding to your post back on the 17th.
As for question 2, you shouldnt have any profiles set while using the smartass governor, as how the smartass governor works, you dont need any profiles set. Smartass takes care of it all on its own.
Click to expand...
Click to collapse
hi, Synergies14.. thanks for getting back to me.. no need to apologize, but thanks anyway.
you said that i shouldnt set any profile while using the smartass governor. i'm a bit confused. what exactly do you mean? do you mean that i shouldnt enter any values for the 3 wake and sleep states?
and do you also mean that i shouldnt set 'smartass' for sleep governor?
trapzz said:
hi, Synergies14.. thanks for getting back to me.. no need to apologize, but thanks anyway.
you said that i shouldnt set any profile while using the smartass governor. i'm a bit confused. what exactly do you mean? do you mean that i shouldnt enter any values for the 3 wake and sleep states?
and do you also mean that i shouldnt set 'smartass' for sleep governor?
Click to expand...
Click to collapse
You are running Setcpu, correct?
Sent from my PC36100 using xda premium
My apologies, it seems that your not, your actually manually editing files for it. I dont have access to a computer right now but i will soon and i will help you futher.
Sent from my PC36100 using xda premium
---------- Post added at 10:27 PM ---------- Previous post was at 09:33 PM ----------
trapzz said:
hi, Synergies14.. thanks for getting back to me.. no need to apologize, but thanks anyway.
you said that i shouldnt set any profile while using the smartass governor. i'm a bit confused. what exactly do you mean? do you mean that i shouldnt enter any values for the 3 wake and sleep states?
and do you also mean that i shouldnt set 'smartass' for sleep governor?
Click to expand...
Click to collapse
Alright, i apologize, i got a bit confused myself there. Judging from your Rom and what the Devs of it say, DO NOT install setcpu like i have mentioned. You will need to install a terminal app. You can go to the market and search for the app "Android Terminal Emulator" and install it. Then in the terminal app, type in "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors" (without the quotation marks) and that will give you a list of available governors to use. Tell me the list of governors it gives you. Then type in "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies". That will tell you the available Min/Max frequencies that your phone will allow. Tell me the list of frequencies that it gives you. Then i shall help you from there after providing that info to me.
A better option would be to undervolt by 25mv a time if ur kernel supports it
Synergies14 said:
You will need to install a terminal app. You can go to the market and search for the app "Android Terminal Emulator" and install it. Then in the terminal app, type in "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors" (without the quotation marks) and that will give you a list of available governors to use. Tell me the list of governors it gives you. Then type in "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies". That will tell you the available Min/Max frequencies that your phone will allow. Tell me the list of frequencies that it gives you. Then i shall help you from there after providing that info to me.
Click to expand...
Click to collapse
hi synergies.. below are the available governors and frequencies on my phone:
governors:
SavagedZen
Scary
smartass
interactive
conservative
userspace
ondemand
performance
freqs:
245760 368640 768000 1024000 825600 844800 864000 883200 902400 921600 940800 960000 979200 998400 1017600 1036800 1056000 1075200 1094400 1113600 1132800 1152000 1171200 1190400 1209600 1228800 1248000 1267200 1286400 1305600 1324800 1344000 1363200 1382400 1401600 1420800 1440000 1459200 1478400 1497600 1516800 1536000 1555200 1574400 1593600 1612800 1632000 1651200 1670400 1689600 1708800
Actually can you update your Rom first? if you haven't updated it, there is an update for it that came out a few days ago, before we do anything i want to make sure you have the latest piece of the software.(updating might actually help with the call vibration issue your having too). If you update it, tell me if you have a custom kernel installed or if you leave it with the stock kernel that the rom uses. The type of kernel you use will affect your available frequencies and also if everything is outdated. After you update your Rom, look to see if there is a program on there called "Daemon Controller". If not, then follow this link http://bit.ly/oDeBtV and install the .apk on your phone. This is the new graphical UI for changing and managing your virtuous_oc so you dont have to manually edit the files yourself.
Synergies14 said:
Actually can you update your Rom first? if you haven't updated it, there is an update for it that came out a few days ago, before we do anything i want to make sure you have the latest piece of the software.(updating might actually help with the call vibration issue your having too). If you update it, tell me if you have a custom kernel installed or if you leave it with the stock kernel that the rom uses. The type of kernel you use will affect your available frequencies and also if everything is outdated. After you update your Rom, look to see if there is a program on there called "Daemon Controller". If not, then follow this link http://bit.ly/oDeBtV and install the .apk on your phone. This is the new graphical UI for changing and managing your virtuous_oc so you dont have to manually edit the files yourself.
Click to expand...
Click to collapse
hi synergies. the problem with the update to my rom (virtuous unity), is that its got some issues. but i'll install it. and hopefully i wont experience the same issues.
one other important thing.. how do i do a EXT4 wipe?
.
trapzz said:
hi synergies. the problem with the update to my rom (virtuous unity), is that its got some issues. but i'll install it. and hopefully i wont experience the same issues.
one other important thing.. how do i do a EXT4 wipe?
.
Click to expand...
Click to collapse
I recommend doing a full nand backup before upgrading so that way if you do run into any issues that you dont like, you can just restore from that nand backup. What Recovery are you using?
Synergies14 said:
I recommend doing a full nand backup before upgrading so that way if you do run into any issues that you dont like, you can just restore from that nand backup. What Recovery are you using?
Click to expand...
Click to collapse
hi synergies.. i'm backing up through booting into recovery.
trapzz said:
hi synergies.. i'm backing up through booting into recovery.
Click to expand...
Click to collapse
Thats good. I need to know what recovery your using so i can help you with doing a ext4 wipe.
Synergies14 said:
Thats good. I need to know what recovery your using so i can help you with doing a ext4 wipe.
Click to expand...
Click to collapse
hi synergies.. i dont understand your question. the recovery i use is the one rooted users use... i boot into recovery and choose backup and restore and then backup my phone.
trapzz said:
hi synergies.. i dont understand your question. the recovery i use is the one rooted users use... i boot into recovery and choose backup and restore and then backup my phone.
Click to expand...
Click to collapse
There are different types of recovery that have different names, when u boot into your recovery it should tell you the name and version of the recovery your using
Sent from my Blazed out OG Evo using xda premium app.
Synergies14 said:
There are different types of recovery that have different names, when u boot into your recovery it should tell you the name and version of the recovery your using
Click to expand...
Click to collapse
hi, synergies. i got clockworkmod revovery v3.0.2.5.
trapzz said:
hi, synergies. i got clockworkmod revovery v3.0.2.5.
Click to expand...
Click to collapse
Alright, when you boot into recovery, as always, make a nand backup (as you've said you have already). When you wipe, please note that everything will be erased from your phone including all apps and settings, EVERYTHING. Also as a precaution, ALWAYS go into your contacts in your phone and select to export them to your SDcard. Then connect your phone to your computer and copy EVERYTHING thats on your sdcard to your computer (easily make a folder on your desktop, then select everything on your sdcard, copy it and paste it into the folder). This is so that all your contacts and all your pics/videos and your nand backup are backed up on your computer just incase the wiping process does completely wipe your sdcard (i highly doubt your sdcard will be erased, but its always good practice to take extreme caution as accidents do happen). Then copy the new Rom's zip file onto your sdcard.
*Once you have done all this, boot back into your recovery.
*From the main menu, select "wipe data/factory reset".
*Once that is done, select "wipe cache partition".
*Once that is done, select "mounts and storage".
*In that menu, select "format system".
*Once that is done, select "format data".
*Once that is done, select "format cache".
*Then, judging that you have ext4, i assume your sdcard is partitioned and has the ext on it, if you do, then select "format sd-ext".
*Then go back to the main menu.
*Select "advanced".
*Select "wipe dalvik cache".
*Return to the main menu. Now to install the rom!
*Select "install zip from sdcard".
*Select "choose zip from sdcard".
*A list will appear of the files on your sdcard, select the rom's zip from the list.
*It will ask to confirm installing the zip, go ahead and confirm.
*Once it is done installing, you should be back at the main menu, if not, navigate back to the main menu.
*Select "reboot system now" and you should now reboot into the new ROM. If you have any issues during this process with any of the steps let me know!
also, to get your contacts back into your phone, judging that your sdcard wasnt erased, go into your contacts and select to import from sdcard and you should be good to go!.
Hi to all. Hope this is the right section to post this question.
I created an init.d script that change the cpu governor to performance. It worked and it did change the governor.
I did this for my personal use only to speed up the boot and start up. After the boot completes I will then use a 3rd party app that will change governor from performance to ondemand.
My problem is that the 3rd party app cannot change the governor. I have root access, and the app says success when changing governor. When I confirm it using a system info app, it shows that the governor is still performance.
Seems like the script is still running? or loaded in the memory? If so... How to stop or unload a script after it executes?
Hello!
Before proceeding. It is absolutely necessary for you to be on a stable TWRP build (currently 3.0.2-1). Also, you must have already have had decrypted your ENTIRE phone. If your phone bootloops into TWRP, you probably didn't decrypt, and/or didn't flash no-verity properly, or it
could also be that you are on an old TWRP build.
--WiFi calling is fixed. (thanks @lordodin912 . Turned out to be the defconfig after all. Netfilter/netlink )
--Built with the latest -old v6 Uber Toolchain cross-compiler (ubertc 7 is bugged, and latest v6 doesn't boot after compile)
--Kernel optimization flags added in for Uber (thanks @lordodin912 for the info on this)
--Better 3g/4g connectivity. Which should hopefully lead to less polls to satellites, and hopefully reduce battery consumption (May need to upgrade to latest bootloader and radio).
--ConservativeX governor and a few others added in
--ConservativeX is default
--ROM tweaks to init.qcom.post_boot to do the following : ensure min CPU freq is at 307mhz for all cpus, 133mhz for GPU, modified cpu_boost and other tunables for bettery battery usage, other small tweaks.
--GPU gov set to simple_ondemand by default
--Many TCP congestion algorithms enabled, westwood+ is default, and recommended.
--Small tweak to ZEN_DECISION hotplug
More things fixed/tuned
*testing* AutoSMP hotplug added to kernel. (idk wtf it is though--likely not working)
--Force current charge. Ability to override charging rate. Might set to max rate (1500mAh) by default. This means your cable+charge combo will charge as fast as it can.
6.5 will not force wipe, but if you have bugs with wifi calling, texting, or rootswitch freezing, this is an indication you have to do a Factory Reset within recovery.
Wifi calling fixed, sms fixed. No bugs that I can find.
You can turn off WiFi while on a WiFi call also. It will stay connected and switch to 4g. First connection may take up to 10 seconds, but it's just the first time.
Your phone will be very slow for the initial setup. Once you finish setting up your email, and fingerprint and all that, reboot your device.
If you have factory reset, you will need to update Google Assistant, and Google Play Services. Both of those updates can be done from opening Google Assistant. She won't work until these are installed/updated. SafetyNet bypass also requires Google Play Services, so just be sure to have all updates installed from play store.
LG Music is back in. I added back in the LG update center and the weather lockscreen thing, but they doesn't show up. I'll make a separate zip that works later in the future. For now, you can download smartworld and other things from LGs website.
One more thing, once your battery goes down to 10%, your phone will slow down and be as conservative as possible. I don't believe at 10% anyone will be worried about a smooth experience, but rather that their phone can last them enough time (it will!!). The savings is even greater if you enable Battery Saver at 15%.
Here is v6.5--perfected
You don't have to wipe anything.
However, if you get one of the following bugs, you will have to factory reset in recovery:
**Rootswitch disable freezes phone
**SMS dont always send, or won't send with root disabled
**No call connection or sound when calling after disabling wifi
**Literally any other bug
Development for NSS H918 will come to a halt as of 6.5, as I need to make an update for the other carriers. Additionally, IRL will be taking over for a month or two.
========================================================
Sidebar:
Here is the 6.5 kernel. Note : this is not an update for v6.0, this is only a kernel to be used on other ROMs.
v6 info below
(old in from previous update)
v6 NSS ROM has been rebased on the latest build from LG (10j). The kernel for v6 has also been built from source from the 10j sources. If you want the stock source for 10j kernel download it frmo my thread in the dev section. The one release by LG does not work as-is. I had to go through it and fix multiple errors preventing compile.
v6 WILL wipe your phone. All your apps, settings, games, and save states will be erased! This will not wipe your SD card, nor internal storage.
v6 is heavily debloated. ROM size is a mere 1.06 GB.
There is no kernel-only zip for v6, nor will there be.
I am also not releasing a way to flash v6 without wiping. The wipe is intended to clear any corrupted caches and/or other issues.
In v6, everything you need to pass SafetyNet is already included. Just disable root with Rootswitch, and you can play Pokemon Go, use Android Pay, and any other app that uses Google SafetyNet.
This ROM and kernel have been heavily modified for speed, stability, and battery.
I have changed the default CPU governor to Bioshock.
Here are some changes for v6
v6 will wipe your data!
Based off LGs latest build (V10j). Comes with matching kernel from 10j as well.
Kernel optimizations to the cpu. CPU ramps down quicker, is more conservative (probably best if you leave CPU settings as they come).
Cancun and triton disabled. Triton removed entirely.
Core Control Helper disabled.
New governors have been added! The default governor is now Bioshock.
You have a choice from ElementalX, Despair, Darkness, Alucard, Wheatley, blu_active, uhh prob 1 or 2 others. Note that not all governors are optimized for this chipset and may cause high CPU usage. Bioshock and blu_active work great! Note that the Darkness driver is outdated. Alucard24 did update it a few days ago, but for now, I don't recommend the Darkness driver.
V6 WILL WIPE YOUR PHONE EVERY TIME YOU FLASH IT!
This new version is going to WIPE your PHONE! This means that your apps, save states for games, games, and custom settings will be deleted.
You can backup your call logs and text+mms messages. My favorite app is called SMS Backup and Restore (by Carbonite).
If you have games and/or apps that you have to backup, you can use Titanium Backup. DO NOT BACKUP SYSTEM APPS! Basically if the app is not white in the Titanium Backup list, do not back it up. If it is green, or red, do not back it up, and certainly don't restore it on the new ROM!!!
ROM is much smaller now. ZIP is only 1.06GB. Lots more stuff ripped out of it. Shouldn't download new stock updates either. Will post a full debloat list tomorrow. No features were harmed in the making of this ROM.
I personally prefer to just use Google Assistant for pretty much everything, including Weather and Weather notifications. So the LG Weather has been removed.
I have 2 rebloat zips.
The LG only zip restores LG Weather, LE QMemoPlus (quickcapture), LG Music, and LG Update center.
The full rebloat zip restores everything minus carrier spyware, and lookout. I do not recommend flashing the full rebloat zip, and if you must, be sure to open the ZIP and delete anything out of it you do not specifically want to re-add. Don't flash the whole 450MB zip just to get LG Backup or something like that.
Phone likes to sleep, sometimes it goes hours without dropping 1%... It's weird... Idk .
Remember, if you don't use NFC, turn it off and save a little extra battery.
Also, phone does not have OK Google....
It only has Google Assistant . She is really awesome! It does not identify as a Pixel either.
Here is the link to v6. It will wipe your phone any time that you flash it! Note that the .ZIP says (fixed). This is because it already includes the fix for WiFi calling, SMS, and hotspot. I used some of the active members as guinea pigs, sue me
So once you flash your phone, just wait... It will take a long time. Once it boots, it will ask for your SIM card. Just wait a minute, and it will come on.
Go through the initial setup, make sure to give Color Control and Rootswitch SU access when prompted (will be really early, if you miss it just open SuperSU app and force grant permission).
Once you finish initial setup with fingerprint and all that stuff let it download whatever Google Play apps it finds, then get to your home screen and reboot the phone to complete setup.
Note, you must manually install Google Play Services. If you hold your Home button, it will activate Google Assistant (same as before with OK Google), and it will get a Services download.
Also, be sure to open Maps, it too will ask you to do a Google Play Services download.
If SafetyNet fails, you do not have Google Play Services, or you forgot to disable root.
SafetyNet passes root check, and unlocked bootloader check.
Here is everything that was ripped out of the ROM
Here is a ZIP to restore some of the removed LG apps on v6 for the 10j build.
This only includes
LG Music app + widget
LG Weather + everything related to it
LG Qmemoplus
LG UpdateCenter
And here is the full rebloat.zip (eww)
/system/app/AndroidPay
/system/app/BookmarkProvider
/system/app/CloudPrint
/system/app/Drive
/system/app/DriveActivator
/system/app/EasterEgg
/system/app/EditorsDocs
/system/app/EditorsSheets
/system/app/EditorsSlides
/system/app/Gmail2
/system/app/GnssAirTest
/system/app/GnssLogCat
/system/app/GnssPosTest
/system/app/GnssTest
/system/app/GoogleCalendarSyncAdapter
/system/app/GooglePrintRecommendationService
/system/app/Hangouts
/system/app/LGAccount
/system/app/LGAirDrive
/system/app/LGBackupLauncher
/system/app/LGDrm
/system/app/LGFOTA
/system/app/LGMusicShare
/system/app/LGSpringCleaning
/system/app/MirrorLinkServer
/system/app/Music2
/system/app/Photos
/system/app/SignatureWallpaper
/system/app/SmartMessagingEngine
/system/app/SmartShare
/system/app/SmartShareProvider
/system/app/talkback
/system/app/Videos
/system/app/YouTube
/system/etc/permissions/com.lge.sizechangable.weather.platform.xml
/system/etc/amzn.mshop.properties
/system/priv-app/AdaptClient
/system/priv-app/CloudHub
/system/priv-app/facebook-installer
/system/priv-app/GoogleFeedback
/system/priv-app/LG360VideoWallpaper
/system/priv-app/LG360Wallpaper
/system/priv-app/LGAirDriveSetting
/system/priv-app/LGApplicationManager
/system/priv-app/LGBackup
/system/priv-app/LGEmail
/system/priv-app/LGExchange
/system/priv-app/LGGestureAnswering
/system/priv-app/LGLDB
/system/priv-app/LGMapUI
/system/priv-app/LGMusic
/system/priv-app/LGMusicController
/system/priv-app/LGMusicWidget
/system/priv-app/LGNLPService
/system/priv-app/LGPartnerBookmarksProvider
/system/priv-app/LGPCSuiteService
/system/priv-app/LGQHelp
/system/priv-app/LGQHelpService
/system/priv-app/LGSignBoardInitialGuide
/system/priv-app/LGSmartSharePush
/system/priv-app/LGSnapPage
/system/priv-app/LGTasksProvider
/system/priv-app/LGTTSPAService
/system/priv-app/LGUpdateCenter
/system/priv-app/LGVoiceCare
/system/priv-app/LGVRPlayer
/system/priv-app/LGWeatherService
/system/priv-app/LGWernickeManager
/system/priv-app/Lookout
/system/priv-app/MyPlacesEngine
/system/priv-app/MyPlacesSettings
/system/priv-app/NameID
/system/priv-app/Tag
/system/priv-app/TMO_MyAccount
/system/vendor/app/facebook-appmanager
/system/vendor/overlay/com.android.providers.partnerbookmarks
/system/vendor/overlay/com.lge.appbox.client
/system/vendor/overlay/com.lge.bnr
/system/vendor/overlay/com.lge.exchange
/system/vendor/overlay/com.lge.friendsmanager
/system/vendor/overlay/com.lge.lgmapui
/system/vendor/overlay/com.lge.lgworld
/system/vendor/overlay/com.lge.lifetracker
/system/vendor/overlay/com.lge.mlt
/system/vendor/overlay/com.lge.mtalk.sf
/system/vendor/overlay/com.lge.qhelp
/system/vendor/overlay/com.lge.qmemoplus
/system/vendor/overlay/com.lge.sizechangable.weather
/system/vendor/overlay/com.lge.sizechangable.weather.platform
/system/vendor/overlay/com.lge.sizechangable.weather.theme.optimus
/system/vendor/overlay/com.lge.smartsharepush
/system/vendor/overlay/com.lge.updatecenter
/system/vendor/overlay/com.lge.wernicke.nlp
Below is just old info from previous ROMs.
Before proceeding. It is absolutely necessary for you to be on a stable TWRP build (currently 3.0.2-1). Also, you must have already have had decrypted your ENTIRE phone. If your phone bootloops into TWRP, you probably didn't decrypt, and/or didn't flash no-verity properly, or it could also be that you are on an old TWRP build.
Here we have the base NRD90M ROM from LG.
I have added a few mods to it.
FEATURES
**This ROM is deODEXd
**Has init.d support
**Modified build.prop for better performance and hardware utility
**Removed bloatware (including that HORRID Lookout)
**Force encrypt disabled
**New kernel built-in.
**Based off 3.18.31 from @jcadduono source (thanks so much)!
**Added in the blu_active governor and set as default (via post_boot)
**No-op scheduler is default, and recommended
**Updated build.prop for better Hotspot support.
**More build.prop tweaks
**init.d support baked into the kernel
**Battery life should be noticeably improved, with no loss of performance (maybe even a bit faster).
**No need to wipe anything. System and caches are automatically wiped.
**Updated to SuperSU 2.78 SR4
**Updated boot and shutdown animation to the Android 7 default (thanks @freeza )
**More bloat removed
** Now includes more performance tweaks.
**Full Busybox support included!
**Built-in DNS Ad-blocking
**Fixed updater-script and binary
**Removed Sony Bravia/Xperia Engine
**Zen_Decision HotPlug enabled by default. (This will improve battery life, especially when your screen is off)
**TCP Congestion controller set to Westwood+ (improved download speeds)
**KCAL Color Control! Plus the Color Control app! Thanks to @savoca for KCAL and the app! Thanks to @freeza for the updated KCAL.c source file
**IO Stats for scheduler turned off
**IO Read ahead set to 2048kb
**Added init.d scripts to optimize your phone, and keep it fast over time.
**VPN is fixed!
**Gallery locked files are fixed!
**Bluetooth and FM should be fixed!
**No hotspot or ADB debug issues!
**More things I can't remember.
Kernel built on the Linaro 6.1.1 x86_x64 toolchain
Latest: v5.5
If you are already on v5.1,here is the 5.5 update. This is intended only for people already on v5.1. It will not wipe anything, and your phone will not need to do its initial setup.
Here are the changes for v5.5:
The main changes here are even more battery saving
**some voltage control preparations (still not active)
**added a DNS resolver module to maybe help some people with hotspot.
**Bluetooth and FM should work even better than before (hopefully not worse lol) **added assertive display which should help draw less power with screen on (not sure if it is actually working, but meh it's in there)
** C-states are made aware in the kernel, so sleeping should be more effective, while waking up should be more snappy.
More things. Do it!
Can confirm Pokemon GO and Android Pay work perfectly. Just need to hide root.
Use the app attached.
Checkmark where it says "Stop all su daemons"
Reboot
Open RootSwitch again, and the checkmark should still be there, click disable root, and test with an app called SafetyNet Helper Sample from Play Store. When root is disabled, SafetyNet test will pass with a full green screen.
When you are done playing, you can enable root again. The game checks every so often, so root needs to be disabled to play for X amount of time.
Here are the changes for v5.1:
The only change in v5.1 that it has my updated kernel. It had previously been giving bugs to random people in bluetooth. Also, FM radio was broken. I am happy to announce that as of 5.1, all functions are in full working order, and there should be nothing else wrong in the ROM.
Here are the changes for v5:
**ViPER4Android is preinstalled
**Kernel updates to latest sources (no changes other than updates)
**Rebased ROM to a full system dump. Major thanks to @NotATreoFan ! His intuition was quite helpful. This should fix issues with WiFi calling, and other odd bugs that have been creeping about.
**Included Titanium Backup pre-installed. I highly recommend getting the license, this program rocks, and never has ads. With a license you can do batch functions, and theres more features.
**Included Kernel Adiutor to prepare future kernel updates (CPU/GPU under+over clocking later on). You can also use this to tweak I/O settings, governor, screen color). Everything should run pretty good as it is, but what I do, is set read_head in I/O to 2048, and disable I/O Stats. I also set it on boot. I do not recommend modifying any CPU or GPU frequencies since there are no changes in the kernel to allow for that.
**Fully debloated. Thanks again to NATF for pointing out the files that were installing the last bit of carrier-based bloat (amazon, facebook stub installer, etc).
**Updated to latest Super SU
**Other things here and there to try and fix bugs.
**Oh, the FM module from the original ROM was also restored. This, in conjunction with the files retrieved from NATF's full dump, should fix FM!
**If you have issues on your phone, and are trying to fix them, I recommend you do a clean install.
**However, if your phone is fine and you have had no issues, you can go ahead and just dirty flash.
No need to wipe anything. The only people who had to or need to wipe, are those on my v2.0 ROM. If you are on any version below or higher (including 2.1) you do not need to wipe anything. If you are on stock ROM, ODEXd or deODEXd, or any other NRD90M ROM, you don't need to wipe, the ZIP will take care of everything for you. /data will not be wiped, so all your old apps and settings will be there. Internal storage is of course untouched.
For anyone interested in my color options, they are:
My new settings are:
All 3 colors at 256
Saturation 64
Value 127
Contrast 129
Know that I love deep, rich, vibrant colors. Also, changing colors will not change effects on pictures taken! This is post-processing. Your phone's screen is what changes, not the files that you create.
Note: Adding saturation (vibrance) will always give some sort of color banding -especially since KCAL is post-processing. You can minimize color banding by ever-so-slightly reducing gamma (read as "Value" in the Color Control app), and by ever-so-slightly fine-tuning Contrast. The value changes would be minimal, and the color banding will only be reduced ever-so-slightly, but this is just how it is. Nonetheless, the device looks friggin amazing with the color options set.
Thanks @zhuhang for V4A!
Major thanks to @Chainfire for creating SuperSU
Major thanks to @jcadduono for the root exploit, AND for the TWRP image(s), AND for inspiring me to learn to do it. Also, he supplied the stock System.img, boot.img, and sources for a custom kernel!/RealMVP
Viper4Android is included! To enable, run the app, and configure how you please!
More to come (as I learn to do it)
Please make any requests. If it is not too difficult, I will learn how to, and add it to the MODDED ROM!
REBLOAT
If you want to add in things I removed, flash this. It will include all apps that were removed. You can open the ZIP and simply delete anything inside the system folder that you don't want before you flash it.
Debloat list
Removed from /system/
system/app/CloudPrint*
system/app/Drive*
system/app/DriveActivator*
system/app/EditorsDocs*
system/app/Gmail2*
system/app/Hangouts*
system/app/Music2*
system/app/talkback*
system/app/Videos*
system/app/YouTube*
system/etc/recovery-resource.dat*
system/priv-app/LGEmail*
system/priv-app/LGTasksProvider*
system/recovery-from-boot.p*
system/app/AndroidPay*
system/priv-app/facebook-installer*
system/priv-app/GoogleFeedback*
system/app/LGAccount*
system/app/LGAirDrive*
system/priv-app/LGAirDriveSetting*
system/priv-app/LGBackup*
system/app/LGBackupLauncher*
system/priv-app/LGExchange*
system/app/LGFOTA*
system/app/LGMusicShare*
system/priv-app/LGPartnerBookmarksProvider*
system/app/LGSpringCleaning*
system/priv-app/Lookout*
system/priv-app/TMO_MyAccount*
system/priv-app/LGApplicationManager*
system/vendor/overlay/com.lge.friendsmanager*
system/vendor/app/facebook-appmanager*
system/priv-app/LGPCSuiteService*
system/priv-app/PromoHelper*
system/priv-app/LGQHelp*
system/priv-app/LGQHelpService*
system/priv-app/NameID*
system/priv-app/LGUpdateCenter*
system/vendor/overlay/com.lge.updatecenter*
system/vendor/overlay/com.android.providers.partnerbookmarks*
system/vendor/overlay/com.lge.appbox.client*
system/vendor/overlay/com.lge.exchange*
system/vendor/overlay/com.lge.updatecenter*
system/vendor/overlay/com.lge.bnr*
system/etc/amzn.mshop.properties
system/vendor/overlay/com.lge.lgworld*
system/vendor/overlay/com.lge.mlt*
system/vendor/overlay/com.lge.lifetracker*
Source for kernel is at https://github.com/Tilde88/nss
Thanks to @jcadduono for the amazing original source he made for us ( you can find it here : https://github.com/jcadduono/android_kernel_lge_msm8996/tree/android-7.0-security
Few minutes you say. Well I shall be one of the first to try it ^.^
Thanks for the hard work*.
shadowxaero said:
Few minutes you say. Well I shall be one of the first to try it ^.^
Thanks for the hard word.
Click to expand...
Click to collapse
Sorry, I noticed I missed 2 lines of scripts after I started upload. I just now started the proper upload. ETA is 15m from now.
I'll be the third to try this ... This is awesome ! Thanks dude ???
Tilde88 said:
Sorry, I noticed I missed 2 lines of scripts after I started upload. I just now started the proper upload. ETA is 15m from now.
Click to expand...
Click to collapse
Such a tease haha
thank you so much for this. now i am using your stock deodexd rom and what will be the proper way to install this over it? is it possible for you to put up the step by step instruction on how to install this rom in op?
thanks!
hslayer said:
thank you so much for this. now i am using your stock deodexd rom and what will be the proper way to install this over it? is it possible for you to put up the step by step instruction on how to install this rom in op?
thanks!
Click to expand...
Click to collapse
Yea I'll add something to the OP tomorrow.
You can flash this without any other steps. Just copy to phone, boot to TWRP, flash. Everything else is taken care of.
Tilde88 said:
Yea I'll add something to the OP tomorrow.
You can flash this without any other steps. Just copy to phone, boot to TWRP, flash. Everything else is taken care of.
Click to expand...
Click to collapse
Question. Does adb commands work for you? The box wont popup for me to authorize the device.
Awesome ness job @Tilde88...
Deleted
Sent from my Pixel XL using XDA-Developers mobile app
Follow the steps listed on my thread and it will work @ ViPER4Android.
Lol'd.
I was able to successfully port it, as displayed by the poll and close to 300 downloads.
shadowxaero said:
Question. Does adb commands work for you? The box wont popup for me to authorize the device.
Click to expand...
Click to collapse
I was wondering if that was just me. No, USB Debugging does not work for me either. Hmm... Now how did I break ADB integration? And how do I fix it?!
Paradoxumical said:
Follow the steps listed on my thread and it will work @ ViPER4Android.
Lol'd.
I was able to successfully port it, as displayed by the poll and close to 300 downloads.
Click to expand...
Click to collapse
Ok I'll try again later. Oh, I thought you were a different person lol.
I did try the steps in your OP. I also baked in all the files, and set all permissions accordingly with the updater script. No matter what, It always tells me that the Driver must be installed. Upon trying to install, it says IO Error. Even though root is on, and System is R/W. /shrug
I am assuming just bout to recovery and flash?
Is there any way to disable the sound mod if I wanted to?
Thank you Tilde88 for your hard work. Thats really awesome to have ROM like that.
Do you think you can also add:
1. boot animation: http://forum.xda-developers.com/v20/themes/stock-android-7-0-boot-shutdown-t3499524
2. 2nd screen flash on new text: http://forum.xda-developers.com/v20/themes/2nd-screen-flash-text-message-tasker-t3490220
3. Also change emoji to samsung ones. Those from LG are terrible. http://forum.xda-developers.com/v20/themes/aroma-1-click-emoji-changer-10-to-pick-t3499517
4. Ad blocker is the same as Ad away? I wish we could get rid of adds from apps.
Thank you again
What's the difference between this rom and the other one that you posted? This one just has mods baked in?
Can you dirty flash this over stock ROM
Sent from my Pixel XL using XDA-Developers mobile app
Paradoxumical said:
Follow the steps listed on my thread and it will work @ ViPER4Android.
Lol'd.
I was able to successfully port it, as displayed by the poll and close to 300 downloads.
Click to expand...
Click to collapse
Yes. Your viper is working. I can't get XHiFi working. But, I don't care. The original viper works great!
lightninbug said:
What's the difference between this rom and the other one that you posted? This one just has mods baked in?
Click to expand...
Click to collapse
@Tilde88 ? There is also another rom with bravia built in, what are the differences?? Why not just update your other thread/rom?
Hey everyone, I just wanted to make a guide on how to improve your battery life on a custom nougat rom with solid performance and little to no heating issues. I use this method after many trials and errors after I only got 2.5-3hrs of SOT after leaving stock and flashing custom roms. However, after Magisk 14.3 I no longer got the frequent safety issue that plague me for months and I also notice my battery life starting to improve.
Please Note: I have not tested this on marshmallow custom roms or any stock Moto G4/G4 Plus rom (6.0 and above) but feel free to try and let me know if it works. Also this method could be duplicated on other devices.
Disclaimer: I'm not responsible for any bricked or damage device you used my method. I give all credit to the developers who does a fantastic job creating all the things they do for the root community. Thank you!
Follow the following tips if your on a custom nougat rom (Ex: LineageOS, Resurrection Remix, InvictaOS, etc.).
1. Download a custom Nougat (7.0+) rom for your device and go through the initial set up as normal. (I personally use InvictaOS for my device which is very stable). Note: Do not install any root app that modifies system files!
2. Download the following files: Ex kernel , Addon-su- remove-14.1.zip , Magisk 14.3 (1437).zip.
2. Reboot into recovery and install the latest Ex kernel for nougat. This kernel is quite stable and works universally with most custom roms. (It also keeps the phone sightly cooler during heavy usage).
3. Next, flash the addonsu-remove.zip file to remove any traces of root from your room as it will interfere with Magisk which could result in your device randomly rebooting. Afterwards, flash magisk 14.3.zip (This version of magisk pass safetynet on a consistent basis in my experience). You can now reboot your device.
4. Once your back into your phone, launch magisk manager and check if your pass safetynet (which means you did it right) now head to the download section of the app and install the module for "Sysconfig Patcher". A solid tweak improves screen off time by putting the battery hog known as Google Play Service into doze.
This is a bonus step but it's well worth it if you want to maximize battery life:
5A. Buy the official Ex kernel app from the play store. This allows you more power over your kernel settings than the alternatives. Next download the kernel turnables "lightning blade" in addition to our device, this works on allow phones using a snapdragon 617 processor like the G4/G4 Plus. Download the zip file and follow the instructions in the thread very carefully. This will give you much improved screen on time by using less cores unless necessary to maintain a smooth experience. Additionally, It keeps the phone cooler during heavy usage coupled with ex kernel.
5B. Now you can play around with the kernel settings if you like. My personal settings is more gear to my average daily use. Under CPU tab I change my governor turnable to lightning blade from the previous step, under GPU tab I use Simple_ondemand as the gpu governor. Under memory tab, I disable both KSM and KSM Deferred Timer and enable Low Memory Killer. Then under miscellaneous I change TCP to Westwood, increase the i/o schedule read ahead time to 512, and press wake blocks to toggle all three wake blocks. If you want to keep these changes make sure to hit apply on boot for every changes made within the app. You can undo all this to return to ex kernel's stock settings by clearing ex kernel manager's app data and rebooting.
Important: If you follow my steps above you should have better battery life. Try not to install Magisk modules what is not compatible with Magisk 14.0 and above as it may cause your device to randomly reboot and bootloop when powering on.
Please share your battery stats!