yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Android Development] foober:
Can you write about magisk? What a files must i dl and flash. Please give me link.

Wysłane z mojego ASUS_Z00A przy użyciu Tapatalka
[Xperia Z1 Android Development] aidebe1:
https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Xperia Z1 Android Development] SuperLamic:
btw [MENTION=6371423]Red-code[/MENTION] can you use that Fork button on the kernel repository instead of kanging it?
[Xperia Z1 Android Development] Red-code:
I got a problem with internet connection in my country (it has low speed and limited) so I had to do that because it uses less bandwidth
[Xperia Z1 Android Development] SuperLamic:
well, I think you're misunderstanding what fork does. You don't have to upload anything. You fork and then you clone from the fork on your git.

It seems like you had to upload whole source to your git now, with fork you don't have to.
[Xperia Z1 Android Development] Red-code:
my problem is with cloning

clone fork > 2789155 items

download zip > 44874 items

in the best condition (no hang-ups) my system should keep working for about a day to clone full source
[Xperia Z1 Android Development] Red-code:
v3-beta released
[Xperia Z1 Android Development] Red-code:
stable one is now available;)
[Xperia Z1 Android Development] gibbykshmr:
:D:D
[Xperia Z1 Android Development] miXXed404:
hi after installing a modified Kernel v3 by Red-code i have purple lines on the lock screen and icons, the rest is just ok, anyone?
[Xperia Z1 Android Development] Red-code:
Rom???

Device??

Are you sure that you are not using beta version???
[Xperia Z1 Android Development] miXXed404:
SuperLamic Lineage 14.1 (i even tried flashing kernel on rr 5.8.4 but same issue)

Sony Xperia Z1

yes i'm sure
[Xperia Z1 Android Development] Red-code:
could you send me a picture of that
[Xperia Z1 Android Development] itemmaster:
the picture not gonna show you the error of purple lines, it's from aftermarket screen, in version 3 its corrected but I have the same issue on v2 (I also have replaced my screen) I corrected lowering the values of colours to 203 195 189 in kernel adiutor
[Xperia Z1 Android Development] andron k:
I lost root with v3 kernel and britnes regulation don't work and display too vivid as for me.
[Xperia Z1 Android Development] Red-code:
https://xdaforums.com/showpost.php?p=73738557&postcount=68
[Xperia Z1 Android Development] aidebe1:
I don't know if it's just me but after installing version 3 I don't see any extra options but the standard kernel ones... ;)
[Xperia Z1 Android Development] Red-code:
what options???:confused:
[Xperia Z1 Android Development] aidebe1:
For example TCP_congestion_algorithms

cpu-hotplug, zen-decision...etc. are missing just the standard kernel options are available... :)
[Xperia Z1 Android Development] Red-code:
Do you have root access????

What app you are using for kernel configs???
[Xperia Z1 Android Development] aidebe1:
Root is granted to kernel auditor. .

Lineage os, z1 6903
[Xperia Z1 Android Development] Red-code:
Run this test command in terminal emulator

su
echo 1 > /sys/kernel/power_suspend/power_suspend_mode
cat /sys/kernel/power_suspend/power_suspend_mode

post the results

or explore the place and tell me if you found files
[Xperia Z1 Android Development] aidebe1:
My bad... After kernel flashing without reboot I was flashing super su and this was the reason... Sorry everything is working excellent ;)
[Xperia Z1 Android Development] luckywj13:
Double tap to wake doesn't work
[Xperia Z1 Android Development] Red-code:
activate it in kernel auditor or pimp my z1 :crying::crying::crying::crying:
[Xperia Z1 Android Development] m9in_KIRCHIK1488:
Swipe2wake

Please, add swipe2wake
[Xperia Z1 Android Development] luckywj13:
thanks :D
[Xperia Z1 Android Development] Comstock:
Best kernel mod. Thanks, Red-code.

Maybe you know how add operator name in statusbar? How in Carbon ROM.
[Xperia Z1 Android Development] elSarych:
HmHm. Flashed your kernel v3 to LOS by SuperLamic. In kernel Adiutor I cant set the cpu freq tower than 1881 mhz.
[Xperia Z1 Android Development] Mysteryhunter:
Tested kernel v3 on superlamic los, but brightness doesn't respond when adaptive brightness and live display disabled, screen always on max brightness..

Edit: sorry my bad, after few reboots suddenly working fine..
[Xperia Z1 Android Development] unan21:
Root with supersu. Maybe work
[Xperia Z1 Android Development] TheCarFierce:
Can be used in Z1C
[Xperia Z1 Android Development] unan21:
Maybe no. Beacuse diferrent driver in lcd, you will get blackscreen
[Xperia Z1 Android Development] Styler911:
is it just my phone or does the kernel have massive battery drain? When phone reaches 14 %, battery drains instantly to 0 % and shuts down. :/
[Xperia Z1 Android Development] Red-code:
calibrate your battery
[Xperia Z1 Android Development] Red-code:
new version with vibration feature for wake up gesture (not tested)

DOWNLOAD

enable it by this command:

echo 1 > /sys/devices/virtual/input/clearpad/wg_vib_enable

or just simply import these controls to kernel adiutor

please report if it worked because my vibrator is broken
[Xperia Z1 Android Development] unan21:
[MENTION=6371423]Red-code[/MENTION] auto brighness not working?
[Xperia Z1 Android Development] Red-code:
reboot your device using terminal emulator
[Xperia Z1 Android Development] Styler911:
how? all tutorials that i read are old :/
[Xperia Z1 Android Development] gibbykshmr:
Open whatever terminal emulator app you have installed and type the command "reboot". Simple as that.

---------- Post added at 11:06 PM ---------- Previous post was at 11:03 PM ----------

Flashed and enabled the wgv, but can't test either 'cos of broken vibrator....
[Xperia Z1 Android Development] MIcHiJK:
Hey [MENTION=6371423]Red-code[/MENTION].

Is it possible that I kernel v. 2.0 has a better battery life than the newer kernels or im just Imagine that :D? And have you plans to make the new versions for carbon?
[Xperia Z1 Android Development] TheCarFierce:
Will you be able to develop Z1C?
[Xperia Z1 Android Development] en0203:
Hi [MENTION=6371423]Red-code[/MENTION],

Thank you for this wonderful kernel. On my phone the dt2w doesn't always work. Is there anything I can do to make it work always?

Thank you.
[Xperia Z1 Android Development] fribriz:
Thank you. Kcal dt2w worked for me. v3.2 went to bootloop.

Wake is working. Switch on with Kernel Auditor app.
[Xperia Z1 Android Development] fribriz:
Hi [MENTION=6371423]Red-code[/MENTION]

Something strange I observed. Massive power drain. About an hour after this, battery level dropped to 25%. Phone was on the pocket.
[Xperia Z1 Android Development] fribriz:
Pic
[Xperia Z1 Android Development] fribriz:
After DT2W is turned off
[Xperia Z1 Android Development] Webetter1990:
Can Carbon support sony xperia z ultra togari ? The device tree is same as xperia z1 and xperia z1c ，they all use rhine platform,The diffrence is the touch driver ,togari uses max1187x touchscreen driver.I tryed to build lineageos 14.1 for it，but there are some issues. Please let the only sony pad flashship alive.I will provide the device tree and kernel 3.4 and local_manifests of togati for you.Thanks
[Xperia Z1 Android Development] andron k:
What is DT2W and how to turn it off?
[Xperia Z1 Android Development] acidrums4:
Double-tap to wake. As OP said, touch the screen with two fingers at the same time when phone is locked to wake the screen.
[Xperia Z1 Android Development] C.T.E:
I think this 3.3 version is more faster and stabil and dt2w is working good. In addition to this my camera is opening faster responding faster too. It is very good. Thank you for your work.
[Xperia Z1 Android Development] Andresruizj:
I just flashed the latest version (v3.3) and it goes to bootloop in LOS Logo :(

Xperia Z1 C6902 - Latest Build LOS 14.1 SuperLamic (25/1/18).
[Xperia Z1 Android Development] andray750:
in your version 3 mp decision is unabled. so what?!
[Xperia Z1 Android Development] r_ramalho:
Tried this kernel 3.3 into z1 c6903 with the latest 14.1 Lineageos from Superlamic and it won't boot. Stuck on Lineageos logo.
[Xperia Z1 Android Development] andray750:
what about fauxsound in V3.3

hi Red-Code,

is even "fauxsound" not implemented in V3.3?

Then for me there is no reason for your kernel.

1. is it not possible to -reboot recovery- your kernel just starts.(v2. --others no tested, not needed for me)

2. is it not possible to "clean cache davlik" in TWRP, always get bootloops. (all versions since v3.2 ;have to do it in Titanium.)

3. nothing in your kernel differs from "hexagon-kernel" (that's o.k. but also no reason for your kernel)

I thought you would do better with the next version
[Xperia Z1 Android Development] Andresruizj:
Same for me, any fix? :confused::(
[Xperia Z1 Android Development] Malle355:
Yep same problem here :confused:
[Magisk] metaspook:
[IMG="aos-banner"]http://i.imgur.com/J4lwtdl.png[/IMG]​

Intro:

ViPERFX is modified version of original ViPER4Android by Audio Labs which is very popular audio mod around the world of Android and probably the best audio mod ever made.

Requirements:

Android 5.0 - 8.0

Magisk v14 +

AlienoidMod test-C01 +

Modifications:

+ ViPER4Android_v2.5.0.5.apk based.

+ Material AMOLED UI.

+ More...

Downloads:

Follow the attachments...

Contributors

metaspook

Version Information

Status: Test

Test Version: C01

Release Date: 2017-09-17
[Magisk] metaspook:
Reserved

Reserved
[Magisk] metaspook:
Reserved2

Reserved2
[Magisk] vergilbt:
Only a question: what's the difference to module [MENTION=5357345]ahrion[/MENTION] is providing?

https://xdaforums.com/showthread.php?p=71533072
[Magisk] Skittles9823:
Just a dope reskin and I assume the module is written differently to work with the Alienoid framework.
[Magisk] L.F.B.:
Thanks one more time metaspook!

This module just works! And is updated. Unlike others that are outdated.

Long live for this module that is simple and efficient!??
[Magisk] metaspook:
understand the lineup.

thanks.. to you also guys for responses.... :good:

I hope you guyz starting to understand the lineup. :fingers-crossed:

Some Q/A

Q: Why its need to depend on a framework?

A:

1. To make the module size smaller.

2. Update faster.

3. Fix bug faster.

4. Less code to write.

5. . . . as more. .. .. as you explore. .. . .

Q: What is the deference?

A:

1. When you first installing AlienoidMod one of its function is cloning audio config files from your system, ....yes cloning, not only coping because it not only copy the config files from system but also their respective permissions, se-context etc. Then when u install ViPERFX module it utilize those audio config files AlienoidMod cloned before and utilize several functions from. So you can use several Audio Mods for Magisk (if based on AMF) all togather.

2. If you are a module developer you do not need to put lines of config file's codes in any audio lib file, all you have to do is use the 'amf' command line interface, which is very simple. like currently

'audmod <source dir> <target dir>'

or

'amf audmod <source dir> <target dir>'

command can clone the all necessary config files from source to target directory.

3. I'm also writing more functions for 'amf' command line interface to make it more powerful that you could use in various type of modules.
[Magisk] VC-34:
Is a deep_buffer remover needed or is it in the framework included?
[Magisk] thetrukos:
Hello, i just installed both modules with twrp, both are shown in magisk as module, but i do not see vipers apk. Also in magisk viper says "module will update in next reboot" . Thanks
[Magisk] Meikk99:
I had a similar issue, try installing the alienoidmod module, rebooting and then installing the viper module.
[Magisk] metaspook:
All necessary audio config will cloned by AlienoidMod and All V4A patching n Deep buffer removing will done by the ViPERFX module.
[Magisk] metaspook:
For two of you and other, I want to inform that as this is at in testing stage and builds are now testing so I don't changing the version code for new builds during this testing periods so when I updated a new test build all you have to do is follow the steps below.

1. Remove previous test version AlienoidMod, ViPERFX and other module related to them from Magisk app.

2. Reboot

3. Install AlienoidMod form Magisk app or twrp

4. Reboot

5. Install ViPERFX and or other AlienoidMod module from Magisk app or twrp but if, then you have to keep a reboot gap between them.

6. Reboot.

That means you have to install freshly after a new test build comes. Please consider this boring kinda steps while this testing period. When the release build will come you don't have to do this necessarily.

Thanks you.
[Magisk] KaiStone:
Module seems cannot help MIUI 9. Viper4Android shows notice that reinstall driver. Could you please take a look at that :D
[Magisk] xbenjamin87x:
Same issue here. I'm on latest global miui 8. (8.5.4.0)

If I press "yes" to install the driver, nothing happens.
[Magisk] metaspook:
Is there any other Viper mod working on your current rom? if, then give me the link then I'll look over where need to patch. :good:
[Magisk] metaspook:
viperfx-test-A05.zip

uploaded... ok
[Magisk] endrju_master:
Don't work on xiaomi mi5 running Android 7.0 miui 9 by xiaomi.eu

Wysłane z mojego MI 5 przy użyciu Tapatalka

---------- Post added at 04:46 PM ---------- Previous post was at 04:46 PM ----------

Wysłane z mojego MI 5 przy użyciu Tapatalka
[Magisk] KaiStone:
Iam currently apply this trick to make V4A work on MIUI 9 and some other ROMs
[Magisk] metaspook:
Can you test it and let me know the steps below?

1. Copy "amf-services.sh" from "/magisk/amf/amf-services.sh" to "/magisk/.core/service.d/amf-services.sh"

2. Reboot

3. Check now working or not
[Magisk] KaiStone:
It's the same thing on RR 5.8.4. Viper4Android requires reinstall the driver.

On Samsung 6.0.1, I even cannot install your modules sucessfully. Both AlienoidMod and ViPERFX modules status shows "Module will be updated at next reboot". If I flash your modules through recovery, modules status shows "No info provided".
[Magisk] xbenjamin87x:
Sorry

I did absolutly nothing and now it works ? Maybe the new version.

Thanks a lot!
[Magisk] metaspook:
I want to inform that as this is at in testing stage and builds are now testing so I don't changing the version code for new builds during this testing periods so when I updated a new test build all you have to do is follow the steps below.

1. Remove previous test version AlienoidMod, ViPERFX and other module related to them from Magisk app.

2. Reboot

3. Install AlienoidMod form Magisk app or twrp

4. Reboot

5. Install ViPERFX and or other AlienoidMod module from Magisk app or twrp but if, then you have to keep a reboot gap between them.

6. Reboot.

That means you have to install freshly after a new test build comes. Please consider this boring kinda steps while this testing period. When the release build will come you don't have to do this necessarily.

Thanks you.
[Magisk] venomus001:
So here is what happened i flashed both zips thinking that it would work it work but it didn't. now, i can't uninstall ViperFx for some reason it just shows the module will be updated after reboot
[Magisk] tom.android:
Not working but old amf-test-A58.zip + Dolby_Atmos-r6.5-c.zip. is ok.
[Magisk] bluemeda:
How bout Android Oreo?
[Magisk] Rom:
So i can flash your module, reboot my phone and i will have all the ViperFX stuff ?
[Magisk] metaspook:
Not yet.. But on upcoming feature lineup..:good:

But you can test it n inform me what would happen cuz I already make the viperfx.apk supported for Oreo but couldn't test it.
[Magisk] metaspook:
Follow the instruction n inform me what is happened
[Magisk] metaspook:
If you can't remove the module from Magisk app then goto "/magisk" directory now delete the module folder here which you want to remove like for AlienoidMod is "amf" and for ViPERFX is "viperfx"

then Reboot
[Magisk] kieeps:
I also get prompted to install drivers every time i start the app.

Procedure:

Flashed amf-test-B05.zip in magisk manager.

Rebooted

Flashed viperfx-test-A05.zip in magisk manager.

Rebooted

I'll post some screeners, i tried what you suggested to the others with this problem and copied amf-services.sh to /magisk/.core/service.d with no luck.
[Magisk] Rom:
I must install Alienoid to get your module works ?
[Magisk] metaspook:
No need to place file /magisk/.core/service.d

They already get normally working now after latest test build whom I suggested to place file /magisk/.core/service.d

You better check here

/magisk/amf/system/etc

and

/magisk/amf/system/verdor/etc

if the audio files here modified with code for viperfx or not

I think problem is there...
[Magisk] metaspook:
Yup..
[Magisk] Rom:
But previous Magisk Module working without need to install any other framework..
[Magisk] kieeps:
Both those folders are empty for me :-O
[Magisk] lekcin18:
Flashed amf-test-B05.zip in magisk manager. Reboot. OK

Flashed viperfx-test-A05.zip in magisk manager. reboot

after reboot all modules are gone. :(
[Magisk] metaspook:
First remove amf and viperfx from magisk app the reboot then start the flashing sequence.
[Magisk] metaspook:
Read more on AlienoidMod thread n in future you can use multiple audio mod without confliction.. N also ViPERFX would have a backup option in condition of no AlienoidMod found... Bro as this is in testing stage give time all these framework and modules to be mature n test the new test builds....

If you found any fix patches or any idea feel free to share with me...
[Magisk] metaspook:
Yes.. as I told you. This shouldn't be happened but it is, the audio config files like audio_policy.conf, audio_effects.conf etc files should've pulled from

/system/etc to /magisk/amf/system/etc

and

/system/vendor/etc to /magisk/amf/system/vendor/etc

You look over if can n if found any fix inform me...
[Magisk] Som_esh:
It doesn't seem to work on magisk 14. It just doesn't. Need fix.
[Magisk] KaiStone:
[MENTION=6029298]metaspook[/MENTION] I don't know why but my Samsung A9 Pro (SM-A910F) is currently having this issue. Other modules installed well.
[Magisk] metaspook:
The the new test build "viperfx-test-C01.zip"

* lot of code improvements..

*Fixed driver installing issue..

*fixed some other issues...

Please install the latest AlienoidMod before try it...
[Magisk] metaspook:
Give me feedback after install the new test build and don't forget to install AlienoidMod before...
[Magisk] Huskerr:
I had a drivers installation issue with the previous build. Now it's gone, it's working

Thank you Dude !!
[Magisk] Rom:
I want to try your module but i have install V4A module before install amf-test-C01 :silly:

So i have successfully disable amf but i don't arrive to uninstall V4A module..

Have u an uninstaller zip please ?

After that i could make the good flash process.
[Magisk] trackloading:
I also had the driver issue, but now it's working for me as well on my HTC 10.

Thanks!
[Magisk] metaspook:
Remove AlienoidMod from Magisk app

reboot

Remove ViPERFX from Magisk app

reboot

Install AlienoidMod from Magisk app

reboot

Install ViPERFX from Magisk app

reboot
[Magisk] L.F.B.:
Thanks [MENTION=6029298]metaspook[/MENTION] for the latest c-01!

Now viperfx drivers flash automatcally!??
[Magisk] Rom:
Magisk Manager won't uninstall the V4A module, do u know where the maigks modules folders are located on Magisk v14 ?
[Magisk] endrju_master:
# [MENTION=5332893]Rom[/MENTION] in /magisk. Use the file explorer. I use mixplorer.

Wysłane z mojego MI 5 przy użyciu Tapatalka
[Magisk] Rom:
I have find the folder with ES thanks :good:
[Magisk] FlemishDroid:
I had no Magisk modules beside SafetyNet fix and Busybox so I dit the following:

Flashed Alienoidmod in twrp

Reboot

Flashed Viperfx-test-C01

Reboot

Alienoidmod was in Magisk manager but Viperfx not so I installed it through Magisk Download but after the reboot there was still no Viper app so I extracted the app from Viperfx-test-C01 and installed it.

When I open Viperfx app it didn't work so I enabled dev options and disabled SELinux enforcing and then it works for a while. I tried to add the starting script v4a.sh in service.d still no luck. What can I do to make it working? I think Viperfx-test_C01 is not installed properly (I tried it twice).

Thanks.
[Magisk] metaspook:
hmm... you could delete those folder from

/magisk/amf

and

/magisk/viperfx
[Magisk] Jerry SQ:
can you make Dolby Atmos module, sir [MENTION=6029298]metaspook[/MENTION] ???? your modules work perfectly with my LG V20, magisk 14.0
[Magisk] Rom:
Thanks u, i have successfully delete theses folders, cleanup maked :good:
[Magisk] dolfet15:
Works perfect on my mi3 with miui 9.

Enviado desde mi MI 3W mediante Tapatalk
[Magisk] zoneofSAM:
works perfectly on oneplus 3T running stable oxygenOS 4.1.7(7.1.1)
[Magisk] kieeps:
Nice work! Drivers loaded fine and im back on great sound :)
[Magisk] krea_h2:
very good job, thank you very much! tested in xiaomi redmi note 3 pro (kenzo), with room LineageOS 15 (android 8.0.0), kerner Agni pure v10.8 and running perfect.
[Magisk] metaspook:
may b in future...
[Magisk] Noru29:
Works very well on Xiaomi Redmi 3S.... but the skin really hurt my eyes... I prefer the sobriety of the official, but it works, and that's a great step ! Thanks !
[Magisk] KaiStone:
Still does not work on Mi 5s Plus with RR 5.8.4

Driver required :D it's the same problem like previous build.
[Magisk] L.F.B.:
The latest magisk beta 14.1 broked viperfx ... Its keep asking for reistall drivers...

Back to last magisk stable 14.0 and evrything works again...
[Magisk] Rom:
Its seem to be sure that this type of module willn't work on the new Magisk version, modules who simple replace files will continue to works without needed modifications, but for modules that execute some commands lines at startup, additionaly to that an module template update, you can be sure that the module willn't works propeply.
[Magisk] L.F.B.:
New hotfix magisk 14.2 beta.

Vipefx module working fine now! ?

It seems a magisk problem that broke 99% off all modules.
[Magisk] tfactor:
Hi!

Thanks for your work.

I'm wondering what kind of a viber driver is used?

'Normal', not a high quality one?

Thz in advance
[Magisk] metaspook:
There is no variant of sound quality driver in base Viper4android 2.5.0.5 so ViPERFX mod also don't have.
[Magisk] metaspook:
If then wait for the next release and instruction when I'll release next version plz kindly follow the new instructions also...
[Magisk] metaspook:
You have to make yourself used to on AMOLED UI cuz AMOLED/OLED are the future of displays.
[Magisk] Noru29:
AMOLED is just a technology not a UI.

There are so many very good UI for AMOLED not so flashy and so 80s like black ones who also saved battery consumption.
[Magisk] metaspook:
Actually mentioned AMOLED friendly UI..
[Magisk] Noru29:
Yes, and that's a false problem. Your work is perfect. The drivers is functionnal, sound could be changed dynamically when player is open. That's great.

I also tried the new version on ViperFX on Magisk Store... doesn't work. I came back to your ViPerFX version with pleasure.
[Magisk] ChARCOOL:
I was using your module successfully in my Samsung Galaxy A5 2017, but after I updated it to A520FXXU2BQIE it's not working anymore.

It wants from you to install the driver when i press yes it says failed cuz busybox is not installed.

But my busybox is installed and it's working i am using magisk busybox
[Magisk] Driv:
I don't understand why I have to install Magisk v14 and AlienoidMod test-C01?
[Magisk] ebeldamasta:
Works perfectly on Mi4LTE - MIUI 9 (xiaomi.eu Beta)

====

Even with previously installed Dolby Atmos from somewhere in XDA
[Magisk] seeker07:
the best v4a module i have tested

on LG G2 7.1.2
[Magisk] partcyborg:
What happened to this? Is it still a thing? Is magisk a hard requirement or can those of us with locked bootloaders use it with supersu system root?
[Magisk] Charli3M:
S5 g900v

It works on S 5 g 9OOV