Mecool KM3 volume dialogue notification - Android Q&A, Help & Troubleshooting

I gave my parents my old mecool km3 when I bought my shield. after a day of having the shield remote I grabbed the original one remote and paired there more firestick remote to the km3. figured that's work better for them since the km3 doesn't control the volume on there 42" lg and the firestick remote does. so they don't have to use 2 separate remotes. so issue is everytime the volume button is pressed it adjusts the volume on the TV and the volume on the box. the little volume notification 8con thing that pops up on the side of the screen. well I'm tired of seeing it and they are too lol. so how do I get it to not show up since the firestick remote can control the tv volume. I've tried button mapper and went and clicked customize the volume buttons and selected no action when they are pressed but it doesn't work. still shows up. I tried all the button settings and won't work. but it'll work on my shield though. if I turn off volume cec control I'll get the same volume notification on the side when adjusting volume so I went Into button mapper on the shield and it'll work on the shield. I can get it to not register anything when pressing volume button on shield so why doesn't it work on the one? all other button mapping settings work on the km3. I even tried ultra volume apk because where you can go In and set the transparency to full transparent and guess what. that doesn't work on the km3 either but guess what again. it'll work on the shield. so wtf

Related

MP3 player with hold function

Does anyone know of an mp3 player that has a hold function where tapping the screen won't work or a player that will still work after my sx56 is turned off. Also I bought the cheap earbud headphones off AT&T's website. Is there anyway to map the answer phone button to have other functions (such as next track).
I asked a very similar question in these forums recently, and got the perfect answer: WMP already allows you to lock the screen.
In the player, go to Tools -> Settings -> Buttons and map 'Screen toggle' to one of your hardware buttons. (I mapped it to the 'Action' button - the centre of the cursor.) Now, when I press this button while WMP is playing, the screen is turned off and locked.
Hope this helps.
otherwise winampaq
mapping the button on my earpiece
Is there anyway I can map the answer call button on my earpiece to goto the next track. I keep my sx56 in my pocket and it is annoying to have to reach in to hit the next track. Also when I am wearing the earbuds it would be nice to have the answer call button a mappable button. Thanks.
great, but not quite there
it's a great improvement, which does indeed disable the screen, but not the buttons.
I'd just like some kind of lock that disables both the screen and the keys, a la nokia phones.
cheers
M

Allshare - Volume Buttons

Anyone noticed that when controlling another player using allshare on your phone that the volume buttons (on screen or rocker) are incredibly incremental. I've sat in front of the computer holding the volume rocker and watch WMP's volume barely slide upward.
Is there a hacked up app- or is it possible to create a hacked up app- that adjusts the volume in larger increments?

[Q] TianHe h920+ and wired headset controls

I recently purchased the TianHe h920+, a Chinese phone that seems to be nearly the exact same as the Mlais MX58 pro, among others. My issue is that my wired one button headset does not work properly with controlling my device. Long presses do not launch Google Now, and two/three repeated presses do not active next song/previous song with music players. This headset works fine with my old Samsung Captivate, so it's not the headset's problem, but the phone's.
After some digging, I installed the KeyTest app, and it turns out that two key presses are registered when the button is pressed down, scanCodes 88 and 164. scanCoe 88 apears first, followed by a registering of scanCode 164 after a second or two. Holding down the button first triggers scanCode 88, and occasionally scanCode 166. However, the little counter for "repeatCount" does not tick up, unlike when I hold down the capactive back or menu keys, or the volume rocker. After much more digging, I finally found the key layout file that the phone uses, and was able to remap 164 from MEDIA_PLAY_PAUSE to MEDIA_NEXT, which in turn let me use the Headset Button Controller app.
But the problems don't end there. Even after commenting out scanCode 88 with a "#", Android still recognizes that scanCode 88 is pressed when the button is pushed down, and this interrupts the repeated key presses, as well as press and hold functions of Headset Button Controller. Anyone have any ideas?

Gravity Box module volume control issue

I've been using Gravity Box a few days now and noticed a problem. When it's running and I turn the volume up, if I press the cog symbol on the right it only displays one volume control and not four. Before I installed this I could change the volume for calls, notifications, media and system but now I can't. Any idea if there's a fix?
I use Gravity Box so I can change music tracks when screen is turned off with volume controls
Scratch that I've found it!
It's in 'media tweaks' then 'expandable volume panel'
mike710_0 said:
I've been using Gravity Box a few days now and noticed a problem. When it's running and I turn the volume up, if I press the cog symbol on the right it only displays one volume control and not four. Before I installed this I could change the volume for calls, notifications, media and system but now I can't. Any idea if there's a fix?
I use Gravity Box so I can change music tracks when screen is turned off with volume controls
Scratch that I've found it!
It's in 'media tweaks' then 'expandable volume panel'
Click to expand...
Click to collapse
Same Issue On Note 3. FIXED! Thanks

How to get Volume buttons to wake phone in Lolipop (CM12.1)?

Edit: this is no longer an issue in CM13.0 snapshot. I went ahead and upgraded and can confirm volume rocker wake (and double tap to wake) work.
Hi All I'm on CM12.1 (MT2L03 cm-12.1-20151117-SNAPSHOT-YOG7DAO1K2-mt2) and can't seem to figure this out. I had the volume buttons waking the phone from screen off in 4.3 working great...I used that for quite a while (since I used the option to end calls with power button need volume buttons to wake screen also saves wear to power button) so the hardware supports it but not sure how to get it working on lolipop (CM12.1).
In Jellybean, I just had to add 'WAKE' after the volume keys like:
key 115 VOLUME_UP WAKE (in /system/user/keylayout to the kl files)
I tried this for CM 12.1 and it doesn't seem to work. Since it worked before I suppose it could work again if a setting is changed or something.
Also I tried adding:
ro.config.hwfeature_wakeupkey=1
to my build.prop and rebooting and that didn't work either. (Setting it to 0 disables volume key waking)
The xposed module XUtilities option: Volume rocker wake also did not work.
The xposed module GravityBox doesn't have the option or I didn't see it there.
There's this reference:
http://cyanogenmod.github.io/cm_pla...ers/CMSettings.System.html#VOLUME_WAKE_SCREEN
which refers to VOLUME_WAKE_SCREEN setting (in CM API)
In the Buttons section of CM's settings, I have the End call (Pressing the power button will end the current call) option ON. One would think this would allow the volume buttons to wake the screen if the screen goes off during a phone call so you can wake it back up without ending the call. Also with this option on, on more than one occasion I went to turn my phone on just as an incoming call came in and used the power button which ended the call...so I've gotten in the habit of using the volume up/down buttons to turn on the screen getting around that issue (also saving wear and tear on my power button).
There's an app in the play store that can do what I want called DTSO (fails after time) VPL by prasi but it stays running and uses more battery power. The hardware solution that was working in 4.3 didn't require a background app to allow this feature and also didn't require extra battery power. So this isn't ideal. I'd rather have Cyanogenmod ROM directly support it or have a way to use it with it.
I want to be able to press the volume buttons and the screen come on like it used to. How?
Thank you for any suggestions :fingers-crossed::good:

Categories

Resources