yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 10 Questions & Answers] horvalos:
Your friend faced the same issue?maybe something goes wrong when you do factory reset because my phone was like yours,i bought it 4 months old and did factory reset...Anyway,the only solution that I've settled is using an app from playstore "volume booster-speaker booster & Sound booster" and ot works for me,if you download the same app every now and then open it and exit because the system stops it..!(for example if you clear the recent apps from the tab)
[Xiaomi Mi 10 Questions & Answers] Abdul Rafé:
Thanks for the response. I will definitely try this. I again and again reset the phone but problem it still there. I think the issue is only with ringtone/notifications because in youtube i have no complaints regarding low sound
[Xiaomi Mi 10 Questions & Answers] horvalos:
I know,same thing for me also.. I've send a bug report at xiaomi.. We'll see maybe with the miui 12,5 the problem will be solved...
[Xiaomi Mi 10 Questions & Answers] Abdul Rafé:
Can you confirm if this problem was not present on previous versions ?
[General Topics] kramerica2:
I'm looking for a BT earphone that will display caller ID as appears in my WM contacts.

Bonus features would be the ability to call these contacts directly from the earphone (not internal headset memory), incoming SMS, reminders, etc...

Anything like that available?

Thanks....
[General Topics] TheChampJT:
I've never used it, but Motorola has one that may work for your device. I saw somewhere online that someone was using it on a non-Motorola device, and of course Motorola wouldn't confirm if it would work on other devices. Plantronics may have one with a display, and I'm about 99% sure Jabra has nothing.

For the reminders and dialing, Microsoft Voice Command is the best bet for you. It's about $35, but if your really going to use it, it's worth it.
[Wear OS Q&A, Help & Troubleshooting] yjay18:
I'm building an app that uses a master key to derive device keys for each watch that runs the app. Currently I am just hard coding the master key but this is obviously not safe at production. I am wondering if/how I can save the master key which is a string like 8hkSrvEy3VV9hdigoLaX/M== so the app can acess it in order to derive the device key without exposing the master key?

I looked in to keystore and SharedPrefrences but not sure it is secure enough for what I need.

Thanks so much!
[Wear OS Q&A, Help & Troubleshooting] a1291762:
If you don't trust the private storage of the phone you need to store your data in the cloud.

If that's a little too much for you, try this as one example of keeping at-rest data encrypted.

Data Encryption on Android with Jetpack Security

Have you ever tried to encrypt data in your app? As a developer, you want to keep data safe, and in the hands of the party intended to use…

medium.com
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
Reserved
[T-Mobile Samsung Galaxy S II SGH-T989] squircular:
I can verify that this ROM works on Hercules (SGH-T989D). Thanks very much for your effort.
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
Thanks for information. Does GPS work on hercules? If yes, how long does it take to get a lock?
[T-Mobile Samsung Galaxy S II SGH-T989] squircular:
Yes, GPS works. It took about 2 minutes to get the first fix (cold start) and about 15 seconds to get subsequent fixes (warm start). Both of these measurements were taken inside near a window so it might be faster outside.
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
Thanks for the feedback. I appreciate it.

Since I bought my phone used, I'm not sure if my GPS is working 100% due to hardware. It shows the satellites, but never gets a fix. If it does work, it takes about 10 minutes to get a fix. It's completely useless for a car GPS.

There are some error messages in the adb logcat which might be related to why I can't get a fix, but I will have to investigate.
[T-Mobile Samsung Galaxy S II SGH-T989] JMSchneider:
I'm going to give this a try - this will be my first modded phone and so I'm taking it very slow. I've got a Rogers Samsung Galaxy S II Skyrocket SGH-I727R which I'm ok with making a mistake on. I don't want Gapps. I've currently got TWRP 3.1.1 and I'm reading through everything multiple times.

My current task is to do my best to understand bryan2894's notes on repartitioning.
[T-Mobile Samsung Galaxy S II SGH-T989] JMSchneider:
Hello retiredtab (or anyone else),

I just want to clarify one little thing. In step 4 of the ROM Installation Instructions as follows:

4. In TWRP, go to Wipe -> Advanced Wipe -> check

Internal Storage

-> press on "Repair or Change File System" -> press on "Change File System" -> press on "EXT4", and then swipe to start formatting the internal SD card. This can take up to a minute.

As can be seen by the picture of my screen, there is no partition called 'Internal Storage'. Instead I'm wondering if it should be 'SDCard'.

Is this correct?

Many thanks for anyone who can confirm this.
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
I think your assumption is correct. I followed the instructions back in February 2021, but honestly can't remember if I ran into the same thing or not with the naming.
[T-Mobile Samsung Galaxy S II SGH-T989] JMSchneider:
Thank you for the reply retiredtab - your input is greatly appreciated!
[T-Mobile Samsung Galaxy S II SGH-T989] JMSchneider:
I think I found an article on TWRP that explains the partition name change.
[T-Mobile Samsung Galaxy S II SGH-T989] JMSchneider:
Because the 'Internal Storage' seems to have changed spots (as indicated in the last post), I came up with a workaround for a problem that I encountered.

Initially, I was using the twrp-3.0.0-0-skyrocket.tar.md5 and reasoned it would be the "latest OFFICIAL TWRP" file for the ROM Installation instructions but in step #9 I ran into a problem - a red-highlighted section of the log read "Updater process ended with ERROR: 7". I later discovered this has something to do with version compatibility mismatching. So I decided to regress to the older Official TWRP (v2.8.6-0) recovery and go at the whole process with the exact files in the links. Then, when I went to flash the ROM I had no problems.
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
bryan2894 and others did all the initial work on TWRP and building this rom. I'm only updating his work + others so I don't know why specific versions of TWRP are required. All I know is that I followed his instructions exactly so that I could build a 2021 rom. As I stated, I'm adding NO VALUE other than compiling a 2021 version.

Once the 14.1 April security patches get merged in LineageOS, I will compile a new version, test it and then share with others who are interested. It looks like there are 5 patches for April as per https://review.lineageos.org/c/LineageOS/android_build/+/307154

A number of people says it compiles, builds and boots with no problems, but I prefer to wait until it's officially merged before I start the compile process.
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
New build called lineage-14.1-20210415-UNOFFICIAL-celox.zip (had to try 3 or 4 times before upload succeeded).

Release notes for April 15, 2021

1. April 5, 2021 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307154

2. A reboot after flashing the April build will take about 6 minutes. Be patient.
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
The May security patches still aren't merged yet into LineageOS as per

https://review.lineageos.org/c/LineageOS/android_build/+/309293

It's waiting approval since May 6. There are 3 CVEs for May.

At this rate, I'll probably skip making the May security patches and wait for June 5th as it's May 26 as I write this.
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
The May 5th security patches finally got merged today, June 7, as per

https://review.lineageos.org/c/LineageOS/android_build/+/309293

However, seeing how the June 5th patches should be announced shortly on LineageOS, I will wait until those are announced and then make a June build. No sense making a May build, testing and uploading it if June patches will be out in a few days.
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
New build called lineage-14.1-20210609-UNOFFICIAL-celox.zip.

Release notes for June 9, 2021

1. May 5 + June 5, 2021 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309293 and https://review.lineageos.org/q/topic:"n-asb-2021-06"+(status:open OR status:merged)

2. A reboot after flashing the June build will take about 6 minutes. Be patient.

3. For builders, there were problems building with 4GB with Jack server which worked before. I had to increase to 6GB using

export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx6G"
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
New build called lineage-14.1-20210709-UNOFFICIAL-celox.zip

Release notes for July 9, 2021

1. July 5, 2021 security patches as per https://review.lineageos.org/q/topic:"n-asb-2021-07"+(status:open OR status:merged)

2. A reboot after flashing the July build will take about 6 minutes. Be patient.
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
New build called lineage-14.1-20211011-UNOFFICIAL-celox.zip

I have not forgotten about this device, but there's a holdup with the security monthly patches starting with the July 5 patch not being merged due to a problem as per https://review.lineageos.org/c/LineageOS/android_build/+/313397

However, the August patches are officially merged while the September and October ones are pending approval. Rather than wait any longer, I decided to merge September and October security patches into this build.

So while the OS may report that it's on the June 5th security patch, that not true in this case. It has all the October 5th 2021 patches included.

Release notes for Oct 11, 2021

1. July 5 + August + September + October, 2021 security patches as per

https://review.lineageos.org/q/topic:"n-asb-2021-07"+(status:open OR status:merged)

https://review.lineageos.org/q/topic:"n-asb-2021-08"+(status:open OR status:merged)

https://review.lineageos.org/q/topic:"n-asb-2021-09"+(status:open OR status:merged)

https://review.lineageos.org/q/topic:"n-asb-2021-10"+(status:open OR status:merged)

2. A reboot after flashing the October build will take about 6 minutes. Be patient.
[T-Mobile Samsung Galaxy S II SGH-T989] squircular:
October build applied perfectly from the April build. Took 8 minutes after rebooting. Thanks very much again for your effort!
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
@squircular , The difference between my observed 6 minutes and your 8 minutes might be due to the fact that I have very little apps installed and no gapps. If you have gapps and lots of apps, it may take the OS extra 2 minutes to process those files before it's fully booted.
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
New build called lineage-14.1-20211208-UNOFFICIAL-celox.zip.

NOTE OS will show June 5th security patches due to hold up of

https://review.lineageos.org/c/LineageOS/android_build/+/313397

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

Release notes for Dec 8, 2021

1. Nov 5th and Dec 5th, 2021 security patches as per https://review.lineageos.org/q/topic:n-asb-2021-11 and https://review.lineageos.org/q/topic:n-asb-2021-12 (about 2,100 files had to be recompiled).

2. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
New build called lineage-14.1-20220128-UNOFFICIAL-celox.zip

NOTE OS will show June 5th security patches due to hold up of

https://review.lineageos.org/c/LineageOS/android_build/+/313397

Release notes for Jan 28, 2022

1. Jan 5th security patches as per https://review.lineageos.org/q/topic:n-asb-2022-01

2. Whatever LineageOS changed since Dec 5th security patches.

3. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
New build called lineage-14.1-20220224-UNOFFICIAL-celox.zip

NOTE OS will show June 5th security patches due to hold up of

https://review.lineageos.org/c/LineageOS/android_build/+/313397

Release notes for Feb 24, 2022

1. UNOFFICIAL Feb 5th security patches as per https://review.lineageos.org/q/topic:n-asb-2022-02

2. Whatever LineageOS changed since Jan 5th security patches.

3. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
[T-Mobile Samsung Galaxy S II SGH-T989] shezy14:
pls how can i download te rom?

pls how can I download this rom?
[T-Mobile Samsung Galaxy S II SGH-T989] Peter0x44:
Hi, I have this rom working perfectly fine on my Samsung Galaxy S2 SGH-T989 hercules, and I figured I'd tell everyone here rather than remain silent.

There were a few roadbumps on the way, which I figured I would also document just in case anyone else runs in to these.

The first very minor problem was the wording on the install page here:

Samsung Galaxy S2 Hercules T-Mobile SGH-t989

Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...

twrp.me

In particular, `Use the PDA tab or button to browse to and select the tar file that you downloaded and flash the device.`

In the latest versions of odin, there is no PDA tab, I was told it had been renamed to AP, and that indeed did work

First real problem, is that the official latest twrp for the device is actually broken, just like JMSchneider reported for his skyrocket device. For me, it showed absolutely no partitions in the backup screen, so I couldn't create any backup, and I also could not view any files on the device. Regressing to older version v2.8.6-0 as JMSchneider did also worked for my device.

Then, the repartitioning instructions before flashing Bryan's unofficial TWRP were also slightly unclear, as other people here have reported

(the "internal storage" VS "sd card" wording), but I didn't have any problems doing this

Afterwards, I just went ahead and flashed the latest ROM provided on this thread, and all went pretty OK regarding the ROM itself.

The very last problem I had was with magisk - for some reason, after extracting the boot.img from the zip of the rom, patching it, then flashing it, magisk was prompting to reboot every time I opened the app. This turned out to be a bug in the latest magisk release at the time of writing, which is magisk v24.3. Downloading the very latest version from github actions solved this issue.

So, to recap, the process I think people should follow on these hercules and skyrocket devices is basically:

1. Flash TWRP v2.8.6-0 using odin, put the tar in the AP slot

2. Back up all partitions from the backup screen.

3. Follow Bryan's repartitioning instructions, keeping in mind that "internal storage" really means "internal SD" or something like that.

4. Flash the latest version of Bryan's unofficial TWRP, and reboot to it

5. Flash the latest version of the ROM on this thread, and optionally gapps, then reboot.

6. Have the patience to wait for everything to boot, then wait the 5 minutes and reboot, then wait the 5 minutes again.

And... profit, hopefully

Thanks to the effort of all who posted in this thread, I definitely would've had much more trouble with this, if I didn't see at least a few of the issues I ran in to already on this thread. I really appreciate it, as I would be stuck with no really useful phone without them!
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
Thanks for your feedback on this. I plan to make another build next month in May if/when the May 5 security patches are made. That build will also include March 5 and April 5 in addition to the May 5th patches.
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
New build called lineage-14.1-20220610-UNOFFICIAL-celox.zip

NOTE OS will show June 5th, 2021 security patches due to hold up of

https://review.lineageos.org/c/LineageOS/android_build/+/313397

but thanks to syphyr@gmail.com, we continue to get security backports, where possible.

Release notes for June 10, 2022

1. UNOFFICIAL March, April, May and June 5th, 2022 security patches as per

https://review.lineageos.org/q/topic:n-asb-2022-03

https://review.lineageos.org/q/topic:n-asb-2022-04

https://review.lineageos.org/q/topic:n-asb-2022-05

https://review.lineageos.org/q/topic:n-asb-2022-06

2. Whatever LineageOS changed since Feb 5th security patches (about 2,000 files had to be recompiled).

3. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
New build called lineage-14.1-20220709-UNOFFICIAL-celox.zip

NOTE OS will show June 5th, 2021 security patches due to hold up of

https://review.lineageos.org/c/LineageOS/android_build/+/313397

but we continue to get unofficial security backports, where possible.

Release notes for July 9, 2022

1. UNOFFICIAL July 5th, 2022 security patches as per

https://review.lineageos.org/q/topic:n-asb-2022-07

2. Whatever LineageOS changed since June 5th security patches (about 2,100 files had to be recompiled).

3. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
[T-Mobile Samsung Galaxy S II SGH-T989] Peter0x44:
Flashed without issues.
[T-Mobile Samsung Galaxy S II SGH-T989] prinnydood:
Apologies if I missed it, but I'm having a hard time finding the "roomservice.xml" mentioned in the first post. Could someone please point me in the right direction? I'd like to build this rom from source.
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
Hmm, at one point it was in post #1, but it disappeared. I re-uploaded it again. Here it is though.

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<project name="thewizrd/android_device_samsung_celox" path="device/samsung/celox" remote="github" revision="cm-14.1" />
<project name="thewizrd/android_device_samsung_msm8660-common" path="device/samsung/msm8660-common" remote="github" revision="cm-14.1" />
<project name="thewizrd/android_device_samsung_celox-common" path="device/samsung/celox-common" remote="github" revision="cm-13.0" />

<project name="thewizrd/android_kernel_samsung_msm8660-common" path="kernel/samsung/msm8660-common" remote="github" revision="cm-14.1" />

<project name="thewizrd/proprietary_vendor_samsung_celox" path="vendor/samsung/celox" remote="github" revision="cm-14.1" />
<project name="thewizrd/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-13.0" />

<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-14.1" />

<!-- Qcom audio -->

<remove-project name="LineageOS/android_hardware_qcom_audio"/>
<project name="thewizrd/android_hardware_qcom_audio" path="hardware/qcom/audio" remote="github" revision="cm-14.1-caf-8660" />
<project name="thewizrd/android_hardware_qcom_audio" path="hardware/qcom/audio-caf/msm8660" remote="github" revision="cm-14.1-caf-8660" />

<remove-project name="LineageOS/android_hardware_qcom_media"/>
<project name="thewizrd/android_hardware_qcom_media" path="hardware/qcom/media" remote="github" revision="cm-14.1-caf-8660" />
<project name="thewizrd/android_hardware_qcom_media" path="hardware/qcom/media-caf/msm8660" remote="github" revision="cm-14.1-caf-8660" />

<remove-project name="LineageOS/android_hardware_qcom_display"/>
<project name="thewizrd/android_hardware_qcom_display" path="hardware/qcom/display" remote="github" revision="cm-14.1-caf-8660" />
<project name="thewizrd/android_hardware_qcom_display" path="hardware/qcom/display-caf/msm8660" remote="github" revision="cm-14.1-caf-8660" />

<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.1" />

<project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-14.1" />

<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="cm-14.1" />

</manifest>
[T-Mobile Samsung Galaxy S II SGH-T989] prinnydood:
Thank you kindly!
[T-Mobile Samsung Galaxy S II SGH-T989] prinnydood:
SUCCESS!

I was able to build from source, and flashed and booted the ROM successfully!

I did hit some roadblocks initially, which I was able to solve.

(Attached build steps, using an Ubuntu Docker/Podman container, in case anyone else would like to try building this as well).

Edit: not sure why `.md` or `.txt` extension won't upload =/

I've zipped up the guide (in markdown).
[T-Mobile Samsung Galaxy S II SGH-T989] digixmax:
I just flashed the latest build lineage-14.1-20220709-UNOFFICIAL-celox.zip on my I727.

Without any GApps, the initial boot completed without any hitch (i.e., no complaint of any Google process/service stopping). After the initial boot, I rebooted into TWRP and flashed open_gapps-arm-7.1-pico-20220215, and the phone again booted without any error indication -- however I am not able to sign into Google through the Playstore or through Settings->Accounts->Google.

Any pointer on how to get the Google sign-in working would be greatly appreciated.
[T-Mobile Samsung Galaxy S II SGH-T989] digixmax:
I also noticed that MTP over USB does not often does not work: MTP either does not show up on Win10 Explorer or shows up but empty (the phone /sdcard alsways shows up when the phone is in TWRP recovery, no issue with the USB cable).
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
I don't run any type of Windows on my systems. I also don't run any Google apps, only Aurora Store.
[T-Mobile Samsung Galaxy S II SGH-T989] cannondale0815:
@retiredtab Thank you for keeping this old junker alive with recent builds. It is appreciated :)
[T-Mobile Samsung Galaxy S II SGH-T989] retiredtab:
New build called lineage-14.1-20221227-UNOFFICIAL-celox.zip

We continue to get unofficial security backports, where possible.

Release notes for Dec 27, 2022

1. UNOFFICIAL Dec 5th, 2022 security patches as per

https://review.lineageos.org/q/topic:n-asb-2022-07

https://review.lineageos.org/q/topic:n-asb-2022-08

https://review.lineageos.org/q/topic:n-asb-2022-09

https://review.lineageos.org/q/topic:n-asb-2022-10

https://review.lineageos.org/q/topic:n-asb-2022-11

https://review.lineageos.org/q/topic:n-asb-2022-12

2. Whatever LineageOS changed since July 5th security patches (about 5,100 files had to be recompiled).

3. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient. It might be longer if you have gapps installed.
[T-Mobile Samsung Galaxy S II SGH-T989] Lost-Entrepreneur439:
Do you know if this would support the i757m, the Canadian "Skyrocket HD"? It appears to be the same phone except for the screen resolution, but who knows, maybe there's some major differene I haven't noticed.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] retiredtab:
For those interested in a March 2021 build for skyrocket, see

https://xdaforums.com/t/unofficial-lineageos-14-1-celox-march-8-2021.4244373/

All responses and replies should go in the above thread so I can track it all in one place.

DO NOT RESPOND in this thread.

Thank you.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] It_ler:
Thanks for your contribution (y)