Database Develop

Viper 4 android on G5S Plus working via Magisk module

Unlocked, rooted, magisk installed. Stock 7.1.1, resurrected kernel v3.0, TWRP 3.2.1 r15
All good.
Driver installed.
Processing is always: No
Anyone got it working? Tried everything under the sun.

barbaroja said:
Unlocked, rooted, magisk installed. Stock 7.1.1, resurrected kernel v3.0, TWRP 3.2.1 r15
All good.
Driver installed.
Processing is always: No
Anyone got it working? Tried everything under the sun.
Click to expand...
Click to collapse
I'm on validus 8.0, twrp r15, and it's all good...
{
"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"
}
Try uninstalling the driver and re-installing. I am using SuperSU 2.82sr5 though, so if Magisk is the issue I'm probably not much help here.
Also - stupid question - you renamed the vendor/etc/audio_effects.conf file, right? I don't think it would install the driver if you didn't...just thought I'd ask tho to be sure.

startswithPendswithOOH said:
I'm on validus 8.0, twrp r15, and it's all good...
Try uninstalling the driver and re-installing. I am using SuperSU 2.82sr5 though, so if Magisk is the issue I'm probably not much help here.
Also - stupid question - you renamed the vendor/etc/audio_effects.conf file, right? I don't think it would install the driver if you didn't...just thought I'd ask tho to be sure.
Click to expand...
Click to collapse
Yeah works on 8 but doesnt seem to work on rooted stock as the OP describes. Installs fine, shows the drivers are there but nothing changes.

bishop0114 said:
Yeah works on 8 but doesnt seem to work on rooted stock as the OP describes. Installs fine, shows the drivers are there but nothing changes.
Click to expand...
Click to collapse
Yep, ur right...my bad. Somehow I misread the the OP as 7.1 resurrection & thought they were referring to resurrection remix ROM. Damn, I really need to get some glasses.
I tried to get it working on stock with SuperSU instead of magisk & got the same results as OP. Strange.

I git it working on stock rom without any changes in files. I installed the Resurrected Kernel, Magisk 14.6, V4A Magisk version after that was done I opened the app and changed FX Compatability mode to Compatible and didn't even have to change anything regarding files or removing the Audio Fx app. Hope this helps

MAZE ALPHA update V09_20180117_20180117-1052

I have a maze alpha which got this update, when it tries to install the update, it gives the android error before even getting to the installation screen ( in recovery mode), no matter what I do it just does this with the update, the phone is the 4GB MODEL it is not routed, and it has the stock ROM, when it does the error it doesn't brick, you just have to hold the power button to turn it off and then it starts up normally.

I haven't received this update yet. I still in the V08... Did you receive an OTA Update or did you find the Firmware in somewhere else?

Punisher66 said:
I haven't received this update yet. I still in the V08... Did you receive an OTA Update or did you find the Firmware in somewhere else?
Click to expand...
Click to collapse
I got this as an OTA update, I am in the UK, they may not have released it in other regions.

I'll try to update later. Need to flash stock recovery again first.
https://www.needrom.com/download/maze-alpha-4gb-ota-v9/
{
"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"
}
Edit: it updated fine.
.
.

N10A said:
I'll try to update later. Need to flash stock recovery again first.
https://www.needrom.com/download/maze-alpha-4gb-ota-v9/
Edit: it updated fine.
.
.
Click to expand...
Click to collapse
Are you sure the rom that is on there is the correct one and working

nebpar said:
Are you sure the rom that is on there is the correct one and working
Click to expand...
Click to collapse
It's the one I used on my 4G Maze Alpha. I was rooted with Magisk and it installed fine anyway. I just had to re-root after it was done.

N10A said:
It's the one I used on my 4G Maze Alpha. I was rooted with Magisk and it installed fine anyway. I just had to re-root after it was done.
Click to expand...
Click to collapse
thanks for that it now works, it is annoying we had go to this much effort in order to update our phones, also you are aware you can root your phone in the developer options on your phone.

nebpar said:
thanks for that it now works, it is annoying we had go to this much effort in order to update our phones, also you are aware you can root your phone in the developer options on your phone.
Click to expand...
Click to collapse
Hmm no, I don't seem to have that option.

my mistake, i am pretty sure i saw the option in a previous version right underneath the OEM unlocking option in dev - options but it does not appear to be available in this version.

Can't get this update to install. Get the error every time. Hope did you install it?

N10A said:
It's the one I used on my 4G Maze Alpha. I was rooted with Magisk and it installed fine anyway. I just had to re-root after it was done.
Click to expand...
Click to collapse
Hello,
How have you managed to root your Maze Alpha? I am guessing it is a 64GB/4GB version?

Magisk Hide

Magisk Hide doesn't seem to be working when it comes to my automobile's app, Uconnect. I'm rooted and now the Uconnect app states that I'm using an unsupported device. It worked before rooting.View attachment magisk_log_20181022_153305.log
{
"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"
}

tried clearing apps data?

kamilmirza said:
tried clearing apps data?
Click to expand...
Click to collapse
Yes. I even uninstalled, then reinstalled the Uconnect app.

destiple said:
Yes. I even uninstalled, then reinstalled the Uconnect app.
Click to expand...
Click to collapse
THIS great module might help :fingers-crossed:

Destiple, can you confirm whether MagiskHide Props Config, which kamilmirza referred you to, worked?
Alternately, did you find another solution to get Uconnect working?

If you haven't already you're probably better off testing the brand new MagiskHide (rewritten from scratch) in the Canary builds (currently at build 18110).

Didgeridoohan said:
If you haven't already you're probably better off testing the brand new MagiskHide (rewritten from scratch) in the Canary builds (currently at build 18110).
Click to expand...
Click to collapse
That's very good to know. I'm nervous about running a Canary build on my normal phone, but I'll see if I can find a spare to test it on.
Will the new MagiskHide be on the next Magisk update, or is it several versions away from being in the stable build?

Try using the "Hide Magisk Manager" option in the settings. I was having the same problem, but after doing that and restarting I can use the Uconnect app again.

Coop9 said:
Try using the "Hide Magisk Manager" option in the settings. I was having the same problem, but after doing that and restarting I can use the Uconnect app again.
Click to expand...
Click to collapse
Good to know! I tried it - hiding the manager by itself wasn't enough. But once I added Uconnect to the apps being hidden, *then* the app finally loaded.
Of course, upon trying to log in, the app immediately crashes. Would that have anything to do with it being added to the MagiskHide list?

EOL_[MM-P][6.0-9.0][Magisk]Dolby-20181123

Dolby Digital Plus for 9.0 ОS(Pie)
{
"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"
}
Hi. I present the mod Dolby Digital Plus (interface and functionality is the same as that of Dolby Atmos). Theoretically should work on OS 6.0-9.0. I checked only on Oreo and Pie (Samsung Tab A 10.1 LTE and Xiaomi Redmi 4x). The mod is based on the post from here . I removed the garbage, made it in one archive and added an uninstaller. Install via TVRP to a clean firmware. Added magisk build.
Download:
DDP for TWRP:
DDP for Magisk(preferable):
Uninstaller for TWRP:
Credits: [MENTION=7433324]A.R.I.S.E. Sound Systems[/MENT
https://www.opendesktop.org/p/1274328/
@heindrix(and AKAVKL / AKA_VKL) for his Dolby Digital magisk module

Reserved

Thanks for your work. I'm installing this mod in OnePlus 5T and works with AML alongside other modules. Till now I was using other DD magisk module which was incompatible with AML, but your module works properly.
Later I will check other devices: Redmi Note 4(Pie) and OnePlus 6(Pie).
Thanks.

I've tried it in the Pixel Experience (Pie) rom and presents Forced Closing. Is it necessary to have Root? (I have installed the TWRP version)

sonry said:
I've tried it in the Pixel Experience (Pie) rom and presents Forced Closing. Is it necessary to have Root? (I have installed the TWRP version)
Click to expand...
Click to collapse
Yes of course.

Everything working fine! Compatible with Viper4Android! A huge thanks, Dev!

Working on Redmi 3S.
Even with audio fx.
Loving it

I'm using it with MIUI 10 from xiaomi.eu .. have to disable snapdragon+ audio mod in Spotify .. WORKS !! Good job

Whenever i sent messages continuously or receive messages continuously at same time, my message app never shows timing for each message separately either received or sent, it always shows time for some texts not every text.
Please help, i am asking this question fromlast 1 year at different forums, never gets an answer.

Ahmed Osama 14 said:
Whenever i sent messages continuously or receive messages continuously at same time, my message app never shows timing for each message separately either received or sent, it always shows time for some texts not every text.
Please help, i am asking this question fromlast 1 year at different forums, never gets an answer.
Click to expand...
Click to collapse
change msg app to google msg app it helps i guess

Working perfectly together with Viper4android on Los 15.1 on a Note 4. Thanks to the dev!

Not working on .eu ROMS. Just FC's
MIUI10 btw.

everything working buddy , thanks for sharing

Where is link

How to find magisk module link

"Android" and "Android OS" are draining my battery

Hello everyone, have a nice day. Here are the screenshots first :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've been using my Mi 9 for a month. It's just great, everything work like a charm, smoothly, like butter. But I've been experiencing some battery issues for 2 or 3 days. "Android" and "Android OS" are draining my battery, (approx. 50 percent total) I can feel, my device is heating up. Can you tell me, how can I solve this problem, can you help me please? Thank you so much, really appreciated.

Are you on stock rom? My device was a bit warmer when I was on stockrom at least. Now I'm on Revolution OS (+ I debloated that additionally) and everything seems fine (using it since ~1 month as well). I can't put my finger on that problem but I ran into something similar as well!
I would try debloating your device or switch your rom (Go with xiaomi.eu or Revolution OS). I hope that helped!

MarvinMe said:
Are you on stock rom? My device was a bit warmer when I was on stockrom at least. Now I'm on Revolution OS (+ I debloated that additionally) and everything seems fine (using it since ~1 month as well). I can't put my finger on that problem but I ran into something similar as well!
I would try debloating your device or switch your rom (Go with xiaomi.eu or Revolution OS). I hope that helped!
Click to expand...
Click to collapse
How to debloat?
Im on xiaomi.eu witch magisk

Thank you for your answer. BTW, I forgot to mention my software version, MIUI 10.2.3.0. Is there any method to solve this problem, I'm new at Android and flashing ROMs.
I'm thinking of that, maybe, I experienced that problem because of installing an app, or something.

nuri552 said:
Thank you for your answer. BTW, I forgot to mention my software version, MIUI 10.2.3.0. Is there any method to solve this problem, I'm new at Android and flashing ROMs.
I'm thinking of that, maybe, I experienced that problem because of installing an app, or something.
Click to expand...
Click to collapse
Try holding down the volume up and power buttons at the same time so your phone boots into recovery. I'm pretty sure the stock recovery had a wipe system cache option. If it does wipe the system cache, boot back into the system and see if there is any improvement.
You could also try using the built in cleaner in the security app. Since it's a system app the built in cleaner can clean app cache and various other things that a cleaner downloaded from the Play Store could not without having root access. Just make sure you look at what it's cleaning before you do it or the cleaner might delete something you actually want to keep like media artwork.
You could also download an app like Better Battery Stats from the Play Store. Without root access you will need to follow the instructions showing how to give the app elevated privileges via ADB (they provide step-by-step instructions that should be easy to follow). BBS might be able to show you if a specific app is causing your problem.