Related
I tried to install V4A on my HTC One with 5.0 GPE but failed.
I had installed something which completely messed up the audio, nothing worked!
So here is a flashable zip which should solve most audio issues.
It is tested with the Android 5 GPE ROM for the HTC One M7.
in short, this will undo any audio mods or hacks.
If you install Viper4Android 2 things are changed on your device:
1) It adds 2 sections to your /etc/audio_effects.conf file
libraries {
Code:
v4a_fx {
path /system/lib/soundfx/libv4a_fx_ics.so
}
and
effects {
Code:
v4a_standard_fx {
library v4a_fx
uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b
}
2) copies the driver to /system/lib/soundfx/libv4a_fx_ics.so
This driver can differ in name.
If you uninstall Viper4Android you need to uninstall the driver first from the Viper4Android settings menu. After that uninstall the Viper4Android app.
But you still need to check the /etc/audio_effects.conf file or restore your original one.
Cheers
Hi all.
Is anyone using Viper4Android with SElinux enforcing mode?
I was able to make V4A run in SElinux enforcing but found out that doing so, breaks the microphone during a call.
Example:
1. Perform a call
2. Switch from handset to Speaker mode <- so far so good
3. Switch back to handset <- the other party can't hear you anymore.
4. Switch back to speaker mode <- the other party can hear you again
The way I made V4A work in SElinux enforcing is by adding these lines to the '50Viper.sh' file under the 'su.d' folder.
Code:
#! /system/bin/sh
/su/bin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { execute };"
supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"
If you are running V4A in SElinux enforcing, do you encounter the issue I described?
gil80 said:
Hi all.
Is anyone using Viper4Android with SElinux enforcing mode?
I was able to make V4A run in SElinux enforcing but found out that doing so, breaks the microphone during a call.
Example:
1. Perform a call
2. Switch from handset to Speaker mode <- so far so good
3. Switch back to handset <- the other party can't hear you anymore.
4. Switch back to speaker mode <- the other party can hear you again
The way I made V4A work in SElinux enforcing is by adding these lines to the '50Viper.sh' file under the 'su.d' folder.
Code:
#! /system/bin/sh
/su/bin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { execute };"
supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"
If you are running V4A in SElinux enforcing, do you encounter the issue I described?
Click to expand...
Click to collapse
I'm using V4A from this thread
http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
I'm using ViPERAudio 4.7.1 Stock.zip (COS13.1.2 + SuperSU) but you can use any of them in Enforcing mode. The only caveat is that it works in Enforcing mode only when you use SuperSU, if you use SuperUser such as in CM13 Nightlies you have to change SELinux to Permissive. There is no configuration required just SuperSU. Flash the zips and enjoy V4A but read info in that thread if you have any questions, have never had any issues so far
Renosh said:
I'm using V4A from this thread
http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
I'm using ViPERAudio 4.7.1 Stock.zip (COS13.1.2 + SuperSU) but you can use any of them in Enforcing mode. The only caveat is that it works in Enforcing mode only when you use SuperSU, if you use SuperUser such as in CM13 Nightlies you have to change SELinux to Permissive. There is no configuration required just SuperSU. Flash the zips and enjoy V4A but read info in that thread if you have any questions, have never had any issues so far
Click to expand...
Click to collapse
I know, I use SuperSU as well.
The OP of the thread you gave, has actually incorporated the code I've posted in my OP to his ZIP files.
See my post here: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137/post66027160#post66027160
After my post he used this to apply this fix on the rest of the V4A variants.
But I'm not taking credit for the fix. I found it elsewhere.
Have you tried to make a call and switch back and forward with speaker mode and handset?
Did you do any change to your mixer_path.xml or build.prop?
gil80 said:
I know, I use SuperSU as well.
The OP of the thread you gave, has actually incorporated the code I've posted in my OP to his ZIP files.
See my post here: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137/post66027160#post66027160
After my post he used this to apply this fix on the rest of the V4A variants.
But I'm not taking credit for the fix. I found it elsewhere.
Have you tried to make a call and switch back and forward with speaker mode and handset?
Did you do any change to your mixer_path.xml or build.prop?
Click to expand...
Click to collapse
Zero changes to the mixer_path.xml
Completely stock except for root, removing ModioFX from system and using a different hosts file (Adaway) and installing V4A.
I haven't had a single issue with calls via speaker phone or handset for the past couple of days on current ROM. I've used a similar set up for months in various ROMs and never noticed or received reports of issues either
can you please see if you can find your 50viper.sh file under system/su.d and post it?
Thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know that there is many tools apps etc to disable or hide SU.
I decide to make this just because those did't work on my device back in 2016 and or CyanogenMod/LineageOS ROM that I use, so I assume this happens to other in CyanogenMod/LineageOS users too, I start this thread and made this app that can help to pass a safety net test on any rooted device (hide SU only when using Lineage add on SU) as it is no longer just a SU hider app is little more.
This is only to CyanogenMod/LineageOS SU binary aka CM-SU, the CM-SU only works with CyanogenMod/LineageOS ROM's and ROM that use they source code as base
That can be Download from Lineageos download page click here to see
No it doesn't work with SUPERSU or any other SU that is not base on CM-SU
No it doesn't support Xposed Hide, if you use Xposed you can't pass safety net with CM-SU.
No it doesn't support AB devices (devices with two system partition) that can't be mounted as rw dynamically in android.
What is iSu?
A simple app to help the user to pass safety net test on CyanogenMod/LineageOS or any CyanogenMod/LineageOS base ROM's.
I personally test this on Marshmallow and Nougat CM base ROM's it works 100%, it also Supports Lollipop but Kit Kat and older OS's are not supported.
How To use it?
read Installation instructions, download Folder with instructions on the bottom of the post
Download and Install the app as a normal app, if you wanna the full app support, use a ROM with the supported SU version (CM-SU), download Folder with instructions on the bottom of the post
if on Marshmallow or Lollipop flash the zip (iSu_kernel_Reboot_Support), download Folder with instructions on the bottom of the post
Learn how to use the app, below instructions
How To pass safety net?
Su deactivated (demanding)
SELinux enforced (demanding)
Android debugging deactivated (not demanding for all devices)
Props known props or special props can't have a red warning (demanding)
Below are some samples of fails or pass:
PASS
*Android debugging only affects some devices, disable if you don't need it.
*In props if there is props with a red warning that may be the reason of the fail if SU and SELinux is set as the above.
If you have SU active you will always fail
FAIL everything
*Fail because SU is Activated
If you have SU deactivate you will not always pass
FAIL everything 2
*Fail because SELinux is in Permissive
If you have SU and SELinux on a correct position you may not always PASS, because some props cause fail of ctsProfile
FAIL ctsProfile
*The above fail because ro.boot.verifiedbootstate
*Some props may or may not cause full FAILS or a FAIL of ctsProfile
Detailed app function description?
The app is divided in 5 tabs (Checks, Controls, Monitor, Props and settings), plus widgets and tiles, bellow a detailed description:
Checks
Basic information about the application, the main start tab if it show a red warning on the SU state options because yours current SU is not supported and the app will work with limited functionality.
SU State, current user SU version and reboot support status
Update, Check for iSu updates
Safety Net test, Let the user try the safety net status, in case of fail it will tell what fail and current SU, SELinux and ADB state as those if on wrong position will cause the fail
Log, Generate a full logs of information about the device and how the app is running, in case of a problem share the log.zip on the thread and explain the problem
Controls
The main control tab, be aware there is extras actions for this controllers in settings tab
SU, Changes and show SU state. This function only works with CM-SU
SELinux, Changes and show SELinux state, plus allow user to fake enforce Selinux for devices that have problems when running with SELinux enforced
Android debugging, Changes and show Android debugging state
Tasker, Info about how to control the app using Tasker
Monitor
This tab only works with CM-SU
A Service to monitor when foreground app starts then, activate or deactivate SU and SELinux or ADB (base on settings options).
App monitor, Status and access to accessibility service.
Don't Care List, Select the apps that will not have effect to App monitor, when a foreground app start.
Deactivate SU, Select the apps that will deactivate SU when started
Automatic Re-Activate SU, If this switch is on, will automatic active SU when leave the app that deactivated SU
Activated SU, Select the apps that will activate SU when started
Automatic Re-Deactivate SU, If this switch is on, will automatic deactivate SU when leave the app that activated SU
Props
A tab to change the value of any ro.prop or read only prop, using the resetprop applets from magisk to make a tool to modify on the go any ro.prop, there is also a list of known props that can cause safety net fail they safe or unsafe value
Read Only editor, List of ro props and the ro props changed by the user
Special Props, Known props that has a complicated value that can't be define as OK or NOK
Known props list, just explanation about safe, unsafe or unknow values
Force set all Known props, Click to force all Known Props to the chosen value
Known props, the real list of known props and they current value click to change
Settings
Basic application setting, extra controls and notifications
Application, Allow to force language to English
SU, Extra SU options allow to deactivate it on boot This function only works with CM-SU
App monitor, Allow delays to app monitor This function only works with CM-SU
Props, Allow to apply props changes on boot
Notifications, Enable disable notifications or toast's of SU state This function only works with CM-SU
SELinux, Extra control of SELinux state base on SU is state changes This function only works with CM-SU
Android debugging, Extra control of Android debugging state base on SU is state changes This function only works with CM-SU
Widgets and tiles
The app has widget and tiles that can be used to control the app Controls
Widgets They only work with CM-SU for SU changes
Mono Widget, Allow to change and read SU state, it also work with Settings extra controls (Notifications, SELinux and Android debugging)
Dual Widget, Allow to change and read SU or SELinux state, it also work with Settings extra controls (Notifications, SELinux and Android debugging)
Tiles Only visible on Nougat
SU tile, Allow to change and read SU state, it also work with Settings extra controls (Notifications, SELinux and Android debugging)
iSu tile, Click to open the app
Installation instructions:
Download Folder: Click Here
There is three files, description:
iSu_X_x.apk Install the apk as a normal app.
iSu_kernel_Reboot_Support_V_X_x_and_up.zip Flashable zip, flash only if you are running Marshmallow or Lollipop
Explanation of the above, iSu only need flashable reboot support for Marshmallow or older OS.
The kernel reboot support , this files prevents from losing SU access after a reboot with SU deactivated.
Old reboot support, in case the current fail
Old reboot support download Folder: Click Here[/B]
iSu_kernel_Reboot_Support_V_X_x_and_up_Enforcing.zip Flashable zip, use only one zip, if running Marshmallow or older
iSu_kernel_Reboot_Support_V_X_x_and_up_Permissive.zip Flashable zip, use only one zip, if running Marshmallow or older
Explanation of the above, iSu only need flashable reboot support for Marshmallow or older OS.
The kernel reboot support use only one(enforcing or permissive), this files prevents from losing SU access after a reboot with SU deactivated.
Use the one base on yours current Selinux status to check on your device look in settings > About a phone > SELinux Status if is enforcing or permissive, some CM ROM Run with selinux in Permissive so check yours.
Be aware!!
Updating CM/Los nightly or any ROM update of any CM/Los base ROM will remove the changes made by the zip, so is need to re-flash those .zip after any ROM update, may be need to do it also with some custom kernel from developer that use a boot.img to share the kernel(check yours kernel zip content to know).
If you forget to flash the .zip in a update and have lost ROOT don't worry just go back to recovery and flash it after the reboot all will be good.
The below are obsolete after V3.6 of the app, see old_version folder in main download folder for those files just reference no longer supported
iSu_kernel_cmdline_Patch_V_X_x_and_up.zip
The kernel_cmdline is only need to some devices that after deactivating SU with the app still can't pass the safety check, Google is using kernel and bootloader arguments to determined that the user modify the stock SW(AKA is using custom ROM) and prevent from passing as "safe", this add extra safe arguments to cmline and help to achieve the pass current it only support some device (Nexus and Motorola, maybe other post on the thread device/vendor if the zip help you)
iSu_kernel_defaultprop_Patch_V_X_x_and_up.zip
This is only for those that have apps that use rootbeer SU detection...
explain in this post (Click here).
After flashing defaultprop_Patch zip the user will no longer have access to the option in Settings > Developer options > Root access
But that is not a problem as the same zip will enable root by default so you can use without changing that option.
XDA:DevDB Information
iSu, App for all CyanogenMod/LineageOS devices (see above for details)
Developer donation link:
To donate via paypal click here
No other donation option is available.
Contributors
All Contributors can be see in github click here
fgl27, I use osm0sis Anykernel2 for the kernel zip
App Source Code: https://github.com/fgl27/isu
Extra App credits: iSu readme credits
Version Information
Status: Stable
Current Stable Version: Check latest version in Download folder
Changelog
Created 2016-Oct-03
Last Updated Check latest version
Changelog
Last app version Click to Download
Awesome work! Glad I accidentally stumbled on to this. Magisk stopped working to hide root but this is still good. Woot!:good:
edit: In your isu.sh, shouldn't the end of the script be:
Code:
mount -o ro,remount /system
# instead of
umount /system;
edit 2: For anyone who wants to build their device/kernel with support baked in, so they don't have to patch, I distilled the changes down from your git and created this patch:
https://github.com/blastagator/cm_d...mmit/79118c58fee32d10aa75464ee95751c7e6b8fdc5
This should be a good basis for others to manually patch in support. Working well on my custom cm13 builds.
blastagator said:
Awesome work! Glad I accidentally stumbled on to this. Magisk stopped working to hide root but this is still good. Woot!:good:
edit: In your isu.sh, shouldn't the end of the script be:
Code:
mount -o ro,remount /system
# instead of
umount /system;
edit 2: For anyone who wants to build their device/kernel with support baked in, so they don't have to patch, I distilled the changes down from your git and created this patch:
https://github.com/blastagator/cm_d...mmit/79118c58fee32d10aa75464ee95751c7e6b8fdc5
This should be a good basis for others to manually patch in support. Working well on my custom cm13 builds.
Click to expand...
Click to collapse
Thanks. For me was similar, magisk did not support my device so user complain to me about support as I did not manage to make magisk to work on my device I manage to make this that seems to be 100% for the most none rooted app.
regards the RW/RO
Theoretically yes but things was a little odd when I first start test for this... for simple reason if we don't mount system as RW we can "hide" or "un-hide" SU because is need to move it and system boot in RO, and if leave it mounted as RW safety net check will not be successful even if SU is hide, but after some safety net update on the google side mount it as RO at the end was not working in the .sh and the unmout was, maybe was some other related problem but it work so I did not change...
So I keep the unmount did not test any more after, and in the java code every time the switch is use it start with RW and ends with RO and that does the trick...
I have update the reboot support and the app for Nougat, Selinux is a little more restricted on N and I did not had the time to test a universal .zip to support N as the changes I did in the ROM I build are a little more time demanding to make it right, or not I really only have my build to test on my devices as N is just starting there is no other ROM, I really need another ROM that doesn't have any of my changes to test and really make it fully work with a simple .zip
But every things is also fully working on N CM did not change the SU binary, safety net, pokemon and payment app are all good, at least for know...
:good:
I update the project for N but I only manage to fully test on my ROM so if any one try and have problem read #3 post and report on the thread.
Hey guys, just tried out this in my Redmi Note 2 Prime with Bule's (cleaned) MoKee ROM CM12.1, and worked great, until now, because says, when I'm going to "hide" su, that the "su state change fail" Don't know for what it was, but if you can help me solving this, I would be grateful
Bhb thank you, using on my daughter's xt1254 phone now which runs cm 13.
---------- Post added at 03:16 AM ---------- Previous post was at 03:12 AM ----------
Shadow646 said:
Hey guys, just tried out this in my Redmi Note 2 Prime with Bule's (cleaned) MoKee ROM CM12.1, and worked great, until now, because says, when I'm going to "hide" su, that the "su state change fail" Don't know for what it was, but if you can help me solving this, I would be grateful
Click to expand...
Click to collapse
This is the reason for the kernel hack.
Without it you can lose root.
Dirty flash your ROM and if the kernel hack won't work
Then just be sure to set everything back to normal before any reboots.
I "THINK" then you would be okay.
mrkhigh said:
Bhb thank you, using on my daughter's xt1254 phone now which runs cm 13.
---------- Post added at 03:16 AM ---------- Previous post was at 03:12 AM ----------
This is the reason for the kernel hack.
Without it you can lose root.
Dirty flash your ROM and if the kernel hack won't work
Then just be sure to set everything back to normal before any reboots.
I "THINK" then you would be okay.
Click to expand...
Click to collapse
Yeah, I did that, but dunno if was because of that it failed, or not... I'm fine for now, reverting it whenever I close the game, I put su back Maybe it was because I was trying to cheat on PoGO, and didn't work with Fly GPS, and uninstalling the app in a bad way provoked that I will do a nandroid and try again
Edit
Shadow646 said:
Yeah, I did that, but dunno if was because of that it failed, or not... I'm fine for now, reverting it whenever I close the game, I put su back Maybe it was because I was trying to cheat on PoGO, and didn't work with Fly GPS, and uninstalling the app in a bad way provoked that I will do a nandroid and try again
Click to expand...
Click to collapse
Are you using the kernel support, have you flash it in TWRP?
The app work in CM under 13 is ok, but the kernel support I have not tested in older them CM13, so I'm curious to know if it works, the only way to really test is to deactivate SU and then reboot if you have SU active after or if the app can activate SU after then is all good if you don't have and or can't activate in the app there is a problem...
the basic function of the kernel support is to have no problem after a reboot when you had disable SU, just like @mrkhigh point it out
So if you reboot with that off let me know the behavior if you can use and activate SU will be need a dirty flash of the ROM you are using...
When I have some time I will do some proper test in cm12.1 and only cm12.1 because my devices can only run that there is no older OS for me...
:good:
I update the app and kernel support to 1.5
Changelog and Download link first page post 2 and 3
In Downloads I add two kernel support one with selinux after boot in Permissive and other with Enforcing just check the zip name and check your device in settings > About a phone SELinux Status is using enforcing or permissive, this is need as some CM ROM Run with selinux in Permissive.
Any problem let me know.
bhb27 said:
Are you using the kernel support, have you flash it in TWRP?
The app work in CM under 13 is ok, but the kernel support I have not tested in older them CM13, so I'm curious to know if it works, the only way to really test is to deactivate SU and then reboot if you have SU active after or if the app can activate SU after then is all good if you don't have and or can't activate in the app there is a problem...
the basic function of the kernel support is to have no problem after a reboot when you had disable SU, just like @mrkhigh point it out
So if you reboot with that off let me know the behavior if you can use and activate SU will be need a dirty flash of the ROM you are using...
When I have some time I will do some proper test in cm12.1 and only cm12.1 because my devices can only run that there is no older OS for me...
:good:
Click to expand...
Click to collapse
Well, now I reinstalled all just because I messed all up, again.
Turned off the phone with root of and no kernel support, tried to flash kernel support, and that would be ok, if I didn't "flash SuperSu" stuff when rebooting :silly:. That made the switch work, but didn't pass validation when using PoGO.
Then, had to reflash ROM, delete chinese stuff, reinstall all of my apps, and iSu, of course, while noticing that there was an update; installed the app and new permissive kernel, and from now, so far so good
Hope that I will keep it clean and working. Thanks for the suggestions btw
@bhb27 Installed and working on sprint htc m8 cm13. The kernel mod is installed but untested.
Great work! I can confirm it worked in my moto g 2014 running cyanogenmod 14.1 official. Pokémon go worked!
Thanks dev!
At last something that works! Running CM14.1 rom on my OnePlus 3 and it works!
Pokémon Go go go...
Thx dev!
HC4Life said:
At last something that works! Running CM14.1 rom on my OnePlus 3 and it works!
Pokémon Go go go...
Thx dev!
Click to expand...
Click to collapse
Now go find that ditto.
Would there be anyway to automatically trigger this for certain apps? This is the first root hiding method i've found that actually tricks Barclays Mobile Banking. Great work
LJAM96 said:
Would there be anyway to automatically trigger this for certain apps? This is the first root hiding method i've found that actually tricks Barclays Mobile Banking. Great work
Click to expand...
Click to collapse
:good:
No there isn't yet, is not all that hard to make but is timing I had no time for the last week to start the implementation, but is in my plans, probably still do this year.
BTW is always nice to be remember that the app can be used for other then to catch monsters :laugh:
You might want to consider removing selinux enforce from the kernel service script. If the ROM doesn't have proper SE policy, it could gum things up. I think the switch in the app is probably sufficient in the event user needs to toggle Enforcing to run an app. I don't believe enforcing on boot toggles anything, but I could be wrong since my ROM boots enforcing. Safety Net actually keeps working for me if I toggle to permissive.
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for LineageOS 17.1 builds for OnePlus 3/3T. The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Tips:
You need at least OxygenOS 9.0.2 firmware, otherwise you'll get error 7 when installing the zip. Latest firmware is recommended.
Installation:
First time flashing LineageOS 17.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (Official TWRP 3.4+ is highly recommended: https://dl.twrp.me/oneplus3/)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package
Reboot
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
......
Changelog:
2019.10.24
Initial release
2019.10.25
Sync latest source
Fix bluetooth
2019.11.20
Sync latest source
Fix wifi display
Ship Snap
Fix vulkan graphics
Pass safetynet
Fix crash of some native services
2019.12.31
Sync latest source
SELiunx working in enforcing mode now
Update kernel to LA.UM.8.6.r1-02900-89xx.0
Update blobs from OOS 9.0.6
Fix suspend when AOD is on
Happy new year!
2020.1.12
Sync latest source
Fix ril of the last build
Update blobs from LA.UM.8.6.r1-02900-89xx.0
Add backuptools
Other trivial fixes
2020.4.2
Official nightlies started
Download:
https://download.lineageos.org/oneplus3
XDA:DevDB Information
LineageOS, ROM for the OnePlus 3
Contributors
dianlujitao
ROM OS Version: Android 10
Version Information
Status: Nightly
Created 2019-10-24
Last Updated 2020-06-26
Any recommendations which gapps to use?
Why not the official ones? https://sourceforge.net/projects/opengapps/files/arm64/beta/20191006/
is this with kernel 4.4?
helderfp said:
is this with kernel 4.4?
Click to expand...
Click to collapse
https://github.com/LineageOS/android_kernel_oneplus_msm8996/blob/lineage-17.0/Makefile#L1-L3
helderfp said:
is this with kernel 4.4?
Click to expand...
Click to collapse
No, 3.18.120 like all other Q roms for our phone.
Our phone doesn't support kernel 4,x. You need OnePlus 5 or above...
dianlujitao said:
Important information:
This thread is for LineageOS 16.0 builds for OnePlus 3/3T.
Click to expand...
Click to collapse
OP needs some changes its for LOS 17 instead of 16 [emoji3][emoji39]
Sent from my ONEPLUS A3003 using Tapatalk
Biggest problem I've found is Bluetooth. It connects and disconnects continuously until it crashes, so it's not usable. The status bar icons are not on the left but rather center-left once BT is activated.
Master_TC said:
No, 3.18.120 like all other Q roms for our phone.
Our phone doesn't support kernel 4,x. You need OnePlus 5 or above...
Click to expand...
Click to collapse
@nvertigo67 is right :good: , but there're others SnapDragon 820 devices, they've running a stable 4.4/4.9 Kernel long time ago, so it be could be possible.
https://github.com/YaroST12/Z2_Kernel/tree/4.4-eas-1.4
https://github.com/AOSiP-Devices/kernel_zuk_msm8996/tree/staging/pie-4.9
@mady51 said one time, he tried to compile a 4.X ver. for op3
mady51 said:
ya i built it once but it didn't booted. after that didn't spent time on it. may be ill give it another try soon
Click to expand...
Click to collapse
Anyway amazing work @dianlujitao you're one of our heroes ???
Viper The Ripper said:
@nvertigo67 is right :good: , but there're others SnapDragon 820 devices, they've running a stable 4.4/4.9 Kernel long time ago, so it be could be possible.
https://github.com/YaroST12/Z2_Kernel/tree/4.4-eas-1.4
https://github.com/AOSiP-Devices/kernel_zuk_msm8996/tree/staging/pie-4.9
@mady51 said one time, he tried to compile a 4.X ver. for op3
Anyway amazing work @dianlujitao you're one of our heroes ???
Click to expand...
Click to collapse
https://github.com/dianlujitao/android_kernel_oneplus_msm8996 @dianlujitao did bring up a 4.4 kernel but it has issues.
Jus asked because of this
mvalda01 said:
Biggest problem I've found is Bluetooth. It connects and disconnects continuously until it crashes, so it's not usable. The status bar icons are not on the left but rather center-left once BT is activated.
Click to expand...
Click to collapse
Can you provide more info such as logs, my aptx headset works fine here.
Thanks for the effort,nice rom for nice phone.
From Op3 owner
Thanks, @dianlujitao, for this. Great to have Android 10 running on an encrypted phone.
I've been playing around with it all day and here's what I've found so far:
Clean install with Gapps from https://sourceforge.net/projects/opengapps/files/arm64/beta/ and Magisk 20 stable. Once I set the security patch date to 2019-08-01 I passed SafetyNet and was able to set up my credit card with Google Pay.
Missing:
- accent colours in settings>display>style>accent colour, though they are available in settings>developer options>accent colour
- battery text doesn't display
Broken:
- NFC: shows as being permanently on and can't be turned off; doesn't register on terminals
- Gallery shows album images in the Music directory (in Los 16 it ignores them). I've had to add a .nomedia file to the directory.
- settings>display>style>dark mode>Black causes LineageOS Settings to stop
- Digital Wellbeing keeps stopping (logs attached)
- BT connects/disconnects continuously when connected to my car (logs attached)
And that's all the issues I've got at the moment. Everything else is working fine.
I'll have a better idea of battery drain after tonight.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Thanks, @dianlujitao, for this. Great to have Android 10 running on an encrypted phone.
I've been playing around with it all day and here's what I've found so far:
Clean install with Gapps from https://sourceforge.net/projects/opengapps/files/arm64/beta/ and Magisk 20 stable. Once I set the security patch date to 2019-08-01 I passed SafetyNet and was able to set up my credit card with Google Pay.
Missing:
- accent colours in settings>display>style>accent colour, though they are available in settings>developer options>accent colour
- battery text doesn't display
Broken:
- NFC: shows as being permanently on and can't be turned off; doesn't register on terminals
- Gallery shows album images in the Music directory (in Los 16 it ignores them). I've had to add a .nomedia file to the directory.
- settings>display>style>dark mode>Black causes LineageOS Settings to stop
- Digital Wellbeing keeps stopping (logs attached)
- BT connects/disconnects continuously when connected to my car (logs attached)
And that's all the issues I've got at the moment. Everything else is working fine.
I'll have a better idea of battery drain after tonight.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thanks for the report, bluetooth should be fixed in 1025 build, for Digital Wellbeing crash you should probably report to opengapps devs, I'm not sure.
NFC works fine for me, it wound be nice if you could grab related logs.
Well done @dianlujitao!
Thanks for your work @dianlujitao! I'll probably flash next build
@dianlujitao:
I've been trying to compile my own version, as part of my preparations for making the LOS17-based version of my personal custom ROM. I've got an unmodified LOS17 repo, the oneplus3 device tree, and the proprietary blobs repo from TheMuppets (which I had to modify to put WfdCommon into Android.mp and comment it out in Android.mk). It compiles up to a point, where I'm getting this error:
Code:
[ 0% 1/74451] build out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
FAILED: out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 out/host/linux-x86/bin/checkpolicy -M -c 30 -o out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy.conf ) && (out/host/linux-x86/bin/sepolicy-analyze out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp neverallow -w -f out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy_2.conf || ( echo \"\" 1>&2; echo \"sepolicy-analyze failed. This is most likely due to the use\" 1>&2; echo \"of an expanded attribute in a neverallow assertion. Please fix\" 1>&2; echo \"the policy.\" 1>&2; exit 1 ) ) && (touch out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp ) && (mv out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows )"
device/oneplus/oneplus3/sepolicy/hal_lineage_livedisplay_qti.te:3:ERROR 'unknown type hal_lineage_livedisplay_qti' at token ';' on line 83421:
allow hal_lineage_livedisplay_qti sysfs_livedisplay_tuneable:file { { getattr open read ioctl lock map } { open append write lock map } };
# Grant access over LiveDisplay tuneables
checkpolicy: error(s) encountered while parsing configuration
11:38:29 ninja failed with: exit status 1
I'm presuming that, since you're the developer for the oneplus3 variant, you've got things going on behind the scenes that have yet to be committed, and have already worked around this issue (if it is an issue and not something on my end). Not trying to steal your thunder or anything (my custom ROM is solely for my own use), I was just wondering if you had any insights you could offer. If there's any other information you need from me, just ask, I'll be more than happy to provide it.
MJPollard said:
@dianlujitao:
I've been trying to compile my own version, as part of my preparations for making the LOS17-based version of my personal custom ROM. I've got an unmodified LOS17 repo, the oneplus3 device tree, and the proprietary blobs repo from TheMuppets (which I had to modify to put WfdCommon into Android.mp and comment it out in Android.mk). It compiles up to a point, where I'm getting this error:
Code:
[ 0% 1/74451] build out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
FAILED: out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 out/host/linux-x86/bin/checkpolicy -M -c 30 -o out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy.conf ) && (out/host/linux-x86/bin/sepolicy-analyze out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp neverallow -w -f out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy_2.conf || ( echo \"\" 1>&2; echo \"sepolicy-analyze failed. This is most likely due to the use\" 1>&2; echo \"of an expanded attribute in a neverallow assertion. Please fix\" 1>&2; echo \"the policy.\" 1>&2; exit 1 ) ) && (touch out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp ) && (mv out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows )"
device/oneplus/oneplus3/sepolicy/hal_lineage_livedisplay_qti.te:3:ERROR 'unknown type hal_lineage_livedisplay_qti' at token ';' on line 83421:
allow hal_lineage_livedisplay_qti sysfs_livedisplay_tuneable:file { { getattr open read ioctl lock map } { open append write lock map } };
# Grant access over LiveDisplay tuneables
checkpolicy: error(s) encountered while parsing configuration
11:38:29 ninja failed with: exit status 1
I'm presuming that, since you're the developer for the oneplus3 variant, you've got things going on behind the scenes that have yet to be committed, and have already worked around this issue (if it is an issue and not something on my end). Not trying to steal your thunder or anything (my custom ROM is solely for my own use), I was just wondering if you had any insights you could offer. If there's any other information you need from me, just ask, I'll be more than happy to provide it.
Click to expand...
Click to collapse
You need to pick - at least - https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/255737 from https://review.lineageos.org/q/project:LineageOS%2Fandroid_device_oneplus_oneplus3+status:open, maybe all.
There's a good reason why OP calls it an experimental build instead of alpha or beta... Rebuilding experimental needs skilld and patience...
EDIT:
For the blobs commits (i.e. https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/260573 and https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/262330) see also https://github.com/dianlujitao/proprietary_vendor_oneplus/commits/lineage-17.0 .
BillGoss said:
- Digital Wellbeing keeps stopping (logs attached)
Click to expand...
Click to collapse
On some other Android 10 ROM, force stopping, disabling and then re-enabling solved this issue.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ALYNX Nethunter Kernel for Pixel 4a - [Stock][Android 12/12L]
What is Nethunter ?
Kali NetHunter is a free & Open-source Mobile Penetration Testing Platform for Android devices, based on Kali Linux.
Click to expand...
Click to collapse
Code:
I'm not responsible for bricked devices, dead SD cards.
Do some research if you have any concerns about features included in this Kernel.
About the kernel :
Kernel is based on stock sources compiled using clang 14.0.7
Features:
Internal Wifi Monitor Mode Support (packet injection doesn't work as it is based on qcacld-3.0 which is not capable of packet injection yet)
HID gadget keyboard/mouse
USB WiFi, mac80211 (Monitor mode, packet capture, packet injection) [Compatibility List]
RTL88XXAU USB WIFI Support
RTL8188EUS USB WIFI Support
ATH9K_HTC USB WIFI Support
Ethernet Support
Bluetooth USB Support
SDR Support
BadUSB
warning: please do not update magisk after flashing the kernel, you can update the magisk before flashing the kernel.
Installation:
Download the zip file containing the kernel .
Flash the zip using twrp or franco kernel manager (Flashing the kernel/zip will preserve the root)
Install Busybox
Download Wireless_firmware.zip open Magisk and install the zip as Magisk module
Install Nethunter store
Install Nethunter app & Nethunter terminal from Nethunter store
Open Nethunter app & Download the full chroot kalifs within the app and let the app setup everything. After it finishes it'll start the chroot automatically.
Update the sources with apt-get update && apt-get upgrade in the chroot using nethunter terminal
Reboot the device
Note: if nethunter app crashes open any android terminal in su environment and paste the following.
Code:
pm grant com.offsec.nethunter android.permission.ACCESS_FINE_LOCATION
pm grant com.offsec.nethunter android.permission.ACCESS_COARSE_LOCATION
pm grant com.offsec.nethunter android.permission.READ_EXTERNAL_STORAGE
pm grant com.offsec.nethunter android.permission.WRITE_EXTERNAL_STORAGE
pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT
pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT_SU
pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT_NH
pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT_NH_LOGIN
Screenshots:
Extra
if you want to replace nethunter terminal with termux (not completely nethunter main app will still launch nethunter terminal everytime for any operation but you can access kali chroot environment from termux.
(i know nethunter terminal sucks)
Follow these steps to access the environment from termux:
Install termux from f-droid or from nethunter store
Open termux and install root repo using pkg update && pkg install root-repo tsu wget
Download the script from termux using wget https://raw.githubusercontent.com/name-is-cipher/boot-nethunter/main/install_boot-kali.sh
chmod +x install_boot-kali.sh && ./install_boot-kali.sh
let it setup everything.
restart termux and type boot-kali to access the nethunter chroot environment
if you like my work give this post a like : )
Credits:
Team Kali For Nethunter
momojura For his help
Special Thanks to Nfury00701 for testing the kernel.
XDA:DevDB Information
Alynx Nethunter For Pixel 4a Sunfish
Contributors: V3rB0se
Source Code: https://github.com/V3rB0se/Alynx-nethunter-sunfish
Version Information
Status: Stable
Stable Release Date: 03/07/2022
Created 03/07/2022
Last Updated 23/08/2022
yes ! FINALLY..
Thank you @V3rB0se
Android 13 Update Changelog: [2022/08/23]
Alynx 2.0
- Upstream Android 13 (Blu Spark Kernel)
- Bluetooth Support
- Ethernet Support
- Fix RTL 8XXX SL (Replaced)
- All the goodies from Blu Spark Kernel
Thanks to @eng.stk for his amazing work.
Downloads & Links :
- Flashable Zip: https://mega.nz/file/OEYUkALL#BsMDy6Gs7gDV7CpO46wOQPI-0uC-fnNJ0C1nyPXI3Rc
This is awesome, thanks a ton! Working on latest CalyxOS (Pixel 4a ofc)
Haven't had much time for testing but so far Duckhunter is working. Rucky complains about the kernel for some reason, though... Edit: Nevermind, Rucky works now. I think it just needed a reboot lol
Also, what do you mean don't update Magisk? Should I just re-flash the kernel after updating Magisk? I'm going to have to update at some point.
BrightShard said:
This is awesome, thanks a ton! Working on latest CalyxOS (Pixel 4a ofc)
Haven't had much time for testing but so far Duckhunter is working. Rucky complains about the kernel for some reason, though... Edit: Nevermind, Rucky works now. I think it just needed a reboot lol
Also, what do you mean don't update Magisk? Should I just re-flash the kernel after updating Magisk? I'm going to have to update at some point.
Click to expand...
Click to collapse
its just a warning. because when i tried to update the magisk to v25 it went into bootloop so i had to setup everything. You can visit my pixel 3 nethunter thread. I don't know if it's different from pixel 4 or maybe it was just the v25 update, but you can try to update the magisk and see what happens.
V3rB0se said:
Yeah its just a warning. because when i tried to update the magisk to v25 it went into bootloop so i had to setup everything. You can visit my pixel 3 nethunter thread. I don't know if it's different from pixel 4 or maybe it was just the v25 update, but you can try to update the magisk and see what happens.
Click to expand...
Click to collapse
Ah, got it. I flashed the kernel with the v25 update already installed, so I can't test it, but if another version comes out I will
Man I feel dumb I am sorry I didn't see your message man.
Can confirm it also works on
lineage-19.1-20220707
d33dvb said:
Man I feel dumb I am sorry I didn't see your message man.
Click to expand...
Click to collapse
no worries i just wanted to test the kernel. i thought maybe you could help with test builds since i don't own the device.
Can you add support for TL-WN727N.
Have you included all the kernel modules?
Hritik utekar said:
Have you included all the kernel modules?
Click to expand...
Click to collapse
everything (that is necessary for nethunter to work) is included in the kernel.. should be working fine.
Do you have oneplus8t kernel for android 13 with nethunter support?
V3rB0se said:
Android 13 Update Changelog: [2022/08/23]
Alynx 2.0
- Upstream Android 13 (Blu Spark Kernel)
- Bluetooth Support
- Ethernet Support
- Fix RTL 8XXX SL (Replaced)
- All the goodies from Blu Spark Kernel
Thanks to @eng.stk for his amazing work.
Downloads & Links :
- Flashable Zip: https://mega.nz/file/OEYUkALL#BsMDy6Gs7gDV7CpO46wOQPI-0uC-fnNJ0C1nyPXI3Rc
Click to expand...
Click to collapse
Nice work.. However, after flashing this one with TWRP 3.7.0_12-0, I cannot boot on slot A. Just slot B where TWRP is. So I'm stuck on TWRP for now.
Any idea about what went wrong? Or what are the next steps you would recommend to troubleshoot?
Thanks!
LABuse56 said:
Nice work.. However, after flashing this one with TWRP 3.7.0_12-0, I cannot boot on slot A. Just slot B where TWRP is. So I'm stuck on TWRP for now.
Any idea about what went wrong? Or what are the next steps you would recommend to troubleshoot?
Thanks!
Click to expand...
Click to collapse
Flash stock kernel and then try using ex kernel manager or franco kernel manager to flash the kernel.
V3rB0se said:
Flash stock kernel and then try using ex kernel manager or franco kernel manager to flash the kernel.
Click to expand...
Click to collapse
I don't know what the #@$ I need with TWRP.. Usually I have no pbs.... But thanks! I worked perfect with Franco... I might use it instead in the future!
There is no RTL88XXAU and RTL8188EUS USB WIFI Support.
My wifi cards are not detected.
You can also add support for internal blutooth as is very easy
cr4sh-lab said:
There is no RTL88XXAU and RTL8188EUS USB WIFI Support.
My wifi cards are not detected.
You can also add support for internal blutooth as is very easy
Click to expand...
Click to collapse
Rtl8188EUS is in there idk why it's not working for you.
V3rB0se said:
Rtl8188EUS is in there idk why it's not working for you.
Click to expand...
Click to collapse
Solution: did my own kernel instead
Hi, new to the forum and the world of rooted devices. I've Just installed on Pixel 4a (4G) Android 13; all is working well, as far as I can tell; thank you.
A couple of issues though; my Atheros chipset is not working (AR5271, I think); my 2800usb, on the other hand, is working well.
The other issue is the boot animation. There is no */system/media* directory and I cannot find the actual media directory (again, I am using a Pixel 4a (4G). On these issues, any assistance would be greatly appreciated.