266 replies to this topic

[tucstwo]

flashed rom restored apps with titanium backup then ran quadrant @1325

Beautiful work man! Thats fantastic. Version 1.2 will be up in about 20 minutes with all kinds of adjustments.

[logan3824]

Nice, will we be able to change our speed to 1200? My.phone cant handle 1325 :/

[srzero]

Nice, will we be able to change our speed to 1200? My.phone cant handle 1325 :/

yes. Go into menu, system settings, then scroll down to performance then processor and change Max CPU speed to 1200

Sent from my XT912 using Tapatalk 2

[tucstwo]

Nice, will we be able to change our speed to 1200? My.phone cant handle 1325 :/

yes. Go into menu, system settings, then scroll down to performance then processor and change Max CPU speed to 1200

Sent from my XT912 using Tapatalk 2

I have made it even easier than that. Now you go into setting and I created a "Clock Speed" menu that you can set your stuff to. Even underclock if you want to save battery.

[srzero]

oh wow...guess I'm still on the "old" version.

Sent from my XT912 using Tapatalk 2

[srzero]

Full wipe on update?

Sent from my XT912 using Tapatalk 2

[fishaholic]

is there a "rotation bug" with this rom? i know a lot of cm9/cm10 builds have it :/

nevermind i read the entire OP lol... wonky rotations not that bad

[srzero]

is there a "rotation bug" with this rom? i know a lot of cm9/cm10 builds have it :/

yup...I think of it as character though. Sorry Tusctwo hope I'm not stepping on your feet.....

Sent from my XT912 using Tapatalk 2

[tucstwo]

is there a "rotation bug" with this rom? i know a lot of cm9/cm10 builds have it :/

nevermind i read the entire OP lol... wonky rotations not that bad

The rotation bug is going to be with any Cyanogenmod rom that isn't Kexec. If you want to try my kexec Jekyll that rom does not have the rotation bug.
It's an issue within the kernel and since we have locked bootloaders, there will always be a rotation bug on the 3.0.8 stock kernel

[tucstwo]

Full wipe on update?

Sent from my XT912 using Tapatalk 2

Full wipe not needed but I can it can't hurt. I dont flash a "data" folder when I build roms so everything that's within your /data/ etc should be just fine if left alone.

[logan3824]

Found a problem, if I go into System under settings then Notification bar > Widget buttons > then try to click Brightness Modes it just FCs on me. :/

[logan3824]

Also if you try to use the camcorder in 1080p it crashes....Not sure if this has to do with jelly or not.

[tucstwo]

Also if you try to use the camcorder in 1080p it crashes....Not sure if this has to do with jelly or not.

Let me try to replicate your problems on my phone. Maybe someone else can try it on theirs too and see if they have the same problems.?

Ok, as for the brightness menu, mine works just fine including all the options so I can't offer you too much help there, I'm not really sure. Maybe another user can pop in.

As far as camera, now I apologize as I haven't used good old CM9 in quite some time, but from what I recall from the "old days", We never had 1080p working properly on CyanogenMod. If you do get stuck in a 1080p loop. Go to Settings>Apps>All Click on Camera, then Click "Clear Data". This will reset the app.

Edited by tucstwo, 17 September 2012 - 03:32 PM.

[thrasher194]

Let me try to replicate your problems on my phone. Maybe someone else can try it on theirs too and see if they have the same problems.?

'

by default 740p, but soon as you turn to 1080p "Unfortunately, Camera has stopped".

[tucstwo]

'

by default 740p, but soon as you turn to 1080p "Unfortunately, Camera has stopped".

As I told the other poster, this is a CM9/Moto Kernel bug just like roation. Go into Settings>Apps>All Click Camera, then click clear data so you can use camcorder again. I'm gonna put this in the OP so no one else runs into it.

OP and Post 2 updated. Thanks guys for submitting bugs, it allows me to either fix em or warn others so they don't end up with problems.

Edited by tucstwo, 17 September 2012 - 03:40 PM.

[imhowie]

Overclocking:

I have changed the way overclocking works in Jekyll 1.2. The rom now boots up at stock clock speed. If you want to overclock or underclock your rom simply go into "Settings". Scroll down to "System" and select the new option "Clock Speed". Within that menu you can click which clock speed you want to run. Make sure you approve SU permissions when asked. Then click the reboot button.
If you want to play with the Governors/Schedulers grab an app like SetCP (there are others) and you can pick from all the added modules and click set on boot to lock them in. I still haven't figured out the best combo of clockspeed/governor/scheduler/battery life.

I can't really speak for this ROM, since I am currently Arctic HD, but the best combo I have found for performance and battery life is the Hotplugx governor with dealine scheduler. I'd give that a try and see what you think.

[tucstwo]

I can't really speak for this ROM, since I am currently Arctic HD, but the best combo I have found for performance and battery life is the Hotplugx governor with dealine scheduler. I'd give that a try and see what you think.

Guess we'll have to give it a shot.

Edit: I got a 3625 quad score with those settings.

Sent from my XT912 using Tapatalk 2

[Rinkle McBally]

Are you overclocked?

[churchmouth]

Anyone else just unable to get this to boot? I've tried three times now with three separate downloads and no matter what every time I hit "reboot phone now" and after the safestrap splash screen it just stays black and the boot animation never comes up. I let it sit for a good 15 minutes a few times thinking maybe there was just no boot ani but I got nothing. I did all the necessary wipes (data, cache, dalvik, system format) every time.

[Rinkle McBally]

Worked first boot fine for me. The boot up takes a long time and yes the screen does stay black longer then one would expect