• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][UNOFFICIAL][11.0.0][r43][I9100] LineageOS 18.1

Search This thread

xdalurker1

Member
Mar 1, 2019
21
14
Has anyone suffer deep sleep issues with latest build (100Mhz, but no deep sleep)? Not sure if an app is going rogue or something did changed unintentedly breaking deep sleep...
It may be related to microg core services: When I installed it and gave it permissions as it required, deep sleep was never reached. Once removed, I got percentages of deep sleep, as on my previous post
 

js-xda

Senior Member
Aug 20, 2018
214
101
Hello, why is TWRP for LineageOS 18.1 still on 3.3.1-1 and not on 3.5.2_9-0?

I want to install latest TWRP 3.5.2_9-0, but it always failed.
Can someone please tell me step by step what I need to flash? I tried all Odins and it did not work. I need the .pit file and Odin just do nothing when I click on Start.

Well, I don't dare to claim that I understand the full technical details but there is some statement in the OP explaining that you need an adapted recovery for this custom ROM - not saying that it can't be newer than 3.3.1.

[...]

For these builds you NEED ISOlated-RECovery because I had to eliminate the embedded (.cpio) ramdisk-images in zImage.

[...]

Not tested:
- Bluetooth headset
- BLN
- FM-Radio (using Spirit2)
- TWRP 3.4.0-0

[...]

It appears generally to be possible to use the adapted 3.4.0 - I am doing so myself too:

A simple question: What will happen if I use TWRP 3.4.0-0 from Lineage 17.1 to flash this rom?

Don't know but I don't expect problems. My test/dev device has twrp 3.3.1-1.

I have flashed the ROM with TWRP-3.4.0-0 successfully here. Thank to rINanDO

You can find the TWRP 3.4.0 (TWRP-3.4.0-i9100-Android-10.img) in the OP of i9100 LineageOS 17.1 thread.
 

anton-

Member
Jul 25, 2013
25
11
Yes, some users experience connection issues and gave me a hint to disable wpa auto upgrade overlay. So I just applied this patch and hope for the best. At least it still works as in previous build.
I am not able to connect to my wifi with wpa, only without wpa I can connect to my wireless. It doesn't work also with a clean install. I can see the different access points but when I put my password and I try to connect to my network it doesn't connect anymore. It is like wpa_supplicant is not working.

Edit: Sorry, it looks that it is a problem with my router (with OpenWRT). I can use the wifi with another router.

Edit 2: This resolved the issue with OpenWRT router and LineageOS:
"OK, so, after doing some testing I pinpointed the WIFi option that creates trouble:
option ieee80211w '1'
Forcing this to '2' does not solve the problem, but setting it to zero (or, to be precise, removing it altogether) fixes the issue. I also tried to install the full wpad but nothing changes.

This option is a security feature, so disabling it is not a long-term solution."


 
Last edited:
  • Like
Reactions: js-xda

OllieW

Senior Member
Jan 29, 2014
61
47
So here's my feedback for the latest 20210715 build of LOS18.1 for the i9100. Update from previous version in TWRP was working flawlessly together with latest pico OpenGApps 20210724 build.
- Everything seems to be OK so far after first reboot, but initial connection to wireless network resulted in no internet - disconnecting and reconnecting did the trick, so all settings are correct (no such problems after second reboot).
- Unfortunately bluetooth calls are still broken - I can't hear the caller and the caller cannot hear me! Curiously Bluetooth Advanced Audio Distribution Profile (A2DP) for web radio or MP3 player is working without any problems, so it's only related to Headset Profile (HSP) and/or Hands-Free Profile (HFP) perhaps in combination with A2DP?!
- Receiving SMS only works if display is on - I guess it's sleep mode related (no wakeup if new message received via SIM when display is off) because every new SMS will be displayed some seconds after display is turned on and unlocked...
I will try wi-fi connection to WPA3 network with WPA2-transistion mode the next days.
 
Last edited:
  • Like
Reactions: rINanDO

rINanDO

Senior Member
Dec 17, 2009
653
4,406

ran000

Senior Member
Dec 16, 2010
169
87
New build is up!
Only updated the sources and adjusted brightness levels and enabled auto-brightness.


Build #10 2021-08-10
Overall state: Stable-ish
Android build: 11.0.0-r40
Required recovery: TWRP 3.3.1-1

Changes:
- Updated sources
- Adjusted OLED brightness levels
- Enabled auto brightness


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

lineage-18.1-20210810-UNOFFICIAL-i9100.zip
lineage-18.1-20210810-UNOFFICIAL-i9100_magisk_boot.img
Hello

Thank rINanDO for new build. I successfully flash it here ( dirty flash ).

For me only issue with WiFi still problematic. I raised up the issue some times and repeat it now:
Issue description:
1) For default security setting: wpa+psk
- Wifi connection to Hotspot with default setting under Windows at my notebook work well. Here is log of successful connection:
https://drive.google.com/file/d/15IQqqaAHaOYIQBS7LAJ9L0XHmWZ5hIdE/view?usp=sharing
- Wifi connection to Hotspot with default setting under Fedora at my notebook does not work. Here is log of connection attempt:
https://drive.google.com/file/d/1QTHcjPQX0drKRe-FRMIcPbuI0osHljrH/view?usp=sharing
- Wifi connection mostly work well with other Hotspots, only few unsuccessful case I can remember.
2) For non default security setting: none
- Wifi connection to Hotspot with default setting (exept security) under Fedora at my notebook work well.

I have not any issues to use Wifi Hotspot from my Fedora (it is my mostly working system) system with other client devices. The problem is not critical for me, but I am interesting to find solution. Please, any help
 

js-xda

Senior Member
Aug 20, 2018
214
101
New build is up!
Only updated the sources and adjusted brightness levels and enabled auto-brightness.


Build #10 2021-08-10
Overall state: Stable-ish
Android build: 11.0.0-r40
Required recovery: TWRP 3.3.1-1

Changes:
- Updated sources
- Adjusted OLED brightness levels
- Enabled auto brightness


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

lineage-18.1-20210810-UNOFFICIAL-i9100.zip
lineage-18.1-20210810-UNOFFICIAL-i9100_magisk_boot.img
Thank you! Installed and works overall.

Observed nevertheless a moment ago a sudden reboot. No SIM installed, flight mode active but WiFi on (and connected). No Magisk, no GApps. Just FYI in case more users observe such incidents.
 
  • Like
Reactions: rINanDO

retiredtab

Senior Member
Nov 16, 2017
856
434
"- lmkd. I reverted a patch "lmkd: Restrict process record modifications to the client that created it" in lmkd which requires to get a pid/credential from kernel (I guess), but I have no idea where to look. lmkd works now but not 'clean'"

Suddenly by accident I stumbled upon some kernel patches which fixed the framework-level patch. A few hours later I found the missing kernel code to fix lmkd hacks (merge conflict resolve from kernel v3.4.113).
@rINanDO , I'm trying to fix a problem with exynos 5433 device where I'm getting constantly (over and over every 1 second) spammed by lmkd messages below. By any chance, when you wrote "lmkd works now but not 'clean'", you saw these messages?

Code:
08-10 22:34:41.497  3758  3786 I ActivityManager: Connection with lmkd established
08-10 22:34:41.497  3280  3280 I lowmemorykiller: lmkd data connection established
08-10 22:34:41.498  3280  3280 E lowmemorykiller: Failed to retrieve sender credentials
08-10 22:34:41.499  3280  3280 I lowmemorykiller: closing lmkd data connection
08-10 22:34:41.502  3758  3786 W ActivityManager: Lost connection to lmkd

When doing a strace, I found that scm_credentials were missing "msg_control, cmsg_type and cmsg_data".

constant lmkd spam t710
recvmsg(6, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\0\0\0\3", iov_len=52}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 4

working lmkd no spam p550
recvmsg(6, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\0\0\0\0\0\0H\0\0\0\0\0\0\0Z\0\0\0\0d\0\0l\0\0\0\0\310\0\0~\0"..., iov_len=52}], msg_iovlen=1, msg_control=[{cmsg_len=24, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS, cmsg_data={pid=2841, uid=1000, gid=1000}}], msg_controllen=24, msg_flags=0}, 0) = 52

I noticed your solution was to fixup scm.c, scm.h and af_unix.c at

"Copied some code from android_kernel_samsung_msm8226 for SCM_CREDENTIAL"

https://github.com/rINanDO/android_...mmit/a1b021f9b709390fcc4e5469a2bdc9006e661a40

I'm going to try your fixes to see if that helps 5433 lmkd spam.

Thank you.
 
  • Like
Reactions: rINanDO

rINanDO

Senior Member
Dec 17, 2009
653
4,406
- Unfortunately bluetooth calls are still broken - I can't hear the caller and the caller cannot hear me! Curiously Bluetooth Advanced Audio Distribution Profile (A2DP) for web radio or MP3 player is working without any problems, so it's only related to Headset Profile (HSP) and/or Hands-Free Profile (HFP) perhaps in combination with A2DP?!
I recently bought my first bluetooth headset. I used to use my car radio "Car-BT" for calls which works perfectly. So I was quite surprised my new headset didn't work like you reported. But now I can reproduce the problem and fix it ;)
 
  • Like
Reactions: TriboDoP

rINanDO

Senior Member
Dec 17, 2009
653
4,406
@rINanDO , I'm trying to fix a problem with exynos 5433 device where I'm getting constantly (over and over every 1 second) spammed by lmkd messages below. By any chance, when you wrote "lmkd works now but not 'clean'", you saw these messages?

Code:
08-10 22:34:41.497  3758  3786 I ActivityManager: Connection with lmkd established
08-10 22:34:41.497  3280  3280 I lowmemorykiller: lmkd data connection established
08-10 22:34:41.498  3280  3280 E lowmemorykiller: Failed to retrieve sender credentials
08-10 22:34:41.499  3280  3280 I lowmemorykiller: closing lmkd data connection
08-10 22:34:41.502  3758  3786 W ActivityManager: Lost connection to lmkd

When doing a strace, I found that scm_credentials were missing "msg_control, cmsg_type and cmsg_data".

constant lmkd spam t710
recvmsg(6, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\0\0\0\3", iov_len=52}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 4

working lmkd no spam p550
recvmsg(6, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\0\0\0\0\0\0H\0\0\0\0\0\0\0Z\0\0\0\0d\0\0l\0\0\0\0\310\0\0~\0"..., iov_len=52}], msg_iovlen=1, msg_control=[{cmsg_len=24, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS, cmsg_data={pid=2841, uid=1000, gid=1000}}], msg_controllen=24, msg_flags=0}, 0) = 52

I noticed your solution was to fixup scm.c, scm.h and af_unix.c at

"Copied some code from android_kernel_samsung_msm8226 for SCM_CREDENTIAL"

https://github.com/rINanDO/android_...mmit/a1b021f9b709390fcc4e5469a2bdc9006e661a40

I'm going to try your fixes to see if that helps 5433 lmkd spam.

Thank you.
I thought I answered your question a while ago, but I don't see my answer here... I hope you have succesfully fixed the lmkd spam. You have the right kernel commit to fix this.
 

rINanDO

Senior Member
Dec 17, 2009
653
4,406

retiredtab

Senior Member
Nov 16, 2017
856
434
I thought I answered your question a while ago, but I don't see my answer here... I hope you have succesfully fixed the lmkd spam. You have the right kernel commit to fix this.
@rINanDO , yes thanks to your github repo fixes, I was able to fix the lmkd spam. I gave you credit for authorship of the Aug 21 fixes at

https://github.com/universal5433/android_kernel_samsung_universal5433/commits/lineage-18.1

There's no way I would have figured out that on my own.

I'm now looking through the rest of your github for another problem that I'm having with adbd NOT starting before boot animation. I wonder if I could ask you to hookup a microusb cable to your 9100 and issue

Bash:
adb reboot
adb logcat

and tell me if your adb logcat appears on the PC screen before the LineageOS boot animation appears on the 9100. BTW, if this is off topic in your thread, perhaps we can move it to PM?

Or if you don't have time to do it, that's fine, I understand and still grateful for your lmkd spam fix. Thank you again.
 
  • Like
Reactions: rINanDO

Sir Charles82

Senior Member
Sep 7, 2015
51
11
Vienna
Hey all,

i have still LOS 14.1 on my S2. I have read that I have to do some re-partioning to get LOS 18.1 working on the S2 but i'm unsure (can't remember) what i have already done to get LOS 14.1 working.

Do you have some advice on how to get LOS 18.1 on the system? Delete everything, update TWRP to this special version (3.3.1-1 or this special version 3.4.0 from LOS 17.1-Thread?), then flashing LOS 18.1 and nano gapps.
Would this be the right procedure ?

The phone is just sitting around so a bit of testing would be possible

Thanks :)
 
  • Like
Reactions: andreoide

jo-so

Member
Nov 23, 2020
14
7
Samsung Galaxy Note II
i9100
Do you have some advice on how to get LOS 18.1 on the system? Delete everything, update TWRP to this special version (3.3.1-1 or this special version 3.4.0 from LOS 17.1-Thread?), then flashing LOS 18.1 and nano gapps.
Would this be the right procedure ?

You have to update the PIT, too. My steps were:
  1. Run a backup of images and documents, because everything gets lost.
  2. Boot in ODIN mode and flash the PIT and the recovery. (this is only needed one time on the first update to a version >= LOS 16.0)
  3. Boot in the recovery and flash the images from a SD card or via sideload.
 
  • Like
Reactions: Sir Charles82
Sep 8, 2019
6
3
20
Serbia
Code:
/*
** Your warranty is now void.
**
** We are not responsible for bricked devices, dead SD cards,
** thermonuclear war, or you getting fired because the alarm app failed. Please
** do some research if you have any concerns about features included in this ROM
** before flashing it! YOU are choosing to make these modifications, and if
** you point the finger at us for messing up your device, we will laugh at you.
**
**/

Hi all,

Well... It is still possible. Galaxy SII running Android 11! I could have made this port sooner, but the lack of time stalled a bit. Thanks to @ChronoMonochrome who ported LOS 18.0 for S3 couple months ago still using kernel 3.0.101 (or optionally 3.4) it should also be possible to build it for S2. Building for i9100 isn't straight forward because of the major changes in the image creation routines (creating boot.img, etc for the installable zip). And the GCC compiler support of Kernel 3.0.101 is removed. After resolving these issues I got my first flashable zip! Then I needed to get manifest.xml properly. Thanks to Shivaay who helped me and I got it finally booting! It was horribly slow because of some internal changes in LMKD which our kernel doesn't support some features. The Settings-app crashes immediately leaving me unable to investigate. After reverting some patches in LMKD and things in framework/base it started to run like Android 10. I addressed the HAL's and got almost everything working in this ROM. Of course it isn't perfect and there will be bugs or instability. I'm no Samsung, just a DIY :)

For these builds you NEED ISOlated-RECovery because I had to eliminate the embedded (.cpio) ramdisk-images in zImage.
Upgrade from Samsung stock ROM using ODIN 3.07
lineage-18.0-20201207-UNOFFICIAL-i9100.zip

PIT: i9100-LOS-16.0-Emulated-Storage.pit
PDA: i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5

1. Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
2. Start ODIN 3.07 on your PC.
3. Connect your phone via USB to your PC.
4. Press volume up on your phone, ODIN should detect your phone.
5. In ODIN:
Auto Reboot : unchecked
Re-Partition: checked
PIT : i9100-LOS-16.0-Emulated-Storage.pit
PDA : i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
6. Press Start.
7. After succesful flash, reboot phone into Recovery:
- Press Volume up + Power/Standby + Home and hold for 10 seconds.
The phone shuts down.
- Repeat Press Volume up + Power/Standby + Home and hold for 10 seconds
Phone boots in recovery TWRP 3.3.1-1.
8. Swipe to Allow Modifications
9. In TWRP 3.3.1-1 you need to format partions
- Wipe -> Format Data -> Type [yes]
- Wipe -> Advanced Wipe -> Select:
* Davik / ART Cache
* Cache
* System
* Non-emulated Storage
-> Swipe to Wipe
10. Install LOS-18 ( + optionally Gapps or MicroG)
To prevent "Uncryption unsuccessful" error of GAPPS at first start:
- Reboot to recovery and Wipe -> Format Data -> Type [yes] again
11. Boot System
DON'T INSTALL TWRP APP. This will cause bootloop!
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


Thanks To
  • @ChronoMonochrome
  • Shivaay
  • @lee.wp14
  • @ze7zez
  • arco68
  • Team Infusion
  • LineageOS team
  • and all prior developers that were working on this phone.
    I hope I didn't missed someone, please let me know.
  • Last but not least @channel48 which reviews custom ROMS from all kind of phones including my work on this ancient one :)
Source code:
https://www.github.com/lineageos
https://www.github.com/rinando

Current state:
Working:
- RIL (Phone/SMS)
- AGPS
- Audio
- Bluetooth (audio & headset)
- Wifi
- IMEI
- Touchkeys
- Camera Pictures
- Camera Videorecording
- Hardware encode/decoder
- Display
- Sensors
- DRM, for e.g. Netflix
- PowerHAL
- LiveDisplay
- Selinux enforced
- BitGapps
- Magisk v22.1
- FM Radio using Spirit2)


Not tested:
- Bluetooth headset
- BLN
- FM-Radio (using Spirit2)
- TWRP 3.4.0-0

Not working/known issues:
- Magisk support (misses some frameworks patches I guess)
- FM-Radio (using Spirit2)
- Home
- MicroG support
- Home-button not working while charging when phone is turned off. Use power-button

- Sometimes shutdown phone hangs (and draining your battery)
- Bluetooth headset connected via SCO

Won't fix:
- HDMI (MHL) (support broken/removed since CM 10)
Hi rINanDO, thanks for your amazing LineageOS ROM for old legend i9100, i was wondering if you can make a flashable zip for bootsplash, i made some remastered edition for Galaxy S2 i9100. Maybe i should remove Secured by Knox, since he is not in whole system...
 
Sep 8, 2019
6
3
20
Serbia
New build is up!
Only updated sources.

Build #12 2021-09-13
Overall state: Stable-ish
Android build: 11.0.0-r43
Required recovery: TWRP 3.3.1-1

Changes:
- Updated sources


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

lineage-18.1-20210912-UNOFFICIAL-i9100.zip
lineage-18.1-20210912-UNOFFICIAL-i9100_magisk_boot.img

Hi rINanDO, thanks for your amazing effort for old legend Galaxy S2. I made some remastered bootsplash for our legend!

I was wondering if you can make some flashable zip for bootsplash. Here is 4 variants black and white with and without Secured by Knox logo :

 

Attachments

  • Bootsplash without Secured By Knox logo.png
    Bootsplash without Secured By Knox logo.png
    71.9 KB · Views: 24
  • Bootsplash with Secured By Knox logo.png
    Bootsplash with Secured By Knox logo.png
    80.2 KB · Views: 25
  • White Bootsplash with Secured By Knox logo.png
    White Bootsplash with Secured By Knox logo.png
    80 KB · Views: 19
  • White Bootsplash without Secured By Knox logo.png
    White Bootsplash without Secured By Knox logo.png
    71.5 KB · Views: 23
  • Like
Reactions: Smoover

Top Liked Posts