yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] R1ffR4ff:
Did you try the Phone Settings Backup and Reset section and do a full Network/Bluetooth/WiFi reset?

Write down any Wifi logins as they will get wiped.
[Moto G 2015 Original Android Development] okam1000:
Problem persists...

I have seen that the MNC value for MásMóvil should be 03 but in my phone it is 04 and if I edit it when I come back to the APN screen it is again set at 04. Maybe this is the problem [MENTION=5881712]althafvly[/MENTION] was referring to...

How can I set MNC value to 03 ?
[Moto G 2015 Original Android Development] R1ffR4ff:
Try this obscure trick which may sound strange. Phone settings and find the Language and input and change to a different language even from US English to UK English then restart the phone and change back and then flick Flight-mode on and off. See if this resets things.

If no good see if an APN Switcher can help,

https://play.google.com/store/search?q=apn chooser&c=apps&hl=en_GB
[Moto G 2015 Original Android Development] okam1000:
Thanks a lot for your help but unfortunately this didn't work.

I have been checking the MNC value and I was mistaken, apparently the value in the phone (04) is the correct one.

So it looks like there is another issue with the data connection...
[Moto G 2015 Original Android Development] R1ffR4ff:
Sorry it didn't work. Check your PMs :)
[Moto G 2015 Original Android Development] okam1000:
I have reported the issue in GitLab including the device log. I hope you can find something: https://gitlab.com/LineageOS/issues/android/-/issues/2806
[Moto G 2015 Original Android Development] Voha888:
I have installed last version and its have bug from many custom ROMs from many devices - hidden wifi networks not works some time. Which version are stable?
[Moto G 2015 Original Android Development] okam1000:
Hi again. I fixed the issue on my device by following the instructions included in GitLab ticket.
[Moto G 2015 Original Android Development] Gordster:
I've noticed on the 2020/11/27 and later rom that I can no longer save camera photos to my SD card and must save them to the device internal memory. Even with Open Camera it doesn't seem to work. Why was this 'feature' taken out?
[Moto G 2015 Original Android Development] IronTechmonkey:
Due to Google's implementation of scope storage in newer versions of Android photos were being saved to a location on external hard drive which was not accessible by either the native Gallery app or the camera app so attempting to access a picture saved to external SD from the preview in the camera app would take the user to the internal SD and the user might never know that were private pictures on the external SD which is not a secure location. A debate rages on about how some apps work around this but that is apparently something that LOS cannot do so save to external SD was removed. There are more details from developers in a ticket at the official LOS gitlab.
[Moto G 2015 Original Android Development] Silver Werewolf:
Lol thats HORRIBLE, so the only solution is to download the version prior to that? the 20-11-2020 to be exact
[Moto G 2015 Original Android Development] IronTechmonkey:
To me the solution that IS to make the device safer by removing option to save to external SD. Also, some perspective on development: I'm interested in testing the software, not just acquiring it and agree with the decision. It's easy to work around; maybe this will spur a wave of development in simple apps that can move the pictures... if there are not already many of those, the broken spell check if far more limiting to me.
[Moto G 2015 Original Android Development] Silver Werewolf:
This device has 4gb for the user, is barely enough for some apps, i don't want the photos and videos too there.... "safer" who cares really, its like the meltdown and spectre patch in windows, nobody cares and it only decreases performance, why i have to use a app to move the photos and videos after taking then... its has no sense.. you pick where you want to store your multimedia files and thats its, if you wanna be "safer" from who knows what you pick internal storage, else sd card :P
[Moto G 2015 Original Android Development] IronTechmonkey:
It's clear that you don't understand the larger Google construct, (including policies and software) in which this development occurs, or the need for prioritization of privacy and safety over convenience. Additionally, this is a development thread where the point is to contribute to development of LOS17-Ocean; not to complain about the decisions that were made from an uninformed point of view having contributed nothing to the effort.
[Moto G 2015 Original Android Development] Silver Werewolf:
Hello, the camera is still broken, that bug that it opens and it only shows a black screen and you have to restart the phone is still there, happen to me two times in a row, it even rebooted my phone just now, and in google maps rebooted my phone too... also there is a notable battery drain compared to stock, i'm using the last nightly with gapps nano, nothing more. Greetings.

EDIT: lol no, i rebooted the phone for 3er time and the camera is still a black screen, i think this last nightly completely broke it XD
[Moto G 2015 Original Android Development] JuniorSPTUX:
I did a clean install of the latest version of osprey, and everything seems to work perfectly!!! One minor issue that bother me is related to wifi. For any reason, it drops frequently and then I need to switch off and on many times till it works. It show my network as saved, then when I try to reconnect it ignores that.

Did anybody faces this behaviour?

tks,
[Moto G 2015 Original Android Development] mumfordfan:
The camera is working fine here on my osprey.

Maybe faulty hardware?
[Moto G 2015 Original Android Development] Silver Werewolf:
emmm no, not at all, i have several random restarts also...
[Moto G 2015 Original Android Development] domin144:
Hi all,

I have installed version lineage-17.1-20210101-nightly-osprey-signed.zip on my XT-1541. Everything works fine except mobile data connection. Phone and SMS work OK. Wi-Fi works OK, but mobile data not. What is even more interesting, when I insert my wife's SIM card (different provider) cellular data works correctly.

My SIM is not broken, it worked before update to lineage os, it also worked in other phone (Moto G5, I no longer have it) with unofficial build of Lineage OS 17.1 and still works in USB modem.

I tried erasing all APN's and putting only exact data provided by service provider, but it didn't help. The provider is plusgsm (ustaw.plus.pl)

Any idea what else I could check?
[Moto G 2015 Original Android Development] domin144:
It solved my problem, too. At least for the mobile data part. I still cannot send or receive MMS messages.
[Moto G 2015 Original Android Development] FredBirne:
Had the same issue with the mobile data connection.

I tried that modem fix as well but didn't really help. I also played around with the APN settings but no change.

As a workaround I was able to change the network type from 2G/3G/4G to 2G/3G. With that the Phone was connecting to the network. Afterwards I changed it back to 2G/3G/4G and it now works as well with LTE.

Not tested MMS as I don't use it.

Model: XT1541

Provider: Congstar (German Telekom)
[Moto G 2015 Original Android Development] cromfr:
hello and first of all thank you for this great work. I've just installed the latest (15/01/2021) version after 5 years of stock ROM.

the only problem i face ils the black screen during call (or listening voicemail message). It seems related to the proximity sensor, but i don't know if it's hardware related (broken ? Calibration ?) or software (i had similar behavior with stock rom but i just had to press power button to get back my screen on).

anyone experiences the same or could give me leads to correct this ?
[Moto G 2015 Original Android Development] Mgallo:
If you want to use the sd card as internal you have to put the device in debugging mode, download adb on your computer and put the following commands:

adb shell

sm list-disks (There it will tell you the number of your sd card, for example: disk: 176,76)

sm partition disk: (insert number of your sd) mixed 50

and voila, they already have the sd partitioned as external and internal, I don't know why the dev doesn't add it natively
[Moto G 2015 Original Android Development] okam1000:
Hello.

It looks like the firmware is reporting hover support (in other words, that it has a mouse) to the browser apps: https://gitlab.com/LineageOS/issues/android/-/issues/2979

Is this something that is device specific @althafvly ? Maybe there is a setting somewhere in Android / LineageOS to configure the device as a "touchscreen device" instead of a mouse-equipped device.

Thanks!
[Moto G 2015 Original Android Development] okam1000:
It seems that other devices are not affected by this issue:

Discord - Group Chat That’s All Fun & Games

Discord is great for playing games and chilling with friends, or even building a worldwide community. Customize your own space to talk, play, and hang out.

discord.com

So it looks like there is something wrong in osprey configuration. Do you know where are the device capabilities configured?
[Moto G 2015 Original Android Development] kr428:
Hi all, just did an install of the latest version (20210219) and ran right into a bootloop. Not sure if this is just my device, now trying to somehow recover from that. Anyone else seen this?
[Moto G 2015 Original Android Development] althafvly:
IMPORTANT MESSAGE

Lineage 17.1 users who uses lineage recovery please update recovery before the ota, downloading from official site. Possible risk of loss of data.

Builds after 20th of February will be affected

TWRP users are not affected
[Moto G 2015 Original Android Development] kr428:
Does TWRP need an update too? Still trying to figure out what got me into bootloop yesterday...
[Moto G 2015 Original Android Development] kr428:
Still trying to understand this bootloop, I updated TWRP to the latest version available for osprey (3.5.0_09), with the result that OTA updates can't be installed through the OTA update downloader/installer anymore. Is this a known issue...?
[Moto G 2015 Original Android Development] Ska2:
I had the same issue with my Osprey, after updating TWRP to 3.5.0_09 I couldn't install OTA updates anymore. When I tried to downgrade TWRP to 3.4.0-1, I couldn't install them too. So, I have downgraded to 3.4.0-0 and after that I could finally install OTA updates.
[Moto G 2015 Original Android Development] Enthused9801:
I have major problems. I updated ota to 26th Feb update with the option selected to update lineage recovery at the same time, surely it updates this first before applying the update?? So why have i got these problems?....bluetooth, mobile function doesn't work at all, no calls or sms, no sim card detected....sometimes after a reboot or bootup, phone reboots again on its own and google services are slow to start.

How can I fix this? Is the data corrupted?

Another question if you could answer while i'm at it, about the ota updates, why doesn't lineageos notify you when the new weekly updates are available automatically?

Thanks, looking forward to a resolution to this asap
[Moto G 2015 Original Android Development] okam1000:
Same problems here after updating to Feb 26th version. How can we fix this? I would like to "update" to the previous version (Feb 19th) without losing all data. Can I use the push_update script with the previous ZIP?
[Moto G 2015 Original Android Development] okam1000:
Hi again. I have been able to successfully rollback to the previous version without losing data using the Sideloading from Recovery method (the push_update method does not work for a rollback because, after uploading the previous version ZIP to the device, when you go to System Updates it is displayed as an old version of the firmware and you cannot install it, only the option DELETE is shown).
[Moto G 2015 Original Android Development] Enthused9801:
Glad you got it working but I thought its not advisable to rollback only forward is allowed....? Have you come across any problems yet?
[Moto G 2015 Original Android Development] okam1000:
Everything is working as before, no problems.
[Moto G 2015 Original Android Development] moojammer:
I too am having issues on my XT1540. I flashed the latest Feb 26 via TWRP 3.5.0_09. I didn't have cell service, no media would play and no sound. I tried sideloading the previous version as stated above but I still had the same issues. So I tried going back to Feb 05 zip but things got worse. I couldn't get passed the lock screen. So again I sideloaded forward to the Feb 19 version with the same issues (no cell service, no audio). I'm not really sure what to do from here.

Any help would be greatly appreciated.

Update: I factory reset and 0219 is working.
[Moto G 2015 Original Android Development] kr428:
That's pretty much what I ran into with the previous version - 0219 left me going back some releases until eventually doing a factory reset, updating TWRP (which didn't seem to change much except for OTA doesn't work anymore at all) and manually flashing 0219 over a then backed-up system. No idea what's going on in these.
[Moto G 2015 Original Android Development] woheller:
Does taking HDR pictures work for you? On harpia I can see a difference between HDR and non HDR pictures. On osprey I do not notice a difference. Also sometimes no sound is played when an HDR image is shot.
[Moto G 2015 Original Android Development] Enthused9801:
Great, I tried going back and it worked too! Next build...is it going to work though? I see no apn fixes in the changelog like last time, so not sure if we are going to run into the same problems?
[Moto G 2015 Original Android Development] kr428:
Did anyone so far try using the 2021-03-05 build? Does it makes sense to give this a try?
[Moto G 2015 Original Android Development] Enthused9801:
Don't think so, no changes in the changelog.
[Moto G 2015 Original Android Development] Enthused9801:
Anyone try the new build 12th March?
[Moto G 2015 Original Android Development] genders:
Yes I have installed per update, but I had the problem that audio was not working.

Then I have decided to make a complete new installation and it seems that all is ok now.
[Moto G 2015 Original Android Development] Enthused9801:
So it seems it only works as a new install unless someone else has the update working? I tried the update and I can't even log in to the phone anymore, it just kicks me back to the lock screen over and over again after I put in the right code...i did go from build 19-2 to 26-2 back to 19-2 then updated to 12-3 then back to 19-2, might have something to do with it. I'll try a new install tomorrow.
[Moto G 2015 Original Android Development] beta_serpico:
Hi @althafvly

I did a factory reset, flash last lineageos recovery and then flash 20210312 rom.

I'm wondering if it is possible to update the recovery via OTA and not by adb sideload. I should maintain my dad's phone and he lives in another city.

Could he upload automatically the recovery?

Thanks!
[Moto G 2015 Original Android Development] Enthused9801:
Yeah just take a look in developer options ;)
[Moto G 2015 Original Android Development] Arch Carrier:
Couldn't update for a while because of a problem with my cache partition. I wiped the cache in TWRP and unintentionally also my vendor partition. Now I can do the update, but the phone won't restart in Lineage OS. It keeps loading until it reboots into LineageOS recovery.

I then have to reinstall TWRP via fastboot and restore a backup.

How can I recreate the Vendor Partition? Or how can I install LineageOs fresh? I can't find the Vendor image which needs to be flashed?
[Moto G 2015 Original Android Development] Enthused9801:
Follow the instructions on the lineageos website https://wiki.lineageos.org/devices/osprey/install for a fresh install.
[Moto G 2015 Original Android Development] LineageUser:
I was affected in a loss of my EMEI-Number while updating (with old lineage recover).

First i thought my sim-card-slot is defective. After reading this post i managed to "repair" my phone.

Fortunately when i first changed to Lineageos14 in 2018 i did a full backup with TWRP before flashing Lineageos14.

So with this old backup and sideloading the old version of twrp i was able to restore the last Stock-Rom. This restored my EMEI as well.

After that i flashed newest lineage recovery and newest Lineageos17 and Gaps again.

In future, how can i automate the update of lineage recovery since with each new Lineageos17 a new lineage recovery is released. Such problems could be coming again.

Without warning OTA-Update should be preventet by the updater when lineage recovery does not match the update-version..

I had no Data lost since my G3 is my holiday, outdoor, walking smartphone. But a lost lot of sweat until i successfully unbrick my smartphone.

This was my first time ever - i had problems with any update.

Question:

The lineageose recovery was first introduced on osprey with Lineageos17.

When Lineageos14 was out TRWP was used by me.

On updating to LOS17.1 i changed recovery to lineage-recovery because i thought it is better because of compatibility issues.

This seemed to be an error of my. Shoud i switch to TRWP again or stay with lineageos recovery (which offers for example no backup or restore - which saved my phone because i was able to restor to stock)?
[Moto G 2015 Original Android Development] okam1000:
Is it safe to update osprey from February 19 (or older) firmware, to the current firmware version? I have remained in this version since the last failed update that rendered my phone unusable and would like to know if someone has successfully done an OTA update from February 19 or previous, to March 19 or 26 version... Thanks!
[Moto G 2015 Original Android Development] Arch Carrier:
I hoped for a way to avoid a fresh install, but in the end followed your advice and reinstalled fresh.
[Moto G 2015 Original Android Development] Gordster:
Has nobody else had occasional spontaneous reboots? I have 2 moto g3 osprey phones and it does this on both of them. It is totally unpredictable but happens at least once or twice each week. It has happened on all tried versions up to and including the 2021/03/26 version.
[Moto G 2015 Original Android Development] Enthused9801:
I did the same and now its running pretty stable, had one random reboot when first installing the next update but now its very solid. Recommend everyone having problems to do the same. The update 26th Feb just doesn't work, it needs a fresh install, something major has changed is my guess. Hope its the last time.
[Moto G 2015 Original Android Development] Gericom2:
Hi, I have been using the lineageos 17.1 2021-03-26 osprey nightly for about two weeks now. Overall I'm pretty satisfied with it, but I've noticed a few issues and I wondered if other people might have them as well.

Issues with mesh wifi networks

At home we have 3 deco mesh wifi accesspoints and when connected to them, it constantly switches (with an actual reconnect that takes a few seconds) between the different ap's. I never had issues with the stock rom.

Google chrome occasionally freezing the entire phone

This issue is pretty major. When browsing with google chrome it can randomly happen that everything suddenly freezes. When this happens, a reboot is not enough to fix it, I guess because the apps you had open last time are started again after a reboot. If you are lucky you can quickly force quit chrome before whatever happens in the background that causes a new freeze. If not, it requires to use adb to quickly quit or uninstall chrome after boot to fix the issue. If you don't do this the phone keeps freezing a short time after every reboot.

Occasional distorted text rendering

Once in a while it happens that some text appears distorted. Very strange crippled, for some reason it slightly reminds me of comic sans xD. When it's inside something scrollable, simply scrolling up and down (and thus forcing redraw) fixes it.

It would be great if something could be done about them. Especially the second issue, although it seems like it might be a quite complicated issue.
[Moto G 2015 Original Android Development] Silver Werewolf:
Yep, here too... since always hahaha
[Moto G 2015 Original Android Development] Silver Werewolf:
Revert "Snap: Remove saving to sdcard"

hehehehe easy peasy lemon squeezy
[Moto G 2015 Original Android Development] IronTechmonkey:
Interesting. I wonder what they did to mitigate the privacy issues. I'm using stock now but will check this out if and when I next test LOS. Thanks for the tip.

[EDIT] some of the notes within the commit may indicate a new save path so maybe they have gotten it all fixed.
[Moto G 2015 Original Android Development] IronTechmonkey:
Digging into the details shows that while this may have been easy for those who waited for a fix (including both of us) it probably was not so easy for those doing the work, if it were it would not have taken so long. They couldn't really enable this without addressing the underlying privacy concern which they have done.

In the April 9 2021 build the ability to save photos from LOS camera to external SD has indeed been restored, and the images are being saved in the conventional /DCIM/camera, location and they are accessible through the preview image in the camera app, and are visible in native gallery. Looking good.
[Moto G 2015 Original Android Development] Ska2:
Can't wait for the release of the official build of LineageOS 18.1 for Osprey. Is there any known release date ?
[Moto G 2015 Original Android Development] IronTechmonkey:
[EDIT] Reflecting change in post to which I responded.

@Ska2, the move to the next device can depend on an individual or group of maintainers and could involve an individual or group of devices. Apart from just searching the Internet (which can indeed be helpful) here are a few suggestions for trying to figure out where future development is going:

- Review the most recent posts of the maintainer of the device to see what they've been working on lately. I would not suggest using this as an opportunity to nag them but it can be informative to see. For instance, it might be considered a good sign if they are working on the next version for a similar device.

- Similarly, see if any of the maintainers have started a new threads.

- I know this suggestion sounds trite but check out the development forum top level for this device for any new.. developments... as it were. Also, ask in SD_shadow's general thread for this device

To the point you made about development moving forward, as a device gets old it may receive little more than general patches and security patches. In that context I agree that device and perhaps many of its users are ready to move on if there are people willing to keep it going.