Database Users

CyanogenMod 6.1 is on its way! And its easy to get on Captivate!

Sorry if this has already been posted.
I apologize for not keeping the site up to date, I’m a slacker We also had a database issue and lost the last post about 6.0′s release, if you were wondering why it went missing.
6.1 is the current work-in-progress and is coming together nicely. There’s a few new features like touch-to-focus in the camcorder, dismiss notifications by swiping, kernel updates for most devices, and improved performance. There will also be support for a few new devices- Acer Liquid, HTC Wildfire and Samsung Vibrant. My eye is also on the new HTC phones that are about to get released like the G2.
A lot of people ask me about adding support for their phone, but we can only support phones that we actually own. The CM team is always looking for new hackers to join up with us to add support for their favorite device. Get in touch with me if you’d like to help.
CyanogenMod is open source. The quality of code being added to CM has vastly improved because of the code review system that we’ve put in place, Gerrit. It’s the same system used by Google to manage the Android Open Source Project. It allows anyone to submit code to the project in a highly-visible way and gives us a way to examine and improve it before it’s actually merged. We want your code, so send us your patches. If there’s something you don’t like, change it.
Nightly builds of CM are always available if you’re brave and want to try out the latest code. If you’re running nightly builds, the best way to stay up to date on new changes is to follow @cmsrc on Twitter.
Our user base is approaching a quarter of a million users. This project has come a long way Thanks for all the support, we are only as strong as the community!
Source- Cyanogenmod.com
Porting a vibrant rom to the captivate is not hard

no wayyyy this is finally coming to our cappy, i'd be beyond happy

Hate to sound like a douche, but is there anything in there (besides maybe some of the features of CM6.1) that we havent known for a long time? No release date, we know thier working on it, and we know they are working with the vibrant.

Well if you look here it still shows as in progress for version 6.0...They have said in the past that the vibrant won't be supported till 6.1 and then someone will still have to port it to the captivate..
https://spreadsheets.google.com/lv?key=0Aledx886TFpZdHdwNzNKZzJLczJjTnA5ekFWRzNxX2c&hl=en&authkey=CNf7ie8G
So I don't think we will be seeing anything soon...

so, i'm sure everyone will get a good laugh, because everyone talks about how this is the best thing about to come since sliced bread........
but what is SO great about this?

buddy17 said:
so, i'm sure everyone will get a good laugh, because everyone talks about how this is the best thing about to come since sliced bread........
but what is SO great about this?
Click to expand...
Click to collapse
Froyo! Plus lots of custom stuff.

well i knew it was based on 2.2....but the "custom stuff" is what i meant. What are some of the big things it does that are so great

I'm new to the whole Android scene so excuse my ignorance but can someone explain how CM6.1 can possibly be put on a GalaxyS phone when there is no source code for the kernel?
Sent from my SAMSUNG-SGH-I897 using XDA App

sdotbrucato said:
I'm new to the whole Android scene so excuse my ignorance but can someone explain how CM6.1 can possibly be put on a GalaxyS phone when there is no source code for the kernel?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The other custom roms seem to use the 2.1 kernel.

I checked that spreadsheet about 3 weeks ago, and it was still in development like it is now for the vibrant.

buddy17 said:
well i knew it was based on 2.2....but the "custom stuff" is what i meant. What are some of the big things it does that are so great
Click to expand...
Click to collapse
Its not really about a wealth of extra features. Cyanogenmod has extra configurability. In addition it is a bit more cohesive than typical roms. I definitely preferred it over the stock Nexus One rom and the stock nexus one rom is better than stock Captivate.
The rapid updates and support is enough for me to use Cyanogenmod.

z28james said:
The other custom roms seem to use the 2.1 kernel.
Click to expand...
Click to collapse
But 6.1 is Froyo, all the ROMs I've seen are Eclaire... How are they using a 2.1 kernel with Froyo?
I was under the impression the reason for no Froyo ROMs on the Captivate was due to lack of source from Samsung?
Sent from my SAMSUNG-SGH-I897 using XDA App

Who needs this when we have cognition?!

designgears said:
Who needs this when we have cognition?!
Click to expand...
Click to collapse
exactly

designgears said:
Who needs this when we have cognition?!
Click to expand...
Click to collapse
i'm sure when this comes out you'll be able to strip the FroYo out of it and make it your own, and better

CM6.1 will come to the captivate after is released to the vibrant, kernel differences are minimal between the two so porting CM6.1 to the captivate will only require few kernel changes.

yeah i'm sure the port will be done in the time it takes to heat up a pop tart.

designgears said:
Who needs this when we have cognition?!
Click to expand...
Click to collapse
+1 Finally got my Cappy right where I want it. CM is awesome, I'm just tired of all the hype, not to mention the waiting for this stuff to happen.

designgears said:
Who needs this when we have cognition?!
Click to expand...
Click to collapse
Everyone who is waiting to use Voice Actions, Chrome-to-phone, and any other cool 2.2-only apps.

Yeah, like real Flash or having the speed boost of the JIT compiler.

A request to All developers

This is a request to all the developers developing for HD2, If you want a fully working, fully stable build on HD2 with top performance you would have to stop treating your device as Bravo, everywhere i look from recoveries to kernel i see Bravo, Evo, Passion. For God's sake the phone is different from all other snapdragon phones.The display, the drivers etc are different. Also please stop keeping the source of your edited files to yourself, if you open source them, they can be improved upon and HD2 can be made faster and better device. Also developers thing beyond overclocking. There are other things HD2 needs in the kernel. If you waste your energy in just overclocking then i would say its pretty dumb. Just a kind request to everyone. Your device is htcleo/leo not bravo/passion/supersonic. They are similar but not same. use htcleo as device name in build, init rather than bravo/passion/supersonic. Your device isnt a mix of device anymore, its a different device that stands apart

im not a dev but ... yes , is time when all work must be unified.

+1 on this.
All devs should work together and share their results.

Bump.
This thread needs to be looked at and acknowledged. Charansingh is trying hard to get our device working to its best possible method and not just patch everything constantly. If some kernel developers (Tytung, rafpigna, iamgpc, etc.) set up conversations with charansingh, I'm pretty sure all outstanding issues could be worked on and we could even fix issues we didn't know we had. Come on, devs! Work together to bring our HD2s to truly compete with android devices out there as a native solution!

Definitely worth a bump

Super bump. Seems like a lot of these roms are sort of half-baked ports of other devices. It's extremely difficult to find a stable rom to use as a daily driver. Coming from the Nexus One, the difference in rom development is staggering. If you go to the Nexus forum you can find tons of stable, fully functional roms optimized for the Nexus. I still haven't found a rom that's come close to the usability, speed, and stability of those for the Nexus. I don't mean to knock t he devs on the board, because they do great work, but I think the HD2 has the potential to be amazing.
Just my 2 cents.

rottenjello138 said:
Super bump. Seems like a lot of these roms are sort of half-baked ports of other devices. It's extremely difficult to find a stable rom to use as a daily driver. Coming from the Nexus One, the difference in rom development is staggering. If you go to the Nexus forum you can find tons of stable, fully functional roms optimized for the Nexus. I still haven't found a rom that's come close to the usability, speed, and stability of those for the Nexus. I don't mean to knock t he devs on the board, because they do great work, but I think the HD2 has the potential to be amazing.
Just my 2 cents.
Click to expand...
Click to collapse
The Nexus is a native Android device. Of course the ROM development will be different. It's a miracle we have Android on the HD2 at all. It was always going to be a painful development process. That said, wise words from charnsingh.
Keep rocking, Devs.

I'm not a dev, and this topic is not addressed to me but I think you should correct the name of the thread to "A request to All developers' except Pongster. Perhaps not only Pongster but I'm sure that He uses the real name our phone in bulid.prop for example and His bulid's it's not just a port from Bravo, Evo etc, etc. Correct me if i'm wrong.

mzebrowski13 said:
I'm not a dev, and this topic is not addressed to me but I think you should correct the name of the thread to "A request to All developers' except Pongster. Perhaps not only Pongster but I'm sure that He uses the real name our phone in bulid.prop for example and His bulid's it's not just a port from Bravo, Evo etc, etc. Correct me if i'm wrong.
Click to expand...
Click to collapse
if you read craefully pongster thread,his build still use desire base..from source of desire

ardianz said:
if you read craefully pongster thread,his build still use desire base..from source of desire
Click to expand...
Click to collapse
Hhhmmm I don't want to be a Pongster lawyer And I hope that HE will not feel offended but let me quote some parts of tread Hyperdroid CM7
Drawing inspiration from the Desire AOSP based Custom ROMs
Click to expand...
Click to collapse
Again, THIS is NOT a PORT... its Completely Built FROM SOURCE, Fully Optimized and Tweaked for the HD2!
Click to expand...
Click to collapse

ardianz said:
if you read craefully pongster thread,his build still use desire base..from source of desire
Click to expand...
Click to collapse
The source is built from the following: Base is Pure AOSP, Framework Tweaks and Settings is Redux, Cool Features & Functions from CyanogenMod.
Click to expand...
Click to collapse
from the gbx thread.

ardianz said:
if you read craefully pongster thread,his build still use desire base..from source of desire
Click to expand...
Click to collapse
Have you bothered checking the source I use? and the device specific stuff by charan for the HD2 in there? I don't use the desire base. The source of the ROM is something any device can use, given the right kernel and proprietary libs the device may need. Just like CM7 is not just for the HD2, but for a myriad of different devices, the source can be used by anyone with the right device specific stuff.
In my ROM, I use the device specific stuff that charan has done for CM7 HD2 (with a few edits for GBX overlays and HD2 specific Settings).
Like charan has mentioned, most of what we currently have here (ROMs) are ports/kangs from other devices. In fact my old SD build was one of them.
His hard work paved the way for a device specific ROM, that being the CM7 RC's he builds (and you can build, which I also do for testing, from source) and the GBX I build now. If you take the source and add the device specific stuff (drivers, ramdisk, kernel, libs) you can build a ROM for other devices using the the device specific stuff available in the CM7 git. (Desire HD, Nexus One, etc. can be built using the source on Git)
As I understand it, from my limited knowledge on this, the device specific stuff is where the difference lies, from the 2D and 3D drivers, to the overlays for every device, down to the kernel for each device.
I don't know much about the kernel development at this point and how we came about using what we do now, but there is definitely room for improvement and we're lucky to have charan, tytung and the rest of the HD2 devs to help us out in this regard.

pongster said:
I don't know much about the kernel development at this point and how we came about using what we do now, but there is definitely room for improvement and we're lucky to have charan, tytung and the rest of the HD2 devs to help us out in this regard.
Click to expand...
Click to collapse
Well said pongster
Sent from my HTC HD2 using XDA Premium App

Hes right,we have to treat our HD2 like a native android device otherwise were not gonna advance that far if we treat it like anougher device.Our HD2s are amazing so lets advance and be happy

I'm in no way a dev, but its great to see common sense prevailing. I wish I had more time to get my head into these ROM's/kernal's etc but I don't. And I for one am eternally grateful for all the hard work done on this site to keep the likes of me interested in the HD2. It's a crackin phone, lets keep it that way!

i agree with you in lots of things but some roms just have to be ported.
htc won´t release a sense build for the hd2 or just a rom to get ported.
guys that want sense just need a ported rom.
and sorry buti dont´t think this is right in the development section.
maybe you should contact them on irc

I agree it would be nice if everything was done just for the LEO, but Im not going to say anything bad about Typoon his ports rock, are uber stable, and anything but half baked.

The reason why the bravo/passion base is used is:
a) Some apps only show up on the android market for known official Android devices. The LEO is not an official Android device.
b) There's no official/main AOSP/CM7 repository with LEO specific changes in them.
EDIT: https://github.com/CyanogenMod/android_device_htc_leo I guess this can be the closest thing to official.
c) In terms of compatibility, the bravo is the hardware closest to our own hardware. Yes there ARE differences which is expected. We do not have a ROM designed for our own hardware that we can refer to.
d) Sense ROM's aren't open source.
I completely agree on the overclocking front. We need improvements in kernel, not just kicking up the CPU clock-speed.
Yes, sources should be shared, however, chefs tend to keep changes to themselves. This is an issue.
In my opinion, an 'official' AOSP/CM7 ROM/repository would be ideal.
That said, I can't think of any bugs/issues now with bravo/passion based ROM's Most issues stem from using ROM's from other devices/chipsets. I'm personally happy with GingerBread based on Passion sources!

DarkStone1337 said:
The reason why the bravo/passion base is used is:
Click to expand...
Click to collapse
a) Some apps only show up on the android market for known official Android devices. The LEO is not an official Android device.
Fixed- We only need to change the fingerprint of the build, same is done for bravo etc using passion fingerprint for gingerbread
b) There's no official/main AOSP/CM7 repository with LEO specific changes in them.
EDIT: https://github.com/CyanogenMod/android_device_htc_leo I guess this can be the closest thing to official.
Fixed - It works
c) In terms of compatibility, the bravo is the hardware closest to our own hardware. Yes there ARE differences which is expected. We do not have a ROM designed for our own hardware that we can refer to.
Fixed - The CM7 nightlies and RC i am compiling.
d) Sense ROM's aren't open source.
Fixed - For sense Roms it isnt an option
I completely agree on the overclocking front. We need improvements in kernel, not just kicking up the CPU clock-speed.
Yes, sources should be shared, however, chefs tend to keep changes to themselves. This is an issue.
In my opinion, an 'official' AOSP/CM7 ROM/repository would be ideal. It is there lol
That said, I can't think of any bugs/issues now with bravo/passion based ROM's Most issues stem from using ROM's from other devices/chipsets. I'm personally happy with GingerBread based on Passion sources!

i am not a dev but there are some roms in this forum that we must give credit to as not being half baked like motomans mytouch rom everything work on it and it is very snappy and responsive also typhoons rom is really good too i can see from there rom that there are those who really treat hd2 like a really android phone

[Q] Blur and AOSP?

what exactly is blur? Ive read that its actually android mixed with motorolla's touch (which is called blur) but what exactly is it?
Ive seen pictures of custom rom and cant tell the difference between blur and custom ROM. At first I thought blur was like a theme and just had fancy animations. But reading about it further it seems like blur is the extra apps that are on the phone that is not stock with the android OS, is that right?
For example if a custom ROM doesnt have blur, how does one get the camera running?
Also is AOSP(android open source project) like the opposite of blur? its considered to be a pure android OS right?

Blur, sense, and touchwiz are all proprietary vendor frameworks that (theoretically) augment the base Android experience. They come at the cost of large ROMs and resources but some people really like them.
AOSP is exactly that- if you build android straight off Google's git, you've built AOSP. It's actually pretty good, hence everyone releasing ROMs for dx /d2 claiming to be 'vanilla' or 'pure.'
In between those is CyanogenMod. CM is more like an extension of AOSP than a replacement framework. You get some nice features and tweaks plus a consistent experience across devices.
HTH!

mrkite38 said:
Blur, sense, and touchwiz are all proprietary vendor frameworks that (theoretically) augment the base Android experience. They come at the cost of large ROMs and resources but some people really like them.
AOSP is exactly that- if you build android straight off Google's git, you've built AOSP. It's actually pretty good, hence everyone releasing ROMs for dx /d2 claiming to be 'vanilla' or 'pure.'
In between those is CyanogenMod. CM is more like an extension of AOSP than a replacement framework. You get some nice features and tweaks plus a consistent experience across devices.
HTH!
Click to expand...
Click to collapse
hmm interesting..
So the google phones that one would buy directly from them without service, are they considered to be pure AOSP?

1dtms said:
hmm interesting..
So the google phones that one would buy directly from them without service, are they considered to be pure AOSP?
Click to expand...
Click to collapse
yes, all nexus model phones are AOSP.

1dtms said:
hmm interesting..
So the google phones that one would buy directly from them without service, are they considered to be pure AOSP?
Click to expand...
Click to collapse
Google only offered that once with the Nexus 1. The Nexus S is sold through T-Mobile and Sprint.
EDIT: but yes, AOSP.

I see.. well thank you! this helped clear up a lot.
So im guessing the camera will still work with all its 8MP if used under an AOSP app?
Also is the liberty rom considered to be pure AOSP? If not, what ROM in your opinion is the best AOSP ROM for .340?

1dtms said:
I see.. well thank you! this helped clear up a lot.
So im guessing the camera will still work with all its 8MP if used under an AOSP app?
Also is the liberty rom considered to be pure AOSP? If not, what ROM in your opinion is the best AOSP ROM for .340?
Click to expand...
Click to collapse
Camera support is more about kernel and libraries, I think, but the aosp camera app handles the Dinc camera fine...
Can't help you much with the rom selection, sorry.

ASOP .............i give up

ok ..i give up What is the difference between my "out of the box" nexus7 rom and an ASOP rom. What are the pros and cons of each and which should I want???

patterone said:
ok ..i give up What is the difference between my "out of the box" nexus7 rom and an ASOP rom. What are the pros and cons of each and which should I want???
Click to expand...
Click to collapse
well depending on the aosp..there are more features to it then stock. a con would probably be more bugs then stock since stock has no bugs i believe.

jarjar124 said:
well depending on the aosp..there are more features to it then stock. a con would probably be more bugs then stock since stock has no bugs i believe.
Click to expand...
Click to collapse
What? Aosp is aosp. Android open source project. There's only one source. It can't "depend on the aosp".
Aosp means built from source which makes it easier to add mods and such. Otherwise stock aosp and stock OTA are pretty similar.
Sent from my Galaxy Nexus using xda premium

Metallice said:
What? Aosp is aosp. Android open source project. There's only one source. It can't "depend on the aosp".
Aosp means built from source which makes it easier to add mods and such. Otherwise stock aosp and stock OTA are pretty similar.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
yes ik that but cyanogen mod is also aosp...as well as others.

W ouldn't AOSP be sorta pointless in a Nexus device, seeing as its basically a pure android experience (as is AOSP) straight out of Google? I get AOSP /AOKP on a Samsung /LG/Sony/etc that's plagued with crap and bloatware, but on a Google device?
Just think about it...

Yeah, the ideal rom to me would be a deodexed stock rom. That way you know everything works but mods are easier to add.

Evo_Shift said:
Yeah, the ideal rom to me would be a deodexed stock rom. That way you know everything works but mods are easier to add.
Click to expand...
Click to collapse
Nah. Mods are much easier to add to aosp. That's why CM and AOKP are modified from AOSP.
Sent from my Galaxy Nexus using xda premium

Someone correct me if I'm wrong here... But isn't the Nexus 7 an AOSP stock rim as is? I mean it seems to me like it's vanilla (AOSP) android with Gapps added... Remove theGapps and u have AOSP, no?

omegajester said:
W ouldn't AOSP be sorta pointless in a Nexus device, seeing as its basically a pure android experience (as is AOSP) straight out of Google? I get AOSP /AOKP on a Samsung /LG/Sony/etc that's plagued with crap and bloatware, but on a Google device?
Just think about it...
Click to expand...
Click to collapse
depends on the rom. as mentioned before, some devs use AOSP as a base and add features to it. if you go for just a plan AOSP, then its semi-pointless. but if you go for a ROM that has AOSP as a base and adds a crapload of customisability to it, then there are some benefits. some have integrated equalisers, integrated speaker amplifer apps, more choices for screen settings, etc.

HTCDev posts framework support files for Google Edition

I'm not sure what they are yet as I'm still downloading the zip. Maybe a way to add the framework support into AOSP?
http://www.htcdev.com/devcenter/downloads

Hopefully a way to implement the Sense Camera and Dialer into AOSP. That would be really awesome, if I could use those two in AOSP, I would switch immediately.

wph said:
Hopefully a way to implement the Sense Camera and Dialer into AOSP. That would be really awesome, if I could use those two in AOSP, I would switch immediately.
Click to expand...
Click to collapse
Well, the Sense stuff requires Sense, it's a choice between Sense and AOSP, really. You'd be better off de-Sensing a Sense ROM than hoping for Sense stuff on AOSP.

These have been available for almost week now

bbedward said:
These have been available for almost week now
Click to expand...
Click to collapse
Yes, I heard it was available on day 2 after the kernel code was released. I don't think anyone has looked into using it/implementing it yet though. I knew the kernel source dropped but I did not see this until today and I'm sure there are many people who didn't know it was even posted.

BenPope said:
Well, the Sense stuff requires Sense, it's a choice between Sense and AOSP, really. You'd be better off de-Sensing a Sense ROM than hoping for Sense stuff on AOSP.
Click to expand...
Click to collapse
I fully understand what you're saying, but these apps depend on the Sense framework, so that's why something like this gives hope.
Porting such stuff was always (almost) impossible, meaning you had to choose between the latest Android and Sense. When, on the long run, the One isn't supported anymore, you are stuck, since de-Sensing a ROM that isn't there is impossible. Maybe, and only maybe, with this framework files it is easier to port a couple of apps and include them in the latest AOSP.
For now I see it like this: HTC made these available, so they must have some reason. Might be because the Google Play Edition camera is not as good as the Sense one, which causes bad publicity, like the review on The Verge which gave a 4 for the camera. By providing these files, they maybe want to reach out to the community?

Forgive me for not knowing much on the development side of things, but if we can't find a way to port the Sense camera with this framework, what can we learn? And what would be required to see what the Sense camera requires to run on an AOSP ROM? Does this make it possible to port the Sense camera to at least the GE edition ROM? I know GE is different from AOSP, so I'm curious. The only reason I'm hesitant to stay on a stock android ROM is because of the camera.