Develop Bugs

[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.

Apparent Android 2.1 SQSH Really fast, and stable

Hey guys, i found the attached build from zenulator in the Vogue forum, been playing with it for a while and i must say it really great. The only problem i've found is that the WiFi is working. The problem appear to be similar to that which we had when the first eclair builds came out. I tried the updated rootfs to get the wifi to work but still no luck. Believe me guys if we can get this build together well it would really sweet!!
P.S. i have no skills in programming for linux, but still i'm will to help in testing further if possible.
Android Eclair 2.1 http://www.4shared.com/file/180373749/2e85c593/eclair-221209.html

wow, this system is really fast, i mean REALLY! fast....
and the startup animation (4 colours) is awesome!!!
in my opinion it's the best i've ever tested..
but... how about the MUSIC player app/spare parts? :/

It's 2.0.1 though, not 2.1.
zenulator said:
This is an Eclair 2.0.1 build taken from the 2.0.1 sdk image and parts of the droid/milestone/nexus and the launcher from manup456's build and also part of his build.prop. Settings reads this as 2.1 but it isn't. It's just for compatibility with some nexus apps.
Click to expand...
Click to collapse
That being said, you can just use the 2.0.1 build found on this forum. I'm not stopping you from trying zen's, but like I said, it's not 2.1. Plus polyrhythmic's build has wi-fi.
By the way, here are some screenshots I found of what is apparently Flan (2.1).

Hey guys, the eclair thread is already existed, it's not necessary to post another here, the only new thing is adding the Nexus One Bootanimation, nothing new other than that... and if you read Zen's thread carefully, you would know that the most important unsolved problem is the current Eclair build never sleep!!! the drainage is so bad that it's not for daily use right now...

tommywoods said:
Hey guys, the eclair thread is already existed, it's not necessary to post another here, the only new thing is adding the Nexus One Bootanimation, nothing new other than that... and if you read Zen's thread carefully, you would know that the most important unsolved problem is the current Eclair build never sleep!!! the drainage is so bad that it's not for daily use right now...
Click to expand...
Click to collapse
...Thank you for only repeating things I said in my post above yours. Oh wait, I said it didn't have sleep but then I edited my post, so that's one thing.

ok, fair enogh, but is it possible that the performance gains in this build could be done in the eclair 2.0.1 floating around? Becase i have used both and the performance of this one is actually alot faster!

Wow! Reaaly fast! Love it

Fast and stable!
Wifi is not working and the sound from speaker is broken intermittently...
I love this version....
Hope some fix for above problem...

Nosrahc said:
Fast and stable!
Wifi is not working and the sound from speaker is broken intermittently...
I love this version....
Hope some fix for above problem...
Click to expand...
Click to collapse
Polyrhythmic's Eclair build in this same forum has wi-fi...

Hi All
it is fast, but my current new updated version i had seen on the vogue thread was also fast, and some nice graphics:
See update link in : http://forum.xda-developers.com/showthread.php?t=587116

New Super Villain Hero _[ROM]

[mod edit]Links removed[/mod edit]
As the rom is now in beta stage and its not open to public yet, I cant tell anything about, but the ROM is really fast and reliable
[mod edit]Donation ware is not permitted as stated in the forum rules. Links removed and thread closed! Consider this first warning.[/mod edit]

Site is down.
edit....................and it's back!!!!!!

is this gonna be a vanilla rom?

And the fragmentation of the rom community increases :|

Agree
naenee said:
And the fragmentation of the rom community increases :|
Click to expand...
Click to collapse
I agree too

I think its ok to reveal a little more.
Currently its vanilla with few sense apps. JIT ADW enabled, extremly fast and stable.

i´m up and running for the past 24 hours.
pretty pleased.
It´s kinda hard to measure speed when your last rom was kimera 1.8 @ 710mhz
guess this rom is really good

whitealien said:
I think its ok to reveal a little more.
Currently its vanilla with few sense apps. JIT ADW enabled, extremly fast and stable.
Click to expand...
Click to collapse
vanilla with sense apps? - please explain

Site doesn't work?

harsha_aithal said:
I agree too
Click to expand...
Click to collapse
Agreed here too.
Same happens at MoDaCo rom's.

site does work fine.

ermacwins said:
vanilla with sense apps? - please explain
Click to expand...
Click to collapse
No rom does not have sense UI so the sense UI apps wont work but with this speed i can live without
ADW Launcher is really nice and it have 3D gallery,fast new drawer,
Its 80% Vanilla Rom

hey rastandroid, how is the widget called with all the applications?

Birba said:
hey rastandroid, how is the widget called with all the applications?
Click to expand...
Click to collapse
More icons widget you can find on market

I think one of the reasons for this 'fragmentation of the rom community' is the sheer number of one hit wonder winzip experts popping up.
There are so many roms which are simply duplicates of other roms that it's hard for actual developers to get the attention their ROM deserves.
Take RaiderX for example.
He's a great developer, and has helped myself and Behnaan out in the past - his ROM gets hardly any attention. Then... someone comes along and re-themes behero, or Villain, and gets twice as many views/comments and probably donations.
For the record; I never would have moved to Villain as a primary if this community had remained as it was in January this year. There were what... 3 ROMs on the go? Maybe 4. That's manageable. It feels very cluttered around here recently.
Please don't take me the wrong way - I love seeing new developers (Robin for example), appear with something fresh.
Now - to the actual ROM.
I will post the ROM on here the day it's ready for public release. The initial reports have been incredibly positive. A lot of people have said it's the fastest ROM they've every used - which of course is astounding feedback.
I can't wait to release it, but as the guys will tell you - there are one or two minor issues I need to iron out first.
I'm not releasing this as an Alpha/Beta/RC - this is going straight to Final, public release.
I'm very proud of it.

whitealien said:
Currently its vanilla with few sense apps. JIT ADW enabled, extremly fast and stable.
Click to expand...
Click to collapse
It's called "fusionilla" I think.

fanfare said:
It's called "fusionilla" I think.
Click to expand...
Click to collapse
That's either pretty funny, or pretty cheeky. Hehe

Can't wait to test it!
A lean Villain could be the ultimate pacifier of this forum.
Go for it guys!

nprussell said:
That's either pretty funny, or pretty cheeky. Hehe
Click to expand...
Click to collapse
Just taking one's chance, my friend.
Keep up the good work.

carrozza said:
Can't wait to test it!
A lean Villain could be the ultimate pacifier of this forum.
Go for it guys!
Click to expand...
Click to collapse
It's not too far off a public release. By the end of the working week I hope. Maybe Saturday!

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

CM6 nightlies: being developed, worth using!

Everyone's aware of froyd, chronos etc since they're actively being developed by people here but I've been using CM6 nightlies since they started being released and they work great! Music controls for lockscreen and a nice configurable power control widget have appeared in the recent builds. I don't even mind the lack of a changelog, more fun working it out for yourself
So, does anyone else use them? Have a look here: http://mirror.kanged.net/cm/nightly/hero/

:O i didnt know there was still work going into CM6 for Hero. Ive been checking one Github Commits page, there were no updates for a while and assumed ppl had given up!
out of curiosity, whos developing those nightlies?

I'm not sure - it's possible i suppose that the new features are just CM6 bits which happen to work ok and no-one's really working towards making it work better on the hero but lox should be back on the case in a couple of weeks and it's no more broken than the other roms....

Do we need to wipe for these, or can we flash them over the current alpha?

Is the camera working in this ROM?..

sinding said:
Is the camera working in this ROM?..
Click to expand...
Click to collapse
no, trust me you'll know when froyo gets a rom with camera working
[edit] actually, it kinda does... the preview only seems to update when something else is moving though, so for example if you press menu, it will work while the menu animation is going on, also auto focus actually seemed to work. So you can get a half-useful camera if you spam menu constantly or rotate the phone like mad. [edit]

The camera doesn't work right but it doesn't work the same way every time I know i can take photos, I just can't see what I'm taking photos of....
I've flashed each nightly over the previous one all the way back and had no issues, just a dalvik wipe each re-flash.

kieranc said:
... but lox should be back on the case in a couple of weeks ...
Click to expand...
Click to collapse
Exciting news! I was beginning to lose hope that the CM6 Alpha build would ever make it out of Alpha.
For those that didn't see it, Lox tweeted this morning with that update.
https://twitter.com/LoxDev

where can I find google apps for this?

no market??

yeah, you miss things 'cause you need to install google apps
I just don't know where to download

on feeyo's website on froyo 2.2 is a link with google apps
http://www.cronosproject.org/forum/viewtopic.php?f=20&t=198
just not sure if you can flash them over this one..
don't know wich ones are included either, but it's worth a shot
grtz

this is the gaps for CM6 nightlis build:
http://www.multiupload.com/9LJMNBHOXF
and this is the link to the original thread of @maxisma:
http://forum.xda-developers.com/showthread.php?t=717824

maxniper said:
this is the gaps for CM6 nightlis build:
http://www.multiupload.com/9LJMNBHOXF
and this is the link to the original thread of @maxisma:
http://forum.xda-developers.com/showthread.php?t=717824
Click to expand...
Click to collapse
thank you : )

There's a newer version of the gapps for cm6 here:
http://www.multiupload.com/DPC7H4DDFO

kieranc said:
Everyone's aware of froyd, chronos etc since they're actively being developed by people here but I've been using CM6 nightlies since they started being released and they work great! Music controls for lockscreen and a nice configurable power control widget have appeared in the recent builds. I don't even mind the lack of a changelog, more fun working it out for yourself
So, does anyone else use them? Have a look here: http://mirror.kanged.net/cm/nightly/hero/
Click to expand...
Click to collapse
I stopped flashing them when I found zero differences in them between builds that were 3 or 4 days apart.
I'm happy they're adding little things still, but the changes I see in cronos and fusion (in particular) are far more dramatic and useful than what I saw in the nightlies from maxisma et al.
The nightlies were the first, and originally the best (and only) froyo. I loved the original test0 build, it was so solid and fast, but with lots of broken bits.
However with the new cronos from yesterday and fusion as an alternative, and froyd of course which hasn't changed in a while but is always solid, fairly quick and runs well... I'd trust those over nightlies any day.
Nightlies aren't meant for mass use or stability - any nightly could suddenly break things. I know they're pretty solid now but it's because thy're not doing significant things either, adding little widgets etc is nice but not really amazing or anything.
I'll stick with Cronos which I'll bet you performs faster in gpu results.

kieranc said:
The camera doesn't work right but it doesn't work the same way every time I know i can take photos, I just can't see what I'm taking photos of....
I've flashed each nightly over the previous one all the way back and had no issues, just a dalvik wipe each re-flash.
Click to expand...
Click to collapse
that is all exactly the same with all froyo roms on the hero.
so if anything is thinking "hey, well in that case I'll flash the nightly so I can at least get SOME previews and some camera operation", it's exactly as with froyd, fusion and cronos. occasional previews, autofocus that works then makes it out of focus again before taking the pic, some crashing of the phone, some gps getting stuck on with camera magic, zero video recording.

For people who think of changing...
Nightly Builds from 6/8/2010 !
Froyo 2.2
Advantages:
- JIT and Compcache on/off
- Overclockable ( to 710MHz )
- all 2.2 benefits otherwise
Bugs (as far as i know):
- Camera (like all 2.2 roms)
- Landscape in gallery 3D
- Battery life isn't that good (imo)
Scores:
- Linpack: 3,531 MFLOPS (JIT on) / 2.32 MFLOPS (JIT off)
- BenchmarkPI: 10863 ms
Screens in attachments
grtz

I've been using the nightly builds, and like it a lot. I've requested changelogs though, but sadly I still haven't got any response on that matter. I don't notice that much differences between the nightly builds, but a few things I noticed lately:
1) browser doesn't FC when closing the last tab anymore
2) music controls on the lockscreen (provided by koush for CM6)
Would be great if we could keep track on changes in this thread. I love changelogs ;-)

opera mini has stopped working for me over the last few days which has made me realise how slow the stock browser is... might have to do something about it.
edit: opera working again in latest nightly