Cyanogenmod 10.2 update through CyanDelta - Droid RAZR M Q&A, Help & Troubleshooting

I tried to update my CM10.2 nighty build through Cyandelta for some weeks now, and the app keep telling me that my ROM is not in the database... Does this happen to someone else too?
Update through a small delta file instead of a 200mb one is a great feature...

Related

CM7 forceclosing on load

Hi guys,
Just have a quick question- wondering if anyone is running into the same problem. I just installed Cyanogen 7 rc1, and it is force closing between the load screen and the welcome screen (for the first time).
I'm not sure if this is the correct place to post this, but any help would be great.
Thanks
Based off what I've read in the development threads, the RC does't seem to be too much of an RC. I'd restore and wait.
you have to flash RC1 over a nightly build.
Nowak4G said:
you have to flash RC1 over a nightly build.
Click to expand...
Click to collapse
Yep! Its was a known issue with the first build of RC1. Something was botched. I recommend you either flash RC1 over nightly build #38, or you just flash nightly build #39 (which already includes fixes that were left out of RC1).
Cheers!

cm7.2 rc1

anyone using cm7.2 rc1 yet? i've been trying to download it, but it's really slow. Been pretty happy with the nightlies so far, and am looking forward ot cm7.2 stable (and cm9 stable of course)
any new bugs that i should be aware of before flashing? I'm not too android savvy, so any tips are appreciated.
thanks
I'm trying to get it too, many people have same issue. The CM servers are hot these days
As far as i know there might be some issue with ringtones when stored on sd card...?
You can check official 'bugzilla'
I did dig but didnt find anything to worry.
tried the official update but it was "meh"
almost same with the nightlies, minus some features from nightlies
I went back to euroskank nightly instead
i suggest using the newest nightlies, 'cause they have some bugs fixed, which RC1 don't. You should see the CM7.2 RC1 thread, there is a .torrent link which is running full speed, opposite to their sever
I'm downloading now will share my experience once I'm done!

[Q] Can't load 7.2 from CWM

Why doesn't the latest release candidate for 7.2 show up as a loadable ROM update from my premium Rom Manager of CWM?
I know I can side load from SD but is there a reason that CWM doesn't recognize the updated ROM?
Littlewhat said:
Why doesn't the latest release candidate for 7.2 show up as a loadable ROM update from my premium Rom Manager of CWM?
I know I can side load from SD but is there a reason that CWM doesn't recognize the updated ROM?
Click to expand...
Click to collapse
Depends on what you are running now. If a nightly, it won't see RC's. If a stable, it won't see RC'S. It will only show you RC's if you are running an RC.
Interesting, I am running a nightly, 7-11162011-Nightly-Encore.
Thanks for your response.

CM10.2 build 2013-09-17

I noticed that the keyboard is missing in the latest cm10.2 build. Bluetooth doesn't seem to work either but the build before that on the same cm10.2 works great!! Much smoother and faster thatn cm10 and cm10.1.
But I wonder if there is a detailed change log for the differences between the two latest 10.2 builds? Because the last one is as said defect.
Otherwise: really awesome work by quarks and all the cm devs! I've updated my defy every step from stock android 2.2 and through all of the cm:s.
Great roms! :good:
Yoelpixel said:
I noticed that the keyboard is missing in the latest cm10.2 build. Bluetooth doesn't seem to work either but the build before that on the same cm10.2 works great!! Much smoother and faster thatn cm10 and cm10.1.
But I wonder if there is a detailed change log for the differences between the two latest 10.2 builds? Because the last one is as said defect.
Otherwise: really awesome work by quarks and all the cm devs! I've updated my defy every step from stock android 2.2 and through all of the cm:s.
Great roms! :good:
Click to expand...
Click to collapse
Keyboard shouldn't be missing, you might have flashed the wrong gapps. Bluetooth file transfer works, bluetooth headset for calls doesn't.
you have to flash gapps package again every time after update the cm10.2 rom
Sent from my MB526 using xda app-developers app
The right gapps can be found in my signature.

[Q] Most stable Defy ROM?

Im giving away my Defy to my brother, who is not good at ROM hacking thus I want to install him a ROM that is as stable as possible. I've installed one of Quarx's 4.3 ROM to it (2 months ago), but after a few days it refused to boot (guess it was the data corruption bug). So I wiped everything, now it has stock 2.2 ROM.
Any recommendations on a newer ROM, that has as few issues as possible?
syddd said:
Im giving away my Defy to my brother, who is not good at ROM hacking thus I want to install him a ROM that is as stable as possible. I've installed one of Quarx's 4.3 ROM to it (2 months ago), but after a few days it refused to boot (guess it was the data corruption bug). So I wiped everything, now it has stock 2.2 ROM.
Any recommendations on a newer ROM, that has as few issues as possible?
Click to expand...
Click to collapse
I suggest trying MS2Ginger or CM7.
hotdog125 said:
I suggest trying MS2Ginger or CM7.
Click to expand...
Click to collapse
Why not cm11? i think it's the only one stable since cm9, and almost everything works.
Android_74 said:
Why not cm11? i think it's the only one stable since cm9, and almost everything works.
Click to expand...
Click to collapse
CM11 is not yet ready fully and it's not fully stable.
SlimBean 4.3.1
GB ROMs: MS2Ginger or CM7, already mentioned.
JB ROM: STABLE SlimBean 4.3.1 (final) build2.2.
Absroid said:
GB ROMs: MS2Ginger or CM7, already mentioned.
JB ROM: STABLE SlimBean 4.3.1 (final) build2.2.
Click to expand...
Click to collapse
Do not install Slimbean for someone who doesn't flash his phone. Slimbean uses a customized version of the playstore, which means that the playstore won't work if google updates it.
There's nothing like CM7 for stability. I thought 4.1.2 was robust but it's starting to behave strangely after a couple of weeks of use.
Nemado said:
Slimbean uses a customized version of the playstore, which means that the playstore won't work if google updates it.
Click to expand...
Click to collapse
Good point, but correct and incorrect.
Google Play Store 4.4.22 still working fine. It shouldn't be a problem to replace or manually update it to the latest 4.5.10.
Just download com.android.vending-4.5.10.apk and install the update.
Absroid said:
GB ROMs: MS2Ginger or CM7, already mentioned.
JB ROM: STABLE SlimBean 4.3.1 (final) build2.2.
Click to expand...
Click to collapse
Is Slimybean based on Quarx's 4.3 ROM? Cause that has several bugs - one of them is, that a partition gets corrupted rendering the phone unable to boot.
Is there a buglist for Slimbean 4.3.1?
syddd said:
Is Slimybean based on Quarx's 4.3 ROM? Cause that has several bugs - one of them is, that a partition gets corrupted rendering the phone unable to boot.
Click to expand...
Click to collapse
Check the link for sources. If you mean Master Quarx's kernel, then yes. But if you want to use another one in JB, your choises are very limited..
This build is too an unofficial port, so only Slim-parts can be called stable, to be more accurate.
Is there a buglist for Slimbean 4.3.1?
Click to expand...
Click to collapse
Changelog stable build 2
If you have time, you should test these suggested GB and JB builds.
Absroid said:
Good point, but correct and incorrect.
Google Play Store 4.4.22 still working fine. It shouldn't be a problem to replace or manually update it to the latest 4.5.10.
Just download com.android.vending-4.5.10.apk and install the update.
Click to expand...
Click to collapse
Bottom line is, the playstore has a convenient auto update feature which Slimroms disables. His brother would have to go to slimroms.net to download further playstore updates. Besides, Slimroms.net could stop supporting the ROM at any time and he would be "stuck" with an outdated playstore. It would work but he would have to pass on any new features or fixes. That's something to consider.
Second thing to consider, every ROM is based on Quarx ROMs. This means that every custom ROM is likely to have Quarx's bugs AND the bugs of the cutomized ROM.
4.3 performs well but it is not 100% functional. I've read they had troubles with bluetooth and I found that some options don't work (adding APN for instance).
4.1.2 is mostly functional but it's not 100% stable. I had several reboots on a fresh install.
Epsylon's latest 4.0.4 is still a good pick. I just installed it and it performs better than JB on Kingdom Rush (it stuttered, crashed and reboot on JB and worked flawlessly on ICS!)
CM7.2 is awesome in every aspects BUT it doesn't have HWA, which means he won't be able to use some of the latest app. Of course, it doesn't mean much since the Defy is not very powerful. But there are some good HWA only apps that still work on the Defy.
I'll say Xperia D3.4 for Defy/Defy+ based on Quarx's CM10 (20130117). It's fast, clutter free, and stable. A very good music player, stable camera, and lots of other addons. Battery life is also not bad.
Because AndroidOS is a chopped/adapted Linux for every hardware (it doesn't contain large drivers library for space economy) is per se a not very stable OS. Even the original firmware isn't "very" stable so the various kind of mods is unstable either. Every mod ROMs is made to cover some aspects and for this cause you must pick the most appropriate for your needs. For beginner try to accomodate with original firmware first, after that try a CM7.x and if you wanna adventure pick a JB or a KK mod. Enjoy.

Categories

Resources