yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] hotaru:
i did that and got it to boot. i'm uploading a flashable zip now.

edit: here it is: kaosgingerbread-v2-heroc.zip
[Hero CDMA Android Development] Porkrinds:
removed text
[Hero CDMA Android Development] hotaru:
it'll probably be pretty much the same as building aosp froyo... but it won't be possible to build gingerbread from source until google releases the source.
[Hero CDMA Android Development] dean.d:
HA, sometimes you gotta fake it to make it. My fake @$$ gingerbread hero.:p

View attachment 458167View attachment 458168

I grabbed the some framework earlier with gingerbread baked in.
[Hero CDMA Android Development] hexskrew:
they released it yesterday. BTW great work hotaru, but how far did it boot? Though the Eris IS as close to the Hero as you can get :p

But yeah, the ultimate goal here is to have a full walkthrough of how to build 2.3 from source specifically for the Hero so we can start devving out new roms asap :)

@dean.d at least your honest on the fake! lol. Hey btw, that would make a nice theme for 2.2 for now.

@smoothtaste thanks for the heads up. I forget theres an irc for almost everything these days :p
[Hero CDMA Android Development] criptix:
lol im hopeful boots up fine i still think they should have changed the ui a lil more than some color adjustments but eh. It boots all the way just camera, wifi, bluetooth, audio dont work....the browser loads web pages faster but it keeps closing itself plus its a lil laggy but hey this is the first attempt and im very impressed.
[Hero CDMA Android Development] criptix:
10 chars my bad
[Hero CDMA Android Development] hexskrew:
Nah it's fine. These are legit responses, I just didn't want 10000 replys of "OMG IT'S 2.3 4 T3h H3r0 yay!", and then "Why isn't 2.3 working yet? Where is it?"

It's all good it happens.

I dunno if it works with java6 or not (I just uninstalled because of the said "incompatibility") but that was what I was going to do. Research cm6 building and then cross-reference with building 2.3 AOSP as per google.

I think the biggest question I have is how to pull the driver source from the 2.1-ish kernel, or do we need to worry about that at all and just shove another kernel into it? As far as screen resolution and such I think I have a good idea on where to change the variables for that.

The one other big question I have is what do we use to replace gapps?! I mean we could always just shove another market into the rom but what about gmail and etc? Not even sure if 2.2 gapps will work or if we have to wait for google to put it out :X

Well off topic as it is, I have to go get a new tire put on my car (damned is my wallet)... Will be back on soon.
[Hero CDMA Android Development] criptix:
Well none of the hardware except radio and touchscreen is working I also installed gapps market works but a lot of apps are missing my gmail sync worked just fine. Seems like they will work only thing that was acting up in my brief test was the browser like I said in my last post. I also flashed the newest cfs kernel no bootloop.
[Hero CDMA Android Development] Asadullah:
My suggestion is this there are quite a few of us that are trying to learn how to compile from source. We should get together and figure it out then make a how to video.

On another note I read Java doesn't work for compiling beyond version 1.5 or 5 the one with 5 in it :D
[Hero CDMA Android Development] hexskrew:
Yeah it's java 5 that you have to have (or rather java 5.? or higher.. cant remember the exact revision number). I havent' found how to find anything else besides jdk/java 6 on ubuntu 10.10. If you have better luck with an earlier version then holla back! lol.

HAHA! I was looking right at it:

sudo apt-get install git-core gnupg sun-java5-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev

For those of you like me using ubuntu 10.10, check the 2nd post for a link to a blog on installing jdk/java 5.
[Hero CDMA Android Development] Twolazyg:
AOSP just posted a gingerbread rom.... haven't tried it but go check it out! hope it helps.
[Hero CDMA Android Development] hexskrew:
Bumped for importance. This thread is taking a turn..

BTW, this thread is supposed to be about gearing everyone up for the SOURCE CODE release. My bad, I didn't realize at first that like what aosp has done is just pulled the rom from the sdk emulator and changed the kernel to use with the Hero. Which is why until we get the source to dev on, we won't have radio access as of course the sdk is compiled just to simulate radio access.

So as of right now my linux box is fully set up to sync with the repo (actually it is currently sync'd) however meaning when google releases the source to gingerbread.

So as of now we need to go back to 2.1 aosp and compile some info on what to edit to get it to our needs, so we can make as speedy of a development as possible once the source hits.
[Hero CDMA Android Development] CrashV2010:
I just want the music from the video.... PM me plz with the name title of song please..
[Hero CDMA Android Development] Asadullah:
I think that we should do what we can with the current rom until the source drops I got mms fixed and roaming fixed using the same technique I did with my mytouch 32b rom (off subject they never released the source code so can't really continue but who cares we got 2.3 coming out). I think we can figure something out with the sound. I miss darchstar
[Hero CDMA Android Development] Decad3nce:
Not much we can really do to get sound fully working. We'd be poking blindly in a hex editor praying to figure out the problem. Source code should be right around the corner with the Nexus S release afaik.
[Hero CDMA Android Development] Asadullah:
Yeah they can't have phones with with gingerbread before there new baby. Didn't darch have most functions working before they release the froyo code
[Hero CDMA Android Development] hexskrew:
What? Lol.

To everyone else, D3cad3nce is right. Not much we can do right now. Yeah we can mess with stuff, change files around and hope it has a bearing but doubtful because the basic structure isn't looking for it and it would be more trouble than what it's worth cause we would still be starting from scratch once they release the source code even if we did get some things working with this sdk rom.

As of right now the only people who could benefit is folks like the creators of a2sd to get their apps working on the new system, but that's about it.
[Hero CDMA Android Development] TpyoKnig:
GB source

http://phandroid.com/2010/12/15/gingerbread-source-headed-to-aosp-soon-now-the-real-fun-begins/

"

Google’s Jean-Baptiste Queru has tweeted that once the Nexus S hits shelves we can expect the Android 2.3 source to hit the AOSP in no time.

"

SWEEEET!!!!!!!!!!!!!
[Hero CDMA Android Development] hexskrew:
That's tomorrow!!!! That probably means day after tomorrow! (or even tomorrow!) lol.

Or hell actually at the time of this posting it's today! Maybe even today! (ok, I'll stop now)

All I know is we have ginger creeping in our bread and we'll be munchin' on it fresh out the oven VERY soon :D
[Hero CDMA Android Development] TpyoKnig:
I know I keep hitting F5 like it owes me money on the android source page of the git repo
[Hero CDMA Android Development] halrulez:
Wow dude really? Go out side take a walk it will be good for you.

Gingerbread... It's what heros crave!
[Hero CDMA Android Development] hexskrew:
Slap that ***** like she screwed your brother! Lol.
[Hero CDMA Android Development] TpyoKnig:
its 29 degree outside and sleeting, aint no way my arse is going out there :)
[Hero CDMA Android Development] halrulez:
I'll trade you weather it's 60 here in cali the bay area. To warm for my thick blogs

Gingerbread... It's what heros crave!
[Hero CDMA Android Development] hotaru:
really? last time i checked, 7:00 AM was earlier than 12:26 PM.
[Hero CDMA Android Development] hexskrew:
Whatchu talkin' bout willis?
[Hero CDMA Android Development] TpyoKnig:
Hotaru, calm down, I know you ported it before AOSP, only reason I believe that it didn't get noticed is because it was not a topic on the forum (ex: hotaru gb rom) etc.. it was put under a thread and not a new one started :)
[Hero CDMA Android Development] hotaru:
i really don't care... just thought it was kinda funny that it said that when there was an earlier one on that same page :p
[Hero CDMA Android Development] :
kernel.org servers are in for a world of hurt. even with the warning from Google to wait it out if you aren't doing end-user work right away (which I'd say we are!)
[Hero CDMA Android Development] hexskrew:
Sorry bout that hotaru! I'll put your name in
[Hero CDMA Android Development] hotaru:
here's what i've found out from my playing with the source:

google says you need a 64-bit system to build it, but i managed to hack the build system to build on 32-bit, but i wasn't able to test whether the build worked because...

google says you need about 12GB of free hard drive space to build it. i had 14GB free and ran out of space. looks like i'll have to get a bigger hard drive.

i was building with the device files from cyanogenmod froyo, and it seemed to be working after a few minor changes.
[Hero CDMA Android Development] hotaru:
i won't be able to get a build out until i get a bigger hard drive, and since i don't have a job right now, i don't know how long that will take.

just relax, i'm sure someone will have a heroc gingerbread build out soon enough. from looking at the source, i think it'll probably happen by the end of the week, but i wouldn't be surprised if it takes longer.
[Hero CDMA Android Development] :
Can you share what you took from Cyanogen to get this to build specifically for the HeroC? (are you using 'lunch'?)

I have the hardware avail to do builds. Either in a VM or actual hardware. 64bit ok.

edit: looks like kernel.org is still piss slow for me ;(
[Hero CDMA Android Development] hotaru:
https://github.com/CyanogenMod/android_device_htc_heroc/ and the dictionaries for the keyboard are the only things i used from cyanogenmod. and yes, i used lunch.
[Hero CDMA Android Development] :
Great. Source is still downloading, so I figured I'd ask while that takes its sweet time..

Which lunch option? vendorsetup.sh only specifies a generic userdebug. Are we sure that the correct HTC drivers are being included during build time (creating the proper update binary and script for flashing)?

Cyanogenmod makes all of this too easy ('make bacon' is fun) so when it comes down to doing it from aosp source I'm a bit lost with the whole devices/ and vendor/ directories and how they tie together at build time. Perhaps I need to get out of the CM mindset for building.

Incase it isn't obvious, I'm somewhat new to ROM building (like I said, cyanongen makes it way too easy) so I'm probably making this harder than it needs to be.

I by no means want to take credit or do anything else other than be able to build the source for myself (and in this case if it helps this thread, even better) to use on my phone.

I'll eventually figure it out on my own, which is what I have been doing so far, but any help is appreciated.
[Hero CDMA Android Development] hotaru:
i was using generic_heroc-eng. "make otapackage" should get us a flashable zip.
[Hero CDMA Android Development] :
source: check

git clone'd heroc files: check -> device/htc/heroc

ran ./extract-files.sh to grab proprietary files: check

mx@ubuntu:~/android/system$ lunch generic_heroc-eng

build/core/combo/TARGET_linux-arm.mk:39: *** Unknown ARM architecture version: armv6j. Stop.

** Don't have a product spec for: 'generic_heroc'

** Do you have the right repo manifest?

mx@ubuntu:~/android/system$

This is what stopped me last time. Wrong arm version and no product spec for generic_heroc. Apparently the armv6j build files exist in the cyanongen source tree.

Lunch doesn't list what you typed.

Lunch menu... pick a combo:

1. generic-eng

2. simulator

3. generic_inc-userdebug

4. full_passion-userdebug

5. full_crespo-userdebug

p.s. . build/envsetup finds the heroc/vendorsetup.sh
[Hero CDMA Android Development] hotaru:
oh, i got around that by changing the "armv6j" to something else... i think it was "armv6".
[Hero CDMA Android Development] s0be:
Should also try armv5te, might produce a better binary for our phones.
[Hero CDMA Android Development] :
Install: out/host/linux-x86/bin/minigzip
Target ram disk: out/target/product/heroc/ramdisk.img
/bin/bash: 002c0000: value too great for base (error token is "002c0000")
Target boot image: out/target/product/heroc/boot.img
target thumb C: recovery <= bootable/recovery/recovery.c
bootable/recovery/recovery.c: In function 'prepend_title':
bootable/recovery/recovery.c:423: warning: assignment from incompatible pointer type
bootable/recovery/recovery.c:428: warning: assignment from incompatible pointer type
target thumb C: recovery <= bootable/recovery/bootloader.c
target thumb C: recovery <= bootable/recovery/install.c
target thumb C: recovery <= bootable/recovery/roots.c
target thumb C: recovery <= bootable/recovery/ui.c
target thumb C: recovery <= bootable/recovery/verifier.c
bootable/recovery/verifier.c: In function 'verify_file':
bootable/recovery/verifier.c:124: warning: comparison between signed and unsigned integer expressions
bootable/recovery/verifier.c:153: warning: comparison between signed and unsigned integer expressions
bootable/recovery/verifier.c:154: warning: comparison between signed and unsigned integer expressions
bootable/recovery/verifier.c:162: warning: comparison between signed and unsigned integer expressions
bootable/recovery/verifier.c:171: warning: comparison between signed and unsigned integer expressions
target thumb C: recovery <= bootable/recovery/encryptedfs_provisioning.c
make: *** No rule to make target `out/target/product/heroc/obj/STATIC_LIBRARIES/librecovery_ui_heroc_intermediates/librecovery_ui_heroc.a', needed by `out/target/product/heroc/obj/EXECUTABLES/recovery_intermediates/LINKED/recovery'. Stop.
mx@ubuntu:~/android/system$

above is almost instant after 'make otapackage'.

Questions while getting this far

1) Using cyanogen parts feels 'cheap' like a band-aid to a larger problem. Just my personal feeling. I've already lost track of changes I've had to make to even get this far into the build. Most of the errors have been almost self-explanatory.

2) If this was so simple as sync/compile/make, how come none of the other experienced DEVs have mentioned anything? I'm not saying they haven't because I don't follow their every posts, just saying

3) :cool:
[Hero CDMA Android Development] hotaru:
that might be what i used.

also, i changed it to tell it not to build a recovery.
[Hero CDMA Android Development] :
removed text
[Hero CDMA Android Development] jaybob413:
The error you have is because the sensor_t struct now has an additional element. If you put a 0 in each element initialization statement before the last field, this error will go away.

For example:

95c95

< SENSOR_TYPE_ACCELEROMETER, 2.8f, 1.0f/4032.0f, 3.0f, 0, { } },

---

> SENSOR_TYPE_ACCELEROMETER, 2.8f, 1.0f/4032.0f, 3.0f, { } }.
[Hero CDMA Android Development] hotaru:
the fix for that is just adding the HAL_* functions to libcamera. it's not too hard to do, just look at the code for the nexus s libcamera (in device/samsung/crespo/libcamera) to see how to do it. you'll also want to make sure you completely remove any libcamera stuff from the out directory, so you don't end up with an old version of it hanging around.
[Hero CDMA Android Development] hotaru:
it's in hardware/msm7k/libcamera. which i found because i realized the functions were supposed to be in libcamera, and figured that libcamera would probably be under hardware if it wasn't under device... and since the hero is an msm7k device, i looked there.
[Hero CDMA Android Development] il Duce:
He's developing, removing text to de-clutter the thread (unlike what you're doing.)

You NEED to stop posting crap like this it actually SLOWS development - by the way that is YOUR SIG, so it says that exact same thing every time you post! I just looked at your 41 posts and about 99% of them are needy posts about "gimme gimme gimme" - stop messing with devs, they are devving! you should get an infraction. If you wish to post, make it helpful, otherwise, don't.
[Hero CDMA Android Development] il Duce:
Well, I read your posts, how about you read mine and see how many of them are helpful. I have helped a few people even un"brick" their phones, some of which were on different phones and different carriers. I do NOT mean you harm or ill will, I just would like to see more development related comments in development threads. Please do not respond to this comment, thank you, and have a happy holiday!
[Hero CDMA Android Development] Twolazyg:
OK, let's try to stay on topic. This is thread about a ROM, NOT when it is going to come out. The devs are working hard and don't need to search through all the BS that is posted on the ROM threads. So, lets give them the space they need and give them time they need to work their magic :D

To the devs: I really appreciate the work you're doing and hope you have a great holiday time :D
[Hero CDMA Android Development] amehdi43:
alright.. heard cm 7 is out for gsm hero. check unstable aospmod..
[Hero CDMA Android Development] zenulator:
http://xdaforums.com/showpost.php?p=10027309&postcount=405

flash a deca kernel on top. have fun.
[myTouch 3G Slide Q&A, Help & Troubleshooting] gabrialxue:
I was thinking that my battery cover is starting to show some wear and tear. So I thought "what would it look like if I put a black mytouch battery door on a white mytouch slide?"

I was hoping everybody could give me their opinion

Would you like it?

Hate it?

And why?

I'd appreciate your help, thank you
[myTouch 3G Slide Q&A, Help & Troubleshooting] dredayholiday:
if you had a black phone with the white back, I'd say it was cool due to the "tuxedo wearing phone" effect, but all white with just a black back kinda looks like Super Mario's eye from the original Super Mario Brothers game.
[myTouch 3G Slide Q&A, Help & Troubleshooting] gabrialxue:
The thing is, I don't really want a white back anymore because it gets a lot dirtier than a black backing (this is why they made it out of the same material as on the original black mytouch)
[myTouch 3G Slide Q&A, Help & Troubleshooting] btate0121:
I have a white slide as well. I originally got black and decided i wanted to hunt down a white one. finally did.. Months later... i definitely miss the black one. I'll never get another white phone. flaws are too easy to see.
[Desire Android Development] AdamG:
Welcome to GingerNinja.

This is a Gingerbread ROM using the system.img and ramdisk.img from the Google SDK before you ask.

This is HIGHLY experimental and there are still a heck of a lot of bugs to be worked out but I will try to fix the majority of them as time progresses.

I would also like to add that this is temporary until Google drop the official code, which of course then I will update Oxygen.

Download here v0.1.1 (seems slower than v0.1 (possibly because of cache2sd?))

Download v0.1

What works / has been fixed.

APNs List

Charging/Activity LED

Hardware keymap

Radio interface (2G/3G)

Screen density set correctly

SD card storage

What doesn't work / still to be fixed.

Sound

Bluetooth

Wifi

Weird lag bug

Credits

Benee - vorkKernel

killkennys - server host

Defer/Kali- - the whole Desire scene owes these 2 a debt of gratitude
[Desire Android Development] AdamG:
Fixes discovered and that will be included in the next release

Google Apps (Not really an issue)

Fixes being worked on currently

Wifi

Version history

v0.1.1

Added A2SD

Added Busybox

Added Superuser

Added Terminfo

Fixed IPV6 Support (needed for Google Goggles)

Fixed Hardware Keymap

Fixed Charging/Activity LED

v0.1

Initial release
[Desire Android Development] sashajovicic:
So no sleep for you , as i can see :)))

But, very nice name for new rom :)))

Will try this!!

Thanks!! :)
[Desire Android Development] penguinolog:
And what about lang support with Oxygen? Wait for next release or Gingerbread?
[Desire Android Development] AdamG:
Gingerbread has/will have wider support for languages, please keep this topic for this ROM only thanks :)

Refer to the following for reference here.
[Desire Android Development] chinesedavid:
Superman INDEED!
[Desire Android Development] howdid:
Flashing now ( : will report bugs
[Desire Android Development] Kalashnikitty:
Damn, im @work right now and cant test your new baby :(
[Desire Android Development] youlsa:
Great work! ;)
[Desire Android Development] LuffyPSP:
Nice name! Will wait for v1.0 though. hopefully google will release them soon.
[Desire Android Development] GuestK00201:
Adam, seriously.. do you ever sleep?????

Thanks a lot again!!
[Desire Android Development] JPAndroid92:
This is awesome... I will try but then I will go back to Oxygen :D
[Desire Android Development] mariosraptor:
what the heck Adam? is this for real? seriously you are the Man.
[Desire Android Development] Milamber:
This is good news! I like the sound of this ROM already! :D
[Desire Android Development] keenkwok:
You are a superman, Adam!
[Desire Android Development] h46it:
Thx for all of your hard work Adam!
[Desire Android Development] kimi789:
so fast！！！！！
[Desire Android Development] GANJDROID:
You are the modern day Jesus!

Sent from my HTC Desire
[Desire Android Development] crowstar:
I lol'd at the changelog:

I have the buggiest/hacky release, but at least google goggles works!!

But seriously FANTASTIC job we got it faster than the nexus one group lol

:D
[Desire Android Development] AdamG:
Thanks for the messages guys

v0.1.1 will be available shortly
[Desire Android Development] Ellingsoc:
So this is GSM or CDMA?
[Desire Android Development] ouglouck:
This works on my GSM Desire.
[Desire Android Development] :
I get an error message when switching from camera to video recorder. *yawn*. Meh, uninstalled.
[Desire Android Development] JonesWTF:
You're kidding, right? You're lucky we have a dev that built this much for us from the SDK and you were able to try it at all!
[Desire Android Development] :
No, I'm not kidding. It was a pain in the ass switching ROMS only to find out it had a major bug. Sorry if that offends.
[Desire Android Development] broderbluff:
Bloody ignorant kid
[Desire Android Development] madd0g:
Guess you aren't too keen on reading properly ->
[Desire Android Development] najar360:
hope gingerbread source code will be release soon.
[Desire Android Development] Jake254:
You ungrateful little sod. Highly experimental.
[Desire Android Development] vnvman:
Ya rly, just read the first post before flashing, noone compells you -_-
[Desire Android Development] wsglj:
Waoooh...u r sooo cool.
[Desire Android Development] jamesfp:
this made me throw up.
[Desire Android Development] mad-murdock:
that actually made me laugh. Switching roms is so very easy. He probably got the iq of a toaster. Or less

Swyped with HTC Desire. Excuse typos.
[Desire Android Development] Wekkel:
Now onto Oxygen

Once Adam puts 2.3 in Oxygen, I will leave OD 4.0.36 behind. Thumbs up for the hard work.
[Desire Android Development] faddys123:
Can someone port the screen off animation please?
[Desire Android Development] vnvman:
It's not a matter of porting: apparently it's not in the sdk, so if it's not a fake we'll be getting it once we get our hands on the first rom dump (n1 release probably)...that might happen even in the next few weeks, so be patient but stay tuned, you might have some nice birthday gift ;)
[Desire Android Development] shokwaav:
wtf where in the first post does it say that this was stable... and had no bugs. do you know how hard it is to port gingerbread to the desire? srsly if you can't appreciate other ppls efforts then f*ck off.
[Desire Android Development] :
Exactly. This ROM is highly unstable, it doesn't even qualify for a beta tag, and you expect a bug-free experience? Either you misunderstood or didn't bother to read, or you have the IQ of my Desire.
[Desire Android Development] Jelte12345:
It's not fake, look at the galaxy s commercial at the end.

It turns of and you can see the animation.