Database Users

Useful Information for people new to XDA and Windows Mobiles

My first post.
First of all to all the seniors, gr8 forum u guys got here.
Second, it's got so much information I cant make head or tail of anything
I am going to be purchasing a HTC P3400i WM 6.0 version soon, most probably in the next week or so.
This is the first time am going to be using a WM device so I was trying to get a feel of things by reading through the posts here.
I have few questions,
1. What exactly is a ROM, why is it called so and will it void my warranty?
2. I understand it is possible to give the p3400i a "touchflow" look can i do it w/o using a "ROM".
3. When using a WM device what are the basic things that one should learn/understand/take care of??
4. Which posts should I go through and what order to understand the whole concept of WM devices, without actually experimenting with my own device.
5 Finally thanks in advance looking forward to your replies and guidance.
P.S: I sincerely hope my post is in the correct section, coz a lot of my questions are of the "General" category.

1. ROM is actually "Read Only files in your pda" ... Its actually the OS and its files running on your gadget........The default OS in p3400i or gene100 comes with lot of junk files and drivers and the RAM will not be sufficient to run all the new Programs....SO dvlpers are cooking faster ROMS than the default one by modifying these files and drivers..... also they make use of files from other faster devices.....YEs it will void your warranty... But normally all the software issues can be rectified.......
2.YEs u can give ur pda touch flo without using by softwares like.......M2D , SPB Mobile shell, Pointui......etc...etc.... But it will faster it will be better if its in a ROM....
3. There are many things.....one advice.....do a research before doing anything stupid on your device,...... Ask lot of questions and doubts...... dont get ur device bricked......
4.Read the Sticky Thread by Sumit before flashing........

Great answer go4thomman Here are my views :
1. A ROM actually is an image, much like images of CDs you create with burning software. It contains the Windows Mobile Operating system, Drivers to run your device as well as Manufacturer made programs to make the best use of device. All these things are packed into a single file, much like you do with zip files. Your phones contains 128 MB of memory for putting things on it. So to provide base functionality to the device, this ROM is written to that memory and that portion is made read only so that things like viruses (and humans ) don't mess around with the important files. The concept of ROM is there only to make this process simpler, as you don't have a CDROM drive in your mobile to pop a cd and install OS into it. Also a phone is expected to come in ready to use condition, not like a computer. So a ROM provides all the software related functionality to your phone. After that, rest of the remaining memory becomes your phone memory.
Device Manufacturers don't allow making custom roms and flashing them to phones as it makes it difficult for them to provide support. So they lock the device using their digital certificates as protection. This locking is done in the special part of the phone called the SPL (Second Program Loader) and the lock is called CID (Carrier IDentifier). SO to unlock the phone, you need to install a SPL that is CID unlocked but this is against the warranty policy of HTC or any other manufacturer for that matter. Plus the process is dangerous and if not done properly can make your device non functional, non booting also called a "Brick" coz the only thing you can then do with it is using it like the one
Fortunately, we have some really good people here who have developed safe unlocking methods as well as unbricking solutions for certain situations (but not all). Two such people that have worked for GENE SPL are Olipro (old gene) and Orefkov (new gene).
For more info regarding this and to know how to do it, ready the sticky post by me.
2. Touchflo refers to two things, Finger scrolling in applications and the Manilla 2D interface. Finger scrolling is something that you will find in recent versions of Windows Mobile OS. So if you upgrade to newer ROMs you will get it. There is also a 3rd party driver available called FTouchFLO but the older versions have problems and newer are not free.
The Manilla 2D interface, which HTC calls TouchFLO in its specs but manilla inside the ROM, is a Today plug in that allows accessing most of the phone functions without going through the usual Windows Mobile OS menus. This plugin is great, looks cool and works nicely. But its disk and ram footprints are quiet large. so HTC only uses it with devices which have 256 MB flash memory and 128 MB of RAM. It is possible to use this plugin on GENE but using it from phone memory is not recommended as it is way too slow that way. When it is cooked into the ROM, it takes half the space as ROM files are compressed and runs smoother. Cons of this plugin are that it acquires all of the screen space so you cant use any other plugin with it, it doesn't even allows to enable any other plugin, It hogs considerable amount of RAM, Decreases the battery backup by 5%, and is not easily customizable.
3. There is not much special you have to do to take care of this baby, its quiet sturdy. But do keep these things in mind:
a. Discharge the battery fully atleast once a week.
b. Use a good quality screen protector with the screen, never ever do cold lamination on the screen, it damages it. Also replace the protector every 6-8 months or so.
c. Avoid hard tapping on the screen, its quiet sensitive and if its not responding, its probably because software is hanging. Dont hit your hardware for that
d. Keep it away from liquids, get cold lamination on the rest of the body to avoid scratches.
e. Keep the volume at a point less than full, speaker sounds good that way.
f. Keep brightness and power settings to the minimum that you prefer, to save battery.
4. This is a forum not a book so i cannot recommend you any particular order, but do read things related to flashing and cooking as well as the threads related to ROMs in the gene section. Wiki is also a good place to learn things, as well as do keep an eye on General Discussions and Development and Hacking section for getting important information and software upgrades.
Always Search before you start a thread or be ready for flaming, respect other members, never demand things as you are not paying for anything and nobody owes you anything, And read thoroughly and between the lines before attempting anything with your phone.
Good luck!

One more thing, rename this thread to "Useful Information for people new to XDA and Windows Mobiles". That way, i guess i wont have to type it all again. You can rename you threads by double cliking besides the title of the thread in the list of threads.

Thanks a lot guys.

[PRJ][AND][LNX] OPANDROID (The Wing-Linux Opal branch)

Please, don't reply with a quote of this post.
Wing Linux​
This thread is a continuation to what happened in the LINUX BOOTS at OPAL! Thanks to linwizard project! thread. I thought it's about time a proper thread is made to get this project the attention it needs.
What is Wing Linux all about
Wing Linux aims to bring Linux and Google's Android operating systems to OMAP850-based devices.
Wait, did you say Linux AND Android?
Yep, you did read that right. If you're running Wing Linux, you are simultaneously running Ångström and Android on top of that. That means you get all of the cool Linux functionality with the intuitive interface and usability of Android.
For more information about Wing Linux please visit the official site. It'll save you from having to read through this whole thread
If I installed Wing Linux, will I lose WM? / Will this brick my device?
No. There's no flashing involved here. Still, it's best practice to have thing backed up before doing anything. I've heard of a few cases were people lost some files from there SD cards.
Great! How can I try this?
I'm glad you asked!
Installation is very easy and smooth, all you have to do is following these simple steps:
Navigate to the Wing Linux site.
On the navigation menu to the right of the main page, you'll find a "Download" link. Obviously, you're supposed to click it
Once the download completes, you'll end up with a zip file that contains a few cab files and 4 text files. Please do open these files using notepad for a quick look. They contain plenty of useful information.
After extracting that zip, and hopefully taking a look at the text files, you'll need to move two of the cab files to your device: rootfs and opal.
From your device, install the two cabs (navigate to them using your favourite file explorer then click them) and make sure to install both files to storage card.
Before proceeding any further, make sure that you still have at least 250MB of free space on your storage card. If you don't then you'll need to do some clean up before you can continue.
Also, make sure to close any open application, otherwise you'll lose any unsaved progress in any of them.
Open the brand new wing-linux short-cut in your start menu.
Hit run.
While Linux is booting up. You'll be asked to input a size for the image file used as storage for Wing Linux (consider it like virtual hard disk). Don't touch anything and just wait, default value (250MB) will be used after a couple of seconds.
Grab yourself a cup of coffee/tea/beer/... then sit back and relax. Installation will take a while.
When everything is over, you'll get a calibration screen. Try your best to get a good calibration on the first time as fixing it later takes some work.
Enjoy Android
Key-map for Android
As the Opal doesn't have that many keys, some changes had to be made:
D-Pad + Centre: works normally.
Green: Dialer.
Red: Default behaviour under Android is like this:
Short press: puts device in standby. This can be changed in the settings (which I recommend).
Long press: Display menu to turn off device, put device in airplane mode...
Volume Up: menu key (it's the key that unlocks the screen as well).
Volume Down: back/cancel.
Power button: It's working, but it doesn't do anything because it's functionality doesn't work in Android yet.
Okay, I'm done playing around and I want to go back to WM.
That's easy:
Click and hold the red button and you'll get a menu.
Select "Shutdown" and the phone will reboot.
Once the phone boots again, you'll be in WM.
I want to completely get rid of Wing Linux
Eh, it's your loss.
Un-install both cabs as you would do for any application.
Check if there's still a folder called "linux" in the root of your storage card.
If there's one, delete it.
What works and what does not work:
For details look at this page here. In short:
For the time being, these stuff work:
Making/receiving calls, although you won't be able to hear the other side during phone calls. But there's a small workaround for that:
When in windows mobile, start Wing Linux during a phone call, that way you'll have sound in Android during calls.
Sending/receiving SMS.
GPRS also works. If your carrier/service providers details are included already, it'll work out of the box. Otherwise you'll need to set up a new APN under settings.
For the time being, these stuff do not work:
Battery (will always report it's 100% full).
Bluetooth
WIFI
Camera
Sound (other than what you'll get with the workaround)
Vibration
LED notifications
Standby/Suspend mode.
Unlocking SIM (Android will accept the PIN code but it won't connect to network, you'll need to disable PIN from WM).
FAQ
Q: When I let the phone sit for a while it goes to a text screen that just rolls android_power_suspend messages?
Right now these message are normal, just hit any key or the screen to go back. The suspend portion of Android is being actively worked on so just hang tight!
Q: I installed and booted Wing Linux and when I attach it via USB to my Windows computer it asks me for a driver for an "Ethernet Gadget". Where can I get this?
Linux has this driver natively. For Windows, there's no driver right now, if you know where we can find one (that is free to distribute legally) please do share it with us.
Q: When I boot for the first time the installer hangs at partitioning 0%, is it not working?
Walk away from your phone, this part will take some time. It will only have to do this on initial install so have faith.
Q: Can I install this to my phone's internal memory?
Not presently. Although the cab file will install, you won't be able to boot from internal memory. Ensure you install to your storage card.
Q: Does this run emulated under Windows Mobile?
Not at all! Although it's started from inside Windows Mobile, HaRET completely replaces Windows with Linux in memory, so you actually are booting native Linux -- No emulation at all.
Q: I successfully entered my PIN and unlocked my SIM card through Android, but I can't get on the network. Why?
This is a known issue -- unlocking a SIM card works, but Android does not follow through with connecting to the network. The best solution to this for now is to remove the PIN from your SIM card.
Q: I opened an application but how to I get back to the main page or quit the program? Where is my back button?
Check the keymap posted above.
Q: When will X work on Opal?
In due time. The project is made of volunteer effort working in their spare time. If you'd like the development to speed up, feel free to give a hand!
Not every single one of the people working on this is a developer. Some, like me, are learning as they go. And none is able to dedicate all his time for this project.
Q: I messed up with the calibration. How can I re-calibrate the screen?
Go to storage card, then go to the folder called 'linux'. You'll find a file called default.txt
In that file, look for the line that says "set CMDLINE", add "reset_ts" to it (between the two quotations). Then boot normally.
Remember to remove that once you're satisfied with the calibration.
(If Microsoft Word asks you to save it in their format, always say no)
Q: I waited a lot but the device won't finish booting after installation. What should I do?
First of all, try resetting the phone and booting Wing Linux again. In most of the cases, this'll work. If that doesn't work, try deleting the "rootfs" file from "/Storage Card/linux". If you don't see that file, delete rootfs.img instead. Then boot back in and it should start installing from scratch.
If you're still having issues, remove everything (refer to the "I want to completely get rid of Wing Linux" section) and reinstall the two cabs.
Q: What version of Android is Wing Linux running?
Right now, it's running Cupcake (1.5). An upgrade is planned.
Q: What version of Ångström is Wing Linux running?
Latest as of time of posting.
Q: I'm trying to use the virtual terminal but the enter button on the virtual keyboard won't do anything. Is that normal?
It happens occasionally. Try pressing the d-pad in various directions then hit then enter button again.
Q: Can I SSH to the phone?
Yes you can
Code:
sudo ifconfig usb0 10.100.0.2 up
ssh [email protected]
The password is "wing".
Q: Is installing to a dedicated partition supported?
Yes it is, for more information check the 'INSTALL' file included in the zip, and that can also be found under /storage card/linux
Q: How can I set up a development environment to help with coding?
Take a look here.
Q: How can I get in contact with developers?
Through this thread, the project's forums and on the IRC channel at #wing-linux on Freenode.net. Please, do not use E-Mails, PMs, IMs...
Personal thanks from me to the following people for making this a reality:
darkstar62 for being the main man behind the whole project. And for going easy on me despite my noobness
The people at Linwizard for creating the base kernel and helping throughout development.
kshaurya for helping me to get the Opal branch started
raditzgds, life02 and zenned for helping to get the touchscreen working on Opal.
HTC for this nice device.
Google for Android.
The people behind Ångström for the base system.
I hope I didn't forget anyone...

Please, don't reply with a quote of this post.
Release Informations
Released Versions:
0.1 released on 2009-02-16
0.2 released on 2009-05-26
0.3pre3 released on 2009-06-14
0.3 released on 2009-06-16
0.4pre1 released on 2009-07-04
0.4pre2 released on 2009-07-25
0.4pre3 released on 2009-08-12
0.4pre4 released on 2009-08-12
0.4 released on 2009-11-09
0.4.1 released on 2009-11-19
0.4.2 released on 2009-11-21
Planned Releases:
Nothing is currently set in stone. Next release can be either 0.4.3 or 0.5.
Things to look forward for in the next release.
Hopefully: Sound and there might be some changes concerning Android.
Latest Change Log:
Will be updated on next release.

Please, don't reply with a quote of this post.
How to help with testing and development on Opal:
The people behind Linwizard and Wing-Linux are in need of the results of running this test:
ali1234 said:
Hi,
Thanks to everyone who came to our sprint and tested things. We got a
basic kernel booting on several platforms.
After looking at the results I started to look at the LCD detection
code. I would like to ask everyone to run this test and send me the
results.
I need testers with any omap7xx phone. You only need to run a haret
script and mail me the output, no kernel boot in necessary. The test
scripts are here:
http://al.robotfuzz.com/~al/htc/lcd1.zip
You need a modified version of haret which is included. Unpack the zip
to the phone's internal memory and run haret. Press the "boot" button
like normal. It won't boot linux, it will run the tests instead. Your
screen will flicker during the test, it is normal. It will generate
lcdlog.txt. Mail that file to me or the list, along with any
information you have about your phone. Especially if you have an
after-market LCD, or you know what model of LCD you have for another
reason.
The test works by rapidly switching between LCD mode and GPIO mode on
the LCD controller pins, to check which pins are tied high, low, or
are floating. It does this 30 or so times. Any pin that changes value
is deemed floating. The others are tied high or low (1 or 0). Ignoring
floating pins (zero them) and you get a code which identifies the
panel type of the phone.
More about the LCD detection, including device database and log
processor: https://sourceforge.net/apps/trac/linwizard/wiki/LCDDetect
Thanks
Click to expand...
Click to collapse
While the quote tells you to email the results to ali1234, it would be best if you PM them to me and I'll handle passing them forwards.

Very nice thread with all the info needed
musikmonk that rom is ready contact me today eve or tom i will send u... then u can do testing works.

good discription brother........
i have tried it out already....but sound wifi etc not working.....hopefully the developers will solve the problems in next build....

indresh88 said:
good discription brother........
i have tried it out already....but sound wifi etc not working.....hopefully the developers will solve the problems in next build....
Click to expand...
Click to collapse
I guess you dont know that musikmonk himself is one of the developer of android for omap 850 devices

i downloaded it from the web to my mobile...took me a couple of hours but was worth it.
installation was a breeze.
wifi is not a necessary for me...so i am okay with it...
there are some probs tho...like the battery percentage...it is stuck at 100%. even after fiddling with it, it remained the same.
i rebooted to wm to find that battery was about 45%. this issue is critical...i feel. what about you guys??
btw...my sincere thanks to all who toiled so hard...without getting paid...to port this amazing os.
hats off to you guys...and do keep up the good work.

i'm testing android from some week
i test version 0.4.2 and the 0.4.3 pre4
bluetooth don't work... when I turn on the bt the scrren increase brightnees...
for the audio problems if you start winglinux during a call audio works
now i want try your kernel

jagan2 said:
I guess you dont know that musikmonk himself is one of the developer of android for omap 850 devices
Click to expand...
Click to collapse
Thanks But I'm still faaaaaar from being a developer. I'm just learning.
freelancer81 said:
there are some probs tho...like the battery percentage...it is stuck at 100%. even after fiddling with it, it remained the same.
i rebooted to wm to find that battery was about 45%. this issue is critical...i feel.
Click to expand...
Click to collapse
Ah, I forgot to mention that . I added it to the not working section now.
Right now, wing-linux is using a fake battery driver that always reports battery as 100% full. There's still no working driver and I'm afraid that it might be a long time till there is one.
gp.triple said:
i'm testing android from some week
i test version 0.4.2 and the 0.4.3 pre4
bluetooth don't work... when I turn on the bt the scrren increase brightnees...
for the audio problems if you start winglinux during a call audio works
now i want try your kernel
Click to expand...
Click to collapse
Please do try that kernel and tell me how it goes for you.

nice work MusikMonk, i m so happy to see development for android on our phones
Bluetooth works on mine, but not all the time(once in 10 it doesn't)
Thank you so much for sharing your work
Edit: Sometimes,network problems occur after changing kernel

i try your new kernel
now when i start bluethoot its start
but don't discovery my sonyericsson w950i
and the s.e. don't find the opal
but the opal find other device...
soon as possible i try to connect other device and give you some feedback
i hope that you can understand my bad english
one question...
it is possible tu build the kernel 2.6.30 or successive?
its contains more driver

mrushabh said:
nice work MusikMonk, i m so happy to see development for android on our phones
Bluetooth works on mine, but not all the time(once in 10 it doesn't)
Thank you so much for sharing your work
Edit: Sometimes,network problems occur after changing kernel
Click to expand...
Click to collapse
Can you please tell me what you tried for bluetooth? I could use some details.
And about network problems, that's normal. It randomly happens with wing-linux, it isn't something specific to that kernel.
Most of the times switching to aeroplane mode and back works. Sometimes you'll have to reboot.
gp.triple said:
i try your new kernel
now when i start bluethoot its start
but don't discovery my sonyericsson w950i
and the s.e. don't find the opal
but the opal find other device...
soon as possible i try to connect other device and give you some feedback
i hope that you can understand my bad english
one question...
it is possible tu build the kernel 2.6.30 or successive?
its contains more driver
Click to expand...
Click to collapse
Does it always find that other device or does it only find it sometimes?
About using a new kernel, there are some problems with that. darkstar62 is working on moving upstream to latest kernel and he submitted some patches to the linux-omap tree to get his device (Herald/Wing) supported some were accepted, others are pending.
I tried these patches on Opal but memory card and usb didn't work. I'm waiting till the patches are complete to try again because, right now, I don't know how to fix them myself. I had a couple of ideas that I tried, but none worked.
Oh, and your English is okay. I can understand you fine.

MusikMonk said:
Does it always find that other device or does it only find it sometimes?
i had few time to try this morning
one time bt start and find some device
one time bt don't start
and one time bt start but don't find any device
as soon as possible i'll do other test
Click to expand...
Click to collapse
Click to expand...
Click to collapse

im glad the network problem is not related to the kernel..
as for the bluetooth, it can find my other phone but somehow cant connect with it, also when set to discoverable also no other device finds it

Thank you all I really appreciate your help with testing.
If you guys have the time, can you also give this kernel a test:
http://dl.dropbox.com/u/1944361/zImage-09-02-10
Edit:
Oh, and can you please give me details such as:
What was the bluetooth state in WM (off/on/hidden/discoverable)?
If you're using WM6.5.x, does bluetooth work normally on the rom you're using? (There seems to be many customized roms with bluetooth problems)
When you searched from Android, if some devices are found, do the name appears or only the address?
Stuff like that...

nice ...work
nice work thank u .
i have test the OS but there are some problem , that i cant make a call and
i cant but it on sleep mode and some time Bluetooth does'nt work .
but until now it's great to see the android work on our mobiles .
.

MusikMonk said:
Thank you all I really appreciate your help with testing.
If you guys have the time, can you also give this kernel a test:
Edit:
Oh, and can you please give me details such as:
What was the bluetooth state in WM (off/on/hidden/discoverable)?
If you're using WM6.5.x, does bluetooth work normally on the rom you're using? (There seems to be many customized roms with bluetooth problems)
When you searched from Android, if some devices are found, do the name appears or only the address?
Stuff like that...
Click to expand...
Click to collapse
i did other test
at first i use the original wm6.1
condition of test
wm bt on/discoverable ---> android don't start bt
wm bt of ---> bt start in android, only one time find other device but appears only the adress, the other device don't find the opaldroid
if i can this evening try the new kernel

Results with the new kernel
Rom used:Official HTC WWE Rom
Bluetooth state in windows mobile:Off
Bluetooth activates and can be set to discoverable but no device can find phone and phone cant find any device
VERY RARELY IN THIS STATE IT CAN FIND MY MAGIC MOUSE
Bluetooth state in windows mobile:On
Same as the one before but no rare luck here..(Bluetooth activates and can be set to discoverable but no device can find phone and phone cant find any device)

hi;
Please take a screen shot from your device and put them there!
thanks.

i did some test whit the new kernel
win 6.1 standard rom
bt off in wm---> sometimes find other device showing the adress but other device cant find opal
bt on in wm--->didn't find other device and other device cant find opal

Android 2 on the Omnia 2?

Okay, first post, I apologize if I've broke a rule. And I didn't see this question anywhere. So... Is there any way to use Android 2.0 on the Omnia II? I don't really like Windows Mobile and wish I could replace it. Thanks.

Perhaps in the near future.
Two phones have similar hardware to the Omnia II: first is the Samsung Moment and the next is the Samsung Beam.
The three share the exact same CPU and only the latter differs in RAM; the beam has 384mb ram but this is probably because it also sports a projector and I assume it is going to be a very resource intensive app.
Both the Beam and the Moment (well at least the Sprint version) will eventually have Android 2.1 on there. If someone still has an interest in this old device which seemed to have so much support and potential behind it only 4 months ago they may decide to get the software from that phone and do a few tweaks to have it running on the Omnia II.
There presently is an Android on Omnia dev but the fact is he is going to have a really hard time porting Android on a device which is quite different to anything current on the market now (the Armv6 instruction set is quite dated). Hopefully he moves onto porting instead of building from the ground up like he is doing now, though he may elect not to because he has probably done a lot of work. IF he or someone else ports it will be a very good Android phone, if it is built from the ground up i have a strong feeling it will lag and crap out worse then the Omnia 2 with Samsung BloatWiz on it right now.
=====
In my opinion Modus Windows Mobile is not the issue, it is Samsung. They have a very poorly coded user interface called "Touch-Wiz". All you need to do is go into the My Menu, Find "settings " > click "Display and Light" > click "Items on Today" > scroll down and go to the Samsung widget plus and untick the box > Now go to the very bottom and just tick "Windows Default". Click Done.
You have to wait a second now go back to your home screen, you no longer have three screens (a useless feature anyway) but everything is faster now. You can also make it look better by going back into that place and clicking "themes".

Thanks. I'll give it a try and check the forum periodically for Android-on-Omnia2 news.

I've been working on this for quite a time now. (see modaco can't post links yet)
Okay I've uploaded all the necessary files. But no time to make a manual. So please, only those who know what they are doing try it out. For the devvers: in winmo change usb mode to mass storage (my internal storage), stick in into linux, change the size of the vfat internal sd, add an ext3 partition. Make sure you chmod it. And there you go!
My plan is to setup a dedicated website with the full source, split up in to braches for the different s3c6410 devices and supported drivers. This costs money and time, my plan is to do this next week.
For those of you who showed support by donations, I would like to do something extra for you guys. I apreciate this, Please PM me if you need any help and have considered the above but can't get it to work.
Paypal:
EDIT:now it is working
rapidshare:
--Alpha Release--
Note: to accomplish booting android requires reformatting the internal sd, this might brick your phone, I only recommend it for the more advanced (linux) users. I will take no responsibility for this. This release is soley for a proof of concept purpose. For the non-devvers: you could try to see if it works from vfat, you'll have to use mmcblk0p5, I know it gets to the android screen or make .img from these files and use an initr and mount the images.
What works:
-frame buffer
-s3c6410 cpu
-internal sd
Android is now in a state where you could open up almost anything, watch a slide show But because of the TC you need to press a little below/left on what you want to click due to faulty calibration.
What is in the making:
-ALSA support
What needs to be done
-hardware keys (using haret) (then we can shuw down the phone, because often you have to reformat the partition due to corruption)
-ADB/USB connection (shouldn't be too hard)
-UART/RIL/DPRAM config (to make 3G/PHONE/text work)
The first two will speed up development, that's why they need to be appended first.
Then:
-Touch screen should be better calibrated
-optimizations/speedups (G2d, G3d, armv6, VFP) + memory layout issues should be resolved. Now only 128 mb is used.
-external SD support (the s8000 android devvers are working on this)
-BT (I don't use it so it has no priority for me)
Which devices are supported?
I think theoretically every s3c6410 omnia/jet/acer iteration should work. But I know some devices will require a small patch to change the frame buffer adress. So please report back failures/successes.
EDIT: ofcourse I will still make a manual these days for the non-devvers, first thing i do when i have time.
Click to expand...
Click to collapse

almar2 said:
I've been working on this for quite a time now. (see modaco can't post links yet)
Click to expand...
Click to collapse
Hey there Almar, how is the speed of the device? Has compiling the drivers been an ok task and what do you think of the new phones coming out soon, will they be of any use to you?
What version of Android have you installed and if it is 2.1, would you say it is at least as fast as pre-2.1 android?

[Q] Some infos before flashing

Hey guys,
it's my first post here, but I'm still some days here in this board, consuming the contents for my HD2 with apreciation.
HD2 was and still is -hardwaresides- a milestone. When it comes up to the stock OS, there are some major things that I don't get. M*cr*s*fts OS is making this device a cripple, if you ask me. But that's another discussion and even more I was excited when I firstly saw a good friend these days holding me his Leo up the nose with Android embedded.
Now, I'd like to know some things before "flashing" my Leo - if you can say so, as the only thing to do seems to apply some kind of bootloader instaed of cleaning and rewriting the ROM. Which leads me to the
1. Will the installer overwrite the WM6.5 ROM or will it run in a dual-boot system?
2. Will a physical hardreset (volume-buttons) return to the stock-Rom?
3. Which of the local Froyo versions is the most stable with nearly all components working and - if possible - NO skin customizations except SENSE?
Thanks for your help and I hope that Android will bring my Leo to a whole new level.

Prepare yourself for a flaming of a lifetime.

Postaldude said:
Hey guys,
it's my first post here, but I'm still some days here in this board, consuming the contents for my HD2 with apreciation.
HD2 was and still is -hardwaresides- a milestone. When it comes up to the stock OS, there are some major things that I don't get. M*cr*s*fts OS is making this device a cripple, if you ask me. But that's another discussion and even more I was excited when I firstly saw a good friend these days holding me his Leo up the nose with Android embedded.
Now, I'd like to know some things before "flashing" my Leo - if you can say so, as the only thing to do seems to apply some kind of bootloader instaed of cleaning and rewriting the ROM. Which leads me to the
1. Will the installer overwrite the WM6.5 ROM or will it run in a dual-boot system?
2. Will a physical hardreset (volume-buttons) return to the stock-Rom?
3. Which of the local Froyo versions is the most stable with nearly all components working and - if possible - NO skin customizations except SENSE?
Thanks for your help and I hope that Android will bring my Leo to a whole new level.
Click to expand...
Click to collapse
First of all, why are you afraid to spell out Microsoft?
Second, Winmo didn't cripple HD2 at all, you have fully function phone.
Now, if you put Android on this phone, this make HD2 a cripple phone.
To answer your questions
1. No, Android will not overwrite the wm 6.5 rom, it need wm to run and it runs from sd card.
2. see #1, it will not alter wm rom, wm will be wm after reboot, you dont need to hardset.
3. This is like... personal preference, you have to try to see which build is for you.
the core here is kernel, if you try this build and you have problem, and you see another the build with the same kernel, it likely not going to fix your problem.

justwonder said:
First of all, why are you afraid to spell out Microsoft?
Second, Winmo didn't cripple HD2 at all, you have fully function phone.
Now, if you put Android on this phone, this make HD2 a cripple phone.
To answer your questions
1. No, Android will not overwrite the wm 6.5 rom, it need wm to run and it runs from sd card.
2. see #1, it will not alter wm rom, wm will be wm after reboot, you dont need to hardset.
3. This is like... personal preference, you have to try to see which build is for you.
the core here is kernel, if you try this build and you have problem, and you see another the build with the same kernel, it likely not going to fix your problem.
Click to expand...
Click to collapse
1. Why shouldn't I? There are enough examples, that anonymity is not given in every way these days on the web...
2. No, it did run well. But it
-isn't nearly as smooth as the iPhone-OS or Android
-HTC Sense seems to stuck several times with WM 6.5, which brings me to conclusion that HTC wasn't allowed to create a consequent GUI without corrupting MS license restrictions
-Browsers (Stock Opera, Opera 10, Opera Mini, Skyfire) are really slow
-I got a bunch of crashes even with updated stock ROMs and CF 3.5 installed
-the response between OS and touchscreen is still very laggy which results in the over-sensibility and the so-called ghost-effect, when the screenkeys begin jerking out/ the screen is working commands that had been given more than a minute along
-pinch-to-zoom only seems to be a gimmick clearly running in the SENSE environment and apps based upon it. The WM GUI isn't compatible to it in many ways
- and most important, it still is giving me white knuckles that MS at last decided to make WMP 7 NOT available, needless to say, AFTER several Leos were sold with prediction for WMP 7 being available sooner or later
Sure, you got a working OS for everydays use, but it is as unattractive and as imperformant as it could be the day it came on such a steroidic device like the HD2. MS has epicly failed in giving attention to the mobile phone market, that's for sure. It isn't done with borderless synchonization of Outlook e-mail and contacts - because todays smartphones are capabale of so much more. For something like this, you don't need a 1 GHz Snapdragon, together with 512 MB systemmemory. And after making such hard license restrictions for developers that are in charge to use WMP7, I think this won't ever change.
And sure, you're able to customize this OS as far as you want. But take the usual Jon Doe, excited by HD2-Ads and offended by an OS, that feels and looks like it is 10 years old under the SENSE-surface, with an app-catalogue that's growing slower and slower. And Jon Doe's not the man to deal with custom roms and tweaks.
Now take Android on the other hand. Based on the Linux-Kernel, which is known to give you every possible freedom, together with every possible brick to handle - which you're able to fix by yourself and what makes it attractive mostly for enthusiastics - it's a good blend of functionality ergonomics/ease-of-use. These two words together exclamated each other more or less in the past and this is one of the reasons, why Linux as a desktop-system hasn't become more popular over the years of development. Besides this, linux distributions are the fastest and most stable running OS I ever used on a PC. Now, Android is in charge and able to become as popular as MS is on desktop-systems, because it's working good. Most of the start-up problems that occured on early Droids are eliminated, this phone-OS becomes more and more performant. And it seems to be a lot more flexible than any other phone-OS
Finally, this discussion turned right the way i thought it would end. I'd like to thank you all for your information at first. If you'd like to make further dialogue affecting the goods and bads of WM, please contact me PM.

Booting straight to Android from Power on.

EDIT: this has been changed to try to clear up some confusion. A few people are looking for the following WINMO/ANDROID combination:
- Power Phone on, phone boots WINMO and then automatically boots Android without any user interaction at all.
- Ideally all WINMO boot screens will be removed from boot, if something needs to be in there use an Android or HTC boot screen.
- This could be done by adding CLRCAD.exe and HARET.exe to the WINMO boot sequence in the registry / batch file perhaps.
- Totally strip down the WINMO rom so it simply acts as a software facilitator to load android, very little has to actually work. Programs, ring tones, etc etc could be removed enabling the Phone to boot WINMO in less than a minute before HARET is called.
- Boot sequence calls to ANDROID build should be standardised so the ANDROID rom can be changed at will by simply copying a new Android folder to the SD renaming the old one. (as most currently are)
This would serve as a good intermediate option between (1) running Android on NAND scrapping WINMO altogether vs (2) Running WINMO on NAND / running Android on SD. The phone would feel more like an Android unit, boot quicker but also allow easy upgrade options for Android whilst allowing an easy fall back to WINMO if required.
Please DO NOT comment on whether or not you feel this is necessary, enough people already do feel this would be a useful option, if you know of a ROM which already has this facility then DO NOT comment without posting a link to it.
Thanks

If I am not mistaken, you will have to boot into WinMo if not booting from NAND. The device boot into WinMo by default.
If you want fast boot time than you should try one of the following
darkstone SuperRAM FroYo v1.2 http://forum.xda-developers.com/showthread.php?t=870518
MDJ FroYo Streak Lite v. 0.4 RAM Edition http://forum.xda-developers.com/showthread.php?t=871804
Darkstone figured out a way to load android system into RAM which is way faster than SD or NAND.
So you can find a strip down WinMo ROM with a boot loader and run one of the RAM build. There has been reports of boot time of 2 minutes or less.

stoolzo said:
I have seen a lot of discussions regarding SD vs NAND and wonder if there is a better intermediate solution for those wanting to bypass winmo and not using nand at all. I am using NAND and it is easily fast enough for me and much better than winmo.
Has anyone built a heavily stripped down winmo rom maximised for Andriod that auto boots android so we don't even have to load it manually from winmo? I would prefer this over NAND as I could much more easily switch back to winmo or change my android ROM. Ideally it would have no winmo boot screens and simply bypass them only showing the Android screen.
Click to expand...
Click to collapse
you're not running from NAND...

stoolzo said:
I have seen a lot of discussions regarding SD vs NAND and wonder if there is a better intermediate solution for those wanting to bypass winmo and not using nand at all. I am using NAND and it is easily fast enough for me and much better than winmo.
Has anyone built a heavily stripped down winmo rom maximised for Andriod that auto boots android so we don't even have to load it manually from winmo? I would prefer this over NAND as I could much more easily switch back to winmo or change my android ROM. Ideally it would have no winmo boot screens and simply bypass them only showing the Android screen.
Click to expand...
Click to collapse
Wow... Just wow...
Sent from my HTC HD2 using XDA App

dung8604 said:
Wow... Just wow...
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
+1 on the wow!

interesting thread for someone who already passed 400 posts. and i thought that i am asking stupid questions every day
but i will give you a hint, just because of your avatar (i have three rats - but none of them is that creature in my avatar lol): there ARE winmo roms stripped down to work best way with android. one of them is goatrip android 1.0 which i am using - it also includes a autostart for haret.exe... since this winmo rom is really old, you should search for it by yourself!

stoolzo said:
Has anyone built a heavily stripped down winmo rom maximised for Andriod that auto boots android so we don't even have to load it manually from winmo? I would prefer this over NAND as I could much more easily switch back to winmo or change my android ROM. Ideally it would have no winmo boot screens and simply bypass them only showing the Android screen.
Click to expand...
Click to collapse
OzDROID
Energy
stoolzo said:
I have seen a lot of discussions regarding SD vs NAND and wonder if there is a better intermediate solution for those wanting to bypass winmo and not using nand at all. I am using NAND and it is easily fast enough for me and much better than winmo.
Click to expand...
Click to collapse
PLEASE search before posting

personal attack removed
I know how Android works, I have been using it instead of winmo for weeks now. What I am suggesting for those children who are more interested in starting arguments than actually having an adult conversation is that it would be good to have a intermediate set up between nand and the current haret set up for those who never want to go nand.
Nand: full android boot, no winmo at all.
Current haret setup: boot winmo and then click on an icon that starts both clrcad.exe and haret.exe.
My suggestion: Turn on phone, boots winmo but also boots android during the same operation it would feel like a fully android phone. Clearly you would have to set a flag file on the SD card to stop auto booting Android in case you did want to drop back into winmo but for me this would be ideal as I never go near winmo anymore but I like to have it there just in case.
Get it now everyone?????

Been doing that for ages mine auto boots haret.exe....

does it take you to winmo and then you see haret starting automatically or does the screen stay black all the way through until you get the Andriod splash?

Sorry but your running nand? Have I missed something?

again total understanding failure, there as no ROMS exactly as I have described, yes there are stripped down roms, loads of them, yes there are haret auto boot programs but show me a rom that boots directly into android from power on?

Thread LOCKED. Will clean up and unlock later...

Thread re-opened. Please keep the swearing and vulgarities to yourselves from here on out. Next time this thread will not be reopened.

granted but I think I poster has the right to respond to personal attacks.
Back to the thread, both roms offered take me halfway as they have stripped down ROMS, but guess what, I am already running a stripped down down using an auto bootloader, this is not what I am after. Yes Windows has to load to load haret, duh but do you have to see it?, does it have to fully load to desktop?, could the haret loader not be cooked into the boot sequence so the windows mobile desktop is bypassed or only flashes up momentarily before android boots.
noob bashing: there is nothing wrong with being a noob, personally I think far to many people on here make a few posts, get to a certain level and then get lulled into a false sense of competence where the feel they can attack people.
Searching: yes you should always search and it is useful for some things like a specific application, fault or ROM, but breaking news, it isn't that great when you are looking for something very specific, some people haven't got time to spend hours reading threads. I always search but on this occasion I could not find anything that specifically met my requirements, the fact that I have only been offered 2 and neither of these are any different to me current solution only backs up my point that searching is not the be all and end all people make it out to be.
If you haven't got something constructive or helpful to add to this thread DON'T POST.

Unless I'm missing something here, this should answer your question.
Clrcad & haret are both exe files, which I'm sure you know are native to windows. They need Windows in order to run, so it's not possible to run them without first starting Windows. 100% not possible.

stoolzo said:
I have seen a lot of discussions regarding SD vs NAND and wonder if there is a better intermediate solution for those wanting to bypass winmo and not using nand at all. I am using NAND and it is easily fast enough for me and much better than winmo.
Has anyone built a heavily stripped down winmo rom maximised for Andriod that auto boots android so we don't even have to load it manually from winmo? I would prefer this over NAND as I could much more easily switch back to winmo or change my android ROM. Ideally it would have no winmo boot screens and simply bypass them only showing the Android screen.
Click to expand...
Click to collapse
What?
stoolzo said:
again total understanding failure, there as no ROMS exactly as I have described, yes there are stripped down roms, loads of them, yes there are haret auto boot programs but show me a rom that boots directly into android from power on?
Click to expand...
Click to collapse
No, because thats not possible.
You NEED winmo to boot first, to start up drivers, and to simply run haret.
There are many bootloaders which will auto boot android before the windows mobile home screen is shown.
Does it really matter though? honestly?
You still auto boot into android at the end of the day. Your not losing anything by seeing winmo for a few seconds!

@AllWhomHasPostedEarlier
I think he means to boot into WinMo but without all the crap like splash screen or even most of the "Apps" . Just boot necessary drivers,system files, EBL's etc ... then clrcad & haret are run .. when you actually see nothing of it . Just black screen for instance . Am I right ? Cuz I'm looking for this too !

I cant see anyone bothering to go to all the effort it would take just to find a solution to the "problem" of 10 secs worth of winmo time......
As it is, winmo boots a few seconds later haret is automatically run very soon after boot....... thats as good as its going to get for all your winmophobes........
at least until nand.......
Im sure you can all tolerate a tiny amount of winmo until then cant you??

kawazaki said:
@AllWhomHasPostedEarlier
I think he means to boot into WinMo but without all the crap like splash screen or even most of the "Apps" . Just boot necessary drivers,system files, EBL's etc ... then clrcad & haret are run .. when you actually see nothing of it . Just black screen for instance . Am I right ? Cuz I'm looking for this too !
Click to expand...
Click to collapse
Yeah I think thats what OP trying to after. Im looking for this too wish there is a cook/dev out there that dont mind spending time to cook such a rom