Yes I know there is Gen.Y DualBOOT out since January, 2010, a bootlauncher application for Windows Mobile. It is not designed to be used with landscape oriented touchscreen devices running Windows (Embedded) CE - as this is the case with many SatNav units. Also, for me, it is not generic enough, ex. drive names where an Android installation is searched for, are hardcoded. Hence I decided to 're-code' this bootloader in MortScript, so that each one can modify the code on the fly, if needed. I named the project 'OSLoader'.
Be aware, 'OSLoader' is only a bootlauncher application, so that you still need to provide a suitable Android on your CE device for yourself.
And, as it is with Gen.Y DualBOOT too, actually 'HaRET' is used to boot Android.
Important Note:
Besides the fact you need to provide a suitable Android on your CE device for yourself - the Android distribution that comes with 'OSLoader' only serves demonstration purposes, it doesn't make any sense to try to get Android running on Windows (Embedded) CE via 'HaRET', if you can't obtain a copy of CE's main display driver as named in HKEY_LOCAL_MACHINE\System\GDI\Drivers\MainDisplay, (perhaps using tool 'NDumpCE' by ablbd and renaming this 'ddi.dll' to 'ace_ddi.dll' ) this because 'HaRET' (at least all its current available versions I've used) expects library 'ace_ddi.dll' (a Samsung's main display driver) to be present in device's folder \Windows. Of course 'OSLoader' comes with a 'ace_ddi.dll' replacement...
'OSLoader' is still under development. It may be incomplete, may contain bugs. Please feel free to report any bugs, suggest any improvements.
Downloads: see post #2
Installation Instructions: see post #3
Disclaimer:
THE SOFTWARE AND DOCUMENTATION AND ANY AND ALL UPDATES AND MODIFICATIONS TO THEM ARE LICENSED 'AS IS.' I DO NOT REPRESENT OR WARRANT THAT ERRORS IN THE SOFTWARE OR ITS DOCUMENTATION WILL BE CORRECTED OR THAT THE SOFTWARE WILL RUN ERROR-FREE. THERE ARE NO WARRANTIES COVERING THE SOFTWARE OR DOCUMENTATION, EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF DESIGN, MERCHANTABLITY, FITNESS FOR A PARTICULAR PURPOSE, OR AGAINST INFRINGEMENT
Credits:
Mirko Schenk (AKA Mort) -> MortScript [ http://www.sto-helit.de/index.php?lang=en ]
TroNik -> CE-utilities (esp. RegFlushKey.exe)
Daniel Schumann .-> SystemInformation [ http://www.ultimatelaunch.de/index_en.html ]
Version history:
2013-08-05 Fixed some typos (thanks to bulldozerecske)
Version 0.0.4 Android-on-CE-DualBoot-0.0.4.zip MD5: 1d73ade6ac8cbc102dc603dfa8d4d66d
2012-12-27 Fixed calculation of RAM needed to run supplied Android port
Version 0.0.3
2012-12-24 Script bugs fixed (thanks to Viper The Ripper)
Version 0.0.2
2012-12-20 Initial release
Version 0.0.1
Installation Instructions:
Unpack .ZIP to root of SD-card. Run <sd-card>\OSLoader\OSLoader.exe
FAQ:
1. How does HaRET work?
As I understand it, the Android port you privide IS NOT A ROM. Hence you copy the Rootfs, Kernel and HaRet to the SD-card and run it. No flashing at all. HaRET unloads Windows (Embedded) CE and starts Android. The internal storage is mounted under Android as a normal partition. After a soft-reset (warm-boot) it returns to Windows (Embedded) CE automatically. So no flashing and no formatting with different filesystem.
2. What is the correct machine type ID for my device?
Honestly I don't know this. AFAIK a generic machine type isn't defined here. If you don't find a valuable identifier please feel free to register your device with http://www.arm.linux.org.uk/developer/machines/ and then use the machine type ID assigned.
Be aware, 'OSLoader' is only a bootlauncher application, so that you still need to provide a suitable Android on your CE device for yourself.
And, as it is with Gen.Y DualBOOT too, actually 'HaRET' is used to boot Android.
Important Note:
Besides the fact you need to provide a suitable Android on your CE device for yourself - the Android distribution that comes with 'OSLoader' only serves demonstration purposes, it doesn't make any sense to try to get Android running on Windows (Embedded) CE via 'HaRET', if you can't obtain a copy of CE's main display driver as named in HKEY_LOCAL_MACHINE\System\GDI\Drivers\MainDisplay, (perhaps using tool 'NDumpCE' by ablbd and renaming this 'ddi.dll' to 'ace_ddi.dll' ) this because 'HaRET' (at least all its current available versions I've used) expects library 'ace_ddi.dll' (a Samsung's main display driver) to be present in device's folder \Windows. Of course 'OSLoader' comes with a 'ace_ddi.dll' replacement...
'OSLoader' is still under development. It may be incomplete, may contain bugs. Please feel free to report any bugs, suggest any improvements.
Downloads: see post #2
Installation Instructions: see post #3
Disclaimer:
THE SOFTWARE AND DOCUMENTATION AND ANY AND ALL UPDATES AND MODIFICATIONS TO THEM ARE LICENSED 'AS IS.' I DO NOT REPRESENT OR WARRANT THAT ERRORS IN THE SOFTWARE OR ITS DOCUMENTATION WILL BE CORRECTED OR THAT THE SOFTWARE WILL RUN ERROR-FREE. THERE ARE NO WARRANTIES COVERING THE SOFTWARE OR DOCUMENTATION, EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF DESIGN, MERCHANTABLITY, FITNESS FOR A PARTICULAR PURPOSE, OR AGAINST INFRINGEMENT
Credits:
Mirko Schenk (AKA Mort) -> MortScript [ http://www.sto-helit.de/index.php?lang=en ]
TroNik -> CE-utilities (esp. RegFlushKey.exe)
Daniel Schumann .-> SystemInformation [ http://www.ultimatelaunch.de/index_en.html ]
Version history:
2013-08-05 Fixed some typos (thanks to bulldozerecske)
Version 0.0.4 Android-on-CE-DualBoot-0.0.4.zip MD5: 1d73ade6ac8cbc102dc603dfa8d4d66d
2012-12-27 Fixed calculation of RAM needed to run supplied Android port
Version 0.0.3
2012-12-24 Script bugs fixed (thanks to Viper The Ripper)
Version 0.0.2
2012-12-20 Initial release
Version 0.0.1
Installation Instructions:
Unpack .ZIP to root of SD-card. Run <sd-card>\OSLoader\OSLoader.exe
FAQ:
1. How does HaRET work?
As I understand it, the Android port you privide IS NOT A ROM. Hence you copy the Rootfs, Kernel and HaRet to the SD-card and run it. No flashing at all. HaRET unloads Windows (Embedded) CE and starts Android. The internal storage is mounted under Android as a normal partition. After a soft-reset (warm-boot) it returns to Windows (Embedded) CE automatically. So no flashing and no formatting with different filesystem.
2. What is the correct machine type ID for my device?
Honestly I don't know this. AFAIK a generic machine type isn't defined here. If you don't find a valuable identifier please feel free to register your device with http://www.arm.linux.org.uk/developer/machines/ and then use the machine type ID assigned.
No comments:
Post a Comment