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.
Related
I want to get back to Screebl this fall and roll version 3.0. I'm going to focus on updating it to make it more 2.3/3.0+ friendly, and try to spend some time on dealing with the variety of issues that come in the form of "I've installed my own custom ROM on my toaster and Screebl doesn't work", which may mean simplifying things a bit. But I digress.
You guys at xda are the most demanding, critical, unrelenting, inflexible, opinionated crowd that I know of. You're also pretty smart. I'm curious to hear what those of you that use the app want to see in a 3.0 release.
dk
Surprised no one has chimed in here yet. First off I would like to say that Screebl is easily my favourite app, even though I mostly forget it is there. Whenever anyone new to Android asks what apps to install, Screebl is at the top of my list. OK, now that the brown nosing is out of the way...
Note: I have a Samsung Epic, currently running the latest leaked build of GB (EH06 as of writing this).
I would like some clarity on the interaction of Screebl and docks. For some reason I can't seem to figure out if it is ever enabled/disabled correctly while docked.
Ever since I started running GB leaks, Screebl has shot to the top of the battery consumption list. This may not be a Screebl issue, but instead something to do with how GB measures battery performance?
I would be nice to include the option to control time between screen off and screen locking.
A slider for choosing the maintained screen brightness, and/or the option to set it to the phone's default.
The option of a 'night mode', with different settings for maintained screen brightness and screen timeout.
Different settings for timeout while on the lock screen vs homescreen vs apps.
Glad to hear you'll get back to this app soon.
Since I updated my Galaxy S to 2.3.4 it stopped working.
I was so sad about this. Now my phone always turns off the screen without me wanting it to..
Wish you good work on it.
Peace
I have a couple of D2Gs running Gingerbread, since the update to Gingerbread the greatest consumer of battery life is the Display, I regularly see 40-60% usage and often only minutes of actual time on.
It seems to be a conflict between the built-in auto brightness and the Screebl low brightness setting. Low brightness is great except when you pull the phone out of your pocket and need to see something at midday...
I discovered that the Juicedefender brightness control manages to keep the brightness at a super low level most of the time, but still auto brightens the screen when required in bright light.
I guess my feature request would be either to have an option to completely remove the brightness control or to take it over with a system that keeps it on minimum brightness but with an user controllable setting to auto increase the backlight when the light sensor detects a particular value.
Thanks for a great app!
I need to update the docs and settings descriptions, but choosing "min brightness" will defer to the phone's sensor generally. That's what I use on my phones.
Dock stuff has been flaky and needs some revamping. I'm planning on redoing the entire loop and eventing framework for the app. It's gotten crazy complicated with all of the device-specific tweaks and conditions involved.
Support for custom lockscreens would be nice. E.g. disable Screebl when MiLocker is in the foreground. Had to stop using Screebl since I started to use MiLocker becuase I can't stand the stock ugly lockscreen.
Just wanted to give those of you that registered interest in Screebl 3.0 a heads up that I've done a ground-up rewrite of the app. It's in beta now -- not pretty, but the underlying engine should be better in many ways, including:
- more compatible with a larger number of devices (moved the accelerometer usage to more modern APIs)
- better with respect to power consumption
- simplified, removed some of the functionality that just didn't work well (like stillness detection)
Still lots of work and polish left to do, but if you want to play with the latest engine, take a look here:
https://market.android.com/details?id=com.keyes.screebl.beta
Let me know what you think!
keyesdav said:
Still lots of work and polish left to do, but if you want to play with the latest engine, take a look here:
https://market.android.com/details?id=com.keyes.screebl.beta
Let me know what you think!
Click to expand...
Click to collapse
I just tried Screebl Beta, and noticed that the proximity sensor is always on, even though the checkbox for it is not checked.
They way I can tell, is that with one of my old phones, the proximity sensor actually glows a faint red light when it's on. To save battery, shouldn't the sensor be off if the checkbox is not checked ?
Firstly, let me say thanks on producing a great app. Always my first installation on any new device.
I've had a small issue on my nexus 5, running 4.4.2 where screebl lite and screebl beta keep turning themselves off. It happens roughly once a day and I have to go into settings and re-enable screebl. Its only a niggle, and not worth uninstallation thankfully.
Good luck on Version 3. :victory:
i have both sgs1 and sgs 2...i have noticed one thing ..that the haptic feedback in sgs2 is not as responsive and not as instense as it used to be in sgs1...is it only with me or otherz have also noticed this thing....??
Have you tried lowering/maximizing the vibrating intensity in Settings?
And if you did, only thing i could think of is they lowered the intensity on the SGS2 deliberatily because then it saves battery compared to the intensity on the SGS1. (i never had a SGS1, so it's a wild guess)
Regards.
Sent from my GT-I9100 using XDA App
BryanNL said:
Have you tried lowering/maximizing the vibrating intensity in Settings?
And if you did, only thing i could think of is they lowered the intensity on the SGS2 deliberatily because then it saves battery compared to the intensity on the SGS1. (i never had a SGS1, so it's a wild guess)
yea i tried everythng ...but still no good
Click to expand...
Click to collapse
Which keyboard do you use? Use the swype-keyboard. That way the haptic is a bit stronger. You don't need to necessarily swype using Swype keyboard, you can also type on it and it's neat to have all symbols under the normal keys (long press for symbol). Give it a try and let me know if it changes anything.
Sent from my GT-I9100 using XDA App
I used to use s.e. W810, recently switched to xperia mini. Everything is pretty nice but the vibration level. It's barely sensible. When I have my phone in my jean pocket switched to silent mode, I feel nothing and when I check it to see whether there is any notification, usually I got ,say, 3 messages and 2 missing call
So, it's obvious that I don't feel the vibration. Searched a little about it, but neither could find anyone suffers from that problem like I do nor a solution to increase vibration level. However thought that maybe by reaching the phone's system files that can be feasible. So, is it possible to do that, if so, how ?
Thanks in advance.
I've not had a problem with it, but there are also apps to allow you to make your own vibration patterns. So maybe something with a bit more stop/start would help?
melenko said:
I've not had a problem with it, but there are also apps to allow you to make your own vibration patterns. So maybe something with a bit more stop/start would help?
Click to expand...
Click to collapse
Thanks for your suggestion but the problem is not the pattern but the level of the vibration definitely. I compared it with other phones and it's really not that high like old phones.
Go sms pro can help you define how many miliseconds the vibration for a notification for a new text should last. haven't used any app which can do the same for incoming calls, but it should exist somewhere in the market!
Actually what I'm looking for is to be able to increase the power of the motor inside the phone which creates those vibrations. This is adjustable for sure, cause for instance as typing it vibrates very slowly. So, by playing with codes they can be achieved, at least as theoretically
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?
Often get many messages and notifications that go noticed as the vibration is very weak. Is there anyway to adjust the intensity?
I really wish there as a way, it's pathetic. I don't think I've managed to notice a single call when I'm walking... I think I might have to switch phones because of this. I've managed to work out almost everything else to be how I want it, but even with root (which I don't have yet), I can't see a way around this one. There are some apps that change vibration pattern and those might help but intensity is a no go I think... Oh well, love the phone so a bit gutted to be honest...