I've been trying to figure out how this could be done for a few months now. My original idea was a .Net managed app wrapped up in a C++ service which would hook the proper WMessage and cause a short vibrate (reg entry to customize strength, duration, frequency, and wave shape perhaps). After looking into the Vibrating Dialpad registry hack and playing with Sound Schemes (see crediting links below), I'm thinking there may be a far more straight forward way using a simliar approach to Vibrating Dialpad. On the other hand, I'm not sure where *vibrate* gets interpreted so it may not be so simple. Anyone have feedback on this? I think even a basic "haptic" screen feedback would be very welcomed by many people and a cross-device solution seems feasable.
http://forum.xda-developers.com/showthread.php?t=300904
http://forum.xda-developers.com/showthread.php?t=340466&page=3
like this?
http://forum.xda-developers.com/showthread.php?t=425063
Yah, something like that I've been asking around for months and this is the first time I've heard of that app. I'll check it out. The "lag when typing fast" could be a problem, but we'll see. Thanks for the link.
Just like Vibrating Dialpad, the resulting vibration is far too long (at least 1 second) even when I configure it for 1ms. Perhaps this is a limitation of something more low-level on the Vouge?
I've tried a couple of these and the lag is always a problem, the vibration wants to be just a slight buzz and linked to the duration of the screen press. It needs to occur instantly too.
The LG touch screen phone seems to do it well.
But in response, I'd pay for a good app.
"I CAN'T GET TO MY PHONE BEFORE IT GOES TO VOICEMAIL!" Sound familiar?
This thread is to discuss and discover/provide work-arounds (and potentally solutions) for the lag time between the initial ring from a caller and the incoming notifications on the android phone. Since there are other ways to make it possible to answer a call before it gets forwarded, other perspectives/ideas/questions/discussion are welcome here as well.
(Since I started the griping here I figure I better follow up.)
After a day or so of being opened, there are already several things we can do to help our phones ring faster posted in this thread. If something is confusing to you, please ask. If you click on the username of a post, you have the option to send a personal message. Unless you are darn sure other people have your question, please use this option. If it turns out your question would better suit this or any thread, you can paste your PM into the thread at any time.
I have to say this so I can rail on people: no matter how many Opening Posts say READ, READ, READ, the people who consistently don't read the thread haven't read the Opening Post, either. Don't be one of those people. The rest of us resent you for cluttering the thread, consequently creating even more clutter because there's too much crap for other people to read. We think you are being ignorant and selfish. This entire forum is public information; try to keep in mind your potential future boss might be checking this out to see how useful you might be in their workplace. So this, though probably not read by its intended audience, reserves for me the right to be even b****ier
In case anybody is inclined to test it, I already discovered that the phone doesn't ring when it's powered down....
The phone Prioritizer, combined with using ogg format, seems to do the best or me: I can't find it anywhere else. If I've posted this wrongly, please holler.
There was discussion going into the cupcake build about the latency increasing. I can't speculate on the cause of the latency, but it seems to have been going from the first OEM builds.
Delay in phone ring
Delayed phone ring (and even more delayed screen activation and caller ID) on incoming calls. Speaking for myself, callers hear a couple of rings before my ringtone starts to play. And there is another couple of seconds of delay beyond that before the screen lights up and the caller ID comes on.
I have been having this problem for the past, oh, ten or twenty updates. I have tried MANY things to fix it. If you hadn't already said that you always reinstall the radio when you flash, I was going to try that next in my quest for a solution. This ringtone delay problem is currently my number one irritation with my G1, and is at the TOP of my list of issues that I hope Cyanogen will address and conquer.
I have tried "renice -20" on the phone program, with no improvement. I have tried moving ringtones2SD from fat32, with no improvement. I have tried reformating all my custom ringtones as OGG, with no improvement. I have tried installing and uninstalling a variety of programs, with no improvement.
I am certain that Janis and I are not the only people with this problem. I have seen it mentioned by a lot of people in a variety of threads. I am glad to see a specific thread about this particular topicl If anyone has figured out a solution, please speak up. If no one has, perhaps reports from enough people will serve to convince developers to look into it more deeply. Anyone else have feedback?
I myself am curious to kno if there is any way to work on this. I have been a happy Rom switcher and each Rom has always given me 2 ring delays. The way I worked mine to get close to 1 ring is to constantly use a task killing APK, which I may add is tedious, and making sure I'm clocked 245min 584max
After I moved my ringtones from sdcard/audio/ringtones to sdcard/media/audio/ringtones a prescribed by Cyanogen when he originally took all the ringtones out, I had to re-pick my ringtone, as I would expect.
The odd thing is I also have to do it when I add (a) ringtone(s) to the folder or delete one or more. Can anyone shed any light for me on how the system/phone app references ringtones? Why would it lose a ringtone to reference just becuase I added one to the folder it's in?
How to test, or one way to do it
I use the home phone or skype, that way I can hear how many rings are actually happening for myself, count actual seconds (ear to the phone, eye on the clock), and I can see what order things happen. No one else,except you guys, has to bear with my hare-brained methods, either.
The last time I tested, the ring actually started before the caller ID popped up, but that was a first for me. Nothing happened until about the end of the second ring from the home phone.
Now I'm running Compcache 32mb, Linux partition swap 128mb, CPU 528/245.
Mines takes about a good 2 to 3 rings on the other side before my phones starts to even vibrate. Itfirst vibrates and then plays the ringtone.
Anyone remember before cupcake, when you got a call, even the call button wouldn't accept the call. Thankfully that's fixed but this still hasn't been fixed.
Mines takes about a good 2 to 3 rings on the other side before my phones starts to even vibrate. Itfirst vibrates and then plays the ringtone.
Anyone remember before cupcake, when you got a call, even the call button wouldn't accept the call. Thankfully that's fixed but this still hasn't been fixed.
I don't think you will get rid of the 2 rings on the other end before the phone rings. That is probably just the network finding your phone. However, I have had issues with my phone vibrating 2 or 3 times before the ringtone would start playing. I turned off vibrate and it helped. Then I turned it back on and disabled Missed Call. Now there is barely one vibrate before the ringtone starts playing. I'm turning off Missed call until they have an update for it.
I also found that the battery status widget causes a huge delay if you have it set to update as soon as it changes. It checks everytime the phone comes on and that slows things way down. I set it to update every 60 seconds and it still had some delay but not as much.
bout time
glad 2 see its not just me, i almost missed out on a job cause my phone will 'pause' so long it goes to voice mail b4 i can answer. seems like the issue comes and goes, but when its bad, its horrible, 1st it will vibrate for 2-5 sec b4 it rings , then its about 3 sec b4 the id info displays and when im lucky the call button wont react for like 4 or 5 pushes. sum times the phone app force closes, which means 15-30 sec wait while it reacquires the network and if it force closes the call doesnt show up in the call log.
iv had this issue with all the rom's and yes i reload the radio about 2 times a week, but even the stock 1.5 gives me the same issue
ok enough venting, any dev's that have might have an alpha or beta fix im willing to test!
SamCookD405 said:
glad 2 see its not just me, i almost missed out on a job cause my phone will 'pause' so long it goes to voice mail b4 i can answer. seems like the issue comes and goes, but when its bad, its horrible, 1st it will vibrate for 2-5 sec b4 it rings , then its about 3 sec b4 the id info displays and when im lucky the call button wont react for like 4 or 5 pushes. sum times the phone app force closes, which means 15-30 sec wait while it reacquires the network and if it force closes the call doesnt show up in the call log.
iv had this issue with all the rom's and yes i reload the radio about 2 times a week, but even the stock 1.5 gives me the same issue
ok enough venting, any dev's that have might have an alpha or beta fix im willing to test!
Click to expand...
Click to collapse
This isn't a ROM problem, it is a phone resources problem. There is something dragging your phone down. It might be different for each one of us having issues.
Ditching userinint.sh
I rm'ed user.conf and userinit.sh to use Cyanogen's default compcache and default CPU scaling. I re-downloaded Swapper and set up to use my 128mb (overkill) linux partition.
I got lights & vibrate at the end of the first ring, I got caller ID and ring just about halfway into the second ring.
Using the attached user.conf I didn't get ring or caller ID until the end of the second ring, sometimes after.
So I installed missed call (donation) and maxed it out. No change. Still getting first response at the end of the first ring, and ring and caller ID about 1/2 way into the second ring.
Maxed out my CPU at 528/528 with SetCPU. Got about .1 of a second advance. It starts to ring and gave me caller ID about 1/4-1/3 of the way into the second ring. Hard to tell, but a bit earlier than 1/2. The second and third time I tried it, it wasn't as fast. Caller ID came up just barely into the 2nd ring, but ring didn't start until the end.
I think the first ring is network time. For the duration of it, I'm guessing, the call isn't at my G1 yet. This sucks.
I think the phone app is set to vibrate and light the phone first, and leaves time for this to happen. It may be because it's the fastest way to alert the user, since looking for ringtone, handling it and sending it can (doesn't always) take some time, it just uses the reliable method and then triggers the less reliable, already slower ring process.
So maybe Cyanogen, or anyone who's familiar with it, can see if this ring vs. vibrate lag can be eliminated. I'd rather have the phone look for a ring first.
But, if you need to get to calls that quickly, set it to vibrate for now?
I downloaded the ogg ring package from the custom userinit thread. Trying that next.
This doesn't contribute anything to the thread at all (except maybe encouragement) but I'm glad someone is bringing this annoying "feature" up for public discussion.
I keep myself updated with CM and kspec oreo as a theme. As it is right now, I get one ring and the call goes to voicemail. The caller ID display actually lights up after the call has been forwarded. Hope the culprit (if there is just one) is found soon.
There has been a parameter on some of my previous phones called slot index. It was available through a keypad menu, it set how often the phone polled the tower. It sped up the ring responce dramatically.
Tried the ogg files, woohoo!
I've got my CPU set to 528/384 with SetCPU, Linux partition swap 128mb with Swapper (I can set them on the fly without rebooting), and used the ogg files in media/audio/ringtones, and I get ring and caller ID at or before the beginning of the second ring, a split second after the vibrate started. I tried messing with CPU speeds, and it does seem to make a difference as to when the ring actually sounds. I'd say about 1/2 a ring between 245 idle and 528 idle with 528 max for both.
I also have my frequency scaling at 16. So I think that means if 16% of my CPU power is being used, it hops it up from min to max. OK, maybe not 16%, I don't know how the numbers translate, but 16 is low, so I'm running at 528 when a squirrel farts outside.
I have BatteryLife and Missed Call enabled.
So there's the pause after the first ring to deal with, but I really don't think it's the phone after this. maybe we need to join forces and barrage T-mobile with complaints. I mean, why have the ringing on the calling end start if the network isn't connected?
Well, at least we won't ever have to worry about appearing too desperate.
2 or 3 bars, so my signal isn't that great. I'm in the suburbs (not that I love it, but it's where I am).
I'd be very curious to find out if others who have their CPUs running high and are using ogg files are getting a different response. I'm also going to try it in different locations.
I am going to suggest to Cyanogen to include the ogg fles as part of his add-on collection.
Face of Ring
I think I may uninstall this, even though I love it. It bumped the ring to after the caller ID. Caller ID still popped up during the pause after the first ring, but the ring and vibrate didn't happen until mid 2nd ring.
(I'm using rings to measure because 1. it's easier 2. the rings/pauses are shorter than a second 3. in large part it's the caller experience we're concerned about. I don't have a stellar chronometer handy, either.)
Well, thanks for starting this thread, Janis. It's a common complaint across all builds. I've grudgingly resorted to calling my phone after every reboot, just to try to keep the ringtone and I'm guessing Phone.apk?? in memory for as long as it will stay in there. That definitely helps for awhile. I know we're trying to make these phones more into computers, but they're still phones and as such calling and communications should be the main priority. I've converted to .ogg, however they are larger files than the .mp3's I converted from. Maybe I should have used a smaller bitrate. Anyhow, it doesn't seem to make much of a difference. I've tried placing them in /sdcard/media/audio/* and /system/sd/media/audio/*. Does not seem to make much of a difference.
I want a hardware hack to increase the RAM...I hate the trade off we're facing. Losing physical keyboard to obtain greater memory. Or make a "Dream plus" with more RAM. I'd even be happy with just a slight increase in internal storage or none at all and more RAM. The devs here have done wonders with the hardware provided, and the implementation of apps to sd has really made this seemingly poor thought out device (in areas), one of the best. I remember, before I was brave enough to attempt apps to sd, having to decide which app to uninstall, just to make room for one I might want more. Seems like ages ago. While I'm reminiscing, I'd like to give a retro shout-out to Lucid and MarcusMaximus who were pioneers in this area and others.
Sorry, about the tangent...but we've made great strides on the computer end of this device...let's regress, so to speak, and make the phone the primary function, hopefully without backsliding on progress we've made on our phones as a mobile computing device.
EDIT: I've also uninstalled "AutoLock" for this reason, because I'd read somewhere that this may be the culprit...I may have seen positive results, or possibly just placebo.
I have the app "Caller Lookup" installed and have noticed tha that app comes up before caller id and or the ringtone. Its there after 1 or 2 vibrate pulses.
make sure T-mobile, or whomever, has your time-before-forwarding maxed
My poor 74-year-old mom was having a heckuva time getting to her phone in time. As per the instructions from a Tmobile service rep, we punched a # and some digits and got a 65 second ring time. This was a year ago or so. I was told that same week that if my OS on my WinMo phone couldn't do it, there was no way they could (there's a way to set it in WinMo), which was BS.
I know it takes network time/space/bandwidth to let it ring, and it's not paid time. I wonder, not to be a rabble rouser (heh), if we kept calling them, maybe hundreds of us if we could get it going, and made them spend more money on customer service than that bandwidth, if they'd bump that.
Anyone?
Maybe someone else can help me with this.
Every so often during the day I keep getting a random notification sound with no visual as to what it is. The sound is 5 tones going in a descending pattern and sounds metallic. I do not have NFC turned on nor the facebook app. I checked all my apps and sounds. I even read a lot of threads else where and tried everyone's suggestion. Still does it. I searched my phone for *.ogg and *.wav files. Nothing.
I do have a wallet case but since NFC is off its not that. I've never heard this sound before. It only started a few days ago and I've have this phone for over a month. FYI I'm running the Hola launcher and omni swipe if that helps. Any suggestions?
I am thinking to uninstall ALL my apps and see if it still does it, but I really dont want to have to do that if I can avoid it.:silly:
Bump
Anyone?
Maybe it's the louncher. .. trai with the touchwiz
Sent from my SM-N915F using XDA Free mobile app
It's not the launcher. It doesn't matter.
This is why I hardly ask anything here. No one cares.
If your not a popular member you never get a reply.
I'll just ask my questions elsewhere where people actually care about you.
Are you using googles smartlock feature? When I first started using it I was receiving this weird notification which sounds like what you're talking about. It don't do it no more for some reason but man was it so annoying not knowing what the heck your phone is trying to tell you.
Sent from my SM-N915P using XDA Free mobile app
Hey there.
I have been checking back on this topic for a while because my wife's Note Edge is having the same exact problem. I even reached out to Samsung Mobile Support and they can't even figure out what it is. All they did was tinker with the sound settings and asked me if it was fixed. I have tried disabling all possible notifications from all possible apps. The only thing left is to do a factory reset it seems. Any luck on your end?
VGMStudios said:
It's not the launcher. It doesn't matter.
This is why I hardly ask anything here. No one cares.
If your not a popular member you never get a reply.
I'll just ask my questions elsewhere where people actually care about you.
Click to expand...
Click to collapse
Well that's not a pessimistic attitude or anything whatsoever! lol. Here's the thing... It might help to try and remember that nobody is on here getting paid to spend their time answering your questions all day long, so unfortunately it's inevitable that there will be times when people might just have to figure their problems out on their own or just be forced to wait until someone responds.. no matter how "popular" they might be.
This entire community wouldn't exist if weren't for all of the people on here who have been and are willing to spend their own free time sharing their knowledge with and helping others, so it's pretty ridiculous to sit there and act like it's a personal assault whenever nobody answers your question right away! From my experience on here people (including myself) are always more than willing to help out whenever they can (as long as the people are willing to help themselves too), but since nobody is getting paid people need to realize that it's more of a "self help" type of community than anything.
There are literally mountains of freely available information for people to search through to try to find their answers with, and with enough determination and persistence 99% of the time people could answer their own questions without ever even having to ask. So I'm definitely not trying to be rude or anything but it's just all in how you look at it.. because when people come here expecting to be handed all of the answers then they're most likely going to be disappointed and upset, but when you come here looking to help yourself instead you'd be surprised how much of a difference it makes and how rarely you'll have to ask any questions.
Anyway I'll try helping with some suggestions below since they're having the same problem too..
Mercodious said:
Hey there.
I have been checking back on this topic for a while because my wife's Note Edge is having the same exact problem. I even reached out to Samsung Mobile Support and they can't even figure out what it is. All they did was tinker with the sound settings and asked me if it was fixed. I have tried disabling all possible notifications from all possible apps. The only thing left is to do a factory reset it seems. Any luck on your end?
Click to expand...
Click to collapse
Ok I've actually had a similar problem in the past and I can't guarantee anything but hopefully this might help..
In my situation it turned out being "profiles" that I didn't realize were turned on, and they were causing rogue and unknown sounds to happen because they were overriding my ringer and media volume settings based on the time of day it was. So all I had to do was turn off the profiles and it solved the problem, but it depends on the rom that you're on as to whether or not profiles like that are even an option.
If not another thing I'd recommend doing (and I'm obviously not sure what all you've tried so I'm just trying to cover the bases just in case) is to get a root explorer (as long as you're rooted.. if not I'm honestly not sure what to tell ya) and navigate to the root folder .. then go to "system/media", and inside there should be a folders called ui, notification, and ringtones.. and this where all of the default notification sounds are located. I would go through and listen to each one of them (they should be .ogg files) and see if you can find a match to the one you're hearing, and if you do then you can just rename that file .bak instead of .ogg and that should stop it from playing randomly (basically a bandaid type fix).
If it's not any of the system sounds then you've basically narrowed it down to where it's most likely an app that's making the sound. If that's the case then what I'd do is go into Titanium Backup and filter it to only show "user apps" and then have it sort them by the date which they were installed, and then I'd just start going down the list looking for apps I've installed that could possibly be making the sound.. that way even if you have a general idea around when the problem started happening you can match that time frame up with apps that were installed around that time to narrow down your search (if that makes sense anyway).
Anyway that's what I would do to start at least and hopefully it helps!
Sent from a ridiculously modified ColecoVision
heh. I have an idea. You know those crappy applications on the edge? Some of them are games. I remember i used to have this issue with the memory one. Remove them from the edge. No root required. Just remove the panels from the panel configurator.
VGMStudios said:
Maybe someone else can help me with this.
Every so often during the day I keep getting a random notification sound with no visual as to what it is. The sound is 5 tones going in a descending pattern and sounds metallic. I do not have NFC turned on nor the facebook app. I checked all my apps and sounds. I even read a lot of threads else where and tried everyone's suggestion. Still does it. I searched my phone for *.ogg and *.wav files. Nothing.
I do have a wallet case but since NFC is off its not that. I've never heard this sound before. It only started a few days ago and I've have this phone for over a month. FYI I'm running the Hola launcher and omni swipe if that helps. Any suggestions?
I am thinking to uninstall ALL my apps and see if it still does it, but I really dont want to have to do that if I can avoid it.:silly:
Click to expand...
Click to collapse
Not sure if this is gonna help you or not. But yesterday I started to getbthe same metallic noises, I only recall 1 change to my settings and that was installing the live wallpaper on the lock screen to show me pictures based in weather and such. And since then every hour or so it makes the sound. Try to find out if you did the same thing.
Random notification sound
I am having a similar problem which has been widely reported but none of the suggested fixes are working for me. The notification tone keeps sounding in a seemingly random way. There is no notification to match the tone. This is not just a beep or random noise. It is the default notification tone. (Skyline for completeness). This happens maybe 5 or 6 times in 24 hours. It has been happening for about 10 days.
I am running Android 8.0.0 (Samsung Experience version 9) on a Galaxy S8. The phone is not rooted.
I have turned off all notifications individually.
I have turned off notifications for the phone.
I have turned off notification reminders (it was never on).
I have turned off NFC and bluetooth.
I have checked under Accessibility settings.
I have uninstalled every app installed in the last 3 weeks.
I can reproduce the NFC and credit card issue but that is a single beep and not what I am talking about.
I have installed 3 different notification log readers (NS Notification, Notif log notification history and Notification Log). None of them show any activity at the times when I am getting the spurious tone.
When I re-enable notifications for Texts, Messenger and WhatsApp, I still receive these as normal.
I recently got a new dual band router and thought maybe the tone was the phone jumping from 2.4 to the 5 Ghz band or vice-versa. It wasn't. I thought it might be the phone jumping from telecoms provider to WiFi. Tested that too and that's not it.
Next step is a factory reset which I am trying to avoid.
I know this is bringing problems to the table, not solutions but this is really bugging me. Any help would be greatly appreciated.