yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Boolian:
Yup, I like interesting, the investigating always adds to sum of knowledge.

Yeah I ran chkdsk which confused me more as it returns FAT32 for the extSd card. I dunno, maybe it does that with vFat as its the same family.

But it is odd that vFat. I'd not knowingly format a microSD in that format. I didn't pay much attention til recently, assumed the AOSP OS's originally formatted /adopted microSD's as Fat32 or exFat ?

Also, I used to have internal as ext4 but after recent hardware rebuild, this board is still on vFat internal.

In a hurry rebuilding - forgetting this board is from an old Neatrom/stock device.

Anyway, it's kinda looking like a FAT mismatch somewhere along the line. Pointing my finger at vFat lol!

I wonder if somehow vFat was added to microsd card table without data loss? Nah surely not

I think there's something in this partitioning/FAT

Since [MENTION=7783831]cristihan[/MENTION] had a persistence after returning to stock rom and only cured with a total vanilla reflash/repit and format of microSD.

I wonder what his two FAT's are?

AOSP is native ext4 throughout yes? Perhaps if the internal storage is left as stock vFat it takes the huff! Those who change internal storage during repitting never see the problem.

Still doesn't explain how my extSDcard got to be vFat though...
[Galaxy S II Android Development] gm0:
Wait what? Adopted storage cannot be FAT at all, it needs a POSIX file system for its file ACLs. Originally you had said you specifically formatted that sdcard as vfat under CM13.

Oh you used repit? Maybe that is the culprit? A messed up partition table and using a tool that changes it makes that the first thing to look at tbh. But I thought we were talking about your external sdcard here. I'm confused now.

I don't understand what you mean by this. Factory file systems for SD cards are FAT32 or exFAT depending on size. If you did not specifically format vFAT then the tool you used might simply give you the wrong data - android uses the vfat driver to access FAT32.

AOSP does not require a specific file system for internal/external storage, but due to some sloppy coding part of the framework is actually incompatible with POSIX-type file systems on external.

I only changed my filesystem on internal later and never ran into the issue so the causality is not a given. I never used repit though, I flashed a new partition table in download mode.
[Galaxy S II Android Development] JaLoou:
Hello again.

Sorry for mistakes in my English.

First of all, I have seen your link last Saturday and there exactly was an announcement that currently they do not accept bug reports at weekends. Unfortunately, I did not maked a screenshot of it at that moment.

And I do not know why there was such announcement last Saturday.

And second: there is an easy proof that Lineage OS 14.1 for i9100 does not provide Camera2 api fully correctly (and probably does not provide it at all even) for our device because if Camera2 api will implemented without bugs in our device then among many other significant camera improvements there semi-professional camera apps like A Better Camera or Manual Camera will show smooth slider for adjust a camera focus manually precisely. But now various camera apps show only few presets for a camera focus and there is always the absence of focus slider.

Moreover, I want more people to know that A Better Camera app allow to record much better videous at low light conditions (getting it by lowering frame rate to 15 fps and even to 10fps) on last Samsung's official firmware Android 4.1.2 for i9100 rather then now with a buggy LOS 14.1...

Sorry, some photo and video stats are my serious hobby and I know that an old camera on i9100 can give to people much more - just we need to be able 'to squizze' it.
[Galaxy S II Android Development] rINanDO:
I took a deep dive in the camera HAL last year to get it running on Snap with all its features and other camera apps. Some features the i9100 camera simply don't support it by hardware. Implementing an API doesn't mean you must implement all its new features. Like for the focus slider there is no way we can instruct the camera to do so because we can only tell the camera its focusmode. Fixed, macro, continuous, infinite, autofocus for example. There is no manualfocus register to set it on 40/100 or some kind. Features the camera doesn't support won't be exposed and the camera apps should disable the unsupported features because it could lead to system crashes. Even some camera commands must be executed in special order otherwise this could crash or hang the HAL also. Most of the time the command order is an issue causing the bugs. Recording at 120fps will never happen. The HAL already exposes supported fps by hardware. Forcing unsupported fps just crashes the driver if I recall correctly. If I got time I will look to those camera apps again. It will help if someone tests which features the LOS implementation is missing compared to stock ROM.

About video recording (you could probably noticed already), some i9100 camera's drops framerate automatically in low light conditions. If don't like this behaviour, you could set focus to autofocus. This will keep framerate stable, but also disables autoexposure as a side effect. This is not a bug in the CameraHAL but a ' feature' on some camera's.
[Galaxy S II Android Development] cristihan:
You have the screenshot with my partitions attached. SDCard is "vfat" .Hope this will help you.
[Galaxy S II Android Development] Boolian:
Apologies for the confusion. Bad editing. That line about adopted/ formatted should only have read Format. ie: "The default behaviour of AOSP when formatting microSD is to use exFat or Fat32 I assume"

The other stuff is correct. Agree what you say.

The initial conditions appear to be that a user has Fat32 microSD and Stock OS on vFat internal storage.

During repitting/flashing new Rom, the microSD suddenly shows a 'corrupt' volume label.

Formatting the micro Sd card again does not always cure the problem according to user reports.

I imagined that there was an OS table/file with a corrupt volume label name which was being read instead of the table of the microSD, but never found anything. Perhaps it had retained an association between the UUID of the microSD and a different FAT. causing some weird behaviour.

Moving forward on the principle it was entirely a corruption of the microSD card FAT, this was checked. blkid etc identified the micro SDcard as vFat. No corruption was apparent, the card functioned well and was not flagged in any way by eg: WIN10 chdsk (which reported it as Fat32 for some reason,assuming it just reported vFat as Fat32 for.. reasons)

Then the volume label was changed to "EXTSD" in Win10 (label.exe) and showed correctly when remounted in the phone (still vFat) and also correct when mounted again, externally, back inWin10.

The label name was deleted in Win10 and showed no label only a drive letter. It was inserted back in the phone and the corrupted name reappeared.

It was again mounted externally in Win10 and it showed as a corrupted name there also.

I made an assumption that the "blank" label was being corrupted when the microSD was inserted back in the phone by the android OS and written (non data destructively) back into the microSD table (if that's even possible!)

The alternative is that the FAT table of the microSD somehow retained a corrupt volume label field, even after this field was deleted, reported deleted and returned a "blank" volume label from command line in a Win10 terminal session (which would be quite bizarre)

If I don't accept that, then I'm right back to pointing the finger at the android OS somewhere.

What the specific conditions users are executing to receive this error I don't know. The corrupted label name was reported as persisting even after flashing back to stock rom. Which puts us back in a circle to pointing at the FAT of the microSD. Maybe it is some artifact of repit tool after all, but hundreds use it with no problems. Who knows?

All I know is one day I had a Fat32 microSD then it was vFat with a corrupted name. Whether others experienced this change of FAT table I don't know, perhaps not.

I've just spent a few hours backing up/restoring gigabytes of data rebuilding my device and microSD from scratch in a rage quit!

Two day ago I was quite content with the corrupt file name, it wasn't bothering me or affecting performance.

:p

Thanks again for all the input. Sorry for the long post and I'll stop cluttering up the thread with this now.
[Galaxy S II Android Development] PhoenixNZ:
[MENTION=2222292]rINanDO[/MENTION]

First, Thanks for all the hard work you've been putting in for our old S2 i9100's. Great to still have my phone ticking along, and now on Nougat.

If I recall correctly, recently you found a bug relating to dropping to 800MHz and our S2's locking at this as the Max.

I was wondering if you were ever able to get around this speed clamp?

Still sitting on 20170531-Nightly, and just wanted to know if its worth updating to latest nightly.

Cheers and Thanks again.
[Galaxy S II Android Development] Nobby1960:
I had this issue after flashing a stock ROM with pit file and after using the Repit tool from Lanchon for more times, randomly. In every case I did reflash the stock ROM with a pit file again to solve it.

---------- Post added at 12:45 AM ---------- Previous post was at 12:39 AM ----------

As far as I know [MENTION=2222292]rINanDO[/MENTION] wrote here, this is a specificity of the Exynos CPU. It clocks down to 800 MHz automatically at a certain temperature. You can't solve this issue with the ROM.
[Galaxy S II Android Development] PhoenixNZ:
Ah, yes. I found the post (finally). I must have originally interpreted it that it may have been possible to correct it, or that the temperature wasn't correctly being determined.

And, foolishly, hoped there was a method to release the lock if the temperature dropped.

My bad. This will teach me not to gloss over the details. :o
[Galaxy S II Android Development] JaLoou:
The short video 120fps recorded by me few days ago using the fully unlocked A Better Camera app on GT-I9100 with the last LOS 14.1 firmware is available for download by the link: https://mega.nz/#!dAMzwZaL!Unt0KdiqWhOdSBV3h9t9eZ220Y2kHvZGDHe8UIIr5xA

But my main point is not about a frame rate.

My main point is about video recording in low light conditions.

And the A Better Camera app allow it much better on Samsung's official firmware with Android 4.1.2 rather than on LOS 14.1 or many other specialised camera apps with LOS 14.1.

For better understanding me, please, make the next simple trick:

1) Get i9100 with the last official Samsung's firmware Android 4.1.2.

2) Install there the last free version of A Better Camera app from the Google's Play Store.

3) Run A Better Camera app.

4) Switch it to a video recording mode.

5) Then go to a dark place or at least point the camera of your smartphone to a dark place.

6) Choose ISO800 in settings.

7) Choose a Firework profile in Scene modes.

And you will see a some magic: the dark scene becomes bright significantly like by a semi-night vision device.

Now you can start a video recording.

There are yet few other tricks with the settings in A Better Camera app for make a dark scene yet more bright.

This useful magic becomes impossible now with LOS14.1!

WHY???
[Galaxy S II Android Development] JaLoou:
The bug with password entering for WiFi.

The yet one serious bug is with password entering for WiFi.

Sometimes it allows to apply a password of 5 symbols lenght (the link 'connect' is active).

But it not allows passwords of 8 or 9 symbols lenght (the link 'connect' is inactive). And so on...

I had attached screenshots for illustration.

Please fix it.

I was unable to determine in what situations it happens exactly. But it happens twice with me for last few days.
[Galaxy S II Android Development] rINanDO:
I found by accident why it falls back tot 800mhz. It is the thermal protection of the CPU. When the CPU gets hot, it lowers the maximum speed to cool down. So it is not a bug, but default feature.
[Galaxy S II Android Development] Boolian:
I had promised to leave this, but a last question :

You say you flashed the Stock Rom with a PIT file to solve the corrupt label name.

Did you ever need to reformat, or alter your microSD card in anyway afterwards, or did it just start showing the correct label name again?
[Galaxy S II Android Development] Draky50110:
Hello.

As a new user of Netflix, I'd like to know why the app is not available on PlayStore for the i9100 + LOS ?
[Galaxy S II Android Development] Sub_Zero2:
Go to developer options and disable root.

Now you can install netflix.

(You can enable root afterwards)
[Galaxy S II Android Development] Draky50110:
Will I be able to update it later with PlayStore, if I root again ?
[Galaxy S II Android Development] Sub_Zero2:
Not sure but you can always disable root and try
[Galaxy S II Android Development] gm0:
I don't see any other way than it being an issue on the microSD itself tbh. Easy way to test is to move the microSD from one phone to another and see if the issue persists. Or open that microSD up in a hex editor and look at the partition table directly to see what's actually in there.

Easiest way to fix is probably to reformat in TWRP - maybe switch file system to ext4 first and then back to fat to make sure everything gets overwritten, UUID gets regenerated.

---------- Post added at 08:52 ---------- Previous post was at 08:38 ----------

Can't say since I'm not using gapps but the app shows up on third-party play store interfaces like Yalp Store even while rooted, so if necessary you can always use those.
[Galaxy S II Android Development] Draky50110:
Enven un-rooted I can't see it in PlayStore so I'll see elsewhere, maybe APK on Internet :D

By the way can't see the difference between https://play.google.com/store/apps/details?id=com.netflix.mediaclient and https://play.google.com/store/apps/details?id=com.netflix.ninja
[Galaxy S II Android Development] rINanDO:
Thanx for the detailed info!

I checked your 120fps video. It's metadata specifies 120fps which is cool, but if i check the recorded frames it is actually 30fps. That's too bad.

I also tried your instructions in A better camera app. I see the dark scene brighten which. However when I start recording my Phone reboots.

The main reason why things is so hard to get it all running in LOS 14.1 is because of closed Samsung sources and changes in Android 4.3 - 7.1.2.
[Galaxy S II Android Development] gm0:
Yep, that's 30 fps for sure. Plus it's not full resolution, not sure if that's on purpose but the phone's rear camera can record in 1080p.

Using his instructions with OpenCamera works flawlessly btw.
[Galaxy S II Android Development] Sub_Zero2:
A titaniumbackup restore should work as well
[Galaxy S II Android Development] nageswarswain:
Strange:::: I am not getting network..Searched here but no one mentioned about it....

Edit: I think it's a hardware problem. Because it's not got solved by flashing stock official rom. I can only use mobile data but while try to call the return message is no network
[Galaxy S II Android Development] Nobby1960:
A repartition has always been enough. I never had to reformat the SD card to have a correct label name again.
[Galaxy S II Android Development] Boolian:
Thanks for that. Problem lies not with the microSD card FAT then. :good:
[Galaxy S II Android Development] JaLoou:
If I make this trick then my i9100 does not reboot. But I can do it only on Samsung's last official firmware Android 4.1.2. And I can record a dark scene significantly bright at 10 or 15 fps. Thus, there is an yet one useful feature of this trick: it is a small video file size.

Please make this trick available with LOS 14.1 also. It will be useful for many i9100 users.

I can be the tester of it cause I need video recordings at a dark often.

I do not know how I can help now but I have the app, which upgrades an outdated camera firmware on i9100. I attached it to the message. May it will be useful for you.
[Galaxy S II Android Development] JaLoou:
This trick is not useful with the Open Camera app. It works properly only with the A Better Camera app.

I was unable to check an actual frame rate of the video due to I do not have a modern PC. Sorry for it. And thanks for your help to know the actual frame rate there.
[Galaxy S II Android Development] toy_story:
Problem TWRP 3.1.1-0 for i9100, return to previous!

Hi, TWRP 3.1.1-0 does not work for i9100!

It's good that you download LineageOS!

You need to return TWRP 3.1.0-0, install Official TWRP App , follow the application instructions and everything will be fine.

Then install any version of ROM.

Good luck ...
[Galaxy S II Android Development] JaLoou:
It is trouble for a noob like me to submit bugs there.
[Galaxy S II Android Development] JaLoou:
The latest version of Lineage OS for i9100 drains more a battery and heats the device.

The other known bugs still is not fixed.
[Galaxy S II Android Development] boambee09745:
I had the same terrible battery experience with lineage-14.1-20170712-nightly-i9100-signed.zip. Not even 2 hours usage, main cause Lineage OS followed by Chrome, Screen etc.

Reverted to lineage-14.1-20170621-nightly-i9100-signed.zip and battery life excellent, no drain overnight and almost full day use so far.
[Galaxy S II Android Development] gianni84r:
Hello,<br />

every time I make a call I lose the mobile connection. it's normal?

Inviato dal mio GT-I9100 utilizzando Tapatalk
[Galaxy S II Android Development] gm0:
Once you're logged in (top right corner) there will be a highlighted button "Create" at the top, which brings up a form that on weekends defaults to weekly/nightly bug reporting and should be self-explanatory. Make sure to enter all the information it asks for including a logcat or your report will be rejected.

You can also submit regression bugs any day of the week but those are only for things that did work correctly in a previous weekly build but then a newer build introduced a bug that broke them.
[Galaxy S II Android Development] olejonbj:
Check my solution over here :)

Thank God for being a Linux expert :P

Your solution does not work as LineageOS does not come with root enabled by default (and I don't want it as some banking apps won't accept it), one have to flash a ZIP for that. So same problem. But now I should be able to flash whatever.
[Galaxy S II Android Development] gm0:
The easier way would have been to simply flash the working TWRP version since you'll want to do that, anyway. That TWRP app is in no way required for that (or anything).
[Galaxy S II Android Development] olejonbj:
No. Read the post. Using TWRP 3.1.1 it is not possible to flash anything from TWRP itself (no ZIPs no IMGs), because it does not detect any filesystems, even after mounting them, but after mounting them manually the LineageOS ZIP script flashes with success. Trying to flash the TWRP .img file does NOT work from TWRP 3.1.1 itself since it does not list any partitions below in the flash image section, and fails.

EDIT: Now I have successfully downgraded to 3.1.0 after updating LineageOS, enabling root the LineageOS-way, and then using the Android app to flash it from Android itself. From TWRP it was impossible.
[Galaxy S II Android Development] toy_story:
You are wrong, it works well.

You have LOS configured - installed applications, there is root and TWRP 3.1.0-0.

You upgraded to TWRP 3.1.1-0 and this solution will help you, root you already have.

And if you installed TWRP 3.1.1-0 on the first installation of LOS, then what prevents you from installing TWRP v2.8.7.0 for Odin.
[Galaxy S II Android Development] gm0:
Eh, don't try to intentionally misunderstand me? You could have flashed TWRP via adb the Linux expert way, or you could just have followed the official installation instructions (download mode).
[Galaxy S II Android Development] gm0:
Look, we're far off-topic, this should have been in the TWRP support thread to begin with. You're wrong, let's leave it at that. And if you want to learn something learn how to copy a partition image under Linux (edit to be more constructive: partition images are just files, you can mount them like you did, but you can also write to them, so e.g. an adb push will do the job).
[Galaxy S II Android Development] MattP79:
I'm not seeing these issues on the 12th July nightly. The difference may be that my phone is rarely used (work text messages and the rare phone call) and lost 25% over 13 hours overnight according to the inbuilt battery stats. Considering how old, and well used the battery was in the past, this isn't surprising. The apps I have installed are BBC Radio iPlayer and Chrome with the micro Gapps package - so not too much going on in the background.
[Galaxy S II Android Development] the.gangster:
As we were off-topic here anyway:

a big "Happy Birthday" to our co-maintainer [MENTION=6159291]Lysergic Acid[/MENTION] (as long as it still is in his Brazilian TimeZone...) :)
[Galaxy S II Android Development] MattP79:
Fwiw - 32% battery remaining with minimal use after 39 hours - 12 July 2017 Nightly.
[Galaxy S II Android Development] linusdan:
2 hours of heavy battery usage with the latest build. What happened with at 4:30H of duration?

Every minute, 3% or 4% of the load goes away.

I use my smartphone to listen to music and view Instagram posts. Only that. Nothing else.

Build 20170719.
[Galaxy S II Android Development] Ac.3:
wanna flash a custom recovery using heimdall on linux but this phone isnt being detected but others are... also tried using TWRP official app to flash but it doesnt work, Mobile Odin not working too...

any alternative solutions?
[Galaxy S II Android Development] JaLoou:
It is probably an alluring lie.

The batteries drained on last LOS even without using i9100. I had attached the screenshot.
[Galaxy S II Android Development] asulthebest:
Can someone upload the 'lineage-14.1-20170621-nightly-i9100-signed.zip' here because i can't download from website. Thanks
[Galaxy S II Android Development] boambee09745:
Recent zips here: https://download.lineageos.org/i9100
[Galaxy S II Android Development] Nobby1960:
Hmm - I can't confirm this. This little drain of 4% on my screenshots is fully normal if my phone runs idle over 6 hours with latest LOS Nougat build. WiFi on in deep sleep, a few WhatsApp messages, div. wakelocks etc. Nougat naturally consumes more battery than Jelly Bean. No problem today for modern phones with high capacity batteries. The small default battery from our S2 with only 1650 mAh wasn't built for long lifetimes with a current OS.
[Galaxy S II Android Development] asulthebest:
I already tried to download from official website, but '21' version can't download. If someone could help me to upload here this version. Thanks
[Galaxy S II Android Development] gm0:
The website has a bug, it displays the past 6 builds but the download servers only hold the past 4 builds.

Why do you want that old build though? Other than it being the last build with working built-in BLN (and as far as I understand that can be remedied by using the BLN mod instead) I don't remember anything particular about that build?

---------- Post added at 16:20 ---------- Previous post was at 16:16 ----------

I assume you're on a higher capacity battery? I'm still on the original one the phone came with, and while I still have about 2 days battery life with moderate usage, I never reached more than 3 days as shown in your screenshot.

One thing I did notice in recent weeks/months is increased battery usage with WiFi compared to mobile data, when it should be (and used to be) the opposite. Can't say for sure that it's the OS, though, could be any number of reasons that I didn't explore.
[Galaxy S II Android Development] asulthebest:
I read here that the 21 build has great battery and is fast
[Galaxy S II Android Development] linusdan:
What you can do is create a virtual machine with windows 10, install the VirtualBox and Samsung drivers and make the CWM flash with Odin3. Then you install TWRP in zip available here on XDA. After that, be happy!