I'll supplement the answer of @beeshyams: since Android O is still in Dev Preview phase, the source code is still incomplete, and no custom ROM (LineageOS, etc.) could even base their work off it. LineageOS (back in their CyanogenMod days) also stated time and again that they will not touch Dev Preview code.
To reinforce the fact: until Android O is ...
These /data-related errors are likely because TWRP can't decrypt the current /data partition. This often happens with stock ROMs, since TWRP is only made to handle the encryption method of AOSP.
To work around it, in TWRP, choose Wipe - Format Data. This will wipe all data from the device, but at the same time remove encryption and allow you to start off ...
You normally don't need to re-flash GApps as most GApps installers will install an addon.d script which restores GApps automatically after flashing a new ROM that supports addon.d (LineageOS does so).
If you are using Open GApps (http://opengapps.org/) you are on the safe side.
Some basics first:
NoGAPPS is deprecated and got replaced by its successor, µG (read: microG).
µG includes the core (basically, GServices) and also UnifiedNlp.
No GService replacements will support the Google License API. That's much too hot an area. While we all love dentists, we better not see them working on us (replace "dentists" by "lawyers" in this ...
If Moto themselves did not update your device, there is no way you can obtain an authentic system image. Even when your device is updated, Motorola is very slow to update the latest image on it's website, and you would have to depend on images obtained through unofficial means hosted on sites like XDA
Related Security Patch level old on Moto G5
Every update would fully overwrite /system and carry all history changes, therefore just installing the latest build would sync you up to progress.
There will be (rare) occasions where the developer pushed patches that negatively affects the build (e.g. wrong CPU governor causing the phone to lag or heat up). On top of that, Android security patches, which ...
If the auto install doesn't work you can go to /data/lineageos_updates and install the update manually.
Remember to wipe dalvik cache after flash ends.
Updated (thanks to Sup3rHugh): LOS changed the OTA folder from /data/data/org.lineageos.update/app_updates to /data/lineageos_updates.
I had this problem. I'd half installed Pinyin so continual prompting for a login account.
Go to Google play store and search for Google Pinyin Input. When that appeared there was an option to uninstall it (because it had already been installed).
OK, so this means that you have an outdated version of TWRP which, apparently, does not correctly report the device model name (it's empty). --
Updating TWRP from 3.1.0-0 to latest is 3.2.2-0 solved this problem!
You can download Gapps package for your lineage from this website source opengapps.org.
Site contains several fields such as :
ARM64 - For 64-bit devices
ARM64 means the devices that are running 64 bit operating system/processor.
ARM - For 32-bit Devices
ARM means the device that are running 32 bit operating system/processor.
for Intel ...
@timoschwarzer already described the persist function of (most) GAPPS packages, so I'd approach this from a different side:
You are still advised to update GAPPS from time to time (in orders of months), due to Google introducing new functions, APIs, etc. in updated versions of their apps, but not doing this usually doesn't affect working aspects of your ...
At the birth of Lineage OS, it's a direct fork (i.e. full copy) of CyanogenMod sources at that time, so it's obvious that LOS is a continuation of CM, not a replacement to it. Thus, aside from differences introduced by individual maintainers, and a few renames here and there in the OS, all that's left is the ROM's age - a CM ROM is definitely compiled before ...
On a rooted device, it is possible to disable/enable user apps using a terminal emulator.
To do so, open a terminal of your choice, enter
to acquire root privileges and then enter
pm disable <packagename>
Take care to replace <packagename> with the package name of the app you wish to disable (for example, if you wish to disable WhatsApp, ...
Go to Settings.
Click on About phone and then tap 7 times on the Build number.
Navigate back, open Developer Options.
Tap Root Access.
Select Apps or Apps and ADB.
Now you have root and Titanium Backup finds it:
You should. That is a "clean flash" and is normally recommended in installation instructions. This ensures that the ROM is written on a clean slate
At times, like in the case of "nightly" ROMs or some mods to ROM, /system is not wiped but written over the existing system called "dirty flash" (not even /data or cache is wiped)
As a thumb rule, switching ...
Even since LineageOS was known as CyanogenMod, it offered a deeper way to manage apps' permissions than the one introduced by Google from Marshmallow onwards. This feature, known as Privacy Guard, can be accessed from within Settings -> Privacy.
To restrict it from starting on boot, hold on the target app in the list that's displayed, then find the Start at ...
Though you did not (yet) confirm both devices are rooted, this solution might be of interest for those where they are:
Following up to our adoptable-storage tag-wiki, you will find a link to How to decrypt adopted storage? Based on that, the following approach seems feasible:
From the original device, extract the encryption key file located in /data/misc/...
If you install CyanogenMod 13 then you cannot install lineage OS 14 without wiping the device.
If you install CyanogenMod 14 then you can directly install Linage OS 14 without wiping the device, but it is not guaranteed.
If you install CyanogenMod 13 then you may install Lineage OS 13 without wiping the device, but it is not guaranteed.
Lineage OS web site ...
Here are some answer, but as I'm not Cyanogen representative, they only engage me.
Users will not receive OTA updates as soon as they stop maintaining their software stack. You keep on using your last Cyanogen ROM and hence receiving no more security updates, or you can change the ROM you install. For changing, you could use an entirely new one and try to ...
S Note is tightly integrated with Samsung's framework and thus can't be ported to non-stock-based ROMs.
In the meantime, try Squid as an alternative. Lots of available pre-defined notes, export to PDF, and best of all it makes use of the spare button on the pen that LineageOS doesn't use.
As far as I can tell, Android OS (sometimes called OS + others) is not actually a real application to say. Basing this on one data application I've used it is explained;
It is a "catch all" pseudo-application accounting for the difference
between global usage (displayed in the main screen) and the sum of all
installed applications usages.
You just need to configure the dhcp.
Open Terminal emulator and type in: su . The $ will change to #.
Type the following command in Terminal Emulator:
netcfg rndis0 dhcp
The name for usb interface inside Android may vary. It is usually rndis0 or usb0. Type busybox ifconfig to identify the name.
It can happen that automatic dhcp method does not work. In ...
n2awifi is the TabPRO 10.1. You might be referring to n1awifi (which you correctly mentioned in your other question).
Sometime during development, some Samsung devices were reassigned codenames, and lt03wifi was renamed to n1awifi (see commit here and developer note here).
No need to worry as these are still the same device, and the ROM itself has ...
Pardon me if I fail to sum up the wast subject in a brief answer :)
SELINUX AND AVC DENIALS
Android is based on Linux kernel that makes use of Discretionary and Mandatory Access Controls (DAC, MAC) to restrict access to system resources such as files on a certain filesystem. DAC includes classic UNIX RWX file modes, owner/group or UID/GID, Extended ...
Yes, binary blobs are part of Android filesystem. Android can't boot without them as they are kind of hardware drivers for the device. Most of those are found under /vendor/lib(64), some also under /system, /etc and /bin. Before Android Treble, /vendor wasn't necessarily a partition but a symlink to /system/vendor directory. Starting with Oreo, /vendor is a ...
I ended up going ahead and just removed the Jelly browser – initially manually by using TWRP's file manager and later – since it came back when I updated the system afterwards (duh) – using a handy flashable zip that I got from LOSdiet. So far, so good. Everything seems to work fine.
As for WebView, the Android System WebView entry in the developer settings ...
Use this tool to upgrade your bootloader to a compatible version.
You should also update your TWRP to the latest version, as older versions aren't compatible with the new bootloader either, and will display a moving line across the screen if you insist.
After these steps you are clear to proceed to flashing LOS 14.1.