Related
PS: Should t be in development?
Hi,
I'm working on my AOSP branch of my ROM but I get a weired problem that I cannot solve since almost a week.
So I check'ed out the AOSP code from scrach and try it.
I/ Point #1: It hangs
Here is what happens:
- compile
- flash
- flash gapps-up frf91
- reboot
Now SetupWizard.apk hangs for ever on the "Signing in..." screen.
I tried branches: froyo, android-2.2_r1 and android-2.2_r1.1... all the same.
adb logcat shows me:
Code:
I/SetupWizard( 211): Got response: SUCCESS
D/SetupWizard( 211): in mWaitForAndroidId.run()
D/GoogleLoginService( 211): in waitForAndroidId result=0
D/SetupWizard( 211): waitForAndroidId returned: 0
then
Code:
D/MobileDataStateTracker( 83): replacing old mInterfaceName (rmnet0) with rmnet0 for hipri
D/MobileDataStateTracker( 83): default Received state= CONNECTED, old= CONNECTED, reason= (unspecified), apnTypeList= default
D/NetworkLocationProvider( 83): onDataConnectionStateChanged 3
D/MobileDataStateTracker( 83): replacing old mInterfaceName (rmnet0) with rmnet0 for hipri
D/MobileDataStateTracker( 83): default Received state= CONNECTED, old= CONNECTED, reason= (unspecified), apnTypeList= default
D/NetworkLocationProvider( 83): onDataConnectionStateChanged 3
D/SntpClient( 83): request time failed: java.net.SocketTimeoutException: Connection timed out
Over and over and over again...
II/ Point #2: It partially worked
Then I do a hard reboot.
When it reboots, I go to Settings, accounts etc.
From there I can see my account... sync is on so I click on it:
- Contacts: OFF
- Gmail: OFF
- Picasa: ON
- Calendar: ON
I tried douzens of times and no matter the time I wait on the "Signing in screen", I always get the same logcat and results.
Please, help me guess what's wrong.
Full logcat: http://fpaste.org/xNXT/
-----
What could I do wrong by building strict from AOSP?
Thanks a lot!
http://pastebin.com/im1v07hZ
Jr33 said:
http://pastebin.com/im1v07hZ
Click to expand...
Click to collapse
Yeah I'm trying thanks bro!
I'm wondering... if "@null" was in place, does it means my AOSP build was not using NetworkLocation.apk ?
Because I saw on CM' git repo and its: "@null" and "@null"... wonder how CM get it working
leonnib4 said:
Yeah I'm trying thanks bro!
I'm wondering... if "@null" was in place, does it means my AOSP build was not using NetworkLocation.apk ?
Because I saw on CM' git repo and its: "@null" and "@null"... wonder how CM get it working
Click to expand...
Click to collapse
i think he has it in the vendor overlay. if "@null" is in place it will not use any network location
Well still not a go.
I'm having the same sockets timeouts...
When logging from the "normal" way and when logging in the "browser" way (menu then "Browser sign-in"):
D/Genie ( 540): Can not get the location from network
D/SntpClient( 89): request time failed: java.net.SocketTimeoutException: Connection timed out
...
Here is the fix!
Thanks to Jr33 !!!
In order to get the SetupWizard.apk properly working when building from AOSP, in my case, android-2.2_r1.1 (full-passion-eng), you need to merge this:
- http://pastebin.com/im1v07hZ
- http://pastebin.com/yqjnY3xP
And it simply works!
Thanks to Jr33 !!!
I actually spent 7 days on that issue...
please help me my n1 is rebooting continuously after little use and restarts , and hanging up at the rebooting loop .. i tried to repair the phone at some service center but it didnt help me out moreover we dont have official htc service in India iam so worried about it and lost completely , i even tried cyanogen mod 7 with gingerbread but it didnt work it is still the same please help me please
sudhank said:
please help me my n1 is rebooting continuously after little use and restarts , and hanging up at the rebooting loop .. i tried to repair the phone at some service center but it didnt help me out moreover we dont have official htc service in India iam so worried about it and lost completely , i even tried cyanogen mod 7 with gingerbread but it didnt work it is still the same please help me please
Click to expand...
Click to collapse
First and easiest thing to try is to do a factory wipe right now to go back to your current base ROM. Don't install any apps. Does the problem happen? If not, next test..
Flash a STABLE ROM and DON'T install any other apps, does it happen? If no reboots, install your apps (manually from the market). Is it still okay? Next test..
Flash the ROM you were having trouble with again, with no apps, does it happen? Install your apps (manually from the market), does it happen?
You can't start guessing unless you narrow the problem. It's simple to do. Of course each time you flash a ROM, wipe data etc.. Start fresh.
When it reboots, open Command prompt in Windows and write: adb bugreport.
Look for the line containing "ARM9". Something like "ARM9 has crashed".
If you find it - return the phone, it's bad.
tried everything its a hardware issue .. how can i repair it?? help
What's up everyone
My GN1 started having the problem way before I got Gingerbread. My phone is all stock, never rooted.
I tried isolating the problem to an app or an specific thing I did to cause it to reboot.
Then I was able to confirm that the problem happens w/ the phone is charging either wall charger or USB cable . When the phone charges and I use a lot of data (browsing, youtube, IM, FB, etc.) mostly during heavy data connection use the phone will restart. None of this happens when the phone is unplugged.
Also I thought that it could've been an overheating problem but the phone runs cool, a bit warmer when charging but nothing abnormal.
Give this a try and might be the problem that you are having.
I'm having the same problem since some days!!!
And I really don't know what to do, cause I've tried ALL sort of procedure! :'-(
I have an unlocked bootloader so it'll be a problem for the Repair Service? I'm ita.
Thanks!
Sent from my Nexus One using XDA Premium App
rebooting randomly
Hi, i have the same issues here with my nexus one... i had in the past, unlocked, rooted and installed CM6, wasnt having any issues at all... but since i installed CM7, troubles started...
this week, i've done some work on that little phone... re-installed stock image, updated to 2.3.4 from OTA, done nothing else, except installing su for terminal purposes... and then, i tried to replicate troubles, which i did easily...
at first, i thought it was heat... not the case, then i remarked that it kept crashing randomly on 3g network connections, since i never have issues watching youtube on my wifi at home, but when im in the bus going to work, it crashed on youtube... so i tried other network datacomm on the 3g, and i can easily make it crash. i can never make it crash on the wifi tho...
so i started adb shell, did su, then logcat command, which gives me output in realtime of whats happening...
this output shows when i started youtube... the video started to play in portrait, so i swithc my creen landscape to get it full screen and BAM! crash, here is the output
Code:
I/WindowManager( 99): Setting rotation to 1, animFlags=0
I/ActivityManager( 99): Config changed: { scale=1.0 imsi=302/500 loc=fr_FR touch=3 keys=1/1/2 nav=3/1 orien=2 layout=34 uiMode=17 seq=5}
D/dalvikvm( 99): GC_EXPLICIT freed 304K, 44% free 5301K/9415K, external 3125K/3903K, paused 140ms
W/TimedEventQueue( 70): Event 2393 was not found in the queue, already cancelled?
D/MediaPlayer(15126): Couldn't open file on client side, trying server side
I/StagefrightPlayer( 70): setDataSource('http : //v21.lscache2.googlevideo.com/videoplayback?id=09857e993aa523f8&itag=18&uaopt=no-save&ip=0.0.0.0&ipbits=0&expire=1307568226&sparams=id,itag,uaopt,ip,ipbits,expire&signature=E5F3700F4F5B82898EB4D207F05C187045243C55.D9B8BFD850E01766AC708F880046A3333B5E29E1&key=yta1&el=standard&devKey=ATdpM7DMA4JyVrf7elHDrdsO88HsQjpE1a8d1GxQnGDm&app=youtube_gdata')
I/NuHTTPDataSource( 70): connect to v21.lscache2.googlevideo.com:80/videoplayback?id=09857e993aa523f8&itag=18&uaopt=no-save&ip=0.0.0.0&ipbits=0&expire=1307568226&sparams=id,itag,uaopt,ip,ipbits,expire&signature=E5F3700F4F5B82898EB4D207F05C187045243C55.D9B8BFD850E01766AC708F880046A3333B5E29E1&key=yta1&el=standard&devKey=ATdpM7DMA4JyVrf7elHDrdsO88HsQjpE1a8d1GxQnGDm&app=youtube_gdata @0
W/libutils.threads( 70): Thread (this=0x12608): don't call waitForExit() from this Thread object's thread. It's a guaranteed deadlock!
I/OMXCodec( 70): [OMX.qcom.video.decoder.avc] allocating 4 buffers of size 460800 on input port
I/OMXCodec( 70): [OMX.qcom.video.decoder.avc] allocating 8 buffers of size 345600 on output port
D/AudioHardwareQSD( 70): AudioHardware pcm playback is going to standby.
W/YouTube (15126): Avoiding double logging of play start
W/QCvdec ( 70): H264_Utils::check_header
W/QCvdec ( 70): check_header: start code 29
I/NuCachedSource2( 70): new range: offset= 1852430
I/NuHTTPDataSource( 70): connect to v21.lscache2.googlevideo.com:80/videoplayback?id=09857e993aa523f8&itag=18&uaopt=no-save&ip=0.0.0.0&ipbits=0&expire=1307568226&sparams=id,itag,uaopt,ip,ipbits,expire&signature=E5F3700F4F5B82898EB4D207F05C187045243C55.D9B8BFD850E01766AC708F880046A3333B5E29E1&key=yta1&el=standard&devKey=ATdpM7DMA4JyVrf7elHDrdsO88HsQjpE1a8d1GxQnGDm&app=youtube_gdata @1852430
W/AudioFlinger( 70): write blocked for 179 msecs, 2 delayed writes, thread 0xea00
another example, was that i wanted to install rom manager, so i went on the market, downloaded rom manager and BAM! crashed, here is a few last line of the logcat output
Code:
W/System.err( 407): at dalvik.system.NativeStart.main(Native Method)
I/TelephonyRegistry( 99): notifyServiceState: 0 home Videotron 302500 UMTS CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false
I/TelephonyRegistry( 99): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=null interfaceName=rmnet0 networkType=3
I/ActivityManager( 99): Starting: Intent { dat=market://details?id=com.koushikdutta.rommanager cmp=com.android.vending/.AssetInfoActivity } from pid 407
I/ActivityManager( 99): No longer want com.android.mms (pid 385): hidden #16
D/dalvikvm( 256): GC_EXPLICIT freed 424K, 47% free 4239K/7879K, external 3230K/3696K, paused 47ms
I/LicenseChecker( 539): Received response.
I/LicenseChecker( 539): Clearing timeout.
I/dalvikvm( 539): Total arena pages for JIT: 11
I/ActivityManager( 99): Displayed com.android.vending/.AssetInfoActivity: +352ms
I/vending ( 256): [1] PermissionsSection.getPermissionGroupLabels(): Invalid group name: null
I/LicenseChecker( 539): Received response.
I/LicenseChecker( 539): Clearing timeout.
D/dalvikvm( 407): GC_CONCURRENT freed 797K, 49% free 3694K/7239K, external 3261K/3411K, paused 3ms+3ms
I/RomNexus( 407): Using gzip for download.
W/KeyCharacterMap( 256): No keyboard for id 131074
W/KeyCharacterMap( 256): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
I/TelephonyRegistry( 99): notifyServiceState: 0 home Videotron 302500 HSDPA CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false
I/TelephonyRegistry( 99): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=null interfaceName=rmnet0 networkType=8
E/C2DMRegistrar( 201): [C2DMReg] handleRequest caught javax.net.ssl.SSLException: Connection closed by peer
I/C2DMReceiver( 407): SERVICE_NOT_AVAILABLE
W/webcore ( 407): Can't get the viewWidth after the first layout
I/TelephonyRegistry( 99): notifyServiceState: 0 home Videotron 302500 UMTS CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false
I/TelephonyRegistry( 99): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=null interfaceName=rmnet0 networkType=3
D/dalvikvm( 407): GC_EXTERNAL_ALLOC freed 662K, 48% free 3782K/7239K, external 3357K/3411K, paused 38ms
D/dalvikvm( 407): GC_EXTERNAL_ALLOC freed 14K, 48% free 3783K/7239K, external 3849K/3921K, paused 34ms
D/dalvikvm( 407): GC_EXTERNAL_ALLOC freed 128K, 48% free 3812K/7239K, external 4286K/4392K, paused 40ms
now i did executed a adb bugreport, i can see the following, if i search for ARM9
Code:
[ 460.500457] ARM9 has CRASHED
[ 460.500518] smem: DIAG '[WCDMA] 02:18:58 FATAL: WCDMA L2 DL (dsmi.c:00191) (0)
that crash code looks really like a 3G connection issues...
here is the header of the bugreport
Code:
Build: GRJ22
Bootloader: 0.35.0017
Radio: 5.12.00.08
Network: Videotron
Kernel: Linux version 2.6.35.7-59463-g52630a3 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 PREEMPT Tue Mar 29 11:49:12 PDT 2011
Command line: board_mahimahi.disable_uart3=0 board_mahimahi.usb_h2w_sw=0 board_mahimahi.disable_sdcard=0 diag.enabled=0 board_mahimahi.debug_uart=0 smisize=0 androidboot.baseband=5.12.00.08 androidboot.cid=GOOGL001 androidboot.carrier=GOOGLE androidboot.mid=PB9910000 androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=HT08LP803098 androidboot.bootloader=0.35.0017 no_console_suspend=1 wire.search_count=5
well, i havnt fixed the issue, i just got a replacement nexusone...
I have found threads with similar problems than mine, but none of the solutions worked for me (i also tried WiFi Fixer).
I have latest CM10 + Devil's Kernel at the moment, but it was going on for a week now also on Semaphore, CM10 kernels and HellyBean rom, although i don't think it is their fault.
Update: I am updating nightlies regularly lately, have also switched back to Semaphore Kernel
I have excellent Wi-Fi connection, but if i leave the phone for a while, i cannot connect to internet anymore. Wi-Fi is still connected, the Wi-fi icon is gray or blue with moving arrows up and down. I can browse local network and my PC's shared folders.
Temporary solution is to disable and re-enable Wi-Fi. Obviously also if i reset the phone or router, but that doesn't matter.
There is no problem with router or access point. It has been working great for years. DHCP always assigns same IP to my phone's MAC address.
I can ping my computer and router, but cannot ping internet - even IP's. (connect: Network is unreachable)
I read somewhere that it is Samsung's (or even i9000) problem with Wi-Fi sleep - that when it should wake up, it does only partially.
I have flashed my phone several times recently but always in CWM, not with Odin, but the problem stays.
I believe it is something wrong with baseband (radio/modem), but don't know if this get flashed with new versions of ROM. I have I9000XXJVT version (System settings/About phone). Edit: i have flashed another modem XXJVU, but problem remains.
If someone also believes this could be the case and has more knowledge than me, what is the procedure to flash only baseband, can i do it from CWM and which version should i look for?
Logcat
I have switched WIFI channels from 11 to 6, tried to change encryption, but it didn't solve the problem.
This is logcat since turning off the screen (internet was working) until start of the problem.. i hope paste will do - it is a short one.
Code:
08-26 09:47:00.800 D/SurfaceFlinger( 489): About to give-up screen, flinger = 0x419caaf0
08-26 09:47:06.011 I/goggles ( 1726): BaseApplication: Getting userWantsHistory = false
08-26 09:47:06.421 D/dalvikvm( 1726): GC_CONCURRENT freed 1870K, 66% free 2808K/8195K, paused 72ms+3ms, total 231ms
08-26 09:47:06.421 D/dalvikvm( 1726): WAIT_FOR_CONCURRENT_GC blocked 112ms
08-26 09:47:06.507 I/goggles ( 1726): FreshnessHelper: Checking for images newer than 1345938048000
08-26 09:47:15.324 V/LockPatternKeyguardView( 664): Set visibility on [email protected]cb8 to 8388608
08-26 09:47:15.511 V/TransportControlView( 664): Create TCV [email protected]
08-26 09:47:15.824 V/KeyguardViewManager( 664): KGVM: Set visibility on com.an[email protected]40edc000 to 6291456
08-26 09:47:15.839 D/PhoneStatusBar( 945): disable: < expand icons alerts ticker system_info back home RECENT* clock >
08-26 09:47:16.019 D/dalvikvm( 664): GC_CONCURRENT freed 2953K, 41% free 13847K/23175K, paused 13ms+46ms, total 218ms
08-26 09:47:16.019 D/dalvikvm( 664): WAIT_FOR_CONCURRENT_GC blocked 120ms
08-26 09:47:16.050 V/LockPatternKeyguardView( 664): Set visibility on [email protected]cb8 to 8388608
08-26 09:47:16.054 D/PhoneStatusBar( 945): disable: < expand icons alerts ticker system_info BACK* HOME* RECENT CLOCK* >
08-26 09:47:16.144 V/LockPatternKeyguardView( 664): Set visibility on [email protected]cb8 to 8388608
08-26 09:48:07.023 I/goggles ( 1726): BaseApplication: Getting userWantsHistory = false
08-26 09:48:07.281 I/goggles ( 1726): FreshnessHelper: Checking for images newer than 1345938048000
08-26 09:48:19.023 D/ConnectivityService( 664): ConnectivityChange for WIFI: CONNECTED/CONNECTED
08-26 09:48:19.027 D/ConnectivityService( 664): handleConnectivityChange: address are the same reset per doReset linkProperty[1]: resetMask=0
08-26 09:48:19.050 D/ConnectivityService( 664): ConnectivityChange for WIFI: CONNECTED/CONNECTED
08-26 09:48:19.058 D/ConnectivityService( 664): handleConnectivityChange: address are the same reset per doReset linkProperty[1]: resetMask=0
[COLOR="red"]08-26 09:48:20.027 D/ConnectivityService( 664): NetTransition Wakelock for WifiStateMachine released by timeout[/COLOR]
08-26 09:49:02.027 D/Sensors ( 664): Smb380Sensor::~enable(0, 1)
08-26 09:49:02.027 D/Sensors ( 664): Smb380Sensor::~enable(0, 1) open /sys/class/input/event1/device/enable
08-26 09:49:02.027 D/Sensors ( 664): Smb380Sensor::~enable(0, 1) opened /sys/class/input/event1/device/enable
08-26 09:49:02.035 D/Sensors ( 664): Smb380Sensor::~setDelay(0, 200000000)
08-26 09:49:02.035 D/Sensors ( 664): Smb380Sensor::~setDelay(0, 66667000)
08-26 09:49:02.187 I/WindowManager( 664): Lock screen displayed!
08-26 09:49:02.210 D/SurfaceFlinger( 489): Screen about to return, flinger = 0x419caaf0
08-26 09:49:02.472 D/Tethering( 664): MasterInitialState.processMessage what=3
08-26 09:49:02.609 D/Tethering( 664): MasterInitialState.processMessage what=3
08-26 09:49:03.003 [COLOR="Red"]D/ConnectivityService( 664): handleInetConditionHoldEnd: net=1, condition=100, published condition=0[/COLOR]
08-26 09:49:03.214 D/PicasaUploaderSyncManager(24298): active network: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
08-26 09:49:03.214 D/PicasaUploaderSyncManager(24298): background data: true
08-26 09:49:03.496 W/ContextScopeImpl(24312): thread=1 tried to enter the scope of the application context. Ignored.
08-26 09:49:03.503 W/ContextScopeImpl(24312): thread=1 tried to enter the scope of the application context. Ignored.
08-26 09:49:03.519 I/goggles ( 1726): BaseApplication: Getting userWantsHistory = false
08-26 09:49:03.691 I/goggles ( 1726): FreshnessHelper: Checking for images newer than 1345938048000
08-26 09:49:03.917 D/PicasaSyncManager(22933): active network: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
08-26 09:49:03.917 D/PicasaSyncManager(22933): background data: true
08-26 09:49:04.074 W/ContextScopeImpl(24312): thread=1 tried to enter the scope of the application context. Ignored.
08-26 09:49:04.082 W/ContextScopeImpl(24312): thread=1 tried to enter the scope of the application context. Ignored.
08-26 09:49:04.093 I/goggles ( 1726): BaseApplication: Getting userWantsHistory = false
08-26 09:49:04.187 D/PicasaUploaderSyncManager(24298): active network: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
08-26 09:49:04.222 D/PicasaUploaderSyncManager(24298): background data: true
08-26 09:49:04.246 D/PicasaSyncManager(22933): active network: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
08-26 09:49:04.246 D/PicasaSyncManager(22933): background data: true
08-26 09:49:04.464 D/dalvikvm( 1726): GC_CONCURRENT freed 1854K, 66% free 2797K/8195K, paused 81ms+67ms, total 245ms
08-26 09:49:04.464 D/dalvikvm( 1726): WAIT_FOR_CONCURRENT_GC blocked 136ms
08-26 09:49:04.503 I/goggles ( 1726): FreshnessHelper: Checking for images newer than 1345938048000
08-26 09:49:06.394 I/ActivityManager( 664): Process com.tmobile.thememanager (pid 24054) has died.
08-26 09:49:12.039 D/Sensors ( 664): Smb380Sensor::~enable(0, 0)
08-26 09:49:12.050 D/Sensors ( 664): Smb380Sensor::~enable(0, 0) open /sys/class/input/event1/device/enable
08-26 09:49:12.050 D/Sensors ( 664): Smb380Sensor::~enable(0, 0) opened /sys/class/input/event1/device/enable
08-26 09:49:12.066 D/Sensors ( 664): Smb380Sensor::~setDelay(0, 66667000)
08-26 09:49:12.441 D/dalvikvm( 664): GC_CONCURRENT freed 2495K, 39% free 14281K/23175K, paused 18ms+11ms, total 137ms
08-26 09:49:12.441 D/dalvikvm( 664): WAIT_FOR_CONCURRENT_GC blocked 109ms
08-26 09:49:12.445 D/dalvikvm( 664): WAIT_FOR_CONCURRENT_GC blocked 79ms
08-26 09:49:12.457 V/TransportControlView( 664): Create TCV [email protected]
08-26 09:49:12.570 D/SurfaceFlinger( 489): About to give-up screen, flinger = 0x419caaf0
08-26 09:49:12.656 V/LockPatternKeyguardView( 664): Set visibility on [email protected]cb8 to 8388608
08-26 09:49:12.687 V/LockPatternKeyguardView( 664): Set visibility on [email protected]cb8 to 8388608
[COLOR="Red"]08-26 09:49:23.093 W/ThrottleService( 664): unable to find stats for iface pdp0[/COLOR]
08-26 09:50:07.011 I/goggles ( 1726): BaseApplication: Getting userWantsHistory = false
08-26 09:50:07.203 I/goggles ( 1726): FreshnessHelper: Checking for images newer than 1345938048000
08-26 09:50:08.261 D/dalvikvm( 664): WAIT_FOR_CONCURRENT_GC blocked 0ms
08-26 09:50:08.382 D/dalvikvm( 664): GC_EXPLICIT freed 1119K, 38% free 14381K/23175K, paused 8ms+8ms, total 121ms
08-26 09:50:44.695 D/ConnectivityService( 664): ConnectivityChange for WIFI: CONNECTED/CONNECTED
08-26 09:50:44.707 D/ConnectivityService( 664): handleConnectivityChange: address are the same reset per doReset linkProperty[1]: resetMask=0
08-26 09:50:44.718 D/ConnectivityService( 664): ConnectivityChange for WIFI: CONNECTED/CONNECTED
08-26 09:50:44.734 D/ConnectivityService( 664): handleConnectivityChange: address are the same reset per doReset linkProperty[1]: resetMask=0
[COLOR="red"]08-26 09:50:45.699 D/ConnectivityService( 664): NetTransition Wakelock for WifiStateMachine released by timeout[/COLOR]
08-26 09:51:07.242 I/goggles ( 1726): BaseApplication: Getting userWantsHistory = false
08-26 09:51:07.421 I/goggles ( 1726): FreshnessHelper: Checking for images newer than 1345938048000
08-26 09:51:07.425 D/Tethering( 664): MasterInitialState.processMessage what=3
08-26 09:51:07.453 D/Tethering( 664): MasterInitialState.processMessage what=3
08-26 09:51:07.589 W/ContextScopeImpl(24312): thread=1 tried to enter the scope of the application context. Ignored.
08-26 09:51:07.609 W/ContextScopeImpl(24312): thread=1 tried to enter the scope of the application context. Ignored.
08-26 09:51:07.625 I/goggles ( 1726): BaseApplication: Getting userWantsHistory = false
08-26 09:51:07.625 D/PicasaUploaderSyncManager(24298): active network: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
08-26 09:51:07.828 D/PicasaSyncManager(22933): active network: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
08-26 09:51:07.863 D/dalvikvm( 1726): GC_CONCURRENT freed 1840K, 66% free 2800K/8195K, paused 19ms+26ms, total 93ms
08-26 09:51:07.863 D/dalvikvm( 1726): WAIT_FOR_CONCURRENT_GC blocked 21ms
08-26 09:51:07.910 I/goggles ( 1726): FreshnessHelper: Checking for images newer than 1345938048000
08-26 09:51:07.933 D/PicasaUploaderSyncManager(24298): background data: true
08-26 09:51:07.937 D/PicasaSyncManager(22933): background data: true
08-26 09:51:07.964 D/PicasaUploaderSyncManager(24298): active network: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
08-26 09:51:07.964 D/PicasaUploaderSyncManager(24298): background data: true
08-26 09:51:07.980 W/ContextScopeImpl(24312): thread=1 tried to enter the scope of the application context. Ignored.
08-26 09:51:07.984 D/ConnectivityService( 664): handleInetConditionHoldEnd: net=1, condition=100, published condition=0
08-26 09:51:07.992 W/ContextScopeImpl(24312): thread=1 tried to enter the scope of the application context. Ignored.
08-26 09:51:08.003 I/goggles ( 1726): BaseApplication: Getting userWantsHistory = false
08-26 09:51:08.199 I/goggles ( 1726): FreshnessHelper: Checking for images newer than 1345938048000
08-26 09:51:08.218 D/PicasaSyncManager(22933): active network: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
08-26 09:51:08.222 D/PicasaSyncManager(22933): background data: true
08-26 09:51:10.476 D/dalvikvm(24085): GC_CONCURRENT freed 3810K, 60% free 3334K/8195K, paused 13ms+4ms, total 58ms
[COLOR="Red"]08-26 09:51:11.253 W/SocketClient( 487): write error (Broken pipe)
08-26 09:51:13.292 W/SocketClient( 487): write error (Broken pipe)
08-26 09:51:15.332 W/SocketClient( 487): write error (Broken pipe)
08-26 09:51:17.375 W/SocketClient( 487): write error (Broken pipe)
08-26 09:51:21.023 W/SocketClient( 487): write error (Broken pipe)[/COLOR]
08-26 09:51:21.152 I/ActivityManager( 664): Start proc com.google.android.gm for service com.google.android.gm/.provider.MailSyncAdapterService: pid=24550 uid=10047 gids={3003, 1015, 1028}
08-26 09:51:21.171 E/Trace (24550): error opening trace file: No such file or directory (2)
08-26 09:51:21.468 I/ActivityThread(24550): Pub gmail-ls: com.google.android.gm.provider.MailProvider
08-26 09:51:21.503 I/ActivityThread(24550): Pub com.google.android.gmail.SuggestionProvider: com.google.android.gm.SuggestionsProvider
08-26 09:51:21.507 I/ActivityThread(24550): Pub com.google.android.gm: com.google.android.gm.provider.PublicContentProvider
08-26 09:51:21.953 I/Gmail (24550): calculateUnknownSyncRationalesAndPurgeInBackground: queueing
08-26 09:51:21.976 I/Gmail (24550): calculateUnknownSyncRationalesAndPurgeInBackground: queueing
08-26 09:51:22.031 I/Gmail (24550): calculateUnknownSyncRationalesAndPurgeInBackground: running
08-26 09:51:22.031 I/Gmail (24550): calculateUnknownSyncRationalesAndPurgeInBackground: running
08-26 09:51:22.078 I/Gmail (24550): MainSyncRequestProto: lowestBkwdConvoId: 0, highestHandledServerOp: 63483, normalSync: true
08-26 09:51:22.250 W/SocketClient( 487): write error (Broken pipe)
[COLOR="red"]08-26 09:51:22.273 E/Gmail (24550): IOException: Unable to resolve host "android.clients.google.com": [/COLOR]No address associated with hostname
08-26 09:51:22.316 D/SyncManager( 664): failed sync operation [email protected] (com.google), gmail-ls, SERVER, earliestRunTime 22107560, SyncResult: stats [ numIoExceptions: 1]
Solved?
Since last time i had problem i have reflashed radio via odin, but then my IMEI disappeared.
Then i flashed radio via CWM and there are no problems for 15 minutes. :victory:
Edit: I have solved the problem by flashing only modem (=radio=baseband) files from recovery mode (CWM).
I've used modem files found here: http://forum.xda-developers.com/showthread.php?t=1158783
xxjvu and xwjw1 both worked for me.
Hello
I have the same problem as you, my s3 is new and has the factory rom.
I do not quite understand how you solved it. Could you explain it better.
In the link above there are many modem files, which is correct?
I need to root the phone? it's affect the warranty?
Thank you very much
aambro said:
Since last time i had problem i have reflashed radio via odin, but then my IMEI disappeared.
Then i flashed radio via CWM and there are no problems for 15 minutes. :victory:
Edit: I have solved the problem by flashing only modem (=radio=baseband) files from recovery mode (CWM).
I've used modem files found here: http://forum.xda-developers.com/showthread.php?t=1158783
xxjvu and xwjw1 both worked for me.
Click to expand...
Click to collapse
aambro said:
Since last time i had problem i have reflashed radio via odin, but then my IMEI disappeared.
Then i flashed radio via CWM and there are no problems for 15 minutes. :victory:
Edit: I have solved the problem by flashing only modem (=radio=baseband) files from recovery mode (CWM).
I've used modem files found here: http://forum.xda-developers.com/showthread.php?t=1158783
xxjvu and xwjw1 both worked for me.
Click to expand...
Click to collapse
thank you very much this helps me...
I have been running the unofficial CM 12.1 release from April on my Tab S2 T-810 since that date.
The tablet has been fine - outside the limitations by that release - this morning, however, I found that I had lost WiFi access and have not been able to restore it. I have not downloaded any program updates, nor updated the system, and this seems to have happened overnight. The tablet had not turned off and showed 71% battery this morning. Rebooting the tablet has no effect. I am loath to reinstall CM since I will lose some of the information related to my setup.
Can this be a software bug? Is there another way of turning WiFi on besides through the CM settings such as using the command line in a terminal window? Any attempt to turn WiFi on in settings only results in "turning WiFi on..." displayed with no further activity. My tablet is rooted. By the way, Bluetooth seems to work.
@T_I
Hmm, how do I interpret your reply?
hga89 said:
Hmm, how do I interpret your reply?
Click to expand...
Click to collapse
Well this would have been a better question to ask in the CM thread.
Try CM13?
Lightn1ng said:
Well this would have been a better question to ask in the CM thread.
Try CM13?
Click to expand...
Click to collapse
I eventually first installed MM 6.0 and then CM 13.0 but WiFi cannot be turned on, then reverting to MM 6.0 to see if WiFi worked there but no luck.
Looks like a hardware problem but has anyone else encountered WiFi suddenly dying completely?
The warranty period is one year and I had had the tablet for almost exactly six months when this happened. Since I have both rooted the tablet and installed another ROM, initially CM 12, it seems it will not be covered?
Does anyone have experience getting warranty repairs on a rooted tablet?
hga89 said:
I eventually first installed MM 6.0 and then CM 13.0 but WiFi cannot be turned on, then reverting to MM 6.0 to see if WiFi worked there but no luck.
Looks like a hardware problem but has anyone else encountered WiFi suddenly dying completely?
The warranty period is one year and I had had the tablet for almost exactly six months when this happened. Since I have both rooted the tablet and installed another ROM, initially CM 12, it seems it will not be covered?
Does anyone have experience getting warranty repairs on a rooted tablet?
Click to expand...
Click to collapse
You might want to check with the dev of the cm13 ROM for the T810. He recently had a warrantee repair on his S2 with knox tripped. You can PM him here.
lewmur said:
You might want to check with the dev of the cm13 ROM for the T810. He recently had a warrantee repair on his S2 with knox tripped. You can PM him here.
Click to expand...
Click to collapse
Thank you, just did that. Samsung quoted me 9-11 days turnaround time for the repair of the WiFi...
I have the same problem, WIFI cannot be turned on
xyandxl said:
I have the same problem, WIFI cannot be turned on
Click to expand...
Click to collapse
Interesting. I have the T810, how about you? Are you on CM?
I spent almost one hour with a Samsung technician yesterday doing the following: force-stopping the two WiFi applications; booting into the recovery partition and wiping the cache; booting into safe mode and finally rebooting my own router on the technician's request. The latter, of course, had no bearing on the problem. The technician had not heard of this problem before.
None of the above worked and just to make sure this was not a CM problem I had - prior to contacting Samsung support - reinstalled stock 6.0 on the unit but it behaved no different.
A command-line tool to run on the unit to find the exact error code would be very helpful.
hga89 said:
Interesting. I have the T810, how about you? Are you on CM?
I spent almost one hour with a Samsung technician yesterday doing the following: force-stopping the two WiFi applications; booting into the recovery partition and wiping the cache; booting into safe mode and finally rebooting my own router on the technician's request. The latter, of course, had no bearing on the problem. The technician had not heard of this problem before.
None of the above worked and just to make sure this was not a CM problem I had - prior to contacting Samsung support - reinstalled stock 6.0 on the unit but it behaved no different.
A command-line tool to run on the unit to find the exact error code would be very helpful.
Click to expand...
Click to collapse
In response to another post I made, Ashyx suggested downloading syslog to check the logs. I will do so. Would be interesting if you could do the same.
Here are the mentions I could find of wifi in the logs using syslog. wifi could be found in last_kmsg.log, logcat.log and eventl.log. I am not used to reading android logs but in last_kmsg.log between lines 399 and 416 a Broadcom Dongle Host Driver is being initialized.
Ideas anyone? I should add that the below is when booting CM 13.
last_kmsg.log:397: [ 2.682373] ## wifi_probe
last_kmsg.log:398: [ 2.682586] wifi_set_power = 1
last_kmsg.log:399: [ 3.202178] wifi_set_carddetect = 1
last_kmsg.log:416: [ 3.378906] wifi_set_power = 0
logcat.log:2080: 08-10 12:57:53.610 I/acvpnagent(16328): Function: OnNetworkChange File: AndroidSNAKSystem.cpp Line: 262 Network Change Message: No Connectivity: 0 Is Failover: 0 NetworkInfo: NetworkInfo: Type: Mobile Coarse State: Connected Detailed State: Connected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Wifi Coarse State: Disconnected Detailed State: Disconnected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Ethernet Coarse State: Unknown Detailed State: Idle Is Available: 0 Is FailOver: 1 Is FailOver: 1
logcat.log:4854: 08-10 13:00:08.532 I/acvpnagent(17178): Function: OnNetworkChange File: AndroidSNAKSystem.cpp Line: 262 Network Change Message: No Connectivity: 0 Is Failover: 0 NetworkInfo: NetworkInfo: Type: Mobile Coarse State: Connected Detailed State: Connected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Wifi Coarse State: Disconnected Detailed State: Disconnected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Ethernet Coarse State: Unknown Detailed State: Idle Is Available: 0 Is FailOver: 1 Is FailOver: 1
event.log:360: 08-10 12:53:44.899 I/netstats_wifi_sample( 414): [849210724,1868292,2286635822,2470712,844926737,1814474,2248078123,2475581,844926737,1814474,2247907129,2474148,1470848024710]
event.log:752: 08-10 12:55:47.258 I/netstats_wifi_sample( 414): [849210724,1868292,2286635822,2470712,844926737,1814474,2248078123,2475581,844926737,1814474,2247907129,2474148,1470848147075]
event.log:1379: 08-10 12:58:13.172 I/netstats_wifi_sample( 414): [849210724,1868292,2286635822,2470712,844926737,1814474,2248078123,2475581,844926737,1814474,2247907129,2474148,1470848293002]
Found 9 matches for "wifi".
hga89 said:
Here are the mentions I could find of wifi in the logs using syslog. wifi could be found in last_kmsg.log, logcat.log and eventl.log. I am not used to reading android logs but in last_kmsg.log between lines 399 and 416 a Broadcom Dongle Host Driver is being initialized.
Ideas anyone? I should add that the below is when booting CM 13.
last_kmsg.log:397: [ 2.682373] ## wifi_probe
last_kmsg.log:398: [ 2.682586] wifi_set_power = 1
last_kmsg.log:399: [ 3.202178] wifi_set_carddetect = 1
last_kmsg.log:416: [ 3.378906] wifi_set_power = 0
logcat.log:2080: 08-10 12:57:53.610 I/acvpnagent(16328): Function: OnNetworkChange File: AndroidSNAKSystem.cpp Line: 262 Network Change Message: No Connectivity: 0 Is Failover: 0 NetworkInfo: NetworkInfo: Type: Mobile Coarse State: Connected Detailed State: Connected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Wifi Coarse State: Disconnected Detailed State: Disconnected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Ethernet Coarse State: Unknown Detailed State: Idle Is Available: 0 Is FailOver: 1 Is FailOver: 1
logcat.log:4854: 08-10 13:00:08.532 I/acvpnagent(17178): Function: OnNetworkChange File: AndroidSNAKSystem.cpp Line: 262 Network Change Message: No Connectivity: 0 Is Failover: 0 NetworkInfo: NetworkInfo: Type: Mobile Coarse State: Connected Detailed State: Connected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Wifi Coarse State: Disconnected Detailed State: Disconnected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Ethernet Coarse State: Unknown Detailed State: Idle Is Available: 0 Is FailOver: 1 Is FailOver: 1
event.log:360: 08-10 12:53:44.899 I/netstats_wifi_sample( 414): [849210724,1868292,2286635822,2470712,844926737,1814474,2248078123,2475581,844926737,1814474,2247907129,2474148,1470848024710]
event.log:752: 08-10 12:55:47.258 I/netstats_wifi_sample( 414): [849210724,1868292,2286635822,2470712,844926737,1814474,2248078123,2475581,844926737,1814474,2247907129,2474148,1470848147075]
event.log:1379: 08-10 12:58:13.172 I/netstats_wifi_sample( 414): [849210724,1868292,2286635822,2470712,844926737,1814474,2248078123,2475581,844926737,1814474,2247907129,2474148,1470848293002]
Found 9 matches for "wifi".
Click to expand...
Click to collapse
Did a further analysis of the various logs. I cannot find any messages tagged error or warning but it seems the Broadcom Dongle Host Driver is able to retrieve a MAC address for the WiFi card immediately followed by:
last_kmsg.log:416: [ 3.378906] wifi_set_power = 0
Any suggestions?
Please don't paste logs in posts.
Use Pastebin.com or upload the logs to Tinyupload.com.
If you upload them I can take a look.
Also you should be running complete stock.
Is your IMEI intact?
ashyx said:
Please don't paste logs in posts.
Use Pastebin.com or upload the logs to Tinyupload.com.
If you upload them I can take a look.
Also you should be running complete stock.
Is your IMEI intact?
Click to expand...
Click to collapse
Than you ashyx. I have now downloaded the zipped logs to http://s000.tinyupload.com/index.php?file_id=38641397716294966079. This is with CM 13 since I need root access to access the logs.
I cannot find an IMEI listing - or any in the About tablet and Status section where it is on my phone. Note that this is a Wifi-only tablet, T-810. On my phone I do have several fields with IMEI, IMEISV, and (cellular) network info, not so on the tablet, only the IP address (unavailable) and MAC address (all zeroes).
Note that I lost Wifi overnight without having installed any system update or any new software at all, it was just not connecting one morning...
hga89 said:
Than you ashyx. I have now downloaded the zipped logs to http://s000.tinyupload.com/index.php?file_id=38641397716294966079. This is with CM 13 since I need root access to access the logs.
I cannot find an IMEI listing - or any in the About tablet and Status section where it is on my phone. Note that this is a Wifi-only tablet, T-810. On my phone I do have several fields with IMEI, IMEISV, and (cellular) network info, not so on the tablet, only the IP address (unavailable) and MAC address (all zeroes).
Note that I lost Wifi overnight without having installed any system update or any new software at all, it was just not connecting one morning...
Click to expand...
Click to collapse
You should really go back to full stock firmware and then pull the logs.
No point trying to track down an issue that is caused by a custom OS.
ashyx said:
You should really go back to full stock firmware and then pull the logs.
No point trying to track down an issue that is caused by a custom OS.
Click to expand...
Click to collapse
OK, will do that and get the logs after rooting.
Before doing so today, I am, however, restoring the latest of the two nandroid backups I have to see if I can get the service back.
hga89 said:
OK, will do that and get the logs after rooting.
Before doing so today, I am, however, restoring the latest of the two nandroid backups I have to see if I can get the service back.
Click to expand...
Click to collapse
Just restored the latest of the two nandroid backups, which included restoring EFS and RADIO partitions. This backup was done /after/ I encountered the Wifi-issue. Restore went fine but no Wifi, I also see that I now have an IMEI field in Phone Settings/Status but that the field is blank.
I believe I have another nandroid from a long time ago when everything was working fine and I will figure out how to get that to the tablet and try a restore.
hga89 said:
Just restored the latest of the two nandroid backups, which included restoring EFS and RADIO partitions. This backup was done /after/ I encountered the Wifi-issue. Restore went fine but no Wifi, I also see that I now have an IMEI field in Phone Settings/Status but that the field is blank.
I believe I have another nandroid from a long time ago when everything was working fine and I will figure out how to get that to the tablet and try a restore.
Click to expand...
Click to collapse
The 2 are tied together. No IMEI usually means an EFS issue and therefore wifi and radio issues.
You really need that backup of the EFS.
ashyx said:
The 2 are tied together. No IMEI usually means an EFS issue and therefore wifi and radio issues.
You really need that backup of the EFS.
Click to expand...
Click to collapse
Just restored a nandroid backup I had made immediately after buying the tablet (Android 5) but restoring it, including the EFS and RADIO partitions did not restore Wifi-connectivity. I also tried "factory reset" from the OS but that also did not help.
I have now uploaded a syslog archive to http://s000.tinyupload.com/index.php?file_id=25506746479682944901.
Ashyx, thank you for looking at them.
Yesterday I used Odin to restore the nandroid backup I made before I rooted and installing a ROM. However, the Wifi problem persists, it cannot be turned on. Not sure the settings in Odin were correct: I used AP to restore and left the Auto-reboot and F. Reset Time checked which was the default. Was this correct?
I am using Odin 3.10.7 since I have to do this from a netbook running Vista Home and have no other Windows computer available. Does this make a difference?
Thank you.
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.