Database Info

Htc Touch Pro (Raphael 500) Running Android , How to overclock?

Alright so Yesterday I installed the android os on my touch pro (raph 500)
i orginally have windows mobile 6.5 which is preety fast
but android is really slow!
i turned off all the settings which i would think it used alot of memory but still no help, so i started seeing videos on overclcking?
can someone explain to me on how to do this,
with links to the download
i really need to speed this up ,it would be amazing if it worked.
also if you give me a response that helps me , ill donate 10.00+ to you .

I do not require funds as I enjoy helping out!
From THIS thread and THIS post:
Overclocking
acpuclock.oc_freq_khz=XXXXXX ( suggested 600000-640000 )
but it is very unstable if you try to get higher than 650000-700000
Click to expand...
Click to collapse
Basically, you add that to the startup.txt file somewhere between the parentheses with an added space between the next command. Keeping in mind, with added OC, you may and may not notice a difference in stability. I honestly never use OC and I am using FroYo from THIS thread. Additionally you can try out Gingerbread Alpha from THIS thread. Please leave feedback in their respective threads, thanks!
n-Joie! (Enjoy)

thanks but this is my startup text :
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 acpuclock.force_turbo=1"
boot
Click to expand...
Click to collapse
so which am i supposed to edit, sorry im a noob lol
& u said that was the one you used,
is it fast?

Actually, I can't use that one because I have an at&t Fuze. If you have a RAPH500, you might want to use the following:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 pm.sleep_mode=1 acpuclock.oc_freq_khz=XXXXXX"
boot
Click to expand...
Click to collapse
Where XXXXXX is equal to a value between 600000-640000
Additional note: make sure you type something like 600000 or any value up to 640000

lol thanks im trying to see if theres a difference in speed.
but you used froyo?
is that running fast?

It's running fine with sync and a few other apps running in the background. I would be mindful of livewallpaper and HQ video at the moment as this project is currently still under development, at best. At least that is what I have noticed as far as performance is considered. I have also run a stripped Gingerbread alpha build (the one I linked you to earlier) and it is running faster/smoother than FroYo. To be expected without all the bells and whistles...
NOTE: Speed is relative to performance at the moment. Hence why I say it's still under development...

intresting ill test that out in about 15 mins
but does yours take a long time to come out of sleep mode?

Hmmm, that might be the notorious sleep of death SOD. I usually do something that most don't like but I sort of turn off the screen time out by first making the screen time out greater than 10 or 30 minutes. After that it should make things easier as far as disabling the auto back light/screen timeout feature. Keep in mind this is only a work around, I believe there is mention of actually fixing this issue. You'll need to download a free app called batterybooster (use the link if you want to read up on it a little). Once installed, run it and look for the far right icon and tap it. Set the timeout to Never and you'll notice a decent performance enhancement in the screen off and screen on.
NOTE: You will need to manually turn it off from here-on. You can try to play around with the setting but I find it somewhat problematic. Meaning that if you enable the timeout, it might and it might not work.

alright well i tried the gingerbread and that didnt work it lagged .
i tried froyo , it was amazing then i found out wifi didnt work
so now im back to the regular android one i had before ill be trying to see if theres a difference now that i "overclocked" it .
but thanks for all the help.
ill post back if i need something!

Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.

R^7Z said:
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
Click to expand...
Click to collapse
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .

ndnmaster096 said:
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
Click to expand...
Click to collapse
NVM I got the wifi to work now .

Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock

R^7Z said:
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
Click to expand...
Click to collapse
well i set it to never timeout and i have a lock pattern
but since it never times out it wont lock .

also now im starting to notice froyo is rebooting for some weird reason automatically .

Calm down, that is kind of "usual behavior" . There are quire a few things going on and the OS is attempting to "handle it". Sometimes it can't and just quits instead of freezing up ( which would be the lesser of two evils ). To get it to lock, you will have to turn it off manually (power button). Unfortunately, I think if the keyboad slides out, it self unlocks (kind of a self defeating purpose, more or less). If you turn the screen off and wait like 10 seconds then turn the screen on (power key), you should see the lock. I can't say for sure but it does work for me. I don't really have much time for troubleshooting today, as I am at work currently but do look over the threads I linked you to earlier if at all possible.

okay so i turned it off using the power button and it booted to windows mobile (odd)
then i tried running haret.exe & got this message:
"The file HARET cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. IF the problem persists, try reinstalling or restoring the file."
im not sure what to do.
i tryed reformatting the card and installing fresh files, which didnt work so now im left questioned?

When you say you turned it off, did you hold the button or just press it once? If you pressed it once, then, that is definitly not "usual" behavior. I recall having that issue once upon a time but for the life of me, I don't recall what I did to recover from it. However, it sounds like you are attempting to run from a shortcut that references the program(haret) that is no longer there. To resolve this, I need you to confirm that you are running from the microSD and not a shortcut. Also, you aren't formatting under windows, right? If you are formatting from windows, that would be a "no-no"
Find something like the HP tool (can be googled) that everyone else talks of or even something like the free version of partition wizard should work.

i held the button and it gave me options
1) airplane mode
2)shutoff
3)vibrate
i did try to make a shortcut but i deleted it and now when i checked i was running it from the actual application.
lastly, i did format from windows but i downloaded hp format tool
and formated my device in quick format.
reinstalled the programs and it still gave me the same error message,
please help, i really miss android =(

Try deleting data.img and letting it recreate the file. To clarify about the screen off issue, when you press the power button once (not hold), what does it do? Also, which kernel package are you using and have you attempted to download a newer kernel package yet?
Also, try THIS kernel package; I got it from THIS site. It looks like that kernel package is specific to our devices.

[Problem] JBOOGIE'S LIQUIDARC

So if anyone is using jboogie's liquidarc rom, i have a question for you: can anyone succesfully run setcpu and milestone or setvsel and successfully overclock/undervolt and scale the cpu? when i do those and run the scaling script from sorensim's guide on modifying the defy, my home and search button stop working, haptic feedback works on them, but they dont do anything when pressed. I love this rom but i cant use it if those 2 keys dont work. ive wiped before and after restoring the rom, flashed the sbf 3.4.11 first and then restored, and then the boot sbf, and still no progess. any tips?

Is usb debugging enabled or disabled? Not sure if this will help, but worth a try to switch back and forth to see if it helps. I have been using liquidarc for a few weeks now and loving it with no real issues to speak of. I was using milestone (what came with rom), but have since removed and gone back to setvsel and have overclocked/undervolted without any issues. All my buttons work.
You might need to redo the steps, and download the files again as perhaps a file was corrupted during download/installation?

i dont see how usb debugging could be a problem, but ill try

I popped onto modmymobile...looks like jboogie just replied to your question.

darule_2011 said:
I popped onto modmymobile...looks like jboogie just replied to your question.
Click to expand...
Click to collapse
yeah i just saw, thanks for replying though

well problem still happens, dosent matter if i use setcpu, milestone, or setvsel, dosent matter if i dont overclock, just cpu scaling, it still happens

I had to shift to his wonderful Korean rom only because of this issue. Any app I use, end up with nonfunctioning home button and search button.

chaihg said:
I had to shift to his wonderful Korean rom only because of this issue. Any app I use, end up with nonfunctioning home button and search button.
Click to expand...
Click to collapse
ok jboogie showed me a fix, dont touch vsel or threshold and it should work perfectly.

zencoran said:
ok jboogie showed me a fix, dont touch vsel or threshold and it should work perfectly.
Click to expand...
Click to collapse
? I use SetvSel and it works perfectly..
I change the threshold to 84% and change completely the others.. They're still working. I got this problem too with Pays-Rom 5.1. The home button still had haptic feedback, but didn't function.

WIIstpM said:
? I use SetvSel and it works perfectly..
I change the threshold to 84% and change completely the others.. They're still working. I got this problem too with Pays-Rom 5.1. The home button still had haptic feedback, but didn't function.
Click to expand...
Click to collapse
jboogie told me not to touch the threshold and it should be fine so idk

i got no problem with LiquidArc and running SetVsel

[Confirmed solution/work around] dialer battery drain issue on gingerbread 2.3.3.

Hi I don't know if this is the right place to put this info.
I see lots of people are having the dialer battery drain issue in pretty much every version of android 2.3.3. And I haven't seen a working solution anywhere other than upgrade to a newer version of android.
Any way, I'm using a HTC legend a gingerbread version 2.3.3, and I have always had the dreaded dialer battery drain issue.
I have found a work around that helps stop the drain, at least on the HTC legend 2.3.3 version I'm using.
In my case it is simply having the line
gsm.proximity.enable=false
In the build.prop
It would seam to stop the proximity sensor from working with the dialer part of phone.
The only side effect I have seen so far is that the screen won't turn off when u hold phone upto your ear, you can of course turn screen off with power button, at least from a legend point of view.
I hope this information will help others with android 2.3.3 on other phones that also have dialer battery drain.
Sent from my HTC Legend using XDA App

Hi, here's a bit of an update for those that are interested, even though the proximity sensor has been disabled for phone calls after adding the line to build.prop, here is a work around to allow the proxy to turn off screen again.
Down load "proximity screen off" from the market, in the settings, select enable during calls only.
Now on my phone the other settings seam to be a bit screwy so you'll have to play with them to suite your device for the way you want it to work.
I am still testing to see how battery life is, but so far its looking good.
If you feel like it, I would appreciate some feedback regarding these mods.
Thanks
Sent from my HTC Legend using XDA App

another point of attack
So.. It seems CyanogenMod team has identified these proximity sensor issues and actually fixed most all of them (on the devices they support). The answer is complicated and nestled into the code. But basically one could say there has been an omission of suspend and wake calls that now make MANY HTC devices not function properly. So, besides this there are SoD issues with some devices after a call.. Same type fix used to resolve and that one usually is resolved with an OTA fairly quickly... But ummm, why can't HTC users ban together and make HTC perfect their sources? They are after all the manufacturer and Sense roms are just copies of their source (modified here and there perhaps)... so the problems have been identified, solutions have been committed by an OPEN SOURCE team... good lord HTC, this has been going on since the Desire.. and just browsing I found Legend, Wildfire S and several others effected..
Great work-a-rounds btw... I just really think the consumers should petition on these issues as they are all related and fixable. Most just hear battery life sucks on the Android and assume their phone going dead after 5 hrs is normal... Well it's not. Just my 2c.
Rob

helppp...!!! pls
im also usin ogoo's rom having battery drain problem.. im kinda noob
cn u tel me specifically wht to do?
nd wht is? build.prop

akashj17 said:
im also usin ogoo's rom having battery drain problem.. im kinda noob
cn u tel me specifically wht to do?
nd wht is? build.prop
Click to expand...
Click to collapse
Well my friend , I was a noob about 7 or 8 months ago too, I did lots of reading and learning and used Google to find my answers.
But here's some quick help to get you started....
Before you do anything if you haven't already do a nandroid backup.
You are using ogos gingerbread so you must be rooted yeah, OK so next we need to find out how u rooted, if you went down the hboot 1.02 and unlocked boot loader method, that is great makes my job much easier.
Build.prop is a file located in the
/system/ folder
It is basically a text file that contains a list of settings/commands/startup options.
In my ogos rom the command in question has a # in front of it which disables that line.
You need to edit that file and remove the #. To do this I used es file explorer with root turned on in settings, then just went to /system and opened it with es file explorer.
Or you could get build.prop editor from market and add the line that way, however you need to leave out the = and put the stuff in front in the top field and the 1 In the other.
Simple as that....
If you are say hboot 1.01 and s-on then that's a lot harder for me :-(
You'll only be able to do it via fastboot method, reboot phone into fast boot menu volume down then power. Connect to your PC, it is properly set up isn't it yeah? use android commander to copy that file to your PC, edit file using notepad then copy it back.
If you done it right, good if not, ummm you might need to search for answers for to what you need.
You could always send your phone to me and pay me I only charge $100 per hour lolol
Sent from my legend using XDA

Thnxxx........ Ranger

Touch key brightness

Hey all, I'm trying to figure out how to get some brightness settings for the touch key brightness to stick. I've used LG 2x Notifications and O2x Touch Key Brightness, and they both work up until the point where i put the phone to sleep by tapping the power button. As soon as I wake it up, the brightness goes straight to zero unless i head back to the app and raise it up again. And if i uninstall the apps, the brightness on my keys stay off until i re-flash or reinstall the app again. Help!

My issue is a little different but similar. It worked fine for me on every basic gingerbread rom, but when I switched to a cm7 based rom the lights change with the brightness of the screen. I turned off all the light notifications but it did not help.
If anyone has any ideas, I'd love to hear them.

What rom?
Sent from my LG-P999 using XDA

redmonke255 said:
What rom?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
On SinghUI but it doesn't have built-in LED notifications, if that's what you're getting at.

If the setting from one of those apps doesn't stick, then it's most likely being set by your ROM or Kernel. Have you tried checking if you get the same issue with other ROMs?
@jcbofkc That's a built-in setting that can't really be changed unless you get a custom ROM or Kernel cooked up to remove the link between the brightnesses.

xBIGREDDx said:
If the setting from one of those apps doesn't stick, then it's most likely being set by your ROM or Kernel. Have you tried checking if you get the same issue with other ROMs?
@jcbofkc That's a built-in setting that can't really be changed unless you get a custom ROM or Kernel cooked up to remove the link between the brightnesses.
Click to expand...
Click to collapse
90% sure the ROM doesn't have built in notifications. I'm noticing now that very rarely the settings do stick. Perhaps there is a way to force the app to stay in memory?

rrroach said:
90% sure the ROM doesn't have built in notifications. I'm noticing now that very rarely the settings do stick. Perhaps there is a way to force the app to stay in memory?
Click to expand...
Click to collapse
That wouldn't work. All that those apps do is write a number from 0-20 to the text file:
/sys/devices/platform/star_touch_led/wled
in your root file system.
When you read the file, it shows you the current output to the LEDs (from 0uA to 2000uA).
When you write to the file, it interacts with the Kernel and sets the brightness.
The Touch Key Lights type apps, all they do is when you move the slider they write a value to that file, and that's it. The only reason it wouldn't stick is if your ROM or Kernel is changing the value in the background. For example it will set it to 0 when you turn the screen off, and then it should set it back to wherever it was before when you turn the screen on again.
The closest you could get is to take the source for LG Touch LED Notifications and modify it to set the brightness every few seconds or something, but that probably wouldn't be too good for your battery life.
Based on your symptoms it appears that either your ROM or your phone doesn't really handle the modifying of the brightness very well. It looks like SinghUI does use a kernel from CM7, so I don't think your kernel is the problem. I'd suggest flashing the most recent CM7.2 RC, and seeing if you have the same problem there. CyanogenMod will change your LED brightness based on your screen brightness though.
EDIT: Ignore all that for a moment, try this first. It is a post from January 21st in the SinghUI thread, so it might not work now, but go ahead and try it: http://forum.xda-developers.com/showpost.php?p=21652744&postcount=293
Also I'd suggest posting in the SinghUI thread as everyone there is using your ROM, so they might be able to help better.

xBIGREDDx said:
That wouldn't work. All that those apps do is write a number from 0-20 to the text file:
/sys/devices/platform/star_touch_led/wled
in your root file system.
When you read the file, it shows you the current output to the LEDs (from 0uA to 2000uA).
When you write to the file, it interacts with the Kernel and sets the brightness.
The Touch Key Lights type apps, all they do is when you move the slider they write a value to that file, and that's it. The only reason it wouldn't stick is if your ROM or Kernel is changing the value in the background. For example it will set it to 0 when you turn the screen off, and then it should set it back to wherever it was before when you turn the screen on again.
The closest you could get is to take the source for LG Touch LED Notifications and modify it to set the brightness every few seconds or something, but that probably wouldn't be too good for your battery life.
Based on your symptoms it appears that either your ROM or your phone doesn't really handle the modifying of the brightness very well. It looks like SinghUI does use a kernel from CM7, so I don't think your kernel is the problem. I'd suggest flashing the most recent CM7.2 RC, and seeing if you have the same problem there. CyanogenMod will change your LED brightness based on your screen brightness though.
EDIT: Ignore all that for a moment, try this first. It is a post from January 21st in the SinghUI thread, so it might not work now, but go ahead and try it: http://forum.xda-developers.com/showpost.php?p=21652744&postcount=293
Also I'd suggest posting in the SinghUI thread as everyone there is using your ROM, so they might be able to help better.
Click to expand...
Click to collapse
Thanks for the link. It turns out that the ROM does have led notifications. However, disabling them didn't help the problem. :/ the g2x has just been an awful experience for me! :/

[Q&A] Infuse Toolkit

Post your questions here

Reserved #1
Reserved....

Reserved #2
Reserved ....

Hello, Sir.
I'm a long time lurker and not the first time poster. Known to troll occasionally.
Does this tool kit work for backing up ICS ROMs?

That's a fair question...there was one ICS tester who provided some valuable feedback and then fled the country.. (or the 50 states anyway)
I believe the ROM backup/restore will work as long as /system, /data, and /dbdata are the only places where ROM information resides.
The toolkit will not backup kernels or modems, but those are easily obtained and flashed from other sources...

qkster said:
Hello, Sir. I'm a long time lurker and not the first time poster. Known to troll occasionally. Does this tool kit work for backing up ICS ROMs?
Click to expand...
Click to collapse
Troll'r here....yes it does work for backup of what u call i c s...?

Thank you, kind sirs.
Since I'm not too much a noob, and you took the time to answer me, I slapped thanks on your posts because you have responded to my question.
Thank you again. Now i just have to figure out how to get the boot animation to work.

removal if needed
if god forbid, the user wants to remove this from his/her phone. How would that do accompllished? and how does this work with the wipe and reload? doesnt the process of flashing delete this program as well?

mhumfleet said:
if god forbid, the user wants to remove this from his/her phone. How would that do accompllished? and how does this work with the wipe and reload? doesnt the process of flashing delete this program as well?
Click to expand...
Click to collapse
not sure what you are asking...this is a zip file you run like installing a ROM
"It's a way to do many useful things in CWM recovery mode via a Touch-Enabled interface,"
>it is a tool used in CWM not within the ROM...
>if you go thru the program has a few questions or prompts to ensure you want to do what you are clicking...
>once you wipe and reload...and boot out of the program and cwm the program closes....does not del the program...it resides on your sd as a zip file like a ROM file until you go back into CWM to exe it again...
>the tool is not visible in the ROM...
make sense...?

mhumfleet said:
if god forbid, the user wants to remove this from his/her phone. How would that do accompllished? and how does this work with the wipe and reload? doesnt the process of flashing delete this program as well?
Click to expand...
Click to collapse
Best way to figure out what the toolkit does is to run it from CWM and try it out. Make sure you run a config backup and a full Rom backup first thing. That way you can undo any changes you make. In the tweaks section there are also undo options for any init.d or build.prop tweaks you add.
If something seems unfamiliar (i.e. "what the heck is init.d?"), Google is your best friend.

thanks
Thanks Zen Will Do
Does anybody have some Raid? there is a bug crawling on my screen when i look at Zens Postings

mhumfleet said:
Thanks Zen Will Do Does anybody have some Raid? there is a bug crawling on my screen when i look at Zens Postings
Click to expand...
Click to collapse
LOL, I don't to use the computer much...due to wife..., but when I get on here....
that bug of Zen, gets me every time...I am wiping my screen saying WTF...my boys laugh at me....

mhumfleet said:
if god forbid, the user wants to remove this from his/her phone. How would that do accompllished? and how does this work with the wipe and reload? doesnt the process of flashing delete this program as well?
Click to expand...
Click to collapse
The aroma tool kit resides on your internal sdcard, where you would place your downloaded program..just like the ROM or a cwm flashable. Flashing a ROM only wipe the system drive, not the 14gb internal drive where we usually store or flashable zips. Deleting it is simple: locate it and delete it. Every time you use it, you need to flash it in cwm.
Sent from USA

Now I have a very serious question for the Tool Kit.
When I put my phone on vibrate, it does nothing for me. I even tried clipping the phone to the front of my pants. Nope, nothing, didn't feel a thing.
Is there any way of increasing the intensity of the vibration so that I can at least feel the vibration and have it do something for me?

Truckerglenn said:
Now I have a very serious question for the Tool Kit. When I put my phone on vibrate, it does nothing for me. I even tried clipping the phone to the front of my pants. Nope, nothing, didn't feel a thing.
Is there any way of increasing the intensity of the vibration so that I can at least feel the vibration and have it do something for me?
Click to expand...
Click to collapse
Howdy Glenn, How you been?
intensity of the vibration... and have it do something for me? I hear that more from her...but HUH, ok, I will let Zen take that one...LOL
kdding Glenn

Truckerglenn said:
Now I have a very serious question for the Tool Kit.
When I put my phone on vibrate, it does nothing for me. I even tried clipping the phone to the front of my pants. Nope, nothing, didn't feel a thing.
Is there any way of increasing the intensity of the vibration so that I can at least feel the vibration and have it do something for me?
Click to expand...
Click to collapse
Check the following first:
1. Go to settings-->sound, enable haptic feedback, change vibration intensity (one below), then turn off haptic feedback.
2. From same sound menu, check your vibrate setting - set to always or only in silent mode. If the latter then use the down volume button to move sound all the way to zero. When it reaches zero, your phone should vibrate.
If you don't feel a vibrate from this you may have a busted vibrator (Joe? Any suggestions here? )
Check the notify bar to see if your sound icon shows as silent with a vibration indicator (usually a squiggly line - but this may vary by ROM).
This app appears to allow some customization of vibration based on specific contacts for SMS and perhaps inbound calls: https://play.google.com/store/apps/details?id=com.base2apps.vibes&hl=en
Other than that, there may be a kernel option to change vibrate intensity. If the above don't work for you, and you do still get some level of vibrate, I'll look into it when I'm working on my next kernel update.

Zen Arcade said:
Check the following first:
If you don't feel a vibrate from this you may have a busted vibrator (Joe? Any suggestions here? )
Click to expand...
Click to collapse
ebay.....

Can we know more abt. the emergency uclb3 packaged with this toolkit?
Is it rooted, zipaligned, deodexed, debloated, with lidroid toogles etc?

The UCLB3 ROM included here is derived from Dman's rooted, deodexed, zipaligned base. I've updated superuser, and debloated all the crap out of it, plus a bunch of other apps that would be included in a typical rom but removed here in the interest of conserving space while staying true to the intent... something to flash in the event of an emergency - i.e. no roms on sdcard, or for devs and testers, something to flash as a "control" to compare against... i.e. flash this, apply your change to see if it causes the same behavior as on your own rom...

Zen Arcade said:
Check the following first:
1. Go to settings-->sound, enable haptic feedback, change vibration intensity (one below), then turn off haptic feedback.
2. From same sound menu, check your vibrate setting - set to always or only in silent mode. If the latter then use the down volume button to move sound all the way to zero. When it reaches zero, your phone should vibrate.
If you don't feel a vibrate from this you may have a busted vibrator (Joe? Any suggestions here? )
Check the notify bar to see if your sound icon shows as silent with a vibration indicator (usually a squiggly line - but this may vary by ROM).
This app appears to allow some customization of vibration based on specific contacts for SMS and perhaps inbound calls: https://play.google.com/store/apps/details?id=com.base2apps.vibes&hl=en
Other than that, there may be a kernel option to change vibrate intensity. If the above don't work for you, and you do still get some level of vibrate, I'll look into it when I'm working on my next kernel update.
Click to expand...
Click to collapse
Oh, I thought that since this phone had all the bells and whisles, the vibrator was for something else. Never mind.