yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] iSonik:
Sweet. Do you know if you can use OTG and charge at the same time on the i9100? I am building a Sound/Charging dock as a present out of wood and i cant test OTG cause i dont have the phone myself
[Galaxy S II Android Development] MigoMujahid:
No, Sorry, don't know about that :rolleyes:
[Galaxy S II Android Development] Wachicamo:
I'm facing a wakelock with "RingtonePlayer". Like I mentioned before, for some reason my phone stops ringing the sound notifications and it seems like it's connected to this wakelock. Right now, It's not working the sound, but vibration does.
[Galaxy S II Android Development] MARCOSOFT:
Remove the superuser indicator "#"

Hello,

I noticed that many of you don't like the superuser indicator ('#') in the status bar and that some of you even flash SuperSU or Xposed, just to get rid of it.

Well, that's not necessary, because there is a much easier way.

So here is the "right way" to remove the "#":

1. Go to Settings > status bar > icons

2. Uncheck and re-check one of the items (to make sure the required settings entry is created)

3. Backup the file /data/system/users/0/settings_secure.xml

4. Open /data/system/users/0/settings_secure.xml with a text editor (as root)

5. Search for "icon_blacklist"

6. you will find something like this:

<settings id="96" name="icon_blacklist" value="" package="com.android.systemui" />

(ID may vary)

7. Add "su" between the quotation marks after value, so it looks like this:

<settings id="96" name="icon_blacklist" value="su" package="com.android.systemui" />

If value is not empty, just append ",su" (with a seperating comma):

<settings id="96" name="icon_blacklist" value="other,icons,su" package="com.android.systemui" />

8. Double check the XML syntax (a mistake here might cause a bootloop)

9. Save and reboot
[Galaxy S II Android Development] sanyigz:
In CM13 there was a switch in developer options that enabled a cpu usage graph overlay, with the highest cpu user applications.

Where is that from LOS 14.1?
[Galaxy S II Android Development] BenjyTec:
Anyone knows if it is possible to directly toogle on mobile data from the quick settings row if you swipe down once? Currently it expands the data usage panel what seems unnecessary to me. I'm on the 0228 build.

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

Looks like it has been removed. I also can't find it. You could use the 'CPU Monitor' app instead. It also can display the CPU usage in the status bar.
[Galaxy S II Android Development] MARCOSOFT:
And changing the maximum cpu frequency, is it possible?
[Galaxy S II Android Development] Nobby1960:
The maximum frequency doesn't stay stable on performance profile. Fallbacks to 800 MHz still happens, especially if you install something from Google Play or the phone is heavily loaded.
[Galaxy S II Android Development] gm0:
Still broken? I thought I saw in the changelog that that got fixed in this week's build. But I'm usually using the On Demand governor so I'm not sure.

I don't think that was his question though. To answer that one: you cannot manipulate the max CPU frequency in Lineage itself but if you root the phone there are plenty of apps to do it for you regardless of the ROM.
[Galaxy S II Android Development] Nobby1960:
One issue is gone, the CPU frequency don't fall back on 800 MHz in deep sleep. I use a modded Kernel Adiutor to hold the frequency on 1200 MHz with own settings in ondemand governor, that works quite well.
[Galaxy S II Android Development] MARCOSOFT:
Leave here the link to the modded Kernel Adiutor you are using.

What is the best app to change max CPU frequency in Lineage with root?
[Galaxy S II Android Development] marcimix:
I jump week ago to LineageOS 14.1 and what can I see is the Signal massaging app do fc during/receiving a call.

Anyone?
[Galaxy S II Android Development] Nobby1960:
I attach you this little file. The values I use see here. Set both cores to 1200 MHz min/max and that everything is taken by the system start.
[Galaxy S II Android Development] Nobby1960:
Which build is installed? It sounds like the RIL bug. Take the latest build from March 29 here .
[Galaxy S II Android Development] marcimix:
You didn't checked. I have it and previous one too.

It is hard to say told you what missing point is ROM or APP.

In my eye I didn't see anything wrong on lolcat :)
[Galaxy S II Android Development] Nobby1960:
Is there an error message on display?
[Galaxy S II Android Development] marcimix:
force close

Similar like this:

http://www.androidpolice.com/wp-con...nexus2cee_android-n-force-close-regular-1.png

EDIT

it is my mother phone so I can not do everything what i wanted like anytime for example do a screenshot.

She have nothing there like 4 apps.
[Galaxy S II Android Development] Nobby1960:
Hmm - very difficult to say. With an exact error message one could say, which app crashes.
[Galaxy S II Android Development] marcimix:
i9100 have similar problem on 4.4.4 till I send an lolcat recipe for creators. :) So it must be the app Thank you : )

Oh and the snapcamera not working too. Please check it he wanted from me to connect the USB memory at start.

https://play.google.com/store/apps/details?id=com.marginz.snaptrial&hl=eg

WEIRDO :crying:
[Galaxy S II Android Development] MARCOSOFT:
Thank you and congratulations for the development.
[Galaxy S II Android Development] jecatch:
Anyone else having an issue where all apps after a dirty flash do not work and crash.

Heaps of apps pop up saying the blow with 3 buttons

XXX has stopped working.

1-Close app

2-Send feedback

3-Mute until device restarts

Sorry didn't get a screenshot as nothing was working, this was after a dirty flash posted here https://xdaforums.com/showpost.php?p=71014418&postcount=10

Might restore my backup for now as it is getting little frustrating as even the keyboard crashes.
[Galaxy S II Android Development] MARCOSOFT:
BootManager

I'm a little lost!

It seemed to me that I already saw in LineageOS a menu that allowed to manage the applications that started in the boot, to the sameness of BootManager!

Can anyone indicate where this menu, or am I mistaken?

Bootmanager is not 100% operational in LineageOS, because there is no Xposed, right?

Thank you
[Galaxy S II Android Development] toy_story:
Apps Started on boot

To configure apps started on boot, be on the path:

Settings - Memory - Apps Started on boot - Select the application and configure.
[Galaxy S II Android Development] Kurt Krummbein:
Can you make a video of your situation, we could use it as a showcase video for : "If it's looking like this, it's time for a clean flash".

Cheers

Kurt
[Galaxy S II Android Development] gm0:
Did you wipe the cache partitions at least? Because that's what causes issues like those for sure.

That aside, Titanium Backup (or similar) what data you need on CM13, do a clean LOS install and then restore the data. Probably faster than trying an experimental upgrade, anyway, and certainly more reliable.
[Galaxy S II Android Development] fireburner-de:
I just switched tom LOS14.1 yesterday. (build from March 29th)

I set up emulated storage, which seemed to work.

I run TWRP-3.1.0-EMU-MIGRATION-M-20170318 + lineage-14.1-20170329-nightly-i9100-signed + addonsu (modiefied one from XDA) + GApps

I did a xclean install (wiped cache system data sdcard0). I manually removed primaryStorageUuid="primary_physical" from /data/system/storage.xml

I only could not modify ro.vold.primary_physical.

Setprop ro.vold.primary_physical 0 does not change the property (stays at1)

But from what I read this is only important when wiping data (factory reset).

Today, I wanted to encrypt but after the encryption restart, I always get System UI has stopped working during boot.

Does anyone have an idea, where I might have gone wrong?

__________________________________________________________________

Somehow it workls now with emulated encrypted sdcard. I completely wiped everything again and started from scratch. The only difference was, that I did not set up anything this time.. Last time I had added my Google Account and had installed some apps.

I can not imagine what elese could have been different.

Nevertheless, I have the newest Android an a almost 6 year old device, thanks to the wonderful work of all the community and the developers in specific!

Thank you all for this work!
[Galaxy S II Android Development] Nobby1960:
This maybe happen, if something went wrong with the flash. First wipe cache/dalvik in recovery. If that does not succeed, make a backup of important data (SD cards) to the PC and do a clean flash. Searching for errors usually takes much longer than a fresh setup and costs your nerves.
[Galaxy S II Android Development] MARCOSOFT:
Limiting the CPU speed to 1000MHz greatly improves the battery life.

I will share my experience!

I was trying to put the CPU at 1400MHz, but without great success because it had high battery consumption and above all it gets a bit unstable and sometimes slower than the settings with the LineageOS Kernel stock!

So I decided to reverse!

With KA I've limited the maximum speed to 1000MHz with the LineageOS Kernel stock, with no further changes.

My feeling is that I did not feel the phone slower, it is stable and fluid, but the battery has improved its behavior a lot! I think it improved about 50%!

Do this experiment and see if you get the same result?

Sorry for my English!
[Galaxy S II Android Development] Nobby1960:
[MENTION=4296222]MARCOSOFT[/MENTION]

Not a bad idea - I have installed a music streaming app called "Radio Tunes", I use it very often. With balanced governor settings it lags terrible by scrolling through the list, really annoying. On 1200 MHz it runs near lag free. Maybe this app is coded awful, but the music selection is very large. That's my "reference" ;) Or Google Mail (Google Play is outside any specification). You can see that the apps are written for ever stronger CPUs, although they have no more features than before. Pure intention to buy a new phone with an eight core CPU.

Btw: You don't have to apologize for your English, mine is also not better :silly:
[Galaxy S II Android Development] joks1:
Does Lineage OS have option to turn on legacy DHCP client (that uses Lollipop client) in developer options? This option is saving my battery on my home wifi a whole day or more on my CM 13 Marshmallow.
[Galaxy S II Android Development] the.gangster:
[MENTION=5543855]joks1[/MENTION]

No, LineageOS 14.1 doesn't have that particular developer option.
[Galaxy S II Android Development] joks1:
Will it be implemented? Otherwise if Lineage OS drains my battery on wifi like CM13 without legacy DHCP, then i cant use it. My phone can survive maybe 2 days at home with wifi ON, with very very light usage.
[Galaxy S II Android Development] Moixo:
Hello friend, this Rom has the Mobile Data Connection Bug? Can I navigate well with mobile data ?? Beforehand thank you very much and sorry for the bad english

I wonder why in CM 13 Last nightly there was that Bug :(
[Galaxy S II Android Development] Mirajoo7:
proximity sensor is in ON state before answering a call[emoji52] also it is ON in lockscreen (without using any gestures)
[Galaxy S II Android Development] gm0:
The former is working as intended and the latter is a known issue. This isn't the place for bug reports by the way - repeatedly posting about issues won't make them go away...

---------- Post added at 18:31 ---------- Previous post was at 18:28 ----------

Just use a static IP configuration for your home WLAN to avoid the renews.
[Galaxy S II Android Development] Kurt Krummbein:
Guess you should rather configure a longer lease time, should be 8 hours +. Then the DHCP client shouldn't try to renew the lease that often.

Gtz

Kurt
[Galaxy S II Android Development] joks1:
Security profile is 1h (max allowed for my router), i have set static IP for all home devices (although it does show countdown for all devices regardless, and it starts with more than 12h).

battery draining on some wifis isnt just my problem, it is very common problem since Marshmallow.
[Galaxy S II Android Development] gm0:
In case the static IP part was in response to my suggestion, what I meant was to configure the parameters of the WiFi connection on the phone manually, i.e. do not use DHCP at all on the phone for your home network. You know all the parameters anyway since it's your network so you to not need DHCP.
[Galaxy S II Android Development] joks1:
Done. Will see how it goes.
[Galaxy S II Android Development] winone1208:
Thanks, I find solution :victory:

I took off the protective foil on the screen:o.

I shocked and happy, gps fix in ~30sec(tested many times).
[Galaxy S II Android Development] trolliumBorate:
Please help me !!!

I am stuck in a bootloop , I cannot go into recovery , but can go into download mode , however from there I am unable to understand how to flash via heimdall because most of the usual stock techniques aren't working there( like zip vs tar , files etc.).

I've spent two days trying to figure out a solution myself but have had no luck so far, I am kindof experienced with this stuff but am failing this time.

Thanks
[Galaxy S II Android Development] gm0:
Just follow the TWRP installation instructions for Heimdall: https://twrp.me/devices/samsunggalaxys2i9100.html
[Galaxy S II Android Development] laptopu:
That guide only skims over one of the key heimdall steps which is an isorec kernel must be flashed too, I think the guide should make this clearer as it's an easily missed step especially if you're stressed in a bootloop and when I got in that situation it had been several years since I used heimdall. To compound it all most online info talks about windows which often was little help on Linux. Hope these points help.

---------- Post added at 10:01 AM ---------- Previous post was at 09:53 AM ----------

Just checking status of latest build and noticed odd commit YOLO and a related br0zip but nothing as a description. Appears this is an April fool's joke. I'm not flashing the next nightly because of this, I remember one year a joke turned all icons to cat symbols which was mildly annoying but wait 24 hours and there was another nightly to revert. I don't fancy waiting a whole week wondering what unexpected things might happen on a handset I use for a daily driver because it was the first of April half a week ago though.
[Galaxy S II Android Development] the.gangster:
New build 20170405 out now.

Get it

(April's fools edition, but harmless, no annoyances)

- new Gallery with timeline

- fixes for cmupdater

(YOLO only affect boot animation.)

Edit: Read here about the amazing new experimental "Aqua" protocol and other April fools edition specials. :)
[Galaxy S II Android Development] Jamie_oppo:
The br0zip is a rom builder. Its works for every device and takes one zip and makes a bugless rom. One catch its an april fools joke ? so is the mascot.
[Galaxy S II Android Development] daneal2u:
Anyone up for building DU For this device or n7000? Or at least help me get the repos in the right order? [MENTION=414800]arnab[/MENTION] [MENTION=2222292]rINanDO[/MENTION]
[Galaxy S II Android Development] treysis:
Thanks for wasting battery with this unnecessary white background after update :(
[Galaxy S II Android Development] gm0:
The April's fools stuff will be gone again next weekly so just skip this one if you don't want it. Nothing else really important in this build, anyway.
[Galaxy S II Android Development] treysis:
Yeah, I saw now that it's April's fool stuff. Just don't get why it's funny. So yeah, it will be gone soon.

At least no sudden reboots with this version during charging.
[Galaxy S II Android Development] robby2107:
And I wonder about the "ugly" jellyfish animation. :p
[Galaxy S II Android Development] trolliumBorate:
I already did that , and it showed flash successful but I still wasn't able to boot into recovery :( :crying: , also I think i'll flash the system again using heimdall , can you tell me where can I find the full lineage os instead of OTAs ( i.e. with boot.img and all other files ) ?
[Galaxy S II Android Development] gm0:
All LineageOS images all full images, no matter the delivery. There are no delta updates yet (or ever). The boot.img is in the zip, just extract that and flash via Heimdall

And yes, if flashing the recovery didn't help then flashing the kernel (boot.img) is certainly a good idea. You did already change your partition table (pit) to at least 1 GB system partition, didn't you?
[Galaxy S II Android Development] 西村大一:
Holy balls, it's like this phone never dies. I might as well get one. Anyone kind enough to share their experiences with an S2 in 2016-2017? I need a secondary phone because of work reasons and I wanted to get myself a customisable one, not those new locked "sh*tboxes" they offer at my work.
[Galaxy S II Android Development] 0670:
I did for battery save :)
[Galaxy S II Android Development] shkedov:
Geez man, the answer is just on the very page you posted your question! RTFT!
[Galaxy S II Android Development] Pendragon2000:
Look 2 posts ago
[Galaxy S II Android Development] neuweiler:
Thanks a bunch! After the experimental, I was able to install an older unofficial version again (20170129) which worked before. But it didn't help either. The System UI always crashed. So I backed up everything and did a full wipe in TWRP and re-installed the signed version from 20170213 and everything works fine now (without restore). Something must have gotten corrupted before. There was some confusion because the migration path may deliver the same crash. Sorry for bothering you all with that and thanks for all your support!
[Galaxy S II Android Development] gm0:
Have to admit I don't understand the procedure in place here. Why post an official thread if you delete the official build the next day (again), as well as all the previous builds? Why delete the official build if it's just a nightly that comes with a fat warning that it may have issues and you need to do your research first? And if after all you decide to delete it anyway why not at least put a message about it in the thread, ideally the first post? Just all seems a bit of a strange way of going about things, that's all.

That said, thanks for all the work, I migrated from CM13 to the late official 14.1 build without a hitch (TWRP factory reset into Titanium Backup restore), everything is working fine (don't care about the file-manager issue), and whatever problem caused the build to get pulled, I haven't noticed it yet.

Keep up the good work!
[Galaxy S II Android Development] Nobby1960:
Take care with experimental builds, always make a nandroid backup before flashing.

Now first try a full wipe in TWRP (cache/dalvik cache/system/data).
[Galaxy S II Android Development] mwnn85:
I think it's fair to say that In 2017 there's better options available even for a (backup) phone - especially if you can search around for a used excellent/mint condition previous flagship model.

PAYG; never had a contract. People change their phones like their underwear - and the carriers/manufacturers love this cycle.

Lucky to get one platform update from Samsung. Criminal really.

The removable battery is always nice to have on the Galaxy phones but the dual core, 1GB RAM and limited screen resolution is really starting to show it's age. The microSD slot being near the battery is a bit of pain as well. It didn't help that Samsung never released any info on Exynos 4210 - pissing off everyone in the process.

Something at Galaxy S4 level or better? Maybe a OnePlus One at the right price? Sony Xperia?

1080p screen; ARMv8 quad core; 2GB RAM - ideally something with good documentation/open source/third party support.

If our two i9100's died - that's what I'd aim for at least.

Not to say that the i9100 struggles with Nougat AOSP; it's far faster than TouchWiz 4.1.2.

Still use the camera often - still good quality imo - better than what I've seen from most iPhones.

Gmail/Google Drive picture uploading.

I'll pickup our tablet for any kind of serious web browsing.

And a cheap Amlogic S905 box handles all our media - if I'm lucky it just might get mainline support in the Linux kernel.
[Galaxy S II Android Development] davidvanwijk:
Did you do a full wipe?
[Galaxy S II Android Development] Iluvatar2000:
Awesome ROM! My s6 edge has older android version than s2 :(
[Galaxy S II Android Development] Lysergic Acid:
I was talking with the Lineage team when I brought to attention that the current SELinux rules were too permissive, rendering it useless as a security feature, then they took the builds down
[Galaxy S II Android Development] bujjo53:
I flashed succesfully zip file was corrupted ,now im usin latest nightly
[Galaxy S II Android Development] shkedov:
Hold on a second - you mean that hanging around with the recent build of LOS (130217) is insecure? And what kind of insecure? How bad is it:confused:

It is my main and only phone, I hope things won't go :silly: for me.

And thanks for the hard work!
[Galaxy S II Android Development] dii86700:
Thanks for explanation but wil be next build have official:( I hope to fix this and go official make thanks for great and perfect and smythly rom. Thanks again :fingers-crossed:
[Galaxy S II Android Development] shkedov:
Also I'm reporting an bug I recieve:

Each time when I end a phonecall (no matter if it's incoming our outgoing calls) I get a popping message that there is no reception, and the anthena shuts for about half a minute and then returns, also it takes about 2 minutes for the data connection to recover. I'm pretty sure it's not about the provider because I didn't have that thing before moving to LOS.

Anyone confirm?
[Galaxy S II Android Development] the.gangster:
Keep an eye on it yourself: commit (I already expected that one to be the reason for take-down and now LA acknowledged)

and its Revert.

But as it got merged already, it will be part of next autobuild nightly.
[Galaxy S II Android Development] Boolian:
You may have the wrong idea about Roms & nightlies - official or otherwise.

You do know CM13 never made it to an official "Stable" build ? Good though it was.

As for any warning - it's the very first thing written in the OP.

"Live updates" on the continuing status of the ROM development is what the thread is for.

That said, good you got it working despite everything.:good:
[Galaxy S II Android Development] vickdu31:
I have problem with sim card, it require a kind of pin code, if I press dismiss, the sim card wont be detected. If I enter correct pin (which I disabled verification) then it just stay stuck at that step.. Any idea ?
[Galaxy S II Android Development] cescof:
can i do a suggestion?

You can try the lag fix implemented by the user MSM in his MSM-CM 10.1 build

He simply fixed the hardware composer of the cyanogenmod 10.1 and made a rom that i think was the smoothest ever created for the samsung galaxy S2 i9100.

you can use the same way to make this phone very very smooth, smooth like modern devices, with nougat 7.1.1
[Galaxy S II Android Development] gm0:
As far as I recall CM13 had a snapshot release early 2016 before they moved to nightlies only, but yeah I know what the labels stand for. Anyway, no reason to really get into this or I'll start sounding like I'm bickering, which I don't really mean to, because the answer to that would be that I could get involved myself which I just don't have the time for these days. So I'll just repeat my original thanks for the work that's being done. ;)
[Galaxy S II Android Development] laptopu:
You must flash kernel as well as recovery, it's well documented our device cannot boot to custom recovery on stock kernel, that's the main point of my earlier post the twrp guide doesn't make this totally obvious.
[Galaxy S II Android Development] ran000:
Snapshot

Sorry if I miss something.

Please, how I can do shapshot of screen?
[Galaxy S II Android Development] MigoMujahid:
you mean Screenshot?

hold power button and volume down together to make Screenshot.
[Galaxy S II Android Development] gm0:
In addition to the answer already given you can also enable a full and partial screenshot option in the power menu (settings>buttons>power menu).