Jump to content

[ICS] [CM9] [4.0.4] CyanogenMod 9 for the ZTE Crescent [ROM] [Last updated: 13/07]


Recommended Posts

Guest MadEye Moody
Posted

Is there a workaround for the one photo from camera per reboot problem? like uloading and loading a module or something?

Guest BrideOfTheAtom
Posted

Is the Vivacity issue going to occur for those with the atmel touch controller? Should there also be an atmel-touchscreen.kl?

Do Vivacity devices even exist with atmels?

I believe there are some vivacity's with Atmel controllers according to this thread:

Guest MadEye Moody
Posted

Is there a workaround for the one photo from camera per reboot problem? like uloading and loading a module or something?

Am I the only one experincing this?

I install the ROM, setup a2sd, reboot

I open the camera, click the blu button, it freezes the preview. (5MP)

I close the camera, re-opens it, change the resolution to 3MP, press the blue button, nothing happens - no freeze, but no photo

I reboot, open the camera, take a picture, it takes the picture, no more preview available. I close and take the camera. Now preview is back

I try to take the picture, nothing happens. I click the blue button again and again, now I get a FC

I open camera again and now it says "Camera error" "Can't connect to the camera"

Is it expected from this cam fix?

Guest adroc
Posted (edited)
Am I the only one experincing this?

we are at least 2 :)

Well, not exactly, what happens seems much more random than what you describe". sometimes it will work, sometimes not at all, sometimes, it work for a while...

it seems work is being done about this by cyanogen developers ( see comment by tilal a few posts back )

Is it expected from this cam fix?

I'd say yes, Dazz said camera is now turning on , but

temperamental for just about every device
Edited by adroc
Guest NinjehKitteh
Posted (edited)

I believe there are some vivacity's with Atmel controllers according to this thread: http://android.modac...re-do-you-have/

I entered the code on there but I get 'Connection problem or invalid MMI code.' so I can be of no help :/

-Ninjeh.

Edited by NinjehKitteh
Guest BrideOfTheAtom
Posted

I entered the code on there but I get 'Connection problem or invalid MMI code.' so I can be of no help :/

I think that code only worked in the stock rom not CM9.

Guest NinjehKitteh
Posted

I think that code only worked in the stock rom not CM9.

That may be why then

-Ninjeh.

Guest NinjehKitteh
Posted

My TMV has an Atmel.

Are you running the ROM?

-Ninjeh.

Guest Dazzozo
Posted (edited)

Talking to fr0do in IRC now.

Also, the codes will only work in the stock ROM as they are part of the ZTE emode dialer.

Edit: As I suspected, the same fix needs to be repeated for the atmel touch controller. I'll put out a full build and a new patch with these changes.

Edited by Dazzozo
Guest NinjehKitteh
Posted

Talking to fr0do in IRC now.

Also, the codes will only work in the stock ROM as they are part of the ZTE emode dialer.

Edit: As I suspected, the same fix needs to be repeated for the atmel touch controller. I'll put out a full build and a new patch with these changes.

Just flashed my first update since the 14th (I'm a little behind :P), I'll tell you if anything goes wrong

-Ninjeh.

Guest NinjehKitteh
Posted

Straight away I've got something. In the Play Store it comes up as T-Mobile Unknown ZTE Crescent.

-Ninjeh.

Guest Dazzozo
Posted

Straight away I've got something. In the Play Store it comes up as T-Mobile Unknown ZTE Crescent.

-Ninjeh.

Beat you to it ;) https://github.com/Dazzozo/android_device_zte_blade2/commit/d9a463641bbfebbf341deca475c26fa1abc4e5e0

Additionally, a new patch including the fix for atmel touchscreens.

http://crescent.thebronasium.com/29042012-cm9-blade2-tmo-home-patch-r2.zip

When I get a verification from someone with a TMV + atmel I'll go live with a new build.

Guest Dazzozo
Posted

Is there any way I can find out whether I have syaptics or atmel from in the ROM?

-Ninjeh.

You can try being crafty and look through a logcat for a mention of atmel or synaptics, I'm not sure of another method. :P

Guest NinjehKitteh
Posted

Okay then, so how do I logcat? :P

-Ninjeh.

Guest Dazzozo
Posted

There's apps for it, or you enter "adb logcat" in to CMD with the phone plugged in with USB debugging enabled.

Guest NinjehKitteh
Posted

Just had a random look through the zip files, and realised you can actually customise the boot animation... This could be fun...

-Ninjeh.

Guest Dazzozo
Posted

Just had a random look through the zip files, and realised you can actually customise the boot animation... This could be fun...

-Ninjeh.

You don't even have to replace the system one. You can just put a bootanimation.zip at /data/local and it will override the one in /system/media.

Guest Dazzozo
Posted

Right, abort, abort. The button bindings for atmel are different and I don't know what they should be bound to. Apparently the same patch broke all of fr0do's buttons.

Guest welshrage
Posted

for some reason (havent installed the latest build yet), my phone randomly rebbots itself... i can leave it on the table and now and again it just reboots itself

Guest NinjehKitteh
Posted

for some reason (havent installed the latest build yet), my phone randomly rebbots itself... i can leave it on the table and now and again it just reboots itself

I've had that too, hasn't happened in a while tho.

-Ninjeh.

Guest Dazzozo
Posted

Reboots come and go. I wouldn't worry about them too much, everything will improve without me even doing anything.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.