Database Develop

Combining Features of different roms?

Like many other people I use the CyanogenMOD 4.1.999 (latest at this time).
I was looking at other ROMs, and I have noticed that there are features in other ROMs that are cool and interesting, that are not included in the cyanogenmod.
Is there a way to include the features of other ROMs into my ROM on my phone? (mytouch 3g)
Is there a way for me to suggest these features? Is there someone out there who might do this for me/ the community?

if the features are that good, they probably are already done. however, without specifics, we can't help you as there is no general procedure for adding features since each feature requires something different

Before you ask you can't (easily) add hero widgets to CM roms or anything like that.
To do so requires a large amount of modifications in other system files (like framework) that doesn't make it worth the time or effort. And don't bother asking someone like Cyanogen to do it either. He hates that.
But maybe if you give us specifics we might be able to serve you better with a better answer.

dont want to jack the thread but the new CM camera is wack i liked the 4.0.4 camera it was better and had zoom, can that be done?

[Q] Will the specialized hardware (camera, mics) pose problems for ROMs?

I'm wondering it some of the very specialized hardware will pose problems for developing cutom ROMs for the HTC One. Especially for AOSP ROMs.
The camera has image stabilization, the special ultrapixel sensor, the Zoe imaging style. Do these things rely on specialized software that would not be in AOSP ROMs?
The mics use a special dual membrane desgin for filtering noise, based on differing sensitivity of each membrane in each mic. Again, is this all hardware based functionality? Or would the noise filtering not work effectively in an AOSP ROM with AOSP kernel?
Thanks for any thoughts from people with knowledge of these things.

the camera will be worse on AOSP than on Sense as Sense has the closed source driver for the image chip.
Zoe etc will be not in AOSP ROMs and ultrapixel sensor should work though.
Mics will be working as well if we get some good devs.

Okay, so the ultrapixel sensor will work (low light photography, etc.) as advertised? But Zoe is an issue because basically it's a software protocol for capturing images and sharing them in a particular fashion?
And the dual-membrane mics will depend on the software in the ROM, but should be doable? I wouldn't want to lose all that potential improvement to in call audio quality.
I'm just interested in this question and any other hardware functionality that might be effected by ROMs, because the One seems like a device where the conceptualization of the hardware is much more integrated with the software that ships with it, than has been the case on other devices.
In the end, I guess I'm just not a fan of Sense (although the new version looks like a big improvement), but I usually like HTC's hardware. But I wouldn't want to lose any of the functionality of the great hardware but flashing a different ROM.

AW: [Q] Will the specialized hardware (camera, mics) pose problems for ROMs?
cb474 said:
Okay, so the ultrapixel sensor will work (low light photography, etc.) as advertised? But Zoe is an issue because basically it's a software protocol for capturing images and sharing them in a particular fashion?
And the dual-membrane mics will depend on the software in the ROM, but should be doable? I wouldn't want to lose all that potential improvement to in call audio quality.
I'm just interested in this question and any other hardware functionality that might be effected by ROMs, because the One seems like a device where the conceptualization of the hardware is much more integrated with the software that ships with it, than has been the case on other devices.
In the end, I guess I'm just not a fan of Sense (although the new version looks like a big improvement), but I usually like HTC's hardware. But I wouldn't want to lose any of the functionality of the great hardware but flashing a different ROM.
Click to expand...
Click to collapse
Well I am not a dev and we don't have any kind of source code of the kernel etc. But the basic camera should work although it will be harder to fix than on other devices. Zoe is simply a software which works only with sense framework as the rest of the sense features do.
Yes micro should be doable as well although it will take some time for sure to fix that by a dev. Expect early sense roms soon but don't expect aosp roms very soon to be working perfectly.
Let's see how it turns out to be when the device is released and some devs get their hands on
Sent from my HTC One X using xda premium

jonas2295 said:
Expect early sense roms soon but don't expect aosp roms very soon to be working perfectly.
Click to expand...
Click to collapse
Yeah, that's what I figured. Thanks for your thoughts.
I guess I can save my pennies while waiting for AOSP ROMs to go stable. At least this is such a desirable phone and it will be on almost all carriers, so I'm hoping it will attract a lot of devs.

AW: [Q] Will the specialized hardware (camera, mics) pose problems for ROMs?
cb474 said:
Yeah, that's what I figured. Thanks for your thoughts.
I guess I can save my pennies while waiting for AOSP ROMs to go stable. At least this is such a desirable phone and it will be on almost all carriers, so I'm hoping it will attract a lot of devs.
Click to expand...
Click to collapse
You are welcome :00
Sent from my HTC One X using xda premium

aosp vs sense camera

It's the sense camera really that much better then the cm/aosp camera? Opinions?

Sense will be that much better cos it interacts with ImageSense and has software to make full use of it. AOSP will have to create their own drivers to make the camera work at all. Should AOSP ever produce super awesome camera drivers, then I would expect it to at least match the Sense camera

As of right now Sense camera destroys AOSP camera, due to software.

Syn Ack said:
As of right now Sense camera destroys AOSP camera, due to software.
Click to expand...
Click to collapse
Yes I just went back to a sense Rom because of it. was really just wondering some of your opinions. I've heard from some that there's really not that much of a difference but it's pretty easily noticed.well hopefully they'll release a pure Google version and we'll be able to steal the drivers from that.

chriselmore said:
Yes I just went back to a sense Rom because of it. was really just wondering some of your opinions. I've heard from some that there's really not that much of a difference but it's pretty easily noticed.well hopefully they'll release a pure Google version and we'll be able to steal the drivers from that.
Click to expand...
Click to collapse
A pure Google version would probably only have basic drivers to ImageSense. If the device supports ImageSense, that means the drivers will have to go open sourced as well. Not sure how much HTC wants that to happen though.

Sense camera is better then AOSP camera.
Not for the zoe etc, but for the software and the ui

Can Someone make a camera guide ?

Yeah title says it.
So is there already a camera guide ? If so where ? And if not can somebody make one who is able to get good pictures with this phone because so far I'm hit and miss and my one x + camera is looking superior and that makes me sad cuz I love this phone. So if someone could Gove me some pointers or feels like making a good guide I'm sure a moderator would stickie it if its useful. I need some help and I'm sure I'm not the only one
Sent from my HTC One using XDA Premium HD app

I actually considered doing this briefly, but the camera in software 2.17.xx is very different and apparently much improved. For instance, in the ARHD 10 thread, there are reports of much better focusing in low light, a 60 fps option for video, and the ability to touch on a part of the image and *lock* focus and/or exposure. I haven't confirmed all these options personally, but as you can see it would be premature to give guidance on how to get the best results from the camera if you are using an early version of HTC One software.
The "best practices" as they stand now go something like this:
1 Stop using 1.29-based or AOSP ROMs
2 ???
3 Profit
The main problem in discussing these matters accurately is identifying the various *versions* of camera software. It is not enough to go into Settings .. Applications .. Camera and look at the version of the apk. You also have to know what libs are included elsewhere in the ROM. Custom kernel packages have achieved improved camera performance simply by replacing these libs without even touching the app itself.
If I get any real information on this I'll start a thread. I have to rip apart one of those flashable "Camera fix" zips first to see what we're talking about.

CM vs GPe - What's the difference?

Hey guys,
since i'm currently a flashaholic and dont want to stick with sense rom's (i just dont like them, can't say why). I'm trying around a bit, mostly with GPe rom's.
But whats the real difference between GPe and CM based rom's?
- Which rom/version is more stable?
- Which rom/version got the better perfomance/battery life?
I know that CM based roms are having more features and looking nice (at least for some peoples).
But i want a overall good performance, stability and moderate batterylife.
Thanks in advice

kewkie said:
Hey guys,
since i'm currently a flashaholic and dont want to stick with sense rom's (i just dont like them, can't say why). I'm trying around a bit, mostly with GPe rom's.
But whats the real difference between GPe and CM based rom's?
- Which rom/version is more stable?
- Which rom/version got the better perfomance/battery life?
I know that CM based roms are having more features and looking nice (at least for some peoples).
But i want a overall good performance, stability and moderate batterylife.
Thanks in advice
Click to expand...
Click to collapse
You've to try the roms for choose which is better.
Howeve the GE have some features like beats audio and some thing from sense, and the update are from htc with the latest release of android.
The CM rom have some features like the editing of status bar and so on, and are built from developers

Well, i dont hear that much music, so beats-audio is useless, not at all, but a bit.
I'm tired of testing around
Just thought you guys can share your experience with some of your used roms

kewkie said:
Well, i dont hear that much music, so beats-audio is useless, not at all, but a bit.
I'm tired of testing around
Just thought you guys can share your experience with some of your used roms
Click to expand...
Click to collapse
The problem is that mod don't like thread as: which rom is better for you?
This rom have a better battery then this?
And questions like this

Yeah i know, but it actually isnt a thread like this
I just wanna hear some experience

Google play edition roms are built on HTC's framework, or they were when it released. AOSP roms are actually built from AOSP framework using the libs and drivers and device trees that have been custom built for the one.
So the foundation of the Google Play edition, the part the user never sees, is a lot closer to stock sense from HTC minus the interface and launcher, while CM and other AOSP roms are built from AOSP style source code (CM from their source, others from their own custom source code some of which is truly custom and some of which is modified from CM source)
There's a lot of advantages to running AOSP source code based romms if you're going for an AOSP rom, but theres also a lot of users that can't use adb or fastboot and don't want to learn how and don't care to read into a rom thread, and the google play edition stuff is nice for people who want a phone with a stock google launcher, that doesn't have the sense interface heft, and just want things to work with an out of the box type experience. You know the type, they don't do a clean install for six months and wonder why the headlights in their car blink and settings force closes when they press the volume rocker.
There are certain apps that will work with the GPE and others that will only work with AOSP source, so on and so fourth. Half the people are better suited for GPE rom's and stockish foundations and then the other chunk of the people only buy their phone so they wipe it till its raw getting HTC stuff off and get custom AOSP source based roms on instead. It all depends on the user and what's better fitted for their experience.
In your case if you're not running sense roms at all and you like to follow development from what I've seen because I've seen you on here a good bit, I'd get into some real AOSP for a bit and see how you like it. The good thing about AOSP is that it's infinitely customizable and any user that wants too could be theming in a week and compiling/merging source in a month and cooking roms for their personal use. Most people way less than that. That doesn't mean that the devs publishing roms don't have a lot of time in them, it's just much easier to compile and work with the source than the HTC source is and the senseish framework.

Thanks @CharliesTheMan Thats a pretty good answer
Well i liked CM/AOSP rom's on my other phones and never used stock-ish ones.
Well, mainly i use my phone for phoning around (no sh*t! lol), social networking, taking photos and derping around a bit.
I never used the sense-features (blink feed, zoe, beats-audio etc. - i like the gallery, but honestly.. i like quickpic much more, i like it minimalism), neither like the look of sense.
I'm just a bit scared of using an AOSP rom, i dont really now why.. maybe scared of phone-signal-breaks, quality breaks or something like this.
But to be honest, i have to test it by myself i know, like the performance, stability and battery - its stuff i have to test and figure out by myself, because everyone is using the phone not in the same way and everyone got other recommendation from a rom and i got the point you wanted to say with your post