-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
if you're missing com.system files then you either got a bad download, bad flash, or modified your .zip file. Redownload the file, CRC/MD5 check the download, transfer it to your phone or means of flashing and make sure the MD5 still checks out, make sure you do a completely clean flash from recovery and make sure there is no errors when flashing.
Also, there is no stable 4.4.x yet.
Also, there is no stable 4.4.x yet.
wetbiker7
Extreme Android User
You're wrong. The Snapshot builds of CM11 are stable.
BRAINZ2013
Extreme Android User
And if your getting any com.android. message pop up you may have the wrong gapps or a build.prop needs to be edited
BRAINZ2013
Extreme Android User
As I said it can be the gapps or build.prop . . its a few other rcustom ros for the device such as pacman , mokee, slimkat . a few to try or where u got the download check to see if anyone is having the same issue or as the dev . may can help if you drop a dime to them dime is aka message 
:what:
:what:I believe you're wrong...
Nightly: usually generated every 24 hours, experimental, newest features, unstable!
M Snapshot: milestone snapshot, more stable than a nightly but potentially some issues
Release Candidate: last builds before stable release, few minor issues, mostly stable and safe for daily use
Stable: most stable version available, all or nearly all issues resolved
Just because it says "more stable" doesn't mean "stable", theres a RC hurdle before it's near done.
Information: Samsung Galaxy S III LTE ("d2lte") - CyanogenMod
BRAINZ2013
Extreme Android User
Nahhh your wrong any custom ROM is unstable and any ROM you flash is unstable that's why the carrier say if you root that you void your warranty . even the stock ROM is unstable . unstable means it will cause a problem but can be used as a everyday use . now you asked about the snapshot and for some devices they are stable keep in mind that this d2lte is a custom ROM can be used with many carriers with a edit to the build.prop and maybe a modem . not every ROM will require a update with a modem or radio only Samsung and HTC I seen and worked with . but to answer your post you said it wasn't no snapshot stable and that's wrong cause for some it is just not the d2lte cause its been combined for custom usage .
BRAINZ2013
Extreme Android User
BRAINZ2013
Extreme Android User
If this is a problem just get a crash report . such as logcat etc.
wetbiker7
Extreme Android User
Well, I guess stable just depends on the person running it and the way they've set their phone up. Personally, I've ran the 1st 2 Snapshots and they worked flawlessly for me. That's the reason their backups are saved to my pc.
I guess if you really break it down, is there a truly stable ROM? I guess not. LOL. Even the stock ROM is questionable.
Another thing plays a huge part of how the ROM runs is the phone its installed on. As many of us know, what runs perfectly on one phone may not on another.
Great post BRAINZ. That, my friend, was very well written.
I guess if you really break it down, is there a truly stable ROM? I guess not. LOL. Even the stock ROM is questionable.
Another thing plays a huge part of how the ROM runs is the phone its installed on. As many of us know, what runs perfectly on one phone may not on another.
Great post BRAINZ. That, my friend, was very well written.
Tokens210
Android Expert
yea ive run many different builds of CM11 4.4.2, mostly nightlies, never 1 single time have i had a stability issue, everyone seems rock steady to me, not to mention the CM team is one of these most famous Rom teams around who make daily updates and changes so if you believe there roms arnt stable why flash a rom at all
ive also detailed out on other thread how some dev teams work together using github which allows them to basically share a folder so everyone in the group can do their respective jobs, all it take is something as simple as a colon or period or anything at all to be missing or out of place to bork the entire build in which case they wont know until someone tells them
as wet said your device and what you actually put on it matters just as much
no device is identical, i could overclock my phone and if you entered my settings it may crash yours
there are also apps that arnt optimized for later roms that can cause jinky behavior
then theres rouge apps which are an entirely different beast altogether and can make even a 100% stable phone act unstable and even drain the battery faster
using custom kernel's is another way to cause issues as seen in many of the thread, some of the kernel builds have been getting borked or causeing issues on one rom and not another
ive also detailed out on other thread how some dev teams work together using github which allows them to basically share a folder so everyone in the group can do their respective jobs, all it take is something as simple as a colon or period or anything at all to be missing or out of place to bork the entire build in which case they wont know until someone tells them
as wet said your device and what you actually put on it matters just as much
no device is identical, i could overclock my phone and if you entered my settings it may crash yours
there are also apps that arnt optimized for later roms that can cause jinky behavior
then theres rouge apps which are an entirely different beast altogether and can make even a 100% stable phone act unstable and even drain the battery faster
using custom kernel's is another way to cause issues as seen in many of the thread, some of the kernel builds have been getting borked or causeing issues on one rom and not another
BRAINZ2013
Extreme Android User
I forgot to mention about the github. but in rooting if you love the looks of a custom rom and its not stable but it can be fixed for a daily use . just put your back into it . repair things ask the dev and others you may have a good rom from a few minor fixes . 