yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Mad-Marty:
Thank you so much for keeping that amazing 14.1 rom alive.

Maybe you could ask to put your folder link in the first post as "unofficial continued" or something like that?

Or create a new thread where 14.1 continues?

You deserve a lot more credit as the occasional post with "new version with bugfixes" generates i think :)

I tried to update from the last offical build, aka 2019-02-17 ... using lineage-14.1-20191115-UNOFFICIAL-i9300 but it tells me "can't install on top of incompatible data".

TWRP 3.1.1-0

Log says: "You have an installed system that isn't signed with this builds key, aborting ..."

How can i continue the upgrade, without wiping ... still need all the stuff.

[MENTION=7346927]NZedPred[/MENTION] - its it possible to flash over old official builds or is it intended to error out?
[Galaxy S III Original Android Development] 69417:
I was just messing around with your latest build.

When you go to "About phone" -> and push "Android version" 5 times really fast and screen comes up with a big N, if spam the N. A small icon appears either of a cat face or like something is blocked. What does this mean? easter egg?
[Galaxy S III Original Android Development] eriol1:
Yes, that's android 7 Easter egg, Android Neko.

Next step is to pull down notification bar, edit tiles and add the Easter egg tile.

Have fun.
[Galaxy S III Original Android Development] Mad-Marty:
Hi [MENTION=7346927]NZedPred[/MENTION] ,

i updated TWRP and wiped system, dalvik cache and cache ... but still the current unofficial can't be flashed and reports "cant be installed on incompatible data".

So is that unofficial version really that different from the last official that installed apps no longer work and require a complete wipe?

Any way to avoid that?

Thank you.

---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------

Hi [MENTION=7346927]NZedPred[/MENTION] ,

i updated TWRP and wiped system, dalvik cache and cache ... but still the current unofficial can't be flashed and reports "cant be installed on incompatible data".

So is that unofficial version really that different from the last official that installed apps no longer work and require a complete wipe?

Any way to avoid that?

Thank you.
[Galaxy S III Original Android Development] NZedPred:
I don't believe there is a way to go from official to unofficial without wiping. [MENTION=4122877]curiousrom[/MENTION] has posted some information previously on this. The thing is the official builds were signed with a key, and they do not give out that key to anyone, hence the need for a clean flash.
[Galaxy S III Original Android Development] Mad-Marty:
Thanks for the info [MENTION=7346927]NZedPred[/MENTION]

That kind of sucks :(

But since it's not modified in any way, just containing patches from the official repo ... can you simply ask them to make your builds "official" ?

Or are there very special paperwork requirements to be fullfilled that one can name his builds official?

Edit:

Found this, explaining how to move between official and unofficial builds.

Apparently there are 2 ways, using a migration build resetting keys on start or using a script.

https://wiki.lineageos.org/signing_builds.html#using-a-script

This should work, right?

I suppose you used said test keys to build unofficial? Or do you use other keys/certs?
[Galaxy S III Original Android Development] Mad-Marty:
Hi [MENTION=7346927]NZedPred[/MENTION] and others,

I successfully switched to unofficial without wipe.

For all who want to switch to unofficial, and may switch back to official (provided there will be a official again at some point) do the following:

- First Read https://wiki.lineageos.org/signing_builds.html#using-a-script or better the whole page to know how the keys are used.

We need to use the script method, because else NZedPred would need to create a migration build (and that would be a waste of his precious time).

- Download the unofficial rom zip you want to install and put it on SD card

- Download the ADB platform package and make sure it recognizes your device when plugged in via adb devices

- Download the migration script at https://raw.githubusercontent.com/LineageOS/scripts/master/key-migration/migration.sh

- Boot to TWRP Recovery (or whatever you use) and make sure /data and /system is mounted

# Ensure both /data and /system are mounted, then continue
adb push ./migration.sh /data/local/tmp/migration.sh
adb shell chmod +x /data/local/tmp/migration.sh
adb shell /data/local/tmp/migration.sh unofficial

- Install you ROM ... it will work now because Keys have been reset / changed to test

- Wipe dalvik / cache

- Reboot

- Enjoy that great ROM :)

OpenGapps apparently don't need a reinstall for such minor switches, they keep themselve up to date through playstore anyway.
[Galaxy S III Original Android Development] NZedPred:
New unofficial build - December 2019 security patches

Just in time for Christmas, a new unofficial build available now:

https://androidfilehost.com/?w=files&flid=290848&sort_by=date&sort_dir=DESC

Enjoy :)
[Galaxy S III Original Android Development] chillinfart:
I tested your last build, everything works except display. It shuts completely during calls making phone locked until the call ends. Even the "always on" feature from the developer options doesn't stop this issue. Perhaps phone app is managing some energy or display orders to shut down the screen.

Also tried with other dialers, with the same behavior.
[Galaxy S III Original Android Development] kurtn:
That's a broken proximity sensor. Can you set power button to end phone call?

https://www.ifixit.com/Guide/Samsung+Galaxy+S+III+Front-Facing+Camera+Replacement/12512
[Galaxy S III Original Android Development] chillinfart:
i can check how to end calls in that way. The problem is i need to use the dialer during calls.

If is a sensor issue, how i can disable it? Phone is rooted via SuperSU (Lineage official root is not available by some reasons)
[Galaxy S III Original Android Development] kurtn:
Headset for calls?
[Galaxy S III Original Android Development] chillinfart:
Again, problem is not the call but the screen. I cannot touch anything during calls.

Sensor was working well before upgrade. Maybe a driver issue
[Galaxy S III Original Android Development] kurtn:
You can always downgrade by dirty flashing
[Galaxy S III Original Android Development] ma30302000:
WiFi problem

I have a problem with wifi

my phone doesn't connect to my wifi network and some of another wifi

I tried it in another wifi and it connects successfully

i used the last [MENTION=7346927]NZedPred[/MENTION] rom

any help?
[Galaxy S III Original Android Development] curiousrom:
WiFi Problem - S3 i9300

Are you trying to connect to hidden WiFi networks?

Try installing the most recent modem for the S3 i9300 and while you are at it get the Most Recent S3 i9300 Bootloader: I9300XXUGPE1

You could also try to use a static IP for the problematic WiFi networks. See LineageOS 14.1 S3 i9300 Known Issues Workarounds - Bugs.

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

***
[Galaxy S III Original Android Development] martins200:
Custom APK file install problem

I'm not sure if this has already been answered, but I'm unable to install any custom APKs from apkmirror.com on this ROM. First it asked for Unknown sources permission, which I enabled, however, during the installation of any app it always shows "This app not compatible with your device" error. I'm having no issues installing the same apps from Google play store though. However, I needed a specific version of it.

Does anyone know a possible fix?
[Galaxy S III Original Android Development] abelenki:
i don't use Google Play Store. i use only .apk files for installing any application. i never had any problems installing .apk files on this firmware.
[Galaxy S III Original Android Development] martins200:
have you tried anything from apkmirror.com? Also, did you install the Root add-on if that changes anything?
[Galaxy S III Original Android Development] abelenki:
yes.

yes. i have root on all firmwares.

you are probably downloading .apk files for wrong architecture.
[Galaxy S III Original Android Development] 0xSherlock:
I'm terribly sorry to ask this, but could anyone merge OMS support into this ROM? I lack a sufficiently performing machine to build LOS.
[Galaxy S III Original Android Development] merkwurdigliebe:
Never mind thank you.
[Galaxy S III Original Android Development] kurtn:
Restore a twrp backup of efs partition.
[Galaxy S III Original Android Development] merkwurdigliebe:
Ok so I flash stock rom, make EFS partition backup and then reflash LOS and that backup?? If I understand correctly?
[Galaxy S III Original Android Development] kurtn:
So no one told you to backup efs? I don't know if stock ROM can recover your imei.
[Galaxy S III Original Android Development] merkwurdigliebe:
Never mind, thank you.
[Galaxy S III Original Android Development] Mad-Marty:
Hello,

i sometimes have the problem that sound is completely garbled during a call, when connected to the car via bluetooth.

I even have a profile switching to 2G if bluetooth connects. This makes the sound work sometimes. Sometimes not.

Baseband is XXUGNA8 - does that even have something to do with that?

Anyone knows a fix which works reliably, so that calls no longer have broken sound when connected via bluetooth?

Thanks
[Galaxy S III Original Android Development] NZedPred:
Just a quick note to everyone. I will no longer be making any unofficial builds of this rom. I will keep my files available in the below link, but the December 2019 build is the last one.

https://androidfilehost.com/?w=files&flid=290848&sort_by=date&sort_dir=DESC
[Galaxy S III Original Android Development] deentky:
[MENTION=7346927]NZedPred[/MENTION] Sorry to hear that :( but thank you for your hard and useful work :good:
[Galaxy S III Original Android Development] Mad-Marty:
Sorry to hear too :(

It was a good ride though. Thanks.
[Galaxy S III Original Android Development] moovtome:
Thanks NZedPred for your work!

What's your opinion? Which ROM we should use now?
[Galaxy S III Original Android Development] Chilling Farts:
Found a solution for black screen during calls. Using a compiled phone apk without sensor support.

https://xdaforums.com/showpost.php?p=69507586&postcount=253

But now i have other. Any workaround for missing unicode symbols and video corruption? Twitter videos has glitches at the first bandwith issue. Also, how to install secondary fonts to LOS? I found some apps but it only changes one font at time.
[Galaxy S III Original Android Development] MK_i9300:
Hello,

this is my first post on XDA. It seems that some people might be interested in unofficial builds based on lineage 14.1 for this device. I am compiling lineage 14.1 for my "klte" and "i9300" since the official builds stopped in ~ 02/2019. I am currently running my unofficial builds on both phones with patches from 01/2020 and it seems that the 02/2020 patches are already under investigation (not yet merged). It seems that the bugfixes continue. Thank you developers :):good:

If somebody has online space available I can upload my build. I am still using my i9300 as secondary phone (klte as primary) without any google stuff (but with 128 Gb SD card) for WLAN telephony, bluetooth music streaming and navigation via GPS (rollover bug present).

The builds I am making are pure lineage 14.1, no changes, blobs extraced from last official lineage 14.1 from 02/2019 for i9300.
[Galaxy S III Original Android Development] Sly Fox007:
You could just use androidfilehost.com or any other cloud storage sites and share it here.
[Galaxy S III Original Android Development] curiousrom:
Unofficial LineageOS 14.1 S3 i9300 Builds by New XDA User

That's cool but since you are new XDA member I cannot trust your unofficial builds unless you link to an other social or forum account with a good reputation.

Malware can be included in a ROM & that's why the reputation of who makes it is important. :eek:

***
[Galaxy S III Original Android Development] MK_i9300:
Thank you very much for the reply.

I completely understand and agree to your point of view. This is why I started building for klte and i9300 on my own in the first place.

I am not a software developer but after one year of testing on klte and i9300 I am confident that my builds work as expected and that I do it properly.

I would prefer not to just simply upload the builds and everybody can install them on their phones, but go a more "secure" way: You tell me where I should put the files (maybe on a non-public account) and one or more persons with internal lineage knowledge check if it fulfills the basic requirements (no viruses, malware etc.) and upload it after the examination to a place where everybody can use it. So everybody can be sure that it is working as expected and does not contain unwanted "features".
[Galaxy S III Original Android Development] curiousrom:
Re: Unofficial LineageOS 14.1 S3 i9300 Builds by New XDA User

That does not work because one build can be OK & the next one include malware.

To have to check all builds one after the other every month and to make sure they are 100% clean is too much work, at least for me.

That's why the reputation of the ROM builder on XDA or an other social or forum account is important as I posted above.

***
[Galaxy S III Original Android Development] Adamu10003:
Teamviewer host add on

Hi,

The ROM works great and I've been using it for a while, I hoped the latest update would fix this issue but hasn't so here goes...

I'm trying to install teamviewer host on my S3, which installs fine but installation of the add-on prompts a message stating there's no space and to "free up storage". I've got plenty of storage so that definitely is not the issue.

I've tried to install it through apks and even installing the add on by searching and installing directly from the playstore, rather than through the app but to no avail.

If anybody has any suggestions on how I could resolve this, it'd be greatly appreciated.
[Galaxy S III Original Android Development] kurtn:
Plenty of storage sounds, like you are operating with adopted SD card. That is storage, but not usable by all apps.
[Galaxy S III Original Android Development] multiwirth:
It sounds like the permissions bug for granting access to the internal storage.

Try to grant storage permissions in app settings before launching the app.

It should work then.
[Galaxy S III Original Android Development] Adamu10003:
Thanks for your reply. I actually don't have an SD card in the phone but I do have around 7GB of internal storage space.

Anymore suggestions?

---------- Post added at 01:03 PM ---------- Previous post was at 12:59 PM ----------

Thanks for your reply. I tried that too but it didn't make a difference unfortunately.

I've searched online and read something about "lucky patcher", I tried fiddling with that but it didn't help.

Anymore possible suggestions?

---------- Post added at 01:05 PM ---------- Previous post was at 01:03 PM ----------

It's a shame we can't experience your ROM. Would have been cool to have more updates on the s3.
[Galaxy S III Original Android Development] teigaff:
The problem still persist in lineage-14.1-20191223-UNOFFICIAL-i9300.zip
[Galaxy S III Original Android Development] curiousrom:
S3 i9300 Encryption Fail - Fix

Try a Format Data as described in S3 i9300 LineageOS Super Clean Install & Samsung Firmware instead of a simple wipe Data.

From TWRP FAQ: What is a data/media device?:

"...In TWRP we also have a wipe internal storage option that rm -rf's the media folder and a "Format Data" option that formats to recreate the entire file system in case something goes completely wrong or to remove device encryption."

Format Data adds an empty encryption footer section at the end of the Data partition for some future encryption related data.

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

***
[Galaxy S III Original Android Development] teigaff:
Thanks for the quick help!

This is actually my daily running phone. I'll switch back to my other phone and will test then.
[Galaxy S III Original Android Development] Chef_of_Sweden:
Wifi won't reconnect

Hi guys, since I installed the [OFFICIAL][WEEKLY][7.1.2] LineageOS 14.1 for i9300 from forkbomb444 :good: according to all rules 6 months ago I haven't been able to get the 'Keep Wifi on in sleep mode > Only when plugged in' option to work, wifi simply won't automatically reconnect when I activate the phone and the only way to get it to reconnect is to turn off and on Wifi manually a 2-4 times. I've tried tried all the fixes I could find, most of them from curiousrom:

- Erasing my network settings, reboot and re-enter them

- Changing Network region

- Different Wifi networks

- Static IP and DNS

- Using the app Better Wifi - on/off

- Upgraded my modem to the latest I9300XXUGOK1

- Upgraded my bootloader to the latest I9300XXUGPE1

- Upgraded to NZedPred's latest rom: December 2019 build

- NFC and Wifi scanning is off

Any ideas? :silly:
[Galaxy S III Original Android Development] kurtn:
When I came to the point that system settings could not satisfy my wishes for WiFi switching, I installed WiFi Automatic (WLAN automatisch ausschalten) - https://f-droid.org/app/de.j4velin.wifiAutoOff
[Galaxy S III Original Android Development] Chef_of_Sweden:
Thanks for your suggestion kurtn, I tried the Wifi Automatic but it too fails to reconnect to Wifi when I unlock the device, just like the app "Better Wifi - on/off" from Play store. The only way to get it to connect again is to toggle the switch manually. It seems the problem is deep within the system :confused:

theronkinator seems to have the exakt same problem
[Galaxy S III Original Android Development] orgert:
I saw nzedpred is not building anymore , i still have my build on hyper-v with which i used to build the experiemental build , i will need to update sources , and will see if it will make a new build from official sources without any other modifications, will let you guys know very soon

Edit : i don't have the phone and can't test the build , but if it builds without any error , i hope it will be safe to flash :victory:
[Galaxy S III Original Android Development] orgert:
So i managed to build the rom successfully without any errors (see below screenshot) so i suppose it's safe to flash, BUT MAKE A BACK UP just in case.

DIRTY FLASHING MIGHT/ MIGHT NOT, work over nzedpred , (normaly it should work ) as i didn't change anything , it's pure lineage os 14 from the sources .

The security patch is form February 2020 , when March security patch comes out i will build another one if it's needed here.

I've been on i9300 community for too many years , it was my first android phone , even though my beloved i9300 died some months ago , i want to give to this community back.

I'm not a developer, i just happened to have the sources and managed to settup a hyper-v machine on my works server, and will keep building as long as i have the job I'm at right now.

I have made a back-up of the hyper-v build on my pc at home , but building on it is really slow.

If anyone is interested to build this rom themselves, i'm willing to share the image , you will just need a capable pc on windows 10 , activate hyper-v on it, and the 250gb image of the virtual machine, even though i don't know how to share that large file (maybe i can create a torrent :confused: )

So to finish this post , i hope the rom boots up so you guys can enjoy it.

Have a nice day everyone ! :laugh:

DOWNLOAD LINK FROM MEGA :

https://mega.nz/#!cHIwXCbD!OguawqZ_Ddbwk7Cs2EW0sDy6rDF9UkUGjLN27s84X3c

Screenshot of finished build :

https://imgur.com/a/F8zYcuc
[Galaxy S III Original Android Development] abelenki:
AndroidFileHost
[Galaxy S III Original Android Development] orgert:
Do i need to pay for their services ? And does it support to upload a single file of 250 Gb? , i'll look into it ,but for now my country is in carantine from coronavirus, so I'm off work for sometime.
[Galaxy S III Original Android Development] abelenki:
no.

yes.
[Galaxy S III Original Android Development] orgert:
Ok
[Galaxy S III Original Android Development] Andresine:
The ROM boots perfect. Everything is ok.
[Galaxy S III Original Android Development] orgert:
Thank you for reporting :svetius:
[Galaxy S III Original Android Development] Sly Fox007:
If anyone wants to build their own they can use the docker image docker-lineage-cicd made by microg.

I built the i9300 a couple of days ago and it has the February 2020 security patch.
[Galaxy S III Original Android Development] orgert:
This looks really great stuff and straight forward ,thank you for sharing
[Galaxy S III Original Android Development] teigaff:
Thanks a lot for this fantastic guide to format data. I didn't know that this partition has to be formatted extra.

Now encryption work flawlessly.

---------- Post added at 10:53 AM ---------- Previous post was at 10:14 AM ----------

Thanks for the update and so continue to use our old mobile phone. I freshly installed mine and it works with SU and F-Droid Store OTA.
[Galaxy S III Original Android Development] kurtn:
In XDA community we use "OTA" to indicate a ROM that has built-in over the air update capability. Usually with an app that downloads the file and starts a recovery script to update without further user interaction.
[Galaxy S III Original Android Development] minealex2244:
Deleted
[Galaxy S III Original Android Development] gr8nole:
While the official thread is not the place for your unofficial build questions, you need to sync the vendor_samsung repo.

See github.com/themuppets
[Galaxy S III Original Android Development] minealex2244:
Thank you! Next time I'll stick directly to questions category instead of the official thread.
[Galaxy S III Original Android Development] :
Root not working for Adaway app . i flashed addonsu package, enabled root for apps+adb, but adaway does not get root . it is going down the drain with this rom, first camera quality much worsened, now root not workened . wtf .
[Galaxy S III Original Android Development] andrescm:
Are you sure you are using an updated version of Adaway?. Do other apps detect root?. If so, it's the app, not the ROM.
[Galaxy S III Original Android Development] Hawaiihemd:
FYI, Adaway v3.2 working just fine here on 20170206 nightly.
[Galaxy S III Original Android Development] :
Ok, with very latest SuperSU it worked, but not with the lineage OS addonsu package (no error message, just not working) , or with older SuperSU (problem when flashing) .
[Galaxy S III Original Android Development] andrescm:
Strange, I'm using addonsu with Adaway 3.2 (60) and it works like a charm.
[Galaxy S III Original Android Development] Ashraf Iraqian:
no i meant when i charging my phone , now i am turned off the Battery LED