yashsingh1/xdaforums huggingface dataset:
[Moto Z Play Guides, News, & Discussion] Ultramanoid:
Shrep's build was done a week later, so a week's worth of Lineage commits and / or fixes over the older build.
[Moto Z Play Guides, News, & Discussion] akaleshnikov:
I'm having a hard time flashing these Lineage OS ROMs. I'm running stock 7.1.1 prior to flashing 14.1, but I keep getting error 7. It says I have 0xC113 but I need 0xC105/106/107/112.

I've tried flashing just the bootloader from the latest 7.1.1 but I'm still stuck and it's driving me nuts.

What am I doing wrong?
[Moto Z Play Guides, News, & Discussion] Ultramanoid:
Here's another unofficial build, but camera is now broken.

https://xdaforums.com/moto-z-play/development/rom-unofficial-lineageos-14-1-t3727440

Flashqueen's build remains the best fully functional one with at least up to most of December's patches ( even if it declares a November patch ) so at this point I'd still recommend it over anything else, other than getting a different, better supported device...

Edit : Lineage with MicroG support last put out a build December 17th, but those builds seem to be broken. I guess without a maintainer fixing things for the device, there's not much point in building as-is, see camera in the linked build above, for instance.
[Moto Z Play Guides, News, & Discussion] Mr_prfssnl:
Another good alternative to the above mentioned ROMs would be Mokee ROM. They actually support the device officially and it keeps getting updates on a daily basis. Although it is not actually Lineage it is in fact really close. It even comes with all of the Lineage features, wallpapers and apps by default. Another cool feature is that it comes with Xposed by default :victory:
[Moto Z Play Guides, News, & Discussion] Ultramanoid:
Thanks for the tip. I have many issues with that distribution, but went to check nonetheless, and was greeted with a warning to disable ad-blocking if I wanted to download a build, or leave. Seriously ? In a time when web advertising code is tracking, data mining and spyware at best, and plain malware at worst, that's ridiculous. I don't think so.
[Moto Z Play Guides, News, & Discussion] e-kai:
kernel patches?

A question for the people who have worked on the builds:

How do you find the patches that should be applied to the device kernel sources?

IIUC this repository is the kernel used by LOS addison:

github com /LineageOS/android_kernel_motorola_msm8953/commits/cm-14.1

It has a commit saying "Bump to NPL26.118-20". Does this mean you were able to update to the kernel sources from an official Motorola update? From where did you obtain the updated sources?

I found github com /MotorolaMobilityLLC/kernel-msm but didn't find matching patches.

(Sorry I'm not allowed to post real links.)
[Moto Z Play Guides, News, & Discussion] e-kai:
build from today

I just completed my very first build. I followed the instructions, and the build completed without failures. Does anyone have a scratch device and is interested to test if my build works? If yes, please send private message for a link.

I didn't change any code. It's just a snapshot of the current code, which I guess contains all the latest changes for the LineageOS core?

What work would be required on top of that to declare that a correct current nightly build?

22595f3457bc7ce34faded695d974e2713018447807e582c30bcb2e756926c54 lineage-14.1-20180104-UNOFFICIAL-addison.zip
[Moto Z Play Guides, News, & Discussion] zander21510:
I did the build with the broken camera...I used Alberto97's device tree and kernel instead of the Lineage repos, figured there'd be a few more fixes there. But I tried building from both, both had a broken camera. Didn't test long enough though to figure out if there were any other bugs.

Doing builds are pretty straightforward, it was even easy to modify repos. Anything else is outside my abilities currently though. I can try to fork and merge fixes...but it'd be working in the dark for sure.
[Moto Z Play Guides, News, & Discussion] e-kai:
Could you please describe the symptoms of the broken camera?

Even with older official builds, I occasionally saw some erratic behavior. When opening/closing the camera app too quickly, the camera app would report a failure on the next attempt to use it. But when being more patient, like waiting a couple of seconds before closing the app, and waiting a bit before opening it again, it worked for me. When I had experienced the misbehaving camera a while ago, I switched to the "open camera" app, which worked better for me.

EDIT: Answering the question myself:

The camera cannot be used at all. The built-in camera app crashes. The Open Camera app reports it cannot open the camera.
[Moto Z Play Guides, News, & Discussion] BtbN:
I never encountered any issues with the camera. Just did a new build from official sources plus a few minor Kernel CVE fixes, and camera works just fine.

https://btbn.de/files/lineage-14.1-20180104-UNOFFICIAL-addison.zip
[Moto Z Play Guides, News, & Discussion] zander21510:
I was able to fix the camera issue on my build, I switched to using the proprietary blobs from TheMuppets repo rather than just pulling them from the last official Lineage build- everything looks good now. I also forked so I could add 0x113 bootloader support:

https://xdaforums.com/moto-z-play/development/rom-unofficial-lineageos-14-1-t3727440
[Moto Z Play Guides, News, & Discussion] e-kai:
zander, are you using the oreo kernel branch for the 14.1 rom?
[Moto Z Play Guides, News, & Discussion] Mr_prfssnl:
You can just upload it to Mega and place the link in this thread. I'll try to check it out when I have the time :)
[Moto Z Play Guides, News, & Discussion] zander21510:
no, I forked Alberto97's Lineage 14.1-next branch. I didn't think the Oreo branch would work, especially with all the new 64-bit stuff going in.
[Moto Z Play Guides, News, & Discussion] Mr_prfssnl:
Indeed it's crazy how much data is collected nowadays. The capped downloader on their website is the worst thing about the ROM. On other fronts it's just fine, however original Lineage will always be better. What other issues do you have with Mokee?
[Moto Z Play Guides, News, & Discussion] Ultramanoid:
We're at a point in time when ad code is simply too dangerous a risk to allow, so requiring it is just a big neon sign saying 'stay away' as far as I'm concerned. I don't have a problem with anything requiring payment, but adware or ad code running anywhere ? No.

Regarding Mokee, to make a long story short, I run a barebones installation of Android based off Lineage, removing Lineage applications from the build, and several libraries and frameworks, I also don't use GApps or Google software, and other changes regarding security and privacy. ( The main advantage of Lineage for me is the fact that they fix bugs constantly and keep security patches up to date, and provide builds for devices other than the Nexus / Pixel, plus a few features such as expanded desktop, good ext4 mounting support, etc. ) Mokee just adds even more bloat on top of Lineage and basically just re-packages it with more unwanted extras.

Edit : Aaand, I think we have 4 ( ! ) working unofficial Lineage builds posted today, three mentioned from posters in this thread and a new one from Shreps. Haven't had time to download any of them yet, but wow. So much love.

( ^_^)
[Moto Z Play Guides, News, & Discussion] Mr_prfssnl:
I think we are pretty much on the same frequency here. I try to run all my stuff without Google services for the same reasons. I still require some functions of Google services to work though, so I use MicroG which is FOSS interpretation of the Google services. Regarding the bloat I did notice that Mokee used a little more RAM than Lineage. I also didn't like the fact that it came with Gboard as the default keyboard. Other than that it ran fine, but it still wasn't a match for actual Lineage.
[Moto Z Play Guides, News, & Discussion] e-kai:
Thanks for the information that newer motorola binary blobs are required. With the updated blobs, I can report success with my own build, too, my local unmodified build has a working camera, too. I wish this information could be recorded somewhere, but I guess linageos can't or doesn't want to link to a latest source of proprietary blobs as part of their build instructions. Having had that information before would have saved me a lot of time, I spent several hours looking through all the commits that were made to the various lineageos git repositories, trying to identify a commit that could have broken the camera. So apparently it's as simple, and as difficult to find out, that the latest lineageos code requires the most recent motorola proprietary blobs for compatibility.
[Moto Z Play Guides, News, & Discussion] zander21510:
I guess it was for legal reasons, the whole extracting blobs thing. It was pretty easy to figure out there was a repo and how to add it into the manifest though...does seem like an odd barrier for first timers though.
[Moto Z Play Guides, News, & Discussion] Mr_prfssnl:
I recently noticed that Alberto is making some tremendous progress on his AOSP ROM. He even got 64-bit support to work. I am very glad that we have such a talented developer working on our device.

I have been wondering about one thing though. Would it be possible to use sources from Alberto's AOSP 8.1 build to build Lineage OS 15.1 (when it comes out obviously) for our device?

The only thing that someone would need to do (I'd do it myself if my PC was powerful enough) is to merge his kernel, vendor and blobs with the Lineage OS source. I am no expert, but it seems to me like a thing that could be done quite easily. Any thoughts?
[Moto Z Play Guides, News, & Discussion] zander21510:
I mean if that's all it takes...I'll take a crack at it. I've got nothing to lose.

My guess would be that its a bit more than that but you never know...I didn't think I'd be able to do all the stuff I've learned to do the past few days and actually build & fix a working ROM...
[Moto Z Play Guides, News, & Discussion] Ultramanoid:
I've noticed all the builds I've checked so far declare a December security patch, I'm guessing Lineage has not merged the January one yet. ( As zander already said in the other thread. )
[Moto Z Play Guides, News, & Discussion] e-kai:
Let's try to collaborate to get us back to having an official build.

My understanding is that we have two device specific repositories that need attention and merging:

https://github.com/LineageOS/android_kernel_motorola_msm8953/commits/cm-14.1

https://github.com/LineageOS/android_device_motorola_addison/commits/cm-14.1

Regarding the kernel, since the last official build, we have the following contributions:

Alberto's kernel fixes:

https://github.com/Alberto97/android_kernel_motorola_msm8953/commits/cm-14.1-next

BtbN's fixes to pick up KRACK fixes:

https://github.com/BtbN/android_kernel_motorola_msm8953/commits/fix_krack

I've forked, and added the above at

https://github.com/kaie/android_kernel_motorola_msm8953/commits/cm-14.1

Then I looked through the Android security bulletins.

From

https://source.android.com/security/bulletin/2018-01-01#kernel-components

I found

https://git.kernel.org/pub/scm/linu...8&id=36c84b22ac8aa041cbdfbe48a55ebb32e3521704

which applied without modifications.

From

https://source.android.com/security/bulletin/2017-12-01#kernel-components

I found

https://git.kernel.org/pub/scm/linu...t/?id=49d31c2f389acfe83417083e1208422b4091cd9

which needed manual merging, but seems applicable for the older kernel that addison appears to be using.

Regarding the device, since the last official build, we have the following contributions:

Alberto's fixes:

https://github.com/Alberto97/android_device_motorola_addison/commits/cm-14.1-next

Zander's fix to the bootloader:

https://github.com/zander21510/android_device_motorola_addison/commits/cm-14.1-next

(I think we shouldn't use zander's fingerprint behavior change, that's more of a personal preference.)

I've added them to my fork:

https://github.com/kaie/android_device_motorola_addison/commits/cm-14.1

I've done a build with all of the above, and I've upgraded my primary device from the last official build (Alberto's Nov 6 build), to my local build, and so far everyhing has been working correctly.

e29d7d073ca6d2794b5c796a7cd9f98dcd74442b492f928ab186d4b7333ce0b6 lineage-14.1-20180106-UNOFFICIAL-addison.zip

WARNING: No guarantees given: http kuix.de /lineageos/addison/lineage-14.1-20180106-UNOFFICIAL-addison.zip

I see that a single REGRESSION bug is currently filed against addision

https://jira.lineageos.org/browse/REGRESSION-1080

but AFAICT, nobody has been able to reproduce that bug.

What else would we have to do to get addison back into official build status?

Zander, BtbN, how about we collaborate in identifying the patches that need to be merged to continue to keep official addison builds alive?

Thanks

Kai
[Moto Z Play Guides, News, & Discussion] Ultramanoid:
A maintainer recognized by Lineage, willing and able to work with the Lineage team, to get the device back on Jenkins for the building roster and keep it there. Lineage has recently become more strict on time limits to fix device-specific bugs, without an official maintainer, no way to fix bugs at all, no way to keep the device in the roster.

( As you say, the bug that took it out of the roster seems to have been a ghost bug, no one but the reporter saw it. )

Otherwise, amazingly put together, thank you.

If any, or all of you, are willing and able, contact Lineage.

Edit : I'm travelling and can't test properly, but is the build above the one with the correct Motorola camera blobs ? It doesn't crash but only get a black screen with the applications I checked. ( Barcode Scanner, Open Camera... ) Camera working fine.
[Moto Z Play Guides, News, & Discussion] mikehat:
I'll bring the beer...
[Moto Z Play Guides, News, & Discussion] sunng87:
Also, is there any chance to get moto mods work with lineageos? I saw some rom already supported.

The keyboard mod is finally available this year. I feel it's a solid addition to the phone. https://www.theverge.com/circuitbre...eyboard-lenovo-vital-health-sensor-z-ces-2018
[Moto Z Play Guides, News, & Discussion] zander21510:
I haven't really introduced anything new or fixed anything myself with my builds- just configured the right sources together to get it working. It's still basically using Alberto97's kernel & device trees, plus the proprietary Motorola stuff. Heck, the only bug I "fixed" on the bootloader I just copied from Alberto97's fix for his AOSP build!

If I can help get official builds going I will, I just don't think i'd be much help. My plan right now is to keep my 14.1 builds going regularly for security patches, and when 15.1 is finally officially released by Lineage, I'll try to build that.
[Moto Z Play Guides, News, & Discussion] zander21510:
I made another build yesterday, but the security patch is still Dec 5. Is there something I have to do to get the Jan security patch included? I thought it was handled by the Lineage source code, am I wrong?
[Moto Z Play Guides, News, & Discussion] Ultramanoid:
I thought so too. Looks like there will be an official Lineage build tomorrow since the device is back in the roster. Take a look when it's posted...

Edit : https://xdaforums.com/showpost.php?p=75204449&postcount=1279
[Moto Z Play Guides, News, & Discussion] Ultramanoid:
Lineage has bumped the security patch declaration to January today. The servers are likely to be offline all week, so no official builds until next Monday, but if you build yourself now it should be finally patched with the latest.
[Moto Z Play Guides, News, & Discussion] zander21510:
Heads up, if you're dying for a build, I made a new one, it's up on my thread. January 5 security patch, synced with the official Lineage repos, so when official builds start, it should be a simple upgrade with the migration zip.

Because, I have this funny feeling the builds might fail or something else might happen...:)
[HTC Excalibur] gadget_lover:
hi I was modifying some values and changed something i dont know what the original value was...can someone tell me whats does it say under HKEY_CURRENT_USER--CONTROL PANEL--SOUNDS--SMS? WHAT IS THE FIRST VALUE BEFORE SOUND? I'd really appreciate the help!
[HTC Excalibur] davewaave:
3 lines

I have:

first line: default, string, value not set

second line: category, string, Notification

third line: sound, string, \Windows\Alert-AscendingChimes.wma.

That's all thats in mine. Good luck.
[HTC Excalibur] gadget_lover:
Thanks davewaave! that did it!
[Tasker Tips & Tricks] murnworb:
Hi,

In Android Oreo you can now select your desired audio output when connected to bluetooth

See this screenshot to see which option exactly:

[IMG="Android O Audio output option"]https://imgur.com/gallery/9xcWm[/IMG]

(because i'm a new user this link is not showing correctly, here it is chopped up: https:// imgur.com /gallery /9xcWm )

(Concrete use case: play my Waze sound through phone speakers while listening to car FM radio and not using car media channel)

Is there any way to select this option throug Tasker?
[Tasker Tips & Tricks] giannisdoe:
Hi murnworb, did you finally figure this out?

I have the same question and havent been able to get an answer so far.

Thanks
[Tasker Tips & Tricks] murnworb:
Hi! Didn't find out through tasker but there's a setting in android Bluetooth settings that lets you choose per BT device what to play on it and what not:

imgur .com /CahQ3Fb
[Nexus 10 Q&A, Help & Troubleshooting] guitargod:
Hi!

I've read about Android Go in some news articles. It is intended for use in less powerfull devices.

Are there any chances for Android Go on the Nexus 10 or do you think it wont work because of the known issues with Oreo?

Greetings
[Nexus 10 Q&A, Help & Troubleshooting] rufy93:
Official, very doubtful since this device never igen got marshmallow.

AFAIK there is at current time no go AOSP image. Maybe when there is.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] jonatrey:
Hello,

I tried this morning to install a custom ROM for my sony xperia z5 compact. Unfortunately, it remains crashing on the "Sony" screen

I unlocked the bootloader via the official link https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/. Until then no worries, everything worked well.

Then I wanted to install a TWRP recovery via this link https://xdaforums.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050

I was able to flash it without worries but when restarting, TWRP asked me if I wanted to install the app, I put OK and from there, impossible to start my phone. "always stuck on Sony screen".

this is my config : E5823 / 32.4.A.1.54

I want just to start my phone. Is there possible to put a stock version? thanks

This is very urgent to resolve it unfortunately :(

Thanks for your help
[Xperia Z5 Compact Q&A, Help & Troubleshooting] jonatrey:
you can close this subject, problem solved. Thanks
[Xperia Z5 Compact Q&A, Help & Troubleshooting] lupus2401:
Wanna share how you fixed it?
[Xperia Z5 Compact Q&A, Help & Troubleshooting] jonatrey:
Yes sure,

I flashed my recovery with the TWRP 3.1.1 posted before with the command "fastboot flash recovery {name_of_file.bin}" and I did a flash of the boot with the good version of boot with the commande "fastboot flash boot {name_of_file.bin}.

I founded the good boot at this address for my version : https://xdaforums.com/z5-compact/general/32-4-1-54-coming-t3685995
[Xiaomi Redmi Note 4 Guides, News, & Discussion] Dr. Hurt:
This is a guide for people who want a rooted MIUI. It will keep stock recovery and system partitions untouched to allow MIUI OTAs to install without problems. It will also pass Google's safety net test so bank apps keep working. The best of both worlds really :)

Requirements:

- Unlocked bootloader

- Windows PC

- fastboot (present in the miunlock app folder)

- Latest TWRP (download here)

- Latest Magisk (download here)

Steps:

- Install latest Magisk app

- Put latest Magisk zip on your device storage (SD)

- Shut down device

- put latest twrp.img in miunlock folder

- Connect phone to PC

- Press volume down and power button to boot to fastboot mode

- Open "Command Prompt" on your PC

- Type: (without quotes)

----- "cd C:\Users\[your name]\Desktop\miflash_unlock-en-2.3.803.10" . (or wherever the folder is)

----- "fastboot devices"

----- "fastboot boot twrp.img"

- In a few seconds, TWRP will boot on your phone. DO NOT swipe to make changes to system.

- In TWRP, flash the Magisk zip

Enjoy root :cowboy:

Disclaimer: I will not be help responsible for any damage or loss caused by following those steps.
[Xiaomi Redmi Note 4 Guides, News, & Discussion] kn1g:
Does it mean I can install TWRP and flash xposed etc and still have OTA updates?

What is the difference to this one: https://xdaforums.com/redmi-note-4/how-to/red-wolf-install-twrp-root-device-t3708337

Best,

kn1g
[Xiaomi Redmi Note 4 Guides, News, & Discussion] ram1MB:
Same as my question. Let say system partition won't touch by root, but twrp is installed over the Mi stock recovery. Will it install Eta?
[Xiaomi Redmi Note 4 Guides, News, & Discussion] Dr. Hurt:
This guide DOES NOT flash TWRP. Stock recovery remains so OTA updates work.

The only thing that is touched by this guide is the "Boot" partition to install magisk. You can restore stock "Boot" using magisk manager's uninstall option at any moment and be 100% stock again.
[Xiaomi Redmi Note 4 Guides, News, & Discussion] kn1g:
Ok, but is Xposed etc. possible?
[Xiaomi Redmi Note 4 Guides, News, & Discussion] Dr. Hurt:
I haven’t tried but should work.

https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268
[Xiaomi Redmi Note 4 Guides, News, & Discussion] sobermind:
It is really works! Thank you!
[Xiaomi Redmi Note 4 Guides, News, & Discussion] xdaforo:
gonna check this cause i wanna root the phone but keep enjoying updates
[Xiaomi Redmi Note 4 Guides, News, & Discussion] Sergiuuuuuu:
I just rooted my Note 4 Qualcomm by this method, so far so good. Really easy and dummy-proof tutorial :)
[Xiaomi Redmi Note 4 Guides, News, & Discussion] xdaforo:
I bump this because it worked. Quite easy, clean and fast. Thanx!
[Xiaomi Redmi Note 4 Guides, News, & Discussion] masri.razak:
I already install latest TWRP for mido and latest magisk, but still I can not update my mido using OTA updater

Anyone can help me?
[Xiaomi Redmi Note 4 Guides, News, & Discussion] Dadovvv:
Wrong...u need to boot twrp not to install. Read the OP for steps.
[Xiaomi Redmi Note 4 Guides, News, & Discussion] masri.razak:
Well... That's I mean, boot TWRP using adb

After have TWRP, how can i get update via OTA?
[Xiaomi Redmi Note 4 Guides, News, & Discussion] arun6199:
it successfully worked for Redmi Note 4 global beta/stable MIUI9.2

even installed camera api 2 using magisk module
[Xiaomi Redmi Note 4 Guides, News, & Discussion] MayankMathur:
Just a quick question. I've TWRP right now with SuperSU. So I'll remove SuperSU, flash Magisk in TWRP. All good till now, but I'd want the stock recovery, a flash-able zip maybe. How can I get it? From where?

**[EDIT]**

Okay. One can get it from fastboot ROMs available at MIUI website (here), extract the pack and get recovery.img.
[Xiaomi Redmi Note 4 Guides, News, & Discussion] ahmed3110c:
Installed successfully on miui 9.2.1.0 stable

Now when a new update for magisk is released, how should i update it??
[Xiaomi Redmi Note 4 Guides, News, & Discussion] Giacomo_ITA:
I have two questions:

1. Why does the bootloader need to be unlocked and how can I do that?

2. What happens to Magisk if I install an OTA?

I'd like to keep the phone untouched but I need to change emojis and with Xposed I can use Youtube in background.
[Xiaomi Redmi Note 4 Guides, News, & Discussion] Baxeisindi:
1. sign on en.miui com and you can use xiaomi unlocker (after 72 hours)

2. two OTA updates and I had to reroot it :(

but it seems that it is not necessary, I can not post the link :(

google --> github magisk tips (it should be the first result)
[Xiaomi Redmi Note 4 Guides, News, & Discussion] Giacomo_ITA:
Do you mean this?
[Xiaomi Redmi Note 4 Guides, News, & Discussion] Baxeisindi:
Yes, I hope it works, anyway at the next update I will reroot it in a few minutes.