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
Related
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.
Push notifications while phone is sleeping - are these commonly disabled by default in custom roms as a battery saving feature? I've tried Embryo 5.1, Majick-Wizz R3, and CM10 Alpha (all using the recommended kernels/radios, flashing using CWM Touch 6.0.1.2 v12.5), all seem to have the same "issue" where I don't get push notifications from things like Gmail or third party apps while the phone is sleeping. As soon as I wake the phone, the notifications come in.
I couldn't really find anyone on this forum or anywhere else on this issue, except for cases with the HTC Evo, which leads me to believe it's common knowledge whatever is causing this or how to fix it, but I'm new here and this is escaping me completely...
Thanks for any help!
I get push notifications for my email account all the time, and when I've tested other apps (Facebook, Twitter, news apps, etc.) they've always worked there as well. This is on several ROMs, including MW (all three releases), SkyICS 4.2F6 and CM9.
Are you restoring system data from Tibu, by chance? That's all I can think of from a practical perspective that would carry the problem across ROMs, but I'm not a dev and can't begin to guess at any potentially more difficult solutions.
I actually don't restore any data from anywhere except Google auto settings backup. These are all fresh installs.
Edit to add: the notifications seem to work until the screen has been off for 10+ minutes. Also they worked on stock rom.
Edit2: Looks like it may have to do with the WiFi. Made sure the WiFi policy was set to remain connected while sleeping, but that setting doesn't appear to be working. Disabled WiFi and let phone sleep for 10 mins and sent emails to test, and notifications worked.
Edit3: Tried disabling/enabling the WiFi sleep settings in various ways to see if a setting was stuck somewhere, to no avail... Flashed InstigatorX 6.3.4, no dice. It's definitely the WiFi going to sleep though. Confirmed that if WiFi is turned off, all works well. Also, upon waking the phone, it takes a few seconds for network connectivity to start working again (if WiFi is enabled). How do I get this setting to stick?!
Update: Ok, so I just reflashed with all of the Google backup stuff turned off, and tested, still not working.
I'm really running out of ideas here. It's not that I'm unwilling to try something, I just literally can't think of anything else to try...
EDIT: So I just downloaded an app for which the purpose is to keep WiFi awake at all times, and it happens that the app also checks your WiFi sleep policy setting for you. In my case, it told me that i had WiFi set to disable when the phone is sleeping (despite that not being the case). I suppose this fully confirms that the issue is the setting isn't sticking. I let the app change that setting for me then uninstalled the app, going to test throughout the day tomorrow. In the meantime, is there a relatively harmless way to manually check whatever configuration file holds this policy setting?
So I'm on Liquid pre-RC based on Cm10 now and it seems to be working intermittently. The only way I can get it working consistently so far is installing an app built for this purpose. Am I really the only one experiencing this issue with custom roms?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I don't really have an answer for you, but I can at least tell you that you're not crazy. I have definitely noticed this happen where I will wake up my phone and instantly be hit with email notifications. However, it didn't happen every time like that. And to be honest, I think my push Gmail worked fine; it was my pull email that would do it to me. That was on CM9. I don't think I've noticed it happen since I've been on MW.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Hello, i have my nexus 5 for 2 weeks now and I noticed a problem my friend with a N5 doesn't have.(or anyone else) At night, right before I sleep i put my phone on silent so i dont get awakened by calls or anything else . But if i set it on silent the alarm volume gets on silent as well.
Seriously, i didn't have this problem on any other device and everyone sets his phone on silent for obvious reason. I had android 4.2.2 on my older device and even there you could tick "Alarm on silent".
What's causing this bug?
Stock Android 4.4.2
Edit: this is a basic feature every phone has, please dont suggest me getting 3rd party alarms from the google play store, thanks.
Try checking the alarm volume in settings and see if it changes when you put the phone in silent/vibrate.
It shouldn't.
Yes, when i put it on vibrate/silent i cant even scroll the alarm's volume in settings , it goes straight to no volume.
There's a post with users complaining about the exact opposite. They want to know why the phone isn't 100% silent when in silent mode. This would contradict what's happening to you.
Sent from my Nexus 5 using Tapatalk
bblzd said:
There's a post with users complaining about the exact opposite. They want to know why the phone isn't 100% silent when in silent mode. This would contradict what's happening to you.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok, what can i do to repair this bug?
I just tested this on my Nexus 5, and I can confirm that this is NOT happening on mine. Setting the phone to vibrate or even silent has no effect on my alarm setting whatsoever. (See the attached image. Note the vibrate icon in the notification bar.)
Do you possibly have a third-party alarm or other sound-controlling app installed? You say your phone is stock, but do you have anything such as Xposed, that can affect system settings?
I know it's probably the last thing you want to do, but you might try doing a hard-reset, and seeing if the conditions persist BEFORE installing any 3rd party apps. If it's working normally at that point, then keep checking it as you reinstall your apps to see if you can narrow down the culprit. If it DOES persist with a freshly wiped device, then you may want to call Google support, as that would be considered a defect.
Oh! Also, make sure you're on the latest build (KOT49H). If you're on an earlier build for some reason, it could be why your device is acting differently than everyone else's.
jt3 said:
I just tested this on my Nexus 5, and I can confirm that this is NOT happening on mine. Setting the phone to vibrate or even silent has no effect on my alarm setting whatsoever. (See the attached image. Note the vibrate icon in the notification bar.)
Do you possibly have a third-party alarm or other sound-controlling app installed? You say your phone is stock, but do you have anything such as Xposed, that can affect system settings?
I know it's probably the last thing you want to do, but you might try doing a hard-reset, and seeing if the conditions persist BEFORE installing any 3rd party apps. If it's working normally at that point, then keep checking it as you reinstall your apps to see if you can narrow down the culprit. If it DOES persist with a freshly wiped device, then you may want to call Google support, as that would be considered a defect.
Oh! Also, make sure you're on the latest build (KOT49H). If you're on an earlier build for some reason, it could be why your device is acting differently than everyone else's.
Click to expand...
Click to collapse
Hard restted once with the apps being restored and it was the same, then i hard resetted the last time without signing in my google account and everything works fine now, thanks!
did you ever find out which app caused this? i have the same problem
it might be a late answer, but it may help anyone who happens to find this post with this issue (as i did)...
I was having the exact same problem with my alarm, but I noticed that it happened after installing "Alarmy (Sleep if you can)" app from play store. It somehow overrides system volumes, and locks it after uninstall.
I reinstalled it and set the alarm volume from inside that app, and now it works as expected to do (silient ringer with alarm on).
This might happen with other Alarm apps, remember if you did install any.
Hopefully it helps someone, as this happened even on 4.4.4
I was having the exact same problem
joaquin.mik said:
it might be a late answer, but it may help anyone who happens to find this post with this issue (as i did)...
I was having the exact same problem with my alarm, but I noticed that it happened after installing "Alarmy (Sleep if you can)" app from play store. It somehow overrides system volumes, and locks it after uninstall.
I reinstalled it and set the alarm volume from inside that app, and now it works as expected to do (silient ringer with alarm on).
This might happen with other Alarm apps, remember if you did install any.
Hopefully it helps someone, as this happened even on 4.4.4
Click to expand...
Click to collapse
I have figured out that problem happened after installing "Xtreme alarm clock."
And I solved this problem with "Alarmy(Sleep If U Can)."
Thanks for your information.
I am running CM 11-20141008-snapshot-m11-ville and bubba_kernel-2014-07-26_Ville. The problem I am having existed PRIOR to both of these. When I make a call and my current call screen is up, it doesn't recognize touch. I can't hang up, use the keypad, etc. I can hang up with my Bluetooth or by pulling down the notification panel and touching 'hang up'. Everything else works fine. When I am NOT in a call I can use the keypad/dial just fine. Here is a clue, I get an FC when I try to look at my call history.
Any suggestions??
Have you tried to replace the dialer.apk with one from the nightlies? Are you using a theme? If yes, have you tried to switch to default holo theme? If you're using Xposed or ART have you tried to disable them? And last but not least... Have you made a clean install? That is wipe system /data/cache /Dalvik?
There are peole using the same build as you are and nobody reported such issue so my guess it is something specific to your setup or device
Sent from nowhere over the air...
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.