Cannot receive phonecalls.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install or run OpenEve GB
2. Call yourself from another phoneline.
3. Observe phone signal bars go down to zero.

What is the expected output? What do you see instead?
Being able to receive phonecall.

What version of the product are you using? On what operating system?
- System image for Gingerbread (CyanogenMod 7.0+OpenEtna froyo patch) ALPHA 
test version
- Boot/Kernel image for Gingerbread (linux 2.6.32.9 based) 2011/04/11 snapshot
- Clockwork Recovery image (CyanogenMod 7.0 version) snapshot (installed from)

Please provide any additional information below.
User from Canada, using Fido (Rogers) sim card and phone line.

I have attached a logcat dump. Hope this helps.

Original issue reported on code.google.com by turkmanz...@gmail.com on 10 Apr 2011 at 4:03

Attachments:

• phonecalls.txt

[GoogleCodeExporter]

I can confirm the same problem, also on Rogers (not Fido)
I had a similar logcat, though not as verbose... Sadly I don't have it anymore. 
 I think the relevant lines are 1-67, 69, 74 and 100.  If I get the chance, 
I'll slap it back on my phone and post my own logcat.

Original comment by grant.bo...@gmail.com on 10 Apr 2011 at 5:53

[GoogleCodeExporter]

I can also confirm the same problem on Rogers, but I do not have a logcat.

There is a logcat posted in the OpenEtna forum, at the following link:

http://forum.openetna.com/index.php?topic=1139.msg10715#msg10715

Original comment by rais...@gmail.com on 10 Apr 2011 at 6:29

[GoogleCodeExporter]

for Korean it works fine.

04-10 14:17:52.059: INFO/TelephonyRegistry(1383): notifyServiceState: 0 home 
olleh olleh 45008  UMTS...

this entry says that Olleh (KT telecom corp.) UMTS mode.

--------
attached logcat says

I/TelephonyRegistry( 1365): notifyServiceState: 0 home ROGERS Rogers Wireless 
302720  EDGE ...

it means ROGERS company and EDGE mode.

http://www.wisegeek.com/what-is-the-difference-between-umts-and-edge.htm
-----
I have searched with "EDGE + CyanogenMod" keywords and I got a relevant link

http://forum.cyanogenmod.com/topic/8753-gprsedge-disconnects/
-----
and...

You can try to change your APN provider

the settings -> wireless and network -> mobile networks ...

Original comment by wkp...@gmail.com on 10 Apr 2011 at 6:42

[GoogleCodeExporter]

I tried using the Testing menu:

*#*#4636#*#*
Phone information
Set preferred network type:

I was set to "WCDMA preferred"
I switched to "WCDMA only"

I called myself and my phone rang.
I tried to answer but it seems like my phone didn't actually do anything.
It shows one missed call.

I called myself again, but the problem is back.

I will try the other network types.

Original comment by rais...@gmail.com on 10 Apr 2011 at 6:55

[GoogleCodeExporter]

http://forum.cyanogenmod.com/topic/17379-cyanogen-7-rc1-rogers-3g-problem/

Original comment by wkp...@gmail.com on 10 Apr 2011 at 7:03

[GoogleCodeExporter]

Oh hey, you're right, I didn't realise I had posted that logcat before I closed 
it.  

Obviously it's nothing to do with EDGE because my logcat says UMTS, not EDGE:

I/TelephonyRegistry( 1376): notifyServiceState: 0 home ROGERS Rogers Wireless 
302720  UMTS ...

Plus, the fact that we can MAKE calls, but not RECEIVE them, and that sending 
and receiving text messages works, as does 3G data and HSPA data... that 
suggests you're on the wrong track.

Original comment by grant.bo...@gmail.com on 10 Apr 2011 at 7:49

[GoogleCodeExporter]

My phone crashed so I restarted it, then i changed the network type to "WCDMA 
only" again, and called myself again, and my phone rang the first time, but I 
couldn't answer.

The next times I called my phone, the problem was back.

Switching back and forth from "WCDMA preferred" to "WCDMA only" didn't help.

No dice with or without disabling data connection either.

I rebooted my phone and called myself in "WCDMA preferred" mode, same problem.

I changed the network type to "WCDMA only", still no success.

I don't know what made it almost work before.

Original comment by rais...@gmail.com on 10 Apr 2011 at 8:05

[GoogleCodeExporter]

The Phone information menu also showed UMTS on my phone as far as I remember 
during my testing of the network types.

Original comment by rais...@gmail.com on 10 Apr 2011 at 8:09

[GoogleCodeExporter]

Yeah, it'll only be EDGE when there's no UMTS reception in that particular spot.
This is the one issue that's keeping me from using this firmware that otherwise 
looks pretty awesome... 
wkpark, do you have any suggestions for how we can help track down the problem?

Original comment by grant.bo...@gmail.com on 10 Apr 2011 at 11:17

[GoogleCodeExporter]

Sorry, if I set it to "GSM only" it switches to EDGE.
It doesn't work if I switch to EDGE either though.

Original comment by rais...@gmail.com on 11 Apr 2011 at 12:19

[GoogleCodeExporter]

How about OpenEtna froyo 6.x series ?

is it works fine?
If so there must be some patch sets for this issue.

See also CyanogenModGingerBreadPatches

Original comment by wkp...@gmail.com on 11 Apr 2011 at 8:40

[GoogleCodeExporter]

I had to revert to OpenEtna because I need to be able to use my phone ;P
I haven't had problems receiving calls in OpenEtna.
I am using 6.3 RC7

Original comment by rais...@gmail.com on 11 Apr 2011 at 5:01

[GoogleCodeExporter]

yeah, exact same here.  OE 6.3-rc7 works perfectly on my phone (aside from the 
occasional stall that I haven't attributed to anything specific yet)
Yours is the only Gingerbread-based image I've tried, but it definitely works 
great in OE froyo

Original comment by grant.bo...@gmail.com on 11 Apr 2011 at 5:54

[GoogleCodeExporter]

I have the same issue as well unfortunately and I am also with Rogers. I do not 
have a logcat, but I am willing to install a fix or patch or flash a new 
firmware to test. 

Original comment by paulie...@gmail.com on 11 Apr 2011 at 7:08

[GoogleCodeExporter]

wkpark, please let us know if you've made any progress on this issue.

Original comment by rais...@gmail.com on 12 Apr 2011 at 1:02

[GoogleCodeExporter]

I have founed one releated patch set

https://github.com/OpenEtna/android_frameworks_base/commit/bc097e94dfd15ecaac4d0
57d30c68d9c77a54744

this is fixed framework.jar

 adb push framework.jar /system/framework/
 adb killall system_server (or reboot)

Original comment by wkp...@gmail.com on 12 Apr 2011 at 5:57

Attachments:

• framework.jar

[GoogleCodeExporter]

Hmmm... Well, it sounds like something like that would keep us from being able 
to *make* phone calls as well.  Plus, I was able to receive calls with OE 
versions both before and after that changeset, so I don't think it was done for 
Rogers people, for whom the phone had pretty much always worked.

I can't test this right now to confirm whether or not it fixes the problem; 
raisage, are you able to?

If not, here are some threads related to not being able to receive calls:

http://forum.openetna.com/index.php?topic=672  
This one sounds promising, but then the posts stop without any resolution, so I 
don't know what happened with it.  But I'm able to receive calls no problem on 
6.3-rc7, so whatever this problem was, it must have been different from ours, 
even though the symptoms sound exactly the same :(

http://forum.openetna.com/index.php?topic=773.msg7365#msg7365
Here's a post where someone mentions that they couldn't receive calls until 
they installed the Google apps.  I can't imagine why you'd need to have Google 
apps for incoming calls, especially when outgoing calls still work, but 
whatever the reason is for that, it could be related since the GB apps are a 
totally different version...

Original comment by grant.bo...@gmail.com on 12 Apr 2011 at 6:27

[GoogleCodeExporter]

Oops, never mind about what I said about the first one:  It says 6.2-rc1 and 
6.3-rc2, so maybe this IS the same problem and it was fixed after that.  I went 
straight from 6.1-rc5 to 6.3-rc7.

Original comment by grant.bo...@gmail.com on 12 Apr 2011 at 6:29

[GoogleCodeExporter]

It's back and forth today, I must have switched between OpenEtna and OpenEVE 4 
times already in 3 hours.

I'll get back to you soon with my results after replacing framework.jar

Original comment by rais...@gmail.com on 12 Apr 2011 at 6:45

[GoogleCodeExporter]

Holy balls, why?  That's so much downtime... It takes me a good hour to finish 
setting everything up every time I wipe my userdata

Original comment by grant.bo...@gmail.com on 12 Apr 2011 at 6:53

[GoogleCodeExporter]

Nope, still doesn't work, and some theme/UI aspects are messed up.
It's like a mix between OpenEtna and OpenEVE, or perhaps more accurately a mix 
between Froyo and Gingerbread.
The call answer buttons look like the OpenEtna versions cut off, but you have 
to rotate them like in OpenEVE.

Also there are a bunch of Force Closes of various processes, including System.

Original comment by rais...@gmail.com on 12 Apr 2011 at 7:03

[GoogleCodeExporter]

I haven't even been restoring my data, just switching between different CWM 
backups I've made, and customizing OpenEVE each time.

Original comment by rais...@gmail.com on 12 Apr 2011 at 7:04

[GoogleCodeExporter]

this is my selected logcat (with ddms)

In Korean, Incoming call works fine.

Original comment by wkp...@gmail.com on 12 Apr 2011 at 10:46

Attachments:

• incoming-call.txt

[GoogleCodeExporter]

So you don't get that big rild stack trace and whatever debug crap when you get 
a call that works, like all the failed logcats show...  

Original comment by grant.bo...@gmail.com on 12 Apr 2011 at 10:56

[GoogleCodeExporter]

sure. It works fine in Korea :)

Original comment by wkp...@gmail.com on 12 Apr 2011 at 11:01

[GoogleCodeExporter]

Could it be SIM card related?

Original comment by rais...@gmail.com on 13 Apr 2011 at 4:00

[GoogleCodeExporter]

Looks like droiduzr2 made some progress:
http://forum.openetna.com/index.php?topic=1160.0

Original comment by rais...@gmail.com on 13 Apr 2011 at 5:01

[GoogleCodeExporter]

still not working for me unfortunately. tried with N2K1's system image and 
wkparks boot and then with N2K1's boot & system images but same problem. My 
WiFi now works, but receiving calls is not working at all.

Original comment by paulie...@gmail.com on 13 Apr 2011 at 7:19

[GoogleCodeExporter]

Have you tried wiping the phone data via clockwork recovery and then installing 
the rom?

Original comment by savalent...@gmail.com on 13 Apr 2011 at 7:45

[GoogleCodeExporter]

Yes, no dice.

Original comment by rais...@gmail.com on 13 Apr 2011 at 7:47

[GoogleCodeExporter]

Unfortunately, droiduzr2's method didn't work for me either, and a few other 
people also had no luck with it.
Back to the drawing board...

Original comment by rais...@gmail.com on 13 Apr 2011 at 11:23

[GoogleCodeExporter]

There is an information I forgot to provide in this bug report.

I had updated to Rogers's official 1.6 update (which I believe is firmware 
v10q). Since I had lost fastboot access, I downgraded to firmware v10g using 
KDZ_FW_UPD and from there I simply installed an image of the LG Official 2.2 
firmware v20g in fastboot mode. That is what I was upgrading from when I 
installed OpenEve GB the first time.

I believe that my modem was still at whatever was provided by the 1.6 v10g 
modem driver. Correct me if that has nothing to do with the current problem.

I am now installing a v20d firmware (again using KDZ_FW_UPD to preserve 
fastboot access) since there was reports of success receiving calls with that 
version.

Once that's done, I'll try to reinstall OpenEve GB. Hopefully, this will yield 
some results.

Original comment by turkmanz...@gmail.com on 14 Apr 2011 at 5:10

[GoogleCodeExporter]

After playing around in the *#*#4636#*#* settings (namely changing the radio 
band to Automatic and the network preference to GSM only as I don't have a data 
plan only phone line), playing aroung with the wifi settings (turning on and 
off) I was able to receive one call (I was using Google Voice to call myself) 
but only once, the next times I tried, it didn't work (same problem as before 
and same kind of logcats).

I have attached the successful call logcat followed by an almost immediate 
second attempt that was a failure.

The logcat is is VERY verbose and I am sorry for that, but I didn't want to 
redact something in case it could be important in understanding what is 
happening.

Original comment by turkmanz...@gmail.com on 14 Apr 2011 at 6:32

Attachments:

• callSuccessAndFail.txt

[GoogleCodeExporter]

I think you are describing exactly what happens to me, however upon subsequent 
tests, I believe it has nothing to do with the network type you set.
I thought at first it had to do with changing the network type, but the pattern 
stays the same whether I do that or not.
What happens to me now is the first incoming call actually rings the phone, but 
I can't answer.
No subsequent incoming calls ring the phone.

Original comment by rais...@gmail.com on 14 Apr 2011 at 6:36

[GoogleCodeExporter]

turkmanz // thankyou for your logcat.

It shows "SIGSEGV" with rild (modem communication daemon)
...
I/DEBUG   ( 1276): pid: 1277, tid: 1350  >>> /system/bin/rild <<<
I/DEBUG   ( 1276): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 
00000009
...

I/TelephonyRegistry( 1370): notifyServiceState: 0 home ROGERS Rogers Wireless 
302720  EDGE
...

and you are using ROGERS, EDGE mode (not UMTS mode)

Original comment by wkp...@gmail.com on 14 Apr 2011 at 7:25

[GoogleCodeExporter]

by switching the phone to 2G mode, I'm able to get to voicemail (from another 
phone), but my phone still will not ring. I'm going to have to go back to an 
older release now though. its been 2 days on GB and although I love it (runs 
better than any version i've had on this phone so far), I do need to be able to 
receive incoming calls. If you need any testing done i'll gladly help out.

Original comment by paulie...@gmail.com on 14 Apr 2011 at 7:40

[GoogleCodeExporter]

I am having the same issue. I am on TMobile USA and I am getting only EDGE 
service because I think the LG GW620 is incompatible with the 3G freq. that 
Tmobile is using?! Can someone help resolve this issue. I am not able to make 
outgoing calls either.

Original comment by RealtorW...@gmail.com on 14 Apr 2011 at 8:16

[GoogleCodeExporter]

I have confirmed that droiduzr2's fix works for me.
For the issue of not being able to receive phone calls.

To recap, contact your mobile carrier, make sure to disable the Name Display 
feature of Call Display / Caller ID.

For more info:
http://forum.openetna.com/index.php?topic=1171.0

Original comment by rais...@gmail.com on 15 Apr 2011 at 4:01

[GoogleCodeExporter]

SIM card ARE a problem.
It has been proven.
http://forum.openetna.com/index.php?topic=1191.0

Also if you are using Rogers, have them TURN OFF the name display feature and 
you WILL be able to receive calls. Send me your email addy and I will provide 
you with my backup ROM of 2.3gb that WORKS on ROGERS.

Original comment by dwayne...@gmail.com on 18 Apr 2011 at 6:34

[GoogleCodeExporter]

I confirm that with roger, disabling 'name display' fix the problem. I just 
called an roger agent, and he was able to disable the option, leaving the 
callerid display.

Original comment by jean.sch...@gmail.com on 19 Apr 2011 at 3:54

[GoogleCodeExporter]

I don't have name display, but I still can't receive calls with rogers. I can 
make calls tho. 

Original comment by justfort...@gmail.com on 22 Apr 2011 at 1:29

[GoogleCodeExporter]

I am on TMObile USA and I neither can receive nor make calls. I switched back 
to my Froyo and waiting for someone to fix the Gingerbread version here. The 
Cyanogen mod has the following problems
1. bluetooth doesn't work at all.
2. FM radio is non functional
3. dialer takes a very long time to load.
BTW I have a LG GW620 with a LG KH5200 ROM Froyo.

Original comment by RealtorW...@gmail.com on 22 Apr 2011 at 1:37

[GoogleCodeExporter]

I changed the SIM card to the new one. still can't receive calls .... can 
anyone give me an advice?

Original comment by justfort...@gmail.com on 10 May 2011 at 12:31

[GoogleCodeExporter]

From what I can decipher - it has to do with the dialer app inside the system 
apps. I have similar problem with openetna bluetooth and fm radio. So the 
individual apps are not tested or someone with a different device than the LG 
EVE will compile their dialer with the package thus rendering it useless for 
the LG EVE. I think the openetna latest version is built from HTC magic and 
thus the bluetooth and FM radio are not working. Can anyone take the LG 
specific app from previous versions and package it with the Gingerbread system 
to make it all work nice?

Original comment by RealtorW...@gmail.com on 10 May 2011 at 3:28

[GoogleCodeExporter]

in Korea, phone call/receive is work perfectly.

----
Please try the lastest GB snapshot and bugreport again. I have no time to track 
all issues against all GB series.

----
why don't you try to attach your logcat ?

without logcat, this issue almost useless.

you can attach more verbose log like as following

 1. adb logcat -c (cleanup logcat)
 2. adb logcat -b radio -v time > radio.txt (logcat radio, with timestamp)
 3. test phone call/receive.
 4. ^C to exit adb logcat and attach the obtained "radio.txt"

Original comment by wkp...@gmail.com on 10 May 2011 at 3:45

• Changed state: NeedInfo

[GoogleCodeExporter]

Original comment by wkp...@gmail.com on 10 May 2011 at 3:52

• Added labels: Component-RIL

[GoogleCodeExporter]

@RealtorW // FM radio, Bluetooth works perfectly in my case from GB2.3.3 to 
GB2.3.4.

LG does not release their source code of FM radio/Bluetooth etc.
so, FMradio/bluetooth and OpenEtna/OpenEVE. are incompatible.
we can't make official FM radio work with GB.

Original comment by wkp...@gmail.com on 10 May 2011 at 1:36

[GoogleCodeExporter]

"LG does not release their source code of FM radio/Bluetooth etc.
so, FMradio/bluetooth and OpenEtna/OpenEVE. are incompatible.
we can't make official FM radio work with GB."

Very Bad News... :(

Original comment by iareh...@gmail.com on 10 May 2011 at 1:48

[GoogleCodeExporter]

but in my case FM radio works fine. bluetooth route it's sound correctly.

what don't you attach your logcat ?

feel free to feedback more intensively to this issue!

Original comment by wkp...@gmail.com on 10 May 2011 at 1:55

[GoogleCodeExporter]

I can't understand what FM radio app discussion is doing in this issue... The 
major problem i feel in FM Radio app is it can't be tuned to EVEN frequencies. 
i.e. you can't tune 100 but 99.9 or 100.1.@wkp Should I open a new Issue?

Original comment by iareh...@gmail.com on 10 May 2011 at 2:13