yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] huzzam:
that's what the "new topic" button is for. it's a different topic. feel free to make one and post here (or even add it to your signature), but it's most definitely off topic. this thread is for lineage Nougat.
[Galaxy S III Original Android Development] Ashraf Iraqian:
Hi guys

anyone explain to me Video Editor apps problem in this ROM

(kineMaster,ActionDirctoer,VideoShow,many others)

when i produce any video after editing it

it is changing the original colors! :(

please help.

even i am googled this issue but didn't found anything like this.
[Galaxy S III Original Android Development] qb74:
I owe you an apology, I'm on the latest official build and I must say, I didn't encounter the playback bug thus far, splendid!

However, I have really atrocious battery life. BetterBatteryStats tells me I'm losing ~30%/h, this was a thing on Nameless as well. No clue what's causing it.
[Galaxy S III Original Android Development] Elton47:
He doesn't want to make a new thread just to tell us about his progress on building Oreo. The reason he's not creating the thread is that the ROM doesn't boot, yet. There is no point to make a "[8.0][ROM][UNOFFICIAL] LineageOS Build That Doesn't Boot" thread, so please, you can just pass through his posts without reading. There are some others, me first, that are interested in minealex's progress. Thanks for reading this.
[Galaxy S III Original Android Development] Noobkid77:
Like Elton said please be considerate there are many of us who are interested in hearing what he has to say at the end of the day you'll benefit as well if all goes well.
[Galaxy S III Original Android Development] zarere:
Everyone respect his work because finally if everything goes well we all use the final product but also I think that there is different thread for each thing so if something needs to be said it's better to be private or in correct thread.Once again nobody is saying that the progress is bad thing but please follow the rules,thank you.
[Galaxy S III Original Android Development] multiwirth:
I hope we will get a boeffla kernel with HWC - on his website he puts the galaxy s3 on the list of "no longer supported in LineageOS15" -so this means he may release new kernels as long as we stay with nougat but after that, we need a new custom kernel.

I don´t care much about overclocking - it is useless if HWC works.

But we really need a faster switching governor like zzmoove (or even better interactive) which gives a much smoother UI due to the fast hotplug which enables/disables cores if needed or not like every more modern phone does.

pegasusq disables one core after boot and after a long time it runs only with two cores if you don´t use heavy apps.

So the load goes up to 100% peak, only 2 cores up and this causes heavy UI laggs.

It would be amazing if [MENTION=5405215]forkbomb444[/MENTION] could include zzmoove and set it as default.
[Galaxy S III Original Android Development] qb74:
Honestly, the latest build is pretty fluid for me. Overall a really pleasant experience to use my device again :D

I do agree on the governor part though. I find intelliactive to be nicer though, at least in my experience.

What I find interesting though is that by default, the i/o scheduler on LOS is cfq. Now, I don't know much about i/o schedulers, read-ahead and governors, but apparently (from the articles I've read) Zen & ROW are the best for most phones, especially slower ones. Could be really wrong, if anyone feels like correcting me and educating us, please do!

What I particularly don't understand though, is that I get REALLY bad battery life, like 30%/h in BBS bad. Apparently the main culprit is under Alarms>Android>*job delay*

Maybe Amplify will help, will report back.
[Galaxy S III Original Android Development] multiwirth:
Intelliactive?

As far as I know, it doesn´t have a hotplug or no "fast" hotplug.

zzmoove runs very well and should be the best balance between performance and battery life:

It disables 3 of 4 cores in idle or when doing nothing while screen is on and enables one or more cores (or all) if you do anything.

So it gives you the power when you need it.

All other governors I tried don´t have hotplug (all cores always up) or just switching 2 cores on and off (so there are always min. 2 cores up)

About sheduler:

I don´t know much but I can´t notice any improvements by changing them.

Working HWC and a better governor is what our device needs - then it can handle android oreo easily ;)

I already tried LOS15 on my HTC and it seems like it needs a little bit less ram so this could also improve performance a little bit.

Priority nr. 1 is HWC
[Galaxy S III Original Android Development] Tech-Ina:
Can you please let us know which zzmoove profile you are running? I haven't played around with this governor all that much. Did a quick test with the standard profile and it appeared to turn off cores very aggressively, to the point where scrolling in the Facebook app was using just a single one and was very laggy. Currently using the performance one and I'm quite happy. My previos governor of choice was lulzactiveq, but that makes the phone heat up quite a bit.

Other than that, the official builds are indeed very smooth at this point.
[Galaxy S III Original Android Development] minealex2244:
Here are the rules: No placeholder threads! I'm not spamming this thread with my notifications it's just quiet. But I can respect your opinion so I'll give more importance to S6. There aren't any "unofficial mods" which respect some new rules XDA doesn't even know. A new thread as you say it's for something. I have nothing for now. Only the help from another dev and a PC. I'm not spamming XDA with useless threads. These are the rules I know. I think a Telegram group would be a great idea. If anyone is interested just PM me with your Telegram name so I can start a group.
[Galaxy S III Original Android Development] multiwirth:
I'm using the profile "optimal" and this gives me the best value between performance and battery life.

And laggs are normal > a similar device with a more modern SoC has it's problems with android 7 and modern apps aswell.

The qualcomm snapdragon 400 is even slower than the exynos 4412
[Galaxy S III Original Android Development] Robert-R:
Try Cameringo-camera-app from the Playstore. Works great for me (no need for the Camera-Restarter then).

---------- Post added at 12:55 PM ---------- Previous post was at 12:23 PM ----------

Coming from cm13-snapshot, I now have flashed LOS 14.1-20171206 (Nightly).

I aim quite happy with it. It is stable enough to be used as daily driver, and it feels comfortable to have a recent Android-security-patch again.

I'm using Cameringo-app from the Playstore in stead of the LOS-camera, QuickPic as gallery, ES File Explorer as file-manager, AFWall+ as rooted firewall.

The only issue I have encountered so far, is the (known) MTP-Host error message (which doesn't bother much).

Many thanks to the developers, especially Simon!
[Galaxy S III Original Android Development] minealex2244:
Ok. Finally I made a group just for LOS 15.0. We will keep this thread clean from my notifications. Here is the link: https://t.me/joinchat/FB1dMk_YtXmpleCz46M9XA
[Galaxy S III Original Android Development] g104:
Did you mean "Cameringo+ Filters Camera"?

By the way, you still need the Camera Restarter when WeChat, Line, Whatsapp video call not working & save your time from rebooting.
[Galaxy S III Original Android Development] Robert-R:
I use the Cameringo+ Filters, indeed (but the Lite - version might work as well). For some strange reason, in the Play Store, I don't find both versions when searching on "Cameringo"; in stead one can search for the developer-name: "Perraco" .
[Galaxy S III Original Android Development] kosmasgr:
Download lite version from Play store. Inside app there are some settings which redirect to buy premium build :)
[Galaxy S III Original Android Development] g104:
Yeah, the camera look quite good, but doesn't allow my navigation button to be appeared.
[Galaxy S III Original Android Development] Robert-R:
On my device "back"-, "home"-, and "recent"-key do function normally when the cameringo-app is opend.

Do you have an extra navigation-button installed?
[Galaxy S III Original Android Development] g104:
Apparently, I'd manually added 'qemu.hw.mainkeys=0', but I found out just swipe up from below, the navigation buttons will be appeared.
[Galaxy S III Original Android Development] qb74:
media playback bug still persists, was surprised it lasted this long without crashing, sigh... (crashed like 4-5 thus far, rebooting is a pain :/)

the wait for another experimental 7.1.2 build continues...

thanks anyways!

What I'd like to point out though, it has been talked a lot about in almost every custom ROM thread. Callers hearing themselves in 3rd party apps (whatsapp/viber/tango etc., both voice call and video call). I'm curious on this, could this be fixable with some edit to the m0 file that's used to boost speaker sound or does it require a completely new driver for noise cancelling? Normal GSM calls work fine though, even when on speakerphone.
[Galaxy S III Original Android Development] Elton47:
2 new commits by Simon 5 mins ago!

Cheers!

https://review.lineageos.org/q/project:LineageOS%2Fandroid_device_samsung_i9300
[Galaxy S III Original Android Development] JosVermeulen:
Let's hope he gets to fix hwcomposer as well. From what I've heard from the few who could run the experimental build, it ran very smooth.
[Galaxy S III Original Android Development] nobuteru:
hello thank you, I wasn't asking ETA... I am just curios about Lineage OS...
[Galaxy S III Original Android Development] ArdaCsknn:
Yeah Im using the experimental build and I cant go back to nightlies.Its so smooth .But there are little problems that not bothering me.
[Galaxy S III Original Android Development] CelticWarrior:
Thans for support Galaxy S3.

I have flashed last release (12.13.2017).

I don't know why, but the phone enter in freeze when screenoff.

So i have to restart each time.

Help me plese :crying:
[Galaxy S III Original Android Development] curiousrom:
LineageOS Clean Install

You don't give ANY details of how you did it coming from which ROM or what you installed so it's impossible to troubleshoot. :rolleyes:

I have zero problems with LineageOS 14.1.2 2017.12.13 on S3 i9300. Here is how I installed it:

...Best is a clean slate: after backup of your data: format internal memory, wipe everything & flash LOS, gapps & the LOS su addon if you want them one after the other before rebooting to OS.

Clean Install

What is your recovery version? Is it the most recent twrp-3.2.1-0-i9300? I downloaded the .img version from TeamWin TWRP here and flashed it with my old Philz recovery directly from the phone's external SD card. Or install the .img.tar version with Odin or heimdall from a computer.

I followed exactly this guide: How to wipe in TWRP properly? and followed exactly the Installing LineageOS from recovery part of the wiki including steps 10 (gapps ARM Android 7.1 first) & step 11 for Lineage su addon addonsu-14.1-arm-signed.zip (after gapps).

And install all apps fresh after that & not from a backup... if you can.

From the post #1 of this thread:

Please be :cool: & report back if you fixed your problem or not. Good luck!

Two days ago I followed the same steps on an old Galaxy Tab 2 7.0 Wi-Fi tablet running Samsung stock 4.2.2 ROM except for flashing TWRP using Odin & installed Official Lineage 13, gapps pico & addon su & it works great. No official LOS 14.1 for that device. :(

***
[Galaxy S III Original Android Development] CelticWarrior:
I have the last TWRP 3.2.1.

Previously ROM: Nameless Androi 6.0 (Marshmallow)

Installed as in official guide lineage with cache, dalvik, data swipe by recovery .

I have installed Magisk v. 14.5

:rolleyes:
[Galaxy S III Original Android Development] curiousrom:
Black Screen Freezing, NAND Trimming & Clean Install

Thanks for the info. So the differences between you & me is that I first Format Data then wiped & rebooted to recovery as per linked TWRP guide before installing LineageOS & no Magisk.

A magisk search in this thread.

*****

NAND Trimming

I suddenly got some daily black screen freezing problems more & more when running a custom NeatRomLite Samsung based 4.3 ROM on my S3 i9300 after years of using it without any problems & that's what got me to try Lineage 14.1 in the first place 5 weeks ago.

I also got some freezing problems after a messy first LOS install so right after booting in a new clean LineageOS install I ran this sequence 4 times to try to fix the random freezing problem as recommended by several S3 users in this thread:

Dummy file Generator > Internal memory > (keep file size default) Generate dummy files until Storage is full. The app may seem to freeze because of damaged memory blocks before reaching 100% full so wait 10 minutes and if it does not get unstock hit Cancel and run it again & it will get higher the next time you do it.

Delete all the dummy files. Close the app.

Run Trimmer (helps to restore NAND Chips performance).

Repeat both apps 4 times to catch more damaged blocks. (screenshots)

Read the 2 apps reviews by S3 users.

I also replaced my broken plastic power button jammed in the depress position & bought a new OEM USB cable as it was also freezing when charging. No more freezing since a couple of weeks. :good:

***
[Galaxy S III Original Android Development] crisis_trustee:
Wait lineage-15.1
[Galaxy S III Original Android Development] CelticWarrior:
News

I tried to uninstall Magisk and WiFi widget.

I installed addonsu lineage 14.1 .

The issue is solved :D
[Galaxy S III Original Android Development] minealex2244:
I wanted to tell you to not use Magisk but you already figured it out. I only want to highlight that this is a possible fix to this kind of issues.
[Galaxy S III Original Android Development] curiousrom:
Kernel Recommendation?

Well "thanks to info i was given today..." is not very informative to say the least. :rolleyes:

So doing some detective work that download link comes from the [SLIMROM] [7.1.1] [Unofficial] thread, posted by a user who kind of taken over the development of that ROM as the OP is gone AWOL.

It seems that he uploaded a kernel that an other user made by modifying a Boeffla kernel.

"...ive not had any problems at all..." - You installed & tested that kernel on a modified [SLIMROM] [7.1.1] [Unofficial] less than 24 hours ago. That's not solid enough to be recommended in a Official Lineage thread without any info or links or caveats IMO.

I don't doubt your good intentions but it should be done properly with links & attribution. ;)

23 December 2017:
[Galaxy S III Original Android Development] curiousrom:
I don't know anything about Magisk but for those who would like to try that kernel: [2017.12.22] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] > Installation Instructions > "If you plan to flash a custom kernel, flash it AFTER installing Magisk".

Edited to add:

I'm just saying that instead of just posting a kernel download link you could have quoted the post so the user is notified and we can get more info about it or when crediting a person add @ before his user name for the same reason as well as creating a link to his profile: [MENTION=7907521]A$teroid[/MENTION] instead of a$teroid for example.

Have a merry whatever!

***
[Galaxy S III Original Android Development] multiwirth:
Running latest build with boeffla kernel and my phone freezes every time i try to shut it down from power menu.

Reboot and stuff works fine
[Galaxy S III Original Android Development] MrDSM:
I don't have any issue with the last build and the last beta beoffla kernel.
[Galaxy S III Original Android Development] :
Wifi issues

Hi everyone,

since around one month I have issues with wifi! :-/ My S3 can't connect to most wifis. It works with the wifi at university but apart from that, I wasn't able to connect to any other router yet. As it's able to connect to the wifi at university, I guess it shouldn't be a hardware issue.

As I already mentioned, the problem occurred around one month ago and all the latest updates didn't fix it. My phone can find all the wifis and I can see all the SSIDs, but as soon as I try to connect, it says "connecting" for maybe half a second and then "saved" or sometimes "disabled". That also appeared if I try to connect to wifis, that aren't secured with passwords. I also already tried a clean install with wiping data and cache and installing again the newest build, but still I can't connect.

Is someone else having that kind of problem? Or can someone tell me where to get a build from around September or October, when the problem didn't occur on my phone? Life without wifi really sucks! :(
[Galaxy S III Original Android Development] Simon_29:
Try to give your device a static ip in the wifi settings of your S3.

I never had such a problem before but I faced some problems with DHCP.
[Galaxy S III Original Android Development] g104:
+1
[Galaxy S III Original Android Development] :
Already tried to do that too on two different routers, doesn't work either.
[Galaxy S III Original Android Development] JosVermeulen:
Is there a reason why there hasn't been a nightly since the 13th?
[Galaxy S III Original Android Development] curiousrom:
S3 i9300 Wifi Can't Connect - Hardware?

I have zero Wifi problems with lineage-14.1-20171213-nightly-i9300 after doing a LineageOS super clean install + gapps + LOS addon su. 100% stock, no custom kernel, no Magisk, no Xposed, no modifications of any kind, no "speedup" or wifi "boost" apps or wifi widgets or Wi-Fi hacking apps.

You could try the basic: Settings > Wifi on > Settings (cog) > Saved networks > press on each of them and > Forget. Turn off wifi, turn off phone, wait a minute, turn on & after a minute try wifi to connect to a network with a strong signal.

You can try all the tricks to try to fix it here except Method A because dial codes do not work in Lineage (does the same as LOS Settings > Wifi > Settings (cog) > Configure Wi-Fi > Keep Wi-Fi on during sleep > Always - not good for battery life): [FIX][GUIDE] S3 can't connect to WIFI

As you can read in that tread some users ended up repairing the wifi chip or replacing the motherboard after everything else failed.

You could try running the free Logcat Extreme > + > Settings > Priority level > Errors, right after failing to connect or MatLog: Material Logcat Reader wich shows a wifi tag on the left side of the lines.

We don't know the history of your phone & if it was repaired it's very possible that the wifi antenna was not properly connected or the antenna's female motherboard side connector was broken which is easy to do or the antenna could have been pinched when putting back the plastic midframe..

See step 20 of this iFixit S3 repair guide (antenna & connector spare part} & my attachment.

You could also try Wifi fix mac-address change trick.

So you said you tried the Lineage Wifi Network Reconnecting Bug Workaround?

Obviously you could flash a stock Official Samsung ROM (Spain Orange 2016 is the most recent) with Odin and see if it fixes the wifi problem.

Just curious, could you check your S3 wifi chip model by navigating here with a root enabled explorer & open as text: /data/.cid.info. Mine says semcosh which is made by Samsung Electro-Mechanics CO.

"... "connecting" for maybe half a second and then "saved"..." - Happens to me when I try to connect to a very weak wifi network signal instead of the strong network I am currently connected to. If you are very close to a router like 1-2 meters and can connect but not when further away that could be a sign of bad antenna or wifi chip.

Please report back if you fixed your Wi-Fi problem or not. :cool:

***

Probably the war on Xmas lol.

***
[Galaxy S III Original Android Development] fir1996:
Our device was removed from the official lineage 15 because there is no maintainer for our device !

https://www.lineageos.org/Changelog-15/

???

Hope [MENTION=5405215]forkbomb444[/MENTION] could look at it.
[Galaxy S III Original Android Development] JosVermeulen:
Where do you read that in that post? Only thing I see is dropped support for the i9305, not i9300.
[Galaxy S III Original Android Development] minealex2244:
That's not even true for 3 reasons:

1. There is no LineageOS 15.0 build roaster list of devices in that article!

2. i9305 is not equal to i9300. Did you know that? No? Now you know!

3. No maintainer?! Where did you read that? Not even that i9305 had that statement! It was removed because of outstanding bugs! Read carefully next time and don't inform us wrongly.
[Galaxy S III Original Android Development] curiousrom:
Perfect thread for LOS 15 i9300 dreamers group therapy: [LOS15] Android Oreo unofficial? :D

It's not very nice to pressure [MENTION=5405215]forkbomb444[/MENTION] in his Official LOS 14.1 thread IMO. :rolleyes:

I'm thankful for the work he did so far, making our devices more fun to use.

***
[Galaxy S III Original Android Development] MrDSM:
Hi,

I have lineageos 14.1 with beoffla kernel, eveything is working fine, but sometime the phone is a little bit slow with transition from application to another, is there any parameter that make the rom more smooth.

Thanks.
[Galaxy S III Original Android Development] JosVermeulen:
Issues with Boeffla kernel shouldn't be asked here, but on the Boeffla thread (if there is one). This is about stock LineageOS.
[Galaxy S III Original Android Development] LuciferIII:
Happens sometimes for me when battery is really low.

So yeah, maybe your battery is dying.
[Galaxy S III Original Android Development] minealex2244:
Disassemble the phone and check all the contacts. This issue is happening when I'm having low battery and rarely when I'm using something related to media intensively (HwComposer issue).
[Galaxy S III Original Android Development] MrDSM:
Hi,

When a milestone or final version will be released ?

Thanks.
[Galaxy S III Original Android Development] minealex2244:
Never. Only nightlies.
[Galaxy S III Original Android Development] eriol1:
That's nor entirely true.

There will be a final (nightly) version of LOS 14.1 when we move to official LOS 15.1 :p
[Galaxy S III Original Android Development] minealex2244:
Haha :D I wanted to mention it but I wasn't sure. Enough with joking. He asked for a stable version but they are no longer doing final versions. It's too hard to decide what means final. There are too many issues so a final version is pretty unlikely to happen.
[Galaxy S III Original Android Development] drakenborg:
Hi,

I have a little problem with the latest build.

The viber messages did not arrive just in time, only 10-15 minutes or more time later, when the phone is on standby mode.

Do you have any idea why?

I am using the latest build with ROM stock kernel.

Thanks in advance!
[Galaxy S III Original Android Development] yoahmad1995:
You might be using apps to prevent Viber from running in sleep mode.

Maybe greenify or amplify
[Galaxy S III Original Android Development] qb74:
Did Forkbomb stop development on our device? His commits on LOS gerrit are all abandoned.

What's happening? D:
[MENTION=5405215]forkbomb444[/MENTION] any info?
[Galaxy S III Original Android Development] minealex2244:
Yeah, I have this question too :( I didn't see any movement in his repos for S3. I think he left S3.
[Galaxy S III Original Android Development] SALL666PL:
I have a problem ... the phone does not go to wake up ... the notification diary is scattering, but you can not turn it on a black screen and that's it, it happens a few times a day ...
[Galaxy S III Original Android Development] LuciferIII:
Do you have Magisk?
[Galaxy S III Original Android Development] nNeFeroN:
He is working on kernel...
[Galaxy S III Original Android Development] acroreiser:
Try to flash this -> https://xdaforums.com/galaxy-s3/development/kernel-koffee-t3728423
[Galaxy S III Original Android Development] mirhl:
Just FIY Simon is totally absorbed into the development of postmarketOS.

Which yes, eventually is likely to also benefit android someway - but not for the moment tho.