yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Czeh:
Hi rINanDO

Guys need help. The manual for the clean installation LOS 16.0:

I can not find this folder / tmp / where it seems to be copied zip

Where to looking for ? Already reviewed all the folders. I tried to repeat the procedure, one and the same error.

PS: I turned off, I thought the system would not boot, but no, the animal booted with the old system,

through ES File Explorer I began to search for this tmp folder and found it, but there is nothing at all in it.

It is strange why it cannot be found from the recovery mode. I'm doing something wrong.

PS2: Don't guess how to install TWRP-3.3.1-1, and tried install the TWRP 3.1.0-EMU-MIGRATION-M-20170318.zip

but I got stop after install lanchon-repit-20170115-system = 1.5G-data = max-sdcard = min + wipe-preload = min + wipe-i9100.zip

rINanDO waiting for your help.
[Galaxy S II Android Development] guest4711:
Thanks again for your continued work. I got a strange problem and like to ask whether it is my g-apps-less installation or an issue of this ROM: Reading or changing settings from the terminal fails with error (2**32-2].

:/ $ settings
cmd: Failure calling service settings: Failed transaction (2147483646)
2|:/ $ su
:/ # settings list global
cmd: Failure calling service settings: Failed transaction (2147483646)
2|:/ #

Another question: I'm missing the setting for "notification access". Settings->Search displays an entry but does not open it...
[Galaxy S II Android Development] rINanDO:
Hi,

I think you read the old instructions for older builds. You need to use "Samsung stock to LOS 16.0" for build #14 and higher.
[Galaxy S II Android Development] TriboDoP:
[MENTION=10050871]Czeh[/MENTION]

Hi

If repit file has been copied to tmp-folder:

Go (in twrp) back to: install>select storage>internal storage

Tap on "up a level"

Scroll down an enter tmp folder

Tap on repit file and swipe to flash.

This should work
[Galaxy S II Android Development] Czeh:
thanks, coz I tried that. ok, will try again

but how can entry in twrp ? After step 1,2,3 anyway I was booted in recovery.

Where or how can I boot in twrp? Sorry my question, I do Lineage OS installation for the first time

---------- Post added at 12:48 AM ---------- Previous post was at 12:38 AM ----------

Can you give the link to that instruction ?

PS: if at current time my Galaxy S2 have not a stock system, but very old Omega android 4.0.3.

What I have to do in this case for full success of install LOS 16 build 15 ?
[Galaxy S II Android Development] linusdan:
View this instruction. This will help you. It was based on [MENTION=2222292]rINanDO[/MENTION] instructions.

https://xdaforums.com/showpost.php?p=79695782&postcount=3
[Galaxy S II Android Development] TriboDoP:
[MENTION=10050871]Czeh[/MENTION]

Hi

Linusdan gave you a perfect guide to to solve your problems.

Just want to add some explanation for you. Your kernel seems to be very old (non-isorec). Thats why the twrp doesn't show up even when beeing successfully installed. It will remain on your device all the time, you will not see it and only show up with a compatibel kernel installed.
[Galaxy S II Android Development] K9100ii:
By the way, you have to run the repit script from your micro SD card, and it will then copy itself to /tmp for you to run. Just in case you haven’t done that and expect it there. Also, to boot into recovery (after installing TWRP, of course, which I assume you’ve done), hold down the Power, Volume up and home buttons at the same time, and when you see the bootloader start screen (the “Samsung Galaxy S II GT-I9100” screen), stop holding the power button and hold only the Volume up and Home buttons.
[Galaxy S II Android Development] Czeh:
linusdan many thanks.

1. If I right understand Latest CarbonROM I can replace into - lineage-16.0-20190721-UNOFFICIAL-i9100.zip

Am I right ?

2. by the way, which custom's system can you recomend for Galaxy S2 ?

becouse this device very old and I would be like have not any bugs or brakes

---------- Post added at 12:49 PM ---------- Previous post was at 12:23 PM ----------

TriboDoP Tnank you.

Which kernel and custom's system can you recomend for Galaxy S2 ?

becouse this device very old and I would be like have not any bugs or brakes. it's main
[Galaxy S II Android Development] TriboDoP:
[MENTION=10050871]Czeh[/MENTION]

Hi

I would start and flash unofficial lineage 11 by grzwolf together with isorec twrp recovery 3.1.... by the.gangster.

So you have a good working rom and a twrp recovery to flash many available roms out there.

To flash lineage 11 you must have a kitkat-compatible recovery. If yours is older flash this one first. Then boot straight into kitkat-compatible recovery and flash rom together with twrp 3.1....

No need to flash kernels. They come with rom.
[Galaxy S II Android Development] linusdan:
You're right :)

It goes to your taste. The ROMs I made are based on the work of rINanDO. The problems that are here will be there.
[Galaxy S II Android Development] guest4711:
Does anybody know where the setting for "notification access" are? Using the search Settings->Search an entry is displayed which does not exist.
[Galaxy S II Android Development] preclix:
Exists in Settings -> App&Notification at the botoom is menu entry Expanded and there you will find what you want.

---------- Post added at 09:15 AM ---------- Previous post was at 09:10 AM ----------

I'm using for flash phone utility heimdall. You can upload PIT and recovery with one command and lineageOS and gapps you can install from microSD card. From recovery you can format the partitions. I can send you short instructions which works for me.
[Galaxy S II Android Development] K9100ii:
Yes, you can use Heimdall for flashing. Indeed you can do all of that. I don’t really need more instructions, as I already understand all the instructions that have been posted already and I have this ROM installed on my phone, anyway, however, [MENTION=10050871]Czeh[/MENTION] may need them if installation is still not successful. I was just replying with answers to [MENTION=10050871]Czeh[/MENTION]‘s questions. :)
[Galaxy S II Android Development] guest4711:
Thanks for the tipp but I don't find it there.

It's neither in 'Notifications' nor in 'App Permissions' nor in 'Special App Access'. Where do you see it?
[Galaxy S II Android Development] sajjads24:
hi

i need app for use radio FM for i9100 on lineage 16 ?
[Galaxy S II Android Development] mirhl:
https://xdaforums.com/galaxy-s2/development-derivatives/pie-i9100-t3850588/page8
[Galaxy S II Android Development] hagadus:
Wow, new update. THX! :)
[Galaxy S II Android Development] guest4711:
Are you sure? I see no newer one than 20190721...
[Galaxy S II Android Development] ze7zez:
Hahaha! :laugh:

It is not surprising when the zombie rises from the grave, or when Last Login: 1st January 1970 12:00 AM

---------- Post added at 21:23 ---------- Previous post was at 21:00 ----------

You're welcome.

I have different experience with Android Pie on my i9100.

Pie has very advanced energy saving support.

I turned on battery saving intensive in Carbon made by [MENTION=8145312]linusdan[/MENTION] and at night (clean ROM) I have 0.3%/h battery consumption overnight (airplane mode off, SIM card active).

So try Carbon.
[Galaxy S II Android Development] rINanDO:
Hi everyone,

I took a deep dive how Magisk is installed/flashed via recovery. The

problem is the ramdisk(.cpio) is in the zImage and not on a separate partition

on modern phones.

Finally I have found a solution to build our i9100-kernel with

Magisk-patched ramdisk.cpio! With other words, flash

i9100-LOS 16.0-magisk-boot.img to boot-partition after flashing

lineage-16.0-20190811-UNOFFICIAL-i9100.zip and install MagiskManager

in Android. Happy testing Magisk!

Build #16 2019-08-11

Overall state: Stable

Android build: 9.0.0-r46

Required recovery: TWRP 3.3.1-1

- Updated sources

- Added Magisk kernel build-script in device-tree

- Magisk support via i9100-LOS 16.0-magisk-boot.img!

This installs the patched kernel with Magisk-v19.3.zip

Known issues:

- Call recording only records microphone

Please report if there are more issues.

Downloads

i9100-LOS-16.0-Emulated-Storage.pit

i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5

i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img

Download LineageOS 16.0 SU (arm) addon/removal here

lineage-16.0-20190811-UNOFFICIAL-i9100.zip

i9100-LOS 16.0-magisk-boot.img
[Galaxy S II Android Development] Apex Predator:
Wow, this is huge news! What a fantastic accomplishment, well done.
[Galaxy S II Android Development] bersem:
Thanks [MENTION=3742928]rlNanDO[/MENTION] ! Flashed dirty from previous build. Again PUK Code appears on first boot-up.

EDIT: Rebooted and same again: "Enter PUK Code"
[Galaxy S II Android Development] K9100ii:
Nice getting magisk to work! It seems to be working, though magisk hide will not work. (Namespace support in current 3.0 kernel is not implemented. Not really an issue to me though since I don’t really use apps that detect root.) Could you please explain how you modify the ramdisk for the kernel to include magisk? I would like to update magisk when updates become available. I don’t really need anything more than instructions on how to patch the ramdisk, I already know how to build the kernel and can get the sources. If you could, that would be great.
[Galaxy S II Android Development] chhapil:
That's a huge leap!!

Magisk hide won't work as it needs the namespace support in kernel which is lacking for now.

But this will atleast allow a nice root solutions to work to allow system tweaking.

Take a Bow!!
[Galaxy S II Android Development] bb0815:
I get error 7 when trying to flash this update over the previous one.

Or do i first have to install this Magisk?

And do we need the Magisk anyway because i don't know what it is and never before heard of it.

And why remove SU? It's working fine.

Other than that, Thanks a lot for this ROM!!!!
[Galaxy S II Android Development] rINanDO:
Hi,

Nice to hear you are happy with this :) I don't know Magisk Hide, but now it makes more sense why the namespace patch is really needed. Feel free to help to get the old 3.0 kernel patched for Magisk.

I just updated my repo for the script I used for creating Magisk kernel. See this commit. https://github.com/rINanDO/android_...mmit/76a4516d96e3490bfd5ddd821d2a69d35765f03e. I use Ubuntu and you need abootimg (sudo apt-get install abootimg). The script tells you what to do. Connect your phone with LOS 16.0 (or other ROM) in TWRP to your pc. Start the script and follow the instructions. It will flash the boot-partition with the format Magisk expects. Then it pauses and instructs you to manually flash Magisk. Then you continue the script and it extracts the patched ramdisk and builds the kernel and flashes this back. On your SD-card you will have a copy of the newly flashed Magisk-enabled kernel. :)
[Galaxy S II Android Development] ChronoMonochrome:
Hi, long time no see :)

Koffee kernel (S3 / Note 2 kernel) has a backport of the namespace commits:

https://github.com/acroreiser/Koffe...2417cd9#diff-3fbed1fd4d15699b74b30cabf5be8133

I don't have a clean patch (i.e. not the squashed commit like one above), but I think that should be possible to cherry pick the commits listed in the commit message in the link.

Beware though, on S3 enabling CONFIG_NAMESPACES (and related configs) caused a dead sleep issue when the phone is receiving data via a modem while in the deepsleep. I'm not certain how people got fixed it (but indeed tinkering with modem sources got fixed it).
[Galaxy S II Android Development] guest4711:
Switching from addon-su to Magisk solved this problem. :svetius:
[Galaxy S II Android Development] mirhl:
Alternatively, you could try this set of patches.

As for the boot partition getting cramped.. I find hard to believe there is a problem that you can't just solve with zstd compression.
[Galaxy S II Android Development] ChronoMonochrome:
I believe the conflicts occurs because a part of the required changes is already applied. At least, a squash commit above states that it uses some commits which (if I'm not mistaken) were introduced in Nougat S2/S3 kernels.

On S3 we use 3.4 kernel (which has mentioned in a squashed commit message patches), but unfortunately I can't give a patchset that would cleanly apply on 3.0.
[Galaxy S II Android Development] pesav995:
Hi everyone, i installed successfully the ROM but i want to go back to lineageos 14 because with the 16 i found the phone laggy and it heats a lot when i use it. My question is: i have to install a normal twrp and redo the repartition or i can install the lineage 14 with the patched twrp? ( sry if the question is stupid but i'm a noob with those things)
[Galaxy S II Android Development] rINanDO:
Thanks for the info. Is Magisk Hide not working? I tested with terminal emulator if su is visible or access was denied. It seems to be working. The Rom passes SafetyNet and I just caught a few pokemons (It took a few minutes to load, but pokemon go runs an playable)
[Galaxy S II Android Development] K9100ii:
Hi,

No, magisk hide doesn’t seem to work for me, on both my own custom kernel (only ENABLE_NAMESPACES is set to ‘y’) and the image of the stock kernel with magisk included. :( Testing su in a terminal emulator app shows the superuser prompt with magisk hide enabled and when granting, it goes to a root shell with no errors. It doesn’t pass safetynet for me whatever I try for both basicintegrity and ctsProfile. What did you do to get it working? Did you do anything to the kernel sources or use the current kernel with magisk (I don’t expect this)? I should mention that I have modified the /system partition and have Nanodroid MicroG (no gapps, with safetynet enabled on official servers), so maybe that’s why safetynet doesn’t pass, but I still expect it to hide root with magisk hide. Would it be possible if you could please upload your boot image you’re using to pass safetynet for me if you’ve modified the kernel sources, as well as explain what you’ve done to the sources?

Thank you.
[Galaxy S II Android Development] rINanDO:
The Zip is the normal LOS installation zip with the normal zImage. Magisk isn't included in this zip/zImage. The .img is the Magisk ramdisk patched zImage. You need to flash this afterwards via twrp Install image and choose Boot. The kernel sources aren't modified. I didn't change ENABLE_NAMESPACES... Which custom rom do you use/build?
[Galaxy S II Android Development] guest4711:
There is a bug in current Magisk implementations. On some devices MagiskHide does not work, on others it does not work if some modules are loaded.

Usually everything is well if you turn MagiskHide off and on again after booting is complete.

Did you try it?
[Galaxy S II Android Development] K9100ii:
Hi,

I have edited my reply several times since you’ve posted, sorry! I understand everything, my initial reply just wasn’t very good. I am building just the kernel with all your sources and LineageOS (plain LOS just like this ROM, no other ROM).

Thank you for this suggestion, this appears to work! Although I still can’t pass safetynet, apps can’t see root after enabling magisk hide for them. This also appears to work on the existing magisk zImage. For safetynet, maybe wiping the system partition, leaving data as is, reinstalling everything (mostly Nanodroid MicroG) and then testing safetynet might be a good idea for later.
[Galaxy S II Android Development] js-xda:
Thank you, [MENTION=2222292]rINanDO[/MENTION], for your work!

Dirty flashed build 16 just today. So far working fine - except the previously mentioned PUK issue upon reboot. But I am wondering whether the August security patches are already included as r46 indicates as well. System info states 5. Juli while kernel states August 11 (double-checked to make sure I flashed the right build - also the build 16 (190811) is stated there). But I learned before that actual patch level is not necessarily connected to what is stated in the system info.
[Galaxy S II Android Development] rINanDO:
Can you provide a logcat when the puk issue occurs? My guess is selinux denial. I will check the security patches. I synched sources only so I assume it is patched..
[Galaxy S II Android Development] tabarnuza:
good morning, I installed the rom following the steps and everything is correct. but I have a problem. I have a disk parrot, (drone) and when I connect the remote I should recognize it and open the application and it doesn't, it just reloads, how can I make it work?
[Galaxy S II Android Development] ccox421:
Hi,

I installed LineageOS 16 on my S2 today, from the 14.1 version. It is really wonderful, but I feel it is quite slow. Is it the GO version or not, and if not, is it possible to activate the GO edition?

Thanks!
[Galaxy S II Android Development] Catfish78:
Wait a day or two for time for optimisation. In my case i think it is faster than with 14.1 . But modern apps are getting bigger and bigger.

Regards
[Galaxy S II Android Development] ccox421:
OK, I will wait then. But is GO activated by default, or is it necessary to use the patch designed for Oreo to do it?

Thanks.
[Galaxy S II Android Development] guest4711:
Take the patch (or set the property ro.config.low_ram=true).
[Galaxy S II Android Development] K9100ii:
ro.config.low_ram (AKA the prop in /system/build.prop that the “Android GO patch” sets) is set to ‘true’ (and so enabled) on this ROM by default. You can always modify /system/build.prop with root (either magisk or LineageSU) and set ro.config.low_ram to false from true or install a TWRP package to disable low_ram if you’d like to.
[Galaxy S II Android Development] guest4711:
Or use a magisk module to toggle it (and feel the difference).
[Galaxy S II Android Development] K9100ii:
ro.config.low_ram is set to ‘true’ by default. There is no need to modify anything.
[Galaxy S II Android Development] rINanDO:
Welcome. 16.0 consumes more memory by default. Even with GO. And android does a lot of things in the background, for sure using Gapps. At memory pressure it slows down time to time. When you just installed LOS 16.0 all apps are being optimized in the background. When charging to 100% it re-optimized apps again when necessary. I tried many things already to free up memory on our 800mb effective ram.
[Galaxy S II Android Development] APBNDRUM:
Pls help, after formatting the storage my media storage part 'sdcard0,' is gone. Only have internal storage 8gb
[Galaxy S II Android Development] js-xda:
Thank you for the prompt reply!

I have little time at hand right now and I have never extracted a logcat so far (so might take me longer than someone doing it regularly). Happy to provide one but might take some weeks (unless there is maybe an option to do so on the phone without root?).

Otherwise, can maybe [MENTION=5677277]bersem[/MENTION] or [MENTION=9549206]TALUAtXDA[/MENTION] provide one as they seem to observe the same behavior?
[Galaxy S II Android Development] MaRtYy01:
Today I ordered an aftermarket battery to replace my 2011 one. So far from my experience with the rom has been almost flawless. I enabled 720p playback in vanced,forgot to lower video quality to 240p and while browsing the internet with vanced playing 720p video in the background the phone froze and restarted,I guess that was too intensive. No such problems when playing video in the background in 240p though. Similar thing happened after the first restart,I forgot to lower quality again and it crashed the audio driver this time,reboot obviously fixed it. Other small things-after I booted up the phone after leaving it inactive for 2 weeks(I was on a vacantion and left it home) it was kinda buggy,the quick settings refused to work. I could click stuff in it but it wouldnt make a difference,for example I could click the settings icon in the quick settings and it would hide them as its about to open the settings app but it just didnt,the other toogles also didnt work;if I tried setting up stuff directly from settings it worked fine. Reboot fixed this as well. Today I got a call while using the phone and it appeared very slowly,the phone started vibrating but call notification didnt come up in heads up,it took it about 5-10 seconds to show up. I mapped my home button to answer calls,havent tried it yet but this might be a good workaround.

So far these are my small problems that I experienced during my work with the rom,they are such little things that its actually insane how stable this rom is. [MENTION=2222292]rINanDO[/MENTION] Absolutely outstanding work. The ''balanced'' battery mode also seems to improve battery while the performance is pretty much the same as the ''performance'' mode. Today I also set up a ''challenge'' for myself,I will use the phone as daily driver for 1 month and I forbid myself to use other phones. Day 1-my battery is bad and this is the only thing that bothers me,phone is good enough for all other work(except higher end gaming) that I usually do.

Another thing,I guess most people already suspected this if they thought about it, but today I spent about 45 mins to check all capable 2010 and 2011 phones and galaxy s2 is the oldest phone that currently runs android 9.0 with note 1 following it. Sorry for the offtopic in this post but im just kinda bored and wanted to share this.

edit: Another thing that I forgot to praise,the capacitive touch buttons blink when there is a notification and I really love this.
[Galaxy S II Android Development] MaRtYy01:
Yesterday I noticed a problem with the video codecs,or whatever its called,related to proper video playback. Fox example if you try to play something from a local website for anime and movies vbox7(dot)com picture will come out disorted and even freeze with the sound as well if the quality is too high. I also tried other sources of online video playback,most of them seem to have some problem with the buffering,my internet is fine and they play fine on my pc so I doubt the problem is in them(sources tested-9anime,crunchyroll). Tried multiple browsers as well without success. Anyway youtube works fine,live videos too which is more important lol. Maybe the drivers are too old for this issue to be fixed but I guess its worth looking into further.

As for for the aftermarket battery-its branded blue star premium 1800mah,I can easily tell its worse than a new oem battery and later today I will be able to tell if its worse than my old battery. Yesterday it was going good with like 1h 30 mins sot at 48℅,then I restarted the phone and poof- down to 2℅. I charged it powered off for about 10-11 hours tonight,currently on 67% with exacly 1h sot so its looking promising. Cost me just 5 euros so its not a big loss if its garbage.

edit: yes this "blue star premium" battery is garbage. It lasts as much as the 2011 battery,about 2 hours. Mine is manufactured 12.2018 so its not like its too old. Avoid unless 2h of sot would do the job for you.

Also screen recording doesnt seem to work properly,I used ADV. Depending on what engine you use,the screen recording is either completely disorted or just with disorted colors and the rom often soft reboots after saving it.
[Galaxy S II Android Development] APBNDRUM:
I'm revert back to stock partition and again try the guide Los 16
[Galaxy S II Android Development] K9100ii:
You might have formatted /data (not sure how, as TWRP keeps /data/media/0 after a 'format', maybe change of filesystems or some other way of formatting /data?), and since we have emulated storage, /sdcard0 is a symlink to /data/media/0, and formatting /data deletes everything in /data including /data/media/0 (sdcard0). If you've otherwise formatted "internal storage", then of course you're going to have all of the contents of /data/media/0 (sdcard0) deleted. (I've put both examples in here, "formatting the storage" can mean anything, really.)

As for reinstalling, you're wasting your time, as all that data is completely gone after a format. You're just reinstalling stuff and formatting everything several times more. I hope you have a good backup of your data, but it seems not as you're trying to reinstall where there is no point in doing so. Good luck.