I have a Lenovo S939 (Android 4.2.2, rooted) and the setting to change the default notification sound is missing. Is there a good app that can be used to browse all system settings and make changes directly (something like regedit in Windows)? Or can this setting be changed in the file system by editing some preferences file? If so, how can I find it?
James Bond 007 said:
I have a Lenovo S939 (Android 4.2.2, rooted) and the setting to change the default notification sound is missing. Is there a good app that can be used to browse all system settings and make changes directly (something like regedit in Windows)? Or can this setting be changed in the file system by editing some preferences file? If so, how can I find it?
Click to expand...
Click to collapse
No settings to change that? That's crazy...I've worked on 100s of phones and have never seen that... But the build.prop found in /system typically has the "code" that points to which file to use for the default sounds.
Thanks, checked the file and found this line: ro.config.notification_sound=HeavenNearby.ogg
If changed, will this be picked up on reboot?
James Bond 007 said:
Thanks, checked the file and found this line: ro.config.notification_sound=HeavenNearby.ogg
If changed, will this be picked up on reboot?
Click to expand...
Click to collapse
Yes. Make sure to make a backup of your build.prop first and that the permissions are still 0644 before you reboot or you'll have to restore the entire phone.
I have changed it to another sound file in the same directory and rebooted, but the sound stayed the same, unfortunately.
Edit: I have "fixed" it by copying the desired sound file over the default one.
Related
To start with, I have the newest version of "CyanogenMod 9 nightly builds"
I might be missing something here but I can't seem to ADD new notifications to this MOD. I added a ringtone, (easy enough) but I have tried adding notifications to the Root DIR "notifications" and I have added them to DIR "media/audio/notifications" and neither show up. what am I missing?
Have you rebooted? The ROM scans the /system directory on boot.
If so, have you checked the permissions match the existing ogg or mp3 files?
Or, if you don't want to mess with system files, use Ringtone Maker app.
LenAsh said:
Have you rebooted? The ROM scans the /system directory on boot.
If so, have you checked the permissions match the existing ogg or mp3 files?
Click to expand...
Click to collapse
Yes and Yes.
Still not working...
i change my ringtones and stuff before flashing, just to let you know that can be done too
I have never had a problem doing it with any other ROM before. So i don't know what is going on with CM9...
Galaxy S3 rooted + unlocked
Can someone tell me how to write to "/sys/class" files? I have checked to make sure that the files I want to modify have permissions to 0777.
From terminal I enter..
"echo 1 >/sys/class/lcd/panel/gamma_mode"
I am still unable to change the setting. What gives?? What am I doing wrong?
There must be a way right??
Any help is appreciated!!!!!
You have a quoting problem there try it like this.
su
echo "1" >/sys/class/lcd/panel/gamma_mode
Unfortunately it still doesn't change the setting. If I go straight to the gamma_mode file and change it with root explorer, save and exit it will go right back to it's default setting. It will not hold the new value. It's value is currently 2. I can't change it to anything else. Same thing with any of the files located there such as contrast and brightness. Permissions are set to write but they immediately go back to there default settings if you try to change them.
I seem to have this issue with all files in /sys/class.
razz1 said:
Unfortunately it still doesn't change the setting. If I go straight to the gamma_mode file and change it with root explorer, save and exit it will go right back to it's default setting. It will not hold the new value. It's value is currently 2. I can't change it to anything else. Same thing with any of the files located there such as contrast and brightness. Permissions are set to write but they immediately go back to there default settings if you try to change them.
I seem to have this issue with all files in /sys/class.
Click to expand...
Click to collapse
Hi, I am knowing this thread is very old, but did you find a solution? I am having the same issue on my galaxy s7 rooted (4 years later )
I'm running a Galaxy Nexus, and the ROM I'm currently on has a Perfomance option in the Settings Menu, which gives control of the kernel and stuff. However, I'd rather use TricksterMod, and I would like to be able to launch TricksterMod from Settings instead of the Performance app.
So far, I've decompiled my Settings.apk, and looked through the files, and I'm not sure what to change.
I have to change \settings\res\xml\settings_headers.xml, correct? Specifically,
Code:
header android:icon="@drawable/ic_settings_performance" android:id="@id/performance_settings" android:title="@string/performance_settings_title" android:fragment="com.android.settings.performance.PerformanceSettings" />
I would also have to change \settings\res\values\strings.xml, specifically, the string referenced by "@string/performance_settings_title" so that I can have the correct name, correct?
And similarly, settings\res\drawable, for the icon.
The big question is, what do I replace with for "com.android.settings.performance.PerformanceSettings"? Do I need to move TricksterMod somewhere specific, or what would I reference? \data\app\com.bigeyes0x0.trickstermod-1.apk?
After making all these changes, I'd simply recompile and push the Settings.apk back without signing, correct? Have I missed any steps?
Firnagzen said:
The big question is, what do I replace with for "com.android.settings.performance.PerformanceSettings"? Do I need to move TricksterMod somewhere specific, or what would I reference? \data\app\com.bigeyes0x0.trickstermod-1.apk?
Click to expand...
Click to collapse
That's what I would try BUT would just be that, to try, seems like you have everything else covered.
Hm. Well, that didn't work.
I successfully made the edits, recompiled, and pushed the file in place of the old Settings.apk.
The Settings app immediately disappeared, and trying to install it (selecting the .apk with a file manager) didn't work; it simply gave me an 'App failed to install'.
Any suggestions as to what I might have done wrongly?
Anyone?
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
deathsquad737 said:
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
Click to expand...
Click to collapse
You know there is already a flash for this and an apk.
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
deathsquad737 said:
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
Click to expand...
Click to collapse
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
tech_head said:
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
Click to expand...
Click to collapse
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
deathsquad737 said:
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
Click to expand...
Click to collapse
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
tech_head said:
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
Click to expand...
Click to collapse
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
deathsquad737 said:
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
Click to expand...
Click to collapse
I can always get you a copy of the file.
tech_head said:
I can always get you a copy of the file.
Click to expand...
Click to collapse
Yes please I pm you
A.L.B/E.B.B
Thank you but...
First of all, thanks for the post. Although I appreciate the helpful post, my phone is now stuck in boot loop . I hate to be the one to open up an old thread but I'm freaking out at the moment due to brick fever :crying: My current setup was a rooted LG G3 VS98512b. My goal was simple, I didn't want to do anything crazy, I just wanted to enable wifi tether now I'm afraid I've lost everything... Is there a way I can get back into the storage of my phone and delete the modified build.prop, remove the ".bak" from the original and be back to the good life? Any assistance is greatly appreciated, this seemed like such a simple modification that led to such a big headache.
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
trent999 said:
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
soundmasterx said:
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
Click to expand...
Click to collapse
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Digital_MD said:
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Click to expand...
Click to collapse
Again, thank you for the response. Do you recommend a specific method or tutorial for trying restore the original build.prop? I did search however, because this scenario is so specific I'm not sure there is an exact solution to my problem.
Again, just in case someone else can chime in, I followed the instructions on the first post of this thread (see first post for detailed info). I copied the original build.prop then changed the name of the original build.prop, edited the copy, moved it to the original directory and restarted the phone. Now my phone doesn't make it to the Verizon screen (I think it is stuck in boot loop), the screen stays black and the small led on the left corner flashes blue and green. If I can just get access to the storage I can replace the modified build.prop with the original that is still in the same directory just renamed. It seems like such an easy task but, I just don't know how to go about it I'm a somewhat of an old school tinker, I'm just now getting back into the swing of Android... Thanks in advance!!
Bump
Bump please
This is crazy... I changed 2 values in build.prop for tethering and my phone wont boot now... I didnt install a ROM, change DPI, or make any major changes WTF???
Do you have a custom recovery (twrp)?
Can you connect to your phone with adb?
If you have twrp, search the board for the startup hardware key sequence to reach twrp, else from adb do a reboot recovery.
In twrp, you can select to mount system, then go to advanced - file manager. You can delete the bad build.prop, rename the good one, then set the permissions on the good one. If your good copy of build.prop is on a PC, put it on a flash drive, and use twrp's file manager to get it into your phone.
If you have a saved copy of build.prop on your PC, you can also use adb's push command. (You may also want to look at the adb shell command. The sequence might be to open a shell, delete the bad build. prop, get the right build.prop into the right directory, then chmod the right build.prop so it has the proper permissions.)
Has anybody successfully been able to do anything with the /system/priv-app/NvCustomize/ app?
I have tried, but even moving the folder to a different place and putting it back without any modification renders it corrupt.
Any idea how to tackle this? I hate the ugly background. I had to disable this app to at least have the Google Leanback wallpaper. But since it's probably just a matter of changing the wallpaper image in the NvCustomize.apk file (which I found), it should be possible to replace it with any image you want.
Does anybody have a clue as to why it won't work?
EDIT: I got it to work. I had to set the read/write permissions to the appropriate 644 setting.
So for anyone trying to change their default wallpaper: Replace the nv_wallpaper.png from within the /system/priv-app/NvCustomize/NvCustomize.apk file to your desired wallpaper with the same name. (And maybe best to keep the same dimensions (1920x1080) for performance reasons.
If you use an file browser that can browse from within an apk, then you should only have to copy the new nv_wallpaper.png file inside the right folder in the apk. Permissions should stay intact. Overwrite the file of course.
If you first extract the apk to modify it on your pc or somewhere else, make sure you set permissions of the apk back to 644.
mr-tee said:
Has anybody successfully been able to do anything with the /system/priv-app/NvCustomize/ app?
I have tried, but even moving the folder to a different place and putting it back without any modification renders it corrupt.
Any idea how to tackle this? I hate the ugly background. I had to disable this app to at least have the Google Leanback wallpaper. But since it's probably just a matter of changing the wallpaper image in the NvCustomize.apk file (which I found), it should be possible to replace it with any image you want.
Does anybody have a clue as to why it won't work?
EDIT: I got it to work. I had to set the read/write permissions to the appropriate 644 setting.
So for anyone trying to change their default wallpaper: Replace the nv_wallpaper.png from within the /system/priv-app/NvCustomize/NvCustomize.apk file to your desired wallpaper with the same name. (And maybe best to keep the same dimensions (1920x1080) for performance reasons.
If you use an file browser that can browse from within an apk, then you should only have to copy the new nv_wallpaper.png file inside the right folder in the apk. Permissions should stay intact. Overwrite the file of course.
If you first extract the apk to modify it on your pc or somewhere else, make sure you set permissions of the apk back to 644.
Click to expand...
Click to collapse
I know this is old, but do you need root for this?
bradleyw801 said:
I know this is old, but do you need root for this?
Click to expand...
Click to collapse
yes you need root privileges to do this
jionny said:
yes you need root privileges to do this
Click to expand...
Click to collapse
Do you know if I can change the mouse cursor the same way while I am in there?
bradleyw801 said:
Do you know if I can change the mouse cursor the same way while I am in there?
Click to expand...
Click to collapse
Sorry no, but a great source of information on the shield is...https://forums.geforce.com/default/board/159/shield-tv/
Hmm I tried replacing the wallpaper with WinRAR, 7Zip, and X-plore and all led to android saying the file appears to be corrupt. Permissions were changed back to 644 everytime. Has anyone succeeded in this and can confirm the above steps? Doesn't appear to work for me.
Believe it or not I'm looking for the original poly wallpaper. It's nowhere online. Even searched nv_wallpaper.png