yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] Siddk007:
My dad is using osprey. I had earlier installed LOS 14.1. Today when I checked the xda thread, was surprised to see Official LOS 17.1 support!! Immediately backuped everything and flashed 26th build and pico gapps. Its like the phone is breathing a new life. Volte also works. So far seems stable. Big thanks to you man [MENTION=5881712]althafvly[/MENTION]. Keep up the good work and hope to see support for osprey for a long time. Cheers
[Moto G 2015 Original Android Development] Danilfilatov:
Thanks for providing my old device with android 10! No, really - thanks.

Now, a question - did you implement a way to turn off moto actions? I am talking about turning flashlight and camera with specific device movements. I reckon in older lineages switches were in settings, now i dont see them. I also cant download moto actions from play store - not suitable for my device lol. maybe you have a link to stock app somewhere?

Side note - on status bar quick advanced settings screen of say wifi or do not distrub mode, top padding seems to be off - smaller than others. i attached two screenshots
[Moto G 2015 Original Android Development] fahadaslam2000:
1. Go to Settings - System - Gestures (The bottom most one,not the one on top). Moto Actions are under there.

2. The padding difference may be because of the screen scaling settings. I use smallest width as 480 dp and I see proper padding. (Available under Settings- Developer Options- Smallest Width- 480 dp. You can try different pixel densities to see what fits your needs)
[Moto G 2015 Original Android Development] 4xxxxL:
Well after a fresh install phone app doesn't display anything when receiving call just a blank screen :/
[Moto G 2015 Original Android Development] Danilfilatov:
There they were! Now i won't accidentally turn on camera takcing phone out of pocket and flashlight running with it in my hand.

Not a big deal, but here are screenshots with 360 480 and 720p.

Didn't know i can turn my phone into a tablet
[Moto G 2015 Original Android Development] fahadaslam2000:
Oh yes, I use the smallest width settings to get even smaller fonts than provided under display settings even on my Nokia. I like a little smaller text. Fits more on screen.

But I see the padding is still a bit off for you. I don't think I know how to fix that.

I use the dark theme. So I thought may be it is so in light theme. But it's the correct way for me even in light theme.

May be you can switch to Dark Theme and not take notice of the padding.
[Moto G 2015 Original Android Development] Danilfilatov:
hehe, no

nevermind then

and thanks
[Moto G 2015 Original Android Development] Loopstoop:
I'm not sure if this is particular to my configuration (no sim), but on my phone every time it restarts the date resets to 2025. This happens both using Network Provided Time and manually setting the date/time.
[Moto G 2015 Original Android Development] woheller:
I have the same problem on my osprey when the SIM is removed. Date is somewhere in the future. When I set date manually it is reset after next reboot.

When connected to WIFI time is set automatically after a while but also lost after reboot.

With SIM I also see the problem but only for a short moment until the phone is logged into the network.
[Moto G 2015 Original Android Development] IronTechmonkey:
It's worth knowing what was the latest version of stock that had been installed and in some cases it is hugely significant. Try to figure it out if you can. My Osprey was updated to Marshmallow (IIRC) stock before custom ROMs were installed and it was running LOS 14 Nougat when LOS 17 was flashed, and so far so good, and I should be OK but would also like to know the reasons for that requirement.

In any event, I was delighted to find the new batch of devices including this one that were added to the LOS 17 device roster. Finally a non AB device to flash and test!.Thanks [MENTION=5881712]althafvly[/MENTION] for working on it,,, and nice to see [MENTION=6485916]squid2[/MENTION] still lurking around.:)

[EDIT] And also thanks for this answer: https://xdaforums.com/showpost.php?p=82846723&postcount=211.

and this one https://xdaforums.com/showpost.php?p=82851547&postcount=218

[MENTION=5299597]kr428[/MENTION], in the linked post there is a brief explanation about the need for the latest stock firmware and the difference between stock and custom. You can find more posts about that by searching thread for "marshmallow" which is how I found that one. If you are getting all functionality including radio, cell phone modes and bt you should be OK.
[Moto G 2015 Original Android Development] IronTechmonkey:
Same symptom here. I'm testing on an Osprey with no SIM. When it is rebooted with Wifi disabled then after reboot the date and time are March 21, 2024, Any backups made with TWRP are dated 2024 as well but only when this ROM is installed. With LOS 14 on the device this does not occur upon reboots or when making TWRP backups of that build. I'm accustomed to seeing small differences of a few hours between the real time and the time in TWRP after a reboot but this is extreme. Once in the past one of these minor differences was fixed but I don't remember if the fix was in the ROM or in TWRP.

With the aforementioned in mind: I'm using the official Osprey TWRP 3.4.0 but wonder if it would make any difference to use using the older custom version of TWRP made by althafvly and available here. I would think not but worth a thought. Meanwhile, this might be worth checking the changelogs and the LOS git problem report system.

Possibly related to this ticket: https://gitlab.com/LineageOS/issues/android/-/issues/1772
[Moto G 2015 Original Android Development] justabegginer:
Hello, last night I installed LineageOS 17.1 in my 3rd gen Moto G following the instructions from the LineageOS webpage.

I probably made a mistake somewhere, but I cannot access my service provider's data connection.

Wifi works fine, but I cannot get my mobile data connection to work. I am trying to configure the APN manually, but nothing happens after the configuration (I tried several times, with reboots and airplane mode toggles here and there...).

Am I the only one with this problem?
[Moto G 2015 Original Android Development] stukdev:
Just installed latest weekly, automatic mode failed the first time, the second works. But the now the camera don't work with stock app, only opencamera works.
[Moto G 2015 Original Android Development] DocLM:
No, I tried this rom today and cannot get my carrier data to work.

I have an italian MNVO operator (CoopVoce) based TIM carrier.

Tried to delete default APN and set-up with my carrier settings but it did not work.

The same settings on Moto G5 plus works fine
[Moto G 2015 Original Android Development] botoid:
Same. Clean installed 2020.07.03 build after discovering this wonderfull thread (big thanks to [MENTION=5881712]althafvly[/MENTION] . No mobile data is working. Is there any build for which mobile data was working?

Also not related I think - since I also have the issue on moto e 2015 - manually choosing the cell provider is not possible. Only automatic works.

Cheers
[Moto G 2015 Original Android Development] althafvly:
Mobiledata is working fine in my carrier (JioVoLTE-India). It maybe carrier specific issue, provide logs if possible
[Moto G 2015 Original Android Development] botoid:
Hi there. Thanks for the prompt reply.

Not too sure which log to provide for such issue.

However note that I can't get mobile data to work for 3 different european providers:

* Sunrise (switzerland)

* Aldi (switzerland)

* orange (france)

Tried to play with APN settings and toggle airplane mode and other 4g settings to no success. I can place phone calls mot no mobile data.

Please note that above sim cards, mobile data is working on Lineage 17.1 (which you provided as well) Moto e 2015 (surnia).

Thanks a lot for your work. Greatly appreciated.
[Moto G 2015 Original Android Development] Gordster:
Hi

I thought I'd give this 'official' lineageos rom a try on my Moto G3 2015 (1gb RAM version). Installed fine and seemed to run well BUT I have had several spontaneous reboots for no apparent reason. No particular app running. Nothing special. It just rebooted. Has anybody else had this problem?
[Moto G 2015 Original Android Development] IronTechmonkey:
I'm running clean flash of previous build (preparing to flash this week's) with no reboots or functional bugs so far other than the inevitable feature tweaks and other minor issues. In fact quite smoooth for an early build on an old device. If this is your first time coming from another ROM you may not have taken all the recommends steps,,, but before anything...

Had you updated stock ROM to Marshmallow before flashing this ROM?

What version of TWRP?

No custom kernals or other modifications such as xposed (until issues are resolved) including remnants of substratum, viper audio and suff like that?

Did you clean flash; Meaning:Advanced wipe clear dalvik & data & system & cache, factory reset, flash ROM and gapps in same TWRP or (other recovery) session?
[Moto G 2015 Original Android Development] Gordster:
Thanks for responding. Yes I was on Marshmallow to begin with but have flashed several other custom roms before trying this official one. They all worked well. I never had this reboot problem before with other custom roms until coming to the 07/03/2020 version of this Lineage rom. And yes I did a clean flash, did advanced wipe to clear dalvik, data, system and cache. Nothing custom and no modifications. I'm using TWRP 3.3.1-0. The reboot has just occurred randomly 3 times in the last couple of hours with the phone in the standby mode. Other than the reboot issue, the rom seems to be working fine. Any other suggestions.

Thanks

Gord
[Moto G 2015 Original Android Development] IronTechmonkey:
For what this is worth

Single SIM, 1GB osprey XT1540

lineage-17.1-20200703-nightly-osprey-signed. with open_gapps-arm-10.0-pico-20200630.zip and Magisk 20.4

US T-mobile prepaid

- LTE only: Data connection OK and with good data transfer.

- WCDMA only (H+): Data connection OK with good data transfer.

- GSM only (Edge): Data connection OK but slow and intermittent transfer. This is normal here.

- By a stroke of luck an incoming call arrived just as I was testing LTE mobile data. This became a test of the expected network switch from LTE to WCDMA (H+) during the call and back to LTE after the call.

= All good.

It's nice to be testing something current again instead of fixing something old. Thanks again!
[Moto G 2015 Original Android Development] IronTechmonkey:
Gapps package as described in this thread's OPs?

If so, then you might want to assemble a "proper" bug report including a description of the steps required to reproduce the issue and a log taken while the issue was reproduced. For something such as reboots which occur "randomly" (not really random, just in a way we cannot predict) those things may not be easy to do but there are specific log files on left on the device which may inform. I don't recall those files but you should be able to find their names and location by searching. In fact since this thread is focused on LOS issues more than the process of reporting them I would suggest doing some external review about logging "spontaneous reboots" and logging/bug reporting in general.

Then...With details that logs assembled you could file an official LOS bug report: https://gitlab.com/LineageOS/issues/android, or kick it around here first.
[Moto G 2015 Original Android Development] asdfuc:
USB tethering does not work. I am using it with my Mikrotik. Two other stock devices work fine.
[Moto G 2015 Original Android Development] IronTechmonkey:
In lineage-17.1-20200703-nightly-osprey-signed USB tethering is working fine for me, and was used to submit this post from a Dell laptop computer connected only to Osprey by USB tether connection.

If you mean 2 stock devices can receive the USB connection from the same device, I cant think of why LOS 17 would not work if the the physical connections are good. IDK if problems with the data connection on in LOS 17 could be the cause but, consider filling a bug report (as described in recent posts and elsewhere) with details that will help devs.

[EDIT] At first I missed the mention of the connecting device and have revised my post accordingly.
[Moto G 2015 Original Android Development] botoid:
Just to add an information my phone is a xt1541.

If [MENTION=7687750]DocLM[/MENTION] and [MENTION=10930529]justabegginer[/MENTION] could confirm the phone model to check if that could be the cause?
[Moto G 2015 Original Android Development] DocLM:
Of course, I have a XT1541 unit.

I don't know what log can be useful but if someone can point me in the right direction I'm happy to help.
[Moto G 2015 Original Android Development] IronTechmonkey:
You can capture logcats with an on device app such as matlog (available at playstore https://play.google.com/store/apps/details?id=com.pluscubed.matlog&hl=en_US) or on a computer via ADB as described at the Lineage OS wiki https://wiki.lineageos.org/logcat.html.

Try to log a period of time representative of the problem, for instance when the device is attempting to resolve the SIM. For an issue like this more details about the SIMs and service providers might help.
[Moto G 2015 Original Android Development] DocLM:
Tried to log when I toggle data on and off.

I filtered the logs with IMS and RIL keywords.

EDIT: Reuploaded logs
[Moto G 2015 Original Android Development] botoid:
I finally broke one of the sim contact pin after switching sim cards...so I am out of the game for moto g. Howhever I will be using your superb work on moto e 2nd gen.

Ironically, before breaking the contact pin I have been able to make data work after a fourth clean install. I think the difference is that sim card was already inserted during install and initial setup.

I noticed that the setup this time started with german language instead of English US.

I also changed the APN bearer setting to LTE so I don't really know what made it work in the end.
[Moto G 2015 Original Android Development] IronTechmonkey:
UI glitch in Theme name panel.

UI glitch in theme creation:

The text in the theme name field is not visible. Tapping recent induces repositioning placement of screen elements so text field is visible.

To reproduce

- Settings > Display > Styles & wallpapers > Custom (any) > (at Font panel) Next > (at Icon panel) Next > (at Color panel) Next > (at Style name panel) > tap text field.

= Not enough of the text in the field is visible to know what is entered there.

Attached ThemeGlitch1

Image pending repair of XDA site issues

After inducing the bad condition as described above, and invoking recents and returning to the theme name panel; then the preview area (and everything else) is moved up making room for the text field and the keyboard.

Attached ThemeGlitch2

Image pending repair of XDA site issues

I have a log spanning the walk-through described above as described above.

[MENTION=5881712]althafvly[/MENTION], Since this is most likely universal rather than device specific I can create an official ticket at gitlab if need be.

Note: At Normal system font size setting the text field is only partially obscured but the same repositioning occurs after the recents button is pressed.

In any event, native device features should accommodate any of the native Font size settings.
[Moto G 2015 Original Android Development] lmeu:
Mobile data isn't working

Today I installed LO 17.1 (2020-07-03) on my osprey. Of course, before the installation, I installed stock 6.0.1 as described in the prerequisites. Partitions were also wiped before both the 6.0.1 and 17.1 installation.

The showstopper for me is that mobile data doesn't work. I see 4G in the status bar, but together with an "X", and mobile data connections fail. The APN settings are the same as I used on 14.1.

The "Preferred Network Type" setting shows the default (GSM/WCDMA/LTE). The list of this settings contains many other abbreviations I've never heard, but even if I set it to only "LTE", it doesn't work.

I use the Deutsche Telekom network with a Klarmobil contract.

Is this a known bug? I saw that several other people have issues with mobile data after installing this official 17.1 ROM. Or is there a way to get this work by some config changes?
[Moto G 2015 Original Android Development] IronTechmonkey:
That does sound similar to some recent reports. See the last few thread pages, posts created since the last build. One person provided a log and another may (or may not indicate issue is regional (Europe), another possibly associated with a specific Osprey model, but you can make more sense of those posts than I can because mobile data is working for me. There is a post by me describing a good condition under different circumstances. Check 'em out (the relevant posts).

[EDIT] D'ohI completely missed that you saw those other posts. Still, since the developer has already chimed in and knows about this but may not have seen a log for it, it might be helpful to have another log.
[Moto G 2015 Original Android Development] althafvly:
Its lineage issue, reporting this to them will be helpful
[Moto G 2015 Original Android Development] IronTechmonkey:
If I was sort of expecting that but wanted to check with you first. Thank you very much for the reply. I'll create a ticket at LOS gitlab.+

[EDIT] I'll do the same with the some logs for the issue of 2024 date after reboot, although IIRC from LOS 14 this might have been device specific and IDK if fix was in ROM or TWRP, squid2 might know. Anyhow, I'll log shutdown and boot through manual data connection and subsequent time sync via adb and create a ticket (or add to a similar ticket there),
[Moto G 2015 Original Android Development] lmeu:
I created a log file, but I don't see any option how to attach it to this post. Therefore, I uploaded it to a paste service:

https://cpaste.org/?ddcbf5f7567f0046#63U8viNMqHtbDjWFUeMqndKp4pD3hKyxWBHeACW5nnrz

Capturing was started when phone was in flight mode and then the flight mode was turned off.

Please let me know if I can provide more details or logs to get this fixed.
[Moto G 2015 Original Android Development] IronTechmonkey:
IIRC, to attach files you must have a certain number of posts (maybe 10). As to the issue maybe dev and users experiencing issue can narrow down the specific cause with the provided information.
[Moto G 2015 Original Android Development] okam1000:
Correction: Bluetooth is NOT working OK for me in osprey, even with the last firmware version (July 3rd). After rebooting the terminal it does not connect to my car Bluetooth set. It does connect however to another Bluetooth device (Oura Ring). However this last device does not require a Bluetooth PIN, maybe this is the reason.
[Moto G 2015 Original Android Development] 0anas0:
Help

Can't download apps from play store. No Sim, WiFi. After flashing I downloaded some apps and now I can't. July 3 build, clean install
[Moto G 2015 Original Android Development] knpk13:
This happened to me on a different device as well, so I think it might be a gapps bug.
[Moto G 2015 Original Android Development] IronTechmonkey:
FWIW I flashed the LOS 17 Osprey July 30 build with open gapps Pico June 30 (which was the newest open gapps available when I flashed) and the ROM has been running fine for several days. If people want to figure out what's broken they could start sharing the details about what gapps package they use. If they want to work around it they could try the June 30th or earlier gapps package and wait until newer gaps packages are sorted out.
[Moto G 2015 Original Android Development] knpk13:
I already reported it in the gapps thread along with the "mandatory voice setup" issue a few months ago, they're still working on it apparently (I don't think my logs were very helpful). I worked around it by clean flashing with a different gapps package and not logging into my google account during the initial setup (I added it later).
[Moto G 2015 Original Android Development] IronTechmonkey:
Thanks for the info here and the work there. IMO it's a good idea to do the account that way in general. I have always created the account after completing setup, placing all my native device settings and confirming basic operations - primarily to get at the native Google settings before account creation. I disable all forms of sync to Google which puts me a step farther from experiencing these sorts of problems but does not serve as a workaround for other people. Some folks actually install older gaps packages intentionally and allow the device to update those components post flash in order to avoid problems that come with a particular gapps package.

BTW, which was the gapps package that had problems for you, and which was the different one you used to work around the issue? Was it the same type of package from a different date or a different type of package?

Thanks again.

[EDIT] It might also be worth noting that Osprey builds are setting date to 2024 upon shutdown and restart until online sync in OS. This does have a negative impact on some apps but IDK if it impacts the relationship between ROM, gapps and account.
[Moto G 2015 Original Android Development] Gordster:
For those looking for a good stable android 10 custom rom, may I suggest trying havoc v3.7. I use this one and found that it works very well on my Moto g3 2015 with essentially no problems, and is very customizable. Although it is not an official release, it is kept right up to date. The link is https://chil360.github.io/index.html
[Moto G 2015 Original Android Development] IronTechmonkey:
It is inappropriate to advertise a different ROM in the development thread for another ROM. Please feel free to submit bug reports for or discus LOS 17 Osprey here as that is the topic of this thread. Otherwise, a Q&A thread for Moto G3 would be a more appropriate place to advertise a different ROM that you recommend.

In fact, here is one created by someone (sd_shadow) who has created other good Moto device Q&A threads.

https://xdaforums.com/2015-moto-g/help/help-thread-moto-g-2015-3rd-gen-noob-t3387661/post67059730
[Moto G 2015 Original Android Development] Gordster:
Sorry, I'll post this in the other thread.
[Moto G 2015 Original Android Development] IronTechmonkey:
I should disclaim that I have no status to insist and that I'm just being a nag, but thank you. I'll be following you there because I'm interested.
[Moto G 2015 Original Android Development] knpk13:
https://xdaforums.com/android/software/pa-gapps-continuation-t3098071/post82702117

This has the details, and if you search the thread you'll find my other posts (one of them is about the moto g) and other people's reports. Nezorflame replied this week. I'm thinking my logs may not have been helpful since I took them with matlog instead of adb, and a dev once told me that the app doesn't record PPID's.

https://xdaforums.com/android/software/pa-gapps-continuation-t3098071/post82996477

I clean flashed a newer gapps package, same variant, and that fixed the app installation issue for me (which I only experienced once on one device, so I cannot help much with that). I can speak more about the "voice setup" issue since it has been happening consistently across 3 devices with multiple nano gapps builds for months. Since the pico build doesn't have the voice detection stuff, perhaps using that is another workaround, but I haven't tried it.
[Moto G 2015 Original Android Development] 0anas0:
Mine just started working again. Did nothing.
[Moto G 2015 Original Android Development] Gordster:
I just posted here first because it looks like most people are having lots of problems with the official lineageos rom. Perhaps as time goes by, it will improve.

I don't think the link that you gave me is quite appropriate either as it seems to be just Q&A and troubleshooting. I found another thread that I think is better.

https://xdaforums.com/2015-moto-g/general/favourite-g3-osprey-2015-roms-android-t4081375.