Related
After successful repair of my device, including the new motherboard with live USB port, returned to my experiments. The 3G modem is seen, it registers in the network, shows the correct APN... but does not connect. "No connection to the Internet". In the ADB I can see that PPP connection goes up, but neither the default route nor resolv.conf are created:
Code:
/ # ls /dev/ttyHS*
/dev/ttyHS0 /dev/ttyHS1 /dev/ttyHS2 /dev/ttyHS3 /dev/ttyHS4
/ # ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:744 errors:0 dropped:0 overruns:0 frame:0
TX packets:744 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:54232 (52.9 KiB) TX bytes:54232 (52.9 KiB)
ppp1 Link encap:Point-to-Point Protocol
inet addr:10.195.192.232 P-t-P:10.64.64.65 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:52 (52.0 B) TX bytes:58 (58.0 B)
/ # ip route
10.64.64.65 dev ppp1 proto kernel scope link src 10.195.192.232
/ # ls -l /etc/resolv.conf
lrwxrwxrwx 1 1000 system 16 Jul 15 15:44 /etc/resolv.conf -> /tmp/resolv.conf
/ # ls /tmp
audiomixer.sock avshsocket powerd.sock
audiomixer_read.sock chap-secrets samba
audiomixer_write.sock inc
avos pap-secrets
/ #
Thus it looks like /etc/ppp/ip-up, or some its daughter scripts, is not executed as it should. Situation is the same for 4.0.7, 4.0.6, and even 3.2.80 - which definitely did work! And for any of the 4 operators available at my location.
If this were a software problem, it could be fixed by reflashing. If it were a hardware problem, then the modem would not connect at all. Any more ideas? Does anyone know where to look for logs, or how to enable PPP logging and debug?
iourine said:
After successful repair of my device, including the new motherboard with live USB port, returned to my experiments. The 3G modem is seen, it registers in the network, shows the correct APN... but does not connect. "No connection to the Internet". In the ADB I can see that PPP connection goes up, but neither the default route nor resolv.conf are created:
Code:
/ # ls /dev/ttyHS*
/dev/ttyHS0 /dev/ttyHS1 /dev/ttyHS2 /dev/ttyHS3 /dev/ttyHS4
/ # ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:744 errors:0 dropped:0 overruns:0 frame:0
TX packets:744 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:54232 (52.9 KiB) TX bytes:54232 (52.9 KiB)
ppp1 Link encap:Point-to-Point Protocol
inet addr:10.195.192.232 P-t-P:10.64.64.65 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:52 (52.0 B) TX bytes:58 (58.0 B)
/ # ip route
10.64.64.65 dev ppp1 proto kernel scope link src 10.195.192.232
/ # ls -l /etc/resolv.conf
lrwxrwxrwx 1 1000 system 16 Jul 15 15:44 /etc/resolv.conf -> /tmp/resolv.conf10.64.64.65 dev ppp1 proto kernel scope link src 10.195.192.232
/ # ls /tmp
audiomixer.sock avshsocket powerd.sock
audiomixer_read.sock chap-secrets samba
audiomixer_write.sock inc
avos pap-secrets
/ #
Thus it looks like /etc/ppp/ip-up, or some its daughter scripts, is not executed as it should. Situation is the same for 4.0.7, 4.0.6, and even 3.2.80 - which definitely did work! And for any of the 4 operators available at my location.
If this were a software problem, it could be fixed by reflashing. If it were a hardware problem, then the modem would not connect at all. Any more ideas? Does anyone know where to look for logs, or how to enable PPP logging and debug?
Click to expand...
Click to collapse
Hi.
It's looks like your route has not been set up properly, I faced this or something similar while playing around the Huawei Stuff, It turned out that the gateway property net.ppp1.gw needed to be set to the remote ip.
I'll power up my archos and have a look for you, It's completely drained at the minute so it takes a while to come back to life..
In the mean time you can add the following to /etc/ppp/peers/datakey
Code:
debug
dump
kdebug 8
this will give a more verbose output on the logcat, I also like to use logcat with the following switches ( basically outputting all logs )
Code:
-b system -b main -b radio -b events
If you're still running into problems I'll post my properties and an example logcat if you want
Hope that helps
Trev
Thnx trevd,
the fact is that there are at least 3 opertaions to be done: defaultroute, resolv.conf, and some system-wide flag stating "internet connection present". Thus I suspect the entire ip-up script is not executed; in my case it is simply missing. Please could you look
Code:
ls -la /etc/ppp
both with the 3G connection on and off. No need to hurry, I'm unlikely to continue in the nearest days.
iourine said:
Thnx trevd,
the fact is that there are at least 3 opertaions to be done: defaultroute, resolv.conf, and some system-wide flag stating "internet connection present". Thus I suspect the entire ip-up script is not executed; in my case it is simply missing. Please could you look
Code:
ls -la /etc/ppp
both with the 3G connection on and off. No need to hurry, I'm unlikely to continue in the nearest days.
Click to expand...
Click to collapse
Hi. The directory layout looks the same either way
Code:
lrwxrwxrwx 1 root root 17 Jun 15 10:00 chap-secrets -> /tmp/chap-secrets
-rwxr-xr-x 1 root root 535 May 21 09:41 init_pppd_datakey
-rwxr-xr-x 1 root root 375 May 21 09:41 ip-down-datakey
-rwxr-xr-x 1 root root 408 May 21 09:41 ip-up-datakey
-rwxr-xr-x 1 root root 5596 May 21 09:56 ip-up-vpn
lrwxrwxrwx 1 root root 16 Jun 15 10:00 pap-secrets -> /tmp/pap-secrets
drwxr-xr-x 2 root root 30 May 21 09:41 peers
lrwxrwxrwx 1 root root 13 Jun 15 10:00 ppp0.pid -> /tmp/ppp0.pid
-rwxr-xr-x 1 root root 345 May 21 09:41 write_secrets
Here is the contents of /system/etc/ppp/ip-up-datakey
Code:
#!/system/bin/sh
NAME=ppp1
/system/bin/log -t pppd "start ip up ip remote=$IPREMOTE dns1=$DNS1 dns2=$DNS2 gateway=$IPLOCAL"
/system/bin/log -t pppd "NAME = $NAME"
/system/bin/setprop "net.$NAME.remote-ip" "$IPREMOTE"
/system/bin/setprop "net.$NAME.dns1" "$DNS1"
/system/bin/setprop "net.$NAME.dns2" "$DNS2"
/system/bin/setprop "net.$NAME.local-ip" "$IPLOCAL"
/system/bin/setprop "ril.pppd.state" "up"
Here is a list of system property which are set when the 3G Dongle is connected
Code:
[gsm.current.phone-type]: [1]
[gsm.defaultpdpcontext.active]: [true]
[gsm.network.type]: [UMTS:3]
[gsm.operator.alpha]: [Orange]
[gsm.operator.iso-country]: [gb]
[gsm.operator.isroaming]: [true]
[gsm.operator.numeric]: [23433]
[gsm.sim.operator.alpha]: [T-Mobile]
[gsm.sim.operator.iso-country]: [gb]
[gsm.sim.operator.numeric]: [23430]
[gsm.sim.state]: [READY]
[gsm.version.baseband]: [S21B47S1XX-RIL: 0.11]
[gsm.version.ril-impl]: [android TCL-ril 0.8]
[init.svc.pppd_datakey]: [running]
[init.svc.ril-daemon]: [running]
[net.dns1]: [149.254.230.7]
[net.dns2]: [149.254.192.126]
[net.dns1]: [149.254.230.7]
[net.dns2]: [149.254.192.126]
[net.dnschange]: [1]
[net.hostname]: [android-0016DC6B5408]
[net.ppp1.dns1]: [149.254.230.7]
[net.ppp1.dns2]: [149.254.192.126]
[net.ppp1.local-ip]: [31.113.123.214]
[net.ppp1.remote-ip]: [10.64.64.65]
[ril.pppd.state]: [up]
[ril.pppd_tty]: [/dev/ttyHS4]
[ril.use_data]: [yes]
[rild.libargs]: [-d /dev/ttyHS3]
[rild.libpath]: [/system/lib/libtcl-ril.so]
Obviously the ip's and networks are going to be different, but I'm sure you already figured that
Thnx trevd,
/etc/ppp looks the same; the problem appeasr to be in another place. Logcat says that PPP session is being established, and then immediatеly dropped with the following diagnostics:
Code:
I/pppd ( 4236): local IP address 10.227.119.86
I/pppd ( 4236): remote IP address 10.64.64.65
I/pppd ( 4236): primary DNS address 217.118.66.243
I/pppd ( 4236): secondary DNS address 217.118.66.244
I/pppd ( 4241): start ip up ip remote=10.64.64.65 dns1=217.118.66.243 dns2=217.118.66.244 gateway=10.227.119.86
I/pppd ( 4242): NAME = ppp1
D/AT ( 4216): AT> AT+CGACT?
D/AT ( 4216): AT< +CGACT: 1,1
D/AT ( 4216): AT< +CGACT: 2,0
D/AT ( 4216): AT< +CGACT: 3,0
D/AT ( 4216): AT< OK
D/AT ( 4216): AT> AT+CGDCONT?
D/AT ( 4216): AT< +CGDCONT: 1,"IP","internet.beeline.ru","0.0.0.0",0,0
D/AT ( 4216): AT< +CGDCONT: 2,"IP","","0.0.0.0",0,0
D/AT ( 4216): AT< +CGDCONT: 3,"IP","","0.0.0.0",0,0
D/AT ( 4216): AT< OK
E/RIL ( 4216): ppp_exit_code is 0
E/RIL ( 4216): ppp_exit_code is 0
E/RIL ( 4216): ppp_exit_code is 0
W/RILJ ( 703): [0052]< SETUP_DATA_CALL exception, possible invalid RIL response
W/RILJ ( 703): java.lang.RuntimeException: RIL_REQUEST_SETUP_DATA_CALL response expecting 1 RIL_Data_Call_response_v5 got 3
W/RILJ ( 703): at com.android.internal.telephony.RIL.responseSetupDataCall(RIL.java:3150)
W/RILJ ( 703): at com.android.internal.telephony.RIL.processSolicited(RIL.java:2235)
W/RILJ ( 703): at com.android.internal.telephony.RIL.processResponse(RIL.java:2125)
W/RILJ ( 703): at com.android.internal.telephony.RIL.access$500(RIL.java:202)
W/RILJ ( 703): at com.android.internal.telephony.RIL$RILReceiver.run(RIL.java:580)
W/RILJ ( 703): at java.lang.Thread.run(Thread.java:856)
D/GSM ( 703): [GsmDC-1] DcActivatingState msg.what=EVENT_SETUP_DATA_CONNECTION_DONE
D/GSM ( 703): [GsmDC-1] onSetupConnectionCompleted failed, ar.exception=java.lang.RuntimeException: RIL_REQUEST_SETUP_DATA_CALL response expecting 1 RIL_Data_Call_response_v5 got 3 response=null
D/GSM ( 703): [GsmDC-1] DcActivatingState onSetupConnectionCompleted result=ERR_GetLastErrorFromRil SetupResult.mFailCause=NONE
D/RILJ ( 703): [0053]> LAST_DATA_CALL_FAIL_CAUSE
D/RIL ( 4216): onRequest: LAST_DATA_CALL_FAIL_CAUSE
E/RIL ( 4216): ppp_exit_code is 0
D/AT ( 4216): AT> AT+CDFC?
D/AT ( 4216): AT< +CDFC:
D/AT ( 4216): AT< OK
D/RILJ ( 703): [0053]< LAST_DATA_CALL_FAIL_CAUSE error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
D/GSM ( 703): [GsmDC-1] DcActivatingState msg.what=EVENT_GET_LAST_FAIL_DONE
D/GSM ( 703): [GsmDC-1] notifyConnectionCompleted at 1346266255724 cause=UNKNOWN
D/GSM ( 703): [GsmDC-1] clearSettings
D/GSM ( 703): [GsmDCT] handleMessage msg={ what=270336 when=-1ms arg1=-1 [email protected] }
D/GSM ( 703): [GsmDCT] isDataSetupCompleteOk return false, ar.result=UNKNOWN
D/GSM ( 703): [GsmDCT] onDataSetupComplete: error apn=internet.beeline.ru cause=UNKNOWN
D/GSM ( 703): [GsmDCT] onDataSetupComplete: WaitingApns.size=0 WaitingApnsPermFailureCountDown=1
D/GSM ( 703): [GsmDCT] onDataSetupComplete: Not all permanent failures, retry
D/GSM ( 703): [GsmDCT] notifyNoData: type=default
D/GSM ( 703): [ApnContext] setState: FAILED for type default, previous state:INITING
D/GSM ( 703): [GsmDCT] Schedule alarm for reconnect: activate failed. Scheduling next attempt for 5s
D/GSM ( 703): [GsmDCT] reconnectAfterFail: NOT Posting GPRS Unavailable notification -- likely transient error
then it loops.
Sometimes the session exists for a few seconds and then is dropped by LSP RST from the other end.
Still trying to understand if this is a software bug, or a modem hardware problem... the modem works on a regular PC, and the soft is brand new after reformat.
I doubt it's a hardware problem. You got a pretty clear error there in the logcat, "expecting 1 ril_v5 response, got 3", further corroborated by the three "ppp exited with 0" lines above. Mind posting your build.prop? I have a Huawei 3g stick, not an Archos 3g stick, so I have no idea how the connection is handled on the Archos 3G stick. Do you have a "datakey" file in etc/ppp/peers?
Sent from my Archos G9 running CM9
Yes, 3 times "ppp exited ..." is exacltly the point where something goes wrong.
Where is build.prop? Do I need root to find it? At the moment I deliberately have a brand fresh software installation, not rooted, to guarantee that everything is as provided by Archos.
etc/ppp/peers/datakey does exist but poses more questions... e.g. why "nodefaultroute"? is it the same in your case?
Actually the background is: the modem did work on my old Archos, then one day it stopped working (did not start on unblocking the screen) and the USB port turned out to be dead. It could equally be caused by h/w problem at either the modem or the port, and the other could also be damaged. Yet the modem still works on a regular PC. Now I have a new motherboard and try to run the modem on it.
iourine said:
Yes, 3 times "ppp exited ..." is exacltly the point where something goes wrong.
Where is build.prop? Do I need root to find it? At the moment I deliberately have a brand fresh software installation, not rooted, to guarantee that everything is as provided by Archos.
etc/ppp/peers/datakey does exist but poses more questions... e.g. why "nodefaultroute"? is it the same in your case?
Actually the background is: the modem did work on my old Archos, then one day it stopped working (did not start on unblocking the screen) and the USB port turned out to be dead. It could equally be caused by h/w problem at either the modem or the port, and the other could also be damaged. Yet the modem still works on a regular PC. Now I have a new motherboard and try to run the modem on it.
Click to expand...
Click to collapse
build.prop is in /system/. And yes, at least in CM9, the datakey peer is nodefaultroute... Does the datakey peer file end up with calling a chat script (should be the last line, something like "connect system/xbin/chat some_switches /system/etc/chatscripts/datakey"? If it does, check the contents of the chatscript...
As i said, im using CM9 with a Huawei modem, so i can only give some obvious pointers...
Hi omegaRED7
Good to hear the Huawei are still good, The Huawei Stuff uses the same method as the archos stock i.e init script call pppd which uses peers and call chat which if successfull calls ip-up. all of it being called from the RIL Library, Just change gprs and you've got the archos implementation. I think the peers scripts differ slightly but so do the RIL's.
EDIT
Oh yeah, the write_secrets part as well is different, but you already knew that :laugh:
@iourine
I'll post my datakey peers and chatscripts for you later on so you can compare, The error you're get is very strange Maybe the libtcl-ril is causing but I don't know.
EDIT: Below are the contents of my files, /etc/ppp/init_pppds_datakey , /etc/ppp/peers/datakey and /etc/chatscripts/datakey_start ; I don't there be any difference given the nature of the error, I suppose It'll be worth check that /system/bin/pppd is actual a binary file an not a script or something that starts pppd 3 times, also check the service definition for pppd_datakey which should be in /etc/init/init.<model>.rc e.g init.A101S.rc, this requires root to access and should look like this
Code:
service pppd_datakey /system/bin/logwrapper /system/etc/ppp/init_pppd_datakey
user root
group radio cache inet misc
disabled
oneshot
This service is started from within libtcl-ril.so and is the archos vendor ril used by the ril-daemon service.
As a test , using the root account
Code:
stop ril-daemon
start pppd_datakey
see if that bring up a connection
Code:
[B]cat /etc/ppp/peers/datakey[/B]
#!/system/bin/sh
# An unforunate wrapper script
# so that the exit code of pppd may be retrieved
# this is a workaround for issue #651747
#trap "/system/bin/sleep 1;exit 0" TERM
PPPD_PID=
PPPD_TTY=`/system/bin/getprop ril.pppd_tty`
/system/bin/setprop "net.datakey.ppp-exit" ""
/system/bin/log -t pppd "Starting pppd with tty [$PPPD_TTY]"
/system/bin/pppd $PPPD_TTY 115200 $* call datakey
PPPD_EXIT=$?
PPPD_PID=$!
/system/bin/log -t pppd "pppd exited with $PPPD_EXIT"
/system/bin/setprop "net.datakey.ppp-exit" "$PPPD_EXIT"
Code:
[B]cat /etc/ppp/peers/datakey[/B]
linkname datakey
mru 1280
mtu 1280
# dump
# debug
unit 1
# connection
# crtscts
connect-delay 3000
hide-password
nodetach
# peer parameters
# noauth
# most gprs phones don't reply to lcp echo
# lcp-echo-interval 0
# lcp-echo-failure 0
# dns, routing
ipcp-accept-remote
ipcp-accept-local
ipcp-max-failure 15
#defaultroute
nodefaultroute
#replacedefaultroute # not currently supported by our pppd
noipdefault
usepeerdns
# avoid compression
novj
novjccomp
noccp
nobsdcomp
nopcomp
noaccomp
# connect scripts
connect '/system/xbin/chat -v -t 3 -f /etc/chatscripts/datakey_start'
# disconnect '/system/xbin/chat -v -t 3 -f /etc/chatscripts/datakey_stop
Code:
[B]cat /etc/chatscripts/datakey_start[/B]
TIMEOUT 5
ECHO ON
ABORT BUSY
ABORT ERROR
ABORT 'NO CARRIER'
ABORT VOICE
ABORT 'NO DIALTONE'
ABORT 'NO DIAL TONE'
ABORT 'NO ANSWER'
ABORT DELAYED
TIMEOUT 12
'' ATD*99***1#
TIMEOUT 30
CONNECT ''
omegaRED7 said:
build.prop is in /system/. And yes, at least in CM9, the datakey peer is nodefaultroute... Does the datakey peer file end up with calling a chat script (should be the last line, something like "connect system/xbin/chat some_switches /system/etc/chatscripts/datakey"?
Click to expand...
Click to collapse
Here is my build.prop (original ICS 4.0.7), hardly it is very different from yours
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MR1
ro.build.display.id=MR1.20120529.141046
ro.build.version.incremental=20120529.141046
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Tue May 29 14:10:46 CEST 2012
ro.build.date.utc=1338293446
ro.build.type=user
ro.build.user=rd
ro.build.host=debian
ro.build.tags=release-keys
ro.product.brand=archos
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=archos
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap4
# ro.build.product is obsolete; use ro.product.device
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=G9A-user 4.0.3 MR1 20120529.141046 release-keys
ro.build.characteristics=nosdcard,tablet
ro.archos.hwswid=167
# end build properties
ro.kernel.android.checkjni=0
dalvik.vm.checkjni=false
dalvik.vm.verify-bytecode=false
persist.service.sv.enable=1
archos.tetherState=off
persist.archos.suspend=enabled
opencore.asmd=1
browser.tioptimization=true
connection.concurrent=10
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
wifi.interface=wlan0
com.ti.omap_enhancement=true
ro.opengles.version=131072
tv.hdmi.uicloning.enable=true
media.avos.enable-rtsp=true
media.avos.enable-scanner=true
persist.archos.firmware_name=firmware_archos_it4.aos
ro.archos.daos.product=gen9
ro.com.google.mcc_fallback=262
enable.3d.bypass=0
ro.crypto.state=unsupported
ro.board.tsp_has_calibration=true
ro.telephony.default_network=3
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.com.android.dataroaming=false
keyguard.no_require_sim=false
hwui.render_dirty_regions=false
drm.service.enabled=true
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.opengles.version=131072
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.0.3_r0
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Don't see anything special for 3G/ppp/dialup
The /etc/ppp/peers/datakey does exist and is exactly the same as quoted by trevd (except for the last line "# disconnect...." that obviously plays no role). So do /etc/ppp/init_pppd_datakey and /etc/chatscripts/datakey_start. But this is not the entire story... someone has to set up the APN, this is the only essential thing, isn't it? And indeed there is a long log of other AT commands (operator query, voice and data service query, etc.), fed to the modem by some other script - which one? And this script uses AT+ACT only, not ATD*99***1. Thus /etc/chatscripts/datakey_start is not actually run! Yet the modem goes online (probably automatically by setting an active content, this may be a feature of its firmware), otherwise LCP negotiation would never begin and IP addresses (correct and specific for the operator) would be never received.
/system/bin/pppd is really a binary file.
To try the tests that require root later...
Please could you get the complete logcat
Code:
logcat -b system -b main -b radio -b events *:V
from the modem plug-in till the successful connection (getting the IP addresses plus ~30 sec after that) and post it or send to my private mail (there will be a long dump).
Hey,
It could be that the connection is indeed established in the RIL itself, for example the huaweigeneric RIL includes commands to connect directly, of course it's a generic implementation, which in our case needs to be circumvented and the connection has to be established through pppd for the Huawei stuff...
Can you setup the APN? Can you force manual selection of the network operator? I really don't understand why, even if the connection is directly initiated by the RIL, it attempts 3 times, esp. since you're running a stock ROM....
Mind also posting the logcat part before the connection is established?
P.S. Trev I haven't forgotten, I'll PM you the changes in the libhuaweigeneric ril
Sent from my Archos G9 running CM9
iourine said:
/system/bin/pppd is really a binary file.
Click to expand...
Click to collapse
Ay, As expected, but always worth checking!
iourine said:
The /etc/ppp/peers/datakey does exist and is exactly the same as quoted by trevd (except for the last line "# disconnect...." that obviously plays no role). So do /etc/ppp/init_pppd_datakey and /etc/chatscripts/datakey_start. But this is not the entire story... someone has to set up the APN, this is the only essential thing, isn't it?
Click to expand...
Click to collapse
Yes and no, There a program in android called the SimToolkit which I believe manages a lot of that when a new sim card is inserted. You'll see I/STK on the logcat if that has been actioned. After that I think the vendor ril manages the APN setting although it cannot hurt to manually set the APN and also manually register on the network as this sometimes helps but that's doesn't seem to be the problem you're facing
iourine said:
And indeed there is a long log of other AT commands (operator query, voice and data service query, etc.), fed to the modem by some other script - which one? And this script uses AT+ACT only, not ATD*99***1. Thus /etc/chatscripts/datakey_start is not actually run! Yet the modem goes online (probably automatically by setting an active content, this may be a feature of its firmware), otherwise LCP negotiation would never begin and IP addresses (correct and specific for the operator) would be never received.
Click to expand...
Click to collapse
EDIT: You probably won't see ATD*99***1 on the logcat as /system/xbin/chat which calls datakey_start doesn't provide any logcat output as far as I'm aware, You can try remove the chat binary or the datakey_start script to confirm if it's needed although you'd need root and an ext4 image for that as I don't think squashfs can be mounted as r/w.
Archos Manage the full process through their USBKeyManager.apk, this switches the device to modem mode, sets the rild.libargs and rild.libpath to the correct values and starts the ril-daemon.
The rild daemon is a service wrapper for /system/bin/rild, this is Android's Radio Interface Layer native controller, Rild, when started looks for rild.libargs and rild.libpath if it has no parameters passed. The rild.libargs property is the tty device used for Control Flow ( /dev/ttyHS3.) The most important part of the jigsaw is the rild.libpath property, which is set to /system/lib/libtcl-rild.so, this is the library which initializes the modem and calls pppd via the pppd_datakey service.
The /system/lib/libtcl-rild.so has logcat symbols AT, GSM and RIL and is responsible for the "long log of other AT commands"
doing a "strings" on this library reveals a lot and does show reference to pppd_datakey service as well as numerous AT commands.
The /system/lib/libtcl-rild.so would be were the crux of the problem is, although To Be Honest i'm still at a loss as to why you get 3 pppd starting
Unfortunately I can't logcat for you right now as I'm in the middle of development on CM10. one thing you might want to try however is
Code:
adb shell watchprops &
adb shell logcat -b system -b main -b radio -b events *:V
This will show what system properties are being set in real time and mix the logcat to provide a context.
EDIT:
@omegaRED7 - Thanks - You got in while I was typing.... maybe should make my posts less verbose :laugh:
omegaRED7 said:
Can you setup the APN? Can you force manual selection of the network operator? I really don't understand why, even if the connection is directly initiated by the RIL, it attempts 3 times, esp. since you're running a stock ROM....
Mind also posting the logcat part before the connection is established?
Click to expand...
Click to collapse
Yes, there is corerct APN in the log. Yes, I can manually select the operator, but I also need to select the correct APN out of the two (internet service and MMS service ones). Another problem that may also be related: for one minor operator the APN is not selected automatically, and I cannot add it manually via the regular interface. I fill all the necessary fields, but this is not saved. Yet it did work in the past!
Attached is my logcat from modem plug-in till looping.
iourine said:
Yes, there is corerct APN in the log. Yes, I can manually select the operator, but I also need to select the correct APN out of the two (internet service and MMS service ones). Another problem that may also be related: for one minor operator the APN is not selected automatically, and I cannot add it manually via the regular interface. I fill all the necessary fields, but this is not saved. Yet it did work in the past!
Attached is my logcat from modem plug-in till looping.
Click to expand...
Click to collapse
Hi
After looking that logcat I'd put that down to an issue with the libril-tcl, I've never seen that before and i've had multiple COPS entries on my simcard/modem albeit different carriers but still.
I think that leaves only one option, Report the "bug" to archos and wait .................... Only Joking, :laugh: this is Xda, we're not going to do that.
Got a couple of options from what I can see,
1.Remove the extra operators of the modem using minicom or similar
2.Hack the init_pppd_datakey script to check if pppd already running and exit if it is.
3. Try a different ril implementation. after all you only need to make a datacall and all the ril does in reality is initialize the modem and call out to pppd, even if you have to compile on yourself it shouldn't take much.
I would check calling the pppd_datakey service on it's own, like I suggested, it will definetly rule it out. and have a google to see if anyone has anything similar with the modem, doesn't even have to be with android.
I could be way off the mark with all this but It's just how I'd tackle it .
One "strange" thing on that logcat. I was surprised by the ril version being a v5, i'll double check that on mine.
Tried all the debug recommended above; not much help. PPP connection is established, ip-up-datakey appears to be run without errors, IP properties appear to be set. And then pppd exits immediately.
Tried running the connection manually. It is established, the interface named ppp1 is created, yet no routes and no resolv.conf are set.
Attached is my log with a couple of loops.
omegaRED7, there are multiple revisions of hardware sold under the same name "Archos 3G modem", with different PID/VIDs, from different vendors - not to speak about other 3G products. Surely it is not an easy thing to manage all this zoo. Surely Archos programmers could set a bug for a particular model at some point. Yet 3.80 software does not work too - and it did!
Hi,
I've been using cyanogenmod in my p880 for a while now and it worked pretty well until last weekend when it started loosing radio (gsm) signal.
After a while I noticed that when I was home, connected to wifi, it didn't occur.
Testing a little bit I found out that the problem was in the 3g. If I set the phone to use only 2g it works, but when I switch to 3g it looses the radio signal after a minute and does not work again until reboot.
The phone gets hot and the battery consumption increases a lot. In the battery status it shows that the "Phone" app's cpu time in "real time", like 100% usage, even with no calls at all..
I'm currently using nightly builds of CM 11, but I flashed the stable CM10 (with factory reset, data wipe) and the problem persisted. Then I flashed the latest nightly again, after another reset/wipe.
To use logcat I turned on the phone using only 2g, started logcat and when switched to 3g. The complete log can be found here:
https://drive.google.com/file/d/0B29xKdkT5wYzZmhleFZlcUhYc28/edit?usp=sharing
It was the first time I saw a logcat file, so I'm not sure, but I found some relevant things:
05-19 17:34:28.263 D/MobileDataStateTracker( 531): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
05-19 17:34:28.263 D/MobileDataStateTracker( 531): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
05-19 17:34:28.273 E/MobileDataStateTracker( 531): default: unknown network type: 0
05-19 17:34:28.313 E/ConnectivityService( 531): net.tcp.usercfg.default not found in system properties. Using defaults
05-19 17:34:28.313 E/ConnectivityService( 531): net.tcp.delack.default not found in system properties. Using defaults
05-19 17:34:28.323 D/MobileDataStateTracker( 531): supl: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=supl
05-19 17:34:28.323 D/MobileDataStateTracker( 531): supl: Received state=DISCONNECTED, old=DISCONNECTED, reason=radioTurnedOff
I hope someone can help me so I can use 3g again...
Thanks
check the settings for your apn
try with another kernel
Does this happen with absolutely no apps installed? (i.e fresh install?)
So I am not alone
hsafenix said:
Hi,
I've been using cyanogenmod in my p880 for a while now and it worked pretty well until last weekend when it started loosing radio (gsm) signal.
After a while I noticed that when I was home, connected to wifi, it didn't occur.
Testing a little bit I found out that the problem was in the 3g. If I set the phone to use only 2g it works, but when I switch to 3g it looses the radio signal after a minute and does not work again until reboot.
The phone gets hot and the battery consumption increases a lot. In the battery status it shows that the "Phone" app's cpu time in "real time", like 100% usage, even with no calls at all..
I'm currently using nightly builds of CM 11, but I flashed the stable CM10 (with factory reset, data wipe) and the problem persisted. Then I flashed the latest nightly again, after another reset/wipe.
To use logcat I turned on the phone using only 2g, started logcat and when switched to 3g. The complete log can be found here:
https://drive.google.com/file/d/0B29xKdkT5wYzZmhleFZlcUhYc28/edit?usp=sharing
It was the first time I saw a logcat file, so I'm not sure, but I found some relevant things:
05-19 17:34:28.263 D/MobileDataStateTracker( 531): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
05-19 17:34:28.263 D/MobileDataStateTracker( 531): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
05-19 17:34:28.273 E/MobileDataStateTracker( 531): default: unknown network type: 0
05-19 17:34:28.313 E/ConnectivityService( 531): net.tcp.usercfg.default not found in system properties. Using defaults
05-19 17:34:28.313 E/ConnectivityService( 531): net.tcp.delack.default not found in system properties. Using defaults
05-19 17:34:28.323 D/MobileDataStateTracker( 531): supl: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=supl
05-19 17:34:28.323 D/MobileDataStateTracker( 531): supl: Received state=DISCONNECTED, old=DISCONNECTED, reason=radioTurnedOff
I hope someone can help me so I can use 3g again...
Thanks
Click to expand...
Click to collapse
+1 here
I believe that it all started around 0427 Nightly, not sure, though.
I thought of switching to 2g network only yesterday after reading an old post in CM forums.
Did not have time to pull a logcat, yet, thanks for sharing! Hope somebody will figure out what the problem can be...
Rudjgaard said:
check the settings for your apn
try with another kernel
Does this happen with absolutely no apps installed? (i.e fresh install?)
Click to expand...
Click to collapse
My settings are as per wind IT specifications, but I noticed that in CM settings there is much more than specified by Wind, such as apn protocol, apn roaming protocol and bearer, which values are unknown to me. Will investigate on those values.
Tried also with official CM11 stock kernel, with no success.
No, I did not try with no apps installed, I will keep this test as the very last resort. I did not install new apps since when the problem started.
Inviato dal mio GT-P3110 utilizzando Tapatalk
Rudjgaard said:
check the settings for your apn
try with another kernel
Does this happen with absolutely no apps installed? (i.e fresh install?)
Click to expand...
Click to collapse
I checked the apn settings and they are ok..
It happened with a fresh install as well, when I fleshed CM10.
I didn't try another kernel yet, but Ottonet did and it did not solve the problem
SignalStrength: Hotfix TD-SCDMA
There could be some interesting news for those like me who are affected by network losses when in 3G.
One of the commits that will be compiled in tomorrow nightly amends misbehaviours in Android/telephony/SignalStrength.java
This is "Take 2".
https://github.com/CyanogenMod/andr...mmit/94186f84815c8f179ebee6b1d07b086fd06af489
The first attempt was made (so far as I was able to reconstruct) on April 28th, see here
https://gitorious.org/cyandreamproj...mmit/cbd9cf1fa383ea588a5a445306534c01f8aa1ca8
I believe I've had 3g issues since the end of april.
Now, I'm not android developer at all, and I would not like to arise too much xpectations or to get overexcited about something that has nothing to do with network losses when in 3g, so I would really appreciate if somebody more skilled than me would provide some comment/explanations.
[EDIT] it turned out that it was *today's nightly*, so, if there is some improvement, it can be enjoyed right away.
Downloading...
[EDIT 05232014] No joy. Whataver it did that fix, it did not solve the network loss issue.
Ottonet said:
There could be some interesting news for those like me who are affected by network losses when in 3G.
One of the commits that will be compiled in tomorrow nightly amends misbehaviours in Android/telephony/SignalStrength.java
This is "Take 2".
https://github.com/CyanogenMod/andr...mmit/94186f84815c8f179ebee6b1d07b086fd06af489
The first attempt was made (so far as I was able to reconstruct) on April 28th, see here
https://gitorious.org/cyandreamproj...mmit/cbd9cf1fa383ea588a5a445306534c01f8aa1ca8
I believe I've had 3g issues since the end of april.
Now, I'm not android developer at all, and I would not like to arise too much xpectations or to get overexcited about something that has nothing to do with network losses when in 3g, so I would really appreciate if somebody more skilled than me would provide some comment/explanations.
[EDIT] it turned out that it was *today's nightly*, so, if there is some improvement, it can be enjoyed right away.
Downloading...
[EDIT 05232014] No joy. Whataver it did that fix, it did not solve the network loss issue.
Click to expand...
Click to collapse
Just confirming, I also installed the last nightly (05-24) and the problem persists.
Does anyone think it could be a hardware problem?
hsafenix said:
Does anyone think it could be a hardware problem?
Click to expand...
Click to collapse
Hi..the problem still persists (I'm on Wind). I've always used Vanir, now I switched to official Cyanogen Nightly...still nothing happens
Hi. I had cellular network problems (no signal) in omni ROM and cm official too. Anyone tryed changing base band? I have v20a EUR ... Anyone tryed different?
Inviato dal mio LG-P880 utilizzando Tapatalk
I'm posting some modem.log , hoping it's not against forum rules (can remove if it is)
06-12 15:28:24.105 D/GsmDCT ( 896): overall state is CONNECTED
06-12 15:28:24.105 D/GsmDCT ( 896): startDataStallAlarm: tag=61578 delay=60s
06-12 15:30:00.745 D/use-Rlog/RLOG-RILC( 151): rild: grabPartialWakeLock, s_wakeup_lock_flag - 0
06-12 15:30:00.745 D/use-Rlog/RLOG-RILC( 151): rild: wakelock acquired
06-12 15:30:00.745 D/use-Rlog/RLOG-RILC( 151): [UNSL]< _LGE_RESTART_RILD {AT Command Timeout}
06-12 15:30:00.745 D/use-Rlog/RLOG-AT( 151): dlc[12] atchannel: at_send_command_full() end; err:-4
06-12 15:30:00.745 D/use-Rlog/RLOG-RILC( 151): [1666]< DATA_CALL_LIST fails by E_REQ_TIMEOUT
06-12 15:30:00.745 D/use-Rlog/RLOG-RIL( 151): dlc[12] lge-ril: requestInterface(DATA_CALL_LIST) invoking *requestFunction(req:57, data: 0x00000000, len:0)...DONE
06-12 15:30:00.745 D/use-Rlog/RLOG-RIL( 151): dlc[12]: lge-ril - requestInterface: Exiting DLC handler, thread - 1074013352. s_dlc_handler_create_tracker - 0x301ff
06-12 15:30:00.755 D/RILJ ( 896): *********RILJ: LgeRestartRild Start
06-12 15:30:00.755 D/RILJ ( 896): ### Show RIL Recovery popup ###
06-12 15:30:00.825 E/RILJ ( 896): Uncaught exception read length=52Exception:java.lang.NullPointerException
06-12 15:30:00.825 I/RILJ ( 896): Disconnected from 'rild' socket
06-12 15:30:00.825 D/PHONE ( 896): [ServiceState] setNullState=1
06-12 15:30:00.825 D/GsmSST ( 896): [GsmSST] Poll ServiceState done: oldSS=[0 0 home I WIND I WIND 22288 UMTS UMTS CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] newSS=[1 1 home null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] oldMaxDataCalls=1 mNewMaxDataCalls=1 oldReasonDataDenied=-1 mNewReasonDataDenied=-1
06-12 15:30:00.825 D/GsmSST ( 896): [GsmSST] RAT switched UMTS -> Unknown at cell -1
06-12 15:30:00.825 D/PHONE ( 896): [ServiceState] setNullState=1
06-12 15:30:00.825 D/PhoneProxy( 896): [PhoneProxy] updatePhoneObject: radioTechnology=0
06-12 15:30:00.825 E/use-Rlog/RLOG-RILC( 151): error on reading command socket errno:104
06-12 15:30:00.825 D/GsmSST ( 896): [GsmSST] Iwlan feature available = false
06-12 15:30:00.825 D/RilRequest( 896): [5314]< DATA_CALL_LIST error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE ret=null
06-12 15:30:00.835 I/use-Rlog/RLOG-RILC( 151): libril: new connection
06-12 15:30:00.835 D/use-Rlog/RLOG-RILC( 151): rild: grabPartialWakeLock, s_wakeup_lock_flag - 1
06-12 15:30:00.835 D/use-Rlog/RLOG-RILC( 151): [UNSL]< UNSOL_RIL_CONNECTED {7}
06-12 15:30:00.835 D/use-Rlog/RLOG-RILC( 151): rild: grabPartialWakeLock, s_wakeup_lock_flag - 1
06-12 15:30:00.835 D/use-Rlog/RLOG-RILC( 151): [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED {RADIO_SIM_READY}
06-12 15:30:00.835 I/use-Rlog/RLOG-RILC( 151): RIL Daemon version: android lge-ril 1.0
06-12 15:30:00.835 I/RILJ ( 896): Connected to 'rild' socket
06-12 15:30:00.865 D/GsmSST ( 896): [GsmSST] updateSpnDisplay: radio is on but out of service, set plmn='Nessun servizio.'
06-12 15:30:00.865 D/RILJ ( 896): [UNSL]< UNSOL_RIL_CONNECTED {7}
06-12 15:30:00.865 D/RILJ ( 896): [0213]> RADIO_POWER off
06-12 15:30:00.865 D/GsmSST ( 896): [GsmSST] updateSpnDisplay: changed sending intent rule=2 showPlmn='true' plmn='Nessun servizio.' showSpn='false' spn=''
06-12 15:30:00.885 D/RILJ ( 896): [0214]> REQUEST_SET_PREFERRED_NETWORK_TYPE : 0
06-12 15:30:00.885 D/use-Rlog/RLOG-RILC( 151): [1363036565]> RADIO_POWER (0)
06-12 15:30:00.885 D/use-Rlog/RLOG-RILC( 151): [1363036565]< RADIO_POWER fails by E_RAIDO_NOT_AVAILABLE
Inviato dal mio LG-P880 utilizzando Tapatalk
I have additionally extreme battery consumption.
I have this problem too.
With Resurrection Remix (CM 11 based) and Wind IT....
complete logs
Happened today, gathered all the logs i could. Kernel dmesg, modem log And main log.
All with official CM11 from 17/06. But it's the same on other cm11 based.
Time is:
<4>[14:06:18 18:49:45.571] ##@acm_read_bulk !ACM_READY
<4>[14:06:18 18:49:45.581] **************************
<4>[14:06:18 18:49:45.581] !!!!! ts_ldisc_close !!!!!
<4>[14:06:18 18:49:45.581] **************************
<4>[14:06:18 18:49:45.581] ### CP Crash : 1, USB DISCONNECT : 0 ###
I have the same problem as well, it started around 2 - 3 weeks ago, I was on beanstalk 4.4.2, a build from march, if I remember correctly. I had no issues before, but suddenly I lost signal every time on 3G. I tried several Roms with and without the RIL-Patch by Flying_Bear, but nothing helped so far. The only "workaround" is to stay on 2G. I'm starting to get tired of constantly reflashing my phone to try other Roms.
Its strange, that the same error occurred around the same time for so many people. I would like to know if it also happens on stock, or if its a special hardware-revision that fails. My phone version is SWS-Black (Swiss market, but bought in Germany).
It looks like something in the connection behavior got changed. When using earlier nightlies you could observe the phone connecting via HSPA+ (H+) everytime it was possible. But in later builds the phone only connects via HSPA+ if you actively use mobile data and changes back the connection to HSDPA (H) afterwards, thus resulting in constant changes between those network types. I believe this change was included to save battery but it really doesn't if your phone constantly loses connection and you have to reboot. Maybe this change was a global one but as you can see our phone can't handle it. Hopefully demetris can either identify that change and revert it or fix it.
@rob3110 , i understand your frustration, i'm changing ROM too. I also did try EPRJ RIL without success. Now I'm experimenting a RIL from CM 10.2. It seems no Dev is looking into it, it's a pity. I'm trying to analyze error logs but I'm no real Dev... You can post your logs if you like
Inviato dal mio LG-P880 utilizzando Tapatalk
Right now I'm trying the strange bug-fix JustChris20 posted in the EPJR-RIL-fix thread:
http://forum.xda-developers.com/showpost.php?p=53015495&postcount=105
1. install your rom of your choice.
don't modify anything, no ril, nothing...
2. shutdown your system and remove your battery. Now press the power button for 30 seconds. Wait further one minute. Now insert your battery back and start handy. enjoy your network... ?
Click to expand...
Click to collapse
(But without flashing a new Rom) So far I haven't lost connection for the last hours, but it is to early to be certain. I'll have to test it for at least some days or weeks to know, if it helped permanently. Maybe it helps others as well.
Just for interest, what carriers are those on with this error, or what countries are they from? Does it only happen in Europe (I'm from Germany)? If so, what happened, did something change with the hsdpa or hsdpa+ networks? Or does this error occur all over the world?
rob3110 said:
Right now I'm trying the strange bug-fix JustChris20 posted in the EPJR-RIL-fix thread:
http://forum.xda-developers.com/showpost.php?p=53015495&postcount=105
(But without flashing a new Rom) So far I haven't lost connection for the last hours, but it is to early to be certain. I'll have to test it for at least some days or weeks to know, if it helped permanently. Maybe it helps others as well.
Just for interest, what carriers are those on with this error, or what countries are they from? Does it only happen in Europe (I'm from Germany)? If so, what happened, did something change with the hsdpa or hsdpa+ networks? Or does this error occur all over the world?
Click to expand...
Click to collapse
I am having the same troubles and I am also from Germany (carrier: simyo).
I did follow your instructions and will report if it worked or not.
Edit: today I did have another disconnect, so unfortunately this rather easy "fix" didn't work out (at least for me).
Hopefully someone finds another sollution.
rootarded said:
I am having the same troubles and I am also from Germany (carrier: simyo).
I did follow your instructions and will report if it worked or not.
Edit: today I did have another disconnect, so unfortunately this rather easy "fix" didn't work out (at least for me).
Hopefully someone finds another sollution.
Click to expand...
Click to collapse
Yeah, didn't work for me either. I still get those disconnects on 3G. I will ask my carrier (E-Plus) if there was a recent change to the 3G-network that might have brought us this error, but I don't think they will give me a useful answer...
Hello people.
I'm using a custom rom for my S Advance (CM11 Janice based). But since last month my phone is randomly rebooting when I use WCDMA (3G Network). The phone works ok when I use 2G only (GSM).
After searching a lot, I found other users with the same issue (including the same build of the rom). Apparently my carrier (TIM, Brazil) and Movistar (Argentina) changed recently something on their WCDMA network, it causes to phone overheat. The proccess "m.android.phone" consumes CPU and the
Code:
adb locat
throws this odd error:
Code:
[...]
E/DataBuffer( 2570): Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: [email protected])
D/AndroidRuntime( 2655): Shutting down VM
W/dalvikvm( 2655): threadid=1: thread exiting with uncaught exception (group=0x41856ce0)
E/WifiManager( 2774): Channel connection lost
E/StrictMode( 2570): RemoteException handling StrictMode violation
E/StrictMode( 2570): android.os.DeadObjectException
E/StrictMode( 2570): at android.os.BinderProxy.transact(Native Method)
E/StrictMode( 2570): at android.app.ActivityManagerProxy.handleApplicationStrictModeViolation(ActivityManagerNative.java:3770)
E/StrictMode( 2570): at android.os.StrictMode$5.run(StrictMode.java:1408)
[...]
I contacted the rom developer (great guy, btw), but he says he could not do anything, because it's a problem with the carrier. I contacted the carrier and they didn't help so much (bunch of generic questions, take to tech support, blablabla)
Someone had the same problem? I tried so many configurations, build.prop editing, secret menu, etc,etc.... Is kinda annoying use only 2G.
- adb logcat 01: http://pastebin.com/FHGipHvk
- adb logcat 02: http://pastebin.com/ZnsKXmwE
- adb logcat 03: http://pastebin.com/A7tFVAw6
Thanks!
My son's Moto X with unofficial Lineage OS 13 has been working just fine until today, when it suddenly stopped finding any network operators. The SIM card is still recognized, I may enter the pin, but then it says "No service", and when I go to network operators choice, I find that not a single operator is displayed.
I tested the SIM in another phone, it seems to be fine. I also inserted different sim, which I know to work into this phone, but that did not help.
This is what I get from adb logcat, but I can't make sense of it:
XXXXXXXXXXX simSlotIndex=0 displayName=Willkommen carrierName=No service nameSource=0 iconTint=-16746133 dataRoaming=0 [email protected] mcc 26
2 mnc 7 mUserNwMode=9}]
01-07 18:11:59.254 1572 1572 D NetworkSettings: onSubscriptionsChanged: Slot matched SimSlotIndex: 0
01-07 18:11:59.257 1833 1833 D KP2AAF : OnAccEvent
01-07 18:11:59.306 1833 1833 D KP2AAF : OnAccEvent
01-07 18:11:59.306 1572 3902 D OpenGLRenderer: endAllStagingAnimators on 0x99f02e00 (RippleDrawable) with handle 0x9d070520
01-07 18:11:59.361 1833 1833 D KP2AAF : OnAccEvent
01-07 18:11:59.361 1833 1833 D KP2AAF : event: 32, package = com.android.phone
01-07 18:11:59.361 1833 1833 D KP2AAF : event package is no launcher
01-07 18:11:59.367 1833 1833 D KP2AAF : root package is no launcher
01-07 18:11:59.367 1833 1833 D KP2AAF : URL=androidapp://com.android.phone
01-07 18:11:59.368 1833 1833 D KP2AAF : Cancel notif
01-07 18:11:59.438 1881 6159 I GeofencerStateMachine: removeGeofences: removeRequest=RemoveGeofencingRequest[REMOVE_BY_IDS Ids=[atn_geofence_request_id], packageName=
com.google.android.apps.maps]
01-07 18:11:59.458 1881 1903 I GeofencerStateMachine: removeGeofences: removeRequest=RemoveGeofencingRequest[REMOVE_BY_IDS Ids=[atn_geofence_request_id], packageName=
com.google.android.apps.maps]
01-07 18:11:59.575 1572 1572 D NetworkQuery: unregistering callback class com.android.phone.NetworkSetting$3
01-07 18:11:59.579 1572 1572 I art : Starting a blocking GC Explicit
01-07 18:11:59.634 1572 1572 I art : Explicit concurrent mark sweep GC freed 29733(3MB) AllocSpace objects, 7(156KB) LOS objects, 40% free, 10MB/17MB, paused 610u
s total 41.233ms
01-07 18:11:59.656 1572 1572 I art : Starting a blocking GC Explicit
01-07 18:11:59.676 1572 1572 I art : Explicit concurrent mark sweep GC freed 13973(846KB) AllocSpace objects, 2(80KB) LOS objects, 39% free, 9MB/15MB, paused 640u
s total 19.563ms
01-07 18:11:59.676 1572 1572 I art : Starting a blocking GC Explicit
01-07 18:11:59.691 1881 1901 I GeofencerStateMachine: removeGeofences: removeRequest=RemoveGeofencingRequest[REMOVE_BY_IDS Ids=[atn_geofence_request_id], packageName=
com.google.android.apps.maps]
01-07 18:11:59.695 1572 1572 I art : Explicit concurrent mark sweep GC freed 3(96B) AllocSpace objects, 0(0B) LOS objects, 40% free, 9MB/15MB, paused 579us total
19.136ms
01-07 18:12:00.121 21030 21030 W ps : type=1400 audit(0.0:1428831): avc: denied { getattr } for path="/proc/1" dev="proc" ino=3578 scontext=u:r:untrusted_app:s0:c5
12,c768 tcontext=u:r:init:s0 tclass=dir permissive=0
01-07 18:12:00.145 1833 1833 D KP2AAF : OnAccEvent
01-07 18:12:00.145 1833 1833 D KP2AAF : event: 2048, package = com.android.systemui
01-07 18:12:00.145 1833 1833 D KP2AAF : return.
Could it be that suddenly the hardware has become faulty? Does anybody have suggestions how to test for the cause?
Thanks very much in advance!!!
Did a factory reset, which did not solve it. Still no network operators found.
Trying to understand the problem. logcat reveals that when it scans for networks, something goes wrong:
IsDataRoamingFromRegistration=false] newSS=[1 1 voice home data home null null null null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false IsDataRoamingFromRegistration=false] oldMaxDataCalls=20 mNewMaxDataCalls=20 oldReasonDataDenied=-1
Can someone enlighten me, what CSS stands for?
Now I spotted more errors:
01-10 15:54:50.960 2132 2132 D DCT : [0]stopNetStatPoll
01-10 15:54:50.964 2132 2132 D DCT : [0]overall state is IDLE
01-10 15:59:14.763 2132 2795 D RILJ : [4000]> RIL_REQUEST_GET_CELL_INFO_LIST [SUB0]
01-10 15:59:14.770 217 7538 W use-Rlog/RLOG-RILQ: (0/217):RIL[0][cmd-109(912)] qmi_ril_qmi_req_log: req QMI NAS, msg id: 67, e len:0
01-10 15:59:14.804 217 7538 W use-Rlog/RLOG-RILQ: (0/217):RIL[0][cmd-109(912)] qmi_ril_qmi_resp_log: rsp - QMI NAS, msg id: 67, e len:7
01-10 15:59:14.804 2132 2243 D RilRequest: [4000]< RIL_REQUEST_GET_CELL_INFO_LIST error: com.android.internal.telephony.CommandException: GENERIC_FAILURE ret=
01-10 15:59:14.804 2132 2132 D GsmSST : [GsmSST] EVENT_GET_CELL_INFO_LIST: error ret null, e=com.android.internal.telephony.CommandException: GENERIC_FAILURE
01-10 15:59:14.804 2132 2795 D GsmSST : [GsmSST] SST.getAllCellInfo(): X size=0 list=null
01-10 15:59:14.805 2132 2795 D GsmSST : [GsmSST] getCellLocation(): X empty mCellLoc and CellInfo mCellLoc=[-1,-1,-1]
01-10 15:59:14.817 1929 3007 D TelephonyManager: getCellLocation returning null because CellLocation is empty
01-10 15:59:14.820 2132 20809 D GsmSST : [GsmSST] SST.getAllCellInfo(): return last, back to back calls
01-10 15:59:14.820 2132 20809 D GsmSST : [GsmSST] SST.getAllCellInfo(): X size=0 list=null
This "Generic failure" sounds spooky to me. As if something about the hardware is broken.
yahya69 said:
Did a factory reset, which did not solve it. Still no network operators found.
Click to expand...
Click to collapse
Have you tried restoring to the stock firmware? If not, try the following commands in fastboot mode first:
Code:
fastboot erase modemst1
fastboot erase modemst2
Additionally, in the Phone app, you may dial *#*#INFO#*#* (*#*#4636#*#*) to obtain more information about the device's network.
VitaTaf said:
Have you tried restoring to the stock firmware?
Click to expand...
Click to collapse
Yes, but that also did not help, so I returned to LineageOS again.
If not, try the following commands in fastboot mode first:
Code:
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
I am not clear what that does. Seemingly, it erases two partitions. Is their content rebuilt after? Are those two partitions shipped with the custom rom? I did several google searches and each time I found it accompanied by the instruction to flash something else in the next step. So before nuking a partition I certainly would want to know., but so far I have not found an explanation of the partition layout.
Additionally, in the Phone app, you may dial *#*#INFO#*#* (*#*#4636#*#*) to obtain more information about the device's network.
Click to expand...
Click to collapse
I know. There it says it has no cellular network. As the logs I posted indicate, something goes badly wrong while searching for cells.
Tried it now, after a backup, but it did not change the situation. The sim card is recognized, but "no service" remains.
yahya69 said:
Tried it now, after a backup, but it did not change the situation. The sim card is recognized, but "no service" remains.
Click to expand...
Click to collapse
The fastboot commands clear the modem cache, and the cache regenerates on boot up.
Unfortunately, it looks like your issue is hardware-related. Which method did you use to restore to the stock firmware?
VitaTaf said:
The fastboot commands clear the modem cache, and the cache regenerates on boot up.
Unfortunately, it looks like your issue is hardware-related.
Click to expand...
Click to collapse
Which really would be a first time for me. I never saw the GSM module of a phone suddenly fail. My son insists that nothing had happened..
Yesterday, after reflashing the stock firmware yet again, I shortly got a very weak signal, and then, after I went to manual operator selection, it immediately went away again and stubbornly remained absent since.
VitaTaf said:
Which method did you use to restore to the stock firmware?
Click to expand...
Click to collapse
TWRP (adb sideload). I am not sure whether the image is flashable via fastboot.
yahya69 said:
Which really would be a first time for me. I never saw the GSM module of a phone suddenly fail. My son insists that nothing had happened..
Yesterday, after reflashing the stock firmware yet again, I shortly got a very weak signal, and then, after I went to manual operator selection, it immediately went away again and stubbornly remained absent since.
TWRP (adb sideload). I am not sure whether the image is flashable via fastboot.
Click to expand...
Click to collapse
As a last resort, I would suggest locating the full stock firmware for your device and follow the included instructions (if any) to flash it via fastboot, or at the very least, flash the fsg.mbn and NON-HLOS.bin for your device as listed under Modem Firmware in this thread. Instructions for flashing are included in the downloaded archive.
VitaTaf said:
As a last resort, I would suggest locating the full stock firmware for your device and follow the included instructions (if any) to flash it via fastboot, or at the very least, flash the fsg.mbn and NON-HLOS.bin for your device as listed under Modem Firmware in this thread. Instructions for flashing are included in the downloaded archive.
Click to expand...
Click to collapse
I reflashed them but as a result, the sim card is no longer recognized, rebooted several times.
Update: Reflashed lineageOS and now I got my sim card back, although still not connecting to the network. Reflashed the stock firmware with twrp (not sure how this would be done via fastboot), I got my phone to re-connect to the network for a few seconds, which made me jump up and down in excitement, but then the connection dropped again, before I could even make a phonecall
Update 2 Tried a different sim card, but again, when I try to register automatically, this is what I see:
}
D/PHONE (15915): [ServiceState] setDataRegState=1
D/PHONE (15915): [ServiceState] setDataRadioTechnology=0
D/GsmSST (15915): [GsmSST] 0handlPollStateResultMessage: GsmSST setDataRegState=1 regState=0 dataRadioTechnology=0
D/PHONE (15915): [ServiceState] setVoiceRegState=1
E/PHONE (15915): [ServiceState] setState deprecated use setVoiceRegState()
D/GsmSST (15915): [GsmSST] 0handleSIB5LackIssue: no cell location change and config is 'on'
D/GsmSST (15915): [GsmSST] 0Poll ServiceState done: oldSS=[1 1 voice home data home null null null null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] newSS=[1 1 voice home data home null null null null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] oldMaxDataCalls=20 mNewMaxDataCalls=20 oldReasonDataDenied=-1 realOldType=Unknown realNewType=Unknown mNewReasonDataDenied=-1
D/PHONE (15915): [ServiceState] setNullState=1
Needless to say it fails.
So basically a few months ago I upgraded from Android 9 nontreble to Android 10 treble. Bad thing is I didn't back up my EFS partition, reason for not doing it?: I've been switching back and forth between non treble and treble and didn't encounter any problems WHATSOEVER, up until today. I decided to switch back to android 9 because my phone felt sluggish with android 10. After flashing the android 9 nontreble ROM, gapps, and magisk. I could set my country at the startup screen, but I was stuck at "Just Wait" logo. Proceeded to do another full wipe this time flashing only the ROM. I was able to get past the "Just Wait" animation, but ended up with being greeted by a blackscreen instead of the usual homescreen, the status bar was visible though, the SIM card was being detected, I could also adjust my volume, but after a few minutes of sitting on a blackscreen my phone would just restart by itself over and over again. I've read a couple of post on XDA and I've come to the conclusion that me reverting back to android 9 while having used android 10 on top of the transition being treble -> nontreble somehow messed with my EFS partition.
To those would help me I would welcome your suggestions on how to fix my EFS partition.
So today i tried finding out what my phone's IMEI is.
tried running in a .bat file a command line i found on android.stackexchange:
Code:
@echo off
setlocal enabledelayedexpansion
for /f "tokens=6*" %%a in ('adb shell "service call iphonesubinfo 1 ^| grep -m 1 \"'\""') do (
set imei1=%%a)
for /f "tokens=6*" %%b in ('adb shell "service call iphonesubinfo 1 ^| grep -m 2 \"'\""') do (
set imei2=%%b)
for /f "tokens=4*" %%c in ('adb shell "service call iphonesubinfo 1 ^| grep -m 3 \"'\""') do (
set imei3=%%c)
set imei=!imei1!!imei2!!imei3!
echo !imei! > imei.txt
for /f "delims=" %%d in (imei.txt) do (
set DeviceIMEI=%%d
set DeviceIMEI=!DeviceIMEI:'=!
set DeviceIMEI=!DeviceIMEI:.=!
set OIMEI=Phone IMEI !DeviceIMEI!
)
echo %OIMEI%
pause
tried using this on two different phones(the busted/semi bricked phone i mentioned in the OP, and another old phone).
running .bat while old phone was connected:
Phone IMEI 3598***********
while on my santoni it dispalyed:
Phone IMEI found