I searched to see if anyone has made this already so this will come in handy.
SHOULD WORK ON ALL VARIANTS FOR THE NOTE 2
What does this mod do?
It disables the voice input method.
All Google apps still work. Voice search still works as well nothing to worry about.
Does this remove any apps?
No! All it does is disable the voice input
Will it "break" any apps?
No
This mod changes the XML files for ime and input prefences in Velvet.apk under system/app
Please hit thanks if you use this
Kinuser1 said:
I searched to see if anyone has made this already so this will come in handy.
SHOULD WORK ON ALL VARIANTS FOR THE NOTE 2
What does this mod do?
It disables the voice input method.
All Google apps still work. Voice search still works as well nothing to worry about.
Does this remove any apps?
No! All it does is disable the voice input
Will it "break" any apps?
No
This mod changes the XML files for ime and input prefences in Velvet.apk under system/app
Click to expand...
Click to collapse
Finally, i have problem when using Light Flow App, when i open any folder, My note says: The folder is opened, same when close it
My solution was disable google speak engine and samsung TTS from application manager.
Will try ur mod now, thx.
Edit : flashed and voice still working !!
If this mod doesn't work then go to accessibility And turn talk back off (if it is on) turn talk back on then back off. I had this issue. It's just a glitch.
Kinuser1 said:
If this mod doesn't work then go to accessibility And turn talk back off (if it is on) turn talk back on then back off. I had this issue. It's just a glitch.
Click to expand...
Click to collapse
Man, first thing i do when install any rom that is uninstall TalkBack
GonDr said:
Man, first thing i do when install any rom that is uninstall TalkBack
Click to expand...
Click to collapse
Are you still having problems? What causes it and what exactly happens
EDIT: the problem is with The light flow app itself. For the time being disable accessibility and it will go away. I'll find a way to mod the sounds in accessibility so you won't have issues
Any ideas if this will work on other Samsung devices? I'm on a Galaxy Ace 2, will it cause the universe to implode if I try it? This could be just what I'm looking for.
edithswanneck said:
Any ideas if this will work on other Samsung devices? I'm on a Galaxy Ace 2, will it cause the universe to implode if I try it? This could be just what I'm looking for.
Click to expand...
Click to collapse
Bit late but what version is it on?
Kinuser1 said:
Bit late but what version is it on?
Click to expand...
Click to collapse
I have no need for it any more but thanks for the reply.
Related
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.
I've installed the Google Now Launcher and microphone icon is perpetually "empty." Checked that hotword detection was enabled in settings as well. I had Nova Launcher installed pre-wipe/root/flash to SlimKat and for some reason it remains in the icons list and I can't get rid of it. Not sure if related to the issue. Thanks!
nex4fanboy said:
I've installed the Google Now Launcher and microphone icon is perpetually "empty." Checked that hotword detection was enabled in settings as well. I had Nova Launcher installed pre-wipe/root/flash to SlimKat and for some reason it remains in the icons list and I can't get rid of it. Not sure if related to the issue. Thanks!
Click to expand...
Click to collapse
do you have google search installed ? If yes, check whether it is configured properly. Open it and keep on pressing next until you see google now.
Tell me the feedback afterwards.
lokesh.3440 said:
do you have google search installed ? If yes, check whether it is configured properly. Open it and keep on pressing next until you see google now.
Tell me the feedback afterwards.
Click to expand...
Click to collapse
I've done all of that already, still the same microphone that isn't filled in and therefore isn't listening.
Hi everyone,
I decided to reflash stock and i'm running into some problems with enabling accessibility services for greenify and pushbullet. Somehow I managed to turn these on, I have then turned pushbullet off with no issues. Trying to re-enable this I get the "Use Pushbullet?" prompt with the cancel and OK buttons. I am unable to click OK... only cancel works.
Does anyone else have this problem? I've reflashed about 3 times now... md5 of image is OK so I just wanted to see if you all can enable and disable accessibility services without any issues.
Thanks
altrstar said:
Hi everyone,
I decided to reflash stock and i'm running into some problems with enabling accessibility services for greenify and pushbullet. Somehow I managed to turn these on, I have then turned pushbullet off with no issues. Trying to re-enable this I get the "Use Pushbullet?" prompt with the cancel and OK buttons. I am unable to click OK... only cancel works.
Does anyone else have this problem? I've reflashed about 3 times now... md5 of image is OK so I just wanted to see if you all can enable and disable accessibility services without any issues.
Thanks
Click to expand...
Click to collapse
I have this exact same problem with every single app in Accessibility... I threw on Lollipop and have yet to be able to click OK. It doesn't even register as a button. Hopefully someone sees this and has a clue as to what is going on.
I wonder if this is a bug... :S
2953
I doubt it, or at least if it is it's a very small one since I have yet to see anything else about it. You're the first person I've encountered with the same issue, funny how you mention both Greenify and Pushbullet (I have both and I didn't notice the issue until after I tried enabling Greenify)
I can confirm it doesn't work for the Google builtin services either on my phone: Talkback / Switch Access
altrstar said:
I can confirm it doesn't work for the Google builtin services either on my phone: Talkback / Switch Access
Click to expand...
Click to collapse
I've been struggling with this exact issue on both my Nexus 5 and Nexus 7 wifi. Flash to stock, setup my account, start the restore process, apps start installing, I wait until either LastPass or AutoVoice are installed and then I can immediately go in and enable accessibility for it. Anything after than and it can't click on the OK button. My theory is that you get one shot at setting whatever applications. It's definitely a bug that not app or hardware specific.
slickie88 said:
I've been struggling with this exact issue on both my Nexus 5 and Nexus 7 wifi. Flash to stock, setup my account, start the restore process, apps start installing, I wait until either LastPass or AutoVoice are installed and then I can immediately go in and enable accessibility for it. Anything after than and it can't click on the OK button. My theory is that you get one shot at setting whatever applications. It's definitely a bug that not app or hardware specific.
Click to expand...
Click to collapse
I found the answer for my specific case. It was Lux that was preventing me from enabling accessibility or installing from unknown sources. Sooo many factory resets and reflashing stock/rooting and it was Lux the whole time. Arggg...
http://www.reddit.com/r/AndroidQues...installed_lollipop_cant_tap_install_or_grant/
I'm going to uninstall LUX and see what happens.
Sent from my Nexus 5 using XDA Free mobile app
You can just disable it in order to have accessibility settings working again.
slickie88 said:
I found the answer for my specific case. It was Lux that was preventing me from enabling accessibility or installing from unknown sources. Sooo many factory resets and reflashing stock/rooting and it was Lux the whole time. Arggg...
http://www.reddit.com/r/AndroidQues...installed_lollipop_cant_tap_install_or_grant/
Click to expand...
Click to collapse
Holy guacamole! It was LUX... I simply uninstalled LUX and I was then able to click OK on Accessibility settings. I'll be sending an email to LUX devs in a few minutes.
Although apparently I could just have disabled it... LOL. Either way the devs have been informed
Sent from my Nexus 5 using XDA Free mobile app
Kallaide said:
Holy guacamole! It was LUX... I simply uninstalled LUX and I was then able to click OK on Accessibility settings. I'll be sending an email to LUX devs in a few minutes.
Although apparently I could just have disabled it... LOL. Either way the devs have been informed
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Wow... Thanks for this! it works now.. damn i wiped my phone 3 times :S. Ah well at least battery life is now rocking!
Thanks for finding the root cause! Seems like we're a bunch of people using the same apps.
GOOD GRIEF! This was so annoying. THANK YOU! This was driving me crazy. I am writing this on Jan 7 2015, I dont think the author knows this is an issue. I will write to him/her. Thanks again. On a Nexus 6 5.0.1
Same problem with app called Twilight. Pausing the app allows OK button to register.
Same thing for "good sleep pro". Highly unexpected. Big thanks!
Sent from my Xperia Z3 using Tapatalk
For me it was "Bluelight Filter". Thanks for setting me in the right direction.
Not a Nexus 5 user but...
I still use a Sprint Galaxy Nexus (toroplus) but, it was Lux for me too. The two reasons I didn't think it could have been Lux are, first, after this same issue came to light with the install button on sideloaded apps, they made Lux auto pause on screens where their overlay could cause issues. Second, it's daytime where I am right now. The screen dimming overlay shouldn't be active during the day. Either way, I think I'll need to poke the Lux devs to inform them that their experimental work around still isn't working in the accessibility menu.
Anyway, thanks for pointing me in the right direction. I'll just have to remember to disable Lux when I need to perform protected actions.
Thank you! HTC One M8 user, and killing Lux helped!
ricardoq said:
Thank you! HTC One M8 user, and killing Lux helped!
Click to expand...
Click to collapse
THX to all of you. Once again Lux was the root cause.
I'm on a stock note 3 running lollipop
Kallaide said:
I have this exact same problem with every single app in Accessibility... I threw on Lollipop and have yet to be able to click OK. It doesn't even register as a button. Hopefully someone sees this and has a clue as to what is going on.
Click to expand...
Click to collapse
I have the same issue on my tmobile note 3 can't click OK in accessibility services settings
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.
I had given up on trying to make all of Androids little features work as they should. Now that I have picked up the Z Flip 3 I have a new found desire to figure out how to use the phone and the features that are giving me issues.
Issue 1 - The screen saver when charging is not working. I've tried my dock, and direct power plug in. No go on any of the screen savers- they simply do not show up. How can I fix or trouble shoot?
2- Please tell me it's possible to re-map the side power button to open the Google assistant. I spend a couple hours on this today and had no success. I tried downloading the assistant app so I could open it, but Samsung has hidden it in the pop up list of apps that can substitute the Bixby option. Same question - how to make it work.
3- I really want nothing to do with the Samsung apps. Is there any way to disable or otherwise get rid of them? Without rooting. Is rooting even possible? I don't really want to start with that again, but will if it comes to it I suppose.
I am trying not to waste days figuring out how to make the phone mine. It seems like everything I want, I can't make happen. So frustrating. Thanks for listening and thanks in advance for any help/guidance/resources etc.
Edited to add - this is a Google FI Samsung phone. I purchased it from Google.
2. https://play.google.com/store/apps/details?id=com.jamworks.sidekeybuttonremap
3. https://forum.xda-developers.com/t/...mate-app-manager-debloat-tool-tweaks.4147837/
Thanks! I tried it out, then purchased the button remapper app. It's working great!
I'll sit down and do the other suggestion also. Wish I didn't have to remove things and hope it doesn't break others in the process.
Thx again
pdxrealtor said:
Thanks! I tried it out, then purchased the button remapper app. It's working great!
I'll sit down and do the other suggestion also. Wish I didn't have to remove things and hope it doesn't break others in the process.
Thx again
Click to expand...
Click to collapse
Only disable the apps you can see an icon for in the launcher and those you are absolutely sure accompany them (ie. Stuff plainly named Bixby) and you'll be fine.
Got it! Thank you!! Will update when I've had the time to mess with it.
On another note- I can't for the life of me get the screen saver when charging to work. It's not that I'm dying to use that feature out of necessity, but it's driving me nuts that such a simple task is, simply not working. lol. I need to let it go.
[email protected] said:
2. https://play.google.com/store/apps/details?id=com.jamworks.sidekeybuttonremap
3. https://forum.xda-developers.com/t/...mate-app-manager-debloat-tool-tweaks.4147837/
Click to expand...
Click to collapse
How's number 3 compare to package disabler pro?
pdxrealtor said:
How's number 3 compare to package disabler pro?
Click to expand...
Click to collapse
it's free, and for me better.