yashsingh1/xdaforums huggingface dataset:
[HD2 Android SD Development] Pop45398:
New Beta Version

I think I've fixed the issues of the language differences. I'm very certain the "Start Menu" shortcut problem is solved and hope the "Storage Card" problem is also. For the former I'm now using a MortScript command for identifying the Start Menu folder. For the latter I'm now reading a registry key; the same key is used in a stock TMOUS 2.13 ROM and also Dutty ROMs based on a stock 3.14 ROM so I'm hoping all ROMs use the same key.

Initial Setup will now complete regardless if any Android builds are found but with error messages, and Sense should be re-enabled upon exit but if not it should be easily re-enabled through the Setup Menu. There's really no reason to upgrade if v2.2.1 is working for you but if you'd like to try v2.2.2_beta please report if it works for you along with your ROM version so I can post a final version on the OP.
[HD2 Android SD Development] dilari:
half

Thanks for your efforts!

I Installed the 2.2.2.beta

It did indeed give me the shortcut and I was able to run the initial setup and also enter the setup menu afterwards. So that's good.

However it still says 'no HARET.exe on this SD' and then shows me only windows as a boot option.

would it be hard to implement an option to manually point to the file ?

and would it not be possible to find/get the file and paths the same way you did in the Test script?

many thanks for helping..

Oh also sense was not automatically re-enabled, had to do it manually.

[offtopic]

b.t.w. I was looking into windows folder on the device, not the pc..It just takes forever..can those files not be cleaned up? what are they good for?
[HD2 Android SD Development] Pop45398:
Another new beta version

Give v2.2.3_beta a try. Now during installation if the SD card is not found by the name "Storage Card" a directory tree of your device will appear. Select your SD card from the tree (not your Android folder). Yours should show up as "Opslagkaart", just highlight it and select OK. The name will be saved to the RunDroid.ini file for future use. If for some reason the SD card is not found by that name during program execution the directory tree dialog will reappear.

As for those multitude of files in the Windows folder, they are required, deleting them will crash your system or at minimum screw up your display. BTW, I meant the Windows folder on the device, looking at it from the PC, that is normally very slow; if you look at it from the device it should load pretty fast.
[HD2 Android SD Development] dilari:
Allmost there

Almost,

Like you said, it displayed the folder tree, from there I highlighted the card, clicked OK, did the configurations, all done. Booted Android, perfect.

But after reboot (again), it just loads windows and wants to run the initial setup again, so I cancelled. This resulted in:

Error:

couldn't remove value in HKLM\init\Depend71

line 343

(/RunDroid\Rundroid.mscr);

RegDelete("HKLM","init","Depend" & n)

After clicking this trough, with windows selected as boot (only option), rebooted. The initial setup runs again but does not show the folder anymore. It displays the original error again > no haret.exe found...

I had autoload disabled,

[EDIT] Now after another uninstal / instal, reboot I did not get that error message, but the rest is the same, first it launches android just fine, after reboot it wants to run init setup again and is than not able to find the card. The folder tree is displayed but the card is not in it.
[HD2 Android SD Development] Pop45398:
I don't know what happened on your first install to cause those errors but I did find the same problem you encountered on the second install. The problem is when rebooting from Android the SD card is not fully initialized by the time RunDroid starts (but it is when rebooting from Windows). Saving the SD card name to the registry instead of to the .ini file has seemed to fix the problem.

The ISP here has blocked ports so I am unable to remote into my computer at home so it will be later tonight before I get home and can cab up the new version to upload.
[HD2 Android SD Development] Pop45398:
Another new beta version

One more time, let's give this one a try; hopefully the bugs due to language have been worked out.

Perhaps the next version will have the ability for the user to change the language of menu and message text.
[HD2 Android SD Development] dilari:
Thanks for your patience..no more errors !

unfortunately no boot menu either..only after clicking the shortcut.

It does load android fine, and even automatically after 10 seconds, but not @ boottime.

It just starts windows..

I would help you debug more efficiently if I knew how...
[HD2 Android SD Development] Pop45398:
Try this one. Did you try enabling AutoStart in the setup menu? Make sure you select to enable AutoStart (the default) when running initial setup.
[HD2 Android SD Development] dilari:
installed this one (2.2.5_beta)

android starts automatically. which is cool, but...while windows is starting it just overwrites it. There's no menu. I wonder how I will ever run windows again ?

Is there a way to re-configure things from within android?

To answer your question, I did enable autostart with the previous version aswell as with this one.
[HD2 Android SD Development] Pop45398:
What ROM are you running? You apparently have a program loading that is taking focus for longer than the 10 second timeout and you'll have to adjust the timeout to something longer than 10 seconds; I'd try setting it for 20 seconds or longer to test it out, you can adjust it shorter once you figure out how much time you need to still have access to the menu. To get into Windows you just have to power down, remove your SD card then power up. It may default to Windows, the Setting Menu, or nothing depending on how many Android builds you had and which was selected as default, if only one then it will default to Windows, two and the second was set as default, Settings will appear. If a 3rd or greater build was set as default then I think the boot menu will remain up. If it goes into Windows, then start RunDroid to get into the Settings Menu. Once in Settings, adjust the timeout then power down and re-insert your SD card and you should be good to go.
[HD2 Android SD Development] dilari:
superdeluxe!

Yep, that worked, supercool.

many Thanks. again, pop. :D
[HD2 Android SD Development] oxdamas:
v 2.2.5 beta working well

using artemis rom
[HD2 Android SD Development] Pop45398:
Version 2.3.1 now available

Version 2.3.1 has been posted in the OP. In addition to the changes and fixes found in v2.2.5_beta, this version allows for easy customization of text content and language. You can now customize RunDroid to your native language or just change the text that appears by editing the RunDroid.ini file. Read the documentation in post #2 or download the .pdf for instructions on customization. As always, please post about any issues.

Edit: If you customize for languages besides English please post your .ini file to share with others.
[HD2 Android SD Development] iPAQ 6515a User:
Pop45398

Let me be the first to congratulate you on your work

Fantastic Mate !!!!!

The latest release is problemless ... as the previous ones

Great !!!

PS

I have been looking for any clues on how to remap hardware keys ;)

Hera are the results:

1. A programme to remap the buttons (ie. AE Button - which I am using)

2. http://xdaforums.com/showthread.php?t=355141

Do you think there is a slight chance to obtain what we were talking (writing) about before?
[HD2 Android SD Development] Pop45398:
I haven't forgotten about the issue or given up. I found some C# code that is supposed to disable all hardware keys but I'm not at all familiar with C#, and it's been several years since I've done any C programming. I've tried compiling the code but get fatal errors. I think I may know what at least part of the problem is and will look into it when I get time. One of my sons is a Solution Architect at MS and he programs is C# quite a bit but he hasn't gotten back with me and I've been too busy to harass him any further.
[HD2 Android SD Development] iPAQ 6515a User:
Pop45398

Thanks a lot for willingness to look into the matter :D

And btw, can't believe how popular this thread has become.
[HD2 Android SD Development] Pop45398:
I forgot to mention that I had already found the thread you linked to and discovered that remapping keys in that manner will not work - notice there is no Short_Home (or Send/End). I have made some progress in compiling the C# code I found; I've fixed the most severe errors and have an idea what to do with the less severe errors, just have to do a little studying.

Yeah, I've been surprised at the popularity as well. I noticed before posting the latest version that the previous version had been downloaded well over 2000 times. I can only assume from the number of posts that most don't have any issues or have tried it and discarded but I have been a little surprised at the number of PMs. I had to ask in another thread why I was getting so many PMs from newbies saying they can't post, and found out that newbies can't post to development threads till they have a minimum of 10 posts.
[HD2 Android SD Development] downbc1:
Hi,

First, thanks for the App.

I have 2 Android build folders (one of them is renamed to a string other than "Android"), total 3 including WM6.5

When I launch Rundroid, it picks the "Android" named folder and it renames it to "Android[1]"

In the next dialog it asks me to rename the "Android[1]" back to Android.

I say yes but it doesnot rename it back to "Android"

The end result is: the original folder "Android" ends up renamed as "Android[1]"

Mutliple times I tried this, each time even though I start with a "Android" folder, it ends up getting renamed to "Android[1]".

I dont post this to criticize your app.

If you feel so, please ignore it.

Just check if you came across this problem and consider fixing it if you like.

Thanks
[HD2 Android SD Development] Pop45398:
This is not a problem, it is functioning as designed. It appears you haven't read the documentation fully and are misunderstanding the question posed. The question during setup is, "Does Android[1] build require renaming to Android?" The key word is "require," it is not asking if "you" want to rename the folder to Android. This is because there can only be one folder named Android and most builds require they be in the Android folder to work (some like Desire_DL don't, others can placed in other folders by taking additional steps during their installation. You will notice that if you answer "yes" to "Does Android[1] build require renaming to Android," once you run that build the folder will be renamed to Android instead of Android[1]. It will remain named Android until another build that requires renaming to Android is run; however, the name that appears in the menu will always say Android[1]. As the documentation says, it is best to start the setup with all builds having meaningful folder names (something other than Android), for instance RafDroid, AmeriCanDroid, MCCM, etc. If there is only one build AND the folder is named Android, that folder will not be renamed to Android[1]. I suggest that if you don't like seeing Android[1] in the menu that you rename that build's folder to something besides Android. I hope this has cleared up the issue for you.
[HD2 Android SD Development] MarkAtHome:
Hi Pop45398 -- I have a question, then.

If one uses the file startup.txt and includes a line:

set cmd "rel_path="

that is completed as

set cmd "rel_path=Android"

or

set cmd "rel_path=xyzROM"

etc. Then I would presume that if this were done, the answer would be no, that renaming would not be required, yes?
[HD2 Android SD Development] Pop45398:
Not all builds (that I know of) use startup.txt. For those that do you would probably not use it for Android as that is usually the default folder anyway. And, you would still be in the same boat as RunDroid would rename it to Android[1] during setup.

Correct; however, I have seen several posts with people having issues using startup.txt. If you want to use startup.txt you should definitely test to see if that build will start from the chosen folder before trying it with RunDroid. Frankly, with RunDroid there is no need for using startup.txt, just name the build folder anything you want (except Android) and then select "Yes" when asked if the build requires renaming.

How RunDroid works is, if a folder requires renaming it will maintain its original name until that build is started by RunDroid then RunDroid will rename that folder to Android. Once another build that requires renaming is started the current Android folder will be renamed back to original (the original name is written to the Droid.ini file in each build folder so it can be later recalled) then the new build folder will be renamed to Android.

For example, assume you have 2 Android builds in the folders, RafDroid and AmeriCanDroid, both requiring renaming. They will appear in the menu as AmeriCanDroid and RafDroid (in that order as they are listed in alphabetical order). If you run the AmericanDroid build the folder will be renamed to Android so you would then have 2 folders, one named Android and the other, RafDroid but the menu would still list them as AmeriCanDroid and RafDroid. This would remain the same till RafDroid is run. Once RafDroid is run the Android folder would be renamed back to AmeriCanDroid then the RafDroid folder would be renamed to Android. In the menu they would still be listed as AmeriCanDroid and RafDroid but if you look at the folders you would find Android and AmeriCanDroid.

This renaming process is seamless to you and occurs each time you run a different build. The only time you need to be concerned with the folder names is if you add or delete builds then run "Enable Builds" from the Setup Menu. Before running "Enable Builds" you should use a file explorer to rename the Android folder back to its original name. In the above example the Android folder would contain the RafDroid build and you would want to rename Android back to RafDroid. (By using startup.txt to use a folder name other than Android you would eliminate this need as that folder name would never change.) I always put an empty folder inside each build folder with the name of that build so I can easily tell what build is in that folder in case it has been renamed to Android and I can also simply copy that name for use in renaming the Android folder back to original. I had actually incorporated a dialog into RunDroid that allowed entering folder names but found that to be more of a hassle as the SIP (keyboard) does not always appear and is difficult and time consuming to make it appear and get back to RunDroid, and it is far easier to do from a PC when connected via ActiveSync.

I hope I made that clearer rather than more confusing. LOL
[HD2 Android SD Development] karle74:
Hi,

i use the latest version of your app. Perfectly works !

Nice job .

I made a french translation, if you want.
[HD2 Android SD Development] Pop45398:
Thanks, have linked to your post in the OP.
[HD2 Android SD Development] MarkAtHome:
Great explanation! Thanks.
[HD2 Android SD Development] spam.anonym:
hi!

is there a list where i can look which rom needs renameing and which not?

can you pls explain to me how i must set the folderstructure? cause there are some folders what i havnt created after first boot of android. do each android-rom share this folders? can i say to each rom "rename it"?

i also found a "bug". if i start "BOYPPC-SHIFTPDA GINGER Sense.s V8 (20.Apr)" first, it creats a folder named "Android". if i will start now a rom wich needs to be renamed it dont starts, only if i delete this Android" folder first, the rom wich needs to be renamed starts.

[edit01]

another thing i recognised is, some roms, f.e. "DL Desire Series v 5.x", needs that the folder has a specific name, in this example "Desire_DL". can you maybe pls integrade another option for renaming? so you have 3 choises: dont rename | rename to "Android" | custom rename. if you choose "custom rename" a inputtextbox pops out and you type your costom rename name.

[/edit01]

[edit02]

another thing i recognise is that sense dont starts somethimes.

also a "windows-class-recognition" would be nice, so the pin-question will be shown AFTER you take your rom choise, or a other possibillity would be to stop the timeout during the pin-question.

only some ideas from me ;)

[/edit02]

sry for my bad english

k.r.
[HD2 Android SD Development] Pop45398:
No, there is no list of builds that require renaming. Whether a build requires renaming just depends on the installation folder for that build. If that build requires being installed in the Android folder and you are going to have more than one build on your SD card then that build will require renaming. See the installation instructions for that particular build to determine if it needs to be in the Android folder. The extra folders that are created in the root folder may be shared by some builds but this issue has been raised several times and no one including myself has had a problem with this.

This is not a bug in RunDroid. The issue you have is due to crappy coding and crappy installation instructions for BOYPPC-SHIFTPDA GINGER Sense.s V8 (20.Apr).

Those instructions are crap! There is no Android Folder in the downloaded RAR file. In fact if you install to the Android folder it will not work without modification because the included startup.txt file sets the installation folder as GINGER_B. Without changing startup.txt you need extract all files to GINGER_B, not Android. You would then select "No" to does this build require renaming.

You are correct that this build creates an Android folder, or if there already is one, it just creates some folders and files within the existing Android folder.

My suggestion for using this build is to install and modify as follows:

1. Extract the GINGER_B folder from the RAR file to the root of the SD card

2. Extract the 2 files (rootfs.img & startup.txt) inside the SDMAGLDR(copy to Android folder).rar file to the GINGER_B folder, overwriting the existing files

3. Rename the GINGER_B folder with a meaningful name such as "BOYPPC-SHIFTPDA"

4. Edit startup.txt (you may have to copy the file to your hard drive in order to edit, depending on your OS). Change the line 'set cmdline "rel_path=GINGER_B gps_zone=us nand_boot=1"' to 'set cmdline "rel_path=ANDROID gps_zone=us nand_boot=1"'

5. In RunDroid go to Setup> Enable Builds (if initial running this will occur automatically). When prompted whether to use the BOYPPC-SHIFTPDA build (or whatever you named the folder) select "Yes" then when prompted whether the build requires renaming select "Yes"

By doing this the folders and files created in the Android folder will remain with the build.
[HD2 Android SD Development] iPAQ 6515a User:
I am happy to hear that I am not the only one.

And I know as soon as Pop45398 knows how to manage it, we will find it here :D
[HD2 Android SD Development] Pop45398:
I'm still working on it. I can lock the taskbar and Menu soft key and lock the hardware keys except for Power, which is not a problem, and Home, which is a problem. I have a lockscreen programed in C# but having problems with my program; I can only get it to enter the PIN once. I could make this work by coding RunDroid for entering the initial PIN or for changing the PIN but would rather do all of it though the lockscreen program, just have to learn more about multi-threading. But, we are still left with the issue of not being able to hook the Home key. I may end up having to program my own basic shell program.
[HD2 Android SD Development] iPAQ 6515a User:
Wow!!! It looks like you got really hooked on the idea. I wish I could help more than verbally in a written way :D

I hope you will make it .... no, wrong ... I do know you will make it happen
[HD2 Android SD Development] Pop45398:
LOL, I always love a challenge.
[HD2 Android SD Development] MarkAtHome:
Can it be themed? LOL
[HD2 Android SD Development] iPAQ 6515a User:
Well, I have also some other ideas :D

and btw, a promising thumbnail
[HD2 Android SD Development] Pop45398:
It cannot be themed as long a MortScript is used, only if converted to a Visual Studio application which will be quite some time before I become proficient enough.
[HD2 Android SD Development] mastered000:
How do this program work it boot up before WM or small program in WM?
[HD2 Android SD Development] Pop45398:
It's a WM program that is run during the init process before startup programs are run.
[HD2 Android SD Development] Szczepanik:
Portadroid SuperRAM GB

Pop - thanks for this. I found your RunDroid following a good plug from boonbing for use with his Portadroid SuperRAM GB http://xdaforums.com/showthread.php?t=1094372 which enables supported Gingerbread HD2 NAND or HTC Desire ROMs to be booted via SD card into RAM on the top of your stock WM6.5 ROM.

Thanks again!

Cheers

Tom
[HD2 Android SD Development] moises93:
How do you boot NAND Roms from SD Card? Or is it not possible? I'm all new to the HD2. :) just replaced my MyTouch with this beast of HD2! :D
[HD2 Android SD Development] moises93:
This app is amazing! Thank you! I was looking for something like this!

Would this app run on WP7 roms? If its possible that would be fantastic!
[HD2 Android SD Development] Pop45398:
I don't know if it would work with WP7 as I've never tried WP7. You might check out this thread about dual-booting WP7 NAND and Android SD: http://xdaforums.com/showthread.php?t=913815. Good luck and please report back if you get it to work, I'm sure others would be interested.
[HD2 Android SD Development] moises93:
Nope it didn't work. :( Windows 7 runs a different type of extention files rather than .cab. :(

Do you think you could port your app to WP7? :D

This is a great app! +1 for you!
[HD2 Android SD Development] Pop45398:
You can try this; I've just uncabbed the files and included MortRunners for the install and uninstall scripts. Unzip and copy the RunDroid folder along with its contents to the root of your device (not storage card) then run install.exe. You will have to also manually run uninstall.exe to uninstall.
[HD2 Android SD Development] moises93:
Will try as soon as I get home! Currently on the road! Thanks! I'll test asap!
[HD2 Android SD Development] n11:
I'm late to the party on this but now that I found it I really like it.

Thank You!
[HD2 Android SD Development] MarkAtHome:
Hi -- any chance we will see a direct port to Android? ;)
[HD2 Android SD Development] kelvinklose:
hi, Mr.Pop

thanks for the build

i've install RunDroid 2.3.1

but it cant find the android rom.(i dont know which ROM is suitable,which file should i put inside my SD card)

can u give me any example of ROM that i must put it in SD card in order to boot it?
[HD2 Android SD Development] kelvinklose:
can anyone link me the ROM that can use in RunDroid?

bcoz it cant scan any Android ROM in my SD card which i have install.
[HD2 Android SD Development] Pop45398:
I've tried quite a few SD Android ROMs and all work, a few are linked below. Do the ones you've installed work when starting CLRCAD.exe and HaRET.exe manually? Is your SD card found automatically by RunDroid or does a directory tree come up for you to select the SD card folder? If the directory tree comes up are you selecting the SD card root or selecting the Android folder? You are supposed to select the SD root, not the Android folder. Is your Android folder in the root of the SD card, i.e. Storage Card\Android, and are CLRCAD.exe and HaRET.exe in this Android folder?

http://xdaforums.com/showthread.php?t=970731

http://xdaforums.com/showthread.php?t=957652

http://xdaforums.com/showthread.php?t=950035
[HD2 Android SD Development] kelvinklose:
thanks for your reply.

let me try again first.
[HD2 Android SD Development] kelvinklose:
i think RunDroid found SD card automatically, because i dont see the directory tree upon installation of the RunDroid