[Nexus 4 Android Development] TPWarrior:
No problems here Zephik. Everything works perfectly after I dirty flashed Chroma 10/28 build. I already had Banks 10/20 6.0 from my previous flash, so no need to load. Everything booted up properly and is running smoothly. Thank you for your work! :good:

You'll also be happy to know that I also have the same ROM version & Gapps on my phone working. So it's not broken at all. Strange that we have the same phone, yet mine works. The difference is the flashing method and whatever changes you- and others- make to settings (changing kernels, clearing app data-or not- for instance, allowing permissions- or not).

Flashing ROMs isn't for everyone. I'm no expert at it either. Two things I've learned in my IT career and on XDA: 1) always follow directions and 2) with technology it's always best to start out with a solid base to build upon. Unfortunately so many people here want to take short cuts, then make changes (customizations for increased battery life or performance or even appearance, with Layers) without knowing exactly what will happen. It's all trial and error. There's nothing wrong with that- it's fun for us. :)

But you have to know how to get back to Square One when things don't work out. The one skill or "best practice" we all should have is the ability to start with a clean flash - a ROM & some minimal Gapps- to build upon. Also Marshmallow has both moved around some settings AND introduced some more capabilities (permissions, for instance) for users to change. It's highly recommended to learn about Marshmallow before going too far down the customization path. I linked two sources to learn more about Marshmallow in this post on the Frank thread: http://xdaforums.com/showpost.php?p=63402375

The best suggestion for anyone whose phone isn't working properly is to start with a completely clean flash (wipe everything except internal storage) and follow the OP's directions, including whatever recommendations are made with regard to Gapps, kernels, etc. In many threads, if you chose a different path than what is recommended you're unlikely to receive help.

Also when asking for help, please give at least a little detail, like ROM version/date, Gapps (WITH version or release date), any kernel different from the standard one, flashing method (dirty-cache + dalvik-, or also wiped data and/or system), what ROM version you from, and what Gapps package and date you flashed from.

Calling things broken (+gioxoid) or that you keep finding bugs (+krykeK/rodrigoswz) , 1) usually isn't the case and 2) does not make a developer particularly receptive to help. Fortunately Zephik (& Sykopompos, because I know many of you have also been Frank users) is gracious in the assistance he offers. :highfive: But, please lets not push it. The vast majority of the time- especially of late-, the errors are a result of user's actions, especially with people less experienced in flashing Roms, in general, or in understanding a new Android version (Marshmallow), in particular.

I'm going to guess that the answer to

most

of the problems in the next few weeks are going to be one of the following: clean flash, check/allow permissions, clear app cache/data (google play services, calendar, etc.), turn off wi-fi/bluetooth scanning or check Wake Lock Detector to determine what process is draining battery, then perform one of the aforementioned tasks. (Channelling my inner Carnac the Magnificent).:cool:

I'm still loving the performance and look of my Nexus 4 and am almost in disbelief that I may not need (or want) to replace it until the next Nexus model (after the 5x) comes out. Thanks to all you guys that help make that happen :D