yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] nobuteru:
Sure at 100%

but I had to bought original one for S3 i9300, as previously posted (2 -3 months ago)

I had one rear camera original that was "burned" with his original logic board, I bought used but tested 100% original logic board, but the rear camera sold with it, I discovered it was a replacement that was taken by Samsung galaxy n710 if i remember right

I had black screen with Lineage ROM, but 100% working with stock ROM.

I solved so, hope it can help you
[Galaxy S III Original Android Development] ackzsel:
Personally I wouldn't touch anything made or acquired by Cheetah Mobile with a ten foot pole. They are notorious for adding malware and advertizing in previously legit apps like ES file explorer. If you value your privacy and battery life I wouldn't go there.
[Galaxy S III Original Android Development] Robert-R:
Auto-update of my Play Store (configured as: via wifi only) doesn't work for me. Does anyone have this (minor) issue, also?
[Galaxy S III Original Android Development] Flegmon:
If you want a Good Browser with ad block try bromite ( https://www.bromite.org/ ) ( https://xdaforums.com/android/apps-games/app-bromite-chromium-plus-adblocking-t3687258 )

I didn't test it on the s3 yet
[Galaxy S III Original Android Development] r4Rok:
Just finished reading its XDA post, lots of issues were reported. No matter what, but CM browser has not given any issues so far.

---------- Post added at 05:17 PM ---------- Previous post was at 05:16 PM ----------

Was the burn due to this ROM?!!
[Galaxy S III Original Android Development] ArdaCsknn:
Don't think so.
[Galaxy S III Original Android Development] nobuteru:
No , it was my mom's smartphone, after 5 years of intense use, it "died"..., I changed logic board in recent month

My only problem with Lineage ROM was about rear camera
[Galaxy S III Original Android Development] r4Rok:
Does any one have original Samsung Boot Animation for this ROM?
[Galaxy S III Original Android Development] alexa10:
Motion camera

hi

camera app with slow/fast motion for this rom?
[Galaxy S III Original Android Development] youxiaojie:
waiting.....
[Galaxy S III Original Android Development] r4Rok:
Nice, you have done a lot. Now, will you suggest some BEST browser with ad blocking as well as faster browsing capabilities?
[Galaxy S III Original Android Development] 239:
Standalone:

Brave

Opera

Firefox (with uBlock Origin or AdGuard)

WebView:

Privacy Browser

Atlas Web Browser

Via Browser
[Galaxy S III Original Android Development] Psycho103:
Via Browser
[Galaxy S III Original Android Development] rekibor:
I'm quoting myself as my question was buried a bit :D

Can anyone help me there?

Cheers
[Galaxy S III Original Android Development] r4Rok:
<deleted>
[Galaxy S III Original Android Development] acroreiser:
You need to know better, how can be required removable components in your OS, before uninstalling.

For example, WebView required not only by browsers. Also WV is needed for some apps and can be replaced only by the Google Chrome browser. If app requesting WV and it removed, app will be crashed.

Next. DocumentsUI. Some apps requires access to an external storage. And asks path to extSdcard via... DocumentsUI! What will be happened in this case if DocumentsUI removed from system?

"Aaargh, it's not working! Again! Noooooooo....

...oooooooooo! Why i do this stupid debloating???"

Epilogue:

So, please, de-blo-a-ter, do a debloating on your {already bloated by CM} phone without disinformation.
[Galaxy S III Original Android Development] zarere:
I did dirty install and only flashed the attached file,after reboot the sound is working again.I've never tested with audiofx settings.I'm using the default root that is coming with lineage os.
[Galaxy S III Original Android Development] Robert-R:
I noticed that with Fastest Mini Browser some websites didn't function properly: search-fields on some sites didn't respond, so this browser needs an update in order to become competitive.:o

At the moment I am lucky with Brave and Via .:good:
[Galaxy S III Original Android Development] r4Rok:
Following issues are noted when the device restarts:

With 2018-02-14 -->> Calculator has a MTP stop error

And, now with 2018-02-21 -->> Calendar has a MTP stop error
[Galaxy S III Original Android Development] curiousrom:
MTP Host as stopped - Again!

Currently linked in my signature ;) MTP Host as stopped - Crashing Bug Workaround Fix S3 LineageOS

It's a known LineageOS 14.1 for S3 bug with an easy workaround & had been reported as described in that post.

It's better to be precise when reporting a bug or issue so if the error message is MTP Host as stopped then writing "MTP stop error" makes searching for a post or solution for it just more difficult.

***
[Galaxy S III Original Android Development] Ashraf Iraqian:
Hi

Thank you for giving your times to help all users

You know me of course i am old user here

and i know everything about "how to install custom Roms and i did what you said but not fixed this sound issue in call .

i am sure it is related to the ROM

regards :)
[Galaxy S III Original Android Development] pascua28:
I believe they rely heavily on webview. You might want to download google webview 64. Unless they strip websites through compression
[Galaxy S III Original Android Development] curiousrom:
Webview Updated to 64 in LineageOS 2018-02-14

Fastest Mini Browser (shown as Browser in > System > Apps like the stock LOS one but w/ a different icon) , Via Browser, LOS stock Jelly Browser 7.1.2 & several others are using the same Chromium open source project's >>> Android WebView included in the LineageOS 14.1 for S3 package as their rendering engine.

That's one of the reasons why they are so small (4-10 MB usually) when you look in Apps compared to (w/o cache & data) Chrome 64 (74.4 MB), Edge 1.0.0.1 (129 MB), FireFox 58 (53.55 MB), Opera 45 (70.7 MB), Opera Mini 32 (19.84 MB), Puffin 7.06 (34.7 MB), Samsung Internet Beta 6.4.1 (129 MB), UC Browser 12 (98.4 MB) and others that include their own web browser engine & more features (and some may add: bloat).

In the LineageOS update 2018-02-21 > Changes https://download.lineageos.org/i9300/changes/ you can see Update webviews (sic) to Chromium 64.0.3282.137. So all the following LOS builds will have it until WebView 64 is updated again. Screenshots of the new Show changelog link added to the Settings > About phone > LineageOS Updates panel and the webpage it opens in the browser of your choice:

That Android System WebView has currently the same version number as the up-to-date Chrome browser 64.0.3282.137 I downloaded from Play Store on S3 LOS 14.1.

I checked the stock LineageOS Jelly Browser 7.1.2 & other browsers before (WebView 63) and after the update (64) to confirm it by visiting the http://html5test.com test. (The screenshot shows Chromium WebView 64 reported by HTML5test.)

So it's not necessary to "download google webview 64" if you update LineageOS. If you don't want to update LOS then you can get the LOS webview.apk 64.0.3282.137 compatible with the S3 here: LineageOS/android_external_chromium-webview /prebuilt/arm/

In this Chromium Projects How-to page it says you must uninstall the existing version before installing the new webview.apk via ADB. There is this in the Play Store: Android System WebView, never tried it & I rather sit back and let LineageOS do the update work OTA.

Screenshots of > Settings > Apps > 3 dots > Show System > Android System WebView and > Settings > Developer options > WebView implementation:

BTW Fastest Mini Browser, Via, CM Browser & others are Trojan Horses sending your data to some big Chinese internet giants in Beijing. :eek: I am currently testing several browsers with DNS requests trackers running in the background & will report back in a day or 3.

***
[Galaxy S III Original Android Development] Mad-Marty:
Any chance, that in-call volume control will be fixed in the next release(s) ?

Some flash-fix from unknown sources or unknown date is not that great ....
[Galaxy S III Original Android Development] ugurkayaoglu5@gmail.com:
I have solved this problem using cwm

twrp gives this error
[Galaxy S III Original Android Development] Ashraf Iraqian:
https://xdaforums.com/galaxy-s3/orig-development/official-lineageos-14-1-i9300-t3544531/post75332032

About Custom Recovery: TWRP recovery is Recommended to flash Lineage.
[Galaxy S III Original Android Development] crisis_trustee:
Wait official lineage-15.1 for i9300.
[Galaxy S III Original Android Development] pascua28:
He's already working on getting the mainline kernel to work. We'll be getting a Linux 4.15 kernel for our devices soon. The kernel only works on a framebuffer console as of now.
[Galaxy S III Original Android Development] dana.marivani:
One of the most fundamental problems we have is the problem HWC is,

Hope this problem lineage-15.1 Resolved
[Galaxy S III Original Android Development] curiousrom:
In-call Volume Too High #2 - Best Recovery for LineageOS?

Thanks for the Thanks :good: . The XDA community taught me most of what I know about custom ROMs & the S3 so it's nice to give back a little & I like troubleshooting & fixing stuff. Besides maybe one day it will be possible to exchange all those Thanks for some Bitcoins lol.

***

In-call Volume Too High?

I updated the post In-call Volume Too High after tracking the origin of the Fix_sound_s.zip flashable file. It is for "...fix for volume incall control if not working".

You did not describe your problem. Is it the volume buttons not changing the volume level at all when making a call or not lowering it enough? You did not respond to any of the questions in the Troubleshooting info? of that post so trying to make fix suggestions is difficult.

"i am sure it is related to the ROM" - Well in-call volume adjustment & minimum/max volume is working fine using the earpiece, headset or speakerphone on my S3 i9300 running Lineage 14.1 updated to 2018-02-21, gapps nano 2018-02-07, addonsu-14.1-arm, root, no custom kernel & no mods. So maybe we have different hardware versions. If you have root, open this file with a text editor about the Wifi chip ID: /data/.cid.info. Mine says semcosh (from Samsung Electro-Mechanics CO.) other hardware versions say murata.

Or we have different apps installed that may affect the volume. To rule that out: > Long press Power button > long press either Power off or Restart > Reboot to safe mode. If the problem is solved when making a call then it's an app you installed.

***

Bug Fixed in next Build?

"...will be fixed in the next release(s) ? - Chances are about zero if bugs/issues are not reported following the Reporting bugs guidelines of the post #1 of this thread. Besides so far only 3 people reported an in-call volume related problem in this thread during the last couple of months.

And you did not describe your problem. See above.

"Some flash-fix from unknown sources or unknown date..." - That's what happens with sloppy posting. Attaching a file one downloaded to a post without any link to the original post gives zero info. After research I updated the post. See link above.

*****

Best Custom Recovery for i9300 running LineageOS

"TWRP recovery is Recommended to flash Lineage" - That's correct and you need an up-to-date TWRP (the bloated data tracking TWRP app is not required or can be uninstalled after flashing the recovery) as you can get Unknown command errors when installing LineageOS with old TWRP versions or other deprecated recovery as reported by [MENTION=8854590]NewbieToo[/MENTION] in his post here. See his screen capture: View attachment 4388516

Also if you want the automatic LineageOS OTA updater installer to work as per post #1 and shown in this screenshot of Settings > About phone > LineageOS updates. The updater is using the OpenRecoveryScript compatibility feature of TWRP to apply the update as illustrated by the second screenshot.

***
[Galaxy S III Original Android Development] Sobhan Mazaheri:
;)

---------- Post added at 05:54 AM ---------- Previous post was at 05:49 AM ----------

I hope.
[Galaxy S III Original Android Development] Sobhan Mazaheri:
It's likely that the lineage os 15.1 will be released in March for the GT i9300 ?:confused:
[Galaxy S III Original Android Development] ArdaCsknn:
Simon still didn't give any info.But I'm sure it wont come in March.
[Galaxy S III Original Android Development] sidelong:
TWRP 3.2.1-0-i9300

I have just installed the latest LineageOS 14.1 nightly using already installed TWRP 3.0.2-1, after doing a factory reset. This was successful and I booted into system and did the initial setup as normal. I then installed the official TWRP app to install the latest TWRP for the i9300, which is 3.2.1-0. as soon as this completed the green android screen with "Downloadng... Do not turn off target!!", as is the case when booting into Download mode, came up. I cannot now boot into Androidbecause this happens every time, no matter what I do. As far as I know I did nothing other than follow the instructions, and I am not a novice at this.

I have been trying to get Heimdall to work on my w10 PC, but so far without success. I have searched this thread, but nothing comes up that comes close to my experience.

Any ideas as to what might have gone wrong, and what to do about it?
[Galaxy S III Original Android Development] rekibor:
Hi,

sorry for the late reply.

I did a clean flash, have no gAPPs and no add ons runing and am using Lineage OS 14.1 nightly from 20180214. Audio FX app did not helped and somehow I am too stupid to use Root. When I activate in developer options I can only select ADB root and nothing else and ES file explorer wont accept root while Root Browser does not show any content at all.

Another thing to be added is that if I use the volume controls during a call I cannot set the volume bar to outermost left (zero position). It stops and has still like 1/8 of the way to go. I can also not put it through the touchscreen to zero position. It looks a bit like on this picture
[Galaxy S III Original Android Development] Mad-Marty:
Hi,

yes i should have been a lot more precise. Thanks for reminding me, just got the impression everyone knows about that bug, because the other guy asked about it too.

- Nothing on the side of custom kernel flashed

- upgrading from i think it was 2017-12-21ish, therefore no clean install

- gapps nano was installed

- LOS su addon flashed

- nothing special modded like Xposed or something like that, just normal apps installed

- tried the suggestion to enable-reboot-disable-reboot audiofx, didn't change anything

Description:

In call Volume change does not work, pressing volume up/down moves the slider but the volume stays like before the call.

If you change the volume before the call, whatever you choose, this will be the volume you are stuck with during the call.

However, if you switch to speaker mode, changing the in-call volume works correctly, e.g. the slider moves and the actual volumen in/de-creases.

So it just doesn't work with the "normal mode".

Hope this is better?
[Galaxy S III Original Android Development] Ashraf Iraqian:
About battery drain

i am installed BBS an hour ago and i checked "process" then i saw file name "surfaceflinger" draing my battery, i googled it and i found info about it and about "hwc"

maybe it will give good explain to everyone don't know what is hwc and surfaceflinger.

http://pierrchen.blogspot.jp/2014/02/what-is-surfaceflinger-in-android.html?m=1
[Galaxy S III Original Android Development] itachi uchia:
Install TWRP with Odin

1 At first download and run Odin3-v3.0.7.

2 Shutdown your phone and connect it to your PC (you should see "ID:COM" in colour).

3 Choose in PDA the twrp 3.2.1-0 "tar" file and click start. Done.
[Galaxy S III Original Android Development] rekibor:
Hi its me again :D

I'm going to answer the questions now as they are in your message.

I am now on Lineage OS 14.1-20180301-NIGHTLY-i9300 and did update from a clean flash of 14.1 (two or three nightlies earlier). I have not installed gapps or any addons. I installed SuperSU however.

Yes, it does not lower enough and the volume bar is not going to the outermost left but stuck a bit before the "zero position on the outermost left". I tried AudioFX but it did not change anything.

With headset it is completely fine! Problem with the volume bar still exists.

Haven't tried this yet.

Tried this, did not help.

Maybe the volume bar problem is an indication for whats wrong with my setup?

Cheers,

rekibor
[Galaxy S III Original Android Development] yoahmad1995:
This is XDA.

Its not a dating site or some social network communication. ?
[Galaxy S III Original Android Development] Sobhan Mazaheri:
yes, you're right. i'm new to the apologies
[Galaxy S III Original Android Development] Ashraf Iraqian:
Just flash the Sound Fix zip file in twrp and it will fix this issue.

Thanks for [MENTION=4273480]kosmasgr[/MENTION] & [MENTION=4122877]curiousrom[/MENTION] :svetius:
[Galaxy S III Original Android Development] rekibor:
Flashed it, did help a little bit but output is till quite loud and I still can't set the volume to 0.

Any other suggestions?

Cheers
[Galaxy S III Original Android Development] multiwirth:
kernel version 4.15 ? wow...

That would be more up to date than my tablet and my current phone which will receive lineageos 15.1 aswell.
[Galaxy S III Original Android Development] dana.marivani:
Another solution try it too:fingers-crossed:

View attachment ViPER4Android_FX_v2505.zip

https://xdaforums.com/showthread.php?t=2191223
[Galaxy S III Original Android Development] Ashraf Iraqian:
you want to make Volume in-call ZERO...!

Ooops
[Galaxy S III Original Android Development] pascua28:
Yes. You can take a look here: https://github.com/fourkbomb/linux
[Galaxy S III Original Android Development] rekibor:
Ah no, sorry for the misunderstanding. I meant that it is still not possible to set the volume control slider to the outermost left position (lowest volume position). This might indicate a problem with the controls right?

---------- Post added at 08:29 PM ---------- Previous post was at 08:23 PM ----------

This unfortunately fails to install cause some files are missing.
[Galaxy S III Original Android Development] drakenborg:
Hi,

after the latest 20180301 update, my phone battery drain faster than before. After 2 hours without usage was 30%. I put back the 20180221 ROM, and after 2 hours there was only 12%.

I using ROM stock kernel on my GT-9300.
[Galaxy S III Original Android Development] Nypan sr:
Same here.
[Galaxy S III Original Android Development] orgert:
the solutionn ive found is to turn of wifi , or set it to keep wifi of during sleep , this has helped me alot with batery drain
[Galaxy S III Original Android Development] curiousrom:
In-call Volume Too High #3 & Fix?

"...if I use the volume controls during a call I cannot set the volume bar to outermost left (zero position)" - That is the normal behavior for in-call earpiece, earbuds & speakerphone volume adjustment using the Volume rocker button or your finger to try to move the slider lower . I checked on a Galaxy S5 Mini G800H running stock Samsung Android 6.0.1 rooted & my S3 14.1 LineageOS stock and made these screenshots:

I managed to lower the in-call earpiece volume by editing the m0 file of my S3 running LineageOS 14.1 & created some Recovery flashable .zip files! Check the edited In-call Volume Too High post.

...Root. When I activate in developer options I can only select ADB root and nothing else... - Did you manage to fix that? You said in an other post "I installed SuperSU" instead of the LineageOS addonsu-14.1-arm-signed.zip, right? If so did you install the SuperSU app? BTW you can enable Pro in the settings of it w/o paying. It will nag you but it will work anyway as tried on a S5 Mini. Note that the app does NOT work with the LOS su addon.

Thanks :good: for the extra troubleshooting info.

"If you change the volume before the call, whatever you choose, this will be the volume you are stuck with during the call..." - How can you "change the volume before the call" as that option is not available in stock LineageOS 14.1 for S3 > Settings > Sound but only when making a call?

I can't explain why you guys have in-call volume problems & I don't but maybe we have different hardware versions. If you have root, open this file with a text editor about the Wifi chip ID: /data/.cid.info. Mine says semcosh (from Samsung Electro-Mechanics CO.) other hardware versions say murata.

Or try the free app WiFi Chipset INFO. And disable Keep awake in Privacy Guard for it or uninstall after getting the info.

A troubleshooting step: Long press Power button > long press either Power off or Restart > Reboot to safe mode. If the problem is solved then it's an app you installed.

Try the Fix_sound_s.zip linked in the updated In-call Volume Too High post. I added some how to reverse that change info & a Recovery flashable .zip to return to stock.

And as always: please report back to say if you fixed your problem or not for the benefit of the next user w/ a similar problem. :cool:

Thanks :good: for the feedback. :cool:

***
[Galaxy S III Original Android Development] curiousrom:
LineageOS 14.1 Update S3 i9300 - Battery Usage

Well guys on my S3 i9300 LineageOS14.1 2018-03-01, OpenGapps Nano 2018-03-01 & addonsu-14.1-arm for 2h 10 min. battery usage is only 3% as shown in this BetterBatteryStats screenshot and that is on cellular data, WhatsApp checking for notifications & 168 apps installed currently.

Long press Power button > long press either Power off or Restart > Reboot to Safe Mode. If the battery usage problem is solved then it's apps you installed or your settings.

Instead of going back to an older LineageOS version check S3 Lineage Battery Drain Troubleshooting & Optimization for suggestions.

You are not suppose to use your phone if you want to troubleshoot with BBS as it introduces too many variables. It is useful to see what your phone is doing behind your back or when it is supposed to sleep, just like naughty kids.

Check BetterBatteryStats free XDA edition thread > read the If you need help chapter for the proper troubleshooting setup.

Yes > Settings > Wireless & networks > Wi-Fi > gear (cog) > Configure Wi-Fi > Keep Wi-Fi on during sleep > Only when plugged in can help a lot, especially if you have a bunch of apps with permission to call home in the background when on Wifi, Play Store checking for updates & downloading apps updates that can be huge, etc. Check post linked above for more solutions.

***
[Galaxy S III Original Android Development] Mad-Marty:
Oops, your right, its just the ring tone volume when no call is running.

checked the .cid.info via cat and it says semcosh.

Flashed the fix (Fix_sound_s.zip), and it works, sliders move and the volume dec/inc correctly as one would expect.

Thanks

So yeah, the fix works, now it realle should be merged into the sources, right?
[Galaxy S III Original Android Development] walter79:
Maybe this work for MTP crashing on i9300 too.

Check this: https://github.com/walter79/android...b/cm-14.1/patch/note-8-nougat-mtp-crash.patch

Works for n5100,n5110,n5120 and i9305.