yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Darth Bidder:
Is it better to download the latest release even if there's no changelog for it or is it going to be the exact same build like the last one that has a changelog?

I'm talking about the 08/23 and 08/30 builds.
[Galaxy S III Original Android Development] bejunk:
when thers nothing in changelog, its the exact same build. You can compare filesizes to see
[Galaxy S III Original Android Development] Blacksteelgrey:
without changelog, is the same build. so, don't worry about update
[Galaxy S III Original Android Development] karpacha:
1. Sometimes the Google Calendar events don't trigger notifications at the specified time. Usually they get delayed by a few minutes. If I wake the phone, I will get the notification immediately.

It seems to be more pronounced when having the Extreme battery saving option enabled, but today it happened on Performance mode as well.

I'm currently using the latest Google Calendar and LineageOS version August 9th, 2018, but this has been happening from the start. I've used the curiousrom guide to clean install official LOS, with gapps, without root. Kernel version 3.0.101-lineage-gb7ffe7f. I've switched to Evie launcher, if it makes any difference.

2. I've had the robotic voice problem, so I've switched to the recommended I9300XXUGMK6 modem.

The problem went away on normal calls, but when I'm connected through bluetooth in my car, I mostly get either the robotic voice or loud white noise once the connection is made.

3. A lot of the times when I open the Open Camera app it says "failed to open camera may be used by another application". The background is blank and I can't take a picture or record a video. I've tried 2-3 other camera apps and weird problems occur there too! The other apps usually don't even open or freeze when I switch to record a video.

I've tried rebooting the phone, but it didn't fix the problem every time.

4. Is there any other way to access logcat, if I don't root my phone? I've tried accessing it through my PC via adb, but the USB connection is not stable enough to do anything. I've tried different cables but to no avail.
[Galaxy S III Original Android Development] curiousrom:
Bluetooth Problem

You have Bluetooth problems when connecting to which device exactly?

"...LineageOS version August 9th, 2018.." - As you can see in LineageOS' Gerrit filtered for 14.1 here there was 8 Bluetooth related commits since Aug. 16, 2018 @ the present so update via the built-in > Settings > About phone > LineageOS updates & check if it solves your problem.

Will reply to your other points later today & after your feedback.

***

Edit: If you add a city + your country in your profile here the forum will add a flag under your username and besides giving an international flavor to this S3 i9300 international version thread it helps for troubleshooting suggestions like for your modem for example. Adding Service provider info helps too.

***
[Galaxy S III Original Android Development] eriol1:
There's ADB over network.

Look in developer options.
[Galaxy S III Original Android Development] karpacha:
I'm connecting my phone to a Ford Fiesta 2013. Other phones don't have this issue, nor did this one on stock OS.

Same report: https://www.reddit.com/r/LineageOS/...ooth_audio_nothing_but_static_in_phone_calls/

Another one: https://www.reddit.com/r/LineageOS/comments/6nabqs/bluetooth_call_quality_issue_with_car_stereo_on/

Thanks for the replies. It will take me a while to respond with better diagnostic info.
[Galaxy S III Original Android Development] minealex2244:
I'll post again my etc/sound/m0 addon.d backup script for those of you who didn't see it: https://xdaforums.com/showpost.php?p=70851380&postcount=354

This script will help you to not loose the changes you made to the m0 file during system update.
[Galaxy S III Original Android Development] andrescm:
Alright, used LineageOS' own updater to upgrade to 02-06. First boot took quite a long time (about 6 or 7 minutes) and I got a bit nervous because I forgot to make a nandroid before but all is good :). Root sticks so it doesn't need to be applied again. The only thing I'd wish for is an option in Settings->Display to change the screen DPI :)
[Galaxy S III Original Android Development] Scorpionea:
Settings/Display/Display size
[Galaxy S III Original Android Development] froycard:
I would like to report something that didn't happen with the Unofficial Built ROM (pre-release UNOFFICIAL 14.1 LINEAGEOS one). I am experiencing Data disconnetion or not connection to my carrier when I arrive at my office. The scenario is the following: at home I connect to my WiFi and I don't use data connection from my carrier, when I arrive at my office, I don't have data connection, but my WiFi is on. So, to have data connection back online from my carrier, I have to turn off my WiFi and put my phone in airplane-mode. Wait for a couple of seconds and then I deactive airplane-mode, afterwards my cellphone connects and sync data with my carrier (kinda annoying to do that everytime I get to my office). Like I explained before, this anomaly was not present in the ROMs I flashed before the official LINEAGE appeared in scene. Anybody knows what is going on with the ROM or has a remedy for this (other than discarding this aging mobile phone, lol)? Thanks
[Galaxy S III Original Android Development] andrescm:
Thanks, but although it seems to do what I'm looking for I'm not sure if it does. Default DPI is 320, I manually set it to 280 and "Display size" still says I'm on the default value.

[MENTION=5703768]froycard[/MENTION]: Have you tried flashing another modem?. Some are best suited for carrier X and others for carrier Y.

P.S.: Emtpy question of the week is in order!: is it just me or does anyone else think the new boot animation looks a bit small, like made for smaller devices?
[Galaxy S III Original Android Development] Lusberg:
Since the Official LineageOS came out, I am having trouble updating (via autoupdate or manual update from TRWP). I always get Status 7 error.

TWRP 3.0.2.2

lineage-14.1-20170131-nightly-i9300-signed.zip (I want to update to latest)

Stock GApps

First I tried to update to latest: cp: write error: No space left on device

Secondly I tried to reflash TWRP: Error opening: '/sdcard/twrp-3.0.2-2-i9300.img/' (Not a directory)

I thought I should ask here first, before trying anything stupid.
[Galaxy S III Original Android Development] baltics:
According to an XDA news item Google is withdrawing Google Now Launcher from playstore at the end of Q1. Those who use it need to get an Apk before then.

---------- Post added at 06:58 PM ---------- Previous post was at 06:51 PM ----------

I posted a website link here in another context a few days ago. Someone reported that after flashing the ROM the device vibrated and would not reboot. The cause of that and your issue may be the same. Not enough space on internal storage. If you can access internal storage using TWRP file manager you can perform some housekeeping. If you cannot, you may have to use Odin and restore stock Samsung, then use it to install TWRP and then flash this ROM or if you have a back up on an Ext SD restore that

But others may have better advice.
[Galaxy S III Original Android Development] froycard:
@ andrescm: Have you tried flashing another modem?. Some are best suited for carrier X and others for carrier Y.... thanks for your answer, but you got me there, I don't know what you mean sorry. I always flash the one that is available for SIII i9300, I don't know where I can check out which ROM is good for a carrier X and not for a carrier Y. If you can explain me further about this, I'd appreciate it... :confused:
[Galaxy S III Original Android Development] PACMAN456:
how do you update? after i downloaded the new update i clicked install then i took me to twrp. i couldnt find the file? where is it located???
[Galaxy S III Original Android Development] magrro:
+1
[Galaxy S III Original Android Development] kcajjones:
Does MHL / TV output work with this ROM?
[Galaxy S III Original Android Development] Simon_29:
No it does only work with sammy based roms.
[Galaxy S III Original Android Development] LuciferIII:
Hello Guys its me again.

I got some good answers on Reddit and i learned some stuff :D

Thanks to the kind people on the LineageOS Reddit i learnd how i can report bugs to JIRA(yes yes,i was a little confused :silly: ) and how i can reset the "Protected apps" settings.

you can read everything here:

https://www.reddit.com/r/LineageOS/comments/5sjwjw/rom_braking_bugsetting_that_keeps_los141_from/

I already factory reseted my ROM and dont need a way to reset the "Protected apps" to recover from that bug ...BUT on that reddit thread i got an answer on how to reset it, Sadly i dont need that anymore but maybe one of you guys will need it!

Anyways, i will wait for the next Bugbash on Jira and report this Bug. :fingers-crossed:

---------- Post added at 08:03 PM ---------- Previous post was at 07:55 PM ----------

:
[Galaxy S III Original Android Development] andrescm:
Chances are you aren't using the latest TWRP as instructed in the OP.
[Galaxy S III Original Android Development] Lusberg:
I found out that there is only 222 MB free on my system partition (/system' 'ext4' '/dev/block/mmcblk0p9)

Is it because Stock GApps? Should I go full/mini? Is this normal? Anyone else using stock GApps and 20170131? Any similar problems?
[Galaxy S III Original Android Development] andrescm:
Following your screenshot I went to the same place and it reports having a size of 1511MB with 790MB free. I don't know exactly what is taking so much space on your partition but if it matters I always use pico Gapps (I prefer to install some Google apps later manually). If you use full Gapps that should be the cause as many Google apps are installed as system apps thus taking space in that partition (someone correct me if I'm wrong).

In order to free up space there you should try removing some system apps manually using Titanium Backup or similar, or if you don't care you can just wipe the entire partition and do a clean install.
[Galaxy S III Original Android Development] Lusberg:
Ok, I will do a wipe tomorrow.

Thank you.
[Galaxy S III Original Android Development] ASVP_MSFT:
Delete
[Galaxy S III Original Android Development] Bometdebanjo:
There is a perfect app for it:

https://play.google.com/store/apps/details?id=com.vasudevrb.cmchangelog
[Galaxy S III Original Android Development] Lusberg:
https://www.cmxlog.com/14.1/i9300/
[Galaxy S III Original Android Development] curiousrom:
MyFord SYNC Car Bluetooth Problem

What an awful thread with a lot of whining, LOS devs bashing & no troubleshooting efforts. :rolleyes:

So I presume that everything works on your MyFord SYNC (hardware/software versions?) when paired to the S3 except the phone calls voice quality. Correct?

After updating LineageOS & testing as suggested above & if it's still does not work properly try this from Ford support: Your SYNC May Need an Update and How to identify your SYNC version

Sadly Vehicle Health Report Service Discontinued for your car just a few days ago on August 1, 2018: "Vehicle Health Report service was discontinued for 2008 through 2016 Model Year vehicles equipped with SYNC®, SYNC with MyFord, SYNC with MyFord Touch, or SYNC with Voice-Activated Navigation."

"...Other phones don't have this issue..." - Well it seems that some iPhone do too using this search: ford sync bluetooth distorted voice site:discussions.apple.com

I found this LineageOS for i9300 unresolved BUGBASH-873 Bluetooth in car phone audio scrambled and the Assignee is Simon Shields/forkbomb444 the maintainer of the S3 i9300 LOS & he could not reproduce & solve the problem which seems to depend on some S3~car bluetooth combos.

My S3 works fine for making calls with a cheap Chinese Bluetooth headphone. Does yours work too or when paired to a different car Bluetooth? Can't test on my vehicle as my motorcycle does not have any Bluetooth or music device except for the beautiful sound of my muffler.

Any other users that can report about how their S3 LineageOS is working with a car Bluetooth or hands-free setup? :cool:

***
[Galaxy S III Original Android Development] 239:
You can install MatLog and use ADB to grant log access once.
[Galaxy S III Original Android Development] kurtn:
[MENTION=9204613]karpacha[/MENTION] your #3

Try

Kill Camera (Kill camera related processes) - https://f-droid.org/app/info.aario.killcamera
[Galaxy S III Original Android Development] rfmalta:
first of all thanks to [MENTION=5405215]forkbomb444[/MENTION] and other devs for the great job!

after a month using this rom, trying different combinations of root and kernels, I finally discovered the ultimate stable settings:

1. don't run custom kernel

2. use addonsu for root

3. use trebuchet launcher

4. disable play store (only enable when updating)

now my rom runs very smooth most of the time (although freezes and reboots still occur on rare occasions)
[Galaxy S III Original Android Development] shaq1907:
Hi to all S3 users,

Is this Rom stable enough for daily usage? Do most features work?
[Galaxy S III Original Android Development] curiousrom:
Is LineageOS 14.1 for S3 Good Enough?

See Running LineageOS Since 8 months!

Since I wrote this in July, in 2 weeks it will be 10 months.

Everything works, minor caveats here: LineageOS S3 i9300 Known Issues Workarounds + go back one page as a user reported a Bluetooth Hands-Free Profile (HFP) problem.

See also [MENTION=7289126]HanSalvatore[/MENTION] post here & many others in this thread.

***
[Galaxy S III Original Android Development] lollo.21:
What is it in simple terms? I know little English Eheh, thanks
[Galaxy S III Original Android Development] qb74:
In simple terms, from what I've understood, he has done a lot of work, but It'll still take time. He got U-Boot working, charging status and booting off EMMC and booted Linux successfully. I, personally, wouldn't expect a release by end of the year though.

I'll be blunt, I don't really understand what he wanted to tell us with this blogpost either? Simon told us what background work he has done and a tutorial on how we can see partitions which most users have no clue what to use for? I don't know. :P
[Galaxy S III Original Android Development] mrmarioman:
Just tried this rom with my old s3, and while everything works fine, it feels very sluggish, very slow. Anyone else?
[Galaxy S III Original Android Development] curiousrom:
S3 LineageOS Sluggish?

Everything is relative.

Sluggish compared to what? And you did not describe your system setup: Open GApps package size if installed (Variant Package Comparison - I use Pico), custom kernel if any, Magisk + modules, Xposed + modules, Substratum & what not system modifications, etc.

The S3 i9300 was launched in 2012 with a limited 827 MB of available RAM & those facts have to be respected when setting up LineageOS 14.1 & user apps.

See these posts: 466 MB of Free RAM - Running LineageOS Since 8 months! and especially the Privacy Guard point #2 and #5 in 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. (screenshot)

Try all those functions before tweaking these animation settings & observe the huge difference. You could also set to .5x to have some animations & fading while gaining some speed too.

***

Developer options*: 1- Settings > About phone > keep tapping on Build number until a pop up saying "Developer options enabled" appears.

2- Go back to Settings > Developer options.

***
[Galaxy S III Original Android Development] mrmarioman:
I just have the rom installed with gapps micro and very few apps. Thank you for your post. I'll try your suggestions.

Edit- ^tried what you said, I did a clean install with gapps Pico, and it runs much better now. Also turned off all animations. :)
[Galaxy S III Original Android Development] dev.xda:
Hi! With 20180906 nightly battery drain increased to 23% in 9 hours. Before drain was about 2-5%. Nothing changed. Only mobile active. Any ideas?
[Galaxy S III Original Android Development] vege666:
I live in Italy and I recently moved to the new carrier Iliad, but phone says "only emergency calls". I manually configured the APN and data is working, but no way to make/receive calls or send/receive sms.

I tested the same sim on other phones (even a i9100 with LineageOS 14.1) and it works fine. I tested sims from other carriers and they work fine, and also a different Iliad sim but it's not working either.

I'm thinking about installing a stock firmware to see if something changes. Do you have any ideas? Maybe installing a different modem? Which one in that case?
[Galaxy S III Original Android Development] Robert-R:
Did you check / try: https://xdaforums.com/showpost.php?p=74938093&postcount=1154 ?

(By the way: my S3 is also stable with enabled Play Store. )
[Galaxy S III Original Android Development] curiousrom:
Iliad Italia SIM Problem - Battery Drain?

"...phone says "only emergency calls". I manually configured the APN and data is working" - That is super weird.

Check this app: Mobile Config by Iliad Italia, turn off the phone, wait 10 seconds & turn back on.

And this thread: Italian New Operator which may explain "I tested sims from other carriers and they work fine" so a bug report as described in post #1 of this thread may be needed to fix the Illiad network provider problem as a fix was merged on June 27 but you still have a problem. Edit: I just noticed that the commit says: Branch lineage-15.1.

What is your LineageOS build date?

Make 100% sure you have the correct APN settings. And double check.

In > Settings > About phone > what is your Baseband version (modem)?

***

Battery Drain?

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

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

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.

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

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

***
[Galaxy S III Original Android Development] vege666:
Mobile Config app only configures APN, I did it manually and data is working fine. My problem is with calls and sms, since I can only make emergency calls.

Baseband is I9300XXUGNB1. Is there any other baseband I can test?
[Galaxy S III Original Android Development] curiousrom:
Re: Iliad Italia SIM Problem - S3 Flashable Modems

You can find more recent S3 i9300 TWRP flashable modems in EFSv2 Modem Collection and the most recent one which I posted @ the end of that thread here.

Edit: [MENTION=6520725]vege666[/MENTION] I forgot to mention that you should do a EFS Partition Backup - No Service Fix before flashing modems just to be on the safe side.

If it does not work call your operator & check the edit I made to the post above about the Iliad merged commit.

You did not answer this question: What is your LineageOS build date?

***
[Galaxy S III Original Android Development] vege666:
Thanks, I'll check it asap.

Sorry, I didn't notice it because it was written in bold. :cyclops:

My build is 20180823.
[Galaxy S III Original Android Development] lollo.21:
Do you also no longer work on MTP when you connect your mobile phone to your PC? I installed the Rom on another S3, equal! Is there a solution? I also tried to enable MTP from TWRP, equals, it doesn't work. With older ROMs It works so I want to as I confirm that it is a problem to the latest ROMs and how can I fix it.

Then, I remember that years ago I had used an app that allowed to use the Voice command to write texts instead of using the headboard that also had the ability to download offline languages and then use the Voice (microphone icon) Even without 3g, someone remembers this App mod?

thanks :)
[Galaxy S III Original Android Development] Nobby1960:
Just two questions: Has this ROM customizable volume steps (music, ringtone, DTMF etc.) and customizable setting for the ambient display (brightness and so on)?
[Galaxy S III Original Android Development] Ashraf Iraqian:
Yes it is.
[Galaxy S III Original Android Development] Properjob70:
The ROM runs fine on my i9300, I just couldn't get GApps 7.1 to install (not compatible with system architecture). I tried several different dates and used pico instead of nano etc. No avail. I reflashed TWRP (as my device had CWM on it and GApps said they favoured TWRP for some reason) but not unexpectedly same problem (if it's system architecture why would it??).

I've gone back to Cyanogen 13.... which kept bootlooping after spending ages booting up and preparing apps (I am assuming this was a minor installation whoopsie on my part).

Gapps 6 installed ok. It's only a spare device to take on hols and chuck a local SIM in.
[Galaxy S III Original Android Development] Hawaiihemd:
There are different device architectures and you need to get the right gapps for your device.

The SGS3 is an "ARM" device. So get an ARM GApps package.

Should work just fine then.

On a side note: CWM is a long outdated recovery that will surely lead to problems when flashing recent stuff to your device. I highly recommend TWRP.
[Galaxy S III Original Android Development] Properjob70:
I have already changed CWM to TWRP as part of the process leading to giving up. I'm sure it'll pay dividends when I find a solution to the GApps 7.1 problem and want to change to Nougat....

I tried OpenGapps arm64-7.1-pico & nano; I also tried releases from earlier in the month to see if the latest nightlies were the problem. Same result error 64 in all cases.

Open Gapps arm64-6.0 works with the Marshmallow release ok.

Also on a sidenote I am suspicious there may be a hardware problem in the GS3 causing the bootloop in CM13 (reaches full bootup via "preparing to start" "Starting Apps" screen then reboots after a few moments once you reach a critical mass of apps though. Time to bin it I think.
[Galaxy S III Original Android Development] James160103:
As you've already been told to do, download and install ARM Open GApps, not ARM64. ARM64 isn't the Galaxy S3's architecture and will therefore not install.

Install the ROM and then the GApps and tell us if that worked out for you. :good:
[Galaxy S III Original Android Development] James160103:
Deleted
[Galaxy S III Original Android Development] Properjob70:
Thanks. Yes the ARM ones worked.... Initially I just clicked on the 7.1 version it linked me to. Now I look at the screen again there is a radio button to toggle between ARM and ARM64. I guess I was hoping it would link straight to the right one, but it didn't! Now sorted. Let's see if my set of apps for foreign travel break it again!
[Galaxy S III Original Android Development] Nobby1960:
Thanks, I meant that these functions (volume steps and ambient display) are also specially configurable, see in my screenshots. Unfortunately not, I have tried this ROM today. I know this features from RR and AICP.