yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] the.gangster:
LOL, well, I hope so. (But don't count your chickens before they are hatched.)

Then you haven't read enough yet. Although it is true, that the preload partition was not used by any non-stock ROM (except for DorimanX kernels dual boot feature), nevertheless most (if not all) kernels for the S2 will try to mount it. If it's not formatted at all they stuck at that point.

As noone usually ever touches that partition, this is only likely to happen if users got guided to use PIT files to change their partition layout AND if that PIT file also changes that partition's position. Otherwise the filesystem of it will/would be preserved (and so wouldn't lead to that problem).

Read more carefully. I wrote you should follow my link to find the modified one. That post does not only contain the current 3.1.0-0 (which is the unmodified official one). At the end it also links to the previous versions: 3.0.2-1 (official) as well as 3.0.2-1 with preload-support. So you would have litterally better read that post to its end.

Yes. But there is a third option:

As you have installed everything already, you could simply use

lanchon-repit-20170115-preload=+wipe-i9100.zip

to format your existing preload partition and see if that fixes your boot problems already. That's similar to option 1.

The partition layout of an unmodified device (=the original Samsung partition layout). In this case, especially regarding the preload's configuration.

preload partition is only called preload partition because its mount point is /preload. But in fact its partition name is mmcblk0p12 and its label is 'HIDDEN'. So p12 was referring to that partition in the emmc area (mmcblk0).

Hopefully I explained that already in detail above.

As explained, this is depending on how users are guided to modify partitions. I am not even using odin/heimdal at all any more to convert from stock Samsung ROM to custom ROM. Eliminating the need to describe things like: driver installations on PCs, ...how to circumvent formatting problems after using PIT files, ...how to remove yellow triangles.

But yes: many descriptions for repitting with PIT files miss to inform users to ensure the preload partition is properly formatted again if changed and some even don't tell users to format internal storage. But the latter does only lead to some "corrupt filesystem"-messages which is not as severe as leaving a device unable to boot.

Hopefully this was really your issue. First it sounded unlikely, due to you describe coming from stock ROM and using the pit with 512mb preload. But after you tried all the other more likely solutions already, it finally sounded very likely to be your problem.

EDIT: [MENTION=8075440]gm0[/MENTION] meanwhile also described my thoughts regarding partition layout very well, while I was still typing. Thx!
[Galaxy S II Android Development] toy_story:
Hello, I gave you "hope and autocracy" in your post, but you spit on it and sing like "Donkikhot", fight windmills, you do not listen to anyone. How are you

"Trolls", I will not be more than you write, because it is useless. I'm so as you see in handwriting, but why do you need this ...

Do not write that you do not have money for another phone! You just seem to be fun above us!
[Galaxy S II Android Development] toy_story:
Many tend to travel and do not stop there, many in constant search. That they had the freedom to intermix on android from 2 to 8.1, you need to have a section of 512mb preload.
[Galaxy S II Android Development] gm0:
Or a fourth option: TWRP does indeed hide p12 in the UI as you said but I just checked and you can access it from the command line just fine. So booting into TWRP and formatting the partition manually via terminal or adb shell will do the job as well:

mke2fs /dev/block/mmcblk0p12

Just to put that out there. Always good to know the direct way to do things rather than having to rely on additional tools to do it for you.
[Galaxy S II Android Development] ale5000:
Just an idea, but why not remove this useless automounting from kernel completely?
[Galaxy S II Android Development] gm0:
I guess the idea was that since the partition exists by default it should be accessible to the user for them to use that space. However, since it gets mounted under the root folder rather than in user land (i.e. you need to be rooted to use it) I'm not sure how much that was thought through. A rooted "power" user can still mount the partition manually if they want to.

Frankly, when everybody needed to repartition since CM13 or LOS14 at the latest the decision should have been made to just drop that partition entirely.
[Galaxy S II Android Development] dumdidum123:
My device somehow managed it, to rename sdcard0 to M-Ni^YM-6M-6^OM-kQ4M-AM-8.

I am really not sure, how to revert this step and I am not even sure when this happend. Any idea? I know it is just a cosmetic thing, but I would like to rename it back to sdcard0

Edit: Nevermind. Mounting it via TWRP as a FAT32 Drive gave me the ability to give it a name, using my Laptop. LOS is also using this name from now on. (Before, it was just shown without a name, when connected to Windows)
[Galaxy S II Android Development] gm0:
Yeah, we've seen this before. The cause is basically a messed up volume label descriptor in the FAT BPB. By default none is set at all for internal storage, so the pre-configured sdcard0 label is used. So, as you found out, overwriting the faulty label with a valid one is one way to fix it.
[Galaxy S II Android Development] mldmld1968:
Hi all,

I want to send big THANKS to the gansters and to gm0 for their precious help. Now my Samsung Galaxy S2 runs Lineage OS 14.1 !!!! :):):):)

To fix, under TWRP I formated all the partition, except the external Sdcard, then I entered

mke2fs /dev/block/mmcblk0p12

And thanks to install.zip option, I installed Linesage OS 14.1, gapps and su !

The first boot lasted 10 minutes, and I was able to access again to my phone !!!

I'm very happy because the fix explains what was the real issue. Not the apply a blind recipe without understanding what happens and pray !

Just for information :

cat /proc/partitions returns the partitions list, and all have major = 179, except mmcblk0p12 where major is 259.

And ls -l /dev/block/platform/dw_mmc/by-name shows :

HIDDEN -> /dev/block/mmcblk0p12

I see nowhere /preload

Yes, I agree too. Or at least the simple command of gm0 could be suggested in the lineagos 14.1 install page for i9100 in case of boot loop. Repit is a great tool, but it's more simpler.

The best could be to have a log of the boot somewhere in the phone.

I made some tests, the only strange thing is I get the same issue as LazyGuy1, the torchlight is buzzing when it is on, and the same when I take a snap with the rear camera. Not a big issue anyway.

All the best
[Galaxy S II Android Development] gm0:
First off, welcome to the fold of LineageOS users. May your I9100 never die! ;)

And I see you've been doing some more research. What you still lack is an understanding of how the file system works. HIDDEN is the label for the partition as per the storage media's partition table (the .pit file you flashed to it). /preload is an (arbitrary) mount point, i.e. a logical location where that partition's file system is being made accessible to the system. The same is possible under Windows, although there partitions are mounted under drive letters by default.

If you want to play around further, check out the df command as well as mount itself. If you're really interested, install a desktop Linux distro into a virtual machine (Android is basically a Linux distro) on your PC and take it from there. But we're definitely leaving the scope of this thread here so I'll leave it at that.
[Galaxy S II Android Development] mldmld1968:
Hi,

Thanks for all theses informations.

My S2 will live as long as I can find batteries. I changed it 6 months ago and I received a new battery. But built ... in 09.2014.

I'm very impressed by my new S2 under Lineage OS 14.1 ! The permissions policies are very nice. The battery last a day now.

No issue with wifi, sim or bluetooth.

After a few days of use I encountered 3 issues :

- The back camera works but it makes a noise each time I select it. Already mentionned here. I'm afraid the camera focus can't bear that very long. Is there a known fix ?

- The mic do not work with skype, but works perfectly during phone call. I read it's a common problem of low sensitivy setting that can be fixed in a setting in mixer_paths.xml. One can read many way to fix that. According to you, what is the best way to fix it ?

- I'm unable to access a joined document in a email using the email client embedded in LineageOS. I'm sure there is a obvious way to access them, but I'm still unable to find where. I would like to avoid to install gmail or yahoo client on my phone.

Best regards
[Galaxy S II Android Development] gm0:
I'm still on the original battery. It's slowly starting to give out but I'm still at a day and a half at least.

Make sure you actually enabled microphone permissions for skype. No problem here, works fine out of the box. I never had to edit any files. You should not have to.

Can't help you with your other two problems, either. I don't have the lens issue

- it might just be wear, you also had noise with the flashlight you said. And I never used the built-in email client.
[Galaxy S II Android Development] LazyGuy1:
I researched that "buzzing noise" behavior and found out that when our S2 does that the camera lens is going to die very soon and recommends us a replacement. I can say it's definitely not worth it (for me at least, shaking the phone a little bit fixes that buzzing noise till the next camera/torch restart/reenabling.
[Galaxy S II Android Development] mldmld1968:
I found that in the log what's wrong but don't know to fix :

04-08 15:39:40.088 2287 2326 W PackageManager: Permission com.android.email.permission.READ_ATTACHMENT from package com.android.email in an unknown group android.permission-group.MESSAGES

04-08 15:39:40.751 2287 2327 W PackageParser: Ignoring duplicate uses-permissions/uses-permissions-sdk-m: android.permission.READ_EXTERNAL_STORAGE in package: com.adobe.reader at: Binary XML file line #60

There is no external sdcard in my phone.
[Galaxy S II Android Development] gm0:
What file system did you end up using for sdcard0? The lazy solution is to go back to vfat (which has no access control). Otherwise I'd probably suggest a clean install (strange since you basically just did one) but it's easier than trying to fix all apps manually. I don't know why permissions have not been set correctly.

PS: This is assuming that you did actually give the respective permissions under Settings->Apps and it didn't work.
[Galaxy S II Android Development] Gramos Qevani:
Gapps

http://opengapps.org/
[Galaxy S II Android Development] robby2107:
Hello together,

i tried to connect der i9100 with LOS 14.1 via androidAuto to my Car Entertaiment (Skoda Amundsen MIB2).

The App androidAuto works fine offline (without connection to the car). But if i connect the USB-Cable to the car, the screen on the phone shows me that´s my phone isn´t compatible.

Some ideas to solve the problem?

greetings

Robby
[Galaxy S II Android Development] mldmld1968:
Hi

I fixed the email issue by using another email client. I choose bluemail. It worth to be used.

I fixed the camera issue by using another app camera. I choose the one from Olympus. There is still a quick buzz at startup, but after, no more.

Finaly, Firefox is able to store on download directory.

I notice Documents directory cannot be accessed with x-plorer or by terminal+su, but I did not detect any issue because of that

I prefer to not reinstall. The better may be the enemy of the good.

Thanks !

Best regards
[Galaxy S II Android Development] LazyGuy1:
Shake your device when it is buzzing. It helps me a lot. Not using the S2 as daily driver, but for those who are using it as a DD, giving suggestions is always a nice help :)
[Galaxy S II Android Development] antarax23:
Hello everyone any ways to root this rom after installation? I tried to flash magisk v16 but it failed bunch of times and im out of solution right now
[Galaxy S II Android Development] LazyGuy1:
Magisk is not working on our device. Use the su addon here:

download.lineageos.org/extras (pick arm 14.1)
[Galaxy S II Android Development] antarax23:
I have root finally. Thanks a lot mate
[Galaxy S II Android Development] LazyGuy1:
No problem :) There is a button for thanking! ?
[Galaxy S II Android Development] the.gangster:
[MENTION=6744231]antarax23[/MENTION]

...And there is an Opening Post for reading at the very least before posting questions that are already answered in its "IMPORTANT INFORMATION"-section.

Someone writing 3 posts in ~3 years should have the time for such basics... or should at least consider this as valuable hint instead of an insultation. :p
[Galaxy S II Android Development] nospamboz:
It may be related to the USB connection mode. I think there are three: charge-only (the most secure), transfer files (MTP), and transfer photos (PTP). You may need to switch modes to get it to work. With the USB attached, swipe down to get notifications, tap the USB notification, and select your mode.

I think charge-only is the normal default, but that can be changed in developer options. Again charge-only is more secure, because the file transfers go both ways, and you don't want someone infecting your phone as if it were a USB key drive. Sure, the phone may not be affected, but the next computer you attach to may be. Leave the default alone, and get used to swipe+select.
[Galaxy S II Android Development] robby2107:
Hello nospamboz,

this morning I tried again with another USB cable and all 3 connection methods. No improvement.

What I know so far is that I am not the only one with the problem and that it used to work fine with CM12.

What have I done so far:

- USB mode changed (Charge, USB for data, Pictures)

- all rights granted for Android car

- USB debugging enabled

- 3 different USB cables tested (all USB certified) with different lengths

- another smartphone to eliminate vehicle errors

- Restart, other Nightly ...

The smartphone works on the computer via USB without any problems, so the error cannot be due to defective hardware on the phone.

Is there anyone who successfully connects AndroidAuto to the car and the i9100 (or another phone) with LineageOS 14.1. who might also be able to support this?

Thank you very much!

greetings

robby

Edit: I have just been able to connect to my radio via AndroidAuto with a colleague's S6 (TouchWiz). So I am absolutely sure that my car radio and the USB cable are okay and it must be on the i9100.

The cross-check in his car (Skoda Superb 2017) showed that my smartphone does not establish a connection.

A positive side effect: We discovered a defective USB cable in his car and now his S6 finally works in his car with AndroidAuto.

At least I could help him. )
[Galaxy S II Android Development] cybero2912:
try this:

https://www.google.de/amp/s/www.xda...fix-device-not-certified-by-google-error/amp/
[Galaxy S II Android Development] robby2107:
Thanks for that tip, cybero.

But unfortunately, it didn't help. The GApps all work perfectly and the AndroidAuto app also starts without any problems. Only if I connect the USB cable it appears with AndroidAuto that my device is incompatible.
[Galaxy S II Android Development] cybero2912:
have you tried another version of this app?
[Galaxy S II Android Development] playitlouder:
I am running 14.1 2018-04-10 and have problems with the mic volume in Whatsapp.

It's lower than in other apps and I guess they do some noise filtering in Whatsapp Calls (to minimize bandwith usage) and since the microphone volume is to low I do have to speak louder than usual to even be heard at all.

Whatsapp Voice Notes work, but are more quiet than on other phones.

Is there a way to tweak mixer paths or something to attenuate the microphone input a little?
[Galaxy S II Android Development] Teekanne3000:
Have tested update from 10.04., no change.

Greetings

Teekanne
[Galaxy S II Android Development] toshibashi:
Where's the complete installation guide again?

Hi,

I'd like to do a fresh install on my second i9100. Where's the TWRP - repit - Lineage-ROM - AddonSU - OpenGAPPS installation guide again?

Thanks,

Toshibashi
[Galaxy S II Android Development] robby2107:
Yes, i tried 3 different versions. One from the beginning of 2017, the second from the middle of 2017 and the last version is the newest version.

:(

Gesendet von meinem GT-I9100 mit Tapatalk
[Galaxy S II Android Development] gm0:
I don't know about volume but after a clean LOS install this weekend I actually have that WhatsApp issue of the voice caller not hearing you at all (no matter the volume) that the conversation you are quoting was about.

Going back to my backup it works again. Same LOS version, so it's a settings/permissions issue somewhere. Haven't looked into it further yet.
[Galaxy S II Android Development] Justice4I:
Have this rom a stable version ?
[Galaxy S II Android Development] cristihan:
Take a look at this page:

https://androidfilehost.com/?w=files&flid=231877 . All of them are stable. I use AOKP-2017-10-26_0507...it's almost pefect :)

crDroid with february security patch: https://xdaforums.com/showpost.php?p=75662300&postcount=56
[Galaxy S II Android Development] Justice4I:
ı really really thank you for reply :) I have one more question only.Now ı am using lineage kitkat rom on my s2.I decided to flash this rom but ı don't know how to repartition.Will you help me about it :/
[Galaxy S II Android Development] cristihan:
Read this : https://xdaforums.com/android/software-hacking/tool-lanchon-repit-data-sparing-t3358036

this: https://xdaforums.com/galaxy-s2/help/guide-tutorial-samsung-galaxy-s2-i9100-t3538601

and this: https://github.com/Lanchon/REPIT.

I used this file for repartition : lanchon-prefered-djibe-repit-20170115-system=1G+wipe-data=max+wipe+f2fs-sdcard=2G+wipe+ext4-preload=min+wipe-i9100.zip

You will fiind this zip file in tutorials.

Read all tutorials before proceeding !!

In case that something goes wrong attached you have stock PIT for ODIN flash. Good luck ! :)
[Galaxy S II Android Development] Justice4I:
I don't know how can ı thank you,I will write again when ı done it :)
[Galaxy S II Android Development] BatyuS:
Friends WhatsApp is also the voice of the headset with the voice of the other party is coming, but my voice does not go have you problem?
[Galaxy S II Android Development] cristihan:
I had the same problem with the latest update from whatsapp with aokp_i9100_nougat_unofficial_2018-04-09_0416 ROM . Install an older version of whatsapp from the apkmirror website and you will fix the problem. :)
[Galaxy S II Android Development] nospamboz:
Goodbye i9100. Hello herolte.

Well, that didn't take long.

It wasn't AT&T but T-Mobile that killed 3G. Not everywhere, and not all 3G, but the i9100-compatible 3G in the town I'm about to move to (for work) is gone, a fact I discovered on my first trip there looking at apartments.

https://www.howardforums.com/showthread.php/1898916-T-Mobile-Replacing-1900-Mhz-3G-With-LTE-in-31-Markets

So with a heavy heart, I'm "retiring" my i9100. After much research, I decided to replace it with the Galaxy S7 SM-G930F, an "international" model like the i9100, with an official LineageOS release (herolte). The S7 is the last Galaxy S with a headphone jack and microUSB connector, so it simply "slots in" to everying I used with my i9100. I got a good used price for it (just over US$300), no blemishes or scratches on the one I got.

(I do miss the FM radio, though.)

Titanium Backup made the migration very straightforward. I'm still getting used to the bigger size and heavier weight, but at least it's not a behemoth like most modern phones. Still that great screen, though, with blacks so black. And LTE and the bigger battery are convenient, though I may need to eventually switch to a TouchWiz-based ROM (uggh) to get VoLTE and wifi-calling. For now, LineageOS suits me fine.

Anyway, if anyone else is in a similar situation, my experience is that the G930F is a great upgrade from the i9100, if your carrier "obsoletes" your i9100 from under you.
[Galaxy S II Android Development] Acid0057:
Running into the same issues with a work issued phone in Canada too. Provider we use is shutting down 3g. I don't get a choice in my new phone though [emoji24]
[Galaxy S II Android Development] treysis:
I changed both (bat & usb circuit), problem remains. I thought about using it as a NAS server.
[Galaxy S II Android Development] laptopu:
Yes if nothing else you can use old handsets as servers. I use an ancient galaxy young as a VPN server.
[Galaxy S II Android Development] treysis:
Ok, enough OT here. Thanks especially [MENTION=6724217]Boolian[/MENTION] for pointing out this other thread about S2. I had already read about the possibly broken capacitor in the past and will head over to this thread now.
[Galaxy S II Android Development] Nobby1960:
You must check more Nougat ROMs on LineageOS base. My S2 is faster and smooter than with the old stock ROMs. I can compare directly here. 4.0.4 - uah, slowly. 4.1.2 - no, thanks - horrible. If you want a real rocket S2 with a minimum on battery consumption, try to flash the Tesla ROM (Lollipop) - see link in my signature.
[Galaxy S II Android Development] Mirajoo7:
I don't think its slower than stock roms

---------- Post added at 04:31 PM ---------- Previous post was at 04:24 PM ----------

waiting for the nightly[emoji102]
[Galaxy S II Android Development] shkedov:
+1 to [MENTION=7513127]Nobby1960[/MENTION], I'm very pleased with the newer roms, especially this one!
[Galaxy S II Android Development] nunosilva10:
can someone upload a nightly?

can't download from the official website
[Galaxy S II Android Development] gm0:
Don't expect one before tomorrow, today's builds had issues and were paused.
[Galaxy S II Android Development] laptopu:
https://status.lineageos.org/ build server is paused, reckon we'll be waiting until tomorrow night now.
[Galaxy S II Android Development] the.gangster:
[MENTION=3203083]nunosilva10[/MENTION]

Most likely in just a few hours you'll find a brand new version on them lineageos download servers. So if you don't have the time to search this thread, simply wait and be the first to install it.
[Galaxy S II Android Development] nunosilva10:
I'll wait then.

Thanks :)
[Galaxy S II Android Development] cybero2912:
if you can't wait get latest ROM from here
[Galaxy S II Android Development] waliuxd:
thanks man , downloading the last (20170218)
[Galaxy S II Android Development] laptopu:
That link 2 posts up is for unofficial not official builds meaning if you flash any of them, you'll then have to wait for an experimental nightly to dirty flash before another dirty official flash to get you onto the nightles unless you do a totally clean install.

I'd just wait until the official nightly is out, much easier and hopefully you'll only wait for a few hours.
[Galaxy S II Android Development] bepcan:
You mean official nightly downloadable from lineageos download area?
[Galaxy S II Android Development] gm0:
Yes, an official build should be available in about half a day, it's preferable that you wait for that.
[Galaxy S II Android Development] treysis:
If I send myself an APK via bluetooth, and then want to open it from the notification popup, I see an error message:

"Bluetooth Share has stopped."

Doesn't happen with other files (only tried zip, where it complained, that there's no app for this filetype). I also observed this in unofficial builds.

Anyone who can confirm this bug?
[Galaxy S II Android Development] the.gangster:
[MENTION=5926322]treysis[/MENTION]

Why do you consider this to be a bug? I'd consider this a feature.

It's for your and everybody else's safety. You don't send executables by email either, do you?

Only defined mime-types are allowed for filetransfer by Bluetooth.

Rename the apk to jpg or another allowed extension (and vice versa on the target) to work around this protection.

Just a quick google search, but should be comparable to this for our phone.
[Galaxy S II Android Development] Mirajoo7:
change log available? for 20 th nightly?