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

Search This thread
By:
Advanced…
T

thebrainkafka

Senior Member
Apr 12, 2011
2,035
2,054
AW: [ROM][Official][4.2.2] CyanogenMod 10.1 Nightlies for the Nexus 4 (mako)

Just wondering what your appr. Battery drain in deepsleep is (GPRS).
THX.
Got 2% per hour.


Where can i find call settings?

How do i change language in keyboard while tipping? The spacebar only shows one language.

Thx
 
Last edited:
S

seamus5

Member
Dec 30, 2007
19
1
I've been having bluetooth hands free pairing problems since moving to 22-feb nightly. Anyone else have similar issues?

Sent from my Nexus 4 using xda app-developers app
 
Zaldi00

Zaldi00

Senior Member
Feb 15, 2012
222
114
Logroño
_conductor said:
Hi everyone, I'm experiencing that pesky wifi/data dropping while in sleep issue. It literally makes my phone unusable since I have no connection while in sleep and it takes 10-15 seconds for it to connect after I unlock the phone. Today I found this topic: http://xdaforums.com/showthread.php?t=2072930 which contains some modifications to /system/etc/wifi/WCNSS_qcom_cfg.ini. I'm curious if someone tried this and what are the developer opinions on these changes. Thanks in advance.
Click to expand...
Click to collapse

In this post you can find one zip Make for me,this zip solved issue for me and others but only works fine with notifications, for Example if You want conect your phone with your pc using airdroid, when the Screen Off, the conexion lost.
Sorry for my english.

Enviado desde mi Nexus 7 usando Tapatalk 2
 
C

_conductor

Member
Mar 1, 2011
31
6
Split
Zaldi00 said:
In this post you can find one zip Make for me,this zip solved issue for me and others but only works fine with notifications, for Example if You want conect your phone with your pc using airdroid, when the Screen Off, the conexion lost.
Sorry for my english.

Enviado desde mi Nexus 7 usando Tapatalk 2
Click to expand...
Click to collapse

Thanks for your reply. If I'm not mistaking you are talking about the same modifications done in the link I posted on my previous post.
 
SleemLDJ

SleemLDJ

Senior Member
Nov 11, 2011
2,460
533
London
Those with auto focus gone, are you using CM camera or Google's

I'm asking coz my autofocus works well with google's from 12122012 gaaps I'm using.

Sent from my Nexus 4 using xda premium
 
Fr33L4nc3r

Fr33L4nc3r

Senior Member
Jul 29, 2011
923
574
thebrainkafka said:
Anyone please
Click to expand...
Click to collapse

Didn't bother to check but seems OK

Open Phone App (Dialer) then Settings.

You have to set at least another language in Settings / Languages & Inputs
In Keyboards & Inputs methods, check the parameters for Android Keyboard (AOSP) / Input Languages, and uncheck System language, then choose the ones you want to see cycle with Space Bar when using the keyboard.
 
  • Like
Reactions: thebrainkafka
AshtonTS

AshtonTS

Senior Member
May 11, 2011
5,727
2,657
27
Woodstock, CT
jmejiaa said:
How's the service around you? That's typical behavior in areas with spotty service and would explain why you get it on every phone.

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

I have full bars at my house which is where I notice most of the unsent messages come from





Contivity said:
Are you sure it's not the message sending limit?
Settings -> security
then go all the way down

Sent from my Nexus 4
Click to expand...
Click to collapse

I have it set to 50, and I don't think I text that much, maybe I'll adjust the settings and see

Sent from my Nexus 4
 
lpasq

lpasq

Senior Member
Feb 14, 2006
1,393
215
anyone running current nightlies with cm kernel having hdmi out funkiness? post 4.2.1 i'm needing to toggle power button to get video to remote display via slimport adapter. upon connection remote display is touch active but dark...first phone power button toggle puts phone screen dark with monitor staying dark...second phone button toggle puts phone screen dark and remote monitor then receives and displays video signal. i'v been directed to this post as a clue: http://xdaforums.com/showpost.php?p=38295686&postcount=11623
 
L

lightningstalon

Senior Member
Dec 20, 2010
162
22
I just flashed the latest nightly - and looked through the changes but can't seem to find why the Reboot menu does not have the reboot to recovery or boot loader anymore. Does anyone know why?

Sent from my Nexus 4 using xda app-developers app
 
FatalityBoyZahy

FatalityBoyZahy

Senior Member
Jan 11, 2010
2,663
520
28
Camp Lejeune, North Carolina
www.YouTube.com
lightningstalon said:
I just flashed the latest nightly - and looked through the changes but can't seem to find why the Reboot menu does not have the reboot to recovery or boot loader anymore. Does anyone know why?

Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse

I believe you have to set that manually now.

Go to Settings -----> System -----> Power menu, and change it from there :)
 
Zainiak

Zainiak

Senior Member
Jul 1, 2012
846
221
24
lightningstalon said:
I just flashed the latest nightly - and looked through the changes but can't seem to find why the Reboot menu does not have the reboot to recovery or boot loader anymore. Does anyone know why?

Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse

developer options. please search next time. this has probably been asked 20 times :D
 
  • Like
Reactions: m3nster
T

thebrainkafka

Senior Member
Apr 12, 2011
2,035
2,054
AW: [ROM][Official][4.2.2] CyanogenMod 10.1 Nightlies for the Nexus 4 (mako)

Fr33L4nc3r said:
Didn't bother to check but seems OK

Open Phone App (Dialer) then Settings.

You have to set at least another language in Settings / Languages & Inputs
In Keyboards & Inputs methods, check the parameters for Android Keyboard (AOSP) / Input Languages, and uncheck System language, then choose the ones you want to see cycle with Space Bar when using the keyboard.
Click to expand...
Click to collapse

1000 thanks!
 
womanizerzz

womanizerzz

Senior Member
Oct 23, 2005
148
15
43
Screen Rotation ?
Well. Everything seem ok but what is the reason why calling screen and apollo music player cannot be in landscape?
 
D

danillll

Senior Member
Jan 27, 2012
73
12
CM clock widget seems to hold to and not release sns periodic wakelock! My phone didn't go to sleep for over 7 hours, once I delete the widget and reboot, the sns wake lock is gone!
I've been experimenting for a week now, better battery stats only shows the kernel lock but not what caused it(if you have a way to find out who exactly called it, please let me know). So I removed/added stuff and when I reenabled the clock/weather widget the wake lock was back.

My weather panel is set to custom settings (I keep GPS off).
FYI this started happening right after 4.2.2 merge and I'm now on the latest cm nightly.

Anybody noticed this behavior?
I really like this widget and would love to put it back.

Thanks!

Sent from my Nexus 4 using xda app-developers app
 
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