yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] ol1ver:
Due to the sad demise of my n7100 (broke the screen; waiting for replacement) I switched to using the i9100 as my daily driver.

Even after upgrading to the 0811 version #16 I think; the PUK code thing still remains.

Related log in the attachment, just after rebooting after installing the 0811 build

With that out of the way; I think i tracked down the high battery consumption down to:

After only 30 minutes of uptime (with top running, to prevent the phone from going into deep sleep) we see that ksmd is a heavy consumer. When 'using' the phone it is not using less (always going between 10+ - 25% at least). KSMd (Kernel Samepage Mergemanager) seems to be always active. I had a few days of uptime (2 - 3) and this number was in the huge range. Looking at the mm kernel /sys node, it does seem to be quite effective (50% shared pages?) but at a very high cost (assuming this is the cause of my problems).

So no matter what network connection I use; in my pocket, it's fine, it can last for a day or two easy. But actually using the phone, is a cyclone on battery drain. If the KSM scanrate is really high, it of course saves memory, but at a very high constant CPU load, and thus very high battery reduction rate. (and toasty fingers).

Anybody able to confirm this theory? Does this somewhat relate to the low_mem=true flag?

I'm not carrying about gapps (any variant) and only use fdroid/aurora, but that is me specifically of course.
[Galaxy S II Android Development] rINanDO:
Nice finding! I could try to disable ksm in a test build and see it has better effect. Thanks for the log I will check it.
[Galaxy S II Android Development] Czeh:
this post is mistake. Moderators please delete it
[Galaxy S II Android Development] Czeh:
for rINanDO

Hi rINanDO! You wrote ab.new version from 11.08.2019

1. I will set this build #16 2019-08-11 on phone with custom rom (Omega) not stock.

How to install your build correctly in this case?

2. Am I right understand that Build #16 2019-08-11 can have in self root ?

This build rooted, right ? If I think mistake, where insrtuction located about root instalation ?
[Galaxy S II Android Development] K9100ii:
Hi,

I have tried disabling KSM and seeing what effect it has. I have disabled it with kernel adiutor (you can also disable it with many other kernel managers or the terminal with "echo '0' > /sys/kernel/mm/ksm/run"), there is really no need for a rebuild of the kernel, or even a full build of the whole ROM to temporarily test and decide if it is worth disabling. In my testing, not only does it improve battery life (considerable increase!), but it improves performance significantly as load on the CPU is reduced very much. Disabling KSM means slightly increased RAM usage of course, but I think it is worth it. I remember disabling KSM on LOS 14.1 and having much better performance and battery life, but decided not to in this ROM for whatever reason.
[Galaxy S II Android Development] JaLoou:
The feature implementation request

Hello.

Sorry for mistakes in my English.

I recommend to implement an useful feature in this ROM, which makes the screen super bright on our old Samsung Galaxy S2 making it visible under the direct sunlight even similar to modern smartphones.

This feature is in the latest Samsung's official firmware with Android 4.1.2 but it is trycky to get it there.

Below I will explain how I usually get it on Android 4.1.2 when necessly:

1) Disable the Media Storage app.

2) Run the Samsung's standard camera app.

3) Switch it to the video recording mode.

4) Go to the app settings and switch on 'Outdoor visibility'. The screen will become super bright.

5) Start to record a video and then stop it immidiately. The camera app will crash (due to the Media Storage app was disabled) but the screen will remain super bright and visible even in a very bright enveronment.

It will be good if the ROM developers will research how the Samsung's standard camera app makes the screen super bright and then to implement this feature in the custom ROMs as a switcher accessible easy by the user without the long trick or may switch on it automatically by the brightness sensor under the ambient light only.

Warnings:

1) This feature is needful only for use in very bright conditions such as under the direct sunlight and etc.

2) It can trigger an eye strain in other light conditions.

3) The super bright screen produces less number of colours than in other screen modes.

4) It can trigger the battery drain.

5) May it can last the OLED screen when using long displaying a constant image only and at least I recommend to avoid to use it with a white background for long.
[Galaxy S II Android Development] Czeh:
for linusdan

Hi linusdan ! You recomended for me instruction for correct installation Lineage ROM.

Please, is that advice now useful for ROM Linage Build #16 2019-08-11 ?
[Galaxy S II Android Development] K9100ii:
High brightnesses are a bad idea for our ancient AMOLED screens. In my experience, people set high (very often near full) brightnesses on their (AM)OLED screens, expereience (AM)OLED burn in and finally wonder why they've got it, only to have the option of a "burn in reduce" app/video that significantly reduces the lifespan of the display and makes colors look extremely wrong if left for a time that is too long and I wonder how they seem to get no eye strain. I think we have brightnesses 0-around 50% purposely set to 0% to help reduce burn in, which I think is a nice idea until people just raise it even higher. I know you have mentioned it in your warnings, but such a thing is a bad idea for our screens, and this seems to be something Samsung only intended to be used for one specific use case (taking photos/videos) for a short time. If we really, REALLY need to implement this, then it would have to be implemented as a higher brightness for the usual brightness toggles, and stay with pure, no extra "bloat" type of apps, LineageOS. (Or it's just that I'd like that if this really has to be done. :P)
[Galaxy S II Android Development] Catfish78:
Hello,

maybe i'm wrong, but isn't there something implemented for better readability in direct sunlight right now, with higher contrast and brighter colours? I am happy how it is right now... for longer lasting battery, the brightness has to be set to a lower point, but that's no problem, rethinking that this is the same on every device for less power consumption.
[Galaxy S II Android Development] linusdan:
Yeah, works :)
[Galaxy S II Android Development] JaLoou:
I use the super bright screen trick for years purposely only in very bright environments like outdoor at sunny days and I newer got burn-in issue in the display of my very old Samsung Galaxy S2.

Also it does NOT trigger any eye strain when used purposely in very bright environments only. Everyone can check it with Samsung's latest official firmware with Android 4.1.2. The colours will be good feasible under the ambilight.

The super bright screen is very useful and helpful feature on our old Galaxy S2. Please, implement it in your custom ROMs by the way easy to use.
[Galaxy S II Android Development] K9100ii:
You've ignored most of the things I've said. Yes, you may use such thing for very short periods of time. For eye strain, I'm talking about people setting high brightnesses everywhere, even indoors. Of course we can check, but that is intended for use in short periods of time and not any normal use for clear picture in light. We're quite literally running the phone out of specification if we set the display to such brightnesses! I'm talking about colors after the burn in has happened. Unless you like a permanent image on your display and a tinge of a color, mainly yellow/orange (are there any other colors?), on it then this is a bad idea. I forgot to mention that our phone suffers from overheating issues, and they will be worse as the AMOLED display takes a lot of power especially on high brightnesses which will cause the power management IC to run hotter and thermal throttle the CPU more than it already gets throttled.

Also you said you're happy with 4.1.2, why don't you stick with it like you said in your "bugs" thread?

[MENTION=2222292]rINanDO[/MENTION] please don't implement this if you'd like to save yourself from headaches from people that complain about this ROM seemingly destroying their screen over time due to high brightnesses and reporting high temperatures and more thermal throttling. This is not a good idea for preservation of the ancient displays, performance or any person holding this phone while it's thermal throttling (touching hot things thermal throttling at 60C+ isn't very pleasant)!
[Galaxy S II Android Development] EmulaMind:
No particular feedback as any issues I've experienced have been mentioned (active use high battery drain, PUK issue), just wanted to say thank you for this ROM - I love that I can still use my S2 with Android 9 as a backup device in 2019!
[Galaxy S II Android Development] JaLoou:
The screen is not hot when acts in the super bright mode. Moreover, the glass over the screen is a very good cooler.

Samsung allows to use the super bright screen mode and for a long time also when using the camera app. For instance, it is possible to record a long video for several hours using the super bright screen mode.

So, it is all according to the device specification.

Please, implement the super bright screen mode in your ROM by the way easy accessible for the users.
[Galaxy S II Android Development] K9100ii:
I am talking about the CPU/processor!!! Look at what I'm writing more properly! The glass barely does anything and all the heat goes to the back of the phone, where it has nowhere to go! The heat is not on the display, it is on the power management IC which gets hot due to the high amount of power usage from the AMOLED display! The power management IC is right near the CPU on the other side of the board from it, where heat will be partially dissipated to the CPU! I would know because I've opened S2's to see the cause for overheating.

This quote "super bright mode" was only intended for use on the camera app. The picture is going to move, which will not really cause burn in all that much, just some wear to the pixels, unless you like to take still videos for some reason which very few people do. The only static elements would be camera control buttons, which may as well be the only things that are going to burn in! (Like stop recording button) This is nowhere near meeting normal specification where there are going to be a lot of static elements instead of a few!

[MENTION=2222292]rINanDO[/MENTION], again, DO NOT implement this feature in this ROM. This person is extremely delusional!
[Galaxy S II Android Development] Byteman3D:
Hi,

I have a S2 9100G model and I've noticed there is a seperate thread for this model. Does the Oreo or Pie versions for 9100 work for 9100G, too? Or would it brick?
[Galaxy S II Android Development] K9100ii:
Hi,

The G variant of the S2 uses a different TI OMAP 4430 CPU, and the non G variant uses a Samsung Exynos 4210 CPU, so unfortunately, installing a ROM from the non G variant to a G variant would brick it. You can only use G variant ROMs on a G variant phone and non G variant ROMs on a non G variant phone. Unfortunately, I only see unofficial LOS 13.0 as the latest for the G variant, but it would still have much better app compatibility than stock 4.1.2.
[Galaxy S II Android Development] JaLoou:
When the device Samsung Galaxy S2 records a Full HD video then its CPU works hot.

So, if Samsung had impemented the super bright mode at the videorecording in its original Samsung's firmware then it is a normal condition for the power management IC and the smartphone CPU.

And there was not reports about burn-in or any other tech issues at using the super bright mode in Samsung Galaxy S2.

Moreover, if we will pretend that the power management IC will be little more hot at using the super bright mode than usually then it will be not for nothing but for the good reason only: for the user was able to use the screen comfortable in very bright environments.

So, there is good only and nothing bad.

Please, implement the super bright mode in your ROM.
[Galaxy S II Android Development] K9100ii:
This ROM has overheating issues on the power management IC and then CPU, while the stock firmware doesn't have anything as bad as this ROM (again, we have no idea where its coming from unless its CPU load). Do you even know much about this ROM? It is certainly not normal conditions as something in this ROM overheats the power management IC and then CPU to over 60C. This feature was only ever intended for the camera app, where you would mostly have a moving picture and few static buttons and not anything to do with normal use. You're ignoring what I'm saying again. Of course there weren't any reports, because no one used it for normal use and only the camera app, so that makes no sense.

Unless you like bad performance and unbearably hot hands and want to quicken the burn in process, then this is a bad idea. The power management IC will not be a "little" too hot, that's an understatement, it will be VERY hot. The screen is already fine at maximum brightness outside, so I don't know what the purpose of this is.

Since when was this a good idea?

Finally, could you please look at what I'm writing properly, think more logically, and stop trashing this thread with your delusional garbage? By the way, if [MENTION=2222292]rINanDO[/MENTION] looks at these posts (he probably will, maybe in disbelief), what will be done will be decided, but I think he already knows very well of burn in and the overheating issues and (possibly?) has implemented some burn in prevention (0% brightness for 0-around 50% or brightness slider) and you insulted him for his work in your "bugs" thread so there are lower chances of anything like this being done and there is also a possible sense of you being ungrateful for what he has done as you've shown in your "bugs" thread for LOS 14.1.
[Galaxy S II Android Development] JaLoou:
Sorry, but you are not able to know about all users of Samsung Galaxy S2 around the World and how they use the device.

For the instance, I use the super bright mode for very long time include the trick to use it outside of the camera app and I do not have any tech issues after it for years.

I think that many the smartphone users found the item 'Outdoor visibility' in the Samsung's camera app menu also.

Moreover, Samsung had implemented the super bright mode in its newer flagman smartphones by the more useful way (it turns on automatically if the brightness sensor detects very bright environments such as at sunny days outdoor). So, almost all users to use it now with newer Samsung's flagmans.

If this custom ROM has the issue with the CPU overheating and the ROM developers know about it then this issue should be clearly mentioned at every public promotions of this ROM for notify people about it and to do not lure they for become victims of this ROM.

Currently, on the 1st page of this topic there is mentioned only an issue with call recording.

Thus, if the CPU overheating issue is existing then it should be enlisted publicly among other known issues of this ROM

otherwise

if the overheat issue does not exist then the screen super bright mode can and should be implemented in this ROM.
[Galaxy S II Android Development] rINanDO:
Hi, after a week is your battery performance still improved? And what about cpu temperture? I can't tell any hard numbers on my experience because my usage differs day by day. Normally my battery life is about 12 hours before it reaches 15%, when using facebook, whatsapp occasionally.
[Galaxy S II Android Development] K9100ii:
Hi,

Battery performance has improved slightly, and has mostly improved in background usage as I can often have no (or else a small) drop in battery percentage from the last time I used it or from charging in sleep. I usually listen to music on my phone and the battery drains less. CPU temperature can still get high if the CPU is on full load for some time, however, it gets higher slower and in normal usage where load increases and decreases, there is an certainly a noticeable improvement in temperature. Overall, there is less thermal throttling. I have to say I use greenify for a lot of apps, disable background and on boot permissions also for a lot of apps using LOS "privacy guard" and disable GMS in MicroG for most apps so I might have slightly better results than some people. I see. By the way, Facebook is regarded as one of the biggest battery draining apps, especially in background. I suggest using a web browser with notification support if needed or using Facebook Lite and Facebook Messenger Lite instead, you could have slightly better battery life. :) Unless you're already doing either, as your battery life suggests, in which case you can ignore this advice.
[Galaxy S II Android Development] ol1ver:
[MENTION=8035227]Rlando[/MENTION] I am trying [MENTION=9549206]TALUAtXDA[/MENTION] 's method of disabling KSM, and it stopped consuming in top :)

I'll read the documentation to see if we can keep it enabled, but only run it periodically. Having it do a sweep once every 5 or 10 minutes may be a nice compromise, if it does save any significant amount of memory. (anything under 10% is debatable I would say). As I listen to a lot of music or use it as a hotspot, this matters quite a bit in terms of battery usage/heat.

A nother issue I have found, is that some settings are not kept after a reboot. Very specifically the display timeout. It is set to 30 seconds by default; it feels like it's doing it at 10 seconds, but changing it to 2 minutes, my preference, works great, until after a reboot, where the menu says 30 seconds again (still feels like 10 seconds; I should time it at some point to see if my feeling is accurate in any form ;)

The second thing that doesn't seem to get rememberd is permission to install from untrusted source. I have f-droid and aurora installed; and I have to grant permission to install apps from there after each reboot. While not horrible, It does indicate something is a miss. edit: Also 'terminal' is gone again :( so I notice I have to re-enable quite a few 'settings' and items.

That said, let me report back in a week to see what my real experience was. As I use this phone as my daily driver now, I do use the phone a lot, but as I am still waiting for my n7100 to be fully up again, I haven't migrated all my favorite apps (signal for example). I think I am going to install it however, to get a better idea for my normal usage pattern.
[Galaxy S II Android Development] ol1ver:
microg

Also, maybe somebody else knows/noticed; I'm having trouble getting microg setup proper.

I have it installed and setup almost right, except for phonesky spoofing seems not to be working and unifiedNLP isn't registering properly. GMS claims to be working and connected, but signal fails to find it, and claims my GMS isn't working properly, and thus falls back to background connectivity (slurping battery).

I'll try re-reading the docs, but thought it was as trivial as installing the microG packages through f-droid (using the microG repo).

Maybe I have overlooked something? This rom has 'everything' enabled to properly run microG right?

---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------

Also a curiosity I had; whilst reading the initial post(s), it was written that the 'default' size of the /system partition was aking to become to small, and it better be increased to 1.5G. Not knowing what the size of the ROM really was, I figured, might as well be future proof and do 1.75G. Turns out, the ROM takes only 950-ish megs. Those additional 500 mb, are those 'reserved' for people wanting to install the full Gapps suite in /system? Or is there some other reason we may want to reserve that much extra space. Thinking of going down to 1.25G for /system as I have no intention of ever running gapps anyway (only microG and F-Droid).
[Galaxy S II Android Development] bersem:
Hello everyone.. What means this? Drive-App?? It appears many times
[Galaxy S II Android Development] xrad:
Your phone is in car mode. I don't have a device available currently to check, but there should be switch for this in quick settings (ie. the notification shade.)
[Galaxy S II Android Development] bersem:
But i didn't turned on. Sorry can't find this..
[Galaxy S II Android Development] xrad:
There's a quick setting tile called "system profiles", you may have to edit quick setting tiles to add this. Car mode is hiding behind that one.

Edit: I didn't check but perhaps system profiles are also accessible under system settings, so you may want to search there first.
[Galaxy S II Android Development] Czeh:
Hi! Is the release lineage-16.0-20190909 stable ?

Which Odin version need use In this version from 2019.09.09 ? Odin3_v3.13.1 or ODIN 3.07 ?
[Galaxy S II Android Development] JaLoou:
Hello.

Sorry, please answer me:

Is it possible with this ROM to record videous by a file size more than 4GB on an external microSD card formatted exFAT?

Is there 4GB file size limitation remained?
[Galaxy S II Android Development] oldsamsungdevice:
Build instructions

Hi, thank you very much for this amazing ROM and all the work you do!

Could I please ask you for build instructions? Also is it possible to compile my own kernel for this (and where does one get a good .config)?

Thanks again!
[Galaxy S II Android Development] K9100ii:
Hi, [MENTION=8145312]linusdan[/MENTION] has made manifests for building this ROM here: https://github.com/linusdan/lineage_manifests The instructions are in the README also right there when you go to the repository in a web browser. Downloads are going to take a while and sources are going to take a lot of disk space, though! Compiling your own kernel is possible and that's what I'm doing myself, you just have to do

mka bootimage

instead of brunch.
[Galaxy S II Android Development] oldsamsungdevice:
Awesome! I'll have to look up what manifests and brunch/mka is. I'm used to make olddefconfig && make xconfig. I have zero knowledge of android development.

Thanks again!
[Galaxy S II Android Development] rINanDO:
It is stable, it is a test build which I almost want to release. New build will be out soon.
[Galaxy S II Android Development] Czeh:
Thanks for your work.

After flash the ROM and Gapps how can do skip turning on to Wi-Fi and type password ?

I can't skip this step and can't completely load the system. Button with skip have not on that page.

How to solve it ?
[Galaxy S II Android Development] bradhoschar:
Guys, asking questions is fine, but keep the rukus to a minimum. If someone doesn't answer you right away, you wait. You. WAIT. People have lives outside XDA. If, after 48 hours with no reply, how about sending a question in a PM?

I will shut down all spam and flaming posts and won't hesitate to give infractions.

I said good day.
[Galaxy S II Android Development] noobgs2:
Hi,

Thanks for this amazing ROM and all the work you do, to keep this old smartphone alive.

As off now, I use my galaxy S2 for Music Playing Only.

With Root and V4A, this works perfectly.
[Galaxy S II Android Development] rINanDO:
New buid is up!

Build #17 2019-09-13

Overall state: Stable

Android build: 9.0.0-r46

Required recovery: TWRP 3.3.1-1

- Updated sources

- Fixed color issues in screen recording

- Implemented Outdoor (bright sun) display mode.

Automatic outdoor mode behavior is disabled by default.

WARNING: Use with caution! Continuous usage in this mode will degrade your OLED display!

- Disabled KSM (Kernel Same-page Merging) for better overal performance.

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

lineage-16.0-20190913-UNOFFICIAL-i9100_magisk_boot.img