ROM cm6 AIO v7 (based on beta 0.40)

[Guest thisweb]

Wouyld it be possible to add 'get front camera working' to the list of to do. Obviously not a major priority but it would be great, especially for gingerbread since this can be switched natively to use with any app. Also the front camera is a rare feature on other android phones, includeing ZTE so would be nice to have that implemented on the cheap old pulse like the iphone has.

[Guest Richard_Arkless]

Can anyone tell me, is vesion 6b4 based on CM6 2.2 or CM7 2.3 (gingerbread) rom?

Thanks

You should be able to get that answer considering its in the title "rom cm6 AIO", I wont be making a custom cm7 rom until it is stable

Wouyld it be possible to add 'get front camera working' to the list of to do. Obviously not a major priority but it would be great, especially for gingerbread since this can be switched natively to use with any app. Also the front camera is a rare feature on other android phones, includeing ZTE so would be nice to have that implemented on the cheap old pulse like the iphone has.

I dont think we will ever get it working, sorry :lol:

But I guess it wont hurt to add it in the task list see if anyone is willing to pick it up and try to get it working

[Guest totiadrenalin]

Neocore 28.0 fps on my phone.

CM6 AIO 6 ROM.

[Guest jeddy1]

Neocore 28.0 fps on my phone.

CM6 AIO 6 ROM.

Mine get 29.3 :lol:

No just jokking:).26.2 I had without your performances

[Guest Richard_Arkless]

Neocore 28.0 fps on my phone.

CM6 AIO 6 ROM.

Wow great, the most I get is 27.3 but im planning on wiping soon to see if I get even more (most likely will), Is that with the opengl es 1.1 or without? (please say without cause then we will get an even bigger fps with it :lol:)

Im planning on releasing b5 as soon as you finish the stuff you want to do, as for when will it be releasing it as final, I would say after we get the low priority bugs fixed, any medium or high things will be a bonus :)

Do you agree?

Edited January 21, 2011 by Richard_Arkless

[Guest jeddy1]

That would be nice. Richard why you wouldn't work on a cm7?

Just asking :lol:

Edited January 21, 2011 by jeddy1

[Guest Richard_Arkless]

Mine get 29.3 :lol:

No just jokking:).26.2 I had without your performances

We heard you the first time :)

[Guest totiadrenalin]

Wow great, the most I get is 27.3, Is that with the opengl es 1.1 or without? (please say without cause then we will get an even bigger fps with it :lol:)

Im planning on releasing b5 as soon as you finish the stuff you want to do, as for when will it be releasing it as final, I would say after we get the low priority bugs fixed, any medium or high things will be a bonus :)

Do you agree?

Ok Man!

But I did this with the 710MHZ oc kernel.

[Guest Richard_Arkless]

Ok Man!

But I did this with the 710MHZ oc kernel.

ok great, keep up the good work :lol:

That would be nice. Richard why you wouldn't work on a cm7?

Just asking :)

Yea originally me and toti (mostly toti as I was incredibly busy at the time with uni work) was trying to port it then tom went and released his version so I decided to abandon it, as for when will I build off it, I plan to when it is stable and everything that works with cm6 works with cm7

Edited January 21, 2011 by Richard_Arkless

[Guest totiadrenalin]

Ok Man!

But I did this with the 710MHZ oc kernel.

Would you mind if I try to perform a bit modification on your current CM AIO v6b4.zip?

But I'll first do it personal on my phone!

I think that I find the reason why it says that it can't connect with the camera device after we take the second shut with 3MP.

But let mi first get prove my suspects.

[Guest Richard_Arkless]

Would you mind if I try to perform a bit modification on your current CM AIO v6b4.zip?

But I'll first do it personal on my phone!

I think that I find the reason why it says that it can't connect with the camera device after we take the second shut with 3MP.

But let mi first get prove my suspects.

Yea sure, why not test it on beta 5?, it would be great to finally say goodbye to this really annoying bug

Edited January 21, 2011 by Richard_Arkless

[Guest Richard_Arkless]

Would you mind if I try to perform a bit modification on your current CM AIO v6b4.zip?

But I'll first do it personal on my phone!

I think that I find the reason why it says that it can't connect with the camera device after we take the second shut with 3MP.

But let mi first get prove my suspects.

sorry, double post

Edited January 21, 2011 by Richard_Arkless

[Guest Richard_Arkless]

Would you mind if I try to perform a bit modification on your current CM AIO v6b4.zip?

But I'll first do it personal on my phone!

I think that I find the reason why it says that it can't connect with the camera device after we take the second shut with 3MP.

But let mi first get prove my suspects.

sorry, tripple post, my internet is terrible atm because sky is playing with the lines

Edited January 21, 2011 by Richard_Arkless

[Guest totiadrenalin]

LOL!

Check this stuff!

I/DEBUG   ( 3923): debuggerd committing suicide to free the zombie!

I/DEBUG   ( 3956): debuggerd: Dec  1 2010 08:39:29

I/BootReceiver( 1327): Copying /data/tombstones/tombstone_04 to DropBox (SYSTEM_

TOMBSTONE)

W/WindowManager( 1327): App freeze timeout expired.

W/WindowManager( 1327): Force clearing freeze: AppWindowToken{452ebba8 token=His

toryRecord{45261de8 com.android.camera/.Camera}}

D/dalvikvm( 1327): GC_EXPLICIT freed 6200 objects / 627064 bytes in 197ms

W/ActivityManager( 1327): Launch timeout has expired, giving up wake lock!

W/ActivityManager( 1327): Activity idle timeout for HistoryRecord{45261de8 com.a

ndroid.camera/.Camera}

D/dalvikvm( 3784): GC_EXPLICIT freed 508 objects / 38952 bytes in 65ms

I/power   ( 1327): *** set_screen_state 0

I/GPSButton( 1327): Update State

D/QCRIL_MSC ( 1211): "RIL"=>"AMSS" [ label = "cm_mm_client_ss_reg()"];

D/QCRIL_MSC ( 1211): "RIL"=>"AMSS" [ label = "cm_mm_client_ss_reg()"];

W/ActivityManager( 1327): Activity pause timeout for HistoryRecord{45261de8 com.

android.camera/.Camera}

[/codebox]

I upload the debugger tombstone where the camera process stack

tombstone_04.txt

Edited January 21, 2011 by totiadrenalin

[Guest Richard_Arkless]

LOL!

Check this stuff!

I/DEBUG   ( 3923): debuggerd committing suicide to free the zombie!

I/DEBUG   ( 3956): debuggerd: Dec  1 2010 08:39:29

I/BootReceiver( 1327): Copying /data/tombstones/tombstone_04 to DropBox (SYSTEM_

TOMBSTONE)

W/WindowManager( 1327): App freeze timeout expired.

W/WindowManager( 1327): Force clearing freeze: AppWindowToken{452ebba8 token=His

toryRecord{45261de8 com.android.camera/.Camera}}

D/dalvikvm( 1327): GC_EXPLICIT freed 6200 objects / 627064 bytes in 197ms

W/ActivityManager( 1327): Launch timeout has expired, giving up wake lock!

W/ActivityManager( 1327): Activity idle timeout for HistoryRecord{45261de8 com.a

ndroid.camera/.Camera}

D/dalvikvm( 3784): GC_EXPLICIT freed 508 objects / 38952 bytes in 65ms

I/power   ( 1327): *** set_screen_state 0

I/GPSButton( 1327): Update State

D/QCRIL_MSC ( 1211): "RIL"=>"AMSS" [ label = "cm_mm_client_ss_reg()"];

D/QCRIL_MSC ( 1211): "RIL"=>"AMSS" [ label = "cm_mm_client_ss_reg()"];

W/ActivityManager( 1327): Activity pause timeout for HistoryRecord{45261de8 com.

android.camera/.Camera}

[/codebox]

lol at the first couple of lines, oh google you comedians :lol:

Edited January 21, 2011 by Richard_Arkless

[Guest totiadrenalin]

lol at the first couple of lines, oh google you comedians :lol:

New achievements in digging the source of the camera bug.

In CameraService.cpp in the source (frameworks/base/camera/libcameraservice/CameraService.cpp)

Simply read this lines

void CameraService::Client::disconnect()

{

    LOGD("Client E disconnect");

    Mutex::Autolock lock(mLock);

    mCameraService->removeClient(mCameraClient);

    if (mHardware != 0) {

        // Before destroying mHardware, we must make sure it's in the

        // idle state.

        mHardware->stopPreview();

        // Cancel all picture callbacks.

        mHardware->cancelPicture(true, true, true);

        // Release the hardware resources.

        mHardware->release();

    }

    mHardware.clear();

    LOGD("Client X disconnect");

}

[/codebox]

And this lines to:

[codebox]
// tell the service whether to callback with each preview frame
void CameraService::Client::setHasFrameCallback(bool installed)
{
Mutex::Autolock lock(mLock);
mHasFrameCallback = installed;
// If installed is false, mPreviewBuffer will be released in stopPreview().
}

// start preview mode, must call setPreviewDisplay first
status_t CameraService::Client::startPreview()

So this could be the state where the camera service is releasing the camera device after each time we take a picture.

But the problem might be somewhere with the media service to!

Because this is happening only with 3MP!

Now just let mi find what could be the reason for this?

I just have to find the original cm6 source code of the CM6 rom that tom was using to build this rom.

I think that I could find the reason why, but I'm afraid, that the rom need's to be re-compiled again from the source.

I truly hope's that I'm wrong.

EDIT:

SO?!

As fare as I understand.

The first code that I post makes sure that the camera device is in idle state before the camera process get killed.

And the second code is what makes the camera to stop responding.

This is what we are dealing with.

See it for your self

Edited January 21, 2011 by totiadrenalin

[Guest thisweb]

You should be able to get that answer considering its in the title "rom cm6 AIO", I wont be making a custom cm7 rom until it is stable

I dont think we will ever get it working, sorry :)

But I guess it wont hurt to add it in the task list see if anyone is willing to pick it up and try to get it working

yeh, sorry, that figures. thanks.

Great. I know its a long shot without drivers but i know you clever pulse enthusiast types like pushing boundries! :lol:

youve all done great work on everything so far !!! I can only dream of having such talents.

Edited January 21, 2011 by thisweb

[Guest thisweb]

sorry, tripple post, my internet is terrible atm because sky is playing with the lines

Sky. Eeew! ;(

[Guest Richard_Arkless]

Sky. Eeew! ;(

Which is why im getting bt infinity once it has reached my area :lol:

Edited January 22, 2011 by Richard_Arkless

[Guest totiadrenalin]

Which is why im getting bt infinity once it has reached my area :lol:

New Neocore resoult now!

29.3

I found new updates of openGL 1.1

And now I'll add them in my folder on dropbox.

But still can't find the reason why does the libcameraservice doesn't release the camera after taking picture.

The problem might isn't there, where I'm looking for.

But Please somebody to tell me which CM6 source code did Tom G use to build this rom.

I have to take a look into that source to get to the core of this camera bug.

Best regards

TOTI

Edited January 22, 2011 by totiadrenalin

[Guest Richard_Arkless]

New Neocore resoult now!

29.3

I found new updates of openGL 1.1

And now I'll add them in my folder on dropbox.

But still can't find the reason why does the libcameraservice doesn't release the camera after taking picture.

The problem might isn't there, where I'm looking for.

But Please somebody to tell me which CM6 source code did Tom G use to build this rom.

I have to take a look into that source to get to the core of this camera bug.

Best regards

TOTI

ive messaged him so hopefully he will link it to us :lol:

Well done btw with the increase in fps

[Guest totiadrenalin]

Why on earth the lights doesnt work with the new CM AIO v6b4 rom?

With the official TOM's CM6.1 rom the lights was working with no problem?!

As i remember the lights stop working until I install the CM AIO v4?!!

Is this solved in the Alpha rom?

And where to find the solution in there?

Richard!

Is there some problem with lights.u8220.so, or lights.msm7k.so.

Or somewhere in build.prop, or maybe,.....?

I don't know?

Just tell me is this issues solved now?

And how to solve it on my phone?

[Guest rulerofkaos]

Why on earth the lights doesnt work with the new CM AIO v6b4 rom?

With the official TOM's CM6.1 rom the lights was working with no problem?!

As i remember the lights stop working until I install the CM AIO v4?!!

Is this solved in the Alpha rom?

And where to find the solution in there?

Richard!

Is there some problem with lights.u8220.so, or lights.msm7k.so.

Or somewhere in build.prop, or maybe,.....?

I don't know?

Just tell me is this issues solved now?

And how to solve it on my phone?

I have got this problem, too, on v5. If you change the brightness with the widget or in the statusbar the lights are working until you switch the screen off.

BTW did you post a link to your dropbox? I would like to check the opengl libs.

Edited January 22, 2011 by rulerofkaos

[Guest Richard_Arkless]

Why on earth the lights doesnt work with the new CM AIO v6b4 rom?

With the official TOM's CM6.1 rom the lights was working with no problem?!

As i remember the lights stop working until I install the CM AIO v4?!!

Is this solved in the Alpha rom?

And where to find the solution in there?

Richard!

Is there some problem with lights.u8220.so, or lights.msm7k.so.

Or somewhere in build.prop, or maybe,.....?

I don't know?

Just tell me is this issues solved now?

And how to solve it on my phone?

I have got this problem, too, on v5. If you change the brightness with the widget or in the statusbar the lights are working until you switch the screen off.

BTW did you post a link to your dropbox? I would like to check the opengl libs.

by lights you mean the back lights on the keys, as far as I know it has never worked for me, I will compare the files with the official 0.40 rom see if I manage to figure it out, dont worry yourself with it ill handle it, what matters atm is getting the camera working after 3 shoots and to do that we need to wait for a reply from tom

rulerofkaos, the new libs are under the alpha folder of my dropbox then rom then modif-TOTI all changes he makes is there, once the beta is released ill merge the changes, originally I wanted it all in the alpha rom, not in another folder but its up to toti on how he wants to handle his files

Edited January 22, 2011 by Richard_Arkless

[Guest totiadrenalin]

by lights you mean the back lights on the keys, as far as I know it has never worked for me, I will compare the files with the official 0.40 rom see if I manage to figure it out, dont worry yourself with it ill handle it, what matters atm is getting the camera working after 3 shoots and to do that we need to wait for a reply from tom

rulerofkaos, the new libs are under the alpha folder of my dropbox then rom then modif-TOTI all changes he makes is there, once the beta is released ill merge the changes, originally I wanted it all in the alpha rom, not in another folder but its up to toti on how he wants to handle his files

OK!

Something mess up in libcameraservice.so for sure.

But I'm not sure even with the camera app

In here I found some very useful information about the camera app.