yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] IronTechmonkey:
An objective comparison tell me otherwise:

- Created by a well meaning but inexperienced user vs. Created by an experienced user who has created most of the highly frequented Moto Q&A threads.

- 2 pages of posts vs. 33 pages of posts.

- Few posts by experienced users vs. many posts by very experienced users.

Of course you can use whichever you think might have information that you could use but I'll stick with the one that has the larger repository of information and more experienced users viewing it.

---------------------------

Anyhow, that's OT, getting back to LOS 17, I'm going to wait for the next build to report a graphic glitch previous described in this thread, and maybe also one for the 2024 date upon reboot.

Regarding the later: Is there anyone who is not getting the 2024 date or other very wrong date upon reboot before on-line time sync? e.g. turn off all data connections, > reboot > after reboot time and date are very wrong until going on line. This issues causes nandroid backups made in TWRP to be dated 2024 and causes some apps to have issues with expiration until the date is properly set.
[Moto G 2015 Original Android Development] woheller:
Wrong date

In my case it is just about a month away from now...

I created a bug report here: https://gitlab.com/LineageOS/issues/android/-/issues/2236

---------- Post added at 04:36 AM ---------- Previous post was at 04:33 AM ----------

Bluetooth

I created a bug report here:

https://gitlab.com/LineageOS/issues/android/-/issues/2176
[Moto G 2015 Original Android Development] IronTechmonkey:
Thank you very much for creating tickets and sharing the links! I'm planning to log the time issue via ADB through shutdown which seems to be where it messes up, as well as boot. I've not even gotten to testing Bluetooth yet but will test tomorrow and add details to your tickets. Thanks again.
[Moto G 2015 Original Android Development] althafvly:
We were working on a fix for osprey without effecting other devices..

It will be fixed from next build onwards
[Moto G 2015 Original Android Development] IronTechmonkey:
Groovy. I thought the issue or possible fix might be device-specific since something similar happened to Osprey early in LOS 14 or 15, Thanks.

I've reproduced this (or something close enough to go in same ticket) with Logitech K480 keyboard. To the point of previous descriptions it seems to be the toggling off/on of BT on the Android device that causes the issue. After that is done I can see the Keyboard in BT config, but cannot connect to it unless removed and re-paired. Once the keyboard is connected properly then; after toggling the keyboard off/on (with BT remaining enabled on Android) no re-pairing is required, and if the keyboard is disconnected within Android's native BT settings it reconnects immediately. Will try to test another BT device and then add to tickets.

[EDIT] There is this in the changelog regarrding BT: "Clean up duplicate uses-permission entries"

https://review.lineageos.org/c/Line..._opensource_packages_apps_Bluetooth/+/280801/

"duplicate uses-permission entries" is descriptively similar to what we've seen so I'll test BT and date in next build.
[Moto G 2015 Original Android Development] woheller:
That is exactly what I see. I can reconnect from the other device or from osprey as long as BT is not switched off on osprey. Once switched of re-pairing is needed.

Maybe the key is just stored in RAM and not in FLASH?
[Moto G 2015 Original Android Development] IronTechmonkey:
Could be, but then could be something else. I've not reviewed the tickets details (and would still not necessarily be able to identify the cause) I'm going see what happens in the next build, although it seems that there were issues with a batch of builds including Osprey in the latest run. IDK if LOS will add them at the end of the existing build queue or just wait until next cycle (next week),
[Moto G 2015 Original Android Development] kr428:
Folks; anyone successfully using GPS on this ROM (latest versions)? Been off for hiking this weekend in regions without network connectivity and failed to get a location in OpenStreetmaps; seems right now location only works using cell / WiFi data on my device. Any ideas how to fix this...?

Thanks in advance (and thanks too for keeping this device alive...)!

Kristian
[Moto G 2015 Original Android Development] woheller:
GPS works great on my osprey with latest version. Takes just a few seconds. I was also hiking in the moutains.

Nevertheless I think GPS is a little worse than on stock ROM.

I have 2 devices, one with Lineage and one on stock.

In GPS Test app the device with stock rom shows higher accuracy even though the reported SNR is worse.

Same for the 2 G4 Play I have (also one on stock rom).
[Moto G 2015 Original Android Development] kr428:
Thanks for the feedback. Hmmm, strange, installed GPS Test now just for the sake of it, and after toggling Location data once or twice it seems to work - and even rather quickly. Strange. Gonna keep an eye on that as soon as I'm back out somewhere. :)
[Moto G 2015 Original Android Development] IronTechmonkey:
Something's odd about "device only" GPS (in addition to the different way the options are presented in system settings). I cannot tell if it is a change in feature function or an issue.

The initial GPS took a very long time. Not the longest I've ever seen but close. I use the app "GPS fix" to get the fix. In this case I also installed the app "GPS status" and downloaded their helper file but the fix was attained offline by GPS fix (which never had network access).

Minor oddity along the way:

Some apps, including GPS fix and Google Maps, did not upon first run offer access to the permission to allow location access "all the time" but rather only when app was open. In system settings the apps could be set to allow location access all the time. The app GPS status prompted for that permission upon first run. All of these apps are exempt from battery optimization.

The Expected Behavior

The expected behavior based on previous LOS ROMs is:

- Enable device only GPS.

- Run GPS fix app, or tracking app.

- While GPS fix app is running in foreground or when minimized there is a GPS iconic in the upper right corner of the status bar.

- The aforementioned icon is the indicator that an app is using GPS.

The Anomaly

In the July 3 LOS 17 build a new behavior is that, after attaining a GPS fix and showing the icon in the upper right of status bar while the app is opened and the screen is on, anytime any of the apps is minimized a few seconds later the status icon disappears.

It's possible that the app is still accessing GPS location in the background but then of what purpose is that indicator icon. Also, a (hypothetical) partial inability of app to maintain the fix may be consistent with the reported difficulties attaining the fix.

Your hiking and walking tests are better indicators than the my static test but I'll install my tracking app of choice for cycling, Orux Maps, to see if it can hold the GPS and track while app is primary but minimized and screen is off.
[Moto G 2015 Original Android Development] woheller:
The GPS symbol is shown as long as the app uses GPS. GPS Test uses GPS only as long as it is in foreground. My navigation program Mapfactor uses GPS also when it is running in background, and the GPS symbol is shown as long as it is running.

GPS fix takes a while if no wifi or mobile data are available. Then A-GPS cannot work and all data have to be retrieved from the satellites, which takes a while. But I think that is normal. With network I have a fix in few seconds.

I think there is a GPS problem on G4 Play (harpia). There A-GPS does not seem to work and a fix takes very long. After that it works. After maybe an hour not being used it again takes very long to get a fix.
[Moto G 2015 Original Android Development] IronTechmonkey:
Yes. Exactly my point.

"GPS Fix" (Not GPS test) uses GPS as long as the back button is not used to leave the app. It can be minimized by home button or by switching to another app and it will continue to hit GPS and the icon will (did until now) persist in the status bar even if the app is minimized as described above.

Yep, and again to my point. None of the apps that I know to be able to use GPS in background seem to be doing so properly, The described behavior of the location icon disappearing when app is minimized occurs with: GPS-Fix, HereWeGo, Google Maps, Orux Map, Google My Tracks, GPS Status & Toolbox, and Mapfactor Navigator. The icon does not persist when it should.

I exclusively and always (quite truly always) use GPS (what was formerly called "Device Only" or before then just "GPS"). This device (in this ROM flash) has never connected to a cell tower or made a data based location fix (the GPS fix app would indicate such). I'm accustom to fairly long delays especially the first time after a ROM flash, and as I mentioned the initial FIX was within that range of expectation.

The issue is not the initial GPS fix but rather that (to paraphrase):

When in true GPS only mode and with no other fix having been made* the GPS/Location icon in the status bar and possibly GPS functionality is lost when apps are minimized (in background) but should still be keeping GPS active.

* Nota bene: This cannot be tested properly if the device has any data connection or if the device has recently gotten a data connection based location fix (formerly High Accuracy=Data+GPS, or Battery Saver=just data), or if those settings are enabled. Even without a data connection if those services are enabled they may place the status icon.

Of course in Android 10 Google has further buried the relevant settings for disabling non GPS location:

Settings > Location > Advanced > disable the following [Wifi and BT scanning, Emergency location service, Google accuracy location,]

When the next build comes out I'll test again.
[Moto G 2015 Original Android Development] woheller:
For Mapfactor Navigator I cannot confirm this.

On my device the GPS icon stays acive when Mapfactor is pushed in the backround.
[Moto G 2015 Original Android Development] IronTechmonkey:
That might be because the other services are enabled but is still useful to know for my next test.
[Moto G 2015 Original Android Development] Ska2:
Bug in LineageOS Camera

When i take pictures with LineageOS Camera, in settings i have selected to save to the SD card, normally the pictures should be saved in DCIM directory but the photos are saved to sd card/Android/data/org.lineageos.snap/files/ . When i access the LineageOS Gallery i dont find them because the location is not indexed by Gallery so the files are not showing there, so i have to use the Files Manager App to find them.
[Moto G 2015 Original Android Development] woheller:
Bluetooth works great now.

Thanks a lot!
[Moto G 2015 Original Android Development] DarkSJ1998:
Just flashed the latest build on my Moto G3 Turbo yesterday, feels so refreshing to see a 5 year old device Android 10 run successfully & that too Official LOS!

Kudos to you [MENTION=5881712]althafvly[/MENTION] for keeping this device alive!

I have a question, since I flashed the ROM, I had this setting turned on by default in which Google Assistant was always listening to my voice, even when screen was off. I was also getting that Microphone Icon on status bar that Google app was accessing it. I found that setting to be awesome & new, so I started finding a toggle for it but somehow I've disabled it IDK how. I had never seen it on my OP6T running OOS based on Android 10.

Can anyone please guide me how to enable it again on my merlin?
[Moto G 2015 Original Android Development] contructor0:
Same here. Clean wiped and installed lineage-17.1-20200717-nightly-osprey-signed.zip (previously lineage 14). Lineage camera app and the Play Store Moto Camera app both do not work. Open Camera works.
[Moto G 2015 Original Android Development] IronTechmonkey:
[MENTION=5881712]althafvly[/MENTION], thanks for working on this.

Although the time is now correct, upon reboot until synchronization, the year and month are still incorrect - always April 20, 2024 after reboot throughout the several days I've been running this build.

July 17 Osprey LOS, July 14 Open Gapps, Magisk (just SU, no modules).

Side note regarding the incorrect date: As written in conventional US formats, 4/20/2024, and stripped of formatting marks, 4202024 (or 4/20/24 and 42024) this date seems like a practical joke: It is a numerical palindrome (same forwards and backwards) which says, in effect, "420 to 420" or "420 420". If so, I do find that humorous but in any event it's doing bad things to backups and other date critical things.
[Moto G 2015 Original Android Development] IronTechmonkey:
GPS only status bar indicator or background permission issue.

Thanks for mentioning Navigator, which turns out to be an example of proper function regarding location permissions when compared to other apps which may not be properly using the new permissions. Before I get into the details of that, another question for you: Regardless of whether or not you were using a GPS only or if the app was in foreground or background, were there any periods of time where you were tracking with the screen off?

As to the observations about location permissions:

Where there was formerly one GPS permission per app, now in LOS17 there are now several permissions which determine access in background for: "location", "precise location", and" approximate location".

App > properties > permissions > menu >All permissions.

Those may or may not be the same as the permissions requested on first app run but they don't use the same terminology. In addition, for some apps the permission for background use is not offered upon first run but can be changed after installation, while for other apps such as Navigator that permission is requested upon first run. The fact that precise location is allowed only in the foreground for all the apps tested including those that do hold onto GPS in the background and those that don't, may be an indication that LOS is not properly handling the permissions (in addition to the need for the apps themselves to be tweaked). In any event this is not likely to bee device specific so when I have a chance I'll create a gitlab ticket. Thanks again for taking a look in Navigator.
[Moto G 2015 Original Android Development] Lperes10:
No sound

I had installed on my moto g3 ( osprey) the 17.1 Lineage , but now i have no sound , just vibrate,

Please need help. ( Clean install)
[Moto G 2015 Original Android Development] IronTechmonkey:
Nice catch, there's clearly some bug here but it's not necessarily the location itself.

As you mention, in LOS17 Osprey, that save location is not being properly scanned by the gallery, nor is it properly scanned by the camera app (or perhaps there is an internal permissions issue). Even the preview of photo in the camera app won't open the file.

For comparison, in LOS16 on Moto Z photos on external SD are also saved to that location, but in that case they appear in the gallery and can be accessed from the preview in the camera app.

The use of that folder as save location might actually be a new normal and part of Google's attempt to keep those images in a more secure location in storage. So the underlying issue is that in LOS17 Osprey that location is not accessible by gallery or camera preview. IDK if this is device specific or universal but it's definitely worth following up with bug reports and logs here or at lineage OS gitlab if the devs do not already know about it.

Does anyone know if this same thing occurs on other LOS 17 devices?
[Moto G 2015 Original Android Development] sraman09:
A wonderful and stable ROM. Thanks for keeping the flag flying. I just ran into a peculiar problem. Before installing the ROM, I had moved my pictures and Videos to SD card. After installing the ROM & Whatsapp when I tried to attach the video from SD card, I get an error "unable to send, restart the device". This does not happen for pictures though and for any media on the phone memory. Any thoughts?. Thanks in advance

update : Video taken inside whatsapp is accepted, while all other videos taken using camera app both open as well as moto are not being sent.

Regards

Subbaraman
[Moto G 2015 Original Android Development] woheller:
Yes, I am using Navigator also with screen off and it works well.
[Moto G 2015 Original Android Development] fahadaslam2000:
I too believe there is some problem with GPS on this ROM as of recently. While I don't use this phone primarily for any other GPS related activity like using maps, I use it for using my Operator's app that facilitates receiving Landline Calls in HD-Voice on a Mobile Phone over the WiFi network of their Fibre broadband (App in case: JioCall by Reliance Jio).

The app now doesn't connect to wifi, despite wifi working for everything else on phone, and instead throws an error: *Enable Location services first to connect to this network.*

While this is not a big issue because I can still receive calls on the Landline unit itself. I noticed it, so I thought I should bring this error to light

---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------

I have had this issue once on this device with this ROM while it was in the Unofficial Channel. Couldn't attach videos stored on SD Card from WhatsApp.

What worked though was sharing the video to WhatsApp from Gallery itself.
[Moto G 2015 Original Android Development] smiffyma:
Hi – Can anyone comment on how this Rom performs on the 1GB osprey model (xt1541)?

I’m current running Official LineageOS 14.1 and wonder if it will be any faster / slower?

Thanks for any feedback.
[Moto G 2015 Original Android Development] freshmeadow1@gmail.com:
I find that this ROM actually runs faster on my 1gb XT1540 (Canadian version). Also, it was much easier to get mobile data working on this ROM. Just my experience, having used both.
[Moto G 2015 Original Android Development] IronTechmonkey:
FYI General usage and product review questions which don't inform development would be more appropriately placed in the general section. If you want product reviews then find SD_Shadow's Moto G3 FAQ thread. Don't be put off by the phrase "Noob friendly". Those threads are indeed friendly to inexperienced users but also have some highly knowledgeable input.

------------

Since we are already here let's turn this into something focused on development (which also happens to answer your question in part, but only coincidentally ;) ).

On 1GB Osprey devices with a moderate persistent load in memory (e.g. in my case; Afwall firewall, Tasker, LMT) the device can have serious app killing issue particularly when using the native LOS camera. Although all 1GB devices will be a bit starved for memory this issue is significantly worse on Osprey than other even older 1GB devices such as Moto G 4g Peregrine and even the ancient Moto E Otus.

As it turned out LOS 14 Osprey had disproportionately high minfree (aka LMK or low memory killer) value for one particular category of app. That alone was unlikely to be the cause of the issue but changing that minfree value did somewhat mitigate the issue, as did using an alternate camera. [IMO the native LOS camera has not been appropriate for 1GB LOS devices for several Android versions, but that's another story]

I reported on this extensively in LOS 14 and device contributor squid2 checked it out but there was nowhere to go with it. When testing the recently reported bug regarding save location of photos on external SD I noticed the same app killing behavior occurring in LOS 17. This is probably not worth chasing anymore but I'd be glad to share information about it in a Q&A thread.
[Moto G 2015 Original Android Development] coolizard:
First of all, thank you very much everyone envolved in keeping this device alive. After 5 years, I still don't need a new smartphone.

I recently installed this ROM (nightly 20200724) and I'm experiencing the same Whatsapp issue about video upload already reported: "Failed to process video, try again later. If you keep seing this message, restart your phone".

This reminds me the same problem in LineageOS 14.1 (https://xdaforums.com/2015-moto-g/o...ogenmod-14-t3466246/post77118310#post77118310) that [MENTION=6485916]squid2[/MENTION] fixed in that version.

About the camera, if I select the sd card as storage for photos, they won't appear in gallery. They are saved in <sdcard>/Android/data/org.lineageos.snap/files. I think this related with the fact that the directory Android/data has a .nomedia file, and then gallery will skip this directory when searching for media. Selecting the internal storage, this issue doesn't exist.
[Moto G 2015 Original Android Development] IronTechmonkey:
Confirming. At first it seemed like a WhatsApp error (and I was probably squawking to that effect and then squid2 fixed it in LOS 14 firmware as you reference.

D'oh, I forgot there was a .nomedia file there while kicking this around a few days ago. I think you're right. Also, if deleted that file will be replaced by the system so there is another factor, perhaps related to stricter Google requirement put on system locations and which things must be in system locations when on external SD.

I.e. Even when set to see hidden folders; current gallery apps (native LOS Gallery and Simple Gallery Pro) cannot see that folder. The only gallery type app other than a file manager with which that folder is visible is an old version of QuickPic which would not know about that new Google requirement.

The behavior of the internal save location is also consistent with this. Since internal storage cannot be physically removed the DCIM directory is considered secure even though it is not in a system folder. On the external SD the DCIM folder is not secure so they put it in a system location.

At least, that's the best hypothesis I can come up with. In any event nice catch about the .nomedia file. Either way there's a bug here.
[Moto G 2015 Original Android Development] sraman09:
One more small issue I have observed is, During an incoming call when it is ringing it says "Incoming call via ___" and then the number. The SIM related to that call is blank. Once you answer that call, the SIM No is displayed. I know these are minor issues, still reporting it. Other issues faced are

1. When reading stories from Google now, the phone restarted twice, once while refreshing it.

2. Installed moto camera app an it is very unstable. Crashed twice.

Other than these minor issues, the ROM is fantastic. The software is lag free and so refreshing for a 5 year old phone. Thank you guys, We are enjoying while you work hard. We owe a lot to you.

Thank you
[Moto G 2015 Original Android Development] woheller:
Seem this is considered a feature and not a bug.

See Nolen Johnson's comments in https://gitlab.com/LineageOS/issues/android/-/issues/443

"I've been corrected internally, apparently it is stored in Snaps private storage, and can't be fixed correctly, as it is intended behavior and therefore won't be fixed"
[Moto G 2015 Original Android Development] IronTechmonkey:
Nice digging. The move from DCIM to the files folder within the system directories is indeed not a bug, which was to the point of my description regarding Google's requirements. That being said, that ticket is only speaking to the save location having been moved from DCIM, (which we have an explanation for) and does not speak sufficiently to the problems accessing the location. Additionally, that report was filed from LOS 16 in 2019, but in LOS 16 several months newer than the one in that ticket the photos are saved to the new system location on external SD and the gallery and camera app preview can see that location.

So...

The inability of the native gallery or even the camera app preview to view pictures that were just taken is simply absurd, AND, there's evidence that this was all working properly since that ticket.

I think it's worth pushing as a new ticket specifically for the inability to see that location from the camera preview or gallery. I'll play with that next chance I get, maybe in a build or two. Thanks again for the head start finding relevant tickets.