Volleynerd Knowledge Base |
Volleynerd's Things to Remember
Hot TopicsFirefox Extensions
DVD issues (latest)
Site Feed (Atom) Archives here
February 2016
January 2016 November 2015 August 2014 February 2014 January 2014 December 2012 December 2011 August 2011 April 2011 March 2011 February 2011 December 2010 November 2010 September 2010 August 2010 May 2010 March 2010 January 2010 December 2009 October 2009 September 2009 August 2009 July 2009 May 2009 April 2009 February 2009 January 2009 December 2008 November 2008 September 2008 August 2008 July 2008 June 2008 May 2008 January 2008 December 2007 November 2007 October 2007 September 2007 August 2007 July 2007 May 2007 March 2007 February 2007 January 2007 December 2006 November 2006 October 2006 September 2006 August 2006 July 2006 June 2006 May 2006 April 2006 March 2006 February 2006 January 2006 December 2005 November 2005 October 2005 September 2005 August 2005 July 2005 June 2005 May 2005 April 2005 March 2005 February 2005 January 2005 December 2004 November 2004 October 2004 September 2004 August 2004 July 2004 June 2004 May 2004 April 2004 March 2004 February 2004 January 2004 December 2003 November 2003 October 2003 September 2003 August 2003 July 2003 June 2003 May 2003 April 2003 March 2003 February 2003 January 2003 December 2002 November 2002 October 2002 September 2002 August 2002 July 2002 June 2002 May 2002 April 2002
|
Wednesday, January 20, 2010
Sort of equivalent to .NET Debug.WriteLine( ) import android.util.Log; sprinkle the following throughout the code Log.d( "Some Category", "blah blah message" ) Couldnt get NetBeans to show me the output. Using Android "adb" dev tool (from SDK tools dir). adb devices adb logcat Can filter output with something like the following: adb logcat XmlNode:D *:S (Above says show DEBUG output for XmlNode category, and SILENT for everything else) blog post about it here ADB documentation here Posted 5:33 PM | 0 comments | Permalink ![]() Tuesday, January 12, 2010
AVS Forum Threads for my new A/V stuff Just wanted to keep these URLs around (also have them on delicious). AVS Forum "official threads" for various devices: Posted 10:22 PM | 0 comments | Permalink ![]() Samsung 55" LCD TV (& DVR setup) Pulled the trigger on the Samsung 55" LCD tv last week. Model: LN55B640 Best Buy - $1599 This will be a post of many setup notes as I hack on setting it all up. XBox 360 Hooked it up today - I only have the component video cable for it. Do they make an HDMI cable for it? (proprietary connector on the 360 side) TV doesn't have optical IN (only OUT to a receiver). Since I don't have a receiver yet, I'm using the (white/red) audio composite connectors on the hybrid component/composite 360 video cable to send audio to the TV. Didn't think this would work, but it does. Eventually, with a receiver, I'll hopefully go HDMI from 360 to receiver, then HDMI to the TV. (worst case, I can go component + optical audio from 360 to rcvr, then HDMI to TV) For a while, was getting 720p on the TV, then finally remembered to set the 360 to output 1080p. SWEET. (Still seeing 60Hz on the tv info display, we looked it up and found that this is talking about the input side, not what the TV is outputting) No lag in picture display, even in Game Mode OFF. Tried turning it ON and didn't notice a difference. Time Warner HD DVR Cable Box Motorola DCX3400 HDMI cable to the TV. Controlling TV volume with the DVR remote. Use this site to find the code. Turn on TV, on remote: TV mode, hold Setup button (blinks twice). Enter code: 0812 (blinks twice). Test by turning off the TV with the remote. Woot. 30-second advance DVR remote doesn't have a button for this, but the functionality exists on the DVR. Just have to program a button on the remote. Lucky - the same procedure that works on the old Motrola remote works for this one too. See my previous post.
Posted 9:58 PM | 2 comments | Permalink ![]() Wednesday, January 06, 2010
WHEW - had a hell of a time today during IK RECESS building my first app for the Droid. Just some notes on what I had to do: Started here with SDK install. Which has a bunch of sub-steps. Download Eclipse, wait, need Java -- what version, and what type (EE, SE, ME)? version 6 JDK most recent, fine. Install Java, which also installs something like "update 17". Install and Run eclipse. Nope. Doesn't find a java VM. Try -vm command line arg to show it where the VM is. Nope. Now doesn't barf, but just runs, and process dies after 5 secs (no UI). Eclipse readme says compatible with Java 1.4.2. WHAT? I'm using Java 6. Go to get old version, maybe uninstall 6 and use 1.4.2? Huge red warning before download 1.4.2 --- it has passed it's "EOSL" (end of service liftetime) - back in Oct 2008. Nice. Coworker Brad says screw all that - use NetBeans. Nice - NetBeans install comes with Java (if needed), but recognizes that I have v6 patch 17 or whatever already and uses that. NetBeans IDE starts up! But ... not so fast. Move on to step 2: Android SDK Extract Android SDK, and try to run "SDK Setup" but it doesn't seem to do anything. Readme says an alternative is command line: tools\android.bat update sdk Whew - runs a UI that goes out and finds packages. Fails on https calls (expired cert? who knows - no detailed error message). Set to use HTTP instead. Get a huge ass list of packages, now we're getting somewhere. Chose them all (shouldn't have) and download. Takes *forever*. Sweet! Now we have some sub-folders under the SDK "platforms" folder that was initially empty. One for each of the Android OS levels, 1.5, 1.6, 2.0, 2.0.1 Next step: ADT plugin ADT plugin is for Eclipse, so we use nbandroid. Loose instructions here. To install the Android platform within Netbeans though, we need to point it to a "platform" folder. Now we have one of those after getting through the Android SDK components updater above. Point at the 2.0.1 platform folder. Woot! Platform installed. Create new project. Hello world. Run! ... wait ... need an emulator. Per Google instructions, use command line tool to create one. tools\android.bat create avd --target 5 --name dan_droid What is "5" ? It's the OS version target dummy. Use the following to see the choices: tools\android.bat list targets OK, created the emulator. Back in NetBeans, Run! Sweet, choose emulator ("AVD") to start. Go. ... damn ... errors in the output window that emulator is not ready. Poke around the tubes and find that you should start the emulator first. (not let the NetBeans IDE start it) Manually start the emulator \tools\emulator -avd dan_droid (dan_droid is the name of the emulator created from above) Ahh, there's a UI to manipulate the emulators too. \tools\android.bat "Virtual devices" node WOOT! After letting the emulator start and settle down, now run from NetBeans IDE -- I see my "hello world" !! In NetBeans, when debugging, to prevent getting prompted for which emulator device to use each time: Project, Properties, Run node. Set Target Device = "automatic", and select the AVD from the list (dont worry that this is the registered one whereas you want it to use the currently running one, it seems to figure that out) Posted 4:57 PM | 0 comments | Permalink ![]() Monday, January 04, 2010
Starting a list of droid apps that I either already have, want to get, or just want to remember about:
Posted 8:49 AM | 0 comments | Permalink ![]()
|