yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] rogers11:
See also here: https://review.lineageos.org/#/q/topic:cm14-themes+(status:open+OR+status:merged)
[Galaxy S II Android Development] waldi801:
Once again, i have big trouble with my S2. Update with the Unofficial Version from here works great, but if i try to install the Nightly i always get a "Zip verification failure". I verified the Hash an its the same, i try to update from Internal or External SD but always the same.

My TWRP was the 3.0.3, back to official 3.0.2.1 and the error ist still the same. What can i do to update to the official nightly? Can someone give me some hints?

Thx for helping.
[Galaxy S II Android Development] gm0:
disable signature verification in TWRP (should be off by default, anyway)
[Galaxy S II Android Development] waldi801:
Ok, disabled. And now the Update fails with this message: Updater process ended with ERROR 7
[Galaxy S II Android Development] Saftpresse99:
Perhaps the same issue?! https://jira.lineageos.org/browse/BUGBASH-115
[Galaxy S II Android Development] waldi801:
But the question is, why it fails on my device until other devices have no problem?

I will try the AICP as long Lineage official wont work.
[Galaxy S II Android Development] rnd83:
I had an error too (not sure what number). The message also suggested a factory reset. So I wiped the data partition. Then it worked.
[Galaxy S II Android Development] MigoMujahid:
Use build 11/2 or older in AICP because newer have problems.
[Galaxy S II Android Development] Saftpresse99:
You should create a logcat and hopefully a revovery expert can help you.
[Galaxy S II Android Development] toy_story:
Script fix LockClock for LineageOS

Script fix LockClock for LineageOS

Weather widget clock with two assembly suppliers (OpenWeather and Yahoo weather).

Set in TWRP: LockClock_LOS-mod.zip!

P.S.If you have installed my script "LockClock_LOS-mod.zip!" .

after upgrade LOS, even after the OTA,

it is necessary to again set in TWRP: LockClock_LOS-mod.zip!

Disliked Returned back !

Set in TWRP: LockClock_LOS-REVERT.zip

_______________________

Help must be mutual ...

[i9100] Useful fixes for LineageOS 14.1 [7.1.2]

_______________________
[Galaxy S II Android Development] treysis:
How can that be? I even wiped my S2 now, including internal storage. Reinstalled current nightly + su-binary. If I start the radio app, I have to make some settings first (like which band, tuner, etc.). But then I only get sound for a few seconds, and only from the headphones, not the speaker. After 2 seconds it says: audio stopping. If I press the switch speaker/headphone button, again I'll have sound for 2 seconds.
[Galaxy S II Android Development] waldi801:
Thx, your hint was the goal. I wiped system, data and cache and now the install succeed without an eror.
[Galaxy S II Android Development] alexisj:
Installed latest build (14.1-20170222-nightly) on my i9100 + OpenGapps Pico

Note that i have error when i try to install addonsu-arm-signed.zip (error 4) from recovery.

I tried to flash addonsu-arm64-signed.zip, successfully on recovery (no error code), but su seems still missing when apps requiere it.

Except that, all works fine.
[Galaxy S II Android Development] Nobby1960:
Issues with build 02/22 here until now:

- file manager don't work (old problem, yes I know ;))

- Energy profile often jumps back from 1200 MHz to 800 MHz - the slider is set on performance (issue on all Lineage-based ROMs). If you want back to 1200 MHz tip the slider down and up. No good solution on the long run.

- No icon in status bar if phone connected to PC (or have I overlooked something in the settings?)

- Original file for root access from LineageOS don't work (or is there a newer version?)

Edit: tested without emulated storage, clean flash.
[Galaxy S II Android Development] laptopu:
You must be on version 3.2 not version 3, v3 caused me same problem as you just described.
[Galaxy S II Android Development] Pier_89:
Thank you so much!! But after a nighlty update, is it still remaining?
[Galaxy S II Android Development] waldi801:
You have installed he wrong version, that one is for ARM Systems with 64 bit and the S2 only have 32bit. I have now installed addonsu-mod-arm-signed-1.zip and now i have in the Developer-Options Root for Apps.
[Galaxy S II Android Development] treysis:
I am (if you mean this Radio_v3-2.apk). In fact, it's not 3.2, it's both v3, just different filename. I did binary compare. The files are identical.
[Galaxy S II Android Development] gm0:
The addonsu-arm-signed.zip works fine, the error message is normal, just ignore it. Remember you need to enable root in the developer options, too.

I would not expect the 64bit su-addon to work correctly on the i9100 though, no reason to use that one.
[Galaxy S II Android Development] the.gangster:
[MENTION=6952459]Pier_89[/MENTION]

LockClock is part of the system image. So with every ROM update, you will have a new chance to test and report...

You could report to Lineageos bugtracker (or to regression tracker if it would have ever worked on an official) to have it fixed. Links were provided already here and there.
[Galaxy S II Android Development] Nobby1960:
Here is the standard radio app V3 (I mean it's from XDA?) - it works fine.
[Galaxy S II Android Development] treysis:
[MENTION=7513127]Nobby1960[/MENTION] Yes, I'm using that one. I only get 2 seconds of radio playback, then it stops. RDS info is incoming fine the whole time. Must have to do with audio. Did it work out of the box for you?
[Galaxy S II Android Development] laptopu:
The only file that worked for radio for me is the Dropbox hosted link around page 30 or 31 of this thread. I installed v3 and it didn't work. I removed it and installed the Dropbox file, it worked.
[Galaxy S II Android Development] Nobby1960:
Yes - it works very fine here. Try in settings Audio/Mode/Analog and Audio/Output/Headset.
[Galaxy S II Android Development] rnd83:
You can enable USB debugging notification in the developer settings.

Root access should work if you disable zip signature verification in TWRP. You still get an error, but you can select apps+adb in the developer settings.
[Galaxy S II Android Development] Boolian:
Are you quite sure?

I just tested the addonsu-arm-signed.zip and it's working fine.

How did you install the latest nightly? Was it a "Clean install - full wipe" ?

I flashed over prior nightly.

I've just removed SU (working) Flashed SU again (working) So just want to be clear before I take time to do a full wipe to test this...
[Galaxy S II Android Development] Nobby1960:
[MENTION=6724217]Boolian[/MENTION]

Yes, I did a clean flash (full wipe). I was not sure if the zip file on my PC is okay. Then I took the revised version of [MENTION=8052153]toy_story[/MENTION] - so the flash worked without error.
[Galaxy S II Android Development] gm0:
No need, I can confirm it's still working fine with a clean install. Since the su addon hasn't been updated in a while it still produces the error message (signal 4 or something) but it works regardless.
[Galaxy S II Android Development] treysis:
It doesn't work for me :(
[Galaxy S II Android Development] laptopu:
Did you go back and get that Dropbox linked file I suggested? The problems you describe are exactly the same as I experienced and the Dropbox file worked.
[Galaxy S II Android Development] Nobby1960:
Very strange - we have identical ROMs and phones... you did a clean flash?
[Galaxy S II Android Development] treysis:
Google drive, but yes. And the dropbox link is the same file, just different filename. I'm 100% sure.

Yes, just 2 hours ago or so. Wiped everything: cache/dalvik, system, data, internal. Then installed the latest nightly, gapps pico, su, and bln_mod (should this be the cause?!).
[Galaxy S II Android Development] alexisj:
Indeed, i retried to flash addonsu-arm-signed.zip and enable root, it's works. :)
[Galaxy S II Android Development] Boolian:
This started ringing bells, so took time to check.

That revised version "allegedly" of [MENTION=8052153]toy_story[/MENTION], is originally a workaround for only the error message - from an original post by [MENTION=1540913]MiroBiala[/MENTION] (as well he knows) See Here

You must also very well know, surely, because both of you always post the same "errors" and "solutions" immediately after I (and others) cover this, which, on checking back is often.

I'll pass on testing. It works perfectly well as it is.
[Galaxy S II Android Development] toy_story:
You can see in the post from [MENTION=1540913]MiroBiala[/MENTION] See Here adonsu rebuild to download?

I do not see!

I collected it and laid out, for everyone who needs and does not like to see an error during installation.

So what's the reason?
[Galaxy S II Android Development] gm0:
What's he saying is that the other guy posted the fix before you did so credits should go to him, in particular considering you copy & pasted his post title so clearly you knew about it.

But since the "fix" isn't needed for anything I'd say who cares...
[Galaxy S II Android Development] the.gangster:
Coming all the way from unofficials over 20170208-experimental to (and now from) 20170208-Nightly (without root) I updated now to 20170222-Nightly:

+ developer settings (useless) update recovery option now no longer present (thx [MENTION=2222292]rINanDO[/MENTION])

- settings (still) shows two "gestures" menues (while in other languages they have different names) but that's nothing device specific I assume.

- accounts other than google not displayed (most likely taken care of already with that revert)

+ addonsu-arm-signed -> working (yes the signal -4- "information" is thrown within TWRP, nevertheless all old root-settings last set in unofficials where still in place)

now after having root again:

+ FM radio: both apps work like they did before: SpiritF + Radio-V3

+ File Manager works without problems (on /storage- as well as /mnt/media_rw-subfolders and / and /system ...)
[Galaxy S II Android Development] gm0:
Yes that's the workround but not exactly what I'd call "without problems". You cannot access sdcard0 directly with it (for me it only works via /mnt bookmark though, from /storage to sdcard0 doesn't work, either).

Other file managers work fine.
[Galaxy S II Android Development] Boolian:
Page 2 in a 5 page thread

Here

Just nice to credit is all.

Also, as I mentioned [MENTION=7513127]Nobby1960[/MENTION] has reported the same error a few times, and I wasted time checking. So I was a little annoyed it keeps cropping up.

Never mind, it's nothing for us to have bad feelings about.

I have memory lapses too, I'm sure that's all with Nobby, and I know you're keen to help, so maybe I was being unfair.
[Galaxy S II Android Development] ale5000:
Why the official su addon hasn't been already fixed?

It should be too hard.
[Galaxy S II Android Development] the.gangster:
I don't quite agree.

My file manager behaves just as my Total Commander does.

That was different before. Before I was only able to access these folders by using the bookmarks, now I can browse to these folders, too.

I can't report for the "sdcard0" access for all configurations, but after having migrated to emulated storage it was that way right from the beginning: the non-emulated internal SD (sdcard0) was automatically hidden in most apps and only accessible by using the /mnt/media_rw path. No longer mounted/linked the /storage path. And again, that doesn't differ between file managers as you can proof them not being mounted in these paths also in a terminal session.

So I'd still claim: File Manager now works without problems (on my device with emulated storage enabled and kind of knowing what to expect).
[Galaxy S II Android Development] gm0:
Fair enough, that was important context. On my device without emulated storage it doesn't work properly at all whereas Total Commander works flawlessly. So overall the default file manager still has severe issues that need fixing.
[Galaxy S II Android Development] treysis:
[MENTION=4419266]laptopu[/MENTION] [MENTION=7513127]Nobby1960[/MENTION]

Well, looks like I got it working. I found a "SpiritF beta" from March 2015. Installed this and that one worked, but unfortunately, no RDS. So I went and opened the other radio app again. And now that one works as well.

(I tried too see what logcat is saying, but couldn't find anything. It would just start and stop like when touching the screen for key tones. So I turned of key tones, but that didn't solve it either. Now it's working though. No idea why :| )

UPDATE: Aaaah, well, not so fast. It stopped again after taking off my headphones. The speaker doesn't work, right?

UPDATE2: Lol, if I connect my bluetooth headphones as well, it works again. But sound will only come from the wired headphones, not the bluetooth headset :/

But even if there's no sound coming, I can record the audio and listen to it later (it will also include sound from the microphone, like me writing on my keyboard)

UPDATE3: And now for some reason it crashed (the phone). And after it had booted again (normal speed), all apps were gone! No safe mode. Just disappeared. Don't even appear as installed in PlayStore.
[Galaxy S II Android Development] Mirajoo7:
is there any radio app works in LOS just like the Spirit? or cyanogen os radio app
[Galaxy S II Android Development] toy_story:
The following night LOS, the choice of return accounts!

Here is a fix in the next night LOS:

* - " Revert" Settings: Change the way of email account displayed "

We should not use a whitelist here, we want to show the accounts

of every app. "
[Galaxy S II Android Development] laptopu:
[MENTION=5926322]treysis[/MENTION] did you actually try installing v3.2 though, regardless if you believe it's the same or not? As I said earlier v3 did exactly what you said with audio, v3.2 works perfectly with RDS, saving station presets, record too. Frustrating for us knowing there's a potential solution you haven't tried instead you keep reporting problems.
[Galaxy S II Android Development] treysis:
[MENTION=4419266]laptopu[/MENTION] Sorry if it wasnt clear. But yes, I also tried the alleged 3.2. Problem remains the same.

And I don't believe it's the same, I KNOW it. I did a binary file compare.
[Galaxy S II Android Development] laptopu:
Okay fair enough. You can try a fresh wipe, system install and see if that works first. If not you'll need to start producing logcats as it's not a problem others are widely reporting which possibly makes it hardware specific to you. Logcats will help with this. Good luck.
[Galaxy S II Android Development] tomzar:
Mms not working?!?
[Galaxy S II Android Development] treysis:
[MENTION=4419266]laptopu[/MENTION] Well, that what I just did yesterday evening, and without success (fresh install of nightly with wiping everything!). Also tried having a look at logcat, but it doesn't show anything, unless there's some debug mode to activate :( Only thing it shows is "Audio start", next line "Audio stop".
[Galaxy S II Android Development] laptopu:
Try a fresh clean install though in case your installation is somehow corrupted.
[Galaxy S II Android Development] Boolian:
Yeah, that's the gist of things, if you're on emulated the errors aren't thrown. But it appears it's not so much just a modular file manager tweak, as how it's actually integrated with the OS and how non-emulated sdcard is handled.
[MENTION=2222292]rINanDO[/MENTION] does have a "fix" though he's deprecatingly referred to it as a hack! Let's call it a 'Workaround' for diplomacy.

It's not being implemented for what, I assume, must be a good reason? Link
[Galaxy S II Android Development] laptopu:
Hmm, but even with emulated storage this still prevents external SD card use with file manager. A proper fix is needed as this affects everyone, rather than individually applied workarounds.
[Galaxy S II Android Development] suapoc:
I have the same issue it tells me that my Systempartition has a size of 8,77 GB and that it is about 60-70% filled.

I reflashed once (to test another rom) already and it happened again this time so this must be a bug?

*edit

The other Problem i have is that most LOS-System Apps seem to have Problems to access sdcard0. This also applies to bluetooth file transfers. the incomming transmissions window just crashes when i hit the filename of files i recently received... most likely because they were stored in sdcard0/bluetooth ;D

Is there a way to get rid of this behaviour.... like switching to emulated storage?
[Galaxy S II Android Development] Shambles22:
Try this
[Galaxy S II Android Development] gm0:
That link doesn't seem related, but I'm not familiar with the file manager code so not gonna dive into that. A simple suggestion would be to see what the default file manager is doing and what other open source file manager that are working correctly are doing differently, e.g. https://xdaforums.com/android/apps-games/app-amaze-file-managermaterial-theme-t2937314

---------- Post added at 13:33 ---------- Previous post was at 13:32 ----------

yes it's a bug, just ignore that number, it's completely bogus
[Galaxy S II Android Development] Hamzaps:
Hi guys .. Am on cm 13 and want to upgrade to cm 14.1 .. Tell me plz .. Do i need to install the experiment and the nightly or just the latest nightly build plz help
[Galaxy S II Android Development] Boolian:
Well, my link was exactly related to the File manager.

Admittedly my coding days were over two decades ago, so diving deeper confuses the hell out me too. But I get the gist of it.

The Lineage team have developed their file manager, and I doubt they will write another because of a tiny bug in a (now getting old) device. But, the Devs are looking at it.

If it's not labour intensive I'm sure it will be worked out.

Otherwise it's just going to become a legacy bug like other Roms before it.

It's no biggy, I've never used a stock file manager in years.
[Galaxy S II Android Development] todonormal:
I think what spirit could include in rom: https://github.com/mikereidis/spirit2_free/blob/master/README_OPENSOURCE_BUILDING.txt

But this experimental not is official, because was deleted

This it's last free version: https://xdaforums.com/apps/spirit-fm/app-spirit2-free-source-real-fm-radio-t2951455
[Galaxy S II Android Development] gm0:
No I got that, but it didn't seem related to the specific issue (the error description doesn't match at all: "Somehow the ls-command (line 52) is returning an error-code because of access denied on .android_secure-folder but still printing the directory contents.") . But as I said, I'm not familiar with the file manager code. Going by that one file it seems very strange that it would implement shell commands rather than native functions though...

edit: ok, nvm that, after renaming the .android_secure folder the file manager starts working so it's probably related after all, my bad. I thought it was something else because it said it would still print the directly contents when for me it didn't.

Also the bug in the source is probably dropping stdout "1>/dev/null" rather than stderr "2>/dev/null" and then not handling the error message correctly. Same issue with a few other commands.

I wasn't suggesting to switch to another file manager, I was suggesting to look at another file manager's code to see how it handles the specific task that's failing in lineage's code.

PS: Also that bug is not device specific.
[Galaxy S II Android Development] bujjo53:
Install just the latest nightly because the experimental was deleted
[Galaxy S II Android Development] peterpunk01:
Hello everybody.

After installing LineageOS, i've looked into storage/system of my i9100 and it occupies more then 12GB. is it normal?

thanks for your efforts and keep up the good work.
[Galaxy S II Android Development] bujjo53:
Why i can't install magisk on this rom ?
[Galaxy S II Android Development] Mirajoo7:
is there anything to do on the future nightlies for the color banding issue on gti9100

---------- Post added at 03:32 PM ---------- Previous post was at 03:28 PM ----------

I think many of the s2 users not noticed about the color banding issue in the display
[Galaxy S II Android Development] thiti31:
Hi everybody,

does anyone have a problem with the camera ?

All pictures are grey and cannot be opened. Test with the last 22/02 nightly build.
[Galaxy S II Android Development] Nobby1960:
No - what about "color banding issue", is there a screenshot to see?

I guess there is an issue with SU.
[Galaxy S II Android Development] Boolian:
Yeah, that's cool, I see what you're saying and you're right, It's not specific only to our device, there is a Jira for it.

So anyway I'll leave that topic, I've nothing constructive to add to it. Unless I have a blinding flash:D
[Galaxy S II Android Development] treysis:
Also tried that one. Still only 1-2 seconds of audio from radio and then it stops.
[Galaxy S II Android Development] Nobby1960:
[MENTION=5926322]treysis[/MENTION]

Have you flashed the ROM new again? Maybe it helps.
[Galaxy S II Android Development] ale5000:
It doesn't mean anything, just because it was deleted do not remove the fact that they have released it; you can also verify the MD5.

They have removed it for a SELinux linux issue that in my opinion isn't critical and since it is a nightly build bugs like this are to be expected.
[Galaxy S II Android Development] gm0:
Nope, working fine here.

No such issue on my end, color gradients look fine.
[Galaxy S II Android Development] todonormal:
Yes, but, it's "obligatory" create new experimental... review all others devices
[Galaxy S II Android Development] Draky50110:
What is "emulated thing" purpose ?

Just to have multi user on a small smartphone ?
[Galaxy S II Android Development] shkedov:
Not just that, lol. Go to the link from OP to the related thread and read there especially the OP. You should keep reading the whole work so far (9 pages) to understand whats going on, it is a necessity.

This thread is for the LOS, please keep the questions relevant to the topic respectively.
[Galaxy S II Android Development] NikosTweak:
5GHz WiFi network does not work on new build lineage 14.1 20170213. More people?
[Galaxy S II Android Development] toy_story:
I know about an issue updating via OTA.

Quick update if the error via OTA
[Galaxy S II Android Development] max6698:
Emulated storage allows you to combine the space currently used by your internal SD partition with your data partition. If you ever have "insufficient storage" errors when installing something, but you have plenty of space in your internal SD partition, emulated storage is the answer.

But please read up on the risks at https://xdaforums.com/galaxy-s2/orig-development/mod-switch-emulated-to-emulated-t3539651 :)
[Galaxy S II Android Development] mwnn85:
"Insufficient storage" is simply lacking a big enough \data partition isn't it?

I don't think "emulated storage" is to be confused with Android 6+ optionally merging an external SD card with internal memory.

Correct me if I'm wrong though.

I thought there are 3 main benefits:

<> Greater than 4GB individual file size limit (perhaps not that important on a phone with ~13GB of storage)

<> EXT4 is more reliable/faster than outdated FAT

<> Security; enabling the ability to encrypt any personal files along with any app data since everything is held in \data. Your personal files would normally be held in the unsecure \sdcard partition.

Any other reasons experts? Does Google mandate that it must/should work this way?

Given it's age the old i9100 seems to have a few odd quirks with it's \preload partition and 512MB \system partition; it doesn't now though!

Great to see it get updated to Nougat (....and beyond?)

Flash to Nougat now or wait a while for emulated storage.

It sounds like it's all mostly working.

I get around 7 days of battery life with the phone left idle on CM13. The phone is obviously much faster than TouchWiz.

Purely used as a phone - I can't see why'd I'd need to replace it!

Does the newer aggressive Doze in Nougat make any more of a difference? Already have Greenify.
[Galaxy S II Android Development] max6698:
Yes, and once you have emulated storage you can shrink the internal SD card partition and give that space to the adjacent /data partition.

Your other reasons are good too :)