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] Updating cyanogenmod 10 to 10.1

I just wanted to be sure that I am going to do this right.
Do I just go Settings > About phone > CyanogenMod updates > then download 10.1 and it will do all the work for me? Or do I have to make a nandroid backup (going to do that anyways), wipe cache and dalvik, flash boot.img then flash the rom?
Also, how stable is 10.1? Any known bugs?

kylepont said:
I just wanted to be sure that I am going to do this right.
Do I just go Settings > About phone > CyanogenMod updates > then download 10.1 and it will do all the work for me? Or do I have to make a nandroid backup (going to do that anyways), wipe cache and dalvik, flash boot.img then flash the rom?
Also, how stable is 10.1? Any known bugs?
Click to expand...
Click to collapse
The automatic updater will not work. At least if you're S-On. So flashing through recovery is the way to do it (wipes and boot.img flashing as usual also ofc). I believe flashing CM10.1 over CM10 might work without factory reset, but prepare for stuff not working and flashing it again with proper wiping.
Bugwise I'd say CM10.1 is absolutely ready as a daily driver. Wifi tether doesn't work when screen is off (same issue is with CM10). Performance is a bit lower than with CM10. You'll see some screen tearing when scrolling and switching home screens and in some games with intense graphics.
Give it a go! It's not too hard to go back to CM10 if it doesn't please you.
Sent from my One S. Please hit thanks if I helped.

zaak00 said:
The automatic updater will not work. At least if you're S-On. So flashing through recovery is the way to do it (wipes and boot.img flashing as usual also ofc). I believe flashing CM10.1 over CM10 might work without factory reset, but prepare for stuff not working and flashing it again with proper wiping.
Give it a go! It's not too hard to go back to CM10 if it doesn't please you.
Click to expand...
Click to collapse
This will be a tl;dr story so only read it if you can be bothered...
I did the automatic update, then as soon as it downloaded I had to run for the bus (one a bloomin' hour). I was then stuck on the htc splash screen for about ten minutes, did a soft reset, went into recovery, went back to CM10, restored the backup, not a problem. Then got home, pushed 10.1 onto the phone, flashed the new boot.img, then flashed CM10.1 and restored backup again. Worked fine. Then I had to try three different Gapps because two of them didn't actually work, and it was agonising that the website that I got them from only had an upload speed of around 0.4Mbs. But flashed that now, and everything works fine (although I had to delete and re-download NatWest and Play Music).
zaak00 said:
Bugwise I'd say CM10.1 is absolutely ready as a daily driver. Wifi tether doesn't work when screen is off (same issue is with CM10). Performance is a bit lower than with CM10. You'll see some screen tearing when scrolling and switching home screens and in some games with intense graphics.
Click to expand...
Click to collapse
Spotted a couple of bugs immediately. Syncing with facebook simply does not work (I only wanted contact pictures for caller IDs). Obviously the clock bug, but I know how that is fixed. Haven't had any screen tearing yet, and since Orange only give me 750MB there is nooooooooo way that I am going to use tethering, so that won't bug me. CM10.1 has fixed the music player bug, where the first song I play would take around 30 seconds to play, if I chose another song then it would restart the previous song, play that for five seconds, then play the selected song, and if I paused a song it would then start playing again for a couple of seconds after five seconds of being paused. That was irritating. Noticed it seems to be a fair bit more RAM heavy than CM10, but I miss the settings button on the top of the notification bar, that tiles thing just seems to take to long for my liking...

kylepont said:
Noticed it seems to be a fair bit more RAM heavy than CM10, but I miss the settings button on the top of the notification bar, that tiles thing just seems to take to long for my liking...
Click to expand...
Click to collapse
You can also swipe down with two fingers, or set a specific area that opens the Quick Settings immediately, in Settings
Sent from my One S using Tapatalk 2

usaff22 said:
You can also swipe down with two fingers, or set a specific area that opens the Quick Settings immediately, in Settings
Click to expand...
Click to collapse
Already knew about the sections thing, but because I'm right-handed every time I wanted to look at a notification I got settings, and setting it so that the settings open on the left side just seems a bit weird. I didn't know about the two fingers thing, and I like that, cheers.

[Q] Capacitive buttons sporadically not working, requires reboot

Skyrocket i727 running CM-10.1-20130807 nightly. Apex launcher. On Rogers with UCMC1 radio.
It's running stable with the (big) exception that occasionally (once or twice a day) the four buttons at the bottom (settings/home/back/search) will not respond to any touch. The only way to fix it is to restart the phone. I searched the forums and cannot find an answer to why this might be happening, nor to anyone else having this problem. I have the backlight on these buttons disabled (to save power).
Also, this might be related or maybe not, but on Monday I had a very strange crash. The HOME button wouldn't work, but the BACK button and SETTINGS button did. The notification bar wasn't functioning and no push notifications were coming through. The quick-settings panel was reverted to default, and the buttons within the quick settings panel were completely unresponsive.
Even stranger, Chrome was unresponsive, Maps/Navigation were constantly force-closing, and in general the phone was throwing a massive fit over almost anything I did. I pulled the battery but that didn't help. I was forced to go into recovery mode and perform factory reset, wipe dalvik cache, and reinstall the ROM. This has worked (although a PITA) but the issue I mentioned first (bottom buttons not working) has manifested itself since then.
Any ideas what to do here?
Much appreciated!
Eric

Run the recent nightly. Could be an issue with your rom, although I haven't seen your problem.

I just flashed the most recent nightly a few minutes ago.
Should I go back into recovery and wipe cache and dalvik? (note: When I flashed the ROM through CM Updater / TWRP, it 'optimized' 119 apps... so I think it automatically wiped the cache...?)

curls00 said:
I just flashed the most recent nightly a few minutes ago.
Should I go back into recovery and wipe cache and dalvik? (note: When I flashed the ROM through CM Updater / TWRP, it 'optimized' 119 apps... so I think it automatically wiped the cache...?)
Click to expand...
Click to collapse
You should be ok. I never go back and wipe caches

The original issue is still occurring even on newest nightly. Completely random (using different apps each time - Facebook, Messenger, Youtube, etc...).
Any idea if a setting I can change is causing this?

mtdew said:
Hardware failure.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
LOL time to sell then!

[Q] All sound dropping out

Hey guys, I've been having this issue for weeks and it seems that it doesn't matter what ROM I'm on.
All sound will inexplicably drop out. I mean system sounds, the ringer, notifications, music, in-call, podcasts - everything. Nothing in particular seems to trigger it and sometimes it eventually just comes back on it's own. It seems that sometimes I can get it to come back on by turning the volume up and down repeatedly (may just be a coincidence though). This occurs multiple times a day.
I've tried numerous 4.3, 4.4, and even 4.2.2 sense ROMs, and it still occurs. Pretty annoying because what good is a phone that never rings or notifies you, and you can't even talk to people when you dial them.
I can't confirm this, but this may have all begun when I updated my hboot to 2.15 for the new 3.4 kernel based ROMs. Can't quite remember because it's been like this for quite awhile now.
Anyways, if anyone has any ideas it would be greatly appreciated. I'll try to post a logcat the next time it happens.

DRUMROT said:
Hey guys, I've been having this issue for weeks and it seems that it doesn't matter what ROM I'm on.
All sound will inexplicably drop out. I mean system sounds, the ringer, notifications, music, in-call, podcasts - everything. Nothing in particular seems to trigger it and sometimes it eventually just comes back on it's own. It seems that sometimes I can get it to come back on by turning the volume up and down repeatedly (may just be a coincidence though). This occurs multiple times a day.
I've tried numerous 4.3, 4.4, and even 4.2.2 sense ROMs, and it still occurs. Pretty annoying because what good is a phone that never rings or notifies you, and you can't even talk to people when you dial them.
I can't confirm this, but this may have all begun when I updated my hboot to 2.15 for the new 3.4 kernel based ROMs. Can't quite remember because it's been like this for quite awhile now.
Anyways, if anyone has any ideas it would be greatly appreciated. I'll try to post a logcat the next time it happens.
Click to expand...
Click to collapse
No idea? How come I seem to be the only person with this issue? Haha
I'm currently using Dark Jelly S 28.1 (the last version with the 3.0 kernel). Seems to be a bit better. Anyone have any links or zips of other 3.0 based ROMs? The lionks in all the threads are dead. Guess they took down the zips when everyone started switching to 3.4 and 4.3/4.4.

DRUMROT said:
No idea? How come I seem to be the only person with this issue? Haha
I'm currently using Dark Jelly S 28.1 (the last version with the 3.0 kernel). Seems to be a bit better. Anyone have any links or zips of other 3.0 based ROMs? The lionks in all the threads are dead. Guess they took down the zips when everyone started switching to 3.4 and 4.3/4.4.
Click to expand...
Click to collapse
Well I tried some other 3.0 roms thanks to some very helpful people in another thread I created http://forum.xda-developers.com/showthread.php?p=48029123#post48029123 but I am still having sound issues.
I tried reflashing the 2.15 firmware and the sound was back until I received a call. After I hung up, I lost all sound.
I'm not very knowledgeable when it comes to this stuff, but I ran a logcat and noticed a view errors relating to sound (SoundPool: error creating audio track, Audiotrack: could not get audio output for stream type 1, AudioPolicyManagerALSA: getDeviceForStrategy() speaker device not found for STRATEGY_SONIFICATION, etc). Not sure what this means or how I can go about fixing it. Looking at running an RUU to see if that will help but I'm on Linux so it's a bit more complicated than just running the .exe and I'll have to reroot anyways so hopefully someone can shed some light on this for me. Attached is a log showing the errors.

I am having the exact same problem with my HTC one S. For no apparant reason all sounds stop (speaker, music, notifications, can't make or recieve phone calls)
My problem started when I was running stock software. It got so bad that I had no choice but to S-OFF, Root and install a custom rom to see if that solved the problem. I currently am running MaximusHD and I love it. But the problem is back.
After searching throught the logs there seem to be two main errors "failed to enable the mixer controls for the speaker" and "AudioPolicyManagerBase(261)".
Does anyone have any idea of how i can disable or reinstall the service that is tied to this?

Bump... I also seem to having this problem. I'm running stock rom, rooted. S-On.
Randomly, my audio stops working. Sometimes a reboot fixes it, sometimes not. Sometimes a hard reboot (holding power down) works, sometimes not. More often than not, rebooting to recovery, then booting sytem fixes it.
I know it's not hardware because during this occurrence, some software (e.g, google voice search) gives an error but runs fine when things are normal.
I tried looking at logcat (I'm new at this) but nothing jumped out. Would love some help getting to the bottom of the problem as it's really annoying to randomly not be able to answer calls.

So this problem is happening more and more to my phone. Since my post earlier this month, I've tried Stock rom, liberty rom, and CM11, and the no-audio problem happens randomly on all of them.
This is really frustrating, as it makes the phone unusable. I'm very close to giving up and just getting a different phone.

Interesting find... I removed Lookout Security, and this appears to have solved 80-90% of the problem.

CM 13 nightly, missing Quick settings and tiles.

Hello all, I need a hand with this one. I'm running the newest version of CM 13 nightly, yesterdays build. The past 2 builds my quick settings seems to have disappeared. I have the setting the turn it on, it does not matter if it is turned on or not, still nothing. On top of that I am missing any and all tiles from the menu as well. As you can imagine this has put me at a major loss, I love my tiles! No more double pull for setting, heck even my notifications are missing, they don't even show up in the bar. Does anyone have any ideas? When I installed this build I did a complete wipe/reinstall to there are no older versions to get borked on.

Figured this out! Seems to be a know issue from openGAPPs. Wipe everything but internal storage, flash the latest nightly, flash the nano package of OpenGAPPs, wipe cache and dalvik, reboot. Should be good to go! For posterity!
Sent from my DROID Turbo using XDA-Developers mobile app

Glad you got it figured out.