My current Zenfone 5 RR Nougat vibration hardware keys are too strong in my opinion.
Is there any way to lower it?
If Google had vibration density on keypress controller and it's working fine. (pic}
So there must be a way to change the vibration of hardware keys one, right?
ps
google search got me nothing
There used to be an Xposed module for lollipop they could do this. I too, have been looking for a solution to this in later versions of Android.
Related
For as long as I can remember the haptic feedback and vibration intensity on my phone has been quite weak compared to other android phones I've played with. After a while I resigned to the fact that it was a hardware problem and nothing on XDA could help me. I was wrong though.
After flashing the froyo MIUI ROM available in the dev forum my haptic feedback was suddenly much stronger. There was an especially noticeable difference with the capacitive buttons below the screen. Since then I've switched between MIUI and several stock-based 2.3/2.3 ROMs and only MIUI has ever felt "right" when it comes to capacitive feedback. I actually really like MIUI for reasons other than this but I can't quite bring myself to use it full time until a few more bugs are worked out.
Wondering if anyone else has this issue and if there's anything I can do to fix it.
Do you have your vibration intensity turned all the way up?
Setting -> Sounds -> Vibration Intensity.
Yes I do. 10char
Hi everybody, i upgraded to the OP5 midnight black from my OP3 with LineageOS and as last year, I'm trying to stay on OxygenOS for as long as possible
Basically I like OOS, but there are some things that just don't make sense to me (those things are not new, but I noticed them when switching back to OOS):
- Dash charge sound: when i plug in the dash charger, i see this lightning animation followed by a sound/jingle. I can't check right now, but I think this only happens when the screen is not unlocked, but also when the phone is on silent/DND mode. At least give us an option to deactivate it.
- Ringer volume to zero: I'm perfectly happy with the stock android volume management. All, DND, and silent - most of the time my phone is in my pocket or in my hands, thus i do not want a ringtone. Sometimes the phone is on my desk and i'm some meters away - that's when i need a ringtone. On LineageOS/Stock Android, i could just raise the ringer volume from zero to the volume i want. On OOS, things are different and I do not like it. Why change it in the first place?
- also i'd like to control the media volume with the volume rocker keys by default (i change ringer volume maybe once a week). this used to be an option in one of the LineageOS / Cyanogenmod versions I think.
- camera disables flash when battery is under 15%. Most of us are grown up people who should be able to decide for themselves if they want to save battery or take a good photo.
- minimum brightness is to high for me and auto brightness is buggy.
- button backlight is too short / only lit after a button is touched.
What do you guys think about these things? Are you annoyed as well or do you think these "features" are legit? If you know of mods/hacks/tricks to fix one of the problems, feel free to share. thanks in advance :good:
Most of these things have already been criticized on the OP3/T and brought to OnePlus' attention months ago.
They didn't listen unfortunately.
Especially the fact that we can't mute our phones with the volume down button is mind-boggling!
Been this way since OOS 3.5 Marshmallow Beta1 on the OP3 and users started complaining. We are at Beta 18 + numerous stable builds later.
I think it speaks for itself.
I'm missing DND mode + vibration because of this.
Also when the device is on the upmost slider position (silent),
it will also silence android wear devices and render them useless for notifications!
tukiii said:
...minimum brightness is to high for me and auto brightness is buggy. ...:
Click to expand...
Click to collapse
I use Lux (on playstore) which completely overrides the built in auto brightness with an easier to control alternative. To use plugins requires root but I am not using plugs on my OP5.
3DSammy said:
I use Lux (on playstore) which completely overrides the built in auto brightness with an easier to control alternative. To use plugins requires root but I am not using plugs on my OP5.
Click to expand...
Click to collapse
That app got buggy on marshmallow - is it any better in N? Doesn't look like it's been updated in over a year. (Just curious.)
Elnrik said:
That app got buggy on marshmallow - is it any better in N? Doesn't look like it's been updated in over a year. (Just curious.)
Click to expand...
Click to collapse
I didn't have any issues with it on AICP Nougat 7.1.2 on a TabS SM-T800. Now on the OP5 (v4.5.4) it works well although occasionally it does not seem to start on a reboot but with so many OTAs so quickly I can't nail when that started. Its also not a consistent issue. Once started it sticks and works as advertised. Lux has been part of every Android device I've owned for a long while now. I really like using the profiles for example one for inside, outside and watching videos (Youtube, Netflx, Plex ...).
Hello all!
Anyone else notice that the keypress vibration is insane when typing? I tried SwiftKey and lowered the vibration to its lowest setting and it stays the same. Also tried G Board and it's still the same. I switched the vibration under setting for touch to light but same issue..
Same for me. After rooting and installing a custom kernel...it's possible to adjust vibration via a kernel manager.
Same here. I just put in for an RMA thinking my vibrator is defective because the vibrator is way too strong to be good haptic feedback for the keyboard. Every other OP has very fine tunability for key pressing. The OP5 is over the top! Not sure now if I should proceed with the RMA or not....
JonDeutsch said:
Same here. I just put in for an RMA thinking my vibrator is defective because the vibrator is way too strong to be good haptic feedback for the keyboard. Every other OP has very fine tunability for key pressing. The OP5 is over the top! Not sure now if I should proceed with the RMA or not....
Click to expand...
Click to collapse
Bro that is such a software fix, don't trip, mine vibration is strong on swiftkey too.
Rebel7022 said:
Bro that is such a software fix, don't trip, mine vibration is strong on swiftkey too.
Click to expand...
Click to collapse
Does your vibrator also have a "long decay" whenever its activated? Like when I get a call or press a key, the vibrator almost feels like a spring and it doesn't stop as quickly as it starts.
This is why I felt the my unit may be defective. But it could just be the nature of this new more powerful vibrator. I was just surprised that nobody else (and our reviews) mentioned it until this lone thread.
With my current phone, I use Wake Gestures extensively while driving to change tracks and play/pause with the screen off.
I would assume that the G6 would work with it, because of it having double-tap-to-wake, but for all I know DT2W is actually part of the always-on-display or something.
I plan on getting a V30 when they get around to releasing the carrier-less variant, so it would be nice to know in advance if it's likely to work.
Recently i have installed pixel experience rom (PixelExperience_land-10.0-20200122-1928).
The capcitive buttons aren't working. The gesture control not working properly. I have tried many times change the settings to hardware key to gesture control but nothing working. Is it the problem with pixel rom or others too. Need help
My Redmi 3s too has problem with Capacitive buttons. Was using quick ball with Stock ROM. Flashed PixelExperience_Plus_land-10.0-20201122-1450-OFFICIAL build assuming that gesture navigation will help. But it looks like only back gesture is working. Home gesture and switch app gesture are not working. 2 & 3 Button navigation option is also not working.
Any other ROM's where gesture navigation is fine with redmi 3s ?
Same issue is seen in FLOS 18.1 too. So it does not look like it is specific to Pixel experience.
Check with a different ROM. When I had first encountered such issues I had put it down to the software. But later the touch issues kept getting worse and about 6 months later the touchscreen was completely dead. This seems to be a rather common issue in this device.