Jl.JamesLaugesen

Yesterday I drained the battery on my iPhone, so the phone shut itself down like usual.

Then after getting home and plugging in to charge overnight... still nothing, the phone wasn't charging, wouldn't turn on, etc.

I thought it might be "stuffed", but obviously that's not how electronics work, so I googled for a nice fix the first result was a real good blog post.

So, just thought I'd post a quick trackback:

http://willy.boerland.com/myblog/iphone_not_charging_read_this
 

The solution is;

• switch the mute switch 4 times (up, down, up down)
• now press home and power for 6-10 seconds

Pretty cool ay.
Holding home & power for 6-10 seconds is just the regular reboot, so I wonder about toggling the mute switch 4 times... maybe that builds a tiny current? Hahaha, however it works, it's cool :-)

Using iTunes 8.2.1.6, after some unknown pattern of successful usage (maybe synced once or twice and disconnected) I am now unable to connect/sync my iPhone (with software version 3.0.1).

After connecting the iPhone to USB and a relatively long delay, I receive the error:

An iPhone has been detected, but it could not be identified properly. Please disconnect and reconnect the iPhone, then try again.

Of course this is a generic error message, so there's a good chance my following solution wont work for you.

Many people on Apple Discussions report disabling Wireless network on the computer to solve the problem:

• http://discussions.apple.com/thread.jspa?threadID=1346346
• http://discussions.apple.com/thread.jspa?threadID=1312323

Since the iPhone software version 3.0 and iTunes 8.2 have introduced tethering (which creates a new LAN interface using "Apple Mobile Ethernet Device"), it makes sense that a bug has crept in here.

Rather than "disabling Wireless", the complete solution for me is to disable all network interfaces other than the iPhone tethering LAN interface.

I am then able to sync my iPhone with iTunes, and access the internet via the iphone tethering.

Update: I have found that after iTunes has detected the iPhone successfuly, the network interfaces can be enabled, and the iPhone can still sync correctly. This is helpful since it means we can still connect to a LAN (and thus internet) while syncronising :-)

Preparing for my ~9,000km round-trip to Darwin in August, I want to have a more efficient means of tethering my laptop & iphone for occaisional net access while on the road, without wasting power running a win xp virtual machine gateway.

Obvious first/easy choice is to use iTunnel (http://www.cs.toronto.edu/~jingsu/itunnel/).

The binary included in the iTunnel version 0.0.5 tar archive is 32bit, so I need to compile my own 64bit.

After extracting the iTunnel tar to somewhere, I clean and make a new build:

cd ~/itunnel-0.0.5
./make clean
./make

But it can't compile since some libraries are missing;

gcc -Wall -g -O0 -I/usr/local/include/ -L/usr/local/lib -lpthread -lusb -lrt -liphone ./iphone.o ./itunnel.o -o itunnel
/usr/bin/ld: cannot find -liphone

I first tried tried installing the iFuse project (http://matt.colyer.name/projects/iphone-linux/index.php?title=Main_Page) to get the libiphone library:

# First add repo sources and key as per the iFuse installation page !
sudo apt-get install ifuse

But that didn't work, so I installed the libiphone-dev package (from the same iFuse repository);

# With the iFuse repos in your sources.list as above
sudo apt-get install libiphone-dev

... and itunnel can now compile :-)

Oh, I also uninstalled iFuse, since I have no need for it and it's annoying having the /media/iPhone_ mounts.

OSX has just "installed successfully" onto a QEMU image file on my laptop running Ubuntu (Intrepid).

The install went very smoothly, and the OS boots smoothly... to the grey screen of death hahaha.

After many unsuccessful attempts with Virtual Box, I found:

• An impressive QEMU/KVM patch from Alexander Graf.
• And a really good guide from d4lamar revolving around Graf's work.

I followed d4lamar's guide precisely, and everything worked smoothly.

OSX has literally only just finished installing, so I will update with some screenshots and more results later.

And of course since we all know how ridiculous Apple are, be aware that the current EULA deems running OSX on non-Mac hardware "illegal" ... for lack of a better understanding I presume ;-)

So if you want to play around with this, do like me and have a genuine OSX license, and buy a Macbook of some kind... yep.

 Now working on getting past the grey screen, woo woo.

I've recently started setting up CruiseControl.NET to run under Mono on an Ubuntu server.

The ccnet.exe process is starting successfully, and projects can be monitored from cctray.

After forcing a build, here what happens: 

[formage.jl.sg:INFO] Project: 'formage.jl.sg' is first in queue: 'formage.jl.sg' and shall start integration.
[formage.jl.sg:DEBUG] https://svn.localhost/formage.jl.sg/trunk
[formage.jl.sg:DEBUG] Starting process [/usr/bin/svn] in working directory [/home/james/public_html/ccnet.jl.sg/private/projects/formage.jl.sg/working] with arguments [log https://svn.localhost/formage.jl.sg/trunk -r "{2009-03-20T07:01:03Z}:{2009-03-20T07:17:11Z}" --verbose --xml --username ccnet --password ********* --non-interactive --no-auth-cache]
[1092073808:DEBUG] [formage.jl.sg /usr/bin/svn] [1092073808:DEBUG] [formage.jl.sg /usr/bin/svn]  [1092073808:DEBUG] [formage.jl.sg /usr/bin/svn] 
[formage.jl.sg:WARN] Process timed out: /usr/bin/svn log https://svn.localhost/formage.jl.sg/trunk -r "{2009-03-20T07:01:03Z}:{2009-03-20T07:17:11Z}" --verbose --xml --username ccnet --password ********* --non-interactive --no-auth-cache.  Process id: 21384.  This process will now be killed.

So the subversion operation is timing out, but it does appear to return correct output before timing out (the svn command does execute manually), ie: 

jameslaugesen ~: /usr/bin/svn log https://svn.localhost/formage.jl.sg/trunk -r "{2009-03-20T07:01:03Z}:{2009-03-20T07:17:11Z}" --verbose --xml --username ccnet --password ccn3t --non-interactive --no-auth-cache

No modifcations in source control... process should just move on.

So far I've just been googling with no results, and trying various configuration combinations, making sure paths are correct/exist.

I've also tried a few different ccnet versions (1.4.3.4032, 1.4.3.4044, and 1.4.1.3863) with the same result.

It's bound to be something stupid, but hopefuly someone else in the same position can find this post :-)