[Upgrading, Modifying and Unlocking] ayilm1:
I don't see this as being very likely. There are a number of problems that will need to be overcome. First and foremost is the processor type. We have no idea what the speed is. Let alone the architecture. Android requires an ARM based architecture to run with a minimum of 200MHz or so which pretty much guarantees global system lag. You'll probably have smoother performance on the proprietary OS. Not that I've used the device or anything but that's what would be expected. After all, the prop. OS's have been slimmed down to the extent that only the incorporated functions run and nothing else. Next is ram. We again are told nothing on how much memory this thing has. Barebones 'droid requires 128mb minimum to run. Storage… Here's a list of 'droid's requirements.

http://www.netmite.com/android/mydroid/development/pdk/docs/system_requirements.html

Recommended is 256MB of minimum internal storage. It says it will run on less but its not recommended. Let's push the boundaries a little. Lets say that the preston has 96mb of internal memory, which realistically should be about right. Maybe 128mb TOPS. Thats 37.5-50% of the original requirement. Even if you did get it running, where are your personal files going to be stored if you can't get the sd card slot working? In addition to that, more lag will be faced as it is a proven fact that all machines slow down if more than half the internal storage has been used.

Assuming that we got passed all of this (it'll be a miracle if we did), there are other matters that are sure to lay down a roadblock. First of all, drivers. The internal hardware of the device will need drivers written for it. That means everything like radio, bluetooth, camera, keypad, touchscreen, audio, display etc. etc. All current devices that run Android can run it because the hardware in the device already exists in an equivalent Android device. If none of the hardware in the 5600 exists in any other droid phone, drivers will need to be reverse engineered. The kernel is essential for the system to boot. It is the underlying structure on which the OS is built. If the CPU in the device is not ARM based, there is a fat chance that a working kernel will ever be built for it. And the final and probably most important reason why this will probably never work is the boot loader. Even Windows Mobile devices which currently run Android won't work without a third party loader. Hence the reason it must boot into WinMo first to load droid. The reason being is that all phone manufacturers lock the phone's boot loader to prevent it from running anything but the shipped OS. Lets say we got past this by creating a loader similar to haret that ran inside the prop. OS. You would be able to TECHNICALLY bypass the problems we would have with the stock boot loader and internal storage (that is, considering that we have established a way to enter the linux kernel). But you would still be faced with CPU compatibility issues, driver support and sufficient ram to barely run an OS as packed as Android. I will gladly give a medal and bow down to the gentleman/woman who manages the task but as I previously said, it does not seem possible.