I always found stock pixel color saturation to be a bit washed out. I prefer the look of more saturated color palette. Even choosing "adaptive" color on display options is still not good enough for me.
If you're rooted and want to increase color saturation do the following:
Open any Android terminal with root capabilities, I personally use Termux.
Type "su" and hit enter to grant root privileges. I don't know if it's a necessary step, but I change the directory to the root of the phone by typing "CD /". Then I copy and paste the below code into the terminal. I personally set my "x.x" to 1.25. hit enter and it will automatically take effect. You can change the values at anytime afterwards to go higher or lower. Values will go back to stock after a reboot using this method, so if you don't like it, just reboot to go back to stock values.
"service call SurfaceFlinger 1022 f X.X" (x.x sets saturation up to 2.0)
I HAVE NOT TESTED THIS, but in the past I have used this code to permanently set the saturation level on boot:
Setprop persist.sys.sf.color_saturation X.X
using this, the saturation level will remain to the chosen value on boot. Again, I have not tested this on the pixel 7 Pro.
That's interesting as I also find the "adaptive" setting too washed out on Pixels.
I wonder if this could be used through a root app with more control over colors and such?
works - thank you!
Ghisy said:
That's interesting as I also find the "adaptive" setting too washed out on Pixels.
I wonder if this could be used through a root app with more control over colors and such?
Click to expand...
Click to collapse
I'm sure it could but that's beyond my capabilities lol l
Gotta wonder what effect this might have on...everything? Battery life...screen life...brightness level adjustments when on auto? YMMV
But what can we use after
"service call SurfaceFlinger 1022 f X.X" to disable if needed ?
Attinderkahlon said:
But what can we use after
"service call SurfaceFlinger 1022 f X.X" to disable if needed ?
Click to expand...
Click to collapse
I believe 1.0 is the stock value. So you can either enter the line again and replace whatever previous value you used with 1.0, or you could just reboot the device and it'll go back to the stock saturation settings.
jaseman said:
Gotta wonder what effect this might have on...everything? Battery life...screen life...brightness level adjustments when on auto? YMMV
Click to expand...
Click to collapse
It could have a negative effect on battery life....but I would guess its minimal. Been using a custom saturation value for 2 days now, no known issues.
I haven't checked yet but going by previous devices, there is probably a way to access other color modes using tasker. "boosted" has been taken away from the menu, my guess is its still there and can be accessed with tasker. I'll check it if i keep the phone.
Thank you for this, legit the only thing driving me crazy was the dull colors now it looks more like I wanted. You da man.
Glad I could help!
Dope. Going to give this a shot whenever I decide to root.
Now, has this always been a thing? If so, I wish I knew about it so I didn't have to use apps the entire time to tweak it to my liking.
Curiousn00b said:
Dope. Going to give this a shot whenever I decide to root.
Now, has this always been a thing? If so, I wish I knew about it so I didn't have to use apps the entire time to tweak it to my liking.
Click to expand...
Click to collapse
I've been using this mod since the OnePlus 6T....so it's been a thing for a while at least for me.
Has anyone tried this? Getting a Parcel Null error when I enter the code. Rooted. That "CD /" comes back as inaccessible too. It's probably me, but not able to get this to work as of now.
Unable to set up after boot, i get the setprop inaccessible
System is read-only for now. There's no rw mount mod so can't really edit build prop to set it on boot. We'll just have to wait for twrp or any system rw mount mod
xgerryx said:
Has anyone tried this? Getting a Parcel Null error when I enter the code. Rooted. That "CD /" comes back as inaccessible too. It's probably me, but not able to get this to work as of now.
Click to expand...
Click to collapse
I get parcell null response as well but it still works.
Also, I just tested changing directory in not necessary so you can skip the "CD /" part.
Trust me on this, run the script with a value of 0.5 and hit enter. Go to your home screen, open apps and scroll through your phone. Then open your emulator again, run the script with a value of 3.0 and hit enter. Then look about your phone it will look completely different. From there, just keep messing around with different values until you get one you like.
Pain-N-Panic said:
I get parcell null response as well but it still works.
Also, I just tested changing directory in not necessary so you can skip the "CD /" part.
Trust me on this, run the script with a value of 0.5 and hit enter. Go to your home screen, open apps and scroll through your phone. Then open your emulator again, run the script with a value of 3.0 and hit enter. Then look about your phone it will look completely different. From there, just keep messing around with different values until you get one you like.
Click to expand...
Click to collapse
Ok yes I'm seeing it now. Thanks for following up. It does change exactly what we're looking for. I bet you someone can make this into a little app or a magisk module.
xgerryx said:
Ok yes I'm seeing it now. Thanks for following up. It does change exactly what we're looking for. I bet you someone can make this into a little app or a magisk module.
Click to expand...
Click to collapse
Glad ya got it working! Yeah I'm sure it's possible, having to run the script everytime you boot is kind of annoying
I wish we could adjust the white balance. This screen is so yellow looking
Related
Alright so Yesterday I installed the android os on my touch pro (raph 500)
i orginally have windows mobile 6.5 which is preety fast
but android is really slow!
i turned off all the settings which i would think it used alot of memory but still no help, so i started seeing videos on overclcking?
can someone explain to me on how to do this,
with links to the download
i really need to speed this up ,it would be amazing if it worked.
also if you give me a response that helps me , ill donate 10.00+ to you .
I do not require funds as I enjoy helping out!
From THIS thread and THIS post:
Overclocking
acpuclock.oc_freq_khz=XXXXXX ( suggested 600000-640000 )
but it is very unstable if you try to get higher than 650000-700000
Click to expand...
Click to collapse
Basically, you add that to the startup.txt file somewhere between the parentheses with an added space between the next command. Keeping in mind, with added OC, you may and may not notice a difference in stability. I honestly never use OC and I am using FroYo from THIS thread. Additionally you can try out Gingerbread Alpha from THIS thread. Please leave feedback in their respective threads, thanks!
n-Joie! (Enjoy)
thanks but this is my startup text :
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 acpuclock.force_turbo=1"
boot
Click to expand...
Click to collapse
so which am i supposed to edit, sorry im a noob lol
& u said that was the one you used,
is it fast?
Actually, I can't use that one because I have an at&t Fuze. If you have a RAPH500, you might want to use the following:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 pm.sleep_mode=1 acpuclock.oc_freq_khz=XXXXXX"
boot
Click to expand...
Click to collapse
Where XXXXXX is equal to a value between 600000-640000
Additional note: make sure you type something like 600000 or any value up to 640000
lol thanks im trying to see if theres a difference in speed.
but you used froyo?
is that running fast?
It's running fine with sync and a few other apps running in the background. I would be mindful of livewallpaper and HQ video at the moment as this project is currently still under development, at best. At least that is what I have noticed as far as performance is considered. I have also run a stripped Gingerbread alpha build (the one I linked you to earlier) and it is running faster/smoother than FroYo. To be expected without all the bells and whistles...
NOTE: Speed is relative to performance at the moment. Hence why I say it's still under development...
intresting ill test that out in about 15 mins
but does yours take a long time to come out of sleep mode?
Hmmm, that might be the notorious sleep of death SOD. I usually do something that most don't like but I sort of turn off the screen time out by first making the screen time out greater than 10 or 30 minutes. After that it should make things easier as far as disabling the auto back light/screen timeout feature. Keep in mind this is only a work around, I believe there is mention of actually fixing this issue. You'll need to download a free app called batterybooster (use the link if you want to read up on it a little). Once installed, run it and look for the far right icon and tap it. Set the timeout to Never and you'll notice a decent performance enhancement in the screen off and screen on.
NOTE: You will need to manually turn it off from here-on. You can try to play around with the setting but I find it somewhat problematic. Meaning that if you enable the timeout, it might and it might not work.
alright well i tried the gingerbread and that didnt work it lagged .
i tried froyo , it was amazing then i found out wifi didnt work
so now im back to the regular android one i had before ill be trying to see if theres a difference now that i "overclocked" it .
but thanks for all the help.
ill post back if i need something!
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
R^7Z said:
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
Click to expand...
Click to collapse
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
ndnmaster096 said:
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
Click to expand...
Click to collapse
NVM I got the wifi to work now .
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
R^7Z said:
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
Click to expand...
Click to collapse
well i set it to never timeout and i have a lock pattern
but since it never times out it wont lock .
also now im starting to notice froyo is rebooting for some weird reason automatically .
Calm down, that is kind of "usual behavior" . There are quire a few things going on and the OS is attempting to "handle it". Sometimes it can't and just quits instead of freezing up ( which would be the lesser of two evils ). To get it to lock, you will have to turn it off manually (power button). Unfortunately, I think if the keyboad slides out, it self unlocks (kind of a self defeating purpose, more or less). If you turn the screen off and wait like 10 seconds then turn the screen on (power key), you should see the lock. I can't say for sure but it does work for me. I don't really have much time for troubleshooting today, as I am at work currently but do look over the threads I linked you to earlier if at all possible.
okay so i turned it off using the power button and it booted to windows mobile (odd)
then i tried running haret.exe & got this message:
"The file HARET cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. IF the problem persists, try reinstalling or restoring the file."
im not sure what to do.
i tryed reformatting the card and installing fresh files, which didnt work so now im left questioned?
When you say you turned it off, did you hold the button or just press it once? If you pressed it once, then, that is definitly not "usual" behavior. I recall having that issue once upon a time but for the life of me, I don't recall what I did to recover from it. However, it sounds like you are attempting to run from a shortcut that references the program(haret) that is no longer there. To resolve this, I need you to confirm that you are running from the microSD and not a shortcut. Also, you aren't formatting under windows, right? If you are formatting from windows, that would be a "no-no"
Find something like the HP tool (can be googled) that everyone else talks of or even something like the free version of partition wizard should work.
i held the button and it gave me options
1) airplane mode
2)shutoff
3)vibrate
i did try to make a shortcut but i deleted it and now when i checked i was running it from the actual application.
lastly, i did format from windows but i downloaded hp format tool
and formated my device in quick format.
reinstalled the programs and it still gave me the same error message,
please help, i really miss android =(
Try deleting data.img and letting it recreate the file. To clarify about the screen off issue, when you press the power button once (not hold), what does it do? Also, which kernel package are you using and have you attempted to download a newer kernel package yet?
Also, try THIS kernel package; I got it from THIS site. It looks like that kernel package is specific to our devices.
been playing around with build.prop tweaks today. here's some that i have had good results with:
setting dalvik to 64
yes, that's high, but, switching screens on the homescreen has been a lot smother. you may have some issues with smaller apps, if so, try a lower setting. stock is 42, 48 may work good if you have a lot of smaller apps.
i also added these, so far so good, no problems. these are older tweaks, but they seem to be working here, but it's hard to tell
Code:
ro.HOME_APP_ADJ=1
locks home in memory
Code:
ro.media.enc.JPEG.quality=100
makes pics display at 100% quality
Code:
debug.sf.hw=1
enables hardware rendering of UI and home
take caution when editing build.prop. the file is located /system
do not delete or change anything else if you don't know what you're really doing.
debug.sf.nobootanimation=1
Disables the boot animations
svtfmook said:
ro.HOME_APP_ADJ=1
locks home in memory
Click to expand...
Click to collapse
Do you know if that works with 3rd party launchers (i.e. is HOME_APP whatever is linked to the home button, not hard coded to the moto home app)?
Wow, nice work guys. Quick question, does disabling the boot animation = faster boot time.
Sent from my MB865 using XDA App
916x10 said:
Wow, nice work guys. Quick question, does disabling the boot animation = faster boot time.
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
Not sure. You will still have the android boot animation. You just won't have the AT&T boot animation
Sent from my MB865 using XDA App
I tried using the these settings and it bricked my phone. Just FYI for anyone thinking of trying them out.
I think it has to do with the hardware rendering setting, because when I boot the video is very distorted and slow. It then goes black and vibrates every few seconds and I can't get it back. Restore to factory default was no help at all.
Any thoughts on how I might get this thing running again?
here's the stock build.prop
if the device will power on, extract it from this zip and try to adb push it to /system
not sure how these settings would brick your phone though. are you sure you added them to build.prop and not default.prop? did you change anything else in build.prop?
Yeah, I only added the options listed in the forum post, and didn't change anything else.
The first thing I tried was shelling into the phone using adb, but it didn't work at all in the state the phone was in. After restoring to factory defaults I was able to boot and get the initial setup screen for the phone where it asks you to add your email accounts, etc., but when clicking "done" the app would crash and restart effectively locking me out of the phone.
I'm assuming the crash is because I de-bloated the phone previously, and maybe it's missing a system library? Who knows.
In any case it looks like I may be taking a trip to the AT&T store
mspaulding06 said:
Yeah, I only added the options listed in the forum post, and didn't change anything else.
The first thing I tried was shelling into the phone using adb, but it didn't work at all in the state the phone was in. After restoring to factory defaults I was able to boot and get the initial setup screen for the phone where it asks you to add your email accounts, etc., but when clicking "done" the app would crash and restart effectively locking me out of the phone.
I'm assuming the crash is because I de-bloated the phone previously, and maybe it's missing a system library? Who knows.
In any case it looks like I may be taking a trip to the AT&T store
Click to expand...
Click to collapse
Thats odd. A factory restore would have overwritten any changed files and added any missing apks from /system
Sent from my MB865 using XDA App
svtfmook said:
Thats odd. A factory restore would have overwritten any changed files and added any missing apks from /system
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
Did you use a text editor on the phone or on a computer? If you use one that word wraps it will fubar the whole thing.
Here's a list of build.prop tweaks I found searching around, I haven't tried any myself yet, but hey, the more the merrier, right?
dasfiend said:
Did you use a text editor on the phone or on a computer? If you use one that word wraps it will fubar the whole thing.
Click to expand...
Click to collapse
i used an on the phone editor. windows editors will wreck it, linux editors are fine with build.prop though. not sure what the member who bricked his phone used.
I just tested the boot animation setting with a stopwatch and it's pretty much the same time one way or the other.
moofree said:
I just tested the boot animation setting with a stopwatch and it's pretty much the same time one way or the other.
Click to expand...
Click to collapse
Ya, but at least we don't have to look at the annoying super bright white at&t animation anymore.
moofree said:
I just tested the boot animation setting with a stopwatch and it's pretty much the same time one way or the other.
Click to expand...
Click to collapse
Thank you for checking and confirming that. I'll hit the button when I get to my pc.
Sent from my MB865 using XDA App
I did in fact use my phone to edit the build.props file (instead of using adb shell). I used the text editor feature of root explorer. I didn't notice the text wrap on the screen or anything like that when I was typing. I suppose that could've been the culprit.
mspaulding06 said:
I did in fact use my phone to edit the build.props file (instead of using adb shell). I used the text editor feature of root explorer. I didn't notice the text wrap on the screen or anything like that when I was typing. I suppose that could've been the culprit.
Click to expand...
Click to collapse
root explorer is fine, that wasn't your problem. i use root explorer as well. i think that either something else was changed, or something else is the problem.
svtfmook said:
Code:
ro.media.enc.JPEG.quality=100
makes pics display at 100% quality
Click to expand...
Click to collapse
With this setting does it change the display of your contact photos? Which show pretty crappy on the call screen.
jshinn1 said:
With this setting does it change the display of your contact photos? Which show pretty crappy on the call screen.
Click to expand...
Click to collapse
That's one thing I hope can be modded once the bootloader gets unlocked. My X10 showed the contact pics the top 1/3rd of the screen and the quality was very good, would be nice to see something similar on this phone.
moofree said:
I just tested the boot animation setting with a stopwatch and it's pretty much the same time one way or the other.
Click to expand...
Click to collapse
Same here, it just doesn't show the animation, but takes the same amount of boot time.
916x10 said:
That's one thing I hope can be modded once the bootloader gets unlocked. My X10 showed the contact pics the top 1/3rd of the screen and the quality was very good, would be nice to see something similar on this phone.
Click to expand...
Click to collapse
Exactly its annoying to have these great pics and when that person calls me it looks like crap not necessarily a huge deal but something I would like to see
After diving into some of the files in the oneplus one, I found some file values that once changed, make the microphone actually strong enough to recognize ok google from an arm's distance away. This is essential for using speakerphone, skype, any recording application, as well as google now. I was tired of having people go WAT ARE YOU SAYING repeatedly.
You will need a rooted Oneplus One with some sort of root explorer.
I used Root Explorer (File Manager) by Speed Software
1. Go to system/etc/mixer_paths.xml
2. Mount system as R/W
3. Open up mixer_paths.xml with Text Editor
4. Scroll close to the bottom of the text, your little scroll position indicator should be about an inch up from the bottom of your screen(no on screen buttons)
5. You will see <!-- Analog input devices --> and a bunch of text underneath.
6. I wasn't entirely sure which mic would make this work so I changed the <path name+"main-mic"> value from 84 to 100. (Play around with the value until you find a sweet spot.) IF YOU GET ENVIRONMENTAL MICROPHONE INTERFERENCE, TRY TURNING THE VALUES BACK DOWN A BIT.
7. Save the changed mixer_paths.xml and reboot your device for good measure
Enjoy your actually functional microphone! I hope that CM11s fixes this in an update shortly. It is not fixed as of July 4, 2014
I AM THE ORIGINAL POSTER
Gabriel Hahr AKA Kokorone
If you want my original Oneplus One forum post, search it up under the CM11s section of their forum. I am not able to link it here because I just joined XDA.
Thanks for this workaround.
I'm wondering if you know how to enable lock screen wake up hotword. Is it working in current version of cyanogenmod 11s? As I now, it should be something like "OK, oneplus" and phone wakes up from a black screen. Thanks.
soul_ride said:
Thanks for this workaround.
I'm wondering if you know how to enable lock screen wake up hotword. Is it working in current version of cyanogenmod 11s? As I now, it should be something like "OK, oneplus" and phone wakes up from a black screen. Thanks.
Click to expand...
Click to collapse
This is not working yet. There's an update on OP forums (https://forums.oneplus.net/threads/ok-oneplus-update.46934/) saying that there's a further delay.
As an OPO owner, I have confirmed the shipped version of the phone with XNPH22R and XNPH25R do not have a working screen off "Ok Google/HeySnapdragon/OK OnePlus"
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
Kokorone said:
After diving into some of the files in the oneplus one, I found some file values that once changed, make the microphone actually strong enough to recognize ok google from an arm's distance away. This is essential for using speakerphone, skype, any recording application, as well as google now. I was tired of having people go WAT ARE YOU SAYING repeatedly.
You will need a rooted Oneplus One with some sort of root explorer.
I used Root Explorer (File Manager) by Speed Software
1. Go to system/etc/mixer_paths.xml
2. Mount system as R/W
3. Open up mixer_paths.xml with Text Editor
4. Scroll close to the bottom of the text, your little scroll position indicator should be about an inch up from the bottom of your screen(no on screen buttons)
5. You will see <!-- Analog input devices --> and a bunch of text underneath.
6. I wasn't entirely sure which mic would make this work so I changed the <path name+"main-mic"> value from 84 to 100. (Play around with the value until you find a sweet spot.) IF YOU GET ENVIRONMENTAL MICROPHONE INTERFERENCE, TRY TURNING THE VALUES BACK DOWN A BIT.
7. Save the changed mixer_paths.xml and reboot your device for good measure
Enjoy your actually functional microphone! I hope that CM11s fixes this in an update shortly. It is not fixed as of July 4, 2014
I AM THE ORIGINAL POSTER
Gabriel Hahr AKA Kokorone
If you want my original Oneplus One forum post, search it up under the CM11s section of their forum. I am not able to link it here because I just joined XDA.
Click to expand...
Click to collapse
Does this only affect OK Google? I'm wondering if affects other mic input like voice calls, etc. I don't want my voice to sound booming while on calls because of this change... lol
is it possible to root without wipe/reinstall CM?
I did it to the "t" and it only gave me force closes. Audiofx wouldn't stop even afteri freezer the all disabled it and force stopped. I'm running usa version of the oneplus. I had to reinstall cm11s
jerrah said:
I did it to the "t" and it only gave me force closes. Audiofx wouldn't stop even afteri freezer the all disabled it and force stopped. I'm running usa version of the oneplus. I had to reinstall cm11s
Click to expand...
Click to collapse
Yea likewise minus the reinstall since I am smart. OP something is not right when we touch this file. It seems to delete a lot of the stuff. I managed to fix it in TWRP, mount system, and adb push the fixed file. Their is an easier way to do this operation using a shell script and the busy box command, "SED" which will place an exact line with what you tell it to. I am in the process of creating one since this hack really helps a lot.
tonu42 said:
Yea likewise minus the reinstall since I am smart. OP something is not right when we touch this file. It seems to delete a lot of the stuff. I managed to fix it in TWRP, mount system, and adb push the fixed file. Their is an easier way to do this operation using a shell script and the busy box command, "SED" which will place an exact line with what you tell it to. I am in the process of creating one since this hack really helps a lot.
Click to expand...
Click to collapse
thank I really wanted to try this. This time I had my back up ready I went to the file didn't change anything later when I restarted it gave me force closes again. So I can't wait for your script.
dmo580 said:
This is not working yet. There's an update on OP forums (https://forums.oneplus.net/threads/ok-oneplus-update.46934/) saying that there's a further delay.
As an OPO owner, I have confirmed the shipped version of the phone with XNPH22R and XNPH25R do not have a working screen off "Ok Google/HeySnapdragon/OK OnePlus"
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
Does this only affect OK Google? I'm wondering if affects other mic input like voice calls, etc. I don't want my voice to sound booming while on calls because of this change... lol
Click to expand...
Click to collapse
OK Snapdragon works on earlier versions of ColorOS with the screen off.
In later versions they took out the support for the OK Snapdragon command and replaced it with their garbage chinese voice control app.
---------- Post added at 10:57 PM ---------- Previous post was at 10:32 PM ----------
jerrah said:
I did it to the "t" and it only gave me force closes. Audiofx wouldn't stop even afteri freezer the all disabled it and force stopped. I'm running usa version of the oneplus. I had to reinstall cm11s
Click to expand...
Click to collapse
You probably had word wrap turned on.
---------- Post added at 10:58 PM ---------- Previous post was at 10:57 PM ----------
Kokorone said:
After diving into some of the files in the oneplus one, I found some file values that once changed, make the microphone actually strong enough to recognize ok google from an arm's distance away. This is essential for using speakerphone, skype, any recording application, as well as google now. I was tired of having people go WAT ARE YOU SAYING repeatedly.
You will need a rooted Oneplus One with some sort of root explorer.
I used Root Explorer (File Manager) by Speed Software
1. Go to system/etc/mixer_paths.xml
2. Mount system as R/W
3. Open up mixer_paths.xml with Text Editor
4. Scroll close to the bottom of the text, your little scroll position indicator should be about an inch up from the bottom of your screen(no on screen buttons)
5. You will see <!-- Analog input devices --> and a bunch of text underneath.
6. I wasn't entirely sure which mic would make this work so I changed the <path name+"main-mic"> value from 84 to 100. (Play around with the value until you find a sweet spot.) IF YOU GET ENVIRONMENTAL MICROPHONE INTERFERENCE, TRY TURNING THE VALUES BACK DOWN A BIT.
7. Save the changed mixer_paths.xml and reboot your device for good measure
Enjoy your actually functional microphone! I hope that CM11s fixes this in an update shortly. It is not fixed as of July 4, 2014
I AM THE ORIGINAL POSTER
Gabriel Hahr AKA Kokorone
If you want my original Oneplus One forum post, search it up under the CM11s section of their forum. I am not able to link it here because I just joined XDA.
Click to expand...
Click to collapse
This fix didn't work for me.
I set all 3 values to 100 and Google Now still can't hear me until I press the microphone button.
I think the problem is not that the volume is too low. I think the problem is that the mic doesn't get turned on until you touch the microphone button.
Edit: This actually seems to be a problem with my specific phone. I'm sorry about that.
tonu42 said:
Yea likewise minus the reinstall since I am smart. OP something is not right when we touch this file. It seems to delete a lot of the stuff. I managed to fix it in TWRP, mount system, and adb push the fixed file. Their is an easier way to do this operation using a shell script and the busy box command, "SED" which will place an exact line with what you tell it to. I am in the process of creating one since this hack really helps a lot.
Click to expand...
Click to collapse
Can you give a quick explanation of how you adb push the fixed XML? I'd rather not have to completely reinstall to fix one file.
tonu42 said:
Yea likewise minus the reinstall since I am smart. OP something is not right when we touch this file. It seems to delete a lot of the stuff. I managed to fix it in TWRP, mount system, and adb push the fixed file. Their is an easier way to do this operation using a shell script and the busy box command, "SED" which will place an exact line with what you tell it to. I am in the process of creating one since this hack really helps a lot.
Click to expand...
Click to collapse
Works perfectly fine on my OnePlus One. I followed the above tutorial and got Google Now finally working as it should.
Kokorone said:
After diving into some of the files in the oneplus one, I found some file values that once changed, make the microphone actually strong enough to recognize ok google from an arm's distance away. This is essential for using speakerphone, skype, any recording application, as well as google now. I was tired of having people go WAT ARE YOU SAYING repeatedly.
You will need a rooted Oneplus One with some sort of root explorer.
I used Root Explorer (File Manager) by Speed Software
1. Go to system/etc/mixer_paths.xml
2. Mount system as R/W
3. Open up mixer_paths.xml with Text Editor
4. Scroll close to the bottom of the text, your little scroll position indicator should be about an inch up from the bottom of your screen(no on screen buttons)
5. You will see <!-- Analog input devices --> and a bunch of text underneath.
6. I wasn't entirely sure which mic would make this work so I changed the <path name+"main-mic"> value from 84 to 100. (Play around with the value until you find a sweet spot.) IF YOU GET ENVIRONMENTAL MICROPHONE INTERFERENCE, TRY TURNING THE VALUES BACK DOWN A BIT.
7. Save the changed mixer_paths.xml and reboot your device for good measure
Enjoy your actually functional microphone! I hope that CM11s fixes this in an update shortly. It is not fixed as of July 4, 2014
I AM THE ORIGINAL POSTER
Gabriel Hahr AKA Kokorone
If you want my original Oneplus One forum post, search it up under the CM11s section of their forum. I am not able to link it here because I just joined XDA.
Click to expand...
Click to collapse
I'm thinking of trying this but hesitant due to the problems others are having. If we run into an issue can we just restore a nandroid and everything will be fine? Thanks
Tried but didn't work for me.
*edit* It does work. Is it supposed to work from the home screen though? If i go into my google now it will work without hitting the microphone but not from the home screen. Just wondering.
Worked great for me, used the stock CM file browser/editor and carefully edited it correctly. no issues. Voice transcription quality is greatly improved, OK Google (On google now screen) is much more reactive.
OK Google (or OK One Plus) is not working on the home screen, but that is to be expected, https://forums.oneplus.net/threads/ok-oneplus-update.46934/ The developers need to re-record the hotword sound files and we will need to get an update to have this function enabled. That problem is unrelated to the low microphone sensitivity.
Thank you so much for posting this fix! Just got my OPO today and was getting fed up w/ "OK Google" not working. Arms length my ass haha. I used Root Explorer as well and no issues.
I set the main-mic to 95 and the anc-mic to 90. Will play around more. :good:
sharp2G said:
Works perfectly fine on my OnePlus One. I followed the above tutorial and got Google Now finally working as it should.
Click to expand...
Click to collapse
Thanks! Honestly I don't think I'll be rooting mine though..
Hey I just came back to say I figured out why hotword detection was not working sometimes.
Some apps you install which use Notification Access prevent Google Search from opening the microphone channel.
Pushbullet is one app that is known to do that.
Worked like a charm. On 64GB Oneplus One, the Chinese version.
Thanks a million.
I received my OPO this past Saturday. Coming from an awesome LG G2 experience I was a bit disappointed that I had to be about no more that 5 inches from the phone to get it to hear OK Google. My phone sits in the cupholder in my truck while driving and I have come to really like the OK Google feature on my G2.
This edit fixed it!
Hopefully the CM11s team will clear it up in the next update.
Thank you.
I recommend using the official fix here:
http://review.cyanogenmod.org/#/c/67619/
I've attached the xml (zipped) in this post. Gerrit seems to name the XML funny. Just be sure to rename it as mixers_path.xml and place it in /system/etc/ and fix the permissions (664)!
I just tried it in a meeting room and it picks up wonderfully at normal arms length distance WITHOUT having to point the microphone at me.
Edit: Wrong permissions = FC fest. If you're a noob, do a Nandroid backup.
dmo580 said:
I recommend using the official fix here:
http://review.cyanogenmod.org/#/c/67619/
I've attached the xml (zipped) in this post. Gerrit seems to name the XML funny. Just be sure to rename it as mixers_path.xml and place it in /system/etc/ and fix the permissions (664)!
I just tried it in a meeting room and it picks up wonderfully at normal arms length distance WITHOUT having to point the microphone at me.
Edit: Wrong permissions = FC fest. If you're a noob, do a Nandroid backup.
Click to expand...
Click to collapse
I really want to do this but I'm too lazy to go through the root process at the current time. However the Ok Google detection completely sucks and I hope someone figures a way to repair without root or someone makes rooting the OPO quicker and easier for lazy folk like myself.
My S3 with CM on it picks up me whispering Ok Google from across a room and under a sweater...this thing can't recognize me shouting at arms length.
Has anyone been successful to disable this?
+1 for this, it is annoying.
Brava27 said:
Has anyone been successful to disable this?
Click to expand...
Click to collapse
Been trying for two days to fix this 'feature' but they have changed the file position of the code and am having trouble finding it. Oh well at least I've learnt everything I ever wanted to know about decompiling/ recompiling . lol
I'm gonna try again in a few days once my sister has gone home as this is the first time in a year I've seen her in a year.
Wish me luck
i'm also looking for a way to disable increasing ring tone , also find it very annoying .
Try headset button controller
Not sure if this is actually a fix but just did some quick informal testing and seems to work: install app headset button controller and under advanced options set the default volume when plugging in headphones to 65% or above. If someone else can verify this it would be awesome.
cavemandave13 said:
Not sure if this is actually a fix but just did some quick informal testing and seems to work: install app headset button controller and under advanced options set the default volume when plugging in headphones to 65% or above. If someone else can verify this it would be awesome.
Click to expand...
Click to collapse
Good try but when plugging my headphone in with this active, the device notices the volume change and the warning comes straight up.
Thanks anyway.
Ah yes, after I rebooted and plugged in I got the warning. However it seems to only be an issue the first time after reboot, then looks like it's good to go. Just don't reboot
Not sure if it applies to this phone as I sport note 4 and am only browsing, but in absence of xposed mod, I use tasker. Also free app 'hearing saver' from play store works for me.
Note 4 ?
need to decompile framework-res.apk ... open integers.xml , search for
<integer name="config_safe_media_volume_index">10</integer>
and change the value to 20
like this
<integer name="config_safe_media_volume_index">20</integer>
Carotix said:
need to decompile framework-res.apk ... open integers.xml , search for
<integer name="config_safe_media_volume_index">10</integer>
and change the value to 20
like this
<integer name="config_safe_media_volume_index">20</integer>
Click to expand...
Click to collapse
That doesn't work. It needs a smali edit
Custom rom im using has it disabled so its possible
Carotix said:
need to decompile framework-res.apk ... open integers.xml , search for
<integer name="config_safe_media_volume_index">10</integer>
and change the value to 20
like this
<integer name="config_safe_media_volume_index">20</integer>
Click to expand...
Click to collapse
I've already tried this. Needs smali edit. But I've been unable to find the code for this function.
edgarf28 has managed to accomplish this in his ROM and I have requested a point in the right direction or even a flashable version (bit cheeky I know) he has also managed to incorporate 5 way reboot that I would really like help with to. Might have to go and beg him again .lol
tiboric said:
I've already tried this. Needs smali edit. But I've been unable to find the code for this function.
edgarf28 has managed to accomplish this in his ROM and I have requested a point in the right direction or even a flashable version (bit cheeky I know) he has also managed to incorporate 5 way reboot that I would really like help with to. Might have to go and beg him again .lol
Click to expand...
Click to collapse
the reason he is able to do it is because his rom is de-odexed or whatever... we arent... that is why he can have it
c_86 said:
the reason he is able to do it is because his rom is de-odexed or whatever... we arent... that is why he can have it
Click to expand...
Click to collapse
I already did this it seem to ho quite smoothly but still having problems with getting 5 way and disabling safe volume.
Just need a bit of help to finish getting my device perfect.
Problem is theres not much ROM deving on 925f at the moment. I know this will pick up. I'm just impatient
I've been searching everywhere for a way to disable this volume warning. Has anyone figure it out and posted instructions? I see it in a couple custom ROMs but I haven't found how it is done.
skiddingus said:
I've been searching everywhere for a way to disable this volume warning. Has anyone figure it out and posted instructions? I see it in a couple custom ROMs but I haven't found how it is done.
Click to expand...
Click to collapse
I've simply flashed the alliance ROM. Very happy
In general, this issue still bothers me. At least in my car, in which I use an auxilliary cord, I've an NFC tag programmed to open Spotify and turn media volume all the way up using NFC Tasks/Tools. At least for me, this works to get past the warning initially, and is useful when I need to unplug then plug back in.
I would love to see a general fix that doesn't require rooting my phone; that sanctimonious popup drives me bonkers.
If youll go to the music player on your phone. Click settings, then click smart volume on. Try it out. Works for me on my s6
BigDaddy38 said:
If youll go to the music player on your phone. Click settings, then click smart volume on. Try it out. Works for me on my s6
Click to expand...
Click to collapse
This works... How easy was that!
sweeet! good work-around man! way better than using roms or rooting the sucker.
OK guys I hope this hasn't already been covered but here goes anyway. I have found this fix for notifications not arriving when doze is enabled. Iff you go into the particular app e.g what's app then into data usage you must select the following settings see pic below. then all the notifications will arrive straight away regardless of doze state.
sam00561 said:
OK guys I hope this hasn't already been covered but here goes anyway. I have found this fix for notifications not arriving when doze is enabled. Iff you go into the particular app e.g what's app then into data usage you must select the following settings see pic below. then all the notifications will arrive straight away regardless of doze state.
Click to expand...
Click to collapse
Yes that seems to be the problem. I had made a post months ago. It's very hidden feature by Lenovo and I think it's wrong to pre-restrict all background data. User should decide what to do.
I think they lenovo did it to block unnecessary data usage but i agree it is not needed and people are thinking their is something wrong with their phones.
Thanks for the tip
Thanks Sam, I saw this on the JJ review of Nougat. Is this for Nougat as my MM P2 settings don't look like the screenshot.
Sent from my Lenovo P2a42 using Tapatalk
Hi yes it is for Nougat the comment posted on JJs review regarding this fix was posted by me also.
Confusing settings these as the first one makes it look like enabling the "Restrict background data" option will disable background data, when in fact it does the opposite. You need to have both of these options enabled so the sliders are green, then you need to open Settings > Power Manager > Battery Optimization
Then you need to search for the apps that you need to fix notifications and change the option so it says "Don't optimize". Then the phone won't 'helpfully' close the app when the phone has been unused for a long time. This is why notifications are stopping.
precisely i agree quite confusing it took me a while i had to get a friend to send me whats app messages continuously untill i figured all this out but im glad i finally did.
If you make the changes to fix the notifications, shut down and power the phone back on rather than do a reboot. The settings don't seem to work until the phone has properly rebooted.
Is it worth noting that elsewhere it's stated that turning off doze altogether (using ADB) might be a saner option? Consensus seems to indicate it's basically a curse with little value, and that would certainly hold water in light of the battery capacity of the P2.
https://forum.xda-developers.com/lenovo-p2/help/regretting-purchase-t3611968
I think the following helps. Credit goes to JasonMR and manototh (Taken from oneplus.net forum)
JasonMR
KitKat
JasonMR, Nov 2, 2016 :
Guys, to avoid having to run the ADB command after each reboot follow these instructions (please note, the files should be downloaded to a PC and then transferred to your phone via USB otherwise they mess up sometimes):
You need to enable USB debugging mode in Developer options first
Download and install this apk and transfer it to your phones storage - https://drive.google.com/file/d/0BxD...w?usp=drivesdk
Then connect phone to PC and allow the drivers to install
Download and install ADB here - https://drive.google.com/file/d/0B0M...ljU2NPR0k/view
Go into the ADB folder, hold shift, right click and select "Open command prompt here"
Type the command: adb devices (now hit enter)
It should return your phones serial number is connected correctly
Run this command in ADB: adb -d shell pm grant com.adamioan.scriptrunner android.permission.DUMP (now hit enter)
Download this file and transfer it to your phones storage - https://drive.google.com/open?id=0Bx...VA4YmxGTS1OX3c
Open the SH Script runner app and tap the three dots in the top right corner, select "Load" and locate the file from teh previous step
Click the Circle button with the play sign at the top of the screen
You should see the message "Idle mode disabled" which means that Doze has now been disabled.
Whenever you reboot your phone, open the SH Script runner and the command will still be there, just click the play button to run the script again.
And that is it, two clicks to disable Doze after each reboot.
Full credit to manototh for putting this together originally.
Doze does not need disabling iff you follow my advice in the initial post i have tried and tested this and can confirm it works fully.
This is really frustrating. No matter what settings I use I still don't get notifications after a while. I don't want to go modifying my phone, can someone post a step by step if they have it working properly?
Spacedog79 said:
This is really frustrating. No matter what settings I use I still don't get notifications after a while. I don't want to go modifying my phone, can someone post a step by step if they have it working properly?
Click to expand...
Click to collapse
Follow my ordinal post and also go into battery optimisation and disable optimization for things like sms eggs what's app Facebook etc all the things you need notifications for should be disabled from sleep mode under battery optimization.
Like this
sam00561 said:
Like this
Click to expand...
Click to collapse
Yes thats exactly how I've done it. I've also tried every combination of settings under Apps for Unrestricted data usage.
And also the setting here
sam00561 said:
And also the setting here
Click to expand...
Click to collapse
Yep doesn't work either.
Perhaps your only option left is to try the disable doze app which has worked for many people but it's a paid app.
Just to update it does seem to be working properly now. I'm not 100% sure but I think turning the phone all the way off and on again instead of rebooting with the settings correct had the desired effect.