So as some of you know, the CM7 pre-beta has limited the max number of fingers registered on the screen to 2.
So here is how to change it to the max of 10 (really its just 8 )
1. Download the Multi-touch.zip
2. Un-zip it
3. Copy both folders to your internal or external sd, whichever u can access.
4. Open up root explorer
5. Go to /etc/touchpad/
6. Mount R/W (On top)
7. Open folder 21 and rename touchpad.cfg to touchpad.cfg.bak
8. Do the same in folder 22
9. Go to your internal/external sdcard folder open up your 21 folder and long-press on touchpad.cfg and select copy (or move, your choice)
10. Go to /etc/touchpad/21 and paste it there
11. Change Permissions to: (If you don't your touchscreen will be backwards and it gets annoying.
Code:
Owner: [X] [X] [_]
Group: [X] [_] [_]
Others: [X] [_] [_]
12. Repeat Steps 9, 10, 11 for folder 22 (except its in folder 22 and copy/move it to /etc/touchpad/22 just for those noobs who didn't know)
12. Reboot
I tried just editing the cm7 touchpad.cfg files but it just changed max limit form 2 to 1 (Fail.) so this is the only thing that worked for me.
Thanks to michael0619 for this great find.
and to Ronaldo_9 who made it work for 2.3.4 in a CWM form ( And hopefully for CM7, hehe )
cm7 pre-beta work now supports 5 fingers. I do not know if this is in the current pre-beta2 release but you should all see it soon.
I flashed the multitouch.zip in cwm several weeks ago to support >2 multi touch. Why all of the unzipping and instruction? Download, flash in cwm. That's all that's is needed to be done.
BravoMotorola said:
I flashed the multitouch.zip in cwm several weeks ago to support >2 multi touch. Why all of the unzipping and instruction? Download, flash in cwm. That's all that's is needed to be done.
Click to expand...
Click to collapse
Agree that's all I use
Sent from my MB860 using XDA Premium App
stevendeb25 said:
Agree that's all I use
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Oh, and to make clear it is actually the 10_point_touch_2.3.4.zip that I flashed. I'm not sure where I got it, but I copied the dl link to wherever on these threads it was from.
I tried to apply this with the stock att build, deodexed and my touchscreen is backwards, the 21 & 22 folder have the correct permissions
Owner: [X] [X] [_]
Group: [X] [_] [_]
Others: [X] [_] [_]
but what is supposed to be for the 20 folder?
is it supposed to be this?
owner [_] [_] [_]
group [X] [X] [X]
others [X] [_] [X]
and what about the touchpad folder itself? My touchpad folder had all the permissions set for owner,group, and others
princeandy63 said:
I tried to apply this with the stock att build, deodexed and my touchscreen is backwards, the 21 & 22 folder have the correct permissions
Owner: [X] [X] [_]
Group: [X] [_] [_]
Others: [X] [_] [_]
but what is supposed to be for the 20 folder?
is it supposed to be this?
owner [_] [_] [_]
group [X] [X] [X]
others [X] [_] [X]
and what about the touchpad folder itself? My touchpad folder had all the permissions set for owner,group, and others
Click to expand...
Click to collapse
Flash the file I put in my post above. Was that post not clear enough or did you not read it?
BravoMotorola said:
Flash the file I put in my post above. Was that post not clear enough or did you not read it?
Click to expand...
Click to collapse
I did read it and it still ended up backwards, anyways I'll flash the file again and post the results
Edit: its still backwards and I wiped the dalvik cache
princeandy63 said:
I did read it and it still ended up backwards, anyways I'll flash the file again and post the results
Edit: its still backwards and I wiped the dalvik cache
Click to expand...
Click to collapse
Woah, that's really strange. Did you move the files over and then flash it? Or did you just flash the file first thing?
BravoMotorola said:
Woah, that's really strange. Did you move the files over and then flash it? Or did you just flash the file first thing?
Click to expand...
Click to collapse
Moved over first, permissions > rebooted > backwards then flashed it, still backwards.
EDIT: I fixed it, I messed around with the permissions and set the 21 and 22 folder to
owner [_] [_] [_]
group [X] [X] [X]
others [X] [_] [X]
and then flashed the zip file and that fixed it
Thanks for trying to help
princeandy63 said:
Moved over first, permissions > rebooted > backwards then flashed it, still backwards.
EDIT: I fixed it, I messed around with the permissions and set the 21 and 22 folder to
owner [_] [_] [_]
group [X] [X] [X]
others [X] [_] [X]
and then flashed the zip file and that fixed it
Thanks for trying to help
Click to expand...
Click to collapse
Glad you fixed it. Although I think if moving the files over form the op and then flashing the zip is what (somehow) messed you up.
Related
Hi people,
first, I don't speak english very well.
I will show you how to change the bootanimation on froyo 2.2 or gingerbread 2.3.X.
What you need?
Root
Stock ROM
Root Explorer
bootanimation.zip is the set of several images that formed a "video" at start of your device.
bootanimation.zip: within this file can contain two folders:
part0 (first part of the animation)
part1 (second part of the animation)
Note: Some have only the folder bootanimation part0
And a text file called:
"Desc"
Within this file there are some parameters:
320 480 15 p p 1 0 0 0 part0 part1
Subtitles:
Red: Size of the picture, regardless of the size that it is within the file "bootanimation.zip" the size of it on the screen of your device will be determined in the field, with 320 width and 480 height. In Galaxy Mini you will use 240x320.
Green: 15 is the time in which images appear, the faster that number, the faster the "video" boot.
Blue: It means how many times the animation will appear in the folder, ie, p 1 0 part0, the animation of a folder will appear as 0.
Purple: The same thing the Blue, but in a folder, ie, the end of the animation.
3 - Understand how to create a bootanimation.zip
1 - you have the image in jpg or png named as you want as long as the end of each name finds the numbers in sequence. EX: 000, 001, 002, 003 ...
2 - Compress images using WinRAR like this:
compct
Filename: bootanimation.zip
File Format: ZIP
Method of storage: Store
4 - Okay, now having bootanimation.zip, copy to SD;
5 - Open Root Explorer and navigate to the directory "system / bin
6 - Look for the "samsungani" or "samsungloop", press and hold over the file, and select "MOVE";
7 - Browse to the folder "sdcard" and tap "PASTE"
Warning: If you have problems with
"Warning: can not've moved because the file system is read-only"
Press the right corner of Root Explorer
"Mount R / W" to be "Mount R / O!
8 - Back to the folder "system / bin" and browse to the "bootanimation"; - Navigate to the folder "sdcard" and tap "PASTE"
9 - Rename the file "bootanimation" to "samsungani" or "samsungloop" (depending on the file that you moved to SD in step 6)
10 - Now navigate to the "sdcard" and copy the bootanimation.zip;
11 - Navigate to the folder "system / media" and paste the bootanimation.zip here.
12 - rename the 2 files with extension. "MGQ" (removing the "g" at the end);
Reboot and enjoy!
I hope you like it!
thankz man!
is this fully working,cause i tried alot of tutorials regarding changing boot animation in stock rom,im using XWKTN 2.3.6,rooted..i have backups of samsungani and bootanimation,the last tutorial i did was.changing bootanimation file to samsungani and delete the samsungani in system/bin and replace bootanimation in system/media..i have nothing to replace in system media,ive only see bootsamsungloop.qmg and samsungloop.qmg?i will just rename that qmg to qm?even though i have no original bootanimation ..just palce my downloaded bootanimation in system/media?..i usually ended up in start up bootanimation,its just stuck there in previous tutorial i follwed.so i have to reflash again..hehehe
Thanks
zarpel said:
Hi people,
first, I don't speak english very well.
I will show you how to change the bootanimation on froyo 2.2 or gingerbread 2.3.X.
What you need?
Root
Stock ROM
Root Explorer
bootanimation.zip is the set of several images that formed a "video" at start of your device.
bootanimation.zip: within this file can contain two folders:
part0 (first part of the animation)
part1 (second part of the animation)
Note: Some have only the folder bootanimation part0
And a text file called:
"Desc"
Within this file there are some parameters:
320 480 15 p p 1 0 0 0 part0 part1
Subtitles:
Red: Size of the picture, regardless of the size that it is within the file "bootanimation.zip" the size of it on the screen of your device will be determined in the field, with 320 width and 480 height. In Galaxy Mini you will use 240x320.
Green: 15 is the time in which images appear, the faster that number, the faster the "video" boot.
Blue: It means how many times the animation will appear in the folder, ie, p 1 0 part0, the animation of a folder will appear as 0.
Purple: The same thing the Blue, but in a folder, ie, the end of the animation.
3 - Understand how to create a bootanimation.zip
1 - you have the image in jpg or png named as you want as long as the end of each name finds the numbers in sequence. EX: 000, 001, 002, 003 ...
2 - Compress images using WinRAR like this:
compct
Filename: bootanimation.zip
File Format: ZIP
Method of storage: Store
4 - Okay, now having bootanimation.zip, copy to SD;
5 - Open Root Explorer and navigate to the directory "system / bin
6 - Look for the "samsungani" or "samsungloop", press and hold over the file, and select "MOVE";
7 - Browse to the folder "sdcard" and tap "PASTE"
Warning: If you have problems with
"Warning: can not've moved because the file system is read-only"
Press the right corner of Root Explorer
"Mount R / W" to be "Mount R / O!
8 - Back to the folder "system / bin" and browse to the "bootanimation"; - Navigate to the folder "sdcard" and tap "PASTE"
9 - Rename the file "bootanimation" to "samsungani" or "samsungloop" (depending on the file that you moved to SD in step 6)
10 - Now navigate to the "sdcard" and copy the bootanimation.zip;
11 - Navigate to the folder "system / media" and paste the bootanimation.zip here.
12 - rename the 2 files with extension. "MGQ" (removing the "g" at the end);
Reboot and enjoy!
I hope you like it!
Click to expand...
Click to collapse
Thanks
---------- Post added at 08:56 PM ---------- Previous post was at 08:54 PM ----------
Is the procedure same on custom rom
If you are rooted then ROM toolbox would work fine
Sent from my GT-S5570 using XDA
Thanks! it works for my galaxy mini
Great tuto man, thanks:good:
It's great!... However It's long so I Flash cumstom rom and I have a easier way to change boot animation and the performance of custom rom, too
Sent from my GT-S5570 using xda
Problem
zarpel said:
Hi people,
first, I don't speak english very well.
I will show you how to change the bootanimation on froyo 2.2 or gingerbread 2.3.X.
What you need?
Root
Stock ROM
Root Explorer
bootanimation.zip is the set of several images that formed a "video" at start of your device.
bootanimation.zip: within this file can contain two folders:
part0 (first part of the animation)
part1 (second part of the animation)
Note: Some have only the folder bootanimation part0
And a text file called:
"Desc"
Within this file there are some parameters:
320 480 15 p p 1 0 0 0 part0 part1
Subtitles:
Red: Size of the picture, regardless of the size that it is within the file "bootanimation.zip" the size of it on the screen of your device will be determined in the field, with 320 width and 480 height. In Galaxy Mini you will use 240x320.
Green: 15 is the time in which images appear, the faster that number, the faster the "video" boot.
Blue: It means how many times the animation will appear in the folder, ie, p 1 0 part0, the animation of a folder will appear as 0.
Purple: The same thing the Blue, but in a folder, ie, the end of the animation.
3 - Understand how to create a bootanimation.zip
1 - you have the image in jpg or png named as you want as long as the end of each name finds the numbers in sequence. EX: 000, 001, 002, 003 ...
2 - Compress images using WinRAR like this:
compct
Filename: bootanimation.zip
File Format: ZIP
Method of storage: Store
4 - Okay, now having bootanimation.zip, copy to SD;
5 - Open Root Explorer and navigate to the directory "system / bin
6 - Look for the "samsungani" or "samsungloop", press and hold over the file, and select "MOVE";
7 - Browse to the folder "sdcard" and tap "PASTE"
Warning: If you have problems with
"Warning: can not've moved because the file system is read-only"
Press the right corner of Root Explorer
"Mount R / W" to be "Mount R / O!
8 - Back to the folder "system / bin" and browse to the "bootanimation"; - Navigate to the folder "sdcard" and tap "PASTE"
9 - Rename the file "bootanimation" to "samsungani" or "samsungloop" (depending on the file that you moved to SD in step 6)
10 - Now navigate to the "sdcard" and copy the bootanimation.zip;
11 - Navigate to the folder "system / media" and paste the bootanimation.zip here.
12 - rename the 2 files with extension. "MGQ" (removing the "g" at the end);
Reboot and enjoy!
I hope you like it!
Click to expand...
Click to collapse
Which 2 files do we have to rename??
AW: [TUTORIAL] How to change bootanimation on stock ROM and some to download
smashingeeks said:
If you are rooted then ROM toolbox would work fine
Sent from my GT-S5570 using XDA
Click to expand...
Click to collapse
I used 'Bootanimation changer' or something like that from ROM toolbox but it didn't work for my mini?!
Sent from my GT-S5570 using xda app-developers app
Good tutorial thanx...:good:
another way to change Bootanimation or font
Hi,
Just sharing, I'm using application from GPlay naming https://play.google.com/store/apps/...sImNvbS5qcnVtbXkubGliZXJ0eS50b29sYm94cHJvIl0.
you can download a ton of bootanimation and also you can make the bootanimation randomize.
Free version on attached.. :fingers-crossed:
My Device:
SGM with TouchWiz V5 ROM by A_U
Hit THANK'S if useful.
thanks :good:
Need fast response
My phone rooted, stock room, locked bl, gingerbread, it's bootloop, i rename 2 file "bootsamsung" & other i forget, from extension "qgm" to "qg", after i reboot it stuck in boot animation.
How to repair it whitout flashing?
Hello guys!
Today I was watching the tutorial from curser4eva.com to get AirView on the N7000. I wasn't successful and I get a little frustrated.
I don't really know why but I changed the permissions of the etc/permissions directory to: rw--r--r-- (0644) using Solid Explorer, and then restart my phone, since then I'm not able to access to my interal or external sdcard and also cannot access to a lot of apps.
Here is what I did exactly:
Using Solid Explorer, I copied the com.sec.feature.hovering_ui.xml file from my sdcard and tried to paste it in the etc/permissions directory but it said that there wasn't enough free space (I got the same message few days ago when I've tried to paste and apk. into the system/app directory).
And after this, I change the etc/permissions folder permissions to: rw--r--r-- (0644) using Solid Explorer, and then restart my phone, and after everything loads, a bunch messages of Force Closed services (dropobox, youtube, gapps services, for example) Pops up.
Then I open Solid Explorer to try to restore the permissions, and immediately pops up this message: Error - Cannot browse to "/storage/sdcard0"- An unknown error occured.
Then I jumped to the system root and accessed to etc/permissions and restored the permissions to: rwxr--xr--x-- (0755) and restart my phone, but nothing changes.
Finally in CWM recovery I flashed again the Jelly Bean eybee ROM to try to fix it, without any good result.
And right now I don't know what else could I do, because, in case you haven't noticed yet, I'm a freaking noob :crying:
Information could be useful:
I'm running Android 4.1.1
Baseband: N7000XXLS1
Build number JRO03C.N7000XXLS2
I'm also able to access to the Sdcard with Root Browser, and noticed that all files dates changed to: Dec 31, 1969 06:00:00, and all have the size of: 0.00B
Thanks in advance for your advices!!!..... And an apology if I'm wasting your time.
- José González
Reflash the room you were on when you changed the permission...
If that doesn't solve then make a titanium backup and do a factory reset, then restore apps
May be you want to go to stock rom using odin again and the come back to this rom
I'll take your advices
Thanks for your replys.
I will do your advices tonight.
Also, can you tell me which are your permissions and ownership of the storage and sdcard folders? Mine are:
Storage: r--xr--x-- (0550) , owner: 1000 system, group: 0 root.
Sdcard0: rwx--rwx--rx-- (0775), Owner: 1000 system, Group: 0 root
I'll wait fot your answer.
jgmoran said:
Thanks for your replys.
I will do your advices tonight.
Also, can you tell me which are your permissions and ownership of the storage and sdcard folders? Mine are:
Storage: r--xr--x-- (0550) , owner: 1000 system, group: 0 root.
Sdcard0: rwx--rwx--rx-- (0775), Owner: 1000 system, Group: 0 root
I'll wait fot your answer.
Click to expand...
Click to collapse
I copied the "com.sec.feature.hovering_ui.xml" and i didnt face any problem
Actually you are required to change the permissions of xml file..not for the etc/permissions folder
And permissions of storage : r-xr-x--- ,owner: system ,group:1028: 1028
sdcard : rwxrwxrwx, owner: 0:root ,group: 0:root
Solved!
Thanks guys!
I followed Jamal Ahmed recomendation. I did a factory reset from recovery and then reflash the ROM, and that's it!. And also I was able finally to copy de .xml to the permissions folder .
XDA Developers For the Win!!!
-José González
That's true! Perfectly working on my stock rooted ICS for 24h+!
This mod is for test porpoises only. Although I'm using it with success right now, I can not guarantee you that it will work, so:
I'm just reproducing the method I used to make it works on my own device. I have no intentions of being a developer, I don't wanna any donations and I'm not encouraging you to try this, and I'm warning you this can potentially brick your device. So, if even knowing this you assume these risks, be warned that I'm not responsible for any problem you could have trying to do this. In short: do it by yourself!
It works on my stock ICS with rooted system.img, and I did as following:
- Backup your internal SDcard, because if anything goes wrong, you will have to use smartflash/nvflash to recover your phone, and your internal sdcard can be formated if you need to reinstall your system.
- Download ES File explorer from market (of course this is for not so advanced user, since they don't need this instructions)
- Enable all root options on it (menu, settings, root settings, check all the three first options)
- Click on the zip you downloaded from here
- Unpack the system folder from the zip attached to your sdcard
(on ES File explorer, click on "select" button, than on "system" folder, than on "extract" button)
- Go to /data
- Create a new dir called ICS
- Move the extracted "system" folder to /data/ICS/
- Enter /data/ICS/system
- There should be 4 folders: addon.d, app, lib and vendor
- Enter addon.p, long-click on 71-gapps-faceunlock.sh, click properties
- Change its properties to owner:read, write and execute; group: read, execute; others: read, execute
- Go back to /data/ICS/system, enter app folder
- long click on FaceLock.apk and change its permissions to owner:read, write; group: read; others: read
- Go back to /data/ICS/system, enter lib folder
- Change the permissions as you did for FaceLock.apk in all the 9 files, one by one, inside this folder
- Go back to /data/ICS/system
- Click on select, than select the four folders, than on CUT
- Go to /system (note: now it's /system, not /data/ICS/system anymore)
- Click on "Paste", confirm the changes on all the files/folders
- Reboot
Well, at this point, if you are a lucky guy and didn't get a 90% of a bootloop chance, you should be able to change your lockscreen to facelock.
I have no idea if this will work on tonyp/harsh's stock ICS flashable zip, because I don't have it to test. It should work since they are almost the same rom, however they have deleted a lot of LGs stuff to make the zip flashable on GB partition layout, so you can try it (the zip itself should be flashable on CWM), however:
- DO A NANDROID BACKUP firstly and
- YOU WILL NEED at least 39MB free on /system to do it! I have no idea if it's even possible to get this on GB partition layout
Link: http://db.tt/daf7KCmD
If you did this and it worked, press thanks and let us know.
reserved
reserved
I will try but it look too hard
Enviado desde mi LG-P990 usando Tapatalk 2
It is working thanks.
how do you unlock youre phone in the dark on lights off???
You just don't
It's really great that you write this to help others, but there is no need in such long instruction. Why just not to say easier:
1. Download lates ics gapps: http://goo.im/gapps/gapps-ics-20120429-signed.zip
2. Copy-past folders "optional/app" and "optional/vendor" into device system folder. (There is no need in addon.d on a stock rom)
3. Copy-past optional/noneon/lib/libfacelock_jni.so into system/lib folder. (There is no need to replace other libs)
4. Change permissions for system/app/FaceLock.apk and system/lib/libfacelock_jni.so to 644 (-rw-r--r--) (just look how it is set for other files in these folders).
5. Reboot.
I tried earlier to extract the face unlock files from gapps, but it didn't work for me... This way it works perfectly, thanks!
working thanks.........
mivv said:
how do you unlock youre phone in the dark on lights off???
Click to expand...
Click to collapse
Facelock always have a secondary method of PIN number. If facelock fails you can enter PIN number (numeric code) and it unlocks,
Has anyone tried this on CM10... I guess I will be the first then would be nice a .zip to flash
louiscypherbr said:
That's true! Perfectly working on my stock rooted ICS for 24h+!
This mod is for test porpoises only. Although I'm using it with success right now, I can not guarantee you that it will work, so:
I'm just reproducing the method I used to make it works on my own device. I have no intentions of being a developer, I don't wanna any donations and I'm not encouraging you to try this, and I'm warning you this can potentially brick your device. So, if even knowing this you assume these risks, be warned that I'm not responsible for any problem you could have trying to do this. In short: do it by yourself!
It works on my stock ICS with rooted system.img, and I did as following:
- Backup your internal SDcard, because if anything goes wrong, you will have to use smartflash/nvflash to recover your phone, and your internal sdcard can be formated if you need to reinstall your system.
- Download ES File explorer from market (of course this is for not so advanced user, since they don't need this instructions)
- Enable all root options on it (menu, settings, root settings, check all the three first options)
- Click on the zip you downloaded from here
- Unpack the system folder from the zip attached to your sdcard
(on ES File explorer, click on "select" button, than on "system" folder, than on "extract" button)
- Go to /data
- Create a new dir called ICS
- Move the extracted "system" folder to /data/ICS/
- Enter /data/ICS/system
- There should be 4 folders: addon.d, app, lib and vendor
- Enter addon.p, long-click on 71-gapps-faceunlock.sh, click properties
- Change its properties to owner:read, write and execute; group: read, execute; others: read, execute
- Go back to /data/ICS/system, enter app folder
- long click on FaceLock.apk and change its permissions to owner:read, write; group: read; others: read
- Go back to /data/ICS/system, enter lib folder
- Change the permissions as you did for FaceLock.apk in all the 9 files, one by one, inside this folder
- Go back to /data/ICS/system
- Click on select, than select the four folders, than on CUT
- Go to /system (note: now it's /system, not /data/ICS/system anymore)
- Click on "Paste", confirm the changes on all the files/folders
- Reboot
Well, at this point, if you are a lucky guy and didn't get a 90% of a bootloop chance, you should be able to change your lockscreen to facelock.
I have no idea if this will work on tonyp/harsh's stock ICS flashable zip, because I don't have it to test. It should work since they are almost the same rom, however they have deleted a lot of LGs stuff to make the zip flashable on GB partition layout, so you can try it (the zip itself should be flashable on CWM), however:
- DO A NANDROID BACKUP firstly and
- YOU WILL NEED at least 39MB free on /system to do it! I have no idea if it's even possible to get this on GB partition layout
Link: http://db.tt/daf7KCmD
If you did this and it worked, press thanks and let us know.
Click to expand...
Click to collapse
From your description it seems that you are more elaborative person so i need on help?
Stefen has give some instruction to root V28G Rom using NVflash but i am unable to find the meaning of those commands available in NVFlash
can u peovide me step by step along with commands to save system partition and all..............
i've just flash it on my 28g (samrtflash install) and work like a charme! thx
I get an error about the end, I can't move "VENDOR" folder into system, says it cannot move vendor folder.... any idea?
after rebooting I tried faceunlock, it was there but unable to initiate, then i tried again to move the VENDOR folder, i could now, after a reeboot still doesnt work
Anyone willing to test it in CM10?
Face unlock works
It's working on 30a version, did exactly the same way just copied the files from the folder to another. Will try in the morning if it can read the face easily as its night at my place now. Thanks
Hello People,
Today i am going to show you how to extract bootanimation.zip from apk. So lets begin,
You would want to apply custom boot animation like the CM theme engine but as the animations in cyanogenmod are in apk format, you cannnot apply them on other Roms. But now don't worry now i have got a way to apply them to non-cyanogenmod devices.
Requirements :
Boot animation apk. I will use the one given below.
File explorer (I would use Es file explorer)
Steps :
Navigate to the downloaded apk and long press it.
Under the 3 dot menu select extract to and extract the apk.*
Now you will find the bootanimatio.zip file in assets folder.*
Now*go to the root folder and navigate through system>media.**Once there locate your current bootanimation.zip file
Long-press your current bootanimation.zip file, and click copy, as we'll want to have a backup just in case. Paste it wherever convenient for you OR simply change the extension from .zip to .bak
Once your new bootanimation.zip has been selected for moving, navigate back to system > media and paste it there. You'll have to overwrite your current animation zip, but that's fine since you have a backup in case something goes wrong. Go for it.
For many of you, the previous step will be the last step. But, if for any reason you're still stuck with you old animation, you can try aligning the permissions of your newly-copied bootanimation.zip file with the permissions in the system/media folder. In our case, those were rw-r-r. Just long-press your new bootanimation.zip file and click Permissions and change them until they fit. The logic behind these abbreviations goes like this: Owner - Group - Other. Read for 'r', Write for 'w', and Execute for 'x'. Save the changes and restart...
Done, Show this awesome boot animation to your friends.*
Note :
You are choosing to make these modifications, and dont point the finger at me for messing up your device.
Watchdogs bootanimation download :
Mega - http://goo.gl/KGMS9i
Drive - http://goo.gl/FfvY8a
Hit the thanks button if you found this helpful :good:
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 on our OnePlus 10 pro with no success.
Below I'll start a list of pledgers who are willing to pay the bounty when/if a fix is found. I'll add to the list as other pledgers come forward. Any pledge amount helps.
•ecera -$50
•Aldonski - $10
On a side note, I'll be willing to test any fixes that are thrown my way. I'm also ready to provide any files or logs that are requested. Also, if you guys/gals want to tag some members that may be willing to take on this task please do so. Thanks.
@shadowstep @dorimanx @zgfg @vczilla @Juniiim
Hope you guys don't mind me tagging you. From posts I have read of yours, you guys know your stuff. Or maybe you can recommend someone who will be interested in the bounty.
So I'm guessing a little basic info would be helpful. The OnePlus 10 pro is running oos12, the normal post-fs-data.sh fix where vendor/etc and odm/etc "audio_effects.xml" is binded doesn't work(as expected since the file doesn't exist under vendor/etc on this device.) I'll attach a photo where audio_effects.xml can be found on this device. Another thing to note is that the viper4android.zip by @shadowstep actually adds audio_effects.xml &.conf to vendor/etc. But trying to bind this newly created audio_effects.xml to the one in odm/etc doesn't make any changes to the one in odm. I'm also unable to launch the viper4android app using his version, but installing the apk again allows me to open the app. I'm just not sure if that affects anything as far as the functionality of his module. I could though bind the audio_effects.xml located in vendor/etc/audio/sku_cape to the odm/etc one, but driver loop persists. I'm out of ideas I've literally tried every module(aml, jdsp, ainur, acp, v4a from the magisk repo, other versions of v4a zips in different orders/ combinations. Nothing has worked so far.
Aldo - $10
great ideea mate
try this:
remove all sound mods you have added, including the module from magisk and the viper app!
reboot!
Install attached Audio-Modification-Library_v4_0-OS12-op10
reboot!
install com.pittvandewitt.viperfx_2.7.2.1-2721.apk
open the viper app, and click install drivers.
phone auto reboot.
copy attached post-fs-data.sh to /data/adb/modules/ViPER4AndroidFX/ (use adb or rooted file manager)
REBOOT, do not open the app!!!!
now if we hit the FIX, if you will open the app it's should not ask to install drivers.
if it's stop asking, check the state, if it's not NORMAL then tick the Legacy Mode, and check state.
should be Status Normal.
I hope this will work for you.
ecera said:
So I'm guessing a little basic info would be helpful. The OnePlus 10 pro is running oos12, the normal post-fs-data.sh fix where vendor/etc and odm/etc "audio_effects.xml" is binded doesn't work(as expected since the file doesn't exist under vendor/etc on this device.) I'll attach a photo where audio_effects.xml can be found on this device. Another thing to note is that the viper4android.zip by @shadowstep actually adds audio_effects.xml &.conf to vendor/etc. But trying to bind this newly created audio_effects.xml to the one in odm/etc doesn't make any changes to the one in odm. I'm also unable to launch the viper4android app using his version, but installing the apk again allows me to open the app. I'm just not sure if that affects anything as far as the functionality of his module. I could though bind the audio_effects.xml located in vendor/etc/audio/sku_cape to the odm/etc one, but driver loop persists. I'm out of ideas I've literally tried every module(aml, jdsp, ainur, acp, v4a from the magisk repo, other versions of v4a zips in different orders/ combinations. Nothing has worked so far.
Click to expand...
Click to collapse
I could give you suggestions/hints based on how I made it to work on my phone - but it was Xiaomi with stock A11, not your OnePlus 10 with oos12:
https://forum.xda-developers.com/t/...ndroid-10-11-12-devices.4213647/post-86870983
Anyway, before we start, please disable ALL audio moudules (any V4A, AML, etc you may have) and REBOOT
And then please respond/confirm the following:
1) Check, does your system show the same content (one should be mounted to another) for /system/vendor/etc and vendor/etc ?
You can use a root explorer like MiXPlorer or you cah check with ls command in terminal window, and when you boot with the Magisk root.
I.e, do not check from a custom recovery (mounting points must be properly in place when system/Android + Magisk are booted)
2) Check, does your system show the same content (one should be mounted to another) for /system/odm/etc and /odm/etc ?
3) Do you have audio_effects.xml in the following folders (with /vendor = /system/vendor and /odm = /system/odm as mentioned above):
/odm/etc
/vendor/etc/
/vendor/etc/audio/sku_cape
/vendor/etc/audio/sku_diwali
/vendor/etc/audio/sku_taro
4) Do you also have audio_effects.conf in the same folders as listed in 3) - if not, list in which of the folders you do have the conf file
For 1) and 2), we need to be sure if standard montings (as needed for V4A to mount files and work on your system).
For 3) and 4), we need to be sure if you originally (without the intervention from any audio module like the previous installation of V4A or AML, etc)
do have the audio_effects.xml and audio_effects.conf files in all those folders, or in which of them exactly
dorimanx said:
try this:
remove all sound mods you have added, including the module from magisk and the viper app!
reboot!
Install attached Audio-Modification-Library_v4_0-OS12-op10
reboot!
install com.pittvandewitt.viperfx_2.7.2.1-2721.apk
open the viper app, and click install drivers.
phone auto reboot.
copy attached post-fs-data.sh to /data/adb/modules/ViPER4AndroidFX/ (use adb or rooted file manager)
REBOOT, do not open the app!!!!
now if we hit the FIX, if you will open the app it's should not ask to install drivers.
if it's stop asking, check the state, if it's not NORMAL then tick the Legacy Mode, and check state.
should be Status Normal.
I hope this will work for you.
Click to expand...
Click to collapse
Thank you for responding! I'm going to test out your methods first, I will report back.
Edit: so I tried the method you suggested and unfortunately driver loop persists. So what I noticed is that audio_effects.xml in all directories on this phone remain untouched. They remain "stock". Also, under /data/adb/modules/aml or /Viper4Androidfx in the system folder in both directories subfolders were created, but remain empty. Not sure if there's any info you would like to take from the phone that I could get for you? I took a few screenshots, not sure if that'll help. I started clean with no mods and I took these after attempting the fix.
zgfg said:
I could give you suggestions/hints based on how I made it to work on my phone - but it was Xiaomi with stock A11, not your OnePlus 10 with oos12:
https://forum.xda-developers.com/t/...ndroid-10-11-12-devices.4213647/post-86870983
Anyway, before we start, please disable ALL audio moudules (any V4A, AML, etc you may have) and REBOOT
And then please respond/confirm the following:
1) Check, does your system show the same content (one should be mounted to another) for /system/vendor/etc and vendor/etc ?
You can use a root explorer like MiXPlorer or you cah check with ls command in terminal window, and when you boot with the Magisk root.
I.e, do not check from a custom recovery (mounting points must be properly in place when system/Android + Magisk are booted)
2) Check, does your system show the same content (one should be mounted to another) for /system/odm/etc and /odm/etc ?
3) Do you have audio_effects.xml in the following folders (with /vendor = /system/vendor and /odm = /system/odm as mentioned above):
/odm/etc
/vendor/etc/
/vendor/etc/audio/sku_cape
/vendor/etc/audio/sku_diwali
/vendor/etc/audio/sku_taro
4) Do you also have audio_effects.conf in the same folders as listed in 3) - if not, list in which of the folders you do have the conf file
For 1) and 2), we need to be sure if standard montings (as needed for V4A to mount files and work on your system).
For 3) and 4), we need to be sure if you originally (without the intervention from any audio module like the previous installation of V4A or AML, etc)
do have the audio_effects.xml and audio_effects.conf files in all those folders, or in which of them exactly
Click to expand...
Click to collapse
1) Ok, so /system/vendor/etc and /vendor/etc does show the same content. I'd note that audio_effects.xml and .conf are both missing in this directory from an untouched unmodified standpoint though.
2) system/odm/etc is non-existent on this phone. Odm/etc is there though. There is /vendor/odm/etc and shows the same content as odm/etc.
3) audio_effects.xml exists in the following locations.
- /odm/etc
- /vendor/etc/audio/sku_cape
- /vendor/etc/audio/sku_diwali
- /vendor/etc/audio/sku_taro
It is absent in
- /vendor/etc
4) audio_effects.conf exists under
- /vendor/etc/audio/sku_cape
- /vendor/etc/audio/sku_diwali
- /vendor/etc/audio/sku_taro
- /system/etc or /etc
It is absent from
- /odm/etc
- /vendor/etc
Again thanks so much for giving this a shot.
ecera said:
1) Ok, so /system/vendor/etc and /vendor/etc does show the same content. I'd note that audio_effects.xml and .conf are both missing in this directory from an untouched unmodified standpoint though.
2) system/odm/etc is non-existent on this phone. Odm/etc is there though. There is /vendor/odm/etc and shows the same content as odm/etc.
3) audio_effects.xml exists in the following locations.
- /odm/etc
- /vendor/etc/audio/sku_cape
- /vendor/etc/audio/sku_diwali
- /vendor/etc/audio/sku_taro
It is absent in
- /vendor/etc
4) audio_effects.conf exists under
- /vendor/etc/audio/sku_cape
- /vendor/etc/audio/sku_diwali
- /vendor/etc/audio/sku_taro
- /system/etc or /etc
It is absent from
- /odm/etc
- /vendor/etc
Again thanks so much for giving this a shot.
Click to expand...
Click to collapse
Ok, thanks
Then shortly based on 1) and 2):
/odm/etc
/vendor/odm/etc
/system/vendor/odm/etc
are all pointing to the same?
ecera said:
1) Ok, so /system/vendor/etc and /vendor/etc does show the same content. I'd note that audio_effects.xml and .conf are both missing in this directory from an untouched unmodified standpoint though.
2) system/odm/etc is non-existent on this phone. Odm/etc is there though. There is /vendor/odm/etc and shows the same content as odm/etc.
3) audio_effects.xml exists in the following locations.
- /odm/etc
- /vendor/etc/audio/sku_cape
- /vendor/etc/audio/sku_diwali
- /vendor/etc/audio/sku_taro
It is absent in
- /vendor/etc
4) audio_effects.conf exists under
- /vendor/etc/audio/sku_cape
- /vendor/etc/audio/sku_diwali
- /vendor/etc/audio/sku_taro
- /system/etc or /etc
It is absent from
- /odm/etc
- /vendor/etc
Again thanks so much for giving this a shot.
Click to expand...
Click to collapse
Following up, please have again all audio modules uninstlled, reboot and then follow:
- Install the official V4A FX module
- Reboot
- Run V4A app, it will complain that there is no driver installed and it will attempt to install
REBOOT but THEN DO NOT RUN V4A app yet!
1) Instead:
- go to /data/adb/modules/ViPER4AndroidFX/system/vendor
- there must be a subfolder etc with audio_effects.xml and audio_effects.conf
- check are those xml and conf files 'patched' by V4A as on my attached screenshots (they should be)?
2) Create the following system of folders:
/data/adb/modules/ViPER4AndroidFX/system/vendor/etc (that one must have been existed)
/data/adb/modules/ViPER4AndroidFX/system/vendor/odm/etc
/data/adb/modules/ViPER4AndroidFX/system/vendor/etc/audio/sku_cape
/data/adb/modules/ViPER4AndroidFX/system/vendor/etc/audio/sku_diwali
/data/adb/modules/ViPER4AndroidFX/system/vendor/etc/audio/sku_taro
Copy that patched audio_effects.xml from:
/data/adb/modules/ViPER4AndroidFX/system/vendor/etc
to the newly created folders:
/data/adb/modules/ViPER4AndroidFX/system/vendor/odm/etc
/data/adb/modules/ViPER4AndroidFX/system/vendor/etc/audio/sku_cape
/data/adb/modules/ViPER4AndroidFX/system/vendor/etc/audio/sku_diwali
/data/adb/modules/ViPER4AndroidFX/system/vendor/etc/audio/sku_taro
Copy also that patched audio_effects.conf from:
/data/adb/modules/ViPER4AndroidFX/system/vendor/etc
for the beginning only to:
/data/adb/modules/ViPER4AndroidFX/system/vendor/odm/etc
Copy also the attached post-fs-data.sh to /data/adb/modules/ViPER4AndroidFX
3) Then reboot, again DO NOT RUN V4A app but first check:
- do you still have the created folders and files from (1) and (2) in /data/adb/modules/ViPER4AndroidFX/system/vendor/...
Also, now in the 'real' folders, starting from root / (no more in /data/adb/modules...):
/vendor/etc
/vendor/odm/etc
/vendor/etc/audio/sku_cape
/vendor/etc/audio/sku_diwali
/vendor/etc/audio/sku_taro
- check if every of them now contains your patched audio_effects.xml from (1).
- and check if the first two contain the patched audio_effects.conf also from (1).
(they are actually not copied there but Magisk must have mounted them from /data/adb/modules/ViPER4AndroidFX/system/vendor/...)
Pls check and confirm.
Then open V4a app and if it does no more complain, switch to Legacy mode and enjoy
4) If V4a app does not pass yet but still complains that driver is missing, it will delete everything that you did in (2).
Hence reboot, redo step (2) again but this time copy both the patched audio_effects.xml and audio_effects.conf from:
/data/adb/modules/ViPER4AndroidFX/system/vendor/etc
to all those folders:
/data/adb/modules/ViPER4AndroidFX/system/vendor/odm/etc
/data/adb/modules/ViPER4AndroidFX/system/vendor/etc/audio/sku_cape
/data/adb/modules/ViPER4AndroidFX/system/vendor/etc/audio/sku_diwali
Reboot, again do not run yet V4A app but check if all the 'real' folders (starting from root /) contain the patched audio_effects.xml and audio_effects.conf:
/vendor/etc
/vendor/odm/etc
/vendor/etc/audio/sku_cape
/vendor/etc/audio/sku_diwali
/vendor/etc/audio/sku_taro
Pls check/confirm.
Now try again V4A app (with Legacy mode)...
Not sure would V4A app now really work but that was based on what you previously confirmed about your folders, trying to adapt how V4A mounts the patched xml and conf files to your case
zgfg said:
Ok, thanks
Then shortly based on 1) and 2):
/odm/etc
/vendor/odm/etc
/system/vendor/odm/etc
are all pointing to the same?
Click to expand...
Click to collapse
Yes, sorry had to drop the kiddo off at school. But, yeah they all point to the same.
ecera said:
Yes, sorry had to drop the kiddo off at school. But, yeah they all point to the same.
Click to expand...
Click to collapse
Ok, try the follow up, my subsequent post above. Let's see the results
@zgfg I installed the official viper magisk module, rebooted, opened the app, allowed the driver to install, rebooted, didn't open the viper app, went to /data/adb/modules/Viper4AndroidFX/system/vendor, it's empty. Besides a lib folder.
@zgfg something interesting though, I copied audio_effects.xml and .conf from /vendor/etc/audio/sku_cape and created a folder named "etc" in /data/adb/modules/Viper4AndroidFX/system/vendor and copied them there. Now, in /vendor/etc both audio_effects.xml & .conf exist. They aren't "patched" though.
ecera said:
@zgfg something interesting though, I copied audio_effects.xml and .conf from /vendor/etc/audio/sku_cape and created a folder named "etc" in /data/adb/modules/Viper4AndroidFX/system/vendor and copied them there. Now, in /vendor/etc both audio_effects.xml & .conf exist. They aren't "patched" though.
Click to expand...
Click to collapse
Yes, of course, that's the way how mounting works (and how all modules, including V4A utilize that)
Everything that Magisk finds in
/data/adb/modules/<some module folder>/system/<subfolders>/<file>
will be mounted to
system/<subfolders>/<file>
Eg, if you use Systemless hosts and AdAway in the root mode, then AdAway writes to:
/data/adb/modules/hosts/system/etc/hosts
and Magisk mounts that (upon reboot) to:
/system/etc/hosts
---
You could try to run V4A app now with your 'fake' XML and conf files in /vendor/etc (although I'm not sure how would VA app react when it already finds the XML and conf file in /data/adb/modules/Viper4AndroidFX/system/vendor/etc - the same place where it must write its own patched files with the same names)
to check would it then find the (mounted) XML and conf file from /vendor/etc
and would it create the corresponding patched files in its /data/adb/... folder
If it does, then you could continue with my previous post
@zgfg so following your instructions everything is working as far as binding all the locations. The only one that is not sticking is /data/adb/modules/ViPER4AndroidFX/system/vendor/odm/etc. I'm able to copy the patched audio_effects.xml and .conf in there, but they aren't reflecting in the "real" folder (/system/vendor/odm/etc/ or odm/etc.
ecera said:
@zgfg so following your instructions everything is working as far as binding all the locations. The only one that is not sticking is /data/adb/modules/ViPER4AndroidFX/system/vendor/odm/etc. I'm able to copy the patched audio_effects.xml and .conf in there, but they aren't reflecting in the "real" folder (/system/vendor/odm/etc/ or odm/etc.
Click to expand...
Click to collapse
Ok, then copy the attached post-fs-data.sh to /data/adb/modules/ViPER4AndroidFX
(Instead of the previously given sh file)
In the sh script you will see two mount -o bind commands, one for XML and the other for conf, like:
mount -o bind /data/adb/modules/ViPER4AndroidFX/system/vendor/etc/audio_effects.xml /system/vendor/odm/etc/audio_effects.xml
Their purpose is to manually mount from:
/data/adb/modules/ViPER4AndroidFX/system/vendor/etc
to:
/system/vendor/odm/etc/
And REBOOT
Hence again, in the first path (folder) the patched XML and conf files must be present
If it doesn't work you can try shortening the second folder path (both for XML and conf) to:
/vendor/odm/etc
or even to:
/odm/etc
zgfg said:
Ok, then copy the attached post-fs-data.sh to /data/adb/modules/ViPER4AndroidFX
(Instead of the previously given sh file)
In the sh script you will see two mount -o bind commands, one for XML and the other for conf, like:
mount -o bind /data/adb/modules/ViPER4AndroidFX/system/vendor//audio_effects.xml /system/vendor/odm/etc/audio_effects.xml
Their purpose is to manually mount from:
/data/adb/modules/ViPER4AndroidFX/system/vendor/etc
to:
/system/vendor/odm/etc/
And REBOOT
Hence again, in the first path (folder) the patched XML and conf files must be present
If it doesn't work you can try shortening the second folder path (both for XML and conf) to:
/vendor/odm/etc
or even to:
/odm/etc
Click to expand...
Click to collapse
That works as far as binding the existing audio_effects.xml that is located in /odm/etc. The .conf file doesn't appear in /odm/etc/. It does appear in /system/etc/ which I was able to mount a patched version by creating a corresponding folder in /data/adb/modules/Viper4AndroidFX/system/etc.
So I think it's safe to say that every audio_effects.xml & .conf are patched at this point.
Driver loop still persists though, I read one member point out that if he ran dumpsys media.audio_flinger, he noticed that the OnePlus 10 pro is using lib64 audio folders instead of the regular lib folders. It seems like viper tries to use the regular lib folder since the lib files that are patched are under lib and not lib64. Not sure how significant that is.
ecera said:
That works as far as binding the existing audio_effects.xml that is located in /odm/etc. The .conf file doesn't appear in /odm/etc/. It does appear in /system/etc/ which I was able to mount a patched version by creating a corresponding folder in /data/adb/modules/Viper4AndroidFX/system/etc.
So I think it's safe to say that every audio_effects.xml & .conf are patched at this point.
Driver loop still persists though...
Click to expand...
Click to collapse
I see now that in post #9 you already wrote that conf file was originally not present in /odm/etc, hence you don't need to bind it there (remove the corresponding mount -o bind command from sh file)
Now, upon the V4A still looped, did you check, do you still have all the folders and files in /data/adb/modules/ViPER4AndroidFX (you previously created) in place.
Ie, are the patched XML and conf files still in 'real' folders after you rebooted?
If so, you are lucky (you don't need to start all over again) - but then copy the whole structure:
/data/adb/modules/ViPER4AndroidFX
to eg (not a nice place to keep but it will be close to your hands and will not harm):
/data/adb/ViPER4AndroidFX
Then you can experiment further if you have an idea what to do with the libs
If, at any moment, V4A (by looping) deletes what you had in /data/adb/modules/ViPER4AndroidFX
you could then easily repair it from your copy, reboot and continue experimenting
---
If you zip and attach the complete content of that /data/adb/modules/ViPER4AndroidFX
I can give you then a flashable zip (module) file that you could easily install through Magisk app to start from that 'frozen' point all over again
ecera said:
Driver loop still persists though, I read one member point out that if he ran dumpsys media.audio_flinger, he noticed that the OnePlus 10 pro is using lib64 audio folders instead of the regular lib folders. It seems like viper tries to use the regular lib folder since the lib files that are patched are under lib and not lib64. Not sure how significant that is.
Click to expand...
Click to collapse
Regarding the lib vs lib64:
Check in the patched audio_effects.conf file
There should be a number of libraries listed as:
path /vendor/lib/soundfx/*.so
Are they really listed with /vendor/lib/
or with
vendor/lib64/
---
Disable the V4A module (through Magisk app or by placing an empty file named disable into /data/adb/modules/ViPER4AndroidFX - Magisk app by itself disables a particular module that way) and REBOOT and then check the original, not-patched conf file in those 'real' folders and check if it refers to lib or lib64
PS: Check those not-patched conf files in all four locations you said you had them in the post #9
Also, with the disabled V4A module, run su and then your dumpsys command directly from Terminal app and look does it list /vendor/lib/soundfx/ or /vendor/lib64/soundfx/ libraries