yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ianos21:
I like it. Installed today. Only one problem. volume buttons do not change speakerphone volume during call... default is full volume. I can't figure out how to change this
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hayo Tee:
http://www.emccann.net/dho/3-Vanir-mirror/4-nighties//
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Trodmantas:
I don't get it. Where are the ROM zip files? I can't find them in Octos page.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Native7i:
I meant download link root. It doesn't get extracted by the time I checked
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ianos21:
I couldn't get them off OctOS site either - I found them at www androidfilehost com search for d2att.zip - the first result is OCT-N-COMMUNITY-20170102-0343-d2att.zip followed by older builds. This is what I flashed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Hey guys! Weeklies are up!!

https://www.teamoctos.com/oct-n-weekly-lineageos-base/

Go get em'! ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Wow! Downloading! If the camera works well i might make this as my daily driver, RR or lonelyskatter seems to be taking a break atm...

Edit: hell yeah, I found my new ROM, thank you for this team OctOS!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoryB:
Your first post mentions CM14 as the base, but the download link goes to AOSP based downloads. That page does not have d2att downloads. You have to go over to the lineage OS based downloads. There is another thread already started for lineage OS based Firmware. https://xdaforums.com/galaxy-s3-att/orig-development/rom-team-octos-oct-n-t3532582

Just thought I point out some things that might confuse people.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Duyo:
Thanks for the rom. Running well. About TWRP nandroid backups. Do you mean the backup wont install or TWRP wont backup the rom at all? I just did a backup with the latest TWRP 3.0.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
The thread you linked is for s4. This thread is for s3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
Oh, it will APPEAR to work. After you restore the image, you can boot, but you will get endless phone force closes. If you find a way to get an N backup to restore on d2 without those FC, please share.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
This bug has been around since L. Haven't looked into it myself.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Duyo:
Just tried it. Would not restore at all. Thanks for the reply.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GamingDevilsCC:
Is this stable enough for daily use? If not, what are the current bugs/problems?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
I've been using it as a DD for weeks now. Not all features have made it back & there are a few empty spots "yet to be filled" in tentacles but other then that its solid.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CwalkPinoy:
Currently my only choice in ROM, hands down.

Few problems to report, of course.

If you tap system profiles, some app called lineageos crashes. Guess that's the system profiles app.

I can't remove the status bar icon for built in superuser. Would be nice.

Loving substratum. Bought swift dark to try it out. Notifications did not get themed. Still that white color. Most everything seems to work as intended, except if I'm using aosp keyboard its also light. But it could be google keyboard or something. That's probably an issue with the theme rather than the ROM, so I'm not too worried about that.

Camera works, guys. Cause nobody seemed to mention that.

Other than those minor disturbances, great ROM. Daily driver ready.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
Yeah, I think we changed to the "pixel" launcher. I didn't pay much attention to it as I wasn't a fan of what was there before either. I've been on nova for years.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] post-mortem:
Yeah, if the hidden Audio Test menu doesn't launch when you type the code, then the code isn't recognized by your ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] droiduzr2:
My phone works with headset.

I tried the codes and it did not come up, just went back to blank dialer.

I think the codes trigger an app. I saw that before on another ROM.

If they remove the "service menu" app then the codes are useless.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tjensen:
What are the chances of defining "#define READ_MACADDR" in the builds so the mac address gets read from /efs/wifi/.mac.info on boot.

This way a spoofed mac address remains after reboot.

With the latest build, you can change the mac address but after reboot the original hardware mac address gets written back to the .mac.info. file.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GoughGhan:
Been using this as my daily driver for a while since before the boringssl fix, I have to say working like a dream right now after the fix. I was so excited to see the post a few weks ago to upgrade for it!

Before the fix I was using outlook as it synced with my G-mail pretty fast, faster than Inbox. Downloading from the play store took a while but it did happen after a bit. I'm on T-mobile with the T-999 variant. Been using d2att variants on my phones for a good long while. Not having the headset bug that people seem to be coming up with, or bluetooth issues or camera crashes.

As of now just pretty much wanted to say thanks it works flawlessly. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
d2att and d2tmo are very similar, but since we maintain separate builds for them, I don't recommend installing one on the other.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
Anyone else with the headset problem? I have a build that needs testing...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manicpanic:
does this rom support apt-X?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GoughGhan:
True but I've never really had issues using any d2att variant on my phones, plus this part of the forum is most active. I mean come on you've seen the T-mo section it's like a ghost town in there.

:laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
Well, you and me. I'm on d2tmo, you better believe if there's something broken, it will get fixed. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] holysaint1:
Oh yes.. Am here for the testing.. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
Check your PMs, I sent you something some days ago. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manfromgta:
Update: May 5/17

Weekly is up on site.

Download from OP or check OTA.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] holysaint1:
Thanks bro.. I seldomly check my pms these days.. Will definitely try out your suggestion... And provide feedback about my findings..

Thanks again for the concern.

However, I also sent you a pm. Do well to reply anytime soon.. Tnx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
Yeah, I can't just post test stuff on the public board or it will be mayhem. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ShazamXD:
Whenever I try updating the rom with a weekly, all my GApps are deleted, and I have to reset my phone, how should I update the phone if I want to prevent this?

I also have another issue. I'm currently on 7.1.1 (from the 21st of April) as whenever I update to 7.1.2 on any rom duo stops working as it can't connect to the camera and then crashes.

Besides those issues everything seems to be working great! Thanks for making an amazing rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] post-mortem:
You need to reflash the gapps package of your choice every time you reflash the ROM, as referenced in the OP:

Personally, I use FlashFire to flash the ROM, then gapps (I use pico, but whatever), and set FlashFire to inject SuperSU, so I'll be rooted. Apparently, though, it's preferred to use the LineageOS su, to ensure compatibility with the ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ShazamXD:
Thanks for the solution, I wasn't used to that since I've never had to do that before, but good to know that the solution is simple enough.

Does anyone know why duo breaks with 7.1.2 though as I would want that to work before I actually updated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
Was duo working on 7.1.1 for you? Or are you coming from an earlier version?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Journey159:
Has anyone gotten this to work on a Rogers variant?

Upon installing, the ROM boots with multiple errors (no sim, phone ha stopped working..) and then reboots to boot image w/ no LED light and stays there :/.

I've tried extracting the stock modem and flashing that via Odin but the same result. Is this ROM even compatible with Rogers?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
You are the first to report on Rogers. Make sure your TWRP, modems, etc are up to date.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Journey159:
Works!

After a couple hours of trial and error, I got it to work, still not sure why it suddenly decided to but I'll outline what I did below.

1 - follow all steps given in OP

2 - flash the lineage root su after flashing the ROM zip

3 - if the phone reboots and the same errors as in my OP occur, wipe phone, follow steps 1 and 2 then ODIN modem on top

4 - if errors occur again, try steps 1 and 2 again (this is where mine booted up properly)

5 - flash gapps after you confirm all radio signals work (wifi, data, Bluetooth)

NOTE - upon boot, there might be no setup and the front camera also reboots the phone

ROM is smooth as butter otherwise, cheers!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
Are you using a video chat program with the front facing camera? There have been some issues with video chat apps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Journey159:
No I've only used the stock camera app so far. It works sometime but other times it randomly reboots the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
If you have adb on your machine, boot fresh (smaller logs are better, less to dig through), reproduce the crash and get me a logcat, I'll take a look.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
PM sent.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ShazamXD:
Duo was working fine on 7.1.1, but seems to be broken in 6.0, and 7.1.2. The specific build duo was working in, for me was the Oct-Os build released on the 21st of April, fixing the boringssl issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ocd_amp:
Rogers / Fido network

Rogers and Fido both have an enhanced Caller information display service called Caller ID Name Display that should show the Name of caller if the caller is using a Land Line or business (and if the name is not Private) along with the Number.

Only the number shows but not the name, using Default dialer as well as Google's dialer. This feature works on Stock ROM from Samsung but does not work with any AOSP Based ROMS.

This feature was very useful because you can easily add the contact when they are not already in your address book and it even works in my old Blackberry Bold.

If OCT OS can fix this, This will be one of the best things ever done for the entire AOSP community when dealing with Samsung devices.

I have a Galaxy S2 which does show the Caller name but it is Garbled up and looks like Symbols. But on the I747M, it does not show a name at all.

To test this,

1) Stop your Google Contacts from Syncing by going into Accounts and uncheck "Contacts"

2) Clear your Contacts Storage

3) Receive a call from a Land Line who is not hiding their identity or number

You can see that on Stock ROM this will work, but on any AOSP/CM/Lineage it will not show any Caller name.

Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gabe2409:
Yes I have. It works perfectly without any errors so far. Installed SuperSU and works without problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rob_z11:
My note4 died of MMC error, so have revived my S3, and very happy with this rom. Everything appears to be working ok except camera at times won't connect, but very nice rom indeed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
thanks for continuing builds for the s3.:cowboy:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
I had an mmc problem on my s3. You can get a new MMC chip soldered on the board, but it's not a trivial fix, best left to the professionals. Alternately, working boards are probably available on ebay. I opted for a new board.

There is a problem with video chat apps, we are looking into it...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] post-mortem:
5/19 is up!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ShazamXD:
Along with the camera issue with duo that I was facing, I also found that the front facing camera stops working on allo as well. Do these google apps utilize the camera differently from other apps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
Every friday, unless we don't. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
Yes, it does have to do with how the apps are utilizing the camera.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] post-mortem:
Was the 'kill app on back button' feature removed? I can't find it in the settings (it never worked for me on N, anyway).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manfromgta:
Yes it was removed when DUI was implemented.

---------- Post added at 07:41 AM ---------- Previous post was at 07:40 AM ----------

Weekly 05/19 is up on site.

Download: https://www.teamoctos.com/oct-n-weekly-lineageos-base/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Syoenth:
can I install this ROM on the I747M variant?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] post-mortem:
According to this user, yes!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Syoenth:
then I can install any d2att ROM on my device, right? I want to try the official Lineage OS Rom :o:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joser96:
Issue with sim card

i have an issue with the d2att variant, its not reading the sim card. i flashed the rom using the last TWRP version. :confused::confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] post-mortem:
Has the same SIM card worked on another ROM? Does the SIM card work in another phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
Is it an att sim or for a different carrier?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Joser96:
EDIT: i solved the whole issue by updating the modem, i finally could find it to download. thanks for the feedback
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Syoenth:
I have an issue with this ROM, I flashed the Viper4Android for Nougat and it won't install the driver, I used this in other ROMS on my I9300 and the driver install flawlessly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] post-mortem:
There is no i9300 version of OctOS, but the LineageOS ROM for your device is here. OctOS is based off of LineageOS anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Syoenth:
I mean, I have a S3 I747M, I love the effects Viper4Android gives and I wanted to install on this ROM, but when i wanted to install the drivers I got an I/O error
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manfromgta:
Update: May 26/17

Weekly 05/26 is up on site.

Download: https://www.teamoctos.com/download/oct-14.1/d2att/OCT-N-WEEKLY-20170526-1513-d2att.zip

Changelog: https://www.teamoctos.com/download/oct-14.1/d2att/OCT-N-WEEKLY-20170526-1513-d2att-changelog.log
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] viddy135:
Hey can someone link me to the rom before it was merged with 7.1.2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manicpanic:
SElinux set to enforcing perhaps? I use viper with no issues after setting to permissive
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GamingDevilsCC:
Hi,

I've been looking for some free phone apps, however with things like Fongo and TextNow, the calling features do not pickup my voice, while on stock android it would. Could this be because my phone app isn't set to the default calling app? And if so, how would I do that, as it doesn't give me an option to change the phone app to anything but the default phone app itself.

I'm on OctOS N, 7.1.1 M1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] post-mortem:
Have you tried other apps, such as Google Voice, Hangouts, Allo/Duo/whatever, I don't know... Tango, Viber? If other apps work for you, then it's not the ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
Most video chat apps don't work right now. I haven't had any other reports of voice only chat apps not working, but if you are attempting to use a video chat, it will die horribly. All lineage based ROMS (they are all lineage based ROMs for d2) have this issue.

It's on my list, I'm chasing down a headphone d2 issue at the moment.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cannothas:
I'm looking for a stable build for a kids phone. Need good battery life, good call quality (speakers work right, have good volume, mics work right, noise-cancellation works, etc), good network and cell reception, and working camera.

Does this stand up to those requirements?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GamingDevilsCC:
I've just tried Hangouts, and same issue. These apps worked fine on stock 4.4.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
You can still get extended batteries for the s3. I'm a fan of lazawireless batteries. Call quality is good. There is a rare bug with wired headphones that doesn't work on some phones.

Video chat apps will not currently work. If this is important to you, there are L versions out there that work fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krajkumar:
Booting for past 6 hours

After I flashed ROM, it's booting for more than six hours. Will it be like that at first phase or something wrong? Installation [ Flashing ROM + Installation of gApps succeeded ]

Kindly advise.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
No, something is wrong. Make sure your modem and bootloader is up to date. Also make sure to update TWRP to the latest version.

Was this a clean flash? Upgrade from earlier octos version?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krajkumar:
I had OctOS OCT-L-M3-5.1.1-20150616

I had issues with network signals from AT&T and installed some wrong modem and didn't work. Later on found correct Modem I747UCUFNE4 and rebuilt with above OS. After that tried with OCT-M versions and didn't succeed.

Now I tried with OctOS-N version [ OCT-N-M1-20170421-d2att.zip & OCT-N-WEEKLY-20170602-2055-d2att.zip ]. I tried with these ROM's without above Modem and with above Modem.

It will keep on booting for more hours and won't go to next stage.

Now I'm again back to OctOS OCT-L-M3-5.1.1-20150616

TWRP - Version - 2.8.5

Bootloader - Kindly let me know how to find. While fixing above issues, I pressed "Power button + Volume down button + Home button" and had an option to upgrade. During that time, I remember I saw some Bootloader information. If I do it again, it will ask for update which I am afraid of. If that shouldn't be a problem, then I will get it.

Any other ways to find Bootloader version?

Kindly share your thoughts on what might have happened.

Thanks in advance.

-Raj
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] post-mortem:
Latest TWRP (3.1.0) is here.

If all else fails, you should be able to Odin back to stock and start over.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krajkumar:
Booting for more than six hours

Thanks. Now I've my latest TWRP. 3.1.0

Kindly let me know what to do next?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krajkumar:
What next? Help please...

My Kernel Version says - 3.4.107-Cyanogenmod-gd5fae87

jenkins@dalek #1

Tue Jun 16 20:04:22 EDT 2015

Build number

to_d2att-userdebug 5.1.1 LMY47Z ac39fc70b1 test-keys
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
Update your modem and bootloader. Search on xda to find them. You will want to search using the model number of your phone (take the battery out and look) to get the right binaries.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krajkumar:
Thanks, Chris

I updated to CM13 and was able to flash OctOs-N-M1-7.1.1. Everything works fine. However, I flashed I747UCUFNJ1 and I747UCUFNJ2. It didn't work.

Steps I followed:

1) I tried flashing I747UCUFNJ1 before CM13. It flashed without any errors.

2) When I flashed I747UCUFNJ2 it threw error.

3) So, I flashed CM13 and no errors seen. After CM13, tried flashing I747UCUFNJ2 and it threw errors.

4) Even though I747UCUFNJ1 succeeded without any issues, my phone still says baseband verison as I747UCUFNE4

As I am using Lyca mobile, most of the places I am not getting any signals. Is there anything I need to do to fix it?

Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
Please use the latest 7.1.2 weekly. The 7.1.1 milestone had a major problem (unknown at the time) that has been fixed in all 7.1.2 versions.

I'm working on getting that build removed or downgraded to a weekly status, it doesn't deserve the M1 label.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krajkumar:
Chris, after 7.1.2, I tried with gApps Aroma. During that boot I got Att boot img. Was it designed like that? I assumed something wrong and Again, I flashed 7.1.2, gApps - Full on top of 7.1.2. It's not working. Error says, I'm not on 7.1.x. Not sure if I did something wrong. Again, I went with 7.1.1 and gApps started installing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
1) Factory wipe

2) install 7.1.2

3) install opengapps MINI

4) If you want root, install lineage root from https://download.lineageos.org/extras (your phone is arm). SuperSU is NOT supported.

5) Wipe cache/dalvik

Edit: Are you saying that you saw an at&t logo on boot? But your phone is otherwise working?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krajkumar:
Yes, Chris.

I saw AT&T logo after I flashed with 7.1.2 & gApps - Aroma. I assumed something wrong and then flashed 7.1.2 & gApps - FULL.

Thank You, Chris. Now, I'm on 7.1.2. I followed all your steps as mentioned above. Still I'm on NE4 baseband version. From some other thread in this forum got info about flashing S3 stock recovery->NJ1->NJ2 succeeded. For me it didn't help and went with Carbon ROM as I'm unable to flash OctOS using stock recovery . Tried to root with different options and all failed. Atlast I installed TWRP using ODIN and was back to 7.1.1. After your above message, now I am on 7.1.2 OctOs. :)

Thank You so much.

My only concern is about my mobile signals. At some places, there are no signals. I'm using Lyca. Should I need to think about baseband version or moving to different network provider? If I get Google's Project FI SIM card, will it work in my mobile?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
I'm not sure which network Lyca is using in your country. I'm also not sure who Google FI is using either. Before you switch providers, I'd make sure you are actually moving networks and not just resellers of the same network.

The sad news is that some networks are starting to think about moving to 5g technology, they are starting to not have robust support for the earlier technologies that are supported by d2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krajkumar:
Lyca - T-Mobile

Lyca use T-Mobile network.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] clearchris:
Ouch, T-Mobile seems to be moving the fastest to go to 5g technologies.

If your phone doesn't have LTE (some d2 do, some don't) you might want to consider switching before T-Mobile completely migrates.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] post-mortem:
Hey guys, they finally updated TWRP for our device! https://dl.twrp.me/d2att/

Here's the XDA post discussing this update: https://www.xda-developers.com/twrp-3-1-1-is-out-brings-minor-fixes/