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
Related
it is a wise choice ? i heard there so many problem with o2x but it is the cheapest dual core phone out there.
I was just thinking to do the opposite! Upgrade from the o2x to a nexus s...
It may be a dual core but with the official firmware only one core is visible. Plus all the problems with the radio and regular reboots...
Latest roms based on GB leak seem better so far. So there's maybe hope at the end of the tunnel.
CM is still not stable enough and is missing some features.
I would wait if I were you.
Sent from my LG-P990 using XDA App
i would do it, stock rom is okay if you install launcher pro, but i use cm7 and for me its very stable and 100 times better then other roms. and i never had a rebort or any other problems.
Yea I'm on a ox2 from a samsung galaxy s and its worked out well on cm7 so im happy with it
Sent from my Optimus 2X using Tapatalk
CyranoB said:
It may be a dual core but with the official firmware only one core is visible.
Click to expand...
Click to collapse
Not even close to being true.
Upgrade from nexus s to 2x??? Once the 2x receives gingerbread the nexus will probably be running ice cream sandwich.
Sent from my Nexus S using Tapatalk
And then the people on CM will get it pretty soon after, not a huge deal.
Indeed true
So final solution having one more core for cheap price is always good deal.
CyranoB said:
I was just thinking to do the opposite! Upgrade from the o2x to a nexus s...
It may be a dual core but with the official firmware only one core is visible. Plus all the problems with the radio and regular reboots...
Latest roms based on GB leak seem better so far. So there's maybe hope at the end of the tunnel.
CM is still not stable enough and is missing some features.
I would wait if I were you.
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
The opposite wouldn't be an upgrade.
You are not even making any sense. "Only one core is visible"? Visible to what? Maybe some outdated app may not represent it correctly, but rest assured that both cores are working.
CM *is* stable. In fact, the nightly builds have been more stable than the so-called "official" ROMs from certain OEMs. Missing features? There are only 2: the A2DP BT profile and FM Radio.
enigma00 said:
The opposite wouldn't be an upgrade.
You are not even making any sense. "Only one core is visible"? Visible to what? Maybe some outdated app may not represent it correctly, but rest assured that both cores are working.
CM *is* stable. In fact, the nightly builds have been more stable than the so-called "official" ROMs from certain OEMs. Missing features? There are only 2: the A2DP BT profile and FM Radio.
Click to expand...
Click to collapse
The myth that Android 2.2 makes more cores than one useless is continually perpetuated. It's incorrect as you pointed out, and people should check their facts.
However, CM is not stable on my O2x. It often black-screens when charging with wall charger, and sometimes black-screens for no apparent reason. Other issues for me are that the sound quality for the other party is plain awful, regardless of what basebands and RILs I've tried. Using BT headset fixes that however.
This might be my device that's defective (regarding the crashes, the phone sound quality is quite known), and yesterday I installed the latest stock for my region (EURO Open) to see if that indeed is the case. The latest stock here (10D) doesn't feel very slow, and the phone sound quality has greatly improved.
drcorwe said:
The myth that Android 2.2 makes more cores than one useless is continually perpetuated. It's incorrect as you pointed out, and people should check their facts.
However, CM is not stable on my O2x. It often black-screens when charging with wall charger, and sometimes black-screens for no apparent reason. Other issues for me are that the sound quality for the other party is plain awful, regardless of what basebands and RILs I've tried. Using BT headset fixes that however.
This might be my device that's defective (regarding the crashes, the phone sound quality is quite known), and yesterday I installed the latest stock for my region (EURO Open) to see if that indeed is the case. The latest stock here (10D) doesn't feel very slow, and the phone sound quality has greatly improved.
Click to expand...
Click to collapse
I should probably count my blessings because I have not seen the issues you describe, with either the stock ROM or CM.
I can speculate HW issues (e.g. LG's manufacturing defect, nVidia's or other suppliers' defect, or just plain ol' HW revisions) just based on the fact that some never had it while the others continue to experience the problems.
enigma00 said:
The opposite wouldn't be an upgrade.
You are not even making any sense. "Only one core is visible"? Visible to what? Maybe some outdated app may not represent it correctly, but rest assured that both cores are working.
CM *is* stable. In fact, the nightly builds have been more stable than the so-called "official" ROMs from certain OEMs. Missing features? There are only 2: the A2DP BT profile and FM Radio.
Click to expand...
Click to collapse
Let me re-phrase: "using a o2x with a stock rom doesn't feel like using a dual core phone."
With the original rom, the o2x is far less snappy than a Nexus S. LG O2X can show up a better hardware on paper, but the crappy software implementation makes it feel far less snappy.
CM is still not stable for my setup Phone/Baseband/Provider. I always had diverse problems, from nightly #1 to #127 (didn't test them all of course). Now this is not to criticize CM: they never pretended to be stable and are for sure doing a incredible job with what they've been given. But someone coming from Nexus S cannot expect the same level of stability. It's up to you to see if you can live with it or not.
well . i guess i need to wait and see first .
yeah nexus s is fast and stable , load it with any custom roms , it is great .
thanks for you all comment and reply , it is because o2x is the cheapest dual core phone out there.
Cant we just put the samsung's rom from the galaxy r on it? ahaha
Personally I went from O2X to SGSII to NS and now back to O2X.
NS (Nexus S) of the tree I had, none where ok, first flash not working scratching sound on phone. Second allot of pixel errors. Third one pixel error bad built quality. After all the O2X is a great combo of features, great built quality, and gingerbread just around the corner, would not hesitate a bit getting the O2X over the NS.
whc said:
Personally I went from O2X to SGSII to NS and now back to O2X.
NS (Nexus S) of the tree I had, none where ok, first flash not working scratching sound on phone. Second allot of pixel errors. Third one pixel error bad built quality. After all the O2X is a great combo of features, great built quality, and gingerbread just around the corner, would not hesitate a bit getting the O2X over the NS.
Click to expand...
Click to collapse
You missed another 'feature' - unreliability.
Also, why did you ditch the SGSII ?
I am coming from gs3. There were huge problems about it not being open source because of undocumented exynos by Samsung. Since I am looking to run cm flawlessly with all future updates of cm coming on my phone how is htc one in that field. Will it get stable CM? Isin't snapdragon 600 open source?
Snapdragon is always opensource. I am guessing the real problem with having a stable CM build on HTC one is it's features like Zoe & camera. Both require HTC's own imaging chipset on which are closed source. So unless you can consider having a basic camera then yes it should be stable.
Riyal said:
Snapdragon is always opensource. I am guessing the real problem with having a stable CM build on HTC one is it's features like Zoe & camera. Both require HTC's own imaging chipset on which are closed source. So unless you can consider having a basic camera then yes it should be stable.
Click to expand...
Click to collapse
CM anyways does not implement these extra features right?
jshashwat93 said:
CM anyways does not implement these extra features right?
Click to expand...
Click to collapse
Correct. Anything that's not AOSP won't be in any CM build so 3rd party apps won't be in it
EddyOS said:
Correct. Anything that's not AOSP won't be in any CM build so 3rd party apps won't be in it
Click to expand...
Click to collapse
So what are the chances of a perfectly up and running AOSP on HTC One?
jshashwat93 said:
So what are the chances of a perfectly up and running AOSP on HTC One?
Click to expand...
Click to collapse
Using HTC's dedicated imaging chip is 98% not possible 2% if someone would bother reverse engineering the driver which is a very2x tedious task and I doubt anyone would bother.
So unless you require the imaging chip on what you call perfect then highly unlikely.
Riyal said:
Using HTC's dedicated imaging chip is 98% not possible 2% if someone would bother reverse engineering the driver which is a very2x tedious task and I doubt anyone would bother.
So unless you require the imaging chip on what you call perfect then highly unlikely.
Click to expand...
Click to collapse
Care to explain that? What do you mean by imaging chip and what does it do?
HTC s last flagship one x still doesn't have flawless cm though its getting close. If enough major players get involved maybe there's a chance but the odds were stacked against h8rift as amazing and appreciated as his work is.
jshashwat93 said:
Care to explain that? What do you mean by imaging chip and what does it do?
Click to expand...
Click to collapse
The camera. HTC has always used unique hardware for their camera and writes their own drivers that are not open source so the only way to get the camera working 100% in CM would be if some one went through the HTC driver.
Miui
nullkill said:
The camera. HTC has always used unique hardware for their camera and writes their own drivers that are not open source so the only way to get the camera working 100% in CM would be if some one went through the HTC driver.
Click to expand...
Click to collapse
But how come MIUI team has been able to port HTC camera & zoe along with gallery on their custom Rom? Any idea?
CM Rom + HTC Zoe Camera = Perfect combination
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
So here's what I ask all of those reading. What is the closest possible equivalent to the 5.0-5.5 sense camera found on our device on aosp. I know that it's technically the same but to me the colors look better on sense, and there's less "loudness" on the pictures. I also understand that porting will absolutely not work due to different frameworks. I love aosp for it's feel but sense for the camera and ir capability and also since my girlfriend loves to take pictures with my phone, and with several roms on the original android dev thread the cameras show up wide and do not produce good photos. In all can someone point me towards a sort of "sense on aosp" camera, any help would be much appreciated.
Randomly enough I'm an Android developer that this section could make use of.
So my question is: Is the community interested in CM based ROMs? (due to the fact that we lose DRM when we unlock the bootloader)
If there are indeed people who are interested. Do you have any ROMs which you wish to be ported for Z3C?
Tbh i guess the biggest issue is that people think that unlocking the bootloader turns the camera into to a old toaster. Atleast that is what my fear was before unlocking. After unlock i can barely make out a difference. Not to mention DRM fixes exists.
What really bothers me however is the lack of kernels for 6.0 and stock roms. Myself5 and Someone777 got custom kernels covered for 5.1 but nothing really exists for 6.0.
I read somewere about them planning 3.10 linux kernels based on Sony AOSP. Unsure for what type of roms tho.
Myself I run two things on my phone
1. Stock Rom + Custom Kernel.
2. Paranoid Android or CM based. PA prefered. + Custom Kernel.
This community could sure use an extra dev tho.
I'd use CM/AOSP based rom in a heartbeat had it not been for that reversed fish eye bug
However they are even now pretty stable other than that bug, I've tried couple of them, and with the removal of Z1 platform camera blobs, we might even see that being fixed. Someone reported that with latest camera blob updates, camera quality was improved though.
That aside, custom rom I have loved was SlimRom, as I have used it on my old S2, and it's still loaded on it, but that's not CM based.
I don't know, it doesn't matter much which rom, just as long as it's stable and has all basic functions working well
---------- Post added at 17:42 ---------- Previous post was at 17:24 ----------
Exzu said:
After unlock i can barely make out a difference. Not to mention DRM fixes exists.
I read somewere about them planning 3.10 linux kernels based on Sony AOSP. Unsure for what type of roms tho.
This community could sure use an extra dev tho.
Click to expand...
Click to collapse
The difference in quality is noticeable when you run into conditions with less light (let's say when ISO goes over 400), but even that can be improved with further camera blob releases. DRM fixes do not apply to CM/AOSP because framework and noise reduction algorithms differ from stock Sony roms.
It would be very nice to have a 3.10 branch kernels
Yep, an extra dev could be really helpful, considering the lack of devs and development for this device. IMO the devs around here did quite a good job, but any extra hand is welcome.
Not really for myself. I would like the last android n preview. I prefer to have the "aosp" rom from Sony than a buggy rom, it's so much work for dev to get something stable. Than the Sony concept rom, which are working so good.
I ran RR for quite a while, and as always enjoyed running something AOSP / CM based (especially coming from Nexus). I lived with the camera being ****ty and all was fine. But as nelvinchi disappeared, I tried put SLiMM (stock based), and to be honest - I absolutely love the camera quality! I can't imagine going back to that ****ty camera.
But whatever happened to Sonys OS camera project?
Hi,
I would really love to see AICP (probably the best CM based rom at this point) for our Z3c.
I don't care much about pictures quality. Using camera only to scan documents or to take notes.
Now running Concept rom with unlocked bootloader.
Yeah sure but good luck getting a working camera ...there isn't a cm rom out there with a properly functioning camera...
The only big issue is the fish-eye bug.
No fix, no party.
istux said:
The only big issue is the fish-eye bug.
No fix, no party.
Click to expand...
Click to collapse
I'd say, for my requirements, it is the only issue keeping me away from AOSP/CM. I can say that I use camera often, so I need something with decent quality (without any kind of fish-eye of course). I have used MultiROM, but it is time consuming to reboot in stock ROM to capture the moment. On top of that, new MultiROM v33x is not working, and Myself5 is nowhere to be seen so I lost hope for a fix.
Cirra92 said:
I'd say, for my requirements, it is the only issue keeping me away from AOSP/CM. I can say that I use camera often, so I need something with decent quality (without any kind of fish-eye of course). I have used MultiROM, but it is time consuming to reboot in stock ROM to capture the moment. On top of that, new MultiROM v33x is not working, and Myself5 is nowhere to be seen so I lost hope for a fix.
Click to expand...
Click to collapse
NOBODY likes to have a broken camera and that's the reason why EVERYBODY keeps away from AOSP roms, like you.
Frankly I gave up on development for this phone MANY MANY months ago.
We'll never get a fix for the fisheye bug, let's face it.
istux said:
NOBODY likes to have a broken camera and that's the reason why EVERYBODY keeps away from AOSP roms, like you.
Frankly I gave up on development for this phone MANY MANY months ago.
We'll never get a fix for the fisheye bug, let's face it.
Click to expand...
Click to collapse
the people over at paranoid android tried but failed miserably with their recent initial release for MM and haven't heard a peep from them since...i'm sure it will get removed from their supported devices...
I wish blisspop would be ported to the z3c.
i'm pretty sure OP would be a god in this community if they produced a working CM/AOSP rom with a fully functioning camera.
istux said:
NOBODY likes to have a broken camera and that's the reason why EVERYBODY keeps away from AOSP roms, like you.
Frankly I gave up on development for this phone MANY MANY months ago.
We'll never get a fix for the fisheye bug, let's face it.
Click to expand...
Click to collapse
We won't probably, because Sony doesn't want to release proper blobs, not that they can't, they don't want to.
Fictional Reality said:
the people over at paranoid android tried but failed miserably with their recent initial release for MM and haven't heard a peep from them since...i'm sure it will get removed from their supported devices...
Click to expand...
Click to collapse
Yea, the PA team have realized probably what crap they have put themselves into. Let's face the simple fact, which should be pretty obvious: people from Sony just don't want to release proper blobs/drivers for Z3 series. Why? That's something we can only guess. But the fact that they have released blobs/drivers for Z1 series (which have been used on Z3 series up until let's say 2 weeks ago) and have now added X camera blobs is something beyond logic. Why did they leave out Z3 series (which has different camera lens compared to Z1, but used Z1 blobs anyway)? It's not like Qualcomm forbid them to for Z3 series specifically, since Z1 has also proprietary DRM functions, yet it has working AOSP/CM with proper drivers released.
Not that I know anything about android drivers/blobs, coding and building, but this is what devs here were discussing, and I would trust them more than Sony officials.