[ROM][Official][4.2.2] CyanogenMod 10.1 Nightlies for the Nexus 4 (mako)
- Thread starter CyanogenMod
- Start date
-
- Tags
- cyanogenmod mako
It just randomly started to work lol
I haven't flashed a more recent one as this one was a snapshot I think? Nightlies make me worried incase of lots of bugs etc. Never used cm before
It just randomly started to work lol
I haven't flashed a more recent one as this one was a snapshot I think? Nightlies make me worried incase of lots of bugs etc. Never used cm before
fair enough, generally speaking there are very little bugs, usually none at all in the nightlies - especially on a nexus device.
Generally bugs are only introduced when CM are trying out new features, or straight after a change in android version occurs. Snapshots are not really any more stable than nighlties.
?!
I've gone back to M2!
State of wifi drops / data for me has been a joke in ALL recent get.cm builds...
Not quite sure what is causing them, it is strange as not everyone is suffering from problems (me included).
Confirmed. I too have this. And mine was a super fresh install. Reflashing again to check.
Update: no change.
Last edited:
+1 I'm having zero issues on M3 fresh install. Sounds to me like too many dirty flashes is probably to blame for some people. I've been told that after a while your data can get corrupted, but don't quote me on this.
Sent from my Nexus 4 using xda app-developers app
I'm not sure if it's a Rom problem or/and tmobile.
Ever since Lte rolled out I'm getting drop calls or no calls coming through.my girl friend has the same problem and her phone is stock.the only problem I am having is Wi-Fi problems and dialer problems and I'm sure that is Rom or radio related.
Sent from my Nexus 4 using xda app-developers app
Same issue here. Looking forward for tomorrow's nightly.
Maybe this was discussed before but how did you solve the grey-wifi-and-network-icons-bug while connected to wifi and display turned off?
I'm using latest franco.Kernel.
thanks guys!
For me its not just data drop its complete signal drops and goes into "emergency calls only" over and over and over.
Every time signal drops out: alarms, time zone, Bluetooth etc seem to be affected. And its more prevalent when I have WiFi on. (It seems)
Every time signal drops out: alarms, time zone, Bluetooth etc seem to be affected. And its more prevalent when I have WiFi on. (It seems)
Last edited:
by flashing a fix on the Q/A section.
Count 5 pages back from the last page there and you'll find it.
Sent from my Nexus 4 using xda premium
This is not related to modem. Do you know how many people are using the .33 radio in this thread??
Something changed in the ROM (or kernel) around early April that started cause signal and data drops. Prior to that running the ROM with .33 radio was flawless, minus the camera focus.
Last edited:
Going by their signature I'd say they're not and will await the 'but I'll lose LTE' response
Doesn't matter, officially the only supported modem is .48, if you are on an unsupported modem you need to report this in another thread.
This is the CM official thread, which is for 4.2.2. 4.2.2 includes the latest bootloader and modem.
I had this once. Happened due to bad reception (cave / underground, and didn't get better after on ground level).
Had to reboot to solve it (I tried using the bugreport feature at that time but it didn't work).
Reminded me of the i9100 RIL crashes :silly:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
893CyanogenMod 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?- Download the zip(s).
- Optional: adb backup
- Fastboot oem unlock > fastboot flash recovery recovery.img.
- Perform a NANDroid backup of your current ROM.
- Wipe data & cache partitions of your device (required when coming from stock!).
- Flash CyanogenMod.
- Optional: Install the Google Apps addon package.
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!54GENERAL 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.53All,
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.48
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?46Re: [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.
New posts
-
-
-
Features disabled on fastboot and bootloader. How do I enable them?- Latest: mayberandomparable
-
