yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] laptopu:
Another one for integrating to ROM please, last weeks build where it was enabled by default was much better.
[Galaxy S II Android Development] rINanDO:
I'm currently investigating the default version since I was aware of its existence a week ago. I can tell the dialog/framework seems to be buggy. I already did some tests by converting these settings to bln breathing settings. Since the dialog is only available by searching for it I doubt it is being maintained at all, but that is my assumption.
[Galaxy S II Android Development] Klaerchen:
I think you can activate the LED notification menu in the overlays:

diff --git a/overlay/frameworks/base/core/res/res/values/config.xml b/overlay/frameworks/base/core/res/res
index a281f0d..382903a 100644
--- a/overlay/frameworks/base/core/res/res/values/config.xml
+++ b/overlay/frameworks/base/core/res/res/values/config.xml
@@ -175,4 +175,19 @@

<!-- Enable button brightness -->
<bool name="config_deviceHasVariableButtonBrightness">true</bool>
+
+ <!-- Is the notification LED intrusive? Used to decide if there should be a disable option -->
+ <bool name="config_intrusiveNotificationLed">true</bool>
+
+ <!-- Is the battery LED intrusive? Used to decide if there should be a disable option -->
+ <bool name="config_intrusiveBatteryLed">false</bool>
+
+ <!-- Default color for notification LED is white. -->
+ <color name="config_defaultNotificationColor">#ffffffff</color>
+
+ <!-- Default LED on time for notification LED in milliseconds. -->
+ <integer name="config_defaultNotificationLedOn">1000</integer>
+
+ <!-- Default LED off time for notification LED in milliseconds. -->
+ <integer name="config_defaultNotificationLedOff">9000</integer>
</resources>

Would you give it a try?

Regards

Klaerchen
[Galaxy S II Android Development] rINanDO:
Thanx! That is useful information! I will give it a try!
[Galaxy S II Android Development] Give me a piggy:
Will we have theme engine like CM13 soon?

Plus could it comes with quick exit to HOME by clicking the blank area in the Recent Apps Menu?
[Galaxy S II Android Development] kami0911:
I just switched an old S2 from Stock to the last LA14.1-Build (20170628) and now the home button and left soft button is not working. If I press it longer, the phone vibrates for a brief moment.

On the homescreen, the left button will open the homescreen-customization, but on every other screen nothing happens.

Are there known issues about the buttons?
[Galaxy S II Android Development] Sub_Zero2:
Not as i know of
[Galaxy S II Android Development] ale5000:
[MENTION=2222292]rINanDO[/MENTION]: I get graphic corruption

See the screen record.

---------- Post added at 04:53 ---------- Previous post was at 04:31 ----------

Also why on this site I get a big "flipped play button"?

It isn't the same on the pc.
[Galaxy S II Android Development] Ri9000:
previous versions are configurable in settings.
[Galaxy S II Android Development] kami0911:
OK, I messed that up on my own... Seems, I broke the ROM by updating the modem after flashing the Lineage-ROM.

Reinstalling from scratch, modem first solved the problem and now the device is working fine.
[Galaxy S II Android Development] ale5000:
You won't broke the ROM if you flash modem withOUT RIL.
[Galaxy S II Android Development] dumdidum123:
Anyones dialer app crashing? while it took up to 8 seconds until my phone showed up the screen to take up an incoming call in previous builds, it now sometimes just crashes without showing the incoming call. It just vibrates and I need to wait until the caller stops or my mailbox took up the call. Then I can look up in the history, who tried to call and can call back.
[Galaxy S II Android Development] Boolian:
I had problems like that recently, but it was a result of rebuilding a new device. I installed a USB board which was the wrong revision number.(Rev2.2/Rev2.3) Correct board solved all problems and better signal reception too.

Probably not your problem though, unless any hardware has been changed recently.
[Galaxy S II Android Development] gm0:
Just to follow up on that in case you're interested: I didn't figure out what was wrong with my wi-fi settings that made the connection go into a crazy connect/disconnect loop when google couldn't be reached (I didn't see any option exposed via the UI that could have been responsible) but in the end simply resetting the network settings via the same named UI function fixed the situation, it connects normally again now.

---------- Post added at 18:50 ---------- Previous post was at 18:41 ----------

Mine is neither crashing this build nor was it slow in previous builds. So something is wrong on your end. Start with a cache wipe if you haven't already, otherwise try resetting dialer settings or consider a clean install. If you're using OpenGApps that may also be the culprit since it replaces files relating to the dialer, you might need to use a different GApps version (I'm not using GApps so I can't say what version is good).
[Galaxy S II Android Development] cristihan:
Strange name for internal storage after repartiton on Galaxy S II

After I increased the system partition with "lanchon-repit-20160406. . . .zip" via TWRP everything was ok. I have installed LineageOS but now my internal storage appears in file explorer " ^ N" instead of "Internal Storage" as it was before (the pictures are attached). How do I rename the partition?
[Galaxy S II Android Development] Nobby1960:
I know that - this is an older bug, it comes sometimes but no idea why. In this case I did make a full wipe and a repit again.
[Galaxy S II Android Development] cristihan:
Thank you, already I tried this option but nothing has changed.

---------- Post added at 10:02 PM ---------- Previous post was at 09:57 PM ----------

I forgot to tell you...I've also come back to stock ROM with ODIN and stock pit file but still no result.
[Galaxy S II Android Development] Nobby1960:
Phew, that would have been my next tip. You can still try to flash the stock ROM with the attached pit file. Make no repit again before you flash the custom ROM, you have enough space with it, perhaps it solves your problem. Good luck!
[Galaxy S II Android Development] gm0:
Those aren't the partition names, those are the mount point names and default to sdcard0 and sdcard1 (see https://github.com/LineageOS/androi...798d27b22a47686db775db/rootdir/fstab.smdk4210). Did you wipe/reformat /system, /data and the caches in TWRP before installing?
[Galaxy S II Android Development] EngineJoe:
You can mount the Internal Storage SD card as USB Storage in TWRP, connect to PC, then select Properties in Explorer and rename (assuming FAT file system).
[Galaxy S II Android Development] cristihan:
It did not work...:(
[Galaxy S II Android Development] cristihan:
Thank you for reply. Yes, I did done that including with "Internal Storage" wich after first repit with "lanchon-repit-20160406.zip" appeared as another SDCard on TWRP screen and not "Internal Storage" as it was before.
[Galaxy S II Android Development] gm0:
Since you mention that, what TWRP version are you using? The latest TWRP 3.1.1-0 did not work on my device, it cannot read my partition table at all. TWRP 3.1.0-0 works fine though. Maybe worth a try to reformat with that.
[Galaxy S II Android Development] Nobby1960:
I see you tried an older version from Lanchon Repit. I attach a newer build, but you must rename the zip file after download, because the forum software makes an underscore from the "=". The syntax is:

lanchon-repit-20170115-system=1G+wipe-data=6G+wipe-sdcard=max+wipe-preload=min+wipe-i9100.zip
[Galaxy S II Android Development] dzikk:
This rom is to stupid. I pass safetynet but pokemon go doesn't work
[Galaxy S II Android Development] cristihan:
Thanks ! I'll try this file tonight.
[Galaxy S II Android Development] marcimix:
nah! I lost the bln after LineageOS upgrade under options.

Finger crossed who is still working on it! :fingers-crossed:
[Galaxy S II Android Development] cristihan:
Did not work !
[Galaxy S II Android Development] cristihan:
SOLVED - Strange name for internal storage after repartiton on Galaxy S II

Many thanks to all who answered me. I solved this problem as below:

- I installed via ODIN stock ROM and repartition with stock pit file (u1_02_20110310_emmc_EXT4.pit).

- Restarted device with JB and setup my phone.

- When was done, got this notification "Unrecognized USB device", I clicked on it and offered to format it. Clicked OK.

- Checked in "My files" and reappeared sdcard0 and extSDCard as it was from the factory. :o

- Rebooted in Recovery mode and instaled "PhilZ-cwm6-XXLSJ-OXX-4.00b21-signed-JB.zip" via stoc recovery. (no waranty void message after rebooted system)

- Rebooted in Philz Touch recovery and clicked Wipe -> cache, system partitions.

- Flashed kernel Lanchon IsoRec CM13, flashed TWRP recovery and rebooted in Recovery mode.

- On TWRP home screen, installed "lanchon-repit-20170115-system=1G+wipe-data=max+wipe-sdcard=2G+wipe-preload=min+wipe-i9100.zip (thanks Nobby1960). After has been done with repit I went back to TWRP home and clicked Wipe -> Dalvik, Cache, System, Data and Internal Storage.

- Returned to TWRP home again and flashed LOS and addonsu-arm-signed zip's, cleared Dalvik/Cache and reboot system.

After the device started it appeared in File Manager "sdcard0" and not that strange name ^N . ;)
[Galaxy S II Android Development] Sub_Zero2:
Try disabling root in developer options, and try again
[Galaxy S II Android Development] Boolian:
That's great you 'cured' it.

I've never bothered with the problem before.

Though, looking at your method, there are complete software wipes and partitions a couple of times. So unless the problem lies somewhere at Kernel level, I'd imagine just a single partition & clean install should solve it.

I always thought it was just crappy file manager, since nothing else has a problem (for me) Terminal session, 3rd party file managers etc. nothing wrong.

Just the system File Manager (DocumentsUI)

It also is a cross-platform issue, not just Lineage (MIUI,OxygenOS etc) so some module is persistent and propagating. The "corrupt name" is also identical across platforms, so it's not random gibberish.

Anyway, your post made me think about it again and showed good clear steps.

:good:
[Galaxy S II Android Development] dzikk:
I have disabled root access and I pass safetynet but now I have no GPS ..... :(
[Galaxy S II Android Development] Sub_Zero2:
Did you have gps before you disabled root?
[Galaxy S II Android Development] gm0:
Well, they're all based on Android, the distributions typically don't tinker with the underlying system much. If it's cross platform issue (I've never seen it myself actually) it is likely to be found in MountService or more likely the volume daemon (vold). Can't be DocumentsUI since I believe he said he also saw the issue when he first flashed the stock ROM again?

PS: By the way, new build is up, although I haven't flashed it yet: https://mirrorbits.lineageos.org/full/i9100/20170705/lineage-14.1-20170705-nightly-i9100-signed.zip. edit: flashes fine, BLN still non-functional without the mod.
[Galaxy S II Android Development] dzikk:
I had gps on stock and last CM13... Probably I had to reflash stock... maybe repartition for Lineage broken something

Wysłane z mojego Redmi Note 3 przy użyciu Tapatalka
[Galaxy S II Android Development] cristihan:
After reading your post and reviewing all the operations I've done, I think you are right and single partition + clean install was enough, if I stayed on stock ROM. My fear was that after repartition for LOS I will get where I was from begining. Probably the older version from Lancheon Repit that I used first time was a problem too, because I saw that others had the same problem after the repartition with Lancheon Repit 2016.
[Galaxy S II Android Development] Sub_Zero2:
Search this thread for gps problems
[Galaxy S II Android Development] JaLoou:
Bugs for fixing.

Hello.

Sorry for mistakes in my poor English.

I flashed the last official LOS firmware and I want to report few bugs of it.

1) It is impossible to set manually 2017 year in the date setting menu in a portrait mode due to numbers of years are very limited in the portrait mode there.

This bug does not exist in the landscape mode.

2) If newer version of some app is installed then the LOS to do not allow to install apk file of previous version of the same app. The LOS reports wrongly that the apk file is allegedly corrupt.

But factually it is not corrupt.

3) The unlocked version A Better Camera app reveals by its menu that this last LOS probably does not provide Camera2 api to the installed camera app.

I kindly ask the LOS developers to fix the bugs above as quickly as possible. Please.
[Galaxy S II Android Development] gm0:
Bug reports go here: https://jira.lineageos.org/projects/BUGBASH/summary

I cannot confirm any of your three issues though, all of that is working just fine for me.
[Galaxy S II Android Development] ale5000:
There is a new change related to button lights.

Does anyone tested if it doesn't break anything on S2?
[Galaxy S II Android Development] Boolian:
Re: the naming error-

I'm intrigued as to where the persistence lies.

The 'error' was maintained after a first return to stock Rom/Pit (apparently) but disappeared the second time. You're probably correct that Vold is returning the sdcard Label/UUID, but from where? An Fstab file or somesuch. I don't know where that is in 7.0 (pardon my ignorance)

Though I'd imagine it's probably integral to the bootloader now, which should have been replaced/cleared during any clean Rom flash.

So, yeah. Vold/Fstab Label field may be 'corrupt' but UUID etc. are ok.

Other ways of interrogating SDcard (3rd party file managers, terminal etc) return UUID/ mount point names/blocks correctly, even parsing them as eg. Sdcard1/Sdcard0 or Internal/external SDcard - but the system file managers (DocumentsUI) choose to return the "Label" field instead.

How Vold gets the same weird Label name is another story, I'm just wondering if the Label field can be edited. Maybe it would need a repackaged bootloader though.

Basically, there should be an easier fix without backing up gigabytes of data, just to try reformatting the ext Sdcard and/or the pain of re-installing a Rom and data from scratch.

*Edit "blkid" command from terminal in OS returns a volume Label :[/dev/block/mmcblk1p1: LABEL="M-^IPNG^M^J^Z^J" ...]

But within terminal via TWRP, it returns no Label field at all.

Hmm that's odd.
[Galaxy S II Android Development] Sercan Ali:
How can I activate Google Assistant without build.prop editing? Google play services is on latest version and I am a beta user of it... My default language is English US...But still only now on top is working.
[Galaxy S II Android Development] Klaerchen:
The change needs to be activated (which it is not for out i9100) with "config_buttonLightOnKeypressOnly=true".

And then it works in the power manager, which always is in control of the button LEDs, i.e. it would work with the BLN implementation.

And I built and tested it: no problems :)
[Galaxy S II Android Development] gm0:
I linked the file above on the github. On your device it's in the root directory /.

Maybe that's the source of your trouble then? Here's my blkid, note that lack of labels with one exception:

i9100:/ # blkid
/dev/block/zram0: UUID="2e8103c4-f31d-4d31-b691-eff1a5ac865f" TYPE="swap"
/dev/block/mmcblk0p1: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p7: UUID="e2d6950a-233c-49b9-a92d-bdd41b9dd223" TYPE="f2fs"
/dev/block/mmcblk0p9: LABEL="system" UUID="da594c53-9beb-f85c-85c5-cedf76546f7a" TYPE="ext4"
/dev/block/mmcblk0p10: UUID="72eef2a8-c353-49fe-bc33-8118489cf862" TYPE="f2fs"
/dev/block/mmcblk0p11: UUID="9ab97a5b-3d88-44e4-a409-559d7e674719" TYPE="f2fs"
/dev/block/mmcblk0p12: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk1p1: UUID="2D83-0B5A" TYPE="exfat"
[Galaxy S II Android Development] Boolian:
Cheers. I'm going to have a delve tmoro.

Also, I should have clarified the '"returns No Labels" thing.

Both Terminal commands returned the 'System' label as they should, I just meant blkid within TWRP shows no label for any other block, only the UUID's etc. Whereas within the OS it showed the extra 'corrupt' label.

Of course that disparity is very odd. I can't quite think why the blkid commands should return different results.

It was just chance I tried it within TWRP as I was thinking maybe I could utilise 'FatLabel' on the extSdcard, as TWRP now includes 'dosfstools' (apparently)

Wasn't sure in quite what capacity it's included and was just poking around

:D
[Galaxy S II Android Development] gm0:
TWRP comes with its own fstab.

My blkid above was from within LineageOS.

I've seen that tune2fs is available (surprisingly actually), have you tried if you can modify the label with that?
[Galaxy S II Android Development] JaLoou:
Hello again.

Sorry for mistakes in my English.

First of all there is an announcement that they do not accept bug reports at weekends. But it is a best time for me for bug reporting.

The second: may you do not experience the bug with manual year entering because you use automatic date setting.

But I can proof by an attached screenshot that I have such bug.

And third: Camera2 api provided by LOS on our device incompletely and may incorrectly. Many specialised camera apps admits it. I attached few screenshots for proof that.

And in general, I think it is sad for us because modern specialised camera apps can significantly improve the old camera of our resurrected dude, which I use almost everyday for some documentary recordings.

For instance, the A Better Camera app somethimes provide HD video recording with 120 frames per second on our old device but this feature is not stable. It can provide also much better possibilities at low light conditions. The Open Camera app allow 4x zooming at Full HD recording. All these features are impossible by the Samsung's camera app with official firmware.

I think that manual focus can be also very useful for resurrect a camera of our old device. And if Camera2 api will implemented correctly then we will get more full-fledged 2nd life for our lovest device.

Unfortunately, I'm a noob in tech. And I'm able to make suggestions only. Please, implement full Camera2 api to our device correctly. If someone do it then it will be a significant step ahead for our old device even beyond many modern devices.
[Galaxy S II Android Development] gm0:
False, in fact they ONLY accept bug reports on weekends. You can file one today.

Actually I understood your problem now. That screen has some weird scrolling. You need to use two fingers. Hold one finger onto the list of years and then scroll with the other one. Alternatively you can select the bottom-most year, accept and reopen that window until you've reached 2017.

I agree this should be changed.

All I can say is that both the built-in camera app as well as OpenCamera that you mention and that I use have no problems with the Camera2 API and allow setting all those things that your screenshot says cannot be done. So the problem may be with your A Better Camera app. I don't know because I've never used that app. I don't understand why you mention Samsung's stock app because that has nothing at all to do with LineageOS.

PS: OpenCamera can also record at 120 fps if that is a feature you require. I don't recall if the built-in app can do it.
[Galaxy S II Android Development] Boolian:
Thanks. Tried that, no joy. Superblock error or somesuch with :

tune2fs -L newname /dev/block/mmcblk1p1

Maybe my syntax is dodgy.

I found I could simply rename the sdcard stuck in an adapter on pc. Which shows up ok when reinserted,

But if I leave it blank, it's assigned the same odd characters in the OS file manager (and Total Commander also, as I discovered)

So whether it's an artifact of the sdcard table/mbr itself or it's the OS doing the assigning, I have no idea.

Couldn't find the above block listed in fstab.smdk4210 either when I went looking for the Label field., so how it's mounted at bootime I pass.

I trawled various files looking for clues.

It's not a huge issue, thanks for the suggestions so far. I've run out of talent I think

:p
[Galaxy S II Android Development] Carontes:
Hello, sorry if my question could be stupid but is this ROM compatible with Galaxy SII plus (I9105p)? What could it happens if I try to flash it into that device? Does it brick or just something doesn't work (like NFC, etc.)? Thank you
[Galaxy S II Android Development] Nobby1960:
This ROM is only for the SII GT-I9100. You find here an unofficial Nougat build from LineageOS for your I9105p.
[Galaxy S II Android Development] Carontes:
Thank you
[Galaxy S II Android Development] gm0:
Ah, so this is an issue with FAT volume labels then? exFAT has unicode labels, so your odd characters might be due to an encoding problem. What did you use for setting the label in the first place?

I tried reproducing but I am not sure what you mean by "if I leave it blank". If I just mount my external sdcard under Windows without touching the (not set) label then no label gets set and it shows up with the default sdcard1 moniker as defined in the fstab. If I set a label and then remove it again from within Windows 10 x64 via label.exe it also shows correctly back on the phone.
[Galaxy S II Android Development] Boolian:
Yeah, I think it's difficult to reproduce if you haven't experienced it. It was a new card at the time and was adopted/ formatted in late CM13 as vFat no label assigned. Though I think it was Lineage.

A Google of "m-^ipng^m^j^z^j" is interesting. I've seen it reported in Omni Rom 4.4 and [MENTION=7783831]cristihan[/MENTION] who just asked about it, reported it as persisting after flashing back to stock jellybean (?) after his issue appeared.

I used the same procedure as you mentioned - in Win10 (mount external via card adaptor) label shows 'corrupt' . Rename via label.exe as eg: EXTSD then remount in phone and DocumentsUI shows the changed label correctly. Remount externally in Win10

Still shows correct rename. Delete label name via label.exe (field is blank) and Win10 shows no label name.

Remount in phone. Label name becomes 'corrupt' again (identical characters) remount external back in Win10 & it's shows ' corrupt: name again in label.exe.

I wouldn't lose too much sleep as it's a minor irritant. I Just took an interest as I thought the whole reflash/ repit solution was extreme.

Though interestingly, in [MENTION=7783831]cristihan[/MENTION] example, his initial corrupt name deviated from the usual characters reported by many, though I also noticed he has an unusual (manual?) rename of his internal SDcard also.

Anyway, thanks for some of the pointers.

It appears something, much like nature, abhors a vacuum.

Or should I say abhors a 'null'

:D
[Galaxy S II Android Development] gm0:
It's just an interesting little issue, that's all. According to your screenshot your sdcard is using vfat, that may explain why I cannot reproduce it since I have no vfat partitions in my device - I use f2fs for internal storage and exFAT for external storage. Alternatively something about the original partition table was bad and if you were to reformat the sdcard as vfat the issue might go away as well. Something to try if you're ever bored I guess. ;)

PS: I assume you did run a chkdsk over it in Windows though?