Develop Bugs

Nexus One ROM/OS on Hero?

I bought my Hero a few weeks ago because I dug the SenseUI (it looked better than the standard Android UI) and because there was an update to 2.1 promised.
At the moment I'm a little bit afraid of two things:
1. There will not be an update. There really are great apps out there requiring 2.0+ and many features I could use like built in VPN support.
2. If there will be an update it might look ugly as hell. From what I've seen from the leaked Expresso ROM, I can only hope that they won't do that ugly **** for the Hero update... actually I just hope they will never really release that design. The current SenseUI looks original, slick, elegant, starting with the home screen, to the individual app icon designs. Sounds stupid, but that stuff really looks neat unlike the Expresso UI I've seen (oh, too much rambling here)
Now, if all goes bad... is it possible to extract the Nexus One ROM and use it on the HTC? After all the Hardware is not too different and should work with a little bit of adjustment.
In general, I'm really amazed by what is going on here... but most ROMs seem to be a modification/theming orgy rather than a decent port of a decent, more advanced OS version. I don't mean to offend anyone. After all, these ROMs are great for people interested into all that modding and theming and all. But for me, it's important to have a nice looking and working OS, not so much community modifications.

well you can't argue about taste, so i'll leave that part out. my bets would go on something looking at least similar to the espresso leak.
there will be an update, that's for sure. it is only a matter of time, i hope not too much time...
about porting the nexus rom, i wouldn't hold my breath for it. the hardware might be not so different, but from how i see it the hero is a ***** when it comes to hardware. this is also the reason why there is only about a dozen roms at all, and the only one without compromises is mcr. look at the g1 section, they literally drown in roms.
and for starters, the nexus has the snapdragon cpu, which seems to be at least one generation further evolved when it comes to mobile computing power, i don't see it coming...

don´t worry .
i read a rumor in the morning that htc is going to release on february 15th

Yes, we will get Nexus version.
Simply put, Nexus is pretty much standard 2.1 Android.
so far, people like Lox have been working on getting version 2.0 & 2.01 running on the Hero, but now that 2.1 SDK has been released they will start working on that. But it will help when HTC release the source code for their own 2.1 version as that will give them all the drivers etc they need.
The only thing I can see causing problems are the live wallpapers, but I believe that people are getting these to run on the G1 so you never know what is possible.
I've been running 2.0.1 software with all the latest gallery,navigation etc apps for a while now so expect 2.1 versions soon.
PS I installed the Expresso version on my phone and uninstalled straight away. Reminds me way too much of HTC's Windows Mobile software !

GXFX said:
don´t worry .
i read a rumor in the morning that htc is going to release on february 15th
Click to expand...
Click to collapse
and where did you read that?

furrypotato said:
people like Lox have been working on getting version 2.0 & 2.01 running on the Hero, but now that 2.1 SDK has been released they will start working on that. But it will help when HTC release the source code for their own 2.1 version as that will give them all the drivers etc they need.
Click to expand...
Click to collapse
Two points!
1. The 2.1 SDK is *not* the source code for Android 2.1. The the tools and libraries required to build Android 2.1 applications, not the OS itself. As far as I'm aware, the 2.1 OS code has not been dropped into the AOSP (Android Open Source Project).
2. HTC are only required to release the source code to the kernel as this is licensed under the GPL, though this will contain the hardware drivers. HTC's version of 2.1 itself does not ever need to be released as the Android source code is licensed under the ASL which is not a copyleft license.
Regards,
Dave

furrypotato said:
that will give them all the drivers etc they need.
Click to expand...
Click to collapse
yeah, i wouldn't be so sure about that. the kernel sources for the g1 kernel .29 are out, doesn't help a tiny bit for the hero so far...

kendong2 said:
well you can't argue about taste, so i'll leave that part out. my bets would go on something looking at least similar to the espresso leak.
Click to expand...
Click to collapse
You are right of course... if they release an upgrade to 2.1 it's logical that they develop and use that for the Espresso. So I guess it will be the same as the Espresso ROM. I just hope that the Espresso ROM won't look like the leaks.
While you can't argue about taste... you have to admit, that the UI looks (stylewise) quite different to the original Sense UI. Usually I wouldn't mind change. Just take Apple's UI, or Google's UI on the web as well as in Android releases. They usually stay the same, sometimes adding more colors, using gradients, etc. and you still recognize the original style. It usually takes very long until a system has changed so much that you can't recognize it's origins. Take the difference between XP and Vista. Was quite huge. Now the difference between XP and Win7 was minimal (stylewise).
Now, in the leaked Espresso rom I can't recognize the old SenseUI at all, except for the widgets, which can be removed / customized anyway and are not the main concern of HTC's developers right now.
Well, in case it looks to my disliking:
I know, that Sense UI as a whole is not just a plugin but the visually relevant parts (home screen, lock screen, mesages app, mail app, contacts app etc.) are mainly applications, right? (Well, the designs for menu lists, like in "settings" are not apps I guess, but they don't bother me as they look the same in the current UI version) How hard do you think would it be to extract the old apps and replace their counterparts in the new ROM?
This could maybe even be done without rooting, like it's possible for the lock screen and home screen. I dunno about replacing the Standard htc apps though.

felikz said:
and where did you read that?
Click to expand...
Click to collapse
Look here - http://www.androidcentral.com/rumors-say-european-htc-hero-get-android-21-february

Sir_Oliver said:
Look here - ...
Click to expand...
Click to collapse
Well the rumor that it's going to be released in February... come one... HTC said it will release in 1Q2010 which leaves January to March. February is right in the middle so they just say February.
That alone, ok, but what about the list of features. It seems to be put together from previous rumors and leaked ROMs noone even knows of whether they apply to the Hero update.
I'd take such a rumor, originally from some obscure Polish website (not to say anything against Poland, but it's a local website and the rumor hasn't surfaced from a more global site anywhere else), with a (huge) grain of salt.

I'm with Olafos here. I've now tried a 2.0 and 2.1 ROM, but come back to MCR3.1 within a few hours. It's not even all totally about visuals, as I think had been mentioned. The contacts widget, giving me my favourite contacts on my homescreen is used a lot by me. The group text is used quite a bit too.
The contacts, messages and other things just don't look very nice on standard 2.1. When the Bravo comes out (or before) with 2.1 have these cool Sense UI additions?
How much different will the Nexus One be to what 2.1 on my Hero looks like? Right now it's totally put me off upgrading. I really want a bigger screen and snapdragon CPU, but I would miss the amazing UI and funcitonality of my Hero on 1.5 with Sense UI :-/

olafos said:
You are right of course... if they release an upgrade to 2.1 it's logical that they develop and use that for the Espresso. So I guess it will be the same as the Espresso ROM. I just hope that the Espresso ROM won't look like the leaks.
While you can't argue about taste... you have to admit, that the UI looks (stylewise) quite different to the original Sense UI. Usually I wouldn't mind change. Just take Apple's UI, or Google's UI on the web as well as in Android releases. They usually stay the same, sometimes adding more colors, using gradients, etc. and you still recognize the original style. It usually takes very long until a system has changed so much that you can't recognize it's origins. Take the difference between XP and Vista. Was quite huge. Now the difference between XP and Win7 was minimal (stylewise).
Now, in the leaked Espresso rom I can't recognize the old SenseUI at all, except for the widgets, which can be removed / customized anyway and are not the main concern of HTC's developers right now.
Click to expand...
Click to collapse
ok, point taken
olafos said:
Well, in case it looks to my disliking:
I know, that Sense UI as a whole is not just a plugin but the visually relevant parts (home screen, lock screen, mesages app, mail app, contacts app etc.) are mainly applications, right? (Well, the designs for menu lists, like in "settings" are not apps I guess, but they don't bother me as they look the same in the current UI version) How hard do you think would it be to extract the old apps and replace their counterparts in the new ROM?
This could maybe even be done without rooting, like it's possible for the lock screen and home screen. I dunno about replacing the Standard htc apps though.
Click to expand...
Click to collapse
i have no idea about backward compatibility of the android system... just try it with one of the 2.0 roms? i'd bet on foobar if you mix 1.5 sense parts with 2.x, but don't let that stop you from romcooking

I just realized I said:
"Now the difference between XP and Win7 was minimal (stylewise). "
Of course I meant Vista and Win7
Ich will nicht wirklich eigene Roms machen...mir fehlt leider die Zeit. Hoechstes der Gefuehle waere evtl. zu rooten und zu schauen was läuft
I think Android apps are backwards compatible, not so sure about the HTC Sense UI integrated ones though.

Which Android Version/Mod with camera and voice search working ?

Hi, developers.
I think that maybe we are losing focus on building a stable and nearly all-functional version of android for kaiser.
Everyone of us has a new app, new feature, requiring an all new mod or version to be installed. We are just replicating the millions of flavours of linux.
That means different energies that, in my opinion, could be collate in one or two major version. This is the spirit of open source community and xda community.
Why simply stopping developping hundreds of mods, backgrounds, subversiones, etc. etc. and focalize on making camera working ? And voice search ? The new google voice maps uses it and having it fully working should be awesome.
Thanks for attention. Just my 2 cents, as someone said
TheMac

Myn's Donut is 100% working as far as I know. There are bugs still, but everything works.
The problem with a lot of Android builds is that they focus too much on a customized UI, rather then fixing existing issues and improving stability and performance.

Dukenukemx said:
Myn's Donut is 100% working as far as I know. There are bugs still, but everything works.
The problem with a lot of Android builds is that they focus too much on a customized UI, rather then fixing existing issues and improving stability and performance.
Click to expand...
Click to collapse
its the same as in WIMO dev. builds are easy. you take the tree and add some tweaks or themes or apps.
fixing problems requires work on the kernal and experience. dont complain about current status unless you intend to do something about it. the people releasing builds usually dont dev the kernal. i know i cant do either.
donate money (to dzo) or do some work or quit complaining
BTW if you spend time reading you would know that there are only two major trees. MOST come from cmod 5.0.7 and mmissions work porting them. wyn seems to be using another branch closer connected to his donut work.

Constructive criticism is not the same as criticism. For example, this thread expresses the concern over charging.
There lots of developers who deserve praise and more, and then there's people who like to put Donate buttons in their sig for no good reason. Not pointing out anyone.

Dukenukemx said:
and then there's people who like to put Donate buttons in their sig for no good reason. Not pointing out anyone.
Click to expand...
Click to collapse
id say most people here dont deserve donation, especially me
still fun to hope i guess

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.

Android 2.3 (Gingerbread) Being Pushed To AOSP

http://www.androidpolice.com/2010/1...3-gingerbread-being-pushed-to-aosp-right-now/
go, go, go! )

These are very good news
I already see my Hero running CM 7
:happy face:

Excellent News Lets see who get's their GingerBread ROM out first

Sweet, if the hero really will be supported!

Cooooooooooooooool man very nice go go go go gooooooooooooooogle

Tchuup-tchuup! Hotness train is leaving the stations

ummm...
yea. will be interesting to watch... if it works on hero it will be fun... I don't expect devs will take the time on the hero any more like they used to but if someone out there has the know how and time and dedication then it's probably possible.

dkelley said:
ummm...
yea. will be interesting to watch... if it works on hero it will be fun... I don't expect devs will take the time on the hero any more like they used to but if someone out there has the know how and time and dedication then it's probably possible.
Click to expand...
Click to collapse
Feeyo...

Good news
Sent from my HTC Hero

C0mpu13rFr34k said:
Feeyo...
Click to expand...
Click to collapse
should be interesting to watch his progress

I wish the technical know-how would be something well documented.
What I mean is, ive seen lox/benocharm (sp?) progress in the last year in terms of Android knowledge, almost from the start. Ive seen one of these two guys post about initial questions about how things work, then edit his own post to do a mini-FAQ on ROM cooking. Now today it would look like they would kick some major ass at doing it if they were still able to give time for this, because they know the Hero hardware by heart; they know the usual glitch when porting (ie: how to make camera/bluetooth work, etc), all the minor details that makes a ROM usable or not for a day-to-day ROM! However, this kind of knowledge seems not so well documented.
What i'm basically saying is if a developer bails out the documentation about how to rebuild a custom ROM does too. It looks like (from a non-cooker point of view) that there is no centralized Wiki or webpage about the usual generic steps or roadblocks when porting from another device or when starting from AOSP to build FOR an Htc Hero (or any device, too).
Personally i know enough about linux in general, ive build a few updates.zip for my own knowledge's sake (nothing fancy though, removed/added apks ), but I have my questions on how to properly make something not built specifically for an Hero work with all the hardware functioning. I'm sure many others are in the same boat (plenty of tech knowledge but lack of Android ROM resources). For example, the question I had in mind were in the form of:
Does specific hardware components (gps, wifi, bt) relies on linux kernel modules? Does it need some kind of special APKS or Jars to make it work along with the framework, or just kernel modules are enough once loaded?
Following up on the point above: would copying modules from another device specific ROM would be sufficient? (I guess not), what about Android release versions (Eclair, Froyo, Gingerbread, etc)? Can modules work regardless of the Android version being run on?
ETC...
Well its pretty much a long rant, but since i'm stuck with a 3 year contract on Telus with an HTC Hero, I wouldnt mind giving a bit of my free time to make a working ROM out of it. However I am/was under the impression that the Hero ROM development scene went to a stop once Cyanogen started supporting Hero (seems to me there are only two *major* roms out there, CM and VillainRom), and due to that ROM cookers stoped caring about the Hero since it was well enough supported as it is (with CM on board).
Thanks for listening, doctor

I'm actually in the process of setting up an Ubuntu virtual box to dive right in, when I saw the AOSP sources getting pushed I thought why wait? Why not try it myself?
Don't expect anything soon. First of all I am just going to build off the Cyanogen tree and see if I can make a working ROM, then I will look into the deep dark hell that is porting software to HTC's proprietory-drivered-up-the-ass Hero

l0st.prophet said:
I'm actually in the process of setting up an Ubuntu virtual box to dive right in, when I saw the AOSP sources getting pushed I thought why wait? Why not try it myself?
Don't expect anything soon. First of all I am just going to build off the Cyanogen tree and see if I can make a working ROM, then I will look into the deep dark hell that is porting software to HTC's proprietory-drivered-up-the-ass Hero
Click to expand...
Click to collapse
Any luck with it? I had the same idea, reading now a lot of information about building a rom.

Maybe we can post some useful links or tutorials about building ROMs in this thread so that we can kind of collaborate?

That would be a great idea, i really like the idea of building my own rom. or at least try to build one.
Here you can find how to setup your own machine to build android roms
http://source.android.com/source/download.html
if you have problems with installing sun-java5-jdk follow the instructions on this page:
http://blog.enea.com/Blog/bid/32050/Ubuntu-9-10-Java-5-and-the-Android-Open-Source-Project

Also checkout Cyanogen's wiki, they really did an excellent job there:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Hero

I'm progressing... slowly. Downloading Ubuntu 10.10 iso, 200MB of updates, the SDK, Eclipse, the ADT plugin, all the platform updates and GIT is taking a while on < 2Mb connection...

Especially the repo syncing... that just takes ages ;

krispijn_s said:
Especially the repo syncing... that just takes ages ;
Click to expand...
Click to collapse
Gives me time to read I spose! I totally understand how to build off Cyanogen's code, that sounds simple, but I get a little lost when it comes to syncing with AOSP or branching Cyanogen to make changes... but I got hours of dowloading yet so I can read up about it then!

Make sure you download the x64 version of Ubuntu. Since 2.2.1 you need a 64-bit system to compile the Android OS project.
Also don't expect to get it compiling right away, I reckon somekind of cpu-profile is missing (could be named different). Third I heard that the sound and camera (again) systems got changed, could be buggers to get those working.
Just my two cents