[ROM][Official][4.2.2] CyanogenMod 10.1 Nightlies for the Nexus 4 (mako)

Search This thread
By:
Advanced…
L

LS1_01

Senior Member
Mar 10, 2012
53
4
Anyone else noticed that the "disable unlock screen" icon on the power pulldown widget doesn't disable the lockscreen? However, using the unlock on the quick settings does? Also, when the phone is restarted the quick settings unlock has to be set to "lock" first then "unlock" for the screen to stay unlocked...otherwise if it booted with the unlock enabled on the quick settings it will still lock and ask for your pin/password/face etc. to unlock each time unless you lock it and toggle right back to unlock using the quick settings.

---------- Post added at 07:48 PM ---------- Previous post was at 07:46 PM ----------
wolfboy1984 said:
Yes, we get the idea.

Can we stop reporting now everyone? Maybe?
Click to expand...
Click to collapse

Btw, is this is the correct place to be reporting these issues on the nightlies or checking elsewhere first to see if it was reported and if not reporting it there on a bug tracker or jira or smth? Thanks!
 
thracemerin

thracemerin

Senior Member
Oct 19, 2011
5,458
5,764
Toronto
LS1_01 said:
Btw, is this is the correct place to be reporting these issues on the nightlies or checking elsewhere first to see if it was reported and if not reporting it there on a bug tracker or jira or smth? Thanks!
Click to expand...
Click to collapse

You can report issues with nightly builds in this thread, JIRA should only be used for 'M' releases or if a CM team member specifically tells you to report something to JIRA on a nightly.

All we're saying is, after 2 pages of people saying it happens to them it's pretty much assumed it happens for everyone, saying "me too" just fills the thread with nonsense.
 
  • Like
Reactions: nsg86 and bedtime_with_the_bear
muff99

muff99

Senior Member
Jan 6, 2011
396
155
continuous focus

Hi,
I got my Nexus 4 today upgrading from a Galaxy S, and I noticed that with the current nightly I have the following issue:
Starting the camera I dont have continuous focus, tap to focus works though.
When I activate HDR and tap to focus once, continuous focus starts to work afterwards. Now I can switch off HDR again and continous focus keeps working, until I close the camera.

I do not have the crackling-noisewhen-focus issue, though (googling the continous focus issue I found several postings that suggest a connection, which I do not see).

I'm on .33 radio, will test .48 next ...
 
  • Like
Reactions: jelle2503 and negroplasty
D

dcarpenter85

Senior Member
Apr 5, 2011
476
77
Zanesville, OH
Experiencing random MMS crashes when trying to send pictures. Doesn't always happen, and I can't really find definitive steps to reproduce it. I'll try a clean install and report back.
 
Zorachus

Zorachus

Senior Member
Dec 15, 2010
4,009
837
Lombard, IL.
Anyone have an inverted Messaging app ? I like the stock default Messaging app CM10.1 has, but not in white, looks better black.

Sent from my Nexus 4 using xda premium
 
EddyOS

EddyOS

Senior Member
Jan 2, 2010
15,279
4,035
London
Zorachus said:
Anyone have an inverted Messaging app ? I like the stock default Messaging app CM10.1 has, but not in white, looks better black.

Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse

I always find this strange on an LCD screen as using black is worse on battery than white. Fair enough on an AMOLED screen, though...
 
C

cdtan99

Member
Mar 14, 2010
27
1
I just noticed that my phone does not go into deep sleep when I'm on data and wifi is enabled but not connected. If I disable wifi or if wifi is connected, My N4 goes into deep sleep with no issues. Is anybody else experiencing this? I'm on the latest stock CM nightly.
 
Last edited:
You must log in or register to reply here.

Similar threads

franciscofranco
[KERNEL][GPL][N4] franco.Kernel - r217
Replies
58K
Views
11M
D
Draketech
molesarecoming
  • Locked
[ROM] [4.4.4] [OFFICIAL] ParanoidAndroid 4.4x/4.5
Replies
53K
Views
9M
El Daddy
El Daddy
AOKP_ROM
[ROM] AOKP :: [4.3.1] jb-mr2 :: Milestone 1 / [4.4.2] kitkat :: Nightlies :: mako
Replies
11K
Views
2M
C
cyprien T
DariosF
  • Locked
[ROM][GPL] [KK 4.4.4] ♦ PURITY ROM ♦ (Mako) 15/10
Replies
12K
Views
2M
Woody
Woody
faux123
[Kernel] (ver 041) Mako KK 4.4 (UV/OTG/CPU/GPU OC/Hybrid Linux 3.4+) [08-02-14]
Replies
17K
Views
3M
B
bubbleguuum

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 893
    C
    CyanogenMod
    CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.2.2 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.

    Code: 
    #include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/

    CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. Your changelog is whatever was merged into gerrit.

    Instructions:

    First time flashing CyanogenMod 10.1 your device, or coming from another ROM?
    1. Download the zip(s).
    2. Optional: adb backup
    3. Fastboot oem unlock > fastboot flash recovery recovery.img.
    4. Perform a NANDroid backup of your current ROM.
    5. Wipe data & cache partitions of your device (required when coming from stock!).
    6. Flash CyanogenMod.
    7. Optional: Install the Google Apps addon package.
    Issues?

    Experience issues? As these are nightlies, bug reports are not accepted. You are relying on yourself and your peers in this thread for support!

    Download Links:

    CyanogenMod:
    Nightly:
    Download: link​

    Google Apps addon:
    Use 4.2 gapps:
    Download: link​


    GENERAL COMMENT AND REQUEST:

    We ask all the regular contributors here to please answer the "xxx is broken" or "yyy force closes" statements without an attached logcat with something like "LOGCAT or it didn't happen"

    Feel free to be creative but DO NOT respond with wipe cache/clear data or any other attempted solution before the reporting user has taken the trouble to actually try to help solve the problem (e.g. by attaching a logcat, detailed steps to reproduce etc.).

    We need to force more discipline in how issues are reported which will help us all find and squash bugs that may exist.

    Just clearing data etc. may in fact cause us to never find the bug that caused the issue and just makes for lazy users.


    The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
    View
    54
    D
    DvTonder
    GENERAL COMMENT AND REQUEST:

    From now on, can we ask all the regular contributors here to please answer the "xxx is broken" or "yyy force closes" statements without an attached logcat with something like "LOGCAT or it didn't happen"

    Feel free to be creative but DO NOT respond with wipe cache/clear data or any other attempted solution before the reporting user has taken the trouble to actually try to help solve the problem (e.g. by attaching a logcat, detailed steps to reproduce etc.).

    We need to force more discipline in how issues are reported which will help us all find and squash bugs that may exist.

    Just clearing data etc may in fact cause us to never find the bug that caused the issue and makes for lazy users.
    View
    53
    D
    DvTonder
    All,

    Please remember that Nightlies are experimental builds and even though we have been lucky thus far that Nexus builds have been fairly stable, we can, and many times do (remember the GPS issue last week), break things in Nightlies.

    4.2.2 just got merged this morning and the builds, even for Nexus devices, are not 100% functional yet. Give it a day or two for the device maintainers to work out the kinks and stabilise things.

    Please STOP flashing bootloaders, radios, kernels and random 4.2.2 builds and wait patiently for another 24 to 48 hours for things to be sorted out. It won't kill you to wait but it might kill your device if you rush things.
    View
    48
    D
    DvTonder
    EvoXOhio said:
    I'll get flamed for saying this, but the problem with CM is that they've become another OEM skin. The reason it takes so long for Samsung, HTC, Motorola, etc. to update phones to a new version of Android is because of all the customizations they do. Their customizations conflict with AOSP so they have to re-integrate them. Well CM is now in the same boat. it is so highly customized that new versions of Android break their code base.

    If anyone remembers when ICS came out, that was the best example of this. It took the CM team so long to port their customizations to ICS, that Jelly Bean ended up being released before CM 9 (ICS) was officially released. They did a better job with Jelly Bean, mostly because the changes to Android weren't as big.

    I love CM, and it is always my ROM of choice. But they've strayed so far from their original vision of bringing AOSP to the masses. They are now just another custom OEM skin that retains the AOSP look and feel. I appreciate everything they do and love the customizations, but unfortunately it makes it harder for them to keep phones up to date.

    /end rant
    Click to expand...
    Click to collapse

    Unfortunately you don't know what you are talking about. CM is not, and never will be "an OEM skin".

    Our 'customizations' have very little to do with how long it takes to merge a new version. There are many, many other factors that contribute, including ensuring it works well on the many, many devices we support.

    Yes, its not always an easy process to bring our features over - especially when Google completely re-architects parts of the system (like lock screen in 4.2) but then if you want AOSP, why don't you just install AOSP?

    Insulting the CM team is not going to make the 4.2.2 merge go any faster, in fact, it may just delay things, why should even I bother spending my personal time adding a feature to CM (like cLock or Quick reply etc.) when this is the type of response it gets?
    View
    46
    D
    DvTonder
    Re: [ROM][Official][4.2.1] CyanogenMod 10.1 Nightlies for the Nexus 4 (mako)

    General comment:

    There are probably a few things broken in the current nightlies similar to the quiet hours issue from yesterday. It will take us a few days to check everything and fix the parts of the merge that did not quite come out right.

    If you notice any old cm10.1 functionality that now no longer works quite the way it should (like the quiet hours issue) please post it here and I will look out for it.

    Please don't ask us to fix things that were broken before. We need to get this build to pre-merge state first.

    The rest of the month is focused on stability and bug fix in anticipation of the next M release.
    View

New posts