yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] baltics:
Yes.

---------- Post added at 07:51 PM ---------- Previous post was at 07:46 PM ----------

Well, it doesn't anymore because I switched the radio/modem to the recommended one.
[Galaxy S III Original Android Development] Ashraf Iraqian:
thanks mate You helped me in your post at that time and it is works fine to yet. :)

regards
[Galaxy S III Original Android Development] steno66:
Hi all. I have last nightly 31.1.2017. I tried to install addonsu-arm-signed but I have error 4. When I try to install 64 bit version, installation go fine but root don't work. Any idea why?
[Galaxy S III Original Android Development] notstpaul:
Ignore the error 4, root is enabled anyway after flashing, despite the error message.
[Galaxy S III Original Android Development] Ashraf Iraqian:
Hi guys

i have installed boeffla kernel latest beta version to fix my charging issue!

can you tell me why my AC charging Rate not stable! :( it is should be 1100 mA

check charger info in screenshots
[Galaxy S III Original Android Development] Gato177:
Check your private mailing list
[Galaxy S III Original Android Development] steno66:
Thanks, works fine
[Galaxy S III Original Android Development] g104:
your hardware issue is related to the charger not kernel.
[Galaxy S III Original Android Development] broken-arrow:
[MENTION=5405215]forkbomb444[/MENTION] No bug report like other build?

And you don´t to bugfix or you do?

Is not soo fun go through Reddit to find bug on your build, then you have this thread for this reason.

I not dear get to move from 14,1 CM get (particular then is no bug reports), is work much better and 13CM and 12CM (i not need to dirty flash almost every day). same build has work at same at is was relished in 24/12, no performance degrade like build before.
[Galaxy S III Original Android Development] Android-Banjarmasin:
Tick the "Ignore unstable power"
[Galaxy S III Original Android Development] mohammad607:
Hi.

i have last version nightly 31/1/2017.when to dirty install error 7

i have twrp v3.02.2 & 21.1.2017 unofficial

plz help me
[Galaxy S III Original Android Development] Simon_29:
I have got the same error even the md5 fits. Maybe the author of the nightly can tell us how he made the rom.
[Galaxy S III Original Android Development] minealex2244:
I don't even care about it. It will need porting and I'm concentrating on fixing bugs and not on performance.
[Galaxy S III Original Android Development] Gizmotech:
I came from stock JB about 6 weeks ago which I had for years. This issue was not there with stock JB and only started when LineageOS went on. Nevertheless, I'll flash back to stock when I have a bit of time on my hand and report back.
[Galaxy S III Original Android Development] muhaiminz91:
Try turn off On-Body detection, it happened to me when I turn it on. No black screen problem after turn off it.
[Galaxy S III Original Android Development] MoHuToP:
From the middle of September this bug occurred in my i9300 and n910f too. It's related to the data/ wifi . When any data connection is available, there a srs chance to wake up bug appear. In my n910f, this was resolved few builds back. It's not hardware issue. When there is not any connection to the internet, everything is good. Future help will be appreciated. Regards
[Galaxy S III Original Android Development] curiousrom:
Wifi Network Reconnecting Bug

From what I read in this thread it's not about "any connection to the internet". It's about being connected to a Wifi network, getting out of range and getting back in & trying to reconnect. A DHCP related problem & happens to some users on some networks.

See Wi-Fi Causing Reboot, Freeze, Crash Bug Workaround - Static IP
[Galaxy S III Original Android Development] MoHuToP:
Okay, but with activated mobile data, the problem still occurred.
[Galaxy S III Original Android Development] TD kai:
Front Camera issues

Hey guys, I really like this ROM (Lineage OS 14.1), Everything works fine on my S3 I9300,

but i cant access the stock camera app, it crashes every time i open it.

So i installed the Google Camera, and although it kinda works, it crashes every time i open the front facing camera and i have to clear the app data and restart the phone for it to work again.

and also my flash doesn't work,

really need assistance, please help.
[Galaxy S III Original Android Development] nobuteru:
I read Android 8.x will be have a "GO" version, that can be activated by a flag or option during compiling , will be used by Lineage project for S3 and older smartphones to make it more faster.

It is designed for 512 MB - to 1 GB RAM
[Galaxy S III Original Android Development] LuciferIII:
What Google camera version do you have?

2.7 should work fine.

Any newer version will either give you crash on front camera or won't even start.
[Galaxy S III Original Android Development] minealex2244:
I know that but do you know whether LOS supports lightweight GApps (a special GApps build)? I think that the answer will be no. Also there are lots of disadvantages. See some of them here: https://www.google.ro/amp/s/www.androidauthority.com/android-go-773037/amp/

We can add to the list: incompatibility with a lot of apps, broken LOS features and maybe more. S3 was never intended to have Android O so Go Edition it's a dream and maybe in one day it will be a real dream. But you never know.

---------- Post added at 15:29 ---------- Previous post was at 15:26 ----------

Don't use latest version of Google Camera. Use this version: see this post

Also try to inspect the camera connector for front camera. If it is not connected very well to the motherboard then every camera app will crash when checking for frontal camera or maybe it will tell you that you couldn't connect to it.

Personally I'm using Snap camera I extracted from an LOS build for OnePlus One. Here is the link: https://xdaforums.com/showpost.php?p=71560252&postcount=1439
[Galaxy S III Original Android Development] g104:
Camera Restarter
[Galaxy S III Original Android Development] nobuteru:
Sorry I didn't know that...

If I can ask, Lineage 15 will be based on Android 0, is it correct? no Lineage 15 for S3 in the future?
[Galaxy S III Original Android Development] minealex2244:
I don't know what Simon will do but I'll try to give you LOS 15.0 as soon as possible.
[Galaxy S III Original Android Development] TD kai:
i'm using google camera version 2.5
[Galaxy S III Original Android Development] curiousrom:
Front Camera Working & Back Camera Flash

Front camera, back camera & flash working fine on my S3 I9300 both in stock camera app & free & fun Open Camera running lineage-14.1-20171206-nightly-i9300-signed.zip, gapps nano, addonsu-14.1-arm-signed.zip, root & no custom kernel. Cat at dawn front camera attachment for your viewing pleasure.

"really need assistance, please help" - Well you got several suggestions but did not give feedback on them. Especially this one if your S3 was repaired:

It's easy to disconnect/reconnect the front camera connector right after removing the plastic midframe. See black rectangle with orange trim bottom right of Step 14 & 17 in this ifixit Samsung Galaxy S III Front-Facing Camera Replacement guide.

If your front camera & back camera flash were working on an other ROM maybe you could go back to test it again.

Edit: Does > Statusbar > Tiles > Flashlight work for you?

***
[Galaxy S III Original Android Development] TD kai:
i tried using the snap camera, it takes blank pictures, still the front facing camera doesn't work on it as well...

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

I tried it, still the stock camera doesn't work,

and on Google Camera version 2.5, the front camera doesn't work

---------- Post added at 01:31 PM ---------- Previous post was at 01:07 PM ----------

sorry for the delay, i'm currently inspecting the hardware...

i will give you a full feedback afterwards
[Galaxy S III Original Android Development] Ertishop:
Is there a fix for the mobile data, i did check my APN settings are right but coudnt make it work.
[Galaxy S III Original Android Development] ArdaCsknn:
Delete it all first and then manually add it yourself.You can check your APN settings from your GSM Operators site.
[Galaxy S III Original Android Development] hamedvojdani:
sound and media problem

hello every body,

before 2017-12-22 nightly had sound cut problem: while playing on music app if screen goes off (by lock button or timeout) had sound lag (or cut) for around 0.5 sec and continue again.

after 2017-12-22 nightly in addition to above issue, i have new problem, most videos in telegram or quick pic does not play and app freeze and then kill dialog appear, after that i have no sound form device(no music sound, no notification and ring sound), till restart the device.

and mention that before flashing zips i wipe davlik and cache. wiped system too on first flashing lineage 14.1

thank u for any suggestion.
[Galaxy S III Original Android Development] qb74:
1st issue is a standard issue of official LOS, don't mind it.

2nd issue is due to the fact we don't have HWC yet, [MENTION=5405215]forkbomb444[/MENTION] has a experimental build with a working HWC up, you could try flashing it and report your findings/bugs to Simon (most people can't even boot, so keep that in mind)
[Galaxy S III Original Android Development] Simon_29:
The first issue isn't related to LOS in gerneral (at least not for all the other devices i tested). I reported it a while ago.

https://jira.lineageos.org/plugins/servlet/mobile#issue/BUGBASH-31
[Galaxy S III Original Android Development] hamedvojdani:
thank u,

so there is no chance for this problems to be solved whiten 2 month or less?
[Galaxy S III Original Android Development] qb74:
yeah, forgot to mention the fact that it's device specific :P

Honestly, quite a few of us are waiting for a 'properly' working ROM. The second issue you have is what keeps me away from Nougat builds.

I'd say in 2 months we'll definitely get a new experimental build, how long it'll take for the HWC to be fully completed though, is all up to forkbomb and tdcfpp.
[Galaxy S III Original Android Development] Tech-Ina:
You say that the lack of HWC keeps you away from Nougat builds. Is there a ROM with fully working HWC?
[Galaxy S III Original Android Development] qb74:
touchwiz based and cm11-based ROMs (most of them at least) along with nameless 6.0.1 (im not entirely sure if this is working fully, even though this is my main driver, camhal isn't fixed here because they dont care about the i9300)

then there's the obvious experimental LOS14.1 that's probably 99% working with a few quirks, the main one being not being able to get it to boot on most devices :P

EDIT: keep in mind though, nothing thus far has got close to stock/touchwiz stability, even cm11-based roms don't have it 100% working (iirc, playing videos through browser is one issue on cm11-based roms? correct me if i'm wrong here, i know there's like 1-2 issues that haven't been ironed out)
[Galaxy S III Original Android Development] ArdaCsknn:
Yeah even CM 11 doesnt have stable HWC or doesnt even have.The experimental build is the most stable rom I have ever tested after Sam based roms.There are some black screen issues but you can use it as a daily driver.
[Galaxy S III Original Android Development] Tech-Ina:
I see, thanks! Hopefully forkbomb will be able to fix the HWC and we'll get it in the official builds, meaning that Boeffla Kernel will also work with it. Imo no ROM comes close to the smoothness of the 7.1.2 experimental build. I was running it for a while but then switched back to the official builds, because I really missed some of the enhancements of Boeffla Kernel, especially the sound.
[Galaxy S III Original Android Development] qb74:
You're one of a few that can run it, grats! :D

For sound, you could take a look at Viper4Android, makes the sound a lot better imo.

Boeffla will have to update his kernel once the commits from experimental go official, so that'll take a while as well :D
[Galaxy S III Original Android Development] TruthNZ:
Yeah, some of us can't even boot it (Murata chip :( ). But drooling over the reports I've heard from those who can.
[Galaxy S III Original Android Development] aldrin3010:
I don't think murata chip is the issue. Mine has murata chip but the experimental build booted successfully (I'm not using it now as I need to use tethering)
[Galaxy S III Original Android Development] kosmasgr:
Anyone on latest build with boeffla beta 5 ? I have some random reboots. Default settings on boeffla with zmoove battery yank governor
[Galaxy S III Original Android Development] minealex2244:
You shouldn't post that here. There is a thread just for Boeffla kernel!
[Galaxy S III Original Android Development] ArdaCsknn:
Yeah, my mothers S3 also has Murata chip and working as intended.
[Galaxy S III Original Android Development] matteo2:
Are there any projects for oreo on s3?

Inviato dal mio SM-G950F utilizzando Tapatalk
[Galaxy S III Original Android Development] Robert-R:
bootloop after app-updates

I'm considering switching over to LOS 14.1.

I was rather happy with CM13.0 as my daily driver, until a few month ago ever more app-updates resulted in a bootloop (e.g. Greenify and Wikipedia).

Question:

Are these bootloops after app-updates less likely on LOS 14.1?
[Galaxy S III Original Android Development] minealex2244:
Finally I built LOS 15.0 and here are the results: it didn't boot (as expected). I got stuck in the kernel. But don't worry. I messed up with the kernel and I'll fix it. I only want to get into the system bootloop (to know that kernel is working) or maybe it will boot up. The WiFi, Bluetooth, GPS, RIL, vibrator, sensors, audio, camera (only pictures) and some other things can be fixed then. I'll inform you about the news on this topic.
[Galaxy S III Original Android Development] LuciferIII:
I literally just took my sister's s2 (secretly) and tested Los15.1, it's really weird xD.

I was testing it out and for now it has lots of bugs but it was really cool to just see it in action.

Also, i have a s5 Neo now(Daily driver), but i still have my s3's.

I will still test out stuff, mainly because s5 neo has just 1 Lineage14.1 ROM, and the dev i currently in a little crysis wih his HDD's.

So yeah, i am still here :o

Ps: Yes i restored her s2 and she will never know :angel:
[Galaxy S III Original Android Development] TD kai:
THANKS GUYS:):), Turns out the camera connector was loose.... I actually bought a replacement front facing camera but i didn't even need it

Now everything works pretty good, i do get some camera clashes here and there, also some lags that i don't get on the stock ROM, but its not really that much of a big deal.

Now the only thing left is that Lineage OS 15 on S3 i9300, Can't wait...

THANKS AGAIN FOR THE ASSISTANCE:good::good::good:
[Galaxy S III Original Android Development] The Octagon:
Sorry for what is probably a very naive question, but would Project Treble be much more work to bring to the S3 than bringing Oreo from scratch? Would it even be possible?
[Galaxy S III Original Android Development] curiousrom:
Music Hiccup, Video Playback & Trim, Equalizer

I guess you meant 2017-11-22. ;)

Video playback working fine so far on my S3 I9300 in stock Gallery app's Video player, QuicPic & QuicPic opening video with stock Gallery app's Video player, ES Media Player, WhatsApp sent/received videos, in stock Browser video viewing YouTube, CNN, Reuters, Politico pages & YouTube app.

BTW check Settings > Personal > Privacy > Privacy Guard > QuickPic > Keep awake & Run in background by default which you can disable.

My I9300 is running lineage-14.1-20171206-nightly-i9300-signed.zip, gapps nano, addonsu-14.1-arm-signed.zip, root, no custom kernel & no mods.

This said stock Gallery crashed ("Gallery has stopped") after successfully using Trim on a video & saving it. It's related to external SD card as seen on the second attachment, a screen capture of the free Logcat Extreme > + > Settings > Priority level > Errors, right after the app crash. Restarting Gallery I could play the trimmed video. No crash when editing a video in the internal memory.

What kind of videos are causing you problems? Maybe you could use Logcat Extreme to troubleshoot. Did you setup QuickPic with password protected folders or cloud backup?

I have the same music playing hiccup when the screen turns off as you describe in 1 as well as when closing Gallery or taking a screen capture but I don't care much.

Well it works for me on the most recent Official LOS 14.1 2017-12-06 so maybe you could try it? ;)

Are you talking about the one with ads requiring BusyBox (yuck) & root? A search in Google Play returns 6 results currently.

Anyway LOS 14.1 for I9300 includes the AudioFX equalizer in which you can create & save custom presets & it remembers if you want it turned on or off for your headsets and with a separate settings for internal speakers. Less granular but clean & simple.

I have been using LOS 14.1 for 1 month, about 20 apps updates & zero boot loops so far. Can't predict the future yet. ;)

Oreo for I9300 is Off Topic

No disrespect intended but this thread is about the Official LOS 14.1 for i9300 & I am not really interested in getting notifications for your unofficial Oreo project blow-by-blow steps as you posted about it several times recently. Maybe you could start a thread for your project and link to it here or in your signature?

Great & thanks for the feedback. :good:

***
[Galaxy S III Original Android Development] skyleth:
Hi! I have a problem with latest build, well actually with any build, the app for my bank (ING) says the phone is rooted although i haven't installed the su addon.

I'm guessing this is because the system image is insecure or something like this. Is there a way to fix this? I really want to find a solution for this so i can use the nfc for payments.

Thanks in advance
[Galaxy S III Original Android Development] minealex2244:
Oreo for S3 is not offtopic! There are a lot of people interested in this subject. I can't create placeholder threads (don't you know the XDA rules?). But I understand... I won't give any new information about this. When something happens everyone should "feel" that somehow. Maybe it'll be a personal build...
[Galaxy S III Original Android Development] curiousrom:
Bank App & NFC Payments

Well you have 2 problems:

1- Your bank app probably requires the phone to pass Google's Play SafetyNet test. Free app SafetyNet Helper Sample shows that my S3 LOS 14.1 fails the 2 tests (attachment).

There are some tricks to try to workaround the problem but then there is problem #2. LineageOS opinion about it: https://www.lineageos.org/Safetynet/

Much more info here: Safetynet check, apps won't run on rooted devices. What IS CTS?

2- The NFC chip on the S3 I9300 probably does not support the required HCE (Hosted Card Emulation) to be able to make NFC payments. Free NFC Check app shows that my S3 i9300 LOS 14.1 does not support HCE as it never got a stock S3 Samsung Android 4.4 update (attachment).

*************************

I knew you would be offended. ;) Between a personal Oreo project blow-by-blow reporting in a Official LOS 14.1 thread & nothing there is a margin.

BTW could you trim the quote please?

***
[Galaxy S III Original Android Development] minealex2244:
Yeah, I trimmed it. I didn't tell you about all the steps from this project. I only posted a few minor things about what to expect in the new release. You should care about others and not about you. Others want information, you want nothing!

If my topic is offtopic then even HwComposer is offtopic!!!
[Galaxy S III Original Android Development] skyleth:
Thanks a lot for the reply, I'll take a look at everything you've written and see if there's any workaround. So far it seems to work with 4.4 touchwiz roms, but it would be nice to have a newer android version
[Galaxy S III Original Android Development] qb74:
1. Yeah, no.

The thing is, it isn't fixed and it won't be until HWC gets fixed. The media playback bug (literally no sound comes out of the device, no video/audio/notification/alarm) once the HWC crashes will persist till the commits from the experimental build go official. It doesn't even have to get triggered by playing content, you can just leave your phone idle for a while and it'll happen. Quite sure you can think of many scenarios where this would be inconvenient as a daily driver, which my S3 is.

2. I'm talking about this
[Galaxy S III Original Android Development] Noobkid77:
You upgraded ?? man I can't wait till I upgrade as well lol
[Galaxy S III Original Android Development] curiousrom:
Playback Blues

Well searching this thread with media playback bug qb74 I see that you posted 8 times on that subject going way back to April 13, 2017.

When was the last time you tried LOS 14.1 stock without any equalizer requiring BusyBox on top of the included AudioFX one? Did you install other mods like Magisk, Xposed or whatnot? Custom kernel? Themes?

As I said in my Music Hiccup, Video Playback post above I did not have any video & audio playback issues so far after 30 days on my S3 I9300 currently running lineage-14.1-20171206, gapps nano, addonsu-14.1-arm, root, no custom kernel & no mods.

Caveat: I know the S3 is old with limited RAM so I keep it mean & lean with very little stuff & services running in the background.

I know [MENTION=5405215]forkbomb444[/MENTION] is working on a [EXPERIMENTAL][7.1.2] LineageOS 14.1 for i9300 & read the thread & am thankful for the work but meanwhile I can enjoy the current Official 14.1.
[Galaxy S III Original Android Development] qb74:
Always ran stock on LOS14.1, didn't even know about half of the mods back then.

A lot of factors could contribute to the issue, namely my +20gb of media on sdcard, almost full internal storage most of the time (+10k pictures, mostly use phone for youtube/instagram/whatsapp/snapchat, i like keeping old pictures :p) and a lot of apps (at that time i used to have +100, now im at ~70)
[Galaxy S III Original Android Development] hamedvojdani:
yes :)

after update to 12/23 and i'll try video playback thing again.

thanks
[Galaxy S III Original Android Development] skyleth:
crap I'm having trouble installing latest nightly with nano gapps. I keep getting bootloop.

Tried different options:

1- wipe dalvik, cache, system, data and internal storage

2- install lineage os

3- install nano gapps

4- reboot

1- wipe dalvik, cache, system, data and internal storage

2- install lineage os + wipe cache

3- install nano gapps + wipe cache

4- reboot

1- wipe dalvik, cache, system, data and internal storage

2- install lineage os

3- install nano gapps + wipe cache

4- reboot

1- wipe dalvik, cache, system, data and internal storage

2- install lineage os + wipe cache

3- install nano gapps

4- reboot

The weird thing is I can restore stock 4.3 rom, or install back-to-n00t 4.4 or even latest hyper rom, but no LOS14.1

Tried redownloading the rom 3 times and checked the checksum and it was good.

Is there anything I haven't tried that you could think of? Do I need to format /system to f2fs?
[Galaxy S III Original Android Development] 239:
Wiped phone yesterday and installed latest build without issues. I would try again:

1) Reboot to RECOVERY after LOS / before GApps

2) GApps pico (ARM 7.1)

3) Without GApps
[Galaxy S III Original Android Development] curiousrom:
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.

Edit: TWRP 3.2.1-0 Released Dec 9, 2017 Changelog.

After Format Data & wiping, reboot to recovery before flashing LOS, gapps & addonsu-14.1-arm if want it.

I followed exactly this guide: How to wipe in TWRP properly? and the Installing LineageOS from recovery part of the wiki including step 10 & 11 for ROOT & gapps nano ARM 7.1 and not arm64 nor 8.

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

***
[Galaxy S III Original Android Development] skyleth:
Thanks! I installed slim rom without problem, then full wipe and install LOS and everything is working, don't know what happened :fingers-crossed: