CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3 (Gingerbread), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I 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. Linked below is a package that has come from another Android project that restore the Google parts. 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. You can also view the Changelog for a full list of changes & features.
Instructions:
First time flashing CyanogenMod 7 to the Barnes & Noble Nook Color, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Upgrading from earlier version of CyanogenMod 7?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod (your Google Apps will be backed up & restored automatically).
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
Official post
CyanogenMod:
Latest version: update-cm-7.1.0-encore
Download: link
Mirror: link
MD5sum: 0e8c6b4a7689de6c2a3c0f0ca1e1f39f
Google Apps addon:
Version: gapps-gb-20110828
Mirror: link
Mirror: link
Version: Google Talk with video addon
Mirror: link
Mirror: link
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
AMAZING!
Installing now. Thanks!
Working great so far.
Ah, finally the wait is over.
Totally freaking awesome!
Next will be ice cream sandwich
Sent from my NookColor using xda premium
2 Quick Questions
1) If I hit cancel when I was going to install Google Apps, what's the method to bring up the process again other than flashing everything again?
2) Is there any way to get rid of the signal bars for calls? I don't remember it from the previous releases (or maybe I just never noticed it on my NC.)
Outstanding!
Now for a possibly stupid question. I upgraded to nightly 214 last night. Are there any significant differences between that and 7.1?
Rebel_lord said:
2 Quick Questions
1) If I hit cancel when I was going to install Google Apps, what's the method to bring up the process again other than flashing everything again?
2) Is there any way to get rid of the signal bars for calls? I don't remember it from the previous releases (or maybe I just never noticed it on my NC.)
Click to expand...
Click to collapse
1. Just flash gapps. Only gapps.
2. A reboot or 2 usually clears that up.
---------------------------------
Sent from my LG Optimus V using Tapatalk
If this post helped you don't forget to say thanks!
craigbru said:
Outstanding!
Now for a possibly stupid question. I upgraded to nightly 214 last night. Are there any significant differences between that and 7.1?
Click to expand...
Click to collapse
I think it's safe to call the stable 7.1 a nightly build 215.
votinh said:
I think it's safe to call the stable 7.1 a nightly build 215.
Click to expand...
Click to collapse
Thank you. That's helpful.
It still seems to have the deep sleep issue, hung on me after 2 hrs of standby with the wifi on. Battery drained to zero too.
I should add that I didnt delete the data partition on upgrading, and had the issue beforehand.
Holy crap. After going weeks and weeks without it happening, I just had a Sleep of Death occur!
Sleep of death is definitely still an active issue.
I'm using the program wakelock to see if it helps.
waylo said:
Sleep of death is definitely still an active issue.
I'm using the program wakelock to see if it helps.
Click to expand...
Click to collapse
Yeah, but it hadn't happened to me since July or something. I thought that maybe it was fixed.
I saw some notes also saying it still locks up when connecting VPN.
I posted on the standard CM7 thread as well, but yes, I also had an SOD this morning on 7.1.0. I've installed Wi-Fi Keep Alive for now from the market to see if that helps.
BitingChaos said:
Yeah, but it hadn't happened to me since July or something. I thought that maybe it was fixed.
I saw some notes also saying it still locks up when connecting VPN.
Click to expand...
Click to collapse
Anything you have/had been doing that you think was helping keep the SOD away? =)
Battery life seems pretty epic.watched over 2 hours of video and still on 80%.. I wish err could lower the screen brightness add low as miui allows seems to reduce battery strain further when watching video.
Sent from my Inspire 4G using xda premium
Goonish said:
Battery life seems pretty epic.watched over 2 hours of video and still on 80%.. I wish err could lower the screen brightness add low as miui allows seems to reduce battery strain further when watching video.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
I use quick settings to adjust many things including brightness. Most movie players (such as Mobo) also have gesture support to change brightness as the movie is playing.
---------------------------------
Sent from my LG Optimus V using Tapatalk
If this post helped you don't forget to say thanks!
Bummer... it seems it still crashes if you have too many apps installed to the SD card.
I wish more people experienced this, so maybe it might actually get fixed...
Oh well, looks like it's back to N136 for me...
Related
CyanogenMod is a free, community built distribution of Android 2.3.4 (Gingerbread) which greatly extends the capabilities of your phone.
This is a release candidate, but you should find it stable for everyday use.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
Visit the CHANGELOG for a full list of changes and features!
All source code is available at the CyanogenMod Github! If you'd like to to contribute to CyanogenMod, checkout our Gerrit instance.
INSTRUCTIONS:
- First time flashing CM 7 to your phone (or coming from another ROM)?
1. Unlock/root your device and install Clockwork Recovery 3 via ROM Manager
2. Do a Nandroid backup!
3. WIPE
4. Install the ROM
5. Optionally install the Google Addon
- Upgrading from an earlier CM?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
HOW TO REPORT BUGS OR PROBLEMS?
- Was it a hard reboot? Get me the file "/proc/last_kmsg".
- Was it a soft reboot or a "boot loop"? Run "adb logcat" and get me the full output.
- Pastebin links preferred
- Please use the issue tracker whenever possible!
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
The preferred method of installation is via ROM Manager, or you can head over to the CM Forums for manual downloads.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
Just want to thank the CyanogenMod team for this release and for all of their hard, quality work.
Thank you so much for this amazing release! Many the issues (mainly cosmetic) in 7.0.3 has been ironed out and nothing has regress yet so far!
Fantastic job as always guys, wonderful release. Thank you.
i still cant change the cpu governors, besides i am liking every thing else
Running smooth as usual. No problem so far. I just tested GPS for some times but the device fails to lock on. Is it fixed in this RC does anyone know. I will test again tomorrow...
I am having a recurring issue with USB tethering. Originally I thought it was a market app I downloaded that was giving me a problem but I attempted to USB tether through WIFI settings and each time my phone locks up for about 5 seconds and then reboots.
WIFI hotspot tether appears to be working fine. Anyone else experiencing this?
As always thank you team Cyanogen for your outstanding work with the MTS, without it we would be stuck with slow, bloated and limited phones. My wife won't even go back to a stock HTC rom after using CM7, once again AWESOME JOB and Thanks!!
Troy.
Is this release built on a new kernel? Or does it use the same kernel as 7.0.3 Stable?
Yes finally the RC is out I'm going to try this out now, if the battery drain still exist I will stick to cm6.
Sent from my T-Mobile myTouch 3G Slide using XDA Premium App
katbastard said:
i still cant change the cpu governors, besides i am liking every thing else
Click to expand...
Click to collapse
Same here, can't change the governor, but otherwise it is running nicely. Heavy battery drain, I think, though.
The usb tethering lock up/reboot is the same for me. Does anyone have it working?
jj110888 said:
The usb tethering lock up/reboot is the same for me. Does anyone have it working?
Click to expand...
Click to collapse
There is a fix for this in the nightly thread. Move any app used by the system (like themes for the Theme Chooser) to internal storage.
As Uber said, I posted that a while ago and it worked everytime for me, search.
Did anyone elses phone app disappear?
Sent from my T-Mobile myTouch 3G Slide using XDA App
Nope, not mine
snag...
I had to restore my Froyo backup. The 7.1RC1 ran well but I discovered the Bluetooth was way flakey. I absolutely must have reliable Bluetooth so that is a no-go for me. Otherwise, it is a beautiful ROM.
Fuzi0719 said:
Same here, can't change the governor, but otherwise it is running nicely. Heavy battery drain, I think, though.
Click to expand...
Click to collapse
Same for me as well.
joshuasvt said:
Same for me as well.
Click to expand...
Click to collapse
I could change the governor using SetCPU, but the flakey Bluetooth issue was a killer for me, I went back to using my rooted "official" Froyo release that I backed up.
Yikes! Mine is eating battery worse than I've ever seen it! Down to 80% after just over 1.5 hours (granted the first 20 minutes was making a backup and flashing RC1) but this is nuts. I may have to go back to what I was using before, battery still wasn't nearly as good as RC2 or 3 for 7.0 but it was much better than this. I'm down to 78% since I started writing this! GPS seems to take atleast as long if not longer to lock for me. Anyone have any great fixes for that? Oh geez, 77%...guess I'm heading back to 7.0
Team EOSJB 4.1.1 TF201NIGHTLIES
Continuing on from the success of the EOS ICS roms, we present to you EOS3, based on JELLYBEAN!
It is the goal of Team EOS to develop and maintain the highest performing and most stable AOSP based rom for an array of platforms. For the latest news on Team EOS releases make sure you follow @teameos on twitter and on IRC on Freenode in #teameos.
--
NOTE: Team EOS, it’s members, friends, dogs, cats, and associates are in no way responsible for any loss of data or device functionality. Use this at your own risk!
--
A quick note on Nightlies: NIGHTLIES ARE DEVELOPMENT BUILDS. They are automatically generated every now and then, and represent the compilation of the latest commits to the code repository. While every effort is made ensure that the commits that are accepted are stable and do not have a negative impact to the overall performance and function of the builds it is not possible to test every aspect of a commits impact to the overall repo prior to it’s inclusion in a given build. As a result it is entirely possible that instabilities may be introduced as a result of a given days commits. That is the nature of the nightly system, and the risk that is taken using the latest code changes to the project.
EOS is an AOSP based rom. It is developed and maintained by Team EOS and is the culmination of our own in house development efforts.
Team EOS Nightly builds: http://goo-inside.me/devs/teameos/roms/eos3/nightlies/tf201/
G-Apps Package
Because this is an AOSP based rom Google Apps are not included in the base rom. To install Google Apps please flash the following package after installing the base rom:
Temporary Gapps package gapps
--
Features:
Because these are nightly builds the included features are constantly evolving, we do not provide a change log manually. Instead please see the changes on jenkins for your build.
For the most up to date and comprehensive listing of the changes included in this rom please visit http://review.teameos.org
Kernel:
Kernel Note: This rom is currently using the stock kernel, so you can find the sources from aosp.
--
Installation Notes:
These builds are designed to be installed from your favorite recovery.
Perform a full wipe (read Factory Reset) prior to installing this over ANY ICS or JB based rom.
BUGS!
If you find strange or otherwise unexplained errors please report them here: https://bugs.teameos.org/ Please include logcats and as thorough a description of the issue and what lead up to the issue as possible. With out this we will be unable to track down these errors.
Want to contribute to the Eos rom? Well you can!
Just follow http://teameos.org/?page_id=6 to checkout our source code, and information on how to submit changes for review.
---
Enabling voice search in google now
Go into Settings
Go to "Language & input"
Scroll down to "Speech" and click on "Voice Search"
Click on "Download offline speech recognition"
Swipe Across to the "ALL" tab if needed
Download your speech pack for your language
Here is what I am aware of that has still to be fixed. I'll add to it once I've went through the bugtracker.
GPS / GPS Dongle
Face Unlock
Audio is a bit wonky
Significant changes in the last build:
Full dock support including keyboard layout selector.
Google Search no longer crashes.
Screen now turns off when the lid is closed on the dock.
Smart covers now switch off the screen.
Location is reported correctly via wifi.
Screen no longer rotates when docked.
Credits:
The rest of Team EOS.
AndroidRoot esp. RaYmAn and Bumble-Bee for helping with the device tree in particular with sound. (Also for all the other great work AndroidRoot have done with this device).
aremcee (Ricardo Cerqueira) of Cyanogenmod for fixing the OMX issues. (Camera/YouTube)
Everyone else who provided feedback.
Seriously...I love developers so much that I donate a ton of cash, but every ROM thread really needs to include working vs. not-working sections right in the first post.
Based on the post as it is right now, I have no idea if stable vs not, no idea if fully functional vs not...really, nothing but a shot in the dark, it seems.
Sent from my Transformer Prime TF201
rorytmeadows said:
Seriously...I love developers so much that I donate a ton of cash, but every ROM thread really needs to include working vs. not-working sections right in the first post.
Based on the post as it is right now, I have no idea if stable vs not, no idea if fully functional vs not...really, nothing but a shot in the dark, it seems.
Sent from my Transformer Prime TF201
Click to expand...
Click to collapse
Well, it does explicitly say NIGHTLIES... which really aren't guaranteed to be stable... but yes, it does not state what works and what doesn't...
I guess I know what I'll be doing at work tomorrow. ;-)
Thanks!
Jelly Beanz! I just flashed the Preview.
lortay78 said:
I guess I know what I'll be doing at work tomorrow. ;-)
Thanks!
Click to expand...
Click to collapse
Keep flashing, flashing hahaha.
very little if anything wrong with this. in fact i'd say there are less bugs in this build than cm10 as of now. no keyboard popup issues or anything like that.
only bug i've seen thus far is that some apps seem to be missing from the market. Also google now force closes for me even after following the instructions above
also, there are some of the specialized team eos settings but of course they arent all there yet.
overall awesome awesome rom and the best JB rom for the prime thus far. definitely can be used as the daily driver.
I keep getting stuck at the Eee Pad screen.
This is my second try.
I did a full wipe, flashed ROM and GApps from OP, and I'm just stuck st the Eee Pad screen.
It's been sitting there for like 10 minutes. Any ideas?
I'm coming from Virtuous Prime 9.4.2.28 v1
NickSaul said:
I keep getting stuck at the Eee Pad screen.
This is my second try.
I did a full wipe, flashed ROM and GApps from OP, and I'm just stuck st the Eee Pad screen.
It's been sitting there for like 10 minutes. Any ideas?
I'm coming from Virtuous Prime 9.4.2.28 v1
Click to expand...
Click to collapse
Some possibilities:
1) Bad download(s) (check md5 sums)
2) Old recovery (What version of TWRP or CWM are you running? I cannot speak for CWM, but TWRP should be 2.1.x or 2.2.)
3) Non-full wipe: Full wipe is Factory Reset (in recovery) and wipe cache and wipe Dalvik, right?
4) Lastly, even though I downloaded JB Gapps properly, I pretty near flashed the old ICS version out of habit. You didn't do that, right?
tedr108 said:
Some possibilities:
1) Bad download(s) (check md5 sums)
2) Old recovery (What version of TWRP or CWM are you running? I cannot speak for CWM, but TWRP should be 2.1.x or 2.2.)
3) Non-full wipe: Full wipe is Factory Reset (in recovery) and wipe cache and wipe Dalvik, right?
4) Lastly, even though I downloaded JB Gapps properly, I pretty near flashed the old ICS version out of habit. You didn't do that, right?
Click to expand...
Click to collapse
SUCCESS!
I reinstalled Virtuous Prime ROM, updated my CWM Recovery to the latest version, tried again, and it worked!
Thank you.
Looks snappy ... but I don't see camera app ... is it not working ..
Sent from my Transformer Prime TF201 using xda premium
Pretty damn cool, but it seems like youtube HD videos are not working? Normal vids work fine...
In CM10 youtube HD is working, but my sdcard isn't (and there are some other issues i
n that one).
And wrt camera, not working indeed... Also tried installing LGCamera but I only get a black viewer when opening it (ie, not the image from the camera which you usually get). Then again, don't use it that often anyway...
HD video/youtube would be sweet though.
Everything was fine, then I tried to turn on Google Now, after that I just keep getting "Unfortunately, Google Search has stopped".
dagrim1 said:
Pretty damn cool, but it seems like youtube HD videos are not working? Normal vids work fine...
In CM10 youtube HD is working, but my sdcard isn't (and there are some other issues i
n that one).
And wrt camera, not working indeed... Also tried installing LGCamera but I only get a black viewer when opening it (ie, not the image from the camera which you usually get). Then again, don't use it that often anyway...
HD video/youtube would be sweet though.
Click to expand...
Click to collapse
We are working on the HW Video decoding issue and that will fix the Camera as well.
NickSaul said:
Everything was fine, then I tried to turn on Google Now, after that I just keep getting "Unfortunately, Google Search has stopped".
Click to expand...
Click to collapse
If you clear data for Google Search and then go through the wizard again selection 'No, maybe later' at the end the search works but minus Google Cards. We will have this fixed in due course.
Netflix no video only sound ... so just gotta wait for hw decoding issue to be solved ... I must say ...this Rom is awesome .. @roach hats off sir and or whole team ...was using or Rom in my previous transformer
Sent from my Transformer Prime TF201 using xda premium
Roach2010 said:
We are working on the HW Video decoding issue and that will fix the Camera as well.
If you clear data for Google Search and then go through the wizard again selection 'No, maybe later' at the end the search works but minus Google Cards. We will have this fixed in due course.
Click to expand...
Click to collapse
Awesome, thanks! Can't wait to see what this turns out to be... it's a great first release for sure!
Roach2010 said:
If you clear data for Google Search and then go through the wizard again selection 'No, maybe later' at the end the search works but minus Google Cards. We will have this fixed in due course.
Click to expand...
Click to collapse
Thanks, that worked! This is really a nice ROM, thank you.
Another bug popping up:
Often in the app drawer the names/labels of the icons are missing in the first or first 2 pages... Then a bit later (after exiting and entering appdrawer a few times) they are back again. Nothing big, just mentioning it
Also, lockscreen is not showing for me atm... I only see the background image when waking up the tablet. Can unlock fine using the gesture, but don't see the 'unlock UI'.
Also browsers are acting up (ics+, quick ics, opera) but guess that's just general JellyBean issues/compatability
Does MicroSD work on this build?
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), 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 our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Download Links
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=dlx&type=nightly
Google apps addon:
Download: http://wiki.cyanogenmod.org/w/Google_Apps
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] CyanogenMod 12.1 Nightlies for the Droid DNA (dlx), ROM for the HTC Droid DNA
Contributors
invisiblek
Source Code: http://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
Version Information
Status: Nightly
Created 2015-04-20
Last Updated 2015-04-19
Thankyouuuuuu!
Unless I am losing my mind it seems like between CM 12.0 and 12.1 they have removed the option to hide the contents of app notifications on the lock screen. For instance, if you go to Settings -> Device -> Notification Manager -> App notifications -> select an app (e.g. Messaging), I could have sworn there was a setting there to hide the contents of the notification on the lock screen. I found this very useful as I really liked knowing when I had an SMS/MMS message come in, but I also didn't want someone who picked up my phone to see the first bit of the message. Previously, I could set it so that it would show "Contents hidden" instead of the message.
I have looked rather extensively through the settings and can't seem to find how to do this in 12.1. Has anyone else noticed this? Does anyone have a solution or know why they removed that feature? TIA
EDIT: Realized what the problem was. I did not have a secure lock screen (e.g. PIN, pattern) set up, so that setting is not available. As soon as I added a PIN, the ability to hide the contents of the notification became available again. In hindsight, I was stupid and should have realized that!
No audio on Call
I'm running 4-21 nightly and I don't get any audio when on a call. If I put it on speaker then I can hear it fine but nothing while normal.
EDIT: Updated to 4-23 and now it works fine.
Anyone experiencing really fast battery drain? My DLX on the latest nightly is draining at a rate of 20% in an hour with very minimal use (4 or 5 SMS, couple web pages). Not seeing any unusual activity in the Battery Stats and no Wakelocks.
My battery has been much improved from 12.0. Only issue is that SMS sending is sporatic needing a reboot, but I am not sure if its my gapps.
Not picking up 12.1 updates
After going to 12.1 nightly update, nightly updates are not showing up even I refreshed manually. If I manually downloaded the nightly update and put in it the .../cmupdater folder then it shows the update however no new updates showing up. Is this feature no longer available in 12.1? Anyone can see updates in 12.1?
Thanks.
@datoe: I won't be able to verify that until the next nightly comes out (hopefully tomorrow). I'm already on 4/26, so there are no new nightlies for the updater to report at this time. UPDATE: Last night I checked for an update using the Settings menu, but it did not find anything newer than the 4/26 nightly. I then checked the CM downloads page and saw that 4/28 nightly was available. So I agree with you, @datoe, that the updater is not picking up the 12.1 nightlies.
I have not been able to get Google Play Music to stream music over Bluetooth at all since clean-flashing to 12.1. I always get playback errors from GPM, or it'll play over the phone's speaker even though it says it's connected to BT for audio. I have a big road trip coming up this weekend, so I think I am going to flash back to 12.0 until they get that solved. I am not trying to complain, but rather make others aware in case BT audio streaming is a big deal for them. I have seen in other threads for 12.1 CM that they are experiencing the same issues with GPM and with CM's music player (which I always remove via a custom ZIP). UPDATE: I have flashed to the 4/28 nightly and at least now I get some songs to play. Out of the 5 I tried on my way to work, only 2 actually played, with the other 3 getting the music playback error messages. But at least that is an improvement from the previous 12.1 nightlies!
Thanks for supporting this... Works fine for me
Sent from my HTC6435LVW using XDA Free mobile app
Loving this ROM . Really no major issues so far...but For some reason Beautiful Widgets will not work/connect.. darn >cellular network not available? I am on Verizon any ideas? < fixed > Beautiful Widgets started working Now I can not get Google voice to work blinks when you talk but "can't load search results"
HELP? how do I fix recovery? when I boot in to recovery twrp shows but only "blinks" but does not load.. If I do a "factory reset" it goes into the stock recovery and installs the rom again.. I just don't know what to do
TweakedSystems said:
Loving this ROM . Really no major issues so far...but For some reason Beautiful Widgets will not work/connect.. darn >cellular network not available? I am on Verizon any ideas?
Click to expand...
Click to collapse
Wait for update for Beautiful Widgets. Got same issue with Power Toggles, until last update.
Thanks so much for the CM12.1 rom!
I flashed it today and everything is working except for some cellular issues. The phone shows me as on the network (3-4 bars and Verizon Wireless listed). I can receive text messages and can use mobile data, but I cannot make calls or send texts. If I try to make a call I get "Cellular network not available". Under "Sim Status" in the status menu, the SIM is listed as "Out of service".
Any help fixing this issue would be much appreciated!
Hello Developers,
When will this rom be going into official status? I have been checking CM ever since I had used CM 9, and the only stable CM out there for the DNA is CM10.
Hi, Everytime I try to update my phone to the newest update it reboots in recovery and it says the Zip file is corrupt and doesn't install. Is there a fix for that? Thanks!
Hey guys. Just got a DNA and since I love AOSP ROMS and also CM I want to install it on my phone. Also since the only way to start the process is using Sunshine and I have to pay $25 for it, I want to know how is battery life and also how are things with CM12.1 before I get to pay for the unlocking.
If you can send screenies with your SOT and/or time since unplugged until you get to 1% or 2%, or how long does it last with a normal/heavy usage. Also , if any of you know any other method to unlock the bootloader or install any custom ROM besides using Sunshine please let me know, it will be very much welcomed.
Im on 4.4.2 sense 5.5 from VzW.
Does anyone has the problem with sim? After updating to 6/14 nightly my phone lose carrier signal. In order to solve this problem I've fully wiped/clean installed latest (6/17) build and now phone randomly "lose" sim. There is a carrier signal and the next moment there is No sim sign. After rebooting it's ok for some time and then it lose sim again. Sometimes it shows a carrier signal but there is no one. And there is a "Emergency calls only" sign in a tray.
I have the latest hboot and radio. Have no any problems since first 12.1 nightly.
I just updated to the 6/21 nightly from the 6/14, and it will no longer connect to cellular service. No sim card errors, just says 'no service'. I tried restoring, no dice. Factory reset and re-install, still no luck. After one of the re-installs, i noticed that the 6/22 build was available. I wiped and installed that, and it connected for a short period right after boot, then cut out within about a minute.
Hopefully there is something I missed. I need this phone to last until August to get a new one.
Never mind. Apparently I managed to fry the sim card. New one in and everything seems to be working again on the 6/14 build. Will try updating again, but I think it was just too hot after running through a titanium backup, then ROM backup and upgrade.
Hey all. I just got this phone Friday after buying it on eBay and I paid Sunshine to achieve an unlocked boot loader and s-off. I've been using the latest CM Nightlies and I'm loving it. The only thing I wish for is to have xposed framework working on this rom. Has anybody able to do this yet?
Works great except for slide keyboard
I do have gesture typing enabled, but when I drag my finger on the keyboard, nothing happens, so I don't have gesture typing even when enabled. I would love for this to get fixed, thanksn
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* 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 our Gerrit Code Review.
Download Links
CyanogenMod:
https://download.cyanogenmod.org/?device=himaul
Google apps:
opengapps.org
Note: You need to flash the package right after you install the ROM. If you boot up and then go back and flash it, your phone won't boot.
XDA:DevDB Information
CyanogenMod 13, ROM for the HTC One (M9)
Contributors
varun.chitre15
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2015-12-07
Last Updated 2015-12-07
Thanks for bringing that to us ! ...
i guess i figured out 2 bugs ...
1) when i make a call it goes but crashes phone app ... ( Unfortunately, Phone has stopped) and it keeps repeating until i reboot or the other caller hangs up ..
2) USB OTG read as corrupted
is it only me or anyone else facing these ??
really its smooth and nothing going wrong except for that calling bug which keeps it out of a daily driver
I too have the dialer crashing whenever I attempt to make a call. Also, that weird bug where the clock will actually start to fall behind the actual time is present for me. I know @rc420head managed to fix that in the unofficial builds.
Other than those two bugs, which are pretty big for me, it's a solid build. Smooth and fast. Good start.
So the dialer crashes for outgoing calls, but do incoming calls work fine?
Sent from my HTC One M9 using Tapatalk
Sprint M9 too, please.
blackroseMD1 said:
I too have the dialer crashing whenever I attempt to make a call. Also, that weird bug where the clock will actually start to fall behind the actual time is present for me. I know @rc420head managed to fix that in the unofficial builds.
Other than those two bugs, which are pretty big for me, it's a solid build. Smooth and fast. Good start.
Click to expand...
Click to collapse
I seen the real fix for clock on Gerrit so should be in soon
Sent from my LG-H811 using Xparent Red Tapatalk 2
ShotSkydiver said:
So the dialer crashes for outgoing calls, but do incoming calls work fine?
Click to expand...
Click to collapse
Yes, incoming calls are okay.
---------- Post added at 10:29 AM ---------- Previous post was at 10:26 AM ----------
blackroseMD1 said:
Also, that weird bug where the clock will actually start to fall behind the actual time is present for me.
Click to expand...
Click to collapse
Yeah, it looks like whenever the phone goes to sleep, the clock goes to sleep too, which is particularly funny when I need the alarm to wake me up, but it can't 'cause it's asleep.
The problems with the clock have I too. The Alarm comes when I wake up my Phone.
Have you also problems with the sd card? No Apps are find her.
d0nk said:
Have you also problems with the sd card? No Apps are find her.
Click to expand...
Click to collapse
To the best of my knowledge, Android 6.0 offers two options for the external SD card: use it as a portable storage or internal storage. It has to be formatted in a specific way for either option. If you choose portable storage, applications will not be able to use it. Formatting it as internal storage doesn't seem to have been implemented in CM 13 yet.
d0nk said:
The problems with the clock have I too. The Alarm comes when I wake up my Phone.
Have you also problems with the sd card? No Apps are find her.
Click to expand...
Click to collapse
Yeah unfortunately it seems like the SD Card issue is a Marshmallow problem..
Which camera app do you use?
When I use "Do not disturb" I can't turn it off.
And same issues with clock also.
FWIW, I built the Verizon variant for myself, and it seems to be running with no problems.
How stable is this?
I'm having issues with:
- The clock on the lock screen is getting the new time but the homescreen clock will not refresh to reflect the new time
- Wifi is disconnecting often even with strong signal
On the plus side - Bluetooth works great!
sghurrie said:
I'm having issues with:
- The clock on the lock screen is getting the new time but the homescreen clock will not refresh to reflect the new time
- Wifi is disconnecting often even with strong signal
On the plus side - Bluetooth works great!
Click to expand...
Click to collapse
The clock thing is a known issue. Apparently it should be fixed in the next build.
blackroseMD1 said:
The clock thing is a known issue. Apparently it should be fixed in the next build.
Click to expand...
Click to collapse
Groovy thanks and thanks Devs. Great work
Looks also, the temperature still being a issue here, looks like is using all the core always for everything, because the battery drops down faster.
erisboxx said:
How stable is this?
Click to expand...
Click to collapse
CM and stable don't mix
rockNme2349 said:
FWIW, I built the Verizon variant for myself, and it seems to be running with no problems.
Click to expand...
Click to collapse
Do you have a link to flash
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANY PROBLEMS ON YOUR DEVICES CAUSED BY FLASHING THESE BUILDS. THE UPSTREAM CODE AND BUILDING IS MAINTAINED BY THE CYANOGENMOD TEAM, NOT ME. I AM NOT ASSOCIATED WITH THEIR TEAM, I AM JUST THE THREAD OWNER.
What is CyanogenMod ? It is an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android based firmwares of vendors of these cell phones.
Notes: CyanogenMod's stock kernel forces encryption. If you're unencrypted use a custom kernel to keep it.
Also this thread assumes you have kept up to date bootloader and radio !!!
The latest can be downloaded here Shamu Factory images around 1gb!. But i recommand you to flash through TWRP the Bootloader and Radio from here Radio and Bootloader around 60mb.
Installation is simple
1/Download rom + gapps (C-apps optional)
2/flash through recovery (Twrp or CM recovery)
3/Enjoy!!!
----->CyanogenMod Download<-----
----->Open GApps<-----
last--CM13--nightlylast--CM12.1--nightly
Changelog
CyanogenApps
Twrp
Sources: Kernel & Rom
XDA:DevDB Information
[ROM] CyanogenMod14.1 {Nightlies and Snapshots} & Cm13, ROM for the Nexus 6
Contributors
Dead-neM
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Up to date firmware (Fastboot+Radio)
Version Information
Status: Nightly
Current Stable Version: Everymonth
Current Beta Version: Everyday
Created 2016-04-22
Last Updated 2016-11-21
Reserved
Q&A
hum yes post your problem here after some research and you'll be helped
...
Reserved
Do not declare a bug here in the idea that they'll be fixed. Here we discuss, share everything related to our CM N6
so this is where we post from now on?
wmfreak said:
so this is where we post from now on?
Click to expand...
Click to collapse
Yes
Sent from my Nexus 6 using Tapatalk
Yay! Best ROM IMHO.
Can i run this in F2FS partitions Lety me know Thank's in advance!!!
Sent from my shamu using XDA Labs
caballon said:
Can i run this in F2FS partitions Lety me know Thank's in advance!!!
Sent from my shamu using XDA Labs
Click to expand...
Click to collapse
Sure, CM13 has been compatible since at least the beginning of this year
Hi, Thank you all making CM work and supporting this device. I particularly love this phone since this is Motorola (well, sort of) with a AMOLED screen, but more importantly it's the CM's custom features that urged me chose this phone.
I have been using the 160402 nightly with no major problem, only having two live lock screen force closes after reboot. Yesterday I hoped to upgrade to a more recent nightly, but that turned out to fail. I got constant FC's on Phone app, although the LLS ones were gone.
I tried cleaning Phone app's data, disabling xposed, but no help. I don't want to wipe data or otherwise I have to TiBu and then manually set up a ton of things.
The new post OP gives me a hint maybe my radio is too old (MDM9625_104662.22.05.32R) so I'm now trying to flash the latest factory radio and flash the yesterday's nightly again. Also it may be true but not so obvious that my cell signal (Tmobile LTE) gets frequently dropped (no signal/emergency only). I didn't test long before TWRPing back to the old working nightly.
Just want to check out at now if there is any other thing I have missed? Or why am I getting constant Phone app FC?
Edit: I updated the radio to .34R but it didn't help. The Phone app crashes every time I launch it, without giving a report button and it even didn't give me a chance hit the OK button before it disappears. I managed to call somebody with the contacts app and I heard the dialing tone. I was able to hang up the call with the notification action button. Everything looks fine except for the "Dialer" app.
Has the Sprint LTE issue been fixed by CM yet? IIRC the issue is once the Nexus 6 (running CM13 of course) drops down to 3G, it will never go back to LTE.
@cyrildtm
Going to have to bite the bullet and clean flash then.
Lawlrus said:
@cyrildtm
Going to have to bite the bullet and clean flash then.
Click to expand...
Click to collapse
True. Maybe in the future.... Now rolling back to and sticking with the post-april-fool version with the one-time LLS FC. (hey I even survived the MOD one!)
Last time when I did a "clean flash" I TiBu-ed the system settings and all things messed up ending in another clean flash.... and TiBu again but this time with painful manual settings go-over.
Snap camera in this version yet?
cyrildtm said:
True. Maybe in the future.... Now rolling back to and sticking with the post-april-fool version with the one-time LLS FC. (hey I even survived the MOD one!)
Last time when I did a "clean flash" I TiBu-ed the system settings and all things messed up ending in another clean flash.... and TiBu again but this time with painful manual settings go-over.
Click to expand...
Click to collapse
Yeah, I mean I clean flash everything but I know everyone is different.
That's the nice thing about ROMs though, you don't HAVE to flash every nightly, I know I sure don't lol.
If they push a new commit I like then I update, but if everything is kosher, then the hell with it.
Yeah, is the sprint LTE issue fixed?
Sent from my Nexus 6 using XDA-Developers mobile app
cyrildtm said:
Hi, Thank you all making CM work and supporting this device. I particularly love this phone since this is Motorola (well, sort of) with a AMOLED screen, but more importantly it's the CM's custom features that urged me chose this phone.
I have been using the 160402 nightly with no major problem, only having two live lock screen force closes after reboot. Yesterday I hoped to upgrade to a more recent nightly, but that turned out to fail. I got constant FC's on Phone app, although the LLS ones were gone.
I tried cleaning Phone app's data, disabling xposed, but no help. I don't want to wipe data or otherwise I have to TiBu and then manually set up a ton of things.
The new post OP gives me a hint maybe my radio is too old (MDM9625_104662.22.05.32R) so I'm now trying to flash the latest factory radio and flash the yesterday's nightly again. Also it may be true but not so obvious that my cell signal (Tmobile LTE) gets frequently dropped (no signal/emergency only). I didn't test long before TWRPing back to the old working nightly.
Just want to check out at now if there is any other thing I have missed? Or why am I getting constant Phone app FC?
Edit: I updated the radio to .34R but it didn't help. The Phone app crashes every time I launch it, without giving a report button and it even didn't give me a chance hit the OK button before it disappears. I managed to call somebody with the contacts app and I heard the dialing tone. I was able to hang up the call with the notification action button. Everything looks fine except for the "Dialer" app.
Click to expand...
Click to collapse
Hi I'm not using the stock dialer app but the Google one from playstore and i don't have force close so that's not a radio problem but an app problem. In fact having radio up to date normally improve stability over network cell comprehension etc... That's not a big deal but it is better to have a Marshmallow fastboot + radio on a Cm13 build which is Marshmallow based
Cm13 nightly can be really messed up a day but not an other. i think you just catch the wrong one
cyrildtm said:
True. Maybe in the future.... Now rolling back to and sticking with the post-april-fool version with the one-time LLS FC. (hey I even survived the MOD one!)
Last time when I did a "clean flash" I TiBu-ed the system settings and all things messed up ending in another clean flash.... and TiBu again but this time with painful manual settings go-over.
Click to expand...
Click to collapse
Used titanium to restore data of system app have always been buggy for me on every phone tablet that i've possessed. TiBu is usefull for data app
Btw a clean flash doesn't mean to restore data of a previous rom lol
Lawlrus said:
That's the nice thing about ROMs though, you don't HAVE to flash every nightly, I know I sure don't lol.
If they push a new commit I like then I update, but if everything is kosher, then the hell with it.
Click to expand...
Click to collapse
I agree with you. Nightlies sometimes can be awesome but sometimes awful. I went to look at the github page for the dialer app and found they recently put quite a lot of commits so maybe one or two is breaking things but anyways those smart people will figure it out sooner or later. I will just wait and take another free software
I bumped up from a March nightly mainly because of a recent CVE patch (of course that went into the 0401 build mod). Other than that I don't really see any urgent reason for increasing the counters in my daily driver again.
Dead-neM said:
Hi I'm not using the stock dialer app but the Google one from playstore and i don't have force close so that's not a radio problem but an app problem. In fact having radio up to date normally improve stability over network cell comprehension etc... That's not a big deal but it is better to have a Marshmallow fastboot + radio on a Cm13 build which is Marshmallow based
Cm13 nightly can be really messed up a day but not an other. i think you just catch the wrong one
Click to expand...
Click to collapse
I'm now on MOB30D radio (34R shown in settings, didn't copy down the version number shown in bootloader, but it did increase after flashing) and I can always make a phone call even now with an older nightly. so I can confirm the radio is working. I also noticed after flashing and first boot, when CM is about to finish "optimizing apps" the system gets a hot reboot (restart from animation) - oh btw another long-time bug is i never get themed boot animation unless i make a hot reboot (by FCing or any other way). Anyone same here?
From what I can remember the Dialer app has been a failure to me for more than a week. They did make a NPE fix there but seemed no help. Maybe I should install the Google's dialer as you do. I can still remember the AOSP English keyboard endless crash :silly: when I was on CM12.1 with an older device
Dead-neM said:
Used titanium to restore data of system app have always been buggy for me on every phone tablet that i've possessed. TiBu is usefull for data app
Click to expand...
Click to collapse
One of the hard lessons I have learned.
Lawlrus said:
Yeah, I mean I clean flash everything but I know everyone is different.
Click to expand...
Click to collapse
Dead-neM said:
Btw a clean flash doesn't mean to restore data of a previous rom lol
Click to expand...
Click to collapse
Oh lol it never means that! A clean "flash" is no more than 90 seconds to me but a clean "install" means recovering a whole shelf of over a hundred apps from .... the play store .... no the auto re-install only works if i got the same android id
Custom Kernel
I've been using nightlies for quite a while now, since my Nexus One and then my Samsung GS3. I've been reading up on Kernels but there are just so many... and they all say the same thing "Best balance of battery life and performance."
Yes, I could just try all 10 or so out there, but would like to be a little more efficient with my time, so I ask: What do you guys think is a good starting point for trying Kernels? I'm looking for obviously a good balance, but I'm a little more towards the performance side... CM13 has been a little laggy for me, especially with Swapps and rendering backgrounds loaded by chainfire's 500 Firepaper app. And I'll be damned if a colleague's iPhone is faster or more responsive than my Nexus!!!! :laugh:
Franko? ElementalX?
skim7x said:
I've been using nightlies for quite a while now, since my Nexus One and then my Samsung GS3. I've been reading up on Kernels but there are just so many... and they all say the same thing "Best balance of battery life and performance."
Yes, I could just try all 10 or so out there, but would like to be a little more efficient with my time, so I ask: What do you guys think is a good starting point for trying Kernels? I'm looking for obviously a good balance, but I'm a little more towards the performance side... CM13 has been a little laggy for me, especially with Swapps and rendering backgrounds loaded by chainfire's 500 Firepaper app. And I'll be damned if a colleague's iPhone is faster or more responsive than my Nexus!!!! :laugh:
Franko? ElementalX?
Click to expand...
Click to collapse
Try this one https://www.androidfilehost.com/?fid=24499762636000737
This is the latest singularity kernel
Also on post 2 I've post 2 kernel Blackbird and Singularity which in my opinion are the best
I don't like elementalx and Franco but I'm open mind and I'll add link if you find an other good kernel