Database Develop

[HOW TO] - Enable CRT animation in Jelly Bean on the N7

Noticed none of the current builds have the CRT animation enabled, thought I'd share how to turn it on. Please note that it is at times a bit buggy. For me it works about 8 out of 10 times.
What it is:
Note: 1 - This will work on any device and on any version of Android back to GB. (Obviously the Nexus specific tools wont work on anything other than the Nexus)
Note 2 - You will have to redo this every time you update your rom.
Here's the quick rundown -
First, you'll have to pull the framework-res.apk from your tablet.
This can be done via adb, but the easiest way would be to either use WugFresh's Nexus Root Toolkit or mskips Google Nexus 7 TOOLKIT.
When asked what file to pull, type in "/system/framework/framework-res.apk" (without quotes)
Once you have that pulled, install this tool: http://forum.xda-developers.com/showthread.php?t=1432152
Follow the directions on how to use it in the thread.
Once you have decompiled the apk, you'll want to edit the "files-to-edit\framework-res.apk\res\values\bools.xml" file.
The value you want to change in the bools value is the "<bool name="config_animateScreenLights">true</bool>" change "true" to "false". I reccommend downloading Notepad++ to edit.
Make sure you save it. Once saved, recompile the apk using the tool you install, then create an update zip (I renamed mine to crtanimation.zip for ease).
Reboot into recovery, flash the zip, clear cache, reboot.
Tada!

Krunk_Kracker said:
Noticed none of the current builds have the CRT animation enabled, thought I'd share how to turn it on. Please note that it is at times a bit buggy. For me it works about 8 out of 10 times.
Here's the quick rundown -
First, you'll have to pull the framework-res.apk from your tablet.
This can be done via adb, but the easiest way would be to either use WugFresh's Nexus Root Toolkit or mskips Google Nexus 7 TOOLKIT.
When asked what file to pull, type in "/system/framework/framework-res.apk" (without quotes)
Once you have that pulled, install this tool: http://forum.xda-dev...d.php?t=1432152
Follow the directions on how to use it in the thread.
Once you have decompiled the apk, you'll want to edit the "files-to-edit\framework-res.apk\res\valuesbools.xml" file.
The value you want to change in the bools value is the "<bool name="config_animateScreenLights">true</bool>" change "true" to "false".
Make sure you save it. Once saved, recompile the apk using the tool you install, then create an update zip (I renamed mine to crtanimation.zip for ease).
Reboot into recovery, flash the zip, reboot.
Tada!
Click to expand...
Click to collapse
"Once you have that pulled, install this tool: http://forum.xda-dev...d.php?t=1432152"
This link is not working.

TahrirSquare said:
"Once you have that pulled, install this tool: http://forum.xda-dev...d.php?t=1432152"
This link is not working.
Click to expand...
Click to collapse
Apologies.
Fixed now

Why would someone want to do this?

Guardsix said:
Why would someone want to do this?
Click to expand...
Click to collapse
Why would someone want to put a custom rom on N7?
Sent from my Nexus 7 using Tapatalk 2

They most likely don't know what CRT animation is, NOT why they might want to make changes to the system.
Nothing in the OP provides a hint as to what that is or what it does. To be honest, I'm not sure I know what it is. A quick search shows that it is enabled in a lot of ROMs but not what it actually is or does.
Sent from my Nexus 7

krelvinaz said:
They most likely don't know what CRT animation is, NOT why they might want to make changes to the system.
Nothing in the OP provides a hint as to what that is or what it does. To be honest, I'm not sure I know what it is. A quick search shows that it is enabled in a lot of ROMs but not what it actually is or does.
Sent from my Nexus 7
Click to expand...
Click to collapse
OK, makes sense, I was assuming most knew what it meant.
I'll make a quick video.
Just made a video, uploading it.

krelvinaz said:
They most likely don't know what CRT animation is, NOT why they might want to make changes to the system.
Nothing in the OP provides a hint as to what that is or what it does. To be honest, I'm not sure I know what it is. A quick search shows that it is enabled in a lot of ROMs but not what it actually is or does.
Sent from my Nexus 7
Click to expand...
Click to collapse
If you don't know what it is then you obviously haven't flashed many roms and therefore should probably not even attempt this...
Thanks OP and sry for the ungrateful ones here.

updated OP with a demo vid
I guess the CRT animation is more obscure than I thought.

Okay... I get it... It enables animation effects when turning the device off, rather than just blanking the screen.
I get the same effect turning on and off with
https://play.google.com/store/apps/details?id=com.soulfulz.android.turnoffscreen
You can select from a number of effects, sounds for both when the device is turned on and off via the button. You have to hit the button for it to do it, but for the risk of modifying system files, this is easy and safe to do.

krelvinaz said:
Okay... I get it... It enables animation effects when turning the device off, rather than just blanking the screen.
I get the same effect turning on and off with
https://play.google.com/store/apps/details?id=com.soulfulz.android.turnoffscreen
You can select from a number of effects, sounds for both when the device is turned on and off via the button. You have to hit the button for it to do it, but for the risk of modifying system files, this is easy and safe to do.
Click to expand...
Click to collapse
Except your solution is wakelock city on top of having to enable it as a device administrator. Sounds like you also have to hit the shortcut or use the app itself to get the desired effect versus it being naturally accomplished when hitting the power button/screen timeout. And if it doesn't work in ICS, not sure it will work on JB.

krelvinaz said:
Okay... I get it... It enables animation effects when turning the device off, rather than just blanking the screen.
I get the same effect turning on and off with
https://play.google.com/store/apps/details?id=com.soulfulz.android.turnoffscreen
You can select from a number of effects, sounds for both when the device is turned on and off via the button. You have to hit the button for it to do it, but for the risk of modifying system files, this is easy and safe to do.
Click to expand...
Click to collapse
My way is easy and safe to do, if you follow the direction.
All your doing is turning something on. It's something that Google intended to be toggled.

Krunk_Kracker said:
My way is easy and safe to do, if you follow the direction.
Click to expand...
Click to collapse
Something users of XDA are so good at doing? Reading and following instructions.
All your doing is turning something on. It's something that Google intended to be toggled.
Click to expand...
Click to collapse
Curious, they didn't implement it in their flagship first tablet and first official device to have Jelly Bean?
BTW, I am not knocking you, just have a lot of experience dealing with users that don't read, can't follow instructions...
The info on extracting and the tool was good reading, I just know a lot of users that will botch this up and start posting BRICKED threads.
Via my HTC Rezound

krelvinaz said:
Something users of XDA are so good at doing? Reading and following instructions.
Curious, they didn't implement it in their flagship first tablet and first official device to have Jelly Bean?
BTW, I am not knocking you, just have a lot of experience dealing with users that don't read, can't follow instructions...
The info on extracting and the tool was good reading, I just know a lot of users that will botch this up and start posting BRICKED threads.
Via my HTC Rezound
Click to expand...
Click to collapse
I'm sorry if people are unable to follow direction, but honestly that's not my problem.
If they mess it up, it wont brick, and if it does, all they have to do is dirty flash their rom and it's fixed.

I asked the question "Why" because it seems a lot of trouble just to see your device (N7, in this case) turn off. I've done a great deal of modding to my ICS devices, but haven't really found much reason to mod a JB device. I know there are tons of boot animations which make your device really different when turned on, but having CRT just for turning off your device seems a waste of time.
Of course, this is only my opinion and I'm glad you figured out how to do this, but I still don't understand why!

Guardsix said:
I asked the question "Why" because it seems a lot of trouble just to see your device (N7, in this case) turn off. I've done a great deal of modding to my ICS devices, but haven't really found much reason to mod a JB device. I know there are tons of boot animations which make your device really different when turned on, but having CRT just for turning off your device seems a waste of time.
Of course, this is only my opinion and I'm glad you figured out how to do this, but I still don't understand why!
Click to expand...
Click to collapse
Why not?
To sound cliche, Android is all about options.
I present you with yet another modding option.
Sent from my Nexus 7 using Tapatalk 2

I'm not really understanding the animosity with this simple mod...

Neat! I am sure that I will get around to this eventually but I am surprised that I haven't noticed that there was no CRT animation enabled already.
Sent from my Nexus 7 using xda app-developers app

Guardsix said:
I asked the question "Why" because it seems a lot of trouble just to see your device (N7, in this case) turn off. I've done a great deal of modding to my ICS devices, but haven't really found much reason to mod a JB device. I know there are tons of boot animations which make your device really different when turned on, but having CRT just for turning off your device seems a waste of time.
Of course, this is only my opinion and I'm glad you figured out how to do this, but I still don't understand why!
Click to expand...
Click to collapse
Don't understand why you don't just switch to an iphone

Ok I tried what the OP has posted but the compiler tool is borked, no way to recompile the file after editing the file. Read over the original posting and found that the issue is still not fixed, any other way to do this??

[Q] Build.prop and the nexus 5 and 6

okay i have found many threads for the build.prop tweaks for the nexus 5. Do these same tweaks work for a nexus 6? If not where can i find such a guide to help with tweaks. And also if i just changed my phone model to nexus 5 would that make a difference. Yes I have made a nandroid backup. Any help would me much appreciated or if your looking for the same thing maybe we could help each other.

Ruthlez Ryn0 said:
okay i have found many threads for the build.prop tweaks for the nexus 5. Do these same tweaks work for a nexus 6? If not where can i find such a guide to help with tweaks. And also if i just changed my phone model to nexus 5 would that make a difference. Yes I have made a nandroid backup. Any help would me much appreciated or if your looking for the same thing maybe we could help each other.
Click to expand...
Click to collapse
most build.prop edits, and I mean most, like 95% of them, are old and do nothing for modern phones. a few still work though. the build.prop edits would be the same as most nexus 5, some would need specific changes for the n6 though.

simms22 said:
most build.prop edits, and I mean most, like 95% of them, are old and do nothing for modern phones. a few still work though. the build.prop edits would be the same as most nexus 5, some would need specific changes for the n6 though.
Click to expand...
Click to collapse
thanks alot for the quick response, well that's a bummer. is there anything out to optimize the nexus. Wonder if I should have kept S6.

Ruthlez Ryn0 said:
thanks alot for the quick response, well that's a bummer. is there anything out to optimize the nexus. Wonder if I should have kept S6.
Click to expand...
Click to collapse
if you go through all the build.prop edits tou know, youll find a few that work on the n6. for instance, you need a build.prop edit to gwt tethering to work, so that your carriers dont see. or, my favorite, i use this when benchmarking, to make fun of people making fun of people.. ill set a build. prop edit to remove the fps limit that is set for our devices :angel:

simms22 said:
if you go through all the build.prop edits tou know, youll find a few that work on the n6. for instance, you need a build.prop edit to gwt tethering to work, so that your carriers dont see. or, my favorite, i use this when benchmarking, to make fun of people making fun of people.. ill set a build. prop edit to remove the fps limit that is set for our devices :angel:
Click to expand...
Click to collapse
Thank you so much for the response. I used a couple and could notice a change, the list I am going from is so long, and the only way for me to input them in the build.prop and sticks. Is to edit it with es note editor. Tried copy and past didn't work. Tried doing with ADB by pulling build.prop and editing it. Didn't work. Only works if I manually put it in. Well guess I will go thru and see which ones work and don't. Or which ones I can tell anyways. Took a couple benchmarks, before I am going to apply tweaks.

Ruthlez Ryn0 said:
Thank you so much for the response. I used a couple and could notice a change, the list I am going from is so long, and the only way for me to input them in the build.prop and sticks. Is to edit it with es note editor. Tried copy and past didn't work. Tried doing with ADB by pulling build.prop and editing it. Didn't work. Only works if I manually put it in. Well guess I will go thru and see which ones work and don't. Or which ones I can tell anyways. Took a couple benchmarks, before I am going to apply tweaks.
Click to expand...
Click to collapse
i use root explorer. i just enter it in, or copy/paste it, save it reboot, and it always works. btw, my build.prop edit to get rid of the fps limit is..
debug.egl.swapinterval=0
copy this to your build.prop, save it, then reboot. to re enable the limit, change the 0 to a 1 and reboot.

[Mod] Native volume boost - no apps needed! mixer_paths.xml - Update Jan 13 2016

This is a tiny mod to get some better volume from Moto G3. I used the mixer_paths.xml from the .44 2gb build for xt1540, but the file should be universal for g3, maybe even g2 and g...I haven't tested it on anything but my own g3, so I can't say.
Use at your own risk!
Drop the file in /etc, rename to mixer_paths.xml, and change permissions to rw-r--r--
To revert, use the mixer_paths-84.xml file provided, rename to mixer_paths.xml and set permissions rw-r--r--
You must reboot for changes to apply. This is a TOTAL volume mod!! it will boost every volume on the device.
Default value is 84, I set it at 90. I like my music extremely loud, and this was slightly lower than I would choose, so it should be good for most people. If anyone wants more or less, I can take requests.
Code:
[b]**Update Changelog:[/b]
[u]Jan 13 2016 - [/u]
- fixed oversight for in-call volume.
- changed file names to be easier to differentiate.
- mixer_paths-84.xml is the stock 100% untouched backup now.
- same exact file, new name. no need to redownload.
- added volume 92.
*WARNING!! For the new vol-92 option, speaker volume WILL be distorted turned all the way up. I got lazy and didn't want to play trial and error to find the one that controls speaker. I will fix this in the next update, coming as soon as I have time. For now, please just turn it down a click or two if you use this one.
mixer_paths-84-90.xml (in- call volume 84 & all others 90.)

Clipping like hell.

No issues, working great but sometimes on full volume, the lower back gets warmed up around the speaker.

maarten2001 said:
Clipping like hell.
Click to expand...
Click to collapse
what rom and music app are you using? I've flashed quite a few roms and used this with no issues on any yet.

I've used this with the MM soak test and it still works fine. It shouldn't need any updating when the official MM rom releases.
....just an fyi

hp420 said:
This is a tiny mod to get some better volume from Moto G3. I used the mixer_paths.xml from the .44 2gb build for xt1540, but the file should be universal for g3, maybe even g2 and g...I haven't tested it on anything but my own g3, so I can't say.
Use at your own risk!
Drop (replace) the file in /etc and change permissions to rw-r--r--
To revert, use the mixer_paths.xml.bak file provided, rename mixer_paths.xml, and set permissions.
You must reboot for changes to apply. This is a TOTAL volume mod!! it will boost every volume on the device.
Default value is 84, I set it at 90. I like my music extremely loud, and this was slightly lower than I would choose, so it should be good for most people. If anyone wants more or less, I can take requests.
mixer_paths.xml (volume 90)
https://drive.google.com/file/d/0B8idNtSYGvpqejFHX3JSdmphX00
mixer_paths.xml.bak (restore stock)
https://drive.google.com/file/d/0B8idNtSYGvpqeExxV25Rb0gzNzA
Click to expand...
Click to collapse
will this work on moto E X1521?though currently using cm12.1

maybe...it's a standard aosp file. I would back up your original mixer_paths.xml and give it a shot. You can just copy your original one back if you have any issues.

All ok in Moto G 3gen (XT1541)
my moto g is now a disco inferno xD (thx man)

dont work in CM12.1 and Blu Life 8

viciuz said:
dont work in CM12.1 and Blu Life 8
Click to expand...
Click to collapse
Only stock, sorry

Works for me on cm12.1

Works amazing on Resurrection-Remix-LP-v5.5.9 no clipping yet
Osprey

Works like a charm here (stock 5.1.1). I was really anoyed by the weak maximum volume, much better now Thanks again.

On my XT1541 all notification, ringtone, calls, etc, goes off, no sounds, worst, after backup the file it's the same no results.
Solution..?? Restore backup or somebody share the stock file to XT1541?
Someone can help me?
Thanks.
Enviado do meu MotoG3 através de Tapatalk

djekan said:
On my XT1541 all notification, ringtone, calls, etc, goes off, no sounds, worst, after backup the file it's the same no results.
Solution..?? Restore backup or somebody share the stock file to XT1541?
Someone can help me?
Thanks.
Enviado do meu MotoG3 através de Tapatalk
Click to expand...
Click to collapse
What rom are you using?
Also, if you restored the original file and have the same results you obviously did something wrong....that or it wasn't working beforehand either, because to restore the original file is to return it to its state prior to modifying it...as in getting rid of my modification entirely. Trust me, my file doesn't affect your device once it's gone...that is completely impossible in every way, shape and form.
Did you remember to change the permissions?? That would definitely explain having absolutely no sound at all.
Also, your sku means absolutely nothing since we all share this identical file within our firmware. There is not a single moto g3 variant which comes stock with a different mixer_paths.xml

Hello again, after a few days of testing the maximum volume is still a bit weak in my opinion (especially for classical music ), is there any way to increase it even more? Thank you again for your work :good:

mendelssohn said:
Hello again, after a few days of testing the maximum volume is still a bit weak in my opinion (especially for classical music ), is there any way to increase it even more? Thank you again for your work :good:
Click to expand...
Click to collapse
Ask and receive! Please see the warning note in the OP before installing. Enjoy!
Code:
[b]**Update Changelog:[/b]
[u]Jan 13 2016 - [/u]
- fixed oversight for in-call volume.
- changed file names to be easier to differentiate.
- mixer_paths-84.xml is the stock 100% untouched backup now.
- same exact file, new name. no need to redownload.
- added volume 92.

Hello, amazing thank you very much

Hmm... Wonder if I could write a OpenRecovery script that would allow you to pick one of these mods, flash it (and backup current settings), and set permissions...
Then, if someone was completely stock but with an unlocked bootloader (like me) you could boot twrp, flash the mod, and still be completely stock and not rooted, thus able to receive an OTA safely too.
Hmm...
Or I could be lazy and finally just root... Tired of those iBrats at work blowing away the volume of my MotoG3 on the speakers in the back of the house, on max with speakers on max it's sad compared to iPhone.
Sent from my MotoG3 using Tapatalk

acejavelin said:
Hmm... Wonder if I could write a OpenRecovery script that would allow you to pick one of these mods, flash it (and backup current settings), and set permissions...
Then, if someone was completely stock but with an unlocked bootloader (like me) you could boot twrp, flash the mod, and still be completely stock and not rooted, thus able to receive an OTA safely too.
Hmm...
Or I could be lazy and finally just root... Tired of those iBrats at work blowing away the volume of my MotoG3 on the speakers in the back of the house, on max with speakers on max it's sad compared to iPhone.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
You're more than welcome to use these any way you like

Marshmallow with Kitkat's Output Power

Hello guys. I had posted some months ago my question but all I was suggested was installing mods that I already had tried.
So, my 'problem' is that I find Stock Marshmallow's output(volume and bass) on headphones (3.5 jack) pretty low compared to Stock Kitkat. Especially the bass, it is really, really louder/heavier on Kitkat.
Is there any way to get/move Kitkat's sound enhancements right into Marshmallow?
Thanks in advance, have a happy new year!

The only way to try this would be decrypting the original KitKat files and recode them into MM, though you need some knowledge about how it works for it. As for now, I do not know any way to get back that feature from KK.
Mods are really great in this sort of situation, I myself use the A.R.I.S.E. mod and configured it for my in-ears.

devil188 said:
The only way to try this would be decrypting the original KitKat files and recode them into MM, though you need some knowledge about how it works for it. As for now, I do not know any way to get back that feature from KK.
Mods are really great in this sort of situation, I myself use the A.R.I.S.E. mod and configured it for my in-ears.
Click to expand...
Click to collapse
Unfortunately, I have no knowledge of coding etc.. I had tried arise sound mod but the sound was completely distorted(maybe I had installed something wrong,but all I did was install a .zip file and nothing more.)
Edit: could you message me and redirect me to the things you did and worked for you? I think I'll give a try tonight or tomorrow night! Thanks!

kwstas 13 said:
Unfortunately, I have no knowledge of coding etc.. I had tried arise sound mod but the sound was completely distorted(maybe I had installed something wrong,but all I did was install a .zip file and nothing more.)
Edit: could you message me and redirect me to the things you did and worked for you? I think I'll give a try tonight or tomorrow night! Thanks!
Click to expand...
Click to collapse
Well, installing the .zip is fine, but you ... gotta turn it on, too. When you flashed the zip, a new tool called Viper4Arise pops up in your app list. Open that and configure how you like to. In the app, you can change everything you like (and there's tons of stuff, trust me) but keep in mind to check if the module is active ( [≡] > Driver Status).
As of the settings I've done, I made the for my personal in-earphones (SoundMagic E10). There are things like ViPER-DDC which makes the sound of your head/earphones pretty nice if they're supported, if not, well then you gotta tune it yourself. Might plan to listen to a lot of different music and testing all the settings for your own preferences

devil188 said:
Well, installing the .zip is fine, but you ... gotta turn it on, too. When you flashed the zip, a new tool called Viper4Arise pops up in your app list. Open that and configure how you like to. In the app, you can change everything you like (and there's tons of stuff, trust me) but keep in mind to check if the module is active ( [≡] > Driver Status).
As of the settings I've done, I made the for my personal in-earphones (SoundMagic E10). There are things like ViPER-DDC which makes the sound of your head/earphones pretty nice if they're supported, if not, well then you gotta tune it yourself. Might plan to listen to a lot of different music and testing all the settings for your own preferences
Click to expand...
Click to collapse
Well, I'll maybe give a try and write you back... I didn't really understand whay you said there ' check if the module is active ( [≡] > Driver Status). '
Also, which one of these folders should I open and then,which version(file name) should I download?
I'm on Stock 6.0.1 with any other mod installed.
(yes,i'll make a nandroid backup before installing it)
Thanks in advance
Edit: I installed ViPER4Arise+2.5.0.5 and it worked fine,but still,the sound is quite,compared to Stock KitKat... Even after raising Master Gate (Limiter) to the max (6dB)... I don't know what to do

kwstas 13 said:
Well, I'll maybe give a try and write you back... I didn't really understand whay you said there ' check if the module is active ( [≡] > Driver Status). '
Also, which one of these folders should I open and then,which version(file name) should I download?
I'm on Stock 6.0.1 with any other mod installed.
(yes,i'll make a nandroid backup before installing it)
Thanks in advance
Edit: I installed ViPER4Arise+2.5.0.5 and it worked fine,but still,the sound is quite,compared to Stock KitKat... Even after raising Master Gate (Limiter) to the max (6dB)... I don't know what to do
Click to expand...
Click to collapse
Then it is probably limited by the ROM itself.. Well you can look up how to create your own custom rom with higher output at the audio jack, but aside from that, I don't have any other ideas how to raise it other than going back to kitkat.
Well the volume is loud enough for me, so sadly I can't help you with this

devil188 said:
Then it is probably limited by the ROM itself.. Well you can look up how to create your own custom rom with higher output at the audio jack, but aside from that, I don't have any other ideas how to raise it other than going back to kitkat.
Well the volume is loud enough for me, so sadly I can't help you with this
Click to expand...
Click to collapse
Exactly, KitKat allowed more output volume than Marshmallow does, I guess....I wish I knew how to increase the output levels and set them just as high as the Stock Kikat are.

kwstas 13 said:
Exactly, KitKat allowed more output volume than Marshmallow does, I guess....I wish I knew how to increase the output levels and set them just as high as the Stock Kikat are.
Click to expand...
Click to collapse
I might just randomly found a way to set the volume gain, but you need a unlocked bootloader + elitekernel (or any other) for that.

devil188 said:
I might just randomly found a way to set the volume gain, but you need a unlocked bootloader + elitekernel (or any other) for that.
Click to expand...
Click to collapse
Ah yeah, I found that too some months ago,forgot to mention that...but i don't want to unlock bootloader for now...thank you man!

Getting the 'Click' to work again.

Yes, I know that the filename is "Effect_Tick.ogg" located in /system/media/audio/ui. I also know that the 'setting' is in "Settings -> Sound and notification -> Other sounds". But for some reason, it just will not play.
Yeah, I like to hear that click when I press things on my phone(s). So much so, that I have kept the old ICS sound around to write it to my other phones since.
I'll try to make this short. I had my old Nexus 6 go into a bootloop about a year ago so I restored it with a factory flash and then re-rooted it and flashed my favorite Rom, Pure Nexus 5.1.1. It (the click) had worked before, but I do not know why it stopped working. There were other problems still on my phone so I finally bought a new one and flashed it to this ROM. I used MyBackupPro to restore my apps as I do not care for some of the newer version of apps that I use. I was also trying to flash the TBO market on my phone as well. When first I flashed my phone, the click was working, but somewhere along the line it stopped. If I use root explorer and go to the file's location and press on it, it will play just fine. So I'm just not sure what's up.
I did get a big hint. I installed "FP Click sound changer". Within that app, when I press on "Effect_Tick.ogg" I get the following message:
"java.lang.NullPointerException: Attempt to invoke virtual method 'void android.media.MediaPlayer.setAudioStreamType(int)' on a null object reference"
This leads me to believe that is is something inside of framework-res.apk or systemui.apk or something like that. I didn't see enough in build.prop to make me think it would be in there. Any ideas?
Thanks in advance.

The error you're getting with FP Click Sound Changer is because the app likely isn't properly initialized. Meaning a change in Android between when the app was last updated and now has broken the app. The error has nothing to do with either of the .APK files you mentioned. If I recall correctly, neither system app deals with media to begin with.
The most obvious question here is whether you have tried a new copy of the audio file, even if it appears to work perfectly. If you have done that and are still having issues, one of your apps that you are using is causing the problem. You're going to have to do some troubleshooting to resolve this, namely starting with a blank slate and reinstalling apps one at a time until you find the one that causes the problem. Before you protest, any answers without you attempting some troubleshooting on your own are merely guesses made off of inadequate data.

Thank you for the reply, however my ROM was 'cooked' up on Sept 2015 and FP Click Sound changer was released/updated on Dec 26 2015, so what you suggest cannot be the cause. Besides, it only throws the error on Effect_Tick.ogg and no other system sound. And yes, I do have fresh copy of the file from ICS days.
But you are correct, if nobody knows which system app would throw that error message, then I know a fresh start is in order.

On this forum, many people have updated their N6 to more up-to-date versions of Android than the version you had. However, I wouldn't have provided that answer had you told us which version of Android you were running in the first place as well as the fact you built it yourself.
In any event, I hope your fresh start works out for you. You may also want to consider building a newer version of AOSP for yourself as well.

Thank you again for the reply, however:
Strephon Alkhalikoi said:
However, I wouldn't have provided that answer had you told us which version of Android you were running in the first place as well as the fact you built it yourself.
Click to expand...
Click to collapse
teddyearp said:
I had my old Nexus 6 go into a bootloop about a year ago so I restored it with a factory flash and then re-rooted it and flashed my favorite Rom, Pure Nexus 5.1.1. <snip>
Click to expand...
Click to collapse
I am trying to do a Google search on the error message itself as well.

I missed that in your post. Oops.

Strephon Alkhalikoi said:
I missed that in your post. Oops.
Click to expand...
Click to collapse
Well, I certainly meant no offence. Some years back, I used to to help folks out with their Android phones/problems and would at times be about the same way as you. Many times the details were not there. However equally so sometimes, the OP did provide the answers but the others that would chime in did not seem to read all of them.
With that said, I was thinking about rewording my question to perhaps ask if anyone knew which system apps on Android 5.1.1 would call for Effect_Tick.ogg so I could try to find where it had been set to 'null', but I stumbled across my solution after all. File permissions. So for any readers:
Yes, using ES Explorer, I copied again my good Effect_Tick.ogg to /system/media/audio/ui and it still didn't work except in music player. So I thought since ES would allow me to see and change file permissions, let me take a look. Sure enough, the file permissions for Effect_Tick.ogg were different than all the other sounds in that location. It was set to rw,rw and group sdcard,s. All the others were rw,r,r and group root. Changed to match the others and problem solved. :highfive:
Thanks very much again for trying to help, at least someone (you) did and that does mean a lot to me on such an old(ish) device since as you said, many have moved on and/or flashed much newer versions of Android to the N6. :good::good:

I'm glad you solved your problem. Even better, you came back to tell us about it.
Too many find the solution and don't say anything.

Strephon Alkhalikoi said:
<snip>Too many find the solution and don't say anything.
Click to expand...
Click to collapse
How well I remember that fact.