Database Develop

[Q] 2.2 Roms in a nutshell

Ok, i've been absent from the forums for some time and have been trying to play catch up... If someone who has been keeping up would just help me get a few things straight it would be awesome.
please just put the number and if its correct or the answer or w.e.
What I think I know:
1. CyanogenMod- Established dev who releases nightly updates (CM6?) to his tweaked build of rooted mostly ASOP 2.2, which recently (thanks to a new kernal?) began working on our CDMA Hero’s.
2. Most 2.2 ROMs are based off of one of the CM6 nightlies, then customized with themes and tweaks
3. “CyanogenMod-6 for Hero CDMA - V6.0.0 (09/18/2010)” is one of these, and has been tweaked minimally, and is considered a stable build as far as CM6 goes
4. “FroYo 2.2 – CM6- Vanilla” is basically same as above, just complied from a differently “nightly”, while “Extremely Blue” and “BlackMod” are the same, just themed
5. The main (only?) NON–CM6 based options for 2.2 are…
a. asopMod v.03m = which is a very ASOP build, includes OC
b. NFX-Hero 2.2.1.update1 = slimed down ASOP, includes OC and JIT option
Questions:
6. If I want the CM6 nightly updates, is there an updater app in any of these ROMS’s, like in Fresh Hero 2.4 (what I’m used to), or do I have to pull an update.zip from somewhere (or something)?
7. Do some phones work with JIT enabled, and others don’t? and if so is there a way to tell without just trying
8. If I'm set on 2.2 should I check out any other ROMs than those I mentioned
9. Is there a standout (stable) kernal right now?

Just want to say:
NFX-Hero 2.2.1 is just the version number. It is still based on HTC Sense 2.1.
There is currently no Sense 2.2 port for the Hero.
As for the stable kernel, I've heard good things about this one
http://forum.xda-developers.com/showthread.php?t=756774
specifically [email protected] 09/14/2010, people refer to it as "#14 kernel"

teddypepper52 said:
Ok, i've been absent from the forums for some time and have been trying to play catch up... If someone who has been keeping up would just help me get a few things straight it would be awesome.
please just put the number and if its correct or the answer or w.e.
What I think I know:
1. CyanogenMod- Established dev who releases nightly updates (CM6?) to his tweaked build of rooted mostly ASOP 2.2, which recently (thanks to a new kernal?) began working on our CDMA Hero’s.
Cyan is the almighty grand pubba of AOSP and was one of there first to release roms in the mainer we see them now. He does not do everything and all roms as he has allot of help from other devs, for us its Darch who maintains the Heroc version of cyanogen (sorry if I forgot some of you other devs)
2. Most 2.2 ROMs are based off of one of the CM6 nightlies, then customized with themes and tweaks
All of the roms you see for the heros here that are AOSP based com from darch's and then cyans repo period, nightlies are built roms while we theme built roms roms deving is done from source and can be taken from different time and snap shots so nightly means nothing then.
3. “CyanogenMod-6 for Hero CDMA - V6.0.0 (09/18/2010)” is one of these, and has been tweaked minimally, and is considered a stable build as far as CM6 goes
The stable build of cm6.0 is from the combined deving of cyan, darch and alot of other people to bring the best of wheat works and leave out what doesn't. Nightlies usually are adding what seems to work but is not always guarenteed
4. “FroYo 2.2 – CM6- Vanilla” is basically same as above, just complied from a differently “nightly”, while “Extremely Blue” and “BlackMod” are the same, just themed
Black mod is a theme, extreme blue is a themed rom compiled from cyan/drach's source vinilla is a terms used to describe a stock rom which is what cm6.00 stable and anyhting else that comes from the repo.
5. The main (only?) NON–CM6 based options for 2.2 are…
a. asopMod v.03m = which is a very ASOP build, includes OC
b. NFX-Hero 2.2.1.update1 = slimed down ASOP, includes OC and JIT option
I'll go ape **** on this but asopMod v.03m is from cyan's source ino at first he tried to make it seem like he compiled from AOSP source but the fact is he uses cyans like almost everone else and if you check his thread now he given the props the the cyan team as he should have at first.... NFX-her is a sense based rom from android 2.1
Questions:
6. If I want the CM6 nightly updates, is there an updater app in any of these ROMS’s, like in Fresh Hero 2.4 (what I’m used to), or do I have to pull an update.zip from somewhere (or something)?
Not yet but that would be nice nightlies are not considered stable and there for i dont think theyll be added to an updater like cm updater or fresh updater but when we start seeing more stable builds you'll see the updater used, cm updater is on cm6 right now just nothing to update
7. Do some phones work with JIT enabled, and others don’t? and if so is there a way to tell without just trying
All phones should work with JIT (Just in Time) dalvik compiler, whether they run betters is a different story but I have never had issues
8. If I'm set on 2.2 should I check out any other ROMs than those I mentioned
For sense I like fresh as he seems to be the best sense dev (imo) around here for AOSP you go with the grand master Cyan and his cm6 (for the hero) there are some other devs out there that make roms for other phones but most of them still use Cyan's repo.
9. Is there a standout (stable) kernal right now?
Yes Decadence
Click to expand...
Click to collapse
if anyones see's an error in what i posted please correct me.

Any froyo rom is going to be based off of CM6. The nightlies are built every night from any changes made that day. They are considered beta, however most will find no issues at all. If you flash CM6 the Jit setting is a quick change and will not screw up the phone. You just go into setting>cyanogenmod setttings>performance settings and check or uncheck jit and reboot. There is a ROM Manager app in CM6, but you have to install clockwork recovery so I am not sure what will show up in the ROMs option or what else it does because I do not want to install clockworks. As mentioned a lot are using #14.

unCoRrUpTeD said:
Any froyo rom is going to be based off of CM6. The nightlies are built every night from any changes made that day. They are considered beta, however most will find no issues at all. If you flash CM6 the Jit setting is a quick change and will not screw up the phone. You just go into setting>cyanogenmod setttings>performance settings and check or uncheck jit and reboot. There is a ROM Manager app in CM6, but you have to install clockwork recovery so I am not sure what will show up in the ROMs option or what else it does because I do not want to install clockworks. As mentioned a lot are using #14.
Click to expand...
Click to collapse
not a lot shows up in the downloads section for rom manager on the hero. there's 4 selections, and none of them include cm6. it's mostly useless in my experience.
hopefully they update the downloads list soon.

Brandito said:
not a lot shows up in the downloads section for rom manager on the hero. there's 4 selections, and none of them include cm6. it's mostly useless in my experience.
hopefully they update the downloads list soon.
Click to expand...
Click to collapse
Actually i was referring to cm updater which is similar to the fresh updater... when we see more stables from cm6 and up it'll start showing some it that. I personally don't care for rom manager.
Sent from my HERO200 using XDA App

ASimmons said:
Actually i was referring to cm updater which is similar to the fresh updater... when we see more stables from cm6 and up it'll start showing some it that. I personally don't care for rom manager.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
rom manager could use some work to make it a bit more useful. i like it for queuing up roms to flash and making things a bit more automated, however i'm not sure it clears the dalvik cache when it does its thing so i generally have to do it myself anyways.
i'll have to check out fresh updater. i have cm updater, installed from the market, does it actually come with cm6 now? i never saw it when i flashed the 9/18 and already had it installed when i clean flashed the latest nightlies.

Brandito said:
rom manager could use some work to make it a bit more useful. i like it for queuing up roms to flash and making things a bit more automated, however i'm not sure it clears the dalvik cache when it does its thing so i generally have to do it myself anyways.
i'll have to check out fresh updater. i have cm updater, installed from the market, does it actually come with cm6 now? i never saw it when i flashed the 9/18 and already had it installed when i clean flashed the latest nightlies.
Click to expand...
Click to collapse
Well fresh updater is pretty much the same as cm updater but its only for fresh roms. cm updater might not be part of cm6 I can't, it probably isnt. I actually would like it to be as with cm5 and below it also had themes in it. hopefully itll come back when theres more cm6 stables.

Thanks all. Didn't want to jump into 2.2 without knowing what I was getting into. I decided to start with CM6.0.0, and so far its been great. As mush as I love all things Freshh, I'm mad I waited this long. I DO miss the Senses dialer (minus the ungodly lag) and I havent made up my mind on the keyboard, but the overall speediness is killer.
Hell yea froyo/ CM.

[Question] Gingerbread on Tattoo?

Hey guys,
Now that Gingerbread is out, I think most questions on people's minds are: Can it happen? What's needed?
Sent from my Tattoo using XDA App

I'm trying to do something about it stay tuned...

i just saw a youtube video about a wildfire running an early built,
so i thinks its not a matter of resolution.

I just hope the CM can be work on ROM.

We need AOSP sources before it can be built properly. The ones on Wildfire etc are just hacked together from an emulator image, and they run quite slowly. For the Tattoo, I'm a bit uncertain if it can be used with kernel 2.6.29, or if 2.6.32 or higher is required.

It will eventually - Froyo took a while but is here. But I can't wait for the new UI and it will be speedy if Google are telling the truth

I was WAITING for someone to ask this question
Anyway, fingers crossed

It has to be possible: http://androinica.com/2010/12/07/go...droinica+(Androinica+-++A+Google+Android+Blog)

I guess gingerbread will take some time to come on tattoo, but there is a full gingerbread theme for tattoo available here.

aliwaqas said:
I guess gingerbread will take some time to come on tattoo, but there is a full gingerbread theme for tattoo available here.
Click to expand...
Click to collapse
I guess it will be pretty soon, because Gingerbread AOSP is already available to create ROMs like fyodor's or spartm's, and Cyanogen is working on modded Gingerbread too already

gingerbread on tattoo would be GREAT
Sent from my HTC Tattoo using XDA App

@those who try to port 2.3 for tattoo: If you're successfull, plz change the icon for mobile data... it's just too tiny for our small screen!

the source code for the nexus one is out, i dont know how difficult it is to port it to another device but i hope someone tries it already

I'm trying to compile gingerbread, if somebody(or more) wants to collaborate making vendor files, we can put up a github start a collaborate rom for our tattoo
I've triend changed fyodor files, but for now i'm stuck (something wrong with libstagefright)
Somebody?

Aaroneke said:
I'm trying to compile gingerbread, if somebody(or more) wants to collaborate making vendor files, we can put up a github start a collaborate rom for our tattoo
I've triend changed fyodor files, but for now i'm stuck (something wrong with libstagefright)
Somebody?
Click to expand...
Click to collapse
Stuck when compiling or when booting?

Compiling i've managed this problem, but i changed some stuff and now i got it again, i'm trying to make new vendor files step by step using fyodor,..etc (and google ref) files just for reference, but it can take a while(if i'll get it working..)

[ROM][CM7] CM7-20120226-Nightly

CM7 20120226 Nightly
http://download.cyanogenmod.com/?device=shadow
*I am not recommending anyone flash this. MAY NOT be for cdma devices*
*I don't even begin to try to take credit for this just stumbled across it*

This is based on the Froyo kernel and requires fixes to be flashed.
Pooka's unofficial Cm7 nightlies can be found over on Rootzwiki, don't require fixes, and are based on the Gingerbread kernel.
Sent from my DROIDX using Tapatalk

It would be great if you could tell us how you determined that. Part of my confusion on what this update is centers around the fact that it popped out under shadow vice cdma_shadow as all previous ones were. Thanks.

All the official nightlies are based on the Froyo kernel.
Sent from my DROIDX using Tapatalk

This is actually CM9. Any builds labeled "cm" are CM9, builds labeled "cyanogenmod" are CM7.
EDIT: Oops, guess that didn't happen like I read it did.
Now that CyanogenMod has their new build servers the nightlies should be going again for everyone soon, I hope!
Check this out too: http://jenkins.cyanogenmod.com/job/android/
EDIT 2: Builds listed at Jenkins as "cm" are CM9, "cyanogen" are CM7.

[Q] Can't build CM6 from sources. Help please!

Hi,
I'm trying to build cyanogenmod 6 (froyo) from sources on github for G1.
Sidenote. The reason I'm trying to do this is i'd like to modify kernel parameters. I'm trying to make the phone talk to external device using built in serial port. I can do it with my current CM6, but it looks like serial debugger engages and starts responding to the device and also steals some of the data being sent to phone.
To build I used instruction posted at cyanogen wiki "HTC Dream & Magic: Compile CyanogenMod (OS X)" which covers gingerbread but checked out froyo-stable branch at first. I know that gingerbread version stopped supporting G1 at some point last year.
Without much success even after fixing manifest to point to updated repo urls from kernel.org to googles repo etc. The problem is that apache-http seems incompatible with old sources and it is referenced by head.
I also tried froyo branch, but it doesn't build as well because something seem to be broken for dream_sapphire, and it is not present in the devices anymore.
I've tried searching for compilation errors, and general build questions/instructions here and on cyanogen's forum, but looks like CM6 is not very active these days.
Can someone point me into right direction where to search for relevant info on building it? Would getting a proper revision help or should I combine stuff from several branches to make it work?
I've already spent quite a lot of time figuring out how build is being configured and how things stitch together but without much progress on the actual build.
And with times required to sync a whole repo and build it, it is becoming frustrating.
Any help would be muchly appreciated!
Regards,
Oleg

It's dead.
I also wanted to make a cm6 rom, but I couldn't get anything to work.
I got the addresses all updated but it looks like a bunch of the files have completely dissappeared. You may be able to make it skip those, but then it may not work completely.
Go for AOSP?

Now that's a shame. I wanted to build CM because I'm familiar with it and the other thing is that they have reasonable instructions about building it. But at least I don't need to waste my time trying to figure out how to fix it.
In fact I don't need any extras they provide, a bare android would suffice to me if all the sensors and connectivity would be available. But I'm not familiar with internals of building vendor specific stuff. My understanding was that I need proprietary parts together with AOSP to build a working ROM and that's one of the things CM guys did. Correct me if I'm wrong.

aliher1911 said:
Now that's a shame. I wanted to build CM because I'm familiar with it and the other thing is that they have reasonable instructions about building it. But at least I don't need to waste my time trying to figure out how to fix it.
In fact I don't need any extras they provide, a bare android would suffice to me if all the sensors and connectivity would be available. But I'm not familiar with internals of building vendor specific stuff. My understanding was that I need proprietary parts together with AOSP to build a working ROM and that's one of the things CM guys did. Correct me if I'm wrong.
Click to expand...
Click to collapse
Nope AOSP is as easy to build now
Go to the android site and follow directions
Google for "build android"
At the part when doing repo init you need to get the right branch
Go to "build for devices" then scroll down for recommended branches and look for the dream
One thing you'll need to do differently is do "make otapackage" instead of plain "make"
And once that's done you'll need to tweak the zip and get rid of the "recovery" folder and tweak the updater-script
Oh yeah, and I don't know exactly how you would do this part, but you'll need to get the source for a newer kernel in there, like ezterry kernel and use it with 2708+ radio/spl
Unless you wanna use the AOSP kernel & spl & radio which is old
What I did is just flash his kernel after the rom, but you want to do kernel stuff so yeah...
Sent from my HTC Dream using Tapatalk

CM7 on New Bootloader - Feasible?

Hi All
I am not really a developer at all but I have had loads of experience messing around with ROMs to improve them (such as changing rils manually, using my own updater scripts, creating my own nvflash layouts and images, etc).
Recently I have been trying out CM10.1 again (mivvs ROM) on the new bootloader and also paranoid android. But both are too buggy for me and the battery life is really bad. So I am thinking to revert back to CM7 again.
I am planning to *TRY* and build my own CM7 rom from source using these fixes by Pengus (http://forum.xda-developers.com/showpost.php?p=35661482&postcount=100) to try and make it boot and run on the new bootloader. I know the advantages are very little but its just a "to see if I can" thing. It will also mean others wanting to go back to CM7 won't have to flash the old bootloader again.
I am planning just a one-time build as CM7 has pretty much reached completion.
I am posting this up to:
Make sure no-one else has already done it
Make sure one of the devs doesn't know of a reason this 100% will fail
To see if anyone else would be interested in such a ROM
To know if its possible to build from Windows (if I need Linux then so be it)
Let me know what you think

hy
I have mivvs rom and the battery life in not bad.
however, your idea is interesting .. good job!

Well, I think this is quite interesting. However, I am a big fan of PA10 and Pengus work... for me they beat GB in all aspects at the moment. However, one of the greatest pro's of having a CM7 on the new bootloader is the ability to have dual boot with CM7 + CM10.1 (or something else), since dual boot only works for roms with the same bootloader.

So far I have:
Set up Ubuntu x64 VirtualPC
Installed Android SDK and all Dependancies
Sync'd the CyanogenMod 7 Source
Sorted out the P990 Proprietary libs
Made MOST of the changes Pengus lists (although some bits are in different files)
It turns out the kernel source isn't downloaded automatically with CM7 so I need to find out how to build the kernel from source (in order to make the rest of the changes on the list Pengus made) but I think its looking good..
CM7 also doesn't have fstab.p990 but these lines can be found in init.p990.rc. Until I have the kernel source I am stuck on point 6
And I didn't mean to knock Pengus/TonyP/Mivv's work. They have helped this phone come a really long way especially now acree seems to have dropped support for it.

Just FYI
I tried this, making all the changes above, compiled the build.... but it doesn't boot.
Just gets stuck on the red lg logo.
I think the old CM kernel will not run on the new boot loader at all.
Was worth a try!

rlees85 said:
Just FYI
I tried this, making all the changes above, compiled the build.... but it doesn't boot.
Just gets stuck on the red lg logo.
I think the old CM kernel will not run on the new boot loader at all.
Was worth a try!
Click to expand...
Click to collapse
Maybe your last resort, try the excellent CM7 ETaNa kernel (link is in my signature).
But, I guess it won't work; kernels are bootloader specific.