yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] visions84:
I run a custom pico gaps from the link oft the first site and it works!

But it wont detect my sim card, and known WLAN reconnecting problems
[Galaxy S II Android Development] Oxydeme:
thanks, will try this one!
[Galaxy S II Android Development] rINanDO:
Yeah... Nice to hear gapps works. Radio and GPS blobs are crashing or hanging. I have no solution for this yet, because of lack of crash info. I don't know what causes this :(.
[Galaxy S II Android Development] droidmanuser:
I'm using OpenGApps 10.0 Nano (beta test) and it's working fine for me.

I've tried the other versions of OpenGApps stored in the beta-folder (parent directory), but no one was working correctly.

Just look here:

https://sourceforge.net/projects/opengapps/files/arm/test/open_gapps-arm-10.0-nano-20200121-TEST.zip/download

---------- Post added at 21:09 ---------- Previous post was at 21:07 ----------

Hi everyone,

I've installed the latest lineageOS ROM with OpenGApps today and now I want to root my device. :):good:

Has anyone experience in rooting and can explain how to do that in this new lineageOS? :cool:

Some information? :confused:

Thank you in advance. :fingers-crossed:
[Galaxy S II Android Development] Oxydeme:
not sure that there is an official way to root it yet,

as new directives were taken and no arm su 17 yet,

hope I helped thanks
[Galaxy S II Android Development] droidmanuser:
Thank you. :)

So, I've tried to root the phone with Kingo Root, but no luck. I got this errorcode: 0x13702B and should try the PC-version... :rolleyes:

I've also tried superuser from official lineageOS download page: https://download.lineageos.org/extras

But superuser is currently only available until lineageOS 16.0... I've got an error too while installing.

Regards
[Galaxy S II Android Development] K9100ii:
You should never use 'one click root methods' like kingoroot. These apps are suspicious and likely spyware. Even if you ignore that, they've never worked in any recent Android versions, only extremely old versions like 4.4 with ancient security patch levels.

Support for addonsu has been dropped in LineageOS 17 as the LineageOS team were unable to port the privacyguard framework which addonsu used. Now, to have root access on 17, you would need to use either root over ADB or Magisk. We don't have boot images with Magisk installed to a ramdisk as the boot image no longer has any ramdisk since system-as-root was implemented (it’s now a requirement in Android 10) so your only option is using root over ADB. You can use it by enabling root access as 'ADB only' in developer options as well as enabling ADB ('Android Debug Bridge') itself and running 'adb root' while having your phone connected to a computer with an installation of ADB. From there, you can use ADB as root. You probably want a shell as root, which you can get using 'adb shell'. To push files, use 'adb push <file_source> <file_destination>'. To pull files, use 'adb pull <file_location>.
[Galaxy S II Android Development] Oxydeme:
Hi, wich files to push exactly,

with push method can it be possible to push su16?

should we wait until a backport is done?

actually using my GsII with los16 as a usb port, long story.

Using drivedroid to push ubuntu onto my old laptop, as my usb keys are all dead xD

As i cant do it with los17 right now

Best regards,

Oxydeme
[Galaxy S II Android Development] K9100ii:
You push whatever files you need to wherever including directories where root access is needed to be modified (such as /system) with root over ADB. You CANNOT push addonsu from 16.0 because support for it has been completely dropped in 17. There is absolutely nothing in 17 to interface with addonsu from 16.0. You'll have to wait until there are boot images with Magisk installed to the ramdisk released.
[Galaxy S II Android Development] :
android 10

hi some one have this android 10 for j5

https://xdaforums.com/galaxy-j5/development/unofficial-lineageos-17-1-beta-galaxy-j5-t4038777
[Galaxy S II Android Development] k1mm3:
Maybe I should find my old phone just to test this?
[Galaxy S II Android Development] rickmar:
I've attached a bunch of PIT files. Use the Stock one. :D

Got from here https://xdaforums.com/galaxy-s2/development-derivatives/mod-increase-partition-size-t3011162

Congrats.

Ricardo
[Galaxy S II Android Development] kifni:
Has enyone tested FM radio?
[Galaxy S II Android Development] rickmar:
Hi there!

anyone knows if it's possible to make de lineage 17.1 dark theme REALLY black (amoled), not that dark grey style?? I reallllly don't like the dark grey and I tried to look over the internet but got nothing...

I think in the lineage 16 it was really black no?

Thanks

Ricardo
[Galaxy S II Android Development] DevisG79:
There's an pure black option if you look under settings>display>dark design>then select pure black
[Galaxy S II Android Development] rickmar:
Hi DevisG79,

i don't have that option. Settings>Display>Dark theme> and got the schedule option and to disable... nothing about pure black... you sure it's in lineage 17.1?

Regards

Ricardo
[Galaxy S II Android Development] xdalurker1:
I did, and following some feedback from rINanDO I made the following tests:

WORKING: spiritF with build #14 with build #14 magisk in boot.

SpiritF requires granting root permission and this is the only combination of app, OS and boot that gave me a working FM radio. Actually this is the only combination that I got working out of the box on Android 10, but YMMV.

NOT WORKING: Spirit2 with build #14 with build #14 magisk in boot.

NOT WORKING: spiritF/spirit2 with build #14 with TALUS in boot partition.

---------- Post added at 07:28 PM ---------- Previous post was at 07:17 PM ----------

It is Settings -> Display -> Dark Theme -> Pure Black
[Galaxy S II Android Development] rickmar:
It is Settings -> Display -> Dark Theme -> Pure Black[/QUOTE]

HI, I don't have that option!! How can this be?!?! :eek: Maybe install the rom again?!

Tks
[Galaxy S II Android Development] DevisG79:
[/COLOR]
[Galaxy S II Android Development] Wikandro:
How to install correctly with microG ?

Hello,

First of all I renew my thanks and compliments to the developers, first of all rINanDO !

Actually, I use his ROM "lineage-15.1-20181010-UNOFFICIAL-i9100_SU_MicroG", installing microG according to the thread "[MOD] [FLASHABLE] microG unofficial installer" (with <microG-unofficial-installer-ale5000-v1.0.33-beta -signed> and <google-sync-addon-ale5000-v1.0.3-beta-signed>).

I would like to do an equivalent with lineage 17.1

- Should I install the same with "microG unofficial installer" ? or if not, with the installation offered by Magisk?

- what about these instructions (in first post) :

12. For MicroG users:

You need manualy grant permissions via ADB to get things working properly.

These are the commands:

adb shell pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE

adb shell pm grant com.google.android.gms android.permission.FAKE_PACKAGE_SIGNATURE

I understand (...?)

- these commands should be run from a PC (via ADB)

- after installing the ROM...? and magisk boot... ?

- and ... before...? installing MicroG (?)

... Is that correct ? if not, can someone tell me my mistakes, and how to get it ?

Thank you !

(For a newbie like me... :( a step by step explanation on how to install with microG would be ideal )
[Galaxy S II Android Development] flameseewa:
Is there any chance the HDMI output capability can ever be possible with this rom?
[Galaxy S II Android Development] Ok:
When you start the program showing over, a window appears:

How do I enable this?
[Galaxy S II Android Development] freakerload:
can someone explain me how is the performence from 14.1 to 15.1 to 16 and then 17.1?

I am running for some years only 14.1.

I want to upgrade but i think with that Ram the newer versions are slower and not so smooth???

Or i am wrong?
[Galaxy S II Android Development] ze7zez:
Change or upgrade the app or install it on the first android version and if the app works fine, upgrade the android.

That's what I do, and it works well.

Until 17.1 works in every aspect, stay on 14.1 which will always be smoother than 17.1 on the i9100.
[Galaxy S II Android Development] kalagani:
In fact, Magisk Manager was missing!!!

Hello,

Thanks you guest4711,

in fact Magisk Manager was missing, newbie with Magisk, I did not understand the Magisk Manager was mandatory and part to use Magisk.

After downloding and installing the Magisk Manager.apk (Magisk already installed with the lineage-17.1-20200613-UNOFFICIAL-i9100_boot_magisk.img), root privileges are now for Applications and ADB instead of only ADB

The old FastGPS application, now get the privileges, su - on terminal also :+)
[Galaxy S II Android Development] guest4711:
Glad you got it working.
[Galaxy S II Android Development] RayanCh:
Hello, hope everyone is fine. I came here to ask for help concerning my GT-I9100 on which I can't flash any ROM except the Jelly Bean stock rom which is a bit old for modern use. Any version of Cyanogen Mod or Lineage OS keep stuck on the boot animation, even the newest build uploaded on this thread. Here is the how I proceeded:

1- I had flashed a CM-11 ROM (which was not working) so had a CWM recovery. So I flashed an ISO-REC CM11 Kernel with a compatible recovery.

2- After this I followed every instruction posted here and could flash a new recovery and the ROM itself.

I am very confused because I have flashed a lot of devices without any problem. But this device is a bit tricky and I don't know why. The first time I installed cm9 was back when there was an installer and everything were working fine untill I decided to upgrade, and now I can't even install cm9. I understand that there is the isolated recovery problem and the re-partitioning and I would be very happy if I am misunderstood something and someone kindly explained it to me. Hope I am not bothering anyone. Thanks in advance.
[Galaxy S II Android Development] TriboDoP:
Hi

If you want to flash this rom you just have to follow the instruction in op and flash with odin the files repartition pitfile and the recovery. Then continue to wipe/format in the recovery and then flash with recovery the rom.

If you just want to install a kitkat rom then you can use a kitkat-compatible recovery and flash the unofficial lineage 11 by grzwolf together with a isorec-twrp recovery 3.1 (this rom has an isorec-kernel included). With this recovery you can flash a repartition zip file in order to install androi 5, 6, 7...

For latest android 9 , 10 you have to use odin to flash according to op.
[Galaxy S II Android Development] xdalurker1:
Try these step by step:

1.	Phone in download mode: use ODIN 3.07

1.1.	PIT

1.2.	PDA

1.3.	Start until flash complete

1.4.	Reboot into recovery​

2.	TWRP recovery

2.1.	Wipe - Data (type yes)

2.2.	Advanced Wipe everything except microSD:​

2.2.1.	Delvik cache

2.2.2.	Cache

2.2.3.	System

2.2.4.	Non-emulated storage

2.2.5.	Internal storage​

2.3.	Install zip - LOS zip

2.4.	Install image - magisk img

2.5.	Settings – Clear 'prompt to install TWRP app'

2.6.	Settings – check 'skip digest generation during backup'​

3.	Reboot to System

4.	In settings:

4.1.	About phone- click 7 times on build to enable developer

4.2.	In system – developer options

4.2.1.	Enable advanced restart

4.2.2.	Enable adb

4.2.3.	Lock screen swipe to none until everything is loaded

4.2.4.	Default USB to file transfer​

5.	Install magisk manager from microsd/APK and reboot system

6.	Check that magisk is working

7.	Install triangle away and rest of apps

8.	Run the following two commands from cmd:

adb shell pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE

adb shell pm grant com.google.android.gms android.permission.FAKE_PACKAGE_SIGNATURE
[Galaxy S II Android Development] TriboDoP:
[MENTION=9771272]xdalurker1[/MENTION]

Very neat and complete instruction!
[Galaxy S II Android Development] Linuxci:
Back to stock rom

Thank you again Ricardo, i really appreciate your help, i'm back on stock now. :o
[Galaxy S II Android Development] Ufonigga:
Guys I really need help with this!!! So I falshed this rom I followed all instructions and it worked I used the ram and liked it but when I decided to flash gapps the rom started getting laggy so I decided to go back to lineage os 14 but I'm not able to boot up any rom even though I'm flashing it the right way the phone doesn't even let me flash all 4 files fix firmware!! I noticed there's "non emulated storage" if I format it it goes back to *internal storage* and whenever I restart to recovery or restart the phone it goes back to *non emulated storage* I EVEN TRIED OFFICIAL PIT FILE. Alongside with all official firmwares and yet it doesn't boot up keeps restarting on rom boot up animation... Please anyone help me fix this I'm sure it's the non emulated storage that wouldn't format in recovery or through fix firmware.... I don't want to lose only phone I've so Rinaldo or anyone help me out with this pretty please because it happened bc of this ROMs pit file
[Galaxy S II Android Development] xdalurker1:
From my experience, you need to go a step backwards, to download mode:

1. Disconnect the phone from USB. Take out battery and insert it again. Battery should be charged of course.

2. Press VolumeDown + Home + Power button in this order and hold it for 10 seconds or until the Samsung screen is displayed . This should get you to download mode. There is no point in doing anything further if you cannot get the phone to this download mode as the kernel is probably messed.

3. Once in download mode, connect to a PC with a data USB and start ODIN 3.07. ODIN will recognize the connection.

4. Load pit file from OP, mark repartition, clear auto-reboot, and PDA TWRP from original post (3.4.0)

5. Click start, wait till it finishes, on phone you should see the blue bar fully across.

Once kernel is loaded, you can continue with the rest as posted in #398
[Galaxy S II Android Development] slev!n:
Sorry guys but I need again your help.

I took our second s2 and went through the steps written on the first post. So far it was working fine (with the old ROM). Then I flashed the newest twrp and afterwards did a factory reset (wipe data, system, cache, internal). Then I flashed the newest ROM and also the image-magisk (selected flash as boot). After a restart my phone went crazy. I couldn't boot correctly. So I did again a factory reset and flashed only LOS without magisk. But after booting I couldn't see any installation instructions and went directly to the home screen. Enabling WiFi is not possible.

What went wrong?

Thank you for your help!
[Galaxy S II Android Development] ze7zez:
As a result of unforeseen events, corrupted files appear in the partition, so instead of wiping, do the format data.

If that doesn't help, then it remains to go back to the stock ROM and start all over again.

In either case, you will lose all your data, so do it knowing what you are doing.

In my experience, this is the fastest way to get rid of problems.
[Galaxy S II Android Development] slev!n:
Ok thank you [MENTION=4810659]ze7zez[/MENTION]. But the steps are correct? Because I didn't get it completely:

1. Do I need to go through lineage-17.1-20200526-UNOFFICIAL-i9100.zip to flash the newest build coming from STOCK or can I flash TWRP 3.4. right away through TWRP 3.3.1-1?

2. Do I need to wipe any partition again after flashing twrp 3.4?

3. Is it still recommend to wipe data and system before installing a newer build (coming from #14)?
[Galaxy S II Android Development] CA|\|ALLA:
Hi all. In the installation instructions you should add the following:

If you come from a stock rom or a rom prior to the new emulation system, the rom cannot be installed ...

In order to be installed I would add ... you need to extract the boot.img file from the Los.17.1 rom and flash it through the modified emulated twrp or through odin in the boot partition and then restart the recovery to be able to install the rom with the kernel new that we have installed with the previous boot.img.

Your support for the device is appreciated but I entertained myself for a while to install the rom because the instructions in the post were insufficient and it wouldn't let me. Thanks for your work and best regards.
[Galaxy S II Android Development] bertofurth:
ipv6

Is anyone running the LineageOS 16.0 or 17.1 build for i9100 able to get IPv6 working with a recent i9100 build? Either on the Wifi or the Mobile Data networks?

I've tried running the builds made available in this forum, lineage-17.1-20200526-UNOFFICIAL-i9100 and lineage-16.0-20200320-UNOFFICIAL-i9100.

The networks I'm testing on are working fine for another lineage device I have (Galaxy S5 running the 1 Aug build of LineageOS 16.0) and all the other non phone devices on the network.

The details are that when the phone connects to the Wifi network, the "Settings" -> "About" dialog under the "IP address" section claims that my phone has successfully received both an IPv4 and IPv6 addresses.

Then if I try to access a remote IPv6 connectivity testing site like

test-ipv6.com

ipv6-test.com

then I'm informed by the site that IPv6 is not operational.

If I try to browse to an IPv6 only website such as

ipv6.test-ipv6.com

Then I get an error message in the browser saying

net::ERR_NAME_NOT_RESOLVED

If I browse to a raw IPv6 address such as

[2600::]

then I get

net::ERR_ADDRESS_UNREACHABLE

If I try to ping6 from the S2 phone to the local IPv6 router device (either link local or public address) using a termux session then I get an error message

connect: Network is unreachable

The very weird thing is though that I can IPv6 ping FROM the local router TO the S2 phone successfully! (Both Link Local and Public IP addresses)

When I try to use Mobile Data I don't see the phone even getting an IPv6 address....but that might be a misconfiguration of the APN on my end. Not sure yet.

Any ideas? Any other troubleshooting I could do? Thanks for your help!
[Galaxy S II Android Development] skyhawk304:
Hi there, I've never installed a custom ROM before. I reached step 6, however I don't have the IsoRec TWRP installed so I can't access the recovery (step 7), so I can only access download mode. Outside of download mode, the phone shows two different battery charging icons (one from the original ROM, one is new). Since I flashed the PIT and PDA through ODIN ("PASS" message was displayed), I can no longer access the original Samsung Android 4 ROM. My device is still recognised in ODIN but not Windows 10. Any ideas? If it's any help, I have a microSD card which I can use on my PC with an SD card adapter. (Please don't shout, if nothing can be done, I'm ok with my S2 being a paperweight ?). I'd appreciate simple instructions. Thanks guys.

Edit: Booted into TWRP now. Don't really know what I'm doing but it seems to be working!

---------- Post added at 05:21 AM ---------- Previous post was at 04:22 AM ----------

Thanks so much for building this ROM, I finally got it and GApps working! I found that:

I needed to unplug the USB cable from my computer before booting into the recovery

3.4.0 TWRP is required for build 14

And also I am glad I did not install the TWRP app. Thanks again, this will be great to use instead of going into landfill.

PS: Are there any ways to speed it up further? How do I boot into LineageOS when the phone is charging (it displays the battery loading icon and doesn't allow me to boot), and how do I remove the yellow ! icon below the Samsung Galaxy S2 boot icon?
[Galaxy S II Android Development] rINanDO:
New build is up!

Hopefully we have now a stable RIL. It took me weeks investigating why libhwbinder and our RIL (and of i9300 also) is crashing. I found out that since Android 10 they binderized libsuspend. When our legacy libsec-ril.so decides to release a wakelock it does this using a binderized call. However the whole RIL is binderized. So while sending a binderized call it sends new messages on topand corrupting the first message AND REPSONSE and crash RIL. Using my hack before the first message is corrupted and RIL still runs fine. Since this is a wakelock release message, good chances are that this is the cause of our batterydrain. It is just theory but please test if this release resolves this issue and hopefully also memory leaks and hang at shutdown.

Build #15 2020-08-18

Overall state: Stable

Android build: 10.0.0-r41

Required recovery: TWRP 3.4.0-i9100 for Android 10

Changes:

- Update sources

- Fixed network selection

- Removed (again) 4G/LTE network option

- Fixed binder RIL issues

Downloads

i9100-LOS-16.0-Emulated-Storage.pit

TWRP-3.4.0-i9100-Android-10.img

lineage-17.1-20200808-UNOFFICIAL-i9100.zip

lineage-17.1-20200808-UNOFFICIAL-i9100_boot_magisk.img
[Galaxy S II Android Development] slev!n:
Coming back to these questions:

4. I dont know what I'm doing wrong but after doing steps 1-9 I'm often dealing with the issue that I cant copy files from my pc to the phone. The file manager of my pc says TWRP 3.4 img file is on my phone but the file doesnt show up. It works just via sd card. The same happens when I want to transfer the newst built to the phone on twrp 3.4. Whats wrong?

5. Thanks [MENTION=2222292]rINanDO[/MENTION] for that new build. Did a clean install. While installing this newst build (8.8.) the phone restarts many times itsself. Also later when I want to changes settings or doing other things. I'm not able to work with the phone. It does restarts every minute :(
[Galaxy S II Android Development] ze7zez:
.

How did your phone work in STOCK ROM (from Samsung)?

.

If you have made STOCK back as I suggested and you are still having problems,

it may be that the NAND "Input-Output" write controller or NAND memory is damaged.

.

However, if you have trouble understanding and executing the custom ROM installation process,

please post exactly what you are doing in another thread to avoid spamming this thread.

.
[Galaxy S II Android Development] slev!n:
I came from 14.1 and all was fine. I didn't play a lot in STOCK but it seemed to be smooth as well.

I've been flashing Custom-Roms since 2014 several phones and never had this kind of trouble as I have with this ROM. Besides flashing and making Nandroid Backups I was not deeply inside that recovery mechanisms. That's true. And this emulated storage things is not simple to understand for everyone. That's why I had questions to do it the right way.

But is it a separate topic when I have trouble with the installation process of this specific recovery and ROM? I have these issues on two S2. Which were running smooth one month ago on LOS 14.1
[Galaxy S II Android Development] skyhawk304:
2011 phone with the August 2020 security patch on a very stable stock ROM. Incredible, it blows my mind - I guess I'm just getting acquainted with the world of custom ROMs. Thank you so much! My problem with the ROM running slowly was caused by GApps, and the device performance was set to 'Power save'. Removing the old ROM and GApps before installing this new ROM makes it run smooth now.

I have one problem. A-GPS does not seem to work in build 15 but was working in build 14 (MapFactor received my location on build 14). First link is screenshot of SatStat, showing 5 satellites obtained but no lat/long. Second screenshot is in MapFactor. Same is occurring in OsmAnd. Any ideas?

Edit: switched back to build #14 by wiping Dalvik/cache/system and installing old ROM. A-GPS no longer works in that build. Not sure what the issue is.

https://i.imgur.com/6RozKxU.png[/IMG]

https://i.imgur.com/gVhr83h.png[/IMG]

(I can't post links or create attachments yet)
[Galaxy S II Android Development] ran000:
Same here. No GPS ( I use iGO and GPS Test ) with build 15, however I had this apps working well with build 14 and earllier
[Galaxy S II Android Development] Dundee930:
Same here X 3

No GPS, all GPS sensor's parameters cannot be shown in GPS app.
[Galaxy S II Android Development] rINanDO:
Thanks, I will check this.