yashsingh1/xdaforums huggingface dataset:
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
That's exactly why I think it is a problem with the current batch of developer 2.2 (Froyo) ROMs.

As I said, I don't make that many calls, so I don't really know how often it happens - but given that it has happened to me a couple of times now (given the small amount of calling that I do), it makes me think it is not just a signal reception issue.

Which ROM and Radio firmware are you using BTW?
[Droid Eris Q&A, Help & Troubleshooting] zwade01:
I've used kaos for about a month and been on celb for almost a week and have not had such an issue. I use my phone frequently for work, too. I have had the current radio from the july update since a week after it was available.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
Bump.

We now have 15 people on XDA (in the Eris forums) reporting the symptom:

bftb0: Tazz V6; Kaos Froyo V29 [Froyo]

jrozga: (unknown) [Froyo]

carycooke: Tazz V8 [Froyo]

tburns: ??? [Froyo]

mcook1670: "All Froyo ROMs" [Froyo]

punkxdead: CELB [CyanogenMod]; CELB Froyo [Froyo]

Macrodroid: Kaos & Tazz [Froyo]

droiderisuser: ??? "2.1"

danwguy: CELB 2.7 cyamogenmod 5.0.8-DS firmware 2.1-update1 [CyanogenMod]

pablocasiano: WW4.6, KaosFroyo V29

crax0r: KaosFroyo V29

tjthebest: CELB 2.8-CM5.0.8

mistaj: CELB 2.8-CM5.0.8

npong: CELB 2.8-CM5.0.8

mflane: CELB 2.8-CM5.0.8

Some of them say "it happens all the time"

And 10 more people over in the AF Eris forum reporting the same oddity - on different Froyo/AOSP ROMs:

erisuser1: Tazz V6; Kaos Froyo V29 [Froyo]

snozzcumber: Kaos Froyo V?? [Froyo]

TJTHEBEST: CELB 2.9 [CyanogenMod]

MrBojenglz: Buufed v???

BlueDC2: CELB v?, Kaos V?

rick311:

BellaSkye: Kaos V32

Kaessa: Kaos V32

tpatnoe: Kaos V30

rc346: Kaos V34

funkyfender: "CM6"

john58543: KaosV30

So far, only one user has said "this also happened to me on a 2.1 ROM" - droiderisuser

[ Edit ]: At least two people have reported this on older radios, and and also on non-Froyo (but CyanogenMod ROMs)

If it happens to you, and you have the SDK set up on your PC, and it is convenient to do so, try to make a note of the time when it happens, and then when your call is complete, dump a "logcat" to your PC, and post up the log during that same minute here.

C:\blech> [B][COLOR=green]adb shell logcat > strange_call_reconnect.txt[/COLOR][/B]

[I](wait about 30 seconds and then hit ^C (Control-C) )[/I]
[Droid Eris Q&A, Help & Troubleshooting] mcook1670:
I've had it happen on all Froyo roms. I work for the FDOT so I'm on the highway 8 hours a day. I don't know if its the phone changing towers or what. I always have a good signal because the towers are next to the highway. Not sure what it is but its annoying
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
Houston, we have a problem.

TJTHEBEST over on AF indicates he experienced the same problem using an older radio firmware on CELB

I have not found any evidence to support or deny jrozga's claim that this is a Froyo "feature", rather than a bug. I'll try to poke around a little and see if I can find anything further.
[Droid Eris Q&A, Help & Troubleshooting] punkxdead:
I also had this problem with CELB with the 2.41.04.02.02 radio. I switched to CELB Froyo after it 'matured' (hoping to resolve it) and still had the issue. I have since switched to KaosFroyo v29 and the latest "July" radio. The issue is still present.

BTW Heres a quote from my post in the CELB Froyo thread awhile back:
[Droid Eris Q&A, Help & Troubleshooting] Duffman3005:
Never happens to me, and I make phone calls about twice per day.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
punkxdead,

Thank you for that detailed report. Very useful information

Turns out that TJTHEBEST from AndroidForums experienced the problem on 2.1 CELB, which is not Froyo - but I guess it is a CyanogenMod build. That further corroborates your experience.

So far, nobody has reported this in a Sense-based ROMs. I'm a little fuzzy on the genealogy of the kernels in the various roms, although I suppose the problem could also be occurring in "rild" or it's supporting libraries.

It's not a show stopper by any means, but it is annoying; it would be nice if we could figure out how to get it fixed, since it seems to appear in lots of different dev ROMs.

If you are able to do the 'logcat' thing to see if we can find some more info, please give it a try; I will do likewise.

bftb0
[Droid Eris Q&A, Help & Troubleshooting] Macrodroid:
I can confirm the 3g to 1x theory. This has happened twice on my phone, several times on my wifes since,we loaded tazz v8. It also happens on kaos. Not on any of the 2.1 roms ive used. Each time, the phone,is,in the 1x data state. I've had it on speaker amd watched this happen each time. When 3g comes back, so does the,other caller. I think it may have something to do with network selection in froyo.

I have recently changed mine from automatic to home only... So far, no bug yet (only been a couple of days, though..).
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
Hmmm. Interesting. I think EVDO (3G) and CDMA Voice are mutually exclusive (simultaneously, anyway - a fundamental technical limitation of the way EVDO is implemented as an overlay in CDMA networks). I suppose it could be that if the ROM thinks that the voice call has ended, the "3G" icon appears right away. So it's not too surprising that you would see something changing in the display at the moment the call is "temporarily lost".

bftb0
[Droid Eris Q&A, Help & Troubleshooting] Macrodroid:
I'm not really sure what the network option really would do. I do know that froyo isn't an eris os, so maybe it's something related to how it interacts with our phones... Either way, i'm waiting to see if the bug comes back on home only. Still love froyo, regardless!
[Droid Eris Q&A, Help & Troubleshooting] droiderisuser:
Not sure if this helps but I have an Eris and pre Froyo when I was using Plain Jane I believe it was not sure precisely but It was a 2.1 rom for sure I had this happened to me quite frequently. So I would assume it is not just a 2.2 issue.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
It has already been reported by users of CELB which is a "2.1" Cyanogen 5.0.8 - derived ROM. So, so far the problem is not restricted to a specific radio, nor "Froyo", but it does seem to have CyanogenMod code bases as a commmon element.

It might be useful if you can figure out/remember exactly what ROM it was - so far, nobody has conclusively reported it on a Sense/HTC kernel ROM. (I'm including in this latter class of ROMs those that used Zanfur's OC kernels, as I believe - but am not completely sure - that Zanfur built those from patched HTC kernel sources).

bftb0
[Droid Eris Q&A, Help & Troubleshooting] danwguy:
I am using celb 2.7 which is cyamogenmod 5.0.8-DS firmware 2.1-update1 and it happens to me all the time. I have been using the celb line for a very long time and have never had this problem until I updated to celb 2.7 but now almost everytime I'm on the phone for longer than 5 mins it will vibrate, go back to the lock screen, then the speaker will come back on and I can hear the person again. hope that helps with ROM and version and anything else needed to address or fix this issue.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
Thanks for the feedback.

Are there any Eris devs currently building CyanogenMod - based ROMs reading this thread? (You don't need to commit yourself to doing anything; just give us a shout to say "Yeah, I've seen the report".)

I realize that the Eris is not (currently) an officially supported CM device, but the CM devs might still be interested in this report - if this gets figured out, it seems like it's going to take a change in the CM source tree.

bftb0
[Droid Eris Q&A, Help & Troubleshooting] pablocasiano:
Ive had the same issue with these random dropped calls and then returns,it has happened running white widow 4.6 and on kaosfroyo v29 these are the only roms i have ran since 1st rooting.
[Droid Eris Q&A, Help & Troubleshooting] crax0r:
I've reported this issue in KaosFroyo v30. I upgraded the radio and I still have the same problem.
[Droid Eris Q&A, Help & Troubleshooting] Macrodroid:
Network HOME seems to work...

Ok, don't know how this will help, but for the past week I've had my phone set to HOME only on my network. I've placed several calls each day, all in locations where I have had the "undead" drop, so far no repeat! It seems like the problem has gone away with this change. I also have noticed that my phone no longer switches 3G to 1X at certain locations, 3G remains solid. I've switched between Kaos, Tazz 1.0, Evil Eris 4 and Zen, testing this on all these Roms...

This week, I'm back on "automatic" for my network option, just to see if the problem DOES come back. I'm wondering how 2.2 determines network switching, compared to the 2.1 roms...?
[Droid Eris Q&A, Help & Troubleshooting] richiea19:
Okay, not too familiar with ARM architecture. I know segfaults are, in my experience, are from accessing memory that has been released.

READ: autokiller settings set too aggressive? If it is releasing memory that needs addressed...
[Droid Eris Q&A, Help & Troubleshooting] aandrsn:
2.42.04.02.02 baseband version with kaosfroyo v34

same weird issue, not often, only seem to notice it happen talking to my mom, she has a tmobil wing on their service. It doesn't happen talking to my friends on verizon. But I can't see what that would have to do with it. That's just all I can think of as far as a coralation.
[Droid Eris Q&A, Help & Troubleshooting] screamingmouse:
I have had these undead calls on Nonsensikal which is based on CM6

I have also noted Last.fm drops in a similar fasion. I'm trying the home only fix to see if that works, and if not I will try the "lib swap." I stream internet radio all day so I should see a difference.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
Well, crap.

That (single replacement of libhtc_ril.so) did not turn out to be the fix - I had the "rild" segfault with the "apparent lost call followed by reconnect" again this evening (a couple minutes ago) - after having replaced the library with the Eris (2.1) version.

Back to the drawing board.

bftb0

[ Edit ] Now running Tazz 2.0 + CFS4 + replacement of /system/bin/rild and /system/lib/libhtc_ril.so with versions from Eris 17 July OTA ( == Leak-V3 in both cases ). Initial testing shows no obvious problems with voice/SMS/MMS/EVDO/voicemail/gmail/email/data. If this doesn't rectify the problem, I'm not sure what will.
[Droid Eris Q&A, Help & Troubleshooting] aandrsn:
Appreciate ya looking into this for us! Is your fix still kicking along?
[Droid Eris Q&A, Help & Troubleshooting] rick311:
EU1, let me know if you still need help doing some testing. i am willing, but i am only so savvy when it comes to this so the instructions need to be easy enough for a 5 year old to understand.
[Droid Eris Q&A, Help & Troubleshooting] theEastonator:
I have had this happen to me several times recently...running zen-EXP rev7...

-------------------------------------

Sent via the XDA Tapatalk App
[Droid Eris Q&A, Help & Troubleshooting] amfetamine:
I haven't had an undead call in a while now. Although I don't talk on the phone alot, 300-400 minutes a month at most. The last time I think I had one was on CELB 2.1 or 2.2. (Currently on 2.6)

I put 2.3 on my wife's phone the day it came out as her first root rom (and she's still using 2.3), and she hasn't complained of any call issues. She talks on the phone more than me:)

Just speculation, but feels like maybe there was a fix somewhere between CELB 2.1 and 2.3. Although not empirically tested.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
I haven't experienced the problem since I also replaced "rild" (a couple of days), but I really don't talk on my phone that much, so I'm not sure that proves anything.

Currently using Tazz2.0+CFS4+ replacement of /system/bin/rild and /system/lib/libhtc_ril.so with the versions from the HTC July 17 OTA (these files are identical to the corresponding files in Leak-V3).

bftb0
[Droid Eris Q&A, Help & Troubleshooting] SicNside:
Im using KaosFroyo v35-1 and no problems yet. But still in the past using theses froyo roms. I haven't had this problem
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
[ Edit ] - Deprecated as of 2010/09/20 2:50pm - see next post.

For anyone who wants to assist in testing the hypothesis that the problem is the use of the "rild" daemon built out of the CM5/CM6 trees, I have attached two flashable zip files for installation via Amon_RA recovery menus. Note that these are overlay flashes - no wiping of anything should be required.

The first, "Eris_rild_patch_v01.zip", makes a backup of whatever you have currently for

/system/bin/rild and

/system/lib/libhtc_ril.so

and then replaces those files with the versions from the HTC July 17 OTA (Android 2.1).

As a convenience, I also provided another (flashable) .zip, "uninstall_Eris_rild_patch_v01.zip". This merely uninstalls the "patch test" to whatever you were using before.

In principle, you don't even need to make a Nandroid backup to use these, (as I provided both an installer and a rollback flash) but I didn't test exhaustively, so it is probably a good idea to make a Nandroid anyway before starting out.

MD5 checksums:

5144c5bcb1324c04ab86e38c5d1dfc7b Eris_rild_patch_v01.zip
7b8d951627f3fbd35eaa5a2d1f6b4349 uninstall_Eris_rild_patch_v01.zip

bftb0
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
Well, that experiment lasted for 5 days - and ended in failure.

I am continuing to experience segfaults of the "rild" (Radio Interface Layer Daemon), even when using the version of "rild" (and the vendor library libhtc_ril.so) from the most recent HTC 2.1 ROMs (17 July 2010) OTA. (This is in conjunction with a Tazz 2.0 (Froyo) ROM and the CFS4 kernel).

These "rild" crashes are 100% correlated in time with the phenomenon of a "temporarily disconnected" voice call.

So, the problem - whatever it is - is something more subtle than just the coding of rild.

The stack traces of the crash look essentially identical in the cases that I have looked at:

libc.so:pthread_create()
libc.so:__thread_entry()
libhtc_ril.so:at_read_thread()
libhtc_ril.so:at_parse_notification()
libhtc_ril.so:at_notify_cdma_g23_data_entry()
libc.so:flcose() <- segfault here

Someone suggested (sorry, can't remember where), that setting

Settings -> Wireless & network settings -> Mobile network settings -> System select

to "Home Only" would change this behavior. I had it set to that value :(

I don't know if this means I am giving up - but chasing this experimentally seems to be getting progressively more subtle - and difficult.

bftb0
[Droid Eris Q&A, Help & Troubleshooting] jmomma1203:
I starting noticing this problem when I was running KaosFroyo v34. I flashed v35-1 the day it came out and just experienced my first "undead" call today. It's really frustrating because you think you're disconnected and then you're not. I really hope someone more tech savvy than myself figures this out for the rest of us!
[Droid Eris Q&A, Help & Troubleshooting] amfetamine:
I read thru the thread looking for mention of vm heap size. Would it have anything to do with the segfaults? I'm a layman here, but thought I'd throw the idea out there. For what it's worth, I haven't had an undead call in a while and mine is at 32mb.

I know people debate whether hi or low vm heap is faster than the other, but disregarding speed, is higher more stable? It feels that way.
[Droid Eris Q&A, Help & Troubleshooting] kzoodroid:
I've been running kaosfroyo v35-1 for a couple days and just had it happen to me today. Never happened before and I've been running kaosfroyo since v28. This was my first time doing a factory wipe before install just did dalvik wipes before. Maybe that had something to do with why I've never had it happen till now. Not really happy with the latest kaosfroyo and am thinking of reinstalling my backup of v34.
[Droid Eris Q&A, Help & Troubleshooting] AlanMAC1982:
This issue happens EVERY time I'm on a call, within the first minute of the call, it will drop, then about 3 seconds later it will come back. Service disconnects, this also happens when I get off the phone too. My SD card also removes itself and they are always getting corrupted (not using apps2sd). Froyo is disappointing me on the Eris. Going back to 2.1 official image.
[Droid Eris Q&A, Help & Troubleshooting] aandrsn:
My vm heap is maxed out, i still get it from time to time. On the kaosfroyo github, it said that it was a radio bug and to try to use the last hero radio release. Gonna give it a wack after some full battery and some md5 checking when i get home, but i thought i would throw that out there. Will let yall know in a few days... it is fairly rare for me, i had a 3g bug with the latest eris radio, and an older version took care of that, a bit apprehensive, i would rather have this bug than that one! Lol ... we shall see :)
[Droid Eris Q&A, Help & Troubleshooting] Stonent:
Just a couple of things:

OS: KaosFroyo V36

Radio: July release

Processor Speed: 710 (Are we all overclocking?)

Undead frequency: A few times a week

Circumstances: 30+ minute calls are almost guaranteed to have an undead call.

Other issues?

The other day I had a kernel panic. I turned on GPS via the widget, hit the voice search button issue a "navigate to blah blah" request. It gave me the confirmation dialog and when I tapped "OK" I was greeted by droids on skateboads. This is the first and only time I've had a panic. Probably completely unrelated since GPS and EVDO are completely different parts of the phone. But what the heck, I'll post it anyway.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
Seems very unlikely. A "segmentation fault" happens when a program tries to access a (data) address which is outside of it's virtual address range - basically, it is a programming logic error that allows this to happen. Management of VM address space is pretty trivial in linux (from the point of view of the running process) - processes never get a "haircut" while they are running. (The kernel may deny them access to new allocations of memory, but it never "steals memory away").

I don't have any new information about this - my efforts so far have failed.

I briefly considered creating a custom boot which would run the "rild" service underneath "strace", but sort of lost the gumption. ("strace" produces prodigious amounts of output, so that type of operation needs to take place for short periods of time - and I don't know how to manually trigger the bug).

For me it happens mostly on long calls. I don't think there is anything special about long calls, except for the fact that the cumulative probability of experiencing the bug increases with call length - the long you yak, the more likely it is that you will experience a rare call-related bug.

The fact that some CyanogenMod users experience it right away, or on every call, while others rarely (or never!) experience it suggests it is triggered by some "local" condition, such as a cell hand-off, fluctuating signal strength, available roaming networks, notification of SMS, etc.

I Googled around to try and figure out what "at_notify_cdma_g23_data_entry()" might be, but made no progress there.

If anyone thinks they have come up with a way where they can "force" the bug to occur somehow, that information could be very useful (for testing purposes).

bftb0
[Droid Eris Q&A, Help & Troubleshooting] skarletlightning:
I'm been having this problem as well. I don't use my phone for more than 150 minutes a month, but the times i'm on the phone for about 10+ minutes it will: drop the call (i can't hear them, they can't hear me; i double checked), it will then go to the home screen, then it will connect me again like nothing happened about 2 seconds later. It usually only happens once per call even if this call goes on for an hour or more. It is really annoying, but all the other great features are keeping me on Froyo.

OS: TazzFroyo V15 (also happened on previous iteration)

Circumstances: 30+ minute calls are almost guaranteed to have an undead call.

Is anyone working on a a fix?
[Droid Eris Q&A, Help & Troubleshooting] SicNside:
The only real fix is to flash the new sprint hero radio. Which has fixed the undead and dead calls plusses has increase my reception
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
I hope it is that simple, but I am reluctant to believe it. Nevertheless, I just flashed the 2.42.02.10.29 radio, and will see if I continue to observe the problem.

( MD5: f3621d901d340b9c9b4e0e560435dc9a heroc.2.42.02.10.29/radio.img )

My reluctance to believe that the problem is due to the radio firmware centers on two separate observations:

(1) prior radio firmware changes did not produce any behavior changes in AOSP/CM ROMs, and

(2) the problem does not occur with HTC 2.1 ROMs using any of the available radio firmwares that produce the problem with AOSP/CM ROMs.

But, I'm willing to give it a try. Look back here in a couple of weeks - I will supply an update if I see the problem crop up again. (I don't make lots of calls, so it will take a while before I would be confident that I haven't seen the bug pop up.)

bftb0
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
Bump! More testers needed!

SicNside might be on to something here.

I've used the new Sprint radio (2.42.02.10.29) for about 1 week now, and have yet to experience an undead call. I don't yak on the phone much, but I have had a couple of hour-long calls without an "undead" incident - that's a good sign.

More testing is needed - if you are willing to flash a radio, and especially if you have been experiencing this problem regularly, your feedback/testing would be helpful. It would be great if a radio flash puts this problem to bed for all Eris CM and AOSP ROMs.

bftb0

PS - If you need any further encouragement to flash a radio, I have noticed that when using this radio in all the typical places I go, it reports about 3 dBm better signal strength than what I had been observing with the July radio. (For those of you unfamiliar with dB units, a 3 dB improvement means twice the signal strength! Kind of hard to believe, but those are the numbers I've been seeing.)
[Droid Eris Q&A, Help & Troubleshooting] lotus22:
I'm on the newest radio and don't have any of the problems listed in this thread.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
Thanks.

What would be really valuable - because the problem is infrequent - is if someone who is experiencing the problem frequently, or even regularly - flashes the new (Sprint Hero CDMA 2.42.02.10.29) radio and then ceases to have the problem over a week or more of regular calling where they continue to use the phone in the same locations and with their typical call usage behaviors where the bug was observed.

There have been a few people that reported not experiencing the problem (on CM or AOSP ROMs) even using older radios; but that does not mean the problem doesn't exist - it might simply mean that the bug is triggered by a condition which is geographically dependent - for example, stuff like call handoff in an area served by multiple carriers within the handset's PRL. (There's a lot of complicated stuff going on under the hood of a cell radio)

I want to believe that the problem is solved - but until we get a report from somebody that consistently had the problem, and then rectified it immediately after flashing the new radio, I'm going to be a little skeptical. (In my own use, I probably have been experiencing only a couple undead calls per month - if no reports of that nature materialize, I will probably wait a couple of months to convince myself that this is a solution)

bftb0
[Droid Eris Q&A, Help & Troubleshooting] mjb413:
i'm running froyoshedyo v10. radio 2.42.02.10.29. i still have the "undead" call issue. it went away for a while, but within the past week (without any new flashes from me) it has returned.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
Arrrrrrrrgh.

(bangs head on desk.)

Well, at least I didn't let my hopes run away with the idea.