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] com.android.phone crashes during calls after copy/paste fix

The specs: Rooted stock ICS on SCH-I535 (Verizon). So, I was experiencing the copy-paste crash described here, and used this solution to solve it. Ever since that fix, the phone process crashes when making a call. Here's what happens.
1. Open stock dialer, make call. Call connects, but screen is black.
2. Message that com.android.phone has stopped comes up. I click "ok."
3. Icon in menubar disappears and reappears. When pulling down the menubar, the call info is there. Selecting the call (via the green phone icon) brings me back to the black screen, and the stopped message reappears. I can end the call using the controls there, though.
4. Bringing up the Phone app while on the call brings me back to the stock dialer screen, but hitting keypad buttons there doesn't affect the call that I'm on. (i.e., if I'm in an automated system call, there are no keytones received by that system.)
5. When call is ended, it doesn't show up in my Recent Calls list.
I tried installing Dialer One, and get the same results.
Should I just wiped the Dalvik cache again in CWM and see what happens? Other ideas?
I was going to finally upgrade to JB and root (while we're at it, does OTA rootkeeper work here?) anyways, but don't really have time before I'm about to travel again. Any bandaids to fix this in the meantime would be great. Thanks in advance.

How did you fix this???
Were you abke to fix this??

ferkis said:
Were you abke to fix this??
Click to expand...
Click to collapse
Yeah, but I had to do a factory reset and re-root, then use Titanium to restore my backed-up apps.

[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.

Z5 Dual E6633 - Issues to pick up calls

Hello guys,
sorry if this has been answered before.
I am currently facing an issue with my Z5 Dual E6633. For some calls, the call screen would freeze when swiping to answer.
- When swiping to pick up the screen freezes and swipes do not respond
- Phone continues to ring
- If swipe down from the notification bar, i can open settings
- The call pop up appears on the top, and if i hit answer button it works
The issue does not happen systematically. Happens from time to time and not with same calling numbers.
Has anyone experienced same? Anyway to solve this?
i already tried:
1) clearing caches
2) clearing data for call settings
3) most recently did a repair using xperia companion
Also note that i am running latest MM stock rom and phone is not rooted.
Thanks for the help

ravijokhun said:
Hello guys,
sorry if this has been answered before.
I am currently facing an issue with my Z5 Dual E6633. For some calls, the call screen would freeze when swiping to answer.
- When swiping to pick up the screen freezes and swipes do not respond
- Phone continues to ring
- If swipe down from the notification bar, i can open settings
- The call pop up appears on the top, and if i hit answer button it works
The issue does not happen systematically. Happens from time to time and not with same calling numbers.
Has anyone experienced same? Anyway to solve this?
i already tried:
1) clearing caches
2) clearing data for call settings
3) most recently did a repair using xperia companion
Also note that i am running latest MM stock rom and phone is not rooted.
Thanks for the help
Click to expand...
Click to collapse
The thing that fixed it for me was a factory reset
Sent from my E6653 using Tapatalk

Thanks but already did same. Even an xperia companion repair

Well I can't help you any further. I'm not an expert at this stuff. Sorry.
Sent from my E6653 using Tapatalk

Hello guys. I am still facing same issue with swipe to answer. It decides randomly to stop working. The issue happens only when answering calls through the swipe to answer lock screen. when answering from homescreen no issues with calls. So i am guessing it is not an issue with hardware.
I already tried everything possible like repairing, reflashing, swapping sims in the trays., rooting, flashed custom rom (but with stock kernel).
Anyone experiecing same or managed to solve this issue?

Marshmallow problems with spontaneous launching of Google Now, taking over device.

My phone has been misbehaving since it upgraded the OS to Marshmallow. It was primarily occurring with the Google Now app and it would take over the phone and flash up and off the screen and whilst this was going on, the phone is busy vibrating, the screen became unresponsive and generally I couldn't do anything with it during these episodes. I stopped it sending to the screen and then it was the Google app that kept flashing up, starting with a round circle coming from the app drawer icon. It has got worse over the last few days to the point that it might take me ten minutes before I could get access to the caller to make a call and even trying to shut down the device was near impossible because the confirmation box never stayed on the screen long enough to answer the question and then it didn't come back. Yesterday, after many tries to restart, it finally restarted in safe mode. If it was related to an app that I downloaded, it should have stopped then but it didn't. When I was able to get into settings, I then went to apps and then disabled google app as this was the one starting up and flashing the screen non stop. I was then asked if I wanted to replace it with a factory version which I did but I also left it disabled. The problem has continued but not as ferociously with the screen becoming unresponsive at times while the buzzing from the vibrate still occurring. I have looked up various forums but haven't found any that have similar problems described. I checked the screen overlay settings and they are enabled and that seems to be the main problem with marshmallow. I'm looking for some advice but realise that this might be too basic for this forum? Vodafone Smart ultra 6, Android version 6.0.1 Kernel version 3.10.49

Stoksie said:
My phone has been misbehaving since it upgraded the OS to Marshmallow. It was primarily occurring with the Google Now app and it would take over the phone and flash up and off the screen and whilst this was going on, the phone is busy vibrating, the screen became unresponsive and generally I couldn't do anything with it during these episodes. I stopped it sending to the screen and then it was the Google app that kept flashing up, starting with a round circle coming from the app drawer icon. It has got worse over the last few days to the point that it might take me ten minutes before I could get access to the caller to make a call and even trying to shut down the device was near impossible because the confirmation box never stayed on the screen long enough to answer the question and then it didn't come back. Yesterday, after many tries to restart, it finally restarted in safe mode. If it was related to an app that I downloaded, it should have stopped then but it didn't. When I was able to get into settings, I then went to apps and then disabled google app as this was the one starting up and flashing the screen non stop. I was then asked if I wanted to replace it with a factory version which I did but I also left it disabled. The problem has continued but not as ferociously with the screen becoming unresponsive at times while the buzzing from the vibrate still occurring. I have looked up various forums but haven't found any that have similar problems described. I checked the screen overlay settings and they are enabled and that seems to be the main problem with marshmallow. I'm looking for some advice but realise that this might be to basic for this forum? Vodafone Smart ultra 6, Android version 6.0.1 Kernel version 3.10.49
Click to expand...
Click to collapse
When you updated to Nougat, what method did you use to update? Did you update via OTA? We're you rooted when you did it?
Have you tried booting to recovery and factory resetting and wiping cache then rebooting?
Sent from my SM-S903VL using Tapatalk

Droidriven said:
When you updated to Nougat, what method did you use to update? Did you update via OTA? We're you rooted when you did it?
Have you tried booting to recovery and factory resetting and wiping cache then rebooting?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
It was an update that appeared on my notifications and I thought it was a small bug fix update and didn't realize that it would replace the entire OS. I just allowed the update and then realized what had happened. I think it is Marshmallow that it updated to but originally the app drawer was paginated and accessed by side swipes whereas the system now is a long page of apps moved up and down. I don't know if it was rooted and I assume that that means it wasn't.
I was trying to avoid a factory reset but I did wipe the cache and rebooting. When google apps is disabled, the interruptions are less often and not for as long but it still went into a complete meltdown of a screen appearing and disappearing at such a rate that nothing can be done with it. It won't show a video because of the interruptions.

Stoksie said:
It was an update that appeared on my notifications and I thought it was a small bug fix update and didn't realize that it would replace the entire OS. I just allowed the update and then realized what had happened. I think it is Marshmallow that it updated to but originally the app drawer was paginated and accessed by side swipes whereas the system now is a long page of apps moved up and down. I don't know if it was rooted and I assume that that means it wasn't.
I was trying to avoid a factory reset but I did wipe the cache and rebooting. When google apps is disabled, the interruptions are less often and not for as long but it still went into a complete meltdown of a screen appearing and disappearing at such a rate that nothing can be done with it. It won't show a video because of the interruptions.
Click to expand...
Click to collapse
Unfortunately, I think you're gonna have to factory reset in stock recovery because there's obviously a conflict with something you already had on the device and it isn't playing nice with something that was in the update.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Unfortunately, I think you're gonna have to factory reset in stock recovery because there's obviously a conflict with something you already had on the device and it isn't playing nice with something that was in the update.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Thanks for taking the time to respond. I have resigned myself to that although it does not seem to be anything that I downloaded to the phone as it occurred in safe mode too. I was just hoping that there was a fix out there but obviously it is not a widespread occurrence.

Stoksie said:
Thanks for taking the time to respond. I have resigned myself to that although it does not seem to be anything that I downloaded to the phone as it occurred in safe mode too. I was just hoping that there was a fix out there but obviously it is not a widespread occurrence.
Click to expand...
Click to collapse
It could have been something in system that got changed during the update but the data from before the change is still there and conflicting with whatever changes were made. Some kind of saved system data that can only be wiped by factory reset or reflashing.
Sent from my SM-S903VL using Tapatalk

I did a factory reset, lost a lot of photos that had started being saved on the phone and not the sdcard after the upgrade to Marshmallow. Have had to accept that but unfortunately the bizarre behavior did not stop and it continues on and off, sometimes so bad that I cannot dial a number on it and other times it happens but I can get in between the action and dial or send a text etc. I have gradually been stopping things like notifications from google apps and traffic reports from google maps (this may have had a good effect) and anything that might be doing constant checks. It seems to have quietened down over the last day or so and I even got to play a game on it but the next option is to send it away to an engineer. I just thought that I would let you know the outcome of the factory reset.