Develop Bugs

Vanilla or WXML v0.10

Someone can tell me what are the difference between this to ROM ?
Same soft (MSN...) ? Video call ?

It's all laid out in the first post here of this thread:
http://forum.xda-developers.com/showthread.php?t=295456

stpete111 said:
It's all laid out in the first post here of this thread:
http://forum.xda-developers.com/showthread.php?t=295456
Click to expand...
Click to collapse
Yes for WXML but for vanilla ?

WMXL for sure... It has the regular Vanilla ROM plus some extras! And they both seem just as quick and stable as the other to me.

I'm a Vanilla lover I'm afraid.
I always manage to get rid of a few unnecessary files/folders etc that are present even in the Vanilla releases, which gives me even more "ROM space" to cook my own ROM with as many of my own software choices squeezed in there as possible...

sub69 said:
I'm a Vanilla lover I'm afraid.
I always manage to get rid of a few unnecessary files/folders etc that are present even in the Vanilla releases, which gives me even more "ROM space" to cook my own ROM with as many of my own software choices squeezed in there as possible...
Click to expand...
Click to collapse
Well, the removal of the Office and RDP icons in the Vanilla ROM were the deciding factor for me. Yeah, the additional software takes up a little space, but they're small and not enough for me to worry about. And since I just started customizing ROMs, I am not too concerned about a MB or two until I really need them back.

richy240 said:
Well, the removal of the Office and RDP icons in the Vanilla ROM were the deciding factor for me. Yeah, the additional software takes up a little space, but they're small and not enough for me to worry about. And since I just started customizing ROMs, I am not too concerned about a MB or two until I really need them back.
Click to expand...
Click to collapse
Absolutely!
Don't get me wrong, Kypher's done a great job. The added software doesn't have any impact on available Storage space after flashing and there's no reason at all why anyone should choose the "Vanilla" ROM over the "Live" ROM...
...unless you're going to cook your own ROM, and you want to start from square one with less to strip out in the first place.
I'll probably make a load of changes and additions that Kypher has already incorporated into "Live", but I like to start with a clean slate, and having messed around with a lot of ROM's on my previous devices, I'm pretty sure that I know 90% of what I'm going to do before I even start, and assuming I'm right, space is going to be at a premium!
Happy cooking!

It also comes down to how soon you got on board .
I was one of the first to download and install the Vanilla ROM before the WXML release was announced, and for me at this point there is no point in changing (especially after just getting my software how I like it ). Remember there will be most likely several releases of WXML over the next couple of weeks, so my advice is if you're already on Vanilla there is not much reason to move to WXML .10 at the minute .

I've a tytn in Portuguese unlocked, can I install vanilla or wxml?
thnks

KevinBaker said:
It also comes down to how soon you got on board .
I was one of the first to download and install the Vanilla ROM before the WXML release was announced, and for me at this point there is no point in changing (especially after just getting my software how I like it ). Remember there will be most likely several releases of WXML over the next couple of weeks, so my advice is if you're already on Vanilla there is not much reason to move to WXML .10 at the minute .
Click to expand...
Click to collapse
Me too, and I used it for a grand total of 10 hours before I downloaded WMXL 0.1. And I'm glad I did. I like the software packaged with it, and I like the restored Office and RDP icons. I'll probably stick with this one for a while, but I am glad I went to WMXL from the Vanilla ROM.
guilherme said:
I've a tytn in Portuguese unlocked, can I install vanilla or wxml?
thnks
Click to expand...
Click to collapse
How about both?!? You like that, don't you? Yeah baby...

hmm that's great, and if I want to get back, that's possible?
thanks for the reply

[ThinkTank] Getting an AOSP Eclair build for Hero

We have had alot of activity over the last few days, what with the first 2.0 releases from the main players and now even some 2.1 builds. Which is excellent.
Maybe I am not 100% up to speed on the whole thing, but if AOSP 2.0 is "released" by google, then surely things like sync issues, etc shouldn't be in the source code?? I mean, the code should be as "bug free" as possible, so anything obvious like that would strike me as odd.
The reason I raise this point, is because I dislike the Rosie/SenseUI on my Hero, I would rather have the good, old Android standard like I had on my G1 - just what I prefer. However there are only beta versions of the AOSP eclair for Hero.
Would it be possible to build an AOSP eclair firmware, using the Qualcomm? proprietory drivers from someones leaked 2.1 image (working on an assumption that 2.1 has the same kernel base?) to produce a fully working Eclair 2.0 for Hero?
If I am way off the mark with this, please say, I'm just trying to think it through with the help of the people in the know.

Ditto. I am all for AOSP 2.0

richbayliss said:
Maybe I am not 100% up to speed on the whole thing, but if AOSP 2.0 is "released" by google, then surely things like sync issues, etc shouldn't be in the source code?? I mean, the code should be as "bug free" as possible, so anything obvious like that would strike me as odd
Click to expand...
Click to collapse
I think part of the "issue" is that whilst Google have release some 2.0 code to AOSP, it is not currently complete (see here). In addition, many of the Google apps (e.g. Gmail) are closed source, so you have to rely on prebuilt components which may, or may not, be compatible.
The long and short of it is that Lox is already doing what you are asking. The prerelease of HTC's 2.1 has possibly served as a distraction to the AOSP 2.0 build, but I'm sure once Google properly drops AOSP 2.1 code that work will be of direct relevance to the AOSP project.
Regards,
Dave

yeah exactly. just sit tight and wait for Lox_dev to finish his 2.1 Then he might look after the AOSP 2.0. and as AOSP 2.0 is running pretty fine without much hassle its fine if Lox takes some time before working on AOSP 2.0 . cheers

I'm with this idea!
I mean, just compare the 2.1 and 2.0 aosp videos; android 2.0 has much cleaner, and better transitions imo.
Design choices in 2.1 by HTC are, imo, bad as usual; the transparent notification drawer for example; what is the purpose? It's only jerky. And so on..

I suggest suspending judgement on HTC's 2.1 until they've actually released final code! Remember this is a leaked internal build - what ends up in the final ROM may be quite different.
Regards,
Dave

I think I have a clearer picture now, thanks guys.
I just wish that we could be in a scenario where we could flash a standard AOSP build onto our Hero's, sans the whole SenseUI, and have a basic usable phone.
I really dont get the whole "gmail is closed source" crap with Google. I mean, I can have Gmail on WinMo, S60, etc - but only on Android IF I have a license?? WTF! Crazy! Luckily, now that Gmail does support Exchange Activesync I don't need the standalone app anyway.
So the word on the street is wait.... which I guess is what we will have to do
I am keen to be able to build from source so I can start on a project I have in mind. Think along the lines of SenseUI, but a bit different.....

richbayliss said:
We have had alot of activity over the last few days, what with the first 2.0 releases from the main players and now even some 2.1 builds. Which is excellent.
Maybe I am not 100% up to speed on the whole thing, but if AOSP 2.0 is "released" by google, then surely things like sync issues, etc shouldn't be in the source code?? I mean, the code should be as "bug free" as possible, so anything obvious like that would strike me as odd.
The reason I raise this point, is because I dislike the Rosie/SenseUI on my Hero, I would rather have the good, old Android standard like I had on my G1 - just what I prefer. However there are only beta versions of the AOSP eclair for Hero.
Would it be possible to build an AOSP eclair firmware, using the Qualcomm? proprietory drivers from someones leaked 2.1 image (working on an assumption that 2.1 has the same kernel base?) to produce a fully working Eclair 2.0 for Hero?
If I am way off the mark with this, please say, I'm just trying to think it through with the help of the people in the know.
Click to expand...
Click to collapse
Forgive me if I'm missing the point, but we already have a fully working AOSP Eclair image for the HTC Hero. I've been using it for over a week, on a daily basis and other than the looping sync issue (which we are working on) it works fantastic..

jnwhiteh said:
Forgive me if I'm missing the point, but we already have a fully working AOSP Eclair image for the HTC Hero. I've been using it for over a week, on a daily basis and other than the looping sync issue (which we are working on) it works fantastic..
Click to expand...
Click to collapse
I wasn't aware that all issues apart from the syncing were fixed. I thought we still had issues with camera stability etc?? Is this not the case??

There are some minor issues with stability, but it's absolutely useable on a daily basis. I guess it would be better for you to list what your problems are or concerns, rather than making (what appears to me) to be a grand claim for concentrated work on something.
There are a number of us who are solely focused on getting AOSP Eclair working 100%.. but we're very nearly there. Having people contribute constructive information about what doesn't work would be the best.

jnwhiteh said:
There are some minor issues with stability, but it's absolutely useable on a daily basis. I guess it would be better for you to list what your problems are or concerns, rather than making (what appears to me) to be a grand claim for concentrated work on something.
There are a number of us who are solely focused on getting AOSP Eclair working 100%.. but we're very nearly there. Having people contribute constructive information about what doesn't work would be the best.
Click to expand...
Click to collapse
Believe me, I'll come back to AOSP soon with great things

That's an awesome news ! Thank you Lox !

Lox_Dev said:
Believe me, I'll come back to AOSP soon with great things
Click to expand...
Click to collapse
Thanks Lox, appreciated.

Lox_Dev said:
Believe me, I'll come back to AOSP soon with great things
Click to expand...
Click to collapse
Great news man! Thanks a lot! Holding my breath...

jnwhiteh said:
There are some minor issues with stability, but it's absolutely useable on a daily basis. I guess it would be better for you to list what your problems are or concerns, rather than making (what appears to me) to be a grand claim for concentrated work on something.
There are a number of us who are solely focused on getting AOSP Eclair working 100%.. but we're very nearly there. Having people contribute constructive information about what doesn't work would be the best.
Click to expand...
Click to collapse
I agree. The only reason I am now using Lox_devs Hero 2.1 1.4 instead of the pure Eclair one is that Eclair does not sync my exchange calendar. I just cant see why the calendar has been left out.

Sense or WinMo Only?

Hi folks,
Got my TP2 to replace my Uni just over a month ago (I know the TP2 is an old phone now, but I could not upgrade until now, and its taken me 4 years to replace the Uni).
Anyway, I love the phone, but my god is so SLOWWWW and so BUGGY and just generally unreliable. Now on my Uni, I was running a Hybrid of 6.1/6.5 that I put on it last May, and it is awsome, its not 100% stable, but it certainly feels faster and is far more reliable than the TP2.
Anyway, i have been jumping backwards and forwards between Sense and Windows Mobile "today" screen, and the difference in just that seems remarkable.
When Sense is running, not only does it seem to be using about 25MB more RAM, but it suffers a hell of a lot of slowdowns, SOD instances, and generally, whilst it can be quite nippy at times, the amount of times it just hangs or is slow, makes the phone next to useless!! I have to restart it at least 4 times a day, sometimes even more. Messaging is almost unusable, and the amount of times I have felt like throwing the phone in the bin is unreal (and cant be healthy).
Now when I turn the Sense off (as much as you can, it still interferes with messaging etc and makes it run like a pile of poo) everything seems lightning fast with very few slowdowns, and certainly no massive halts in what it is doing. I can't recall the last time I had an SOD problem, and I have had the phone on for 2 days now and not a restart.
When you get into pure WinMo interfaces (not made to look nice by Sense) they are so smooth, scrolling is as responsive as the iPhone (which I hate but it makes my TP2 look like a piece of poo and im embarrassed by it to be frank because of the bugginess), it appears to be all the crap HTC have done to the phone that is causing the problems.
Now I need to change the ROM for a more stable one regardless of anything, and have been considering the Energy ROM for about a week (reading up on it, still not clear how to change the ROM, jeeze it was so much easier with the Uni). I was originally considering the Std Sense 2.5 version, but after reading the coment about the Cookie HomeTab being how Sense should have been designed, I was considering that instead.
After running WinMo without the main Sense interface on the phone however, and seeing it running a lot smoother, I have been reconsidering my decision.
I need this phone to run with as little in the way of hassle as problem, I dont want to be constantly fighting a losing battle to keep it stable and reliable, I dont want to be taking 10 minutes to type a text or use IE (I do use Opera Mini for most things, but like IE from time to time) just because the interface is slowing everything down. Do peeps think that the Energy ROM with the Cookie HomeTab interface is the way to go, or does it still have issues, and I should stick with a stock install of Windows Mobile and only Windows Mobile.
I appreaciate your thoughts... I can't believe how HTC can release a phone with such bugged up software as this and actually expect consumers to use it, imho, my phone is not even as stable as one would expect the software to be in BETA stages, nevermind as a public release. I work on the development team for TopUp TV in Europe (we deal with the propietary software that runs on all the set-top boxes) so I know what to expect from public software, and this is certainly not fit for use, and if this is the way HTC are going, then the TP2 will be the final HTC I ever buy (in fact if I can't get it stable, it will be on eBay and ill be back on my Uni).
Current phone info:
OS Version - 5.2.21887
Manilla Version - 2.5.20121225.0
ROM Version - 2.07.401.1 (80303)
ROM Date - 02/04/10
Radio Version - 4.49.25.91

Shame to hear you had such bad experience.
I´m quite happy with my Rhodium, which tweaked properly works great!
And I also have an Uni

If you're looking on step by step instructions there's a sticky in the ROM Dev forum called "Flashing your first rom" if you have a GSM version (looks like it based on radio version). That'll take you through the how.
Now if all you want is a fast, stable rom, i'd recommend staying away from Sense 2.5. The fastest, stablest Energy rom is going to be the Sense 2.1 running on the 21xxx branch (currently 21901). See my sig for a link to the thread. Once you start going into the 23xxx branch or Sense 2.5 you start piling on additional features which tie up more resources. It's a trade off of eye candy for speed.

While I agree that HTC's Sense is generally more trouble than it's worth, aside from increased memory usage and occasional stuttering, it works just fine for me. I simply prefer the default WinMo interfaces. And I do not think anyone likes HTC Messaging, that part is horribly bugged and slow.
There are many ROMs or variants of which that do not have any Sense components built in, I believe there is an Energy ROM that uses Titanium as the default shell.
I would suggest to you the Cosmik Debris ROM here:
http://forum.xda-developers.com/showthread.php?t=608009
It is based on WinMo 6.1 so it will probably be familiar to what you were using on your Uni, and out of all the ROMs I've tried it seems to have the least amount of HTC software built in (there always seems to be some left, you will defiantly want to disable the HTC dialer).
If you do not mind the classic WinMo (pre-titanium) today screen, or plan on using a third party one such as Spb, I think 6.1 is a good way to go. I've not found any advantage at all to running 6.5 besides a startmenu that looks like it was just carpet bombed.

got no problems using Sense 2.5....if you dont like it, try Sense 2.1 which is hecka quicker than 2.5 just no Twitter tab....im only on Sense for the sake of twitter and the fact all info is there all in one piece

I'm with the OP... My Sprint Rhodium was working fairly well prior to my update to WinMo 6.5 (stock ROM)... Afterwards, the boot time was slow, sometimes Sense just wouldn't load at all. Going to any tab was initially, painfully slow. Loading apps was not TOO much slower than 6.1, but it was still leaving a lot to be desired. So about 4 days ago, I switched from Sense to the WinMo 6.5 default today screen.. BAM! Problems gone.
Don't get me wrong, I'm not hating on HTC's Sense, I think it's great, the UI is awesome, it's just buggy... Perhaps there's some versions of the phone (think: manufacturing batches) that have issues with the newer software. Because OP is definitely not alone.
Sticking with WinMo's 6.5 Default - Mark

I just don't think the rhodium has the ram or the processor for sense 2.5. I gave up on sense a while ago. and even though 2.5 with cookie 1.8 is very nice looking, I'll take my custom cooked 23563 sys with 3.5.3 mobile shell on top. very fast and not buggy at all. everything works as it should.
since you have tried it with sense off, try the trial version of mobile shell or just stick with titanium. Some people are happier with that.
fyi, I have never had a SOD with sense not on my phone.

I second the previous poster's recommendation of SPB Mobile Shell 3.5.3. I've been using it since V2, and it's great. It only uses 4-6 MB of RAM. It's about as customizable as one could wish for right out of the box. As for ROM, I've been using Sergio76's Leo Cell Pro version 9.1 for a few days now, and I haven't had any hangs requiring restart or SOD. I've had SOD's without Sense, but that was only in the 23xxx branch. Serg's Pro series is on the 21xxx branch, the latest being 21901 in V 9.1. It's made of win and profit. Make sure you grab the one with no HTC Messaging or CHT.

Best combination stays the stock HTC 6.1 ROM with TouchFlo for me. The TouchFlo interface is very light on the hardware and looks smooth.
The newer Manilla 2.1 looks nice, but slows down here and there, together with WM6.5 it eats RAM!
I tried the Manilla 2.5, and it looks ugly (to me) with the big fat icons at the bottom together with allot of lag It's very noticeble that it's designed for the HD2, wich has allot more horsepower!
I like the fact that TouchFlo still keeps things finger-friendly ^^
Grtz,
FeareX

FeareX said:
Best combination stays the stock HTC 6.1 ROM with TouchFlo for me. The TouchFlo interface is very light on the hardware and looks smooth.
The newer Manilla 2.1 looks nice, but slows down here and there, together with WM6.5 it eats RAM!
I tried the Manilla 2.5, and it looks ugly (to me) with the big fat icons at the bottom together with allot of lag It's very noticeble that it's designed for the HD2, wich has allot more horsepower!
I like the fact that TouchFlo still keeps things finger-friendly ^^
Grtz,
FeareX
Click to expand...
Click to collapse
The bottom icons are not Sense 2.5; they are the newer version of WM6. I am using 2.5, and my start menu is in the upper left, not the lower left.

stevedebi said:
The bottom icons are not Sense 2.5; they are the newer version of WM6. I am using 2.5, and my start menu is in the upper left, not the lower left.
Click to expand...
Click to collapse
The new Sense 2.5 has those 3 big shortcut icons at the bottom (which turn to 9 when sliding up); that's likely what FeareX means.

ridolfo said:
The new Sense 2.5 has those 3 big shortcut icons at the bottom (which turn to 9 when sliding up); that's likely what FeareX means.
Click to expand...
Click to collapse
Oh, is that Sense? I thought it was any WM 6 version with 6.5.x instead of just 6.5?
EDIT: Oh, the shortcut icons. I'm using Co0kies Home Tab, which has currently 25 shortcuts on 4 pages under my settings - 100 shortcuts. My ROM burned CHT into the mix and I've not used the "stock" sense 6.5.

stevedebi said:
Oh, is that Sense? I thought it was any WM 6 version with 6.5.x instead of just 6.5?
EDIT: Oh, the shortcut icons. I'm using Co0kies Home Tab, which has currently 25 shortcuts on 4 pages under my settings - 100 shortcuts. My ROM burned CHT into the mix and I've not used the "stock" sense 6.5.
Click to expand...
Click to collapse
You are confusing Sense, which is an HTC UI, with Windows Mobile, which is an operating system.
Sense UI comes in three different versions for our phone:
Sense 2.0 no eye candy, stock
Sense 2.1 colored slider, programs tab
Sense 2.5 Twitter, facebook tabs, quick launch icons on homepage
Then there is WM, which has too many versions for our phone:
WM 6.1
WM 6.5
WM 6.5.3
WM 6.5.5
Here is info about WM:
http://www.modaco.com/content/i9x0-...m/299717/com-branches-explained/#entry1153714

burtonsnow8 said:
You are confusing Sense, which is an HTC UI, with Windows Mobile, which is an operating system.
Sense UI comes in three different versions for our phone:
Sense 2.0 no eye candy, stock
Sense 2.1 colored slider, programs tab
Sense 2.5 Twitter, facebook tabs, quick launch icons on homepage
Then there is WM, which has too many versions for our phone:
WM 6.1
WM 6.5
WM 6.5.3
WM 6.5.5
Here is info about WM:
http://www.modaco.com/content/i9x0-...m/299717/com-branches-explained/#entry1153714
Click to expand...
Click to collapse
Actually, I think the OP was the one confused.
I don't think the original author was talking about Sense. I'm assuming he has the large soft keys found in the newer WM, which has the taskbar on the bottom rather than the top. Mine is OS build 21x; the bottom taskbar is builds 23x. That is OS, not Sense. But it was actually a bit difficult to make out what the OP was having problems with.

stevedebi said:
Actually, I think the OP was the one confused.
Click to expand...
Click to collapse
Not quite. He is saying with Sense UI loaded his phone is slow. Without Sense UI his phone is responsive but looks like crap.
I would suggest trying SPB mobile shell if you don't like Sense UI. Also titanium has some nice mods which can look good.

burtonsnow8 said:
Not quite. He is saying with Sense UI loaded his phone is slow. Without Sense UI his phone is responsive but looks like crap.
I would suggest trying SPB mobile shell if you don't like Sense UI. Also titanium has some nice mods which can look good.
Click to expand...
Click to collapse
I must be the only one left who thinks good old classic Windows Mobile today screen looks just fine.
Absolutely every piece of information you need on one screen in a simple functional list. Easily customizable as well.
It is a beautiful sight to see how quickly WinMo boots up without having to load Sense.

Thans for the all info folks, I have spent the past week or so plodding along with the standard WinMo interface, and considering my options, using the info in this thread a guide...
Anyway, I am pleased to say the slugishness and text messaging problems of the stock ROM even with Sense disabled got too much for me, and I ended up changing the ROM...
I took a risk and decided to throw a Sense ROM on to begin with, thinking what the hell, if it struggles, ill just change it as ill notice problems pretty quickly.
I went for the Leo Cell Evo 9.1 23562 running Windows Mobile 6.5.5 and Sense and WITHOUT the HTC Messaging crap that plagued the stock ROM... and so far, I have to say, I am extremely impressed, everything runs smooth and fast, with no crashing, no SOD (yet), no massive slowdowns or hangs, and Sense is at last a dream to use, it is working how it should be!!
I am absolutely made up with this ROM, but I am also appalled at HTC's decision to expect the stock ROM to be suitable for this phone, as its only really suitable for odd call every now and again (its a £400 smartphone ffs, people dont buy them for the odd call now and again).
The ROM totally puts HTC and their development team to shame, and they should be ashamed of themselves - I have emailed them to let them know of my complete disappointment with the phone compared to my old Uni (out of the box) as I felt it was not fit for purpose with the stock ROM installed, and have mentioned the fact I have changed to a custom XDAD ROM and finally have a phone that works as it should - but why should I have to do this, and how can they expect to sell these phones to people who are not so involved or interested in modding and ROM's etc (the TP2 is aimed solely at the business user as far as im concerned, indeed the conference calling features, and the fact only Vodafone Business sell it through their retail channel in the UK suggest this to me - I got it on o2, but from a 3rd party supplier, o2 themselves dont do the phone). A business user does not want a phone that gives them hassle, they simply want on that works and is productive, with the best efficiency and no problems.
Maybe its HTC's way of saying to the world "get over to Android and save us the license fee's for WinMo" because I can't honestly see why they would release such a flawwed product when the hardware itself is fine, when using a working ROM, which HTC are either unable to, or don't want to release.
Anyway, once again XDA Developers have come to the rescue, and a well earned donation will be going to the team behind the Leo Cell ROM's next week!!
THANK YOU!! :-D

How long till a 2.2 ROM will be usable?

Hey this is mainly aimed at Dev's,
How long will it be before a workable 2.2 ROM is cooked up, I think its just come out for the G1 with cyanogen 6, so it shouldn't be too long here?
Thanks guys!!

Cyan's 6alpha is quite usable even now. Just few issues like no preview in camera (but camera is taking photos correctly), and trackball isn't blinking for notifications.
But seems to work stable, and is almost fully functional

zbaracki said:
Cyan's 6alpha is quite usable even now. Just few issues like no preview in camera (but camera is taking photos correctly), and trackball isn't blinking for notifications.
But seems to work stable, and is almost fully functional
Click to expand...
Click to collapse
yeah, and its only a matter of time before all these bugs are ironed out one by one, especially as all the good dev's will be working on a 2.2 rom, they will manage to get everything fixed between them.

I second that, Cyanogemod 6 is working on my phone for the last two days, it's super quick and usable. If you can manage without Sense, it's a real charm.

Datrio said:
I second that, Cyanogemod 6 is working on my phone for the last two days, it's super quick and usable. If you can manage without Sense, it's a real charm.
Click to expand...
Click to collapse
Did u put it on via one of the nightly builds? Because i cant get the graphics to render correctly,

stickyasglue said:
Did u put it on via one of the nightly builds? Because i cant get the graphics to render correctly,
Click to expand...
Click to collapse
Use the alpha0 from CM Forum or the latest nightly from teamdouche buildbot.
(Both are the same version)

rootbox00 said:
Use the alpha0 from CM Forum or the latest nightly from teamdouche buildbot.
(Both are the same version)
Click to expand...
Click to collapse
flashing again now

I tried one of the nightly builds and nothing worked. The colours on the screen were all messed up — most stuff was lime green. And none of the buttons work and the touchscreen didn't work. I had to just take the battery out.

FunkTrooper said:
I tried one of the nightly builds and nothing worked. The colours on the screen were all messed up — most stuff was lime green. And none of the buttons work and the touchscreen didn't work. I had to just take the battery out.
Click to expand...
Click to collapse
tried the new kernel? i think that will be fixed if you flash it
download

FunkTrooper said:
I tried one of the nightly builds and nothing worked. The colours on the screen were all messed up — most stuff was lime green. And none of the buttons work and the touchscreen didn't work. I had to just take the battery out.
Click to expand...
Click to collapse
this one (07/12) works fine

Cyanogen 6 alpha for Hero http://forum.xda-developers.com/showthread.php?t=714923
worked for me

FunkTrooper said:
I tried one of the nightly builds and nothing worked. The colours on the screen were all messed up — most stuff was lime green. And none of the buttons work and the touchscreen didn't work. I had to just take the battery out.
Click to expand...
Click to collapse
read the thread about nightly builds. widely discussed with well documented easy to flash fix.
or, do as posted above your post and just get the latest from the new nightly buildbot or the alpha.

The 10/07 build (currently the latest one on the Cyanogen website) works fine for me - just no camera preview and some issues with trackball lights as mentioned elsewhere in this thread.
Works good enough for me to keep it on as my regular rom...

i think at the latest when the legend become its 2.2 update. then we are afloat with legend ports

essbee1958 said:
The 10/07 build (currently the latest one on the Cyanogen website) works fine for me - just no camera preview and some issues with trackball lights as mentioned elsewhere in this thread.
Works good enough for me to keep it on as my regular rom...
Click to expand...
Click to collapse
second that!

Fraqq said:
i think at the latest when the legend become its 2.2 update. then we are afloat with legend ports
Click to expand...
Click to collapse
that would be nice, but it's clear we won't have to wait that long. the only major hickup is the camera and they're working away trying to solve issues with it. Remember this is an AOSP rom (with cyanogen additions and changes), not a sense rom, and hardware support from 2.1 roms is ripe which is I'm sure part of why froyo worked so well right off the bat on the hero (again, other than the obvious camera bug, some media/3d issues (which if I recall seemed to be specific to a couple of apps) and some minor led notification problems).
strange though that the latest alpha build isn't as fast (measurably so and by quite a bit) as the original pre-alpha build was.
Considering the original had a sort-of camera thanks to camera magic it's really a more fun rom to play with than the later builds which ahve working apps2sd etc.
I hope they can get the speed back up.

I have a better question:
How long til 2.2 with Sense?!
any idea?
Desire has it as I know.

liljom said:
I have a better question:
How long til 2.2 with Sense?!
any idea?
Desire has it as I know.
Click to expand...
Click to collapse
froyo with sense seems like htc trying to make the most of the "sense" brand name now. I'd prefer a froyo phone without sense after having used my hero with nonsense froyo for a few days.
does sense on desire 2.2 have anything the older sense versions don't have? if not then it would take features away from froyo (such as froyo's contact integration, froyo's multiple exchange account support with multiple exchange calendars, just to name a couple of great features which are already in the current alpha builds).
UPDATE: I should add that Sense was an incredible thing in 1.5 roms. it's still got sexier widgets than most other non-sense widgets offer, although exceptions exist. But it stomps all over the way android works by offering it's own set of features (like exchagne support with calendar integration for one account).
now with froyo we have almost everythign sense offers and in some cases we have quite a bit better tools than what sense offers.
the worst part about froyo adn all vanilla roms is the dialer, so just download "dialer one" from the market for free and set it as your default dialer. it's at least as good as the sense dialer and integrates well with froyo and with all vanilla roms.

I understand what you say : )
I like the way I can dial people/numbers, I can write sms, I can call the favorites, the calendar widget, the notes widget.
You are lucky that you can get "your" Froyo now : )

liljom said:
I understand what you say : )
I like the way I can dial people/numbers, I can write sms, I can call the favorites, the calendar widget, the notes widget.
You are lucky that you can get "your" Froyo now : )
Click to expand...
Click to collapse
I'm sure you're happy now. I was happy with sense. I didn't understand that vanilla's sms, contacts, and so on are better than those in sense.
if you think your favorites setup is good now, just wait until your froyo setup has finished it's first update (this can take an hour or more if you come from 2.1 with lots of apps installed previously... google will try to reinstall them for you on your froyo rom!). you find your person in the contacts list and have instant single screen click-to-contact with every form of contact that person has enabled. sms, each phone number, gmail, exchange mail, gtalk, facebook, and more. it's quite a bit nicer than sense.
I think you'll like it if you actually give it a chance. Sense's feature list is getting pretty old now by android standards. launcherpro and adw launcher are dramatically better than the sense launcher too, especially imho launcherpro which is the only alternative launcher that is actually faster than the sense launcher even with live wallpaper running and 5 to 7 screenfuls of widgets and shortcuts (as I'm doing now).
I'm just telling you this because I'd hate to see someone disable great features in the new operating system by having sense installed because they don't realize that sense is actually overwriting the superior newer android features with sense's older and less integrated contact and email features.
I wish HTC would release their mail widget as a product for non-sense phones, it's really sexy. but the sense contacts widgets are pretty terrible compared to what's built into vanilla roms with launcherpro (the home screen contact shortcuts are brilliant and very sexy in vanilla). and the calendars from free products like jorte or gemini are excellent, integrated products, and have a great style of their own if you like that kind of thing (but they can only integrate calendars in froyo, not in 2.1 vanilla from my experience... so I suspect those developers will see a big increase in use of their great products in coming months).
sorry, too much caffeine here LoL
cheers
UPDATE: by the way, I don't expect you to say "oh wow, I didn't know that, I'll take your word for it" LoL. I just am hoping you and others will keep an open mind that "vanilla" doesn't mean "missing features" necessarily. seems to be my goal today, I'll stop posting about it now

FroydVillain 1.3.x/2.x Roadmap

FroydVillain 1.3/2.x roadmap
EDIT: Due to unforeseen issues rapidly accelerating the release of 1.3 (more framework changes), I'll edit this roadmap to reflect 1.4 as well as what we hope to accomplish depending on how many of the 1.3 promised features make it into the accelerated release. Thanks for your patience.
Now that FroydVillain 1.2.x is somewhat stable we can concentrate on the next releases.
First, any and all "WHENNNNNNNNNNN???????!!!!!111oneeleven" posts will be ignored. As usual, "when" = "when it's done".
Features/items in this roadmap are things you can definitely look forward to unless otherwise stated, ie, something happens that renders that feature impossible. Like an asteroid hitting my house, for example.
First, the preliminary work.
I promised the guys over at Cyanogenmod that my new build profile for the Hero (and other MSM7xxA based phones, so the Dream, Slide, G1, etc etc) will be tidied up and offered up in a pull request. I will be cleaning up my tree and submitting my changes before I begin work on the next release of FroydVillain. The main reason for this being, the closer the CM tree is to my tree, the less work involved in keeping the FroydVillain tree up to date with upstream fixes.
Right, so the changes.
Version 1.3.x:
Obviously it is customary to break some **** with each major revision just to give me an excuse to release another release after that broken release.
So for 1.3.0 I nominate, umm...nah I'll let you find out. A release post isn't complete without at least 20 posts asking if anyone is having xxxxx problem and a further 20 posts complaining about the said problem after I post that we're aware and we're very sorry and those responsible shall be flogged.
FroydVillain 1.3.x:
Further changes to the build base and source code to move Froyo-on-Hero further away from reliance upon Eclair libraries. We aim to be building a native libcamera.so in the same vein as the D/S guys are. This combined with already eliminating proprietary liblights makes it easier to...
Switch over to the Froyo prelink map. If you don't know what prelinking is, don't ask. Either don't worry about it or do some Googling. The upshot for you the end user should be better stability and maybe even some added performance improvements.
Along with the addition of the CPU profile to the CM base I'm hoping to get VFP support fixed in the kernel and in the dalvik source. VFP is your phone's ability to offload number crunching to a dedicated number crunch piece of hardware. The cpu the Hero has supports it, however support for VFP on ArmV6 architecture is a bit...well, pants. Accomplishing this should also give another measurable boost in dalvik performance since currently the only enhancement to dalvik, is the optimised binary, the source itself still trudges along with only armv5te support which again rather pants.
Giant /data partition. Thanks Maxisma and co. I'm not going to bring this in until we next need to do a wipe, ie, 1.3 since it resizes the mtd partitions. Coupled with old school apps2sd there should never be a single whine about space on /data ever again. Even dkelley could fit all of his dalvik cache data on it with his encyclopaedic collection of apps. Be aware this will be accompanied by an updated recovery.img so the different layout is supported. You have been warned.
Debugged Exchange support. I can't promise that this will appear in a 1.2.x update but I will get it in for 1.3. I don't use Exchange and so have to rely on others to help find the cause of the issue, debug it and test it. I can't believe after nearly 10 years dodging it, I'm back troubleshooting Exchange bollocks again.
Theme revival. Because Google were kind enough to provide no theming engine what so f**king ever (cheers lads) theming is a pain in the behind that involves hacking the framework. However because we now build from source rather than trying to crowbar bits in and out of a prebuilt HTC tree, it's significantly easier to produce themes from the newly built source tree. I'm working with Alex24 on a project to go with 1.3.x which will put Themes back into the OTA app and they'll be available at the same time as the new releases are. This also allows us to easily add more themes over time.
CMSettings/CMParts. After having a chat with the folks at Cyanogenmod they're more than happy for me to make the menu entry in settings feel more at home within FroydVillain instead of looking like a kicking and screaming rip off from the Cyanogenmod ROM itself. So those of you that have been hopping up and down for CMSettings functionality, it's coming.
Better GPS functionality/better radio functionality overall. For various reasons, changes made by Google, the fact we'll never have official "Froyo supporting" radios, bugs creep into the OS when it comes to using newer Google based apps that make use of the radio. We'll have some fixes for the slow GPS locking and the random reboot/crash when looking for a GPS signal. We're hoping we have mobile data+gps properly nailed down as well.
We're also going to look into different Gallery implementations. Gallery 3D is annoying as hell and the bugs with it are likely due to us relying on the Eclair GL libs. So no further ground is likely to be made until/if/when another MSM7xxA class phone gets Froyo which if any will likely be the Legend. That's a big if though. Imagine if you will, 50 metre tall letters I and F, draped in neon coating with a flashing, strobing sign above them announcing "THIS IS A BIG IF." But no whining if the best you get is the old 2D Gallery as I'm really struggling to find any decent Gallery implementation. Which is somewhat surprising. Perhaps we should offer a bounty for a new decent one.
Add further language support
That's all for 1.3.x for now I think. I'll update this as new things occur or as things appear to be impossible.
FroydVillain 2.x:
Kernel 2.6.34.
What? That's not enough? Wtf is wrong with you? Ok fine.
2.6.34 will provide official support for the newer Froyd features such as in built Tethering and no more annoying bull**** surrounding connecting a simple USB phone to a simple USB port on a simple Windows system. Apparently the Windows driver stack is easier to confuse than a 90 year old Alzheimers suffering dementia patient.
We'll also be looking to bring the Hero Froyo platform closer in line to the more complete Cyanogenmod D/S platform. There's really no reason why we shouldn't be able to especially once 2.6.34 is available since as far as the hardware is concerned the phones are practically identical.
More will be added to the 2.x branch as we discover it. Don't be surprised if in the course of working on 1.3.x some features get pushed back to the 2.x release due to practical limitations or it just making more sense.
Now is the time for feature requests from you the user. 1.2.x is now critical bugs only, I do not want to have to make you wipe/flash 1.2.x now until 1.3 hits so any fixes involving a framework rebuild won't appear until 2.x. 1.2.x is now considered feature complete in the scope of features we want to have supported. New features will appear in 1.3.x or 2.x depending on the work required to make them appear.
So the forum is now yours, dear users, to get those feature requests in. We'll endeavour to get as many implemented as we can. Any ridiculous or unobtainable goals will be identified as such as quickly as possible so people don't get their hopes up only for me to dash them like an abusive husband.

Thanks for all of the Froyo deliciousness you've provided us with! I myself will be waiting with baited breath for the next installments of Froyd.
p.s.
If you need more people with access to Exchange, or if you'd like an Exchange environment to play around with, let me know. I've got an Exchange 2010 machine sitting next to me.

Looking great! Hope you'll get that all working!

acolwill said:
Thanks for all of the Froyo deliciousness you've provided us with! I myself will be waiting with baited breath for the next installments of Froyd.
p.s.
If you need more people with access to Exchange, or if you'd like an Exchange environment to play around with, let me know. I've got an Exchange 2010 machine sitting next to me.
Click to expand...
Click to collapse
Ah, now that -would- be useful. [email protected] if you want to hit me up on GTalk.
maxisma said:
Looking great! Hope you'll get that all working!
Click to expand...
Click to collapse
Cheers bud! Check your PMs.

wow keep on the great work...

Flash? 10char

dpi295 said:
Flash? 10char
Click to expand...
Click to collapse
Impossible, it doesn't work on ARMv6 CPUs.

Ah, now that -would- be useful. [email protected] if you want to hit me up on GTalk.
Click to expand...
Click to collapse
Req sent. Gimme a nudge

dpi295 said:
Flash? 10char
Click to expand...
Click to collapse
Best we can do is see if we can hack over the Flash Lite stuff from Sense, but don't hold your breath.
In fact, you all should start a campaign and hammer the **** out of Adobe to provide an armv5te or armv6j version of the flash library. It's their fault, make them fix it.

Hacre said:
Best we can do is see if we can hack over the Flash Lite stuff from Sense, but don't hold your breath.
In fact, you all should start a campaign and hammer the **** out of Adobe to provide an armv5te or armv6j version of the flash library. It's their fault, make them fix it.
Click to expand...
Click to collapse
They won't do that, they aren't powerful enough..

I'd appreciate it if you would make an optional patch for people who want their phone unlocked by double clicking menu button.

Amazing work! Data Partition, Themes, VillainSettings... cant wait!
As for Feature Requests, +1 for a quick 2D Gallery

Nice post ninpo.

Thanks for your great ROM. I'd love to see better rtl language support in your ROM.

Really lame request, and probably easily fixed just by finding the pictures myself, but could you put all the nice wallpapers you had back into the releases?
It's obviously a very trivial request, but the wallpapers were always exceptional compared to my attempts of being sophisticated. I always ended up with either breasts or something Xbox related...

mobydeek said:
As for Feature Requests, +1 for a quick 2D Gallery
Click to expand...
Click to collapse
+1 for the standard 2D Gallery.
Tanks guys for your hard work.
Sent from my HTC Hero using Tapatalk

Woah, that's a lot of things to do, and some big ones too. Good luck on that, would be awesome to see these things done in the next months, though, take your time, no rush .
As for Feature-Requests: I only have one, and I don't have any idea if it's already done (I don't test many ROMs that often, I'll prefer to stay on my 2.1 Vanilla ROM ) or if it's even possible, so sorry for my Noobishness in advance. Now, I would love to be able to control the Music Player with the volume keys. Short presses change the volume, like before, and long presses skip the songs.

Screatch said:
I'd appreciate it if you would make an optional patch for people who want their phone unlocked by double clicking menu button.
Click to expand...
Click to collapse
Blue-K said:
Woah, that's a lot of things to do, and some big ones too. Good luck on that, would be awesome to see these things done in the next months, though, take your time, no rush .
As for Feature-Requests: I only have one, and I don't have any idea if it's already done (I don't test many ROMs that often, I'll prefer to stay on my 2.1 Vanilla ROM ) or if it's even possible, so sorry for my Noobishness in advance. Now, I would love to be able to control the Music Player with the volume keys. Short presses change the volume, like before, and long presses skip the songs.
Click to expand...
Click to collapse
We'll be putting a modified CMSettings back into FroydVillain in 1.3, so these features will be there automaticallymagically.
Yeah, it's a fair bit of work, but with HTC pretty much ditching the Hero we can take the project and make sure it's all done and done right.
There's collaboration with other developers on other projects for a lot of this, it's not just me or Team Villain making it all happen. I'll be pushing the fixed cpuprofile up to cyanogenmod and they can then work on it too, I'm working with Elemag on the 2.6.34 port, Maxisma brought the repartitioning stuff to everyone's attention for the Hero, etc. Proper open source development at its best.
It's well worth it too. Look how different the Hero runs with FroydVillain 1.2.1, I'm quite frankly disgusted that HTC never, ever, tapped all that potential.

I can't believe it, my hero will never die!
This is indeed great news and I can't wait!
I just wanna thank everyone involved, all the developers are doing a fantastic job bringing us things i never thought was possible on the hero, and I totally agree Hacre, it's a real shame that HTC ditched ther hero when there's still juice left in it!
Cheers!

e2zippo said:
I can't believe it, my hero will never die!
This is indeed great news and I can't wait!
I just wanna thank everyone involved, all the developers are doing a fantastic job bringing us things i never thought was possible on the hero, and I totally agree Hacre, it's a real shame that HTC ditched ther hero when there's still juice left in it!
Cheers!
Click to expand...
Click to collapse
Not to mention juice they never, ever bloody gave us. Grr.