Develop Bugs

Disable HTC Sense on the Desire

For the people that wanted to know if you can disable HTC Sense on the Desire, or just wanted to know how to do it:
Here is a short demonstration of how to disable HTC Sense on a Desire.
It's nice to know this is possible. IMO the stock version (Nexus One look) also has some nice benefits.
Sorry if this was already posted

thanks....
this what i needed to make my decision....
defintally a desire

thanks that what i was looking for..
so excited about getting the Desire...

But, I dont think that will completely stop all Sense processes.
The Sense framework is still being used, CMIIW.

gogol said:
But, I dont think that will completely stop all Sense processes.
The Sense framework is still being used, CMIIW.
Click to expand...
Click to collapse
All Sense on Android is, is a few apps.
The main one being the Launcher which you can disable as seen in that video.
There's then the Messaging and Dialler apps which you can replace with stock apps (without being rooted).
That's about it apart from the fact you'd be left with a Black notification tray instead of a White one and a far superior lock screen.

gogol said:
But, I dont think that will completely stop all Sense processes.
The Sense framework is still being used, CMIIW.
Click to expand...
Click to collapse
IMO, i dont think someone would disable the Sense (maybe just to see how the plain Nexus One looks like ).
and we have 576 MB RAM; I dont think we should worry about "apps that run in the background"

gogol said:
But, I dont think that will completely stop all Sense processes.
The Sense framework is still being used, CMIIW.
Click to expand...
Click to collapse
Jup I found out that even if you disable Sense, tbere will still be some 'behind the scenes' Sense stuff going on. Like for example, Stock 2.1 only supports 5 homescreens instead of 7.
So if you REALLY want the fast Stock 2.1 experience, disable Sense is not enough. You will have to put a real stock 2.1 ROM on it, or how it is called.
Anyway, most people probably wont have any problems with this.

Speaking of stock 2.1 rom being faster than the one with Sense UI.
How much faster is it? Is it very noticeable?
XDA mark said:
Jup I found out that even if you disable Sense, tbere will still be some 'behind the scenes' Sense stuff going on. Like for example, Stock 2.1 only supports 5 homescreens instead of 7.
So if you REALLY want the fast Stock 2.1 experience, disable Sense is not enough. You will have to put a real stock 2.1 ROM on it, or how it is called.
Anyway, most people probably wont have any problems with this.
Click to expand...
Click to collapse

Keeping the HTC framework will be to the owner's advantage, some of the HTC apps that don't run on a stock Android rom will then work properly.

a stupid question....can i put manila on the desire?? and then....it's android similar to windows mobile?? there's a cab for everything?
exscuse me for stupid questions but i have a topaz and i'm thinking about take a desire!

mikawa said:
a stupid question....can i put manila on the desire?? and then....it's android similar to windows mobile?? there's a cab for everything?
exscuse me for stupid questions but i have a topaz and i'm thinking about take a desire!
Click to expand...
Click to collapse
The contents of each tab in Manila are available as widgets in Android and they're far more customizable. There's really no reason to have Manila on Android.

nm... it was shown in the video @ the OP.

XDA mark said:
Jup I found out that even if you disable Sense, tbere will still be some 'behind the scenes' Sense stuff going on. Like for example, Stock 2.1 only supports 5 homescreens instead of 7.
So if you REALLY want the fast Stock 2.1 experience, disable Sense is not enough. You will have to put a real stock 2.1 ROM on it, or how it is called.
Anyway, most people probably wont have any problems with this.
Click to expand...
Click to collapse
When / If it gets rooted and vanilla 2.1 gets ported to it, I am going to always have a Nandroid backup of a version with SenseUI and a Nandroid backup of Vanilla 2.1 Android so I can swap between them as and when I want.

gogol said:
Speaking of stock 2.1 rom being faster than the one with Sense UI.
How much faster is it? Is it very noticeable?
Click to expand...
Click to collapse
From what I have seen, the difference is almost not even noticeable. But then again all the Desire video's I have seen are after it has just been turned on. Maybe the Sense UI will cause some lag after a while of using.
Anyway, Stock 2.1 HAS to be faster, that is a fact. 2 homescreens less, no Sense stuff running in the background, etc.
If I would turn off Sense UI, I would not do it for the speed improvement btw. I like the look of 2.1, with that 5 homescreens and the way to switch between them.

Dude it's a ''snap the dragon'' 1ghz cpu inside! You will not need extra speed

vegetaleb said:
Dude it's a ''snap the dragon'' 1ghz cpu inside! You will not need extra speed
Click to expand...
Click to collapse
And the Desire has extra RAM to accommodate SenseUI.

vegetaleb said:
Dude it's a ''snap the dragon'' 1ghz cpu inside! You will not need extra speed
Click to expand...
Click to collapse
Well, when I finally got my long awaited HTC TyTn, I asked on a forum if anyone knew if there were any possibility to overclock the CPU....
The only answer I got back then was : "..There's no need to overclock the TyTn, the CPU is a 400 mhz!!"
But now, I'm sitting here, stuck with my sloooow TyTn (after selling my Hero to earn money for a new Desire)
So...I guess we can always need some more power, just wait some months and the apps and games are demanding more than enough for the Snapdragon CPU....and you need to swallow a camel or two

vegetaleb said:
Dude it's a ''snap the dragon'' 1ghz cpu inside! You will not need extra speed
Click to expand...
Click to collapse
Yeah, sure it's a 1Ghz processor. But my HD2 has it and it still lags.
So I will take all the extra speed I can get for perfect performance

XDA mark said:
Yeah, sure it's a 1Ghz processor. But my HD2 has it and it still lags.
So I will take all the extra speed I can get for perfect performance
Click to expand...
Click to collapse
You can argue that on the HD2 it's down to the OS/custom ROMs that it still 'lags'. My brother has the a stock T-mobile ROM on his device and I fail to see any lag.

brummiesteven said:
That's about it apart from the fact you'd be left with a Black notification tray instead of a White one and a far superior lock screen.
Click to expand...
Click to collapse
The better lock screen you're talking about, is that after disabling Sense? Which lock screen would that be, and what lock screen does the alternative have? And I always thought there were several lock screens to choose from - I've seen one where you make a pattern, one where you just flick the lock screen down, one where you "turn a wheel", and possibly some others, can't remember.
That's a lot of "lock screen" for one post

Slow Android 2.1

I've been experimenting with the Sense 2.1 VGA build of XDAndroid and after compiling it and copying it over I see that Android itself runs very sluggishly on my RAPH110.
Im using a 4GB HC Class 4 card.
Are there any ways that I can actually speed this thing up?
Ive used ATK and thats about it. Im out of ideas here.
Also: 1) Is there anyway to fix the backlight issue when coming out of sleep mode? (It stays at minimum brightness)
2) Is there anyway to transfer winmo contacts to XD?

howeasy said:
I've been experimenting with the Sense 2.1 VGA build of XDAndroid and after compiling it and copying it over I see that Android itself runs very sluggishly on my RAPH110.
Im using a 4GB HC Class 4 card.
Click to expand...
Click to collapse
AFAIK There's no XDAndroid build with HTC Sense in it. There's this but it's not part of the XDAndroid project, has fewer users and is (in my experience) updated less frequently. Click the banner in my sig to go to the XDAndroid thread - there's a new Eclair 2.1 build out which I'm yet to try. If that's slow, try the 2.0.1 build, which has none of the backlight issues you've mentioned. It shouldn't be slow, but if it is to you then it's just because you're used to Windows Mobile running very quickly on the device, and there's no way to get Android going that smoothly just yet.

You could try overclocking but it should be pretty speedy already. Is this your first build of Android? Have you deleted data.img and let it remake it. Try formatting your sd card.

ben_duder said:
AFAIK There's no XDAndroid build with HTC Sense in it. There's this but it's not part of the XDAndroid project, has fewer users and is (in my experience) updated less frequently. Click the banner in my sig to go to the XDAndroid thread - there's a new Eclair 2.1 build out which I'm yet to try. If that's slow, try the 2.0.1 build, which has none of the backlight issues you've mentioned. It shouldn't be slow, but if it is to you then it's just because you're used to Windows Mobile running very quickly on the device, and there's no way to get Android going that smoothly just yet.
Click to expand...
Click to collapse
That is indeed the build i'm currently using.
The official XDAndroid build of 2.1 would give me the endless fireworks screen even and updated zImage.
If there's a version that will work on my Fuze then please link me to it as I have been unable to track it down.
But regardless, I've been working on trying to get it to run faster, Ive had moderate luck using ATK but thats about it.
Im baffled as to why its running this slow.
Also, using the 2.0.1 build caused the phone not to send SMS messages, hence the reason I came looking for a new build and came across the Sense one.

Did you use the Fuze startup text instead of Raphael? Did you leave it long enough? On first boot my Raph100 takes about five minutes to start, but it's only about one minute after that.
Here's proof (if you want it) that it's normal for it to take ages to load on first boot.

ben_duder said:
Did you use the Fuze startup text instead of Raphael? Did you leave it long enough? On first boot my Raph100 takes about five minutes to start, but it's only about one minute after that.
Click to expand...
Click to collapse
Indeed I did. It simply played the Nexus one boot animation for a while, froze for around 5 seconds, and then went back and played the nexus one animation from the beginning.
The sense build im using works in all aspects other than the fact I would prefer the normal Android layout, I want it to run smoothly, and I want a more constantly updated version.
I used the Fuze startup text with and without the overclocking script thrown in.
I'd be more than willing to go at it again if its worth the shot.

I really recommend having another go: XDAndroid is exactly what you're looking for with regards to the lack of Sense and the frequent updates. There's no hardware-related reason why it shouldn't work on your Fuze, so delete everything from the build that's already on there, get the right startup.txt and give it a go

Thanks for the positive reinforcement!
If you could possibly directly link me to the 2.1 build you'd personally recommend that would be appreciated.
Ive been trying a build for the RAPH800 that was linked to in your sig and its giving me to the same problem I described earlier.
I have the RAPH110, as you know, but the RAPH800 build was the closest thing I could track down.

Eh? Don't use the 800 unless your phone is CDMA. Just download the 2.1 bundle for the normal Raphael, the link is just under the changelog. I'm giving it a go right now and I'm currently waiting for it to boot, I'll tell you if I have any problems.

ben_duder said:
Eh? Don't use the 800 unless your phone is CDMA. Just download the 2.1 bundle for the normal Raphael, the link is just under the changelog. I'm giving it a go right now and I'm currently waiting for it to boot, I'll tell you if I have any problems.
Click to expand...
Click to collapse
Oopsy! I had a hard time tracking that down.
Im using the one labeled "03.05.10 | 2.1 builds". Is that correct?
It also says it already has the lastest zImage that should work so do I need to go update that?
I swear, if there was a super mega +rep button i'd press it.
You're what support forums are all about <3
(3:42PM: Just calibrated touch screen)

Yep, that's the one I'm trying. I've had some experience with the 2.0.1 but I've never actually used this build before, so it's possible there's something missing that I don't know about.
Haha thanks, although there are much nicer and more knowledgeable people on here than me

Well you're the one putting forth the effort to help a guy in need, so I truly do appreciate it.
I'm still getting the constant Nexus one boot animation sadly enough.
Maybe I'll go test out the 2.0.1 build and see if I can get that one to work, but like I said earlier, I had SMS issues with that one.
EDIT: I was able to get the 2.0.1 build working with SMS after zImage and etc..
Going to test sound and whatnot now and come back with another edit to verify.
I would still like the 2.1 build though but this might have to suffice.

Okay, I've just been messing with the 2.1 build and couldn't get it working either. I checked my startup.txt and noticed that set mtype was on the same line as set ram size, so I'm deleting my data.img and trying again.
Edit: It worked! No more boot animation

ben_duder said:
Okay, I've just been messing with the 2.1 build and couldn't get it working either. I checked my startup.txt and noticed that set mtype was on the same line as set ram size, so I'm deleting my data.img and trying again.
Edit: It worked! No more boot animation
Click to expand...
Click to collapse
AWESOME!
Mind uploading whatever it is you did and tell me what I have to do to get the same result?
Sorry, Im still pretty new to this whole thing.

I won't upload it, but just check your startup.txt and there should be two lines of text that look like they should be separated. Press return just before the second, save it and delete your data.img file. Then run HaRET again and it should work fine.

You have to try this build - it's brilliant.

Well I suppose I'll have to give that a shot.
I found and edited the lines and also threw in the overclocking script.
After deleting the data.img Im giving it one last shot now.
If that doesnt seem to work then I'll just deal with the 2.0.1 build until I find a way to get this to work.
EDIT: anddddd, no such luck.
Guess I'm left to stick with 2.0.1 for now, it was running pretty fast as well.
So if anyone reading this gets 2.1 working please feel free to post.
Is there a way to get Android on the phone itself rather than SD? I'd love to ditch Winmo and save some battery life here.

Shame... I can't understand how it's not working now. All I did was edit the startup.txt, delete my data.img and try again, then wait for ages while everything loaded. If you're not sure if you've edited your startup right you can try using the one that works for you with 2.0.1.
As for not having to use the SD, that would require NAND flashing, which has some way to go before we can use it on our Touch Pros to replace Windows Mobile. There's a thread about it here. There are dual-booting and light WM ROMs designed for XDAndroid users, however.

In case you don't believe me
Sent from my AOSP on XDANDROID MSM using the XDA mobile application powered by Tapatalk

Did you happen to update the zImage or anything or did you just copy and paste and throw in the startup?

Best Android

Hi All,
Been looking around, (ive tried android on my kaiser once), and just wondered what is the best (most stable) android for kaiser, as a lot of them seem to have a lot under "not working"?
Thanks,
Tom,

Kinda hard to answer, since no one Android build has anything working 100%.
Myn’s Warm Donut will get you most of your stuff working, but there's still a lot of bugs.
Incubus26Jc's Super Eclair is pretty good, but you lose out on Camera and Bluetooth. Less bugs then Donut, but more stable IMO.

Although Polyrhythmic hasn't updated his 2.1D for a while, I still think it's the best of the eclairs. For Donut, Myn's is really the only game in town.
Eclair is still struggling with non-working camera, but GPS , WiFi, and BT are working reasonably well, if you are prepared to invest some time into hunting out the best combination of nbh and build.
Donut is reasonably complete, I have had Myns working with WiFi, GPS and Camera, or GPS, BT and Camera, but never managed all working at once, it is the most feature-complete and arguably the most stable build of all.
Given that we have only had Android on our kaisers since the end of last year, I still think that all the devs have done a remarkable job, and development continues.
Compared to the start of the year, when all that was possible was running from SD, with battery life measured in minutes, no wifi, gps, bt or camera, I think what we have now is a complete OS, it's been my everyday phone OS now for months, and once you get into a few good habits, it's stable and smooth, with decent battery life.

Thanks for replies guys,
I have installed Myn’s Warm Donut, but it seems the graphics are a bit weird, they seem like they are the wrong bit depth or something, not quite sure how to describe it.
Any help on this please?
Thanks,
Tom

XCougar said:
Thanks for replies guys,
I have installed Myn’s Warm Donut, but it seems the graphics are a bit weird, they seem like they are the wrong bit depth or something, not quite sure how to describe it.
Any help on this please?
Thanks,
Tom
Click to expand...
Click to collapse
Q: I installed Android but now everything is blurry.
A: It's due to wrong resolution. Kaiser phones have panel for 230x320 but you're probably using 320x480 build. Here is a post by user tatnai where he explains this situation for Vogue devices (it goes same for Kaiser).
Android FAQ: http://forum.xda-developers.com/showthread.php?t=683644
Click to expand...
Click to collapse
Myn's Warm Donut is basically a scaled down version of 320x480 resolution to fit 230x320 panels, with 110 density, hence the blurriness.
One build with native 230x320 I like is vilord's Tattoo Sense, but there is a camera and BT audio not working problem in that build - hopefully incubus26jc's next release will fix this.

milanche said:
Myn's Warm Donut is basically a scaled down version of 320x480 resolution to fit 230x320 panels, with 110 density, hence the blurriness.
One build with native 230x320 I like is vilord's Tattoo Sense, but there is a camera and BT audio not working problem in that build - hopefully incubus26jc's next release will fix this.
Click to expand...
Click to collapse
vilord's Tattoo Sense sounds pretty good, and it has rosie which I'd love to see working stable. I think I'll try this on the weekend, but just wanted to know, has anyone tried this? is it stable and/or fast? Its for the touch, but as far as I've seen, vogue builds work for kaiser... would this work too?

milanche said:
Myn's Warm Donut is basically a scaled down version of 320x480 resolution to fit 230x320 panels, with 110 density, hence the blurriness.
One build with native 230x320 I like is vilord's Tattoo Sense, but there is a camera and BT audio not working problem in that build - hopefully incubus26jc's next release will fix this.
Click to expand...
Click to collapse
Hi, thanks for reply, not that I don't believe you, but its not so much blurryness, there are pink and green bits everywhere? Or is this what your describing?
Thanks again,

Oh thats because you´ve choosed a wrong paneltype. Kaiser was built with 3 different Panels so you have to choose the right one. Look at the second sticky thread.

xPreSiDenT said:
vilord's Tattoo Sense sounds pretty good, and it has rosie which I'd love to see working stable. I think I'll try this on the weekend, but just wanted to know, has anyone tried this? is it stable and/or fast? Its for the touch, but as far as I've seen, vogue builds work for kaiser... would this work too?
Click to expand...
Click to collapse
I've tried it and believe it's the best Android build so far, despite BT and Camera problem (which we should be able to fix as it is Donut 1.6 Android).
For Kaiser you should use kallt_kaffe's update to get Wifi working and it also fixes Rosie and Market.

Thanks for info.
Ok please dont flame me, ive looked around and I used to flash windows mobile all the time, but I really dont understand these nbh files.
What are they, what do they do, why are there different ones e.g voguimg.nbh and kaisimg.nbh and polimg.nbh
Thanks for your patience with me

XCougar said:
Thanks for info.
Ok please dont flame me, ive looked around and I used to flash windows mobile all the time, but I really dont understand these nbh files.
What are they, what do they do, why are there different ones e.g voguimg.nbh and kaisimg.nbh and polimg.nbh
Thanks for your patience with me
Click to expand...
Click to collapse
VOGUIMG is for Vogue devices, POLAIMG is for Polaris devices and KAISIMG is for Kaiser. Think of them as some sort of bootloaders for Android. You flash the NBH, boot to the install console, install Android from SD to NAND/SD/EXT2 and boot Android. Also you have to choose the correct panel to avoid screen problems you're having. The only way to see which panel are you using on Kaiser is to test all three of them and see which one doesn't cause you screen problems.
To test which panel you're using you should first make an SD install with Haret, there you have the option to specifiy panel type in the config file default.txt and can change this before every boot. With NAND this is hard-coded into NBH file. Later you can flash to NAND if you decide to stick with Android.
Please go thru this Q/A topic, it should help you get the answers to most of newbie-type questions.

I´m not a developer and especially on android i´m a noob but i think the NBH contains all what is going to be flashed into nand. In case of WiMo it´s the whole Operating system, somtimes with radio too. In case of android the NBH contains the Kernel only. The kernel is designed for your device with all the drivers you need (touchscreen, wifi, BT, GPS, etc.). so kernels from other devices may not work becaus of other hardware specs. in worst case it may brick your device. I read alot before i flashed my kaiser an kallt_kaffe´s kernel seems to be the best for now. Nearly all funktions are available. Only the Camera have a bug, but i think it only takes only a little time to fix this too.
I use kallt_kaffe´s kernel and Myn´s Warm Donut RLS5 and i´m totally happy with it. Fingerfriendly (you´ll never need your stylus again except for reset ^^), and much more responsive then the fastest WiMo ROMs.
You only have to modify the nbh for your panel type. But you only can do trial & error to find out which type you have.
So... happy flashing.

Thanks everyone for your help, I have the tattoo sense rom on my phone now, my phone uses panel2 type of kaiser nbh.
I now understand the nbh better.
As im more then likely going to upgrade to a newer android rom when more stable ones come out, can anyone recommend a android application that will allow me to backup my txts, emails, contacts, and settings, etc.
Thanks all

Current integration of Android with HTC diamond

I am a newbie to WinMo and Android devices.
I know it is possible to run Android on HTC window mobile pre-installed device, with the matter of the non-working camera.
I wanna know actually what is process/method which can makes Android possibly runs on HTC diamond, and does it mean once we have this boot system, we can boot any Android even the latest 2.2 Froyo?
All I want is to get some knowledge which can help me to step into this area, I love software engineering and find that this forum is the one which most positive users come, so hopefully I can start building sth from sketch in here.
Many thanks in advance, and thanks for the patiences and the kindness of knowledge sharing.

Hi, as you said, it is currently possible to boot an Android system from a WinMo one. But they are some issues left, mainly the battery life. Indeed, battery drains pretty fast with Android (and the indicator is not accurate at all).
Concerning Froyo (2.2), I ran many android systems on my Diamond 100, and Eclair versions (2.1) are really very slow, that is why I am currently using a Donut version (1.6), which is pretty fast and stable. So I'm not sure the Diamond will be able to run smoothly Froyo.
Last thing: today, the only way to have a working Android is to boot on WinMo and then launch a program (Haret) which will "kill" WinMo and boot to Android from internal storage (or SD card for other devices). There is currently no way of flashing an Android as you can do with WinMo.
Hope we'll get asap a fully working Android for our WinMo's HTCs

damien2702 said:
Hi, as you said, it is currently possible to boot an Android system from a WinMo one. But they are some issues left, mainly the battery life. Indeed, battery drains pretty fast with Android (and the indicator is not accurate at all).
Concerning Froyo (2.2), I ran many android systems on my Diamond 100, and Eclair versions (2.1) are really very slow, that is why I am currently using a Donut version (1.6), which is pretty fast and stable. So I'm not sure the Diamond will be able to run smoothly Froyo.
Last thing: today, the only way to have a working Android is to boot on WinMo and then launch a program (Haret) which will "kill" WinMo and boot to Android from internal storage (or SD card for other devices). There is currently no way of flashing an Android as you can do with WinMo.
Hope we'll get asap a fully working Android for our WinMo's HTCs
Click to expand...
Click to collapse
instead i think that froyo will run well...because yesterday i saw some benchmark over the nexus one and the preformance were multiplyied by 2...and i saw the internet browsing benchmark and was the fastest browser i saw

So let's hope you are right about Froyo =)

damien2702 said:
So let's hope you are right about Froyo =)
Click to expand...
Click to collapse
i hope it too..i love android...i'm waiting for froyo and for a flashable android...i don't like a lot wm

And so do I ^^ I recently tried the Desire with Android 2.1, and I'll certainly buy one when I'll change my Diamond =)
Correct me if I'm wrong, but I guess you are the one trying to cook a Sense XDAndroid ?

damien2702 said:
And so do I ^^ I recently tried the Desire with Android 2.1, and I'll certainly buy one when I'll change my Diamond =)
Correct me if I'm wrong, but I guess you are the one trying to cook a Sense XDAndroid ?
Click to expand...
Click to collapse
i was trying but i was having porblem using ubuntu(no ethernet,no wireless and some other things) so when i will resolve those problem i will start

so haret in fact is a simulator?? just to provide a simulated environment to run Android?

If I'm right, Haret isn't a simulator. It is a program which, launched under WinMo, will kill all WinMo processes and boot on internal storage with Android files. Have you ever tried it?

if you want to try it the easy way:
http://forum.xda-developers.com/showthread.php?p=5420781#post5420781
there is an cab to download, just install it
than you can run android
bewhare, android uses a huge amount of internetactivity ( maybe it costs money with your telephon provider )
or just for testing remove the sim card...
its the easy way to run android, for multiboot
you need to install a multibootmanager on your phone
for me there are some problems with android on the diamond,
i get sometimes time outs of some programs, but its possible to use it... and test it...
maybe some thing in settings but i tryed it only for some hours ( telephonprovier... i got only 300 minutes of mobile internet connection for free )
but remember, back up your data...

[Q] How is android supposed to run?

I have tried both a Froyo variant and a Gingerbread variant on my Diamond but for me its not usable at all .. It lockups every 30 seconds for like 1 minute. Just when my devices screen goes black i am barely able to turn it back on again.
Now im not complaining about the devs work here, dont take it that way.. I just want to know if its supposed to run this way or if its something i do wrong?

Da9L said:
I have tried both a Froyo variant and a Gingerbread variant on my Diamond but for me its not usable at all .. It lockups every 30 seconds for like 1 minute. Just when my devices screen goes black i am barely able to turn it back on again.
Now im not complaining about the devs work here, dont take it that way.. I just want to know if its supposed to run this way or if its something i do wrong?
Click to expand...
Click to collapse
try to install android rom on your device's internal storage and use GenYDualBoot to be able to run it from windows !

Hakim Rahman said:
try to install android rom on your device's internal storage and use GenYDualBoot to be able to run it from windows !
Click to expand...
Click to collapse
Is it usable on a day to day basis or is it still heavily in development? Can't find that much information on it to be honest.

Lipinsky said:
Is it usable on a day to day basis or is it still heavily in development? Can't find that much information on it to be honest.
Click to expand...
Click to collapse
I have two 2 months applying it to my Htc diamond {dual boot = Eto.Y 2.4a WWE + XDAndroid FRX07.1 (on internal storage)}

Lipinsky said:
Is it usable on a day to day basis or is it still heavily in development? Can't find that much information on it to be honest.
Click to expand...
Click to collapse
The usability has definitely increased over the years but it is still more a concept than a real operating system as the hardware and software dont work together very well. This is because there are no official kernels, drivers or anything provided by HTC. The xdandroid team has done an incredible work to get android running on this device, but they couldnt find a way to properly get android on the NAND because the storage is too small. Thats also why you have to start it via windows mobile and cant directly boot to it, it runs out of the SD Card. So you will never achieve a nice performance as long as the OS isnt located on the NAND. The lags and force closes you are certainly experiencing derive from this problem. The device itself would definitely have the power to run android at an acceptable performance.
As far as I know the development has ceased. If you search the corresponding threads you will find the statement of the devs. Here is were you can look:
Froyo, Gingerbread: http://forum.xda-developers.com/showthread.php?t=951981
Froyo 07: http://forum.xda-developers.com/showthread.php?t=951811
Gingerbread 0A: http://forum.xda-developers.com/showthread.php?t=711692
wiki: http://xdandroid.com/wiki/Main_Page
blog: http://southcape.org/category/android/

yeah development seems to be halted, its nice to play with, but not as main os for day to day use