[DEV] [JB] [CM10] [4.1.1] CyanogenMod 10 for the Huawei Ascend G300 [ROM] [Last updated: 26/08]

[Guest b4da55]

That's what I'm hoping :P

Let us know daz please

[Guest Dazzozo]

I need to be able to compile a libcamera first :P

[Guest b4da55]

I need to be able to compile a libcamera first :P

Didn't mean now just when you can

[Guest Dazzozo]

Sorry for the lack of responses, I was cloning the entire CAF tree so I could build their camera module easily -- I can't be bothered getting something to compile that might not even work.

So here we are, building CAF stock Jelly Bean for msm7627a. All for camera.msm7627a.so. :P

[Guest jsevi83]

So was that to find out if the problem is in liboemcamera or in libcamera?

[Guest Dazzozo]

Headers are still missing in the CAF source - if you disable camera stub in CAF (so that it builds the source) it errors out.

So, I'm back to hacking it up in my device config for CM... :P

[Guest Fagulhas]

Headers are still missing in the CAF source - if you disable camera stub in CAF (so that it builds the source) it errors out.

So, I'm back to hacking it up in my device config for CM...

Have you added our kernel camera headers to the libcamera sources?

Edited October 6, 2012 by Fagulhas

[Guest Dazzozo]

Yep, this is a genuine missing header.

It seems to be composed of bits of QCamera_Intf.h. Still hacking.

The only error currently is 'error: 'cam_sensor_fps_range_t' does not name a type'. Can't find cam_sensor_fps_range_t anywhere.

[Guest Dazzozo]

Right, the HTC msm8960 devices use a similar sort of libcamera, but obviously without the 7x27a support because they don't need it. Seems they've had to edit it a lot to get it to compile, working on it.

[Guest Dazzozo]

Good news: the libcamera works fully!

Bad news: the error isn't in libcamera and is still the same :P

[Guest tcpaulh]

Thanks for the updates. Page views for an alpha build are remarkable. Failing any insurmountable road blocks, this is going to be huge.

[Guest b4da55]

At least you know one wau or other and from what ive been reading thats not to much of a bad thing is it?

[Guest Dazzozo]

Ignore me, I'm an idiot, I used the wrong lib (the old one which we know doesn't work with ion)...

I'll be back shortly after testing it for real! :P

[Guest tcpaulh]

Lovely forwardslash jubbly

[Guest Romu_Android]

I am really in a hurry to test the update :)

[Guest Curlie]

If youd be an idiot there would be No cm10

[Guest djuroue]

Daz knows how to make my day! Great man!

[Guest ScutulatusCrotalus]

There's no reason to hurry. Release it, when it's done. Even if it'd be next year.

[Guest unaszplodrmann]

Ha! Next year? Good one!

* raps fingers on the table *

Ignore me, I'm an idiot, I used the wrong lib (the old one which we know doesn't work with ion)...

I'll be back shortly after testing it for real!

Well?! :P

[Guest Dazzozo]

It totally fails. I've given up completely with libcamera. It's such a goddamn mess.

I'm currently trying to track down what part of ion actually breaks the camera. Building with a full ion kernel, but with the qcom media parts in usermode disabled.

[Guest Curlie]

Could you publish the 3.0.8 Kernel in his last version (there is camera and bluetooth working?)

[Guest Dazzozo]

I don't want to. Simple as that. I want to get the most out of this and to be fair it's a dev thread.

[Guest Curlie]

Ok

And what about starting a new thread (Not a dev Rom )for no developers

Edited October 7, 2012 by Curlie

[Guest Dazzozo]

And hat about starting a new thread (Not a dev Rom )for no developers,,

No, because I don't care about general use at the moment.

[Guest Curlie]

And when youll care?

Edited October 7, 2012 by Curlie