yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] grzwolf:
Installed a day ago, works well as supposed.

Nice job, many thanks.
[Galaxy S II Android Development] TriboDoP:
Hi [MENTION=5955924]zjq985062714[/MENTION]

Thanks for keeping KK alive and updated!
[Galaxy S II Android Development] zjq985062714:
thankyou,i just do what i can do[emoji6] [emoji6]
[Galaxy S II Android Development] cosjav:
How can I downgrade from MM rom to this KK rom

Hi,

How can I downgrade from Resurrection Remix MM rom to this KK rom? I have twrp, can I do a normal factory reset and then flash this rom and then gapps or do I also need to wipe system?

Thanks
[Galaxy S II Android Development] TriboDoP:
Hi!

Make a clean install of rom and gapps with full wipe.

(but i think it worked with normal factory reset + wipe cache/dalvik aswell but cannot remember exactly)

I would just try.
[Galaxy S II Android Development] cosjav:
Awesome, that worked (the full wipe) - thanks!
[Galaxy S II Android Development] Rhod-Wulf:
Hello. Thanks so much for your time and work.

How can I help with this build?. I have no idea how, but i'll like follow with this project. I think that this is the best rom for this device (i9100).

If you have got a guide or "how to", please let me know.

Regards and thank you again.
[Galaxy S II Android Development] zjq985062714:
just follow the cyanogenmod official wiki and the thread http://xdaforums.com/showthread.php?t=2814763 can help you a lot.if i my memory is right,official wiki should be wiki.cyanogenmod.com.you can find it easily by Google.if you have any other question,just ask me,i am glad to help you.
[Galaxy S II Android Development] IonutGherman:
I will continue to maintain both 4.4.4 and 5.1.1 alongside 6.0.1. :)
[Galaxy S II Android Development] Rhod-Wulf:
Great!. It seems to be more current than this thread:

http://xdaforums.com/showthread.php?t=1801690

I'll read it. If i have any doubt i'll try to disturb as little as possible :p

Thank you. Have a nice day!.

Regards.

---------- Post added at 10:23 ---------- Previous post was at 10:08 ----------

Excelent!.

Will you keep this thread or have your own?.
[Galaxy S II Android Development] IonutGherman:
My own thread :)
[Galaxy S II Android Development] Rhod-Wulf:
OK. Let me know when it's ready, please.

I have much to learn...

Thank you!.
[Galaxy S II Android Development] zjq985062714:
just ask.i will try my best to help you,like somebody who helped me[emoji6]
[Galaxy S II Android Development] zjq985062714:
new build should come soon?
[Galaxy S II Android Development] Rhod-Wulf:
Hi!.

Is good hear this news. Do you know if this new build come with security patchs only?. Or can bring some bugs fixes?.
[Galaxy S II Android Development] M4riusz8:
Is this ROM "music bug" free? I heard that CM-builds after 20141111 don't have this problem already, but I would like some confirmation.
[Galaxy S II Android Development] zjq985062714:
what's it mean by "music bug",i don't get any bug report yet,so i can't answer you,but it should be OK,you can ask some else[emoji2]
[Galaxy S II Android Development] :
Music bug aka FP bug? Ancient history. Don't worry
[Galaxy S II Android Development] FreddieFrog:
I just installed this rom, and everytime i reboot the device "Android is upgrading" appears all the time (It's optimizing all my apps). I did a clean install before installing the rom. Is this a bug? I have never experienced this behavior with older versions of this rom.
[Galaxy S II Android Development] zjq985062714:
i will test it with my phone,just wait, if it's true,new build will come tomorrow.
[Galaxy S II Android Development] FreddieFrog:
Did you figure out something, sir?
[Galaxy S II Android Development] zjq985062714:
not yet.because for me it is OK,please consider don't install any app,then test this ROM,bytheway do you install Gapps?if so,which one do you install?
[Galaxy S II Android Development] Phonemagic:
I had that problem using recent versions of open gapps. Try a fresh install and then the base gapps from this link instead, or other alternative gapps.

http://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
[Galaxy S II Android Development] FreddieFrog:
I used the the latest Opengapps for Android 4.4 (Pico).

---------- Post added at 22:18 ---------- Previous post was at 22:18 ----------

Cheers mate! I will check it out.
[Galaxy S II Android Development] mirhl:
Pretty nice project, I see there might be people that just don't want afford the resizing stuff.

But assume I did (just different size, or even totally removing UMS), is this still going to work?
[Galaxy S II Android Development] TriboDoP:
Hi

I am on Partition 1 GB system_4 GB data and this Rom works fine.
[Galaxy S II Android Development] zjq985062714:
in fact,i think it should work welll.Because cyanogenmod official works when i change my data partition.And i see there is someone else say it is work[emoji2]

bytheway what is UMS?
[Galaxy S II Android Development] Saber:
UMS = USB mass storage = Internal sd storage
[Galaxy S II Android Development] Ham1do:
Thank you for updating cm11

All went well except I could not rearrange the quick settings tiles :confused:

( Dirty flash over slimsaber-i9100-4.4.4 )
[Galaxy S II Android Development] zjq985062714:
nobody report this.please consider to clean setting and status bar data.
[Galaxy S II Android Development] almosely:
Hello zjq985062714,

at first: A big thank you for your effort! I own the S2 since 09.2012 and I still love it.

I have a few questions and comments about your project.

1. The downloadable file in your first post is not a version from 19.09.2016, it is from august (08).

2. Which compiler-chain are you using, google, linaro, saber, uber? I would love to hear, it would be just google.

3. Which cm11-version is this exactly? The last version at cyanogenmod downloads is M12 from 15.11.2014. The last versions from the original xda-thread were build by Lanchon, once a nightly from 05.09.2015 and a stable from 04.09.2015. So, I guess, if CyanogenMod was releasing it's last build at 04.09.2015, your version is build from this source-code plus all security patches from google till 01.08.2016?

4. I want to use the TRIM-command, but I don't think that TRIM was implemented in cm11, as it was implemented in cm12.1 and cm13 at 03.2016. Lanchon provides a TRIM-kernel with IsoRec-support (version from 12.01.2016) and I guess, it's working with both his last builds (09.2015). So if your version is from the same source-code, will his kernel work with your build too? BTW, I tried and booted - so far it's actually working, yes, but with no real-life testing till now. And I guess, this kernel by Lanchon is patched for the fpbug too, because he was providing older kernels with this patch and implemented it in his TRIM-kernels later. I think, he just shortened the filename and took away the "fpbug_patched" (or something similar). In a xda-thread (I don't know in which, right now) he stated, that every kernel nowadays is fpbug-patched (or should be) and this was on a date before 12.01.2016.

5. For everyone who is considering to install this build and is unsure about the partition-size of his S2: The system-partition uses about 480 mb, with the base delta gapps.

6. And I tried to switch from "Dalvik" to "ART" (in developer options), but after that, google play store services was shutting down all the time (with the above delta gapps). I tried to switch to ART, right after the installation of plain cm11 (without google apps) too, and was willing to install gapps afterwards, but scrolling was so horribly stuttering, so I decided to do a fresh and clean cm11-install without switching to ART.

7. I do not know, which modem-version comes with this build, because I replace it with XXLS8, right after installing the cm11-zip through the recovery. The original modem-version of this build could be mentioned in the start-post as well.
[Galaxy S II Android Development] zjq985062714:
because i use mobile phone now and my poor English,i can only answer the question of 1.2.7.other question will be answer after i test and verify it.

first:it is 0919build,i click and enter the Link,the file name is 0919.

second:i use default build chain,i don't change it yet,because i am a senior and busy for finding a job now.i was considering building with linaro,but the guide is too old to use.

seventh:cyanogenmod shouldnot change your modem version.
[Galaxy S II Android Development] ssanjy:
OK I've few things to add:

Regarding trim I don't think it's needed in cm11 but if you flash dorimanx for KitKat then you'll have trim, fpbug fix and IsoRec support and the kernel should run fine in the cm11 build.

I read that ART for KitKat is quite different than in later versions of Android and is buggy so I would suggest you not to use it
[Galaxy S II Android Development] almosely:
Thanks for your answers.

1. No, your uploaded cm11-build is not from september, only the filename is september. I have it installed and when I go to the preferences, I see build-date 19th august and security patch date is 1st august.

2. In my opinion, it is great that you do not use linaro, saber or uber. Please, do not change that.

3. I did not ask, whether cm11 does change my modem. The modem is saved in the system-partition. You can easily change it. But what I wanted to know is, which modem is shipped within your compiled cm11-version. The most cyanogenmods I tested (cm12.1, cm13 in different versions) had XXMS4. It would just be nice, to add this info in your starting post. I changed the modem to XXLS8 anyway (it's the best one for me).

4. Why should I don't need TRIM? Everybody should use this within every (TRIM-Bug-patched) Android-Version. I do not like Custom-Kernels. I tried several and all of them were buggy, laggy and not satisfying at all. I always got the best results in performance vs battery-saving with stock-kernels. As I said earlier, I gave Lanchons TRIM-Kernel a try and up to now it works fine with this cm11-build.

5. And regarding ART: That's what I experienced - and read on several websites (after I tried it). I am using DALVIK now, with 4.4.4, and I am not going to change that. ART worked fine, while I was testing cm12.1 and cm13, but with cm11 it's incompatible/buggy/laggy ...

6. BTW: I changed back from cm12.1 and cm13 to stock 4.1.2 (rooted), because 12.1 and 13 are so buggy and battery hungry and not even a single camera-app is focusing sharp (and I tried almost every camera-app in playstore and modified ones from xda too) - only Snapcam HDR (the paid one) is focusing sharp, only when I turn the Camera2-API on, but then, the app is totally buggy and useless. Till now, Snapcam HDR seems to work quite fine with this cm11-build (I haven't tested it that much, but I will do so the next days). The only downside till now is, that the brightness metering-modes are gone, with every camera-app (spot and center-weighted) - but that was the same with cm12.1 and cm13. Oh, and I changed back to a custum ROM, after I tried cm12.1, cm13 and went back to stock 4.1.2, because 4.1.2 was so slow and a few days ago my S2 freezed and I could not turn it on again (it was not booting anymore - I only saw the white Samsung-Logo forever and I could not get into the recovery either). That happend, while I only wanted to wake up my phone - and freeze. So I took out the battery for some hours, put it back in - and voila, I could at least get into the recovery and give cm11 a try (I did not test it before). Till now, cm11 aka Kitkat 4.4.4 is performing great, very battery-friendly, the cam seems to be working ... could be the best option for my S2. A second downside I could find (but it was the same with cm12.1 and cm13): The audio-quality is a little bit worse (less resolution, clarity) then with stock (and I use the best android-player available: Neutron Music Player - I tried almost every Music-app available). But I think, I can live with that.
[Galaxy S II Android Development] TriboDoP:
hi [MENTION=7787185]almosely[/MENTION]

concerning the baseband-version:

If you would have checked it before changing to XXLS8 you would have seen that it is already version XXLS8.,

Regards
[Galaxy S II Android Development] FreddieFrog:
Hi zjq985062714! I love this rom, but will there be an update soon with the latest security patches from Google? (stupid question from a noob)
[Galaxy S II Android Development] almosely:
Hi, TriboDoP,

and thanks for your information about the built in modem-version. Of course I could have done that, but I wanted to update the modem right after the fresh installation. I only was curious about the version and thought, that there are many informations about this build left in the opening thread (modem, cm11-version, compiler-chain, system-partition-size, TRIM, IsoRec). I think, everyone who is interested in this build would like to know about that. Mostly it is really hard to gather all the informations about a "project" within xda (by forum-searches), so it would be very helpful and nice, if the maintainer here would add that infos to the first post.
[Galaxy S II Android Development] zjq985062714:
new update will come soon:D
[Galaxy S II Android Development] zjq985062714:
i will add more information next build:)
[Galaxy S II Android Development] zjq985062714:
I test it and for the previous question,here is my thought:

1:you are right,it is 08.19 build.but i don't know why,i truly built it in 0919.and the next build will come soon.

2:i have answered you,and in fact,i will try to build it with linaro.thirty-party chains have a better performence.but take it easy,the build with default compliler-chain will still exist even though i build an version with other chain.

3:yes,my version is based on 04.09.2015 with latest code and security patches.it should be an nightly version.because i sync source code from cyanogenmod branch cm-11.0 which means nightly version,rather than stable whose latest is XNG3C as Lanchon built.But i noticed that the code was not changed too much.

4:I flashed the TRIM-kernel with IsoRec-support,but i don't feel clear improvement.now that Lanchon provide the kernel,it should work normally and have a better perforence.but i don't ask [MENTION=4141005]Lanchon[/MENTION] for an answer.and i don't know too much about "fpbug_patched",but seems it has fixed.

5:i will reedit my first post.thankyou for your reminding.

6:in 4.4.4,ART was only a experimental feature,i don't even use it.i think "Dalvik" should be better for our old i9100.i will test it in my next build.

7:do you mean which is better for the build?if so,i think each are suitable.because i use zslpe which is using in hongkong.
[Galaxy S II Android Development] almosely:
Thank you! :)

So, for me, security patches till august 2016 are fine. I just wondered what happend. After constantly installing my S2 since 4-5 months, I am happy to finally have found a ROM that is actually working fine for a daily use. Nice to hear, that you are updating the ROM.

Okay, so give Linaro etc. a try ;) I am glad to hear, that you will still provide plane google-builds. I am sharing my opinion with some other ROM-maintainers here, to not use other compiler-chains. For me, it is more important to have the reliablest and stablest system rather than one thats maybe sometimes a little bit more performing.

Yeah, very nice to read that your version is the last updated version which was released (04.09.2015) and not only the last version available at cyano-downloads (15.11.2014)!!! :) If it is "nightly" or "stable" is not important to me. I think, every custom ROM is a "nightly", ever ;)

You will not feel any difference with Lanchon's TRIM-kernel through the kernel per se. If you have used your system for a while (installed, deinstalled, copied, cached, deleted ...), than there will be "fragmentation", parts of the eMMC which will not be "given free" by android to be reused. That's the point, where TRIM comes in play. If you use the app Trimmer (fstrim) from Play Store, reboot after that, than this deleted areas are free to use again - but only if you are using a TRIM-enabled kernel. TRIM is introduced to android since v4.3 and a fixed part of it since than, but it was never built into cm11 - that's why one has to use Lanchons TRIM-kernel. TRIM was built into cm12.1 and cm13 (since 03.2016), so there is no need for Lanchon's kernels to use it (if you are using a build not older than march 2016). With a custom ROM, one has to TRIM manually (with fstrim command or with Trimmer-app), but with a stock-ROM (starting with v4.3), android will trim automatically every night while loading (at least, I heard so).

Here's where the FPBug is explained (by Lanchon).

Modems are mostly "regional things", I think. So, everyone using a custum ROM has to update the modem depending on his living area. But be aware to not update a modem with RIL included - that can brick a device. Only update modems without RIL-informations included! But, to release the same modems as cm12.1 and cm13 (for the S2), you could change the built in modem to XXMS4 - but you don't have to. Personally, I tried XXLS8, XXMS2 and XXMS4. My stock-ROM had XXLS8. With XXMS4 and MS2, my S2 got hotter and the battery drained more faster. So, I am using LS8 and that's fine.
[Galaxy S II Android Development] zjq985062714:
in my experience,cm12.1 also work fine in our 9100.but no one update it anymore.i build it too.in fact,linaro should work stable too,at least,for me.for modem,if i am right,it relates to your mobile signal strength.if you use wrong modem,it will always search for higher signal,wasting more battery,so just choose a good one.
[Galaxy S II Android Development] almosely:
What I was experiencing with cm12.1 (and cm13) was, that no camera-app worked, not the built in one, none of "all" the others, available. They all could not focus sharply. I think, that is caused by the new camera2 api, which was introduced in android since 5.0. But not only android 5.0+ is necessary, the hardware-drivers must support the new api too. And obviously, neither cm12.1 nor cm13 are doing so. One can test if the phone is "hardware-ready" for camera2 with the app Manual Camera Compatibility from the playstore. So, if a phone is not ready for camera2, all cam-apps are falling back to a legacy-driver-mode and that one does not function right. I found only one camera-app where I could force the using of the camera2-api (Snap Camera HDR), whereas all other apps automatically fall back into the legacy mode. With activated camera2-api in Snap Camera HDR I could take 100% sharp pictures, but the app got very unstable. It never took a long time (a few times focusing) until the app refused to take pictures at all, so I had to force close the app manually and start again. And sometimes I had no luck in taking a picture at all. For me, a smartphone is a digital camera as well and I cannot go without it - it has to be fully and reliable functioning. So, every cyanogenmod-version above KitKat is not working on a Galaxy S2, at least not for me and everybody who wants to use his camera.

The second reason, why I don't use cm12.1 and cm13 is because of the unreliable wifi connection. To be more specific, It happend a lot of times where I switched off the wifi but it still was turned on. I could not see that, neither within the status bar icons nor within the preferences. But within the battery monitor I could see that wifi was still on very often although I had it turned off. And no, I did not forget some settings. I turned off "always notify when an open wlan is available" and I turned off the google positioning service to "always use wifi, bluetooth etc. even it was turned off".

The third reason, why I do not use cm12.1 and cm13 is the battery consumption. I is really a lot higher than with android 4.1.2. And now, with 4.4.4 (cm11), the battery consumption is even less than with 4.1.2.

The fourth reason to not use cm12.1 and cm13 is that it is using too much RAM. And to manage that, in cm12.1 and cm13 ZRAM (a part of the RAM which is ZIP-compressed) was introduced. This not only slows down the device, it needs more cpu power and therefore mory battery too.
[Galaxy S II Android Development] TriboDoP:
Hi [MENTION=7787185]almosely[/MENTION]

Thanks for all your interesting Informations in this thread.

Regards

TriboDoP
[Galaxy S II Android Development] Rhod-Wulf:
I agree all your points.
[Galaxy S II Android Development] almosely:
May I ask what you have changed regarding the former build, except the filename? You do not change anything within cm11, right? And the security-patch-date is 1st august of 2016 too? So, this "new" build is exactly the same as the last one from 19th september of 2016?

And you could add the info about the exact latest code of cm11 too: 2015.09.04 - as you said earlier (because "latest code" is not really without ambiguity).
[Galaxy S II Android Development] zjq985062714:
in fact,the op don't edited completely.i was thinking edit it today.i truly do not change anything.from the ROM build.pro,i get the security patch date which is same as 0819 build,like 0719 build security patch is 0624,doesn't change.if you read op carefully,you may notice i said i sync code before i build it,which means the code is 10.19.Practically speaking,the difference between the 1019 build and 0819 build is depending on the developer,if they change the code,they are different,if not,they are same,that is why i think about giving change log.
[Galaxy S II Android Development] almosely:
I read that you do not change anything by yourself within cm11 and thought that the developing of cm11 for our i9100 stopped in september 2015 too. So when the security patch date is also the 1st august of 2016, then why do you compile and release a new build? Whether you are pulling the code from github on 19th october or 19th september it is always the same as september 2015, isn't it?

I do not know much about github but I found two URLs, where you could possibly pull the code for your builds:

CyanogenMod/android_device_samsung_i9100 - latest commit on 4 Sep 2014

CyanogenMod/android_device_samsung_galaxys2-common - latest commit on 23 Aug 2015

So, and - as far as I understand that - the latest commit is the latest change, isn't it? So, nobody changed anything since 23.08.2015, right? Or do I understand that wrong or do you pull your code from another place?
[Galaxy S II Android Development] zjq985062714:
everything you say is right,and i know,these two project is stop updating,but i don't check something else,like setting,framework etc and there are some code may change for optimization in some other place.And in fact,i sometimes doubt the meaning of this new build,but i notice that the md5 is different which means something changed,if they are same,the md5 should be same,am i wrong?
[Galaxy S II Android Development] zjq985062714:
bytheway,when i synchronize code,i notice something was downloaded because my net speed will reach a very high value like 800-900KB,then reduce to a low value.so i think something was changed but i don't know what it is and is it for our i9100.
[Galaxy S II Android Development] almosely:
I don't know that much about setting up and compiling a new build, so to explain that, it would need someone else :(

... but you are pulling your cm11-code from the newer github-branch, the one with commit on 23 Aug 2015, right?

Yes, I tested the md5 of your new build too (yesterday) and it is different from the last one. I don't know why.
[Galaxy S II Android Development] zjq985062714:
i also don't know too much.yes,i pull code from newergithub-brunch.
[Galaxy S II Android Development] adxamg:
Just delete "out" dir, before you next time start a new build -> rm out -r

You will get a fresh build with actual sources. Parts of your build are not up to date when you don't delete it.

There where many changes (security patches) in cm-11.0 branch on Oct. 24. Also patch level was set to 01.10.2016 there.
[Galaxy S II Android Development] zjq985062714:
but,when i check the change log,i notice that the string of patch level in framework wasn't changed.it just said someone change patch level to 2016.08,not 2016.10
[Galaxy S II Android Development] zjq985062714:
new build has uploaded.
[Galaxy S II Android Development] TriboDoP:
Thanks once more for keeping kitkat alive and updated!

Regards!