Related
VAlert
Customize vibration on phone ring
This small program allows customizing vibration incoming call alerts.
Windows based phones vibrate either before the ring or constantly during the ring.
Having a short ringtone can possibly solve this problem, but with long mp3 ringtone the phone will constantly vibrate during the ring.
This program will enable Windows Mobile phones to produce short vibrations when the phone rings.
Vibration patterns can be easily changed by the user.
Possibly to match vibration patterns to the ringtone, so the phone will vibrate in a rhythm.
Very low (~4K) memory usage
This software is a freeware.
How to use
1. Install the CAB
2. Enjoy the program with default settings
3. The program is hidden by default. To display program window (if needed), run the program again
7. In Phone->Options make sure ring type is Vibrate and Ring
4. Edit script.txt to change vibration pattern. Every line in the file is a pair of vibration length and note pause
5. From the program window run Menu->Test to test the created pattern
6. Perform Menu->Hide to hide program window
What's new:
- More devices support, including non-HTC
- The installer executes the program upon installation (no soft reset required)
- No vibration on waiting call
- Support for incoming call ring mute (stop vibration)
- Silent start
- Even lower memory footprint - ~4K on standby (was 11K before)
sounds cool
gunna try now
you should make it so you tap the screen to show when u want it to vibrate instead of editing the .txt file
Edit: Great app but confusing to change the pattern
Edit2: lol doesnt seem to work on my vogue when i go to phone->options and press play its just a long vibrate
Ohh man i was about to post a thread on something like this. Thank you so much for making this!
Sounds nice. Will try it out. Thanks for sharing.
bedaweed said:
Edit2: lol doesnt seem to work on my vogue when i go to phone->options and press play its just a long vibrate
Click to expand...
Click to collapse
Play from phone options is not implemented. Open the program and click Menu->Test or just try an incoming call.
oh okay im gunna try now
hmm.it may be useful.thx.
bedaweed said:
you should make it so you tap the screen to show when u want it to vibrate instead of editing the .txt file
Edit: Great app but confusing to change the pattern
Click to expand...
Click to collapse
+ 100 i would guess
Downloading now,.
Thanks for sharing sir!
to save people the bother of working it out themselves, and to get everyone started...
here's my version of the Nokia classic message vibration
i can't hum it, so you'll need to try it, i guess!
Edit : Oh, by the way... is it possible to do something like this for recieving SMS / MMS / Email, or is that a different process altogether?
Dr J said:
Edit : Oh, by the way... is it possible to do something like this for recieving SMS / MMS / Email, or is that a different process altogether?
Click to expand...
Click to collapse
Yeah, that's what I wanted to ask too! Would be awesome, would be a very useful app, thanks. And yup, maybe an easier way to edit vibrates would be nice. However, it's cool now, for a version 1.
Future versions
Post your suggestions. I am making a list of changes for the next version.
Suggestions :
- a settings UI on the device (instead of having to pull the txt file off to PC and edit and then put back in on device)
- ability to change between multiple vibrate scripts (via drop-down menu or list?)
- if possible (?) ability to use vibrate scripts for SMS / MMS / Email / Other alerts
- vibe scripts that match pattern with the actual ring / message tone would be VERY cool
excellent little program, thanks a lot for the effort
if the other message alerts can be changed from within this (or even just another separate small app) it's just what i'm looking for!
and please can other people post their script efforts, it'd be good to have several pre-sets to start out with.
there might be a slight bug in this
a few calls have come through recently, the vibrate kicks in itself and the ringtone does not play for about 10 seconds or so.
also the programmed pattern seems distorted.
it might just be my device, as i'm noticing that S2U2's full screen call ID has been struggling to kick in when a call comes in these days since i started using Manilla2D as well.
it might be that the device is struggling to find the ID picture and the ringtone and the vibrate pattern at the same time, all the while trying to run M2D.
i'd check if it works correctly without all these extras running, but M2D and S2U2 are pretty much essentials for me these days.
anyone else care to help?
Dr J said:
there might be a slight bug in this
a few calls have come through recently, the vibrate kicks in itself and the ringtone does not play for about 10 seconds or so.
also the programmed pattern seems distorted.
it might just be my device, as i'm noticing that S2U2's full screen call ID has been struggling to kick in when a call comes in these days since i started using Manilla2D as well.
it might be that the device is struggling to find the ID picture and the ringtone and the vibrate pattern at the same time, all the while trying to run M2D.
i'd check if it works correctly without all these extras running, but M2D and S2U2 are pretty much essentials for me these days.
anyone else care to help?
Click to expand...
Click to collapse
Do you have this problem with all calls or just some?
What do you mean by distorted pattern?
Does this problem happens when VAlert is disabled?
Thanks works great on my prophet with 6.1
ochakov said:
Do you have this problem with all calls or just some?
What do you mean by distorted pattern?
Does this problem happens when VAlert is disabled?
Click to expand...
Click to collapse
i have that problem with calls but its only like 2 seconds not 10
Sounds nice. Will try it out. Thanks for sharing.
bedaweed said:
i have that problem with calls but its only like 2 seconds not 10
Click to expand...
Click to collapse
That's not a delay. By default (there is a registry setting to change it) the ring is delayed by 2 seconds. VAlert does not have that delay, so it will always start vibrating 2 seconds before the ring.
Nice tool... works goodm i like it!!!
i saw a post about ringer delay for AT&T user and they just need to disable the dialer and the problem solve but what about us sprint users? Here is the original post about that http://forum.xda-developers.com/showthread.php?t=449417
i tried to disable the dialer on registry but still get 2-3 second delay before my Touch Pro actually ring.
Download and install DiamondTweaks. There is an option to disable the ringer delay. Works well.
convert your ringer to .wav file
temperamentalman said:
Download and install DiamondTweaks. There is an option to disable the ringer delay. Works well.
Click to expand...
Click to collapse
The ringer delay that this changes is the pause between when the ringtone ends and it repeats. Not the delay from when the LED starts flashing (because a call arrived) till the phone actually starts ringing.
If you wish to turn off the HTC dialer and use the WM Dialer, simply goto the following registry entry,
[HKEY_LOCAL_MACHINE/Security/Phone/Skin]
"Enabled" = dword:1change the Enabled value from 1 to 0 which will disable the HTC dialer.
I vote for converting to WAV files as well.
If you would like to complain to Sprint about it, the following is the thread I started on Sprint's forum regarding this very subject.
http://forums.buzzaboutwireless.com/baw/board/message?board.id=SmartPhones&thread.id=5304
Thanks smotrs...
Know anyway to get the light sensor to turn off the screen when on a call (Sprint) other than S2U2?
temperamentalman said:
Thanks smotrs...
Know anyway to get the light sensor to turn off the screen when on a call (Sprint) other than S2U2?
Click to expand...
Click to collapse
Depends on what you may have done (adding programs, etc..) to your phone. By default, our devices will turn the screen off to conserve battery while a call is in session. However, if you have added one of the S2A dialer GSM versions which was taken from the Touch HD, that feature was disabled because of the InCall curtain. The CDMA versions (my signature and others) were taken from the Sprint Diamond ROM that was released and still contains the necessary code to turn off the screen display while the call is in progress.
Smotrs...just HR'd and installing now. I haven't tried that one, and actually think I ended up with the GSM version I WAS using.
I'll let you know how it works.
Thanks...
Well, it still sits there while the screen "times" out. I thought the light sensor was supposed to dim the screen almost immediately. I'm on the call for 30-40 seconds before it dims, and then cuts off.
Is this a Sprint thing?
temperamentalman said:
Well, it still sits there while the screen "times" out. I thought the light sensor was supposed to dim the screen almost immediately. I'm on the call for 30-40 seconds before it dims, and then cuts off.
Is this a Sprint thing?
Click to expand...
Click to collapse
It should Dim after about 10 seconds (or whatever you have in the backlight Advanced setting under Battery). After about 40 seconds or so (same location) it should turn off the screen.
At least that's what mine does, just verified it again. Sounds like maybe your values are too high. After a HR they usually are by default.
Somehow it was at 30 (dim) and 1 min (off). That is a little high. Changed it to 10 / 40. We'll see what that does.
Thanks for the tip. I'll keep you posted.
Seems to now be working the way you explained!!! Thank you for the help!
Is there anything else out there, other than S2U2 that allow FULL SCREEN Caller ID pictures??? I don't want to reinstall that because the dialer is actually working right. I just miss full screen caller ID.
Thanks again.
That I don't know, sorry.
Eh...it's ok. I'd much rather have a dialer that works than a full screen picture of my ignorant brother.
you can also change the Slot Cycle Index in the epst settings... you'll need your MSL though
it's under "Modem Settings"
What is slot cycle and where are these settings? How do I find my MSL? I don't see "Modem Settings".
not trying to be an ass, but i suggest you do some searching. there is plenty of info on the subject
check out this thread - http://forum.ppcgeeks.com/showthread.php?t=48775&highlight=epst+poll
or here - http://forum.ppcgeeks.com/showpost.php?p=625185&postcount=14
and here - http://forum.ppcgeeks.com/showthread.php?t=42730&highlight=epst+poll
I don't think you are an ass...I'm thinking thanks for the threads!
I know search is my friend LOL
lol, no prob man...
Changed the SCI to 1. We'll see if that helps. There is always "0"!
I'm also seeing mixed reports/opinions on ACCOLC - Access Overload Class. Mine was defaulted at 8 on Sprint. People say leave it alone. People say set it lower. Others say set it higher.
i found that setting SCI to 1 is good enough, i'm able to catch my calls and haven't noticed decreased battery life from it so that's where mine stays.
I had an old phone that had 3 or 4 different styles of vibration that you could set to different forms of communication. This came in very handy as I could tell immediately if the vibration was for an incoming call or just a text.
I can't find that feature on the Streak anywhere. THere is only one vibrate style. Would someone (smarter than me) be willing to look into ways to create different vibrate settings?
ie:
loooooooong short looooooong.
constant.
short short short.
This way even if the phone is hanging out in your back pocket on vibrate all day (like mine mostly is) while you are talking to customers, you know if it is something you can leave alone or if it is something you should check immediately.
You can this with Tasker, trigger it so that when a notification comes from another app then run a particular sequence of vibrations. I use it to give a vibrating alert to Bugme which has a sound and popup but no vibrating alert of it's own. If the app has a built in alert I guess you would just turn it off and use tasker to run the sequence you like. Tasker can look a little complicated at first but is very useful even to non-programmers like myself.
mellojoe said:
I had an old phone that had 3 or 4 different styles of vibration that you could set to different forms of communication. This came in very handy as I could tell immediately if the vibration was for an incoming call or just a text.
I can't find that feature on the Streak anywhere. THere is only one vibrate style. Would someone (smarter than me) be willing to look into ways to create different vibrate settings?
ie:
loooooooong short looooooong.
constant.
short short short.
This way even if the phone is hanging out in your back pocket on vibrate all day (like mine mostly is) while you are talking to customers, you know if it is something you can leave alone or if it is something you should check immediately.
Click to expand...
Click to collapse
Another option I use is to use handcent or chompsms you can customize your vibrate pattern for texts that way.
Sent from my Dell Streak using Tapatalk
Hi guys
This might be a basic question to most, but I´m posting it regardless;
On the standby state (screen off/all functions on) when a notification like a sms arrives the screen turns on for about 5 secs.
I find that timming a bit too short but could not find a way or options to get it a bit longer.
Any hints on this ?
thks in advance
i dont think there is an easy way...
didnt find anything related to this so in my opinion - its an inside setting that can be change only by changing the code itself.
10 seconds should be better...
Hey there.
One thing I remember from Gingerbread is how, when on lockscreen, the screen would turn off after some 7 secs. So say I wanted to check the clock I could just turn on the screen and put the phone away again. On JB it seems like it uses the same timeout setting as the rest of the system, one I keep at 1 min..
Is there a way to make to make it seperate? I want the screen to turn off after 10 secs when Im on the lockscreen, so I dont have to press the, quite, inconviniently placed power button on my phone, each time (seeing as I got tap2wake on my phone)
Kocayine said:
Hey there.
One thing I remember from Gingerbread is how, when on lockscreen, the screen would turn off after some 7 secs. So say I wanted to check the clock I could just turn on the screen and put the phone away again. On JB it seems like it uses the same timeout setting as the rest of the system, one I keep at 1 min..
Is there a way to make to make it seperate? I want the screen to turn off after 10 secs when Im on the lockscreen, so I dont have to press the, quite, inconviniently placed power button on my phone, each time (seeing as I got tap2wake on my phone)
Click to expand...
Click to collapse
You can try my app, KinScreen. It allows setting a different timeout for the lockscreen. However, the lockscreen timeout doesn't seem to have an effect in KitKat (where the default is 10s).
Kocayine said:
Hey there.
One thing I remember from Gingerbread is how, when on lockscreen, the screen would turn off after some 7 secs. So say I wanted to check the clock I could just turn on the screen and put the phone away again. On JB it seems like it uses the same timeout setting as the rest of the system, one I keep at 1 min..
Is there a way to make to make it seperate? I want the screen to turn off after 10 secs when Im on the lockscreen, so I dont have to press the, quite, inconviniently placed power button on my phone, each time (seeing as I got tap2wake on my phone)
Click to expand...
Click to collapse
Have you found a way to do this? My new 4.3 JB smartphone used to have a lockscreen screen timeout of 5 seconds, which I liked, but somehow it is now something like 30 seconds... which is TOO long for my liking... I've tried any combination of settings to revert this but with no luck...
BTW, 30 seconds is not even my screen timeout ... I have it set to 1 minute. So... I have absolutely no clues...
MegaSharkXDA said:
Have you found a way to do this? My new 4.3 JB smartphone used to have a lockscreen screen timeout of 5 seconds, which I liked, but somehow it is now something like 30 seconds... which is TOO long for my liking... I've tried any combination of settings to revert this but with no luck...
BTW, 30 seconds is not even my screen timeout ... I have it set to 1 minute. So... I have absolutely no clues...
Click to expand...
Click to collapse
Only way I could come up with was to use Tasker. Make a profile that does when on lockscreen timeout is 7 secs and when not its 1 minute.
Not very ideal.
Kocayine said:
Only way I could come up with was to use Tasker. Make a profile that does when on lockscreen timeout is 7 secs and when not its 1 minute.
Not very ideal.
Click to expand...
Click to collapse
Can you share how was your Tasker profile created? I remember trying to do a similar profile on my previous smartphone (actually it was running KitKat) and I couldn't figure a way for a profile to detect lockscreen for the timeout to be set differently.
Also you can't set it below 7 seconds....
Interestingly enough, I suspect Tasker was the reason why I lost my "short" lockscreen screen timeout in the first place on my new smartphone
MegaSharkXDA said:
Can you share how was your Tasker profile created? I remember trying to do a similar profile on my previous smartphone (actually it was running KitKat) and I couldn't figure a way for a profile to detect lockscreen for the timeout to be set differently.
Also you can't set it below 7 seconds....
Interestingly enough, I suspect Tasker was the reason why I lost my "short" lockscreen screen timeout in the first place on my new smartphone
Click to expand...
Click to collapse
That was indeed the trick. To detect the lockscreen. I came across this plugin:
https://bitbucket.org/laceous/android-atlockscreen/wiki/Home
AtLockScreenTaskerConditionPlugin.1.0.0.apk
AtLockScreenTaskerSettingPlugin.1.0.1.apk
Those you'll need. It runs a background service, without battery drain ofcourse, that uses something 4 mb ram.
Attached is the entire "project" you can import to get something that works.
Kocayine said:
That was indeed the trick. To detect the lockscreen. I came across this plugin:
https://bitbucket.org/laceous/android-atlockscreen/wiki/Home
AtLockScreenTaskerConditionPlugin.1.0.0.apk
AtLockScreenTaskerSettingPlugin.1.0.1.apk
Those you'll need. It runs a background service, without battery drain ofcourse, that uses something 4 mb ram.
Attached is the entire "project" you can import to get something that works.
Click to expand...
Click to collapse
Thanks! But I managed to do it yesterday all by myself just using Tasker and nothing else wanna know how?
MegaSharkXDA said:
Thanks! But I managed to do it yesterday all by myself just using Tasker and nothing else wanna know how?
Click to expand...
Click to collapse
Yes we want to know how! What Android version? I haven't been able to change the lockscreen timeout on KitKat from the default 10s (higher or lower) on stock Nexus 5 ROM.
Sent from my Nexus 5
Flyview said:
Yes we want to know how! What Android version? I haven't been able to change the lockscreen timeout on KitKat from the default 10s (higher or lower) on stock Nexus 5 ROM.
Sent from my Nexus 5
Click to expand...
Click to collapse
So basically this is set by using two profiles:
. Event Screen on -» Display timeout 7 seconds
. Event Screen unlocked -» Display timeout 60 seconds
The only caveat I can think of is that instantly lock after sleep should be activated to prevent false positives.
Now if only I could set the timeout to a value lower than 7 seconds...
MegaSharkXDA said:
So basically this is set by using two profiles:
. Event Screen on -» Display timeout 7 seconds
. Event Screen unlocked -» Display timeout 60 seconds
The only caveat I can think of is that instantly lock after sleep should be activated to prevent false positives.
Now if only I could set the timeout to a value lower than 7 seconds...
Click to expand...
Click to collapse
Cool.
However, the reason I didn't go with something like this is because there's times where I'll have the lockscreen disabled thru a widget OR if I wake up right after it had turned the screen off (and there's a time of 5-15 secs before actually locking the phone). That would result in having an extremely fast dispaly timeout at times where it's not actually wanted. The way I've gone about it ensures, for the most part, that it only applies when locked.