yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] leitefresco:
Hi

Same here.

1. I installed only the ROM and then rooted it;

2. New battery (2019.12.10) fully charged, disconnected charger;

3. The phone was idle, after some time I decided to take a look, it had a full crash;

4. Power button for device to reboot;

5. Battery at 90% charge, less than 1 h after being fully charged.
[Galaxy S II Android Development] Galaxyninja66:
I'm getting some battery read issues too. Figure it's the battery.

On the latest build (04-13-2020) voice calls, data, everything works. wifi isn't spotty after I enable "stay connected even if wifi has no internet". BT audio works fine in my car, magisk works, video playback, all camera functions, microphones, everything seems to work and the vsync issue is *significantly* better. I'd say this is a keeper for sure!
[Galaxy S II Android Development] skmurthy1988:
Can you elaborate on the same I am having difficulty to boot LOS 17.1 by following all the the procedure mentioned in OP.
[Galaxy S II Android Development] Mr.cyrux:
I tried to install last build (with and without GApps, with and without wipes/factory reset) LOS boot logo for 5 minutes and then auto reboot to TWRP, any idea what i can do?

(sorry for my bad english skills :D )

Edit: Without installing TWRP App it works ...
[Galaxy S II Android Development] Lister Of Smeg:
Hi [MENTION=5668462]Mr.cyrux[/MENTION],

If you've tried with or without factory resets, then by the sounds of things you've already wiped your phone and therefore have nothing to lose (regarding data).

So I would suggest ODIN restore to stock rom, wiping out all previous partition layouts, and then follow the guide again. I wonder if it's a partition issue, and can't access/create/enough space, and hence it loops and does nothing.

So yeah, try ODIN back to stock and then go from there...

Cheers, Lister
[Galaxy S II Android Development] Mr.cyrux:
Thx for answering.

The "mistake" was at the end of flashing TWRP asked to install the TWRP App, last time i said no and now everthing works fine...
[Galaxy S II Android Development] guest4711:
That's a known issue with TWRP app - causing bootloops on Android 10. Nobody needs this app which is phoning home on every boot.
[Galaxy S II Android Development] skmurthy1988:
Thanks for the information after 10 days of trying everything I am able to boot LOS 17.1 based on your post.
[Galaxy S II Android Development] ze7zez:
Long long time ago ...

From TWRP v.3.0.3-0, i.e. from December 2016 there is an option to disable the question in the settings called "Prompt to install TWRP app if not installed".
[Galaxy S II Android Development] guest4711:
Right. Thanks for reminder ;)
[Galaxy S II Android Development] rINanDO:
Thanks, I updated the OP.
[Galaxy S II Android Development] rINanDO:
Hi everyone,

New buid is up!

In this build I focused to get all the stuff working in LOS < 17.1 like:

- Spirit 2 (FM Radio)

- Netflix

- SafetyNet

- Selinux enforced

- Chrome browser

- Magisk

I think I addressed enough issues to remove 'BETA' from the title.

When debugging around why Chrome crashes I stumbled on DRM missing service errors.

Dunno why Chrome needs this at startup at the first place, but after resolving this

the next issue was missing symbols in proprietary blob vendor/lib/mediadrm/libwvdrmengine.so.

So after hexediting and using old libprotobuf-cpp-lite.so prior Android O,

Netflix was working too :D. I don't know if this also resolves Chromecast issues since I don't own

this device, but please test!

Selinux is fixed now, but I decided to leave the main installation ZIP on Selinux permissive

so apps that don't work with selinux remain to work using this ZIP only.

The Magisk Kernel-image is Selinux enforced. This will give you superuser and let you pass

SafetyNet and even (on clean installation) and will show up as 'certified device' in GAPPS Pico.

Happy testing!

Build #8 2020-05-06

PLEASE TEST FOR DAILY DRIVE

Overall state: Stable-ish

Android build: 10.0.0-r33

Required recovery: TWRP 3.3.1-1

Changes:

- Update sources

- Selinux enforced for Magisk kernel image

- Browser crashed fixed. This is because of missing DRM HIDL services.

- Netflix, DRM playback fixed!

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-20200505-UNOFFICIAL-i9100.zip (Selinux permissive)

lineage-17.1-20200505-UNOFFICIAL-i9100_boot_magisk.img (Selinux enforced)
[Galaxy S II Android Development] ze7zez:
I think that it is not only my opinion,

that you are a glorious example of a person involved in the project

who does not have a device, but continues to work and research

like a real scientist.

We users can learn a lot from the progress and results of your work.

Many, many thanks, Professor. :good::)
[Galaxy S II Android Development] js-xda:
Thank you for your efforts! I installed last night the below build without magisk or any GApps (using F-Droid).

Once it is started up, it runs quite smoothly. During startup, I am observing an issue where I am not sure whether it is specific to the build, LineageOS 17.1 or rather more relevant due to the limited computational power of the device: When I am too quick to unlock the device after a (re)start, it will present me "System starting up" (or similar - not using English GUI) with a moving bar below. Most of the time, it will restart at some moment while I can't do anything about it. If I wait some time to unlock, everything is fine. I recall having seen the message itself also on either my S5 LTE+ or the Oneplus 2 while both are still on LineageOS 16.0. For both, the message disappeared at some moment without a reboot.
[Galaxy S II Android Development] changel pro:
Hi sr.

I have a doubt...

Suppose I am installing an app that requires permissions to read notifications (such as one that syncs a smartwatch with the phone). But when entering those settings, the screen shows "the function is not available on this device".

so the question is: Is it a system problem? Or is it phone compatibility with this android version?
[Galaxy S II Android Development] :
1+5 android 10

https://xdaforums.com/oneplus-5/development/jaguar-q-oneplus-5-official-v1-t4035061

s4 android 10

https://xdaforums.com/galaxy-s4/i9505-develop/rom-lineageos-15-1-t3816279
[Galaxy S II Android Development] js-xda:
Well, it is fair enough to indicate that somewhere else in the complete XDA-developers forum might be the answer. But it does not hurt to be a bit more specific (e. g. link to the specific post - not only the thread - or mention what is the buzz word that I might have missed). I browsed thru the whole S4 thread and OP and last posts of the other and there is nothing on the issue that I describe as far as I can see.
[Galaxy S II Android Development] rickmar:
Battery drain

Hi there!

I've installed the 17.1 Lineage (OP) and everything when smoothly. Works great so far. My best regards to rINanDO :good:

the only thing i'm facing is a strange bettery drain. Battery at 100% leeave over night. 10hrs later and it show 33%....... No wi-fi or any app running... no SIM card also...

Prior to this build i've had intalled the 16.0 lineage OS and sometimes it did the same thing! I had GAPPS at that time, but now after installed 17.1 i've tried the BitGapps , as I thought it was the culpit, but it seems its isn's... BTW and don't have anything specia installed , it's amost stock...

Anyone face the same problem?

Thanks!

Ricardo
[Galaxy S II Android Development] rINanDO:
Hi, did you use magisk which is using selinux enforced? And had you closed all running apps before screen off? I used Kernel Audiutor to detect if the device deep sleep properly. The only thing I can think of is that a running app is holding a wakelock so the phone keeps running in 100Mhz instead of letting it deep sleep.

Please check if you like to find behavior changes when closing all running apps and/or using magisk selinux enforced.
[Galaxy S II Android Development] rickmar:
Hi rINanDO,

No, I didn't use magisk or any other root software. Just installed the rom (clean) and BitGaps and youtube app I think. Nothing else. I remember the email app got running in the background for some hours, but just one time.

Over the night I will try to make sure anything is running in the background and check out again, but I usually do this. Let's see....

Btw there is something I can do to make sure there are no wakelocks?

Thanks, i'll get back to you.

Ricardo
[Galaxy S II Android Development] rINanDO:
Hi Ricardo,

I will try that configuration and check if wakelocks are released properly. If you can you could get some logs via 'adb shell dumpsys deviceidle' and 'adb shell dumpsys batterystats'.

And check if the WiFi setting 'automatic activate WiFi' is disabled.
[Galaxy S II Android Development] OllieW:
Hi there, I also switched to the latest LOS17.1 (fresh installation after full wipe - stock kernel with no Magisk, OpenGapps Pico) and it's running very smooth so far (only a bit laggy after first start of phone and first start of apps). After some days of testing here are the bugs I found so far:

WiFi connections to AP with PMF enabled don't work (the bug was also in LOS16 and could be fixed with the "pmf=0" instead of default "pmf=1" setting in "wpa_supplicant.conf", because PMF is not working on S2 but driver will force PMF right now)

WiFi hotspot will not start up and be turned off immediately (same problem in older LOS release, but could fixed - I will try to check this)

sudden reboot (some minutes after trying to turn on WiFi hotspot several times - may be the cause...)

volume control while voice call in hands-free mode (only loudspeaker) does not work (ear speaker volume control is ok)

lock-screen symbol over "sim card symbol" after start up (only graphical bug)

I really like this release - unbelievable that Android 10 is running so good on the old S2! But I have one question: What exactly is the mentioned "SIM Pin on RIL is currently disabled" and what will change if it could be enabled?

Great work again rlNanDO! Really impressive.. :good:
[Galaxy S II Android Development] ze7zez:
Android Messages with RCS support

Hello all.

I just sent the first message from Android 10 using RCS in Google Messages via Wi-Fi to an Android 4.3 device in my region, i.e. outside of US.

Receiving an SMS from Adroid 4.3 also works correctly without chat, plain sms.

You need:

In the phone a SIM card from the GSM operator, with which Google has established cooperation in the field of Jibe RCS cloud support (you will find out when you try to set up chat),

Airplane mode turned off,

Connection to or without a hotspot,

Data transfer mode enabled,

Google services enabled,

Carrier Services application,

Messages application,

Turn on chat features in the Messages application.

Important note.

Only after completing the connection setup with entering your own SIM card phone number, you can turn off data transmission.

Chat features by Google FAQ.
[Galaxy S II Android Development] rickmar:
Hi rINanDO,

Keep it idle this night about 9 hours, and no problem this time. Went from 100% to 98%, so all good. I cleared all apps before leave it. No automatic wi-fi setting activated. Not touch it anyways.

In Lineage 16 it also had this behaviour , sometimes all good and just one day it drained the battery inexplicably. I'll keep looking into it more thoroughly and reporting it, because I cannot replicate it.

I think maybe an app that it's not sleeping, as you said, is the probable cause...

Thanks,

Ricardo
[Galaxy S II Android Development] cikenkari:
my phone having wake up like every minute, then i disable email application.

is it possible to having pop up windows feature as android go disabling "Display over other a..".

thanks
[Galaxy S II Android Development] rINanDO:
Hi OllieW,

Thanks for your found bugs. I located the patches for pfm=0 and also found the solution of WiFi hotspot. The will be there in the next build.

"SIM PIN on RIL". I disabled the patched code because it could lead to trashed sim (it asked directly for your puck-code and when you reboot, the SIM is trashed). So only use a SIM-card which is not PIN-locked with this ROM.
[Galaxy S II Android Development] OllieW:
OK, great news! But my SIM has PIN code enabled and it works perfectly asking for PIN and not PUK (So no trashed SIM card here - perhaps this bug doesn't exist any more?!) - only sometimes after first start up the "Enter SIM PIN" text is directly over the SIM card lock symbol.
[Galaxy S II Android Development] Jookia:
Has anyone been able to get encryption to work with this?
[Galaxy S II Android Development] rINanDO:
Ow ok! That's great! So it already works without my old patch from LOS 16.0? Then its behavior is probably fixed commonly in LOS 17.1. I didn't dare to test since I will end up again with a trashed SIM card. I will update the OP when I release next build.
[Galaxy S II Android Development] rINanDO:
My phone now had suddenly deep sleep issue. I'm using magisk, pico gapps, WiFi active connected and ril. It's my daily drive phone. Need to recharge after 6-7 hours.
[Galaxy S II Android Development] rickmar:
Hi rINanDO,

This morning had the same issue... I had about 73% last night and when I woke this morning it had 1%. So it drained the battery again. I don't know at is doing it,, as i've closed all the apps before i left the phone.

Any ideias? I don't know how to use console/linux but if there is something you would like me to do, i'll do it no problem :)

Regards,

Ricardo
[Galaxy S II Android Development] :
Push service stopped working (GMS core) and apps need to run background.

[Fix]

Other push services:

https://mega.nz/file/5JAxxAwZ#KnfV3fr7mjyyAZTWfHepOJdhB0y0xDCUFXJyVDdzNKo

https://www.apkmirror.com/apk/samsu...-service/samsung-push-service-3-1-00-release/
[Galaxy S II Android Development] rickmar:
Hi there,

I have to install both the apps to to resolve the wakelocks / battery drain? that is it?

Thanks

Ricardo
[Galaxy S II Android Development] OllieW:
Small update: The sudden reboot happened again or otherwise after some time the SIM card is lost (No SIM card inserted). I will try to disable SIM PIN und check if the problems will resist - perhaps the "SIM pin / RIL issue" is still there and the behavior is different from one SIM card to another?! But I don't have battery drain problems with LOS17.1 - in LOS16.0 the battery was down after one day and now the same battery will last much longer..
[Galaxy S II Android Development] rINanDO:
The sudden RIL issue is still there but less often since using a hack. It is not solved yet. Some racing occurs in combination with ril and WiFi it seems. You can check logcat if you like and search for 'racing' if it had occurred and the hack has been applied.
[Galaxy S II Android Development] :
Maybe. You can test this method and try to run system optimizer to free ram, and battery may drain slower.
[Galaxy S II Android Development] OllieW:
How can I apply the hack and is there any manual how to use logcat? There is no root in LOS17.1 with no magisk, so terminal access will be limited I think?!

Update: After activating Terminal Editor in Developer options, I did enter "logcat | grep racing" - no entry so far! I disabled SIM PIN and will watch for the "next sudden reboot" or "SIM card removed notification"..

I found two more bugs:

The "Preferred network type " will list 2G, 3G and 4G (recommended) although the GT-I9100 doesn't support 4G/LTE. Selecting "4G" will have no effect - perhaps it's used for "2G+3G" instead?!

Manual network search will get no other result despite the SIM card operator. Selecting the home operator while seach is running will freeze settings app. So automatic network selection can't be disabled at all.
[Galaxy S II Android Development] rINanDO:
New build is up!

Thanks guys for finding the bugs! I squashed some of them :)

In my experience running this phone still as daily drive with Magisk and Pico Gapps and it is still very usable. Ok, sometimes you need to be patient. I decided to give it the overall state of stable. If someone disagrees, please say so.

Build #9 2020-05-13

Overall state: Stable

Android build: 10.0.0-r35

Required recovery: TWRP 3.3.1-1

Changes:

- Update sources

- Fixed Screencast (Chromecast)

- Fixed Wifi Hotspot

- Fixed Wifi with PMF enabled (should work now, but please test this)

- Enabled Restrict USB feature, thanks to [MENTION=9549206]TALUAtXDA[/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-20200512-UNOFFICIAL-i9100.zip (Selinux permissive)

lineage-17.1-20200512-UNOFFICIAL-i9100_boot_magisk.img (Selinux enforced)
[Galaxy S II Android Development] rINanDO:
The hack is already there. This is the commit to fix RIL's binder issues due multi threading issues. It keeps RIL alive for a few days instead of a few hours.

https://github.com/rINanDO/android_...mmit/c402c62eb419561232f593e8ca8a1d34ec78583b

Hopefully someone could help us out. I can't figure out what is causing this.
[Galaxy S II Android Development] OllieW:
Thanks for the explanation and the update! After full wipe and fresh install of the new LOS17.1 build (20200512) with OpenGapps Pico (20200514) I can give the following information:

WiFi hotspot working now (thanks for that)

Disabled WiFi PMF support NOT working (still "pmf=1" in /system/system/etc/wifi/wpa_supplicant.conf and therefore after setup wizard in data/etc/wifi/wpa_supplicant.conf - after changing to "pmf=0" connection with PMF enabled routers will work)

Settings - operator - network mode will list "4G (recommended)" option (should not be listed or "3G+2G")

RIL problems (unfortunately no "RACING" visible in logcat after checking with terminal editor from developer options)
[Galaxy S II Android Development] D...:
Hi: my report in the last build LOS17.1 (20200512) with OpenGapps Pico (20200514).

- Screen cast on chromecast not found, the icon of cast turn red, but i can send movies to netflix with chromecast buton. Thanx rINanDO!!
[Galaxy S II Android Development] rINanDO:
I just figured out the updated _overlay.conf files are still put in /system/etc/wifi instead of /system/vendor/etc/wifi. Thanks for testing!
[Galaxy S II Android Development] NadavCE:
Great work on this! Performance is better than Lineage 14.1 (Android 7.1), and might actually be better than CM11.

I'd like to report a bug, though; the "sensors-disable" quick toggle (that can be enabled through developer options) doesn't work. Camera still works after enabling...

I'm happy to provide more details.
[Galaxy S II Android Development] :
Black wallpaper may fix battery drain.

---------- Post added at 05:25 AM ---------- Previous post was at 04:59 AM ----------

Pls remove status testing

---------- Post added at 05:25 AM ---------- Previous post was at 05:25 AM ----------
[Galaxy S II Android Development] js-xda:
Thank you for the continued efforts!

Running the above build without a SIM in the device and so far going well except the below previously reported start-up bug where I am doubting whether it is actually linked to the build or something else.

While copying the latest build to the device running still the previous build, I noticed that USB debugging was active as default while I had never developer options activated (which resulted also in an error message that I should first do so before activating USB debugging ...). Not sure whether linked to the "Restricted USB feature" in the above listed changes but this seems to be gone with the latest build.

This behavior is still present and I am still wondering where it is linked to. If someone knows and would be kind enough to point me to the right buzzword or a specific post linked to this, it would be great!
[Galaxy S II Android Development] Badger50:
[MENTION=9635294]jjgvv[/MENTION] and [MENTION=10638533]j730gm[/MENTION], please check your PM's!! Thank you.

--Badger50
[Galaxy S II Android Development] rINanDO:
I noticed I left debugging active by default in normal builds, so I removed it. It is technically not related to Restricted USB feature.
[Galaxy S II Android Development] andreaslev:
I have been trying to flash the system with the firmware since yesterday. I followed the instructions. However, the system does not boot. After a while, the cell phone returns to recovery mode. What's wrong?

-----

has done itself ... after flashing again it worked :)
[Galaxy S II Android Development] ze7zez:
Could you write briefly why apex\com.android.runtime.debug is used instead of apex\com.android.runtime.release?

In apex\com.android.runtime.debug, there are duplicate *d.so libraries with *.so.

I suppose that less debugging means less load on the processor.
[Galaxy S II Android Development] rickmar:
I had to do a full wipe and install again the ROM., as I was getting the same return to recovery as you said. Even after flashing again. But i see you got it sorted :)

Regards
[Galaxy S II Android Development] OllieW:
After some days of testing the actual 20200512 build (no magisk) I can give some more feedback:

Much more battery drainage than last build

"No service found error" (RIL errors on SIM) more often even with disabled SIM PIN

Phone will hang up completly (black screen - also occuring once after hitting reboot) and revival only after removing battery for some seconds

I suppose that SIM RIL problems are the main cause for all problems - perhaps I can help sorting them out! Unfortunately logcat on terminal editor won't display any errors..
[Galaxy S II Android Development] leitefresco:
Hi

I came across this review The $7 Samsung Galaxy...

Once again rINanDO congrats.
[Galaxy S II Android Development] rINanDO:
Sim ril issue is one symptom of a binder threading issue. The currrent thread is accessing another's thread local variable. This happens very rare.... and causing ril to crash.
[Galaxy S II Android Development] ze7zez:
Just information.

dumpsys ends with "DUMP OF SERVICE usb:" and the phone resets.
[Galaxy S II Android Development] rINanDO:
Sim ril issue is one symptom of a binder threading issue. The currrent thread is accessing another's thread local variable. This happens very rare.... and causing ril to crash.

Also try to set logd to eg. 16MB because the loglines are deleted/summarized after little time.
[Galaxy S II Android Development] skyrider699:
Issue I am having

I have watched the latest video from channel48 on how to install this but still no luck. I install it with TWRP 3.1.1-1 but after I reboot it the phone never gets past the loading lineage logo. I have tried it with and without GAPPS. Please help!
[Galaxy S II Android Development] bersem:
Why channel48 ??? All you need to do is described on first page there. Most important flash guide named as OP !!!

Just follow the steps in OP and you will.. Its so detailed and easy and also for every noob described.

Regards !
[Galaxy S II Android Development] skyrider699:
I have followed all the steps and even watched the linked video (from channel48) but no luck. The phone has been on the lineage loading screen for 5hrs.
[Galaxy S II Android Development] Faffendecker:
Try TWRP 3.3.1.1. as the instructions show on first page. I've had issues in the past with roms not installing because I was not using the version recommended by the developer.
[Galaxy S II Android Development] rINanDO:
Did you chose not to install twrp in first reboot?
[Galaxy S II Android Development] rINanDO:
All builds I released are so called userdebug builds. These builds allow legacy phones to allow text relocation, and permissive domains, etc. With little modifications in Android I can create a user build. This is considered as a hack because in HIDL we should rebuild proprietary blobs by code we don't have. Selinux blocks this 'neverallow'-rule on execmod. Technically removing validation code on these never allow rules by build flag I can create a user build.