yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] Viva La Android R.I.P.:
Okay. Then your model is definitely compatible with this LOS v17.0 ROM.

---------- Post added at 08:14 PM ---------- Previous post was at 08:09 PM ----------

Update: here is a link to the Osprey device specific Moto Camera Mod. https://xdaforums.com/2015-moto-g/themes-apps/mod-rom-t3983007
[Moto G 2015 Original Android Development] Kobusyeshead:
The camera app didn't work for me. I now installed open camera

Verstuurd vanaf mijn MotoG3 met Tapatalk
[Moto G 2015 Original Android Development] lonkar:
Yes althaf did a great work this ROM is real smooth but i found out AOSIP 10.0 on https://telegram.dog/iammotog3/759

You can check it these guys frequently update these channels
[Moto G 2015 Original Android Development] Viva La Android R.I.P.:
Thank you [MENTION=9050141]lonkar[/MENTION]. I wasn't even aware that an AOSP Android 10 build was available for the Osprey. Very kind of you to mention.
[Moto G 2015 Original Android Development] lokeshyadav007:
Hey Guy's I have flashed lineages 10 by chil360, build no lineage_osprey-userdebug 10 QP1A.191005.007 eng.kyle.20191019.123326 test-keys

I am facing some issues,

1. GPS not working, not able to locate device location

2. Digital wellbeing is crashing

Additionally I want to know ,

1. is there any way to customize?

2. Is there possibility of face unlock?
[Moto G 2015 Original Android Development] lonkar:
There are 3 builds available for now

1. AOSiP (Most stable)

2. Lineage (Maybe some less stable than aosip)

3. AOSP (TEST BUILD SO NO FURTHER UPDATES)

I would like to tell that most of the major bugs are already solved by chil even GPS, camcorder and volte is working in recent builds

Not so sure but new build will be landing soon (a stalker stated that chil is going paranoid ?)
[Moto G 2015 Original Android Development] Kobusyeshead:
ROM Name : [Alpha] Lineage Os 17.0

Android version : 10.0

Build By : chil360

Security Patch : October 2019

Gapps : Not included.

Bugs : Stable release .. No major bugs

Changelog :

- Wellbeing fix

- Disable Codec2 (Youtube fix - Credit to [MENTION=8714092]DanGLES3[/MENTION])

- Additional ims/telephony commits

Mega Upload Link : https://megaupload.is/Vad8o790n9

∆∆ For those running last week's build, this build should be available as an OTA update through the Lineage Updater in settings.

~~~~~~~~~~~~~~~~~~~~~~~~

Join & Support - [MENTION=1239934]iammo[/MENTION]tog3

~~~~~~~~~~~~~~~~~~~~~~~~

Verstuurd vanaf mijn MotoG3 met Tapatalk

[
[Moto G 2015 Original Android Development] akhiltj114:
i can't update Android System WebView from play store..

---------- Post added at 02:43 PM ---------- Previous post was at 02:42 PM ----------

GPS still not working
[Moto G 2015 Original Android Development] Kobusyeshead:
GPS works fine for me??

Verstuurd vanaf mijn MotoG3 met Tapatalk
[Moto G 2015 Original Android Development] rockersz:
Dirty flashed this build over althafvly's build and voila it solves all the bugs, one small bug I found is battery percentage not showing until I pull down the notification bar, other major and small bugs fixed
[Moto G 2015 Original Android Development] althafvly:
Then its probably your device specific issue. G4 play and moto g3 shares same hardware and blobs. So it should be affected both devices. I didn't even find this issue in my osprey. And its already 5 years old.. so can't expect more.
[Moto G 2015 Original Android Development] woheller:
I have 2 Ospreys, one with 8GB and one with 16GB. Both show this problem...

---------- Post added at 07:27 AM ---------- Previous post was at 07:18 AM ----------

I think 3 days is quite good. I usually get 2 days with maybe 2h screen time. But that is at least as good as on stock ROM. It only goes down drastically if I use hotspot and do not activate Wifi afterwards.

It also strongly depends on position. In an area with bad reception consumption strongly increases, especially when 4G is requested. I set my phone to 2G/3G and manually switch to 4G if needed.
[Moto G 2015 Original Android Development] Gitah.:
Before updating to 17.1 from a very old build of 14.1, I (I'm not the one using the phone but still) was getting more than 3 hours of screen time and definitely more than 3 days on idle.

I just noticed they're still updating the security patches on 14.1 so maybe I'll try that one if the issue is just inherent power consumption of a much newer OS.
[Moto G 2015 Original Android Development] lmeu:
Great ROM, thanks.

The only issues I have (also with the latest lineage-17.1-20201016) are:

* Unexpected reboots. The device lies on the table and suddenly it's vibrating for a short moment (that's what it does when you turn it on or reboot). If you check the display, then you see that the phone is booting. The most interesting fact is that, after the reboot, I'm not prompted for the SIM's PIN. It seems I'm not the only one with this bug. Someone else mentioned this problem earlier in this thread.

* Calender (the one shipped with LO 17.1) notification sound is played every 10 minutes if you don't swipe away a notification. It's a local calendar (not sync'ed to Google, etc.). If a calendar notification pops up, Android play a sound. If you don't swipe away the notification, then this sound is played again and again every 10 minutes, what is annoying.

One related question: Yesterday TWRP 3.4.0-1 for Osprey was released. Does anyone know why the size is 14.9 MB, while all other previous releases were only ~7.3 MB?

I tried it and it seems to work, but I wonder why the size has doubled for this bug fix release. Unfortunately, there are no device-specific release notes.
[Moto G 2015 Original Android Development] woheller:
I had such reboots where I was not asked for a pin in the past. But that was several months ago. No more such problems since then. These usually ocurred in areas with very bad mobile signal strengh.

Regaring calender: I also have a local calender and I actually like getting reminded if I don't swipe it away...
[Moto G 2015 Original Android Development] lmeu:
I mostly discovered this problem when I sit on my desk at home and the phone lies next to me. In this location, the mobile signal (4G) is almost at maximum. Often the phone wasn't touched for hours. I never had this issue when I actively used the phone. But since the problem occurs just 0-2 times per day, it's not frequent enough to say that it only happens if it's not actively used.

I expect only one audio notification and not every 10 minutes. It's annoying if I sit on the sofa in the evening and my phone plays the notifiation sound every 10 minutes until I stand up, walk to the kitchen table, and swipe away the "waste collection" reminder for the next day (this is just one example :)). I also see no option to disable this behavior (bug). In the past, the notification was shown and the sound was played only once.
[Moto G 2015 Original Android Development] Gordster:
I've had this unexpected reboot on it's own for several months now on both of my osprey phones. It can happen when the phone is just sitting on my desk or it can happen when I'm using the phone on wifi or it has happened in the middle of a phone call.......bang the phone just reboots. Never know when this will happen but it is very annoying. Glad to see that I'm not the only person with this issue. I've tried a different ROM (can't mention which one in this forum) and it never happened. There must be a bug somewhere in LineageOS.
[Moto G 2015 Original Android Development] woheller:
In August I wrote a bug report regarding that subject.

https://gitlab.com/LineageOS/issues/android/-/issues/2351

It was closed by [MENTION=5881712]althafvly[/MENTION] and since then I did not have such reboots anymore. Don't know if there were any changes made.

After such reboots I experienced higher power consumtion until a full reboot. Do you see that as well?
[Moto G 2015 Original Android Development] vjon:
I, too, was bitten by the no-mobile-data bug. When browsing the logs returned by `adb logcat -b radio`, it seems Android thinks it is being refused by the operator. There is the following line:

10-23 18:09:48.907 2124 2242 D RILJ : [4108]< SETUP_DATA_CALL DataCallResponse: { cause=33 retry=-1 cid=0 linkStatus=0 protocolType=-1 ifname= addresses=[] dnses=[] gateways=[] pcscf=[] mtu=0} [SUB0]

And cause 33 (maybe) refers to DataFailCause error SERVICE_OPTION_NOT_SUBSCRIBED? But data connection with the same SIM and APN settings works in a different phone.

My phone is XT1541 (it seems that all users who have this problem are from Europe?), baseband version M8916_2020629.41.03.21.51R. I can't upload files or post links, but the log is here: https://pastebin.com/EtQB8FfE

Is there any way to get more logs or debugging information?
[Moto G 2015 Original Android Development] althafvly:
Previous TWRP builds were built on nougat and it was alot compressed (may hit on performance - so far no one cares on recovery). Currently we are building from Android Pie source with new changes in hw decryption made it bit big in size.. Also i didn't do much compression like nougat , thats why its bit sizy :p

Some Carrier apns are missing in lineage apns.conf. that why some of you are facing mobile data issues.. if you could specify any previously working rom and apn configs or ss will be helpful to add those apns to lineage repo
[Moto G 2015 Original Android Development] vjon:
I don't think that's the issue, as I've re-entered the APN settings manually in hope that this would fix it. Mobile data used to work on LOS 14.1. My carrier is Vodafone CZ.

As far as I can see, the records for Vodafone CZ in

github.com/LineageOS/android_vendor_lineage/blob/lineage-17.1/prebuilt/common/etc/apns-conf.xml

are identical to

github.com/LineageOS/android_vendor_cm/blob/cm-14.1/prebuilt/common/etc/apns-conf.xml
[Moto G 2015 Original Android Development] althafvly:
Manually settings apn configuration isnt working on los17 for some reasons. You need to edit apns-conf.xml and replace it in system/product/etc/ . Theres no mobile data issues in our current builds.. most issues are due to apns , changes in proxy can also cause such issues.. you can check gitlab issues if you want something related
[Moto G 2015 Original Android Development] vjon:
OK, thanks for letting me know. I've reset the settings to the defaults, which are correct, and rebooted the phone, but I still get no connection. I'll try to fiddle with the apns-conf.xml file through TWRP.
[Moto G 2015 Original Android Development] mattcri:
same issue here, i tried adding the data in apns-conf.xml.

<apn carrier="ho." carrier_id = "2455" mcc="222" mnc="10" apn="web.ho-mobile.it" authtype="0" type="default,supl,hipri,fota" mvno_type="spn" mvno_match_data="ho." />

<apn carrier="ho. (Tethering)" carrier_id = "2455" mcc="222" mnc="10" apn="internet.ho-mobile.it" authtype="0" type="dun" mvno_type="spn" mvno_match_data="ho." />

Ho-mobile sim from italy, after adding the config in the file the apn is correctly selected bu data still does't work.
[Moto G 2015 Original Android Development] Gluipertje:
Yup same issue here, mobile not working with apn confirmed set correctly
[Moto G 2015 Original Android Development] woheller:
After a long time I justs ha such an unexpected reboot. Nothing in the logcat...
[Moto G 2015 Original Android Development] mattcri:
fixed for me in today build, data works just settings the apn manually
[Moto G 2015 Original Android Development] Ska2:
Thank you [MENTION=5881712]althafvly[/MENTION] cant wait for the stable build :D
[Moto G 2015 Original Android Development] DarkSJ1998:
Hi guys I've been on LOS 17.1 on my Merlin since August, it has been pretty stable for me.

I upgraded to the 24th October build day before yesterday.

I just figured out 2 issues yesterday:

1. My device doesn't support 5Ghz WiFi anymore. Neither can it detect 5Ghz WiFi, nor can it create a 5Ghz WiFi Hotspot.

2. My device speakers are not longer working. I can listen to audio via earphones, but not via the device speaker. Any way to check if it's software or it's an hardware issue?

Since I don't use merlin as a daily driver, I just figured out these 2 issues yesterday. Honestly don't know if these popped up after I upgraded to the 20201024 build or it's just a coincidence.
[Moto G 2015 Original Android Development] llamagustin:
Existe la posibilidad de habilitar Miracast ?, Build.prop no incluye la opción. :fingers-crossed:

Gracias por el excelente trabajo :good:
[Moto G 2015 Original Android Development] honky-tonk77:
APN not working

Today I setup a device with 30th build. I also don't have mobile data on 4g.

Strange observation that let me assume APN is correctly set:

Switching between 2 preconfigured APNs 20-30 times back and forth suddenly gets 4g data working, until the next "disconnect"/airplane mode on&off

Setting mobile data to 3g works perfectly -> which would not work when APNs are misconfigured

What could I do to help debug?

Edit:

- 4g sim from a different carrier with different APN of course works well...
[Moto G 2015 Original Android Development] R1ffR4ff:
If I have problems with APNs I click on the 3 dots top right in the APN section and choose the Reset option and then flick Flight-mode on and off. Give that a go.

HTH :)
[Moto G 2015 Original Android Development] justabegginer:
Modifying apns-conf.xml worked for me. In my case, the carrier specified that the mnc should be 03, but the apns-config.xml file had it specified with a value of 08, I just replaced its value, and now everything works fine.

Here is what I specified in the modified file

<apn carrier="Euskaltel" mcc="214" mnc="03" apn="internet.euskaltel.mobi" user="CLIENTE" password="EUSKALTEL" type="default,supl,Internet" />

Thank you [MENTION=5881712]althafvly[/MENTION] !!
[Moto G 2015 Original Android Development] althafvly:
Create an issue in lineageos. Then i can add this
[Moto G 2015 Original Android Development] justabegginer:
[MENTION=5881712]althafvly[/MENTION], I created an issue in GitLab, named "Incorrect configuration of Euskaltel in apns-config.xml" (I cannot post links yet, so I could not insert it in the reply).

Please, tell me if the issue report is OK.

Thank you!
[Moto G 2015 Original Android Development] SantiStark:
Help me, Battery Drain

Hello,

I had lineageOS 17.1 20201023 and The rom is incredible, but this have a big problem ... "Battery Drain"

I used this rom for Eleven days and I have 2 hours of screen time every day with a full charge, I don´t know, What do I do?, I only use the phone for Whattsapp, Instagram, Youtube, Facebook lite and others Social Networks.

Today, I went back to lineageOS 14.1 20201027 and I have between 4 or 5 hours of screen time, but I love lineageOS 17.1, is the best experience that I had.

Please, Help me!!!!!!
[Moto G 2015 Original Android Development] ctcx:
If this device's CPU supports arm64, why is this ROM still always built in plain arm?
[Moto G 2015 Original Android Development] honky-tonk77:
..deleted
[Moto G 2015 Original Android Development] althafvly:
Test Build

- lineage-18.0-20201109-UNOFFICIAL-osprey

- lineage-18.0-20201109-UNOFFICIAL-merlin

To-do: Selinux enforcing

Everything else should be working fine now

ROM

https://androidfilehost.com/?fid=10763459528675580388 (osprey)

https://androidfilehost.com/?fid=10763459528675580258 (merlin)

GAPPS

https://sourceforge.net/projects/al...rm-11.0-pico-20201108-UNOFFICIAL.zip/download
[Moto G 2015 Original Android Development] honky-tonk77:
Cool! Thanks!!! ...could you please provide/specify the device tree you're building with?
[Moto G 2015 Original Android Development] Amjadh:
Poli Dude.. Thanxx :)
[Moto G 2015 Original Android Development] ctcx:
[MENTION=5881712]althafvly[/MENTION]:

If osprey's CPU supports arm64 in hardware, can't LOS 17.1 and 18.0 be build as arm64 as well?
[Moto G 2015 Original Android Development] Dany XP:
Does anybodt know why camera doesnt take any pictures? Or where can i find osprey builds of Lineage 17 or 16?
[Moto G 2015 Original Android Development] Amjadh:
I think the the device drivers also need to be written in 64bit which isn't the case here.. If u need a 64 bit rom, some dev have to extensively develop 64 bit open source drivers, kernel and recovery along other things before even starting to think about ROM.. Considering we have a 2GB ram device and a severely outdated SoC, I don't think it is worth the effort.. There won't be any considerable performance or efficiency benefit..
[Moto G 2015 Original Android Development] woheller:
GPS

Can anyone provide the original gps.conf from a Moto G3 stock image?

GPS fix is much faster there compared to LineageOS default GPS settings.
[Moto G 2015 Original Android Development] beta_serpico:
Hi there,

Camera seems broken after 17.1-20201113-NIGHTLY-osprey update.

I can see only a black screen after opening default camera app.

Any ideas? Should I wait for next update?

Thanks!
[Moto G 2015 Original Android Development] lmeu:
TWRP no longer installs update automatically / error during update install

Hi,

I have two questions:

1) Since two or three weeks, the osprey OTA update no longer runs as smooth as it did before: In "System" / "Updater", I download the latest build, click "Install", and "OK" to confim. Then the system boots into recovery, but TWRP no longer automatically starts the installation. It just boots into the main menu of TWRP. To update, I have then to manually select the ZIP file from "/data/lineageos_updates/". I'm 95% sure that this problem appeared the first time after I updated TWRP from 3.4.0-0 to 3.4.0-1 (downloaded from the official home page). Does anyone else have this problem?

2) Today, I installed the 20201113 update for osprey. During the update, the following error was shown:

Failed to map file '@/cache/recovery/block.map'
Error installing zip file '@/cache/recovery/block.map'

Appart from this error, the update completed and LinageOS seems to work as expected and also my recovery (TWRP) still works. Is the error something I should be worried about?
[Moto G 2015 Original Android Development] woheller:
I have the same problem with latest TWRP and installed the previous TWRP again. I think the error which is shown stems from previous fail to execute the update script.

---------- Post added at 07:37 PM ---------- Previous post was at 07:29 PM ----------

On my phone camera works fine with that update. But I sometimes (also with previous versions) have the problem of a black screen. After a reboot camera works again.

https://gitlab.com/LineageOS/issues/android/-/issues/2728

Are you using Magisk?
[Moto G 2015 Original Android Development] beta_serpico:
Thank you! After reboot, it starts working again!

No, I don't use Magisk.
[Moto G 2015 Original Android Development] woheller:
If it happens again you should maybe add information to my bug report if possible.
[Moto G 2015 Original Android Development] Amjadh:
For me, TWRP never worked with inbuilt updater from los 17.1.. It will reboot to recovery but fails with some error and reboots.. Manual updates aren't an issue though.. Well my problems are now fixed as i flashed LOS recovery.. Now updater works, and I keep a twrp system and img backup just in case..
[Moto G 2015 Original Android Development] fahadaslam2000:
For me, OTA has never worked for me on LOS17 on this device. While device reboots into recovery, it does nothing. I've always had to navigate TWRP to data/lineageos_updates and manually select the update to start flashing.

But it hasn't been much of a problem, so I haven't bothered too much to look into it.
[Moto G 2015 Original Android Development] Carnilex:
Hi,

I am a happy user of Lineage OS since two years or so on a Motorola from 2015. Today, I subscribed to this forum to report an incident that occurred when updating to the last version available.

Here are remarks and description of the problem :

- The download of the update got interrupted by a slight lack of storage. After deleting some pictures, it got completed. I clicked on install, it booted to TWRP and auto-lauched to installation

- The first boot after install lead back to TWRP

- The next boot attempt stayed frozen

- I manage to enter back to TWRP and "restore" from a backup one month ago, leading to a boot fail (AP Fastboot Flash Mode)

- "wipe+restore" did not helped more

- luckily, wipe+install from scratch (.zip files) yields a working system

- Trying to restore from this point and backups fails again.

Apparently, the best I can do is Wipe+Install from .zip. Any idea on how to recover my setup from a backup?

Thank you!

EDIT : I managed to recover my system at last backup from wipe + install .zip files + download/install last update + recover data from last backup.
[Moto G 2015 Original Android Development] landal:
I had same problem here: no mobile data at all.

I applied this and now it works: https://xdaforums.com/showpost.php?p=74733635&postcount=4

(my baseband was M8916_2020632.44.03.21.54R, same after update... but working)
[Moto G 2015 Original Android Development] stukdev:
Latest OVA update (21112020) broke more functions:

- no bluetooth

- no audio

- no sim

- much ui freeze

Can i manual update with the previuos update?
[Moto G 2015 Original Android Development] vjon:
My mobile data connection works now. You're my hero. :) My baseband also didn't update to a newer version, but the simple act of reflashing made it work properly.
[Moto G 2015 Original Android Development] honky-tonk77:
[MENTION=11202557]vjon[/MENTION] [MENTION=2049955]landal[/MENTION]

Which versions did you flash?

I tried from here https://xdaforums.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639

for my xt1541 16/2GB model:

Retail Europe (2GB) - XT1541_OSPREY_RETEU_2GB_6.0.1_MPI24.107-55-2_cid7

Retail Europe (2GB) - XT1541_OSPREY_RETEU_2GB_6.0.1_MPIS24.107-55-2-5_cid7 (Newer Build)

here I only flashed firmware as shown in this guide:

https://xdaforums.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750

did you proceed the same way or anything different???

---------- Post added at 01:40 PM ---------- Previous post was at 01:40 PM ----------

[/COLOR [MENTION=11202557]vjon[/MENTION] [MENTION=2049955]landal[/MENTION]

Which versions did you flash?

I tried from here https://xdaforums.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639

for my xt1541 16/2GB model:

Retail Europe (2GB) - XT1541_OSPREY_RETEU_2GB_6.0.1_MPI24.107-55-2_cid7

Retail Europe (2GB) - XT1541_OSPREY_RETEU_2GB_6.0.1_MPIS24.107-55-2-5_cid7 (Newer Build)

here I only flashed firmware as shown in this guide:

https://xdaforums.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750

did you proceed the same way or anything different???
[Moto G 2015 Original Android Development] vjon:
I used the newest one for my phone:

XT1541_OSPREY_RETEU_2GB_6.0.1_MPIS24.107-55-2-5_cid7
[Moto G 2015 Original Android Development] honky-tonk77:
also only flashed firmware or full rom?
[Moto G 2015 Original Android Development] vjon:
Only the firmware. I simply followed the linked instructions.
[Moto G 2015 Original Android Development] okam1000:
MásMóvil APN does not work on Osprey with LineageOS 17.1

Hello.

The mobile data connection of my Moto G3 does not work after switching to a different carrier (MásMóvil). I have tried manually configuring APN settings without success. I have read that APN cannot be manually configured due to a bug in 17.1. So it looks like the default settings for MásMóvil APN are wrong. How can we fix this?

Thanks!
[Moto G 2015 Original Android Development] R1ffR4ff:
Have you trying to modify the old entry or making a new entry?
[Moto G 2015 Original Android Development] okam1000:
Yes, I have tried that, but the mobile data connection still does not work, and I have seen a message from [MENTION=5881712]althafvly[/MENTION] in this same thread explaining that the APN manual configuration is broken....
[Moto G 2015 Original Android Development] R1ffR4ff:
Shame :(

Try this. In the phone settings > Networks & Internet > Mobile Network > Advanced and scroll down to the Access Point Names > 3 Dots top right and reset them and then restart the phone and see if it picks up the correct ones :)
[Moto G 2015 Original Android Development] okam1000:
Thanks, tried that too, it didn't work... :(