yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] curiousrom:
Thanks for the feedback. Which guide did you follow exactly? If you Thanks :good: the post it's not only good for my ego but also indicates to other users that the info may be useful for them too.

Next time you have problems in TWRP saving a log to the external SD card may give precious clues. While still in TWRP you can save a log as described in the top of this post.

Or: it's not always available after a failed install but after a reboot if rooted (or w/ ADB CMD) you can check in: /cache/recovery/last_log which is a TWRP log that you can rename Recovery_last_log.txt & open w/ Wordpad or Notepad++ for example.

Thanks for the feedback & glad you fixed your "...the phone never unlocks on after screen locked when mobile data on..." problem. :cool:

***
[Galaxy S III Original Android Development] barathrr96:
Yes I do that since im using XDA.. Yes it helps...

Since it had no lags I had not seen that problem at all... Even legendary bug on all Samsung phones starhub firmware using in India, no video from front facing camera on WhatsApp video call I'm not facing it ....

Before flashing kofee kernal yesterday.. It works after installing it to...

No hangs and freezes during m.data on..

And passes safety test only when no root and after installing kofee kernal..
[Galaxy S III Original Android Development] kosmasgr:
First i installed stock firmware with Odin and TWRP tar img. Then format data and wipe data-cache-dalvik. Rebooted to recovery again and installed LOS14.1
[Galaxy S III Original Android Development] barathrr96:
I first rooted my stock ROM using kingo root app..

Then flashed twrp 3.2.1 using flashify..

And rooted with SuperSU. But Kingo root took root management.

Now did the dummy file generation and delete the files , trimmed using the respective apps for 4-5times

Now I tried installing los 14.1 after factory reset only.. Then flashed gapps, n after first boot installed kofee kernal n low ram kofee, latest magisk

It was that smooth.. So now with confidence I have done the same for RR and going good.

Goona install viper soon..
[Galaxy S III Original Android Development] barathrr96:
Those who have any freeze or hangs in ur S3, check ur chip, root ur device, generate dump files and delete and trim nand chip as prescribed by #curiousrom. Then try anything..
[Galaxy S III Original Android Development] capo56:
Guys, sorry for maybe bad question, but let me ask honestly. How stable this build (the latest nightly) is? I need to have any newer Android version on my 9300 that I just took out from my desk as to use it for my young doughter. Currently this is on 4.3 (latest offical ROM version available) and many kid apps are not compatible with that and requires something newer. If this is not stable enough, is there any other version that you might recommend (CM 13 or so?). Thanks a lot.
[Galaxy S III Original Android Development] LazyGuy1:
It's stable enough for daily use, but I would still recommend CM12.1/13, as for me sometimes my S3 is freezing when connecting to WiFi (Only if you install Gapps: low RAM device > searching for updates for Instant Apps makes the device slow and requires a reboot sometimes..). So, yes. If you want Android 7.1.x, then go ahead and install LOS14.1

Regards,

Lazy.
[Galaxy S III Original Android Development] curiousrom:
Is LineageOS Stable? - Wifi Freezing Workaround

LineageOS 14.1 (updated to 2018-03-22) + Open Gapps nano + Lineage su addon + more than 100 apps has been running 99% trouble free since 4 months on my S3 i9300 which is my daily driver.

I had the camera crashing 3 times in 4 months but it's easily fixed with Camera Restarter.

Installed as described in this post: stock Samsung firmware & LineageOS Super Clean Install.

***

You are one of the few unlucky ones. Have you tried this: S3 Lineage Crashing Wifi Network Reconnecting Bug Workaround

***
[Galaxy S III Original Android Development] dana.marivani:
I found the solution for MTP

you have to use full wipe and reinstalling los14.1 so the problem is resolved on windows 10
[Galaxy S III Original Android Development] Robert-R:
I came from CM13, and I can't recommend it anymore, as many app-updates resulted in a bootloop. This started happening since approximately October 2017.

I switched over to Lineage 14.1, and was happily surprised; see my post: https://xdaforums.com/showpost.php?p=75500185&postcount=4088

"freezing when connecting to WiFi (Only if you install Gapps: low RAM device > searching for updates for Instant Apps makes the device slow and requires a reboot sometimes" :

I also have Gapps installed (not using Instant Apps, however), and I have never experienced this freezing at my S3/Lineage 14.1.
[Galaxy S III Original Android Development] Robert-R:
Restrictions to Play Store access / "device-not-certified-by-google-error"

I assume, we will face this in the near future:

https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/
[Galaxy S III Original Android Development] lollo.21:
are there no commits for this week's build? some news?
[Galaxy S III Original Android Development] curiousrom:
Bunch of Links: S3 i9300 LineageOS, Developer & Oreo Project
[Galaxy S III Original Android Development] lollo.21:
Thanks for the reply :)

I normally check here:

https://www.cmxlog.com/14.1/i9300/

but this week I do not see new changelogs, if you can tell me about the news since I'm not very good at reading English :)

thanks you very much
[Galaxy S III Original Android Development] mountainguan:
I think there won't have any changes specify for i9300 in couple months, until forkbomb444 finished s3's new kernel. New kernel named midas , github can check every changes of this kernel. Forkbomb444 is the core member of LOS , so besides the work on s3's kernel , he also have to work a lot in other LOS projects. He is quite diligent on coding , and always can see the commits on github for the new kernel. So the work on old branches may slow down or even will be abandoned. But we will get Oreo and get a latest linux kernel for our device. Just be patient and waiting for his great job.
[Galaxy S III Original Android Development] anupritaisno1:
Guys don't worry about Google showing uncertified on some devices this is actually quite an old feature and Google has been doing this for a long time

None of you will be affected by this
[Galaxy S III Original Android Development] lollo.21:
very well, you have been very clear with the explanation, is waiting without any problem :)

a curiosity, but with Oreo we will always have the boeffla kernel available and xposed? thank you so much
[Galaxy S III Original Android Development] Ashraf Iraqian:
why :confused:

my device certified

read this https://www.xda-developers.com/magisk-16-3-fixes-pokemon-go-uncertified-devices/
[Galaxy S III Original Android Development] Robert-R:
My device isn't certified. I didn't install Magisk (yet).
[Galaxy S III Original Android Development] curiousrom:
Device is not Certified by Google - Who Cares?

No S3 Official LineageOS 14.1 user reported a "Device is not Certified by Google" error when using Play Store yet so there is no need to worry IMO.

See error splash screen and more info here: https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/

Even if you can see in Play Store > Settings > Device certification > Uncertified > if you can download or update apps then there is no reasons to worry.

My S3 i9300 is working fine since 4 months and I will not be modifying the 100% stock LineageOS 14.1 (currently updated to 2018-03-22) + Open Gapps nano + Lineage su addon unless I get that splash screen and if it does appear I will try the registering method in that article before installing Magisk and/or a custom kernel.

Why try to fix something that is not broken? :confused:

+1. :good:

***
[Galaxy S III Original Android Development] Robert-R:
+1:good:
[Galaxy S III Original Android Development] :
Does anyone have an issue that this ROM just runs a bit in like slow motion,like the touch responsiveness isn't very great and it just feels a bit slowed down overall.

Probably it is like that since the phone is 6 years old.
[Galaxy S III Original Android Development] curiousrom:
S3 Slow? Speed Up Tips

More than the age of the S3 it's the RAM limitation & lack of implementation of hwcomposer in LineageOS 14.1 for S3 i9300.

From this post S3 Lineage Battery Drain Troubleshooting & Optimization:

5- Speed up considerably the opening/closing of App tray, Statusbar curtain, swiping between Home pages, Recents app window, opening & closing of apps, etc and also save battery with: Settings > Developer options > Drawing > set Window animation scale, Transition animation scale & Animator duration scale from 1x to Off. Try all those functions before tweaking those settings & observe the huge difference. You could also set to .5x to have some animations & fading while gaining some speed too.

And obviously prevent apps from running in the background if you don't need them:

2- LineageOS awesome built-in tool: Settings > Personal > Privacy > Privacy Guard > 3 dots > Advanced > 3 dots > Show built-in apps or not > then swipe between Location, Personal, Messaging, Media, Device, Background (my favorite) & Bootup (love that one too). You can optimize the power usage for each app (long press) by denying Notification, Vibrate, Keep awake, Run in background & Start at boot according to your needs. You can create a direct shortcut to Privacy Guard & much more with the Settings widget (long press on an empty space in Home pages).

7- That's an important one because it kills some background processes: Recents apps button (left of Home) > kill all the ones you will not be using for a while. You can observe that if you have a Task Manager app & observe the processes closing or in #2 Privacy Guard above. Also when finished with an app use Back button (right of Home) and only Home button for using again that app in a short while (which saves battery in that case) because Home does not fully close them.

+ 12 more tips in that post.

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

***
[Galaxy S III Original Android Development] :
Thanks I will try these out later but just an offtopic question if you can answer it,how big is the performance difference between Lineage 14.1 and for example an Android 6.0.1 custom ROM such as CM13?
[Galaxy S III Original Android Development] curiousrom:
I went from Samsung 4.3 based custom to LOS 14.1 and would never go back.

Don't know about CM13 on S3.
[Galaxy S III Original Android Development] ArdaCsknn:
Phone shows as uncertified in play store and I can't install anything.Anyone knows the fix?
[Galaxy S III Original Android Development] curiousrom:
You did not say if running stock LOS or/and Magisk & custom kernel.

https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/

Google dropped the ball in this mess created by them.

***
[Galaxy S III Original Android Development] ArdaCsknn:
Sorry for not giving informations.I installed Experimental build with the latest changes,microg,Hybrid kernel and tried fix for magisk.But I'm not able to fix anything.I also tried registering device but didn't help.
[Galaxy S III Original Android Development] curiousrom:
Your setup has nothing to do with Official LineageOS 14.1 which is this thread's topic.

My guess is a Microg related problem. Check that thread.
[Galaxy S III Original Android Development] ArdaCsknn:
I checked the thread but they are saying it is not a problem with microg.I guess I need to re-flash the rom.I don't want to install opengapps because it causes huge battery drain which I can not fix.Also SafetyNet fails.Can I find a framework that patched for S3?
[Galaxy S III Original Android Development] Darth Bidder:
I have a question about upgrading to a newer build of LOS 14.1.

If I update it to a newer build, would all of my files on the Internal Storage be deleted too?

Do I have to make a backup of the files in the Internal Storage everytime I update?
[Galaxy S III Original Android Development] ArdaCsknn:
No you don't have to wipe all the time you can dirty flash it.But I'm not sure about switching like CrDroid to LOS or Ressurection Remix to LOS.
[Galaxy S III Original Android Development] Kippy51:
Switching ROM's: always clean flash (so back-up everything). Updating ROM: dirty flash, unless the dev says otherwise. If you dirty flash, all your files survive, but it's always wise to do a back-up (just in case).

The 'cleanest' dirty flash for updating I always do is: Reboot into TWRP, Wipe, Advanced Wipe, wipe cache, dalvik and system. Go back to main menu of TWRP and install ROM and Gapps in one go (if you need root add SuperSU, Magisk or Lineage's own root addon to that as last file to flash).
[Galaxy S III Original Android Development] forkbomb444:
A little Oreo update for you all...

Linux 4.17 will have support for the S3/Note 2. (So with a little bit of modification, you could install a regular Linux distro and use it on your phone!). I'm working on getting the notification LED driver submitted upstream - it should land for 4.18, probably along with support for the back/menu keys.

I've gotten audio working, but it's in need of more testing. I also manages to test the camera: [IMG="camera"]https://i.imgur.com/Yq7qXCO.jpg[/IMG]

I've managed to successfully load the firmware onto i9300/n7100's modem. Currently I'm working on rewriting the kernel driver that RIL communicates with - Samsung's old implementation was unnecessarily complex, and they made some interesting design decisions in the way the driver behaves... Hopefully that will be done relatively soon - you can watch the progress here
[Galaxy S III Original Android Development] kosmasgr:
This guy deserves our donations. Everyone ??
[Galaxy S III Original Android Development] LazyGuy1:
Just 3 words: YOU ARE AWESOME! :)
[Galaxy S III Original Android Development] multiwirth:
So much love for an old device like this :good:
[Galaxy S III Original Android Development] LazyGuy1:
We won't have boeffla kernel unless someone ports it to Oreo.
[Galaxy S III Original Android Development] multiwirth:
Shouldn´t be so hard to port it´s extra features to the new kernel.

I only care for zzmoove governor and the higher headphone output gain.

Anyways I don´t use the galaxy s3 much since i have a newer device which runs perfectly with stock lineage kernel.
[Galaxy S III Original Android Development] LazyGuy1:
Haha yeah, me too. Not using my S3 as daily driver as I have other devices which are 10 times better than our old S3.
[Galaxy S III Original Android Development] curiousrom:
Thanks for nagging us who are using the S3 as daily driver and doing it in a S3 thread.
[Galaxy S III Original Android Development] rocciacoraggiosa45:
Galaxy s3 is at second ranking of los installation so we need Oreo thank you forkbomb
[Galaxy S III Original Android Development] LazyGuy1:
I'm sorry haha, not meant seriously, my S3 is still in my heart <3
[Galaxy S III Original Android Development] acroreiser:
Not Boeffla, but derivatives.

Koffee will be ported to upstream 100%,

Hybrid - don't know, but very and very possible.
[Galaxy S III Original Android Development] LazyGuy1:
Nice, thanks for the nice Koffee kernel! Would be nice on Oreo too!
[Galaxy S III Original Android Development] sajeel:
just downloaded and installed all went smooth rom looks good and comes with privacy guard
[Galaxy S III Original Android Development] sajeel:
2 issues so far

mtp keeps closing ?

and settings about phone keeps closing ?
[Galaxy S III Original Android Development] Robert-R:
workaround for MTP-host error:

https://goo.gl/Vm3hT1
[Galaxy S III Original Android Development] slonioo:
We are famous:good:

https://www.xda-developers.com/samsung-galaxy-siii-samsung-galaxy-note-ii-htc-hd2/
[Galaxy S III Original Android Development] ArdaCsknn:
I was going to buy a new phone before Simon teasing us.Because I dropped my phone in to bleach and it started to acting weird(touching everywhere on screen and unresponsive led buttons).I put it in dry rice and waited a day it fixed the problems but the home button sometimes not pressing.So after that news I am waiting for the Oreo Rom.
[Galaxy S III Original Android Development] Dr.N@:
If i understand it right, bring a kernel with Version 3.17 or 3.18 . this is amazing if you look to the s5 that use 3.4 . The last time i saw a Kernel base port was in the S Plus forum where great developer port 3.0 and 3.4 Linux kernel to a device that official roll out with Linux kernel Version 2.6 . This is amazing and i think Android Go (8.1) will run better than the offical Android 4.3 Form Sammy.
[Galaxy S III Original Android Development] LazyGuy1:
It's not 3.17 which comes to our beloved S3, it is 4.17 linux!! Ah, my main device (Galaxy S5) has 3.4.113 as you say, but I'd really like to have an updated kernel version for it, too.
[Galaxy S III Original Android Development] Dr.N@:
Now you habe find a developer for it for example the guy from smartpack kernel
[Galaxy S III Original Android Development] LazyGuy1:
I may start porting the 3.10 kernel to the S5 soon with the help from the dev of the SmartPackKernel, but I'm really not sure I can do it, but let's leave S5 discussions in the S5 forums, and not in the S3 forums, we are OT now :D.
[Galaxy S III Original Android Development] ArdaCsknn:
Yes it was another level of flashing :D
[Galaxy S III Original Android Development] qb74:
Can we expect a working HWC (finally) with Oreo's release? Huge thanks for still keeping our device alive!
[Galaxy S III Original Android Development] LazyGuy1:
It depends. No one knows it (except Simon).
[Galaxy S III Original Android Development] rINanDO:
Awesome! I see some commits for exynos4210 in your repo. Will the kernel also be running for i9100? What needs to be done to make this possible?
[Galaxy S III Original Android Development] tdcfpp:
Wrong! We'll update hwc!
[Galaxy S III Original Android Development] anarchist1017:
Well its already working smoothly in the exp build with absolutely no issues so...
[Galaxy S III Original Android Development] tdcfpp:
No, my friend. Framebuffer driver on kernel 4.17 differs a lot from the one from stock sammy kernel. We should find again the way how to put 5 layers on the screen.
[Galaxy S III Original Android Development] anarchist1017:
I trust forkbomb if he can update our kernel to 4.xx he can update the hwc
[Galaxy S III Original Android Development] tdcfpp:
Of course. He can count on me for that
[Galaxy S III Original Android Development] qb74:
except that a majority of people couldn't even boot into the ROM, so yeah.

Great to hear! One more question, what exactly happened to the exp. build you released back in October? Did you guys just abandon it due to moving over to 4.xx?

Thank you for your support for our device!
[Galaxy S III Original Android Development] ArdaCsknn:
And it is not that perfect and still crashing sometimes.
[Galaxy S III Original Android Development] GalaxyMaster_P:
That's not forkbomb, I think you got confused there. Btw I made an updated build of the experimental rom, it's in the thread somewhere. I'm planning on doing another build, possibly also doing builds with Uber toolchain.
[Galaxy S III Original Android Development] qb74:
[MENTION=3350694]tdcfpp[/MENTION] is a major contributer to fixing S3/Note2 HWC and making the exp. build along with our device maintainer, forkbomb.

Have yet to try your updated build, I'll take a look at it.
[Galaxy S III Original Android Development] GalaxyMaster_P:
Apologies, I didn't realize [MENTION=3350694]tdcfpp[/MENTION] helped fix the hwc.
[Galaxy S III Original Android Development] ArdaCsknn:
I'm always wondering what is the cause of the playback issue?
[Galaxy S III Original Android Development] anarchist1017:
Damn right..again thanx a bunch for that I actly taught of abandoning i9300 if the hwc was not fixed coz I needed playback of videos
[Galaxy S III Original Android Development] anarchist1017:
Nope haven't encountered any crashes..maybe coz I'm using a diff kernel??
[Galaxy S III Original Android Development] ArdaCsknn:
I had it once while browsing on instagram.I was swiping really fast to see older posts then none of the videos played.Tried youtube and gallery and didnt work.As usual restart fixed it.
[Galaxy S III Original Android Development] qb74:
it's a issue which is correlated to a unstable HWC implementation/no HWC, HWC crashes due to lack of RAM(unsure if its the lack of RAM, correct me if I'm wrong)and you can't have any media playback (no audio, no video)

plagues most of Marshmallow and above ROMs on the S3 iirc, not sure if exp. build fixes this.
[Galaxy S III Original Android Development] fonfox:
https://xdaforums.com/lenovo-p2/how-to/disable-lineage-os-validation-error-t3774252
[Galaxy S III Original Android Development] antares*:
Great to see there is support for this device :) thinking of flashing this over the original firmware, is there any inherent issues experienced over time or is safe to go ahead with it? How is the overall day to day usage of the device in your personal experience?

Sorry for questions, still a newbie at this.

Thanks in advance :)
[Galaxy S III Original Android Development] curiousrom:
LineageOS 14.1 for i9300 as Daily Driver?

What he said. :good:

Known bug: MTP Host as stopped - Crashing Bug Workaround Fix S3 LineageOS

See S3 Samsung Stock & Lineage Clean Install

***
[Galaxy S III Original Android Development] Simon_29:
Normally you have to give your device a static ip if it crashes to connect to wifi. It is strange that it isnt restarting...

---------- Post added at 08:38 PM ---------- Previous post was at 08:37 PM ----------

Thank you! Haven´t seen it.
[Galaxy S III Original Android Development] avishek83:
[EDIT]

Here's the commit for the switch to the common audio HAL : https://review.lineageos.org#/c/159471/[/QUOTE]

Im sure it is a device specific/kernel related problem since los has been ported to other devices and they aint facing video calling problms in whatsapp, hike , skype or viber like galaxy s3 users.

Video calling works on 4.4.4 stock base roms but thats no big deal
[Galaxy S III Original Android Development] arnicika:
is it maybe the gapps nano? i download stock now, and try
[Galaxy S III Original Android Development] Maxoobidou:
1. That common HAL is for Samsung devices only.

2. At the moment, the i9300 is using a specific implementation. But it is going to be switched to that common HAL. I'm not saying your issue comes from that HAL. I'm saying you have an audio problem, and the audio part is going to be revamped soon. So troubleshooting the issue now might prove to be a waste of time. It might be solved when switching HAL. If not, then it'll be time to investigate.
[Galaxy S III Original Android Development] Pasindu88:
Dirty flash experimental and reboot. Then dirty flash nightly. Please read older posts before ask. This question was answered in many pages. They changed the camera app. Maybe they will later add old camera app or improve current app with proper libs.
[Galaxy S III Original Android Development] dzincha:
Dirty flashed to 31.01 from CM14.1.

Battery charging is interesting - if left charging overnight it sometimes is ~95% in morning, but sometimes 70%. Samsung charger 700 mA.

There was one case, when camera failed. And one message that playstore failed. Playstore didn't flashed when migrated to 31.01.

Is there new camera app what should be installed? Readed previous 3 pages didn't saw link whatever.
[Galaxy S III Original Android Development] strayhero92:
I am facing a bootloop issue, the only error showed up during flashing/wipe is unable preload invalid argument, any solution?

Thanks in advance
[Galaxy S III Original Android Development] abelenki:
yes.

boot into TWRP. wipe everything (excluding your sdcard-ext and otg) and flash official LineageOS + addonsu-arm-signed (ignore error) + open_gapps.
[Galaxy S III Original Android Development] strayhero92:
I'll give it a try, thanks man

---------- Post added at 10:44 AM ---------- Previous post was at 10:29 AM ----------

@abelenki still bootloop, any other solution?