352 replies to this topic

[PaulOBrien]

jusumgeezer, on 16 January 2013 - 10:43 PM, said:

Just moved from JellyBeer to this, great work. I was gonna post about issues with battery life on this rom, until I realised I still had 79% when I got home after a day of use including a long call over bluetooth & heavy web use & live widgets, so.. erm never mind
I did have a random shut down though, charged it over night after installing the rom & had a few texts in the morning when the phone was in my pocket. When I took it out the phone was completely dead? It was a clean install with a full wipe. I had just started work so was unable to make any logs or anything. Seems to be a one off  & it's been behaving itself since.

Random, not seen that! Remember to use a kernel with the wakelock fix - eg Franco - for best battery life!

P

[azrash]

hi there, i would like to try this rom and I am curious on how to use the option.txt file. it seems similar like a pre-installation script that a ROM used in my previous phone, but this one are just numbers instead of say

amazon appstore=yes

I would appreciate it if someone can point me to the right direction on how to use the option.txt file.

thanks!.

[PaulOBrien]

The option.txt is for information only i'm afraid!

P

[jusumgeezer]

PaulOBrien, on 16 January 2013 - 10:57 PM, said:

Random, not seen that! Remember to use a kernel with the wakelock fix - eg Franco - for best battery life!

P

Is that the default Kernel on this rom? The battery life has been amazing so far.

Sorry to be a complete noob, but I just had to do a factory reset due to my spotify downloading a load of albums for offline use, I only have the 8GB so it filled up quite quickly. I was late for work so just did a factory reset through the settings menu. However that didn't work & everything is still there, is this because I should have formatted through recovery instead? or is it just Google's backup/restore feature? I'm using TWRP I've a huge amount of space taken up by unknown items, I presume spotify cached songs somewhere.

Edited by jusumgeezer, 17 January 2013 - 11:27 AM.

[PaulOBrien]

No, the standard kernel is stock. Actually, that will have the wakelock fix too since it's nightly.

A wipe doesn't wipe the internal SD, you can do that by selecting the format option from the recovery menu.

P

[jmagee]

Bluetooth really isn't working for me. Calls aren't being put through voice or controls, at least MCR does the voice. It also disconnected after an hour. Anyone else seeing this?

[kisman]

I used this image once a short time, but I'm back to MCR. Feels better, smoother. But, sorry, no experience with Bluetooth...

[PaulOBrien]

Preparing the Friday update to the latest nightly now!

P

[PaulOBrien]

r2 is now online both in the kitchen and as a pre-bake, enjoy! No wipe needed of course.

P

Changelog

18th Jan

• Updated to 180113 nightly
  
• Updated all 3rd party components
  
• Added MoDaCo Forums app

[duderuud]

Updated my R1 first, gave me Gapps errors. Did a full wipe/del cache/dalvik cache but again:

Unfortunately, the process com.google.process.gapps has stopped


Got any idea why?

[PaulOBrien]

duderuud, on 18 January 2013 - 08:58 PM, said:

Updated my R1 first, gave me Gapps errors. Did a full wipe/del cache/dalvik cache but again:

Unfortunately, the process com.google.process.gapps has stopped


Got any idea why?

Clear data on Google Services Framework and reboot.

P

[jmagee]

Try clearing all date for Google apps. Gmail, G+ etc.

[duderuud]

Thanks, will try that!

[Jan-Jakob Fahrländer]

Is there any way to get rid of the Volume Warning when you are using headphones and want to turn the volume up a little more? Both here and in the other release?

[PaulOBrien]

Jan-Jakob Fahrländer, on 18 January 2013 - 10:09 PM, said:

Is there any way to get rid of the Volume Warning when you are using headphones and want to turn the volume up a little more? Both here and in the other release?

Not currently!

P

[duderuud]

Latest R2 isn't working. Fresh install crashes constantly (gapps errors).

Can't get past the install wizard. So not usable at the moment. Will try to restore an R5 image and update it to this version.

[PaulOBrien]

r3 is now in the kitchen, this should resolve all issues with r2. Unfortunately due to an oversight some of the custom MCR CM code wasn't merged correctly after updating the main repo to the latest nightly, this has now been resolved. Remember to be patient on first boot after a wipe while it runs dexopt.

As always, no wipe is required for this release.

Enjoy, and have a great weekend!

P

Changelog

19th Jan

• Updated to latest nightly (still tagged 180113)
  
• Fixed issues with dirty-flash enhancement code (apologies)

[80sLoveCHILD]

internet connected in new house
my nexus 4 is now unlocked and rooted. time for a new rom
cant wait to try this paul. thanks

Update
The joys of nexus. From stock to running a custom ROM in well under thirty mins. Great ROM Paul, no issues so far, although not been using it long. Thanks Paul, Cm, Google and Dev community

Edited by 80sLoveCHILD, 19 January 2013 - 03:13 PM.

[chakrata]

Hi Paul,
may I suggest the YYMMDD format for the file names, generated by the kitchen?
Presently it is DDMMYY and the chronological sorting by name gets a bit messy.
(of course there are other solutions to the issue)

[wollyka]

Updated from AOKP m1 release to R1 3 days ago. All went well except the contacts data were corrupted (kept getting process acore  errors). Wiping contacts data fixed the issue.