Database Users

List of unsolved registery tweaks. Need help.

Ok a lot of fun can be discovered from changing registry entries and seeing what they can do. Here is a small guide:
If an entry has a 0 it means it is disabled or off. If it has a 1 it means it is enabled or on.
Remember and make a note of any change you make in case you need to put it back.
Search for common words in the entries and see what they relate to and if they can be changed Eg:
disable, enable, show, hide, lsk, sms, boost, cache, icon etc. Go through each one. Make any changes you want based on logic of the entry and reset maybe. Go to the app where you would expect to see the change and see if your tweak has worked. If not change the reg back again.
Report back here any discoveries or potential discoveries you come across and maybe we can give advice on what should be changed in the reg entry.
Be in the frame of mind you may need to do a hard reset as a last resort so back up PIM first.
I will make a list of new potential tweaks soon and maybe someone could advise on how we can change it. Any changes found will be added to the hints and tips thread.

Here are a few to get started. Please respond with ideas if you can help and submit your own findings too.
1. HKCU\Software\HTC\WebSnapShot
Enabled currently set to 0.
Which app would use this if we enabled it?
2. HKLM\Drivers\BuitIn\GSensor
EnableShaking currently set to 0.
Sounds useful somewhere.
3. HKLM\Services\MyPhoneService
IsEnabled currently set to 1.
If we disable this if we don't use MyPhone will this free up some services/resources/memory?
4. HKLM\Software\HTC\Camera\Common
DisableCapAnimation currently set to 1.
I presume this means some sort of caputre animation when taking a photo (like the iphone when the iris closes). I tried setting this to 0 to enable it but saw no animation when I took the photo. Maybe something else needs to be done.
5. HKLM\Software\HTC\HTCMessaging
DisableCacheWhenLengthierMessage currently set to 1.
This mean cache is off with long sms messages. If we turned on cache would this be good?
6. HKLM\Software\HTC\HTCMessaging
ManilaEntry currently set to 0.
I set this to 1 but could not find any change. Maybe I am looking in the wrong place.
7. HKLM\Software\HTC\HTCSettings_Improvement
HavePersonalSecurity currently set to 0.
I have set this to 1 and a new option suddenly appears in the Manila Settings tab below About Phone option. It is ABPS, ISP, network location service (Personal Info Center). However tapping on it does not open it up. Hmmmm...
8. HKLM\Software\Tegic\T9
Prediction is currently set to 0.
I thought T9 prediction is already part of it? What could this do if we turned it on?
9. HKLM\Services\Windows Live\Plugins\Mail
Max Mail Headers currently set to 50.
Dy defualt Hotmai only downloads the last 50 messages. I tried changing this entry to 75 but no luck. Anyone else?

Anyone want to get involved? I think it could be a good challenge and we may discover a gem of a tweak.

Attention: Found Unusual Registry within T-Mobile USA HD2!

I was just viewing various system registry... and came across some keys that I've never before noticed in the past.
They really aren't too outlandish, but I'm wondering if folks are interested in "testing" what exactly these registry edits "do" in terms of whether or NOT they are enhancements or NOT much of anything.
DO NOT ATTEMPT TO MAKE ALTERATIONS TO THE SYSTEM REGISTRY IF YOU ARE NOT FAMILIAR WITH ADVANCED WINDOWS MOBILE CAPABILITIES!
Now, having said all of that... here are a few of those interesting "tweaks" I've come across:
1.) HKEY_CURRENT_USER\ControlPanel\Keybd: WM7KeybdLayout - "0"
By default this registry value is ZERO... perhaps if "enabled" by using "1" as the replacement value, something "cool" may happen.
2.) HKEY_CURRENT_USER\ControlPanel\Gestures\Touch: Disabled - "0"
By default this registry value is ZERO... and I'm not entirely sure what this COULD allow your system to do, but it may be "cool" also.
3.) HKEY_CURRENT_USER\Performance: Available RAM on boot - "327274496"
By default this registry value is LIST ABOVE, and perhaps editing this value, and making it larger could allow for a more "hasty" booting process.
4.) HKEY_CURRENT_USER\Software\HTC\WebSnapShot: Enabled - "0"
By default this registry value is ZERO... but I'm wondering if this will allow for some kind of built-in screen shot function to "snap" thumbnail images of your online browsing history. Assumed value to "enable" it, should be "1".
5.) HKEY_CURRENT_USER\Software\Microsoft\Shell: AnalogClock - "0"
By default this registry value is ZERO... so I figure changing this value to "1" might "create" some kind of analog clock on for Manila.
6.) HKEY_CURRENT_USER\Software\Microsoft\Shell: HasKeyboard - "0"
By default this registry value is ZERO... and to be quite honest, this seems pretty obvious that it will "allow" or display the keyboard somewhere on the "shell" of your device. Assumed value to "enable" it, should be "1".
7.) HKEY_CURRENT_USER\ControlPanel\BackLight
This ENTIRE key has some pretty interesting settings that can be adjusted for advanced or unseen backlight settings.
8.) HKEY_CURRENT_USER\ControlPanel\AllLEDMgr
Here is the key in which you can adjust the LED settings such as interval.
9.) HKEY_LOCAL_MACHINE\Audio\SoftwareMixer: SampleRate - "268435456"
The default value is listed above, but my query involves whether or not tampering with this could resolve the "audio delay" for some users.
10.) HKEY_LOCAL_MACHINE\ControlPanel\Power
Here is the key in which you can adjust the values to be labeled for battery power settings. HIGH, MEDIUM, and LOW. The percentage before the system provides a warning can be changed.
11.) HKEY_LOCAL_MACHINE\Drivers\Display
Here is the key in which you will find a majority of your advanced display settings for your device.
12.) HKEY_LOCAL_MACHINE\Software\Qualcomm\DSM
Here is the key in which I believe you might find another possible solution for the audio delay, considering one of the string values is "250" as a file queue setting.
13.) HKEY_LOCAL_MACHINE\Software\OEM\USBtoPC
Here is the key in which you'll find the way to REMOVE or otherwise disable the "popup" window that appears whenever you connect your device via USB to a desktop PC.
14.) HKEY_LOCAL_MACHINE\Software\OEM\MASD
THIS KEY, THIS KEY RIGHT HERE FOLKS... this is VERY important for those of you who are trying to figure out what "official" version number of specific services is currently installed on your device.
15.) HKEY_LOCAL_MACHINE\Software\Microsoft\ActiveSync\OEM Links\T-Mobile Help - "0"
Enabling this key by changing the value to "1" should provide for a direct system link to the T-Mobile support network for the HD2. This is very similar to the Microsoft error reporting services.
16.) HKEY_LOCAL_MACHINE\Software\Microsoft\Calendar: ShowLunarCalendar - "0"
By enabling this, you should be able to have the Lunar Calendar displayed within the HTC system calendar... among other things. Assumed value to "activate" this should be "1".
17.) HKEY_LOCAL_MACHINE\Software\Microsoft\CHome
Here is where you'll find a laundry list of options to make changes to the original WM6.5, "Titanium".
18.) HKEY_LOCAL_MACHINE\Software\Microsoft\Pictures\ImageSendSize
Here is where you'll find 3 sub-keys that contain resolution values that can be altered in order to provide a "bigger picture" for MMS or uploads.
19.) HKEY_LOCAL_MACHINE\Software\HTC\Camera\Image
This key will open up a list of options that will allow you to change various settings for image capture and resizing.
20.) HKEY_LOCAL_MACHINE\Software\HTC\PhoneCanvas
In this key you'll find options that will allow you to make changes to the picture size for contacts.
21.) HKEY_LOCAL_MACHINE\Software\HTC\PHONE
Here are more device settings for in-call and beyond.
ENJOY!
Oh, and don't hesitate to leave a bit of feedback. Thanks.

I am patiently waiting for you to try these and update the post.
I sure as heck don't plan to "play" with my registry

As soon as the store calls to tell me that mine is *FINALLY* in, I'll be happy to test some of those out. As long as you back up your registry before you do anything (and aren't afraid of a Hard Reset as a last resort), there shouldn't be any issue trying these...any of the changes you make can be reversed that way.

Snarksneeze said:
I am patiently waiting for you to try these and update the post.
I sure as heck don't plan to "play" with my registry
Click to expand...
Click to collapse
sirphunkee said:
As soon as the store calls to tell me that mine is *FINALLY* in, I'll be happy to test some of those out. As long as you back up your registry before you do anything (and aren't afraid of a Hard Reset as a last resort), there shouldn't be any issue trying these...any of the changes you make can be reversed that way.
Click to expand...
Click to collapse
Agreed fellas. This stuff seems interesting. I haven't played with these listed items just yet. I was so exhausted last night while skimming through tons and tons of registry keys... that I may have gotten a little desperate to post this rather than test each one.
Some are just useful tips, but others I have not before seen on the EURO model of the HD2. For instance, the WM7 keyboard... that's rather curious, huh?

5 - puts tiny analog clock where digi clock is by battery
6 - for phones with hardware keyboards
14 - can change that to fake any system info you like
18 - doesnt necessarily work. best way ive yet to find to fix the small mms size on some networks is the mms userprofile tweak that reports it as a diamond, and the mms useragent as a nokian95. (I can tfind the link, sorry)

3.) HKEY_CURRENT_USER\Performance: Available RAM on boot - "327274496"
By default this registry value is LIST ABOVE, and perhaps editing this value, and making it larger could allow for a more "hasty" booting process.
When I looked I had a lower value, "281640960". I increased it to "327274496" startup seems a bit faster, not much. I'm gonna try increasing it later. On another note, slide to unlock seems to be faster. Of course this could all be in my head.

chrys9989 said:
3.) HKEY_CURRENT_USER\Performance: Available RAM on boot - "327274496"
By default this registry value is LIST ABOVE, and perhaps editing this value, and making it larger could allow for a more "hasty" booting process.
When I looked I had a lower value, "281640960". I increased it to "327274496" startup seems a bit faster, not much. I'm gonna try increasing it later. On another note, slide to unlock seems to be faster. Of course this could all be in my head.
Click to expand...
Click to collapse
This looks suspiciously like overclocking to me. If it is, I doubt that the S2U being faster is in your head...
Are you sure that "on boot" only means during the bootup process and not the original RAM available before the processes kick in?

Snarksneeze said:
This looks suspiciously like overclocking to me. If it is, I doubt that the S2U being faster is in your head...
Are you sure that "on boot" only means during the bootup process and not the original RAM available before the processes kick in?
Click to expand...
Click to collapse
What's weird though is that the value keeps changing, on every boot it's a different value. On the last boot, it was 280760320.

chrys9989 said:
What's weird though is that the value keeps changing, on every boot it's a different value. On the last boot, it was 280760320.
Click to expand...
Click to collapse
Then it just about has to be a record and not reference value. Shoulda known it wouldn't be that easy

samsamuel said:
5 - puts tiny analog clock where digi clock is by battery
6 - for phones with hardware keyboards
14 - can change that to fake any system info you like
18 - doesnt necessarily work. best way ive yet to find to fix the small mms size on some networks is the mms userprofile tweak that reports it as a diamond, and the mms useragent as a nokian95. (I can tfind the link, sorry)
Click to expand...
Click to collapse
chrys9989 said:
What's weird though is that the value keeps changing, on every boot it's a different value. On the last boot, it was 280760320.
Click to expand...
Click to collapse
Thanks for the reports.
And yeah, I noticed that as well... yet my value is always relatively in the same demographic in terms of "high" or "low".
But yes, it is some "lowbrow" version of overclocking, but as far as I know... it only pertains to the RAM available during and shortly thereafter a booting process is complete. It's like tweaking the allocated resources that "HTC Sense" used each time it booted up.

Awesome find. looking forward to what will be unconvered

I have a few friends skimming the registry keys day n' night as well... it's just very, very exhausting to read thousands of lines of coding.
I doubt I'll be updating the OP with tons of additions, but I'll certainly add to it, should something reasonably decent come to my attention.

I would like to add something that also seems interesting
HKLM/System/Autoupdate: 0 <-- I wonder what 1 does.. I just set to 1, will update as i hopefully receive updates
PS: I'm not sure if its this that caused this, but my phone just locks on slide to unlock.. As soon as i try unlocking the screen turns off.

Reignzone said:
I have a few friends skimming the registry keys day n' night as well... it's just very, very exhausting to read thousands of lines of coding.
I doubt I'll be updating the OP with tons of additions, but I'll certainly add to it, should something reasonably decent come to my attention.
Click to expand...
Click to collapse
Bump.
Anyone found any interesting tidbits as of yet?

[Q] change live wallpaper with tasker

hi all,my question is:
is there a way to change live wallpaper using the app tasker?
for example have a live wallpaper for when i use n7 at home and one different for when i use in car.

furious84 said:
hi all,my question is:
is there a way to change live wallpaper using the app tasker?
for example have a live wallpaper for when i use n7 at home and one different for when i use in car.
Click to expand...
Click to collapse
I've found solution! :3
This command sets live wallpaper¹:
Code:
service call wallpaper 2 i32 1 s16 "[package name]" s16 "[class name]"
This command allows to get name of active live wallpaper:
Code:
service call wallpaper 4
And this command disables it:
Code:
service call wallpaper 5
More details here²:
android/app/IWallpaperManager.java
com/android/server/WallpaperManagerService.java
¹ Application must have SET_WALLPAPER_COMPONENT permission, and this permission available only for applications from /system/. So, in your case you need superuser privileges.
² There were links to source code, but xda doesn't allow me to post it. You can found it yourself — just search "grepcode [filename]" in google.
Sorry for my english.

4ufak said:
I've found solution! :3
This command sets live wallpaper¹:
Code:
service call wallpaper 2 i32 1 s16 "[package name]" s16 "[class name]"
This command allows to get name of active live wallpaper:
Code:
service call wallpaper 4
And this command disables it:
Code:
service call wallpaper 5
More details here²:
android/app/IWallpaperManager.java
com/android/server/WallpaperManagerService.java
¹ Application must have SET_WALLPAPER_COMPONENT permission, and this permission available only for applications from /system/. So, in your case you need superuser privileges.
² There were links to source code, but xda doesn't allow me to post it. You can found it yourself — just search "grepcode [filename]" in google.
Sorry for my english.
Click to expand...
Click to collapse
Really Thank You very much, sincerelly i decided To use Car home ultra like home when n7 is plug in Car (then i didn t need wallpaper, But i will try.
Ps your English is better then mine. I m from italy, And you?
Inviato dal mio Nexus 7 utilizzando Tapatalk

Here's the script (.txt, because it is a very strange forum). Without arguments script disables live wallpapers, overwise sets livewallpaper - first arguments is package name, second is class name. For example:
Code:
/data/lwmgr.sh com.h6ah4i.android.music_visualizer2 com.h6ah4i.android.music_visualizer_wallpaper.MusicVisualizerWallpaperService
Don't forget to copy script into right place and set right permissions.
View attachment lwmgr.txt

furious84 said:
Really Thank You very much, sincerelly i decided To use Car home ultra like home when n7 is plug in Car (then i didn t need wallpaper, But i will try.
Ps your English is better then mine. I m from italy, And you?
Inviato dal mio Nexus 7 utilizzando Tapatalk
Click to expand...
Click to collapse
It's my pleasure, glad to help. I'm from Russia. :3

Basic understanding of shell and Tasker
I really would like to get Live Wallpaper switching to work. I tried entering the txt into the shell but it doesn't work or return the correct values. Could you help me out?

I found this solution really good until kitkat , but now with lollipop does not work anymore , someone is able to change the codes ? I use a rom based cm now but I tried it with the stock without any results .
knows maybe an alternative method ?
thanks for any help

quack75 said:
I found this solution really good until kitkat , but now with lollipop does not work anymore , someone is able to change the codes ? I use a rom based cm now but I tried it with the stock without any results .
knows maybe an alternative method ?
thanks for any help
Click to expand...
Click to collapse
Have you found a way for Lollipop yet?

JudgeDread11 said:
Have you found a way for Lollipop yet?
Click to expand...
Click to collapse
At least only with paid app and rooted phone, search Automagic, it work for my N4 with any Rom [emoji3]

The evaluation version doesn't work for me on lollipop. I didn't take to much time to look into it though since u found an other solution. The LW I use has its own ui so starting that and only 2 tasker input button clicks it sets it. Not a nice solution as the screen needs to come on and user input can disturb the action. But to have an other app running for just this purpose isn't a great solution too. Especially since I want to disabled my LW to save battery when it gets low.
---------- Post added at 07:34 AM ---------- Previous post was at 07:30 AM ----------
Hopefully somebody with more knowledge about these things then me will figure out three correct command line for lollipop and post it here

Lollipop fix
If that isn't working on new versions like lollipop try just changing the 2 to a 3: service call wallpaper 3.. The addition of a function to set the keyguard wallpaper bumped it down to 3.

how do you make it work on nougat?
it's throwing an "error: 10" at the end of the shell command. it does work on my old phone ( kitkat )
i've tried with both 3 as well as 2 and both give the error: 10
this is the last 3 lines of the output text.
add wait type shell1 done
add wait task
Error: 10
any ideas how to make it work ?

Not working on Samsung Galaxy Note 8 on Nougat 7.1.1 rooted
Hello,
I was using Tasker in my rooted Elephone running on android Marshmallow for automatically changing the live wallpaper on 'time+date'schedule using RUN SHELL command as described in this forum successfully.
Now I bought Samsung Galaxy Note 8 on Nougat 7.1.1 Stockrom, rooted using TWRP< superSU. Tasker has been granted SuperSU permission also. I have exported my tasker profiles from Elephone to Sansung, also it shows green lines at the end of each task. it fails to execute the task .I am very much disappointed. This is the only way to automate live wallpaper changing in Android.
So kindly help me how to solve this problem.
Thanking You
drsaidalavi

citkast said:
If that isn't working on new versions like lollipop try just changing the 2 to a 3: service call wallpaper 3.. The addition of a function to set the keyguard wallpaper bumped it down to 3.
Click to expand...
Click to collapse
Yeah! It's working on OnePlus 5T with OxygenOS beta 33 (pie).
Using Livewallaper Betta Fish:
Code:
service call wallpaper 3 i32 1 s16 "com.maxelus.livewallpaper.betta" s16 "com.maxelus.livewallpaper.betta.LiveWallpaperService"

Hello? I've tried doing the same things...
Just to test.... I have set that if I shake my device I want to change the Live Wallpaper (Magic Fluids)
But it's not working...
What I truly want is:
1) if my device is in landscape mode → change live wallpaper to "Transparent Screen LWP"
2) if my device is in Portrait mode → change live wallpaper to "Magic Fluids"
Please help ???

How to change live walpaper as per schedule in Oreo
aashir.s.shaikh said:
Hello? I've tried doing the same things...
Just to test.... I have set that if I shake my device I want to change the Live Wallpaper (Magic Fluids)
But it's not working...
What I truly want is:
1) if my device is in landscape mode → change live wallpaper to "Transparent Screen LWP"
2) if my device is in Portrait mode → change live wallpaper to "Magic Fluids"
Please help
Click to expand...
Click to collapse
.
Here I will detail how I set up the automatic change of live wallpaper using Tasker. It can work only in rooted phone either by Magisk or SuperSu
First you have to install two applications from Play store
1-' Application Information'- to get the Package name of live wallpapers you have already installed
2- 'Disable service- to get the service name of the wallpaper. Some live wallpapers have more than one service name. The one comes with Wallpaper'in the last liine will be the one we have to enter in the Run Shell command. The other way to find it is just deselect the tick mark one by one in Disable service, then look for the disappearance of that live wallpaper from the live wallpaper picker screen. The service causing the disappearance is what we want to enter in the Run Shell command
Set up a profile - Name it -for Example LWC
then select 'EVENT'- select Date and time set- then it will ask for a task
Name the Task eg: Live wallpaper
Then it opens Task Edit
Select -RUN SHELL-
Put the following command in the Run Shell
service call wallpaper 5 i32 1 s16 ---------------------------- s16 --------------( fill the first dash area the package name you are copying from The Application Information APk, and the second one the service package obtained from the Disable Service Apk as described above. This number '5'is for Oreo rom, if you go downwards to Nougat make it '4', if you go above to Pie make it '6'.)
You have tick the root option in the next line
Then in then ' If', choose what variables you want to choose. As I choose date and time , I selected ' Day of the month' for the first variable then' equals' to the number of the day of the month eg:1 for the first day
Then again press the plus button of the variable, selected 'Time' made it 'greater than' -then put the time in this format- 09.00 for nine o' çlock in the morning. Tasker will only accept the time in 24 hour format
Those who have finger print or pattern lock, this may not work properly when the display off and phone locked. To make this work in this condition, we have to make another 2 profiles
Name of profile -anything you like- select State- Display -Display state edit- make it off
then add the task we already created eg: Live wallpaper in the this prfile
Make another profile- Name it- then select ' Event'- then 'Monitor'- then select the task 'live wallpaper changer
If you set up all these profile , you can see your live wallapapers changing according to a schedule you created.
Thank you
drsaidalavi

seems all solutions here didn't work anymore on Android 11 R! Anyone knows a new working solution?

Still no solution found yet..

Volume Steps Adjustment

I don't find any "ro.config.vc_call_vol_steps=......" or "...... music_vol_steps=....." settings in the A7 build.prop.
I added these lines to my build.prop to increase the steps from the default (which appears to be 7) to 30, but saw no change after reboot.
Is anyone aware of where the size of the volume steps is set, so I might make the steps smaller in adjustment?
Thanks

amphi66 said:
I don't find any "ro.config.vc_call_vol_steps=......" or "...... music_vol_steps=....." settings in the A7 build.prop.
I added these lines to my build.prop to increase the steps from the default (which appears to be 7) to 30, but saw no change after reboot.
Is anyone aware of where the size of the volume steps is set, so I might make the steps smaller in adjustment?
Thanks
Click to expand...
Click to collapse
Try and see if ro.config.media_vol_steps and ro.config.vc_call_steps works for you.

razorblader said:
Try and see if ro.config.media_vol_steps and ro.config.vc_call_steps works for you.
Click to expand...
Click to collapse
Tried it as you typed and also ro.config.vc_media_steps=30
but neither made a difference. I suspect it is set somewhere in the SystemUI where I don't have access.
Thanks

amphi66 said:
Tried it as you typed and also ro.config.vc_media_steps=30
but neither made a difference. I suspect it is set somewhere in the SystemUI where I don't have access.
Thanks
Click to expand...
Click to collapse
Thanks for the feedback, was gonna try this as well once I'll root my phone.

amphi66 said:
I don't find any "ro.config.vc_call_vol_steps=......" or "...... music_vol_steps=....." settings in the A7 build.prop.
I added these lines to my build.prop to increase the steps from the default (which appears to be 7) to 30, but saw no change after reboot.
Is anyone aware of where the size of the volume steps is set, so I might make the steps smaller in adjustment?
Thanks
Click to expand...
Click to collapse
If you want to, you can use gravity box to change it.

amphi66 said:
Tried it as you typed and also ro.config.vc_media_steps=30
but neither made a difference. I suspect it is set somewhere in the SystemUI where I don't have access.
Thanks
Click to expand...
Click to collapse
I've just tested this on B08 rooted and it works are you sure you've disabled system write protection so that your build.prop changes survive a reboot?

razorblader said:
I've just tested this on B08 rooted and it works are you sure you've disabled system write protection so that your build.prop changes survive a reboot?
Click to expand...
Click to collapse
I'm good there.
Thinking back tho, I only checked the ring tone steps from the home page (and that wasn't one of the volume adjustments made), so very like that build.prop edit DID work for what it was set for. I'll try again.
BTW, did you use the "media" or "music" entry?

amphi66 said:
I'm good there.
Thinking back tho, I only checked the ring tone steps from the home page (and that wasn't one of the volume adjustments made), so very like that build.prop edit DID work for what it was set for. I'll try again.
BTW, did you use the "media" or "music" entry?
Click to expand...
Click to collapse
'media' as the 'music' variant doesn't seem to work on newer iterations of Android any more.
ro.config.media_vol_steps=80
ro.config.vc_call_vol_steps=40
These settings work for me.

I just found this thread and I'd like to make this change on my phone too.
I find my phone has to go up to about 80% max volume before I can really hear things on the headphones/earbuds and at that point, it's only a couple clicks away from max volume.
I'm not very familiar with Android stuff yet, so could somebody provide me with some very basic step-by-steps on how to do this or where to find the file to change?
My phone is the US version, running B20 with locked BL but is rooted.

mozerxdaven said:
I just found this thread and I'd like to make this change on my phone too.
I find my phone has to go up to about 80% max volume before I can really hear things on the headphones/earbuds and at that point, it's only a couple clicks away from max volume.
I'm not very familiar with Android stuff yet, so could somebody provide me with some very basic step-by-steps on how to do this or where to find the file to change?
My phone is the US version, running B20 with locked BL but is rooted.
Click to expand...
Click to collapse
The suggestions in this thread only change the increments between volume steps, NOT overall volume. Good luck!

amphi66 said:
The suggestions in this thread only change the increments between volume steps, NOT overall volume. Good luck!
Click to expand...
Click to collapse
Yes, I understand this only changes the increments, but I would still like to find out how to make the change so I can have finer-grained control of the volume, even at higher levels.

mozerxdaven said:
Yes, I understand this only changes the increments, but I would still like to find out how to make the change so I can have finer-grained control of the volume, even at higher levels.
Click to expand...
Click to collapse
It's pretty straight forward since you are rooted: use a File Manager & Text Editor to add the lines below to /system/build.prop Save & then reboot. Your option as to the number of steps.
It is always good practice to make a nandroid backup prior to making changes to give you a recovery point in the event of a mistype or other error. Goodluck
ro.config.media_vol_steps=30
ro.config.vc_call_vol_steps=30

amphi66 said:
It's pretty straight forward since you are rooted: use a File Manager & Text Editor to add the lines below to /system/build.prop Save & then reboot. Your option as to the number of steps.
It is always good practice to make a nandroid backup prior to making changes to give you a recovery point in the event of a mistype or other error. Goodluck
ro.config.media_vol_steps=30
ro.config.vc_call_vol_steps=30
Click to expand...
Click to collapse
I did as suggested but it didn't seem to change anything for me.
I had to use the command to unlock system file changes first, because the change wasn't sticking after reboot at first.
I put those 2 lines at the bottom of the /system/build.prop file
Is it working properly on your phone?
Edit:: Scratch that, i was looking at the ringtone slider rather than the media/apps volume control.
Thank you!

mozerxdaven said:
I did as suggested but it didn't seem to change anything for me.
I had to use the command to unlock system file changes first, because the change wasn't sticking after reboot at first.
I put those 2 lines at the bottom of the /system/build.prop file
Is it working properly on your phone?
Edit:: Scratch that, i was looking at the ringtone slider rather than the media/apps volume control.
Thank you!
Click to expand...
Click to collapse
Yep, changing ringtone steps is tougher. It takes an edit of a System UI .jar file or the use of an Exposed Module.
Glad these worked for you!

[DEPRECATED] Night Light on Nexus 5x/6P Android O

Hey all,
So I'd like to share my discovery with all of you.
Yesterday I was playing around with my Rooted Nexus 5x on Android O DP2 and later found that I activated Night Light in Settings>Display.
The requirements are:
A rooted Nexus 5x/6P on Android O
Pixel Theme placed in vendor/overlay
Developer Options enabled
Steps:
What you want to do is:
1. Add the Pixel theme to vendor/overlay (there are a lot of articles online for this)
2. Change your smallest width in Developer Options to 450.
3. Activate the Pixel theme in Settings>Display>Advanced>Theme
4. Voila
Why does it work?
I honestly don't know if I were to take a guess, it would be that the combination of Pixel theme and DPI trigger the software to think it's a Pixel, but again, just a guess...
I am attaching screenshots of everything and also the overlay file I used, please report back whether it worked or not!
Cheers!

Interesting! Since its already there, we should be able to trigger it without root and UI.
We need figure out what it wrote to settings.
Could you dump adb output of these 3 command, try to filter out key and value related to night mode.
I check mine and could not find one, perhaps it never existed since I never had a chance to access it yet.
Code:
adb shell settings list system
adb shell settings list global
adb shell settings list secure
Then we should be able trigger Night Light using app that can write custom key to settings like AutoTools.
Maybe one time adb command is need to grant the app permission to write secure settings depend on where the value is stored.
Developer can write an app for the switch. Better yet, Night Light quick settings tile!!
EDIT: You may also placed the Night Light tile on Quick Settings, check values of 'sysui_qs_tiles' under secure settings list.
We might be able to just add Night Light tile there using adb command.

HebeGuess said:
Interesting! Since its already there, we should be able to trigger it without root and UI.
We need figure out what it wrote to settings.
Could you dump adb output of these 3 command, try to filter out key and value related to night mode.
I check mine and could not find one, perhaps it never existed since I never had a chance to access it yet.
Code:
adb shell settings list system
adb shell settings list global
adb shell settings list secure
Then we should be able trigger Night Light using app that can write custom key to settings like AutoTools.
Maybe one time adb command is need to grant the app permission to write secure settings depend on where the value is stored.
Developer can write an app for the switch. Better yet, Night Light quick settings tile!!
EDIT: You may also placed the Night Light tile on Quick Settings, check values of 'sysui_qs_tiles' under secure settings list.
We might be able to just add Night Light tile there using adb command.
Click to expand...
Click to collapse
Night light is enabled by changing the bool value from false to true in the bool.xml in framework-res.apk/res/values/bool.xml/<bool name="config_nightDisplayAvailable">true</bool>

Tulsadiver said:
Night light is enabled by changing the bool value from false to true in the bool.xml in framework-res.apk/res/values/bool.xml/<bool name="config_nightDisplayAvailable">true</bool>
Click to expand...
Click to collapse
Arghh, totally forgot about this. They likely only start laying ground works for this kind of overlay capability around N-O (quite fresh).
Probably in-preparation for Project Treble, make it easier for OEM to configure devices. Forgo the need of modify main framework for each device.
However, I just did a quick look inside overlay apks posted above. They are no night light related strings laying around, good news for us.
As of O, our main framework-res should be the same as Pixels. This is the reason they made overlay like this.
Nevertheless, whatever detection mechanism they using for Night Light detection. There are using switch and intensity slider in settings mean they will be save inside settings provider.
We can hook onto it.
The method you mentioned was used in N, they modified that value for each device.

Tulsadiver said:
Night light is enabled by changing the bool value from false to true in the bool.xml in framework-res.apk/res/values/bool.xml/<bool name="config_nightDisplayAvailable">true</bool>
Click to expand...
Click to collapse
Apktool 2.2.2 not working as of now in compiling Android O framework.apk... so how can you change the value ?

Tulsadiver said:
Interesting! Since its already there, we should be able to trigger it without root and UI.
We need figure out what it wrote to settings.
Could you dump adb output of these 3 command, try to filter out key and value related to night mode.
I check mine and could not find one, perhaps it never existed since I never had a chance to access it yet.
Night light is enabled by changing the bool value from false to true in the bool.xml in framework-res.apk/res/values/bool.xml/<bool name="config_nightDisplayAvailable">true</bool>
Click to expand...
Click to collapse
So I did that and only found Night Light related details in secure, I'm attaching all three complete-non filtered files!

HebeGuess said:
Interesting! Since its already there, we should be able to trigger it without root and UI.
We need figure out what it wrote to settings.
Could you dump adb output of these 3 command, try to filter out key and value related to night mode.
I check mine and could not find one, perhaps it never existed since I never had a chance to access it yet.
Then we should be able trigger Night Light using app that can write custom key to settings like AutoTools.
Maybe one time adb command is need to grant the app permission to write secure settings depend on where the value is stored.
Developer can write an app for the switch. Better yet, Night Light quick settings tile!!
EDIT: You may also placed the Night Light tile on Quick Settings, check values of 'sysui_qs_tiles' under secure settings list.
We might be able to just add Night Light tile there using adb command.
Click to expand...
Click to collapse
So I shared all three files in the post above, I'm quoting you so you'd get notified! Cheers!

So did it work for y'all too?
I'm on Telegram too, very active there, if you have any doubts hit me up and mention you came from here so that I don't Spam Report ???
Telegram ID: @Anirudhgupta109

Anirudhgupta109 said:
So I shared all three files in the post above, I'm quoting you so you'd get notified! Cheers!
Click to expand...
Click to collapse
Thanks, those values store inside 'secure settings'.
I tried manually insert them into settings, actually got settings app displayed 'Night Light On' message.
Night Light itself is not working, looks like they still do some explicit check on certain conditions which your method some how have met.

HebeGuess said:
Thanks, those values store inside 'secure settings'.
I tried manually insert them into settings, actually got settings app displayed 'Night Light On' message.
Night Light itself is not working, looks like they still do some explicit check on certain conditions which your method some how have met.
Click to expand...
Click to collapse
I made a video of night light in action, couldn't upload it here so I'm sharing the GDrive link to the video
https://drive.google.com/file/d/0B_pirmux_1caa0VLODZPeU92WlE/view?usp=drivesdk
Sent from my bullhead using XDA Labs

I followed your steps, but unfortunately it doesn't seem to work.
I first extracted the theme to the folder "overlay" i created in vendor. Rebooted and applied the theme succesfully. Then opened dev option and adjusted the min width to 450, it changed to 449 automatically. Nothing happened. Rebooted but still nothing.
Anyway thanks, I will try it again later cause i loved Night Mode.

Anirudhgupta109 said:
Hey all,
So I'd like to share my discovery with all of you.
Yesterday I was playing around with my Rooted Nexus 5x on Android O DP2 and later found that I activated Night Light in Settings>Display.
The requirements are:
A rooted Nexus 5x/6P on Android O
Pixel Theme placed in vendor/overlay
Developer Options enabled
Steps:
What you want to do is:
1. Add the Pixel theme to vendor/overlay (there are a lot of articles online for this)
2. Change your smallest width in Developer Options to 450.
3. Activate the Pixel theme in Settings>Display>Advanced>Theme
4. Voila
Why does it work?
I honestly don't know if I were to take a guess, it would be that the combination of Pixel theme and DPI trigger the software to think it's a Pixel, but again, just a guess...
I am attaching screenshots of everything and also the overlay file I used, please report back whether it worked or not!
Cheers!
Click to expand...
Click to collapse
Hi bro, can u explain me how to root nexus 5x with o dp2?

diaboliko.hacker said:
Hi bro, can u explain me how to root nexus 5x with o dp2?
Click to expand...
Click to collapse
You need to know how to flash TWRP, there's a guide by Heisenberg over here
Once in TWRP flash Magisk v13 (unofficial snapshot) and install Magisk Manager 5.
Magisk: https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
The download is on thier GitHub! Cheers!
Sent from my bullhead using XDA Labs

johnannis said:
I followed your steps, but unfortunately it doesn't seem to work.
I first extracted the theme to the folder "overlay" i created in vendor. Rebooted and applied the theme succesfully. Then opened dev option and adjusted the min width to 450, it changed to 449 automatically. Nothing happened. Rebooted but still nothing.
Anyway thanks, I will try it again later cause i loved Night Mode.
Click to expand...
Click to collapse
Did you try my overlay file? If yes, it contains the rro type too, switch between that and Pixel while on 449 smallest width (yes it switches to 449 automatically) and your screen should flicker and your settings screen should move down one row! Please let me know if it works!
Sent from my bullhead using XDA Labs

Work for me

iamaniff said:
Work for me
Click to expand...
Click to collapse
I'm glad it did!

Not working for me.
Using rooted Nexus 5X Android O DP2
I copied all files in /vendor/overlay/ folder.
I have the option to select a theme, I can select 2 themes but nothing is changing if i clock on them.
I also changed my min DPI to 449 like you said in your post.

Aragur said:
Not working for me.
Using rooted Nexus 5X Android O DP2
I copied all files in /vendor/overlay/ folder.
I have the option to select a theme, I can select 2 themes but nothing is changing if i clock on them.
I also changed my min DPI to 449 like you said in your post.
Click to expand...
Click to collapse
You're not even on Android O anymore
Sent from my bullhead using XDA Labs

Anirudhgupta109 said:
You're not even on Android O anymore
Click to expand...
Click to collapse
I am using Android O??

It works in DP3, you dont get the theming option but night light works.