yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] osm0sis:
[MENTION=2222292]rINanDO[/MENTION] (or anyone who is familiar with the build process for the i9100) can you help me track down the $(MKBOOTIMG) for i9100?

I see it referenced here: https://github.com/LineageOS/android_device_samsung_galaxys2-common/blob/cm-14.1/shbootimg.mk

But I can't find where it's defined in the BoardConfigs and so can't seem to find the actual binary. I'd like to support devices like this in my Android Image Kitchen and AnyKernel2 projects if it's something I can cross-compile.
[Galaxy S II Android Development] Sub_Zero2:
Is this what you're looking for?

https://github.com/LineageOS/android_system_core/blob/cm-14.1/mkbootimg/Android.mk

Might be, althought I'm not 100% sure.
[Galaxy S II Android Development] osm0sis:
Nope. I was looking for what sets $(MKBOOTIMG). Anyway, I've been informed by the great [MENTION=3208754]codeworkx[/MENTION] that all this is rather misleading since none of it is actually used, and instead the "boot.img" in the zip is generated entirely from the kernel Makefile.

Furthermore, it's a Linux standard format and has the ramdisk baked in, and due to some start/endpoints compiled into the kernel code it makes it near impossible to support unpacking/repacking on-the-fly AnyKernel2 style.

There are some options on a desktop Linux box though: https://xdaforums.com/showthread.php?p=37381076#post37381076

Anyway, I'll unsubscribe here now, @ mention me if you need me. :good:
[Galaxy S II Android Development] kai_15:
please help me on how to remove # icon in status bar, i am rooted.. thanks
[Galaxy S II Android Development] toy_story:
Script remove the superuser indicator "#" !
[Galaxy S II Android Development] MauroRTR:
Swipe the app that is using root from the recent task list.
[Galaxy S II Android Development] kai_15:
--> thank you sir.. gobless

---------- Post added at 06:21 AM ---------- Previous post was at 05:50 AM ----------

guys any fix for mtp has stopped?
[Galaxy S II Android Development] toy_story:
To get rid of it, go to Settings-> Applications-> Show system processes-> MTP-host and disable it.
[Galaxy S II Android Development] kai_15:
--> thanks again sir i a new in lineage os since i want to use my samsung S2 :salute:
[Galaxy S II Android Development] kai_15:
hi again guys i notice right now that even if my phone is sleep and i receive a message the menu and back key is blinking, how to remove that blinking?
[Galaxy S II Android Development] MauroRTR:
Go to Notifications settings and tap the configuration icon, turn off light notification.
[Galaxy S II Android Development] MagMerlin:
Hello. Someone can tell me if in last builds is solved the audio mic issue in VOIP (Skype, WhatsApp mic not working but working in normal phone). Or some tech/Dev explain exact issue and why it working in Los 15.1 less developed?
[Galaxy S II Android Development] kai_15:
--> thank you sir and one last question sir in notification toggle is there a option for example when i turn on wifi, data, bluetooth instead showing their setting they will autically on and off when i press them?
[Galaxy S II Android Development] robby2107:
Hello, everybody,

can anyone tell me if rSAP on the S2 works with the official LineageOS?

I was able to connect the S2 to my new car via Bluetooth, but I didn't notice any indication of rSAP.

Greetings and thank you!
[Galaxy S II Android Development] the.gangster:
Hello robby2107,

not natively.

If you want to add remote SIM access profile to your S2 you (still) need to buy the Bluetooth SIM Access Profile App. It works for me and there is a trial version as well to check compatibility with your car.

Its developer recently posted here that he'd added code to our repository already that needs testing/review. So maybe it might change one day if that code would get merged.

I think it's this one.
[Galaxy S II Android Development] robby2107:
Thank you very much for the quick response.

I will test the app and see what changes are made to the normal Bluetooth protocol. However, I do not yet fully see the advantage of rSAP over the normal Bluetooth protocol.

Another question:

I tried connecting to the car via AndroidAuto, but I keep getting error messages ("GooglePlayService faulty" or "Your device is not supported"). Sometimes the app "AndroidAuto" also shows me a connection, but neither the radio (Skoda Amundsen MIB2) nor the phone shows a connection. Very mysterious! :eek:

I hope someone has an idea.

Additional question: Is it possible to hide the ROOT from certain apps? Magisk seems to have this option, but LineageOS is rooted differently in the I9100. Right?

Many thanks and greetings

robby
[Galaxy S II Android Development] hasantekeoglu:
My s2 lag then the music player, youtube, instagram videos does not work ???
[Galaxy S II Android Development] PaveelOS:
Gapps does not want to install. Why? Something I'm doing wrong?
[Galaxy S II Android Development] guest4711:
Did you adjust the size of your system partition (1 G)? Which g-apps did you try (pico should be ok)?
[Galaxy S II Android Development] kai_15:
hi guys any guide on how to update the rom without losing my apps and data, i downloaded the update thru lineage software ota update in settings. thanks
[Galaxy S II Android Development] PaveelOS:
Yes, I have adapted the size of the partition has 1G. Gapps I am trying to install https://download.lineageos.org/i9100

I installed Pico, but no changes. All the time there is the same information when trying to install gapps, no matter what version.
[Galaxy S II Android Development] rsap:
Sorry, don't check XDA so often...

No more need to install my rSAP app and/or installer :o

It's not so easy to get the code integrated into LineageOS, and I understand it. It's my first code submission and the maintainer has no way to test it.
[Galaxy S II Android Development] infinion:
20180322 build still whatsapp cannot be heard by the other caller problem
[Galaxy S II Android Development] gm0:
Bug reports belong on jira. But since I never had such a problem with WhatsApp maybe try a clean install.
[Galaxy S II Android Development] infinion:
clean install

on last 13.1 no problem ,on 15.1 slow sound...
[Galaxy S II Android Development] rINanDO:
I have submitted your commit. I totally forgot about it. If there are problems related to this, I will revert the commit.
[Galaxy S II Android Development] gm0:
This thread is about LOS 14.1, where I have no issues with WhatsApp.

Oreo issues you can discuss here: https://xdaforums.com/galaxy-s2/development-derivatives/rom-lineageos-15-0-t3674567 - issues are expected with that build.
[Galaxy S II Android Development] Saftpresse99:
Hi,

i have a problem with the amazon app store apk (latest version) from here: https://www.amazon.de/androidapp. I can install the app and enter my credentials and the app runs well, but if i open the app again the app closes immediately. I touch the icon, the startscreen appears but then the app closes. The only thing which helps is to clear app data in settings. I created a logcat and found a exception:

03-29 15:23:26.366 8399 8514 E AndroidRuntime: FATAL EXCEPTION: IntentService[com.amazon.android.service.ScheduleAlarmsService]
03-29 15:23:26.366 8399 8514 E AndroidRuntime: Process: com.amazon.venezia, PID: 8399
03-29 15:23:26.366 8399 8514 E AndroidRuntime: java.lang.RuntimeException: Can't obtain account with name: AmazonSyncAccount-f2eaed2fc87f07ac3a4914bc442469d78a5da8a9dcd1538b9caae4e9bbecd643
03-29 15:23:26.366 8399 8514 E AndroidRuntime:	at com.amazon.android.csf.DummyAndroidAccountAccessor.getAccount(DummyAndroidAccountAccessor.java:104)
03-29 15:23:26.366 8399 8514 E AndroidRuntime:	at com.amazon.mas.client.locker.service.lockersync.LockerSyncAdapter.requestSync(LockerSyncAdapter.java:375)
03-29 15:23:26.366 8399 8514 E AndroidRuntime:	at com.amazon.mas.client.locker.service.lockersync.LockerSyncDecisionDelegate.initiateDigitalLockerSync(LockerSyncDecisionDelegate.java:594)
03-29 15:23:26.366 8399 8514 E AndroidRuntime:	at com.amazon.mas.client.locker.service.lockersync.LockerSyncDecisionDelegate.handleSyncIntent(LockerSyncDecisionDelegate.java:292)
03-29 15:23:26.366 8399 8514 E AndroidRuntime:	at com.amazon.mas.client.locker.service.lockersync.LockerSyncDecisionDelegate.handleSyncIntent(LockerSyncDecisionDelegate.java:252)
03-29 15:23:26.366 8399 8514 E AndroidRuntime:	at com.amazon.mas.client.locker.service.lockersync.LockerSyncDecisionDelegate.handleScheduleAlarms(LockerSyncDecisionDelegate.java:741)
03-29 15:23:26.366 8399 8514 E AndroidRuntime:	at com.amazon.mas.client.locker.service.lockersync.LockerSyncDecisionDelegate.handleScheduleAlarms(LockerSyncDecisionDelegate.java:925)
03-29 15:23:26.366 8399 8514 E AndroidRuntime:	at com.amazon.android.service.ScheduleAlarmsService.onHandleIntent(ScheduleAlarmsService.java:85)
03-29 15:23:26.366 8399 8514 E AndroidRuntime:	at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:68)
03-29 15:23:26.366 8399 8514 E AndroidRuntime:	at android.os.Handler.dispatchMessage(Handler.java:102)
03-29 15:23:26.366 8399 8514 E AndroidRuntime:	at android.os.Looper.loop(Looper.java:154)
03-29 15:23:26.366 8399 8514 E AndroidRuntime:	at android.os.HandlerThread.run(HandlerThread.java:61)
03-29 15:23:26.370 2388 2420 W ActivityManager: Force finishing activity com.amazon.venezia/.AppstoreReactNativeActivity

Anybody knows whats going on and can help me with a solution?

Thank you!
[Galaxy S II Android Development] rsap:
What happened?
[Galaxy S II Android Development] rINanDO:
Don't know.... I saw the revert commit in gerrit just now...
[Galaxy S II Android Development] toy_story:
Hi, on lineageOS 14.1 writes that there is no signal, although the signal is also quite good. On the firmware Android 4.1.2, everything is working fine, even on the CM 12, too, with the connection is normal.

What's the problem with LOS 14.1, why writes that there is no signal?
[Galaxy S II Android Development] gm0:
Sounds to me like you did everything right basically, including the repartitioning (last I checked it wasn't included in the wiki article, no). The only thing I was wondering was why you didn't reformat the internal storage /sdcard0 as well. After repartitioning you should write new file systems onto every partition.

The pit file you used sounds fine - you could have gone with just a 1 GB system partition and you don't need the 512 MB of preload except for the stock ROM, either, but there is nothing functionally wrong with the sizes you have gone with.

Your logs were created from within the recovery so that doesn't help that much. So I'm not really sure what's wrong but I would suggest you reformat every partition except external (and make sure TWRP is configured to actually do that and not just rm -rf them). At this point you can also consider whether you want to keep the default file systems. Personally I'm using F2FS for /cache, /data and Internal-Storage, for example. In case of doubt just stick with the defaults though, just wanted to make you aware of the option.

Anyway, then flash LOS again but only LOS itself this time and see if that boots. If it gets stuck on the boot logo again, try to pull the battery after a few minutes and then let it boot again. If that still doesn't help then connect your phone to your PC and see if you can grab an adb logcat while it's stuck at the logo.

If it did boot then you can go back and flash gapps and the su addon (if you really need them) and see if it still boots.
[Galaxy S II Android Development] mldmld1968:
Hi all,

Thank you.
[MENTION=357633]toy[/MENTION]-Story : AFAIU, your method uses Odin to install TWR. As TWR is already running on my phone do you think I may :

- boot to TWR recovery mode (volume up, screen button, power)

- use the installed TWR to install : kernel-Lanchon-20160406-i9100.zip

- reboot to recovery mode again

- use TWR again to install lineageOS 14.1 ?

[MENTION=8075440]gm0[/MENTION] :

- I changed partition type of cache data and sdcard0 (is it what you call internal storage ?) to F2FS

- format everything except external storage

- install LineageOS only through TWR.

I checked that TWR is not configured to rm -rf partition instead of formating it.

I remove the battery to try a second time to boot the device

It's still stuck on the animation... :(

I connected my phone to my PC, adb devices do not return any attached devices.

Is there a way to know what LineageOS is doing during this first boot ?

Thanks
[Galaxy S II Android Development] gm0:
This confused me. TWRP should call it Internal-Storage, and the recovery.log in your previous post indicated that it did. Maybe flash the official TWRP 3.1.0-0 again just in case https://twrp.me/devices/samsunggalaxys2i9100.html
[Galaxy S II Android Development] Nojevah:
From time to time I reinstall LineageOS hoping the BT will work with my Bose QC35 (for phoning) but it still doesn't work. :(

If one dev is interested in resolving this, I'm ready to take time for tests.
[Galaxy S II Android Development] mldmld1968:
I downloaded again TWR from the link you sent me, the file is identitcal with the one I used. I checked with fc /b file1 file 2. In fact I think I downloaded it from this site.

I check also the pit file, I checked with the one of the link of Toy_story. File are identicals.

This time, I did not confirm to install TWR App in the phone. Just to see what happens this way.

Could the kernel be the issue ?

This is the kernel from LineageOS.zip file.

---------- Post added at 04:59 PM ---------- Previous post was at 04:34 PM ----------

I look in a terminal in TWR :

The boot.txt file ends by

cpio : dev not created : newer or same age file exists

cpio : proc not created : newer or same age file exists

cpio : sys not created : newer or same age file exists

The fstab.smdk4210 shows , all partition are mounted with the ext4 parameter.

I also can see a supersu directory, but i did not install it with install.zip option of TWR :confused:
[Galaxy S II Android Development] LazyGuy1:
So guys, I installed LOS 14.1 on my S2 which I bought for 10€ a few hours ago and I have to say it rocks for an 7 year old device. The only thing I have found was its torchlight is buzzing when it is on, but else everything works. Thanks [MENTION=2222292]rINanDO[/MENTION] :)
[Galaxy S II Android Development] gm0:
Flashing LOS also flashes the kernel, so you're always getting that one, anyway. And the latest LOS build runs fine on my device.

That said, I still can't see anything from your description that would prevent a boot. How long are you actually waiting for the boot to complete. If it actually was 30 minutes that sounds exceptionally long but at this point I'd recommend to just let it sit there.

Another possibility is that either your download of LOS was corrupt or the file did not copy correctly on the sd card (or the sd card is bad).

none of these are a problem. you are looking at TWRP's ramdisk. Do not install supersu from within TWRP, it's not compatible with LOS (the /supersu folder on the TWRP ramdisk is irrelevant)
[Galaxy S II Android Development] LazyGuy1:
Do you guys know why the torchlight is buzzing on the latest LOS14.1 build? On Stock, Torchlight isn't buzzing.
[Galaxy S II Android Development] gm0:
Hardware issue? It's not making the slightest sound on my device.
[Galaxy S II Android Development] LazyGuy1:
It only makes those noises sometimes. So.. not a problem anyway.
[Galaxy S II Android Development] ale5000:
I think he is just a spammer since all his commits are revert, look here.
[Galaxy S II Android Development] mldmld1968:
Stuck on boot animation with Mokee and Resurection Remix too

I tried to install Mokee 60.1 170413 and Resurection Remix v5.8.4 20170910 on my S2. They both stuck on boot animation, even after a system/cache/dalvik/data wipe.

I came back to full ext4 parititons for RR.

So now, on can say the common code between them is the Firmware (BIOS for a PC ?) or the regional settings.

At the beginning my phone has in properties :

- Android 4.1.2

- BaseBand version : I9100XXMS4

- Build number : JZO54K.I9100XWMS3

So it should be this one : https://samsung-firmware.org/download/Galaxy__S__2__/5124/FOP/I9100XWMS3/I9100XXMS4/

So, Is there a way to change the firmware ? AFAIU :

- (PDA/AP) I9100XWMS3 is android itself (here 4.1.2)

- (CSC) I9100XXMS4 ?

- (MODEM/CP) I9100FOPLS6 ?

Thanks for any idea !
[Galaxy S II Android Development] toy_story:
Look here - https://xdaforums.com/showpost.php?p=71481676&postcount=587

I wrote to you what to do from the very first point in this manual - https://xdaforums.com/galaxy-s2/help/preparing-clean-loss-data-installation-t3712409

But you are lazy and just write messages with stupidities.
[Galaxy S II Android Development] gm0:
My only idea at this point is to start over from flashing the partition table, something must have gone wrong somewhere. I'll attach my own .pit in case something was wrong with yours (it's a 1 GB / 3 GB layout though). Remember to format all partitions afterwards.

You can also try what toy_story wrote in such an unfriendly manner, which basically amounts to using Odin instead of Heimdall, since you already did everything else, but I've always used Heimdall myself without problems.
[Galaxy S II Android Development] the.gangster:
Even if you used one of my PIT-file(s) (which hopefully is unchanged) and which should have the same starting block as the stock layout for p12.

And even if it sounds as if you were on stock ROM before which would make one assume that you also were still on stock layout:

Your error of inability to boot ROMs would perfectly and simply be explained with an unformatted preload partition.

So either give my modified TWRP (follow my signature's TWRP post to find the modified version that allows formatting of preload area) a try to format it (to ext4) or continue reading....

Why so rude? Even your recommendations are not always perfect.

Not meant to be offensive but as examples:

- why do you recommend using my PIT with 512mb preload instead of the variant with 32mb and thus waisting unused space? I intentionally published them in a single ZIP. The one with 512mb was intended for dualbooting DorimanX-kernel users at that time.

- Why do you recommend pitting at all after there are more noob-proof ways to do it?

No need to answer though. There are always many ways to achieve something and people do assess their simplicity differently.

Why still doing it the oldfashioned way? We are lucky to have REPIT-support with our device! No need to worry with PIT files and no worry about forgetting to format anything. Even I didn't use my own PIT-files anymore (although they work!) ever after Repit was launched on any of my devices. It's so much more easy and flexible....

Just rename the downloaded latest repit.zip to something like:

lanchon-repit-20170115-system=1.5G+wipe-data=6G+wipe-sdcard=max-preload=min+wipe-i9100.zip (for an equivilant to the PIT with 32MB preload. 'min' will create an 8MB preload)

lanchon-repit-20170115-system=1.5G+wipe-data=6G+wipe-sdcard=max-preload=512M+wipe-i9100.zip (for an equivilant to the PIT with 512MB preload.)

Above examples do format (except for the internal SD. You can put an +wipe for the latter as well if you start from scratch) If you read the readme of repit, you'll know how to use these parameters in detail. Its support-thread is here.
[Galaxy S II Android Development] mldmld1968:
Hi guys ! :)

Thank you so much the gangster for your precious help ! Reading you shows you really know what you are talking about !

I read many forums about people having boot loog issue, the only fix I found many times was to format dalvik, cache, data partitions. I never heard of /preload.

Even, thanks to your comment, I read using /preload key word. I read it is a useless partition used by stock roms, not used by custom roms and nowhere I read it can cause a boot loop if not formated.

So it seems I can fix this loop boot issue using 2 ways :

- by installing your TWRP rebuild. I read https://xdaforums.com/showpost.php?p=71384669&postcount=633. You says there, there is no difference to the official TWRP 3.1.0-0, but in fact, you say here, there is a difference, it manage the /preload partition. The current installed TWRP do not displays /preload in the partition list.

- by installing the repit.zip directly from the currently installed TWRP renaming the file. As it will wipe and format /preload

To do that, I

- copy the lanchon-repit-20170115-system=1.5G+wipe-data=6G+wipe-sdcard=max-preload=min+wipe-i9100.zip to the sdcard

- I insert the SD in the phone, boot on it on current TWRP.

- using install.zip start the script on the sdcard, it will be automatically copied to /tmp

- start it again from /tmp.

- install rom + gapps + su

As the vocabulary is new for me, I'm not sure to understand correctly this :

Even if you used one of my PIT-file(s) (which hopefully is unchanged) and which should have the same starting block as the stock layout for p12.

And even if it sounds as if you were on stock ROM before which would make one assume that you also were still on stock layout:

==> Before my phone was in stock Android 4.1.2 with the Siyah-s2-v6.0b5 kernel to get root deployed with Odin 1.85, then I used Heimdall to install your pit and the latest TWRP

==> What do you call the the stock layout ?

==> What is p12 ?

==> Why some people don't meet this /preload issue ? In fact, how do I kill the /preload partition ?

I think it would be great to add information about formating /preload in the LineageOS how to install. I'm not alone with this issue.

Thank you gm0 for your support too ! :)

Toy_story, I consider your words have exceeded your thought.

Best regards and thank you again
[Galaxy S II Android Development] gm0:
Mostly because he already knew how to do it that way, plus I didn't realize that recent TWRP versions hide some partitions from the user now. So thanks for giving him the details.

He's referring to the way the partition are arranged on the device. By default, /dev/block/mmcblk0p12 is mounted as /preload, hence "p12". His idea is that in your case there may have been something non-standard about your layout so the modified partition table that you flashed isn't actually pointing mmcblk0p12 to the same starting block as your stock ROM did, thus no valid file system is found at that location. In that case the solution would not be to "kill" /preload but to format it (using either of the two ways he pointed you to).