Nightly builds back online 
Now those will be built with i7 4790K(O.C'ed to 4.6 GHz) & 2 SSD with RAID 0 setup.
Now those will be built with i7 4790K(O.C'ed to 4.6 GHz) & 2 SSD with RAID 0 setup.
[5.0.2] [EOL] [Weekly 10/Nightly] [2015-04-01] CyanogenMod 12 for i9300
- Thread starter JustArchi
- Start date
Nightly builds back online
Now those will be built with i7 4790K(O.C'ed to 4.6 GHz) & 2 SSD with RAID 0 setup.
Wow..
Sent from my GT-I9300 using XDA Free mobile app
You should use the q&a thread.
Sent from my GT-I9300 using XDA Free mobile app
Nightly builds back online
Now those will be built with i7 4790K(O.C'ed to 4.6 GHz) & 2 SSD with RAID 0 setup.
thanks and dayyuummmm haha
Gz. How much time you need to build on that?Nightly builds back online
Now those will be built with i7 4790K(O.C'ed to 4.6 GHz) & 2 SSD with RAID 0 setup.
TapaTold from LolliPooped Crapsung GT-I9300
This has nothing to do with development thread,same as arter97 new PC specs (dunno why he even mentioned as it will only encourage more spam) sorry nothing against you ,just talk in general
Sent from my GT-I9300
Nightly builds back online
Now those will be built with i7 4790K(O.C'ed to 4.6 GHz) & 2 SSD with RAID 0 setup.
Great build !!! :good::good:
pd.: I'm afraid to install the new nightly and tomorrow new weekly is released...
Nightly builds back online
Now those will be built with i7 4790K(O.C'ed to 4.6 GHz) & 2 SSD with RAID 0 setup.
Nice setup
PS. Hope you have torture stability tested your overclock for at least 24hrs continuously. Usually oc'ng a build PC is not recommended as there can be errors. 4790 is already fast enough right
. But I believe you know what you are doing. Keep up the good work :beer:Sent from my GT-I9300 using XDA Free mobile app
Congrats!Nightly builds back online
Now those will be built with i7 4790K(O.C'ed to 4.6 GHz) & 2 SSD with RAID 0 setup.
But is the builder running stable - won't there be any cryptic single bit errors (or similar problems) in produced bytecode (or other files) caused by OC?
hi guys I have a problem upgrade to version 1.3.15 of the day and does not leave me off the lights of the physical buttons when they accept the disable him and go put back assets
Offtopic: 4.6GHz is a pretty standard OC for any generation i5/i7 since Sandy ***** and it's dead stable at turbo voltage up to max 1.52v per Intel spec (read the spreadsheet for more info). I ran my Ivy up to 5.2 and Sandy up til 5.4, yet the radiator heat dispensation was the limiting factor while stress testing
Anyway on topic, I posted a problem in the Q&A about an issue with wireless I encountered when I was setting up my improved private/voip/hotspot vlans.
When I switched a few times between networks I couldn't connect to any wireless network until I rebooted the phone.
This also happens when I drive with my car as my phone repeatedly tries to reconnect to ziggo hotspot, which haven't worked either since I'm using these builds. Or walking about on campus (also switching AP's).
Anyway on topic, I posted a problem in the Q&A about an issue with wireless I encountered when I was setting up my improved private/voip/hotspot vlans.
When I switched a few times between networks I couldn't connect to any wireless network until I rebooted the phone.
This also happens when I drive with my car as my phone repeatedly tries to reconnect to ziggo hotspot, which haven't worked either since I'm using these builds. Or walking about on campus (also switching AP's).
Nightly bugs are not supported here, anyway by now only works if enable navigation bar, even the default 5 seconds cannot be changed, wait next weekly to check, but is I very minor issue since doesn't make sense to turn it off without activate navigation bar for most people.
Last edited:
welp, i took the plunge and installed the 23/2 weekly. was all going pretty well and i did a load of tinkering to get it to where i wanted it but after a couple of hours i did a refresher reboot and good bootloop'd. unfortunately i can't even say for sure what i'd done immediately prior to rebooting. went straight back to my backed up 4.4 (slimkat). might try again in a couple of weeks. thanks to all involved tho, looks and feels lovely.
Tinkering as in? Could you specify the app you used, anything?
ummm. i'd used titanium for some app deinstallation and restoring some data. not for any app installation though. i'd updated the SU binary by installing supersu. i'd changed some of the properties of the profiles and reconfigured the quicksettings. and played with a lot of the settings. and i'd had a play with a few themes. so quite a bit of playing around (as you do with a whole new version of android) but nothing i thought was particularly controversial. but i'd done quite a few reboots problem-free before i got the bootloops. in hindsight i should probably have just reflashed CM+gapps over the existing installation, that might've got me out of trouble.
Nightly 2015-02-23
I was using stable CM11 on Boeffla 2.7 kernel with TWRP recovery.
Gave CM12 a try thinking I will go back to CM11 until 12 is more stable. Did a factory reset in TWRP, then flashed CM12, gapps and Boeffla 3.0. No issues at all, ROM seems stable and performance is great! I'll use it as my daily driver!
Early days still, but so far a great experience. Thanks devs!
Dejan
I was using stable CM11 on Boeffla 2.7 kernel with TWRP recovery.
Gave CM12 a try thinking I will go back to CM11 until 12 is more stable. Did a factory reset in TWRP, then flashed CM12, gapps and Boeffla 3.0. No issues at all, ROM seems stable and performance is great! I'll use it as my daily driver!
Early days still, but so far a great experience. Thanks devs!
Dejan
Some minor issues, from storage, USB computer connection doesn't open. Using OTG I said mouse was not working, actually it works but cannot see the arrow in the display. Is not possible to use another time than 5 seconds for capacitive buttons light (you can choose but it doesn't change), I use navigation bar so it doesn't matter for me (I am one of the crazy ones that like it better because I am used to use it and because I like that switch between last two apps feature of it ) .
) .
Last edited:
Really Amazing !!
@Moster2 This thing is awesome , i see an occasional jank here and there but that will be fixed as google is improving amdroid and cyanogen is improving cyanogenmod , so with the release of 5.1 i think this will get even better..
And yeah thank you !!!
@Moster2 This thing is awesome , i see an occasional jank here and there but that will be fixed as google is improving amdroid and cyanogen is improving cyanogenmod , so with the release of 5.1 i think this will get even better..
And yeah thank you !!!
Similar threads
- 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:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone