Related
I see in the Dev forum that the first RC1 of Cyanogenmod 7 for Milestone is available, but when I go to download it here, it doesn't seem to be available. I guess it would be called update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip but that last one available was the 11.02.15 release. Does anyone know whether the RC1-7.0.0-11.02.18 has been withdrawn for some reason?
I've been testing each and every build with good success, so I'm really keen to try the new one. I would ask in the dev forum, but I'm relatively new at the XDA forum and am therefore not eligible to post in it.
SF
Well, I eventually found the correct download link at https://github.com/downloads/nadlabak/android/update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip
Thanks,
SF
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
I would stick with cm6 for now. CM7 could use many improvements and as of now is very memory hungry (I was on the feb.10 release). CM7, however, has many bug fixes that are not implemented in cm6, for example, the wifi fix (wasn't working with some n routers before I think [depending on the security type or something] ) and it seems as though there is also the random freeze + random reboot fix (using another, older kernel) I would not switch to CM7, until many bugs are fixed. Also some games don't work.
FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
It's great. But video playing not working for me.
So I installed CM7 to try it out, and on RC1 my videos play fine (widescreen) using the included "Video" app. Well most of them do, one of them is displayed 4:3 for some reason?
I'm finding that it works quite well. Battery life is good, but there are a few bugs that need working out. CM6 is probably better if you need your phone to be 100% reliable, but I like to push the boundaries and play around.
Bugs or missing features so far:
- Button lights and keyboard backlight not working properly for me (and at least one other user here)
- Auto backlight brightness not working for me at all
- Volume button swapping/remapping not yet implemented, so that in lanscape mode left means louder (which is the wrong way round for me)
- Memory usage is a problem, so that Launcher pro keeps having to re-initialise
- Camera is VERY unreliable
- Getting random reboots and lockups, especially in Google Maps
Still, things are getting better with every release and I can always go back to CM6 if I want, since I made a Nandroid backup in OpenRecovery before I installed the CM7 update. I've just installed the RC2 update, so lets see how that goes...
SF
Hi..
I Have a nexus one. My question is regarding the CyanogenMod Nighty and stable. whats the difference? Which one should i use? Which is better?
Thanks.
Nightly build = Work-in-Progress version. You can try new features, but it can be buggy and less stable. Besides, there's no support provided officially.
Stable = The 'Official' version.
great
Thanks a bunch, helped me out
FYI, the nightlies will also be the first to get major bugfixes like the wonk. That has been in the nightlies for almost a week, and they are still working on updating the stable to 7.0.4 to include it. The nightlies have also been running 2.3.4 for a couple of weeks, which was nice when the big security flaw came out that affected all versions except for 2.3.4.
Nightlies usually end up still being "stable", they just don't have any labels next to it, although occasionally there have been issues that will crop up that are usually resolved the next nightly (like earlier this week, a nightly caused the alarm app to FC whenever someone tried to set an alarm, this was resolved in the next release).
I usually stay behind on the releases, as I need my phone to be running and able to do the functions that I need. This way I can read what others are experiencing and see if it is worth upgrading to. Currently I am on #76 and I think #80 was just released.
Also, "stables" aren't always stables (which is the case in most programs). Just like with Windows, there are updates that need to be put out when security holes or major bugs are patched. But the smaller bugs will usually get fixed in the nightlies long before they ever make it to the stable.
Overall, I love the nightlies. I don't think I could go back to a stable build.
bassmadrigal said:
FYI, the nightlies will also be the first to get major bugfixes like the wonk. That has been in the nightlies for almost a week, and they are still working on updating the stable to 7.0.4 to include it. The nightlies have also been running 2.3.4 for a couple of weeks, which was nice when the big security flaw came out that affected all versions except for 2.3.4.
Nightlies usually end up still being "stable", they just don't have any labels next to it, although occasionally there have been issues that will crop up that are usually resolved the next nightly (like earlier this week, a nightly caused the alarm app to FC whenever someone tried to set an alarm, this was resolved in the next release).
I usually stay behind on the releases, as I need my phone to be running and able to do the functions that I need. This way I can read what others are experiencing and see if it is worth upgrading to. Currently I am on #76 and I think #80 was just released.
Also, "stables" aren't always stables (which is the case in most programs). Just like with Windows, there are updates that need to be put out when security holes or major bugs are patched. But the smaller bugs will usually get fixed in the nightlies long before they ever make it to the stable.
Overall, I love the nightlies. I don't think I could go back to a stable build.
Click to expand...
Click to collapse
I just checked the website and for the nighty it has #81. I understand the part of updating at night. My question is like how u said that you are on #76, so do you have to manually change to #81(by flashing and making a backup) or it automatically updates? Am confused.
You manually update like you would a normal release of CyanogenMod. If you have the premium version of ROM Manager, it can notify you of new nightlies and you can download them through it. If you don't have it, you would manually have to download the files from http://mirror.teamdouche.net.
And I ALWAYS recommend making a backup. That way, if one of the nightlies you install is all screwed up, you just revert to the last one and wait until it is fixed bfore you flash the next verison.
You don't really have to wipe when going to the next nightly. Just flash and all your data is in tact, just like a regular upgrade.
I suggest going with the latest nightly.
You can get it here: http://get.cm/?device=quincytmo&type=RC
Seems stable. Everything working so far.
I guess I need to go check it out. I'm still on the latest monthly.
As far as I can tell, it is caught up with the nightlies as far as features go: Camera timer, stylus gestures, whatever else is new. Everything I've tested so far works, wifi tether, bluetooth etc,
Yeah, so far so good. It seems pretty stable and fluid. Haven't checked battery life. I noticed on the last nightly that it took longer to charge the battery.
Battery life here seems very good. Very smooth, not getting lagginess that was in a couple of nightlies.
Had a couple of instabilities with a couple of apps. Reinstalling them seems to have fixed the problem. Time will tell.
Sent from my SAMSUNG-SGH-T879 using xda app-developers app
Going back to M3. Having too many instabilities, random reboots, lock ups.
srpanadero said:
Going back to M3. Having too many instabilities, random reboots, lock ups.
Click to expand...
Click to collapse
I was about to say that I haven't seen any bugs with this latest release, but then I thought for a second and remembered that I had a weird screen issue where my screen was flickering, and then went black until I restarted the phone. It only happened once, so I didn't think much of it. I expect a few bugs with any ROM no matter how stable/baked it is.
Here is a bug report for graphical issues. Now is the time to report any bugs that you see.
https://jira.cyanogenmod.org/browse/CYAN-1057
Never saw a blue screen until I used this one. Random reboots also, something I never dealt with before.
Now there's an RC2. Trying it now.
fraughtsigewulf said:
Never saw a blue screen until I used this one. Random reboots also, something I never dealt with before.
Click to expand...
Click to collapse
So then could you and anyone else who've seen the issue sign up and vote on the bug report here: https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/CYAN-1125
Either that or add your own comment and log if you have. Hopefully the devs will then see and fix the problem.
My random reboots seem to have gone away, but I still have the issue of where BT won't turn on unless I reboot, or reboot twice.
hogasswild said:
My random reboots seem to have gone away, but I still have the issue of where BT won't turn on unless I reboot, or reboot twice.
Click to expand...
Click to collapse
Now i'm getting freezes and reboots 5-6 times a day. Today I could hardly use my phone. And that was even after doing a full wipe this morning and reinstalling the latest nightly and Gapps. I think i'm gonna roll back to a version from a couple of months ago if I can find one and see if that helps.
I did go to that dev page that was suggested earlier in the thread and signed up and voted up this issue. I hope it gets the ball rolling.
I'm kinda disappointed. I know these are nightlies and aren't supported, but i'm really used to Cyanogenmod putting out solid builds, even for their nightlies. A few bugs I can deal with, but this is unusable.
Well the night lies are getting worse. The RC1 and RC2 for me are usually OK for a day or so, but the more time goes by and the more frequent the random freeze and reboot.
Back on M3 and that's OK.
error when installing
when I try to install the zip file I get this error "assert failed: getprop("ro.product.device)...." this is just the beginning the type is small and its hard to read- any suggestions? Some searches I've done say this error shows when the ROM is for the wrong phone, but don't see how that can be. I have the T-Mobile Galaxy Note for sure. Thanks for any help that I can get. Since it seems like T-Mobil is never going to upgrade OTA to Jelly Bean I really would like to get this ROM.
Just making sure. You have installed the TWRP recovery? Can't do it unless you have installed this first.
#2. You do not want this ROM(s), read the thread, nothing but problems. My suggestion if you want a custom ROM, is to download the M3 CyanogenMod. Here is the links. http://get.cm/?device=quincytmo&type=snapshot
srpanadero said:
Just making sure. You have installed the TWRP recovery? Can't do it unless you have installed this first.
#2. You do not want this ROM(s), read the thread, nothing but problems. My suggestion if you want a custom ROM, is to download the M3 CyanogenMod.
I was using Clockwork MOD. I will admit I'm a bit of a Newb with this custom recovery stuff. I went to install Goomanager on my phone, but when I reboot it reboots it into Clockwork MOD. So do I need to uninstall clockwork MOD somehow? I will try the other ROM you mentioned, but I think I had tried that one as well and got the same error. Of course this was using clockwork MOD.
Thanks,
John
Click to expand...
Click to collapse
This is the twrp page for this phone.
http://teamw.in/project/twrp2/113
It lists several ways to install it. Try them all, one will work.
srpanadero said:
Well the night lies are getting worse. The RC1 and RC2 for me are usually OK for a day or so, but the more time goes by and the more frequent the random freeze and reboot.
Back on M3 and that's OK.
Click to expand...
Click to collapse
So M3 is stable enough to use? I couldn't remember whether it was M2 or M3.
Yes M2 and M3 are stable enough for daily use. Actually any nightly from that time is good too. It wasn't until after M3 that things took a dive, and didn't get any better with RC1 and 2.
Only problem I'm aware of is a bug with the Bluetooth on off toggle that affects some. If it happens reboot or force close Bluetooth share.
Hallo,
I am sorry, to post it here, but I cannot post in the related forums below 10 posts.
So I had 4.1.5 and it was great. I flashed 4.2.3 now and it was great until after pretty much one day, when it becomes slow, had the same issues with 4.2.2 (becomes slow after a day until reboot or downgrade to 4.1.5) where I downgraded again, but it is not possible anymore without resetting the launcher3 due to some changes.
It will crash repeatedly.
Any help?
Kind regards
neox
I've been using CM based Mackay ROM for a long time now, updating to every new version as they have been released, and have not experienced anything like what you are describing.
Also, you should have really posted in the Mackay ROM thread...
Sent from my GT-I9000 using Tapatalk
@neox456! I am not sure I understand your problem fully. I have been using the same ROM since it came out for Kit Kat but never had a problem such as yours.
Could it be the no. of apps you have in your phone ? Or maybe because you aren't using low mem option (which was a feature of Kit Kat)?
It'd be good if you could explain your issues a bit briefly.
neox456 said:
Hallo,
I am sorry, to post it here, but I cannot post in the related forums below 10 posts.
So I had 4.1.5 and it was great. I flashed 4.2.3 now and it was great until after pretty much one day, when it becomes slow, had the same issues with 4.2.2 (becomes slow after a day until reboot or downgrade to 4.1.5) where I downgraded again, but it is not possible anymore without resetting the launcher3 due to some changes.
It will crash repeatedly.
Any help?
Kind regards
neox
Click to expand...
Click to collapse
Did you install CM10.2 (stable) or CM11 before Mackay 4.2.3? This increases your partition giving you better performance and is recommended for KK roms. Try again with 3 wipes plus Format System first, then the CM11, 3 wipes and format again then the Mackay Rom. If you get into trouble, go back to GB 2.3.6 with ODIN like you did when you first rooted your phone and back up from there. Hope it works for you.
The difference was between 4.1.5 and 4.2.2/3. But I played around a little and the main difference was, that KSM was on with the later ones and not with 4.1.5 so I am pretty sure that slowed my device down after a while.
I'll try 4.2.3 without KSM now and see if it won't slow down.
I cannot answer on the official Mackay-Thread until I reached 10 posts!
neither can I yet...
Naaah, it did not really help...
But I guess it is the KitKat slow downs... it is not as horrible as 4.3, but still far from well usable.
neox456 said:
Naaah, it did not really help...
But I guess it is the KitKat slow downs... it is not as horrible as 4.3, but still far from well usable.
Click to expand...
Click to collapse
Very strange.. I went all the way back to GB 2.3.6 then CM 10.2 (or 11) then SlimKat and it works really well with no FC or lags. (well maybe say max 2 second delay opening Whatsapp but I can live with that. Plus they all seem to have a 1 or 2 second delay when a call comes in for the screen to register.
Well... I am not sure... Maybe it is too many apps. At least they are not constanlty crashing like in JB4.3.
What about waking up the phone for you? Do you have a 2 seconds delay there, too? Well I sometimes have a more like 10-15 seconds delay. I press the power button and nothing happens and after a while you notice the phone is ready, because the LEDs are glowing and funnily you can already unlock it, although the screen does not show anything yet...
Well and sometimes it is only a few seconds...
I have always used CM or Mackay-CM... not sure, whether the other ROM will make such a big difference...
I had lags with CM in ICS so I went to Liquid smooth by aways .
http://forum.xda-developers.com/showthread.php?t=2223729
I like that one, no problems opening apps or answering phone call. Pkus he uses semaphore and the Nova Launcher which has a nice look and feel. Pluis customisable.
Then after to SlimKat, (after increasing partition using the CM11) which works pretty good. I will flash the mackay rom or the omni this weekend to see how it behaves in comparison.
I am down to CM9 (still Mackay) now and happy with it. :angel:
Some features got lost, but I am happy, because in general it is way more useable.
Hey all, got a problem which needs solving - haven't been able to figure this one out myself.
Okay, here's the dealio:
I'm running CM 12.1 nightly on my HTC One (m7) device and haven't really had any problems which proved to be as hard to solve as this one. My launcher - i use ADWLauncher -constantly crashes no matter what I do (Trebuchet is acting no differently).
Also noteworthy, many areas of my settings are unreachable (such as settings->apps) as they immediately crash upon attempting to access them as well. I've tried numerous methods to fix this annoyance to no avail.
This has been ongoing for over a week now although yesterday my launcher worked flawlessly for a good 8 hours (just the launcher, the other crashables within 'settings' were still crashing. And now for some reason a selection of my apps are crashing as well.
kayohbe said:
Hey all, got a problem which needs solving - haven't been able to figure this one out myself.
Okay, here's the dealio:
I'm running CM 12.1 nightly on my HTC One (m7) device and haven't really had any problems which proved to be as hard to solve as this one. My launcher - i use ADWLauncher -constantly crashes no matter what I do (Trebuchet is acting no differently).
Also noteworthy, many areas of my settings are unreachable (such as settings->apps) as they immediately crash upon attempting to access them as well. I've tried numerous methods to fix this annoyance to no avail.
This has been ongoing for over a week now although yesterday my launcher worked flawlessly for a good 8 hours (just the launcher, the other crashables within 'settings' were still crashing. And now for some reason a selection of my apps are crashing as well.
Click to expand...
Click to collapse
Do not expect nightly builds of CM to be stable and bug free. You should only flash a nightly build if you are ready to deal with various bugs. I would try the latest stable or at least snapshot build (if available) and see if you have the same problems.
I hadn't upgraded for a few days when this started which leads me to believe it's not cm's fault but I'll take your advice and give a go with a stable then post my results. Thank you for your time [:=
Got it
Turns out it was an application I had installed causing some sort of confliction. Managed to uninstall it (after a whole lot of messing around due to being unable to access most of my system) and everything has been working just fine ever since.
The app was SD Maid.......