yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Lysergic Acid:
Of course, I'm already aware of the changes I'll have to do to get 6.0 support, so things will be quicker than it was with CM12 ;)

ATTENTION EVERYONE:

In order to fix the "wipe data" issue on the cyanogen recovery, I had to move the encryption key that was stored in /efs/metadata to the /data partition itself, on the footer of it. So I'm pretty sure that will force anyone using encrypted phones to wipe their data to get the phone working on the next nightly. I'm not sure about non-encrypted phones, might not have problems at all. Just be cautious when updating to a newer nightly, I'm sure most of you know how to be cautious.
[Galaxy S II Original Android Development] thegangsta:
Does device encryption work? Last time I tried it didn't.
[Galaxy S II Original Android Development] laserkater:
Same here, last time I tried, it didn't work. Also messed up my update from encrypted Kitkat to (ergo unencrypted) Lollipop, I assume.
[Galaxy S II Original Android Development] ran000:
Today nightly looks ok here.
[Galaxy S II Original Android Development] Pa9an:
What is with the 3 "DO NOT MERGE" items in today's Nightly's changelog that seem to have got merged?

Should I better hold off on upgrading today, as they might be removed again tomorrow for maybe a good reason?

sqlite: upgrade to SQLite 3.8.6.1 - DO NOT MERGE (android_external_sqlite)

DO NOT MERGE. Truncate and ellipsize app name if too long for dialog. (android_frameworks_base)

DO NOT MERGE Fix security vulnerabilities in permission of deleting MMS/SMS (android_packages_apps_Bluetooth)
[Galaxy S II Original Android Development] Dr.Fix:
Yes, I noticed the same... I prefer to wait.....
[Galaxy S II Original Android Development] maro777:
Uploaded last nightly 1006 and it seems that everything is OK.
[Galaxy S II Original Android Development] Weib67:
Hi LA,

Always nice to have news from you. :)

Btw, is there any plan to fix backup issue in stock recovery ? I’m not asking for any ETAs, but I think that this feature is very important when it comes to flash nightlies, frequently or not. For the moment, the only alternative is the TWRP kernel you provided more than a month ago.

So, I would like to update to latest nightlies, but it would be better with an updated TWRP in order to do so. Some changes has been made to the official kernel since 25/08, right ?

Thank you. :good:
[Galaxy S II Original Android Development] Weib67:
Lol man, you're sending me to the very post I just quoted.:silly:

You obviously did not understand what I was talking about. :p
[Galaxy S II Original Android Development] Kurt Krummbein:
I guess "wipe_data" is first on his list, it's #1 of the bug-reports on this list ;).
[Galaxy S II Original Android Development] Weib67:
I was talking about the backup issue, not the wipe data one. ;)

Btw, I'm on 02/08 nightly on my second i9100, and already 100+ hours of uptime. Looking good. :)

Finger crossed for the next updated twrp to be released. :good:
[Galaxy S II Original Android Development] Lysergic Acid:
I'm crazy

I've made an attempt to build pure AOSP 6.0.0_r1 directly from Google to our device, well I managed to bring up the device tree in the process, as well as fix tons of errors from our Samsung blobs, but it doesn't boot. If you flash a kernel like [MENTION=414800]arnab[/MENTION]'s AOSP kernel over it, you'll get past the Samsung logo, but bootloop. Logcat says vold keep dying from libc errors.

If someone is interested in the files or wants to mess with it for some reason, here's the zip, at the moment I made it flashable from twrp: https://www.androidfilehost.com/?fid=24052804347831974
[Galaxy S II Original Android Development] vdZERO:
Sorry if it was posted before, couldn't find it.

Can you please tell me what xposed file I need to install for it to work on 5.1.

Thank you.
[Galaxy S II Original Android Development] arnab:
u need to backport important commits for vold .. these are the most quintessential important commits 1 & 2

Other than that ... u need important files in system_core init folder ..hardware_libhardware...broadcomm_libbt & system_vold...other files like LPM (offline charge) is also needed to be put in android.mk of init folder in system_core.
[Galaxy S II Original Android Development] Lysergic Acid:
I know what I would need to do, AOSP is just a waste of time for now, we need to properly update all the hardware/samsung repo first.
[Galaxy S II Original Android Development] arnab:
Ya right. else those RIL bugs might be back.

---------- Post added at 01:42 AM ---------- Previous post was at 01:38 AM ----------

And moreover we need M to be mainlined for release else its just dumb nexus now with only qualcomm patches and no proper exynos implementation.

---------- Post added at 01:42 AM ---------- Previous post was at 01:42 AM ----------

And moreover we need M to be mainlined for release else its just dumb nexus now with only qualcomm patches and no proper exynos implementation.

---------- Post added at 02:09 AM ---------- Previous post was at 01:42 AM ----------

And moreover we need M to be mainlined for release else its just dumb nexus now with only qualcomm patches and no proper exynos implementation.
[Galaxy S II Original Android Development] makix13:
Take a look here and post in the right thread

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

Keep this thread clean for rom discussion [emoji6]

S2 LA Cyanogenmod 5.1.1 [unofficial] [06/17] - Xposed [unofficial romracer's framework] - [rovo's beta 4 apk] - Viper4Android
[Galaxy S II Original Android Development] vdZERO:
I'm sorry for OT, just wanted to know what what type is our S2, arm, or x86.
[Galaxy S II Original Android Development] p3dboard:
The s2 has an arm processor. Exynos 4210 from memory.
[Galaxy S II Original Android Development] Zentori:
Anyone has achieved this? Is the only thing I miss in this phone, a notification light.
[Galaxy S II Original Android Development] xhoster:
Check out the dorimanx kernel thread. If nothing has changed it should have that feature.
[Galaxy S II Original Android Development] d_j_l:
Will this effects the phones with mod pit? http://review.cyanogenmod.org/#/c/110854/
[Galaxy S II Original Android Development] cherryb8844:
My god

Really

That was a great news for me and s2 user my phone never gonna old haha BIG THANKS TO [MENTION=6159291]Lysergic Acid[/MENTION] AND XDA :D
[Galaxy S II Original Android Development] Linskun:
Anyone have proximity issue with official CM12.1 ?

It work without problem with CM11,NeatRom,Chameleon,Original but with CM12.1 after a while it stop working

On Z-Device tester it show always 0,0000 cm, on call it never turn off display until reboot
[Galaxy S II Original Android Development] Mikros:
I have the same issue and i saw it some hours ago. No matter what i do proximity sensor does not work and before upgrading to cm12.1 everything was working fine.
[Galaxy S II Original Android Development] LeBourrin:
I never meet proxymity sensor bug with my phone. I'm on stock kernel.

---------- Post added at 04:57 PM ---------- Previous post was at 04:55 PM ----------

Last time I tried DorimanX kernel, it can't make work the notification led. So for now, no kernel can do this :(
[Galaxy S II Original Android Development] Spyr0s:
no
[Galaxy S II Original Android Development] madmax00:
You can try with NoLED, it's not the same as BLN (Back Line Notification), but it does the trick for me
[Galaxy S II Original Android Development] Lysergic Acid:
About snapshot

I want some opinions here now, I'm seriously thinking about signing-in our device to get the next CM stable build, I'm even working on some commits for more stability. Do you guys think we are ready to get in the next CM-12.1 snapshot? It's a bit of responsibility on my side, and some opinions would be nice.
[Galaxy S II Original Android Development] king_ahmed:
go ahead we trust you :good:
[Galaxy S II Original Android Development] nhmanas:
An idea about power saving mode [MENTION=6159291]Lysergic Acid[/MENTION] 200 mhz is not enough for operating. I think scaling at 500 or 800 is good for everyone.
[Galaxy S II Original Android Development] Lysergic Acid:
That mode is not made to be usable indeed, it's for when you're low on battery and it should last the rest of the day or something. Good point tho, make it less laggy shouldn't harm.
[Galaxy S II Original Android Development] ouzowtf:
I got some spontaneous reboots more since two or three weeks or something like that. So stability is very welcome.

But I can't decide if this should stop you from a snapshot release.
[Galaxy S II Original Android Development] nhmanas:
Btw I know you already know this but just a reminder. 200mhz and 500mhz is using same voltage value (stock) 950mV :D so it is not harmful for battery too
[Galaxy S II Original Android Development] Zile995:
Wrong :) 500MHz uses 975mV :)
[Galaxy S II Original Android Development] Lysergic Acid:
Well I never actually had random reboots in CM12/12.1. All I got was logs from people reporting this, really, even if I forced the phone it didn't reboot lol

I'm thinking about the freeze issue mainly.
[Galaxy S II Original Android Development] Spyr0s:
no, many users still report random reboots and freeze
[Galaxy S II Original Android Development] Zile995:
I don't have random reboots... I have freeze issues.
[Galaxy S II Original Android Development] steph3003:
i had random reboots AND freeze, it's very unstable (i tried Dorimanx, Samsung stock, Cyanogen stock kernels and i think even other, most of the time Cyanogen)

i use only few apps, but everyday usage is still a nightmare:

- spotify (many freezes, some unwanted reboots)

- telegram (MANY freezes and MANY unwanted reboots too)

- google maps (oh-my-god impossible to use it. and phone freezes/maps crashes at easy time. i had to use web-app or waze. thanks god, never had to force reboot)

- whatsapp (sometime freezes, especially with many notifications. always force reboot)

- facebook (ahahaha. so slowly. uninstalled, impossible to use on a galaxy 2 nowadays)

- messenger (same)

- facebook lite (never froze. but it crashes sometime)

- shazam (sometime freezes. fortunately, don't have always to force reboot)

- instagram (very unbelievable, but this can run on a galaxy 2, as opposite to fb/msn. never froze or maybe once, but i don't use it very much)

- x-plore (if i remember correctly, it froze only once)

- youtube (i don't use it very often on smartphone, but it can't really run long videos. on >30', it becomes unstable, freezes very likely and have to force reboot -if it don't reboot itself, already)

- adaway, google keep (maybe one freeze), and others: nothing relevant

almost any freeze (a part from shazam) can't be killed: nor "task manager" or long-pressed back button work.

this is my situation on first week of september. after this, i returned to stock (that is very slowly, and have some crash on heavy processes, like every samsung phones always does on massive usage). i don't know if something changed on these days, but to me it seems very unstable and it's too early to have a snapshot.
[Galaxy S II Original Android Development] Lysergic Acid:
TWRP

Updated the Stock Kernel + TWRP zip to October 9th sources in OP, link is: https://www.androidfilehost.com/?fid=24052804347833059.

Regards
[Galaxy S II Original Android Development] nhmanas:
Sorry ur right but 25 mV don't make a big change

---------- Post added at 06:13 AM ---------- Previous post was at 06:07 AM ----------

I was having this issues too and they were very annoying. So I buy greenify donation package and greenified almost everything! (Notifications still coming on donation package) But that wasn't enough. Still freezes. I edited minfree values via kernel auditor. (Aggressive) and now it looks OK to me :D
[Galaxy S II Original Android Development] vdZERO:
Do you mind sharing the values edited? thanks
[Galaxy S II Original Android Development] nhmanas:
Agressive: 8,16,32,64,96,128

Very agressive: 16,32,64,128,192,256

Test it and choose which you want. I am using aggressive now.

Btw I have ~450 mb free ram
[Galaxy S II Original Android Development] eminem_b:
I'm up for taking it to a snapshot.

Although, I saw that you're considering giving zRAM a try.

Our device just OOMs all the time and this whole process of clearing memory constantly just to make a simple activity pop is killing the battery.

The above is not our fault, apps just keep getting bigger and more RAM-hungry, so it's inevitable.

One or two pages back, someone said that he has 430 MB of RAM free. I don't really believe that.

I have like 30 or 40 at max and they are probably always kept like that from the system for availability. Otherwise, they would have been filled too.
[Galaxy S II Original Android Development] Dr.Fix:
After days of no iusse, yeasterday I installed 20151008 from 20151003.

I left the phone on my desk for some hours, with no app open, everything killed from task manager.

When I looked back to the phone it was showing the boot logo (that blue cyanogen alien face).. stucked.

I think it reebooted itself for some reason that I don't understant, since it wasn't doing nothing and, even more strange, it feezed at boot.

Kept the power button pressed, turned it off and on again. It started normally.

Strange things happening here.
[Galaxy S II Original Android Development] Fr4nz83:
[MENTION=6159291]Lysergic Acid[/MENTION] , well, I suppose the problem with replicating these issues is to keep the telephone running for a sufficient time (> 24h) and use it for browsing/facebook/etc...in these cases the freeze/reboot issues can be met on a daily basis. Too many users are reporting these kind of problems to be just a mere coincidence.

Anyway, for what relates to my personal experience I find the current nightlies pretty stable - had uptimes up to 48h.

My suggestion is to focus on/investigate these problems before releasing a snapshot :)
[Galaxy S II Original Android Development] Linskun:
My proximity sensor now

And after reboot

Default kernel, same problem with all nightly
[Galaxy S II Original Android Development] jholstein:
+1

I also get this exact behavior nearly every night when the phone is in airplane mode and doing nothing except showing clock while getting charged.

Not for snapshot yet...
[Galaxy S II Original Android Development] Dr.Fix:
Just to give a complete scenario, my phone wasn't in airplane mode nor charging.

Since I use it as alarm clock in the morining, I use to reboot it every night before going to sleep just to restart it and clean it up...
[Galaxy S II Original Android Development] p3dboard:
I also can get that large quantity of ram free at times, but I am using the Greenify App running in root mode to put applications to sleep, the other guy is probably doing something similar, so we are not allowing the apps to behave as the normally would, staying in Ram, and I only launch them when I need them, after they close, greenify puts them back to sleep. For myself, I feel this gives me better performance and longer battery life.
[Galaxy S II Original Android Development] essenov:
Some hours after I installed nightly 20151008 the phone got frozen on video play. I rebooted the phone and it stuck on the samsung logo. I was not able to boot into Recovery. Download mode was working, so I tried flashing stock ROM from sammobile through ODIN, but it failed few times. Now I cannot even enter the Download mode. I'm not sure if the battery still has a charge, but there is no logo when I plug it to the charger. I most probably have a brick now.
[Galaxy S II Original Android Development] maro777:
In my latest nightly in 1009 running ok so far no problems.
[Galaxy S II Original Android Development] ringen00:
I'm using 'cm12.1-kernel-22-06_gustavo'.

Random reboots!

When downloading the phone becomes very very slow!
[Galaxy S II Original Android Development] Weib67:
SELinux on permissive

Thank you LA. :)

However, flashing the zip switch SELinux to permissive state. Is it normal ?

Anyway, I hope that the dlmalloc solution on today’s build will help with general stability. Testing from now. :)
[Galaxy S II Original Android Development] steph3003:
I forgot to tell, I used to run the very popular-but-I-think-not-useful "Clean Master phone boost" from the Play store (that is almost a sort of Greenify without root access), but it didn't show very stable. freezes and reboots still shown up.

I also used the "Romtool box lite" to freeze every system app unnecessary to me, and I didn't flash all the stock Google apps (but only micro or something like that package, I don't remember)
[Galaxy S II Original Android Development] n3m3sis:
Okay, I rooted my Samsung GT-i9100 on 23/09/2015 for the first time and installed the official version of LA 12.1 rom.

I was pleasantly surprised as there seemed to be very little issues at all, in fact I have held off buying a new phone since I installed the rom as I was so pleased with how it was running(except netflix everything else worked). I started installing the nightlies on 26/09/2015 and so far very little problems indeed, on or two random reboots but buy and large everything working as it should and much faster than the stock rom. My first real issues came when I installed cm-12.1-2051008. It made my phone freeze a few times and my mx player would no longer play videos (mp.4) on the hw or hw+ decoder, giving a choppy playback - software decoder was fine. I reverted back to cm-12.1-2051006 and freezing stopped but mx player remained the same. I have updated now to cm-12.1-2051009 and everything seems ok except mxplayer..still choppy. I can use software player for now though until one of the nightly's fixes it again.

LA , I am in awe of the work you (and others) have put into this rom as it really has given my aging SII a new lease of life( and save me some money to buy a new phone). Thank you very much!
[Galaxy S II Original Android Development] ringen00:
Hey! Did the same as you (Greenify+ Kernel Adiutor).

Then updated nightly with CyanDelta.

Now I'm stuck on boot animation...! ! !

Maybe because I didn't reboot after Kernel Adiutor demanded that to take effect? Started the CyanDelta update instead.

What shall I do?
[Galaxy S II Original Android Development] Fr4nz83:
Yeah, I also noticed the introduction of the dlmalloc usage.

So far no problems (5h uptime) and the phone seems faster too! :D

PS: If someone is interested in knowing what is dlmalloc, here's a nice article:

http://gameangst.com/?p=496
[Galaxy S II Original Android Development] Lysergic Acid:
I've been using the phone as a daily driver for months on CM12, no reboots, cannot be a coincidence too ;)

I'm doing my best to get it to a more stable condition, we still have 2 or 3 weeks before the sign-in for stable closes.

I probably let this pass, it wasn't my intention :o

Anyway, you won't have SELinux problems now lol
[Galaxy S II Original Android Development] Linskun:
Me too, no reboot here.

But i suggest you to investigate to proximity problem that i have sometime as reported some post ago.
[Galaxy S II Original Android Development] Fr4nz83:
[MENTION=6159291]Lysergic Acid[/MENTION] Well, it also really depends one the usage of your phone...for example, how much is its average uptime? Also, how do you use it (intense browsing, watching videos, etc.)? Many users pointed out that the issues arise whenever the phone is - somehow - intensely used :)
[Galaxy S II Original Android Development] Mr.cyrux:
Uptime over 250 hours, browsing, watching videos, phone calls - everything works pretty fine.

i love this ROM :P
[Galaxy S II Original Android Development] nhmanas:
I did exact same thing today. Yesterday I've done kernel auditor and greenify things and today I've updated via cyandelta. But no I was not stuck on boot animation.

Did you wait at least 10 minutes to boot? Because dalvik cache has been wiped after every update.

And do you have xposed?
[Galaxy S II Original Android Development] Lysergic Acid:
I normally used it for 2 or 3 days at max without powering the phone off. Changing between youtube, chrome, whatsapp, telegram, hangouts and gmail is my most common usage. Of course OCD makes me clean the recents all the time but it shouldn't be necessary. Looks like the ooms are related to those reboots for some reason, I'll try to enable zRAM and see how it goes.
[Galaxy S II Original Android Development] azunino:
I use my i9100 for light apps. No facebook/whatsapp... so no problems. No random reboots for many weeks. I use greenify and tk pico gapps. The *only* problem IMHO is the hardware... RAM is not enough for typical apps, but the ROM is perfect considering the hardware constraints. So... IMHO it is stable.

Good work LS!
[Galaxy S II Original Android Development] Lysergic Acid:
Indeed RAM is a problem, I tested CM 12.1 on a 2014 device with 1gb of RAM, and got launcher redraws on it.
[Galaxy S II Original Android Development] Fr4nz83:
[MENTION=6159291]Lysergic Acid[/MENTION] Anyhow, so far with dlmalloc no problems...let's keep the fingers crossed :)
[Galaxy S II Original Android Development] vidara:
I had these issues for months on cm 12 and 12.1, but they seem very sporadic. My i9100 has been degraded to a night watch and alarm clock. So it mostly sits still in a dock on a table. The freeze can happen without any interaction. Sometimes it can go months. I do however suspect hardware related issue, without any facts to back it up, possibly from bad ram after much wear. I guess the only way to find out that hypothesis is running some ram diagnostics. Not sure what tools are available for doing that on a phone done.

On the topic of dock support, I see no difference with the latest patches and how it's been working for months. It works just fine. There is one issue though. Backlight on the buttons doesn't turn off when the phone is docked and displaying the daydream clock.

Btw. this phone really deserves M ;) except for proprietary blobs, this phone has really stood against the tide of time. Can still play modern heavy games on it! But this is thanks to you Lysergic, you have proved that phones have a long life and that manufacturers are wrong in not supporting their devices longer!

Thanks for a great job with this rom! :D

- - va
[Galaxy S II Original Android Development] Fr4nz83:
Probably you meant the worning-out of the eMMC (flash) memory (not the actual RAM) on which /data, /system, /cache, etc. partitions are stored, correct? Anyway yes, I think that could be a possible candidate explaining the freeze/reboot issues - especially for what relates data going inside the /cache partition.

In theory it is possibile to check the eMMC by using "e2fsck", which can be accessed via ADB. I did use it once for checking the /data partition (didn't find bad blocks). Perhaps I should check the entire eMMC - due to the way the blocks are managed at hardware level - in order to find bad blocks...will report about any finding later.

EDIT: it seems all ok, used e2fsck with the "-c" option...however, I guess if e2fsck is powerful enough for finding out bad blocks, since the eMMC manages the bad blocks at hardware level...

EDIT2: For testing the eMMC integrity I also found this app => https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=it
[Galaxy S II Original Android Development] ringen00:
Yeah! I've been waiting long enough :)

Using Xposed (Greenify).

Any idea how I can make it work again?
[Galaxy S II Original Android Development] vidara:
I actually did mean ram. I have experienced bad ram making systems hang up for no reasons. But this is of course just guessing on my part with regards to this issue and should be ignored until backed up with data.

With regards to flash memory, Samsung doesn't really have the best reputation when it comes to their emmc controllers. Seen reports of systems lagging when storage space dips below a certain level being an issue in the past for some phone.

Bad sectors would probably cause a phone to slow down, but wouldn't those be detected and marked bad by ext4 in the kernel? It is probably worth checking out though. Will try out your suggestions the next time. :)

-- va