yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Q&A, Help & Troubleshooting] IronTechmonkey:
Thanks for re-posting here instead of in the development thread. FWIW, I'm using pattern to unlock the device with no problems, and have been doing so on multiple LOS 14.1 devices for a long time with no problems.

When you go to Settings > Security > Screen lock do you receive the prompt "Confirm your pattern"? If not then it would seem that the pattern is not properly set and you could try setting it again. If you do see the the prompt "Confirm your pattern" at that point then something else may be interfering.

- Make sure you don’t have any 3rd party utilities which might alter the security settings. For instance some utilities such as the "Secure Settings" app may be able to temporarily disable the lock screen.

- Make sure that you are not using the native Smart Lock feature (or any similar feature) to automatically to and conditionally unlock the device (eg when it is in hand or when it is connected to home wifi). You can review Smart Lock settings at Settings > Security > Smart Lock. Note: depending on various settings there may bee no items in Settings > Security > Smart Lock, in whcih case that may not be a factor.

Beyond that you may have tto do some external research or, for testing purposes try a clean flash.
[Moto G 2015 Q&A, Help & Troubleshooting] Shreeram02:
The pattern appears once after boot but after I unlock it once it just stops appereing
[Moto G 2015 Q&A, Help & Troubleshooting] IronTechmonkey:
That's good to know but you've not answered the questions that were asked or confirmed no 3rd party utilities or confirmed whether or not Smartlock is a factor. Those are things that others cannot do for you.
[Moto G 2015 Q&A, Help & Troubleshooting] Nikos dima:
Maybe you have any smart lock option enabled.. Chek that once
[Moto G 2015 Q&A, Help & Troubleshooting] IronTechmonkey:
... which is why I mentioned Smart Lock a few posts ago: https://xdaforums.com/showpost.php?p=77298106&postcount=432 ;)
[Moto G 2015 Q&A, Help & Troubleshooting] Nikos dima:
Ops I didn't notice that.. I though by 3rd party utility you was meant 3rd party apps.. I should read more careful before I post anything ?.

Sorry for my bad English
[Moto G 2015 Q&A, Help & Troubleshooting] IronTechmonkey:
No worries. It's still nice to have confirmation from more than just one person that checking Smart Lock is worth doing. Thanks.
[Moto G 2015 Q&A, Help & Troubleshooting] Shreeram02:
I'll ask him and tell u
[Moto G 2015 Q&A, Help & Troubleshooting] IronTechmonkey:
Ahhh, it sounds like you are working on someone else’s phone but don’t have direct access to it, which does add some degrees of diffficulty to the communication. In such cases, explaining the circumstances up front can save some time and trouble. In any event, check those things out when you have a chance then take it from there.
[Moto G 2015 Q&A, Help & Troubleshooting] Shreeram02:
actually that was my phone I sold it to him so he has that problem
[Moto G 2015 Q&A, Help & Troubleshooting] IronTechmonkey:
How it got there does not matter. The key point being that it may take some time to answer various troubleshooting questions.
[Moto G 2015 Q&A, Help & Troubleshooting] Shreeram02:
Ok thanks for the help I took the phone and clean flashed it now it is fine
[Moto G 2015 Q&A, Help & Troubleshooting] IronTechmonkey:
Please note the difference between development threads such as the one where you initially posted your question and general thread such as this one where I've answered. If you’ve not gathered the requisite bug testing details or clearly established this as a ROM issue then you should post in general thread such as this one rather than in the development threads.

As to the issue you are experiencing:

If you experience that problem in "each and every ROM" (except for stock) then this is most likely not an issue with this individual ROM. This is not to say that it could not possibly be a ROM bug but if it is, then there is more you would be expected to do in order to report it in development threads.

- Confirm that you are testing in a clean flash of the most recent build with no 3rd party factors such as custom mods (Xposed, Substratum, viper audio, SuperSU Magisk). In fact it’s good to describe the exact flashing process you used.

- Provide specific details about the device, the SIM and the carrier, the specific ROM build, the specific Gapps package, and any additional items that were flashed.

- List the exact steps you take to reproduce the issue.

- Provide a log taken while you reproduced the issue.

Once you have gathered all the requisite bug reporting information, then post in the development thread and or at LOS Jira https://jira.lineageos.org/. Note: LOS Jira is Lineage OS’ official problem tracking system.
[Moto G 2015 Q&A, Help & Troubleshooting] Ellahi:
How to get certified play store any one help me..!
[Moto G 2015 Q&A, Help & Troubleshooting] olimpero84:
I had to go back to nougat because oreo is immature to use every day and I can say that previous bugs like sending videos by whatsapp were solved
[Moto G 2015 Q&A, Help & Troubleshooting] IronTechmonkey:
For similar reasons I never moved from Nougat to Oreo. To your point the WhatsApp Video issue was resolved by some commits from squid2. Also there have been many more device specific commits from squid2 as well as many general LOS commits in the last few weeks.
[Moto G 2015 Q&A, Help & Troubleshooting] JJamesC:
LOS can't work alongside TWRP?

Hi, thank you for your hard work. I've noticed that this ROM (LOS 14.1 last update) does not support being installed allongside a custom recovery (twrp-osprey-3.2.1-r1), Is there a particular reason for that? I need sometimes to perform backups so I can test last builds of this rom, (If they are too buggy I often would go back to a previous version). But for that purpose I need to keep flashing the original boot img, making kind of extra work speccially in this particular cases:

1. After doing a backup

2. After restoring a backup (cause since boot got modified when flashing twrp, the file required to boot again won't be there, so I have to flash again the original boot.img included on the RAR package of LOS).

3. After every updtate LOS selfpatches, and appreciate that a lot... but it's not a way that this ROM work perfectly with TWRP? Otherwise this brings me the and 3rd maybe major issue: I have to procure the original boot imgs of every version. (14.1, 15, 16 ) And in some cases, one boot.img can get outdated enought so I will have to search for the new one (included on the new update packages via OTA and moving it to the pc so I can flash it again). Causing to constantly digging the RAR for this images. I think the rom its worth it to do all of this, mainly because of stability. But if I could know how to adress this problem I'd be more than perfect! Im kind of newbie to xda, dont bash me if I'm doing something wrong please :(
[Moto G 2015 Q&A, Help & Troubleshooting] IronTechmonkey:
LOS can be flashed just fine with TWRP, in fact that is the most common way to do so. I flash LOS several times a month on 3 different devices ( including Osprey) with the appropriate version of TWRP for each device, and I have several terabytes of successful post-installation TWRP backups of those ROM builds. I'm not sure what you mean by "After every updtate LOS selfpatches" unless you are flashing an older build or the wrong build and then the LOS updater offers a newer build. Once you have properly clean flashed latest LOS build with latest compatible Gapps and LOS SU (if you use SU) there should be no update offered, no patching required and no need to fiddle with the boot.img.

Unless something has gone very wrong in recent builds (which seems unlikely) you might consider reviewing your flashing process and the resources you are using so; In general terms for the Osprey device (including some things you may already know and may have already done):

Disclaimer: I'm not responsible for anything that goes wrong by following this advise, be that loosing data, bricking your device. At least make sure you have some sort of backup of your data.

- Unlock bootloader. Once this is done you need not and probably should not try to change it or re-lock the bootloader.

- Install TWRP. One of the nice things about Osprey is that one of it's primary maintainers (squid2) also makes a version of TWRP for it which is available here: https://xdaforums.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537. You can also use the regular version of TWRP from the officail TWRP site but I'd suggest using squid2's TWRP, following the instruction in that thread.

- In TWRP wipe dalvik and system caches, then factory reset (full wipe).

- In same TWRP session flash latest official build of LOS 14.1 and latest compatible gapps package (recommend OpenGapps) and LOS SU (if you use SU).

- Wipe dalvik and system caches again.

- Reboot to system.

In some cases, depending on the past history of the device and which ROM it had previously been running it may be necessary to put a stock ROM on the device and start from the beginning but this is more than I could offer advise about.
[Moto G 2015 Q&A, Help & Troubleshooting] JJamesC:
Oh right, my problem is: whenever I install or update my LOS, my custom recovery goes off (gets overwritten with stock recovery). Is it normal? And also, when flashing TWRP my device would only reboot itself to custom recovery (can't log until I flash original Boot img). I'm aware that this rom does not endorse the use of integrated root because of restrictive root apps such bankary ones, and thought that they designed the TWRP in the same way to avoid this kind of problems. But because of what you are telling me... maybe this wasn't to be designed like this... (overwritting TWRP)? BTW I'm already using the recovery that you recommend (the one with the green theme of squid2). Thanks for your fast reeply.
[Moto G 2015 Q&A, Help & Troubleshooting] IronTechmonkey:
I cant tell what the problem is except to say that you seem to be doing things well outside the recommended process and procedures.

LOS' native root (not to be confused with fully managed SU) should not prevent the device from being "certified" in play store HOWEVER NOTE: There seems to be a recent issue with recent LOS 14.1 Osprey build which may cause "uncertified" status even without root. you can (and should) review the relevant recent posts in the Osprey LOS 14.1 development thread. A subtle clue that this is a real issue is that squid2 thanked the post in which that issue was reported.

As to SU: LOS has it's own SU package which you can install separately - unless you want device to be certified or can hide SU with Magisk (not recommended until you sort out other things)

As to TWRP: TWRP should not have an impact on Google "certified" status, although it would prevent the device from receiving stock OTA updates even after reverting to stock unless re-locking bootloader.

To get philosophical about it.

- Stop.

- Forget what you know.

- Regroup and reconfirm resources.

- Re-learn methods. General research.

- Give it another go.
[Moto G 2015 Q&A, Help & Troubleshooting] JJamesC:
Understood, I will read the relevant LineageOS posts first (may have begun with that in the first place, really sorry), reconfirm resources and try it again. If I'm able to report back I'll do so. Thank you a lot.
[Moto G 2015 Q&A, Help & Troubleshooting] rtrock:
Information regarding the nightly updates

There are some doubts which I need someone to clear for me .

1. Can we download and Install the nightlies automatically or do we have to do it manually via twrp recovery?

2. While updating the latest build via recovery , will our phone's memory and the apps which are there on the phone still remains ?

3. Do i have to re-root again after updating my phone with the latest nightlies ? Currently I am using Magisk for Rooting .

Thanks :)
[Moto G 2015 Q&A, Help & Troubleshooting] IronTechmonkey:
Either of the 2 things you mentioned:

1) Use the built in updater automatically or manually. IDK If the built in updater avoids the need for a manual TRWP session, but it notifies you when an update is available and may save saves some steps.

2) Install manually via TWRP. Good for clean flashing*, or when other TWRP features may be of use; eg. use TWRP built in file manager to recover logs.

Yes by dirty flashing, and this gets us to the difference between dirty flash and clean flash:

Dirty flashing is flashing the new ROM and Gapps package on top of the previous installation without doing a full wipe/factory reset (just wipe dalvik and system caches). Contrary to the name, dirty flashing is not a bad thing, in fact it is expected. We are supposed to be able to update that way. Apps and their data should persist (but may not in all cases*).

The plot twist: Regarding reporting ROM related bugs; dirty flashing introduces doubt about the cause to any discovered issues so if there are problems after a dirty flash, the next step is often to reproduce the issue for logging after a clean flash.

Clean flashing includes at least a factory reset and sometimes manually clearing more device locations/partitions. Good for ROM testing, yields generally more stable long term results at the expense of some extra time at each flash. I have a strong bias toward clean flashing for the more stable results and the cleaner base for bug reporting as well as some reasons beyond the scope ATM.

[Nota bene: No matter what you do, you should at very least have a backup of all data that is important to you. There a variety of ways to do that. At best you could have backup of all apps and app data (eg. with Titanium Backup) as well as full nandroid backups created with TWRP,.]

It is generally best practice to flash ROM, Gapps and SU package (whichever one you use) during the same TWRP session but I always clean flash and use LOS SU. You could search and review Magisk related resources to see if Magisk would persist through a ROM flash of has its own backup method.
[Moto G 2015 Q&A, Help & Troubleshooting] LARN:
hi. what is the most stable version of lineage os 14.1 for moto g3 2015 ¡?¡???

Because I have the version of the first of September installed and everything else well, but the equalizer has bugs, it is not activated right away and well, it is a very good equalizer.
[Moto G 2015 Q&A, Help & Troubleshooting] rtrock:
LOS 14.1 with all the nightlies are almost stable and none of them have any bugs .

Even if u r facing the bugs in the stock equaliser then just dont use it , instead use the equaliser of ur favourite music player .

To help developers work on the equaliser bug , provide them the logcat .

Peace out [emoji4]
[Moto G 2015 Q&A, Help & Troubleshooting] LARN:
Well, i use it because It very well equalizes the Samsung headphones. The bugs that i mean is that with the last version i had, i don't remember which, actives the equalizes by blocking and unlocking the screenshot. But with this version i do it and that does not happen, It is actives only after 10 or 15 minutes unlocking the screen. And the equalizer Musicana brings, which is the application i use to listen music. IT IS VERY BAD hahahahahaha xD:laugh:
[Moto G 2015 Q&A, Help & Troubleshooting] IronTechmonkey:
I'm sorry that you cannot tell the difference between spam and constructive coaching about how to report bugs and how to communicate in development threads. Ironically, your off topic messages in the development thread are indeed spam, unlike the thoughtful coaching that I provided to you. You must have been looking into a mirror when you felt the need to accuse people of spamming.

My statement about false claims of clean flash was obviously not directed specifically at you, but it does matter to you for the following reason; As a result of the frequency of such false claims few people will believe the statement "I clean flashed" without seeing a list of steps that were performed. Also, your initial post about camera was relatively useless as a bug report as it contained none of the expected confirmations of clean flash process without 3rd party factors, and it included no specific step-by-step description about how to reproduce the issues, and included no log. Those things are all expected when reporting bugs, and since reporting bugs is the purpose of the development thread, I've replied here in the Q&A thread.

BTW, From the point of view of someone who was entering High School before you were born, the fact that you are 42 and speak as you do seems more like something to be embarrassed about than something to brag about. In any event you would benefit from learning more about the expectations of reporting bugs and communicating in development forums, and could start here: https://xdaforums.com/wiki/Reporting_A_Problem_-_Android.
[Moto G 2015 Q&A, Help & Troubleshooting] JJamesC:
My Experience so far:

1. The nightlies Can not be installed automatically, (if you use the built in updater It goes to the 'no command' display and wont update anything. You even will receive an error message when rebooting. This happens I think because of motorola's stock recovery cant install the updates. So... To update: first download the update, flash twrp, and then access to the custom recovery. It will update automatically.

2. After automatically updating the phone with twrp. All your data will remain. (Nonetheless, beware of posible bugs/failures during the proccess, so keep a backup of your important data.

3. Can't really help with that, because I'm not a fan of rooting. Really Sorry
[Moto G 2015 Q&A, Help & Troubleshooting] IronTechmonkey:
FYI, It is typically considered inappropriate to ask for ETAs, and development threads such as the one in which you posted that question are the worst place to do that - which is why I've replied in this Osprey LOS Q&A thread.

In regards to your question, there are indications that developer squid2 will be working on LOS 15.x for Osprey after doing some other stuff. You can find further details by reading the last dozen or so pages of the development thread or reviewing squid2's recent posts in that thread (where he makes an announcement about this). Beyond that, no time-line has been stated and it is not ours to ask for one.
[Moto G 2015 Q&A, Help & Troubleshooting] IronTechmonkey:
Has anyone else experienced this: No notifications for group MMS messages until phone has data connection?

I'm not referring to the manual download of extra content (eg image or sound file) which might be required after receiving a message notification while off-line, but rather I'm referring to missing notification for group MMS messages which don’t include any such content. Those notifications don't appear unless until I connect to a data network (which could be many hours after the message was sent).

I've been experiencing this in LOS on several devices for the past year or so and don't know if it is...

1) Just a limitation of that type of group messaging. (I typically use only SMS).

2) Something that could be tweaked/fixed by modifying APN (Will check with service provider).

3) A glitch or limitation of the LOS ROM (this seems very unlikely).
[Moto G 2015 Q&A, Help & Troubleshooting] rtrock:
Is moto g3 (osprey) compatible with Dolby atmos and if it is then how to install Dolby Atmos and make it work ?
[Moto G 2015 Q&A, Help & Troubleshooting] Gravemind2015:
Adb doesn't work in fastboot mode. The point where fastboot works, do you see an android robot? There should be device info shown at the bottom too.

Try power+volume down button for 15 seconds to see if it lands you on a similar screen.

Once you've got to the bootloader mode (where you can access fastboot) you can follow this guide to get back to the stock ROM.

Broadcasted from Zeta Reticuli
[Moto G 2015 Q&A, Help & Troubleshooting] PeTeAQ:
Hi!

I don't see anything on screen - it is absolutely blank (it looks like it is off, because even backlight is not turned on).

It may be lcd issue?
[Moto G 2015 Q&A, Help & Troubleshooting] Gravemind2015:
Could be, but as you said it happend after a software issue which is weird.

Anyway, if fastboot recognises the device, you can use that guide. If you come across "preflash validation failed", then just skip to the next command.

Make sure to select latest firmware file of the the right variant.

Broadcasted from Zeta Reticuli
[Moto G 2015 Q&A, Help & Troubleshooting] JJamesC:
My question is how to update this ROM (easily)? Whenever I try to update from the 'about the device>LineageOS updates' section. the update is able to download but after I hit the update option... device reboots into a green android icon that says 'no command'. So... after rebooting the phone I get a notification that says 'update error'. Is there a possible way to update the ROM without using the adb commands? Sometimes I just dont have a pc to be installing customs recoverys and then updating from them. Id rather update all from the phone itself. Thank you!
[Moto G 2015 Q&A, Help & Troubleshooting] Gravemind2015:
The 'no command' screen is of the stock recovery.

If you flash the latest squid or official twrp on your device (required only once, is permanently installed after that), the next time you tap "update", it'll boot into recovery (now twrp) and automatically start flashing the update. Once finished, it'll either reboot back automatically (can't remember the default behaviour) or will show a "reboot system" button.

I used to use the built in updater back in marshmallow days (when the ROM was called cyanogenmod), and I remember you could add all the zip files that'd be automatically flashed after updating the ROM. I don't know if it's still available, but that's where you add some mods that you use (if any). Once set-up, it's nearly automatic.

Hope this helps.

Broadcasted from Zeta Reticuli
[Moto G 2015 Q&A, Help & Troubleshooting] JJamesC:
Not the same behavior

Okay. This is where my device has a different behavior, If I flash squids2 recovery you said It should be only flashed once and It'd remain there. But After installing every update (from this same TWRP), this TWRP just disappears. That's right, ROM updates correctly but if I try to go to the custom recovery... I only can access to the default recovery mode (the green Android screen) and... If I flash the TWRP again (to have the TWRP installed and ready for the next update) device won't boot until I flash the boot IMG provided with the ROM. And that's why I always need a PC and ADB commands to update. Would you mind providing me the link to the proper TWRP version I should use to avoid this? (I remember I went to squids 2 thread for TWRP Moto g 2015) but still kind of new to XDA and may have messed up something. Thank you!
[Moto G 2015 Q&A, Help & Troubleshooting] IronTechmonkey:
This could be an issue with process rather than resources. Are you by any chance wiping recovery as part of your flashing process?

In any event, in almost all cases squid2's TWRP should work as well or better than official TWRP. I've been using squid2's TWRP for a few years on this Osprey device and have used his TWRP versions for other devices as well).

A few suggestions:

- Thoroughly list and review the steps you take during your flashing process (every actions, tap, swipe, button press, etc) so we can see if something in that workflow is messing up TWRP.

- It is good practice (although not always necessary) to boot into your the newly flashed TWRP and into your existing operating system a few times after flashing TWRP but before using TWRP to flash ROMs.

- If your workflow seems okay and problems persist then it might be worth testing with official TWRP. IMO this seems unlikely, although not impossible.

[EDIT]Just realized that you are flashing a boot IMG file. That should not be part of normal clean flashing. You should only need to flash the ROM, a gapps package, and if needed an SU package.