So does anyone else have a Pressy here? I can't seem to get mine to work with this phone. Every time I insert it, the message would pop up that I had pressed the button. Even if I didn't and used my nails without pressing the button I would still get that message. It works perfectly fine with my Nexus 5 though. I also noticed that the Pressy goes pretty deep but the message pops up before it even goes all the way in. Any solutions?
I have had continuous issues with Marshmallow and the Pressy. If you read some of the comments on their Kickstarter, we are not alone. They pretty much adandoned this project and moved on to some silly dice.
You may want to check out some 3rd party apps for this
PaisanNYC said:
I have had continuous issues with Marshmallow and the Pressy. If you read some of the comments on their Kickstarter, we are not alone. They pretty much adandoned this project and moved on to some silly dice.
You may want to check out some 3rd party apps for this
Click to expand...
Click to collapse
Wow thanks for that. Backers worked mad hard to bring their project together. I backed $20 myself instead of just buying the $2 XiaoMi one. This is really sad to see them abandon their Backers like that.
I'm not actually have trouble with the app. I just can't seem to get the button plugged in without the message saying I pressed the button even when I didn't. I believe it works on my MM Nexus 5 though. Need to check again.
PaisanNYC said:
You may want to check out some 3rd party apps for this
Click to expand...
Click to collapse
I removed my Pressy with marshmallow since it wasn't working. I'd be interested to know if you've found any good replacement 3rd party apps.
Marcellus1 said:
I removed my Pressy with marshmallow since it wasn't working. I'd be interested to know if you've found any good replacement 3rd party apps.
Click to expand...
Click to collapse
I am sorry but I haven't even looked. I gave up on Pressy. They will not answer any questions on Pressy, but they have no problems spamming me with their new kickstarter campaign
Had to remove Pressy from phone one year ago when I got an Android Wear. Has been an expensive keychain ever since. No updates, no love for us. Shame on you, Nimrod
I had a problem with the audio not being redirected correctly when Pressy was plugged in which resulted in the microphone not working (Nexus 5 stock Marshmallow). This was never an issue for me on Lollipop.
I have found an app called KeyCut that seems to work for Pressy and various other similar products. I've switched to using it instead of the Pressy app and it seems to have fixed the microphone problem for me.
KeyCut
I remember being so excited for the Pressy. The the $2 clone came out and neither ended up working well.
I was excited about pressy as well. Unfortunately it's been sitting in my desk since I got it because it's never worked right.
http://www.androidpolice.com/2014/08/26/pressy-review-i-had-no-clue-something-could-suck-this-badly/
Is this the thing you guys are talking about?
If so, what does it do? (Or supposed to do?) The article doesn't do a good job of explaining it.
]SK[ said:
It just adds a button to the phone so you can assign an action to it like open the camera etc.
I purchase a cheap Chinese version a while back. I plugged it into my Nexus 5, said "neat" and put it back in it's box to never use it again. Cool idea but pretty pointless IMO.
Click to expand...
Click to collapse
Thanks
Teleshot said:
I have found an app called KeyCut that seems to work for Pressy and various other similar products. I've switched to using it instead of the Pressy app and it seems to have fixed the microphone problem for me.
KeyCut
Click to expand...
Click to collapse
Thanks Teleshot. I tried the KeyCut app. It works well but there was still some additional functionality that Pressy had that I preferred so I kept looking for other options. I just came across an app called SoundAbout that based on my testing so far seems to do the trick. There may be other settings you could use to get things working, but these are the settings in the app that I used.
1. Turn the service on (you can choose the On - No Status option if you don't want a notification in your notification bar).
2. Set media and phone call audio to the speaker.
3. Set alert behavior -> wired headset behavior to phone speaker (or phone speaker + headset).
4. In connectable devices -> wired headset settings: allow plug in/out detection, ignore microphone for wired headset, ignore plug-in volume when wired headset plugged in.
I've tested app audio; microphone recording; always listening; phone: ringer, conversation, speakerphone. All of it seems to be working fine and I can also use Pressy the same as before the Marshmallow update. I'll try it with bluetooth audio later.
For using headphones (which I rarely do), turn the service off or set the media and phone call audio to the headset rather than speaker.
PlayStore: SoundAbout
Marcellus1 said:
...I just came across an app called SoundAbout that based on my testing so far seems to do the trick...All of it seems to be working fine and I can also use Pressy the same as before the Marshmallow update...
Click to expand...
Click to collapse
Not certain how you came across this app in searching for a Pressy fix, yet alone how you discovered the particular settings to restore functionality but it's great to hear this nevertheless.
Unfortunately, I tried applying your settings on my 6P (unlocked bootloader, original factory recovery, not rooted) but they did not seem to work as none of my presses were detected by the Pressy app.
Android 6.0.1, Pressy 1.0.27 and SoundAbout 2.6.6.6
Related
Just got my new G2X this morning. I came from a N1.
I generally like the phone and got it to address a couple of problems I had with the N1 (handset speaker went out and I only could talk via speaker or BT, sticky buttons, and continuous switching between EDGE/3G).
I can overlook the display bleed, the fact that I HATE where the power button is located, trackball, LED notifications (boy, will I miss those) and can (I think) tolerate the lack of early android updates.
There are couple of other things that REALLY bug me, though, and was wondering if anyone else was experiencing it and if there were any solutions. (Yeah, I searched the 'net today but haven't come up with any thing elegant). I don't have these problems on the N1 so could probably tolerate it and return the G2X until more appropriate hardware was out. (Maybe sensation? Although I don't like large screens on my phone)
1. Bluetooth lag. There is a significant (sometimes 1-2 seconds) lag between the time my phone generates sounds and when my BT headset picks them up (Jawbone Icon).
2. BT/Handset simultaneous sounds. I liked the fact that when my BT headset was connected, the handset speaker would mute and all sounds would only come through the headset. This does not happen that way with the G2X - is there a way to change it?
3. So I have two places for storage and by default, most of the apps point to the internal one and can't be changed to point to the external (I was able to point the camera storage to external at least, whew!). Any known workaround?
4. Task killer can't kill certain apps. I get a message saying that 2.2 didn't allow 3rd party apps to cancel processes. Never noticed this on the N1.
5. Car Home - I'm sure a lot of people find this useful, but I don't. Is there any way to supress this from coming up? Sometimes I get it when I connect my BT headset. At other times it doesn't show up until I get a call.
I really want to like this phone, but aside from 4G, it seems like it isn't much more than a minor improvement over my N1...
I can't help you on 1-3, but...
4) Task killers on android do more harm than good.*
5) Root the phone. It's REALLY simple. Download some drivers for your PC, download the program, connect your phone, run it, boom, rooted. Download Titanium Backup, find Car Home, freeze it.
more info on rooting
I myself coming from a N1 I keep looking at the N1 wanting to reach for it and throw my SIM back in and cry holding it. Wish I could put new guts in it and make it more update.
1. the track ball my thumb keeps reaching for and its not there
2. Two storage places I dont like either
3. The bleed isn't bad on mine but Im going to wait a week and take it back and try another g2x out before my buyer's remorse period is up.
4. I'm very surprised at you coming from a N1 that you use task killers very surprised and I'm gonna keep my eye on your.
cliffy15 said:
1. Bluetooth lag. There is a significant (sometimes 1-2 seconds) lag between the time my phone generates sounds and when my BT headset picks them up (Jawbone Icon).
Click to expand...
Click to collapse
I have a BlueAnt Q2 and have no issues with Bluetooth. Phone to headset and headset to phone are almost instantaneous.
2. BT/Handset simultaneous sounds. I liked the fact that when my BT headset was connected, the handset speaker would mute and all sounds would only come through the headset. This does not happen that way with the G2X - is there a way to change it?
Click to expand...
Click to collapse
My G2 used to work that way too. The G2X and my headset work like yours. It drives me crazy but I don't think there's a fix. Oddly, in my car, it play signals through the car's speakers when I wish it wouldn't. So that seems to indicate the connected device has something to do with it.
5. Car Home - I'm sure a lot of people find this useful, but I don't. Is there any way to supress this from coming up? Sometimes I get it when I connect my BT headset. At other times it doesn't show up until I get a call.
Click to expand...
Click to collapse
You could disable it under settings with HTC phones. Settings on the G2X take you to Android settings. I kill the process when I reboot the phone.
Thanks for the info!
lance713: yeah, assuming this phone makes it past the return date, I'm going to have to root it. I was never really was into custom roms, but I think I may start soon.
lance713/wondercoolguy: btw, I don't use task killers for much ... but coverage is spotty here (Hawaii) and I kill things when they get interrupted mid-task because they wait and "search" for awhile, killing my battery. I also kill gallery and messages when they have the occasional hang.
Guess I'll have to get used to no trackball/pad. My only other consideration was the Sensation (I really don't want most of the Sense UI) and that doesn't have one, either.
Rooting and flashing with different rom, will not fixed the screen bleeding problem or charging problem, that causes the phone to reboot. Those are hardware flaws
I can help with one of your issues the LED Notifications. Check out NoLED Settings in the Android Market by a fellow XDA developer member. It works great and highly customizable.
Came from an N1 myself.
Solution: Flash CM7
You'll feel right at home!
led notification
try lg2/black notifications from the market place.
I found something interesting on the Amazon store I thought I would share, I found this is incredibly useful for me so hopefully is to someone else.
this should work on pretty much any Android device but I'm posting it here as it is the only one I can/have tested it on.
I cannot post links yet but it can be found on Amazon UK under the name "Satechi BT MediaRemote Bluetooth Multi-Media Remote Control"
It's a small Bluetooth remote for iPad/iPhone/Mac and very quietly mentions Android so I decided to buy one and see how it goes as I needed something like it for my car.
Anyway it arrived this morning and I love it, I've successfully used it and I've been able to remap keys using the "External Keyboard Helper Pro" app by "Apedroid" which allows remapping of keys to media keys or launching apps.
All keys on the remote can be remapped except the wireless symbol which un-pairs and goes into discover mode.
My requirements were a remote that allows me to change tracks while driving but it also got Google now working in my car Bluetooth system. (it did not connect properly when I launched it via car voice controls)
I have now got the keyboard button remapped to switch to the maps app and the mute button to launch Google now so once Google now is done I have a button to go back to the navigation screen .
I have also been fairly successful in getting this to work with Tasker however it required a small workaround by exporting the task as an app (via Tasker App Factory) and then using "External Keyboard Helper Pro" to launch it.
My only issue with the remote at the moment is that it connects as a hardware keyboard meaning I cannot type while using it (obviously not an issue in the car though)
All this was done on a non rooted Nexus 4 on 4.4.2 so root is not required by the way.
If anyone has any questions feel free to ask, I'm going to figure out how I can bind the other 9 keys on the remote
Oh and finally if you do use the app in question and use Tasker I'd recommend exporting a Tasker task which launches the intent "android.intent.action.VOICE_COMMAND" rather than using the built in voice control key setting.
Dude!! I have totally been looking for this! I like playing podcasts from my phone while I'm working in the garage, so I hook the phone up to my stereo but whenever I need to pause it or adjust the volume, I gotta go clean up or slide out from under the car... This will be perfect!! I'm totally ordering this right now!! Thanks brother (or sister?)!!
Sent from my Nexus 7 using Tapatalk
Cazomino05 said:
...
Click to expand...
Click to collapse
Seems very good indeed.
http://www.amazon.com/gp/product/B00DY9UFB8/ref=cm_cd_asin_lnk
http://www.satechi.net/index.php/satechi-bluetooth-remote-control-for-android
Could you please check if there are any answer call buttons or microphones on this thing? Personally I hope not because it happens so easy in your pocket.
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.
Hi All,
Recently I got my xperia xz dual sim and directly updated it to Nougat.. So dont know how it is on 6.x
I noticed something weird. Basically with whatsapp notification sounds so far. When i get a whatsapp message, sometimes the notificatiom tone works normally and sometimes it is cut.. I mean sometimes i hear just the first part of it.. Did anyone see this problem?
Thanks in advance,
Did anyone face that?
Thanks,
any news friends?
Seriously no one noticed it? :fingers-crossed:
I don't use WhatsApp, but I noticed another weird notification glitch. And this may seem different to yours, unfortunately.
I have an app (my local ISP's) which, very rarely, pops a notification regarding an offer or a service update. And when that happens, the notification sound is different (something I did not set as it is not customisable) and, worse, it JUST DOES NOT STOP! It keeps buzzing and buzzing and buzzing. Dismissing the text from the drop-down does not shut it either, and I am forced to restart the device. This didn't happen with any other app, though (and most of those pop up notifications way more often).
Likewise, another annoying bug I noticed was that the phone/system update notifier became a constant presence in the drop-down even if THERE WAS NO UPDATE on offer from Sony.
Full resets did not help and, anyway, I decided to move on. Cashed in on an attractive offer and traded it for a Google Pixel earlier today.
I hope you find a solution to yours, a_k_gano.
kartnite said:
I don't use WhatsApp, but I noticed another weird notification glitch. And this may seem different to yours, unfortunately.
I have an app (my local ISP's) which, very rarely, pops a notification regarding an offer or a service update. And when that happens, the notification sound is different (something I did not set as it is not customisable) and, worse, it JUST DOES NOT STOP! It keeps buzzing and buzzing and buzzing. Dismissing the text from the drop-down does not shut it either, and I am forced to restart the device. This didn't happen with any other app, though (and most of those pop up notifications way more often).
Likewise, another annoying bug I noticed was that the phone/system update notifier became a constant presence in the drop-down even if THERE WAS NO UPDATE on offer from Sony.
Full resets did not help and, anyway, I decided to move on. Cashed in on an attractive offer and traded it for a Google Pixel earlier today.
I hope you find a solution to yours, a_k_gano.
Click to expand...
Click to collapse
Thanks alot for your reply. it is different than mine.. seems everyone has his own impact
Did you try reinstalling WhatsApp?
On that note, I noticed notification and ringer sounds to "cut" abruptly when I tried listening to them while, for example, choosing a tone (be it notification, alarm or ringer). I am referring to the sounds menu under Settings. Come to think, this comes closest to what you have described and no, I didn't find a solution to that either.
kartnite said:
Did you try reinstalling WhatsApp?
On that note, I noticed notification and ringer sounds to "cut" abruptly when I tried listening to them while, for example, choosing a tone (be it notification, alarm or ringer). I am referring to the sounds menu under Settings. Come to think, this comes closest to what you have described and no, I didn't find a solution to that either.
Click to expand...
Click to collapse
this happens to me randomly... when i receive a notification, sometimes it cuts and sometimes it works normally... mainly happens with whatsapp or this is what i noticed so far. I reinstalled whatsapp, I did factory reset to the phone... but no progress so far.
I can say.. for two days after the 7.1.1 SW update, the problem stopped happening
Oh good! I did get an alert on my email that a new update is ready. But I don't have the phone, traded it up for a Pixel.
This is 7.1.1 and not 7.1.2?
you use whatsapp beta or original one from play store
7.1.1 don't have the problem
kartnite said:
Oh good! I did get an alert on my email that a new update is ready. But I don't have the phone, traded it up for a Pixel.
This is 7.1.1 and not 7.1.2?
Click to expand...
Click to collapse
it is 7.1.1
karrouma said:
you use whatsapp beta or original one from play store
7.1.1 don't have the problem
Click to expand...
Click to collapse
I use original from playstore
There's this warning, when you use headphones, and get volume up. It's something like "too high volume can damage your hearing, are you sure", or something like that. Any way to disable this? It's freaking annoying.
I second this question - really annoying for me when using AUX cable in the car...
SystemUI Tuner in Play Store has that option, and it doesn't require root. The one by Zachary Warden. It uses ADB.
myweca said:
SystemUI Tuner in Play Store has that option, and it doesn't require root. The one by Zachary Warden. It uses ADB.
Click to expand...
Click to collapse
I don't know if you tried it but on 10.5.9 seems not to be working
Seems to work fine for me...
exnokiafan said:
I don't know if you tried it but on 10.5.9 seems not to be working
Click to expand...
Click to collapse
Have you run the adb commands?
Hi frieds, all I want is to say a BIG BIG THANKS to you. I've spent a long (very long) time trying to find a way to remove the fateful and disgusting Safe Volume Warning message, I use a bluetooth connection with my car to send the music to the car's audio system and from time to time I get the disgusting message.
Now I have installed the app that you have mentioned, having carried out all the ADB commands, and it seems that... IT WORKS. It's too early to say, but I've been rebooting several times and I've tried every time with headphones where it used to appear the warning, and now FINALLY NOT ANYMORE!!!