Related
Please read this post in detail to know all the details about viper4arise and the great team behind A.R.I.S.E
Sound Systems™ (Auditory Research in Sound Enhancement™ ).
https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
I have installed SwanSong and the sound is amazing. SwanSong have an aroma interface during the installation in TWRP and it will be easy for you to install it with all the guides inside the installer. Here are the steps I have done to install it (Thanks to @tywinlannister).
1. Install the BusyBox app and also install BusyBox inside it.
2. Set SELinux to be permissive. (This is important, but you can do it during the installation of SwanSong).
3. Download Arise Sound Systems zip from the link https://www.androidfilehost.com/?w=files&flid=151719
(Click Aroma & look for ARISE+Deuteronomy+X.XX+Modular+AROMA+Installer.zip )
4. Reboot to TWRP and flash the downloaded file. Aroma will start and guide you through the installation process. (There will be many number of modules which will make you confused as to whether it is needed or not. Refer the below recommended setup to get the best experience).
4. Reboot to system.
5. Configure the mods.
6. Reboot again.
This is the recommended setup from the developer itself while flashing SwanSong in Aroma. (Thanks to guitardedhero).
I would recommend Core (mandatory, if not already installed), ViPER4Arise™ 2.5.0.5, Profiles, Arkamys™, ICEsound™, Skip Config and Preset, MusicFX (unless you know it's already installed, this script will leave an existing MusicFX installation intact and end, just in case), permissive (do not, if Enforcing Mode is preferred), Repair SD Card Permissions (allow up to 3-5 minutes of additional time for this script).
Don't flash deep buffer unless you absolutely need to. It's a last resort to get streaming apps to process and should never be flashed as part of your normal installation unless it's been found from flashing previous ARISE version that it's necessary on your device.
Once booted:
Android Settings > Apps > Menu > Show System > Arkamys > Enable Phone Permissions
Android Settings > Apps > Menu > Show System > ViPER4Arise > Enable Storage Permissions
Open ViPER4Arise™ and select Audiophile™ X profile from the Load Effect Profile option in Menu.
On displayed output tab:
Master Power > Off
Master Power > On
Menu > Device Status
Should show Enabled, Normal, and Processing: Yes (at least during audio playback for some scenarios)
If you want to select ViPER4Arise™ through a media player's Equalizer option (not necessary, recommended for users that prefer to get to ViPER4Arise™ through a media player rather than launch the app from Recents or App Drawer):
Android Settings > Apps > Menu > Show System > MusicFX > Disable
Reboot for good measure.
Hope it will help for you. If anything bad happens or you want to uninstall viper, just dirty flash your rom (only wipe cache and dalvik) and everything will be good.
Please note that the selinux mode shall be set to permissive for viper4arise to work. If the selinux mode will not stick to permissive, you may need to disable inbuilt root (if there) and flash latest supersu and then everything will be fine.
There will be a lot of modules during the aroma installation which you can skip (Toolkit, Dolby Plus, Dolby Atmos etc) if it is not mentioned in the recommended setup. Its your choice. Enjoy a crystal clear sound from the great developers.
:good:
NB: I hope I have covered everything that needs to know. Sorry for my bad english and errors if any. I was always a fan of viper4android and been using it for last 3 years and viper always made the music much better to my ears. My only intention is to help others who may be confused with all those modules which will come during the installation of this massive all-in-one package.
Hey! First of all, thank you very much for this great guide. I've followed your instructions, but it seems like I'm experiencing some kind of lag when changing songs. It's like the effects needs to catch up for 1 or 2 seconds after changing songs.. I have done everything mentioned in the guide, and I'm using Spotify, by the way. Any help is appreciated
Lankern98 said:
Hey! First of all, thank you very much for this great guide. I've followed your instructions, but it seems like I'm experiencing some kind of lag when changing songs. It's like the effects needs to catch up for 1 or 2 seconds after changing songs.. I have done everything mentioned in the guide, and I'm using Spotify, by the way. Any help is appreciated
Click to expand...
Click to collapse
I think that your problem with lag is caused by an ondemand-governor or a governor, which set the mhz of cores too low for battery-saving features or whatever.
Which rom are you on. Are you using any battery saving tweaks (for viper with super audio quality driver, i think, need 2 cores on with 600mhz the minimum for non-stuttering sound-processing).
Either setting the governor to interactive or manually adjusting the lower CPU speeds may solve your problem.
Perfect!
My long wait to have an audio mod on stock N ends here.. Thanks for the wonderful share.
krossifix said:
Perfect!
My long wait to have an audio mod on stock N ends here.. Thanks for the wonderful share.
Click to expand...
Click to collapse
Always happy to help :good:
Nothing came....Already installed viper4android does it affect this package??
naveen135 said:
Nothing came....Already installed viper4android does it affect this package??
Click to expand...
Click to collapse
This is the latest version of viper4android. If any other sound mod is installed (including old viper), it should be removed by dirty flashing your rom and then proceed with this.
nazim7 said:
I think that your problem with lag is caused by an ondemand-governor or a governor, which set the mhz of cores too low for battery-saving features or whatever.
Which rom are you on. Are you using any battery saving tweaks (for viper with super audio quality driver, i think, need 2 cores on with 600mhz the minimum for non-stuttering sound-processing).
Either setting the governor to interactive or manually adjusting the lower CPU speeds may solve your problem.
Click to expand...
Click to collapse
Hey again!
I'm running RR 5.8.2 [09/03 update], and no, I'm not using any type of battery-saving tweaks. With Viper4Arise disabled, I still experience the lag. Check the screenshots for the governor setting i set inside the EX Kernel Manager app. Any ideas on how to further troubleshoot/fix this?
Lankern98 said:
Hey again!
I'm running RR 5.8.2 [09/03 update], and no, I'm not using any type of battery-saving tweaks. With Viper4Arise disabled, I still experience the lag. Check the screenshots for the governor setting i set inside the EX Kernel Manager app. Any ideas on how to further troubleshoot/fix this?
Click to expand...
Click to collapse
Thanks for the screenshots. I have used viper in stock nougat and lineage oms, I haven't faced any kind of lags in these. Maybe it is specific to RR rom.
Or you can check with the viper installation; start fresh and install only core and viper4 arise(skip all other modules) and check if there is any lags. If there is still lag, you will have to switch the rom. If there is no lag, try installing the modules one by one until you find which module is causing the lag and avoid using it.
nazim7 said:
Thanks for the screenshots. I have used viper in stock nougat and lineage oms, I haven't faced any kind of lags in these. Maybe it is specific to RR rom.
Or you can check with the viper installation; start fresh and install only core and viper4 arise(skip all other modules) and check if there is any lags. If there is still lag, you will have to switch the rom. If there is no lag, try installing the modules one by one until you find which module is causing the lag and avoid using it.
Click to expand...
Click to collapse
Okay, so I've done some troubleshooting for the past 30 minutes.. It seems like it is the ICEsound™ that is causing the lag for some reason. Everything else seems to work, and thank you again for your help!
Doesnt work while using play music. Works with YouTube, though.
Noticed the "Processing" is set to No while on play music and to Yes while on YouTube. Help?
radichification said:
Doesnt work while using play music. Works with YouTube, though.
Noticed the "Processing" is set to No while on play music and to Yes while on YouTube. Help?
Click to expand...
Click to collapse
Which rom you are on. Try disabling the audiofx or music fx in apps(check show system apps in options ) and reboot. It will work then.
nazim7 said:
Which rom you are on. Try disabling the audiofx or music fx in apps(check show system apps in options ) and reboot. It will work then.
Click to expand...
Click to collapse
I'm on Lineage OMS. Already disabled both and rebooted. Still Processing: No
radichification said:
I'm on Lineage OMS. Already disabled both and rebooted. Still Processing: No
Click to expand...
Click to collapse
Do you have busybox installed, give root permissions "always" , selinux mode set to permissive. I was on lineage OMS before and viper was working, but I didn't tried google play music. Can you try in any other player and reply back.
nazim7 said:
Do you have busybox installed, give root permissions "always" , selinux mode set to permissive. I was on lineage OMS before and viper was working, but I didn't tried google play music. Can you try in any other player and reply back.
Click to expand...
Click to collapse
Yes I followed your guide step by step. So unfortunate
radichification said:
Yes I followed your guide step by step. So unfortunate
Click to expand...
Click to collapse
Sometimes, Viper stops processing after plugging in earbuds, but it will start processing after a reboot with the earbuds plugged in. Check if this is what happening to you. If still not processing, try to freeze icesound service in system apps. It can also mess up with some roms. There is a minor glitch somewhere, hopefully we will find it.
Thanks Nazim7 for this awesome guide!!
Viper screams on my phone and audio quality is improved drastically....u can feel the thump and bass!!!
Some people reported that processing was : no...I faced the same issue...What I did was plugged in earphones -- restarted phone --- make sure selinux set to permissive before restarting...
Go to viper4arise settimgs and set fx to compatible...then play song ..
nazim7 said:
This is the latest version of viper4android. If any other sound mod is installed (including old viper), it should be removed by dirty flashing your rom and then proceed with this.
Click to expand...
Click to collapse
Thanks!!!!It worked
naveen135 said:
Thanks!!!!It worked
Click to expand...
Click to collapse
Glad to know that it worked for you. Enjoy..
help
i'm on stock rom and elemental x kernel, unable to install busybox and after installing viper, in driver status everything says 'no'. Please help.
So I have been trying to get LDAC or apt-X working on my razer phone but it has not worked. I am on the latest stock ROM rooted with magisk (via ADB not TWRP) and with the rayglobe magisk module installed but it just stays on AAC. My headphones are Sony WH-1000XM2 and LDAC was working when using the resurrection remix ROM from the development thread but I had to uninstall the ROM due to instability and no sign of progression. Any help would be appreciated.
Firebuster said:
So I have been trying to get LDAC or apt-X working on my razer phone but it has not worked. I am on the latest stock ROM rooted with magisk (via ADB not TWRP) and with the rayglobe magisk module installed but it just stays on AAC. My headphones are Sony WH-1000XM2 and LDAC was working when using the resurrection remix ROM from the development thread but I had to uninstall the ROM due to instability and no sign of progression. Any help would be appreciated.
Click to expand...
Click to collapse
They locked it down somehow I think. I have 2 threads in here asking for help but no one seems to be able to help me. For added reference, here is the error produced even when all the files are added with root to enable aptx or ldac
I installed the magisk aptx&aptxHD module and modified /system/vendor/build.prop then aptx got working.
(I couldn't test with aptxHD or LDAC cos I have no compatibe device with them.)
Code:
persist.vendor.bt.a2dp_offload_cap=sbc-aac
to
Code:
persist.vendor.bt.a2dp_offload_cap=sbc-aptx-aptXHD
This is the same parameter the magisk module set to /system/build.prop.
To guess, LDAC will may work if an appropriate value set to the prop.
ClubRaptor said:
I installed the magisk aptx&aptxHD module and modified /system/vendor/build.prop then aptx got working.
(I couldn't test with aptxHD or LDAC cos I have no compatibe device with them.)
to
This is the same parameter the magisk module set to /system/build.prop.
To guess, LDAC will may work if an appropriate value set to the prop.
Click to expand...
Click to collapse
This worked to enable switching to them however now Bluetooth just crashes. I changed it to persist.vendor.bt.a2dp_offload_cap=sbc-aptx-aptxhd-ldac
Edit:
Some interesting notes. I tried a few steps to debugging including readding AAC to the list which did nothing but if I only add aptx then the Bluetooth app no longer crashes however no sound plays so I'm guessing it's the lib files that are not correct? I just used the aptx package in magisk so if there's any other that I'm missing or other suggestions that would be useful
Firebuster said:
This worked to enable switching to them however now Bluetooth just crashes. I changed it to persist.vendor.bt.a2dp_offload_cap=sbc-aptx-aptxhd-ldac
Edit:
Some interesting notes. I tried a few steps to debugging including readding AAC to the list which did nothing but if I only add aptx then the Bluetooth app no longer crashes however no sound plays so I'm guessing it's the lib files that are not correct? I just used the aptx package in magisk so if there's any other that I'm missing or other suggestions that would be useful
Click to expand...
Click to collapse
I still can't get it to switch to aptx (the one I want) or ldac. It still falls back to SBC usually or aac if I'm on a different speaker. Any idea what I'm doing wrong? I'm on slot a on my device, rooted with magisk and I have tried multiple aptx modules. Is there a specific build.prop editor you use? Both my speakers and headphones support it and work with other devices and I'm still getting the error I replied with above (page one)
I'm an experienced rooter, so don't be afraid to fully explain any steps I may be missing out!
manor7777 said:
I still can't get it to switch to aptx (the one I want) or ldac. It still falls back to SBC usually or aac if I'm on a different speaker. Any idea what I'm doing wrong? I'm on slot a on my device, rooted with magisk and I have tried multiple aptx modules. Is there a specific build.prop editor you use? Both my speakers and headphones support it and work with other devices and I'm still getting the error I replied with above (page one)
I'm an experienced rooter, so don't be afraid to fully explain any steps I may be missing out!
Click to expand...
Click to collapse
I used root explorer and changed the build.prop entries in system\vendor\. In the first place I used the root essentials build.prop editor which shows a different build.prop. other than that I literally just edited that line and that allowed me to change it. I can't think of anything else I did other than install a bunch of library files which I'm guessing you found the same ones as me because it was very limited on what was available and up to date
Firebuster said:
I used root explorer and changed the build.prop entries in system\vendor\. In the first place I used the root essentials build.prop editor which shows a different build.prop. other than that I literally just edited that line and that allowed me to change it. I can't think of anything else I did other than install a bunch of library files which I'm guessing you found the same ones as me because it was very limited on what was available and up to date
Click to expand...
Click to collapse
OK, awesome. You rock. That got it to select aptx - now my 2nd problem, no audio! I can see in dev options and bt settings that it's showing aptx, but I get no audio (well, I get an almost click click click noise) then my Bluetooth adaptor for my headphones crashes. And it forces my headphones to turn off. I tried 3 different magisk modules for the library files, any ideas - I was getting SBC audio before
manor7777 said:
OK, awesome. You rock. That got it to select aptx - now my 2nd problem, no audio! I can see in dev options and bt settings that it's showing aptx, but I get no audio (well, I get an almost click click click noise) then my Bluetooth adaptor for my headphones crashes. And it forces my headphones to turn off. I tried 3 different magisk modules for the library files, any ideas - I was getting SBC audio before
Click to expand...
Click to collapse
Sounds like the same problem I am having. Aptx doesn't work and aptx HD and LDAC just crash Bluetooth. Genuinely have no idea where to go from here. It must be a driver or library file. Real shame it's not working.
Edit: seems to be looping these messages in catlog
Firebuster said:
Sounds like the same problem I am having. Aptx doesn't work and aptx HD and LDAC just crash Bluetooth. Genuinely have no idea where to go from here. It must be a driver or library file. Real shame it's not working.
Click to expand...
Click to collapse
OK, so last night and this morning I have been just messing with things. I no longer crash my headphones and force them to turn off, but I still have no audio over aptx - though at least it's not crashing my headphones (Bluetooth in the phone was always OK). There is one error I'm getting and I'm not sure if its related of not, but is to do with a buffer failing to release. See my screenshots of logs (just documenting here for reference)
so basically i went your path a few days ago and dropped that idea. please post updates if you manage to get aptx\aptx hd\ldac working (Razer Phone + Sony WH-1000 XM2)
hatemosphere said:
so basically i went your path a few days ago and dropped that idea. please post updates if you manage to get aptx\aptx hd\ldac working (Razer Phone + Sony WH-1000 XM2)
Click to expand...
Click to collapse
Cc @Firebuster
So, I might be an experienced rooter (no 1 click toolkits here) I am NOT a developer. I've tried a combination of a bunch of things to try and get this to work, and nothing has!
I did however get it to work by installing a GSI (basically a rom) to the device, but even that was painful to get working (well, installed). Now running AOSP 8.1 GSI w/gapps and I flashed magisk for root. I then installed the Aptx magisk module from the built in repo and it works perfectly fine. Not sure if It's something in razer software as I'm technically more up to date now so it's not like I was using the wrong drivers.
Can't find a decent dolby atmos I can install that will work along side v4a, all the magisk modules are for android 7 or 6.
Otherwise that's the only way I have found so far, sorry guys! - benefit is, other than AOSP's ****ty camera app (use the gcam port instead), literally everything works fine, and I even get stronger vibration on a GSI
manor7777 said:
Cc @Firebuster
So, I might be an experienced rooter (no 1 click toolkits here) I am NOT a developer. I've tried a combination of a bunch of things to try and get this to work, and nothing has!
I did however get it to work by installing a GSI (basically a rom) to the device, but even that was painful to get working (well, installed). Now running AOSP 8.1 GSI w/gapps and I flashed magisk for root. I then installed the Aptx magisk module from the built in repo and it works perfectly fine. Not sure if It's something in razer software as I'm technically more up to date now so it's not like I was using the wrong drivers.
Can't find a decent dolby atmos I can install that will work along side v4a, all the magisk modules are for android 7 or 6.
Otherwise that's the only way I have found so far, sorry guys! - benefit is, other than AOSP's ****ty camera app (use the gcam port instead), literally everything works fine, and I even get stronger vibration on a GSI
Click to expand...
Click to collapse
Yeah I might move onto that too. To try to fix the Bluetooth issues. I can only assume razer excluded some of the functionality but since it's baked into android 8 I don't see why they would remove it.
Razer and their development team is already informed about this issue, and they have correctly addressed it, and all the Bluetooth issues (which were a few), in the upcoming update MR2. No ETA.
linuxct said:
Razer and their development team is already informed about this issue, and they have correctly addressed it, and all the Bluetooth issues (which were a few), in the upcoming update MR2. No ETA.
Click to expand...
Click to collapse
so i've just got a new update and now i'm wondering if we should try this again...
hatemosphere said:
so i've just got a new update and now i'm wondering if we should try this again...
Click to expand...
Click to collapse
Go ahead, I can't since I'm on a Pie GSI.
If anyone has an LDAC BT Headset please give this a try.
cc @Firebuster
Great news, I just spent 2 hours updating my phone, with flashing back to stock because the OTA did not want to update me since I had Magisk, then putting everything back like before.
The update did not change anything.
Tried to do my research on issues with the Razer phone before getting it, but I guess this is just one of those things you don't comprehend until actually having the device in your hands. I came from a Oneplus One on Lineage OS and am comfortable with flashing (but no experience with GSI yet).
My razer phone is stock and not rooted. Anything I can do to contribute to test getting Apt-X working? The settings says my phone is up to date (build number OPM1.171019.011-RZR-180803.6033).
Got the official Pie installed - no LDAC nor AptX still.
cubeover said:
Got the official Pie installed - no LDAC nor AptX still.
Click to expand...
Click to collapse
you installed the official pie update for the razer phone 1?
{
"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"
}
[ROM][AOKP 9/PIE][cheeseburger] AOKP Pie for OnePlus 5
Code:
*** Disclaimer***
Your warranty is now void!
I am not responsible for damages caused by this ROM
YOU are choosing to install it!
If you have any concerns about potential issues or features with this ROM, do your research!
If you accuse me of causing problems with your device, you WILL be ridiculed!
Introduction
WE ARE LIVE!!
AOKP is a ROM developed by TeamKang, based on AOSP/LineageOS with magical unicorn bytes (awesome features) baked right in!
Features
Android 9 Pie
OMS/Substratum Support - Theming baked right in
SU baked in - No need for SuperSU/Magisk (Unless you want them!)
Custom animations
Customizable AOKP logo in status bar
So many other features, explore and find them on your own!
ROMControl App - A centralized place to manage all almost all the cool features Magical unicorn Bytes!!
Click to expand...
Click to collapse
Known Issues
Pixel Launcher crashes constantly if you try to use it. This is an upstream issue, Lineage-16.0 has the same issue.
You tell me! I have limited testing time, so the more reports I get the better. Please see below for proper issue reporting!
Click to expand...
Click to collapse
Proper Issue Reporting
Make sure you are seeing the issue on a CLEAN install! If the problem pops up after a dirty flash, wipe data/factory reset and see if it still happens before reporting it
Make sure you have not flashed anything extra, such as 3rd party kernels, SuperSU, Magisk, Xposed, etc. These extra packages can cause their own issues. As above, try a full wipe and then only flash the ROM package and Gapps package, and see if the issue persists before reporting
In your report please include the following:
Issue you are seeing, and how to recreate it
Logcat/kmesg from right after the issue if possible
Build date of ROM you are running
Gapps package you have installed
Click to expand...
Click to collapse
Installation instructions
Ensure you have the proper firmware installed (9.0.9)
Backup your data! (nandroid, TiBu, etc.)
Wipe Data/Factory Reset (You did backup, right?)
Flash ROM
Flash GAPPS
Wipe Cache/Dalvik Cache
Reboot
Click to expand...
Click to collapse
Download
Official AOKP download page:
AOKP cheeseburger files
Source:
AOKP Source
Kernel source
Click to expand...
Click to collapse
Changelog
Initial Official release.
Thanks To/Credits
TeamKang
tdm
LineageOS
PayPal Donations and thanks are always appreciated!
XDA:DevDB Information
Pie Android Open Kang Project for OnePlus 5 [cheeseburger], ROM for the OnePlus 5
Contributors
shane87
Source Code: http://aokp.co/source/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader, TWRP 3.2.3 or later by codeworkx (Other TWRP versions not tested!!), Firmware package from OOS 9.0.9
Based On: LineageOS, CyanogenMod, OmniRom, AOSP
Version Information
Status: Nightly
Created 2020-01-20
Last Updated 2020-01-24
Reserved
Reserved
Builds are LIVE!!
Hey guys, AOKP Pie is OFFICIAL! Download links are in the OP, and I am including them below.
http://xfer.aokp.co/?developer=AOKP&folder=cheeseburger
This ROM doesn't officially support signature spoofing/microg?
Pokemetti2 said:
This ROM doesn't officially support signature spoofing/microg?
Click to expand...
Click to collapse
No. AOKP has never officially supported signature spoofing/microg. We did discuss it in the past, but we decided not to, due to the security concerns of allowing signature spoofing.
Does this rom has a working googlepay support?
I have been on stock oxygen OS roms for too long and i am thinking about a change.
EDIT: it is working. Had to make sure that safetynet is passed and using hidemagisk on google products
shane87 said:
No. AOKP has never officially supported signature spoofing/microg. We did discuss it in the past, but we decided not to, due to the security concerns of allowing signature spoofing.
Click to expand...
Click to collapse
May I ask what kind of security concerns? AFAIK the signature spoofing permission needs to be explicitly granted on a per-app basis OR the spoofing app needs to be installed in /system.
For the first point, you would have to be a special kind of retard to just grant any app that permission.
And as for the second point, you would either have to have a ROM that already has a malicious app installed in /system in the first place, or you would have to explicitly install an app in /system through a flashable zip, TWRP file manager or Magisk. And for that you would have to have user interaction and know what you are doing.
So it basically all boils down to the user being the biggest security concern.
@Pokemetti2 you can try patching it either with NanoDroid patcher (if AOKP is deodexed, I don't know) or patch it manually using one of many methods such as haystack, tingle or others. Just look at the NanoDroid documentation.
d1n0x said:
May I ask what kind of security concerns? AFAIK the signature spoofing permission needs to be explicitly granted on a per-app basis OR the spoofing app needs to be installed in /system.
For the first point, you would have to be a special kind of retard to just grant any app that permission.
And as for the second point, you would either have to have a ROM that already has a malicious app installed in /system in the first place, or you would have to explicitly install an app in /system through a flashable zip, TWRP file manager or Magisk. And for that you would have to have user interaction and know what you are doing.
So it basically all boils down to the user being the biggest security concern.
@Pokemetti2 you can try patching it either with NanoDroid patcher (if AOKP is deodexed, I don't know) or patch it manually using one of many methods such as haystack, tingle or others. Just look at the NanoDroid documentation.
Click to expand...
Click to collapse
Yes, that is the case. However, with a rooted device, it would not be difficult for a malicious app to gain root access, then install itself into system, where it would then have access to the signature spoofing. Also, not everyone pays attention to the prompts that pop up on their phone, nor do they understand the ramifications of granting permissions, so it also wouldn't be difficult for a malicious app to gain permission for spoofing. Especially if the app has been granted permission to draw over other apps. It could actually hide the permission request under an innocuous sounding request.
;TLDR
Team Kang made the decision not to include signature spoofing/microg support. If you want to use NanoDroid patcher, or build your own unofficial AOKP with microg support, you are more than welcome to. But we will not be adding microg support officially.
shane87 said:
Yes, that is the case. However, with a rooted device, it would not be difficult for a malicious app to gain root access, then install itself into system, where it would then have access to the signature spoofing. Also, not everyone pays attention to the prompts that pop up on their phone, nor do they understand the ramifications of granting permissions, so it also wouldn't be difficult for a malicious app to gain permission for spoofing. Especially if the app has been granted permission to draw over other apps. It could actually hide the permission request under an innocuous sounding request.
;TLDR
Team Kang made the decision not to include signature spoofing/microg support. If you want to use NanoDroid patcher, or build your own unofficial AOKP with microg support, you are more than welcome to. But we will not be adding microg support officially.
Click to expand...
Click to collapse
That's fine by me, just wanted to know whether I had to flash NanoDroid Patcher.
Update to OP
Hey guys, I just wanted to point out that I made a small update to the OP. I included a notice of the required firmware package from OOS that this ROM needs. Currently that is 9.0.9. We ran into an issue over on 5T, and it likely had to do with incorrect firmware on the phone. I forget that not everyone pours over gerrit as much as I do, so they don't see the required firmware commits.
I will update the OP, and post an announcement, any time that we update the firmware base required.
I ve been on this rom for a couple of days and i have not experienced a crash so far.
Camera, gps, bluetooth and wifi are working. I can phone and everyone can hear me clearly.
I like the feature with the energy saving that you can use smart pixels to use less pixels on screen in order to increase the screen on time.
As for the sound effects, i had to disable the audioFX app to get Viper4Android working in order to get global sound effects.
What bothers me, is that once i have started up the phone, that it pops up a message that sim2 is not working and you get asked too early to switch to sim1. Perhaps if possible, adding a delay if 1minute has passed and that defined standard sim still has no reception, then ask for a simcard switch.
Also i wasnt able to find an option to turn off the alwaysOn display effect.
Above all else, great rom! Still using it as my daily driver.
fosunite said:
I ve been on this rom for a couple of days and i have not experienced a crash so far.
Camera, gps, bluetooth and wifi are working. I can phone and everyone can hear me clearly.
I like the feature with the energy saving that you can use smart pixels to use less pixels on screen in order to increase the screen on time.
As for the sound effects, i had to disable the audioFX app to get Viper4Android working in order to get global sound effects.
What bothers me, is that once i have started up the phone, that it pops up a message that sim2 is not working and you get asked too early to switch to sim1. Perhaps if possible, adding a delay if 1minute has passed and that defined standard sim still has no reception, then ask for a simcard switch.
Also i wasnt able to find an option to turn off the alwaysOn display effect.
Above all else, great rom! Still using it as my daily driver.
Click to expand...
Click to collapse
I am pleased to hear everything is working well for you.
As far as sim1/sim2 goes, I only have a single sim card in my OP5, so I have not seen anything with it saying sim2 is not working. It automatically disables sim2 on boot. I will take a look this weekend, and bring it up to the team, see if there is anything we have changed that would affect sim1/sim2.
To the best of my knowledge, we have no feature to disable always on display. There are options to disable the Ambient Display, but that only affects whether the display pulses notifications on pick up, or removal from pocket.
shane87 said:
I am pleased to hear everything is working well for you.
As far as sim1/sim2 goes, I only have a single sim card in my OP5, so I have not seen anything with it saying sim2 is not working. It automatically disables sim2 on boot. I will take a look this weekend, and bring it up to the team, see if there is anything we have changed that would affect sim1/sim2.
To the best of my knowledge, we have no feature to disable always on display. There are options to disable the Ambient Display, but that only affects whether the display pulses notifications on pick up, or removal from pocket.
Click to expand...
Click to collapse
Thanks for the reply.
About sim1 and sim2: i use both simcards and when i reboot, i ve noticed, that one of my simcards caught up reception quicker than the other one. So i got that message just like that i ve attached in the post. Although both are working after 10seconds, i still need to acknowledge with "no" to keep my settings with the standard sim cards.
It s quite hard finding the option to disable alwaysOn display. I ve tried finding the option through settings=>display=>ambient display but it does not turn off the ambient display. Instead, i had to enter the keyword ambient on the searchbar in settings and click on the first entry to disable the option.
I find it quite misleading that the term ambient display is there but you cannot find the actual option to disable alwaysON. Please see picture 2 and 3 and 4.
fosunite said:
Thanks for the reply.
About sim1 and sim2: i use both simcards and when i reboot, i ve noticed, that one of my simcards caught up reception quicker than the other one. So i got that message just like that i ve attached in the post. Although both are working after 10seconds, i still need to acknowledge with "no" to keep my settings with the standard sim cards.
It s quite hard finding the option to disable alwaysOn display. I ve tried finding the option through settings=>display=>ambient display but it does not turn off the ambient display. Instead, i had to enter the keyword ambient on the searchbar in settings and click on the first entry to disable the option.
I find it quite misleading that the term ambient display is there but you cannot find the actual option to disable alwaysON. Please see picture 2 and 3 and 4.
Click to expand...
Click to collapse
I see what you mean. I will definitely bring these up to the Team. I'm a bit embarrassed to admit it, but I did not know it was possible to fully disable Ambient Display until you mentioned how. :facepalm: Then again, I like the Ambient Display option. But I will definitely bring these up. On the sim issue, could you get me a logcat? Do a fresh reboot, wait until it clears the sim notification, then capture a logcat. That should have all of the log from boot, so we can see if anything weird is going on in the boot process causing the sim to time out temporarily.
In case you are unfamiliar with how to capture a logcat, here is how:
To capture the logcat, you can use adb via your PC (ensure you go to Settings -> About Phone and tap Build Number until it tells you you have unlocked Development Settings (Settings -> System -> Developer Options) and make sure you enable adb), use an app such as catlog, or use a terminal emulator (su <press enter>; logcat -d > /sdcard/logcat.txt).
Added to the OnePlus 5 Index Thread here.
shane87 said:
I see what you mean. I will definitely bring these up to the Team. I'm a bit embarrassed to admit it, but I did not know it was possible to fully disable Ambient Display until you mentioned how. :facepalm: Then again, I like the Ambient Display option. But I will definitely bring these up. On the sim issue, could you get me a logcat? Do a fresh reboot, wait until it clears the sim notification, then capture a logcat. That should have all of the log from boot, so we can see if anything weird is going on in the boot process causing the sim to time out temporarily.
In case you are unfamiliar with how to capture a logcat, here is how:
To capture the logcat, you can use adb via your PC (ensure you go to Settings -> About Phone and tap Build Number until it tells you you have unlocked Development Settings (Settings -> System -> Developer Options) and make sure you enable adb), use an app such as catlog, or use a terminal emulator (su <press enter>; logcat -d > /sdcard/logcat.txt).
Click to expand...
Click to collapse
Sorry it will take a while, because i am unfamiliar with doing logcat. I will try connect my phone to pc via adb and try to log the events. It s quite tough doing while phone should boot.
newest build (01/31) doesnt boot for me (it reboots to twrp)
anyone else facing this issue?
shane87 said:
I see what you mean. I will definitely bring these up to the Team. I'm a bit embarrassed to admit it, but I did not know it was possible to fully disable Ambient Display until you mentioned how. :facepalm: Then again, I like the Ambient Display option. But I will definitely bring these up. On the sim issue, could you get me a logcat? Do a fresh reboot, wait until it clears the sim notification, then capture a logcat. That should have all of the log from boot, so we can see if anything weird is going on in the boot process causing the sim to time out temporarily.
In case you are unfamiliar with how to capture a logcat, here is how:
To capture the logcat, you can use adb via your PC (ensure you go to Settings -> About Phone and tap Build Number until it tells you you have unlocked Development Settings (Settings -> System -> Developer Options) and make sure you enable adb), use an app such as catlog, or use a terminal emulator (su <press enter>; logcat -d > /sdcard/logcat.txt).
Click to expand...
Click to collapse
Ok, Finally managed to pull a logcat. Hope this helps.
rikkker said:
newest build (01/31) doesnt boot for me (it reboots to twrp)
anyone else facing this issue?
Click to expand...
Click to collapse
I ve been there. Please do following steps:
1) If you have wiped data/factory reset already Flash Rom
2) Flash Gapps
3) Flash a no verity OP5
DO not flash Magisk. do your first boot and then flash magisk afterwards. Also some magisk plugins like Oxy ify doesnt let you boot.
fosunite said:
Ok, Finally managed to pull a logcat. Hope this helps.
I ve been there. Please do following steps:
1) If you have wiped data/factory reset already Flash Rom
2) Flash Gapps
3) Flash a no verity OP5
DO not flash Magisk. do your first boot and then flash magisk afterwards. Also some magisk plugins like Oxy ify doesnt let you boot.
Click to expand...
Click to collapse
Thanks for the logcat. I'll dig into it this weekend and see if it shows anything interesting. Quick question, have you tried lineage 16? If so, does it do the same thing as far as the sim1/sim2? Since we base off of Lineage, I want to make sure that the issue is linked to AOKP, and not something that we have inherited from lineage. I only have a single sim, so I can't test myself.
On the flashing sequence, I have personally never had any issues with flashing magisk right away, but ymmv. I do a wipe/factory reset, (after backing up via tibu and/or nandroid back up in twrp), manually wipe system, cache, and dalvik cache, flash ROM, flash magisk, flash gapps. Again, YMMV.
Also, you ONLY need the no verity flash if you have unencrypted your data partition. I left my data partition encrypted.
I have not flashed the 01/31 build yet, but I will check it out, probably tomorrow.
Hi, I did some experiments with the GSI PIXEL EXPERIENCE ALPHA that might interest some developers.
It works properly as is on nairo (moto g 5g plus) except for a few things.
- TWRP recovery gets broken, i think we need a newer version for this phone to work with android 12.
- The audio doesn't get routed in any way (i've tried with apps) to the aux output (headset).
I would take care of this problems if i had knowledge, if anyone can help it's welcome for sure, thanks in advance!
Tommy0000 said:
Hi, I did some experiments with the GSI PIXEL EXPERIENCE ALPHA that might interest some developers.
It works properly as is on nairo (moto g 5g plus) except for a few things.
- TWRP recovery gets broken, i think we need a newer version for this phone to work with android 12.
- The audio doesn't get routed in any way (i've tried with apps) to the aux output (headset).
I would take care of this problems if i had knowledge, if anyone can help it's welcome for sure, thanks in advance!
Click to expand...
Click to collapse
1 share the gsi twrp is broken for even on a android 11 gsi as for audio
1. Go to developer options, find something like "Disable A2DP offload", turn it on and restart your device.
2. After the restart head back to settings, head to Phh Treble settings, then misc and enable "Force headphone switch" and
wesleyvanneck12345678 said:
1 share the gsi twrp is broken for even on a android 11 gsi as for audio
1. Go to developer options, find something like "Disable A2DP offload", turn it on and restart your device.
2. After the restart head back to settings, head to Phh Treble settings, then misc and enable "Force headphone switch" and
Click to expand...
Click to collapse
Thank you very much, i'll try it, i don't get yor first sentence, is it broken for everyone? (english isn't my first language)
wesleyvanneck12345678 said:
1 share the gsi twrp is broken for even on a android 11 gsi as for audio
1. Go to developer options, find something like "Disable A2DP offload", turn it on and restart your device.
2. After the restart head back to settings, head to Phh Treble settings, then misc and enable "Force headphone switch" and
Click to expand...
Click to collapse
It worked without forcing headphone switch, tysm! Now i'm working to get some padding on the status bar if i'm able to
Tommy0000 said:
It worked without forcing headphone switch, tysm! Now i'm working to get some padding on the status bar if i'm able to
Click to expand...
Click to collapse
if make cutout work send it phhusson
wesleyvanneck12345678 said:
if make cutout work send it phhusson
Click to expand...
Click to collapse
I successfully made one with nonsense notch, idk if i can send phh the apk the module created, i used the customleft script at 240 px
Tommy0000 said:
I successfully made one with nonsense notch, idk if i can send phh the apk the module created, i used the customleft script at 240 px
Click to expand...
Click to collapse
share it with me am waiting for fix to long with gsis
Tommy0000 said:
I successfully made one with nonsense notch, idk if i can send phh the apk the module created, i used the customleft script at 240 px
Click to expand...
Click to collapse
you cant send it to him but i didnt know mudule but can you share it with me
Sure! I've used nonsense notch to create an overlay at 240 pixel from the left of the statusbar, it doesn't work on landscape mode but it's fine for me.
Idk if it works by just inserting it in /system/product/overlay and unzipping it and then maybe installing the apk(?) (Mine it's in a folder that's why i made a zip file)
Overlays are really tricky, i recommend following the guide for the module instead of doing this.
After installation you can go to dev options and under simulate screen cutout you can choose the one you created *DO NOT CHOOSE THE STOCK OPTIONS ON ANDROID 12 THEY WILL SOFTLOCK YOUR PHONE*
I will create a guide on the fixes for gsi roms with your audio tweaks and this one, thank you again, let me know if you succeed!
Again, you shoudl really create one yourself on the custom mode of this module https://forum.xda-developers.com/t/module-n3o-no-nonsense-notch-overlay.4226413/
I created a guide to install everything https://forum.xda-developers.com/t/...s-nairo-and-some-post-install-tweaks.4364963/
Tommy0000 said:
Sure! I've used nonsense notch to create an overlay at 240 pixel from the left of the statusbar, it doesn't work on landscape mode but it's fine for me.
Idk if it works by just inserting it in /system/product/overlay and unzipping it and then maybe installing the apk(?) (Mine it's in a folder that's why i made a zip file)
Overlays are really tricky, i recommend following the guide for the module instead of doing this.
After installation you can go to dev options and under simulate screen cutout you can choose the one you created *DO NOT CHOOSE THE STOCK OPTIONS ON ANDROID 12 THEY WILL SOFTLOCK YOUR PHONE*
I will create a guide on the fixes for gsi roms with your audio tweaks and this one, thank you again, let me know if you succeed!
Again, you shoudl really create one yourself on the custom mode of this module https://forum.xda-developers.com/t/module-n3o-no-nonsense-notch-overlay.4226413/
Click to expand...
Click to collapse
thank you very much it works and it even does my games without a black bar
wesleyvanneck12345678 said:
thank you very much it works and it even does my games without a black bar
Click to expand...
Click to collapse
Ye it's very fortunate it stops working when landscape! I quite like that non-feature
hello, a few months ago I put a GSI on my moto G30 (ArrowOS), I actually liked this GSI a lot... but I can't use some phone functions like bluetooth and headphones on the P2 output...
I use headphones a lot and I was using one with a USB Type-C output but this headphones is having some problems and I want to go back to using my JBL bluetooth headphones that I stopped using because it doesn't connect with my cell phone...
But I don't remember how to put a GSI and I don't even know a good one that I can have a good performance on battery and in games...
Can someone help me?
Hi. GSI performance doesnt varry that much if at all so pick any you like best.
Look at phhusson's GSI List to find a GSI that is compatible
(Must be a higher or equal Android version to the one your phone has stock and the GSI shoud be A/B and arm64)
Your problems sound quite generic and are mentioned in the GSI Troubleshooting FAQ
Such as:
Wired headphones not getting detected.Solution 1Enable alternative headphones detection in phh settings and reboot
This one ^ worked for me and should work for you too i believe.
Bluetooth connecting to device and then disconnectingTry disabling A2DP offload in phh settings
I've tried this too but cant remember if it worked, what works for me is going to the Bluetooth settings for the device and disabling HD Audio.
You can find more fixes on the link above.
About installing the GSI first flash the stock ROM and then follow Sammm77's GSI Flashing Guide.
You can try ArrowOS again with the fixes above and see if they work or pick another GSI.
If you need any clarifications i would be more than happy to help!
KAN7A said:
Hi. GSI performance doesnt varry that much if at all so pick any you like best.
Look at phhusson's GSI List to find a GSI that is compatible
(Must be a higher or equal Android version to the one your phone has stock and the GSI shoud be A/B and arm64)
Your problems sound quite generic and are mentioned in the GSI Troubleshooting FAQ
Such as:
Wired headphones not getting detected.Solution 1Enable alternative headphones detection in phh settings and reboot
This one ^ worked for me and should work for you too i believe.
Bluetooth connecting to device and then disconnectingTry disabling A2DP offload in phh settings
I've tried this too but cant remember if it worked, what works for me is going to the Bluetooth settings for the device and disabling HD Audio.
You can find more fixes on the link above.
About installing the GSI first flash the stock ROM and then follow Sammm77's GSI Flashing Guide.
You can try ArrowOS again with the fixes above and see if they work or pick another GSI.
If you need any clarifications i would be more than happy to help!
Click to expand...
Click to collapse
man, you really helped me alout...
i tried these two methods
-Enable alternative headphones detection in phh settings and reboot
-Try disabling A2DP offload in phh settings (in this case I restarted the phone too)
and both starting working again