Related
Apologies if this question has been asked and answered before, but if so, could someone please redirect me. This is my first time on this forum. I've had my HTC Touch Pro (Raphael) for a couple of months now, and cannot get round the problem that whenever I receive a call, I somehow manage to cut it off before I can get the phone out of my pocket. I have tried several different cases (the current one opens like a book, so doesn't press any of the buttons), but something happens in the process of removing the phone from my pocket, however gently and swiftly I try to do it, which means that all I get is a "missed call" message, even after only one ring. If the phone is on a flat surface, it will ring for a long time, so it's not that setting. This is SO frustrating, especially when you try to see who called you, and it just comes up with "unknown caller".... it's also costing me a lot of money having to phone people back when I do know who they are. Please help somebody. I really like my little phone, but it may well end up being thrown out of a window at this rate! Thank you!
Check out this utility here on XDA. Works great. Unlock the phone by rolling it over. It uses the gravity sensor.
http://forum.xda-developers.com/showthread.php?t=422871
Many thanks for that. We've installed this thread, although I'm not really clear about what it does. It seems I can now lock and unlock the phone by turning it clockwise and counterclockwise respectively along its axis (in addition to the long press, which is what I usually use to lock the phone).
I tried answering one call whilst it was locked, but couldn't free it up to press the "answer" key until I had turned it several times. Fortunately, the caller was quite patient! Is this just a technique I have to get used to, and will it mean that I get a chance to answer calls before the connection is severed? Sorry to sound so thick, but this is all very new to me.
Sarahah said:
Many thanks for that. We've installed this thread, although I'm not really clear about what it does. It seems I can now lock and unlock the phone by turning it clockwise and counterclockwise respectively along its axis (in addition to the long press, which is what I usually use to lock the phone).
I tried answering one call whilst it was locked, but couldn't free it up to press the "answer" key until I had turned it several times. Fortunately, the caller was quite patient! Is this just a technique I have to get used to, and will it mean that I get a chance to answer calls before the connection is severed? Sorry to sound so thick, but this is all very new to me.
Click to expand...
Click to collapse
Go to the settings menu and edit your SensorLock preferences to lock the screen only on an incoming call thus leaving the buttons unlocked.
Maybe the "face down mute" is happening to your calls? Try disabling it.
Um..... how?
answer keys disabler
You the thread below, it disables the onscreen answer buttons while ringing. Helps me getting the phone outta my pocket when ringing
http://forum.xda-developers.com/showthread.php?t=425650
Ooooh. Thank you. Sounds like just what I need ... watch this space!
if u want to thrown your htc trough windows, how about if u thrown it to my window bro.
HHumbert said:
Check out this utility here on XDA. Works great. Unlock the phone by rolling it over. It uses the gravity sensor.
http://forum.xda-developers.com/showthread.php?t=422871
Click to expand...
Click to collapse
Gravity sensor... I ever seen this technology on nokia phone. but until now I'm still amazed by this technology. how this sensor works..
sorry 4 my english cause I'm from asia
Ah Dedy - if I win the lottery I shall come and throw a brand new Touch Pro through your window, I promise! I'm afraid that I'm having far too much fun with this one (despite the problems in my pocket) to part with it just yet though. Hope you have a great Christmas, and maybe Santa will bring you one, you never know!
The chair of my company is paralyzed from the neck down though has enough limited mobility with his arms to manage his wheelchair yoke and an oversized trackball for his computer. Whether in the office, home or wherever, he relies on either his secretary or his handler to call someone for him. He'd like to call people himself with a cell phone that someone leaves on a desk or a table for him without further assistance and wants me to make it happen so I turn to you for ideas (and maybe a registry tweak).
I set him up a few years ago with voice recognition software on his computer and that has worked out very well so I'm thinking MSVC. But the first and hopefully easiest obstacle is how to get the phone, a Touch Pro or Diamond specifically, to default to speakerphone. An earpiece is not the best option because that requires someone to put it on him (and take it off if it's wired) and the battery eventually dies. Any way to do that?
The next hurdle is how to get the phone to initiate whatever command that is the equivalent of pressing the button on an earpiece that triggers MSVC, hangs up and answers incoming calls ideally with the screen off so that the battery doesn't die too quickly or so that the phone doesn't need to be plugged in. So, again, can move his forearm and *maybe* be able to have enough coordination to hit the circular button hard enough to use that though he has no muscle control in his fingers so the pressure would rely on the natural stiffness of his fingers (he uses his thumb to click the large trackball buttons). On the other hand, I could map all the buttons surrounding the circle to do the same thing perhaps. But it would be fantastic if he could trigger the phone by shaking it a little to, again, do the same thing that would be done by pressing a bluetooth earpiece's button.
So, 1) how can I get a WinMo phone always to default to speaker and 2) can he take advantage of the accelerometer of the Touch Pro (or Diamond, whichever) to map a soft jiggle (the phone would otherwise be stationary on a flat surface or fully off) to trigger MSVC? I guess he doesn't need to be able to hang up and incoming calls could be set to automatically answer so if those two functions are out of reach that's not a dealbreaker. And leaving the phone on in order to take advantage of the screen for touching, though less desirable, is also an option as his handler can plug the phone in. Or do any other approaches come to mind?
I grately appreciate it.
Doug
Thought I'd take a shot at a possibility. Since you have his PC voice enabled, what about using something like Pocket Controller? I don't know if it can be voice controlled, but it might be worth exploring something like that.
it might be a drain on the battery but maybe something like having a script that runs msvc once a minute so if he need to call someone just wait and then say what he needs to say. or get him an oqo with data and set him up on skype and use dragon speaking software
get a bluetooth for car like : http://direct.motorola.com/ens/carkits/learn-IHF1000.html
install Cyberon Voice Commander on your phone for voice dial. you can answer and dial with one button and voice cammand.
Hmm.. how about windows Vista's built-in voice recognition software? although it takes little time, I did manage to make it do everything I wanted to do without my touching anything.
How about using My Mobiler to control it from his pc
http://freewareppc.com/utilities/mymobiler.shtml
Sorry to post such an unconstructive reply, but what use is a touch-heavy-reliant phone like Diamond or same-thing-but-with-HW-keyboard like Touch Pro to a quadriplegic?
In my humble opinion you should get a BT handsfree with a proper full-time-phone like Nokia or Sony ericsson.
Again sorry for actually not helping much with your problem. But still, my opinion stays the same as mentioned above. Both the telephones are more reliable on functional hands then others.
Thanks!
Wow these are all very good and equally appreciated suggestions! Feels like I've got enough to start googling and hopefully help this guy out. I am truly grateful for the time you all took to respond. I'll post if I have success or problems...
You people are fantastic.
Doug
"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?
(please delete the other thread)
N1 suffers from one simple but debilitating hardware limitations - lack of hardware buttons.
Since trackball clicking is rarely used, it would be nice to assign a different function to it.
The first function coming to mind has to do with the fact that the device is a phone -
make trackball into a "Send" button.
This is what it should do:
1) whenever not in the dialer app, clicking trackball should bring up/start the dialer.
2) when in the dialer app, and a phone number was entered, clicking trackball should dial the number.
3) when there's an incoming call, clicking the trackball should answer the call.
I know some people with arthritis who would kill for such an app.
Thanks.
If such an app. were to be created, how about the case where the foreground process requires the use of the trackball click? Then every time you clicked it, the phone dialer would load.
I also don't personally thing the Android APIs would allow such a global hook (w/o root), but I'm not the best dev. out there so I'll let the more experienced respond to that one.
jayshah said:
If such an app. were to be created, how about the case where the foreground process requires the use of the trackball click? Then every time you clicked it, the phone dialer would load.
Click to expand...
Click to collapse
Well, that's the whole point.
You mean like a game? So far, games might be the only programs where you HAVE to use trackball for functionality.
I think all other programs allow touch screen input in place of the trackball.
Since I never use the trackball for anything, and I've seen a number of comments with the same sentiment (ie "trackball is useless"), I'd gladly trade the entire trackball function (including moving the cursor with the ball) for the ability to have a hardware "send" button.
I'll personally pay 50 dollars to a man/woman who can make this work. Then they can collect the money from thousands of market goers who'd would prefer a useful hardware button over a useless one.
Just a small bump.
why is this in the development section?
/sarcasm
jesus people your right stuff like this should be posted next to / under/ above threads like Cyanogen and Amon_RA
And how would you handle the movement of the ball when it rolls? I find when in recovery, it doesn't take much for the trackball movement to register and overshoot the options I am aiming for if not careful. Obviously a sensitivity setting would be the recourse for such a dilemma but still...or were you thinking that anything beyond buttonOn (false function obviously) is ignored?
Technically you could go as far as to have the tracball pressed trigger the dialer. From there you can scroll to call log, contacts, favourites using the trackball and then scroll down if you so desire.
I do find it odd that the phone has this hardware button and rarely is it actually used.
I think being able to touch the trackball and force the phone out of sleep is a sound expectation for this phone...the fact it isn't there is odd.
just get a sense or blur rom, that fixes everything
PsychoKilla666 said:
just get a sense or blur rom, that fixes everything
Click to expand...
Click to collapse
hahaha...
in other news, plenty of people have no interest in senseUI
One more bump.
Someone should really write this program.
Using the trackball to bring the phone in and out of sleep would drain your battery. That trackball is way to easily pressed (ie in your pocket) to be of any use as that function, but I would love the phone/send function. Would be wonderful as I hate having a phone shortcut on my homescreen.
Would be willing to pay or donate as well.
APrinceAmongMen said:
Using the trackball to bring the phone in and out of sleep would drain your battery. That trackball is way to easily pressed (ie in your pocket) to be of any use as that function, but I would love the phone/send function. Would be wonderful as I hate having a phone shortcut on my homescreen.
Would be willing to pay or donate as well.
Click to expand...
Click to collapse
Thank you. One of very few people who seem to understand this problem.
Anyway, the community's reluctance to implement this feature is a seeming indication of difficulty to do it. Maybe Android OS isn't that flexible; or maybe it's just too new, so people haven't really learned yet how to do things with it.
After all, the Win Mobile OS has been around for ages, and sure enough, as soon my Sprint Touch Pro2 was released, I had an app to rebind all the keys to whatever function I wanted.
Perhaps, in the future, we will see an Android app like the one I want. But, to my greatest disappointment, it may be years...
bump bump bump
I'll bump it one more time.
Any progress with this feature?
Another month has passed...
Has any developer figured out if it'd even be possible to make an app like that?
Thanks.
Just thought i'd share this with the community. You can do LOTS of really cool stuff with this app. If you get if from the website rather the market you get a 7 day trial. Look in the wiki for examples and tutorials of what you can do with it.
I'm face down in this app all day, almost every day.
I've gotten it to do some nice things, such as get the area code of the current caller and display it in the notification area or as a toast notification (the grey popup box, like when you get superuser notifications). I'm currently devising a way for it to do this for country codes, but some of these country codes have some oddly specific rules, and I'd rather it not have 290 profiles for 1 function
It replaces my alarm clock in the morning, and it turns the alarm off if I unlock widgetlocker.
When I flip my phone face down, it goes to vibrate mode.
I found a blog/forum post where someone had made a popup list of launcher icons when you plug in headphones, and I like that.
I use it to pin lock apps, but that's far from perfect. It did replace an app I had for that purpose.
I have it send WOL packets to my computers at work; depending on the time of day and the day of the week, it chooses specific computers.
When I'm at my home screen, I shake the phone up/down and it goes through my menus and applies the rendering effects found in CM7, kind of like the Chainfire shortcut.
If I get a missed call, meaning I didn't answer it or hang it up, it responds to the missed call with a text message. Too bad there's not a way for me to find out if that number is cellular or not, and I can get a phonecall from anywhere in the US throughout the day because of work
I had, for a little while, been trying to replicate JuiceDefender's methods by using a series of variables and controls, with profiles to enable and disable almost all interfaces for comms on the phone. The way tasker works when the screen is off, however, caused issues so I went back to reinstalling Juicedefender. I really only wanted to have a cleaner notification bar
I also got some profiles to make it work like the Screebl app, but it has since quit working with the newest tasker updates.
Very well worth the money however. I'd have easily paid 15 dollars for this application