search

HopelessFantasy / openetna

Automatically exported from code.google.com/p/openetna
0 stars 0 forks source link

no calls or sms (2degrees New Zealand) #43

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

What version of the boot.img and system.img are you using?
bootv1.2 systemv4.1

Can you provide logcat output during that error?

Please provide any additional information below.

have tried all different settings in *#*#4636#*#* 
phones runs android 1.6 apps2sd+sshd images with no problem everything working 
fine

Original issue reported on code.google.com by nzfalcon...@gmail.com on 31 Jul 2010 at 4:48

GoogleCodeExporter commented 9 years ago 
Is it possible that this issue is related to the driver of Qualcomm?Just a 
guess,no evidence.

Original comment by walteron...@gmail.com on 24 Aug 2010 at 4:18

GoogleCodeExporter commented 9 years ago 
I think it's same as issues 79 : Call and sms problem with operator SFR 
(france)

Original comment by cyril.po...@gmail.com on 24 Aug 2010 at 6:05

GoogleCodeExporter commented 9 years ago 
Having network identification errors in the radio log (by lrsscl and 
walteronly1) doesn't sound very promising:

E/GSM     ( 1259): Wrong network type: 0
E/GSM     ( 1259): Wrong network type: 0
D/GSM     ( 1259): Poll ServiceState done:  oldSS=[3 home null null null  
Unknown CSS not supported -1 -1RoamInd: -1DefRoamInd: -1] newSS=[1 home     
Unknown CSS not supported -1 -1RoamInd: -1DefRoamInd: -1] oldGprs=1 newGprs=1 
oldType=unknown newType=unknown
W/GSM     ( 1259): countryCodeForMcc 
errorjava.lang.StringIndexOutOfBoundsException

There is also the odd line like this:
D/RILJ    ( 1259): [0018]< SIM_IO error: 
com.android.internal.telephony.CommandException: GENERIC_FAILURE

I'll have a look tonight if I have something similar. I've got working SMS, 
data and incoming calls, just unable to place calls. How do I find the sim card 
capacity?

Original comment by h.n.erik...@gmail.com on 31 Aug 2010 at 4:04

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
My sim card capacity is written outside,just on the back side wothout a metal 
chip.
Mine is printed "128KB".Maybe yours is printed"128/64/32KB".
I attempted to ask the service to change a lower capacity sim card,but they 
only offer 128KB sim for 3G users.
If you have further progress but without a 128KB SIM card,I can test the boot 
image and post the logcat here.Thanks for your efforts!

Original comment by walteron...@gmail.com on 31 Aug 2010 at 4:45

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
As some posts show,a 64KB SIM card can save 250 contacts and 88 SMS.So Maybe a 
128KB SIM card can save 2 times.

Original comment by walteron...@gmail.com on 31 Aug 2010 at 4:59

GoogleCodeExporter commented 9 years ago 
thats right, a 128kb card can save up to 500 contacts

Original comment by cwhc...@gmail.com on 31 Aug 2010 at 5:03

GoogleCodeExporter commented 9 years ago 
There is no marking on my SIM that could be indicating any sort of capacity. My 
old SIM could store at least 200 numbers, and that one didn't work at all 
("please insert sim" type of error) with the GW620 so I got a replacement one 
that really ought to be higher or equal capacity, as it's 4 years newer.

I also get the "Unknown CSS not supported" in the radio log, before the phone 
has settled down and managed to connect to something. It then changes to

D/GSM     ( 1269): Poll ServiceState done:  oldSS=[0 roaming Telia Sweden 3G 
24005 (manual) UMTS CSS not supported -1 -1RoamInd: -1DefRoamInd: -1] newSS=[0 
roaming Telia Sweden 3G 24005 (manual) HSDPA CSS not supported -1 -1RoamInd: 
-1DefRoamInd: -1] oldGprs=0 newGprs=0 oldType=UMTS newType=HSDPA

Shouldn't be much of a problem there. I also have the SIM_IO error, though.

Original comment by h.n.erik...@gmail.com on 1 Sep 2010 at 6:02

GoogleCodeExporter commented 9 years ago 
I have the "Wrong network type: 0" and "W/GSM     ( 1251): countryCodeForMcc 
errorjava.lang.StringIndexOutOfBoundsException" and some SIM_IO errors in my 
(working) log, too, so that may or may not affect this issue.

For the sms issue:
Can you please dial *#*#4636#*#*  AKA  *#*#INFO#*#*, go to Phone Info, scroll 
down to the SMSC field and press "Refresh". Please post the text of the smsc 
field after that.
Then you can change that field to the SMS center number of your provider (if it 
does not match already) and press update. Try to send an sms after that.

Original comment by polyth...@gmail.com on 1 Sep 2010 at 10:11

GoogleCodeExporter commented 9 years ago 
And please do only use latin characters and sms with a length smaller then 30 
characters for testing purpose.

Original comment by polyth...@gmail.com on 1 Sep 2010 at 10:19

GoogleCodeExporter commented 9 years ago 
It said "+46707990001",145 (which is correct and after writing +46707990001 it 
said "update failed" and with "+46707990001" it was possible to send an sms, 
but pressing the refres button reverts it to "+46707990001",145

Original comment by h.n.erik...@gmail.com on 1 Sep 2010 at 11:20

GoogleCodeExporter commented 9 years ago 
@h.n.eriksson:
Let me recapture that.
So after writing "+46707990001" in the field and pressing update, it is 
possible to send sms for you. When you go then back there and press "refresh", 
it shows "+46707990001",145 in the field. Are you still able to send sms? Or 
does it stop working? Does it stop working after the first successful sms or 
after clicking "refresh"?

Can you give a logcat -b radio for updating the smsc, a logcat -b radio for 
sending an sms when it does work and and a logcat -b radio for sending an sms 
when it does not work?

(In your post 53, you said that you have no issues sending sms at all. So did 
you have issues before "update"ing the smsc?)

Original comment by polyth...@gmail.com on 1 Sep 2010 at 12:33

GoogleCodeExporter commented 9 years ago 
I can still send SMS. Just like before. Never had a problem with SMS, only 
outgoing calls. Have so far not been able to make the phone fail at sending an 
SMS. Might try out a different SIM tonight just to see how the phone reacts to 
it.

I honestly don't think the two issues (outbound calls and sms) are related. I 
have all the same symptoms of problems with outgoing calls described in this 
thread (hanging up directly or not able to hang up at all) but none of the SMS 
problems.

Original comment by h.n.erik...@gmail.com on 1 Sep 2010 at 12:48

GoogleCodeExporter commented 9 years ago 
For the call issue:
I have looked through the difference in your logs (not working) and my logs 
(working), but it is not so easy to spot the siginficant differences because of 
different sims and networks.

As we using the libril and libril-qc-1 from zacpods' korean-v10t image and 
since it works there, the difference is presumably anywhere in our framework. 
To make that difference clear, please do the following:
Switch the phone off, issue adb logcat -b radio > boot_plus_call_not_working, 
boot the phone, call someone. After the line has been established, stop logcat.

Flash zacpods 1.6 image, which is based on the korean-v10t image. Switch the 
phone off, issue adb logcat -b radio > boot_plus_call_working, boot the phone, 
call someone. After the line has been established, stop logcat.

Do everything as fast as possible to not make the log grow to big.
I then can diff the two logs and (hopefully) find the point at which we are 
doing something different.

I dont know if the sms issue is the same or not, maybe we will see.

Original comment by polyth...@gmail.com on 1 Sep 2010 at 3:24

GoogleCodeExporter commented 9 years ago 
Issue 79 has been merged into this issue.

Original comment by polyth...@gmail.com on 1 Sep 2010 at 3:29

GoogleCodeExporter commented 9 years ago 
@polytheus:
Here you go. 2 logcats:
boot_call_not_working from Eclair
boot_call_working from zacpod 1.6 image

I'm having the same issue with Rogers (canada).

Original comment by hussein....@gmail.com on 2 Sep 2010 at 1:13

Attachments:

GoogleCodeExporter commented 9 years ago 
Ok after going through a few logcats I noticed that there were a bunch of 
"obj=android.os.AsyncResult" errors.

Upons googling that, it turns out the nexus one is also having issues with 
their hsdpa.
They did some research which may apply to us. Looks like there were some issues 
with PDP. 

http://hideki.hclippr.com/2010/06/21/analysis-of-nexus-ones-3g-issue/

try googling "obj=android.os.AsyncResult"

I hope this helps.

Original comment by abatr...@gmail.com on 2 Sep 2010 at 6:18

GoogleCodeExporter commented 9 years ago 
Having the same issue on boot 1.6, system 4.3. Cannot make calls. Found the 
error described on this thread: 

D/RILJ    ( 1238): [0599]< DIAL error: 
com.android.internal.telephony.CommandException: GENERIC_FAILURE
D/GSM     ( 1238): GSMDataConnTrack handleMessage { what=14 when=1865022 
obj=android.os.AsyncResult@43e0d138 }

I have a 128 kb SIM card from Entel PCS Chile.

Original comment by mase...@gmail.com on 6 Sep 2010 at 10:45

Attachments:

GoogleCodeExporter commented 9 years ago 
More logs.
SAludos
LRSSCL

Original comment by lrs...@gmail.com on 8 Sep 2010 at 6:23

Attachments:

GoogleCodeExporter commented 9 years ago 
I try with this sim in chile.

1.- sim superchip - no dialing call
2.- sim superchip 2 - no dialing call
3.- sim super 3,5g - ok outgoing call   

Saludos
LRSSCL

Original comment by lrs...@gmail.com on 8 Sep 2010 at 10:06

GoogleCodeExporter commented 9 years ago 
lrsscl, i use Entel 3.5g Chile and all work, try install the system 4.3 with 
fastboot -w

Original comment by croxz3...@gmail.com on 8 Sep 2010 at 10:24

GoogleCodeExporter commented 9 years ago 
yes, only found with sim superchip 3,5g, the other not found.
Saludos
LRS

Original comment by lrs...@gmail.com on 8 Sep 2010 at 10:51

GoogleCodeExporter commented 9 years ago 
Sorry croxz3669 but fastboot -w no fix this problem.

Original comment by lrs...@gmail.com on 8 Sep 2010 at 10:58

GoogleCodeExporter commented 9 years ago 
OK buy a new sim  (superchip 3,5g) and found the rom.
Saludos
LRSSCl

Original comment by lrs...@gmail.com on 9 Sep 2010 at 2:17

GoogleCodeExporter commented 9 years ago 
RT lrsscl:
Is superchip 3.5g a 128KB SIM card or a 64KB SIM card?

Original comment by walteron...@gmail.com on 9 Sep 2010 at 3:37

GoogleCodeExporter commented 9 years ago 
I do not know.
Saludos
LRSSCL

Original comment by lrs...@gmail.com on 9 Sep 2010 at 4:37

GoogleCodeExporter commented 9 years ago 
The superchip 3.5G has, according to Entel, a capacity to store 250 contacts, 
just like the superchip 2 (128kb), so this must be a 128kb sim either.

Original comment by mase...@gmail.com on 9 Sep 2010 at 11:54

GoogleCodeExporter commented 9 years ago 
All superchip have the capacity to store 250 contacts and 20 sms, and only 
superchip 3.5g work with the rom. 

Saludos
LRSSCL

superchip 3.5 250 contacts 20 sms 
http://personas.entelpcs.cl/PortalPersonas/appmanager/entelpcs/personas?_nfpb=tr
ue&_pageLabel=P7000183771267113225652
superchip     250 contacts 20 sms
http://personas.entelpcs.cl/PortalPersonas/appmanager/entelpcs/personas?_nfpb=tr
ue&_pageLabel=P7000183771267113225652
superchip 2   250 contacts 20 sms 
http://personas.entelpcs.cl/PortalPersonas/appmanager/entelpcs/personas?_nfpb=tr
ue&_pageLabel=P7000283771267113290527

Original comment by lrs...@gmail.com on 10 Sep 2010 at 3:33

GoogleCodeExporter commented 9 years ago 
RT :
As some chinese operator say,a 128KB SIM card can store 4 contact books,each 
book can store 250 contacts,so a 128KB SIM card can store up to 1000 
contacts,and 50 SMS.
a 64kb SIM card can store 200 contacts,and 40 SMS,this matches some search 
results.
I guess the 3.5G/2 represents your network type.
According to this post(http://forums.techarena.in/portable-devices/1311560.htm) 
,
16KB 120 contacts,
32KB 200 contacts,
64KB 500 contacts.

Original comment by walteron...@gmail.com on 10 Sep 2010 at 4:11

GoogleCodeExporter commented 9 years ago 
with the latest 1.6 boot image and the 4.3 openetna sys. image. I cannot send 
sms. I receive sms with no issue. Also, I have no 3G network, only edge. I live 
in Ecuador, using Porta. Porta operates on the same GSM and HSPDA frequencies 
as At&t in the USA. 

Maybe the 3g problem is with the build prop?

Attached is the logcat output when trying to send an sms.

Original comment by Rune.Bra...@gmail.com on 12 Sep 2010 at 5:41

Attachments:

GoogleCodeExporter commented 9 years ago 
The system version shows Android 2.1 update1,according to the post link of 
abatrour,it seems that the droid SMS issue is also related with this version of 
system.

Original comment by walteron...@gmail.com on 13 Sep 2010 at 9:53

GoogleCodeExporter commented 9 years ago 
Please try copying the attached flex.xml to /system/etc/flex/flex.xml by
adb shell mkdir /system/etc/flex
adb shell chown root:root /system/etc/flex
adb shell chmod 777 /system/etc/flex
adb push flex.xml /system/etc/flex/flex.xml
adb shell chown root:root /system/etc/flex/flex.xml
adb shell chmod 777 /system/etc/flex/flex.xml
and reboot. Does this fix any of this issues here?

I found references to this file in the kernel, but it's more a guess.

Original comment by polyth...@gmail.com on 17 Sep 2010 at 11:48

Attachments:

GoogleCodeExporter commented 9 years ago 
I'm getting the feeling that those error are caused by different radio firmware.
There are quite some places in the kernel, which directly interface with the 
modem(=radio) and which interface seems to have changed.

Which was the last radio firmware that you flashed?
Radio firmware cannot be flashed by fastboot, but only by the LG update tool, 
so which firmware was the last one that you flashed by the LG update tool?

My last firmware was the Vodafone/Germany(=AVD2BB) V10E_05. And it is working 
for me.

Original comment by polyth...@gmail.com on 17 Sep 2010 at 12:08

GoogleCodeExporter commented 9 years ago 
Ahhhh, I opened up an issue #108, and I think this is the same one, Poly, you 
can merge or close issue 108.

I also have a New Zealand bought gw620F It comes unlocked and ready for TELECOM 
NZ.
And i am back in the states running the 1.6+4.3 and have no 3g... The reason 
anyone In nz is not getting sms or calls is because Telecom NZ is ONLY running 
the 850wcdma (3g) and no gsm... so if 3g raido is'nt working, no service....

and Poly, the last frimware I flashed was the one given in the WIKI , V10D_00

Hope all this helps, and looking forward to getting some 3g going

Original comment by Bear60009@gmail.com on 17 Sep 2010 at 12:32

GoogleCodeExporter commented 9 years ago 
You know, i was about to type "and reboot. Does this fix any of this issues 
here?" as a comment xD

well it sure didnt fix any of the issues, but i get the problem where i cant 
hang up (:

meddling around with it now

Original comment by cwhc...@gmail.com on 17 Sep 2010 at 1:45

GoogleCodeExporter commented 9 years ago 
http://www.yellow-teddy.de/Flex.ini i found this file..

Original comment by cwhc...@gmail.com on 17 Sep 2010 at 3:28

GoogleCodeExporter commented 9 years ago 
update: pushed flex.xml and settings.db from my country's rom to 
/system/etc/flex/flex.xml and /system/etc/flex/settings.db

i can't hang up calls now.

Original comment by cwhc...@gmail.com on 17 Sep 2010 at 3:55

GoogleCodeExporter commented 9 years ago 
nice! and for sms? working now?

Original comment by benten...@gmail.com on 17 Sep 2010 at 6:01

GoogleCodeExporter commented 9 years ago 
In my old 1.5 rom:

etc/flex/settings.db mostly contains default settings and email config (some 
78000 such values). It also contains some sort of settings for operators:

CREATE TABLE flexoperator(_id INTEGER PRIMARY KEY,operatorkey INTEGER,nation 
TEXT,operator TEXT,MCC TEXT,MNC TEXT,SPN TEXT);

The last value in the table in my settings.db:
INSERT INTO "flexoperator" VALUES(132,124,'Default','OPEN','0','0','Default');

This also matches the flex.xml on this open (not bought from any operator) 
phone:
<?xml version="1.0" encoding="utf-8"?>
<Flexinfo>
<Flexinfo   
        FLEX_COUNTRY_CODE="GB"
        FLEX_OPERATOR_CODE="OPEN"
        FLEX_MCC_CODE="0"
        FLEX_MNC_CODE="0"
        FLEX_SIMLOCK_ON="0"
        FLEX_MODEL_CODE="0" />
</Flexinfo>

Pushing them and rebooting does not help. I still cannot call out.

The original firmware on my phone (never updated except using fastboot) has 
these  build.prop values that I cannot really correlate to any .kdz firmware 
file:

ro.build.display.id=CUPCAKE.v10
ro.build.version.incremental=v10

ro.build.date=Thu Dec 31 14:26:57 IST 2009
ro.build.date.utc=1262249817

ro.build.fingerprint=OPEN/LG_EVE/EVE/EVE/:1.5/GB/31.122325.13:user/ota-rel-keys,
release-keys
gsm.version.baseband=AMSS6385

Original comment by h.n.erik...@gmail.com on 17 Sep 2010 at 8:53

GoogleCodeExporter commented 9 years ago 
just to clarify some questions here..

1. I did not manage to dial out even after pushing flex.xml.
2. The behaviour of my phone changed, though I still cannot make any calls
-   With flex.xml, my phone would not allow me to hang up calls even when it 
doesn't connect
-   Without flex.xml, my phone will drop the call immediately (no connection 
made)
-   With an improperly formatted version of flex.xml, the first behaviour is 
shown too.
3. I can send/receive smses even without pushing flex.xml

Original comment by cwhc...@gmail.com on 18 Sep 2010 at 3:21

GoogleCodeExporter commented 9 years ago 
Please try with the new system/boot. I have included all the patches from 
codeaurora regarding the telephony framework.
And please post the HW/Modem/Factory version, which can now be found under 
Settings->About Phone.

Original comment by polyth...@gmail.com on 18 Sep 2010 at 12:28

GoogleCodeExporter commented 9 years ago 
Nope. Doesnt work.

Factory Version: GW620AT-00-V10g-ESA-XX-JAN-06-2010
HW version: GW620_1_0
Modem Version: GW620-V10G

Original comment by cwhc...@gmail.com on 18 Sep 2010 at 1:46

GoogleCodeExporter commented 9 years ago 
Just for reference: I have
Factory: GW620AT-00-V10e-262-02-NOV-02-2009
HW: GW620_1_0
Modem: GW620-V10e
and everything is working fine for me.

Original comment by polyth...@gmail.com on 18 Sep 2010 at 1:52

GoogleCodeExporter commented 9 years ago 
Flashed with V10E_05-Vodafone.kdz
Not working.

Factory: GW620AT-00-V10e-KTF-KR-NOV02-2009
HW: GW620_1_0
Modem: GW620-V10e

Original comment by cwhc...@gmail.com on 18 Sep 2010 at 3:52

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
BOOT 1.7+SYSTEM 4.4:
Factory: GW620AT-00-V10g-EUY-XX-DEC-30-2009
HW: GW620_1_0
Modem: GW620-V10g
Baseband:unknown

Original comment by walteron...@gmail.com on 18 Sep 2010 at 4:32

GoogleCodeExporter commented 9 years ago 
http://code.google.com/p/vogue-android/issues/detail?id=11

a related issue.

Original comment by cwhc...@gmail.com on 18 Sep 2010 at 4:55

GoogleCodeExporter commented 9 years ago 
Just like walteronly1:

Modem version: GW620-V10g
Factory version: GW620AT-00-V10g-EUY-XX-DEC-30-2009
HW version: GW620_1_0

Original comment by h.n.erik...@gmail.com on 18 Sep 2010 at 5:19