yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] curiousrom:
MtpDocumentsProvider Patch? | In-Call Volume Adjustment Fix Feedback

Thanks [MENTION=382340]walter79[/MENTION] for posting the info & link in this thread. If you look at the Logcat errors (under CLICK TO SHOW CONTENT) I posted in MTP Host as stopped - Crashing Bug Workaround Fix S3 LineageOS the first one is E vold : Failed to readlink for /proc/1/ns/mnt there is no mnt file in the ns folder in my S3 running LineageOS 14.1 updated to 2018-03-01. Could you provide one?

I am not a developer but willing to test it if you can explain how to apply your patch. I searched root w/ MtpDocumentsProvider (screenshots) & could not find a MtpDocumentsProvider.java file. Is it part of the files found in the /system/priv-app/MtpDocumentsProvider/MtpDocumentsProvider.apk which I attached to this message?

*****

In-Call Volume Adjustment Not Working Fix

Thanks for the thanks and feedback & hit the :good: Thanks! button on the posts that you find helpful. Besides being good for the ego of the poster, it indicates to other users that the suggestions/tips were useful to somebody so may be good for them too.

In reference to: In-call Volume Too High - Volume Adjustment Not Working Fix

"...should be merged into the sources, right?" - I don't think it will be merged any time soon as no Bug report was made as described in post #1 , you are one of just 3 users who reported this problem in the thread since Nov. 2017 & all hands on deck currently for the LineageOS 15.1 Oreo launch for a small batch of devices for testing it. Check LineageOS Changelog 16 - Smart Styles, Treble is trouble and Omfg Oreo and the post by forkbomb444 the dev of LineageOS for S3 i9300 & OP of this thread here.

***
[Galaxy S III Original Android Development] lyolic:
Phone app is not showing for some seconds when I receive incoming call. Are there any ability to resolve this issue?
[Galaxy S III Original Android Development] acroreiser:
This is not a fix. To fix MTP-host crash, LOS kernel need my Mount Namespace backport, which can be found here: https://github.com/acroreiser/Koffee/commit/6e85942e07d095d77b0bdb810b400cb4b2417cd9

Or just flash Koffee.
[Galaxy S III Original Android Development] nobuteru:
It works, I have disabled MTP host as suggested as workaround, now reactivated, and it works
[Galaxy S III Original Android Development] mountainguan:
Removed 14.1 devices
Samsung Galaxy S III US variants: AT&T, Sprint, T-Mobile and Verizon - no longer maintained

I think i9300 still have hope to update, due to other devices has been abandoned, but i9300 still be maintained.
[Galaxy S III Original Android Development] abelenki:
my eyes. :D

try to use full stops, then maybe someone will be able to read your message.
[Galaxy S III Original Android Development] Hawaiihemd:
Latest twrp will fix your issues. Grab from here: https://twrp.me/devices/samsunggalaxys3internationalexynos.html

There are explicit instructions on how to install twrp right there too.

EDIT: And please always use latest version of any given rom when you have any issues. Chances are they have been fixed already.
[Galaxy S III Original Android Development] hasanfares:
thanx

Thanks

I've already dowloaded latest twrp the problem is can I flash it using philz or by Odin right above philz will it work this way
[Galaxy S III Original Android Development] Bometdebanjo:
Use Odin. Read instructions!
[Galaxy S III Original Android Development] :
Latest daily 0131 could not be flashed by twrp, "updater process ended with error: 7" . I installed unofficial lineage version before, can i just flash official over it ?

And can u make camera quality great again ? in CM 13 camera quality was great, now in 14 camera quality is very very bad .
[Galaxy S III Original Android Development] mohand06:
Your charger has usb cable
[Galaxy S III Original Android Development] abelenki:
latest weekly 20170131 flashes just fine with lates TWRP.
[Galaxy S III Original Android Development] OllinAtl:
Ok .. first, I know nothing about android, but i bought a old S3 (small project) to install Lineage .. and .. well, everything works fine, but from time to time i get this "MTP host has stopped". I appreciate any help. Thank you.
[Galaxy S III Original Android Development] dana.marivani:
Anyone can answer?!
[Galaxy S III Original Android Development] LuciferIII:
Ignore it ,we all get that error.It will get fixed some day :laugh: maybe :D
[Galaxy S III Original Android Development] avishek83:
Anybody pls confirm if videocall is working in whatsapp..cause my front cam not working in videocall..

Is there any fix for this?
[Galaxy S III Original Android Development] Simon_29:
It isnt working and there is no fix for it. I already made a bug report on jira.lineageos.org for it :)
[Galaxy S III Original Android Development] baltics:
Has anyone applied this code change?

http://www.techugly.com/2016/08/how-to-enable-video-calling-and-unlock.html
[Galaxy S III Original Android Development] Simon_29:
The tutorial explains how you activated it when Whatsapp Video call wasn't available... We are looking for a solution for how to fix the error when you call someone via Whatsapp video call.

Thanks anyway!
[Galaxy S III Original Android Development] baltics:
Hi Simon, I realised that. But wondered if the issue was on the ROM side or the App side.
[Galaxy S III Original Android Development] qb74:
how come "there's no fix for it"? what exactly is broken? something with the camera api?
[Galaxy S III Original Android Development] Simon_29:
I am pretty sure that it is rom sided but the question is if it is caused by the Los base or our kernel/device drivers. As you may have seen I reported the bug a few days ago at jira but I got no answer :( https://jira.lineageos.org/browse/BUGBASH-40

Can you read the included log? :)

In my point of view there seems to be something broken with the "CameraService" and the "audio_hw_primary" (i think so because there are errors :D)

---------- Post added at 04:49 PM ---------- Previous post was at 04:48 PM ----------

Read above.
[Galaxy S III Original Android Development] Maxoobidou:
audio is being revamped AFAIK. They are switching to a common Samsung HAL.

Once that's merged, you can try again and see if it solved your issue. That's probably the reason the ticket doesn't have an answer yet.

But just to be on the safe side, people experiencing the same issue can post some logs on the JIRA issue (2 or 3 is fine, there's no need to drown the ticket with logs).

[EDIT]

Here's the commit for the switch to the common audio HAL : https://review.lineageos.org#/c/159471/
[Galaxy S III Original Android Development] arnicika:
install was so smooth and perfect, but now i'm stuck on first using, i found wifi, connected, but now it is stuck in "network is checked" and nothing happens, tried restart and waiting since 15 minutes?

what could this be?

thanks
[Galaxy S III Original Android Development] Gogolo2:
For video call in whatsapp you have to go back to 4.4.4. There it works, Ive tested it.
[Galaxy S III Original Android Development] ArdaCsknn:
Yeah we still have hope thanks to Simon.He is putting a lot of afford to S3.He even halfly fixed the HWC and released experimental build.
[Galaxy S III Original Android Development] Noobkid77:
Things are looking bad ? we can only hope we will receive Oreo at this rate
[Galaxy S III Original Android Development] ArdaCsknn:
Many changes are for Galaxy A7-A5.But sometimes he commits for 4412.
[Galaxy S III Original Android Development] LuciferIII:
We ain't getting Oreo anytime soon, and Android P is on it's way (kinda). It would be best if Simon would just skip Oreo a go straight to P.

Just my option, anyone else?
[Galaxy S III Original Android Development] doug613:
Horrible news...My i9300 just died!

Question; What phone (2-5yrs old) should I buy which HAS trouble free ROMS at least 6.0?

150 USD budget?
[Galaxy S III Original Android Development] curiousrom:
Sorry for you.

Cause of i9300 running LineageOS death is on topic, the rest is not.

Suggesting this search to find a proper thread to ask for buying advices: https://xdaforums.com/?query=which phone should i buy

Top 30 phones running LineageOS w/ links to LOS wiki with specs & release date: LineageOS Downloads Stats, "Active Installs" & Top 30

***
[Galaxy S III Original Android Development] Noobkid77:
Easy get a Galaxy S5 SM-G900F look for a used one on eBay there are plenty
[Galaxy S III Original Android Development] dc_01:
i9300: no WLAN link to router with 14.1

hi there, please allow me to report my issue since i have applied lineage-14.1-20180301-nightly-i9300-signed on my wife's S3 i9300:

I am not able to connect to my fritzbox 7490 router.

what i have alredy done:

1.) used the search function for several forums -> did not find anything that solved my problem

2.) reinstalled 14.1 after full wipe -> no change, still cannot connect to FritzBox

3.) restarted fritzbox -> no change

4.) modified wlan pwd to avoid special characters such as §$ and so on -> no change

5.) deleted old MAC entries in the fritzbox -> no change

6.) flight mode on / off - > no change

i applied Lineage OS on my N9005 and T705 without any issue and everything works well, so i do not understand why the S3 i9300

does not cooperate.

i am thankful for any help you may provide. thx and have a nice day
[Galaxy S III Original Android Development] Simon_29:
What is the exact issue? What error do you get when you are connecting?

Is the device freezing when it is Connecting to the router? Then you have to give your S3 a static ip in the wifi settings of your S3.
[Galaxy S III Original Android Development] dc_01:
hallo simon,

there is indeed no error message, when i enter the WLAN pwd of my fritzbox and press "connect" then the S3 does not connect to the fritzbox but only shows "network saved".

sometimes "authenticating" shows up, but nothing more. Usually as for the other devices i expect to see "connected"

in the meantime i checkes some other forums such as "android-hilfe" and applied the boeffla kernel to the LOS14.1 but so far no change, i still do not get a WLAN connection.

as stated before, the N9005 Galaxy Note3 and the SM-T705 both with LOS14.1 do not have any issue with WLAN.

thx

edit: did another test, setup my Note4 as mobile hotspot, the S3 connected quickly without any issue. seems the root cause is the fritzbox :(
[Galaxy S III Original Android Development] Simon_29:
Ok weird... Are you able to connect to other wifis like a hotspot or is it just this one special case?
[Galaxy S III Original Android Development] dc_01:
yes, could connect to a mobile hotspot of my Note4. it is really strange...

---------- Post added at 04:52 PM ---------- Previous post was at 04:49 PM ----------

some additional info: the fritzbox runs with a beta SW, there under WLAN - additional security settings -> disable PMF. now it works. thx Simon for the time you spent
[Galaxy S III Original Android Development] minealex2244:
Is there any ROM other than stock which is passing SafetyNet check? If not then I'll move to stock 4.3.
[Galaxy S III Original Android Development] acroreiser:
Any nougat with Koffee.
[Galaxy S III Original Android Development] concerned_user:
So what you're saying is that you're abandoning the project? RIP Galaxy S3 I guess.:crying:
[Galaxy S III Original Android Development] curiousrom:
S3 i9300 LineageOS Passing SafetyNet Check?

The S3 i9300 LineageOS 14.1 100% stock with or without root will not pass a SafetyNet check (SafetyNet check apps).

Did you try with SuperSU and suhide? Or with Magisk + either Boeffla-Kernel or KERNEL 7.X i9300 Koffee or Hybrid Kernel i9300?

Official Lineage article: SafetyNet: What it is, and how it affects you

XDA article: ...the SafetyNet bypassing is a cat and mouse game between Google and the community...

Edit: SafetyNet check is only needed for some banking apps, Google Pay, Netflix & some games requirement which I don't care for & prefer to stick with the stable stock Lineage 14.1 + Open Gapps ARM Pico + Lineage 14.1 ARM super user add-on I have been running for 6 months w/o any problems.

***

It's obvious for you what you are talking about but not for everybody as you did not even include the word kernel and the Magisk requirement. Why not save a link to your thread somewhere & cut-and-paste when posting about it or create a signature in your XDA Control Panel? Instead of having hundred of users running searches to find the thread.

Like this KERNEL 7.X i9300 Koffee. Just remove the spaces I added to break the link: [ URL="https://xdaforums.com/galaxy-s3/development/kernel-koffee-t3728423"]KERNEL 7.X i9300 Koffee[/URL ]

***

What are you talking about? The maintainer of the Official LineageOS for S3 i9300 is very active & there is currently more than 50,000 S3 i9300 phones running LineageOS. So no RIP Galaxy S3 at all on the horizon.

Maybe you miss this post just 2 pages back from yours: Bunch of Links: S3 i9300 LineageOS, Developer & Oreo Project

***
[Galaxy S III Original Android Development] minealex2244:
Nope, I just need SafetyNet to work ??? S3 won't be dead for me. If the phone is working then why to make it "dead"? :)
[Galaxy S III Original Android Development] Elton47:
Mine's pretty dead.

Edit: No photo editing involved.
[Galaxy S III Original Android Development] mountainguan:
Thanks for your links. I feel quite excited about the new linux kernel for i9300. It's really amazed me. Simon looks like a superman:fingers-crossed:
[Galaxy S III Original Android Development] curiousrom:
Ugly Battery Usage Graph - LineageOS 14.1?

"No photo editing involved." - Lol, it seems that no stock Official LineageOS 14.1 for S3 i9300 involved either. Here are screenshots side-by-side of > Settings > Battery done on my S3 running 100% stock LOS 14.1 vs. yours. What does that trash can icon do? Does it wipe the battery usage stats? The broken graph line normally indicates that the phone was off. Did you turned it off or did it do it by itself?

Since you did not include any troubleshooting info like which version of LineageOS are you running exactly, did you add Open GApps (date, variant?) and/or LOS addon su or SuperSU or Magisk (+modules?) and/or custom kernel or other mods I can only suggest:

Turn off phone and place the battery on a flat surface to check on both sides if there is a bulge, a symptom of dying battery which may cause intermittent lost of contact with the phone.

Check BetterBatteryStats free XDA edition thread > read the If you need help chapter for the proper troubleshooting setup & get the most recent apk in post #2.

After doing a full backup w/ TWRP including a crucial EFS Partition backup, backing up your apps & their data with Titanium Backup for example and backing up your personal data from internal sdcard do a super clean install of LineageOS w/ Format Data & wipe as described in this guide (including reboot in Recovery before installing any OS) and install only these 2 apps: Dummy file Generator & Trimmer (requires root) & run 4 times each while you have maximum free memory as described in S3 Black Screen Freezing Fix - Sudden Death Syndrome. After that you can install your apps & customize your setup.

*****

Thanks for the Thanks :good: and yes it's quite incredible the amount of stuff he does. And that's not including all the LineageOS Open patch code submission by other devs that he reviews for which I don't know how to list in a search so far.

BTW if you could edit your post & trim the quote a little bit that would be nice:

Guys, why quote over and over full long posts? You can just delete some content between
[Galaxy S III Original Android Development] LuciferIII:
I take it all back, i am disappointed on P.

Let's have a perfect Oreo build.
[Galaxy S III Original Android Development] Elton47:
It is not battery's fault. I have 3 original batteries. It's something wrong with how the display is being powered. At the moment when I want to turn the screen on, it flashes full green and I have to push the button many times until the screen turns on. The trash icon just resets the battery stats. The phone was off by itself during the empty graph stage. Also the ROM is RR, I just posted it here because the"dead" word was in topic recently.

Though, thank you for the help, but there is no way to fix the phone, atm I am using it for the last time to reply your post. I will continue to follow these forums and I hope i9300 will get it's Oreo.

BTW: Android 9.0 is out!
[Galaxy S III Original Android Development] curiousrom:
S3 Green Screen First & Hard to Turn On

Just curious:

1- Same if you use the Home button to wake up or enable > Settings > Buttons > Volume buttons > Wake device > toggle on?

2- You tried flashing stock Samsung 4.3 ROM & same result.

3- With the phone plugged to power adapter (not computer), same result?

3- You could try to disconnect/reconnect the digitizer cable (step 18) and the display data cable (step 19) from this iFixit Samsung Galaxy S III guide.

If you throw the towel, give it to somebody that can fix it or use some parts instead of hiding it in a drawer maybe?

Could you ship a spare battery to Costa Rica? ;)

***
[Galaxy S III Original Android Development] shoxyy:
I want to drag Google Nearby or the Nougat Eastern Egg Quicktoogle to my statusbar, but as soon as Im getting to the top (the active quicktoogles) it disappears :( am I doing something wrong?

*03-01 build, stock los kernel
[Galaxy S III Original Android Development] Elton47:
Same with everything, even bootloader logo.
[Galaxy S III Original Android Development] lyolic:
How long does it usually takes to wake up when you have incoming call?
[Galaxy S III Original Android Development] Ashraf Iraqian:
my phone took 3 - 5 sec to wakeup

using more than 100 apps installed :D
[Galaxy S III Original Android Development] Samofr:
How about 8-3-2018 build ?
[Galaxy S III Original Android Development] drakenborg:
I tested it yesterday.

The problem eliminated on my S3.

Thx.
[Galaxy S III Original Android Development] curiousrom:
Battery Drain & LineageOS 2018-03-08 Update? - In Call Wake Up Time

Glad you fixed your problem but there is only 2 minor changes in LineageOS 14.1 for S3 version 2018-03-08 and they do not concern the S3: https://download.lineageos.org/i9300/changes/

So I presume that flashing an older version & the new one just repaired or replaced some system file(s) or fixed some bad settings or wiping Dalvic / ART Cache and Cache solved the problem. Did you also update Open Gapps?

Anyway all is good now & that's what counts.

*****

Incoming Call Wake Up Time

Wake up & screen on takes 2.2 to 5 seconds after the phone starts ringing for my S3 LOS 14.1 using a stop watch and depending on settings & doze state: Wifi sleep if on battery, cellular data only or GSM, deep sleep or not & what other apps are requesting in the BroadcastQueue.

I checked in Logcat & there is an average additional .8 second between new incoming call and AsyncRingtonePlayer: Play ringtone.

Using the free MatLog: Material Logcat Reader (screenshot) > Settings > Clear > File > Record > and calling the S3 > then Stop > Send > Send Log as attachment (File > Save as works too) here is part of the trimmed Logcat (3.596 seconds) but that does not include the time it takes for the backlight to actually turn on & the time it takes for my brain to react to it:

03-08 15:34:12.915 I/Telecom ( 2386): : Adding new incoming call with phoneAccountHandle

03-08 15:34:13.833 I/Telecom ( 2386): AsyncRingtonePlayer: Play ringtone.

03-08 15:34:13.956 I/InCall (22080): InCallPresenter - Start Full Screen in call UI

03-08 15:34:14.132 I/InCall (22080): InCallPresenter - Phone switching state: NO_CALLS -> INCOMING

03-08 15:34:14.358 D/Ringtone( 2386): Successfully created local player

03-08 15:34:14.363 I/Telecom ( 2386): AsyncRingtonePlayer: Repeat ringtone.

03-08 15:34:15.173 I/InCall (22080): InCallPresenter - UI Initialized

03-08 15:34:15.174 I/InCall (22080): InCallPresenter - Phone switching state: INCOMING -> INCOMING

03-08 15:34:15.871 I/ActivityManager( 2386): Displayed com.android.dialer/com.android.incallui.InCallActivity: +1s21ms (total +1s31ms)

03-08 15:34:16.511 I/DisplayManagerService( 2386): Display device changed state: "Built-in Screen", ON

Total time it took: 16.511 - 12.915 = 3.596 seconds.

The same procedure with MatLog is great to troubleshoot some apps or the OS too.

***

BTW I added some links & reorganized this post a little: Bunch of Links: S3 i9300 LineageOS, Developer & Oreo Project

***
[Galaxy S III Original Android Development] Samofr:
Anyone stuck on patching system image unconditionally ? As i always do, clean dalvik, data, cache and system then install zip, but this build is getting stuck. I'm on twrp 3.2.1.0

This is the 1st time it happens to me since the 1st los was released. What's wrong ?

Update: After 4 times of downloading and flashing, it worked finally.
[Galaxy S III Original Android Development] curiousrom:
Stuck on patching system image unconditionally - Corrupted File?

Glad :) you fixed it & Thanks :good: for reporting back how you did it.

1- You don't need to wipe data when updating a previously installed same LOS 14.1 OS. Wiping Dalvic / ART Cache and Cache is a good thing but not obligatory when updating.

Was this a fresh install? Edit: yes it was as I just noticed ...clean dalvik, data, cache and system...". Oops! BTW a wipe Data is not as clean as Format Data as described in this this guide: How to wipe in TWRP properly? and rebooting in Recovery before installing LineageOS, Gapps and su addon if you wish. That's what I did for the initial LOS clean install on my S3.

2- Your downloads were probably corrupted & that's maybe why you solved it by "After 4 times of downloading and flashing, it worked finally". Or maybe the wipe was not perfect?

3- If you use > Settings > About phone > LineageOS updates to download & automatically install the update > the LineageOS Updater will check automatically the integrity of the downloaded update .zip file. (screenshot)

4- Next time to check the integrity of a downloaded file you can use a free app like Hash Calc (Checksum Utility) (screenshot) and: Select File > Hash function > SHA-256 > Browse to downloaded update .zip’s location & it will automatically calculate the Hash value.

Compare the result to the SHA-256 info link on the LineageOS download page. In this example from here for lineage-14.1-20180301-nightly-i9300-signed.zip : 2b8d04c692c158704b6de709867332d3d4314ca6f5452a38eeeebb3683b7fdfa - just checking the last 6 letters/numbers is enough. Hash Calc is a small app & does not have any background services nor require any special permissions except access to files.

You can also enable the Lineage built-in Terminal Emulator app in Developer options & navigate to your download location & use the command sha256sum lineage-the_Exact_name_of_your_file.zip but the app is faster IMO. Or on a computer to check the file downloaded on it.

If you still have one of the 3 update files you first downloaded maybe you could do a sha256 check on it?

***
[Galaxy S III Original Android Development] Gizmotech:
Apologies for my long absence. Anyway, I did revert back to Stock JB in December 2017 and can confirm the phone has been working flawlessly since. There does seem to be a bug in LineageOS for I9300 which seems to be affecting a small proportion of phones. For those who weren't following, the phone would go to some deep sleep and it was impossible to wake the phone back up. The only way around it was to reboot the phone. At one point it was unusable and I was having to reboot over 10 times a day.

I also confirmed that it was not an app causing the sleep issue as at one point I did have lineageOS running with no other apps installed and it was still going sleep and not waking up. It is now 3 months back on stock from LineageOS and can confirm it was never a hardware fault as many suggested.