yashsingh1/xdaforums huggingface dataset:
[Galaxy S3 Neo Original Android Development] Humaxxx:
If your Neo is not certified, then you did something wrong. Not certified means that safetynet fails, Its either CTSProfile or BasicIntegry or both. That means every App you which proofs safetyNet wont start!

But thats fixable! Normally without modifications (root for example or using exposed) S3 Neo with LOS16 is certified. So did you modifications ? If yes undo that. Otherwiese maybe Lineage SU triggers that - i dont know, because i dont use lineage SU.

Here is what you should try:

Uninstall LineageSU with the uninstaller from the LOS-Website. Package name is "su removal (arm) 16.0"

After uninstallig it, boot up again and check in playstore if device is certified. If Not, then message here again, because there must something else triggering it.

If its certified, then everything is fine and you also can use your "Sparkasse-App" - But you have to decide if you can live without root. If you want root and Sparkasse then you have to use Magisk and use some "options" - because the DEVS from the Sparkasse often makes security updates for there apps, which are often able to detect root.

With "normal" Magisk (20.4) the Sparkasse-Apps won't work, but today there is a new Update to Version 21. Maybe thats working, otherwise you have to use "Magisk Canary - Build" from here, download debuk.apk from github and install it (its Magisk Manager - canary build) . From there also update Magisk.

In Magisk Manager App you have to enable some options to get Sparkasse Apps to work:

1: Magisk Hide - enable it, close the app and open it again. Then In Menu there is a new Button "Magisk Hide". there you have to enable all your Sparkasse Apps you are using

2: Hide Magisk Manager - It will ask you for a new Name for Magisk, because some Apps just search if you have installed Magisk Manager, so they know you have root... Choose a Name. After its finished, open that new "App" and it will update. Then Sparkasse should work!

If you got problems message again

---------- Post added at 09:30 ---------- Previous post was at 09:24 ----------

Open a terminal (on your Neo) and type getprop ro.bootloader and post the result here.

It should beginn with "I9301I" or "I9300I"
[Galaxy S3 Neo Original Android Development] Aufhellblitz:
First of all, thank you very much for your detailed answer.

But I don't want to give up my "root" status because of such a stupid app. The following apps would no longer work:

- Titanium Backup

- Total Commander

- Root browser

- Quick reboot

- ~ Adaway

So, in short: it's all too much of a hassle for me. But thanks again for your effort.

I will still test the newer version 21 ..
[Galaxy S3 Neo Original Android Development] Humaxxx:
Yeah if you want root and don't need Sparkasse it's ok. But it's quite easy and needs max 15 minutes to got both to work
[Galaxy S3 Neo Original Android Development] Aufhellblitz:
Do I have to uninstall my old addon-su (LOS root) before installing magisk 21?
[Galaxy S3 Neo Original Android Development] Humaxxx:
If its still on your phone - yes!
[Galaxy S3 Neo Original Android Development] Aufhellblitz:
Sorry for my stupid Question: How? :)
[Galaxy S3 Neo Original Android Development] Humaxxx:
In my Answer from this morning i added a link to LOS - Website wich contains the uninstaller. Its a zip file, flash it in twrp
[Galaxy S3 Neo Original Android Development] Aufhellblitz:
oh dear, I should read better, sorry
[Galaxy S3 Neo Original Android Development] HTC82:
Some bank apps doesn't whant to work on root devices. :(
[Galaxy S3 Neo Original Android Development] Humaxxx:
I tried yesterday, Sparkasse and Push Tan, both worked with the method I described.

If there are other apps which does not work for you, name it here and I will try
[Galaxy S3 Neo Original Android Development] HTC82:
Great, with the Magisk v21 and the right settings the apps are working!! :D:good::good:

EDIT: the IBL BANK is still detecting root on the phone :(
[Galaxy S3 Neo Original Android Development] Aufhellblitz:
Unfortunately not with me. But I now have two magisk managers installed. Once the normal magisk (v21) and the other magisk-canary. Do I have to uninstall the original magisk? I have renamed both to Manager-1 (original) and Manager-2 (app-debug.apk).

The whole thing is very confusing!
[Galaxy S3 Neo Original Android Development] Humaxxx:
Open Magisk Manager App from v21, click deinstall and follow the procedure, Only use Magisk Canary !

Edit:

1) Deinstall both Magisk Version.

2) Reboot

3) Install S-Pushtan - it should work, because you dont have root anymore!

4) Install Magisk Canary Manager apk, click install Magisk, download the zip file

5) Boot to twrp, click install and install the just downloaded Magisk zip

6) Boot and start S-Pushtan - it should fail and close emmidiatly!

7) Open Magisk Manager app

8) Click setting (right upper corner)

9) enable MagiskHide

10) Go to Mgisk Hide, select S-Pushtan app

11) Go back to settings

12) click hide Magisk Manager and select a new Name ( i choose "MM")

13 Wait until Magisk Manager was closed

14) open "MM" or how you called it, click ok

15 Open S-Pushtan - it works
[Galaxy S3 Neo Original Android Development] Aufhellblitz:
Thanks for the detailed and step-by-step description.

But I'll use a different approach now:

Every 3 months I deactivate root for the s-Pushtan app to get a new tan. That is acceptable to me.
[Galaxy S3 Neo Original Android Development] faridtnt:
Hello, I have latest version on my s3ve3gds (gt-i9300i).

But my device time is incorrect and I can't update it!!!

Have you any solution?
[Galaxy S3 Neo Original Android Development] Humaxxx:
When detects the bank app it, directly at start? Or when using it?

For me it worked with Magisk Canary, Magisk Hide and hide Magaisk Manager App...

---------- Post added at 07:46 ---------- Previous post was at 07:45 ----------

Hmm, sorry, dont really understand. What means device time???

You can set time up manually or let it set up automatically by system over network (mobile data or wifi).
[Galaxy S3 Neo Original Android Development] HTC82:
It heppen something strange. I installed Magisk v21, Hide it and the setting for the apps. At the first time the bank apps worked perfect without detection of the root. After a reboot the apps detected again the root (they detect imidiatly at start of the app, some has only an advise of "system non secure" and works anyway other close after the advise).

I will try the other method that you descriped up to the other user and hope will work
[Galaxy S3 Neo Original Android Development] Humaxxx:
Yeah give feedback if it will work, if not i can have a look into it again, because i have only checked once because i am not a customer from Sparkasse...
[Galaxy S3 Neo Original Android Development] andriodking:
When will be 17.1 available? ?
[Galaxy S3 Neo Original Android Development] Humaxxx:
17.1 is available - but not official, because there are still minor bugs
[Galaxy S3 Neo Original Android Development] SirClanger:
Problem with Internal Storage

I've flashed the latest rom of Lineage 16 for Sony camera (from the latest baseband APG1), but now Android can't access to the internal memory storage. How can I fix it?

EDIT: Repartitioning System to EXT4 solved the problem!
[Galaxy S3 Neo Original Android Development] Humaxxx:
Sometimes this problem occurs. Don't know why...

There are some ways to fix it, but can you explain how you did it. In twrp?
[Galaxy S3 Neo Original Android Development] SirClanger:
Using TWRP I formatted Data and System partitions firstly to other filesystem (f2fs for example) and reformatted them again to EXT4.
[Galaxy S3 Neo Original Android Development] Humaxxx:
OK, thanks for info.

Another way to fix it was using a terminal app typing:

su

restorecon -fR /data/media
[Galaxy S3 Neo Original Android Development] 1poweruser1:
you should restore pit and reset nand with odin 3.14.1

flag the erase nand and repartition option in odin, load latest firmware GT-I9301I_1_20180125102753_khg3hokm4o and pit i9301i_S3VE3G_EUR_OPEN.pit.zip
[Galaxy S3 Neo Original Android Development] helloyello:
Greetings!

Glad I was able to remember my XDA-Developers username & pass :)

Meanwhile Mozilla ceased development and support for Firefox on Android below 5.0 and I gave the S3 Neo (using it as a spare toy) it's latest revival, loaded lineage-16.0-20201012-nightly-s3ve3gxx-signed.zip

There were a lot of changes in LOS since I last tried it and also a lot of posts here in the thread, wasn't able to read everything.

Some observations & issues I'm experiencing with lineage-16.0-20201012-nightly-s3ve3gxx

- the battery life is is still at ~50-70% compared to stock ROM, even after the latest changes related to deep sleep & putting the CPU (one core only) at 300Mhz while asleep. One thing I've noticed is the color/brightness of the screen - in LOS it's too crispy/bright even on lower brightness compared to stock ROM, where it looks a little more pale. Maybe stock ROM uses some extra screen PM settings.

- then, apparently the BlueTooth doesn't disconnect anymore on normal phone calls (reported this some time ago) and I believe it's due to the latest changes in firmware/drivers for the WiFi&BT chip. I've used it for hours and never got disconnected.

Now the big issue. While the BlueTooth is stable and OK for phone calls, it drops the WiFi 2.4 GHz connections instantly if used for a VoIP call. Tested it and able to replicate 100% on both Signal Messenger and Skype Lite (I'm only using these two, more Signal).

There's a little detail here. I was using an older TP-Link router loaded with OpenWRT and it all worked OK with it - WiFi 2.4 & BlueTooth. But that router was really lazy.

Some days ago I bought another router (second hand), a newer model - faster one, and with this I'm experiencing the WiFi 2.4 & BlueTooth disconnects. It looks like the LOS firmware/driver gets overwhelmed by the faster traffic and resets the WiFi interface when the BlueTooth is also active. This doesn't happen on the 5GHz band.

Here are more details - a thread I opened on the OpenWRT forum (I was posting as justme123):

forum-dot-openwrt-dot-org/t/solved-d-link-dir-860l-b1-2-4-ghz-wifi-issues-on-voip-calls/77667/4

- substitute the -dot- with actual dots
[Galaxy S3 Neo Original Android Development] HTC82:
Hello, yesterady heppens something anormal on my S3. I had the august version installed from a few monts and all was worked fine. Yesterday a process started to make an error, the process is "com.android.providers.media". It's the Media Storage app of the OS. It appers constantly an error with the option "app information" or "kill app". Now i disabled the app but i don't have the ringtons on the phone.

I tryed to update the OS to the oktober version but i didn't solve the problem. What can i do?
[Galaxy S3 Neo Original Android Development] Humaxxx:
Can you still install apps or take photos (and store it to internal storage) ?

---------- Post added at 09:40 ---------- Previous post was at 09:13 ----------

Are you sure about this? For me it is exactly the other way round!

I tested a few days back with same phone, same settings, same battery... I compared Stock Rom and LOS16. My results are:

- Standby-Time in Flightmode is almost identical

- Standby-Time with flightmodus off, without Simcard inserted, Wifi enabled, GPS enabled, Bluetooth enabled: LOS16 is beating Stock Rom

Stock ROM

* After 12 hours its remaining 79% of battery

* After 23 hours ist remining 64% of battery

LOS 16

* After 24 hours its remaining 78% of battery; Deep Sleep was 22 hours

* After 51 hours ist remining 56% of battery; Deep Sleep was 47 hours

- Screen-On-Time / Display-On-Time: LOS16 is beating Stock Rom

Stock ROM

* 3 hours and about 10 minutes; using Telegram & Browser, + screen off about 2 hours ( dont know i fit was in deep sleep)

LOS 16

* 3 hours and about 40 minutes; using Telegram & Browser –> note: screen was off for additional 8 hours, deep sleep 2¼ hours (tested with wifi enabled but no wifi connected - this will break deep sleep)

So for me battery-lifetime is much better on LOS with standard-settings: in Stock Rom i have disabled / uninstalled all apps that can be disabled / uninstalled by default without an additional app.

LOS16 was running with gapps pico package.

If i use my personal settings on LOS16 (max cpu frequency set to 1190MHz), i got a Sreen-On-Time for about 4-5 hours, depending if phone was completly used or some time in standyby (with drains additional battery!).

Wifi-Firmware was taken now from latest greece Stock-Rom, also settings from there - that was necessary to fix the random reboots (caused by wcnss (wifi) crash), which some users with "special" routers had.

I have to ask, because i didntt get it clear...

You are connected to Wifi2,4 GHz, Bluetooth is enabled (and connected or disconnected?) Then you doing a call with for example signal messenger and wifi connection drops instantly?
[Galaxy S3 Neo Original Android Development] HTC82:
yes i can, the internal memory is working and it has 2,7 GB free, only the Gallery app it dosen't detect any photo or video on the device.

EDIT: it seams i have solved. I reinstaled the gallery app, cleared the cache and data memory of the Media Manager and Download Manager, reboot and no more errors... strange things...
[Galaxy S3 Neo Original Android Development] Humaxxx:
:good:

that would have been my guess
[Galaxy S3 Neo Original Android Development] helloyello:
[MENTION=8750475]Humaxxx[/MENTION]

- regarding battery life - on stock ROM, a German unbloated & latest ROM that I stripped further on my own - uninstalled around 100 applications, and not the crappy & bloated Greece ROM (useful only for the new bootloader) I usually got a 4 day long usage with 6 hours of phone calls (2G) and more than 4 hours of display ON with WiFi/Mobile Data (Firefox & Signal/Skype). I had a screenshot that I wanted to attach to the forum the last time we discussed this, unfortunately I cannot find it right now. In comparison, on LOS I only get maximum 70% of what I got with the stock ROM. 3 hours of phone call, 3 hours of display and after 2-3 days I already need to charge the battery (meaning standby time is also shorter).

- I can confirm what HTC82 reported, the Gallery & Media Storage is buggy on the latest LOS. I had to force stop & clean the cache & storage for Gallery, Media Storage, Download, Download Manager several times in the past days (and reboot the phone) and I still get inconsistencies in the Gallery app - not displaying all my pictures all the time, sometimes not displaying anything at all... But I don't really care about the Gallery, browsing my pictures with Total Commander.

- On the WiFi 2.4 GHz & BT issue. I'm sorry for not being clear (actually I was). Why would you enable the BT and not connect it to the BT audio headset?

The scenario for replicating the issue is the following:

- enable and connect 2,4 GHz WiFi

- enable and connect BT to an audio headset

- start VoIP app - Signal or Skype Lite (should work with any other similar app)

- while inside the app - start a call

What happens after the last step is - the app initiates the VoIP connection, sending quite an amount of UDP packets and proceeds to enable the BT Headset (I suppose it tells Android to route audio through BT). The moment you hear a click in the BT headset and the ringing (calling) sound, the WiFi 2.4 GHz drops instantly and then reconnects. However, due to this disconnection, the VoIP call session is lost.

Again, you need a modern/faster router that has a performant CPU and can handle fast the high amount of packets per second during the VoIP call initialization. On older and lazier routers, the disconnection doesn't happen and I suppose it has something to do with the S3 Neo WiFi&BT firmware/driver not able to handle the higher packets amount together with switching the audio over BT.
[Galaxy S3 Neo Original Android Development] Humaxxx:
So heavily debloated, that may be. For my test i only applied actions which the non - experienced user also can easily perform... Then LOS is much better.

Normally you are right, but there a a lot of (again non experienced) users, which always have enabled it and dont use it...

And I am using bluetooth very rare, but since there is the corona warn app, which needs bluetooth enabled, its enabled all the time, without being connected to a bluetooth headset..

I will try to test this...

But what you can test by yourself is the following:

Edit this file:

/etc/firmware/wlan/prima/wcnss_qcom_cfg.ini

Add the following line:

gChannelBondingMode24GHz=1

Save and reboot and test again.

Note: this can cause random reboots on some routers...
[Galaxy S3 Neo Original Android Development] helloyello:
Proceeded as advised, found an already existing gChannelBondingMode5GHz=1 line and added gChannelBondingMode24GHz=1 after it.

Saved the file, restarted the phone and learned that it didn't help. Unfortunately I'm experiencing the same WiFi 2.4 GHz disconnection when initiating the VoIP call and using the BT headset. :(
[Galaxy S3 Neo Original Android Development] Humaxxx:
Ok, it only was a try. If you dont have random reboots with this line you can keep it - it will increase your (theoretical) wifi speed to 150mbit (instead of 75) in 2,4 network.

I havent tried voip calling by my self at the moment.

--EDIT__

Tried it now, and it worked for me.

I checked in my Router if i am really connected in 2,4GHz Network, also checked in Router if my connection was cancelled at any time - but it was stable.

But everything seems fine (except not the best quality).

I used Telegram to do a call to my wife. Talked 38 seconds and then also did a video call, for 47 seconds which also worked.

My Router is a new one (FB7590).
[Galaxy S3 Neo Original Android Development] helloyello:
[MENTION=8750475]Humaxxx[/MENTION]

Thanks for the test!

Before reporting the issue here, I also tested on several Android devices, 2 stock ROM devices - Samsung tablet & phone and another LineageOS (Android 7) powered J3 2016 Samsung phone. All of them were working fine, no disconnection.

It's only the S3 Neo that is experiencing this issue with the latest LineageOS.

I made a backup of the stock ROM with TWRP, loaded it back on the S3 Neo now and I'm not experiencing the disconnect. Meaning, it's definitely an issue only with LineageOS.

I wish I knew how to debug what's happening during the disconnect. Don't now how to capture the kernel/system log under LineageOS. On the router I only see that theS3 Neo dropped the connection and cannot determine the reason behind.

Some instructions on how to start and capture debugging information would be really helpful now.
[Galaxy S3 Neo Original Android Development] Humaxxx:
I believe you, that this issue exists for you only on neo... But i can only tell you that for me it's working. Don't know if its more depending on your used router or Bluetooth headset.

For log I think you can use catlog or syslog from playstore. Also here on XDA should be existing threads about it.

---------- Post added at 17:13 ---------- Previous post was at 17:11 ----------

Also as I am on latest build since yesterday, i don't faced issues with gallery app.
[Galaxy S3 Neo Original Android Development] helloyello:
Will look to debug it without the Android SDK and I did search on XDA-Developers after some practical info about debugging and failed so far, that was before asking here in this thread. Tried already "logcat main" in a console directly on the phone during the WiFi 2.4GHz disconnect and what I could only get was the "usual" always repeating Video issue : OpenGLRenderer & gralloc.msm8226.so & Adreno-EGL & EGL_BAD_ATTRIBUTE

Exploring the logs on the phone I stumbled upon 13 tombstone files all related to /system/bin/audioserver crashing and all starting (timestamps) from my first LOS16 installation back some months ago (May 2020). The last one happened 2 days ago, in the evening, exactly when I had a Bluetooth audio disconnection during a phone call and thought it was something else, because I believed these BT audio disconnections were resolved in the latest LOS. Apparently I was wrong, they just don't occur that often.

I could upload the tombstone(s) somewhere for inspection - at least the latest one (130KB each), they all look similar on my brief inspection, some audio routing is happening on BT, then some out of memory for some processes, and finally audioserver crashing.

A simple sample - header for the latest tombstone:

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
LineageOS Version: '16.0-20201012-NIGHTLY-s3ve3gxx'
Build fingerprint: 'samsung/s3ve3gxx/s3ve3g:4.4.2/KOT49H/I9301IXXUANL1:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 340, tid: 727, name: TimeCheckThread >>> /system/bin/audioserver <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'TimeCheck timeout for IAudioPolicyService: 6'
r0 00000000 r1 000002d7 r2 00000006 r3 00000008
r4 00000154 r5 000002d7 r6 a38d44a4 r7 0000010c
r8 a2283774 r9 a56926f8 r10 3b9aca00 r11 a47f00f0
ip 7fffffff sp a38d4490 lr a5f34115 pc a5f2be3a

backtrace:
#00 pc 0001ce3a /system/lib/libc.so (abort+58)
#01 pc 00006d5d /system/lib/liblog.so (__android_log_assert+156)
#02 pc 0000e337 /system/lib/libmedia_helper.so (android::TimeCheck::TimeCheckThread::threadLoop()+270)
#03 pc 0000c155 /system/lib/libutils.so (android::Thread::_threadLoop(void*)+292)
#04 pc 00064b43 /system/lib/libc.so (__pthread_start(void*)+22)
#05 pc 0001e051 /system/lib/libc.so (__start_thread+32)

Worth mentioning that I use ViPER4AndroidFX 2.7.1.6, but it isn't enabled for the BT headphones and I don't know how (if even possible) to uninstall it clean without messing around the ROM. However, ViPER4AndroidFX is also installed on the Samsung J3 (Android 7 LOS) and there I don't get any BT audio disconnections.
[Galaxy S3 Neo Original Android Development] Humaxxx:
As i am not a developer, i cant help you with this log. To come into contact with devs you should use telegram S3Neo - Group.

I dont use ViperforAndroid so i dont know if this can cause a problem.
[Galaxy S3 Neo Original Android Development] Amirproton:
Problem with calls S3NEO

I installed LOS 16, every thing work exept call. there is no audio on calls. When I pick up, I cannot hear anybody on the other end and other cannot hear me. when I hang up just hear call end sound. i can recording voice with voice recorder and microphone work corecctly. also i used wire headphone and bluethooth headphone but the problem is not sloved. i install offical rom android 4.4.4 and call is working. any body known how to slove this problem?
[Galaxy S3 Neo Original Android Development] Humaxxx:
As you installed 4.4.4 i guess you have GT-I9300I ? Maybe trying inserting Sim card to Slot 1.

And you have to use latest bootloader on LOS16!
[Galaxy S3 Neo Original Android Development] Amirproton:
yes i have GT-I9300I. I have 2 sim. both of them dosn't work.

i find this solution: https://xdaforums.com/redmi-note-3/help/sound-voice-call-lineage-14-1-t3546237

but i have problem again.
[Galaxy S3 Neo Original Android Development] Humaxxx:
So which of the steps in your mentioned thread did you try?

I recommend to check if your bootloader is up to date... Third last letter should be Q
[Galaxy S3 Neo Original Android Development] Amirproton:
I have lastest bootloader.

finally i change my SIMs slot (SIM1 to slot2 and SIM2 to slot1) and problem solved:D. Thank you
[Galaxy S3 Neo Original Android Development] HTC82:
waw, with the LOS on my S3Neo with all day 2G connection, some calls (less than 1 hour), no other wifi connections, greenefed all possible apps, more than 1 hour of whatsapp usage, a little connection on 3G for some Firefox reserches.. new battery... network open from 6 am to 11/12 pm and i finish the day with 10% of battery... How can you feel 2-3 days without charging it?

extract the gallery apk, disintall the app and reinstall it. I solved for about a week... yesterday the problem came back... reinstall and it's ok... i don't know why this problem...

until last summer the LOS was working great, in normal usage i didn't have any problem on the phone... after august there is every time any problem... why the developers toch what is working good? :D