yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] curiousrom:
Messy LineageOS Install - Volume Steps & Ambient Display

If you do not follow the post #1 of this thread or the LineageOS i9300 install wiki or this simplified installation guide that I wrote for Windows users S3 i9300 LineageOS Super Clean Install & Samsung Firmware that all say to first update the Recovery then install Lineageos + Open GApps ARM one after the other

in that exact order

before rebooting the first time then expect problems.

Updated TWRP is required to avoid installation problems as well as for the OTA built-in LineageOS Updater automated Recovery script to work. See step 4 in the attachment.

You should start over with a clean install IMO.

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

Volume Steps & Ambient Display

That's all fluff IMO. I prefer the clean Official LineageOS + it's monthly security patches + it's OTA update and would be curious to compare RAM & battery usage when rebooted in Safe Mode to eliminate user installed apps from the equation.

I counted in LineageOS 14.1 for S3: Volume button: Media volume 15 clicks from 0 to 100%, Ring, Alarm & Notification 7 clicks. Plus you can long press the button or tap & slide with your finger on the drop down volume curtain that appears when pressing the Volume button to get exactly what you want instead of clicking up to 30 times as your screenshot shows.

The Settings > Display, LiveDisplay, Status bar & Buttons options are plenty for me.

I did not research the subject but maybe there are some mods or apps that could work on LineageOS to add those tweaks. Search example: site:xdaforums.com ambient display

Edit: [MENTION=7513127]Nobby1960[/MENTION] I just tested this & it works on my S3 i9300 LineageOS 14.1: if rooted using BuildProp Editor, adding to the bottom of /system/build.prop: ro.config.media_vol_steps=30, Save and rebooting gives you 30 steps for the Media volume. Add this if you also want 30 steps for Call volume: ro.config.vc_call_vol_steps=30.

Note that those mods will not survive a LineageOS update & must be done every time afterwards.

Anyway Thanks :good: for reporting back with the correct info & screenshots. :cool:

***
[Galaxy S III Original Android Development] Properjob70:
It was a clean install using the advice in post #1 including loading both ROM and GApps, then wipe before exiting.

It was the GApps screen that foxed me. The way the radio buttons work is not my favourite so for some reason it linked onto the ARM64 version? Never mind - I got there in the end. I've loaded up the apps I want to use as a travelling phone and (unlike the CM13 one) it isn't bootlooping. So far so good. I will use it in country in about ten days.
[Galaxy S III Original Android Development] curiousrom:
Re: Messy LineageOS Install

So you did that after each time you tried to install the wrong Open GApps version?

I which tutorial did you read to "then wipe before exiting..."? You have to either Format Data as I suggest + wipe stuff before flashing LineageOS and if you want the optional Open GApps and LineageOS' su addon for ROOT.

Wiping afterwards is not required nor necessary.

Edit: I just noticed that the Install LineageOS on i9300 tutorial now also recommends to Format Data like my tutorial. :highfive:

Before as seen in https://web.archive.org/web/20170322185017/https://wiki.lineageos.org/devices/i9300/install

Currently:

From this TWRP FAQ page:

***
[Galaxy S III Original Android Development] Properjob70:
Terminology problem. TWRP looks after you here.

You wipe using recommended TWRP method before installing ROM & GApps.

After installing zips within TWRP there is a button placed prominently to tell you to wipe cache/dalvik. The other button on that screen is reboot (into system).

One of the installation tutorials (don't remember which) stressed that this cache wipe should be done to avoid ongoing problems once you boot into your shiny new firmware
[Galaxy S III Original Android Development] curiousrom:
That does not make sense. Why would a clean LineageOS install on a clean wiped and/or formatted device put some destructive garbage in cache so to create problems afterwards. :D

A button does not mean that you have to blindly press it. I hope that Trump knows this. :eek:

***
[Galaxy S III Original Android Development] heisenmark:
Hi guys, I installed lineage 14.1 two days ago and everything works fine. I just wanted to refine RAM usage, so I'd like to know if I can safely disable two services: 1)android services library ; 2) cell broadcaster. If yes, is there a way to disable them without installing third-party apps (I can't disable them from settings>apps because the option is greyed)? Moreover, is it safe to remove wakelocks, run in background and on boot for gplay services?
[Galaxy S III Original Android Development] Properjob70:
https://lineageosrom.org/install-lineageos-twrp/

See step 7....
[Galaxy S III Original Android Development] Properjob70:
No it was not blind faith in some rando. It was on the Lineage Wiki. One deviates from the steps given at ones own risk.....

Basically it said install the ROM & Gapps at the same time from recovery. Don't iinstall ROM, boot, then recovery, then GApps. Or you will end up with problems. As my CM13 kept bootlooping the last thing I wanted was more time solving more problems.

After doing ROM & GApps it said wipe cache/dalvik before rebooting. TWRP provides this facility at this point. I did what it said.
[Galaxy S III Original Android Development] vege666:
I've tried the following:

-installed XXUGND1 modem

-installed XXUGOK1 modem

-installed UBUGNK1 modem

-installed I9300XXUGOE1_I9300ITVGOE1_ITV stock firmware (XXUGNB1 modem)

-installed cm-13.0-20161220-SNAPSHOT (XXUGNB1 modem)

Problem persists: voice and sms don't work, data does.

From SIM status display (with CM13) under "Service state" it says "Voice: Out of service / Data: In service".

Iliad SIM works fine on a Galaxy S2 (i9100, with both stock and custom firmware) and on a Galaxy Trend Plus (S7850, with stock firmware), and they're both older smartphones than i9300.

SIMs from other operators work fine on my i9300.

Does it make any sense to test an old modem version? Any suggestion? :eek:
[Galaxy S III Original Android Development] Nobby1960:
Good idea to editing the build.prop file with the volume levels. I often use ambient display when my S3 I9300 switched to mute lies in sight on my desk. Only the standard brightness level is too dark for me and the display time is too short to take right notice. I set the brightness level up to 150 and the lighting duration to 5 seconds. Is there something synonymous with the build.prop possible, cause the feature itself is already built in from Lineage?

At the moment I'm using an ancient AICP ROM from 11/2017. It is actually running quite well, better than the final RR 5.8.5 ROM. This has an annoying bug on phone calls with the volume. :victory::D
[Galaxy S III Original Android Development] heisenmark:
Hello, I'm an Iliad customer from Italy. I used the SIM both with Resurrection Remix 5.8.x and Lineage 14.1, and everything works. My modem version is XXUGOK1. In both cases the only thing that didn't work on first boot was data, but after manually configuring APN the problem vanished. I don't know what is the cause of your problem but if you need help I'm here
[Galaxy S III Original Android Development] the-spea76:
Hi. First of all thank you for this ROM. I installed it yesterday afternoon and until now it's working great.

2nd: how to make a print screen pls?
[Galaxy S III Original Android Development] Nobby1960:
Press the power key and volume down (volume minus) at the same time. The screenshots were saved in the folder Pictures/Screenshots.
[Galaxy S III Original Android Development] the-spea76:
Thanks
[Galaxy S III Original Android Development] vege666:
I tried the same SIM and it works. I tried another Iliad SIM on my i9300 and it doesn't work.

This might be the problem: this phone's IMEI was lost long time ago due to no EFS backup, and therefore it has now a different IMEI.

Weird thing is that phone works fine with SIMs from other operators (much older than Iliad).

Thanks for your help.
[Galaxy S III Original Android Development] heisenmark:
Any help?
[Galaxy S III Original Android Development] 239:
If you want a stable system then leave it as it is.

If you want to experiment then do it but leave the idea behind that you are "optimizing" the system on this experience level.
[Galaxy S III Original Android Development] Psycho103:
What is best fix for "Can't Connect to Camera" bug?
[Galaxy S III Original Android Development] karpacha:
I have the same problem and I have no idea.

Someone suggested this app: https://f-droid.org/packages/info.aario.killcamera/ but I haven't tried it yet.
[Galaxy S III Original Android Development] dev.xda:
If possible deny:

* stay active

* run in Background

* start on Boot

for every camera app.
[Galaxy S III Original Android Development] pascua28:
Copy the files from /system/vendor (not sure about the exact location, it may be on a subfolder as I don't have the phone now) that contain "Slim" and paste them to /data/cfw/
[Galaxy S III Original Android Development] dev.xda:
> Battery Drain?

> Try updating LineageOS to 2018-09-13. BTW I did not have any battery problem with build 2018-09-06.

With 20180913 drain is as it used to be - OK again.

> Have you tried BetterBatteryStats to troubleshoot your battery drain problem? Check the If you need help chapter in post #1 of that thread.

No. I didn't change anything except updating to 20180906 as i do every week.

> And use the HockeyApp in post #2 of that thread to get the most recent free XDA version which is 2.4-262 @ the present.

Why? I use an ancient Tapatalk 2.4.12 with XDA.

> Check also this post: S3 Lineage Battery Drain Troubleshooting & Optimization.

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

***[/QUOTE]

Yes. Fixed with update to 20180913.

Thanks a lot.
[Galaxy S III Original Android Development] Psycho103:
Slim files are already there in /data/cfw
[Galaxy S III Original Android Development] curiousrom:
LineageOS S3 i9300 2018-09-20 - Another Build With No Changes

With LineageOS 14.1 reaching maturity & the bulk of developers moving on to 15.1 & 16.0 one can expect less changes in the updates which the LineageOS system keeps on building automatically every week even if there are no changes.

We may expect some monthly security patches, some bug fixes & some commits cherry picked from 15.1 but not every week like in the beginning of LOS 14.1.

So the suggestion is to always check in https://download.lineageos.org/i9300/changes/ or in Settings > About phone > LineageOS updates > 3-dots > Show the changelog before wasting your time downloading & installing a build with no changes compared to the 2018-09-13 running on my S3 like the LineageOS S3 i9300 dated 2018-09-20 example in the screenshots.

Settings > About phone > LineageOS updates > Check for updates will offer to download a build with zero changes if the date stamp has been changed. If the update is the same size as the build you are currently running it might be a clue but some changes are for small files and the only way to make sure is to check the Changelog.

I created a thread here in the LineageOS subreddit Why Make LineageOS Builds With Zero Changes? with the suggestion of "...do a check & if there is no changes then skip making a useless build for a given week?" and the reply in that thread by [MENTION=2195612]zifnab06[/MENTION], one of the Lineage Directors and in charge of the build scheduler was: "It's an item on a backlog a few miles long. Previously (with cm) this lead to a massive influx of "where's my build"."

The suggestion of having the Lineage Updater reply this did not stick: No new build this week. Your device is up-to-date!

There is a September 2018 Security patch for 14.1 in the tubes but it's still in the Code Review stage @ the present and will probably be Edit: now Merged & included in the next update.

***
[Galaxy S III Original Android Development] Marc0601:
Replace existing files
[Galaxy S III Original Android Development] the-spea76:
Good night. I saw the update of 20/09 and I tried to install it but it doesn't work. I''m download it and once in TWRP for the update.....failed
[Galaxy S III Original Android Development] the-spea76:
Thanks very much. I will try and keep inform
[Galaxy S III Original Android Development] the-spea76:
Regarding the update, the error message is this one. I have the root.
[Galaxy S III Original Android Development] curiousrom:
Re: LineageOS Update Fail? TWRP Error 7

No recovery log + no troubleshooting Info + no sha256 check = no solution (besides don't update or wipe & clean install).

Maybe somebody else wants to take a stab in the dark. :eek:

In your TWRP screenshot it says Error 7 can't install this package on top of incompatible data which is a generic message with several possible causes.

***
[Galaxy S III Original Android Development] notstpaul:
What a difference it makes using the Google Now or Pixel launcher. I've always used Nova, but the phone was so laggy. I'm using this phone again because my new one is in for repairs. No problems, just the launchers don't have unread count badges.
[Galaxy S III Original Android Development] the-spea76:
Ok thanks. So wait and see and maybe next time
[Galaxy S III Original Android Development] curiousrom:
LineageOS S3 Update 2018-09-27 & Security Patch

FYI the LineageOS 14.1 S3 Update 2018-09-27 is worth it IMO because of the September 2018 Security patch & 15 other changes including several related to Bluetooth as seen in Settings > About phone > LineageOS updates > 3-dots > Show the changelog or in https://download.lineageos.org/i9300/changes/

The update went very smooth using the built-in LineageOS OTA updater on S3 i9300 (previously 2018-09-13) + Open Gapps ARM Pico + Lineage ARM super user add-on with Recovery twrp-3.2.3-0-i9300.

The automatic reboot to full system was quite long, almost 10 minutes.

***
[Galaxy S III Original Android Development] Nobby1960:
The Nova launcher normally shouldn't make lags on on the S3. I've been using it for a while now with a Lineage-based Nougat ROM, together with Tesla Unread to have unread marks. The reaction is snappy. Maybe you must reinstall Nova and make a fresh configuration.
[Galaxy S III Original Android Development] Ashraf Iraqian:
Hi

The problem is not using launchers it's our RAM and i am sure he is using apps using high RAM on the background like (Facebook,Messenger,UC browser..etc) i am removed these apps and my phone being so smooth.

yeah we need these apps for daily using but we should lose something to get another...
[Galaxy S III Original Android Development] Nobby1960:
That's right, 1 GB RAM is too litte for today's fat apps. I try too to run apps that use as little RAM as possible.
[Galaxy S III Original Android Development] sonvegeta:
About the Ram, there is a ram manager module for magisk that really works and make difference to the ram. Just install the module via magisk and, with the other matters, the overall experience should improve for you. Use the pugb module, not to play(because it can't) but to improve the ram even more with an aggressive script. The link is here
[Galaxy S III Original Android Development] DELLINSPIRON1958:
Hello

i just installed this rom but no gapps works: error code 64 unmomting / system, someone help me.

Thank you
[Galaxy S III Original Android Development] curiousrom:
Wrong Open Gapps - Error 64

"...no gapps works: error code 64..." - From https://github.com/opengapps/opengapps/wiki/FAQ

"#64 - Incompatible device architecture: Your device has been detected as having a different kind of architecture then the package used. Like arm vs arm64 vs x86 etc. Install the correct Open GApps version for your device.

Solution: Use a compatible version of the Open GApps package for your device's architecture."

You need to install Open Gapps ARM 7.1 - for S3 & LineageOS 14.1.

I prefer the smaller Pico variant because of the S3's limited RAM and anyway you can always download extra apps in Play Store if you wish. See Open Gapps Package Comparison (Variant).

It needs to be done immediately after flashing LineageOS & reboot after. If you already rebooted after LineageOS you need to do it again: flash LineageOS then flash Open Gapps ARM 7.1 then Lineage su addon if you wish then reboot to system.

The Lineage su addon can be flashed at anytime afterwards if you changed your mind.

See S3 i9300 LineageOS Super Clean Install & Samsung Firmware

***
[Galaxy S III Original Android Development] karpacha:
I just wanted to inform people who might want to change launchers from the default one to Evie. Don't do it.

It worked well and somewhat faster than Trebuchet for a while, but then it started to lag a lot. To the point where nothing but the background was loading and I was getting unexpected reboots.
[Galaxy S III Original Android Development] samustra36:
Camera not working on lineage 14.1

my camera is not working. how to fix?
[Galaxy S III Original Android Development] dana.marivani:
You can solve the problem with three simple solutions:

1-Use this app View attachment 4609493 Or download link directly from the Google Play Store

2-Enter your device settings>Developer options>Enable Local terminal

open Terminal>type su Enter > killall cameraserver Enter

3-Or reboot

And also add options 1 and 2 need to be rooted
[Galaxy S III Original Android Development] curiousrom:
LineageOS S3 Update 2018-10-04 No Changes - Feedback Please!

FYI the LineageOS 14.1 for S3 i9300 Update 2018-10-04 has no changes compared to build 2018-09-27 as seen in the attached screenshots so don't bother updating if you are running that version. More details about how to detect that here: Another Build With No Changes.

OTOH if you are running a build older than 2018-09-27 then it's worth updating as 2018-10-04 includes the updates as described in LineageOS S3 Update 2018-09-27 & Security Patch.

***

Feedback Please & Trimming Quotes

It's OK to ask questions but it's cool :cool: to give feedback about the reply you received. It's a way to learn if a suggestion was useful or not.

You can do that by hitting the Thanks :good: button which indicates that the reply was useful to you thus pointing to other users with a similar problem that the solution may also work for them. Besides collecting Thanks is good for the ego & is an encouragement to contribute more to the thread. ;)

Or you can do a quick reply & include a mention of the user that replied to you and he/she will get notified if you add a @ in front of his/her username like this: [MENTION=4122877]curiousrom[/MENTION] which also links to the user profile.

Or right-click on the Permalink of the post you are referring to and copy/paste that link in your Quick reply. It's the number on the right side of the post's date. For example top of this post:

Today, 06:13 PM | #5059.

Or reply to the solution post with quote as it will send a notification to the poster and includes a link to the original post (the colored > next to the user name).

You can trim the quote, especially if it was a long post like I did below: after hitting the Reply button of the post you want to quote, just delete some stuff between the two pair of quote brackets like [ QUOTE=DELLINSPIRON1958;77751820]...no gapps works: error code 64... delete some stuff...[/QUOTE ]

***

***

***

***
[Galaxy S III Original Android Development] the-spea76:
I uninstalled the past version I had and I'm currently with the nightly of the 27.09

I will check with the next update if I have the same problem.
[Galaxy S III Original Android Development] curiousrom:
Orphan Post

Read the post above yours again. If you don't do one of the 3 things I described then there is no link to the message or user you are replying to.

Your post is an orphan post lost in this big thread. So sad. :(

And I did not get any notification for it because of that. When replying to users who don't check the thread often it's important to get notified.

Anyway, Thanks :good: for the feedback. :cool:

***
[Galaxy S III Original Android Development] mont99:
Screen capture through any other third party app does not seem to work

So the OS to amazing. No doubt about that, but there is one certain issue that is bugging me out. I don't seem to be able to screen capture through any third party app. I also received an error from one of them stating that "the system returns image in unknown format". It also fails to connect to my HTS for screen mirroring.

Also other apps that deal with editing also seem have issues. Apps like timbre are unable to load the file from the SD card and WhatsApp is unable to crop videos.

Edit- I would like to add that the OS can see the HTS available for screen mirroring but is unable to connect (no error message)
[Galaxy S III Original Android Development] himmon:
Had the exact same issue when trying to install a pure clean build, tried previous builds of gapps and and even earlier builds of los 14.1, no go.

Factory reset and wiped data but still no go. Finaly found formatting system in advanced wipe in twrp fixed this issue.

Can now install latest aroma or pico gapps with latest los 14.1 after tons of trial and errors.

Good luck!
[Galaxy S III Original Android Development] curiousrom:
Re: Screen Capture & Open GApps Installation Error

I'm not sure I understand: if you mean screenshot the tiny & button saver Screenshot Tile [Root] includes a customizable timer & can make some screenshots that other methods cannot do as they close some popup windows and it is using only 2~3.5 MB in cached processes.

If you are talking about screen recording, the LineageOS built-in Record > video w/ or w/o sound works fine for me.

***

Open GApps Installation Error & Formatting in TWRP

Thanks :good: for the report.

You probably mean Format Data as I did not see any format system option in TWRP. The data partition is written to & erased all the time so it's much susceptible to errors than the System partition which is written to when flashing the firmware + optional Gapps & then it's mostly read only except for occasional advanced user tweaks but that's minimal.

That's why its better to Format Data instead of just wiping Data: to rebuild the file system including the internal sdcard which destroys encryption if any, to avoid any problems & start with a really clean slate as explained in S3 LineageOS Super Clean Install & Samsung Firmware step #6 with screenshots & link to a TWRP FAQ page w/ technical explanation.

Check also S3 Black Screen Freezing Fix - Sudden Death Syndrome as some S3's like mine have a defective eMMC chip & also some sectors can become corrupted over time as the device gets older.

***
[Galaxy S III Original Android Development] mont99:
The inbuilt screen recorder works like a charm, and so does the inbuilt screenshot functionality. This issue occurs when I try to use different app for the same. Furthermore apps that deal with screen mirroring also do not work. (Just saying if both the cases are related)

Also it seems that apps are not able to access the storage, in perticular the SD card. For example chrome is unable to download on the SD card but is able to in the internal memory. Edit :-unable to download in internal too.
[Galaxy S III Original Android Development] himmon:
Hi,

No, I meant as I said, wipe System partition in "Advanced Wipe" options in TWRP. I've always wiped data / factory reset myself as clearly required for a clean build however due to the gapps not installing unusually this time around, wiping the system partition as well fixed the gapps error which allowed gapps to install straight after the lineage 14.1 install. I tested Aroma and pico, both installing fine after the System partition wipe.