Related
Long time lurker first time poster... so don't beat me up too bad.
I'm looking at jumping into the CM7 world and am looking for some input.
I've used multiple versions of Skyraider up to 3.5 and loved them until they began getting a bit laggy (tried multiple kernels). I'm now using myn's warm 2.2 and ziggy's kernel with great success. Phone operates VERY smooth and all features work (not even sure why I want to try something new... guess I'm bored?).
Long story short, my phone is a daily driver and needs good battery life and all features to work (BT, camera, data, WiFi, etc...). I don;t mind flashing a few ROM's but it gets quite time consuing setting up the desktop screens, apps, calendars, etc...
I see that some builds break things, some fix things and it's hard to know which build does what. Many folks feel CM7 is the greatest thing since the Atari 2600; so here's my question:
What build are you using?
Does the phone scroll and transition smoothly?
All features working?
Getting FC's?
And yes... I have done quite a bit of reading on the CM7 nightly thread and others as well. People have a tendancy to post issues, not sucesses so it's difficult to find a good stable GB ROM.
Im on the latest release #37 I believe Using slayhers .37 kernal.
Love it. Altho, ever since I installed .37 kernal I've had my phone randomly reboot between 7:30 am - 9:00 am
I have yet to find out why... and it's only durring those hours too
I'm loving this ROM. Every time i go back to a sense, rom, i end up flashing cm6/7 back.
There are good things about cm6 and cm7... cm6 has a better camera app, probably more stable, but cm7 brings all the little things together, like multitouch keyboard + maps, it's snappy, the txting lag has been much improved. I think they are going to drop RC1 tonite..
I'm using build #33 with Chad's.37 kernel and everything's been running perfectly for the past few days. I don't think I've had a single FC or reboot. Battery life has also been very good, been using it pretty heavily all day and I'm down to 50%.
Just flashed 38, Have also used pretty much all the 20's 31 and 32. .37 Slayher Homebrewed #14
No reboots. I would say I could count the FCs on one hand easily and honestly don't blame the build I blame the app.
I used a number of roms before. Most of them from Rom manager. Now I am strictly a CM guy. Love these builds. I don't use Rom manager anymore either, just manually flash.
Personally, I'm someone who generally avoids experimental roms that still have incomplete functionality. Like you, my phone is a daily driver and I need to be able to rely on it. But CM7 was getting such rave reviews, I started to read up on it. It seemed that by the time I was hopping onto the bandwagon (nightly build 27 or so), everything was functional, there were just some things to be polished here and there.
It would be an understatement to say that I've been pleased.
To answer your questions specifically:
What build are you using? - Just flashed to #38, but have used a number of the builds
Does the phone scroll and transition smoothly? - Yes. For whatever its worth, I use LauncherPro Plus rather than ADW (which is what CM7 comes with)
All features working? - Yes. At least everything that I use.
Getting FC's? - Nothing that can't be traced back to another issue besides CM7
Don't get me wrong, I've had some tiny issues here and there, and some weird interactions, but nothing critical, and nothing that has stopped me from using this as my only rom.
I still keep old nandroids of the last two roms I used before CM7, but unless something drastic changes, they will just collect dust.
I've been using CM7 as a daily driver since like build 11, I haven't had any problems at all and its nice seeing new things added with each build
My dinc runs CM7 with the modified slayher .37 kernel. I runs super fast, but I haven't really noticed a significant increase in battery life. It used to crash, but since I set the wifi sleep policy to never, I have not had any problems.
build#38 ran awesome. no force closes and great battery life 20 hours or more. id say give it a try.
Just flashed RC1. Going great so far with only a few FC's that were solved with a simple reinstall.
Sent from my ADR6300 using XDA App
Did RC1, shaky, but amazing. Running 39 and it is better, has a lot of fixes that RC1 was plagued with. Like the rotary lock in the call screen.
I've been following CM7 development since Crackflashers. The rom has come a long way. Many people had problems with the first RC1 release because a mistake was made and those who did a clean wipe were locked out of the system. -Guess that should serve as a lesson to always nandroid first-
My advice is to continue flashing nightlies. As previously mentioned, the code will continue to improve and you will receive the latest fixes and features. Save yourself the trouble and clear cache and Dalvik before every flash. No need to wipe data.
Does anybody happen to know if there is a .37 version of the invisiblek kernel that includes the wifi sleep policy fix?
Its been working fine for me. The only problem I am having is that trackball wake doesn't function. I've made sure its selected int he CM settings, but I can press the trackball until kingdom come and it won't do anything. Looking at the dev. thread, I'm either the only one experiencing it, or the only one who cares.
SD card not mounting
flashed CM7 yesterday, really like how it runs. problem is my SD card won't load on the phone! I tried two different cards but no luck. recovery won't mount them either so I can't restore a nandroid backup. help!
also when I reboot most of the time, it'll show the htc incredible screen then go black and vibrate 5 times.
I'm running CM7 nightly #2 with the 2.6.37 incredikernel and it's great. Everything is very smooth and I can't seem to find anything that refuses to work. I had fc's when I first flashed the rom but fixing permissions in rom manager did the trick, since then I've had no problems.
I flashed CM7 as soon as they posted RC1 to ROM manager. I was skeptical at first and had a bunch of FC issues until I ran fix permissions (AFTER you install all apps). Haven't had issues since and my battery is lasting longer than ever, even without Juice Defender. Performs great. Can't wait until they get to adding more features like 6.1 had.
Sent from HTC Incredible [CyanogenMod 7 RC1]
Is it just me, or did Cyanogenmod lose some customization options from CM6.1 to CM7?
I dont see many editing options under CyanogenMod Settings and miss the ones from CM6.1
I'm on Build #41 and I can say a few things:
1) Battery life sucks on the Incredible no matter what. So just accept that. That being said, with Incredikernel .37 and CM7 Build 41, my battery life is "acceptable" compared to completely unacceptable with any other kernel or Sense Rom combination.
2) Random reboots. I don't know if it's just my phone, but even after trying three different .37 kernels, fixing permissions and re-flashing, my phone will go through "reboot anxiety attacks" where it reboots once every 10-12 minutes and then it will be fine for a whole day. It's not at specific times either.
3) Honeybread Theme - Get it. That's all.
4) Turn off wifi sleep completely. It seemed to curb some battery issues I was having.
Thanks All...
I went ahead and took the plunge and I don't regret it
I had some issues with RC1 and had to go to nightly #38. Everything has been solid with the exception of 2 random reboots (in the last 3 days). Not sure why but this isn't a show stopper.
I'll likley wait a while before flashing another nightly build.
So far so good. Batter life is ok... I know the Inc isn't the best for battery life but I got a bit better with Myn's ROM.
My quadrant numbers have improved (I know... relatively meaningless) and the UI is quite smooth.
Thanks to the development team... You've done a great job !!!
Hi,
I flashed CM7 (nightly 213) as I'm looking to try AOSP instead of sense for a bit. I'd heard great things about the performance and battery. Today however, I didn't use my DHD too much - a couple of short calls and some texts, the screen was on for 1hr15mins.
Before today I restored some apps with Titanium backup after flashing and used LordModUE's kernel (2way call recording, BFS), wouldn't have thought that should cause high drain though?
Display only used 8%, in sense it regularly used around 60%. I doubt it's using any less power, just other things are using more! Any tips would be greatly appreciated!
http://i.imgur.com/pade7.png
http://i.imgur.com/wKnwX.png
http://pastebin.com/a4YCq5fV <-- Currentwidget log
If you were simply looking to try out an AOSP ROM then you probably shouldn't have flashed a nightly build of CM7. That could be the cause of your problem, since from what I know, nightly builds are intended for the more experienced users.
I suggest trying out a more stable build, either from the CyanogenMod site or a custom one from here!
I flashed a nightly thinking it would be the most up to date, bugs gone, etc. After reading a bit more I've realised that's not the case! I've just backed up and will try CM7.1 RC1 with the stock kernel.
If battery life is good I'll try LordMod's kernel and add up slowly; I put too many things on at once so it could have been anything really!
I'll come back in 24 hours and see what's improved
My experience with the rc1 is bad and nightlies builds currently seem better.
Sent from my Desire HD using xda premium
I use CM7 RC1 and I have to say that my experience with this ROM is more then satisfying. Battery lasts something around 20 to 48 hours (on weeekends when I don't receive so much mails, 20 hours is something I get on normal working day when I receive around 50 mails during the day) and I have 5 mail accounts online all the time, everything set to push and Facebook, LinkedIn, googletalk and so on. But, I do not use any application to retreive my aplications from backup. I just install them manually one by one. And don't forget about calibrating battery after you install new ROM, it helped me a lot. Also, it is possible that you have some aplication which is draining battery and you are not aware of it.
Sent from my Desire HD using Tapatalk
Tamen said:
Hi,
Before today I restored some apps with Titanium backup after flashing
Click to expand...
Click to collapse
I assume that you didn't restore system data via Titanium, yeah? Coz that would be bad.
been using cyanogen mod for a bit with the alpha and beta 1. Just switched to the beta 2 and everything is very laggy. Anyone else having this problem with the new beta2
Same here. Jerl92is trying to make it smoother...
Sent from my HTC Vision using XDA
Thought maybe did something wrong. Switched to Andromadus Audacity Beta 2 for now and its running okay. Thanks for the reply
As suggested by a user @ cm9betathread,
I flashed the tiamat 314 kernel.
To be more specific: I did a full wipe, flashed the cm9beta2, flashed the kernel, flashed the gapps and then set up my phone via titanium.
The battery drain is a tad high, altough that may very well be because my battery's 1.5 yrs old by now. Coming from cm7 (tested andromadus (laggy) and jibwich (okay)), I'd say its about 30% more battery drain using similar settings in everyday circumstances (than cm7).
The performance is very good with the kernel, in drawer or home screen close to zero lags and a snappy performance. I do experience some lags when the system seems to be under heavy load (3g @ ics browser, eg.), which sometimes leads to a complete freeze, forcing me to take out the battery. I don't know if that is because of the kernel or cm9, but I haven't had the time nor the patience to test that.
Had amazing battery life when running the stock kitkat ROM and even when running early stock Lollipop builds. Now I'm struggling to get 5 hours out of the device with moderate usage - Streaming music, scrolling on social media apps and the occasional browse on the internet. Been having this issue for a while now but it's starting to get irritating when I have to carry a charger around with me like an Apple user, issue has been present on pretty much every ROM ranging from CM based and stock based which leads me to thinking it's a device problem.
Anyone know how I can check what's draining my battery as the battery stats doesn't really help, downloaded a wakelock detector but I can't make sense of it. Currently running ChupaChups 4.1 on a D855 model.
Cheers.
CurtisAndroid5 said:
Had amazing battery life when running the stock kitkat ROM and even when running early stock Lollipop builds. Now I'm struggling to get 5 hours out of the device with moderate usage - Streaming music, scrolling on social media apps and the occasional browse on the internet. Been having this issue for a while now but it's starting to get irritating when I have to carry a charger around with me like an Apple user, issue has been present on pretty much every ROM ranging from CM based and stock based which leads me to thinking it's a device problem.
Anyone know how I can check what's draining my battery as the battery stats doesn't really help, downloaded a wakelock detector but I can't make sense of it. Currently running ChupaChups 4.1 on a D855 model.
Cheers.
Click to expand...
Click to collapse
I get 6/6.:30h of sot with 16h on battery(with cc 4.1) in wakelock detector the apps that are on thee top off thelist keep your device awake the longest the x(number) represents how much time your phone has been wokken and the minutes/seconds is how long an app used the cpu. all non system apps on top off the list are popential drainers
We're all here because we want better roms than what our phones came with, upgraded roms etc. Idealy we'd want the most stable version with the last junk so it's the most responsive. As I upgraded more and more roms, I started to feel that the phone is showing it's age in processing power, and just like computers, you can't just install a newer stronger OS on older hardware, at some point you aren't gaining performance, you start to lose it because the hardware is struggling to keep up. I went from stock to 4.2 roms, then 4.4 roms, (pacman, mokee, CM, etc etc ). I eventually went back to 4.4 stock and it gave me the least trouble and quite snappy. Of course it had the OEM bloat from Verizon. Its been going strong for maybe a year, and now it too is starting to crash with a lot of bugs, probably from installing so many apps, but also I see a lot of built in apps taking up memory. So my main question is, if you still the Razr M and still using roms, what have you settled with ? What has been the most stable and fastest for you so far? For me so far it turned out to be the stock 4.4.2. So my options are to start over again with a fresh 4.4.2 or maybe a stripped 4.4.2, or one of the new 5.1 builds. I mainly use it for Navigation + music + calls, generally nav + music at the same time. Someone mentioned that CM12.1 couldn't handle that because of memory issues so that scared me off, but I love the CM12.1 on my galaxy tab pro. I do use the Bluetooth when im riding, and the camera from time to time, and the stock just had everything working.
If I can't find a stable build/rom, it might be time for me to move on to a newer quad core 2ghz + phone, browsing on the razer m is ok, but admittedly a little slow. The battery isn't what it used to, but it still gets through the day, and there are (albeit dodgy quality ) replacement batteries on amazon to hold out longer... The phone was basically free over 2 years ago, I've never been one to shell out $300 for a phone, but that oneplus one is mighty tempting to switch carriers for. ATT failed me on signal at this house so Verizon has been great, but i'd be willing to try tmobile if im forced to pick a new phone.
TLDR: Which rom has been the most stable for you ? ( rom name and build/version ).
vo_danh said:
So my main question is, if you still the Razr M and still using roms, what have you settled with ? What has been the most stable and fastest for you so far?.
Click to expand...
Click to collapse
Stock 4.1.2 (with uninstalled bloatware), as 4.4.2 has broken audio on (some?) Rev.B phones.
I have been on stock jelly bean, rooted stock kitkat (debloated with permissions removed for batt life), cm12.1 (our device is just too limited) and now cm11 snapshot 12 on kitkat boot loader. So far cm11 is my favorite.
Sent from my DROID RAZR M using XDA Free mobile app
For me stock kitkat debloated runs smoother, although is very sluggish sometimes: for example when I'm swapping messenger, whatsapp and running music player at the same time, it's almost impossible...
Ice tested cm when was 5.0,and was terrible. Pac man Kk, not as good as stock.
Sorry for this ugly link, I'm on my phone, but this post and the thread overall has a lot of good tips:
http://forum.xda-developers.com/showpost.php?p=53724034&postcount=17
In the last 2 and a half years I've been through:
Stock 4.1.2 (rooted after 1 day, debloated, Safestrap)
Eclipse Rom v1.2 (Safestrap)
CM10.1 (Unlocked BL)
CM10.2 (Unlocked BL)
CM11 (Unlocked BL, JB Kernel)
Stock 4.4.2 (rooted, debloated)
CM11 (Unlocked BL, KK Kernel)
CM12.1 (Unlocked BL, KK Kernel)
Best user experience for me? Sad to say but I had it with the Stock 4.1.2: overall smoother than all the rest. Then after some months my Razr M started a bootloop, so I unlocked the bootloader and tryed the CM ROM: the CM Power Widgets were an overkill at the time (mainly the 2G/3G toggle)...
After all the CM ROM that I've used, the second place goes to CM11 (with JB BL).
Right now I'm testing the latest CM12.1 builds, and they seems ok. I've installed onlyt the apps that are strictly necessary to me (gmail, maps, onenote, osmand, dropbox, wikipedia, Room Toolbox Pro, SuperSu, calendar, meteo, etc...). Everithing seems fine but I liked more the old KK style (lockscreen, quick settings). Everything is working, even if sometimes the data, Wifi and GPS signals are erratic. The performance are acceptable too.
So far a vote for CM11, and stock unlocked debloated. That's what i was heading towards too, stock debloat, and probably 4.1 it still has the best performance really. I mean the custom roms look great and all, but at the cost of performance which, after the initial wow factor, I think we would all prefer performance. Back when I had my HTC my favorite and most stable rom was jacko's most basic slim version ( he had like 1-5 tiers of peformance and features ). If I go back to stock and it lasts me another year or two i'll take it.
I'm trying out CM11 Snapshot 12 right now. I was already on 4.4.2 stock with unlocked kk bootloader so it made sense to try it first. Its already a lot smoother than what it was, freeing up half the memory. I noticed the dialer doesn't go all the way up sometimes, you have to push back and hit the keypad icon again. Otherwise very smooth so far. I'll report back after I get some use out of it and if I ever decide to go back to 4.1. I might need a new battery though, if I'm using it it doesn't last through a day.
*Update - I went from having basically no free memory left to about 50% free memory. I think my battery life increased dramatically with so much less running in the background. Maybe by 20-50%.
I took one phone call and updated a few apps, about mid day through the work day. was 12h by the end of the day and a few calls and some browsing w/o having to charge. Definitely gave new life to the phone. Very minor dialer bugs, sometimes the number pad doesn't come up correctly the first time.
Android 4.1 has various security issues that won't be fixed anymore, so that's not really an option.
But I don't think there are big differences in battery life anyway (see this).
After testing a lot of CM11, using Performance settings, changing memory settings, having a very poor battery performance, I've come back to the 4.4 backup with all the apps I had. The difference was incredible, now my phone feels snappier than an iPhone, and sincerely, i don't know why!! I think that doing a restore sometimes can help a lot.
Yeah the last time I did a fresh install of 4.4.2 stock it was great. After a while though with all my apps installed + the oem bloat the phone had very little memory left and became sluggish. My best options right now seem like going back to stock, either 4.1 or 4.4 and trying to do manual debloat.
I did a fresh install of CM11 again but still didn't fix it. I still had the occasional dialer error and wifi would only work upon boot, after disabling, it never reconnects to any wifi. Battery was still horrible. I went back to stock 4.4.2. RSlite would not work on any version on windows 8.1 64 bit. I had to do msfastbootv2 and was able to restore to stock 4.4.2 However upon booting, it wanted to update to 183.84.15 but failing. It would say there's an update, download it, reboot, and automatically boot into recovery. I would select reboot and it boots in, sometimes saying update complete but it hasnt' actually updated anything. I eventually gave up and started over, this time using stock recovery, not logging into my google account so it doesn't start downloading all my apps, no supersu, no gapps, and it successfully updated to 183.81.15. At that point using mfastbootv2 I installed twrp 2.8.5, rebooted into recovery, installed gapps and supersu. Then used titan to debloat using http://forum.xda-developers.com/droid-razr-m/general/complete-debloat-list-droid-razr-m-t3045731 , removed most of the things on that list, particularly anything I didn't use that I saw running. I also installed Greenify. After about a day I started noticing the google play services issue using a majority of my battery. I downloaded App Ops to disable google play services wake permissions. I am amazed at what happened. I feel like I have the original batteries back. I received 2-3 short calls today, and 2 browsing sessions, installed some apps (facebook lite), and I still have a lot of battery left, normally it would be over half gone. Going home after that much use and still having over 70% of battery left is nothing short of amazing and I no longer feel like getting a new phone. I was very close to trying the Droid Turbo.
TLDR: Got original usage/battery back with stock 4.4.2 + debloat (backup & Uninstall with titanium ) + App ops to fix google services wake battery drain + Greenify. I don't know how much Greenify is doing, I attribute most of my gains from debloat + fixing the google services issue. Before App Ops you'd see a giant bar at the top of Google Services instead of screen.
Still odd you having WiFi issues. I don't I did learn recently that my Bluetooth does not seem to be fully functional.
Sent from my GT-P3110 using XDA Free mobile app
So far, all I've tried (and stuck with) are stock 4.1, stock 4.4.2, and CM 12/12.1.
Stock ROMs were fairly snappy, but I was always a little fearful (irrationally, but still) of trying to debloat while on 4.4 (and I remain fearful of downgrading the bootloader). This is my daily driver, though, and it must remain so until I become eligible for a newer phone in December (or I can pick up something better, used, for extremely cheap ...).
I have been toughing it out on CM 12 since late January. I like several of Lollipop's UI changes and new features (as well as CM's additions over stock), so despite some frustrations with bugs and somewhat-laggy performance, I haven't felt terribly compelled to try CM 11, or to go back to stock 4.4.2. (At least, not all the time; there have been moments of extremely slow response times where I've wanted to wipe /system right then and there and flash CM 11. I have stuck with 12 so far in hopes of improvements on the way to the first snapshot.)
Also, vo_danh, I was the one who reported about the issue with simultaneously running Maps and Play Music. I don't think I've ever gotten a phone call while trying to run those, but suffice to say that I have enough trouble with (occasional) lag when a call comes in.
If you're already on the kk boot loader like me, you don't need to downgrade the boot loader for cm11. Its been almost a week and i am still just amazed at how well this config is working for me. The battery life is like new again. Don't be afraid of debloating with titanium, since you can back it up first before unisntalling, if anything goes wrong, simply reinstall the backup. As a safety, after I restored to stock 4.4.2, updated to 183.84.15 OTA, I created a TWRP backup, so if anything goes wrong I can just restore it with TWRP instead of doing through all the steps to go back to stock. I didn't remove everything that was on that debloat list, just most things from verizon or anything I raw under 'running' list that I didn't need. It's so stable and fast. I would only move to a stock + debloat rom now for this phone for now. If I had a stronger phone there's no doubt i'd be using Cm12.1 but for now, this phone isn't meant to handle it smoothly and the wifi issues i had with Cm11 just make it not worth it. All wifi issues are gone now on stock. I didn't have wifi issues on any of the other roms either.
vo_danh said:
We're all here because we want better roms than what our phones came with...
Click to expand...
Click to collapse
1. One that the phone came with, with a little tweaking. 4.1.2 deodexed and debloated. Best usability and battery life. Slows down with heavy games tho so i unlocked the BL.
2. KK debloated. 4.4.2 i think. better in many respects but I sorely miss the Jb camera. It was wonderful. Battery life had come down a couple of notches.
3. Currently running the Bliss rom (5.1). My earpiece and mic doesn't work with the latest update. lol.
Edit: Call issues in the Bliss rom have been fixed. It's a solid rom and deserves a strong recommendation.