Develop Bugs

[Q] 2am bugs on new OTA (Touch of Blue ROM)

My Dinc currently has cmlusco's excellent Touch of Blue v2.2 installed(a full wipe install with v6), which includes the latest OTA. I also have the latest radio (2.15.10.12.20) which cmlusco pulled from the OTA installed.
Since the latest OTA files were installed I have seen a lot of people complaining about 2am reboots. I happen to work 3rd shift, so I am awake during this time and instead of the reboots(as I am usually using my phone at this time) I begin to have mounting errors. This never happened before the new OTA files and only occurs between the times of 2am-5am.
Basically, the second it hits 2am if the screen goes to sleep(either by time or by pressing the power button) after 2-3 seconds both the sd card and emmc unmount themselves. As soon as you wake the phone up the "Preparing phone storage" message is displayed and everything is remounted. I noticed this because I listen to music from my sd card through amazon mp3, and when the screen goes dark the music stops.
I began pulling logs with alogcat and this is an example of what I see happening:
--------- beginning of /dev/log/system
D/InputManagerService( 145): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$[email protected]
--------- beginning of /dev/log/main
I/power ( 145): *** set_screen_state 0
D/PowerManagerService( 145): setScreenStateLocked++, on: false, err: 0
D/SensorService( 145): disable: connection.get() = 0x37d8f8
D/SensorService( 145): disable: get sensor name = CM3602 Light sensor
D/SensorService( 145): SensorDevice::activate: handle = 0x4, enabled = 0x0
D/SensorService( 145): noteStopSensor: uid = 0x3e8, handle = 0x4
D/SensorService( 145): pid=145, uid=1000
D/SensorService( 145): Active sensors:
D/SensorService( 145): BMA150 3-axis Accelerometer (handle=0x00000000, connections=1)
D/PowerManagerService( 145): setScreenStateLocked, turn off the button light
D/lights ( 145): set_light_buttons_func: on=0 brightness=0
V/KeyguardViewMediator( 145): password timeout delay 599226ms
D/KeyguardViewManager( 145): show(); mKeyguar[email protected]409e7148
D/HtcLockScreen( 145): createPatternUnlockScreen() ...
D/HtcLockScreen( 145): package name not found - com.htc.lockscreen
D/SensorService( 145): disable: connection.get() = 0x37d8f8
D/SensorService( 145): disable: get sensor name = BMA150 3-axis Accelerometer
D/SensorService( 145): SensorDevice::activate: handle = 0x0, enabled = 0x0
D/Sensors ( 145): Enable akm: en = 0
D/SensorService( 145): noteStopSensor: uid = 0x3e8, handle = 0x0
D/SensorService( 145): pid=145, uid=1000
D/SensorService( 145): Active sensors:
D/AlarmManager( 145): ACTION_SCREEN_OFF
W/InputManagerService( 145): Receive : Intent.ACTION_SCREEN_OFF
D/SurfaceFlinger( 145): About to give-up screen, flinger = 0xb26c0
W/InputManagerService( 145): Disable input method client.
W/IInputConnectionWrapper( 8615): beginBatchEdit on inactive InputConnection
W/IInputConnectionWrapper( 8615): endBatchEdit on inactive InputConnection
D/StatusBarPolicy( 216): onSignalStrengthsChanged
D/StatusBarPolicy( 216): iconIndex=1
V/StatusBarPolicy( 216): cdmaLevel:3;max:4
D/StatusBarPolicy( 216): iconLevel:3
D/StatusBarService( 216): updateIcon slot=phone_signal index=20 viewIndex=14 old=StatusBarIcon(pkg=com.android.systemui id=0x7f020009 level=0 visible=true num=0 ) icon=StatusBarIcon(pkg=com.android.systemui id=0x7f02000a level=0 visible=true num=0 )
I/USERIAL_LINUX( 458): ##### USerial_Ioctl: BT_Wake, 0x8003 ####
D/ContactWidget Matrix( 264): Received intent:android.intent.action.SCREEN_OFF
D/StatusBarManagerService( 145): disable what =1, token = [email protected], pkg = android, mBar = [email protected]
D/MountService( 145): Receive Screen OFF!
D/MountService( 145): persist.erasedirtyfat.done = 0
D/MountService( 145): The current time is 2:40:13
D/AK8973 ( 102): Compass CLOSE
D/AutoSetting( 8786): service - mHandler: cancel location update
D/AutoSetting( 8786): service - changes count: 0
D/InputManagerService( 145): Starting input on non-focused client [email protected] (uid=10108 pid=8615)
V/SyncManager( 145): runstateidle: nonHTCActiveCount++ :1
I/USERIAL_LINUX( 458): ##### USerial_Ioctl: BT_Sleep, 0x8004 ####
D/KeyguardViewMediator( 145): wakeWhenReadyLocked(26)
D/lights ( 145): set_light_buttons_func: on=2960685 brightness=45
I/power ( 145): *** set_screen_state 1
D/PowerManagerService( 145): setScreenStateLocked++, on: true, err: 0
D/SurfaceFlinger( 145): Screen about to return, flinger = 0xb26c0
D/SensorService( 145): enable: connection.get() = 0x37d8f8, (2.3.4)
D/SensorService( 145): enable: get sensor name = CM3602 Light sensor
D/SensorService( 145): SensorDevice::activate: handle = 0x4, enabled = 0x1
D/SensorService( 145): noteStartSensor: uid = 0x3e8, handle = 0x4
D/SensorService( 145): pid=145, uid=1000
D/SensorService( 145): Active sensors:
D/SensorService( 145): CM3602 Light sensor (handle=0x00000004, connections=1)
D/PowerManagerService( 145): New lightsensor value:40, lcdValue:45
D/PowerManagerService( 145): lightSensorChangedLocked, buttonValue >= 0, mPowerState = 3
D/lights ( 145): set_light_buttons_func: on=16777215 brightness=255
D/PowerManagerService( 145): button light setOrientation:-1
V/KeyguardViewMediator( 145): password timeout delay 594138ms
D/AlarmManager( 145): ACTION_SCREEN_ON
W/InputManagerService( 145): Receive : Intent.ACTION_SCREEN_ON
W/InputManagerService( 145): Enable input method client.
D/HtcCdmaPhoneApp( 288): eri_id = 64 home or roaming = VZW_HOME_NETWORK
V/HtcCdmaGloableRoamingUtil( 288): localGetGlobalRoamingOption:0
D/HtcCdmaGloableRoamingUtil( 288): getNeedShowRoamingOption():true
D/HtcCdmaGloableRoamingUtil( 288): getNeedAutoSetDeny():false
D/StatusBarPolicy( 216): onSignalStrengthsChanged
D/ContactWidget Matrix( 264): Received intent:android.intent.action.SCREEN_ON
D/HtcNBPCDUtil( 288): EVENT_NBPCD_INFO
D/StatusBarPolicy( 216): iconIndex=1
V/StatusBarPolicy( 216): cdmaLevel:3;max:4
D/StatusBarPolicy( 216): iconLevel:3
D/StatusBarService( 216): updateIcon slot=phone_signal index=20 viewIndex=14 old=StatusBarIcon(pkg=com.android.systemui id=0x7f02000a level=0 visible=true num=0 ) icon=StatusBarIcon(pkg=com.android.systemui id=0x7f02000a level=0 visible=true num=0 )
D/MountService( 145): Receive Screen ON!
D/VoldCmdListener( 90): erase stop
D/VoldCmdListener( 90): Erase stop...
W/FrameworkListener( 90): Handler 'erase' error (No such file or directory)
D/VoldCmdListener( 90): volume mount /mnt/emmc
I/Vold ( 90): /dev/block/vold/179:3 being considered for volume emmc
D/Vold ( 90): Volume emmc state changing 1 (Idle-Unmounted) -> 3 (Checking)
I/StorageNotification( 216): Media {/mnt/emmc} state changed from {unmounted} -> {checking}
I//system/bin/fsck_msdos( 90): ** /dev/block/vold/179:3
I//system/bin/fsck_msdos( 90): ** Phase 1 - Read and Compare FATs
I//system/bin/fsck_msdos( 90): Attempting to allocate 845 KB for FAT
I//system/bin/fsck_msdos( 90): Attempting to allocate 845 KB for FAT
D/KeyguardViewManager( 145): hide()
D/StatusBarManagerService( 145): disable what =0, token = [email protected], pkg = android, mBar = [email protected]
D/SensorService( 145): enable: connection.get() = 0x37d8f8, (2.3.4)
D/SensorService( 145): enable: get sensor name = BMA150 3-axis Accelerometer
D/SensorService( 145): SensorDevice::activate: handle = 0x0, enabled = 0x1
D/Sensors ( 145): Enable akm: en = 1
D/AK8973 ( 102): Compass Start
D/SensorService( 145): noteStartSensor: uid = 0x3e8, handle = 0x0
D/SensorService( 145): pid=145, uid=1000
D/SensorService( 145): Active sensors:
D/SensorService( 145): BMA150 3-axis Accelerometer (handle=0x00000000, connections=1)
D/SensorService( 145): CM3602 Light sensor (handle=0x00000004, connections=1)
D/InputManagerService( 145): Window already focused, ignoring focus gain of: [email protected]
I//system/bin/fsck_msdos( 90): ** Phase 2 - Check Cluster Chains
I//system/bin/fsck_msdos( 90): ** Phase 3 - Checking Directories
D/dalvikvm( 8615): GC_CONCURRENT freed 477K, 49% free 3323K/6407K, external 36K/548K, paused 3ms+5ms
I//system/bin/fsck_msdos( 90): ** Phase 4 - Checking for Lost Files
I//system/bin/fsck_msdos( 90): 1370 files, 2008096 free (193825 clusters)
I/Vold ( 90): Filesystem check completed OK
I/Vold ( 90): Device /dev/block/vold/179:3, target /mnt/emmc mounted @ /mnt/secure/staging
D/Vold ( 90): Volume emmc state changing 3 (Checking) -> 4 (Mounted)
I/StorageNotification( 216): Media {/mnt/emmc} state changed from {checking} -> {mounted}
D/Ringer ( 288): -- intent.getAction() =android.intent.action.MEDIA_MOUNTED
D/MountService( 145): persist.erasedirtyfat.done = 0
D/MountService( 145): The current time is 2:40:19
D/FacebookReceiver( 8190): Intent.ACTION_USER_PRESENT SyncInterval=86400000,currTime=1341902419199
D/FacebookReceiver( 8190): Intent.ACTION_USER_PRESENT lastStreamSyncTime=1341902419200,lastFriendSyncTime=1341902419200
D/dalvikvm( 987): GC_EXTERNAL_ALLOC freed 191K, 46% free 2985K/5511K, external 1759K/2270K, paused 32ms
D/AppWidgetHostView( 264): updateAppWidget mInfo = AppWidgetProviderInfo(provider=ComponentInfo{mikado.bizcalpro/mikado.bizcalpro.WidgetProvider4x4})
V/CalendarProvider2( 8786): ACTION_EVENT_CHANGED
D/dalvikvm( 987): GC_EXTERNAL_ALLOC freed 176K, 46% free 2986K/5511K, external 1126K/1637K, paused 31ms
D/DrmScannerReceiver( 8918): android.intent.action.MEDIA_MOUNTED
I/EMMC ( 8918): Action mounted + path: /mnt/emmc,/mnt/sdcard,/mnt/ext_sd, /mnt/emmc,android.intent.action.MEDIA_MOUNTED
D/DrmIntentService( 8918): SCAN_STORAGE
D/DrmIntentService( 8918): Scanning /images
E/MediaScannerService( 8918): Failed to delete file /data/data/com.android.providers.media/pause_scan
D/DrmIntentService( 8918): Empty in /images
I/MediaUploader( 8937): No need to wake up
D/DrmIntentService( 8918): Scanning /audio
D/DrmIntentService( 8918): Empty in /audio
D/DrmIntentService( 8918): Scanning /video
D/DrmIntentService( 8918): Empty in /video
D/DrmIntentService( 8918): Scanning /jar
D/DrmIntentService( 8918): Empty in /jar
I/AmazonAppstore.UpdateCommands( 8587): Self-updating enabled: true
W/JustPictures( 8229): External storage mounted
D/AmazonAppstore.UpdateCommands( 8587): Adding self-update command to UpdateService
D/AmazonAppstore.UpdateService( 8587): Received action: com.amazon.mas.client.framework.UpdateService.SD_CARD_MOUNTED from intent: Intent { act=com.amazon.mas.client.framework.UpdateService.SD_CARD_MOUNTED cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/MediaScannerService( 8918): start scanning volume phoneStorage
D/MediaProvider( 8918): lock thumbnail worker
D/MediaProvider( 8918): thread is un-locked
D/MediaProvider( 8918): lock thumbnail worker
V/MediaPlayerService( 7891): Create new media retriever from pid 8918
D/MediaScannerService( 8918): getDefaultLocale =en_US
D/MediaScannerService( 8918): [MediaScannerService][scan]+external-fc303da9.db volume ID: -63947351,phoneStorage,/mnt/emmc
D/dalvikvm( 8918): GC_CONCURRENT freed 319K, 47% free 3084K/5767K, external 712K/1024K, paused 2ms+2ms
D/MediaScanner( 8918): MediaScanner:scanDirectories.doBulkInsertAll+
D/MediaScanner( 8918): MediaScanner:scanDirectories.doBulkInsertAll-
D/MediaScanner( 8918): prescan time: 34ms
D/MediaScanner( 8918): scan time: 293ms
D/MediaScanner( 8918): postscan time: 0ms
D/MediaScanner( 8918): total time: 327ms
D/MediaScannerService( 8918): [MediaScannerService][scan]-
D/MediaProvider( 8918): un-lock thumbnail worker
D/MediaProvider( 8918): un-lock thumbnail worker
D/MediaScannerService( 8918): done scanning volume phoneStorage
E/MediaScannerService( 8918): Failed to delete file /data/data/com.android.providers.media/pause_scan
D/StatusBarPolicy( 216): onSignalStrengthsChanged
D/StatusBarPolicy( 216): iconIndex=1
V/StatusBarPolicy( 216): cdmaLevel:2;max:4
D/StatusBarPolicy( 216): iconLevel:2
D/StatusBarService( 216): updateIcon slot=phone_signal index=20 viewIndex=14 old=StatusBarIcon(pkg=com.android.systemui id=0x7f02000a level=0 visible=true num=0 ) icon=StatusBarIcon(pkg=com.android.systemui id=0x7f020009 level=0 visible=true num=0 )
I/USERIAL_LINUX( 458): ##### USerial_Ioctl: BT_Wake, 0x8003 ####
I/USERIAL_LINUX( 458): ##### USerial_Ioctl: BT_Sleep, 0x8004 ####
Click to expand...
Click to collapse
I am very new to reading these logs but a few lines stuck out to me...
D/MountService( 145): Receive Screen OFF!
D/MountService( 145): persist.erasedirtyfat.done = 0
D/MountService( 145): The current time is 2:40:13
Click to expand...
Click to collapse
and then:
D/MountService( 145): Receive Screen ON!
D/VoldCmdListener( 90): erase stop
D/VoldCmdListener( 90): Erase stop...
W/FrameworkListener( 90): Handler 'erase' error (No such file or directory)
D/VoldCmdListener( 90): volume mount /mnt/emmc
I/Vold ( 90): /dev/block/vold/179:3 being considered for volume emmc
D/Vold ( 90): Volume emmc state changing 1 (Idle-Unmounted) -> 3 (Checking)
I/StorageNotification( 216): Media {/mnt/emmc} state changed from {unmounted} -> {checking}
Click to expand...
Click to collapse
I don't see anything obvious enough to make me understand what is going on, but I can definitely see that as soon as the screen goes off the phone checks the time and starts doing something with the mounts, and as soon as the command to turn back on again comes the phone begins working on remounting everything.
On another site someone mentioned HTC stating that the reboots were for memory optimization and should only happen once. I'm sure there is some sort of commonality between the reboots and my errors but it has me puzzled. Does anyone more experienced than me see anything in the logs that could lead to a fix, as I don't plan on changing my work schedule anytime soon.
Thanks for any assistance.

Laxnkio said:
My Dinc currently has cmlusco's excellent Touch of Blue v2.2 installed(a full wipe install with v6), which includes the latest OTA. I also have the latest radio (2.15.10.12.20) which cmlusco pulled from the OTA installed.
Since the latest OTA files were installed I have seen a lot of people complaining about 2am reboots. I happen to work 3rd shift, so I am awake during this time and instead of the reboots(as I am usually using my phone at this time) I begin to have mounting errors. This never happened before the new OTA files and only occurs between the times of 2am-5am.
Basically, the second it hits 2am if the screen goes to sleep(either by time or by pressing the power button) after 2-3 seconds both the sd card and emmc unmount themselves. As soon as you wake the phone up the "Preparing phone storage" message is displayed and everything is remounted. I noticed this because I listen to music from my sd card through amazon mp3, and when the screen goes dark the music stops.
I began pulling logs with alogcat and this is an example of what I see happening:
I am very new to reading these logs but a few lines stuck out to me...
and then:
I don't see anything obvious enough to make me understand what is going on, but I can definitely see that as soon as the screen goes off the phone checks the time and starts doing something with the mounts, and as soon as the command to turn back on again comes the phone begins working on remounting everything.
On another site someone mentioned HTC stating that the reboots were for memory optimization and should only happen once. I'm sure there is some sort of commonality between the reboots and my errors but it has me puzzled. Does anyone more experienced than me see anything in the logs that could lead to a fix, as I don't plan on changing my work schedule anytime soon.
Thanks for any assistance.
Click to expand...
Click to collapse
Those logs are interesting as with this newest update a file in /system/bin called erase_dirty_fat. From looking at this file it seems it scans emmc and the sdcard for bad sectors and errors. The mounting problems may be intentional by htc, as the script unmounts and mounts the emnc and sdcard. This could some how cause reboots i suppose just not sure how yet. I need to examine the file more to se exactly what it does.

cmlusco said:
Those logs are interesting as with this newest update a file in /system/bin called erase_dirty_fat. From looking at this file it seems it scans emmc and the sdcard for bad sectors and errors. The mounting problems may be intentional by htc, as the script unmounts and mounts the emnc and sdcard. This could some how cause reboots i suppose just not sure how yet. I need to examine the file more to se exactly what it does.
Click to expand...
Click to collapse
I'm running the odex version and except for the one time after first flashing it I haven't had another 2 am reboot since and never a problem mounting storage,

Bit of an update...after scouring the net i tried the manual setting the clock to 2am idea while I wasn't using the phone and let it sit for over 8 hours. I don't think I got any reboots but last night at the real 2am I didn't get any unmounts. So it has to be some sort of optimization script or something that can only run when you aren't using the phone. Hope tonight is the same result.
Sent from my ADR6300 using Tapatalk 2

For those of you getting the 2am reboots try this as a fix. Go to /system/bin and look for a file called " erase_dirty_fat ". Rename or move the file and reboot the phone. See if you still get the 2am reboots.

cmlusco said:
For those of you getting the 2am reboots try this as a fix. Go to /system/bin and look for a file called " erase_dirty_fat ". Rename or move the file and reboot the phone. See if you still get the 2am reboots.
Click to expand...
Click to collapse
Be interesting to know if this fixes the problem also, may try this Rom if it does.

Spoke too quickly I guess because the problem returned tonight after 5 days in the clear. Will try to erase that file now and see if it works.
Sent from my ADR6300 using Tapatalk 2

Its so weird i feel lucky, but also left out lol. I havent had it happen to me at all.

Same here in a way since I don't have the reboots. I've tried deleting that file to no avail, also tried leaving the phone alone for 2 8 hour blocks to try and let it finish but that doesn't seem to help either.
Wouldn't be a problem if I didn't work mids and listen to podcasts, the perfect storm. Good job htc screwing up a phone 2 years after release.
Sent from my ADR6300 using Tapatalk 2

Laxnkio said:
Spoke too quickly I guess because the problem returned tonight after 5 days in the clear. Will try to erase that file now and see if it works.
Sent from my ADR6300 using Tapatalk 2
Click to expand...
Click to collapse
Same with me, problem returned after a week of not having it. Deleting the mentioned system/bin file had no effect on mine, reboot problem still there.

kzoodroid said:
Same with me, problem returned after a week of not having it. Deleting the mentioned system/bin file had no effect on mine, reboot problem still there.
Click to expand...
Click to collapse
Well my next guess would be its one of the new apps mabey. The pic below shows the new apks added in the update. Try renaming them one at a time and see if the reboots stop.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I would start with linkify dispatcher. Make sure you have a backup incase it messes something up.

Linkify didn't work for me, going to try the one that starts with q next since it has sd in the name.
Sent from my ADR6300 using Tapatalk 2

Renaming qx didn't work either. So weird.
Sent from my Thrive using Tapatalk 2

Laxnkio said:
Renaming qx didn't work either. So weird.
Sent from my Thrive using Tapatalk 2
Click to expand...
Click to collapse
There were many other files updated and patched that could be the cause. Mabey its a common app like gmail or something, as i dont use the gmail app and i dont get the 2am bug. Hard to tell, im going to install gmail app and see if i get the reboots. I just keep thinking it has to be an app commonly used, but that i dont have installed. If it were in the framework i should be experiencing it too.

Hmmmm... Mine keeps asking me to update but I'm not doing it.
Sent from my ADR6300 using xda premium

I just went back to TOB 1.3 and everything is running fine.
---------- Post added at 11:24 PM ---------- Previous post was at 11:21 PM ----------
Is GingerTiny_v2_2.6.35.14_08/10/2012+ compatibe with TOB 1.3. I had a problem with this combo so I went back to the Feb release.

joeyz400 said:
I just went back to TOB 1.3 and everything is running fine.
---------- Post added at 11:24 PM ---------- Previous post was at 11:21 PM ----------
Is GingerTiny_v2_2.6.35.14_08/10/2012+ compatibe with TOB 1.3. I had a problem with this combo so I went back to the Feb release.
Click to expand...
Click to collapse
Yes, all versions of the Gingertiny kernel are compatible with all versions of TOB. What issues were you having?

cmlusco said:
Yes, all versions of the Gingertiny kernel are compatible with all versions of TOB. What issues were you having?
Click to expand...
Click to collapse
I get a lot of freezes and have to restart. I tried to reinstall it and got bootloops. I just did another recovery.

JB 4.1.2 ROM has bugs in WiFi

I tried both ROM which using latest 4.1.2 JellyBean, but found bugs when connecting wifi. It's always obtaining ip address..
But sometimes, it can get ip.. toggling wifi on/off cannot success connecting.
Here's the logcat, hope some experts here can give me solutions
As I'm now very dissapointed why some people not getting this problem..
Code:
E/WifiHW ( 2529): supplicant_name : wpa_supplicant
I/wpa_supplicant(29520): wpa_supplicant v2.0-devel-4.1.2 2012-11-26/18:22:02
E/wpa_supplicant(29520): Can't open default ap file
I/wpa_supplicant(29520): rfkill: Cannot open RFKILL control device
E/WifiHW ( 2529): wifi_wpa_ctrl_cleanup is skiped.
I/p2p_supplicant(29523): wpa_supplicant v2.0-devel-4.1.200
I/wpa_supplicant(29520): State: DISCONNECTED -> SCANNING
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00.00.00
I/wpa_supplicant(29520): Scan requested (ret=0) - scan timeout 10 seconds
I/wpa_supplicant(29520): nl80211: Received scan results (2 BSSes)
I/wpa_supplicant(29520): Trying to associate with F4.7C.2A (freq=2412 MHz rssi=-50dBm)
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): ASSOC when wpa_state = 3, do_assoc = 0, reassociate = 0
I/wpa_supplicant(29520): State: SCANNING -> ASSOCIATING
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=F4.7C.2A
I/wpa_supplicant(29520): Start Assoc status = [0] !!!!!
W/wpa_supplicant(29520): wlan0: Failed to initiate AP scan
E/wpa_supplicant(29520): wlan0: Not associated - Delay processing of received EAPOL frame !!!!
I/wpa_supplicant(29520): State: ASSOCIATING -> ASSOCIATED
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=6 BSSID=F4.7C.2A
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): Associated with F4.7C.2A
I/wpa_supplicant(29520): State: ASSOCIATED -> 4WAY_HANDSHAKE
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=7 BSSID=00.00.00
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
I/wpa_supplicant(29520): State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=8 BSSID=00.00.00
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): WPA: Key negotiation completed with F4.7C.2A [PTK=CCMP GTK=CCMP]
I/wpa_supplicant(29520): State: GROUP_HANDSHAKE -> COMPLETED
I/wpa_supplicant(29520): CTRL-EVENT-CONNECTED - Connection to F4.7C.2A completed (auth) [id=0 id_str=]
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=9 BSSID=00.00.00
I/wpa_supplicant(29520): 6369706C756B
I/dhcpcd (29551): dhcp main start
I/dhcpcd (29551): if(wlan0) info get Success. (MAC : F4.7C.2A)
I/dhcpcd (29551): bssid match
E/DhcpStateMachine( 2529): DHCP failed on wlan0: Timed out waiting for DHCP to finish
I/dhcpcd (30384): dhcp main start
I/dhcpcd (30384): if(wlan0) info get Success. (MAC : F4.7C.2A)
I/dhcpcd (30384): bssid match

hendry said:
I tried both ROM which using latest 4.1.2 JellyBean, but found bugs when connecting wifi. It's always obtaining ip address..
But sometimes, it can get ip.. toggling wifi on/off cannot success connecting.
Here's the logcat, hope some experts here can give me solutions
As I'm now very dissapointed why some people not getting this problem..
Code:
E/WifiHW ( 2529): supplicant_name : wpa_supplicant
I/wpa_supplicant(29520): wpa_supplicant v2.0-devel-4.1.2 2012-11-26/18:22:02
E/wpa_supplicant(29520): Can't open default ap file
I/wpa_supplicant(29520): rfkill: Cannot open RFKILL control device
E/WifiHW ( 2529): wifi_wpa_ctrl_cleanup is skiped.
I/p2p_supplicant(29523): wpa_supplicant v2.0-devel-4.1.200
I/wpa_supplicant(29520): State: DISCONNECTED -> SCANNING
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00.00.00
I/wpa_supplicant(29520): Scan requested (ret=0) - scan timeout 10 seconds
I/wpa_supplicant(29520): nl80211: Received scan results (2 BSSes)
I/wpa_supplicant(29520): Trying to associate with F4.7C.2A (freq=2412 MHz rssi=-50dBm)
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): ASSOC when wpa_state = 3, do_assoc = 0, reassociate = 0
I/wpa_supplicant(29520): State: SCANNING -> ASSOCIATING
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=-1 state=5 BSSID=F4.7C.2A
I/wpa_supplicant(29520): Start Assoc status = [0] !!!!!
W/wpa_supplicant(29520): wlan0: Failed to initiate AP scan
E/wpa_supplicant(29520): wlan0: Not associated - Delay processing of received EAPOL frame !!!!
I/wpa_supplicant(29520): State: ASSOCIATING -> ASSOCIATED
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=6 BSSID=F4.7C.2A
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): Associated with F4.7C.2A
I/wpa_supplicant(29520): State: ASSOCIATED -> 4WAY_HANDSHAKE
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=7 BSSID=00.00.00
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
I/wpa_supplicant(29520): State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=8 BSSID=00.00.00
I/wpa_supplicant(29520): 6369706C756B
I/wpa_supplicant(29520): WPA: Key negotiation completed with F4.7C.2A [PTK=CCMP GTK=CCMP]
I/wpa_supplicant(29520): State: GROUP_HANDSHAKE -> COMPLETED
I/wpa_supplicant(29520): CTRL-EVENT-CONNECTED - Connection to F4.7C.2A completed (auth) [id=0 id_str=]
I/wpa_supplicant(29520): CTRL-EVENT-STATE-CHANGE id=0 state=9 BSSID=00.00.00
I/wpa_supplicant(29520): 6369706C756B
I/dhcpcd (29551): dhcp main start
I/dhcpcd (29551): if(wlan0) info get Success. (MAC : F4.7C.2A)
I/dhcpcd (29551): bssid match
E/DhcpStateMachine( 2529): DHCP failed on wlan0: Timed out waiting for DHCP to finish
I/dhcpcd (30384): dhcp main start
I/dhcpcd (30384): if(wlan0) info get Success. (MAC : F4.7C.2A)
I/dhcpcd (30384): bssid match
Click to expand...
Click to collapse
Why are you posting this here when you've already posted it in the Omega 8 thread? This is not the place to be posting it. I'm not seeing any wifi problems.

I want some experts here can give me solutions on what's wrong with my device.. so everybody can see
My friend also never got problem using 4.1.2 based ROM. I think maybe the structure android files on my devices has invalid permission access or something else i dont know.. That's why i want to get any explanation on this..
Here i added more logcat debug data
Code:
I/WifiManager( 2820): setWifiEnabled : true
E/WifiHW ( 2529): ##################### set firmware type 0 #####################
D/WifiStateMachine( 2529): setWifiEnabled : WifiNative.setFwType(0)
D/WifiService( 2529): setWifiEnabled: true pid=2820, uid=10092
I/WifiHW ( 2529): module is semco
E/WifiHW ( 2529): ==========[WIFI] Station firmware load ===========
I/WifiHW ( 2529): Start Check B2 #######
I/WifiHW ( 2529): wifi_trigger_poke : Found 4334B3
I/WifiHW ( 2529): ==========[WIFI] SEMCO MODULE ===========
D/WfdService( 2529): intent recieved android.net.wifi.WIFI_STATE_CHANGED
D/STATUSBAR-NetworkController( 2820): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
D/STATUSBAR-WifiQuickSettingButton( 2820): Wifi onReceive(2)
D/TMSERVER/TMNetworkReceiver( 4961): TMNetworkReceiver.onReceive() Action android.net.wifi.WIFI_STATE_CHANGED
E/WifiHW ( 2529): supplicant_name : wpa_supplicant
D/WifiP2pService( 2529): P2pDisabledState{ what=131203 }
E/WifiHW ( 2529): wifi_wpa_ctrl_cleanup is skiped.
E/WifiHW ( 2529): supplicant_name : p2p_supplicant
D/WifiP2pService( 2529): Supplicant start successful
D/WifiP2pService( 2529): P2pEnablingState
E/WifiHW ( 2529): Unable to open connection to supplicant on "/data/misc/wifi/sockets/p2p0": Connection refused
D/STATUSBAR-NetworkController( 2820): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
D/STATUSBAR-WifiQuickSettingButton( 2820): Wifi onReceive(3)
D/WfdService( 2529): intent recieved android.net.wifi.WIFI_STATE_CHANGED
D/WifiP2pService( 2529): P2pEnablingState{ what=143378 }
D/WifiP2pService( 2529): DefaultState{ what=143378 }
E/WifiP2pService( 2529): Unhandled message { what=143378 }
E/WifiHW ( 2529): ##################### set firmware type 0 #####################
D/WifiStateMachine( 2529): setWifiEnabled : WifiNative.setFwType(0)
D/WifiService( 2529): startScan: false pid=31094, uid=10027
E/WifiHW ( 2529): ##################### set firmware type 0 #####################
D/WifiStateMachine( 2529): setWifiEnabled : WifiNative.setFwType(0)
D/WifiService( 2529): startScan: false pid=3240, uid=10031
D/WifiNative( 2529): callSECApiBoolean - ID [13]
D/TMSERVER/TMNetworkReceiver( 4961): TMNetworkReceiver.onReceive() Action android.net.wifi.WIFI_STATE_CHANGED
D/WifiNative( 2529): callSECApiVoid - ID [50]
D/WfdService( 2529): intent recieved android.net.wifi.STATE_CHANGE
D/STATUSBAR-NetworkController( 2820): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
D/STATUSBAR-NetworkController( 2820): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
E/WifiP2pStateTracker( 2529): getNetworkInfo : NetworkInfo: type: WIFI_P2P[], state: DISCONNECTED/DISCONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: false
D/TMSERVER/TMNetworkReceiver( 4961): TMNetworkReceiver.onReceive() Action android.net.wifi.STATE_CHANGE
E/WifiHW ( 2529): ##################### set firmware type 0 #####################
D/WifiStateMachine( 2529): setWifiEnabled : WifiNative.setFwType(0)
E/WifiHW ( 2529): ##################### set firmware type 0 #####################
D/WifiStateMachine( 2529): setWifiEnabled : WifiNative.setFwType(0)
D/WifiP2pService( 2529): P2pEnablingState{ what=147457 }
D/WifiP2pService( 2529): P2p socket connection successful
D/WifiP2pService( 2529): P2pEnabledState
D/WifiP2pService( 2529): sending p2p connection changed broadcast
I/STATUSBAR-QuickSettingButton( 2820): action: android.net.wifi.p2p.STATE_CHANGED
E/WifiStateMachine( 2529): BroadcastReceiver : WIFI_P2P_STATE_CHANGED_ACTION is : android.net.wifi.p2p.STATE_CHANGED
D/WfdService( 2529): intent recieved android.net.wifi.p2p.STATE_CHANGED
D/WfdService( 2529): intent recieved android.net.wifi.p2p.CONNECTION_STATE_CHANGE
D/WfdService( 2529): onReceive << WIFI_P2P_CONNECTION_CHANGED_ACTION
D/WfdService( 2529): WIFI_P2P_CONNECTION_CHANGED_ACTION >> isConnected() false
W/WifiP2pStateTracker( 2529): WifiP2pStateReceiver : android.net.wifi.p2p.CONNECTION_STATE_CHANGE
D/WifiP2pService( 2529): DeviceAddress: 3a:76:f1
D/WifiP2pService( 2529): InactiveState
D/WifiP2pService( 2529): InactiveState{ what=147462 }
D/WifiP2pService( 2529): P2pEnabledState{ what=147462 }
D/WfdService( 2529): intent recieved android.net.wifi.p2p.THIS_DEVICE_CHANGED
D/WfdService( 2529): WIFI_P2P_THIS_DEVICE_CHANGED_ACTION arrived
D/WifiP2pService( 2529): DefaultState{ what=147462 }
D/WifiDirectBR( 5039): WifiDirectBroadcastReceiver::onReceive() : android.net.wifi.p2p.STATE_CHANGED
D/WifiDirectBR( 5039): WifiDirectBroadcastReceiver::onReceive() : android.net.wifi.p2p.CONNECTION_STATE_CHANGE
D/WifiDirectBR( 5039): WifiDirectBroadcastReceiver::onReceive(), Action : WifiP2pManager.WIFI_P2P_CONNECTION_CHANGED_ACTION, isConnected() == false
D/WifiDirectBR( 5039): stopServiceTest : false

try installing this modem LJ2 http://www.mediafire.com/?9wfmm51c87b2bwn

I think the problem lies in the modem/router software, it only is a problem on specific routers. I haven`t had a issue yet so far.

Flash the official stock 4.1.2 polish release that must came out. Check it out, may solve your problem!

I already tried several ways, from installing poland 4.1.2 stock ROM, same problem...
I think router is okay.. why using stock 4.1.1 ROM, wifi always working good and always getting ip address whatever i toggle on/off wifi several times..
I also already flashed modem from 4.1.1 stock rom, but still no success..
The only solutions is to copy /etc/wifi folder from 4.1.1 stock to any 4.1.2 custom rom.. I just got this solutions from someone here in this forum too..
Strange, why it happened on some devices. Why most people not suffering this problem like me..If my device has some hardware broken, why using 4.1.1 stock rom, the problem dissapeared ?

If this is the bugs on 4.1.2 ROM, we should report it to samsung, so they can fix this bugs on the next build of the ROM..
Also custom rom developer should patch their ROM to avoid this bugs..

I have same problem with 4.1.1 it is perfect, but with 4.1.2 it has same problems as yours.
---------- Post added at 02:33 PM ---------- Previous post was at 02:16 PM ----------
hendry said:
I already tried several ways, from installing poland 4.1.2 stock ROM, same problem...
I think router is okay.. why using stock 4.1.1 ROM, wifi always working good and always getting ip address whatever i toggle on/off wifi several times..
I also already flashed modem from 4.1.1 stock rom, but still no success..
The only solutions is to copy /etc/wifi folder from 4.1.1 stock to any 4.1.2 custom rom.. I just got this solutions from someone here in this forum too..
Strange, why it happened on some devices. Why most people not suffering this problem like me..If my device has some hardware broken, why using 4.1.1 stock rom, the problem dissapeared ?
Click to expand...
Click to collapse
Can you please attach the /etc/wifi folder from 4.1.1 stock??? I want to fix my wifi problem.
Thanks

hendry said:
I already tried several ways, from installing poland 4.1.2 stock ROM, same problem...
I think router is okay.. why using stock 4.1.1 ROM, wifi always working good and always getting ip address whatever i toggle on/off wifi several times..
I also already flashed modem from 4.1.1 stock rom, but still no success..
The only solutions is to copy /etc/wifi folder from 4.1.1 stock to any 4.1.2 custom rom.. I just got this solutions from someone here in this forum too..
Strange, why it happened on some devices. Why most people not suffering this problem like me..If my device has some hardware broken, why using 4.1.1 stock rom, the problem dissapeared ?
Click to expand...
Click to collapse
Yes your right . i am also facing wifi problem disconcerting in 4.1.2 .. in previous version 4.1.1 working fine

Well i dont have this problem as yours....have a stranger one lol
I have 50 mbits internet speed at home with speed of 5.2 MB/S while just on 4.1.2 speed dont cross 2 or 3 mbits out of 50 mbits while download speed is only 200 to 270 KB/S.....
Sent from my GT-N7100 using XDA Premium HD app

I've some problem with wifi on galaxy tab 3 7.0 (JB 4.1.2)
When connect using hotspot laptop or tethering via other device, my wifi always scanning every 7s. make my battery run out.
I was trying use advance setting (static IP) but still same.
How to solved this problem?

[Guide] How To Logcat

I think this one is definitely needed for this forum as i am seeing more and more users ask how to logcat. So posting this here.
Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
From Moscow Desire:
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Update for windows users:
Thank go to FuzzyMeep Two, Here's what he's posted for windows
(If you used his tool, here's his post, thank him for his work!)
Note : I am just sharing. Original post here.

Great job brother!!You are in the right path for RC :beer::thumbup:
Sent from my Galaxy Nexus using xda app-developers app

keep going on my friend...:good:

Khizar said:
I think this one is definitely needed for this forum as i am seeing more and more users ask how to logcat. So posting this here.
Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
From Moscow Desire:
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Update for windows users:
Thank go to FuzzyMeep Two, Here's what he's posted for windows
(If you used his tool, here's his post, thank him for his work!)
Note : I am just sharing. Original post here.
Click to expand...
Click to collapse
I'm happy very happy ... I have little exp with log cat this is my guide ....
Very good another user of Ak team near RC
Sent from my Galaxy Nexus using xda app-developers app

One doubt, I've downloaded catlog and make it run but I don't know where the txt files are stored or what can I do to recover them.
Also the problem I'm experiencing is a random reboot so even if I have catlog running when the reboot occurs, will I be able to recover the log or it will be lost?
Sorry for the noob question but I'm pretty lost here...

binlalo said:
One doubt, I've downloaded catlog and make it run but I don't know where the txt files are stored or what can I do to recover them.
Also the problem I'm experiencing is a random reboot so even if I have catlog running when the reboot occurs, will I be able to recover the log or it will be lost?
Sorry for the noob question but I'm pretty lost here...
Click to expand...
Click to collapse
catlog should have its own folder in data/media where it saves the txt files...

[Tutorial] How To Logcat

Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: CatLog or aLogcat
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator:
Open your terminal app;
Type:
Code:
su
logcat > /sdcard/logcat.txt
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html

Nice guide.

gonna bookmark this Thanks!

Android Auto API_UNAVAILABLE

Hi,
on latest nightly LineageOS 15.1 Android Auto crashes with "Google Play Services not working" on startup.
Log:
Code:
11-14 13:02:26.748 1107 2869 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity bnds=[440,288][640,561]} from uid 10033
11-14 13:02:26.868 1107 1183 I ActivityManager: Displayed com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity: +90ms
11-14 13:02:27.083 8728 8728 I GH.LifetimeManager: connectToCarService
11-14 13:02:27.084 8728 8728 E GH.LifetimeManager: CarService onConnectionFailed (API_UNAVAILABLE: null)
11-14 13:02:27.125 1107 5646 W ActivityManager: Unable to start service Intent { act=com.google.android.gms.car.service.START pkg=com.google.android.gms } U=0: not found
11-14 13:02:27.129 8728 8979 E GmsClient: unable to connect to service: com.google.android.gms.car.service.START on com.google.android.gms
11-14 13:02:27.130 604 604 D SurfaceFlinger: duplicate layer name: changing com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity to com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity#1
11-14 13:02:27.145 8728 8728 W GH.CarApiClientManager: connection failed: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null}
11-14 13:02:27.145 8728 8728 E GH.LifetimeManager: CarService onConnectionFailed (API_UNAVAILABLE: null)
11-14 13:02:27.183 604 604 D SurfaceFlinger: duplicate layer name: changing com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity to com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity#2
API_UNAVAILABLE sounds like I missed something to install? I'm using Open GApps Mini. Android auto menu item is also missing in settings - google - services menu.
Same setup on other devices for example HTC M8s works without problem.
Anyone seen this issue before and may help?
Edit:
Got it somehow working for now. I was in settings - google - show debug items (in top menu) - google play services modules (at the bottom) - car / car_setup. There I did check for updates nothing happened went back to GCM Diagnostics pressed disconnect, then connect, and ping nothing really happened again. Then I went back did hide debug items now Android auto menu was present and I was able to startup Android Auto without the error.
Log seems fine now:
Code:
11-17 23:26:19.848 1107 2924 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity bnds=[241,612][440,885]} from uid 10033
11-17 23:26:19.970 1107 1183 I ActivityManager: Displayed com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity: +77ms
11-17 23:26:20.187 15152 15152 I GH.LifetimeManager: connectToCarService
11-17 23:26:20.188 15152 15152 D GH.CarApiClientManager: registered listener [email protected]
11-17 23:26:20.188 15152 15152 D GH.CarApiClientManager: start
11-17 23:26:20.195 15152 15178 D CAR.CLIENT: connect [email protected]
11-17 23:26:20.212 14973 14987 D CAR.SERVICE: Package validated: com.google.android.projection.gearhead
11-17 23:26:20.215 14973 14987 D CAR.SERVICE: Android Auto has car home but both aliases are disabled. Nothing to do
11-17 23:26:20.235 15152 15152 D CAR.CLIENT: onICarAvailable [email protected]
11-17 23:26:20.236 14973 14987 D CAR.SERVICE: Registering [email protected]
11-17 23:26:20.236 15152 15152 I GH.CarApiClientManager: connected
11-17 23:26:20.236 15152 15152 D GH.CarApiClientManager: calling onConnected on [email protected]
11-17 23:26:20.247 11394 11394 D GH.CarApiClientManager: registered listener [email protected]
11-17 23:26:20.248 11394 11394 D GH.CarApiClientManager: start
Still I do not know what was causing the issue. I was always able to use Android Auto until it was broken for no reason. Maybe some strange issue while disconnecting from the car caused the car play service to crash. Nevertheless, reboot alone did not fix it. I'll report back if it breaks again in the future and maybe dump logs directly after the incident.