For all events/calls/notifications/etc, I want my vibration intensity set to max so when my phone is in my pocket I can be sure to feel it going off. However, when I'm using it I want a more mild intensity on key presses.
Does anyone know of a way/mod/app that would allow me to have this "dual" intensity?
From the little bit of looking I've done, I'm suspecting the answer is no, but I can always hope
Thanks for any insight.
Kidd_Funkadelic
I used to have a vibration app from the market called smart vibrator I believe. Hope this is want you're looking for.
FrankenCleaned & Coma Volted
I've been running gingerbread ROMs since the day I received my phone, and one of the few things about it that bugs me is the increased haptic feedback response. It vibrates so strongly that the phone rattles with each keystroke. Is there any sort of variable I can modify, perhaps in some system configuration file, to adjust the intensity of the haptic feedback? I'd rather not have to disable it entirely, as it does help me to type more reliably.
Sent from my ATRIX running CherryBlur 1.2.
I'm having trouble with the vibration intensity on my SGS2...it is very inconsistent...when I set it to where I want it, after awhile I'll notice that I can't feel any haptic feedback either on the keyboard or the buttons. I'll go back in to the settings and they'd be the same, but I'd increase and I could feel it again, but then after awhile the intensity will be way too high and I'll have to go back and set it where I had it previously.
This seems like it might be a hardware issue as it did it with the stock rom as well as UnNamed. Any other ideas?
I have always left mine at the default level, and haven't has issues on stock or UnNamed or S8. Do you only have this problem after changing the default setting? Does it happen if you don't change the intensity from default?
Sent from my Galaxy S II (i777)
I never messed with it until I noticed I couldn't feel it anymore...I wonder if it could be the A.I. Type keyboard I'm using, it has its own haptic intensity settings too, I suppose it could be interfering with the global setting...the problem is that it just seems to change on its own...
I had a problem using the gingerbread keyboard from the market, having issues with vibration, but only within the keyboard. The problem never effected my global settings. Try a different keyboard and see if the problem persists. I like the stock keyboard or swiftkey. I have heard you can get it free from getjar.com.
Sent from my Galaxy S II (i777)
I disabled the AI Type and enabled the stock Samsung keyboard and it's the same. I can go into settings/sound/vibration intensity and move the slider up and down and I can feel the different intensities just fine, very strong on the high end of the scale...but as of right now, whatever I select it makes no difference to the actual intensity I get from the buttons, it never changes...wierd.
Hello all
I have a OnePlus One running CM12 (unofficial). My haptic feedback for virtual button presses is very weak. I *may* have affected performance of the motor a when trying to solder a Qi receiver into the handset, as I accidentally touched the battery live to the motor causing it to run at full power for a few seconds. Otherwise, I could be totally imagining it and it could be caused by CM12 [edit: I have tried Paranoid Android and it is super weak on PA too]. Either way, I just want to make the haptic feedback duration for virtual button presses a few milliseconds longer so it's more noticable.
I have managed to do this for Google Keyboard in the app settings and it works nicely.
Otherwise, vibration intensity is set to maximum, which is good for notifications, but I really need to increase the duration, not the intensity. Is there a way to do this in Android... like the equivalent of a registry tweak or something?
Thanks
Mike
EDIT: I found an old post here which explains that (at least on Gingerbread):
If you want to set your own values they are located in the framework-res.apk\res\values\arrays
Click to expand...
Click to collapse
Being a total amateur, I have no idea how to edit these - any suggestions?
Change the minimum brightness level from usual 10 to 1. It doesn't modify the autobrightness level map so automatic brightness won't be lowered (though it can be easily adjusted on CM11).
This is so far exactly the same as GravityBox offers (modifying 'config_screenBrightnessSettingMinimum').
But Minimum Brightness offers one unique feature - it also modifies the lower brightness levels in MX Player (free/paid). Because no matter whatever you use manual or auto brightness, MX Player always uses minimum brightness of 0.05 (12/255, 19/255, 27/255, 36/255...). To actually lower the brightness, you would have to turn off brightness control in MX Player or use one of many 'overlay filter brightness app'.
So Minimum Brightness module retains the same quadratic function for brightness levels but includes lower values (1/255, 4/255, 9/255, 16/255, 25/255...).
Minimum Brightness uses value 1/255 which might not be suitable for every display (meaning LCD) but it suits perfectly my Super AMOLED screens (Galaxy S5 / Galaxy Tab S 8.4) and watching videos at night is still enjoyable.
There are many excellent auto brightness apps (Lux, Darker etc) that can use overlay filters to lower brightness even more so it's up to everyone to try and decide.
This module has been merged into new module http://forum.xda-developers.com/xposed/modules/mod-xposed-tweaks-cm-t3279109. Please check that module for any future updates.
Hello! Thanks for the mod, I will test
Works very nice on Xperia Z2, however minimum brightness is absolute darkness Could you please add an option to define minimum brightness value?
_mysiak_ said:
Works very nice on Xperia Z2, however minimum brightness is absolute darkness Could you please add an option to define minimum brightness value?
Click to expand...
Click to collapse
The situation is the same on my Xperia SP. When I set the brightness to miniumum the screen is totally black, also when the backlight decreases after 10 seconds screen gets black.
Hi! Tried min brightness but when screen is set to the lowest level, I get a white screen after locking the phone.
Sent from my DIAMOND D1 using XDA Free mobile app
Really great tweak!! I'm noobie in Android enviroment with my new Elephone P3000S and the lowest screen brightness is to high for me so your tweak is very usefull.
I also have the issue that the lowest brightness level sets the screen completly black and I have been scared for 1 hour truing to solve a completely black, touching all buttons but the phone didn't "wake up". Finally, pressing power buttom + volumen up + home soft key it has worked :angel:
So it would be very important to prevent black screen by allowing the user to set the minimun level.
Thanks!
Hey, I know making GUI is a pain in the ass so can you please make alternative version with minimum brightness set to 2? That will satisfy most of people complaining here. Your app is currently the only dimmer working on lollipop.
Dri0m said:
Hey, I know making GUI is a pain in the ass so can you please make alternative version with minimum brightness set to 2? That will satisfy most of people complaining here. Your app is currently the only dimmer working on lollipop.
Click to expand...
Click to collapse
I will have a new device soon so that could make me change my mind about lowest value and UI.
@Dri0m
In the first post you can find archive containing multiple versions of module with different low values.
How to disable this module...?
I installed this module last night, enabled it in Xposed Framework, but did nothing with it. Then this afternoon I opened the Settings menu, went to Display, and before I could do anything else I received a phone call. As I terminated the call, the screen flashed, the phone rebooted--and after restarting it is completely, or almost completely blank. If I repeatedly tap the power button I get a fraction-of-a-second glimpse of the SIM PIN screen at normal brightness. This leads me to the suspicion that, by some weird combination of bad luck and an accidental touch of a finger after terminating the phone call, that the Minimum Brightness somehow got set--although why the phone then rebooted I don't know.
Anyway, by luck and good judgement I finally managed to enter the correct SIM PIN and then the phone unlock PIN. However, I can do nothing else. The screen is still blank, and as the phone is currently unlocked I don't want to touch the power button. Before sending the phone back to the manufacturer or anything drastic like that, I would like to try disabling the Xposed Framework. Whilst trying to find something useful in Windows Explorer I found Xposed-Disabler-Recovery.zip in the Internal storage\Android\data\de.robv.android.xposed.installer\files folder on my phone. I assume that this should be what I need. However, as I cannot see anything on the screen I would need to know the exact buttons to press, in which order and how many times etc, in order to enter the Recovery menu and do what is needed. According to the phone manufacturer the OS is unmodified Android 4.4.2., although strangely they will not even tell me which keys to press to enter the Recovery menu (long story, the upshot is, they flat out refuse to help apart from suggesting returning the phone).
Note that I only suspect it is the Minimum Brightness module that is causing the problem, however the problem did not exist before yesterday (when I installed the module), and as I was about to do something with the brightness when the phone rebooted itself, it seems too much of a coincidence to be anything else. If I cannot disable the module/framework, the only other thing I can think of is a factory reset--but again I would need to know exactly which buttons to press, in which order etc. Unfortunately at the moment USB debugging is not enabled, and again without the screen I cannot access it to turn it on.
Any help or suggestions hugely appreciated.
PL
@Papalazzzaru
Xposed now sports a safemode which allows you to disable Xposed during bootloops. To disable Xposed, you'll have to repeatedly tap one of the hardware buttons (Power, Volume, or Home) on your device during startup.
During boot, your device will vibrate twice when it detects the first key press. You'll then have five seconds to press that same button four more times, with each keystroke producing a short single vibration. After ending with a long vibration, your device will disable and prevent most of Xposed's actions, allowing you to easily troubleshoot problematic modules.
Sorted
Outstanding, thanks.
Papalazzzaru said:
I installed thi............. gely appreciated.
PL
Click to expand...
Click to collapse
Device model please?
Caterpillar S50, on Android 4.4.2, baseband version LTE_S0201121.0_S50_0.017.00.
it is compatible with lollipop?
imam88 said:
it is compatible with lollipop?
Click to expand...
Click to collapse
The MX Player part still works. I don't know about the lowest value of brightness in general but at least with CM12 & Samsung the brightness goes to the hardware minimum by default.
Thanks, this is exactly what I want.
Could you make it for LP ?
I want my phone be absolute zero brightness for driving navigation.
Tested it on CM12.1 Nightly on the Nexus 6. It works here, but on 0 the screen is a bit purple. However, I guess this is the screen's fault
Gesendet von meinem Nexus 6 mit Tapatalk
moneytoo said:
The MX Player part still works. I don't know about the lowest value of brightness in general but at least with CM12 & Samsung the brightness goes to the hardware minimum by default.
Click to expand...
Click to collapse
Yes it works
This module seems to be working well on the Moto X Pure Edition (Motorola xt1095) running Lollipop 5.1. It's an AMOLED screen, and I personally find the minimum brightness on 5.1 too bright, so this has helped solve that.