[Nook Color General] tekchip:
I've actually engaged OpenFeint themselves through their support and they've been as helpful as they can be considering it isn't an officially supported device. Here's what I got.

My LogCat is attached which they requested and actually looked at.

Here's what the thread looks like.

Is there any chance you could tell me what other resources feint depends on? I know you can call resources from other apps so feint must require something that isn't available on the Nook Color's version of Android.

Feb-04 2011 13:08

Erwin

OpenFeint

Hi,

Feint depends web-related components such as webView and Apache...so if the Nook version doesn't have it it will error out.

-Erwin

Regards,

Erwin

Feb-04 2011 16:22

Tekchip

Odd, I know the NC has a Browser.apk installed. It's not clear if it's the original or not so that shouldn't be the problem. I don't recall seeing an org.apache.http but it must have one as the Android docs http://developer.android.com/reference/org/apache/http/package-descr.html indicate it's necessary for http communication to happen at all. Ideas? Is there anything I can run/do to gather more information about the problem?

Feb-04 2011 16:32

Tekchip

I see webView is a default function with in Android so if it's running android, and has a browser it should have webview. I imagine the hang up is on this Apache piece. Doing a quick search I found a package called org.apache.http. It appears to be a package but I don't find any apks out there. I also don't see an installed apache APK's on my phone(droid 1 running 2.3).

Feb-04 2011 16:42

Erwin

OpenFeint

Hi,

We'll take a look to see how it works but we currently don't support the device so there are no guarantees. Let me know if you need help with anything else.

-Erwin

Regards,

Erwin

Feb-04 2011 17:21

Erwin

OpenFeint

Can you connect it to a computer with the Android dev tools installed, run the Feint Game Spotlight app up until it hangs, and run adb logcat on a connected computer and send the output?

Regards,

Erwin

Feb-05 2011 07:49

Tekchip

I do have adb access to do that however I am out of town with nothing but my mobile available so I won't be able to get that info for you until 7 Feb.

Feb-05 2011 12:59

Tekchip

Here is the log cat from running Feint Game Spotlight. I captured this using a logcat app that has some settings to get more fine grained information so hopefully it didn't exclude anything important. I couldn't get it to replicate but earlier on I saw an error that indicated a cache directory could not be created. From there on it throws this set of errors that appear is if it's simply timing out. I'm going to try to re-create the original logcat entry I saw that in.

W/InputManagerService( 836): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@4a14c430

I/ActivityManager( 836): Starting activity: Intent { act=com.encore.intent.action.jump flg=0x14400000 cmp=com.bn.nook.applauncher/.jump.JumpActivity }

V/alogcat ( 8979): save instance

V/alogcat ( 8979): paused

D/DeviceManagerBroadcastReceiver( 1070): action (com.bn.devicemanager.ACTION_DEVICE_USAGE)

I/DeviceManagerHandler( 1070): HandleMessage(): msg.what (7)

I/ActivityManager( 836): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.aurorafeint.spotlight/.SpotlightActivity }

V/WebUI ( 7963): --- WebUI Bootup ---

V/WebUI ( 7963): Loading URL: file:///data/data/com.aurorafeint.spotlight/files/webui/index.html

W/InputManagerService( 836): Starting input on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@4a0f6730 (uid=10002 pid=1398)

I/ActivityManager( 836): Displayed activity com.aurorafeint.spotlight/.SpotlightActivity: 1548 ms (total 3033 ms)

D/alogcat ( 8979): stopping ...

W/InputManagerService( 836): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@4a0371b8

D/alogcat ( 8979): stopped

D/WindowManager( 836): interceptKeyTi code=4 down=true repeatCount=0 keyguardOn=false mHomePressed=false

D/WindowManager( 836): interceptKeyTi code=4 down=false repeatCount=0 keyguardOn=false mHomePressed=false

I/NotificationService( 836): enqueueToast pkg=org.jtb.alogcat callback=android.app.ITransientNotification$Stub$Proxy@4a12d1f0 duration=1

D/alogcat ( 8979): stopping ...

D/alogcat ( 8979): starting ...

D/alogcat ( 8979): canceling periodic saves

V/alogcat ( 8979): started

V/alogcat ( 8979): resumed

D/dalvikvm( 8979): GC freed 2923 objects / 399720 bytes in 131ms

D/webviewglue( 7963): nativeDestroy view: 0x422cd0

D/dalvikvm( 7963): GC freed 4907 objects / 509912 bytes in 100ms

D/dalvikvm( 1398): GC freed 920 objects / 65960 bytes in 144ms

D/WifiService( 836): ACTION_BATTERY_CHANGED pluggedType: 0

D/DeviceManagerBroadcastReceiver( 1070): action (android.intent.action.BATTERY_CHANGED)

D/twcCurrentConditions( 1249): updateLoc:52002

D/twcCurrentConditions( 1249): no need to pull any data:52002

D/WifiService( 836): ACTION_BATTERY_CHANGED pluggedType: 0

D/DeviceManagerBroadcastReceiver( 1070): action (android.intent.action.BATTERY_CHANGED)

D/WindowManager( 836): interceptKeyTi code=82 down=true repeatCount=0 keyguardOn=false mHomePressed=false

D/WindowManager( 836): interceptKeyTi code=82 down=false repeatCount=0 keyguardOn=false mHomePressed=false

Feb-09 2011 08:27

Erwin

OpenFeint

Hi,

We couldn't find anything obvious from the log output so we'll need to get our hands on a device to check it out. Thanks for the info!

Regards,

Erwin

Feb-09 2011 10:26

Tekchip

Erwin,

I don't think the logcat app I used had the right filtering. I'm going to try to get it hooked up to my PC with real ADB access and do a raw logcat. Been busy lately so I had to try to use the shortcut method to get some output. I'll drop the info as soon as I get it. I appreciate your patience in working with me!

Brock

Feb-09 2011 10:45

Tekchip

Got it! This shows everything and it appears to be obvious where the problems are. I can't decipher it my self but some things are not able to be loaded etc. and it can't seem to locate the sdcard. I hope this helps!

logcat.txt

Feb-09 2011 13:38

Erwin

OpenFeint

Here's the latest on that from our Android guru:

So, the 'unable to access /sdcard' is actually expected, and doesn't indicate a problem...

However, the "unable to create webviewCache directory" is something I haven't seen before. That error message is actually coming from Android OS instead of our code. I've googled around a bit and it looks like this seems to happen on some rooted devices when they open the Browser. Most of the hits I'm finding are from the HTC Desire. Here is a quote from the only person I can find who seems to have fixed it:

"EDIT: Update - now fixed after repairing ext filesystem on the sdcard and repairing uid permissions from the receovery partition."

Hope that helps

Regards,

Erwin

Feb-09 2011 14:06

Erwin

OpenFeint

Google: 'fix apk uid permissions' in amonra recovery

That might help/might not...but keep in mind we can't officially support

Regards,

Erwin

Feb-09 2011 14:19

It looks like the red highlighted text is the fix. I haven't had a chance to try it using Amonra's recovery. I did try a fix permissions from clockwork but to no avail.