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. Hard. A lot. */

Working

Not Working

NOT A STABLE BUILD





build date and cm version seem to be off. I don't know why, but the kernel version is right build date and cm version seem to be off. I don't know why, but the kernel version is right

Wipe dalvik cache, cache, data and system Flash the ROM Flash gapps

Use the search function. Think of it as Google, but for this thread. Also search Archi's thread Read the last 10-15 pages of both this thread, and Archi's Still haven't found someone who has reported your issue or haven't found a fix? logcatlogcatlogcatlogcat. Post it here in an attachment. Explain how you produced the issue, specifically. "I pressed the button and then the thingy stopped working" is not enough.

XDA:DevDB Information

CyanogenMod 12 semi-nightly, ROM for the Samsung Galaxy S III I9300

Contributors

Version Information

Read theOP.- updater-script (flashing)- kernel (booting)- OpenGL (CPU rendering)- MALI blobs (GPU rendering)- HWComposer and MALI R4P0 drivers- Rotation- Camera (this DOES NOT include stock camera app, use e.g. google camera)- WiFi- Bluetooth- NFC (Android Beam)- Sensors (ALL!)- Internal / External SD Card- Vibration- GPS- RIL (including mobile data)- Nothing?!?This isIf you suffer bootloops, or any other bugs,, unless you can provide a logcat.If you have an issue that has already been solved or reported,. I'm 99% sure that your issue is known and is being worked on by the devs.Youneed to flash this over any other ROM. Wipe dalvik cache, data and system before flashing. Allow some time for ART to finish booting.If it doesn't work for you, and you aren't willing to put the effort in to either get a logcat or perhaps do a little bit of research by yourself,. You clearly should not be running pre-alpha builds.I use the ParanoidAndroid Beta gapps , they work fine.And the downloads? (Changelog is in the next post down) 2014-12-11 (md5sum: 4c96155f2c46c2b3d716fa9e833165fc) 2014-12-10 (md5sum: e8fda36be5e1aaa5b58161363ebafaf5)Screenshot:If you like this, support. They do all the code, I just build the builds.I use TWRP, although any recovery should work fine. As long as your recovery is recent (i.e the latest version), it willmake a difference to how successful your installation is.Doesn't work? Try skipping step 3. Still doesn't work? Logs or it didn't happen.I have a life. I generally prefer my actual life over reading XDA. I do go places without an internet connection. I do not always have a computer capable of building Android. I do sleep. I do go out during the day. I do live in a timezone that is not in the USA. Therefore, I may disappear off the internet for hours, evenat a time. You can always build your own builds if you want!These builds come straight from @JustArchi's repos. To duplicate my build, use the CM 12 manifest and put Archi's roomservice.xml in your local_manifest folder. I recommend getting a CM11 build working before attempting to build this. forkbomb444 , JustArchi, Moster2, arter975.0.x LollipopAlpha2014-12-102014-12-11