Pardon me if I fail to sum up the vast 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 ...
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 ...
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 ...
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).
LineageOS is Open Source OS. Google apps like Play Store, Gmail, Maps etc are proprietary Google products and cannot be bundled with LineageOS due to licencing issues.
However, you can always download these Google Apps Packages (Gapps) to run with LineageOS. These come in different flavors, starting with minimal Google services to full fledged suite of ...
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.
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 ...
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.
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 ...
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!
I rebooted into TWRP and edited /data/system/packages.xml. Under <package name="com.google.android.apps.nexuslauncher" and <perms>, I added the following lines:
<item name="android.permission.STATUS_BAR" granted="true" flags="0" />
<item name="android.permission.MANAGE_ACTIVITY_STACKS" granted="true" flags="0" />
When I rebooted back ...
Back in 2012, /proc/last_kmsg (1) used to be a dump of kernel console messages, exported after reboots by Android's ram_console functionality (CONFIG_ANDROID_RAM_CONSOLE), which used persistent_ram (CONFIG_ANDROID_PERSISTENT_RAM) to handle a block of RAM that wasn't erased across reboots (2).
persistent_ram was based on Linux upstream RAMOOPS code which ...
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:
Eventually, I found a workaround (which is not a fix but it allowed me to continue the installation).
Since my device was detected in discovery, I did not used sideload. I just pushed the image to the sdcard with:
adb push xxxxx.zip /sdcard/
and then I installed the image from the sdcard directly in TWRP.
Firstly you need to setup the build environment. You should be running Ubuntu 18.04. LineageOS build guide for a random device can be used as a reference. Reproducing the steps here:
Install the build packages:
sudo apt install bc bison build-essential ccache curl flex g++-multilib gcc-multilib git gnupg gperf imagemagick lib32ncurses5-dev lib32readline-...
AFAIK with LineageOS 14.1 (I have a rooted FairPhone 2), sshd is enabled by default and ready to use. Its config file is /system/etc/ssh/sshd_config which points to /data/ssh/ for keys storage. I guess you can reconfigure it to use /sdcard/. In theory, /data should be preserved across system updates, though I have not much experience to confirm it. The ...
The right-most way (bootctl)
The command to provide this information is bootctl. As root (having run adb root), you can use this like this,
$ adb shell bootctl get-current-slot
Note this is the slot's number, you resolve that to the letter with,
$ adb shell 'bootctl get-suffix $(bootctl get-current-slot)'
See also: How can I boot to a specific partition ...
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, ...
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.
You didn't look hard enough, but it's probably not your fault, because 1) the site of LineageOS (LOS) does not list devices formerly in the CyanogenMod (CM) build roster, and 2) the device is never a member of the official CM/LOS queue.
There are a bunch of unofficial CM builds on XDA-Developers, all the way up to Android 5.x, with various bugs. See for ...
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 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 ...