[ROM][osprey] Official LineageOS 14.1

Search This thread

KrisM22

Senior Member
Sep 12, 2010
3,961
1,318
many ways to guide, many ways to heal
Last edited:
  • Like
Reactions: Realz4747

Sachin ET

Senior Member
Dec 21, 2016
373
55
Does any the recent built come up with full substratum support........? i just saw something in a latest theme pack..........
 

Attachments

  • Screenshot_20170720-105038.png
    Screenshot_20170720-105038.png
    67.3 KB · Views: 610

IronTechmonkey

Recognized Contributor
Feb 12, 2013
10,055
18,112
Does any the recent built come up with full substratum support........? i just saw something in a latest theme pack..........

AFAIK nothing has changed since here: https://xdaforums.com/showpost.php?p=72081212&postcount=4410 or here: https://xdaforums.com/showpost.php?p=72820276&postcount=4977.

Also, even the Substratum Playstore page says it is not supported by Lineage OS: https://play.google.com/store/apps/details?id=projekt.substratum&hl=en.

If you saw something that says Substatum is supported by Lineage please share the source of that information.
 
Last edited:

IronTechmonkey

Recognized Contributor
Feb 12, 2013
10,055
18,112
7-21 is up. Seems fine. ringtones are hosed.
For ringtones, etc:
Use "Complete action using Media Storage" and is fine.

Problem goes away when I remove the new version of root browser by JRummy.

That is fairly common default action prompt and expected behavior which occurs when there is an app present that plays media files using the direct system commands (as opposed to a dedicated media player such as Poweramp). It should only occur after such an app is installed, uninstalled, frozen, or defrosted. Similar things can happen with root explorer apps that can access the content of APK files, in which case the default action prompt will occur when installing apks. For a long time I've seen both of these things frequently when testing MiXplorer (which has similar root browsing capability as well as a native media player).
 
Last edited:
  • Like
Reactions: sevenrock

arbasakbar

Member
Jan 8, 2017
41
4
Timer settings for do not disturb mode is not working. if i set it for 15 minutes of do not disturb, it is not getting off after that 15 minute and if i set it for next alarm, it is not turning off.

---------- Post added at 05:30 PM ---------- Previous post was at 05:18 PM ----------

Can i change my phone name ?
Now it's showing " lineage_osprey " after last flashing.
 
Last edited:

sanchith.hegde

Senior Member
Oct 12, 2015
105
12
FYI: Not only is LP off topic in this thread but it is considered warez and therefor off-topic everywhere on XDA (see XDA Rule 6). It is also just disrespectful to developers to discuss it on a developers' forum.

I agree it's bad and not to be discussed about here. But isn't that yellow badge in the screenshot due to LP? I wanted to point that out and nothing else. If I have done anything wrong, I'm sorry about that.
 

IronTechmonkey

Recognized Contributor
Feb 12, 2013
10,055
18,112
I agree it's bad and not to be discussed about here. But isn't that yellow badge in the screenshot due to LP? I wanted to point that out and nothing else. If I have done anything wrong, I'm sorry about that.

Ahhh, I misunderstood. Thanks for clarifying. Perhaps my previous post should have been addressed to Sachin ET instead of you. In any event I would not say either of you have done anything wrong, I was just reminding about it so we did not go off topic about an undesirable utility, but here I go off topic about i:eek:, so I'll stop doing that and try to break some software and report some bugs... speaking of which, a few recently reported issues should be fixed in upcoming build:

Increasing system fonts size pushes countdown timer backspace button off screen
https://jira.lineageos.org/browse/BUGBASH-300
Fixed by this commit: https://review.lineageos.org/#/c/181319/

An additional thin gray border line on call log panel creating the rsemblance of a white bar which behaves like an auto-hiding toolbar.
https://jira.lineageos.org/browse/BUGBASH-651
Fixed by this commit: https://review.lineageos.org/#/c/181852/

More about persisting bugs later, or next week.
 

sanchith.hegde

Senior Member
Oct 12, 2015
105
12
Understood. You have not afaiac.

Thanks! :)

Ahhh, I misunderstood. Thanks for clarifying. Perhaps my previous post should have been addressed to Sachin ET instead of you. In any event I would not say either of you have done anything wrong, I was just reminding about it so we did not go off topic about an undesirable utility, but here I go off topic about i:eek:, so I'll stop doing that and try to break some software and report some bugs... speaking of which, a few recently reported issues should be fixed in upcoming build:

Increasing system fonts size pushes countdown timer backspace button off screen
https://jira.lineageos.org/browse/BUGBASH-300
Fixed by this commit: https://review.lineageos.org/#/c/181319/

An additional thin gray border line on call log panel creating the rsemblance of a white bar which behaves like an auto-hiding toolbar.
https://jira.lineageos.org/browse/BUGBASH-651
Fixed by this commit: https://review.lineageos.org/#/c/181852/

More about persisting bugs later, or next week.

Welcome! No problem. :)
 

temper999

Member
Mar 25, 2014
24
4
Yesterday I switched from Cyanogenmod to LineageOS 14.1-20170721 on my Moto G 2015 (osprey) and open_gapps-arm-7.1-mini-20170724.
I wiped everything on that device and reformated the 32GB sdcard as internal device.
The device is not rooted.

After installing several apps I noticed that most of them were not installed on the sdcard instead on the internal storage.
After trying to force migrate them to the sdcard I receive a error message about not enought storage.

Is this a bug or a normal behavior?
I would like to use the sdcard space since the internal storage is nearly full.
 
Last edited:

IronTechmonkey

Recognized Contributor
Feb 12, 2013
10,055
18,112
Yesterday I switched from Cyanogenmod to LineageOS 14.1-20170721 on my Moto G 2015 (osprey) and open_gapps-arm-7.1-mini-20170724.
I wiped everything on that device and reformated the 32GB sdcard as internal device.
The device is not rooted.

After installing several apps I noticed that most of them were not installed on the sdcard instead on the internal storage.
After trying to force migrate them to the sdcard I receive a error message about not enought storage.

Is this a bug or a normal behavior?
I would like to use the sdcard space since the internal storage is nearly full.

Answered in Osprey LOS14.1 Q&A thread here: https://xdaforums.com/showpost.php?p=73163659&postcount=116
 
  • Like
Reactions: sevenrock

temper999

Member
Mar 25, 2014
24
4
I have deleted some of the installed Apps and tried to migrate again.
Now it had worked.

Now the 32GB card is fully used as internal storage. Everything is working as before on Cyanogenmod.
 
  • Like
Reactions: scattey

Char_G

Inactive Recognized Contributor
Apr 9, 2013
1,162
1,898
Missouri
FYI: Not only is LP off topic in this thread but it is considered warez and therefor off-topic everywhere on XDA (see XDA Rule 6). It is also just disrespectful to developers to discuss it on a developers' forum.

He is correct though, I work with the Substratum team and the yellow screen is part of our Substratum anti piracy, also @sanchith.hegde is known to me as a being very supportive of developers and is firmly against piracy. Perhaps informing @Sachin ET that use of piracy apps is disrespectful to devs would be more appropriate
 
  • Like
Reactions: sanchith.hegde

Top Liked Posts

  • There are no posts matching your filters.
  • 299
    zYkSW7S.png

    Code:
    /*
     * Your warranty is now void.
     *
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at me for messing up your device, I will laugh at you.
     */
    This works only on XT1540, XT1541, XT1542, XT1543, XT1544, XT1548 and XT1550.

    LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (Nougat), which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Working
    • Boots
    • RIL (Calls, SMS, Data)
    • Wifi
    • Bluetooth
    • Camera
    • Video Playback
    • VoLTE

    Not Working/Bugs
    • /

    Installation
    Requires Unlocked Bootloader & a custom recovery

    1. Place ROM & Gapps in your virtual SD
    2. Reboot in Bootloader Mode
    3. Go to "Recovery" (Vol +/Vol -) and confirm (power)
    4. Wipe Data/Factory Reset
    5. Wipe Dalvik cache
    6. Install the ROM zip
    7. DO NOT REBOOT
    8. Install the Gapps zip (optional)
    9. Reboot

    N.B. Official LineageOS builds are unrooted, if you want this feature back flash su (arm) (available here) then enable root access from Settings -> Developer options.
    Unroot is even easier, just flash "su removal" package available at the previous linked page.


    Downloads
    download.lineageos.org
    AndroidFileHost


    XDA:DevDB Information
    LineageOS 14.1, ROM for the Moto G 2015

    Contributors
    Alberto97, squid2
    Source Code: https://github.com/LineageOS

    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.10.x

    Version Information
    Status: Nightly

    Created 2016-09-21
    Last Updated 2017-09-04
    121
    Changelog

    10/01/2017
    • Reverted back to old radio stack
    • Reintroduced possible data toggling fix

    09/01/2017
    • Added back VoLTE support
    • January security patches
    • Updated blobs (MPI24.241-15.3)
    • Updated sdcardfs
    • Updated prima wlan
    • Many other security fixes

    CyanogenMod Builds:

    12/11/2016
    • Enabled sdcardfs
    • All the wifi issues should be fixed now

    10/11/2016
    • Upgraded to CM14.1
    • Camera is fully working now
    • Enforcing SELinux
    • CMActions: Better Integration with Settings
    • No more shim libs for Camera (and DRM) blobs

    21/09/2016
    • Initial release
    72
    Does it now support VoLTe? Because the aosp ROM still doesn't
    Did you really subscribe just to ask this? And you aren't the only one I see...

    How many times do you need to repeat that question? Think about that, I'm closing the thread for some days
    66
    Did you really subscribed just to ask this? And you aren't the only one I see...

    How many times do you need to repeat that question? Think about that, I'm closing the thread for some days

    It does seem that the question comes mainly from clowns members with very few posts (often just 1) and from a specific region.

    Not much we can do apart from deleting as they appear. I would request that other members who enjoy the normal interaction/collaboration in this thread avoid responding to the VOLTE and ETA Spam-ish posts and let me just delete them. I know the temptation to lambast them is high!!! You can probably guess what I would LIKE to say to them...

    Cheers
    54
    I'm releasing an unofficial LineageOS build which should improve GPS thanks to working Glonass. It should also have fixed the data toggling issue, let me know please. Additionally it includes updated sdcardfs, wlan drivers and fixes many security holes.
    I didn't actually want to release this because it's not yet clear if we will provide upgrading paths from CM14.1 (read dirty flash) or not but people already built it, so it doesn't matter anymore. Also I really wanted to know if the data issue is finally fixed since I wasn't able to reproduce it many times here.
    I'm going to rename the thread once official LineageOS builds starts. Hopefully it's clearer for those who still can't understand that we are just rebranding. Same people, same code but different name and infrastructures.