Search results

@braveheart_7 LOS for MicroG are unofficial builds, so it is hard to say when updates arrive for them, mosty a longer time period afterwards. For me, i use official LOS for my device, installed Magisk, installed MicroG GMScore.apk und used Nanodroid patcher for signature spoofing. Keeps me...

@Dante_XDA That is fully usual during boot to system. Near 10 sec the Motorola screen and after that a few seconds trhe LOS boot animation, then the lock screen comes up.

@mikedeaster I use this one on my Moto X4 (XT1900-7): https://apk.support/app/com.motorola.camera2 Switch between 4MP and 16MP for front camera in options possible.

All necessary stock firmware you could find here: https://mirrors.lolinet.com/firmware/moto/payton/official/ Also you may have a look in this thread: https://forum.xda-developers.com/t/guide-video-text-how-to-flash-official-factory-firmware-moto-x4.3808348/

Maybe have a look on this? https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348 I did update from Stock Android Oreo to Stock Android Pie for my MotoX4 XT1900-7 RETEU before start to install LOS according to the warning you mentioned in wiki instructions.

I used just "fastboot flash boot twrp-payton-xxx.img" to flash TWRP, after that the parts with the sideloads of copy_partition.zip and LOS-Payton-xxx.zip

For me it worked with following exactly the wiki instructions from LOS download pages. Started with update MotoX4 XT1900-7 RETEU from Oreo to latest Pie as Warning said so.

Have already tried Moto Camera 2 APK or Open Camera with LOS 17.1?

Does TWRP 3.4.0-0 (https://dl.twrp.me/crackling/twrp-3.4.0-0-crackling.img.html) have same issues for you?

If i use the zip, i have to reinstall it after every LOS update? When yes, why not provide as an usual apk, that is survive updates as usual?

OTA update replaces TWRP with Lineage recovery (as usual on A/B devices) and i don't want it to reinstall all that time, that's why.

New TWRP version twrp-3.4.0-0-payton.img (https://dl.twrp.me/payton) is working fine for me so far. - Able to decrypt data partition with my PIN code when entering TWRP. - Backup to my SDcard also worked flawless. But i will still use it only temporary with "fastboot boot TWRP.img" if...

I followed this post https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348 to install Stock Android 9.0 before starting install of LOS 17.1

Seems like your TWRP version was not able to decrypt data partition. Boot to system and disable encryption for your phone (Lock screen -> none). Boot to recovery again afterwards. Try flashing your zips.

I use Moto Camera 2 without issues from here https://forum.xda-developers.com/moto-x4/themes/mod-rom-t3982965

Dirty flashed it over my LOS 16.0 (after preactive uninstall of addonsu) with TWRP-3.3.1-0. Installed Magisk for root. Works all fine by now.

LineageOS build queues are running again after that long suspend! :) Newest LOS 17.1 payton is already available for OTA and download. ---------- Post added at 06:11 PM ---------- Previous post was at 06:09 PM ---------- Dis you follow exactly the instructions wiki? Updated to at least...

https://download.lineageos.org/payton

If you bring all necessary .zip files on SDcard, then install from TWRP.

Put your TWRP.img (replace with the full filename) into the folder where adb and fastboot are in. fastboot boot TWRP.img or fastboot flash boot TWRP.img OR Look here: https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348

See here: https://www.reddit.com/r/LineageOS/comments/gbdlzx/lineageos_downloads/

There is some fixing on official TWRP for payton just in progress. See https://forum.xda-developers.com/moto-x4/development/dev-testing-t3707432/page38

Started with the Moto X4 on stock rom 8.0, flashed latest stock rom 9.0 because of warning in install instructions. Rest was fully as described in the install instructions. Installed no GApps, but Magisk. Circle Clock and Moto Cam just for test. All working fine, beside TWRP issues with...

Yes, that is also the result of my test with different lock screen setups. Every time pattern, pin or password is involved, TWRP shows the password request at start and neither pin nor password is correct.. So, i will use the "workaround" too, hopefully not necessary to boot to recovery often...

On another phone with LOS 16.0 also locked by PIN code, i have no issues in entering TWRP when boot to recovery, is this new behavior on LOS 17.1? Or is it just a momentary lack of compatibility in current TWRP version?

What is the preferred recovery for that LOS 17.1 version? I tried TWRP 3.3.1-0 (also temporary used for first install), but being asked for decrypt password for data at recovery start, which is unknown to me, so cancel is only option there (causing issues?). So i am back on LOS recovery now...

Did you activate Root in Developer options after installing in TWRP?

Hi, have you tried to optimize your gps.conf for your country (Timeserver, Links to nearer location)? There could be some tutorials found for that and it is worth a try. BR wkn

Hi, short question to the bluetooth fix, is it persistent over an update of LOS or do i have to install it again then? BR wkn

LOS is mostly very stable and also very responsive on my Swift. If an update does anyhow not work, i will recover my backup taken before in TWRP. For functionallity from original software missing, i couldn't tell you. It was only a few days last year since i changed to CM and now to LOS wit the...

Testing LOS builds 170918 and 170025 without flashing Foxy Kernel 2.7 works fine without any reboot issues for two days now. Smiff3: Mostly every new build is a little bit more stable than the one before, but issues could happens all the time. There are no stable or snapshot builds with LOS as...

Hi, i am facing more often reboots on Swift 1 with LOS 170918, Gapps Pico and Foxy 2.7. There is no defined reason recognizable, happens even when lockerd. Before build from August did not show this. BR wkn

Todays update lineage-14.1-20170508-nightly-crackling-signed solved the wifi issue for me (without installing Foxy kernel in addition). Thanks to the devs :)

With 20170501 build, the wifi issue still persists for me.

Until todays build, i had never any issues with the update from LOS, without use of any additional patches. So, i hope the issue will be fixed with the next builds.

Hi! Installed new build a short time ago, but found issues with WLAN. It is not possible to deactivate WLAN connection neither in quick tiles nor in options. Causes reboot after a few seconds of freeze. Reverted back to previous build at the moment. Greets, WKN

Hi, will there be a .zip version for update with installed TWRP soon? Thanks in advance wkn