yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Android Development] TheForce:
Thanks for your hard work.

Did you consider to skip LOS-15.1 and going straight for LOS 16 microG-hardend. Because Anisnoorudheen has achieved very good results with 16.

I've read half a year ago what you wrote about this, that was at that time also my point of view. I had no idea that pie should reach osprey. My experience with Oreo-roms weren't very good. But when I tried CrDroid from Anisnoorudheen (a LOS-16.0-rom ) I was very pleased with the stability and performance.

So in my ignorance I wrote above consideration.

Hope you are not offended ??
[Moto G 2015 Android Development] jemail:
First, many thanks for your work in keeping the osprey updated with security updates.

I would vote to keep putting out Nougat builds unless we can actually build blobs from source specifically for O or P. Is that possible now, or are we still trying to work around using Nougat blobs for O and P.

Is there any reason why Nougat cannot continue to be updated with security updates only? Nougat has been rock solid for me, all I need is a rock solid build that is Google security patched to latest level if possible. Maybe this will be too much work though?

I have been following Pie threads but what I'm seeing is, it's great until after a time of use then the problems start with WiFi, battery etc. These seem to be quite fundamental problems with accessing the hardware, which to me point to blob problems.

It's these reports that indicate to me that Oreo and Pie are not ready to be used as daily drivers in my use case. When I have time I'm all for helping ROM development but I need to know I have a rock solid stable daily driver to actually use my osprey reliably.

If it ain't broke don't fix it is my philosophy.

If you have to move to another Android version I would say skip Oreo and move to Pie, assuming osprey is officially supported by lineageOS.
[Moto G 2015 Android Development] MSe1969:
Hello [MENTION=4879946]TheForce[/MENTION] [MENTION=5445416]jemail[/MENTION] - thanks for your feedbacks.

Some points to be made for a better understanding:

In general, my motivation is to provide builds, which are suitable as daily-drivers - this obviously means, that in most cases my builds aren't made from the latest android versions. (If you e.g. look into my Xperia Z1 LineageOS 15.1 thread, which I have linked above for the key migration topic, this build does have some limitations like Radio app only mono or WiFi-Hotspot only working in 2.4 band - but it definitely is suitable as a daily driver with e.g. proper battery behavior and working Cam). So yes, unless a newer version suitable as daily driver is available, I will continue providing cm-14.1 builds for the Osprey device.

Having said so, I have come to know since a couple of weeks, that [MENTION=6485916]squid2[/MENTION] has requested to officially maintain LineageOS 15.1 for Osprey (i.e. conforming the strict LineageOS charter), which has a significantly different meaning to me compared to the various other oreo and pie threads for the osprey device, so I thought it could be considered worth a try (I was waiting for it to happen officially first...).

Regarding pie, in addition to the points made above: Whilst I am working on bringing my hardened build to LineageOS 16.0 (for my primary device, an OP3T, for which there is already official LineageOS 16.0 support), I am not finished yet porting everything, have intermediate issues with microG and coarse location and still finding out about the differences (e.g. AOSP pie does not have an onboard TTS anymore, and Gapps is definitely no option in my case) - so skipping Oreo for Pie is no option right now.

The Osprey device by the way is not any more my primary device, in fact my son uses it now - therefore the "level of testing" is different compared to using the device myself, that is why I am asking for qualified feedback from people willing to give it a try to see whether it would be worth following that path.

So any feedback to the test build's functionality is highly appreciated.

:)
[Moto G 2015 Android Development] jemail:
I will try your test build, but it will not be until later this week and probably the weekend before I have time to try it on my osprey. I will give feedback on it probably next week sometime.
[Moto G 2015 Android Development] hovnonium:
This build works for me without any issues. :good:

Thanks
[Moto G 2015 Android Development] wxjpjgsvne:
Your work here is so underrated man, I wish I had saw this thread before (I was stucked on LOS 14.1 with Feb. Patch). I will be testing your LOS 15.1 test build and try to keep as a daily driver for at least one week. Thank you very much for all the effort put in those builds.
[Moto G 2015 Android Development] MSe1969:
New builds available with May 2019 ASB

Hi,

new builds with May 2019 ASB patches are available for download:

A. Regular LineageOS 14.1 with OMS and microG patch

https://www.androidfilehost.com/?fid=1395089523397962962

- Android System Webview updated to M74

B. Hardened build with pre-installed microG (w/o OMS)

https://www.androidfilehost.com/?fid=1395089523397962963

- Bromite System Webview updated to M74

- Pre-installed Yalpstore

C. Hardened microG-build with OMS patch

https://www.androidfilehost.com/?fid=1395089523397962961

- Bromite System Webview updated to M74

- Pre-installed Yalpstore

Happy flashing!

M.
[Moto G 2015 Android Development] jemail:
Initial feedback after installation with no root. Very basic testing at this time.

Flashes with no problems.

Boots with no problems.

WiFi and Bluetooth seem OK.

All stock apps launch with no FCs.

APNs - I have 3 APNs that cannot be edited or deleted. All other APNs can be edited and deleted. I have a French SFR sim card, but I do not have these problems at all on lineageOS 14.1.

No default camera app installed.

Settings - > Search in settings causes FC.

I will continue testing over the next few days, but I'm not seeing any advantage over lineageOS 14.1 so far.

Edit: Cannot login to Google using microg. I get the unending Agree page. This is a bug with Bromite Webview as far as I'm aware. This is a deal breaker for me unfortunately, so I have to roll back to lineageOS 14.1 as I have that working with no problems. For me the only reason I will upgrade to Oreo or Pie will be if I'm absolutely forced to or I buy a new device.

I really hope you continue to build lineageOS 14.1 and share them.
[Moto G 2015 Android Development] MSe1969:
Thanks a lot for your efforts - the Google issue seems to be related to webview M74 in General, not specific to Bromite. Let's see...

If you guys are happy with 14.1, let's continue staying on it for now...
[Moto G 2015 Android Development] wxjpjgsvne:
Well, after 4 days I can easily say that the Oreo build is pretty stable as a daily driver. I have a XT1544 (1 GB RAM, Digital TV), everything works well, but the system is a little less responsive. Battery is lasting as much as Nougat, but the smartphone gets hot sometimes during afternoon, not really a issue, but that doesn't happen on Nougat. Oh, I rooted the system too, but I'm not using Magisk, I got the official LOS 15.1 root add-on.

Between the Oreo and Pie builds, the current Oreo is far more optimized. Pie's kernel is a battery hog, and the system has a lot of lag spikes during animations.

That said, I still found some bugs, but most of then were already reported by the post above. The rom didn't come with a Camera app, the search function in the configuration menu doesn't work, MicroG unable to log-in, and sometimes MicroG services crashs too, but I think that's related with the log-in problem. Encryption of the whole system doesn't work too, but that is a problem with TWRP if I'm not wrong.

Oreo will be a great build once finished, but I'm afraid that it maybe won't reach a official status before Lineage drop their support for the 15.1 version.
[Moto G 2015 Android Development] MSe1969:
Many thanks for your efforts!

Well, I think - especially since I can't really test the device using it as a daily driver - that I'll stay with cm-14.1, as it is solid and stable.
[Moto G 2015 Android Development] crazy4jack:
I had FC for yalp only, cmaera app is gone and unfortunatelly i cant flash any cameras:( i have MotoCamera_Mod for and its working on Lineage and Oreo roms but not here, im sad cuz i wanna be on Oreo - i feel this is the best Android now - Pie is strange and battery hungry - i hope MSe1969 will fix camera app on this rom cuz this is pure gold ROM imho for Osprey :)

And i installed 14.1 and for me he still have GPS issue, gps shows my location about 400m further that i am ;) and sometimes is on point - i didnt see this on 15.1 ...
[Moto G 2015 Android Development] jemail:
That's really interesting about GPS. I have no idea what could cause that. I can get a GPS lock down to 10m, sometimes 5m using the 14.1 hardened build.
[Moto G 2015 Android Development] MSe1969:
Also no problem on my (son's) osprey with hardened microG build: fast and accurate GPS fix
[Moto G 2015 Android Development] lonkar:
Sorry not asking any eta or anything but just curious. About june patches

Is there gonna be any update or not

And really thankful for still maintaining nougat
[Moto G 2015 Android Development] MSe1969:
Yes, there will be an update with June patches, probably next week. Would you be willing to test and report back, as my son is not around atm (and hence no osprey device for testing)?
[Moto G 2015 Android Development] jemail:
I will test the June build.

The May build is working on my osprey and my wife's osprey with no problems. Rock solid and stable as always.
[Moto G 2015 Android Development] lonkar:
I will definitely test it

I am on oms build and osprey is my primary device
[Moto G 2015 Android Development] lonkar:
Check this ss

And it's my primary device
[Moto G 2015 Android Development] ajaysingh23:
Which theme & which font ?
[Moto G 2015 Android Development] lonkar:
Pitch black Netflix red & font is from typeface app "overlock"
[Moto G 2015 Android Development] MSe1969:
New TEST(!) build available for download

Hi all,

as explained before, due to my son not being around with his Osprey device, I have created builds with June ASB patches (incl. two Kernel fixes as well), but I haven't tested them.

The device independent changes for cm-14.1 work for other devices (e.g. falcon) and the kernel fixes as well on other kernels. So it should work, but as I haven't tested myself this time, I can't provide the builds with the same confidence as usual.

Nevertheless, here they are:

A. Default LineageOS 14.1 with substratum and microG patch

https://www.androidfilehost.com/?fid=6006931924117893948

System Webview updated to 74.0.3729.157

B. Hardened build with pre-installed microG and F-Droid

https://www.androidfilehost.com/?fid=6006931924117893949

C. Above hardened microG build with substratum patch

https://www.androidfilehost.com/?fid=6006931924117893947

Please note the following changes for build variants B and C:

Bromite Webview updated to 75.0.3770.86

Yalpstore replaced by Aurorastore. (Yalp isn't actively maintained anymore since October last year, and since mid of last month, the app search does not work any longer - the pre-installed AuroraStore also allows app installation w/o "unknown sources")

Updates of F-Droid, F-Droid privileged extension and microG GMS core

As agreed before,

please provide feedback, whether all is ok.

If yes, I will update the OP and change log accordingly.

(If not, I will have to look next weekend)

Regards, M.
[Moto G 2015 Android Development] byemoto:
At first i just want to thank you for making this build, because for now it's the only stable daily driver for this device available. I wish you would make at least several more builds. Just upgraded to your last build (B), seems ok and as stable as before, the only issue was an ancient version of f-droid, upgraded it though. Keep on the great job!
[Moto G 2015 Android Development] Ectatomma:
Error formatting SD card as internal storage

Hi M.

I just find this superb build, thanks a lot! It gives new life to my Osprey with the much needed privacy and Google independence. I'm in for testing new builds!

I did full wipe (including internal storage) and installed test build B.

I found an error trying to format an SD card as an internal storage. It happens just after finishing formatting:

"Attempt to invoke virtual method 'java.lang.String android.os.storage.VolumeInfo.getId()' on a null object reference"

However, SD card works normally so far.

If it helps, I have a logcat starting when SD is formatting and ending just after the error, but I don't have enough posts to paste a link.

Regards, E.
[Moto G 2015 Android Development] lonkar:
Checked A build no issues no lags just perfect made a dirty flash over last build looking forward to use these builds of yours till last charge in my osprey ?
[Moto G 2015 Android Development] MSe1969:
Thanks for the feedback - glad it finally worked for you, which is the most important thing. Unfortunately, SD card issues are difficult to reproduce. If you can paste the few relevant lines of the log here, either I or maybe others reading here may have an idea. However - as I can't really test that specific behavior, it might be difficult to solve. - Since it seems to work anyhow, I tend to simply "accept" it right now . . .
[Moto G 2015 Android Development] MSe1969:
Based on the positive feedback so far on the June builds, I have updated the OP and change log.
[Moto G 2015 Android Development] lonkar:
. can you tell me which variant you prefer on your osprey ?

I use A variant but just curious and want to try the build you use
[Moto G 2015 Android Development] MSe1969:
I was, and now my son is, using variant B.
[Moto G 2015 Android Development] omzart:
Hello is that normal that in camera app, i can't turn on the flash? it's grey
[Moto G 2015 Android Development] XDrive10:
Make sure you have disabled HDR
[Moto G 2015 Android Development] omzart:
thank you that was the problem, any tips on this build regarding battery lifetime? i had to use gapps so i was wondering if i have to disable microG? thanks you
[Moto G 2015 Android Development] MSe1969:
If you wish to use the "real" Gapps, you need to use build variant A. In that case, there is no microG, only the patch allowing to use microG, and this has no further impact, if you use Gapps.

No specific advice on battery life.
[Moto G 2015 Android Development] omzart:
Ok perfect thanks

nice rom
[Moto G 2015 Android Development] MSe1969:
New builds available for download (TEST)

Hi all, new builds ready for download.

Same as last month, I could not test, since my son is still away.

However, as the device-independent parts definitely work fine, I simply have postponed applying kernel patches, therefore security string this time is 2019-07-01 only.

(Will patch the kernel later this month, when I have the opportunity to test)

A. Default LineageOS 14.1 with substratum and microG patch

https://www.androidfilehost.com/?fid=6006931924117909763

System Webview updated to M75

B. Hardened build with pre-installed microG and F-Droid

https://www.androidfilehost.com/?fid=6006931924117909762

C. Above hardened microG build with substratum patch

https://www.androidfilehost.com/?fid=6006931924117909761

Happy flashing - regards, M.
[Moto G 2015 Android Development] kaanten:
Thanks for all the hard work bro!
[Moto G 2015 Android Development] crazy4jack:
Is push notifications work or dont? :)
[Moto G 2015 Android Development] MSe1969:
In case you use microG: In microG, you need to enable it: Device registration and Cloud messaging.
[Moto G 2015 Android Development] Coffinator:
Do you plan to launch a rom with LineageOS 15.1?
[Moto G 2015 Android Development] MSe1969:
Currently not for Osprey.

Main reason is that my son (who's not living with us right now) uses the device, so testing opportunities are limited to his visits - good enough to maintain a stable release with ASB patches, but definitely not suitable to bring up a device to the next Android version.

Besides, no true "game changing" advantage...
[Moto G 2015 Android Development] MSe1969:
Don't mix things :) - If you stay within the same build variant, you can simply dirty-flash.

Variant A = oms (i.e. no microG prebuilt) - available for falcon and osprey

Variant B = prebuilt microG (i.e. no oms) - available only for osprey

Variant C = oms and prebuilt microG - available for falcon and osprey

Regarding OMS:

When switching build-flavors from oms to non-oms (A => B or C => B) and you had been using substratum themes before, you must purge the compiled themes, restore first the standard layout, remove all installed themes and uninstall the substratum app before flashing the build variant B.

Regarding microG:

When switching from a build variant A, which contains the microG patch but no pre-installed microG components, to any variant having microG pre-installed (B or C) and you had microG installed as regular user-apps (e.g. downloaded from F-Droid), then you should uninstall all the microG apps first.

If you would like to switch from a microG build flavor to the oms flavor (A), you need to deactivate all microG apps before, this will uninstall any microG updates and make sure, that nothing is left after flashing the oms build flavor.

Hope that clarifies :)

I was always announcing builds, every month - I normally update

1. The OP (links and details),

2. the change log post (#2)

3. and I create a new post in this thread to announce (see e.g. posts 133, 139, 140, 148, 163, 176).

Noticed however this time, that I forgot last month to update the change log (fixed that now), but besides, I have always announced, so I am a little bit surprised that you got the impression that I wasn't building any longer...
[Moto G 2015 Android Development] MSe1969:
Hi,

my general approach is that I try to stay with LineageOS and also prefer to build things from source. However, I also add further stuff, mostly prebuilt. When I do so, it must be one of the following reasons:

- Modified LineageOS app for specific reason

- Delivering as prebuilt is a necessity, because it is not possible to do the same by simply installing as a user app

Your app can simply be installed as a user app, there is no issue with that and bundling it does not really bring any advantage over the individual install.

Regards, M.
[Moto G 2015 Android Development] NewUser012345:
Hi

[MENTION=7929484]MSe1969[/MENTION] big thx for keeping the Moto g3 alive.

I didnt get notification in the notificationbar from my apps. The app Mydealz inform me about new shopping deals but i didnt get notification. How can i fix it?

I use (B) with F-droid store...

THX
[Moto G 2015 Android Development] MSe1969:
I think you need to configure microG and enable device registration and cloud messaging
[Moto G 2015 Android Development] NewUser012345:
device registration and cloud messaging are ON but still no notification. [MENTION=9350973]All[/MENTION] Do you get notifications?

thx

Edit:

I have clean installed LineageOS 14.1 (A) and notification are working now! :)

1. Backup your data. use MyPhoneExporer Client APP and My Phone Explorer (for Windows users). For Backup your address book u must use a older version from the MyPhoneExporer Client APP but after install the newest Version. Otherwise u get an Error by copy data.

2. Use SD Card Formatter (Windows) to format SD Card and then copy LineageOS 14.1 unofficial (A), Open Gapps (ARM, 7.1, pico), Magisk 19.2 on the microSD card and put it back into your phone.

3a. Turn the Phone off.

3b. after press and hold Volume Down and press and hold also the Power button for 8 secounds (both) then select Recovery Mode (Volume down and Power button for OK)

3c. TWRP starts(must be installed)

3d. TWRP > Wipe >Advanced Wipe > erase everything except sd card (Only if u come from a other rom)

3e. Install via TWRP > install > select SD Card > LineageOS 14.1 unofficial (A), Open Gapps and Magisk without reboot after system reboot (allways wipe cache and dalvick)

3f. skip Google Play Store

4. Download and install f-droid Store via Browser (hxxps://f-droid.org)

5. Download the zip file: hxxps://f-droid.org/en/packages/org.fdroid.fdroid.privileged.ota/

6. install the Zip file via TWRP and system restart > f-droid > settings > activate Automatic install

7. Open Magisk Manager and search and install updates and after go to settings activiert Hide Magisk Manager

8. Install your Banking TAN APP via Aurora Store !!but DONT START IT!!

9. Open Magisk Manager >Magsik Hide > activate your Banking TAN APP and also turn off root (Magisk Manager >settings)

10. You can start your Banking APP and it should work fine. If u have still a problem delete APPS DATA from your Banking APP via titanium App and try to install Magisk again and do the steps again.

11. disable updates for Banking TAN Apps in Aurora Store. (Do not update your Banking TAN APP if u dont have to)

xx=tt

I hope this will help someone!

Auroa Service: Join Aurora on Telegramm there u get a Auroa Service zip files that can u flash with TMWP or Magisk Manager, Start Aurora Service and after start Aurora Store >settings > Install > chosse Aurora Service.

UPDATE MAGISK MANAGER > Start Manager> Setting restore Magisk Manager to old name > now u can update > after hide Magisk Manager again.

It would be awesome if someone could tell us how get LineageOS 14.1 (B) notification to work!

THX
[Moto G 2015 Android Development] MSe1969:
Usually, GCM works with microG, assuming you have the self test successful and done all necessary things and enabled dev registration and GCM - however, it may happen, that it does not work for specific apps...
[Moto G 2015 Android Development] naenee:
Hi there. I'm rather enjoying this build but I have a question I'm hoping one of you can answer - should I blacklist updates to Google Services and such, or can I allow Aurora to update those components without messing the way this ROM was setup?
[Huawei P10 Plus Questions & Answers] mojoe:
Hello,

Please advise hot to update my Huawei P10 Plus VKY-L09CO2B102 to OREO.

Currently Stock Rooted EMUI 5.1 - Android 7.0 - TWRP 3.1.0-0 - root Superuser Koushik.

Did not update since purchase in June 2017. No security updates as well. I deactivated the updater.

Now I would like to update to OREO, update TWRP, and root.

Please advice how to.
[Samsung Galaxy S9+ Guides, News, & Discussion] cz_viper:
Hi,

S9+ Exynos i capable of 4k 120Fps or 1080p 480Fps. S9+ SD is not. Its a way, how upgrade camera software for these options?
[Samsung Galaxy S9+ Guides, News, & Discussion] Devhux:
I believe that while the Exynos chip is capable of that, the software doesn't allow for it. Pretty sure we would have seen mention of that in reviews (even those that had an Exynos version).
[Samsung Galaxy S9+ Guides, News, & Discussion] le0.br4zuc4:
The camera performance is the same on both devices, no extras features from one to the other either. Only onboard memory in certain markets, color and radios.

Samsung uses SD in the US because of Qualcomm's LTE license fees... That'd will change with 5G roll out
[Samsung Galaxy S9+ Guides, News, & Discussion] cz_viper:
You arent right. Exynos is capable of 4K 120FPS recording/decoding, SD845 not.
[Samsung Galaxy S9+ Guides, News, & Discussion] le0.br4zuc4:
Processor may be able to handle that but the phone, which is what I was talking about doesn't have this feature. Not out of the box or before some mods are done
[Samsung Galaxy S9+ Guides, News, & Discussion] Huey85:
Anyone having issue with video recordings stuttering? Recording in UHD (not 60 fps though). S9+ Eynos version.
[Samsung Galaxy S9+ Guides, News, & Discussion] jrharvey:
YES! Both Exnos and US version have this issue with 4k 30fps. I dont see this issue with 4k 60fps as much. Its easily noticable. My solution is to turn off stabilization. That seems to fix it. Either stabilization is taking up too much CPU or the EIS is jsut crappy and makes a hard jump rather than a smooth roll.
[Samsung Galaxy S9+ Guides, News, & Discussion] Huey85:
Wtf that's so **** man. I never encountered that with my Note8. And it's not like I'm even moving around that much or that quickly. Just moving the phone around slightly.