yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] p3dboard:
Yes, still occasionally getting this. Our two I9100, had this on 04/20 and 04/26 builds. Doesn't happen every time, but wiping the Davilk and Cache gets it out of this boot loop / long boot. Sometimes there's a random reboot and this happens, other times its happening at boot after the phone has been powered off.

This issue wasn't present on the previous Android 7.1.1 builds. Hopefully the solution can be found soon.
[Galaxy S II Android Development] Skyline:
Anyone tried 29/04 build ??

I tried it with full wipe but it bricked my device. Device gets stucked at bootlogo and I was not able to boot into recovery mode. If anyone going to upgrade to latest builds take a complete backup.
[Galaxy S II Android Development] w1lh3lm3d:
Is it a.bug vor really no change in the latest build? THX at all.
[Galaxy S II Android Development] MigoMujahid:
You can check the changelog, if we don't feel the changes, that doesn't mean that it's there.
[Galaxy S II Android Development] w1lh3lm3d:
I die but there was nohing until the 30. today is a lot oft changes and now its fixed. Thx you all.
[Galaxy S II Android Development] melkozerov:
Good day dear. The first problem appeared after upgrading 29.04 30.04 and 01.05. After that, I all apps would fail. Helped only a complete WIPE and format system. But after a rollback on 26.04, I was unable to install the updates. very long download and the phone was very hot. Today did full WIPE and format system. Installed the upgrade from 02.05. Now there is a restore apps from GOOGLE account. I am sure your recovery will go fine
[Galaxy S II Android Development] melkozerov:
All recovered
[Galaxy S II Android Development] lexus46:
How do you make an update (upgrade, like you wrote)? You don't need to wipe everything. Just flash the new build and wipe ONLY cache and dalvik. Doing so you don't have to restore your apps and settings, they remain the same like before. Full wipe is needed only when you change from a particular rom to another or when upgrade from Marshmallow to Nougat.
[Galaxy S II Android Development] melkozerov:
I wipe cache and dalvik, wipe data, format system.

When I can't install the ROM I do these steps. Formatting of system section, I get rid of all remnants of the old system. But in my opinion it is not necessary. You quite clearly describe what happens. I'll try follow Your recommendations. Thank you very much.

---------- Post added at 11:52 AM ---------- Previous post was at 11:24 AM ----------

How to make an update 03-05. Wipe cache and dalvik. Veryyyyyy long boot logo. I waited a very long time. Back again 02-05

---------- Post added at 12:00 PM ---------- Previous post was at 11:52 AM ----------

"Just flash the new build and wipe ONLY cache and dalvik"

If I understand correctly, I need to do wipe cache and dalvik after installation new ROM? Is not it?
[Galaxy S II Android Development] lexus46:
That's right. After flashing TWRP gives option to wipe cache and dalvik. Than reboot. After flashing a rom (or update) first boot always take a long time. You can force it by holding power button until the phone turns off (or take the battery off) than press again to turn on. Usually the second boot takes shorter time.
[Galaxy S II Android Development] MigoMujahid:
Order won't really matter, for me i wipe after most of the times, some times i wipe before and after..:rolleyes:
[Galaxy S II Android Development] linusdan:
I was comparing the build 02072017 (no magisk included) with the current (with magisk included). 1000x faster with no magisk!

Then I asked myself: Was it a good idea include it even with the features offered? Maybe not.
[Galaxy S II Android Development] melkozerov:
I think we initially gave more control of the system using magisk. Everyone has to decide for himself. If someone does not like this feature , it can simply be REMOVED.
[Galaxy S II Android Development] GreekDragon:
Seems we have problems after we got 7.1.2 merged. I will try to fix them.

By the way, since our device doesn't get much device updates, i decided to move it to weeklies, less stress for our server.

So..Monday.
[Galaxy S II Android Development] lexus46:
Besides, as I understood, Magisk won't work with S2.:crying:

Anyway, I think we reached our S2's extreme limits with Nougat. Too many problems, the devs solve a problem and suddenly appear three others. Lollipop and Marshmallow developing was far easier, I think.
[Galaxy S II Android Development] linusdan:
Yeah! I fully agree.

Too I think we reached our S2's extreme limits with Nougat.

I think the future is to fix what does not work well and improve some things to get the final version.

From what I've tested since March:

1. Which does not work well:

- Camera in mode filming in applications that offer this feature for use (instagram, snapchat, facebook etc)

2. To improve

- Battery friendly

About magisk: lexus46 already said what I was going to say :o

I think it would be better the user to have the superuser on the traditional mode #SuperSU.zip# or some other tool for that.
[Galaxy S II Android Development] MigoMujahid:
SuperSU system mode zip should be working good here, it needs a permissive kernel and we have it.
[Galaxy S II Android Development] p3dboard:
Hi Guys, I have been using Lineageos for a few days, and it feels a lot smoother than the latest aicp builds. Its zram settings are around 260mb, aicp is at 400mb. Also lineageos doesn't seem to be suffering from the reboot / long boot bug. I am on the 2017-04-19 build. I was sticking with Aicp, but since i use the phone daily, aicp at the moment was a bit to unstable and could quickly drain my battery if it rebooted and got stuck on the long boot.

Lineage os is also Android 7.1.2, so i was also thinking maybe it is to do with the change in governer to Peagesus that could be causing the problem. Not sure at this point. Sometimes a reboot would happen when installing or uninstalling an app on aicp.
[Galaxy S II Android Development] linusdan:
SuperSU works very fine!

I use and i have no problems.

I am in favor of his return as standard on the I9100.
[Galaxy S II Android Development] Nobby1960:
I agree, the 7.1.1 builds from "pre Magisk era" with the built-in root are IMHO the fastest Nougat ROMs on our device. The reason why I am on AICP 12.1 is very simple: It has volume steps, they are important for me and the brightness for ambient display is adjustable. I did changed the older, more buggy camera app (Snap.apk) with the latest one.
[Galaxy S II Android Development] lexus46:
I agree, but I think all those who are trying AICP, RR or other custom roms want more customization options.;)
[Galaxy S II Android Development] bujjo53:
Hello i got my s2 back , latest build of AICP 12.1 it's stable or not ?
[Galaxy S II Android Development] Nobby1960:
No, it isn't. But [MENTION=5651185]GreekDragon[/MENTION] will try to fix it, see here .
[Galaxy S II Android Development] MigoMujahid:
A new build was released yesterday, i haven't tested it yet, but maybe he fixed it there.
[Galaxy S II Android Development] w1lh3lm3d:
Its running very stable since Monday on my phone
[Galaxy S II Android Development] MigoMujahid:
Great, thanks for the info :o:good:
[Galaxy S II Android Development] Yakap:
Clean install or dirty? Thanks
[Galaxy S II Android Development] MigoMujahid:
Dirty flashed, i was running 27th April build before that one.
[Galaxy S II Android Development] bujjo53:
Flashed latest build it's soo smoother ?
[Galaxy S II Android Development] linusdan:
My tests with build 05082017 with opengapps 05102017 installed (clean instalation)

1. Camera in filming mode works, however, when saving the file, the video does not run because the gallery says is corrupted.

2. .m4a music files do not run in both the native app and other music players (LineageOS and XenonHD work normally)

3. App Recorder does not work for audio and screen recording (Tip: why not replace with the app sony audio recorder to record audio and AZ Screen Recorder for screen recording? Or ... let the user choose =D)

4. Magisk does not work and is not uninstalled with the magisk_uninstaller.zip file.

5. SuperSU is installed with the flash file, but does not grant root and consequently the manager does not appear in the application menu.

6. Apps that grant the option to shoot do not work (ex: instagram and facebook freeze the footage when starting the recording).

Video demonstrating problem 6 (it was in LineageOS build 03052017, but the same thing happens with AICP ROM): https://youtu.be/_dOn4ROeV1E

I wanted to demonstrate the recording of the video in the ROM itself, but as there is this video problem and I do not have a camera, it had to be this video.

The rest works very well =)

Battery friendly very good!

Thats all folks

[MENTION=5651185]GreekDragon[/MENTION] , sorry to bother = D

Thanx =D
[Galaxy S II Android Development] Nobby1960:
You make me curious, I have to compare it with my old build ;).

---------- Post added at 01:16 PM ---------- Previous post was at 01:12 PM ----------

Thanks you for your detailed report - I think, Magisk will never work with the S2 because of its outdated boot image.

Edit: I confirm, video recording works, but the gallery plays no video. On PC the video file works fine, it's not corrupted. I did changed the gallery with the older one, no effect. Something wrong with decoding?

Edit 2: I had installation problems (totally clean flash) - crashing GApps, boot loops, app crashes. No idea why. After a few tries it works fine now. The ROM runs really smoother than the earlier builds. That's good.

All videos don't work, not only new recordings. Seems this is a decoding issue.

Edit 3: Always boot loops sometimes, if I restart the phone.
[Galaxy S II Android Development] GreekDragon:
Hey guys, new test build for everyone. Please test and report back, i need to know if that "long" boot exists or no. I tried 24 reboots and none of them were that long.

Download
[Galaxy S II Android Development] linusdan:
Happened to me 2 days after installing the previous build (installed as soon as it was released on the downloads page). It took 5 minutes to start, i found strange. On other occasions started normally, it took 1 minute to start.

I will test the new build and return with feedback.
[Galaxy S II Android Development] linusdan:
[MENTION=5651185]GreekDragon[/MENTION],

I rebooted 13 times + 3 times off / on.

Gapps 05102017 installed.

Test time (Restart):

AICP test 1 - 00:35:55

AICP test 2 - 00:31:48

AICP test 3 - 00:36:96

AICP test 4 - 00:36:07

AICP test 5 - 00:31:37

AICP test 6 - 00:31:85

AICP test 7 - 00:31:96

AICP test 8 - 00:32:22

AICP test 9 - 00:37:17

AICP test 10 - 00:32:86

AICP test 11 - 00:31:30

AICP test 12 - 00:37:27

AICP test 13 - 00:30:88

Test time (OFF/ON):

AICP test 1 - 00:36:71

AICP test 2 - 00:36:18

AICP test 3 - 00:35:75

My variant is I9100XMMS2 (I do not know if it influences)

I think it's the previous boot animation that's giving trouble.
[Galaxy S II Android Development] MigoMujahid:
WOW, a lot of effort there :eek: :eek:
[Galaxy S II Android Development] linusdan:
I tested it again, now with VLC on android. The video worked normally and the .m4a files worked as well.

It really problem decoding with the .m4a and .mp4 files.

On my notebook with Arch linux I had tested the video with the parole media player (ffmpeg was not installed). I installed what was missing and it played normally, not only the video of the phone, but of the notebook too =)

The screen recorder now works with this test build =)

Summary of opera: Just correct the errors of decoding videos and audio in .m4a format to stay perfect (think it's this) :highfive: :laugh:

I feel the smell of AICP Nougat stable coming soon <3
[Galaxy S II Android Development] Lughsen:
Mean values

48s in a full reboot time

36s since Samsung logo disappear

Stock kernel. No Gapps
[Galaxy S II Android Development] MoixyS2:
XenonHD is good Rom? Personalizations and bugs please?
[Galaxy S II Android Development] Nobby1960:
XenonHD I don't have tested. If you are looking for a really stable Nougat ROM, then read my posting completely through. I've been using it as a daily driver. You need no separate SU to root, it's built in. Try it out.
[Galaxy S II Android Development] linusdan:
With XenonHD, you have what the user actually uses. It is stable for daily use, it flows well. Substratum works fine in the last build. SU is already comes activated. What bothers me in XenonHD is the launcher Nova as default.

Bugs found:

Filming mode in apps like instagram and facebook not working properly.
[Galaxy S II Android Development] Nobby1960:
I did just tested the build 05/15 from yesterday. Boot loops, long boots (I had the blue boot logo) and the video decoding problem are still present.
[Galaxy S II Android Development] Skyline:
Kernel Bug

Hello [MENTION=5651185]GreekDragon[/MENTION], did you checked Virtual Memory settings when selinux is permissive. It seems to mess'd up. First, I thought it's the problem with my kernel but now I think that's not true. Plz take a look at it if you get some time.
[Galaxy S II Android Development] linusdan:
[MENTION=5651185]GreekDragon[/MENTION], i tested the build of the day 20170522.

Boot loops, long boots disappeared with the new boot logo!!!

I noticed that the boot is faster compared to the test build (25-30s with the current x 35-37s with the test build).

Changes needed to make the build stable:

- Video decoding problem (.mp4)

- Audio decoding problem (.m4a )

- Fix filming mode issues with app integration as demonstrated in the video

- Root not working with supersu.zip

I wanted a lot to help, but I do not know half the half of the knowledge needed to encode (yet)
[Galaxy S II Android Development] GreekDragon:
Our kernel is being messed up since LP when it comes to virtual memory. No matter what, without hackery you simply can't edit anything. Seems the only solution is to make it compatible with an app like Dorimanx with stweaks which KA do not "support" dorimanx. I have no idea how to deal with those issues, first i thought is because we already defined zram value in device tree but then i noticed the problem appears even without defining it. I'm really out of ideas. I thought maybe is because we're using old zram /LMK driver, but this doesn't seem to be the problem.

Thanks sir, will take a look, thanks.:o
[Galaxy S II Android Development] pacman7:
Great work, thanks [MENTION=5651185]GreekDragon[/MENTION]

Regards.
[Galaxy S II Android Development] bujjo53:
Anyone flashed latest build , it is fast and stable ?
[Galaxy S II Android Development] pacman7:
I flashed latest build and it is fast and stable.

Regards.
[Galaxy S II Android Development] Nobby1960:
Works video decoding in this build?

Edit: Great- yes, it works! Many thanks [MENTION=5651185]GreekDragon[/MENTION]
[Galaxy S II Android Development] linusdan:
OHHHH YEAAAAHHH

.mp4 and .m4a it's working!

The bug in filming mode still persists in instagram.

'MTP was stopped' too.

The rest works very well.

Thanks [MENTION=5651185]GreekDragon[/MENTION]!
[Galaxy S II Android Development] jecatch:
Not sure if anyone can shed some light here but tried to install SuperSU stuck on a boot loop with the AICP loading page(acip changing colours).

Flashed AICP rom and Gapps pico, boot device loads fine reboot to recovery and flash SuperSU System-Mode 2.82 SR1 and now stuck in a boot loop.

Any help would be greatly appreciated
[Galaxy S II Android Development] MigoMujahid:
Install the su.addon instead, SuperSU needs a permissive kernel.

I attached the su.addon for you, and you can download it from the LineageOS website from "extras" section.
[Galaxy S II Android Development] bujjo53:
Change kernel to permisive first than flash supersu..
[Galaxy S II Android Development] jecatch:
Thanks any recommendations on a kernel worth trying with AICP
[Galaxy S II Android Development] Skyline:
The kernel comes with aicp is already well customized and have most of the features from custom kernel for our device
[Galaxy S II Android Development] Nobby1960:
A new build is up:

Download
[Galaxy S II Android Development] GreekDragon:
AICP going to build rootless builds.

This change will happen during a short period of time.

I could explain the decision for that,

but that would not be understandable for all users, so i put it this way...

Going rootless means that the ROM will NOT come with any Root or SU built in anymore.

There will be no Magisk - as a buildin root solution - be provided when the user flashes the ROM zip file.

What you will have to do (If you don't do it by now):

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

You will have to flash a root solution of your choice (lineage-su addon, SuperSU or Magisk) by yourself after the ROM.

I will link the appropiate solutions here in this post.

REMEMBER:

First flash the ROM, then your desired root solution!

This MUST also be done on every dirty flash to ensure root is not lost!

This MUST be done, when using the OTA app too! Just add the "root" zipfile after the ROM!

What will be noticable to the user:

~~~~~~~~~~~~~~~~~~~~~~

1. We had to cut out some features for getting this done. Those are:

a. The SELinux switch in the dev options is gone for now.

This can also be done by other apps, if necessary.

b. The feature to flash another bootanimation from AICP Extras is gone.

You can still use a flashable ZIP from TWRP or Substratum.

c. The builtin logcat feature in AICP Extras will be gone.

Most users did not use it either as it only can store max. 400KB.

We already advised to use Catlog or Syslog Apps (both free on Play store).

Remember that both need root!

d. The builtin "System app remover" will be gone, as it required root to run.

2. You will, of course, not see Magisk Manager in the app folder, of course.

3. Remember that without a root solution some other apps e.g. Kernel Audiutor will also not work.

Whatever you choose. Lineage SU options are in dev options in settings. The others use separate Apps.

Links to tested root solutions (download):

~~~~~~~~~~~~~~~~~~~~~~~~~~~

Magisk (remember that v12 need the Manager to be flashed separately. v13 will have it buildin the flashable ZIP:

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

SuperSU (Use whatever works for you, stable or beta):

https://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703

https://download.chainfire.eu/supersu

Lineage SU-addon (check your needed version 14.1 arm or arm64!):

https://download.lineageos.org/extras

-> the removal zip is available here too.
[Galaxy S II Android Development] MoixyS2:
Need help with Substratum?

Check my post and comment :laugh:

https://xdaforums.com/galaxy-s2/help/qa-common-issues-t3621453/post72662659#post72662659
[Galaxy S II Android Development] Troubadour666:
any trouble of boot of FCs on this build ? i plan to flash on I9100 soon :)

thanks
[Galaxy S II Android Development] Egyptianator:
hey dude , i was just facing a minor problem : when you try to change the long press or double press function of hardware buttons it does not change no matter what and always stay the default values can you check that out [MENTION=5651185]GreekDragon[/MENTION]
[Galaxy S II Android Development] linusdan:
I suggest leaving it as it is and remove the Magisk completely from the I9100. Let the user choose even.

Magisk does not work well on this model...
[Galaxy S II Android Development] Egyptianator:
Well, Magisk does not and will probably never work on I9100
[Galaxy S II Android Development] Nobby1960:
Sorry, I'm still on the previous build, unfortunately I did not yet had time to test :(
[Galaxy S II Android Development] Skyline:
I don't faced any problems yet with 12June build other than phone is lags alot with Interactive gov so I switch to lulzactiveq and all seems good.

Hello [MENTION=5651185]GreekDragon[/MENTION], I think you should remove Interactive gov it doesn't work good for our device or needs to be updated/tuned
[Galaxy S II Android Development] Nobby1960:
In fact, lulzactiveq is the best governor choice for our S2. With default intelliactive it often lags like hell.
[Galaxy S II Android Development] Nobby1960:
Now I did flash the lastest build (06/12) on my S2. The backlight of the hardware buttons lit short if I touch the screen somewhere. Normally, the buttons should only lit for a short time if I touch them directly (new LOS feature, works like in stock ROM). Is there a setting for this?﻿ In latest RR ROM it works correctly.
[Galaxy S II Android Development] kiva1:
Can someone help me, what SuperSu zip work with this rom?
[Galaxy S II Android Development] bujjo53:
Supersu v2.82 systemmode : https://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120

Just make sure that your kernel is set to permisive
[Galaxy S II Android Development] kiva1:
Thanks a lot, 'll try it.

Edit: It's still don't work.
[Galaxy S II Android Development] bujjo53:
Did you changed selinux to permisive ?
[Galaxy S II Android Development] kiva1:
Trying but, for tha Selinuxmode change need root l, and I use Los root.. And after flashing SuperSu open the app and says "s bin occupied".

I got folder with 20 different SuperSu zips, an non of them work..

Btw. I am new to Galaxy S2 system.. A know S3 and A3,but S2 i completely different story.
[Galaxy S II Android Development] bujjo53:
Try to flash rom then flash addon su and reboot , if not work i will flash tomorrow this rom and i will report
[Galaxy S II Android Development] kiva1:
Addon su works, but I don't want to use that.. Some of app doesn't detect that root method.. They ask for SuperSu.
[Galaxy S II Android Development] bujjo53:
Okey i will flash tomorrow and i will try to root with supersu
[Galaxy S II Android Development] Sercan Ali:
Same for me. Sim card can't be detected....
[Galaxy S II Android Development] rubentkato77:
Me too no SIMcard and extsd not detected
[Galaxy S II Android Development] Zarosky:
Very faster!!! but not work simcard.
[Galaxy S II Android Development] 2mecky:
Working fine on my i9100. Simcard detected, ext sd ok using Solid Explorer File Manager
[Galaxy S II Android Development] Skyline:
Stucked at patching system unconditionally!

Using latest twrp also checked MD5

Does it take more time than cm13 for flashing?
[Galaxy S II Android Development] Zarosky:
Resize Partition
[Galaxy S II Android Development] Skyline:
I already have 705 mb system, 8 mb preload and 3 gb data
[Galaxy S II Android Development] AngelRoker:
You need at least 1GB system partition for this rom.

Has anyone got sim card working with 20161023 build?
[Galaxy S II Android Development] Sezi01:
Wow this is very cool:D:D. Though I don't personally own a galaxy s2 device, my friend who i installed it for really loves this Rom. Really wished i could get something similar on my old Galaxy S3 device( hatred for Verizon and their locked boot loaders just got a +1:(:(). Seriously, nice work guys:good::good:;)
[Galaxy S II Android Development] sparky.lennie:
Hi everyone

Has anyone got the sim card working (detected) on the 20161023 build?

I love this ROM its fluid quick, great Work [MENTION=5651185]GreekDragon[/MENTION]
[Galaxy S II Android Development] carlx:
I can confirm that I also have SIM card problem restored backup and the SIM is back so maybe there is something with certain phone will try again latter, otherwise really good version.
[Galaxy S II Android Development] sparky.lennie:
Hey did you get the sim to work on i9100 AICP 20161023 build? If so how did you manage to do it?
[Galaxy S II Android Development] GreekDragon:
Hello everyone, in the past 2 days got hit with serious real life issues. I'm back now. Sorry for the RIL issue, did a mistake on my side, will push a new build today or tomorrow with the fixed one.
[Galaxy S II Android Development] sparky.lennie:
Good to hear you're back [MENTION=5651185]GreekDragon[/MENTION]

We're looking forward to the next build #You-rock
[Galaxy S II Android Development] Oluseun:
Can this ROM work on sgh i727 since it's Samsung galaxy S2
[Galaxy S II Android Development] Deses:
I'm amazed that this phone still gets so much love... I wish mine didn't die two years ago.