yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] rINanDO:
I relied on hwc 1.4. I used [MENTION=5405215]forkbomb444[/MENTION] Midas kernel only for those video drivers. I updated our kernel and drivers for autosleep because early suspend patch didn't work on Pie somehow... Not specific for magisk.
[Galaxy S II Android Development] mirhl:
https://github.com/topjohnwu/Magisk/issues/209#issuecomment-428733161
[Galaxy S II Android Development] Buzzefall:
Some bugs

Used TWRP 3.1.0-0 to flash ROM, worked nice (3.2.3 failed to "map" something). Still 3.0.2 is better as newer versions fail to mount /sdcard through USB.

Also I installed GApps through Aroma (checked the very basic apps). Faced some freezes on device settings restore from cloud - had to restart my device and continue.

Sometimes system freeze when you try to check some option in settings (say, in Display section, can't remember what exactly).

Couldn't continue on testing due to a heavy screen bug - it flickers in some apps and popup dialogs is flickering as well, until that section of screen (where dialog is) becomes black. Then the only option is to kill the app and restart. But in Firefox browser it always repeated to it's no use to restart apps i think.

So, system dialogs (such as confirm Location Service permissions, etc.) and some apps make screen flickering and then (not always) flickering sections become black.
[Galaxy S II Android Development] SirGarmaples:
Wow. A 7 year and 5 months old phone, unofficially running on the latest version of Pie. That's some serious dedication.
[Galaxy S II Android Development] wmdhs1213801:
What a fansy work you have done!!!:good::good::good:
[Galaxy S II Android Development] linusdan:
I may be mistaken, but the reason the camera is not working is because of the exclusion of the support for old smartphones? I have seen the code in some ROMS to understand how things work and realized absence of functions.
[Galaxy S II Android Development] DJ.Kurrare:
this method works

root
[Galaxy S II Android Development] Oxydeme:
Thanks for this info as soon as I red, I dled the SU, reflashed v2 (to be quick) flashed root, rebooted, SU app was here but broken,

Internal was broken too, I went to recovery, Repaired Internal using format.f2fs, so once Int. had been reformatted in f2fs,

I reboot into system,

Surprisingly it worked,

I'm currently enjoying Pie + Root + Lucky Patcher + IDE

> This all result in an app I can continue dev over Pie API!

[MENTION=2222292]rINanDO[/MENTION] thanks for all the hard work you put in your rom during your spare time,

I know you can't build all the time,

but in the name of everyone Following your threads, thank you.
[Galaxy S II Android Development] JaLoou:
Hello.

I'm a noob in tech and may I'm wrong...

But please look here: https://github.com/torvalds/linux/tree/master/drivers/media/i2c/m5mols

There are drivers for the camera sensor (Fujitsu M5MOLS) in Galaxy S2 for the latest Linux kernels.

May it helps to fix the camera.
[Galaxy S II Android Development] mirhl:
M-5MO LS is the ISP, not the sensor.

Then, the problem's likely the changes google keeps doing to the userside legacy HAL1 interface.
[Galaxy S II Android Development] rINanDO:
Thanks. But I think it isn't the driver itself. It's because of the display drivers and some changes in display memory that causing issues with camera. I don't have the skills to fix it because forkbomb was the one initially added hwc 1.4 support but didn't finished (no offence!). He got the skills. So far no camera support.
[Galaxy S II Android Development] Asian Kiwi:
Is there any way to get the gestures nav bar and normal nav bar working?

When i type in "nav bar" in the search box, it comes up but the option is no where to be found
[Galaxy S II Android Development] wmdhs1213801:
Can I flash it without gapps(1Gsystem)?
[Galaxy S II Android Development] guest4711:
Yes, why not. G-apps is an optional addon.
[Galaxy S II Android Development] rINanDO:
New build is up! Not much progress but we have SU out of the box.

Build #3 2018-10-26

Overall state: Stable-ish

Android build: 9.0.0-r10

Updated sources

Added Lineage SU Addon

Download here: lineage-16.0-20181026-UNOFFICIAL-i9100.zip
[Galaxy S II Android Development] ran000:
Twice download ( both same MD5SUM - shown as correct ), twice flash - booting loop ( I wait more then 30 min ).

Does somebody get other result?

Back to previous build for now.
[Galaxy S II Android Development] rINanDO:
Did you do a clean flash? I had bootloop also when dirty flash.
[Galaxy S II Android Development] ran000:
Thank. New build is work after clean flash for me as well.
[Galaxy S II Android Development] K9100ii:
[MENTION=2222292]rINanDO[/MENTION], multi user has completely gone in build #14, this is true. Also, may I ask why you’ve enabled the low_ram flag again?
[Galaxy S II Android Development] rINanDO:
Hmm I didn't removed multi user intentionally. Probably because of low_ram flag which I did. I try to get Max available memory as possible. Do you see any effect in performance? And did anyone already tried the Bluetooth SIM Access Profile? The problem with focus qr codes I can reproduce and have a solution for it.
[Galaxy S II Android Development] guest4711:
See https://xdaforums.com/android/softw...roperty-patcher-android-t3737373/post79708833 for disabling/enabling low_ram property using TWRP (if you don't like to modify tge properties by hand).
[Galaxy S II Android Development] K9100ii:
I see, I wonder how it could have been removed. Setting the low_ram flag to false doesn’t bring it back though I’m not sure if it would, anyway. The difference in memory usage is not much. I don’t see much difference in performance, just the slightest bit more lag after booting it on the lock screen. I haven’t tried the Bluetooth SIM access profile, as I don’t have any use for it. Nice that you have a solution for that bug, already!

Yes, I edit build.prop manually, but this could make setting it to false easier.
[Galaxy S II Android Development] OllieW:
I installed the new July LOS16.0 build with the fresh TWRP 3.3.1-1 EMU-release and wiped everything. There are some minor problems with a complete wipe and fresh installation:

- There is a problem with "wipe cache" - seems that the cache partition cannot be unmounted correctly for a wipe.

- Although the kernel now supports F2FS on system partition, the installation script of LOS16.0 will convert the partition formatted with F2FS back to EXT4. AFAIK there was a former release with won't chance the existing format of the system partition.

I will test the Android rSAP feature ASAP. Thanks for the great work!
[Galaxy S II Android Development] rINanDO:
Hmmm if low_ram wasn't the issue, then I guess the Android source r44 changed the behavior somehow?. I found extra configs I didn't use about multiuser where max users is set to 1 if not set.... I will try using this set this to 3 and hope this will work.
[Galaxy S II Android Development] K9100ii:
Maybe. That could be it. I saw a build.prop modification somewhere for multiuser that set a flag in it to ‘3’, maybe related.

By the way, what modem do we recommend/use for this ROM? I’m currently using XXMS4, but maybe there’s something better (maybe XXLS8, maybe even XXMS2 (though I read XXMS4 is better than 2), anything else?). Also, are we able to only use LineageSU, with no alternative? It’s fine by me, but maybe there is also something better? If anyone can answer, that would be nice.
[Galaxy S II Android Development] rINanDO:
Well, I just tested with multiuser to 3.... no use.... And I found the code in Android frameworkbase. It checks the low_ram flag via activitymanager. It returns 1 max user if the device isn't a television. Otherwise it checks the multiuser setting.

I don't know which modem is better. Can't answer that. I'm building with lineagesu as convienient. I could exclude this from the build so you need to flash manually afterwards. (Not tested yet)
[Galaxy S II Android Development] linusdan:
XXMS2 because is more popular.

To use other alternatives such as Magisk it would be necessary to update the kernel version, which takes a lot of time to leave stable. SuperSU is obsolete and installation is not recommended for security reasons (Android 7+).
[Galaxy S II Android Development] K9100ii:
I see, that’s sad. It’s okay that you can’t answer. You may continue building LineageSU in the builds if you’d like to, there is no issue. However, if you’d like to make this ROM official, you will have to exclude LineageSU so that the user can install it if they would like to have it (because security by default).

I find XXMS4 much better than XXMS2, especially for GPS, so I’ll continue with XXMS4. Yeah, I’ve figured that it would be difficult to update the kernel. I’ve tried to compile my own kernel on 14.1 with CONFIG_NAMESPACES enabled and tried to patch a few things but nothing would work because of the outdated kernel. SuperSU is very much obsolete, and the last time I tried installing on 14.1, it gave me a bootloop.
[Galaxy S II Android Development] LeBourrin:
Hello guys, I'm running LN14.1 no EMU so I made a clear install with TWRP-EMU LN16.0.

- My first problem is that I can't mount USB to copy install zips in TWRP from my computer. I have to use a SDCard.

- Second, I confirm that ROM doesn't boot if you flash OpenGapp with it. I tried pico, nano and micro without success.
[Galaxy S II Android Development] rINanDO:
Correct. I tried a while ago before oreo to add the patches on our kernel but I didn't succeed. I also don't now technical details how it should work. Maybe I will try this again sometime. Anyone have more details about Namespace and Magisk?
[Galaxy S II Android Development] hellbach:
Same here. It worked with MindTheGapps.
[Galaxy S II Android Development] K9100ii:
Has anyone else got an issue where the CPU frequency is not available to some apps? For example, CPU-Z shows 1 core with core frequency shown as “n.a. - n.a.” and CPUFloat shows “cpu0 -“. I hope it doesn’t mean my hardware is failing, but probably not. htop as root in termux (LOS comes with htop) shows both cores fine with correct usage and kernel adiutor shows both cores and frequencies fine, too as some examples of apps that show the frequency fine.
[Galaxy S II Android Development] bersem:
maybe it`s selinux related ?

https://xdaforums.com/showpost.php?p=79588679&postcount=487
[Galaxy S II Android Development] K9100ii:
​

I see, interesting. I have restored a nandroid backup from 2 days ago, where there is no issue. I run SELinux in permissive mode for ViPER4Android, set by an init.d script, so I'm not sure if SELinux has anything to do with it. Looks like if it happens again, I'm not restoring.
[Galaxy S II Android Development] js-xda:
Not sure whether related to the low_ram flag but battery life has improved quite a bit with this build for my rather special use case (operating always on wifi data plus active SIM set to 2G and mobile data deactivated; no GAPPS or alike; basically a non-mobile messenger base). From about 3,5...4,0 days to 5,5...6,0 days (current forecast even 6+ days). I like it! Thank you! :)

Update 16.7.: Turned out to be around close to 5,5 d in the end - still great!
[Galaxy S II Android Development] ale5000:
Hi,

has this ROM got all the features of LineageOS 14.1 or something is missing?
[Galaxy S II Android Development] OllieW:
That's a TWRP problem - if I fresh install ROM and OpenGApps with the "Add more ZIPs" option after a full wipe, the OpenGApps script will abort installation because the environment variables aren't set correctly for the installed Android 9 version. Flashing ROM and OpenGApps separately (install ROM and then install OpennGApps) will work perfectly without any boot loop.
[Galaxy S II Android Development] GeneV1:
Hi,

First and most of all thank you so much to the developer. It's great to have these newer OSes on the good old i9100.

I successfully installed this ROM (lineage-16.0-20190707-UNOFFICIAL-i9100.zip). Seems to work fine (as far as I could test it).

Only exception is Orbot-VPN, where no App gets internet access. Tested same settings on Cyanogenmod 13 and Lineage 14.1, where it worked fine.

(BTW, on Lineage 15 it didn't work either.) Any help for a workaround for this problem (or an explanation why it doesn't work) is more than appreciated.
[Galaxy S II Android Development] rINanDO:
Hi everyone,

For everyone who used my new PIT, please read this!

I'm so sorry I released a corrupted PIT file. Please backup all your stuff on Data and Internal Storage so you won't loose your data!

I updated the links in the OP with the new PIT:

Pit: i9100-LOS-16.0-Emulated-Storage.pit UPDATED ON 15-7-2019 due an error in previous PIT

Yesterday I dirty flashed my develop-phone which was rePITed with ODIN following my new instructions. I suddenly lost all my apps and data after boot except GAPPS.... After reinstalling via ODIN and my new PIT I discovered the Data-partition couldn't be mounted after I installed a new ROM. I ended up Formatting Data-partition again. Long story short I found out my PIT-file wasn't correct. System- and Data partition overlaps! The cause is the buggy PIT Magic which not always saved the the partition offsets and size somehow after I changed it. And I didn't check technically because it all worked fine until I flashed a new ROM which I want to publish....(Restarting PIT Magic and reopening the file everytime to double check my set values.... and retrying)

Again I'm so sorry for this! :crying: I hope the issues with GAPPS Pico and Nano are related to this because of the overlap, System-partition gets corrupted at the end because Data-partition starts there. Updating System-partition corrupts the beginning of Data-partition so you always end up with a corrupt partition. Lanchons REPIT can't fix this either because it detects the overlap and bails out.
[Galaxy S II Android Development] Darkstriker:
I was following the steps for a clean install coming from a Stock Firmware but the phone refuses to enter recovery mode. All I seem to get is the Bootlogo with the big yellow triangle. Download mode still work without any issues. Any ideas why?

PS: Just re-bought the phone for nostalgia's sake.
[Galaxy S II Android Development] rINanDO:
When phone is off you need to keep vol up+home+power buttons pressed until the bootlogo reappears. It should go to recovery the second time it boots.
[Galaxy S II Android Development] Darkstriker:
That didn't do the trick for me unfortunately. Maybe this only works with a certain bootloader? I'm using the one found in the "stock" TWRP thread.

Edit: nvm, got it working. Thanks for the tip. It did help in the end.
[Galaxy S II Android Development] JuanDelPueblo:
This ROM is a decent performer, as long as you let it wait for 5 minutes after booting. Is there any chance at adding exFAT support in the near future, so I can use my SD card formatted as such, and be able to store movies or documents above 4GB?
[Galaxy S II Android Development] Hubalu:
Hi rINanDO, could you fix the issue that causes the SIM card locks?

I havent updated to your latest build because everything runs stable now except that my SIM card gets locked everytime I restart the phone and the switching between networks can cause this as well (if it switches and not crashes).
[Galaxy S II Android Development] Darkstriker:
Alright, I figured out that the problem is that the home button on my device is not responding well and so entering recovery mode was less than reliable.

With that settled I was wondering, can we just un-root the device using the LOS packages or is there something we need to pay extra attention to?
[Galaxy S II Android Development] OllieW:
Any chance that the next release will allow installation on F2FS system partition and the TWRP error while wiping cache partition can be fixed with a new release?
[Galaxy S II Android Development] LeBourrin:
I made a clean flash with you new fixed pit and I succeeded to install LOS 16.

The 2 bugs have gone.

- In TWRP I can now copy files form my computer to the phone with USB storage

- I installed OpenGAPPS pico without bootloop.
[Galaxy S II Android Development] rINanDO:
I'm thinking of removing su for new builds because we can flash official los-su package afterwards.
[Galaxy S II Android Development] Darkstriker:
The standard LOS 16 su-removal zip works, so it doesn't matter much i guess.
[Galaxy S II Android Development] bersem:
I think that the issue with the flashlight is not completely solved . Every time I use the flashlight my battery is completely discharged.

Over the night, the battery is completely discharged.

Regards !
[Galaxy S II Android Development] rINanDO:
You mean the phone doesn't deep sleep after you used flashlight?
[Galaxy S II Android Development] bersem:
Yeah that is what i mean.
[Galaxy S II Android Development] rINanDO:
You're so right! Flash-wakelock is never released. Fix will be in next build.
[Galaxy S II Android Development] rINanDO:
New build is up!

Build #15 2019-07-22

Overall state: Stable

Android build: 9.0.0-r44

Required recovery: TWRP 3.3.1-1

- Updated sources

- Reenabled multi-user in low_ram

- Pinnerservice: Drop camera- and launcher apps, resulting more memory for other apps

- Camera: Fixed autofocus in preview (tested with WhatsApp)

- Set ro.config.small_battery-flag. Deep sleep kicks in 15 minutes instead of 30 minutes

- Fixed wakelock issue after using flashlight once

- Dropped Lineage SU in build, download and install seperately from Lineage website

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-20190721-UNOFFICIAL-i9100.zip
[Galaxy S II Android Development] guest4711:
Thanks for the new update. Is it a known issue that after dirty flashing the build /data is empty? I lost all downloads, contacts, pictures and apps... ;(
[Galaxy S II Android Development] bersem:
No problems at all after dirty flash for me.

EDIT: Lost SU. SU addon reflashed after dirty flash
[Galaxy S II Android Development] guest4711:
This was mentioned in announcement.

I did wipe /system (as I do always when flashing, but I did not wipe /data).
[Galaxy S II Android Development] MaRtYy01:
Very impressive rom. I just picked up one galaxy s2 on 2.3.3,it had bad imei so I flashed it with odin to 4.1.2 and imei got fixed(price was reduced because of that,only 15 euros). Stock 4.1.2 is actually slower than lineage 16 lol,even youtube playback was choppy there. So I flashed this rom following the instructions from the first post(thanks for section especially for coming from stock rom!) and its working flawlessly. Initally it felt laggy but I just disabled animations and its pretty fast now. I can multitask a fairly good amount of apps with youtube vanced playing in the background with minimal slowdown. Only battery seems to charge kinda hard when the phone is on,but its from 04.2011 and I probably need to calibrate it. Also wanna try some games,so is swap ram good for this rom? Or there is already swap memory by default?
[Galaxy S II Android Development] bersem:
I dont know what happend on your device. Btw. i never wipe system when dirty flashing. The reason is that what happend you now.
[Galaxy S II Android Development] rINanDO:
Yes. It was because of the faulty PIT. You need to download this PIT file and apply it. See OP and a few posts back explaining this issue.
[Galaxy S II Android Development] rINanDO:
This ROM already uses ZRAM to the max. Give the device a day or 2 to stabilize because Pie optimizes apps overnight when charging or after full charge. May this is the reason it is charging hard. Battery usage is high because apps and OS in 2019 are very heavy for this device with only 2 cores and 1GB of mem. I don't therfore think that calibrating will help because the battery remaining algorithm wasn't designed for this heavy load and dying batteries. Games like angry birds run fine. I didn't try others.
[Galaxy S II Android Development] sajjads24:
hi

thanks for it :good: good work for me .

please update kernel linux to v4.xx or v5.xx ?
[Galaxy S II Android Development] guest4711:
Totally forgot. Thanks for explanation.

---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------

You know that some closed source drivers for our beloved i9100 require 3.0.x kernel api, don't you?
[Galaxy S II Android Development] Catfish78:
Hello,

after some time, today i´ve tried the newest build, flashing it with repitting with the new twrp. This did work, but after that twrp didn´t want to flash lineage 16, because i did not have an i9100, it said i have an "." . Galaxy point, the new phone... haha. After this issue i´ve done it via Odin, repittet and flashed twrp, and reflashed LOS 16 with pico GApps. Until now it installes the apps from my Google backup, i think it runs faster with all that load than before. And looks great :) . My IMEI was backed up before, but is still there. Temperature is still low until now. So i am now very interested how it will do his job :) . Thank you, Rinando (and all the other helpfull hands) for keeping this eight year old phone alive.

One of the other SII i own didn´t work, hoping it didn´t die while it was lying around.

By the way: did anyone ask Samsung for the source code for kernel update? Maybe it is old enough now.

Edit 1: after opening opencamera, and switching to selfie cam, the phone reboots. Same thing with Cam app in LOS.

Regards
[Galaxy S II Android Development] mirhl:
You know you can shim/wrap apis as you want?

Put aside even so much that you could get android drivers to run desktop linux, nowadays it's not even like there are all those blobs (modem and camera being the only kind of "hard" ones, if even)

5.3 toggled on the open source lima driver for exynos boards, and as I already posted around here even the never-before-seen hdmi support is doable.

This said, it's still incredibly burdening to reinvent the wheel, as the two gentlemen credited in the OP are proving.

And it's not like we are golden stable already, as the last post hints (and that would be important for comparisons during forward porting)
[Galaxy S II Android Development] ale5000:
It is great to see that this is evolving so much.

I will donate money to those that will add a working HDMI support (MHL).
[Galaxy S II Android Development] mirhl:
You can set up a bountysource I guess.
[Galaxy S II Android Development] Catfish78:
Hello,

my Galaxy SII Nr. 2 and 3 didn't have any problem with the selfie cam after flashing the newest build, it works great. I'll reflash Nr. 1 and test it again.
[Galaxy S II Android Development] sajjads24:
hi

can i use camera Mod for better quality picture on i9100 for LOS 16 ?

https://androidfilehost.com/?fid=817550096634742170
[Galaxy S II Android Development] Catfish78:
Hello,

as described earlier, did i upgrade all my Galaxy S2. The last one had a bad board, i've changed it with a spare part i had. The one and only one on which the selfie cam isn' working is my daily phone, all other three works fine as far i am using the functions.

Best things are for me:

- phone keeps cooler

- battery runtime seems higher than before

- and it runs better than ever, snappier and smooth.

Really amazing work. Thanks for this great work :) .

I am looking forward for the runtime with the installed 2000 mAh upgrade battery, old original Samsung.
[Galaxy S II Android Development] ale5000:
[MENTION=2222292]rINanDO[/MENTION]:

Hi,

what is the GitHub repo (related to i9100) where I can add a ticket about MHL and post a Bounty?