[ROM][OFFICIAL][enchilada][9] LineageOS 16.0

Search This thread

breakingspell

Senior Member
Dec 1, 2010
392
122
I'm also experiencing an unending boot when flashing a newer build. Blamed it on my own self-builds/keys at first, before noticing that users in this thread were also having issues.
Ensured that I updated in the usual fashion. 1st clean install was LOS16 to both _a and _b

-Boot to TWRP, flash latest LOS16 zip, then TWRP installer, then reboot to recovery
-Flash MindtheGapps, latest Magisk, reboot.
Device hangs on boot logo until restarted. Switching back to the previous ROM slot and reflashing Magisk rolls back to the working previous version as intended.

I haven't MSM restored or flashed OOS over both slots since April or so, is there a newer bootloader/modem we need?
 

Master One

Senior Member
Jan 31, 2011
742
254
Europe
Something went wrong with yesterday's OTA update. I'm using LOS 16 for microG with TWRP and Magisk. Somehow it seems that I managed to let the OTA updater install LOS twice, so to the active and inactive slot, and now TWRP is not there anymore (the Magisk Module "TWRP A/B Rentention Script" just says "TWRP ramdisk not found" and fails).

I haven't rebooted yet. What's the easiest way to resolve this? So I somehow need to reinstall TWRP and Magisk. Is that possible with the LOS recovery or do I need to fastboot TWRP over?
 

T2000T2000

Member
Jun 20, 2012
45
6
hi,

I am not sure if this is the 100% correct forum to post my issue, but since I am experiencing it with this ROM, I decided to post it here.

My battery runtime is quite bad although I rarely use my phone, i.e. its mostly in idle mode, but I can barely reach 2 days of usage.

I noticed that If I set the phone to flight mode OR remove its mobile internet connection and wifi, the battery drain is about normal and not very critical.

I installed BetterBatteryStats and noticed these alarms (see screenshot in attachment).

9Mma3SZ



com.google.android.gms and android. Their percentage on this screenshot with around 50% is LOW, if I do not set flight mode over night, this is A LOT higher.

I am using opengapps nano from 25.10.2019 and I think its auto updating itself anyway, at least I searched for newer versions of the playstore and google play services but couldn't find any.

My lineage 16 is from the 25.10.2019 too. But I had the battery drain also in previous versions.

I decided to have a look with logcat and see what happens. What caught my eyes were these three log entries:

1. WakeLock: GCM_HB_ALARM release without a matched acquire

2. AlarmManagerService: Kernel timezone updated to -60 minutes west of GMT

3. libsuspend: error writing to /sys/power/wakeup_count: Invalid argument

If the phone does not have a mobile data connection or wifi, these log entries disappear.

So I am wondering whats wrong with my phone. Does anybody else experience battery drain with this ROM?

Any recommendations what I could do? I cleaned all caches etc. already.

Regards,

Stefan
 

Attachments

  • Screenshot_20191123-110404_BetterBatteryStats.jpg
    Screenshot_20191123-110404_BetterBatteryStats.jpg
    162.5 KB · Views: 865
Last edited:

dupsatou

Senior Member
Aug 19, 2008
184
20
Dallas, Texas
So I can't get this to boot - I'm not sure if I'm doing something wrong or if there is something going on with the builds. I tried the most recent and back to the oldest available (19th) and no matter what it sits for a long time on first boot on the Lineage logo and then reboots with some red text saying it can't load the Android system. Anybody else experiencing this? Did I miss something crucial?

EDIT: Nevermind. I messed up. Tried to apparently flash the x86 version of MindTheGapps... Nothing to see here... Move along...
 
Last edited:

purlupar

Member
May 27, 2019
9
1
Black screen

What is your--
LineageOS version: lineage-16.0-20191210-microG-enchilada.zip
LineageOS Download url: lineage.microg.org
Gapps version: none

Did you--
wipe: yes
restore with titanium backup: no
reboot after having the issue: yes

Are you using--
a task killer: no
a non-stock kernel: no
other modifications: addonsu

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
logcat: https:// paste.ubuntu.com/p/WK6rWKYhtk/
display went black at 18:37:17:
Code:
12-09 18:37:17.265   703   861 I SDM     : HWCSession::UpdateVsyncSource: No other active builtin display, nothing to do.
12-09 18:37:17.266   703   861 I SDM     : HWCSession::HandleConcurrency: sec_builtin_active 0

occurrence: 1st boot works (LOS setup, can enable adb debugging)
2nd boot either goes black after the LOS boot animation, or about 10 seconds into the booted os.
wiping internal storage, data and cache reverts to normal lineage, but only for 1 boot.
 

hayvan96

Senior Member
  • Mar 23, 2018
    255
    194
    Hi
    I'd like to upgrade my opengapps from nano to micro to see if it improves Exchange connection. Is it as simple as reboot to recovery, flash nano and reboot?
    It's my first a/b device and I don't want to end in bootloop if it's not the correct process. Thank you
     

    Luk3s

    New member
    Dec 29, 2019
    4
    0
    all the currently available official builds and microg builds based on them result in "Can't load android system" :/

    I'm using build 1224, without problems.

    ---------- Post added at 01:41 PM ---------- Previous post was at 01:04 PM ----------

    Hi
    I'd like to upgrade my opengapps from nano to micro to see if it improves Exchange connection. Is it as simple as reboot to recovery, flash nano and reboot?
    It's my first a/b device and I don't want to end in bootloop if it's not the correct process. Thank you

    Hi, at least with my a/b phone, I didn't have success installing opengapps micro and nano, using build 1224, first with fresh install got error 20, and after rebooted in fastboot got error 70, tried to resize partition without success, I found people with same difficult and they advanced installing mindthegapss, I tried that and worked.
     
    Last edited:

    dolorem

    Member
    Oct 12, 2011
    24
    4
    I'm using build 1224, without problems.

    Official or MicroG build? I tried both the ordinary way (instructed in this thread) i've always done, and also used the TOOL ALL IN ONE to flash 9.0.9 and later 9.0.7 OOS (which works fine) to ensure that all the partitions are ok.

    Others in this thread seemed to encounter similar challenges on builds somewhere after Nov 17 or thereabouts.
     

    Luk3s

    New member
    Dec 29, 2019
    4
    0
    Official or MicroG build? I tried both the ordinary way (instructed in this thread) i've always done, and also used the TOOL ALL IN ONE to flash 9.0.9 and later 9.0.7 OOS (which works fine) to ensure that all the partitions are ok.

    Others in this thread seemed to encounter similar challenges on builds somewhere after Nov 17 or thereabouts.

    Official build, the only challenge I had was installing gapps, all done in command line. OOS Oxygen OS? I removed OOS before Lineage. Maybe this graphic tool is outdated? Is your device a/b type?
     

    dolorem

    Member
    Oct 12, 2011
    24
    4
    Official build, the only challenge I had was installing gapps, all done in command line. OOS Oxygen OS? I removed OOS before Lineage. Maybe this graphic tool is outdated? Is your device a/b type?

    Well, this thread and rom ARE for enchilada :) i didn't know that OP6 came with any other flavour than a/b

    What do you mean you removed OOS? In order to install the ROM you have to flash the OOS twice to populate both slots with the appropriate images (as instructed by the thread author). After that flashing LOS will overwrite the relevant parts.

    by flashing 9.0.7 OOS ROM twice (both slots) and then LOS 191224 + blu spark TWRP i was able to boot to the setup screen but then encountered a hang, dmesg reports the following:

    [ 27.977498] dwc3 a600000.dwc3: wakeup failed --> -22
    [ 27.977523] ------------[ cut here ]------------
    [ 27.977539] WARNING: CPU: 2 PID: 75 at dwc3_send_gadget_ep_cmd+0x5bc/0x61c

    it seems the USB controller failed but I have no idea whether this can result in a total hang.

    Edit: I always flash from command line, either by pushing zips or just sideloading
     

    Luk3s

    New member
    Dec 29, 2019
    4
    0
    Well, this thread and rom ARE for enchilada :) i didn't know that OP6 came with any other flavour than a/b

    What do you mean you removed OOS? In order to install the ROM you have to flash the OOS twice to populate both slots with the appropriate images (as instructed by the thread author). After that flashing LOS will overwrite the relevant parts.

    by flashing 9.0.7 OOS ROM twice (both slots) and then LOS 191224 + blu spark TWRP i was able to boot to the setup screen but then encountered a hang, dmesg reports the following:

    [ 27.977498] dwc3 a600000.dwc3: wakeup failed --> -22
    [ 27.977523] ------------[ cut here ]------------
    [ 27.977539] WARNING: CPU: 2 PID: 75 at dwc3_send_gadget_ep_cmd+0x5bc/0x61c

    it seems the USB controller failed but I have no idea whether this can result in a total hang.

    Edit: I always flash from command line, either by pushing zips or just sideloading

    You're right, we are in a specific topic for a/b device OP6, my fault.
    In this device, *(OEM was already unlocked), first I removed OOS 9 with twrp, Advanced Wipe (System, Data, Cache), then rebooted to fastboot, sideload and pushed twrp again to install Lineage. Alternatively you can mount by USB and copy Lineage image to /sdcard, to install locally.
     
    Last edited:

    dolorem

    Member
    Oct 12, 2011
    24
    4
    You're right, we are in a specific topic for a/b device OP6, my fault. In this device, I removed OOS 9 with twrp, Advanced Wipe (System, Data, Cache), then rebooted to fastboot, sideload and pushed twrp again to install Lineage. Alternatively you can mount by USB and copy Lineage image to /sdcard, to install locally.

    Edit: if someone else encounters the same problems as me:

    1) either "Android system couldn't boot" OSLT (the Lineage error screen with red text)
    2) fastboot boot loop
    3) anrdoid.process.acore force closes constantly

    I urge you to get the 9.0.8 OOS Fastboot and install the following images:

    Code:
    fastboot -w
    fastboot flash aop_a aop.img
    fastboot flash aop_b aop.img
    fastboot flash bluetooth_a bluetooth.img
    fastboot flash bluetooth_b bluetooth.img
    fastboot flash boot_a boot.img
    fastboot flash boot_b boot.img
    fastboot flash dsp_a dsp.img
    fastboot flash dsp_b dsp.img
    fastboot flash dtbo_a dtbo.img
    fastboot flash dtbo_b dtbo.img
    fastboot flash fw_4j1ed_a fw_4j1ed.img
    fastboot flash fw_4j1ed_b fw_4j1ed.img
    fastboot flash fw_4u1ea_a fw_4u1ea.img
    fastboot flash fw_4u1ea_b fw_4u1ea.img
    fastboot flash modem_a modem.img
    fastboot flash modem_b modem.img
    fastboot flash oem_stanvbk oem_stanvbk.img
    fastboot flash qupfw_a qupfw.img
    fastboot flash qupfw_b qupfw.img
    fastboot flash storsec_a storsec.img
    fastboot flash storsec_b storsec.img
    fastboot flash system_a system.img
    fastboot flash system_b system.img
    fastboot flash vbmeta_a vbmeta.img
    fastboot flash vbmeta_b vbmeta.img
    fastboot flash vendor_a vendor.img
    fastboot flash vendor_b vendor.img
    fastboot flash LOGO_a LOGO.img
    fastboot flash LOGO_b LOGO.img
    fastboot flash persist persist.img
    fastboot boot twrp-3.3.1-x_blu_spark_v9.101_op6.img
    adb wait-for-recovery
    TIMEOUT /T 5 /NOBREAK
    adb push abl.img /sdcard/abl.img
    adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_a
    adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_b
    adb push cmnlib.img /sdcard/cmnlib.img
    adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_a
    adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_b
    adb push cmnlib64.img /sdcard/cmnlib64.img
    adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_a
    adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_b
    adb push devcfg.img /sdcard/devcfg.img
    adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_a
    adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_b
    adb push hyp.img /sdcard/hyp.img
    adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_a
    adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_b
    adb push keymaster.img /sdcard/keymaster.img
    adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_a
    adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_b
    adb push xbl.img /sdcard/xbl.img
    adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_a
    adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_b
    adb push xbl_config.img /sdcard/xbl_config.img
    adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_a
    adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_b

    Worked for me and now i'm running LOS16 191224 + microG + Magisk 20.1. + blu_spark r103 kernel very nicely.
     
    Last edited:

    iTalisman

    Senior Member
    Why 9.0.8? Any issues with 9.0.9?


    Edit: if someone else encounters the same problems as me:

    1) either "Android system couldn't boot" OSLT (the Lineage error screen with red text)
    2) fastboot boot loop
    3) anrdoid.process.acore force closes constantly

    I urge you to get the 9.0.8 OOS Fastboot and install the following images:

    Code:
    fastboot -w
    fastboot flash aop_a aop.img
    fastboot flash aop_b aop.img
    fastboot flash bluetooth_a bluetooth.img
    fastboot flash bluetooth_b bluetooth.img
    fastboot flash boot_a boot.img
    fastboot flash boot_b boot.img
    fastboot flash dsp_a dsp.img
    fastboot flash dsp_b dsp.img
    fastboot flash dtbo_a dtbo.img
    fastboot flash dtbo_b dtbo.img
    fastboot flash fw_4j1ed_a fw_4j1ed.img
    fastboot flash fw_4j1ed_b fw_4j1ed.img
    fastboot flash fw_4u1ea_a fw_4u1ea.img
    fastboot flash fw_4u1ea_b fw_4u1ea.img
    fastboot flash modem_a modem.img
    fastboot flash modem_b modem.img
    fastboot flash oem_stanvbk oem_stanvbk.img
    fastboot flash qupfw_a qupfw.img
    fastboot flash qupfw_b qupfw.img
    fastboot flash storsec_a storsec.img
    fastboot flash storsec_b storsec.img
    fastboot flash system_a system.img
    fastboot flash system_b system.img
    fastboot flash vbmeta_a vbmeta.img
    fastboot flash vbmeta_b vbmeta.img
    fastboot flash vendor_a vendor.img
    fastboot flash vendor_b vendor.img
    fastboot flash LOGO_a LOGO.img
    fastboot flash LOGO_b LOGO.img
    fastboot flash persist persist.img
    fastboot boot twrp-3.3.1-x_blu_spark_v9.101_op6.img
    adb wait-for-recovery
    TIMEOUT /T 5 /NOBREAK
    adb push abl.img /sdcard/abl.img
    adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_a
    adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_b
    adb push cmnlib.img /sdcard/cmnlib.img
    adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_a
    adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_b
    adb push cmnlib64.img /sdcard/cmnlib64.img
    adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_a
    adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_b
    adb push devcfg.img /sdcard/devcfg.img
    adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_a
    adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_b
    adb push hyp.img /sdcard/hyp.img
    adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_a
    adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_b
    adb push keymaster.img /sdcard/keymaster.img
    adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_a
    adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_b
    adb push xbl.img /sdcard/xbl.img
    adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_a
    adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_b
    adb push xbl_config.img /sdcard/xbl_config.img
    adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_a
    adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_b

    Worked for me and now i'm running LOS16 191224 + microG + Magisk 20.1. + blu_spark r103 kernel very nicely.
     

    purlupar

    Member
    May 27, 2019
    9
    1
    What is your--

    LineageOS version: lineage-16.0-20191210-microG-enchilada.zip

    LineageOS Download url: lineage.microg.org

    Gapps version: none



    Did you--

    wipe: yes

    restore with titanium backup: no

    reboot after having the issue: yes



    Are you using--

    a task killer: no

    a non-stock kernel: no

    other modifications: addonsu



    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

    logcat: https:// paste.ubuntu.com/p/WK6rWKYhtk/

    display went black at 18:37:17:

    Code:
    12-09 18:37:17.265   703   861 I SDM     : HWCSession::UpdateVsyncSource: No other active builtin display, nothing to do.
    
    12-09 18:37:17.266   703   861 I SDM     : HWCSession::HandleConcurrency: sec_builtin_active 0



    occurrence: 1st boot works (LOS setup, can enable adb debugging)

    2nd boot either goes black after the LOS boot animation, or about 10 seconds into the booted os.

    wiping internal storage, data and cache reverts to normal lineage, but only for 1 boot.
    I'd like to bug-report this or get advice but have had no success yet.
    Anyone with a hint?
    Tried all kind of releases of OOS, and of lineage, lineage+microg, twrp, bluspark-twrp, magisk, without addonsu, with addonsu ...
    I'm feeling like spamming but this is the relevant thread.
    Thanks.

    Gesendet von meinem ONEPLUS A5000 mit Tapatalk
     

    Gotolei

    Member
    Has anyone else been having problems where alarm and/or notification volume will randomly mute itself? It's been an issue on and off for a month or two now. Just a few minutes ago, I noticed the popup for a new email, but no notification sound, so I checked the settings and sure enough notification volume had been set to zero somehow. I turned it up to what it's normally at, made sure the rest of the volumes were what they were supposed to be, then locked the phone and set it down for a few minutes. When next I picked it up and unlocked it, it opened back to the same settings screen to show that in the two or three minutes of downtime the alarm volume decided that it was its turn to zero out.
    Oftentimes, over the course of the night this will happen again. As far as I can tell there's pretty much no pattern, rhyme or reason to when it happens. How would I go about figuring what's going on? What part of the system handles volumes?

    Also. Does this rom have any special sauce for the auto-brightness, or is it just whatever's in aosp? A few weeks back it decided to be extra special and take completely black conditions in the middle of the night to be a good time to turn brightness up half as high as it can possibly go, and I've spent much of the time since then trying and failing to convince the braindead thing otherwise (setting it all the way back to minimum at the first opportunity). Is there a way to just change the response curves ourselves?
     
    Last edited:

    NecrolyseS

    Member
    Jul 11, 2017
    45
    0
    What is your--
    LineageOS version: lineage-16.0-20200109-nightly-enchilada-signed
    LineageOS Download url: https://mirrorbits.lineageos.org/fu...ge-16.0-20200112-nightly-enchilada-signed.zip
    Gapps version: 9.0 nano latest

    Did you--
    wipe: no
    restore with titanium backup: no
    reboot after having the issue: yes

    Are you using--
    a task killer: no
    a non-stock kernel: no
    other modifications: no

    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
    Successfully install the rom but got some bug: System stop working or something else (it's just blinking the pop up), unable to use home and recent button, notification bar can not be pull down 2nd time.
    Any solution? Please help me.
     
    Last edited:

    skid9000

    Member
    Sep 24, 2016
    6
    0
    I have a weird issue since the last update (January 7th), when i plug in my phone to the oem charger, it work correctly, but when i plug in my powerbank or my laptop, the led tell me that it is charging but Android tell me it's not... Any Idea ? (I use LineageOS for microG)

    (It worked fine before the update)


    Bad IKEA cable, sorry.
     
    Last edited:

    Top Liked Posts

    • There are no posts matching your filters.
    • 110
      2okPze5.png


      LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.

      LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

      All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

      Instructions :
      • Download the latest build and gapps
      • Boot to recovery
      • Flash the latest build
      • Boot to recovery again
      • Flash gapps
      • Reboot
      Downloads :
      Reporting Bugs
      • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
      • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
      • If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
      • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
      Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

      Code:
      What is your--
      LineageOS version:
      LineageOS Download url:
      Gapps version:
       
      Did you--
      wipe:
       restore with titanium backup:
      reboot after having the issue:
       
      Are you using--
      a task killer:
      a non-stock kernel:
      other modifications:
       
      Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

      XDA:DevDB Information
      [ROM][OFFICIAL][enchilada][9] LineageOS 16.0, ROM for the OnePlus 6

      Contributors
      LuK1337, luca020400
      Source Code: https://github.com/LineageOS

      ROM OS Version: Windows 8 Mobile

      Version Information
      Status: Testing

      Created 2018-09-08
      Last Updated 2019-06-15
      40
      NOTE: Before flashing these builds you have to flash latest Oxygen OS or Hydrogen OS in TWRP twice ( so that both A and B slots are flashed ); Oreo firmware is not supported and will not work on these builds.
      27
      Voila enchilada is official, commits merged.
      Expect a build by tomorrow
      16
      >Last build ~6h ago
      >Have you abandoned the project?
      Yeah obviously, can't you tell we did so?
      12
      I think OTA updates are a challenge for a/b devices like this one. Looking at the procedure how they are flashed manually, I am looking forward to see a way how OTAs achieve the same!

      OTA will be as simple as flashing from the built-in Updater
      Gapps ( or any other package that provides support for addon.d ) will be backed up automatically.