yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] K9100ii:
Precisely, but for the zImage image format (not elf) and specific to our device.
[Galaxy S II Android Development] Little Rooster:
Maybe a workourant via Odin is possible??

Safetynet passes on other phones, I read. And Edxposed is advertising that it can pass safety net.

Some modules are very useful to configure the android.

Another issue of the integrated magisk.image ...

My phone drainds battery completely within 5 days when it's POWERED OFF.

I wanted to test if this also happens when Magisk is uninstalled.

But I can not uninstall it.

What's the trick here??
[Galaxy S II Android Development] oldsamsungdevice:
Next release?

Hi again and thanks a lot for the ROM. Can we expect an update/upgrade from the 06.10.2019 release?
[Galaxy S II Android Development] Catfish78:
Hello,

sometimes it is a faulty capacitor on the mainboard. You can find a video about it on youtube, search about it with "galaxy s2 capacitor". It could be something other, too, but with some skills, a soldering iron and a multimeter you can find it out. I would suggest to measure the power consumption with a regulated voltage source on 3.6 v instead of the battery, looking at the amperemeter. Do it all on your own risk!!

Regards
[Galaxy S II Android Development] hagadus:
Hello people, very good instructions and nice rom! Worked right away,

Good work! Thanks a lot! :)

Best Regards
[Galaxy S II Android Development] K9100ii:
Hi, [MENTION=2222292]rINanDO[/MENTION],

I see you have cherry-picked the native exFAT driver, thank you. However, I see you are missing this commit: https://github.com/TALUAtGitHub/and...mmit/0dc727fe94ea18cda800a8b8fe1c5b446956224f You should also include this commit in the 3.0.101 kernel, otherwise, there will be kernel panics when things relating to truncating are done. You may, for example, encounter these kernel panics when trying to record a video.

Edit: also, you're trying to port kernel 3.18 (https://github.com/rINanDO/android_kernel_samsung_smdk4412/tree/android-3.18)??? Great! By the way, you should not include that commit in 3.18 if you want to add exFAT to that kernel. It would be preferable if you implement the driver directly from here: https://github.com/arter97/exfat-linux

Edit 2: Recently, you had committed a few commits to branch lineage-16.0. I have found that the following commits cause either the kernel to be unbootable or cause the OS to bootloop:

https://github.com/TALUAtGitHub/and...mmit/aaf53fe9da9fc761f49143d87b42d9f26a171484 (unbootable, bootloader splash screen loop)

https://github.com/TALUAtGitHub/and...mmit/50e0d45705525af846488971692adba36e0f2ba4 (reverted as part of commit a15354a2dc20869b9ee657679b3ce4685fe63b3a)

https://github.com/TALUAtGitHub/and...mmit/99f985d8dbb166b869a329c95b5d864303511b5d (reverted as part of commit a15354a2dc20869b9ee657679b3ce4685fe63b3a)

https://github.com/TALUAtGitHub/and...mmit/a15354a2dc20869b9ee657679b3ce4685fe63b3a (caused bootloops)

All of the other changes in all of the other commits work fine. I see you have removed some of the new commits. Were these commits for LOS 17.0?

Edit 3: For the Bluetooth stack for 3.18, you could possibly (probably?) use the generic bluetooth stack. If this generic Bluetooth stack works, it would save you a lot of time not porting the mgmt stack, and make the kernel more like v3.18 instead of v3.18 with a few more parts of v3.0. You would switch to the generic stack like this:

1. Set CONFIG_BT to y in defconfig.

2. Remove CONFIG_BT_MGMT from defconfig.

3. Remove mgmt Bluetooth stack files as well as Tizen bluetooth stack files.
[Galaxy S II Android Development] rINanDO:
Thanks for the headsup! I will cherry pick the panic fix with exfat. I'm currently messing things with my branches. Pushed some things to wrong lineage branch. I have noticed the bootloop thing and it is already fixed in lineage-17.0 branch. I needed those commits for system-as-root with backwards compatibility. I just managed finally to boot LOS 16.0 succesfully with system-as-root. Now its time to finally build and boot LOS 17.0 for the first time... to be continued...
[Galaxy S II Android Development] jer194:
The same in 'heimdall' (it worked for me ...):

5. In heimdall (S2 in download mode):
tar -xf i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
heimdall flash --repartition --pit i9100-LOS-16.0-Emulated-Storage.pit --KERNEL zImage --RECOVERY recovery.img

Pretty impressive, to see Pie on S2, thanks! :good:
[Galaxy S II Android Development] rINanDO:
New build is up!

Build #19 2019-11-30

Overall state: Stable

Android build: 9.0.0-r46

Required recovery: TWRP 3.3.1-1

- Updated sources

- Added support for exFAT + NTFS (Thanks to [MENTION=9549206]TALUAtXDA[/MENTION])

- Updated Magisk to v20.1 in lineage-16.0-20191130-UNOFFICIAL-i9100_magisk_boot.img

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-20191130-UNOFFICIAL-i9100.zip

lineage-16.0-20191130-UNOFFICIAL-i9100_magisk_boot.img
[Galaxy S II Android Development] ran000:
The build works well one day here. Thank rINanDO
[Galaxy S II Android Development] Xtreme.Ornob:
Fix for "developer options" crashing!!
[Galaxy S II Android Development] K9100ii:
What are you trying to do with this replacement build.prop? I just compared my almost stock build.prop with your build.prop, and the only modifications I see you've done is replace [MENTION=2222292]rINanDO[/MENTION]'s username with your username. Wiping data again will probably not do anything, and if it somehow does, not installing your useless zip would save time. Is this some type of joke? (I'm presuming it is, judging by your updater-script) If so, this must be one of the worst jokes I've ever seen. Don't take my opinion too seriously. :P

That said, I have only noticed weird labels on some sections of settings on both of my dirty flashed S2's. Screenshots attached.
[Galaxy S II Android Development] rINanDO:
Hmmm I did not changed things intentionally. Just updated sources, magisk and added exfat support. I will check.
[Galaxy S II Android Development] Xtreme.Ornob:
I mistakenly uploaded the files from my device directly without changing the username back to stock ones. I am really sorry for this inconvenience, it was not at all intentional. I tend to modify the build.prop and change the username first. I should have been more careful.

And about the crash thing, i dirty flashed and it worked fine. But on a clean flash, it doesn't open "Developer Options" and throws a very weird error (i forgot the exact error log). I did change the build type from "eng" to "userdebug" which actually fixed the problem for me. And as we are switching from build types, i recommended a data wipe.
[Galaxy S II Android Development] K9100ii:
Probably an error in a change in LineageOS sources, I am on Magisk canary that had no issues before and exFAT support didn't cause this as this issue didn't occur in the previous build with my own kernel.

Interesting, so you've change the build type. I have my build type set to userdebug with Magisk props config. I have just checked the build.prop straight from the installation zip, and suddenly, build type indeed is eng. Now the question is what has caused this? By the way, build type changes don't need wipes.
[Galaxy S II Android Development] mithic:
Hi, i did a dirty flash from 06/10 to 30/11 (with cache & dalvik cleaning) and when i go to developer options it crashes.

It appears "Settings keeps stopping" and under App info & Close app.
[Galaxy S II Android Development] Xtreme.Ornob:
Yeah flash this. No worries. LINK lol
[Galaxy S II Android Development] Xtreme.Ornob:
Yeah that is why. I wonder why that happened. Uploaded another one with the original username now. ^
[Galaxy S II Android Development] mithic:
Hi , i've noticed 2 weird things....

-1. When i press the power button and i select "power off" the phon ok shut down but restart as i have had press "restart"!!

-2. The "Gallery" doesn't show (can't find) the photos i took with the camera and i select as archive "SD Card".

Update:After forced reboot a did again a dalvik &cache cleaning and seems that the 2nd is ok.but the 1st still there...
[Galaxy S II Android Development] essalfiti:
I had installed Google camera ( from open gaps aroma ) it didn't installed but the stock camera had been fixed
[Galaxy S II Android Development] maynereiner:
Works perfectly, but mobile data drain battery

Many thanks for this built! I highly appreciate that I still can use my old hardware!

I was running on stock ROM until two weeks ago as I'm not a heavy smartphone user. But then some crucial apps didn't work any longer because of insufficient security patches. So I finally flashed this built and I'm very happy with it. Everything works fine: Wifi, BT, GPS, camera ...

As long as I'm connected only to phone network battery life is really good. With Wifi it's still quite ok. But as soon as I turn on mobile data I can watch the counter going down immediately. It takes about 7 hours to consume the battery nearly completely and during this time I didn't touch the phone once. My workaround is to connect with mobile data only when needed, but I would appreciate to receive messages instantaneously.

Can anyone point me to how to improve this or where to look for any configuration that might cause this behaviour? Your help is very welcome!
[Galaxy S II Android Development] preclix:
GPS problem

I have a problem with GPS. Waiting a long time for a signal (europe). Exists and work something like previous androids gps.conf in etc? It will help? Thanks.
[Galaxy S II Android Development] Hubalu:
Switching mobile network disables SIM card

Hi,

thank you so much for fixing issue with the locked SIM card.

Still, manually switching the provider does not work properly.

The situation: I'm registered with a roaming network but my own providers network is available. So I dissable automatic network. Then, it searches the networks and shows the list.

When I select my home providers network, it jumps back to the main connection settings page (and maybe restarts the SIM?).

The end: I'm still in the roaming network and automatic network is reselected.

When I'm already in my home provider's network, then everything works as I would expect it. Searches networks, shows the list, after picking the same menu is displayed and automatic network is disabled.
[Galaxy S II Android Development] Little Rooster:
No voice search / speech to text option

Hello,

the keyboard has a microphone button, but when I press the button nothing happens.

In System-Settings: Input method / Keyboards there is only the AOSP Keyboard. No Google Voice input option.

PicoGapps are installed.

Out of despair I have now installed google assistant, google voice search, google go, and Gboard, but there is still no speech to text option available.

What can I do??
[Galaxy S II Android Development] Lioh:
Stuck in Boot Splash

Hi,

I have flashed my S2 according to the instructions in the first post. Sadly it is stuck in the Boot process, only showing the LineageOS splash screen. Before the upgrade to L16 the device was equipped with the latest available L14 version, not sure if that matters.

Greetings

Lioh
[Galaxy S II Android Development] SethGeckoXDA:
On first boot, it needs a couple of minutes. Give it like 5 - 10 minutes and wait.
[Galaxy S II Android Development] Little Rooster:
Hello [MENTION=2222292]rINanDO[/MENTION]

some issues ....

1. Voice Input method doesn't work. No chance to install or activate the keyboard mic "speech-to-text" function.

2. HDMI out doesn't work. There is no signal.

3. Cast to chromecast doesn't work. It connects to chromecast and in the same second it disconnects.

4. Device does not recognize when plugged in car dock.

5. huge battery drain when powered off (tested on two S2)

6. When powered off and connected to AC, problems to boot. It always changes between original green battery logo and new white battery logo.
[Galaxy S II Android Development] Iv4n99:
This isn't a bug.
[Galaxy S II Android Development] Little Rooster:
It isn't??

I have never heard about that a device doesn't boot when it is connected to a charger.

I must disconnect it first, then I can boot. I don't think that's normal.
[Galaxy S II Android Development] K9100ii:
Are you using my kernel? I am aware of this bug and can reproduce it on my own kernels, I'm pretty sure it is to do with the charging current control, and I'm not sure about how I would go about fixing it (maybe need a UART connection to see what the board is doing? Even then, I'm not sure what I could do.) and wouldn't like to remove it as it is useful. I have felt like this is only a very slight annoyance, so I've mostly ignored it. How much does this bug annoy you? I can't imagine it annoying you too much. I will put it as an issue on my kernels thread when I have a new release.
[Galaxy S II Android Development] Little Rooster:
1. I think the Kernel is wrapped into the Emulated-Storage-TWRP-3.3.1-1.tar.md5, isn't it?

2. I am used to reboot my phone automated during charging time over night. Won't work with this issue.

More over this, I would like to use another S2 as stationary media device (if the HDMI would work sometime).

This means it is always connected to MHL power supply, and I would have to disconnect every time before I start the device, and then reconnect. Not a convincingly procedure.

And last, but not least, I guess this issue is possibly related to the battery drain when the phone is powered off ?? There seems to be deep issues with the power management.

Wait, I will explain some more to this issue ....

---------- Post added at 02:19 AM ---------- Previous post was at 02:16 AM ----------

I don't think the battery drain when powered off is a hardware issue. In any case it wasn't a hardware issue before I installed this rom.

I have tested it with another S2, with the same results.

I have tested it over days: Battery full charged. Phone powered off.

After a day the white battery logo (when powered off and connected to a charger) shows around 5% (visual estimated) battery drain. When I boot into system the battery level shows around 10-20% battery drain. Sometimes even more.

(The white logo when powered off mostly shows very different values then the system informations.)

After around 5-7 days in power off mode the battery is totally drained.

When the original 4.1.2 was installed, both phones didn't drain battery when powered off mode.
[Galaxy S II Android Development] K9100ii:
1. No, to have gotten my custom kernel, you have had manually installed my kernel from here: https://xdaforums.com/galaxy-s2/development-derivatives/talus-custom-kernel-lineageos-16-0-t3996021 The kernel in the boot image in that TWRP package is the standard kernel that comes with some older version of this ROM. If you haven't installed my custom kernel from there, then you're almost certainly running the standard kernel that comes with the ROM or the standard Magisk image, which also seems to have this bug from what you're telling me.

2. Interesting use case. Yes, it would be very annnoying in a use case like this. No, it is not related to the power drain issue, I don't have such an issue and have this bug myself.
[Galaxy S II Android Development] ze7zez:
The bootloader first reads the kernel from the boot partition. Forcing the kernel to be read from the recovery partition is done using a key combination.

You can see it on the schematic of the android boot process.

I confirm it with certainty.

I test many smartphone models. This happens on many different devices with the kernel not optimized for the specific device.
[Galaxy S II Android Development] Little Rooster:
The install discription of this rom by rinando is detailed and easy to follow. But I can not find a hint which advices that it is neccessary to flash a specific kernel.

Why is this information missing??

I don't know which of my mentioned issues are related to the rom, and which are related to the kernel.

I will try flashing your kernel now and see if it changes some of the issues …
[Galaxy S II Android Development] ze7zez:
1. Charge the battery.

2. Clear the system, data, cache and dalvik partitions

and reset the boot partitions by adb:

dd if=/dev/zero of=/dev/block/platform/dw_mmc/by-name/KERNEL

3. Remove the battery for a few minutes and insert it again. After a day, check how many batteries are left.

You will find out if you have a software or hardware problem.
[Galaxy S II Android Development] K9100ii:
No, installation of my kernel isn't required. So you haven't. My kernel has this same bug, and it appears to be the same bug that the standard kernel has.

Installing my kernel will not solve your issues, it's a custom kernel you can install which has many additional features. You can install it if you'd like. You have confirmed to me that this issue exists on the standard kernel.

---------- Post added at 04:38 PM ---------- Previous post was at 04:35 PM ----------

That command will not work. That command is for some Qualcomm Snapdragon phones, as evident by "msm". For us, its /dev/block/platform/dw_mmc/by-name/KERNEL.
[Galaxy S II Android Development] Little Rooster:
issues

I have flashed your kernel. The system kernel information showing: "3.0.101-lineage-g8800doc'7 Sat Nov 30 23 28 00GMT 2019" (I think it's the same name as before the flash?)

But anyway, if your kernel does not solve any of the mentioned issues it doesn't make sense for me to install it, because before I go to specific system enhancements, the main features must work!

E.g. it doesn't make sense to update the OS to make installations of new TV apps possible, but on the other hand I can not use them, because HDMI-MHL and Chromecast streaming doesn't work. So it would be pretty useless and it's better to stay with the old android 4.1.2 stock, because everything is working fine there.

Compared to the original stock firmware the only (maybe) important advantage of LA16 is to use payment / banking apps (which I only very very rarely need). All the other news of the new LA16 custom rom is only disadvantage, because most of the main features (which a smartphone should provide) doesn't work.

I am wondering if I am the only one with these problems.

Can somebody confirm these main issues (higlighted), or telling me if these feature are basically working on this LA16 rom, or not:

1. Keyboard Voice Input method doesn't work. (No chance to install or activate the keyboard mic "speech-to-text" function.) ps: solved with Gborad

2. HDMI out doesn't work. (There is no output signal.)

3. System integrated Cast to chromecast (or maybe dnla) doesn't work. (It connects to chromecast and in the same second it disconnects. DNLA devices are even not found)

4. Device does not recognize when plugged in car dock. (so I can not autostart my task-automated car setup)

5. huge battery drain when powered off (tested on two S2)

6. When powered off and connected to AC, problems to boot. (It always changes between original green battery logo and new white battery logo, but doesn't boot.)

7. Sometimes after a restart, the battery level goes down massiv. (so sometimes after less than one hour of use the systems shuts down, because of drained battery)***

8. Error message "system UI stopped". (after boot, or when waking up the device)

***the same battery is working with android 4.1.2 at least 5 Hours with full constant heavy use, and up to one week in standby.
[Galaxy S II Android Development] K9100ii:
The LOCALVERSION for my kernel is the same as the standard kernel so pre existing modules in /system/lib/modules and /system/vendor/lib/modules still work. The kernel build date is different, of course. There is a point to my kernel, which is the additional features it offers, but if those don't interest you, then there is no point for you. I don't really know if the typical smartphone user has use cases like yours. My S2 works fine as a phone with this ROM, but it isn't exactly the fastest phone. No, you are not the only one with the offline charging power on issue.
[Galaxy S II Android Development] Little Rooster:
I am sorry to say so, but the "typical user" is stupid. He makes calls, whatsapp, facebook, instagram and taking photos. He buys a new phone each 2 years, and urgently needs 5G, because he thinks it makes sense that his whatsapp message is 0,2ms faster.

So please don't mention the "typical user" when talking about hightec ;)
[Galaxy S II Android Development] K9100ii:
Yes, you have a point, but in the end, my point is that 0.05% of people use HDMI with their phones. :P
[Galaxy S II Android Development] JaLoou:
Thank you for your courageous report about the issues in LOS16 for Samsung Galaxy S2.

---------- Post added at 01:28 AM ---------- Previous post was at 01:10 AM ----------

Your testament is wrong for this use case due to the users, who use a particular one smartphone model for a very long time (for almost a decade), they use it much more fully fulfledge rather than average smartphone users on the Earth, which change smartphone models often.

---------- Post added at 01:54 AM ---------- Previous post was at 01:28 AM ----------

It can be a trace of a faked power off implemented in the custom ROM secretly.
[Galaxy S II Android Development] Little Rooster:
Most users even don't know what HDMI is. So how could they come to the idea to use it??

I'm not sure, but I think most modern phones don't even provide HDMI anymore? But it's a very importat funktion for media use, especially when your projector doesn't have a networkadapter, or when no network is available.

I have a HDMI Docking station, and a real CarDock (not only a holder). There are so many nice gadgets like this available for the S2, for very small 2ND hand prices. For most modern phones these things are even not existant. The S2 was in the beginning of the innovation and thats why these gadgets exists. That's what makes the S2 very special, and it would be a waste to own this special phone, but not to make use of it's special features.

[MENTION=8356117]JaLoou[/MENTION]

I have tested several android 5/7/9 custom roms. Most of the roms have the same, or equal issues.

That's why I still stuck on my (extremly modified) 4.1.2 stock rom.

E.G. with the 2000mah battery it stays 2 weeks in standby-telephone mode (but without internet).

Most of the "new" impovements which are implemented in modern roms (e.g. app optimazion) I have implented myself with the free task automation tool "E-Robot", in another, but more specific way and without any artifacts.

Unfortunately, I can not change that the development moves on, unnecessarily, and the developers of a few important apps (like TV and Banking) no longer provide updates for 4.1.2.

So I am looking for an alternative recent OS for my S2s ...

A disappointing search, so far :(

---------- Post added at 03:14 AM ---------- Previous post was at 03:06 AM ----------

Could be possible. But I more believe in a bug because of heavy customization of the kernel and other basics.

I also was thinking about a Google "find my device" or "emergency" feature issue. (pico gapps are installed)
[Galaxy S II Android Development] K9100ii:
Take off your tinfoil hat. Now. And welcome back to reality, where you can look at source code and build it. Oh, you can't? Then just stop until you're sure.

There could be some users that just know it's a cable that you plug into places. I personally just use a computer instead of a phone with so much non standard things, the output resolution is higher, too. No, new phones don't support HDMI anymore. The S2 was quite a significant phone, yes, but these days, I think 1GB of RAM and a dual core 1.2(or 4 overclocked)GHz CPU is getting older and slower and we can't keep using it forever. Screen resolution is 800*480, which is considered low today. Accessories for this phone are definitely interesting.

So you're using GAPPS? I'm using MicroG and I get good battery life. GAPPS is an intrusive performance and battery hog.