yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] rINanDO:
New build is up!

Build #20 2019-12-20

Overall state: Stable

Android build: 9.0.0-r46

Required recovery: TWRP 3.3.1-1

- Updated sources

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

lineage-16.0-20191220-UNOFFICIAL-i9100_boot_magisk.img

And you probably want to peek here:

LOS 17.0 Build #1 (i9100)
[Galaxy S II Android Development] Little Rooster:
I don't want, and I don't need a computer in my Living room / Bedroom / Guestroom.

I have my S2s :)

I stream only HD. Can't see any difference to higher resolutions, because I don't have a ballroom cinema.

I have tried MicroG, but one of the services didn't work. Geocoding (reverse) was not possible.

On my 4.1.2 S2 the google services are no problem.

I know, once the drained up to 50% batterie sometimes, when they where hanging and waiting for their data food. Fixing this is a part of my own app optimazion.

For the GS I have disabled unused services, and I monitored when theyy keep hanging and wakelocking my device. In these situations I do simply automated a force Stopp the services and then everything is resettet and only 2-3 useful services restart running. All wakelocks gone. I have only 2% to max 4% GS battery drain.

With my app optimation my ram loads always only the apps I need, and this way there is always enough space for the running apps. No apps need to be kicked off by the system.

Unfortunately this specific app optimazion (every app has it's own rules) is no longer possible since android 8.1 because the system does not provide any informations anymore about running and foreground state of the apps, which is neccessary for these commands. A bad google trick :(

So I wanted to change to MicroG. But not successfully.
[Galaxy S II Android Development] JaLoou:
I'm sure and I know feasible and much easy rule:

Any good ROM must not have a suspicious behaviour exactly.

If the ROM developers are knowing about this serios issue (the big battery drain even at the power off state) but do not advice about it then such situation triggers an opinion that the ROM developers are trying to conceal something from people - that may this issue is a result of hidden feature secretly implemented in the ROM such as spying for the smartphone users or controlling the smartphones remotely without the users knowledge about it and etc, etc.

---------- Post added at 10:28 PM ---------- Previous post was at 10:04 PM ----------

I strictly and really recommend to avoid it or you risk to get not only the drained battery over night but also the squizzed money from your bank account remotely!
[Galaxy S II Android Development] K9100ii:
Ah, you're back, and you still have a tinfoil hat on you while thinking about *suspicious things* that don't really exist, just like a conspiracy theorist..... how I already knew you were going to come back without doing what I kindly asked of you.

BTW, have you managed to read the source code at https://github.com/LineageOS and https://github.com/rINanDO yet? I really, really recommend you do. This source code is really good for looking at, especially for me when I'm bored! I also suggest you read up on how newer programs and OS's run slower and less efficiently over time on older hardware... it could really help your knowledge!

Ooh, and the conspiracy continues. I am logged into my bank called 'gull&bull financial' on my phone running this ROM, with large funds on my account, and I've never lost anything. You must have some severe spyware on your phone!
[Galaxy S II Android Development] paranoid42:
I think you're both right but anyway should discuss this further in a separate thread.

I.e. can anyone (even a dummy like me) say for sure that the binaries i download and install equal the code basis on github?

I especially also don't have the time to set up a machine to comple the source code myself. Even if i would (and could) do that, to be sure i would also have to read the whole source code myself.

Even if everything might then be ok with the binaries (did anyone check the compiler source code?) i still could not be sure that the installation target would work as expected (because of bit and/or hardware errors).

We all just hope for the best until someone creates a solution that is able to proof itself without any doubt.

Maybe NASA is working on that but i also doubt that until mathematically proven.

Sorry, just my 5 cents.

Thanks a lot to all devs out there working together and also for this rom and else!!!!

(Anyway i admit that the battery drain on my S2 when switched off is also anoying me, that's why i always remove the battery when switched off for some time already)
[Galaxy S II Android Development] SethGeckoXDA:
This is how custom ROM development works:

Developers build their custom ROMs in their free time

Users report issues as good as they can (e.g. by generating a logcat)

Developers fix these issues if they find enough free time, and have the motivation to do so

If you expect bugs to be fixed within a certain time frame, you hire a professional developer, or, more commonly, offer a bug bounty. Making extra noise certainly does not help the matter.

You are right about being careful which software/custom ROM to install on your device. Never download a build from a source you do not trust.

On XDA, trust usually comes with reputation. Reputation is earned by helpful posts (measured by the "Thanks Meter") and having a history of releasing good software.

Your accusations are unjustified and lead to harsh reactions by other users because the developer rINanDO excels in all of the previously mentioned points and therefore is as trustable a custom ROM dev on these forums can be.
[Galaxy S II Android Development] js-xda:
Thank you - installed it today and works smoothly so far. Just the regular lagging after installation of an update and wiping Dalvik cache.

Not that I share the tin foil hat perspective of some but since I can understand that some see it as a bug: Would it be possible to list the battery drain while being switched off as an issue? I know that it is also an issue e. g. with the official LineageOS for Samsung Galaxy S5 LTE+ (G901F) / LTE-A (G906S/K/L) and understand the reasoning stated there that it is kind of tricky to debug a bug occurring while being switched off.
[Galaxy S II Android Development] MaddogIT:
Maybe there is also a UFO launch code inside the rom... I must check...

Of course there may be everithing, you must trust the developers or check the code. Nobody force you to use it, if you don't like it just move to something else. The free time given to create and maintain the rom is priceless, don't vaste it.

It's more likely to find spyware in official code that you cannot control because you don't have the source rather than in freely searchable code.
[Galaxy S II Android Development] DevisG79:
I clean flashed successfully build 20. Works very good. So good that the phone flys by itself. Don't know if that's spyware, virus or extremely good performance. I am afraid that it will fly through the window by itself and then it will get cold at home for Christmas.
[Galaxy S II Android Development] js-xda:
I have no concrete idea and don't have the issue myself but maybe some options to investigate what could be the issue:

Have you tried moving back to the previous build?

Are you using Magisk? Same issue without Magisk?

Are you using OpenGApps or MicroG? Have you tried without or with other build date?

Have you wiped Dalvik cache?

Does any of the above change the observed issue?
[Galaxy S II Android Development] JaLoou:
Yes, I'm also about it and for fixing this serious issue with the battery drain at the powered off smartphone.
[Galaxy S II Android Development] K9100ii:
Oh, you're back after the free for all ended. You get told to stop urging and making noise like this, yet you continue. We get it. Also, this issue is often a hardware issue with a faulty charging filter capacitor. In theory, the phones bootloader isn't even booted when the phone is powered off and not charging, so no one has an idea of how this ROM can cause battery drain when the phone is powered off. AFAIK you don't even use this ROM and apparently mostly haven't read any of the things people are saying. Please use logic and understand that PEOPLE HAVE LIVES and you could be helping fix this issue, but of course, you continue to urge which does nothing and you have already done enough of this urging after it being evident that you can't help fix it.

TL;DR: Stop urging for this to be fixed when no one has the time to or knows how to. We get it.
[Galaxy S II Android Development] JaLoou:
"XDA's Thanks Meter" is not a trustful indicator because it can be easy overscored by making fake 'thanks' from faked nick names on the XDA forum and by other methods too.
[Galaxy S II Android Development] js-xda:
Please learn to read posts of others completely and quote them correctly! Cherry picking phrases of others without context that suit your view is abuse!

Do you read anywhere that I was pushing for having it resolved? No, I stated even that I can understand the problem being a tricky one to debug.
[Galaxy S II Android Development] JaLoou:
A custom ROM development can going not only by the way described by you but by another ways also and can be corrupted too (for example, for secret mass implementation of viruses, backdoors and etc).

My opinion is that all known issues of the custom ROM must be open published for:

1) People know what they install.

2) As more people will know about the issues then more chance that someone will suggest a good way for fixing it.

3) The open publication of all known ROM issues will help to avoid an existing opportunity for secret corruption in the ROM development process.

And finally:

If all source code of the ROM is allegedly open then why the info about the existing known ROM issues is not open?

What the reason for conceal the ROM issues from people?

For people are suffering with they?
[Galaxy S II Android Development] Catfish78:
A tip for thinking about it: take a external energy source with around 3.6 V +/- 0.4 V, find out where + and - is on the battery contacts of the phone, and measure with an amperemeter the milliampere. If there will be a power consumption, your phone is faulty when switched off (maybe a capacitor). And the energy consumption will be there from the first millisecond - useless to say that there is no time for booting anything.

Regards
[Galaxy S II Android Development] JaLoou:
Unfortunately, the XDA forum user

'rINanDO' has a history of releasing ROMs suspiciously hungry for power consumption and it was proofed by me once in the messages with screenshots on 1st page of this topic: https://xdaforums.com/galaxy-s2/help/bugs-official-lineage-os-14-1-galaxy-s2-t3649329/

The continues attempts to hide the power consumption issues in his custom ROMs are only double increasing the serious suspicion that some secret activity is hidden in his ROMs.
[Galaxy S II Android Development] ChronoMonochrome:
So you're mentioning in your "proofs" post:

This doesn't really prove anything.

Because you can't precisely know what is a capacity of the battery, you don't either know what those 39% are.

Installing a different ROM and then checking the power loss over the same time (with the same apps setup) could show at least how those % are compared with % of charge loss on another ROM.

But since according to other users responses, it seems like you don't really listen to what other peoples saying, so that could be kinda a waste of time for me doing so.

What are proofs behind these conspirology theories? A "double increasing the serious suspicion" is, of course, a very strong argument.

With custom ROM development you either trust developer or if you don't, nobody prevents you from building the ROM yourself.

Or simply don't use it either, if you don't have enough knowledge to build it yourself (anyway better than to build conspiracy theories).
[Galaxy S II Android Development] K9100ii:
If anyone is interested, the stuff with [MENTION=8356117]JaLoou[/MENTION] probably started here: https://xdaforums.com/galaxy-s2/development-derivatives/rom-t3555834/page182 This user has actively ripped on developers many times from what started as a small bug: not being able to install OTA updates. I've watched it all, even seen [MENTION=8356117]JaLoou[/MENTION]'s posts before I was a XDA member thinking about how disrespectful this member was. Why he or she didn't think of booting into recovery and then installing there thinking maybe this bug will be fixed in a near release is beyond me. From the start, this user has been extremely inconsiderate at ROM developers and their actual lives they want to do stuff in and not understanding anything about what goes into these ROMs. The thread started by [MENTION=8356117]JaLoou[/MENTION] shows nothing more than not only his or her inconsideration, but how unjustifiable the arguments are.

I don't think we can do anything to make [MENTION=8356117]JaLoou[/MENTION] think differently and more logically, but I think we should just ignore this very bad example of a member of the community, and make it so that this member is now nothing but a memory... Just have to hope new users see the issues with this member and decide if they would like to use this ROM or not without influence of this member.
[Galaxy S II Android Development] Negan:
It seems you have a bit if a history of passive aggressively making conspiracy claims and such. If you have any actual fact based evidence then please send us a report with said proof attached. If not please stop with these type of posts. It is so unnecessary. You should be happy anyone's even still supporting this device and take what is being shared with you instead of making wild claims. Also you mentioned an experiment you did as being proof. Sadly that is not proof of anything. Proof would be definitive logs noting said issues. Now even if you had gathered logs and such there is one important thing worth noting. No one is forcing you to use another person's shared work which I may add was done free of charge and in their spare time. Which would also mean no one owes you anything. So I'm going to ask you nicely to cut it out with the silly crap and either contribute to the thread or to log off and take a break. It's also just impolite and poor forum etiquette.

Now let's move on from this please and thank you.

Merry Christmas everyone!
[Galaxy S II Android Development] JaLoou:
Ok.

There was the message on 2019 December 19 where an independent user of the smartphone (his nickname is 'Little Rooster') reports about the several existing issues he experienced with the custom ROM promoted in this topic on the XDA forum: https://xdaforums.com/galaxy-s2/development-derivatives/pie-i9100-t3850588/page91

It is possible to find the smartphone user report about the ROM issues on the page of this topic following the link provided above and also on the 1st screenshot attached to this my message.

After that moment the custom ROM maintainer with the nickname 'rINanDO' did NOT enlisted the new known existing issues among the list of issues which he is publishing at every public promotion of his custom ROM in this topic on the XDA forum.

So, he did produced an incident to conceal the known existing ROM issues from people making a false perception that almost all issues (except the call recording) are allegedly solved.

Everyone can see it on the 2nd, 3rd and 4th screenshots attached to this my message.

Moderator, please take appropriate measurements to the XDA forum user 'rINanDO' for he newer repeat it again.

Moreover, I'm suggesting that it must be added as a rule in general on the XDA forum that if an exact existing ROM issue is known to a ROM promoter then it must be announced by him at his every public promotion of such ROM. It is good for avoid false expectations, problems and futher tensions between people.
[Galaxy S II Android Development] JaLoou:
but lure me and other people concealing the existing well known issues.

I think it must be forbidden on the XDA forum.
[Galaxy S II Android Development] dag4004:
Hello,

First, thanks for that ROM that I use for month with great success without gapps.

It is very fluent and I am happy to be able to still use my SGS2 in 2019.

Today I have tried the phone encryption but I seems not to work.

We I activate it, it ask me the password, it warn that it will be unrecoverable, I accept.

Then I see a Android drown on a black screen with clock hour on the top left.

And the device reboot just after.

Do you have an idea about what I am doing wrong ?

Best regards.
[Galaxy S II Android Development] Negan:
I've sent you a private message as this is a

development thread

and as such and out of respect for our OP, no further off topic discussion about this shall be made here. Read it, comply, move on.
[Galaxy S II Android Development] rINanDO:
Hi, you're welcome. I have no idea (yet) why encryption doesn't work. And how it supposed to work...and when it broke when it was working. Anyone has an idea how it work technically?
[Galaxy S II Android Development] K9100ii:
Hi

Sometimes, this is an issue when there is not enough space for the crypto footer near the data partition. If I recall correctly, resizing the data partition to be slightly smaller allows the crypto footer to be placed and encryption would be successful. There was a post on this from another user here on this thread some time ago. Otherwise, some people are using F2FS which is known to not really support encryption (maybe there are updates to it that add support for encryption?).

How does everyone have their phones perform with encryption (for those who have it working)? I imagine it would be considerably slower, due to the several year old eMMC flash and no hardware encryption.
[Galaxy S II Android Development] rINanDO:
Hi,

I never used HDMI on the phone before and don't own hardware to test this. I do see some commented code about HDMI but probably you are right that it never worked and never considered as normal feature of custom ROMs. So I can't fix this.

Battery drain can't test that either because I use my s2 as daily drive since you need a sim to reproduce. Can you provide a logcat? Maybe the phone sometimes hangs during shutdown somehow.
[Galaxy S II Android Development] kololee:
Hello!

So, I installed LineageOS 16 on my Galaxy S2.

It works pretty much ok, but MAC address is corrupted and need to restore efs zip.

The thing is, I have no root access? I installed Root Explorer and tells me that the device seems not to be rooted.

Any helps here?

Thanks in advance
[Galaxy S II Android Development] MaddogIT:
Look to previous posts...

https://xdaforums.com/showpost.php?p=81259771&postcount=912

If you flash lineage-16.0-20191220-UNOFFICIAL-i9100_boot_magisk.img after flashing lineage-16.0-20191220-UNOFFICIAL-i9100.zip you can use Magisk for root
[Galaxy S II Android Development] ran000:
Use Magisk as MaddogIT suggest or ( may be more simple ) use addonsu-16.0-arm-signed.zip / addonsu-remove-16.0-arm-signed.zip from https://download.lineageos.org/extras
[Galaxy S II Android Development] kololee:
Thanks both!

I tried to post another "post" but xda didn't allow me.

I installed adb on my pc, SuperSu on my phone, tried different things, in the end, somehow (I don't know how), I got back the correct MAC address, and was able to connect to the wifi, so I think everything in my S2 is working now. The only thing I haven't tested yet is the SIM and making a phone call, but I guess is gonna work.

Very very thank you
[Galaxy S II Android Development] K9100ii:
[MENTION=2222292]rINanDO[/MENTION] hi,

What has happened with the kernel sources? Git history appears to be rewritten. There have been some new commits, commits with content that was there before the rewrite and commits that have probably already existed before the rewrite in the past 3 days, but after those commits, there are old commits from June 26 2018 and older (of course). Some commits that have existed before this rewrite, most noticeably for exfat support, don't anymore. Would it be possible if you could explain why was this necessary? Are you attempting to make this ROM official and are doing this so the kernel is more likely to be accepted?
[Galaxy S II Android Development] mirhl:
As a matter of fact, it did happen to work somehow in early CM9.

Perhaps it's the good old fast dormancy?
[Galaxy S II Android Development] ze7zez:
exFAT in the Linux kernel? Yes!

Despite Microsoft's declaration, the existence of exfat support in the kernel is still a sensitive topic.

P.S.

Moderation in this forum leaves much to be desired. Total stupidity is ignored, and interesting statements are castrated.
[Galaxy S II Android Development] rINanDO:
Hi, uhm I hope I didn't messed things up... I tried to merge commits of i9300 to this branch so it will build for i9100 and i9300 and works for both. I needed a revert of an old commit and fix this properly. Rewriting history with the fixed commit was less work. However I probably broke exfat? Not intensional. I'm on vacation so I can't fix this now until Monday.

Edit: I was searching for the exfat commits in my other draft lineage-16.0 branches but they we're not there also.... I probably broke this quite a while ago.... before los 17.0 :( My bad.
[Galaxy S II Android Development] rINanDO:
I never build cm9 or used it. Nice to know that it worked back then. I know we had to upgrade the Mali blobs somewhere in cm 12-13? Probably the HDMI blobs doesn't work because of that....

Fast dormancy.... I need to investigate what it is.

Thanks for the info.
[Galaxy S II Android Development] mirhl:
I mean, as I mentioned in the thread, it's gonna be probably easier to do something by backporting the new mainline driver by now, than trying to resurrect the blobs.

But IANAD.
[Galaxy S II Android Development] rINanDO:
Where can I got those sources?
[Galaxy S II Android Development] Little Rooster:
Hi riNando,

HDMI is a very cool feature of the S2, as I allready explained to TALUAtXDA.

e.g. you can use the S2 as a better Chromecast via dlna. So it's like a Chromecast with display. You can comntrol it remotely from another S2 with TeamViewer. Very comfortable, much more possibilities and at least cheaper than a chromecast ;) You can find a HDMI Dock vor 5 bucks on Ebay. It is realy worth the little money. It's a very good multimedia solution.

I have lots of S2 all for different things.

Yes, I think the powered off batterie drain is maybe because of a not proper modem shutdown, or so. It drains around 20% per day, what is around the same like the cell receiver uses.

When I plug in the battery without booting/shutdown it doesn't drain battery.

Another strange thing, when the phone is shutdown and I plug it to a charger, it is automatically booting sometimes.

All this is obviously related to a not proper shutdown.

I'm sorry, I don't have a logcat. But it shouldn't be a big problem for you to find a SIM and test it.

Hopefully you can solve this important issue.

Best,

Rooster
[Galaxy S II Android Development] ChronoMonochrome:
Hi,

here you can find those sources - https://github.com/Sekilsgs2/i9100_kernel_mainline_port/issues/1

Unfortunately, no git history is available. Just was curious to see if there's anything that could be reused on i9300, so I'll try dig into that to see what changes were made.

UPD. for anyone who might be interested - I splitted up changes to LK 4.20 into a small isolated commits, so it's easier to track changes.

https://github.com/ChronoMonochrome/android_kernel_samsung_smdk4412/commits/lk-4.20-i9100

Can't test it since I don't own i9100, but these sources in the same state as original ones (and it compiles fine)

Credits to [MENTION=5368296]sekil[/MENTION] for his work.
[Galaxy S II Android Development] Catfish78:
Well, i know it is slower than the S2, but can anyone try to give a something newer OS for the S3 mini? There is no one who is working on it anymore.

Regards