yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] nick mccombie:
Unable to use mobile data on straight talk

I am unable to use mobile data on straight talk. I can call and text but no data.

I have tried,

Resetting network settings

Factory reset

Different apn settings

If anyone know how to correct this please let me know
[Galaxy S II Android Development] :
He deleted his account

!?
[Galaxy S II Android Development] ze7zez:
It is not known where you are from and what Samsung Galaxy S II model you are using.

From the pictures I can suppose you are using a model from the AT&T network.

This ROM is mainly for the i9100 model, what you can read about in the first post of the thread.

Perhaps the differences in the operation of operators and network bands cause your problem that you have a problem.

In my i9100, internet works just fine.
[Galaxy S II Android Development] lee.wp14:
AT&T network should not be confused with AT&T model in this case. AT&T model has AT&T logo in place of samsung logo. However correct me if I'm wrong.

I did suggest that it is an APN misconfiguration. You have a AT&T sim, but the APNs are not AT&T APNs. You may try setting AT&T APN and retry mobile network data.
[Galaxy S II Android Development] 908070:
I have to install gapps for arm or arm64 ?
[Galaxy S II Android Development] blunatic:
ARM
[Galaxy S II Android Development] defmy:
First of all, thank you for this portage, we all appreciate this work :)

I have a problem, my screen does not stop turning on by itself without turning off, do you also have this problem?

Using last version with Magisk + root.

PS: I found a temporary solution, screen off with an application and not wait for the screen timeout.
[Galaxy S II Android Development] rINanDO:
New build is up!

This is the first user-build instead of the userdebug builds I created.

Officially we can't create user-builds because we are not allowed to load legacy blobs for our sensors and stuff.

Selinux prevents us by doing this. However I hacked this security check to ignore 'never allow rules' like we have in userdebug-builds.

Please share your experience with this build if it runs smoother or more worse :)

Build #10 2020-05-27

Overall state: Stable

Android build: 10.0.0-r35

Required recovery: TWRP 3.3.1-1

Changes:

- Update sources

- Changed buildtype to user (was userdebug)

- Fixed Wifi with PMF enabled

- Fixed FullHD recording

It was actually recording at 720p but saved as 1080p

- Removed 4G/LTE from preferred network type thanks to [MENTION=6944026]lee.wp14[/MENTION]

Downloads

i9100-LOS-16.0-Emulated-Storage.pit

i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5

i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img

lineage-17.1-20200526-UNOFFICIAL-i9100.zip (Selinux permissive)

lineage-17.1-20200526-UNOFFICIAL-i9100_boot_magisk.img (Selinux enforced)
[Galaxy S II Android Development] ze7zez:
Very functional camera.

Requires clean installation.

Installation from the previous version without wiping the Data causes bootloop.

After restoring the backup using twrp, flash rom.zip again (same version as the backup) because flashing the ROM again does overwrite the rootfs where TWRP has set wrong selinux labels. >Source<

The 5.0 GHz access point band for Wi-Fi hotspot is not useful for this model.

The GPS fix did not work and still does not work.

After enabling debug mode with the PC cable connected, the screen froze and the system required hardreset.

The phenomenon of the vibrating screen happened once.

It records 1080p video very well with full image and sound synchronization. Incredible! :good::D

And besides, very smooth operation, as in the previous version.
[Galaxy S II Android Development] defmy:
It may not be related, but my problem with the screen turning always on is resolved with the last release :)

No problem without wiping the Data, perhaps because I had an already clean installation with very little use. The 5.0 GHz access point is useful for me because I only have this type of network, it saves me from leaving an active 2.4 GHz ;)
[Galaxy S II Android Development] RicardoMullion:
Hey, thanks for your work, it works quite stable, but with some lags due to GAPPS, however, can you make a build which have Selinux Enforced and without Magisk?

As here without Magisk is permissive, I want a version without Magisk and Enforcing, thanks
[Galaxy S II Android Development] 908070:
First start

How long does the first start after installation take?
[Galaxy S II Android Development] js-xda:
Not sure whether related but have you seen the above remark that the latest build might require a clean installation (while mentioning boot loop and not stuck booting)? Could this be part of your issue? I assume an issue is at least what your question is pointing towards.
[Galaxy S II Android Development] 908070:
After a clean installation according to instructions, the boot process stops.

The bow (is that what it is called?) runs 1 hour without progress.

I don't know what else I could try :confused:
[Galaxy S II Android Development] ze7zez:
Clean installation is after wiping Cache, Dalvik Cache, System, Data.

Don't forget to disable the TWRP installer.
[Galaxy S II Android Development] defmy:
Do you also have a proportional loss of autonomy? I use it little and the battery drains for no reason.
[Galaxy S II Android Development] 908070:
Thanks, this was the problem. This should be noted in the instructions.
[Galaxy S II Android Development] js-xda:
This is not specific to this build but a common general issue of the TWRP app. But indeed nasty that it is not well documented - in general, not here.
[Galaxy S II Android Development] guest4711:
I really don't understand why people tend to install this needless spying app.
[Galaxy S II Android Development] js-xda:
Well ... if you are new to custom ROMs and TWRP, you first need to learn A) that it is a bad idea to install it due to running often into startup issues, B) that is does not provide real benefit and C) that it might spy on you (where I can't want to judge whether it is true). Thing is that this is not stated where one would want it for a newbie to find easily: At the place that you can download it - the TWRP website or the respective TWRP threads. For someone involved since a while with custom ROMs, all of this is obvious ... but most of us learned it also the hard way, right?

Thank you! Few minor things to consider for next build or OP:

The above indicated build is now also SE enforcing - at least indicating so in the Trust menu within settings. Or is this about the user-build aspect?

Already the case for previous builds incl. 16: Is there a reason why these builds don't present the USB connection type choice in the quick access menu upon connecting a USB cable?

Maybe rather central LineageOS "bug" but I don't have another device running yet on 17.1 to compare: In the phone app, the shortcut at the bottom of the page for contacts is not localized (label is "contacts" instead "Kontakte" (German)). UPDATE: Upgraded another phone to 17.1 and observed the same localization issue - not related to this build therefore.
[Galaxy S II Android Development] guest4711:
[mantra]

× I never touch 'okay' before checking all settings...

× I do not install any app when I'm not sure I'll need it.

× I use advanced setup instead of simplified/standard one

× I backup all data before updating the system.

× I double check everything before allowing it to run with system rights

[/mantra]
[Galaxy S II Android Development] defmy:
I don't always understand my battery problem (see image). No GPS, no SIM card, no bluetooth, but just use of WiFi and the camera. And yet, I don't even have a day ...
[Galaxy S II Android Development] js-xda:
Hard to provide help based on the provided information. Would be helpful to provide how long the battery lasts (1 d = from morning til next morning or from morning til evening or from morning til afternoon?) and what kind of usage frequency (do you use the camera as a kind of webcam or do you take a few pictures during the day?). The slope of the battery trend won't be that much different whether lasting 1 h or 4 d. ;) Mine lasts with active WiFi, SIM installed but no data and using basically only WhatsApp something like 48 h when checking on average every other hour messages.

Are you sure it is the software and not the battery?

Something that I observed in the past with 16.0: When using the backlight of the menu & reverse button for notifications, I had the feeling that battery drain was much more. Can't say whether it was the power consumption of the backlight or whether the blinking hindered some power saving mode. But turning off LED notification seemed to have helped back then.

Is the drain already the case with the bare build or only when installing certain apps?
[Galaxy S II Android Development] rINanDO:
True,I added it just now. Thanks.
[Galaxy S II Android Development] defmy:
I leave the phone on at night and in the morning it is completely switched off.

My usage, I take a few pictures during the day, for scan barcode for example, nothing else. I feel like my phone never sleeps and stays active all the time without going into deep sleep.

I bought another battery this week and I have the same issue.

As the phone drains even without touching, I am not sure that the LED has a link on my autonomy.

I only installed a barcode scan application, I rooted the phone (with magisk) to install afwall (firewall) and nothing else, that's why I was wondering if others people also had a problem with autonomy.

I was looking for similar cases and a potential solution to resolve it. Thanks in any case for your attention :)
[Galaxy S II Android Development] js-xda:
Indeed, described situation sounds a bit odd but I have no experience with afwall. No specific further idea.

Just to be sure: My remark was about using the backlight for notifications. Not the backlight when touching the buttons during usage.
[Galaxy S II Android Development] defmy:
I solved a problem which made me lose autonomy, the WiFi never seems to be deactivated, I did not find a setting in the parameters. So I use Tasker to turn off the Wifi when the screen turns on.

I now hold more than 24 hours now, even if I would like the consumption curve to be more straight than descending in deepsleep mode, strange...
[Galaxy S II Android Development] rINanDO:
I took a deep dive into A-GPS and it seems A-GPS is indeed broken. Some overlays introduced in Pie are undone in Q which handles AGPS-settings.

A fix is already made, so A-GPS should be fixed in next build :)
[Galaxy S II Android Development] rickmar:
Hi defmy, i'm sure I have the same issue with battery drain as you mentioned. I have no other applications installed (just the BiTGApps) and sometimes my phone just drains... It's not always, i don't know when it does.

I too have notifications lights disabled but I don't think it's that...

Hope it can be fixed :)
[Galaxy S II Android Development] ze7zez:
Restoring Android 10 via TWRP - final fix

To avoid bootloop after restoring ROM from a TWRP backup,

you no longer need to reinstall the same ROM that was restored.

The invaluable [MENTION=3044346]arco68[/MENTION] prepared the fix_rootfs_label.zip file for flashing in TWRP after restoring the ROM,

which fixes the rootfs label.

[MENTION=2222292]rINanDO[/MENTION], please add this information in the first post.
[Galaxy S II Android Development] K.D.A:
Dear rINanDO, please return it to the busybox firmware.
[Galaxy S II Android Development] NadavCE:
Great work so far, rINanDO! My i9100 feels snappier than ever.

However, I'd like to report a few issues I found with the current build:

* Encryption is broken.

* Battery drain is present, but disappears when switching to Airplane Mode (no SIM in device in any case, tested on WiFi).

* The "Sensors Disable" Developer quick-toggle doesn't disable the camera.

I'd be glad to provide logs or more details in order to get these issues fixed :good:
[Galaxy S II Android Development] defmy:
Cool I am not alone, I have the same behavior with the same case. As seen above, the autonomy has been improved by deactivating the Wifi when the screen is on. It's not yet optimal yet...
[Galaxy S II Android Development] rINanDO:
Thanks! I added in the OP.
[Galaxy S II Android Development] rINanDO:
I just found out that booting permissive is blocked in user-build. I didn't knew that. I'll update the OP.

Is this quick access option available on other phones? Maybe I can enable it when I figure out how to do so.
[Galaxy S II Android Development] ze7zez:
This is a trifle, because the screen with the choice of USB preferences when connected to a PC can be easily found in the settings search engine (enter: USB pref)
[Galaxy S II Android Development] js-xda:
Thank you.

Yes, it is available for sure on current and past LineageOS builds of OnePlus 2, OnePlus 5, Samsung Galaxy S4 and I am pretty sure it was available on Samsung Galaxy S5+ and Samsung Galaxy Tab S2. Not sure though about the Nexus 7 AOSP 7. If it is an easy one to include, great. If it is a major hassle, don't bother. Was more wondering whether there is specific reason to not have it.

Did I mention anywhere that it isn't possible to access? I was asking whether there is a reason not to included the

quick

access option.
[Galaxy S II Android Development] ze7zez:
[MENTION=2222292]rINanDO[/MENTION]

I wonder what the LineageOS kernel does after normal "Power off" the phone.

If you do this, the battery will drain.

Does LineageOS still perform hidden work when powered off?

For a change, if in LineageOS in advanced restart you do:

Restart -> Recovery,

then in TWRP you do:

Reboot -> Power Off (for 100% certainty I do: Reboot -> Recovery and again Reboot -> Power Off)

then there is no drain battery because the correct shutdown will be done by the TWRP kernel.

In this case, however, turning the phone back on will start TWRP instead of LineageOS,

which means that the bootloader will boot the kernel from the recovery partition instead of the boot partition.

And did I write that you wrote that there isn't possible to access?

No!

I wrote that it is

a trifle

.
[Galaxy S II Android Development] js-xda:
First of all: No offence taken - I hope likewise. Was not the intention at all.

My point was only that commenting "This is a trifle ..." on a question that states "Is there a reason ..." (asking for information) is not correctly considering the context. This would have been different if I had asked "Please include it because it is otherwise not workable" (asking for implementing a possibly unnecessary feature). Sorry if my point was not coming across the right way.
[Galaxy S II Android Development] ze7zez:
I apologize if you have felt somehow affected.

My intention was not to discredit the report, but to point out that there are more important issues for rINanDO to do.

If we pay attention to small things, rINanDO will not focus on the most important matters.
[Galaxy S II Android Development] rINanDO:
Thanks, I will check those repos how they activated it.
[Galaxy S II Android Development] rINanDO:
I honestly don't know, but I doubt it has something to do with LineageOS. Possibly a kernel driver thing is sometimes hanging and I can't debug at shutdown....

When I try to use ADB, it just stops logging when shutting down...... and it doesn't hang everytime when it's shutting down. With SIM or without SIM.
[Galaxy S II Android Development] officiallyme:
Hi everyone,

I just got my S2 back out and wanted to install this cool new ROM.

I followed the instructions to the letter but after booting my apps cannot seem to access the internal storage properly. Total commander was unable to access the drive until I installed Magisk and gave it root permissions.

I also cannot see the internal storage when connecting to my notebook (but it is possible when the phone is in recovery).

And I tried e.g. Servers Ultimate and it shows an error that it cannot write/access 0.

Is there something I can do about this? I did not get any errors during installation

By the way, I followed the instructions for people coming of off Samsung Stock. I was coming off of an old LineageOS which had a custom pit. But I asume that this is not an issue because you supplied the pit files in the first post, right? Or would I need to flash a different re-partition pit first?

I also did not manually install IsoRec. If I understand your first post correctly, this is included in the TWRP file you flash in Odin.
[Galaxy S II Android Development] rINanDO:
New build is up!

Build #11 2020-06-07

Overall state: Stable

Android build: 10.0.0-r37

Required recovery: TWRP 3.3.1-1

Changes:

- Update sources

- Selinux enforced

- A-GPS fixed

- Speaker volume control during call

Downloads

i9100-LOS-16.0-Emulated-Storage.pit

i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5

i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img

lineage-17.1-20200606-UNOFFICIAL-i9100.zip

lineage-17.1-20200606-UNOFFICIAL-i9100_boot_magisk.img
[Galaxy S II Android Development] chief_wigum:
Build #11 2020-06-07 Audio Jack no Sound with Build #8 2020-05-06 Audio Jack working.
[Galaxy S II Android Development] Oxydeme:
Maybe a little fix in there or revert would do the trick,
[MENTION=2222292]rINanDO[/MENTION] what about latest commits?

Any way to help?
[Galaxy S II Android Development] leitefresco:
Hi.

Yes, not working here also...
[Galaxy S II Android Development] rINanDO:
Yes, I made a error in audio policy. Fixed speaker but broke audio jack and Bluetooth audio...
[Galaxy S II Android Development] rINanDO:
Thanks, I fixed it already. I will create a new build soon. I'm checking encryption stuff how it suppose to work. Anyone has experience with this?
[Galaxy S II Android Development] ze7zez:
Do you mean an encrypted system like e.g. Nexus 6 stock ROM, on which applications intensively using nand are able to warm up the phone that it is difficult to hold it in hand? :confused:
[Galaxy S II Android Development] rINanDO:
Sounds like something we don't want. My guess the encryption decryption is done by software meaning our s2 will be more slow on nand... Anyone has experience with encrypted s2? And which los version did it actually worked?
[Galaxy S II Android Development] mirhl:
N6 was bugged and rushed.

Now, of course a humble S2 wouldn't stand a chance to that either.. But nowadays there's actually another kind of encryption.
[Galaxy S II Android Development] bersem:
So it was time to upgrade from LOS 16.

Wiped Cache > Dalwik> System> rebooted to recovery> dirty flashed last LOS 17.1 build + gapps pico.

Works like a charm. [MENTION=2222292]rINanDO[/MENTION] thank you !!!
[Galaxy S II Android Development] K.D.A:
Bluetooth low energy - does not work :(

My bluetooth lamp is not visible. On previous versions of android everything worked.
[Galaxy S II Android Development] rINanDO:
New build is up!

Not much done except fixing the audio-policy stuff to fix audio.

I also checked why encryption is not working. It is because TWRP 3.1.1-1 is formatting /data-partition wrong.

But if we fix this in fstab in TWRP and reformat /data, Android is encrypting and reboots a couple times.

But it hangs at mounting the encrypted /data and hangs on bootanimation. It doesn't let me boot into TWRP.

The kernel reboots leaving me to ODIN the phone.

Build #12 2020-06-13

Overall state: Stable

Android build: 10.0.0-r37

Required recovery: TWRP 3.3.1-1

Changes:

- Update sources

- Fixed audio volume control

Downloads

i9100-LOS-16.0-Emulated-Storage.pit

i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5

i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img

lineage-17.1-20200613-UNOFFICIAL-i9100.zip

lineage-17.1-20200613-UNOFFICIAL-i9100_boot_magisk.img
[Galaxy S II Android Development] bersem:
Everything works well since upgrade (dirty flash ) from LOS 16 except boot. It boots after third time properly into system. 2 times soft reboot at lockscreen with no sim card bug.

I remember i have repitted as LOS 16 starts with lanchon tool and switched to emulated storage..

[MENTION=2222292]rINanDO[/MENTION] should i repit with the new pit file that u have made after ? Or some else is wrong and it doesnt boot properly ? Or i have to clean flash the Rom ?

May logcat help ?

Thanks in advance !

Regards
[Galaxy S II Android Development] mirhl:
Yes, that really does sound like the same bug I have been reporting times and times again with any kind of corrupted partition.
[Galaxy S II Android Development] starsider:
Had a go and got it running on my S2. Got a lot a lagg when moving around menu's and that sort of things. Still experimenting.

A great achievement to get this android 10 on an S2, a phone which is still impressive.
[Galaxy S II Android Development] David_s2vep:
If someone tries to bring android 10 to s2 plus (GT I9105P)I make him a bronze statue
[Galaxy S II Android Development] Sobhan Mazaheri:
Please changelog for last build LineageOS 17.1 i9300 (2020.06.16) [MENTION=3742928]rln[/MENTION]anDO
[Galaxy S II Android Development] js-xda:
Just in case you missed it by accident: It is a build for i9300 (S III), not i9100 which is the scope of this thread. So, would explain why there is no changelog here.
[Galaxy S II Android Development] Sobhan Mazaheri:
I understand that this forum is not i9300 But mr@ rlNanDO has just made a new build for the s3 i9300 And I didn't know where to ask that question
[Galaxy S II Android Development] rINanDO:
I'm helping Chronomonohrome with some issues in i9300 and created a build for the team to check. It is not a release I plan to publish. Use at own risk. Specifically this i9300 build you refer has fixed gps. Other stuff state is unknown and not aligned with the build sources of Chronomonochrome. We are also try to fix vsync for both devices since it uses same kernel and some device hals.
[Galaxy S II Android Development] Sobhan Mazaheri:
Thanks for your efforts

So let's wait for the final build Chronomonohrome
[Galaxy S II Android Development] ertun2017:
google play store problem

there is a google play store installation problem
[Galaxy S II Android Development] Linuxci:
Hello, i had installed lineage 17.1 on my s2 device, it was so exciting to run adroid 10 on this device, thanks for all efforts but i have to return to stock rom because of the missing 3G video call feature. Can you please write the instructions to install stock rom back, thanks.
[Galaxy S II Android Development] ozbargainerforlife1:
stuck into recovery mode

Hi,

I have followed through steps on my s2. After step 6, my ODIN says Pass. I shut the phone but when I try to boot into recovery mode, it is stuck on the boot screen.

Please help how do I go into recovery mode?

1. Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).

2. Start ODIN 3.07 on your PC.

3. Connect your phone via USB to your PC.

4. Press volume up on your phone, ODIN should detect your phone.

5. In ODIN:

Auto Reboot : unchecked

Re-Partition: checked

PIT : i9100-LOS-16.0-Emulated-Storage.pit

PDA : i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5

6. Press Start.

7. After succesful flash, reboot phone into Recovery:

- Press Volume up + Power/Standby + Home and hold for 10 seconds.

The phone shuts down.

- Repeat Press Volume up + Power/Standby + Home and hold for 10 seconds

Phone boots in recovery mode
[Galaxy S II Android Development] kalagani:
E3004: This package is for device: galaxys2,i9100,GT-...: this device is .

Hello rlNando,

on my S2, I am using your lineage-15.1-20181010-UNOFFICIAL-i9100_SU_MicroG.zip.

So before installing it with an adb sideload command,

with heimdall I flashed isorec recovery and kernel on a new repartition pit

heimdall flash --repartition --pit I9100_1.5GB-System_6GB-Data_512MB-Preload_by-the.gangster.pit --KERNEL boot.img --RECOVERY recovery.img --no-reboot

Thinking these isorec recovery and boot on this new repartition was sufficant, I just made a new adb sideload lineage-17.1-20200613-UNOFFICIAL-i9100.zip

So, process do no occur with error

I know my current TWRP is trwp3.1.0-0 and not your 3.3.1-1 but I am not sure it is the only cause?