yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] ChronoMonochrome:
Not really necessarily. Having official status usually means a stricter policies about the introducing changes, which may or may not hurt stability / security. So usually that means an unofficial ROMs / kernels have some more freedom in this regard.

Whether the kernel / ROM is stable / secure or not is entirely dependent on the developer experience and skills. I am not saying whether official or unofficial is better, I believe both choices have its advantages and disadvantages.

Btw, we (me and Note 2 devs) are doing some work to make getting official status more feasible than now. Whilst it still may be not be possible for LOS 15.1 (at least as of now) due to still using some hacks in ROM sources, it maybe at least possible to get official status for other ROMs which have less strict policies about device specific hacks in the ROM sources. Can't say anything more specific because it's still work in progress, just that need in some device hacks was eliminated (but there are still a few that needs resolution).
[Galaxy S III Original Android Development] buaser:
Hi, I'm experiencing Screen of death, cant wake phone after a while of sleep, is there a fix?
[Galaxy S III Original Android Development] curiousrom:
S3 Black Screen Freezing Fix - Sudden Death Syndrome

S3 Black Screen Freezing Fix - Sudden Death Syndrome

Please report back if you fix your problem or not. :cool:

Good luck!

***
[Galaxy S III Original Android Development] buaser:
I do not have the faulty emmc, but tried this metod, no luck.
[Galaxy S III Original Android Development] curiousrom:
S3 Black Screen Freezing Fix - Sudden Death Syndrome

No setup description & no logs = can't help.

See post #1 of this thread > Reporting bugs & S3 LineageOS Super Clean Install & Samsung Firmware

***

Edit: [MENTION=5186426]buaser[/MENTION] - The reason I'm asking for your system setup is because without any troubleshooting info it's like calling a doctor & saying I'm sick & nothing else.

I use a .txt doc so I can copy/paste this without having to type it every time: I am running 100% stock Official Lineage 14.1 on the S3 i9300 (currently 2019-01-17) + Open Gapps ARM 7.1 Pico + LineageOS ARM 14.1 super user add-on (addonsu-14.1-arm-signed.zip for root) with twrp-3.2.3-0-i9300 @ the present. No custom kernel, Magisk, Substratum or system modifications of any kind.

I remembered Magisk users reporting that their S3 i9300 LineageOS 14.1 was going to sleep with no way to wake it up. The workarounds are:

Completely uninstall Magisk using Magisk Manager & use the LineageOS ARM 14.1 super user add-on: addonsu-14.1-arm-signed.zip for root then > Developer options > Root access > enable Apps and ADB.

Or keep Magisk & install a custom kernel like Boeffla-Kernel or Kernel Koffee or Hybrid Kernel i9300

***

If you reply please use a mention like [MENTION=5186426]buaser[/MENTION] or a partial quote like this so I can get notified:

***
[Galaxy S III Original Android Development] dark-ryuk:
volume less

Hello . The sound is less when you listen to music from the speakers. I haven't tried a few audio amplifier applications via google play but I didn't get the yield. How can I fix?

Thank you in advance for your interest.
[Galaxy S III Original Android Development] curiousrom:
Open GApps Downloads Down - Mirrors - Checking MD5

***

Edit: All builds of 9 February 2019 accessible @ the present: https://opengapps.org/

***

FYI the Open GApps downloads Repo is offline @ the present. For example: Open Gapps for S3 ARM 7.1 (for LineageOS 14.1).

The Open GApps Wiki & issues is up:

Open GApps Package Comparison

The downloads offline issue: Access to Repo #719

Edit 2: There is no official Open GApps downloads mirror @ the present but [MENTION=2010892]Nezorflame[/MENTION] backed up all Open GApps packages build 2019-02-09 to his server (including open_gapps-arm-7.1-pico-20190209.zip for LineageOS 14.1) here: https://builds.nezorfla.me/?dir=opengapps/ (click on "i" to get the MD5 & SHA1 hash).

Note that you can use older Open GApps packages (not too old!) & the apps & Play Store should update themselves after you log into your Google account.

***

How To Check the Integrity of your Downloads - MD5

You can use a Hash checker or Hash calculator to check the integrity of the downloaded file with MD5.

For example Hash Checker for Windows (screenshot) or Hash Calc (Checksum Utility) for Android.

BTW I had several corrupted downloads from Open GApps as seen in the second screenshot that Windows 10 reported as completed so I always check the MD5 to avoid installation errors & boot loops.

***
[Galaxy S III Original Android Development] inceptionlevel3:
does anybody have mirror link of 20181117 firmware....i installed the new 20190117 and its buggy....loses sim and battery drain is crazy...plz provide link if you have ...lineage os website removed all 2018 firmwares
[Galaxy S III Original Android Development] kurtn:
So you've done something wrong. How about factory reset or clean flash?
[Galaxy S III Original Android Development] inceptionlevel3:
i dunno...i just updated the lineage os like always from settings and update and this time the phone has been losing sim card and battery drain in crazy....after restarting the sim is detected....i also cleared the cache and dalvic still no solution

---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------

Junior Member

7*posts

Thanks: 0

*

i dunno...i just updated the lineage os like always from settings and update and this time the phone has been losing sim card and battery drain in crazy....after restarting the sim is detected....i also cleared the cache and dalvic still no solution
[Galaxy S III Original Android Development] denver04:
How are the chances for the .png image vulnerability fix to be included in the upcoming build?
[Galaxy S III Original Android Development] kurtn:
Yo
[Galaxy S III Original Android Development] eriol1:
I don't think that's it.

That's last month's ASB.

February ASB hasn't been merged yet to los 14.1

(as you can see, it's still marked as active on Gerrit)
[Galaxy S III Original Android Development] kurtn:
Oh s***t. Nougat is one month behind. So we have to check individual commit.
[Galaxy S III Original Android Development] curiousrom:
Bump Security String to 2019-02-05 - SIM & Battery Problem

LineageOS 14.1 is not one month behind. :)

Bump Security String to 2019-02-05 for 15.1 was merged yesterday: "Change has been successfully merged by Kevin Haggerty Feb 11 20:19".

So be patient. It's will probably be included in the next LineageOS 14.1 for i9300 which should be on Feb. 17 2019 if all goes well with the LineageOS automated firmware builder.

***

SIM & Battery Problem After Updating

You could try putting your SIM in a stock phone for 10 minutes & make a call. It could be a SIM provisioning from your network provider problem.

You did not describe your setup like if you installed Magisk + some modules, a custom kernel, Xposed or any other system modification.

I am running 100% stock Official Lineage 14.1 on the S3 i9300 (currently 2019-01-17) + Open Gapps ARM 7.1 Pico + Lineage ARM 14.1 super user add-on (addonsu-14.1-arm-signed.zip for root) with twrp-3.2.3-0-i9300 @ the present. No custom kernel, Magisk, Substratum or system modifications of any kind and did not have any problem using the LineageOS Updater. I copy/paste this from a .txt doc so I don't have to type it every time.

Check:

S3 i9300 LineageOS Super Clean Install & Samsung Firmware

S3 LineageOS 14.1 Battery Optimization including the #3 BetterBatteryStats part (screenshot).

EFS Partition Backup - No Service, No IMEI & No SIM Card Fix

What is your current modem/baseband? I attached the most recent S3 i9300 modem I9300XXUGOK1 (2015-Nov-25) and the one I am using in Costa Rica I9300UBUGNK1 (2014-Nov-6) as TWRP flashable files to this post. In the OP of that thread you can find NEUGOA1 (2015-Jan-26). That's the 3 most recent modems for the S3 i9300. The higher the last 4 alphanumeric characters, the more recent the modem is.

And next time make sure you have a recent TWRP full backup so you can easily go back to your current setup in case of a problem.

***
[Galaxy S III Original Android Development] saiesh nachinolkar:
I installed this ROM ....& My Sim card is not getting detected...I tried using different sims ..also wiped data,cache again but still m facing same issue.... someone plzzz help me
[Galaxy S III Original Android Development] kurtn:
Dirt in sim contacts?

Sim correct oriented? Sim detected with other ROM?
[Galaxy S III Original Android Development] saiesh nachinolkar:
Sim card is oriented prply..... I tried using different ROMs...facing the same issue in all the ROMs....
[Galaxy S III Original Android Development] Sobhan Mazaheri:
1- Download official rom 4 file samsung (for your own area)

2- Extract modem and csc files

3- Flashing with odin
[Galaxy S III Original Android Development] 69417:
Hi

I just flashed my Samsung Galaxy S3 with LineageOS 14.1 (lineage-14.1-20190117-nightly-i9300-signed) i'm having a few problems with the camera and geolocation.

Also flashed GAPPS (open_gapps-arm-7.1-nano-20190209)

When i use the default lineage camera app i get a lot of flickering, i found out by installing "open camera" i could change to 50hz and the flickering goes away.

Is there a way to change this also in the default camera app? maybe there is a better alternative for a app, i'm not really a fan of open camera, and it is a problem because snapchat still use the default app.

My other problem is geolocation is not working even though i installed gapps, when i start my weather app or any other app that needs location it detects my location to be in sweden, even though i live in denmark.

It works fine with GPS enable, but at the cost of battery, i prefer using the option where it detects the location through wifi.

am i missing something or is these options simply not working right now?
[Galaxy S III Original Android Development] curiousrom:
S3 i9300 SIM Not Detected

"Sim card is not getting detected ...I tried using different ROMs...facing the same issue in all the ROMs..." - That's not good. :eek:

Install the most recent stock i9300 Samsung firmware for your region:

If the SIM is not detected you have a hardware problem: SIM card reader, water damage or bad motherboard.

If the SIM is detected and Data is working check EFS Partition Backup - No Service, No IMEI & No SIM Card Fix.

Do a clean install as described here S3 i9300 LineageOS Super Clean Install & Samsung Firmware.

In LineageOS if the SIM is not detected turn phone off, wait 5 seconds & turn back on.

If still not detected restore the EFS partition backup you did above.

Please report back if you fix your problem or not. :cool:

***
[Galaxy S III Original Android Development] curiousrom:
New S3 LineageOS 14.1 Build 2019-02-17 Update & Security Bump

FYI there is a new S3 i9300 LineageOS 14.1 build 2019-02-17 Update available in > Settings > About phone > LineageOS updates or in this page: https://download.lineageos.org/i9300.

There are several valuable changes including a security patch (2019-01-05. It was December 5, 2018 in build 2019-01-17) and a Chromium Webviews update (v71) which is used by the LineageOS browser & several other browsers & apps as seen in Updater > 3-dots > Changelog and in this page https://download.lineageos.org/i9300/changes/

In the LineageOS Gerrit, the Bump Security Patch Level to 2019-02-05 patch for 14.1 is still marked as Active (under review) @ the present & is not merged yet. It will be probably be included in the next i9300 update.

Currently the S3 i9300 is getting updates every month around the 17th. but that may change at any time if the LineageOS firmware builder schedule is changed by the team.

Edit: Bad news! See No More Official LineageOS 14.1 for S3 i9300 - Support Dropped!

I will update this post with screenshots after updating my S3. Done. The other screenshot is of Apps > 3-dots > Show System > Android System WebView.

Before downloading the update I enabled > Settings > Status bar > Network traffic monitor and the speed was erratic & changing all the time from 0 to 7.7 Mb/s. Can't say if it was the LineageOS servers or my network provider but thankfully the LineageOS Updater checks the integrity of the file before installing automatically the update.

The update went smoothly as usual & from the moment I clicked on Install & the full reboot to System it took 4 minutes 45 seconds. That may vary depending on your setup.

This was on 100% stock Official Lineage 14.1 on the S3 i9300 (2019-01-17 before the update) + Open Gapps ARM 7.1 Pico + Lineage ARM 14.1 super user add-on (addonsu-14.1-arm-signed.zip for root) with twrp-3.2.3-0-i9300 @ the present. No custom kernel, Magisk, Substratum or system modifications of any kind.

***
[Galaxy S III Original Android Development] saiesh nachinolkar:
So I installed most recent stock rom...

Here's what I am facing.... Sim is detecting but it says cannot register to the network ...I can even see the contacts from Sim card ...here are the screenshots

I tried manually connecting to the network still getting same problem

Then I tried wid different sim cards still same error
[Galaxy S III Original Android Development] curiousrom:
GT-i9300 Not Registered On Network

Thanks for the screenshots. :good:

"...most recent stock rom... Sim is detecting but it says cannot register to the network...tried wid different sim cards still same error" - So this is not a LineageOS problem & must be solved while you are running stock Samsung firmware before trying any custom firmwares.

Have you checked your network provider's APN settings? If it's a new SIM it could take up to 10 minutes to get registered on the network depending on the provider.

The exact error as seen in your screenshot is "Not Registered On Network" and this is what you need to use when searching for a solution.

If the SIM works on other phones & gets network but not in the i9300 my guess is that in About phone the IMEI & serial number is not the same as on the sticker under the battery.

You could try Phone INFO Samsung > hamburger menu > S/N and IMEI Analyser.

On my i9300 it says after clicking on MY S/N & deleting the /0000000000000 part & clicking MY IMEI then Analyse: Country of Origin: MADE IN CHINA, Manufacturing date July 2012 & The IMEI looks valid.

Try these searches:

site:xdaforums.com/ gt-i9300 "not registered on network" imei

gt-i9300 not registered on network

gt-i9300 Z3X Samsung Tool PRO >>> to try to repair the IMEI.

Can't help any more than that. Good luck! :eek:

***
[Galaxy S III Original Android Development] 69417:
I have a problem were my Phone/Caller app seems to be a little slow in the loading, like when i touch the icon i can count to 2 seconds before its fully loaded, and when i receive phone calls the screen is a bit slow to show who is calling, everything else runs pretty smooth.

I downloaded the Google Phone app just to test if that also was slow, and set it to default in the settings.

After this i noticed my i started loosing SIM/Signal, basically just showing as the sim got unplugged, Wifi is still working, and the only way to fix it is by restarting the phone, i dont know if its something to do with the multiple caller apps, i never had this problem on stock.

suggestions?

Edit:

Using 20190217 build with pico gapps

baseband: i9300xxugna8
[Galaxy S III Original Android Development] curiousrom:
Slow Phone App

Yes the phone app is slow on the S3 i9300. Check Incoming Call Screen On Lag.

"baseband: i9300xxugna8" - That's "30.01.14" according to this post.

I attached the most recent S3 i9300 modem I9300XXUGOK1 (2015-Nov-25) and the one I am using in Costa Rica I9300UBUGNK1 (2014-Nov-6) as TWRP flashable files to this post. In the OP of that thread you can find NEUGOA1 (2015-Jan-26). That's the 3 most recent modems for the S3 i9300. The higher the last 4 alphanumeric characters, the more recent the modem is.

***
[Galaxy S III Original Android Development] 69417:
Ahh okay, I might be wrong here, but when i tried XenonHD for i9300 the other day i think it's was faster with the call app, but i prefer stock LineageOS, thats why i was wondering, maybe they did some tweaking with that rom.

gonna try one of those modem firmwares, maybe i'm gonna get a more stabile sim connection.
[Galaxy S III Original Android Development] 69417:
now i got another problem, all my outgoing calls are marked as "unknown" i only installed the rom, gapps pico and then rooted, no other modules or anything other then a few "normal" apps.

i did try the "connected line identification" both in on and off, same problem.

ROM: lineage-14.1-20190217-nightly-i9300-signed
[Galaxy S III Original Android Development] curiousrom:
No feedback about your SIM problem above? :(
[Galaxy S III Original Android Development] 69417:
After i removed Googles phone app i've not had any problems, still running with the same modem firmware.

I don't know if the modem version i'm running with can cause the "unknown" number problem i'm having.

been reading in here but i'm not sure what to do at this point. https://github.com/AOSP-JF-MM/issue_tracking_aosp/issues/60
[Galaxy S III Original Android Development] SRainheart:
Hi. After some searching the thread i can't find answer for the problem i have. I've successfully installed LOS from TWRP.

I have over 10 GiB free internal space and 32 Gib Transcend class 10 external SD.

Formatting External SD as Internal had no success - as i understand - it is SD card problem (but i tried 2 cards same type). So External SD now as a portable.

First problem i've met - after launching Camera app i've got error "insert SD card.." and so on.

Ok, it is not problem - just installed another Camera app and set photo directory on External SD - without the path i cann't save photo/video from camera.

Next - Viber - after successfully installation - i can chat (but cann't see all media recieved), i can do video/audio call, but i can't do photo/video from viber while trying to send photo/video - there is an error - "low storage space". The same error appears when viber automatically tries to download stickers.

I've a root access.

Any advice?

Thanks
[Galaxy S III Original Android Development] curiousrom:
No More Official LineageOS 14.1 for S3 i9300 - Support Dropped!

Well it has been a good run but the LineageOS Team stopped building new Official LineageOS 14.1 for all devices including the S3 i9300. :crying:

LineageOS Gerrit commit 242408: Prepare for 16.0 was merged on February 24, 2019: "14.1 is now deprecated. 15.1 is now weekly."

All builds older than 5 weeks will be removed from the LineageOS servers eventually.

Expand lineage-build-targets on that page to see the devices affected.

If your device like the S3 i9300 is not in the right side of the LineageOS Gerrit 241918: hudson: The real lineage-16.0 ship commit & expanding > lineage-build-targets then no more new Official LineageOS for you.

Note that in the top left of the commit page it says @ the present "Active" which means it's still under review. It will say Merged when approved.

Again: Unless the LineageOS Team change their policy, all builds older than 5 weeks will be removed from the LineageOS servers eventually so backup now the ones you want to preserve for possible future use: https://download.lineageos.org/i9300

Edit: you can find the last 2 official LineageOS 14.1 for S3 i9300 builds in this archive: https://files.moskvich.xyz/LineageOS/14.1/i9300/ Most recent unofficial compiled by [MENTION=7346927]NZedPred[/MENTION] which include security patches: https://androidfilehost.com/?w=files&flid=290848&sort_by=date&sort_dir=DESC

Looking at https://stats.lineageos.org/ there is 42,000 active i9300 LineageOS users as of today. Clicking on i9300 you can see the breakdown of the builds in use currently: https://stats.lineageos.org/model/i9300

***
[Galaxy S III Original Android Development] sonvegeta:
Quite bad. However, those buids (Los 15.1 unnoficial betas) are very good, which means the thing is on its way.
[Galaxy S III Original Android Development] multiwirth:
You should get asked for storage access and if you granted it, you have to close the app and open it again to get the permissions inside the app working.

This is a bug but not a big deal if you know the workaround.

If it didn't ask for the permission, you may grant it manually for each app in settings.

About the internal storage formated sd card i can't help you, it worked just fine back when I used my galaxy s3 as daily driver and now it is running unoffical 15.1 so testing on that won't help you anyways.

Good luck
[Galaxy S III Original Android Development] SRainheart:
Hmmm.

Thanks for reply.

I don't get it.

I have grant on it.

Is it on Settings-Apps-NameOfApplication-Permitions-Storage (Checked on) ??

If it is - so i have it. Trying stop Viber, uncheck, start, stop, check, start.

Didn't try to clear data during operations.

Or is there any other access settings?
[Galaxy S III Original Android Development] multiwirth:
Hmm this is strange and no there isn´t anything else that is related to the storage.

Can you access your internal storage using the built in file manager?

Maybe the build is broken, try an older build if avaiable.
[Galaxy S III Original Android Development] SRainheart:
Yes - i'll try.

That is strange - i see chapter sdcard1 (my external) and GT-I9300 with 0B free on it (selecting it gives me no result)

-

update

strange but older release works fine
[Galaxy S III Original Android Development] 69417:
btw i did try the modems you suggested, it didnt do anything to solve my "unknown" outgoing calls problem, and since i think my other problem was related to the Google Phone app it didnt really make much of a difference for me, with these new modems.

Edit: i managed to fix the "unknown" calls problem by installing xposed and this module, https://repo.xposed.info/module/ru.timjosten.unknownnumberfix
[Galaxy S III Original Android Development] N-Gage4ever:
Hey can we flash it to the latest version of the Rom to get activated Google Assistant?
[Galaxy S III Original Android Development] NZedPred:
Unofficial build - Feb 2019 security patches

And so someone must fill the void...

I currently do unofficial Lineage Nougat builds for another device, so it's not a big deal for me to do builds for this one as well. As long as the repos are still getting commits (it looks as if this will continue as long as others in the community continue to contribute in this way, much like how the Marshmallow repos are being maintained with security patches - they have Jan 2019 security), I can do builds.

So, first up, a build done as of now, which will have the February 2019 security patches.

lineage-14.1-20190302-UNOFFICIAL-i9300.zip

I'll also keep some copies of any builds I do in this folder in Dropbox

i9300 Lineage Nougat

Hit thanks if you want me to keep contributing by doing builds moving forwards.
[Galaxy S III Original Android Development] kurtn:
Last microG build is out https://download.lineage.microg.org
[Galaxy S III Original Android Development] denver04:
Does it include the February 2019 security patches or is it based on the latest official LineageOS build?
[Galaxy S III Original Android Development] itachi uchia:
Yes, it includes February patch.
[Galaxy S III Original Android Development] joesnose:
Hello , this is great news. I have a note 2 and would like to be able to run linux natively. Do you have a link to a guide as to how to accomplish this? Thanks
[Galaxy S III Original Android Development] kurtn:
Looks like Simon stopped working on this. But there is some activities

https://wiki.postmarketos.org/wiki/The_Mainline_Kernel
[Galaxy S III Original Android Development] ArdaCsknn:
Yeah there are no news since September 2018 and he didn't commit anything if you look in to his GitHub. His last sign in to XDA was also 15th September 2018.