Hello, I'm on Android12 (EvolutionX) and I've seen people have this problem, But I can't fix the problem, any idea please?
{
"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"
}
please help me !!
Install ainur narsil in magisk
V0ltan said:
Hello, I'm on Android12 (EvolutionX) and I've seen people have this problem, But I can't fix the problem, any idea please? View attachment 5633897
Click to expand...
Click to collapse
I had the same problem with my Mi 11 Lite 5G NE, tried various guides, no luck
Finally I made V4A working for me the following way:
https://forum.xda-developers.com/t/...ndroid-10-11-12-devices.4213647/post-86870983
However, I'm on stock and MIUI 12.5.8/A11 - you can try does the same work for your custom ROM A12
zgfg said:
I had the same problem with my Mi 11 Lite 5G NE, tried various guides, no luck
Finally I made V4A working for me the following way:
https://forum.xda-developers.com/t/...ndroid-10-11-12-devices.4213647/post-86870983
However, I'm on stock and MIUI 12.5.8/A11 - you can try does the same work for your custom ROM A12
Click to expand...
Click to collapse
Thank you very much, I will try this now
zgfg said:
I had the same problem with my Mi 11 Lite 5G NE, tried various guides, no luck
Finally I made V4A working for me the following way:
https://forum.xda-developers.com/t/...ndroid-10-11-12-devices.4213647/post-86870983
However, I'm on stock and MIUI 12.5.8/A11 - you can try does the same work for your custom ROM A12
Click to expand...
Click to collapse
It doesn't work at all, I put the new post-fs-data.sh as you gave, and still the same, any idea?
this is how i put the files
V0ltan said:
It doesn't work at all, I put the new post-fs-data.sh as you gave, and still the same, any idea?
Click to expand...
Click to collapse
Read my post there, what I was looking for, how I found what changes I needed to apply to the sh file. Seems you have now different folders with audio drivers, etc
zgfg said:
Read my post there, what I was looking for, how I found what changes I needed to apply to the sh file. Seems you have now different folders with audio drivers, etc
Click to expand...
Click to collapse
Why I is not audio_effect.xml?
V0ltan said:
Why I is not audio_effect.xml?
Click to expand...
Click to collapse
Look also here - good luck:
[Bounty] Viper4android fix
So I'm not sure if I'm doing this the right way, but I think in an effort to get experienced devs to take a look into our viper4android driver loop issue a bounty is in order. I have tried every method I could find to get viper4android to work...
forum.xda-developers.com
I used these instructions on both xiaomi.eu and now PixelOS, Viper4Android works perfectly.
[APP] [FIX] 100% working Viper4Android for Android 10-11-12 devices
If you are someone like me who encountered countless problems while installing Viper4Android on your Android 10 or 11 device and have no idea what to do then you are in the right place. Just download and install the apk from the attachment below...
forum.xda-developers.com
guardian_uk said:
I used these instructions on both xiaomi.eu and now PixelOS, Viper4Android works perfectly.
[APP] [FIX] 100% working Viper4Android for Android 10-11-12 devices
If you are someone like me who encountered countless problems while installing Viper4Android on your Android 10 or 11 device and have no idea what to do then you are in the right place. Just download and install the apk from the attachment below...
forum.xda-developers.com
Click to expand...
Click to collapse
Btw, did your phone come or you upgraded to MIUI 13/A12?
Also, you used Xiaomi.eu ROM (Weekly or Stable) with A12?
I'm asking bcs I'm curious, you are quoting to my post for (stock) MIUI 12.5.8/A12 for Lisa, I'd like to know does it work for A12 as well (potentially different folders for audio drivers)
@zgfg
Phone came with MIUI 12.5 based on Android 11, I upgraded it to MIUI 13 / Android 12. Battery life was pathetic on stock for me, so unlocked and flashed the stable xiaomi.eu ROM.
Moved to an AOSP ROM (PixelOS) a week back because I prefer stock Android any day. Battery life is far better than even xiaomi.eu.
But I was able to successfully install Viper4Android on both xiaomi.eu and now PixelOS using these instructions. Although there is one additional step I did which is not mentioned here. I manually copied the audio_effects.xml file to all the locations mentioned in the instructions. You need to copy over the xml file which has v4a_fx mentioned inside the file after the copyright section. It is also the larger size file (7.93 KB for me). Unfortunately I don't remember where this file is originally stored for you to copy it. But you can search for it using a file manager that supports root. You need to copy this file to the locations mentioned after installing Viper plus the driver and rebooting for the first time.
Also make sure that all other audio mods like AudioFX, Dolby Atmos, etc are not installed before installing Viper. I am aware of Audio Modification Library which integrates multiple audio mods, however I have never used it. I suppose it will be even more difficult to install Viper with AML. I could be wrong though. Anyway, for me Viper is enough.
Apparently the problem is with the atom kernel, I say this because I installed the same OS on my two devices (Alioth and Lisa), on Alioth SuperiorOS uses n0kernel, on Lisa it uses atom kernel, and in Alioth a simple installation of the module audio modification library + V4A already worked, a pity that the same does not happen in Lisa, the same already happened in Evox.
Does anyone know which pixelOS kernel it uses?
I'm seriously thinking about going back to Memeui with Lisa, my last attempt will be AOSPA which apparently doesn't use atom kernel.
dude.. i need help
i use Samsung Galaxy A50 and CRDroid Custom ROM Android 11,
i have installed Viper4Android. when i use loud speaker. it worked very well, but when i play with my earphone plugged in.. driver status said processing : no
can you guys help me please?? thanks.. pardon my english
@unsavorypinkie
I also face this problem once in a while. Try toggling Legacy Mode on and off. You can also force close the app playing audio and Viper and then first open Viper, then your music app and resume playback. It should start processing again.
guardian_uk said:
@unsavorypinkie
I also face this problem once in a while. Try toggling Legacy Mode on and off. You can also force close the app playing audio and Viper and then first open Viper, then your music app and resume playback. It should start processing again.
Click to expand...
Click to collapse
sadly it's still didnt work processing is still no.. but thanks dude for the tips.. maybe it'll help in the future
Then paer
unsavorypinkie said:
sadly it's still didnt work processing is still no.. but thanks dude for the tips.. maybe it'll help in the future
Click to expand...
Click to collapse
Then perhaps it could be due to the audio_effects.xml file. The file found in /data/adb/modules/ViPER4AndroidFX/system/vendor/etc has to be copied over to /vendor/etc and /vendor/etc/audio/inside whatever folder you have there. For me on a 11 Lite NE 5G it is SKU_YUPIK.
The file in the original location (/data/adb/modules/ViPER4AndroidFX/system/vendor/etc) must have v4a_fx mentioned in it. You can search within the file for it to confirm. It is after the copyright section.
After all this is done, restart and you should be good. Also ensure Legacy Mode is enabled and Compatibility Mode is disabled. If all else fails, try starting from scratch using the instructions by user "zgfg" that I linked to.
If it still doesn't work, then I'm sorry, I really don't know. Hope you can get it running though. The difference Viper makes is really like night and day!
guardian_uk said:
Then paer
Then perhaps it could be due to the audio_effects.xml file. The file found in /data/adb/modules/ViPER4AndroidFX/system/vendor/etc has to be copied over to /vendor/etc and /vendor/etc/audio/inside whatever folder you have there. For me on a 11 Lite NE 5G it is SKU_YUPIK.
The file in the original location (/data/adb/modules/ViPER4AndroidFX/system/vendor/etc) must have v4a_fx mentioned in it. You can search within the file for it to confirm. It is after the copyright section.
After all this is done, restart and you should be good. Also ensure Legacy Mode is enabled and Compatibility Mode is disabled. If all else fails, try starting from scratch using the instructions by user "zgfg" that I linked to.
If it still doesn't work, then I'm sorry, I really don't know. Hope you can get it running though. The difference Viper makes is really like night and day!
Click to expand...
Click to collapse
that folder you mentioned is empty, and i've tried to search with my root explorer. unfortunately i don't have audio_effects.xml file on my phone.. how can i solve this sir?? can i download it from the internet??
EDIT : i have found it sir.. i have copied that file from data/adb/modules/VIPER4AndroidFX/system/vendor/edc to vendor/etc but i don't have folder named audio inside but i have folder called dolby
Sorry, I have no idea then. What I do know is Viper will not work with existing audio mods so you'll have to remove/disable those. There is a Magisk module for multiple audio mods, but I have never used it.
That yupik folder is specific to a 11 Lite NE. I have two other phones, they don't have a yupik folder in them. But they are also running Android 11, which is easier to get Viper working on compared to Android 12.
You'll have to research how to get it working specifically for your phone.
Related
{
"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"
}
This is modded JUI ROM by @Cuoco92 running on android 7.1.1. I do not own and make this ROM but I have asked for @Cuoco92 permission to make a thread here so that we can all refer and share this ROM in one, easy and organized place.
I'm using C103 device but so far this ROM is working fine for me with working wifi, hotspot, bluetooth, compass and fingerprint.
Installation :1. Boot into TWRP
2. Make a backup (optional. I don't need backups because I'm flashing this right from the beginning, migrating from EUI)
3. Wipe>Format Data (this is to remove device encryption so that you can see your internal memory in TWRP)
4. Wipe>Advanced>Cache, Dalvik/ART, System, Data (wipe)
5. Copy ROM into internal memory.
6. Go back to TWRP main page and select Install.
7. Flash the ROM.
8. Device will be automatically restarted after flashing finished. Don't worry if it does.
Downloads :
- ROM (VR12 from GDrive)
- VR10 (stable, from AFH)
BETA Builds Updates :- VR13.2
Features :
- Android 7.1.1 Nougat
- New recents compared to the iOS like EUI
- Tethering data limit
- Auto connect in File Transfer Mode
- Dolby and Viper4Android pre-installed
- Latest 3.2.1 TWRP automatically flashed after ROM flash finished.
- CameraHAL3 enabled ( in Cuoco app ; pre-installed with ROM)
- Adaway pre-installed (also in Cuoco app)
- Gapps preinstalled
- Better battery life, better heating management
- Rooted with Magisk v16.3
What's working :
1. Wifi and tethering
2. Fingerprint unlock
3. Root
4. Compass
5. SLR (bokeh), Mono Mode in camera.
6. Band 3 and Band 5 LTE, WCDMA, GSM.
7. Pretty much everything so far...
What's Not Working (in BETA):
- Some users reported speaker bugs coming from C103 devices. You can try this fix here
- For some reason Vanced youtube is not working in both TWRP install and Magisk Install
- Video recording does not work due to mic problem.
- You can try the mic fix using Magisk module here and see if it fix it. Voice call is working after using this module.
- PreInstalled Viper4Android do not work and buggy. @Cuoco92 has removed it in VR13 release.
Special thanks to @Cuoco92 for this wonderful ROM and for allowing me to create a thread for his ROM here. Check out all of his wonderful work in AFH here :
Screenshots :
Some camera samples :
Bokeh :
Mono :
Auto :
Some extra notes to C103 users :
This ROM was built by @Cuoco92 for C106 devices. So expect some bugs for your device as I have already written on the 1st post. However, you can this fix as shared by my local Coolpad Cool 1 community users and see if it works for you. It works for them but I have not yet tried this fix as I currently doesn't have much free time due to work.
If you're eager to fix it, you can try to :
1) Roll back stock EUI for C103.
2) Install stock EUI for C106 using Coolpad Manager.
3) Install official JUI for C106 using Coolpad Manager.
4) Install TWRP on your Official JUI.
5) Flash this Cuoco ROM.
*Some users reported their C103 works well without bugs when doing this steps since this ROM was built for C106 originally. I have not tested this yet because I have no problem with unable to record video since I don't use them. But you can try and let us all know if it works.
Thank you for shearing this Rom and a big thanks to the Dev @Cuoco92.
Magisk modules are working?
It can be works for c103 indian version??
reddsmokee said:
Magisk modules are working?
Click to expand...
Click to collapse
Which module?
[email protected] said:
It can be works for c103 indian version??
Click to expand...
Click to collapse
Works for me. Just wipe everything before flash. Follow the guides. It should work fine. I'm using C103 too.
But c103 indian version is different than Malaysian ....
After installing JUI Indian version c103 have bugs like no sound , second sim not working.
Congratulations on the initiative and thank you!
[email protected] said:
But c103 indian version is different than Malaysian ....
After installing JUI Indian version c103 have bugs like no sound , second sim not working.
Click to expand...
Click to collapse
Bro...read the first post. I AM using C103. When you do a full wipe, your device will be recognized as C106 after flashing this rom. I'm using it and so far everything is working fine. 4G LTE, second sim, speakers...
kodbz said:
Congratulations on the initiative and thank you!
Click to expand...
Click to collapse
It's about time actually. We need more thread in order to gain full functional device section.
vulturext said:
It's about time actually. We need more thread in order to gain full functional device section.
Click to expand...
Click to collapse
Maybe you should include a "From EUI to JUI" guide to avoid bricked devices.
You need to upgrade using Coolpad assistant, right?
I haven't made the move yet, but thanks for posting an organized thread. Going to upgrade my C103 soon.
Also, perhaps throw a link to GCam. Not sure which version/settings work best (haven't tested yet).
vulturext said:
Which module?
Click to expand...
Click to collapse
Generally friend, except youtube vance. For example viperx, ios emojis or systemless xposed?
Palm Trees said:
Maybe you should include a "From EUI to JUI" guide to avoid bricked devices.
You need to upgrade using Coolpad assistant, right?
I haven't made the move yet, but thanks for posting an organized thread. Going to upgrade my C103 soon.
Also, perhaps throw a link to GCam. Not sure which version/settings work best (haven't tested yet).
Click to expand...
Click to collapse
Coming soon. I don't have too much time at hand for now. Only some free time.
Edit : Guide to flash TWRP in EUI here : https://forum.xda-developers.com/android/development/guide-easy-twrp-root-using-qfil-eui-t3781171
reddsmokee said:
Generally friend, except youtube vance. For example viperx, ios emojis or systemless xposed?
Click to expand...
Click to collapse
Bro, viper4android is included in rom. Font changer is included too. I've installed busybox module from magisk manager and it's working fine. I don't use Xposed.
Very good rom, keep up the great work.
Hello, thank you for the great Work, the ROM works almost perfect.
BUT I have the Problem that my sim Card can't find any Connection at all. Before i flashed the ROM there was no Issue with it. Can anyone help?
Pavel0815 said:
Hello, thank you for the great Work, the ROM works almost perfect.
BUT I have the Problem that my sim Card can't find any Connection at all. Before i flashed the ROM there was no Issue with it. Can anyone help?
Click to expand...
Click to collapse
Have you tried creating new APN?
Yes, created new APN, checked Baseband, IMEI, Airplane Mode and so on, everthing fine. But at Testing Menu it says that Radio is turned off. (Wifi/BT is working)
Also, the SIM is not detected after a Reboot. I have to take it out and in again.
Hi there!
I made this Magisk module to enable more options to choose with the Always on display on monet and not only the annoying option of "10 seconds after tapping".
Did it modifying the "AODSettings.smali" file inside an old AOD apk, where there was an exception to our device to enable more options. I'm trying to make it work with recent versions.
Tested and working on MIUI Q/R stock and xiaomi.eu based ROMS.
Changelog:
v1.0 (26/01/2021)
- Initial release
- Patched original apk, ver. 2.0.453.
v1.1 (11/02/2021)
-Updated AOD app from 2.0.453 to 2.4.542
-Solved a syntax error on "AODSettings.smali" which could cause side effects on some sensors.
-Dark mode fully supported
-Specific apk bugs solved (Xiaomi's changelog)
Maybe there won't be more updates of this mod because for earlier versions of AOD they included proprietary libs that are not easy to manage.
Known bugs:
-You tell me
Screenshot:
{
"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"
}
santiagog242 said:
Hi there!
I made this Magisk module to enable more options to choose with the Always on display on monet and not only the annoying option of "10 seconds after tapping".
Did it modifying the "AODSettings.smali" file inside an old AOD apk, where there was an exception to our device to enable more options. I'm trying to make it work with recent versions.
The MOD is under testing, working fine with xiaomi.eu 12.1.1 - Android 11.
Super Wallpapers compatible.
Not tested yet on global and another MIUI based ROMs.
Known bugs:
-Some users with Android 10 reported audio jack isn't working with this module installed.
-You tell me.
Screenshot:
View attachment 5199641
Click to expand...
Click to collapse
I have tested your module, but I cannot boot my device with it. I am on xiaomi.eu 12.1.1 as well.
Works on 12.1.3 EEA rom with root.
Please add dark mode. I love sheduled mode.
works fine on 12.1.3.0.RJIEUXM
no problem with audio jack
thanks for this module
works fine for me! Thank you!
Edit: After one day usage I noticed a bug for me: AOD and Lock screen shows AM, PM while using 24hrs clock, so probably I will stop using it for now
wacuafek said:
works fine for me! Thank you!
Edit: After one day usage I noticed a bug for me: AOD and Lock screen shows AM, PM while using 24hrs clock, so probably I will stop using it for now
Click to expand...
Click to collapse
It is a specific apk version bug, so I'll try to make the mod work with recent versions.
santiagog242 said:
It is a specific apk version bug, so I'll try to make the mod work with recent versions.
Click to expand...
Click to collapse
I would be grateful!
wacuafek said:
I would be grateful!
Click to expand...
Click to collapse
Updated, try new version.
santiagog242 said:
Updated, try new version.
Click to expand...
Click to collapse
Thanks for update! Now works as expected!
Can this mod be used also for the Redmi Note 10 Pro?
andrazek said:
Can this mod be used also for the Redmi Note 10 Pro?
Click to expand...
Click to collapse
As this mod is not device specific, you can try, but do it at you own risk, it may work.
Hi, i need to root my Phone for this Mod, right?
Or is there a way to install this without root?
Untier said:
Hi, i need to root my Phone for this Mod, right?
Or is there a way to install this without root?
Click to expand...
Click to collapse
Yes, you must root with Magisk. I don't know if there's another way. Maybe uninstalling the system app with adb and then install manually the modified APK. But I didn't try.
santiagog242 said:
Yes, you must root with Magisk. I don't know if there's another way. Maybe uninstalling the system app with adb and then install manually the modified APK. But I didn't try.
Click to expand...
Click to collapse
I read that this is unfortunately not working with System Apps.
Is it not possible to edit the Android Manifest and raise the APP Version higher than the already installed AOD App?
Has anyone tried to root the Redmi note 10 pro and tried this mod?
"Maybe there won't be more updates.."
What do you mean by that? So it won't work with the upcoming versions? Then I won't play with root if it's just a temporary solution. Have you noticed the changes of the libs in the latest beta?
Oh, and BTW, is the functionality of this mod the same as for other xiaomi smartphones that include AOD always options out-of-box? I'm sure it's a better solution than disabling MIUI optimizations to get it working (regarding battery efficiency)...
andrazek said:
Has anyone tried to root the Redmi note 10 pro and tried this mod?
"Maybe there won't be more updates.."
What do you mean by that? So it won't work with the upcoming versions? Then I won't play with root if it's just a temporary solution. Have you noticed the changes of the libs in the latest beta?
Oh, and BTW, is the functionality of this mod the same as for other xiaomi smartphones that include AOD always options out-of-box? I'm sure it's a better solution than disabling MIUI optimizations to get it working (regarding battery efficiency)...
Click to expand...
Click to collapse
Didn't know that Redmi Note 10 Pro have the same limitation. I mean, maybe there won't be more updates of my mod because for earlier versions than 2.4.542, Xiaomi included proprietary libs inside the apk, they don't have debug symbols and the built apk doesn't work. Look at this
Recompile Settings.apk MIUI 11 · Issue #2243 · iBotPeaches/Apktool
Information Apktool Version (apktool -version) - 2.4.1 Operating System (Mac, Linux, Windows) - Linux Ubuntu 18 APK From? (Playstore, ROM, Other) - ROM Stacktrace/Logcat I: Using Apktool 2.4.1 I: C...
github.com
Is the same problem for me, so this is not my notion.
Also, note that the mod works fine, even with latest betas, so is not a temporary solution. Have been using this along with the Telegram community. Maybe if I have the time I'll try to modify the Android Manifest and see if it works without root. By now, this should work on any Xiaomi with AOD support.
is it possible to install it trough adb with an apk?
Eu Rom Miui 12.5 rom pürüzsüz.
Only the weather super theme has a double clock display error
There is a new update for monet, 12.5.2 (xiaomi.eu), the module doesn't work anymore. Clicking the AOD in settings throws you back to the main settings page.
Thanks, I just installed v1.1_MIUI_AOD-Patched zip to Xiaomi 11 Lite 5G NE, MIUI 12.5.8 EEA stock, and it works flawlessly (I can now use AOD really always (actually scheduled during the day), not only for 10 seconds as Xiaomi forces)
1. Install AML and ViperFX
2. Reboot.
3. Launch Viper and install the driver.
4. Without running Viper:
- From the archive AML.rar
replace post-fs-data.sh along the path /data/adb/modules/AML
- From the archive Viper.rar
replace post-fs-data.sh along the path /data/adb/modules/VIPER4AndroidFX
5. Reboot.
6. Done.
Note.
1) My PowerAmp does not work correctly.
2) If there is a clock offset in the status bar then install the module selinux_enforce.zip
Spoiler: Screenshot
{
"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"
}
[email protected] said:
1. Install AML and ViperFX
2. Reboot.
3. Launch Viper and install the driver.
4. Without running Viper:
- From the archive AML.rar
replace post-fs-data.sh along the path /data/adb/modules/AML
- From the archive Viper.rar
replace post-fs-data.sh along the path /data/adb/modules/VIPER4AndroidFX
5. Reboot.
6. Done.
Note.
1) My PowerAmp does not work correctly.
2) If there is a clock offset in the status bar then install the module selinux_enforce.zip
Spoiler: Screenshot
View attachment 5544989View attachment 5544991
Click to expand...
Click to collapse
Thanks. Can't extract your .rar files, seem corrupted
Bepi Mosto said:
corrupted
Click to expand...
Click to collapse
reload
Finally working in OOS12 thanks!
P.S for some reason the folder directories to copy the files were:
data/adb/modules/aml
and
data/adb/modules/ViPER4AndroidFX
Figured it out when getting directory does not exit when trying the paths given in first post
TY for this. I had it working 100% on Android 11, but figured I was lost on 12. Only issue I've had is it constantly thinks I'm connected to my car radio's BT after I disconnect, so profiles aren't perfect, but I missed V4Android. Sound quality is night vs day.
Hi there,
after several other methods this one helped me to solve the driver problem. Thanks for that!
Still I have the problem that NEON is not activated. Is there any solution to be found anywhere?
I am using the Oneplus Nord 2T with Oxygen OS Android 12.
EDIT: found solution.
This worked fine for me on OOS13, it works in all apps when the legacy mode is on. However after doing this whole procedure, Dolby Atmos no longer works (at least on the integrated speakers, which is what I only tested)
Didn't work. After replacing files Viper driver is installed loop (OnePlus 10 Pro, OOS 13, C20 (EU))
Arcide said:
This worked fine for me on OOS13, it works in all apps when the legacy mode is on. However after doing this whole procedure, Dolby Atmos no longer works (at least on the integrated speakers, which is what I only tested)
Click to expand...
Click to collapse
Did anyone else have this issue and any clue on how to solve it?
Hey guy i installed viper works but when i try to use the Convolver and than i click on impulse response. I get this message on the bottom. Anyway to fix this.
The presets install into a different folder. You have to manually move them over to where Viper is telling you it can't find them. Oddly enough, I had to use Terminal to move them. Even Root Explorer with SU permissions got a r/w denial.
MStrawder said:
The presets install into a different folder. You have to manually move them over to where Viper is telling you it can't find them. Oddly enough, I had to use Terminal to move them. Even Root Explorer with SU permissions got a r/w denial.
Click to expand...
Click to collapse
i Wnet into the folder and i have everytinh there took a screen shot of it.
Am i doing something wrong
I believe its a weird permissions error. There's a guide to getting these to work in the main Viper4Android thread here on XDA.
MStrawder said:
I believe its a weird permissions error. There's a guide to getting these to work in the main Viper4Android thread here on XDA.
Click to expand...
Click to collapse
Would you be able to link to that fix please.
Also i removed viper and verytime it asks me to install drivers and i do and when i reboot start viper it asks me to do it again. Sorry a little frustrated
Viper4Android That's the thread. Its towards the end. As far as troubleshooting, I can only recommend removing all of the modules and starting from scratch. The steps at the top of this thread worked perfectly for me.
MStrawder said:
Viper4Android That's the thread. Its towards the end. As far as troubleshooting, I can only recommend removing all of the modules and starting from scratch. The steps at the top of this thread worked perfectly for me.
Click to expand...
Click to collapse
Someone recommened to install the dolby app and it would work going to try it and let you know.
MStrawder said:
Viper4Android That's the thread. Its towards the end. As far as troubleshooting, I can only recommend removing all of the modules and starting from scratch. The steps at the top of this thread worked perfectly for me.
Click to expand...
Click to collapse
So far nothing i have done has fixed the impulse problem says its not there but the files are in there.
I don't have the link, but Google for Viper4Android 2.7 profiles. A guy has a GitHub page where he's updated them all to work with Viper 2.7. I remember having to download those as the old profiles didn't seem to be recognized.
MStrawder said:
I don't have the link, but Google for Viper4Android 2.7 profiles. A guy has a GitHub page where he's updated them all to work with Viper 2.7. I remember having to download those as the old profiles didn't seem to be recognized.
Click to expand...
Click to collapse
So afterman trys i was able to get the convolver and impulse response to work. One last question on my old one plus 7 pro i have viper installed with a rom on it and i have this layout wanted to know where i could find this version. Also Its the same version i am using but the layout is different.
I can't spot a difference in the two images. It won't enable though until you toggle the Master Power button to on.
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.
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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Downloads
Here
Flashing instructions
Here
Upgrade instructions
Here
Sources:
- LineageOS
- Kernel Tree
Happy modding!
Reserved
Okay but does it run Crysis?
I've been running it and everything seems to work ok
Links provided by you are loopy and I don't seem to find any link to the "firmware.zip" you have mentioned in your website. Please write some more details. I'm very excited to flash it
Edit: Found everything.
Hey @Its_Vixano,
Thank you for this release in the first place, I'm really happy with it. Seems to be stable so far after the few days I've been running it.
I have only noticed some minor UX bugs with the recents(/gestures) while using Trebuchet (I haven't experienced it yet after switching to Lawnchair), but a more important issue is that I cannot play audio on a Bluetooth device.
I tested it with several devices, they show up as connected, but they remain silent even on maximum volume.
My guess (from the logs and my experience) is that for some reason the bluetooth audio connection cannot be built up correctly, it seems like it gets interrupted every second or so.
Other than that, do you know if the camera quality is better with the stock MIUI camera app? If yes, maybe it would also be worth to include it in this ROM as well, since others are starting to include it, I figured it wouldn't be too much of a hassle.
I only meant these as suggestions/observations, if you need more information on the bug, please let me know.
Thanks in advance.
ardrift said:
but a more important issue is that I cannot play audio on a Bluetooth device.
I tested it with several devices, they show up as connected, but they remain silent even on maximum volume.
My guess (from the logs and my experience) is that for some reason the bluetooth audio connection cannot be built up correctly, it seems like it gets interrupted every second or so.
Click to expand...
Click to collapse
Are you sure is not caused by any system modification or modules flashed via magisk ??
I use everyday a bluetooth pair (AAC, Samsung buds live) without any issues
Its_Vixano said:
Are you sure is not caused by any system modification or modules flashed via magisk ??
I use everyday a bluetooth pair (AAC, Samsung buds live) without any issues
Click to expand...
Click to collapse
Thanks for the hint, I tried rebooting to safe mode so that all the 3rd party apps get disabled, and also disabled some system modifications manually (tasker, dev options), but these didn't help unfortunately :/
But now that you mentioned it's working for you, I thought that the reason might be that I flashed your ROM to the V13.0.9.0.SKOEUXM firmware I had installed previously. I will re-test with the V13.0.4.0.SKOMIXM firmware that you recommend in your guide as well, I'll get back with the results.
P.S: I have attached the installed modules list and the error logs.
ardrift said:
Thanks for the hint, I tried rebooting to safe mode so that all the 3rd party apps get disabled, and also disabled some system modifications manually (tasker, dev options), but these didn't help unfortunately :/
But now that you mentioned it's working for you, I thought that the reason might be that I flashed your ROM to the V13.0.9.0.SKOEUXM firmware I had installed previously. I will re-test with the V13.0.4.0.SKOMIXM firmware that you recommend in your guide as well, I'll get back with the results.
P.S: I have attached the installed modules list and the error logs.
Click to expand...
Click to collapse
Can you try reflashing the fw i mentioned ??
Its_Vixano said:
Can you try reflashing the fw i mentioned ??
Click to expand...
Click to collapse
I flashed it now and it fixed the problem, thanks for confirming that it was working for you.
Thank you for sharing this. I have a few questions. Is there a touch head option in fingerprint? Do banking apps give root warning? Camera app snap? Do you have any gcam you recommend or can we install miui camera?
Just pushed august ota
enjoy
by_BenjamiN said:
Thank you for sharing this. I have a few questions. Is there a touch head option in fingerprint? Do banking apps give root warning? Camera app snap? Do you have any gcam you recommend or can we install miui camera?
Click to expand...
Click to collapse
The least i can do for banking apps is to include ih8sn on my builds (which i already do it)
You're doing a remarkable work. What about submit for official build?
Its_Vixano said:
Just pushed august ota
enjoy
Click to expand...
Click to collapse
Thanks a lot for your great work!
AudioSculpt said:
You're doing a remarkable work. What about submit for official build?
Click to expand...
Click to collapse
who knows ?
Not sure where to ask this, I apologize if I'm asking in the wrong place. But how is the lack of the proximity sensor is handled in this ROM?
Do you face any issues when accepting calls or listening to WhatsApp audio messages?
Thanks for sharing your work.
Has anybody managed to get Google wallet working?
Flashed today, so far everything looks very good
Is it possible to get the stock Xiaomi Cam on this rom?
I need makro and ultrawide cam
Thanks a lot for this great Rom
I have a Xiaomi Mi 11 Lite 5G NE (256gb DG - Global Version). I bootloader unlocked it after a week's usage. It is visible to ADB and Fastboot on Windows 10.
Ran into a bit of a problem following the flashing guide.
Downloaded the following files:
boot.img
192 MB17 days ago
dtbo.img
24 MB6 days ago
lineage-19.1-20220824-UNOFFICIAL-lisa.zip
1.1 GB17 days ago
vendor_boot.img
96 MB17 days ago
From the link. Successfully flashed boot.img, vendor.boot.img, and dtbo.img. It automatically selected _b as a destination on the phone. Attempting a reboot with power + volume up never got me to a recovery screen, only had the Mi logo flash before re-entering fastboot.
I re-read the instructions and there's a place where it is a little unclear as to if recovery.img is to be used for all phones or not despite only being in the ys1 repository. So I downloaded that and flashed it (successfully), it auto selected _a as a destination.
Phone still continues to reboot to fastboot, but now without the Mi logo flashing (guessing I blew away whatever was left of the factory ROM on _a with that last move).
Suggestions on what to do next? I'm stuck at a place where the phone is in fastboot mode and connected to a Windows machine with adb and the proper drivers but I'm guessing has no bootable recovery or ROM so sideloading isn't an option.
Hello community,
I have no programming experience whatsoever but I am interested in having my Oneplus 9 Pro degoogled because I value my privacy.
Installing a Custom ROM is not an option yet because I don't seem to have found a Camera app that is as satisfying as the stock one (I especially like its Pro mode).
My friend suggested installing Magisk and Debloater, delete all Google services and stay with the Stock rom. So I unlocked the bootloader, booted into fastboot, booted TWRP. I flashed an official firmware Update (Oxygen OS 11.2.10.10.LE15AA), it loaded up to 47% and then showed an Error. I pushed some buttons until I was stuck in a Fastboot-Loop. Luckily I soon found a thread and tried out "fastboot --set-active=b" which solved the issue by booting into Oxygen OS 11.2.10.10.
I would like to understand what happened - I guess I tried to flash an update that was not full and somehow got mixed up with the slots, but the Update was installed anyway on the other slot which I was able to access with changing active slots - but I don't really know.
Anyway, what I really like to know is if anyone has any suggestions for me how to move on from here.
I downloaded the Magisk App but wasn't able to install it properly as I wasn't able to extract the boot.img. I tried with Python 3.8 and payload dumper on my Mac but the command "pip install -r requirements.txt" doesn't work (neither does python -m pip install -r requirements.txt or putting ./ in front of it - it always answers with "no such file or directory").
I also couldn't flash it with TWRP as I don't have the zip file and I heard conflicting opinions about that confused me.
Can somebody help me with a guide for dummies? Or maybe even come up with a different solution for my need to access the Stock Camera App but not having Google Tracking involved in any of my phone activities.
Thank you, this will be highly appreciated!
lai.sha said:
Hello community,
I have no programming experience whatsoever but I am interested in having my Oneplus 9 Pro degoogled because I value my privacy.
Installing a Custom ROM is not an option yet because I don't seem to have found a Camera app that is as satisfying as the stock one (I especially like its Pro mode).
My friend suggested installing Magisk and Debloater, delete all Google services and stay with the Stock rom. So I unlocked the bootloader, booted into fastboot, booted TWRP. I flashed an official firmware Update (Oxygen OS 11.2.10.10.LE15AA), it loaded up to 47% and then showed an Error. I pushed some buttons until I was stuck in a Fastboot-Loop. Luckily I soon found a thread and tried out "fastboot --set-active=b" which solved the issue by booting into Oxygen OS 11.2.10.10.
I would like to understand what happened - I guess I tried to flash an update that was not full and somehow got mixed up with the slots, but the Update was installed anyway on the other slot which I was able to access with changing active slots - but I don't really know.
Anyway, what I really like to know is if anyone has any suggestions for me how to move on from here.
I downloaded the Magisk App but wasn't able to install it properly as I wasn't able to extract the boot.img. I tried with Python 3.8 and payload dumper on my Mac but the command "pip install -r requirements.txt" doesn't work (neither does python -m pip install -r requirements.txt or putting ./ in front of it - it always answers with "no such file or directory").
I also couldn't flash it with TWRP as I don't have the zip file and I heard conflicting opinions about that confused me.
Can somebody help me with a guide for dummies? Or maybe even come up with a different solution for my need to access the Stock Camera App but not having Google Tracking involved in any of my phone activities.
Thank you, this will be highly appreciated!
Click to expand...
Click to collapse
Never mind - I just found it here: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-c-65.4252373/
I'm stil open for better solutions if someone has them!
Hey there!
Loading up to 47% and then throwing an error is actually quite normal, it should still succeed.
Anyway, some intelligent person was able to manage to move the stock OOS cam to custom ROM's. I'm currently running Nameless which is Android 12 which has the OOS cam.
Since you asked for a non-gapps build, you should look for a 'pristine' or 'vanilla' build. I know out of the top of my head that StagOS has builds like this, but you can also search the forums yourself. If the title of the ROM says [OOS Cam] then the stock camera app is included.
You can also use ADB to debloat (remove) all google stuff from your phone. This is a guide which could be helpful: https://forum.xda-developers.com/t/...bloating-thread-for-the-s20-u-series.4089089/
This way, you can keep the same stock software without having to go through the hassle of installing a custom ROM
GolovaRaoul said:
Hey there!
Loading up to 47% and then throwing an error is actually quite normal, it should still succeed.
Click to expand...
Click to collapse
Oh thank you, that is very satisfying to know. Why is that?
GolovaRaoul said:
Anyway, some intelligent person was able to manage to move the stock OOS cam to custom ROM's. I'm currently running Nameless which is Android 12 which has the OOS cam.
Click to expand...
Click to collapse
Are you thinking of this one: https://forum.xda-developers.com/t/apk-oneplus-camera-for-any-a11-custom-rom.4350205/ That's the 7 Pro App, which is crashing on my friend's phone on Lineage OS in macro mode
GolovaRaoul said:
Since you asked for a non-gapps build, you should look for a 'pristine' or 'vanilla' build. I know out of the top of my head that StagOS has builds like this, but you can also search the forums yourself. If the title of the ROM says [OOS Cam] then the stock camera app is included.
You can also use ADB to debloat (remove) all google stuff from your phone. This is a guide which could be helpful: https://forum.xda-developers.com/t/...bloating-thread-for-the-s20-u-series.4089089/
Click to expand...
Click to collapse
Great, thank you! As I got Magisk running, I prefer the debloater as I can play with it without Laptop access
GolovaRaoul said:
This way, you can keep the same stock software without having to go through the hassle of installing a custom ROM
Click to expand...
Click to collapse
Thank you for all your help!
lai.sha said:
Oh thank you, that is very satisfying to know. Why is that?
Are you thinking of this one: https://forum.xda-developers.com/t/apk-oneplus-camera-for-any-a11-custom-rom.4350205/ That's the 7 Pro App, which is crashing on my friend's phone on Lineage OS in macro mode
Great, thank you! As I got Magisk running, I prefer the debloater as I can play with it without Laptop access
Thank you for all your help!
Click to expand...
Click to collapse
Eeehm I don't know why it gets stuck at 47%. It's a common issue, you can google it and you'll find lots of results
{
"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"
}
And I mean these ROM's for example. Maybe some of these ROMs in the list also have the OxygenOS cam but I don't know. They are pre-built into the ROM so you don't need to do anything, just install the ROM and you should have the OxygenOS cam also
GolovaRaoul said:
Eeehm I don't know why it gets stuck at 47%. It's a common issue, you can google it and you'll find lots of results
View attachment 5742135
And I mean these ROM's for example. Maybe some of these ROMs in the list also have the OxygenOS cam but I don't know. They are pre-built into the ROM so you don't need to do anything, just install the ROM and you should have the OxygenOS cam also
Click to expand...
Click to collapse
Interesting, I thought that maybe that's what you meant but I wasn't sure if it just means "compatible" with...
Thank you so much, I guess it's time to play