pidcat doesn't produce any output

[delor]

system: Arch Linux 3.9.6-1 x86_64
python version: 2.7.5 and 3.3.2
pidcat version: 571826e

Pidcat doesn't produce any output. Jeff Sharkey's version works fine.

[JakeWharton]

Can you add a print(repr(line)) after each line is read and paste a few safe lines of output?

[delor]

btw Android Debug Bridge version 1.0.31

That explains a lot:

'D/dalvikvm(15466): GC_CONCURRENT freed 441K, 16% free 9877K/11719K, paused 17ms+2ms, total 41ms'
'E/SPPClientService(16783): [b] ProvMessageChannelHandler.exceptionCaught()'
'E/SPPClientService(16783): [b] exceptionCaught(). ClosedChannelException'
'E/SPPClientService(16783): [f] processError. message.arg1:1043294996,  internalErrorCode:-103'
'E/SPPClientService(16783): [b] SharedConstants.WHAT_INTERNAL_ERROR'
'E/SPPClientService(16783): [b] handleError->resultCode: PROVISIONING_FAIL(-103)'
'E/SPPClientService(16783): [b] redoProvisioning()'
'W/AlarmManager( 2113): FACTORY_ON= 0'
'E/SPPClientService(16783): [b] SharedConstants.WHAT_INTERNAL_ERROR_PENDING_TASK. message.arg1:-2'
'E/SPPClientService(16783): [b] handleError->resultCode: INITIALIZATION_FAIL(-104)'
'E/SPPClientService(16783): [b] reInitPushServerConnection()'
'E/SPPClientService(16783): [a] Connection is already disconnected.'
'E/SPPClientService(16783): [a] Connection is already disconnected.'
'E/SPPClientService(16783): [d] doProvisioningWithHandling: Alarm is already set. Return.'
'D/BatteryService( 2113): update start'
'D/BatteryService( 2113): level:33 scale:100 status:2 health:2 present:true voltage: 3883 temperature: 280 technology: Li-ion AC powered:false USB powered:true icon:17303239 invalid charger:0'
'D/ThermistorObserver( 2113): mBatteryBRForAMOLED :: onReceive(). newTemperature =280'
'D/STATUSBAR-BatteryController( 2330): onReceive() - ACTION_BATTERY_CHANGED'
'D/STATUSBAR-BatteryController( 2330): onReceive() - level:33'
'D/STATUSBAR-BatteryController( 2330): onReceive() - plugged:2'
'D/STATUSBAR-BatteryController( 2330): onReceive() - BATTERY_STATUS_CHARGING:'
'D/STATUSBAR-PhoneStatusBar( 2330): ACTION_BATTERY_CHANGED'
'D/STATUSBAR-PhoneStatusBar( 2330): NORMAL_BATTERY'
'D/BatteryService( 2113): turn on LED for charging'
'E/MtpService(18274): In MTPAPP onReceive:android.intent.action.BATTERY_CHANGED'
'E/MtpService(18274): battPlugged Type : 2'
'E/Watchdog( 2113): !@Sync 18739'
'D/dalvikvm(15466): GC_CONCURRENT freed 511K, 16% free 9869K/11719K, paused 26ms+2ms, total 65ms'
'D/dalvikvm(15466): WAIT_FOR_CONCURRENT_GC blocked 9ms'
'V/AlarmManager( 2113): waitForAlarm result :4'
'V/AlarmManager( 2113): trigger ELAPSED_REALTIME_WAKEUP or RTC_WAKEUP'
'E/WifiHW  ( 2113): ##################### set firmware type 0 #####################'
'D/WifiStateMachine( 2113): setWifiEnabled : WifiNative.setFwType(0)'
'D/WifiService( 2113): startScan: false pid=24516, uid=10013'
'W/AlarmManager( 2113): FACTORY_ON= 0'
'I/wpa_supplicant(16561): Scan requested (ret=0) - scan timeout 30 seconds'
'W/AlarmManager( 2113): FACTORY_ON= 0'
'I/wpa_supplicant(16561): nl80211: Received scan results (14 BSSes)'
'D/Tethering( 2113): interfaceLinkStateChanged wlan0, true'
'D/Tethering( 2113): interfaceStatusChanged wlan0, true'
'W/AlarmManager( 2113): FACTORY_ON= 0'
'W/AlarmManager( 2113): FACTORY_ON= 0'
'W/AlarmManager( 2113): FACTORY_ON= 0'
'E/WifiHW  ( 2113): ##################### set firmware type 0 #####################'
'D/WifiStateMachine( 2113): setWifiEnabled : WifiNative.setFwType(0)'
'D/dalvikvm( 2113): GC_CONCURRENT freed 2063K, 16% free 34027K/40199K, paused 23ms+26ms, total 329ms'
'D/dalvikvm( 2113): WAIT_FOR_CONCURRENT_GC blocked 0ms'
'D/dalvikvm( 2113): GC_EXPLICIT freed 289K, 17% free 33749K/40199K, paused 6ms+17ms, total 273ms'
'D/dalvikvm( 6003): WAIT_FOR_CONCURRENT_GC blocked 0ms'
'D/dalvikvm( 6003): GC_EXPLICIT freed 296K, 17% free 10848K/12935K, paused 3ms+6ms, total 133ms'
'D/dalvikvm(15466): GC_CONCURRENT freed 449K, 16% free 9869K/11719K, paused 14ms+16ms, total 149ms'
'D/dalvikvm( 6003): GC_CONCURRENT freed 396K, 16% free 10876K/12935K, paused 12ms+3ms, total 58ms'

[JakeWharton]

Hmmm those strings look fine. They're not unicode or binary strings either, it seems. I'll have to run through the regex's tomorrow morning and see what's causing them to not match properly.

I'm working on adding tests to prevent things like this in the future. Just need to find an hour or two of free time where I'm not chasing down bugs.

[felixb]

I've the same issue with current HEAD aka 9ca81d8.
Printing lines like above prints just the lines. Nothing strange.

[felixb]

it's working here now. maybe 064a73d fixed it.

[imlunacat]

I got same issue with eb0c5b2 .
I guess root cause is :pids would not be set if log is cleaned ( Because init message "Start proc ... " would be deleted ).

For now, I used pscommand to find out process id and add process id intopids.

P.S. kill <pid> also works!

[stephentalley]

I just upgraded from a build from several months ago and am running into this issue. ccbaa1a produces no output.

[AndrewReitz]

I tried a different phone today than my normal dev phone and am getting output now. I looked and the issue was I wasn't getting PIDs, with this new phone it would appear I do. Could these issues we are seeing be with certain phones and not the script? For reference I was not getting the PIDs with a GS4.

[JakeWharton]

Yes. It's likely Samsung devs in their infinite brilliance changed the
standard log format. It's also likely there isn't a way to support them
because of this.
On May 17, 2014 6:07 PM, "Andrew Reitz" notifications@github.com wrote:

I tried a different phone today than my normal dev phone and am getting
output now. I looked and the issue was I wasn't getting PIDs, with this new
phone it would appear I do. Could these issues we are seeing be with
certain phones and not the script? For reference I was not getting the PIDs
with a GS4.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/20#issuecomment-43428559
.

[stephentalley]

The device I'm testing against is in fact a Samsung. However, an older
version of pidcat (maybe 6 months old) works fine on that device. Shouldn't
that version also not work if it's a log format issue?
On May 17, 2014 9:09 PM, "Jake Wharton" notifications@github.com wrote:

Yes. It's likely Samsung devs in their infinite brilliance changed the
standard log format. It's also likely there isn't a way to support them
because of this.
On May 17, 2014 6:07 PM, "Andrew Reitz" notifications@github.com wrote:

I tried a different phone today than my normal dev phone and am getting
output now. I looked and the issue was I wasn't getting PIDs, with this
new
phone it would appear I do. Could these issues we are seeing be with
certain phones and not the script? For reference I was not getting the
PIDs
with a GS4.

—
Reply to this email directly or view it on GitHub<
https://github.com/JakeWharton/pidcat/issues/20#issuecomment-43428559>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/20#issuecomment-43428601
.

[AndrewReitz]

@stephentalley Can you provide me the commit for the one that is working for you?

[nschwermann]

Seems to be hit or miss on samsung devices. Sometimes it works just fine, other times there is no output. Same device, not sure if it has something to do with moon phases or what.

[delor]

With a21ee6e I no longer have this issue.

[mhubig]

See #76 for a possible solution!

[castrojr913]

Hello jake, the same issue happens me. I'm tested with Android 5.1 and a Nexus 5 .. without logs :(