[5.0.2] [EOL] [Weekly 10/Nightly] [2015-04-01] CyanogenMod 12 for i9300
- Thread starter JustArchi
- Start date
See I was gain to try that but I didn't think it would work. I'll give it a go. Thanks [emoji1]
Sent for my KitKat'd SGS3 i9300
Try the 5.1.1,the 5.0.2 is very laggy but CM12.1 is better
Sent from my BlissPop 3.2 ✌
Try the 5.1.1,the 5.0.2 is very laggy but CM12.1 is better
Sent from my BlissPop 3.2 ✌
Yeah I will. Now Xposed is in its alpha stage for 5.1.1. Only thing is I want it to be stable be for I go jump on 5.1.1.
Sent for the sweetest Lollipop'd SGS3 i9300
System should definitely not be taking so much of Ram, that's the memory leak of 5.0 kicking in.
Sent from Bikini Bottom ??
Yeah. I thought so too. System was running for 2 days.
Sent for the sweetest Lollipop'd SGS3 i9300
Thisis hotplugging, a feature of pegasusq governot is that if cpu load goes below a certain value for a certain time it switches off unused cores. If you put load on the cpu you will see it coming live again, if you let it sleep for longer eventually it will hotplug-off anotger one or even two cores.
tapatalked from lollipopped i9300
tapatalked from lollipopped i9300
Cool. Thanks for that. Learn something new everyday on XDA.
Goddamn! That should be a motto! [emoji23]
Sent for the sweetest Lollipop'd SGS3 i9300
Anyone know if the cyanogenmod account stuff (remote locate, wipe) is supposed to work with these unofficial builds?
I'm just asking because i figured I'd make sure it works now, before i lose my phone...
When i tried just now though, i couldn't get a location (didn't try wiping...)
The cyanogenmod account site does show the device with up to date cm version info.
I know it used to work on cm11 because i happened to forget my phone in someone's car and didn't know where the car was parked and couldn't get hold of the driver...
I'm just asking because i figured I'd make sure it works now, before i lose my phone...
When i tried just now though, i couldn't get a location (didn't try wiping...)
The cyanogenmod account site does show the device with up to date cm version info.
I know it used to work on cm11 because i happened to forget my phone in someone's car and didn't know where the car was parked and couldn't get hold of the driver...
Anyone know if the cyanogenmod account stuff (remote locate, wipe) is supposed to work with these unofficial builds?
I'm just asking because i figured I'd make sure it works now, before i lose my phone...
When i tried just now though, i couldn't get a location (didn't try wiping...)
The cyanogenmod account site does show the device with up to date cm version info.
I know it used to work on cm11 because i happened to forget my phone in someone's car and didn't know where the car was parked and couldn't get hold of the driver...
Why aren't you using Google device manager?
Smash that like button if i helped you
Why aren't you using Google device manager?
Smash that like button if i helped you
Thanks for trying to help but,
Android device manager doesn't turn gps on if it happens to be off when you lose your phone. Cyanogenmod account does.
That aside, I've just tried android device manager but all i get is "location unavailable".
Android device manager is listed as device administrator, location is on, android device manager location setting is on.
Don't know what else to check...
On the cyanogenmod account side of things, cyanogenmod account does manage to remotely turn on the gps (as i see gps switch on on the phone itself) but then it just goes in loading without displaying a location.
I searched around a bit and other devices/roms have a similar problem with android device manager so this isn't specific to this rom.
I guess I'll just try some 3rd party app for finding the phone.
Try androidlost, it has tons of other features for stolen device recovery.
tapatalked from lollipopped i9300
I read in the news that Cyanogenmod 12 is nearing its final version ,
you can make a last update to this rom ?
News http://androidayuda.com/2015/06/26/cyanogenmod-11-12-final/
you can make a last update to this rom ?
News http://androidayuda.com/2015/06/26/cyanogenmod-11-12-final/
Similar threads
- Locked
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
953This project is no longer updated, and has been deprecated by [url=http://forum.xda-developers.com/galaxy-s3/development/5-1-x-cyanogenmod-12-1-t3066864]CM12.1[/URL]
Weekly 10 Download (Mega)
Alternative Download via Google Drive
Alternative Download via 4shared
Alternative Download via Dev-Host
Alternative Download via Androidfilehost
MD5: 32b8b85205bb0f78fae710624a32d1da
SHA1: 040bfe316dda94a260bbece3301639fb55318d30
Unofficial nightly builds by [URL="http://forum.xda-developers.com/member.php?u=4898097"]@arter97 [/URL]
Changelog:
Background:
Due to lack of official maintainer for i9300 device for CyanogenMod. I, together with @Moster2 decided that we will work unofficially on i9300 device tree for CM12, to bring Lollipop goodness to our beloved Galaxy S3.
All builds provided in this thread are UNOFFICIAL, which means that:
- There is no official support for i9300
- There are no OTAs available
- There are no automated "nightglies"
At some point, we definitely will try to make proper pull requests, and maybe even support CM12 officially, but at the moment this project is in WIP - Work-In-Progress state, and many things are still broken/unusable. Until we finish, all builds are unofficial, and proper device support is not finished yet.
At the moment, this project is considered: BETA. All core functions should work, ROM shouldn't have any critical issues, but it's still not ready to mark as stable. However, it should work properly as daily driver.
Please refrain from talking about other kernels than stock. We can't track every kernel and it's problems, hence, you're using other kernels at your own risk. Please don't report bugs while you're using custom kernels.
Main developers:
- JustArchi
- Moster2
Thanks to:
- dhiru1602
- arter97
Current issues
Manifest / Sources
Build instructions:
Follow CM build instructions for i9300. When doing repo init, don't forget to declare CM-12.0 (-b cm-12.0) instead of CM-11.0.
Before "breakfast i9300", you must include our manifest and resync the sources:
Code:croot cd .repo mkdir -p local_manifests cd local_manifests wget https://raw.githubusercontent.com/ArchiDroid/manifest/cm-12.0/roomservice.xml croot repo sync
Notice: Our manifest already includes proprietary_vendor_samsung, so don't execute ./extract-files.sh. Just repo sync.
Then follow "breakfast i9300" and the rest of the commands in original instructions, while keeping in mind above notice.
XDA:DevDB Information
[5.0.2] [EOL] [Weekly 10/Nightly] [2015-04-01] CyanogenMod 12 for i9300, ROM for the Samsung Galaxy S III I9300
Contributors
JustArchi, Moster2, arter97
Source Code: https://github.com/ArchiDroid
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod 12
Version Information
Status: No Longer Updated
Created 2014-11-12
Last Updated 2015-04-06132
The problem of people nowadays is the fact that they destroy their own system intentionally, then blame the ROM for all their problems.
If we look at google services for example, what are they? A bunch of closed-source apps that SHOULD work on android platform. Now if they don't work, it's a problem of android platform, or application itself. If CM12 is based purely on Android - AOSP, and google app doesn't work as it should, then it means that the problem is in poorly designed app, which is not possible to work under certain circumstances and flaws on specific android platform. Android is not perfect, it may look like it works, but it's just a thousand of pieces glued all together, if something breaks, everything will ruin.
Some people blindly restore their apps and data from other systems, and they can't see any problem with it. Poorly designed app may not work properly with data that was created BEFORE certain update was introduced. If Lollipop introduced a new way of doing something, and application is doing this thing in old way, which is incompatible or at least not fully compatible with the new way, it IS gonna break, sooner or later.
We're not fixing android here, we're not fixing the framework, we're not fixing the android runtime. We are fixing android's support for i9300 device. Long sms issue was related directly to the RIL, it didn't work, because our RIL had exactly the same problem as incompatible app has - it worked the old way, and didn't want to work in a new way. What we did? We added a workaround number #72381128293 that fixes the issue by implementing a new way that utilizes the old working way, making certain thing work in new environment.
i9300 does NOT support android platform well. It never did, because Samsung's policy denies any developer like me access to their proprietary sources that include the support for their platform. It's like working with a big blackbox, you put a cup in the front, and you get a cup of coffee from the back. You have no idea what is happening in between, you have input and the output. Now, when it works, it's nice, we're getting the effect we want, alright? The problem is when it doesn't work. We put a cup in the front, but the cup is too small and black box isn't working properly for it, so we get empty broken cup as the result, which is not the cup of coffee we want.
There is no software that is flawless. Software is designed and written by humans, humans are making mistakes. Even Google fuc*ed up their early lollipop release for their own devices - nexuses, which had various memory leaks, didn't work stable enough, and even wi-fi had several problems. You can say "well, it doesn't happen on iOS or windows phone...", you're wrong. Every operating system has it's problems, the question is how well they can hide them from the users, or catch the exceptions and handle them without interruptions. Developers design software that should work properly on certain hardware. If you know how certain hardware works, it's easier to spot problems, fix them in proper way, and make software run better. When you don't know how hardware works, you have no documentation and all you have is black box with the input at front and the output at back, fixing anything in proper way is impossible, and all your fixes are usually either workarounds or hacks, to make broken things work, without understanding what was broken in the first place.
This is the case with i9300. Some great developers such as Paul Kocialkowski reverse-engineered some parts of the black box, allowing us to fix it or modify as we please, but big majority of things that we need are impossible to reverse-engineer, due to complexity. For example MALI blobs or a modem. If google suddenly changed the way Android utilizes the GPU, making old blobs not working properly, we had no idea how to workaround/hack it, and Samsung didn't release new "blackbox" to fix this problem, we would have NEVER make working release. There are certain things that must stay the same to make support for certain device. If something changes, like RIL, it's the question how fast, and if, we will spot the issue and fix it. There are no assumptions, you can't assume that everything will be fixed at some point, because this statement is already false with samsung's policy - things like screen mirroring, support for Samsung's TVs and certain other highly-proprietary things will never work, until Samsung's policy changes. It's not like they can't work, they certainly do, the problem is that there is no developer that will even TRY to make it work, because the amount of knowledge and catch-and-try fun is too damn high to finish in the next couple of years.
Take a look at me for example. I started having fun with my sammy-based ArchiDroid around 2 years ago. This is not much, look at my join date, it's march 2013. Since then I learnt much how Android works, how badly is our device supported, how to make things a little easier. I spent much time on that, I managed to make one of the most popular ROMs up to this point for i9300 (ArchiDroid), this is much in terms of things that you can do in 2 years, especially, because I didn't know much about Android when I was starting the fun.
The more you know, the less time you have. I barely can find time for developing for i9300 these days, and I'm sure that I won't find any time when I change the phone, as my old LG E610 is waiting for kitkat since last year, and I managed to compile only TWRP since then. You know that this release wouldn't been possible without help of @Moster2, as he is the boss here working on support for i9300 right now. I'm sad that there are only three developers left for i9300, and I'm the one of them.
Quoting Dhiru: By the time we fix hwcomposer and other core things to make proper support for i9300, people are going to change their phones already. If you want an advice from me, stay away from Samsung, don't support their "we-don't-care" policy regarding development. Take a look at many other companies that do make quality phones and care about the developer, Sony, LG, and Google (Nexuses) are only some noticable examples. I don't know when I'm going to change my phone, but it won't be a samsung for sure.106Unofficial nightly builds
Unofficial nightly builds
/* Info */
- These nightly builds are for those who want cutting-edge changes ready for installing, substituting official CyanogenMod nightly.
- These builds are based on CyanogenMod 12 by @JustArchi and @Moster2
- Please consider donating to JustArchi and Moster2 before using this ROM.
- The ROMs uploaded are provided "as is" and no support will be given. You're installing those at your own risk.
- For changelog, visit https://github.com/CyanogenMod and https://github.com/ArchiDroid.
- The builds are automated as long as my computer is operational.
- Because those are an "unofficial" nightly, no OTA support will be given. CMUpdater app is excluded.
- There are no funny, funky changes made. Builds are made as cleanly as possible.
- Builds are built with the latest Oracle's JDK 7.
- Builds are always built after fully clobbering the previous build.
- Block-based-OTA is disabled for making 3rd-party easy to modify this ROM.
- Other developers/cookers are encouraged to make his or her ROM based on these builds as long as they leave proper credits to @JustArchi and @Moster2.
- All apk and jar files are not compressed for optimal memory usage.
- Builds are "user" builds. Meaning it's more optimized than a "userdebug" build, but lacks root access. If you need root access, flash SuperSU upon installation.
/* Downloads */
XDA DevDB Downloads (located on the top of the thread)
arter97.iptime.org
Donations would help me with our house power bills... :silly:
