yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] kraehetest:
Hello JaLoou,

can you explain more about the camera firmware, or post a link. It sounds interesting, but i never heard about this.

Are there other improvements?

If it deosn't work, how can i restore the old fimeware/files? (Backup in TWRP should be OK?)

Thanks
[Galaxy S II Android Development] Nobby1960:
To have a pitch black background everywhere you must install Substratum and a special dark theme. If you want to have a black background in the settings menu only, just install the latest build from AICP 12.1 (8/21). There you can change the colors with a new feature in display settings.
[Galaxy S II Android Development] toy_story:
[MENTION=8356117]JaLoou[/MENTION]

Or you can install "ViperOS"

https://xdaforums.com/galaxy-s2/development-derivatives/rom-viperos-t3640000

Good black background

Screenshots:
[Galaxy S II Android Development] JaLoou:
Sorry, I'm unable to say anything serious about a camera firmware in Samsung Galaxy S2 due to I'm a noob in smartphones.

May you need to ask Samsung or proper camera sensors producers (some Galaxy S2 devices equipped with a camera sensor produced by FujiFilm) about it directly.

I can tell little only I think that the camera in our smartphone can be improved yet for better functioning at low light conditions and the semi-night-vision trick with A Better Camera app by Almalence proofs it clearly.
[Galaxy S II Android Development] Boolian:
I admire your enthusiasm and your tips have been interesting.

The core problem is really the GPU driver itself.

There are bodies littered around the web who have been trying to perfect an open-source Mali-like driver. The reverse engineering is tortuous. The manufacturers have been asked but it was a universal "No" for information. If some Samsung blobs hadn't been leaked a few years ago we'd be lucky to have a functioning camera/graphics at all!

The Lima driver project was a great hope a few years ago and there are many other ARM/Mali developer forums trying to solve some bug or other. I don't hold out much hope for a major breakthrough any time soon, but the incremental improvements to the camera have been welcome.

Tweaks and tips such as yours also add to the body of knowledge. But to be honest, for camera work, it's not the S2. Not even with Stock rom and drivers was it much good. I have an old 5mp Sony-ericsson W995 (Cybershot) feature phone that kicked the stock S2 up and down the street when it came to quality photographs in all lighting conditions.
[Galaxy S II Android Development] robby2107:
Hello to all,

first i will say thank you for this great development and i hope this will be go on with LOS15. ;)

But i have a little problem since the last few updates:

Sometimes if i get an incoming call, the Display still stay off/black. The only chance to take the call, is to push the ON/OFF-Button.

Is someone working on this bug?

greetings

Robby
[Galaxy S II Android Development] JaLoou:
The ROM developer had answered to this bug here: https://xdaforums.com/galaxy-s2/help/bugs-official-lineage-os-14-1-galaxy-s2-t3649329/page2

I'm more for fixing all bugs in Android 7.1.2 rather than for a new buggy Android O.

---------- Post added at 09:15 PM ---------- Previous post was at 08:21 PM ----------

I suggest measures for fix a bug with a big battery drain, experienced by some users:

the Media Storage app must just use less of CPU performance.

I discover this app drains a battery mostly when many media files are on the internal or external smartphone storage due to this app finds the files, scans they, creates and saves databases.

May it is possible to decrease the CPU frequaincy for this app only?

May it is possible to lower a priority for this app among other apps?

This app read and writes a NAND memory. But a NAND memory is much more slow rather than RAM. So, the CPU haves empty cycles mostly performing this app.

If CPU frequaincy will be decreased for this app only then it will not make this app too slowly but the battery drain will be less significantly.

I think if such measures will be implemented in the ROM then the battery drain problem will be solved finally.
[Galaxy S II Android Development] rINanDO:
I can't reproduce the bug. If you can reproduce, please provide a logcat. It is possibly a RAM issue. Too much apps in memory and the phone needs too much time to switch to the dialer app. Which apps do you have installed?
[Galaxy S II Android Development] Saftpresse99:
Hi,

since two or three weeks the battery draining very fast (Build: 20170816) compared to earlier builds.
[Galaxy S II Android Development] robby2107:
Hello rlNanDo,

i use my S2 as an all-day-device , so i have a lot of apps installed.

Now i have deinstalled some of these apps, cleaned the RAM and i think it´s a little bit better. Actually there are 3-4 seconds between start ringing an switch the display on.

Average RAM using in the last 24h: 91% :eek:
[Galaxy S II Android Development] MARCOSOFT:
Me too, or even longer (+/- 6 seconds).
[Galaxy S II Android Development] PhoenixNZ:
Have seem this delay as well, wondering if it's an issue or the Phone being in a deep sleep?? ? And taking longer to kick up the processor??

May be way wrong..
[Galaxy S II Android Development] rINanDO:
Android keeps the RAM occupied to load apps faster. That's why it keeps at about 85-90%. I guess the lmk kicks in to free memory for the dialer-app to activate causing the delays of several seconds.
[Galaxy S II Android Development] robby2107:
So, you think that´s normal?
[Galaxy S II Android Development] Nobby1960:
[MENTION=8356117]JaLoou[/MENTION]

With the camera issues you are right. Yesterday I compared the stock camera app in 4.1.2, especially in video recording with the Snap solution on 7.1.2. With the stock camera app full HD videos have a much better quality and resolution without artefacts, the reaction is faster and autofocus works nearly perfect. The stock camera has a "very fine" mode in settings. I think this is a driver problem, maybe Samsung does not want to release the drivers as open source.

So much video quality can be extracted from our good old S2 (the recording does not come from me). Look it in fullscreen mode:

https://www.youtube.com/watch?v=0B6EkYqV9Ww
[Galaxy S II Android Development] rINanDO:
The behavior is normal but the delay because of this is unfortunate. I don't know if there is any option to keep the dialer app the highest priority and keep it in memory no matter what. But having that app in memory leaves less memory for anything else... Our device just has not enough memory and it is already tweaked with zram and ksm. Apps are growing larger and larger. Keep in mind we only have 700mb ram and the OS consumes 250-350mb for as for I have seen. On top of that you got Google services and running apps like your current launcher and its widgets.
[Galaxy S II Android Development] trevor12:
big battery drain on 23.08.2017 rom .. I do not know if all august 2017 roms have battery drain but in the past I had some earlier lineage 7.0.x rom and that rom had not battery drain. pls fix it ... (I have same apps across last year so it is ROM problem).
[Galaxy S II Android Development] robby2107:
I don´t have this Problem on my S2.

So I think the Problem is one of your installed apps. Maybe a buggy update?!
[Galaxy S II Android Development] trevor12:
I don't think so. 56% usage from 100% battery only to backup in twrp (that is without running rom). 8 a.m 100%, no calls, no display on, no activities (only wifi on) and in the 12 a.m. I am on 56%, it is not normal ...

what Lineage 7.x rom (nightly) in the past was rock solid for everyday use without significant battery drain ?
[Galaxy S II Android Development] Hawaiihemd:
You just said it yourself: Can't be the rom. Or more to the point, the running system. If you experience such a drain in recovery, I'd say your battery is going downhill.

To be fair: Could (and I emphasize COULD) be kernel related though. But I don't think so.
[Galaxy S II Android Development] Saftpresse99:
I have a similar problem with the battery since a few weeks. I'am running build 20170816. Not such a big draining like [MENTION=4019562]trevor12[/MENTION], but the battery is going down faster.
[Galaxy S II Android Development] JaLoou:
It depends of number of various media files in the internal and external storages of smartphone. As more media files then more the battery drain.

So, not every user experienced such bug.
[Galaxy S II Android Development] Boolian:
Re battery problems.

Never underestimate the power of coincidence. After having 3 devices failing over the last 6 months (two within a fortnight recently) I can now state categorically, it was hardware failure in every instance.

I spent a long time believing various software & nightly updates were probably to blame. Especially given the sometimes intermittent issues and coincidences (problems after a nightly install etc)

After much wailing and gnashing of teeth I finally have a hardware build which is solid, the old batteries I thought were poor are now lasting all day. However, if I do get "drain" in the next nightly and a revertion cures it, certainly I'd be looking at the OS, but not without double checking for component failure (again!)
[Galaxy S II Android Development] JaLoou:
I had investigated a battery drain in my smartphone and it revealed that the hidden Media Storage app drains a battery depending of number of various media files in the smartphone (include map tiles).

May this app is buggy (not recognised .nomedia files in folders). But high probably the ROM developers just must decrease a CPU usage for this app by decreasing the CPU frequiency for this app only and may be another measures.
[Galaxy S II Android Development] gm0:
Media storage is neither hidden nor should it be throttled. It's Android's media indexer that allows apps to access your media files without having to index them themselves. I have no issue with it ignoring .nomedia. Also it indexes files only once, if you don't make changes to the files it will never touch them again.
[Galaxy S II Android Development] trevor12:
so I flashed to 30.08.2017 rom and nothing is changed ... same battery drain .. In battery statistics I see that most power consumption are Google Play services (Google Play services cca 15%, others processes including screen etc. maximally 3 %, I have no calls, no sms, only wifi is enabled, no mobile data, no screen on - ) ... Google Play Services also constantly crash minimally in last three weekly roms .. Window with option what to do after crashing .. Ignore until next restart etc.. what option is best to choose in regard to battery consumption .. ? as temporary solution I set maximal (extreme) battery saving mode ...
[Galaxy S II Android Development] gm0:
Sounds like your problem is with OpenGAPPS and not LineageOS. Try to download and flash the most recent OpenGAPPS package and see if that helps. If not go and clean out the data for all gapps apps/services via the System>Applications view (show system apps). Or just do a clean install (and if you do that consider if you need gapps at all and if not just go without).
[Galaxy S II Android Development] avtandil33:
Hello rlNanDo,

Is it possible add Cyrillic letters sorting in the installed programs menu ? It was available in CM13, but in LOS program sorting is possible only by digits and latin letters...
[Galaxy S II Android Development] MARCOSOFT:
Please, change default governor back to ondemand (IMO, better battery life and stability with little difference in performance vs pegasusq).
[Galaxy S II Android Development] ale5000:
Pegasusq works fine for me.

I think that the battery life is increased a lot of build a go before introducing pegasusq, I'm not sure where.
[Galaxy S II Android Development] gm0:
I love pegasusq on the battery saver cpu profile. I like it very much more than the previous one, it's actually become my default profile for every day phone and email operation whereas with the previous governor I used to use balanced. Very stable and I don't really notice the lower speed (whereas with the balanced profile I find that the CPU's speed stepping is sometimes very noticeable in apps).
[Galaxy S II Android Development] Hawaiihemd:
Got your device rooted? If yes I'm sure with Kernel Adiutor you can set your governor just the way you like. To each his own.
[Galaxy S II Android Development] rINanDO:
Can you tell more why ondemand should give better battery life? Can you share your experience? Have you monitored the behavior with older builds? About stability I heard no complains about crashing, random reboots like we had before with this governor.

My experience yesterday with normal usage I got 17 hours and 30% left before charging for next day. Today google play services used 20% for some reason, which gave me 13 hours to 1%.....unexpected.
[Galaxy S II Android Development] rINanDO:
I actually considered setting that profile when screen is off in balanced mode. But that would give performance issues with a navigation app (Waze, google maps) when you turn off your screen to save battery.
[Galaxy S II Android Development] MARCOSOFT:
Noppy22 is also of the same opinion.

This is the impression I have too!

Issues resolved with version 30/08 (OFFICIAL):

- Fix internal storage summary for non-emulated storage devices.

- Actually, there are only 1-2 seconds between start ringing and switch on the display on.
[Galaxy S II Android Development] :
[MENTION=4296222]MARCOSOFT[/MENTION]

My experiences with pegasusq vs ondemand is on AOKP not Lineage. It's possible there are minor incompatibilities on that rom. I had two random reboots(where I haven't had any since LP) and generally the battery usage was significantly(maybe 20%) greater over a day normal usage. Switched to ondemand for a few days and usage went back to what it was before.

I haven't tested LineageOS to be able to comment about it here, and it seems most people here have no issues. Sorry for OT
[Galaxy S II Android Development] rINanDO:
Which kernel does aokp use? Does it contain the patches to fix pegasusq and does it include the pegasusq powerHAL? The default configuration from kernel of pegasusq will drain the battery.
[Galaxy S II Android Development] :
I use an up-to-date, unmodified Lineage kernel. Unless there are changes/dependencies in system, I don't know why it doesn't seem to work as expected....Aokp Rom control has caused a few issues with hardware buttons, maybe other things as well...Feel free to PM me if you want to keep OT off your thread. :)
[Galaxy S II Android Development] mattberlin:
Hi,

there's an issue concerning HFP audio via Bluetooth:

I got an app that is using HFP in order to transmit audio messages to a car radio. With LineageOS the car radio switches to an incoming telephone call which is the way it is supposed to be.

But there is no audio!
[Galaxy S II Android Development] kepsilla:
I changed with Kernel Adiutor kernel governor from peqasusq to ondemand and also frequency step and lowest frequency to 200 MHz.

Is there some other tricks to improve battery life in governor settings?

I have a feeling , that it improved battery life and GPS sensitivity to CM13.1 level.

With pegasusq governor and 100 MHz steps there was more noise in GPS and less deep sleep percentage.

Also more CPU frequency steps can cause unstability?

I changed to Lineage, because application Xplore update caused boot loop in CM13.1.
[Galaxy S II Android Development] ran000:
What happend with today build - 404 not found ?
[Galaxy S II Android Development] toy_story:
Patience, have a cup of coffee and soon everything will be.

---------- Post added at 13:02 ---------- Previous post was at 12:59 ----------

Everything is working, downloading and enjoying the new build.
[Galaxy S II Android Development] bersem:
Finally flashed yesterday on my GT-I9100P from stock to LOS 14.1. Very fast and stable.. This are the Batterystats.

Can be better ??
[Galaxy S II Android Development] Shambles22:
Substratum latest version doesn't work with LOS and neither with RR. Does anyone know why?
[Galaxy S II Android Development] rINanDO:
Hi all,

:D I'm just dropping an image and a link :D

Click here!
[Galaxy S II Android Development] someghost:
The MHL

Galaxy S2 is immortal!!!

Guys, too many opinions... I don't know which one I can trust. I love my old friend S2. I like this rom too much. But the only way I can stay with this phone is make it connected with tv and use it like tv box. Do I have to choose between this rom and mhl?

Does this rom support MHL?
[Galaxy S II Android Development] dirkovic:
I could kiss you! But I will refrain from it :)

Thank you and everybody involved for their great work in keeping our S2s fresh :good:
[Galaxy S II Android Development] rubentkato77:
Thanx mate! Will try it soon as I get home.
[Galaxy S II Android Development] cherep20:
Hello. Prompt someone faced such problem, wifi is connected, but without access to the Internet (on 6.0.1 all works). Dalvik/Cache wipe is done.
[Galaxy S II Android Development] Spyr0s:
Touchscreen is not very responsive when i'm charging, sometimes i can't even unlock the phone. I'm swiping up but the lock barely moves. Problem started when new power hal introduced.
[Galaxy S II Android Development] Yurienu:
Hi there,

When I installed 20170913 (upgrade from 20170830) I experienced random reboots, I think it was due to a defect in my spare battery but now I can't seem to reboot (boot loop), I tried to flash back .zip file but it doesn't work :/

Do you know what I can do to investigate some logs or something?

I have full access to USB storage and terminal from Recovery ;)

Thanks,
[Galaxy S II Android Development] 1eStar:
Try a different charger.
[Galaxy S II Android Development] toy_story:
Developers LineageOS since September 13 began to work on the official LineageOS 15.0

https://www.lineageoslog.com/15.0
[Galaxy S II Android Development] freecaster:
Since yesterday, after upgrade to the newest lineageos 14.1 nightly snapshot, I've noticed when I connect my phone with my earphones, the device is going to the boot splash and hanging on. But when I remove the earphones, the booting is stoped and phone boots back to the normal. It's that a big bug or am I alone with my problem here?
[Galaxy S II Android Development] EngineJoe:
I'm not experiencing any problem with earphones in 20170920 nightly, however I should mention that I configure the OpenGApps installer to remove AudioFX so don't know what would happen if AudioFX was installed.
[Galaxy S II Android Development] dumdidum123:
Is there a possibility to figure out why a device crashes/reboots?

If I type adb logcat the log just starts from the beginning of the reboot. But I would need the log before rebooting to figure out whats the problem is. I am facing a lot of reboots, so I think it might be a problem with my specific device (hardware maybe?)
[Galaxy S II Android Development] gm0:
Under development options you can choose to store logs persistently so they won't get wiped upon reboot. dmesg is the command to see kernel messages, which is where you are more likely to find hardware related error messages.

Also consider a clean install to see if that fixes your issue.
[Galaxy S II Android Development] freecaster:
I don't use OpenGApps, but apkpure to install the apps which I need. Hmmm, I'll wait until the next nightly. It does not matter with the earphones for right now. It was just very curious, because I trust the nightlies :D
[Galaxy S II Android Development] gm0:
If you mean wired earphones then I can confirm not having any issues, either. No gapps. There is an option in settings to start the default media player automatically when you plug in headphones, if you got that enabled maybe turn it off and see if it helps.
[Galaxy S II Android Development] bersem:
can someone confirm when the phone is in the pocket, does it set the ringtones by itself on silent? why??
[Galaxy S II Android Development] freecaster:
I don't use wired earphones, just cable version. So when I connect my earphones with my i9100, the Lineage OS make a reboot. I could make a video, if you want to see how it happens.:)
[Galaxy S II Android Development] Boolian:
I never even noticed that automatic launch option [MENTION=8075440]gm0[/MENTION] mentioned!

Anyway, fwiw, I've got all sorts including Gapps on the latest nightly and use earbuds with cable/jack input.

No problems at all, with or without the auto 'Launch music player' But, I've just remembered I don't have Google Play Music - do you?

If so disable or "freeze" it with eg Titanium etc. See what happens... iirc Play Music had a problem a couple of months ago, crashing if a bluetooth device was connected at launch. Maybe it was even if bluetooth was on? Don't remember exactly.

Either that or a dirty headphone socket is causing a short, but that's a bit of a long shot for a reboot problem.
[Galaxy S II Android Development] gm0:
wired = cable version (I just wanted to make sure you weren't on wireless headphones which are an entirely different affair). I don't need a video, I believe you, I was just saying that it is not happening on my device so it's not something about LOS in general but something specific about your particular device/settings/software so you'll have to troubleshoot that way. In case of doubt make a backup, do a clean install and see if it's still happening (to rule out a hardware issue).
[Galaxy S II Android Development] dumdidum123:
Because having some problems with full rebooting I decided to reset my phone.

First try, I just deleted data partition via TWRP, but the Lineage Configuration Wizard crashed always when I selected a language.

So I wiped system partition completely and installed the latest nightly + pico opengapps. Now, I can select the language and enter my google account. But as soons as I need to configure the Google-Services (like enabling location services etc.), the wizard crashes and I am at the beginning, where I need to select my language.

What should I do? I have no option to kill the wizard and just configure it manually...

I could restore my TWRP backup, but this was not my plan, because I can't use a phone, which will reboot as soon as I don't use it for a few minutes....
[Galaxy S II Android Development] Nojevah:
Hello,

Unfortunately, BT is not working for making call (Bose QC35). It was already not working with CM13, and it works with stock 4.1.2. If any dev is interested, I can help (don't really know how). Until then I'll consider BT not functional.

[MENTION=7465165]dumdidum123[/MENTION]: I wasn't able to pass the Google Setup Wizard too.

In the end, I realized I didn't need google apps except Play store, so I downloaded app with another phone, and copy/paste them.

Sorry it won't help, I can just confirm that I had your problem.
[Galaxy S II Android Development] jojobg:
Try with different GAPS package, nano probably.
[Galaxy S II Android Development] Hawaiihemd:
Simple solution is to just delete the setupwizard apk via TWRP file manager before first boot.
[Galaxy S II Android Development] polaxis:
Had the same issue. Flashing another Gapps package (like nano or pico) fixed the issue for me.
[Galaxy S II Android Development] Nojevah:
It's not an ideal solution: you can't enable "developer mode". Ikr, that sounds illogical. If you don't install any gapps, you have "developer mode", if you have google services without google setup, you can't enable this menu.

I guess there's a way to do that through TWRP, but in the end, it's better to have a working Google Setup Wizard.

I hope it's only the pico package which is faulty. I did not try nano package. Let's hope dumdidum123 will confirm this.
[Galaxy S II Android Development] mithic:
Today official release failed to build??
[Galaxy S II Android Development] Oxydeme:
Today DL Builds Page throw an internal server error unfortunately :3