yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] gm0:
As far as I understand flashing LineageOS should have given you Lineage's own recovery. If you're still booting into PhilZ after having flashed Lineage something went wrong. I suggest you flash a compatible recovery first, I suggest https://dl.twrp.me/i9100/.

edit: also agreeing with [MENTION=4419266]laptopu[/MENTION] above who ninja'd my post. A 1.5 GB system partition is wasted space, LineageOS including opengapps pico takes less than 700 MB.
[Galaxy S II Android Development] laptopu:
I think that's the difference - you've come from a Titanium restore, I've gone totally clean. It was working on a Feb nightly but I can't be sure if it's the latest one or not, that was on a dirty upgrade for me, but since totally clean it's not working.
[Galaxy S II Android Development] ale5000:
If we don't get a review here before tomorrow we won't get the build :(
[Galaxy S II Android Development] gm0:
Yes that's possible, that's why I mentioned it. I had Titanium restore my old system settings so maybe some default settings are bad, not sure. Forgot to mention I also have the phone rooted with the su-addon provided by lineage. Shouldn't matter but you never know. And one thing regarding sounds I had noticed was that the system couldn't find any of the default ringtones or notification sounds, it took 2 reboots for those to appear (I also needed to reboot for root to work properly - basically the system felt like Windows of old where every problem could be solved by a reboot, haha - all working properly now though).
[Galaxy S II Android Development] antrrax:
With rom stock 4.1.2 I enter recovery mode via 'PhilZ-cwm6', and install LineageOS, not reboot. And already install the 'Gapps'. Only then did I reboot the system.

But when start the wizard setup, it appears this message: 'Setup Wizard Has Stopped'. And Google apps do not work.

----------

From that point on if I go into recovery mode and it's Cyanogenmod recovery. But if I try to install the Gapps at that moment, a simple message appears in the center of the screen: 'Error'

I have already tried to put the Gapps image in both the root of sdcard0 and the root of sdcard1 and it is always the same error.

-----------
[Galaxy S II Android Development] shkedov:
I believe our prayers have been answered!

https://review.lineageos.org/#/q/project:LineageOS/hudson

Check out the subjected "add back i9100", it got two V's for cr and v!:fingers-crossed:
[Galaxy S II Android Development] gm0:
I see. You need to have a compatible recovery installed before flashing open gapps, so that's likely what went wrong.

Boot into Lineage's recovery, do a factory reset or wipe of system & caches, then flash lineage and opengapps again, reboot after. If that does not work flash the TWRP recovery I linked and then repeat the above, because TWRP is the only one that's officially supported by opengapps (Lineage's should work as well though so try that first since you already have it).
[Galaxy S II Android Development] Utwoo:
I don't understand, from where do you download this ROM? It looks like the official link doesn't work right now.
[Galaxy S II Android Development] treysis:
Did you only flash LineageOS and GApps, or did you also flash the modem? You need to also flash the modem!!!
[Galaxy S II Android Development] gm0:
There is no official build right now. You can either wait for one (hopefully there will be one tomorrow, otherwise next week) or install an unofficial build. I suggest you wait.

---------- Post added at 16:51 ---------- Previous post was at 16:47 ----------

No you don't, and I strongly doubt the modem has anything to do with gapps setup which is what he's struggling with.
[Galaxy S II Android Development] laptopu:
You need to be on twrp 3.0.2, boot into that, then wipe, then lineage and gapps.
[Galaxy S II Android Development] treysis:
I did reinstall from twrp, but for me it only worked after I installed the modem as well. But I might be mistaken.
[Galaxy S II Android Development] toy_story:
This ROM installs its ril library, but not the modem.
[Galaxy S II Android Development] braniels2:
So the ril will be "flashed and installed" but with the same modem that i have now.. im have xxlms4.

later if i flash the modem the ril will be the same?

sorry if i have bad english...
[Galaxy S II Android Development] toy_story:
The LOS 14.1 ROM does not install or change the modem.

Modems you can install separately, through custom recovery or Odin.

Choosing a modem, this is a personal choice for the phone, which depends on many factors. For example: location, coverage area of the cellular network, from the network operator and so on ...
[Galaxy S II Android Development] PhoenixNZ:
And for there Roms does the modem have to not have ril?
[Galaxy S II Android Development] rINanDO:
I haven't got the time to test this. My dev is now at los15. Has anybody tested this?
[Galaxy S II Android Development] Boolian:
Correct. Do not install RIL.

If you find a flashable modem, choose one which does not include RIL.
[Galaxy S II Android Development] gm0:
Just thought it worth adding that you are using the latest available modem firmware, there are no newer versions. You could experiment with older versions but for most users there is little point to that.
[Galaxy S II Android Development] ran000:
New build lineage-14.1-20171004-nightly-i9100-signed.zip work well.
[Galaxy S II Android Development] braniels2:
Any know if this rom (pico gapps, bln mod without other apps and stock kernel) have better battery life with dorimanx kernel? i came from cm 12.1 with dorimanx (pico gapps, bln and only whatsapp) and have better battery life.

and the only issue when flashing de rom was the setup wizard that show FC, i fix it skipping the option "choice wifi or data connection"

edit: with the new build "lineage-14.1-20171004-nightly-i9100-signed.zip" i dont have the FC in setuo wizard, with clean flash
[Galaxy S II Android Development] ale5000:
Currently I don't have too much time but if someone compile it with the change included I can test it and report back.
[Galaxy S II Android Development] Klaerchen:
I uploaded an unofficial build from the LineageOS sources, including the commit

https://review.lineageos.org/#/c/191362/

to enable the display setting "burn-in protection".

Download links:

ROM: https://www.androidfilehost.com/?fid=962021903579482731

MD5: https://www.androidfilehost.com/?fid=962021903579482724

As it is my normal daily used ROM, it contains also these pending commits:

The last pending commit for Button-Light-Notification (without 3rd-party tools, to be found in the notifications):

https://review.lineageos.org/#/c/179725/

Three commits for network transfer speed in the status bar (status bar settings):

https://review.lineageos.org/#/c/151975/

https://review.lineageos.org/#/c/148321/

https://review.lineageos.org/#/c/113415/

Two commits to replace the SamsungDoze with a more common LineageOS Doze (display settings):

https://review.lineageos.org/#/c/168930/

https://review.lineageos.org/#/c/172637/

and something to hide the root-symbol configurable as status bar setting (status bar settings):

https://review.lineageos.org/#/c/167528/

But beware, as it is an unofficial build, you probably cannot dirty-flash it over an official build and vice versa. So please test it on test device, not your normal working device, in order not to lose data!

Regards

Klaerchen
[Galaxy S II Android Development] mertgirt1:
Hi,

I was installed new rom. But, the back button works by itself
[Galaxy S II Android Development] ale5000:
It works fine.
[Galaxy S II Android Development] mirhl:
So.. Yesterday SiI9234 driver got pulled in mainline drm-next tree, thus I'll take advantage of the occasion to re-post a recent comment of mine here, if somebody is looking for some good day of fun

EDIT: in mainline
[Galaxy S II Android Development] markokrstic:
Hello guys,

I have latest version of CM on S2, so I would like to know how I can upgrade from CM latest build (before they discontinued CM) to LineageOS ? I wanna do this cause S2 with latest CM build is is very slow not every day. If some of you can send me which apps and drivers to install and how to upgrade I will be more then thankful.
[Galaxy S II Android Development] todonormal:
Fantastic!!! MHL support for Galaxy i9100 on LineageOS?
[Galaxy S II Android Development] mirhl:
It just means development effort goes from titanic to medium-hard
[Galaxy S II Android Development] Andrea900:
No. It will never happen.
[Galaxy S II Android Development] ale5000:
I haven't so much hopes but I hope it happens.
[Galaxy S II Android Development] todonormal:
But i found what exist phones LineageOS with support, view: https://www.reddit.com/r/LineageOS/comments/74ifzc/lineageos_141_mhl_microusb_to_hdmi_support/
[Galaxy S II Android Development] bit032:
when you wipe everything you lose system pit?.
[Galaxy S II Android Development] mirhl:
That just means google and/or qualcomm have better (and more forward compatible) blobs.

and that some good dev spent nevertheless his fair share of time to do small adjustments

Here instead even masterminds gave up the effort.

Having finally sources available instead (for as much as for plain linux afaiu), now allow you to take a new route to get to the same results.

Wiping just formats partitions.

Their table remains intact then.
[Galaxy S II Android Development] ale5000:
Hi,

I have two questions.

Is the ROM vulnerable to Key Reinstallation Attacks (that affect Wireless)?

Is the ROM vulnerable to BlueBorne (that affect Bluetooth)?

The softwares that test (BlueBorne in particular) probably look only at patch level but I don't think they test the real exploits, I would like a complete reply.
[Galaxy S II Android Development] Klaerchen:
The commit for BlueBorne is still pending: https://review.lineageos.org/#/c/192488/.

The fixes for Krack are already merged, i.e. will be active with the next build.
[Galaxy S II Android Development] WingedLion:
Are the 2017-10-11 build or any previous builds stable enough for daily use?
[Galaxy S II Android Development] Acid0057:
I'm on the official non-root October 11th build and my capacitive buttons stay on when the screen is off and turn off when the screen is on. Didn't happen on the October 4th build.

Did I do something wrong? I didn't change any settings between flashes. The buttons still work as menu and back fine when the screen is on.
[Galaxy S II Android Development] ale5000:
In my opinion yes,

but I suggest to wait the tomorrow build that contain the fix for the wireless vulnerability that is really serious.

---------- Post added at 21:11 ---------- Previous post was at 21:05 ----------

Sorry to bother but is there a possibility to merge the BlueBorne fix before the new build of tomorrow?
[Galaxy S II Android Development] Klaerchen:
Could you check settings/notifications/gear symbol. Maybe the notification light is active.
[Galaxy S II Android Development] Acid0057:
I don't have an option for Notification light in Settings/Notifications/Gear Icon :(
[Galaxy S II Android Development] toshibashi:
Google app lagging, voice search completely unusable

Hi,

I'm using Lineage-14.1-20170802-nightly-i9100. Great ROM, best Android I've ever seen (congratulations and thanks a lot!). However, Google search is lagging terribly, voice search and voice recognition apps are completely unusable. I've already deleted and re-installed the Google app to no avail. What else can I do?

Best regards,

toshibashi

ps

I'm using the Nova Launcher
[Galaxy S II Android Development] toy_story:
In the settings menu, in the search field write "notification indicator", disable it.
[Galaxy S II Android Development] Klaerchen:
I just noticed, that the last required commit for BLN (i.e. the settings/notifications...) is missing in the build of Oct. 11th. It will be present in the next nightly. Sorry for misleading!
[Galaxy S II Android Development] Acid0057:
No problem. I'll go to the next nightly and check. Thanks.
[Galaxy S II Android Development] Acid0057:
Updated to the latest nightly tonight and it has the option. Turned off and working with no capacitive lights on when the phone is off. Also got the KRACK updates. Running smooth here.
[Galaxy S II Android Development] Boolian:
After latest nightly update, I noticed that capacitive button backlight was on (*edit -with screen on) even though I had it disabled in the Settings/Button menu.

Simply sliding illumination back up, then back to zero sorted it.

Possibly the new Pulse Notification default was the cause . Though the backlight was on permanently, not as a pulsing notification.

Anyway, no big deal, just an observation.

Kudos for the new features & the quick KRACK update.
[Galaxy S II Android Development] WingedLion:
I'm currently using the 18-10-2017 build and "Gallery" doesn't show images.I downloaded another "Gallery" app and it's the same.If you know any "Gallery" app that works,tell me."Files">"images"doesn't show images either and most of them appear as 0 byte files.Browsing "sdcard0" within "Files" works though.Does any of you have the above issue?
[Galaxy S II Android Development] toshibashi:
Google app lagging, voice search completely unusable

*** BUMP ***
[Galaxy S II Android Development] toy_story:
Hi, save everything from "sdcard0" to external memory or PC and format "sdcard0" in TWRP.
[Galaxy S II Android Development] WingedLion:
[/COLOR]

Thanks,problem solved.
[Galaxy S II Android Development] avtandil33:
Hi,

despite of configuring BLN as short or very short seems that it drops any time to permanent light, what increases accu eating a lot. Could you please check ?
[Galaxy S II Android Development] Boolian:
Try resetting the Button Backlight to 'disabled' (Setting/Buttons)

It doesn't seem to play nice with BLN.

I once had permanent button backlight until I reset to 'disabled'.

I also seem to have issues switching it back on since then. I'm still testing, with eg: 5 sec Button backlight. + BLN on/off

The Button Backlight will switch on each time the BLN is toggled either on or off and the backlight remains on for approx 20+ seconds (illumination timeout seems to vary randomly from 10-60 seconds approx (not the 5 sec manually set)

To be honest, I don't use the capacitive Button backlight and I feel it should really be disabled in settings if one wants to use BLN.

It certainly still works alongside BLN (or should I say Pulse Notification Light? ) but is a bit random.

Intuitively, I think having it enabled could mask a notification (especially if set to pulse while screen is on)

I've been testing and would give my results, but there are a lot of combinations. In summary the button backlights appears to randomly illuminate and timeout is usually considerably longer than whatever is manually set.

Other than that, the seperate Pulse Notification (BLN) is working well when the button backlight is disabled.
[Galaxy S II Android Development] cikenkari:
any feedback for working xposed?
[Galaxy S II Android Development] toy_story:
Look here - https://xdaforums.com/showthread.php?t=3034811&page=5
[Galaxy S II Android Development] avtandil33:
Many thanks for your reply.

I tested this on my device. Buttons-> Indication brightness was set to 0 and timeout I didn't touch and is was still 5 sec.

Then I checked BLN work. When new notification is coming, buttons start to blink and after approx. 10 minutes they became permanent lit. Seems that Buttons settings are not affect BLN settings at all - the same behavior was with Button backlight enabled.

Could you please check that.
[Galaxy S II Android Development] Boolian:
Yes, I managed to reproduce that behaviour.

Curious, as I never saw that previously in daily use. As you say, possibly the backlight is not affecting BLN, but I have my doubts.

I also noticed backlight timeout had stabilised to around the actual 5 second mark but was dependent on the app i was using when activated. Some apps held a button backlight longer than others.

Damn! Now I have to mess around and hope BLN starts working correctly again, thanks very much... Lol!
[Galaxy S II Android Development] dumdidum123:
Soft keys not working since I got the first notification with BLN. Disabled them and tried to reboot to get the buttons work again. And I ended up in a boot loop. Wiping cache helped, but I think I will wait until I try to use BLN again. Managed it to live without it for years now, so it will work a few weeks more
[Galaxy S II Android Development] guest4711:
Just checked. I can connect to channels 36 - 47, means 36, 40 and 44.

But I'm using RR now.
[Galaxy S II Android Development] simono_pl:
I still can't. I'm on stock kernerl. I see network but no luck on connect :(
[Galaxy S II Android Development] yupo72:
Hi guys,

I've recently installed this ROM as my device was very very slow with another custom one....anyway, now it seems I'm no more rooted so, how can I root again?

Thanks all
[Galaxy S II Android Development] DevisG79:
Did you flash su addon? You find it on the LOS website.
[Galaxy S II Android Development] Dayhood:
Here is the link:

https://download.lineageos.org/extras

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S II Android Development] bersem:
since last update my phone charge only up to 70-80%. :( :(

before it was all ok. What can i do now to have full charged battery?
[Galaxy S II Android Development] Alex.NoName:
Same problem here. And the 2,4G connection is sometime broken.
[Galaxy S II Android Development] max6698:
No problem here, as the attached image shows.

I'm running lineage-14.1-20171026_113245-UNOFFICIAL-i9100. Although it's unofficial, it's just a regular compile with no cherry picked fixes or any other modifications apart from having root baked in.

Perhaps your problem is related to a wi-fi setting on your device, eg wi-fi region code?
[Galaxy S II Android Development] Kohkaenn:
Hi all,

First time posting, and first time trying to change the ROM of a good old Android phone (I don't even remember the Android version before trying all this, yep that's absurd sorry, surely Ice Cream Sandwich (rooted) ).

So I tried to refresh my old Galaxy S2 to give him a new youth. But problems appeared :

- I successfully followed the tutorial available here : wiki.lineageos.org/devices/i9100/install

- Everything was working correctly, but when I tried to install the .ZIP file while in Recovery Mode (btw my recovery mode is CWM v5.5.0.4), it stuck at "Patching system image unconditionally...".

- So I restarted everything, did a bit of research, and then I understood that I shouldn't try to install LineageOS 14.1 with CWM. With more research, I saw that before all that I should have installed CyanogenMod 13.

- So I downloaded it, put it on my Micro SD card, then tried to install it, always using CWM V5.5.0.4, then I get the following error : " Warning : No file_contextsThis package is for device: "put various devices names here" ; this device is . ". Two line after this, an error Status 7 was displayed.

- At this moment I understood the LineageOS installation destroyed my Rom. When booting, I'm stuck at the "Samsung Galaxy S2 GT-i9100" screen.

- I also tried to edit the "updater-script" file from the CyanogenMod .ZIP file, without any success (error Status 6 all the time).

What should I do to install a proper Rom (even if this is an official Rom) ? Do you have any advices ?

Thanks a lot for reading !

EDIT : I'm just understanding something. If I'm correct, TWRP 3.1.0 should replace the CWM V5.5.0.4 Recovery mode, right...? Or this is just something working in the backend ? Because as stated before, I'm always with CWM despite the TWRP installation seemed to work perfectly using the wiki.lineageos.org tutorial.

EDIT 2 : Fast edit just for saying that after a bit more of research, I found this tutorial : xdaforums.com/galaxy-s2/help/guide-tutorial-samsung-galaxy-s2-i9100-t3538601

For now this is working very well, I just had to edit the "updater-script" files from some of the Djibe package with Notepad++ (before I was using Dreamweaver, this may be related).

Sorry for the inconvenience. At least I hope some of the keywords in this post may help others struggling like me.
[Galaxy S II Android Development] gm0:
All good, after all you figured it out yourself. In the spirit of helping those coming after you, here's the concise version (you were missing the compatible kernel in step 2):

0. Backup your data as needed (don't use Samsung's software for that)

1. Increase your system partition size (using REPIT or by flashing a .pit, in particular in the latter case reformat partitions as needed/wanted)

2. Flash the boot.img from the LineageOS .zip along with TWRP

3. Boot into TWRP recovery and flash LineageOS

May your i9100 never die. ;)
[Galaxy S II Android Development] sky321:
Have you noticed this fork?

https://lineage.microg.org/

Living without google ?
[Galaxy S II Android Development] DevisG79:
Yes. I think it's worth a try anyway.
[Galaxy S II Android Development] gm0:
On a Google OS? ;) Also that's not what it's about, it's just LOS with microG pre-built-in. "Access all the Google services without proprietary closed software" is their slogan.

If you want to reduce the "google" impact to a minimum just don't flash gapps at all. All apps that don't need google cloud or payment systems will continue working
[Galaxy S II Android Development] sky321:
Shure, you are right :cyclops: But it's a step in the right direction, isn't it?
[Galaxy S II Android Development] gm0:
Open source alternatives are always a good thing, although in my experience only a small part of the users will ever check and compile the sources themselves and whichever variant you use, the data will end up at google's servers.

Rather than a doubtful privacy gain the real advantage of microG is the smaller footprint, i.e. it takes up less of your system resources.

Personally, the only part of gapps I run is the swype keyboard library (libjni_latinimegoogle.so).
[Galaxy S II Android Development] sky321:
I totally agree, but it‘s possible to send less data to google with microG and unifiedNlp as with gapps installed. One can disable device and message communication to google and also use a mozilla netlocation provider. So from my point of view it’s more control over my privacy with microG.
[Galaxy S II Android Development] DroidHero2002:
How the hell is the galaxy s2 still alive? Surely most versions of android would have rejected the low specs of this beautiful but low end device by now. Ofc it's always great to see the classics live on :).
[Galaxy S II Android Development] Acid0057:
I have two in use currently. One is just a glorified music and podcast player. The other still going strong as a work phone. Both on android 7.1.2 lineage os 14.1
[Galaxy S II Android Development] blue whale:
after reading this, I tried it and it works well. I have more RAM a tboot with 316MB taken. Maps and offline maps work too.

I am testing the battery drain right now. with los I have 0,6/hour and it seems to be the same with this rom.
[Galaxy S II Android Development] Wolfey7:
Hi, I tested Lineage and I noticed that when I use search bar in stock video player and MX, the video freezes while the sound still can be heard. Is this happening to someone else too? It works fine on Slim KK. It happens on MM and N.
[Galaxy S II Android Development] blue whale:
Lineage keep asking for root when I launch a rooted app. I removed and put root again but nothing is solved.
[Galaxy S II Android Development] toy_story:
Look here
[Galaxy S II Android Development] Nobby1960:
I use two old classics as daily drivers, an I9100 and the subsequent model I9300, both with LOS based Android 7.1.2.
[Galaxy S II Android Development] DroidHero2002:
I'm using 3 devices, 2 being older and 1 being newer. Galaxy s4 mini soon to be on Oreo, galaxy young 1 on android lollipop and a moto e 2015 on miui 8.
[Galaxy S II Android Development] gm0:
Not happening for me and never has. Might be an issue specific to the codec used for your video files though.