• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] Quattrimus JB (CM10.1, AOKP42)

ortrigger said:
Those are options in the cLock lockscreen widget. You should be able to find it under lockscreen settings and then choose clock widget.

@death: Is CM10.1 still using chronus? I thought they switched to cLock. I guess I should try out straight cm10.1 now being as I've only used roms that are derivatives and/or use parts of it up until now.
Click to expand...
Not sure, I'm using the 1-29-13 Toro nightly. Guess I should update ;) Lol.

Edit: according to the the changelogs its now cLock
 
tdm said:
CM10.1 beta3 is up before the official P930 build.

Changes:

Sync to latest code. Includes 4.2.2 update.
Click to expand...

File pulled. This seems to have the same issue with the display turning off that AOKP42 does.

That is a big clue. I'll look into this .. I expect the solution for both will be simple. Expect a new build within a couple hours.
 
tdm said:
File pulled. This seems to have the same issue with the display turning off that AOKP42 does.

That is a big clue. I'll look into this .. I expect the solution for both will be simple. Expect a new build within a couple hours.
Click to expand...

Did you ever get that ROM Manager app you talked about resurrected?
 
tdm said:
New build uploaded, md5 in op is updated (f31bba0e062b606a4aca529722c2f12f). Power button and key lights seem to work fine on i_vzw.

And the official P930 nightly is still not up yet... :p
Click to expand...

Dirty flash? Did clean flash for Beta 2
 
sosaudio1 said:
Dirty flash? Did clean flash for Beta 2
Click to expand...

Dirty flashing between beta builds of the same rom should generally be pretty safe but there are always little gotchas (usually when someone changes a database schema for the system to implement a new feature).

This is a bit more than just a nightly update so the risk of breakage is higher.

But give it a try. If it doesn't work, the solution is really easy... reboot to recovery, wipe, reboot back.
 
IMUcarmen said:
You got aokp42 working as well?
Click to expand...

Building now. We'll see later this morning.

I just started running this myself last night. One user is reporting an apparent memory leak (available memory drains over time) that doesn't happen on CM10.1. I'll need to investigate and fix that, but just be forewarned if you're a unicorn fan.

BTW, the AOKP42 source is currently not buildable. AOKP uses some of the CM repos directly, so it's likely the CM update to 4.2.2 caused the breakage. I'm sure they will have it fixed in the next day or two. In the meantime, I reverted back to yesterday's code.
 
tdm said:
Dirty flashing between beta builds of the same rom should generally be pretty safe but there are always little gotchas (usually when someone changes a database schema for the system to implement a new feature).

This is a bit more than just a nightly update so the risk of breakage is higher.

But give it a try. If it doesn't work, the solution is really easy... reboot to recovery, wipe, reboot back.
Click to expand...

oh yeah I am aware. Dirty flash is working installing now
rebooting......
watching for leds.......no leds on boot
android is updating.....
finishing boot....
LEDs work
 
Tdm. I'm loving your progress. But can I ask for a small favor? Some way to disable the key lights. Maybe a option in the next build or a flashable zip or something?
 
You must log in or register to reply here.
Back
Top Bottom