Database Users

[GUIDE] [NOUGAT] Viper4Android

//Thank you all for 30k+ Views. You're amazing guys//
You want Android 8 with Viper4android to?
Thread created check my profile...
Hi,
at first im not responsible for anything that happens to your phone OK?
Fine Let's Start.
If you are on cm skip all until the cm section
Supported kernel list and known errors/bugs see second post
Step 1
- Flash full Factory Images.
- Install TWRP, remember you have to be decrypted.
Step 2
- Install Android 7 ROM by tupac4u / or any other rom / or leave stock
- Reboot //if nessesairy
Step 3
- Flash ElementalX's N Kernel.
- Flash Viper5.0_Stock.zip in Recovery / or any other viper
- Reboot.
Step 4
- Install driver.
- Open File Explorer and delete /system/vendor/etc/audio_effects.conf
- Reboot.
Step 5
- Set enforcing to permissive (You have to do it at every Reboot!).
- In Viper open Menu->FX-CompatibleMode->yes // you can try without, it may work
- Enjoy Viper.
CM Section
1. Flash arise sound mod ( link down below )
2. And IMPORTANT flash super su
3. Disable audio fx and reboot
SPOTIFY FIX
1. Download that file
https://drive.google.com/file/d/0BxyY1q0qeeeEeUFGT3JHeDZLZkE/view
2. Place it under /system/etc
3. Reboot
PURE NEXUS ONLY WORKS WITH BUILD 10/25!!!
If it worked leave a reply.
Alternative Download link for ARISE Viper here:
http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709

Unsupported Rom/Kernel
Kernel:
- Stock
- Jolla
ROM:
F.A.Q.
Q: Spotify isn't working with that
A: Force enable Viper4Android and turn FX Mode to compatible. Then restart both applications.
Q: Why ElementalX Kernel?
A: That's the only Kernel who works with Viper except Stock kernel. Elite Kernel may also work but it hasent been updated since the Dev Previews.
Q: Is that also working with the stock rom?
A: Yup. Also works with (nearly) any stock based ROM.

Is there a definite way of checking if it's working? Not by sound?

Yes, just check driver status in viper when something is playing in the background. If it says 'processing', then it's working.
Btw, why would I need custom kernel for viper?
Sent from my Nexus 5X using Tapatalk

how to set permissive mode permanently?

Nightshadow931 said:
Yes, just check driver status in viper when something is playing in the background. If it says 'processing', then it's working.
Btw, why would I need custom kernel for viper?
Click to expand...
Click to collapse
I found that it isn't working on jolla Kernel and Stock.

Did you enable viper in app itself?
Not sure, but maybe you need to enable it on order to see 'processing'..
Did the installation of driver went well?
Sent from my Nexus 5X using Tapatalk

enzippo said:
how to set permissive mode permanently?
Click to expand...
Click to collapse
use a file exlorer with root privileges like es or root explorer and go to /etc/init.d directory, create a file and named "08setperm" (without quotes) and add the below lines in the file and save it..
#!/system/sh
setenforce 0
And give full permission (rwxrwxrwx)
reboot and you should be good. if for some reason your init.d script doesn't launch then download and install universal init.d tool and enable it.

Nice that someone is trying to get Viper4Android to work on Nexus 5x with Android 7.0 (Nougat). Sadly it does not work, tried your way but it does not enable me to get Viper4Android to work in Spotify.
Selinux is in permissive, your viber4android package is in place, audio_effects.conf removed, Android 7 by tupac4u installed and complete factory image installation before all this. No go..
Viper4android driver status does not complain but processing is always "no".

Try some other app like play music, v4a won't work on all apps if they have their own equalizer.
Sent from my Nexus 5X using Tapatalk

Blinkiz said:
Nice that someone is trying to get Viper4Android to work on Nexus 5x with Android 7.0 (Nougat). Sadly it does not work, tried your way but it does not enable me to get Viper4Android to work in Spotify.
Selinux is in permissive, your viber4android package is in place, audio_effects.conf removed, Android 7 by tupac4u installed and complete factory image installation before all this. No go..
Viper4android driver status does not complain but processing is always "no".
Click to expand...
Click to collapse
For those who want to use Viper4android with Spotify change fx compatible Mode to compatible in Viper settings. Then Open Spotify and go to Settings->Equalizer that should bring up Viper. Select Force enable and close Viper and Spotify. Open up both again and Boom Viper is there.

How find Android 7 by tupac4u ??
EDIT.
I found him already

Did someone get it working with stock rooted ROM?

noidea24 said:
use a file exlorer with root privileges like es or root explorer and go to /etc/init.d directory, create a file and named "08setperm" (without quotes) and add the below lines in the file and save it..
#!/system/sh
setenforce 0
And give full permission (rwxrwxrwx)
reboot and you should be good. if for some reason your init.d script doesn't launch then download and install universal init.d tool and enable it.
Click to expand...
Click to collapse
Idk if this will work on the new version, but this zip I've attached here sets the previous ElementalX-N5x-1.17 kernel permissive permanently. I'm not on nougat yet, waiting for Xposed.

trhacker01 said:
Idk if this will work on the new version, but this zip I've attached here sets the previous ElementalX-N5x-1.17 kernel permissive permanently. I'm not on nougat yet, waiting for Xposed.
Click to expand...
Click to collapse
In gonna give it a try

Nightshadow931 said:
Did someone get it working with stock rooted ROM?
Click to expand...
Click to collapse
Me not

Thargorsson said:
In gonna give it a try
Click to expand...
Click to collapse
Nope it don't works

Thargorsson said:
Nope it don't works
Click to expand...
Click to collapse
thats how im running right now, just checked. only with the universal init.d though

noidea24 said:
thats how im running right now, just checked. only with the universal init.d though
Click to expand...
Click to collapse
Ur saying that permissive zip works with the universal init.d?

trhacker01 said:
Ur saying that permissive zip works with the universal init.d?
Click to expand...
Click to collapse
As long as the zip creates/places a file in the init.d to change selinux then i guess it should work

Llama Sweet Kernel Tweaks

Feature list​
- sets hostname to LG-G4 something that was missing at first from lineage/aosp 7.1.1 (maybe i will remove that)
- Better mount point flags
- Internal storage:
nomerges
nr_requests
lower safe read_ahead_kb
cfq scheduler
cfq scheduler tweaks
remove add_random (if its enabled in the kernel by default)
rq_affinity
- external storage:
nomerges
nr_requests
lower safe read_ahead_kb
cfq scheduler
cfq scheduler tweaks
remove add_random (if its enabled in the kernel by default)
rq_affinity
- Net and virtual memory:
tcp_congestion_control
disable_ipv6
dirty_writeback_centisecs
dirty_expire_centisecs
dirty_background_ratio
dirty_ratio
drop_caches
kernel.panic
min_free_kbytes
overcommit_ratio
panic_on_oom
swappiness 0 #llama doesn't have zram feature, it's useless on Lg G4
vfs_cache_pressure
- CPU customisations ~depends on your choice of script~
balanced ~doesn't make any cpu changes~
less ~for less battery drain, cpu rests more~
more-less ~for a lot less battery drain, but with a big lag (will soon try fix stability and smoothness)~
performance ~for full cpu power, but rest when the screen is off~
- Kernel customisations
msm_thermal ~off on battery save / on and set a safe temp. for performance~
lowmemorykiller
read_wakeup_threshold
write_wakeup_threshold
hotplug customisation
- Only the safe internet customisations
tcp_timestamps
tcp_tw_reuse
tcp_sack
tcp_tw_recycle
tcp_window_scaling
tcp_keepalive_probes
tcp_keepalive_intvl
tcp_fin_timeout
For stock based roms follow the guide in post #2
How to "install" it ? Simple
1.unzip
2.place it in /system/etc/init.d
Code:
adb root
adb remount
adb push <your tweak> system/etc/init.d/
3.change its permissions to 755
4.lastly change owner:group to root:shell
Code:
adb shell
su
mount -o remount rw /system
chmod 755 /system/etc/init.d/<your tweak>
chown root:shell /system/etc/init.d/<your tweak>
If you don't have a pc, type in a terminal inside your g4
Code:
su
mount -o rw remount /system
chmod 755 /system/etc/init.d/<your tweak>
chown root:shell /system/etc/init.d/<your tweak>
Those of you that use the new systemless root method of chainfire you can put the script in /system/su.d or in /su/su.d with permissions 700 (same permissions at folder and script) and set owner:group to root:root
Those of you that use the new magisk root method you can put the script in /magisk/.core/service.d/ with the same permissions and ownership as in init.d
Those coming using search bar and don't have this phone and this kernel, don't try it, unless you know what to edit to "fit" your own kernel.
These tweaks aren't just for faster easy setting up our phone, they are more useful for those that don't want to have root access ON, for various personal reasons. They can apply those settings on boot and setup their phone without the need of root and an app asking for root.
Easy removal: delete the script and reboot. And never use more than one of these scripts inside init.d
Careful, some stock based roms have preinstalled some scripts inside init.d by default.
Those must be removed after flashing Llama Sweet Kernel. They are not compatible and they cause instability !
BIG Thanks to this genius
@genesixxbf3
for his kernel to our lg g4.
XDA:DevDB Information
[Tweaks][MM/N][H815][H811]Kernel Tweaks[CM/STOCK/AOSP], Tool/Utility for the LG G4
Contributors
kessaras, genesixxbf3
Version Information
Status: Stable
Created 2016-12-09
Last Updated 2017-04-25

Reserved
This is a guide for ALL stock based roms and all kernels.
My script will only add tweaks that apply to all kernels.
For those that are rooted with SuperSu, they must first fully remove it.
Nub guide to change SuperSu for Magisk root:​
Step 1.
SuperSu must be removed.
Go into supersu -> settings -> fully remove root access.
###Or download and flash in recovery mode the UnSu script from osm0sis thread.###
Step 2.
Use hardware key combination to boot to TWRP.
###If you used the UnSu script, no need to reboot to recovery, skip step 2 and go to next one.###
Step 3.
Flash latest magisk flashable zip for users that are not rooted yet.
It sais: "If you're not rooted, or something went wrong and you need a clean start"
Download that .zip file and flash it.
Now you are rooted again. Reboot to your rom.
Step 4.
Download Magisk Manager from play store. In that app you can even enable systemless root to hide root from the apps, or do many things that you like.
Questions further go to magisk thread not here. And don't forget to re-enable usb debugging. After you removed root, that was toggled, ###Unless you used the UnSu script again. That means that before reboot you were already rooted.###
Now it's time to install your script.
Download the compressed tweak from this post , uncompress it and follow the next guide.
The steps are the same with the lineage based roms and it works for ALL lineage based roms too
If you use a root file manager then you can skip the guide and just cut - paste the script in /magisk/.core/service.d/
set permissions to 755, ownership to root:shell and reboot.
INSTALLATION​Step 1.
place it in /magisk/.core/service.d/
Code:
adb push /<path to the script>/90balanced /sdcard/
adb shell
su
mv /sdcard/90balanced /magisk/.core/service.d/
Step 2.change its permissions to 755 if it's not already set to 755 by default
Code:
chmod 755 /magisk/.core/service.d/90balanced
If you don't have a pc, type the same commands in g4 terminal but of course without the adb command. Script is supposed to be in path /sdcard/
not in /sdcard/download/ or whatever path. Otherwise edit the command "mv ..." to match the script path.
That's it. Reboot to apply your tweaks.
~I will add Llama Sweet kernel tweaks for stock based ROMS when Genesixxbf3 fixes the bluetooth issue.
Until then all use this one that applies to all kernels including Llama.
Special thanks to:
@topjohnwu for developing Magisk
and to
@osm0sis for his UnSU script

My scripts are not meant for use with kernel adiutor.
Changelog
31/01/2017
- fixed stability for "90less"
- changed to "westwood" tcp congestion control
01/02/2017
- changed to Fiops scheduler only for the 90less and 90more-less
- fixed stability for 90more-less
12/02/2017
- when screen is on, 3 cores always online not 1.
- fixed stability for 90less , 90more-less
- 90balance, interactive governor stable and at the same time conserving some battery
- big cores governor is same with small cores
15/02/2017 and 20/02/2017
- changed back to cfq scheduler
- added cfq scheduler tweaks
- fixed path to disable ipv6
09/03/2017
- fixed a bug for those that big cores were found disabled on boot
Although this is something caused from dirty flashing and can only be fixed with a clean flash
18/03/2017
- Added better mount point flags for Lineage/Aosp based roms, for f2fs, for those that prefer using f2fs partitions format
- i changed the way the mount points get set, now you don't need busybox if you don't want to.
- bigger timer rate for interactive governor for the balanced tweak, balanced can conserve battery now too.
25/04/2017
- Less-more is not lagging anymore but of course it still loads slow since cpu runs at a lower frequency
- interactive governor in balanced script saves more battery than before
- All scripts now give a small cpu frequency amount on input to reduce lag
- At less and less-more the hotplug sets the cores online at a lower frequency. Before, with those scripts you could rarely see the other cores online

kessaras said:
You can request any setting for kernel and cpu you want. I can add them for you.
Screenshots of battery with 90less.
~Haven't done anything special. Brightness is at normal with "auto" ON, gapps stock, usage: Normal, chat, xda, phone Calls/Messages, GPS ON.
Many factors determine the battery drain, such as 3rd party apps, ads from apps, services and more, don't blame my settings. Those settings are absolute and tested and i only do this to help everyone.
Click to expand...
Click to collapse
Thanks for you work, I am using H818p without BL unlock. Currently, I can modify /etc/init/qcom.post_boot.sh from this thread (http://forum.xda-developers.com/tmo...-msm-8992-cpu-io-ram-interactive-gov-t3351478).
The question is, can I port some tweaks from this thread to the stock kernel using qcom.post_boot ? I am not familiar with the seqence of boot, any idea ?
Thanks,

jskasia said:
Thanks for you work, I am using H818p without BL unlock. Currently, I can modify /etc/init/qcom.post_boot.sh from this thread (http://forum.xda-developers.com/tmo...sm-8992-cpu-io-ram-interactive-gov-t3351478).
The question is, can I port some tweaks from this thread to the stock kernel using qcom.post_boot ? I am not familiar with the seqence of boot, any idea ?
Thanks,
Click to expand...
Click to collapse
Scripts are only for Llama kernel. So,
it depends if the stock kernel has same file "trees". Worst case scenario is to not be able to boot. If you can enter recovery you can fix it by doing :
Code:
rm /system/etc/init.d/<name of the script>
Or use the recovery file manager to delete it,
reboot and you are fine.
Don't use 90less as it is or for sure you won't boot. Less is using alucard governor which doesn't exist in stock. Open script and edit those lines, change alucard to interactive.
"kernel tweaks" delete them. the stock kernel doesn't have same hotplugs and heat protection.
EDIT:
a part of the scripts does work for stock without llama kernel. it's not dangerous because the stock lg rom doesn't have init.d support on boot and the script only can be applied inside kernel adiutor by enabling init.d emulator.
you can use it then. you will just not get the 100% out of it.
in the 90less you wont get the alucard governor and the hotplug to let the cpu rest.
the only alternative available is to make you one that edits the interactive governor to work almost the same as alucard and conserve a bit more battery than the stock interactive does.

@matgesiarz
follow the op

kessaras said:
Scripts are only for Llama kernel. So,
it depends if the stock kernel has same file "trees". Worst case scenario is to not be able to boot. If you can enter recovery you can fix it by doing :
Code:
rm /system/etc/init.d/<name of the script>
Or use the recovery file manager to delete it,
reboot and you are fine.
Don't use 90less as it is or for sure you won't boot. Less is using alucard governor which doesn't exist in stock. Open script and edit those lines, change alucard to interactive.
"kernel tweaks" delete them. the stock kernel doesn't have same hotplugs and heat protection.
Click to expand...
Click to collapse
Okay, I successfully put the tweaks (balance) on to init.qcom.post_boot.sh. My phone boot without any problem. After few days we will see the result.
Thanks

we just need to push scripts or I need also to clean the init.d folder first from other scripts? I am on ChyperOS 3.1.4

If I understand right, if I put this tweak I don't need to setup any kernel modification in apps like EX Kernel manager, isn't?

Vipery said:
we just need to push scripts or I need also to clean the init.d folder first from other scripts? I am on ChyperOS 3.1.4
Click to expand...
Click to collapse
no you don't clean the init.d folder. if you do that you will lose important script that needs the rom to boot. you only use one of those scripts in init.d, if you put 2 of those in, delete the one.
Oletros said:
If I understand right, if I put this tweak I don't need to setup any kernel modification in apps like EX Kernel manager, isn't?
Click to expand...
Click to collapse
exactly and if you need any change and you don't know how to edit the script, you can ask me to add it for you

kessaras said:
no you don't clean the init.d folder. if you do that you will lose important script that needs the rom to boot. you only use one of those scripts in init.d, if you put 2 of those in, delete the one.
Click to expand...
Click to collapse
Thank you. Another thing, I need to set owner and group to shell or just group? The other scripts are set root/shell and not shell/shell.

Vipery said:
Thank you. Another thing, I need to set owner and group to shell or just group? The other scripts are set root/shell and not shell/shell.
Click to expand...
Click to collapse
only what the op sais. only group owner. its already set from me, but you have to at least check if its set, if not, set it. group owner shell

Thanks for the tweaks!
Sorry for this perhaps silly question, but which is supposed to be more battery friendly between balanced and less?

joaste said:
Thanks for the tweaks!
Sorry for this perhaps silly question, but which is supposed to be more battery friendly between balanced and less?
Click to expand...
Click to collapse
less refers to less battery consuption and its only by a little cause we don't want to have lags. Of course we can do it even more battery friendly but we will have a very slow phone.

kessaras said:
less refers to less battery consuption and its only by a little cause we don't want to have lags. Of course we can do it even more battery friendly but we will have a very slow phone.
Click to expand...
Click to collapse
Thanks for the clarification!

kessaras said:
exactly and if you need any change and you don't know how to edit the script, you can ask me to add it for you
Click to expand...
Click to collapse
Thanks

Ok,I applied your 90less tweaks and here's what I've got after reboot:
The big cores governor-interactive,max.freq.-1248
The little cores governor-alucard,max.freq.-1440
MSM Hotplug-OFF
MSM MPDecision Hotplug-ON
Is that ok or...?

welder73 said:
Ok,I applied your 90less tweaks and here's what I've got after reboot:
The big cores governor-interactive,max.freq.-1248
The little cores governor-alucard,max.freq.-1440
MSM Hotplug-OFF
MSM MPDecision Hotplug-ON
Is that ok or...?
Click to expand...
Click to collapse
nothing applied on boot.
in less,
max for the big is set to 1536
and hotplug is off to not get load for nothing since the temp wont go higher than 60 even under the hot summer sun.

kessaras said:
nothing applied on boot.
in less,
max for the big is set to 1536
and hotplug is off to not get load for nothing since the temp wont go higher than 60 even under the hot summer sun.
Click to expand...
Click to collapse
So I should change the max for the little cores to 1536 and everything else is ok?

Vipery said:
Thank you. Another thing, I need to set owner and group to shell or just group? The other scripts are set root/shell and not shell/shell.
Click to expand...
Click to collapse
...

4/20/2017 [] 7.1.1 UPDATE [] One Plus 3 (msm 8996) [] CPU, VM, RAM, IO "Tune"

4/20/2017 [] 7.1.1 UPDATE [] One Plus 3 (msm 8996) [] CPU, VM, RAM, IO "Tune"
ORIGINAL THREAD HERE: https://forum.xda-developers.com/axon-7/development/2-15-2017-axon-7-msm-8996-cpu-vm-ram-t3557392
This mod was originally created for the Axon 7, but due to several requests, I've modified a version for the One Plus 3, please see below, and post questions or comments in the original thread above. Please state you are a One Plus 3 user if you have feedback in that thread, to consolidate user feedback and speed up response time.
Custom tuning for a device is always a necessity. "Canned" settings will get you by, but they are certainly never optimized for a specific device. In fact, Linux typically takes a general approach to find harmonic balance in default settings that will, for the most part, work in an acceptable manner for just about any device. There are a lot of resources available on this device, so we should utilize it in a manner appropriate to squeeze out as much battery life and performance as possible without sacrificing much of those outputs, don't you think? This is going to fix that for you.
Here is what is required of you before you begin:
1. Must be rooted
2. Must have the One Plus 3 OR a device running the Snapdragon 820, as this modification is not so much device specific, but hardware specific. The important aspect being the snapdragon 820 and the RAM disk size.
3. Must have write protection disabled. If the One Plus 3 requires write protection to be disabled, see the code and instruction below:
Using adb shell:
Code:
adb reboot disemmcwp
Using Linux terminal (from your phone, for example):
Code:
reboot disemmcwp
Let's begin.
Getting right to it, here's what I've done:
- modified parameters of the interactive governor, and quite extensively at that (search some of my threads if you want a little bit of a breakdown of the general approach I take)
- reconfigured input_boost parameters
- reconfigured vm parameters (again, the device has a lot of RAM resource, this will utilize it and give you a far better user experience. Basically, I've adjusted dirty_ratio, dirty_background_ratio, swappiness, and other parameters of the virtual machine.)
- disabled zRAM for 6 GB variants (RAM compression, again, not needed on this device really, this mod will save you CPU cycles and power) this will not apply to 4 GB devices, you will still have zRAM enabled.
- remapped minfree parameters for LMK (low memory killer) again only for 6 GB variants
- Tuned CFQ scheduler for flash storage devices
- Tuned "core_ctl" module (needs kernel support, I recommend freeza's latest version of BeastMode. For those wondering, yes, you can still use this mod with the stock kernel. It won't break anything.) again this will only apply to devices that support core_ctl at the kernel.
In a nutshell, that's what we're looking at here. I can guarantee you this will have a significantly positive impact on your device. Turbo time, homies.
How to install????
Easy. First, the file we are replacing is found in /system/etc... it is the "init.qcom.post_boot.sh" file - this file is basically shell scripts, which are applied at boot via this particular shell file.
All you have to do is download the file to your device, open up a file explorer (must have root capability), navigate to the /system/etc folder with said file explorer, mount your /system as RW (read write), delete your stock "init.qcom.post_boot.sh" file, and replace it with mine.
After you've successfully done this, change the new file's permissions to rw-r--r-- (0644), and then reboot!
Or, if you are brave, you can do it manually via a terminal app and get your fingers wet... if you choose to do that, see below:
Make sure the file is located on the root of your internal sdcard in /sdcard, open your terminal app (again, must have root) and type the following commands, hitting enter after each one (be careful to pay attention to the spacing).
Code:
su
Code:
cd /
Code:
mount -o remount,rw /system
Code:
cd /system/etc
Code:
rm init.qcom.post_boot.sh
Code:
cd /sdcard
Code:
mv init.qcom.post_boot.sh /system/etc
Code:
chmod 0644 /system/etc/init.qcom.post_boot.sh
I don't want credit, don't need you to give or offer donations, this is purely for the community in the spirit of Linux ideology. All I ask is for you to hit the thanks button :good:
That's pretty much it, guys. Enjoy!
DOWNLOAD

I'm willing to give it a go...
File attached ?

Downloaded
warBeard_actual said:
ORIGINAL THREAD HERE: https://forum.xda-developers.com/axon-7/development/2-15-2017-axon-7-msm-8996-cpu-vm-ram-t3557392
Hello, everyone. I would like to provide this modification for this device, as it uses the same SoC as the Axon 7, V10, HTC 10... and a few other devices.
If anybody is interested, please provide me with the STOCK init.qcom.post_boot.sh file, which is found in /system/etc and I will post the modified file and instructions on how to install it.
:good:
Click to expand...
Click to collapse
Ok see immediately improvement! Thanks !
Going to test it a couple of days!

danny b. said:
Ok see immediately improvement! Thanks !
Going to test it a couple of days!
Click to expand...
Click to collapse
I haven't posted the one for your device yet, but I am uploading now.
op updated****

Axon7
warBeard_actual said:
I haven't posted the one for your device yet, but I am uploading now.
op updated****
Click to expand...
Click to collapse
This op3 is my daily phone
The axon 7 is my girlfriend phone also mine?but tested it on the 7 sorry for the confusion. Great work going to test it tomorrow on op3

Read through your entire other thread, you have been updating pretty tirelessly. I installed it on Open Beta 14, ran cat /proc to ensure swappiness was good and it shows 1 just like the config file so the tweaks are up and running on my device. I'm running the beta with the stock kernel so I'll do some testing and see how it does with general performance over the next few days.
I don't know who asked to you share this with us, but we definitely appreciate it :good:

will test it for a couple of days and report...
Heads Up...
the adb command doesn't work for me on OB13, it reboots the phone and doesn't disable Write protection, i went around that by deleting and replacing the file from TWRP...

Thank you I could see some battery improvements.i copied that file through twrp ..Using 4g and got 2.40 hours sot still 50 percent battery remaining.phone doesn't slow down or heat up it's a must try

If i change the kernel like blue spark then its worth it ?
And orignel file is about 122 k and youe file is only 22k.

Facebooook said:
If i change the kernel like blue spark then its worth it ?
And orignel file is about 122 k and youe file is only 22k.
Click to expand...
Click to collapse
He addresses this in the original thread and it is the same size difference on the axon 7. He removed the generic options and put in modified and tuned optimizations for our specific hardware build instead of every MSM device. It definitely provides a more responsive system overall, but I haven't had it running long enough to see the battery impact on the device.

How to check if it works?
Will it work on custom ROMs (AICP etc?)

Day 2 hotter than normal. In keep on testing
Edit: back to normal
Problem was new app

Plz ignore. Problem solved

Will definitely try this thanx a bunch???

Sn0wFl4keZ said:
How to check if it works?
Will it work on custom ROMs (AICP etc?)
Click to expand...
Click to collapse
Definitely no for custom ROMs. Using AICP with latest ElementalX, the file mentioned by OP is not even present in our /system/etc.
Anyway, pretty sure that kernel devs have already tweaked most of the parameters changed by this sh script, so I don't see any need for it for anyone except stock ROM and stock kernel users.
P.S. Still, a lot of work was done by OP, it definitely deserves a big Thank you.

Nezorflame said:
Definitely no for custom ROMs. Using AICP with latest ElementalX, the file mentioned by OP is not even present in our /system/etc.
Anyway, pretty sure that kernel devs have already tweaked most of the parameters changed by this sh script, so I don't see any need for it for anyone except stock ROM and stock kernel users.
P.S. Still, a lot of work was done by OP, it definitely deserves a big Thank you.
Click to expand...
Click to collapse
Thanks for the nod. And while I can't speak to the changes implemented by kernel compilers on this forum, I would be willing to give you guys a comparison of the custom ROMs/combos you're running on your op3.
It might shed some light on whether or not you'd benefit from using it if you're using a CM type set up.
Here's what you do... Go into /sys/devices/system/cpu/cpu0/cpufreq/interactive ...
There will be a bunch of files in there for above_hispeed_freq, hispeed_load... A bunch of others. Open them up with a file explorer, snap a screen shot, post it here so I can see the values of your CM-based ROMs.

Is there I way to confirm that it is working properly because I think it is but it feels like a placebo effect. Thanks for the mod :good:

Thanks

warBeard_actual said:
Thanks for the nod. And while I can't speak to the changes implemented by kernel compilers on this forum, I would be willing to give you guys a comparison of the custom ROMs/combos you're running on your op3.
It might shed some light on whether or not you'd benefit from using it if you're using a CM type set up.
Here's what you do... Go into /sys/devices/system/cpu/cpu0/cpufreq/interactive ...
There will be a bunch of files in there for above_hispeed_freq, hispeed_load... A bunch of others. Open them up with a file explorer, snap a screen shot, post it here so I can see the values of your CM-based ROMs.
Click to expand...
Click to collapse
Here are the contents of the .../interactive folder (everything except boostpulse - got 'Permision denied' on that).
That's for the AICP (based on LOS).

Hello.. Thanks for your mod.
I'm using freedomOS OB13 with francos kernel with his app. Already did all the steps in this thread.
Now, I Just wanted to know if it's just for stock phones or will it improve for everyone?
And how to check if everything is as it should?
Thanks in advance!
---------- Post added at 10:27 AM ---------- Previous post was at 10:22 AM ----------
theduke7 said:
will test it for a couple of days and report...
Heads Up...
the adb command doesn't work for me on OB13, it reboots the phone and doesn't disable Write protection, i went around that by deleting and replacing the file from TWRP...
Click to expand...
Click to collapse
Hey.. How did you check if the write protection is still disabled?
I'm on OB13 as well and my phone just restarted after the command and I thought that's it!

OnePlus 5 Kali Nethunter

Hello boys & girls!
I want to port the Kali Nethunter rom to the OnePlus 5.
Because it is my first time i need some people who can port it together with me.
Offensive Security has a nice tutorial on their website but its getting complicated when i come to the modify kernel part.
I really need some help with that.
More info:
offensive-security.com/kali-linux-nethunter-download
Porting info:
github.com/offensive-security/kali-nethunter/wiki/Porting-Nethunter
Sorry due the spam restrictions i cant post the links.
If you got some tips or advice on how to do it let me know! :good:
Greetings,
Stefjoe

Let me see...
EDIT: Ok. I can't help sorry

_MartyMan_ said:
Let me see...
EDIT: Ok. I can't help sorry
Click to expand...
Click to collapse
Damn.... too bad

Any luck with this? Having a hard time myself.

I've looked at it myself and it seems complicated to me because I've never done that before but maybe anyone here is able to do it...

stefjoe said:
Damn.... too bad
Click to expand...
Click to collapse
Any progress?

The only problem to port nethunter to the OP5 is to add HID and CDROM support to the kernel but in order to do so, those patches have to be ported to kernel version 4.4+ ...
Otherwise packet injection over usb works fine on OOS.
I'm trying to compile a kernel with packet injection for RR.

Tell me if you want the kernel ... I've modded Adin's kernel (OOS) and Lightning kernel (LOS).
You will then have to install the nethunter chroot zip and you're good to go.

Arka1n said:
The only problem to port nethunter to the OP5 is to add HID and CDROM support to the kernel but in order to do so, those patches have to be ported to kernel version 4.4+ ...
Otherwise packet injection over usb works fine on OOS.
I'm trying to compile a kernel with packet injection for RR.
Click to expand...
Click to collapse
I think you can find the patch for HID and CDROM support here:
https://forum.xda-developers.com/showthread.php?t=2196707
https://github.com/CyanogenMod/andr...mmit/46bd47757a9f34c1d95dd2620414893212fb0526
FYI I don't know anything about patching kernels so i might be wrong

Well this leads to the hid patch :
github.com/pelya/android-keyboard-gadget/blob/master/kernel-3.4.patch
And this to something about the CDROM patch for the OP3 :
github.com/binkybear/androiddevs_kernel_oneplus_msm8996/commit/fc6f4b6b5f70509fbc5d583e8315f88119acb3c2
Not yet allowed to post links...
Anyway i need some help from other devs to port those to 4.4 :silly:...

Arka1n,
Hey,
I saw the post regarding putting nethuntr on the 1+ 5.
Are you willing to give me the needed kernel too plz?
Thanks
Jazzzzz

Arka1n said:
Tell me if you want the kernel ... I've modded Adin's kernel (OOS) and Lightning kernel (LOS).
You will then have to install the nethunter chroot zip and you're good to go.
Click to expand...
Click to collapse
Most definitely would like it! Message me

Arka1n said:
Tell me if you want the kernel ... I've modded Adin's kernel (OOS) and Lightning kernel (LOS).
You will then have to install the nethunter chroot zip and you're good to go.
Click to expand...
Click to collapse
I definitely would like it too !!!

Crappy upload rate so it may take some time...

[WOOT]
Here : https://forum.xda-developers.com/oneplus-5/development/burgerhunter-t3638810 :victory:

OnePlus5
I just got mine and want to do the same. I currently have nethunter on the original oneplus one and it works great. I am hoping it's the same process. Has anyone done it on any of the oneplus phones before? I ask because it took me at least 3 weeks every day after work playing with it. I bricked it maybe 3 times and OnePlus team remotely fixed it and finally I got it working. It wasn't easy.
If somebody has, please share your experience. I will try to pull up all of the links I used and videos I watched before I finally got nethunter to boot.
I want to do this to the oneplus 5 so I can use it for nethunter then wipe the onplus one and use it as my phone. Any help/advice is greatly appreciated. I will come back and post the info I used for the oneplus one and anything I find for the oneplus 5.
cheers

Nethunter for OnePlus 5
I found a way to "port" but not the entire kernel.
I managed to create chroot and can run Kali shell after one failed trail.
IMPORTANT : I went into bootloop(only boots into twrp) once while trying to remount /system as rw. But then I figured out SElinux must be disabled. You know what to do if you went into a bootloop, but just take a backup (nandroid backup didn't work for me)
And I also lost all of my data after I flashed stock recovery.
Everything seems to be working fine. But there is a problem with the Nethunter 3.0.
The
Code:
apt-get
does not work.
However, I pinged google.com and I get replies.
So, we need to install metapackages manually. At least for now.
What I did :
1. Download OnePlus One nethunter 3.0 ROM
2. Locate the apks (<nethunter_extracted>/data/app)
3. Install in this order :
• Nhterminal
• VNC
• Nethunter app
4. Open the Nethunter app and install the chroot
( I selected full chroot, however, you may choose minimal chroot too instead )
5. From any root explorer, we need to copy the files that are under /data/data/com.offsec.nethunter/files/scripts/*
to
/system/bin
(If you don't find the .../files/scripts, open Nethunter app and try again)
6. After copying the files to /system/bin,
There are three important files :
•bootkali
•bootkali_bash
•bootkali_login
We need to symlink these ↑
Important : we need to make the system writable first.
Run from AndroidSU shell:
Code:
#setenforce 0
Code:
#mount -o rw,remount /system
Then, linking :
Code:
ln -s /data/data/com.offsec.nethunter/files/scripts/bootkali /system/bin/bootkali
Code:
ln -s /data/data/com.offsec.nethunter/files/scripts/bootkali_bash /system/bin/bootkali_bash
Code:
ln -s /data/data/com.offsec.nethunter/files/scripts/bootkali_login /system/bin/bootkali_login
You can remount /system to read-only if you wish to.
7. Next, install BusyBox to /system/bin
Usually, it is installed to /su/xbin.
But we need to install to /system/bin too.
This step is necessary.
8. Now, the Kali shell works fine.
Try running
Code:
#bootkali
in AndroidSU shell and you should be in the Kali shell
You can also open Nhterminal app and select Kali.
9. You may install the other apks now.
Enjoy ~ !!

Unable to start monitor mode error showing pls rply
Whats the problem
---------- Post added at 02:39 AM ---------- Previous post was at 02:16 AM ----------
I m using oneplus 5 naughat 7.1 rom and kali nethunter installed.
But problem in monitor mode
Error:Newly created monitor mode interface wlan0mon is *NOT* in monitor mode.
Removing non-monitor wlan0mon interface...
WARNING: unable to start monitor mode, please run "airmon-ng check kill"
I m trying this command 'airmon-ng check kill' but same problem

xposed framework for huawei p10 lite?

Recently it has come out xposed framework by rovo89 for android N:
https://forum.xda-developers.com/showthread.php?t=3034811
Has anyone tried it on the p10 lite, with rom stock + recovery + root? or in some other device huawei with rom stock and emui 6?
Thanks in advance.

I've tried it and it works fine, but since I rooted my p10 and installed xposed my battery started to drain noticeably faster, so I went back to stock.

I use xposed with magisk v14 and no battery drain(I think)

Testing and work fine.
Some times, after reboot, xposed in disabled. Need run this attached script on init, in /su/su.d

mpiero11 said:
Testing and work fine.
Some times, after reboot, xposed in disabled. Need run this attached script on init, in /su/du.d
Click to expand...
Click to collapse
I get this too, but to fix I just untick all enabled modules in xposed, reboot, enable modules again and reboot again.

hayabusa2yk said:
I use xposed with magisk v14 and no battery drain(I think)
Click to expand...
Click to collapse
How did you install magisk?

plerohero said:
How did you install magisk?
Click to expand...
Click to collapse
Just flash in TWRP
sorry for my bad English

mpiero11 said:
Testing and work fine.
Some times, after reboot, xposed in disabled. Need run this attached script on init, in /su/su.d
Click to expand...
Click to collapse
I am facing the same problem and when I tried to use your solution its not working either.
I somehow able to found out the error (by using init.d scripts app):
Path is not correct for
/data/user_de/0/de.robv.android.xposed.installer/conf/enabled.modules.list
/data/user_de/0/de.robv.android.xposed.installer/conf/modules.list
On checking the path appears to be correct. Then whats the issue here? Please guide.
My P10-Lite is rooted. So I can see the path actually exists in my phone's root folder.
Thanks

mzeeshan2 said:
I am facing the same problem and when I tried to use your solution its not working either.
I somehow able to found out the error (by using init.d scripts app):
Path is not correct for
/data/user_de/0/de.robv.android.xposed.installer/conf/enabled.modules.list
/data/user_de/0/de.robv.android.xposed.installer/conf/modules.list
On checking the path appears to be correct. Then whats the issue here? Please guide.
My P10-Lite is rooted. So I can see the path actually exists in my phone's root folder.
Thanks
Click to expand...
Click to collapse
Change permisions for .sh file, chmod 777 to script, reboot and enjoy.
No problems for my.