yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] the.gangster:
In short:

Last commit (for going back to common_full_phone) was: galaxys2-common: Increase System Partition Image from 512MB to 640MB

Even if you don't want to flash GApps, don't go below that size to ensure the ROM's system-image fits.

If that is too much work for you (as it is for me, too), why don't you simply place the matching settings-widget on the home-screen?

Then it's only pressing Home, tapping the "Tethering & ..."-icon and you are where you want to go.

And now it's waiting for its first nightly again. :laugh:
[Galaxy S II Android Development] neuweiler:
Help! I need a working build! I only downloaded lineage-14.1-20170213-nightly-i9100-signed.zip form lineageos.org and installed it. I just read about the procedure to install a second image after that one but now everything is gone from the site and I'm stuck with a not working phone (black screen, crashing UI). How can I get the necessary files now? I can't even go back to the previous image 20170129-UNOFFICIAL-i9100 - TWRP complains "can't install this package on top of incompatible data". But I don't want to do a factory reset.
[Galaxy S II Android Development] ale5000:
I have flashed first 20170208-experimental and then 20170213-nightly.

Now everything works perfectly (except the know issue about the file manager).
[Galaxy S II Android Development] neuweiler:
Happy for you but that doesn't get me a working phone..
[Galaxy S II Android Development] ale5000:
Have you tried to flash the experimental again, reboot in the system, then reboot in the recovery and flash the nightly?
[Galaxy S II Android Development] Spyr0s:
Works fine on 1.2Ghz for me
[Galaxy S II Android Development] davidvanwijk:
You could try this build: https://androidfilehost.com/?fid=457095661767137452

Works for me.

Verstuurd vanaf mijn GT-P7500 met Tapatalk
[Galaxy S II Android Development] rubentkato77:
Is this your own baked build? Does it support emulated storage?

Do we need to flash su addon to gain root access?

Regards :good:
[Galaxy S II Android Development] davidvanwijk:
Yes, own baked and no: no support for emulated storage. However: I suppose this thread is not the place for unofficial builds.

Verstuurd vanaf mijn GT-P7500 met Tapatalk
[Galaxy S II Android Development] neuweiler:
Thanks.. but unfortunately also doesn't work: still "incompatible data" error
[Galaxy S II Android Development] suapoc:
i have some charging issues right now.

my phone takes about 5 hours to charge from about 6% charge to 100% it's so slow that i actually can't use it while charging because the battery is drained faster than it is charged....

i had no issues before flashing LOS 7.1. but it could just be an odd coincidence.

Does anybody have the same issue?

also just out of couriosity how long does your S2 take to recharge completly?
[Galaxy S II Android Development] Jamie_oppo:
Does ur device get extremely hot while charging. Maybe its limiting power because its soo hot?
[Galaxy S II Android Development] gm0:
Did you try different chargers? I had one that did that because of a bad connector, it wouldn't reliably deliver current unless you basically held it down in a specific angle to ensure a good connection.

But nope, no issues with LOS and charging.
[Galaxy S II Android Development] suapoc:
no... it's just getting a little bit warm but not as warm as it used to get while charging.

yes, i tested two 5V / 2A chargers... i'll test the original charger when i find him.... however i had no issues with the other two before.

good to know so it's either the cable, the battery or the usb connector of the phone....
[Galaxy S II Android Development] s2l9100:
Hello guys,

I'm running rooted - LOS 14.1 - 02.28.2017.

I have problem with guitar tuners like PitchLab - the apps show massage that "no audio detected" or better "can't access microphone".

Thanks for your attention!

Edit: Google voice search was using the microphone all the time and the apps couldn't access it.
[Galaxy S II Android Development] Nobby1960:
The bug in the built-in CPU governor and how to reproduce it - I've tested it on two S2 devices:

Install an app to watch the CPU clockspeed like CPU-Z. Select the "Performance" profile in the settings/battery/battery saver and performance (slider to the right, 1200 MHz constantly). We start now Google Play Store, scroll down and up several times - yeah, first it lags like hell :D Now check the CPU clock, it's fallen back to 800 MHz. It must stay on 1200 MHz if you need power. An app like Kernel Adiutor uses the internal profile if you switch in CPU governor to "Performance", so the app makes no sense.

This issue is in all LineageOS-based ROMs (AICP, crDroid, RR). A workaround is to patch the ROM with the custom kernel from [MENTION=5798657]Skyline[/MENTION] with the special modded Kernel Adiutor. There you can take an other governor. A better solution is a fix in the ROM.
[Galaxy S II Android Development] laptopu:
Thanks for your update, I couldn't get zoiper VoIP app to send audio and I spent a long time checking port and server settings when it was the problem you described. I turned off Google on any screen and my app is working fine.
[Galaxy S II Android Development] sanyigz:
Why the camera app gps location isn't works? (or barely works). In CM13.1 it always added location to photos, but the current one only adds location if i started a GPS using app just before. The camera app itself isn't tries to get gps location at all. I'm using 20170228-nightly
[Galaxy S II Android Development] todonormal:
In my Xperia SP and Xperia L with LineageOS, I found SmartLock, but i don't found in Galaxy S2...
[Galaxy S II Android Development] gm0:
Mine has it. Maybe you forgot to install GApps? It's a Google feature, nothing to do with LineageOS.
[Galaxy S II Android Development] todonormal:
Ok. Thanks:

Go to Settings—Security.

Under Advanced, tap Trusted agents as shown below.

Tap Smart Lock (Google) to Enable\Disable it. You can also drag the switch to the Right\Left side to Enable\Disable it.
[Galaxy S II Android Development] thepredictor:
Cant play videos on wwe network and hbo now, it gives me lines on the screen like small boxes, i get audio but the video is cut into small boxes, dont know what this is, had this issue on cm 13 and now upgraded to lineage os 14.1 but still same problem. My device is samsung galaxy s2. Im only facing this on these two apps otherwise netflix,youtube etc are working great
[Galaxy S II Android Development] rINanDO:
I noticed this behavior some time ago in cm 13.0. In my experiments I disabled the code. https://github.com/rINanDO/android_...mmit/a15f3e0db347c60f223bc6ec26e410ddbd725279

Seems it is implemented to reduce battery consumption...
[Galaxy S II Android Development] Nobby1960:
[MENTION=2222292]rINanDO[/MENTION]

Many thanks for reply and your hard work. Would it be possible to remove this step up limit again in next build, so that you have a real performance profile? The built-in profile "Balanced" is very well suited for energy saving. That would be really great.
[Galaxy S II Android Development] gm0:
I can't actually reproduce your problem. I followed your steps exactly and CPU speed stays glued to 1200 MHz no matter what. I'm running the official LineageOS build. So the issue must be something else. Happy to help track it down if you want me to try something.

edit: I did however notice that letting the device go idle will drop the speed to 800 where it will stay until you toggle the performance profile again.

edit2: Seems the 800 is the hardcoded frequency target from [MENTION=2222292]rINanDO[/MENTION]'s linked commit above (who wrote that code, anyway - hardcoding is bad), see https://github.com/LineageOS/androi...b/cm-14.1/arch/arm/mach-exynos/cpufreq-4210.c. I'm not sure why that code exists (the governor alone should take care of frequency limits for power saving) and I also vote for killing it.
[Galaxy S II Android Development] Nobby1960:
If I use an app like Google Earth, which needs a lot of power and I work with it, the frequency falls to 800 MHz here too in performance profile. You also notice this clearly that the app begins to lag.
[Galaxy S II Android Development] gm0:
Can't repro. Do you have automatic optimization on or off?
[Galaxy S II Android Development] Nobby1960:
Automatic optimazion is off, strange thing. I reflash the ROM and check it again. To exclude hardware errors, I test ROMs here with three devices (and five batteries :silly:).
[Galaxy S II Android Development] gm0:
Maybe I got a hero S2. ;) No idea what the difference is then, I'm sure it's some setting somewhere. To reiterate, what I did was switch to performance governor/profile, put load on the CPU for a while, switch back to CPU-Z immediately to confirm that the frequency is still at 1200 MHz. Only way I found to get it down is to turn the screen off manually or by idle timeout.
[Galaxy S II Android Development] thepredictor:
Help

Cant play videos on wwe network and hbo now, it gives me lines on the screen like small boxes after few secs, you can see images and watch video below, i get audio but the video is cut into small boxes, dont know what this is, had this issue on cm 13 and now upgraded to lineage os 14.1 but still same problem. My device is samsung galaxy s2. Im only facing this on these two apps otherwise netflix,youtube etc are working great.

Any help would be appreciated.

Screenshots:

http://pasteboard.co/FO8QVEGC2.png

http://pasteboard.co/FOGvfhKsk.png

Ive uploaded a video of this problem.

https://vid.me/wPeA
[Galaxy S II Android Development] Nobby1960:
Indeed, you must have a high powered S2 version :laugh: New clean flash of the latest build and I can't count the frequency fallbacks alone during installation. Crazy :eek:
[Galaxy S II Android Development] boscorama:
I was trying out the latest nightly (experimental + 02/28) and it really makes the phone zing.

However, it would suddenly lose the timezone info from the cell network and revert to GMT. Nothing would bring it back except a reboot.

I looked thru the thread and didn't see any other instances mentioned that would indicate this is a known issue. Is anyone else experiencing this?
[Galaxy S II Android Development] xda helios:
Hi!

Well, I've noticed a have a very bad reception of signal. But, when I say bad, it's really bad! Places where I had 3 or 4 bars in signal, now I get none!
[Galaxy S II Android Development] MigoMujahid:
Install latest "Android System WebView" app from playstore by google, then go to "Developer Options" in settings, and press on "WebView implementation" and choose "Google WebView".
[Galaxy S II Android Development] Nobby1960:
Exactly, after a deepsleep the CPU remains at 800 MHz - without a new manual switching there ist no step up to 1200 MHz. No good solution.
[Galaxy S II Android Development] kraehetest:
Hello,

i downgrade my Modem from I9100XXMS4 to I9100XXMS2, and install the sirfgps.conf.

I think GPS is running better. GPS fix before from 2 - 3 minutes, now about 30 seconds or less.

I think the main reason is the modem, i think i have already used the modified sirfgps.conf.

Thank you.
[Galaxy S II Android Development] Nobby1960:
A nice workaround to hold tight the CPU on 1200 MHz, whatever happens. You need this modded Kernel Adiutor . Switch the CPU governor on ondemand, lock the frequency from both cores to 1200 MHz minimum/maximum. You must change some values in the ondemand governor profile, see screenshots. You see also that core 1 stops, if not needed to save battery. Have fun!
[Galaxy S II Android Development] Oxydeme:
Almost sure there will be a newer build tonight or at least tomorrow as others, waiting for it

Quote: "in all LineageOS 14.1 builds from 6th March 2017"

http://lineageos.org/Last-Week-in-LineageOS-4/

And "OneHand" mod, see the review here:

https://review.lineageos.org/#/q/status:merged+branch:cm-14.1+topic:oneHand
[Galaxy S II Android Development] gm0:
No need for guesswork. Automated weekly builds are currently getting created for our device on Tuesdays: https://github.com/LineageOS/hudson/blob/master/lineage-build-targets
[Galaxy S II Android Development] jt12345:
With pleasure - I'm glad that it has helped you.

J :)
[Galaxy S II Android Development] robby2107:
Yesturday I switched on LineageOs 14.1, too.

Thanks to all involved People/Devs for this great new ROM.

The i9100 will never die!! ;)
[Galaxy S II Android Development] Nobby1960:
The "screen medium bug":

Sometimes it happens after a missed call - the screen stucks on "medium", dimmed but not switched off (on homescreen). If you don't recognize that (who is staring at his phone the whole day/night except we crazy testers :p ), the battery runs empty in shortest time. This issue has been in the ROM for some time. You can reproduce it, if you call yourself several times. Between the calls there must be a longer time.

If it happens I must reboot, to get the automatical deepsleep mode again.

Edit: This issue happens not only by phone calls. If you awake the device manually or any app automatically it's also there, randomly. It looks as if the lockscreen wants to come and can not.
[Galaxy S II Android Development] Oxydeme:
Got a issue too, when battery is getting low, sometimes the phone go itself in low battery mode, and then the navbar and the other zone switch from low battery to normal battery every second, ending with something ugly. Is it normal?

Tried to record that weird thing,... Impossible :/
[Galaxy S II Android Development] gm0:
New build is up.
[Galaxy S II Android Development] treysis:
OTA went fine.
[Galaxy S II Android Development] dumdidum123:
OTA always fails with damaged or unsafe download. Tried around 10 times.

manual update via twrp went fine, first try
[Galaxy S II Android Development] sarkasm14:
Bootloop

Was working seamlessly for a week on 28/02 nightly build. But got bootlooped on 07/03 OTA. So I decided to dirty flash the 28/02 nightly. Still bootlooped. I don't want to clean flash as i dont want to lose whatsapp messages. What should i do? Help please :crying:
[Galaxy S II Android Development] SimonBell:
Tried to flash it via TWRP from 26.02 - stuck on flashing

Tried via OTA - flashed, but got bootloop

Don't know what to think
[Galaxy S II Android Development] laptopu:
I had bootloop last night on 28/2, worked fine for a week then turned it on and could hear camera autofocus kept clicking away and it wouldn't boot. Only solution was to wipe data. Wiping cache and reinstalling system doesn't work has to be data wipe which was a real pain. Looks like I'm not the only one. What's going on any ideas?
[Galaxy S II Android Development] gm0:
Not knowing anything about your configuration all we could do is make wild guesses but simply checking the logs seems the easier solution. ;)

(edit: assuming you have any, of course, depends at what point it restarts - personally I haven't had a bootloop in years).
[Galaxy S II Android Development] Nobby1960:
First I got error 7 in TWRP, after a full wipe there was all right for a successful flash.
[Galaxy S II Android Development] rogers11:
Most probably the same happens for me:

Updated to 07/03 together with updated nano-GApps -> never ending boot-animation

Restored backup

Updated just the nano-GApps -> booting fine

Updated to 07/03 -> never ending boot-animation

Something seems to be wrong. Maybe one of the next Weeklies does the job.
[Galaxy S II Android Development] Wachicamo:
Installed 03/07 directly from OTA, no issues at all.
[Galaxy S II Android Development] ale5000:
Any anyone tried to wipe system partition, cache and ART cache before flashing?

I usually do it and it works perfectly.
[Galaxy S II Android Development] rnd83:
OTA went fine for me. No boot loop. I don't have gapps installed though.
[Galaxy S II Android Development] jojobg:
OTA went fine without issues, no boot loops. But before OTA gets downloaded the 02/28 was crazy powering off and boot looping, started early in the morning in EET. I would say that there are specifics in the setup of the guys/girls that had OTA boot loop or issues with 28-th build. Mine is F2FS and Semi-Adoptable sd card :)
[Galaxy S II Android Development] ale5000:
Can someone please verify if our device is affected by some of these vulnerabilities?
[Galaxy S II Android Development] gm0:
did you see the "Affected Devices" column in the page you linked?
[Galaxy S II Android Development] steiner.seevetal:
OTA update work fine for me too. Coming from 28.02 also with OTA update. Boot seems a bit longer than the first OTA update.

Gesendet von meinem SM-G920F mit Tapatalk
[Galaxy S II Android Development] ale5000:
For some I know they don't apply but some others target libraries or specific hardware components that I don't know if they apply to us.
[Galaxy S II Android Development] gm0:
Correct me if I'm wrong but I don't think we can answer that for the components where they don't list the devices yet since all you get for those is "Redacted content". Suppose we'll just have to wait for the final version of that page.
[Galaxy S II Android Development] dumdidum123:
If you have still problems and WhatsApp is you only problem and you have TWRP. Boot into TWRP Recovery, do a full backup, copy it to your computer. There are tools to extract single apps + data from a nandroid backup. Not sure if it works, but might be your only solution.

And for the future:

Do a nandroid backup always before updating. Just in case...
[Galaxy S II Android Development] wihushae:
I did a clean install on 03/07 and everything worked fine.

But there is one strage thing: the OTA downlader suggests me to download the 03/07 version which is already installed!

Has anyone else this issue?
[Galaxy S II Android Development] Nobby1960:
You can make a clean flash (wipe cache/ARTcache/system/data), but do NOT wipe the internal SD card, there is the WhatsApp folder. Backup your complete internal card on PC via TWRP (InternalStorage). You must reinstall WhatsApp after the ROM setup, all data should be there after verifying. If you have made automatical backups via Google Drive, the last should be restored.
[Galaxy S II Android Development] gm0:
Known issue, needs to be fixed server-side. IIRC the workaround is to simply delete (or move) the update .zip file.
[Galaxy S II Android Development] BenjyTec:
You can find the inbuilt WhatsApp backup function at Settings - Chats - Chat Backup.
[Galaxy S II Android Development] toy_story:
OTA dowloader

Check the path: data/ data/ org.lineageos.updater/ app_updates/ lineage-14.1-20170307-nightly-i9100-signed.zip

You must have a firmware file in the folder "app_updates" - lineage-14.1-20170307-nightly-i9100-signed.zip

If it is not there, then the OTA dowloader will constantly suggest that I download the 03/07 version.

Or, in the configuration of the OTA dowloader, select the update - weekly.
[Galaxy S II Android Development] winone1208:
I have low strange signal(13-30%) and max 3 satelites satellite on stock rom(last XEO from sammobile) and new LineageOS. I have I9100XXMS2 baseband. I use your sirfgps.conf. Change baseband may help?
[Galaxy S II Android Development] rogers11:
The problem was TWRP 3.0.3 (at least it seems so). I could not boot any LOS version that was flashed with 3.0.3. Went back to 3.0.2 it it succeeded with the first try.
[Galaxy S II Android Development] laptopu:
I was able to use it with no problems, I'm on [MENTION=2222292]rINanDO[/MENTION] version 3.03 second version with marshmallow support if that makes a difference.
[Galaxy S II Android Development] ale5000:
The changes here and here fix "'UID' field is not set".

Do we need to apply the second change also to lineageos_i9100_defconfig?
[Galaxy S II Android Development] rogers11:
Where did you get it?
[Galaxy S II Android Development] laptopu:
https://xdaforums.com/showpost.php?p=71181662&postcount=145 :)
[Galaxy S II Android Development] rogers11:
OK thanks, but that's for emulated storage (only?).
[Galaxy S II Android Development] gm0:
If you're not using emulated storage there's no reason not to use the official TWRP build. Unless you're enjoying them boot loops of course. ;)
[Galaxy S II Android Development] Nomeji:
Does anybody else have issues with dual band wifi network?

My home wifi network is using 2 channel with 40 Hz separation and I'm experimenting really strange bug.

Sometime when I connect my phone gets really laggy when connecting and then goes back to normal after a while and sometimes it just freeze and I have to hard reboot. I'm only experimenting this issue on my home network. No problem at university or any other network.

I would like to do a logcat but I never know when this will happen. Most of the time I'm not experimenting any issue at all. It's very strange. Just made a full wipe today to be sure and the issue is still there.
[Galaxy S II Android Development] ori.on:
I guess I "bricked" my I9100

Current situation:

I can boot into recovery, and get to see the Lineage-Recovery (14.1). Any attempts to install different recovery modules, or any other zip result in:

failed to seek cache/recovery/command bad file descriptor

Since I wiped the cache and used all sort of other "reset to default" functions, I can't boot the Lineages OS anymore either - it's stuck in the "Samsung Galaxy S2..." boot screen.

What I did:

I was on CM 12, and decided to upgrade to LOS 14.1.

1) I followed the Repartition instructions here: https://xdaforums.com/galaxy-s2/orig-development/repartition-memory-s2-t3018749

2) I used Method 1, but forgot to do step 10 (reset dalvik, system etc), and went right installing LOS 14.1.

3) That got stuck, because apparently I had also forgotten to increase the system partition to 1GB...

4) So I found the proper PIT file, used Odin to partition. That succeeded

5) Back to recovery I decided to do the steps to changed the file system to EXT4 and then ExFAT manually again. After doing that the option to wipe "emmc" became available (which it wasn't before). So I wiped everything as described in step 10 of Method 1.

5) Installed LOS 14.1 and GAPPS in one go. That worked without troubles.

6) Booted into LOS, worked fine, but during the initial setup procedure I noticed graphical glitches of icons and such. I had a feeling that was caused due to me not following the instruction a 100% and doing things in the wrong order.

7) One day later I decided to go back to CM13 (or CM12). So I booted into recovery. Since only LOS recovery was available with limited options, my goal was to get TWRP 3, which had all those specific options. However, any attempt to install a zip, failed. I tried ODIN as well. It failed too... Which is a bit worrying.

My suspicion is that due to the whole repartitioning and formatting/changing the file system to EXT4 and then to ExFAT (which sounds weird to me), is the source of the troubles. I probably got "weird partitions" now, and any attempt to either download (via download mode) or "update zip" fails - with the error listed above.

Any ideas? Any way to restore/recreate the original partition layout, so that I can go back to CM12 or CM13? Thanks a lot for your help!!
[Galaxy S II Android Development] Nobby1960:
The download mode works correct? That's important! Try to flash the Odin-based TWRP recovery. If all else fails take the wood hammer ;):

- Flash a Samsung stock ROM and a pit file (1,5GB_6GB) via Odin

- Flash the Odin-based TWRP recovery

- Full wipe (cache/dalvik cache/system/data

- Flash LineageOS and GApps