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.
Related
Hi I don't know if this is the right place to put this info.
I see lots of people are having the dialer battery drain issue in pretty much every version of android 2.3.3. And I haven't seen a working solution anywhere other than upgrade to a newer version of android.
Any way, I'm using a HTC legend a gingerbread version 2.3.3, and I have always had the dreaded dialer battery drain issue.
I have found a work around that helps stop the drain, at least on the HTC legend 2.3.3 version I'm using.
In my case it is simply having the line
gsm.proximity.enable=false
In the build.prop
It would seam to stop the proximity sensor from working with the dialer part of phone.
The only side effect I have seen so far is that the screen won't turn off when u hold phone upto your ear, you can of course turn screen off with power button, at least from a legend point of view.
I hope this information will help others with android 2.3.3 on other phones that also have dialer battery drain.
Sent from my HTC Legend using XDA App
Hi, here's a bit of an update for those that are interested, even though the proximity sensor has been disabled for phone calls after adding the line to build.prop, here is a work around to allow the proxy to turn off screen again.
Down load "proximity screen off" from the market, in the settings, select enable during calls only.
Now on my phone the other settings seam to be a bit screwy so you'll have to play with them to suite your device for the way you want it to work.
I am still testing to see how battery life is, but so far its looking good.
If you feel like it, I would appreciate some feedback regarding these mods.
Thanks
Sent from my HTC Legend using XDA App
another point of attack
So.. It seems CyanogenMod team has identified these proximity sensor issues and actually fixed most all of them (on the devices they support). The answer is complicated and nestled into the code. But basically one could say there has been an omission of suspend and wake calls that now make MANY HTC devices not function properly. So, besides this there are SoD issues with some devices after a call.. Same type fix used to resolve and that one usually is resolved with an OTA fairly quickly... But ummm, why can't HTC users ban together and make HTC perfect their sources? They are after all the manufacturer and Sense roms are just copies of their source (modified here and there perhaps)... so the problems have been identified, solutions have been committed by an OPEN SOURCE team... good lord HTC, this has been going on since the Desire.. and just browsing I found Legend, Wildfire S and several others effected..
Great work-a-rounds btw... I just really think the consumers should petition on these issues as they are all related and fixable. Most just hear battery life sucks on the Android and assume their phone going dead after 5 hrs is normal... Well it's not. Just my 2c.
Rob
helppp...!!! pls
im also usin ogoo's rom having battery drain problem.. im kinda noob
cn u tel me specifically wht to do?
nd wht is? build.prop
akashj17 said:
im also usin ogoo's rom having battery drain problem.. im kinda noob
cn u tel me specifically wht to do?
nd wht is? build.prop
Click to expand...
Click to collapse
Well my friend , I was a noob about 7 or 8 months ago too, I did lots of reading and learning and used Google to find my answers.
But here's some quick help to get you started....
Before you do anything if you haven't already do a nandroid backup.
You are using ogos gingerbread so you must be rooted yeah, OK so next we need to find out how u rooted, if you went down the hboot 1.02 and unlocked boot loader method, that is great makes my job much easier.
Build.prop is a file located in the
/system/ folder
It is basically a text file that contains a list of settings/commands/startup options.
In my ogos rom the command in question has a # in front of it which disables that line.
You need to edit that file and remove the #. To do this I used es file explorer with root turned on in settings, then just went to /system and opened it with es file explorer.
Or you could get build.prop editor from market and add the line that way, however you need to leave out the = and put the stuff in front in the top field and the 1 In the other.
Simple as that....
If you are say hboot 1.01 and s-on then that's a lot harder for me :-(
You'll only be able to do it via fastboot method, reboot phone into fast boot menu volume down then power. Connect to your PC, it is properly set up isn't it yeah? use android commander to copy that file to your PC, edit file using notepad then copy it back.
If you done it right, good if not, ummm you might need to search for answers for to what you need.
You could always send your phone to me and pay me I only charge $100 per hour lolol
Sent from my legend using XDA
Thnxxx........ Ranger
***UPDATE***
I upgraded to ParanoidAndroid and had to use a different apk. I don't know who made this one (i downloaded like 10 from xda and tried about 4 before it started working), but here's the winner:
techneesh.com/paranoidandroidnfcscreenoff.apk
*****************
Hey guys,
I searched for hours but could only find reports of people *NOT* getting this to work on the Verizon GS3 (hence the name of the thread).
I tried hacking my stock Nfc.apk using dex2jar & modding the smali files (after looking up the appropriate values to change using decompiled dex2jar classes.dex's nfcservice.java), but after much frustration decided to just go ahead and try the existing versions out there.
By the way, if anyone is looking for how to do this (decompiling/modding/recompiling an apk) with 4.0.4 (and getting the 'bad magic number with smali/baksmali), refer to the comment on May 8th in this thread.
I'm pleased to report that mayhemer's AT&T version (for the SGS-I747) works for us Verizon folks!
You can grab it on his thread here.
I've also uploaded it to my server. Here's a direct link:
techneesh.com/Nfc.apk
I posted this in the Development section because I would really like to encourage devs to work on modding Nfc functionality further. Also, this is a more advanced mod for a system app.
Google Wallet did not throw errors with this .apk (as it did with others), although I have not tested it yet.
NFC reads trigger the nfc tag's function and the alarm/beep, but do not turn on or unlock the screen (while it is off).
Also, I just got a whole bunch of NFC tags in and plan to make some cool products for them... if you have any ideas let me know on my 3D-printing-on-demand-for-xda-samsung-gs3-folks thread.
Note- I am on Bean's Custom Stock R3.1 07/28 (I know, I need to upgrade)
4.0.4, SCH-I535, Baseband I535VRLF2, Kernel 3.0.38imoseyon+, Hardware I535.10
Instructions for apk:
1. Get apk onto your phone
2. Stop NFC (or else your phone will start lagging // freezing after the next step)
3. Copy the apk to /system/app/ with a root explorer and overwrite the existing Nfc.apk (you should make a backup first)
4. Change permissions to match other system apks (rw-r--r--)
5. Reboot & re-enable nfc. Profit. Share your uses.
For zip you should be able to just flash in cwm.
What reasons would one what NFC enable while the screen is off/ phone locked ????
yardi4life said:
What reasons would one what NFC enable while the screen is off/ phone locked ????
Click to expand...
Click to collapse
So you don't have to unlock we are lazy people
Sent from my Verizon Galaxy S III
is this for reals?
really hoping this works..been waiting for it!
yardi4life said:
What reasons would one what NFC enable while the screen is off/ phone locked ????
Click to expand...
Click to collapse
oh man, don't get me started!
think about it - you get to your desk and want to tether / turn on music / silence phone. just tap it on the nfc sticker on your desk. done.
you get into your car and want to enable gps / turn on music / navigate somewhere. tap your phone to the nfc sticker. done.
i have a lockscreen for security and even though it only takes a second to open it still adds up over the course of the day. the ability to quickly do (any) task on your phone without unlocking it or even pressing a button is huge.
for example, I canceled home internet last year when I got LTE but this means I have to turn on tethering every time i sit down at my PC. using a tasker nfc-activated command I can just touch my phone to my desk and it's on. time saving and just fun.
or maybe you are in a meeting and miss a call and want to call them back - have a pre-programmed nfc sticker that will command your phone to set an alarm for (e.g.) 1 hour. tap your phone to it without fiddling /unlocking/interrupting your meeting further.
what really made me think of this is while I was looking for something behind a wardrobe and wanted to turn on my LED flashlight on my phone. how cool would it be to have an nfc sticker (on your keychain? on a sliding mechanism on a custom techneesh.com case on your phone?) that could basically act as a 4th hard button to do a custom function (in this case, turn on the LED flashlight without 1. turning on screen 2. unlocking 3. going to home screen 4. finding LED flashlight app and opening)
and yes, this is for real
I'm trying to get this to work on CleanROM 2.5, with the G7 baseband. I followed the steps correctly, but it doesn't to anything different than the stock NFC
I can still read my tags when screen on and unlocked, but i get no response with the screen off or on and locked.
Triskite, did you modify the .apk from the linked At&t SGSIII thread at all? If not, would it be safe to try the other apk's listed there?
Thanks!
usatf1290 said:
I'm trying to get this to work on CleanROM 2.5, with the G7 baseband. I followed the steps correctly, but it doesn't to anything different than the stock NFC
I can still read my tags when screen on and unlocked, but i get no response with the screen off or on and locked.
Triskite, did you modify the .apk from the linked At&t SGSIII thread at all? If not, would it be safe to try the other apk's listed there?
Thanks!
Click to expand...
Click to collapse
the apk worked as-is for me - only thing i can think of to try is to turn ON a lockscreen? (I use the pattern security one)
safe? I certainly can't assure that... but would I try them? yes.
Triskite said:
the apk worked as-is for me - only thing i can think of to try is to turn ON a lockscreen? (I use the pattern security one)
safe? I certainly can't assure that... but would I try them? yes.
Click to expand...
Click to collapse
I went ahead and tried the .zips from that thread
I flashed the nfcmodI747_lockscreen.zip flashable from CWM and it works like a charm!
Once i did this, i wanted to see if the screen off nfcmodI747_screenoff.zip works, and it sure does (again, flashed via CWM)!
Don't know if it matters, but i did not disable NFC from settings before i flashed them via CWM.
Thanks again!
Just saying this is as of the moment the most unsafe mod someone can implant or put a nfc tag somewhere to run malicious code on your device. While I do not condone hacking of any sort, I know the possibilties of what these hacks can do from different forums (not naming any).
TLR, caution with this one guys. Especially if you're using wallet using my guide......
Ok...what are these tags you're talking about? I've never ran across NFC tags in "the wild"...do you buy them and then tell your phone what to do when it reads a certain tag?
backcourse said:
Ok...what are these tags you're talking about? I've never ran across NFC tags in "the wild"...do you buy them and then tell your phone what to do when it reads a certain tag?
Click to expand...
Click to collapse
Yeah you can get nfc tags at stores and program it what to do when u tag ur phone with it, using the TecTiles app or some sort
Pretty cool
Sent from my SCH-I535
nfc keychain dongle for $5!
Hmong_Xiong said:
Yeah you can get nfc tags at stores and program it what to do when u tag ur phone with it, using the TecTiles app or some sort
Pretty cool
Sent from my SCH-I535
Click to expand...
Click to collapse
I wrote up a post outlining some sweet stuff you can do and some cool apps to use, here.
I also just finished creating a keychain nfc dongle! Grab one for $5 on my site, techneesh
tonu42 said:
Just saying this is as of the moment the most unsafe mod someone can implant or put a nfc tag somewhere to run malicious code on your device. While I do not condone hacking of any sort, I know the possibilties of what these hacks can do from different forums (not naming any).
TLR, caution with this one guys. Especially if you're using wallet using my guide......
Click to expand...
Click to collapse
Yea, I understand the risks and all.
I agree that it is a major security vulnerability for someone that wishes to highly protect their information.
I just wanted to try it for a proof-of-concept kind of thing.
Honestly its pretty quick to flash these via Cwm. I went back to stock Nfc.apk for parties/bars this weekend (Too many people close to me for security comfort), then today I flashed the lock screen version for my school week.
It would be really cool if it were possible to toggle this.
usatf1290 said:
Yea, I understand the risks and all.
I agree that it is a major security vulnerability for someone that wishes to highly protect their information.
I just wanted to try it for a proof-of-concept kind of thing.
Honestly its pretty quick to flash these via Cwm. I went back to stock Nfc.apk for parties/bars this weekend (Too many people close to me for security comfort), then today I flashed the lock screen version for my school week.
It would be really cool if it were possible to toggle this.
Click to expand...
Click to collapse
Can somebody post the stock nfc apk file(s)? I guess they are needed to take the OTA update after mucking with Wallet, and i didn't save them.
I just tried the nfcmodI747_screenoff.zip with the latest paranoid android (2.16) and it does not work. The NFC settings disappear entirely.
morttt said:
Can somebody post the stock nfc apk file(s)? I guess they are needed to take the OTA update after mucking with Wallet, and i didn't save them.
Click to expand...
Click to collapse
Here is my stock nfc.apk
I have flashed synergy (ICS), jellywiz and now cleanrom 2.5. I don't know if they've modified anything in the NFC.apk, but this is what I have.
If you wanna guarantee its ok, you can pull it from the stock ROM.
Md5: ddacac3aad2e700b91239404e193f88b
Has anyone got this to work with cm10? Im more interested in disabling the nfc scan noise. I tried to replace the ogg files in nfc.apk with silent ones using ninjamorph and zip signer but i keep getting force closes. Any ideas?
Triskite said:
oh man, don't get me started!
think about it - you get to your desk and want to tether / turn on music / silence phone. just tap it on the nfc sticker on your desk. done.
you get into your car and want to enable gps / turn on music / navigate somewhere. tap your phone to the nfc sticker. done.
i have a lockscreen for security and even though it only takes a second to open it still adds up over the course of the day. the ability to quickly do (any) task on your phone without unlocking it or even pressing a button is huge.
for example, I canceled home internet last year when I got LTE but this means I have to turn on tethering every time i sit down at my PC. using a tasker nfc-activated command I can just touch my phone to my desk and it's on. time saving and just fun.
or maybe you are in a meeting and miss a call and want to call them back - have a pre-programmed nfc sticker that will command your phone to set an alarm for (e.g.) 1 hour. tap your phone to it without fiddling /unlocking/interrupting your meeting further.
what really made me think of this is while I was looking for something behind a wardrobe and wanted to turn on my LED flashlight on my phone. how cool would it be to have an nfc sticker (on your keychain? on a sliding mechanism on a custom techneesh.com case on your phone?) that could basically act as a 4th hard button to do a custom function (in this case, turn on the LED flashlight without 1. turning on screen 2. unlocking 3. going to home screen 4. finding LED flashlight app and opening)
and yes, this is for real
Click to expand...
Click to collapse
Tasker can do all of this.. no NFC needed
Lock-N-Load said:
Tasker can do all of this.. no NFC needed
Click to expand...
Click to collapse
True, but this involves active running processes like GPS which can drain your battery. From my experience, NFC has no noticeable extra drain, not even the screen off modified version. Not to mention how easy it is to use the NFC programming apps versus Tasker, IMO.
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
bambam2k3 said:
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
Click to expand...
Click to collapse
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
joannn said:
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
Click to expand...
Click to collapse
Joannn,
Thanks for the thoughts.
I tested safe mode and the classic voice dialer does not come up at all so it definitely has to be some sort of app or weird way my system is calling something when using the headset in normal mode.
I tried the following with no success in normal mode:
1) Disabled Xposed and all modules - rebooted - no change
2) Disabled tasker and tested with just plugging in the headset and testing the button - no change
3) Switched from Nova launcher back to stock launcher - no change
4) Uninstalled a headset button control app - no change
So, I'm not sure why the phone randomly thinks this old dialer is the correct one to launch, nor do I have any idea where it is coming from. It doesn't appear to be a separate app and even when I look through the system apks, I see nothing that looks like it references this classic voice dialer. Not sure what's triggering it.
--Bambam2k3
take a screenshot of your classic looking dialer and post it here.
simms22 said:
take a screenshot of your classic looking dialer and post it here.
Click to expand...
Click to collapse
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
bambam2k3 said:
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
Click to expand...
Click to collapse
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
simms22 said:
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
Click to expand...
Click to collapse
Holy hell, Simms, I did NOT even notice that.
Marvelous. Now to find out what app installed this crap...
--bambam2k3
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
simms22 said:
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
Click to expand...
Click to collapse
I've got to assume it's something related to Tasker or the Secure Settings plugin for it. I uninstalled every single app I could think of that may have had the ability to make any calls of any nature, and in Settings>Apps I don't see the Voice Dialler at all, even before I started uninstalling things.
Without Tasker being used, I haven't seen the bad dialer come back again.
Was really only using tasker to get around the fact that the headset button is ignored if the phone is pin locked. Guess I'll try and find another way around it.
Thanks for your help,
bambam2k3
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
bambam2k3 said:
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
Click to expand...
Click to collapse
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
simms22 said:
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
Click to expand...
Click to collapse
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
bambam2k3 said:
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
Click to expand...
Click to collapse
so it seams then that you either need to update your google search or you are using a samsung device and not a nexus 5.
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.
So, the problem started when I was typing fast, sometimes the keyboard would minimize itself. Then I realized it was only when I was near the "a" key (independent of the keyboard app). So, I got to make some tests, it turns out the screen thinks I am swiping to go back, when I'm not. Please check this video: https://youtu.be/cdg4_oJ68aM
Is there something I can do?
I'm on a Mi Mix 2s 9.5.19.0
I had this problem too. I no longer own the phone though so I'm afraid I can't help. I was wondering if it was fixed in the MIUI 10 beta but nobody has answered it so far. If anyone can chime in to say if it's fixed now would be nice, it made typing basically impossible for me.
Well, it was a display defect. I have to wait 2 weeks for the replacement part to arrive, but it's under warranty. Until then, I'll just use the on screen buttons.
It happens to me from time to time, but not sure if this is my fault. I don't understand the methodology of your test on the video (what are you pressing and when?).
hayatesan said:
It happens to me from time to time, but not sure if this is my fault. I don't understand the methodology of your test on the video (what are you pressing and when?).
Click to expand...
Click to collapse
It's the test module of MIUI, I'm just tapping left, right, left, right, etc, sometimes it is interpreted as a swipe between the 2 points (when a line appears). But it's pretty agressive in my display, got it checked and they are going to replace it under warranty.
So I shouldn't get any red lines when just taping right and left? I have those....
That's what happens to me and I'm getting back randomly after a few seconds of quickly taping left and right.
Where did you buy your phone?
I bought it on Aliexpress with Goldway but sending it back for a replacement is not really an option for me.
hayatesan said:
So I shouldn't get any red lines when just taping right and left? I have those....
That's what happens to me and I'm getting back randomly after a few seconds of quickly taping left and right.
Where did you buy your phone?
I bought it on Aliexpress with Goldway but sending it back for a replacement is not really an option for me.
Click to expand...
Click to collapse
That lines get interpreted as swipes, so that's why my keyboard minimized when i was using it. If you want something more graphic you can try it on a simple drawing app (like this one), please look at the attached file. I live in Bolivia, here Xiaomi has official representation, so they come with a 15-month warranty.
Kristof_clg said:
That lines get interpreted as swipes, so that's why my keyboard minimized when i was using it. If you want something more graphic you can try it on a simple drawing app (like this one), please look at the attached file. I live in Bolivia, here Xiaomi has official representation, so they come with a 15-month warranty.
Click to expand...
Click to collapse
So this shouldn't happen at all?
Please see image attached.
Could other users confirm that when they just tap left and right very quickly, no lines are created? Thanks!
Xiaomi now sells directly in France but I have the 8/256 version only sold in China for now anyway.
Now it happens to me from time to time to have the keybord closed with a "false" back, but not enough to really think there was an issue, I just didn't understand why it closed. Thanks for pointing that, now I'm gonna be annoyed each time.
hayatesan said:
So this shouldn't happen at all?
Please see image attached.
Could other users confirm that when they just tap left and right very quickly, no lines are created? Thanks!
Xiaomi now sells directly in France but I have the 8/256 version only sold in China for now anyway.
Now it happens to me from time to time to have the keybord closed with a "false" back, but not enough to really think there was an issue, I just didn't understand why it closed. Thanks for pointing that, now I'm gonna be annoyed each time.
Click to expand...
Click to collapse
But hey, you know what i did in the meantime? I installed XDA Gestures, configured the same gestures as MIUI, and hid the gesture pill. Voilà, you get the same but without that problem. :good: That's good for now.
Kristof_clg said:
But hey, you know what i did in the meantime? I installed XDA Gestures, configured the same gestures as MIUI, and hid the gesture pill. Voilà, you get the same but without that problem. :good: That's good for now.
Click to expand...
Click to collapse
You mean:
1) Put back navigation bar on MIUI, disable gesture
2) Install XDA gesture and remove the navbar, configure it as MIUI
3) ?????
4) Profit
Is that it?
There are quite some options in XDA Gesture settings, could you post a screenshot of your preferences (like the 4 screens) so I can copy them? Sorry to bother you with this!
Also instead of using the sides to swipe back, it will use the lower part of the screen only? That's how your fix works?
hayatesan said:
You mean:
1) Put back navigation bar on MIUI, disable gesture
2) Install XDA gesture and remove the navbar, configure it as MIUI
3) ?????
4) Profit
Is that it?
There are quite some options in XDA Gesture settings, could you post a screenshot of your preferences (like the 4 screens) so I can copy them? Sorry to bother you with this!
Also instead of using the sides to swipe back, it will use the lower part of the screen only? That's how your fix works?
Click to expand...
Click to collapse
Here are the settings attached (the pill color is transparent), just changed the right swipe to go to last app, instead of back. Remember that to install XDA Gestures you have to use ADB from your PC/Mac, for that to work you have to enable both "USB Debugging" toggles shown in the screenshot.
Does attached mean my unit is ok?
Kristof_clg said:
Here are the settings attached (the pill color is transparent), just changed the right swipe to go to last app, instead of back. Remember that to install XDA Gestures you have to use ADB from your PC/Mac, for that to work you have to enable both "USB Debugging" toggles shown in the screenshot.
Click to expand...
Click to collapse
Thanks a lot, gonna do that on monday, just waiting for my bootloader waiting period to end (I know I can to this without root or anything, but as I'll need to do it again....)
Just to confirm, this means the gestures will be at the bottom of the screen only, no back function from the edge, right ? I don't think it will bother me much if this is like that.
---------- Post added at 01:31 PM ---------- Previous post was at 01:30 PM ----------
vince_junior said:
Does attached mean my unit is ok?
Click to expand...
Click to collapse
Seems to be fine, if you were tapping fast each side, this is perfect. I can't manage to do this without having false swipe.