phone answer problems - Touch CDMA Android Development

Been running Haret Eclair on sd, ran fine for about a month. Know all of a sudden it lags and recently won't answer an incoming call.
Sounds like mssmison has a good build but not haret. Any knew eclair builds for haret?

graphic914 said:
Been running Haret Eclair on sd, ran fine for about a month. Know all of a sudden it lags and recently won't answer an incoming call.
Sounds like mssmison has a good build but not haret. Any knew eclair builds for haret?
Click to expand...
Click to collapse
Haret is not the problem, it's just the launcher that kills winmo and starts linux. Can you make calls ok? what happens when you receive a call?

I can make call fine, it seems that when screen is locked the phone will start to vibrate for maybe 5 times before the ringer starts. I get 2 rings and miss call. All the time I push the green answer button and it doesn't pick up.

Sorry, I should have asked this - what build are you running? I assume something from mssmison?

mssmison's xrom-eclair-2.1 beta

turn off vibrate.

Related

Lag on incoming calls

I got a little problem with my g1.
When my phone is in standby and i get an incoming call it lags like hell.
After a delay of about 5 sec. the screen wakes...
I experienced this problem a long time, but always thought it's a ROM problem. After i tried various ROMs, i realized i still have this bug.
i don't no exactly when this problem started, but I think it came with the first donut ROMs.
I also think that it's no spl problem since i got this delay with the stock spl and the danger spl.
Does anyone have the same problem or even know a fix?
Can confirm this. I have a delay of a few seconds between the first vibration, the ringtone and the screen turning on and displaying the incoming call screen.
Zappza said:
Can confirm this. I have a delay of a few seconds between the first vibration, the ringtone and the screen turning on and displaying the incoming call screen.
Click to expand...
Click to collapse
i have the same problem
I have 2 G1s and this happens to me occationaly. I only have a few apps on my phone but my wife has lots of icons and apps on hers. i notice i only get a delay once in a while but she has a delay all the time. last night i updated both a Eclair 2.1-V1.5 from CYM 4.2.13 so far 2.1 seems to be a little faster so we will see...
used to get this a lot
on CM. admittedly i had never done a full wipe from 4.1.99 onwards so it was getting pretty laggy by 4.2.12. i've noticed a huge improvement when running dwang 1.17 and even more so on super d 1.6.
this bug really sucks...i get it on every rom...sometimes i cant even answer the phone...
Does nobody know a soloution?
Flashed latest xROM Eclair by JAC. Under idle, the phone almost always rings after the caller hears the 1st "do do" and before the 2nd.
If the phone is being used, especially with heavy apps (e.g. browser), then it's another matter...

Slow to start dialing

Does anybody know why my hero might be a bit slow at dialing? When I touch a number in my contacts, it takes up to 30 seconds before it starts connecting the call. Sometimes its instant, sometimes its a long time. If I press it twice, it'll try to three way call the person later.
What causes this, and how do I fix it?
I have this problem too as does my hubby's phone.
We have tried damagecontrol and fresh roms and it happens on both of them.
We also get issues with the internet and gps not working on and off so we have to reboot. Not sure at all if this is any way related to the phone calls being so slow to take.
would LOVE an answer to how to fix this!
a dialer without haptic feedback usually solves this, here's one for damage/fresh/sprint based roms. Other wise, try zen's slide rom, dialer works GREAT, fastest yet for me even with haptic on!
gapoochi said:
We also get issues with the internet and gps not working on and off so we have to reboot. Not sure at all if this is any way related to the phone calls being so slow to take.
Click to expand...
Click to collapse
I get the same problem as well. Usually its fixed by turning wifi on then off, or turning gps off then on respectively.
danaff37 said:
a dialer without haptic feedback usually solves this, here's one for damage/fresh/sprint based roms. Other wise, try zen's slide rom, dialer works GREAT, fastest yet for me even with haptic on!
Click to expand...
Click to collapse
I get this problem without even using the dialer though. E.g. going into people, touching a contact, then touching the phone number to call it. The phone just does nothing for a little bit then suddenly it initiates the call. Would changing the dialer still fix this problem?
not entirely sure... possibly, I think it still has to load the dialer app when you do that. Best I could say is just try it. If it doesn't, and you want the old dialer, just pull it from the original zip you flashed and adb push to system/app to replace the one I posted. But that dialer works much better, in my opinion
Mine does this too and has on the stock ROM as well as every version of damagecontrol since 2.06. Sometimes it will dial right away and other times it will wait 10-20 seconds, then turn the screen off and immdiately back on and then dial and other times it just waits however long it wants to start dialing.
I know when I was still on stock and not rooted it would sometimes go into a state where it wouldn't respond to any commands that would make it dial but every other function seemed to be fine. I don't believe that's happened since I rooted and ROM'd it though.
I've used the stock dialer and well as SuperDial and Dialer One and all have had the problem. I've had this problem with haptic turned off/removed and still on. Sometimes waiting a few seconds after unlocking will help but not always.
So far for me, 100% fix has been the slide rom or darch droid (which finally booted for me today!). Both those, not one issue.
-------------------------------------
Sent via the XDA Tapatalk App

new test kernel ..

there is a new test kernel ...
see link: http://forum.xda-developers.com/showthread.php?t=788815
camro said:
there is a new test kernel ...
see link: http://forum.xda-developers.com/showthread.php?t=788815
Click to expand...
Click to collapse
Great thanks for it!
It good kernel: battery, USB and phone sound works on my Topaz with him and Neopeek CM6 build
My TD2 is faster with this kernel. Wake up from sleep is the best i've seen. Will continue to test.
This kernel along with the newest neopeek.com test build is working great! I haven't tried phone calls but I've downloaded many apps and ran them no problem. Also, battery life is AMAZING.
Texting is working good too. I'm guessing phone calls still have the "No incoming calls in deep sleep" bug and the "Push volume down to make incall sound work" bug. Once that deep sleep bug is gone i know a LOT of people will be happy here
Still not as long as windows mobile battery life but it's certainly getting there. The new battery display algorithm is great.
Edit: Topaz HTC AT&T Pure with stock ROM installed.
Edit 2: Phone freezes after about 4 seconds in to incoming calls, happened twice i had to press reset with stylus.
Joshwaa808 said:
Edit 2: Phone freezes after about 4 seconds in to incoming calls, happened twice i had to press reset with stylus.
Click to expand...
Click to collapse
I had the same problem on my Topaz but it would get to 8 sec before rebooting. If you make a phone call out when the device boots into Android then you'll get incoming calls with no problem. The downside is you need to do it every boot.

[Q] Weird entry in call log.

I was calling someone back earlier by going to the call log and when I was in the call log, I noticed something weird. There was an outgoing call to *0000000 as my last call which had lasted for 15 seconds. I know I wasn't touching my phone when the call was made because I was still hitting some golf balls at the range. I don't have the menu menu unlock enabled so it can't be butt dialing either. Anyone have any idea what this may be or what could have caused it?
I'm currently running herodeck 1.2t with minimal apps.
Ummm update your rom perhaps to 2.2 or 2.3? Didn't think anyone uses old roms anymore
®patience is a virtue©
herodeck is GB 2.3.4.
1.2u is out so I'll be upgrading to that when I have time as you need to do full wipes to update that particular ROM.
Hmmmm I'm not to sure then. Hopefully the upgrade will help you out then
®patience is a virtue©

phone.android keeps crashing on JB (CM10)

I've been running hashcode's CM10 build for about a week (KEXEC-cm-10-20121103-UNOFFICIAL-solana) and everything has been pretty solid except each time I end a call with somebody, the phone.android service crashes. This isn't a huge deal because it happens at the end of every call, but nonetheless, I'd like to get all the crashes figured out. Anybody else running into this issue in any JellyBean roms on the D3?
DRELUXOID said:
I've been running hashcode's CM10 build for about a week (KEXEC-cm-10-20121103-UNOFFICIAL-solana) and everything has been pretty solid except each time I end a call with somebody, the phone.android service crashes. This isn't a huge deal because it happens at the end of every call, but nonetheless, I'd like to get all the crashes figured out. Anybody else running into this issue in any JellyBean roms on the D3?
Click to expand...
Click to collapse
Yeah - it happens to me about half the time. I'm trying to figure out if it makes a difference whither it's an outgoing or incomming call or who hangs up first, but can't see a pattern yet.
djbolden said:
Yeah - it happens to me about half the time. I'm trying to figure out if it makes a difference whither it's an outgoing or incomming call or who hangs up first, but can't see a pattern yet.
Click to expand...
Click to collapse
It's fixed in the 12-12 build. Sensor works during phone calls now too.

Categories

Resources