yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] nospamboz:
Why I stick with i9100

The looks I get from my family when I tell them I'm still using my nearly-7-year-old s2: priceless. Especially when I do more with it than they do with their smartphones.

Still, I sometimes wonder how much longer I can use it. AT&T killed 2G recently, is 3G far behind? (Still 2G on T-Mobile, necessary in some rural areas.) Then there's the leaky BAT1 that killed 5GHz wifi, and affects the auto-time-zone setting. (I think.) Then there's the issue of finding replacement batteries...

The fact is, though, I hold onto my s2 because it's all I want. It's the right size, right screen, does everything I want. If it ever dies, I'm more likely to buy a refurbished one from Hong Kong than any new-fangled one. (As long as I can keep the software up-to-date. Thank you, LineageOS!)

(Discussion may be better suited for another forum.)
[Galaxy S II Android Development] jt12345:
GPS performance: official build vs microG

I've just done a quick comparison of the GPS performance between a cleanly-installed lineage-14.1-20171108-nightly-i9100-signed.zip and a cleanly-installed lineage-14.1-20171117-microG-i9100.zip. (I should explain that I'm swapping between the 2 roms on 1 single i9100, so the hardware is *identical*). The microG variant is *much* faster to fix (between 2 and 5 seconds for the microG rom vs between 20 and 60 seconds for the official rom) and although it's only subjective, the gps signal also seems to be stronger and more stable on the microG variant.

I thought that the only changes that microG made were to replace Google’s proprietary core libraries and applications with their own home-grown (open source) code, so I'm confused - I don't see how these changes would make a difference to gps strength and stability.

Is there any way to bring these improvements over to this official lineage rom?

Kind regards, Jaime
[Galaxy S II Android Development] ale5000:
Does someone know why we don't get a build this week?
[Galaxy S II Android Development] MauroRTR:
according to their subreddit

https://www.reddit.com/r/LineageOS/comments/7ddxba/infrastructure_problems_ie_where_are_my_builds/
[Galaxy S II Android Development] kudos1uk:
Is it OK to stick with Lanchon IsoRec TWRP recovery 2.8.7.0 I already have on the phone?

Don't worry I flashed 3.1
[Galaxy S II Android Development] toy_story:
LineageOS is Adding a Quick Settings Tile for LiveDisplay - https://www.xda-developers.com/lineageos-adding-livedisplay-quick-settings-tile/
[Galaxy S II Android Development] corvus.corax:
The Lineage ROM gave new life to my S2. Except for no 4g and an outdated camera, it works great. This ROM is really fast! I have run into one problem, though. 3rd party camera apps, like Snap camera, no longer recognize the external SD card. Is there a setting I have not discovered or is something else going on? I see Quickpic, my file managers, and such all find the external SD.
[Galaxy S II Android Development] MauroRTR:
S2 i9100 doesn't have 4G
[Galaxy S II Android Development] Nobby1960:
In Snap camera I can select between internal and external SD to store, see my screenshot. It's from my S3 but it works also with the S2.

Edit: The right screenshot is from the S2.
[Galaxy S II Android Development] corvus.corax:
I know! That was my point. A great phone but for the lack of 4g.

---------- Post added at 12:30 AM ---------- Previous post was at 12:27 AM ----------

I know it should be able to pick the external SD. But it's not working right. It did the first time I upgraded from stock 5.0.1 to Lineage 7.1.2. But then I tried RR (curious type that I am) and it stopped working. So, when I reinstalled Lineage, it continued not working. I guess I should probably go back to the beginning - 5.0.1 - and reinstall as cleanly as I can.
[Galaxy S II Android Development] blue whale:
I have the same pb, I just do ''reset the settings'' in SNAP, then force close, then open again.
[Galaxy S II Android Development] corvus.corax:
So I did a clean install of lineage. When asked, I set up the SD card and then I redownloaded snap camera. This time, snap let me select the SD card. But then it gave me the same message as before - Insert an SD card before using the camera. I use a 32gb card. Reformatting the SD card didn't do help, nore did trying a different SD card. As I mentioned earlier, other apps like the file manager recognize that an SD card is installed. Any suggestions?
[Galaxy S II Android Development] raecer:
First of all, thanks for keeping this great phone alive all these years :)

I updated yesterday and was using it as a hotspot (with vpn) for torrents. I had a few (from what i could tell) spontaneous reboots during those few hours. I don't know if it was related to the activity yet or if it happens either way. Was charging my phone at the same time and the phone was a getting a little bit hot but seemed to work fine again after each reboot (not really cooling off in between).

Just wanted to report this in case it helps.
[Galaxy S II Android Development] kudos1uk:
I wonder if it is related to this?

https://arstechnica.com/civis/viewtopic.php?f=9&t=1323137
[Galaxy S II Android Development] corvus.corax:
Yes, I was just about to write that that was the conclusion I came to. I thought those restrictions went away with Nougat, but I guess I was wrong. So, for example, QuickPic asks and receives permission to use the external SD. It seems that Snap Camera does not, nor do many other apps., like Dolphin Browser or Nova Launcher :(. I will just work around them like I did in KitKat.
[Galaxy S II Android Development] Nobby1960:
You're right, I did test different versions of the Snap camera - you can switch to ext. SD, but there were no pictures saved. Seems like a bug.
[Galaxy S II Android Development] gm0:
I don't know if that helps you guys but the Snap camera version/variant that comes with LineageOS handles external SD access just fine, as does any app implementing the storage access framework (introduced long ago with Android 4.4, i.e. only some "ancient" apps should still have trouble with this).
[Galaxy S II Android Development] robby2107:
I hope the devs find a solution for this problem. The GPS-Signal is very bad on my S2 too.

Greets

Gesendet von meinem GT-I9100 mit Tapatalk
[Galaxy S II Android Development] max6698:
I can confirm that. The camera that comes with LineageOS on my device handles works with the external SD card.

i9100:/storage/57f8f4bc-abf4-655f-bf67-946fc0f9f25b/DCIM/Camera $ ls -al
total 2464
drwxrwx--x 2 root sdcard_rw 4096 2017-11-24 08:51 .
drwxrwx--x 3 root sdcard_rw 4096 2017-11-24 08:50 ..
-rw-rw---- 1 root sdcard_rw 2512908 2017-11-24 08:51 [B]IMG_20171124_085104.jpg[/B]

If you're wondering why my external SD card is mounted at the ridiculously long mount point /storage/57f8f4bc-abf4-655f-bf67-946fc0f9f25b, it's a consequence of having an EXT4 filesystem on the card.
[Galaxy S II Android Development] gm0:
Does that work correctly now? I used to run into all kinds of ACL trouble with that since some of the system was hardcoded to expect the emulated FAT ACL's apparently and didn't set them correctly on file/folder creation. The statement at the time was that the LOS team had no plans to support it, either.
[Galaxy S II Android Development] max6698:
Going by the creation dates of files on the card, I've had it formatted as EXT4 since February this year. I have had no issues yet. Your mileage may vary.

If you've got a spare card lying around, why not give it a try? You may have to format it using a shell command.
[Galaxy S II Android Development] gm0:
Weird, didn't work for me and a bunch of others later than that. Guess I'll give it another try one of these days, you never know. Thanks.
[Galaxy S II Android Development] kudos1uk:
I just updated to today's build, google play services comes up "checking information", I enter my details and 2 step authentication, it comes up "checking information" again then closes, if I open play store it just does the same again.

I restarted

Forced play store stop, cleared data and cache

I cleared cache on framework

If I go into accounts there are no accounts, if I try to add google from there, same loop as above.

Still the same any ideas?

EDIT: I cant create any accounts, even if I try to add my dropbox account that was there before the update it comes up "failed unknown error".

Also cleared dalvik & cache but no joy, it just wont save the account details, it's like there is some write error not being able to save any account details?

MTP host has stopped could that be relevant?
[Galaxy S II Android Development] ran000:
Today build Lineage and today build opengaaps work without problem here.
[Galaxy S II Android Development] kudos1uk:
I have 2 x S2 one updated fine and works the other has this problem.
[Galaxy S II Android Development] ale5000:
I suggest to get the latest opengapps and flash them again, then clear the data of Google Play Services.

Maybe it fix the problem.
[Galaxy S II Android Development] kudos1uk:
Thanks for that, I was just considering that as the next step.

EDIT: no good, still the same, running out of ideas, think I need to flash the update again maybe I had a bad download.
[Galaxy S II Android Development] Xenxda:
Hi everyone,

I'm using an old build 14.1-20170119-UNOFFICIAL-i9100 and I remember I already partitioned to install it.

Can I update to the latest version directly? Do I need to install a new recovery?

Sorry I didn't follow all the discussion and thanks for any help.
[Galaxy S II Android Development] TriboDoP:
No, make a clean install using latest isorec twrp recovery ( which is i think 3.1.0.0 which sure will do anyway).
[Galaxy S II Android Development] kudos1uk:
even re flashed the ROM and still nothing, look like i'm gonna have to wipe it unless anyone has any ideas, i'm sure it must have something to do with account information storage as I cant create any accounts when I create a dropbox account it fails and says unknown error, but I get a notification on my pc of a log in so dropbox is accepting the login attempt but clearly my phone cant save the details in settings.

Same as Google, I get asked to confirm the login attempt on another phone but my phone just can;t save the login details for the next use?

EDIT: Reset phone and all sorted....
[Galaxy S II Android Development] corvus.corax:
I just got my first OTA update. It seems to have wiped out some of my home screens (I use trebuchet). I am not sure what's going on, but I can easily re-add them. Also I am getting a frozen screen on home page..

One other problem - actually it was there in the previous build - when I boot the phone and open the file manager, I get a message MTP File Host Has Stopped. What is that about and how to fix it?
[Galaxy S II Android Development] TriboDoP:
This message doesnt give any trouble and has been around here for ages. So do as we all do: Ingnore it!
[Galaxy S II Android Development] corvus.corax:
Okay, thanks.
[Galaxy S II Android Development] kudos1uk:
Who can explain this.

My two S2s both identical setup, one certified in google Play and one not certified?

https://photos.app.goo.gl/LhBMpYFFk81BZP6w2

How can I have a certified phone on a custom ROM?
[Galaxy S II Android Development] gm0:
Instead of ignoring better go into settings>apps, select to show system apps, find MTP Host, open and then disable it so it won't ever bother you again.

That system component has basically been broken from the start, I'm surprised it's still being shipped in that state.
[Galaxy S II Android Development] corvus.corax:
Thanks. I suppose it is just a nuisance and therefore a very low priority thing,
[Galaxy S II Android Development] max6698:
The uncertified phone may be rooted. If you previously installed addonsu from https://download.lineageos.org/extras it may have survived reflashing your system partition, like opengapps does. (Unless you wipe /system before you flash.)

To test that idea, "adb shell" from your PC or open a terminal on the device and enter the command "su". If you don't get "permission denied" it's a rooted device.

If your device is rooted and you want to change that, install addonsu-remove.
[Galaxy S II Android Development] TriboDoP:
[MENTION=5710255]kudos1uk[/MENTION] about certified phone

out of curiosity i checked all my s+ and s II (all rooted on custom-roms from KK to Nougat) and they are all uncertified.

and i have 2 oneplus one (one on oreo other one on nougat - both rooted and customroms - and both are CERTIFIED ?!?[COLOR="Silver

maybe rooting with magisk can give this result (but one opo is rooted with SuperSu other one with magisk) so i really don`t know.......
[Galaxy S II Android Development] max6698:
If anyone's wondering, the screens in kudos1uk's previous post can be found under the settings screen within Play Store.

I have 3 android devices. My S2 (i9100) and S5 (lentislte) both run Lineage OS compiled by me with "WITH_SU=true". So they're both rooted and come up as "Uncertified" in the Play Store settings as expected.

My other device is a Lenovo Tab 2 A10-70F. Lineage OS is not available for this device but I'm working on it. It's also rooted but it's rooted using Magisk. Because of that, it passes Google's Safety Net and comes up as "Certified". I rooted my A10-70F in this way so I could pass Safety Net and run Netflix. I couldn't give a stuff about it on my other devices :)

Does your i9100 which is certified use Magisk?

Does your i9100 which is uncertified also use Magisk but may have used addonsu, supersu or something else previously which may still be hanging around?
[Galaxy S II Android Development] kudos1uk:
Neither device has ever had Magisk, both have addonsu, I have not added supersu apk, just flashed the addon.

Both had an TWRP reset before upgrading to Lineage and both were on official CM 12.1 before the upgrade.

Both are also rooted
[Galaxy S II Android Development] guest4711:
Afaik magisk will not run on our SII... Or did you manage it?
[Galaxy S II Android Development] Corsa83:
Now I have some spare time, I am gonna give a new life to my old s2 (stock rom) by LineageOS but I have a doubt about the baseband/modem: I am from a diferent country with a specific carrier (my phone comes CSC configured for that carrier; not multi-csc stock rom). In fact, my device runs an animation for that carrier at boot time. Is this gonna be a problem when I flash LineageOS? I mean it is gonna recognize my SIM card and the signal stregth/bands are gonna be ok? is LineageOS a multi-CSC ROM?

As far I now I need to backup the /EFS from my Samsung device (IMEI, Modem file...) just in case any problem happen. Also, that folder is never overwritten during a flash process, so if it all goes correctly... LineageOS will be using my modem file, no? or I am gonna need to use the *#272 USSD code trick to select the specific CSC (by using my IMEI).

Sorry for the noob questions, I am learning quite a lot before asking :D
[Galaxy S II Android Development] gm0:
[MENTION=8478082]Corsa83[/MENTION] basically all of what you wrote is only relevant for the stock ROM. LineageOS does not modify your baseband/modem firmware.

You should however make a complete NANDroid backup of your phone to your external SD or your PC in case you ever want to go back. And of course make sure to backup app data you want to keep like contacts and such in a format that you will be able to import into LineageOS -- in other words, do not use Kies for that.
[Galaxy S II Android Development] Boolian:
That's really only an issue if you want to flash back to Stock Rom. Finding the correct Stock Rom with relevent CSC.

Your Baseband/Modem should stay the same after flashing LineageOS. (Independent of CSC)

Your SIM should not be affected in any way. Your Baseband remains the same and so your connection should not be affected.

Always a good idea to have a backup of your EMS directory (IMEI, NV_data.bin) etc. when flashing roms.

Country/Carrier specific modems can be flashed in Lineage (if you can find them) Some do experiment with different modems to find possible improved connections via "newer" modem firmware.

If you do wish to try that at some point - Do not flash a RIL, or a combined Modem/RIL file- Flash modem only.

Couple of links I found on my travels which may interest you:

An old S2 modem thread - worth a read of posts #1-5 (some links are broken) Here

A link for the most common "newer" Modems for the S2 Here

Useful list of Carrier specific Firmwares Here if you are trying to identify an old stock firmware to revert back to.
[Galaxy S II Android Development] Corsa83:
Firstly, thank you both for your quick reply. Is good to know that is only a concern in a stock ROM context. That makes perfect sense because the EFS folder is protected against flashes, so it's logical to no be modified (I think Odin has an option to flash it if you want; the modem). Obviously it is quite recommended to make a copy before hand in order to avoid future issues. That's one of the main reasons I gonna get root, for using the EFS Professional backup program (I wanna repair some corrupted files with root before wipe the phone).

[MENTION=8075440]gm0[/MENTION] I'm using TitaniumBackup for copy particular apps configuration and I am planning in use NandDroid backup to image my system state before try LineageOS. I use Samsung Kies only for copy very basic things like multimedia files or contacts. Anyway is very good to you pointing me to that (many new users never backup things and then **** happens :S)

[MENTION=6724217]Boolian[/MENTION] Very useful links!. Interesting reading. Thanks!. You both solve my doubt about CSC. Now I am reading about custom kernels hehehe. I am a developer and I never did any serious tweak to my Android phones, so I really enjoying the thinkering thing.

Another silly question I had:

At first I planned in use the TWRP recovery (flashing it with heimdall) and do the nandroid backup thing from there, but I wasn't sure if it would wipe my phone in the process. As far as I know, is the unlocking what triggers the wipe of your phone (for security reasons) and is a requirement for flashing a custom recovery/ROM. Apparently, Samsung devices comes with unlocked bootloader so my doubt is: if I flash TWRP in a Samsung phone it would wipe my data???
[Galaxy S II Android Development] gm0:
EFS is a separate partition and it's not protected against anything. Frankly I wouldn't worry about it and just stay away from it but that's up to you. Also as long as you're aware that installing LineageOS will wipe your existing system so file repairs are rather futile...

Nothing triggers a wipe of your phone unless you trigger it. But you'll both have to re-partition your device and wipe system and data partitions, anyway, that's why you need to make sure to have a proper backup for the data you'll want to keep. Think of formating your PC's hard-drive and installing a new operating system, it's the same thing.

You can safely flash TWRP but you'll also need to flash the LineageOS boot.img along with that (or any other IsoRec compatible kernel) since TWRP is not compatible with your stock kernel. It's probably easiest to find one of the many install guides for LineageOS in this thread or elsewhere and take it from there. Most I've seen are unnecessarily complex but they should all get you there in the end. Installing a custom ROM is only "scary" the first time you do it.
[Galaxy S II Android Development] Boolian:
[MENTION=8478082]Corsa83[/MENTION]

LineageOS Wiki. Is as simple as it gets.

I'd suggest the following Tips:

ExternalSD card for holding your files.

Install TWRP

Repartition phone as you prefer with Lanchons REPIT Tool recommend a minimum of 1gb system partition - try not have a typo when setting all the zip file parameters...

*Format Preload Partition via TWRP - ext4*

Flash LineageOS

Flash Gapps if required - Eg. Arm-7.1-Pico

Gapps can be added at the same time as LineageOS, but I find results vary - Flash LineageOS first and boot. Then back to recovery and flash Gapps if you wish.

LineageOS downloads do have a flashable Root add-on available if you so wish, but is not required.

There is a seperate Uninstall Root add-on available also.

*The Root add-on does show an error when flashing - Ignore.

Root requires to be 'switched-on' to your preference via Developer Options. It will be disabled by default after flashing*

Good Luck.
[Galaxy S II Android Development] gm0:
That was actually fixed a while ago.

edit to add: Also reminder that without an IsoRec compatible kernel TWRP won't load up, that's why I mentioned flashing LineageOS's kernel separately as well. TWRP's own installation instructions do mention it though.
[Galaxy S II Android Development] Boolian:
Oh? Thanks!

I did not know that. Haven't used it in a long time.
[Galaxy S II Android Development] gm0:
Me neither, but I did get the notification from jira when the bug report was resolved. ;)
[Galaxy S II Android Development] elwhiteboy01:
Installed LineageOS 14.1 on Samsung Galaxy Tab A 9.7 SM-T550 and works fine, but there's no sound! Any suggestions?
[Galaxy S II Android Development] Acid0057:
I don't mean to be rude but this thread is for the Samsung Galaxy S2 GT-i9100 phone. You might have better luck in the Galaxy Tab forum.
[Galaxy S II Android Development] Saftpresse99:
Hi,

i'am using this rom almost since the first release.

If i take the phone in my pocket and i'am going to a festival for example, where are many people around the batterie drains very fast and the phone becomes hot. Internet access with many people around me is not always possible. Sometimes it took minutes to send a whatsapp message.

A few weeks ago i travel with a train and put the phone on a desk. The train drives through tunnels and the phone on the desk becomes also hot.

Somebody experienced the same issues?
[Galaxy S II Android Development] Teekanne3000:
Hello,

can't take videos with the rear camera with WhatsApp. Photos with the front and rear camera are possible. Videos only with the front camera.

Microsoft translator crashes also when using rear camera.

Battery drain seems to be higher while using WiFi as cm 13.

The "open with ..." dialog doesn't react on the area with the latest used app, as before on cm 13. It only reacts on the lettered buttons.

Greetings

Teekanne
[Galaxy S II Android Development] vbracer:
Why does the proximity sensor Power up (flashing red) when in the lock screen? This must use power unnecessarily.
[Galaxy S II Android Development] Klaerchen:
DI'd you activate settings/display/ambient display/pocket or hand wave? It uses the proximity sensor to wake up.
[Galaxy S II Android Development] Pr0xiMUS:
RSS

If someone needs RSS feed for LineageOS SGS2 downloads, you can use this https://feed43.com/sgs2_lineageos_downloads.xml

I had this one laying arround for CM and now it is adjusted for lineage.
[Galaxy S II Android Development] dumdidum123:
Same here, even on a fresh installed device with no apps installed. Never found out why, but it won't drain much battery as you usually don't watch the lockscreen that long. After unlocking the device the proximity sensor is disabled again.

---------- Post added at 12:14 AM ---------- Previous post was at 12:08 AM ----------

Yes, but I think it is quite normal, that the battery is draining faster when your device is always searching for the network. When you are in a train, your device must connect to the next cell very often, which costs more battery than staying at one place.

Could be the same with places with many people. The network is overloaded and can't handle all requests from all devices. So your device is sending the data again and again and again. I always switch my device to 2G only in such situations because most people use LTE or 3G/HSPA so it is often more likely to get connected via EDGE. And WhatsApp is even possible with only G.
[Galaxy S II Android Development] vbracer:
Settings/display/ambient display slider is set OFF, so proximity should not activate on lock screen.

Could others also check by:

1. With device asleep/screen OFF press Home button.

2. When the swipe screen comes up, look closely at Proximity Sensor high frequency flashing RED.

It can be difficult to see, you might need to cup your hand around sensor at the top of the phone.