yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] curiousrom:
Re: LineageOS 14.1 for S3 i9300 Mirrors?

There is no need to upload LineageOS 14.1 for S3 i9300 and split it in 3 parts.

Search for mirror in Bunch of Links: S3 i9300 LineageOS, Developer & Oreo Project and go to official LineageOS mirrors:

https://www.cmxlog.com/14.1/i9300/ or Problem with Lineage Download 502 Bad Gateway & Mirrors

which includes Lineage websites status link.

This said https://download.lineageos.org/i9300 works fine for me @ the present.

***
[Galaxy S III Original Android Development] shahamk34:
You can get in to that menu through phone info app- secret codes-0228
[Galaxy S III Original Android Development] curiousrom:
Fake Samsung S3 Battery

It seems that you bought a third-party battery disguised as a Samsung because the weight is the only external difference between my original Samsung S3 battery & the fake one bought in a small shop that is a 4 hour drive round trip from my house so that's why I did not return it. I don't have access to a precision scale @ the present, just grams & no decimals. OEM 38g, fake 33g and a third-party Bastex bought recently 36g as seen in the screenshots.

After using the fake battery I was not happy because it was not lasting any longer than my 4 year old OEM and only after removing it & comparing to the OEM did I realize that it was noticeably lighter. So if you buy from a small shop bring the original to compare the weight using the same hand if a scale is not available.

Funny enough the Bastex is printed upside-down, says CELL MADE IN CHIAN instead of China and there is no production date but at least it does not pretend to be a Samsung. My guesstimate is a capacity of 1900~2000 mAh using the estimated data from Settings > Battery but I don't know how long it will last so I can't recommend it @ the present.

Using the Phone INFO Samsung > Secret Code as [MENTION=9064127]shahamk34[/MENTION] mentioned above, code 0228 is pretty useless and does not show any real differences besides small voltage variance between the OEM & Bastex when both charged 100% while my old OEM has a capacity of 1500mAh @ best.

Note that if you keep on charging for at least 30 minutes after the battery shows 100% you may reach the maximum 4.35v (4350mV or 4349mV in my case) but voltage only does not say anything about the ampere/hour that the battery can give and the real power output capacity.

There are plenty of posts about counterfeit S3 Samsung batteries and looks & stickers does not mean much like in https://xdaforums.com/galaxy-s3/accessories/counterfeit-samsung-batteries-t1902391 and this guy pushed it to the extreme but still got conned on Fleabay:

http://goughlui.com/2014/03/21/genuinely-fake-pt-3-samsung-galaxy-siii-batteries-eb-l1g6llu/

http://goughlui.com/2015/04/13/genuinely-confused-another-samsung-galaxy-siii-battery-eb-l1g6llu/

BTW I used that Phone INFO app & code 0011 to check cellular data & posted 2 screenshots about it here: Modems: New Zealand + Latin America & Secret Codes.

Hey be polite! FYI I am a certified Google Search Ninja as I went to the week-end Google Search Jungle Camp right here in Costa Rica. ;)

***
[Galaxy S III Original Android Development] Sobhan Mazaheri:
Lineage os 16

Hey guys

In your opinion,19300 supports lineageos16?:confused:
[Galaxy S III Original Android Development] multiwirth:
No

14.1 is hard on it´s limits, if 15.1 will ever boot on it, it wouldn´t be better and Android P will probably never land on the Galaxy S3.

This is like porting CM11 to a Samsung Galaxy Ace with features a 832Mhz armv6 Single Core CPU, 256MB RAM and 512MB rom.

AND this was already done and it´s unuseable.

The 1GB ram of the Galaxy S3 is the biggest bottleneck.

Maybe we can get Android Go which is designed for such low end hardware
[Galaxy S III Original Android Development] Psycho103:
I also have lost hope of getting Oreo on this device now.

We used to say "Long Live S3"

Maybe it will soon change to "RIP S3"

As most of the active devs are losing their device.
[Galaxy S III Original Android Development] TheRuan:
They made it work for S2, Android GO version could work just fine, there just isn't enough people wanting this, so i highly doubt we will ever get another update.
[Galaxy S III Original Android Development] multiwirth:
Android go would be the only option which makes sense on this device in the future and for future updates.

Even 2gb ram is not enough for today.
[Galaxy S III Original Android Development] ArdaCsknn:
While forkbomb still adding new commits noone can say Oreo not coming to S3. I still have hopes for S3.
[Galaxy S III Original Android Development] Nypan sr:
This thread is about LineageOS, there is plenty of batteryproblems discussed here: https://xdaforums.com/galaxy-s3/accessories
[Galaxy S III Original Android Development] ZjemCiKolege:
https://xdaforums.com/galaxy-s2/development-derivatives/rom-lineageos-15-0-t3674567 ;)
[Galaxy S III Original Android Development] Ashraf Iraqian:
Hi Mr. [MENTION=5405215]forkbomb444[/MENTION]

Can you please fix the Screen Recorder issue in the next update , when i am recording the screen and finishing my project The app won't stop!

And the result is "can't play this video".

Note: i got this issue in Almost official lineage 14.1 ROM versions

Thanks in Advance :)
[Galaxy S III Original Android Development] curiousrom:
Screen Recorder & Speaker Volume Boost

"...Screen Recorder issue... in Almost official lineage 14.1 ROM versions... - Define "almost". ;)

The LineageOS built-in Recorder > Record screen works fine on my 100% stock Official Lineage 14.1 running on S3 i9300 (currently 2018-08-03) + Open Gapps ARM Pico + Lineage ARM super user add-on.

If when tapping on notification > Screen Recorder > Stop does not work then tap on the Screen Recorder above it to open the main window of the Record screen and tap on the square button to stop it as seen in these screenshots.

Here is a S3 Lineage 14.1 screen recording I made using the stock Music app with the speaker volume set to the maximum after applying the S3 Boosting Speaker Volume - TWRP Flashable Zip modification.

Naturally Screen Recorder is using the microphone so it's not as loud & clear as the actual music I am hearing trough the S3's speaker. You can see @ 37 seconds that the Stop was not visible because of the space Music was taking in notifications so I stopped the recording using the method described above.

The sound hiccup @ 3 seconds is from Youtube's video processing because the original screen recording does not have it. I also made a screen recording before applying the S3 speaker volume boost mod and the difference is obvious when comparing both recordings but once uploaded to YouTube it's volume equalizing algo is erasing the differences so it's no use to post it here.

[YOUTUBE]xwqIUKcHWzU[/YOUTUBE]

"...@ forkbomb444 Can you please fix the Screen Recorder issue in the next update..." - It is no use to bother the S3 LineageOS maintainer with a @ mention ping because see the post #1 in this thread > Reporting bugs chapter for the proper way to report a bug.

***

BTW I did not update to lineage-14.1-20180809-nightly-i9300 because there is exactly zero changes compared to the 2018-08-03 I am currently running as seen in https://download.lineageos.org/i9300/changes/ The two files are exactly the same size.

***
[Galaxy S III Original Android Development] 1is7ac3:
I have no problems, verify that the app has all the permissions, forced stop and try again.
[Galaxy S III Original Android Development] curiousrom:
Screen Recorder Landscape Mode

Lineage's Screen Recorder works fine for me in landscape mode and that was while watching a video using the YouTube app as seen in the screenshot.

Have you tried as described in the post above? And you still did not describe your system setup (custom kernel if any, Xposed + modules & what not system modifications, etc.) so it makes it very difficult to make troubleshooting suggestions.

***
[Galaxy S III Original Android Development] Ashraf Iraqian:
with or without boeffla kernel i have the issue.

AZ Screen Recorder just works fine.
[Galaxy S III Original Android Development] XDA@AndroidGeek:
[MENTION=5405215]forkbomb444[/MENTION] ,mostly thank you for your great efforts you & your team are putting on this project & for the great OS you are building. At the last builds, i'm afraid my antivirus that I installed on the OS of my phone, has detected the system app: com.android.wallpaperpicker, as infected system app. Again, thank you for your all great efforts, and check it please.
[Galaxy S III Original Android Development] fonfox:
Yes virus total did also detect

found Android.Trojan.Ransom.gTGSI (B)

But cant say if it is false positive
[Galaxy S III Original Android Development] fonfox:
Virus total result [MENTION=5405215]forkbomb444[/MENTION]
[Galaxy S III Original Android Development] Robert-R:
What is the exact date of the build which notified the infection?

Did you do this virusscan also on a previous build?
[Galaxy S III Original Android Development] 239:
False positive: Android.Trojan.Ransom.gTGSI

WallpaperPicker.apk

13 / 60

Ad-Aware	Android.Trojan.Ransom.gTGSI	20180820

Arcabit	Android.Trojan.Ransom.gTGSI	20180820

BitDefender	Android.Trojan.Ransom.gTGSI	20180820

CAT-QuickHeal	Android.Ransom.Ab434 (PUP)	20180819

Emsisoft	Android.Trojan.Ransom.gTGSI (B)	20180820

F-Secure	Android.Trojan.Ransom.gTGSI	20180820

GData	Android.Trojan.Ransom.gTGSI	20180820

Ikarus	Trojan.AndroidOS.Ransom	20180820

MAX	malware (ai score=87)	20180820

McAfee	Artemis!349DAB990592	20180820

eScan	Android.Trojan.Ransom.gTGSI	20180820

Symantec Mobile Insight	AdLibrary:Generisk	20180814

TrendMicro-HouseCall	Suspicious_GEN.F47V0814	20180820

classes.dex (extracted from WallpaperPicker.apk)

1 / 60

CAT-QuickHeal	Android.Ransom.Ab434 (PUP)	20180820

classes.dex_source_from_JADX.zip (extracted Java source files)

0 / 60
[Galaxy S III Original Android Development] gabyzen:
???? antivirus
[Galaxy S III Original Android Development] bejunk:
only working antivirus is brain.exe

its easy peasy to change signature or size of an malware etc = will not be detected since many scanners (especially the online quick ones) work with hashes ... so if someone wants to hack you, antivirus app is useless.
[Galaxy S III Original Android Development] gabyzen:
Yep, in addition, some "antivirus" do nothing, just a random function for the estimating time and other function for the number of viruses
[Galaxy S III Original Android Development] curiousrom:
Update 2018-08-23 LineageOS Security Bump & WebView 67

FYI while the last 3 updates had nothing for the S3 i9300, the LineageOS 14.1 build 2018-08-23 has several worthwhile changes including a Android security patch level bump to 2018-08-05 & a Chromium WebView update (67.0.3396.87) which is used by the built-in Browser & several other browsers & apps. More info about the commits in https://download.lineageos.org/i9300/changes/

You can see the WebView version change in Settings > Apps > 3-dots select Show system > Android System WebView and also by going to html5test.com in Browser. (screenshots)

The OTA update went smoothly as usual for my S3 using the built-in Settings > About phone > LineageOS updates. I enabled the LineageOS Network Traffic Monitor to show the download speed in the status bar, 2.7 Mbps is the maximum internet download speed my network can achieve so it confirmed a good connection to the Lineage servers.

Thank you to the LineageOS Team & [MENTION=5405215]forkbomb444[/MENTION] (maintainer of the S3 i9300) for supporting our device. :good:

***
[Galaxy S III Original Android Development] Mano678:
Speaking of security, after updating my router (AVM Fritzbox) a few days ago i couldn't connect my I9300 via WLAN any longer.

Updated phone from an older LOS build to 2018-08-23 just for a try, but it didn't change anything.

Turned out the router update activated the PMF (protected management frames) feature, which causes the I9300 to connect, then drop the connection. All my other WLAN devices (including an old Android 4 tablet) didn't have a problem with that.

Found a closed jira entry related to that problem (BUGBASH-1184 on jira.lineageos.org , can't post links jet)

Disabling PMF in the router solved the problem for me, but it would be preferable if LOS could run with PMF on.

Any chance to get that fixed? From the jira post, it seems to be "only" a config setting, but i'm unsure if that setting could be applied to the I9300 as well.

Otherwise, i'm greatly pleased with LOS 14.1 on my S3. Keep up the good work!
[Galaxy S III Original Android Development] curiousrom:
Lineage Summer Survey 2 - Give Your Opinion!

There is just a couple of days left if you want to give your opinion on the firmware, apps, features & give thanks or cr@p to the LineageOS Team in the last question (open reply box) via the Summer Survey 2. :cool:

It's painless & takes just a couple of minutes. You can read the report of last year's survey here: Summer Survey - Results 2017

***

Bug Reporting - PMF & WiFi Problem

Thanks for reporting back your WiFi problem & workaround. :good:

Edit: Searching this thread with PMF I found this & it's with the same Fritzbox router brand:

***

"Any chance to get that fixed?..." - The only way to get a bug fixed is to do a proper bug report that includes a Logcat & other relevant info so a LineageOS developer can reproduce the problem & try to fix it. See the Reporting bugs chapter in the post #1 of this thread.

BTW you can capture easily & quickly a Logcat & other logs with the free SysLog (screenshot) if rooted instead of using adb + computer or Terminal as described in the How to capture logs in the Lineage Wiki.

I also like to use MatLog: Material Logcat Reader to check stuff on the fly & filter & export part of the Logcat. Logcat Extreme is pretty good too.

Here is a link to the bug report you were referring to but that's for an other device that is using the p2p_supplicant while the S3 i9300 is using the wpa_supplicant: BUGBASH-1184 WiFi - bcmdhd authenticates then disconnects from AP when 802.11w set to "Capable"

***

Edit: [MENTION=9023568]Mano678[/MENTION] reading what the bug reporter wrote if your S3 is rooted maybe you could try this:

1- On the S3 > Settings > Wi-Fi > with WiFi on, tap on your network's name and tap FORGET. Then disable Wi-Fi.

2- Using a root enabled editor like QuickEdit navigate to /system/etc/wifi/wpa_supplicant.conf, open it and replace 1 with 0 in this line: pmf=0, save & turn off the S3.

3- Enable the PMF (protected management frames) feature in your router.

4- Turn on the S3 & connect to your network & test the wifi connection by navigating in Browser for several minutes & maybe download some stuff.

5- If you can: try to connect to an other wifi network without the PMF feature (like one of your other device turned into a hotspot for example) to see if it's affected by the S3's pmf=0 modification.

Please report back if it works for you or not. :cool: Note that this mod will probably not survive a Lineage update but I could make a TWRP flashable zip with the fix if it works & the fix suggestion could be included in a new Bugbash report.

***
[Galaxy S III Original Android Development] Marc0601:
Oreo project status?
[Galaxy S III Original Android Development] Sobhan Mazaheri:
Oreooo?

Why does Mr. fourkbomb not report any oreo status?:confused::confused::confused:
[Galaxy S III Original Android Development] pascua28:
He's doing it. We should be thankful because our device even have nougat support even if Samsung abandoned it years ago. Our device has reached this far and thanks to developers who are constantly working
[Galaxy S III Original Android Development] ninohs:
Hi guys. After installing last build i am not able to activate root. I have flashed suaddon 15.1 but when i go to developper option the function to manage root app is disable. Could anyone help me? Thanks
[Galaxy S III Original Android Development] pandalov:
suaddon 15.1 For LOS 14.1 ?
[Galaxy S III Original Android Development] ninohs:
Yes bro
[Galaxy S III Original Android Development] Mano678:
Thanks for giving such specify instructions, unfortunately, the workaround didn't help - no change in the behaviour.

The different part in the logcat is:

PMF on:

08-26 17:03:28.768 3955 3955 I wpa_supplicant: wlan0: WPA: Key negotiation completed

08-26 17:03:28.768 3955 3955 I wpa_supplicant: wlan0: CTRL-EVENT-CONNECTED

08-26 17:03:28.774 3955 3955 W wpa_supplicant: wlan0: WPA: Failed to configure IGTK to the driver

08-26 17:03:28.775 3955 3955 I wpa_supplicant: wlan0: RSN: Failed to configure IGTK

08-26 17:03:28.796 3955 3955 I wpa_supplicant: wlan0: CTRL-EVENT-DISCONNECTED bssid=<my ssid> reason=1 locally_generated=1

...

08-26 17:03:28.914 2382 2470 D ConnectivityService: NetworkAgentInfo [WIFI () - 104] EVENT_NETWORK_INFO_CHANGED, going from CONNECTING to DISCONNECTED

vs

PMF off:

08-26 17:04:01.918 3955 3955 I wpa_supplicant: wlan0: WPA: Key negotiation completed

08-26 17:04:01.919 3955 3955 I wpa_supplicant: wlan0: CTRL-EVENT-CONNECTED

...

08-26 17:04:02.159 2382 2470 D ConnectivityService: NetworkAgentInfo [WIFI () - 107] EVENT_NETWORK_INFO_CHANGED, going from CONNECTING to CONNECTED
[Galaxy S III Original Android Development] ninohs:
How can i do this?
[Galaxy S III Original Android Development] kurtn:
Use 14.1 ARM
[Galaxy S III Original Android Development] curiousrom:
Wrong LineageOS super user addon for Root

Like [MENTION=8798528]pandalov[/MENTION] and [MENTION=8031265]kurtn[/MENTION] said above you need to install the su addon 14.1 arm to enable root if running LineageOS 14.1 on S3 i9300. Available here: https://download.lineageos.org/extras

You did not say which 15.1 su addon version you installed exactly but if you installed addonsu-15.1-arm-signed.zip then try flashing in TWRP Recovery addonsu-remove-15.1-arm-signed.zip, reboot to System and hopefully it will remove all the garbage. If you installed the arm64 or x86 version then try the corresponding removal tools.

Then back in TWRP recovery flash the proper addonsu-14.1-arm-signed.zip.

Then as described in S3 LineageOS Super Clean Install & Samsung Firmware:

To enable Root if you installed the Lineage super user 14.1 arm for S3 i9300 add-on:

1- Settings > About phone > click on Build number until a pop up saying "Developer options enabled" appears.

2- Back to > Settings > Developer options > Root access > enable Apps and ADB.

3- Done. Reboot the phone for good measure.

If it fails maybe you could consider doing a clean install as described in that post or reflash LineageOS + the proper su addon but that would not be my first choice for a trouble free fresh install.

Note that some S3 i9300 LineageOS 14.1 users prefer Magisk + a custom kernel for root but my S3 has been running trouble free for 9 months with the 100% stock LineageOS 14.1 updated almost every week via the built-in Lineage Updater + Open Gapps Pico + Lineage addonsu so I will stick to that.

Please report back if it worked for you or not. :cool:

***
[Galaxy S III Original Android Development] ninohs:
First of all thanks for your reply bro.

I have tried to flash suaddon 14.1 and it works fine. But i noticed that if i flash a costum kernel (i am usimg kofee) root is enable on developer options but it doesnt work on any app.

I dont know if i have to ask here or in koffe'sdiscussion (and i apologize myelf if i am wrong) how can use root with custom kernel?
[Galaxy S III Original Android Development] Ashraf Iraqian:
the best custom kernel for this ROM is Boeffla kernel

https://xdaforums.com/galaxy-s3/development/kernel-boeffla-kernel-2-2-stable-27-03-t2449408
[Galaxy S III Original Android Development] wadken1:
Stuck on Samsung Flash Screen

Until a few minutes ago I had a nice fully working LOS14.1 installation on my S3 - then, while reading this thread I saw that TWRP had been updated and decided to flash it. I downloaded the latest TWP image file and flashed it with the official TWRP app then tested by trying to reboot to recovery.

No good. All I get is the Samsung flash screen. I've also completely powered down by removing the battery and attempted a normal restart and "pwr+home+vol up" and I just get the same result i.e. can't get to recovery or normal rom boot. "pwr+home+vol dwn" gets me in to download mode so I can at least use Odin as a last resort.

I appreciate this may not strictly be the right thread but it's one of the very few active ones - any help / advice appreciated.

Cheers

EDIT: Additional information as per remarks in the next post by [MENTION=4122877]curiousrom[/MENTION] - hope it does help others avoid this problem but really I think the best advice is to never flash with the TWRP app - I know that I've problems like this before but some peculiar reason though that it out to have been fixed by now.

ROM: Lineage 14.1 2018-08-23, Kernel: Stock Lineage, Recovery: TWRP 3.2.3-0, SU: Magisk 16.7 with Cloudflare DNS mod, Gapps: Open Gapps ARM Nano, Xposed: No
[Galaxy S III Original Android Development] curiousrom:
Re: Stuck on Samsung Flash Screen - Bootloader & Bad TWRP Flash

Thanks :good: for the quite good problem description. It would better if you could edit your post & include the exact files versions as "the latest TWP image file" will not mean anything after the next update & "fully working LOS14.1 installation" says not much without build version, Gapps variant, rooted or not and is it with LineageOS addonsu or Magisk which modifies the boot image, Magisk modules & if you have a custom kernel or not.

That essential troubleshooting info may help other users to avoid your problem & may bring more relevant troubleshooting suggestions. :cool:

For example I am running 100% stock Official Lineage 14.1 on the S3 i9300 (currently 2018-08-23) + Open Gapps ARM Pico + Lineage ARM super user add-on and have the twrp-3.2.1-0-i9300 @ the present. No Magisk & no custom kernel.

***

The Samsung Flash Screen is the Samsung Bootloader's first step so it's a really bad problem. If the suggestions below does not work then you may have to install a stock Samsung firmware to try to fix it.

Since you can only boot your S3 i9300 in Download mode go here & download the most recent Odin: S3 LineageOS Super Clean Install & Samsung Firmware step #3.

Then using Odin flash the Most Recent S3 i9300 Bootloader: I9300XXUGPE1 and reboot to system.

If you are again stuck on the Samsung splash screen try to press the power button for 8-10 seconds until the screen turns black & release the button immediately which should turn off the S3 & is much better than removing the battery when stuck in a bootloop or bootloader which may cause all kinds of problems.

Then back in Download mode & using Odin flash the known to work without problems twrp-3.2.1-0-i9300.img.tar using exactly the instructions of the clean install post linked above.

If it still does not work install the stock Samsung firmware as described in the post & after making sure that all is OK in system flash TWRP using Odin as described, boot to Recovery, make a EFS partition backup, format Data & wipe as described & restore a LineageOS backup you made with TWRP.

If you don't have a backup do a clean LineageOS install as described in the post.

***

TWRP Official App

"...and flashed it with the official TWRP app" - That app is bad as it collects data & runs in the background all the time for no good reason. A TWRP.img downloaded or copied to sdcard can be flashed directly using Recovery if the S3 is running TWRP 2.8.4 or later.

Please report back if it worked for you or not & good luck!

***
[Galaxy S III Original Android Development] wadken1:
Many thanks for your comprehensive reply. I've adjusted my previous post as per your suggestion. The remedial steps you indicate are pretty much where I thought I was going to end up but you never know when someone may have found a short cut so had to ask - I'd already seen your extensive post on the subject while browsing today - looks great and will be a great help. Cheers