Database Info

[Q] Inspire suddenly stopped vibrating w/SMS

Seems to be somewhat common but no fix to be found...
Using CM7.1
Was working perfectly for a month.
Seemed to happen out of no where, no new apps installed or settings changed. The phone will vibrate for incoming calls, haptic, everything except SMS.
Using GoSMS but it does the same with the stock messanging app. Vibration is turned on in all the system and messanging settings. In fact, when I test settings in GoSMS it reports "vibration on".
Tried clearing the dalvik cache and tried installing this app but it won't show anywhere in the app drawer and I can't find it anywhere on the phone despite the market saying its installed. Unfortunate becasue it seems this app was designed for this very issue with desire/insprire.
Anyone have a fix for this or a method I could get the above app to install properly?
Thanks.

edit.....It's looking like an app issue......
never mind on the rom repair part....sorry
mods can delete....g

Gregsarg was actually probably right the first time. It doesn't seem to be an APP issue (as all MMS apps have the same lack of vibrate), but a broader issue.
His suggestion to install CM7 on top of itself is likely the simplest attempt at solution since you haven't found a specific solution through your searches.
I also tried the GoodVibrations.apk and it only shows in airdroid, mybackup, and managing all apps... It doesn't even have the 'open' command on the market menu after installing it >.>

Wulamoc said:
His suggestion to install CM7 on top of itself is likely the simplest attempt at solution since you haven't found a specific solution through your searches.
Click to expand...
Click to collapse
Thanks. Unfortunately I didn't see this suggestion before it was edited out. What exactly is meant by install CM7 on top of itself? Through clockwork I presume?

Yeah, just flash the SAME rom again (after backing up AND without wiping anything), and your settings should stay in place.

There is also a setting in the stock CM sms app that controls vibration, which is turned off by default.

Yeah vibrate in the stock SMS program is on. While I haven't gotten around to reflashing just yet I have noticed a few other things that lead me to believe its a ROM issue. Sometimes when I put the phone on silent it turns off all system vibrations even after coming off silent. I have to go back in and turn vibration back on. This is intermittent. Also, out of the blue the phone started vibrating during calls, come to find out "vibrate every 45 seconds during outgoing calls" was magically turned on.
It WILL vibrate when an SMS arrives if I'm on a call. Swell.

Flashed the new 7.2 nightly and the problem still exists. Everything remained intact after the flash so I figure I'll just do a full wipe/factory reset and flash the new nightly again and start over. Hopefully whatever caused this won't carry over with titanium restoring apps.

Do the full wipe, install the rom... then get a friend to send you text messages BEFORE you restore from Titanium, and then after....
Easy to isolate if you're carrying the issue from ROM to ROM.

Had the same issue, could find no fix. Used vibrate tools from the market and no issues for a week or so now..
*signed

mrrick said:
Had the same issue, could find no fix. Used vibrate tools from the market and no issues for a week or so now
Click to expand...
Click to collapse
That did it thanks! Saved me from having to do a full wipe. Phone is back to vibrating with SMS and I can change the vibration pattern. Nice.

Cool, glad it worked for you. I really wish I knew what happened though, it's kind of bugging me.
Meh, technology..
*signed

Well I'll add this... Out of curiosity I removed the vibrate tools app and everything is still operating as designed. So whatever that app turned on has stuck.

[Q] ringtone notification errors

I have been having ringtone errors recently, after device wakeup, sometimes during device sleep; but most often at wakeup the ringtone will sound off without any notification present, nor a caller trying to connect. It started after I engaged the pattern lock, but it must be caused by something else because after I turned off the lock screen and did a restart it still has the error. Anyone else having the same issue? Any ideas on a fix?
well, I've been working on this and so far I have found it is related to the use of the alarm server but the only fix is a temp fix. I set the phone to vibration and then turn back on the ring setting and that works for a day. I am still working to find a more permanent fix. please feel free to post any ringtone issues here maybe they are related and everyone can help with fixes here.

Ok I got it worked out. I had to flash from my nand backup and reinstall all my apps. The trouble came from titanium backup. It shouldn't be used to reinstall app data. If just the app it's ok, but app plus data will make the ringtone go flakey

I have been using titanium backup for app and data .No issues here mate.
May be you are trying to restore system settings across ROM's
Sent from a Desire S waiting for Kernel 3 sources. WAKE UP HTC!!!!

Nope, I'm using my stock Rom it's just rooted. I have stopped using TB. However I think it may have been only one or two apps causing the trouble. I think it was Facebook and Catfiz.
Sent from my HTC Desire S using Tapatalk 2 Beta-5

[Q] Notification icons gone after crash

I've got a Samsung Infuse 4G, originally Rogers now on Telus. It's been running ParanoidAndroid 2.53 from scott.hart.bti (build pa_infuse4g-userdebug 4.1.2 JO54K eng.scott.20121104.152548 test-keys) nearly flawlessly for a few weeks. I've installed a few apps (facebook, twitter, wikipedia, imdb, accuweather, etc.) but none recently.
Today, I answered a phone call from my brother, and when I took the phone away from my ear to hang up, it stayed black. I heard the disconnect sound, then it pretty much froze. I powered off to the Power Reset / Debug Mode screen, then rebooted. When it came back on, I'd lost a bunch of my settings, but not all. I currently have been unable to get back my full menu when I long-press the power button - it only has power off and reboot, no airplane mode, no volume, no profile choice (yes, I have configured these options in the settings). Further, my notifications work (ie, sound and vibrate), but the notification icon does not appear.
Anyone have any ideas what I should try? I could reflash and start over, but I'd rather not if I don't have to.
Thanks in advance.

Can anyone comment on whether or not this make be a problem with Trebuchet? Are the problems I mentioned the domain of the launcher, or is it something else? If these things are controlled by the launcher, am I able to reinstall / reset it to possibly fix the problem?

It sounds more like a SystemUI problem than a launcher problem. You can reflash the ROM without losing any data or settings by formatting just the cache partition and /system and also clearing dalvik cache. That will reinstall the ROM without data loss but if the problem persists I recommend a full and complete wipe and reflash.
If you believe it to be a trebucket problem though then download a free launcher replacement like Holo launcher from the store and see if that fixes your problems.
Sent from my SGH-I997 using xda premium

[Q] Stock rooted reverts back to default keyboard

I have two issues, both of which are very frustrating. I have changed my default keyboard to Smart Keyboard Pro and it keeps the change for a day or two and then it reverts back to the Samsung keyboard. It is not tied to restarts, and I cannot figure out what causes it t suddenly change back.
The second issue is the call log shows everything (including messages) even though I tell it just show "all calls". The issues is kind of the same where I change it and it stays that way for a few days and then reverts back but the tow changes don't even take place together.
Any ideas?

ssnapier said:
I have two issues, both of which are very frustrating. I have changed my default keyboard to Smart Keyboard Pro and it keeps the change for a day or two and then it reverts back to the Samsung keyboard. It is not tied to restarts, and I cannot figure out what causes it t suddenly change back.
The second issue is the call log shows everything (including messages) even though I tell it just show "all calls". The issues is kind of the same where I change it and it stays that way for a few days and then reverts back but the tow changes don't even take place together.
Any ideas?
Click to expand...
Click to collapse
Sounds weird, have you installed a mod recently that may have messed it up? Sometimes doing things to your phone can cause these little issues.
I'd restore a recent backup if you have it, you can try to factory reset also but you'll lose your app and system data.
If that still doesn't work, I'd pull off any files you want to keep and format the internal SD card. It'll return your phone to a very clean state, but you'll also start from scratch.
I also think flashing a custom rom should clear things up. If you find any you're interested in give them a shot. cleanrom, bonestock, and obsessed all are extremely stable roms and as close to stock as you'll get. There are also many other roms that are more heavily modded and themed that you'd enjoy. I think you'd probably like them more than a stock rooted rom anyway.
Sent from my SCH-I535 using Tapatalk 2

[Q] Phone only rings for about one second and then stops.

After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)

c4sh said:
After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)
Click to expand...
Click to collapse
Are you using a custom ringtone?

Aerowinder said:
Are you using a custom ringtone?
Click to expand...
Click to collapse
No, just the stock tones. I find it happening sometimes with my SMS messages as well but not all the time.

Update: I have since unlocked my bootloader (wiped) and rooted my phone and the problem still persist. Seems like I'm not alone, I have starred this so hopefully someone can see it. https://code.google.com/p/android/issues/detail?id=81178#makechanges
Anyone have any suggestions that I could try?

update
I had thought I had fixed the problem by re flashing the stock image of lollipop, the problem went away and my phone started to ring again but shortly its back to only vibrating. I noticed that the little vibrate symbol was popping up in the status bar whenever I received a call, even when I turned off the also vibrate for calls option. I then remembered that when I use the volume butler app and set it to my vibrate profile that symbol would also pop up. I uninstalled volume butler and everything seemed to be working fine. Next I Checked the play store for comments regarding the issue and I noticed two things: There was a recent fix "ringtone changing to silent upon first install" and it said that the app was installed onto my device and not requiring an update even though I had just uninstalled it. So I decided to open it up and it was as if I was starting the app for the first time as none of my previous data was in there for testing purposes I decided to set up the same profiles that I had before and try calling my phone and my phone rang like it should, weird. Perhaps I had two versions and that was the one that I originally uninstalled is that even possible?( I could have sworn I had updated it,as it was under the up to date app list) Regardless, I uninstalled it again and everything is still working as it should. Hoping that this was was the culprit I will continue to test my phone and see.